eCall – at its core – is a system that automatically places a distress call in the event of a crash. Sounds simple – but when you get into the compliance framework, the regulatory layers, technical standards, and transition schedules are quite granular.

2026 is a pivotal year: the CS‑domain (circuit‑switched) eCall sunset in Europe is already counting down – and China's own standard GB 45672-2025 (AECS) has been published. If you have eCall projects in your annual plan, the following timelines and standard version differences need close attention.

1. EU eCall – The Regulatory Framework

·Legal foundation

The EU eCall legal foundation is Regulation (EU) 2024/1180 – which replaced the older (EU) 2015/758 in 2024. It mandates eCall systems for all new M1 (passenger cars) and N1 (light commercial vehicles) models.

Beware of a non‑existent regulation number – (EU) 2025/1871 is an industry‑circulated error – the formal regulation is (EU) 2024/1180. Always double‑check the reference when preparing compliance documents.

·Does the certificate have a validity period?

This is a frequently misasked question. The certificate itself has no fixed expiry date – validity is maintained through annual CoP (Conformity of Production) audits. Each year, CoP audits check that production units match the certified sample – hardware configuration, software version, critical component sources – all reviewed. CoP failure suspends certificate usage rights – a remediation period is given – the timeline is determined by the issuing NB – there's no fixed 3‑month or 6‑month blanket rule.

If the harmonised standard is repealed or the regulation is updated – even with hardware unchanged – existing certificates cannot be used for new‑model WVTA applications. Already‑certified, unchanged, CoP‑compliant products can continue to be used for production of already‑type‑approved models.

·Technical standards

·Functional requirements: EN 17184:2024.

·Test methods: EN 17240:2024.

These are used together – and testing references both.

EN 17240:2024/A1 – the amendment adds more than just crash‑trigger and vibration test cases – it also updates MSD V3 interaction protocols, IPv6 support, and IMS‑CS dual‑mode interoperability test cases. Before designing a test plan, check which version of EN 17240 applies – test items can differ significantly.

  2. NG‑eCall – IMS Transition and the 2027 Hard Milestone

·Three key dates

Industry focus has shifted from legacy CS‑domain eCall to NG‑eCall (IMS‑based next‑generation emergency calling). The reason: multiple EU countries are actively decommissioning 3G networks – relying solely on 3G CS for voice fallback is unsustainable.

Timeline:

·1 January 2025: NG‑eCall formally opens for applications.

·1 January 2026: CS‑eCall new applications are rejected – including extensions and change applications for existing CS‑eCall certificates.

·1 January 2027: CS‑eCall is no longer accepted for new type approvals.

Note: "new type approvals" – not a blanket cut‑off for existing products. Products certified before 2027 can continue to be sold.

For manufacturers: if you're still developing new products with CS‑domain eCall – after 2026, you can't apply for new models – and even legacy certificate extensions are blocked.

·IMS call‑setup latency – a hard metric

IMS call‑setup latency is a core NG‑eCall performance metric. EN 17184:2024 requires ≤3 seconds – measured from the in‑vehicle IMS call initiation to receipt of PSAP voice media – excluding crash‑detection and triggering time. Note: the timing start point is not from crash detection – if you calculate that way, your hardware timing budget will be wrong.

Many products fail here. IMS registration, SIP signalling exchange, and audio codec negotiation – each consumes part of the 3‑second budget. It's a very tight design target.

  3. MSD (Minimum Set of Data) – Version Transition

·V2 to V3 transition

MSD is the critical data package that the eCall system automatically sends to the PSAP after establishing the voice channel – including vehicle location, VIN, crash time, heading, etc. The current mainstream version is MSD V2.

MSD V3 is mandated with the formal EN 17184:2024 – from 1 January 2027, new certification applications must use the formal EN 17184:2024 – the CEN/TS transition specification will no longer be accepted. These are not two independent parallel conditions – they are cause and effect: formal standard mandatory → V3 follows. For projects using the CEN/TS 17184 transition path, MSD V2 remains valid during the transition.

