eCall and NG-eCall testing

• Transport network: Legacy eCall sends the Minimum Set of Data (MSD) over 2G/3G circuit-switched networks, then sets up a voice call to emergency services. NG eCall uses IP-based IMS/VoLTE communication using packet-switched networks over 4G/5G for data and voice.
• Data model: The legacy MSD is a compact payload (up to 140 bytes). NG eCall enables richer/extended information beyond the basic MSD.
• Standards: To verify legacy eCall for 3GPP eCall in-band modem standards such as EN 15722 are used. NG eCall is in line with the most recent specification ETSI TS 103 683 (NG eCall tests) and EN 17240 (IMS eCall E2E)
• Performance & reliability: IMS-based emergency calling typically achieves faster call setup and more robust connectivity than CS.
• Migration driver: As 2G/3G networks sunset, NG eCall ensures continuity and future-proofing.

How testing works (Rohde & Schwarz):

• Conformance & interoperability in accordance with ETSI TS 103 683 / EN 17240.
• Network/IMS core emulation including public safety answering point (PSAP) for LTE/5G + VoLTE/IMS scenarios (R&S CMX/CMW radio communications testers).

Yes. Regions use different systems and mandates:

• European Union – eCall (112): Mandatory for new M1/N1 (passenger/commercial) vehicle types since Mar 2018; new types must support packet-switched (4G/5G) eCall from Jan 2026. Key refs: EUR-Lex
• Russia – ERA-GLONASS: National system defined in federal law; mandatory for new vehicles (rollout finalized in 2017). Key refs: Oreanda News
• China – Accident Emergency Call Systems (AECS): New GB 45672-2025 standard published in 2025; industry sources indicate mandatory inclusion starting for M1 categories from July 2027 onwards. Key refs: Interregs
• India – AIS-140 (PSVs): Public service vehicles must have vehicle tracking + panic buttons from Jan 2019 (not full EU-style eCall). Kef refs: Ministry of Road Transport and Highways
• Japan – D-Call Net (AACN): Nationwide service adopted by major OEMs; not a blanket mandate. Key refs: Toyota Motor Corporation Official Corporate Website
• United States – NG911 (PSAP side): No federal in-vehicle eCall mandate; states upgrade 911 to IP-based NG911 (NENA i3). Key refs: Government Accountability Office

How Rohde & Schwarz helps (multi-standard):

Conformance & interoperability testing for EU eCall / NG eCall (IMS), ERA-GLONASS, and global variants, incl. LTE/5G/IMS emulation (e.g., CMX/CMW).

According to CEN EN 15722 , the MSD is a compact record sent from the in-vehicle system to the PSAP and typically includes the time of the incident, precise GNSS location, vehicle identification (e.g., VIN), direction of travel, and the eCall status (automatic/manual). In legacy eCall (CS domain), the MSD is limited to about 140 bytes; with next-generation eCall (IMS over 4G/5G), extended/optional additional data can be carried to support more advanced response (e.g., crash-severity metrics under Euro NCAP’s OAD beyond EN 15722 ).

Tip for engineers: EN 15722 models the MSD in ASN.1 (UPER), which your IVS must encode/validate before call setup.

Sources:
( Mobility & Transport - Road Safety )
( iTeh Standards )
( ETSI )
( Euro NCAP )

• Vehicles (in-vehicle system): Under Commission Delegated Regulation (EU) 2024/1180 (amending Reg. 2015/758), from 1 Jan 2026 EU authorities will refuse new type approvals that are not packet-switched (IMS) eCall compliant (CEN/TS 17184 & 17240 refs). From 1 Jan 2027, new vehicles approved after 31 Mar 2018 cannot be registered/put into service unless their eCall meets the packet-switched specs.
• PSAPs (emergency call handling centers): Delegated Reg. 2024/1084 requires PSAPs to handle IMS/packet-switched eCall—new PSAPs since 2 May 2024; all existing PSAPs by 1 Jan 2026. CS-based eCalls must continue to be supported while CS networks exist.
• Scope reminder: eCall has been mandatory for new M1/N1 vehicle types since 31 Mar 2018; NG eCall updates that mandate for 4G/5G/IMS.

China’s AECS is defined in GB 45672-2025 for M1/N1 vehicles. Compared with EU eCall, it (a) extends the MSD to carry longitudinal/lateral Δv (deceleration) and the vehicle’s location immediately before trigger, and (b) requires validation via frontal, lateral and rear-impact tests, which may be performed as sled tests with specified deceleration pulses. The standard also aligns the stack with BeiDou-priority GNSS and at least 4G full-band communication, plus requirements for a physical emergency button, voice quality, power backup, impact resistance and EMC. Implementation is phased: M1—new types 1 Jul 2027, all new vehicles 1 Aug 2028; N1—new types 1 Feb 2028, all new vehicles 1 Feb 2029.

How Rohde & Schwarz helps: Validate AECS MSD content & encoding, trigger behavior, GNSS (BeiDou-priority), cellular (≥4G), voice/EMC/impact—with standards-compliant LTE/5G/IMS & PSAP emulation and conformance/interoperability test tools.