The transition from CS‑eCall to NG‑eCall for in‑vehicle emergency calling systems is already underway. The 4G and 5G technology routes have certification timelines that differ by more than a little. Get the numbers right in your schedule – or your SOP will fail.
Three milestones – many remember the dates but misunderstand their meaning.
·1 January 2025: EU opens NG‑eCall certification applications – new projects can start directly.
·1 January 2026: New applications and existing certificate extensions for pure CS‑eCall are no longer accepted. However, existing CS‑eCall certificates already issued do not immediately become invalid – they can still be used. This distinction is critical – it does not mean old certificates expire on New Year's Day 2026.
·1 January 2027: CS‑eCall certificates can no longer be used for new vehicle type approvals. This does not mean all existing certificates automatically expire – member‑state transition implementation details depend on local Notified Body requirements.
The primary regulation (EU) 2024/1180 has replaced the old (EU) 2015/758. NG‑eCall has been upgraded from an option to a mandatory item for new vehicles – non‑compliant models cannot pass WVTA whole‑vehicle type approval.
2. NG‑eCall Certification – Practical Impact on Scheduling
For new projects starting in the second half of 2025, NG‑eCall is the only path. The renewal window for existing CS‑eCall models closes at the end of 2026 – delaying further will be too late.
3. NG‑eCall Certification Path – AECS vs. AECC – Not the Same
NG‑eCall certification follows UN‑R144 Part Ib – covering AECS (Accident Emergency Call System) as an independent technical unit approval. Note: UN‑R144 is a component‑level certification under the UN regulation framework – obtaining an AECS certificate does not mean the whole vehicle is compliant – that still requires EU WVTA.
Both standalone STU modules and integrated T‑Box solutions follow the AECS path – but different Notified Bodies have different document‑review stringency for each; integrated solutions are typically reviewed more thoroughly.
Functional standard: EN 17184:2024; test method: EN 17240:2024. Throughout 2026, these EN standards run in parallel with the old CEN/TS transition standards – new projects can choose either the formal EN standard or the transition standard – timelines differ slightly.
4. AECC Module Certification Scope
For module‑level AECC (Accident Emergency Call Component) certification – following UN‑R144's definition for eCall communication components – backup battery, crash‑trigger, and voice‑path tests are not required – scope is significantly narrower than full AECS. Timeline: typically 4–6 weeks. However, if IMS stack or MSD transmission has issues in the first round, retesting adds 2–4 weeks.
An AECC certificate cannot substitute for whole‑vehicle eCall compliance – AECS is still required.
5. 4G vs. 5G – Technical Route Differences
First, correct a widespread misunderstanding: NG‑eCall is designed around the IMS packet‑domain – the regulation does not mandate that 4G terminals support CSFB fallback to 3G circuit‑domain. NG‑eCall relies on multiple IMS link redundancy to ensure reliability – not on keeping 3G as a backup. Many EU operators are already decommissioning 3G networks – forcing a CSFB requirement is disconnected from reality.
Testing focus is on domain‑switching logic when IMS calls are unreachable. Scenarios cover: IMS registration failure, PSAP not supporting IMS, and loss of 4G/5G coverage – each must verify MSD dataset delivery and call‑setup latency.
6. 5G Solutions – No 3G Backup Required
EN 17184 and (EU) 2024/1180 contain no clause mandating 3G CS circuit‑domain for 5G NG‑eCall. VoNR + EPS Fallback (to 4G VoLTE) is sufficient to meet redundancy requirements. There is no need to design a 3G fallback link for 5G terminals.
NSA and SA 5G architectures have different test‑matrix workloads – SA typically skips one step of LTE anchor verification. Confirm the test scope with your Notified Body in advance – do not assume both architectures have the same timeline.
7. NG‑eCall Certification – Stage‑by‑Stage Breakdown
7.1 Document access and pre‑review
Technical document preparation: roughly 2 weeks. Core documents: system architecture description, software version management plan, and cybersecurity assessment reports. Must fully describe IMS call flow, MSD transmission mechanism, and link redundancy logic.
7.2 Test execution phase
·Backup‑power test – under (EU) 2025/1871 Annex X, the full cycle is: 5‑minute call, 60‑minute standby, then 5‑minute call – total 70 minutes. Some accredited labs allow compliant segmented execution with voltage‑curve recording – segmentation is not absolutely forbidden.
·IMS call‑setup latency – EN 17184 defines trigger‑to‑session‑establishment metrics with clear scenario boundaries – 3 seconds is not a universal hard threshold for all test cases – do not generalise.
·MSD version confusion: For 2026 new projects, a V2/V3 transition period allows parallel use – not a blanket V3 mandate. The actual full switch to the new MSD version is 1 January 2027, with EN 17184:2024 mandatory. Projects starting in the first half of 2026 can continue using the old version – no need to waste time on V3.
·Crash trigger, voice quality, GNSS positioning, and other items run in parallel – overall test cycle: 6–8 weeks. V3 adds vehicle‑heading and occupant‑count fields – data structure does change – but that is for 2027 onwards.
7.3 Certification review phase
After test reports are submitted to the technical service body for review: typically 2–3 weeks for results. If multiple vehicle platforms share the same AECS solution, the review scope expands to platform‑compatibility assessment. If the OEM directly reuses an already‑certified AECS system, much duplicate testing can be waived – significantly shortening the timeline.
Post‑certification CoP (Conformity of Production) annual audits are an ongoing obligation – separate from the initial certification timeline.
8. Easily Overlooked Variables
·UN‑R155 cybersecurity – often misunderstood. R155 is a WVTA whole‑vehicle requirement – not a prerequisite for NG‑eCall components (UN‑R144 AECS). Component manufacturers do not need to obtain R155 before AECS certification – do not add a parallel synchronisation round unnecessarily.
·Commercial vehicle temperature testing – under UN‑R144 and EN 17240, the base limit is 85°C. Some NBs add cyclic temperature tests based on vehicle application scenarios – do not assume only a single 85°C point is required.
·CoP audits – minor non‑conformities result in a remediation notice first – not immediate certificate revocation. Only serious and persistent CoP non‑conformance leads to revocation. Recovery timeline: 3–6 months.
For NG‑eCall certification timelines, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
相关新闻
