2004/52/EC - Interoperability of electronic road toll systems in the Community

This document defines requirements for short-range communication for the purposes of compliance checking in autonomous electronic fee collecting systems. Compliance checking communication (CCC) takes place between a road vehicle's on-board equipment (OBE) and an interrogator (roadside mounted equipment, mobile device or hand-held unit), and serves to establish whether the data that are delivered by the OBE correctly reflect the road usage of the corresponding vehicle according to the rules of the pertinent toll regime. The operator of the compliance checking interrogator is assumed to be part of the toll charging role as defined in ISO 17573-1. The CCC permits identification of the OBE, vehicle and contract, and verification of whether the driver has fulfilled his obligations and the checking status and performance of the OBE. The CCC reads, but does not write, OBE data. This document is applicable to OBE in an autonomous mode of operation; it is not applicable to compliance checking in dedicated short-range communication (DSRC)-based charging systems. It defines data syntax and semantics, but not a communication sequence. All the attributes defined herein are required in any OBE claimed to be compliant with this document, even if some values are set to “not defined” in cases where certain functionality is not present in an OBE. The interrogator is free to choose which attributes are read in the data retrieval phase, as well as the sequence in which they are read. In order to achieve compatibility with existing systems, the communication makes use of the attributes defined in ISO 14906 wherever useful. The CCC is suitable for a range of short-range communication media. Specific definitions are given for the CEN-DSRC as specified in EN 15509, as well as for the use of ISO CALM IR, the Italian DSRC as specified in ETSI ES 200 674-1, ARIB DSRC and WAVE DSRC as alternatives to the CEN-DSRC. The attributes and functions defined are for compliance checking by means of the DSRC communication services provided by DSRC application layer, with the CCC attributes and functions made available to the CCC applications at the roadside equipment (RSE) and OBE. The attributes and functions are defined on the level of application data units (ADU).

This document defines requirements for short-range communication for the purposes of compliance checking in autonomous electronic fee collecting systems. Compliance checking communication (CCC) takes place between a road vehicle's on-board equipment (OBE) and an interrogator (roadside mounted equipment, mobile device or hand-held unit), and serves to establish whether the data that are delivered by the OBE correctly reflect the road usage of the corresponding vehicle according to the rules of the pertinent toll regime.
The operator of the compliance checking interrogator is assumed to be part of the toll charging role as defined in ISO 17573-1. The CCC permits identification of the OBE, vehicle and contract, and verification of whether the driver has fulfilled his obligations and the checking status and performance of the OBE. The CCC reads, but does not write, OBE data.
This document is applicable to OBE in an autonomous mode of operation; it is not applicable to compliance checking in dedicated short-range communication (DSRC)-based charging systems.
It defines data syntax and semantics, but not a communication sequence. All the attributes defined herein are required in any OBE claimed to be compliant with this document, even if some values are set to "not defined" in cases where certain functionality is not present in an OBE. The interrogator is free to choose which attributes are read in the data retrieval phase, as well as the sequence in which they are read. In order to achieve compatibility with existing systems, the communication makes use of the attributes defined in ISO 14906 wherever useful.
The CCC is suitable for a range of short-range communication media. Specific definitions are given for the CEN-DSRC as specified in EN 15509, as well as for the use of ISO CALM IR, the Italian DSRC as specified in ETSI ES 200 674-1, ARIB DSRC and WAVE DSRC as alternatives to the CEN-DSRC. The attributes and functions defined are for compliance checking by means of the DSRC communication services provided by DSRC application layer, with the CCC attributes and functions made available to the CCC applications at the roadside equipment (RSE) and OBE. The attributes and functions are defined on the level of application data units (ADU).
The definition of the CCC includes:
— the application interface between OBE and RSE (as depicted in Figure 2);
— use of the generic DSRC application layer as specified in ISO 15628 and EN 12834;
— CCC data type specifications given in Annex A;
— a protocol implementation conformance statement (PICS) proforma is given in Annex B;
— use of the CEN-DSRC stack as specified in EN 15509, or other equivalent DSRC stacks as described in Annex C, Annex D, Annex E and Annex F;
— security services for mutual authentication of the communication partners and for signing of data (see Annex H);
— an example CCC transaction is presented in Annex G;
— the informative Annex I highlights how to use this document for the European electronic toll service (as defined in Commission Decision 2009/750/EC).
Test specifications are not within the scope of this document.

This document defines the architecture of toll system environments in which a customer with one contract may use a vehicle in a variety of toll domains and with a different Toll Charger for each domain.
Toll systems conforming to this document may be used for various purposes including road (network) tolling, area tolling, collecting toll for bridges, tunnels, ferries, for access, for parking. From a technical point of view the considered toll systems use electronic equipment on-board of a vehicle.
The actual collection of the toll, i.e. collecting payments, is outside of the scope of this document.
The architecture in this document is defined with no more details than those required for an overall overview, a common language, an identification of the need for and interactions among other standards, and the drafting of these standards.
This document as a whole provides:
• The enterprise view on the architecture, which is concerned with the purpose, scope and policies governing the activities of the specified system within the organization of which it is a part.
• Terms and definitions for common use in a toll environment
• A decomposition of the toll systems environment into its main enterprise objects
• The roles and responsibilities of the main actors
• Identification of the provided services by means of action diagrams that underline the needed standardised exchanges
• Identification of interoperability interfaces and related standards

