Electronic fee collection - Information exchange between service provision and toll charging (ISO 12855:2025)

This document specifies:
—    the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;
—    an exchange of information between the back-office system of the two roles of service provision and toll charging, e.g.:
—   charging-related data (toll declarations, billing details, payment claims, payment announcements),
—   administrative data (trust objects, EFC context data, etc.), and
—   confirmation data;
—    transfer mechanisms and supporting functions;
—    information objects, data syntax and semantics.
This document is applicable for any vehicle-related toll service and any technology used for charging.
The data types and associated coding related to the data elements described in Clause 6 are specified in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).
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;
—    any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve several APDU exchanges;
—    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.

ktronische Gebührenerhebung - Informationsaustausch zwischen Dienstleistern und Gebühreneinzugsunternehmen (ISO 12855:2025)

Perception de télépéage - Échange d'informations entre la prestation de service et la perception du péage (ISO 12855:2025)

Le présent document spécifie:
—     les interfaces entre les systèmes back-office de perception de télépéage (EFC) pour les services de transport associés aux véhicules, comme la tarification des usagers de la route, le stationnement et le contrôle d'accès;
—     l'échange d'informations entre les systèmes back-office des deux rôles de prestataire de services et d'exploitant de péage, par exemple:
—    les données liées à la perception (déclarations de péage, détails de facturation, demandes de paiement, annonces de paiement);
—    les données administratives (objets de confiance, données de contexte EFC);
—    les données de confirmation;
—     les mécanismes de transfert et les fonctions de support;
—     les objets d'informations, la syntaxe et la sémantique des données.
Le présent document est applicable à tout service lié à des véhicules et à toute technologie utilisée pour la perception.
Les types de données et le codage associé aux éléments de données décrits à l'Article 6 sont spécifiés à l'Annexe A selon la notation de syntaxe abstraite numéro un (ASN.1) conformément à l'ISO/IEC 8824-1.
Le présent document spécifie les mécanismes de protocole de base sur lesquels des réalisations peuvent spécifier et exécuter des transferts (transactions) complexes.
Le document ne spécifie pas, entre autres:
—     toute communication entre l'exploitant de péage ou le fournisseur de service de péage, et toute autre partie prenante;
—     toute communication entre éléments de l'exploitant de péage et du fournisseur de service de péage ne faisant pas partie de la communication back-office;
—     les interfaces pour systèmes de télépéage destinés aux transports publics;
—     tous transferts (transactions) complexes, c'est-à-dire des séquences d'unités de données d'application (ADU) pouvant éventuellement mettre en jeu plusieurs échanges d'unités de données de protocole d'application (APDU);
—     les processus concernant les paiements et les échanges de documents comptables fiscaux, commerciaux ou juridiques;
—     la définition des canaux de communication de services, des protocoles et des primitives de service permettant de transférer les APDU.

Elektronsko pobiranje pristojbin - Izmenjava informacij med ponudnikom in operaterjem cestninjenja (ISO 12855:2025)

