Driving Support Device Reduces Unnecessary Warnings
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing driving support devices issue unnecessary warnings by not considering whether the host vehicle and collision-possible vehicles can reach the predicted collision point, leading to driver discomfort.
Innovation Solution
A driving support device with a host-vehicle scheduled route acquiring unit, information receiving unit, object-vehicle scheduled route acquiring unit, warning unit, and travelable condition determining unit, which assesses whether both vehicles can reach the route overlap point by transmitting travel record inquiry requests to a travel record server to determine the travelable conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the driving support device issues warnings based on scheduled route overlap without considering travelable conditions, then the warning coverage is improved, but the frequency of unnecessary warnings increases causing driver discomfort
Solution Approach 1:
The system performs preliminary determination of travelable conditions by checking historical travel data before issuing collision warnings. The travelable condition determining unit queries the travel record server to verify if vehicles have actually traveled along the predicted routes in the past, filtering out false collision risks before warnings are generated.
Solution Approach 2:
The travel record server acts as an intermediary that provides historical travel data to verify the validity of predicted collision scenarios. By mediating between the driving support device and the collision warning logic, it enables accurate assessment of whether vehicles can actually reach the predicted collision point.
2Measurement precision
If the driving support device checks travelable conditions using historical travel data, then the accuracy of collision prediction is improved, but the system complexity increases
Solution Approach 1:
The travel record server serves as an external intermediary system that handles the complexity of historical data storage and querying. The driving support device itself remains relatively simple, delegating the complex data management tasks to the server, thus achieving high prediction accuracy without significantly increasing onboard system complexity.
Solution Approach 2:
The system replaces complex real-time simulation of vehicle travel with a simpler query-based approach using historical travel records. Instead of mechanically simulating whether vehicles can reach collision points, the system substitutes this with a data lookup that checks if similar travel patterns have occurred before.
3Measurement precision
If the driving support device queries travel record server for every potential collision scenario, then the determination accuracy is improved, but the communication load and processing time increase
Solution Approach 1:
The system performs travelable condition determination only for collision scenarios that meet certain criteria, rather than querying the travel record server for every possible overlap. By selectively applying the detailed check only when necessary, it balances accuracy with processing efficiency.
Data Source
AI summary
A warning is not issued when there is not a history in which a host vehicle or an object vehicle (a recording target vehicle) have traveled from a current position of the host vehicle to a predicted collision point and a history in which the recording target vehicle has traveled from a current position of a collision-possible vehicle to the predicted collision point.