This document defines the architecture of electronic fee collection (EFC) system environments, in which a customer with one contract may use a vehicle in a variety of toll domains with a different toll charger for each domain.
EFC systems conforming to this document can be used for various purposes including road (network) tolling, area tolling, collecting fees for the usage of bridges, tunnels, ferries, for access or for parking. From a technical point of view the considered toll systems may identify vehicles subject to tolling by means of electronic equipment on-board in a vehicle or by other means (e.g. automatic number plate recognition, ANPR).
From a process point of view the architectural description focuses on toll determination, toll charging, and the associated enforcement measures. The actual collection of the toll, i.e. collecting payments, is outside of the scope of this document.
The architecture in this document is defined with no more details than required for an overall overview, a common language, an identification of the need for and interactions among other standards, and the drafting of these standards.
This document as a whole provides:
— the enterprise view on the architecture, which is concerned with the purpose, scope and policies governing the activities of the specified system within the organization of which it is a part;
— the terms and definitions for common use in an EFC environment;
— a decomposition of the EFC systems environment into its main enterprise objects;
— the roles and responsibilities of the main actors. This document does not impose that all roles perform all indicated responsibilities. It should also be clear that the responsibilities of a role may be shared between two or more actors. Mandating the performance of certain responsibilities is the task of standards derived from this architecture;
— identification of the provided services by means of action diagrams that underline the needed standardised exchanges;
— identification of the interoperability interfaces for EFC systems, in specialised standards (specified or to be specified).

This document provides a suite of tests in order to assess the central equipment of toll chargers and toll service providers for compliancy towards the requirements listed in CEN/TS 16986. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific Test Purposes defined in FprCEN/TS 17154-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).

This document provides a suite of tests in order to assess the central equipment of toll chargers and toll service providers for compliancy towards the requirements listed in CEN/TS 16986. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific Test Purposes defined in FprCEN/TS 17154-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).

This document specifies the test suite structure (TSS) and test purposes (TP) to test conformity of central equipment of both toll chargers and toll service providers versus CEN/TS 16986.
It further provides templates for the protocol conformance test reports (PCTR) for the implementation under tests (IUT) for both the toll charger and the toll service provider.
This document contains the technical provisions to perform conformance testing of functional and dynamic behaviour of implementations conforming to CEN/TS 16986.
NOTE   The specifications in this Part provide the base for the tree and tabular combined notation (TTCN) of the test cases and steps which are provided in CEN/TS 17154 2.

This document provides a suite of tests in order to assess the central equipment of toll chargers and toll service providers for compliancy towards the requirements listed in CEN/TS 16986. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific Test Purposes defined in CEN/TS 17154-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).

The ISO 16410 series provides a suite of tests in order to assess the Front End (FE) and Back End (BE)
behaviour’s compliancy towards the requirements listed in ISO 17575-3. This document contains
the definition of such tests in the form of test cases, reflecting the required individual steps listed in
specific test purposes defined in ISO 16410-1. The test cases are written in Testing and Test Control
Notation version 3 (TTCN v3).

The ISO 16407 series provides a suite of tests in order to assess the Front End (FE) and Back End
(BE) behaviour compliancy towards the requirements listed in ISO 17575-1. This document contains
the definition of such tests in the form of test cases, reflecting the required individual steps listed in
specific test purposes defined in ISO 16407-1. The test cases are written in Testing and Test Control
Notation version 3 (TTCN v3).

This document specifies the application interface in the context of electronic fee collection (EFC) systems using the dedicated short-range communication (DSRC).

The ISO 16407 series provides a suite of tests in order to assess the Front End (FE) and Back End (BE) behaviour compliancy towards the requirements listed in ISO 17575‑1. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific test purposes defined in ISO 16407‑1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).

The ISO 16410 series provides a suite of tests in order to assess the Front End (FE) and Back End (BE) behaviour's compliancy towards the requirements listed in ISO 17575‑3. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific test purposes defined in ISO 16410‑1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).

This document contains the definition of test cases, reflecting the individual steps listed in specific test
purposes defined in ISO/TR 16401-1. The test cases are written in Testing and Test Control Notation
version 3 (TTCN-3).

This document defines the data transfer models between roadside equipment (RSE) and integrated
circuit card (ICC) and the interface descriptions between the RSE and on-board equipment (OBE) for
on-board accounts using the ICC. It also provides examples of interface definitions and transactions
deployed in several countries.
This document covers:
— data transfer models between the RSE and ICC which correspond to the categorized operational
requirements and the data transfer mechanism for each model;
— interface definition between the RSE and OBE based on each data transfer model;
— interface definition for each model;
— functional configuration;
— RSE command definitions for ICC access;
— data format and data element definitions of RSE commands;
— a transaction example for each model in Annex B.

