2026 is a critical eCall solution‑switch year. From the start of this year, the EU no longer accepts new CS‑domain eCall product certifications – combined with multiple 2027 regulatory deadlines approaching. OEMs and Tier‑1s need to finalise their solution path – decide whether to maintain existing CS‑eCall legacy projects or switch to NG‑eCall – and plan ongoing CoP compliance.

1. CS‑eCall Sunset and Legacy Product Compliance Boundaries

1.1 New application channel closed
From 1 January 2026, the EU stopped accepting new type‑approval applications for legacy CS‑domain eCall products – this rule is uniformly applied – there are no vehicle‑type or sales‑region exemptions.

1.2 Clarifying the January 2027 regulatory scope
Common misconception: not all CS‑eCall certificates expire on 1 January 2027, nor are all vehicles banned from sale. The 2027 date applies to new vehicle type approvals – CS‑eCall solutions are no longer accepted. Already‑certified, continuously produced vehicles and existing market stock – implementation varies by member state – there is no blanket prohibition. Contact your target market's Notified Body in advance to confirm local transition policies – avoid last‑minute compliance risks.

1.3 Project switch timeline reference
Starting an NG‑eCall switch in mid‑2026 leaves reasonable time. Further delays will significantly increase remediation pressure. NG‑eCall has more test items than legacy CS – EMS pre‑testing and building a full CoP documentation system both extend the overall project timeline.

  2. NG‑eCall Certificate Maintenance and Core Technical Test Points

2.1 CoP production‑conformity audit rules
NG‑eCall certificates have no fixed expiry – validity is maintained through annual CoP audits. A failed audit does not immediately revoke the certificate – the Notified Body gives a remediation period. There is no statutory uniform remediation duration – different NBs have different standards – do not assume 3–6 months as a fixed rule. Audit focus includes: backup‑power discharge performance, emergency‑call link stability, IMS signalling compliance – mass‑production sample parameters must match type‑approval test data.

2.2 Backup power and IMS call‑setup latency

·Backup power must complete the full 66‑minute duty cycle: 5‑minute emergency call + 56‑minute low‑power standby + 5‑minute second call.

·Design trap: many engineers size batteries for continuous full‑load – note that the 56‑minute phase only requires low‑power standby – no continuous RF transmission.

Under EN 17184:2024, IMS call‑setup latency upper limit is 3 seconds. Timing starts at eCall trigger, ends when two‑way voice channel is established – not simply PSAP receiving a confirmation message. Lab emulation environments differ from real operator networks – confirm test baseline conditions with the lab before submission.

2.3 MSD version rules and T‑Box fallback

2.3.1 MSD V2 vs. V3 transition
EN 17184 has parallel old/new standard transition. Early NG‑eCall projects certified under CEN/TS 17184 transition standards may continue using MSD V2. From 1 January 2027, new projects must use the official EN 17184:2024 – MSD V3 is mandatory. Do not believe online claims that "V2 samples are immediately rejected" – legacy transition‑period projects still have compliance space. Compared to V2, MSD V3 adds: vehicle type, fuel type, and autonomous‑driving status fields.

2.3.2 Dual‑mode fallback – functional requirement ≠ hardware mandate
NG‑eCall relies on 4G/5G IMS packet‑domain. Fallback mechanisms are required – mainly for scenarios where PSAP cannot handle VoIP IMS. However: UN‑R144 and EN 17184 do not mandate that 4G/5G modules include 3G baseband hardware. Many EU countries are actively decommissioning 3G networks – relying solely on 3G CS as a long‑term backup is not viable. The industry claim that "single‑mode hardware cannot pass certification" is one‑sided – it conflates interoperability test conditions with hardware mandates – blindly procuring multi‑mode modules adds unnecessary hardware costs.

2.4 Environmental temperature testing – common misconceptions

·-40°C to +85°C is the standard IVS automotive test range – equally applicable to passenger and commercial vehicles.

·Some OEMs raise internal standards to 105°C – this is a corporate requirement – not the certification baseline – keep them separate.

  3. Certification Path Distinctions – STU Terminology, RF Modules, and Integrated Terminals

3.1 Official terminology – STU
The official UN‑R144 term is STU (Separate Technical Unit). STU products and integrated eCall systems use the Part Ib path; Part II covers whole‑vehicle WVTA type approval – not applicable to component/system‑level certification. AECD is not an official R144 classification – only an industry colloquialism – use STU when communicating with Notified Bodies.

3.2 RF module vs. integrated IVS terminal boundaries

·Pure cellular/GNSS RF modules seeking R144 certification – test scope excludes backup battery, crash‑trigger interfaces, and voice path.

·Integrated IVS terminals with full eCall logic – even if filed as STU components – must still complete backup‑power and external‑trigger interface assessments.

Some module vendors claim full eCall system compliance based solely on module R144 certificates – distinguish the boundaries – module certification does not cover all terminal‑level test items.

  4. EN17240 A1 Amendment and Cybersecurity Compliance Boundaries

4.1 EN17240 A1 – scope of impact
EN 17240:2024 A1 revisions are not limited to crash‑trigger reliability and vibration test conditions – they also update MSD V3 interaction rules, IPv6 support, and IMS‑CS dual‑mode interoperability test cases. Products with reports based on older versions do not need full retesting – but they do need to assess whether new test conditions affect existing software/hardware designs.

4.2 R155 and component‑level R144 – don't confuse

·UN‑R155 cybersecurity is a WVTA whole‑vehicle requirement – OEMs must build a CSMS and complete whole‑vehicle cybersecurity certification.

·Component‑level T‑Box/STU R144 certification – the regulation does not mandate a prerequisite R155 certificate.

Many Tier‑1s only do component‑level R144 – no R155 required. The claim that "without R155 you cannot get NG‑eCall" misleads module manufacturers and misallocates project budgets.

  5. Transition Summary – Mid‑2026

Mid‑2026 is a critical solution‑switch window. Manufacturers should prioritise three tasks:

·Maintain CoP audit systems routinely.

·Fully validate dual‑mode fallback functionality.

·Prepare supporting cybersecurity documentation early.

Certificates themselves have no fixed expiry – but when the supporting harmonised standard is repealed, or the product undergoes major hardware/firmware changes – the original certificate cannot be used for new project applications.

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