EN ISO 13143-1:2016

SLOVENSKI STANDARD
01-april-2017
1DGRPHãþD
SIST-TS CEN ISO/TS 13143-1:2011
Elektronsko pobiranje pristojbin - Ugotavljanje skladnosti opreme v vozilu in
obcestni napravi s standardom ISO 12813 - 1. del: Zgradba preskuševalnega niza
in namen preskušanja (ISO 13143-1:2016)
Electronic fee collection - Evaluation of on-board and roadside equipment for conformity
to ISO 12813 - Part 1: Test suite structure and test purposes (ISO 13143-1:2016)
Elektronische Gebührenerhebung - Konformitätsbeurteilung von bordeigenen und
straßenseitigen Ausrüstungen nach ISO 12813 - Teil 1: Struktur und Zweck des
Prüfprogramms (ISO 13143-1:2016)
Perception du télépéage - Évaluation des équipements embarqués et en bord de route
quant à la conformité avec l' ISO 12813 - Partie 1: Structure de suite d'essais et buts des
essais (ISO 13143-1:2016)
Ta slovenski standard je istoveten z: EN ISO 13143-1:2016
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
43.040.15 $YWRPRELOVNDLQIRUPDWLND Car informatics. On board
9JUDMHQLUDþXQDOQLãNLVLVWHPL computer systems
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN ISO 13143-1
EUROPEAN STANDARD
NORME EUROPÉENNE
December 2016
EUROPÄISCHE NORM
ICS 03.220.20; 35.240.60 Supersedes CEN ISO/TS 13143-1:2011
English Version
Electronic fee collection - Evaluation of on-board and
roadside equipment for conformity to ISO 12813 - Part 1:
Test suite structure and test purposes (ISO 13143-1:2016)
Perception du télépéage - Évaluation des équipements Elektronische Gebührenerhebung -
embarqués et en bord de route quant à la conformité Konformitätsbeurteilung von bordeigenen und
avec l'ISO 12813 - Partie 1: Structure de suite d'essais straßenseitigen Ausrüstungen nach ISO/TS 12813 -
et buts des essais (ISO 13143-1:2016) Teil 1: Struktur und Zweck des Prüfprogramms (ISO
13143-1:2016)
This European Standard was approved by CEN on 6 December 2016.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2016 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 13143-1:2016 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 13143-1:2016) has been prepared by Technical Committee ISO/TC 204
“Intelligent transport systems” in collaboration with Technical Committee CEN/TC 278 “Intelligent
transport systems” the secretariat of which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by June 2017, and conflicting national standards shall be
withdrawn at the latest by June 2017.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent
rights.
This document supersedes CEN ISO/TS 13143-1:2011.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.
Endorsement notice
The text of ISO 13143-1:2016 has been approved by CEN as EN ISO 13143-1:2016 without any
modification.
INTERNATIONAL ISO
STANDARD 13143-1
First edition
2016-12-01
Electronic fee collection — Evaluation
of on-board and roadside equipment
for conformity to ISO 12813 —
Part 1:
Test suite structure and test purposes
Perception du télépéage — Évaluation des équipements embarqués et
en bord de route quant à la conformité avec l’ISO 12813 —
Partie 1: Structure de suite d’essais et buts des essais
Reference number
ISO 13143-1:2016(E)
©
ISO 2016
ISO 13143-1:2016(E)
© ISO 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 Test suite structure (TSS) . 4
5.1 Structure . 4
5.2 Reference to conformance test specifications . 4
5.3 Test purposes (TP) . 5
5.3.1 TP definition conventions . 5
5.3.2 TP naming conventions . 5
5.4 Conformance test report . 6
Annex A (normative) Test purposes for on-board units . 7
Annex B (normative) Test purposes for roadside equipment.36
Annex C (normative) PCTR proforma for on-board units .45
Annex D (normative) PCTR proforma for roadside equipment .52
Bibliography .57
ISO 13143-1:2016(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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
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. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO’s adherence to the World Trade Organization (WTO) principles in the
Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.
The committee responsible for this document is ISO/TC 204, Intelligent transport systems.
This first edition of ISO 13143-1 cancels and replaces the first edition of ISO/TS 13143-1:2011, which has
been technically revised and incorporates the following main modifications compared to ISO/TS 13143-1:
— conversion from a Technical Specification to an International Standard;
— amendment of terms, in order to reflect harmonization of terms across electronic fee collection
(EFC) standards;
— amendments to reflect changes to the underlying requirements standards, in particular ISO 12813
and ISO 14906;
— editorial and formal corrections.
A list of all parts in the ISO 13143 series can be found on the ISO website.
iv © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
Introduction
ISO 17575 is part of a set of standards that supports interoperability of autonomous EFC-systems. It
defines the EFC context data, their charge reports and their use of communication infrastructure.
The set of standards also supports short-range communication links in the context of autonomous
electronic fee collection (EFC) on-board equipment (OBE) to enable spot checks for the enforcement
process. The application interface is defined in ISO 12813:2015.
Within the set of EFC standards, this document defines the process and tests for conformity evaluation
of OBE and roadside equipment (RSE) that comply with the requirements in ISO 12813:2015.
This document is intended to
— assess OBU and RSE capabilities,
— assess OBU and RSE behaviour,
— serve as a guide for OBU and RSE conformance evaluation and type approval,
— achieve comparability between the results of the corresponding tests applied in different places at
different times, and
— facilitate communication between parties.
This document is based on
— ISO 12813:2015,
— the set of dedicated short-range communication (DSRC) standards defining the communication
stack, and
— ISO/IEC 9646.
This document is based on using the tree and tabular combined notation (TTCN) that is a standardized
language suitable for specification of test cases and steps for assessment of protocol and application
behaviour. The TTCN language is also supported by modern automated tools that accelerate software
design, implementation and testing.
INTERNATIONAL STANDARD ISO 13143-1:2016(E)
Electronic fee collection — Evaluation of on-board and
roadside equipment for conformity to ISO 12813 —
Part 1:
Test suite structure and test purposes
1 Scope
This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity
of on-board units (OBU) and roadside equipment (RSE) to ISO 12813:2015.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment
(on-board units and roadside units) to enable interoperability between different equipment supplied by
different manufacturers.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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 12813:2015, Electronic fee collection — Compliance check communication for autonomous systems
ISO 14906:1/Amd 1:2015, Electronic fee collection — Application interface definition for dedicated short-
range communication / Amendment 1
ISO/TS 14907-2:2016, Electronic fee collection — Test procedures for user and fixed equipment — Part 2:
Conformance test for the on-board unit application interface
EN 15509:2014, Electronic fee collection — Interoperability application profile for DSRC
EN 15876-1:2016, Electronic fee collection — Evaluation of on-board and roadside equipment for
conformity to EN 15509 — Part 1: Test suite structure and test purposes
ETSI/TS 102 486-2-2 V1.2.1 (2008-10), Intelligent Transport Systems (ITS); Road Transport and Traffic
Telematics (RTTT); Test specifications for Dedicated Short Range Communication (DSRC) transmission
equipment; Part 2: DSRC application layer; Sub-Part 2: Test Suite Structure and Test Purposes (TSS&TP)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at http://www.iso.org/obp
ISO 13143-1:2016(E)
3.1
access credentials
trusted attestation or secure module that establishes the claimed identity of an object or application
Note 1 to entry: Access credentials carry information needed to fulfil access conditions in order to perform the
operation on the addressed element in the OBE. Access credentials can carry passwords, as well as cryptography-
based information such as authenticators.
[SOURCE: EN 15509:2014, 3.1]
3.2
attribute
addressable package of data consisting of a single data element or structured sequences of data
elements
[SOURCE: ISO 17575-1:2016, 3.2]
3.3
authentication
security mechanism allowing verification of the provided identity
[SOURCE: EN 301 175]
3.4
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: EN 15509:2014, 3.3]
3.5
cryptography
principles, means and methods for the transformation of data in order to hide its information content,
prevent its undetected modification or prevent its unauthorised use
[SOURCE: EN 15509:2014, 3.6]
3.6
data group
class of closely related attributes
[SOURCE: ISO 17575-1:2016, 3.10]
3.7
Element
directory containing application information in the form of attributes
[SOURCE: ISO 14906:2011, 3.11 modified]
3.8
implementation conformance statement
statement of capabilities and options that have been implemented defining to what extent the
implementation is compliant with a given specification
[SOURCE: ISO/TS 14907-2:2016, 3.16]
3.9
implementation extra information for testing
statement containing all of the information related to the implementation under test (IUT) and its
corresponding system under test (SUT) which will enable the testing laboratory to run an appropriate
test suite against that IUT
[SOURCE: ISO/TS 19015:2000, 3.20]
2 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
3.10
on-board equipment
OBE
all required equipment on-board a vehicle for performing required EFC functions and communication
services
3.11
on-board unit
OBU
single electronic unit on-board a vehicle for performing specific EFC functions and for communication
with external systems
3.12
roadside equipment
RSE
equipment located along the road, either fixed or mobile
[SOURCE: ISO/TS 19299:2015, 3.34]
3.13
tester
combination of equipment, humans and processes able to perform specified conformance tests
[SOURCE: EN 15876-1:2016, 3.12]
3.15
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: ISO 17575-1:2016, 3.21]
4 Abbreviated terms
AC_CR Access Credentials
ADU Application Data Unit
APDU Application Protocol Data Unit (ISO 14906)
AP Application Process
ASN.1 Abstract Syntax Notation One (ISO/IEC 8824-1)
ATS Abstract Test Suite
BI Behaviour Invalid (i.e. Invalid Behaviour tests)
B-Kernel Broadcast Kernel
BST Beacon Service Table (ISO 14906)
BV Behaviour Valid (i.e. Valid Behaviour tests)
cf Confirm
DLC Data link Control
DSRC Dedicated Short-Range Communication (ISO 14906)
DUT Device Under Test (ISO/TS 14907-2)
ISO 13143-1:2016(E)
EID Element Identifier
EFC Electronic Fee Collection (ISO 17573)
ICS Implementation Conformance Statement
LLC Logical Link Control (EN 12795)
MAC Medium Access Control (EN 12795)
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PIXIT Protocol Implementation eXtra Information for Testing
TSS Test Suite Structure
VST Vehicle Service Table (ISO 14906)
5 Test suite structure (TSS)
5.1 Structure
Table 1 shows the Test suite structure (TSS) including its subgroups that are inherited from other
specifications.
Table 1 — Test suite structure
Group Type of DUT Behaviour
Physical layer On-board unit Valid behaviour
Invalid behaviour
Roadside equipment Valid behaviour
Invalid behaviour
DLC MAC sublayer On-board unit Valid behaviour
Invalid behaviour
Roadside equipment Valid behaviour
Invalid behaviour
DLC LLC sublayer On-board unit Valid behaviour
Invalid behaviour
Roadside equipment Valid behaviour
Invalid behaviour
Application layer On-board unit Valid behaviour
Invalid behaviour
Roadside equipment Valid behaviour
Invalid behaviour
Physical layer tests are to be performed in a radio wave laboratory. They will not form part of the ATS.
5.2 Reference to conformance test specifications
Conformance to a profile standard implies conformance to the related base standards; hence, a
number of test cases for the CCC application are exactly the same as the conformance test cases for
the related base standards. Other test cases are derived from the base standards conformance test
4 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
cases, by applying some restrictions or choices in, for example, the parameters values, according to
what is stated in the profile standard. Finally, specific conformance test cases for the CCC application
are identified for statements contained in the CCC application, which have no equivalence in the base
standards. These latter cases cover for example the application layer data test purposes. This document
takes into account already defined test purposes for conformance to the base standards by referencing
them, so that:
a) For test purposes that are identical to those defined in the base standards conformance test
cases (see e.g. ETSI/TS 102 486-2-2 or EN 15876-1), a direct reference is reported. For reader’s
convenience, the title or a verbal description of the referenced test purpose is given, together with
the reference.
b) For test purposes that are derived from those defined in the base standards conformance test
cases, a direct reference is reported, plus an indication on how the referred test purpose has to be
modified for the profile conformance testing.
c) For test purposes that are specific to the standard profile, a complete description is given.
An indication on whether a test purpose is identical, derived, or specific is given in each test purpose.
5.3 Test purposes (TP)
5.3.1 TP definition conventions
The TPs are defined following the rules shown in Table 2. All test purposes are defined in Annex A and
Annex B.
Table 2 — TP Definition Rules
TP ID according to Title
the TP naming conventions Reference
TP origin
Initial condition
Stimulus and expected behaviour
TP ID The TP ID is a unique identifier. It shall be specified according to the
TP naming conventions defined in the sub-clause below.
Title Short description of test purpose objective.
Reference The reference should contain the references of the subject to be val-
idated by the actual TP (specification reference, clause, paragraph),
or the reference to the standard document defining the TP.
TP origin Indicates if the TP is identical to a TP defined in another test stand-
ard, derived from a TP defined in another test standard, or specific
for this standard profile.
Initial condition The condition defines in which initial state the DUT has to be to
apply the actual TP.
Stimulus and expected Definition of the events the tester performs, and the events that are
behaviour expected from the DUT to conform to the base specification.
5.3.2 TP naming conventions
Each TP is given a unique identification. This unique identification is built up to contain the following
string of information:
TP/ //-
ISO 13143-1:2016(E)
TP : to indicate that it is a test purpose;
: which group among those defined in Table 1 does the TP apply to;
: type of DUT (i.e. OBU or RSE);
: type of testing (i.e. Valid behaviour tests, BV, or Invalid behaviour tests, BI);
: sequential TP number (01 to 99).
The naming conventions are as described in Table 3.
Table 3 — TP naming convention
Identifier: TP/ /
/ -

