ISO/TC 204/WG 5 - Fee and toll collection

This document specifies the application interface in the context of electronic fee collection (EFC) systems using dedicated short-range communication (DSRC). The EFC application interface is the EFC application process interface to the DSRC application layer, as can be seen in Figure 1. This document comprises specifications of: — EFC attributes (i.e. EFC application information) that can also be used for other applications and/or interfaces; — the addressing procedures of EFC attributes and (hardware) components (e.g. integrated circuit(s) card); — EFC application functions, i.e. further qualification of actions by definitions of the concerned services, assignment of associated ActionType values, and content and meaning of action parameters; — the EFC transaction model, which defines the common elements and steps of any EFC transaction; — the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level. This is an interface standard, adhering to the open systems interconnection (OSI) philosophy (see ISO/IEC 7498-1), and it is as such not primarily concerned with the implementation choices to be realized at either side of the interface. This document provides security-specific functionality as place holders (data and functions) to enable the implementation of secure EFC transactions. Yet the specification of the security policy (including specific security algorithms and key management) remains at the discretion and under the control of the EFC operator, and hence is outside the scope of this document.

This document specifies: — the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control; — an exchange of information between the back end system of the two roles of service provision and toll charging, e.g.: — charging-related data (toll declarations, billing details), — administrative data, and — confirmation data; — transfer mechanisms and supporting functions; — information objects, data syntax and semantics. This document is applicable for any vehicle-related toll service and any technology used for charging. The data types and associated coding related to the data elements described in Clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824‑1. This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions). This document does not specify, amongst others: — any communication between toll charger (TC) or toll service provider (TSP) with any other involved party; — any communication between elements of the TC and the TSP that is not part of the back-office communication; — interfaces for EFC systems for public transport; — any complex transfers (transactions), i.e. sequences of inter-related application data units (ADUs) that can possibly involve several application protocol data unit (APDU) exchanges; — processes regarding payments and exchanges of fiscal, commercial or legal accounting documents; and — definitions of service communication channels, protocols and service primitives to transfer the APDUs.

This document specifies: personalization interface; physical systems: on-board equipment (OBE), personalization equipment (PE) and integrated circuit(s) cards (ICCs); electronic fee collection (EFC) personalization functions between the PE and the OBE in accordance with ISO/TS 21719-1 when using an ICC; data and security elements that are transferred between the PE and the OBE using the ICC. It is outside the scope of this document to define: conformance procedures and test specifications; setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party, etc.); legal issues; the exact commands and security functionality within ISO/IEC 7816-4 used by the PE and the OBE, respectively, to interface an ICC. NOTE Some of the issues that are outside the scope of this document are the subject of separate standards prepared by CEN/TC 278 and ISO/TC 204.

This document describes tests which verify on-board unit (OBU) conformance of functions and data structures implementations, as defined in the implementation conformance statement (ICS) based on ISO 14906 for EFC applications. This document defines tests for assessing OBU conformance in terms of : — basic dedicated short-range communication (DSRC) L7 functionality, — EFC application functions, — EFC attributes (i.e. EFC application information), — the addressing procedures of EFC attributes and (hardware) components, — the EFC transaction model, which defines the common elements and steps of any EFC transaction, and — the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface level. After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing a complete EFC transaction (C.3). Although this document defines examples of test cases for DSRC and EFC functionality (see Annex C), it does not intend to specify a complete test suite for a certain implementation. To compose a test suite for a specific EFC implementation, the test cases can be modified and new test cases can be defined and added in order for the conformance test suite to be complete. It can be useful to consider the following when defining a complete test suite: — small range: "exhaustive testing" of critical interoperability/compatibility features, — large range: testing of boundaries and random values, and — composite types: testing of individual items in sequence or parallel. This document does not define tests which assess: — performance, — robustness, and — reliability of an implementation. NOTE 1 ISO 14907‑1 defines test procedures that are aimed at assessing performance, robustness and reliability of EFC equipment and systems. NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and related devices that can be relevant for OBUs which support such cards. Annex D provides an informative overview of Japanese on-board equipment (OBE) conformance tests which are based on the ISO 14907 series, in order to illustrate how these can be applied in practice.

