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

Intelligent Transport Systems (ITS); Testing; Conformance test specifications for GeoNetworking ITS-G5; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)

RTS/ITS-0030024

General Information

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

Standards Content (Sample)

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






Technical Specification
Intelligent Transport Systems (ITS);
Testing;
Conformance test specifications for GeoNetworking ITS-G5;
Part 3: Abstract Test Suite (ATS) and Protocol Implementation
eXtra Information for Testing (PIXIT)

�

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



Reference
RTS/ITS-0030024
Keywords
ATS, 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 871-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 . 6
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.2.1 Test Configuration Overview . 8
4.2.2 Configuration 1: CF01 . 9
4.2.3 Configuration 2: CF02 . 9
4.2.4 Configuration 3: CF03 . 10
4.2.5 Configuration 4: CF04 . 11
4.2.6 Configuration 5: CF05 . 12
4.2.7 Configuration 6: CF06 . 13
4.2.8 Configuration 7: CF07 . 14
4.3 Test architecture . 14
4.4 Ports and ASPs (Abstract Services Primitives) . 15
4.4.1 Primitives of the geoNetworkingPort . 16
4.4.2 Primitives of the utPort . 16
4.4.3 Primitives of the taPort . 16
5 Untestable Test Purposes. 16
6 ATS conventions . 16
6.1 Testing conventions . 17
6.1.1 Testing states . 17
6.1.1.1 Initial state . 17
6.1.1.2 Final state . 17
6.2 Naming conventions . 17
6.2.1 General guidelines . 17
6.2.2 ITS specific TTCN-3 naming conventions . 18
6.2.3 Usage of Log statements . 19
6.2.4 Test Case (TC) identifier . 19
Annex A (normative): TTCN-3 library modules . 21
A.1 Electronic annex, zip file with TTCN-3 code . 21
Annex B (normative): Partial PIXIT proforma for GeoNetworking . 22
B.1 Identification summary. 22
B.2 ATS summary . 22
B.3 Test laboratory . 22
B.4 Client identification . 23
B.5 SUT . 23
B.6 Protocol layer information. 23
B.6.1 Protocol identification . 23
B.6.2 IUT information . 24
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 102 871-3 V1.2.1 (2014-04)
Annex C (normative): PCTR Proforma for GeoNetworking . 26
C.1 Identification summary. 26
C.1.1 Protocol conformance test report . 26
C.1.2 IUT identification . 26
C.1.3 Testing environment . 26
C.1.4 Limits and reservation . 27
C.1.5 Comments. 27
C.2 IUT Conformance status . 27
C.3 Static conformance summary . 27
C.4 Dynamic conformance summary . 28
C.5 Static conformance review report . 28
C.6 Test campaign report . 29
C.7 Observations . 31
Annex D (informative): Bibliography . 32
History . 33

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 102 871-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 specification for GeoNetworking
ITS-G5 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

