SIST EN ISO 12855:2022

SLOVENSKI STANDARD
01-julij-2022
Nadomešča:
SIST EN ISO 12855:2016
Elektronsko pobiranje pristojbin - Izmenjava informacij med ponudnikom in
operaterjem cestninjenja (ISO 12855:2022)
Electronic fee collection - Information exchange between service provision and toll
charging (ISO 12855:2022)
Elektronische Gebührenerhebung - Informationsaustausch zwischen Dienstleistern und
Gebühreneinzugsunternehmen (ISO 12855:2022)
Perception du télépéage - Échange d'informations entre la prestation de service et la
perception du péage (ISO 12855:2022)
Ta slovenski standard je istoveten z: EN ISO 12855:2022
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
May 2022
EUROPÄISCHE NORM
ICS 03.220.20; 35.240.60 Supersedes EN ISO 12855:2015
English Version
Electronic fee collection - Information exchange between
service provision and toll charging (ISO 12855:2022)
Perception du 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:2022) Gebühreneinzugsunternehmen (ISO 12855:2022)
This European Standard was approved by CEN on 22 February 2022.

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

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

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 12855:2022 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 12855:2022) 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 November 2022, and conflicting national standards
shall be withdrawn at the latest by November 2022.
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:2015.
This document has been prepared under a Standardization Request given to CEN by the European
Commission and the European Free Trade Association.
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, Turkey and the
United Kingdom.
Endorsement notice
The text of ISO 12855:2022 has been approved by CEN as EN ISO 12855:2022 without any modification.

