CVS124.pdf · Supplier Evaluation / Capability Assessment · Hardware / Platform
CVS124.pdf · Supplier Evaluation / Capability Assessment · Hardware / Platform
Systems-engineering read of what this document defines for the system - scope, boundaries, interfaces, obligations, and what is still open.
Scope: this supplier evaluation / capability assessment specifies requirement, covering 5 Requirements; 5.2 ECU Identification Requirements; 5.2.1 Used data identifier in order to identify an ECU; 5.3 Diagnostic sessions requirements; 5.4 Data identifier requirements; 5.4.1 Integrity Validation Data DIDs (IVD-DIDs).
System boundary and interfaces: the document constrains 1 interface(s) - OEM/Customer Review Interface; principal functions in scope are Secure software update and flash readiness; Secure communication and freshness protection; Secure software update and flash readiness; Security evidence and traceability; Security evidence and traceability.
Design and security impact: affects Secure software update and flash readiness; Secure communication and freshness protection; Secure software update and flash readiness; Security evidence and traceability; Security evidence and traceability; security capabilities touched: Diagnostic security; Key management; 32 supplier system requirement(s) were derived from this document.
Open for the customer: 5 document-linked open point(s) - mainly Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).; Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.; Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. (sample: 3 of 5) - plus 31 unidentified requirement-like statement(s). Do not baseline these until the customer confirms.
Confidence and limits: High confidence. Categorisation is derived from the converted Markdown (customer IDs, normative wording, and section context); no OCR or downstream PDF analysis is used.
| Theme | Engineering Meaning | Requirement Count | Representative Requirements |
|---|---|---|---|
| Requirement | Groups related document requirements into a single engineering theme. | 376 | RFQX-CVS124-0018; RFQX-CVS124-0019; RFQX-CVS124-0020 |
| System architecture design | Groups related document requirements into a single engineering theme. | 372 | RFQX-CVS124-0001; RFQX-CVS124-0002; RFQX-CVS124-0007 |
| Diagnostics and service access | Defines UDS service behavior, authorization expectations, safe-state checks, and diagnostic evidence. | 211 | RFQX-CVS124-0006; RFQX-CVS124-0014; RFQX-CVS124-0020 |
| System | Groups related document requirements into a single engineering theme. | 205 | RFQX-CVS124-0001; RFQX-CVS124-0002; RFQX-CVS124-0007 |
| Software | Groups related document requirements into a single engineering theme. | 131 | RFQX-CVS124-0014; RFQX-CVS124-0020; RFQX-CVS124-0025 |
| Responsibility and customer approval model | Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk. | 130 | RFQX-CVS124-0003; RFQX-CVS124-0004; RFQX-CVS124-0005 |
| Cybersecurity concept and evidence | Drives cybersecurity concept, risk treatment, verification evidence, and traceability obligations. | 99 | RFQX-CVS124-0003; RFQX-CVS124-0004; RFQX-CVS124-0005 |
| Core ECA system behavior | Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope. | 87 | RFQX-CVS124-0005; RFQX-CVS124-0006; RFQX-CVS124-0011 |
| Section | Requirements | Information | Unknown / Review Needed | Total Items | Critical | Open Points | SSR Links |
|---|---|---|---|---|---|---|---|
| 4 Terms, definitions and abbreviations | 0 | 0 | 0 | 13 | 8 | 2 | 1 |
| -- 4.2 Abbreviations | 0 | 0 | 0 | 9 | 5 | 1 | 0 |
| -- 4.3 Conventions | 0 | 0 | 0 | 4 | 3 | 2 | 1 |
| 5 Requirements | 352 | 42 | 0 | 422 | 66 | 5 | 31 |
| -- 5.2 ECU Identification Requirements | 45 | 9 | 0 | 55 | 2 | 1 | 5 |
| -- -- 5.2.1 Used data identifier in order to identify an ECU | 45 | 9 | 0 | 55 | 2 | 1 | 5 |
| -- 5.3 Diagnostic sessions requirements | 53 | 3 | 0 | 56 | 2 | 1 | 8 |
| -- 5.4 Data identifier requirements | 3 | 1 | 0 | 4 | 0 | 0 | 3 |
| -- -- 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) | 3 | 1 | 0 | 4 | 0 | 0 | 3 |
| -- 5.5 Diagnostic services requirements | 159 | 9 | 0 | 188 | 36 | 4 | 21 |
| -- -- 5.5.1 DiagnosticSessionControl (0x10) service | 8 | 1 | 0 | 11 | 3 | 2 | 4 |
| -- -- 5.5.2 ECUReset (0x11) service | 18 | 1 | 0 | 21 | 6 | 1 | 9 |
| -- -- 5.5.3 CommunicationControl (0x28) service | 11 | 3 | 0 | 15 | 3 | 2 | 4 |
| -- -- 5.5.5 ControlDTCSetting (0x85) service | 8 | 1 | 0 | 9 | 1 | 1 | 4 |
| -- -- 5.5.6 Link Control (0x87) service | 6 | 1 | 0 | 7 | 2 | 0 | 3 |
| -- -- 5.5.7 ReadDataByIdentifier (0x22) service | 7 | 0 | 0 | 7 | 0 | 0 | 3 |
| -- -- 5.5.8 WriteDataByIdentifier (0x2E) service | 10 | 0 | 0 | 11 | 1 | 1 | 5 |
| -- -- 5.5.10 ReadDTCInformation (0x19) service | 29 | 1 | 0 | 38 | 9 | 3 | 6 |
| -- -- 5.5.11 InputOutputControlByIdentifier (0x2F) service | 7 | 0 | 0 | 7 | 0 | 0 | 2 |
| -- -- 5.5.12 RoutineControl (0x31) service | 7 | 0 | 0 | 8 | 1 | 1 | 1 |
| -- -- 5.5.13 Request Download Service (0x34) | 12 | 1 | 0 | 13 | 4 | 0 | 4 |
| -- -- 5.5.14 RequestUpload (0x35) | 2 | 0 | 0 | 2 | 0 | 0 | 0 |
| -- -- 5.5.15 TransferData (0x36) service | 7 | 0 | 0 | 7 | 0 | 0 | 1 |
| -- -- 5.5.16 RequestTransferExit (0x37) service | 8 | 0 | 0 | 8 | 0 | 0 | 2 |
| -- -- 5.5.18 Authentication (0x29) service | 16 | 0 | 0 | 16 | 1 | 1 | 4 |
| -- -- 5.5.19 RequestFileTransfer (0x38) service | 3 | 0 | 0 | 8 | 5 | 1 | 1 |
| -- 5.6 Routine Identifier Requirements | 56 | 15 | 0 | 78 | 19 | 4 | 16 |
| -- -- 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions | 16 | 1 | 0 | 20 | 3 | 3 | 4 |
| -- -- 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) | 13 | 6 | 0 | 20 | 3 | 1 | 7 |
| -- -- 5.6.3 Routine 0x2401 – Software Installation | 25 | 5 | 0 | 33 | 12 | 3 | 11 |
| -- -- 5.6.5 Routine 0xCAFE – EMP | 2 | 3 | 0 | 5 | 1 | 1 | 2 |
| -- 5.7 Fault memory requirements | 23 | 3 | 0 | 26 | 1 | 0 | 3 |
| -- -- 5.7.2 Occurrence counter OCC | 8 | 1 | 0 | 9 | 1 | 0 | 3 |
| -- -- 5.7.3 Timestamp of occurrence | 6 | 1 | 0 | 7 | 0 | 0 | 2 |
| -- -- 5.7.4 Vehicle distance at occurrence | 9 | 1 | 0 | 10 | 0 | 0 | 2 |
| -- 5.10 Session layer performance requirements | 13 | 2 | 0 | 15 | 6 | 1 | 6 |
| 6 Normative references | 24 | 2 | 0 | 26 | 0 | 0 | 0 |
Tables are reconstructed column-correct from the document text layer (no OCR). Diagrams are linked from converted image assets.
| 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 source context
| 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). |
Diagnostic parameter or service behavior
Wide table - scrolls 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 |
| 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 source context
Wide table - scrolls 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 |
| 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 |
Diagnostic parameter or service behavior
Wide table - scrolls 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 |
| 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 |
Diagnostic parameter or service behavior
Wide table - scrolls 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 |
State-machine or transition behavior
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 |
Diagnostic parameter or service behavior
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 |
State-machine or transition behavior
Wide table - scrolls 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 source context
Wide table - scrolls 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 |
Software update or memory programming context
Wide table - scrolls 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 |
Software update or memory programming context
Wide table - scrolls 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 |
Software update or memory programming context
Wide table - scrolls 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 |
State-machine or transition behavior
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 source context
Wide table - scrolls 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 |
Security protocol or cryptographic context
Wide table - scrolls 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 |
State-machine or transition behavior
Wide table - scrolls 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 |
| 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 |
Diagnostic parameter or service behavior
| CVS31 and CVS32 requirements preconditions per service shall be defined by the RBAC |
|---|
| Configuration file in the ECU. |
Diagnostic parameter or service behavior
| Byte value | Description |
|---|---|
| 0x0611-0x0620 | Reserved for collective data identifiers |
| 0xB000 – 0xB1FF | Reserved for TRATON |
| 0xCF00 – 0xCFFF | TRATON data field identifiers |
| 0xF010 | disableDiagnosticClient |
Table source context
| Byte value | Description |
|---|---|
| 0x0611-0x0620 | Reserved for collective data identifiers |
| 0xB000 – 0xB1FF | Reserved for TRATON |
| 0xCF00 – 0xCFFF | TRATON data field identifiers |
| 0xF010 | disableDiagnosticClient |
Diagnostic parameter or service behavior
| Byte value | Description |
|---|---|
| 0x0611-0x0620 | Reserved for collective data identifiers |
| 0xB000 – 0xB1FF | Reserved for TRATON |
| 0xCF00 – 0xCFFF | TRATON data field identifiers |
| 0xF010 | disableDiagnosticClient |
State-machine or transition behavior
| Negative response code 0x22, conditionsNotCorrect , shall be used if a service request is |
|---|
| denied due to insufficient rights according to the RBACC check. |
Diagnostic parameter or service behavior
| Hex (bit 6-0) | Description | Cvt |
|---|---|---|
| 0x01 | hardReset | M |
| 0x02 | keyOffOnReset | C |
Table source context
| Hex (bit 6-0) | Description | Cvt |
|---|---|---|
| 0x01 | hardReset | M |
| 0x02 | keyOffOnReset | C |
Table source context
| 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 source context
| Byte No | Description | Cvt |
|---|---|---|
| 1 | CommunicationControl Request SID | M |
| 2 | controlType | M |
| 3 | communicationType | M |
Table source context
| Byte No | Description | Cvt |
|---|---|---|
| 1 | CommunicationControl Request SID | M |
| 2 | controlType | M |
| 3 | communicationType | M |
Table source context
| Byte No | Description | Cvt |
|---|---|---|
| 1 | CommunicationControl Request SID | M |
| 2 | controlType | M |
| 3 | communicationType | M |
Table source context
| Byte Value | Description | Cvt |
|---|---|---|
| 0x01 | verifyModeTransitionWithFixedParameter | M |
| 0x03 | transitionMode | M |
| 0x40-0x5F | vehicleManufacturerSpecific | U |
State-machine or transition behavior
| Byte Value | Description | Cvt |
|---|---|---|
| 0x01 | verifyModeTransitionWithFixedParameter | M |
| 0x03 | transitionMode | M |
| 0x40-0x5F | vehicleManufacturerSpecific | U |
Table source context
| Hex | Description | Cvt |
|---|---|---|
| 0x01 | reportNumberOfDTCByStatusMask | M |
| 0x02 | reportDTCByStatusMask | M |
| 0x03 | reportDTCSnapshotIdentification | M |
| 0x04 | reportDTCSnapshotRecordByDTCNumber | M |
| 0x06 | reportDTCExtendedDataRecordByDTCNumber | M |
| 0x0F | reportMirrorMemoryDTCByStatusMask | U |
Diagnostic parameter or service behavior
| Hex | Description | Cvt |
|---|---|---|
| 0x10 | reportMirrorMemoryDTCExtendedDataRecordByDTCNumber | U |
| 0x11 | reportNumberOfMirrorMemoryDTCByStatusMask | U |
| 0x12 | reportNumberOfEmissionsRelatedOBDDTCByStatusMask | E |
| 0x13 | reportEmissionsRelatedOBDDTCByStatusMask | E |
| 0x42 | reportWWHOBDDTCByMaskRecord | E |
| 0x55 | reportWWHOBDDTCWithPermanentStatus | E |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
Wide table - scrolls 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| Byte No | Description | Cvt |
|---|---|---|
| 1 | inputOutputControlParameter controlState byte 1 | M C |
| 2 .. 2 + (m-1) | : controlState byte m | : C |
State-machine or transition behavior
| Byte No | Description | Cvt |
|---|---|---|
| 1 | inputOutputControlParameter controlState byte 1 | M C |
| 2 .. 2 + (m-1) | : controlState byte m | : C |
Table source context
| 0x01 | resetToDefault | U |
|---|---|---|
| 0x02 | freezeCurrentState shortTermAdjustment | U |
| 0x03 | Refer to ISO 14229-1 for parameter description. | M |
Diagnostic parameter or service behavior
| 0x01 | resetToDefault | U |
|---|---|---|
| 0x02 | freezeCurrentState shortTermAdjustment | U |
| 0x03 | Refer to ISO 14229-1 for parameter description. | M |
Diagnostic parameter or service behavior
| 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 |
| 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 |
Diagnostic parameter or service behavior
| 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 |
Software update or memory programming context
| 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 source context
| encryptingMethod: | |||
|---|---|---|---|
| 3 - 0 | 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer | M | 0x0 – 0x1 |
Software update or memory programming context
| encryptingMethod: | |||
|---|---|---|---|
| 3 - 0 | 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer | M | 0x0 – 0x1 |
Software update or memory programming context
| encryptingMethod: | |||
|---|---|---|---|
| 3 - 0 | 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer | M | 0x0 – 0x1 |
Table source context
| 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 |
Software update or memory programming context
| 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 source context
| 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 |
Software update or memory programming context
| 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 source context
| Byte No | Description | Cvt |
|---|---|---|
| 1 | RequestTransferExit Request SID | M |
Table source context
| Byte No | Description | Cvt |
|---|---|---|
| 1 | RequestTransferExit Request SID | M |
Table source context
| 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) |
| 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 |
Diagnostic parameter or service behavior
| 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 |
Software update or memory programming context
| Byte value | Description | Cvt |
|---|---|---|
| 0x07 – 0xFF | ISO Reserved | M |
Table source context
| 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 |
Diagnostic parameter or service behavior
| 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) |
| 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 |
Diagnostic parameter or service behavior
| 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 |
| 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 |
Diagnostic parameter or service behavior
| 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 |
Software update or memory programming context
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| Byte | Description | Byte Value |
|---|---|---|
| #1 | RoutineControl Response SID | 0x71 |
| #2 | routineControlType (StartRoutine) | 0x01 |
| #3 | routineIdentifier (MSB) | 0xFF |
| #4 | routineIdentifier (LSB) | 0x00 |
Diagnostic parameter or service behavior
| Byte | Description | Byte Value |
|---|---|---|
| #1 | RoutineControl Response SID | 0x71 |
| #2 | routineControlType (StartRoutine) | 0x01 |
| #3 | routineIdentifier (MSB) | 0xFF |
| #4 | routineIdentifier (LSB) | 0x00 |
Diagnostic parameter or service behavior
| Byte | Description | Byte Value |
|---|---|---|
| #1 | RoutineControl Response SID | 0x71 |
| #2 | routineControlType (StartRoutine) | 0x01 |
| #3 | routineIdentifier (MSB) | 0xFF |
| #4 | routineIdentifier (LSB) | 0x00 |
Diagnostic parameter or service behavior
| Byte | Description | Byte Value |
|---|---|---|
| #1 | RoutineControl Response SID | 0x71 |
| #2 | routineControlType (StartRoutine) | 0x01 |
| #3 | routineIdentifier (MSB) | 0xFF |
| #4 | routineIdentifier (LSB) | 0x00 |
Diagnostic parameter or service behavior
| Byte | Description | Byte Value |
|---|---|---|
| #2 | routineControlType (StartRoutine) | 0x01 |
| #3 | routineIdentifier (MSB) | 0xFF |
| #4 | routineIdentifier (LSB) | 0x00 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 source context
Table content was not available from the extracted artifact.
Table source context
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
| 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 |
Diagnostic parameter or service behavior
Wide table - scrolls 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 |
| 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 |
Diagnostic parameter or service behavior
Diagnostic parameter or service behavior
Diagnostic parameter or service behavior
| Field | Value |
|---|---|
| Source PDF | CVS124.pdf |
| Document Type | Supplier Evaluation / Capability Assessment |
| Domain | Hardware / Platform |
| Scope Summary | 376 confirmed requirements, 31 needing clarification, 44 information, 3 reference items; 32 linked SSRs; 5 linked open points. |
| Main Themes | Requirement; System architecture design; Diagnostics and service access; System; Software (sample: 5 of 8) |
| Does Not Confirm | Customer-owned responsibility, final customer decisions, and unresolved open points remain unconfirmed. |
| Confidence | High |
| Evidence Basis | Markdown-derived requirements and generated RFQX registers; no downstream PDF analysis. |
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| ID | Score | Category | Requirement / Reason | Supplier Position |
|---|---|---|---|---|
| RFQX-CVS124-0039 | 81 | High risk due to unclear OEM/supplier responsibility | Minimum length shall be 8 bytes and the assigned value shall be unique for every unit provided by one supplier per project.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0138 | 81 | High risk due to unclear OEM/supplier responsibility | The application shall respond with NRC 0x22 (conditionsNotCorrect) if communication has not been switched off.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0141 | 81 | High risk due to unclear OEM/supplier responsibility | In this process, it shall end all routines and functions that influence programming and ensure that the server checked for safe state conditions at minimal.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0159 | 81 | High risk due to unclear OEM/supplier responsibility | The implementation of hardReset shall first ensure that data corruption will not occur.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0212 | 81 | High risk due to unclear OEM/supplier responsibility | If this action is necessary then it shall be integrated implicitly into ECU Reset (0x11) Service subfunction 0x02.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0237 | 81 | High risk due to unclear OEM/supplier responsibility | 5.5.10.2.6 Response parameter reportDTCSnapshotRecordByDTCNumber The snapshot data sub-function (0x04) shall have positive response message data and format as specified in Table 67.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0241 | 81 | High risk due to unclear OEM/supplier responsibility | dependent depend ent depende nt U #65+N+M- #66+N+M dataIdentifier 0x0000 – #67+N+M +P Data required by law or regulations Signal dependent depend ent depende nt C1 #68+N+M +P DTCSnapshotRecordNumber#2 (Latest Snapshot captured) 0x02 M #69+N+M +P DTCSnapshotRecordNumberOfIdentifiers#2 0x00 : 0xFF M #70+N+M +P : #70+2*(N +M+P) See specification for DTCSnapshotRecord[]#1 This latest snapshot shall contain the same type of data and format as DTCSnapshotRecord[]#1.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0245 | 81 | High risk due to unclear OEM/supplier responsibility | Table 57 – Extended data sub-function (0x06) positive response message content and format Byte Description Range Resolu tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = reportDTCExtDataRecordByDTCNumber 0x06 M #3 : #6 DTCAndStatusRecord[] = [ DTCHighByte DTCMiddleByte DTCLowByte statusOfDTC ] M #7 DTCExtDataRecordNumber#1 This byte shall be set to value 0x11.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0246 | 81 | High risk due to unclear OEM/supplier responsibility | Byte Description Range Resolu tion This byte shall be set to value 2 and is used to identify the response structure variant #9 Occurrence counter OCC, as described in section 5.7.2 [unsigned integer] 0..127 0 M #10 DTC priority 1 – Highest priority 2 - Second highest priority 3 – Lowest priority 255 – Unknown 1..3, 255 0xFF M #11..#16 Time/Date of the first DTC activation See Table 98 but without byte #7 and #8 M #17..#22 Time/Date of the latest DTC activation M #23..#26 ECU Operational hours at the first DTC activation [4-byte int, big endian] as described in section 5.7.5.2.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0248 | 81 | High risk due to unclear OEM/supplier responsibility | Byte Description Range Resolu tion 0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m #35..#38 Total vehicle distance at the latest DTC activation [4-byte int, big endian] in section 5.7.4.1 Not used for TRATON External engine and marine ECUsFor these ECUs these bytes shall contain default value 0xFF (all bytes).security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0265 | 81 | High risk due to unclear OEM/supplier responsibility | The routine IDs as listed in Table 61 are reserved by TRATON and shall not be used by the system supplier.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-CVS124-0328 | 81 | High risk due to unclear OEM/supplier responsibility | Preconditions to be discussed with the vehicle manufacturer shall include but not be limited to Diag safe state conditions.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.
Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Open Point | Priority | Question / Impact | Required Customer Decision | Recommended Supplier Position | Owner | Status |
|---|---|---|---|---|---|---|
| OP-001 | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).TARA scope and effort stay open; downstream assets, goals and design may rework. | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). | Proceed on the working ECA-ECU interpretation; flag every TARA-scope statement as assumption until confirmed. | OEM / Customer | Open | |
| OP-002 | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.Security-access design and verification scope cannot be frozen; risk of an unprotected diagnostic service. | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. | Implement configurable session/security-access on the ECU and request the customer-confirmed service-to-role table. | Shared (OEM policy / Supplier ECU) | Open | |
| OP-004 | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.Update-control scope and evidence ownership stay open; risk of an unprotected update path. | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. | Implement authenticated, integrity-protected ECU programming with controlled boot/app state; require OEM update-chain definition. | Shared (OEM backend / Supplier ECU) | Open | |
| OP-009 | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.Without an agreed DIA the supplier risks owning customer work products or leaving cybersecurity gaps in the case. | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. | Deliver supplier-owned work products per concept; require a signed DIA/RASIC before treating shared items as supplier scope. | OEM / Customer + Supplier (DIA) | Open | |
| OP-011 | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.Supplier position, estimation, and affected design allocation remain conditional for the listed requirements. | Decide whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context. | Carry the items as customer-confirmation dependencies and review them in the next clarification workshop. | OEM / Customer | Open |
Items carrying a customer requirement ID and a normative (shall/must) statement.
When receiving CommunicationControl service request, Gateway server applications shall ensure quieting down of network to ECUs without diagnostic server which are present in their sub-buses Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 35 Security capability Diagnostic security Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Authentication (0x29) service shall be used for authentication of client and server. Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
The server shall be available for complete diagnostic communication within two seconds after a power on. Details & reviewer feedbackSection 5.9 Performance requirements on CAN Page page 83 Security capability Diagnostic security Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. |
The server implementation shall comply with the following state diagram and the following state Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 26 Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 1
|
Before switching to programming session, the server shall ensure the applicable conditions as per Table 76 - Programming preconditions is checked to ensure the vehicle is in safe condition. Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Feature / Interface Secure software update and flash readiness / None Supplier proposal Partially accept. ECU-side bootloader/update behavior can be implemented after the customer confirms the applicable SUV2 variant, diagnostic programming sequence, security-access expectations, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Servers shall reject a ControlDTCSetting service request (DTC setting type = off) with NRC 0x22 (conditionsNotCorrect) if programming preconditions are not satisfied. Details & reviewer feedbackSection 5.5.5 ControlDTCSetting (0x85) service Page page 37 Feature / Interface Secure software update and flash readiness / None Supplier proposal Partially accept. ECU-side bootloader/update behavior can be implemented after the customer confirms the applicable SUV2 variant, diagnostic programming sequence, security-access expectations, and acceptance criteria. |
The server shall support RoutineControl (CheckProgrammingDependencies) service request formatted according to Table 92. Details & reviewer feedbackSection 5.6.4.1 Request Page page 77 Feature / Interface Secure software update and flash readiness / None Supplier proposal Partially accept. ECU-side bootloader/update behavior can be implemented after the customer confirms the applicable SUV2 variant, diagnostic programming sequence, security-access expectations, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 96 – Positive response: server → client #1 RoutineControl Response SID 0x71 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01 #5 routineStatus (routineResult) 0x00 5.6.5 Routine 0xCAFE – EMP The request and response shall be implemented according to CVS33. Details & reviewer feedbackSection 5.6.5 Routine 0xCAFE – EMP Page page 79 Feature / Interface Secure software update and flash readiness / None Supplier proposal Partially accept. ECU-side bootloader/update behavior can be implemented after the customer confirms the applicable SUV2 variant, diagnostic programming sequence, security-access expectations, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that every server task is finished prior sending a positive response. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 34 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The authenticity and integrity information shall be supplied to the server before the software is updated. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The implementation of the client and the server shall be compliant with ISO 14229-1 with the Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 8 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The server shall implement support for RBAC (Role Based Access Control) based on CVS151. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 25 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The server shall be available for ECU identification within one second after sending positive response message to an ECUReset request. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
The maximum time it takes from the positive response is sent from the server until it responds to new requests shall be agreed with vehicle manufacturer and documented. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
The ECUReset service with requestParameter value 0x01 (hardReset) shall simulate the power-on / start-up sequence performed after a server has been previously disconnected from its power supply (i.e. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 34 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Servers involved in engine start shall not process CommunicationControl service requests until 2 seconds after terminal 15 goes active. Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 35 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The server shall be able to switch baud rate within one second. Details & reviewer feedbackSection 5.5.6 Link Control (0x87) service Page page 38 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
The boot loader shall inherit the selected baud rate if the LinkControl service request was received when the server was executing in the application. Details & reviewer feedbackSection 5.5.6 Link Control (0x87) service Page page 38 Supplier proposal Partially accept. ECU-side bootloader/update behavior can be implemented after the customer confirms the applicable SUV2 variant, diagnostic programming sequence, security-access expectations, and acceptance criteria. |
It shall be mandatory to utilize SPNs & FMIs according to SAE J1939. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 42 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
If the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall start erasing the memory area specified with the RequestDownload request. Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 57 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
If the most recent Erase Memory routine request in the current session was made with the addressAndLengthFormatIdentifier parameter set to value 0x00 the server shall reset the following identification DIDs to their default values: • If boot software download is requested, reset 0xF180, 0xF191 and 0xF187 to default values (some of the DIDs will be automatically erased as a consequence of erasing one or more modules). Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 57 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
If a non-permitted service is requested after the RequestDownload service has started and before RequestTransferExit has been called the server shall respond with NRC 0x12 (sub Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 58 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The server shall support service request formatted according to Table 62. Details & reviewer feedbackSection 5.5.13.1 Request Page page 58 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The server shall respond with a positive response code without erasing memory if the specified memory area has already been completely erased (or is writable) at the time the service is requested. Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 69 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
When the addressAndLengthFormatIdentifier parameter is set to a value > 0x00 the server shall reset the following software and data identification DIDs to their default values (see Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 70 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
If authenticity verification is valid the server shall initiate all necessary steps for installation of the received file. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 74 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The server shall send a response to RoutineIdentifier 0x2401 Software Installation without any further inputs from the client. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 74 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
If authenticity verification fails the server shall send the positive response with AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) set to 0x02 (Authenticity Verification Failed) and SoftwareInstallationStatus bit 7-6 (InstallationStatus) set to 0x02 (Installation Failed). Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 74 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The server shall check whether or not the individual modules are complete and compatible with Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
The consistency check shall be carried out solely by the server. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The server shall verify the authenticity and integrity of the software as a part of the consistency check. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The authenticity and integrity check shall be carried out solely by the server. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter shall increment if it’s value is not at it’s maximum value already. Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
For P2Server, the minimum value shall be 0 ms, a maximum value shall be 50 ms. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 83 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
For P2*Server, the minimum value shall be 0ms, the maximum value shall be 4000ms. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 84 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
The value for P4_Server_max shall be maximum 30 seconds. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 84 Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
The system supplier shall document the implemented value for P4_Server_max. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 84 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Partially accept. Supplier can implement ECU-side UDS/session/security-access behavior; customer must confirm the service-to-role table, diagnostic authorization policy, and acceptance criteria. |
This DID shall be stored under flash memory module in flash memory. Details & reviewer feedbackSection 0x20 Page page 10 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This DID shall be stored under dataset module stored in flash memory. Details & reviewer feedbackSection 0x7E 0x20 Page page 11 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This DID shall be stored under dataset module stored in flash memory. Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 12 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This DID shall be stored under flash memory module in flash memory. Details & reviewer feedbackSection 0x20 Page page 15 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This DID shall report a snapshot of the mileage of the vehicle as received on CAN or other ECU-external source at the first reception of the signal with a good signal status after a software update. Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 20 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This DID shall be stored under flash memory module in flash memory. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 23 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
A default diagnostic session shall be supported. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 23 Security capability Diagnostic security Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
A non-default diagnostic session referred to as “extendedDiagnosticSession” shall be supported. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 23 Security capability Diagnostic security Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Diagnostic sessions not defined in this document shall be agreed with the vehicle manufacturer. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 23 Feature / Interface None / OEM/Customer Review Interface Security capability Diagnostic security Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Diagnostics safe state shall be checked before executing the diagnostics services as per Table 40. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 25 Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
A DiagnosticSessionControl service request with parameter diagnosticSessionType set to ProgrammingSession shall be processed only if normal communication is currently switched off as a result of a previous call to the Communication Control service. Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Response parameter diagnosticSessionType shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.1.2.1 Response parameter diagnosticSessionType Page page 33 Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. |
The ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall simulate the turning of the ignition key off and back on and shall ensure that the values of non-volatile memory locations are preserved and the volatile memory will be initialized. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 34 Security capability Key management Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that the volatile memory buffered data is stored into non volatile memory prior sending a positive response. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 34 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The execution of this service in the application shall only impact the DTC setting - diagnostic tests for safety and degradations shall not be impacted (shall work as normal). Details & reviewer feedbackSection 5.5.5 ControlDTCSetting (0x85) service Page page 37 Security capability Diagnostic security Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. |
If it is necessary to force an explicit transfer of buffered data into non-volatile memory then this shall be supported both with ECU-Reset Service subfunction 0x02 and ignition (IGN) key Off/On (power cycle). Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Security capability Key management Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Once the RequestDownload service has started, only services TesterPresent, ECUReset,TransferData and DiagnosticSessionControl shall be permitted until service RequestTransferExit has been called or until any of these services returns an error. Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 57 Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. |
Negative response format shall be as per ISO 14229-1 5.5.18 Authentication (0x29) service Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
The Authentication (0x29) service shall be implemented according to CVS31 . Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 64 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
For detailed error cases and the mapping to the corresponding NRCs the Authentication service implementation specification CVS31 shall be used. Details & reviewer feedbackSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
In case the non volatile memory area is currently hosting a bootloader copy, meaning there is an ongoing bootloader update procedure, the ECU shall ensure that this memory area shall not be erased until a valid bootloader is flashed in the bootloader memory area. Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 69 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. |
The latest occurrence shall be updated at a change of DTC status bits 0 (testFailed) and 3 Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The latest occurrence shall be updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already. Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The first occurrence shall be updated at the first change of DTC status bits 0 (testFailed) and 3 5.7.4 Vehicle distance at occurrence Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
If diagnostic data is not available in time the ECU should respond with NRC 0x78 (requestCorrectlyReceived-ResponsePending) for maximum allowed time. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 83 Security capability Diagnostic security Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. |
Table 5 -Data identifiers used at ECU identification DID Description/ Name Application Boot loader Changing Def Non- Def Def Ext Prg Ext 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 Details & reviewer feedbackSection 5.2 ECU Identification Requirements 5.2.1 Used data identifier in order to identify an ECU Page page 8 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier 0xF186 Name: ActiveDiagnosticSessionDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 Diagnostic session type 1-Byte-A_UINT32 M 0x00 – 0xFF 0x01 Details & reviewer feedbackSection 5.2.1.4 DID 0xF186 ActiveDiagnosticSessionDataIdentifier Page page 11 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp 0xF1A9 Name: lifetimeECUruntimeAtSoftwareUpdateStamp Byte No Description Format Cvt Byte Value Default Data #1 : #4 Lifetime ECU- runtime at software update stamp Unit: s A_UINT32 M : M : 0xFFFFFFFF C = mandatory for TRATON Standalone and External engines 5.2.1.26 DID 0xF1AA Mileage at software update stamp Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 20 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 31 – Description of DID 0xF1AA Mileage at software update stamp ID Description 0xF1AA Name: mileageAtSoftwareUpdateStamp Byte No Description Format Cvt Byte Value Default Data #1 : #4 Mileage at software update stamp Unit: km Formula: 0,005*X 4-Bytes- A_UINT32 M : M : 0xFFFFFFFF C = Mandatory for ECUs that store Operational data and have access to Vehicle milage information. Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 20 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 32 – Description of DID 0xF1AB Date at software update stamp 0xF1AB Name: dateAtSoftwareUpdateStamp Byte Data Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 21 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier 0xF1D1 Name: RootCertificateIdentifier Byte Data Details & reviewer feedbackSection 5.2.1.32 DID 0xF1D1 RootCertificateIdentifier Page page 22 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The default diagnostic session is referred to as “defaultSession”. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 23 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 39 – Diagnostic service support Service according to ISO 14229-1 Addressin g mode Application Boot loader Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 24 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Diagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing certain diagnostics services. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 25 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
. If a programming request is active (progRequest P2 == true), the server activates the programming session in the bootloader module. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests a change to the ProgrammingSession in the ExtendedSession in the application software, the server sets the progRequest flag to "true", so that after restarting it can be seen, that changing to the ProgrammingSession has been requested. If the SPRMIB was not set a positive response is sent from the application before the transition to Bootloader. The request is only sent physically. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. Applies to terminal 15 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the ExtendedSession in the application software, a restart is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. Applies to terminal 15 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the DefaultSession in the application software, a restart is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If a server exchanges diagnostic messages with the client within the ExtendedSession and state terminal 15 ON, the following step is performed if there is a change to terminal 15 OFF and response in progress was finished: Return to DefaultSession after an already started response message has been completely sent to the client. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If there is a state change from terminal 15 ON to terminal 15 OFF while a server exchanges diagnostic messages with the client within the DefaultSession, the server stops the communications with the client after sending the complete response to the last request. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. Applies to terminal 30 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the ExtendedSession in the application software, a change to the DefaultSession is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. Applies to terminal 30 powered servers: If the client requests an ECUReset with the sub-function KeyOffOnReset (0x02) in the DefaultSession in the application software, the server accepts the request and remains in the DefaultSession. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests an ECUReset (0x11) with the sub-function KeyOffOnReset (0x02) in the DefaultSession in the boot loader, the reset is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests an ECUReset (0x11) with the sub-function KeyOffOnReset (0x02) in a Non-DefaultSession in the boot loader, the reset is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.1.1.1 Request parameter diagnosticSessionType Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 43 – Service 0x10 request parameter diagnosticSessionType description Hex (bit 6-0) Description Cvt 0x01 defaultSession M 0x02 ProgrammingSession M 0x03 extendedDiagnosticSession M Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
After a final positive response has been sent for ECUReset the server is not allowed to respond to any diagnostic service requests (except ECU identification) until it has restarted and been re- initialized. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Table 44 – Service 0x11 request parameter resetType description Hex (bit 6-0) Description Cvt 0x01 hardReset M 0x02 keyOffOnReset C C = If the server is connected to the ignition key Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 34 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.9 ClearDiagnosticInformation (0x14) service 5.5.9.1 Request Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 41 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 61 – Service 0x31 request parameter RoutineIdentifier description 0x02B2 0x02B3 0x02B4 ReadStatusOfDiagnosticEventCodes Details & reviewer feedbackSection 5.5.12 RoutineControl (0x31) service Page page 56 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 79 – Request parameter addressAndLengthFormatIdentifier values Byte Value Description Cvt 0x00 Automatic erase: Erase is performed by boot loader automatically when RequestDownload is received for each Flash sector in the module. Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 71 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3 Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
The latest distance value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already. Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
The first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3 Details & reviewer feedbackSection 5.7.4.2 First occurrence Page page 82 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
The latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1. Details & reviewer feedbackSection 5.7.5.1 Latest occurrence Page page 83 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
The latest operational hours value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 83 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
The first operational hours value is updated at the first change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1. Details & reviewer feedbackSection 5.7.5.2 First occurrence Page page 83 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Updated the document references Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
0XCAFE and 0xFF02 are updated to Mandatory Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infos Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
All deviations and extensions shall be agreed with the applicable vehicle manufacturer and shall be documented. Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 8 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 13 – Description of DID 0xF18A systemSupplierIdentifierDataIdentifier 0xF18A Name: systemSupplierIdentifierDataIdentifier Byte No Description Format Cvt Byte Value Default Data To be specifie d by the Content and format to be specified by the supplier Should be M : M : 5.2.1.9 DID 0xF18B ECUManufacturingDateDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 13 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This DID shall contain a snapshot of the mandatory lifetime ECU-runtime operational data Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 20 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Of a marked service, an execution shall be implemented for the specified session as perTable 39. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 23 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The mapping of RoutineControl service routines to sessions shall be discussed and agreed with the vehicle manufacturer. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 25 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
CVS31 and CVS32 requirements preconditions per service shall be defined by the RBAC Configuration file in the ECU. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 25 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The session transitions stated below shall be possible to request both physically or functionally Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 27 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
Project specific DID shall be added to ranges defined as system supplier specific in ISO 14229 Details & reviewer feedbackSection 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Page page 31 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which shall only be implemented in agreement with the vehicle manufacturer. Details & reviewer feedbackSection 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Page page 31 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
These ECUs shall implement the following DIDs according to Table 42. Details & reviewer feedbackSection 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Page page 31 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
The SPRMIB shall be supported for services as specified in (ISO 14229-1). Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Negative response codes specified in ISO 14229-1 Annex A.1 shall only be supported if explicitly specified by this specification or its normative references. Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Negative response code 0x22, conditionsNotCorrect , shall be used if a service request is denied due to insufficient rights according to the RBACC check. Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Following an accepted request to switch to the ProgrammingSession, the application shall make all preparations to guarantee trouble-free programming operation. Details & reviewer feedbackSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Positive response shall be sent before the actual switch in case switching to Programming session. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. |
Response parameter sessionParameterRecord shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.1.2.2 Response parameter sessionParameterRecord Page page 33 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
An ECUReset shall not be executed if the vehicle safety can be compromised. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Feature / Interface None / External Interfaces Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
ECU shall execute the reset only after sending a positive response to the ECU reset service Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
After ECU reset, ECU shall be restarted and re-initialized within 2sec. Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Response parameter resetType shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 35 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Safety conditions are project specific and shall be checked before accepting a request to disable communication. Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 35 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
If the parameter suppressPosRespMsgIndicationBit = true in a functionally addressed request message, the service request shall not influence any ongoing physically addressed service Details & reviewer feedbackSection 5.5.5 ControlDTCSetting (0x85) service Page page 37 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Request format and parameter shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.4.2 Request Page page 37 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Positive response shall be sent before the actual switch of the baud-rate takes place. Details & reviewer feedbackSection 5.5.6 Link Control (0x87) service Page page 38 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 51 – Service 0x87 request parameter linkControlModeIdentifier description Byte Value Description Cvt 0x11 CAN250000Baud C 0x12 CAN500000Baud C 0x13 CAN1000000Baud C C = Baud rates shall be defined by the Project representative. Details & reviewer feedbackSection 5.5.7 ReadDataByIdentifier (0x22) service Page page 39 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
If ECU supports request containing more than one data identifier it shall be documented (like in CDD, ODX etc). Details & reviewer feedbackSection 5.5.7 ReadDataByIdentifier (0x22) service Page page 39 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
DataIdentifier parameter definition shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.7.1.1 Request parameter dataIdentifier Page page 39 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The data identifier ranges specified in Table 41 shall be followed. Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
The sequence of writing data records with service 0x2E WriteDataByIdentifier shall be independent of any specific order Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
All changed data shall be valid and stored into non-volatile memory at the latest after an ECU Reset(0x11) subfunction 0x02 requested from client. Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Request format and parameter shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.8.1 Request Page page 40 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
groupOfDTC parameter definition shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 41 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
ReportNumberOfDTCByStatusMask parameter format shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.1.2 Request parameter reportNumberOfDTCByStatusMask Page page 42 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
DTCStatusMask parameter format shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.1.3 Request parameter DTCStatusMask Page page 42 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
DTCSnapshotRecordNumber parameter format shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.1.5 Request parameter DTCSnapshotRecordNumber Page page 42 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Response parameter FunctionalGroupIdentifier shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 43 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
DTCSeverityMaskRecord parameter format shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.1.8 Request parameter DTCSeverityMaskRecord Page page 43 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
DTCSeverityMask parameter format shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.1.9 Request parameter DTCSeverityMask Page page 43 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Response parameter DTCStatusAvailabilityMask shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 43 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Response parameter DTCFormatIdentifier shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.2.2 Response parameter DTCFormatIdentifier Page page 43 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Response parameter DTCCount shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.2.3 Response parameter DTCCount Page page 43 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Response parameter DTCAndStatusRecord shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 44 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Response parameter DTCRecord shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.2.5 Response parameter DTCRecord Page page 44 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 55 – Snapshot data sub-function (0x04) positive response message content and format Range tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = [ reportDTCSnapshotRecordByDTCNumber ] = 0x04 M #3 : #6 DTCAndStatusRecord[] = [ Byte 1: DTCHighByte Byte 2: DTCMiddleByte Byte 3: DTCLowByte Byte 4: statusOfDTC 0xFF 0xFF 0xFF 0xFF M M M M #7 DTCSnapshotRecordNumber#1 This byte shall be set to value 0x01. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 44 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
DTCSnapshotRecordNumber#1 & DTCSnapshotRecordNumber#2 shall correspond to first time DTC happened and latest time DTC happened correspondingly. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 50 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The extended data sub-function (0x06) shall have the positive response message data and format specified in Table 68. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 51 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Response parameter FunctionalGroupIdentifier shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.2.9 Response parameter FunctionalGroupIdentifier Page page 53 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Response parameter DTCSeverityAvailabilityMask shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.10.2.10 Response parameter DTCSeverityAvailabilityMask Page page 53 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Response parameter DTCAndSeverityRecord shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.11 InputOutputControlByIdentifier (0x2F) service Page page 54 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Negative response codes shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.11 InputOutputControlByIdentifier (0x2F) service Page page 54 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The data identifier ranges specified in ISO 14229-1 shall be followed. Details & reviewer feedbackSection 5.5.11 InputOutputControlByIdentifier (0x2F) service Page page 54 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
ControlEnableMaskRecord parameter format shall be as per ISO 14229-1. Details & reviewer feedbackSection M 5.5.11.1.4 Request parameter controlEnableMaskRecord Page page 55 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Request parameter routineIdentifier shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.12.1.2 Request parameter RoutineIdentifier Page page 55 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Request parameter routineControlOptionRecord shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.12.1.3 Request parameter RoutineControlOptionRecord Page page 57 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
MemoryAddress parameter definition shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.15 TransferData (0x36) service Page page 61 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
MemorySize parameter definition shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.14.1.4 Request parameter memorySize Page page 61 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Refer to ISO 14229-1 for negative response format and codes shall be as per ISO 14229-1. Details & reviewer feedbackSection M 0 5.5.14.3 Negative response Page page 61 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
MemoryAddress parameter definition shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.16 RequestTransferExit (0x37) service Page page 62 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
MemorySize parameter definition shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.15.1.2 Request parameter transferRequestParameterRecord Page page 62 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The transferRequestParameterRecord shall not be supported. Details & reviewer feedbackSection 5.5.16 RequestTransferExit (0x37) service Page page 62 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The transferRequestParameterRecord shall not be supported. Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
This service shall be used when transmitting data in a secured mode, see CVS32. Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Data parameter definition shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Positive response shall be as per CVS32. Details & reviewer feedbackSection 5.5.17.2 Positive response Page page 63 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Negative response shall be as per CVS32 5.5.17.3.1 Supported negative response codes Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Supported negative response codes shall be as per ISO 14229-1, especially the NRC range 0x50 – 0x5D according to Table 73. Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 64 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 74 – Service 0x38 request parameter modeOfOperation description Byte value Description Cvt 0x00 ISO Reserved M 0x01 AddFile This value shall be used to add the file (download) defined in the filePathAndName parameter M 0x02 DeleteFile This value shall be used to delete the file defined in the filePathAndName parameter U 0x03 ReplaceFile This value shall be used to replace the file (download) defined in the filePathAndName parameter. Details & reviewer feedbackSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Refer to ISO 14229-1 for parameter sub-function format shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 66 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Supported negative response codes shall be as per ISO 14229-1. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 66 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The programming preconditions shall be agreed with the vehicle manufacturer. Preconditions to Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Feature / Interface Secure software update and flash readiness / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. |
The decision on conditions of the programming precondition shall be based on minimum two independent sources of information. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
If information is not available for checking a programming precondition the programming precondition shall be considered fulfilled. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
This routine shall be supported in Extended session of both Application and Boot. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Request parameter RoutineControlOptionRecord shall not be supported. Details & reviewer feedbackSection 5.6.1.1 Request 5.6.1.2 Request parameter RoutineControlOptionRecord Page page 67 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Each routineStatus byte shall represent one not satisfied precondition according to Table 18 (see definition of “Satisfied programming precondition”). Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Which ones of the programming precondition codes in Table 18 that need to be supported shall Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 68 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
If all preconditions are satisfied, no routineStatus byte shall be reported. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 68 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Programming preconditions that do not map to one of the entries in Table 77 shall be discussed with the vehicle manufacturer. Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 68 Feature / Interface Secure software update and flash readiness / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The erasing of memory shall not prevent the client from starting a data transfer using the TransferData (0x36) service, i.e. Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 70 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
This routine shall be supported in Programming session. Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 70 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported 5.6.2.2 Request parameter addressAndLengthFormatIdentifier Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 71 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
When the addressAndLengthFormatIdentifier is set to 0x01 the following defined module to index mapping shall apply for the memoryStartAddress: 1 – Boot loader 2 – Application 3 – Application Data 4 ... Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 71 Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The routineResult byte values shall be as specified in Table 81. Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 72 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This routine shall be supported in Programming session. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 74 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. |
Request parameter RoutineControlOptionRecord shall not be supported. Details & reviewer feedbackSection 5.6.3.1 Request Page page 74 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Positive responses to RoutineControl (Software Installation) service requests shall be formatted Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 75 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
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 AuthenticityVerificationStatus shall be formatted according to Table 90. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 75 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) shall remain as 0x0 (Software Authenticity Invalid) until the verification completes. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 75 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
If no authenticity verification will take place as part of RoutineIdentifier, the AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) shall be changed to 0x1 (Authenticity Verification Successful). Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 75 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
SoftwareInstallationStatus shall be formatted according to Table 91. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 76 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
SoftwareInstallationStatus bit 7-6 (InstallationStatus) shall remain as 0x0 (Installation On-going) until the installation completes. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 76 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 91 – SoftwareInstallationStatus Bit Bit Name Bit Values Description 7-6 InstallationStatus 0x0: Installation On-going 0x1: Installation Successful 0x2: Installation Failed 5 - 3 InstallationFailureType 0x0: No Failures 0x1 – 0x7: Project Specific 2 ResetRequired 0x0: Reset not required 0x1: Reset required 1 - 0 Reserved Note: Shall be kept as 0x0 CompletionPercentage shall inform the progress percentage of the software has been installed in the partition memory area. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 76 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
TimeRemaningEstimative shall inform the time estimative to complete the installation of the file. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 76 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The method used to check compatibility/consistency shall be determined by the supplier in consultation with the vehicle manufacturer. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
This routine shall be supported in Programming session. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 92 – RoutineIdentifier 0xFF01 description 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 Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Positive responses to RoutineControl (CheckProgrammingDependencies) service requests shall be formatted according to Table 93. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 78 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 93 – RoutineControl (CheckProgrammingDependencies) positive response format #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 Parameter routineResult shall adopt one of the values specified in Table 94. Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 78 Feature / Interface Secure software update and flash readiness / None Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This routine shall be supported in all sessions of Application and Boot. Details & reviewer feedbackSection 5.6.5 Routine 0xCAFE – EMP Page page 79 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
DTC status bits shall not make use of any vehicle manufacturer specific reset condition (e.g. Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter minimum value shall be zero (0). Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter maximum value shall be 126. Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter default value shall be zero (0). Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter shall increment by one (1) only. Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter shall increment at a change of DTC status bits 0 testFailed and 3 confirmedDTC both from 0 to 1. Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter shall increment at a change of DTC status bit 0 testFailed from 0 to 1, Details & reviewer feedbackSection 5.7.3 Timestamp of occurrence Page page 81 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
The occurrence counter shall increment at a change of DTC status bit 3 confirmedDTC from 0 to 1, if bit 0 testFailed is 1 already. Details & reviewer feedbackSection 5.7.3 Timestamp of occurrence Page page 81 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The occurrence counter value 127 shall be defined as "errors with the counter". Details & reviewer feedbackSection 5.7.3 Timestamp of occurrence Page page 81 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The timestamp default value shall be a 0xFF in each data. Details & reviewer feedbackSection 5.7.3 Timestamp of occurrence Page page 81 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
If occurrence counter is set to 1, the timestamp of the latest occurrence shall be set to 0xFF. Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
The vehicle distance shall be represented by a four byte integer, big endian, with five meter per bit (5m/bit). Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies. |
If all sources of vehicle distance information present no current data, the distance information shall be set to 0xFF at all bytes. Details & reviewer feedbackSection 5.7.4 Vehicle distance at occurrence Page page 82 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
If all sources of operational hours information present no current data, the operational hours information shall be set to 0xFF at all bytes. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 83 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
For P2Client, a value of 150 ms shall be used. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 83 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
For P2*Client, the value estimation given in ISO 14229-2 shall be used. Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 84 Supplier proposal Accept with assumption. Implement the ECU-side diagnostic behavior with configurable authorization and verification evidence, subject to customer-confirmed UDS service allocation and role model. |
Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier 0xF180 Name : bootSoftwareIdentificationDataIdentifier Byte Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 10 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier 0xF181 Name : applicationSoftwareIdentificationDataIdentifier Byte Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application software identifier #1: : M 0x7E 0x7E 0x20 : : : #n – 12 : #n Application software identifier #m: : C 0x7E 0x7E 0x20 Details & reviewer feedbackSection 5.2.1.2 DID 0xF181 applicationSoftwareIdentificationDataIdentifier Page page 10 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 11 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier 0xF182 Name: applicationDataIdentificationDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application data module part number #1: : 13 Bytes- M : M 0x7E . Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 11 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier 0xF187 Name: vehicleManufacturerSparePartNumberDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 : #13 Vehicle manufacturer sparepart number : G, M : M 0x7E : 0x7E 0x20 Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 12 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier 0xF188 Name: vehicleManufacturerECUSoftwareNumberDataIdentifier Byte Data #1 : #13 Vehicle manufacturer ECU (server) software number : M : M : 0x20 Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 12 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.2.1.7 DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 12 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 12 – Description of DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier 0xF189 Name: vehicleManufacturerECUSoftwareVersionNumberDataIdentifier Byte Data Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 12 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.2.1.8 DID 0xF18A systemSupplierIdentifierDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 13 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier 0xF18B Name: ECUManufacturingDateDataIdentifier Byte Data #1 . Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 13 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier 0xF18C Name: ECUSerialNumberDataIdentifier Byte Data Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 14 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 16 – Description of DID 0xF190 VINDataIdentifier 0xF190 Name: VINDataIdentifier Byte Data #1 : #17 VIN number : Byte #17 17-Bytes- M : M : 0x30 . Details & reviewer feedbackSection 5.2.1.11 DID 0xF190 VINDataIdentifier Page page 14 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier 0xF191 Name: vehicleManufacturerECUHardwareNumberDataIdentifier Byte Data Details & reviewer feedbackSection 5.2.1.12 DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier Page page 14 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier 0xF192 Name: systemSupplierECUHardwareNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.14 DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 15 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier 0xF193 Name: systemSupplierECUHardwareVersionNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.15 DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 15 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier 0xF194 Name: systemSupplierECUSoftwareNumberDataIdentifier Byte No Description Format Cvt Byte Value Data To be specified by the External Supplier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 15 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
DID 0xF197 systemNameOrEngineTypeDataIdentifier Details & reviewer feedbackSection 5.2.1.18 DID 0xF197 systemNameOrEngineTypeDataIdentifier Page page 16 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier 0xF195 Name: systemSupplierECUSoftwareVersionNumberDataIdentifier Byte Data To be specified by the External supplier 5.2.1.17 DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 16 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier 0xF196 Name: exhaustRegulationOrTypeApprovalNumberDataIdentifier Cvt: E Byte Data #1 : #10 Exhaust regulation or type approval 10-Bytes- M : M : 0000000 000 5.2.1.18 DID 0xF197 systemNameOrEngineTypeDataIdentifier Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 16 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 4 | Linked diagrams: 0
|
Table 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier 0xF197 Name: systemNameOrEngineTypeDataIdentifier Byte Data #1 : #22 System name or engine type 6-to-22-Bytes- G, M : C : 0x20 . Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 16 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
DID 0xF198 SoftwareItemSemanticDataIdentifiers Details & reviewer feedbackSection 5.2.1.19 DID 0xF198 SoftwareItemSemanticDataIdentifiers Page page 17 Feature / Interface Secure communication and freshness protection / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s 0xF199 Name: SoftwareAssemblySemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01 Details & reviewer feedbackSection 5.2.1.20 DID 0xF199 SoftwareAssemblySemanticDataIdentifiers Page page 17 Feature / Interface Secure communication and freshness protection / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers 0xF19A Name: HardwareSemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01 #4 : #n+3 HardwareSemantic Data Identifier #1: : byte #n* A_ASCIISTR ING, zero M 0x00, 0x20 – 0x7E : : : : : : : HardwareSemantic Data Identifier #m: : byte #q* A_ASCIISTR ING, zero C 0x00, 0x20 – 0x7E *depends on the SoftwareItemSemanticDataIdentifiers length. Details & reviewer feedbackSection 5.2.1.21 DID 0xF19A HardwareSemanticDataIdentifiers Page page 18 Feature / Interface Secure communication and freshness protection / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier 0xF19D Name: ECUInstallationDateDataIdentifier Byte Data Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 19 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber 0xF1A5 Name: vehicleManufacturerECUHardwareWithoutBootNumber Byte No: Description Format Cvt Byte Value Default Data #1 : #13 vehicleManufactur er ECU Hardware Number Byte #2 : 13-Byte- M : M : Project 5.2.1.24 DID 0xF1A6 engineNumber Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 19 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 29 – Description of DID 0xF1A6 engineNumber 0xF1A6 Name: engineNumber Byte Data #1 : #14 Engine number 14-Bytes- A_ASCIISTRING MM : 0x20 C = Applicable only for TRATON standalone engine solutions Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 19 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier 0xF1AD Name: activeECUSoftwareDataIdentifier Byte Data #1 : #2 Active ECU Software 2-Bytes- A_BYTEFIEL D M : M Boot loader: 0x0000 Application Software: 0x0002 No information: 0xFFFF Not applicabl e 5.2.1.29 DID 0xF1AF NodeUID Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 21 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 34 – Description of DID 0xF1AF NodeUID 0xF1AF Name: NodeUID Byte Data #1 : #8 NodeUID 8-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 21 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber 0xF1B9 Name: RBACCIdentifierNumber Byte Data #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 22 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 36 – Description of DID 0xF1BA RBACCStructureVersion 0xF1BA Name: RBACCStructureVersion Byte Data #1 : #2 RBACC Structure Version 2-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 Details & reviewer feedbackSection 5.2.1 Used data identifier in order to identify an ECU Page page 22 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 38 – Description of DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber 0xF1E1 Name: vehicleManufacturerECUBootSoftwareNumber Byte No: Description Format Cvt Byte Value Default Data #1 : #13 vehicleManufacturer ECUBootSoftwareNu mber Byte #2 : 13-Byte- G, M : M : Project Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 23 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
. Default transition for the start of the software in the server after power-up/wake-up. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 27 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
to Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 27 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 27 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 1
|
. The initialization routine is started. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If a valid application software is available in the server (applValid P1 == true) and there is no programming request (progRequest P2 == false), the server changes to the DefaultSession in the application software. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If there is no programming request (progRequest P2 == false) and no valid application software is available (applValid P1 == false), the server changes to the DefaultSession in the boot loader. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client posts a physical service request to change session from DefaultSession to ProgrammingSession in the application software, the server sends a negative response with NRC 0x7E (sub-functionNotSupportedInActiveSession). Applies to non-reprogrammable servers: If the client requests a change to the ProgrammingSession in the DefaultSession in the application software, the server Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests a change to the ExtendedSession in the DefaultSession in the application software, the session is changed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client does not send any requests during a time period defined by S3Server in the ExtendedSession in the application software, the server falls back into the DefaultSession in the application software. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests a change to the DefaultSession in the ExtendedSession in the application software, the session is changed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests a change to the ExtendedSession in ExtendedSession in the application software, the server accepts the request. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
2. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 28 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the boot loader ExtendedSession or ProgrammingSession, the reset is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests a change to the DefaultSession in the boot loader ExtendedSession or ProgrammingSession, the reset is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client does not send any requests during a time period defined by S3Server in a Non-DefaultSession in the boot loader, the server performs a reset. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests a change to the DefaultSession in the DefaultSession in the boot loader, the server accepts the request. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the DefaultSession in the boot loader, the reset is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests the ExtendedSession in the DefaultSession in the boot loader, the session is changed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client posts a physical service request to change session from DefaultSession to ProgrammingSession in the boot loader, the server sends a negative response with NRC 0x7E (sub-functionNotSupportedInActiveSession). Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests the ExtendedSession in the ExtendedSession in the boot loader, the server accepts the request. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests the ProgrammingSession in the ExtendedSession in the boot loader, the session is changed regardless of whether the programming preconditions are fulfilled or not. The request is only sent physically. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests a change to the ProgrammingSession in ProgrammingSession in the boot loader, the server accepts the request. The request is only sent physically. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client posts a physical service request to change session from ProgrammingSession to ExtendedSession in the boot loader, the server sends a negative response with NRC 0x7E (sub-functionNotSupportedInActiveSession). Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests the DefaultSession in the DefaultSession in the application, the server accepts the request. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
12. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 29 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in a DefaultSession in the application software, a restart is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
. If the client requests an ECUReset (0x11) with the sub-function HardReset (0x01) in the ExtendedSession in the application software a restart is performed. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
24. Details & reviewer feedbackSection 5.3 Diagnostic sessions requirements Page page 30 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Positive response Details & reviewer feedbackSection 5.5.1.2 Positive response Page page 33 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.2 ECUReset (0x11) service Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 33 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.2.1.1 Request parameter resetType Details & reviewer feedbackSection 5.5.2 ECUReset (0x11) service Page page 34 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 45 – Service 0x11 positive response parameter description 1 ECUReset Response SID M 2 resetType M Details & reviewer feedbackSection 5.5.2.2 Positive response Page page 34 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.2.3.1 Supported negative response codes Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 35 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 46 – Service 0x11 negative response codes NRC Description and scenario 0x12 sub-functionNotSupported Refer to ISO 14229-1 for scenario. Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 35 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Negative response Details & reviewer feedbackSection 5.5.3.3 Negative response Page page 36 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 47 – Service 0x28 request parameter description 1 CommunicationControl Request SID M 2 controlType M 3 communicationType M 5.5.3.1.1 Request parameter controlType Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 36 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 48 – Service 0x28 request parameter controlType description Hex (bit 6-0) Description Cvt 0x00 enableRxAndTx M 0x01 enableRxAndDisableTx M 0x40 – 0x5F vehicleManufacturerSpecific U 5.5.3.1.2 Request parameter communicationType Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 36 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 49 – Service 0x28 request parameter communicationType description Bits Value (Hex) Description Cvt 0 -1 1 normalCommunicationMessages M 4 – 7 0 Disable / Enable specified communicationType M 5.5.3.2 Positive response Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 36 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
5.5.3.3 Negative response Details & reviewer feedbackSection 5.5.3 CommunicationControl (0x28) service Page page 36 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
5.5.4.4 Negative response Details & reviewer feedbackSection 5.5.5 ControlDTCSetting (0x85) service Page page 37 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.5 ControlDTCSetting (0x85) service Details & reviewer feedbackSection 5.5.5 ControlDTCSetting (0x85) service Page page 37 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Refer to ISO 14229-1 for request format. Details & reviewer feedbackSection 5.5.5.1 Request Page page 37 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Refer to ISO 14229-1 for request parameter DTCSettingType. Details & reviewer feedbackSection 5.5.5.1.1 Request parameter DTCSettingType Page page 37 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Request parameter DTCSettingControlOptionRecord Details & reviewer feedbackSection 5.5.5.1.2 Request parameter DTCSettingControlOptionRecord Page page 38 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Refer to ISO 14229-1 for positive response format and parameter. Details & reviewer feedbackSection 5.5.5.2 Positive response Page page 38 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Refer to ISO 14229-1 for negative response format and codes. Details & reviewer feedbackSection 5.5.5.3 Negative response Page page 38 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Request Details & reviewer feedbackSection 5.5.7.1 Request Page page 39 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 50 – Service 0x87 request parameter linkControlType description Byte Value Description Cvt 0x01 verifyModeTransitionWithFixedParameter M 0x03 transitionMode M 0x40-0x5F vehicleManufacturerSpecific U 5.5.6.2.1 Request parameter linkControlModeIdentifier Details & reviewer feedbackSection 5.5.7 ReadDataByIdentifier (0x22) service Page page 39 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.6.4 Negative Response Details & reviewer feedbackSection 5.5.7 ReadDataByIdentifier (0x22) service Page page 39 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.7 ReadDataByIdentifier (0x22) service 5.5.7.1 Request Details & reviewer feedbackSection 5.5.7 ReadDataByIdentifier (0x22) service Page page 39 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Positive response Details & reviewer feedbackSection 5.5.8.2 Positive response Page page 40 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.7.3 Negative response Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.8 WriteDataByIdentifier (0x2E) service Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
The range of a requested dataRecord value has to be checked by the server if the DID is safety relevant. Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Additional client requests which start copying RAM buffer data into non-volatile memory are not allowed. Details & reviewer feedbackSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.9.1.1 Request parameter groupOfDTC Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 41 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.9.3 Negative response Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 41 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.10 ReadDTCInformation (0x19) service 5.5.10.1 Request Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 41 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.10.1.1 Request parameter reportType Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 41 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 52 – Service 0x19 request parameter reportType description 0x01 reportNumberOfDTCByStatusMask M 0x02 reportDTCByStatusMask M 0x03 reportDTCSnapshotIdentification M 0x04 reportDTCSnapshotRecordByDTCNumber M 0x06 reportDTCExtendedDataRecordByDTCNumber M 0x0F reportMirrorMemoryDTCByStatusMask U Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 41 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Legislated OBD relevant ECUs have to support legislated OBD standards. Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 42 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 53 – Service 0x19 request parameter DTCMaskRecord description Byte Description Cvt High Definition according to either ISO 15031-6, ISO 14229 vehicle- manufacturer-defined, SAE J1939-73 M Middle M Low M Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 42 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 54 – Service 0x19 request parameter DTCExtDataRecordNumber description 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 5.5.10.1.7 Request parameter FunctionalGroupIdentifier Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 43 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.10.2.1 Response parameter DTCStatusAvailabilityMask Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 43 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 56 – Service 0x19 response parameter DTCExtDataRecordNumber description 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 5.5.10.2.8 Response parameter DTCExtDataRecord Details & reviewer feedbackSection 5.5.10 ReadDTCInformation (0x19) service Page page 51 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.10.3.1 Supported negative response codes Details & reviewer feedbackSection 5.5.11 InputOutputControlByIdentifier (0x2F) service Page page 54 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.11.1.1 Request parameter dataIdentifier Details & reviewer feedbackSection 5.5.11 InputOutputControlByIdentifier (0x2F) service Page page 54 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 58 – Service 0x2F request parameter controlOptionRecord description 1 inputOutputControlParameter M 2 .. Details & reviewer feedbackSection 5.5.11.1.2 Request parameter controlOptionRecord Page page 54 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 59 – Service 0x2F request parameter inputOutputControlParameter description 0x00 returnControlToECU Refer to ISO 14229-1 for parameter description. Details & reviewer feedbackSection 2 + (m-1) controlState byte 1 : controlState byte m C : C 5.5.11.1.3 Request parameter inputOutputControlParameter Page page 54 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.11.3 Negative response Details & reviewer feedbackSection 5.5.12 RoutineControl (0x31) service Page page 55 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
5.5.12 RoutineControl (0x31) service 5.5.12.1 Request Details & reviewer feedbackSection 5.5.12 RoutineControl (0x31) service Page page 55 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
5.5.12.1.1 Request parameter RoutineControlType Details & reviewer feedbackSection 5.5.12 RoutineControl (0x31) service Page page 55 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 60 – Service 0x31 request parameter RoutineControlType description 0x01 startRoutine M 0x02 stopRoutine C 0x03 requestRoutineResults C C = Mandatory for routines implemented according to Method “A”. Details & reviewer feedbackSection 5.5.12 RoutineControl (0x31) service Page page 55 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.12.3 Negative response Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 57 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.13 Request Download Service (0x34) Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 57 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 63 – Service 0x34 request parameter dataFormatIdentifier description compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF Details & reviewer feedbackSection M 5.5.13.2 Request parameter dataFormatIdentifier Page page 58 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description 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 5.5.13.4 Positive response Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 59 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 65 – Positive response parameter description #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier M 0x20 #3.. Details & reviewer feedbackSection 5.5.13 Request Download Service (0x34) Page page 59 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 66 – Service 0x34 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved. Details & reviewer feedbackSection #4 maxNumberOfBlockLength[] = [ byte #1 (MSB) byte #2 ] M M 0xFF 0xFF 5.5.13.5 Response parameter lengthFormatIdentifier Page page 59 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 67 – Service 0x35 request parameter description 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier M 4 .. (m-1)+4 Details & reviewer feedbackSection 5.5.14 RequestUpload (0x35) Page page 60 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 4 | Linked diagrams: 0
|
Table 68 – Service 0x35 request parameter dataFormatIdentifier description Bytes Description Cvt Values compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1 Details & reviewer feedbackSection M 5.5.14.1.1 Request parameter dataFormatIdentifier Page page 60 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Request Details & reviewer feedbackSection 5.5.15.1 Request Page page 61 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 69 – Service 0x35 request parameter addressAndLengthFormatIdentifier description 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 5.5.14.1.3 Request parameter memoryAddress Details & reviewer feedbackSection 5.5.15 TransferData (0x36) service Page page 61 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
5.5.14.2.1 Response parameter lengthFormatIdentifier Details & reviewer feedbackSection 5.5.15 TransferData (0x36) service Page page 61 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
Table 70 – Service 0x35 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved. Details & reviewer feedbackSection 5.5.15 TransferData (0x36) service Page page 61 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.15.3 Negative response Details & reviewer feedbackSection 5.5.16 RequestTransferExit (0x37) service Page page 62 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.15.3.1 Supported negative response codes Details & reviewer feedbackSection 5.5.16 RequestTransferExit (0x37) service Page page 62 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.16 RequestTransferExit (0x37) service 5.5.16.1 Request Details & reviewer feedbackSection 5.5.16 RequestTransferExit (0x37) service Page page 62 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 71 – Service 0x37 request parameter description 1 RequestTransferExit Request SID M 5.5.16.1.1 Request parameter transferRequestParameterRecord Details & reviewer feedbackSection 5.5.16 RequestTransferExit (0x37) service Page page 62 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 72 – Service 0x37 positive response parameter description 1 RequestTransferExit Response SID M Details & reviewer feedbackSection 5.5.16.2 Positive response Page page 62 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.16.3.1 Supported negative response codes Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.17 SecuredDataTransmission (0x84) service Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
5.5.17.1.1 Request message data-parameter definition Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 63 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Refer to CVS31 . Details & reviewer feedbackSection 5.5.18.1 Request Page page 64 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Refer to CVS31 . Details & reviewer feedbackSection 5.5.18.2 Request parameter subFunction Page page 64 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Refer to CVS31 . Details & reviewer feedbackSection 5.5.18.3 Positive response Page page 64 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.18.4.1 Supported negative response codes Details & reviewer feedbackSection 5.5.18 Authentication (0x29) service Page page 64 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.19.2 Request Parameter modeOfOperation Details & reviewer feedbackSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 75 – Service 0x38 request parameter dataFormatIdentifier description compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1 5.5.19.5 Positive response Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 66 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
5.5.19.6 Negative response Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 66 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
5.5.19.7 Supported negative response codes Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 66 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format #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 Details & reviewer feedbackSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Feature / Interface Secure software update and flash readiness / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 78 – RoutineIdentifier 0xFF00 description #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x00 #5 addressAndLengthFormatIdentifier (XXXXYYYYb) XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter. Details & reviewer feedbackSection 5.6.2.1 Request Page page 70 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 80 – RoutineControl (EraseMemory) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) eraseMemory [byte#1] M 0xFF #4 routineIdentifier (LSB) eraseMemory [byte#2] M 0x00 #5 routineStatus routineResult M 0x00-0xFF Details & reviewer feedbackSection 255 – System specific 5.6.2.3 Positive response Page page 71 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The RoutineIdentifier may verify the authenticity of the received file package. See CVS123 and Details & reviewer feedbackSection 5.6.3 Routine 0x2401 – Software Installation Page page 74 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 97 – Fault memory DTC status bits description 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 Details & reviewer feedbackSection 5.7.2 Occurrence counter OCC Page page 80 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The timestamp is presented in SAE J1939-71 format without local hour/minute offsets. Details & reviewer feedbackSection 5.7.3 Timestamp of occurrence Page page 81 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
In SAE J1939-71 section “PGN 65254 Time/Date”, the following format is specified: Table 98 – J1939-71 timestamp format Byte No Length Name Resolutio n Offset Note 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 4 1 byte Month 1 month/bit 0 Value 1 identifies January, value 2 identifies February and so on 5 1 byte Day 0.25 days/bit 0 Values 1,2,3 and 4 identifes first day of month, value 5,6,7,8 identifies second day of month and so on 6 1 byte Year 1 year/bit 1985 Value of 0 identifies year 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 Details & reviewer feedbackSection 5.7.3 Timestamp of occurrence Page page 81 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit). Details & reviewer feedbackSection 5.10 Session layer performance requirements Page page 83 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
F198 Request and response format Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
F199 Request and response format Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
F19A Request and response format Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
NRC for RBACC check failures Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
, Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
, Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
, Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
, Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
, Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
, Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Requirements, Request and response formats for the ControlDTCSetting(0x85) added. Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Added semantic Identifier DIDs, changed the NodeUID DID to INTERNAL Details & reviewer feedbackSection 6 Normative references Page page 90 Feature / Interface Secure communication and freshness protection / None Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Change in the length of NodeUID(0xF1AF) Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
0xF1B9 RBACCIdentifierNumber is changed to Mandatory Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
0xF1BA RBACCStructureVersion,bit-length changed Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Changes for service (0x84) and (0x31) Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Modifcations on the bit values and new bit added Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
(0x86) service removed Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
, Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Removed the reserved DID ranges and 0xF1C1 Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
0xF19E ODXFileDataIdentifier is removed 2024-10 First issue Details & reviewer feedbackSection 6 Normative references Page page 90 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
02, Module 2 (Application SW module) M 0x02 – 0xFF Physical memory range erase: Refer to ISO 14229-1 Table H1 M C = Mandatory if required to meet the performance requirements & & Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 71 Supplier proposal Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
in CVS123. Details & reviewer feedbackSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 71 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Reads like a requirement but no customer requirement ID was identified in the source. Confirm with the customer before baselining — not counted as a confirmed requirement.
Minimum length shall be 8 bytes and the assigned value shall be unique for every unit provided by one supplier per project. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 14 Feature / Interface None / OEM/Customer Review Interface |
The application shall respond with NRC 0x22 (conditionsNotCorrect) if communication has not been switched off. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 |
In this process, it shall end all routines and functions that influence programming and ensure that the server checked for safe state conditions at minimal. Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. DetailsSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 Feature / Interface Secure software update and flash readiness / None |
The implementation of hardReset shall first ensure that data corruption will not occur. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.2 ECUReset (0x11) service Page page 34 |
If this action is necessary then it shall be integrated implicitly into ECU Reset (0x11) Service subfunction 0x02. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.8 WriteDataByIdentifier (0x2E) service Page page 40 |
5.5.10.2.6 Response parameter reportDTCSnapshotRecordByDTCNumber The snapshot data sub-function (0x04) shall have positive response message data and format as specified in Table 67. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 44 |
dependent depend ent depende nt U #65+N+M- #66+N+M dataIdentifier 0x0000 – #67+N+M +P Data required by law or regulations Signal dependent depend ent depende nt C1 #68+N+M +P DTCSnapshotRecordNumber#2 (Latest Snapshot captured) 0x02 M #69+N+M +P DTCSnapshotRecordNumberOfIdentifiers#2 0x00 : 0xFF M #70+N+M +P : #70+2*(N +M+P) See specification for DTCSnapshotRecord[]#1 This latest snapshot shall contain the same type of data and format as DTCSnapshotRecord[]#1. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 50 Feature / Interface None / External Interfaces |
Table 57 – Extended data sub-function (0x06) positive response message content and format Byte Description Range Resolu tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = reportDTCExtDataRecordByDTCNumber 0x06 M #3 : #6 DTCAndStatusRecord[] = [ DTCHighByte DTCMiddleByte DTCLowByte statusOfDTC ] M #7 DTCExtDataRecordNumber#1 This byte shall be set to value 0x11. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 51 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Byte Description Range Resolu tion This byte shall be set to value 2 and is used to identify the response structure variant #9 Occurrence counter OCC, as described in section 5.7.2 [unsigned integer] 0..127 0 M #10 DTC priority 1 – Highest priority 2 - Second highest priority 3 – Lowest priority 255 – Unknown 1..3, 255 0xFF M #11..#16 Time/Date of the first DTC activation See Table 98 but without byte #7 and #8 M #17..#22 Time/Date of the latest DTC activation M #23..#26 ECU Operational hours at the first DTC activation [4-byte int, big endian] as described in section 5.7.5.2. Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 52 |
Byte Description Range Resolu tion 0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m #35..#38 Total vehicle distance at the latest DTC activation [4-byte int, big endian] in section 5.7.4.1 Not used for TRATON External engine and marine ECUsFor these ECUs these bytes shall contain default value 0xFF (all bytes). Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 53 |
The routine IDs as listed in Table 61 are reserved by TRATON and shall not be used by the system supplier. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.12 RoutineControl (0x31) service Page page 55 Feature / Interface None / OEM/Customer Review Interface Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Preconditions to be discussed with the vehicle manufacturer shall include but not be limited to Diag safe state conditions. Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. DetailsSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 Feature / Interface None / OEM/Customer Review Interface |
Table 77 – Programming preconditions Hex Description Origin 0x01 Engine speed is not zero Defined by the “manufacturers software initiative” (HIS) 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 0x08 No programming voltage 0x09 Ignition (terminal 15) is not turned on 0x0A Supply voltage too low 0x0B Temperature too high 0x0C Temperature too low .. Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. DetailsSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 68 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The User shall apply the latest version of this CVS124. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection page-1 Page 1 Page page 1 |
Any review of CVS124 shall only be done in agreement with the involved departments stated in the table on the first page under section “Technical responsibility”. Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. DetailsSection page-2 Page 2 Page page 2 |
• Affiliate means any legal entity that directly or indirectly controls, is controlled by, or is commonly controlled with TRATON SE, it is being understood that “control” shall mean ownership of at least 50% of the voting rights or interest in the issued share capital, including for the avoidance of doubt any branch. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection page-2 Page 2 Page page 2 |
the disconnect from the battery shall not be simulated. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.2 ECUReset (0x11) service Page page 34 |
If a request is received before this time has passed the server shall respond with NRC 0x78 (requestCorrectlyReceived-ResponsePending) (and process the request and send a final response when 2 seconds have passed) or NRC 0x22 (conditionsNotCorrect). Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.3 CommunicationControl (0x28) service Page page 35 |
If a mechanic is working on the vehicle, the driveline shall report Not Ready and place the vehicle in the state PropulsionNotReady. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 46 |
For these ECUs these bytes shall contain default value 0xFF (all bytes). Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 52 |
0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m 0xFFF FFFFF 5 m/bit 0xFF (all bytes) C #41+(2p+1) +1 DTCExtDataRecordNumber#4 This byte shall be set to value 0x14. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 53 |
If the file is not stored at the location the file shall be added. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 |
M 0x04 ReadFile This value shall be used to read the file (upload) at the location defined by the filePathAndName parameter. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 |
U 0x05 ReadDir This value shall be used to read the directory defined in the filePathAndName parameter. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 |
U 0x06 ResumeFile This value shall be used to resume downloading the file defined in the filePathAndName parameter at the returned filePosition indicator. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 |
The file specified in the filePathAndName shall already exist in the ECU’s file system. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.5.19 RequestFileTransfer (0x38) service Page page 65 |
If the ECU received the information related to any of the conditions during the same driving cycle then it shall use that information. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 67 |
the erasing of memory shall proceed in parallel with data transfer in case for ECUs implementing Automatic erase. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 70 |
Information shall be provided in percentage. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.6.3 Routine 0x2401 – Software Installation Page page 76 |
Information shall be provided in seconds. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5.6.3 Routine 0x2401 – Software Installation Page page 76 |
In addition, a check shall be made to determine whether or not the software is compatible with the hardware version (e.g., variants of sensors/actuators) and other data structures (e.g., EEPROM data). Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). DetailsSection 5.6.3 Routine 0x2401 – Software Installation Page page 77 |
Descriptive or contextual statements with a customer ID but no binding (shall/must) wording.
for Linux based systems still running in boot, the server should indicate with DID 0xF1AD that it is running in boot. DetailsSection 5.10 Session layer performance requirements Page page 83 |
The format should follow the pattern: Appl: <Diag.family> <Diag.generation> Boot: <Diag.family> <Diag.generation>_BOOT DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 16 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
In Table 39, bootloader sessions should only be applicable to Software updateable ECUs. DetailsSection 5.3 Diagnostic sessions requirements Page page 25 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The conditions that shall be checked are • Vehicle speed ~ 0 • Engine speed ~ 0 (for vehicles with IC engines) • High Voltage system disengaged ( for vehicles with high Voltage battery system) • Gear Box in neutral • Parking brake engaged Diagnostics safe state is not intended for ensuring the vehicle safety rather its conditions that are checked to prevent executing Diagnostics services during vehicle operation DetailsSection 5.3 Diagnostic sessions requirements Page page 25 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The server shall send an ECUReset positive response message after the server tasks above are finished but before the server performs the actual resetType. DetailsSection 5.5.2 ECUReset (0x11) service Page page 34 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Communication control service should not only be used to improve the bandwidth situation during flashing /parametrisation but also for inhibiting systems in vehicle (like engine start) to ensure safety. DetailsSection 5.5.3 CommunicationControl (0x28) service Page page 36 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Whereas the result of the dependency check is returned as part of a positive response, a negative response code (NRC) shall be returned if the normal conditions according to (ISO 14229-1) (authentication, service request length, parameter range check etc) for performing the service are not correct. DetailsSection 5.6.3.3 Negative response Page page 76 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
This RoutineIdentifier value allows the client to start a consistency check of the server and should be able to execute independent from programming sequence. DetailsSection 5.6.4 Routine 0xFF01 – CheckProgrammingDependencies (check the flash programming) Page page 76 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Table 94 – CheckProgrammingDependencies routineStatusRecord results 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 5.6.4.3 Negative response Whereas the result of the dependency check is returned as part of a positive response, a negative response code (NRC) shall be returned if the normal conditions according to (ISO 14229-1)(authentication, service request length, parameter range check etc) for performing the service are not correct. DetailsSection 5.6.3 Routine 0x2401 – Software Installation Page page 78 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
SUPPLIER in the Changing column means that the DID can be changed only at the supplier premises for non-programmable ECUs. Data identifier details. DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 9 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The format in the DID description in the following tables is given in ODX base data types. DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 9 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
This identifier is used for follow up and quality check at production and service and for legal reasons if applicable. DetailsSection 0x30 Page page 14 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The current date as received on CAN or other ECU-external source at first reception of a valid signal after a software update. DetailsSection 5.2.1.27 DID 0xF1AB Date at software update stamp Page page 20 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This identifier is used to link a ECU HW to its specialized security attributes. DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 22 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The value to be stored is fetched from TRATON backend system in production. DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 22 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Information on RBACC can be found in CVS151. DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 22 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Information on RBACC can be found in CVS151. DetailsSection 5.2.1 Used data identifier in order to identify an ECU Page page 22 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Description of the individual transitions as per Figure 2 -State Diagram is explained from DetailsSection 5.3 Diagnostic sessions requirements Page page 27 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
Table 41 – Data identifier (DID) ranges Byte value Description 0x0611-0x0620 Reserved for collective data identifiers 0xB000 – 0xB1FF Reserved for TRATON 0xCF00 – 0xCFFF TRATON data field identifiers 0xF010 disableDiagnosticClient 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Refer to VehSec_IVD_ECU for detailed requirements on Integrity Validation Data (IVD) for ECUs which need to be compliant to UNECE R156 regulation. DetailsSection 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Page page 31 Feature / Interface Secure software update and flash readiness; Security evidence and traceability / None Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
This requirement mitigates DOS (Denial Of Service) attacks DetailsSection 5.5.3 CommunicationControl (0x28) service Page page 35 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
After receiving CommunicationControl service request, ECUs could still keep sending some networks messages/signals to keep a healthy vehicle system. DetailsSection 5.5.3 CommunicationControl (0x28) service Page page 35 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
A functionally addressed TesterPresent may arrive at any time during another request. DetailsSection 5.5.5 ControlDTCSetting (0x85) service Page page 37 |
Link Control (0x87) service is only applicable to CAN & CAN FD. DetailsSection 5.5.6 Link Control (0x87) service Page page 38 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Range tion #54 ECU start-up and alive reasons Bits 0-3 (start-up reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6-0xE: Reserved 0xF: Not available Bits 4-7 (alive reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6: Stay alive 0x7-0xE: Reserved 0xF: Not available Note 1: While the reason for keeping the ECU alive may change during execution startup reason and alive reason are always identical at ECU startup. DetailsSection 5.5.10 ReadDTCInformation (0x19) service Page page 49 |
In order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into another memory area before the boot loader memory is erased, see Annex A for an implementation hint. DetailsSection 5.5.13 Request Download Service (0x34) Page page 57 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
This RoutineIdentifier enables the client to query the state of the programming preconditions in the server and applicable only for programmable ECUs. DetailsSection 5.6 Routine Identifier Requirements 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page page 66 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
In order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into another non-volatile memory area before the boot loader memory is erased, see Annex A for an implementation hint. DetailsSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 69 |
SUV2_INFO 114 in CVS123 prevents the scenario of erasing the copied bootloader while boot loader update and leaving the ECU without any bootloader. DetailsSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 69 |
5.6.2.5 Message flow example(s) RoutineControl (EraseMemory) Example #1: Request: client → server DetailsSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 72 Related Tables / DiagramsLinked tables: 3 | Linked diagrams: 0
|
This is an example where the client requests to erase a module in the server memory by a given memoryStartAddress and memorySize. DetailsSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 72 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
This example reports a failure when the erase operation is started, e.g. memory failure. DetailsSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 73 Related Tables / DiagramsLinked tables: 4 | Linked diagrams: 0
|
This is an example where the client requests to erase a module with module index 3 in the server’s memory. DetailsSection 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page page 73 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 4 | Linked diagrams: 0
|
The authenticity verification performed by the RoutineIdentifier 0x2401 Software Installation does not exempt the authenticity verification for RoutineIdentifier 0xFF01 – CheckProgrammingDependencies. DetailsSection 5.6.3 Routine 0x2401 – Software Installation Page page 74 Feature / Interface Secure software update and flash readiness; Security evidence and traceability / None Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
Implementation hint can be seen on Annex B. DetailsSection 5.6.3 Routine 0x2401 – Software Installation Page page 76 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
This is an example where the client requests CheckProgrammingDependencies to finalize the validation after software download. DetailsSection 5.6.5 Routine 0xCAFE – EMP Page page 79 Feature / Interface Secure software update and flash readiness; Security evidence and traceability / None Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The checksum was contained in the data stream programmed to the memory. DetailsSection 5.6.5 Routine 0xCAFE – EMP Page page 79 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Table 95 – Example: Request: client → server #1 RoutineControl Request SID 0x31 #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier byte#1 (checkProgrammingDependencies MSB) 0xFF #4 routineIdentifier byte#2 (checkProgrammingDependencies LSB) 0x01 Example: Positive response: server → client In this example the routine status indicates that the programming dependencies returned correct result. DetailsSection 5.6.5 Routine 0xCAFE – EMP Page page 79 Feature / Interface Secure software update and flash readiness / None Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
The occurrence counter is used in DTCExtDataRecords, see section 5.5.10.2.8. DetailsSection 5.7.2 Occurrence counter OCC Page page 80 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The timestamp of occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8. DetailsSection 5.7.3 Timestamp of occurrence Page page 81 Related Tables / DiagramsLinked tables: 1 | Linked diagrams: 0
|
The total vehicle distance at occurrence is used in DTCExtDataRecords, see section 5.5.10.2.8. DetailsSection 5.7.4 Vehicle distance at occurrence Page page 82 |
The operational hours at occurrence is used at DTCExtDataRecords, see section 5.5.10.2.8. DetailsSection 5.10 Session layer performance requirements Page page 83 |
F197 structure added DetailsSection 6 Normative references Page page 90 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Change in the retrieval method for NodeUID(0xF1AF) DetailsSection 6 Normative references Page page 90 Related Tables / DiagramsLinked tables: 2 | Linked diagrams: 0
|
Its upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer. DetailsSection 5.5.1 DiagnosticSessionControl (0x10) service Page page 32 |
Definitions, abbreviations, document history, scope and other boilerplate. Not customer requirements.
Conventions Shall be agreed between the supplier and the vehicle manufacturer. Table 3 – Conventions Implementation Description M Mandatory Mandatory data marked as ‘M’ always shall be returned. If valid data is not needed for the use-case and system at hand, default values should be used. E Mandatory for ECUs which shall be compliant with OBD legislation Worldwide like ISO27145,J1979 etc C Conditional U User optional. Shall be agreed between the supplier and the vehicle manufacturer. - (dash) Not supported Table 4 – Definitions of terms Changing Description DIAG Diagnostics - The Data Identifier content can be changed by means of the UDS service 0x2E FLASH BOOT Boot loader module stored in flash memory FLASH APPL Application module stored in flash memory FLASH DATA Dataset download - The Data Identifier content is changed by a dataset download process as per document Harmonized programming (see /11/) SUPPLIER Supplier process - The Data Identifier content is changed at the supplier's facilities by the manufacturing process. INTERNAL ECU software - The Data Identifier content is determined by the server at runtime. E Mandatory for ECUs which shall be compliant with OBD legislation Worldwide like ISO27145,J1979 etc C Conditional U User optional. If valid data is not needed for the use-case and system at hand, default values should be used. DetailsSection 4.3 Conventions Page page 7 Feature / Interface None / OEM/Customer Review Interface |
Abbreviations Shall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification. Should This word, or the adjective “Recommended”, means that there may exist 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. 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. 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 2 – Abbreviated terms Abbreviation Description DID Data Identifier EnvCond Environment Condition FMI Failure Mode Indication Def Default diagnostic session DSIV Diagnostic Security Implementation Variant Project specific. Dependent of the security variant implemented in the diagnostic server. DTC Diagnostic Trouble Code ECU Electronic Control Unit Ext Extended diagnostic session UDS Unified Diagnostic Services CAN Controller Area Network Table 1 – Definition of Terms 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. Should This word, or the adjective “Recommended”, means that there may exist 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. Should not This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. May 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. 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). Should not This phrase, or the phrase “Not recommended”, means that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. May This word, or the adjective “Optional”, means that an item is truly optional. DetailsSection 4.2 Abbreviations Page page 6 |
Page 2 Foreword This CVS124 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable. DetailsSection page-2 Page 2 Page page 2 |
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| SSR | Statement / Trace | Feature | Security Capability | Interface | Responsibility | Status | Verification |
|---|---|---|---|---|---|---|---|
| SSR-BOOT-001 | Secure software update and flash readiness — Bootloader and Application State HandlingThe ECU shall verify boot and application authenticity/integrity for Secure software update and flash readiness and enforce the defined behaviour on verification failure (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0014. | Secure software update and flash readiness | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-BOOT-002 | Secure software update and flash readiness — Bootloader and Application State HandlingThe ECU shall verify boot and application authenticity/integrity for Secure software update and flash readiness and enforce the defined behaviour on verification failure (Hardware domain; allocated to Hardware Platform).From this PDF: RFQX-CVS124-0343. | Secure software update and flash readiness | None | None | Supplier-Owned | Candidate | Review + Test + table/diagram context review |
| SSR-BOOT-005 | Bootloader and Application State Handling — Bootloader and Application State HandlingThe ECU shall verify boot and application authenticity/integrity for Bootloader and Application State Handling and enforce the defined behaviour on verification failure (Software domain; allocated to Application Software).From this PDF: RFQX-CVS124-0193; RFQX-CVS124-0354. | Bootloader and Application State Handling | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-COM-002 | Secure Communication and Boundary Control — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (System domain; allocated to System Core).From this PDF: RFQX-CVS124-0172. | Secure Communication and Boundary Control | None | None | Supplier-Owned | Candidate | Review + Test + table/diagram context review |
| SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (IT / backend domain; allocated to Backend and IT Systems).From this PDF: RFQX-CVS124-0433. | Secure Communication and Boundary Control | None | None | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software).From this PDF: RFQX-CVS124-0168; RFQX-CVS124-0198. | Secure Communication and Boundary Control | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-COM-007 | External Interfaces — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for External Interfaces, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Interface domain; allocated to External Interfaces; interface: External Interfaces).From this PDF: RFQX-CVS124-0149. | External Interfaces | None | External Interfaces | Supplier-Owned | Candidate | Review + Test + table/diagram context review |
| SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems).From this PDF: RFQX-CVS124-0387. | Data Authenticity and Integrity Verification | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (Software domain; allocated to Application Software).From this PDF: RFQX-CVS124-0385; RFQX-CVS124-0386. | Data Authenticity and Integrity Verification | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-DAI-005 | Security evidence and traceability — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0370. | Security evidence and traceability | None | OEM/Customer Review Interface | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-DAI-006 | Security evidence and traceability — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0362; RFQX-CVS124-0365. | Security evidence and traceability | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-DAI-007 | Security evidence and traceability — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (System domain; allocated to System Core; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0369; RFQX-CVS124-0371. | Security evidence and traceability | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Review + Test + table/diagram context review |
| SSR-DIAG-003 | Diagnostic Services — Diagnostic ServicesThe ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (System domain; allocated to System Core; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0087; RFQX-CVS124-0203; RFQX-CVS124-0242; RFQX-CVS124-0400; RFQX-CVS124-0407; RFQX-CVS124-0408; RFQX-CVS124-0409; RFQX-CVS124-0415; RFQX-CVS124-0416; RFQX-CVS124-0418. | Diagnostic Services | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-DIAG-004 | Diagnostic Services — Diagnostic ServicesThe ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Process / compliance domain; allocated to Compliance Process).From this PDF: RFQX-CVS124-0146; RFQX-CVS124-0223; RFQX-CVS124-0226; RFQX-CVS124-0229; RFQX-CVS124-0230; RFQX-CVS124-0232; RFQX-CVS124-0233; RFQX-CVS124-0234; RFQX-CVS124-0235; RFQX-CVS124-0236; RFQX-CVS124-0251; RFQX-CVS124-0252; RFQX-CVS124-0256. | Diagnostic Services | None | None | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-DIAG-005 | Diagnostic Services — Diagnostic ServicesThe ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Hardware domain; allocated to Hardware Platform).From this PDF: RFQX-CVS124-0201. | Diagnostic Services | None | None | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-DIAG-006 | Diagnostic Services — Diagnostic ServicesThe ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Software domain; allocated to Application Software).From this PDF: RFQX-CVS124-0207; RFQX-CVS124-0238. | Diagnostic Services | None | None | Shared | Blocked by Customer Clarification | Test + table/diagram context review |
| SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure StorageThe ECU hardware shall provide the platform and secure-storage capabilities required for Hardware / HSM / Secure Storage (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0058; RFQX-CVS124-0130; RFQX-CVS124-0152; RFQX-CVS124-0153; RFQX-CVS124-0209; RFQX-CVS124-0270. | Hardware / HSM / Secure Storage | None | OEM/Customer Review Interface | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-KEY-001 | Key and Certificate Handling — Key and Certificate HandlingThe ECU shall manage key and certificate material for Key and Certificate Handling across provisioning, storage, use, renewal and revocation per the agreed key lifecycle (Cybersecurity domain; allocated to Security Services; security capability: Certificate handling; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0160; RFQX-CVS124-0210. | Key and Certificate Handling | Certificate handling | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Cybersecurity domain; allocated to Security Services; security capability: Diagnostic security; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0075; RFQX-CVS124-0077; RFQX-CVS124-0078; RFQX-CVS124-0171; RFQX-CVS124-0186; RFQX-CVS124-0431; RFQX-CVS124-0432. | Secure Diagnostics / RBAC | Diagnostic security | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (IT / backend domain; allocated to Backend and IT Systems).From this PDF: RFQX-CVS124-0083. | Secure Diagnostics / RBAC | None | None | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Software domain; allocated to Application Software).From this PDF: RFQX-CVS124-0084; RFQX-CVS124-0135; RFQX-CVS124-0305; RFQX-CVS124-0306; RFQX-CVS124-0307. | Secure Diagnostics / RBAC | None | None | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security ContainerThe ECU shall protect security-relevant data transfer for Secure Data Transfer / Data Security Container using the agreed secured data transfer / data security container scheme (Software domain; allocated to Application Software).From this PDF: RFQX-CVS124-0273; RFQX-CVS124-0346. | Secure Data Transfer / Data Security Container | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-SYS-001 | System Function — System FunctionThe ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (System domain; allocated to System Core; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0019; RFQX-CVS124-0036; RFQX-CVS124-0089; RFQX-CVS124-0132; RFQX-CVS124-0195; RFQX-CVS124-0295; RFQX-CVS124-0297; RFQX-CVS124-0303; RFQX-CVS124-0304; RFQX-CVS124-0333; RFQX-CVS124-0334; RFQX-CVS124-0338; RFQX-CVS124-0350; RFQX-CVS124-0356; RFQX-CVS124-0367; RFQX-CVS124-0372; RFQX-CVS124-0373; RFQX-CVS124-0376; RFQX-CVS124-0383; RFQX-CVS124-0390; RFQX-CVS124-0402; RFQX-CVS124-0403; RFQX-CVS124-0404; RFQX-CVS124-0405; RFQX-CVS124-0410; RFQX-CVS124-0412; RFQX-CVS124-0417; RFQX-CVS124-0420; RFQX-CVS124-0421; RFQX-CVS124-0427; RFQX-CVS124-0435. | System Function | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-SYS-002 | System Function — System FunctionThe ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Process / compliance domain; allocated to Compliance Process; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0129; RFQX-CVS124-0133; RFQX-CVS124-0134; RFQX-CVS124-0147; RFQX-CVS124-0165; RFQX-CVS124-0182; RFQX-CVS124-0202; RFQX-CVS124-0213; RFQX-CVS124-0216; RFQX-CVS124-0222; RFQX-CVS124-0228; RFQX-CVS124-0250; RFQX-CVS124-0254; RFQX-CVS124-0259; RFQX-CVS124-0264; RFQX-CVS124-0267; RFQX-CVS124-0284; RFQX-CVS124-0285; RFQX-CVS124-0288; RFQX-CVS124-0289; RFQX-CVS124-0290; RFQX-CVS124-0302; RFQX-CVS124-0312; RFQX-CVS124-0325; RFQX-CVS124-0437. | System Function | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-SYS-003 | System Function — System FunctionThe ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0079; RFQX-CVS124-0082; RFQX-CVS124-0150; RFQX-CVS124-0162; RFQX-CVS124-0180; RFQX-CVS124-0244; RFQX-CVS124-0300; RFQX-CVS124-0313; RFQX-CVS124-0315; RFQX-CVS124-0321; RFQX-CVS124-0332; RFQX-CVS124-0352; RFQX-CVS124-0368; RFQX-CVS124-0374; RFQX-CVS124-0398. | System Function | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0018; RFQX-CVS124-0088; RFQX-CVS124-0154; RFQX-CVS124-0225; RFQX-CVS124-0381; RFQX-CVS124-0384; RFQX-CVS124-0406; RFQX-CVS124-0436. | Tooling / IT / Evidence Storage | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Software domain; allocated to Application Software).From this PDF: RFQX-CVS124-0157; RFQX-CVS124-0161; RFQX-CVS124-0192; RFQX-CVS124-0272; RFQX-CVS124-0274; RFQX-CVS124-0275; RFQX-CVS124-0341; RFQX-CVS124-0345; RFQX-CVS124-0364. | Tooling / IT / Evidence Storage | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-TOOL-004 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (System domain; allocated to System Core; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0434; RFQX-CVS124-0438; RFQX-CVS124-0439. | Tooling / IT / Evidence Storage | None | OEM/Customer Review Interface | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-UPD-001 | Secure software update and flash readiness — Software Update / FlashingThe ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0060; RFQX-CVS124-0137; RFQX-CVS124-0140; RFQX-CVS124-0185; RFQX-CVS124-0389; RFQX-CVS124-0391. | Secure software update and flash readiness | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-UPD-002 | Secure software update and flash readiness — Software Update / FlashingThe ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (System domain; allocated to System Core; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0145; RFQX-CVS124-0327; RFQX-CVS124-0329; RFQX-CVS124-0330; RFQX-CVS124-0336; RFQX-CVS124-0337; RFQX-CVS124-0339; RFQX-CVS124-0348; RFQX-CVS124-0366; RFQX-CVS124-0388; RFQX-CVS124-0392. | Secure software update and flash readiness | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-UPD-003 | Secure software update and flash readiness — Software Update / FlashingThe ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0142; RFQX-CVS124-0397. | Secure software update and flash readiness | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-UPD-004 | Secure software update and flash readiness — Software Update / FlashingThe ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface).From this PDF: RFQX-CVS124-0024; RFQX-CVS124-0028; RFQX-CVS124-0031; RFQX-CVS124-0043; RFQX-CVS124-0074. | Secure software update and flash readiness | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Review + Test + table/diagram context review |
| Impact Area | Evidence From This PDF |
|---|---|
| Impacted system features | Secure communication and freshness protection; Secure software update and flash readiness; Secure software update and flash readiness; Security evidence and traceability; Security evidence and traceability |
| Impacted interfaces | External Interfaces; OEM/Customer Review Interface |
| Impacted security capabilities | Diagnostic security; Key management |
| Impacted architecture elements | Application Software; Application Software; OEM/Customer Review Interface; Backend and IT Systems; Backend and IT Systems; OEM/Customer Review Interface; Compliance Process; Compliance Process; OEM/Customer Review Interface; External Interfaces; Hardware Platform; Hardware Platform; OEM/Customer Review Interface; Security Services; Security Services; OEM/Customer Review Interface; System Core (sample: 12 of 13) |
| Impacted work products | Cybersecurity concept; Cybersecurity verification report; DIA / cybersecurity case; Requirement traceability record; System/architecture design |
| Tools / IT / hardware / test | High/High/Low; High/Low/Low; High/Low/Medium; Low/High/High; Low/High/Low; Low/High/Medium; Low/Low/High; Low/Low/Low; Low/Low/Medium; Medium/High/High; Medium/High/Low; Medium/High/Medium (sample: 12 of 15) |
| Design assumptions introduced | Security-relevant requirement the ECU can own once responsibility/method is confirmed. Linked source table/diagram context was considered for interpretation. |
| Design decisions required | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| Impact | Status |
|---|---|
| Estimation impact | yes |
| Resource/tool/IT/HW/test impact | High/High/Low; High/Low/Low; High/Low/Medium; Low/High/High; Low/High/Low; Low/High/Medium; Low/Low/High; Low/Low/Low; Low/Low/Medium; Medium/High/High; Medium/High/Low; Medium/High/Medium (sample: 12 of 15) |
Generated from document-specific requirement, traceability, SSR, and open-point evidence.
flowchart LR
doc["CVS124.pdf"]
d0["Diagnostic security"]
doc --> d0
d1["Key management"]
doc --> d1
f0["Feature: Secure communication and freshness protection"]
doc --> f0
f1["Feature: Secure software update and flash readiness"]
doc --> f1
f2["Feature: Secure software update and flash readiness; Security evidence and traceability"]
doc --> f2
i0["Interface: External Interfaces"]
doc --> i0
i1["Interface: OEM/Customer Review Interface"]
doc --> i1
s0["SSR: SSR-BOOT-001"]
doc --> s0
s1["SSR: SSR-BOOT-002"]
doc --> s1
s2["SSR: SSR-BOOT-005"]
doc --> s2
o0["Open point: OP-001"]
doc --> o0
o1["Open point: OP-002"]
doc --> o1
o2["Open point: OP-004"]
doc --> o2
CVS124.pdf
Supplier Evaluation / Capability Assessment
Hardware / Platform
376 requirements, 44 information, 32 SSRs
100 tables, 2 diagrams
Markdown-derived requirements and registers; OCR disabled; no downstream PDF analysis
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Customer Requirement | SSR | Disposition | Confidence | Reason |
|---|---|---|---|---|
| RFQX-CVS124-0001 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0002 | None | Covered by Existing Supplier System Requirement | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0003 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0004 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0005 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-CVS124-0006 | None | Covered by Existing Supplier System Requirement | n/a | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0007 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0008 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0009 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-CVS124-0010 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0011 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0012 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0013 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0014 | SSR-BOOT-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0015 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-CVS124-0016 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0017 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0018 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0019 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0020 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0021 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0022 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0023 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0024 | SSR-UPD-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0025 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0026 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0027 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0028 | SSR-UPD-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0029 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0030 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0031 | SSR-UPD-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0032 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0033 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0034 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0035 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0036 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0037 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0038 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0039 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0040 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0041 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0042 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0043 | SSR-UPD-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0044 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0045 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0046 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0047 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0048 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0049 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0050 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0051 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0052 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0053 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0054 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0055 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0056 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0057 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0058 | SSR-HW-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0059 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0060 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0061 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0062 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0063 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0064 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0065 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0066 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0067 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0068 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0069 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0070 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0071 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0072 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0073 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0074 | SSR-UPD-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0075 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0076 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0077 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0078 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0079 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0080 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0081 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0082 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0083 | SSR-RBAC-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0084 | SSR-RBAC-004 | Derive Supplier System Requirement | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0085 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0086 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0087 | SSR-DIAG-003 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0088 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0089 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0090 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0091 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0092 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0093 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0094 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0095 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0096 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0097 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0098 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0099 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0100 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0101 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0102 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0103 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0104 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0105 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0106 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0107 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0108 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0109 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0110 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0111 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0112 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0113 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0114 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0115 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0116 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0117 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0118 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0119 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0120 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0121 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0122 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0123 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0124 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0125 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0126 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0127 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0128 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0129 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0130 | SSR-HW-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0131 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0132 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0133 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0134 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0135 | SSR-RBAC-004 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0136 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0137 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0138 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0139 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0140 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0141 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0142 | SSR-UPD-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0143 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0144 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0145 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0146 | SSR-DIAG-004 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0147 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0148 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0149 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0150 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0151 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0152 | SSR-HW-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0153 | SSR-HW-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0154 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0155 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0156 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0157 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0158 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0159 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0160 | SSR-KEY-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0161 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0162 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0163 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0164 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0165 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0166 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0167 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0168 | SSR-COM-006 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0169 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0170 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0171 | SSR-RBAC-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0172 | SSR-COM-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0173 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0174 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0175 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0176 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0177 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0178 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0179 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0180 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0181 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0182 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0183 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0184 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0185 | SSR-UPD-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0186 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0187 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0188 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0189 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0190 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0191 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0192 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0193 | SSR-BOOT-005 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0194 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0195 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0196 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0197 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0198 | SSR-COM-006 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0199 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0200 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0201 | SSR-DIAG-005 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0202 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0203 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0204 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0205 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0206 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0207 | SSR-DIAG-006 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0208 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0209 | SSR-HW-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0210 | SSR-KEY-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0211 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0212 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0213 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0214 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0215 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0216 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0217 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0218 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0219 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0220 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0221 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0222 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0223 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0224 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0225 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0226 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0227 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0228 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0229 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0230 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0231 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0232 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0233 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0234 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0235 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0236 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0237 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0238 | SSR-DIAG-006 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0239 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0240 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0241 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0242 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0243 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0244 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0245 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0246 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0247 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0248 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0249 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0250 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0251 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0252 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0253 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0254 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0255 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0256 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0257 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0258 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0259 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0260 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0261 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0262 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0263 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0264 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0265 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0266 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0267 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0268 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0269 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0270 | SSR-HW-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0271 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0272 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0273 | SSR-SDT-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0274 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0275 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0276 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0277 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0278 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0279 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0280 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0281 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0282 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0283 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0284 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0285 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0286 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0287 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0288 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0289 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0290 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0291 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0292 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0293 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0294 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0295 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0296 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0297 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0298 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0299 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0300 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0301 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0302 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0303 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0304 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0305 | SSR-RBAC-004 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0306 | SSR-RBAC-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0307 | SSR-RBAC-004 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0308 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0309 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0310 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0311 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0312 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0313 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0314 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0315 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0316 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0317 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0318 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0319 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0320 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0321 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0322 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0323 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0324 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0325 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0326 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0327 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0328 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0329 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0330 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0331 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0332 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0333 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0334 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0335 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0336 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0337 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0338 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0339 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0340 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0341 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0342 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0343 | SSR-BOOT-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0344 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0345 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0346 | SSR-SDT-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0347 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0348 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0349 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0350 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0351 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0352 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0353 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0354 | SSR-BOOT-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0355 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0356 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0357 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0358 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0359 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0360 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0361 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0362 | SSR-DAI-006 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0363 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0364 | SSR-TOOL-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0365 | SSR-DAI-006 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0366 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0367 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0368 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0369 | SSR-DAI-007 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-CVS124-0370 | SSR-DAI-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0371 | SSR-DAI-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0372 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0373 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0374 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0375 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0376 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0377 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0378 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0379 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0380 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0381 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0382 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-CVS124-0383 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0384 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0385 | SSR-DAI-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0386 | SSR-DAI-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0387 | SSR-DAI-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0388 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0389 | SSR-UPD-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0390 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0391 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0392 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0393 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0394 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0395 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0396 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0397 | SSR-UPD-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0398 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0399 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0400 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0401 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0402 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0403 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0404 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0405 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0406 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0407 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0408 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0409 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0410 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0411 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0412 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0413 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0414 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0415 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0416 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0417 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0418 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0419 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0420 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0421 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0422 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0423 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0424 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0425 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0426 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0427 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0428 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0429 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0430 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0431 | SSR-RBAC-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0432 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0433 | SSR-COM-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0434 | SSR-TOOL-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0435 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0436 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0437 | SSR-SYS-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-CVS124-0438 | SSR-TOOL-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0439 | SSR-TOOL-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-CVS124-0440 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0441 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0442 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0443 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0444 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0445 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0446 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0447 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0448 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0449 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0450 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0451 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0452 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0453 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0454 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0455 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0456 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0457 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0458 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0459 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0460 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0461 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0462 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0463 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0464 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-CVS124-0465 | None | Informational Only | n/a | Non-binding; not derived. |
CVS124.pdfconverted/markdown/source documentScope: this supplier evaluation / capability assessment specifies requirement, covering 5 Requirements; 5.2 ECU Identification Requirements; 5.2.1 Used data identifier in order to identify an ECU; 5.3 Diagnostic sessions requirements; 5.4 Data identifier requirements; 5.4.1 Integrity Validation Data DIDs (IVD-DIDs). System boundary and interfaces: the document constrains 1 interface(s) - OEM/Customer Review Interface; principal functions in scope are Secure software update and flash readiness; Secure communication and freshness protection; Secure software update and flash readiness; Security evidence and traceability; Security evidence and traceability.
Engineering obligations: 376 confirmed customer requirement(s) carry an explicit ID and normative wording and must be implemented and verified; 31 further requirement-like statement(s) have no customer ID and must be clarified before they can be baselined; 44 informational and 14 reference item(s) were separated out as non-binding. Design and security impact: affects Secure software update and flash readiness; Secure communication and freshness protection; Secure software update and flash readiness; Security evidence and traceability; Security evidence and traceability; security capabilities touched: Diagnostic security; Key management; 32 supplier system requirement(s) were derived from this document.
Open for the customer: 5 document-linked open point(s) - mainly Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).; Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.; Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. (sample: 3 of 5) - plus 31 unidentified requirement-like statement(s). Do not baseline these until the customer confirms. Confidence and limits: High confidence. Categorisation is derived from the converted Markdown (customer IDs, normative wording, and section context); no OCR or downstream PDF analysis is used.
| Field | Interpretation |
|---|---|
| Document Purpose | Scope: this supplier evaluation / capability assessment specifies requirement, covering 5 Requirements; 5.2 ECU Identification Requirements; 5.2.1 Used data identifier in order to identify an ECU; 5.3 Diagnostic sessions requirements; 5.4 Data identifier requirements; 5.4.1 Integrity Validation Data DIDs (IVD-DIDs). |
| Engineering Interpretation | System boundary and interfaces: the document constrains 1 interface(s) - OEM/Customer Review Interface; principal functions in scope are Secure software update and flash readiness; Secure communication and freshness protection; Secure software update and flash readiness; Security evidence and traceability; Security evidence and traceability. |
| Supplier Proposal Impact | Engineering obligations: 376 confirmed customer requirement(s) carry an explicit ID and normative wording and must be implemented and verified; 31 further requirement-like statement(s) have no customer ID and must be clarified before they can be baselined; 44 informational and 14 reference item(s) were separated out as non-binding. |
| System / Security Impact | Design and security impact: affects Secure software update and flash readiness; Secure communication and freshness protection; Secure software update and flash readiness; Security evidence and traceability; Security evidence and traceability; security capabilities touched: Diagnostic security; Key management; 32 supplier system requirement(s) were derived from this document. |
| Customer Clarification Impact | Open for the customer: 5 document-linked open point(s) - mainly Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).; Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy.; Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. (sample: 3 of 5) - plus 31 unidentified requirement-like statement(s). Do not baseline these until the customer confirms. |
| Confidence and Limits | Confidence and limits: High confidence. Categorisation is derived from the converted Markdown (customer IDs, normative wording, and section context); no OCR or downstream PDF analysis is used. |
| Theme | Summary | Requirement Count | Representative Requirements |
|---|---|---|---|
| Requirement | Groups related document requirements into a single engineering theme. | 376 | RFQX-CVS124-0018; RFQX-CVS124-0019; RFQX-CVS124-0020 |
| System architecture design | Groups related document requirements into a single engineering theme. | 372 | RFQX-CVS124-0001; RFQX-CVS124-0002; RFQX-CVS124-0007 |
| Diagnostics and service access | Defines UDS service behavior, authorization expectations, safe-state checks, and diagnostic evidence. | 211 | RFQX-CVS124-0006; RFQX-CVS124-0014; RFQX-CVS124-0020 |
| System | Groups related document requirements into a single engineering theme. | 205 | RFQX-CVS124-0001; RFQX-CVS124-0002; RFQX-CVS124-0007 |
| Software | Groups related document requirements into a single engineering theme. | 131 | RFQX-CVS124-0014; RFQX-CVS124-0020; RFQX-CVS124-0025 |
| Responsibility and customer approval model | Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk. | 130 | RFQX-CVS124-0003; RFQX-CVS124-0004; RFQX-CVS124-0005 |
| Cybersecurity concept and evidence | Drives cybersecurity concept, risk treatment, verification evidence, and traceability obligations. | 99 | RFQX-CVS124-0003; RFQX-CVS124-0004; RFQX-CVS124-0005 |
| Core ECA system behavior | Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope. | 87 | RFQX-CVS124-0005; RFQX-CVS124-0006; RFQX-CVS124-0011 |
| Section | Requirements | Information | Unknown | Excluded | Total Items | Critical | Open Points | SSR Links |
|---|---|---|---|---|---|---|---|---|
| 4 Terms, definitions and abbreviations | 0 | 0 | 0 | 0 | 13 | 8 | 2 | 1 |
| -- 4.2 Abbreviations | 0 | 0 | 0 | 0 | 9 | 5 | 1 | 0 |
| -- 4.3 Conventions | 0 | 0 | 0 | 0 | 4 | 3 | 2 | 1 |
| 5 Requirements | 352 | 42 | 0 | 0 | 422 | 66 | 5 | 31 |
| -- 5.2 ECU Identification Requirements | 45 | 9 | 0 | 0 | 55 | 2 | 1 | 5 |
| -- -- 5.2.1 Used data identifier in order to identify an ECU | 45 | 9 | 0 | 0 | 55 | 2 | 1 | 5 |
| -- 5.3 Diagnostic sessions requirements | 53 | 3 | 0 | 0 | 56 | 2 | 1 | 8 |
| -- 5.4 Data identifier requirements | 3 | 1 | 0 | 0 | 4 | 0 | 0 | 3 |
| -- -- 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) | 3 | 1 | 0 | 0 | 4 | 0 | 0 | 3 |
| -- 5.5 Diagnostic services requirements | 159 | 9 | 0 | 0 | 188 | 36 | 4 | 21 |
| -- -- 5.5.1 DiagnosticSessionControl (0x10) service | 8 | 1 | 0 | 0 | 11 | 3 | 2 | 4 |
| -- -- 5.5.2 ECUReset (0x11) service | 18 | 1 | 0 | 0 | 21 | 6 | 1 | 9 |
| -- -- 5.5.3 CommunicationControl (0x28) service | 11 | 3 | 0 | 0 | 15 | 3 | 2 | 4 |
| -- -- 5.5.5 ControlDTCSetting (0x85) service | 8 | 1 | 0 | 0 | 9 | 1 | 1 | 4 |
| -- -- 5.5.6 Link Control (0x87) service | 6 | 1 | 0 | 0 | 7 | 2 | 0 | 3 |
| -- -- 5.5.7 ReadDataByIdentifier (0x22) service | 7 | 0 | 0 | 0 | 7 | 0 | 0 | 3 |
| -- -- 5.5.8 WriteDataByIdentifier (0x2E) service | 10 | 0 | 0 | 0 | 11 | 1 | 1 | 5 |
| -- -- 5.5.10 ReadDTCInformation (0x19) service | 29 | 1 | 0 | 0 | 38 | 9 | 3 | 6 |
| -- -- 5.5.11 InputOutputControlByIdentifier (0x2F) service | 7 | 0 | 0 | 0 | 7 | 0 | 0 | 2 |
| -- -- 5.5.12 RoutineControl (0x31) service | 7 | 0 | 0 | 0 | 8 | 1 | 1 | 1 |
| -- -- 5.5.13 Request Download Service (0x34) | 12 | 1 | 0 | 0 | 13 | 4 | 0 | 4 |
| -- -- 5.5.14 RequestUpload (0x35) | 2 | 0 | 0 | 0 | 2 | 0 | 0 | 0 |
| -- -- 5.5.15 TransferData (0x36) service | 7 | 0 | 0 | 0 | 7 | 0 | 0 | 1 |
| -- -- 5.5.16 RequestTransferExit (0x37) service | 8 | 0 | 0 | 0 | 8 | 0 | 0 | 2 |
| -- -- 5.5.18 Authentication (0x29) service | 16 | 0 | 0 | 0 | 16 | 1 | 1 | 4 |
| -- -- 5.5.19 RequestFileTransfer (0x38) service | 3 | 0 | 0 | 0 | 8 | 5 | 1 | 1 |
| -- 5.6 Routine Identifier Requirements | 56 | 15 | 0 | 0 | 78 | 19 | 4 | 16 |
| -- -- 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions | 16 | 1 | 0 | 0 | 20 | 3 | 3 | 4 |
| -- -- 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) | 13 | 6 | 0 | 0 | 20 | 3 | 1 | 7 |
| -- -- 5.6.3 Routine 0x2401 – Software Installation | 25 | 5 | 0 | 0 | 33 | 12 | 3 | 11 |
| -- -- 5.6.5 Routine 0xCAFE – EMP | 2 | 3 | 0 | 0 | 5 | 1 | 1 | 2 |
| -- 5.7 Fault memory requirements | 23 | 3 | 0 | 0 | 26 | 1 | 0 | 3 |
| -- -- 5.7.2 Occurrence counter OCC | 8 | 1 | 0 | 0 | 9 | 1 | 0 | 3 |
| -- -- 5.7.3 Timestamp of occurrence | 6 | 1 | 0 | 0 | 7 | 0 | 0 | 2 |
| -- -- 5.7.4 Vehicle distance at occurrence | 9 | 1 | 0 | 0 | 10 | 0 | 0 | 2 |
| -- 5.10 Session layer performance requirements | 13 | 2 | 0 | 0 | 15 | 6 | 1 | 6 |
| 6 Normative references | 24 | 2 | 0 | 0 | 26 | 0 | 0 | 0 |
| Artifact | Type | Caption | Page | Related Requirements | Impact |
|---|---|---|---|---|---|
| TABLE-CVS124-0001 | Table | Table 1 – Definition of Terms | page 6 | RFQX-CVS124-0005 | Table source context |
| TABLE-CVS124-0002 | Table | Table 2 – Abbreviated terms | page 6 | RFQX-CVS124-0006 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0003 | Table | Table 3 – Conventions | page 7 | RFQX-CVS124-0014 | Table source context |
| TABLE-CVS124-0004 | Table | Table 4 – Definitions of terms | page 7 | RFQX-CVS124-0014; RFQX-CVS124-0020; RFQX-CVS124-0018; RFQX-CVS124-0019; RFQX-CVS124-0452 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0005 | Table | Table 5 -Data identifiers used at ECU identification | page 8 | RFQX-CVS124-0020; RFQX-CVS124-0018; RFQX-CVS124-0019; RFQX-CVS124-0452 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0006 | Table | Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier | page 10 | RFQX-CVS124-0023; RFQX-CVS124-0025; RFQX-CVS124-0024; RFQX-CVS124-0021; RFQX-CVS124-0022 | State-machine or transition behavior |
| TABLE-CVS124-0007 | Table | Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier | page 10 | RFQX-CVS124-0025; RFQX-CVS124-0024; RFQX-CVS124-0027; RFQX-CVS124-0026 | Table source context |
| TABLE-CVS124-0008 | Table | Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier | page 11 | RFQX-CVS124-0027; RFQX-CVS124-0029; RFQX-CVS124-0026; RFQX-CVS124-0028 | Table source context |
| TABLE-CVS124-0009 | Table | Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier | page 11 | RFQX-CVS124-0029; RFQX-CVS124-0028; RFQX-CVS124-0030; RFQX-CVS124-0027 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0010 | Table | Table 10 – Description of DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier | page 12 | RFQX-CVS124-0030; RFQX-CVS124-0032; RFQX-CVS124-0031 | Table source context |
| TABLE-CVS124-0011 | Table | Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier | page 12 | RFQX-CVS124-0032; RFQX-CVS124-0031; RFQX-CVS124-0033; RFQX-CVS124-0034; RFQX-CVS124-0030 | Table source context |
| TABLE-CVS124-0012 | Table | Table 12 – Description of DID 0xF189 | page 12 | RFQX-CVS124-0034; RFQX-CVS124-0033 | Table source context |
| TABLE-CVS124-0013 | Table | Table 13 – Description of DID 0xF18A systemSupplierIdentifierDataIdentifier | page 13 | RFQX-CVS124-0036; RFQX-CVS124-0035; RFQX-CVS124-0037 | Table source context |
| TABLE-CVS124-0014 | Table | Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier | page 13 | RFQX-CVS124-0037; RFQX-CVS124-0038; RFQX-CVS124-0036 | Table source context |
| TABLE-CVS124-0015 | Table | Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier | page 14 | RFQX-CVS124-0038; RFQX-CVS124-0040 | Table source context |
| TABLE-CVS124-0016 | Table | Table 16 – Description of DID 0xF190 VINDataIdentifier | page 14 | RFQX-CVS124-0040; RFQX-CVS124-0038; RFQX-CVS124-0042; RFQX-CVS124-0041 | Table source context |
| TABLE-CVS124-0017 | Table | Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier | page 14 | RFQX-CVS124-0042; RFQX-CVS124-0041 | Table source context |
| TABLE-CVS124-0018 | Table | Table 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier | page 15 | RFQX-CVS124-0044; RFQX-CVS124-0043; RFQX-CVS124-0045; RFQX-CVS124-0046 | Table source context |
| TABLE-CVS124-0019 | Table | Table 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier | page 15 | RFQX-CVS124-0045; RFQX-CVS124-0044; RFQX-CVS124-0043; RFQX-CVS124-0046 | Table source context |
| TABLE-CVS124-0020 | Table | Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier | page 15 | RFQX-CVS124-0046; RFQX-CVS124-0045; RFQX-CVS124-0044; RFQX-CVS124-0048; RFQX-CVS124-0049 | Table source context |
| TABLE-CVS124-0021 | Table | Table 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier | page 16 | RFQX-CVS124-0048; RFQX-CVS124-0049 | Table source context |
| TABLE-CVS124-0022 | Table | Table 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier | page 16 | RFQX-CVS124-0049; RFQX-CVS124-0048; RFQX-CVS124-0050 | Table source context |
| TABLE-CVS124-0023 | Table | Table 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier | page 16 | RFQX-CVS124-0050; RFQX-CVS124-0047; RFQX-CVS124-0051; RFQX-CVS124-0052; RFQX-CVS124-0440; RFQX-CVS124-0441; RFQX-CVS124-0049 | Table source context |
| TABLE-CVS124-0024 | Table | Table 24 – Description of DID 0xF198 SoftwareItemSemanticDataIdentifiers | page 17 | RFQX-CVS124-0052; RFQX-CVS124-0053; RFQX-CVS124-0047; RFQX-CVS124-0051; RFQX-CVS124-0440; RFQX-CVS124-0441; RFQX-CVS124-0442 | Table source context |
| TABLE-CVS124-0025 | Table | Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s | page 17 | RFQX-CVS124-0053; RFQX-CVS124-0442 | Table source context |
| TABLE-CVS124-0026 | Table | Table 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers | page 18 | RFQX-CVS124-0054; RFQX-CVS124-0055; RFQX-CVS124-0443 | Table source context |
| TABLE-CVS124-0027 | Table | Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier | page 19 | RFQX-CVS124-0055; RFQX-CVS124-0056 | Table source context |
| TABLE-CVS124-0028 | Table | Table 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber | page 19 | RFQX-CVS124-0056; RFQX-CVS124-0057 | State-machine or transition behavior |
| TABLE-CVS124-0029 | Table | Table 29 – Description of DID 0xF1A6 engineNumber | page 19 | RFQX-CVS124-0057; RFQX-CVS124-0058; RFQX-CVS124-0059; RFQX-CVS124-0056 | Table source context |
| TABLE-CVS124-0030 | Table | Table 30 – Description of DID 0xF1A9 Lifetime ECU-runtime at software update stamp | page 20 | RFQX-CVS124-0059; RFQX-CVS124-0061; RFQX-CVS124-0058; RFQX-CVS124-0060 | Software update or memory programming context |
| TABLE-CVS124-0031 | Table | Table 31 – Description of DID 0xF1AA Mileage at software update stamp | page 20 | RFQX-CVS124-0061; RFQX-CVS124-0060; RFQX-CVS124-0062; RFQX-CVS124-0063; RFQX-CVS124-0059 | Software update or memory programming context |
| TABLE-CVS124-0032 | Table | Table 32 – Description of DID 0xF1AB Date at software update stamp | page 21 | RFQX-CVS124-0063; RFQX-CVS124-0062; RFQX-CVS124-0064 | Software update or memory programming context |
| TABLE-CVS124-0033 | Table | Table 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier | page 21 | RFQX-CVS124-0064; RFQX-CVS124-0065; RFQX-CVS124-0453 | State-machine or transition behavior |
| TABLE-CVS124-0034 | Table | Table 34 – Description of DID 0xF1AF NodeUID | page 21 | RFQX-CVS124-0065; RFQX-CVS124-0068; RFQX-CVS124-0066; RFQX-CVS124-0067; RFQX-CVS124-0453; RFQX-CVS124-0454; RFQX-CVS124-0455; RFQX-CVS124-0064 | Table source context |
| TABLE-CVS124-0035 | Table | Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber | page 22 | RFQX-CVS124-0068; RFQX-CVS124-0070; RFQX-CVS124-0066; RFQX-CVS124-0067; RFQX-CVS124-0069; RFQX-CVS124-0455; RFQX-CVS124-0454; RFQX-CVS124-0456 | Table source context |
| TABLE-CVS124-0036 | Table | Table 36 – Description of DID 0xF1BA RBACCStructureVersion | page 22 | RFQX-CVS124-0070; RFQX-CVS124-0072; RFQX-CVS124-0069; RFQX-CVS124-0071; RFQX-CVS124-0456; RFQX-CVS124-0068 | Table source context |
| TABLE-CVS124-0037 | Table | Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier | page 22 | RFQX-CVS124-0072; RFQX-CVS124-0071; RFQX-CVS124-0073 | Security protocol or cryptographic context |
| TABLE-CVS124-0038 | Table | Table 38 – Description of DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber | page 23 | RFQX-CVS124-0073; RFQX-CVS124-0074; RFQX-CVS124-0075; RFQX-CVS124-0076; RFQX-CVS124-0077; RFQX-CVS124-0078; RFQX-CVS124-0079 | State-machine or transition behavior |
| TABLE-CVS124-0039 | Table | Table 39 – Diagnostic service support | page 24 | RFQX-CVS124-0080; RFQX-CVS124-0079; RFQX-CVS124-0078; RFQX-CVS124-0081; RFQX-CVS124-0082; RFQX-CVS124-0083; RFQX-CVS124-0084; RFQX-CVS124-0085 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0040 | Table | Table 40 – Diagnostic Safe State check for Services | page 25 | RFQX-CVS124-0085; RFQX-CVS124-0086; RFQX-CVS124-0087; RFQX-CVS124-0084; RFQX-CVS124-0088; RFQX-CVS124-0458 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0041 | Table | Table 41 lists reserved ECU DIDs/DID ranges which are not used for identification and which | page 31 | RFQX-CVS124-0130; RFQX-CVS124-0129; RFQX-CVS124-0131; RFQX-CVS124-0132; RFQX-CVS124-0464; RFQX-CVS124-0093; RFQX-CVS124-0463 | Table source context |
| TABLE-CVS124-0042 | Table | Table 41 – Data identifier (DID) ranges | page 31 | RFQX-CVS124-0131; RFQX-CVS124-0129; RFQX-CVS124-0130; RFQX-CVS124-0132; RFQX-CVS124-0464; RFQX-CVS124-0463 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0043 | Table | Table 42 – IVD DIDs | page 31 | RFQX-CVS124-0130; RFQX-CVS124-0131; RFQX-CVS124-0132; RFQX-CVS124-0133; RFQX-CVS124-0134; RFQX-CVS124-0135; RFQX-CVS124-0136; RFQX-CVS124-0137 | State-machine or transition behavior |
| TABLE-CVS124-0044 | Table | Table 43 – Service 0x10 request parameter diagnosticSessionType description | page 32 | RFQX-CVS124-0139; RFQX-CVS124-0133; RFQX-CVS124-0134; RFQX-CVS124-0135; RFQX-CVS124-0136; RFQX-CVS124-0137; RFQX-CVS124-0140; RFQX-CVS124-0142 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0045 | Table | Table 44 – Service 0x11 request parameter resetType description | page 34 | RFQX-CVS124-0156; RFQX-CVS124-0157; RFQX-CVS124-0160; RFQX-CVS124-0161; RFQX-CVS124-0162; RFQX-CVS124-0155; RFQX-CVS124-0163; RFQX-CVS124-0153 | Table source context |
| TABLE-CVS124-0046 | Table | Table 45 – Service 0x11 positive response parameter description | page 34 | RFQX-CVS124-0164; RFQX-CVS124-0160; RFQX-CVS124-0161; RFQX-CVS124-0162; RFQX-CVS124-0163; RFQX-CVS124-0167; RFQX-CVS124-0165; RFQX-CVS124-0166 | Table source context |
| TABLE-CVS124-0047 | Table | Table 46 – Service 0x11 negative response codes | page 35 | RFQX-CVS124-0167; RFQX-CVS124-0165; RFQX-CVS124-0166; RFQX-CVS124-0168; RFQX-CVS124-0170; RFQX-CVS124-0171; RFQX-CVS124-0172; RFQX-CVS124-0173 | Table source context |
| TABLE-CVS124-0048 | Table | Table 47 – Service 0x28 request parameter description | page 36 | RFQX-CVS124-0176; RFQX-CVS124-0177; RFQX-CVS124-0178; RFQX-CVS124-0174; RFQX-CVS124-0175; RFQX-CVS124-0179 | Table source context |
| TABLE-CVS124-0049 | Table | Table 48 – Service 0x28 request parameter controlType description | page 36 | RFQX-CVS124-0177; RFQX-CVS124-0176; RFQX-CVS124-0178; RFQX-CVS124-0174; RFQX-CVS124-0175; RFQX-CVS124-0179 | Table source context |
| TABLE-CVS124-0050 | Table | Table 49 – Service 0x28 request parameter communicationType description | page 36 | RFQX-CVS124-0178; RFQX-CVS124-0176; RFQX-CVS124-0177; RFQX-CVS124-0174; RFQX-CVS124-0179; RFQX-CVS124-0180 | Table source context |
| TABLE-CVS124-0051 | Table | Table 50 – Service 0x87 request parameter linkControlType description | page 39 | RFQX-CVS124-0197; RFQX-CVS124-0198; RFQX-CVS124-0196; RFQX-CVS124-0199; RFQX-CVS124-0200; RFQX-CVS124-0201; RFQX-CVS124-0194; RFQX-CVS124-0195 | State-machine or transition behavior |
| TABLE-CVS124-0052 | Table | Table 51 – Service 0x87 request parameter linkControlModeIdentifier description | page 39 | RFQX-CVS124-0198; RFQX-CVS124-0197; RFQX-CVS124-0196; RFQX-CVS124-0199; RFQX-CVS124-0200; RFQX-CVS124-0201; RFQX-CVS124-0202 | Table source context |
| TABLE-CVS124-0053 | Table | Table 52 – Service 0x19 request parameter reportType description | page 41 | RFQX-CVS124-0220; RFQX-CVS124-0218; RFQX-CVS124-0214; RFQX-CVS124-0215; RFQX-CVS124-0216; RFQX-CVS124-0217; RFQX-CVS124-0219; RFQX-CVS124-0221 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0054 | Table | Table 53 – Service 0x19 request parameter DTCMaskRecord description | page 42 | RFQX-CVS124-0224; RFQX-CVS124-0221; RFQX-CVS124-0222; RFQX-CVS124-0223; RFQX-CVS124-0225; RFQX-CVS124-0226; RFQX-CVS124-0227 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0055 | Table | Table 54 – Service 0x19 request parameter DTCExtDataRecordNumber description | page 43 | RFQX-CVS124-0227; RFQX-CVS124-0228; RFQX-CVS124-0229; RFQX-CVS124-0230; RFQX-CVS124-0231; RFQX-CVS124-0232; RFQX-CVS124-0233; RFQX-CVS124-0225 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0056 | Table | Table 55 – Snapshot data sub-function (0x04) positive response message content and format | page 44 | RFQX-CVS124-0238; RFQX-CVS124-0235; RFQX-CVS124-0236 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0057 | Table | Table 56 – Service 0x19 response parameter DTCExtDataRecordNumber description | page 51 | RFQX-CVS124-0243; RFQX-CVS124-0244; RFQX-CVS124-0242 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0058 | Table | Table 57 – Extended data sub-function (0x06) positive response message content and format | page 51 | RFQX-CVS124-0245; RFQX-CVS124-0243; RFQX-CVS124-0244 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0059 | Table | Table 58 – Service 0x2F request parameter controlOptionRecord description | page 54 | RFQX-CVS124-0257; RFQX-CVS124-0258; RFQX-CVS124-0252; RFQX-CVS124-0253; RFQX-CVS124-0254; RFQX-CVS124-0255; RFQX-CVS124-0256 | State-machine or transition behavior |
| TABLE-CVS124-0060 | Table | Table 59 – Service 0x2F request parameter inputOutputControlParameter description | page 54 | RFQX-CVS124-0258; RFQX-CVS124-0257; RFQX-CVS124-0259; RFQX-CVS124-0260; RFQX-CVS124-0261 | Table source context |
| TABLE-CVS124-0061 | Table | Table 60 – Service 0x31 request parameter RoutineControlType description | page 55 | RFQX-CVS124-0263; RFQX-CVS124-0261; RFQX-CVS124-0259; RFQX-CVS124-0260; RFQX-CVS124-0262; RFQX-CVS124-0264; RFQX-CVS124-0266; RFQX-CVS124-0459 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0062 | Table | Table 61 are reserved by TRATON and shall not be used by the system supplier. | page 55 | RFQX-CVS124-0264; RFQX-CVS124-0260; RFQX-CVS124-0261; RFQX-CVS124-0262; RFQX-CVS124-0263; RFQX-CVS124-0265; RFQX-CVS124-0266; RFQX-CVS124-0459 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0063 | Table | Table 61 – Service 0x31 request parameter RoutineIdentifier description | page 56 | RFQX-CVS124-0266; RFQX-CVS124-0264; RFQX-CVS124-0270; RFQX-CVS124-0271; RFQX-CVS124-0267; RFQX-CVS124-0268; RFQX-CVS124-0269; RFQX-CVS124-0459 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0064 | Table | Table 62 – Service 0x34 request parameter description | page 58 | RFQX-CVS124-0275; RFQX-CVS124-0276; RFQX-CVS124-0274 | Software update or memory programming context |
| TABLE-CVS124-0065 | Table | Table 63 – Service 0x34 request parameter dataFormatIdentifier description | page 58 | RFQX-CVS124-0276; RFQX-CVS124-0277; RFQX-CVS124-0278 | Table source context |
| TABLE-CVS124-0066 | Table | Table 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description | page 59 | RFQX-CVS124-0277; RFQX-CVS124-0278 | Software update or memory programming context |
| TABLE-CVS124-0067 | Table | Table 65 – Positive response parameter description | page 59 | RFQX-CVS124-0278; RFQX-CVS124-0277; RFQX-CVS124-0279; RFQX-CVS124-0280 | Software update or memory programming context |
| TABLE-CVS124-0068 | Table | Table 66 – Service 0x34 response parameter lengthFormatIdentifier description | page 59 | RFQX-CVS124-0279; RFQX-CVS124-0280 | Table source context |
| TABLE-CVS124-0069 | Table | Table 67 – Service 0x35 request parameter description | page 60 | RFQX-CVS124-0280; RFQX-CVS124-0281; RFQX-CVS124-0279 | Software update or memory programming context |
| TABLE-CVS124-0070 | Table | Table 68 – Service 0x35 request parameter dataFormatIdentifier description | page 60 | RFQX-CVS124-0281; RFQX-CVS124-0280; RFQX-CVS124-0283; RFQX-CVS124-0284; RFQX-CVS124-0285; RFQX-CVS124-0286 | Table source context |
| TABLE-CVS124-0071 | Table | Table 69 – Service 0x35 request parameter addressAndLengthFormatIdentifier description | page 61 | RFQX-CVS124-0283; RFQX-CVS124-0287; RFQX-CVS124-0284; RFQX-CVS124-0285; RFQX-CVS124-0286; RFQX-CVS124-0288 | Software update or memory programming context |
| TABLE-CVS124-0072 | Table | Table 70 – Service 0x35 response parameter lengthFormatIdentifier description | page 61 | RFQX-CVS124-0287; RFQX-CVS124-0283; RFQX-CVS124-0282; RFQX-CVS124-0284; RFQX-CVS124-0285; RFQX-CVS124-0286; RFQX-CVS124-0288; RFQX-CVS124-0289 | Table source context |
| TABLE-CVS124-0073 | Table | Table 71 – Service 0x37 request parameter description | page 62 | RFQX-CVS124-0294; RFQX-CVS124-0293; RFQX-CVS124-0296; RFQX-CVS124-0289; RFQX-CVS124-0290; RFQX-CVS124-0291; RFQX-CVS124-0292; RFQX-CVS124-0295 | Table source context |
| TABLE-CVS124-0074 | Table | Table 72 – Service 0x37 positive response parameter description | page 62 | RFQX-CVS124-0296; RFQX-CVS124-0293; RFQX-CVS124-0294; RFQX-CVS124-0290; RFQX-CVS124-0291; RFQX-CVS124-0292; RFQX-CVS124-0295; RFQX-CVS124-0297 | Table source context |
| TABLE-CVS124-0075 | Table | Table 73 – Service 0x29 supported negative response codes | page 64 | RFQX-CVS124-0312; RFQX-CVS124-0307; RFQX-CVS124-0308; RFQX-CVS124-0309; RFQX-CVS124-0310; RFQX-CVS124-0311; RFQX-CVS124-0313; RFQX-CVS124-0314 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0076 | Table | Table 74 – Service 0x38 request parameter modeOfOperation description | page 65 | RFQX-CVS124-0315; RFQX-CVS124-0313; RFQX-CVS124-0314; RFQX-CVS124-0322; RFQX-CVS124-0321 | Software update or memory programming context |
| TABLE-CVS124-0077 | Table | Table 75 – Service 0x38 request parameter dataFormatIdentifier description | page 66 | RFQX-CVS124-0322; RFQX-CVS124-0321; RFQX-CVS124-0323; RFQX-CVS124-0324; RFQX-CVS124-0325; RFQX-CVS124-0326 | Table source context |
| TABLE-CVS124-0078 | Table | Table 76 – RoutineControl (CheckProgrammingPreconditions) positive response format | page 67 | RFQX-CVS124-0335; RFQX-CVS124-0334; RFQX-CVS124-0329; RFQX-CVS124-0330; RFQX-CVS124-0332; RFQX-CVS124-0333; RFQX-CVS124-0336; RFQX-CVS124-0337 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0079 | Table | Table 77 – Programming preconditions | page 68 | RFQX-CVS124-0340; RFQX-CVS124-0337; RFQX-CVS124-0339; RFQX-CVS124-0338 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0080 | Table | Table 78 – RoutineIdentifier 0xFF00 description | page 70 | RFQX-CVS124-0349; RFQX-CVS124-0346; RFQX-CVS124-0348; RFQX-CVS124-0351; RFQX-CVS124-0350 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0081 | Table | Table 79 – Request parameter addressAndLengthFormatIdentifier values | page 71 | RFQX-CVS124-0351; RFQX-CVS124-0352; RFQX-CVS124-0355; RFQX-CVS124-0354; RFQX-CVS124-0350; RFQX-CVS124-0353 | Software update or memory programming context |
| TABLE-CVS124-0082 | Table | Table 80 – RoutineControl (EraseMemory) positive response format | page 71 | RFQX-CVS124-0355; RFQX-CVS124-0352; RFQX-CVS124-0354; RFQX-CVS124-0353; RFQX-CVS124-0356; RFQX-CVS124-0357 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0083 | Table | Table 81 – RoutineControl (EraseMemory) routineResult values | page 72 | RFQX-CVS124-0356; RFQX-CVS124-0357; RFQX-CVS124-0358 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0084 | Table | Table 82 – Example #1: Request: client → server | page 72 | RFQX-CVS124-0357; RFQX-CVS124-0358; RFQX-CVS124-0359 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0085 | Table | Table 83 – Example #1: Positive response: server → client | page 73 | RFQX-CVS124-0359; RFQX-CVS124-0360 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0086 | Table | Table 84 – Example #1: Negative response: server → client | page 73 | RFQX-CVS124-0359; RFQX-CVS124-0360 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0087 | Table | Table 85 – Example #2: Request: client → server | page 73 | RFQX-CVS124-0359; RFQX-CVS124-0360 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0088 | Table | Table 86 – Example #2: Positive response: server → client | page 73 | RFQX-CVS124-0360; RFQX-CVS124-0361; RFQX-CVS124-0362 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0089 | Table | Table 87 – Example #2: Negative response: server → client | page 74 | RFQX-CVS124-0361; RFQX-CVS124-0362; RFQX-CVS124-0363; RFQX-CVS124-0364; RFQX-CVS124-0365 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0090 | Table | Table 88 – RoutineControl (Software Installation) positive StartRoutine response format | page 75 | RFQX-CVS124-0369; RFQX-CVS124-0368; RFQX-CVS124-0370; RFQX-CVS124-0371; RFQX-CVS124-0367 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0091 | Table | Table 89 – RoutineControl (Software Installation) positive requestRoutineResult response format | page 75 | RFQX-CVS124-0369; RFQX-CVS124-0368; RFQX-CVS124-0370; RFQX-CVS124-0371 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0092 | Table | Table 90 – AuthenticityVerificationStatus | page 75 | RFQX-CVS124-0370; RFQX-CVS124-0369; RFQX-CVS124-0371; RFQX-CVS124-0373; RFQX-CVS124-0372; RFQX-CVS124-0460 | Table source context |
| TABLE-CVS124-0093 | Table | Table 91 – SoftwareInstallationStatus | page 76 | RFQX-CVS124-0374; RFQX-CVS124-0373; RFQX-CVS124-0372; RFQX-CVS124-0376; RFQX-CVS124-0378; RFQX-CVS124-0379; RFQX-CVS124-0380; RFQX-CVS124-0460 | Table source context |
| TABLE-CVS124-0094 | Table | Table 92 – RoutineIdentifier 0xFF01 description | page 77 | RFQX-CVS124-0390; RFQX-CVS124-0389; RFQX-CVS124-0384; RFQX-CVS124-0385; RFQX-CVS124-0386; RFQX-CVS124-0387; RFQX-CVS124-0388; RFQX-CVS124-0391 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0095 | Table | Table 93 – RoutineControl (CheckProgrammingDependencies) positive response format | page 78 | RFQX-CVS124-0392; RFQX-CVS124-0393; RFQX-CVS124-0391; RFQX-CVS124-0390; RFQX-CVS124-0461 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0096 | Table | Table 94 – CheckProgrammingDependencies routineStatusRecord results | page 78 | RFQX-CVS124-0393; RFQX-CVS124-0392; RFQX-CVS124-0391; RFQX-CVS124-0461 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0097 | Table | Table 95 – Example: Request: client → server | page 79 | RFQX-CVS124-0396; RFQX-CVS124-0397; RFQX-CVS124-0394; RFQX-CVS124-0395; RFQX-CVS124-0398 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0098 | Table | Table 96 – Positive response: server → client | page 79 | RFQX-CVS124-0397; RFQX-CVS124-0396; RFQX-CVS124-0394; RFQX-CVS124-0395; RFQX-CVS124-0398; RFQX-CVS124-0399 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0099 | Table | Table 97 – Fault memory DTC status bits description | page 80 | RFQX-CVS124-0399; RFQX-CVS124-0400; RFQX-CVS124-0407; RFQX-CVS124-0401; RFQX-CVS124-0402; RFQX-CVS124-0403; RFQX-CVS124-0404; RFQX-CVS124-0405 | Diagnostic parameter or service behavior |
| TABLE-CVS124-0100 | Table | Table 98 – J1939-71 timestamp format | page 81 | RFQX-CVS124-0414; RFQX-CVS124-0411; RFQX-CVS124-0409; RFQX-CVS124-0410; RFQX-CVS124-0412; RFQX-CVS124-0413; RFQX-CVS124-0415; RFQX-CVS124-0416 | Diagnostic parameter or service behavior |
| DIAGRAM-CVS124-0001 | Diagram | Figure 1 - Overview of relation between specifications | page 5 | None | Diagnostic parameter or service behavior |
| DIAGRAM-CVS124-0002 | Diagram | Figure 2 -State Diagram | page 27 | RFQX-CVS124-0091; RFQX-CVS124-0089; RFQX-CVS124-0092; RFQX-CVS124-0093; RFQX-CVS124-0088 | Diagnostic parameter or service behavior |
Customer-owned responsibility, final customer decisions, and unresolved open points remain unconfirmed.
| ID | Score | Category | Reason | Statement |
|---|---|---|---|---|
| RFQX-CVS124-0039 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Minimum length shall be 8 bytes and the assigned value shall be unique for every unit provided by one supplier per project. |
| RFQX-CVS124-0138 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | The application shall respond with NRC 0x22 (conditionsNotCorrect) if communication has not been switched off. |
| RFQX-CVS124-0141 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | In this process, it shall end all routines and functions that influence programming and ensure that the server checked for safe state conditions at minimal. |
| RFQX-CVS124-0159 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | The implementation of hardReset shall first ensure that data corruption will not occur. |
| RFQX-CVS124-0212 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | If this action is necessary then it shall be integrated implicitly into ECU Reset (0x11) Service subfunction 0x02. |
| RFQX-CVS124-0237 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | 5.5.10.2.6 Response parameter reportDTCSnapshotRecordByDTCNumber The snapshot data sub-function (0x04) shall have positive response message data and format as specified in Table 67. |
| RFQX-CVS124-0241 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | dependent depend ent depende nt U #65+N+M- #66+N+M dataIdentifier 0x0000 – #67+N+M +P Data required by law or regulations Signal dependent depend ent depende nt C1 #68+N+M +P DTCSnapshotRecordNumber#2 (Latest Snapshot captured) 0x02 M #69+N+M +P DTCSnapshotRecordNumberOfIdentifiers#2 0x00 : 0xFF M #70+N+M +P : #70+2*(N +M+P) See specification for DTCSnapshotRecord[]#1 This latest snapshot shall contain the same type of data and format as DTCSnapshotRecord[]#1. |
| RFQX-CVS124-0245 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Table 57 – Extended data sub-function (0x06) positive response message content and format Byte Description Range Resolu tion #1 ReadDTCInformation Response SID = 0x59 M #2 reportType = reportDTCExtDataRecordByDTCNumber 0x06 M #3 : #6 DTCAndStatusRecord[] = [ DTCHighByte DTCMiddleByte DTCLowByte statusOfDTC ] M #7 DTCExtDataRecordNumber#1 This byte shall be set to value 0x11. |
| RFQX-CVS124-0246 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Byte Description Range Resolu tion This byte shall be set to value 2 and is used to identify the response structure variant #9 Occurrence counter OCC, as described in section 5.7.2 [unsigned integer] 0..127 0 M #10 DTC priority 1 – Highest priority 2 - Second highest priority 3 – Lowest priority 255 – Unknown 1..3, 255 0xFF M #11..#16 Time/Date of the first DTC activation See Table 98 but without byte #7 and #8 M #17..#22 Time/Date of the latest DTC activation M #23..#26 ECU Operational hours at the first DTC activation [4-byte int, big endian] as described in section 5.7.5.2. |
| RFQX-CVS124-0248 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Byte Description Range Resolu tion 0: 0 m 1: 5 m (factor 5) … 4261412863: 21 307 064 315 m #35..#38 Total vehicle distance at the latest DTC activation [4-byte int, big endian] in section 5.7.4.1 Not used for TRATON External engine and marine ECUsFor these ECUs these bytes shall contain default value 0xFF (all bytes). |
| Open Point | Priority | Question | Impact | Status |
|---|---|---|---|---|
| OP-001 | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). | TARA scope and effort stay open; downstream assets, goals and design may rework. | Open | |
| OP-002 | Confirm the diagnostic role model, the authorized services per role, and which party owns the diagnostic authorization policy. | Security-access design and verification scope cannot be frozen; risk of an unprotected diagnostic service. | Open | |
| OP-004 | Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. | Update-control scope and evidence ownership stay open; risk of an unprotected update path. | Open | |
| OP-009 | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. | Without an agreed DIA the supplier risks owning customer work products or leaving cybersecurity gaps in the case. | Open | |
| OP-011 | Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. | Supplier position, estimation, and affected design allocation remain conditional for the listed requirements. | Open |
| SSR | Title | Statement | Reqs From This PDF | Other PDFs | Status |
|---|---|---|---|---|---|
| SSR-BOOT-001 | Secure software update and flash readiness — Bootloader and Application State Handling | The ECU shall verify boot and application authenticity/integrity for Secure software update and flash readiness and enforce the defined behaviour on verification failure (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | RFQX-CVS124-0014 | no | Blocked by Customer Clarification |
| SSR-BOOT-002 | Secure software update and flash readiness — Bootloader and Application State Handling | The ECU shall verify boot and application authenticity/integrity for Secure software update and flash readiness and enforce the defined behaviour on verification failure (Hardware domain; allocated to Hardware Platform). | RFQX-CVS124-0343 | no | Candidate |
| SSR-BOOT-005 | Bootloader and Application State Handling — Bootloader and Application State Handling | The ECU shall verify boot and application authenticity/integrity for Bootloader and Application State Handling and enforce the defined behaviour on verification failure (Software domain; allocated to Application Software). | RFQX-CVS124-0193; RFQX-CVS124-0354 | no | Ready for Customer Alignment |
| SSR-COM-002 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (System domain; allocated to System Core). | RFQX-CVS124-0172 | no | Candidate |
| SSR-COM-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (IT / backend domain; allocated to Backend and IT Systems). | RFQX-CVS124-0433 | no | Blocked by Customer Clarification |
| SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software). | RFQX-CVS124-0168; RFQX-CVS124-0198 | no | Ready for Customer Alignment |
| SSR-COM-007 | External Interfaces — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for External Interfaces, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Interface domain; allocated to External Interfaces; interface: External Interfaces). | RFQX-CVS124-0149 | no | Candidate |
| SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems). | RFQX-CVS124-0387 | no | Ready for Customer Alignment |
| SSR-DAI-004 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (Software domain; allocated to Application Software). | RFQX-CVS124-0385; RFQX-CVS124-0386 | no | Ready for Customer Alignment |
| SSR-DAI-005 | Security evidence and traceability — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | RFQX-CVS124-0370 | no | Ready for Customer Alignment |
| SSR-DAI-006 | Security evidence and traceability — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | RFQX-CVS124-0362; RFQX-CVS124-0365 | no | Blocked by Customer Clarification |
| SSR-DAI-007 | Security evidence and traceability — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Security evidence and traceability data and reject manipulated or unauthenticated data (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | RFQX-CVS124-0369; RFQX-CVS124-0371 | no | Candidate |
| SSR-DIAG-003 | Diagnostic Services — Diagnostic Services | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | RFQX-CVS124-0087; RFQX-CVS124-0203; RFQX-CVS124-0242; RFQX-CVS124-0400; RFQX-CVS124-0407; RFQX-CVS124-0408; RFQX-CVS124-0409; RFQX-CVS124-0415; RFQX-CVS124-0416; RFQX-CVS124-0418 | no | Candidate |
| SSR-DIAG-004 | Diagnostic Services — Diagnostic Services | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Process / compliance domain; allocated to Compliance Process). | RFQX-CVS124-0146; RFQX-CVS124-0223; RFQX-CVS124-0226; RFQX-CVS124-0229; RFQX-CVS124-0230; RFQX-CVS124-0232; RFQX-CVS124-0233; RFQX-CVS124-0234; RFQX-CVS124-0235; RFQX-CVS124-0236; RFQX-CVS124-0251; RFQX-CVS124-0252; RFQX-CVS124-0256 | no | Candidate |
| SSR-DIAG-005 | Diagnostic Services — Diagnostic Services | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Hardware domain; allocated to Hardware Platform). | RFQX-CVS124-0201 | no | Candidate |
| SSR-DIAG-006 | Diagnostic Services — Diagnostic Services | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Software domain; allocated to Application Software). | RFQX-CVS124-0207; RFQX-CVS124-0238 | no | Blocked by Customer Clarification |
| SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | The ECU hardware shall provide the platform and secure-storage capabilities required for Hardware / HSM / Secure Storage (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface). | RFQX-CVS124-0058; RFQX-CVS124-0130; RFQX-CVS124-0152; RFQX-CVS124-0153; RFQX-CVS124-0209; RFQX-CVS124-0270 | no | Ready for Customer Alignment |
| SSR-KEY-001 | Key and Certificate Handling — Key and Certificate Handling | The ECU shall manage key and certificate material for Key and Certificate Handling across provisioning, storage, use, renewal and revocation per the agreed key lifecycle (Cybersecurity domain; allocated to Security Services; security capability: Certificate handling; interface: OEM/Customer Review Interface). | RFQX-CVS124-0160; RFQX-CVS124-0210 | no | Blocked by Customer Clarification |
| SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Cybersecurity domain; allocated to Security Services; security capability: Diagnostic security; interface: OEM/Customer Review Interface). | RFQX-CVS124-0075; RFQX-CVS124-0077; RFQX-CVS124-0078; RFQX-CVS124-0171; RFQX-CVS124-0186; RFQX-CVS124-0431; RFQX-CVS124-0432 | no | Blocked by Customer Clarification |
| SSR-RBAC-003 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (IT / backend domain; allocated to Backend and IT Systems). | RFQX-CVS124-0083 | no | Blocked by Customer Clarification |
| SSR-RBAC-004 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Software domain; allocated to Application Software). | RFQX-CVS124-0084; RFQX-CVS124-0135; RFQX-CVS124-0305; RFQX-CVS124-0306; RFQX-CVS124-0307 | no | Blocked by Customer Clarification |
| SSR-SDT-001 | Secure Data Transfer / Data Security Container — Secure Data Transfer / Data Security Container | The ECU shall protect security-relevant data transfer for Secure Data Transfer / Data Security Container using the agreed secured data transfer / data security container scheme (Software domain; allocated to Application Software). | RFQX-CVS124-0273; RFQX-CVS124-0346 | no | Ready for Customer Alignment |
| SSR-SYS-001 | System Function — System Function | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | RFQX-CVS124-0019; RFQX-CVS124-0036; RFQX-CVS124-0089; RFQX-CVS124-0132; RFQX-CVS124-0195; RFQX-CVS124-0295; RFQX-CVS124-0297; RFQX-CVS124-0303; RFQX-CVS124-0304; RFQX-CVS124-0333; RFQX-CVS124-0334; RFQX-CVS124-0338; RFQX-CVS124-0350; RFQX-CVS124-0356; RFQX-CVS124-0367; RFQX-CVS124-0372; RFQX-CVS124-0373; RFQX-CVS124-0376; RFQX-CVS124-0383; RFQX-CVS124-0390; RFQX-CVS124-0402; RFQX-CVS124-0403; RFQX-CVS124-0404; RFQX-CVS124-0405; RFQX-CVS124-0410; RFQX-CVS124-0412; RFQX-CVS124-0417; RFQX-CVS124-0420; RFQX-CVS124-0421; RFQX-CVS124-0427; RFQX-CVS124-0435 | no | Candidate |
| SSR-SYS-002 | System Function — System Function | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Process / compliance domain; allocated to Compliance Process; interface: OEM/Customer Review Interface). | RFQX-CVS124-0129; RFQX-CVS124-0133; RFQX-CVS124-0134; RFQX-CVS124-0147; RFQX-CVS124-0165; RFQX-CVS124-0182; RFQX-CVS124-0202; RFQX-CVS124-0213; RFQX-CVS124-0216; RFQX-CVS124-0222; RFQX-CVS124-0228; RFQX-CVS124-0250; RFQX-CVS124-0254; RFQX-CVS124-0259; RFQX-CVS124-0264; RFQX-CVS124-0267; RFQX-CVS124-0284; RFQX-CVS124-0285; RFQX-CVS124-0288; RFQX-CVS124-0289; RFQX-CVS124-0290; RFQX-CVS124-0302; RFQX-CVS124-0312; RFQX-CVS124-0325; RFQX-CVS124-0437 | no | Candidate |
| SSR-SYS-003 | System Function — System Function | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | RFQX-CVS124-0079; RFQX-CVS124-0082; RFQX-CVS124-0150; RFQX-CVS124-0162; RFQX-CVS124-0180; RFQX-CVS124-0244; RFQX-CVS124-0300; RFQX-CVS124-0313; RFQX-CVS124-0315; RFQX-CVS124-0321; RFQX-CVS124-0332; RFQX-CVS124-0352; RFQX-CVS124-0368; RFQX-CVS124-0374; RFQX-CVS124-0398 | no | Candidate |
| SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | RFQX-CVS124-0018; RFQX-CVS124-0088; RFQX-CVS124-0154; RFQX-CVS124-0225; RFQX-CVS124-0381; RFQX-CVS124-0384; RFQX-CVS124-0406; RFQX-CVS124-0436 | no | Blocked by Customer Clarification |
| SSR-TOOL-003 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Software domain; allocated to Application Software). | RFQX-CVS124-0157; RFQX-CVS124-0161; RFQX-CVS124-0192; RFQX-CVS124-0272; RFQX-CVS124-0274; RFQX-CVS124-0275; RFQX-CVS124-0341; RFQX-CVS124-0345; RFQX-CVS124-0364 | no | Ready for Customer Alignment |
| SSR-TOOL-004 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | RFQX-CVS124-0434; RFQX-CVS124-0438; RFQX-CVS124-0439 | no | Ready for Customer Alignment |
| SSR-UPD-001 | Secure software update and flash readiness — Software Update / Flashing | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | RFQX-CVS124-0060; RFQX-CVS124-0137; RFQX-CVS124-0140; RFQX-CVS124-0185; RFQX-CVS124-0389; RFQX-CVS124-0391 | no | Blocked by Customer Clarification |
| SSR-UPD-002 | Secure software update and flash readiness — Software Update / Flashing | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | RFQX-CVS124-0145; RFQX-CVS124-0327; RFQX-CVS124-0329; RFQX-CVS124-0330; RFQX-CVS124-0336; RFQX-CVS124-0337; RFQX-CVS124-0339; RFQX-CVS124-0348; RFQX-CVS124-0366; RFQX-CVS124-0388; RFQX-CVS124-0392 | no | Blocked by Customer Clarification |
| SSR-UPD-003 | Secure software update and flash readiness — Software Update / Flashing | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | RFQX-CVS124-0142; RFQX-CVS124-0397 | no | Blocked by Customer Clarification |
| SSR-UPD-004 | Secure software update and flash readiness — Software Update / Flashing | The ECU shall support secure software update/flashing for Secure software update and flash readiness, accepting only authenticated, integrity-verified software through the agreed programming sequence (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface). | RFQX-CVS124-0024; RFQX-CVS124-0028; RFQX-CVS124-0031; RFQX-CVS124-0043; RFQX-CVS124-0074 | no | Candidate |