Car manufacturers exporting to Eurasian Economic Union (EAEU) member states including Russia, Belarus, Kazakhstan, Armenia and Kyrgyzstan will inevitably come across two core terms for in-vehicle emergency call systems: UN-R144 certification and ERA-GLONASS. Although the regulatory framework is similar to the EU eCall solution, the practical implementation rules differ greatly. This article sorts out the latest updates as of the first half of 2026.

1. The Relationship Between UN-R144 and ERA-GLONASS

UN-R144 is a unified regulation issued by the UNECE WP.29 working group, fully named the technical regulation for Accident Emergency Call System (AECS). It is a global standard applicable to all signatory countries.For EU market access, manufacturers comply with UN-R144 together with EU 2015/758. For EAEU countries, UN-R144 serves as the technical basis, while compliance follows the EAC Conformity Assessment System, locally named ERA-GLONASS.

The working principle is universally adopted worldwide:Once a collision occurs, the system triggers an emergency call automatically or manually, transmits Minimum Set of Data (MSD) to the Public Safety Answering Point (PSAP), and establishes a voice call to enable rescuers to obtain accident location and key information instantly. It applies to M1 passenger cars and N1 light commercial vehicles.

Two mainstream product forms:

·Integrated AECS system built into vehicle T-Box;

·Standalone Aftermarket Accident Emergency Call Device (AECD).

Most global markets recognize UN-R144, while each region adds customized technical requirements. The EU, Turkey, Gulf countries and parts of South America directly take UN-R144 as the market entry threshold.What makes the EAEU unique is the mandatory connection to Russia’s local ERA-GLONASS PSAP, data encoding compliance with GOST standards, and the official launch of the 4G LTE ERA-GLONASS compliant channel since the second half of 2024.

  2. Core Requirements of EAEU EAC Certification

First, clarify two widespread industry rumors before introducing official requirements.

·EAEU mandates dual GLONASS + Beidou positioning

This is false information widely spread by intermediaries and some domestic marketing articles, inconsistent with official regulations.TR CU 018/2011 and its amendments clearly stipulate GLONASS satellite positioning is mandatory. GPS, Beidou and Galileo are auxiliary optional systems, not mandatory dual-mode requirements. Hardware selection only needs to ensure GLONASS compatibility; other satellite constellations are value-added options rather than rigid entry barriers.

·Cold start time is legally limited to within 60 seconds

This indicator comes from some OEM internal standards or reference values in old test specifications, with no mandatory regulatory limit in official UN-R144 and ERA-GLONASS provisions. Cold start performance depends on module suppliers, and it is not a standalone pass/fail test item in EAEU certification.

Official Mandatory Requirements

·Satellite Positioning: Stable reception and decoding of GLONASS satellite signals is compulsory; GPS/Beidou/Galileo are auxiliary alternatives. Tests require capturing GLONASS constellation and outputting high-precision location data.

·Communication Network: 4G LTE ERA-GLONASS channel has become the mainstream solution since late 2024. 2G/3G is technically available but no longer preferred for new projects. Russian operators enforce LTE B20 (800MHz) band coverage, which must be supported by T-Box hardware for local network access.

·Data Encoding: ERA-GLONASS is built on the international EN 15722 standard, with extended local fields and GOST character set adaptation. Software modification cost is low, only adding extended fields based on the existing MSD framework instead of full redevelopment.

·MSD Content: Includes VIN, accident timestamp, latitude & longitude, vehicle type, drive type, energy type, collision severity and other core fields, with encoding rules fully compliant with local PSAP decoding protocols.

  3. Four UN-R144 Certification Paths (Full Explanation)

This is the most error-prone part of the regulation. UN-R144 defines four clear certification levels:

·Part Ia: AECC CertificationCertification for individual components or combined parts such as communication modules, positioning modules and control units. It does not verify vehicle integration performance, mainly adopted by component suppliers for independent certification and subsequent OEM reference.

·Part Ib: AECD CertificationCertification for a complete independent emergency call device integrated with AECC components, covering full processes including collision detection, MSD generation and voice calling. Widely known as the "Universal Passport", the certificate can be referenced by multiple automakers without repeated full testing.

