TABLE-1001379436P1000001RDDM11-0001 Table Table 1: Definition of terms Image available: no 1001379436_P10_000_01_RDDM-1140152501-1744.pdf 1001379436_P10_000_01_RDDM-1140152501-1744 page 3 1.3 High Table 1: Definition of terms Artifact ID TABLE-1001379436P1000001RDDM11-0001
Section 1001379436_P10_000_01_RDDM-1140152501-1744
Why it matters Table source context
View details Table 1: Definition of terms
Wide tables scroll horizontally inside this card.
Term Definition Shall This word, or the term "Required", means that the definition is an absolute requirement of the specification. Threat Analysis and A structured approach to identify possible threats and evaluate risks with respect to the potential Risk Assessment damages and the effort needed for successful attack. A cybersecurity concept is a work product that documents cybersecurity relevant aspects of the Cybersecurity concept product. The cybersecurity concept shall describe the scope of the risk analysis, risks that were identified during the risk analysis, cybersecurity goals, cybersecurity requirements, mitigation strategies, validation, and verification strategies, etc.
TABLE-1001379436P1000001RDDM11-0002 Table Table 2: Abbreviated terms Image available: no 1001379436_P10_000_01_RDDM-1140152501-1744.pdf 1001379436_P10_000_01_RDDM-1140152501-1744 page 3 1.4; INFO_SEC_001; REQ_SEC_0001 ; REQ_SEC_0002 High Table 2: Abbreviated terms Artifact ID TABLE-1001379436P1000001RDDM11-0002
Section 1001379436_P10_000_01_RDDM-1140152501-1744
Why it matters Security protocol or cryptographic context
View details Table 2: Abbreviated terms
Wide tables scroll horizontally inside this card.
Abbreviation Description ECU Electronic Control Unit
TABLE-1001379436P1000001RDDM11-0003 Table Table 3: Bibliography Image available: no 1001379436_P10_000_01_RDDM-1140152501-1744.pdf 1001379436_P10_000_01_RDDM-1140152501-1744 page 15 None Low Table 3: Bibliography Artifact ID TABLE-1001379436P1000001RDDM11-0003
Section 1001379436_P10_000_01_RDDM-1140152501-1744
Why it matters Table source context
View details Table 3: Bibliography
Wide tables scroll horizontally inside this card.
ID1 Name Scania/MAN Unified Version Content [1] Diagnostic Services – Security access mechanisms 1.0, 2018-04-18 Scania/MAN Unified Diagnostic Services – Security access mechanisms
TABLE-1001379436P1000001RDDM11-0004 Table Table 4: History of the document Image available: no 1001379436_P10_000_01_RDDM-1140152501-1744.pdf 1001379436_P10_000_01_RDDM-1140152501-1744 page 16 None Low Table 4: History of the document Artifact ID TABLE-1001379436P1000001RDDM11-0004
Section 1001379436_P10_000_01_RDDM-1140152501-1744
Why it matters Table source context
View details Table 4: History of the document
Wide tables scroll horizontally inside this card.
Version Date Editor Notes 1.0 2021-06-02 mxxm36 Initial version. As close as possible to the last Excel sheet version of the requirements 2.0 2021-06-30 mxxm36 Added new requirements and adjusted old requirements. More clarifications and cosmetics.
TABLE-CVS1232-0001 Table Table 1: Definition of terms Image available: no CVS123-2.pdf 3.1 page 6 REQ_UDS_0051 ; SUV2_INFO 13High Table 1: Definition of terms Artifact ID TABLE-CVS1232-0001
Section 3.1 Definitions of terms
Why it matters Diagnostic parameter or service behavior
View details Table 1: Definition of terms
Wide tables scroll horizontally inside this card.
Term Definition Adaptive data A data set that controls the system behaviour depending on the installation environment. Contains a variant-specific set of parameter values that is required for correct Application data operation of the control unit in a specific vehicle variant. module It must be clearly separated from the application software. For this reason, it is (Calibration data) located in a separate memory area and must also be erasable and programmable independently of the application software. Application software Contains all vehicle functions required for the normal server operation. If valid module Application software is programmed, the server will activate the application software after the start-up phase by starting the operating system. The application software is programmable by an external programming tool. Boot loader Equivalent with reprogramming software in (1) Contains the boot software which is used for the booting and reprogramming of the Boot software ECU via diagnostic protocol (e.g., UDS on CAN). The software is located in a
View full table (14 rows) Term Definition Adaptive data A data set that controls the system behaviour depending on the installation environment. Contains a variant-specific set of parameter values that is required for correct Application data operation of the control unit in a specific vehicle variant. module It must be clearly separated from the application software. For this reason, it is (Calibration data) located in a separate memory area and must also be erasable and programmable independently of the application software. Application software Contains all vehicle functions required for the normal server operation. If valid module Application software is programmed, the server will activate the application software after the start-up phase by starting the operating system. The application software is programmable by an external programming tool. Boot loader Equivalent with reprogramming software in (1) Contains the boot software which is used for the booting and reprogramming of the Boot software ECU via diagnostic protocol (e.g., UDS on CAN). The software is located in a module protected area of the ECU flash memory. All software parts required for the reprogramming like CAN driver, network layer, diagnostic services, boot operating (Boot loader and system, start-up code, low level flash routines (for erasing, writing, reading), Boot manager) EEPROM access routines (read, write functionality), software compatibility checks etc. shall be implemented in the boot software code. Also referred to as “application valid” flag. Variable holding information about whether or not the software modules installed on the ECU are consistent and executable. C1 The value of this variable (and C2, see below) may be used by the boot manager to determine whether to start the application or the boot loader. More information on CVS124 REQ_UDS 0051 Also referred to as “programming request” flag. Variable holding information about whether or not there is a pending programming request from client. C2 The value of this variable (and C1, see above) may be used by the boot manager to determine whether or not to start the application or the boot loader. More information on CVS124 REQ_UDS 0051 Also referred to as “reprogrammed” flag. Variable holding information about whether or not the ECU has been C3 reprogrammed after the application was used the last time. The value of this variable may be used by the application to determine whether or not initialization is required.
TABLE-CVS1232-0002 Table Table 2: Abbreviated terms Image available: no CVS123-2.pdf 3.2 page 7 RFQX-CVS123-2-0031 High Table 2: Abbreviated terms Artifact ID TABLE-CVS1232-0002
Section 3.2 Abbreviated terms
Related requirements RFQX-CVS123-2-0031
Why it matters Diagnostic parameter or service behavior
View details Table 2: Abbreviated terms
Wide tables scroll horizontally inside this card.
Term Definition Component of the software to be installed which identity (e.g., part number and Module version) can be obtained via UDS service ReadDataByIdentifier, e.g., boot loader, application software, application data. Data collected or calculated during the operation of an ECU, used to obtain an Operational data understanding of the product’s current condition or of how the product has been used. Satisfied A programming precondition agreed between supplier and vehicle manufacturer programming which, together with other agreed programming preconditions, shall be fulfilled precondition before an ECU is made eligible for programming. Server Function that is part of an electronic control unit and that provides the diagnostic services defined in (1) Standalone (server) Server which is not yet connected to the vehicle network SW area An allocation in memory with start and end address to which a software module is allocated. System that controls functions such as test, inspection, monitoring, or diagnosis of
View full table (9 rows) Term Definition Component of the software to be installed which identity (e.g., part number and Module version) can be obtained via UDS service ReadDataByIdentifier, e.g., boot loader, application software, application data. Data collected or calculated during the operation of an ECU, used to obtain an Operational data understanding of the product’s current condition or of how the product has been used. Satisfied A programming precondition agreed between supplier and vehicle manufacturer programming which, together with other agreed programming preconditions, shall be fulfilled precondition before an ECU is made eligible for programming. Server Function that is part of an electronic control unit and that provides the diagnostic services defined in (1) Standalone (server) Server which is not yet connected to the vehicle network SW area An allocation in memory with start and end address to which a software module is allocated. System that controls functions such as test, inspection, monitoring, or diagnosis of Tester an on-vehicle electronic control unit and may 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) see (1)
TABLE-CVS1232-0003 Table Table 3: Services support due to SUV2 Image available: no CVS123-2.pdf 6.1.1.2 page 23 SUV2_REQ 52; SUV2_REQ 55; SUV2_REQ 62; SUV2_INFO 106; SUV2_REQ 63; SUV2_REQ 53; SUV2_REQ 54; SUV2_INFO 104 High Table 3: Services support due to SUV2 Artifact ID TABLE-CVS1232-0003
Section 6.1.1.2 Boot software session requirements
Related requirements SUV2_REQ 52; SUV2_REQ 55; SUV2_REQ 62; SUV2_INFO 106; SUV2_REQ 63; SUV2_REQ 53; SUV2_REQ 54; SUV2_INFO 104
Why it matters Diagnostic parameter or service behavior
View details Table 3: Services support due to SUV2
Wide tables scroll horizontally inside this card.
Service according to (1) Addressing mode Application Sessions Def Non-Def Ext Boot loader Sessions Def Non-Def Prg Ext RequestDownload (0x34) P - - - M - TransferData (0x36) P - - - M - RequestTransferExit (0x37) P - - - M - SecuredDataTranmission (0x84) P M M M M M
TABLE-CVS1232-0004 Table Table 4: Routine identifiers for non-volatile memory access Image available: no CVS123-2.pdf 6.1.1.4.1 page 24 SUV2_REQ 64; SUV2_REQ 65; SUV2_REQ 66; SUV2_INFO 107; SUV2_REQ 63 High Table 4: Routine identifiers for non-volatile memory access Artifact ID TABLE-CVS1232-0004
Section 6.1.1.4.1 Server routine access
Related requirements SUV2_REQ 64; SUV2_REQ 65; SUV2_REQ 66; SUV2_INFO 107; SUV2_REQ 63
Why it matters Diagnostic parameter or service behavior
View details Table 4: Routine identifiers for non-volatile memory access
Wide tables scroll horizontally inside this card.
Byte Description Value 0x2202 checkMemory This routineIdentifier allows the client to start a check routine of the server. 0xCAFE Entity Management Protocol This routineIdentifier enables the client to query/update the cyber security entities. 0xFF00 eraseMemory This routineIdentifier allows the client to start an erase routine of the server. checkProgrammingDependencies 0xFF01 This routineIdentifier allows the client to start a server check routine, in order to check the consistency of the server.
TABLE-CVS1232-0005 Table Table 5: Service 0x34 Request Format Image available: no CVS123-2.pdf 7.1.1 page 25 SUV2_REQ 72; SUV2_INFO 108; SUV2_REQ 71; SUV2_INFO 109; SUV2_REQ 190; SUV2_INFO 150; SUV2_REQ 73 High Table 5: Service 0x34 Request Format Artifact ID TABLE-CVS1232-0005
Related requirements SUV2_REQ 72; SUV2_INFO 108; SUV2_REQ 71; SUV2_INFO 109; SUV2_REQ 190; SUV2_INFO 150; SUV2_REQ 73
Why it matters Software update or memory programming context
View details Table 5: Service 0x34 Request Format
Wide tables scroll horizontally inside this card.
Byte No. Description Cvt Byte Value 1 RequestDownload Request SID M 0x34 2 dataFormatIdentifier M 0x00 – 0xFF 3 addressAndLengthFormatIdentifier memoryAddress byte 1 (MSB) byte 2 M 0x33 or 0x44 4 .. (m- byte 3 M 0x00 – 0xFF 1)+4 byte 4 : User Optional byte 5 : not available .. byte m : not available memorySize byte 1 (MSB) byte 2 n -(k-1) .. byte 3 0x00 – 0xFF n byte 4 :Mandatory if Memory address byte 4 is used byte 5 : not available .. byte m : not available M
TABLE-CVS1232-0006 Table Table 6: Service 0x34 Positive Response Format Image available: no CVS123-2.pdf 7.1.2 page 26 SUV2_REQ 73; SUV2_REQ 74; SUV2_REQ 165; SUV2_REQ 166; SUV2_REQ 167; SUV2_INFO 137; SUV2_REQ 75 High Table 6: Service 0x34 Positive Response Format Artifact ID TABLE-CVS1232-0006
Section 7.1.2 Positive Response
Related requirements SUV2_REQ 73; SUV2_REQ 74; SUV2_REQ 165; SUV2_REQ 166; SUV2_REQ 167; SUV2_INFO 137; SUV2_REQ 75
Why it matters Software update or memory programming context
View details Table 6: Service 0x34 Positive Response Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier maxNumberOfBlockLength[] = [ M 0x20 0x0000 – #3.. #4 byte #1 (MSB) byte #2 ] M 0xFFFF
TABLE-CVS1232-0007 Table Table 7: Service 0x34 dataFormatIdentifier Format Image available: no CVS123-2.pdf 7.1.4.1 page 26 SUV2_REQ 75; SUV2_REQ 165; SUV2_REQ 166; SUV2_REQ 167; SUV2_INFO 137; SUV2_REQ 77; SUV2_REQ 76 High Table 7: Service 0x34 dataFormatIdentifier Format Artifact ID TABLE-CVS1232-0007
Section 7.1.4.1 Parameter dataFormatIdentifier
Related requirements SUV2_REQ 75; SUV2_REQ 165; SUV2_REQ 166; SUV2_REQ 167; SUV2_INFO 137; SUV2_REQ 77; SUV2_REQ 76
Why it matters Table source context
View details Table 7: Service 0x34 dataFormatIdentifier Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier maxNumberOfBlockLength[] = [ M 0x20 0x0000 – #3.. #4 byte #1 (MSB) byte #2 ] M 0xFFFF
TABLE-CVS1232-0008 Table Table 8: Service 0x34 addressAndLengthFormatIdentifier Format Image available: no CVS123-2.pdf 7.1.4.2 page 27 SUV2_REQ 77; SUV2_REQ 76; SUV2_REQ 78; SUV2_REQ 79 High Table 8: Service 0x34 addressAndLengthFormatIdentifier Format Artifact ID TABLE-CVS1232-0008
Section 7.1.4.2 Parameter addressAndLengthFormatIdentifier
Related requirements SUV2_REQ 77; SUV2_REQ 76; SUV2_REQ 78; SUV2_REQ 79
Why it matters Software update or memory programming context
View details Table 8: Service 0x34 addressAndLengthFormatIdentifier Format
Wide tables scroll horizontally inside this card.
Bits Description Cvt Values 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4
TABLE-CVS1232-0009 Table Table 9: Service 0x34 lengthFormatIdentifier Format Image available: no CVS123-2.pdf 7.1.4.3 page 27 SUV2_REQ 77; SUV2_REQ 80; SUV2_REQ 76; SUV2_REQ 78; SUV2_REQ 79; SUV2_REQ 81; SUV2_REQ 82 High Table 9: Service 0x34 lengthFormatIdentifier Format Artifact ID TABLE-CVS1232-0009
Section 7.1.4.3 Parameter lengthFormatIdentifier
Related requirements SUV2_REQ 77; SUV2_REQ 80; SUV2_REQ 76; SUV2_REQ 78; SUV2_REQ 79; SUV2_REQ 81; SUV2_REQ 82
Why it matters Table source context
View details Table 9: Service 0x34 lengthFormatIdentifier Format
Wide tables scroll horizontally inside this card.
Bits Description Cvt Values 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4
TABLE-CVS1232-0010 Table Table 10: Service 0x37 Request Format Image available: no CVS123-2.pdf 7.3.1 page 28 SUV2_REQ 86; SUV2_REQ 83; SUV2_REQ 84; SUV2_REQ 85; SUV2_REQ 87; SUV2_REQ 88 High Table 10: Service 0x37 Request Format Artifact ID TABLE-CVS1232-0010
Related requirements SUV2_REQ 86; SUV2_REQ 83; SUV2_REQ 84; SUV2_REQ 85; SUV2_REQ 87; SUV2_REQ 88
Why it matters Table source context
View details Table 10: Service 0x37 Request Format
Wide tables scroll horizontally inside this card.
Byte No Description Cvt Byte Value 1 RequestTransferExit Request SID M 0x37
TABLE-CVS1232-0011 Table Table 11: Service 0x37 Positive Response Format Image available: no CVS123-2.pdf 7.3.2 page 28 SUV2_REQ 86; SUV2_REQ 83; SUV2_REQ 84; SUV2_REQ 85; SUV2_REQ 87; SUV2_REQ 88; SUV2_REQ 89; SUV2_REQ 90 High Table 11: Service 0x37 Positive Response Format Artifact ID TABLE-CVS1232-0011
Section 7.3.2 Positive Response
Related requirements SUV2_REQ 86; SUV2_REQ 83; SUV2_REQ 84; SUV2_REQ 85; SUV2_REQ 87; SUV2_REQ 88; SUV2_REQ 89; SUV2_REQ 90
Why it matters Table source context
View details Table 11: Service 0x37 Positive Response Format
Wide tables scroll horizontally inside this card.
Byte No Description Cvt Byte Value 1 RequestTransferExit Request SID M 0x37
TABLE-CVS1232-0012 Table Table 12: Routine Support per Diagnostic Session Image available: no CVS123-2.pdf 8.1.1 page 29 SUV2_REQ 97; SUV2_REQ 94; SUV2_REQ 95; SUV2_REQ 96; SUV2_REQ 98 High Table 12: Routine Support per Diagnostic Session Artifact ID TABLE-CVS1232-0012
Section 8.1.1 Routine Session Support
Related requirements SUV2_REQ 97; SUV2_REQ 94; SUV2_REQ 95; SUV2_REQ 96; SUV2_REQ 98
Why it matters Diagnostic parameter or service behavior
View details Table 12: Routine Support per Diagnostic Session
Wide tables scroll horizontally inside this card.
RID Name Application Sessions Def Non-Def Ext Boot Sessions Def loader Non-Def Prg Ext 0x2202 Check Memory Block - - - M - 0xFF00 EraseMemory - - - M - 0xFF01 CheckProgrammingDependencies - M - M M 0xCAFE Entity Management Protocol (EMP) M M M M M
TABLE-CVS1232-0013 Table Table 13: Routine Support per routineControlType Image available: no CVS123-2.pdf 8.1.2 page 30 SUV2_REQ 181; SUV2_INFO 110; SUV2_REQ 98; SUV2_REQ 99 High Table 13: Routine Support per routineControlType Artifact ID TABLE-CVS1232-0013
Section 8.1.2 Routine routineControlType Support
Related requirements SUV2_REQ 181; SUV2_INFO 110; SUV2_REQ 98; SUV2_REQ 99
Why it matters Diagnostic parameter or service behavior
View details Table 13: Routine Support per routineControlType
Wide tables scroll horizontally inside this card.
RID Name startRoutine (0x01) routineControlType stopRoutine (0x02) requestRoutineResults (0x03) 0x2202 Check Memory Block M - - 0xFF00 EraseMemory M - - 0xFF01 CheckProgrammingDependencies M - - 0xCAFE Entity Management Protocol (EMP) M - -
TABLE-CVS1232-0014 Table Table 14: Routine support for Safe State Conditions Image available: no CVS123-2.pdf 8.1.3 page 30 SUV2_INFO 110; SUV2_REQ 181; SUV2_REQ 99; SUV2_REQ 100; SUV2_REQ 101 High Table 14: Routine support for Safe State Conditions Artifact ID TABLE-CVS1232-0014
Section 8.1.3 Routine Safe State Requirement
Related requirements SUV2_INFO 110; SUV2_REQ 181; SUV2_REQ 99; SUV2_REQ 100; SUV2_REQ 101
Why it matters Diagnostic parameter or service behavior
View details Table 14: Routine support for Safe State Conditions
Wide tables scroll horizontally inside this card.
RID Name startRoutine (0x01) routineControlType stopRoutine (0x02) requestRoutineResults (0x03) 0x2202 Check Memory Block M - - 0xFF00 EraseMemory M - - 0xFF01 CheckProgrammingDependencies M - - 0xCAFE Entity Management Protocol (EMP) M - -
TABLE-CVS1232-0015 Table Table 15: Routine 0x2202 Request Format Image available: no CVS123-2.pdf 8.2.1 page 31 SUV2_REQ 103; SUV2_REQ 104; SUV2_REQ 102; SUV2_INFO 111 High Table 15: Routine 0x2202 Request Format Artifact ID TABLE-CVS1232-0015
Related requirements SUV2_REQ 103; SUV2_REQ 104; SUV2_REQ 102; SUV2_INFO 111
Why it matters Diagnostic parameter or service behavior
View details Table 15: Routine 0x2202 Request Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0x22 #4 routineIdentifier (LSB) M 0x02
TABLE-CVS1232-0016 Table Table 16: Routine 0x2202 Positive Response Format Image available: no CVS123-2.pdf 8.2.2 page 31 SUV2_REQ 104; SUV2_REQ 103; SUV2_REQ 102; SUV2_REQ 105 High Table 16: Routine 0x2202 Positive Response Format Artifact ID TABLE-CVS1232-0016
Section 8.2.2 Positive Response
Related requirements SUV2_REQ 104; SUV2_REQ 103; SUV2_REQ 102; SUV2_REQ 105
Why it matters Diagnostic parameter or service behavior
View details Table 16: Routine 0x2202 Positive Response Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0x22 #4 routineIdentifier (LSB) M 0x02
TABLE-CVS1232-0017 Table Table 17: Routine 0x2202 routineStatus routineResult Format Image available: no CVS123-2.pdf 8.2.4.1 page 32 SUV2_INFO 112; SUV2_REQ 104; SUV2_INFO 114; SUV2_REQ 105; SUV2_REQ 106; SUV2_INFO 113; SUV2_REQ 107; SUV2_REQ 4 High Table 17: Routine 0x2202 routineStatus routineResult Format Artifact ID TABLE-CVS1232-0017
Section 8.2.4.1 Parameter routineStatus routineResult
Related requirements SUV2_INFO 112; SUV2_REQ 104; SUV2_INFO 114; SUV2_REQ 105; SUV2_REQ 106; SUV2_INFO 113; SUV2_REQ 107; SUV2_REQ 4
Why it matters Diagnostic parameter or service behavior
View details Table 17: Routine 0x2202 routineStatus routineResult Format
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x00 correctResult M 0x01 incorrectResult M
TABLE-CVS1232-0018 Table Table 18: Routine 0xFF00 Request Format Image available: no CVS123-2.pdf 8.3.1 page 33 SUV2_REQ 110; SUV2_REQ 111; SUV2_REQ 109 High Table 18: Routine 0xFF00 Request Format Artifact ID TABLE-CVS1232-0018
Section 8.3.1 Routine Request
Related requirements SUV2_REQ 110; SUV2_REQ 111; SUV2_REQ 109
Why it matters Diagnostic parameter or service behavior
View details Table 18: Routine 0xFF00 Request Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) addressAndLengthFormatIdentifier (XXXXYYYYb) M 0x00 #5 XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. M 0x00 – 0xFF #6 memoryStartAddress[] = [ : byte#1 (MSB) C1 0x00 – 0xFF #(m-1)+6 : byte#m ] : C1 : 0x00 – 0xFF
View full table (11 rows) Byte Description Cvt Byte Value #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) addressAndLengthFormatIdentifier (XXXXYYYYb) M 0x00 #5 XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. M 0x00 – 0xFF #6 memoryStartAddress[] = [ : byte#1 (MSB) C1 0x00 – 0xFF #(m-1)+6 : byte#m ] : C1 : 0x00 – 0xFF #n-(k-1) memorySize[] = [ : byte#1 (MSB) C2 0x00 – 0xFF #n : byte#k ] : C2 : 0x00 – 0xFF
TABLE-CVS1232-0019 Table Table 19: Routine 0xFF00 Positive Response Format Image available: no CVS123-2.pdf 8.3.2 page 33 SUV2_REQ 111; SUV2_REQ 112; SUV2_REQ 113 High Table 19: Routine 0xFF00 Positive Response Format Artifact ID TABLE-CVS1232-0019
Section 8.3.2 Routine Positive Response
Related requirements SUV2_REQ 111; SUV2_REQ 112; SUV2_REQ 113
Why it matters Diagnostic parameter or service behavior
View details Table 19: Routine 0xFF00 Positive Response Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) addressAndLengthFormatIdentifier (XXXXYYYYb) M 0x00 #5 XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. M 0x00 – 0xFF #6 memoryStartAddress[] = [ : byte#1 (MSB) C1 0x00 – 0xFF #(m-1)+6 : byte#m ] : C1 : 0x00 – 0xFF
View full table (11 rows) Byte Description Cvt Byte Value #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) addressAndLengthFormatIdentifier (XXXXYYYYb) M 0x00 #5 XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. M 0x00 – 0xFF #6 memoryStartAddress[] = [ : byte#1 (MSB) C1 0x00 – 0xFF #(m-1)+6 : byte#m ] : C1 : 0x00 – 0xFF #n-(k-1) memorySize[] = [ : byte#1 (MSB) C2 0x00 – 0xFF #n : byte#k ] : C2 : 0x00 – 0xFF
TABLE-CVS1232-0020 Table Table 20: Routine 0xFF00 addressAndLengthFormatIdentifier Format Image available: no CVS123-2.pdf 8.3.4.1 page 34 SUV2_REQ 62; SUV2_REQ 112; SUV2_REQ 114; SUV2_REQ 113; SUV2_REQ 63; SUV2_REQ 115 High Table 20: Routine 0xFF00 addressAndLengthFormatIdentifier Format Artifact ID TABLE-CVS1232-0020
Section 8.3.4.1 Parameter addressAndLengthFormatIdentifier
Related requirements SUV2_REQ 62; SUV2_REQ 112; SUV2_REQ 114; SUV2_REQ 113; SUV2_REQ 63; SUV2_REQ 115
Why it matters Diagnostic parameter or service behavior
View details Table 20: Routine 0xFF00 addressAndLengthFormatIdentifier Format
Wide tables scroll horizontally inside this card.
Byte Value Description Cvt 0x00 Automatic erase: Erase is performed by boot loader automatically when C RequestDownload is received for each Flash sector in the module. Module erase: memoryStartAddress byte is used for module index. 0x01 memorySize parameter is not used. M E.g., 02, Module 2 (Application SW module) 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M
TABLE-CVS1232-0021 Table Table 21: Module to Index Mapping Image available: no CVS123-2.pdf 8.3.4.1 page 34 SUV2_REQ 62; SUV2_REQ 114; SUV2_REQ 63; SUV2_REQ 115 High Table 21: Module to Index Mapping Artifact ID TABLE-CVS1232-0021
Section 8.3.4.1 Parameter addressAndLengthFormatIdentifier
Related requirements SUV2_REQ 62; SUV2_REQ 114; SUV2_REQ 63; SUV2_REQ 115
Why it matters State-machine or transition behavior
View details Table 21: Module to Index Mapping
Wide tables scroll horizontally inside this card.
Hex Description When addressAndLengthFormatIdentifier = 0x00: Cvt 0x00 Erasing will be initiated when RequestDownload service is requested. When addressAndLengthFormatIdentifier > 0x00: Erase operation was completed successfully. M 0x01 Erase operation was unsuccessful. M
TABLE-CVS1232-0022 Table Table 22: Routine 0xFF00 routineStatus routineResult Format Image available: no CVS123-2.pdf 8.3.4.2 page 34 SUV2_REQ 114; SUV2_REQ 62; SUV2_REQ 63; SUV2_REQ 115; SUV2_INFO 115; SUV2_REQ 143; SUV2_INFO 124; SUV2_REQ 116 High Table 22: Routine 0xFF00 routineStatus routineResult Format Artifact ID TABLE-CVS1232-0022
Section 8.3.4.2 Paramter routineStatus routineResult
Related requirements SUV2_REQ 114; SUV2_REQ 62; SUV2_REQ 63; SUV2_REQ 115; SUV2_INFO 115; SUV2_REQ 143; SUV2_INFO 124; SUV2_REQ 116
Why it matters Diagnostic parameter or service behavior
View details Table 22: Routine 0xFF00 routineStatus routineResult Format
Wide tables scroll horizontally inside this card.
Byte Value Description Cvt 0x00 Automatic erase: Erase is performed by boot loader automatically when C RequestDownload is received for each Flash sector in the module. Module erase: memoryStartAddress byte is used for module index. 0x01 memorySize parameter is not used. M E.g., 02, Module 2 (Application SW module) 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M
TABLE-CVS1232-0023 Table Table 23: Routine 0xFF01 Request Format Image available: no CVS123-2.pdf 8.4.1 page 35 SUV2_REQ 122; SUV2_REQ 117; SUV2_REQ 118; SUV2_REQ 119; SUV2_REQ 120; SUV2_REQ 121; SUV2_INFO 140; SUV2_REQ 124 High Table 23: Routine 0xFF01 Request Format Artifact ID TABLE-CVS1232-0023
Related requirements SUV2_REQ 122; SUV2_REQ 117; SUV2_REQ 118; SUV2_REQ 119; SUV2_REQ 120; SUV2_REQ 121; SUV2_INFO 140; SUV2_REQ 124
Why it matters Diagnostic parameter or service behavior
View details Table 23: Routine 0xFF01 Request Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x01
TABLE-CVS1232-0024 Table Table 24: Routine 0xFF01 Positive Response Format Image available: no CVS123-2.pdf 8.4.2 page 36 SUV2_REQ 123; SUV2_REQ 124; SUV2_REQ 125; SUV2_REQ 126 High Table 24: Routine 0xFF01 Positive Response Format Artifact ID TABLE-CVS1232-0024
Section 8.4.2 Positive Response
Related requirements SUV2_REQ 123; SUV2_REQ 124; SUV2_REQ 125; SUV2_REQ 126
Why it matters Diagnostic parameter or service behavior
View details Table 24: Routine 0xFF01 Positive Response Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingDependencies[byte#1] M 0xFF #4 routineIdentifier (LSB) checkProgrammingDependencies [byte#2] M 0x01 #5 routineStatus routineResult M 0x00-0xFF #6 … #7 routineResultProofLength M Uint16 #8 … #n routineResultProof M Uint8[]
TABLE-CVS1232-0025 Table Table 25: Routine 0xFF01 routineStatus routineResult Format Image available: no CVS123-2.pdf 8.4.4.1 page 36 SUV2_REQ 126; SUV2_REQ 124; SUV2_REQ 125; SUV2_REQ 146; SUV2_REQ 151; SUV2_REQ 169; SUV2_REQ 170; SUV2_INFO 128 High Table 25: Routine 0xFF01 routineStatus routineResult Format Artifact ID TABLE-CVS1232-0025
Section 8.4.4.1 Parameter routineStatus routineResult
Related requirements SUV2_REQ 126; SUV2_REQ 124; SUV2_REQ 125; SUV2_REQ 146; SUV2_REQ 151; SUV2_REQ 169; SUV2_REQ 170; SUV2_INFO 128
Why it matters Diagnostic parameter or service behavior
View details Table 25: Routine 0xFF01 routineStatus routineResult Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingDependencies[byte#1] M 0xFF #4 routineIdentifier (LSB) checkProgrammingDependencies [byte#2] M 0x01 #5 routineStatus routineResult M 0x00-0xFF #6 … #7 routineResultProofLength M Uint16 #8 … #n routineResultProof M Uint8[]
TABLE-CVS1232-0026 Table Table 26: Routine 0xCAFE Request Format Image available: no CVS123-2.pdf 8.5.1 page 39 SUV2_REQ 130; SUV2_REQ 129; SUV2_REQ 132; SUV2_REQ 131; SUV2_REQ 133; SUV2_REQ 178; SUV2_REQ 179; SUV2_REQ 180 High Table 26: Routine 0xCAFE Request Format Artifact ID TABLE-CVS1232-0026
Related requirements SUV2_REQ 130; SUV2_REQ 129; SUV2_REQ 132; SUV2_REQ 131; SUV2_REQ 133; SUV2_REQ 178; SUV2_REQ 179; SUV2_REQ 180
Why it matters Diagnostic parameter or service behavior
View details Table 26: Routine 0xCAFE Request Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xCA #4 routineIdentifier (LSB) M 0xFE #5 … #n EMP Message M 0x00 – 0xFF
TABLE-CVS1232-0027 Table Table 27: Routine 0xCAFE Positive Response Format Image available: no CVS123-2.pdf 8.5.2 page 39 SUV2_REQ 130; SUV2_REQ 129; SUV2_REQ 132; SUV2_REQ 131; SUV2_REQ 133; SUV2_INFO 117 High Table 27: Routine 0xCAFE Positive Response Format Artifact ID TABLE-CVS1232-0027
Section 8.5.2 Positive Response
Related requirements SUV2_REQ 130; SUV2_REQ 129; SUV2_REQ 132; SUV2_REQ 131; SUV2_REQ 133; SUV2_INFO 117
Why it matters Diagnostic parameter or service behavior
View details Table 27: Routine 0xCAFE Positive Response Format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xCA #4 routineIdentifier (LSB) M 0xFE #5 … #n EMP Message M 0x00 – 0xFF
TABLE-CVS124-0001 Table Table 1 – Definition of Terms Image available: no CVS124.pdf 4.1 page 6 4.1 High Table 1 – Definition of Terms Artifact ID TABLE-CVS124-0001
Why it matters Table source context
View details Table 1 – Definition of Terms
Wide tables scroll horizontally inside this card.
Term Definition Shall This word, or the terms "Required" or "Must", means that the definition is an absolute requirement of the specification. Shall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification. This word, or the adjective “Recommended”, means that there may exist Should valid reasons in particular circumstances to ignore a particular item, but the full implications shall be understood and carefully weighed before choosing a different course. This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is Should not acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. This word, or the adjective “Optional”, means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. May An implementation which does not include a particular option shall be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option shall be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides).
TABLE-CVS124-0002 Table Table 2 – Abbreviated terms Image available: no CVS124.pdf 4.2 page 6 4.2 High Table 2 – Abbreviated terms Artifact ID TABLE-CVS124-0002
Why it matters Diagnostic parameter or service behavior
View details Table 2 – Abbreviated terms
Wide tables scroll horizontally inside this card.
Term Definition Shall This word, or the terms "Required" or "Must", means that the definition is an absolute requirement of the specification. Shall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification. This word, or the adjective “Recommended”, means that there may exist Should valid reasons in particular circumstances to ignore a particular item, but the full implications shall be understood and carefully weighed before choosing a different course. This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is Should not acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. This word, or the adjective “Optional”, means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. May An implementation which does not include a particular option shall be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option shall be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides).
TABLE-CVS124-0003 Table Table 3 – Conventions Image available: no CVS124.pdf 4.3 page 7 4.3 High Table 3 – Conventions Artifact ID TABLE-CVS124-0003
Why it matters Table source context
View details Table 3 – Conventions
Wide tables scroll horizontally inside this card.
ISO International Organization for Standardization non-Def Non-default diagnostic session ODX Open Diagnostic Data Exchange, ODX-Standard (ASAM MCD-2D) Prg Programming diagnostic session SPN Suspected Parameter Number PDU Protocol Data Unit SID Service Identification Data IVD Integrity Validation Data RBAC Role Base Access Control
View full table (13 rows) ISO International Organization for Standardization non-Def Non-default diagnostic session ODX Open Diagnostic Data Exchange, ODX-Standard (ASAM MCD-2D) Prg Programming diagnostic session SPN Suspected Parameter Number PDU Protocol Data Unit SID Service Identification Data IVD Integrity Validation Data RBAC Role Base Access Control RBACC RBAC Configuration SPRMIB Suppress Positive Response Message Indication Bit A_ASCIISTRING ODX BASE-DATA-TYPE for an ASCII coded character field (ISO 8859-1) min-max-length zero The bit length of the ODX element DOP (DATA-OBJECT-PROP) is terminated variable; minimal and maximal ZERO for binary and ‘NULL’ for length ASCII is given in bytes; the termination is
TABLE-CVS124-0004 Table Table 4 – Definitions of terms Image available: no CVS124.pdf 4.3 page 7 4.3; REQ_UDS_0003 ; REQ_UDS_0001 ; REQ_UDS_0002 High Table 4 – Definitions of terms Artifact ID TABLE-CVS124-0004
Why it matters Diagnostic parameter or service behavior
View details Table 4 – Definitions of terms
Wide tables scroll horizontally inside this card.
ISO International Organization for Standardization non-Def Non-default diagnostic session ODX Open Diagnostic Data Exchange, ODX-Standard (ASAM MCD-2D) Prg Programming diagnostic session SPN Suspected Parameter Number PDU Protocol Data Unit SID Service Identification Data IVD Integrity Validation Data RBAC Role Base Access Control
View full table (13 rows) ISO International Organization for Standardization non-Def Non-default diagnostic session ODX Open Diagnostic Data Exchange, ODX-Standard (ASAM MCD-2D) Prg Programming diagnostic session SPN Suspected Parameter Number PDU Protocol Data Unit SID Service Identification Data IVD Integrity Validation Data RBAC Role Base Access Control RBACC RBAC Configuration SPRMIB Suppress Positive Response Message Indication Bit A_ASCIISTRING ODX BASE-DATA-TYPE for an ASCII coded character field (ISO 8859-1) min-max-length zero The bit length of the ODX element DOP (DATA-OBJECT-PROP) is terminated variable; minimal and maximal ZERO for binary and ‘NULL’ for length ASCII is given in bytes; the termination is
TABLE-CVS124-0005 Table Table 5 -Data identifiers used at ECU identification Image available: no CVS124.pdf 5.2.1 page 8 REQ_UDS_0003 ; REQ_UDS_0001 ; REQ_UDS_0002 High Table 5 -Data identifiers used at ECU identification Artifact ID TABLE-CVS124-0005
Section 5.2.1 Used data identifier in order to identify an ECU
Why it matters Diagnostic parameter or service behavior
View details Table 5 -Data identifiers used at ECU identification
Wide tables scroll horizontally inside this card.
DID Description/ Name Application Sessions Def Non- Def Ext Boot Sessions Def loader Non-Def Prg Ext Changing 0xF180 bootSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF181 applicationSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF182 applicationDataIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF186 ActiveDiagnosticSessionDataIdentifier ● ● ● ● ● INTERNAL 0xF187 vehicleManufacturerSparePartNumberDataIdentifier ● ○ ● ○ ○ SUPPLIER 0xF188 vehicleManufacturerECUSoftwareNumberDataIdent ifier ● ● ● ● ● SUPPLIER 0xF189 vehicleManufacturerECUSoftwareVersionNumberD ataIdentifier ● ● ● ● ● SUPPLIER 0xF18A systemSupplierIdentifierDataIdentifier ● ● - - - SUPPLIER
View full table (15 rows) DID Description/ Name Application Sessions Def Non- Def Ext Boot Sessions Def loader Non-Def Prg Ext Changing 0xF180 bootSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF181 applicationSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF182 applicationDataIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF186 ActiveDiagnosticSessionDataIdentifier ● ● ● ● ● INTERNAL 0xF187 vehicleManufacturerSparePartNumberDataIdentifier ● ○ ● ○ ○ SUPPLIER 0xF188 vehicleManufacturerECUSoftwareNumberDataIdent ifier ● ● ● ● ● SUPPLIER 0xF189 vehicleManufacturerECUSoftwareVersionNumberD ataIdentifier ● ● ● ● ● SUPPLIER 0xF18A systemSupplierIdentifierDataIdentifier ● ● - - - SUPPLIER 0xF18B ECUManufacturingDateDataIdentifier ● ● ● ● ● SUPPLIER 0xF18C ECUSerialNumberDataIdentifier ● ● ● ● ● SUPPLIER 0xF190 VINDataIdentifier ● ○ ● ● ● DIAG 0xF191 vehicleManufacturerECUHardwareNumberDataIde ntifier ● ● ● ● ● SUPPLIER 0xF192 systemSupplierECUHardwareNumberDataIdentifier ● ● - - - SUPPLIER 0xF193 systemSupplierECUHardwareVersionNumberDataI dentifier ● ● - - - SUPPLIER 0xF194 systemSupplierECUSoftwareNumberDataIdentifier ● ● - - - SUPPLIER
TABLE-CVS124-0006 Table Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier Image available: no CVS124.pdf 5.2.1.1 page 10 REQ_UDS_0004 ; REQ_UDS_0006 ; REQ_UDS_0005 ; INFO_UDS_0001; INFO_UDS_0002High Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier Artifact ID TABLE-CVS124-0006
Section 5.2.1.1 DID 0xF180 bootSoftwareIdentificationDataIdentifier
Why it matters State-machine or transition behavior
View details Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name : Cvt: Byte No #1 bootSoftwareIdentificationDataIdentifier Description numberOfModules Description M Format 1-Byte-A_UINT32 Cvt M Byte Value 0x01 Default Data 0x01 0xF180 #2 : #14 Boot software identifier #1: byte #1 : byte #13 13-Bytes- A_ASCIISTRING, min-max-length zero terminated M : M 0x00, 0x20 – 0x7E . , 0x00, 0x20 – 0x7E 0x20 . . 0x20
TABLE-CVS124-0007 Table Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier Image available: no CVS124.pdf 5.2.1.2 page 10 REQ_UDS_0006 ; REQ_UDS_0005 ; REQ_UDS_0007 ; REQ_UDS_0231 High Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier Artifact ID TABLE-CVS124-0007
Section 5.2.1.2 DID 0xF181 applicationSoftwareIdentificationDataIdentifier
Why it matters Table source context
View details Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name : Cvt: Byte No #1 bootSoftwareIdentificationDataIdentifier Description numberOfModules Description M Format 1-Byte-A_UINT32 Cvt M Byte Value 0x01 Default Data 0x01 0xF180 #2 : #14 Boot software identifier #1: byte #1 : byte #13 13-Bytes- A_ASCIISTRING, min-max-length zero terminated M : M 0x00, 0x20 – 0x7E . , 0x00, 0x20 – 0x7E 0x20 . . 0x20
TABLE-CVS124-0008 Table Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier Image available: no CVS124.pdf 5.2.1.3 page 11 REQ_UDS_0007 ; REQ_UDS_0008 ; REQ_UDS_0231 ; REQ_UDS_0232 High Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier Artifact ID TABLE-CVS124-0008
Section 5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifier
Why it matters Table source context
View details Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No #1 #2 : #14 applicationDataIdentificationDataIdentifier Description numberOfModules Application data module part number #1: byte #1 Description U Format 1-Byte-A_UINT32 13 Bytes- A_ASCIISTRING min-max-length Cvt M M : M Byte Value 0x01 0x02 – 0xFF 0x00, 0x20 – 0x7E . . Default Data 0x01 0x20 0xF182 : #n – 12 : #n : byte #13 : Application data module part number #m byte #1 : byte #13 zero terminated : 13-Bytes- A_ASCIISTRING min-max-length zero terminated C : C 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E . . 0x00, 0x20 – 0x7E 0x20
TABLE-CVS124-0009 Table Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier Image available: no CVS124.pdf 5.2.1.4 page 11 REQ_UDS_0008 ; REQ_UDS_0232 ; REQ_UDS_0009 ; REQ_UDS_0007 High Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier Artifact ID TABLE-CVS124-0009
Section 5.2.1.4 DID 0xF186 ActiveDiagnosticSessionDataIdentifier
Why it matters Diagnostic parameter or service behavior
View details Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No #1 #2 : #14 applicationDataIdentificationDataIdentifier Description numberOfModules Application data module part number #1: byte #1 Description U Format 1-Byte-A_UINT32 13 Bytes- A_ASCIISTRING min-max-length Cvt M M : M Byte Value 0x01 0x02 – 0xFF 0x00, 0x20 – 0x7E . . Default Data 0x01 0x20 0xF182 : #n – 12 : #n : byte #13 : Application data module part number #m byte #1 : byte #13 zero terminated : 13-Bytes- A_ASCIISTRING min-max-length zero terminated C : C 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E . . 0x00, 0x20 – 0x7E 0x20
TABLE-CVS124-0010 Table Table 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.5 page 12 REQ_UDS_0009 ; REQ_UDS_0010 ; REQ_UDS_0233 High Table 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier Artifact ID TABLE-CVS124-0010
Section 5.2.1.5 DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier
Why it matters Table source context
View details Table 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No vehicleManufacturerSparePartNumberDataIdentifier Description Description M Format Cvt Byte Value Default Data 0xF187 #1 : #13 Vehicle manufacturer sparepart number Byte #1 : Byte #13 13-Bytes- A_ASCIISTRIN G, min-max-length zero terminated M : M 0x00, 0x20 – 0x7E : 0x00, 0x20 – 0x7E 0x20
TABLE-CVS124-0011 Table Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.6 page 12 REQ_UDS_0010 ; REQ_UDS_0233 ; REQ_UDS_0234 ; REQ_UDS_0011 ; REQ_UDS_0009 High Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier Artifact ID TABLE-CVS124-0011
Section 5.2.1.6 DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier
Why it matters Table source context
View details Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No vehicleManufacturerSparePartNumberDataIdentifier Description Description M Format Cvt Byte Value Default Data 0xF187 #1 : #13 Vehicle manufacturer sparepart number Byte #1 : Byte #13 13-Bytes- A_ASCIISTRIN G, min-max-length zero terminated M : M 0x00, 0x20 – 0x7E : 0x00, 0x20 – 0x7E 0x20
TABLE-CVS124-0012 Table Table 12 – Description of DID 0xF189 Image available: no CVS124.pdf 5.2.1.7 page 12 REQ_UDS_0011 ; REQ_UDS_0234 High Table 12 – Description of DID 0xF189 Artifact ID TABLE-CVS124-0012
Section 5.2.1.7 DID 0xF189
Why it matters Table source context
View details Table 12 – Description of DID 0xF189
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No vehicleManufacturerSparePartNumberDataIdentifier Description Description M Format Cvt Byte Value Default Data 0xF187 #1 : #13 Vehicle manufacturer sparepart number Byte #1 : Byte #13 13-Bytes- A_ASCIISTRIN G, min-max-length zero terminated M : M 0x00, 0x20 – 0x7E : 0x00, 0x20 – 0x7E 0x20
TABLE-CVS124-0013 Table Table 13 – Description of DID 0xF18A systemSupplierIdentifierDataIdentifier Image available: no CVS124.pdf 5.2.1.8 page 13 REQ_UDS_0012 ; REQ_UDS_0235 ; REQ_UDS_0013 High Table 13 – Description of DID 0xF18A systemSupplierIdentifierDataIdentifier Artifact ID TABLE-CVS124-0013
Section 5.2.1.8 DID 0xF18A systemSupplierIdentifierDataIdentifier
Why it matters Table source context
View details Table 13 – Description of DID 0xF18A systemSupplierIdentifierDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No Description Description systemSupplierIdentifierDataIdentifier Format M Cvt Byte Value Default Data 0xF18A To be specifie d by the supplier Content and format to be specified by the supplier Should be A_ASCIISTRING, min-max-length zero terminated M : M 0x20 – 0x7E : 0x00, 0x20 – 0x7E System supplier specific
TABLE-CVS124-0014 Table Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier Image available: no CVS124.pdf 5.2.1.9 page 13 REQ_UDS_0013 ; REQ_UDS_0014 ; REQ_UDS_0012 High Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier Artifact ID TABLE-CVS124-0014
Section 5.2.1.9 DID 0xF18B ECUManufacturingDateDataIdentifier
Why it matters Table source context
View details Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No Description Description systemSupplierIdentifierDataIdentifier Format M Cvt Byte Value Default Data 0xF18A To be specifie d by the supplier Content and format to be specified by the supplier Should be A_ASCIISTRING, min-max-length zero terminated M : M 0x20 – 0x7E : 0x00, 0x20 – 0x7E System supplier specific
TABLE-CVS124-0015 Table Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.10 page 14 REQ_UDS_0014 ; REQ_UDS_0015 High Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier Artifact ID TABLE-CVS124-0015
Section 5.2.1.10 DID 0xF18C ECUSerialNumberDataIdentifier
Why it matters Table source context
View details Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No ECUSerialNumberDataIdentifier Description Description M Format Cvt Byte Value Default Data 0xF18C To be specified Minimum and the unique for one by the supplier. length shall be 8 bytes assigned value shall be every unit provided by supplier per project. A_ASCIISTRING System supplier specific
TABLE-CVS124-0016 Table Table 16 – Description of DID 0xF190 VINDataIdentifier Image available: no CVS124.pdf 5.2.1.11 page 14 REQ_UDS_0015 ; REQ_UDS_0014 ; REQ_UDS_0016 ; INFO_UDS_0003High Table 16 – Description of DID 0xF190 VINDataIdentifier Artifact ID TABLE-CVS124-0016
Section 5.2.1.11 DID 0xF190 VINDataIdentifier
Why it matters Table source context
View details Table 16 – Description of DID 0xF190 VINDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No ECUSerialNumberDataIdentifier Description Description M Format Cvt Byte Value Default Data 0xF18C To be specified Minimum and the unique for one by the supplier. length shall be 8 bytes assigned value shall be every unit provided by supplier per project. A_ASCIISTRING System supplier specific
TABLE-CVS124-0017 Table Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.12 page 14 REQ_UDS_0016 ; INFO_UDS_0003High Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier Artifact ID TABLE-CVS124-0017
Section 5.2.1.12 DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier
Why it matters Table source context
View details Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No ECUSerialNumberDataIdentifier Description Description M Format Cvt Byte Value Default Data 0xF18C To be specified Minimum and the unique for one by the supplier. length shall be 8 bytes assigned value shall be every unit provided by supplier per project. A_ASCIISTRING System supplier specific
TABLE-CVS124-0018 Table Table 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.13 page 15 REQ_UDS_0017 ; REQ_UDS_0236 ; REQ_UDS_0018 ; REQ_UDS_0019 High Table 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier Artifact ID TABLE-CVS124-0018
Section 5.2.1.13 DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier
Why it matters Table source context
View details Table 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: systemSupplierECUHardwareNumberDataIdentifier Description U 0xF192 Byte No Description To be specified Format by the External Supplier Cvt Byte Value Default Data System supplier specific
TABLE-CVS124-0019 Table Table 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.14 page 15 REQ_UDS_0018 ; REQ_UDS_0017 ; REQ_UDS_0236 ; REQ_UDS_0019 High Table 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier Artifact ID TABLE-CVS124-0019
Section 5.2.1.14 DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier
Why it matters Table source context
View details Table 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: systemSupplierECUHardwareNumberDataIdentifier Description U 0xF192 Byte No Description To be specified Format by the External Supplier Cvt Byte Value Default Data System supplier specific
TABLE-CVS124-0020 Table Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.15 page 15 REQ_UDS_0019 ; REQ_UDS_0018 ; REQ_UDS_0017 ; REQ_UDS_0020 ; REQ_UDS_0021 High Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier Artifact ID TABLE-CVS124-0020
Section 5.2.1.15 DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier
Why it matters Table source context
View details Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: systemSupplierECUHardwareNumberDataIdentifier Description U 0xF192 Byte No Description To be specified Format by the External Supplier Cvt Byte Value Default Data System supplier specific
TABLE-CVS124-0021 Table Table 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.16 page 16 REQ_UDS_0020 ; REQ_UDS_0021 High Table 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier Artifact ID TABLE-CVS124-0021
Section 5.2.1.16 DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier
Why it matters Table source context
View details Table 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: systemSupplierECUSoftwareVersionNumberDataIdentifier Description U 0xF195 Byte No Description To be specified Format by the External Cvt supplier Byte Value Default Data System supplier specific
TABLE-CVS124-0022 Table Table 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier Image available: no CVS124.pdf 5.2.1.17 page 16 REQ_UDS_0021 ; REQ_UDS_0020 ; REQ_UDS_0022 High Table 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier Artifact ID TABLE-CVS124-0022
Section 5.2.1.17 DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier
Why it matters Table source context
View details Table 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: systemSupplierECUSoftwareVersionNumberDataIdentifier Description U 0xF195 Byte No Description To be specified Format by the External Cvt supplier Byte Value Default Data System supplier specific
TABLE-CVS124-0023 Table Table 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier Image available: no CVS124.pdf 5.2.1.18 page 16 REQ_UDS_0022 ; REQ_UDS_0237 ; INFO_UDS_0039; REQ_UDS_0339 ; REQ_UDS_0021 High Table 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier Artifact ID TABLE-CVS124-0023
Section 5.2.1.18 DID 0xF197 systemNameOrEngineTypeDataIdentifier
Why it matters Table source context
View details Table 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: systemSupplierECUSoftwareVersionNumberDataIdentifier Description U 0xF195 Byte No Description To be specified Format by the External Cvt supplier Byte Value Default Data System supplier specific
TABLE-CVS124-0024 Table Table 24 – Description of DID 0xF198 SoftwareItemSemanticDataIdentifiers Image available: no CVS124.pdf 5.2.1.19 page 17 REQ_UDS_0339 ; REQ_UDS_0340 ; REQ_UDS_0237 ; INFO_UDS_0039High Table 24 – Description of DID 0xF198 SoftwareItemSemanticDataIdentifiers Artifact ID TABLE-CVS124-0024
Section 5.2.1.19 DID 0xF198 SoftwareItemSemanticDataIdentifiers
Why it matters Table source context
View details Table 24 – Description of DID 0xF198 SoftwareItemSemanticDataIdentifiers
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No #1 : #3 SoftwareItemSemanticDataIdentifiers Description numberOfModules (m) Description C Format 3-Byte- A_UINT32 Cvt M Byte Value 0x000000 – 0xFFFFFF Default Data 0x0000 00 0xF198 #4 : #n+3 : : SoftwareItemSemantic Data Identifier #1: byte #1 : byte #n* : SoftwareItemSemantic Data Identifier #m: byte #1 : byte #q* 0 - 128- Bytes- A_ASCIIST RING, zero terminated : 0 - 128- Bytes- A_ASCIIST RING, zero terminated C1 : C1 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E : 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E 0x00 : 0x00
TABLE-CVS124-0025 Table Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s Image available: no CVS124.pdf 5.2.1.20 page 17 REQ_UDS_0340 High Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s Artifact ID TABLE-CVS124-0025
Section 5.2.1.20 DID 0xF199 SoftwareAssemblySemanticDataIdentifiers
Why it matters Table source context
View details Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No #1 : #3 SoftwareItemSemanticDataIdentifiers Description numberOfModules (m) Description C Format 3-Byte- A_UINT32 Cvt M Byte Value 0x000000 – 0xFFFFFF Default Data 0x0000 00 0xF198 #4 : #n+3 : : SoftwareItemSemantic Data Identifier #1: byte #1 : byte #n* : SoftwareItemSemantic Data Identifier #m: byte #1 : byte #q* 0 - 128- Bytes- A_ASCIIST RING, zero terminated : 0 - 128- Bytes- A_ASCIIST RING, zero terminated C1 : C1 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E : 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E 0x00 : 0x00
TABLE-CVS124-0026 Table Table 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers Image available: no CVS124.pdf 5.2.1.21 page 18 REQ_UDS_0341 ; REQ_UDS_0023 High Table 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers Artifact ID TABLE-CVS124-0026
Section 5.2.1.21 DID 0xF19A HardwareSemanticDataIdentifiers
Why it matters Table source context
View details Table 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No #1 : #3 HardwareSemanticDataIdentifiers Description numberOfModules(m) HardwareSemantic Data Description M Format 3-Byte- A_UINT32 Cvt M Byte Value 0x000001 – 0xFFFFFF Default Data 0x0000 01 0xF19A #4 : #n+3 : : Identifier #1: byte #1 : byte #n* : HardwareSemantic Data Identifier #m: byte #1 : byte #q* 0 - 128- Bytes- A_ASCIISTR ING, zero terminated : 0 - 128- Bytes- A_ASCIISTR ING, zero terminated M : C 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E : 0x00, 0x20 – 0x7E 0x00, 0x20 – 0x7E 0x00 : 0x00
TABLE-CVS124-0027 Table Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier Image available: no CVS124.pdf 5.2.1.22 page 19 REQ_UDS_0023 ; REQ_UDS_0025 High Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier Artifact ID TABLE-CVS124-0027
Section 5.2.1.22 DID 0xF19D ECUInstallationDateDataIdentifier
Why it matters Table source context
View details Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No ECUInstallationDateDataIdentifier Description Format: “YYYYMMDD” byte #1 YY (most Description M Format Cvt Byte Value Default Data 0xF19D #1 . . #8 significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- A_ASCIIST RING M : M 0x20, 0x30 – 0x39 : 0x20, 0x30 – 0x39 0x2020 20202 020
TABLE-CVS124-0028 Table Table 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber Image available: no CVS124.pdf 5.2.1.23 page 19 REQ_UDS_0025 ; REQ_UDS_0026 High Table 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber Artifact ID TABLE-CVS124-0028
Section 5.2.1.23 DID 0xF1A5 vehicleManufacturerECUHardwareWithoutBootNumber
Why it matters State-machine or transition behavior
View details Table 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No ECUInstallationDateDataIdentifier Description Format: “YYYYMMDD” byte #1 YY (most Description M Format Cvt Byte Value Default Data 0xF19D #1 . . #8 significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- A_ASCIIST RING M : M 0x20, 0x30 – 0x39 : 0x20, 0x30 – 0x39 0x2020 20202 020
TABLE-CVS124-0029 Table Table 29 – Description of DID 0xF1A6 engineNumber Image available: no CVS124.pdf 5.2.1.24 page 19 REQ_UDS_0026 ; REQ_UDS_0027 ; REQ_UDS_0028 ; REQ_UDS_0025 High Table 29 – Description of DID 0xF1A6 engineNumber Artifact ID TABLE-CVS124-0029
Section 5.2.1.24 DID 0xF1A6 engineNumber
Why it matters Table source context
View details Table 29 – Description of DID 0xF1A6 engineNumber
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No ECUInstallationDateDataIdentifier Description Format: “YYYYMMDD” byte #1 YY (most Description M Format Cvt Byte Value Default Data 0xF19D #1 . . #8 significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- A_ASCIIST RING M : M 0x20, 0x30 – 0x39 : 0x20, 0x30 – 0x39 0x2020 20202 020
TABLE-CVS124-0030 Table Table 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp Image available: no CVS124.pdf 5.2.1.25 page 20 REQ_UDS_0028 ; REQ_UDS_0030 ; REQ_UDS_0027 ; REQ_UDS_0029 High Table 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp Artifact ID TABLE-CVS124-0030
Section 5.2.1.25 DID 0xF1A9 Lifetime ECU-runtime at software update stamp
Why it matters Software update or memory programming context
View details Table 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No lifetimeECUruntimeAtSoftwareUpdateStamp Description Description Format C Cvt Byte Value Default Data 0xF1A9 #1 : #4 Lifetime ECU- runtime at software update stamp Unit: s A_UINT32 M : M 0x00 – 0xFF : 0x00 – 0xFF 0xFFFFFFFF
TABLE-CVS124-0031 Table Table 31 – Description of DID 0xF1AA Mileage at software update stamp Image available: no CVS124.pdf 5.2.1.26 page 20 REQ_UDS_0030 ; REQ_UDS_0029 ; INFO_UDS_0004; REQ_UDS_0032 ; REQ_UDS_0028 High Table 31 – Description of DID 0xF1AA Mileage at software update stamp Artifact ID TABLE-CVS124-0031
Section 5.2.1.26 DID 0xF1AA Mileage at software update stamp
Why it matters Software update or memory programming context
View details Table 31 – Description of DID 0xF1AA Mileage at software update stamp
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No lifetimeECUruntimeAtSoftwareUpdateStamp Description Description Format C Cvt Byte Value Default Data 0xF1A9 #1 : #4 Lifetime ECU- runtime at software update stamp Unit: s A_UINT32 M : M 0x00 – 0xFF : 0x00 – 0xFF 0xFFFFFFFF
TABLE-CVS124-0032 Table Table 32 – Description of DID 0xF1AB Date at software update stamp Image available: no CVS124.pdf 5.2.1.27 page 21 REQ_UDS_0032 ; INFO_UDS_0004; REQ_UDS_0033 High Table 32 – Description of DID 0xF1AB Date at software update stamp Artifact ID TABLE-CVS124-0032
Section 5.2.1.27 DID 0xF1AB Date at software update stamp
Why it matters Software update or memory programming context
View details Table 32 – Description of DID 0xF1AB Date at software update stamp
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No Description Format: “YYYYMMDD” byte #1 YY (most Description dateAtSoftwareUpdateStamp C Format Cvt Byte Value Default Data 0xF1AB #1 . . #8 significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- A_ASCIISTRING M : M 0x20, 0x30 – 0x39 : 0x20, 0x30 – 0x39 0x20202 0202020 20
TABLE-CVS124-0033 Table Table 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier Image available: no CVS124.pdf 5.2.1.28 page 21 REQ_UDS_0033 ; REQ_UDS_0034 High Table 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier Artifact ID TABLE-CVS124-0033
Section 5.2.1.28 DID 0xF1AD activeECUSoftwareDataIdentifier
Why it matters State-machine or transition behavior
View details Table 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No Description Format: “YYYYMMDD” byte #1 YY (most Description dateAtSoftwareUpdateStamp C Format Cvt Byte Value Default Data 0xF1AB #1 . . #8 significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- A_ASCIISTRING M : M 0x20, 0x30 – 0x39 : 0x20, 0x30 – 0x39 0x20202 0202020 20
TABLE-CVS124-0034 Table Table 34 – Description of DID 0xF1AF NodeUID Image available: no CVS124.pdf 5.2.1.29 page 21 REQ_UDS_0034 ; REQ_UDS_0036 ; INFO_UDS_0005; INFO_UDS_0040; REQ_UDS_0033 High Table 34 – Description of DID 0xF1AF NodeUID Artifact ID TABLE-CVS124-0034
Section 5.2.1.29 DID 0xF1AF NodeUID
Why it matters Table source context
View details Table 34 – Description of DID 0xF1AF NodeUID
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No Description Format: “YYYYMMDD” byte #1 YY (most Description dateAtSoftwareUpdateStamp C Format Cvt Byte Value Default Data 0xF1AB #1 . . #8 significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- A_ASCIISTRING M : M 0x20, 0x30 – 0x39 : 0x20, 0x30 – 0x39 0x20202 0202020 20
TABLE-CVS124-0035 Table Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber Image available: no CVS124.pdf 5.2.1.30 page 22 REQ_UDS_0036 ; REQ_UDS_0037 ; INFO_UDS_0005; INFO_UDS_0040; INFO_UDS_0006High Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber Artifact ID TABLE-CVS124-0035
Section 5.2.1.30 DID 0xF1B9 RBACCIdentifierNumber
Why it matters Table source context
View details Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte Description RBACCIdentifierNumber Description Format M Cvt Byte Value Default 0xF1B9 No #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M 0x00 – 0xFF : 0x00 – 0xFF Data 0x00 : 0x00
TABLE-CVS124-0036 Table Table 36 – Description of DID 0xF1BA RBACCStructureVersion Image available: no CVS124.pdf 5.2.1.31 page 22 REQ_UDS_0037 ; REQ_UDS_0038 ; INFO_UDS_0006; INFO_UDS_0007; REQ_UDS_0036 High Table 36 – Description of DID 0xF1BA RBACCStructureVersion Artifact ID TABLE-CVS124-0036
Section 5.2.1.31 DID 0xF1BA RBACCStructureVersion
Why it matters Table source context
View details Table 36 – Description of DID 0xF1BA RBACCStructureVersion
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte Description RBACCIdentifierNumber Description Format M Cvt Byte Value Default 0xF1B9 No #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M 0x00 – 0xFF : 0x00 – 0xFF Data 0x00 : 0x00
TABLE-CVS124-0037 Table Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier Image available: no CVS124.pdf 5.2.1.32 page 22 REQ_UDS_0038 ; INFO_UDS_0007; REQ_UDS_0039 High Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier Artifact ID TABLE-CVS124-0037
Section 5.2.1.32 DID 0xF1D1 RootCertificateIdentifier
Why it matters Security protocol or cryptographic context
View details Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte Description RBACCIdentifierNumber Description Format M Cvt Byte Value Default 0xF1B9 No #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M 0x00 – 0xFF : 0x00 – 0xFF Data 0x00 : 0x00
TABLE-CVS124-0038 Table Table 38 – Description of DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber Image available: no CVS124.pdf 5.2.1.33 page 23 REQ_UDS_0039 ; REQ_UDS_0238 ; REQ_UDS_0040 ; REQ_UDS_0041 ; REQ_UDS_0042 ; REQ_UDS_0043 ; REQ_UDS_0044 High Table 38 – Description of DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber Artifact ID TABLE-CVS124-0038
Section 5.2.1.33 DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber
Why it matters State-machine or transition behavior
View details Table 38 – Description of DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber
Wide tables scroll horizontally inside this card.
DID Name: Cvt: Byte No: vehicleManufacturerECUBootSoftwareNumber Description Description M Format Cvt Byte Value Default Data 0xF1E1 #1 : #13 vehicleManufacturer ECUBootSoftwareNu mber Byte #1 Byte #2 : Byte #13 13-Byte- A_ASCIISTRIN G, min-max-length zero terminated M : M 0x20 – 0x7E 0x00, 0x20 – 0x7E : 0x00, 0x20 – 0x7E Project specific
TABLE-CVS124-0039 Table Table 39 – Diagnostic service support Image available: no CVS124.pdf 5.3 page 24 REQ_UDS_0045 ; REQ_UDS_0044 ; REQ_UDS_0043 ; INFO_UDS_0038; REQ_UDS_0046 ; REQ_UDS_0047 ; REQ_UDS_0048 ; REQ_UDS_0049 High Table 39 – Diagnostic service support Artifact ID TABLE-CVS124-0039
Section 5.3 Diagnostic sessions requirements
Why it matters Diagnostic parameter or service behavior
View details Table 39 – Diagnostic service support
Wide tables scroll horizontally inside this card.
Addressin Application Sessions Boot Sessions loader Service according to ISO 14229-1 g mode Def Non-Def Extd Def Prg Non-Def Extd DiagnosticSessionControl (0x10) F, P M M M M M ECUReset (0x11) F, P M M M M M SecurityAccess (0x27) - - - - - CommunicationControl (0x28) F, P - M - - M TesterPresent (0x3E) F, P M M M M M AccessTimingParameter (0x83) - - - - - Authentication (0x29) F, P M M M M M
View full table (27 rows) Addressin Application Sessions Boot Sessions loader Service according to ISO 14229-1 g mode Def Non-Def Extd Def Prg Non-Def Extd DiagnosticSessionControl (0x10) F, P M M M M M ECUReset (0x11) F, P M M M M M SecurityAccess (0x27) - - - - - CommunicationControl (0x28) F, P - M - - M TesterPresent (0x3E) F, P M M M M M AccessTimingParameter (0x83) - - - - - Authentication (0x29) F, P M M M M M SecuredDataTransmission (0x84) P M M M M M ControlDTCSetting (0x85) F, P - M - - M LinkControl (0x87) - C - C C ReadDataByIdentifier (0x22) F, P M M M M M ReadMemoryByAddress (0x23) - - - - - ReadScalingDataByIdentifier (0x24) - - - - - ReadDataByPeriodicIdentifier (0x2A) - - - - - DynamicallyDefineDataIdentifier (0x2C) P U U - - - WriteDataByIdentifier (0x2E) P - M - M C WriteMemoryByAddress (0x3D) - - - - - ClearDiagnosticInformation (0x14) F, P M M - - - ReadDTCInformation (0x19) F, P M M - - - InputOutputControlByIdentifier (0x2F) P - C - - - RoutineControl (0x31) P M M - M M RequestDownload (0x34) P - C - C1 C1 RequestUpload (0x35) P - C - - - TransferData (0x36) P - C - M C RequestTransferExit (0x37) P - C - M C RequestFileTransfer (0x38) P - C - C1 C1
TABLE-CVS124-0040 Table Table 40 – Diagnostic Safe State check for Services Image available: no CVS124.pdf 5.3 page 25 REQ_UDS_0049 ; INFO_UDS_0008; REQ_UDS_0050 ; REQ_UDS_0048 ; REQ_UDS_0051 High Table 40 – Diagnostic Safe State check for Services Artifact ID TABLE-CVS124-0040
Section 5.3 Diagnostic sessions requirements
Why it matters Diagnostic parameter or service behavior
View details Table 40 – Diagnostic Safe State check for Services
Wide tables scroll horizontally inside this card.
CVS31 and CVS32 requirements preconditions per service shall be defined by the RBAC Configuration file in the ECU.
TABLE-CVS124-0041 Table Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which Image available: no CVS124.pdf 5.4 page 31 REQ_UDS_0053 ; REQ_UDS_0052 ; INFO_UDS_0009; REQ_UDS_0054 ; REQ_UDS_0337 High Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which Artifact ID TABLE-CVS124-0041
Section 5.4 Data identifier requirements
Why it matters Table source context
View details Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which
Wide tables scroll horizontally inside this card.
Byte value Description 0x0611-0x0620 Reserved for collective data identifiers 0xB000 – 0xB1FF Reserved for TRATON 0xCF00 – 0xCFFF TRATON data field identifiers 0xF010 disableDiagnosticClient
TABLE-CVS124-0042 Table Table 41 – Data identifier (DID) ranges Image available: no CVS124.pdf 5.4 page 31 INFO_UDS_0009; REQ_UDS_0052 ; REQ_UDS_0053 ; REQ_UDS_0054 High Table 41 – Data identifier (DID) ranges Artifact ID TABLE-CVS124-0042
Section 5.4 Data identifier requirements
Why it matters Diagnostic parameter or service behavior
View details Table 41 – Data identifier (DID) ranges
Wide tables scroll horizontally inside this card.
Byte value Description 0x0611-0x0620 Reserved for collective data identifiers 0xB000 – 0xB1FF Reserved for TRATON 0xCF00 – 0xCFFF TRATON data field identifiers 0xF010 disableDiagnosticClient
TABLE-CVS124-0043 Table Table 42 – IVD DIDs Image available: no CVS124.pdf 5.4.1 page 31 REQ_UDS_0053 ; INFO_UDS_0009; REQ_UDS_0054 ; REQ_UDS_0055 ; REQ_UDS_0056 ; REQ_UDS_0342 ; REQ_UDS_0239 ; REQ_UDS_0057 High Table 42 – IVD DIDs Artifact ID TABLE-CVS124-0043
Section 5.4.1 Integrity Validation Data DIDs (IVD-DIDs)
Why it matters State-machine or transition behavior
View details Table 42 – IVD DIDs
Wide tables scroll horizontally inside this card.
Byte value Description 0x0611-0x0620 Reserved for collective data identifiers 0xB000 – 0xB1FF Reserved for TRATON 0xCF00 – 0xCFFF TRATON data field identifiers 0xF010 disableDiagnosticClient
TABLE-CVS124-0044 Table Table 43 – Service 0x10 request parameter diagnosticSessionType description Image available: no CVS124.pdf 5.5.1.1.1 page 32 REQ_UDS_0058 ; REQ_UDS_0055 ; REQ_UDS_0056 ; REQ_UDS_0342 ; REQ_UDS_0239 ; REQ_UDS_0057 ; REQ_UDS_0059 ; REQ_UDS_0060 High Table 43 – Service 0x10 request parameter diagnosticSessionType description Artifact ID TABLE-CVS124-0044
Section 5.5.1.1.1 Request parameter diagnosticSessionType
Why it matters Diagnostic parameter or service behavior
View details Table 43 – Service 0x10 request parameter diagnosticSessionType description
Wide tables scroll horizontally inside this card.
Negative response code 0x22, conditionsNotCorrect , shall be used if a service request is denied due to insufficient rights according to the RBACC check.
TABLE-CVS124-0045 Table Table 44 – Service 0x11 request parameter resetType description Image available: no CVS124.pdf 5.5.2.1.1 page 34 REQ_UDS_0068 ; REQ_UDS_0069 ; REQ_UDS_0070 ; REQ_UDS_0071 ; REQ_UDS_0072 ; REQ_UDS_0244 ; INFO_UDS_0010; REQ_UDS_0066 High Table 44 – Service 0x11 request parameter resetType description Artifact ID TABLE-CVS124-0045
Section 5.5.2.1.1 Request parameter resetType
Why it matters Table source context
View details Table 44 – Service 0x11 request parameter resetType description
Wide tables scroll horizontally inside this card.
Hex (bit 6-0) Description Cvt 0x01 hardReset M 0x02 keyOffOnReset C
TABLE-CVS124-0046 Table Table 45 – Service 0x11 positive response parameter description Image available: no CVS124.pdf 5.5.2.2 page 34 REQ_UDS_0073 ; REQ_UDS_0070 ; REQ_UDS_0071 ; REQ_UDS_0072 ; INFO_UDS_0010; REQ_UDS_0074 ; REQ_UDS_0245 ; REQ_UDS_0246 High Table 45 – Service 0x11 positive response parameter description Artifact ID TABLE-CVS124-0046
Section 5.5.2.2 Positive response
Why it matters Table source context
View details Table 45 – Service 0x11 positive response parameter description
Wide tables scroll horizontally inside this card.
Hex (bit 6-0) Description Cvt 0x01 hardReset M 0x02 keyOffOnReset C
TABLE-CVS124-0047 Table Table 46 – Service 0x11 negative response codes Image available: no CVS124.pdf 5.5.2.3.1 page 35 REQ_UDS_0074 ; REQ_UDS_0245 ; REQ_UDS_0246 ; REQ_UDS_0075 ; INFO_UDS_0011; REQ_UDS_0076 ; REQ_UDS_0077 ; INFO_UDS_0012High Table 46 – Service 0x11 negative response codes Artifact ID TABLE-CVS124-0047
Section 5.5.2.3.1 Supported negative response codes
Why it matters Table source context
View details Table 46 – Service 0x11 negative response codes
Wide tables scroll horizontally inside this card.
NRC Description and scenario sub-functionNotSupported 0x12 Refer to ISO 14229-1 for scenario. incorrectMessageLengthOrInvalidFormat 0x13 Refer to ISO 14229-1 for scenario. conditionsNotCorrect 0x22 Refer to ISO 14229-1 for scenario.
TABLE-CVS124-0048 Table Table 47 – Service 0x28 request parameter description Image available: no CVS124.pdf 5.5.3.1 page 36 REQ_UDS_0078 ; REQ_UDS_0079 ; REQ_UDS_0080 ; REQ_UDS_0248 ; INFO_UDS_0013; REQ_UDS_0247 High Table 47 – Service 0x28 request parameter description Artifact ID TABLE-CVS124-0048
Why it matters Table source context
View details Table 47 – Service 0x28 request parameter description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 CommunicationControl Request SID M 2 controlType M 3 communicationType M
TABLE-CVS124-0049 Table Table 48 – Service 0x28 request parameter controlType description Image available: no CVS124.pdf 5.5.3.1.1 page 36 REQ_UDS_0079 ; REQ_UDS_0078 ; REQ_UDS_0080 ; REQ_UDS_0248 ; INFO_UDS_0013; REQ_UDS_0247 High Table 48 – Service 0x28 request parameter controlType description Artifact ID TABLE-CVS124-0049
Section 5.5.3.1.1 Request parameter controlType
Why it matters Table source context
View details Table 48 – Service 0x28 request parameter controlType description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 CommunicationControl Request SID M 2 controlType M 3 communicationType M
TABLE-CVS124-0050 Table Table 49 – Service 0x28 request parameter communicationType description Image available: no CVS124.pdf 5.5.3.1.2 page 36 REQ_UDS_0080 ; REQ_UDS_0078 ; REQ_UDS_0079 ; REQ_UDS_0248 ; REQ_UDS_0247 ; REQ_UDS_0081 High Table 49 – Service 0x28 request parameter communicationType description Artifact ID TABLE-CVS124-0050
Section 5.5.3.1.2 Request parameter communicationType
Why it matters Table source context
View details Table 49 – Service 0x28 request parameter communicationType description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 CommunicationControl Request SID M 2 controlType M 3 communicationType M
TABLE-CVS124-0051 Table Table 50 – Service 0x87 request parameter linkControlType description Image available: no CVS124.pdf 5.5.6.2 page 39 REQ_UDS_0085 ; REQ_UDS_0086 ; REQ_UDS_0254 ; REQ_UDS_0252 ; REQ_UDS_0253 ; REQ_UDS_0087 ; INFO_UDS_0015; REQ_UDS_0084 High Table 50 – Service 0x87 request parameter linkControlType description Artifact ID TABLE-CVS124-0051
Section 5.5.6.2 Request parameter linkControlType
Why it matters State-machine or transition behavior
View details Table 50 – Service 0x87 request parameter linkControlType description
Wide tables scroll horizontally inside this card.
Byte Value Description Cvt 0x01 verifyModeTransitionWithFixedParameter M 0x03 transitionMode M 0x40-0x5F vehicleManufacturerSpecific U
TABLE-CVS124-0052 Table Table 51 – Service 0x87 request parameter linkControlModeIdentifier description Image available: no CVS124.pdf 5.5.6.2.1 page 39 REQ_UDS_0086 ; REQ_UDS_0085 ; REQ_UDS_0254 ; REQ_UDS_0252 ; REQ_UDS_0253 ; REQ_UDS_0087 ; REQ_UDS_0255 High Table 51 – Service 0x87 request parameter linkControlModeIdentifier description Artifact ID TABLE-CVS124-0052
Section 5.5.6.2.1 Request parameter linkControlModeIdentifier
Why it matters Table source context
View details Table 51 – Service 0x87 request parameter linkControlModeIdentifier description
Wide tables scroll horizontally inside this card.
Byte Value Description Cvt 0x01 verifyModeTransitionWithFixedParameter M 0x03 transitionMode M 0x40-0x5F vehicleManufacturerSpecific U
TABLE-CVS124-0053 Table Table 52 – Service 0x19 request parameter reportType description Image available: no CVS124.pdf 5.5.10.1.1 page 41 REQ_UDS_0094 ; REQ_UDS_0264 ; REQ_UDS_0260 ; REQ_UDS_0261 ; REQ_UDS_0262 ; REQ_UDS_0263 ; REQ_UDS_0265 ; REQ_UDS_0095 High Table 52 – Service 0x19 request parameter reportType description Artifact ID TABLE-CVS124-0053
Section 5.5.10.1.1 Request parameter reportType
Why it matters Diagnostic parameter or service behavior
View details Table 52 – Service 0x19 request parameter reportType description
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x01 reportNumberOfDTCByStatusMask M 0x02 reportDTCByStatusMask M 0x03 reportDTCSnapshotIdentification M 0x04 reportDTCSnapshotRecordByDTCNumber M 0x06 reportDTCExtendedDataRecordByDTCNumber M 0x0F reportMirrorMemoryDTCByStatusMask U
TABLE-CVS124-0054 Table Table 53 – Service 0x19 request parameter DTCMaskRecord description Image available: no CVS124.pdf 5.5.10.1.4 page 42 REQ_UDS_0096 ; REQ_UDS_0095 ; REQ_UDS_0266 ; REQ_UDS_0267 ; REQ_UDS_0097 ; REQ_UDS_0268 ; REQ_UDS_0098 High Table 53 – Service 0x19 request parameter DTCMaskRecord description Artifact ID TABLE-CVS124-0054
Section 5.5.10.1.4 Request parameter DTCMaskRecord
Why it matters Diagnostic parameter or service behavior
View details Table 53 – Service 0x19 request parameter DTCMaskRecord description
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x10 reportMirrorMemoryDTCExtendedDataRecordByDTCNumber U 0x11 reportNumberOfMirrorMemoryDTCByStatusMask U 0x12 reportNumberOfEmissionsRelatedOBDDTCByStatusMask E 0x13 reportEmissionsRelatedOBDDTCByStatusMask E 0x42 reportWWHOBDDTCByMaskRecord E 0x55 reportWWHOBDDTCWithPermanentStatus E
TABLE-CVS124-0055 Table Table 54 – Service 0x19 request parameter DTCExtDataRecordNumber description Image available: no CVS124.pdf 5.5.10.1.6 page 43 REQ_UDS_0098 ; REQ_UDS_0269 ; REQ_UDS_0270 ; REQ_UDS_0271 ; REQ_UDS_0272 ; REQ_UDS_0273 ; REQ_UDS_0274 ; REQ_UDS_0097 High Table 54 – Service 0x19 request parameter DTCExtDataRecordNumber description Artifact ID TABLE-CVS124-0055
Section 5.5.10.1.6 Request parameter DTCExtDataRecordNumber
Why it matters Diagnostic parameter or service behavior
View details Table 54 – Service 0x19 request parameter DTCExtDataRecordNumber description
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x00 Reserved by ISO/SAE M 0x11 ExtDataRecNum 1 M 0x14 ExtDataRecNum 4 M 0xFE All legislated OBD stored DTCExtendedData records E 0xFF All stored DTCExtendedData records M
TABLE-CVS124-0056 Table Table 55 – Snapshot data sub-function (0x04) positive response message content and format Image available: no CVS124.pdf 5.5.10.2.6 page 44 REQ_UDS_0099 ; REQ_UDS_0276 ; REQ_UDS_0277 High Table 55 – Snapshot data sub-function (0x04) positive response message content and format Artifact ID TABLE-CVS124-0056
Section 5.5.10.2.6 Response parameter reportDTCSnapshotRecordByDTCNumber
Why it matters Diagnostic parameter or service behavior
View details Table 55 – Snapshot data sub-function (0x04) positive response message content and format
Wide tables scroll horizontally inside this card.
Byte Description Type / Range Resolu tion Default value Cvt #1 ReadDTCInformation Response SID = 0x59 reportType = [ M #2 reportDTCSnapshotRecordByDTCNumber ] = 0x04 DTCAndStatusRecord[] = [ Byte 1: DTCHighByte 0x00 – 0xFF M #3 Byte 2: DTCMiddleByte 0x00 – M : Byte 3: DTCLowByte 0xFF M #6 Byte 4: statusOfDTC DTCSnapshotRecordNumber#1 0x00 – 0xFF 0x00 – 0xFF M M #7 This byte shall be set to value 0x01. 0x01 0x00 0x01 M #8 DTCSnapshotRecordNumberOfIdentifiers#1 : 0xFF M #9 - #10 dataIdentifier 0x0000 – 0xFFFF M
TABLE-CVS124-0057 Table Table 56 – Service 0x19 response parameter DTCExtDataRecordNumber description Image available: no CVS124.pdf 5.5.10.2.7 page 51 REQ_UDS_0100 ; REQ_UDS_0101 ; REQ_UDS_0304 High Table 56 – Service 0x19 response parameter DTCExtDataRecordNumber description Artifact ID TABLE-CVS124-0057
Section 5.5.10.2.7 Response parameter DTCExtDataRecordNumber
Why it matters Diagnostic parameter or service behavior
View details Table 56 – Service 0x19 response parameter DTCExtDataRecordNumber description
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x00 Reserved by ISO/SAE M 0x11 ExtDataRecNum 1 M 0x14 ExtDataRecNum 4 M 0xFE All legislated OBD stored DTCExtendedData records E 0xFF All stored DTCExtendedData records M
TABLE-CVS124-0058 Table Table 57 – Extended data sub-function (0x06) positive response message content and format Image available: no CVS124.pdf 5.5.10.2.8 page 51 REQ_UDS_0100 ; REQ_UDS_0101 High Table 57 – Extended data sub-function (0x06) positive response message content and format Artifact ID TABLE-CVS124-0058
Section 5.5.10.2.8 Response parameter DTCExtDataRecord
Why it matters Diagnostic parameter or service behavior
View details Table 57 – Extended data sub-function (0x06) positive response message content and format
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x00 Reserved by ISO/SAE M 0x11 ExtDataRecNum 1 M 0x14 ExtDataRecNum 4 M 0xFE All legislated OBD stored DTCExtendedData records E 0xFF All stored DTCExtendedData records M
TABLE-CVS124-0059 Table Table 58 – Service 0x2F request parameter controlOptionRecord description Image available: no CVS124.pdf 5.5.11.1.2 page 54 REQ_UDS_0103 ; REQ_UDS_0104 ; REQ_UDS_0280 ; REQ_UDS_0281 ; REQ_UDS_0282 ; REQ_UDS_0283 ; REQ_UDS_0102 High Table 58 – Service 0x2F request parameter controlOptionRecord description Artifact ID TABLE-CVS124-0059
Section 5.5.11.1.2 Request parameter controlOptionRecord
Why it matters State-machine or transition behavior
View details Table 58 – Service 0x2F request parameter controlOptionRecord description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 inputOutputControlParameter controlState byte 1 M C 2 .. 2 + (m-1) : controlState byte m : C
TABLE-CVS124-0060 Table Table 59 – Service 0x2F request parameter inputOutputControlParameter description Image available: no CVS124.pdf 5.5.11.1.3 page 54 REQ_UDS_0104 ; REQ_UDS_0103 ; REQ_UDS_0284 ; REQ_UDS_0285 ; REQ_UDS_0286 High Table 59 – Service 0x2F request parameter inputOutputControlParameter description Artifact ID TABLE-CVS124-0060
Section 5.5.11.1.3 Request parameter inputOutputControlParameter
Why it matters Table source context
View details Table 59 – Service 0x2F request parameter inputOutputControlParameter description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 inputOutputControlParameter controlState byte 1 M C 2 .. 2 + (m-1) : controlState byte m : C
TABLE-CVS124-0061 Table Table 60 – Service 0x31 request parameter RoutineControlType description Image available: no CVS124.pdf 5.5.12.1.1 page 55 REQ_UDS_0105 ; REQ_UDS_0286 ; REQ_UDS_0284 ; REQ_UDS_0285 ; REQ_UDS_0287 ; REQ_UDS_0106 ; REQ_UDS_0107 High Table 60 – Service 0x31 request parameter RoutineControlType description Artifact ID TABLE-CVS124-0061
Section 5.5.12.1.1 Request parameter RoutineControlType
Why it matters Diagnostic parameter or service behavior
View details Table 60 – Service 0x31 request parameter RoutineControlType description
Wide tables scroll horizontally inside this card.
0x01 resetToDefault U 0x02 freezeCurrentState shortTermAdjustment U 0x03 Refer to ISO 14229-1 for parameter description. M
TABLE-CVS124-0062 Table Table 61 are reserved by TRATON and shall not be used by the system supplier. Image available: no CVS124.pdf 5.5.12.1.2 page 55 REQ_UDS_0106 ; REQ_UDS_0285 ; REQ_UDS_0286 ; REQ_UDS_0287 ; REQ_UDS_0105 ; REQ_UDS_0107 High Table 61 are reserved by TRATON and shall not be used by the system supplier. Artifact ID TABLE-CVS124-0062
Section 5.5.12.1.2 Request parameter RoutineIdentifier
Why it matters Diagnostic parameter or service behavior
View details Table 61 are reserved by TRATON and shall not be used by the system supplier.
Wide tables scroll horizontally inside this card.
0x01 resetToDefault U 0x02 freezeCurrentState shortTermAdjustment U 0x03 Refer to ISO 14229-1 for parameter description. M
TABLE-CVS124-0063 Table Table 61 – Service 0x31 request parameter RoutineIdentifier description Image available: no CVS124.pdf 5.5.12.1.2 page 56 REQ_UDS_0107 ; REQ_UDS_0106 ; REQ_UDS_0108 ; INFO_UDS_0017; REQ_UDS_0288 ; REQ_UDS_0289 ; REQ_UDS_0290 High Table 61 – Service 0x31 request parameter RoutineIdentifier description Artifact ID TABLE-CVS124-0063
Section 5.5.12.1.2 Request parameter RoutineIdentifier
Why it matters Diagnostic parameter or service behavior
View details Table 61 – Service 0x31 request parameter RoutineIdentifier description
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x02B2 ReadStatusOfDiagnosticEventCodes 0x02B3 ReadDiagnosticEventCodesByStatus 0x02B4 ReadEventCodeData These routine IDs are used to handle diagnostic event codes and only mandatory when these type of data are used. U 0x2202 Reserved for CheckMemory routine (Legacy purposes) M 0x2203 Reserved for CheckProgrammingPreConditions routine M 0x2204 Reserved for Data Rescue Preparation (rcDataRescuePreparation) C1 0x2401 Reserved for routine SoftwareInstallation M 0x2501- Reserved for Secure Boot, see f_secureBoot C4
View full table (21 rows) Hex Description Cvt 0x02B2 ReadStatusOfDiagnosticEventCodes 0x02B3 ReadDiagnosticEventCodesByStatus 0x02B4 ReadEventCodeData These routine IDs are used to handle diagnostic event codes and only mandatory when these type of data are used. U 0x2202 Reserved for CheckMemory routine (Legacy purposes) M 0x2203 Reserved for CheckProgrammingPreConditions routine M 0x2204 Reserved for Data Rescue Preparation (rcDataRescuePreparation) C1 0x2401 Reserved for routine SoftwareInstallation M 0x2501- Reserved for Secure Boot, see f_secureBoot C4 0x2509 0xC020 Reserved for routine to set all DIDs to the defined default values, see f_secureLoggingEC C3 0xCAFE This routine ID is reserved to handle Entity Management Protocol request and response, see CVS33 M 0xD000 GetValidDriverParameters 0xD001 GetValidRangeForDriverParameter 0xD002 GetCurrentValueForDSriverParameter 0xD003 SetValueForDriverParameter U 0xD004 SetDefaultValueForDriverParameter These routine IDs are used to handle driver parameters and are only mandatory when these types of parameters are used. 0xDF00 – Reserved for flash routine external data storage U 0xDFFF 0xFF00 Reserved for EraseMemory routine C2 0xFF01 Reserved for CheckProgrammingDependencies routine M 0xFF02 Reserved for CheckParameterDependencies routine M
TABLE-CVS124-0064 Table Table 62 – Service 0x34 request parameter description Image available: no CVS124.pdf 5.5.13.1 page 58 REQ_UDS_0112 ; REQ_UDS_0113 ; REQ_UDS_0111 High Table 62 – Service 0x34 request parameter description Artifact ID TABLE-CVS124-0064
Why it matters Software update or memory programming context
View details Table 62 – Service 0x34 request parameter description
Wide tables scroll horizontally inside this card.
Byte No. Description Cvt 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier memoryAddress byte 1 (MSB) byte 2 M 4 .. (m-1)+4 byte 3 byte 4 : User Optional byte 5 : not available .. byte m : not available memorySize byte 1 (MSB) byte 2 M n -(k-1) .. n byte 3 byte 4 :Mandatory if Memory address byte 4 is used byte 5 : not available .. byte m : not available M
TABLE-CVS124-0065 Table Table 63 – Service 0x34 request parameter dataFormatIdentifier description Image available: no CVS124.pdf 5.5.13.2 page 58 REQ_UDS_0113 ; REQ_UDS_0114 ; REQ_UDS_0115 High Table 63 – Service 0x34 request parameter dataFormatIdentifier description Artifact ID TABLE-CVS124-0065
Section 5.5.13.2 Request parameter dataFormatIdentifier
Why it matters Table source context
View details Table 63 – Service 0x34 request parameter dataFormatIdentifier description
Wide tables scroll horizontally inside this card.
Byte No. Description Cvt 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier memoryAddress byte 1 (MSB) byte 2 M 4 .. (m-1)+4 byte 3 byte 4 : User Optional byte 5 : not available .. byte m : not available memorySize byte 1 (MSB) byte 2 M n -(k-1) .. n byte 3 byte 4 :Mandatory if Memory address byte 4 is used byte 5 : not available .. byte m : not available M
TABLE-CVS124-0066 Table Table 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description Image available: no CVS124.pdf 5.5.13.3 page 59 REQ_UDS_0114 ; REQ_UDS_0115 High Table 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description Artifact ID TABLE-CVS124-0066
Section 5.5.13.3 Request parameter addressAndLengthFormatIdentifier
Why it matters Software update or memory programming context
View details Table 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description
Wide tables scroll horizontally inside this card.
encryptingMethod: 3 - 0 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1
TABLE-CVS124-0067 Table Table 65 – Positive response parameter description Image available: no CVS124.pdf 5.5.13.4 page 59 REQ_UDS_0115 ; REQ_UDS_0114 ; REQ_UDS_0116 ; REQ_UDS_0117 High Table 65 – Positive response parameter description Artifact ID TABLE-CVS124-0067
Section 5.5.13.4 Positive response
Why it matters Software update or memory programming context
View details Table 65 – Positive response parameter description
Wide tables scroll horizontally inside this card.
encryptingMethod: 3 - 0 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1
TABLE-CVS124-0068 Table Table 66 – Service 0x34 response parameter lengthFormatIdentifier description Image available: no CVS124.pdf 5.5.13.5 page 59 REQ_UDS_0116 ; REQ_UDS_0117 High Table 66 – Service 0x34 response parameter lengthFormatIdentifier description Artifact ID TABLE-CVS124-0068
Section 5.5.13.5 Response parameter lengthFormatIdentifier
Why it matters Table source context
View details Table 66 – Service 0x34 response parameter lengthFormatIdentifier description
Wide tables scroll horizontally inside this card.
encryptingMethod: 3 - 0 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1
TABLE-CVS124-0069 Table Table 67 – Service 0x35 request parameter description Image available: no CVS124.pdf 5.5.14.1 page 60 REQ_UDS_0117 ; REQ_UDS_0118 ; REQ_UDS_0116 High Table 67 – Service 0x35 request parameter description Artifact ID TABLE-CVS124-0069
Why it matters Software update or memory programming context
View details Table 67 – Service 0x35 request parameter description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier memoryAddress byte 1 (MSB) byte 2 M 4 .. (m-1)+4 byte 3 byte 4 : User Optional byte 5 : not available .. byte m : not available memorySize byte 1 (MSB) byte 2 M n -(k-1) .. n byte 3 byte 4 :Mandatory if Memory address byte 4 is used byte 5 : not available .. byte m : not available M
TABLE-CVS124-0070 Table Table 68 – Service 0x35 request parameter dataFormatIdentifier description Image available: no CVS124.pdf 5.5.14.1.1 page 60 REQ_UDS_0118 ; REQ_UDS_0117 ; REQ_UDS_0119 ; REQ_UDS_0291 ; REQ_UDS_0292 ; REQ_UDS_0293 High Table 68 – Service 0x35 request parameter dataFormatIdentifier description Artifact ID TABLE-CVS124-0070
Section 5.5.14.1.1 Request parameter dataFormatIdentifier
Why it matters Table source context
View details Table 68 – Service 0x35 request parameter dataFormatIdentifier description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier memoryAddress byte 1 (MSB) byte 2 M 4 .. (m-1)+4 byte 3 byte 4 : User Optional byte 5 : not available .. byte m : not available memorySize byte 1 (MSB) byte 2 M n -(k-1) .. n byte 3 byte 4 :Mandatory if Memory address byte 4 is used byte 5 : not available .. byte m : not available M
TABLE-CVS124-0071 Table Table 69 – Service 0x35 request parameter addressAndLengthFormatIdentifier description Image available: no CVS124.pdf 5.5.14.1.2 page 61 REQ_UDS_0119 ; REQ_UDS_0120 ; REQ_UDS_0291 ; REQ_UDS_0292 ; REQ_UDS_0293 ; REQ_UDS_0294 High Table 69 – Service 0x35 request parameter addressAndLengthFormatIdentifier description Artifact ID TABLE-CVS124-0071
Section 5.5.14.1.2 Request parameter addressAndLengthFormatIdentifier
Why it matters Software update or memory programming context
View details Table 69 – Service 0x35 request parameter addressAndLengthFormatIdentifier description
Wide tables scroll horizontally inside this card.
Bits Description Cvt Values 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4
TABLE-CVS124-0072 Table Table 70 – Service 0x35 response parameter lengthFormatIdentifier description Image available: no CVS124.pdf 5.5.14.2.1 page 61 REQ_UDS_0120 ; REQ_UDS_0119 ; REQ_UDS_0295 ; REQ_UDS_0291 ; REQ_UDS_0292 ; REQ_UDS_0293 ; REQ_UDS_0294 ; REQ_UDS_0296 High Table 70 – Service 0x35 response parameter lengthFormatIdentifier description Artifact ID TABLE-CVS124-0072
Section 5.5.14.2.1 Response parameter lengthFormatIdentifier
Why it matters Table source context
View details Table 70 – Service 0x35 response parameter lengthFormatIdentifier description
Wide tables scroll horizontally inside this card.
Bits Description Cvt Values 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4
TABLE-CVS124-0073 Table Table 71 – Service 0x37 request parameter description Image available: no CVS124.pdf 5.5.16.1 page 62 REQ_UDS_0121 ; REQ_UDS_0300 ; REQ_UDS_0123 ; REQ_UDS_0296 ; REQ_UDS_0297 ; REQ_UDS_0298 ; REQ_UDS_0299 ; REQ_UDS_0122 High Table 71 – Service 0x37 request parameter description Artifact ID TABLE-CVS124-0073
Why it matters Table source context
View details Table 71 – Service 0x37 request parameter description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 RequestTransferExit Request SID M
TABLE-CVS124-0074 Table Table 72 – Service 0x37 positive response parameter description Image available: no CVS124.pdf 5.5.16.2 page 62 REQ_UDS_0123 ; REQ_UDS_0300 ; REQ_UDS_0121 ; REQ_UDS_0297 ; REQ_UDS_0298 ; REQ_UDS_0299 ; REQ_UDS_0122 ; REQ_UDS_0124 High Table 72 – Service 0x37 positive response parameter description Artifact ID TABLE-CVS124-0074
Section 5.5.16.2 Positive response
Why it matters Table source context
View details Table 72 – Service 0x37 positive response parameter description
Wide tables scroll horizontally inside this card.
Byte No Description Cvt 1 RequestTransferExit Request SID M
TABLE-CVS124-0075 Table Table 73 – Service 0x29 supported negative response codes Image available: no CVS124.pdf 5.5.18.4.1 page 64 REQ_UDS_0138 ; REQ_UDS_0133 ; REQ_UDS_0134 ; REQ_UDS_0135 ; REQ_UDS_0136 ; REQ_UDS_0137 ; REQ_UDS_0139 ; REQ_UDS_0140 High Table 73 – Service 0x29 supported negative response codes Artifact ID TABLE-CVS124-0075
Section 5.5.18.4.1 Supported negative response codes
Why it matters Diagnostic parameter or service behavior
View details Table 73 – Service 0x29 supported negative response codes
Wide tables scroll horizontally inside this card.
NRC NRC definition 0x50 Certificate verification failed - Invalid Time Period 0x51 Certificate verification failed - Invalid Signature 0x52 Certificate verification failed - Invalid Chain of Trust 0x53 Certificate verification failed - Invalid Type 0x54 Certificate verification failed - Invalid Format 0x55 Certificate verification failed - Invalid Content 0x56 Certificate verification failed - Invalid Scope 0x57 Certificate verification failed – Invalid Certificate (revoked)
View full table (14 rows) NRC NRC definition 0x50 Certificate verification failed - Invalid Time Period 0x51 Certificate verification failed - Invalid Signature 0x52 Certificate verification failed - Invalid Chain of Trust 0x53 Certificate verification failed - Invalid Type 0x54 Certificate verification failed - Invalid Format 0x55 Certificate verification failed - Invalid Content 0x56 Certificate verification failed - Invalid Scope 0x57 Certificate verification failed – Invalid Certificate (revoked) 0x58 Ownership verification failed 0x59 Challenge calculation failed 0x5A Setting Access Rights failed 0x5B Session key creation/derivation failed 0x5C Configuration data usage failed 0x5D DeAuthentication failed
TABLE-CVS124-0076 Table Table 74 – Service 0x38 request parameter modeOfOperation description Image available: no CVS124.pdf 5.5.19.2 page 65 REQ_UDS_0141 ; REQ_UDS_0139 ; REQ_UDS_0140 ; REQ_UDS_0143 ; REQ_UDS_0142 High Table 74 – Service 0x38 request parameter modeOfOperation description Artifact ID TABLE-CVS124-0076
Section 5.5.19.2 Request Parameter modeOfOperation
Why it matters Software update or memory programming context
View details Table 74 – Service 0x38 request parameter modeOfOperation description
Wide tables scroll horizontally inside this card.
Byte value Description Cvt 0x00 ISO Reserved AddFile M 0x01 This value shall be used to add the file (download) defined in the filePathAndName parameter DeleteFile M 0x02 This value shall be used to delete the file defined in the filePathAndName parameter ReplaceFile U 0x03 This value shall be used to replace the file (download) defined in the filePathAndName parameter. If the file is not stored at the location the file shall be added. ReadFile M 0x04 This value shall be used to read the file (upload) at the location defined by the filePathAndName parameter. ReadDir U 0x05 This value shall be used to read the directory defined in the filePathAndName parameter. This value implies that the request does not include a filename. ResumeFile U 0x06 This value shall be used to resume downloading the file defined in the filePathAndName parameter at the returned filePosition indicator. The file specified in the filePathAndName shall already exist in the ECU’s file system. M
TABLE-CVS124-0077 Table Table 75 – Service 0x38 request parameter dataFormatIdentifier description Image available: no CVS124.pdf 5.5.19.4 page 66 REQ_UDS_0143 ; REQ_UDS_0142 ; REQ_UDS_0144 ; REQ_UDS_0145 ; REQ_UDS_0146 ; INFO_UDS_0018High Table 75 – Service 0x38 request parameter dataFormatIdentifier description Artifact ID TABLE-CVS124-0077
Section 5.5.19.4 Request Parameter dataFormatIdentifier
Why it matters Table source context
View details Table 75 – Service 0x38 request parameter dataFormatIdentifier description
Wide tables scroll horizontally inside this card.
Byte value Description Cvt 0x07 – 0xFF ISO Reserved M
TABLE-CVS124-0078 Table Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format Image available: no CVS124.pdf 5.6.1.3 page 67 REQ_UDS_0153 ; REQ_UDS_0152 ; REQ_UDS_0148 ; REQ_UDS_0149 ; REQ_UDS_0150 ; REQ_UDS_0151 ; REQ_UDS_0154 ; REQ_UDS_0155 High Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format Artifact ID TABLE-CVS124-0078
Section 5.6.1.3 Positive response
Why it matters Diagnostic parameter or service behavior
View details Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingPreconditions [byte#1] M 0x22 #4 routineIdentifier (LSB) checkProgrammingPreconditions [byte#2] M 0x03 #5 routineStatus (byte#1) programmingPreconditionList [byte#1] U 0x00-0xFF #5+m-1 routineStatus (byte#m) programmingPreconditionList [byte#m] U 0x00-0xFF
TABLE-CVS124-0079 Table Table 77 – Programming preconditions Image available: no CVS124.pdf 5+m-1 routineStatus (byte#m) programmingPreconditionList page 68 REQ_UDS_0155 ; REQ_UDS_0157 ; REQ_UDS_0156 High Table 77 – Programming preconditions Artifact ID TABLE-CVS124-0079
Section 5+m-1 routineStatus (byte#m) programmingPreconditionList
Why it matters Diagnostic parameter or service behavior
View details Table 77 – Programming preconditions
Wide tables scroll horizontally inside this card.
Hex Description Origin 0x01 Engine speed is not zero 0x02 Engine immobilizer is not released 0x03 Transmission input speed is not zero 0x04 Transmission output speed is not zero 0x05 Vehicle speed is not zero 0x06 Closed-loop control active 0x07 Ignition system off-on required Defined by the “manufacturers 0x08 No programming voltage software initiative” (HIS)
View full table (24 rows) Hex Description Origin 0x01 Engine speed is not zero 0x02 Engine immobilizer is not released 0x03 Transmission input speed is not zero 0x04 Transmission output speed is not zero 0x05 Vehicle speed is not zero 0x06 Closed-loop control active 0x07 Ignition system off-on required Defined by the “manufacturers 0x08 No programming voltage software initiative” (HIS) 0x09 Ignition (terminal 15) is not turned on 0x0A Supply voltage too low 0x0B Temperature too high 0x0C Temperature too low .. …. 0x7F Reserved for HIS 0x80 Selector lever is not in P or N position 0x81 Blocking time for programming is active 0x82 ECU in post-run 0x83 Maximum number of programming cycles reached 0x84 Slave ECU is not present Defined by 0x85 Crash counter is not zero Volkswagen/Audi 0x86 Sub bus system in diagnostics 0x87 Move selector lever into P position 0x88 Message received and invalid 0x89 Engine stop in start-stop mode active
TABLE-CVS124-0080 Table Table 78 – RoutineIdentifier 0xFF00 description Image available: no CVS124.pdf 5.6.2.1 page 70 REQ_UDS_0163 ; REQ_UDS_0161 ; REQ_UDS_0162 ; REQ_UDS_0165 ; REQ_UDS_0164 High Table 78 – RoutineIdentifier 0xFF00 description Artifact ID TABLE-CVS124-0080
Why it matters Diagnostic parameter or service behavior
View details Table 78 – RoutineIdentifier 0xFF00 description
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) addressAndLengthFormatIdentifier (XXXXYYYYb) M 0x00 #5 XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. M 0x00 – 0xFF #6 memoryStartAddress[] = [ : byte#1 (MSB) C1 0x00 – 0xFF #(m-1)+6 : byte#m ] : C1 : 0x00 – 0xFF
View full table (11 rows) Byte Description Cvt Byte Value #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) addressAndLengthFormatIdentifier (XXXXYYYYb) M 0x00 #5 XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. M 0x00 – 0xFF #6 memoryStartAddress[] = [ : byte#1 (MSB) C1 0x00 – 0xFF #(m-1)+6 : byte#m ] : C1 : 0x00 – 0xFF #n-(k-1) memorySize[] = [ : byte#1 (MSB) C2 0x00 – 0xFF #n : byte#k ] : C2 : 0x00 – 0xFF
TABLE-CVS124-0081 Table Table 79 – Request parameter addressAndLengthFormatIdentifier values Image available: no CVS124.pdf 5.6.2.2 page 71 REQ_UDS_0165 ; SUV2_REQ 62; REQ_UDS_0167 ; REQ_UDS_0166 ; REQ_UDS_0164 ; SUV2_REQ 63High Table 79 – Request parameter addressAndLengthFormatIdentifier values Artifact ID TABLE-CVS124-0081
Section 5.6.2.2 Request parameter addressAndLengthFormatIdentifier
Why it matters Software update or memory programming context
View details Table 79 – Request parameter addressAndLengthFormatIdentifier values
Wide tables scroll horizontally inside this card.
Byte Value Description Automatic erase: Erase is performed by boot loader automatically Cvt 0x00 when RequestDownload is received for each Flash sector in the module. Module erase: memoryStartAddress byte is used for module index. C 0x01 memorySize parameter is not used. E.g. 02, Module 2 (Application SW module) M 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M
TABLE-CVS124-0082 Table Table 80 – RoutineControl (EraseMemory) positive response format Image available: no CVS124.pdf 5.6.2.3 page 71 REQ_UDS_0167 ; SUV2_REQ 62; REQ_UDS_0166 ; SUV2_REQ 63; REQ_UDS_0168 ; INFO_UDS_0022High Table 80 – RoutineControl (EraseMemory) positive response format Artifact ID TABLE-CVS124-0082
Section 5.6.2.3 Positive response
Why it matters Diagnostic parameter or service behavior
View details Table 80 – RoutineControl (EraseMemory) positive response format
Wide tables scroll horizontally inside this card.
Byte Value Description Automatic erase: Erase is performed by boot loader automatically Cvt 0x00 when RequestDownload is received for each Flash sector in the module. Module erase: memoryStartAddress byte is used for module index. C 0x01 memorySize parameter is not used. E.g. 02, Module 2 (Application SW module) M 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M
TABLE-CVS124-0083 Table Table 81 – RoutineControl (EraseMemory) routineResult values Image available: no CVS124.pdf 5 routineStatus routineResult M 0x00-0xFF page 72 REQ_UDS_0168 ; INFO_UDS_0022; INFO_UDS_0023High Table 81 – RoutineControl (EraseMemory) routineResult values Artifact ID TABLE-CVS124-0083
Section 5 routineStatus routineResult M 0x00-0xFF
Related requirements REQ_UDS_0168 ; INFO_UDS_0022; INFO_UDS_0023
Why it matters Diagnostic parameter or service behavior
View details Table 81 – RoutineControl (EraseMemory) routineResult values
Wide tables scroll horizontally inside this card.
Hex Description When addressAndLengthFormatIdentifier = 0x00: Cvt 0x00 Erasing will be initiated when RequestDownload service is requested. When addressAndLengthFormatIdentifier > 0x00: Erase operation was completed successfully. M 0x01 Erase operation was unsuccessful. M
TABLE-CVS124-0084 Table Table 82 – Example #1: Request: client → server Image available: no CVS124.pdf 5.6.2.5 page 72 INFO_UDS_0022; INFO_UDS_0023; INFO_UDS_0024 High Table 82 – Example #1: Request: client → server Artifact ID TABLE-CVS124-0084
Section 5.6.2.5 Message flow example(s) RoutineControl (EraseMemory)
Related requirements INFO_UDS_0022; INFO_UDS_0023; INFO_UDS_0024
Why it matters Diagnostic parameter or service behavior
View details Table 82 – Example #1: Request: client → server
Wide tables scroll horizontally inside this card.
Hex Description When addressAndLengthFormatIdentifier = 0x00: Cvt 0x00 Erasing will be initiated when RequestDownload service is requested. When addressAndLengthFormatIdentifier > 0x00: Erase operation was completed successfully. M 0x01 Erase operation was unsuccessful. M
TABLE-CVS124-0085 Table Table 83 – Example #1: Positive response: server → client Image available: no CVS124.pdf 13 memorySize byte#4 (LSB) 0x00 page 73 INFO_UDS_0024; INFO_UDS_0025 High Table 83 – Example #1: Positive response: server → client Artifact ID TABLE-CVS124-0085
Section 13 memorySize byte#4 (LSB) 0x00
Related requirements INFO_UDS_0024; INFO_UDS_0025
Why it matters Diagnostic parameter or service behavior
View details Table 83 – Example #1: Positive response: server → client
Wide tables scroll horizontally inside this card.
Byte Description Byte Value #1 RoutineControl Response SID 0x71 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier (MSB) 0xFF #4 routineIdentifier (LSB) 0x00
TABLE-CVS124-0086 Table Table 84 – Example #1: Negative response: server → client Image available: no CVS124.pdf 4 routineIdentifier (LSB) 0x00 page 73 INFO_UDS_0024; INFO_UDS_0025 High Table 84 – Example #1: Negative response: server → client Artifact ID TABLE-CVS124-0086
Section 4 routineIdentifier (LSB) 0x00
Related requirements INFO_UDS_0024; INFO_UDS_0025
Why it matters Diagnostic parameter or service behavior
View details Table 84 – Example #1: Negative response: server → client
Wide tables scroll horizontally inside this card.
Byte Description Byte Value #1 RoutineControl Response SID 0x71 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier (MSB) 0xFF #4 routineIdentifier (LSB) 0x00
TABLE-CVS124-0087 Table Table 85 – Example #2: Request: client → server Image available: no CVS124.pdf 3 generalProgrammingFailure 0x72 page 73 INFO_UDS_0024; INFO_UDS_0025 High Table 85 – Example #2: Request: client → server Artifact ID TABLE-CVS124-0087
Section 3 generalProgrammingFailure 0x72
Related requirements INFO_UDS_0024; INFO_UDS_0025
Why it matters Diagnostic parameter or service behavior
View details Table 85 – Example #2: Request: client → server
Wide tables scroll horizontally inside this card.
Byte Description Byte Value #1 RoutineControl Response SID 0x71 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier (MSB) 0xFF #4 routineIdentifier (LSB) 0x00
TABLE-CVS124-0088 Table Table 86 – Example #2: Positive response: server → client Image available: no CVS124.pdf 6 memoryStartAddress byte#1 (MSB) 0x03 page 73 INFO_UDS_0025; REQ_UDS_0169 ; REQ_UDS_0170 High Table 86 – Example #2: Positive response: server → client Artifact ID TABLE-CVS124-0088
Section 6 memoryStartAddress byte#1 (MSB) 0x03
Why it matters Diagnostic parameter or service behavior
View details Table 86 – Example #2: Positive response: server → client
Wide tables scroll horizontally inside this card.
Byte Description Byte Value #1 RoutineControl Response SID 0x71 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier (MSB) 0xFF #4 routineIdentifier (LSB) 0x00
TABLE-CVS124-0089 Table Table 87 – Example #2: Negative response: server → client Image available: no CVS124.pdf 4 routineIdentifier (LSB) 0x00 page 74 REQ_UDS_0169 ; REQ_UDS_0170 ; INFO_UDS_0026; REQ_UDS_0171 ; REQ_UDS_0172 High Table 87 – Example #2: Negative response: server → client Artifact ID TABLE-CVS124-0089
Section 4 routineIdentifier (LSB) 0x00
Why it matters Diagnostic parameter or service behavior
View details Table 87 – Example #2: Negative response: server → client
Wide tables scroll horizontally inside this card.
Byte Description Byte Value #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier (MSB) 0xFF #4 routineIdentifier (LSB) 0x00
TABLE-CVS124-0090 Table Table 88 – RoutineControl (Software Installation) positive StartRoutine response format Image available: no CVS124.pdf 5.6.3.2 page 75 REQ_UDS_0176 ; REQ_UDS_0175 ; REQ_UDS_0177 ; REQ_UDS_0178 ; REQ_UDS_0174 High Table 88 – RoutineControl (Software Installation) positive StartRoutine response format Artifact ID TABLE-CVS124-0090
Section 5.6.3.2 Positive Response
Why it matters Diagnostic parameter or service behavior
View details Table 88 – RoutineControl (Software Installation) positive StartRoutine response format
Wide tables scroll horizontally inside this card.
Byte No. Description Cvt Values #1 RoutineControl Request SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0x24 #4 routineIdentifier (LSB) M 0x01
TABLE-CVS124-0091 Table Table 89 – RoutineControl (Software Installation) positive requestRoutineResult response format Image available: no CVS124.pdf 4 routineIdentifier (LSB) M 0x01 page 75 REQ_UDS_0176 ; REQ_UDS_0175 ; REQ_UDS_0177 ; REQ_UDS_0178 High Table 89 – RoutineControl (Software Installation) positive requestRoutineResult response format Artifact ID TABLE-CVS124-0091
Section 4 routineIdentifier (LSB) M 0x01
Why it matters Diagnostic parameter or service behavior
View details Table 89 – RoutineControl (Software Installation) positive requestRoutineResult response format
Wide tables scroll horizontally inside this card.
Byte No. Description Cvt Values #1 RoutineControl Request SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0x24 #4 routineIdentifier (LSB) M 0x01
TABLE-CVS124-0092 Table Table 90 – AuthenticityVerificationStatus Image available: no CVS124.pdf 8-#9 TimeRemaningEstimative M 0x0000 – page 75 REQ_UDS_0177 ; REQ_UDS_0176 ; REQ_UDS_0178 ; REQ_UDS_0180 ; REQ_UDS_0179 High Table 90 – AuthenticityVerificationStatus Artifact ID TABLE-CVS124-0092
Section 8-#9 TimeRemaningEstimative M 0x0000 –
Why it matters Table source context
View details Table 90 – AuthenticityVerificationStatus
Wide tables scroll horizontally inside this card.
Byte No. Description Cvt Values #1 RoutineControl Request SID M 0x71 #2 routineControlType (requestRoutineResults) M 0x03 #3 routineIdentifier (MSB) M 0x24 #4 routineIdentifier (LSB) M 0x01 #5 AuthenticityVerificationStatus M 0x00 – 0xFF #6 SoftwareInstallationStatus M 0x00 – 0xFF #7 CompletionPercentage M 0x00 – 0x64 #8-#9 TimeRemaningEstimative M 0x0000 – 0xFFFF
TABLE-CVS124-0093 Table Table 91 – SoftwareInstallationStatus Image available: no CVS124.pdf 8-#9 TimeRemaningEstimative M 0x0000 – page 76 REQ_UDS_0181 ; REQ_UDS_0180 ; REQ_UDS_0179 ; REQ_UDS_0182 ; INFO_UDS_0027; INFO_UDS_0028; INFO_UDS_0029High Table 91 – SoftwareInstallationStatus Artifact ID TABLE-CVS124-0093
Section 8-#9 TimeRemaningEstimative M 0x0000 –
Why it matters Table source context
View details Table content was not available in the Markdown-derived artifact.
TABLE-CVS124-0094 Table Table 92 – RoutineIdentifier 0xFF01 description Image available: no CVS124.pdf 5.6.4.1 page 77 REQ_UDS_0191 ; REQ_UDS_0190 ; REQ_UDS_0185 ; REQ_UDS_0186 ; REQ_UDS_0187 ; REQ_UDS_0188 ; REQ_UDS_0189 ; REQ_UDS_0192 High Table 92 – RoutineIdentifier 0xFF01 description Artifact ID TABLE-CVS124-0094
Why it matters Diagnostic parameter or service behavior
View details Table 92 – RoutineIdentifier 0xFF01 description
Wide tables scroll horizontally inside this card.
Byte Description Cvt Hex #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x01
TABLE-CVS124-0095 Table Table 93 – RoutineControl (CheckProgrammingDependencies) positive response format Image available: no CVS124.pdf 5.6.4.2 page 78 REQ_UDS_0193 ; INFO_UDS_0030; REQ_UDS_0192 ; REQ_UDS_0191 High Table 93 – RoutineControl (CheckProgrammingDependencies) positive response format Artifact ID TABLE-CVS124-0095
Section 5.6.4.2 Positive response
Why it matters Diagnostic parameter or service behavior
View details Table 93 – RoutineControl (CheckProgrammingDependencies) positive response format
Wide tables scroll horizontally inside this card.
Byte Description Cvt Byte Value #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) checkProgrammingDependencies[byte#1] M 0xFF #4 routineIdentifier (LSB) checkProgrammingDependencies [byte#2] M 0x01 #5 routineStatus routineResult M 0x00-0xFF
TABLE-CVS124-0096 Table Table 94 – CheckProgrammingDependencies routineStatusRecord results Image available: no CVS124.pdf 5 routineStatus routineResult M 0x00-0xFF page 78 INFO_UDS_0030; REQ_UDS_0193 ; REQ_UDS_0192 High Table 94 – CheckProgrammingDependencies routineStatusRecord results Artifact ID TABLE-CVS124-0096
Section 5 routineStatus routineResult M 0x00-0xFF
Why it matters Diagnostic parameter or service behavior
View details Table 94 – CheckProgrammingDependencies routineStatusRecord results
Wide tables scroll horizontally inside this card.
Hex Description Cvt 0x00 correctResult M 0x01 incorrectResult M 0x02 incorrectResult error SW – HW M 0x03 incorrectResult error SW – SW M 0x04 IncorrectResult One or more modules are not programmed or are incorrectly programmed M 0x05 incorrectResult One or more modules failed when verifying the authenticity and integrity of the software M 0x06 – 0xFF Reserved
TABLE-CVS124-0097 Table Table 95 – Example: Request: client → server Image available: no CVS124.pdf 5.6.4.4 page 79 INFO_UDS_0033; REQ_UDS_0194 ; INFO_UDS_0031; INFO_UDS_0032; REQ_UDS_0195 High Table 95 – Example: Request: client → server Artifact ID TABLE-CVS124-0097
Section 5.6.4.4 Message flow example for RoutineControl
Why it matters Diagnostic parameter or service behavior
View details Table 95 – Example: Request: client → server
Wide tables scroll horizontally inside this card.
Byte Description Byte Value #1 RoutineControl Request SID 0x31 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01
TABLE-CVS124-0098 Table Table 96 – Positive response: server → client Image available: no CVS124.pdf 4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01 page 79 REQ_UDS_0194 ; INFO_UDS_0033; INFO_UDS_0031; INFO_UDS_0032; REQ_UDS_0195 ; REQ_UDS_0196 High Table 96 – Positive response: server → client Artifact ID TABLE-CVS124-0098
Section 4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01
Why it matters Diagnostic parameter or service behavior
View details Table 96 – Positive response: server → client
Wide tables scroll horizontally inside this card.
Byte Description Byte Value #1 RoutineControl Request SID 0x31 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01
TABLE-CVS124-0099 Table Table 97 – Fault memory DTC status bits description Image available: no CVS124.pdf 5.7.1 page 80 REQ_UDS_0196 ; REQ_UDS_0197 ; REQ_UDS_0203 ; INFO_UDS_0034; REQ_UDS_0198 ; REQ_UDS_0199 ; REQ_UDS_0200 ; REQ_UDS_0201 High Table 97 – Fault memory DTC status bits description Artifact ID TABLE-CVS124-0099
Section 5.7.1 DTC status bits
Why it matters Diagnostic parameter or service behavior
View details Table 97 – Fault memory DTC status bits description
Wide tables scroll horizontally inside this card.
Bit Description Cvt 0 testFailed M 1 testFailedThisOperationCycle U 2 pendingDTC M 3 confirmedDTC M 4 testNotCompletedSinceLastClear E 5 testFailedSinceLastClear U 6 testNotCompletedThisOperationCycle M 7 warningIndicatorRequested M
TABLE-CVS124-0100 Table Table 98 – J1939-71 timestamp format Image available: no CVS124.pdf 5.7.3 page 81 REQ_UDS_0209 ; INFO_UDS_0035; REQ_UDS_0205 ; REQ_UDS_0206 ; REQ_UDS_0207 ; REQ_UDS_0208 ; REQ_UDS_0210 High Table 98 – J1939-71 timestamp format Artifact ID TABLE-CVS124-0100
Section 5.7.3 Timestamp of occurrence
Why it matters Diagnostic parameter or service behavior
View details Table 98 – J1939-71 timestamp format
Wide tables scroll horizontally inside this card.
Byte Length Name Resolutio Offset Note No n 1 1 byte Seconds 0.25 s/bit 0 2 1 byte Minutes 1 min/bit 0 3 1 byte Hours 1 hr/bit 0 Value 1 identifies January, 4 1 byte Month 1 month/bit 0.25 0 value 2 identifies February and so on Values 1,2,3 and 4 identifes first day of month, 5 1 byte Day days/bit 0 value 5,6,7,8 identifies second day of month and so on Value of 0 identifies year 6 1 byte Year 1 year/bit 1985 1985, value of 1 identifes year 1986 and so on 7 1 byte Local minute offset 1 min/bit -125 Not used in DTC timestamps
View full table (9 rows) Byte Length Name Resolutio Offset Note No n 1 1 byte Seconds 0.25 s/bit 0 2 1 byte Minutes 1 min/bit 0 3 1 byte Hours 1 hr/bit 0 Value 1 identifies January, 4 1 byte Month 1 month/bit 0.25 0 value 2 identifies February and so on Values 1,2,3 and 4 identifes first day of month, 5 1 byte Day days/bit 0 value 5,6,7,8 identifies second day of month and so on Value of 0 identifies year 6 1 byte Year 1 year/bit 1985 1985, value of 1 identifes year 1986 and so on 7 1 byte Local minute offset 1 min/bit -125 Not used in DTC timestamps 8 1 byte Local hour offset 1 hr/bit -125 Not used in DTC timestamps
TABLE-CVS151-0001 Table Table 1 – Pattern Rule Settings Image available: no CVS151.pdf 3.7 page 9 RBAC_REQ 15; RBAC_INFO 22; RBAC_INFO 23; RBAC_REQ 16; RBAC_REQ 17; RBAC_REQ 18; RBAC_INFO 24 High Table 1 – Pattern Rule Settings Artifact ID TABLE-CVS151-0001
Related requirements RBAC_REQ 15; RBAC_INFO 22; RBAC_INFO 23; RBAC_REQ 16; RBAC_REQ 17; RBAC_REQ 18; RBAC_INFO 24
Why it matters Diagnostic parameter or service behavior
View details Table 1 – Pattern Rule Settings
Wide tables scroll horizontally inside this card.
Bit Name Description index 0 Reserved Reserved 0 == This rule is not valid for a UDS-server 1 UDS 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 0 == No confidentiality is required on the diagnostics request 3 Confidentiality 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules. 4-7 N/A Reserved for future use
TABLE-CVS151-0002 Table Table 2 – DID Rule Settings Image available: no CVS151.pdf 3.8 page 10 RBAC_REQ 20; RBAC_INFO 25; RBAC_REQ 21; RBAC_REQ 19; RBAC_INFO 24 High Table 2 – DID Rule Settings Artifact ID TABLE-CVS151-0002
Related requirements RBAC_REQ 20; RBAC_INFO 25; RBAC_REQ 21; RBAC_REQ 19; RBAC_INFO 24
Why it matters Diagnostic parameter or service behavior
View details Table 2 – DID Rule Settings
Wide tables scroll horizontally inside this card.
Bit Name Description index 0 Reserved Reserved 0 == This rule is not valid for a UDS-server 1 UDS 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 0 == No confidentiality is required on the diagnostics request 3 Confidentiality 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules. 0 == This rule is not applicable when the DID is being 4 Read read 1 == This rule is applicable when the DID is being read 0 == This rule is not applicable when the DID is being 5 Write written 1 == This rule is applicable when the DID is being written 0 == This rule is not applicable when the DID is being 6 IO-control used for IO-control 1 == This rule is applicable when the DID is being used for IO-control
View full table (9 rows) Bit Name Description index 0 Reserved Reserved 0 == This rule is not valid for a UDS-server 1 UDS 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 0 == No confidentiality is required on the diagnostics request 3 Confidentiality 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules. 0 == This rule is not applicable when the DID is being 4 Read read 1 == This rule is applicable when the DID is being read 0 == This rule is not applicable when the DID is being 5 Write written 1 == This rule is applicable when the DID is being written 0 == This rule is not applicable when the DID is being 6 IO-control used for IO-control 1 == This rule is applicable when the DID is being used for IO-control 7 N/A Reserved for future use
TABLE-CVS151-0003 Table Table 3 – RID Rule Setting Image available: no CVS151.pdf 3.9 page 11 RBAC_INFO 26; RBAC_REQ 22; RBAC_INFO 27; RBAC_INFO 25; RBAC_REQ 21 High Table 3 – RID Rule Setting Artifact ID TABLE-CVS151-0003
Related requirements RBAC_INFO 26; RBAC_REQ 22; RBAC_INFO 27; RBAC_INFO 25; RBAC_REQ 21
Why it matters Diagnostic parameter or service behavior
View details Table 3 – RID Rule Setting
Wide tables scroll horizontally inside this card.
Bit index Name Description 0 Reserved Reserved 0 == This rule is not valid for a UDS-server 1 UDS 1 == This rule is valid for a UDS-server This bit shall always assume value 1 2 Reserved Reserved 0 == No confidentiality is required on the diagnostics request 3 Confidentiality 1 == Confidentiality is required on the diagnostics request e.g., 0x84 (CVS32) Note: This bit is supported but not used for deny rules. 4 Start 0 == This rule is not applicable when the RID is being started 1 == This rule is applicable when the RID is being started 5 Stop 0 == This rule is not applicable when the RID is being stopped 1 == This rule is applicable when the RID is being stopped 6 Read-results 0 == This rule is not applicable when the RID results are being read 1 == This rule is applicable when the RID results are being read 7 N/A Reserved for future use
TABLE-CVS31-0001 Table Table 1 – Abbreviations Image available: no CVS31.pdf 1.3 page 6 None Low Table 1 – Abbreviations Artifact ID TABLE-CVS31-0001
Section 1.3 Document quirks
Why it matters Diagnostic parameter or service behavior
View details Table 1 – Abbreviations
Wide tables scroll horizontally inside this card.
Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A, NA, N.A Not Applicable MAC Message Authentication Code PKI Public key infrastructure SDT Secured Data Transmission SID Service Identifier CRNG / Cryptographically Random Number Generator
View full table (13 rows) Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A, NA, N.A Not Applicable MAC Message Authentication Code PKI Public key infrastructure SDT Secured Data Transmission SID Service Identifier CRNG / Cryptographically Random Number Generator CSPRNG / Cryptographically Secure Pseudorandom Number Generator CPRNG Cryptographic Pseudorandom Number Generator RBAC Role based access control RBACC Role based access control configuration D-RBACC Diagnostics RBACC
TABLE-CVS31-0002 Table Table 2 – Conventions Image available: no CVS31.pdf 1.3 page 6 None Low Table 2 – Conventions Artifact ID TABLE-CVS31-0002
Section 1.3 Document quirks
Why it matters Table source context
View details Table 2 – Conventions
Wide tables scroll horizontally inside this card.
Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A, NA, N.A Not Applicable MAC Message Authentication Code PKI Public key infrastructure SDT Secured Data Transmission SID Service Identifier CRNG / Cryptographically Random Number Generator
View full table (13 rows) Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A, NA, N.A Not Applicable MAC Message Authentication Code PKI Public key infrastructure SDT Secured Data Transmission SID Service Identifier CRNG / Cryptographically Random Number Generator CSPRNG / Cryptographically Secure Pseudorandom Number Generator CPRNG Cryptographic Pseudorandom Number Generator RBAC Role based access control RBACC Role based access control configuration D-RBACC Diagnostics RBACC
TABLE-CVS31-0003 Table Table 3 – Terms and Definitions Image available: no CVS31.pdf 1.3 page 6 AUTH_INFO 1; AUTH_REQ 1; AUTH_INFO 2 High Table 3 – Terms and Definitions Artifact ID TABLE-CVS31-0003
Section 1.3 Document quirks
Related requirements AUTH_INFO 1; AUTH_REQ 1; AUTH_INFO 2
Why it matters Security protocol or cryptographic context
View details Table 3 – Terms and Definitions
Wide tables scroll horizontally inside this card.
Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A, NA, N.A Not Applicable MAC Message Authentication Code PKI Public key infrastructure SDT Secured Data Transmission SID Service Identifier CRNG / Cryptographically Random Number Generator
View full table (13 rows) Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A, NA, N.A Not Applicable MAC Message Authentication Code PKI Public key infrastructure SDT Secured Data Transmission SID Service Identifier CRNG / Cryptographically Random Number Generator CSPRNG / Cryptographically Secure Pseudorandom Number Generator CPRNG Cryptographic Pseudorandom Number Generator RBAC Role based access control RBACC Role based access control configuration D-RBACC Diagnostics RBACC
TABLE-CVS31-0004 Table Table 4 – Supported subFunctions (ISO 14229-1:2020) Image available: no CVS31.pdf 1.3 page 7 AUTH_REQ 155; AUTH_INFO 1; AUTH_REQ 1; AUTH_INFO 2; AUTH_REQ 2 High Table 4 – Supported subFunctions (ISO 14229-1:2020) Artifact ID TABLE-CVS31-0004
Section 1.3 Document quirks
Related requirements AUTH_REQ 155; AUTH_INFO 1; AUTH_REQ 1; AUTH_INFO 2; AUTH_REQ 2
Why it matters Security protocol or cryptographic context
View details Table 4 – Supported subFunctions (ISO 14229-1:2020)
Wide tables scroll horizontally inside this card.
Name verifyCertificateBidirectional proofOfOwnership deAuthenticate
TABLE-CVS31-0005 Table Table 5 – verifyCertificateBidirectional Request Image available: no CVS31.pdf 3.1.1 page 8 AUTH_REQ 117; AUTH_REQ 45; AUTH_REQ 2; AUTH_INFO 30; AUTH_REQ 118; AUTH_INFO 24; AUTH_REQ 119; AUTH_INFO 27 High Table 5 – verifyCertificateBidirectional Request Artifact ID TABLE-CVS31-0005
Related requirements AUTH_REQ 117; AUTH_REQ 45; AUTH_REQ 2; AUTH_INFO 30; AUTH_REQ 118; AUTH_INFO 24; AUTH_REQ 119; AUTH_INFO 27
Why it matters Security protocol or cryptographic context
View details Table 5 – verifyCertificateBidirectional Request
Wide tables scroll horizontally inside this card.
Field Description Type/Value Cvt Included in proofOfOwnershipServer Authentication Request SID Service ID for Authentication service Initiate request Authentication by 0x29 M Yes SubFunction = verifying the [AuthenticationTask = Certificate and 0x02 M Yes verifyCertificateBidirectional] generating a Proof of Ownership from the server communicationConfiguration NOT USED 0x00 M Yes lengthOfCertificateClient Length parameter for certificateClient uint16 M Yes certificateClient The Certificate to verify uint8[] M Yes lengthOfChallengeClient Length parameter for challengeClient uint16 M Yes
View full table (9 rows) Field Description Type/Value Cvt Included in proofOfOwnershipServer Authentication Request SID Service ID for Authentication service Initiate request Authentication by 0x29 M Yes SubFunction = verifying the [AuthenticationTask = Certificate and 0x02 M Yes verifyCertificateBidirectional] generating a Proof of Ownership from the server communicationConfiguration NOT USED 0x00 M Yes lengthOfCertificateClient Length parameter for certificateClient uint16 M Yes certificateClient The Certificate to verify uint8[] M Yes lengthOfChallengeClient Length parameter for challengeClient uint16 M Yes challengeClient See 3.1.1.1 uint8[] M Yes
TABLE-CVS31-0006 Table Table 6 – verifyCertificateBidirectional Response Image available: no CVS31.pdf 3.1.2 page 10 AUTH_REQ 5; AUTH_REQ 6; AUTH_REQ 174; AUTH_REQ 120; AUTH_INFO 143; AUTH_REQ 7 High Table 6 – verifyCertificateBidirectional Response Artifact ID TABLE-CVS31-0006
Related requirements AUTH_REQ 5; AUTH_REQ 6; AUTH_REQ 174; AUTH_REQ 120; AUTH_INFO 143; AUTH_REQ 7
Why it matters Security protocol or cryptographic context
View details Table 6 – verifyCertificateBidirectional Response
Wide tables scroll horizontally inside this card.
Field Description Type/ Value Cvt Included in proofOfOwnershipServer Authentication Response SID Service ID for Authentication service Initiate request Authentication 0x69 M Yes SubFunction = by verifying the [AuthenticationTask = Certificate and 0x02 M Yes verifyCertificateBidirectional] generating a Proof of Ownership from the server This parameter returns authenticationReturnParameter the result of the procedure on the server. uint8 M Yes lengthOfChallengeServer Length parameter for the following challenge uint16 M Yes challengeServer See 3.1.2.1 uint8[] M Yes lengthOfCertificateServer Length parameter for the following uint16 M Yes
View full table (15 rows) Field Description Type/ Value Cvt Included in proofOfOwnershipServer Authentication Response SID Service ID for Authentication service Initiate request Authentication 0x69 M Yes SubFunction = by verifying the [AuthenticationTask = Certificate and 0x02 M Yes verifyCertificateBidirectional] generating a Proof of Ownership from the server This parameter returns authenticationReturnParameter the result of the procedure on the server. uint8 M Yes lengthOfChallengeServer Length parameter for the following challenge uint16 M Yes challengeServer See 3.1.2.1 uint8[] M Yes lengthOfCertificateServer Length parameter for the following uint16 M Yes certificateServer The Certificate Certificate to verify uint8[] M Yes lengthOfProofOfOwnershipSer Length parameter for ver the following Proof of Ownership uint16 M Yes proofOfOwnershipServer See 3.1.2.2 uint8[] M No lengthOfEphemeralPublicKeyS Length parameter for erver ephemeralPublicKeyS erver. uint16 M Yes ephemeralPublicKeyServer See 3.1.2.3 uint8[] M Yes
TABLE-CVS31-0007 Table Table 7 – proofOfOwnership Request Image available: no CVS31.pdf 3.2.1 page 12 AUTH_REQ 110; AUTH_REQ 116; AUTH_REQ 111; AUTH_REQ 113; AUTH_REQ 114; AUTH_REQ 115; AUTH_REQ 8; AUTH_INFO 31 High Table 7 – proofOfOwnership Request Artifact ID TABLE-CVS31-0007
Related requirements AUTH_REQ 110; AUTH_REQ 116; AUTH_REQ 111; AUTH_REQ 113; AUTH_REQ 114; AUTH_REQ 115; AUTH_REQ 8; AUTH_INFO 31
Why it matters Security protocol or cryptographic context
View details Table 7 – proofOfOwnership Request
Wide tables scroll horizontally inside this card.
Field Description Type/Value Cvt Included in proofOfOwnershipClient Authentication Request SID Service ID for Authentication service 0x29 M Yes SubFunction = Verify request the Proof of [AuthenticationTask = Ownership from the 0x03 M Yes proofOfOwnership] client This field indicates the lengthOfProofOfOwnershipClient length (in octets) of the proofOfOwnershipClient field uint16 M Yes proofOfOwnershipClient See 3.2.1.1 uint8[] M No lengthOfEphemeralPublicKey Length parameter for Client ephemeralPublicKey Client uint16 M Yes
View full table (9 rows) Field Description Type/Value Cvt Included in proofOfOwnershipClient Authentication Request SID Service ID for Authentication service 0x29 M Yes SubFunction = Verify request the Proof of [AuthenticationTask = Ownership from the 0x03 M Yes proofOfOwnership] client This field indicates the lengthOfProofOfOwnershipClient length (in octets) of the proofOfOwnershipClient field uint16 M Yes proofOfOwnershipClient See 3.2.1.1 uint8[] M No lengthOfEphemeralPublicKey Length parameter for Client ephemeralPublicKey Client uint16 M Yes ephemeralPublicKeyClient See 3.2.1.2 uint16 M Yes
TABLE-CVS31-0008 Table Table 8 – proofOfOwnership Response Image available: no CVS31.pdf 3.2.2 page 13 AUTH_REQ 161; AUTH_REQ 160; AUTH_INFO 142; AUTH_INFO 3; AUTH_INFO 140; AUTH_REQ 162; AUTH_INFO 145; AUTH_REQ 124 High Table 8 – proofOfOwnership Response Artifact ID TABLE-CVS31-0008
Related requirements AUTH_REQ 161; AUTH_REQ 160; AUTH_INFO 142; AUTH_INFO 3; AUTH_INFO 140; AUTH_REQ 162; AUTH_INFO 145; AUTH_REQ 124
Why it matters Diagnostic parameter or service behavior
View details Table 8 – proofOfOwnership Response
Wide tables scroll horizontally inside this card.
Field Description Type/Value Cvt Included in sessionKeyInfo Authentication Response SID Service ID for Authentication service 0x69 M Yes SubFunction = Verify request the Proof of [AuthenticationTask = Ownership from the 0x03 M Yes proofOfOwnership] client. This parameter returns authenticationReturnParameter the result of the procedure on the server. uint8 M Yes lengthOfSessionKeyInfo Specifies the length of the field (in octets) uint16 M Yes sessionKeyInfo See 3.2.2.1.1 uint8[] M No
TABLE-CVS31-0009 Table Table 9 – deAuthenticate request message layout Image available: no CVS31.pdf 3.3.1 page 15 AUTH_REQ 96; AUTH_REQ 159; AUTH_INFO 11 High Table 9 – deAuthenticate request message layout Artifact ID TABLE-CVS31-0009
Related requirements AUTH_REQ 96; AUTH_REQ 159; AUTH_INFO 11
Why it matters State-machine or transition behavior
View details Table 9 – deAuthenticate request message layout
Wide tables scroll horizontally inside this card.
Field Description Type/Value Cvt Authentication Request SID Service ID for Authentication service 0x29 M SubFunction = [AuthenticationTask = Subfunction request for request 0x00 M deAuthenticate] to leave the
TABLE-CVS31-0010 Table Table 10 – deAuthenticate response message layout Image available: no CVS31.pdf 3.3.2 page 15 AUTH_REQ 96; AUTH_INFO 32; AUTH_REQ 159; AUTH_REQ 158; AUTH_REQ 130; AUTH_REQ 131 High Table 10 – deAuthenticate response message layout Artifact ID TABLE-CVS31-0010
Related requirements AUTH_REQ 96; AUTH_INFO 32; AUTH_REQ 159; AUTH_REQ 158; AUTH_REQ 130; AUTH_REQ 131
Why it matters State-machine or transition behavior
View details Table 10 – deAuthenticate response message layout
Wide tables scroll horizontally inside this card.
Field Description Type/Value Cvt Authentication Response SID Service ID for Authentication service 0x69 M SubFunction = Subfunction response for request [AuthenticationTask = to leave the 0x00 M deAuthenticate] authenticated state returnValue [] = This parameter returns 0x00 – [authenticationReturnParameter] the result of the procedure on the server. 0xFF M
TABLE-CVS31-0011 Table Table 11 – References Image available: no CVS31.pdf 4.9 page 27 None Low Table 11 – References Artifact ID TABLE-CVS31-0011
Section 4.9 Authentication completion timer
Why it matters Diagnostic parameter or service behavior
View details Table 11 – References
Wide tables scroll horizontally inside this card.
Document designation Title CVS30 X.509 CVS32 0x84 SecuredDataTranmission CVS33 Entity Management Protocol CVS34 EMP – Basic Entity Definitions Specification CVS124 Traton Specification on Unified diagnostic Services (UDS) requirements CVS150 Requirements on using cryptographic algorithms in the vehicle CVS151 RBAC v2 for diagnostic ISO 14229-1:2020 Road vehicles – Unified diagnostic services (UDS) –Part 1: Application layer
View full table (10 rows) Document designation Title CVS30 X.509 CVS32 0x84 SecuredDataTranmission CVS33 Entity Management Protocol CVS34 EMP – Basic Entity Definitions Specification CVS124 Traton Specification on Unified diagnostic Services (UDS) requirements CVS150 Requirements on using cryptographic algorithms in the vehicle CVS151 RBAC v2 for diagnostic ISO 14229-1:2020 Road vehicles – Unified diagnostic services (UDS) –Part 1: Application layer RFC 5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile https://datatracker.ietf.org/doc/html/rfc5280 RFC 7748 Elliptic Curves for Security
TABLE-CVS32-0001 Table Table 1 – Abbreviations Image available: no CVS32.pdf 1.4 page 5 None Low Table 1 – Abbreviations Artifact ID TABLE-CVS32-0001
Why it matters Security protocol or cryptographic context
View details Table 1 – Abbreviations
Wide tables scroll horizontally inside this card.
Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A Not Applicable MAC Message Authentication Code HMAC Hash-based Message Authentication Code HKDF HMAC-based Key Derivation Function SDT SecuredDataTransmission NRC Negative Response Code
View full table (14 rows) Abbreviation Description ECU Electronic Control Unit ID, id, Id Identifier N/A Not Applicable MAC Message Authentication Code HMAC Hash-based Message Authentication Code HKDF HMAC-based Key Derivation Function SDT SecuredDataTransmission NRC Negative Response Code TAG Typically a MAC or similar. A cryptographic element used to ensure authenticity. Carried in the SIGMACBYTE protocol element. PREQARC State variable. Previous REQuest Anti-Replay Counter. The ANTIREPLAYCNT used by the client in the previous SDT request. PRESARC State variable. Previous RESponse Anti-Replay Counter. The ANTIREPLAYCNT used by the server in the previous SDT response. PREQTAG State variable. Previous REQuest TAG. The TAG from the previous SDT request. PSIGENCRYPT State variable. Previous SIGENCRYPT. The SIGENCRYPT used in the previous SDT transaction. PKEY State variable. Previous KEY. The key used in the previous SDT transaction. Covaries with PSIGENCRYPT.
TABLE-CVS32-0002 Table Table 2 – Supported CipherSchemes Image available: no CVS32.pdf 3.2 page 10 SDT_INFO 16; SDT_REQ 20; SDT_REQ 21; SDT_REQ 22; SDT_REQ 17; SDT_REQ 18; SDT_REQ 19; SDT_INFO 19 High Table 2 – Supported CipherSchemes Artifact ID TABLE-CVS32-0002
Section 3.2 Authenticity and Confidentiality
Related requirements SDT_INFO 16; SDT_REQ 20; SDT_REQ 21; SDT_REQ 22; SDT_REQ 17; SDT_REQ 18; SDT_REQ 19; SDT_INFO 19
Why it matters Security protocol or cryptographic context
View details Table 2 – Supported CipherSchemes
Wide tables scroll horizontally inside this card.
CipherScheme SIGENCRYPT Reserved by vehicle manufacturer 0 - 1 SDT_AEAD_CHACHA20_POLY1305 2 SDT_POLY1305 3 Reserved by vehicle manufacturer 4 - 127 Reserved by system supplier 128 - 143 Reserved by ISO 144 – 255
DIAGRAM-32992161-0001 Diagram Open diagram Figure 1 - Position definition Image available: yes 3299216_1.pdf 3.4 page 6 None Low Figure 1 - Position definition Artifact ID DIAGRAM-32992161-0001
Section 3.4 The PP and AP are moving in one direction parallel to the axis “X”. X=0 where the AP is at its
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0002 Diagram Open diagram Figure 2 - Position relations Image available: yes 3299216_1.pdf 3.6 page 7 None Low Figure 2 - Position relations Artifact ID DIAGRAM-32992161-0002
Section 3.6 In Figure 2 - Position relations, the behavior of PP and AP can be seen throughout a stroke.
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0003 Diagram Open diagram Figure 3 - Pushrod positions Image available: yes 3299216_1.pdf 4.3 page 8 4.3 High Figure 3 - Pushrod positions Artifact ID DIAGRAM-32992161-0003
Section 4.3 The clutch actuator shall be able to reach the extreme positions A and B in with the center of
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0004 Diagram Open diagram Figure 4 – ISO view of 3d envelope. (all parts not shown) Image available: yes 3299216_1.pdf 4.4 page 9 53612101 High Figure 4 – ISO view of 3d envelope. (all parts not shown) Artifact ID DIAGRAM-32992161-0004
Section 4.4 ECA shall not interfere with any geometry in the 3D envelope 53612101-1 1_RFQ2030.stp
Related requirements 53612101
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0005 Diagram Open diagram Figure 5 - Gearbox flange Image available: yes 3299216_1.pdf 4.9 page 10 4.9 High Figure 5 - Gearbox flange Artifact ID DIAGRAM-32992161-0005
Section 4.9 The ECA shall be adapted for 2 pcs 10 mm guide pins.
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0006 Diagram Open diagram Figure 6 - Snap in tool space Image available: yes 3299216_1.pdf 4.18 page 11 4.18 High Figure 6 - Snap in tool space Artifact ID DIAGRAM-32992161-0006
Section 4.18 When the cover is assembled it shall not be possible to insert an object larger than Ø0,2 mm
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0007 Diagram Open diagram Figure 7 – Maximum disengage time Image available: yes 3299216_1.pdf 5.1 page 13 REQ 6.4 High Figure 7 – Maximum disengage time Artifact ID DIAGRAM-32992161-0007
Section 5.1 It shall be possible to disengage the clutch in 180ms (= Ts) with accuracy according to req
Related requirements REQ 6.4
Why it matters State-machine or transition behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0008 Diagram Open diagram Figure 8 - Maximum engage time Image available: yes 3299216_1.pdf 5.2 page 14 REQ 6.4 High Figure 8 - Maximum engage time Artifact ID DIAGRAM-32992161-0008
Section 5.2 It shall be possible to engage the clutch in 180ms (=Ts) with accuracy according to re q.5.10,
Related requirements REQ 6.4
Why it matters State-machine or transition behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0009 Diagram Open diagram Figure 9 - Step response. Image available: yes 3299216_1.pdf 5.10 page 16 REQ 5.1 High Figure 9 - Step response. Artifact ID DIAGRAM-32992161-0009
Section 5.10 The actuator shall move the pushrod according to the following points:
Related requirements REQ 5.1
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0010 Diagram Open diagram Figure 9 - Step response Image available: yes 3299216_1.pdf 5.2 page 16 REQ 5.1 High Figure 9 - Step response Artifact ID DIAGRAM-32992161-0010
Section 5.2 and this section.
Related requirements REQ 5.1
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0011 Diagram Open diagram Figure 10 - Step response test cycle Image available: yes 3299216_1.pdf 5.11 page 17 5.11 High Figure 10 - Step response test cycle Artifact ID DIAGRAM-32992161-0011
Section 5.11 Req. 5.10 shall be tested with a step response test cycle, according to description and Figure
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0012 Diagram Open diagram Figure 11 - Release frequency test Image available: yes 3299216_1.pdf 5.12 page 18 REQ 8.1 High Figure 11 - Release frequency test Artifact ID DIAGRAM-32992161-0012
Section 5.12 The ECA shall be able to run the 4 second test cycle in Figure 11 - Release frequency test
Related requirements REQ 8.1
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0013 Diagram Open diagram Figure 12 - Class B exceptions Image available: yes 3299216_1.pdf 5.13 page 19 None Low Figure 12 - Class B exceptions Artifact ID DIAGRAM-32992161-0013
Section 5.13 Under some conditions the requirements for disengage and engage strokes (See req. 5.1, req.
Why it matters State-machine or transition behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0014 Diagram Open diagram Figure 133 A 3. Up to 100 kHz Image available: yes 3299216_1.pdf 7.20 page 29 7.20 High Figure 133 A 3. Up to 100 kHz Artifact ID DIAGRAM-32992161-0014
Section 7.20 Peak current (Ipeak): - - See
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0015 Diagram Open diagram Figure 13 - Max current Image available: yes 3299216_1.pdf 7.21 page 30 None Low Figure 13 - Max current Artifact ID DIAGRAM-32992161-0015
Section 7.21 Inrush current
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0016 Diagram Open diagram Figure 13 - Wake up signal hysteresis Image available: yes 3299216_1.pdf 7.31 page 32 None Low Figure 13 - Wake up signal hysteresis Artifact ID DIAGRAM-32992161-0016
Section 7.31 Hysteresis: 1 - - V
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0017 Diagram Open diagram Figure 14 – Dual function block diagram Image available: yes 3299216_1.pdf 7.33 page 33 None Low Figure 14 – Dual function block diagram Artifact ID DIAGRAM-32992161-0017
Section 7.33 Dual function block diagram as per Figure 14.
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0018 Diagram Open diagram Figure 15 - Reference circuit Image available: yes 3299216_1.pdf 7.38 page 34 7.38 High Figure 15 - Reference circuit Artifact ID DIAGRAM-32992161-0018
Section 7.38 Baud rate for
Why it matters Software update or memory programming context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0019 Diagram Open diagram Figure 16 - Temperature histogram Image available: yes 3299216_1.pdf 8.1 page 37 None Low Figure 16 - Temperature histogram Artifact ID DIAGRAM-32992161-0019
Section 8.1 In Figure 16, the average temperature profile for all trucks is shown. Specific vehicles can run
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0020 Diagram Open diagram Figure 17 - Test procedure I Image available: yes 3299216_1.pdf 10.4 page 41 10.4 High Figure 17 - Test procedure I Artifact ID DIAGRAM-32992161-0020
Section 10.4 For this unit, the following definitions of test procedure I and test procedure II shall be used:
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0021 Diagram Open diagram Figure 18 - Disengage force Image available: yes 3299216_1.pdf 14.33 page 55 None Low Figure 18 - Disengage force Artifact ID DIAGRAM-32992161-0021
Section 14.33 CVS10 Traton customer requirements
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0022 Diagram Open diagram Figure 19 - Engage force Image available: yes 3299216_1.pdf 14.33 page 56 None Low Figure 19 - Engage force Artifact ID DIAGRAM-32992161-0022
Section 14.33 CVS10 Traton customer requirements
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0023 Diagram Open diagram Figure 20 - Test cycle Image available: yes 3299216_1.pdf 14.33 page 58 None Low Figure 20 - Test cycle Artifact ID DIAGRAM-32992161-0023
Section 14.33 CVS10 Traton customer requirements
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0024 Diagram Open diagram Figure 21 – Release Load vs Strokes Image available: yes 3299216_1.pdf 14.33 page 60 None Low Figure 21 – Release Load vs Strokes Artifact ID DIAGRAM-32992161-0024
Section 14.33 CVS10 Traton customer requirements
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-32992161-0025 Diagram Open diagram Figure 22 – Release Load vs Strokes Image available: yes 3299216_1.pdf 14.33 page 61 None Low Figure 22 – Release Load vs Strokes Artifact ID DIAGRAM-32992161-0025
Section 14.33 CVS10 Traton customer requirements
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0001 Diagram Open diagram Figure 1: Overview of relation between specifications Image available: yes CVS123-2.pdf 2.3 page 5 SUV2_INFO 12; SUV2_INFO 10; SUV2_INFO 11 High Figure 1: Overview of relation between specifications Artifact ID DIAGRAM-CVS1232-0001
Section 2.3 Relation to other specifications
Related requirements SUV2_INFO 12; SUV2_INFO 10; SUV2_INFO 11
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0002 Diagram Open diagram Figure 2: Programming Phase #1 - Pre-Programming Step Image available: yes CVS123-2.pdf 5.1.1 page 13 SUV2_INFO 26; SUV2_INFO 27; SUV2_INFO 28; SUV2_INFO 29 High Figure 2: Programming Phase #1 - Pre-Programming Step Artifact ID DIAGRAM-CVS1232-0002
Section 5.1.1 Pre-programming step of phase #1 – Setup vehicle network for programming
Related requirements SUV2_INFO 26; SUV2_INFO 27; SUV2_INFO 28; SUV2_INFO 29
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0003 Diagram Open diagram Figure 3: Programming phase #1 – Programming step Image available: yes CVS123-2.pdf 5.1.2 page 16 SUV2_REQ 28; SUV2_REQ 30; SUV2_INFO 54; SUV2_REQ 29; SUV2_INFO 55; SUV2_INFO 56; SUV2_INFO 57; SUV2_INFO 53 High Figure 3: Programming phase #1 – Programming step Artifact ID DIAGRAM-CVS1232-0003
Section 5.1.2 Programming step of phase #1 – Download of application software and data
Related requirements SUV2_REQ 28; SUV2_REQ 30; SUV2_INFO 54; SUV2_REQ 29; SUV2_INFO 55; SUV2_INFO 56; SUV2_INFO 57; SUV2_INFO 53
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0004 Diagram Open diagram Figure 4: Programming phase #1 – Post-Programming step Image available: yes CVS123-2.pdf 5.1.3 page 19 SUV2_INFO 87; SUV2_INFO 88; SUV2_INFO 90; SUV2_INFO 81; SUV2_INFO 82; SUV2_INFO 89 High Figure 4: Programming phase #1 – Post-Programming step Artifact ID DIAGRAM-CVS1232-0004
Section 5.1.3 Post-Programming step of phase #1 — Re-synchronization of vehicle network
Related requirements SUV2_INFO 87; SUV2_INFO 88; SUV2_INFO 90; SUV2_INFO 81; SUV2_INFO 82; SUV2_INFO 89
Why it matters Software update or memory programming context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0005 Diagram Open diagram Figure 5: diagram for signing of software update results Image available: yes CVS123-2.pdf 8.4.4.3 page 38 SUV2_REQ 177; SUV2_REQ 183; SUV2_REQ 128; SUV2_INFO 141; SUV2_REQ 176; SUV2_REQ 178; SUV2_REQ 173; SUV2_INFO 139 High Figure 5: diagram for signing of software update results Artifact ID DIAGRAM-CVS1232-0005
Section 8.4.4.3 Parameter routineResultProof
Related requirements SUV2_REQ 177; SUV2_REQ 183; SUV2_REQ 128; SUV2_INFO 141; SUV2_REQ 176; SUV2_REQ 178; SUV2_REQ 173; SUV2_INFO 139
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0006 Diagram Open diagram Figure 6: Erased-only bytes of a memory module Image available: yes CVS123-2.pdf 9.2 page 41 SUV2_INFO 126; SUV2_REQ 155; SUV2_INFO 127; SUV2_REQ 156; SUV2_REQ 153; SUV2_REQ 154; SUV2_REQ 157; SUV2_REQ 158 High Figure 6: Erased-only bytes of a memory module Artifact ID DIAGRAM-CVS1232-0006
Section 9.2 Software Verification
Related requirements SUV2_INFO 126; SUV2_REQ 155; SUV2_INFO 127; SUV2_REQ 156; SUV2_REQ 153; SUV2_REQ 154; SUV2_REQ 157; SUV2_REQ 158
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0007 Diagram Open diagram Figure 7 – Received ECU Memory Layout Image available: yes CVS123-2.pdf 9.3 page 47 None Low Figure 7 – Received ECU Memory Layout Artifact ID DIAGRAM-CVS1232-0007
Section 9.3 Software decryption
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0008 Diagram Open diagram Figure 8 – Memory layout Image available: yes CVS123-2.pdf 00AFAAAB page 47 00930000; 00868000 High Figure 8 – Memory layout Artifact ID DIAGRAM-CVS1232-0008
Related requirements 00930000; 00868000
Why it matters Security protocol or cryptographic context
View details same source PDF and page; caption token match
Open diagram DIAGRAM-CVS1232-0009 Diagram Open diagram Figure 9 – Resulting SDSC content transmitted using EMP Image available: yes CVS123-2.pdf 00AFAAAB page 48 None Low Figure 9 – Resulting SDSC content transmitted using EMP Artifact ID DIAGRAM-CVS1232-0009
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0010 Diagram Open diagram Figure 10 - Verification Entry for Module C Image available: yes CVS123-2.pdf 00AFAAAB page 49 None Low Figure 10 - Verification Entry for Module C Artifact ID DIAGRAM-CVS1232-0010
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0011 Diagram Open diagram Figure 11 – Memory layout Image available: yes CVS123-2.pdf 00AFAAAB page 50 00930000; 00868000 High Figure 11 – Memory layout Artifact ID DIAGRAM-CVS1232-0011
Related requirements 00930000; 00868000
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0012 Diagram Open diagram Figure 12 – Resulting SDSC content Image available: yes CVS123-2.pdf 00AFAAAB page 51 None Low Figure 12 – Resulting SDSC content Artifact ID DIAGRAM-CVS1232-0012
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS1232-0013 Diagram Open diagram Figure 13 – Memory layout Image available: yes CVS123-2.pdf 00AFAAAB page 52 None Low Figure 13 – Memory layout Artifact ID DIAGRAM-CVS1232-0013
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS124-0001 Diagram Open diagram Figure 1 - Overview of relation between specifications Image available: yes CVS124.pdf 5.10 page 5 None Low Figure 1 - Overview of relation between specifications Artifact ID DIAGRAM-CVS124-0001
Section 5.10 Session layer performance requirements 83
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS124-0002 Diagram Open diagram Figure 2 -State Diagram Image available: yes CVS124.pdf 5.3 page 27 INFO_UDS_0019; REQ_UDS_0338 ; REQ_UDS_0305 ; REQ_UDS_0337 ; REQ_UDS_0051 High Figure 2 -State Diagram Artifact ID DIAGRAM-CVS124-0002
Section 5.3 Diagnostic sessions requirements
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0001 Diagram Open diagram Figure 1 – Overview Image available: yes CVS151.pdf 3.1 page 4 RBAC_INFO 1; RBAC_INFO 3; RBAC_INFO 2; RBAC_INFO 4; RBAC_INFO 5 High Figure 1 – Overview Artifact ID DIAGRAM-CVS151-0001
Related requirements RBAC_INFO 1; RBAC_INFO 3; RBAC_INFO 2; RBAC_INFO 4; RBAC_INFO 5
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0002 Diagram Open diagram Figure 1 shows a highlevel view of the RBAC concept. Image available: yes CVS151.pdf 3.1 page 4 RBAC_INFO 1; RBAC_INFO 3; RBAC_INFO 2; RBAC_INFO 4; RBAC_INFO 5 High Figure 1 shows a highlevel view of the RBAC concept. Artifact ID DIAGRAM-CVS151-0002
Related requirements RBAC_INFO 1; RBAC_INFO 3; RBAC_INFO 2; RBAC_INFO 4; RBAC_INFO 5
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0003 Diagram Open diagram Figure 2 – Visual representation of the RBACC Image available: yes CVS151.pdf 3.2 page 7 RBAC_REQ 7 High Figure 2 – Visual representation of the RBACC Artifact ID DIAGRAM-CVS151-0003
Section 3.2 Role Based Access Control Configuration
Related requirements RBAC_REQ 7
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0004 Diagram Open diagram Figure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic. Image available: yes CVS151.pdf 3.12 page 12 RBAC_INFO 30; RBAC_REQ 36; RBAC_INFO 28; RBAC_INFO 29; RBAC_REQ 35 High Figure 3 shows the interaction between the diagnostics server and the RBAC enforcer logic. Artifact ID DIAGRAM-CVS151-0004
Related requirements RBAC_INFO 30; RBAC_REQ 36; RBAC_INFO 28; RBAC_INFO 29; RBAC_REQ 35
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0005 Diagram Open diagram Figure 3 – Logic Overview Image available: yes CVS151.pdf 3.12 page 13 RBAC_INFO 30; RBAC_REQ 35 High Figure 3 – Logic Overview Artifact ID DIAGRAM-CVS151-0005
Related requirements RBAC_INFO 30; RBAC_REQ 35
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0006 Diagram Open diagram Figure 4 – RBAC internal logic Image available: yes CVS151.pdf 3.12 page 14 RBAC_INFO 32; RBAC_INFO 33 High Figure 4 – RBAC internal logic Artifact ID DIAGRAM-CVS151-0006
Related requirements RBAC_INFO 32; RBAC_INFO 33
Why it matters State-machine or transition behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0007 Diagram Open diagram Figure 5 – Pattern-rules evaluation Image available: yes CVS151.pdf 3.12 page 15 RBAC_INFO 34; RBAC_REQ 33 High Figure 5 – Pattern-rules evaluation Artifact ID DIAGRAM-CVS151-0007
Related requirements RBAC_INFO 34; RBAC_REQ 33
Why it matters Diagram source context
View details same source PDF and page; caption token match
Open diagram DIAGRAM-CVS151-0008 Diagram Open diagram Figure 6 – DID-rules evaluation Image available: yes CVS151.pdf 3.12 page 16 RBAC_REQ 34 High Figure 6 – DID-rules evaluation Artifact ID DIAGRAM-CVS151-0008
Related requirements RBAC_REQ 34
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0009 Diagram Open diagram Figure 7 – RID-rules evaluation Image available: yes CVS151.pdf 3.12 page 17 RBAC_INFO 37 High Figure 7 – RID-rules evaluation Artifact ID DIAGRAM-CVS151-0009
Related requirements RBAC_INFO 37
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0010 Diagram Open diagram Figure 8 – The full rule evaluation scheme (Figure 5 Figure 6, Figure 7 tied together) Image available: yes CVS151.pdf 3.12 page 18 RBAC_INFO 38; RBAC_REQ 24; RBAC_REQ 25 High Figure 8 – The full rule evaluation scheme (Figure 5 Figure 6, Figure 7 tied together) Artifact ID DIAGRAM-CVS151-0010
Related requirements RBAC_INFO 38; RBAC_REQ 24; RBAC_REQ 25
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0011 Diagram Open diagram Figure 9 – Updating the RBACC using EMP Image available: yes CVS151.pdf 4.1 page 22 None Low Figure 9 – Updating the RBACC using EMP Artifact ID DIAGRAM-CVS151-0011
Section 4.1 Normative references
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS151-0012 Diagram Open diagram Figure 10 – Example Image available: yes CVS151.pdf 4.1 page 26 None Low Figure 10 – Example Artifact ID DIAGRAM-CVS151-0012
Section 4.1 Normative references
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0001 Diagram Open diagram Figure 1 – Specification relationship Image available: yes CVS154.pdf 4.2 page 3 None Low Figure 1 – Specification relationship Artifact ID DIAGRAM-CVS154-0001
Section 4.2 Informative references . 12
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0002 Diagram Open diagram Figure 2 Image available: yes CVS154.pdf 3.1 page 4 DSC_BASE_INFO 2; DSC_BASE_INFO 1; DSC_BASE_INFO 3 High Figure 2 Artifact ID DIAGRAM-CVS154-0002
Related requirements DSC_BASE_INFO 2; DSC_BASE_INFO 1; DSC_BASE_INFO 3
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0003 Diagram Open diagram Figure 2 – DSC structure Image available: yes CVS154.pdf 3.1 page 4 DSC_BASE_INFO 2; DSC_BASE_INFO 1; DSC_BASE_INFO 3 High Figure 2 – DSC structure Artifact ID DIAGRAM-CVS154-0003
Related requirements DSC_BASE_INFO 2; DSC_BASE_INFO 1; DSC_BASE_INFO 3
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0004 Diagram Open diagram Figure 3 – HashCmp Image available: yes CVS154.pdf 3.1.1.1 page 6 DSC_BASE_INFO 7; DSC_BASE_REQ 5 High Figure 3 – HashCmp Artifact ID DIAGRAM-CVS154-0004
Related requirements DSC_BASE_INFO 7; DSC_BASE_REQ 5
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0005 Diagram Open diagram Figure 4 – AESCTR128 Image available: yes CVS154.pdf 3.1.2.1 page 7 DSC_BASE_REQ 11 High Figure 4 – AESCTR128 Artifact ID DIAGRAM-CVS154-0005
Related requirements DSC_BASE_REQ 11
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0006 Diagram Open diagram Figure 4 – ChaCha20 Image available: yes CVS154.pdf 3.1.2.2 page 8 None Low Figure 4 – ChaCha20 Artifact ID DIAGRAM-CVS154-0006
Why it matters Diagram source context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0007 Diagram Open diagram Figure 5 – Item list Image available: yes CVS154.pdf 3.1.3 page 9 DSC_BASE_INFO 17; DSC_BASE_REQ 41; DSC_BASE_REQ 42 High Figure 5 – Item list Artifact ID DIAGRAM-CVS154-0007
Related requirements DSC_BASE_INFO 17; DSC_BASE_REQ 41; DSC_BASE_REQ 42
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS154-0008 Diagram Open diagram Figure 6 – DSC sanity check and verification Image available: yes CVS154.pdf 4.2 page 13 None Low Figure 6 – DSC sanity check and verification Artifact ID DIAGRAM-CVS154-0008
Section 4.2 Informative references
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS31-0001 Diagram Open diagram Figure 1 – Overview of relation between specifications Image available: yes CVS31.pdf 1.1 page 4 1.1 High Figure 1 – Overview of relation between specifications Artifact ID DIAGRAM-CVS31-0001
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS31-0002 Diagram Open diagram Figure 2 – Security concepts (ISO 14229-1:2020) Image available: yes CVS31.pdf 1.1 page 5 None Low Figure 2 – Security concepts (ISO 14229-1:2020) Artifact ID DIAGRAM-CVS31-0002
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS31-0003 Diagram Open diagram Figure 3 – Client certificate validation logic Image available: yes CVS31.pdf 4.1 page 17 AUTH_REQ 9; AUTH_REQ 166; AUTH_REQ 106 High Figure 3 – Client certificate validation logic Artifact ID DIAGRAM-CVS31-0003
Related requirements AUTH_REQ 9; AUTH_REQ 166; AUTH_REQ 106
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS31-0004 Diagram Open diagram Figure 4 – Overview Ephemeral Diffie-Hellman key-exchange Image available: yes CVS31.pdf 4.3 page 22 AUTH_INFO 146; AUTH_REQ 167; AUTH_REQ 168; AUTH_INFO 26; AUTH_REQ 24; AUTH_REQ 33 High Figure 4 – Overview Ephemeral Diffie-Hellman key-exchange Artifact ID DIAGRAM-CVS31-0004
Related requirements AUTH_INFO 146; AUTH_REQ 167; AUTH_REQ 168; AUTH_INFO 26; AUTH_REQ 24; AUTH_REQ 33
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS31-0005 Diagram Open diagram Figure 5 – Overview Image available: yes CVS31.pdf 4.9 page 25 AUTH_INFO 36 Medium Figure 5 – Overview Artifact ID DIAGRAM-CVS31-0005
Section 4.9 Authentication completion timer
Related requirements AUTH_INFO 36
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS31-0006 Diagram Open diagram Figure 6 – Server Handling of Signature Image available: yes CVS31.pdf 4.9 page 26 None Low Figure 6 – Server Handling of Signature Artifact ID DIAGRAM-CVS31-0006
Section 4.9 Authentication completion timer
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS31-0007 Diagram Open diagram Figure 7 – Authentication State Transition Image available: yes CVS31.pdf 4.9 page 28 AUTH_REQ 4; AUTH_REQ 159; AUTH_REQ 1; AUTH_REQ 160; AUTH_REQ 2; AUTH_REQ 161 High Figure 7 – Authentication State Transition Artifact ID DIAGRAM-CVS31-0007
Section 4.9 Authentication completion timer
Related requirements AUTH_REQ 4; AUTH_REQ 159; AUTH_REQ 1; AUTH_REQ 160; AUTH_REQ 2; AUTH_REQ 161
Why it matters State-machine or transition behavior
View details same source PDF and page; caption token match
Open diagram DIAGRAM-CVS32-0001 Diagram Open diagram Figure 1 – SDT Overview Image available: yes CVS32.pdf 1.5 page 6 SDT_INFO 1; SDT_REQ 1; SDT_INFO 2; SDT_INFO 3; SDT_REQ 2; SDT_REQ 3 High Figure 1 – SDT Overview Artifact ID DIAGRAM-CVS32-0001
Related requirements SDT_INFO 1; SDT_REQ 1; SDT_INFO 2; SDT_INFO 3; SDT_REQ 2; SDT_REQ 3
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0002 Diagram Open diagram Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to Image available: yes CVS32.pdf 1.5 page 6 SDT_INFO 2; SDT_INFO 1; SDT_REQ 1; SDT_INFO 3; SDT_REQ 4; SDT_REQ 2; SDT_REQ 3 High Figure 1 shows the layout of an SDT message with its protocol elements (for details refer to Artifact ID DIAGRAM-CVS32-0002
Related requirements SDT_INFO 2; SDT_INFO 1; SDT_REQ 1; SDT_INFO 3; SDT_REQ 4; SDT_REQ 2; SDT_REQ 3
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0003 Diagram Open diagram Figure 2 – Anti-replay protection Image available: yes CVS32.pdf 3.1 page 8 SDT_REQ 12; SDT_REQ 13; SDT_REQ 11; SDT_INFO 9; SDT_INFO 10; SDT_REQ 71; SDT_REQ 9; SDT_INFO 11 High Figure 2 – Anti-replay protection Artifact ID DIAGRAM-CVS32-0003
Section 3.1 Anti-replay Protection and Transaction Coherency
Related requirements SDT_REQ 12; SDT_REQ 13; SDT_REQ 11; SDT_INFO 9; SDT_INFO 10; SDT_REQ 71; SDT_REQ 9; SDT_INFO 11
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0004 Diagram Open diagram Figure 3 – Anti-replay protection and transaction coherency Image available: yes CVS32.pdf 3.1 page 9 SDT_INFO 13; SDT_INFO 16; SDT_REQ 15; SDT_REQ 14; SDT_INFO 14; SDT_INFO 15 High Figure 3 – Anti-replay protection and transaction coherency Artifact ID DIAGRAM-CVS32-0004
Section 3.1 Anti-replay Protection and Transaction Coherency
Related requirements SDT_INFO 13; SDT_INFO 16; SDT_REQ 15; SDT_REQ 14; SDT_INFO 14; SDT_INFO 15
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0005 Diagram Open diagram Figure 3 illustrates transaction coherency and the use of PREQTAG. To avoid mix-up, the Image available: yes CVS32.pdf 3.1 page 9 SDT_INFO 13; SDT_INFO 16; SDT_REQ 15; SDT_REQ 14; SDT_INFO 14; SDT_INFO 15 High Figure 3 illustrates transaction coherency and the use of PREQTAG. To avoid mix-up, the Artifact ID DIAGRAM-CVS32-0005
Section 3.1 Anti-replay Protection and Transaction Coherency
Related requirements SDT_INFO 13; SDT_INFO 16; SDT_REQ 15; SDT_REQ 14; SDT_INFO 14; SDT_INFO 15
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0006 Diagram Open diagram Figure 4 illustrates the switching of CipherSchemes within an SDT sequence. The client has Image available: yes CVS32.pdf 3.2 page 11 SDT_INFO 20; SDT_REQ 21; SDT_REQ 22 High Figure 4 illustrates the switching of CipherSchemes within an SDT sequence. The client has Artifact ID DIAGRAM-CVS32-0006
Section 3.2 Authenticity and Confidentiality
Related requirements SDT_INFO 20; SDT_REQ 21; SDT_REQ 22
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0007 Diagram Open diagram Figure 4 – Change of CipherScheme mid sequence Image available: yes CVS32.pdf 3.2 page 11 SDT_REQ 23; SDT_REQ 24; SDT_REQ 25; SDT_REQ 26; SDT_INFO 21 High Figure 4 – Change of CipherScheme mid sequence Artifact ID DIAGRAM-CVS32-0007
Section 3.2 Authenticity and Confidentiality
Related requirements SDT_REQ 23; SDT_REQ 24; SDT_REQ 25; SDT_REQ 26; SDT_INFO 21
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0008 Diagram Open diagram Figure 5 – Use of HKDF output key material (okm) with SDT_CHACHA20_POLY1305 Image available: yes CVS32.pdf 3.2.2 page 12 SDT_REQ 30; SDT_INFO 24; SDT_REQ 27; SDT_REQ 28; SDT_REQ 29; SDT_INFO 25; SDT_REQ 31; SDT_REQ 32 High Figure 5 – Use of HKDF output key material (okm) with SDT_CHACHA20_POLY1305 Artifact ID DIAGRAM-CVS32-0008
Section 3.2.2 SDT_AEAD_CHACHA20_POLY1305
Related requirements SDT_REQ 30; SDT_INFO 24; SDT_REQ 27; SDT_REQ 28; SDT_REQ 29; SDT_INFO 25; SDT_REQ 31; SDT_REQ 32
Why it matters Security protocol or cryptographic context
View details same source PDF and page; caption token match
Open diagram DIAGRAM-CVS32-0009 Diagram Open diagram Figure 6 – Example of client and server's behavior using SDT_AEAD_CHACHA20_POLY1305 Image available: yes CVS32.pdf 3.2.2.2 page 14 SDT_INFO 27; SDT_INFO 28; SDT_INFO 29; SDT_REQ 42 High Figure 6 – Example of client and server's behavior using SDT_AEAD_CHACHA20_POLY1305 Artifact ID DIAGRAM-CVS32-0009
Section 3.2.2.2 Server Decryption/Encryption
Related requirements SDT_INFO 27; SDT_INFO 28; SDT_INFO 29; SDT_REQ 42
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0010 Diagram Open diagram Figure 7 – Use of HKDF output key material (okm) with SDT_POLY1305 Image available: yes CVS32.pdf 3.2.3 page 15 SDT_REQ 52; SDT_INFO 30; SDT_REQ 49; SDT_REQ 50; SDT_REQ 51; SDT_INFO 49; SDT_REQ 91; SDT_REQ 89 High Figure 7 – Use of HKDF output key material (okm) with SDT_POLY1305 Artifact ID DIAGRAM-CVS32-0010
Section 3.2.3 SDT_POLY1305
Related requirements SDT_REQ 52; SDT_INFO 30; SDT_REQ 49; SDT_REQ 50; SDT_REQ 51; SDT_INFO 49; SDT_REQ 91; SDT_REQ 89
Why it matters Security protocol or cryptographic context
View details same source PDF and page; caption token match
Open diagram DIAGRAM-CVS32-0011 Diagram Open diagram Figure 8 – Example of client and server's behavior using SDT_POLY1305 Image available: yes CVS32.pdf 3.2.3.2 page 17 SDT_INFO 31; SDT_INFO 32; SDT_REQ 61 High Figure 8 – Example of client and server's behavior using SDT_POLY1305 Artifact ID DIAGRAM-CVS32-0011
Section 3.2.3.2 Server Verification/Authentication
Related requirements SDT_INFO 31; SDT_INFO 32; SDT_REQ 61
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0012 Diagram Open diagram Figure 9 shows how the different “layers”1 interact conceptually. Image available: yes CVS32.pdf 3.3 page 18 SDT_INFO 33; SDT_INFO 34; SDT_INFO 35; SDT_INFO 36; SDT_INFO 32 High Figure 9 shows how the different “layers”1 interact conceptually. Artifact ID DIAGRAM-CVS32-0012
Section 3.3 Error- and state-handling
Related requirements SDT_INFO 33; SDT_INFO 34; SDT_INFO 35; SDT_INFO 36; SDT_INFO 32
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0013 Diagram Open diagram Figure 9 – Conceptual overview of SDT error handling Image available: yes CVS32.pdf 3.3 page 18 SDT_INFO 34; SDT_REQ 67; SDT_INFO 33; SDT_INFO 35; SDT_INFO 36 High Figure 9 – Conceptual overview of SDT error handling Artifact ID DIAGRAM-CVS32-0013
Section 3.3 Error- and state-handling
Related requirements SDT_INFO 34; SDT_REQ 67; SDT_INFO 33; SDT_INFO 35; SDT_INFO 36
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0014 Diagram Open diagram Figure 10Figure 10 illustrates error- and state handling in the server’s security sub-layer. The Image available: yes CVS32.pdf 3.3.1 page 18 SDT_REQ 67; SDT_INFO 34; SDT_INFO 33; SDT_INFO 35; SDT_INFO 36 High Figure 10Figure 10 illustrates error- and state handling in the server’s security sub-layer. The Artifact ID DIAGRAM-CVS32-0014
Section 3.3.1 Server’s Behaviour
Related requirements SDT_REQ 67; SDT_INFO 34; SDT_INFO 33; SDT_INFO 35; SDT_INFO 36
Why it matters Diagnostic parameter or service behavior
View details same source PDF and page; caption token match
Open diagram DIAGRAM-CVS32-0015 Diagram Open diagram Figure 10 – Server's error and state handling Image available: yes CVS32.pdf 3.3.1 page 19 SDT_REQ 69; SDT_REQ 68; SDT_REQ 67; SDT_REQ 70 High Figure 10 – Server's error and state handling Artifact ID DIAGRAM-CVS32-0015
Section 3.3.1 Server’s Behaviour
Related requirements SDT_REQ 69; SDT_REQ 68; SDT_REQ 67; SDT_REQ 70
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0016 Diagram Open diagram Figure 11 shows an example where the client sends a RDBI and the server responds with two Image available: yes CVS32.pdf 3.3.1.1 page 21 SDT_INFO 42; SDT_INFO 41; SDT_INFO 44; SDT_REQ 78; SDT_INFO 43; SDT_INFO 40 High Figure 11 shows an example where the client sends a RDBI and the server responds with two Artifact ID DIAGRAM-CVS32-0016
Section 3.3.1.1 SDT transactions with multiple responses
Related requirements SDT_INFO 42; SDT_INFO 41; SDT_INFO 44; SDT_REQ 78; SDT_INFO 43; SDT_INFO 40
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0017 Diagram Open diagram Figure 11 – Example of a multi-response transaction Image available: yes CVS32.pdf 3.3.1.1 page 21 SDT_INFO 41; SDT_REQ 78; SDT_INFO 44; SDT_INFO 42; SDT_INFO 43 High Figure 11 – Example of a multi-response transaction Artifact ID DIAGRAM-CVS32-0017
Section 3.3.1.1 SDT transactions with multiple responses
Related requirements SDT_INFO 41; SDT_REQ 78; SDT_INFO 44; SDT_INFO 42; SDT_INFO 43
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0018 Diagram Open diagram Figure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer. The Image available: yes CVS32.pdf 3.3.2 page 21 SDT_INFO 44; SDT_REQ 78; SDT_INFO 42; SDT_INFO 43 High Figure 12Figure 12 illustrates error- and state handling in the client’s security sub-layer. The Artifact ID DIAGRAM-CVS32-0018
Section 3.3.2 Client’s Behaviour
Related requirements SDT_INFO 44; SDT_REQ 78; SDT_INFO 42; SDT_INFO 43
Why it matters Security protocol or cryptographic context
View details same source PDF and page; caption token match
Open diagram DIAGRAM-CVS32-0019 Diagram Open diagram Figure 12 – The client's error and state handling Image available: yes CVS32.pdf 3.3.2 page 22 SDT_REQ 79; SDT_REQ 80; SDT_REQ 81; SDT_REQ 78; SDT_REQ 82; SDT_INFO 44 High Figure 12 – The client's error and state handling Artifact ID DIAGRAM-CVS32-0019
Section 3.3.2 Client’s Behaviour
Related requirements SDT_REQ 79; SDT_REQ 80; SDT_REQ 81; SDT_REQ 78; SDT_REQ 82; SDT_INFO 44
Why it matters Security protocol or cryptographic context
View details same source PDF and page; figure number match; caption token match
Open diagram DIAGRAM-CVS32-0020 Diagram Open diagram Figure 9.) Image available: yes CVS32.pdf 3.3.2.1 page 29 SDT_REQ 88; SDT_REQ 90; SDT_REQ 91; SDT_REQ 54; SDT_REQ 57; SDT_REQ 58; SDT_REQ 59; SDT_REQ 60 High Figure 9.) Artifact ID DIAGRAM-CVS32-0020
Section 3.3.2.1 Lost and Repeated SDT Messages
Related requirements SDT_REQ 88; SDT_REQ 90; SDT_REQ 91; SDT_REQ 54; SDT_REQ 57; SDT_REQ 58; SDT_REQ 59; SDT_REQ 60
Why it matters Security protocol or cryptographic context
View details same source PDF and page; caption token match
Open diagram