V3 adds significant new data fields and interaction changes – requiring PSAP‑side upgrades. Currently, PSAP upgrade progress varies across EU countries – confirm your target market's PSAP V3 support status early in the project.

  4. Dual‑Mode Fallback and 3G Sunset

·IMS‑to‑CS fallback logic

NG‑eCall runs on IMS (IP Multimedia Subsystem) – typically over 4G LTE or 5G NR. Not all PSAPs support IMS eCall – IMS‑CS dual‑mode fallback automatically reverts to CS‑domain when the PSAP doesn't support IMS.

Critical qualification: UN‑R144 and EN 17184 do not mandate that 4G/5G hardware must include 3G baseband. However: if the product claims support for IMS‑CS dual‑mode fallback – the hardware must have CS‑domain capability. Many manufacturers misinterpret this as "NG‑eCall = 3G baseband required" – the accurate statement is: don't declare dual‑mode fallback and you don't need 3G; declare it and you must have it.

With multiple EU countries accelerating 3G sunset – relying solely on 3G CS for fallback is unsustainable. OEMs and Tier‑1s are prioritising PSAP‑side IMS eCall support – reducing reliance on CS fallback – CS fallback is a temporary safety net, not a long‑term solution.

  5. UN‑R144 Certification Paths

·Integrated vs. STU

UN‑R144 is the UN regulation on eCall system type approval – referenced under the EU WVTA framework. eCall systems follow two certification paths:

·Integrated: eCall functionality is part of the whole‑vehicle WVTA type approval – the eCall system does not get a separate certificate – test results are included in the vehicle's technical file.

·STU (Separate Technical Unit): the eCall system as an independent module applies for R144 type approval – after obtaining an STU certificate, Tier‑1s can sell to different OEMs – the OEM references the STU certificate during whole‑vehicle certification.

·Don't confuse Part Ib and Part II

STU is the official R144 term. Both STU and integrated systems follow Part Ib – Part II is for whole‑vehicle WVTA. AECD (Automotive Emergency Call Device) is an abbreviation for the eCall device itself – not an R144 certification path name – distinguish this in project documentation.

·Module certification boundaries

A pure RF module (cellular baseband + RF front‑end, no eCall application logic) under R144 – does not require backup battery, crash‑trigger, or voice‑path assessment. However, if the module integrates IVS (in‑vehicle emergency call system) logic – even if packaged as a "module" – backup power and trigger interfaces must still be assessed.

  6. Backup Power and Temperature Requirements

·Annex X – the 70‑minute duty cycle

(EU) 2025/1871 Annex X specifies the backup‑power duty cycle: 5 minutes of call + 60 minutes of callback standby + 5 minutes of call – total 70 minutes.

Critical: this Annex X backup‑power requirement only takes effect on 1 January 2027. Projects starting in 2026 are not yet subject to this – don't design to the wrong standard.

·Temperature range – applicability

IVS systems typically operate from -40°C to +85°C – applies equally to passenger vehicles – not just commercial vehicles. Some OEMs specify 105°C in their internal standards – that's a commercial requirement – not the regulatory test temperature – keep them separate.

  7. China GB 45672-2025

China's eCall counterpart is GB 45672-2025 In‑Vehicle Emergency Call System (AECS) – published 25 April 2025. Mandatory implementation is staggered by vehicle type:

·M1 new type‑approval applications: 1 July 2027.

·M1 already‑type‑approved: 1 July 2028.

·N1 new type‑approval: 1 January 2028.

·N1 already‑type‑approved: 1 January 2029.

It's not a blanket "all vehicles 1 July 2027" – N1 light commercial vehicles need separate scheduling.

GB 45672 and EN 17184 have technical differences – EU certificates cannot directly cover the Chinese market. Global‑platform OEMs need to consider China‑EU standard compatibility in their design.

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