This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813. It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and RSE to support interoperability between different equipment supplied by different manufacturers. ISO 12813 defines requirements on the compliance check communication (CCC) interface level, but not for the RSE or OBE internal functional behaviour. Consequently, tests regarding OBE and/or RSE functional behaviour remain outside the scope of this document.

This document defines an information security framework for all organizational and technical entities of an EFC scheme and for the related interfaces, based on the system architecture defined in ISO 17573-1. The security framework describes a set of security requirements and associated security measures. Annex D contains a list of potential threats to EFC systems and a possible relation to the defined security requirements. These threats can be used for a threat analysis to identify the relevant security requirements for an EFC system. The relevant security measures to secure EFC systems can then be derived from the identified security requirements.

This document defines terms within the field of electronic fee collection (EFC). This document defines: — terms within the fields of electronic fee collection and road user charging; — terms that are used in standards related to electronic fee collection; — terms of a more general use that are used more specifically in standards related to electronic fee collection. This document does not define: — Terms related primarily to other fields that operate in conjunction with EFC, such as terms for intelligent transport systems (ITS), common payment systems, the financial sector, etc. — Deprecated terms.

This document specifies the test procedures of electronic fee collection (EFC) roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically. The scope of this document is restricted to systems operating within the radio emission, electromagnetic compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated. This document identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters: — functionality; — quality; — referenced pre-tests. An overview of the tests and parameters provided by this document is given in 5.1 and 5.2. This document describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this document provide instructions to evaluate the test results. This document defines only the tests and test procedures, not the benchmark figures that these are to be measured against. The test procedures defined in this document can be used as input, e.g. by scheme owners, for prototype testing, type approvals, tests of installations and periodic inspections. Related to a conceptual model of an EFC system, this document relates only to the equipment of the user and the service provider. Any other entities are outside the scope of document. EFC systems for dedicated short-range communication (DSRC) consist, in principle, of a group of technical components, which in combination fulfil the functions required for the collection of fees by electronic automatic means. These components comprise all, or most, of the following: — OBE within a vehicle; — OBE containing the communications and computing sub-functions; — optional integrated circuit card which may carry electronic money, service rights, and other secured information; — communication between OBE and RSE based on DSRC; — equipment for the fee collection at the RSE containing the communications and computing sub-functions; — equipment for the enforcement at the roadside; — central equipment for the administration and operation of the system. The scope of this document relates solely to OBE and RSE and the DSRC interface between OBE and RSE including its functions to perform the fee collection. All the equipment used for enforcement (e.g. detection, classification, localization, and registration) and central equipment are outside the scope of this document.

This document defines an application interface between DSRC-based OBE (hereinafter referred to as "DSRC-OBE") and an external in-vehicle device (hereinafter referred to as "the external device") to make DSRC-OBE applicable for diversified external devices. NOTE For use in autonomous tolling and DSRC-based (CEN, UNI, ARIB, TTA and GB/T) electronic fee collection (EFC) systems. For use in urban and inter-urban toll schemes. The scope of this document covers the following items (as shown in Figure 4): — definitions of the application interface between DSRC-OBE and external devices, including global navigation satellite system (GNSS), cellular network (CN) and controller area network (CAN) device; — definitions of data groups and data elements. Figure 4 — Scope of this document The following items are out of the scope of this document: — definitions of hardware components in the external device such as GNSS module, CN module and mobile devices; — definitions of the physical interface between DSRC-OBE and the external device such as USB and Bluetooth; — definition of ITS services other than EFC; — definition of algorithms for authentication, encryption and key management.

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 requirements to support information exchanges among related entities of a common payment scheme. It defines: a) electronic fee collection (EFC) functional requirements for a common payment medium; b) an application structure in a common payment medium; c) EFC application data in a common payment medium. The following are outside the scope of this document: — requirements and data definitions for any other transport services such as public transport; — a complete risk assessment for an EFC system using a common payment medium; — security issues arising from an EFC application among all transport services; — the technical trust relationship between a CSRP and a service user; — concrete implementation specifications for implementation of security for an EFC system; — detailed specifications required for privacy-friendly EFC implementations; — any financial transactions of the CSRP.

