ISO/TS 14907-2:2006

Road transport and traffic telematics — Electronic fee collection — Test procedures for user and fixed equipment — Part 2: Conformance test for the onboard unit application interface

ISO TS 14907-2:2006 describes tests that verify OBU conformance of implementations of functions and data structures, as defined in the implementation conformance statement based on ISO 14906, for EFC applications.

Télématique de la circulation et du transport routier — Perception du télépéage — Modes opératoires relatifs aux équipements embarqués et aux équipements fixes — Partie 2: Essai de conformité de l'interface d'application de l'unité embarquée

General Information

• Status: Withdrawn
• Publication Date: 18-Jun-2006
• Withdrawal Date: 18-Jun-2006
• ICS: 35.240.60 - IT applications in transport
• ICS: 43.040.15 - Car informatics. On board computer systems
• Technical Committee: ISO/TC 204 - Intelligent transport systems
• Drafting Committee: ISO/TC 204/WG 5 - Fee and toll collection
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 25-Oct-2011

Relations

• Revised: ISO/TS 14907-2:2011 - Electronic fee collection — Test procedures for user and fixed equipment — Part 2: Conformance test for the onboard unit application interface
• Effective Date: 25-Sep-2010
• Consolidates: ISO 7369:1983 - Pipework — Flexible metallic hoses — Vocabulary of general terms
• Effective Date: 06-Jun-2022

Standards Content (Sample)

TECHNICAL ISO/TS
SPECIFICATION 14907-2
First edition
2006-06-15

Road transport and traffic telematics —
Electronic fee collection —
Test procedures for user and fixed
equipment —
Part 2:
Conformance test for the onboard unit
application interface
Télématique de la circulation et du transport routier — Perception du
télépéage — Modes opératoires relatifs aux équipements embarqués et
aux équipements fixes —
Partie 2: Essai de conformité de l'interface d'application de l'unité
embarquée




Reference number
ISO/TS 14907-2:2006(E)
©
ISO 2006