applicable for OBU/RSE PHY Physical layer
applicable for OBU/RSE MAC/LLC MAC/LLC sublayer
applicable for OBU/RSE AP-BAS Application layer – I Kernel support
applicable for OBU AP-FUN Application layer – T Kernel support
applicable for OBU AP-DAT Application layer – Data attributes support
applicable for OBU AP-SEC Application layer – Security Level 1 support
applicable for RSE AP-GET Application layer - GET-rq PDU test purposes,
applicable for RSE AP-STA Application layer - GET-STAMPED-rq PDU test purposes
applicable for RSE AP-MMI Application layer - SET-MMI-rq PDU test purposes
applicable for RSE AP-ECH Application layer - ECHO-rq PDU test purposes
applicable for RSE AP-REL Application layer - EVENT-REPORT-rq PDU test purposes
= type of DUT OBU On-board unit
RSE Roadside equipment
x = Type of testing BV Valid behaviour tests
BI Invalid behaviour tests
= sequential number (01–99) Test purpose number
5.4 Conformance test report
The manufacturer of the OBU and RSE, respectively, is responsible for providing a conformance
test report.
The manufacturer of the OBU shall complete the protocol conformance test report (PCTR) for on-board
units as defined in Annex C.
The manufacturer of the RSE shall complete the PCTR for roadside equipment as defined in Annex D.
6 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
Annex A
(normative)
Test purposes for on-board units
A.1 General
This annex contains the test purposes (TP) for the conformity evaluation of OBUs to ISO 12813.
A.1.1 Symbols in TP descriptions
For the application layer test purposes, a special notation and symbol convention is used, as defined in
what follows.
Symbols are used in the description of the TPs, with meanings according to Table A.1.
Table A.1 — Description of TP Symbols
SYMBOL DESCRIPTION
XXX.rq ⇒ The Tester sends the XXX.rq PDU to the DUT
⇐ YYY.rs The DUT sends the YYY.rs PDU to the Tester
A ≡ B Test purpose A “is congruent to” test purpose B. The notation
Test purpose A ≡ Test purpose B means that the Test purpose
A is the same as Test purpose B. If differences in parameters
or parameter values have to be applied, these differences are
indicated in the text immediately below.
A → B Object A “is transformed” into Object B. So a notation like
“Table X → Table Y” means that, for the scope of the Test pur-
pose, any reference of Table X should be changed into references
to Table Y.
= Means “assignment”. That is, a notation like “accessCredentials =
a value” means that the field accessCredentials is given a value.
Ø Means “empty” or “not set”. So, a notation like “accessCreden-
tials = Ø → accessCredentials = calculated value”, for a given
Test purpose, means “change all occurrences in which the field
accessCredentials has not been assigned to calculation of the
value accessCredentials to a given value.
A.2 Physical layer
Per ISO 12813:2015, 5.5.2, all test purposes TP/PHY/OBU/Bx/yy defined in EN 15876-1 are applicable
for the conformity evaluation of OBUs to CEN–DSRC based CCC as claimed in ISO/TS 12813:2015,
Table B.8, Item 1.
A.3 MAC and LLC
Per ISO 12813:2015, 5.5.2, all test purposes TP/MAC/OBU/Bx/yy and TP/LLC/OBU/Bx/yy defined in
EN 15876-1 are applicable for the conformity evaluation of OBUs to CEN–DSRC based CCC as claimed in
ISO 12813:2015, Table B.8, Item 1.
ISO 13143-1:2016(E)
A.4 Application Layer
A.4.1 Structure of BST and VST
A.4.1.1 BST
The BST general structure, as is transmitted to the OBU, is described in Table A.2.
Table A.2 — BST general structure
Length Allowed Values
T-APDUs 4 bit ’1000’ indicating initialisation-request (BST)
Option indicator 1 bit (nonmandApplications opt.) 0/1
rsu manufacturerid 16 bits See ISO 14816
individualid 27 bits as specified by manufacturer
Time 32 bits UNIX real time
profile 1 bit (Profile ext.) 0 (= no extension)
7 bits See Profile in EN 12834:2003, Annex A and
EN 13372, 6.3.2
MandAp- 1 bit (mandApplications ext.) 0 (= no extension)
plications
7 bits (number of applications) M
CCC Applica- 1 bit (eid opt.) 0 (= eid not present)
tion
1 bit (parameter opt.) 0 (= parameter not present)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits 20 (= CCC application)
Applica- 1 bit (eid opt.) 0/1
tion 2
1 bit (parameter opt.) 0/1
(not CCC)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits 20 (= CCC application)
eid 1 bit (eid ext.) 0 (= no extension)
7 bits any
parameter See ApplicationContextMark in
EN 12834:2003, Annex A
... ... ...
Application 1 bit (eid opt.) 0/1
M
1 bit (parameter opt.) 0/1
(not CCC)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits 20 (= CCC application)
eid 1 bit (eid ext.) 0 (= no extension)
7 bits any
parameter See ApplicationContextMark in
EN 12834:2003, Annex A
non- 1 bit (mandApplications ext.) 0 (= no extension)
mandAp
7 bits (number of applications) N
plications
Application 1 See “Application 2 (not EFC)” of mandApplications
(not EFC)
... ...
Application N See “Application 2 (not EFC)” of mandApplications
(not EFC)
profileList 1 bit (profileList ext.) 0 (= no extension)
7 bits (number of profiles) K
Profile 1 1 bit (Profile ext.) 0 (= no extension)
8 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
Table A.2 (continued)
Length Allowed Values
7 bits See Profile in EN 12834:2003, Annex A and
EN 13372, 6.3.2
... ... ...
Profile K 1 bit (Profile ext.) 0 (= no extension)
7 bits See Profile in EN 12834:2003, Annex A and
EN 13372, 6.3.2
A.4.1.2 VST
The VST general structure, as is transmitted by the OBU, is described in Table A.3.
Table A.3 — VST general structure (security level 1)
Length Allowed value
fill 4 bits any
1 bit (Profile ext.) 0 (= no extension)
profile
See Profile in EN 12834:2003,
7 bits
Annex A
1 bit (applications ext.) 0 (= no extension)