The ISO 16410 series provides a suite of tests in order to assess compliance of the Front End and Back
End behaviours in relation to the requirements in ISO 17575-3. This document contains the definition of
such tests in the form of test purposes, listing the required initial conditions, references and individual
steps in a structured textual manner. ISO 16410-2 contains the identical tests written in testing and
test control notation version 3 (TTCN v3).
The test purposes defined in this document reflect the structural and semantic requirements stated in
ISO 17575-3.
— Presence/absence of particular data elements (see ISO 17575-3:2016, 8.5.5);
— Semantics related to various data elements, e.g.:
— Activation of context data and handling multiple contexts (see ISO 17575-3:2016, 8.3);
— Handling the precedence and priority levels (see ISO 17575-3:2016, 8.5.2 to 8.5.4);
— Uniqueness of relevant data elements (see ISO 17575-3:2016, 8.5.2 to 8.5.4);
— Correct definition of the charge objects (see ISO 17575-3:2016, 8.5.4);
— Fee calculation algorithm (see ISO 17575-3:2016, 8.5.3.7);
— Security (see ISO 17575-3:2016, 7.2).
With regard to the individual data sets and EFC attributes defined in ISO 17575-3, the test purposes
have been organized into the test suite groups, designated for the Front End and Back End respectively.
In addition to the test purposes, this document also provides proforma conformance test report
templates for both the Front End and Back End test purposes and an informative statement on the
usage of this document for the European electronic toll service (EETS).
For more information regarding the requirements against which the conformance is evaluated in this
document, refer to ISO 17575-3.
Testing of the following behaviours and functionalities is outside the scope of this document:
— dynamic behaviour, i.e. sequence of messages and triggering events that must be exchanged/happen
to fulfil certain charging scenarios;
— profiles and business logic built on top of particular pricing schemas;
— behaviour invalid of Front End and Back End, BI test purposes are not applicable for any test purpose
group (as ISO 17575-3 does not specify behaviour invalid).

ISO/TR 16401-2:2018 contains the definition of test cases, reflecting the individual steps listed in specific test purposes defined in ISO/TR 16401-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN-3).

This document defines the Examination Framework for the measurement of charging performance
metrics defined in ISO/TS 17444-1 to be used during Evaluation and/or on-going Monitoring.
It specifies a method for the specification and documentation of a Specific Examination Framework
which can be used by the responsible entity to evaluate charging performance for a particular
information exchange interface or for overall charging performance within a Toll Scheme.
It provides a toolbox of Examination Tests for the roles of Toll Charger and Toll Service Provider for the
following Scheme types:
a) DSRC Discrete;
b) Autonomous Discrete;
c) Autonomous Continuous.
The detailed choice of the set of examination tests to be used depends on the application and the
respective context. Compliance with this specification is understood as using the definitions and
prescriptions laid out in this document whenever the respective system aspects are subjected to
performance measurements, rather than using other definitions and examination methods than the
ones specified in this document.
The following aspects are outside the scope of this document.
— This document does not propose specific numeric performance bounds, or average or worst-case
error bounds in percentage or monetary units. Those decisions are left to the Toll Charger (or
to agreements between Toll Charger and Service Provider).This document does not consider the
evaluation of the expected performance of a system based on modelling and measured data from
trial at another place.
— This document does not consider the specification of a common reference system which would be
required for comparison of performance between systems.
— This document defines measurements only on standardized interfaces. Proprietary interfaces
are excluded, because it is not possible to define standardized metrics on such system properties.
These excluded interfaces are among others the link between Toll Charger RSE and central systems
in DSRC systems, and the additional sensor input of GNSS modules (inertial sensors, CAN-bus for
wheel ticks, etc.).

This document defines metrics for the charging performance of electronic fee collection (EFC) systems
in terms of the level of errors associated with charging computation.
This document is a toolbox standard of metrics. The detailed choice of metrics depends on the
application and the respective context.
This document describes a set of metrics with appropriate definitions, principles and formulations,
which together make up a reference framework for the establishment of requirements for EFC systems
and their later examination of the charging performance.
The charging performance metrics defined in this document are intended for use with any Charging
Scheme, regardless of its technical underpinnings, system architecture, tariff structure, geographical
coverage, or organizational model. They are defined to treat technical details that can be different
among technologies and vendors or vary over time as a “black box”.
They focus solely on the outcome of the charging process, i.e. the amount charged in relation to a premeasured
or theoretically correct amount, rather than intermediate variables from various components
as sensors, such as positioning accuracy, signal range, or optical resolution. This approach ensures
comparable results for each metric in all relevant situations.
The metrics are designed to cover the information exchanged on the Front End interface and the
interoperability interfaces between Toll Service Providers, Toll Chargers and Road Users as well as on
the End-to-End level.
Metrics on the following information exchanges are defined:
— Charge Reports;
— Toll Declarations;
— Billing Details and associated event data;
— Payment Claims on the level of toll service user accounts;
— User Accounts;
— End-to-End Metrics which assess the overall performance of the charging process.
The details on the rationale of this choice are described in 5.1.
The proposed metrics are specifically addressed to protect the interests of the actors in a toll system,
such as Toll Service Providers, Toll Chargers and Road Users. The metrics can be used to define
requirements (e.g. for requests for proposals) and for performance assessment.
This document recognises two types of situations where a performance assessment is necessary:
a) when an assessment is carried out during a limited time span, such as when formulating
requirements and assessing systems for acquisition purposes, conducting acceptance testing as
assessment is referred to as an evaluation;
b) when an assessment is needed as an ongoing supervision process, throughout the lifetime of
a system, in order to validate contracted service levels, to identify fraud or malfunction, or to
support ongoing maintenance and performance improvement processes. This type of assessment is
referred to as monitoring.

