Contents
RegulationUNECE

UN R156

Uniform provisions concerning the approval of vehicles with regard to software update and software updates management system

UN R156 requires vehicle manufacturers to manage software updates through controlled processes and demonstrate that vehicles can receive updates safely and securely.

What it is

UN R156 is a vehicle type-approval regulation covering software updates and the manufacturer’s Software Update Management System (SUMS). Type approval means demonstrating to an approval authority that a vehicle type meets applicable regulatory requirements.

A SUMS combines organizational responsibilities, procedures and records for controlling updates. Approval therefore involves both the manufacturer’s management system and the vehicle’s update capabilities. Installing an OTA client alone does not establish compliance.

The regulation covers wired updates, including workshop reprogramming, as well as over-the-air (OTA) updates. Its text is publicly available.

Who it applies to

The vehicle manufacturer holds responsibility for demonstrating compliance where UN R156 applies under the relevant market’s approval rules. Suppliers contribute software, components, services and evidence needed by that manufacturer.

Its stated scope includes update-capable vehicles in categories M, N, O, R, S and T: passenger vehicles, goods vehicles, trailers and specified agricultural vehicles and machinery. Market legislation determines which categories and approvals actually require it; the scope alone does not establish a universal obligation everywhere.

Engineers should identify the amendment series applicable to their vehicle approval. Requirements and transitional provisions must be checked against that approval context.

What it covers

The regulation connects release management with vehicle approval and update execution. Key concerns include:

Concern What engineers need to establish
Software identification Which software versions and relevant hardware belong to a vehicle configuration
Update assessment Whether a change affects approved characteristics or requires approval action
Compatibility Whether the update suits the target vehicle and its dependencies
Protection How update authenticity and integrity are protected
Execution How installation conditions, failures and recovery are handled
Records How update decisions and results can be demonstrated

RXSWIN means RX Software Identification Number. It connects software relevant to a particular UN Regulation’s type approval with an identifier defined by the manufacturer. It should be understood alongside the applicable amendment series, rather than treated as a generic version number for every application.

OTA updates carry additional requirements concerning matters such as available power, safe execution, user information and recovery or a safe state following failure. The regulation does not prescribe an A/B storage layout, a particular package format or a specific update protocol.

How it fits with other documents

UN R155 addresses vehicle cybersecurity and the Cyber Security Management System (CSMS). Its processes overlap with SUMS activities where update threats, vulnerabilities and security controls are involved, while each regulation has its own approval purpose.

ISO 24089 provides an engineering framework for software updates that can help organize implementation and evidence. Applying it does not automatically establish UN R156 compliance.

ISO 26262 safety activities help assess changes affecting safety-related functions. Uptane can support update security mechanisms. These documents and technologies contribute to the implementation; approval still depends on meeting the applicable regulatory requirements.

In practice

For a gateway update, establish the target vehicle configurations, dependent ECU versions and affected approvals before releasing the package. Record the impact assessment, verification results and release authorization.

Demonstrate that the vehicle accepts the intended package, checks installation conditions and responds appropriately to interruption or failure. Define how users receive relevant information and how service teams handle unsuccessful installations.

Maintain traceability from the released software and applicable RXSWIN records to vehicle configurations and campaign outcomes. An approval reviewer needs a coherent evidence trail across engineering, release operations and the manufacturer’s SUMS.

What it means for your discipline

  • Software update & OTACore

    Own the update lifecycle, campaign controls and SUMS evidence. Show how each release reaches compatible vehicles and how installation outcomes are handled.

  • HPC & application softwareCore

    Maintain software identification, dependency records and release verification. Assess whether software or configuration changes affect approved vehicle characteristics.

  • CybersecurityCore

    Define and verify protection against unauthorized updates and compromised update processes. Coordinate update security evidence with the manufacturer's CSMS.

  • E/E architecturePartial

    Design update boundaries and dependencies across ECUs and central computers. Ensure the vehicle architecture supports coordinated installation and recovery.

  • Functional safetyPartial

    Assess how updates affect safe vehicle operation and existing safety evidence. Help define installation conditions and acceptable behavior after failure.

  • Base softwarePartial

    Implement bootloader, programming and platform mechanisms that support controlled updates. Provide evidence for integrity checks, software identification and recovery behavior.

  • Diagnostics & lifecyclePartial

    Support workshop reprogramming and access to relevant software identifiers. Keep diagnostic programming workflows consistent with approved update processes.

  • Hardware & siliconPartial

    Provide storage and power capabilities needed for reliable installation and recovery. Check that hardware variants remain compatible with intended software releases.

  • Networks & communicationPartial

    Support dependable update transfer and coordination between vehicle controllers. Account for communication interruptions and network dependencies during programming.