7 bits (number of applic.) M
1 bit (eid opt.) 1 (= eid present)

1 bit (parameter opt.) 1 (= parameter present)
1 bit (aid ext.) 0 (= no extension)
aid
5 bits 20 (= CCC application)
1 bit (eid ext.) 0 (= no extension)
eid
7 bits any (≠ other eid used in this VST)
1 bit (Container ext.) 0 (= no extension)

7 bits (Container CHOICE) 2 (= OCTET STRING)
1 bit (octet string ext.) 0 (= no extension)

7 bits (octet string length) 16
10 bits (CountryCode) See ISO 3166-1
contract
Provider
14 bits (IssuerIdentifier) See ISO 14816
CCC- typeOf
16 bits any
CCC
ContextMark Contract
Application
1 bit (contextVersion ext.) 0 (= no extension)
context
Version
7 bits any
para
meter
1 bit (Container ext.) 0 (= no extension)
7 bits (Container CHOICE) 2 (= OCTET STRING)

1 bit (octet string ext.) 0 (= no extension)
7 bits (octet string length) 2
applications
AC_Master
8 bits any
KeyRef
AC_CR-
Reference
AC_CR-
8 bits any
Diversifier
1 bit (Container ext.) 0 (= no extension)
7 bits (Container CHOICE) 2 (= OCTET STRING)

