EU eCall Type Approval: How Long Is It Valid, and When Does It Need to Be Updated?

Understanding approval validity, technical changes, regulatory updates and long-term compliance

The EU eCall system is an important part of vehicle safety compliance in the European market. It is designed to automatically contact emergency services when a serious road accident occurs, transmitting essential information such as the vehicle's location and incident details through the European 112 emergency number.

For vehicle manufacturers and eCall system suppliers, obtaining type approval is only one part of the compliance process. Another important question often arises after approval has been granted:

How long does an eCall type approval remain valid? Does it need to be renewed after a certain number of years?

The answer is not as straightforward as a conventional certificate renewal cycle. EU eCall approval is governed by the applicable vehicle type-approval framework. Its continued validity depends on factors such as the approved vehicle type, technical modifications, changes in regulatory requirements and the status of production.

There is no general fixed annual or five-year renewal cycle specifically established for eCall approval. However, this does not mean that an approval remains valid indefinitely under all circumstances.

Understanding the relevant regulatory requirements is essential for manufacturers who want to avoid unnecessary retesting or unexpected compliance issues.

1. Understanding EU eCall Type Approval

The term "eCall certification" is commonly used in the automotive industry. Technically, it refers to type approval for a vehicle's 112-based in-vehicle emergency call system, or for the relevant eCall equipment.

Under Regulation (EU) 2015/758, the mandatory eCall requirements apply to new vehicle types in categories M1 and N1.

• M1: Vehicles designed and constructed primarily for passenger transport, with no more than eight passenger seats in addition to the driver's seat.

• N1: Vehicles designed and constructed primarily for the carriage of goods, with a maximum mass not exceeding 3.5 tonnes.

Since 31 March 2018, new types of vehicles in these categories have generally been required to be equipped with a 112-based eCall system, subject to the exemptions provided by the legislation.

Depending on the product and approval approach, type approval may cover:

• The complete vehicle with its installed eCall system.

• An in-vehicle eCall system.

• An eCall Separate Technical Unit (STU).

• Relevant eCall system components.

The main regulatory framework includes:

• Regulation (EU) 2015/758: Establishes the requirements for deploying 112-based eCall systems in vehicles.

• Commission Delegated Regulation (EU) 2017/79: Specifies technical requirements and test procedures for vehicles, STUs and components.

• Regulation (EU) 2018/858: Establishes the broader framework for vehicle type approval, conformity of production and market surveillance.

• UN Regulation No. 144: Provides the corresponding UNECE approval framework for eCall systems.

For technical documentation, the Minimum Set of Data (MSD) must also comply with the applicable EN 15722 requirements.

It is important to distinguish between vehicle approval and STU approval. Although they are related, they are not interchangeable. An approved STU does not automatically mean that the complete vehicle installation has fulfilled all relevant type-approval requirements.

2. Does eCall Type Approval Have an Expiry Date?

This is one of the most frequently asked questions by vehicle manufacturers and eCall equipment suppliers.

Unlike certificates that require renewal at fixed intervals, eCall type approval does not have a general fixed renewal period specifically defined by Regulation (EU) 2015/758.

However, its validity is subject to the wider requirements of Regulation (EU) 2018/858.

For whole-vehicle type approval, Article 35 establishes a regulatory compliance verification mechanism. For M1 and N1 vehicles, the approval authority must verify compliance with the relevant regulatory requirements seven years after the latest update of the information package.

The regulation also identifies circumstances in which an EU type approval can become invalid. These include the introduction of mandatory new requirements that cannot be addressed through an extension, failure to meet applicable requirements, and certain circumstances involving the definitive discontinuation of production.

For manufacturers, the practical takeaway is clear:

An eCall approval should not be treated as a certificate that simply expires after a fixed number of years. Its status needs to be assessed against the approved type, applicable regulatory requirements and any changes made during its lifecycle.

The following stages deserve particular attention.

3. What Happens After eCall Approval Is Granted?

Once approval has been obtained, manufacturers should maintain a complete technical record linked to the approved vehicle or product type.

