ISO 12855:2025
(Main)Electronic fee collection — Information exchange between service provision and toll charging
Electronic fee collection — Information exchange between service provision and toll charging
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.
Perception de télépéage — Échange d'informations entre la prestation de service et la perception du péage
Le présent document spécifie: — les interfaces entre les systèmes de back-office de perception de télépéage (EFC) pour les services de transport associés aux véhicules, tels que la tarification des usagers de la route, le stationnement et le contrôle d’accès; — l’échange d’informations entre les systèmes centraux des deux rôles de prestataire de services et d’exploitant de péage, par exemple: — données liées à la perception (déclarations de péage, détails de facturation); — données administratives; et — données de confirmation; — les mécanismes de transfert et fonctions de support; — les objets d’informations, syntaxe et 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 définis en Annexe A, à l’aide de 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 de back-office; — les interfaces pour systèmes de télépéage destinés aux transports publics; — tous transferts complexes (transactions), 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; ni — la définition des canaux de communication de services, des protocoles et des primitives de service permettant de transférer les APDU.
General Information
Relations
Standards Content (Sample)
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 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
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
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 Toll
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.