SIST EN ISO 12855:2025/oprA1:2026

• Status: Not Published
• Public Enquiry End Date: 14-Oct-2026
• ICS: 03.220.20 - Road transport
• ICS: 35.240.60 - IT applications in transport
• Technical Committee: ITC - Information technology
• Current Stage: 4020 - Public enquire (PE) (Adopted Project)
• Start Date: 11-Aug-2026
• Due Date: 29-Dec-2026
• Ref Project: EN ISO 12855:2025/prA1 - Electronic fee collection - Information exchange between service provision and toll charging - Amendment 1 (ISO 12855:2025/DAM 1:2026)

• Amends: SIST EN ISO 12855:2025 - Electronic fee collection - Information exchange between service provision and toll charging (ISO 12855:2025)
• Effective Date: 12-Nov-2025

Overview

SIST EN ISO 12855:2025/oprA1:2026 is a draft amendment to the international standard ISO 12855:2025, focusing on Electronic Fee Collection (EFC) and the information exchange protocols between service providers and toll charging operators. This amendment, coordinated by CEN and ISO/TC 204, addresses updates and refinements to support interoperability and secure data transfer in road transport tolling systems. The standard aims to facilitate efficient, secure, and accurate electronic toll transactions, supporting modern Intelligent Transport Systems (ITS) and aligning with evolving technology and regulatory needs.

Key Topics

• Information Exchange Architecture: Specifies computational objects for information exchanges between Toll Chargers (TCs) and Toll Service Providers (TSPs), ensuring that each object is clearly identified by its name, functions, and associated data units.
• Data Integrity and Authentication: Enhances data element definitions for authentication, including the structure of digital signatures, certificate management, and methods to safeguard against data manipulation.
• Identification and Versioning: Refines identifiers for protocol versions, application data units, and user-related data to ensure precise data tracking and compatibility across multiple system versions.
• Flexible Data Structures: Updates tables and data elements to reflect advancements in identifiers, application payloads, attachments, and user/vehicle parameter requests.
• Security and Privacy: Adds and updates normative references to the latest security protocols like TLS and DTLS, ensuring compliance with up-to-date industry standards for transport layer security.
• User and Vehicle Data: Expands options for the collection and verification of user, contract, and vehicle parameters, enabling more customized tolling, billing, and user management processes.

Applications

The amendments introduced in SIST EN ISO 12855:2025/oprA1:2026 have significant practical value for organizations involved in the provision and management of electronic toll systems:

• Electronic Toll Collection Systems: Ensures seamless and secure data interchange between back-office systems, streamlining toll declaration, billing, payment claims, and enforcement procedures.
• Intelligent Transport Systems (ITS): Integrates with IT applications in transport, supporting interoperability between different national and regional tolling infrastructures.
• Road Transport Operators: Facilitates accurate billing and settlements across cross-border and multi-provider environments, supporting the European Electronic Toll Service (EETS) and similar frameworks.
• Service Providers/Operators: Enhances the ability to manage user contracts, complaints, vehicle data, and settlement information securely and efficiently.
• Policy Makers and Regulators: Provides a harmonized reference for preparing regulations or directives tied to electronic fee collection and road use charging.

Related Standards

When implementing the requirements of SIST EN ISO 12855:2025/oprA1:2026, the following standards and references are particularly relevant:

• ISO 12855:2025: The base standard for information exchange in electronic fee collection.
• EN 16986:2026: Guidance on interoperability requirements for European electronic toll services.
• ISO 19299:2020: Security framework for electronic fee collection, ensuring robust protection of transactional data.
• IETF RFCs such as RFC 6040, RFC 6347, RFC 8446, and RFC 9147: Cover secure communication protocols vital for protecting information exchanges (TLS, DTLS, Explicit Congestion Notification).
• ISO 17573-3: Reference for data elements related to user and provider identifiers, widely used across EFC systems.

By aligning with these standards, stakeholders can ensure that their EFC systems remain interoperable, secure, and compliant with European and international best practices, supporting smarter and more efficient road transport solutions.

