ETSI TS 102 797-2-2014 Intelligent Transport Systems (ITS) Communications Access for Land Mobiles (CALM) Test specifications for ITS station management (ISO 24102) Part 2 Test Suit.pdf

1、 ETSI TS 102 797-2 V1.2.1 (2014-06) Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102); Part 2: Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respec

2、t of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of othe

3、r IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS). The present document

4、is part 2 of a multi-part deliverable covering Communications Access for Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102), as identified below: Part 1: “Protocol Implementation Conformance Statement (PICS) specification“; Part 2: “Test Suite Structure and Test Purposes

5、 (TSS Part 3: “Abstract Test Suite (ATS) and partial PIXIT proforma“. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “may not“, “need“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETS

6、I Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)51 Scope The present document provides the test suite structure and test purpose specification for

7、the ISO protocols specified in ISO 24102-4 1 and ISO 24102-5 2 in compliance with the relevant requirements, and in accordance with the relevant guidance given in EG 202 798 i.1. 2 References References are either specific (identified by date of publication and/or edition number or version number) o

8、r non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/do

9、cbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. 1 ISO 24102-4:2013

10、: “Intelligent transport systems - Communications access for land mobiles (CALM) - ITS station management - Part 4: Station-internal management communications“. 2 ISO 24102-5:2013: “Intelligent transport systems - Communications access for land mobiles (CALM) - ITS station management - Part 5: Fast

11、service advertisement protocol (FSAP)“. 3 ETSI TS 102 797-1 (V1.2.1): “Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for ITS station management (ISO 24102); Part 1: Protocol Implementation Conformance Statement (PICS) specification“. 2.2 Info

12、rmative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI EG 202 798: “Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability te

13、sting“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO 24102-4 1, ISO 24102-5 2 and EG 202 798 i.1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ISO 24102-4 1, ISO 24102-

14、5 2 and EG 202 798 i.1 apply. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)64 Test suite structure In general, the conformance test system architecture presented in the ITS testing framework EG 202 798 i.1 extended as illustrated in figure 1 applies. CodecFigure 1: General conformance test system architec

15、ture for SUTs Such SUTs which support the “ITS station-internal Management Communications Protocol“ (IICP) ISO 24102-4 1 may benefit from the conformance test system architecture illustrated in figure 2, where the access to the IUT is performed via remote access to the management SAPs applying IICP.

16、 This may be applied in general for all three ports (utPort, ltPort, cnPort). In case of testing IICP itself, the ITS lower layers end up in the ITS station-internal network. Upper tester applicationSUTUpper tester and configuration / notification transportProtocol stack for access to ITS station-in

17、ternal networkITS lower layersIUTProtocol in ITS management entityLower layers link(maybe the ITS station-internal network)Upper tester and configuration / notification transport linkITS station-internal networkITS test systemConfiguration / notification transportTest controlTTCN-3 test componentsUp

18、per tester transportutPortltPortITS lower layerscnPortTest adapterDispatcherFigure 2: Conformance test system architecture for SUTs compliant with ISO 24102-4 1 ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)7Testing a protocol which resides inside the ITS management entity does not follow strictly the illu

19、strations given in the ITS testing framework EG 202 798 i.1. Nevertheless the principles outlined there apply also. The essential difference is, that the access from the “upper tester application“ and from the “ITS lower layers“ to the IUT is via the management SAPs. Note that for testing of FSAP an

20、d IICP, the ITS lower layers connect to the IUT via MF-SAP only. 5 Test purpose basics 5.1 TP definition conventions The TP definition is built according to the guidelines provided in the ITS testing framework EG 202 798 i.1, applying a formalized language with pre-defined keywords for the behaviour

21、 description. 5.2 TP identifier naming conventions The identifier of the TP is built according to tables 1 and 2 as recommended in the ITS testing framework EG 202 798 i.1. Table 1: TP naming convention for the ITS station-internal management communications protocol (IICP) specified in ISO 24102-4 1

22、 TP/ = root IICP ITS station-Internal management Communication Protocol = group MGM Management COM Communication = type of testing BV Valid Behaviour tests BI Invalid Syntax or Behaviour Tests = sequential number 01 to 99 TPs for the IICP are specified in clause 6. Table 2: TP naming convention for

23、the Fast Service Advertisement Protocol (FSAP) specified in ISO 24102-5 2 TP/ = root FSAP Fast Service Advertisement Protocol = group SP Service provider SU Service user = sub-group HR Combined ITS-S host and ITS-S router HO ITS-S host only RO ITS-S router only = type of testing BV Valid Behaviour t