1 bit (octet string ext.) 0 (= no extension)
7 bits (octet string length) 4

RndOBE 32 bits any
ISO 13143-1:2016(E)
Table A.3 (continued)
Length Allowed value
1 bit (eid opt.) 0/1
1 bit (parameter opt.) 0/1
1 bit (aid ext.) 0 (= no extension)
aid
See DSRCApplicationEntityID,
5 bits
Application 2 EN 12834:2003, Annex A
1 bit (eid ext.) 0 (= no extension)
eid
7 bits any (≠ other eid used in this VST)
See ApplicationContextMark,
parameter
EN 12834:2003, Annex A
… 1 bit (eid opt.) 0/1
1 bit (parameter opt.) 0/1
1 bit (aid ext.) 0 (= no extension)
aid
See DSRCApplicationEntityID,
5 bits
EN 12834:2003, Annex A
Application M
1 bit (eid ext.) 0 (= no extension)
eid
7 bits any (≠ other eid used in this VST)

See ApplicationContextMark,
parameter
EN 12834:2003, Annex A
1 bit (obeStatus opt.) 0/1
obe
Configuration
equipmentClass 15 bits any
manufacturerId 16 bits any
obeStatus 16 bits any
A.4.2 PDUs parameters
A.4.2.1 Parameters of request PDUs
The following tables describe the valid format of the request APDUs:
— Table A.4;
— Table A.5;
— Table A.6;
— Table A.7;
— Table A.8.
No other request commands are used by CCC application.
Fill bits shall always be set to zero.
Table A.4 — GET-Rq parameters (security level 1)
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16
Annex A
GET-Rq fill =
eid =
accessCredentials OPTIONAL = mandatory
iid OPTIONAL prohibited
attributeIdList OPTIONAL mandatory
10 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
Table A.5 — Action-Rq parameters for GET_STAMPED action (security level 1)
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16 and
Annex A ISO 12813
AC- mode TRUE
TION-Rq
eid =
actionType 0 (GET_STAMPED)
=
accessCredentials OPTIONAL mandatory
actionParameters OPTIONAL GetStampedRq
iid OPTIONAL prohibited
Table A.6 — Action-Rq parameters for SET_MMI action
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16 and
Annex A ISO 12813
AC- mode =
TION-Rq
eid 0
actionType 10 (SET_MMI)
=
accessCredentials OPTIONAL prohibited
actionParameters OPTIONAL SetMMIRq
iid OPTIONAL prohibited
Table A.7 — Action-Rq parameters for ECHO action
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16 and
Annex A ISO 12813
AC- mode =
TION-Rq
eid 0
actionType 15 (ECHO)
=
accessCredentials OPTIONAL prohibited
actionParameters OPTIONAL mandatory
iid OPTIONAL prohibited
Table A.8 — EVENT-REPORT-Rq parameters
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16
Annex A and ISO 12813
EVENT- mode =
RE-
eid 0
PORT-
eventType 0 (release)
Rq
=
accessCredentials OPTIONAL prohibited
eventParameters OPTIONAL prohibited
iid OPTIONAL prohibited
A.4.2.2 Parameters of response PDUs
The following tables describe the valid format of the request APDUs:
— Table A.9;
— Table A.10;
— Table A.11;
ISO 13143-1:2016(E)
— Table A.12.
No other request commands are used by CCC application.
Fill bits always shall be set to zero.
Table A.9 — GET-Rs parameters
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16
Annex A
GET-Rs fill =
eid =
iid OPTIONAL = prohibited
attributeList OPTIONAL mandatory
ret OPTIONAL mandatory
Table A.10 — Action-Rs parameters for GET_STAMPED action
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16 and
Annex A ISO 12813
AC- fill =
TION-Rs
eid =
iid OPTIONAL = prohibited
responseParameter OPTIONAL mandatory
ret OPTIONAL mandatory
Table A.11 — Action-Rs parameters for SET_MMI action
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16
Annex A and ISO 12813
AC- fill =
TION-Rs
eid 0
iid OPTIONAL = prohibited
responseParameter OPTIONAL prohibited
ret OPTIONAL mandatory
Table A.12 — Action-Rs parameters for ECHO action
EN 12834:2003, Annex A ISO 14906/Amd 1:2015, EN 15509:2014, Table C.16
Annex A and ISO 12813
AC- fill =
TION-Rs
eid 0
iid OPTIONAL prohibited
=
responseParameter OPTIONAL conditional (present when
ret = 0)
ret OPTIONAL mandatory
A.4.3 Application I-kernel test purposes for on-board unit, security level 1
These Test purposes apply to the security level 1 as claimed in ISO 12813:2015, Table B.6, Item 1 and to
initialization and termination processes claimed in ISO/TS 12813:2015, Table B.7, Items 1 and 5.
12 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
A.4.3.1 Data structures
For the purpose of this conformance test, the following BSTs described in
— Table A.13 and
— Table A.14
are transmitted to the DUT. Invalid values are indicated in boldface.
Table A.13 — BST1 (actual BST used, BV) valid BST
Length Value
Option indicator 1 bit (nonmandApplications opt.) 0 (= nonmandApplications not
present)
RSU manufacturerid 16 bits registered value
individualid 27 bits any
Time 32 bits any
profile 1 bit (Profile ext.) 0 (= no extension)
7 bits 0
MandAp- 1 bit (mandApplications ext.) 0 (= no extension)
plica-
7 bits (number of applications) 1
tions
CCC Appli- 1 bit (eid opt.) 0 (= eid not present)
cation
1 bit (parameter opt.) 0 (= parameter not present)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits 20 (= CCC application)
profileList 1 bit (profileList ext.) 0 (= no extension)
7 bits (number of profiles) 0 (= list empty)
Table A.14 — BST2 (actual BST used, BI) invalid BST: extraneous parameter (CCC application
inserted as non-mandatory application)
Length Value
Option indicator 1 bit (nonmandApplications opt.) 1 (= nonmandApplications present)
RSU manufacturerid 16 bits registered value
individualid 27 bits any
Time 32 bits any
profile 1 bit (Profile ext.) 0 (= no extension)
7 bits 0
MandAp- 1 bit (mandApplications ext.) 0 (= no extension)
plications
7 bits (number of applications) 1
A pp l i c a - 1 bit (eid opt.) 1 (= eid present)
tion #1
1 bit (parameter opt.) 0 (= parameter not present)
(not CCC)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits ≠ 20 (AID that is not supported by
the OBU)
eid 1 bit (eid ext.) 0 (= no extension)
7 bits any
ISO 13143-1:2016(E)
Table A.14 (continued)
Length Value
Option indicator 1 bit (nonmandApplications opt.) 1 (= nonmandApplications present)
non- 1 bit (nonmandApplications ext.) 0 (= no extension)
mandAp-
7 bits (number of applications) 1
plica-
CCC Appli- 1 bit (eid opt.) 0 (= eid not present)
tions
cation
1 bit (parameter opt.) 0 (= parameter not present)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits 20 (= CCC application)
profileList 1 bit (profileList ext.) 0 (= no extension)
7 bits (number of profiles) 0 (= list empty)
A.4.3.2 BV test purposes
Test subgroup objective:
— to test the behaviour of the DUT in relation to
— valid BST, and
— valid EVENT-REPORT-Rq (Release);
— to test the DUT support of
— BeaconId,
— Time,
— Profile,
— Applications, and
— LID.
TP/AP-BAS/OBU/BV/01 Receive and manage INITIALISATION.request (BST)
TP origin Identical to TP/AL-I/OBU/BV/01 in ETSI/TS 102 486–2-2, 5.4.1
Reference ISO 12813:2015, 6.1.2
Initial condition See TP/AL-I/OBU/BV/01 in ETSI/TS 102 486–2-2, 5.4.1
Stimulus and Expected behaviour
See TP/AL-I/OBU/BV/01 in ETSI/TS 102 486–2-2, 5.4.1.

