ETSI TS 102 486-2-2-2006 Electromagnetic compatibility and Radio spectrum Matters (ERM) Road Transport and Traffic Telematics (RTTT) Test specifications for Dedicated Short Range C.pdf

1、 ETSI TS 102 486-2-2 V1.1.1 (2006-08)Technical Specification Electromagnetic compatibility and Radio spectrum Matters (ERM);Road Transport and Traffic Telematics (RTTT);Test specifications for Dedicated Short Range Communication (DSRC) transmission equipment;Part 2: DSRC application layer;Sub-Part 2

2、: Test Suite Structure and Test Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Pol

3、icy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given 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 Tec

4、hnical Specification (TS) has been produced by ETSI Technical Committee Electromagnetic compatibility and Radio spectrum Matters (ERM). The present document is part 2, sub-part 2 of a multi-part deliverable covering Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated Shor

5、t Range Communication (DSRC) transmission equipment, as identified below: Part 1: “DSRC data link layer: medium access and logical link control“; Part 2: “DSRC application layer“; Sub-part 1: “Protocol Implementation Conformance Statement (PICS) proforma specification“; Sub-part 2: “Test Suite Struc

6、ture and Test Purposes (TSS Sub-part 3: “Abstract Test Suite (ATS) and partial PIXIT proforma“. ETSI ETSI TS 102 486-2-2 V1.1.1 (2006-08)5 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the ERM/TG37 Dedicated Short Range Communication (DSRC); Appl

7、ication layer. The objective of the present document is to provide a basis for conformance tests for DSRC equipment giving a high probability of inter-operability between different manufacturers equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 5 and ISO/IEC 9646

8、-2 6) as well as the ETSI rules for conformance testing (ETS 300 406 4) are used as a basis for the test methodology. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identifi

9、ed by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might

10、be found at http:/docbox.etsi.org/Reference. 1 CEN EN 12834 (2003): “Road transport and traffic telematics - Dedicated Short Range Communication (DSRC) - DSRC application layer“. 2 CEN EN 12253 (2003): “Road transport and traffic telematics - Dedicated short-range communication - Physical layer usin

11、g microwave at 5,8 GHz“. 3 CEN EN 13372 (2003): “Road transport and traffic telematics (RTTT) - Dedicated short-range communication - Profiles for RTTT“. 4 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodo

12、logy“. 5 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 6 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Tes

13、t Suite specification“. 7 ISO/IEC 9646-6: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. 8 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology

14、and framework - Part 7: Implementation Conformance Statement“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 8, EN 12253 2, EN 12834 1 and EN 13372 3 apply. ETSI ETSI TS 102 486-2-2 V1.1.1 (2006-08)6 3.2 Ab

15、breviations For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 5, ISO/IEC 9646-6 7, ISO/IEC 9646-7 8, EN 12834 1 and the following apply: ASP Abstract Service Primitive ATS Abstract Test Suite BI Invalid Behaviour tests BST Beacon Service Table BV Valid Behaviour tes

16、ts DSRC Dedicated Short Range Communication IUT Implementation Under Test LID Link IDentifier MAC Medium Access Control OBU On Board Unit PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement PrWRq MAC frame Private Window Request RSU Road Side Unit SUT System Under Test TP Test

17、Purpose TSS Test Suite Structure VST Vehicle Service Table 4 Test Suite Structure (TSS) 4.1 Structure Table 1 shows the Application Test Suite Structure (TSS) including its subgroups defined for the conformance testing. Table 1: TSS for DSRC Application Group Type of SUT Behaviour Application Layer

18、T-Kernel On Board Unit Valid behaviour Invalid behaviour Road Side Unit Valid behaviour Invalid behaviour Application Layer I-Kernel On Board Unit Valid behaviour Invalid behaviour Road Side Unit Valid behaviour Invalid behaviour 4.2 Test groups The test groups are organized in three groups. The fir

19、st is designed for the application T-kernel testing. The second is designed for Application I-kernel testing and the third is designed for Application B-kernel testing. 4.3 Type of SUT test groups The type of SUT test groups are organized in two groups. The first is designed for the On Board Unit (O

20、BU) testing and the second is designed for Road Side Unit testing (RSU). ETSI ETSI TS 102 486-2-2 V1.1.1 (2006-08)7 4.4 Behaviour test groups 4.4.1 Valid Behaviour (BV) tests This test sub group shall verify that the IUT reacts in conformity with the EN, after receipt or exchange of a valid Protocol

