SIST EN ISO 13140:2025

SLOVENSKI STANDARD
01-oktober-2025
Nadomešča:
SIST EN ISO 13140-1:2017
Elektronsko pobiranje pristojbin - Vrednotenje skladnosti opreme v vozilu in
obcestni napravi s standardom ISO 13141 (ISO 13140:2025)
Electronic fee collection - Evaluation of on-board and roadside equipment for conformity
to ISO 13141 (ISO 13140:2025)
Elektronische Gebührenerhebung - Bewertung der Konformität fahrzeuginterner und
straßenseitiger Ausrüstung nach ISO 13141 (ISO 13140:2025)
Perception de télépéage - Évaluation des équipements embarqués et en bord de route
quant à la conformité avec ISO 13141 (ISO 13140:2025)
Ta slovenski standard je istoveten z: EN ISO 13140:2025
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 13140
EUROPEAN STANDARD
NORME EUROPÉENNE
July 2025
EUROPÄISCHE NORM
ICS 03.220.20; 35.240.60 Supersedes EN ISO 13140-1:2016
English Version
Electronic fee collection - Evaluation of on-board and
roadside equipment for conformity to ISO 13141 (ISO
13140:2025)
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 ISO 13141 (ISO 13140:2025) Ausrüstung nach ISO 13141 (ISO 13140:2025)
This European Standard was approved by CEN on 5 March 2025.

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, Türkiye 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
© 2025 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 13140:2025 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 13140:2025) 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 January 2026, and conflicting national standards shall
be withdrawn at the latest by January 2026.
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 13140-1:2016.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN website.
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, Türkiye and the
United Kingdom.
Endorsement notice
The text of ISO 13140:2025 has been approved by CEN as EN ISO 13140:2025 without any modification.

International
Standard
ISO 13140
First edition
Electronic fee collection —
2025-07
Evaluation of on-board and
roadside equipment for conformity
to ISO 13141
Perception de télépéage — Évaluation des équipements embarqués
et en bord de route quant à la conformité avec ISO 13141
Reference number
ISO 13140:2025(en) © ISO 2025
ISO 13140:2025(en)
© ISO 2025
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 13140:2025(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Conformance . 3
6 Test suite structure . 3
6.1 Structure .3
6.2 Reference to conformance test specifications . .3
6.3 Test purposes .4
6.3.1 TP definition conventions .4
6.3.2 TP naming conventions .4
Annex A (normative) Test purposes for on-board equipment . 6
Annex B (normative) Test purposes for roadside equipment .21
Annex C (normative) PCTR proforma for on-board equipment.27
Annex D (normative) PCTR proforma for roadside equipment .33
Bibliography .38

iii
ISO 13140:2025(en)
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 document 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).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
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 first edition cancels and replaces the first edition (ISO 13140-1:2016), which has been technically
revised.
The main changes are as follows:
— as a result of the withdrawal of ISO 13140-2, the title of this document has been updated.
— amendments have been made to reflect changes to ISO 13141, which makes reference to ISO 17573-3 as
the primary source of data specifications;
— terms and definitions have been updated and ISO/TS 17573-2 has been included as the primary source
for harmonized terminology across electronic fee collection (EFC) standards.
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 13140:2025(en)
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. For
this purpose, an autonomously operating OBE needs real-time and precise information about its location.
Location information is provided by satellite-based systems, optionally supported by on-board sensors.
Occasionally, location information can also be provided by fixed roadside infrastructure, by means of DSRC-
based localization augmentation communication (LAC).
This document specifies the process and tests for evaluation of OBE and roadside equipment (RSE) for
conformity to ISO 13141.
ISO 13141 specifies requirements for dedicated short-range communication (DSRC) between OBE and an
interrogator for the purpose of localization augmentation. 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 at different locations and
at different times;
— facilitate communications between parties.

