Autonomous Driving Feature Switching for Closed-Loop ODD Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The development and verification of Automated Driving Systems (ADS) are costly and time-consuming due to the difficulty in assessing reliability and safety, particularly in handling corner cases, which also leads to the 'curse of automation' where drivers become complacent, reducing their reaction times when relying on advanced driver-assistance systems (ADAS).
Innovation Solution
A method for controlling a vehicle's control system that switches between ADAS and under-development ADS features within an overlapping operational design domain (ODD), allowing for closed-loop testing and data collection while maintaining driver supervision to avoid the curse of automation, by activating the ADS feature for a significant portion of the time within the ODD, thereby accelerating development and improving data collection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional testing methods are used to ensure safety and reliability of autonomous systems, then the system meets safety standards, but the development cost and time increase significantly due to combinatorial explosion of possible situations
Solution Approach 1:
The patent applies preliminary action by using simulation environments to pre-test and verify autonomous driving features before real-world deployment. The system performs virtual validation of edge cases and corner cases in advance, reducing the need for extensive physical testing while maintaining safety standards.
Solution Approach 2:
The patent creates virtual copies of real-world driving scenarios through high-fidelity simulations. These simulated environments replicate complex road conditions, weather, and traffic situations, allowing comprehensive testing without the time and cost constraints of physical testing.
2Reliability
If engineers focus on solving corner cases to reach safety level for ADS launch, then reliability improves, but the customer value of ADAS modules decreases due to limited operational design domain
Solution Approach 1:
The patent applies partial action by enabling ADAS features to operate in broader conditions than strictly required for ADS safety certification. This allows the system to provide partial automation benefits to customers while reserve testing resources focus on critical corner cases for full autonomous deployment.
Solution Approach 2:
The patent segments the testing and deployment process into distinct phases: ADAS can be deployed to provide immediate customer value in common scenarios, while separate parallel development continues to solve corner cases for full ADS capability. This segmentation allows both goals to progress simultaneously.
3Ease of operation
If ADAS performance is improved to perfect comfort level, then driver satisfaction increases, but driver reaction time worsens due to the curse of automation
Solution Approach 1:
The patent implements feedback mechanisms that continuously monitor driver engagement and system performance. The system provides feedback to maintain optimal driver awareness levels, preventing complete disengagement while preserving comfort. This includes selective alerting and maintaining situational awareness without compromising driver experience.
Data Source
Figure 1a
Figure 1b
Figure 2
AI summary
The present disclosure relates to a method for controlling a control system of a vehicle having a first driver support module (e.g. ADAS feature) and a second driver support module (e.g. "under-development" ADS feature). The first driver support module and the second driver support module are capable of operation within an overlapping operational design domain (ODD). The method comprises obtaining sensor data comprising information about a surrounding environment of the vehicle, and determining fulfilment of the overlapping ODD based on the obtained sensor data. Further, if the overlapping ODD is fulfilled, the method comprises switching between a first configuration where the first driver support module is active and the second driver support module is inactive, and a second configuration where the first driver support module is inactive and the second driver support module is active. Moreover, the switching between the first configuration and the second configuration is based on a switching protocol in order to perform closed loop testing of the second driver support module for at least portion of a time period that the vehicle is within an environment that fulfils the overlapping ODD.