TP/AP-BAS/OBU/BV/02 Receive and manage EVENTREPORT request (RELEASE) with
mode = 0
TP origin Identical to TP/AL-I/OBU/BV/02 in ETSI/TS 102 486–2-2, 5.4.1
Reference ISO 12813:2015, 6.1.6
Initial condition See TP/AL-I/OBU/BV/02 in ETSI/TS 102 486–2-2, 5.4.1
Stimulus and Expected behaviour
See TP/AL-I/OBU/BV/02 in ETSI/TS 102 486–2-2, 5.4.1.
14 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
TP/AP-BAS/OBU/BV/03 Read and manage the BeaconID in the BST
TP origin Identical to TP/AL-I/OBU/BV/03 in ETSI/TS 102 486–2-2, 5.4.1
Reference ISO 12813:2015, 6.1.2
Initial condition Identical to TP/AL-I/OBU/BV/03 in ETSI/TS 102 486–2-2, 5.4.1
Stimulus and Expected behaviour
See TP/AL-I/OBU/BV/03 in ETSI/TS 102 486–2-2, 5.4.1.

TP/AP-BAS/OBU/BV/04 Read and manage time of reception of BST in parameter
Time in BST
TP origin Identical to TP/AL-I/OBU/BV/04 in ETSI/TS 102 486–2-2, 5.4.1
Reference ISO 12813:2015, 6.1.2
Initial condition Identical to TP/AL-I/OBU/BV/04 in ETSI/TS 102 486–2-2, 5.4.1
Stimulus and Expected behaviour
See TP/AL-I/OBU/BV/04 in ETSI/TS 102 486–2-2, 5.4.1.
NOTE Test purposes with ID TP/AP-BAS/OBU/BV/05 to TP/AP-BAS/OBU/BV/08 have not been used to be in
line with the numbering in ETSI/TS 102 486–2-2.
TP/AP-BAS/OBU/BV/09 Manage profile selection
TP origin Identical to TP/AL-I/OBU/BV/09 in ETSI/TS 102 486–2-2, 5.4.1
Reference ISO 12813:2015, 6.1.2
Initial condition See TP/AL-I/OBU/BV/09 in ETSI/TS 102 486–2-2, 5.4.1
Stimulus and Expected behaviour
See TP/AL-I/OBU/BV/09 in ETSI/TS 102 486–2-2, 5.4.1.

