ISO 14229-1:2020 道路車両—統合診断サービス（UDS）—パート1：アプリケーション層 | ページ 6

3.1

boot memory partition

area of the server(3.18) memory in which the boot software(3.2) is located

3.2

boot software

software which is executed in a special part of server(3.18) memory which is used primarily to boot the ECU(3.9) and perform server programming

Note 1 to entry: This area of memory is not erased during a normal programming sequence and executes when the server application is missing or otherwise deemed invalid to always ensure the capability to reprogram the server.

Note 2 to entry: See 0 and 17.3.1.1.

3.3

client

function that is part of the tester(3.20) and that makes use of the diagnostic services(3.6)

Note 1 to entry: A tester normally makes use of other functions such as data base management, specific interpretation, human-machine interface.

3.4

diagnostic channel

dedicated transmission path from client(3.3) to server(3.18) for diagnostic communication

Note 1 to entry: Several simultaneously connected clients to one server can be differentiated by an individual tester(3.20) source address.

3.5

diagnostic data

data that is located in the memory of an electronic control unit(3.9) which may be inspected and/or possibly modified by the tester(3.20)

Note 1 to entry: Diagnostic data includes analogue inputs and outputs, digital inputs and outputs, intermediate values and various status information.

The server(3.18) is not obliged to keep internal copies of its data for diagnostic purposes, in which case the tester may only request the current value.

Note 3 to entry: Defining a repair shop or development testing session selects different server functionality (e.g. access to all memory locations may only be allowed in the development testing session).

3.6

diagnostic service

information exchange initiated by a client(3.3) in order to require diagnostic information from a server(3.18) or/and to modify its behaviour for diagnostic purpose

3.7

diagnostic session

state within the server(3.18) in which a specific set of diagnostic services(3.6) and functionality is enabled

3.8

diagnostic trouble code

DTC

numerical common identifier for a fault condition identified by the on-board diagnostic system

3.9

ECU

electronic control unit

unit providing information regarding the connected sensor and control network

Note 1 to entry: Systems considered as electronic control units include anti-lock braking system (ABS) and engine management system.

3.10

functional unit

set of functionally close or complementary diagnostic services(3.6)

3.11

local server

server(3.18) that is connected to the same local network as the client(3.3) and is part of the same address space as the client

3.12

permanent DTC

diagnostic trouble code(3.8) that remains in non-volatile memory, even after a clear DTC request, until other criteria (typically regulatory) are met (e.g. the appropriate monitors for each DTC have successfully passed)

Note 1 to entry: Refer to the relevant legislation for all necessary requirements.

3.13

record

one or more diagnostic data(3.5) elements that are referred to together by a single means of identification

Note 1 to entry: A snapshot including various input/output data and trouble codes is an example of a record.

3.14

remote server

server(3.18) that is not directly connected to the main diagnostic network

Note 1 to entry: A remote server is identified by means of a remote address. Remote addresses represent an own address space that is independent from the addresses on the main network.

Note 2 to entry: A remote server is reached via a local server(3.11) on the main network. Each local server on the main network can act as a gate to one independent set of remote servers. A pair of addresses therefore always identifies a remote server: one local address that identifies the gate to the remote network and one remote address identifying the remote server itself.

3.15

remote client

client(3.3) that is not directly connected to the main diagnostic network

Note 1 to entry: A remote client is identified by means of a remote address.

Note 2 to entry: Remote addresses represent an own address space that is independent from the addresses on the main network.

3.16

reprogramming software

part of the boot software(3.2) that allows for reprogramming of the electronic control unit(3.9)

3.17

security

mechanism for protecting vehicle modules from"unauthorized" intrusion through a vehicle diagnostic data(3.5) link

3.18

server

function that is part of an electronic control unit(3.9) and that provides the diagnostic services(3.6)

Note 1 to entry: This document differentiates between the server (i.e. the function) and the electronic control unit to ensure independence from implementation.

3.19

supported DTC

diagnostic trouble code(3.8) which is currently configured/calibrated and enabled to execute under predefined vehicle conditions.

3.20

tester

system that controls functions such as test, inspection, monitoring, or diagnosis of an on-vehicle electronic control unit(3.9) and can be dedicated to a specific type of operator (e.g. an off-board scan tool dedicated to garage mechanics, an off-board test tool dedicated to assembly plants, or an on-board tester)

Note 1 to entry: The tester is also referenced as the client(3.3) .