24、ests BI Invalid Syntax or Behaviour Tests = sequential number 01 to 99 TPs for FSAP are specified in clause 7. 5.3 Rules for behaviour description The description of the TP is built according to the guidelines provided in the ITS testing framework EG 202 798 i.1. 5.4 Sources of TP definitions All TP

25、s are specified according to ISO 24102-4 1 and ISO 24102-5 2. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)85.5 TP proforma EG 202 798 i.1 proposes a TP proforma which is used in the present document. The fields of this proforma as used in the present document are explained in table 3. Table 3: TP proform

26、a field description TP Header TP ID The TP ID is a unique identifier according to the TP naming conventions in tables 1 and 2. Test objective Short description of test purpose objective according to the requirements from the base standard. Reference The reference indicates the clauses of the referen

27、ce standard specifications in which the conformance requirement is expressed. PICS selection Reference to the PICS statement involved for selection of the TP. Contains a Boolean expression. May contain PICS acronyms specified in tables 4 and 5. This section is only used in case an optional or condit

28、ional behaviour needs to be selected. Mandatory behaviour is identified by an empty field. TP Behaviour Initial conditions (optional) The initial conditions define in which initial state the IUT has to be to apply the actual TP. In the corresponding “Test Case“ (TC), when the execution of the initia

29、l condition does not succeed, it leads to the assignment of an Inconclusive verdict. Expected behaviour (TP body) Definition of the events, which are parts of the TP objective, and the IUT are expected to perform in order to conform to the base specification. In the corresponding TC, “Pass“ or “Fail

30、“ verdicts can be assigned there. 5.6 PICS mnemonics The PICS mnemonics presented in tables 4 and 5 are used in the TP proforma. Table 4: PICS mnemonics for FSAP Mnemonic PICS item PICS_FSAP_ROLE_SP TS 102 797-1 3 B.2/1 PICS_FSAP_ROLE_SU TS 102 797-1 3 B.2/2 PICS_ITS_S_INW TS 102 797-1 3 B.6/1 PICS_

31、ROLE_HONLY TS 102 797-1 3 B.5/1 PICS_ROLE_RH TS 102 797-1 3 B.5/3 PICS_ROLE_RONLY TS 102 797-1 3 B.5/2 PICS_SIP_N_CTX TS 102 797-1 3 B.4/2 PICS_SIP_W_CTX TS 102 797-1 3 B.4/1 PICS_SUT_AT_CHG TS 102 797-1 3 B.1/2 PICS_SUT_CH_CHG TS 102 797-1 3 B.1/1 Table 5: PICS mnemonics for IICP Mnemonic PICS item

32、 PICS_IICP_MGM TS 102 797-1 3 A.8/1 PICS_ROLE_HONLY TS 102 797-1 3 A.1/1 PICS_ROLE_RH TS 102 797-1 3 A.1/3 PICS_ROLE_RONLY TS 102 797-1 3 A.1/2 ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)96 TPs for IICP 6.1 Management 6.1.1 Valid behaviour tests TP Id IICP/MGM/BV/01 Test objective Generation of ITS-SCUa

33、live message after power on - no other ITS-SCU in the SUT Reference ISO 24102-4 1, clauses 9.1 and 9.2 PICS Selection PICS_IICP_MGM Initial conditions with the IUT having no knowledge about other ITS-SCUs in the SUT Expected behaviour ensure that when the IUT starting then the IUT generates an ITS-S

34、CUalive (new) message with DestinationITS-SCU-ID=65535 and with SourceITS-SCU-ID equal to the own ITS-SCU ID, indicating its IST-SCUtype, and forwards this with MF-COMMAND IICrequestTX to the IICA TP Id IICP/MGM/BV/02 Test objective Reception of ITS-SCUalive (new) message with no address conflict Re

35、ference ISO 24102-4 1, clauses 9.1 and 9.2 PICS Selection PICS_IICP_MGM Initial conditions with the IUT having its own ITS-SCU-ID allocated Expected behaviour ensure that when the IUT having received an ITS-SCUalive (new) message without address conflict then the IUT shall acknowledge this with Erro

36、rStatus = 0 using MF-COMMAND IICresponseTX ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)10TP Id IICP/MGM/BV/03 Test objective Reception of ITS-SCUalive (new) message with address conflict Reference ISO 24102-4 1, clauses 9.1 and 9.2 PICS Selection PICS_IICP_MGM Initial conditions with the IUT having its o

