Contents

Software update rules around the world

How major vehicle markets regulate software updates, and what engineering teams must prove before and after a release.

5 min read · Discipline stake: Update Security Safety Diagnostics

Why it exists

A software update can change braking behaviour, emissions control or the information shown to a driver. It can also fail during installation and leave a vehicle unable to operate. Delivering the correct file is only part of the job.

Regulators therefore ask manufacturers to control changes throughout a vehicle’s life. Engineers need to know which vehicles an update fits, what it changes, whether the vehicle remains compliant and how installation success is confirmed.

Over-the-air (OTA) describes delivery through a wireless connection. It does not decide whether a change needs approval or recall handling. A workshop update can face the same regulatory questions.

What it is

Vehicle update regulation is a collection of market rules. Some markets require approval of the manufacturer’s processes and vehicle design. Others place responsibility on the manufacturer and enforce compliance through investigations and recalls.

UN Regulation No. 156 (R156) belongs to the United Nations Economic Commission for Europe (UNECE) framework under the 1958 Agreement. It was adopted in 2020. Contracting parties applying the regulation include Japan and the Republic of Korea, as recorded in the United Nations Treaty Collection entry for R156. Membership of the agreement alone does not establish every country’s domestic implementation timetable.

The European Union (EU) applies R156 through its vehicle type-approval framework. Type approval means an authority accepts a vehicle type against specified requirements before market entry. The EU introduced mandatory update requirements for new vehicle types, then extended them to newly supplied vehicles, including vehicles built under existing approvals.

The transition has qualifications. Article 2 of Commission Delegated Regulation (EU) 2022/2236 distinguishes vehicles receiving updates affecting approved characteristics, broader new-type requirements, and complete versus completed vehicles. A completed vehicle passes through multiple manufacturing stages. Check the current text for the applicable category and deadline; a single “all new vehicles” date hides these distinctions. See the EU regulation’s transitional provisions.

China uses GB 44496-2024, a mandatory national standard titled General technical requirements for software update of vehicles. The official national standards catalogue gives its implementation date as 1 January 2026. Check the current text, amendments and implementation rules for a particular product. See the official Chinese standard record.

The United States (US) has no equivalent federal update type-approval regime. Manufacturers self-certify compliance with applicable Federal Motor Vehicle Safety Standards. The National Highway Traffic Safety Administration (NHTSA) oversees compliance and recalls, as explained in its manufacturer handbook.

How it works

The comparison below separates legal approval from engineering assurance. The responsible organization depends on the market and assessment route.

Framework Scope What is certified or approved? Who audits or checks?
R156 in applying markets, including the EU Update management and vehicle update capabilities within the applicable scope Manufacturer’s Software Update Management System (SUMS) receives a compliance certificate; the vehicle type receives approval Approval authority, with assessment or testing by its technical service
China: GB 44496-2024 Vehicle software update requirements within the national standard’s scope Compliance supports the applicable Chinese vehicle access or certification route; it is not an R156 approval Relevant Chinese authorities and testing or certification bodies under that route
US federal framework Vehicle safety compliance, safety defects and recalls Manufacturer self-certification; no NHTSA approval of each update Manufacturer performs compliance checks; NHTSA investigates and oversees recalls
ISO 24089 Organizational and project engineering of updates No statutory vehicle approval from the standard itself Internal, customer or independent assessors, according to the chosen arrangement

Under R156, the manufacturer needs both repeatable processes and evidence that the vehicle supports compliant updates. A SUMS certificate does not replace vehicle type approval. Nor does it mean an authority approves every software package individually. The manufacturer must assess changes and involve the authority where approval action is required. These responsibilities are described in the public R156 text.

In practice, prepare a release record that answers:

  • What changes? Record affected functions, software versions and approved characteristics.
  • Which vehicles qualify? Match hardware, installed software, configuration and market.
  • Can installation finish safely? Define vehicle conditions, interruption handling and recovery.
  • What must happen before release? Resolve approval, notification and recall questions with the responsible specialists.
  • What happened afterwards? Retain installation results, failures and corrective actions.

For a US safety recall, remote delivery does not remove the obligations to file the recall, notify owners and provide an effective remedy. NHTSA explicitly says it oversees OTA recalls as it does physical repairs. Downloading a package also does not prove that the remedy was installed successfully. See NHTSA’s Recalls Next public meeting remarks.

ISO 24089 supplies the engineering foundation: responsibilities, configuration information, update packages and campaign preparation and execution. It covers organizational and project activities across vehicles and infrastructure. Its public abstract describes that scope; following it does not automatically establish legal compliance in every market. See the ISO 24089 catalogue entry.

When to use it — and when not

Use this overview when planning a vehicle programme, adding a sales market or preparing an update campaign. Start the applicability review while designing the update system. Requirements for identification, recovery and evidence can affect both the vehicle and its backend.

Revisit the review when a release changes regulated behaviour, introduces a feature or remedies a possible safety defect. A shared software package may need different release decisions in different markets.

Do not use this overview as a final approval checklist. The controlling material is the current regulation, its amendments, national implementation and the vehicle’s approval record. An existing fleet also needs separate consideration: a rule for newly supplied vehicles does not automatically require every older vehicle to be retrofitted.

Best practices

  • Maintain a market matrix with vehicle categories, applicable documents, amendment versions and named owners. Record why each requirement applies.
  • Build a shared engineering evidence set, then add market-specific decisions and submissions.
  • Link each release to its compatibility checks, safety and cybersecurity assessments, approval review and installation results.
  • Agree supplier evidence and escalation responsibilities before campaign preparation starts.
  • Keep workshop and OTA records consistent so that both routes produce a trustworthy installed configuration.
  • Have regulatory and recall specialists review uncertain cases before release. Record the decision and supporting evidence.

Common pitfalls

  • Treating R156 as worldwide law. Its application depends on the market and relevant implementation.
  • Using one EU deadline for every vehicle. Transitional provisions distinguish approval stages and vehicle situations; check the current text.
  • Assuming Chinese compliance follows from R156 approval. Similar objectives do not make the approval routes interchangeable.
  • Calling a safety remedy a routine update. The release label does not determine US recall obligations.
  • Treating ISO 24089 assessment as market authorization. Engineering evidence supports compliance but does not replace required legal decisions.
  • Closing a campaign when delivery finishes. Installation, activation and remedy effectiveness need their own evidence.

What it means for your discipline

  • Software update & OTA Core

    Maintains the market applicability matrix, release evidence and campaign records; checks whether each update needs approval action or recall handling.

  • Cybersecurity Partial

    Provides evidence for package authenticity, protected delivery and vulnerability fixes; checks that urgent security releases follow the required update process.

  • Functional safety Partial

    Assesses changed vehicle behaviour and installation hazards; supplies safety evidence and helps determine whether a defect needs recall handling.

  • Diagnostics & lifecycle Partial

    Makes installed software versions readable and keeps workshop recovery procedures aligned with remote campaigns.

No direct stake: E/E architecture · Base software · HPC & application software · Hardware & silicon · Networks & communication

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • OTA client · UCM — Implements installation conditions, recovery handling and outcome reporting needed to demonstrate compliant vehicle updates.
  • Diagnostics — Makes installed software identifiers readable for configuration checks and regulatory traceability.
  • Security services — Enforces update authorization and verifies package authenticity and integrity as required by the applicable update framework.
MCU-based ECU · AUTOSAR Classic
  • Flash bootloader · secure boot — Provides authenticated programming and defined interruption recovery to support vehicle update compliance.
  • Diagnostics — Exposes installed software identifiers and programming results for release evidence and workshop recovery.