SLOVENSKI STANDARD
01-oktober-2026
Elektronsko pobiranje pristojbin - Izmenjava informacij med ponudnikom in
operaterjem cestninjenja - Dopolnilo A1 (ISO 12855:2025/DAM 1:2026)
Electronic fee collection - Information exchange between service provision and toll
charging - Amendment 1 (ISO 12855:2025/DAM 1:2026)
Elektronische Gebührenerhebung - Informationsaustausch zwischen Dienstleistern und
Gebühreneinzugsunternehmen - Ergänzung 1 (ISO 12855:2025/DAM 1:2026)
Perception de télépéage - Échange d'informations entre la prestation de service et la
perception du péage - Amendement 1 (ISO 12855:2025/DAM 1:2026)
Ta slovenski standard je istoveten z: EN ISO 12855:2025/prA1
ICS:
03.220.20 Cestni transport Road transport
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
Amendment
ISO 12855:2025/
DAM 1
ISO/TC 204
Electronic fee collection —
Secretariat: ANSI
Information exchange between
service provision and toll charging
Voting begins on:
2026-07-31
AMENDMENT 1
Voting terminates on:
2026-10-23
Perception de télépéage — Échange d'informations entre la
prestation de service et la perception du péage
AMENDEMENT 1
ICS: 03.220.20; 35.240.60
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENTS AND APPROVAL. IT
IS THEREFORE SUBJECT TO CHANGE
AND MAY NOT BE REFERRED TO AS AN
INTERNATIONAL STANDARD UNTIL
PUBLISHED AS SUCH.
This document has not been edited by the ISO Central Secretariat.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
ISO/CEN PARALLEL PROCESSING
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
NATIONAL REGULATIONS.
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION.
Reference number
ISO 12855:2025/DAM 1:2026(en)
DRAFT
ISO 12855:2025/DAM 1:2026(en)
Amendment
ISO 12855:2025/
DAM 1
ISO/TC 204
Electronic fee collection —
Secretariat: ANSI
Information exchange between
service provision and toll charging
Voting begins on:
AMENDMENT 1
Voting terminates on:
Perception de télépéage — Échange d'informations entre la
prestation de service et la perception du péage
AMENDEMENT 1
ICS: 03.220.20; 35.240.60
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENTS AND APPROVAL. IT
IS THEREFORE SUBJECT TO CHANGE
AND MAY NOT BE REFERRED TO AS AN
INTERNATIONAL STANDARD UNTIL
PUBLISHED AS SUCH.
This document has not been edited by the ISO Central Secretariat.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
© ISO 2026
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
STANDARDS MAY ON OCCASION HAVE TO
ISO/CEN PARALLEL PROCESSING
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
BE CONSIDERED IN THE LIGHT OF THEIR
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
or ISO’s member body in the country of the requester.
NATIONAL REGULATIONS.
ISO copyright office
RECIPIENTS OF THIS DRAFT ARE INVITED
CP 401 • Ch. de Blandonnet 8
TO SUBMIT, WITH THEIR COMMENTS,
CH-1214 Vernier, Geneva
NOTIFICATION OF ANY RELEVANT PATENT
Phone: [phone]
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION.
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ISO 12855:2025/DAM 1:2026(en)
ii
ISO 12855:2025/DAM 1:2026(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 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).
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.
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.

iii
ISO 12855:2025/DAM 1:2026(en)
Electronic fee collection — Information exchange between
service provision and toll charging
AMENDMENT 1
1  Scope
Replace the last paragraph with the following text (in which “any complex transfers (transactions), i.e.
sequences of inter-related ADUs that can possibly involve several APDU exchanges has been removed”):
This document does not specify, amongst others:
— any communication between TC or TSP with any other involved party;
— any communication between elements of the TC and the TSP that is not part of the back-office
communication;
— interfaces for EFC systems for public transport;
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;
— definitions of service communication channels, protocols and service primitives to transfer the APDU.

2  Normative references
Amend the following normative reference from:
IETF RFC 6040, Tunnelling of Explicit Congestion Notification, February 2013
to:
IETF RFC 6040, Tunnelling of Explicit Congestion Notification, November 2010

Amend the following normative reference from:
ISO 19299, Electronic fee collection — Security framework
to:
ISO 19299:2020, Electronic fee collection — Security framework

Add the following references:
IETF RFC 6347, Datagram Transport Layer Security Version 1.2, January 2012
IETF RFC 9147, The Datagram Transport Layer Security (DTLS) Protocol Version 1.3, April 2022
IETF RFC 8446. The Transport Layer Security (TLS) Protocol Version 1.3, August 2018

ISO 12855:2025/DAM 1:2026(en)
IETF RFC 9601, Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim,
August 2024
4  Symbols and abbreviated terms
Add the following abbreviations:
IETF Internet Engineering Task Force
JSON JavaScript object notation
JWT JSON web token
LTPA lightweight third-party authentication
REST representational state transfer
RFC request for comments
SOAP simple objects access protocol
TCP/IP transmission control protocol/internet protocol
UDP/IP user datagram protocol/ internet protocol

6.1  Overview
Replace the first paragraph with the following:
This clause specifies the computational objects for the information exchanges between TCs and TSPs. Each
computational object is identified by:
— a name;
— the function(s) it performs and
— the ADU(s) it can generate or accept.

6.2.1  General
Replace Table 2 with the following:
Table 2 — Data elements of InfoExchange
Data element Data type/data description Status
infoExchangeContent M
InfoExchangeContent (see Table 3)
The data element shall contain the ADU(s) as content of the APDU.
infoExchangeAuthenticator
AuthenticatorEfc (see Table 16 and 7.3.2) O
The data element may optionally contain a calculated signature
over the data element infoExchangeContent. This signature can
be calculated either by the APDU originator or the information
sender (see 6.2.2).
Replace Table 3 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 3 — Data elements of InfoExchangeContent
Data element Data type/data description Status
Apci
ApciFields (see Table 4) M
The data element shall contain the APCI of the APDU specifying originator, sender and
recipient of the APDU, its relation to other APDUs and the version of the protocol.
Adus
Adus (see Table 7) M
The data element shall contain the ADUs as payload of the APDU.