37、wn ITS-SCU-ID allocated Expected behaviour ensure that when the IUT having received an ITS-SCUalive (new) message with address conflict, i.e. from an ITS-SCU having the same ITS-SCU-ID then the IUT shall acknowledge this with ErrorStatus = 2 using MF-COMMAND IICresponseTX for transmission to all ITS

38、-SCUs TP Id IICP/MGM/BV/04 Test objective Reception of ITS-SCUalive (alive) message with no address conflict Reference ISO 24102-4 1, clauses 9.1 and 9.3 PICS Selection PICS_IICP_MGM Initial conditions with the IUT having its own ITS-SCU-ID allocated Expected behaviour ensure that when the IUT havin

39、g received an ITS-SCUalive (alive) message without address conflict then the IUT does not show any visible reaction TP Id IICP/MGM/BV/05 Test objective Periodic transmission of ITS-SCUalive (alive) message Reference ISO 24102-4 1, clauses 9.1 and 9.3 PICS Selection PICS_IICP_MGM Initial conditions w

40、ith the IUT having its own ITS-SCU-ID allocated Expected behaviour ensure that when the IUT having transmitted an ITS-SCUalive (alive) message with DestinationITS-SCU-ID=65535 and with SourceITS-SCU-ID equal to its own ITS-SCU ID, which does not result in an address conflict then the IUT transmits t

41、he next ITS-SCUalive (alive) message after the time span given in parameter Talive. ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)11TP Id IICP/MGM/BV/06 Test objective Transmission of ITS-SCUalive (delete) message Reference ISO 24102-4 1, clauses 9.1 and 9.4 PICS Selection PICS_IICP_MGM Initial conditions

42、with the IUT having its own ITS-SCU-ID allocated Expected behaviour ensure that when the IUT wants to shut down and stop operation then the IUT transmits an ITS-SCUalive (delete) message with DestinationITS-SCU-ID=65535 and with SourceITS-SCU-ID equal to its own ITS-SCU ID using MF-COMMAND IICreques

43、tTX 6.1.2 Invalid behaviour tests TP Id IICP/MGM/BI/01 Test objective Reception of ITS-SCUalive (alive) message with address conflict Reference ISO 24102-4 1, clauses 9.1 and 9.3 PICS Selection PICS_IICP_MGM Initial conditions with the IUT having its own ITS-SCU-ID allocated Expected behaviour ensur

44、e that when the IUT having received an ITS-SCUalive (alive) message with address conflict , i.e. from an ITS-SCU having the same ITS-SCU-ID then the IUT shall acknowledge this with ErrorStatus = 2 using MF-COMMAND IICresponseTX for transmission to all ITS-SCUs, the IUT shall delete its own ITS-SCU-I

45、D and shall register newly by sending an ITS-SCU (new) message indicating a new ITS-SCU-ID with MF-COMMAND IICrequestTX to the IICA for transmission to all ITS-SCUs TP Id IICP/MGM/BI/02 Test objective Reception of ITS-SCUalive message with unknown AliveMessage Reference ISO 24102-4 1, clause 9 PICS

46、Selection PICS_IICP_MGM Initial conditions with the IUT having own ITS-SCU-ID Expected behaviour ensure that when the IUT having received an ITS-SCUalive message with unknown AliveMessage then the IUT acknowledges the message with ErrorStatus 3 ETSI ETSI TS 102 797-2 V1.2.1 (2014-06)12TP Id IICP/MGM

47、/BI/03 Test objective Reception of ITS-SCUalive message with unknown ITS-SCU type Reference ISO 24102-4 1, clause 9 PICS Selection PICS_IICP_MGM Initial conditions with the IUT having its own ITS-SCU-ID allocated Expected behaviour ensure that when the IUT having received an ITS-SCUalive message wit

48、h unknown ITS-SCU type then the IUT acknowledges the message with ErrorStatus 4 6.2 Communications 6.2.1 Valid behaviour tests TP Id IICP/COM/BV/01 Test objective Transmission of IIC-Request VCI-info to all types of ITS-SCUs Reference ISO 24102-4 1, clause 8.2.1 and annex B.2.3 PICS Selection Initia

49、l conditions with the IUT having its own ITS-SCU-ID allocated Expected behaviour ensure that when the IUT having received the request to send an VCI-info request message to all ITS-SCUs then the IUT generates an VCI-info request message with DestinationITS-SCU-ID=65535 and with SourceITS-SCU-ID equal to its own ITS-SCU-ID, and fo