Powered by Google www.ChineseStandard.net Database: 189759 (21 Apr 2024)

GB/T 40822-2021 (GB/T40822-2021)

Standard IDContents [version]USDSTEP2[PDF] delivered inName of Chinese StandardStatus
GB/T 40822-2021English8005 Add to Cart 0-9 seconds. Auto-delivery. Road vehicles -- Unified diagnostic services Valid


Standards related to: GB/T 40822-2021

GB/T 40822-2021: PDF in English (GBT 40822-2021)

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 description ... 244 
6.5.6.2 Request message ... 246 
6.5.6.3 Positive response message ... 250 
6.5.6.4 Supported negative response codes (NRC_) ... 251 
6.5.6.5 Message flow examples DynamicallyDefineDataIdentifier ... 252 
6.5.7 WriteDataByIdentifier (2E16) service ... 268 
6.5.7.1 Service description ... 268 
6.5.7.2 Request message ... 269 
6.5.7.3 Positive response message ... 269 
6.5.7.4 Supported negative response codes (NRC_) ... 270 
6.5.7.5 Message flow example WriteDataByIdentifier ... 271 
6.5.8 WriteMemoryByAddress (3D16) service ... 272 
6.5.8.1 Service description ... 272 
6.5.8.2 Request message ... 273 
6.5.8.3 Positive response message ... 274 
6.5.8.4 Supported negative response codes (NRC_) ... 275 
6.5.8.5 Message flow example WriteMemoryByAddress ... 277 
6.6 Stored data transmission functional unit ... 280 
6.6.1 Overview ... 280 
6.6.2 ClearDiagnosticInformation (1416) service ... 281 
6.6.2.1 Service description ... 281 
6.6.2.2 Request message ... 281 
6.6.2.3 Positive response message ... 282 
6.6.2.4 Supported negative response codes (NRC_) ... 282 
6.6.2.5 Message flow example ClearDiagnosticInformation ... 284 
6.6.3 ReadDTCInformation (1916) service ... 285 
6.6.3.1 Service description ... 285 
6.6.3.2 Request message ... 301 
6.6.3.3 Positive response message ... 313 
6.6.3.4 Supported negative response codes (NRC_) ... 330 
6.6.3.5 Message flow examples - ReadDTCInformation ... 331 
6.7 InputOutput control functional unit ... 369 
6.7.1 Overview ... 369 
6.7.2 InputOutputControlByIdentifier (2F16) service ... 369 
6.7.2.1 Service description ... 369 
6.7.2.2 Request message ... 371 
6.7.2.3 Positive response message ... 372 
6.7.2.4 Supported negative response codes (NRC_) ... 373 
6.7.2.5 Message flow example(s) InputOutputControlByIdentifier ... 374 
6.8 Routine functional unit ... 384 
6.8.1 Overview ... 384 
6.8.2 RoutineControl (3116) service ... 385 
6.8.2.1 Service description ... 385 
6.8.2.2 Request message ... 386 
6.8.2.3 Positive response message ... 388 
6.8.2.4 Supported negative response codes (NRC_) ... 389 
6.8.2.5 Message flow example(s) RoutineControl ... 392 
6.9 Upload download functional unit ... 395 
6.9.1 Overview ... 395 
6.9.2 RequestDownload (3416) service ... 396 
6.9.2.1 Service description ... 396 
6.9.2.2 Request message ... 396 
6.9.2.3 Positive response message ... 397 
6.9.2.4 Supported negative response codes (NRC_) ... 398 
6.9.2.5 Message flow example(s) RequestDownload ... 400 
6.9.3 RequestUpload (3516) service ... 400 
6.9.3.1 Service description ... 400 
6.9.3.2 Request message ... 401 
6.9.3.3 Positive response message ... 402 
6.9.3.4 Supported negative response codes (NRC_) ... 403 
6.9.3.5 Message flow example(s) RequestUpload ... 405 
6.9.4 TransferData (3616) service ... 406 
6.9.4.1 Service description ... 406 
6.9.4.2 Request message ... 406 
6.9.4.3 Positive response message ... 407 
6.9.4.4 Supported negative response codes (NRC_) ... 408 
6.9.4.5 Message flow example(s) TransferData ... 410 
6.9.5 RequestTransferExit (3716) service ... 410 
6.9.5.1 Service description ... 410 
6.9.5.2 Request message ... 411 
6.9.5.3 Positive response message ... 411 
6.9.5.4 Supported negative response codes (NRC_) ... 412 
6.9.5.5 Message flow example(s) for downloading/uploading data ... 413 
6.9.6 RequestFileTransfer (3816) service ... 421 
6.9.6.1 Service description ... 421 
6.9.6.2 Request message ... 421 
6.9.6.3 Positive response message ... 423 
6.9.6.4 Supported negative response codes (NRC_) ... 425 
6.9.6.5 Message flow example(s) RequestFileTransfer ... 427 
6.10 Security sub-layer definition ... 430 
6.10.1 General ... 430 
6.10.1.1 Purpose ... 430 
6.10.1.2 Security sub-layer description ... 430 
6.10.1.3 Security sub-layer access ... 432 
6.10.1.4 General server response behaviour ... 434 
6.10.2 SecuredDataTransmission (8416) service ... 436 
6.10.2.1 Service description ... 436 
6.10.2.2 Request message ... 436 
6.10.2.3 Positive response message for successful internal message ... 438 
6.10.2.4 Supported negative response codes (NRC_) ... 441 
6.10.2.5 Message flow example SecuredDataTransmission ... 441 
6.11 Non-volatile server memory programming process ... 445 
6.11.1 General information ... 445 
6.11.2 Detailed programming sequence ... 450 
6.11.2.1 Programming phase #1 - Download of application software and/or
application data ... 450 
6.11.2.2 Preprogramming step of phase #2 - Server configuration ... 458 
6.11.2.3 Programming step of phase #2 - Final server configuration ... 459 
6.11.2.4 Post-programming step of phase #2 - Re-synchronisation of vehicle network
... 460 
6.11.3 Server reprogramming requirements ... 461 
6.11.3.1 Requirements for servers to support programming... 461 
6.11.3.2 Software, data identification and fingerprints ... 466 
6.11.3.3 Server routine access ... 466 
6.11.4 Non-volatile server memory programming message flow examples ... 467 
6.11.4.1 General information ... 467 
6.11.4.2 Programming phase #1 - Pre-Programming step ... 467 
6.11.4.3 Programming phase #1 - Programming step ... 468 
6.11.5 Programming phase #1 - Post-Programming step ... 472 
7 Session layer services ... 472 
7.1 Document overview ... 472 
7.2 Service content ... 473 
7.2.1 General ... 473 
7.2.2 Specification of session layer service primitives ... 476 
7.2.2.1 General ... 476 
7.2.2.2 S_Data.request ... 476 
7.2.2.3 S_Data.confirm ... 476 
7.2.2.4 S_Data.indication ... 477 
7.2.3 Session data unit specification ... 477 
7.2.3.1 S_Mtype, Session layer message type ... 477 
7.2.3.2 S_SA, Session layer source address ... 477 
7.2.3.3 S_TA, Session layer target address ... 478 
7.2.3.4 S_TAtype, Session layer target address type ... 478 
7.2.3.5 S_AE, Session layer Address Extension (optional parameter) ... 478 
7.2.3.6 S_Length ... 478 
7.2.3.7 S_Data ... 479 
7.2.3.8 S_Result ... 479 
7.2.3.9 Mapping of S_PDU onto T_PDU and vice versa for message transmission
... 479 
7.3 Timing parameter definition ... 480 
7.3.1 General application timing considerations ... 480 
7.3.1.1 Server ... 480 
7.3.1.2 Client ... 481 
7.3.2 Application timing parameter definitions - defaultSession ... 481 
7.3.3 Example for P4Server without enhanced response timing ... 485 
7.3.4 Example for P4Server with enhanced response timing ... 486 
7.3.5 Session timing parameter definitions for the non-default session ... 488 
7.3.6 Client and server timer resource requirements ... 490 
7.3.7 Error handling ... 490 
7.4 Timing handling during communication ... 492 
7.4.1 Physical communication ... 492 
7.4.1.1 Physical communication during defaultSession - without SOM.ind ... 492 
7.4.1.2 Physical communication during defaultSession - with SOM.ind ... 492 
7.4.1.3 Physical communication during defaultSession with enhanced response
timing ... 493 
7.4.1.4 Physical communication during a non-default session ... 495 
7.4.2 Functional communication ... 503 
7.4.2.1 Functional communication during defaultSession - without SOM.ind ... 503 
7.4.2.2 Functional communication during defaultSession - with SOM.ind ... 504 
7.4.2.3 Functional communication during defaultSession with enhanced response
timing - with SOM.ind ... 505 
7.4.2.4 Functional communication during non-default session - with SOM.ind ... 507 
7.4.3 Minimum time between client request messages ... 512 
8 UDSonCAN ... 520 
8.1 Document overview ... 520 
8.2 Unified diagnostic services implementation on CAN ... 522 
8.2.1 General ... 522 
8.2.2 UDS on CAN services overview ... 522 
8.2.3 ResponseOnEvent (8616) service DoCAN implementation requirements ... 523 
8.2.4 ReadDataByPeriodicIdentifier (2A16) service ... 525 
8.2.4.1 Periodic transmission response message ... 525 
8.2.4.2 Periodic transmission response message handling ... 526 
8.2.4.3 CAN frame format ... 527 
8.3 Application layer requirements ... 532 
8.3.1 Application layer services ... 532 
8.3.2 Application layer protocol ... 533 
8.3.3 Application layer timing ... 533 
8.3.3.1 General ... 533 
8.3.3.2 Message timing parameter values ... 533 
8.3.3.3 Unsolicited response messages ... 533 
8.4 Presentation layer requirements ... 533 
8.5 Session layer requirements ... 533 
8.6 Transport/Network layer interface adaptation ... 533 
8.6.1 General information ... 533 
8.6.2 DoCAN Transport/Network layer interface adaptation ... 534 
8.6.2.1 Mapping of data link independent service primitives onto CAN data link
dependent service primitives ... 534 
8.6.2.2 Mapping of T_PDU onto N_PDU for message transmission ... 534 
8.7 Data link layer diagnostic implementation requirements ... 535 
8.7.1 Usage of legislated 11-bit OBD CAN Identifiers for enhanced diagnostics ... 535 
8.7.2 Usage of legislated 29-bit OBD CAN Identifiers for enhanced diagnostics ... 535 
9 UDSonFR ... 536 
9.1 Document overview ... 536 
9.2 Unified diagnostic services implementation on FlexRay ... 538 
9.2.1 General ... 538 
9.2.2 UDS on FlexRay services overview ... 538 
9.2.3 CommunicationControl (2816) service ... 539 
9.2.4 ResponseOnEvent (8616) service ... 540 
9.2.5 LinkControl (8716) service ... 542 
9.2.6 ReadDataByPeriodicIdentifier (2A16) service ... 543 
9.2.6.1 Periodic transmission response message ... 543 
9.2.6.2 Periodic transmission response message handling ... 544 
9.2.6.3 Periodic transmission message flow ... 546 
9.3 Application layer requirements ... 550 
9.3.1 Application layer services ... 550 
9.3.2 Application layer protocol ... 551 
9.3.3 Application layer timing ... 551 
9.4 Presentation layer requirements ... 551 
9.5 Session layer requirements ... 551 
9.6 Transport/Network layer interface adaptation ... 551 
9.6.1 General information ... 551 
9.6.2 DoFR Transport/Network layer interface adaptation ... 551 
9.6.2.1 Mapping of data link independent service primitives onto FlexRay data link
dependent service primitives ... 551 
9.6.2.2 Mapping of T_PDU onto C_PDU for message transmission ... 552 
9.7 Data Link layer diagnostic implementation requirements ... 552 
10 UDSonIP ... 553 
10.1 Document overview ... 553 
10.2 Unified diagnostic services implementation on Internet Protocol ... 555 
10.2.1 General ... 555 
10.2.2 UDS on IP services overview ... 555 
10.2.3 DiagnosticSessionControl (1016) service ... 556 
10.2.4 ECUReset (1116) service ... 556 
10.2.5 ReadDataByPeriodicIdentifier (2A16) service DoIP implementation requirements
... 557 
10.2.5.1 Periodic data response message ... 557 
10.2.5.2 Periodic transmission response message handling ... 557 
10.3 Application layer requirements ... 565 
10.3.1 Application layer services ... 565 
10.3.2 Application layer protocol ... 565 
10.3.3 Application layer timing ... 565 
10.4 Presentation layer requirements ... 565 
10.5 Session layer requirements ... 565 
10.6 Transport/network layer interface adaptation ... 565 
10.6.1 General information ... 565 
10.6.2 DoIP transport/network layer interface adaptation ... 566 
10.6.2.1 Mapping of data link-independent service primitives onto IP data link-
dependent service primitives ... 566 
10.6.2.2 Mapping of T_PDU onto DoIP_PDU for message transmission ... 566 
10.7 Data link layer diagnostic implementation requirements ... 567 
11 UDSonK-Line ... 567 
11.1 Document overview ... 567 
11.2 Unified diagnostic services implementation on K-Line ... 569 
11.2.1 General ... 569 
11.2.2 UDSonK-Line services overview ... 569 
11.2.3 Diagnostic and communication control functional unit ... 570 
11.2.3.1 AccessTimingParameter (8316) service ... 570 
11.2.3.2 LinkControl (8716) service ... 571 
11.2.4 Data transmission functional unit ... 572 
11.3 Application layer requirements ... 572 
11.3.1 Application layer services ... 572 
11.3.2 Application layer protocol ... 572 
11.3.3 Application layer timing ... 572 
11.3.3.1 General ... 572 
11.3.3.2 Application layer timing parameter values ... 572 
11.4 Presentation layer requirements ... 572 
11.5 Session layer requirements ... 572 
11.6 Transport/network layer interface adaptation ... 573 
11.6.1 General information ... 573 
11.6.2 DoK-Line transport/network layer interface adaptation ... 573 
11.6.2.1 Mapping of data link independent service primitives onto K-Line data link
dependent service primitives ... 573 
11.6.2.2 Mapping of T_PDU onto DL_PDU for message transmission ... 573 
11.7 Data link layer diagnostic implementation requirements ... 574 
11.7.1 General information ... 574 
11.7.2 Data segmentation ... 574 
11.7.3 Session handling ... 574 
11.7.4 Timings ... 575 
11.7.5 Protocol initialization, start and stop of communication ... 575 
11.7.6 Error handling ... 576 
11.8 Non-volatile server memory programming process ... 576 
12 UDSonLIN ... 576 
12.1 Document overview ... 576 
12.2 UDSonLIN implementation requirements ... 578 
12.2.1 General ... 578 
12.2.2 Definition of diagnostic classes ... 578 
12.2.2.1 Overview ... 578 
12.2.2.2 Diagnostic class I ... 578 
12.2.2.3 Diagnostic class II ... 578 
12.2.2.4 Diagnostic class III ... 578 
12.2.3 LIN node requirements ... 579 
12.2.3.1 Master node requirements ... 579 
12.2.3.2 Slave node requirements ... 580 
12.2.4 Signal-based diagnostics ... 580 
12.2.4.1 Slave implementation ... 580 
12.2.4.2 Master implementation ... 581 
12.2.5 Tool suite support ... 581 
12.3 UDSonLIN implementation ... 581 
12.3.1 UDSonLIN services overview ... 581 
12.3.2 Diagnostic and communication control functional unit ... 582 
12.3.2.1 CommunicationControl (2816) service ... 582 
12.3.2.2 ResponseOnEvent (8616) service ... 583 
12.4 Application layer requirements ... 583 
12.4.1 Application layer services ... 583 
12.4.2 Application layer protocol ... 583 
12.4.3 Application layer timing ... 584 
12.4.3.1 General ... 584 
12.4.3.2 Application layer timing parameter values ... 584 
12.5 Presentation layer requirements ... 586 
12.6 Session layer requirements ... 586 
12.7 Transport/network layer interface adaptation ... 586 
12.7.1 General information ... 586 
12.7.2 LIN transport/network layer interface adaptation ... 586 
12.7.2.1 Mapping of data link independent service primitives onto LIN data link
dependent service primitives ... 586 
12.7.2.2 Mapping of T_PDU onto N_PDU for message transmission ... 586 
12.8 Network layer diagnostic implementation requirements ... 587 
12.8.1 LIN slave node network layer requirements ... 587 
12.8.2 LIN master node network layer requirements ... 588 
12.8.2.1 Network address requirements ... 588 
12.8.2.2 Use of functional addressing ... 589 
12.9 Data link layer diagnostic implementation requirements ... 589 
13 UDSonCXPI ... 589 
13.1 Document overview ... 589 
13.2 UDSonCXPI implementation requirements ... 590 
13.3 SIP - Service interface parameters ... 591 
13.3.1 SIP - General ... 591 
13.3.2 SIP - Data type definitions ... 591 
13.3.3 SIP - A_Mtype, message type ... 591 
13.3.4 SIP - A_TAtype, target address type ... 591 
13.3.5 SIP - A_TA, target address ... 592 
13.3.6 SIP - A_SA, source address ... 592 
13.3.7 SIP - A_Length, length of A_PDU ... 592 
13.3.8 SIP - A_Data, protocol data unit ... 592 
13.3.9 SIP - A_SCT, sequence count ... 592 
13.3.10 SIP - A_Result, result ... 593 
13.3.11 SIP - ev_wakeup_ind, event wake-up indication (optional) ... 593 
13.3.12 SIP - cmd_wakeup_req, command wake-up request ... 593 
13.3.13 SIP - NMInfo, network management information ... 594 
13.4 APP - Application ... 594 
13.4.1 APP - General ... 594 
13.4.2 APP - Definition of diagnostic classes ... 595 
13.4.2.1 APP - Overview ... 595 
13.4.2.2 APP - Diagnostic class I ... 595 
13.4.2.3 APP - Diagnostic class II ... 595 
13.4.2.4 APP - Diagnostic class III ... 595 
13.4.3 APP - CXPI master node requirements - Master node fault management, sensor
reading, I/O control ... 596 
13.4.4 APP - CXPI slave node requirements ... 596 
13.4.4.1 APP - General ... 596 
13.4.4.2 APP - Error indications ... 596 
13.4.5 APP - CXPI measurement and control data diagnostics ... 597 
13.4.5.1 APP - Master handling of slave failure status measurement and control data
... 597 
13.4.5.2 APP - Slave node current failure status support ... 597 
13.4.6 APP - Network management (optional) ... 598 
13.4.7 APP - CXPI master node gateway application ... 598 
13.4.7.1 APP - General ... 598 
13.4.7.2 APP - CXPI master gateway number of subnets ... 598 
13.4.7.3 APP - CXPI master gateway address routing table ... 598 
13.4.7.4 APP - CXPI master gateway all nodes request message handling ... 598 
13.4.7.5 APP - Round trip of all node addressing with functional NAD ... 599 
13.4.7.6 APP - Round trip of all node addressing with node-specific NADs ... 599 
13.5 AL - Application layer ... 600 
13.5.1 AL - Client to CXPI slave node(s) communication ... 600 
13.5.2 AL - Overview of UDSonCXPI services and applicability to diagnostic classes
... 600 
13.5.3 AL - CommunicationControl (2816) service ... 602 
13.5.4 AL - UDSonCXPI services ... 603 
13.5.4.1 AL - Supported functions ... 603 
13.5.4.2 AL - Master node receive buffer length ... 603 
13.5.4.3 AL - Message length is exceeded ... 604 
13.5.5 AL - Protocol ... 604 
13.5.6 AL - Timing ... 604 
13.5.6.1 AL - General ... 604 
13.5.6.2 AL - Timing parameter values ... 604 
13.5.6.3 AL - Server timing performance requirements ... 604 
13.5.6.4 AL - SuppressPosRspMsgIndicationBit ... 604 
13.5.7 AL - Response pending ... 605 
13.5.8 AL - CXPI slave node configuration services ... 605 
13.5.8.1 AL - CXPI node configuration ... 605 
13.5.8.2 AL - Slave node model ... 606 
13.5.8.3 AL - WriteDataByIdentifier - AssignNodeAddress ... 610 
13.5.8.4 AL - WriteDataByIdentifier - NodeDataDump ... 612 
13.5.8.5 AL - ReadDataByIdentifier - NodeProductIdentification ... 613 
13.5.8.6 AL - ReadDataByIdentifier - NodeSerialNumberIdentification ... 614 
13.5.8.7 AL - ReadDataByIdentifier - NodeConfigurationFileAvailability ... 615 
13.5.8.8 AL - WriteDataByIdentifier - SaveConfiguration ... 617 
13.5.8.9 AL - WriteDataByIdentifier - AssignFrameIdentifierRange ... 618 
13.6 PL - Presentation layer ... 620 
13.7 SL - Session layer ... 620 
13.7.1 SL - General ... 620 
13.7.2 SL - A_Data and T_Data service interface parameter mapping ... 620 
13.8 TL - Transport layer ... 620 
13.8.1 TL - Service primitive interface adaptation - General information ... 620 
13.8.2 TL - CXPI transport layer interface adaptation ... 621 
13.8.2.1 TL - Mapping of session layer to transport layer service primitives ... 621 
13.8.2.2 TL - Mapping of T_Data service primitive interface parameters ... 621 
13.9 NL - Network layer ... 622 
13.9.1 NL - Service primitive interface adaptation ... 622 
13.9.1.1 NL - General information ... 622 
13.9.1.2 NL - CXPI network layer interface adaptation ... 622 
13.9.2 NL - CXPI master node ... 623 
13.9.2.1 NL - Network layer ... 623 
13.9.2.2 NL - Dynamic NAD assignment ... 623 
13.9.2.3 NL - NodeIdentificationNumber ... 623 
13.9.3 NL - Master message routing ... 623 
13.9.3.1 NL - General ... 623 
13.9.3.2 NL - Diagnostic request message routing ... 624 
13.9.3.3 NL - Diagnostic response message routing ... 624 
13.9.3.4 NL - Master node transport protocol support ... 624 
13.9.4 NL - CXPI slave node ... 624 
13.9.4.1 NL - General ... 624 
13.9.4.2 NL - Node configuration handling ... 624 
13.9.4.3 NL - Slave node diagnostic class II ... 625 
13.9.4.4 NL - Slave node diagnostic class II - Fixed node address ... 625 
13.9.4.5 NL - Slave node diagnostic class II - Ignore NAD 7E16 as broadcast ... 625 
13.9.4.6 NL - Slave diagnostic class III - Network layer... 625 
13.9.4.7 NL - Slave diagnostic class III - Fixed node address ... 625 
13.9.4.8 NL - Slave diagnostic class III - Accept NAD 7E16 as broadcast ... 626 
13.10 DLL - Data link layer ... 626 
Annex A (Normative) Global parameter definitions ... 627 
Annex B (Normative) Diagnostic and communication management functional unit
data-parameter definitions ... 637 
Annex C (Normative) Data transmission functional unit data-parameter definitions643 
Annex D (Normative) Stored data transmission functional unit data-parameter
definitions ... 661 
Annex E (Normative) Input output control functional unit data-parameter definitions
... 683 
Annex F (Normative) Routine functional unit data-parameter definitions ... 684 
Annex G (Normative) Upload and download functional unit data-parameter ... 686 
Annex H (Informative) Examples for addressAndLengthFormatIdentifier parameter
values ... 687 
Annex I (Informative) Security access state chart ... 689 
Annex J (Informative) Recommen......
 
Source: Above contents are excerpted from the PDF -- translated/reviewed by: www.chinesestandard.net / Wayne Zheng et al.