Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
Introduction: The ISO 14229 series has been established in order to define common requirements for diagnostic systems, whatever the serial data link is. To achieve this, the ISO 14229 series is based on the Open Systems Interconnection (OSI) Basic Reference Model in accordance with ISO/IEC 7498-1 [1] and ISO/IEC 10731 [2], which structures communication systems into seven layers in accordance with Figure 1. Figure 1 — UDS-based vehicle diagnostic communication framework according to OSI model When mapped on the OSI model, the services used by a diagnostic tester (client) and an Electronic Control Unit (ECU, server) are broken into the following layers: — Application layer (layer 7): unified diagnostic services specified in this document, ISO 14229-3 [3] UDSonCAN to ISO 14229-X UDSon... , ISO 20730-1 [4] ePTI, ISO 26021-1 [5] EOLAIVPD, ISO 27145-3 [6] WWH-OBD, ISO/SAE AWI 1979-3 [7] ZEonUDS, and further standards; — Presentation layer (layer 6): vehicle manufacturer specific, SAE J1979-DA [8], SAE J2012-DA [9], SAE J1939- DA [10], SAE J1930-DA [11], ISO 22901 [12] ODX, ISO 20730-3 [13] ePTI, and ISO 26021-3 [14] EOLAIVPD; — Session layer services (layer 5): specified in ISO 14229-2. © ISO 2026 – All rights reserved
Scope: This document specifies data link independent requirements of diagnostic communication services. These allow a diagnostic tester (client) to control diagnostic functions in an in-vehicle electronic control unit (ECU, server) such as an electronic fuel injection, automatic gearbox, anti-lock braking system, etc. connected to a serial data link embedded in a road vehicle. This document specifies diagnostic communication services, which allow the diagnostic tester (client) to stop or to resume non-diagnostic message transmission, to read vehicle identification data and real-time sensor data, read and clear diagnostic information, control actuators, start/stop routines, and many more functions to assist in diagnosing the vehicle's electronic systems. This document does not apply to non-diagnostic message transmission on the vehicle's communication data link between two electronic control units. This document does not restrict an in-vehicle on-board tester (client) implementation in an ECU/server in order to utilize the diagnostic communication services on the vehicle's communication data link to perform bidirectional diagnostic data exchange. This document does not specify any implementation requirements.