1、 ETSI TS 102 486-2-2 V1.2.1 (2008-10)Technical Specification Intelligent Transport Systems (ITS);Road Transport and Traffic Telematics (RTTT);Test specifications for Dedicated Short Range Communication (DSRC) transmission equipment;Part 2: DSRC application layer;Sub-Part 2: Test Suite Structure and
2、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 Policy, no investigation, incl
3、uding 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 Technical Specification (TS) h
4、as been produced by ETSI Technical Committee Intelligent Transport System(ITS). The present document is part 2, sub-part 2 of a multi-part deliverable covering Intelligent Transport Systems (ITS); Road Transport and Traffic Telematics (RTTT); Test specifications for Dedicated ShortRange Communicatio
5、n (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 Structure and Test Purpose
6、s (TSS Sub-part 3: “Abstract Test Suite (ATS) and partial PIXIT proforma“. ETSI ETSI TS 102 486-2-2 V1.2.1 (2008-10)51 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the Dedicated Short Range Communication (DSRC); Application layer. The objective of
7、 this test specification 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-2 6) as well as the ETSI ru
8、les for conformance testing (ETS 300 406 4) are used as a basis for the test methodology. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific
9、 reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which
10、 are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited,
11、in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lo
12、wer case letters. 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 indispensable for the application of the present document. For dated references,
13、only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 CEN EN 12834 (2003): “Road transport and traffic telematics - Dedicated Short Range Communication (DSRC) - DSRC application layer“. 2 CEN EN 12253 (2003):
14、Road transport and traffic telematics - Dedicated short-range communication - Physical layer using 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 Spe
15、cification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 5 ISO/IEC 9646-1 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. ETSI ETSI TS 102 486-2-2 V1.2.1 (2008-
16、10)66 ISO/IEC 9646-2 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 7 ISO/IEC 9646-6 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and fram
17、ework - Part 6: Protocol profile test specification“. 8 ISO/IEC 9646-7 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statement“. 2.2 Informative references The following referenced documents are not
18、 essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. 3 Definitions and abbreviations 3.1 Definitions For the purp
19、oses 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. 3.2 Abbreviations 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 and EN 12834 1 and the following
20、 apply: PrWRq MAC frame Private Window Request 4 Test Suite Structure (TSS) 4.1 Structure Figure 1 shows the Application Test Suite Structure (TSS) including its subgroups defined for the conformance testing. Group Type of SUT behaviour Application Layer - T-Kernel On Board Unit Valid behaviour Inva
21、lid behaviourRoad Side Unit Valid behaviour Invalid behaviourApplication Layer - I-Kernel On Board Unit Valid behaviour Invalid behaviourRoad Side Unit Valid behaviour Invalid behaviourFigure 1: TSS for DSRC Application 4.2 Test groups The test groups are organized in three groups. The first is desi
22、gned 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. ETSI ETSI TS 102 486-2-2 V1.2.1 (2008-10)74.3 Type of SUT test groups The type of SUT test groups are organized in two groups. The first is d
23、esigned for the On Board Unit testing and the second is designed for Road Side Unit testing. 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 Data Units (PDUs). Val
24、id 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 Test Purposes (TP) 5.1 Int
25、roduction 5.1.1 TP definition conventions The TPs are defined following particular rules as shown in table 1. Table 1: TP definition rules TP Id according to the TP naming conventions Title Reference PICS selection TC reference Initial condition Stimulus and Expected Behaviour TP Id The TP Id is a u
26、nique identifier. It shall be specified according to the TP naming conventions defined in the 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, parag
27、raph). PICS selection Reference to the PICS statement involved for selection of the TP. Contains a Boolean expression. Only those PICS statements are shown that are explicitly related to the test. TC reference Shows the reference number of the related Test Case in the ATS. Initial condition The cond
28、ition 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 specification. 5.1.2 TP naming conventions The identifier of the TP is bui
29、lt according to table 2. ETSI ETSI TS 102 486-2-2 V1.2.1 (2008-10)8Table 2: 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 Tests BI Invalid Behaviour T
30、ests = sequential number (01-99) Test Purpose Number 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 5.2.1 BV test purposes Test subgroup objective: - to test the behaviour of the IUT in relation to syntactically
31、 and contextual correct behaviour of the test system. Test purposes: TP/AL-T/OBU/BV/01 Verify that the OBU can receive GET.request and manage GET.response, with LID=private Reference: EN 12834 1 clauses 6.2 and Annex A PICS selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.11/5 AND
32、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. Stimulus and Expected Behaviour: 1. Tester sends GET.request with FlowControl=7, requesting retrieval of data available in the IUT without late response. 2. Verify
33、 IUT provides the data requested in step 1 in a GET-Response with proper ReturnStatus. TP/AL-T/OBU/BV/02 Verify that the OBU can receive SET.request with mode=1 and manage SET.response, with LID=private Reference: EN 12834 1 clauses 6.2 and Annex A PICS Selection: Table A.1/1 AND Table A.8/3 AND Tab
34、le A.8/4 AND Table A.15/4 AND Table E.2/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. Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode=1 and FlowControl=7, requesting storage of data=DATA in the I
35、UT. 2. Verify proper ReturnStatus indicated in the SET-Response. ETSI ETSI TS 102 486-2-2 V1.2.1 (2008-10)9TP/AL-T/OBU/BV/03 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 clauses 6.2 and Annex
36、 A PICS Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3 AND Table A.8/4 AND Table A.11/5 AND Table A.15/4 AND Table E.2/11 AND Table E.2/12 AND Table 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 test
37、er. Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode=1 and FlowControl=7, requesting storage of data=DATA1 in the attribute 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 ord
38、er 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 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
39、 by EID=EID1 and attributeId=attributeID1 in the IUT. 7. Verify proper ReturnStatus indicated in the SET-Response. 8. Tester sends GET.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 id
40、entical to the data sent in step 6. TP/AL-T/OBU/BV/04 Verify that the OBU can receive SET.request with mode=0 and GET.request and GET.response, with LID=private Reference: EN 12834 1 clauses 6.2 and Annex A PICS Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3 AND Table E.2/9 A
41、ND 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 tester. Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode=0 and FlowControl=4, requesting storage of DATA1 in the attribute given
42、by EID=EID1 and attributeId=attributeID1 of the IUT. 2. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=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=attri
43、buteID1 in the IUT. 4. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=attributeID1 using GET.request. TP/AL-T/OBU/BV/05 Verify that the OBU can receive SET.request with mode=0 and GET.request and GET.response, with LID=private Reference: EN 12834 1 clauses 6.2 and Annex A PICS
44、Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3 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: OBU already initialized, waiting to be served by tester. Stimulus and Expected Behaviour: 1. Tester sends SET.request with mode=0
45、 and FlowControl=1, requesting storage of DATA1 in the data element given by EID=EID1 and attributeId=attributeID1 of the IUT. 2. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=attributeID1 using GET.request. 3. Tester sends SET.request with mode=0 and FlowControl=1, requesting
46、 storage of DATA2 in the data element given by EID=EID1 and attributeId=attributeID1 in the IUT. 4. Verify proper operation of IUT by retrieval of EID=EID1, attributeId=attributeID1 using GET.request. ETSI ETSI TS 102 486-2-2 V1.2.1 (2008-10)10TP/AL-T/OBU/BV/06 Verify that the OBU can receive SET.re
47、quest with mode=0 and with LID=broadcast after initialization,and GET.request and manage GET.response, with private LID Reference: EN 12834 1 clauses 6.2 and Annex A PICS Selection: Table A.1/1 AND Table A.8/1 AND Table A.8/2 AND Table A.8/3 AND Table E.3/4 AND Table E.2/11 AND Table E.3/9 TC refere
48、nce: TC_AL_T_OBU_BV_06 Initial condition: OBU already initialized, waiting to be served by tester. 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. Tester sends GET.request in order to retrieve
49、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 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. TP/AL-T/OBU/BV/07 Verify that the OBU can receive SET.request with mode=0 and with LID=broadcast without initialization, and GET.request and manage
