ISO 17978-1

Road vehicles — Service-oriented vehicle diagnostics (SOVD) — Part 1: General information, definitions, rules and basic principles

This series of documents defines the use cases and their associated APIs for the SOVD and fall within the scope already defined by ISO 20077-1 "ExVe”. The methodology adopted for the implementation of an SOVD API is intended to follow the definitions in ISO 20077 (all parts) regarding “Extended Vehicle (ExVe)” (definitions, basic principles, rules, uses cases, API, etc...). It specifies the way to diagnose the vehicle via High Performance Computer (HPC) and Electronic Control Unit (ECU). The SOVD API provides, in the ExVe perimeter a unified access to ECUs and HPCs. This access can be performed remotely (e.g., backend or cloud), nearby in the repair shop (e.g., repair shop test equipment), or in the vehicle (e.g., on-board application). The SOVD API leverages existing technologies: • The API follows the Representational State Transfer (REST) principles and uses Javascript Object Notation (JSON) for encoding the transmitted data. • SOVD uses Hypertext Transfer Protocol (HTTP) 1.1 but for achieving the best communication performance HTTP/2 is recommended. No HTTP/2 specific features are used. • The SOVD API utilizes the OpenAPI specification to define the API as well as the diagnostic capabilities of the vehicle. • The authentication and authorization of clients builds upon OpenID Connect and Open Authentication (OAuth) 2.0, but a vehicle manufacturer may use other authentication mechanism like certificates if required. The SOVD API provides the following functions in the perimeter of the Extended Vehicle: • Clients can access the faults, including reading the fault entries, reading environment data, and deleting fault entries. • Measurements and identifications from all entities in the vehicle can be read. In addition, identifications may be written as well. • SOVD supports the execution of routines, I/O controls, and software functions. Their execution can only be performed in certain modes or states. Thus, an SOVD client can set the component into a specific mode. • The configuration of a vehicle (e.g., equipment, country, customer demand, variant coding etc.) can be read and written using the SOVD API. • SOVD provides an interface to initiate and monitor a software update for a vehicle • SOVD provides access to Extended Vehicle logging information With these features SOVD covers the entire chain of the vehicle life cycle: engineering (development), manufacturing (production), storage park, sales, vehicle operation (usage), maintenance and repair, technical inspection, recycling (re-use). This document provides general information, specifies common definitions applicable for SOVD and defines overall rules and basic principles.

Véhicules routiers — Diagnostic Véhicule Orienté Services (SOVD) — Partie 1: Informations générales, définitions, règles et principes de base

General Information

• Status: Not Published
• ICS: 01.040.43 - Road vehicle engineering (Vocabularies)
• ICS: 43.040.15 - Car informatics. On board computer systems
• Technical Committee: ISO/TC 22 - Road vehicles
• Drafting Committee: ISO/TC 22 - Road vehicles
• Current Stage: 6000 - International Standard under publication
• Start Date: 17-Apr-2026
• Completion Date: 25-Apr-2026

Overview

ISO 17978-1: Road vehicles - Service-oriented vehicle diagnostics (SOVD) - Part 1: General information, definitions, rules and basic principles establishes the foundational concepts for the SOVD standard, focusing on the digital transformation of vehicle diagnostics. This international standard, developed by the International Organization for Standardization (ISO), aligns with the extended vehicle (ExVe) methodology as defined by ISO 20077. It provides an overview of the SOVD framework, including key definitions, fundamental rules, and basic principles necessary for implementing unified vehicle diagnostics.

Service-oriented vehicle diagnostics (SOVD) addresses the evolving needs of modern vehicles, which increasingly rely on high performance computers (HPCs) and complex electronic control units (ECUs). The standard ensures consistent access to diagnostic data, supports multiple access modes (remote, in-vehicle, or repair-shop environments), and leverages secure, state-of-the-art information technologies for data exchange and authentication.

Key Topics

