Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS Misbehaviour Reporting service; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT); Release 2

DTS/ITS-00596-3

General Information

Status
Not Published
Technical Committee
Current Stage
12 - Completion
Due Date
06-May-2024
Completion Date
13-May-2024
Ref Project
Standard
ETSI TS 103 868-3 V2.1.1 (2024-05) - Intelligent Transport Systems (ITS); Testing; Conformance test specifications for ITS Misbehaviour Reporting service; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT); Release 2
English language
26 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


TECHNICAL SPECIFICATION
Intelligent Transport Systems (ITS);
Testing;
Conformance test specifications for ITS Misbehaviour
Reporting service;
Part 3: Abstract Test Suite (ATS) and
Protocol Implementation eXtra Information for Testing (PIXIT);
Release 2
2 ETSI TS 103 868-3 V2.1.1 (2024-05)

Reference
DTS/ITS-00596-3
Keywords
ATS, ITS, PIXIT, security, 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 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
https://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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
her, no representation or warranty is made of merchantability or fitness
and/or governmental rule and/or regulation and furt
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2024.
All rights reserved.
ETSI
3 ETSI TS 103 868-3 V2.1.1 (2024-05)
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 . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 8
4 Contents of the ITS MRS Test Suite . 8
5 Abstract Test Method . 8
5.1 Introduction . 8
5.2 Abstract protocol tester . 8
5.3 Test Configuration . 9
5.3.1 Introduction. 9
5.3.2 MRS infrastructure . 9
5.3.2.1 Overview . 9
5.3.2.2 MRS certificate hierarchy . 9
5.3.2.3 Test system settings. 11
5.3.2.3.1 Test adapter settings . 11
5.3.2.3.2 Test Suite Parameters . 11
5.3.2.4 Certificate profiles . 11
5.3.2.5 Certificate generation . 12
5.3.2.6 Certificate installation . 13
5.4 Test architecture . 13
5.5 Ports and ASPs . 13
5.5.1 Introduction. 13
5.5.2 Primitives of the geoNetworkingPort . 13
5.5.3 Primitives of the utPort . 13
6 External functions . 14
7 ATS conventions . 14
7.1 Introduction . 14
7.2 Testing conventions . 14
7.2.1 Testing states . 14
7.2.1.1 Initial states . 14
7.2.1.2 Final state . 14
7.3 Naming conventions . 14
7.3.1 Introduction. 14
7.3.2 General guidelines . 14
7.3.3 ITS specific TTCN-3 naming conventions . 15
7.3.4 Usage of Log statements . 16
7.3.5 Test Case (TC) identifier . 16
7.4 On line documentation . 17
Annex A (informative): ATS in TTCN-3 . 18
A.1 TTCN-3 files and other related modules . 18
Annex B (normative): Partial PIXIT pro forma for Security . 19
B.1 The right to copy . 19
ETSI
4 ETSI TS 103 868-3 V2.1.1 (2024-05)
B.2 Introduction . 19
B.3 Identification summary. 19
B.4 ATS summary . 19
B.5 Test laboratory . 20
B.6 Client identification . 20
B.7 SUT . 20
B.8 Protocol layer information. 21
B.8.1 Protocol identification . 21
B.8.2 IUT information . 21
Annex C (normative): PCTR pro forma for Security . 23
C.1 The right to copy . 23
C.2 Introduction . 23
C.3 Identification summary. 23
C.3.1 Protocol conformance test report . 23
C.3.2 IUT identification . 23
C.3.3 Testing environment . 24
C.3.4 Limits and reservation . 24
C.3.5 Comments. 24
C.4 IUT Conformance status . 24
C.5 Static conformance summary . 25
C.6 Dynamic conformance summary . 25
C.7 Static conformance review report . 25
C.8 Test campaign report . 25
C.9 Observations . 25
History . 26

