ISO 17575-1:2016
(Main)Electronic fee collection — Application interface definition for autonomous systems — Part 1: Charging
Electronic fee collection — Application interface definition for autonomous systems — Part 1: Charging
ISO 17575-1:2016 defines the format and semantics of the data exchange between a Front End (OBE plus optional proxy) and corresponding Back Ends in autonomous toll schemes. It defines the data elements that are used to generate charge reports containing information about the road usage of a vehicle for certain time intervals, sent from the Front End to the Back End. It also defines the data that can be used to re-configure the ongoing process of gathering charge relevant information in the Front End. The scope is shown in Figure 1. The constitution of the charge report is dependent on configuration data that are assumed to be present in the Front End. The assembly of charge reports can be configured for each individual toll scheme according to local needs. Charge reports generated in accordance with this part of ISO 17575 are consistent with the requirements derived from the architectural concept defined in ISO 17573:2010. The definitions in ISO 17575-1:2016 comprise - reporting data, i.e. data for transferring road usage data from Front End to Back End, including a response from the Back End towards the Front End, - data for supporting security mechanisms, - contract data, i.e. data for identifying contractually essential entities, - road usage data, i.e. data for reporting the amount of road usage, - account data for managing a payment account, - versioning data, and - compliance checking data, i.e. data imported from ISO 12813:2015, which are required in compliance checking communication. Annex A contains the data type specifications using ASN.1 notation. The protocol implementation conformity statements (PICS) proforma are provided in Annex B. Annex C provides a graphical presentation of the structure of the data elements described in Clause 7. Annex D provides information on how this part of ISO 17575 can be used in EETS environment and how the requirements that are specified in the EU-Decision 2009/750 are addressed by this standard.
Perception du télépéage — Définition de l'interface d'application pour les systèmes autonomes — Partie 1: Imputation
ISO 17575-1:2016 définit le format et la sémantique pour l'échange de données entre un système frontal (OBE plus proxy optionnel) et des systèmes centraux correspondants dans des systèmes de péage autonomes. Elle définit les éléments de données utilisés pour générer des rapports de perception contenant des informations sur l'utilisation du réseau routier par un véhicule pendant des intervalles de temps donnés, envoyées du système frontal au système central. Elle définit également les données qui peuvent être utilisées pour reconfigurer le processus de collecte permanente des informations d'imputation pertinentes dans le système frontal. Son domaine d'application est représenté à la Figure 1. La constitution d'un rapport de perception dépend des données de configuration supposées être présentes dans le système frontal. L'ensemble des rapports de perception peut être configuré pour chaque système de péage individuel selon les besoins locaux. Les rapports de perception générés conformément à la présente partie de l'ISO 17575 concordent avec les exigences dérivées du concept architectural défini dans l'ISO 17573:2010. Dans l'ISO 17575-1:2016, les définitions comprennent - les données des rapports, c'est-à-dire les données permettant de transférer des données d'utilisation du réseau routier d'un système frontal à un système central, y compris une réponse du système central au système frontal, - les données de prise en charge des mécanismes de sécurité, - les données contractuelles, c'est-à-dire les données permettant d'identifier les entités contractuellement essentielles, - les données d'utilisation du réseau routier, c'est-à-dire les données permettant de communiquer l'utilisation qui est faite du réseau routier, - les données de compte pour gérer un compte de paiement, - les données de contrôle des versions, - les données de contrôle de conformité, c'est-à-dire les données importées de l'ISO 12813:2015, qui sont requises dans les communications de contrôle de conformité. L'Annexe A donne la spécification du type de données dans la notation ASN.1. Les formulaires PICS (déclaration de conformité d'implémentation de protocole) sont fournis en Annexe B. L'Annexe C comprend une représentation graphique de la structure des éléments de données décrits à l'Article 7. L'Annexe D fournit des informations sur la façon dont la présente partie de l'ISO 17575 peut être appliquée dans un environnement SET et sur la manière dont la présente norme couvre les exigences spécifiées dans la Décision de la Commission 2009/750.
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 17575-1
First edition
2016-01-15
Electronic fee collection —
Application interface definition for
autonomous systems —
Part 1:
Charging
Perception du télépéage — Définition de l’interface d’application pour
les systèmes autonomes —
Partie 1: Imputation
Reference number
ISO 17575-1:2016(E)
©
ISO 2016
---------------------- Page: 1 ----------------------
ISO 17575-1:2016(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, 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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 17575-1:2016(E)
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 3
4 Abbreviated terms . 5
5 Architectural considerations . 5
5.1 Business architecture . 5
5.2 Technical architecture . 6
5.3 Location of the specification interface . 7
6 Procedural requirements . 8
6.1 General . 8
6.2 Toll collection process . 8
6.3 Charge report . 8
6.4 Charge report response . 9
7 Data elements . 9
7.1 Overview of data elements . 9
7.2 Reporting .10
7.2.1 ChargeReport .10
7.2.2 ChargeReportResponse .11
7.3 Data group General.11
7.3.1 timeOfReport .11
7.3.2 reportPeriod .11
7.3.3 sumVatForThisSession .12
7.3.4 chargeReportCounter .12
7.3.5 mileage .12
7.3.6 Distance .12
7.3.7 Position .12
7.3.8 Period .12
7.3.9 Duration.13
7.4 Data group Security .13
7.4.1 AuthenticatedChargeReport .13
7.4.2 AuthenticatedChargeReportResponse .13
7.4.3 AuthenticatedUsageStatement .13
7.4.4 AuthenticatedReloadAccount .13
7.4.5 AuthenticatedNewAccountLimit . .14
7.4.6 AuthenticatedAddToAccount .14
7.4.7 MessageAuthenticator .14
7.4.8 MacMessageAuthenticator .14
7.4.9 MessageAuthenticatorEfc .14
7.5 Data group Contract .14
7.5.1 obeId .14
7.5.2 vehicleLPNr .15
7.5.3 paymentMeans .15
7.5.4 serviceProviderContract .15
7.5.5 tollContext .15
7.5.6 chargeReportFinalRecipient .15
7.5.7 obeStatusForDriver .15
7.5.8 ObeStatus .16
7.5.9 chargeReportRespSender .16
7.6 Data group Usage .16
7.6.1 usageStatementList .16
© ISO 2016 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 17575-1:2016(E)
7.6.2 UsageStatement .16
7.6.3 usageStatementID .17
7.6.4 aggregatedFee .17
7.6.5 aggregatedSingleTariffClassSession .17
7.6.6 currentTariffClass .18
7.6.7 VehicleDescription .18
7.6.8 listOfChargeObjects and DetectedChargeObject .18
7.6.9 ChargeObjectId .19
7.6.10 ListOfRawUsageData, measuredRawData .19
7.6.11 NmeaData . .19
7.6.12 additionalGnssData .20
7.6.13 ListOfDSRCUsageData .20
7.6.14 additionalUsageInformation .21
7.6.15 DataReceived .21
7.7 Data group Account .21
7.7.1 accountStatus .21
7.7.2 accountUpdate .21
7.7.3 reloadAccount .22
7.7.4 setAccount .22
7.7.5 addToAccount .22
7.8 Data group Versioning .22
7.8.1 protocolVersion.22
7.8.2 versionInfo .22
7.8.3 versionResponse .23
7.9 Data group Compliance Checking — listOfCCCAttributes and CCCAttributes .23
Annex A (normative) Data type specifications .24
Annex B (normative) Protocol implementation conformance statement (PICS) proforma .25
Annex C (informative) Hierarchical data structure illustration .33
Annex D (informative) Use of this part of ISO 17575 for the EETS .36
Bibliography .38
iv © ISO 2016 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 17575-1:2016(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 on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/TC 204, Intelligent transport systems.
This edition of ISO 17575-1 cancels and replaces ISO/TS 17575-1:2010, which has been technically
revised. The following changes have been made:
— conversion from a Technical Specification to an International Standard;
— amendments to reflect changes to the underlying base standards, especially ISO 14906;
— adoption of security prescriptions previously located in other standards for specification of
authenticated data structures;
— editorial and formal corrections as well as changes to improve readability.
ISO 17575 consists of the following parts, under the general title Electronic fee collection — Application
interface definition for autonomous systems:
— Part 1: Charging
— Part 2: Communication and connection to the lower layers
— Part 3: Context data
In this edition of the ISO 17575-series the contents of ISO/TS 17575-4:2011 were incorporated into
ISO 17575-3:2016. ISO/TS 17575-4:2011 will be withdrawn once ISO 17575-3 has been published.
© ISO 2016 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 17575-1:2016(E)
Introduction
0.1 Autonomous systems
ISO 17575 is a series of standards defining the information exchange between the Front End and the
Back End in electronic fee collection (EFC) based on autonomous on-board equipment (OBE). EFC
systems automatically collect charging data for the use of road infrastructure including motorway
tolls, zone-based fees in urban areas, tolls for special infrastructure like bridges and tunnels, distance-
based charging and parking fees.
Autonomous OBE operates without relying on dedicated road-side infrastructure by employing wide-
area technologies such as Global Navigation Satellite Systems (GNSS) and Cellular Networks (CN). These
EFC systems are referred to by a variety of names. In addition to the terms autonomous systems and
GNSS/CN systems, the terms GPS/GSM systems and wide-area charging systems are also in use.
Autonomous systems use satellite positioning, often combined with additional sensor technologies such
as gyroscopes, odometers and accelerometers, to localize the vehicle and to find its position on a map
containing the charged geographic objects, such as charged roads or charged areas. From the charged
objects, the vehicle characteristics, the time of day and other data that are relevant for describing road
use, the tariff and ultimately the road usage fee are determined.
Two strengths of the autonomous approach to electronic fee collection are its flexibility, allowing
the implementation of almost all conceivable charging principles, and its independence from local
infrastructure, thereby predisposing this technology towards interoperability across charging systems
and countries. Interoperability can only be achieved with clearly defined interfaces, which is the aim
and justification of ISO 17575.
0.2 The parts of ISO 17575
Part 1: Charging, defines the attributes for the transfer of usage data from the Front End to the Back End.
The contents of charge reports might vary between toll regimes, hence, attributes for all requirements
are offered, ranging from attributes for raw localization data, for map-matched geographic objects and
for completely priced toll transactions. A toll regime comprises a set of rules for charging, including the
charged network, the charging principles, the liable vehicles and a definition of the required contents of
the charge report.
Part 2: Communication and connection to lower layers, defines basic communication services for data
transfer over the OBE air-link or between Front End and Back End. The data defined in this part of
ISO 17575-1 and ISO 17575-3 can but need not be exchanged using the communication stack as defined
in ISO 17575-2.
Part 3: Context data, defines the data to be used for a description of individual charging systems in
terms of charged geographical objects and charging and reporting rules. For every toll charger’s system,
attributes as defined in ISO 17575-3 are used to transfer data to the Front End in order to instruct it on
which data to collect and report.
0.3 Application needs covered by ISO 17575
The ISO 17575-series of standards
— is compliant with the architecture defined in ISO 17573:2010,
— supports charges for use of road sections (including bridges, tunnels, passes, etc.), passage of
cordons (entry/exit) and use of infrastructure within an area (depending on distance, time),
— supports fee collection based on units of distance or duration, and based on occurrence of events,
— supports modulation of fees by vehicle category, road category, time of usage and contract type (e.g.
exempt vehicles, special tariff vehicles, etc.),
— supports limiting of fees by a defined maximum per period of usage,
vi © ISO 2016 – All rights reserved
---------------------- Page: 6 ----------------------
ISO 17575-1:2016(E)
— supports fees with different legal status (e.g. public tax, private toll),
— supports differing requirements of different toll chargers, especially in terms of
— geographic domain and context descriptions,
— contents and frequency of charge reports,
— feedback to the driver (e.g. “green” or “red light”), and
— provision of additional detailed data on request, e.g. for settling of disputes,
— supports overlapping geographic toll domains,
— supports adaptations to changes in
— tolled infrastructure,
— tariffs, and
— participating toll schemes, and
— supports the provision of trust guarantees by the toll service provider to the toll charger for the
data originated from the Front End.
© ISO 2016 – All rights reserved vii
---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO 17575-1:2016(E)
Electronic fee collection — Application interface definition
for autonomous systems —
Part 1:
Charging
1 Scope
This part of ISO 17575 defines the format and semantics of the data exchange between a Front End
(OBE plus optional proxy) and corresponding Back Ends in autonomous toll schemes. It defines the data
elements that are used to generate charge reports containing information about the road usage of a
vehicle for certain time intervals, sent from the Front End to the Back End. It also defines the data that
can be used to re-configure the ongoing process of gathering charge relevant information in the Front
End. The scope is shown in Figure 1.
The constitution of the charge report is dependent on configuration data that are assumed to be present
in the Front End. The assembly of charge reports can be configured for each individual toll scheme
according to local needs. Charge reports generated in accordance with this part of ISO 17575 are
consistent with the requirements derived from the architectural concept defined in ISO 17573:2010.
The definitions in this part of ISO 17575 comprise
— reporting data, i.e. data for transferring road usage data from Front End to Back End, including a
response from the Back End towards the Front End,
— data for supporting security mechanisms,
— contract data, i.e. data for identifying contractually essential entities,
— road usage data, i.e. data for reporting the amount of road usage,
— account data for managing a payment account,
— versioning data, and
— compliance checking data, i.e. data imported from ISO 12813:2015, which are required in compliance
checking communication.
Annex A contains the data type specifications using ASN.1 notation.
The protocol implementation conformity statements (PICS) proforma are provided in Annex B.
Annex C provides a graphical presentation of the structure of the data elements described in Clause 7.
Annex D provides information on how this part of ISO 17575 can be used in EETS environment and how
the requirements that are specified in the EU-Decision 2009/750 are addressed by this standard.
© ISO 2016 – All rights reserved 1
---------------------- Page: 8 ----------------------
ISO 17575-1:2016(E)
Figure 1 — Scope of ISO 17575-1
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 6709:2008, Standard representation of geographic point location by coordinates
ISO/IEC 8824-1, Information technology— Abstract Syntax Notation One (ASN.1): Specification of basic
notation — Part 1
ISO/IEC 8825-2:2008, Information technology — ASN.1 encoding rules: Specification of Packed Encoding
Rules (PER) — Part 2
ISO/IEC 9594-8:2014, Information technology — Open Systems Interconnection — The Directory —
Part 8: Public-key and attribute certificate frameworks
ISO 12813:2015, Electronic fee collection— Compliance check communication for autonomous systems
ISO 13141:2015, Electronic fee collection— Localisation augmentation communication for autonomous
systems
ISO 14906:2011/Amd1:2015, Electronic fee collection — Application interface definition for dedicated
short-range communication
ISO 17573:2010, Electronic fee collection — Systems architecture for vehicle-related tolling
2 © ISO 2016 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 17575-1:2016(E)
ISO 17575-3:2016, Electronic fee collection— Application interface definition for autonomous systems—
Part 3: Context data
NIMA TR8350.2, Third Edition — Amendment 1, January 2000, Department of Defense — World
Geodetic System 1984, Its Definition and Relationships With Local Geodetic Systems, issued by National
Imagery and Mapping Agency (NIMA), US Department of Defense
IETF RFC 5035:2007-08, Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
area charging
charging based on road usage within a given area
3.2
attribute
addressable package of data consisting of a single data element or structured sequences of data elements
3.3
authenticator
data, possibly encrypted, that is used for authentication
[SOURCE: EN 15509:2014, 3.3]
3.4
Back End
part of a back office system interfacing to one or more Front Ends (3.12)
3.5
charge object
geographic or road related object for the use of which a charge is applied
3.6
charge report
information containing road usage and related information originated at the Front End (3.12)
3.7
cordon
border line of an area
3.8
cordon charging
charging for the crossing of a cordon (3.7)
3.9
data element
coded information, which might itself consist of lower level information structures
3.10
data group
class of closely related attributes (3.2)
3.11
toll cluster
group of toll schemes operating under a common agreement providing interoperability for road users
having a contract with a toll service provider being part of the cluster
© ISO 2016 – All rights reserved 3
---------------------- Page: 10 ----------------------
ISO 17575-1:2016(E)
3.12
Front End
part of a tolling system consisting of an OBE and possibly a proxy (3.13) where road tolling information
and usage data are collected and processed for delivery to the Back End (3.4)
[SOURCE: ISO/TS 19299:2015, 3.17]
3.13
proxy
optional part of a Front End (3.12) that communicates with external equipment and processes the data
received into an agreed format to be delivered to the Back End (3.4)
3.14
road section charging
tolling principle where the fee is due if predefined sections of roads are used
3.15
tariff modifier
four classes (vehicle class, time class, user class and location class) on w
...
DRAFT INTERNATIONAL STANDARD
ISO/DIS 17575-1
ISO/TC 204 Secretariat: ANSI
Voting begins on: Voting terminates on:
2013-09-26 2014-02-26
Electronic fee collection — Application interface definition
for autonomous systems —
Part 1:
Charging
Perception du télépéage — Définition de l’interface d’application pour les systèmes autonomes —
Partie 1: Imputation
[Revision of first edition (ISO/TS 17575-1:2010) and first edition ISO/TS 17575-1:2010/Cor 1:2013]
ICS: 35.240.60;03.220.20
ISO/CEN PARALLEL PROCESSING
This draft has been developed within the International Organization for
Standardization (ISO), and processed under the ISO lead mode of collaboration
as defined in the Vienna Agreement.
This draft is hereby submitted to the ISO member bodies and to the CEN member
bodies for a parallel five month enquiry.
Should this draft be accepted, a final draft, established on the basis of comments
received, will be submitted to a parallel two-month approval vote in ISO and
THIS DOCUMENT IS A DRAFT CIRCULATED
formal vote in CEN.
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
To expedite distribution, this document is circulated as received from the
IN ADDITION TO THEIR EVALUATION AS
committee secretariat. ISO Central Secretariat work of editing and text
BEING ACCEPTABLE FOR INDUSTRIAL,
composition will be undertaken at publication stage.
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 17575-1:2013(E)
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. ISO 2013
---------------------- Page: 1 ----------------------
ISO/DIS 17575-1:2013(E)
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as
permitted under the applicable laws of the user’s country, neither this ISO draft nor any extract
from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means,
electronic, photocopying, recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to either ISO at the address below or ISO’s
member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO 2013 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/DIS 17575-1
Contents Page
Foreword . v
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviations . 4
5 Procedural requirements . 4
5.1 General . 4
5.2 Charge report configuration . 4
5.3 Charge report response . 5
6 Data elements . 5
6.1 Introduction . 5
6.2 Reporting . 6
6.3 General . 7
6.3.1 vehicleDescription . 7
6.3.2 timeOfReport . 7
6.3.3 reportPeriod . 8
6.3.4 vatForThisSession . 8
6.3.5 transactionCounter . 8
6.3.6 mileage . 8
6.3.7 Distance . 8
6.3.8 Position. 8
6.3.9 Period. 8
6.3.10 Duration . 8
6.3.11 authenticator and responseAuthenticator . 8
6.3.12 MessageAuthenticator . 8
6.4 Contract . 9
6.4.1 obeId . 9
6.4.2 vehicleLPNr . 9
6.4.3 paymentMeans . 9
6.4.4 serviceProviderContract . 9
6.4.5 tollCharger . 9
6.4.6 reportRecipientID . 9
6.4.7 obeStatusForDriver . 9
6.4.8 ObeStatus . 10
6.5 Usage . 10
6.5.1 usageStatementList and UsageStatement . 10
6.5.2 usageStatementID . 10
6.5.3 regimeID . 11
6.5.4 aggregatedFee . 11
6.5.5 aggregatedSingleTariffClassSession . 11
6.5.6 tariffClass . 11
6.5.7 listOfChargeObjects and DetectedChargeObject . 11
6.5.8 ChargeObjectId . 12
6.5.9 ListOfRawUsageData . 12
6.5.10 ListOfDSRCUsageData . 14
6.5.11 additionalUsageInformation . 14
6.5.12 DataReceived . 14
6.6 Account . 14
© ISO 2013 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/DIS 17575-1
6.6.1 accountStatus .14
6.6.2 accountUpdate .15
6.6.3 ReloadAccount .15
6.6.4 NewAccountLimit .15
6.6.5 AddToAccount .15
6.7 Versioning .15
6.7.1 versionInfo .15
6.7.2 versionResponse .16
6.8 Compliance Checking — listOfCCCAttributes and CCCAttributes .16
Annex A (normative) EFC data type specifications .17
Annex B (normative) Protocol implementation conformance statements (PICS) proforma .23
B.1 Introduction .23
B.2 Mandatory data types .23
B.3 Optional data elements .23
B.3.1 ChargeReport .23
B.3.2 ChargeReportResponse .24
B.3.3 UsageStatement .24
B.3.4 Account types .24
Annex C (informative) Hierarchical data structure illustration .25
Annex D (informative) Use of this standard for the EETS .27
D.1 General .27
D.2 Overall relationship between European standardisation and the EETS .27
D.3 European standardisation work supporting the EETS .27
D.4 Correspondence between this standard and the EETS .28
Bibliography .29
iv © ISO 2013 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/DIS 17575-1
Foreword
¾ Part 1: Charging
¾ Part 2: Communication and connection to the lower layers
¾ Part 3: Context data
¾ Part 4: Roaming
Changes in second version of 17575-1
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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
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.
ISO 17575-1 was prepared by Technical Committee ISO/TC 204, Intelligent transport systems, Subcommittee
SC , and by Technical Committee CEN/TC 278, Intelligent transport systems in collaboration.
This second/third/. edition cancels and replaces the first/second/. edition (), [clause(s) / subclause(s) /
table(s) / figure(s) / annex(es)] of which [has / have] been technically revised.
ISO 17575 consists of the following parts, under the general title Electronic fee collection — Application
interface definition for autonomous systems:
¾ Part 1: Charging
¾ Part [n]:
¾ Part [n+1]:
¾ Part 1: Part 1: Charging
¾ Part [n]:
¾ Part [n+1]:
This second edition (ISO 17575-1:2013) of part 1 of ISO 17575 provides the following changes compared to
the previous one:
¾ Correction of several errors also published in the form of corrigenda.
© ISO 2013 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/DIS 17575-1
¾ Adaptation to new versions of other standards, especially ISO 14906.
¾ Several minor technical and editorial improvements, with emphasis on backward compatibility with the first
version of ISO 17575.
¾ Conversion into a full Standard. The first version was a Technical Specification.
vi © ISO 2013 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/DIS 17575-1
Introduction
Autonomous systems
This part of ISO 17575 is part of a series of specifications defining the information exchange between the
Front End and the Back End in Electronic Fee Collection (EFC) based on autonomous on-board equipment
(OBE). EFC systems automatically collect charging data for the use of road infrastructure including motorway
tolls, zone-based fees in urban areas, tolls for special infrastructure like bridges and tunnels, distance-based
charging and parking fees.
Autonomous OBE operates without relying on dedicated road-side infrastructure by employing wide-area
technologies such as Global Navigation Satellite Systems (GNSS) and Cellular Communications Networks
(CN). These EFC systems are referred to by a variety of names. Besides the terms autonomous systems and
GNSS/CN systems, also the terms GPS/GSM systems, and wide-area charging systems are in use.
Autonomous systems use satellite positioning, often combined with additional sensor technologies such as
gyroscopes, odometers and accelerometers, to localize the vehicle and to find its position on a map containing
the charged geographic objects, such as charged roads or charged areas. From the charged objects, the
vehicle characteristics, the time of day and other data that are relevant for describing road use, the tariff and
ultimately the road usage fee are determined.
Some of the strengths of the autonomous approach to electronic fee collection are its flexibility, allowing the
implementation of almost all conceivable charging principles, and its independence from local infrastructure,
thereby predisposing this technology towards interoperability across charging systems and countries.
Interoperability can only be achieved with clearly defined interfaces, which is the aim and justification of
ISO 17575.
Business architecture
This part of ISO 17575 complies with the business architecture defined in the draft of the International
Standard ISO 17573. According to this architecture, the Toll Charger is the provider of the road infrastructure
and, hence, the recipient of the road usage charges. The Toll Charger is the actor associated with the Toll
Charging role. See Figure 1.
Figure 1 - The role-based model underlying this Standard
Service Providers issue OBE to the users of the road infrastructure. Service Providers are responsible for
operating the OBE that will record the amount of road usage in all toll charging systems the vehicle passes
© ISO 2013 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/DIS 17575-1
through and for delivering the charging data to the individual Toll Chargers. In general, each Service Provider
delivers charging data to several Toll Chargers, as well as each Toll Charger in general receives charging
data from more than one Service Provider. Interoperability Management in Figure 1 comprises all
specifications and activities that in common define and maintain a set of rules that govern the overall toll
charging environment.
Technical architecture
The technical architecture of Figure 2 is independent of any particular practical realization. It reflects the fact
that some processing functionalities can either be allocated to the OBE or to an associated off-board
component (Proxy). An example of processing functionality that can be realized either on- or off-board is map-
matching, where the vehicle locations in terms of measured coordinates from GNSS are associated to
geographic objects on a map that either resides on- or off-board. Also tariff determination can be done with
OBE tariff tables and processing, or with an off-board component.
Figure 2 - Assumed technical architecture and interfaces
The combined functionality of OBE and Proxy is denoted as Front End. A Front End implementation where
processing is predominately on OBE-side is known as a smart client (or intelligent client, fat client) or edge-
heavy. A Front End where processing is mostly done off-board is denoted as thin-client or edge-light
architecture. Many implementations between the "thin" and "thick" extremes are possible, as depicted by the
gradual transition in the wedges in Figure 2. Both extremes of architectural choices have their merits and are
one means where manufacturers compete with individual allocations of functionality between on-board and
central resources.
Especially for thin client OBE, manufacturers might devise a wide variety of optimizations of the transfer of
localization data between OBE and off-board components, where proprietary algorithms are used for data
reduction and data compression. Standardization of this transfer is neither fully possible nor beneficial.
Location of the specification interface
In order to abstract from, and become independent of, these architectural implementation choices, the primary
scope of ISO 17575 is the data exchange between Front End and Back End (see the corresponding dotted
line in Figure 2). For every toll regime, the Back End will send context data, i.e. a description of the toll regime
in terms of charged objects, charging rules and, if required, the tariff scheme to the Front End, and will receive
usage data from the Front End.
viii © ISO 2013 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/DIS 17575-1
It has to be noted also that the distribution of tasks and responsibilities between Service Provider and Toll
Charger will vary individually. Depending on the local legal situation, Toll Chargers will require "thinner" or
"thicker" data, and might or might not leave certain data processing tasks to Service Providers. Hence, the
data definitions in ISO 17575 may be useful on several interfaces.
ISO 17575 also provides for basic media-independent communication services that may be used for
communication between Front End and Back End, which might be line-based or an air-link, and can also be
used for the air-link between OBE and central communication server.
The parts of ISO 17575
Part 1: Charging, defines the attributes for the transfer of usage data from the Front End to the Back End. The
required attributes will differ from one Toll Charger to another, hence, attributes for all requirements are
offered, ranging from attributes for raw localization data, for map-matched geographic objects and for
completely priced toll transactions.
Part 2: Communication and connection to lower layers, defines basic communication services for data transfer
over the OBE air-link or between Front End and Back End.
Part 3: Context Data, defines the data to be used for a description of individual charging systems in terms of
charged geographical objects and charging and reporting rules. For every Toll Charger's system, attributes as
defined in part 3 are used to transfer data to the Front End in order to instruct it which data to collect and
report.
Part 4: Roaming, defines the functional details and data elements required to operate more than one EFC
regime in parallel. The domains of these EFC regimes may or may not overlap. The charge rules of different
overlapping EFC regimes can be linked, i.e. they may include rules that an area charging scheme will not be
charged if an overlapping toll road is used and already paid for.
Figure 3 — Scope of ISO 17575
© ISO 2013 – All rights reserved ix
---------------------- Page: 9 ----------------------
ISO/DIS 17575-1
Application needs covered by ISO 17575
¾ The parts of ISO 17575 are compliant with the architecture defined in the international Standard
ISO 17573.
¾ The parts of ISO 17575 support charges for use of road sections (including bridges, tunnels, passes, etc.),
passage of cordons (entry/exit) and use of infrastructure within an area (distance, time).
¾ The parts of ISO 17575 support fee collection based on units of distance or duration, and based on
occurrence of events.
¾ The parts of ISO 17575 support modulation of fees by vehicle category, road category, time of usage and
contract type (e.g. exempt vehicles, special tariff vehicles, etc.).
¾ The parts of ISO 17575 support limiting of fees by a defined maximum per period of usage.
¾ The parts of ISO 17575 support fees with different legal status (e.g. public tax, private toll).
¾ The parts of ISO 17575 support differing requirements of different Toll Chargers, especially in terms of
· geographic domain and context descriptions,
· contents and frequency of charge reports,
· feedback to the driver (e.g. green or red light),
· provision of additional detailed data on request, e.g. for settling of disputes.
¾ The parts of ISO 17575 support overlapping geographic toll domains.
¾ The parts of ISO 17575 support adaptations to changes in
· tolled infrastructure,
· tariffs, and
· participating regimes.
¾ The parts of ISO 17575 support the provision of trust guarantees by the Service Provider to the Toll
Charger for the data originated from the Front End.
x © ISO 2013 – All rights reserved
---------------------- Page: 10 ----------------------
DRAFT INTERNATIONAL STANDARD ISO/DIS 17575-1
Electronic fee collection — Application interface definition for
autonomous systems — Part 1: Charging
1 Scope
This part of ISO 17575 defines the format and semantic of the data exchange between a Front End (OBE plus
optional proxy) and corresponding Back Ends in autonomous toll regimes. This part of ISO 17575 deals with
the definition of the data elements used to report charging details from the Front End to the Back End and to
receive data which can be used to re-configure the ongoing process of gathering charge relevant information
in the Front End.
The constitution of the charge report is dependent on configuration data that are assumed to be present in the
Front End. The assembly of charge reports can be configured for each individual toll regime according to local
needs. Charge reports generated in accordance with this part of ISO 17575 are consistent with the
requirements derived from the current architectural concept favoured in the relevant standardization bodies as
defined in ISO 17573.
The data defined in this part of ISO 17575 are used to generate charge reports that contain information about
the road usage of a vehicle for certain time intervals. The contents of these charge reports might vary between
toll regimes. A toll regime comprises a set of rules for charging, including the charged network, the charging
principles, the liable vehicles and a definition of the required contents of the charge report.
The data defined in this part of ISO 17575 are exchanged using an open definition of a communication stack
as defined in ISO 17575 2.
The definitions in this part of ISO 17575 comprise:
¾ reporting data, i.e. data for transferring road usage data from Front End to Back End, including a response
from the Back End towards the Front End;
¾ contract data, i.e. data for identifying contractually essential entities;
¾ road usage data, i.e. data for reporting the amount of road usage;
¾ account data for managing a payment account;
¾ versioning data;
¾ compliance checking data, i.e. data imported from ISO 12813, which are required in Compliance
Checking Communications.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For the remainder of this document undated references to the
documents below always refer to the dated versions listed in this clause.
ISO 6709:2008, Standard representation of geographic point location by coordinates
© ISO 2013 – All rights reserved 1
---------------------- Page: 11 ----------------------
ISO/DIS 17575-1
ISO/IEC 8824-1:2008, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic
notation — Part 1
ISO/IEC 8825-2:2008, Information technology — ASN.1 encoding rules: Specification of Packed Encoding
Rules (PER) — Part 2
ISO 12813:2014, Electronic fee collection - Compliance check communication for autonomous systems
ISO 12855:2014, Electronic fee collection - Information exchange between service provision and toll charging
ISO 14906:2011, Electronic fee collection - Application interface definition for dedicated short-range
communication
CEN/TS 16331:2012, Electronic fee collection - Interoperable application profiles for autonomous systems
ISO 17573:2010, Electronic fee collection - Systems architecture for vehicle related tolling
ISO 17575-2:2014, Electronic fee collection - Application interface definition for autonomou
...
NORME ISO
INTERNATIONALE 17575-1
Première édition
2016-01-15
Perception du télépéage — Définition
de l’interface d’application pour les
systèmes autonomes —
Partie 1:
Imputation
Electronic fee collection — Application interface definition for
autonomous systems —
Part 1: Charging
Numéro de référence
ISO 17575-1:2016(F)
©
ISO 2016
---------------------- Page: 1 ----------------------
ISO 17575-1:2016(F)
DOCUMENT PROTÉGÉ PAR COPYRIGHT
© ISO 2016, Publié en Suisse
Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni utilisée
sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie, l’affichage sur
l’internet ou sur un Intranet, sans autorisation écrite préalable. Les demandes d’autorisation peuvent être adressées à l’ISO à
l’adresse ci-après ou au comité membre de l’ISO dans le pays du demandeur.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – Tous droits réservés
---------------------- Page: 2 ----------------------
ISO 17575-1:2016(F)
Sommaire Page
Avant-propos .v
Introduction .vi
1 Domaine d’application . 1
2 Références normatives . 2
3 Termes et définitions . 3
4 Abréviations . 5
5 Considérations architecturales . 6
5.1 Architecture commerciale . 6
5.2 Architecture technique . 7
5.3 Emplacement de l’interface de spécification . 8
6 Spécifications relatives aux procédures . 8
6.1 Généralités . 8
6.2 Perception du péage . 8
6.3 Rapport de perception . 9
6.4 Réponse à un rapport de perception .10
7 Eléments de données .10
7.1 Vue d’ensemble des éléments de données .10
7.2 Etablissement de rapports .11
7.2.1 ChargeReport (rapport de perception) .11
7.2.2 ChargeReportResponse (réponse au rapport de perception) .12
7.3 Groupe de données Général .12
7.3.1 timeOfReport (date et heure du rapport) .12
7.3.2 reportPeriod (période du rapport) .12
7.3.3 sumVatForThisSession (TVA pour cette session) .12
7.3.4 chargeReportCounter (compteur de rapport de perception) .13
7.3.5 mileage (kilométrage) .13
7.3.6 Distance .13
7.3.7 Position .13
7.3.8 Period (période) .13
7.3.9 Duration (durée) .13
7.4 Groupe de données Sécurité .14
7.4.1 AuthenticatedChargeReport (rapport de perception authentifié) .14
7.4.2 AuthenticatedChargeReportResponse (réponse au rapport de
perception authentifié) .14
7.4.3 AuthenticatedUsageStatement (déclaration d’utilisation authentifiée) .14
7.4.4 AuthenticatedReloadAccount (recharge du compte authentifié) .14
7.4.5 AuthenticatedNewAccountLimit (limite de compte nouveau authentifiée) .14
7.4.6 AuthenticatedAddToAccount (ajout au compte authentifié) .15
7.4.7 MessageAuthenticator (authentifiant de message) .15
7.4.8 MacMessageAuthenticator (authentificateur de message mac) .15
7.4.9 MessageAuthenticatorEfc (EFC d’authentificateur de message) .15
7.5 Groupe de données Contrat .15
7.5.1 obeId (ID de l’OBE) .15
7.5.2 vehicleLPNr (n° d’immatriculation du véhicule) .15
7.5.3 paymentMeans (moyen de paiement) .16
7.5.4 serviceProviderContract (contrat du fournisseur de services) .16
7.5.5 tollContext (contexte de péage) .16
7.5.6 chargeReportFinalRecipient (destinataire final du rapport de perception) .16
7.5.7 obeStatusForDriver (statut de l’OBE pour le conducteur) .16
7.5.8 obeStatus (statut de l’OBE) .17
7.5.9 chargeReportRespSender (expéditeur de la réponse au rapport de perception) 17
7.6 Groupe de données Utilisation .17
© ISO 2016 – Tous droits réservés iii
---------------------- Page: 3 ----------------------
ISO 17575-1:2016(F)
7.6.1 usageStatementList (liste des déclarations d’utilisation) .17
7.6.2 UsageStatement (déclaration d’utilisation) .17
7.6.3 usageStatementID (ID de déclaration d’utilisation).18
7.6.4 aggregatedFee (redevance agrégée) .18
7.6.5 aggregatedSingleTariffClassSession (session de classe tarifaire
unique agrégée) .18
7.6.6 currentTariffClass (classe tarifaire actuelle) .19
7.6.7 VehicleDescription (description du véhicule) .19
7.6.8 listOfChargeObjects (liste d’objets d’imputation) et DetectedChargeObject
(objet d’imputation détecté) . .19
7.6.9 ChargeObjectId (ID d’objet d’imputation) .20
7.6.10 ListOfRawUsageData (liste des données d’utilisation brutes),
measuredRawData (données brutes mesurées) .20
7.6.11 NmeaData (données NMEA) .21
7.6.12 additionalGnssData (données GNSS supplémentaires) .22
7.6.13 ListOfDSRCUsageData (liste des données d’utilisation DSRC) .22
7.6.14 additionalUsageInformation (informations supplémentaires
concernant l’utilisation) .22
7.6.15 DataReceived (données reçues) .22
7.7 Groupe de données Compte .23
7.7.1 accountStatus (statut du compte) .23
7.7.2 accountUpdate (mise à jour du compte) .23
7.7.3 reloadAccount (recharge du compte) .23
7.7.4 setAccount (définir le compte) .23
7.7.5 addToAccount (ajout au compte) .24
7.8 Groupe de données Contrôle des versions.24
7.8.1 protocolVersion (version du protocole) .24
7.8.2 versionInfo (informations concernant la version) .24
7.8.3 versionResponse (réponse à la version) .24
7.9 Groupe de données Contrôle de conformité — listOfCCCAttributes (liste des
attributs CCC) et CCCAttributes (attributs CCC) .24
Annexe A (normative) Spécifications des types de données .26
Annexe B (normative) Formulaire de déclarations de conformité d’implémentation de
protocole (PICS).27
Annexe C (informative) Illustration de la structure hiérarchique des données .36
Annexe D (informative) Utilisation de la présente partie de l’ISO 17575 pour le SET .39
Bibliographie .41
iv © ISO 2016 – Tous droits réservés
---------------------- Page: 4 ----------------------
ISO 17575-1:2016(F)
Avant-propos
L’ISO (Organisation internationale de normalisation) est une fédération mondiale d’organismes
nationaux de normalisation (comités membres de l’ISO). L’élaboration des Normes internationales est
en général confiée aux comités techniques de l’ISO. Chaque comité membre intéressé par une étude
a le droit de faire partie du comité technique créé à cet effet. Les organisations internationales,
gouvernementales et non gouvernementales, en liaison avec l’ISO participent également aux travaux.
L’ISO collabore étroitement avec la Commission électrotechnique internationale (IEC) en ce qui
concerne la normalisation électrotechnique.
Les procédures utilisées pour élaborer le présent document et celles destinées à sa mise à jour sont
décrites dans les Directives ISO/IEC, Partie 1. Il convient, en particulier de prendre note des différents
critères d’approbation requis pour les différents types de documents ISO. Le présent document a été
rédigé conformément aux règles de rédaction données dans les Directives ISO/IEC, Partie 2 (voir www.
iso.org/directives).
L’attention est appelée sur le fait que certains des éléments du présent document peuvent faire l’objet de
droits de propriété intellectuelle ou de droits analogues. L’ISO ne saurait être tenue pour responsable
de ne pas avoir identifié de tels droits de propriété et averti de leur existence. Les détails concernant
les références aux droits de propriété intellectuelle ou autres droits analogues identifiés lors de
l’élaboration du document sont indiqués dans l’Introduction et/ou dans la liste des déclarations de
brevets reçues par l’ISO (voir www.iso.org/brevets).
Les appellations commerciales éventuellement mentionnées dans le présent document sont données
pour information, par souci de commodité, à l’intention des utilisateurs et ne sauraient constituer
un engagement.
Pour une explication de la signification des termes et expressions spécifiques de l’ISO liés à
l’évaluation de la conformité, ou pour toute information au sujet de l’adhésion de l’ISO aux principes
de l’OMC concernant les obstacles techniques au commerce (OTC), voir le lien suivant: Avant-propos —
Informations supplémentaires.
L’ISO 17575-1 a été élaborée par le comité technique ISO/TC 204, Systèmes intelligents de transport.
Cette deuxième édition annule et remplace la première édition (ISO/TS 17575-1:2010), qui fait l’objet
d’une révision technique.
L’ISO 17575 comprend les parties suivantes, présentées sous le titre général Perception du télépéage —
Définition de l’interface d’application pour les systèmes autonomes:
— Partie 1: Imputation
— Partie 2: Communications et connexions aux couches basses
— Partie 3: Données du contexte
Dans la présente édition de l’ISO 17575:2016, le contenu de la norme ISO/TS 17575-4:2011 a été
incorporé à la norme ISO 17575-3:2016. La norme ISO/TS 17575-4:2011 sera retirée lorsque la norme
ISO 17575-3 aura été publiée.
© ISO 2016 – Tous droits réservés v
---------------------- Page: 5 ----------------------
ISO 17575-1:2016(F)
Introduction
0.1 Systèmes autonomes
L’ISO 17575 est une série de normes relatives à l’échange d’informations entre le système frontal et le
système central des applications de perception de télépéage (EFC, Electronic Fee Collection) reposant
sur un équipement embarqué (OBE, On-Board Equipment) autonome. Les systèmes EFC collectent
automatiquement les données de perception relatives à l’utilisation d’une infrastructure routière,
comprenant les péages d’autoroute, les redevances dans certaines zones urbaines, les péages relatifs
à une infrastructure particulière telles que ponts et tunnels, les imputations basées sur la distance
parcourue et les frais de stationnement.
Un OBE autonome fonctionne sans s’appuyer sur une infrastructure dédiée en bord de route en faisant
appel à des technologies à couverture étendue telles que les systèmes mondiaux de navigation par
satellite (GNSS) et les réseaux cellulaires (CN). Ces systèmes EFC ont diverses dénominations. Outre les
termes «systèmes autonomes» et «systèmes GNSS/CN», les termes «systèmes GPS/GSM» et «systèmes
de localisation par satellite» sont également utilisés.
Les systèmes autonomes utilisent la localisation par satellite, souvent combinée à des technologies de
détection supplémentaires telles que des gyroscopes, des odomètres et des accéléromètres, pour localiser
le véhicule et trouver sa position sur une carte contenant les objets géographiques soumis à redevance, tels
que des routes ou des zones soumises à péage. A partir des objets soumis à redevance, des caractéristiques
du véhicule, de l’heure de la journée et d’autres données pertinentes pour décrire l’utilisation du réseau
routier, le tarif et finalement la redevance d’utilisation du réseau routier sont déterminés.
Ces systèmes EFC autonomes présentent une réelle flexibilité permettant d’implémenter presque
tous les principes d’imputation existants et ne dépendent pas de l’infrastructure routière favorisant
l’interopérabilité de cette technologie dans les pays et les systèmes de perception. L’interopérabilité
ne peut être obtenue qu’avec des interfaces clairement définies, ce qui est l’objectif et la justification
de l’ISO 17575.
0.2 Parties de l’ISO 17575
Partie 1: Imputation, définit les attributs pour le transfert des données d’utilisation du système frontal
au système central. Le contenu des rapports de perception peut varier d’un régime de péage à l’autre; la
présente partie fournit en conséquence des attributs pour toutes les exigences, y compris des attributs
pour les données brutes de localisation, pour les objets géographiques de repérage cartographique et
pour les transactions de péage dont le prix est fixé. Un régime de péage comprend un ensemble de règles
d’imputation, y compris le réseau soumis à péage, les principes d’imputation, les véhicules assujettis au
péage et une définition du contenu exigé du rapport de perception.
Partie 2: Communications et connexions aux couches basses, définit les services de communication de base
pour le transfert des données sur la liaison aérienne de l’OBE ou entre le système frontal et le système
central. Les données définies dans la présente partie de l’ISO 17575-1 et de l’ISO 17575-3 peuvent être
échangées au moyen d’une pile de communication telle que définie dans l’ISO 17575-2, mais cet échange
n’est pas nécessaire.
Partie 3: Données du contexte, définit les données à utiliser pour la description de chaque système
de perception en termes d’objets géographiques soumis à redevance et de règles d’imputation et
d’établissement de rapports. Pour chaque système de percepteur de péage, les attributs définis dans la
norme ISO 17575-3 sont utilisés pour transférer des données vers le système frontal afin de lui indiquer
quelles données il doit collecter et utiliser pour générer des rapports.
0.3 Besoins en termes d’application couverts par l’ISO 17575
La série de normes ISO 17575
— est conforme à l’architecture définie dans l’ISO 17573:2010,
vi © ISO 2016 – Tous droits réservés
---------------------- Page: 6 ----------------------
ISO 17575-1:2016(F)
— traite des redevances liées à l’utilisation de tronçons de route (y compris ponts, tunnels, passages,
etc.), au franchissement de cordons (entré/sortie) et à l’utilisation d’une infrastructure dans une
zone (distance, temps),
— traite de la perception d’un péage fondée sur des unités de distance ou de durée, et fondée sur
l’occurrence d’événements,
— traite de la modulation des redevances par catégorie de véhicule, catégorie de route, durée
d’utilisation et type de contrat (par exemple véhicules exemptés, véhicules à tarif spécial, etc.),
— traite de la limitation des redevances par un maximum défini par période d’utilisation,
— traite des redevances ayant un statut juridique différent (par exemple taxe publique, péage privé),
— traite des exigences variables des différents percepteurs de péage, notamment en termes de
— descriptions du domaine géographique et du contexte,
— contenu et fréquence des rapports de perception,
— retour d’information au conducteur (par exemple feu vert ou rouge), et
— fourniture de données détaillées supplémentaires sur demande, par exemple pour le
règlement des litiges,
— traite des domaines géographiques de péage se chevauchant,
— traite des adaptations relatives aux changements
— d’infrastructure à péage,
— de tarifs, et
— fait partie de systèmes de péage, et
— traite de la fourniture par le prestataire de services au percepteur de péage de garanties de confiance
pour les données provenant du système frontal.
© ISO 2016 – Tous droits réservés vii
---------------------- Page: 7 ----------------------
NORME INTERNATIONALE ISO 17575-1:2016(F)
Perception du télépéage — Définition de l’interface
d’application pour les systèmes autonomes —
Partie 1:
Imputation
1 Domaine d’application
La présente partie de l’ISO 17575 définit le format et la sémantique pour l’échange de données entre
un système frontal (OBE plus proxy optionnel) et des systèmes centraux correspondants dans des
systèmes de péage autonomes. Elle définit les éléments de données utilisés pour générer des rapports
de perception contenant des informations sur l’utilisation du réseau routier par un véhicule pendant
des intervalles de temps donnés, envoyées du système frontal au système central. Elle définit également
les données qui peuvent être utilisées pour reconfigurer le processus de collecte permanente des
informations d’imputation pertinentes dans le système frontal. Son domaine d’application est
représenté à la Figure 1.
La constitution d’un rapport de perception dépend des données de configuration supposées être
présentes dans le système frontal. L’ensemble des rapports de perception peut être configuré pour
chaque système de péage individuel selon les besoins locaux. Les rapports de perception générés
conformément à la présente partie de l’ISO 17575 concordent avec les exigences dérivées du concept
architectural défini dans l’ISO 17573:2010.
Dans la présente partie de l’ISO 17575, les définitions comprennent
— les données des rapports, c’est-à-dire les données permettant de transférer des données d’utilisation
du réseau routier d’un système frontal à un système central, y compris une réponse du système
central au système frontal,
— les données de prise en charge des mécanismes de sécurité,
— les données contractuelles, c’est-à-dire les données permettant d’identifier les entités
contractuellement essentielles,
— les données d’utilisation du réseau routier, c’est-à-dire les données permettant de communiquer
l’utilisation qui est faite du réseau routier,
— les données de compte pour gérer un compte de paiement,
— les données de contrôle des versions,
— les données de contrôle de conformité, c’est-à-dire les données importées de l’ISO 12813:2015, qui
sont requises dans les communications de contrôle de conformité.
L’Annexe A donne la spécification du type de données dans la notation ASN.1.
Les formulaires PICS (déclaration de conformité d’implémentation de protocole) sont fournis en Annexe B.
L’Annexe C comprend une représentation graphique de la structure des éléments de données décrits
à l’Article 7.
L’Annexe D fournit des informations sur la façon dont la présente partie de l’ISO 17575 peut être
appliquée dans un environnement SET et sur la manière dont la présente norme couvre les exigences
spécifiées dans la Décision de la Commission 2009/750.
© ISO 2016 – Tous droits réservés 1
---------------------- Page: 8 ----------------------
ISO 17575-1:2016(F)
Anglais Français
Scope of the ISO 17575- series Domaine d’application de la série de normes ISO 17575
Back End Système central
Back End Application Application du système central
Back End calls Appel du système central
communication Functions for EFC Fonctions de communication pour l’EFC
communication service primitives Primitives de service de communication
ADU ADU
Front End Système frontal
Front End Application Application du système frontal
Front End calls Appel du système frontal
communication Functions for EFC Fonctions de communication pour l’EFC
communication service primitives Primitives de service de communication
data communication service Service de communication de données
Figure 1 — Domaine d’application de l’ISO 17575-1
2 Références normatives
Les documents ci-après, dans leur intégralité ou non, sont des références normatives indispensables à
l’application du présent document. Pour les références datées, seule l’édition citée s’applique. Pour les
références non datées, la dernière édition du document de référence s’applique (y compris les éventuels
amendements).
2 © ISO 2016 – Tous droits réservés
---------------------- Page: 9 ----------------------
ISO 17575-1:2016(F)
ISO 6709:2008, Représentation normalisée de la localisation des points géographiques par coordonnées
ISO/IEC 8824-1, Technologies de l’information — Notation de syntaxe abstraite numéro un (ASN.1):
Spécification de la notation de base — Partie 1
ISO/IEC 8825-2:2008, Technologies de l’information — Règles de codage ASN.1: Spécification des règles de
codage compact (PER) — Partie 2
ISO/IEC 9594-8:2014, Technologies de l’information — Interconnexion de systèmes ouverts (OSI) —
L’annuaire — Partie 8: Cadre général des certificats de clé publique et d’attribut
ISO 12813:2015, Perception du télépéage — Communication de contrôle de conformité pour systèmes
autonomes
ISO 13141:2015, Perception de télépéage — Communications d’augmentation de localisations pour
systèmes autonomes
ISO 14906:2011/Amd1:2015, Perception du télépéage — Définition de l’interface d’application relative aux
communications dédiées à courte portée
ISO 17573:2010, Perception du télépéage — Architecture de systèmes pour le péage lié aux véhicules
ISO 17575-3:2016, Perception du télépéage — Définition de l’interface d’application pour les systèmes
autonomes — Partie 3: Données du contexte
NIMA TR8350.2, Third Edition — Amendment 1, January 2000, Department of Defense — World
Geodetic System 1984, Its Definition and Relationships With Local Geodetic Systems, issued by National
Imagery and Mapping Agency (NIMA), US Department of Defense (disponible en anglais seulement)
IETF RFC 5035:2007-08, Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility
(disponible en anglais seulement)
3 Termes et définitions
Pour les besoins du présent document, les termes et définitions suivants s’appliquent.
3.1
péage de zone
péage basé sur l’utilisation du réseau routier dans une zone donnée
3.2
attribut
ensemble de données adressables consistant en un élément de données unique ou des séquences
structurées d’éléments de donnée
3.3
authentifiant
données (pouvant être chiffrées) qui sont utilisées à des fins d’authentification
[SOURCE: EN 15509:2014, 3.3]
3.4
système central
partie du système de back-office assurant l’interface avec un ou plusieurs systèmes frontaux (3.12)
3.5
objet d’imputation
ob
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.