Europe is upgrading its in‑vehicle emergency call system – the new generation is called NG eCall (Next Generation eCall). At first glance, it might look like a routine feature upgrade – but in reality, the entire communications architecture has been replaced. OEMs, T‑Box solution providers, and cellular module suppliers all need to adjust their project plans accordingly.
This article covers the core logic of NG eCall certification, why the switch is necessary, the differences between old and new systems, and practical testing points – for companies exporting models to the EU, a useful self‑check reference.
The earlier eCall system relied on 2G/3G circuit‑switched networks – collectively known as CS‑eCall. Many regions are now decommissioning 2G/3G – European operators have already announced sunset schedules – circuit‑switched voice services are shrinking.
The core value of eCall is stable connection to the rescue dispatch centre after a crash. Once legacy networks are shut down in a region – traditional CS‑eCall terminals cannot establish calls – the emergency function fails – violating EU regulatory requirements.
The EU introduced NG eCall regulations – the core idea: migrate emergency calling to 4G/5G IMS VoIP channels – eliminating dependence on 2G/3G circuit‑switched networks.
2. Old vs. New – Core Technical Differences
CS‑eCall: shares the voice channel – MSD data is transmitted via in‑band narrowband modulation – voice and data share the same link – higher latency – limited data fields. The old MSD only supported basic information: location, VIN, occupant count, heading – hard to extend for crash‑related data.
NG eCall: built on IMS – over VoLTE/VoNR – voice and MSD data are transmitted independently. MSD is separately encapsulated – can carry richer vehicle information – better positioning accuracy and crash‑data completeness. With IMS, cross‑operator and cross‑border emergency call stability improves.
The communications link has fundamentally changed – the entire test standard is updated. CS‑eCall focused on voice‑channel modulation – NG eCall focuses on IMS signalling and IP packet verification – the test cases and pass/fail criteria are not interchangeable – old reports cannot be directly reused.
3. Regulatory Documents
The base NG eCall regulation is (EU) 2024/1180 – published in 2024 – replacing the earlier (EU) 2015/758 – mandating IMS‑based eCall for new M1 passenger vehicles and N1 light commercial vehicles.
Common confusion on regulation numbers – (EU) 2025/1871 is not a wrong number – it is a supplementary amendment to (EU) 2024/1180 – adding the Annex X backup‑power clause. When preparing compliance documents, refer to both the base regulation and the amendment – don't cite only one.
Harmonised standards:
·Functional framework: EN 17184:2024.
·Test methods: EN 17240:2024.
EN 17240 has since been updated with additional content – MSD V3 protocol, IPv6 extensions, IMS‑CS dual‑mode fallback test scenarios. Before designing a test plan, confirm which standard version applies to your project.
4. Three Key Dates
NG eCall implementation is phased – project scheduling must avoid window risks.
Date Event
1 January 2025 NG eCall type‑approval applications open – voluntary
1 January 2026 New CS‑eCall type‑approval applications no longer accepted – existing CS‑eCall certificate extensions also prohibited
1 January 2027 Existing CS‑eCall type‑approval certificates expire – new vehicle WVTA applications only accept NG eCall
The timeline is clear – after 2027, continuing with legacy circuit‑switched solutions means no type approval – effectively losing EU sales eligibility. R&D plans must work backwards – module selection, protocol‑stack development, and multiple test rounds – all must be completed before the deadlines.
5. Mandatory Test Metrics
NG eCall has several hard test metrics – checking them early in development reduces later remediation.
Backup power:
·Full duty cycle: 5‑minute call + 60‑minute callback standby + 5‑minute second call – total 70 minutes.
·Many articles mention 66 minutes or 56‑minute standby – those are intervals between call disconnection and platform callback – not the regulatory duty cycle. After main power is cut, the backup battery must support the full call process – from initiation to completion.
IMS call‑setup latency:
·Upper limit: 3 seconds – fully specified in EN 17240:2024.
·From crash‑signal trigger to successful call‑link establishment – tight window – IMS registration, SIP signalling, and media negotiation all need ongoing optimisation.
MSD:
·All new certifications from 1 January 2026 use MSD V3. From 2027, all compliant vehicles on the market use V3.
·Compared to the old protocol, MSD V3 adds many new data fields – encoding and transmission timing are all changed – software stacks must be developed against the new version.
6. Certification Path and Scope
The industry references Part Ib and Part II – these are within the whole‑vehicle WVTA framework. For NG eCall T‑Box and in‑vehicle communication terminals, the mainstream path is UN R144 (AECS) independent component type approval – not the WVTA Part Ib channel. Choosing the wrong path at the application stage extends the project timeline significantly.
Simple boundary:
·T‑Box hardware: UN R144 component approval.
·After hardware is installed in the vehicle: separate WVTA type approval.
The two approvals are independent. Component suppliers need to note: obtaining the T‑Box component certificate does not mean the whole vehicle can directly pass WVTA – after installation, additional vehicle‑level integration and real‑world verification are required.
UN R155 – vehicle cybersecurity – applies to the whole vehicle. During T‑Box component certification, R155 review is not conducted separately. However, during whole‑vehicle WVTA review, all electronic control units are checked – the T‑Box's encryption, vulnerability protection, and access controls directly affect the R155 assessment – security design at the component level cannot be simplified.
7. China Domestic Standard
China's domestic eCall mandatory national standard is GB 45672-2025 – published 25 April 2025 – mandatory from 1 July 2027 – the corresponding AECS system also uses IMS architecture.
The two standards cannot share a single implementation. Message structure, rescue‑platform interfaces, and BeiDou positioning compatibility differ significantly. For global platform models, the underlying IMS foundation can be shared to control development costs – but MSD packaging and interaction logic must be separately adapted to both regulations – the same firmware cannot be directly reused.
8. What Companies Should Do Now
For existing CS‑eCall projects, the compliance buffer is shrinking. New CS applications are no longer accepted from 2026 – existing certificates expire in 2027. Companies with such projects should start switch‑feasibility assessments as soon as possible.
Three dimensions:
·Hardware: can 4G/5G modules and in‑vehicle antennas meet IMS voice RF requirements?
·Software: are IMS stack, MSD V3 encoding, and SIP signalling fully developed?
·Testing: does the test plan fully cover EN 17240 – including IMS/CS dual‑mode fallback?
All three must be satisfied before the switch is viable.
9. Certificate Validity and Annual CoP
NG eCall certificates have no fixed expiry date – but long‑term validity has several pre‑conditions:
·Annual CoP (Conformity of Production) audits are completed.
·No substantive hardware or firmware changes.
·Applicable harmonised standards have not been updated with mandatory new versions.
Annual audits check mass‑production products against the certified sample – material configurations, software versions, and critical component supplier information. If a CoP audit fails – certificate usage is suspended – the company must remediate within a timeline determined by the severity – there is no fixed universal duration.
Even if hardware remains unchanged – if EU regulations or harmonised standards undergo major updates – existing certificates cannot be used for new model applications – a change assessment is required – supplementary testing may be necessary.
Module suppliers – any firmware change to IMS call logic or MSD message generation is a substantive change. Before mass‑production rollout, confirm the change level with the certification body – assess whether change certification is required – don't push directly to production.
10. Practical Test Traps
10.1 Backup power: the test procedure looks clear – but retesting is common. The full 70‑minute duty cycle must simulate main‑power disconnection – bench power‑switching logic, temperature conditions, and dynamic loads should match real‑vehicle operation. Inadequate lab simulation leads to repeated rework.
10.2 IMS call latency: easily affected by the test network – rescue‑platform emulator configuration and IMS core‑network parameters both change measured values. Different labs have different network setups – the same terminal can produce different results. Before formal submission, confirm that the lab environment meets standard requirements.
10.3 MSD verification: check every field for completeness, encoding format, and transmission timing – retain full logs of all message interactions – full traceability. Attention to these basics significantly improves first‑pass probability.
10.4 BlueAsia has full NG eCall project experience – from pre‑testing to formal certification – across multiple vehicle platforms and T‑Box component projects. If you're planning NG eCall upgrades or new projects, bring your product solution for discussion – we can align timelines and test planning.
For NG eCall certification, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.
Related News
