eCall rules have changed significantly over the past three years. The EU transition from CS eCall to NG eCall is now fully underway – how certificates are managed, when old certificates expire, and what ongoing compliance involves – all changed. Many Tier 1 suppliers are still following old rules – and finding themselves unable to keep up when clients ask.

1. CS eCall – What Does the 2027 Deadline Really Mean?

From 1 January 2026, the EU no longer accepts new type-approval applications for pure 2G/3G CS eCall – that is correct. The key is the 1 January 2027 deadline. Many assume that on this date, all old eCall component certificates become invalid and cannot continue supply.

That is not how it works.

EU 2024/1180 states clearly: from 2027, whole-vehicle CoC certificates for new vehicles equipped with pure CS eCall systems are not recognised – new vehicles cannot be registered. Component‑level UN R144 CS eCall certificates are not automatically revoked. Existing production vehicles and already‑type‑approved vehicles can continue using CS eCall components. The deadline restricts new vehicle registration – not component certificate validity.

Distinguish component type approval from whole-vehicle WVTA timelines – only then will you avoid misreading new-vehicle registration restrictions as component certificate invalidation.

  2. NG eCall – Old Standard Transition Is Also Not a Clean Cut

From 1 January 2028, you can no longer use the old CEN/TS 17240:2018 technical specification for new type approvals or certificate extensions.

Can components already certified under the old specification continue to supply? The regulation does not say all are invalid. Notified bodies assess on a case-by-case basis, considering the vehicle's market‑placement scenario – there is no blanket "all old certificates expire" rule. NG eCall certification is not permanent – the old specification is being phased out, but that does not mean all old certificates go to zero overnight.

  3. eCall Certificate Validity – The True Conditions

eCall components follow UN R144 type approval – the regulation text does not contain a "valid for X years" fixed term.

The legal basis for maintaining validity is CoP (Conformity of Production). Some NBs internally apply a 3‑year CoP audit cycle – that is their own management policy – not a WP.29 mandatory clause.

The real conditions determining whether a certificate can be maintained are:

·Hardware RF solution unchanged.

·Audio calibration parameters unchanged.

·MSD data format unchanged.

·Applicable standards not repealed.

Regarding EN 17184 backup‑power duty‑cycle differences: NB disagreements centre on fault simulation, power‑down timing, and backend signalling integration – not conflicting core duration standards. Renewal risks come more from standard upgrades than from interpretation differences. POLQA and voice test samples evolve with EN standard updates – supplementary retesting during renewal is normal.

  4. UN R155 Cybersecurity – ISO 21434 Deliverable Obligations

Under whole-vehicle WVTA, UN R155 cybersecurity is a mandatory requirement for the OEM. Standalone UN R144 eCall component certification does not mandate R155 type approval. The two systems are independent – that part is correct.

However: do not assume component manufacturers have no cybersecurity work.

For independently sold eCall components – even though you do not need a separate R155 certificate – development processes must meet ISO/SAE 21434. You must deliver risk assessment reports and security evidence packages to the OEM – not just meet interface specifications. Integrating these into the OEM's R155 CSMS framework is the OEM's responsibility – but the component supplier's cybersecurity deliverables are the supplier's responsibility. Two separate lines – do not confuse them.

  5. EC‑REP, DPIA, and DoC – Boundaries

·EC‑REP is not purely a post‑production compliance obligation. During UN R144 type‑approval application, some NBs require the EU‑based responsible person to be identified – not only at the production stage. Changing the EC‑REP requires a change notification to the NB – not just for market surveillance.

·DPIA is a GDPR data‑protection compliance obligation. NBs do not review DPIA during type approval – but do not shift all responsibility to the OEM. If the component manufacturer independently collects and transmits MSD personal data, they also have GDPR obligations. Some member‑state market surveillance may request the DPIA – not having one creates problems.

·DoC – under UN R144, the type‑approval file and manufacturer's declaration of conformity are separate from CE RED DoC templates and signing rules – completely independent.

  6. eCall Change Management and Easily Overlooked Compliance Items

·eCall modules: change assessment is triggered not only by hardware changes. Firmware changes to IMS logic, MSD data content, or emergency trigger logic – all require notification to the notified body. Making these changes without申报 may compromise the certificate's compliance status.

·MSD dataset format updates: typically do not trigger hardware retesting – but require NB technical documentation review. If a version cross‑generation upgrade (MSDv2 → MSDv3) occurs, some NBs may require end‑to‑end communication retesting – cannot assume it is only documentation review.

·Antenna or audio component supplier changes – even if the core eCall chip remains unchanged – require assessment of AECS audio channel calibration – likely supplementary audio testing.

·One frequently overlooked item: in addition to UN R144 certification, the built‑in cellular communication module in both CS and NG eCall systems requires separate RED directive RF compliance assessment. Two independent certifications – you cannot do only one.

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