1、 ETSI TS 103 191-2 V1.2.1 (2017-03) Intelligent Transport Systems (ITS); Testing; Conformance test specifications for Facilities layer protocols and communication requirements for infrastructure services; Part 2: Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs n
2、otified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/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
3、as to the existence of other 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 (
4、ITS). The present document is part 2 of a multi-part deliverable covering Conformance test specifications for Facilities layer protocols and communication requirements for infrastructure services, as identified below: Part 1: “Test requirements and Protocol Implementation Conformance Statement (PICS
5、) pro forma“; Part 2: “Test Suite Structure and Test Purposes (TSS Part 3: “Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)“. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not
6、“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI 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 103 191-2 V1.2.1 (2017-03)6 1 Scope The pres
7、ent document provides the Test Suite Structure and Test Purposes (TSS Vehicular Communications; Basic Set of Applications; Facilities layer protocols and communication requirements for infrastructure services“. 3 ETSI TS 103 191-1 (V1.2.1): “Intelligent Transport Systems (ITS); Testing; Conformance
8、test specifications for Facilities layer protocols and communication requirements for infrastructure services; Part 1: Test requirements and Protocol Implementation Conformance Statement (PICS) pro forma“. 2.2 Informative references References are either specific (identified by date of publication a
9、nd/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time o
10、f publication, ETSI cannot guarantee their long term validity. 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 (V1.1.1): “Intelligent Transport Systems (ITS); Testi
11、ng; Framework for conformance and interoperability testing“. i.2 ISO/IEC 9646-1 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. i.3 ISO/IEC 9646-2 (1994): “Information technology - Open Systems Interconnectio
12、n - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. ETSI ETSI TS 103 191-2 V1.2.1 (2017-03)7 i.4 ISO/IEC 9646-7 (1995): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conforma
13、nce Statements“. i.5 ETSI ETS 300 406 (1995): “Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given
14、 in SAE J2735 1, ISO/IEC 9646-1 i.2 and in ISO/IEC 9646-7 i.4 apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite BTP Basic Transport Protocol BV Valid test events for Behaviour tests GN GeoNetworking ISO International Organiz
15、ation for Standardization ITS Intelligent Transport Systems IUT Implementation Under Test IVI Infrastructure to Vehicle Information IVIM IVI-message MAPEM MapData Messages MSD Message Dissemination MSP Message Processing PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement RLT R
16、oad and Lane Topology SAE Society of Automotive Engineers SHB Single Hop Broadcast SPATEM Signal Phase And Timing Messages SREM Signal Request Message SSEM Signal Response Message TLC Traffic Light Control TLM Traffic Light Manoeuvre TP Test Purposes TSS Test Suite Structure ETSI ETSI TS 103 191-2 V
17、1.2.1 (2017-03)8 4 Test Suite Structure (TSS) 4.1 Structure for MAPEM-SPATEM tests Table 1 shows the MAPEM-SPATEM Test Suite Structure (TSS) including its subgroups defined for conformance testing. Table 1: TSS for MAPEM-SPATEM Root Group Category MAPEM-SPATEM Message Dissemination Valid Message pro
18、cessing ValidThe test suite is structured as a tree with the root defined as MAPEM-SPATEM. The tree is of rank 2 with the first rank a Group and the second a category. The second rank is the standard ISO conformance test categories. 4.1.1 Test groups 4.1.1.1 Introduction The test suite has a total o
19、f three levels. The first level is the root. The second level separates the root into various functional areas. The third level is the standard ISO conformance test categories. 4.1.1.2 Root The root identifies the MapData and SPAT Messages given in SAE J2735 1 and ETSI TS 103 301 2. 4.1.1.3 Groups T
20、his level contains two functional areas identified as: Message Dissemination Message Processing 4.1.1.4 Categories This level contains the standard ISO conformance test categories limited to valid behaviour. 4.2 Structure for IVIM tests Table 2 shows the IVIM Test Suite Structure (TSS) including its
21、 subgroups defined for conformance testing. Table 2: TSS for IVIM Root Group Category IVIM Message Dissemination Valid Message processing ValidThe test suite is structured as a tree with the root defined as IVI. The tree is of rank 2 with the first rank a Group and the second a category. The second
22、rank is the standard ISO conformance test categories. ETSI ETSI TS 103 191-2 V1.2.1 (2017-03)9 4.2.1 Test groups 4.2.1.1 Introduction The test suite has a total of three levels. The first level is the root. The second level separates the root into various functional areas. The third level is the sta
23、ndard ISO conformance test categories. 4.2.1.2 Root The root identifies the IVI Messages given in ETSI TS 103 301 2. 4.2.1.3 Groups This level contains two functional areas identified as: Message Dissemination Message Processing 4.2.1.4 Categories This level contains the standard ISO conformance tes
24、t categories limited to valid behaviour. 4.3 Structure for SREM-SSEM tests Table 3 shows the SREM-SSEM Test Suite Structure (TSS) including its subgroups defined for conformance testing. Table 3: TSS for SREM-SSEM Root Group Category SREM-SSEM Message Dissemination Valid Message processing ValidThe
25、test suite is structured as a tree with the root defined as SREM-SSEM. The tree is of rank 2 with the first rank a Group and the second a category. The second rank is the standard ISO conformance test categories. 4.3.1 Test groups 4.3.1.1 Introduction The test suite has a total of three levels. The
26、first level is the root. The second level separates the root into various functional areas. The third level is the standard ISO conformance test categories. 4.3.1.2 Root The root identifies the SREM and SSEM given in ETSI TS 103 301 2. ETSI ETSI TS 103 191-2 V1.2.1 (2017-03)10 4.3.1.3 Groups This le
27、vel contains two functional areas identified as: Message Dissemination Message Processing 4.3.1.4 Categories This level contains the standard ISO conformance test categories limited to valid behaviour. 5 Test Purposes (TPs) 5.1 Introduction 5.1.1 TP definition conventions The TP definition is built
28、according to ETSI EG 202 798 i.1. 5.1.2 TP Identifier naming conventions The identifier of the TP is built according to table 4. Table 4: TP naming convention Identifier TP/ Example = root IS_TLM IS_RLT IS_IVI IS_TLC = group MSGF Message Dissemination EVUP Event Update EVGN Event Generation EVTR Eve
29、nt Termination COMM Communication GFQ Timers SEC_SND Send behaviour of Security SSP_SND Send behaviour of Specific service Permission SSP_RCV Receive behaviour of Specific service Permission = type of testing BV Valid event tests = sequential number 01 to 99 5.1.3 Rules for the behaviour description
30、 The description of the TP is built according to ETSI EG 202 798 i.1. SAE J2735 1 does not use finite state machine concept. As consequence, the test purposes use a generic “Initial State“ that corresponds to a state where the IUT is ready for starting the test execution. Furthermore, the IUT shall
31、be left in this “Initial State“, when the test is completed. Being in the “Initial State“ refers to the starting point of the initial device configuration. There are no pending actions, no instantiated buffers or variables, which could disturb the execution of a test. ETSI ETSI TS 103 191-2 V1.2.1 (
32、2017-03)11 5.1.4 Sources of TP definitions All TPs have been specified according to SAE J2735 1 and ETSI TS 103 301 2. 5.1.5 Mnemonics for PICS reference To avoid an update of all TPs when the PICS document is changed, table 5 introduces mnemonics name and the correspondence with the real PICS item
33、number. The PICS item column refers to tables and items of ETSI TS 103 191-1 3. The PICS item as defined in ETSI TS 103 191-1 3 shall be used to determine the test applicability. Table 5: Mnemonics for PICS reference Mnemonic PICS item PICS_SPATEM_GENERATION A.2/3 PICS_SPATEM_RECEPTION A.2/4PICS_MAP
34、EM_GENERATION A.2/1 PICS_MAPEM_RECEPTION A.2/2PICS_IVIM_GENERATION A.3/1PICS_IVIM_RECEPTION A.3/5 PICS_IVIM_UPDATE A.3/2PICS_IVIM_CANCELLATION A.3/3 PICS_IVIM_NEGATION A.3/4PICS_SREM_GENERATION A.5/1 PICS_SREM_RECEPTION A.5/2PICS_SSEM_GENERATION A.5/3 PICS_SSEM_RECEPTION A.5/4PICS_IS_IUT_SECURED A.1
35、/1PICS_T_GENIVIMMIN A.4/1 PICS_T_GENIVIMMAX A.4/25.2 Requirements 5.2.1 Traffic Light Manoeuvre (TLM) service 5.2.1.1 Check the message protocol version TP Id TP_IS_TLM_MSGF_BV_01 Summary Check that protocolVersion is set to 1 and messageID is set to 4 Reference ETSI TS 103 301 2, clause 5.3 PICS Se
36、lection PICS_SPATEM_GENERATION Expected behaviour with the IUT being in the “initial state“ and the IUT sending SPATEM ensure that when a SPATEM is generated then the IUT sends a valid SPATEM containing ITS PDU header containing protocolVersion indicating value 1 and containing messageID indicating
37、value 4 ETSI ETSI TS 103 191-2 V1.2.1 (2017-03)12 TP Id TP_IS_TLM_MSGF_BV_02 Summary Check that the IUT can successfully process all mandatory fields of SPATEM received Reference ETSI TS 103 301 2, clause 5.3 PICS Selection PICS_SPATEM_RECEPTION Expected behaviour with the IUT being in the “initial
38、state“ and the IUT having receive a valid SPATEM ensure that when the IUT receives a valid SPATEM then the IUT forwards the SPATEM content to upper layers and the IUT forwards the SPATEM content to other facilities 5.2.1.2 TLM service trigger, update, repetition and termination TP Id TP_IS_TLM_EVGN_
39、BV_01 Summary Check that TLM Service generates a new SPATEM on reception of a valid AppSPATEM _Start request Reference ETSI TS 103 301 2, clause 5.4.2 PICS Selection PICS_SPATEM_GENERATION Expected behaviour with the IUT being in the “initial state“ and the IUT has not sent any SPATEM yet ensure tha
40、t when the IUT receives an AppSPATEM_Start request from the application layer then the IUT sends a valid SPATEM TP Id TP_IS_TLM_EVGN_BV_02 Summary Check that TLM Service generates SPATEM are time ordered Reference ETSI TS 103 301 2, clause 5.4.2 PICS Selection PICS_SPATEM_GENERATION Expected behavio
41、ur with the IUT being in the “initial state“ and the IUT has sent a SPATEM ensure that when several SPATEM are generated then the IUT sends SPATEM in time order TP Id TP_IS_TLM_EVGN_BV_03 Summary Check that TLM Service terminates on reception of a valid AppSPATEM _Stop request Reference ETSI TS 103
42、301 2, clause 5.4.2 PICS Selection PICS_SPATEM_GENERATION Expected behaviour with the IUT being in the “initial state“ and the IUT sending SPATEM ensure that when the IUT receives an AppSPATEM _Stop request from the application layer then the IUT stops sending SPATEM ETSI ETSI TS 103 191-2 V1.2.1 (2
43、017-03)13 TP Id TP_IS_TLM_EVGN_BV_04 Summary Check that TLM Service generates a new SPATEM on reception of a valid AppSPATEM_Trigger request Reference ETSI TS 103 301 2, clause 5.4.2 PICS Selection PICS_SPATEM_GENERATION Expected behaviour with the IUT being in the “initial state“ ensure that when t
44、he IUT receives an AppSPATEM_Trigger request from the application layer then the IUT sends a valid SPATEM 5.2.1.3 Check presence of destination area TP Id TP_IS_TLM_COM_BV_01 Summary Check that TLM Service provides the destination area in SPATEM Reference ETSI TS 103 301 2, clause 5.4.3.2 PICS Selec
45、tion PICS_SPATEM_GENERATION Expected behaviour with the IUT being in the “initial state“ and the IUT sending SPATEM ensure that when a SPATEM is generated then the IUT sends a valid SPATEM containing spat containing regional containing at least on region indicating a regionId and indication a regExt
46、Value 5.2.1.4 Check BTP type and port number TP Id TP_IS_TLM_COM_BV_02 Summary Check that SPATEM uses BTP_B packet Check that the destination port for SPATEM is set to 2004 Reference ETSI TS 103 301 2, clauses 10.2 and 5.4.3.2 PICS Selection PICS_SPATEM_GENERATION Expected behaviour with the IUT bei
47、ng in the “initial state“ and the IUT sending SPATEM ensure that when a SPATEM is generated then the IUT sends a valid SPATEM encapsulated in a BTP-B packet containing a destination port value set to 2004 and containing a destination port info value set to 0 ETSI ETSI TS 103 191-2 V1.2.1 (2017-03)14
48、 5.2.1.5 Check destination type TP Id TP_IS_TLM_COM_BV_03 Summary Check that TLM service encapsulates SPATEM in a GBC with the HeaderType field set to the value of 4 Reference ETSI TS 103 301 2, clause 5.4.3.2 PICS Selection PICS_SPATEM_GENERATION Expected behaviour with the IUT being in the “initia
49、l state“ and the IUT sending SPATEM ensure that when a SPATEM is generated then the IUT sends a valid SPATEM encapsulated in a GBC packet containing a correctly formatted Common Header containing HeaderType field indicating the value 4 5.2.1.6 TLM security parameters 5.2.1.6.1 Check TLM ITS AID value TP Id TP_IS_TLM_SEC_SND_BV_01 Summary Check that TLM service uses certificate containing valid ITS AID to sign SPATEM messages Reference ETSI TS 103 301 2, clause 5.4.3.2 PICS Selection PICS_SPATEM_GENERAT