Replace Table 4 with the following:
Table 4 — Data elements of ApciFields
Data element Data type/data description Status
aidIdentifier
AidIdentifier (see Table 5) specified as INTEGER ranging from 0 to M
This data element shall contain a reference to a protocol version
either based on a specific edition of this document or EN 16986 or in
association with the value of protocolIssuerId a private imple-
mentation specification with additional restrictions or extensions of
this document. Any change to a data specification shall be identified
by a different value in aidIdentifier.
Permitted values are specified in Table 5.
See 5.3 on the use of private values.
If a private value is specified, the indicated implementation specifi-
cation shall be compliant to all normative requirements specified in
a specific edition of this document or EN 16986. That edition shall be
stated in the indicated implementation specification.
apduOriginator
Provider (imported from ISO 17573-3) M
This data element shall contain the identifier of the entity originating
the contents of the APDU, which can either be a TC or a TSP. This may
be, but is not necessarily, the actual sender of the information.
informationSenderId
Provider (imported from ISO 17573-3) M
This data element shall contain the identifier of the entity sending
the APDU.
It shall contain a different identifier as the data element
apduOriginator when a technical entity is supporting the origina-
tor of the APDU in the task of compiling and transferring informa-
tion.
It shall contain the same identifier as the data element
apduOriginator when the originator and the sender of the APDU
are the same entity.
ISO 12855:2025/DAM 1:2026(en)
TTabablele 4 4 ((ccoonnttiinnueuedd))
Data element Data type/data description Status
protocolIssuerId
Provider (imported from ISO 17573-3) O
This data element shall not be present if the protocol is based on a
specific edition of ISO 12855 or EN 16986 stated in data element
aidIdentifier without any private values, restrictions or exten-
sions.
This data element shall be present and shall contain the iden-
tifier of the issuer of a private protocol stated in data element
aidIdentifier specifying any private values, restrictions or exten-
sions.
The data element protocolIssuerId shall contain the same value as
the data element apduOriginator if the originator of the APDU uses
its own private protocol.
The data element protocolIssuerId shall contain the same value
as the data element informationSenderId if the originator of the
APDU uses a private protocol of the sender.
The data element protocolIssuerId shall contain another
value as the data element apduOriginator or the data element
informationSenderId if the originator of the APDU uses a private
protocol of someone else.
EXAMPLE A TSP states the identifier of the TC to which it sends
information to indicate the use of a private protocol, values or exten-
sions specified by the TC.
See clause 5.3 on the use of private values.
informationRecipientId
Provider (imported from ISO 17573-3) M
This data element shall contain the identifier of the entity to which
the content of the APDU is sent, which can be a TC or a TSP.
apduIdentifier
ApduIdentifier specified as INTEGER ranging from 0 to 2 -1 M
This data element shall contain a unique identifier for each
apduOriginator. It is assigned by the originator of the APDU.
previousApduId
RelatedApduId (see Table 6) O
This data element may optionally contain the unique identifier of the
previously sent APDU.
nextApduId
RelatedApduId (see Table 6) O
This data element may optionally contain the unique identifier of the
APDU to be sent next.
inResponseToApduId
RelatedApduId (see Table 6) O
This data element may optionally contain the unique identifier of the
APDU to which this APDU is sent in response.
apduDate
GeneralizedTime M
This data element shall specify the time stamp of the generation of the
APDU in coordinated universal time (UTC).

Replace Table 5 with the following:
Table 5 — Values and semantics of AidIdentifier
Name Semantics Value
iso12855v4
Identifies the object identifier (OID) version 1.0.12855.4 of ISO 12855:2015 0
isoDIS12855v5
Identifies the OID version 1.0.12855.5 of ISO/DIS 12855:2020 1
isoFDIS12855v5
Identifies the OID version 1.0.12855.5 of the FDIS version of ISO 12855:2021 2
iso12855v5
Identifies the OID 1.0.12855.5 of ISO/FDIS 12855:2022 3
isoDIS12855v6m1
Identifies the OID 1.0.12855.6.1 of ISO/DIS 12855:2024 4

ISO 12855:2025/DAM 1:2026(en)
TTabablele 5 5 ((ccoonnttiinnueuedd))
Name Semantics Value
iso12855v7m1
Identifies the OID 1.0.12855.7.1 of ISO/FDIS 12855:2025 5
iso12855v8m1
Identifies the OID 1.0.12855.8.1 of ISO 12855:2025 amendment 1:2026 6
Values reserved for future ISO use 7.15
cen16986x2016
Identifies CEN/TS 16986:2016 16
NOTE There was no ASN.1 code for this edition and it is therefore not regis-
tered in the OID database.
enENQ16986v1m1
identifies the OID 1.3.162.16986.1.1.1, 1.3.162.16986.2.1.1, 1.3.162.16986.3.1.1 17
or 1.3.162.16986.4.1.1 of prEN 16986:2022 (i.e. the CEN Enquiry version)
en16986v2m1
identifies the OID 1.3.162.16986.1.2.1, 1.3.162.16986.2.2.1, 1.3.162.16986.3.2.1 18
or 1.3.162.16986.4.2.1 of EN 16986:2024
enENQ16986v3m1
identifies the OID 1.3.162.16986.1.3.1, 1.3.162.16986.2.3.1, 1.3.162.16986.3.3.1 19
or 1.3.162.16986.4.3.1 of prEN 16986:2026 (i.e. the CEN Enquiry version)
en16986v4m1
identifies the OID 1.3.162.16986.1.4.1, 1.3.162.16986.2.4.1, 1.3.162.16986.3.4.1 20
or 1.3.162.16986.4.4.1 of EN 16986:2026
Values reserved for future CEN use 21.31
Values reserved for private use 32.255