ETSI
5 ETSI TS 103 868-3 V2.1.1 (2024-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the ®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
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. Full details of the entire series can be found in part 1 [4].
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
6 ETSI TS 103 868-3 V2.1.1 (2024-05)
1 Scope
The present document specifies the Abstract Test Suite (ATS) for ITS MRS service as defined in ETSI TS 103 759 [2]
in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.6]. The objective of the present document is to
provide a basis for conformance tests for ITS Misbehaviour Reporting service in order to guarantee interoperability
between different manufacturers' equipment.
The ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [i.3] and ISO/IEC 9646-2 [i.4]) as
well as the ETSI rules for conformance testing (ETSI ETS 300 406 [i.7]) 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
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 TS 102 940 (V2.1.1): "Intelligent Transport Systems (ITS); Security; ITS communications
security architecture and security management; Release 2".
[2] ETSI TS 103 759 (V2.1.1): "Intelligent Transport Systems (ITS); Security; Misbehaviour
Reporting service; Release 2".
[3] ETSI TS 103 097 (V2.1.1): "Intelligent Transport Systems (ITS); Security; Security header and
certificate formats; Release 2".
[4] ETSI TS 103 868-1 (V2.1.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for ITS Misbehaviour Reporting service; Part 1: Protocol Implementation
Conformance Statement (PICS); Release 2".
[5] ETSI TS 103 868-2 (V2.1.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for ITS Misbehaviour Reporting service; Part 2: Test Suite Structure and Test
Purposes (TSS & TP); Release 2".
[6] ETSI TS 102 871-2 (V1.5.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for GeoNetworking; Part 2: Test Suite Structure and Test Purposes (TSS & TP)".
[7] ETSI TS 102 871-3 (V1.5.1): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for GeoNetworking; Part 3: Abstract Test Suite (ATS) and Protocol Implementation
eXtra Information for Testing (PIXIT)".
[8] ETSI TS 103 096-2 (V1.5.2): "Intelligent Transport Systems (ITS); Testing; Conformance test
specifications for ITS Security; Part 2: Test Suite Structure and Test Purposes (TSS & TP)".
[9] ETSI TS 103 096-3 (V1.5.2): "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)".
ETSI
7 ETSI TS 103 868-3 V2.1.1 (2024-05)
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: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and
interoperability testing".
[i.2] ETSI TR 103 099: "Intelligent Transport Systems (ITS); Architecture of conformance validation
framework".
[i.3] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems
Interconnection -- Conformance testing methodology and framework - Part 1: General concepts".
[i.4] ISO/IEC 9646-2 (1994): "Information technology -- Open Systems
Interconnection -- Conformance testing methodology and framework -- Part 2: Abstract Test Suite
specification".
[i.5] ISO/IEC 9646-6 (1994): "Information technology -- Open Systems
Interconnection -- Conformance testing methodology and framework -- Part 6: Protocol profile test
specification".
[i.6] ISO/IEC 9646-7 (1995): "Information technology -- Open Systems
Interconnection -- Conformance testing methodology and framework - Part 7: Implementation
Conformance Statements".
[i.7] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[i.8] OpenSSL Project Toolkit Library V1.0.1j.
[i.9] 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".
[i.10] T3D TTCN-3 documenting tool.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 103 097 [3], ETSI TS 103 868-1 [4], ETSI
TS 103 868-2 [5], ETSI TS 102 871-3 [7], ISO/IEC 9646-6 [i.5] and ISO/IEC 9646-7 [i.6] apply.
3.2 Symbols
Void.
ETSI
8 ETSI TS 103 868-3 V2.1.1 (2024-05)
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TS 103 759 [2], ETSI TS 103 097 [3], ETSI
TS 103 861-1 [4] and the following apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BV Valid Behaviour tests
ES ETSI Standard
GN GeoNetworking
HTML HyperText Markup Language
HTTP Hypertext Transfer Protocol
ISO International Organization for Standardization
IUT Implementation Under Test
OER Octet Encoding Rules
PCTR Protocol Conformance Testing Report
PICS Protocol Implementation Conformance Statement
PIXIT Partial Protocol Implementation eXtra Information for Testing
PKI Public Key Infrastructure
SAP Service Access Point
SCS System Conformance Statement
SCTR Static Conformance Test Report
SUT System Under Test
TC Test Case
TP Test Purposes
TR Technical Report
TS Test System
TTCN Testing and Test Control Notation
UT Upper Tester
XER XML Encoding Rules
XML eXtensible Markup Language
XSLT eXtensible Stylesheet Language Transformations
4 Contents of the ITS MRS Test Suite
The ITS MRS test suite contains:
• test implemented in TTCN-3 code;
• certificate profiles and certificate generation tool.
To execute the ITS MRS Test Suite a Test Adapter implementation and a TTCN-3 compiler are required. The reference
Test Adapter implementation can be found at https://forge.etsi.org/rep/ITS/TS.ITS.git. TTCN-3 compilers can be
acquired at http://www.ttcn-3.org.
5 Abstract Test Method
5.1 Introduction
This clause describes the ATM used to test the ITS MRS framework.
5.2 Abstract protocol tester
The abstract protocol tester used by the ITS-Mrs test suite is described in Figure 1. The Test System simulates valid and
invalid protocol behaviour and analyses the reaction of the IUT.
ETSI
9 ETSI TS 103 868-3 V2.1.1 (2024-05)

Test System SUT: ITS-S
TTCN-3 test UT Upper Tester
Port
suite
HTTP
MR service
Port
Adaptation
GeoNetw
/ codec
Detectors
orking
layer
(optional)
Port
Figure 1: Abstract protocol tester - MRS
5.3 Test Configuration
5.3.1 Introduction
This test suite shall use test configurations as defined in ETSI TS 103 868-2 [5], i.e. the tester simulates the MA
implementing the ITS Mrs framework over HTTP protocol.
5.3.2 MRS infrastructure
5.3.2.1 Overview
Before executing tests:
• security certificates need to be generated, see clause 5.3.2.5;
• security certificates need to be installed onto the IUT, see clause 5.3.2.6; and
• some Test System settings need to be configured, see clause 5.3.2.3.
5.3.2.2 MRS certificate hierarchy
The required MRS certificate hierarchy of the test infrastructure shall be as specified in ETSI TS 102 940 [1] and ETSI
TS 103 759 [2].
The following certificates are required for the test execution:
1) The custom user-generated root certificate, referred as CERT_IUT_A_RCA, is used to sign all CA certificates
used by the Test System and by the IUT to verify the Test System certificates. For the generation procedure
see clause 5.3.2.5. The IUT shall install this CERT_IUT_A_RCA certificate and consider it as trusted. In the
case where the IUT cannot install the CERT_IUT_A_RCA, no tests can be executed.
2) The MA certificate CERT_IUT_A_MA shall be generated and installed on the IUT.
ETSI
10 ETSI TS 103 868-3 V2.1.1 (2024-05)
3) Further certificates to be installed on the IUT:
- Option 1: Certificates (CERT_TS_EA and CERT_IUT_AA) can be installed onto the IUT. See
clause 5.3.2.6 for further details on certificate installation.
If the IUT supports AT certificate selection using the UtInitialize Upper Tester command, then all
mandatory tests can be executed and PICS_CERTIFICATE_SELECTION shall be set to true.
- Option 2: The IUT can only use its own pre-installed certificates. In this case only a subset of mandatory
tests can be executed and PICS_CERTIFICATE_SELECTION shall be set to false.
In both cases it is necessary to copy these certificates to the subfolder of the location defined in
PX_CERTIFICATE_POOL_PATH. The name of the subfolder shall be provided in
PX_IUT_SEC_CONFIG_NAME.
It is not necessary to install IUT's ROOT and AA certificates onto the Test System when IUT and TS are using different
PKIs. The TS trusts any root and AA certificate from the IUT.
A set of certificates and private keys are used on the Test System side to sign various messages and other Test System
certificates. These files are generated by the generation script (see clause 5.3.2.5).
All certificates and private keys shall be stored as hexadecimal streams.
The TS selects certificate using its file name. Table 1 describes file extensions to be used to store certificates and private
keys.
Table 1: Certificate pool file extensions
File extension File role
.crt Certificate
.vkey Verification private key
.ekey Encryption private key
Each Enrolment, Authorization or Misbehaviour Authority certificate contains:
• Start and End time
• Assurance level
• Application and Issuing Permissions
• Geographical Validity Restriction (optional)
• Verification public key
• Encryption public key
Each Authorization Ticket certificate contains:
• Start and End time
• Assurance level as defined in ETSI TS 103 097 [3]
• Application Permissions
• Geographical Validity Restriction (optional)
• Verification public key
ETSI
11 ETSI TS 103 868-3 V2.1.1 (2024-05)
5.3.2.3 Test system settings
5.3.2.3.1 Test adapter settings
A reference test adapter has been developed and validated on the TTCN-3 runtime environments as listed in Table 2 and
can be downloaded at https://forge.etsi.org/rep/ITS/ttcn/mbr_ts_103759.git.
Table 2: TTCN-3 Tool Test Adapter Location
TTCN-3 Tool Location
TITAN AtsMBR.cfg
The relevant test adapter parameters for the Test System security and MRS support are listed in Table 3.
Table 3: TTCN-3 Tool Test Adapter Parameters
Parameter Role Default value
TsSecuredMode Shall be set to FALSE to be able to test security envelope on TTCN-3 level. false
TsSecuredPath Secured root path to acces
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...