ETSI TS 102 870-3 V1.1.1 (2011-03)

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)

DTS/ITS-0030010

General Information

• Status: Published
• Publication Date: 22-Mar-2011
• Technical Committee: ITS WG3 - Transport and Network
• Current Stage: 12 - Completion
• Due Date: 30-Mar-2011
• Completion Date: 23-Mar-2011
• Mandate: M/453

Standards Content (Sample)

Technical Specification
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)

�
2 ETSI TS 102 870-3 V1.1.1 (2011-03)

Reference
DTS/ITS-0030010
Keywords
ATS, ITS, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (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 reference 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 change 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
Copyright 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.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP 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 Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 870-3 V1.1.1 (2011-03)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Abstract Test Method (ATM) . 7
4.1 Abstract protocol tester . 7
4.2 Test Configuration . 8
4.3 Test architecture . 8
4.4 Ports and ASPs (Abstract Services Primitives) . 9
4.4.1 Primitives of the btpPort . 9
4.4.2 Primitives of the utPort . 9
5 Untestable Test Purposes. 10
6 ATS conventions . 10
6.1 Testing conventions . 10
6.1.1 Testing states . 10
6.1.1.1 Initial state . 10
6.1.1.2 Final state . 10
6.2 Naming conventions . 10
6.2.1 General guidelines . 10
6.2.2 ITS specific TTCN-3 naming conventions . 11
6.2.3 Usage of Log statements . 12
6.2.4 Test Case (TC) identifier . 12
6.3 On line documentation . 13
Annex A (normative): TTCN-3 library modules . 14
A.1 Electronic annex, zip file with TTCN-3 code . 14
A.2 Electronic annex, zip file with HTML documentation . 14
Annex B (normative): Partial PIXIT proforma for BTP . 15
B.1 Identification summary. 15
B.2 ATS summary . . 15
B.3 Test laboratory . 15
B.4 Client identification . 16
B.5 SUT . 16
B.6 Protocol layer information. 16
B.6.1 Protocol identification . 16
B.6.2 IUT information . 17
Annex C (normative): PCTR Proforma for BTP . 18
C.1 Identification summary. 18
C.1.1 Protocol conformance test report . 18
C.1.2 IUT identification . 18
ETSI
4 ETSI TS 102 870-3 V1.1.1 (2011-03)
C.1.3 Testing environment . 18
C.1.4 Limits and reservation . 19
C.1.5 Comments. 19
C.2 IUT Conformance status . 19
C.3 Static conformance summary . 19
C.4 Dynamic conformance summary . 20
C.5 Static conformance review report . 20
C.6 Test campaign report . 21
C.7 Observations . 21
Annex D (informative): Bibliography . 22
History . 23

ETSI
5 ETSI TS 102 870-3 V1.1.1 (2011-03)
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 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", 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, 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 Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport System (ITS).
The present document is part 3 of 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&TP)";
Part 3: "Abstract 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
6 ETSI TS 102 870-3 V1.1.1 (2011-03)
1 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 the 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 manufacturer's equipment.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [2] and ISO/IEC 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 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 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): "Information 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".
[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 framework - 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 Test 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) proforma".
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
interoperability testing".
ETSI
7 ETSI TS 102 870-3 V1.1.1 (2011-03)
3 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 present 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 Information for Testing
SCS System Conformance Statement
SUT System Under Test
TC Test Case
TP Test Purposes
TTCN 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).
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
8 ETSI TS 102 870-3 V1.1.1 (2011-03)
Test System SUT
Upper Tester
BTP
PDUs
IUT
GeoN GeoN
ITS-G5 ITS-G5
Lower tester
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 architecture
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 the 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 BTP 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
Btp Port
Adpt_Ctlr
control port
UTport
control port
9 ETSI TS 102 870-3 V1.1.1 (2011-03)
ITS TTCN-3 test execution
ItsNt
(MTC)
NT1
NT
CODECS
ITS Test Adaptor
Upper tester
ITS lower layers stack
External
transport
functions
System adaptor
Platform adaptor
(SA)
(PA)
SUT SUT
Group of TTCN-3 ports
TTCN-3 ports TTCN-3 external functions

Figure 2: test system architecture
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 BtpPdu
• 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
10 ETSI TS 102 870-3 V1.1.1 (2011-03)
5 Untestable Test 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 conventions
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 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 function 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 standard, 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 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 should 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
...