SIST EN ISO 13143-1:2021

SLOVENSKI STANDARD
01-januar-2021
Nadomešča:
SIST EN ISO 13143-1:2017
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:2020)
Electronic fee collection - Evaluation of onboard and roadside equipment for conformity
to ISO 12813 - Part 1: Test suite structure and test purposes (ISO 13143-1:2020)
Elektronische Gebührenerhebung - Bewertung der Konformität fahrzeuginterner und
straßenseitiger Ausrüstung nach ISO 12813 - Teil 1: Struktur und Zweck des
Prüfprogrammes (ISO 13143-1:2020)
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:2020)
Ta slovenski standard je istoveten z: EN ISO 13143-1:2020
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 Avtomobilska informatika. Car informatics. On board
Vgrajeni računalniški sistemi 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
November 2020
EUROPÄISCHE NORM
ICS 03.220.20; 35.240.60 Supersedes EN ISO 13143-1:2016
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:2020)
Perception de télépéage - Évaluation des équipements Elektronische Gebührenerhebung - Bewertung der
embarqués et en bord de route quant à la conformité Konformität fahrzeuginterner und straßenseitiger
avec l'ISO 12813 - Partie 1: Structure de suite d'essais Ausrüstung nach ISO 12813 - Teil 1: Struktur und
et buts des essais (ISO 13143-1:2020) Zweck des Prüfprogrammes (ISO 13143-1:2020)
This European Standard was approved by CEN on 24 October 2020.

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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, 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: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 13143-1:2020 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 13143-1:2020) 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 May 2021, and conflicting national standards shall be
withdrawn at the latest by May 2021.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN ISO 13143-1:2016.
This document has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association.
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, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the
United Kingdom.
Endorsement notice
The text of ISO 13143-1:2020 has been approved by CEN as EN ISO 13143-1:2020 without any
modification.
INTERNATIONAL ISO
STANDARD 13143-1
Second edition
2020-11
Electronic fee collection — Evaluation
of on-board and roadside equipment
for conformity to ISO 12813 —
Part 1:
Test suite structure and test purposes
Perception de 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:2020(E)
©
ISO 2020
ISO 13143-1:2020(E)
© ISO 2020
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
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 (TPs) . 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 equipment . 7
Annex B (normative) Test purposes for roadside equipment.46
Annex C (normative) Protocol conformance test report proforma for on-board equipment .58
Annex D (normative) Protocol conformance test report proforma for roadside equipment .65
Bibliography .70
ISO 13143-1:2020(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 of the voluntary nature of standards, 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 www .iso .org/
iso/ foreword .html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, in
collaboration with the European Committee for Standardization (CEN) Technical Committee CEN/TC
278, Intelligent transport systems, in accordance with the Agreement on technical cooperation between
ISO and CEN (Vienna Agreement).
This second edition cancels and replaces the first edition (ISO 13143-1:2016), which has been technically
revised.
The main changes compared to the previous edition are as follows:
— amendments to reflect changes to the underlying requirements standards, in particular ISO 12813
and ISO 14906;
— amendment of terms to reflect the harmonization of terms across electronic fee collection (EFC)
standards.
A list of all parts in the ISO 13143 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
Introduction
On-board equipment (OBE) that uses satellite-based positioning technology to collect data required for
charging for the use of roads operates in an autonomous way (i.e. without relying on dedicated roadside
infrastructure). The OBE records the amount of road usage in all toll charging systems it passes through.
This document defines the process and tests for evaluation of OBE and roadside equipment (RSE) for
conformity to ISO 12813.
ISO 12813 defines requirements for dedicated short-range communication (DSRC) between OBE and an
interrogator for the purpose of checking conformance of road use with a local toll regime. It assumes an
electronic fee collection (EFC) services architecture according to ISO 17573-1.
This document is intended to:
— assess OBE and RSE capabilities,
— assess OBE and RSE behaviour,
— serve as a guide for OBE 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,
— the set of DSRC standards defining the communication stack, and
— ISO/IEC 9646.
INTERNATIONAL STANDARD ISO 13143-1:2020(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 (TPs) for evaluating the
conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and
RSE to support interoperability between different equipment supplied by different manufacturers.
ISO 12813 defines requirements on the compliance check communication (CCC) interface level, but
not for the RSE or OBE internal functional behaviour. Consequently, tests regarding OBE and/or RSE
functional behaviour remain outside the scope of this document.
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 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country codes
ISO 12813:2019, Electronic fee collection — Compliance check communication for autonomous systems
ISO 14816, Road transport and traffic telematics — Automatic vehicle and equipment identification —
Numbering and data structure
ISO 14906:2018, Electronic fee collection — Application interface definition for dedicated short-range
communication
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 12834:2003, Road transport and traffic telematics — Dedicated Short Range Communication (DSRC) —
DSRC application layer
EN 13372:2004, Road Transport and Traffic Telematics (RTTT) — Dedicated short-range communication —
Profiles for RTTT applications
EN 15509:2014, Electronic fee collection — Interoperability application profile for DSRC
EN 15876-1, 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)
ISO 13143-1:2020(E)
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:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
access credentials
AC-CR
trusted attestation or secure module that establishes the claimed identity of an object or application
[SOURCE: ISO/TS 17573-2:2020, 3.4]
3.2
attribute
addressable package of data consisting of a single data element or structured sequences of data
elements
[SOURCE: ISO/TS 17573-2:2020, 3.13]
3.3
authentication
security mechanism allowing verification of the provided identity
[SOURCE: ISO/TS 17573-2:2020, 3.15]
3.4
authenticator
data, possibly encrypted, that is used for authentication (3.3)
[SOURCE: ISO/TS 17573-2:2020, 3.16]
3.5
data group
class of closely related attributes (3.2)
[SOURCE: ISO/TS 17573-2:2020, 3.55]
3.6
Element
dedicated short-range communication (DSRC) directory containing application information in the form
of attributes (3.2)
3.7
implementation conformance statement
ICS
statement of capabilities and options that have been implemented that defines to what extent the
implementation is compliant with a given specification
[SOURCE: ISO/TS 17573-2:2020, 3.90]
3.8
protocol implementation conformance statement
PICS
ICS (3.7) for an implementation or system claimed to conform to a given protocol specification
[SOURCE: ISO/IEC 9646-1:1994, 3.3.80]
2 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
3.9
on-board equipment
OBE
all required equipment on-board a vehicle for performing required electronic fee collection (EFC)
functions and communication services
[SOURCE: ISO/TS 17573-2:2020, 3.126]
3.10
on-board unit
OBU
electronic unit on-board a vehicle for performing specific electronic fee collection (EFC) functions and
for communication with external systems
[SOURCE: ISO/TS 17573-2:2020, 3.127]
3.11
roadside equipment
RSE
fixed of moveable electronic fee collection (EFC) equipment located along or on the road
[SOURCE: ISO/TS 17573-2:2020, 3.161, modified — Note 1 to entry deleted.]
3.12
tester
combination of equipment, humans and processes able to perform specified conformance tests
[SOURCE: ISO/TS 17573-2:2020, 3.188]
3.13
transaction
whole of the exchange of information between two physically separated communication facilities
[SOURCE: ISO/TS 17573-2:2020, 3.211]
4 Abbreviated terms
APDU application protocol data unit
AP application process
ATS abstract test suite
BI behaviour invalid (i.e. invalid behaviour tests)
BST beacon service table
BV behaviour valid (i.e. valid behaviour tests)
CCC compliance check communication
DLC data link control
DSRC dedicated short-range communication
DUT device under test
EFC electronic fee collection
EID Element identifier
ISO 13143-1:2020(E)
LLC logical link control
MAC medium access control
PCTR protocol conformance test report
PDU protocol data unit
PIXIT protocol implementation extra information for testing
SCTR system conformance test report
T-APDU transfer-application protocol data unit
TP test purpose
TSS test suite structure
VST vehicle service table
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 OBE BV
BI
RSE BV
BI
Data link Control (DLC) OBE BV
BI
Medium Access Control (MAC) sublayer
RSE BV
BI
DLC Logical Link Control (LLC) sublayer OBE BV
BI
RSE BV
BI
Application layer OBE BV
BI
RSE BV
BI
Physical layer tests are to be performed in a radio wave laboratory. They will not form part of the
abstract test suite (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 identical to the conformance test cases for the related base
4 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
standards. Other test cases are derived from the base standards conformance test 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 the 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 been
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 (TPs)
5.3.1 TP definition conventions
The TPs are defined following the rules shown in Table 2. All TPs 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 is specified according to the TP naming conven-
tions defined in 5.3.2.
Title Short description of TP objective.
Reference Contains the reference (document, clause, paragraph) to the subject to be validated
by the actual TP.
TP origin Indicates if the TP is identical to a TP defined in another test standard, derived from
a TP defined in another test standard, or specific for this standard profile.
Initial condition The condition defines the required initial state of the DUT at the time of launching
of the actual TP.
Stimulus and expected Definition of the events the tester performs and the events that are expected from
behaviour 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:2020(E)
TP : to indicate that it is a test purpose;
: to which group among those defined in Table 1 the TP applies;
: type of DUT (i.e. OBE 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 conventions

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 protocol data unit (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
5.4 Conformance test report
The manufacturer of the OBE and the RSE, respectively, is responsible for providing a conformance
test report.
The manufacturer of the OBE shall complete the protocol conformance test report (PCTR) for OBE as
defined in Annex C.
The manufacturer of the RSE shall complete the PCTR for roadside equipment as defined in Annex D.
6 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
Annex A
(normative)
Test purposes for on-board equipment
A.1 Introduction
A.1.1 General
This annex contains the test purposes (TPs) for the conformity evaluation of OBE to ISO 12813.
A.1.2 Symbols in TP descriptions
For the application layer test purposes, a special notation and symbol convention is used, as defined in
this subclause.
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 protocol data unit (PDU) to the device under test (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 pa-
rameter 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 TP, any reference of Table X should be changed into a reference 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 “accessCredentials = Ø → accessCredentials = calcu-
lated value”, for a given TP, means “change all occurrences in which the field accessCredentials has
not been assigned to a calculation of the value accessCredentials to a given value".
A.2 Physical layer
As per ISO 12813:2019, 5.5.2, all test purposes TP/PHY/OBU/Bx/yy defined in EN 15876-1 are
applicable for the conformity evaluation of OBE to CEN–DSRC based CCC as defined in ISO 12813:2019,
Table B.8, Item 1.
A.3 MAC and LLC
As per ISO 12813:2019, 5.5.2, all test purposes TP/MAC/OBU/Bx/yy (except TP/MAC/OBU/BV/09, see
NOTE) and TP/LLC/OBU/Bx/yy defined in EN 15876-1 are applicable for the conformity evaluation of
OBE to CEN–DSRC based CCC as defined in ISO 12813:2019, Table B.8, Item 1.
NOTE Test purpose TP/MAC/OBU/BV/09 has been excluded from this document as this TP does not apply
for profiles 0/1 of EN 13372.
ISO 13143-1:2020(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 OBE, is described in Table A.2.
Table A.2 — BST general structure
Length Allowed values
T-APDUs 4 bits '1000' indicating initialisation-request (BST)
Option indicator 1 bit (nonmandApplications opt.) 0/1
RSE manufacturerid 16 bits As per 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 As per Profile in EN 13372:2004, 6.3.2
MandAp- 1 bit (mandApplications ext.) 0 (= no extension)
plications
7 bits (number of applications) M
CCC  1 bit (eid opt.) 0 (= eid not present)
application
1 bit (parameter opt.) 0 (= parameter not present)
Aid 1 bit (aid ext.) 0 (= no extension)
5 bits 20 (= CCC application)
Applica-
tion 2
1 bit (eid opt.) 0/1
(not CCC)
1 bit (parameter opt.) 0/1
Aid 1 bit (aid ext.) 0 (= no extension)
5 bits ≠ 20 (= no CCC application)
Eid 1 bit (eid ext.) 0 (= no extension)
7 bits Any
parameter Refer to ApplicationContextMark
as per EN 12834:2003, Annex A
... ... ...
Application
M
1 bit (eid opt.) 0/1
(not CCC)
1 bit (parameter opt.) 0/1
Aid 1 bit (aid ext.) 0 (= no extension)
5 bits ≠ 20 (= no CCC application)
Eid 1 bit (eid ext.) 0 (= no extension)
7 bits Any
parameter Refer to ApplicationContextMark as per
EN 12834:2003, Annex A
Nonmand 1 bit (mandApplications ext.) 0 (= no extension)
Applica-
7 bits (number of applications) N
tions
Application 1 See “Application 2 (not CCC)” of mandApplications
(not CCC)
... ...
Application N See “Application 2 (not CCC)” of mandApplications
(not CCC)
profileList 1 bit (profileList ext.) 0 (= no extension)
8 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
Table A.2 (continued)
Length Allowed values
7 bits (number of profiles) K
Profile 1 1 bit (Profile ext.) 0 (= no extension)
7 bits Refer to Profile as per EN 12834:2003, Annex A
and EN 13372:2004, 6.3.2
... ... ...
Profile K 1 bit (Profile ext.) 0 (= no extension)
7 bits Refer to Profile as per EN 12834:2003, Annex A
and EN 13372:2004, 6.3.2
A.4.1.2 VST
The general structure for a VST indicating one CCC-application as is transmitted by the OBE is described
in Table A.3.
Table A.3 — VST1 (security level 1): valid VST indicating one CCC application
Length Allowed value
Fill 4 bits Any
1 bit (Profile ext.) 0 (= no extension)
Profile
Refer to Profile as per
7 bits
EN 12834:2003, 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) As per ISO 3166-1
Contract
Provider
14 bits (IssuerIdentifier) As per ISO 14816
CCC- typeOf
16 bits Any
CCC
ContextMark Contract
application
Applications 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
AC_Master
8 bits Any
KeyRef
AC_CR-
Reference
AC_CR-
8 bits Any
Diversifier
1 bit (Container ext.) 0 (= no extension)
ISO 13143-1:2020(E)
Table A.3 (continued)
Length Allowed value
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
1 bit (eid opt.) 0/1
1 bit (parameter opt.) 0/1
1 bit (aid ext.) 0 (= no extension)
Refer to DSRCApplicationEntit-
aid
5 bits yID,
Application 2
as per EN 12834:2003, Annex A
1 bit (eid ext.) 0 (= no extension)
eid
7 bits Any (≠ other eid used in this VST)
Refer to ApplicationContextMark,
parameter
as per EN 12834:2003, Annex A
…
1 bit (eid opt.) 0/1
1 bit (parameter opt.) 0/1
1 bit (aid ext.) 0 (= no extension)
Refer to DSRCApplicationEntit-
aid
Application M 5 bits yID,
as per EN 12834:2003, Annex A
1 bit (eid ext.) 0 (= no extension)
eid
7 bits Any (≠ other eid used in this VST)
Refer to
parameter ApplicationContextMark,
as per 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
The general structure for a VST indicating two CCC applications as is optionally transmitted by the OBE
is described in Table A.4.
VST2 shall indicate the presence of two CCC applications with the following definitions (refer to
ISO 12813:2019, 8.2.3):
— one CCC application shall conform to ISO 12813:2019; and
— the other CCC application shall conform to ISO 12813:2015.
NOTE Evaluation of conformance with ISO 12813:2015 is outside the scope of this document.
Table A.4 — VST2 (security level 1) — Valid VST indicating two CCC applications
Length Allowed value
Fill 4 bits Any
1 bit (Profile ext.) 0 (= no extension)
Profile
Refer to Profile as per
7 bits
EN 12834:2003, Annex A
1 bit (applications ext.) 0 (= no extension)

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

1 bit (parameter opt.) 1 (= parameter present)
10 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
Table A.4 (continued)
Length Allowed value
1 bit (aid ext.) 0 (= no extension)
aid
5 bits 20 (= CCC application)
1 bit (eid ext.) 0 (= no extension)
eid
7 bits Any
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) As per ISO 3166-1
Contract
Provider
14 bits (IssuerIdentifier) As per ISO 14816
CCC TypeOf
Applications CCC- 16 bits Any
application1 Contract
ContextMark1
1 bit (contextVersion ext.) 0 (= no extension)
context
para
Version
7 bits Any
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
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
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 ≠ eid of CCC application1
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) As per ISO 3166-1
Contract
Provider
14 bits (IssuerIdentifier) As per ISO 14816
TypeOf
CCC- 16 bits Any
Contract
ContextMark2
1 bit (contextVersion ext.) 0 (= no extension)
context
CCC
Version
7 bits Any
application2
1 bit (Container ext.) 0 (= no extension)
para
7 bits (Container CHOICE) 2 (= OCTET STRING)
meter
1 bit (octet string ext.) 0 (= no extension)
7 bits (octet string length) 2
ISO 13143-1:2020(E)
Table A.4 (continued)
Length Allowed value
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
:::
1 bit (eid opt.) 1 (= eid present)

1 bit (parameter opt.) 0 (= parameter not present)
1 bit (aid ext.) 0 (= no extension)
Optional application M
aid
(non CCC-application)
5 bits ≠ 20
1 bit (eid ext.) 0 (= no extension)
eid
7 bits Any (≠ other eid used in this VST)
1 bit (obeStatus opt.) 1 (= obeStatus present)
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.5;
— Table A.6;
— Table A.7;
— Table A.8;
— Table A.9.
No other request commands are used by CCC application.
Fill bits shall always be set to zero.
Table A.5 — GET-Rq parameters (security level 1)
EN 12834:2003, Annex A ISO 14906:2018, Annex A EN 15509:2014, Table C.16
GET-Rq Fill =
Eid =
accessCredentials optional = mandatory
Iid optional prohibited
attributeIdList optional mandatory
12 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
Table A.6 — Action-Rq parameters for GET_STAMPED action (security level 1)
EN 12834:2003, Annex A ISO 14906:2018, Annex A EN 15509:2014, Table C.16 and
ISO 12813
ACTION-Rq Mode TRUE
Eid =
actionType 0 (GET_STAMPED)
=
accessCredentials optional mandatory
actionParameters optional GetStampedRq
Iid optional prohibited
Table A.7 — Action-Rq parameters for SET_MMI action
EN 12834:2003, Annex A ISO 14906:2018, Annex A EN 15509:2014, Table C.16 and
ISO 12813
ACTION-Rq Mode =
Eid 0
actionType 10 (SET_MMI)
=
accessCredentials optional prohibited
actionParameters optional SetMMIRq
Iid optional prohibited
Table A.8 — Action-Rq parameters for ECHO action
EN 12834:2003, Annex A ISO 14906:2018, Annex A EN 15509:2014, Table C.16 and
ISO 12813
ACTION-Rq Mode =
Eid 0
actionType 15 (ECHO)
=
accessCredentials optional prohibited
actionParameters optional mandatory
Iid optional prohibited
Table A.9 — EVENT-REPORT-Rq parameters
EN 12834:2003, Annex A ISO 14906:2018, Annex A EN 15509:2014, Table C.16 and
ISO 12813
EVENT-RE- Mode =
PORT-Rq
Eid 0
eventType 0 (release)
=
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 response APDUs:
— Table A.10;
— Table A.11;
— Table A.12;
ISO 13143-1:2020(E)
— Table A.13.
No other request commands are used by CCC application.
Fill bits shall always be set to zero.
Table A.10 — GET-Rs parameters
EN 12834:2003, Annex A ISO 14906:2018, EN 15509:2014, Table C.16
Annex A
GET-Rs Fill =
Eid =
Iid optional = prohibited
attributeList optional mandatory
Ret optional mandatory
Table A.11 — Action-Rs parameters for GET_STAMPED action
EN 12834:2003, Annex A ISO 14906:2018, EN 15509:2014, Table C.16 and
Annex A ISO 12813
ACTION-Rs Fill =
Eid =
Iid optional = prohibited
responseParameter optional mandatory
Ret optional mandatory
Table A.12 — Action-Rs parameters for SET_MMI action
EN 12834:2003, Annex A ISO 14906:2018, EN 15509:2014, Table C.16 and
Annex A ISO 12813
ACTION-Rs Fill =
Eid 0
Iid optional = prohibited
responseParameter optional prohibited
Ret optional mandatory
Table A.13 — Action-Rs parameters for ECHO action
EN 12834:2003, Annex A ISO 14906:2018, EN 15509:2014, Table C.16 and
Annex A ISO 12813
ACTION-Rs Fill =
Eid 0
Iid optional = prohibited
responseParameter optional conditional (present when ret = 0)
Ret optional mandatory
A.4.3 Application I-kernel TPs for OBE, security level 1
A.4.3.1 General
These TPs apply to security level 1 as defined in ISO 12813:2019, Table B.6, Item 1 and to initialisation
and termination processes defined in ISO 12813:2019, Table B.7, Items 1 and 5.
14 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
A.4.3.2 Data structures
For the purpose of this conformance test, the following BSTs described in
— Table A.14, and
— Table A.15
are transmitted to the DUT. Invalid values are indicated in boldface.
Table A.14 — BST1 (actual BST used, BV) valid BST
Length Value
Option indicator 1 bit (nonmandApplications opt.) 0 (= nonmandApplications not
present)
RSE manufacturerid 16 bits Registered value
individualid 27 bits Any
Time 32 bits Any
profile 1 bit (Profile ext.) 0 (= no extension)
7 bits 0
MandApplications 1 bit (mandApplications ext.) 0 (= no extension)
7 bits (number of applications) 1
CCC 1 bit (eid opt.) 0 (= eid not present)
application
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.15 — 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)
RSE manufacturerid 16 bits Registered value
individualid 27 bits Any
Time 32 bits Any
profile 1 bit (Profile ext.) 0 (= no extension)
7 bits 0
MandApplications 1 bit (mandApplications ext.) 0 (= no extension)
7 bits (number of applications) 1
Application #1 1 bit (eid opt.) 1 (= eid present)
(not CCC)
1 bit (parameter opt.) 0 (= parameter not present)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits ≠ 20 (AID that is not supported by the
OBE)
eid 1 bit (eid ext.) 0 (= no extension)
7 bits Any
nonmandApplications 1 bit (nonmandApplications ext.) 0 (= no extension)
7 bits (number of applications) 1
CCC 1 bit (eid opt.) 0 (= eid not present)
application
1 bit (parameter opt.) 0 (= parameter not present)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits 20 (= CCC application)
ISO 13143-1:2020(E)
Table A.15 (continued)
Length Value
profileList 1 bit (profileList ext.) 0 (= no extension)
7 bits (number of profiles) 0 (= list empty)
A.4.3.3 BV test purposes
Test subgroup objective:
a) to test the behaviour of the DUT in relation to:
— valid BST, and
— valid EVENT-REPORT-Rq (Release).
b) to test the DUT support of:
— BeaconId,
— Time,
— Profile,
— Applications, and
— LID.
Table A.16 — TP/AP BAS/OBU/BV/01
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:2019, 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.
Table A.17 — TP/AP BAS/OBU/BV/02
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:2019, 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.
Table A.18 — TP/AP BAS/OBU/BV/03
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:2019, 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.
16 © ISO 2020 – All rights reserved

ISO 13143-1:2020(E)
Table A.19 — TP/AP BAS/OBU/BV/04
TP/A
...