ETSI TS 102 760-2-2014 Intelligent Transport Systems (ITS) Communications Access for Land Mobiles (CALM) Test specifications for Access Technology Support (ISO 21218) Part 2 Test S.pdf

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

2、pect 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 o

3、ther 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 docume

4、nt is part 2 of a multi-part deliverable covering the test specifications for ITS access technology support (service access points and related procedures) ISO 21218 1 as identified below: Part 1: “Implementation Conformance Statement (ICS) proforma“; 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 ETSI

6、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. Introduction Communications for Intelligent Transport Systems (ITS) is standardized at ISO TC204 WG16 under the acronym CALM (Communications

7、 Access for Land Mobiles). The communications architecture of ITS and cooperative ITS and the concept of an ITS station (ITS-S) as a “Bounded Secured Managed Domain“ (BSMD) are specified in ISO 21217 i.1. The ITS-S architecture is based on the OSI model as illustrated in figure 1. An implementation

8、of a BSMD is named an “ITS station unit“ (ITS-SU), or more precisely a “Bounded Secured Managed Entity“ (BSME), which may consist of one or several physical units named “ITS station communication units“ (ITS-SCU). ITS-SCUs are interconnected via the ITS station-internal network specified in ISO 2121

9、7 i.1. ETSI ETSI TS 102 760-2 V1.2.1 (2014-06)5Figure 1: Simplified ITS station reference architecture The OSI protocol layers of an ITS-S are grouped as shown in figure 1: The ITS-S access layer contains OSI layers 1 and 2, using the MI-interface towards the ITS-S management entity and the SI-inter

10、face towards the ITS-S security entity, and providing the IN-interface towards the ITS-S networking Communications Access for Land Mobiles (CALM); Test specifications for Access Technology Support (ISO 21218); Part 1: Implementation Conformance Statement (ICS) proforma“. 3 ISO 24102-3: “Intelligent

11、Transport Systems - Communications access for land mobiles (CALM) - ITS station management - Part 3: Service access points“. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particula

12、r subject area. i.1 ISO 21217:2014: “Intelligent Transport Systems - Communications access for land mobiles (CALM) - Architecture“. i.2 ETSI EG 202 798: “Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing“. i.3 ISO 24102-4:2013: “Intelligent Transpor

13、t Systems - Communications access for land mobiles (CALM) - ITS station management - Part 4: Station-internal management communication“. i.4 ETSI TS 102 760-3: “Intelligent Transport Systems (ITS); Communications Access for Land Mobiles (CALM); Test specifications for Access Technology Support (ISO

14、21218); Part 3: Abstract Test Suite (ATS) and partial PIXIT proforma“. ETSI ETSI TS 102 760-2 V1.2.1 (2014-06)83 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO 21218 1, ISO 21217 i.1, ISO 24102-3 3, ISO 24102-4 i.3, ETSI

15、 TS 102 760-1 2 and ETSI EG 202 798 i.2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ISO 21218 1, ISO 21217 i.1, ISO 24102-3 3, ISO 24102-4 i.3, ETSI TS 102 760 1 2 and ETSI EG 202 798 i.2 apply. 4 Test suite architecture ISO 21218 1 cannot be tested

16、without being applied to a specific communication interface (CI) specified in ISO 21217 i.1. Thus the test architecture presented in figure 3 shows also the OSI communication layers PHY and DLL which are below the “Communication Adaptation Layer“ (CAL), both in the system under test (SUT) and in the

17、 ITS lower layers of the ITS test system. Managementadaptationentity(MAE)LayermanagementMI-SAPSecurityadaptationentity(SAE)CodecUppertesteraccessConfigurationaccessFigure 3: Test architecture The IUT is connected via three points of control and observation (PCO) with the TTCN-3 test components: “PCO

18、 IN-SAP“, providing access to the IN-SAP of the IUT; “PCO MI-SAP“, providing access to the MI-SAP of the IUT; “PCO Link“, the communication link. ETSI ETSI TS 102 760-2 V1.2.1 (2014-06)9Access to the MI-SAP and IN-SAP beneficially may be provided with the “ITS station-internal management communicati

19、ons protocol“ (IICP) specified in ISO 24102-4 i.3 as specified in ETSI TS 102 760-3 i.4. Alternative approaches for the upper tester access specified in ETSI EG 202 798 i.2 also are possible. NOTE: Not using IICP to access IM-SAP and MI-SAP may cause extra cost to the applicant in order to adapt the

20、 SUT to the test environment in a test house. A SUT may contain several CIs. However in a given test at a given time, only a single of them together with the functionality of ISO 21218 1 shall constitute the IUT. Testing of a SUT containing several CIs thus requires repetition of the tests for all C