The ISO 16410 series provides a suite of tests in order to assess compliance of the Front End and Back End behaviours in relation to the requirements in ISO 17575‑3. ISO 16410-1:2017 contains the definition of such tests in the form of test purposes, listing the required initial conditions, references and individual steps in a structured textual manner. ISO 16410‑2 contains the identical tests written in testing and test control notation version 3 (TTCN v3).
The test purposes defined in ISO 16410-1:2017 reflect the structural and semantic requirements stated in ISO 17575‑3.
- Presence/absence of particular data elements (see ISO 17575‑3:2016, 8.5.5);
- Semantics related to various data elements, e.g.:
- Activation of context data and handling multiple contexts (see ISO 17575‑3:2016, 8.3);
- Handling the precedence and priority levels (see ISO 17575‑3:2016, 8.5.2 to 8.5.4);
- Uniqueness of relevant data elements (see ISO 17575‑3:2016, 8.5.2 to 8.5.4);
- Correct definition of the charge objects (see ISO 17575‑3:2016, 8.5.4);
- Fee calculation algorithm (see ISO 17575‑3:2016, 8.5.3.7);
- Security (see ISO 17575‑3:2016, 7.2).
With regard to the individual data sets and EFC attributes defined in ISO 17575‑3, the test purposes have been organized into the test suite groups, designated for the Front End and Back End respectively.
In addition to the test purposes, ISO 16410-1:2017 also provides proforma conformance test report templates for both the Front End and Back End test purposes and an informative statement on the usage of ISO 16410-1:2017 for the European electronic toll service (EETS).
For more information regarding the requirements against which the conformance is evaluated in ISO 16410-1:2017, refer to ISO 17575‑3.
Testing of the following behaviours and functionalities is outside the scope of ISO 16410-1:2017:
- dynamic behaviour, i.e. sequence of messages and triggering events that must be exchanged/happen to fulfil certain charging scenarios;
- profiles and business logic built on top of particular pricing schemas;
- behaviour invalid of Front End and Back End, BI test purposes are not applicable for any test purpose group (as ISO 17575‑3 does not specify behaviour invalid).

ISO 25110:2017 defines the data transfer models between roadside equipment (RSE) and integrated circuit card (ICC) and the interface descriptions between the RSE and on-board equipment (OBE) for on-board accounts using the ICC. It also provides examples of interface definitions and transactions deployed in several countries.

ISO/TS 17444-2:2017 defines the Examination Framework for the measurement of charging performance metrics defined in ISO/TS 17444‑1 to be used during Evaluation and/or on-going Monitoring.
It specifies a method for the specification and documentation of a Specific Examination Framework which can be used by the responsible entity to evaluate charging performance for a particular information exchange interface or for overall charging performance within a Toll Scheme.
It provides a toolbox of Examination Tests for the roles of Toll Charger and Toll Service Provider for the following Scheme types:
a) DSRC Discrete;
b) Autonomous Discrete;
c) Autonomous Continuous.
The detailed choice of the set of examination tests to be used depends on the application and the respective context. Compliance with this specification is understood as using the definitions and prescriptions laid out in ISO/TS 17444-2:2017 whenever the respective system aspects are subjected to performance measurements, rather than using other definitions and examination methods than the ones specified in ISO/TS 17444-2:2017.
The following aspects are outside the scope of ISO/TS 17444-2:2017.
- ISO/TS 17444-2:2017 does not propose specific numeric performance bounds, or average or worst-case error bounds in percentage or monetary units. Those decisions are left to the Toll Charger (or to agreements between Toll Charger and Service Provider). ISO/TS 17444-2:2017 does not consider the evaluation of the expected performance of a system based on modelling and measured data from trial at another place.
- ISO/TS 17444-2:2017 does not consider the specification of a common reference system which would be required for comparison of performance between systems.
- ISO/TS 17444-2:2017 defines measurements only on standardized interfaces. Proprietary interfaces are excluded, because it is not possible to define standardized metrics on such system properties. These excluded interfaces are among others the link between Toll Charger RSE and central systems in DSRC systems, and the additional sensor input of GNSS modules (inertial sensors, CAN-bus for wheel ticks, etc.).

ISO/TS 17444-1:2017 defines metrics for the charging performance of electronic fee collection (EFC) systems in terms of the level of errors associated with charging computation.
ISO/TS 17444-1:2017 is a toolbox standard of metrics. The detailed choice of metrics depends on the application and the respective context.
ISO/TS 17444-1:2017 describes a set of metrics with appropriate definitions, principles and formulations, which together make up a reference framework for the establishment of requirements for EFC systems and their later examination of the charging performance.
The charging performance metrics defined in ISO/TS 17444-1:2017 are intended for use with any Charging Scheme, regardless of its technical underpinnings, system architecture, tariff structure, geographical coverage, or organizational model. They are defined to treat technical details that can be different among technologies and vendors or vary over time as a "black box".
They focus solely on the outcome of the charging process, i.e. the amount charged in relation to a pre-measured or theoretically correct amount, rather than intermediate variables from various components as sensors, such as positioning accuracy, signal range, or optical resolution. This approach ensures comparable results for each metric in all relevant situations.
The metrics are designed to cover the information exchanged on the Front End interface and the interoperability interfaces between Toll Service Providers, Toll Chargers and Road Users as well as on the End-to-End level.