---------------------- Page: 5 ----------------------
6 ETSI TS 102 871-3 V1.2.1 (2014-04)
1 Scope
The present document contains the Abstract Test Suite (ATS) for GeoNetworking ITS-G5 as defined in
EN 302 636-4-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 ITS-G5
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/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 EN 302 636-4-1 (V1.2.0): "Intelligent Transport Systems (ITS); Vehicular Communications;
GeoNetworking; Part 4: Geographical addressing and forwarding for point-to-point and point-to-
multipoint communications; Sub-part 1: Media-Independent Functionality".
[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 871-1: "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for GeoNetworking ITS-G5; 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 (V1.1.1): "Intelligent Transport Systems (ITS); Testing; Framework for
conformance and interoperability testing".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 102 871-3 V1.2.1 (2014-04)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 302 636-4-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
BAA GeoBroadcast Advanced Algorithm
BAH Basic Header
BCA GeoBroadcast CBF Algorithm
BEA Beacon
BI Invalid Behaviour
CAN Controller Area Network
CAP Buffer Capacities
CBF Contention Based Forwarding
COH Common Header
FPB Forwarding Packet Buffer
FSR Forwarder, Sender and the local GeoAdhoc router positions
GAC Geographically-Scoped Anycast
GBC Geographically-Scoped Broadcast
GNA GeoNetworking Address
GUC Geographically-Scoped Unicast
HST Header Sub-Type
ITS Intelligent Transportation Systems
ITS-G5 5 GHz wireless communication
IUT Implementation Under Test
LDM Local Dynamic Map
LOS Location Service
LPV Local Position Vector
MTC Main Test Component
PCTR Protocol Conformance Test Report
PIXIT Partial Protocol Implementation Extra Information for Testing
PTC Parallel Test Component
SAP Service Access Point
SCS System Conformance Statement
SCTR System Conformance Test Report
SHB Single Hop Broadcast
SQN Sequence Number
SUT System Under Test
TC Test Case
TH Threshold
TP Test Purposes
TSB Topologically-Scoped Broadcast
TTCN Tree and Tabular Combined Notation
V2I Vehicle-to-Infrastructure
V2V Vehicle-to-Vehicle
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 102 871-3 V1.2.1 (2014-04)
4 Abstract Test Method (ATM)
4.1 Abstract protocol tester
The abstract protocol tester used by the GeoNetworking 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
Upper Tester
GeoNet
working
PDUs
IUT
ITS-G5 ITS-G5
Lower tester

Figure 1: Abstract protocol tester - GeoNetworking
4.2 Test Configuration
4.2.1 Test Configuration Overview
This clause introduces the test configurations that have been used for the definition of test purposes. The test
configurations cover the various scenarios of the GeoNetworking tests. The test configurations show:
• green ItsNode: ItsNode is in the communication range of the IUT.
• red ItsNode: ItsNode is not in the communication range of the IUT.
• dashed rectangle: definition of a specific geographical area (see note).
NOTE: A geographical area is defined in the GeoBroadcast or GeoAnycast packet by HST field of Common
Header and GeoAreaPos Latitude, GeoAreaPos Longitude, DistanceA, DistanceB and Angle fields of the
Extended Header.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 102 871-3 V1.2.1 (2014-04)
Seven test configurations are defined below.
4.2.2 Configuration 1: CF01
ItsNodeA
ItsN odeB
AREA2
IUT
CF01
AREA1

Figure 2
ItsNodeA is not in IUT's communication range
ItsNodeB is in IUT's communication range
is in direction of ItsNodeA
is in AREA1
is in AREA2
IUT is in AREA1

4.2.3 Configuration 2: CF02
ItsNodeB
ItsNodeD
AREA2
IUT
AREA1
CF02

Figure 3
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 102 871-3 V1.2.1 (2014-04)
ItsNodeB is in IUT's communication range
is close to the centre of AREA2
is in AREA1
is in AREA2
ItsNodeD is in IUT's communication range
is in direction of ItsNodeB
is in AREA1
is in AREA2
IUT is in AREA1

4.2.4 Configuration 3: CF03

Figure 4
ItsNodeA is not in IUT's communication range
ItsNodeB is in IUT's communication range
is in direction of ItsNodeA
is in AREA1
is in AREA2
ItsNodeC is in IUT's communication range
is not in direction of ItsNodeA
IUT is in AREA1
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 102 871-3 V1.2.1 (2014-04)

4.2.5 Configuration 4: CF04
ItsNodeA
ItsNodeB
ItsNodeD
AREA2
IUT
AREA1
CF04
ItsNodeC

Figure 5
ItsNodeA is not in IUT's communication range
ItsNodeB is in IUT's communication range
is in direction of ItsNodeA
is closer to ItsNodeA than ItsNodeD
is in AREA1
is in AREA2.
is close to the centre of AREA2
ItsNodeC is in IUT's communication range
is not in direction of ItsNodeA
ItsNodeD is in IUT's communication range
is in direction of ItsNodeA
is in AREA1
is in AREA2
IUT is in AREA1

ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 102 871-3 V1.2.1 (2014-04)
4.2.6 Configuration 5: CF05
Dist_R
ItsNodeB
IUT
Dist_F
ItsNodeE
AREA1
CF05

Figure 6
ItsNodeB is in IUT's communication range
is in AREA1
is close to the centre of AREA1
ItsNodeE is in IUT's communication range
is in AREA1
IUT is in AREA1
is closer to ItsNodeB than ItsNodeE (Dist_R < Dist_F)
Angle FSR formed by ItsNodeE, ItsNodeB and IUT is less
than Angle_TH

ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 102 871-3 V1.2.1 (2014-04)
4.2.7 Configuration 6: CF06

Figure 7
ItsNodeB is in IUT's communication range
is in AREA1
is close to the centre of AREA1
ItsNodeF is in IUT's communication range
is in AREA1
IUT is in AREA1
is closer to ItsNodeB than ItsNodeE (Dist_R < Dist_F)
Angle FSR formed by ItsNodeF, ItsNodeB and IUT is
greater than Angle_TH

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 102 871-3 V1.2.1 (2014-04)
4.2.8 Configuration 7: CF07
Dist_F
ItsNodeB
ItsNodeD
Dist_R
IUT
AREA1
CF07

Figure 8
ItsNodeB is in IUT's communication range
is in AREA1
is close to the centre of AREA1
ItsNodeD is in IUT's communication range
is in AREA1
is closer to ItsNodeB than IUT (Dist_R > Dist_F)
Angle FSR formed by ItsNodeD, ItsNodeB and IUT is less
than Angle_TH
IUT is in AREA1

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 and
clause 8.3.1.
Figure 9 shows the TTCN-3 test architecture used for the GeoNetworking ATS. In single-component testcases
(configuration CF01), the MTC is of type ItsNt and communicates with SUT over geoNetworkingPort. In
multi-component testcases (configuration CF02, CF03 and CF04), the MTC is of type ItsMtc and is used to synchronize
the different PTCs. The PTCs are implemented using ItsNt components and communicate with SUT over
geoNetworkingPort. Port geoNetworkingPort is used to exchange GeoNetworking protocol messages between the
GeoNetworking test components and the GeoNetworking IUT.
The Upper tester entity in the SUT enables triggering GeoNetworking functionalities by simulating primitives from
application or LDM entities. It is required to trigger the GeoNetworking layer in the SUT to send GeoNetworking
messages, which are resulting from upper layer primitives. Furthermore, receiving GeoNetworking messages may result
for the GeoNetworking layer in sending primitives to the upper layer.
ETSI

---------------------- Page: 14 ----------------------
Adpt_Ctlr
control port
UTport
control port
 15 ETSI TS 102 871-3 V1.2.1 (2014-04)
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 9: Test system architecture
In multi-component testcases, each PTC maps the geoNetworkingPort. In this case, the geoNetworkingPort is connected
in a one-to-many manner, as described in ES 201 873-1 [7], clause 9.1, Figure 6h.
For each PTC mapping the geoNetworkingPort, the test adapter shall assign a different MAC layer address which will
be used for all send operations of this PTC. In addition the test adapter shall follow the rules below when receiving
GeoNetworking packets:
• If the lower layer headers indicate a broadcasted message, then enqueue the GeoNetworking packet on all
PTCs.
• Otherwise, use the lower layer destination MAC address to determine on which PTC the GeoNetworking
packet shall be enqueued.
4.4 Ports and ASPs (Abstract Services Primitives)
Two ports are used by the GeoNetworking ATS:
• The geoNetworkingPort, of type GeoNetworkingPort
• The utPort of type UpperTesterPort
ETSI

---------------------- Page: 15 ----------------------
16 ETSI TS 102 871-3 V1.2.1 (2014-04)
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 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.3 Primitives of the taPort
This port uses the following primitives to trigger special behaviour in Test adapter:
• AcStartBeaconing: Test adapter shall start sending beacon messages for a simulated ITS node
• AcStopBeaconing: Test adapter shall stop sending beacon messages for a simulated ITS node
• AcStartPassBeaconing: Test adapter shall transmit received beacon messages to TTCN-3 script
• AcStopPassBeaconing: Test adapter shall not transmit received beacon messages to TTCN-3 script
• AcStartBeaconingMultipleNeighbour: Test adapter shall start sending beacon messages for multiple simulated
ITS nodes
• AcStopBeaconingMultipleNeighbour: Test adapter shall stop sending beacon messages for multiple simulated
ITS nodes
• AcGetLongPosVector used to retrieve IUT's position (extracted from IUT's beacon messages)
5 Untestable Test Purposes
Table 1 gives a list of TP, which are not implemented in the ATS due to the restriction of the chosen ATM.
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.
ETSI

---------------------- Page: 16 ----------------------
17 ETSI TS 102 871-3 V1.2.1 (2014-04)
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 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 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 2 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix,
suffixes (if any) and capitalization.
ETSI

---------------------- Page: 17 ----------------------
18 ETSI TS 102 871-3 V1.2.1 (2014-04)
Table 2: ETSI TT
...