Ta dokument določa: –   vmesnike med zalednimi sistemi za elektronsko pobiranje pristojbin (EFC) za prevozne storitve z vozili (npr. zaračunavanje uporabnine cest, parkirnine in nadzor dostopa); –   izmenjavo informacij med zalednim sistemom z dvema vlogama zagotavljanja storitev in zaračunavanja cestnine, na primer: –  podatki v zvezi z zaračunavanjem (plačilo cestnine, podrobnosti obračunavanja, zahtevki za plačila, obvestila o plačilu); –  skrbniški podatki (zaupanja vredni objekti, kontekstni podatki EFC, kontaktni podatki za izvršbo ipd.); in –  podatki o potrditvi; –   prenosni mehanizmi in podporne funkcije; –   informacijski objekti, skladnja in semantika podatkov. Ta dokument se uporablja za vse storitve cestninjenja v povezavi z vozili in tehnologije, ki se uporabljajo za zaračunavanje. Podatkovne vrste in povezano kodiranje podatkovnih elementov, opisanih v točki 6, so opisani v dodatku A na podlagi zapisa abstraktne skladnje št. ena (ASN.1) v skladu s standardom ISO/IEC 8824-1. Ta dokument določa osnovne mehanizme protokola, prek katerih lahko izvedbe določajo in izvajajo kompleksne prenose (transakcije). Ta dokument med drugim ne določa: –   komunikacije med pobiralcem cestnine (TC) ali izvajalcem storitve pobiranja cestnine (TSP) in katero koli drugo udeleženo stranko; –   komunikacije med elementi pobiralca cestnine in izvajalca storitve pobiranja cestnine, ki ni del zaledne komunikacije; –   vmesnikov za sisteme za elektronsko pobiranje cestnin za javni prevoz; –   kompleksnih prenosov (transakcij), tj. zaporedij medsebojno povezanih aplikacijskih podatkovnih enot (ADU), ki lahko vključujejo več izmenjav podatkovnih enot aplikacijskega protokola (APDU); –   postopkov v zvezi s plačili in izmenjavami fiskalnih, tržnih ali pravnih računovodskih listin; –   določitve storitvenih komunikacijskih kanalov, protokolov in storitvenih primitivov za prenos podatkovnih enot aplikacijskega protokola.

General Information

Status
Published
Publication Date
15-Apr-2025
Current Stage
6060 - Definitive text made available (DAV) - Publishing
Start Date
16-Apr-2025
Completion Date
16-Apr-2025

Relations

Standard
EN ISO 12855:2025 - BARVE
English language
307 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-julij-2025
Nadomešča:
SIST EN ISO 12855:2022
Elektronsko pobiranje pristojbin - Izmenjava informacij med ponudnikom in
operaterjem cestninjenja (ISO 12855:2025)
Electronic fee collection - Information exchange between service provision and toll
charging (ISO 12855:2025)
Elektronische Gebührenerhebung - Informationsaustausch zwischen Dienstleistern und
Gebühreneinzugsunternehmen (ISO 12855:2025)
Perception de télépéage - Échange d'informations entre la prestation de service et la
perception du péage (ISO 12855:2025)
Ta slovenski standard je istoveten z: EN ISO 12855:2025
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.

EN ISO 12855
EUROPEAN STANDARD
NORME EUROPÉENNE
April 2025
EUROPÄISCHE NORM
ICS 03.220.20; 35.240.60 Supersedes EN ISO 12855:2022
English Version
Electronic fee collection - Information exchange between
service provision and toll charging (ISO 12855:2025)
Perception de télépéage - Échange d'informations Elektronische Gebührenerhebung -
entre la prestation de service et la perception du péage Informationsaustausch zwischen Dienstleistern und
(ISO 12855:2025) Gebühreneinzugsunternehmen (ISO 12855:2025)
This European Standard was approved by CEN on 22 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 12855:2025 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 12855: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 October 2025, and conflicting national standards shall
be withdrawn at the latest by October 2025.
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 12855:2022.
This document has been prepared under a standardization request addressed to CEN by the European
Commission. The Standing Committee of the EFTA States subsequently approves these requests for its
Member States.
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 12855:2025 has been approved by CEN as EN ISO 12855:2025 without any modification.