·Part II: Vehicle Integration Certification (With Valid Part Ib Approval)For automakers integrating pre-certified Part Ib devices into vehicle models. It only verifies integration performance including electrical interface matching, CAN bus communication, power management and antenna layout impact. No physical crash test required as the standalone device has been fully validated.

·Part III: Full Vehicle System Certification (No Pre-Approved Device)Mandatory for automakers adopting self-developed uncertified emergency call systems, requiring complete functional, performance and environmental tests. It is the most complex, time-consuming and costly path.

Key reminder: No physical crash test is required for any UN-R144 certification path. All tests adopt bench simulation and signal injection without real vehicle collision.

Path selection depends on product form and business strategy: Component suppliers choose Part Ia; automakers pursuing multi-model certificate sharing prioritize Part Ib; vehicles using certified Part Ib devices adopt Part II; Part III is only for completely new platform development.

  4. UN-R144 Certification Document Checklist

Most enterprises underestimate document preparation workload for first-time certification. Intermediaries often package non-mandatory items as compulsory charges; below is the official mandatory document list.

Category 1: Enterprise Qualification Documents

Overseas manufacturers require an EAEU local authorized representative with valid business license. EAC conformity assessment mandates a Production Conformity Control Plan (CoP) for mass production consistency control with standardized format.ISO 9001 certification is not a mandatory prerequisite for EAC eCall certification and will not result in application rejection if unavailable.

Category 2: Core Technical Documents (Audit Focus)

Technical specification covering GLONASS positioning parameters, 2G/3G/4G communication bands, CAN bus protocol and emergency trigger logic;Design drawings including system block diagram, circuit schematic and antenna design layout;Software documents with version number, version description and OTA update management rules. Non-safety parameter adjustments irrelevant to MSD data and trigger logic do not require authority notification.

Category 3: Test Reports

Tests must be conducted by EAEU recognized laboratories, covering collision trigger interface verification, MSD data integrity, voice call establishment, GNSS positioning accuracy, all completed via bench testing without physical crash.

Important clarification:UN-R144 certification does not include UN R10 EMC testing and environmental reliability tests (high/low temperature, vibration, shock). EMC compliance follows independent UN R10 regulations, and reliability tests belong to separate vehicle/component environmental standards. Bundling these tests into UN-R144 quotation is unnecessary overcharging by intermediaries.

EAC Certificate Validity

EAC certificates for in-vehicle equipment are valid for 5 years with mandatory re-assessment upon expiration; permanent validity is not allowed under EAEU rules.

  5. Core Differences Between EAEU and EU eCall Systems

Many automakers apply EU eCall experience to the EAEU market, ignoring three critical gaps:

·PSAP Docking Mode: The EU allows PSAP simulation testing via lab instruments such as CMW500; EAEU mandates physical joint debugging with Russia’s real ERA-GLONASS system, leading to high communication cost and uncertain scheduling.

·Satellite Positioning Rules: The EU only requires GPS or Galileo; EAEU enforces mandatory GLONASS support as a policy-based technical requirement.

·MSD Encoding Framework: Both adopt EN 15722 foundation, while EAEU adds GOST character set adaptation and local extended fields, requiring regional software configuration rather than fully independent code development.

Additional note:The EU is promoting NG eCall (4G/5G IMS architecture) with phased phase-out of 2G/3G, while light commercial vehicles and existing derivative models enjoy long-term exemptions. The claim of full 2G/3G ban by 2027 is an overstatement leading to wrong project decisions.

  6. UN-R144 Certification Cycle & Cost

With mature hardware/software adaptation and smooth Russian joint debugging, the certification cycle ranges from 3.5 to 5 months. 6-8 months is an abnormal cycle caused by rectification delays and document supplements, not the standard timeline.

For cost, complete UN-R144 testing + EAC certification + ERA-GLONASS joint debugging has a much higher overall cost than a basic UN-R144 certificate. Low-price quotations usually exclude physical network joint debugging fees, resulting in budget overruns in later stages. Confirm full-process coverage including Russian joint debugging, local PSAP testing and EAC certification before signing contracts.

For Eurasian Union UN-R144 certification, consult Blueasia technical certification advisor: 13534225140