This document identifies the architecture of a toll system environment in which a toll charger (TC) can act to support traffic management with the use of a tariff scheme. The scope of this document defines: — the architecture related to the scope; — a standard framework and data flow model; — an exchange of information between a TC and a road and traffic manager (RTM), e.g.: — level of service (LOS); — tariff scheme; — data which is needed to support traffic management (vehicle probe and traffic flow data). This document is a toolbox standard of application protocol data units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in real implementation are outside the scope of this document. This document does not define communication stacks or timings. Data types and associated coding related to the data elements described in Clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1. This document allows the implementer to define suitable protocol procedures such as basic interaction, protocol mechanism, and choice of transfer protocol.

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 investigates the stemming from requirements of charging policies and corresponding charging technologies in order to propose future standardization theme candidates. This document reports the findings of the investigation of charging policies and technologies in order to: — Classify the conventional charging policies and the new charging policies and their functional requirements. — Classify the existing technologies and the emerging technologies to be used for EFC services or other intelligent transport system (ITS) services. — Conduct a gap analysis between the needs of the new charging policies and the existing standardized technologies for EFC. — Recommend development of emerging standards or amendments for existing EFC standards according to the results of the gap analysis.

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).

ISO/TS 21719-1:2018 describes: - an overall description of the EFC personalization process; - a description of EFC functionality that can be used for personalization. The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.

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).

ISO/TR 16401-1:2018 covers the test purposes for Front End Communications API covering functionalities related to instance handling, session handling, communication service primitives (i.e. sending/receiving of ADUs) and visible state transitions. It covers EFC communication services described in ISO 17575‑2:2016, Clause 5 and PICS proforma in ISO 17575‑2:2016, B.2. Claims related to Front End storage capacity are out of scope of this document. ISO/TR 16401-1:2018 covers the test purposes for Front End Application related to session establishment on Back End request and related to session re-establishment when session requested by Back End failed. There are no other claims with respect to Front End Application described in ISO 17575‑2. The underlying communication technology requirements for layer 1 to 4 specified in ISO 17575‑2:2016, Clause 6 are out of scope of this document. Similarly, Back End Communications API is out of scope of this document. According to ISO 17575‑2 it is expected that these Front End Communications API will be "reflected" in the BE; however, BE Communications API is out of scope of ISO 17575‑2. Test purposes have been organized into the test suite groups, designated for the Front End Communications API and Front End Application, respectively. Aside from the test purposes, this document also provides proforma conformance test reports templates for both the Front End and Back End test purposes. ISO 17575‑2 contains more information regarding the requirements against which the conformance is evaluated in this document.

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).

The ISO 16407 series of standards specifies a suite of tests in order to assess the Front End and Back End behaviour compliancy towards the requirements listed in ISO 17575-1. ISO 16407-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 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 17574:2017 provides guidelines for preparation and evaluation of security requirements specifications, referred to as Protection Profiles (PP) in ISO/IEC 15408 (all parts) and in ISO/IEC TR 15446. By Protection Profile (PP), it means a set of security requirements for a category of products or systems that meet specific needs. A typical example would be a PP for On-Board Equipment (OBE) to be used in an EFC system. However, the guidelines in this document are superseded if a Protection Profile already exists for the subsystem in consideration.

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.

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.

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 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 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).

Common payment scheme for multi-modal transport services, such as toll roads and public transport, are implemented all over the world. These systems are often based on a common payment medium, e.g. IC cards, for use in more than one transport service. The aim of ISO/TR 19639:2015 is to analyse the existing set of EFC standards for their suitability for using common payment media for multi-modal transport services, where applicable identify standardisation gaps and to make proposals for such EFC standardisation projects. This includes definition of additional information to be exchanged among the related entities and to define the specific requirements for common payment scheme. The scope of ISO/TR 19639:2015 includes: investigation of a suitable model for EFC systems and other transport services; identification of the required interface definitions between the EFC and the public transport services including e-money services; identification of additional needs for additional EFC related information exchange among the related entities; provision of guiding information to be considered in revisions of EFC standards. The scope includes all types of EFC systems, i.e. including both DSRC based EFC and autonomous EFC systems, and both pre-pay type and post-pay type. Service related information of both public transport and e-money are outside the scope of ISO/TR 19639:2015.

