The certification process and cycle of in-vehicle emergency call systems for exporting to Russia, Belarus, Kazakhstan and other EAEU countries differ greatly from other global markets. This article breaks down every procedure, approval link and time cost in detail.
-Select the Correct Certification Path (Project Core Premise)
Path selection determines all subsequent procedures and cycle arrangements. UN-R144 has four clear certification levels:
·Part I/A (AECC): For individual components such as communication and GLONASS positioning modules. Certificates cannot be directly used for vehicle compliance, only for supplier component qualification.
·Part I/B (AECD): For complete standalone emergency call devices such as T-Box units. Certificates can be referenced by multiple vehicle projects, the most cost-effective mainstream option for most export projects.
·Part II: Vehicle Integration Certification: Only available with a valid Part I/B certificate, verifying only vehicle-level integration performance without repeated device full testing, saving significant time and cost.
·Part III: Full Vehicle Certification: For vehicles adopting newly developed uncertified emergency call systems. Only chosen for completely new platform development due to complex procedures and high cost.
Path selection basis: Existing valid device certificate, certificate sharing demand for multiple models, and vehicle integration timeline.
-Lock Technical Solution (Hardware & Software Confirmation)
Pre-certification technical solution confirmation is more important than formal testing:
·Confirm communication mode: 4G LTE ERA-GLONASS is the mainstream solution for Russia T-Box; 4G IMS + CS dual-stack architecture is compliant with no mandatory 2G fallback requirement.
·Positioning module selection: GLONASS is legally mandatory; multi-mode fusion with GPS/Beidou/Galileo improves positioning stability with no regulatory restrictions.
·LTE B20 (800MHz) band coverage: Not a written regulatory mandate but a practical requirement for Russian local network coverage, confirmed before hardware finalization.
·MSD data format adaptation: Based on EN 15722 with GOST character set and local extended fields, requiring regional software configuration instead of independent code development.
·Pre-technical communication with Russian authorities: Conduct informal technical clarification via local partners in advance to avoid document rejection and rework after official submission.
-Compile Technical Document Package Compliant with Russian Standards
Document preparation is the most underestimated workload, requiring restructuring per GOST standards and TR CU 018/2011 logic instead of simple Chinese-to-Russian translation.
Core mandatory documents:
·System design files: Architecture description, hardware schematic, software module division, communication protocol stack, MSD data flow and emergency trigger logic.
·Data transmission & compliance statement: Clarify transmission channel, local data storage and access authorization; no complex network security penetration testing required for civilian eCall terminals.
·Software version management plan: Clear certified software version and OTA update rules; only core safety logic modifications require authority notification.
·Production Conformity Control Plan (CoP): Define mass production consistency control rules; no mandatory factory on-site audit for T-Box and eCall device certification under normal circumstances.
-Domestic Laboratory Testing
Domestic pre-testing ensures one-pass formal certification and reduces rectification risks. Core UN-R144 test items:
·Functional verification: Automatic/manual trigger logic, MSD data integrity, GNSS positioning accuracy (max 50m horizontal error), voice call quality and multi-network communication stability.
·All tests adopt bench simulation and signal injection; no physical vehicle crash test required. Vehicle crash testing belongs to separate whole-vehicle safety regulations, irrelevant to UN-R144 eCall certification.
The biggest cycle variable is rectification time; pre-testing in advance effectively shortens the overall project cycle.
-ERA-GLONASS Platform Access & Physical Network Joint Debugging
The highest communication cost link in the entire certification chain, completed locally in Russia with real ERA-GLONASS system docking to verify emergency call establishment, MSD transmission and voice communication.With official direct Russian cooperation channels, joint debugging takes 2 to 6 weeks. Delays are mainly caused by multi-layer outsourcing, time difference and holiday scheduling. Choosing a service provider with direct Russian joint debugging channels is critical.
-EAC Conformity Assessment Audit
After lab testing and Russian joint debugging, certification bodies review technical documents, verify test report consistency and approve EAC certificate issuance. The audit cycle is 1 to 2 months with complete documents; document inconsistency will prolong the review period.
EAC certificates are valid for 5 years with no annual maintenance fee. Only substantial hardware, MSD or trigger logic changes require supplementary assessment. No vehicle database registration is needed for standalone T-Box/eCall device EAC certificates (only for whole-vehicle type approval).
-Whole-Vehicle Integration Certification
For model-specific market access, complete vehicle integration certification after obtaining the Part I/B device certificate. Under Part II rules, only vehicle integration matching is verified without repeated device testing, with shorter cycle and lower cost. Prior Part I/B certificate application is the most cost-effective strategy for multi-model automakers.
2. Overall UN-R144 Certification Cycle
·Ideal cycle (mature solution + one-pass test + smooth joint debugging): 3.5 to 5 months from launch to certificate issuance.
·Practical planning cycle (including pre-preparation, rectification and scheduling): 10 to 12 months recommended for first-time applicants.
Key reminder: Lock Russian joint debugging scheduling in the later stage of domestic lab testing instead of waiting for test report issuance to avoid overall project delays. Substantial software/hardware changes within the 5-year certificate validity period require advance authority confirmation for filing.
For Eurasian Union UN-R144 certification, consult Blueasia technical certification advisor: 13534225140
相关新闻
