Operational Design Domain Decision for Automated Driving
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automatic driving systems struggle to determine the operational design domain effectively, especially when vehicles need to perform operations like follow-up traveling, overtaking, and lane keeping, as they rely solely on lane marking detection, neglecting the interaction with moving objects around the vehicle.
Innovation Solution
An operational design domain decision apparatus that utilizes a traffic map database to estimate vehicle position, acquire speed restrictions, calculate the required detection distance for object detection sensors, and determine if the automatic driving system is within the operational design domain by comparing the detectable distance with the required distance, considering the vehicle and moving object speeds.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the automatic driving determination is based solely on lane marking detection, then the system simplicity is maintained, but the accuracy of operational design domain determination deteriorates when moving objects are involved
Solution Approach 1:
The patent merges multiple determination criteria (lane marking detection, object detection sensor results, and speed restriction information) into a unified operational design domain determination system. This combination allows the system to accurately assess whether automatic driving can be executed by considering both lane keeping capability and interaction with moving objects, resolving the contradiction between system simplicity and determination accuracy.
2Reliability
If the detection distance requirement is calculated considering speed restrictions and moving object interactions, then the safety of automatic driving is improved, but the computational complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-storing speed restriction information in a database before automatic driving execution. The electronic control unit retrieves this pre-stored information and combines it with real-time detection data to calculate detection distance requirements. This approach improves safety by considering speed restrictions and moving object interactions while reducing computational complexity during real-time operation.
3Adaptability or versatility
If the operational design domain is expanded to include various operations like follow-up traveling and overtaking, then the versatility of automatic driving is improved, but the difficulty of determining appropriate execution conditions increases
Solution Approach 1:
The patent implements a universal determination mechanism that uses the same core logic (comparing detection distance requirements with actual detection capabilities) across multiple different automatic driving operations including lane keeping, follow-up traveling, and overtaking. This universal approach allows the system to accurately determine execution conditions for various operations without requiring separate complex determination systems for each function.
Data Source
AI summary
An operational design domain decision apparatus includes: a position estimation unit configured to estimate a vehicle position; a traffic map database in which a restriction related to a vehicle speed and a position are associated with each other; a rule acquisition unit configured to acquire the restriction; a required value calculation unit configured to calculate a required detection distance at which it is necessary for an object detection sensor equipped in the vehicle to have detected a moving object for execution of a predetermined automatic driving; a distance measurement unit configured to calculate a detectable distance based on a detection result of the object detection sensor; and a determination unit configured to determine that the automatic driving system is in the operational design domain, when the detectable distance is equal to or more than the required detection distance.