ISO 17575-2:2016

Overview - ISO 17575-2:2016 (Electronic fee collection, Part 2)

ISO 17575-2:2016 specifies the communication and connection to the lower layers for autonomous electronic fee collection (EFC) systems. It defines how to convey all or parts of the data element structures (defined in other parts of ISO 17575) over any suitable communication stack and media, with a focus on mobile communication links (air-links such as cellular, GNSS-assisted systems). The standard presents a media‑independent, abstract communications API for the Front End (FE) to interact with lower-layer communications and describes conformance artifacts (PICS proforma) and example concrete APIs.

Key topics and technical requirements

• Abstract communications API: semantics and service primitives to initialize sessions, address messages, forward payloads and manage the communication lifecycle between FE and lower layers.
• Communication services: initialization, session establishment (incoming/outgoing), point‑to‑point primitives, unstructured and structured application data units (ADUs), session end and failure handling.
• Use of a communication stack: guidance on conveying ISO 17575 data across heterogeneous stacks and media; requirements for underlying mobile technologies.
• Conformance and examples: normative Abstract API (Annex A), Protocol Implementation Conformance Statement (PICS) proforma (Annex B), and an example concrete API (Annex C). Informative annexes include language-specific examples and an EETS use case.
• Scope boundaries: specification covers FE-side communication API semantics; concrete BE API definition, certificate handling, encryption mechanisms and media selection policies are explicitly out of scope.

Practical applications and typical users

Who uses ISO 17575-2:2016:

• OBE manufacturers and Front End software developers implementing the FE communication interface for autonomous tolling devices.
• System integrators and vendors building EFC solutions that must interoperate across toll chargers and service providers.
• Toll operators and service providers ensuring interoperable message exchange with Back Ends and participating in EETS clusters.
• Test labs and conformance teams using the PICS proforma and example APIs to validate implementations.

Typical uses:

• Designing FE communication stacks for GNSS/CN-based autonomous tolling systems.
• Implementing session management, ADU handling, and mobile‑terminated call behavior according to a media‑independent API.
• Enabling interoperability between FE implementations and multiple Back Ends within cross-border or multi‑charger environments.

Related standards

• ISO 17575-1 - Charging (data elements for usage reporting)
• ISO 17575-3 - Context data (charged objects, tariffs)
• ISO 17573 - Business architecture for tolling/EFC

Keywords: ISO 17575-2:2016, electronic fee collection, EFC, autonomous systems, communications API, Front End, Back End, OBE, GNSS, cellular networks, PICS, EETS.