ISO 16410-1:2017

Overview

ISO 16410-1:2017 - "Electronic fee collection - Evaluation of equipment for conformity to ISO 17575‑3 - Part 1: Test suite structure and test purposes" - defines a structured suite of conformance test purposes to assess Front End and Back End behaviour against the context-data requirements of ISO 17575‑3. The document describes each test purpose in a textual, structured form (initial conditions, references and step sequences). Identical tests are available in TTCN‑v3 form in ISO 16410‑2. ISO 16410‑1:2017 also supplies proforma conformance test report (PCTR) templates and an informative note on use for the European electronic toll service (EETS).

Key topics and technical requirements

• Test suite structure: Tests are organized into groups for Front End and Back End evaluation (e.g., ADU header/body, tariff tables, toll context layout, charge report).
• Data element validation: Presence/absence checks and structural conformance to ISO 17575‑3 data sets and attributes.
• Semantic checks: Verification of semantics for context activation, handling multiple contexts, precedence and priority rules, and uniqueness of relevant elements.
• Charge definition and calculation: Tests for correct definition of charge objects and verification of the fee calculation algorithm (including rounding and alternative currency considerations introduced in the 2017 revision).
• Security-related checks: Conformance testing related to security attributes as referenced in ISO 17575‑3.
• Reporting: Proforma templates for standardized conformance reporting for Front End and Back End.
• Scope limits: Explicitly excludes dynamic sequencing/triggering scenarios, higher‑level business logic or pricing profiles, and behaviour‑invalid tests (BI not applicable since ISO 17575‑3 does not specify behaviour‑invalid cases).

Practical applications and who uses it

ISO 16410‑1:2017 is intended for:

• Test laboratories and conformity assessors performing interoperability and compliance testing for EFC equipment.
• On‑board equipment (OBE) and back‑office vendors validating that implementations meet ISO 17575‑3 context‑data requirements.
• Toll operators, EETS providers and system integrators who need objective conformance evidence prior to deployment.
• Regulators and procurement teams requiring standardized test reports to verify supplier claims.

Practical uses include structured conformance test planning, automated test development (via ISO 16410‑2/TTCN‑v3), and producing repeatable PCTRs for certification and procurement.

Related standards

• ISO 17575‑3:2016 - Application interface definition: Context data (base requirements).
• ISO 17575‑1 - Charging message definitions (referenced for charge report validation).
• ISO 16410‑2 - Same test purposes implemented in TTCN‑v3.
• ISO 9646 series - Conformance test methodology referenced by this document.

Keywords: ISO 16410-1:2017, electronic fee collection, EFC test purposes, ISO 17575-3, conformance testing, Front End, Back End, TTCN‑v3, EETS.