This Technical Specification defines an application interface definition by selecting suitable options from the base standard EN ISO 12855:2015. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between TCs and TSPs.
This Technical Specification covers:
-   exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
-   charging related data (exception lists, toll declarations, billing details, payment claims);
-   administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
-   confirmation data.
-   transfer mechanisms and supporting functions;
-   semantics of data elements;
-   implementation conformance statement proforma (Annex A), as a basis for assessment of conformity to this Technical Specification;
-   an Interoperability statement proforma (Annex B), as a basis for assessment of transactional intereoperability of two technical implementations;
-   a web service definition (Annex C) for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered. Therefore, outside of the scope is in particular:
-   details on how to achieve security using the authenticator data elements of the base standards;
-   how to operate compliance checking and the enforcement process;
-   commercial aspects;
-   definition of non-functional features such as performance indicators like accuracy, availability and reporting requirements.
This Technical Specification further provides an assessment of support of the EETS (Annex D) and an explanation how to read the unified modelling language (UML) diagrams (Annex E) that are used in this document.

This Technical Specification defines an application interface definition by selecting suitable options from the base standard EN ISO 12855:2015. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between TCs and TSPs.
This Technical Specification covers:
-   exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
-   charging related data (exception lists, toll declarations, billing details, payment claims);
-   administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
-   confirmation data.
-   transfer mechanisms and supporting functions;
-   semantics of data elements;
-   implementation conformance statement proforma (Annex A), as a basis for assessment of conformity to this Technical Specification;
-   an Interoperability statement proforma (Annex B), as a basis for assessment of transactional intereoperability of two technical implementations;
-   a web service definition (Annex C) for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered. Therefore, outside of the scope is in particular:
-   details on how to achieve security using the authenticator data elements of the base standards;
-   how to operate compliance checking and the enforcement process;
-   commercial aspects;
-   definition of non-functional features such as performance indicators like accuracy, availability and reporting requirements.
This Technical Specification further provides an assessment of support of the EETS (Annex D) and an explanation how to read the unified modelling language (UML) diagrams (Annex E) that are used in this document.

This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity
of on-board units (OBU) and roadside equipment (RSE) to ISO 13141.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment
(on-board units and roadside units) to enable interoperability between different equipment supplied by
different manufacturers.

This European Standard specifies the abstract test suite (ATS) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to EN 15509 in accordance with the test suite structure and test purposes defined in EN 15876-1:2016.
The objective of the present document is to provide a basis for conformance tests for DSRC equipment (OBE and RSE) to support interoperability between different equipment supplied by different manufacturers.

The objective of this document is to provide a basis for conformance tests for DSRC equipment (on board units and roadside units) to support interoperability between different equipment supplied by different manufacturers.

This Technical Specification defines an application interface definition by selecting suitable options from the base standard ISO 12855:2015. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between TCs and TSPs.
This Technical Specification covers:
   exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
   charging related data (exception lists, toll declarations, billing details, payment claims);
   administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
   confirmation data.
   transfer mechanisms and supporting functions;
   semantics of data elements;
   implementation conformance statement proforma (Annex A), as a basis for assessment of conformity to this Technical Specification;
   an Interoperability statement proforma (Annex B), as a basis for assessment of transactional intereoperability of two technical implementations;
   a web service definition (Annex C) for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered. Therefore, outside of the scope is in particular:
   details on how to achieve security using the authenticator data elements of the base standards;
   how to operate compliance checking and the enforcement process;
   commercial aspects;
   definition of non-functional features such as performance indicators like accuracy, availability and reporting requirements.
This Technical Specification further provides an assessment of support of the EETS (Annex D) and an explanation how to read the UML diagrams that are used (Annex E).

ISO 13140-1:2016 specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of on-board units (OBU) and roadside equipment (RSE) to ISO 13141.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment (on-board units and roadside units) to enable interoperability between different equipment supplied by different manufacturers.

This European Standard specifies the abstract test suite (ATS) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to EN 15509 in accordance with the test suite structure and test purposes defined in EN 15876-1:2016.
The objective of the present document is to provide a basis for conformance tests for DSRC equipment (OBE and RSE) to support interoperability between different equipment supplied by different manufacturers.

The objective of this document is to provide a basis for conformance tests for DSRC equipment (on board units and roadside units) to support interoperability between different equipment supplied by different manufacturers.

