Needs beyond UDS
The rationale for exploring options beyond UDS stems from its reliance on a static configuration presented in the Open Diagnostic data eXchange (ODX) file format. This configuration model proves unsuitable for software-defined vehicles, which require the flexibility to accommodate frequent software changes. Given that high-performance computing systems serve as pivotal facilitators for software-defined vehicles, software is expected to assume increasing responsibilities.
Figure 5.1 – UDS boundaries
In the case of UDS, clients (testers/testing tools) need to have a UDS stack built in to translate UDS messages to human-readable information and vice versa. Figure 5.1 shows a high-level view of what UDS can support well in the High-Performance Computing world and what its limitations are. UDS is adequate in supporting diagnostics on classic Electronic Control Units. However, it is not adequate to support diagnostics for whole HPCs or...