This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of values are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824‑1. This document defines: — ASN.1 (data) types within the fields of EFC; — ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC. This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.

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

ISO/TS 21719-2:2018 specifies - personalization interface: dedicated short-range communication (DSRC), - physical systems: on-board equipment and the personalization equipment, - DSRC-link requirements, - EFC personalization functions according to ISO/TS 21719-1 when defined for the DSRC interface, and - security data elements and mechanisms to be used over the DSRC interface. Protcol information conformance statement (PICS) proforma is provided in Annex B, whereas security computation examples are provided in Annex E.

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.

ISO 13140-2:2016 specifies the abstract test suite (ATS) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 13141:2015 in accordance with the test suite structure and test purposes defined in ISO 13140‑1:2016. It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment (OBE and RSE) to support interoperability between different equipment supplied by different manufacturers.

ISO 18143-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 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.

ISO 13143-2:2016 specifies the abstract test suite (ATS) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813 in accordance with the test suite structure and test purposes defined in ISO 13143‑1:2016. It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment (OBE and RSE) to enable interoperability between equipment supplied by different manufacturers. In order to ascertain that OBE and RSE fulfil essential radio requirements, they are also likely to be subject to additional factory, site and system acceptance testing (e.g. of physical and environmental endurance, quality assurance and control at manufacturing, and charge point integration), which is outside the scope of this document.

ISO/TS 14907-2:2016 describes tests that verify on-board unit (OBU) conformance of implementations of functions and data structures, as defined in the implementation conformance statement based on ISO 14906:2011/Amd1:2015, for electronic fee collection (EFC) applications. After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing of a complete EFC transaction (C.3). It comprises definitions of OBU conformance assessment tests of - basic dedicated short-range communication (DSRC) L7 functionality, - EFC application functions, - EFC attributes (i.e. EFC application information), - the addressing procedures of EFC attributes and (hardware) components [e.g. integrated circuit cards (ICC) and man-machine interfaces (MMI)], - the EFC transaction model, which defines the common elements and steps of any EFC transaction, and - the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface level. The purpose of this part of ISO/TS 14907 is to define tests that - assess OBU capabilities, - assess OBU behaviour, - serve as a guide for OBU conformance evaluation and type approval, - achieve comparability between the results of the corresponding tests applied in different places at different times, and - facilitate communications between parties. Whereas, ISO/TS 14907-2:2016 defines examples of test cases for DSRC and EFC functionality in Annex C, it does not intend to specify a complete test suite for a certain implementation. To compose a test suite for a specific EFC implementation, the test cases may have to be modified and new test cases may have to be defined and added in order for the conformance test to be complete. It can be useful to take into account the following considerations when defining a complete test suite: - small range: "exhaustive testing" of critical interoperability/compatibility features, - large range: testing of boundaries and random values, and - composite types: testing of individual items in sequence or parallel. It is outside the scope of ISO/TS 14907-2:2016 to define tests that assess - performance, - robustness, and - reliability of an implementation. Annex D provides an informative overview of Japanese OBE conformance tests that are based on the ISO/TS 14907 series, in order to illustrate how these can be applied in practice.

ISO 12855:2015 specifies - the interfaces between electronic fee collection (EFC) systems for vehicle related transport services, e.g. road user charging, parking and access control; it does not cover interfaces for EFC systems for public transport; an EFC system can include any EFC system, e.g. including systems that automatically read licence plate numbers of vehicles passing a toll point, - an exchange of information between the central equipment of the two roles of service provision and toll charging, e.g. - charging related data (toll declarations, billing details), - administrative data, and - confirmation data, - transfer mechanisms and supporting functions, - information objects, data syntax and semantics, - examples of data interchanges (see Annex C and Annex D), and - an example on how to use this International Standard for the European Electronic Tolling Service (EETS) (see Annex F). ISO 12855:2015 is applicable for any toll service and any technology used for charging. It is defined as a toolbox standard of transactions and Application Protocol Data Units (APDUs), which can be used for the assigned purpose. The detailed definitions of mandatory and optional elements in a real implementation are defined elsewhere. It does not define all communication sequences, communication stacks and timings. The scope of ISO 12855:2015 is illustrated in Figure 2. The data types and associated coding related to the data elements described in Clause 6 are defined in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824‑1.

