ISO 16410-2:2018

Overview

ISO 16410-2:2018 defines an abstract test suite (ATS) for evaluating conformance of electronic fee collection (EFC) equipment to the context-data requirements of ISO 17575-3. Part of the ISO 16410 series, this standard specifies test cases - written in TTCN‑3 (Testing and Test Control Notation v3) - to assess Front End (FE) and Back End (BE) behavior against the test purposes defined in ISO 16410‑1. The ATS targets autonomous EFC systems (GNSS/CN) where on‑board equipment (OBE) calculates fees using satellite positioning and context data.

Key topics

• Abstract Test Method (ATM) and test architecture: Guidance on how to execute TTCN‑3 test cases against an implementation under test (IUT) using an emulated communication sub‑layer.
• TTCN‑3 test cases: Formalized test case definitions reflecting the individual steps of test purposes from ISO 16410‑1.
• ASN.1 data structures: ASN.1 modules used by the ATS (e.g., EfcAutonomousContextData, EfcAutonomousCharging, LacModule) and notes on parametrization.
• PIXIT (Protocol Implementation eXtra Information for Testing): Requirement for suppliers to provide a PIXIT proforma (Annex B) containing implementation-specific test information.
• Security considerations: Coverage of authentication and secure packet embedding as specified by ISO 17575‑3; abridged ASN.1 security modules are used in the ATS and test adapters are required to exercise real security mechanisms.
• TTCN‑3 tool requirements: Use of TTCN‑3 advanced parametrization to handle ASN.1 parameterized data elements is required; compilation and execution may need tool support.
• Untestable TPs: Clause identifying currently no untestable test purposes.

Applications

• Conformance testing of FE and BE components for tolling and electronic fee collection systems.
• Interoperability validation for OBE vendors, toll system integrators, and back‑office providers implementing ISO 17575‑3 context data.
• Test suite development and automation in certification labs using TTCN‑3 and ASN.1.
• Supplier testing prior to deployment to ensure compliance with charging, context data handling, and authenticated reporting requirements.