ADAS SoC Context-Aware Diagnostics for Low-Overhead Safety
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing advanced driver-assistance systems (ADAS) face challenges in efficiently performing diagnostic tests without consuming excessive system resources or disrupting system functionality, as periodic diagnostic tests can be resource-intensive and may impact performance.
Innovation Solution
Implementing context-aware safety diagnostics that identify and execute a targeted subset of diagnostic procedures based on application use case context information, using a context analyzer and safety management module to trigger specific diagnostic tests when needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If periodic diagnostic tests are performed to ensure system safety, then system reliability is improved, but system resource consumption increases and productivity decreases
Solution Approach 1:
The patent applies dynamics by transitioning from static periodic diagnostic testing to dynamic context-aware diagnostic testing. The system continuously monitors application context information and dynamically adjusts which diagnostic procedures are executed based on current system state, application requirements, and safety criticality. This allows the system to maintain reliability while minimizing disruptions to productivity by performing diagnostics only when contextually appropriate.
Solution Approach 2:
The patent changes the parameter of diagnostic execution from fixed periodic intervals to variable context-based triggering. By monitoring parameters such as application type, system state, and safety requirements, the system adjusts diagnostic execution parameters dynamically. This enables the system to perform comprehensive diagnostics when needed while reducing or eliminating unnecessary diagnostics during normal operation, thus resolving the contradiction between reliability and productivity.
2Measurement precision
If comprehensive diagnostic procedures are executed to improve system safety, then measurement precision is improved, but use of energy increases
Solution Approach 1:
The patent applies partial action by executing only the necessary subset of diagnostic procedures based on current context rather than running all available diagnostics. The system analyzes application context information to determine which specific components and functions require monitoring, then selects and executes only those diagnostic procedures relevant to the current operational state. This partial execution maintains diagnostic accuracy for critical functions while significantly reducing overall energy consumption compared to comprehensive periodic testing.
Solution Approach 2:
The patent segments the diagnostic procedure set into multiple categories based on application context, safety criticality, and component importance. Instead of executing a monolithic diagnostic suite, the system divides diagnostics into targeted groups and executes only the relevant segments based on current system state. This segmentation allows the system to maintain high measurement precision for critical functions while minimizing energy usage by excluding non-essential diagnostic operations.
3Reliability
If frequent diagnostic tests are performed to enhance system reliability, then reliability is improved, but loss of time increases
Solution Approach 1:
The patent modifies periodic action by replacing fixed-interval diagnostic execution with context-triggered diagnostic execution. Instead of performing diagnostics at regular time intervals regardless of system state, the system monitors for specific contextual conditions and triggers diagnostics only when those conditions indicate potential safety issues or changes in operational mode. This contextual periodicity maintains reliability by ensuring diagnostics occur when necessary while reducing time loss by eliminating unnecessary periodic interruptions during stable operation.
Data Source
AI summary
A method includes receiving application use case context information for context-aware safety management for an advanced driver-assistance system (ADAS) and/or an autonomous driving system-on-a-chip (SoC). The method also includes selecting a group of components of the SoC for running a selected subset of diagnostic procedures based on application use case context information. The method further includes identifying the selected subset of diagnostic procedures based on the group of components of the SoC associated with the use case context information. The selected subset of diagnostic procedures may be a subset of stored diagnostic procedures. The method still further includes triggering the selected subset of diagnostic procedures and performing the selected subset of diagnostic procedures based on the triggering.


