Autonomous Vehicle Component Testing via Segmented Self-Diagnosis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current parallel processing devices in autonomous vehicles lack the capability to test their individual components for functional correctness during operation, limiting their ability to detect faults and maintain performance.
Innovation Solution
A system and method for testing operational components of computer devices in autonomous vehicles, which involves selecting a test operation that utilizes the full capacity of the component, instructing the device to perform the test, generating and comparing results with a second device, and indicating faultiness based on differences between the results.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If built-in self-test (BIST) capability is implemented, then functional correctness can be tested at boot-up, but the device cannot run tests during operation and cannot test individual components
Solution Approach 1:
The patent segments the testing process into individual component-level tests that can be selectively executed during device operation. Each operational component (ALU, register, memory) can be tested independently through targeted test operations, allowing flexible testing without requiring complete device shutdown or boot-up sequences.
Solution Approach 2:
The patent implements dynamic testing capability where test operations can be executed at any time during device operation rather than being restricted to boot-up. The system can dynamically switch between normal operation modes and test modes, allowing components to be tested while the device remains operational and adaptable to different testing scenarios.
2Reliability
If comprehensive testing is performed, then functional correctness is verified, but performance impact increases and testing cannot be done during operation
Solution Approach 1:
The patent divides comprehensive testing into segmented, isolated component tests that can be executed individually. By testing one operational component at a time through targeted test operations, the system can verify functionality without requiring complete system shutdown or sacrificing overall device performance during normal operation.
Solution Approach 2:
The patent enables periodic testing where operational components are tested at scheduled intervals during device operation rather than continuously or exclusively at boot-up. This periodic testing approach allows fault detection while maintaining device productivity, as testing occurs during low-impact periods or idle time.
3Reliability
If test operations are executed during operation, then continuous monitoring is enabled, but computational capacity is consumed
Solution Approach 1:
The patent segments computational resources by isolating test operations from normal computational workloads. Test operations are executed as separate, targeted operations on specific operational components rather than consuming overall device computational capacity. This allows continuous monitoring while preserving productivity, as testing does not block normal device functions.
Solution Approach 2:
The patent implements self-service testing where operational components test their own functionality through self-directed test operations. Each component performs its own diagnostic tests independently, eliminating the need for external computational resources to conduct comprehensive testing. This self-testing capability enables continuous monitoring without significant computational overhead.
Data Source
AI summary
Systems and methods are provided for testing a first computer device of a vehicle. A method includes selecting an operational component of the first computer device and selecting a test operation that is configured to utilize an entire capacity of the operational component. The method further includes instructing the first computer device to perform the test operation and to generate a first result. The method further yet includes retrieving a second result of the test operation and comparing the first result of the test operation from the first computer device with the second result. The method further yet includes indicating that the first computer device is faulty based at least in part on a difference between the first result and the second result.