6.2.3  Application data units
Replace Table 7 with the following:
Table 7 — Data elements of Adus
Data element Data type/data description Status
requestAdus
List (ASN.1 SEQUENCE OF) of one to 10 000 elements of data type N/A
RequestAdu (see 6.4)
ackAdus
List (ASN.1 SEQUENCE OF) of one to 10 000 elements of data type N/A
AckAdu (see 6.5)
trustObjectAdus
List (ASN.1 SEQUENCE OF) of one element of data type N/A
TrustObjectAdu (see 6.7)
efcContextDataAdus
List (ASN.1 SEQUENCE OF) of one element of data type N/A
EfcContextDataAdu (see 6.8)
exceptionListAdus
List (ASN.1 SEQUENCE OF) of one element of data type N/A
ExceptionListAdu (see 6.9)
reportAbnormalBehaviourAdus
List (ASN.1 SEQUENCE OF) of one to 10 000 elements of data type N/A
ReportAbnormalBehaviourAdu (see 6.10)
tollDeclarationAdus
List (ASN.1 SEQUENCE OF) of one to 100 000 elements of data N/A
type TollDeclarationAdu (see 6.11)
billingDetailsAdus
List (ASN.1 SEQUENCE OF) of one to 100 000 elements of data N/A
type BillingDetailsAdu (see 6.12)
paymentClaimAdus
List (ASN.1 SEQUENCE OF) of one to 100 000 elements of data N/A
type PaymentClaimAdu (see 6.13)
reportQaAdus
List (ASN.1 SEQUENCE OF) of one to 1 000 elements of data type N/A
ReportQaAdu (see 6.14)
statusAdus
List (ASN.1 SEQUENCE OF) of one to 1 000 elements of data type N/A
StatusAdu (see 6.6)
provideUserDetailsAdus
List (ASN.1 SEQUENCE OF) of one to 10 000 elements of data type N/A
ProvideUserDetailsAdu (see 6.15)
reportCccEventAdus
List (ASN.1 SEQUENCE OF) of one to 100 000 elements of data N/A
type ReportCccEventAdu (see 6.16)

ISO 12855:2025/DAM 1:2026(en)
TTabablele 7 7 ((ccoonnttiinnueuedd))
Data element Data type/data description Status
provideUserIdListAdus
List (ASN.1 SEQUENCE OF) of one to 10 000 elements of data type N/A
ProvideUserIdListAdu (see 6.17)
paymentAnnouncementAdus
List (ASN.1 SEQUENCE OF) of one to 10 000 elements of data type N/A
PaymentAnnouncementAdu (see 6.18)
contractIssuerListAdus
List (ASN.1 SEQUENCE OF) of one element of data type N/A
ContractIssuerListAdu (see 6.19)
userComplaintAdus
List (ASN.1 SEQUENCE OF) of one to 1 000 elements of data type N/A
UserComplaintAdu (see 6.20)
userComplaintResponseAdus
List (ASN.1 SEQUENCE OF) of one to 1 000 elements of data type N/A
UserComplaintResponseAdu (see 6.21)
mediaSettlementDataAdus
List (ASN.1 SEQUENCE OF) of one to 10 000 elements of data type N/A
MediaSettlementDataAdu (see 6.22)
enforcementStatusAdus
List (ASN.1 SEQUENCE OF) of one to 100 000 elements of data N/A
type EnforcementStatusAdu (see 6.23)

