1、 ETSI TS 102 870-3 V1.1.1 (2011-03)Technical Specification Intelligent Transport Systems (ITS);Testing;Conformance test specifications for GeonetworkingBasic Transport Protocol (BTP);Part 3: Abstract Test Suite (ATS) and Protocol ImplementationeXtra Information for Testing (PIXIT)floppy3ETSI ETSI TS
2、 102 870-3 V1.1.1 (2011-03)2Reference DTS/ITS-0030010 Keywords ATS, ITS, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis 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 Grass
3、e (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the re
4、ference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the 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 c
5、hange of status. Information on the current status 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: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyri
6、ght Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo an
7、d the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP O
8、rganizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definition
9、s and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Abstract Test Method (ATM) . 7g34.1 Abstract protocol tester 7g34.2 Test Configuration 8g34.3 Test architecture . 8g34.4 Ports and ASPs (Abstract Services Primitives) 9g34.4.1 Primitives of the btpPort . 9g34.4.2 Primitives of the
10、utPort . 9g35 Untestable Test Purposes 10g36 ATS conventions 10g36.1 Testing conventions 10g36.1.1 Testing states 10g36.1.1.1 Initial state . 10g36.1.1.2 Final state 10g36.2 Naming conventions . 10g36.2.1 General guidelines 10g36.2.2 ITS specific TTCN-3 naming conventions . 11g36.2.3 Usage of Log st
11、atements . 12g36.2.4 Test Case (TC) identifier 12g36.3 On line documentation . 13g3Annex A (normative): TTCN-3 library modules . 14g3A.1 Electronic annex, zip file with TTCN-3 code 14g3A.2 Electronic annex, zip file with HTML documentation . 14g3Annex B (normative): Partial PIXIT proforma for BTP .
12、15g3B.1 Identification summary. 15g3B.2 ATS summary 15g3B.3 Test laboratory 15g3B.4 Client identification 16g3B.5 SUT 16g3B.6 Protocol layer information 16g3B.6.1 Protocol identification 16g3B.6.2 IUT information . 17g3Annex C (normative): PCTR Proforma for BTP 18g3C.1 Identification summary. 18g3C.
13、1.1 Protocol conformance test report 18g3C.1.2 IUT identification . 18g3ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)4C.1.3 Testing environment . 18g3C.1.4 Limits and reservation 19g3C.1.5 Comments. 19g3C.2 IUT Conformance status 19g3C.3 Static conformance summary . 19g3C.4 Dynamic conformance summary 20g
14、3C.5 Static conformance review report . 20g3C.6 Test campaign report 21g3C.7 Observations . 21g3Annex D (informative): Bibliography . 22g3History 23g3ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)5Intellectual Property Rights IPRs essential or potentially essential to the present document may have been dec
15、lared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members 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“, whic
16、h 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, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
17、 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 System (ITS). The present document is part 3 o
18、f a multi-part deliverable covering Conformance test specification for Geonetworking Basic Transport Protocol (BTP) as identified below: Part 1: “Test requirements and Protocol Implementation Conformance Statement (PICS) proforma“; Part 2: “ Test Suite Structure and Test Purposes (TSS Part 3: “Abstr
19、act Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)“. The development of ITS test specifications follows the guidance provided in the EG 202 798 i.1. Therefore this ATS documentation is also based on the guidance provided in EG 202 798 i.1. ETSI ETSI TS 102 870-3 V
20、1.1.1 (2011-03)61 Scope The present document contains the Abstract Test Suite (ATS) for Geonetworking Basic Transport Protocol (BTP) as defined in TS 102 636-5-1 1 in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 5. The objective of th
21、e present document is to provide a basis for conformance tests for Geonetworking Basic Transport Protocol (BTP) 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 2 and ISO/IE
22、C 9646-2 3) as well as the ETSI rules for conformance testing (ETS 300 406 6) 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 specific references, only the cited
23、 version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 2.1 Normative references The
24、following referenced documents are necessary for the application of the present document. 1 ETSI TS 102 636-5-1 (V1.1.1): “Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 5: Transport Protocols; Sub-part 1: Basic Transport Protocol“. 2 ISO/IEC 9646-1 (1994): “Infor
25、mation technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 3 ISO/IEC 9646-2 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“.
26、4 ISO/IEC 9646-6 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. 5 ISO/IEC 9646-7 (1995): “Information technology - Open Systems Interconnection - Conformance testing methodology and framew
27、ork - Part 7: Implementation Conformance Statements“. 6 ETSI ETS 300 406 (1995): “Methods for testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 7 ETSI ES 201 873-1: “Methods for Testing and Specification (MTS); The Testing and Tes
28、t Control Notation version 3; Part 1: TTCN-3 Core Language“. 8 ETSI TS 102 870-1: “Intelligent Transport Systems (ITS); Testing; Conformance test specifications for GeoNetworking Basic Transport Protocol (BTP); Part 1: Test requirements and Protocol Implementation Conformance Statement (PICS) profor
29、ma“. 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 particular subject area. i.1 ETSI EG 202 798: “Intelligent Transport Systems (ITS); Testing; Framework for conformance and intero
30、perability testing“. ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)73 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 102 636-5-1 1 , ISO/IEC 9646-1 2 and in ISO/IEC 9646-7 5 apply. 3.2 Abbreviations For the purposes of the prese
31、nt document, the following abbreviations apply: ATM Abstract Test Metho ATS Abstract Test Suite BTP Basic Transport Protocols CAN Controller Area Network ITS Intelligent Transportation Systems IUT Implementation Under Test MTC Main Test Component PIXIT Partial Protocol Implementation Extra Informati
32、on for Testing SCS System Conformance Statement SUT System Under Test TC Test Case TP Test PurposesTTCN Tree and Tabular Combined Notation V2I Vehicle-to-Infrastructure V2V Vehicle-to-Vehicle 4 Abstract Test Method (ATM) This clause describes the ATM used to test the Basic Transport Protocol (BTP).
33、4.1 Abstract protocol tester The abstract protocol tester used by this test suite is described in figure 1. The test system will simulate valid and invalid protocol behaviour, and will analyse the reaction of the IUT. ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)8SUT Test System ITS-G5 IUT BTP ITS-G5 Lowe
34、r tester PDUs Upper Tester GeoN GeoN Figure 1: Abstract protocol tester - BTP 4.2 Test Configuration This test suite uses a unique test configuration in order to cover the different test scenarios. In this configuration, the tester simulates one ITS station implementing the BTP protocol. 4.3 Test ar
35、chitecture This test specification implements the general TTCN-3 test architecture described in EG 202 798 i.1, clauses 6.3.2 and 8.3.1. Figure 2 shows the test architecture used in for the BTP ATS. The BTP test component requires using only the Main Test Component (MTC). The MTC communicates with t
36、he BTP SUT over the btpPort. The btpPort port is used to exchange BTP protocol messages between the BTP test component and the BTP IUT. The Upper tester entity in the SUT enables triggering BTP functionalities by simulating primitives from application or LDM entities. It is required to trigger the B
37、TP layer in the SUT to send BTP messages, which are resulting from upper layer primitives. Furthermore, receiving BTP messages may result for the BTP layer in sending primitives to the upper layer (sending Data to Facilities Layers for instance). ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)9ITS TTCN-3 te
38、st execution ItsNt (MTC) ITS lower layers stack Upper tester transport ITS Test Adaptor SUT Adpt_CtlrcontrolportUTportcontrolportNT External functions CODECS System adaptor (SA) Platform adaptor (PA) NT1 SUT Group of TTCN -3 ports TTCN-3 ports TTCN-3 external functions BtpPortFigure 2: test system a
39、rchitecture 4.4 Ports and ASPs (Abstract Services Primitives) Two ports are used by the BTP ATS: The btpPort, of type BtpPort The utPort of type UpperTesterPort 4.4.1 Primitives of the btpPort Two types of primitives are used in the btpPort: The BtpInd primitive used to receive messages of type BtpP
40、du The BtpReq primitive used to send messages of type BtpPdu 4.4.2 Primitives of the utPort This port uses two types of primitives: The UtInitialize primitive used to initialise IUT The UtTrigger primitive used trigger upper layer events in IUT ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)105 Untestable T
41、est Purposes This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or other restrictions. Table 1: Untestable TP Test purpose Reason None 6 ATS conventions The ATS conventions are intended to give a better understanding of the ATS but they also describe the conve
42、ntions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions and the naming conventions. The testing conventions describe the functional structure of
43、the ATS. The naming conventions describe the structure of the naming of all ATS elements. To define the ATS, the guidelines of the document ETS 300 406 6 was considered. 6.1 Testing conventions 6.1.1 Testing states 6.1.1.1 Initial state All test cases start with the function f_prInitialState. This f
44、unction brings the IUT in an “initialized“ state by invoking the upper tester primitive UtInitialize. 6.1.1.2 Final state All test cases end with the function f_poDefault. This function brings the IUT back in an “idle“ state. As no specific actions are required for the idle state in the base standar
45、d, the function f_ poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. 6.2 Naming conventions This test suite follows the naming convention guidelines provided in the EG 202 798 i.1. 6.2.1 General guidelines The naming convention is based
46、on the following underlying principles: in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 2) indicating the type of TTCN-3 element it represents; suffixes should not be used except in those specific cases identified in table 7; prefixes and suffixes sho
47、uld be separated from the body of the identifier with an underscore (“_“); EXAMPLE 1: c_sixteen, t_wait. only module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-c
48、ase letter; ETSI ETSI TS 102 870-3 V1.1.1 (2011-03)11 the start of second and subsequent words in an identifier should be indicated by capitalizing the first character. Underscores should not be used for this purpose. EXAMPLE 2: f_initialState. Table 2 specifies the naming guidelines for each elemen
49、t of the TTCN-3 language indicating the recommended prefix, suffixes (if any) and capitalization. Table 2: ETSI TTCN-3 generic naming conventions Language element Naming convention Prefix Example identifier Module Use upper-case initial letter none IPv6Templates Group within a module Use lower-case initial letter none messageGroup Data type Use upper-case initial letter none SetupContents Message template Use lower-case initial letter m_ m_setupInit Message template with wildcard or matching expression Use lowe