ISO 12813:2015 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 outside interrogator (road-side 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. 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. ISO 12813:2015 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 does not define a communication sequence. All the attributes defined herein are required in any OBE claimed to be compliant with this International Standard, 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, 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 and ARIB 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 layer 7, with the CCC attributes and functions made available to the CCC applications at the road-side equipment (RSE) and OBE. The attributes and functions are defined on the level of application data units (ADU).

The overall scope of ISO/TS 19299:2015 is an information security framework for all organizational and technical entities of an EFC scheme and in detail for the interfaces between them, based on the system architecture defined in ISO 17573. The security framework describes a set of requirements and associated security measures for stakeholders to implement and thus ensure a secure operation of their part of an EFC system as required for a trustworthy environment according to its security policy. The scope of ISO/TS 19299:2015 comprises the following: definition of a trust model; Basic assumptions and principles for establishing trust between the stakeholders. security requirements; security measures - countermeasures; Security requirements to support actual EFC system implementations. security specifications for interface implementation; These specifications represent an add-on for security to the corresponding standards. key management; Covering the (initial) setup of key exchange between stakeholders and several operational procedures like key renewal, certificate revocation, etc. security profiles; implementation conformance statement provides a checklist to be used by an equipment supplier, a system implementation, or an actor of a role declaring his conformity to ISO/TS 19299:2015; general information security objectives of the stakeholders which provide a basic motivation for the security requirements; threat analysis on the EFC system model and its assets using two different complementary methods, an attack-based analysis, and an asset-based analysis; security policy examples; recommendations for privacy-focused implementation; proposal for end-entity certificates.

ISO/TS 14907-1:2015 specifies the test procedures of EFC roadside equipment (RSE) and on-board equipment (OBE) with regard to the conformance to standards and requirements for type approval and acceptance testing which is within the realm of EFC application specifically. ISO/TS 14907-1:2015 is restricted to systems operating within the radio emission, electromagnetic compatibility (EMC) regulations, traffic, and other regulations of the countries in which they are operated. ISO/TS 14907-1:2015 identifies a set of suitable parameters and provides test procedures to enable the proof of a complete EFC system, as well as components of an EFC system, e.g. OBE, related to the defined requirements of an application. The defined parameter and tests are assigned to the following groups of parameters: ? functionality; ? quality; ? referenced pre-tests. An overview of the tests and parameters provided by this part of ISO/TS 14907 is given in 5.1 and 5.2. ISO/TS 14907-1:2015 describes procedures, methods and tools, and a test plan which shows the relation between all tests and the sequence of these tests. It lists all tests that are required to measure the performance of EFC equipment. It describes which EFC equipment is covered by the test procedures; the values of the parameters to be tested are not included. It also describes how the tests are to be performed and which tools and prerequisites are necessary before this series of tests can be undertaken. It is assumed that the security of the system is inherent in the communications and EFC functionality tests, therefore they are not addressed here. All tests in this part of ISO/TS 14907 provide instructions to evaluate the test results.

ISO/TS 16785:2014 defines an application interface between DSRC-based OBE and external in-vehicle devices to make DSRC-OBE applicable for diversified tolling environment.

ISO/TS 17444-2:2013 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: DSRC Discrete; Autonomous Discrete; Autonomous Continuous. The detailed choice of the set of examination tests to be used depends on the application and the respective context. Compliance with ISO/TS 17444-2:2013 is understood as using the definitions and prescriptions laid out in ISO/TS 17444-2:2013 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:2013. Out of scope of ISO/TS 17444-2:2013 are the following aspects: ISO/TS 17444-2:2013 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 Technical Specification 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:2013 does not consider the specification of a common reference system which would be required for comparison of performance between systems. ISO/TS 17444-2:2013 defines measurements only on standardised interfaces. Proprietary interfaces are excluded, because it is not possible to define standardised 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 25110:2013 defines the data transfer models between roadside equipment (RSE) and integrated circuit card (ICC), and the interface descriptions between RSE and on-board equipment (OBE) for on-board account using ICC. It also provides examples of interface definitions and transactions deployed in several countries.