INTERNATIONAL ISO
STANDARD 12855
Third edition
2022-04
Electronic fee collection —
Information exchange between service
provision and toll charging
Perception du télépéage — Échange d'informations entre la
prestation de service et la perception du péage
Reference number
ISO 12855:2022(E)
ISO 12855:2022(E)
© ISO 2022
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:2022(E)
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 charging and provision . 5
5.2.1 General . 5
5.2.2 Basic protocol mechanisms . 7
5.2.3 Exchange trust objects functionality . 8
5.2.4 Originating and providing EFC context data functionality . 8
5.2.5 Provide contract issuer information functionality . 9
5.2.6 Manage exception list functionality . 9
5.2.7 Report toll declarations functionality . 10
5.2.8 Report billing details functionality . 10
5.2.9 Payment settlement functionality . 11
5.2.10 Exchange enforcement data functionality .12
5.2.11 Process user complaints functionality . 13
5.2.12 Exchange quality assurance parameters functionality .13
5.2.13 Provide media settlement data functionality . . 14
6 Computational specification .14
6.1 Overview . 14
6.2 Application protocol data units . 17
6.2.1 General . 17
6.2.2 Application protocol control information (APCI) . 19
6.2.3 Application data units .20
6.2.4 ADU identification .20
6.2.5 ADU action code . 21
6.2.6 User identification . 21
6.3 RequestAdu data structure . .22
6.4 AckAdu data structure .25
6.5 StatusAdu data structure . 32
6.6 TrustObjectAdu data structure . 32
6.7 EfcContextDataAdu data structure . 39
6.7.1 General .39
6.7.2 GeneralContextData type .40
6.7.3 MeshedContextData type . 57
6.7.4 Common data structures .66
6.8 ContractIssuerListAdu data structure .88
6.9 ExceptionListAdu data structure .90
6.10 ReportAbnormalObeAdu data structure .94
6.11 TollDeclarationAdu data structure . 95
6.12 BillingDetailsAdu data structure.99
6.12.1 General .99
6.12.2 UsageList data type.101
6.12.3 AssociatedEventData data type . 111
6.13 PaymentClaimAdu data structure . 117
6.14 PaymentAnnouncement Adu data structure . . 119
6.15 ProvideUserDetailsAdu data structure .121
6.16 ReportCccEventAdu data structure .125
iii
ISO 12855:2022(E)
6.17 ProvideUserIdListAdu data structure .126
6.18 Report QA data structure.127
6.19 User complaint data structure .128
6.20 User complaint response data structure.129
6.21 Media settlement data structure .131
7 Transfer mechanisms and supporting functions . 132
7.1 Transfer mechanisms .132
7.2 Secure communication channel .133
7.3 Supporting functions .133
7.3.1 Communication services .133
7.3.2 Authenticators .133
7.3.3 Signature and hash algorithms .135
7.3.4 Keys encryption .135
Annex A (normative) Data type specifications . 136
Annex B (informative) Example enforcement process applyingstandardized APDU
exchanges . 137
Annex C (informative) Example of data flows in a toll domain .142
Annex D (informative) Example of rounding differences .145
Annex E (informative) Example of fee calculation using EFC context data . 149
Bibliography . 153
iv
ISO 12855:2022(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, in
collaboration with the European Committee for Standardization (CEN) Technical Committee CEN/TC
278, Intelligent transport systems, in accordance with the Agreement on technical cooperation between
ISO and CEN (Vienna Agreement).
This third edition cancels and replaces the second edition (ISO 12855:2015), which has been technically
revised.
The main changes are as follows:
— addition of new application data units (ADUs);
— alignment of the ASN.1 data definitions with the current edition of ISO 14906;
— removal of all dependencies on the ISO 17575 series ASN.1 data types and creation of corresponding
definitions;
— re-classification of the electronic fee collection (EFC) context types by tolling and geographical
characteristics and removal of the previous distinction based on tolling technology;
— splitting of the ASN.1 module into two modules: one containing ISO 12855-specific definitions, and
another containing data-type definitions that are common to other standards in the EFC domain.
This common data types module has then been moved to ISO/TS 17573-3;
— clarification of the semantics of all parameters in ADUs;
— alignment of the structure of all major clauses in a consistent manner 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:2022(E)
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 those vehicles require on-board equipment (OBE) this should be interoperable
with the toll systems in the various toll domains. In Europe, for example, this need has been officially
[8]
recognized and legislation on interoperability has already been adopted (see Directive 2019/520 ,
[10]
related Commission delegated regulation 2020/2003 and Commission implementing regulation
[9]
2020/204 ). There is both a commercial and economic justification regarding the OBE and the toll
systems for International Standards supporting interoperability.
The system architecture defined in ISO 17573-1 is the basis for all International Standards that relate
to tolling systems in the toll domain. With respect to ISO 17573-1, this document:
— adopts its definitions of terms and concepts and basic system functionalities and structure,
— uses its terminology, and
— specifies the interfaces identified therein.
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:2022(E)
Key
DSRCdedicated short-range communication
QA quality assurance
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.
The amount due for a given transport service used by a vehicle liable to toll is finalized by the TC with
the use of 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 toll service provider
(TSP) the task of calculating the amount due.
The information above, 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 by the
TC and/or the relevant TSP; they are finalized by the TC or by the TSP if the TC has assigned this task to
the TSP.
The TC settles the payment claims (or toll payment claims) 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 billing details. These payment claims include an amount due, taking into account
any specific commercial conditions applicable to a vehicle, a fleet of vehicles or a given TSP.
vii
ISO 12855:2022(E)
This document defines 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 defined in ISO 17573-1.
This document does not provide a full solution for interoperability and it does not define other parts
of the EFC system, other services, other technologies and non-technical elements of interoperability. It
is defined as a toolbox International Standard of application protocol data units (APDUs), which can be
used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real
implementation are defined elsewhere. It does not define all communication sequences, communication
stacks and timings.
The development of a common European Electronic Toll Service (EETS), as a part of the already cited
European EFC Directive and related Regulation and Implementing acts, also calls for the definition
of an interoperable EFC service. It should be noted that CEN/TS 16986 (to be revised and converted
into a European Standard) specifies interoperable application profiles (IAP), applicable based on
this document. These profiles define a specific coherent set of transactions, triggers, conditions,
data elements, transfer mechanisms and supporting functions for an interoperable exchange of data
between the back end system of TCs and TSPs. CEN/TS 16986 is consistent with and is intended to
provide support for the technical specification of the EETS.
This document identifies and specifies the set of APDUs exchanged between two actors in the roles of
TSP and TC as defined in ISO 17573-1. To specify these interfaces, this document uses the enterprise
description of the toll environment, and the interactions defined between the named classes of roles,
as defined 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 application protocol data units are defined.
viii
INTERNATIONAL STANDARD ISO 12855:2022(E)
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 end system of the two roles of service provision and
toll charging, e.g.:
— charging-related data (toll declarations, billing details),
— administrative data, 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 defined 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 toll charger (TC) or toll service provider (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 application data units (ADUs)
that can possibly involve several application protocol data unit (APDU) exchanges;
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;
and
— definitions of service communication channels, protocols and service primitives to transfer the
APDUs.
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 612, Road vehicles — Dimensions of motor vehicles and towed vehicles — Terms and definitions
ISO 12855:2022(E)
ISO 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code
ISO 1176, Road vehicles — Masses — Vocabulary and codes
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code
ISO 4217, Codes for the representation of currencies
ISO 8583-1, Financial transaction card originated messages — Interchange message specifications — Part
1: Messages, data elements and code values
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 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/IEC 11770-3, Information security — Key management — Part 3: Mechanisms using asymmetric
techniques
ISO 13616-1, Financial services — International bank account number (IBAN) — Part 1: Structure of the
IBAN
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 17444-1, Electronic fee collection — Charging performance — Part 1: Metrics
ISO/TS 17573-2, Electronic fee collection — System architecture for vehicle related tolling — Part 2:
Vocabulary
ISO/IEC 18033-2, Information technology — Security techniques — Encryption algorithms — Part 2:
Asymmetric ciphers
ISO 19299, Electronic fee collection — Security framework
ISO 20524-1:2020, Intelligent transport systems — Geographic Data Files (GDF) GDF5.1 — Part 1:
Application independent map data shared between multiple sources
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 12855:2022(E)
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/
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
LAC localization augmentation communication
LPN licence plate number
NMEA National Marine Electronics Association
OBE on-board equipment
OBU on-board unit
ISO 12855:2022(E)
OCSP online certificate status protocol
OSI open systems interconnection
PAN personal account number
QA quality assurance
RINEX receiver independent exchange format
RSA Rivest, Shamir and Adleman
RSE roadside equipment
SLA service level agreement
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 ISO 17573-1.
ISO 17573-1 specifies the four main roles shown in Figure 2.
ISO 12855:2022(E)
Figure 2 — Roles in the toll charging environment
Information exchanges are agreed upon between TC and TSP, taking into account privacy regulations.
The information exchanges needed by the TC and the TSP to perform their roles are described in this
clause.
5.2 Information exchange between toll charging and provision
5.2.1 General
The information exchange between the service provision and the toll charging roles supports the
provision of functionalities that are based on the EFC system service specifications in ISO 17573-1.
Figure 3 gives a general picture of the functionalities provided in this document.
ISO 12855:2022(E)
Figure 3 — Functionalities of this document (ISO 12855)
These functionalities are listed below, in the order in which they are given in Clause 5:
— basic protocol mechanisms;
— exchange trust objects;
— provide EFC context data;
— provide contract issuer list;
— manage exception list;
— report toll declarations;
— report billing details;
— payment settlement:
— claim payment for service usage,
— announce payments.
— exchange enforcement data:
— exchange of user details,
— exchange of compliance check communication (CCC) events,
— exchange of UserId lists,
— process user complaints:
— provide a user complaint;
ISO 12855:2022(E)
— response to a user complaint.
— exchange quality assurance parameters.
— provide media settlement data.
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; and
— the semantics and the format of the APDUs that are exchanged.
These functionalities are described in 5.2.2 to 5.2.13.
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. sequences of
inter-related ADUs which may involve several APDU exchanges. Instead, this document specifies basic
protocol mechanisms to be used by implementations that need to specify and perform transactions.
This document provides the following basic protocol mechanisms to exchange information between the
TSP’s and the TC’s back end system. These basic protocol mechanisms consist of:
— an identification schema for the APDUs that are exchanged,
— a generic interaction (i.e. not related to any specific functionality) that supports requesting a specific
information exchange from the counterpart. This interaction is provided by the “request” ADU,
— a generic acknowledge mechanism (i.e. not related to any specific functionality) that supports
acknowledging a specific interaction. The “ack” ADU provides this mechanism, and
— an optional generic status mechanism (i.e. not related to any specific functionality) that supports
providing status information for a specific interchange. This mechanism is provided by the “status”
ADU.
By means of the above mechanisms, an implementation can build more complex protocol procedures,
including rollback, recovery, checkpoint or restart.
This document does not specify timings and retry procedures for acknowledgements. Timeouts can be
specified as agreements between TC and TSP to cover the case of missing acknowledgements.
5.2.2.2 Identification schema
Each APDU contains a unique identifier in the namespace of the originator of the APDU. The combination
of originator identifier and APDU identifier ensures that all APDUs are uniquely identified.
5.2.2.3 Request functionality
The request functionality is used to:
— alert the counterpart that one is ready to accept any kind of information exchange,
— inform the counterpart that one is ready to accept a specific type of ADU, by indicating the type of
ADU one is ready to accept,
ISO 12855:2022(E)
— request the counterpart re-issue a specific APDU, by indicating the type and the identifier of the
APDU, and
— request information identified by type and ADU content.
5.2.2.4 Acknowledgement functionality
The acknowledgement functionality is used to inform the counterpart that a specific ADU has been
received correctly, or that errors have been detected.
5.2.2.5 Status functionality
The status functionality may be used to provide the counterpart with general status information about
the interface or to inform it about a status on previously transferred information. It is used to:
— provide general information on the status of the interface,
— alert the counterpart that some previously provided information becomes invalid without any new
information being currently available, and
— alert the counterpart that the previous information contained an error and should be recalled.
5.2.3 Exchange trust objects functionality
The exchange trust objects functionality is derived from the EFC system service “trust object
exchange”. The functionality is used whenever an entity, both TC and TSP, needs to send unsolicitedly
new or updated trust objects to its counterpart or when asked by its counterpart to update or resend
an already existing trust object.
NOTE Examples of trust objects are: asymmetric public keys, certificates, symmetric keys and certificate
revocation lists.
Requiring the counterpart to send trust objects is performed by means of a “request” ADU. The “request”
ADU supports requesting already issued trust objects to be resent, as well as requesting newly issued
trust objects.
The exchange trust objects functionality provides the “trust objects” ADU to transfer the requested or
newly generated trust objects to the counterpart, which has the possibility of confirming or rejecting
the received trust objects by using the acknowledgement functionality.
The exchanged trust objects are valid from either the time of their acknowledgment or from the validity
starting, if specified in the “trust object” ADU. Trust objects may also become valid based on bilateral
agreements between TSP and TC (as defined in the implementation conformance statement).
5.2.4 Originating and providing EFC context data functionality
The originating and providing EFC context data functionality is derived from ISO 17573-1 as specified
in the EFC system service “adding or modifying a toll regime”.
The originating and providing EFC context data functionality gives a TC the possibility to communicate
any change of a toll domain or toll regime, including the start of a new toll domain, by issuing an “EFC
context data” ADU.
A TSP has the possibility of requiring a TC to provide information about the toll context data for a toll
domain under its responsibility by using a “request” ADU. The TC provides the information requested
by this “request” ADU by using an “EFC context data” ADU.
The TSP has the possibility to confirm reception of an “EFC context data” ADU by using the
acknowledgement functionality.
ISO 12855:2022(E)
5.2.5 Provide contract issuer information functionality
The contractual information functionality supports a TSP in delivering to the TC any type of user
contract related information that is stored in the OBE, among which the personal account number
(PAN), the supported security level and the key set to be used in the calculation of dedicated short-
range communication (DSRC) authenticators. This functionality supports, among others, the TC in
comparing data retrieved from the OBEs with information received by the TSP.
5.2.6 Manage exception list functionality
5.2.6.1 General
The manage exception list functionality originates from ISO 17573-1 and is specified in the EFC system
service “exceptions handling”.
NOTE 1 This document uses the term “exception list” to summarize all possibilities of limiting the availability
of transport services to a user or giving information on the special handling of an OBE in a toll regime. Other
standards use different terms, but they are all included in the term “exception list”.
NOTE 2 The conditions and the periods of time that a user can be accepted within a toll regime are limited by
putting it on the exception list or removing it. This is solely the responsibility of the related TSP. Any information
sufficient for the identification of a specific vehicle or OBE by the TC, e.g. OBE ID, PAN, LPN (licence plate number),
are included in the exception list as agreed between TC and TSP.
5.2.6.2 Exception list entry requested by a toll charger
The manage exception list functionality supports a TC in notifying a TSP about detected violations by a
...