• Service-Oriented Architecture for Vehicle Diagnostics
  • Standardizes diagnostic communication for both HPCs and ECUs.
  • Facilitates unified access across diverse vehicle electrical and electronic (E/E) architectures.
• API and Communication Protocols
  • Specifies RESTful APIs using JSON for data encoding.
  • Utilizes HTTP 1.1, with recommendations to use HTTP/2 for optimal performance.
  • Defines APIs through the OpenAPI specification.
• Authentication and Security
  • Incorporates OpenID Connect and OAuth 2.0 for secure client authorization.
  • Allows manufacturers to implement certificate-based or alternative security mechanisms as needed.
• Core Diagnostic Functions
  • Unified access to vehicle faults, environment data, measurement, identification, routine execution, and I/O controls.
  • Supports reading and writing of vehicle configurations.
  • Enables software update initiation and monitoring.
  • Provides access to extended vehicle (ExVe) logging information.
• Rules and Principles
  • Mandates safety and security throughout the vehicle lifecycle.
  • Supports coexistence and interoperability with existing diagnostic protocols.
  • Addresses concurrent access and management by multiple diagnostic operators.

Applications

ISO 17978-1 is crucial for the following use cases within the automotive industry:

• Remote Diagnostics: Enables cloud-based and backend systems to perform diagnostics and maintenance, reducing physical intervention and shortening repair cycles.
• Repair and Maintenance: Facilitates comprehensive diagnostic access for repair shops using standardized APIs, streamlining troubleshooting and repair services.
• Lifecycle Management: Covers diagnostics throughout engineering, manufacturing, sales, operations, maintenance, inspection, and recycling.
• Fleet Management: Equips fleet operators and service providers with real-time, standardized access to a range of vehicle diagnostic data.
• Regulatory Compliance and Inspection: Provides clear interfaces for technical inspection authorities to access necessary vehicle data efficiently.

Related Standards

For a complete implementation and deeper understanding of the SOVD framework, reference these related standards:

• ISO 20077-1 & ISO 20077-2: Define the methodology and requirements for extended vehicle (ExVe) architecture.
• ISO 17978-2: Details SOVD use cases, especially for co-located diagnostics and repair scenarios.
• ISO 17978-3: Defines the application programming interface (API) specifications for SOVD.
• ISO 14229-1: Outlines the application layer for unified diagnostic services (UDS).
• OpenAPI Specification: Industry standard for defining RESTful APIs.

Practical Value

Implementing ISO 17978-1 ensures interoperability, security, and efficiency for all stakeholders involved in vehicle diagnostics, from manufacturers and service providers to fleet managers and regulatory agencies. By setting foundational definitions and principles, it lays the groundwork for scalable, future-proof vehicle diagnostic solutions aligned with the digitalization trends in the automotive sector. Adherence to ISO 17978-1 streamlines the integration of new diagnostic services, supports legal compliance, and enhances overall vehicle safety and lifecycle management.

Standards Content (Sample)

FINAL DRAFT
International
Standard
ISO/FDIS 17978-1
ISO/TC 22/SC 31
Road vehicles — Service-oriented
Secretariat: DIN
vehicle diagnostics (SOVD) —
Voting begins on:
2026-02-19
Part 1:
General information, definitions,
Voting terminates on:
2026-04-16
rules and basic principles
Véhicules routiers — Diagnostic Véhicule Orienté Services
(SOVD) —
Partie 1: Informations générales, définitions, règles et principes
de base
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/FDIS 17978-1:2026(en) © ISO 2026

FINAL DRAFT
ISO/FDIS 17978-1:2026(en)
International
Standard
ISO/FDIS 17978-1
ISO/TC 22/SC 31
Road vehicles — Service-oriented
Secretariat: DIN
vehicle diagnostics (SOVD) —
Voting begins on:
Part 1:
General information, definitions,
Voting terminates on:
rules and basic principles
Véhicules routiers — Diagnostic Véhicule Orienté Services
(SOVD) —
Partie 1: Informations générales, définitions, règles et principes
de base
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ISO/FDIS 17978-1:2026(en) © ISO 2026

