Document Purpose
Confirmed by requirements: this diagnostic standard contributes 301 Markdown-derived RFQ requirements with the strongest evidence in diagnostics and service access.
CVS124
Product and cybersecurity architecture understanding package generated from Markdown-derived requirements.
CVS124
Diagnostic Standard · Diagnostics · Diagnostics and service access
Executive Takeaway
Confirmed by requirements: this diagnostic standard contributes 301 Markdown-derived RFQ requirements with the strongest evidence in diagnostics and service access. Inferred from requirement pattern: for RFQX it affects the Electric Clutch Actuator ECU on the TRATON GW AMT platform by shaping diagnostics and service access; core eca system behavior; system architecture design.
Confirmed by requirements: supplier positioning is 25 accept; 150 accept with assumption; 45 partially accept; 3 needs customer clarification; 2 needs internal review (showing 5 of 6). The generated traceability links this document to 28 supplier system requirement records. Inferred from mapped features, capabilities, and interfaces: the main design/security impact is diagnostics and service access; core eca system behavior; system architecture design. These themes should drive concept updates, verification evidence, and supplier proposal assumptions only where the linked requirements support them.
Requires customer confirmation: 5 document-linked open point(s) remain, 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. (showing 3 of 5). Do not convert these items into agreed baseline scope until the customer confirms the decision. Confidence and limits: High confidence. Evidence is limited to Markdown-derived requirements, registers, open points, and SSR links; no downstream PDF analysis or AI-generated conclusion is claimed.
Requirements301from this PDF
Critical48ranked
Open Points5linked
Derived SSRs28linked
Concept Impactyesdocument-specific
Estimation Impactyesdocument-specific
Document Abstract
Engineering Interpretation
Inferred from requirement pattern: for RFQX it affects the Electric Clutch Actuator ECU on the TRATON GW AMT platform by shaping diagnostics and service access; core eca system behavior; system architecture design.
Main Requirement Themes
Diagnostics and service access; Core ECA system behavior; System architecture design; System; Responsibility and customer approval model (showing 5 of 8)
System / Security Impact
Inferred from mapped features, capabilities, and interfaces: the main design/security impact is diagnostics and service access; core eca system behavior; system architecture design. These themes should drive concept updates, verification evidence, and supplier proposal assumptions only where the linked requirements support them.
Supplier Proposal Impact
Confirmed by requirements: supplier positioning is 25 accept; 150 accept with assumption; 45 partially accept; 3 needs customer clarification; 2 needs internal review (showing 5 of 6). The generated traceability links this document to 28 supplier system requirement records.
Customer Clarification Impact
Requires customer confirmation: 5 document-linked open point(s) remain, 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. (showing 3 of 5). Do not convert these items into agreed baseline scope until the customer confirms the decision.
Confidence and Limits
Confidence and limits: High confidence. Evidence is limited to Markdown-derived requirements, registers, open points, and SSR links; no downstream PDF analysis or AI-generated conclusion is claimed.
Main Requirement Themes
| Theme | Engineering Meaning | Requirement Count | Representative Requirements |
|---|---|---|---|
| Diagnostics and service access | Defines UDS service behavior, authorization expectations, safe-state checks, and diagnostic evidence. | 261 | REQ-AUTO-00496; REQ_UDS-0001; REQ_UDS-0002 |
| Core ECA system behavior | Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope. | 228 | REQ-AUTO-00484; REQ-AUTO-00485; REQ-AUTO-00486 |
| System architecture design | Groups related document requirements into a single engineering theme. | 225 | REQ-AUTO-00484; REQ-AUTO-00485; REQ-AUTO-00488 |
| System | Groups related document requirements into a single engineering theme. | 111 | REQ-AUTO-00484; REQ-AUTO-00485; REQ-AUTO-00488 |
| Responsibility and customer approval model | Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk. | 109 | REQ-AUTO-00486; REQ-AUTO-00487; REQ-AUTO-00493 |
| Software | Groups related document requirements into a single engineering theme. | 89 | REQ_UDS-0003; REQ_UDS-0004; REQ_UDS-0006 |
| Cybersecurity concept and evidence | Drives cybersecurity concept, risk treatment, verification evidence, and traceability obligations. | 78 | REQ-AUTO-00486; REQ-AUTO-00487; REQ-AUTO-00493 |
| System core | Groups related document requirements into a single engineering theme. | 78 | REQ-AUTO-00484; REQ-AUTO-00488; REQ-AUTO-00489 |
Document Content Structure
| Section | Requirements | Critical | Open Points | SSR Links |
|---|---|---|---|---|
| 4 Terms, definitions and abbreviations | 12 | 1 | 1 | 3 |
| -- 4.2 Abbreviations | 8 | 1 | 1 | 2 |
| -- 4.3 Conventions | 4 | 0 | 0 | 2 |
| 5 Requirements | 283 | 47 | 4 | 26 |
| -- 5.2 ECU Identification Requirements | 33 | 1 | 1 | 5 |
| -- -- 5.2.1 Used data identifier in order to identify an ECU | 33 | 1 | 1 | 5 |
| -- 5.3 Diagnostic sessions requirements | 19 | 3 | 1 | 8 |
| -- 5.4 Data identifier requirements | 3 | 0 | 0 | 3 |
| -- -- 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) | 3 | 0 | 0 | 3 |
| -- 5.5 Diagnostic services requirements | 133 | 21 | 3 | 17 |
| -- -- 5.5.1 DiagnosticSessionControl (0x10) service | 9 | 2 | 2 | 6 |
| -- -- 5.5.2 ECUReset (0x11) service | 16 | 6 | 1 | 8 |
| -- -- 5.5.3 CommunicationControl (0x28) service | 7 | 2 | 1 | 5 |
| -- -- 5.5.5 ControlDTCSetting (0x85) service | 7 | 1 | 1 | 4 |
| -- -- 5.5.6 Link Control (0x87) service | 6 | 2 | 1 | 3 |
| -- -- 5.5.7 ReadDataByIdentifier (0x22) service | 3 | 0 | 0 | 2 |
| -- -- 5.5.8 WriteDataByIdentifier (0x2E) service | 8 | 1 | 1 | 6 |
| -- -- 5.5.10 ReadDTCInformation (0x19) service | 29 | 2 | 2 | 6 |
| -- -- 5.5.11 InputOutputControlByIdentifier (0x2F) service | 5 | 0 | 0 | 2 |
| -- -- 5.5.12 RoutineControl (0x31) service | 5 | 0 | 0 | 2 |
| -- -- 5.5.13 Request Download Service (0x34) | 10 | 4 | 1 | 4 |
| -- -- 5.5.14 RequestUpload (0x35) | 2 | 0 | 0 | 0 |
| -- -- 5.5.15 TransferData (0x36) service | 5 | 0 | 0 | 2 |
| -- -- 5.5.16 RequestTransferExit (0x37) service | 4 | 0 | 0 | 2 |
| -- -- 5.5.18 Authentication (0x29) service | 10 | 1 | 1 | 5 |
| -- -- 5.5.19 RequestFileTransfer (0x38) service | 7 | 0 | 0 | 3 |
| -- 5.6 Routine Identifier Requirements | 61 | 14 | 2 | 16 |
| -- -- 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions | 15 | 1 | 1 | 6 |
| -- -- 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) | 13 | 2 | 1 | 9 |
| -- -- 5.6.3 Routine 0x2401 – Software Installation | 31 | 10 | 1 | 11 |
| -- -- 5.6.5 Routine 0xCAFE – EMP | 2 | 1 | 1 | 2 |
| -- 5.7 Fault memory requirements | 20 | 2 | 1 | 3 |
| -- -- 5.7.2 Occurrence counter OCC | 7 | 1 | 1 | 3 |
| -- -- 5.7.3 Timestamp of occurrence | 6 | 0 | 0 | 1 |
| -- -- 5.7.4 Vehicle distance at occurrence | 7 | 1 | 1 | 1 |
| -- 5.10 Session layer performance requirements | 14 | 6 | 1 | 6 |
| 6 Normative references | 2 | 0 | 0 | 0 |
What This PDF Is About
| Field | Value |
|---|---|
| Source PDF | customer-input/pdf/CVS124.pdf |
| Converted Markdown | converted/markdown/CVS124.md |
| Document Type | Diagnostic Standard |
| Domain | Diagnostics |
| Scope Summary | 301 extracted requirements; 28 linked SSRs; 5 linked open points. |
| Main Themes | Diagnostics and service access; Core ECA system behavior; System architecture design; System; Responsibility and customer approval model (showing 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. |
Key Conclusions From This PDF
- Confirmed by requirements: this diagnostic standard contributes 301 Markdown-derived RFQ requirements with the strongest evidence in diagnostics and service access.
- Confirmed by requirements: supplier positioning is 25 accept; 150 accept with assumption; 45 partially accept; 3 needs customer clarification; 2 needs internal review (showing 5 of 6). The generated traceability links this document to 28 supplier system requirement records.
- Requires customer confirmation: 5 document-linked open point(s) remain, 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. (showing 3 of 5). Do not convert these items into agreed baseline scope until the customer confirms the decision.
Critical Requirements
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| ID | Score | Category | Requirement / Reason | Supplier Position |
|---|---|---|---|---|
| REQ-AUTO-00634 | 95 | High risk due to unclear OEM/supplier responsibility | Internal Page 52 (90) 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; Unknown estimation impact; blocks SSR derivation | Needs Customer Clarification |
| REQ-AUTO-00488 | 80 | High risk due to unclear OEM/supplier responsibility | 4 Terms, definitions and abbreviations 4.1 Terms 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.architecture relevant; Needs Customer Clarification; linked open point; Unknown estimation impact; blocks SSR derivation | Needs Customer Clarification |
| REQ_UDS-0051 | 77 | High risk due to unclear OEM/supplier responsibility | Internal Page 26 (90) Diagnostics Service Diag Safe state check Application Boot loader TransferData (0x36) M - RequestFileTransfer (0x38) M - C1 = Mandatory except for going to default session C2 = Based on recommendation from Safety Team C3 = Needs to be defined at each individual routines The server implementation shall comply with the following state diagram and the following state transition descriptions (P1 and P2 flags should be seen as implementation hints).security relevant; architecture relevant; Needs Customer Clarification; linked open point; High estimation impact | Needs Customer Clarification |
| REQ_UDS-0063 | 77 | High risk due to unclear OEM/supplier responsibility | ECU shall execute the reset only after sending a positive response to the ECU reset service REQ_UDS 0064 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.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ_UDS-0068 | 77 | High risk due to unclear OEM/supplier responsibility | Internal Page 34 (90) 5.5.2.1 Request REQ_UDS 0244 5.5.2.1.1 Request parameter resetType - 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 REQ_UDS 0069 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.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ_UDS-0071 | 77 | High risk due to unclear OEM/supplier responsibility | The implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that every server task is finished prior sending a positive response.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ_UDS-0076 | 77 | High risk due to unclear OEM/supplier responsibility | INFO_UDS 0011 This requirement mitigates DOS (Denial Of Service) attacks - 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 REQ_UDS 0077 Safety conditions are project specific and shall be checked before accepting a request to disable communication.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ_UDS-0128 | 77 | High risk due to unclear OEM/supplier responsibility | 5.5.17.3 Negative response - Negative response shall be as per CVS32 5.5.17.3.1 Supported negative response codes REQ_UDS 0129 Negative response format shall be as per ISO 14229-1 5.5.18 Authentication (0x29) service REQ_UDS 0130 Authentication (0x29) service shall be used for authentication of client and server.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ-AUTO-00733 | 77 | High risk due to unclear OEM/supplier responsibility | 5.6.4 Routine 0xFF01 – CheckProgrammingDependencies (check the flash programming) INFO_UDS 0029 This RoutineIdentifier value allows the client to start a consistency check of the server and should be able to execute independent from programming sequence.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ_UDS-0187 | 77 | High risk due to unclear OEM/supplier responsibility | The authenticity and integrity information shall be supplied to the server before the software is updated.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ_UDS-0212 | 77 | High risk due to unclear OEM/supplier responsibility | 5.7.3.2 First occurrence - 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 INFO_UDS 0036 The total vehicle distance at occurrence is used in DTCExtDataRecords, see section 5.5.10.2.8.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
| REQ_UDS-0223 | 77 | High risk due to unclear OEM/supplier responsibility | 5.9 Performance requirements on CAN - The server shall be available for complete diagnostic communication within two seconds after a power on.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Partially Accept |
Customer Clarifications / Open Points
Total Open Points5document-linked
P10priority
P20priority
Blocking Conceptyesyes/no
Blocking Estimationyesyes/no
Blocking SSRyesyes/no
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 |
Requirements From This PDF
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| ID | Requirement / Proposal | Supplier Position | Review | Security Capability | Feature / Interface | SSR | Open Point | Source |
|---|---|---|---|---|---|---|---|---|
| REQ-AUTO-00634 | Internal Page 52 (90) 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.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. | Needs Customer Clarification | Reviewed Internally | None | Hardware platform support None | None | OP-001 | 5.5.10 ReadDTCInformation (0x19) service page 52 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 52 |
| REQ-AUTO-00488 | 4 Terms, definitions and abbreviations 4.1 Terms 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.Proposal: Needs customer clarification. The requirement implies customer-owned infrastructure, approval, or a responsibility split that is not yet available. | Needs Customer Clarification | Reviewed Internally | None | System behavior None | None | OP-011 | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ_UDS-0051 | Internal Page 26 (90) Diagnostics Service Diag Safe state check Application Boot loader TransferData (0x36) M - RequestFileTransfer (0x38) M - C1 = Mandatory except for going to default session C2 = Based on recommendation from Safety Team C3 = Needs to be defined at each individual routines The server implementation shall comply with the following state diagram and the following state transition descriptions (P1 and P2 flags should be seen as implementation hints).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. | Needs Customer Clarification | Reviewed Internally | None | Application software behavior; System behavior; Secure software update and flash readiness None | None | OP-002 | 5.3 Diagnostic sessions requirements page 26 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 26 |
| REQ_UDS-0063 | ECU shall execute the reset only after sending a positive response to the ECU reset service REQ_UDS 0064 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.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. | Partially Accept | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | OP-002 | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ_UDS-0068 | Internal Page 34 (90) 5.5.2.1 Request REQ_UDS 0244 5.5.2.1.1 Request parameter resetType - 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 REQ_UDS 0069 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.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. | Partially Accept | Proposal Ready | Key management | Key management None | SSR-KEY-001 | OP-002 | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ_UDS-0071 | The implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that every server task is finished prior sending a positive response.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ_UDS-0076 | INFO_UDS 0011 This requirement mitigates DOS (Denial Of Service) attacks - 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 REQ_UDS 0077 Safety conditions are project specific and shall be checked before accepting a request to disable communication.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. | Partially Accept | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | OP-002 | 5.5.3 CommunicationControl (0x28) service page 35 Source detailsDocument section 5.5.3 CommunicationControl (0x28) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.3 CommunicationControl (0x28) service Page reference page 35 |
| REQ_UDS-0128 | 5.5.17.3 Negative response - Negative response shall be as per CVS32 5.5.17.3.1 Supported negative response codes REQ_UDS 0129 Negative response format shall be as per ISO 14229-1 5.5.18 Authentication (0x29) service REQ_UDS 0130 Authentication (0x29) service shall be used for authentication of client and server.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-RBAC-004 | OP-002 | 5.5.18 Authentication (0x29) service page 63 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 63 |
| REQ-AUTO-00733 | 5.6.4 Routine 0xFF01 – CheckProgrammingDependencies (check the flash programming) INFO_UDS 0029 This RoutineIdentifier value allows the client to start a consistency check of the server and should be able to execute independent from programming sequence.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. | Partially Accept | Proposal Ready | None | Backend and IT integration; Secure software update and flash readiness None | SSR-UPD-005 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ_UDS-0187 | The authenticity and integrity information shall be supplied to the server before the software is updated.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DAI-003 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0212 | 5.7.3.2 First occurrence - 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 INFO_UDS 0036 The total vehicle distance at occurrence is used in DTCExtDataRecords, see section 5.5.10.2.8.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. | Partially Accept | Proposal Ready | None | System behavior None | SSR-DIAG-001 | OP-002 | 5.7.4 Vehicle distance at occurrence page 82 Source detailsDocument section 5.7.4 Vehicle distance at occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.4 Vehicle distance at occurrence Page reference page 82 |
| REQ_UDS-0223 | 5.9 Performance requirements on CAN - The server shall be available for complete diagnostic communication within two seconds after a power on.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. | Partially Accept | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | OP-002 | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0001 | Internal Page 8 (90) 5 Requirements 5.1 General Requirements - The implementation of the client and the server shall be compliant with ISO 14229-1 with the clarifications, extensions and exceptions stated in this specification.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | OP-002 | 5.2.1 Used data identifier in order to identify an ECU page 8 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 8 |
| REQ_UDS-0047 | The server shall implement support for RBAC (Role Based Access Control) based on CVS151.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-RBAC-003 | OP-002 | 5.3 Diagnostic sessions requirements page 25 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 25 |
| REQ_UDS-0338 | Internal Page 27 (90) Figure 2 -State Diagram - The session transitions stated below shall be possible to request both physically or functionally addressed to the server, otherwise the applicable addressing method is stated for the explicit transition.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | OP-002 | 5.3 Diagnostic sessions requirements page 27 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 27 |
| REQ-AUTO-00561 | 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.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. | Partially Accept | Proposal Ready | None | Backend and IT integration; Secure software update and flash readiness None | SSR-UPD-005 | OP-004 | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ_UDS-0060 | 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.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. | Partially Accept | Proposal Ready | None | Backend and IT integration; Secure software update and flash readiness None | SSR-UPD-005 | OP-002 | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ_UDS-0065 | The server shall be available for ECU identification within one second after sending positive response message to an ECUReset request.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. | Partially Accept | Proposal Ready | None | Hardware platform support None | SSR-DIAG-006 | OP-002 | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ_UDS-0067 | 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.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. | Partially Accept | Proposal Ready | None | Backend and IT integration OEM/Customer Review Interface | SSR-DIAG-003 | OP-002 | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ-AUTO-00578 | INFO_UDS 0010 The server shall send an ECUReset positive response message after the server tasks above are finished but before the server performs the actual resetType.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | OP-002 | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ_UDS-0075 | 5.5.3 CommunicationControl (0x28) service - Servers involved in engine start shall not process CommunicationControl service requests until 2 seconds after terminal 15 goes active.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.5.3 CommunicationControl (0x28) service page 35 Source detailsDocument section 5.5.3 CommunicationControl (0x28) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.3 CommunicationControl (0x28) service Page reference page 35 |
| REQ_UDS-0250 | 5.5.4.3 Positive response - 5.5.4.4 Negative response REQ_UDS 0251 5.5.5 ControlDTCSetting (0x85) service REQ_UDS 0343 Servers shall reject a ControlDTCSetting service request (DTC setting type = off) with NRC 0x22 (conditionsNotCorrect) if programming preconditions are not satisfied.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. | Partially Accept | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | OP-002 | 5.5.5 ControlDTCSetting (0x85) service page 37 Source detailsDocument section 5.5.5 ControlDTCSetting (0x85) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.5 ControlDTCSetting (0x85) service Page reference page 37 |
| REQ_UDS-0082 | 5.5.6 Link Control (0x87) service - The server shall be able to switch baud rate within one second.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.5.6 Link Control (0x87) service page 38 Source detailsDocument section 5.5.6 Link Control (0x87) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.6 Link Control (0x87) service Page reference page 38 |
| REQ_UDS-0083 | The boot loader shall inherit the selected baud rate if the LinkControl service request was received when the server was executing in the application.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-BOOT-001 | OP-002 | 5.5.6 Link Control (0x87) service page 38 Source detailsDocument section 5.5.6 Link Control (0x87) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.6 Link Control (0x87) service Page reference page 38 |
| REQ_UDS-0089 | 5.5.7.2 Positive response REQ_UDS 0256 5.5.7.3 Negative response REQ_UDS 0257 5.5.8 WriteDataByIdentifier (0x2E) service - The sequence of writing data records with service 0x2E WriteDataByIdentifier shall be independent of any specific order REQ_UDS 0090 The range of a requested dataRecord value has to be checked by the server if the DID is safety relevant.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ-AUTO-00636 | Internal Page 53 (90) 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).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. | Partially Accept | Proposal Ready | None | System behavior None | SSR-DIAG-001 | OP-004 | 5.5.10 ReadDTCInformation (0x19) service page 53 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 53 |
| REQ_UDS-0108 | 5.5.12.2 Positive response REQ_UDS 0289 5.5.12.3 Negative response REQ_UDS 0290 5.5.13 Request Download Service (0x34) - 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.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.5.13 Request Download Service (0x34) page 57 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 57 |
| REQ_UDS-0109 | 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).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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.5.13 Request Download Service (0x34) page 57 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 57 |
| REQ_UDS-0111 | Internal Page 58 (90) - 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- functionNotSupported) and shall accept programming to proceed from the state at which it was executing before this non-permitted service was requested.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. | Partially Accept | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | OP-002 | 5.5.13 Request Download Service (0x34) page 58 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 58 |
| REQ_UDS-0112 | 5.5.13.1 Request - The server shall support service request formatted according to Table 62.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.5.13 Request Download Service (0x34) page 58 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 58 |
| REQ-AUTO-00691 | Preconditions to be discussed with the vehicle manufacturer shall include but not be limited to Diag safe state conditions.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. | Partially Accept | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-SYS-005 | OP-009 | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0158 | 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.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 69 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 69 |
| REQ_UDS-0160 | Internal Page 70 (90) - 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 section Software and data identification): • If boot software (any part) is erased, 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).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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 70 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 70 |
| REQ_UDS-0170 | If authenticity verification is valid the server shall initiate all necessary steps for installation of the received file.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. | Partially Accept | Proposal Ready | None | Backend and IT integration; Security evidence and traceability OEM/Customer Review Interface | SSR-DAI-004 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 74 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 74 |
| REQ_UDS-0171 | The server shall send a response to RoutineIdentifier 0x2401 Software Installation without any further inputs from the client.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 74 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 74 |
| REQ_UDS-0172 | 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).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. | Partially Accept | Proposal Ready | None | Backend and IT integration; Security evidence and traceability OEM/Customer Review Interface | SSR-DAI-004 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 74 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 74 |
| REQ_UDS-0183 | Internal Page 77 (90) - The server shall check whether or not the individual modules are complete and compatible with one another.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0185 | The consistency check shall be carried out solely by the server.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0186 | The server shall verify the authenticity and integrity of the software as a part of the consistency check.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. | Partially Accept | Proposal Ready | None | Application software behavior None | SSR-DAI-003 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0188 | The authenticity and integrity check shall be carried out solely by the server.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DAI-004 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0190 | 5.6.4.1 Request - The server shall support RoutineControl (CheckProgrammingDependencies) service request formatted according to Table 92.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. | Partially Accept | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | OP-002 | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0194 | 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.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. | Partially Accept | Proposal Ready | None | Backend and IT integration; Secure software update and flash readiness None | SSR-UPD-005 | OP-002 | 5.6.5 Routine 0xCAFE – EMP page 79 Source detailsDocument section 5.6.5 Routine 0xCAFE – EMP Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.5 Routine 0xCAFE – EMP Page reference page 79 |
| REQ_UDS-0202 | The occurrence counter shall increment if it’s value is not at it’s maximum value already.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | OP-002 | 5.7.2 Occurrence counter OCC page 80 Source detailsDocument section 5.7.2 Occurrence counter OCC Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.2 Occurrence counter OCC Page reference page 80 |
| REQ_UDS-0225 | 5.10 Session layer performance requirements - For P2Server, the minimum value shall be 0 ms, a maximum value shall be 50 ms.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. | Partially Accept | Proposal Ready | None | System behavior None | SSR-DIAG-001 | OP-002 | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0227 | Internal Page 84 (90) - For P2*Server, the minimum value shall be 0ms, the maximum value shall be 4000ms.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. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | OP-002 | 5.10 Session layer performance requirements page 84 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 84 |
| REQ_UDS-0229 | The value for P4_Server_max shall be maximum 30 seconds.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. | Partially Accept | Proposal Ready | None | System behavior None | SSR-DIAG-001 | OP-002 | 5.10 Session layer performance requirements page 84 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 84 |
| REQ_UDS-0230 | The system supplier shall document the implemented value for P4_Server_max.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. | Partially Accept | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-DIAG-002 | OP-002 | 5.10 Session layer performance requirements page 84 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 84 |
| REQ-AUTO-00776 | for Linux based systems still running in boot, the server should indicate with DID 0xF1AD that it is running in boot.Proposal: Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. | Partially Accept | Proposal Ready | None | Backend and IT integration None | SSR-COM-003 | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ-AUTO-00496 | Internal Page 7 (90) 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 variable; minimal and maximal length is given in bytes; the termination is ZERO for binary and ‘NULL’ for ASCII 4.3 Conventions Table 3 – Conventions Implementation Description M Mandatory Mandatory data marked as ‘M’ always shall be returned.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. | Accept with Assumption | Proposal Ready | Diagnostic security | Diagnostic security; Secure software update and flash readiness; Security evidence and traceability OEM/Customer Review Interface | SSR-RBAC-001 | - | 4.3 Conventions page 7 Source detailsDocument section 4.3 Conventions Section path 4 Terms, definitions and abbreviations > 4.3 Conventions Page reference page 7 |
| REQ_UDS-0005 | 0x20 - This DID shall be stored under flash memory module in flash memory.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support; Secure software update and flash readiness None | SSR-UPD-002 | - | 5.2.1 Used data identifier in order to identify an ECU page 10 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 10 |
| REQ_UDS-0232 | 0x7E 0x20 - This DID shall be stored under dataset module stored in flash memory.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support; Secure software update and flash readiness None | SSR-UPD-002 | - | 5.2.1 Used data identifier in order to identify an ECU page 11 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 11 |
| REQ_UDS-0009 | Internal Page 12 (90) 5.2.1.5 DID 0xF187 vehicleManufacturerSparePartNumberDataIdentifier - 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 REQ_UDS 0233 This DID shall be stored under dataset module stored in flash memory.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support; Secure software update and flash readiness OEM/Customer Review Interface | SSR-UPD-002 | - | 5.2.1 Used data identifier in order to identify an ECU page 12 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 12 |
| REQ_UDS-0012 | Byte #7 Correction Byte #8 Correction Byte #9 Correction Byte #10 Correction XX.YY.ZZZZ (XX – Major version YY-Minor version ZZZZ – Extra release within XX.YY for Bug fixes, Functional updates etc) 10Bytes- A_ASCIISTR ING, min-max- length zero M : M : 0x20 REQ_UDS 0235 5.2.1.8 DID 0xF18A systemSupplierIdentifierDataIdentifier 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 REQ_UDS 0013 Table 14 – Description of DID 0xF18B ECUManufacturingDateDataIdentifier 0xF18B Name: ECUManufacturingDateDataIdentifier Byte Data #1 .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. | Accept with Assumption | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-DIAG-001 | - | 5.2.1 Used data identifier in order to identify an ECU page 13 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 13 |
| REQ_UDS-0236 | 0x20 - This DID shall be stored under flash memory module in flash memory.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support; Secure software update and flash readiness None | SSR-UPD-002 | - | 5.2.1 Used data identifier in order to identify an ECU page 15 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 15 |
| REQ_UDS-0027 | Internal Page 20 (90) 5.2.1.25 DID 0xF1A9 Lifetime ECU-runtime at software update stamp - This DID shall contain a snapshot of the mandatory lifetime ECU-runtime operational data variable captured at the first power on after a software update.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.2.1 Used data identifier in order to identify an ECU page 20 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 20 |
| REQ_UDS-0028 | 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 REQ_UDS 0029 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.2.1 Used data identifier in order to identify an ECU page 20 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 20 |
| REQ_UDS-0039 | 32-Bytes A_BYTEFIEL D M : M 0x00 – 0xFF 0x20 5.2.1.33 DID 0xF1E1 vehicleManufacturerECUBootSoftwareNumber - 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 REQ_UDS 0238 This DID shall be stored under flash memory module in flash memory.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support; Secure software update and flash readiness None | SSR-UPD-002 | - | 5.3 Diagnostic sessions requirements page 23 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 23 |
| REQ_UDS-0040 | 5.3 Diagnostic sessions requirements - A default diagnostic session shall be supported.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. | Accept with Assumption | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | - | 5.3 Diagnostic sessions requirements page 23 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 23 |
| REQ_UDS-0042 | A non-default diagnostic session referred to as “extendedDiagnosticSession” shall be supported.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. | Accept with Assumption | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | - | 5.3 Diagnostic sessions requirements page 23 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 23 |
| REQ_UDS-0043 | Diagnostic sessions not defined in this document shall be agreed with the vehicle manufacturer.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. | Accept with Assumption | Proposal Ready | Diagnostic security | Diagnostic security OEM/Customer Review Interface | SSR-RBAC-001 | - | 5.3 Diagnostic sessions requirements page 23 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 23 |
| REQ-AUTO-00540 | Internal Page 25 (90) INFO_UDS 0038 In Table 39, bootloader sessions should only be applicable to Software updateable ECUs.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-BOOT-001 | - | 5.3 Diagnostic sessions requirements page 25 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 25 |
| REQ_UDS-0050 | 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 INFO_UDS 0008 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 Diagnostics safe state shall be checked before executing the diagnostics services as per Table 40.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.3 Diagnostic sessions requirements page 25 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 25 |
| REQ_UDS-0055 | Internal Page 32 (90) 5.5 Diagnostic services requirements - The SPRMIB shall be supported for services as specified in (ISO 14229-1).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. | Accept with Assumption | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | - | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ_UDS-0057 | 5.5.1 DiagnosticSessionControl (0x10) service 5.5.1.1 Request REQ_UDS 0239 5.5.1.1.1 Request parameter diagnosticSessionType - 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ_UDS-0058 | Table 43 – Service 0x10 request parameter diagnosticSessionType description Hex (bit 6-0) Description Cvt 0x01 defaultSession M 0x02 ProgrammingSession M 0x03 extendedDiagnosticSession M REQ_UDS 0059 Following an accepted request to switch to the ProgrammingSession, the application shall make all preparations to guarantee trouble-free programming operation.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ_UDS-0241 | 5.5.1.2.1 Response parameter diagnosticSessionType - Response parameter diagnosticSessionType shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ_UDS-0070 | 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.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. | Accept with Assumption | Proposal Ready | Key management | Key management None | SSR-KEY-001 | - | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ_UDS-0072 | 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ-AUTO-00585 | INFO_UDS 0013 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.5.3 CommunicationControl (0x28) service page 36 Source detailsDocument section 5.5.3 CommunicationControl (0x28) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.3 CommunicationControl (0x28) service Page reference page 36 |
| REQ_UDS-0344 | 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).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. | Accept with Assumption | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | - | 5.5.5 ControlDTCSetting (0x85) service page 37 Source detailsDocument section 5.5.5 ControlDTCSetting (0x85) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.5 ControlDTCSetting (0x85) service Page reference page 37 |
| REQ_UDS-0092 | 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).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. | Accept with Assumption | Proposal Ready | Key management | Key management None | SSR-KEY-001 | - | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ_UDS-0260 | Internal Page 41 (90) 5.5.8.3 Negative response - 5.5.9 ClearDiagnosticInformation (0x14) service 5.5.9.1 Request REQ_UDS 0261 5.5.9.1.1 Request parameter groupOfDTC REQ_UDS 0262 groupOfDTC parameter definition shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.10 ReadDTCInformation (0x19) service page 41 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 41 |
| REQ_UDS-0110 | 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-SDT-001 | - | 5.5.13 Request Download Service (0x34) page 57 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 57 |
| REQ_UDS-0133 | Internal Page 64 (90) - The Authentication (0x29) service shall be implemented according to CVS31 .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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-RBAC-004 | - | 5.5.18 Authentication (0x29) service page 64 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 64 |
| REQ_UDS-0139 | Internal Page 65 (90) - For detailed error cases and the mapping to the corresponding NRCs the Authentication service implementation specification CVS31 shall be used.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.19 RequestFileTransfer (0x38) service page 65 Source detailsDocument section 5.5.19 RequestFileTransfer (0x38) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.19 RequestFileTransfer (0x38) service Page reference page 65 |
| REQ_UDS-0159 | 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.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support; Secure software update and flash readiness None | SSR-BOOT-002 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 69 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 69 |
| REQ_UDS-0164 | Internal Page 71 (90) - Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported 5.6.2.2 Request parameter addressAndLengthFormatIdentifier REQ_UDS 0165 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.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-BOOT-003 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 71 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 71 |
| REQ-AUTO-00732 | 5.6.3.3 Negative response INFO_UDS 0028 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ-AUTO-00746 | 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 INFO_UDS 0030 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.6.3 Routine 0x2401 – Software Installation page 78 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 78 |
| REQ_UDS-0210 | Internal Page 82 (90) 5.7.3.1 Latest occurrence - The latest occurrence shall be updated at a change of DTC status bits 0 (testFailed) and 3 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.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.4 Vehicle distance at occurrence page 82 Source detailsDocument section 5.7.4 Vehicle distance at occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.4 Vehicle distance at occurrence Page reference page 82 |
| REQ_UDS-0224 | If diagnostic data is not available in time the ECU should respond with NRC 0x78 (requestCorrectlyReceived-ResponsePending) for maximum allowed time.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. | Accept with Assumption | Proposal Ready | Diagnostic security | Diagnostic security None | SSR-RBAC-001 | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0008 | 5.2.1.4 DID 0xF186 ActiveDiagnosticSessionDataIdentifier - 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 0x01Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 11 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 11 |
| REQ_UDS-0045 | Internal Page 24 (90) - Table 39 – Diagnostic service support Service according to ISO 14229-1 Addressin g mode Application Boot loader Def Def Extd Prg 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 C1 = Either 0x34 or 0x38 is mandatory depending on file based or memory based ECU system.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.3 Diagnostic sessions requirements page 24 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 24 |
| REQ_UDS-0107 | Internal Page 56 (90) - Table 61 – Service 0x31 request parameter RoutineIdentifier description 0x02B2 0x02B3 0x02B4 ReadStatusOfDiagnosticEventCodes ReadDiagnosticEventCodesByStatus ReadEventCodeData These routine IDs are used to handle diagnostic event codes and only mandatory when these type of data are used.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.12 RoutineControl (0x31) service page 56 Source detailsDocument section 5.5.12 RoutineControl (0x31) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.12 RoutineControl (0x31) service Page reference page 56 |
| REQ-AUTO-00491 | 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.Proposal: Needs internal review. Confirm whether this should-level requirement is in the committed baseline. | Needs Internal Review | Reviewed Internally | None | System behavior None | None | - | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ-AUTO-00497 | If valid data is not needed for the use-case and system at hand, default values should be used.Proposal: Needs internal review. Confirm whether this should-level requirement is in the committed baseline. | Needs Internal Review | Reviewed Internally | None | System behavior None | None | - | 4.3 Conventions page 7 Source detailsDocument section 4.3 Conventions Section path 4 Terms, definitions and abbreviations > 4.3 Conventions Page reference page 7 |
| REQ-AUTO-00499 | Shall be agreed between the supplier and the vehicle manufacturer.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-SYS-005 | - | 4.3 Conventions page 7 Source detailsDocument section 4.3 Conventions Section path 4 Terms, definitions and abbreviations > 4.3 Conventions Page reference page 7 |
| REQ_UDS-0002 | All deviations and extensions shall be agreed with the applicable vehicle manufacturer and shall be documented.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. | Accept with Assumption | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-DIAG-001 | - | 5.2.1 Used data identifier in order to identify an ECU page 8 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 8 |
| REQ-AUTO-00513 | Minimum length shall be 8 bytes and the assigned value shall be unique for every unit provided by one supplier per project.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-SYS-005 | - | 5.2.1 Used data identifier in order to identify an ECU page 14 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 14 |
| REQ_UDS-0237 | 0x20 - INFO_UDS 0039 The format should follow the pattern: Appl: <Diag.family> <Diag.generation> Boot: <Diag.family> <Diag.generation>_BOOTProposal: 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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.2.1 Used data identifier in order to identify an ECU page 16 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 16 |
| REQ_UDS-0044 | Of a marked service, an execution shall be implemented for the specified session as perTable 39.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.3 Diagnostic sessions requirements page 23 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 23 |
| REQ_UDS-0046 | The mapping of RoutineControl service routines to sessions shall be discussed and agreed with the vehicle manufacturer.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. | Accept with Assumption | Proposal Ready | None | Application software behavior OEM/Customer Review Interface | SSR-DIAG-004 | - | 5.3 Diagnostic sessions requirements page 25 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 25 |
| REQ_UDS-0048 | CVS31 and CVS32 requirements preconditions per service shall be defined by the RBAC Configuration file in the ECU.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-RBAC-004 | - | 5.3 Diagnostic sessions requirements page 25 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 25 |
| REQ_UDS-0052 | Internal Page 31 (90) 5.4 Data identifier requirements - Project specific DID shall be added to ranges defined as system supplier specific in ISO 14229- 1.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. | Accept with Assumption | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-DIAG-005 | - | 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) page 31 Source detailsDocument section 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Section path 5 Requirements > 5.4 Data identifier requirements > 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Page reference page 31 |
| REQ_UDS-0053 | 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.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support OEM/Customer Review Interface | SSR-DIAG-006 | - | 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) page 31 Source detailsDocument section 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Section path 5 Requirements > 5.4 Data identifier requirements > 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Page reference page 31 |
| REQ_UDS-0054 | These ECUs shall implement the following DIDs according to Table 42.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) page 31 Source detailsDocument section 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Section path 5 Requirements > 5.4 Data identifier requirements > 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) Page reference page 31 |
| REQ_UDS-0056 | 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.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ_UDS-0342 | Negative response code 0x22, conditionsNotCorrect , shall be used if a service request is denied due to insufficient rights according to the RBACC check.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-RBAC-004 | - | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ-AUTO-00559 | The application shall respond with NRC 0x22 (conditionsNotCorrect) if communication has not been switched off.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
| REQ_UDS-0061 | Internal Page 33 (90) 5.5.1.2 Positive response REQ_UDS 0240 - Positive response shall be sent before the actual switch in case switching to Programming session.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ_UDS-0242 | 5.5.1.2.2 Response parameter sessionParameterRecord - Response parameter sessionParameterRecord shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ_UDS-0062 | 5.5.1.3 Negative response REQ_UDS 0243 5.5.2 ECUReset (0x11) service - An ECUReset shall not be executed if the vehicle safety can be compromised.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ_UDS-0066 | After ECU reset, ECU shall be restarted and re-initialized within 2sec.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support None | SSR-DIAG-006 | - | 5.5.2 ECUReset (0x11) service page 33 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 33 |
| REQ-AUTO-00574 | The implementation of hardReset shall first ensure that data corruption will not occur.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ_UDS-0245 | Internal Page 35 (90) 5.5.2.2.1 Response parameter resetType - Response parameter resetType shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.3 CommunicationControl (0x28) service page 35 Source detailsDocument section 5.5.3 CommunicationControl (0x28) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.3 CommunicationControl (0x28) service Page reference page 35 |
| REQ_UDS-0081 | Internal Page 37 (90) 5.5.4 TesterPresent (0x3E) service 5.5.4.1 General service requirements - If the parameter suppressPosRespMsgIndicationBit = true in a functionally addressed request message, the service request shall not influence any ongoing physically addressed service request/response.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.5 ControlDTCSetting (0x85) service page 37 Source detailsDocument section 5.5.5 ControlDTCSetting (0x85) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.5 ControlDTCSetting (0x85) service Page reference page 37 |
| REQ_UDS-0249 | 5.5.4.2 Request - Request format and parameter shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.5 ControlDTCSetting (0x85) service page 37 Source detailsDocument section 5.5.5 ControlDTCSetting (0x85) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.5 ControlDTCSetting (0x85) service Page reference page 37 |
| REQ_UDS-0084 | Positive response shall be sent before the actual switch of the baud-rate takes place.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.5.6 Link Control (0x87) service page 38 Source detailsDocument section 5.5.6 Link Control (0x87) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.6 Link Control (0x87) service Page reference page 38 |
| REQ_UDS-0085 | Internal Page 39 (90) 5.5.6.1 Request 5.5.6.2 Request parameter linkControlType - 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 REQ_UDS 0086 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.7 ReadDataByIdentifier (0x22) service page 39 Source detailsDocument section 5.5.7 ReadDataByIdentifier (0x22) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.7 ReadDataByIdentifier (0x22) service Page reference page 39 |
| REQ_UDS-0087 | 5.5.6.3 Positive response REQ_UDS 0252 5.5.6.4 Negative Response REQ_UDS 0253 5.5.7 ReadDataByIdentifier (0x22) service 5.5.7.1 Request REQ_UDS 0254 If ECU supports request containing more than one data identifier it shall be documented (like in CDD, ODX etc).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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.7 ReadDataByIdentifier (0x22) service page 39 Source detailsDocument section 5.5.7 ReadDataByIdentifier (0x22) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.7 ReadDataByIdentifier (0x22) service Page reference page 39 |
| REQ_UDS-0255 | 5.5.7.1.1 Request parameter dataIdentifier - DataIdentifier parameter definition shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.7 ReadDataByIdentifier (0x22) service page 39 Source detailsDocument section 5.5.7 ReadDataByIdentifier (0x22) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.7 ReadDataByIdentifier (0x22) service Page reference page 39 |
| REQ_UDS-0088 | Internal Page 40 (90) - The data identifier ranges specified in Table 41 shall be followed.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ_UDS-0091 | 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.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support None | SSR-DIAG-006 | - | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ-AUTO-00608 | If this action is necessary then it shall be integrated implicitly into ECU Reset (0x11) Service subfunction 0x02.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-SYS-008 | - | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ_UDS-0258 | 5.5.8.1 Request - Request format and parameter shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ_UDS-0266 | 5.5.10.1.2 Request parameter reportNumberOfDTCByStatusMask - ReportNumberOfDTCByStatusMask parameter format shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 42 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 42 |
| REQ_UDS-0267 | 5.5.10.1.3 Request parameter DTCStatusMask - DTCStatusMask parameter format shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 42 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 42 |
| REQ_UDS-0096 | 5.5.10.1.4 Request parameter DTCMaskRecord - 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 REQ_UDS 0097 It shall be mandatory to utilize SPNs & FMIs according to SAE J1939.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.10 ReadDTCInformation (0x19) service page 42 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 42 |
| REQ_UDS-0268 | 5.5.10.1.5 Request parameter DTCSnapshotRecordNumber - DTCSnapshotRecordNumber parameter format shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 42 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 42 |
| REQ_UDS-0098 | Internal Page 43 (90) 5.5.10.1.6 Request parameter DTCExtDataRecordNumber - 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 REQ_UDS 0269 Response parameter FunctionalGroupIdentifier shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.10 ReadDTCInformation (0x19) service page 43 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 43 |
| REQ_UDS-0270 | 5.5.10.1.8 Request parameter DTCSeverityMaskRecord - DTCSeverityMaskRecord parameter format shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 43 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 43 |
| REQ_UDS-0271 | 5.5.10.1.9 Request parameter DTCSeverityMask - DTCSeverityMask parameter format shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 43 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 43 |
| REQ_UDS-0272 | 5.5.10.2 Positive response - 5.5.10.2.1 Response parameter DTCStatusAvailabilityMask REQ_UDS 0273 Response parameter DTCStatusAvailabilityMask shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 43 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 43 |
| REQ_UDS-0274 | 5.5.10.2.2 Response parameter DTCFormatIdentifier - Response parameter DTCFormatIdentifier shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 43 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 43 |
| REQ_UDS-0275 | 5.5.10.2.3 Response parameter DTCCount - Response parameter DTCCount shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 43 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 43 |
| REQ_UDS-0276 | Internal Page 44 (90) 5.5.10.2.4 Response parameter DTCAndStatusRecord - Response parameter DTCAndStatusRecord shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 44 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 44 |
| REQ_UDS-0277 | 5.5.10.2.5 Response parameter DTCRecord - Response parameter DTCRecord shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 44 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 44 |
| REQ-AUTO-00626 | 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.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-SYS-008 | - | 5.5.10 ReadDTCInformation (0x19) service page 44 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 44 |
| REQ_UDS-0099 | 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.10 ReadDTCInformation (0x19) service page 44 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 44 |
| REQ-AUTO-00630 | 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.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | External interfaces External Interfaces | SSR-DIAG-007 | - | 5.5.10 ReadDTCInformation (0x19) service page 50 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 50 |
| REQ_UDS-0304 | DTCSnapshotRecordNumber#1 & DTCSnapshotRecordNumber#2 shall correspond to first time DTC happened and latest time DTC happened correspondingly.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.5.10 ReadDTCInformation (0x19) service page 50 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 50 |
| REQ_UDS-0100 | Internal Page 51 (90) 5.5.10.2.7 Response parameter DTCExtDataRecordNumber - 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 REQ_UDS 0101 The extended data sub-function (0x06) shall have the positive response message data and format specified in Table 68.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.10 ReadDTCInformation (0x19) service page 51 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 51 |
| REQ-AUTO-00633 | 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.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.10 ReadDTCInformation (0x19) service page 51 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 51 |
| REQ_UDS-0278 | 5.5.10.2.9 Response parameter FunctionalGroupIdentifier - Response parameter FunctionalGroupIdentifier shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 53 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 53 |
| REQ_UDS-0279 | 5.5.10.2.10 Response parameter DTCSeverityAvailabilityMask - Response parameter DTCSeverityAvailabilityMask shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 53 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 53 |
| REQ_UDS-0280 | Internal Page 54 (90) 5.5.10.2.11 Response parameter DTCAndSeverityRecord - Response parameter DTCAndSeverityRecord shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.11 InputOutputControlByIdentifier (0x2F) service page 54 Source detailsDocument section 5.5.11 InputOutputControlByIdentifier (0x2F) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.11 InputOutputControlByIdentifier (0x2F) service Page reference page 54 |
| REQ_UDS-0281 | 5.5.10.3 Negative response - 5.5.10.3.1 Supported negative response codes REQ_UDS 0282 Negative response codes shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.11 InputOutputControlByIdentifier (0x2F) service page 54 Source detailsDocument section 5.5.11 InputOutputControlByIdentifier (0x2F) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.11 InputOutputControlByIdentifier (0x2F) service Page reference page 54 |
| REQ_UDS-0102 | 5.5.11 InputOutputControlByIdentifier (0x2F) service 5.5.11.1 Request REQ_UDS 0283 5.5.11.1.1 Request parameter dataIdentifier - The data identifier ranges specified in ISO 14229-1 shall be followed.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.11 InputOutputControlByIdentifier (0x2F) service page 54 Source detailsDocument section 5.5.11 InputOutputControlByIdentifier (0x2F) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.11 InputOutputControlByIdentifier (0x2F) service Page reference page 54 |
| REQ_UDS-0284 | M 5.5.11.1.4 Request parameter controlEnableMaskRecord - ControlEnableMaskRecord parameter format shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.12 RoutineControl (0x31) service page 55 Source detailsDocument section 5.5.12 RoutineControl (0x31) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.12 RoutineControl (0x31) service Page reference page 55 |
| REQ_UDS-0106 | 5.5.12.1.2 Request parameter RoutineIdentifier - Request parameter routineIdentifier shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.12 RoutineControl (0x31) service page 55 Source detailsDocument section 5.5.12 RoutineControl (0x31) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.12 RoutineControl (0x31) service Page reference page 55 |
| REQ-AUTO-00648 | The routine IDs as listed in Table 61 are reserved by TRATON and shall not be used by the system supplier.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. | Accept with Assumption | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-SYS-005 | - | 5.5.12 RoutineControl (0x31) service page 55 Source detailsDocument section 5.5.12 RoutineControl (0x31) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.12 RoutineControl (0x31) service Page reference page 55 |
| REQ_UDS-0288 | 5.5.12.1.3 Request parameter RoutineControlOptionRecord - Request parameter routineControlOptionRecord shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.13 Request Download Service (0x34) page 57 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 57 |
| REQ_UDS-0119 | Internal Page 61 (90) 5.5.14.1.2 Request parameter addressAndLengthFormatIdentifier - 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 REQ_UDS 0291 MemoryAddress parameter definition shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.15 TransferData (0x36) service page 61 Source detailsDocument section 5.5.15 TransferData (0x36) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.15 TransferData (0x36) service Page reference page 61 |
| REQ_UDS-0292 | 5.5.14.1.4 Request parameter memorySize - MemorySize parameter definition shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.15 TransferData (0x36) service page 61 Source detailsDocument section 5.5.15 TransferData (0x36) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.15 TransferData (0x36) service Page reference page 61 |
| REQ_UDS-0294 | M 0 5.5.14.3 Negative response - Refer to ISO 14229-1 for negative response format and codes shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.15 TransferData (0x36) service page 61 Source detailsDocument section 5.5.15 TransferData (0x36) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.15 TransferData (0x36) service Page reference page 61 |
| REQ_UDS-0296 | Internal Page 62 (90) 5.5.15.1.1 Request parameter blockSequenceCounter - MemoryAddress parameter definition shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.16 RequestTransferExit (0x37) service page 62 Source detailsDocument section 5.5.16 RequestTransferExit (0x37) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.16 RequestTransferExit (0x37) service Page reference page 62 |
| REQ_UDS-0297 | 5.5.15.1.2 Request parameter transferRequestParameterRecord - MemorySize parameter definition shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.16 RequestTransferExit (0x37) service page 62 Source detailsDocument section 5.5.16 RequestTransferExit (0x37) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.16 RequestTransferExit (0x37) service Page reference page 62 |
| REQ_UDS-0121 | 5.5.15.2 Positive response REQ_UDS 0298 5.5.15.3 Negative response REQ_UDS 0299 5.5.15.3.1 Supported negative response codes REQ_UDS 0300 5.5.16 RequestTransferExit (0x37) service 5.5.16.1 Request Table 71 – Service 0x37 request parameter description 1 RequestTransferExit Request SID M 5.5.16.1.1 Request parameter transferRequestParameterRecord REQ_UDS 0122 The transferRequestParameterRecord shall not be supported.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.16 RequestTransferExit (0x37) service page 62 Source detailsDocument section 5.5.16 RequestTransferExit (0x37) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.16 RequestTransferExit (0x37) service Page reference page 62 |
| REQ_UDS-0124 | Internal Page 63 (90) 5.5.16.2.1 Response parameter transferResponseParameterRecord - The transferRequestParameterRecord shall not be supported.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.5.18 Authentication (0x29) service page 63 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 63 |
| REQ_UDS-0125 | 5.5.16.3 Negative response REQ_UDS 0301 5.5.16.3.1 Supported negative response codes REQ_UDS 0302 5.5.17 SecuredDataTransmission (0x84) service This service shall be used when transmitting data in a secured mode, see CVS32.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.18 Authentication (0x29) service page 63 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 63 |
| REQ_UDS-0126 | 5.5.17.1 Request REQ_UDS 0303 5.5.17.1.1 Request message data-parameter definition - Data parameter definition shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | External interfaces External Interfaces | SSR-DIAG-007 | - | 5.5.18 Authentication (0x29) service page 63 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 63 |
| REQ_UDS-0127 | 5.5.17.2 Positive response - Positive response shall be as per CVS32.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.5.18 Authentication (0x29) service page 63 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 63 |
| REQ_UDS-0137 | 5.5.18.4 Negative response - 5.5.18.4.1 Supported negative response codes REQ_UDS 0138 Supported negative response codes shall be as per ISO 14229-1, especially the NRC range 0x50 – 0x5D according to Table 73.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.5.18 Authentication (0x29) service page 64 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 64 |
| REQ_UDS-0140 | 5.5.19 RequestFileTransfer (0x38) service 5.5.19.1 Request - 5.5.19.2 Request Parameter modeOfOperation REQ_UDS 0141 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.5.19 RequestFileTransfer (0x38) service page 65 Source detailsDocument section 5.5.19 RequestFileTransfer (0x38) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.19 RequestFileTransfer (0x38) service Page reference page 65 |
| REQ_UDS-0142 | Internal Page 66 (90) Byte value Description Cvt 0x07 – 0xFF ISO Reserved M 5.5.19.3 Request parameter subFunction - Refer to ISO 14229-1 for parameter sub-function format shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 66 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 66 |
| REQ_UDS-0143 | 5.5.19.4 Request Parameter dataFormatIdentifier - 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 REQ_UDS 0144 5.5.19.6 Negative response REQ_UDS 0145 5.5.19.7 Supported negative response codes REQ_UDS 0146 Supported negative response codes shall be as per ISO 14229-1.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. | Accept with Assumption | Proposal Ready | None | Application software behavior OEM/Customer Review Interface | SSR-DIAG-004 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 66 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 66 |
| REQ_UDS-0147 | Internal Page 67 (90) - The programming preconditions shall be agreed with the vehicle manufacturer.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness OEM/Customer Review Interface | SSR-UPD-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0148 | The decision on conditions of the programming precondition shall be based on minimum two independent sources of information.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0149 | If information is not available for checking a programming precondition the programming precondition shall be considered fulfilled.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0150 | This routine shall be supported in Extended session of both Application and Boot.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0151 | 5.6.1.1 Request 5.6.1.2 Request parameter RoutineControlOptionRecord - Request parameter RoutineControlOptionRecord shall not be supported.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0152 | Request parameter routineControlType with value 0x03 (requestRoutineResults) shall not be supported.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0153 | 5.6.1.3 Positive response - 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 REQ_UDS 0154 Each routineStatus byte shall represent one not satisfied precondition according to Table 18 (see definition of “Satisfied programming precondition”).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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ_UDS-0155 | Internal Page 68 (90) - Which ones of the programming precondition codes in Table 18 that need to be supported shall be discussed and agreed with the vehicle manufacturer.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness OEM/Customer Review Interface | SSR-UPD-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 68 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 68 |
| REQ_UDS-0156 | If all preconditions are satisfied, no routineStatus byte shall be reported.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 68 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 68 |
| REQ_UDS-0157 | Programming preconditions that do not map to one of the entries in Table 77 shall be discussed with the vehicle manufacturer.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness OEM/Customer Review Interface | SSR-UPD-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 68 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 68 |
| REQ-AUTO-00702 | 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 ..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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 68 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 68 |
| REQ_UDS-0161 | The erasing of memory shall not prevent the client from starting a data transfer using the TransferData (0x36) service, i.e.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-SDT-001 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 70 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 70 |
| REQ_UDS-0162 | This routine shall be supported in Programming session.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 70 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 70 |
| REQ_UDS-0166 | 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 ...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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-BOOT-001 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 71 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 71 |
| REQ_UDS-0168 | Internal Page 72 (90) - The routineResult byte values shall be as specified in Table 81.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 72 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 72 |
| REQ_UDS-0173 | This routine shall be supported in Programming session.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 74 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 74 |
| REQ_UDS-0174 | 5.6.3.1 Request - Request parameter RoutineControlOptionRecord shall not be supported.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 74 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 74 |
| REQ_UDS-0175 | Internal Page 75 (90) 5.6.3.2 Positive Response - Positive responses to RoutineControl (Software Installation) service requests shall be formatted according to Table 88 and Table 89.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.6.3 Routine 0x2401 – Software Installation page 75 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 75 |
| REQ_UDS-0176 | 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.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. | Accept with Assumption | Proposal Ready | None | System behavior; Security evidence and traceability OEM/Customer Review Interface | SSR-DAI-002 | - | 5.6.3 Routine 0x2401 – Software Installation page 75 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 75 |
| REQ_UDS-0177 | AuthenticityVerificationStatus bit 7-6 (AuthenticityStatus) shall remain as 0x0 (Software Authenticity Invalid) until the verification completes.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Security evidence and traceability OEM/Customer Review Interface | SSR-DAI-003 | - | 5.6.3 Routine 0x2401 – Software Installation page 75 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 75 |
| REQ_UDS-0178 | 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).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. | Accept with Assumption | Proposal Ready | None | System behavior; Security evidence and traceability OEM/Customer Review Interface | SSR-DAI-002 | - | 5.6.3 Routine 0x2401 – Software Installation page 75 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 75 |
| REQ_UDS-0179 | Internal Page 76 (90) 0x1: Authenticity Verification Successful 0x2: Authenticity Verification Failed 5-0 Reserved Note: Shall be kept as 0x0 SoftwareInstallationStatus shall be formatted according to Table 91.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. | Accept with Assumption | Proposal Ready | None | System behavior; Security evidence and traceability OEM/Customer Review Interface | SSR-DAI-002 | - | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ_UDS-0180 | SoftwareInstallationStatus bit 7-6 (InstallationStatus) shall remain as 0x0 (Installation On-going) until the installation completes.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ_UDS-0181 | 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.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ_UDS-0182 | TimeRemaningEstimative shall inform the time estimative to complete the installation of the file.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ_UDS-0184 | The method used to check compatibility/consistency shall be determined by the supplier in consultation with the vehicle manufacturer.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. | Accept with Assumption | Proposal Ready | None | System behavior OEM/Customer Review Interface | SSR-DIAG-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0189 | This routine shall be supported in Programming session.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0191 | 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.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ_UDS-0192 | Internal Page 78 (90) 5.6.4.2 Positive response - Positive responses to RoutineControl (CheckProgrammingDependencies) service requests shall be formatted according to Table 93.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. | Accept with Assumption | Proposal Ready | None | Application software behavior; Secure software update and flash readiness None | SSR-UPD-003 | - | 5.6.3 Routine 0x2401 – Software Installation page 78 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 78 |
| REQ_UDS-0193 | 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.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. | Accept with Assumption | Proposal Ready | None | System behavior; Secure software update and flash readiness None | SSR-UPD-001 | - | 5.6.3 Routine 0x2401 – Software Installation page 78 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 78 |
| REQ_UDS-0195 | This routine shall be supported in all sessions of Application and Boot.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. | Accept with Assumption | Proposal Ready | None | Application software behavior None | SSR-DIAG-004 | - | 5.6.5 Routine 0xCAFE – EMP page 79 Source detailsDocument section 5.6.5 Routine 0xCAFE – EMP Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.5 Routine 0xCAFE – EMP Page reference page 79 |
| REQ_UDS-0196 | Internal Page 80 (90) 5.7 Fault memory requirements 5.7.1 DTC status bits - 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 REQ_UDS 0197 DTC status bits shall not make use of any vehicle manufacturer specific reset condition (e.g.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. | Accept with Assumption | Proposal Ready | None | Hardware platform support OEM/Customer Review Interface | SSR-DIAG-006 | - | 5.7.2 Occurrence counter OCC page 80 Source detailsDocument section 5.7.2 Occurrence counter OCC Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.2 Occurrence counter OCC Page reference page 80 |
| REQ_UDS-0198 | The occurrence counter minimum value shall be zero (0).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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.2 Occurrence counter OCC page 80 Source detailsDocument section 5.7.2 Occurrence counter OCC Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.2 Occurrence counter OCC Page reference page 80 |
| REQ_UDS-0199 | The occurrence counter maximum value shall be 126.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.2 Occurrence counter OCC page 80 Source detailsDocument section 5.7.2 Occurrence counter OCC Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.2 Occurrence counter OCC Page reference page 80 |
| REQ_UDS-0200 | The occurrence counter default value shall be zero (0).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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.2 Occurrence counter OCC page 80 Source detailsDocument section 5.7.2 Occurrence counter OCC Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.2 Occurrence counter OCC Page reference page 80 |
| REQ_UDS-0201 | The occurrence counter shall increment by one (1) only.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.2 Occurrence counter OCC page 80 Source detailsDocument section 5.7.2 Occurrence counter OCC Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.2 Occurrence counter OCC Page reference page 80 |
| REQ_UDS-0203 | The occurrence counter shall increment at a change of DTC status bits 0 testFailed and 3 confirmedDTC both from 0 to 1.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.2 Occurrence counter OCC page 80 Source detailsDocument section 5.7.2 Occurrence counter OCC Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.2 Occurrence counter OCC Page reference page 80 |
| REQ_UDS-0204 | Internal Page 81 (90) - The occurrence counter shall increment at a change of DTC status bit 0 testFailed from 0 to 1, if bit 3 confirmedDTC is 1 already.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.3 Timestamp of occurrence page 81 Source detailsDocument section 5.7.3 Timestamp of occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.3 Timestamp of occurrence Page reference page 81 |
| REQ_UDS-0205 | 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.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.3 Timestamp of occurrence page 81 Source detailsDocument section 5.7.3 Timestamp of occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.3 Timestamp of occurrence Page reference page 81 |
| REQ_UDS-0206 | The occurrence counter value 127 shall be defined as "errors with the counter".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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.3 Timestamp of occurrence page 81 Source detailsDocument section 5.7.3 Timestamp of occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.3 Timestamp of occurrence Page reference page 81 |
| REQ_UDS-0207 | The timestamp default value shall be a 0xFF in each data.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.3 Timestamp of occurrence page 81 Source detailsDocument section 5.7.3 Timestamp of occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.3 Timestamp of occurrence Page reference page 81 |
| REQ_UDS-0211 | If occurrence counter is set to 1, the timestamp of the latest occurrence shall be set to 0xFF.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.4 Vehicle distance at occurrence page 82 Source detailsDocument section 5.7.4 Vehicle distance at occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.4 Vehicle distance at occurrence Page reference page 82 |
| REQ_UDS-0213 | The vehicle distance shall be represented by a four byte integer, big endian, with five meter per bit (5m/bit).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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.4 Vehicle distance at occurrence page 82 Source detailsDocument section 5.7.4 Vehicle distance at occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.4 Vehicle distance at occurrence Page reference page 82 |
| REQ_UDS-0214 | If all sources of vehicle distance information present no current data, the distance information shall be set to 0xFF at all bytes.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.7.4 Vehicle distance at occurrence page 82 Source detailsDocument section 5.7.4 Vehicle distance at occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.4 Vehicle distance at occurrence Page reference page 82 |
| REQ_UDS-0219 | If all sources of operational hours information present no current data, the operational hours information shall be set to 0xFF at all bytes.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0226 | For P2Client, a value of 150 ms shall be used.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0228 | For P2*Client, the value estimation given in ISO 14229-2 shall be used.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. | Accept with Assumption | Proposal Ready | None | System behavior None | SSR-DIAG-005 | - | 5.10 Session layer performance requirements page 84 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 84 |
| REQ_UDS-0003 | Modified requirements - Added semantic Identifier DIDs, changed the NodeUID DID to INTERNAL REQ_UDS 0034: Change in the length of NodeUID(0xF1AF) INFO_UDS 0040: Change in the retrieval method for NodeUID(0xF1AF) REQ_UDS 0036: 0xF1B9 RBACCIdentifierNumber is changed to Mandatory REQ_UDS 0037: 0xF1BA RBACCStructureVersion,bit-length changed REQ_UDS 0045: Changes for service (0x84) and (0x31) REQ_UDS 0048: Updated the document references REQ_UDS 0107: 0XCAFE and 0xFF02 are updated to Mandatory REQ_UDS 0180: Modifcations on the bit values and new bit added REQ_UDS 0193: 0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infos: REQ_UDS 0045: (0x86) service removed REQ_UDS 0053, REQ_UDS 0054: Removed the reserved DID ranges and 0xF1C1 REQ_UDS 0024: 0xF19E ODXFileDataIdentifier is removed 2024-10 First issueProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure communication and freshness protection None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 8 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 8 |
| REQ_UDS-0004 | Internal Page 10 (90) 5.2.1.1 DID 0xF180 bootSoftwareIdentificationDataIdentifier - Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier 0xF180 Name : bootSoftwareIdentificationDataIdentifier Byte Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x01 #2 : #14 Boot software identifier #1: : M : M 0x7E .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 10 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 10 |
| REQ_UDS-0006 | 5.2.1.2 DID 0xF181 applicationSoftwareIdentificationDataIdentifier - 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 0x20Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 10 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 10 |
| REQ_UDS-0007 | Internal Page 11 (90) REQ_UDS 0231 5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifier - 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 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 11 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 11 |
| REQ_UDS-0010 | 5.2.1.6 DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier - Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier 0xF188 Name: vehicleManufacturerECUSoftwareNumberDataIdentifier Byte Data #1 : #13 Vehicle manufacturer ECU (server) software number : M : M : 0x20 REQ_UDS 0234 5.2.1.7 DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier REQ_UDS 0011 Table 12 – Description of DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier 0xF189 Name: vehicleManufacturerECUSoftwareVersionNumberDataIdentifier Byte DataProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 12 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 12 |
| REQ_UDS-0014 | Internal Page 14 (90) byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 0x20, 0x30 – 0x39 5.2.1.10 DID 0xF18C ECUSerialNumberDataIdentifier Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier 0xF18C Name: ECUSerialNumberDataIdentifier Byte Data To be specified by the supplier.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 14 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 14 |
| REQ_UDS-0015 | 5.2.1.11 DID 0xF190 VINDataIdentifier - Table 16 – Description of DID 0xF190 VINDataIdentifier 0xF190 Name: VINDataIdentifier Byte Data #1 : #17 VIN number : Byte #17 17-Bytes- M : M : 0x30 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 14 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 14 |
| REQ_UDS-0016 | 5.2.1.12 DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier - Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier 0xF191 Name: vehicleManufacturerECUHardwareNumberDataIdentifier Byte DataProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 14 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 14 |
| REQ_UDS-0017 | 5.2.1.13 DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier - 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 REQ_UDS 0018 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 REQ_UDS 0019 Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier 0xF194 Name: systemSupplierECUSoftwareNumberDataIdentifier Byte No Description Format Cvt Byte Value Data To be specified by the External SupplierProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 15 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 15 |
| REQ_UDS-0020 | Internal Page 16 (90) 5.2.1.16 DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier - 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 REQ_UDS 0021 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 REQ_UDS 0022 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 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 16 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 16 |
| REQ_UDS-0339 | Internal Page 90 (90) Annex C (informative) Change history Release date Changes 2025-12 New requirements and infos: INFO_UDS 0039: F197 structure added F198 Request and response format REQ_UDS 0340: F199 Request and response format REQ_UDS 0341: F19A Request and response format REQ_UDS 0342: NRC for RBACC check failures REQ_UDS 0343, REQ_UDS 0344, REQ_UDS 0345, REQ_UDS 0346, REQ_UDS 0347, REQ_UDS 0348, REQ_UDS 0349: Requirements, Request and response formats for the ControlDTCSetting(0x85) added.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure communication and freshness protection None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 17 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 17 |
| REQ_UDS-0340 | 5.2.1.20 DID 0xF199 SoftwareAssemblySemanticDataIdentifiers - Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s 0xF199 Name: SoftwareAssemblySemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure communication and freshness protection None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 17 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 17 |
| REQ_UDS-0341 | 5.2.1.21 DID 0xF19A HardwareSemanticDataIdentifiers - 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure communication and freshness protection None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 18 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 18 |
| REQ_UDS-0023 | Internal Page 19 (90) 5.2.1.22 DID 0xF19D ECUInstallationDateDataIdentifier - Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier 0xF19D Name: ECUInstallationDateDataIdentifier Byte Data #1 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 19 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 19 |
| REQ_UDS-0025 | #8 Format: “YYYYMMDD” byte #1 YY (most significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- RING M : M : 0x2020 20202 020 5.2.1.23 DID 0xF1A5 vehicleManufacturerECUHardwareWithoutBootNumber 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 REQ_UDS 0026 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 solutionsProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 19 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 19 |
| REQ_UDS-0030 | 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure software update and flash readiness None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 20 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 20 |
| REQ_UDS-0032 | Internal Page 21 (90) - Table 32 – Description of DID 0xF1AB Date at software update stamp 0xF1AB Name: dateAtSoftwareUpdateStamp Byte Data #1 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure software update and flash readiness None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 21 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 21 |
| REQ_UDS-0033 | 5.2.1.28 DID 0xF1AD activeECUSoftwareDataIdentifier - 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 REQ_UDS 0034 Table 34 – Description of DID 0xF1AF NodeUID 0xF1AF Name: NodeUID Byte Data #1 : #8 NodeUID 8-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 21 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 21 |
| REQ_UDS-0036 | 5.2.1.30 DID 0xF1B9 RBACCIdentifierNumber - 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 INFO_UDS 0006 Information on RBACC can be found in CVS151.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 22 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 22 |
| REQ_UDS-0037 | 5.2.1.31 DID 0xF1BA RBACCStructureVersion - 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 INFO_UDS 0007 Information on RBACC can be found in CVS151.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 22 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 22 |
| REQ_UDS-0038 | 5.2.1.32 DID 0xF1D1 RootCertificateIdentifier - Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier 0xF1D1 Name: RootCertificateIdentifier Byte DataProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.2.1 Used data identifier in order to identify an ECU page 22 Source detailsDocument section 5.2.1 Used data identifier in order to identify an ECU Section path 5 Requirements > 5.2 ECU Identification Requirements > 5.2.1 Used data identifier in order to identify an ECU Page reference page 22 |
| REQ_UDS-0041 | The default diagnostic session is referred to as “defaultSession”.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.3 Diagnostic sessions requirements page 23 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 23 |
| REQ_UDS-0049 | Diagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing certain diagnostics services.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.3 Diagnostic sessions requirements page 25 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 25 |
| REQ_UDS-0305 | INFO_UDS 0019 Description of the individual transitions as per Figure 2 -State Diagram is explained from - to REQ_UDS 0337.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.3 Diagnostic sessions requirements page 27 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 27 |
| REQ_UDS-0306 | Internal Page 28 (90) - 2.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.3 Diagnostic sessions requirements page 28 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 28 |
| REQ_UDS-0316 | Internal Page 29 (90) - 12.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.3 Diagnostic sessions requirements page 29 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 29 |
| REQ_UDS-0328 | Internal Page 30 (90) - 24.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.3 Diagnostic sessions requirements page 30 Source detailsDocument section 5.3 Diagnostic sessions requirements Section path 5 Requirements > 5.3 Diagnostic sessions requirements Page reference page 30 |
| REQ_UDS-0073 | 5.5.2.2 Positive response - Table 45 – Service 0x11 positive response parameter description 1 ECUReset Response SID M 2 resetType MProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ_UDS-0074 | 5.5.2.3 Negative response REQ_UDS 0246 5.5.2.3.1 Supported negative response codes - Table 46 – Service 0x11 negative response codes NRC Description and scenario 0x12 sub-functionNotSupported Refer to ISO 14229-1 for scenario.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.3 CommunicationControl (0x28) service page 35 Source detailsDocument section 5.5.3 CommunicationControl (0x28) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.3 CommunicationControl (0x28) service Page reference page 35 |
| REQ_UDS-0078 | 5.5.3.1 Request - 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 REQ_UDS 0079 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 REQ_UDS 0080 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 REQ_UDS 0247 5.5.3.3 Negative response REQ_UDS 0248Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.3 CommunicationControl (0x28) service page 36 Source detailsDocument section 5.5.3 CommunicationControl (0x28) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.3 CommunicationControl (0x28) service Page reference page 36 |
| REQ-AUTO-00588 | INFO_UDS 0014 A functionally addressed TesterPresent may arrive at any time during another request.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.5 ControlDTCSetting (0x85) service page 37 Source detailsDocument section 5.5.5 ControlDTCSetting (0x85) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.5 ControlDTCSetting (0x85) service Page reference page 37 |
| REQ_UDS-0345 | 5.5.5.1 Request - Refer to ISO 14229-1 for request format.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.5 ControlDTCSetting (0x85) service page 37 Source detailsDocument section 5.5.5 ControlDTCSetting (0x85) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.5 ControlDTCSetting (0x85) service Page reference page 37 |
| REQ_UDS-0346 | 5.5.5.1.1 Request parameter DTCSettingType - Refer to ISO 14229-1 for request parameter DTCSettingType.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.5 ControlDTCSetting (0x85) service page 37 Source detailsDocument section 5.5.5 ControlDTCSetting (0x85) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.5 ControlDTCSetting (0x85) service Page reference page 37 |
| REQ_UDS-0347 | Internal Page 38 (90) 5.5.5.1.2 Request parameter DTCSettingControlOptionRecord - Refer to ISO 14229-1 for request parameter DTCSettingControlOptionRecord.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.6 Link Control (0x87) service page 38 Source detailsDocument section 5.5.6 Link Control (0x87) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.6 Link Control (0x87) service Page reference page 38 |
| REQ_UDS-0348 | 5.5.5.2 Positive response - Refer to ISO 14229-1 for positive response format and parameter.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.6 Link Control (0x87) service page 38 Source detailsDocument section 5.5.6 Link Control (0x87) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.6 Link Control (0x87) service Page reference page 38 |
| REQ_UDS-0349 | 5.5.5.3 Negative response - Refer to ISO 14229-1 for negative response format and codes.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.6 Link Control (0x87) service page 38 Source detailsDocument section 5.5.6 Link Control (0x87) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.6 Link Control (0x87) service Page reference page 38 |
| REQ_UDS-0093 | Additional client requests which start copying RAM buffer data into non-volatile memory are not allowed.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ_UDS-0259 | 5.5.8.2 Positive responseProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.8 WriteDataByIdentifier (0x2E) service page 40 Source detailsDocument section 5.5.8 WriteDataByIdentifier (0x2E) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.8 WriteDataByIdentifier (0x2E) service Page reference page 40 |
| REQ_UDS-0094 | 5.5.9.2 Positive response REQ_UDS 0263 5.5.9.3 Negative response REQ_UDS 0264 5.5.10 ReadDTCInformation (0x19) service 5.5.10.1 Request REQ_UDS 0265 5.5.10.1.1 Request parameter reportType 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 UProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.10 ReadDTCInformation (0x19) service page 41 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 41 |
| REQ_UDS-0095 | Internal Page 42 (90) 0x10 reportMirrorMemoryDTCExtendedDataRecordByDTCNumber U 0x11 reportNumberOfMirrorMemoryDTCByStatusMask U 0x12 reportNumberOfEmissionsRelatedOBDDTCByStatusMask E 0x13 reportEmissionsRelatedOBDDTCByStatusMask E 0x42 reportWWHOBDDTCByMaskRecord E 0x55 reportWWHOBDDTCWithPermanentStatus E Legislated OBD relevant ECUs have to support legislated OBD standards.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.10 ReadDTCInformation (0x19) service page 42 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 42 |
| REQ-AUTO-00629 | Internal Page 49 (90) 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.10 ReadDTCInformation (0x19) service page 49 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 49 |
| REQ_UDS-0103 | 5.5.11.1.2 Request parameter controlOptionRecord - Table 58 – Service 0x2F request parameter controlOptionRecord description 1 inputOutputControlParameter M 2 ..Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.11 InputOutputControlByIdentifier (0x2F) service page 54 Source detailsDocument section 5.5.11 InputOutputControlByIdentifier (0x2F) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.11 InputOutputControlByIdentifier (0x2F) service Page reference page 54 |
| REQ_UDS-0104 | 2 + (m-1) controlState byte 1 : controlState byte m C : C 5.5.11.1.3 Request parameter inputOutputControlParameter - Table 59 – Service 0x2F request parameter inputOutputControlParameter description 0x00 returnControlToECU Refer to ISO 14229-1 for parameter description.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.11 InputOutputControlByIdentifier (0x2F) service page 54 Source detailsDocument section 5.5.11 InputOutputControlByIdentifier (0x2F) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.11 InputOutputControlByIdentifier (0x2F) service Page reference page 54 |
| REQ_UDS-0105 | 5.5.11.2 Positive response REQ_UDS 0285 5.5.11.3 Negative response REQ_UDS 0286 5.5.12 RoutineControl (0x31) service 5.5.12.1 Request REQ_UDS 0287 5.5.12.1.1 Request parameter RoutineControlType 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”.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.12 RoutineControl (0x31) service page 55 Source detailsDocument section 5.5.12 RoutineControl (0x31) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.12 RoutineControl (0x31) service Page reference page 55 |
| REQ-AUTO-00652 | INFO_UDS 0017 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.13 Request Download Service (0x34) page 57 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 57 |
| REQ_UDS-0113 | M 5.5.13.2 Request parameter dataFormatIdentifier - 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 – 0xFProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.13 Request Download Service (0x34) page 58 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 58 |
| REQ_UDS-0114 | Internal Page 59 (90) encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1 5.5.13.3 Request parameter addressAndLengthFormatIdentifier 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 REQ_UDS 0115 Table 65 – Positive response parameter description #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier M 0x20 #3..Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.13 Request Download Service (0x34) page 59 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 59 |
| REQ_UDS-0116 | #4 maxNumberOfBlockLength[] = [ byte #1 (MSB) byte #2 ] M M 0xFF 0xFF 5.5.13.5 Response parameter lengthFormatIdentifier - Table 66 – Service 0x34 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.13 Request Download Service (0x34) page 59 Source detailsDocument section 5.5.13 Request Download Service (0x34) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.13 Request Download Service (0x34) Page reference page 59 |
| REQ_UDS-0117 | Internal Page 60 (90) 5.5.14 RequestUpload (0x35) 5.5.14.1 Request - Table 67 – Service 0x35 request parameter description 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier M 4 ..Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.14 RequestUpload (0x35) page 60 Source detailsDocument section 5.5.14 RequestUpload (0x35) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.14 RequestUpload (0x35) Page reference page 60 |
| REQ_UDS-0118 | M 5.5.14.1.1 Request parameter dataFormatIdentifier - 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 – 0x1Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.14 RequestUpload (0x35) page 60 Source detailsDocument section 5.5.14 RequestUpload (0x35) Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.14 RequestUpload (0x35) Page reference page 60 |
| REQ_UDS-0120 | 5.5.14.2 Positive response REQ_UDS 0293 5.5.14.2.1 Response parameter lengthFormatIdentifier - Table 70 – Service 0x35 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.15 TransferData (0x36) service page 61 Source detailsDocument section 5.5.15 TransferData (0x36) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.15 TransferData (0x36) service Page reference page 61 |
| REQ_UDS-0295 | 5.5.15 TransferData (0x36) service 5.5.15.1 RequestProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.15 TransferData (0x36) service page 61 Source detailsDocument section 5.5.15 TransferData (0x36) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.15 TransferData (0x36) service Page reference page 61 |
| REQ_UDS-0123 | 5.5.16.2 Positive response - Table 72 – Service 0x37 positive response parameter description 1 RequestTransferExit Response SID MProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.16 RequestTransferExit (0x37) service page 62 Source detailsDocument section 5.5.16 RequestTransferExit (0x37) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.16 RequestTransferExit (0x37) service Page reference page 62 |
| REQ_UDS-0134 | 5.5.18.1 Request - Refer to CVS31 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.18 Authentication (0x29) service page 64 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 64 |
| REQ_UDS-0135 | 5.5.18.2 Request parameter subFunction - Refer to CVS31 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.18 Authentication (0x29) service page 64 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 64 |
| REQ_UDS-0136 | 5.5.18.3 Positive response - Refer to CVS31 .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.18 Authentication (0x29) service page 64 Source detailsDocument section 5.5.18 Authentication (0x29) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.18 Authentication (0x29) service Page reference page 64 |
| REQ-AUTO-00704 | INFO_UDS 0020 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 69 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 69 |
| REQ_UDS-0163 | 5.6.2.1 Request - 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 70 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 70 |
| REQ_UDS-0167 | 255 – System specific 5.6.2.3 Positive response - 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-0xFFProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 71 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 71 |
| REQ_UDS-0169 | Internal Page 74 (90) #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier (MSB) 0xFF #4 routineIdentifier (LSB) 0x00 Example #2: Negative response: server → client Table 87 – Example #2: Negative response: server → client #1 Negative Response 0x7F #2 RoutineControl Response SID 0x31 #3 conditionsNotCorrect 0x22 5.6.3 Routine 0x2401 – Software Installation The RoutineIdentifier may verify the authenticity of the received file package.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.6.3 Routine 0x2401 – Software Installation page 74 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 74 |
| REQ_UDS-0208 | The timestamp is presented in SAE J1939-71 format without local hour/minute offsets.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.7.3 Timestamp of occurrence page 81 Source detailsDocument section 5.7.3 Timestamp of occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.3 Timestamp of occurrence Page reference page 81 |
| REQ_UDS-0209 | 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 timestampsProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.7.3 Timestamp of occurrence page 81 Source detailsDocument section 5.7.3 Timestamp of occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.3 Timestamp of occurrence Page reference page 81 |
| REQ_UDS-0215 | 5.7.4.1 Latest occurrence - The latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3 REQ_UDS 0216 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.7.4 Vehicle distance at occurrence page 82 Source detailsDocument section 5.7.4 Vehicle distance at occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.4 Vehicle distance at occurrence Page reference page 82 |
| REQ_UDS-0217 | 5.7.4.2 First occurrence - The first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.7.4 Vehicle distance at occurrence page 82 Source detailsDocument section 5.7.4 Vehicle distance at occurrence Section path 5 Requirements > 5.7 Fault memory requirements > 5.7.4 Vehicle distance at occurrence Page reference page 82 |
| REQ_UDS-0218 | The operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit).Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0220 | 5.7.5.1 Latest occurrence - The latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0221 | 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0222 | 5.7.5.2 First occurrence - 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.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.10 Session layer performance requirements page 83 Source detailsDocument section 5.10 Session layer performance requirements Section path 5 Requirements > 5.10 Session layer performance requirements Page reference page 83 |
| REQ_UDS-0339 | Internal Page 90 (90) Annex C (informative) Change history Release date Changes 2025-12 New requirements and infos: INFO_UDS 0039: F197 structure added F198 Request and response format REQ_UDS 0340: F199 Request and response format REQ_UDS 0341: F19A Request and response format REQ_UDS 0342: NRC for RBACC check failures REQ_UDS 0343, REQ_UDS 0344, REQ_UDS 0345, REQ_UDS 0346, REQ_UDS 0347, REQ_UDS 0348, REQ_UDS 0349: Requirements, Request and response formats for the ControlDTCSetting(0x85) added.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure communication and freshness protection None | None | - | 6 Normative references page 90 Source detailsDocument section 6 Normative references Section path 6 Normative references Page reference page 90 |
| REQ_UDS-0003 | Modified requirements - Added semantic Identifier DIDs, changed the NodeUID DID to INTERNAL REQ_UDS 0034: Change in the length of NodeUID(0xF1AF) INFO_UDS 0040: Change in the retrieval method for NodeUID(0xF1AF) REQ_UDS 0036: 0xF1B9 RBACCIdentifierNumber is changed to Mandatory REQ_UDS 0037: 0xF1BA RBACCStructureVersion,bit-length changed REQ_UDS 0045: Changes for service (0x84) and (0x31) REQ_UDS 0048: Updated the document references REQ_UDS 0107: 0XCAFE and 0xFF02 are updated to Mandatory REQ_UDS 0180: Modifcations on the bit values and new bit added REQ_UDS 0193: 0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infos: REQ_UDS 0045: (0x86) service removed REQ_UDS 0053, REQ_UDS 0054: Removed the reserved DID ranges and 0xF1C1 REQ_UDS 0024: 0xF19E ODXFileDataIdentifier is removed 2024-10 First issueProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | Secure communication and freshness protection None | None | - | 6 Normative references page 90 Source detailsDocument section 6 Normative references Section path 6 Normative references Page reference page 90 |
| REQ-AUTO-00484 | The User shall apply the latest version of this CVS124.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | page-1 Page 1 page 1 Source detailsDocument section page-1 Page 1 Section path Page 1 Page reference page 1 |
| REQ-AUTO-00486 | 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”.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-009 | - | page-2 Page 2 page 2 Source detailsDocument section page-2 Page 2 Section path Page 2 Page reference page 2 |
| REQ-AUTO-00487 | • 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | Backend and IT integration None | SSR-TOOL-002 | - | page-2 Page 2 page 2 Source detailsDocument section page-2 Page 2 Section path Page 2 Page reference page 2 |
| REQ-AUTO-00489 | Shall not This phrase, or the phrase "Must not", means that the definition is an absolute prohibition of the specification.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ-AUTO-00490 | 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ-AUTO-00493 | 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | Backend and IT integration None | SSR-TOOL-002 | - | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ-AUTO-00494 | 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ-AUTO-00495 | 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).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ-AUTO-00498 | E Mandatory for ECUs which shall be compliant with OBD legislation Worldwide like ISO27145,J1979 etc C Conditional U User optional.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 4.3 Conventions page 7 Source detailsDocument section 4.3 Conventions Section path 4 Terms, definitions and abbreviations > 4.3 Conventions Page reference page 7 |
| REQ-AUTO-00573 | the disconnect from the battery shall not be simulated.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.2 ECUReset (0x11) service page 34 Source detailsDocument section 5.5.2 ECUReset (0x11) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.2 ECUReset (0x11) service Page reference page 34 |
| REQ-AUTO-00583 | 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).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | Backend and IT integration None | SSR-DIAG-003 | - | 5.5.3 CommunicationControl (0x28) service page 35 Source detailsDocument section 5.5.3 CommunicationControl (0x28) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.3 CommunicationControl (0x28) service Page reference page 35 |
| REQ-AUTO-00628 | If a mechanic is working on the vehicle, the driveline shall report Not Ready and place the vehicle in the state PropulsionNotReady.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 46 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 46 |
| REQ-AUTO-00635 | For these ECUs these bytes shall contain default value 0xFF (all bytes).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.10 ReadDTCInformation (0x19) service page 52 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 52 |
| REQ-AUTO-00637 | 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-DIAG-001 | - | 5.5.10 ReadDTCInformation (0x19) service page 53 Source detailsDocument section 5.5.10 ReadDTCInformation (0x19) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.10 ReadDTCInformation (0x19) service Page reference page 53 |
| REQ-AUTO-00683 | If the file is not stored at the location the file shall be added.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.19 RequestFileTransfer (0x38) service page 65 Source detailsDocument section 5.5.19 RequestFileTransfer (0x38) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.19 RequestFileTransfer (0x38) service Page reference page 65 |
| REQ-AUTO-00684 | M 0x04 ReadFile This value shall be used to read the file (upload) at the location defined by the filePathAndName parameter.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.19 RequestFileTransfer (0x38) service page 65 Source detailsDocument section 5.5.19 RequestFileTransfer (0x38) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.19 RequestFileTransfer (0x38) service Page reference page 65 |
| REQ-AUTO-00685 | U 0x05 ReadDir This value shall be used to read the directory defined in the filePathAndName parameter.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.19 RequestFileTransfer (0x38) service page 65 Source detailsDocument section 5.5.19 RequestFileTransfer (0x38) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.19 RequestFileTransfer (0x38) service Page reference page 65 |
| REQ-AUTO-00686 | U 0x06 ResumeFile This value shall be used to resume downloading the file defined in the filePathAndName parameter at the returned filePosition indicator.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.5.19 RequestFileTransfer (0x38) service page 65 Source detailsDocument section 5.5.19 RequestFileTransfer (0x38) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.19 RequestFileTransfer (0x38) service Page reference page 65 |
| REQ-AUTO-00687 | The file specified in the filePathAndName shall already exist in the ECU’s file system.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | Hardware platform support None | SSR-HW-001 | - | 5.5.19 RequestFileTransfer (0x38) service page 65 Source detailsDocument section 5.5.19 RequestFileTransfer (0x38) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.19 RequestFileTransfer (0x38) service Page reference page 65 |
| REQ-AUTO-00694 | If the ECU received the information related to any of the conditions during the same driving cycle then it shall use that information.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | Hardware platform support None | SSR-HW-001 | - | 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions page 67 Source detailsDocument section 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions Page reference page 67 |
| REQ-AUTO-00708 | the erasing of memory shall proceed in parallel with data transfer in case for ECUs implementing Automatic erase.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | Hardware platform support None | SSR-HW-001 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 70 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 70 |
| REQ-AUTO-00712 | 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 & SUV2_REQ 62 & SUV2_REQ 63 in CVS123.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. | Accept | Proposal Ready | None | Application software behavior None | SSR-SYS-008 | - | 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) page 71 Source detailsDocument section 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) Page reference page 71 |
| REQ-AUTO-00729 | Information shall be provided in percentage.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ-AUTO-00731 | Information shall be provided in seconds.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | System behavior None | SSR-SYS-005 | - | 5.6.3 Routine 0x2401 – Software Installation page 76 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 76 |
| REQ-AUTO-00735 | 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).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria. | Accept | Proposal Ready | None | Application software behavior None | SSR-SYS-008 | - | 5.6.3 Routine 0x2401 – Software Installation page 77 Source detailsDocument section 5.6.3 Routine 0x2401 – Software Installation Section path 5 Requirements > 5.6 Routine Identifier Requirements > 5.6.3 Routine 0x2401 – Software Installation Page reference page 77 |
| REQ-AUTO-00485 | Internal Page 2 (90) Foreword This CVS124 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | page-2 Page 2 page 2 Source detailsDocument section page-2 Page 2 Section path Page 2 Page reference page 2 |
| REQ-AUTO-00492 | May This word, or the adjective “Optional”, means that an item is truly optional.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 4.2 Abbreviations page 6 Source detailsDocument section 4.2 Abbreviations Section path 4 Terms, definitions and abbreviations > 4.2 Abbreviations Page reference page 6 |
| REQ-AUTO-00563 | Its upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. | Informational Only | Proposal Ready | None | None None | None | - | 5.5.1 DiagnosticSessionControl (0x10) service page 32 Source detailsDocument section 5.5.1 DiagnosticSessionControl (0x10) service Section path 5 Requirements > 5.5 Diagnostic services requirements > 5.5.1 DiagnosticSessionControl (0x10) service Page reference page 32 |
Derived Supplier System Requirements
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 | Application software behavior — Bootloader and Application State HandlingThe ECU shall verify boot and application authenticity/integrity for Application software behavior and enforce the defined behaviour on verification failure.From this PDF: REQ-AUTO-00540; REQ_UDS-0083; REQ_UDS-0166. This SSR is also supported by requirements from other PDFs. | Application software behavior | None | None | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-BOOT-002 | Hardware platform support — Bootloader and Application State HandlingThe ECU shall verify boot and application authenticity/integrity for Hardware platform support and enforce the defined behaviour on verification failure.From this PDF: REQ_UDS-0159. This SSR is also supported by requirements from other PDFs. | Hardware platform support | None | None | Supplier-Owned | Candidate | Review + Test |
| SSR-BOOT-003 | System behavior — Bootloader and Application State HandlingThe ECU shall verify boot and application authenticity/integrity for System behavior and enforce the defined behaviour on verification failure.From this PDF: REQ_UDS-0164. This SSR is also supported by requirements from other PDFs. | System behavior | None | None | Supplier-Owned | Candidate | Review + Test |
| SSR-COM-003 | Backend and IT integration — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Backend and IT integration, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.From this PDF: REQ-AUTO-00776. This SSR is also supported by requirements from other PDFs. | Backend and IT integration | None | None | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-DAI-002 | System behavior — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of System behavior data and reject manipulated or unauthenticated data.From this PDF: REQ_UDS-0176; REQ_UDS-0178; REQ_UDS-0179. This SSR is also supported by requirements from other PDFs. | System behavior | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Review + Test |
| SSR-DAI-003 | Application software behavior — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Application software behavior data and reject manipulated or unauthenticated data.From this PDF: REQ_UDS-0177; REQ_UDS-0186; REQ_UDS-0187. This SSR is also supported by requirements from other PDFs. | Application software behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-DAI-004 | Backend and IT integration — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Backend and IT integration data and reject manipulated or unauthenticated data.From this PDF: REQ_UDS-0170; REQ_UDS-0172; REQ_UDS-0188. This SSR is also supported by requirements from other PDFs. | Backend and IT integration | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-DIAG-001 | System behavior — Diagnostic ServicesThe ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ-AUTO-00636; REQ-AUTO-00637; REQ_UDS-0002; REQ_UDS-0012; REQ_UDS-0050; REQ_UDS-0054; REQ_UDS-0084; REQ_UDS-0088; REQ_UDS-0124; REQ_UDS-0127; REQ_UDS-0151; REQ_UDS-0152; REQ_UDS-0156; REQ_UDS-0168; REQ_UDS-0174; REQ_UDS-0180; REQ_UDS-0182; REQ_UDS-0184; REQ_UDS-0191; REQ_UDS-0198; REQ_UDS-0199; REQ_UDS-0200; REQ_UDS-0201; REQ_UDS-0203; REQ_UDS-0204; REQ_UDS-0205; REQ_UDS-0206; REQ_UDS-0207; REQ_UDS-0210; REQ_UDS-0211; REQ_UDS-0212; REQ_UDS-0213; REQ_UDS-0214; REQ_UDS-0219; REQ_UDS-0225; REQ_UDS-0226; REQ_UDS-0229; REQ_UDS-0237; REQ_UDS-0304. This SSR is also supported by requirements from other PDFs. | System behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Test |
| SSR-DIAG-002 | System behavior — Diagnostic ServicesThe ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ_UDS-0230. | System behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Test |
| SSR-DIAG-003 | Backend and IT integration — Diagnostic ServicesThe ECU shall provide the diagnostic services for Backend and IT integration required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ-AUTO-00578; REQ-AUTO-00583; REQ_UDS-0001; REQ_UDS-0067; REQ_UDS-0183; REQ_UDS-0185; REQ_UDS-0202; REQ_UDS-0227; REQ_UDS-0338. This SSR is also supported by requirements from other PDFs. | Backend and IT integration | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Test |
| SSR-DIAG-004 | Application software behavior — Diagnostic ServicesThe ECU shall provide the diagnostic services for Application software behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ-AUTO-00559; REQ-AUTO-00633; REQ-AUTO-00732; REQ_UDS-0044; REQ_UDS-0046; REQ_UDS-0062; REQ_UDS-0071; REQ_UDS-0072; REQ_UDS-0075; REQ_UDS-0081; REQ_UDS-0082; REQ_UDS-0085; REQ_UDS-0087; REQ_UDS-0089; REQ_UDS-0096; REQ_UDS-0098; REQ_UDS-0099; REQ_UDS-0100; REQ_UDS-0102; REQ_UDS-0108; REQ_UDS-0109; REQ_UDS-0112; REQ_UDS-0119; REQ_UDS-0121; REQ_UDS-0125; REQ_UDS-0139; REQ_UDS-0140; REQ_UDS-0142; REQ_UDS-0143; REQ_UDS-0150; REQ_UDS-0158; REQ_UDS-0160; REQ_UDS-0171; REQ_UDS-0175; REQ_UDS-0181; REQ_UDS-0195; REQ_UDS-0260. This SSR is also supported by requirements from other PDFs. | Application software behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Test |
| SSR-DIAG-005 | System behavior — Diagnostic ServicesThe ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ_UDS-0052; REQ_UDS-0056; REQ_UDS-0106; REQ_UDS-0137; REQ_UDS-0228; REQ_UDS-0241; REQ_UDS-0242; REQ_UDS-0245; REQ_UDS-0249; REQ_UDS-0255; REQ_UDS-0258; REQ_UDS-0266; REQ_UDS-0267; REQ_UDS-0268; REQ_UDS-0270; REQ_UDS-0271; REQ_UDS-0272; REQ_UDS-0274; REQ_UDS-0275; REQ_UDS-0276; REQ_UDS-0277; REQ_UDS-0278; REQ_UDS-0279; REQ_UDS-0280; REQ_UDS-0281; REQ_UDS-0284; REQ_UDS-0288; REQ_UDS-0292; REQ_UDS-0294; REQ_UDS-0296; REQ_UDS-0297. | System behavior | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test |
| SSR-DIAG-006 | Hardware platform support — Diagnostic ServicesThe ECU shall provide the diagnostic services for Hardware platform support required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ_UDS-0053; REQ_UDS-0065; REQ_UDS-0066; REQ_UDS-0091; REQ_UDS-0196. | Hardware platform support | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Test |
| SSR-DIAG-007 | External interfaces — Diagnostic ServicesThe ECU shall provide the diagnostic services for External interfaces required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ-AUTO-00630; REQ_UDS-0126. | External interfaces | None | External Interfaces | Supplier-Owned | Candidate | Test |
| SSR-HW-001 | Hardware platform support — Hardware / HSM / Secure StorageThe ECU hardware shall provide the platform and secure-storage capabilities required for Hardware platform support.From this PDF: REQ-AUTO-00687; REQ-AUTO-00694; REQ-AUTO-00708. This SSR is also supported by requirements from other PDFs. | Hardware platform support | None | OEM/Customer Review Interface | Shared | Ready for Customer Alignment | Review + Test |
| SSR-KEY-001 | Key management — Key and Certificate HandlingThe ECU shall manage key and certificate material for Key management across provisioning, storage, use, renewal and revocation per the agreed key lifecycle.From this PDF: REQ_UDS-0068; REQ_UDS-0070; REQ_UDS-0092. This SSR is also supported by requirements from other PDFs. | Key management | Key management | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-RBAC-001 | Diagnostic security — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Diagnostic security, restricting security-relevant diagnostic services per the OEM-agreed role model.From this PDF: REQ-AUTO-00496; REQ_UDS-0040; REQ_UDS-0042; REQ_UDS-0043; REQ_UDS-0055; REQ_UDS-0063; REQ_UDS-0076; REQ_UDS-0223; REQ_UDS-0224; REQ_UDS-0344. This SSR is also supported by requirements from other PDFs. | Diagnostic security | Diagnostic security | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-RBAC-003 | Backend and IT integration — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Backend and IT integration, restricting security-relevant diagnostic services per the OEM-agreed role model.From this PDF: REQ_UDS-0047. This SSR is also supported by requirements from other PDFs. | Backend and IT integration | None | None | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-RBAC-004 | Application software behavior — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Application software behavior, restricting security-relevant diagnostic services per the OEM-agreed role model.From this PDF: REQ_UDS-0048; REQ_UDS-0128; REQ_UDS-0133; REQ_UDS-0342. This SSR is also supported by requirements from other PDFs. | Application software behavior | None | None | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-SDT-001 | Application software behavior — Secure Data Transfer / Data Security ContainerThe ECU shall protect security-relevant data transfer for Application software behavior using the agreed secured data transfer / data security container scheme.From this PDF: REQ_UDS-0110; REQ_UDS-0161. This SSR is also supported by requirements from other PDFs. | Application software behavior | None | None | Shared | Ready for Customer Alignment | Review + Test |
| SSR-SYS-005 | System behavior — System FunctionThe ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00484; REQ-AUTO-00489; REQ-AUTO-00490; REQ-AUTO-00494; REQ-AUTO-00495; REQ-AUTO-00498; REQ-AUTO-00499; REQ-AUTO-00513; REQ-AUTO-00573; REQ-AUTO-00574; REQ-AUTO-00628; REQ-AUTO-00635; REQ-AUTO-00648; REQ-AUTO-00683; REQ-AUTO-00684; REQ-AUTO-00685; REQ-AUTO-00686; REQ-AUTO-00691; REQ-AUTO-00729; REQ-AUTO-00731. This SSR is also supported by requirements from other PDFs. | System behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Test |
| SSR-SYS-008 | Application software behavior — System FunctionThe ECU shall implement the Application software behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00608; REQ-AUTO-00626; REQ-AUTO-00712; REQ-AUTO-00735. This SSR is also supported by requirements from other PDFs. | Application software behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Test |
| SSR-SYS-009 | System behavior — System FunctionThe ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00486. This SSR is also supported by requirements from other PDFs. | System behavior | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test |
| SSR-TOOL-002 | Backend and IT integration — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Backend and IT integration.From this PDF: REQ-AUTO-00487; REQ-AUTO-00493. This SSR is also supported by requirements from other PDFs. | Backend and IT integration | None | None | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-UPD-001 | System behavior — Software Update / FlashingThe ECU shall support secure software update/flashing for System behavior, accepting only authenticated, integrity-verified software through the agreed programming sequence.From this PDF: REQ_UDS-0061; REQ_UDS-0147; REQ_UDS-0148; REQ_UDS-0149; REQ_UDS-0153; REQ_UDS-0155; REQ_UDS-0157; REQ_UDS-0162; REQ_UDS-0173; REQ_UDS-0189; REQ_UDS-0193. This SSR is also supported by requirements from other PDFs. | System behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-UPD-002 | Hardware platform support — Software Update / FlashingThe ECU shall support secure software update/flashing for Hardware platform support, accepting only authenticated, integrity-verified software through the agreed programming sequence.From this PDF: REQ_UDS-0005; REQ_UDS-0009; REQ_UDS-0039; REQ_UDS-0232; REQ_UDS-0236. This SSR is also supported by requirements from other PDFs. | Hardware platform support | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Review + Test |
| SSR-UPD-003 | Application software behavior — Software Update / FlashingThe ECU shall support secure software update/flashing for Application software behavior, accepting only authenticated, integrity-verified software through the agreed programming sequence.From this PDF: REQ-AUTO-00585; REQ-AUTO-00702; REQ-AUTO-00746; REQ_UDS-0027; REQ_UDS-0028; REQ_UDS-0057; REQ_UDS-0058; REQ_UDS-0111; REQ_UDS-0190; REQ_UDS-0192; REQ_UDS-0250. This SSR is also supported by requirements from other PDFs. | Application software behavior | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-UPD-005 | Backend and IT integration — Software Update / FlashingThe ECU shall support secure software update/flashing for Backend and IT integration, accepting only authenticated, integrity-verified software through the agreed programming sequence.From this PDF: REQ-AUTO-00561; REQ-AUTO-00733; REQ_UDS-0060; REQ_UDS-0194. This SSR is also supported by requirements from other PDFs. | Backend and IT integration | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test |
System / Security Design Impact
| Impact Area | Evidence From This PDF |
|---|---|
| Impacted system features | Application software behavior; Application software behavior; Secure software update and flash readiness; Application software behavior; Security evidence and traceability; Application software behavior; System behavior; Secure software update and flash readiness; Backend and IT integration; Backend and IT integration; Secure software update and flash readiness; Backend and IT integration; Security evidence and traceability; Diagnostic security; Diagnostic security; Secure software update and flash readiness; Security evidence and traceability; External interfaces; Hardware platform support; Hardware platform support; Secure software update and flash readiness (showing 12 of 18) |
| 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 (showing 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/High/Medium; 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/Low; Medium/High/Medium (showing 12 of 15) |
| Design assumptions introduced | Security-relevant requirement the ECU can own once responsibility/method is confirmed. |
| Design decisions required | Send linked open point to the customer for decision.; Agree responsibility split (DIA) for the non-ECU portion. |
Estimation / Resource / Tooling Impact
| Impact | Status |
|---|---|
| Estimation impact | yes |
| Resource/tool/IT/HW/test impact | High/High/Low; High/High/Medium; 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/Low; Medium/High/Medium (showing 12 of 15) |
Document Impact Diagram
Document Impact
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: Application software behavior"]
doc --> f0
f1["Feature: Application software behavior; Secure software update and flash readiness"]
doc --> f1
f2["Feature: Application software behavior; 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-003"]
doc --> s2
o0["Open point: OP-001"]
doc --> o0
o1["Open point: OP-002"]
doc --> o1
o2["Open point: OP-004"]
doc --> o2
Mermaid source
flowchart LR
doc["CVS124.pdf"]
d0["Diagnostic security"]
doc --> d0
d1["Key management"]
doc --> d1
f0["Feature: Application software behavior"]
doc --> f0
f1["Feature: Application software behavior; Secure software update and flash readiness"]
doc --> f1
f2["Feature: Application software behavior; 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-003"]
doc --> s2
o0["Open point: OP-001"]
doc --> o0
o1["Open point: OP-002"]
doc --> o1
o2["Open point: OP-004"]
doc --> o2
Traceability
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Customer Requirement | SSR | Disposition | Confidence | Reason |
|---|---|---|---|---|
| REQ_UDS-0051 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0051 | None | Duplicate / Merged | n/a | Duplicate of another requirement. |
| REQ_UDS-0051 | None | Duplicate / Merged | n/a | Duplicate of another requirement. |
| REQ-AUTO-00484 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00485 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ-AUTO-00486 | SSR-SYS-009 | Covered by Existing Supplier System Requirement | High | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00487 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00488 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| REQ-AUTO-00489 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00490 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00491 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| REQ-AUTO-00492 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ-AUTO-00493 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00494 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00495 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00496 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00497 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| REQ-AUTO-00498 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00499 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0001 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0002 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0003 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0004 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0005 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0006 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0007 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0232 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0008 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0009 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0010 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0012 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0014 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ-AUTO-00513 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0015 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0016 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0236 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0017 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0020 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0237 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0339 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0340 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0341 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0023 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0025 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0027 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0028 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0030 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0032 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0033 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0036 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0037 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0038 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0039 | SSR-UPD-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0040 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0041 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0042 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0043 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0044 | SSR-DIAG-004 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| REQ_UDS-0045 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ-AUTO-00540 | SSR-BOOT-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0046 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0047 | SSR-RBAC-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0048 | SSR-RBAC-004 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0049 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0050 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0051 | None | Duplicate / Merged | n/a | Duplicate of another requirement. |
| REQ_UDS-0338 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0305 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0306 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0316 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0328 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0052 | SSR-DIAG-005 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| REQ_UDS-0053 | SSR-DIAG-006 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| REQ_UDS-0054 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0055 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0056 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0342 | SSR-RBAC-004 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0057 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00559 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0058 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00561 | SSR-UPD-005 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0060 | SSR-UPD-005 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00563 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0061 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0241 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0242 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0062 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0063 | SSR-RBAC-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0065 | SSR-DIAG-006 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0066 | SSR-DIAG-006 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0067 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0068 | SSR-KEY-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00573 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00574 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0070 | SSR-KEY-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0071 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0072 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00578 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0073 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0245 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0074 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0075 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00583 | SSR-DIAG-003 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0076 | SSR-RBAC-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00585 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0078 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0081 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00588 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0249 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0250 | SSR-UPD-003 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0344 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0345 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0346 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0347 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0348 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0349 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0082 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0083 | SSR-BOOT-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0084 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0085 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0087 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0255 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0088 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0089 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0091 | SSR-DIAG-006 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0092 | SSR-KEY-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0093 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ-AUTO-00608 | SSR-SYS-008 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0258 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0259 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0260 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0094 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0095 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0266 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0267 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0096 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0268 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0098 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0270 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0271 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0272 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0274 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0275 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0276 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0277 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00626 | SSR-SYS-008 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0099 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00628 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00629 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ-AUTO-00630 | SSR-DIAG-007 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| REQ_UDS-0304 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0100 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00633 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00634 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| REQ-AUTO-00635 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00636 | SSR-DIAG-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00637 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0278 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0279 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0280 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0281 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0102 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0103 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0104 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0284 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0105 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0106 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00648 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0107 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0288 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0108 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00652 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0109 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0110 | SSR-SDT-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0111 | SSR-UPD-003 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0112 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0113 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0114 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0116 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0117 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0118 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0119 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0292 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0120 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0294 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0295 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0296 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0297 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0121 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0123 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0124 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0125 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0126 | SSR-DIAG-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0127 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0128 | SSR-RBAC-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0133 | SSR-RBAC-004 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0134 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0135 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0136 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0137 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0139 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0140 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00683 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00684 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00685 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00686 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00687 | SSR-HW-001 | Covered by Existing Supplier System Requirement | High | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0142 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0143 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0147 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00691 | SSR-SYS-005 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0148 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0149 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00694 | SSR-HW-001 | Covered by Existing Supplier System Requirement | High | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0150 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0151 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0152 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0153 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0155 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0156 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0157 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00702 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0158 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00704 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0159 | SSR-BOOT-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0160 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0161 | SSR-SDT-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00708 | SSR-HW-001 | Covered by Existing Supplier System Requirement | High | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0162 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0163 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0164 | SSR-BOOT-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00712 | SSR-SYS-008 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0166 | SSR-BOOT-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0167 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0168 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0169 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0170 | SSR-DAI-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0171 | SSR-DIAG-004 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0172 | SSR-DAI-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0173 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0174 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0175 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0176 | SSR-DAI-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0177 | SSR-DAI-003 | Covered by Existing Supplier System Requirement | Low | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0178 | SSR-DAI-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0179 | SSR-DAI-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0180 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0181 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00729 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0182 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00731 | SSR-SYS-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00732 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00733 | SSR-UPD-005 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0183 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ-AUTO-00735 | SSR-SYS-008 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0184 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0185 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0186 | SSR-DAI-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0187 | SSR-DAI-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0188 | SSR-DAI-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0189 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0190 | SSR-UPD-003 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0191 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0192 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0193 | SSR-UPD-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00746 | SSR-UPD-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0194 | SSR-UPD-005 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0195 | SSR-DIAG-004 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0196 | SSR-DIAG-006 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0198 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0199 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0200 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0201 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0202 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0203 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0204 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0205 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0206 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0207 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0208 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0209 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0210 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0211 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0212 | SSR-DIAG-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0213 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0214 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0215 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0217 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0218 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0219 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0220 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0221 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0222 | None | Informational Only | n/a | Non-binding; not derived. |
| REQ_UDS-0223 | SSR-RBAC-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0224 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ-AUTO-00776 | SSR-COM-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0225 | SSR-DIAG-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0226 | SSR-DIAG-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0227 | SSR-DIAG-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0228 | SSR-DIAG-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| REQ_UDS-0229 | SSR-DIAG-001 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0230 | SSR-DIAG-002 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| REQ_UDS-0339 | None | Duplicate / Merged | n/a | Duplicate of another requirement. |
| REQ_UDS-0003 | None | Duplicate / Merged | n/a | Duplicate of another requirement. |
Detailed Evidence
Document intelligence markdown
CVS124
- Source PDF:
customer-input/pdf/CVS124.pdf - Converted Markdown:
converted/markdown/CVS124.md - Document type: Diagnostic Standard
- Domain: Diagnostics
- Confidence: High
- Evidence basis: Markdown-derived requirements and generated RFQX registers; no downstream PDF analysis.
Executive Summary
Confirmed by requirements: this diagnostic standard contributes 301 Markdown-derived RFQ requirements with the strongest evidence in diagnostics and service access. Inferred from requirement pattern: for RFQX it affects the Electric Clutch Actuator ECU on the TRATON GW AMT platform by shaping diagnostics and service access; core eca system behavior; system architecture design.
Confirmed by requirements: supplier positioning is 25 accept; 150 accept with assumption; 45 partially accept; 3 needs customer clarification; 2 needs internal review (showing 5 of 6). The generated traceability links this document to 28 supplier system requirement records. Inferred from mapped features, capabilities, and interfaces: the main design/security impact is diagnostics and service access; core eca system behavior; system architecture design. These themes should drive concept updates, verification evidence, and supplier proposal assumptions only where the linked requirements support them.
Requires customer confirmation: 5 document-linked open point(s) remain, 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. (showing 3 of 5). Do not convert these items into agreed baseline scope until the customer confirms the decision. Confidence and limits: High confidence. Evidence is limited to Markdown-derived requirements, registers, open points, and SSR links; no downstream PDF analysis or AI-generated conclusion is claimed.
Document Abstract
| Field | Interpretation |
|---|---|
| Document Purpose | Confirmed by requirements: this diagnostic standard contributes 301 Markdown-derived RFQ requirements with the strongest evidence in diagnostics and service access. |
| Engineering Interpretation | Inferred from requirement pattern: for RFQX it affects the Electric Clutch Actuator ECU on the TRATON GW AMT platform by shaping diagnostics and service access; core eca system behavior; system architecture design. |
| Supplier Proposal Impact | Confirmed by requirements: supplier positioning is 25 accept; 150 accept with assumption; 45 partially accept; 3 needs customer clarification; 2 needs internal review (showing 5 of 6). The generated traceability links this document to 28 supplier system requirement records. |
| System / Security Impact | Inferred from mapped features, capabilities, and interfaces: the main design/security impact is diagnostics and service access; core eca system behavior; system architecture design. These themes should drive concept updates, verification evidence, and supplier proposal assumptions only where the linked requirements support them. |
| Customer Clarification Impact | Requires customer confirmation: 5 document-linked open point(s) remain, 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. (showing 3 of 5). Do not convert these items into agreed baseline scope until the customer confirms the decision. |
| Confidence and Limits | Confidence and limits: High confidence. Evidence is limited to Markdown-derived requirements, registers, open points, and SSR links; no downstream PDF analysis or AI-generated conclusion is claimed. |
Main Requirement Themes
| Theme | Summary | Requirement Count | Representative Requirements |
|---|---|---|---|
| Diagnostics and service access | Defines UDS service behavior, authorization expectations, safe-state checks, and diagnostic evidence. | 261 | REQ-AUTO-00496; REQ_UDS-0001; REQ_UDS-0002 |
| Core ECA system behavior | Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope. | 228 | REQ-AUTO-00484; REQ-AUTO-00485; REQ-AUTO-00486 |
| System architecture design | Groups related document requirements into a single engineering theme. | 225 | REQ-AUTO-00484; REQ-AUTO-00485; REQ-AUTO-00488 |
| System | Groups related document requirements into a single engineering theme. | 111 | REQ-AUTO-00484; REQ-AUTO-00485; REQ-AUTO-00488 |
| Responsibility and customer approval model | Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk. | 109 | REQ-AUTO-00486; REQ-AUTO-00487; REQ-AUTO-00493 |
| Software | Groups related document requirements into a single engineering theme. | 89 | REQ_UDS-0003; REQ_UDS-0004; REQ_UDS-0006 |
| Cybersecurity concept and evidence | Drives cybersecurity concept, risk treatment, verification evidence, and traceability obligations. | 78 | REQ-AUTO-00486; REQ-AUTO-00487; REQ-AUTO-00493 |
| System core | Groups related document requirements into a single engineering theme. | 78 | REQ-AUTO-00484; REQ-AUTO-00488; REQ-AUTO-00489 |
Document Content Structure
| Section | Requirements | Critical | Open Points | SSR Links |
|---|---|---|---|---|
| 4 Terms, definitions and abbreviations | 12 | 1 | 1 | 3 |
| -- 4.2 Abbreviations | 8 | 1 | 1 | 2 |
| -- 4.3 Conventions | 4 | 0 | 0 | 2 |
| 5 Requirements | 283 | 47 | 4 | 26 |
| -- 5.2 ECU Identification Requirements | 33 | 1 | 1 | 5 |
| -- -- 5.2.1 Used data identifier in order to identify an ECU | 33 | 1 | 1 | 5 |
| -- 5.3 Diagnostic sessions requirements | 19 | 3 | 1 | 8 |
| -- 5.4 Data identifier requirements | 3 | 0 | 0 | 3 |
| -- -- 5.4.1 Integrity Validation Data DIDs (IVD-DIDs) | 3 | 0 | 0 | 3 |
| -- 5.5 Diagnostic services requirements | 133 | 21 | 3 | 17 |
| -- -- 5.5.1 DiagnosticSessionControl (0x10) service | 9 | 2 | 2 | 6 |
| -- -- 5.5.2 ECUReset (0x11) service | 16 | 6 | 1 | 8 |
| -- -- 5.5.3 CommunicationControl (0x28) service | 7 | 2 | 1 | 5 |
| -- -- 5.5.5 ControlDTCSetting (0x85) service | 7 | 1 | 1 | 4 |
| -- -- 5.5.6 Link Control (0x87) service | 6 | 2 | 1 | 3 |
| -- -- 5.5.7 ReadDataByIdentifier (0x22) service | 3 | 0 | 0 | 2 |
| -- -- 5.5.8 WriteDataByIdentifier (0x2E) service | 8 | 1 | 1 | 6 |
| -- -- 5.5.10 ReadDTCInformation (0x19) service | 29 | 2 | 2 | 6 |
| -- -- 5.5.11 InputOutputControlByIdentifier (0x2F) service | 5 | 0 | 0 | 2 |
| -- -- 5.5.12 RoutineControl (0x31) service | 5 | 0 | 0 | 2 |
| -- -- 5.5.13 Request Download Service (0x34) | 10 | 4 | 1 | 4 |
| -- -- 5.5.14 RequestUpload (0x35) | 2 | 0 | 0 | 0 |
| -- -- 5.5.15 TransferData (0x36) service | 5 | 0 | 0 | 2 |
| -- -- 5.5.16 RequestTransferExit (0x37) service | 4 | 0 | 0 | 2 |
| -- -- 5.5.18 Authentication (0x29) service | 10 | 1 | 1 | 5 |
| -- -- 5.5.19 RequestFileTransfer (0x38) service | 7 | 0 | 0 | 3 |
| -- 5.6 Routine Identifier Requirements | 61 | 14 | 2 | 16 |
| -- -- 5.6.1 Routine 0x2203 – CheckProgrammingPreConditions | 15 | 1 | 1 | 6 |
| -- -- 5.6.2 Routine 0xFF00 – EraseMemory (erasing the program memory) | 13 | 2 | 1 | 9 |
| -- -- 5.6.3 Routine 0x2401 – Software Installation | 31 | 10 | 1 | 11 |
| -- -- 5.6.5 Routine 0xCAFE – EMP | 2 | 1 | 1 | 2 |
| -- 5.7 Fault memory requirements | 20 | 2 | 1 | 3 |
| -- -- 5.7.2 Occurrence counter OCC | 7 | 1 | 1 | 3 |
| -- -- 5.7.3 Timestamp of occurrence | 6 | 0 | 0 | 1 |
| -- -- 5.7.4 Vehicle distance at occurrence | 7 | 1 | 1 | 1 |
| -- 5.10 Session layer performance requirements | 14 | 6 | 1 | 6 |
| 6 Normative references | 2 | 0 | 0 | 0 |
What this document does not confirm
Customer-owned responsibility, final customer decisions, and unresolved open points remain unconfirmed.
Critical Requirements
| ID | Score | Category | Reason | Statement |
|---|---|---|---|---|
| REQ-AUTO-00634 | 95 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; Unknown estimation impact; blocks SSR derivation | Internal Page 52 (90) 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. |
| REQ-AUTO-00488 | 80 | High risk due to unclear OEM/supplier responsibility | architecture relevant; Needs Customer Clarification; linked open point; Unknown estimation impact; blocks SSR derivation | 4 Terms, definitions and abbreviations 4.1 Terms 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. |
| REQ_UDS-0051 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; High estimation impact | Internal Page 26 (90) Diagnostics Service Diag Safe state check Application Boot loader TransferData (0x36) M - RequestFileTransfer (0x38) M - C1 = Mandatory except for going to default session C2 = Based on recommendation from Safety Team C3 = Needs to be defined at each individual routines REQ_UDS 0051 The server implementation shall comply with the following state diagram and the following state transition descriptions (P1 and P2 flags should be seen as implementation hints). |
| REQ_UDS-0063 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | REQ_UDS 0063 ECU shall execute the reset only after sending a positive response to the ECU reset service REQ_UDS 0064 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. |
| REQ_UDS-0068 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | Internal Page 34 (90) 5.5.2.1 Request REQ_UDS 0244 5.5.2.1.1 Request parameter resetType REQ_UDS 0068 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 REQ_UDS 0069 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. |
| REQ_UDS-0071 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | REQ_UDS 0071 The implementation of ECUReset service with requestParameter value 0x02 (keyOffOnReset) shall ensure that every server task is finished prior sending a positive response. |
| REQ_UDS-0076 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | INFO_UDS 0011 This requirement mitigates DOS (Denial Of Service) attacks REQ_UDS 0076 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 REQ_UDS 0077 Safety conditions are project specific and shall be checked before accepting a request to disable communication. |
| REQ_UDS-0128 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | 5.5.17.3 Negative response REQ_UDS 0128 Negative response shall be as per CVS32 5.5.17.3.1 Supported negative response codes REQ_UDS 0129 Negative response format shall be as per ISO 14229-1 5.5.18 Authentication (0x29) service REQ_UDS 0130 Authentication (0x29) service shall be used for authentication of client and server. |
| REQ-AUTO-00733 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | 5.6.4 Routine 0xFF01 – CheckProgrammingDependencies (check the flash programming) INFO_UDS 0029 This RoutineIdentifier value allows the client to start a consistency check of the server and should be able to execute independent from programming sequence. |
| REQ_UDS-0187 | 77 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact | REQ_UDS 0187 The authenticity and integrity information shall be supplied to the server before the software is updated. |
Open Points
| 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 |
Supplier System Requirements
| SSR | Title | Statement | Reqs From This PDF | Other PDFs | Status |
|---|---|---|---|---|---|
| SSR-BOOT-001 | Application software behavior — Bootloader and Application State Handling | The ECU shall verify boot and application authenticity/integrity for Application software behavior and enforce the defined behaviour on verification failure. | REQ-AUTO-00540; REQ_UDS-0083; REQ_UDS-0166 | yes | Blocked by Customer Clarification |
| SSR-BOOT-002 | Hardware platform support — Bootloader and Application State Handling | The ECU shall verify boot and application authenticity/integrity for Hardware platform support and enforce the defined behaviour on verification failure. | REQ_UDS-0159 | yes | Candidate |
| SSR-BOOT-003 | System behavior — Bootloader and Application State Handling | The ECU shall verify boot and application authenticity/integrity for System behavior and enforce the defined behaviour on verification failure. | REQ_UDS-0164 | yes | Candidate |
| SSR-COM-003 | Backend and IT integration — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for Backend and IT integration, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals. | REQ-AUTO-00776 | yes | Blocked by Customer Clarification |
| SSR-DAI-002 | System behavior — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of System behavior data and reject manipulated or unauthenticated data. | REQ_UDS-0176; REQ_UDS-0178; REQ_UDS-0179 | yes | Candidate |
| SSR-DAI-003 | Application software behavior — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Application software behavior data and reject manipulated or unauthenticated data. | REQ_UDS-0177; REQ_UDS-0186; REQ_UDS-0187 | yes | Blocked by Customer Clarification |
| SSR-DAI-004 | Backend and IT integration — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Backend and IT integration data and reject manipulated or unauthenticated data. | REQ_UDS-0170; REQ_UDS-0172; REQ_UDS-0188 | yes | Blocked by Customer Clarification |
| SSR-DIAG-001 | System behavior — Diagnostic Services | The ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers. | REQ-AUTO-00636; REQ-AUTO-00637; REQ_UDS-0002; REQ_UDS-0012; REQ_UDS-0050; REQ_UDS-0054; REQ_UDS-0084; REQ_UDS-0088; REQ_UDS-0124; REQ_UDS-0127; REQ_UDS-0151; REQ_UDS-0152; REQ_UDS-0156; REQ_UDS-0168; REQ_UDS-0174; REQ_UDS-0180; REQ_UDS-0182; REQ_UDS-0184; REQ_UDS-0191; REQ_UDS-0198; REQ_UDS-0199; REQ_UDS-0200; REQ_UDS-0201; REQ_UDS-0203; REQ_UDS-0204; REQ_UDS-0205; REQ_UDS-0206; REQ_UDS-0207; REQ_UDS-0210; REQ_UDS-0211; REQ_UDS-0212; REQ_UDS-0213; REQ_UDS-0214; REQ_UDS-0219; REQ_UDS-0225; REQ_UDS-0226; REQ_UDS-0229; REQ_UDS-0237; REQ_UDS-0304 | yes | Blocked by Customer Clarification |
| SSR-DIAG-002 | System behavior — Diagnostic Services | The ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers. | REQ_UDS-0230 | no | Blocked by Customer Clarification |
| SSR-DIAG-003 | Backend and IT integration — Diagnostic Services | The ECU shall provide the diagnostic services for Backend and IT integration required by the allocated customer requirements, including the specified services, sessions and data identifiers. | REQ-AUTO-00578; REQ-AUTO-00583; REQ_UDS-0001; REQ_UDS-0067; REQ_UDS-0183; REQ_UDS-0185; REQ_UDS-0202; REQ_UDS-0227; REQ_UDS-0338 | yes | Blocked by Customer Clarification |
| SSR-DIAG-004 | Application software behavior — Diagnostic Services | The ECU shall provide the diagnostic services for Application software behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers. | REQ-AUTO-00559; REQ-AUTO-00633; REQ-AUTO-00732; REQ_UDS-0044; REQ_UDS-0046; REQ_UDS-0062; REQ_UDS-0071; REQ_UDS-0072; REQ_UDS-0075; REQ_UDS-0081; REQ_UDS-0082; REQ_UDS-0085; REQ_UDS-0087; REQ_UDS-0089; REQ_UDS-0096; REQ_UDS-0098; REQ_UDS-0099; REQ_UDS-0100; REQ_UDS-0102; REQ_UDS-0108; REQ_UDS-0109; REQ_UDS-0112; REQ_UDS-0119; REQ_UDS-0121; REQ_UDS-0125; REQ_UDS-0139; REQ_UDS-0140; REQ_UDS-0142; REQ_UDS-0143; REQ_UDS-0150; REQ_UDS-0158; REQ_UDS-0160; REQ_UDS-0171; REQ_UDS-0175; REQ_UDS-0181; REQ_UDS-0195; REQ_UDS-0260 | yes | Blocked by Customer Clarification |
| SSR-DIAG-005 | System behavior — Diagnostic Services | The ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers. | REQ_UDS-0052; REQ_UDS-0056; REQ_UDS-0106; REQ_UDS-0137; REQ_UDS-0228; REQ_UDS-0241; REQ_UDS-0242; REQ_UDS-0245; REQ_UDS-0249; REQ_UDS-0255; REQ_UDS-0258; REQ_UDS-0266; REQ_UDS-0267; REQ_UDS-0268; REQ_UDS-0270; REQ_UDS-0271; REQ_UDS-0272; REQ_UDS-0274; REQ_UDS-0275; REQ_UDS-0276; REQ_UDS-0277; REQ_UDS-0278; REQ_UDS-0279; REQ_UDS-0280; REQ_UDS-0281; REQ_UDS-0284; REQ_UDS-0288; REQ_UDS-0292; REQ_UDS-0294; REQ_UDS-0296; REQ_UDS-0297 | no | Candidate |
| SSR-DIAG-006 | Hardware platform support — Diagnostic Services | The ECU shall provide the diagnostic services for Hardware platform support required by the allocated customer requirements, including the specified services, sessions and data identifiers. | REQ_UDS-0053; REQ_UDS-0065; REQ_UDS-0066; REQ_UDS-0091; REQ_UDS-0196 | no | Blocked by Customer Clarification |
| SSR-DIAG-007 | External interfaces — Diagnostic Services | The ECU shall provide the diagnostic services for External interfaces required by the allocated customer requirements, including the specified services, sessions and data identifiers. | REQ-AUTO-00630; REQ_UDS-0126 | no | Candidate |
| SSR-HW-001 | Hardware platform support — Hardware / HSM / Secure Storage | The ECU hardware shall provide the platform and secure-storage capabilities required for Hardware platform support. | REQ-AUTO-00687; REQ-AUTO-00694; REQ-AUTO-00708 | yes | Ready for Customer Alignment |
| SSR-KEY-001 | Key management — Key and Certificate Handling | The ECU shall manage key and certificate material for Key management across provisioning, storage, use, renewal and revocation per the agreed key lifecycle. | REQ_UDS-0068; REQ_UDS-0070; REQ_UDS-0092 | yes | Blocked by Customer Clarification |
| SSR-RBAC-001 | Diagnostic security — Secure Diagnostics / RBAC | The ECU shall enforce authenticated, role-authorised access for Diagnostic security, restricting security-relevant diagnostic services per the OEM-agreed role model. | REQ-AUTO-00496; REQ_UDS-0040; REQ_UDS-0042; REQ_UDS-0043; REQ_UDS-0055; REQ_UDS-0063; REQ_UDS-0076; REQ_UDS-0223; REQ_UDS-0224; REQ_UDS-0344 | yes | Blocked by Customer Clarification |
| SSR-RBAC-003 | Backend and IT integration — Secure Diagnostics / RBAC | The ECU shall enforce authenticated, role-authorised access for Backend and IT integration, restricting security-relevant diagnostic services per the OEM-agreed role model. | REQ_UDS-0047 | yes | Blocked by Customer Clarification |
| SSR-RBAC-004 | Application software behavior — Secure Diagnostics / RBAC | The ECU shall enforce authenticated, role-authorised access for Application software behavior, restricting security-relevant diagnostic services per the OEM-agreed role model. | REQ_UDS-0048; REQ_UDS-0128; REQ_UDS-0133; REQ_UDS-0342 | yes | Blocked by Customer Clarification |
| SSR-SDT-001 | Application software behavior — Secure Data Transfer / Data Security Container | The ECU shall protect security-relevant data transfer for Application software behavior using the agreed secured data transfer / data security container scheme. | REQ_UDS-0110; REQ_UDS-0161 | yes | Ready for Customer Alignment |
| SSR-SYS-005 | System behavior — System Function | The ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing. | REQ-AUTO-00484; REQ-AUTO-00489; REQ-AUTO-00490; REQ-AUTO-00494; REQ-AUTO-00495; REQ-AUTO-00498; REQ-AUTO-00499; REQ-AUTO-00513; REQ-AUTO-00573; REQ-AUTO-00574; REQ-AUTO-00628; REQ-AUTO-00635; REQ-AUTO-00648; REQ-AUTO-00683; REQ-AUTO-00684; REQ-AUTO-00685; REQ-AUTO-00686; REQ-AUTO-00691; REQ-AUTO-00729; REQ-AUTO-00731 | yes | Blocked by Customer Clarification |
| SSR-SYS-008 | Application software behavior — System Function | The ECU shall implement the Application software behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing. | REQ-AUTO-00608; REQ-AUTO-00626; REQ-AUTO-00712; REQ-AUTO-00735 | yes | Blocked by Customer Clarification |
| SSR-SYS-009 | System behavior — System Function | The ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing. | REQ-AUTO-00486 | yes | Candidate |
| SSR-TOOL-002 | Backend and IT integration — Tooling / IT / Evidence Storage | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Backend and IT integration. | REQ-AUTO-00487; REQ-AUTO-00493 | yes | Blocked by Customer Clarification |
| SSR-UPD-001 | System behavior — Software Update / Flashing | The ECU shall support secure software update/flashing for System behavior, accepting only authenticated, integrity-verified software through the agreed programming sequence. | REQ_UDS-0061; REQ_UDS-0147; REQ_UDS-0148; REQ_UDS-0149; REQ_UDS-0153; REQ_UDS-0155; REQ_UDS-0157; REQ_UDS-0162; REQ_UDS-0173; REQ_UDS-0189; REQ_UDS-0193 | yes | Blocked by Customer Clarification |
| SSR-UPD-002 | Hardware platform support — Software Update / Flashing | The ECU shall support secure software update/flashing for Hardware platform support, accepting only authenticated, integrity-verified software through the agreed programming sequence. | REQ_UDS-0005; REQ_UDS-0009; REQ_UDS-0039; REQ_UDS-0232; REQ_UDS-0236 | yes | Candidate |
| SSR-UPD-003 | Application software behavior — Software Update / Flashing | The ECU shall support secure software update/flashing for Application software behavior, accepting only authenticated, integrity-verified software through the agreed programming sequence. | REQ-AUTO-00585; REQ-AUTO-00702; REQ-AUTO-00746; REQ_UDS-0027; REQ_UDS-0028; REQ_UDS-0057; REQ_UDS-0058; REQ_UDS-0111; REQ_UDS-0190; REQ_UDS-0192; REQ_UDS-0250 | yes | Blocked by Customer Clarification |
| SSR-UPD-005 | Backend and IT integration — Software Update / Flashing | The ECU shall support secure software update/flashing for Backend and IT integration, accepting only authenticated, integrity-verified software through the agreed programming sequence. | REQ-AUTO-00561; REQ-AUTO-00733; REQ_UDS-0060; REQ_UDS-0194 | yes | Blocked by Customer Clarification |
Design Impact
- Impacted System Features: Application software behavior; Application software behavior; Secure software update and flash readiness; Application software behavior; Security evidence and traceability; Application software behavior; System behavior; Secure software update and flash readiness; Backend and IT integration; Backend and IT integration; Secure software update and flash readiness; Backend and IT integration; Security evidence and traceability; Diagnostic security (showing 8 of 18)
- 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 (showing 8 of 13)
- Impacted Work Products: Cybersecurity concept; Cybersecurity verification report; DIA / cybersecurity case; Requirement traceability record; System/architecture design
- Impacted Tools It Hardware Test: High/High/Low; High/High/Medium; High/Low/Low; High/Low/Medium; Low/High/High; Low/High/Low; Low/High/Medium; Low/Low/High (showing 8 of 15)
- Impacted Supplier System Requirements: SSR-BOOT-001; SSR-BOOT-002; SSR-BOOT-003; SSR-COM-003; SSR-DAI-002; SSR-DAI-003; SSR-DAI-004; SSR-DIAG-001 (showing 8 of 28)
- Design Assumptions Introduced: Security-relevant requirement the ECU can own once responsibility/method is confirmed.
- Design Decisions Required: Send linked open point to the customer for decision.; Agree responsibility split (DIA) for the non-ECU portion.