6.3.3  Version and validity of information
Replace Table 12 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 12 — Data elements of UserId
Data element Data type/data description Status
pan
PersonalAccountNumber (imported from ISO 17573-3) O
This data element may optionally be used to identify the user by the
personal account number.
contractSerialNumber
ContractSerialNumber specified as UTF8String SIZE(1.32) O
This data element may optionally be used to identify the user by the
serial number of the contract.
NOTE 1 The data element contractSerialNumber, specified as data
type INTEGER in ISO 17573-3, can be stated as a UTF8string if provided
in this data element.
NOTE 2 The definition of this data element as data type UTF8string
also allows the provision of a character-oriented serial number.
licencePlateNumber
Lpn (imported from ISO 17573-3) O
This data element may optionally be used to identify the user by the
structured licence plate number and the country of registration.
NOTE 1 In Europe a structured licence plate number contains letters
and numbers and the dash “-“ or space “ “ as separation character for
countries with non-unique licence plate numbers (currently Austria
and Germany). No separation character is provided for countries with
unique licence plate numbers.
NOTE 2 In Europe, characters in a licence plate number from latinAlpha-
betNo2, latinCyrillicAlphabet, latinGreekAlphabet or latinAlphabetNo10
are mapped to the corresponding latinAlphabetNo1 lower case charac-
ters by applying the mapping table as specified in EN ISO 14906:2022,
Table D.1.
obeId
ObeId (imported from ISO 17573-3) O
This data element may optionally be used to identify the user by the OBE
identifier.
The data element efcContextMark may be used to provide additional
information about the OBE, if needed.
equipmentIccId
EquipmentIccId (imported from ISO 17573-3) O
This data element may optionally be used to identify the user by the
number of an integrated circuit card (ICC).
customerId
OCTET STRING SIZE(1.16) O
This data element may optionally be used to identify the user by the cus-
tomer identification issued by the TSP.
efcContextMark
EfcContextMark (imported from ISO 17573-3) O
This data element may optionally be used to provide additional informa-
tion about an OBE. It shall not be used without the data element obeId
as an identification of a user.
NOTE 3 The data element efcContextMark is not suitable to identify
the user by itself.
ISO 12855:2025/DAM 1:2026(en)
Table 13 — Data elements of VersionAndValidity
Data element Data type/data description Status
version
VersionId (see Table 14) M
This data element shall contain a unique version information of the information to
which it refers.
NOTE The format of the version information is specified by the originator or sender of
the information and is outside the scope of this document.
validFrom
GeneralizedTime M
This data element shall contain the starting date and time of the validity of the infor-
mation to which it refers.
The decision to use UTC or local time is specified by the originator or sender of the
information and is outside the scope of this document.

Replace Table 14 with the following:
Table 14 — Data elements of VersionId
Data element Data type/data description Status
— OCTET STRING SIZE(1.255) M
This data element shall contain a unique identification of the version of an object.
An object may be a list of data elements of a specific data type.

6.3.5  Authentication of data elements
Replace Table 17 with the following:
Table 17 — Data elements of TbsAuthenticatorEfc
Data element Data type/data description Status
version
INTEGER ranging from 0 to 2 -1 with a default value of 1. O
This data element may optionally contain a version number of the
certificate.
signatureAlgorithm
AlgorithmIdentifier (see Table 18) using the parameter M
Pkcs1Algorithms
This data element shall contain the identifier and parameters of the
algorithm used to generate the signature.
issuer
Name (see Table 69) M
This data element shall contain the name of the issuer to be used for
the calculation of the signature.
serialNumber
CertificateSerialNumber specified as INTEGER M
This data element shall contain the unique serial number of the cer-
tificate to be used for the calculation of the signature.
apduContentDigest
ApduContentDigest (see Table 19) M
This data element shall contain the hash calculated of the cXER
encoded payload and the identifier of the hash algorithm used to
calculate the hash.
ISO 12855:2025/DAM 1:2026(en)
TTabablele 1 177 ((ccoonnttiinnueuedd))
Data element Data type/data description Status
signatureDate
GeneralizedTime M
This data element shall contain the time stamp of the generated
signature.
certificates
List (ASN.1 SEQUENCE OF) of one to 100 elements of data type O
CertificateObject (see Table 63)
This data element shall be present and shall contain the certificate(s)
needed to calculate the signature if they were not previously shared.
This data element shall not be present if the certificate(s) needed to
calculate the signature were previously shared.
NOTE It is not advised to provide the certificates to calculate the
signature in the same APDU as the signature itself, as this poses
the risk of providing correctly signed data by an impostor. It would
be better to provide the certificate by another means via a trust-
ed channel or in a separate APDU via the TrustObjectAdu (see
Table 59).
signingCertificateHash
CertHash (see Table 20) O
This data element may optionally contain a hash code calculated
over the certificate provided in the data element certificates
used to generate the signature. It may optionally be used to avoid an
attack based on reissuing a certificate by a key certification author-
ity with the same identification but other certificate attributes, i.e.
the certificates to sign the APDU and to verify it are not identical.

6.3.7  Geographical points and areas
Replace Table 23 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 23 — Data elements of Link
Data element Data type/data description Status
linkId
INTEGER ranging from 0 to 2 -1 M
This data element shall contain a unique identifier of a link within the toll
context partition.
startPoint
Point (see Table 22) M
This data element shall contain the start point of the link.
This data element may be specified by using the data element
relativePointCoordinates to provide relative coordinates to the data
element chargeObjectRefPoint in data type Section (see Table 164),
if it is provided, or to the data element geoRefPoint in data type
TollContetPartitionOverview (see Table 156), if it is provided.
intermediatePoints
List (ASN.1 SEQUENCE OF) of zero to 100 elements of data type Point (see O
Table 22)
This data element may optionally contain (a unidirectional list of) interme-
diate point(s) from the start point to the end point of the link, to provide a
more accurate model of the link.
This data element may be specified by using the data element
relativePointCoordinates to provide relative coordinates to the data
element chargeObjectRefPoint in data type Section (see Table 164),
if it is provided, or to the data element geoRefPoint in data type
TollContextPartitionOverview (see Table 156), if it is provided.
endPoint
Point (see Table 22) M
This data element shall contain the end point of the link.
This data element may be specified by using the data element
relativePointCoordinates to provide relative coordinates to the data
element chargeObjectRefPoint in data type Section (see Table 164),
if it is provided, or to the data element geoRefPoint in data type
TollContextPartitionOverview (see Table 156), if it is provided.