ii
ISO/FDIS 17978-1:2026(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Overview of the ISO 17978 series . . 5
6 Conventions for identifying rules and basic principles and for specifying their content . 6
7 Rules and basic principles . 6
7.1 General .6
7.2 Rules .7
7.3 Basic principles .7
7.3.1 Basic principle 001 (BP_001) .7
7.3.2 Basic principle 002 (BP_002) .8
7.3.3 Basic principle 003 (BP_003) .8
7.3.4 Basic principle 004 (BP_004) .9
7.3.5 Basic principle 005 (BP_005) .10
7.3.6 Basic principle 006 (BP_006) .10
Bibliography .13

iii
ISO/FDIS 17978-1:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by ISO/TC 22 Road vehicles, Subcommittee SC 31, Data communication.
A list of all parts in the ISO 17978 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
ISO/FDIS 17978-1:2026(en)
Introduction
The introduction of high performance computers (HPCs) in vehicles is associated with changes in the classical
electronic and electrical vehicle architectures. Besides classical distributed embedded electronic control
unit (ECU) architectures, domain- or zone-based architectures are also available. These architectures also
extend beyond the physical vehicle.
This extends the focus from checking hardware to also checking the functionality of applications. It requires
the recording of data such as memory usage, processor load, and the number of active services, as well as the
collection of log and trace files.
These topics result in challenges regarding the management of the vehicle life cycle. Some aspects to be
considered are:
— faster release and update cycles;
— increased requirements such as data protection and cybersecurity;
— state-of-the-art diagnostic API using current information technologies.
The ISO 17978 series define an API which standardizes the methods for:
— discovering the SOVD capabilities;
— performing diagnostics;
— (re-)configuring and re-programming;
— allowing the introduction of new functionalities.
Figure 1 shows the OSI layers of the ISO17978 series.

v
ISO/FDIS 17978-1:2026(en)
a
Communication protocol.
b
Network technology depending on E/E vehicle network architecture.
Figure 1 — OSI layers of SOVD
vi
FINAL DRAFT International Standard ISO/FDIS 17978-1:2026(en)
Road vehicles — Service-oriented vehicle diagnostics
(SOVD) —
Part 1:
General information, definitions, rules and basic principles
1 Scope
This document
— gives an overview of the ISO 17978 series;
— specifies rules and basic principles for the service-oriented vehicle diagnostics (SOVD), conforming to
the extended vehicle (ExVe) methodology, as specified in the ISO 20077 series;
— defines general terms.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 20077-2:2018, Road Vehicles — Extended vehicle (ExVe) methodology — Part 2: Methodology for designing
the extended vehicle
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
basic principle
design principle that is considered when designing an extended vehicle (3.8)
[SOURCE: ISO 20077-2:2018, 3.1]
3.2
capability
ability of a system, component or function to execute a defined task or provide a specific service
Note 1 to entry: Capabilities refer to concrete actions or functions that can be performed, such as executing a diagnostic
routine, retrieving sensor data, modifying configuration parameters or accessing logs.

ISO/FDIS 17978-1:2026(en)
3.3
classic diagnostic adapter
software that translates between the service-oriented vehicle diagnostics (SOVD) and another diagnostic
protocol
Note 1 to entry: The other diagnostic protocol may be a protocol that is not intended for diagnostic, Figure 2 CDA-
enabling communication between SOVD and two other diagnostic protocols.
Figure 2 — OSI layers of the SOVD
3.4
co-located
located in the same place as the vehicle
EXAMPLE Co-located diagnostics (3.6), co-located access.
Note 1 to entry: Figure 3 illustrates a co-located diagnostics operator (3.5) in relation to an extended vehicle (3.8).
Key
responsible operator
Figure 3 — Co-located diagnostics operator using different network technologies and ExVe
interfaces
Note 2 to entry: The colours used in this figure refer to the ones in ISO 20077-1.
3.5
diagnostics operator
natural person that performs a diagnostic procedure
Note 1 to entry: A diagnostics operator can work at any service provider.

ISO/FDIS 17978-1:2026(en)
Note 2 to entry: In the ISO 17978 series, a co-located (3.4) diagnostics operator is responsible for the diagnostic
process.
3.6
diagnostics
diagnostic process
process including the detection process of possible vehicle malfunctions, the identification of the likely root
cause of these malfunctions and the appraisal of its relevance for the operation of the vehicle
[SOURCE: ISO 20077-1:2017, 3.2]
3.7
electronic control unit
embedded computing device used for vehicle control functions
3.8
extended vehicle
entity, still in accordance with the specifications of the vehicle manufacturer, that extends beyond the
physical boundaries of the road vehicle and consists of the road vehicle, off-board systems, external
interfaces and the data communication between the road-vehicle
...

ISO/FDIS 17978-1
ISO/TC 22/SC 31
Secretariat: DIN
Date: 2026-02-04
Road vehicles — Service-oriented vehicle diagnostics (SOVD) —
Part 1:
General information, definitions, rules and basic principles
Véhicules routiers — Diagnostic Véhicule Orienté Services (SOVD) —
Partie 1: Informations générales, définitions, règles et principes de base
FDIS stage
ISO/FDIS 17978-1:2026(en)
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO
at the address below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
E-mail: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
ISO/FDIS 17978-1:2026(en)
Contents
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Overview of the ISO 17978 series . 5
6 Conventions for identifying rules and basic principles and for specifying their content . 6
7 Rules and basic principles . 7
7.1 General . 7
7.2 Rules . 7
7.3 Basic principles . 8
Bibliography . 15

iii
ISO/FDIS 17978-1:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
ISO documentdocuments should be noted. This document was drafted in accordance with the editorial rules
of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights
in respect thereof. As of the date of publication of this document, ISO had not received notice of (a) patent(s)
which may be required to implement this document. However, implementers are cautioned that this may not
represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by ISO/TC 22 Road vehicles, Subcommittee SC 31, Data communication.
A list of all parts in the ISO 17978 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
ISO/FDIS 17978-1:2026(en)
Introduction
The introduction of high performance computers (HPCs) in vehicles is associated with changes in the classical
electronic and electrical vehicle architectures. Besides classical distributed embedded ECUelectronic control
unit (ECU) architectures, domain- or zone-based architectures are also available. These architectures also
extend beyond the physical vehicle.
This extends the focus from checking hardware to also checking the functionality of applications. It requires
the recording of data such as memory usage, processor load, and the number of active services, as well as the
collection of log and trace files.
These topics result in challenges regarding the management of the vehicle life cycle. Some aspects to be
considered are:
— faster release and update cycles;
— increased requirements such as data protection and cybersecurity;
— state-of-the-art diagnostic API using current information technologies.
The ISO 17978 series define an API which standardizes the methods for:
— discovering the SOVD capabilities;
— performing diagnostics;
— (re-)configuring and re-programming;
— allowing the introduction of new functionalities.
Figure 1 shows the OSI layers of the ISO17978 series.

Key
v
ISO/FDIS 17978-1:2026(en)
a
communicationCommunication protocol.
b
networkNetwork technology depending on E/E vehicle network architecture.
Figure 1 — OSI layers of SOVD
vi
DRAFT International Standard ISO/FDIS 17978-1:2025(en)

Road vehicles — Service-oriented vehicle diagnostics (SOVD) — —
Part 1:
General information, definitions, rules and basic principles
1 Scope
This document
— — gives an overview of the ISO 17978 series;
— — specifies rules and basic principles for the service-oriented vehicle diagnostics (SOVD), conforming to
the extended vehicle (ExVe) methodology, as specified in the ISO 20077 series;
— — defines general terms.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO 20077-2:2018, Road vehicles –Vehicles — Extended vehicle (ExVe) methodology –— Part 2: Methodology for
designing the extended vehicle
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at https://www.electropedia.org/
3.1
basic principle
design principle that is considered when designing an extended vehicle (3.8)
[SOURCE: ISO 20077-2:2018, 3.1]
3.2
capability
capacityability of a system, component or function to execute a defined task or provide a specific service
Note 1 to entry: Capabilities refer to concrete actions or functions that can be performed, such as executing a diagnostic
routine, retrieving sensor data, modifying configuration parameters or accessing logs.
3.3 3.3
classic diagnostic adapter
software that translates between the service-oriented vehicle diagnostics (SOVD) and another diagnostic
protocol
ISO/FDIS 17978-1:2026(en)
Note 1 to entry: The other diagnostic protocol may be a protocol that is not intended for diagnostic, Figure 2 CDA-
enabling communication between SOVD and 2two other diagnostic protocols.

Figure 2 — OSI layers of the SOVD
3.4
co-located
located in the same place as the vehicle
EXAMPLE Co-located diagnostics (3.6), co-located access.
Note 1 to entry: Figure 3 illustrates a co-located diagnostics operator (3.5) in relation to an extended vehicle (3.8).

Key:
responsible operator
ISO/FDIS 17978-1:2026(en)
Figure 3 — Co-located diagnostics operator using different network technologies &and ExVe
interfaces
Note: 2 to entry: The colours used in this figure refer to the ones in ISO 20077-1.
3.5
diagnostics operator
natural person that performs a diagnostic procedure
Note 1 to entry: A diagnostics operator can work at any service provider.
Note 2 to entry: In the ISO 17978 series, a co-located (3.4) diagnostics operator (3.4) is responsible for the diagnostic
process.
3.6
diagnostics
diagnostic process
process including the detection process of possible vehicle malfunctions, the identification of the likely root
cause of these malfunctions and the appraisal of its relevance for the operation of the vehicle
[SOURCE: ISO 20077-1:2017, 3.2]
3.7
electronic control unit
embedded computing device used for vehicle control functions
3.8
extended vehicle
entity, still in accordance with the specifications of the vehicle manufacturer, that extends beyond the physical
boundaries of the road vehicle and consists of the road vehicle, off-board systems, external interfaces, and the
data communication between the road-vehicle and the off-board systems
Note 1 to entry: Road vehicles without off-board systems and road vehicles equipped with telematics units are extended
vehicles.
[SOURCE: ISO 20077-1:2017, 3.5]
3.9
ExVe manufacturer
vehicle manufacturer responsible for the extended vehicle 8)(3.8)
3.10
High performance computer
device owning high capacity of computing within the vehicle
Note 1 to entry: A high performance computer used in the ISO 17978 series, typically hosts multiple virtualized guest
systems.
3.103.11
remote, adj
performed on a vehicle from a distance where the operator responsible for the concerned operation is not co-
located (3.4)(3.4) to the vehicle and where the vehicle is connected via an external network
ISO/FDIS 17978-1:2026(en)
EXAMPLE Remote diagnostics (3.6), remote access.
Note 1 to entry: The “operator responsible for the concerned operation” is a specific actor in terms of use case (3.14).
[SOURCE: ISO 20077--1:2017, 3.14]
3.113.12
resource
data or functionality of the vehicle
3.123.13
rule
fundamental design requirement that is complied with when designing an extended vehicle (3.8)
[SOURCE: ISO 20077-2:2018, 3.6]
3.133.14
use case
sequence of interactions between one or several actors and the concerned system, which has a defined goal
and provides a measurable result
EXAMPLE Read all active DTCs.
Note 1 to entry: “Read all active DTCs” may be comprisedcomposed of the following interactions: initialization of the
communication, identification of the vehicle, sending the request to get DTC information (“read DTC”), receiving DTC
information, terminating of the communication.
Note 2 to entry: Actors may be both human and machines.
Note 3 to entry: In the case of an extended vehicle (3.8), the concerned system is the extended vehicle itself.
Note 4 to entry: In order to be able to perform the design of an extended vehicle, it is necessary that the use cases are
completed by the appropriate use case scenarios
...