v
International Standard ISO 13140:2025(en)
Electronic fee collection — Evaluation of on-board and
roadside equipment for conformity to ISO 13141
1 Scope
This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of
on-board equipment (OBE) and roadside equipment (RSE) to ISO 13141.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment to
support interoperability between different equipment supplied by different manufacturers.
ISO 13141 specifies requirements for the localization augmentation communication (LAC) interface level, but
not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and 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 code
ISO 13141:2024, Electronic fee collection — Localization augmentation communication for autonomous systems
ISO 14816, Road transport and traffic telematics — Automatic vehicle and equipment identification —
Numbering and data structure
ISO 14907-2:2021, Electronic fee collection — Test procedures for user and fixed equipment — Part 2:
Conformance test for the on-board unit application interface
ISO/TS 17573-2, Electronic fee collection — System architecture for vehicle related tolling — Part 2: Vocabulary
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:2023, Electronic fee collection — Interoperability application profile for DSRC
EN 15876, Electronic fee collection — Evaluation of on-board and roadside equipment for conformity to
EN 15509
ETSI/TS 102 486-2-2:2008, 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 terms and definitions given in ISO/TS 17573-2 and the following apply.

ISO 13140:2025(en)
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
protocol implementation conformance statement
PICS
implementation conformance statement (ICS) for an implementation or system claimed to conform to a
given protocol specification
[SOURCE: ISO/IEC 9646-1:1994, 3.3.80, modified — grammar and syntax updated.]
4 Abbreviated terms
AC_CR access credentials
APDU application protocol data unit
ATS abstract test suite
BI behaviour invalid (i.e. invalid behaviour tests)
BST beacon service table
BV behaviour valid (i.e. valid behaviour tests)
DLC data link control
DSRC dedicated short-range communication
DUT device under test
EID element identifier
EFC electronic fee collection
ICS implementation conformance statement
LLC logical link control
MAC medium access control
PCTR protocol conformance test report
PDU protocol data unit
PICS protocol implementation conformance statement
PIXIT protocol implementation extra information for testing
SCTR system conformance test report
T-APDU transfer-application protocol data unit
TP test purpose
TP-ID test purpose identifier
TSS test suite structure
ISO 13140:2025(en)
VST vehicle service table
5 Conformance
The conformance tests shall be performed as specified in Annex A and Annex B for OBE and RSE respectively.
The conformity assessment body of the OBE and RSE, respectively, is responsible for providing a conformance
test report.
The conformity assessment body of the OBE shall complete the protocol conformance test report (PCTR) for
the OBE as specified in Annex C.
The conformity assessment body of the RSE shall complete the PCTR for the RSE as specified in Annex D.
NOTE The PCTR forms a basis for the manufacturer’s declaration of conformity.
6 Test suite structure
6.1 Structure
Table 1 shows the TSS including its subgroups that are inherited from other specifications.
Table 1 — Test Suite Structure
Group Type of DUT Behaviour
Physical layer OBE Valid behaviour (BV)
Invalid behaviour (BI)
RSE BV
BI
Data link control (DLC) OBE BV
Medium access control (MAC)
BI
sublayer
RSE BV
BI
DLC OBE BV
Logical link control (LLC)
BI
sublayer
RSE BV
BI
Application layer OBE BV
BI
RSE BV
BI
Physical layer tests shall be performed in a radio wave laboratory.
6.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 LAC 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 cases by applying some
restrictions or choices in elements such as the parameters values, according to what is stated in the profile
standard. Specific conformance test cases for the LAC application are identified for statements contained in
the LAC application, which have no equivalence in the base standards. These latter cases cover, for example,

ISO 13140:2025(en)
the application layer data test purposes. This document considers existing test purposes for conformance to
the base standards by referencing them, so that:
a) for test purposes that are identical to those specified in the base standards conformance test cases (see
e.g. ETSI/TS 102 486-2-2 or EN 15876), a direct reference is reported;
NOTE For the reader’s convenience, in the TPs the title or a verbal description of the referenced test purpose
is provided, together with the reference to EN 15876.
b) for test purposes that are derived from those specified 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 provided.
An indication of whether a test purpose is identical, derived or specific is given in each test purpose.
6.3 Test purposes
6.3.1 TP definition conventions
The TPs are specified following the rules shown in Table 2.
Table 2 — TP specification rules
TP-ID according to the TP naming Title
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 conventions
defined in 6.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 specified in another test standard, derived from a
TP specified in another test standard, or specific for this standard profile.
Initial condition The condition specifies the required initial state of the device under test (DUT) at the
time of launching of the actual TP.
Stimulus and expected Specification of the events the tester performs, and the events that are expected from
behaviour the DUT to conform to the base specification.
6.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///–
TP: to indicate that it is a TP;
: to which group among those specified in Table 1 the TP applies;
: type of DUT (i.e. OBE or RSE);
X: type of testing (i.e. valid behaviour tests — BV, or invalid behaviour tests — BI);
: sequential TP number (01-99).

