The biggest difference between NG eCall and legacy eCall is the network: NG eCall runs on 4G/5G IMS packet-switched networks, not the old GSM circuit-switched domain. The testing standard is EN 17184, paired with CEN TS 17240 — not the EN 16454 that gets cited all over the internet. EN 16454 only covers legacy CS eCall circuit-domain testing. It has nothing to do with NG eCall.
Get the standard wrong and the lab can run the entire test suite — you still won't pass.
1.1 Three Standards, Each with Its Own Scope
EN 17184:2024 is the NG eCall end-to-end mandatory testing standard. CEN TS 17240:2024 is the companion IMS packet-switched link transmission test. EN 16072 defines MSD and end-to-end common signaling procedures — shared between NG and CS eCall. UN R144 covers AECS (Automatic Emergency Call System) for vehicles. The EU mandate for whole-vehicle NG eCall is (EU) 2024/1180, which references EN 17184.
EN 16454:2023 only applies to legacy CS circuit-domain eCall conformance testing. You can't use it for NG eCall certification. Broker materials that mix the two standards together send you in the completely wrong direction.
1.2 NG and CS Can't Substitute for Each Other
Legacy eCall tests GSM circuit-domain signaling. NG eCall tests IMS registration, SIP signaling, and VoLTE AMR-WB codec. The test environments are different, and reports can't substitute for each other. Submit a CS eCall test report for an NG eCall application and it gets returned without review.
2. EN 17184 Core Test Items
2.1 MSD V3 Data Set Integrity
NG eCall mandates MSD V3 per EN 15722 Ed.3, with 32 standard fields. The old MSD V2 only has 28 fields. The additional V3 fields cover propulsion system type and battery information. EN 17184 verifies that all 32 fields are correctly populated. Missing fields or format non-compliance with EN 15722 means an automatic fail.
2.2 Auto-Trigger and Manual-Trigger Tested Separately
Crash auto-trigger and SOS button manual-trigger follow two independent test paths. Neither substitutes for the other. When the PSAP calls back, the IVS must auto-answer — no muting or rejecting. Multiple cycles verify continuous callback capability.
EN 17184 tests the complete call establishment total link metric. The standard doesn't break out individual segment deadlines like "4 seconds to send MSD, 2 seconds to establish voice, 1 second to resend." Those don't exist as hard requirements in the standard.
2.3 GNSS Positioning and MSD Resend
GNSS testing must use a signal simulator to inject positioning scenarios — you can't rely on receiving live satellite signals outdoors. EN 17184 only verifies that complete positioning data is correctly populated in the MSD. There's no -145dBm sensitivity mandatory threshold in the standard.
MSD resend success rate of 99.5% and upload rate of 64kbps aren't explicitly mandated standard values — they're industry lab internal control benchmarks.
3. Mandatory Switch Deadlines and Data Channels
3.1 Hard Switch Deadlines
(EU) 2024/1180 sets two hard deadlines. January 1, 2026: all new vehicle type approval applications must support NG eCall. January 1, 2027: all CS eCall certificates are voided. The March 31 and December 31 dates circulating online are wrong — don't plan projects with incorrect dates.
3.2 Data Channels: Less Than You've Heard
NG eCall data channels primarily carry MSD transmission and voice. Claims about a 2025 standard adding 64kbps pre/post-crash vehicle data upload testing don't hold up. EN 16454 has no 2025 revision, and EDR (Event Data Recorder) bulk data streaming isn't part of EU NG eCall mandatory testing. Some OEMs test it in their own enterprise acceptance — but that's not a certification requirement.
3.3 PSAP Compatibility Verification
EU PSAP platforms have been upgraded to support NG eCall data channels. Downward compatibility means NG terminals connecting to legacy CS eCall PSAPs shouldn't fail just because the PSAP hasn't upgraded. There's no such thing as "PSAP 1.0/2.0 dual NG protocol stacks" — NG eCall PSAP has one IMS interface specification.
4. Lab Environment and Equipment Requirements
4.1 PSAP Simulator Is Mandatory
You can't use live network PSAPs for testing. The lab must have an authorized eCall PSAP simulator. CMW500, MD8475B, and similar cellular network emulators only provide network emulation — they can't run complete NG eCall end-to-end testing alone. They must be paired with a dedicated EN 17184 eCall simulation software module.
A lab that lists a bunch of hardware but doesn't mention the matching software? The report they produce is useless. Pure wasted effort.
4.2 GNSS Uses a Simulator
As noted above, GNSS signal simulators inject positioning signals. Different location scenarios need to be simulated, and live sky signals can't cover all test cases.
5. Post-Certification Maintenance Obligations
EN 17184 test reports don't have a fixed expiry date, but UN R144 requires re-evaluation of eCall functionality after major changes.
Swapping communication module suppliers doesn't necessarily require full retesting. Switching to a same-architecture, same-RF-performance module goes through differential testing. No full retest needed. If MSD fields change locally, only the MSD parsing items need retesting — no need to run the complete IMS and voice link.
Annual functional regression self-testing is a recommendation, not an EU regulatory mandate. Only hardware or firmware changes or standard updates trigger mandatory retesting. Pure data-only IVS devices without voice can be exempt from VoLTE AMR-WB codec testing — only terminals with voice channels are subject to it.
For NG eCall certification standards and EN 17184 testing items, contact BlueAsia technical testing and certification consultant at 13534225140 (king) or king.guo@cblueasia.com
Related News