Replace Table 24 with the following:
Table 24 — Data elements of Polygon
Data element Data type/data description Status
— List (ASN.1 SEQUENCE OF) of three to 10 000 elements of data type Point (see Table 22) M
NOTE A polygon consists of at least three points to form an area.
The segments of the polygon shall be created by connecting each of the points with its
successor point in a clockwise direction.
The polygon shall be closed by connecting the last point in the list with the first point.
The points shall be specified in a way that means the connections between the points do
not intersect.
The inner side of the polygon (tolled area) is specified as the geographical area that is
located at the right-hand side when moving on a polygon segment from its start point to
its end point.
Replace Table 25 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 25 — Data elements of SupportingPoint
Data element Data type/data description Status
supportPoint
Point (see Table 22) M
This data element shall contain the location of a point on the
section.
supportPointDescription
UTF8String SIZE(1.255) M
This data element may optionally contain a textual description of
the supporting point and the adjacent road.
distanceToNextRoad
Distance (imported from ISO 17573-3) O
This data element may optionally contain the minimum dis-
tance from the supporting point specified in the data element
supportPoint to an adjacent road.

6.3.8  Textual descriptions or attachments
Replace Table 26 with the following:
Table 26 — Data elements of InfoData
Data element Data type/data description Status
textItem
OCTET STRING SIZE(1.1000) N/A
This data element shall contain (if used) a textual description.
binaryItem
BinaryItem (see Table 27) N/A
This data element shall contain (if used) a document in different formats.
EXAMPLE Word, PDF or ZIP.
Replace Table 2z with the following:
Table 27 — Data elements of BinaryItem
Data element Data type/data description Status
content
OCTET STRING SIZE(1.4194304) M
This data element shall contain the binary content.
NOTE The maximum size of a binary attachment (document size) is 4 MB.
mediaType
OCTET STRING SIZE(1.255) M
This data element shall contain the Internet Assigned Numbers Authority
(IANA) Registry application media-type describing the type of Content.