---------------------- Page: 1 ----------------------
ISO/TS 14907-2:2006(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO 2006
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO 2006 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/TS 14907-2:2006(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Normative references . 4
3 Terms and definitions. 5
4 Abbreviations . 8
5 OBU and supporting information. 12
5.1 ICS . 13
5.2 IXIT. 13
6 Testing requirements . 13
6.1 Conceptual test architecture . 13
6.2 Conformance test system. 14
6.3 Test documentation. 16
Annex A (normative) Implementation conformance statement pro forma. 17
Annex B (normative) Implementation of extra information for testing. 31
Annex C (informative) OBU Test Cases . 35
Annex D (informative) OBE conformance test procedures conducted in Japan. 87
Bibliography . 92

© ISO 2006 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/TS 14907-2:2006(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has
been established has the right to be represented on that committee. International organizations, governmental
and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
— an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
— an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting
a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a
further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is
confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an
International Standard or be withdrawn.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TS 14907-2 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
ISO/TS 14907 consists of the following parts, under the general title Road transport and traffic telematics —
Electronic fee collection — Test procedures for user and fixed equipment:
⎯ Part 1: Description of test procedures
⎯ Part 2: Conformance test for the onboard unit application interface

iv © ISO 2006 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/TS 14907-2:2006(E)
Introduction
This CEN/ISO Technical Specification describes tests that verify OBU conformance of implementations of
functions and data structures for EFC applications.


© ISO 2006 – All rights reserved v

---------------------- Page: 5 ----------------------
TECHNICAL SPECIFICATION ISO/TS 14907-2:2006(E)

Road transport and traffic telematics — Electronic fee
collection — Test procedures for user and fixed equipment —
Part 2:
Conformance test for the onboard unit application interface
1 Scope
This CEN/ISO Technical Specification describes tests that verify OBU conformance of implementations of
functions and data structures, as defined in the implementation conformance statement based on ISO 14906,
for EFC applications. After the tests of isolated data items and functions (C.1-C.2), an example is given for
testing of a complete EFC transaction (C.3).
The scope of this CEN/ISO Technical Specification comprises definitions of OBU conformance assessment
tests of:
⎯ Basic DSRC L7 functionality;
⎯ EFC application functions;
⎯ EFC attributes (i.e. EFC application information);
⎯ the addressing procedures of EFC attributes and (hardware) components (e.g. ICC and MMI);
⎯ the EFC transaction model, which defines the common elements and steps of any EFC transaction; and
⎯ the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface
level.
© ISO 2006 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO/TS 14907-2:2006(E)

Figure 1 — The EFC application interface
The purpose of this CEN/ISO Technical Specification is to define tests that:
⎯ assess OBU capabilities;
⎯ assess OBU behaviour;
⎯ serve as a guide for OBU conformance evaluation and type approval;
⎯ achieve comparability between the results of the corresponding tests applied in different places at
different times; and
⎯ facilitate communications between parties.
Whereas this Technical Specification defines examples of test cases for DSRC and EFC functionality in
Annex C, it does not intend to specify a complete test suite for a certain implementation. To compose a test
suite for a specific EFC implementation, the test cases may have to be modified and new test cases may have
to be defined and added in order for the conformance test to be complete. It may be useful to take into
account the following considerations when defining a complete test suite:
⎯ Small range: “exhaustive testing” of critical interoperability/compatibility features;
⎯ Large range: testing of boundaries and random values;
⎯ Composite types: testing of individual items in sequence or parallel.
Figure 2 shows the overall procedure of conformance testing.
2 © ISO 2006 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/TS 14907-2:2006(E)

Figure 2 — Conformance testing process
© ISO 2006 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO/TS 14907-2:2006(E)
Figure 3 gives a more detailed picture of the interface between the entity performing the conformance test and
the supplier of the Device Under Test (DUT). By the EFC application specification, the implementation
conformance statement pro forma and the implementation extra information for testing pro forma the supplier
is requested to provide the DUT (OBU), containing the Implementation Under Test (IUT), as well as the
documentation needed to perform the tests. More details on the content of the different documents are given
in Clause 5 on OBU and supporting information.
NOTE 1 The Device Under Test contains the Implementation Under Test.

Figure 3 — Documentation DUT supplier
It is outside the scope of this CEN/ISO Technical Specification to define tests that assess:
⎯ performance;
⎯ robustness; and
⎯ reliability of an implementation.
NOTE 2 ISO/TS 14907-1 defines test procedures that are aimed at assessing performance, robustness and reliability
of EFC equipment and systems.
NOTE 3 The ISO/IEC 10373 family of International Standards defines test methods for proximity, vicinity, integrated
circuits(s) cards and related devices that may be relevant for OBUs that support such cards.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic
notation
4 © ISO 2006 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/TS 14907-2:2006(E)
ISO/IEC 8825-2, Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules
(PER)
ISO/IEC 9646-1, Information technology — Open Systems Interconnection — Conformance testing
methodology and framework — Part 1: General concepts
ISO 14906:2004, Road transport and traffic telematics — Electronic fee collection — Application interface
definition for dedicated short-range communication
ISO/TS 14907-1, Road transport and traffic telematics — Electronic fee collection — Test procedures for user
and fixed equipment — Part 1: Description of test procedures
ISO/TS 17574, Road transport and traffic telematics — Electronic fee collection (EFC) — Guidelines for EFC
security protection profiles
EN 12253, Road transport and traffic telematics — Dedicated short-range communication — Physical layer
using microwave at 5,8 GHz
EN 12795, Road transport and traffic telematics — Dedicated short-range communication (DRSC) — DRSC
data link layer: medium access and logical link control
EN 12834, Road transport and traffic telematics — Dedicated short-range communication (DRSC) — DRSC
application layer
EN 13372, Road transport and traffic telematics (RTTT) — Dedicated short-range communication — Profiles
for RTTT applications
3 Terms and definitions
For the purposes of this document, the following definitions apply.
3.1
access credentials
data that is transferred to OBE in order to establish the claimed identity of an RSE application process entity
[ISO 14906]
NOTE The access credentials carry information needed to fulfil access conditions in order to perform the operation
on the addressed element in the OBE. The access credentials can carry passwords as well as cryptographic based
information such as authenticators.
3.2
action
function that an application process resident at the RSE can invoke in order to make the OBE execute a
specific operation during the transaction
[ISO 14906]
3.3
attribute
application information formed by one or by a sequence of data elements, which is managed by different
actions used for implementation of a transaction
[ISO 14906]
3.4
authenticator
data appended to, or a cryptographic transformation of, a data unit that allows a recipient of the data unit to
prove the source and/or the integrity of the data unit and protect against forgery
© ISO 2006 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO/TS 14907-2:2006(E)
[ISO 14906]
3.5
channel
information transfer path
[ISO/IEC 7498-2 and ISO 14906]
3.6
component
logical and physical entity composing OBE, supporting a specific functionality
[ISO 14906]
3.7
contract
expression of an agreement between two or more parties concerning the use of the road infrastructure
[ISO 14906]
3.8
cryptography
discipline which embodies principles, means and methods for the transformation of data in order to hide its
information content, prevent its undetected modification or/and prevent its unauthorized use
[ISO/IEC 7498-2 and ISO 14906]
3.9
data group
collection of closely related EFC data attributes which together describe a distinct part of an EFC transaction
[ISO 14906]
3.10
data integrity
property that data has not been altered or destroyed in an unauthorized manner
[ISO/IEC 7498-2 and ISO 14906]
3.11
element
in the context of DSRC, a directory containing application information in form of attributes
[ISO 14906]
3.12
implementation conformance statement
statement made by the supplier of an implementation or system claimed to conform to a given specification,
stating which capabilities have been implemented
3.13
implementation conformance statement pro forma
document, in the form of a questionnaire, which when completed for an implementation or system becomes
an implementation conformance statement
6 © ISO 2006 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/TS 14907-2:2006(E)
3.14
implementation extra information for testing
statement made by the supplier or an implementer of an IUT which contains or references all of the
information (in addition to that given in the implementation conformance statement) related to the IUT and its
testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT
3.15
implementation extra information for testing pro forma
document, in the form of a questionnaire, which when completed for an IUT becomes an implementation extra
information for testing
3.16
on-board equipment
OBE
equipment located within the vehicle and supporting the information exchange with the RSE, it is composed of
the OBU and other sub-units whose presence are considered optional for the execution of a transaction
[ISO 14906]
3.17
on-board unit
OBU
minimum component of an OBE, whose functionality always includes at least the support of the DSRC
interface
[ISO 14906]
3.18
roadside equipment
RSE
equipment located at a fixed position along the road transport network, for the purpose of communication and
data exchanges with the OBE of passing vehicles
[ISO 14906]
3.19
service (EFC)
road-transport-related facility provided by a service provider, normally a type of infrastructure, the use of which
is offered to the user for which the user may be requested to pay
[ISO 14906]
3.20
service primitive (communication)
elementary communication service provided by the application layer protocol to the application processes
[ISO 14906]
NOTE The invocation of a service primitive by an application process implicitly calls upon and uses services offered
by the lower protocol layers.
3.21
service provider (EFC)
operator that accepts the user’s payment means and in return provides a road-use service to the user
[ISO 14906]
© ISO 2006 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO/TS 14907-2:2006(E)
3.22
session
exchange of information and interaction occurring at a specific EFC station between the RSE and the
user/vehicle
[ISO 14906]
3.23
transaction
whole of the exchange of information between the RSE and the OBE necessary for the completion of an EFC
operation over the DSRC
[ISO 14906]
3.24
transaction model
functional model describing the general structure of EFC transactions
[ISO 14906]
3.25
tester
combination of equipment and processes which is able to perform conformance tests according to this
Technical Specification
3.26
user
entity that uses transport services provided by the service provider according to the terms of a contract
[ISO 14906]
4 Abbreviations
For the purposes of this Technical Specification, the following abbreviations apply throughout the document
unless otherwise specified.
4.1
ADU
Application Data Unit
4.2
APDU
Application Protocol Data Unit
4.3
AP
Application Process
4.4
ARIB
Association of Radio Industries and Businesses
NOTE ARIB (www.arib.or.jp) is based in Japan.
4.5
ASCII
American Standard Code for Information Interchange
8 © ISO 2006 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/TS 14907-2:2006(E)
4.6
ASN.1
Abstract Syntax Notation One
[ISO/IEC 8824-1]
4.7
ASP
Abstract Service Primitives
[ISO 9646-1]
4.8
AVI
Automatic Vehicle Identification
4.9
B-Kernel
Broadcast Kernel
4.10
BST
Beacon Service Table
4.11
cf
confirm
4.12
DSRC
Dedicated Short-Range Communication
4.13
DUT
Device Under Test
4.14
EID
Element Identifier
4.15
EFC
Electronic Fee Collection
4.16
FTP
File Transfer Protocol
4.17
HDLC
High-level Data Link Control
4.18
ICS
Implementation Conformance Statement
4.19
I-Kernel
Initialization Kernel
© ISO 2006 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO/TS 14907-2:2006(E)
4.20
IID
Invoker Identifier
4.21
ind
indication
4.22
IUT
Implementation Under Test
[ISO 9646-1]
4.23
IXIT
Implementation eXtra Information for Testing
4.24
L1
Layer 1 of DSRC (physical layer)
4.25
L2
Layer 2 of DSRC (data link layer)
4.26
L7
Application Layer Core of DSRC
4.27
LID
Logical Link Control Identifier
4.28
LLC
Logical Link Control
4.29
LPDU
LLC Protocol Data Unit
4.30
M
a
ManufacturerID
[EN 12834]
4.31
MAC
Medium Access Control
4.32
MMI
Man-Machine Interface
4.33
n.a.
not applicable
10 © ISO 2006 – All rights reserved

---------------------- Page: 15 ----------------------
ISO/TS 14907-2:2006(E)
4.34
OBE
On-Board Equipment
4.35
OBU
On-Board Unit
4.36
ORSE
Organization for Road System Enhancement
4.37
P
a,b,c,d
Profile
[EN 13372, EN 12834]
EXAMPLE P denotes Profile 0.
0
4.38
PDU
Protocol Data Unit
4.39
PER
Packed Encoding Rules
[ISO/IEC 8825-2]
4.40
PoC
Point of Control
4.41
PoO
Point of Observation
4.42
PPDU
Physical Layer Protocol Data Unit
4.43
PrWA
Private Window Allocation
[EN 12795]
4.44
PrWRq
Private Window Request
[EN 12795]
4.45
req
request
© ISO 2006 – All rights reserved 11

---------------------- Page: 16 ----------------------
ISO/TS 14907-2:2006(E)
4.46
rs
response
4.47
RSE
Roadside Equipment
4.48
RTTT
Road Transport and Traffic Telematics
4.49
SAM
Secure Application Module
4.50
T-APDU
Transfer-Application Protocol Data Unit
4.51
T-ASDU
Transfer-Application Service Data Unit
4.52
T-Kernel
Transfer Kernel
4.53
TTI
Traffic and Traveller Information
4.54
VST
Vehicle Service Table
5 OBU and supporting information
The supplier shall provide the OBU, i.e. the DUT, and the associated information including:
⎯ OBUs personalized to be able to perform tests according to the ICS and IXIT as defined in 5.1 and 5.2,
respectively. At least five samples shall be submitted for test. More samples may be needed if several
different data structures and data contents are required in the tests;
⎯ user’s manual for the OBU, which shall include instructions how to handle the equipment, and may
include further detailed information about the protocol functions;
⎯ implementation conformance statement according to 5.1. The ICS shall include statements regarding the
following:
⎯ layer 7 services that are implemented in the OBU;
⎯ EFC functions (action types) that are implemented in the OBU;
⎯ whether or not data elements are used;
⎯ implementation extra information for testing according to 5.2. The IXIT shall, if applicable, include:
⎯ a statement regarding which layer 2 services shall be used to transfer the L7 services (and EFC
services);
12 © ISO 2006 – All rights reserved

---------------------- Page: 17 ----------------------
ISO/TS 14907-2:2006(E)
⎯ a description of security calculations in the OBU including a specification of the encryption algorithm
used;
⎯ values of the test Master Keys for calculation and verification of OBU security data such as
authenticators and access credentials.
The supplier should also provide configuration/personalization equipment for the OBU if that ensures effective
testing.
5.1 ICS
The ICS is a statement made by the supplier that claims conformance to a certain specification. The ICS
states which capabilities have been implemented in the specifications. It also states possible limitations in the
implementation of the specification.
This Technical Specification describes testing of implementations according to the following standards:
⎯ DSRC application layer; EN 12834;
⎯ EFC application interface; ISO 14906.
Annex A contains the ICS pro forma that shall be used for the ICS.
5.2 IXIT
The IXIT is a statement made by the supplier or an implementer of an IUT which contains or references all of
the information, in addition to that given in the implementation conformance statement, related to the DUT and
its testing environment. The IXIT enables the test laboratory to run an appropriate test suite against the DUT.
In this Technical Specification, the IXIT specifies the services in the lower communication layers that shall be
used to perform the services to be tested. These services are described e.g. in EN 12795, EN 12253 and
EN 13372.
The IXIT shall also contain further information and describe algorithms and procedures that are not specified
in the above standards but are prerequisites to perform the testing. Example of such information is:
⎯ content of the ApplicationContextMark in the VST;
⎯ calculation of access credentials in DSRC services;
⎯ use of ReturnCode in DSRC L7 services and EFC functions; and
⎯ calculation of authenticators in EFC functions.
Annex B contains the IXIT pro forma that shall be used for the declaration of the IXIT.
6 Testing requirements
6.1 Conceptual test architecture
A remote test method shall be used for the conformance test of OBUs (DUT). Figure 4 shows the conceptual
testing architecture of tester and DUT. The conformance test is only related to the implementation of the DUT.
The PoC, which is the point where the test events are controlled, shall be implemented inside the tester on the
interface between the application layer and the application process.
© ISO 2006 – All rights reserved 13

---------------------- Page: 18 ----------------------
ISO/TS 14907-2:2006(E)
The PoO, which is the point where the occurrence of test events is to be observed, shall be implemented
inside the tester on the interface between the application layer and the application process. The PoO must
also interface the data link layer since some tests require observation of the behaviour on this layer.
The PoC and PoO are characterized by a set of ASPs, according to the specifications of the tests. The test
events observed at the PoO may be supplemented by information provided by other sub-units, e.g. MMI or an
IC card if available with the DUT.

Figure 4 — Conceptual architecture of the conformance test
6.2 Conformance test system
The conformance tests shall be performed under controlled conditions by using a test system according to
Figure 5.

Figure 5 — Test facilities
14 © ISO 2006 – All rights reserved

---------------------- Page: 19 ----------------------
ISO/TS 14907-2:2006(E)
6.2.1 Functionality of tester
6.2.1.1 Reference beacon
The beacon shall be a transparent physical layer interface for DSRC according to European or International
Standards, which means it shall be able to operate standardized data profiles of DSRC links. A simple beacon
may be used which will only send and receive frames to or from the DUT. The communication is controlled by
the application and data link process of the tester.
Beacon parameters, e.g. the transmitting power, shall be adjustable by the tester.
6.2.1.2 Application and data link process
The tester shall be able to operate the communication link in real time according to data link layer functionality
of European or International Standards. The process shall provide the connection to the test control and
observation process and shall control the sending and reception of frames to and from the beacon.
6.2.1.3 Test control and observation processes
The test control and observation processes shall be implemented on an appropriately equipped computer
system. The processes shall comply with the definitions of the application and data link layers defined by
European or International standards and shall be able to generate test suites in reference to ISO 14906. The
control process shall provide functionality to configure the test-bed, to generate test suites and to perform test
suites.
EXAMPLE Test suites may be generated in plain ASCII format and may be retrieved by the real-time control process
via FTP.
While the tests are being performed, all events shall be observed by the PoO process. All results shall be
documented, visualized and be made available for detailed analysis.
6.2.2 Conformance testing
The tests performed by the tester shall be able to concentrate on EFC-communication protocol aspects, which
are:
⎯ initialization phase (BST-VST exchange);
⎯ application layer services according to EN 12834;
⎯ EFC functions and services according to ISO 14906;
⎯ EFC data and parameters used according to ISO 14906; and
⎯ transaction phase (logical sequence).
The DUT shall be operated in a controlled environment according to the manufacturer’s instructions.
All test suites shall be generated corresponding to the specification of the manufacturer, which shall describe
the behaviour of the DUT in terms of expected messages from the beacon and intended answers from the
DUT. The communication sequence shall be unambiguously defined. The test generation tool shall be able to
check the messages against the European or International DSRC standards. All events of a DUT are stored
by the tester.
The test suites generated shall strictly correspond to the European or International DSRC standards and to
ISO 14906.
© ISO 2006 – All rights reserved 15

---------------------- Page: 20 ----------------------
ISO/TS 14907-2:2006(E)
The results of the tests shall only be related to the IUT of the DUT. Only the correctness of the implementation
shall be tested, and any assessment of performance, robustness or reliability is excluded. The results of the
tests shall be able to provide confidence that the DUT works according to ICS, the underlying DSRC
standards and to ISO 14906, within the scope of the performed tests.
6.3 Test d
...