Contents
StandardISO

ISO 17978 (SOVD)

Road vehicles — Service-oriented vehicle diagnostics (SOVD)

ISO 17978 defines a common diagnostic interface that lets tools inspect and service vehicle computers, their software applications, and traditional electronic control units.

What it is

ISO 17978 is the service-oriented vehicle diagnostics (SOVD) series. It provides a common interface for diagnostic access to high-performance computers (HPCs), their software, and legacy electronic control units (ECUs). Its REST/HTTP approach brings familiar web-service techniques into vehicle diagnostics.

The useful mental model is a diagnostic service that a tool can explore: discover available capabilities, inspect information, and request supported actions. This suits vehicles whose diagnostic content changes as applications are installed or updated. The ISO API standard explicitly covers unified access to HPCs and classic ECUs. Source: ISO’s Part 3 overview.

Who it applies to

The series matters to vehicle manufacturers, platform suppliers, diagnostic software developers, and service-tool providers implementing SOVD. Diagnostic engineers define what information and actions the vehicle exposes; software engineers implement the interface and connect it to the underlying systems.

Architecture, cybersecurity, network, safety, and update teams contribute integration constraints. For example, exposing a routine requires decisions about access rights, communication paths, and the vehicle conditions under which execution is acceptable.

ISO 17978 is a technical standard. Whether a particular project must implement it depends on its contracts, platform requirements, and applicable obligations; publication alone does not make SOVD mandatory for every vehicle.

What it covers

The published parts divide the subject into principles, use cases, and the interface itself:

Part Purpose Typical reader
Part 1 General information, terminology, rules, and principles Architects and technical leads
Part 2 Diagnostic use cases Requirements and diagnostic engineers
Part 3 Application programming interface Implementers and integration testers

The diagnostic scope includes discovering capabilities, accessing fault information, reading measurements and identification data, executing supported operations, and managing configuration. SOVD also addresses software-oriented needs such as logging and bulk-data handling. The ASAM foundation uses HTTP/REST and JSON, with mechanisms for discovering available diagnostic content. Source: ASAM SOVD overview.

Discovery helps a client understand what a particular vehicle exposes. It does not eliminate the need to define meaningful data, stable behavior, or permissions.

How it fits with other documents

ISO 17978 is based on ASAM SOVD. Projects should identify the exact ISO parts and ASAM release they target and assess differences before claiming compatibility.

SOVD can coexist with Unified Diagnostic Services (UDS), standardized in ISO 14229. A vehicle implementation can provide SOVD access while retaining UDS communication with legacy ECUs. Translating between those interfaces requires deliberate handling of diagnostic meaning and errors.

Part 1 also places SOVD within the extended vehicle methodology of ISO 20077. Platform specifications such as AUTOSAR address implementation concerns alongside the diagnostic interface. Cybersecurity, functional safety, and software-update requirements still need their own engineering evidence.

In practice

Start with a diagnostic capability inventory: which applications and ECUs must be visible, what information they expose, and which operations clients may request. Assign an owner to each capability and document any translation to legacy diagnostics.

Then verify complete workflows: discover a capability, obtain access, read its data, execute an allowed operation, and handle failure. Include unavailable applications, interrupted communication, denied access, and changing software content. Successful HTTP communication is only one check; the diagnostic result must also remain correct and understandable.

What it means for your discipline

  • Diagnostics & lifecycleCore

    Own the diagnostic capabilities exposed through SOVD and verify that clients and servers behave consistently. Map existing ECU diagnostics into the service interface while preserving their meaning.

  • HPC & application softwareCore

    Implement SOVD servers, clients, and application integrations. Handle resource discovery, diagnostic data, operation execution, and application lifecycle changes.

  • E/E architecturePartial

    Decide where diagnostic services run and how clients reach HPC applications and legacy ECUs. Define responsibilities across vehicle computers, gateways, and external systems.

  • CybersecurityPartial

    Define who may read diagnostic information or trigger changes, and integrate authentication and authorization. Review privileged operations and diagnostic exposure across trust boundaries.

  • Base softwarePartial

    Connect platform diagnostic services and existing ECU diagnostic stacks to SOVD implementations. Preserve underlying diagnostic behavior when requests cross an adapter or gateway.

  • Networks & communicationPartial

    Provide reliable IP connectivity and appropriate routing for diagnostic traffic. Account for large transfers and competing vehicle traffic when integrating the service.

  • Software update & OTAPartial

    Understand how diagnostic operations support software servicing and update workflows. Coordinate their use with the vehicle's update orchestration and recovery mechanisms.

  • Functional safetyPartial

    Assess diagnostic operations that can change vehicle behavior. Ensure the implementation enforces appropriate operating conditions before allowing consequential actions.

No direct stake: Hardware & silicon