21、Is contained in the SUT. Tests for a configuration with several active CIs in a single SUT are not considered in the present document. 5 TP basics 5.1 TP definition conventions The TP definition is built according to the guidelines provided in the ITS testing framework ETSI EG 202 798 i.2, applying

22、a formalized language with pre-defined keywords for the behaviour description. 5.2 TP identifier naming conventions The identifier of the TP is built according to table 1 as recommended in the ITS testing framework ETSI EG 202 798 i.2. Table 1: TP naming convention TP/ group = Group of tests SE Stat

23、e event transitions MB MIB I-Parameters HC Handling of CIs DP Handling of data plane x = Type of testing BV Valid Behaviour Tests BI Invalid Behaviour Tests = sequential number 0 Test Purpose Number, 01 99 5.3 Rules for behaviour description The description of the TP is built according to the guidel

24、ines provided in the ITS testing framework ETSI EG 202 798 i.2. 5.4 Sources of TP definitions All TPs are specified according to ISO 21218 1. ETSI ETSI TS 102 760-2 V1.2.1 (2014-06)105.5 TP proforma ETSI EG 202 798 i.2 proposes a TP proforma which is used in the present document. The fields of this

25、proforma as used in the present document are explained in table 1. Table 1: TP proforma field description TP Header TP ID The TP ID is a unique identifier according to the TP naming conventions in table 1. Test objective Short description of test purpose objective according to the requirements from

26、the base standard. Reference The reference indicates the clauses of the reference 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 speci

27、fied in table 2. This section is only used in case an optional or conditional behaviour needs to be selected. Mandatory behaviour is not identified here. 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 c

28、orresponding “Test Case“ (TC), when the execution of the initial 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, the IUT is expected to perform in order to conform to the ba

29、se specification. In the corresponding Test Case,“Pass“ or “Fail“ verdicts can be assigned there. Final conditions (optional) Definition of the events that the IUT is expected to perform or shall not perform, according to the base standard and following the correct execution of the actions in the ex

30、pected behaviour above. In the corresponding Test Case, the execution of the final conditions is evaluated for the assignment of the final verdict. The following initial conditions shall apply for all TPs, if not defined differently in a specific TP: The Link-ID of all CIs not being in the CI state

31、“not_existent“ and of all existent VCIs shall be known to the ITS test system, see figure 3. The MIB of the CI / VCI shall contain default values except for the I-Parameters ISO 21218 1 listed below. - “MinimumUserPriority“ shall be set to zero if not requested differently. Additional initial condit

32、ions may apply for specific TPs. According to ISO 24102-3 3, the service primitives COMMAND.confirm and REQUEST.confirm shall be present in case of an error and may be omitted otherwise. The optional presence of confirm service primitives with ErrStatus indicating success are not explicitly included

33、 in the TPs, but will have to be considered in the abstract test suite, i.e. in part 3 i.4 of this multi-part deliverable. ETSI ETSI TS 102 760-2 V1.2.1 (2014-06)115.6 PICS mnemonics The PICS mnemonics presented in table 2 are used in the TP proforma. Table 2: PICS mnemonics Mnemonic PICS item Expla

34、nation PICS_ACT ETSI TS 102 760-1 2 C.11/4 PICS_BCVCI ETSI TS 102 760-1 2 C.8/1 IUTis supporting BC-VCI transmitter PICS_CIAC1 ETSI TS 102 760-1 2 C.6/1 IUT is of CI access class CIAC-1 (no user authentication required, usage of CI is free of charge) PICS_CIAC2 ETSI TS 102 760-1 2 C.6/2 IUT is of CI

35、 access class CIAC-2 (access credentials required, usage of CI is subject of a service charge) PICS_CIAC3 ETSI TS 102 760-1 2 C.6/3 IUT is of CI access class CIAC-3 (access credentials required, usage of CI is free of charge) PICS_CIC_il1 ETSI TS 102 760-1 2 C.5/6 IUT is of CI class CIC-il1 (non-det

36、erministic ITS station-internal network interface) PICS_CIC_il2 ETSI TS 102 760-1 2 C.5/7 IUT is of CI class CIC-il2 (deterministic ITS station-internal network interface) PICS_CIC_l1 ETSI TS 102 760-1 2 C.5/1 IUT is of CI class CIC-l1 (multiple simultaneous peer stations transceiver) PICS_CIC_l2 ET

37、SI TS 102 760-1 2 C.5/2 IUT is of CI class CIC-l2 (single peer station transceiver) PICS_CIC_l3 ETSI TS 102 760-1 2 C.5/3 IUT is of CI class CIC-l3 (groupcast transmitter) PICS_CIC_l4 ETSI TS 102 760-1 2 C.5/4 IUT is of CI class CIC-l4 (broadcast receiver only) PICS_CIC_l5 ETSI TS 102 760-1 2 C.5/5