This Technical Specification defines an application interface definition by selecting suitable options from the base standard EN ISO 12855:2015. Furthermore, it defines transfer mechanisms and supporting functions to ensure the interoperability between TCs and TSPs.
This Technical Specification covers:
-   exchange of information between the central equipment associated with the two roles service provision and toll charging, e.g.:
-   charging related data (exception lists, toll declarations, billing details, payment claims);
-   administrative data (trust objects, EFC context data, contact details for enforcement, etc.);
-   confirmation data.
-   transfer mechanisms and supporting functions;
-   semantics of data elements;
-   implementation conformance statement proforma (Annex A), as a basis for assessment of conformity to this Technical Specification;
-   an Interoperability statement proforma (Annex B), as a basis for assessment of transactional intereoperability of two technical implementations;
-   a web service definition (Annex C) for the use of web services as communication technology.
The implementation of the underlying back office systems and their business processes is not covered. Therefore, outside of the scope is in particular:
-   details on how to achieve security using the authenticator data elements of the base standards;
-   how to operate compliance checking and the enforcement process;
-   commercial aspects;
-   definition of non-functional features such as performance indicators like accuracy, availability and reporting requirements.
This Technical Specification further provides an assessment of support of the EETS (Annex D) and an explanation how to read the unified modelling language (UML) diagrams (Annex E) that are used in this document.

This part of ISO 17575 defines how to convey all or parts of the data element structure defined in other parts of ISO 17575 over any communication stack and media suitable for this application. It is applicable monly to mobile communication links (although wired links, i.e. back office connections, can use the same methodology).
To establish a link to a sequence of service calls initializing the communication channel, addressing the reception of the message and forwarding the payload are required. The definition provided in this part of ISO 17575 includes the required communication medium independent services, represented by an abstract application programming interface (API).
The communication interface is implemented as an API in the programming environment of choice for the Front End (FE) system. The specification of the Back End (BE) API is outside the scope of this part of ISO 17575.
The definition of this API in concrete terms is outside of the scope of this part of ISO 17575. This part of ISO 17575 specifies an abstract API that defines the semantics of the concrete API as illustrated in Figure 3 and its protocol implementation conformance statement (PICS) proforma (see Annex B). An example of a concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs, the term “communications API” or just “API” can be used.

This part of ISO 17575 defines the content, semantics and format of the data exchange between a Front End (OBE plus optional proxy) and the corresponding Back End in autonomous toll systems. It defines the data elements used to specify and describe the toll context details. Context data are transmitted from the Back End to the Front End to configure it for the charging processes of the associated toll context.
In ISO 17575, context data is the description of the properties of a single instance of an electronic fee collection (EFC) context. This single instance of an EFC context operates according to one of the basic
tolling principles such as
— road section charging,
— area charging (according to travelled distance or duration of time), and
— cordon charging.
EFC context data comprise a set of rules for charging, including the description of the charged network, the charging principles, the liable vehicles and a definition of the required contents of the charge report.
This set of rules is defined individually for each EFC context according to local needs.
The following data and associated procedures are defined in this part of ISO 17575:
— data providing toll context overview information;
— data providing tariff information (including definitions of required tariff determinants such as
vehicle parameters, time classe, etc.);
— data providing context layout information;
— data providing reporting rules information.
This part of ISO 17575 also provides the required definitions and data specifications to be applied when one single toll context is spilt inot more than one toll context partitions. This is applicable to cases where one EFC scheme and the rules applied cannot be described with a single set of context data.
Annex A provides the data type specification 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 toll context data.
Annexes D, E and F contain further information and descriptions, which may support the understanding and the implementation of the rules specified in this part of ISO 17575.
Annex G provides information how this part of ISO 17575 can be used in a European Electronic Toll Service (EETS) environment, with reference to EU Decision 2009/750.

This International Standard establishes requirements for short-range communication for the purposes
of augmenting the localization in autonomous electronic fee collection (EFC) systems. Localization
augmentation serves to inform on-board equipment (OBE) about geographical location and the
identification of a charge object. This International Standard specifies the provision of location and
heading information and security means to protect from the manipulation of the OBE with false
roadside equipment (RSE).
The localization augmentation communication takes place between an OBE in a vehicle and fixed roadside
equipment. This International Standard is applicable to OBE in an autonomous mode of operation.
This International Standard defines attributes and functions for the purpose of localization
augmentation, by making use of the dedicated short-range communications (DSRC) communication
services provided by DSRC Layer 7, and makes these LAC attributes and functions available to the LAC
applications at the RSE and the OBE. Attributes and functions are defined on the level of Application
Data Units (ADUs, see Figure 1).
As depicted in Figure 1, this International Standard is applicable to:
— the application interface definition between OBE and RSE;
— the interface to the DSRC application layer, as specified in ISO 15628 and EN 12834;
— the use of the DSRC stack.
The localization augmentation communication is suitable for a range of short-range communication
media. This International Standard gives specific definitions regarding the CEN DSRC stack as specified
in EN 15509, and Annexes C, D and E give the use of the Italian DSRC as specified in ETSI/ES 200 674-1,
ISO CALM IR, and ARIB DSRC.
This International Standard contains a protocol implementation conformance statement (PICS)
proforma in Annex B and informative transaction examples in Annex F. The informative Annex G
highlights how to use this International Standard for the European electronic toll service (as defined in
Commission Decision 2009/750/EC).
Test specifications are not within the scope of this International Standard.

