Over-the-air updates, SUMS, software bills of materials and continuous delivery for vehicles in the field — and why recalls are increasingly fixed by software.
Over-the-air (OTA) updates are the practical heart of the SDV: they let a vehicle improve — and be fixed — after sale. UN R156 requires a Software Update Management System (SUMS) and traceable software identification (the RXSWIN) for type-approval-relevant software. It covers wired and wireless updates alike and adds conditions for OTA: safe vehicle state, sufficient energy, user information and recovery from failed updates. ISO 24089 describes the engineering processes behind it.
Technical patterns
A/B (dual-bank) partitions — install in the background, switch on reboot, roll back on failure.
Delta updates — transmit only the differences to save bandwidth and time.
Campaign management — targeting by VIN and configuration, staged roll-out, monitoring and pausing.
Signed and verified packages — Uptane is the reference security framework, designed to survive a compromised backend server.
Software bills of materials (SBOMs) — track every component and its vulnerabilities across the fleet.
State of play (late 2026)
Recalls are increasingly software. In 2026 several large US recalls (rear-view camera software, for example) were remedied fully or partly over the air; trackers count dozens of software recall campaigns per quarter.
Volume keeps rising. Analysts forecast SDV OTA update volumes to grow roughly fourfold by 2035.
Regulators are refining R156, with 2026 proposals to clarify SUMS requirements.
Fleet angle
For commercial fleets, uptime is money. Update windows must fit operations, fleet operators need control over when updates are applied, and mixed fleets bring many software baselines at once.
Why it matters: It shows how a wheel-slip estimation edge case involving several combined conditions slipped past an earlier fix in a supplier-built brake ECU, and how OTA delivery can serve as the primary remedy path for a safety-critical brake software recall.
Why it matters: If US recall rules adapt to OTA remedies, recall completion becomes a software-delivery KPI — and update reliability a compliance topic.
Why it matters: Four times more OTA updates means SUMS processes, campaign tooling and update security have to scale with the fleet — not just the first launch.
Why it matters: A textbook SDV recall: the remedy was software, and over 95% of affected vehicles were updated before the recall letters were even mailed.
Why it matters: Great Britain joins the EU in requiring cybersecurity and software-update management for type approval — one more market where a CSMS and SUMS are entry tickets.