GB/T 40822-2021Road vehicles - Unified diagnostic services (English PDF)

Contents

• Foreword16
• Introduction18
• 1 Scope20
• 2 Normative references20
• 3 Terms, definitions and abbreviations22
• 3.1 Terms and definitions22
• 3.2 Abbreviations26
• 4 Conventions29
• 5 Overview30
• 6 Application layer31
• 6.1 Application layer services31
• 6.1.1 General31
• 6.1.2 Format description of application layer services33
• 6.1.3 Format description of service primitives34
• 6.1.3.1 General definition34
• 6.1.3.2 Service request and service indication primitives34
• 6.1.3.3 Service response and service confirm primitives35
• 6.1.3.4 Service request-confirm and service response-confirm primitives36
• 6.1.4 Service data unit specification37
• 6.1.4.1 Mandatory parameters37
• 6.1.4.2 Vehicle system requirements40
• 6.1.4.3 Optional parameters - A_AE, application layer remote address40
• 6.2 Application layer protocol41
• 6.2.1 General definition41
• 6.2.2 A_PDU, application protocol data unit42
• 6.2.3 A_PCI, protocol control information42
• 6.2.4 SI, service identifier43
• 6.2.5 A_NR_SI, Negative response service identifier44
• 6.2.6 Negative response/confirmation service primitive45
• 6.2.7 Server response implementation rules45
• 6.2.7.1 General definitions45
• 6.2.7.2 General server response behaviour46
• behaviour54
• 6.2.7.5 Pseudo code example of server response behaviour56
• addressing58
• 6.3 Service description conventions59
• 6.3.1 Service description59
• 6.3.2 Request message59
• 6.3.2.1 Request message definition59
• 6.3.2.2 Request message SubFunction parameter $Level (LEV_) definition60
• 6.3.2.3 Request message data-parameter definition62
• 6.3.3 Positive response message63
• 6.3.3.1 Positive response message definition63
• 6.3.3.2 Positive response message data-parameter definition64
• 6.3.4 Supported negative response codes (NRC_)64
• 6.3.5 Message flow examples65
• 6.4 Diagnostic and communication management functional unit66
• 6.4.1 Overview66
• 6.4.2 DiagnosticSessionControl (1016) service66
• 6.4.2.1 Service description66
• 6.4.2.2 Request message70
• 6.4.2.3 Positive response message72
• 6.4.2.4 Supported negative response codes (NRC_)73
• programmingSession74
• 6.4.3 ECUReset (1116) service75
• 6.4.3.1 Service description75
• 6.4.3.2 Request message75
• 6.4.3.3 Positive response message77
• 6.4.3.4 Supported negative response codes (NRC_)78
• 6.4.3.5 Message flow example ECUReset78
• 6.4.4 SecurityAccess (2716) service79
• 6.4.4.1 Service description79
• 6.4.4.2 Request message81
• 6.4.4.3 Positive response message83
• 6.4.4.4 Supported negative response codes (NRC_)84
• 6.4.4.5 Message flow example(s) SecurityAccess85
• 6.4.5 CommunicationControl (2816) service87
• 6.4.5.1 Service description87
• 6.4.5.2 Request message87
• 6.4.5.3 Positive response message89
• 6.4.5.4 Supported negative response codes (NRC_)89
• network management messages)90
• connected to)90
• connected to a sub-network, is addressed)91
• 6.4.6 Authentication (2916) service92
• 6.4.6.1 Service overview92
• 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 requirements105
• 6.4.6.5 Request message106
• 6.4.6.6 Positive response message115
• 6.4.6.7 Supported negative response codes (NRC_)123
• 6.4.6.8 Message flow example(s) Authentication124
• 6.4.7 TesterPresent (3E16) service148
• 6.4.7.1 Service description148
• 6.4.7.2 Request message148
• 6.4.7.3 Positive response message149
• 6.4.7.4 Supported negative response codes (NRC_)149
• 6.4.7.5 Message flow example(s) TesterPresent150
• 6.4.8 ControlDTCSetting (8516) service151
• 6.4.8.1 Service description151
• 6.4.8.2 Request message151
• 6.4.8.3 Positive response message153
• 6.4.8.4 Supported negative response codes (NRC_)153
• 6.4.8.5 Message flow example(s) ControlDTCSetting153
• 6.4.9 ResponseOnEvent (8616) service155
• 6.4.9.1 Service description155
• 6.4.9.2 Request message163
• 6.4.9.3 Positive response message171
• 6.4.9.4 Supported negative response codes (NRC_)174
• 6.4.9.5 Message flow example(s) ResponseOnEvent175
• 6.4.10 LinkControl (8716) service192
• 6.4.10.1 Service description192
• 6.4.10.2 Request message193
• 6.4.10.3 Positive response message195
• 6.4.10.4 Supported negative response codes (NRC_)196
• 6.4.10.5 Message flow example(s) LinkControl196
• 6.5 Data transmission functional unit199
• 6.5.1 Overview199
• 6.5.2 ReadDataByIdentifier (2216) service200
• 6.5.2.1 Service description200
• 6.5.2.2 Request message200
• 6.5.2.3 Positive response message201
• 6.5.2.4 Supported negative response codes (NRC_)202
• 6.5.2.5 Message flow example ReadDataByIdentifier204
• 6.5.3 ReadMemoryByAddress (2316) service207
• 6.5.3.1 Service description207
• 6.5.3.2 Request message207
• 6.5.3.3 Positive response message208
• 6.5.3.4 Supported negative response codes (NRC_)209
• 6.5.3.5 Message flow example ReadMemoryByAddress211
• 6.5.4 ReadScalingDataByIdentifier (2416) service214
• 6.5.4.1 Service description214
• 6.5.4.2 Request message214
• 6.5.4.3 Positive response message215
• 6.5.4.4 Supported negative response codes (NRC_)216
• 6.5.4.5 Message flow example ReadScalingDataByIdentifier217
• 6.5.5 ReadDataByPeriodicIdentifier (2A16) service221
• 6.5.5.1 Service description221
• 6.5.5.2 Request message225
• 6.5.5.3 Positive response message226
• 6.5.5.4 Supported negative response codes (NRC_)227
• 6.5.5.5 Message flow example ReadDataByPeriodicIdentifier230
• 6.5.6 DynamicallyDefineDataIdentifier (2C16) service244
• 6.5.6.1 Service description244
• 6.5.6.2 Request message246
• 6.5.6.3 Positive response message250
• 6.5.6.4 Supported negative response codes (NRC_)251
• 6.5.6.5 Message flow examples DynamicallyDefineDataIdentifier252
• 6.5.7 WriteDataByIdentifier (2E16) service268
• 6.5.7.1 Service description268
• 6.5.7.2 Request message269
• 6.5.7.3 Positive response message269
• 6.5.7.4 Supported negative response codes (NRC_)270
• 6.5.7.5 Message flow example WriteDataByIdentifier271
• 6.5.8 WriteMemoryByAddress (3D16) service272
• 6.5.8.1 Service description272
• 6.5.8.2 Request message273
• 6.5.8.3 Positive response message274
• 6.5.8.4 Supported negative response codes (NRC_)275
• 6.5.8.5 Message flow example WriteMemoryByAddress277
• 6.6 Stored data transmission functional unit280
• 6.6.1 Overview280
• 6.6.2 ClearDiagnosticInformation (1416) service281
• 6.6.2.1 Service description281
• 6.6.2.2 Request message281
• 6.6.2.3 Positive response message282
• 6.6.2.4 Supported negative response codes (NRC_)282
• 6.6.2.5 Message flow example ClearDiagnosticInformation284
• 6.6.3 ReadDTCInformation (1916) service285
• 6.6.3.1 Service description285
• 6.6.3.2 Request message301
• 6.6.3.3 Positive response message313
• 6.6.3.4 Supported negative response codes (NRC_)330
• 6.6.3.5 Message flow examples - ReadDTCInformation331
• 6.7 InputOutput control functional unit369
• 6.7.1 Overview369
• 6.7.2 InputOutputControlByIdentifier (2F16) service369
• 6.7.2.1 Service description369
• 6.7.2.2 Request message371
• 6.7.2.3 Positive response message372
• 6.7.2.4 Supported negative response codes (NRC_)373
• 6.7.2.5 Message flow example(s) InputOutputControlByIdentifier374
• 6.8 Routine functional unit384
• 6.8.1 Overview384
• 6.8.2 RoutineControl (3116) service385
• 6.8.2.1 Service description385
• 6.8.2.2 Request message386
• 6.8.2.3 Positive response message388
• 6.8.2.4 Supported negative response codes (NRC_)389
• 6.8.2.5 Message flow example(s) RoutineControl392
• 6.9 Upload download functional unit395
• 6.9.1 Overview395
• 6.9.2 RequestDownload (3416) service396
• 6.9.2.1 Service description396
• 6.9.2.2 Request message396
• 6.9.2.3 Positive response message397
• 6.9.2.4 Supported negative response codes (NRC_)398
• 6.9.2.5 Message flow example(s) RequestDownload400
• 6.9.3 RequestUpload (3516) service400
• 6.9.3.1 Service description400
• 6.9.3.2 Request message401
• 6.9.3.3 Positive response message402
• 6.9.3.4 Supported negative response codes (NRC_)403
• 6.9.3.5 Message flow example(s) RequestUpload405
• 6.9.4 TransferData (3616) service406
• 6.9.4.1 Service description406
• 6.9.4.2 Request message406
• 6.9.4.3 Positive response message407
• 6.9.4.4 Supported negative response codes (NRC_)408
• 6.9.4.5 Message flow example(s) TransferData410
• 6.9.5 RequestTransferExit (3716) service410
• 6.9.5.1 Service description410
• 6.9.5.2 Request message411
• 6.9.5.3 Positive response message411
• 6.9.5.4 Supported negative response codes (NRC_)412
• 6.9.5.5 Message flow example(s) for downloading/uploading data413
• 6.9.6 RequestFileTransfer (3816) service421
• 6.9.6.1 Service description421
• 6.9.6.2 Request message421
• 6.9.6.3 Positive response message423
• 6.9.6.4 Supported negative response codes (NRC_)425
• 6.9.6.5 Message flow example(s) RequestFileTransfer427
• 6.10 Security sub-layer definition430
• 6.10.1 General430
• 6.10.1.1 Purpose430
• 6.10.1.2 Security sub-layer description430
• 6.10.1.3 Security sub-layer access432
• 6.10.1.4 General server response behaviour434
• 6.10.2 SecuredDataTransmission (8416) service436
• 6.10.2.1 Service description436
• 6.10.2.2 Request message436
• 6.10.2.3 Positive response message for successful internal message438
• 6.10.2.4 Supported negative response codes (NRC_)441
• 6.10.2.5 Message flow example SecuredDataTransmission441
• 6.11 Non-volatile server memory programming process445
• 6.11.1 General information445
• 6.11.2 Detailed programming sequence450
• application data450
• 6.11.2.2 Preprogramming step of phase #2 - Server configuration458
• 6.11.2.3 Programming step of phase #2 - Final server configuration459
• 6.11.3 Server reprogramming requirements461
• 6.11.3.1 Requirements for servers to support programming461
• 6.11.3.2 Software, data identification and fingerprints466
• 6.11.3.3 Server routine access466
• 6.11.4 Non-volatile server memory programming message flow examples467
• 6.11.4.1 General information467
• 6.11.4.2 Programming phase #1 - Pre-Programming step467
• 6.11.4.3 Programming phase #1 - Programming step468
• 6.11.5 Programming phase #1 - Post-Programming step472
• 7 Session layer services472
• 7.1 Document overview472
• 7.2 Service content473
• 7.2.1 General473
• 7.2.2 Specification of session layer service primitives476
• 7.2.2.1 General476
• 7.2.2.2 S_Data.request476
• 7.2.2.3 S_Data.confirm476
• 7.2.2.4 S_Data.indication477
• 7.2.3 Session data unit specification477
• 7.2.3.1 S_Mtype, Session layer message type477
• 7.2.3.2 S_SA, Session layer source address477
• 7.2.3.3 S_TA, Session layer target address478
• 7.2.3.4 S_TAtype, Session layer target address type478
• 7.2.3.5 S_AE, Session layer Address Extension (optional parameter)478
• 7.2.3.6 S_Length478
• 7.2.3.7 S_Data479
• 7.2.3.8 S_Result479
• 7.3 Timing parameter definition480
• 7.3.1 General application timing considerations480
• 7.3.1.1 Server480
• 7.3.1.2 Client481
• 7.3.2 Application timing parameter definitions - defaultSession481
• 7.3.3 Example for P4Server without enhanced response timing485
• 7.3.4 Example for P4Server with enhanced response timing486
• 7.3.5 Session timing parameter definitions for the non-default session488
• 7.3.6 Client and server timer resource requirements490
• 7.3.7 Error handling490
• 7.4 Timing handling during communication492
• 7.4.1 Physical communication492
• 7.4.1.1 Physical communication during defaultSession - without SOM.ind492
• 7.4.1.2 Physical communication during defaultSession - with SOM.ind492
• timing493
• 7.4.1.4 Physical communication during a non-default session495
• 7.4.2 Functional communication503
• 7.4.2.1 Functional communication during defaultSession - without SOM.ind503
• 7.4.2.2 Functional communication during defaultSession - with SOM.ind504
• timing - with SOM.ind505
• 7.4.2.4 Functional communication during non-default session - with SOM.ind507
• 7.4.3 Minimum time between client request messages512
• 8 UDSonCAN520
• 8.1 Document overview520
• 8.2 Unified diagnostic services implementation on CAN522
• 8.2.1 General522
• 8.2.2 UDS on CAN services overview522
• 8.2.3 ResponseOnEvent (8616) service DoCAN implementation requirements523
• 8.2.4 ReadDataByPeriodicIdentifier (2A16) service525
• 8.2.4.1 Periodic transmission response message525
• 8.2.4.2 Periodic transmission response message handling526
• 8.2.4.3 CAN frame format527
• 8.3 Application layer requirements532
• 8.3.1 Application layer services532
• 8.3.2 Application layer protocol533
• 8.3.3 Application layer timing533
• 8.3.3.1 General533
• 8.3.3.2 Message timing parameter values533
• 8.3.3.3 Unsolicited response messages533
• 8.4 Presentation layer requirements533
• 8.5 Session layer requirements533
• 8.6 Transport/Network layer interface adaptation533
• 8.6.1 General information533
• 8.6.2 DoCAN Transport/Network layer interface adaptation534
• dependent service primitives534
• 8.6.2.2 Mapping of T_PDU onto N_PDU for message transmission534
• 8.7 Data link layer diagnostic implementation requirements535
• 8.7.1 Usage of legislated 11-bit OBD CAN Identifiers for enhanced diagnostics535
• 8.7.2 Usage of legislated 29-bit OBD CAN Identifiers for enhanced diagnostics535
• 9 UDSonFR536
• 9.1 Document overview536
• 9.2 Unified diagnostic services implementation on FlexRay538
• 9.2.1 General538
• 9.2.2 UDS on FlexRay services overview538
• 9.2.3 CommunicationControl (2816) service539
• 9.2.4 ResponseOnEvent (8616) service540
• 9.2.5 LinkControl (8716) service542
• 9.2.6 ReadDataByPeriodicIdentifier (2A16) service543
• 9.2.6.1 Periodic transmission response message543
• 9.2.6.2 Periodic transmission response message handling544
• 9.2.6.3 Periodic transmission message flow546
• 9.3 Application layer requirements550
• 9.3.1 Application layer services550
• 9.3.2 Application layer protocol551
• 9.3.3 Application layer timing551
• 9.4 Presentation layer requirements551
• 9.5 Session layer requirements551
• 9.6 Transport/Network layer interface adaptation551
• 9.6.1 General information551
• 9.6.2 DoFR Transport/Network layer interface adaptation551
• dependent service primitives551
• 9.6.2.2 Mapping of T_PDU onto C_PDU for message transmission552
• 9.7 Data Link layer diagnostic implementation requirements552
• 10 UDSonIP553
• 10.1 Document overview553
• 10.2 Unified diagnostic services implementation on Internet Protocol555
• 10.2.1 General555
• 10.2.2 UDS on IP services overview555
• 10.2.3 DiagnosticSessionControl (1016) service556
• 10.2.4 ECUReset (1116) service556
• 10.2.5.1 Periodic data response message557
• 10.2.5.2 Periodic transmission response message handling557
• 10.3 Application layer requirements565
• 10.3.1 Application layer services565
• 10.3.2 Application layer protocol565
• 10.3.3 Application layer timing565
• 10.4 Presentation layer requirements565
• 10.5 Session layer requirements565
• 10.6 Transport/network layer interface adaptation565
• 10.6.1 General information565
• 10.6.2 DoIP transport/network layer interface adaptation566
• dependent service primitives566
• 10.6.2.2 Mapping of T_PDU onto DoIP_PDU for message transmission566
• 10.7 Data link layer diagnostic implementation requirements567
• 11 UDSonK-Line567
• 11.1 Document overview567
• 11.2 Unified diagnostic services implementation on K-Line569
• 11.2.1 General569
• 11.2.2 UDSonK-Line services overview569
• 11.2.3 Diagnostic and communication control functional unit570
• 11.2.3.1 AccessTimingParameter (8316) service570
• 11.2.3.2 LinkControl (8716) service571
• 11.2.4 Data transmission functional unit572
• 11.3 Application layer requirements572
• 11.3.1 Application layer services572
• 11.3.2 Application layer protocol572
• 11.3.3 Application layer timing572
• 11.3.3.1 General572
• 11.3.3.2 Application layer timing parameter values572
• 11.4 Presentation layer requirements572
• 11.5 Session layer requirements572
• 11.6 Transport/network layer interface adaptation573
• 11.6.1 General information573
• 11.6.2 DoK-Line transport/network layer interface adaptation573
• dependent service primitives573
• 11.6.2.2 Mapping of T_PDU onto DL_PDU for message transmission573
• 11.7 Data link layer diagnostic implementation requirements574
• 11.7.1 General information574
• 11.7.2 Data segmentation574
• 11.7.3 Session handling574
• 11.7.4 Timings575
• 11.7.5 Protocol initialization, start and stop of communication575
• 11.7.6 Error handling576
• 11.8 Non-volatile server memory programming process576
• 12 UDSonLIN576
• 12.1 Document overview576
• 12.2 UDSonLIN implementation requirements578
• 12.2.1 General578
• 12.2.2 Definition of diagnostic classes578
• 12.2.2.1 Overview578
• 12.2.2.2 Diagnostic class I578
• 12.2.2.3 Diagnostic class II578
• 12.2.2.4 Diagnostic class III578
• 12.2.3 LIN node requirements579
• 12.2.3.1 Master node requirements579
• 12.2.3.2 Slave node requirements580
• 12.2.4 Signal-based diagnostics580
• 12.2.4.1 Slave implementation580
• 12.2.4.2 Master implementation581
• 12.2.5 Tool suite support581
• 12.3 UDSonLIN implementation581
• 12.3.1 UDSonLIN services overview581
• 12.3.2 Diagnostic and communication control functional unit582
• 12.3.2.1 CommunicationControl (2816) service582
• 12.3.2.2 ResponseOnEvent (8616) service583
• 12.4 Application layer requirements583
• 12.4.1 Application layer services583
• 12.4.2 Application layer protocol583
• 12.4.3 Application layer timing584
• 12.4.3.1 General584
• 12.4.3.2 Application layer timing parameter values584
• 12.5 Presentation layer requirements586
• 12.6 Session layer requirements586
• 12.7 Transport/network layer interface adaptation586
• 12.7.1 General information586
• 12.7.2 LIN transport/network layer interface adaptation586
• dependent service primitives586
• 12.7.2.2 Mapping of T_PDU onto N_PDU for message transmission586
• 12.8 Network layer diagnostic implementation requirements587
• 12.8.1 LIN slave node network layer requirements587
• 12.8.2 LIN master node network layer requirements588
• 12.8.2.1 Network address requirements588
• 12.8.2.2 Use of functional addressing589
• 12.9 Data link layer diagnostic implementation requirements589
• 13 UDSonCXPI589
• 13.1 Document overview589
• 13.2 UDSonCXPI implementation requirements590
• 13.3 SIP - Service interface parameters591
• 13.3.1 SIP - General591
• 13.3.2 SIP - Data type definitions591
• 13.3.3 SIP - A_Mtype, message type591
• 13.3.4 SIP - A_TAtype, target address type591
• 13.3.5 SIP - A_TA, target address592
• 13.3.6 SIP - A_SA, source address592
• 13.3.7 SIP - A_Length, length of A_PDU592
• 13.3.8 SIP - A_Data, protocol data unit592
• 13.3.9 SIP - A_SCT, sequence count592
• 13.3.10 SIP - A_Result, result593
• 13.3.11 SIP - ev_wakeup_ind, event wake-up indication (optional)593
• 13.3.12 SIP - cmd_wakeup_req, command wake-up request593
• 13.3.13 SIP - NMInfo, network management information594
• 13.4 APP - Application594
• 13.4.1 APP - General594
• 13.4.2 APP - Definition of diagnostic classes595
• 13.4.2.1 APP - Overview595
• 13.4.2.2 APP - Diagnostic class I595
• 13.4.2.3 APP - Diagnostic class II595
• 13.4.2.4 APP - Diagnostic class III595
• reading, I/O control596
• 13.4.4 APP - CXPI slave node requirements596
• 13.4.4.1 APP - General596
• 13.4.4.2 APP - Error indications596
• 13.4.5 APP - CXPI measurement and control data diagnostics597
• 13.4.5.2 APP - Slave node current failure status support597
• 13.4.6 APP - Network management (optional)598
• 13.4.7 APP - CXPI master node gateway application598
• 13.4.7.1 APP - General598
• 13.4.7.2 APP - CXPI master gateway number of subnets598
• 13.4.7.3 APP - CXPI master gateway address routing table598
• 13.4.7.4 APP - CXPI master gateway all nodes request message handling598
• 13.4.7.5 APP - Round trip of all node addressing with functional NAD599
• 13.4.7.6 APP - Round trip of all node addressing with node-specific NADs599
• 13.5 AL - Application layer600
• 13.5.1 AL - Client to CXPI slave node(s) communication600
• 13.5.3 AL - CommunicationControl (2816) service602
• 13.5.4 AL - UDSonCXPI services603
• 13.5.4.1 AL - Supported functions603
• 13.5.4.2 AL - Master node receive buffer length603
• 13.5.4.3 AL - Message length is exceeded604
• 13.5.5 AL - Protocol604
• 13.5.6 AL - Timing604
• 13.5.6.1 AL - General604
• 13.5.6.2 AL - Timing parameter values604
• 13.5.6.3 AL - Server timing performance requirements604
• 13.5.6.4 AL - SuppressPosRspMsgIndicationBit604
• 13.5.7 AL - Response pending605
• 13.5.8 AL - CXPI slave node configuration services605
• 13.5.8.1 AL - CXPI node configuration605
• 13.5.8.2 AL - Slave node model606
• 13.5.8.3 AL - WriteDataByIdentifier - AssignNodeAddress610
• 13.5.8.4 AL - WriteDataByIdentifier - NodeDataDump612
• 13.5.8.5 AL - ReadDataByIdentifier - NodeProductIdentification613
• 13.5.8.6 AL - ReadDataByIdentifier - NodeSerialNumberIdentification614
• 13.5.8.7 AL - ReadDataByIdentifier - NodeConfigurationFileAvailability615
• 13.5.8.8 AL - WriteDataByIdentifier - SaveConfiguration617
• 13.5.8.9 AL - WriteDataByIdentifier - AssignFrameIdentifierRange618
• 13.6 PL - Presentation layer620
• 13.7 SL - Session layer620
• 13.7.1 SL - General620
• 13.7.2 SL - A_Data and T_Data service interface parameter mapping620
• 13.8 TL - Transport layer620
• 13.8.1 TL - Service primitive interface adaptation - General information620
• 13.8.2 TL - CXPI transport layer interface adaptation621
• 13.8.2.1 TL - Mapping of session layer to transport layer service primitives621
• 13.8.2.2 TL - Mapping of T_Data service primitive interface parameters621
• 13.9 NL - Network layer622
• 13.9.1 NL - Service primitive interface adaptation622
• 13.9.1.1 NL - General information622
• 13.9.1.2 NL - CXPI network layer interface adaptation622
• 13.9.2 NL - CXPI master node623
• 13.9.2.1 NL - Network layer623
• 13.9.2.2 NL - Dynamic NAD assignment623
• 13.9.2.3 NL - NodeIdentificationNumber623
• 13.9.3 NL - Master message routing623
• 13.9.3.1 NL - General623
• 13.9.3.2 NL - Diagnostic request message routing624
• 13.9.3.3 NL - Diagnostic response message routing624
• 13.9.3.4 NL - Master node transport protocol support624
• 13.9.4 NL - CXPI slave node624
• 13.9.4.1 NL - General624