21、 Data Units (PDUs). Valid PDUs means that the exchange of messages and the content of the exchanged messages are considered as valid. 4.4.2 Invalid Behaviour (BI) tests This test sub group shall verify that the IUT reacts in conformity with the EN, after receipt of a syntactically invalid PDU. 5 Tes

22、t Purposes (TP) 5.1 Introduction 5.1.1 TP definition conventions The TPs are defined following particular rules as shown in table 2. Table 2: TP definition rules Title Reference Initial condition TP Id according to the TP naming conventions Stimulus and Expected behaviour. TP Id The TP Id is a uniqu

23、e identifier. It shall be specified according to the TP naming conventions defined in the sub-clause below. Title Short description of test purpose objective. Reference The reference should contain the references of the subject to be validated by the actual TP (specification reference, clause, and p

24、aragraph). PICS selection PICS conformance statements are evaluated in a Boolean expression. If the result of the expression is TRUE, the test shall be performed. A references table cell is TRUE in case the related protocol feature is declared to be implemented. TC reference Shows the reference numb

25、er of the related Test Case in the ATS. Initial condition The condition defines in which initial state the IUT has to be to apply the actual TP. Stimulus and Expected Behaviour Definition of the events the tester performs, and the events that are expected from the IUT to conform to the base specific

26、ation. 5.1.2 TP naming conventions The identifier of the TP is built according to table 3. Table 3: TP naming convention Identifier: TP/- AL-T Application Layer - T-Kernel AL-I Application Layer - I-Kernel = type of SUT OBU On Board Unit RSU Road Side Unit x = Type of testing BV Valid Behaviour Test

27、s BI Invalid Behaviour Tests = sequential number (01-99) Test Purpose Number ETSI ETSI TS 102 486-2-2 V1.1.1 (2006-08)8 5.1.3 Sources of TP definitions All TPs are specified according to EN 12834 1. 5.2 Application T-kernel test purposes for On Board Unit (OBU) 5.2.1 BV Test Purposes Test subgroup o

28、bjective: To test the behaviour of the IUT in relation to syntactically and contextual correct behaviour of the test system. Test purposes: Verify that the OBU can receive GET.request and manage GET.response, with LID = private Reference: EN 12834 1 clause 6.2 and annex A PICS selection: Table A.1/1

29、 AND Table E.2/11 AND Table E.3/9 TC reference: TC_AL_T_OBU_BV_01 Initial condition: OBU already initialized, waiting to be served by tester. TP/AL-T/OBU/BV/01 Stimulus and Expected Behaviour: 1. Tester sends GET.request with FlowControl = 7, requesting retrieval of data available in the IUT without

30、 late response. 2. Verify IUT provides the data requested in step 1 in a GET-Response with proper ReturnStatus. Verify that the OBU can receive SET.request with mode = 1 and manage SET.response, with LID = private Reference: EN 12834 1 clause 6.2 and annex A PICS Selection: Table A.1/1 AND Table E.2

31、/12 AND Table E.3/10 TC reference: TC_AL_T_OBU_BV_02 Initial condition: OBU already initialized, waiting to be served by tester. TP/AL-T/OBU/BV/02 Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode = 1 and FlowControl = 7, requesting storage of data = DATA in the IUT. 2. Verify p

32、roper ReturnStatus indicated in the SET-Response. Verify that the OBU can receive SET.request with mode = 1 and GET.request, and manage SET.response and GET.response, with LID = private Reference: EN 12834 1 clause 6.2 and annex A PICS Selection: Table A.1/1 AND Table E.2/11 AND Table E.2/12 AND Tab

33、le E.3/9 AND Table E.3/10 TC reference: TC_AL_T_OBU_BV_03 Initial condition: OBU already initialized, waiting to be served by tester. TP/AL-T/OBU/BV/03 Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode = 1 and FlowControl = 7, requesting storage of data = DATA1 in the attribute

34、given by EID = EID1 and attributeId = attributeID1 in the IUT. 2. Verify proper ReturnStatus indicated in the SET-Response. 3. Tester sends GET.request in order to retrieve the data sent in step 1. 4. Verify proper ReturnStatus indicated in the GET-Response. 5. Verify that the data retrieved in step

35、 3 is identical to the data sent in step 1. 6. Tester sends SET.request with mode = 1 and FlowControl = 7, requesting storage of data = DATA2 in the attribute given by EID = EID1 and attributeId = attributeID1 in the IUT. 7. Verify proper ReturnStatus indicated in the SET-Response. 8. Tester sends G