6.4.2  Generic request
Replace Table 32 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 32 — Data elements of the sub-structure of genericRequest
Data element Data type/data description Status
apduIdentifier
ApduIdentifier O
This data element may optionally be used to request that the APDU carrying
the same identifier is resent.
requestedAduType
AduType (see Table 9) O
This data element may optionally be used to specify the type of the requested
ADU.
aduIdentifier
List (ASN.1 SEQUENCE OF) of one to 100 000 elements of data type O
AduIdentifier
This data element may optionally be used to ask for retransmission of the
specified ADUs.
actionCode
ActionCode (see Table 10) O
This data element may optionally be used to indicate specific actions per-
formed by the sender of the request. Only the value send is allowed.
actionRequest
ActionCode (see Table 11) O
This data element may optionally be used to indicate specific actions to
be pursued by the receiver of the request. Only the values send, resend or
revoke are allowed.
6.4.4  Request for trust objects
Replace Table 35 with the following:
Table 35 — Data elements of TrustObjectSpec
Data element Data type/data description Status
typeOfTrustObject
Record (ASN.1 SEQUENCE) of data type RequestedTrustObjectType M
(see Table 36)
This data element shall contain the type of the requested trust object.
purposesOfTrustObject
List (ASN.1 SEQUENCE OF) of one to 255 elements of data type O
TrustObjectPurpose (see Table 60)
This data element may optionally contain the purpose of the requested
trust object.
6.4.6 Request for user details
Replace Table 38 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 38 — Data elements of the sub-structure of userDetailsRequest
Data element Data type/data description Status
requestedAduType
AduType (see Table 9) M
This data element shall contain the value
provideUserDetailsAdu.
userId
UserId (see Table 12) O
This data element may optionally be used to indicate the user
for the requested user details.
listOfParametersRequested
List (ASN.1 SEQUENCE OF) of one to 255 elements of data type O
UserParameterRequest (see Table 39)
This data element may optionally be used to specify the list of
requested parameters.
userDetailsRequestReason
UserDetailsRequestReason (see Table 40) O
This data element may optionally be used to indicate a reason
for the request for user details.
period
Period (imported from ISO 17573-3) O
This data element may optionally be used to indicate a certain
point in time for the requested user details.
The data elements beginOfPeriod and endOfPeriod in the
data type Period shall contain the same value.
additionalProofDocument
List (ASN.1 SEQUENCE OF) of one to 10 elements of data type O
TextualDescription (see Table 15)
This data element may optionally contain a textual description
of the requested proof document.
actionCode
ActionCode (see Table 10) O
This data element may optionally be used to indicate specific ac-
tions performed by the originator of the request. Only the value
send is allowed.
actionRequest
ActionCode (see Table 11) O
This data element may optionally be used to indicate specific
actions to be pursued by the receiver of the request. Only the
value send is allowed.
Replace Table 39 with the following:
Table 39 — Values and semantics of UserParameterRequest
Name Semantics Value
Value reserved for future CEN and ISO use 0
contractSerialNumber
Request to provide the number of the contract of the user in the 1
system of the TSP.
contractValidity
Request to provide the contractValidity as used in the pa- 2
rameter contval in the EfcContainer of the OBE.
driverCharacteristics
Request to provide the class of the driver and purpose of a trip 3
for a specific trip of a vehicle.
A trip shall be specified by providing a userId and specific
point in time in the data element period, where the startTime
and endTime contain the same value.
efcContextMark
Request to provide the EFC context mark of the OBE 4
environmentalCharacteristics
Request to provide the environmental characteristics 5
euroValue and copValue of a vehicle
engineCharacteristics
Request to provide the vehicle’s engine type and fuel character- 6
istics.
ISO 12855:2025/DAM 1:2026(en)
TaTabbllee 39 39 ((ccoonnttiinnueuedd))
Name Semantics Value
equipmentObuId
Request to provide the unique number of the OBE specified by 7
the manufacturer.
equipmentStatus
Request to provide the operator-specific EFC application-relat- 8
ed information of the OBE.
paymentMeans
Request to provide the payment means of the user and its expi- 9
ry date.
paymentMeansBalance
Request to provide the balance of the payment means of the 10
user.
NOTE 1 Typically requested together with payUnit.
payUnit
Request to provide the payUnit for the paymentMeansBalance. 11
NOTE 2 Typically requested together with
paymentMeansBalance.
personalAccountNumber
Request to provide the PAN of the OBE. 12
provider
Request to provide the identification of the contract issuer of 13
the OBE or for the vehicle.
NOTE 3 The provider can identify the contracting TSP in an
ANPR scheme without an OBE.
receiptContract
Request to provide the identification for a contract for a speci- 14
fied period.
validityOfContract
Request to provide information about any validity restrictions 15
and the validity period of the user’s contract.
vehicleAuthenticator
Request to provide an authenticator calculated over the vehicle 16
data at the time of entry.
vehicleClass
Request to provide the class of the vehicle. 17
vehicleDimensions
Request to provide the dimensions of the vehicle. 18
vehicleLicencePlateNumber
Request to provide the licence plate number and nationality of 19
the vehicle.
vehicleIdentificationNumber
Request to provide the unique vehicle identification number of 20
the vehicle.
vehicleWeightLaden
Request to provide the laden weight of a vehicle for a specific 21
trip or time span.
NOTE 4 A trip is specified through the userId and period,
where startTime and endTime have the same value.
vehicleWeightLimits
Request to provide the three weight limits 22
vehicleMaxLadenWeight, vehicleTrainMaximumWeight and
vehicleWeightUnladen of a vehicle.
NOTE 5 This parameter does not include the vehicleTechnica
lPermissibleMaxLadenMass.
vehicleAxles
Request to provide the height over the first axle and the number 23
of axles of a vehicle.
exhaustEmissionValues
Request to provide the exhaust emission values of a vehicle. 24
dieselEmissionValues
Request to provide the diesel emission values of a vehicle. 25
userPostalAddress
Request to provide the postal address of the holder of a vehicle. 26
preferredUserLanguage
Request to provide the preferred language of communication of 27
a user.
icc
Request to provide the number of the ICC. 28
co2EmissionValueLoad
Request to provide the specific CO emission of a vehicle in g/ 29
tkm.
initialVehicleRegistrationDate
Request to provide the initial date of registration of a vehicle. 30
euVehicleGroup
Request to provide the EU vehicle group of a vehicle. 31

ISO 12855:2025/DAM 1:2026(en)
TaTabbllee 39 39 ((ccoonnttiinnueuedd))
Name Semantics Value
engineDetails
Request to provide the engine capacity and net power of a 32
vehicle.
cabType
Request to provide the cabin type of a vehicle. 33
NOTE 6 Used to distinguish between the usage profile long haul
(LH) and regional distribution (RD) for the EU vehicle sub-
group.
co2Class
Request to provide the CO class of a vehicle. 34
chassisType
Request to provide the chassis type of a vehicle. 35
wheelsConfiguration
Request to provide the configuration of wheels of a vehicle. 36
vehicleTechnicalPermissibleMaxL
Request to provide the technical permissible maximum laden 37
adenMass
mass of a vehicle.
NOTE 7 This parameter is not included in
vehicleWeightLimits.
suspensionType
Request to provide the suspension type of a vehicle. 38
futureElement
Request to provide the future element. 39
Value reserved for future CEN and ISO use 40.127
Values reserved for private use 128.255

