Contents

Over-the-air updates and UN R156 (SUMS)

How vehicles are updated remotely — campaign management, secure packages, installation and rollback — and what the UN R156 software update regulation requires.

Why it exists

Software defines more and more of the vehicle. OTA updates fix bugs and security issues without a workshop visit — in 2026 several large recalls were remedied mostly over the air — and enable new features after sale.

What R156 requires

  • A Software Update Management System (SUMS) at the manufacturer, assessed by an approval authority.
  • Traceable software identification (RXSWIN) for type-approval-relevant software.
  • For OTA: the vehicle must be in a safe state, have enough energy, inform the user, and be able to recover from failed updates.

How an update works

The backend builds a signed campaign for the vehicles that need it → the TCU downloads it → the update master on the HPC verifies and distributes it → each ECU installs (often into an inactive A/B bank) → activation at a safe moment → verification and reporting; rollback on failure.

OTA update sequence
Signed campaignBackend targets vehicles needing the update
DownloadTCU receives the update package
Verify and distributeUpdate master on HPC checks the package
InstallECUs often use an inactive A/B bank
ActivateAt a safe moment
Verify and reportRoll back on failure

This simplified sequence shows the update path from the backend to ECU activation and recovery.

Best practices

  • Use A/B partitions or equivalent recovery for every updatable ECU.
  • Verify compatibility of the complete software set, not single ECUs.
  • Stage roll-outs and monitor before expanding.

Common pitfalls

  • ECUs that cannot be updated remotely, forcing workshop visits for the whole fleet.

What it means for your discipline

  • Software update & OTA Core

    Owns the update process end to end: SUMS, campaigns, RXSWIN, compatibility, installation, verification and recovery.

  • Cybersecurity Core

    Signed packages, secure transport and protection of the update backend are essential — updates are a powerful attack vector.

  • HPC & application software Core

    Update clients, A/B partitions and orchestration across ECUs run on the HPC.

  • Diagnostics & lifecycle Partial

    Provides version read-out, update-related DTCs and the tester path used for recovery and workshop updates.

  • E/E architecture Partial

    Memory sizing, update paths to every ECU and energy during installation must be designed in.

  • Functional safety Partial

    Updates change safety-relevant software; the safety case must be maintained and installation must happen in a safe state.

No direct stake: Base 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 — Verifies and distributes packages, checks installation conditions, coordinates activation, and reports the resulting software configuration.
  • Security services — Authenticates update packages and protects authorization for update operations.
  • Diagnostics — Exposes software identification and update failures for traceability and service recovery.
  • Secure boot chain · TEE — Enforces boot-time image verification and supports recovery when an updated system image fails to start.
MCU-based ECU · AUTOSAR Classic
  • Flash bootloader · secure boot — Verifies and installs authorized images and provides a recovery path after interrupted or failed programming.
  • Diagnostics — Provides software version readout, update-related fault reporting and the diagnostic path for workshop recovery.
  • Application layer — Reports whether vehicle functions permit activation and confirms required behavior after the update starts.