GB/T 40822-2021 English PDF (GBT40822-2021)

Delivery: 3 seconds. Download true-PDF + Invoice.
Get QUOTATION in 1-minute: Click GB/T 40822-2021
Historical versions: GB/T 40822-2021
Preview True-PDF (Reload/Scroll if blank)

GB/T 40822-2021: Road vehicles -- Unified diagnostic services
GB/T 40822-2021
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.040
CCS T 36
Road vehicles - Unified diagnostic services
[ISO 14229-1:2020, ISO 14229-2:2013, ISO 14229-3:2012, ISO 14229-
4:2012, ISO 14229-5:2013, ISO 14229-6:2013, ISO 14229-7:2015, ISO 14229-
8:2020, Road vehicles - Unified diagnostic services (UDS), MOD]
ISSUED ON: OCTOBER 11, 2021
IMPLEMENTED ON: MAY 01, 2022
Issued by: State Administration for Market Regulation;
Standardization Administration of the PRC.
Table of Contents
Foreword ... 16 
Introduction ... 18 
1 Scope ... 20 
2 Normative references ... 20 
3 Terms, definitions and abbreviations ... 22 
3.1 Terms and definitions ... 22 
3.2 Abbreviations ... 26 
4 Conventions ... 29 
5 Overview ... 30 
6 Application layer ... 31 
6.1 Application layer services ... 31 
6.1.1 General ... 31 
6.1.2 Format description of application layer services ... 33 
6.1.3 Format description of service primitives ... 34 
6.1.3.1 General definition ... 34 
6.1.3.2 Service request and service indication primitives ... 34 
6.1.3.3 Service response and service confirm primitives ... 35 
6.1.3.4 Service request-confirm and service response-confirm primitives ... 36 
6.1.4 Service data unit specification ... 37 
6.1.4.1 Mandatory parameters ... 37 
6.1.4.2 Vehicle system requirements ... 40 
6.1.4.3 Optional parameters - A_AE, application layer remote address ... 40 
6.2 Application layer protocol ... 41 
6.2.1 General definition ... 41 
6.2.2 A_PDU, application protocol data unit ... 42 
6.2.3 A_PCI, protocol control information ... 42 
6.2.4 SI, service identifier ... 43 
6.2.5 A_NR_SI, Negative response service identifier ... 44 
6.2.6 Negative response/confirmation service primitive ... 45 
6.2.7 Server response implementation rules ... 45 
6.2.7.1 General definitions ... 45 
6.2.7.2 General server response behaviour ... 46 
6.2.7.3 Request message with SubFunction parameter and server response behaviour
... 48 
6.2.7.4 Request message without SubFunction parameter and server response
behaviour ... 54 
6.2.7.5 Pseudo code example of server response behaviour ... 56 
6.2.7.6 Multiple concurrent request messages with physical and functional
addressing ... 58 
6.3 Service description conventions ... 59 
6.3.1 Service description ... 59 
6.3.2 Request message ... 59 
6.3.2.1 Request message definition ... 59 
6.3.2.2 Request message SubFunction parameter $Level (LEV_) definition ... 60 
6.3.2.3 Request message data-parameter definition ... 62 
6.3.3 Positive response message ... 63 
6.3.3.1 Positive response message definition ... 63 
6.3.3.2 Positive response message data-parameter definition ... 64 
6.3.4 Supported negative response codes (NRC_) ... 64 
6.3.5 Message flow examples ... 65 
6.4 Diagnostic and communication management functional unit ... 66 
6.4.1 Overview ... 66 
6.4.2 DiagnosticSessionControl (1016) service ... 66 
6.4.2.1 Service description ... 66 
6.4.2.2 Request message ... 70 
6.4.2.3 Positive response message ... 72 
6.4.2.4 Supported negative response codes (NRC_) ... 73 
6.4.2.5 Message flow example(s) DiagnosticSessionControl - Start
programmingSession ... 74 
6.4.3 ECUReset (1116) service ... 75 
6.4.3.1 Service description ... 75 
6.4.3.2 Request message ... 75 
6.4.3.3 Positive response message ... 77 
6.4.3.4 Supported negative response codes (NRC_) ... 78 
6.4.3.5 Message flow example ECUReset ... 78 
6.4.4 SecurityAccess (2716) service ... 79 
6.4.4.1 Service description ... 79 
6.4.4.2 Request message ... 81 
6.4.4.3 Positive response message ... 83 
6.4.4.4 Supported negative response codes (NRC_) ... 84 
6.4.4.5 Message flow example(s) SecurityAccess ... 85 
6.4.5 CommunicationControl (2816) service ... 87 
6.4.5.1 Service description ... 87 
6.4.5.2 Request message ... 87 
6.4.5.3 Positive response message ... 89 
6.4.5.4 Supported negative response codes (NRC_) ... 89 
6.4.5.5 Message flow example CommunicationControl (disable transmission of
network management messages) ... 90 
6.4.5.6 Message flow example CommunicationControl (switch a remote network
into the diagnostic-only scheduling mode where the node with address 000A16 is
connected to) ... 90 
6.4.5.7 Message flow example CommunicationControl (switch to application
scheduling mode with enhanced address information, the node 000A16, which is
connected to a sub-network, is addressed) ... 91 
6.4.6 Authentication (2916) service ... 92 
6.4.6.1 Service overview... 92 
6.4.6.2 Authentication with PKI Certificate Exchange (APCE) ... 93 
6.4.6.3 Authentication with Challenge-Response (ACR) ... 99 
6.4.6.4 Common requirements ... 105 
6.4.6.5 Request message ... 106 
6.4.6.6 Positive response message ... 115 
6.4.6.7 Supported negative response codes (NRC_) ... 123 
6.4.6.8 Message flow example(s) Authentication ... 124 
6.4.7 TesterPresent (3E16) service ... 148 
6.4.7.1 Service description ... 148 
6.4.7.2 Request message ... 148 
6.4.7.3 Positive response message ... 149 
6.4.7.4 Supported negative response codes (NRC_) ... 149 
6.4.7.5 Message flow example(s) TesterPresent ... 150 
6.4.8 ControlDTCSetting (8516) service ... 151 
6.4.8.1 Service description ... 151 
6.4.8.2 Request message ... 151 
6.4.8.3 Positive response message ... 153 
6.4.8.4 Supported negative response codes (NRC_) ... 153 
6.4.8.5 Message flow example(s) ControlDTCSetting ... 153 
6.4.9 ResponseOnEvent (8616) service ... 155 
6.4.9.1 Service description ... 155 
6.4.9.2 Request message ... 163 
6.4.9.3 Positive response message ... 171 
6.4.9.4 Supported negative response codes (NRC_) ... 174 
6.4.9.5 Message flow example(s) ResponseOnEvent ... 175 
6.4.10 LinkControl (8716) service ... 192 
6.4.10.1 Service description ... 192 
6.4.10.2 Request message ... 193 
6.4.10.3 Positive response message ... 195 
6.4.10.4 Supported negative response codes (NRC_) ... 196 
6.4.10.5 Message flow example(s) LinkControl ... 196 
6.5 Data transmission functional unit ... 199 
6.5.1 Overview ... 199 
6.5.2 ReadDataByIdentifier (2216) service ... 200 
6.5.2.1 Service description ... 200 
6.5.2.2 Request message ... 200 
6.5.2.3 Positive response message ... 201 
6.5.2.4 Supported negative response codes (NRC_) ... 202 
6.5.2.5 Message flow example ReadDataByIdentifier ... 204 
6.5.3 ReadMemoryByAddress (2316) service ... 207 
6.5.3.1 Service description ... 207 
6.5.3.2 Request message ... 207 
6.5.3.3 Positive response message ... 208 
6.5.3.4 Supported negative response codes (NRC_) ... 209 
6.5.3.5 Message flow example ReadMemoryByAddress ... 211 
6.5.4 ReadScalingDataByIdentifier (2416) service ... 214 
6.5.4.1 Service description ... 214 
6.5.4.2 Request message ... 214 
6.5.4.3 Positive response message ... 215 
6.5.4.4 Supported negative response codes (NRC_) ... 216 
6.5.4.5 Message flow example ReadScalingDataByIdentifier ... 217 
6.5.5 ReadDataByPeriodicIdentifier (2A16) service ... 221 
6.5.5.1 Service description ... 221 
6.5.5.2 Request message ... 225 
6.5.5.3 Positive response message ... 226 
6.5.5.4 Supported negative response codes (NRC_) ... 227 
6.5.5.5 Message flow example ReadDataByPeriodicIdentifier ... 230 
6.5.6 DynamicallyDefineDataIdentifier (2C16) service ... 244 
6.5.6.1 Service descriptio...