oSIST prEN 16986:2023
(Main)Electronic fee collection - Interoperable application profiles for information exchange between Service Provision and Toll Charging
Electronic fee collection - Interoperable application profiles for information exchange between Service Provision and Toll Charging
This document defines an application interface definition by selecting suitable options from the base standard EN ISO 12855:2021. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between Toll Chargers and Toll Service Providers.
This document covers:
— exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
o charging related data (exception lists, toll declarations, billing details, payment claims);
o administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
o confirmation data.
— transfer mechanisms and supporting functions;
— semantics of data elements;
— restrictions on parameters and their values
— implementation conformance statement proforma, in an Annex, as a basis for assessment of conformity to this document;
— an Interoperability statement proforma, in an Annex, as a basis for assessment of transactional interoperability of two technical implementations;
— a web service definition, in an Annex, for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered.
Elektronische Gebührenerhebung - Interoperable Anwendungsprofile für den Informationsaustausch zwischen den Dienste-Versorgern und Mauterhebern
Perception de télépéage - Profils d’application d’interopérabilité pour échange d’informations entre la prestation de service et la perception du péage
Le présent document spécifie des profils d’application d’interopérabilité pour l’échange d’informations entre des exploitants de péage (TC) et des fournisseurs de service de péage (TSP), en sélectionnant des options appropriées dans la norme de base EN ISO 12855:2022.
Ce document couvre les aspects suivants :
— échange d’informations entre les systèmes centraux des TC et des TSP, par ex. :
— données liées à la perception (déclarations de péage, détail de facturation, demande de paiement, annonce de paiement) ;
— données administratives (objets de confiance, données de contexte de perception électronique du télépéage, coordonnées pour le contrôle-sanction, etc.) ;
— données liées à l’utilisateur (listes d'exceptions, coordonnées d’utilisateur, information OBE anormales, données d’événement CCC, réclamations d’utilisateur) ;
— données de confirmation.
— les mécanismes de transfert et fonctions de support ;
— sémantique des éléments de données ;
— définitions formelles (Annexe A) des restrictions sur les types de données relatives aux définitions de l’ASN.1 dans la norme de base EN ISO 12855:2022 à travers l’introduction d’un schéma XML (XML Schema Definition – XSD) pour chaque profil spécifié ;
— formulaire de déclaration de conformité de mise en œuvre (Annexe B), servant de base à l’évaluation d’une mise en œuvre en conformité avec le présent document ;
— formulaire de déclaration d’interopérabilité (Annexe C), servant de base à l’évaluation de l’interopérabilité transactionnelle de deux mises en œuvre techniques ;
— définition des services web (Annexe D) pour l’utilisation des services web comme technologie de communication.
La mise en œuvre des systèmes centraux sous-jacents et de leurs processus commerciaux n’est pas traitée. Par conséquent, les aspects suivants ne relèvent pas du domaine d’application du présent document :
— détails de la manière dont les systèmes centraux utilisent les éléments de données des authentificateurs de la norme de base pour mettre en œuvre la sécurité ;
— fonctionnement des contrôles de conformité et du processus de contrôle sanction ;
— aspects commerciaux ;
— définition des caractéristiques non fonctionnelles telles que les indicateurs de performance, les niveaux de défaillance acceptables, la disponibilité des interfaces des TC et TSP, et les exigences en matière de rapport.
Par ailleurs, le présent document explicite la correspondance entre la législation relative au service européen de télépéage (EETS) et le présent document (Annexe E).
Elektronsko pobiranje pristojbin - Interoperabilni profili aplikacije za informativno izmenjavo med ponudnikom storitve in operaterjem cestninjenja
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN 16986:2023
01-maj-2023
Elektronsko pobiranje pristojbin - Interoperabilni profili aplikacije za informativno
izmenjavo med ponudnikom storitve in operaterjem cestninjenja
Electronic fee collection - Interoperable application profiles for information exchange
between Service Provision and Toll Charging
Elektronische Gebührenerhebung - Interoperable Anwendungsprofile für den
Informationsaustausch zwischen den Dienste-Versorgern und Mauterhebern
Perception de télépéage - Profils d’application d’interopérabilité pour échange
d’informations entre la prestation de service et la perception du péage
Ta slovenski standard je istoveten z: prEN 16986
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 16986:2023 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 16986:2023
---------------------- Page: 2 ----------------------
oSIST prEN 16986:2023
DRAFT
EUROPEAN STANDARD
prEN 16986
NORME EUROPÉENNE
EUROPÄISCHE NORM
March 2023
ICS 35.240.60 Will supersede CEN/TS 16986:2016
English Version
Electronic fee collection - Interoperable application
profiles for information exchange between Service
Provision and Toll Charging
Perception de télépéage - Profil d'application Elektronische Gebührenerhebung - Interoperable
interopérabilité pour échange d'informations entre la Anwendungsprofile für den Informationsaustausch
prestation de service et la perception du péage zwischen den Dienste-Versorgern und Mauterhebern
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 278.
If this draft becomes a European Standard, 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.
This draft European Standard was established by CEN 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.
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.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
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
© 2023 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 16986:2023 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 16986:2023
prEN 16986:2023 (E)
Contents Page
EUROPEAN FOREWORD . 5
INTRODUCTION . 6
1 SCOPE . 7
2 NORMATIVE REFERENCES. 7
3 TERMS AND DEFINITIONS . 8
4 ABBREVIATED TERMS . 12
5 CONFORMANCE . 13
5.1 GENERAL . 13
5.2 BASE STANDARD . 13
5.3 MAIN CONTENTS OF THE IAPS IN THIS DOCUMENT . 14
5.3.1 General requirements . 14
5.3.2 Profiles . 14
5.3.3 Interaction protocol . 17
5.4 CONFORMANCE REQUIREMENTS . 24
5.4.1 Relations between this document and the base standard . 24
5.4.2 Conformance to profiles . 25
5.5 CONFORMANCE STATEMENT . 26
5.6 INTEROPERABILITY . 26
6 GENERAL RESTRICTIONS . 26
6.1 GENERAL . 26
6.2 CODED VALUES AND RANGES . 26
6.3 EXTENDED DATA TYPES . 29
6.3.1 General . 29
6.3.2 NominalVehicleParameters. 29
6.3.3 UserParameterResponseDetails . 31
6.4 INFOEXCHANGE APDU . 33
6.4.1 Information sender and information originator . 33
6.4.2 Restrictions in InfoExchangeContent data elements . 33
6.4.3 InfoExchangeAuthenticator . 34
6.5 ACKADU . 35
6.5.1 General . 35
6.5.2 Transaction protocol . 35
6.5.3 Syntax and semantics . 35
6.6 APDU TRANSFER MECHANISMS . 36
6.6.1 ASN.1 encoding . 36
6.6.2 Generic transfer mechanisms . 36
6.6.3 Alternative transfer mechanisms for transaction type TRUSTOBJECTS . 36
7 COMMON TRANSACTIONS . 36
7.1 USERDETAILS - RETRIEVE AND PROVIDE USER DETAILS . 36
7.1.1 Transaction sequence, triggers and timings . 36
7.1.2 Syntax and semantics . 38
7.2 LISTOFUSERS – PROVIDE A LIST OF USERS . 40
7.2.1 Transaction sequence, triggers and timings . 40
7.2.2 Syntax and semantics . 41
7.3 EXCEPTIONLIST - MANAGING EXCEPTION LISTS . 42
7.3.1 Transaction sequence, triggers and timings . 42
7.3.2 Syntax and semantics . 44
7.4 TRUSTOBJECTS - EXCHANGE TRUST OBJECTS. 51
2
---------------------- Page: 4 ----------------------
oSIST prEN 16986:2023
prEN 16986:2023 (E)
7.4.1 APDU transfer mechanisms . 51
7.4.2 Transaction sequence, triggers and timings . 51
7.4.3 Syntax and semantics . 54
7.5 CONTRACTISSUERLIST – TRANSFER OBE CONTRACTUAL INFORMATION .5 5
7.5.1 Transaction sequence, triggers and timings . 55
7.5.2 Syntax and semantics . 56
7.6 EFCCONTEXTDATA – TRANSFER TOLL CONTEXT DATA INFORMATION .5 7
7.6.1 Transaction sequence, triggers and timings . 57
7.6.2 Syntax and semantics . 58
7.7 BILLINGDETAILS_TC – TRANSFER BILLING DETAILS FROM TC .5 8
7.7.1 Transaction sequence, triggers and timings . 58
7.7.2 Syntax and semantics . 60
7.8 BILLINGDETAILS_TSP .6 1
7.8.1 Transaction sequence, triggers and timings . 61
7.8.2 Syntax and semantics . 63
7.9 PAYMENTCLAIM – ISSUE A PAYMENT CLAIM .6 4
7.9.1 Transaction sequence, triggers and timings . 64
7.9.2 Syntax and semantics . 66
7.10 REPORTABNORMALOBE – REPORT DETECTION OF OBE MISBEHAVIOUR .6 7
7.10.1 Transaction sequence, triggers and timings . 67
7.10.2 Syntax and semantics . 68
7.11 USERCOMPLAINT – REPORT A USER COMPLAINT .6 9
7.11.1 Transaction sequence, triggers and timings . 69
7.11.2 Syntax and semantics . 71
7.12 QAINFO – EXCHANGE OF QUALITY RELATED INFORMATION .7 2
7.12.1 Transaction sequence, triggers and timings . 72
7.12.2 Syntax and semantics . 74
8 SECTIONDISCRETE PROFILE. 75
8.1 DESCRIPTION .7 5
8.2 COMMON TRANSACTIONS USED BY THE PROFILE.7 5
8.3 ADDITIONAL PROFILE RESTRICTIONS .7 6
8.3.1 Apci restrictions . 76
8.3.2 EXCEPTIONLIST restrictions . 76
8.3.3 TRUSTOBJECTS restrictions. 76
8.3.4 EFCCONTEXTDATA restrictions . 77
8.3.5 BILLINGDETAILS_TC restrictions . 84
8.3.6 PAYMENTCLAIM restrictions . 86
8.4 SPECIFIC PROFILE TRANSACTIONS .8 7
9 SECTIONAUTONOMOUS PROFILE . 87
9.1 DESCRIPTION .8 7
9.2 COMMON TRANSACTIONS USED BY THE PROFILE.8 7
9.3 FURTHER PROFILE RESTRICTIONS ON USED TRANSACTIONS .8 8
9.3.1 EXCEPTIONLIST restrictions . 88
9.3.2 BILLINGDETAILS transactions restrictions. 88
9.3.3 EFCCONTEXTDATA restrictions . 89
9.4 SPECIFIC PROFILE TRANSACTIONS .8 9
9.4.1 TOLLDECLARATIONS_SECT . 90
9.4.2 PAYMENTANNOUNCEMENT transaction . 94
10 MESHEDDISCRETE PROFILE . 97
10.1 DESCRIPTION .9 7
10.2 COMMON TRANSACTIONS USED BY THE PROFILE.9 7
10.3 FURTHER PROFILE RESTRICTIONS ON USED TRANSACTIONS .9 8
10.3.1 EXCEPTIONLIST restrictions. 98
10.3.2 TRUSTOBJECTS restrictions . 98
3
---------------------- Page: 5 ----------------------
oSIST prEN 16986:2023
prEN 16986:2023 (E)
10.3.3 EFCCONTEXTDATA restrictions . 98
10.3.4 BILLINGDETAILS_TC restrictions .102
10.3.5 BILLINGDETAILS_TSP_restrictions .103
10.4 SPECIFIC PROFILE TRANSACTIONS . 104
11 AREADISTANCEAUTONOMOUS PROFILE .104
11.1 DESCRIPTION . 104
11.2 COMMON TRANSACTIONS USED BY THE PROFILE . 104
11.3 FURTHER PROFILE RESTRICTIONS ON USED TRANSACTIONS . 104
11.3.1 EXCEPTIONLIST restrictions .104
11.3.2 EFCCONTEXTDATA restrictions .104
11.3.3 BILLINGDETAILS_TSP restrictions . 105
11.3.4 REPORTABNORMALOBE restrictions .106
11.4 SPECIFIC PROFILE TRANSACTIONS . 106
11.4.1 TOLLDECLARATIONS_AREA .106
ANNEX A (NORMATIVE) FORMAL RESTRICTIONS ON DATA TYPES .112
ANNEX B (NORMATIVE) ICS PROFORMA .114
ANNEX C (NORMATIVE) INTEROPERABILITY STATEMENT PROFORMA .193
ANNEX D (NORMATIVE) WEB SERVICE DEFINITION (WSDL) .201
ANNEX E (NORMATIVE) USE OF THIS DOCUMENT FOR THE EETS .202
BIBLIOGRAPHY .204
4
---------------------- Page: 6 ----------------------
oSIST prEN 16986:2023
prEN 16986:2023 (E)
European foreword
This document (prEN 16986:2023) has been prepared by Technical Committee CEN/TC 278 “Intelligent
transport systems”, the secretariat of which is held by NEN.
This document is currently submitted to the CEN Enquiry.
This document will supersede CEN/TS 16986:2016.
This document has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association.
In comparison to the previous edition, the following main technical changes have been made:
• updated interoperability application profiles tailored according to electronic fee collection (EFC)
charging policies and primary used technologies;
• updated data definitions to reflect changes made to the underlying base standard, i.e., EN ISO
12855:2022;
• addition of a second level of the version identifier (i.e. minor version) of the abstract syntax
notation one (ASN.1) module to provide enhanced support to standards that import data types
from this document;
• introduction of use of imported ASN.1 types with successors (i.e. including all future minor
versions);
• updated terms and definitions, including reference to ISO/TS 17573-2 as the primary source;
• inserted a normative formal specification of profiles’ restrictions on data, both as ASN.1 data
types, and as XSD specifications as Annex A and renumbered other annexes consequently;
• updated informative Annex E on the “Use of this document for the European electronic toll
[16]
service” (EETS), so as to reflect the recast of the EETS legislation (i.e. Directive (EU) 2019/520
[18]
and the corresponding Commission Implementing Regulation ).
5
---------------------- Page: 7 ----------------------
oSIST prEN 16986:2023
prEN 16986:2023 (E)
Introduction
The CEN ISO Standard on Electronic fee collection - Information exchange between service provision and
toll charging (i.e. EN ISO 12855) is a so-called toolbox standard. That means that it provides a large
number of options that can be used to support various needs of toll chargers (TCs) and toll service
providers (TSPs). As such, it provides useful but not sufficient support to ensure technical
interoperability.
The aim of this document is to produce a profile specification that provides technical interoperability to
support the EFC information exchange between TSPs and TCs according to the following tolling policies:
— based on traversing sections of roads;
— based on travelling within areas of territory;
— based on traversing meshed networks of roads.
This document covers the definition of interoperable application profiles (IAP) applicable for the use of
EN ISO 12855:2022. 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 systems of TCs and TSPs (in Europe).
This document defines profiles using the concept of “International Standardized Profiles (ISP)”, as
defined in ISO/IEC TR 10000-1. The ISP concept is specifically suited for defining interoperability
specifications where a set of base standards can be used in different ways. This is exactly the case for
EN ISO 12855:2022, where the base standard allows for different choices that are not interoperable.
The principles of the ISP-concept can be summarized as follows:
— an ISP will make references only to base standards or other ISPs;
— the profile will restrict the choice of base standard options to the extent necessary to maximize
the probability of interoperability (e.g. chosen classes, conforming subsets, options and
parameter values of base standards);
— the ISP will not copy content of the base standards (in order to avoid consistency problems with
the base standards);
— the profile will not specify any requirements that would contradict or cause non-conformance to
the base standards;
— the profile may contain conformance requirements that are more specific and limited in scope
than those of the base standards;
— conformance to a profile implies by definition conformance to a set of
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.