ISO 13140:2025(en)
The naming conventions are as described in Table 3.
Table 3 — TP naming convention

applicable for OBE/RSE PHY Physical layer
applicable for OBE/RSE MAC/LLC MAC/LLC sublayer
applicable for OBE/RSE AP-BAS Application layer — I Kernel support
applicable for OBE AP-FUN Application layer — T Kernel support
applicable for OBE AP-DAT Application layer — Data attributes support
applicable for OBE AP-SEC Application layer — Security Level 1 support
applicable for RSE AP-SET Application layer — SET-rq PDU test purposes,
applicable for RSE AP-REL Application layer — EVENT-REPORT-rq PDU test purposes

ISO 13140:2025(en)
Annex A
(normative)
Test purposes for on-board equipment
A.1 General
A.1.1 Content
This annex contains the TPs for the conformity evaluation of OBE to ISO 13141.
A.1.2 Symbols in TP descriptions
For the application layer test purposes (see A.4), a special notation and symbol convention is used, as
specified in 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 TP A “is congruent to” TP B. The notation TP A ≡ TP B means that the TP A is
the same as TP 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 TP, any
reference of Table X should be changed into references to Table Y.
= Means “assignment”. So, 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 = calculated 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
In accordance with ISO 13141:2024, 5.5.2, all test purposes TP/PHY/OBE/Bx/yy specified in EN 15876 shall
be applicable for the conformity evaluation of OBE to CEN–DSRC based LAC as specified in ISO 13141:2024,
Table B.8, Item 1.
A.3 MAC and LLC
In accordance with ISO 13141:2024, 5.5.2, all test purposes TP/MAC/OBE/Bx/yy and TP/LLC/OBE/Bx/yy
specified in EN 15876 shall be applicable for the conformity evaluation of OBE to CEN–DSRC based LAC as
specified in ISO 13141:2024, Table B.8, Item 1.

ISO 13140:2025(en)
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, shall be in accordance with Table A.2.
Table A.2 — BST general structure
Length Allowed values
“1 000” indicating
T-APDUs 4 bit
initialization-request (BST)
1 bit (nonmandApplications
Option indicator 0/1
opt.)
manufacturerId 16 bits In accordance with ISO 14816
rsu
as specified by
individualId 27 bits
manufacturer
time 32 bits UNIX real time
1 bit (Profile ext.) 0 (= no extension)
In accordance with profile in
profile
7 bits EN 12834:2003, Annex A
and EN 13372:2004, 6.3.2.
1 bit (mandApplications ext.) 0 ( = no extension)

7 bits (number of M
applications)
LAC 1 bit (eid opt.) 0 (= eid not present)

Application
1 bit (parameter opt.) 0 (= parameter not present)
1 bit (aid ext.) 0 (= no extension)
aid
5 bits 21 (= LAC application)
Application 2 1 bit (eid opt.) 0/1

(not LAC)
1 bit (parameter opt.) 0/1
1 bit (aid ext.) 0 (= no extension)
aid
5 bits any (≠ LAC application)
1 bit (eid ext.) 0 (= no extension)
eid
Mand
7 bits any
Applications
ApplicationContextMark
parameter in accordance with
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
5 bits any (≠ LAC application)

1 bit (eid ext.) 0 (= no extension)
eid
7 bits any
ApplicationContextMark in ac-
parameter cordance with EN 12834:2003,
Annex A
ISO 13140:2025(en)
TTabablele A A.22 ((ccoonnttiinnueuedd))
Length Allowed values
1 bit (mandApplications ext.) 0 (= no extension)
7 bits (number of Can be in the range of 0 . N,

applications) provided the maximum frame-
length is not exceeded.
nonmand
Application 1 In accordance with “Application 2 (not EFC)” of mandApplications
Applications
(not EFC)
... ...
Application N In accordance with “Application 2 (not EFC)” of mandApplications
(not EFC)
1 bit (profileList ext.) 0 (= no extension)

