eCall (emergency call) certification for vehicles has two layers. UN R144 is the UNECE global regulation covering the whole‑vehicle AECS (Automatic Emergency Call System). For the EU, (EU) 2024/1180 mandates NG eCall under whole‑vehicle type approval (WVTA). UN R144 test reports can be used for EU access, but the EU adds GDPR compliance documents and local EU representative materials – the two are not fully equivalent.

1. Type Approval Application Form

The UN R144 application must clearly state: vehicle model, VIN applicability range, and eCall system type – NG or CS.
Critical deadline: From 1 January 2026, all new vehicle types and extensions must use NG eCall. However, existing CS eCall certificates remain valid for production and registration until 1 January 2027.

1.1 Technical Description Document

This is where most applicants stumble. You must detail:

·Overall eCall system architecture

·Trigger mechanisms – automatic (crash sensor) and manual (SOS button)

·Communication – 4G/5G IMS packet‑switched

·PSAP interface logic

·MSD V3 data content and format

·Multi‑constellation GNSS positioning

The signal path must be fully traceable: from crash‑sensor acceleration threshold → TCU activation → MSD V3 packaging → IMS call setup → voice channel handover. Every step needs technical parameters and signal flow.

1.2 System Block Diagram and Communication Topology

Provide a complete eCall system block diagram and communication topology – label each module, protocol type per link, and transmission direction. Also include power management: backup battery switching circuit and isolation from the vehicle’s main power supply.

1.3 EU Representative (EC‑REP) Authorisation

Non‑EU manufacturers must appoint an authorised representative physically located in the EU. The authorisation agreement must be signed and cover all communications with the Type Approval authority.

  2. MSD Dataset and Positioning Documents

2.1 MSD V3 Data Definition File

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

2.2 GNSS Positioning Scheme

Document your multi‑GNSS solution – GPS, GLONASS, Galileo, BeiDou. For each, describe usage logic and switchover strategy.
Critical trap: Under EU (EU) 2017/79 Annex VI, the GNSS dynamic positioning CEP95 horizontal error must be ≤ 50 m. The “3‑metre accuracy” often cited online is from Chinese GB standards for BeiDou – it does not apply to UN R144 or EN 17184.

  3. eCall Test Reports

3.1 End‑to‑End Functional Test Report

The core NG eCall test standard is EN 17184:2024 – not EN 16454 (which is for legacy CS eCall circuit‑switched systems). Submitting EN 16454 for NG eCall will be rejected immediately.
Tests must cover:

·Automatic crash‑trigger scenarios

·Manual SOS activation path

·MSD V3 generation and transmission

·End‑to‑end PSAP emulator interaction

·PSAP callback auto‑answer verification

Each scenario must have its own test cases and pass/fail criteria.

3.2 Voice Quality Test

Use ITU‑T P.emergency (emergency‑call‑specific standard) – not P.1100/P.1110 (which are for normal hands‑free). Tests must run under both backup and primary power, and AMR‑WB wideband codec is mandatory.
Exception: Pure‑data IVS devices with no two‑way voice (only MSD data) can skip voice coding tests. But if you only remove the internal speaker while retaining PSAP voice reception, you must still run full AMR‑WB.

3.3 Backup Power System Test

The backup battery must support at least one full eCall session after vehicle power loss. The current EN 17184 already mandates a dual‑call endurance requirement – a 5‑minute call + 56‑minute standby + another 5‑minute call. (This is not a new “2027 tightening” – it’s already in force.)
The report must include discharge curves, switching time, and battery capacity validation.

3.4 Network Compatibility Test

NG eCall must be validated over 4G VoLTE and 5G VoNR IMS registration and call flows. The regulation only requires verification on major EU bands – this can be done entirely in a lab emulator; multi‑MNO real‑network field testing is not mandatory.

  4. Compliance Declarations and Security Files

4.1 Privacy and GDPR Compliance Statement

eCall‑collected location and vehicle data are sensitive personal data. You must submit:

·Data minimisation explanation – what data is transmitted, stored, who has access, retention period.

·For cloud‑connected solutions with remote monitoring, a DPIA (Data Protection Impact Assessment) under GDPR Article 35 is legally mandatory – not optional. Missing it = automatic rejection.

4.2 DoC (Declaration of Conformity)

The manufacturer must self‑declare that the product complies with UN R144 and all applicable EU directives. The DoC must be signed by the manufacturer or EU representative’s legal representative – a Chinese factory engineer, even with internal authorisation, has no signing authority.

4.3 Vehicle Cybersecurity (UN R155)

When pursuing UN R144 whole‑vehicle approval, remember that UN R155 (whole‑vehicle cybersecurity) is a mandatory companion. EN 18031 applies only to stand‑alone aftermarket wireless devices – do not apply it to whole‑vehicle eCall projects.

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