International
Standard
ISO 12855
Fourth edition
Electronic fee collection —
2025-04
Information exchange between
service provision and toll charging
Perception de télépéage — Échange d'informations entre la
prestation de service et la perception du péage
Reference number
ISO 12855:2025(en) © ISO 2025
ISO 12855: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 12855:2025(en)
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms. 3
5 Architectural concepts and information exchanges . 4
5.1 Main roles in the toll charging environment .4
5.2 Information exchange between toll charger and toll service provider .5
5.2.1 General .5
5.2.2 Basic protocol mechanisms .6
5.2.3 Exchange trust objects functionality .7
5.2.4 Originate EFC context data functionality .8
5.2.5 Manage exception list functionality .8
5.2.6 Report abnormal behaviour functionality .9
5.2.7 Report toll declarations functionality .9
5.2.8 Report billing details functionality .9
5.2.9 Report payment claim functionality.10
5.2.10 Exchange quality assurance parameters functionality .11
5.2.11 Report CCC event functionality .11
5.2.12 Provide user details and user list information functionalities .11
5.2.13 Report payment announcement functionality . 12
5.2.14 Provide contract issuer information functionality . 13
5.2.15 User complaint and response functionality . 13
5.2.16 Provide media settlement data functionality . . 13
5.2.17 Report enforcement status functionality .14
5.3 Use of private values and extensions.14
6 Computational specification . 14
6.1 Overview .14
6.2 Application protocol data units .19
6.2.1 General .19
6.2.2 Application protocol control information . 20
6.2.3 Application data units .24
6.2.4 ADU identification . 26
6.3 Common data types .27
6.3.1 ADU action codes .27
6.3.2 User identification . 28
6.3.3 Version and validity of information . 29
6.3.4 Textual descriptions . . 30
6.3.5 Authentication of data elements . 30
6.3.6 Payment amount . . 33
6.3.7 Geographical points and areas . 33
6.3.8 Textual descriptions or attachments . 35
6.3.9 Identification of toll events . 36
6.3.10 Time . 36
6.4 RequestAdu data structure .37
6.4.1 Requesting information .37
6.4.2 Generic request .37
6.4.3 Request for an exception list . 38
6.4.4 Request for trust objects . 39
6.4.5 Request for toll declarations .41
6.4.6 Request for user details .42
6.4.7 Request for CCC events .45

iii
ISO 12855:2025(en)
6.4.8 Request for a list of associated users . 46
6.4.9 Request for media settlement data .47
6.4.10 Request for quality assurance parameters . . 48
6.4.11 Request for an enforcement status . 49
6.5 AckAdu data structure .52
6.6 StatusAdu data structure . 78
6.7 TrustObjectAdu data structure . 80
6.7.1 General . 80
6.7.2 Certificate object . 83
6.7.3 Public key object . 84
6.7.4 DSRC key object . 85
6.7.5 DSRC key reference . 89
6.7.6 Other trust object . 90
6.8 EfcContextDataAdu data structure . 90
6.8.1 General . 90
6.8.2 The EntityOverview data structure . 94
6.8.3 Toll context properties . 99
6.8.4 General toll context data . 136
6.8.5 Meshed toll context data . 157
6.9 ExceptionListAdu data structure .174
6.10 ReportAbnormalBehaviourAdu data structure .184
6.11 TollDeclarationAdu data structure . 187
6.12 BillingDetailsAdu data structure . 199
6.12.1 General . 199
6.12.2 Usage information . 205
6.12.3 Associated event data . 225
6.12.4 Discounts . 236
6.13 PaymentClaimAdu data structure . 236
6.14 ReportQaAdu data structure . 242
6.15 ProvideUserDetailsAdu data structure .246
6.16 ReportCccEventAdu data structure .254
6.17 ProvideUserIdListAdu data structure. 255
6.18 PaymentAnnouncementAdu data structure . 256
6.19 ContractIssuerListAdu data structure .260
6.20 UserComplaintAdu data structure . 263
6.21 UserComplaintResponseAdu data structure .266
6.22 MediaSettlementDataAdu structure .268
6.23 EnforcementStatusAdu data structure. 270
7 Transfer mechanisms and supporting functions .276
7.1 Transfer mechanisms .276
7.2 Secure communication channel . 277
7.3 Supporting functions . 277
7.3.1 Communication services . 277
7.3.2 Authenticators . 277
7.3.3 Signature and hash algorithms . 278
7.3.4 Key encryption . 278
Annex A (normative) Data type specifications .279
Annex B (informative) Example enforcement process applyingstandardized APDU exchanges . 280
Annex C (informative) Example of data flows in a toll domain . 284
Annex D (informative) Example of rounding differences . 287
Annex E (informative) Fee calculation using EFC context data .291
Bibliography .295