ISO 17575-3:2016 defines the content, semantics and format of the data exchange between a Front End (OBE plus optional proxy) and the corresponding Back End in autonomous toll systems. It defines the data elements used to specify and describe the toll context details. Context data are transmitted from the Back End to the Front End to configure it for the charging processes of the associated toll context.
In ISO 17575, context data is the description of the properties of a single instance of an electronic fee collection (EFC) context. This single instance of an EFC context operates according to one of the basic tolling principles such as
- road section charging,
- area charging (according to travelled distance or duration of time), and
- cordon charging.
EFC context data comprise a set of rules for charging, including the description of the charged network, the charging principles, the liable vehicles and a definition of the required contents of the charge report. This set of rules is defined individually for each EFC context according to local needs.
The following data and associated procedures are defined in this part of ISO 17575:
- data providing toll context overview information;
- data providing tariff information (including definitions of required tariff determinants such as vehicle parameters, time classe, etc.);
- data providing context layout information;
- data providing reporting rules information.
ISO 17575-3:2016 also provides the required definitions and data specifications to be applied when one single toll context is spilt inot more than one toll context partitions. This is applicable to cases where one EFC scheme and the rules applied cannot be described with a single set of context data.
Annex A provides the data type specification 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 toll context data.
Annexes D, E and F contain further information and descriptions, which may support the understanding and the implementation of the rules specified in this part of ISO 17575.
Annex G provides information how this part of ISO 17575 can be used in a European Electronic Toll Service (EETS) environment, with reference to EU Decision 2009/750.

ISO 17575-2:2016 defines how to convey all or parts of the data element structure defined in other parts of ISO 17575 over any communication stack and media suitable for this application. It is applicable only to mobile communication links (although wired links, i.e. back office connections, can use the same methodology).
To establish a link to a sequence of service calls initializing the communication channel, addressing the reception of the message and forwarding the payload are required. The definition provided in this part of ISO 17575 includes the required communication medium independent services, represented by an abstract application programming interface (API).
The communication interface is implemented as an API in the programming environment of choice for the Front End (FE) system. The specification of the Back End (BE) API is outside the scope of this part of ISO 17575.
The definition of this API in concrete terms is outside of the scope of this part of ISO 17575. This part of ISO 17575 specifies an abstract API that defines the semantics of the concrete API as illustrated in Figure 3 and its protocol implementation conformance statement (PICS) proforma (see Annex B). An example of a concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs, the term "communications API" or just "API" can be used.
ISO 17575-2:2016 also provides a detailed specification for the structure of associated API statements, an example on how to implement it and its role in a complex toll cluster such as the EETS (see Annex A to Annex E).
Media selection policies, certificate handling and encryption mechanisms are outside of the scope of this part of ISO 17575.

ISO 13141:2015 establishes requirements for short-range communication for the purposes of augmenting the localization in autonomous electronic fee collection (EFC) systems. Localization augmentation serves to inform on-board equipment (OBE) about geographical location and the identification of a charge object. This International Standard specifies the provision of location and heading information and security means to protect from the manipulation of the OBE with false roadside equipment (RSE).
The localization augmentation communication takes place between an OBE in a vehicle and fixed roadside equipment. This International Standard is applicable to OBE in an autonomous mode of operation.
ISO 13141:2015 defines attributes and functions for the purpose of localization augmentation, by making use of the dedicated short-range communications (DSRC) communication services provided by DSRC Layer 7, and makes these LAC attributes and functions available to the LAC applications at the RSE and the OBE. Attributes and functions are defined on the level of Application Data Units (ADUs, see Figure 1).

This Technical Report (TR) contains an analysis of the technical and operational feasibility of using a generic ITS Station as specified in ETSI EN 302 665, Intelligent Transport Systems (ITS); Communications Architecture, for EFC applications compliant to the requirements specified in ISO 17573, EN ISO 12855, CEN ISO/TS 17575 (all parts), EN ISO 14906, EN 15509, CEN ISO/TS 12813, CEN ISO/TS 13141 and CEN/TS 16439.
The scope of this Technical Report includes:
-   description of the context of Cooperative ITS and the ITS Stations;
-   providing details of the context of EFC applications;
-   outlining the basic architectural concepts and role model of both EFC and Cooperative ITS;
-   identification of core requirement areas for operation of an EFC application on an ITS Station;
-   specification of a set of recommendations for functional, operational and security requirements to the ITS Station supporting the EFC application(s);
-   description of a possible role model in which the roles known in EFC applications make use of the roles in the C-ITS system in order to provide EFC services in an C-ITS context;
-   provision of considerations in particular areas of EFC like certification and governances;
-   guideless and recommendations for further standardization work in this area;
-   emphasising on security related elements of EFC that need to be considered in a C-ITS environment.
The scope of this Technical Report is limited to in-vehicle ITS Stations. However, an EFC service always requires the involvement of in-vehicle and central functionalities. Furthermore, for enforcement purposes as well as in DSRC based toll domains for toll charging purposes also, it is essential that road-side based functions are provided and operated. In order to facilitate EFC services a set of functionalities, tasks and responsibilities are defined and specified in an EFC role model (ISO 17573). These functionalities, tasks and responsibilities are shared between the roles Toll Charger, Toll Service Provider, Road User and Interoperability Management. All these roles interact with each other. As a consequence this Technical Report provides in various areas explanations that are beyond the in-vehicle environment. This is required in order to present the full environment and context. It keeps the readability of this document at a sound level and provides valuable information to those readers which are not yet familiar with EFC in detail.
Outside the scope of this Technical Report is:
-   detailed technical specifications for EFC services and applications on C-ITS systems;
-   implementation specific elements.

