|
TECHNICAL SPECIFICATION
Intelligent Transport Systems (ITS);
Testing;
Interoperability test specifications for ITS V2X use cases;
Part 3: Abstract Test Suite (ATS) and Protocol Implementation
eXtra Information for Testing (PIXIT)
---------------------- Page: 1 ----------------------
2 ETSI TS 103 192-3 V1.1.1 (2018-09)
Reference
DTS/ITS-45
Keywords
ATS, interoperability, 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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
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
If you find errors in the present document, please send your comment to one of the following services:
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.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3 ETSI TS 103 192-3 V1.1.1 (2018-09)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 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 Test Configuration . 8
4.1.1 CF-01: Verify complete forwarding message scenario . 8
4.1.2 CF-02: Road Works Warning configuration . 8
4.1.3 CF-03: CA messages . 9
4.1.4 CF-04: Intersection Collision Warning configuration . 9
4.2 Ports and ASPs (Abstract Services Primitives) . 9
4.2.1 Introduction. 9
4.2.2 Primitives of the geoNetworkingPort . 10
4.2.3 Primitives of the utPort . 10
4.2.4 Primitives of the hmiPort . 10
4.2.5 Primitives of the taPort . 10
5 Untestable Test Purposes. 10
6 ATS conventions . 11
6.1 Introduction . 11
6.2 Testing conventions . 11
6.2.1 Testing states . 11
6.2.1.1 Initial state . 11
6.2.1.2 Final state . 11
6.3 Naming conventions . 11
6.3.1 Introduction. 11
6.3.2 General guidelines . 11
6.3.3 ITS specific TTCN-3 naming conventions . 12
6.3.4 Usage of Log statements . 13
6.3.5 Test Case (TC) identifier . 13
Annex A (normative): TTCN-3 library modules . 14
A.1 Electronic annex, zip file with TTCN-3 code . 14
Annex B (normative): Partial PIXIT pro forma for AutoInterop . 15
B.1 The right to copy . 15
B.2 Introduction . 15
B.3 Identification summary. 15
B.4 ATS summary . 15
B.5 Test laboratory . 15
B.6 Client identification . 16
B.7 SUT . 16
B.8 Protocol layer information. 16
ETSI
---------------------- Page: 3 ----------------------
4 ETSI TS 103 192-3 V1.1.1 (2018-09)
B.8.1 Protocol identification . 16
B.8.2 EUT information . 17
Annex C (normative): PCTR pro forma for GeoNetworking . 18
C.1 The right to copy . 18
C.2 Introduction . 18
C.3 Identification summary. 18
C.3.1 Protocol conformance test report . 18
C.3.2 EUT identification . 18
C.3.3 Testing environment . 18
C.3.4 Limits and reservation . 19
C.3.5 Comments. 19
C.4 EUT Conformance status . 19
C.5 Static conformance summary . 19
C.6 Dynamic conformance summary . 20
C.7 Static conformance review report . 20
C.8 Test campaign report . 20
C.9 Observations . 21
Annex D (informative): Bibliography . 22
History . 23
ETSI
---------------------- Page: 4 ----------------------
5 ETSI TS 103 192-3 V1.1.1 (2018-09)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
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 C-ITS test specification for automated
interoperability testing as identified below:
Part 1: "Test requirements and Interoperability Feature Statement (IFS) pro forma ";
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 ETSI EG 202 798 [i.1]. Therefore, the
ATS documentation outlined in the present document is also based on the guidance provided in ETSI EG 202 798 [i.1].
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 interpreted 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.
ETSI
---------------------- Page: 5 ----------------------
6 ETSI TS 103 192-3 V1.1.1 (2018-09)
1 Scope
The present document provides parts of the Abstract Test Suite (ATS) for ITS Interoperability scenarios. The objective
of the present document is to provide a basis for automated interoperability testing.
2 References
2.1 Normative 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
https://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 referenced documents are necessary for the application of the present document.
[1] ETSI EN 302 636-4-1: "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] ETSI EN 302 637-2: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set
of Applications; Part 2: Specification of Cooperative Awareness Basic Service".
[3] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 1: General concepts".
[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".
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 applies. 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 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 103 192-3 V1.1.1 (2018-09)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI EN 302 637-2 [2],
ISO/IEC 9646-1 [3] and 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
BO Inopportune test events for Behaviour tests
BV Valid test events for Behaviour tests
CA Cooperative Awareness
CAM Cooperative Awareness Message
CAN Controller Area Network
CF Configuration
COH Common Header
CRW Collision Risk Warning
DAD Duplicate Address Detection
DEN Decentralized Environmental Notification
DENM Decentralized Environmental Notification Message
EN European Norm
ES ETSI Standard
EUT Equipment Under Test
FDV Formatting and Data Validity
GEONW GeoNetworking
GMC Geo-broadcast Message Caching
HMI Human Machine Interface
ISO International Organization for Standardization
ITS Intelligent Transportation Systems
ITS-G5 5 GHz wireless communication
IUT Implementation Under Test
LOT Location Table
MAC Media Access Control
MFW Message Forwarding
NBD Neighbours Detection
PCTR Protocol Conformance Test Report
PICS Protocol Implementation Conformance Statement
PIXIT Partial Protocol Implementation eXtra Information for Testing
PON Protocol Operation
PX Pixit
RHS Road Hazard Signals
RSU Road Side Unit
RWW Road Works Warning configuration
SAP Service Access Point
SCS System Conformance Statement
SCTR Static Conformance Test Report
SUT System Under Test
SVW Stationary Vehicle Warning
TC Test Case
TI Timer test
TP Test Purposes
TS Technical Specification
TSS Test Suite Structure
TTCN Testing and Test Control Notation
ETSI
---------------------- Page: 7 ----------------------
8 ETSI TS 103 192-3 V1.1.1 (2018-09)
4 Abstract Test Method (ATM)
4.1 Test Configuration
4.1.1 CF-01: Verify complete forwarding message scenario
There are two independent geonetworking areas defined:
1) EUT1 is the source
2) EUT2 is closer to TARGET_GEOAREA than EUT3
3) EUT4 is in the destination area (TARGET_GEOAREA)
4) EUT1, EUT2 and EUT3 are on-link
5) EUT2, EUT3 and EUT4 are on-link
6) EUT1 and EUT4 are off-link
TARGET_GEOAREA
EUT1
EUT2
EUT4
EUT3
Figure 1: DEN message forward
4.1.2 CF-02: Road Works Warning configuration
1) EUT1 and EUT2 are on-link.
2) EUT1 and EUT2 are located in the same Geonetworking area.
3) EUT1 acts as a RSU.
4) EUT2 acts as a vehicle.
5) EUT2 is moving from Start position to End position.
End
POS0 POS1 POS2 POS4
Start POS3
Figure 2: Road Works Warning configuration
ETSI
---------------------- Page: 8 ----------------------
9 ETSI TS 103 192-3 V1.1.1 (2018-09)
4.1.3 CF-03: CA messages
1) EUT1, EUT2 and EUT3 are on-link.
2) EUT1, EUT2 and EUT3 are located in the same Geonetworking area.
3) EUT1, EUT2 and EUT3 act as vehicle.
4) EUT1, EUT2 and EUT3 are moving.
4.1.4 CF-04: Intersection Collision Warning configuration
1) EUT1 and EUT2 are on-link.
2) EUT1 and EUT2 are located in the same Geonetworking area.
3) EUT1 (vehicle) in moving from Start1 position to End1 position.
4) EUT2 (vehicle) in moving from Start2 position to End2 position.
5) Positions POS0 and POS1 are located at the same distance from the intersection.
6) EUT1 respectively EUT2 shall pass the position POS0 respectively POS1 at the same time.
Start1
POS1
POS3
End2
POS2
Start2
End1
Figure 3: Road Works Warning configuration
4.2 Ports and ASPs (Abstract Services Primitives)
4.2.1 Introduction
Two ports are used by the GeoNetworking ATS:
• The geoNetworkingPort, of type GeoNetworkingPort
• The utPort of type UpperTesterPort
• The hmiPort of type HmiPort
ETSI
---------------------- Page: 9 ----------------------
10 ETSI TS 103 192-3 V1.1.1 (2018-09)
4.2.2 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.2.3 Primitives of the utPort
This port uses two types of primitives:
• The UtGnInitialize primitive used to initialize EUT
• The UtTrigger primitive used trigger upper layer events in EUT
4.2.4 Primitives of the hmiPort
This port uses two types of primitives:
• The HmiInitialize primitive used to initialize HMI EUT
• The HmiTrigger primitive used trigger upper layer events in HMI EUT
4.2.5 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 EUT's position (extracted from EUT'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
ETSI
---------------------- Page: 10 ----------------------
11 ETSI TS 103 192-3 V1.1.1 (2018-09)
6 ATS conventions
6.1 Introduction
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 ETSI ETS 300 406 [6] were considered.
6.2 Testing conventions
6.2.1 Testing states
6.2.1.1 Initial state
All test cases start with the function f_prInitialState. This function brings the EUT in an "initialized" state by invoking
the upper tester primitive UtInitialize.
6.2.1.2 Final state
All test cases end with the function f_poDefault. This function brings the EUT 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.3 Naming conventions
6.3.1 Introduction
This test suite follows the naming convention guidelines provided in ETSI EG 202 798 [i.1].
6.3.2 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.
ETSI
---------------------- Page: 11 ----------------------
12 ETSI TS 103 192-3 V1.1.1 (2018-09)
Table 2 specifies the naming guidelines for each element 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 Use lower-case initial letters mw_ mw_anyUserReply
matching expression
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 letters vc_ vc_systemName
Timer (local) Use lower-case initial letter t_ t_wait
Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin
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.3.3 ITS specific TTCN-3 naming conventions
Next to such general naming conventions, table 3 shows specific naming conventions that apply to the ITS TTCN-3 test
suite.
Table 3: ITS specific TTCN-3 naming conventions
Language element Naming convention Prefix Example identifier
ITS Module Use upper-case Its"IUTname"_ ItsGeoNetworking_
initial letter
Module containing Use upper-case Its"IUTname"_TypesAndValues ItsGeoNetworking_TypesAndValues
types and values initial letter
Module containing Use upper-case Its"IUTname"_Templates ItsGeoNetworking_Templates
Templates initial letter
Module containing test Use upper-case Its"IUTname"_TestCases ItsGeoNetworking_TestCases
cases initial letter
Module containing Use upper-case Its"IUTname"_Functions ItsGeoNetworking_Functions
functions initial letter
Module containing Use upper-case Its"IUTname"_ExternalFunctions ItsGeoNetworking_ExternalFunctions
external functions initial letter
Module containing Use upper-case Its"IUTname"_Interface ItsGeoNetworking_Interface
components, ports and initial letter
message definitions
Module containing Use upper-case Its"IUTname"_TestSystem ItsGeoNetworking_TestSystem
main component initial letter
definitions
Module containing the Use upper-case Its"IUTname"_TestControl ItsGeoNetworking_TestControl
control part initial letter
ETSI
-----
...