iv
ISO 12855: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 fourth edition cancels and replaces the third edition (ISO 12855:2022), which has been technically
revised.
The main changes are as follows:
— the application data units (ADUs) have been revised;
— the data definitions and semantics have been updated, including making reference to ISO/TS 17573-2 as
the primary source;
— the remaining references to the ISO 17575 series in 5.2.7 and in the Bibliography have been removed;
— the MacKeyObject has been removed from the TrustobjectAdu (see 6.7);
— the ADUs have been adapted to support automatic number plate recognition (ANPR)-based fee collection
and enforcement;
— the structure of all major clauses has been harmonized to improve readability.
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.

v
ISO 12855:2025(en)
Introduction
The widespread use of road tolling requires provisions for users of vehicles that circulate through many
different toll domains. Users should be offered a single contract for driving a vehicle through various toll
domains. Where vehicles require on-board equipment (OBE) or where tolling is based on automatic number
plate recognition (ANPR), these options should be interoperable with the toll systems in the various toll
domains. In Europe, this need has been officially recognized and legislation on interoperability has
[7] [9]
already been adopted (see Directive 2019/520, related Commission delegated regulation 2020/2003
[8]
and Commission implementing regulation 2020/204 ). There is both a commercial and an economic
justification regarding the OBE and the toll systems for International Standards supporting interoperability.
The system architecture specified in ISO 17573-1 is the basis for all ISO and CEN Standards in the road
tolling domain. This document:
— adopts the concepts and basic system functionalities and structure of ISO 17573-1;
— uses the terminology of ISO 17573-1; and
— specifies the interfaces identified in ISO 17573-1.
ISO 17573-1 uses ISO/IEC 10746-3 for the description of the architecture.
Figure 1 shows the scope of the group of International Standards related to electronic fee collection (EFC)
based upon the ISO 17573-1 system architecture.

vi
ISO 12855:2025(en)
Key
ANPR automatic number plate recognition
DSRC dedicated short-range communication
GNSS global navigation satellite system
QA quality assurance
OBE on-board equipment
RSE roadside equipment
Figure 1 — Scope of EFC-related International Standards
A given transport service for a given vehicle is fully identified by one or several toll declarations made
available to the toll charger (TC). It is necessary to make toll declarations available according to the rules of
the toll regime of the toll domain. These toll declarations can either be acquired on the road-side equipment
(RSE) of the TC or acquired by an autonomous OBE and sent to the TC by the toll service provider (TSP).
The amount due for a given transport service used by a vehicle liable to toll is finalized by the TC with the
use of the acquired or received toll declarations (as described above) and calculations are made according
to the rules of the toll regime (formula, tariff tables, specific situations rules, traffic conditions, etc.). This
means that the TC has the authority to decide on the amount due, even if it decides to assign the task of
calculating the amount due to the TSP.
The calculated amount due, associated with a given transport service, is referred to as "billing details". For a
given transport service, the billing details refer to one or several toll declarations.
Depending on the toll regime, billing details are computed by means of the information collected either by
the TC or the relevant TSP, or both. They are finalized by the TC – or by the TSP if the TC has assigned this
task to the TSP – and sent to the counterpart.

