EU eCall 4G/5G Transition: Where New Type-Approval and Testing Demand Will Emerge

Commission Delegated Regulation (EU) 2025/1871 entered into force on 17 November 2025 and updates the technical requirements and test procedures for 112-based eCall. The Commission states that the purpose is to keep eCall operational as legacy 2G and 3G communication networks are switched off and the system moves toward packet-switched communication technology.

The first transition point arrived on 1 January 2026. From that date, national authorities must refuse new type approvals or extensions for vehicles, systems, components, or separate technical units that fail to meet at least the transitional eCall communication specifications identified in Article 3(1), where the manufacturer requests approval under those provisions.

The larger commercial step arrives on 1 January 2027, when new approvals must comply with EN 17184:2024 and EN 17240:2024 and new approvals for vehicles, systems, and separate technical units must also meet the new backup-power requirements. A further 1 January 2028 milestone adds roadworthiness-test readiness for new approvals.

It would be easy to describe the change as a telecommunications migration from 2G/3G to 4G/5G. For homologation purposes, the regulatory workload is broader. The amended framework changes applicable standards, test procedures, communication pathways, backup-power testing, and the evidence expected when existing approvals are extended.

That means an OEM, Tier supplier, telematics supplier, or eCall separate technical unit manufacturer may face several work packages around the same platform: hardware or communication-module changes, documentation of the differences from the original approved system, representative testing, approval-extension strategy, and interaction with a Technical Service or approval authority.

For a service provider, the more useful commercial question is therefore not 'who still uses 2G?' but 'which approved eCall systems are being modified, extended, or newly approved against the 2027 standards and test procedures?'

The amended Delegated Regulation (EU) 2017/79 contains a specific route for extending approvals granted before 1 January 2027. A Technical Service may exempt an updated system from the full-scale impact test and subsequent audio-equipment test in certain cases, but the manufacturer must document and explain the changes to the Technical Service and the type-approval authority.

Where the communication part is modified and a vehicle crash test is already being conducted for another purpose, the amended eCall system must be included in that test. If the communication modification affects other parts of the eCall system, the regulation requires the full-scale impact test and the subsequent audio-equipment test.

This creates a practical decision point for vehicle programs and eCall suppliers: determine whether the change is isolated enough for a lighter extension route or whether it triggers a broader revalidation campaign. That assessment itself can create demand for homologation engineering and Technical Service support.

The revised test procedures explicitly support emergency calls performed in the packet-switched domain. They also require dedicated PSAP test points or simulators under Technical Service control and specify how public, non-public, or wired test-network arrangements can be used for approval testing.

That matters commercially because not every laboratory or engineering organization has equivalent capability for packet-switched eCall validation. Service providers able to combine mobile-network simulation, PSAP-side testing, audio verification, positioning checks, and type-approval evidence may become more relevant as 2027 approaches.

The regulation also updates the test structure around location information and test eCalls, so migration work may touch both communications and the wider evidence package used during approval.

From 1 January 2027, national authorities must refuse new type approvals for vehicles, systems, or separate technical units that do not meet the new requirements for backup-power performance set out in Annex X to Delegated Regulation (EU) 2017/79 as amended.

This is commercially significant because eCall must remain functional after an accident even if the vehicle's main power supply is disconnected. The revised framework therefore adds explicit test procedures for a backup power source, where fitted, and for a secondary vehicle power supply that may be used after a crash.

For suppliers and vehicle manufacturers, the resulting workload can include power-system design review, durability or performance validation, test execution, evidence preparation, and approval documentation. The exact external service requirement depends on what is done in-house and on the architecture of the eCall system.

A second wave arrives on 1 January 2028. New type approvals for vehicles, systems, or separate technical units must then meet technical requirements that enable periodic roadworthiness testing of the eCall system over the vehicle lifecycle.

That requirement expands the problem beyond initial approval. It links the design of the system and its diagnostics or testability to future inspection needs, which can create additional validation and documentation work for vehicle manufacturers and suppliers.

For providers serving both homologation and vehicle-inspection ecosystems, the 2028 deadline can therefore represent a separate demand window rather than merely a continuation of the 2027 communications migration.

Not every M1 or N1 manufacturer represents the same opportunity. The strongest signal combines a vehicle or eCall system with an upcoming approval event, a communication-module change, an approval extension, a legacy network dependency, a backup-power redesign, or a test-capability gap.

The same logic applies to suppliers. A telematics or eCall STU supplier that is changing hardware for packet-switched operation may create technical-service demand even when the final vehicle manufacturer owns the whole-vehicle approval strategy.

RegDemand treats these as evidence-backed opportunity hypotheses. A regulation creates the trigger, but the qualified commercial opportunity comes from matching that trigger to the specific program, approval route, technical change, responsible organization, and likely buying timing.

Traditional regulatory monitoring can tell a sales team that EU eCall standards have changed. Regulatory buying intelligence adds the commercially useful layer: which approved systems need an extension, which new programs fall under the 2027 standards, which architectures are likely to require packet-switched testing or backup-power validation, and which organizations may need external Technical Service or homologation support.

Candidate service categories include eCall communications testing, PSAP-simulator testing, positioning and audio validation, backup-power testing, crash-linked revalidation, documentation for approval extensions, STU/component approval, whole-vehicle homologation support, and 2028 roadworthiness-readiness validation.

Those categories are not claims of confirmed buyer intent. They are the service needs most directly connected to the regulatory changes and therefore the places where evidence-based prospecting can begin before an RFQ is public.