Contents

SOVD — Service-Oriented Vehicle Diagnostics

A modern REST/HTTP diagnostic API for HPC-centric vehicles — usable from workshop, cloud and in-vehicle apps — standardised as ISO 17978 in 2026.

Why it exists

An HPC runs dozens of processes and VMs, not one firmware image. Byte-oriented UDS cannot describe that well, and remote diagnostics from the cloud needs modern web APIs.

What it is

A REST API with JSON: diagnostic entities (components, apps) offer faults, data, configurations, operations and logs as resources. Discovery tells a client what each entity supports.

How it coexists with UDS

UDS remains on classic ECUs for years. An SOVD server on the HPC includes a classic diagnostic adapter that translates SOVD requests to UDS for legacy ECUs.

SOVD access to classic ECUs
Diagnostic client
SOVD serverRuns on the HPC
Classic diagnostic adapterTranslates requests within the server
Classic ECU

The adapter translates requests for classic ECUs, while HPC software diagnostics are exposed directly through SOVD.

Best practices

  • Start by exposing HPC software diagnostics via SOVD, keep UDS for ECUs.
  • Design access control and auditing from the beginning.

Common pitfalls

  • Treating SOVD as “UDS over HTTP” instead of modelling diagnostic content anew.

What it means for your discipline

  • Diagnostics & lifecycle Core

    SOVD changes how diagnostic content is modelled and accessed — logs, configuration and software state, not just DTCs.

  • HPC & application software Core

    SOVD servers run on HPCs as services and expose diagnostics of processes, containers and VMs.

  • Cybersecurity Partial

    HTTP APIs need strong authentication, authorisation and TLS.

  • Base software Partial

    Classic ECUs stay on UDS; a classic diagnostic adapter translates SOVD to UDS.

  • Software update & OTA Partial

    Uses exposed software inventory, operations and logs to check update prerequisites and diagnose failed installations on HPCs; coordinates access through classic diagnostic adapters for legacy ECUs.

No direct stake: E/E architecture · Functional safety · 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)
  • Diagnostics — Exposes faults, logs, configuration and operations through SOVD resources and translates requests to UDS for classic ECUs.
  • Security services — Provides authentication, authorisation and TLS support to protect access to SOVD diagnostic resources.
MCU-based ECU · AUTOSAR Classic
  • Diagnostics — Handles UDS requests translated by the HPC's classic diagnostic adapter and supplies diagnostic data and operations.