vii
ISO 12855:2025(en)
The TC derives the payment claims from the billing details and makes them available to each TSP, or
requires the TSP to send payment announcements, according to the bilateral agreements it has with each
TSP, referring to one or several billing details. These payment claims include an amount due, considering any
specific commercial conditions applicable to a vehicle, a fleet of vehicles or a given TSP, if specified for the
transport service.
This document specifies a set of interactions in support of technical interoperability between back-office
systems of TCs and TSPs. The EFC service and the EFC system model on which this document is based are
specified in ISO 17573-1.
This document does not provide a full solution for interoperability and it does not specify other parts of the
EFC system, other services, other technologies and non-technical elements of interoperability. It is specified
as a toolbox International Standard of an application protocol data unit (APDU), which can be used for the
assigned purpose. This APDU may contain different ADUs, which bear the transferred data. The detailed
definitions of mandatory and optional elements in a real implementation are specified elsewhere. It does not
specify all communication sequences, communication stacks and timings.
The development of a common European Electronic Toll Service (EETS), as a part of the aforementioned
European EFC Directive and related Regulation and Implementing acts, also calls for the definition of an
interoperable EFC service. EN 16986 specifies interoperable application profiles (IAP), applicable based on
this document. These profiles specify a specific coherent set of transactions, triggers, timings, conditions,
data elements, transfer mechanisms and supporting functions for an interoperable exchange of data
between the back-office system of TCs and TSPs. EN 16986 is consistent with and is intended to provide
support for the technical specification of the EETS.
This document identifies and specifies the APDU and a set of ADUs exchanged between two actors in the
roles of TSP and TC as specified in ISO 17573-1. To specify these interfaces, this document uses the enterprise
description of the toll environment, and the interactions specified between the named classes of roles, as
specified in ISO 17573-1. This supports a complete specification of the data that is transferred between
those identified entities. In addition, a number of computational interfaces are identified and interactions in
terms of sequences of APDUs are specified.

viii
International Standard ISO 12855:2025(en)
Electronic fee collection — Information exchange between
service provision and toll charging
1 Scope
This document specifies:
— the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport
services, e.g. road user charging, parking and access control;
— an exchange of information between the back-office system of the two roles of service provision and toll
charging, e.g.:
— charging-related data (toll declarations, billing details, payment claims, payment announcements),
— administrative data (trust objects, EFC context data, etc.), and
— confirmation data;
— transfer mechanisms and supporting functions;
— information objects, data syntax and semantics.
This document is applicable for any vehicle-related toll service and any technology used for charging.
The data types and associated coding related to the data elements described in Clause 6 are specified in
Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document specifies basic protocol mechanisms over which implementations can specify and perform
complex transfers (transactions).
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;
— any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve
several APDU exchanges;
— 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
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 639, Code for individual languages and language groups
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country code

ISO 12855:2025(en)
ISO 4217, Codes for the representation of currencies
ISO/IEC 7812-1, Identification cards — Identification of issuers — Part 1: Numbering system
ISO/IEC 7812-2, Identification cards — Identification of issuers — Part 2: Application and registration
procedures
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1) — Part 1: Specification of
basic notation
ISO/IEC 8825-4, Information technology — ASN.1 encoding rules — Part 4: XML Encoding Rules (XER)
ISO/IEC 8825-8, Information technology — ASN.1 encoding rules — Part 8: Specification of JavaScript Object
Notation Encoding Rules (JER)
ISO/IEC 9594-8, Information technology — Open systems interconnection — Part 8: The Directory: Public-key
and attribute certificate frameworks
ISO/IEC 9797-1:2011, Information technology — Security techniques — Message Authentication Codes (MACs)
— Part 1: Mechanisms using a block cipher
ISO/IEC 10118-3, IT Security techniques — Hash-functions — Part 3: Dedicated hash-functions
ISO 11568, Financial services — Key management (retail)
ISO/IEC 11770-3, Information security — Key management — Part 3: Mechanisms using asymmetric techniques
ISO 12813, Electronic fee collection — Compliance check communication for autonomous systems
ISO 13141, Electronic fee collection — Localization augmentation communication for autonomous systems
ISO/IEC 14888-2:2008, Information technology — Security techniques — Digital signatures with appendix —
Part 2: Integer factorization based mechanisms
ISO 14906, Electronic fee collection — Application interface definition for dedicated short-range communication
ISO/TS 17573-2, Electronic fee collection — System architecture for vehicle related tolling — Part 2: Vocabulary
ISO 17573-3, Electronic fee collection — System architecture for vehicle related tolling — Part 3: Data dictionary
ISO/IEC 18033-2, Information technology — Security techniques — Encryption algorithms — Part 2:
Asymmetric ciphers
ISO 19299, Electronic fee collection — Security framework
ISO/TS 37444, Electronic fee collection — Charging performance framework
IETF RFC 4347, Datagram Transport Layer Security, April 2006
IETF RFC 5246, The Transport Layer Security (TLS) Protocol, August 2008
IETF RFC 5746, Transport Layer Security (TLS) Renegotiation Indication Extension, February 2010
IETF RFC 6040, Tunnelling of Explicit Congestion Notification, February 2013
W3C Recommendation XML Signature Syntax and Processing Version 1.1
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/TS 17573-2 apply.
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

