ETSI TS 102 859-3 V1.2.1 (2014-04)

Intelligent 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)

RTS/ITS-0030026

General Information

• Status: Published
• Publication Date: 06-Apr-2014
• Technical Committee: ITS WG3 - Transport and Network
• Current Stage: 12 - Completion
• Due Date: 02-May-2014
• Completion Date: 07-Apr-2014

Standards Content (Sample)

ETSI TS 102 859-3 V1.2.1 (2014-04)






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

�

---------------------- Page: 1 ----------------------
2 ETSI TS 102 859-3 V1.2.1 (2014-04)



Reference
RTS/ITS-0030026
Keywords
ATS, IPv6, ITS, network, PIXIT, 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
The present document can be downloaded from:
http://www.etsi.org
The present document 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/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 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 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 extend to reproduction in all media.

© European Telecommunications Standards Institute 2014.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI 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

---------------------- Page: 2 ----------------------
3 ETSI TS 102 859-3 V1.2.1 (2014-04)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Abstract Test Method (ATM) . 8
4.1 Abstract protocol tester . 8
4.2 Test Configuration . 8
4.3 Test Architecture . 9
4.4 Ports and ASPs (Abstract Services Primitives) . 10
4.4.1 Primitives of the geoNetworkingPort . 10
4.4.2 Primitives of the ipv6OverGeoNetworkingPort. 10
4.4.3 Primitives of the utPort . 10
4.4.4 Primitives of the taPort . 10
5 Untestable Test Purposes. 10
6 ATS conventions . 11
6.1 Testing conventions . 11
6.1.1 Testing states . 11
6.1.1.1 Initial state . 11
6.1.1.2 Final state . 11
6.2 Naming conventions . 11
6.2.1 General guidelines . 11
6.2.2 ITS specific TTCN-3 naming conventions . 12
6.2.3 Usage of Log statements . 13
6.2.4 Test Case (TC) identifier . 14
Annex A (normative): TTCN-3 library modules . 15
A.1 Electronic annex, zip file with TTCN-3 code . 15
Annex B (normative): Partial PIXIT proforma for IPV6overGEONET . 16
B.1 Identification summary. 16
B.2 ATS summary . 16
B.3 Test laboratory . 16
B.4 Client identification . 17
B.5 SUT . 17
B.6 Protocol layer information. 17
B.6.1 Protocol identification . 17
B.6.2 IUT information . 18
Annex C (normative): PCTR Proforma for IPv6overGEONET . 19
C.1 Identification summary. 19
C.1.1 Protocol conformance test report . 19
C.1.2 IUT identification . 19
C.1.3 Testing environment . 19
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 859-3 V1.2.1 (2014-04)
C.1.4 Limits and reservation . 20
C.1.5 Comments. 20
C.2 IUT Conformance status . 20
C.3 Static conformance summary . 20
C.4 Dynamic conformance summary . 21
C.5 Static conformance review report . 21
C.6 Test campaign report . 22
C.7 Observations . 22
Annex D (informative): Bibliography . 23
History . 24

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 859-3 V1.2.1 (2014-04)
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://ipr.etsi.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 present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Intelligent Transport Systems
(ITS).
The present document is part 3 of a multi-part deliverable covering Conformance test specifications for Transmission of
IP packets over GeoNetworking 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)".
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 102 859-3 V1.2.1 (2014-04)
1 Scope
The present document contains the Abstract Test Suite (ATS) for Transmission of IP packets over GeoNetworking as
defined in EN 302 636-6-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 Transmission of IP packets over
GeoNetworking equipment giving a high probability of interoperability between different manufacturers' 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.
Annex A provides the Tree and Tabular Combined Notation (TTCN) part of the ATS.
Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the ATS.
Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of the ATS.
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
reference 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.
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 necessary for the application of the present document.
[1] ETSI EN 302 636-6-1 (V1.2.0): "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 6: Internet Integration; Sub-part 1: Transmission of IPv6 Packets over
GeoNetworking Protocols".
[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 (V4.5.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 859-1 (V1.2.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for Transmission of IP packets over GeoNetworking; Part 1: Test requirements and
Protocol Implementation Conformance Statement (PICS) proforma".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 859-3 V1.2.1 (2014-04)
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 (V1.1.1): "Intelligent Transport Systems (ITS); Testing; Framework for
conformance and interoperability testing".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 302 636-6-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 Method
ATS Abstract Test Suite
BI Invalid behaviour
BV Valid behaviour
EVI Expired virtual interfaces
GVL Geographical Virtual Link
IP Internet Protocol
IPv6 Internet Protocol version 6
ITS Intelligent Transportation Systems
IUT Implementation Under Test
MG Message Generation
MR Message Reception
MTC Main Test Component
NVI New virtual interfaces
PA Platform Adaptor
PCTR Protocol Conformance Test Report
PICS Protocol Implementation Conformance Statement
PIXIT Partial Protocol Implementation Extra Information for Testing
PX PiXit
SA System Adaptor
SAP Service Access Point
SCS System Conformance Statement
SCTR System Conformance Test Report
SUT System Under Test
TC Test Case
TP Test Purposes
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
TVL Topological Virtual Link
VM Virtual Interface Management
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 859-3 V1.2.1 (2014-04)
4 Abstract Test Method (ATM)
4.1 Abstract protocol tester
The abstract protocol tester used by the IPv6OverGeoNetworking 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.
Test System SUT
IPv6
SDUs
IPv6Over
GeoNetworking
PDUs
IUT
ITS-G5 ITS-G5
Lower tester

Figure 1: Abstract protocol tester - IPv6OverGeoNetworking
4.2 Test Configuration
The IPv6OverGeoNetworking 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 IPv6OverGeoNetworking protocol.
ItsNodeA
IUT
GVL_AREA3
GVL_AREA2
GVL_AREA1

Figure 2: Test configuration CF01
Both IUT and Test system are located in the GeoAreas associated with the three predefined GVLs. Each GVL is
associated with an IPv6 prefix which can be parameterized using module parameters.
ETSI

---------------------- Page: 8 ----------------------
Adpt_Ctlr
control port
UTport
control port
 9 ETSI TS 102 859-3 V1.2.1 (2014-04)
Table 1: Association between IPv6 prefixes and GVLs
GVL IPv6 Prefix
GVL_AREA1 PX_GN6_PREFIX_1
GVL_AREA2 PX_GN6_PREFIX_2
GVL_AREA3 PX_GN6_PREFIX_3

4.3 Test Architecture
The present document implements the general TTCN-3 test architecture described in EG 202 798 [i.1], clause 6.3.2.
Figure 3 shows the TTCN-3 test architecture used in for the GeoNetworking ATS. The IPv6OverGeoNetworking test
component requires using only the Main Test Component (MTC). The MTC communicates with the
IPv6OverGeoNetworking SUT over the ipv6OverGeoNetworkingPort and geoNetworkingPort. The
ipv6OverGeoNetworkingPort port is used to exchange IPv6 protocol messages between the test component and the
IUT. The geoNetworkingPort port is used to exchange GeoNetworking protocol messages between the test component
and the IUT.
The Upper tester entity in the SUT enables triggering IPv6OverGeoNetworking functionalities by simulating primitives
from applications. It is required to trigger the IPv6OverGeoNetworking layer in the SUT to send
IPv6OverGeoNetworking messages, which are resulting from upper layer primitives. Furthermore, receiving
IPv6OverGeoNetworking messages may result for the IPv6OverGeoNetworking layer in sending primitives to the
upper layer.
ITS TTCN-3 test execution
ItsMtc
(Sync
component)


ItsNt (PTCs)
NT2
geoNetworking
Port

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 3: Test System Architecture
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 859-3 V1.2.1 (2014-04)
4.4 Ports and ASPs (Abstract Services Primitives)
Three ports are used by the IPv6OverGeoNetworking ATS:
• The geoNetworkingPort, of type GeoNetworkingPort.
• The ipv6OverGeoNetworkingPort, of type Ipv6OverGeoNetworkingPort.
• The utPort of type UpperTesterPort.
4.4.1 Primitives of the geoNetworkingPort
Two types of primitives are used in the geoNetworkingPort:
• The geoNetworkingInd primitive used to receive messages of type GeoNetworkingPacket.
• The geoNetworkingReq primitive used to send messages of type GeoNetworkingPacket.
4.4.2 Primitives of the ipv6OverGeoNetworkingPort
Two types of primitives are used in the geoNetworkingPort:
• The Ipv6OverGeoNetworkingInd primitive used to receive messages of type IPv6.
• The Ipv6OvergeoNetworkingReq primitive used to send messages of type IPv6.
4.4.3 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.
4.4.4 Primitives of the taPort
This port uses the following primitives to trigger special behaviour in Test Adapter:
• AcGn6InterfaceInfoList used to retrieve the list of IUT's link-layer interfaces with their configured IPv6
addresses.
• AcGetLongPosVector used to retrieve IUT's position (extracted from IUT's beacon messages).
5 Untestable Test Purposes
Table 2 gives a list of TPs, which are not implemented in the ATS due to the chosen ATM or other restrictions.
Table 2: Untestable TP
Test purpose Reason


ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 859-3 V1.2.1 (2014-04)
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 naming conventions and the implementation conventions. The naming
conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the
functional structure of the ATS.
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 3) indicating the
type of TTCN-3 element it represents;
• suffixes should not be used except in those specific cases identified in table 2;
• 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 identifier following the prefix) should begin with a lower-case letter;
• 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 3 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix,
suffixes (if any) and capitalization.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 859-3 V1.2.1 (2014-04)
Table 3: 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 Use lower-case initial mw_ mw_anyUserReply
matching expression letters
Modifying message template Use lower-case initial letter md_ md_setupInit
Modifying message template with wildcard Use lower-case initial mdw_ mdw_anyUserReply
or matching expression letters
Signature template Use lower-case initial letter s_ s_callSignature
Port instance Use lower-case initial letter none signallingPort
Test component instance Use lower-case initial letter none userTerminal
Constant Use lower-case initial letter c_ c_maxRetransmission
Constant (defined within component type) Use lower-case initial letter cc_ cc_minDuration
External constant Use lower-case initial letter cx_ cx_macId
Function Use lower-case initial letter f_ f_authentication()
External function Use lower-case initial letter fx_ fx_calculateLength()
Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup()
Test case Use ETSI numbering TC_ TC_COR_0009_47_ND
Variable (local) Use lower-case initial letter v_ v_macId
Variable (defined within a component type) Use lower-case initial vc_ vc_systemName
letters
Timer (local) Use lower-case initial letter t_ t_wait
Timer (defined within a component) Use lower-case initial tc_ tc_authMin
letters
Module parameters for PICS Use all upper case letters PICS_ PICS_DOOROPEN
Module parameters for other parameters Use all upper case letters PX_ PX_TESTER_STATION_ID
Formal Parameters Use lower-case initial letter p_ p_macId
Enumerated Values Use lower-case initial letter e_ e_syncOk

