ETSI TS 103 191-3 V1.2.1 (2017-03)

Intelligent Transport Systems (ITS); Testing; Conformance test specifications for Facilities layer protocols and communication requirements for infrastructure services; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)

RTS/ITS-00177

General Information

• Status: Published
• Publication Date: 27-Mar-2017
• Technical Committee: ITS WG1 - Application Requirements and Services
• Current Stage: 12 - Completion
• Due Date: 31-Mar-2017
• Completion Date: 28-Mar-2017

Standards Content (Sample)

ETSI TS 103 191-3 V1.2.1 (2017-03)






TECHNICAL SPECIFICATION
Intelligent Transport Systems (ITS);
Testing;
Conformance test specifications for
Facilities layer protocols and communication requirements
for infrastructure services;
Part 3: Abstract Test Suite (ATS) and Protocol Implementation
eXtra Information for Testing (PIXIT)

�

---------------------- Page: 1 ----------------------
2 ETSI TS 103 191-3 V1.2.1 (2017-03)



Reference
RTS/ITS-00177
Keywords
ATS, ITS, 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/standards-search
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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 2017.
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 103 191-3 V1.2.1 (2017-03)
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 Abstract protocol tester . 8
4.2 Test Configuration . 8
4.3 Test architecture . 8
4.4 Ports and ASPs (Abstract Services Primitives) . 9
4.4.1 Introduction. 9
4.4.2 MAPEM SPATEM ATS . 10
4.4.2.1 Primitives of the mapemSpatemPort . 10
4.4.2.2 Primitives of the utPort . 10
4.4.3 IVIM ATS . 10
4.4.3.1 Primitives of the ivimPort . 10
4.4.3.2 Primitives of the utPort . 11
4.4.4 SSREM SSEM ATS . 11
4.4.4.1 Primitives of the mapemSsemPort . 11
4.4.4.2 Primitives of the utPort . 11
4.5 Executing CA tests in secured mode . 11
4.6 ETSI test adapter . 12
5 Untestable Test Purposes. 12
6 ATS conventions . 12
6.1 Introduction . 12
6.2 Testing conventions . 13
6.2.1 Testing states . 13
6.2.1.1 Initial state . 13
6.2.1.2 Final state . 13
6.2.2 Message types - ASN.1 definitions . 13
6.3 Naming conventions . 13
6.3.1 Introduction. 13
6.3.2 General guidelines . 13
6.3.3 ITS specific TTCN-3 naming conventions . 14
6.3.4 Usage of Log statements . 15
6.3.5 Test Case (TC) identifier . 15
Annex A (normative): TTCN-3 library modules . 17
A.1 Electronic annex, zip file with TTCN-3 code . 17
Annex B (normative): Partial PIXIT pro forma . 18
B.1 Partial cancellation of copyright . 18
B.2 Introduction . 18
B.3 Identification summary. 18
B.4 ATS summary . 18
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 191-3 V1.2.1 (2017-03)
B.5 Test laboratory . 19
B.6 Client identification . 19
B.7 SUT . 19
B.8 Protocol layer information. 20
B.8.1 Protocol identification . 20
B.8.2 IUT information . 20
B.8.2.1 MAPEM/SPATEM . 20
B.8.2.2 IVIM . 20
B.8.2.3 SREM/SSEM . 21
B.8.2.4 Generic . 21
Annex C (normative): PCTR pro forma . 22
C.1 Partial cancellation of copyright . 22
C.2 Introduction . 22
C.3 Identification summary. 22
C.3.1 Protocol conformance test report . 22
C.3.2 IUT identification . 22
C.3.3 Testing environment . 23
C.3.4 Limits and reservation . 23
C.3.5 Comments. 23
C.4 IUT Conformance status . 23
C.5 Static conformance summary . 24
C.6 Dynamic conformance summary . 24
C.7 Static conformance review report . 24
C.8 Test campaign report . 25
C.9 Observations . 26
History . 27

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 191-3 V1.2.1 (2017-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 (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.
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 Facilities layer
protocols and communication requirements for infrastructure services as identified below:
Part 1: "Test requirements and Protocol Implementation Conformance Statement (PICS) 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 191-3 V1.2.1 (2017-03)
1 Scope
The present document contains the Abstract Test Suite (ATS) for MAPEM-SPATEM, IVIM and SREM-SSEM as
defined in SAE J2735 [1] and ETSI TS 103 301 [2] in compliance with the relevant requirements and in accordance
with the relevant guidance given in ISO/IEC 9646-7 [i.7].
The objective of the present document is to provide a basis for conformance tests for MAPEM-SPATEM, IVIM and
SREM-SSEM equipment giving a high probability of interoperability between different manufacturers' equipment.
The ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [i.4] and ISO/IEC 9646-2 [i.5]) as
well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.8]) are used as a basis for the test methodology.
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
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.
The following referenced documents are necessary for the application of the present document.
[1] SAE J2735 (2016-03): "Dedicated Short Range Communications (DSRC) Message Set
Dictionary™".
[2] ETSI TS 103 301 (V1.1.1) (2016-11): "Intelligent Transport Systems (ITS); Vehicular
Communications; Basic Set of Applications; Facilities layer protocols and communication
requirements for infrastructure services".
[3] ETSI TS 103 191-1 (V1.2.1): "Intelligent Transport Systems (ITS); Facilities layer protocols and
communication requirements for infrastructure services; Part 1: Test requirements and Protocol
Implementation Conformance Statement (PICS) pro forma".
[4] ETSI TS 103 191-2 (V1.2.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for Facilities layer protocols and communication requirements for infrastructure
services; Part 2: Test Suite Structure and Test Purposes (TSS & TP)".
[5] ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications
requirements; Part 2: Applications and facilities layer common data dictionary".
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
referenced 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 191-3 V1.2.1 (2017-03)
[i.2] ETSI TS 103 096-3 (V1.3.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for ITS Security; Part 3: Abstract Test Suite (ATS) and Protocol Implementation
eXtra Information for Testing (PIXIT)".
[i.3] ETSI TR 103 099 (V1.4.1): "Intelligent Transport Systems (ITS); Architecture of conformance
validation framework".
[i.4] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework - Part 1: General concepts".
[i.5] ISO/IEC 9646-2 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 2: Abstract Test Suite specification".
[i.6] ISO/IEC 9646-6 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 6: Protocol profile test specification".
[i.7] ISO/IEC 9646-7 (1995): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 7: Implementation Conformance
Statements".
[i.8] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[i.9] 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".
[i.10] ETSI ES 201 873-7 (V4.5.1): "Methods for Testing and Specification (MTS); The Testing and
Test Control Notation version 3; Part 7: Using ASN.1 with TTCN-3".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given SAE J2735 [1], ISO/IEC 9646-1 [i.4] and in
ISO/IEC 9646-7 [i.7] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASN Abstract Syntax Notation
ATM Abstract Test Method
ATS Abstract Test Suite
BI Invalid Syntax or Behaviour Tests
BV Valid Behaviour Tests
ES ETSI Standard
IS Infrastructure Services
ISO International Organization for Standardization
ITS Intelligent Transport Systems
IUT Implementation Under Test
IVI Infrastructure to Vehicle Information
IVIM IVI-Message
MAPEM MapData Messages
MSD MesSage Dissemination
MSP Message Processing
MTC Main Test Component
PCTR Protocol Conformance Test Report
PICS Protocol Implementation Conformance Statement
PIXIT Partial Protocol Implementation eXtra Information for Testing
PX Pixit
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 191-3 V1.2.1 (2017-03)
RLT Road and Lane topology
SAE Society of Automotive Engineers
SAP Service Access Point
SCS System Conformance Statement
SCTR System Conformance Test Report
SPATEM Signal Phase And Timing Messages
SREM Signal Request Message
SSEM Signal Response Message
SUT System Under Test
TC Test Case
TLC Traffic Light Control
TLM Traffic Light Manoeuvre
TP Test Purposes
TSS Test Suite Structure
TTCN Testing and Test Control Notation
4 Abstract Test Method (ATM)
4.1 Abstract protocol tester
The abstract protocol tester used by this test suite is described in figure 1. The test system simulates valid and invalid
protocol behaviour, and analyses the reaction of the IUT.

Figure 1: Abstract protocol tester - MAPEM SPATEM case
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 MAPEM SPATEM protocol.
4.3 Test architecture
The present document implements the general TTCN-3 test architecture described in ETSI EG 202 798 [i.1],
clauses 6.3.2 and 8.3.1.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 191-3 V1.2.1 (2017-03)
Figure 2 shows the test architecture used in for the MAPEM SPATEM ATS case. The MAPEM SPATEM test
component requires using only the Main Test Component (MTC). The MTC communicates with the MAPEM
SPATEM SUT over the MapemSpatemPort. The MapemSpatemPort is used to exchange MAPEM SPATEM protocol
messages between the MAPEM SPATEM test component and the MAPEM SPATEM IUT.
NOTE: The same behaviour applies for IVIM and SREM SSEM.
The Upper tester entity in the SUT enables triggering MAPEM SPATEM functionalities by simulating primitives from
application. It is required to trigger the MAPEM SPATEM layer in the SUT to send MAPEMs, which are resulting
from upper layer primitives. Furthermore, receiving MAPEMs may result for the MAPEM SPATEM layer in sending
primitives to the upper layer.

ITS TTCN-3 test execution
ItsMtc
(Sync
component )


ItsNt (PTCs)

UTport FA1

Adpt_Ctlr
control port
control port
Facility

Port






FA

CODECS


ITS Test Adaptor

Upper tester ITS lower layers stack

External
transport

functions

System ada ptor
Platform ada ptor
(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)
4.4.1 Introduction
Two ports are used by the MAPEM SPATEM ATS:
• The mapemSpatemPort, of type MapemSpatemPort.
• The utPort, of type UpperTesterPort.
Two port are used by the IVIM ATS:
• The ivimPort, of type IvimPort.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 191-3 V1.2.1 (2017-03)
• The utPort, of type UpperTesterPort.
Two ports are used by the SREM SSEM ATS:
• The sremSsemPort, of type SremSsemPort.
• The utPort, of type UpperTesterPort.
4.4.2 MAPEM SPATEM ATS
4.4.2.1 Primitives of the mapemSpatemPort
Four types of primitives are used in the mapSpatPort:
• The MapemInd primitive used to receive messages of type MapemMsg (MAPEM_PDU + RawData).
• The SpatemInd primitive used to receive messages of type SpatemMsg (SPATEM_PDU + RawData).
• The MapemReq primitive used to send messages of type MAPEM_PDU.
• The SpatemReq primitive used to send messages of type SPATEM_PDU.
These four primitives use the MAPEM type and the SPATEM type, which is declared in the ETSI_TS_103301.asn
ASN.1 module, following the ASN.1 definition from SAE J2735 [1].
4.4.2.2 Primitives of the utPort
This port uses six types of primitives:
• The UtInitialize primitive used to initialize IUT.
• The UtMapemSpatemTrigger primitive used to trigger upper layer events in IUT.
• The UtInitializeResult primitive used to receive upper layer result of initialization in IUT.
• The UtMapemSpatemTriggerResult primitive used to receive upper layer result of triggering
MAPEM-SPATEM in IUT.
• The UtMapemEventInd primitive used to receive upper layer event of MAPEM_PDU in IUT.
• The UtSpatemEventInd primitive used to receive upper layer event of SPATEM_PDU in IUT.
4.4.3 IVIM ATS
4.4.3.1 Primitives of the ivimPort
Four types of primitives are used in the mapSpatPort:
• The ivimInd primitive used to receive messages of type IvimMsg (IVIM_PDU + RawData).
• The IvimReq primitive used to send messages of type IVIM_PDU.
These two primitives use the IVIM_PDU type, which is declared in the ETSI_TS_103301.asn ASN.1 module contained
in the archive ts_10319103v010201p0.zip which accompanies the present document, following the ASN.1 definition
from SAE J2735 [1].
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 191-3 V1.2.1 (2017-03)
4.4.3.2 Primitives of the utPort
This port uses six types of primitives:
• The UtInitialize primitive used to initialize IUT.
• The UtIvimtrigger primitive used to trigger upper layer events in IUT.
• The UtInitializeResult primitive used to receive upper layer result of initialization in IUT.
• The UtIvimTriggerResult primitive used to receive upper layer result of triggering IVIM in IUT.
• The UtIvimEventInd primitive used to receive upper layer event of IVIEM_PDU in IUT.
4.4.4 SSREM SSEM ATS
4.4.4.1 Primitives of the mapemSsemPort
Four types of primitives are used in the mapSpatPort:
• The SremInd primitive used to receive messages of type SremMsg (SSREM_PDU + RawData).
• The SsemInd primitive used to receive messages of type SsemMsg (SSEM_PDU + RawData).
• The SremReq primitive used to send messages of type SSREM_PDU.
• The SsemReq primitive used to send messages of type SSEM_PDU.
These four primitives use the SSREM type and the SSEM type, which is declared in the ETSI_TS_103301.asn ASN.1
module, following the ASN.1 definition from SAE J2735 [1].
4.4.4.2 Primitives of the utPort
This port uses six types of primitives:
• The UtInitialize primitive used to initialize IUT.
• The UtSremSsemTrigger primitive used to trigger upper layer events in IUT.
• The UtInitializeResult primitive used to receive upper layer result of initialization in IUT.
• The UtSremSsemTriggerResult primitive used to receive upper layer result of triggering SSREM-SSEM in
IUT.
• The UtSremEventInd primitive used to receive upper layer event of SSREM_PDU in IUT.
• The UtSsemEventInd primitive used to receive upper layer event of SSEM_PDU in IUT.
4.5 Executing CA tests in secured mode
All the CA tests, with the execption of the SSP tests, can be executed with security enabled or with security disabled.
The choice of running the CA tests in secured or non-secured mode has no impact on the result of the CA tests because
the test verdicts assess CA protocol behaviour only.
The SSP tests can only be executed in secured mode.
The choice of running the CA tests in secured or non-secured mode can be controlled via the test suite parameter
PICS_IS_IUT_SECURED, see table A.4/1 in ETSI TS 103 191-1 [3].
Before running the CA tests in secured mode, the following steps need to be executed:
• security certificates need to be gener
...