1、 ETSI TR 103 099 V1.3.1 (2015-07) Intelligent Transport Systems (ITS); Architecture of conformance validation framework TECHNICAL REPORT ETSI ETSI TR 103 099 V1.3.1 (2015-07) 2 Reference RTR/ITS-00346 Keywords architecture, conformance, ITS, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipol
2、is Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present docu
3、ment may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/
4、or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current st
5、atus of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reprod
6、uced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction
7、 extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Me
8、mbers and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 103 099 V1.3.1 (2015-07) 3 Contents Intellectual Property Rights 6g3Foreword . 6g3Modal verbs terminology 6g3Introduction 6g31 Scope 7g32 References 7g32.1 No
9、rmative references . 7g32.2 Informative references 7g33 Abbreviations . 8g34 Test platform overview 9g34.1 Constraints and requirements . 9g34.2 General architecture . 9g35 Hardware equipment 10g35.1 PC . 10g35.2 G5 adapter box . 11g36 Codecs 11g36.1 Introduction 11g36.2 Advanced details of implemen
10、tation 11g37 Test Adapter . 13g37.1 Introduction 13g37.2 Lower Tester 14g37.2.1 Overview 14g37.2.2 Advanced details of implementation 16g37.2.3 Extensibility of the test adapter. 18g37.2.4 Adapter Control primitives . 18g37.2.5 Adapter configuration parameters . 18g37.3 Platform Adapter 20g37.4 Uppe
11、r Tester . 20g3Annex A: Codecs Source Code 22g3Annex B: Test Adapter Source Code . 23g3Annex C: Upper Tester Message Format. 24g3C.1 Introduction 24g3C.2 Common Upper Tester Primitives 24g3C.2.1 UtInitialize 24g3C.2.2 ChangePosition . 25g3C.2.3 ChangePseudonym . 26g3C.3 CAM Upper Tester Primitives .
12、 26g3C.3.1 ChangeCurvature 26g3C.3.2 ChangeSpeed 27g3C.3.3 SetAccelerationControlStatus. 27g3C.3.4 SetExteriorLightsStatus 29g3C.3.5 ChangeHeading 29g3C.3.6 SetDriveDirection . 30g3C.3.7 ChangeYawRate . 30g3C.3.8 CamEventIndication . 31g3C.3.9 SetStationType . 31g3C.3.10 SetVehicleRole . 32g3C.3.11
13、SetEmbarkationStatus 32g3ETSI ETSI TR 103 099 V1.3.1 (2015-07) 4 C.3.12 SetPtActivation . 33g3C.3.13 SetDangerousGoods . 33g3C.3.14 SetLightBarSiren 34g3C.4 DENM Upper Tester Primitives . 35g3C.4.1 GenerateDenmEvent 35g3C.4.2 UpdateDenmEvent . 37g3C.4.3 TerminateDenmEvent 38g3C.4.4 DenmEventIndicati
14、on . 38g3C.5 GeoNetworking Upper Tester Primitives . 39g3C.5.1 GenerateGeoUnicast . 39g3C.5.2 GenerateGeoBroadcast . 39g3C.5.3 GenerateGeoAnycast 40g3C.5.4 GenerateSHB 41g3C.5.5 GenerateTSB 41g3C.5.6 GnEventIndication 42g3C.6 IPv6OverGeoNetworking Upper Tester Primitives . 42g3C.6.1 SendIPv6Message
15、42g3C.6.2 GetInterfaceInfos 43g3C.6.3 Gn6EventIndication 43g3C.7 BTP Upper Tester Primitives . 44g3C.7.1 GenerateBtpA . 44g3C.7.2 GenerateBtpB . 44g3C.7.3 BtpEventIndication . 45g3C.8 MAP SPAT Upper Tester Primitives . 45g3C.8.1 UtMapSpatTrigger 45g3C.8.2 UtMapEventInd 46g3C.8.3 UtSpatEventInd 46g3A
16、nnex D: Example of Test Platform implementation . 47g3Annex E: Complete Test Adapter class diagram 52g3Annex F: Bibliography 53g3History 54g3ETSI ETSI TR 103 099 V1.3.1 (2015-07) 5 List of figures Figure 1: General architecture .10g3Figure 2: Communication via G5 adaptation box .11g3Figure 3: Commun
17、ication via Ethernet .11g3Figure 4: Codec class diagram 13g3Figure 5: Message sending sequence diagram 15g3Figure 6: Message reception sequence diagram 15g3Figure 7: Test Adapter class diagram 16g3Figure 8: Port initialization sequence diagram 17g3Figure 9: Upper Tester architecture .21g3Figure E.1:
18、 Test adapter complete class diagram 52g3ETSI ETSI TR 103 099 V1.3.1 (2015-07) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI mem
19、bers and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); 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:/ipr.etsi
20、.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 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
21、present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Intelligent Transport Systems (ITS). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be i
22、nterpreted 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. Introduction In response to EC mandate M/453 i.10, ETSI Technical Committee (TC) ITS has s
23、tandardized base and test specifications for ITS protocols. In a next step a prototype TTCN-3 test system was built and validated. The present document describes the design and validation of the prototype TTCN-3 test system. The action described in the present document has supported the implementati
24、on of ITS standards by: Making available validated and standardized test specifications and thus enabling the application of reliable certification schemes. Executing conformance validation framework against real Implementations Under Test (IUTs) from industry and thus providing these companies a co
25、nformance assessment of their implementations. During the lifetime of this action, the conformance validation framework was as well provided at ITS Cooperative Mobility Services Interoperability events. Releasing all software as open source and thus allowing industry to build and run their own confo
26、rmance validation framework. ETSI ETSI TR 103 099 V1.3.1 (2015-07) 7 1 Scope The present document provides a description of the architecture of the ITS conformance validation framework, including definition of the test environment, codec and test adapter. It provides, as well, all the necessary sour
27、ce code to build and run the ITS conformance validation framework. The ITS conformance validation framework integrates the test suites ETSI TS 102 871-3 i.4, ETSI TS 102 868-3 i.5, ETSI TS 102 869-3 i.6, ETSI TS 102 870-3 i.7, ETSI TS 102 859-3 i.8 and ETSI TS 103 191-3 i.9. 2 References 2.1 Normati
28、ve references References are either specific (identified by date of publication and/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 reference document (including any amendments) appl
29、ies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.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. The following r
30、eferenced documents are necessary for the application of the present document. Not applicable. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applie
31、s. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necess
32、ary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI ES 201 873-5 (V4.5.1): “Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 5: TTCN-3 Runtime Interface (TRI)“. i.2 ETSI EG 201 0
33、15 (V2.1.1): “Methods for Testing and Specification (MTS); Standards engineering process; A handbook of validation methods“. i.3 IEEE 802.11p: “IEEE Standard for Local and Metropolitan Area Networks - Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) S
34、pecifications; Amendment 6: Wireless Access in Vehicular Environments“. i.4 ETSI TS 102 871-3 (V.1.3.1): “Intelligent Transport Systems (ITS); Testing; Conformance test specifications for GeoNetworking ITS-G5; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testin
35、g (PIXIT)“. i.5 ETSI TS 102 868-3 (V.1.3.1): “Intelligent Transport Systems (ITS); Testing; Conformance test specifications for Cooperative Awareness Basic Service (CA); Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)“. i.6 ETSI TS 102 869-3 (V.1.4
36、.1): “Intelligent Transport Systems (ITS); Testing; Conformance test specifications for Decentralized Environmental Notification Basic Service (DEN); Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)“. ETSI ETSI TR 103 099 V1.3.1 (2015-07) 8 i.7 ETSI
37、 TS 102 870-3 (V.1.1.1): “Intelligent Transport Systems (ITS); Testing; Conformance test specifications for Geonetworking Basic Transport Protocol (BTP); Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)“. i.8 ETSI TS 102 859-3 (V.1.2.1): “Intelligen
38、t Transport Systems (ITS); Testing; Conformance test specifications for Transmission of IP packets over Geonetworking; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)“. i.9 ETSI TS 103 191-3 (V.1.1.1): “Intelligent Transport Systems (ITS); Testing;
39、 Conformance test specifications for Signal Phase And Timing (SPAT) and Map (MAP); Part 3: Abstract Test Suite (ATS) and Implementation eXtra Information for Testing (IXIT)“. i.10 EC mandate M/453: “Standardisation mandate addressed to CEN, CENELEC and ETSI in the field of Information and Communicat
40、ion Technologies to support the interoperability of co-operative systems for Intelligent Transport in the European Community“. 3 Abbreviations For the purposes of the present document, the following abbreviations apply: AC Adapter Control ACC Adaptive Cruise Control API Application Programming Inter
41、face ASN Abstract Syntax Notation AT Authorization TicketATS Abstract Test Suite BTP Basic Transport Protocol BTP-A Basic Transport Protocol - Type A BTP-B Basic Transport Protocol - Type B CAM Cooperative Awareness Message CC Cruise Control DENM Decentralized Environmental Notification Message EC E
42、uropean Commission ETH ETHernet GN GeoNetworking HB High BeamIP Internet Protocol ITS Intelligent Transportation Systems ITS-S Intelligent Transportation Systems - Station IUT Implementation Under Test JDK Java Development Kit LB Low Beam LS Location Service LT Left Turn MAC Media Access Control MAP
43、 MapData MTC Main Test Component OS Operating SystemOSI Open Systems Interconnection model PC Personal Computer Pcap Packet capture PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement RT Right Turn SHB Single Hop Broadcast SPAT Signal Phase And Timing SUT System Under Test TA T
44、est Adapter TC Test CasesTCI TTCN-3 Control Interface TP Test Purposes ETSI ETSI TR 103 099 V1.3.1 (2015-07) 9 TRI TTCN-3 Runtime Interface TSB Topology Scoped Broadcast TTCN-3 Testing and Test Control Notation 3 UDP User Datagram Protocol UT Upper Tester XP Windows XP operating system 4 Test platfo
45、rm overview 4.1 Constraints and requirements The purpose of the ITS test platform is to provide a reliable set of software and hardware equipments that can be used to validate TTCN-3 abstract test suites (ATS) developed in ETSI. The architecture of this test platform has been designed with respect t
46、o the following constraints: to be compatible with the requirements expressed in the validation handbook (ETSI EG 201 015 i.2); to be independent of the platform used to implement the test system; to be independent of the TTCN-3 tool provider; to be configurable and customizable; to provide tools an
47、d well defined interfaces to system under test (SUT), allowing test automation; to be easily extensible for future ITS protocols; to provide generic components that can be reused in other test platforms. In order to ensure independence of hardware platforms, all software pieces running on the test p
48、latform have been implemented using Java language, using generic and widely used libraries. Test tool independence has been achieved by isolating the tool specific interfaces from core functionalities of the platform. Adapting the current platform to a different test tool would only require the impl
49、ementation of a very simple piece of software mapping tool-specific functions to generic functions defined in this project. In addition, great care has been taken to separate ITS specific functionalities from generic test platform tasks in order to provide a maximum number of reusable components for future test platforms. 4.2 General architecture Typically a TTCN-3 test platform is composed of four different components: The TTCN-3 test tool providing necessary software to execute the abstract test suites. The har