6.2.2 ITS specific TTCN-3 naming conventions
Next to such general naming conventions, table 4 shows specific naming conventions that apply to the ITS TTCN-3 test
suite.
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 859-3 V1.2.1 (2014-04)
Table 4: ITS specific TTCN-3 naming conventions
Language element Naming Prefix Example identifier
convention
ITS Module Use upper-case Its"IUTname"_ ItsIpv6OverGeoNetworking_
initial letter
Module containing Use upper-case Its"IUTname"_TypesAndValues ItsIpv6OverGeoNetworking_TypesAndValues
types and values initial letter
Module containing Use upper-case Its"IUTname"_Templates ItsIpv6OverGeoNetworking_Templates
Templates initial letter
Module containing Use upper-case Its"IUTname"_TestCases ItsIpv6OverGeoNetworking_TestCases
test cases initial letter
Module containing Use upper-case Its"IUTname"_Functions ItsIpv6OverGeoNetworking_Functions
functions initial letter
Module containing Use upper-case Its"IUTname"_ExternalFunctions ItsIpv6OverGeoNetworking_ExternalFunctions
external functions initial letter
Module containing Use upper-case Its"IUTname"_Interface ItsIpv6OverGeoNetworking_Interface
components, ports initial letter
and message
definitions
Module containing Use upper-case Its"IUTname"_TestSystem ItsIpv6OverGeoNetworking_TestSystem
main component initial letter
definitions
Module containing Use upper-case Its"IUTname"_TestControl ItsIpv6OverGeoNetworking_TestControl
the control part initial letter