7 bits (number of profiles) K
Profile 1 1 bit (Profile ext.) 0 (= no extension)
7 bits Profile in accordance with
EN 12834:2003, Annex A
and EN 13372:2004, 6.3.2.
... ... ...
Profile K 1 bit (Profile ext.) 0 (= no extension)
7 bits Profile in accordance with
EN 12834:2003, Annex A
and EN 13372:2004, 6.3.2.
A.4.1.2 VST
The VST general structure, as is transmitted by the OBE, shall be in accordance with 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 in accordance with
profile
7 bits EN 12834:2003,
Annex A
1 bit (applications ext.) 0 (= no extension)
Can be in the range of 0.M depend-

ing on OBE support and provided
7 bits (number of applic.)
the maximum frame-length is not
exceeded.
1 bit (eid opt.) 1 (= eid present)

1 bit (parameter opt.) 1 (= parameter present)
1 bit (aid ext.) 0 (= no extension)
aid
5 bits 21 (= LAC 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

ISO 13140:2025(en)
TTabablele A A.33 ((ccoonnttiinnueuedd))
Length Allowed value
10 bits (CountryCode) In accordance with ISO 3166-1
contract
Provider
14 bits (IssuerIdentifier) In accordance with ISO 14816
LAC- typeOf
16 bits any
LAC
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
1 bit (eid opt.) 0/1
1 bit (parameter opt.) 0/1
1 bit (aid ext.) 0 (= no extension)
In accordance with DSRCApplica-
aid
5 bits tionEntityID,
Application 2
EN 12834:2003, Annex A
1 bit (eid ext.) 0 (= no extension)
eid
7 bits any (≠ other eid used in this VST)
ApplicationContextMark in accord-
parameter
ance with EN 12834:2003, Annex A

… 1 bit (eid opt.) 0/1
1 bit (parameter opt.) 0/1
1 bit (aid ext.) 0 (= no extension)
DSRCApplicationEntityID in
aid
5 bits accordance with EN 12834:2003,

Annex A
Application M
1 bit (eid ext.) 0 (= no extension)
eid
7 bits any (≠ other eid used in this VST)

ApplicationContextMark in accord-
parameter
ance with 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
Request APDUs shall be as specified in Table A.4 and Table A.5.
No other request commands are used by LAC application.
Fill bits shall always be set to zero.

ISO 13140:2025(en)
Table A.4 — SET-Rq parameters (security level 1)
EN 12834:2003, Annex A EN 15509:2023, Table B.18
fill =
mode =
eid =
SET-Rq
accessCredentials optional mandatory
attrList =
iid optional prohibited
Table A.5 — EVENT-REPORT-Rq parameters
EN 12834:2003, Annex A EN 15509:2023, Table B.22
and ISO 13141
mode false
eid 0
eventType 0 (release)
EVENT-REPORT-Rq
accessCredentials optional prohibited
eventParameters optional prohibited
iid optional prohibited
A.4.2.2 Parameters of response PDUs
Response APDUs shall be as specified in Table A.6.
No other response APDUs are used by the LAC application.
Fill bits shall always be set to zero.
Table A.6 — SET-Rs parameters (security level 1)
EN 12834:2003, Annex A EN 15509:2023, Table B.19
fill =
eid =
SET-Rs
iid optional prohibited
ret optional mandatory
A.4.3 Application I-kernel TPs for OBE, security level 1
A.4.3.1 General
TPs specified in Clause A.4.3 apply to the security level 1 as specified in ISO 13141:2024, Table B.6, Item 1
and to initialization and termination as specified in ISO 13141:2024, Table B.7, Items 1 and 5.
A.4.3.2 Data structures
For the purpose of this conformance test, the following BSTs specified in
— Table A.7 for a valid BST used in BV TPs; and
— Table A.8 for an invalid BST used in BI TPs
shall be transmitted to the DUT.
NOTE BST2 contains erroneous parameters in form of a LAC application inserted as non-mandatory application.

ISO 13140:2025(en)
Table A.7 — BST1
Length Value
Option indicator 1 bit (nonmandApplications opt.) 0 (= nonmandApplications not pres-
ent)
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
Mand  1 bit (mandApplications ext.) 0 (= no extension)
Applications
7 bits (number of applications) 1
LAC  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 21 (= LAC application)
profileList 1 bit (profileList ext.) 0 (= no extension)
7 bits (number of profiles) 0 (= list empty)
Table A.8 — BST2
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
Mand  1 bit (mandApplications ext.) 0 (= no extension)
Applications
7 bits (number of applications) 1
Application  1 bit (eid opt.) 1 (= eid present)
#1 (not LAC)
1 bit (parameter opt.) 0 (= parameter not present)
aid 1 bit (aid ext.) 0 (= no extension)
5 bits ≠ 21 (AID that is not supported
by the OBE)
eid 1 bit (eid ext.) 0 (= no extension)
7 bits any
nonmand  1 bit (nonmandApplications ext.) 0 (= no extension)
Applications
7 bits (number of applications) 1
LAC  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 21 (= LAC application)
profileList 1 bit (profileList ext.) 0 (= no extension)
7 bits (number of profiles) 0 (= list empty)

ISO 13140:2025(en)
A.4.3.3 BV test purposes
The test subgroup objectives are:
a) to test the behaviour of the DUT in relation to:
— valid BST;
— valid EVENT-REPORT-Rq (Release);
b) to test the DUT support of:
— BeaconId;
— Time;
— Profile;
— Applications;
— LID.
TPs to assess conformity of Application I-kernel functions for OBE, security level 1, for valid behaviour shall
be performed as specified are specified in Tables A.9 to A.14.
NOTE Test purposes with IDs TP/AP-BAS/OBE/BV/04 to TP/AP-BAS/OBE/BV/08 have not been used in this
document to apply a TP numbering consistent with ETSI/TS 102 486-2-2.
Table A.9 — TP/AP BAS/OBE/BV/01
TP/AP-BAS/OBE/BV/01 Receive and manage INITIALIZATION.request (BST)
TP origin Identical to TP/AL-I/OBU/BV/01 in ETSI/TS 102 486-2-2-V1.2.1
(2008-10), 5.4.1
Reference ISO 13141:2024, 7.2.2
Initial condition In accordance with TP/AL-I/OBU/BV/01 in ETSI/TS 102 486-2-2:2008 , 5.4.1
Stimulus and expected behav- In accordance with TP/AL-I/OBU/BV/01 in ETSI/TS 102 486-2-2:2008, 5.4.1.
iour
Table A.10 — TP/AP BAS/OBE/BV/02
TP/AP-BAS/OBE/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:2008, 5.4.1
Reference ISO 13141:2024, 7.2.4
Initial condition In accordance with TP/AL-I/OBE/BV/02 in ETSI/TS 102 486-2-2:2008, 5.4.1
Stimulus and expected behav- In accordance with TP/AL-I/OBE/BV/02 in ETSI/TS 102 486:2008, 5.4.1.
iour
Table A.11 — TP/AP BAS/OBE/BV/03
TP/AP-BAS/OBE/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:2008, 5.4.1
Reference ISO 13141:2024, 7.2.2
Initial condition Identical to TP/AL-I/OBU/BV/03 in ETSI/TS 102 486-2-2:2008, 5.4.1
Stimulus and expected behav- In accordance with TP/AL-I/OBU/BV/03 in ETSI/TS 102 486-2-2:2008, 5.4.1.
iour
ISO 13140:2025(en)
Table A.12 — TP/AP BAS/OBE/BV/04
TP/AP-BAS/OBE/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:2008, 5.4.1
Reference ISO 13141:2024, 7.2.2
Initial condition Identical to TP/AL-I/OBU/BV/04 in ETSI/TS 102 486-2-2:2008, 5.4.1
Stimulus and expected behav- In accordance with TP/AL-I/OBU/BV/04 in ETSI/TS 102 486-2-2:2008, 5.4.1.
iour
Table A.13 — TP/AP BAS/OBE/BV/09
TP/AP-BAS/OBE/BV/09 Manage profile selection
TP origin Identical to TP/AL-I/OBU/BV/09 in ETSI/TS 102 486-2-2:2008, 5.4.1
Reference ISO 13141:2024, 7.2.2
Initial condition In accordance with TP/AL-I/OBU/BV/09 in ETSI/TS 102 486-2-2:2008, 5.4.1
Stimulus and expected behav- In accordance with TP/AL-I/OBU/BV/09 in ETSI/TS 102 486-2-2:2008, 5.4.1.
iour
Table A.14 — TP/AP BAS/OBE/BV/10
TP/AP-BAS/OBE/BV/10 Verify that the DUT replies to a BST with a VST
TP origin Specific
Reference ISO 13141:2024, 7.2.2
Initial condition DUT not in sleep mode and not yet initialized
Stimulus and expected behav- Tester DUT
iour
BST1
1 ⇒
VST
2 ⇐
Verify length and allowed
values of VST (in accordance
with Table A.3)
IF verification performed in
step 3 was not successful
THEN TP failed
A.4.3.4 BI test purposes
The test subgroup objectives are:
— to check the behaviour of the DUT in response to invalid messages.
TPs to assess conformity of Application I-kernel functions for OBE, security level 1, for invalid behaviour
shall be performed as specified in Tables A.15 to A.17.
Table A.15 — TP/AP BAS/OBE/BI/01
TP/AP-BAS/OBE/BI/01 Manage profile selection
TP origin Identical to TP/AL-I/OBU/BI/01 in ETSI/TS 102 486-2-2:2008, 5.4.2
Reference ISO 13141:2024, 7.2.2
Initial condition In accordance with TP/AL-I/OBU/BI/01 in ETSI/TS 102 486-2-2:2008, 5.4.2
Stimulus and expected behav- In accordance with TP/AL-I/OBU/BI/01 in ETSI/TS 102 486-2-2:2008, 5.4.2.
iour
ISO 13140:2025(en)
Table A.16 — TP/AP BAS/OBE/BI/02
TP/AP-BAS/OBE/BI/02 Manage applications
TP origin Identical to TP/AL-I/OBU/BI/02 in ETSI/TS 102 486-2-2:2008, 5.4.2
Reference ISO 13141:2024, 7.2.2
Initial condition In accordance with TP/AL-I/OBU/BI/02 in ETSI/TS 102 486-2-2:2008, 5.4.2
Stimulus and expected behav- In accordance with TP/AL-I/OBU/BI/02 in ETSI/TS 102 486-2-2:2008, 5.4.2.
iour
Table A.17 — TP/AP BAS/OBE/BI/03
TP/AP-BAS/OBE/BI/03 Verify that the DUT handles BST with LAC application marked as
non-mandatory application
TP origin Specific
Reference ISO 13141:2024, 7.2.2
Initial condition DUT not in sleep mode and not yet initialized
Stimulus and expected behav- Tester DUT
iour
BST2
1 ⇒
Verify that DUT does
not initialize with
INITIALIZATION-response
(VST).
IF verification performed
in step 3 was not
successful THEN TP failed
A.4.4 Application T-kernel test purposes for OBE
A.4.4.1 General
These TPs apply to the layer 7 functions related to T-kernel in accordance with ISO 13141:2024, Table B.7,
Items 1, 2 and 5.
A.4.4.2 BV test purposes
The test subgroup objective is:
— to test the behaviour of the DUT in relation to syntactically and contextual correct behaviour of the
test system.
TPs to assess conformity of Application T-kernel functions for OBE for valid behaviour shall be performed as
specified in Tables A.18 to A.22.
Table A.18 — TP/AP FUN/OBE/BV/02
TP/AP-FUN/OBE/BV/02 Receive SET.request and manage SET.response with LID = private
TP origin Identical to TP/AL-T/OBU/BV/02 in ETSI/TS 102 486-2-2:2008, 5.2.1
Reference ISO 13141:2024, 7.2.3
Initial condition In accordance with TP/AL-T/OBU/BV/02 in ETSI/TS 102 486-2-2:2008, 5.2.1
Stimulus and expected behav- In accordance with TP/AL-T/OBU/BV/02 in ETSI/TS 102 486-2-2:2008, 5.2.1.
iour
NOTE Request with accessCredentials.