This is important because future modifications, conformity of production checks and regulatory reviews will all rely on the original approval documentation.

3.1 Verify Approval Documents

The approval certificate, information package and test reports should be checked to ensure that their approval numbers and technical details are consistent.

For vehicle manufacturers, it is also advisable to maintain a clear installation record showing which approved eCall system, STU and components are fitted to each relevant vehicle type.

3.2 Keep the Approved Configuration on Record

The configuration tested and approved should be documented in detail, including:

• Sample and hardware identification numbers.

• Hardware and software versions.

• Communication module and antenna configuration.

• MSD generation and transmission logic.

• GNSS positioning and emergency call functions.

• Relevant supplier and component information.

These records provide a technical reference for evaluating future changes.

3.3 Maintain Complete Technical Documentation

The original application documents, sample lists, test reports, approval certificates and related technical records should be properly archived.

They are not simply documents required to complete the initial certification process. They also provide the reference point for subsequent conformity of production (COP) assessments.

4. When Do eCall Modifications Require a New Assessment?

Technical changes are one of the main reasons why manufacturers need to review an existing approval.

A vehicle facelift, hardware replacement or software update does not automatically mean that a completely new approval is required. However, every change should be evaluated against the original approved configuration and the applicable regulatory requirements.

Under Articles 33 and 34 of Regulation (EU) 2018/858, amendments to an existing EU type approval can generally be handled as revisions or extensions, depending on their impact.

Minor changes or revisions

Where the approval authority determines that a change does not affect compliance and no additional inspections or tests are necessary, the change may be handled as a revision of the information package.

Extensions of approval

Where additional inspections or tests are required, the approval authority may process the change as an extension. This may involve supplementary testing and an updated approval certificate.

New type approval

If the proposed modification cannot be covered by an extension of the existing approval, a new type-approval application may be necessary.

In practical terms, manufacturers should pay particular attention to the following changes.

Hardware and Supplier Changes

Replacing the main control unit, communication module, GNSS receiver or antenna may affect the original approved configuration.

Changing a supplier does not automatically require a new approval, but the technical impact must be evaluated. Compatibility, performance and the relevant test requirements should all be considered.

Software Updates

Software changes can have a direct impact on eCall functionality.

Particular attention should be paid to changes involving:

• Emergency call triggering logic.

• MSD generation, encoding and transmission.

• Audio communication between the vehicle and emergency services.

• GNSS positioning and location transmission.

• Network connectivity and communication protocols.

Even if a software update appears minor from a user-interface perspective, its impact on the approved functions should be assessed before implementation.

Approval Extension and Documentation

Where an extension is necessary, manufacturers should clearly identify:

• The scope of the proposed modification.

• The differences from the original approved configuration.

• Existing test reports that can still be used.

• Additional tests or assessments required.

• Updated technical documents and approval records.

A clear change history makes future approval reviews much easier and helps avoid unnecessary repeated testing.

5. How Do New eCall Regulations Affect Existing Approvals?

The eCall regulatory framework continues to evolve, particularly as European mobile networks move away from traditional circuit-switched technologies towards IP-based communication.

For manufacturers, this means that regulatory updates should be monitored carefully. However, a new standard does not automatically invalidate every previously approved eCall system.

The key is to understand which requirements apply to new approvals, approval extensions and existing vehicle types, as well as the relevant transition periods.

Important Regulatory Developments

Regulation (EU) 2015/758

This remains the main legislative framework for 112-based eCall deployment in vehicles.

Commission Delegated Regulation (EU) 2017/79

This establishes the technical requirements and test procedures for vehicle eCall systems, STUs and components.

Commission Delegated Regulation (EU) 2024/1180

This regulation updates the referenced eCall standards to accommodate IP-based communication using the IP Multimedia Subsystem (IMS).

It introduced a transition towards IMS-based eCall protocols, including the relevant technical specifications for high-level application protocols and end-to-end conformance testing.

Commission Delegated Regulation (EU) 2025/1871

This regulation further updates the eCall technical framework, including requirements relating to backup power supply and secondary vehicle power supply.