Replace Table 40 with the following:
Table 40 — Values and semantics of UserDetailsRequestReason
Name Semantics Value
generalInterest
Request without a specified reason. 0
allowingCalculatingFee
Request to calculate the amount due for the use of a charge 1
object.
incompleteCccReadout
Request to supplement a CCC readout of an OBE. 2
forwardingEnforcementTicket
Request to support the generation of an enforcement case 3
against a user.
checkOfParameters
Request to support the verification of the validity of the 4
submitted user or vehicle parameters.
If this value is present, the data element
additionalInformation in the data type
ProvideUserDetailsAdu (see Table 314) shall be present.
terminateLocalContract
Information to the TSP that a local contract at the TC was 5
terminated.
changeLocalcontract
Information to the TSP that a local contract at the TC was 6
changed.
Values reserved for future CEN and ISO use 7.127
Values reserved for private use 128.255

6.4.9  Request for media settlement data
Replace Table 43 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 43 — Data elements of the sub-structure of mediaSettlementDataRequest
Data element Data type/data description Status
requestedAduType
AduType (see Table 9) M
This data element shall contain the value
mediaSettlementDataAdu.
period
Period (imported from ISO 17573-3) O
This data element may optionally be used to indicate a certain peri-
od for the requested MediaSettlementDataAdus.
equipmentIccId
EquipmentIccId (imported from ISO 17573-3) O
This data element may optionally be used to limit the sending of a
MediaSettlementDataAdu to a specific equipmentIccId.
mediaSettlementListVersion
VersionId (see Table 14) O
This data element may optionally be used to indicate a certain ver-
sion of a requested mediaSettlementDataAdu.
actionCode
ActionCode (see Table 10) O
This data element may optionally be used to indicate specific ac-
tions performed by the sender of the request. Only the value send is
allowed.
actionRequest
ActionCode (see Table 11) O
This data element may optionally be used to indicate specific ac-
tions to be pursued by the receiver of the request. Only the values
send or resend are allowed.
6.4.11  Request for an enforcement status
Replace Table 45 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 45 — Data elements of the sub-structure of enforcementStatusRequest
Data element Data type/data description Status
requestedAduType
AduType (see Table 9) M
This data element shall contain the value
enforcementStatusRequest.
associatedEventData
List (ASN.1 SEQUENCE OF) of one to 100 elements of data type O
AssocEventData (see Table 281)
This data element may optionally contain a limitation of the request
for enforcement data to charge object(s) identified by the provided
associated event data.
The TSP shall apply its usual processing parameters, which are applied
to identify a usage of the charge object(s) provided in this data ele-
ment, in its search for applicable enforcement data.
rseId
BeaconID (imported from ISO 14906) O
This data element may optionally contain a limitation of the request
for enforcement data to a charge object identified by the provided
identifier of the RSE.
The TSP shall apply the usual processing parameters, which are ap-
plied to identify a usage of the charge object that contains this RSE, in
its search for applicable enforcement data.
proximitySearchData
ProximitySearchData (see Table 46) O
This data element may optionally contain a geographic limitation of
the request for enforcement data.
The TSP shall apply the provided geographical areas in its search for
applicable enforcement data.
usedChargeObjectData
List (ASN.1 SEQUENCE OF) of one to 100 elements of data type O
UsedChargeObjectData (see Table 49)
This data element may optionally contain a limitation of the request
for enforcement data to identifiers of the provided charge object(s).
The TSP shall apply its usual processing parameters, which are applied
to identify a usage of the provided charge object(s), in its search for
applicable enforcement data.
additionalInformation
OCTET STRING SIZE(1.1023) O
This data element may optionally contain additional infor-
mation from the TC: what it wants the TSP to provide in the
EnforcementStatusAdu (see Table 348).
period
Period (imported from ISO 17573-3) O
This data element may optionally contain a limitation of the request
for enforcement data to a certain time period.
actionCode
ActionCode (see Table 10) O
This data element may optionally be used to indicate specific ac-
tions performed by the sender of the request. Only the value send is
allowed.
actionRequest
ActionCode (see Table 11) O
This data element may optionally be used to indicate specific actions
to be pursued by the receiver of the request. Only the value send is
allowed.
Replace Table 46 with the following:

ISO 12855:2025/DAM 1:2026(en)
Table 46 — Data elements of ProximitySearchData
Data element Data type/data description Status
boundingBoxes
List (ASN.1 SEQUENCE OF) of one to 100 elements of data type Box (see N/A
Table 47)
This data element shall contain (if used) a list of coordinates of rectangles de-
scribing the search area.
polygons
List (ASN.1 SEQUENCE OF) of one to 100 elements of data type Polygon (see N/A
Table 24)
This data element shall contain (if used) a list of coordinates of polygons de-
scribing the search area.
The polygons shall be specified using points with absolute coordinates.
circles
List (ASN.1 SEQUENCE OF) of one to 100 elements of data type Circle (see N/A
Table 48)
This data element shall contain (if used) a list of coordinates of circles describ-
ing the search area.
locationRawData
List (ASN.1 SEQUENCE OF) of one to 100 elements of data type Point (see N/A
Table 22)
This data element shall contain (if used) a list of points describing the search
area.
Replace Table 49 with the following:
Table 49 — Data elements of UsedChargeObjectData
Data element Data type/data description Status
use
...