ISO 12855:2025(en)
— IEC Electropedia: available at https:// www .electropedia .org/
4 Symbols and abbreviated terms
ADU application data unit
ANPR automatic number plate recognition
APCI application protocol control information
APDU application protocol data unit
BIC bank identifier code
CCC compliance check communication
CRL certificate revocation list
cXER canonical XML encoding rules
DSRC dedicated short-range communication
DST daylight saving time
DTLS datagram transport layer security
EFC electronic fee collection
FTP file transfer protocol
GDF geographical data file
GNSS global navigation satellite system
HOT high occupancy tolling
HTTPS hyper-text transfer protocol secure
IANA internet assigned numbers authority
IBAN international bank account number
ICC integrated circuit card
IEC International Electrotechnical Commission
ITU International Telecommunication Union
JER JavaScript Object Notation Encoding Rules
LAC localization augmentation communication
LPN licence plate number
NMEA National Marine Electronics Association
OBE on-board equipment
OCSP online certificate status protocol
OID object identifier
ISO 12855:2025(en)
OSI open systems interconnection
PAN personal account number
QA quality assurance
RINEX receiver independent exchange format
RSA Rivest, Shamir and Adleman
RSE roadside equipment
SMTP simple mail transfer protocol
SU service user
TC toll charger
TLS transport layer security
TSP toll service provider
UTC coordinated universal time
VAT value added tax
VPN virtual private network
VRM vehicle registration mark
XER XML encoding rules
NOTE RSA is an algorithm for public-key cryptography, also referred to as asymmetrical cryptographic technique.
5 Architectural concepts and information exchanges
5.1 Main roles in the toll charging environment
This document is built upon the system architecture specified in ISO 17573-1.
ISO 17573-1 specifies the four main roles shown in Figure 2.

ISO 12855:2025(en)
Figure 2 — Roles in the toll charging environment
Information exchanges are agreed upon between TC and TSP, considering privacy regulations and other
legal requirements of the jurisdiction of the TC. The information exchanges needed by the toll charging role
covered by the TC and the service provision role covered by the TSP are described in this clause.
Annex C depicts examples of data exchanges between these roles.
5.2 Information exchange between toll charger and toll service provider
5.2.1 General
This document leaves implementers the freedom of specifying suitable protocol procedures, i.e. for complex
transactions. Therefore, it only specifies:
— a basic interaction protocol (request – response) for information exchange;
— basic protocol mechanisms, to be used to build more complex protocol procedures;
— the semantics and the format of the APDU and ADUs that are exchanged.
The information exchange between the TC and TSP supports the provision of functionalities that are based
on the EFC system service specifications in ISO 17573-1. Figure 3 gives an overview of the functionalities
provided in this document.
ISO 12855:2025(en)
Figure 3 — Functionalities of the back-office interface
The functionalities depicted in Figure 3 are described in 5.2.2 to 5.2.17.
5.2.2 Basic protocol mechanisms
5.2.2.1 General approach
Information exchanges are performed by means of APDU transfers.
Some APDU transfers need to be acknowledged. When this happens, related protocol procedures are
specified. This document specifies no provisions for complex transfers (transactions), i.e. s
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.