38、IUT is of CI class CIC-l5 (CEN / Japanese DSRC) PICS_CONN ETSI TS 102 760-1 2 C.11/7 IUT is supporting the connection procedure PICS_CRCIP_I ETSI TS 102 760-1 2 C.11/10 IUT is supporting the Cross-CI prioritization - interferer procedure PICS_CRCIP_V ETSI TS 102 760-1 2 C.11/9 IUT is supporting the

39、Cross-CI prioritization - victim procedure PICS_DISCONN ETSI TS 102 760-1 2 C.11/8 IUT is supporting the disconnection procedure PICS_DYNREG ETSI TS 102 760-1 2 C.1/1 Dynamic registration using the standardized registration procedure PICS_INACT ETSI TS 102 760-1 2 C.11/3 IUT is supporting the inacti

40、vation procedure PICS_INUDS ETSI TS 102 760-1 2 C.12/2 IUT is supporting the IN-UNITDATA-STATUS service PICS_IPNO ETSI TS 102 760-1 2 C.24 any selected I-Parameter IUT is supporting notification-only I-Parameters PICS_IPRO ETSI TS 102 760-1 2 C.21 and C.22 any selected I-Parameter IUT is supporting

41、read-only I-Parameters PICS_IPRW ETSI TS 102 760-1 2 C.19 and C.20 any selected I-Parameter IUT is supporting read/write I-Parameters PICS_IPWO ETSI TS 102 760-1 2 C.23 any selected I-Parameter IUT is supporting write-only I-Parameters PICS_MAC48 ETSI TS 102 760-1 2 C.4/1 IUT uses 48 bit MAC address

42、es PICS_MCVCI ETSI TS 102 760-1 2 C.8/2 IUT is supporting MC-VCI transmitter PICS_REJECT ETSI TS 102 760-1 2 C.11/20 IUT is supporting rejection of DL-UNITDATA.requests with user priority less than given in parameter “MinimumUserPriority“ PICS_RES ETSI TS 102 760-1 2 C.11/6 IUT is supporting the res

43、uming procedure PICS_RIM ETSI TS 102 760-1 2 C.11/12 IUT is supporting the Regulatory Information Management procedure PICS_SNAP ETSI TS 102 760-1 2 C.13/1 IUT is supporting SNAP PICS_SUSP ETSI TS 102 760-1 2 C.11/5 IUT is supporting the suspension procedure PICS_UCVCI ETSI TS 102 760-1 2 C.8/3 IUT

44、is supporting UC-VCI (transmitter and receiver) ETSI ETSI TS 102 760-2 V1.2.1 (2014-06)12Mnemonic PICS item Explanation PICS_WAKEUP ETSI TS 102 760-1 2 C.15/4 IUT is supporting the WakeUp command PICS_IN_UNITDATA_STATUS ETSI TS 102 760-1 2 C.12/2 IUT is supporting the IN-UNITDATA-STATUS service prim

45、itive PICS_MONITOR ETSI TS 102 760-1 2 C.15/11 IUT is supporting the MONITOR command 6 Test purposes 6.1 CI state transitions 6.1.1 Valid behaviour tests TP ID SE/BV/01 Test objective IUT with CI supporting 48-bit MAC addresses registers correctly at the management entity Reference ISO 21218 1, clau

46、se 6.4.2 PICS Selection PICS_DYNREG AND PICS_MAC48 Initial conditions with the IUT being in the CI state “not-existent“ Expected behaviour ensure that when the IUT starts operation then the IUT registers properly at the ITS-S management Final conditions ensure that when the IUT presented the state “

47、registered“ to the ITS-S management then the IUT has a LocalCIID representing the 48 bit MAC address of the IUT ETSI ETSI TS 102 760-2 V1.2.1 (2014-06)13TP ID SE/BV/02 Test objective IUT with CI not supporting 48-bit MAC addresses registers correctly at the management entity Reference ISO 21218 1, c

48、lause 6.4.2 PICS Selection PICS_DYNREG AND NOT PICS_MAC48 Initial conditions with the IUT being in the CI state “not-existent“ Expected behaviour ensure that when the IUT starts operation then the IUT registers properly at the ITS-S management Final conditions ensure that when the IUT presented the

49、state “registered“ to the ITS-S management then the IUT has a LocalCIID created from ITS-SCU-ID and MedID TP ID SE/BV/03 Test objective IUT repeats registration as long as management entity does not confirm it Reference ISO 21218 1, clause 6.4.2 PICS Selection PICS_DYNREG Initial conditions with the IUT being in the CI state “not-existent Expected behaviour ensure that when