ADAS Routing Using V2X Collaboration and ODD Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Advanced Driver Assistance Systems (ADAS) face limitations in effectively utilizing supplemental information from Vehicle-to-Everything (V2X) communication to enhance navigation and routing, as current route selection algorithms prioritize speed and efficiency over ADAS functionality utilization, leading to suboptimal activation of ADAS features.
Innovation Solution
The proposed method involves generating ADAS-friendly routes by incorporating Operational Design Domain (ODD) information and collaboration data from V2X communication, which indicates physical interactions between drivers and ADAS functions, to increase the utilization of ADAS features and reduce driver workload.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If route selection algorithms prioritize speed and efficiency, then travel time is reduced, but ADAS functionality utilization deteriorates
Solution Approach 1:
The routing system dynamically adjusts route selection based on real-time conditions and ADAS operational characteristics. The system evaluates multiple route options and selects paths that optimize both travel time and ADAS functionality utilization, rather than statically prioritizing one objective. This dynamic approach allows the system to adapt to changing traffic conditions, road types, and ADAS performance requirements simultaneously.
Solution Approach 2:
The system changes the parameters used in route selection from traditional metrics (only speed and efficiency) to include ADAS-specific parameters such as operational design domain compatibility, feature activation opportunities, and collaboration scores. By modifying the optimization parameters to incorporate ADAS functionality metrics, the system achieves balanced routing that considers both time efficiency and driver assistance utilization.
2Productivity
If ADAS functions are activated in areas with limited operational design domain compatibility, then driver assistance coverage is improved, but system reliability deteriorates
Solution Approach 1:
The system performs preliminary evaluation of route options against operational design domain constraints before final route selection. By pre-assessing which routes offer compatible environments for ADAS functions (such as highways for autonomous driving modes versus urban streets for detection and warning functions), the system ensures that selected routes maintain high reliability while maximizing driver assistance coverage.
Solution Approach 2:
The system incorporates feedback mechanisms that continuously monitor actual ADAS performance and operational domain compliance along the selected route. This feedback allows the system to adjust future routing decisions, avoiding areas where reliability issues have been observed and prioritizing routes with proven ADAS operational success, thereby maintaining both coverage and reliability.
3Measurement precision
If routing information incorporates collaboration information from multiple sources, then routing accuracy is improved, but information processing complexity increases
Solution Approach 1:
The system extracts and separates collaboration information from multiple V2X sources into distinct, structured data elements that can be independently evaluated. By extracting specific metrics such as road condition data, traffic flow information, and ADAS performance metrics from various sources and organizing them into standardized formats, the system reduces processing complexity while maintaining routing accuracy through multi-source validation.
Data Source
AI summary
Techniques for providing and utilizing supplemental information obtained from Vehicle-to-Everything (V2X) enabled entities to enhance navigation and routing based on opportunities to implement Advanced Driver Assistance Systems (ADAS) functions are discussed. An example method for generating routing information for a vehicle includes determining a desired destination, obtaining operational design domain information based at least in part on a geographic area including a present location and the desired destination, determining collaboration information for one or more driving assistance functions based on the operational design domain information, the collaboration information including indications of physical actions performed by vehicle operators when the one or more driving assistance functions are activated, and generating routing information based at least in part on the collaboration information.