TP/AP-BAS/OBU/BV/10 Verify that the DUT replies to a BST with a VST
TP origin Specific
Reference ISO 12813:2015, 6.1.2
Initial condition DUT not in sleep mode and not yet initialized
Stimulus and Expected behaviour
Tester DUT
1 BST1 ⇒
2 ⇐ VST
3 Verify length and allowed values of VST
(see Table A.3)
4 IF verification performed in step 3 was
not successful THEN TP failed
A.4.3.3 BI test purposes
Test subgroup objective:
— to check the behaviour of the DUT in response to invalid messages
ISO 13143-1:2016(E)
TP/AP-BAS/OBU/BI/01 Manage profile selection
TP origin Identical to TP/AL-I/OBU/BI/01 in ETSI/TS 102 486–2-2, 5.4.2
Reference ISO 12813:2015, 6.1.2
Initial condition See TP/AL-I/OBU/BI/01 in ETSI/TS 102 486–2-2, 5.4.2
Stimulus and Expected behaviour
See TP/AL-I/OBU/BI/01 in ETSI/TS 102 486–2-2, 5.4.2.

TP/AP-BAS/OBU/BI/02 Manage applications
TP Origin Identical to TP/AL-I/OBU/BI/02 in ETSI/TS 102 486–2-2, 5.4.2
Reference ISO 12813:2015, 6.1.2
Initial Condition See TP/AL-I/OBU/BI/02 in ETSI/TS 102 486–2-2, 5.4.2
Stimulus and Expected behaviour
See TP/AL-I/OBU/BI/02 in ETSI/TS 102 486–2-2, 5.4.2.

