eCall Certification – Which Standards Apply? Clause‑by‑Clause Interpretation

2026-08-21

1. eCall – Regulatory Hierarchy

EU eCall is not a single standard – it's a complete regulatory framework:

·Base regulation: mandates emergency‑call systems for passenger and light commercial vehicles.

·Implementing regulation: technical requirements and test methods.

·Amendments: bring 4G/5G next‑generation eCall into scope – with transition periods.

Newer regulations take precedence – but old clauses remain valid during transitions – don't rely solely on outdated materials for project decisions.


  2. Core Reference Standards – Line by Line

-EN 15722 – Minimum Set of Data (MSD): location, VIN, time, trigger type. Edition 3 adds sensor and battery data.

·Mandatory for new NG eCall applications from 1 January 2026.

·Mandatory for new registrations from 1 January 2027.

·Edition 2 is no longer suitable for new projects.

-EN 17184 – System performance: functionality, voice quality, communication latency.

-Mandatory for new certification projects after 1 January 2027.

·EN 17240 – End‑to‑end communication conformance: in‑vehicle unit ↔ PSAP interaction logic – critical for cross‑network interoperability – missing this blocks certification.


  3. Next‑Generation eCall – Dedicated Standards

-EN 17240: upgraded from transitional technical specification.

·Mandatory for new applications from 2027.

·Transition‑period certificates must be updated by 2028.

-Added requirements for 4G/5G packet‑domain architecture – the core difference from legacy circuit‑switched eCall.

-Positioning performance: GNSS cold‑start/hot‑start time, accuracy.

-EMC: UN R10 – both emissions and immunity must pass – failure blocks whole‑vehicle type approval.


  4. Test Module Breakdown

Functional/communication tests:

·Automatic trigger, manual trigger, 10‑second link establishment, dataset format, backup‑battery baseline capability.

Voice call link is safety‑critical – in addition to ideal networks, simulate weak‑signal environments – many projects focus only on data and neglect voice – leading to later rework.

Next‑generation specific:

·IMS packet‑domain communication.

·End‑to‑end platform co‑ordination.

·Positioning accuracy validation.

Full backup‑battery endurance is mandatory from 1 January 2027 – reserve adequate test time in project planning.

Communication module, antenna, or positioning‑chip changes require partial or full retesting – old reports cannot be directly reused.


  5. Certification Paths and Validity Dates

Two paths: whole‑vehicle and component.

·eCall is part of whole‑vehicle type approval – cannot be independently certified as a whole vehicle.

·In‑vehicle eCall units may use STU (Separate Technical Unit) component certification – locking supply chains early – only interface validation needed at the vehicle stage – reducing duplicate testing.

UN R144 component certificates: no statutory 3‑year expiry – valid as long as the design is unchanged and CoP is maintained – only transition‑period certificates require updating by 2028.

Key dates:

·1 January 2026: no new CS‑eCall applications.

·1 January 2027: no new CS‑eCall vehicle type approvals.

·Already‑approved, CoP‑compliant existing models: may continue production/sale.


  6. Common Misconceptions

·Don't confuse institutional review cycles with statutory certificate validity.

·Don't assume all old CS‑eCall certificates are invalidated after 2027 – compliant existing models have a continuation path.

·eCall cannot be certified as a whole vehicle independently of vehicle approval.

·Standard‑version numbering errors are a frequent low‑level rejection reason – verify before submission.

·New EU projects no longer mandate 2G/3G compatibility – LTE + IMS voice is the mainstream.


  7. Practical Recommendations

·At project definition, lock in communication‑module, antenna, and Edition‑3 dataset solutions.

·If core hardware or firmware changes – assess whether retesting is triggered – don't wait until the vehicle stage.

·Pre‑validate weak‑signal voice, backup battery, positioning, and end‑to‑end PSAP integration at the R&D stage.

·BlueAsia can handle eCall, UN R144, and multi‑country vehicle access – early involvement clarifies old/new version boundaries – reducing later rework.


For eCall certification standards, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.