This Technical Report (TR) contains an analysis of the technical and operational feasibility of using a generic ITS Station as specified in ETSI EN 302 665, Intelligent Transport Systems (ITS); Communications Architecture, for EFC applications compliant to the requirements specified in ISO 17573, EN ISO 12855, CEN ISO/TS 17575 (all parts), EN ISO 14906, EN 15509, CEN ISO/TS 12813, CEN ISO/TS 13141 and CEN/TS 16439.
The scope of this Technical Report includes:
-   description of the context of Cooperative ITS and the ITS Stations;
-   providing details of the context of EFC applications;
-   outlining the basic architectural concepts and role model of both EFC and Cooperative ITS;
-   identification of core requirement areas for operation of an EFC application on an ITS Station;
-   specification of a set of recommendations for functional, operational and security requirements to the ITS Station supporting the EFC application(s);
-   description of a possible role model in which the roles known in EFC applications make use of the roles in the C-ITS system in order to provide EFC services in an C-ITS context;
-   provision of considerations in particular areas of EFC like certification and governances;
-   guideless and recommendations for further standardization work in this area;
-   emphasising on security related elements of EFC that need to be considered in a C-ITS environment.
The scope of this Technical Report is limited to in-vehicle ITS Stations. However, an EFC service always requires the involvement of in-vehicle and central functionalities. Furthermore, for enforcement purposes as well as in DSRC based toll domains for toll charging purposes also, it is essential that road-side based functions are provided and operated. In order to facilitate EFC services a set of functionalities, tasks and responsibilities are defined and specified in an EFC role model (ISO 17573). These functionalities, tasks and responsibilities are shared between the roles Toll Charger, Toll Service Provider, Road User and Interoperability Management. All these roles interact with each other. As a consequence this Technical Report provides in various areas explanations that are beyond the in-vehicle environment. This is required in order to present the full environment and context. It keeps the readability of this document at a sound level and provides valuable information to those readers which are not yet familiar with EFC in detail.
Outside the scope of this Technical Report is:
-   detailed technical specifications for EFC services and applications on C-ITS systems;
-   implementation specific elements.

This Technical Specifications defines the specific use of a set of base standards for Interoperable application profiles for autonomous EFC systems.
The set of base standards includes CEN ISO/TS 17575-suite, EN ISO 17573, EN ISO 12855, CEN ISO/TS 13141 and CEN ISO/TS 12813. The standard will specify details on how to use the mentioned base standards to achieve interoperability among EFC schemes with Service providers using CEN ISO/TS 17575 compatible front ends.
The standard will also define the rules for using optional elements to provide a consistent definition of specific EFC domain properties. It will also include the definition of the consistent use of identifiers and other data elements throughout all applied base standards including references to other standards providing means to achieve security and privacy.
This standard will be consistent with and is intended to provide support for the technical specification of the European Electronic Toll Service laid down in the European Directive 2004/52/EC and the subsequent Decision 2009/750/EC.
This includes consideration of the findings of European projects specifying the commercial set-up of organisations, their responsibilities and the interactions among them.
Outside the scope are:
-   the details on how to achieve security using the authenticator data elements of the base standards;
-   how to operate the enforcement process ;
-   commercial aspects ;
-   the handling of DSRC charging domains ;
the definition of non-functional features such as performance indicators like accuracy, availability and reporting requirements. These definitions are seen as part of the bilateral agreements between involved actors or other profile standards.

This Technical Specification defines a set of interoperable application profiles suitable to be used defining the overall functionality of an interoperable EFC cluster using autonomous vehicle equipment. Doing so, it also defines a way of defining further profiles for future use.
The profiles cover a wide range from simple toll road systems up to very complex tolling principles and tariff rules. An EFC cluster shall select and use one of these profiles covering the needs of all participating Toll Chargers.
The scope is limited to those base standards providing data elements or messages to be used specifically when defining the data exchange for autonomous tolling principles. This covers ISO 17573 and the base standards CEN ISO/TS 17575 parts 1 to 4, CEN ISO/TS 12813, CEN ISO/TS 13141 and those parts of
EN ISO 12855 specifying messages which are only relevant for autonomous systems.
Figure 3 provides a graphical illustration of the scope of this Interoperable Application Profile which is based on the ISP concept according to ISO IEC/TR 10000-1.
For each specified profile, the conditional requirements resulting from the actual use of data elements being still optional according to this profile are specified in Annex A. A set of rules on how to re-use identifiers of a specific entity within the full chain of transactions is specified in Annex B and a protocol implementation conformance statement (PICS) proforma in Annex C.
Outside of the scope are:
- details on how to achieve security using the authenticator data elements of the base standards;
- how to operate the enforcement process;
- commercial aspects and the billing process;
- the handling of DSRC charging transactions;
- system monitoring and performance indicators;
- test standards;
- the initial configuration of the OBE.

2016-01-26: WI cancelled following cancellation of equivalent ISO WI (ISO notification in dataservice on 2016-01-19).

2016-01-26: WI cancelled following cancellation of equivalent ISO WI (ISO notification in dataservice on 2016-01-19).

This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity
of on-board units (OBU) and roadside equipment (RSE) to ISO 12813:2015.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment
(on-board units and roadside units) to enable interoperability between different equipment supplied by
different manufacturers.