Vehicle Controller Fault Validation Using Simulated Log Injection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Autonomous and semi-autonomous vehicle systems face challenges in detecting and mitigating faults in real-time, as existing simulation methods only assess performance differences without ensuring fault detection and mitigation capabilities within critical time thresholds.

Innovation Solution

An evaluation computing system introduces faults into vehicle controller logs, runs simulations to determine fault detection and mitigation times, and iteratively modifies log data to test various fault scenarios, validating components based on threshold compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If existing simulation methods are used to assess performance differences, then performance comparison between system versions is achieved, but fault detection and mitigation capabilities within critical time thresholds cannot be ensured

Engineering Contradiction:
Improveperformance comparison accuracyVSAvoidfault detection capability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent applies preliminary action by introducing faults into log data before running simulations. The evaluation computing system proactively injects faults into historical log data associated with the vehicle controller, then executes simulations to observe how the controller responds to these introduced faults. This allows assessment of fault detection and mitigation capabilities before actual deployment, ensuring critical time threshold requirements are met while maintaining performance comparison accuracy.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If simulations are run to evaluate fault detection performance, then fault detection capability is validated, but additional computational time and resources are required

Engineering Contradiction:
Improvefault detection validationVSAvoidsimulation execution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies copying by using historical log data as a foundation and creating modified copies with introduced faults. Instead of creating entirely new simulation scenarios, the system copies existing operational log data and injects faults into these copies. This approach validates fault detection capability while reducing computational time, as the base log data already represents real operational conditions and only requires fault injection and simulation execution rather than complete scenario generation.

Inventive Principle:
Principle #26Copying

3Productivity

If the vehicle controller is updated to optimize performance, then system performance is improved, but fault detection capabilities may be compromised

Engineering Contradiction:
Improvesystem performanceVSAvoidfault detection capability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies feedback by establishing a closed-loop evaluation process. The evaluation computing system receives log data from the vehicle controller, introduces faults, runs simulations, and determines whether the controller detects and mitigates faults within specified time thresholds. This feedback mechanism validates that performance optimizations do not compromise fault detection capabilities, allowing confident deployment of updated systems while maintaining both performance and reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12258027B1Fault detection in vehicle control systems
Publication Date: 2025.03.25 ZOOX INC
  • US12258027B1 patent drawing
  • US12258027B1 patent drawing
  • US12258027B1 patent drawing

AI summary

An evaluation computing system may implement techniques to validate a vehicle controller, such as based on an update thereto. The evaluation computing system may access data associated with an operation of the vehicle in an environment as controlled by the controller. The evaluation computing system may modify a portion of the data representative of a fault associated with the controller. The evaluation computing system may run a simulation utilizing modified log data to determine whether the controller detects and/or mitigates the fault within a threshold time. Based on a determination that the controller does not detect and/or mitigate the fault within the threshold time, the evaluation computing system may determine an error associated with the controller. Based on a determination that the controller detects and/or mitigates the fault within the threshold time, the evaluation computing system may validate the controller.