For EU‑exporting vehicle OEMs and Tier‑1s, NG eCall is now the mainstream direction for 2026. Several EU member states no longer accept new CS‑eCall type‑approval applications from 2026 – but there is no unified EU‑wide cut‑off date. For new projects, plan around NG eCall, and confirm the local implementing policy with the target market authority before starting.

The certification process itself is not complicated – components follow UN R144 type approval, whole vehicles follow (EU) 2024/1180 WVTA – but each step has hidden traps – wrong order wastes time and money.

1. Before You Start – Define Your eCall Path

1.1 Component or whole‑vehicle?

·T‑BOX or comms module → UN R144 AECS component type‑approval – tests do not include real‑vehicle crash – lab end‑to‑end simulation is sufficient.

·Whole‑vehicle → UN R144 plus additional vehicle‑level crash testing and on‑road validation – longer process.

Once a component certificate is obtained, vehicle OEMs can reference it for whole‑vehicle submission – reducing component‑level retesting. However: the reference is conditional on no changes to hardware, firmware, or MSD logic – the notified body has the right to request additional vehicle‑level interaction verification – cannot guarantee full retest exemption.

1.2 EU Authorised Representative (EC‑REP)
Non‑EU manufacturers must appoint an EC‑REP with a signed formal agreement – but note: the EC‑REP is a market‑surveillance obligation after product placement – not a mandatory prerequisite for the notified body to accept a UN R144 application. Many agents exaggerate urgency – don’t be pushed into early signing. The representative’s address must be a physically operating entity in the EU – a shell address will be rejected.

1.3 Choose your notified body and test lab
NG eCall requires a notified body with specific capabilities – must be able to perform EN 17184:2024 end‑to‑end functional tests and EN 17240:2024 network‑compatibility validation. Contact the NB to confirm their test scope – some only handle components, not vehicles – clarify before signing.

Domestic labs with CNAS accreditation now offer NG eCall testing – you do not need to ship samples to Europe. Confirm the lab’s report‑acceptance relationship with the NB in advance.

  2. Technical Documents and MSD Data

2.1 System technical description
This is the most frequently criticised document. Describe the signal path layer by layer – from crash‑sensor trigger → TCU activation → MSD V3 packaging → IMS call setup → voice‑channel handover.

·Trigger mechanisms – both automatic (crash) and manual SOS – with decision logic.

·Communication – 4G VoLTE or 5G VoNR – IMS packet‑switched (not legacy circuit‑switched).

·GNSS positioning – multi‑constellation (GPS, Galileo, BeiDou) – describe usage logic and handover strategy.

2.2 MSD V3 data definition
Current standard: EN 15722 Ed.3 – MSD V3 has 32 fields – trigger type (auto/manual), VIN, vehicle type, powertrain (EV/ICE), GNSS coordinates and timestamp, heading, optional passenger count.
The 28‑field version is MSD V2 – do not use old templates.

2.3 GNSS positioning document
Separate document describing your multi‑GNSS solution. Under EU (EU) 2017/79 Annex VI, the dynamic positioning CEP95 horizontal error must be ≤ 50 m. The “3‑metre” figure you see online is from Chinese GB standards for BeiDou – not relevant to UN R144 or EN 17184 – do not apply Chinese standards to EU testing.

  3. Core Testing Phases

3.1 EN 17184 end‑to‑end functional tests
This is the heart of NG eCall certification:

·Automatic crash‑trigger scenarios

·Manual SOS independent path

·MSD V3 generation and transmission validation

·PSAP emulator end‑to‑end interaction

·PSAP callback auto‑answer check

Each scenario has its own test cases and pass/fail criteria.
Test standard: EN 17184:2024 – not EN 16454 (which is for legacy CS eCall circuit‑switched systems). Submitting EN 16454 for NG eCall will be immediately rejected.

3.2 Voice quality testing
Use ITU‑T P.emergency – emergency‑call‑specific – not P.1100/P.1110 (for normal hands‑free). Tests must run under both backup and primary power – AMR‑WB wideband codec is mandatory.
Exemption – only for simplified terminals with no two‑way voice (only MSD data). If you only remove the internal speaker but retain PSAP voice reception, you must still run full AMR‑WB. The final decision rests with the notified body – confirm exemption conditions in writing before starting.

3.3 Backup‑power system test
After vehicle power loss, the backup battery must support a full eCall session. Many NBs adopt a 5‑min call + 56‑min standby + 5‑min call duty‑cycle as an internal acceptance criterion – but this is not a mandatory universal clause of EN 17184.
The report must include discharge curves, switching time, and battery capacity validation. Confirm the duty‑cycle requirement with your NB before testing.

3.4 Network‑compatibility test
Validate IMS registration and call flows over 4G VoLTE and 5G VoNR in a lab emulator – covering major EU bands and modes – no need for real‑network field testing with multiple operator SIMs.

  4. Cybersecurity and Supporting Documents

4.1 UN R155 – relationship
UN R155 (whole‑vehicle cybersecurity) is mandatory for WVTA whole‑vehicle type‑approval – but for component‑level UN R144 (T‑BOX/AECS), it is not legally bundled. Tier‑1 component suppliers should not be misled into unnecessary testing.

EN 18030 (RED 3.3 cybersecurity) applies to standalone aftermarket wireless devices – not whole‑vehicle eCall – do not apply it to vehicle projects.

4.2 GDPR data compliance
eCall‑collected location and vehicle data are sensitive personal data. Prepare a data‑minimisation statement – what data is transmitted, stored, who has access, retention period.
For cloud‑connected solutions with remote monitoring, a DPIA under GDPR Article 35 is a statutory obligation to data protection authorities – not a submission file for UN R144 type‑approval. However, the manufacturer must complete it and be ready for national DPA inspections.

4.3 DoC (Declaration of Conformity)
The manufacturer self‑declares compliance with UN R144 and all applicable regulations. The signing rules for UNECE R‑regulations are not identical to CE directives – follow your notified body’s template – do not directly copy CE signing rules.

  5. Review and Issuance

After lab reports and all technical files are submitted to the notified body, the formal review begins – checking document consistency, test compliance, and data authenticity. The NB may issue requests for supplementary information – respond promptly.

Upon full approval, an NG eCall compliance certificate is issued. UN R type‑approval certificates have no unified WP.29 statutory validity – the “3‑year” figure is an internal NB management cycle for CSMS surveillance – not a regulatory clause. Validity depends on ongoing surveillance and regulatory updates.

5.1 Medium‑/long‑term trend
Industry discussions include future revisions – eCall systems reading key status via standard diagnostic interfaces and performing basic voice‑function self‑checks. These are still draft proposals or member‑state initiatives – not yet legislated. You can reserve hardware/software interfaces in design, but do not make large‑scale hardware investments based on non‑effective drafts – regulatory risk must be factored in.

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