36、ET.request in order to retrieve the data sent in step 6. 9. Verify proper ReturnStatus indicated in the GET-Response. 10. Verify that the data retrieved in step 8 is identical to the data sent in step 6. ETSI ETSI TS 102 486-2-2 V1.1.1 (2006-08)9 Verify that the OBU can receive SET.request with mode

37、 = 0 and GET.request and GET.response, with LID = private Reference: EN 12834 1 clause 6.2 and annex A PICS Selection: Table A.1/1 AND Table E.2/9 AND Table E.2/11 AND Table E.3/6 AND Table E.3/10 TC reference: TC_AL_T_OBU_BV_04 Initial condition: OBU already initialized, waiting to be served by tes

38、ter. TP/AL-T/OBU/BV/04 Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode = 0 and FlowControl = 4, requesting storage of DATA1 in the attribute given by EID = EID1 and attributeId = attributeID1 of the IUT. 2. Verify proper operation of IUT by retrieval of EID = EID1, attributeId

39、 = attributeID1 using GET.request. 3. Tester sends SET.request with mode = 0 and FlowControl = 4, requesting storage of DATA2 in the attribute given by EID = EID1 and attributeId = attributeID1 in the IUT. 4. Verify proper operation of IUT by retrieval of EID = EID1, attributeId = attributeID1 using

40、 GET.request. Verify that the OBU can receive SET.request with mode = 0 and GET.request and GET.response, with LID = private Reference: EN 12834 1 clause 6.2 and annex A PICS Selection: Table A.1/1 AND Table E.3/6 AND Table E.2/11 AND Table E.3/9 TC reference: TC_AL_T_OBU_BV_05 Initial condition: OB

41、U already initialized, waiting to be served by tester. TP/AL-T/OBU/BV/05 Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode = 0 and FlowControl = 1, requesting storage of DATA1 in the data element given by EID = EID1 and attributeId = attributeID1 of the IUT. 2. Verify proper ope

42、ration of IUT by retrieval of EID = EID1, attributeId = attributeID1 using GET.request. 3. Tester sends SET.request with mode = 0 and FlowControl = 1, requesting storage of DATA2 in the data element given by EID = EID1 and attributeId = attributeID1 in the IUT. 4. Verify proper operation of IUT by r

43、etrieval of EID = EID1, attributeId = attributeID1 using GET.request. Verify that the OBU can receive SET.request with mode = 0 and with LID = broadcast after initialization,and GET.request and manage GET.response, with private LID Reference: EN 12834 1 clause 6.2 and annex A PICS Selection: Table A

44、.1/1 AND Table E.3/4 AND Table E.2/11 AND Table E.3/9 TC reference: TC_AL_T_OBU_BV_06 Initial condition: OBU already initialized, waiting to be served by tester. TP/AL-T/OBU/BV/06 Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode = 0, FlowControl = 1 and LID = broadcast, request

45、ing storage of data = DATA1 in the IUT. 2. Tester sends GET.request in order to retrieve the data sent in step 1. 3. Verify that the data retrieved in step 2 is identical to the data sent in step 1. 4. Tester sends SET.request with mode = 0 and FlowControl = 1 and LID = broadcast, requesting storage

46、 of data = DATA2 in the IUT. 5. Tester sends GET.request in order to retrieve the data sent in step 4. 6. Verify that the data retrieved in step 5 is identical to the data sent in step 4. ETSI ETSI TS 102 486-2-2 V1.1.1 (2006-08)10Verify that the OBU can receive SET.request with mode = 0 and with LI

47、D = broadcast without initialization, and GET.request and manage GET.response, with private LID Reference: EN 12834 1 clause 6.2 and annex A PICS Selection: Table A.1/1 AND Table E.3/4 AND Table E.2/11 AND Table E.3/9 TC reference: TC_AL_T_OBU_BV_07 Initial condition: OBU not in sleep mode and not y

48、et initialized. TP/AL-T/OBU/BV/07 Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode = 0, FlowControl = 1 and LID = broadcast, requesting storage of data = DATA1 in the IUT. 2. Perform initialization with the IUT. 3. Tester sends GET.request in order to retrieve the data sent in

49、step 1. 4. Verify that the data retrieved in step 2 is identical to the data sent in step 1. 5. Tester sends RELEASE command. 6. Tester immediately, i.e. before beacon time-out, sends SET.request with mode = 0, FlowControl = 1 and LID = broadcast, requesting storage of data = DATA2 in the IUT. 7. Repeat step 2 after beacon time-out. 8. Tester sends GET.request in order to retrieve the data sent in step 6. 9. Verify that the data retrieved in step 8 is identical to the data sent in step 6. Verify that the OBU can recei