TP/AP-BAS/OBU/BI/03 Verify that the DUT handles BST with CCC application
marked as non-mandatory application
TP origin Specific
Reference ISO 12813:2015, 6.1.2
Initial condition DUT not in sleep mode and not yet initialized
Stimulus and Expected behaviour
Tester DUT
1 BST2 ⇒
2 Verify that DUT does not initialize with
INITIALISATION-response (VST).
3 IF verification performed in step 2 was
not successful THEN TP failed
A.4.4 Application T-kernel test purposes for on-board unit
These Test purposes apply to the layer 7 functions related to T-kernel as claimed in ISO 12813:2015,
Table B.7, Items 2 to 6.
A.4.4.1 BV test purposes
Test subgroup objective:
— to test the behaviour of the DUT in relation to syntactically and contextual correct behaviour of the
test system.
TP/AP-FUN/OBU/BV/01 Receive GET.request and manage GET.response with
LID = private
TP origin Identical to TP/AL-T/OBU/BV/01 in ETSI/TS 102 486–2-2, 5.2.1
Reference ISO 12813:2015, 6.1.3
Initial condition See TP/AL-T/OBU/BV/01 in ETSI/TS 102 486–2-2, 5.2.1
Stimulus and Expected behaviour
See TP/AL-T/OBU/BV/01 in ETSI/TS 102 486–2-2, 5.2.1.
NOTE: Request with accessCredentials.
16 © ISO 2016 – All rights reserved

ISO 13143-1:2016(E)
TP/AP-FUN/OBU/BV/08 Receive ACTION.request with mode = 1, manage ACTION.re-
sponse with LID = private
TP origin Identical to TP/AL-T/OBU/BV/08 in ETSI/TS 102 486–2-2, 5.2.1
Refer
...