“Validity” is the most misunderstood term in NG‑eCall certification. Companies ask about the certificate’s “years of validity” as if it were a quality‑test report with a fixed expiry date. That is the wrong way to think about it.

For EU whole‑vehicle type approval and NG‑eCall component certificates, validity works differently.

1. NG‑eCall Has No Unified Statutory Expiry

1.1 Valid as Long as You Maintain Compliance

(EU) 2024/1180 does not state a 3‑year or 5‑year validity for NG‑eCall certificates. Validity is not defined by time – it is defined by the manufacturer’s continued compliance.

·Annual CoP (Conformity of Production) checks,

·Major design changes are assessed,

·Product quality remains acceptable –
If these are maintained, the certificate is valid. Suspension or revocation only occurs when compliance fails.

1.2 Different from CCC

China’s CCC has a mandatory 3‑year renewal cycle – NG‑eCall has no such fixed cycle. However, it is constrained by standard updates, change assessments, CoP audits, and member‑state transition policies – not unconditionally permanent.

  2. Whole‑Vehicle vs. Component – Separate Management

2.1 Whole‑Vehicle WVTA – Model‑Based

NG‑eCall is part of WVTA – no expiry date – but annual on‑site CoP audits are required by the NB (or their delegate). If the audit fails, the vehicle’s approval status becomes non‑compliant – cannot ship under that approval.

2.2 Component – NB Practice of ~5‑Year Cycle

Component T‑Box NG‑eCall certificates have an issue date but no expiry date. CoP is based on random NB audits – not mandatory annual on‑site inspection.
Important: component manufacturers are not legally required to submit annual compliance reports with CMA‑sampled retest data – most NBs only require retention of consistency records and batch production logs.

  3. Official Deadlines and Transition Rules

·The key date is 1 August, not 1 January.
(EU) 2024/1180 states:

·From 1 August 2026, new type approvals will no longer accept pure CS‑eCall solutions.

·From 1 August 2027, new vehicles with legacy CS‑eCall cannot be registered.
The industry’s “1 January” simplification is a miscommunication.
Important: After 1 August 2027, new vehicles cannot be registered – the CS‑eCall type‑approval certificate itself does not automatically expire. The document remains; it just cannot be used for new registrations – legally different.

·Transition certificates under CEN/TS 17184:2022 (old draft) have no uniform automatic expiry – each NB and member‑state authority handles them differently.
1 January 2028 is the full‑enforcement date for EN 17184:2024 – not the date transition certificates collectively expire. Two separate things.

  4. CoP – The Core Compliance Mechanism

4.1 Whole‑Vehicle – Mandatory Annual On‑Site Audits

CoP ensures mass‑production matches the approved test sample.
OEMs undergo annual NB on‑site audits – checking production‑line process documents, key‑component procurement records, outgoing inspection records, and random BOM checks.

4.2 Components – Random Audit Model

Components follow a random‑audit model – NBs conduct periodic (or ad‑hoc) sample checks – not necessarily annual on‑site. Only if an audit fails or CoP records are seriously deficient does suspension occur.
Simply not submitting an annual report usually does not directly trigger suspension – the NB will issue a correction notice with a grace period. Direct suspension is triggered by failed CoP audits, failed random samples, or unapproved major changes that have already shipped.

  5. Suspension vs. Revocation

·Suspension – reversible. Common causes: CoP audit failure, sample‑test failure, unapproved major change discovered. During suspension, you cannot ship under that certificate – existing inventory is unaffected, but new production cannot use it. Complete remediation within the deadline – certificate can be restored.

·Revocation – irreversible. Causes: refusal to remediate, persistent non‑conformance after remediation, or systemic fraud. Revoked certificates are permanently void – must restart full approval.

  6. Major‑Change Assessment Rules

·Not all changes are “major”. Replacing the comms module, T‑box hardware revision, IMS stack upgrade, or cell‑supplier change – all require assessment, but not automatically classified as major. The NB decides case‑by‑case under UN R144 rules – not arbitrary. A pin‑to‑pin compatible module with identical parameters may be considered minor by some NBs.
Production before assessment completion: depends on the nature of the change. It is normal practice to complete prototype validation and submit the assessment application in parallel – production is not absolutely forbidden while assessment is pending. However, placing changed products on the market without filing the change is indeed a violation.

·Only eCall‑link changes trigger NG‑eCall assessment. OTA changes to vehicle‑wide systems that do not affect eCall trigger logic, IMS calling, MSD generation, or backup‑power management – do not require NG‑eCall change assessment.

  7. Common Technical Traps

·UN R155 is not mandatory for component eCall. A standalone NG‑eCall T‑Box applying for E‑mark type approval is not legally required to bundle UN R155 (or EN 18031) cybersecurity compliance. UN R155 is a WVTA requirement for whole vehicles – not a component‑access condition. OEMs may additionally require cybersecurity documents commercially – but that is a contract matter.

·Annual maintenance does not mean submitting a GDPR privacy‑review report every year. GDPR is a general market‑compliance obligation – it is not a mandatory CoP filing item for NBs.

·MSD V2/V3 compatibility – decided by NB. New standards recognise V2; new type‑approval applications must have V3 generation capability – but they are not forced to transmit only V3. If the product natively supports V3, a pure message‑version optimisation is not automatically a major change – the NB decides case‑by‑case.

·66‑minute backup‑power duty cycle (5‑min call + 56‑min standby + 5‑min call) comes from (EU) 2025/1871 Amendment Annex X – applies only to shared backup‑power architectures. Dedicated independent backup batteries are not required to run this full cycle.
IMS call‑setup latency – EN 17184 has no globally mandated “≤3 seconds” statutory limit. Some labs use 3 seconds as an internal acceptance benchmark – it is not an official yardstick for major‑change determination.

For NG‑eCall certification, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.