ISO 13140:2025(en)
Table A.19 — TP/AP FUN/OBE/BV/13
TP/AP-FUN/OBE/BV/13 Receive and manage non-fragmented APDUs with random PDU number
TP origin Identical to TP/AL-T/OBU/BV/13 in ETSI/TS 102 486-2-2:2008, 5.2.1
Reference ISO 13141:2024, 7.2.3
Initial condition In accordance with TP/AL-T/OBU/BV/13 in ETSI/TS 102 486-2-2:2008, 5.2.1
Stimulus and expected behav- In accordance with TP/AL-T/OBU/BV/13 in ETSI/TS 102 486-2-2:2008, 5.2.1.
iour
NOTE Request with accessCredentials for SET. TP is applicable for SET only.
Table A.20 — TP/AP FUN/OBE/BV/14
TP/AP-FUN/OBE/BV/14 Receive and manage multiplexed APDUs from two different applications
TP origin Identical to TP/AL-T/OBU/BV/14 in ETSI/TS 102 486-2-2:2008, 5.2.1
Reference ISO 13141:2024, 7.2.3
Initial condition In accordance with TP/AL-T/OBU/BV/14 in ETSI/TS 102 486-2-2:2008, 5.2.1
Stimulus and expected behav- In accordance with TP/AL-T/OBU/BV/14 in ETSI/TS 102 486-2-2:2008, 5.2.1.
iour
NOTE Request with accessCredentials for SET. TP is applicable for SET only.
Table A.21 — TP/AP FUN/OBE/BV/16
TP/AP-FUN/OBE/BV/16 Receive and manage concatenated and chained APDUs from a single appli-
cation
TP origin Identical to TP/AL-T/OBU/BV/16 in ETSI/TS 102 486-2-2:2008, 5.2.1
Reference ISO 13141:2024, 7.2.3
Initial condition In accordance with TP/AL-T/OBU/BV/16 in ETSI/TS 102 486-2-2:2008, 5.2.1
Stimulus and expected behav- In accordance with TP/AL-T/OBU/BV/16 in ETSI/TS 102 486-2-2:2008, 5.2.1.
iour
NOTE Request with accessCredentials for SET. TP is applicable for SET only.
Table A.22 — TP/AP FUN/OBE/BV/18
TP/AP-FUN/OBE/BV/18 Support of DSRC L7 SET
TP origin Identical to TC04-A in ISO 14907-2:2021, C.2.4
Reference ISO 13141:2024, 7.2.3
Initial condition In accordance with TC04-A in ISO 14907-2:2021, C.2.4
Stimulus and expected behav- In accordance with TC04-A in ISO 14907-2:2021, C.2.4.
iour
NOTE Request with accessCredentials.
A.4.4.3 BI test purposes
The test subgroup objective is:
— to check the behaviour of the of the DUT in response to invalid stimuli and behaviour from the test
tool. TPs to assess conformity of Application T-kernel functions for OBE for invalid behaviour shall be
performed as specified in Tables A.23 to A.26.
NOTE TPs with ID TP/AP-BAS/OBU/BI/05 have not been used in this document to apply a TP numbering consistent
with ETSI/TS 102 486-2-2.
ISO 13140:2025(en)
Table A.23 — TP/AP FUN/OBE/BI/02
TP/AP-FUN/OBE/BI/02 Receive and manage PDUs to broadcast kernel with awake but not
yet initialized OBE
TP origin Identical to TP/AL-T/OBU/BI/02 in ETSI/TS 102 486-2-2:2008, 5.2.2
Reference ISO 13141:2024, 7.2.2
Initial condition In accordance with TP/AL-T/OBU/BI/02 in ETSI/TS 102 486-2-2:2008, 5.2.2
Stimulus and expected behav- In accordance with TP/AL-T/OBU/BI/02 in ETSI/TS 102 486-2-2:2008, 5.2.2.
iour
Table A.24 — TP/AP FUN/OBE/BI/03
TP/AP-FUN/OBE/BI/03 Receive and manage non-fragmented PDUs with wrong fragment
counter value with initialized OBE
TP origin Identical to TP/AL-T/OBU/BI/03 in ETSI/TS 102 486-2-2:2008, 5.2.2
Reference ISO 13141:2024, 7.2.3
Initial condition In accordance with TP/AL-T/OBU/BI/03 in ETSI/TS 102 486-2-2:2008, 5.2.2
Stimulus and expected behav- In acc
...