ISO 14229-1:2020

INTERNATIONAL ISO
STANDARD 14229-1
Third edition
2020-02
Road vehicles — Unified diagnostic
services (UDS) —
Part 1:
Application layer
Véhicules routiers — Services de diagnostic unifiés (SDU) —
Partie 1: Couches application
Reference number
©
ISO 2020
© ISO 2020
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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved

Contents Page
Foreword . ix
Introduction . x
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms . 5
5 Conventions . 5
6 Document overview . 6
7 Application layer services . 7
7.1 General . 7
7.2 Format description of application layer services . 9
7.3 Format description of service primitives . 9
7.3.1 General definition. 9
7.3.2 Service request and service indication primitives . 10
7.3.3 Service response and service confirm primitives . 11
7.3.4 Service request-confirm and service response-confirm primitives . 11
7.4 Service data unit specification . 12
7.4.1 Mandatory parameters . 12
7.4.2 Vehicle system requirements . 14
7.4.3 Optional parameters - A_AE, application layer remote address . 15
8 Application layer protocol . 15
8.1 General definition. 15
8.2 A_PDU, application protocol data unit . 16
8.3 A_PCI, application protocol control information . 16
8.4 SI, service identifier . 17
8.5 A_NR_SI, Negative response service identifier . 17
8.6 Negative response/confirmation service primitive . 18
8.7 Server response implementation rules . 18
8.7.1 General definitions. 18
8.7.2 General server response behaviour . 19
8.7.3 Request message with SubFunction parameter and server response behaviour . 21
8.7.4 Request message without SubFunction parameter and server response behaviour . 25
8.7.5 Pseudo code example of server response behaviour . 27
8.7.6 Multiple concurrent request messages with physical and functional addressing . 29
9 Service description conventions . 29
9.1 Service description . 29
9.2 Request message . 30
9.2.1 Request message definition . 30
9.2.2 Request message SubFunction parameter $Level (LEV_) definition . 31
9.2.3 Request message data-parameter definition . 33
9.3 Positive response message. 33
9.3.1 Positive response message definition . 33
9.3.2 Positive response message data-parameter definition . 34
iii
9.4 Supported negative response codes (NRC_) . 34
9.5 Message flow examples . 35
10 Diagnostic and communication management functional unit . 36
10.1 Overview . 36
10.2 DiagnosticSessionControl (10 ) service . 36
10.2.1 Service description . 36
10.2.2 Request message . 40
10.2.3 Positive response message . 41
10.2.4 Supported negative response codes (NRC_) . 42
10.2.5 Message flow example(s) DiagnosticSessionControl – Start programmingSession . 43
10.3 ECUReset (11 ) service . 43
10.3.1 Service description . 43
10.3.2 Request message . 44
10.3.3 Positive response message . 45
10.3.4 Supported negative response codes (NRC_) . 46
10.3.5 Message flow example ECUReset . 47
10.4 SecurityAccess (27 ) service. 47
10.4.1 Service description . 47
10.4.2 Request message . 49
10.4.3 Positive response message . 51
10.4.4 Supported negative response codes (NRC_) . 51
10.4.5 Message flow example(s) SecurityAccess . 52
10.5 CommunicationControl (28 ) service . 54
10.5.1 Service description . 54
10.5.2 Request message . 54
10.5.3 Positive response message . 56
10.5.4 Supported negative response codes (NRC_) . 56
10.5.5 Message flow example CommunicationControl (disable transmission of network
management messages). 57
10.5.6 Message flow example CommunicationControl (switch a remote network into the
diagnostic-only scheduling mode where the node with address 000A is connected
to) . 57
10.5.7 Message flow example CommunicationControl (switch to application scheduling
mode with enhanced address information, the node 000A , which is connected to a
sub-network, is addressed) . 58
10.6 Authentication (29 ) service . 59
10.6.1 Service overview . 59
10.6.2 Authentication with PKI Certificate Exchange (APCE). 60
10.6.3 Authentication with Challenge-Response (ACR) . 65
10.6.4 Common requirements . 69
10.6.5 Request message . 71
10.6.6 Positive response message . 78
10.6.7 Supported negative response codes (NRC_) . 85
10.6.8 Message flow example(s) Authentication . 86
10.7 TesterPresent (3E ) service . 108
10.7.1 Service description . 108
10.7.2 Request message . 108
10.7.3 Positive response message . 108
10.7.4 Supported negative response codes (NRC_) . 109
10.7.5 Message flow example(s) TesterPresent . 109
10.8 ControlDTCSetting (85 ) service .
...