6.2.3 Usage of Log statements
All TTCN-3 log statements use the following format using the same order:
• Three asterisks.
• The TTCN-3 test case or function identifier in which the log statement is defined.
• One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT.
• Free text.
• Three asterisks.
EXAMPLE 1: log("*** f_utInitializeIut: INFO: IUT initialized ***");
Furthermore, the following rules are applied for the IPv6OverGeoNetworking ATS:
• Log statements are used in the body of the functions, so that invocations of functions are visible in the test
logs.
• All TTCN-3 setverdict statements are combined (as defined in TTCN-3 - ES 201 873-1 [7]) with a log
statement following the same above rules (see example 2).
EXAMPLE 2: setverdict(pass, "*** TC_IPV6GEO_MG_GVL_BV_01: PASS: Received
correct GeoNetworking GeoBroadcast ***");
ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 102 859-3 V1.2.1 (2014-04)
6.2.4 Test Case (TC) identifier
Table 5: TC naming convention
Identifier: TC_____
= root IPv6GEO IPv6 over GeoNetworking
= group MG Message Generation
 MR Message Reception
 VM Virtual Interface Management
= subgroup GVL GVL
 TVL TVL
 NVI New virtual interfaces
 EVI Expired virtual interfaces
= type of testing BV Valid Behaviour tests
 BI Invalid Syntax or Behaviour Tests
= sequential number 01 to 99

EXAMPLE: TP identifier: TP/IPv6GEO/MG/GVL/BV/03
TC identifier: TC_IPv6GEO_MG_GVL_BV_03
ETSI

---------------------- Page: 14 ----------------------
15 ETSI TS 102 859-3 V1.2.1 (2014-04)
Annex A (normative):
TTCN-3 library modules
...