It also updates the relevant standards and sets 1 January 2027 as the mandatory application date for EN 17184:2024 and EN 17240:2024.

These developments are particularly relevant to manufacturers developing new eCall platforms or planning software and hardware upgrades.

What Should Manufacturers Do?

When a new regulation or technical standard is introduced, manufacturers should take the following steps:

1. Check the applicable standards: Review the standards and versions referenced in the original approval documents and identify the new requirements.

2. Determine the transition period: Establish whether the new requirements apply immediately or are subject to a specified transitional arrangement.

3. Assess the approved configuration: Identify whether the existing hardware, software and communication architecture meet the updated requirements.

4. Determine whether additional testing is necessary: Where technical differences exist, identify the tests needed to demonstrate continued compliance.

5. Update the technical records: Keep the previous and updated standards, assessment reports, supplementary test results and communication with the approval authority on file.

The important point is that manufacturers should not assume that every existing circuit-switched eCall approval becomes invalid simply because IMS-based requirements have been introduced.

The applicable transition provisions and the approval status of the specific vehicle or system must be considered before deciding whether an update or additional approval work is necessary.

6. What Happens When a Vehicle Model Is Discontinued?

Discontinuing a vehicle model does not mean that all related approval and compliance responsibilities immediately disappear.

Conformity of production (COP) is an ongoing obligation throughout the production period. Manufacturers must ensure that vehicles coming off the production line continue to conform to the approved type.

Before production ends, manufacturers should complete a final review of the relevant technical configuration, including:

• The final hardware and software versions.

• The MSD configuration and related parameters.

• The approved supplier and component list.

• Production records and conformity documentation.

• The relationship between the final production vehicles and the original approval.

How Long Must Approval Documents Be Kept?

This is another area where manufacturers need to distinguish between different approval categories.

Under Regulation (EU) 2018/858, the general document retention requirements include:

• Whole-vehicle type approval: Manufacturers must retain the EU type-approval certificates and their attachments for 10 years after the approval becomes invalid.

• System, component and STU type approval: The corresponding retention period is generally five years after the approval becomes invalid.

• Certificates of conformity (CoCs): Vehicle manufacturers must keep copies available to approval authorities for 10 years from the date of manufacture.

These periods should not be confused with a fixed approval renewal cycle.

Even after production has ended, proper documentation management remains important. Authorities may need to review historical approval records, investigate compliance issues or verify the conformity of vehicles already placed on the market.

7. A Practical Approach to eCall Approval Management

For manufacturers and suppliers, managing eCall approval effectively is less about renewing a certificate and more about keeping the approved product compliant throughout its lifecycle.

A practical management approach can be summarized in four stages:

Stage 1 – After Initial Approval

Verify the approval certificate, technical documents and tested configuration. Establish a complete approval record.

Stage 2 – When Technical Changes Occur

Review hardware, software and supplier changes against the original approval. Determine whether a revision, extension or new approval is required.

Stage 3 – When Regulations Are Updated

Monitor changes to EU regulations and referenced technical standards. Check the applicable transition arrangements and assess whether additional testing is necessary.

Stage 4 – When Production Ends

Complete the final production conformity review, organize the approval records and retain the relevant documents for the legally required periods.

Ultimately, the most effective way to manage eCall approval is to treat it as part of the vehicle's ongoing compliance process rather than a one-time certification exercise.

How Can BlueAsia Support Your eCall Approval Project?

Navigating eCall type approval involves more than completing a series of laboratory tests. Manufacturers also need to understand the applicable regulatory framework, technical documentation requirements, approval procedures and the impact of future product changes.

BlueAsia provides professional automotive electronics testing and certification support, helping manufacturers understand approval requirements and manage their compliance projects.

Whether you are developing a new 112-based eCall system, preparing an STU for type approval, upgrading an existing product or reviewing the impact of new EU regulations, our team can help you identify the relevant requirements and plan the next steps.

For eCall type approval consultation and technical support, please contact us.

BlueAsia

Contact: Mandy
Mobile: +86 139 2344 9427
Email: [email protected]
Website: https://www.cblueasia.com/