When automakers start planning an NG-eCall certification project, the first question is almost always about timeline. NG-eCall is not a single test. It chains together communication, positioning, data security, and real-world road testing into one sequential pipeline. One stage stalls, and everything downstream shifts.
·Component Certification: 6-8 Weeks (Best Case)
If everything goes smoothly, component certification from sample submission to certificate takes 6 to 8 weeks. The prerequisite is that the sample passes on the first attempt with no major remediation needed. If the communication module's IMS protocol stack has gaps or the backup power supply cannot sustain the full 66-minute cycle, expect delays measured in months, not weeks.
·Whole-Vehicle Certification: 4-6 Months (Normal Pace)
For a standard M1 passenger vehicle, the normal timeline runs 4 to 6 months. This assumes core component certificates are already in hand, technical documentation is complete, and the sample vehicle configuration is locked.
High-end vehicles with advanced driver assistance and V2X capabilities push the timeline to 7 to 10 months. The reason is system integration complexity. V2X and NG-eCall share the same hardware platform, but wake-up logic and crash trigger conditions must be coordinated within the same domain controller. Software integration debugging tends to require multiple iterations.
·Parallel Import Vehicles: 10-14 Months
Parallel import vehicles lack original factory component certificates and cannot reuse batch vehicle test data. Full independent testing pushes the timeline to 10 to 14 months. Plan accordingly if this is your situation.
Preparation Is the Most Underestimated Phase
People assume the testing takes the longest. In reality, inadequate preparation is what kills project schedules.
If technical documents are incomplete, the laboratory will not accept the sample. If documents contain errors, you may find out halfway through testing and have to start over.
Technical documentation must pass GDPR review. Translating a user manual into English is not enough. Data encryption schemes, transmission link security descriptions, local storage time commitments, and user informed consent text all need to be prepared and reviewed by a data compliance specialist beforehand. Many projects stall here for a month, not because the content is hard to write, but because teams do not know how deep the EU privacy compliance requirements go before the submission is considered acceptable.
Sample vehicle status must be locked early. NG-eCall tests the mass production configuration, not an engineering prototype. The lab checks VIN codes and component BOM before testing. If the sample does not match the production version, they require a new sample. That means sourcing another production-spec vehicle, which can take weeks.
The Real Time Cost of Laboratory Testing
Bench testing takes 3 to 4 weeks. Road testing takes 2 to 3 weeks. But within those numbers, two hard-threshold items cause the most trouble.
IMS call setup latency must be 3 seconds or less per EN 17184:2024, down from the old CS-eCall standard of 10 seconds. If the module's IMS protocol stack is not properly tuned, this test fails repeatedly. Each failed attempt means debugging, firmware patches, and rescheduling the lab slot. We have seen a single module take four iterations to pass this test, adding five weeks to the project.
Shared backup power supply must sustain the full 66-minute cycle: 5 minutes of call time, 56 minutes of standby, then another 5 minutes of call time. Battery capacity that is calculated too tight will fail this test. Hardware changes mean new samples, new test scheduling, and more delays.
MSD V3 only reserves video transmission fields. EU regulations do not mandate onboard cameras, so no additional video hardware development time is needed.
Dual-mode fallback testing requires advance scenario planning. NG-eCall prioritizes IMS VoIP packet domain, falling back to CS circuit domain only when the local PSAP does not support VoIP. Both bench and road testing must simulate this switching scenario. Teams that do not plan the test sequence in advance end up needing a second round of testing.
Notified Body Review Timeline
After test reports are issued, they go to the EU notified body for review. This typically takes 2 to 4 weeks, assuming the reports are clean and documentation is complete.
If you use a domestic laboratory with mutual recognition qualifications, the test reports still need to be sent to the EU notified body for secondary review. This adds 2 to 3 weeks. Build this buffer into your project schedule from the start.
In the second half of 2026, lab scheduling will tighten significantly. Expedited channels can compress lab testing to around 3 weeks, but fees increase by 30% to 50%. Decide whether the time savings justify the cost before committing to the rush option.
Transition Certificate Supplementary Retesting
Transition certificates obtained in 2025-2026 were tested against the draft EN standard. Before January 1, 2028, they must undergo supplementary testing against the final EN 17184:2024 standard.
Supplementary retesting takes 4 to 6 weeks, assuming no major hardware changes. If the communication module or T-Box supplier was changed during the transition period, a change evaluation plus partial retesting is required, and the timeline approaches that of a full recertification.
Why Schedules Will Get Tighter After 2027
After January 1, 2027, all legacy CS-eCall certificates become invalid. Every new vehicle exported to the EU must hold an NG-eCall certificate. After January 1, 2028, all transition certificates expire as well. In the lead-up to both deadlines, laboratories and notified bodies will be operating at maximum capacity.
Booking slots will become harder. Expedited fees will climb higher. Projects that could have been completed in 4 months may stretch to 6 or 7 simply because lab availability is constrained.
2026 is the window. If your team has been holding off on starting NG-eCall certification, waiting another six months will not make the project cheaper or faster. It will make both worse.
Our recommendation for automakers targeting EU market entry in 2027 or 2028: start the gap analysis in early 2026, lock component certificates by mid-year, and aim for whole-vehicle certification completion before the Q4 2026 rush begins. The difference between starting in January versus starting in July is not six months of timeline. It is six months of timeline plus three months of scheduling delays plus higher expedited fees.
BlueAsia Testing is a Huawei HiCar authorized certification organization, recognized with the "Excellent Certification Organization" award in 2025. We help automakers and component manufacturers plan realistic NG-eCall certification timelines and coordinate testing resources.
For NG-eCall certification timeline consultation, contact BlueAsia Testing: 13632500972 (Benson)
相关新闻
