Vehicle Trajectory Cross-Checking for Collision-Free Autonomous Driving
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for semi-automated or automated vehicles do not effectively verify the planar trajectory against other vehicles, leading to potential collisions and unreliable vehicle control.
Innovation Solution
A method and system for checking the planar trajectory of a semi-automated or automated vehicle by transmitting or querying the planned trajectory to/from other vehicles, using communication interfaces, and verifying it against their trajectories, with uncertainty and confidence measures to determine the need for verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the planned trajectory is verified against all other vehicles in the vicinity, then the collision-free operation is improved, but the computational effort and data traffic increase
Solution Approach 1:
The patent applies parameter changes by dynamically adjusting the verification threshold (uncertainty or confidence level) based on traffic density and vehicle proximity. When traffic is dense or vehicles are close, verification is triggered more frequently; when traffic is sparse, verification is reduced. This resolves the contradiction by making the verification intensity adaptive rather than static, ensuring collision safety while avoiding unnecessary computational overhead in low-risk scenarios.
Solution Approach 2:
The patent implements partial verification by selectively checking trajectories only when uncertainty thresholds are exceeded or confidence levels fall below thresholds, rather than continuously verifying all trajectories. This partial action approach maintains collision safety by verifying only when necessary, thereby reducing overall computational effort and data traffic while preserving essential reliability.
2Reliability
If the planned trajectory is verified against all other vehicles in the vicinity, then the collision-free operation is improved, but the data traffic increases
Solution Approach 1:
The patent reduces data traffic by dynamically changing the verification parameter thresholds based on traffic conditions. By adjusting uncertainty and confidence thresholds according to vehicle density and proximity, the system triggers verification messages only when necessary, thereby maintaining collision safety while significantly reducing the quantity of verification data transmitted across the network.
Solution Approach 2:
The system performs partial verification by sending trajectory verification requests only when specific conditions are met (uncertainty threshold exceeded or confidence threshold not met), rather than continuously broadcasting verification messages. This partial action reduces data traffic while maintaining sufficient verification coverage to ensure collision-free operation.
3Reliability
If continuous verification of the planned trajectory is performed, then the reliability of vehicle control is improved, but the computational resources are consumed continuously
Solution Approach 1:
The patent implements periodic verification triggered by specific events or conditions rather than continuous verification. Verification is performed periodically when uncertainty thresholds are exceeded, confidence levels drop below thresholds, or at scheduled intervals. This periodic approach maintains vehicle control reliability by verifying trajectories at critical moments while conserving computational resources by avoiding unnecessary continuous verification.
Solution Approach 2:
The system changes verification frequency based on dynamic parameters such as vehicle proximity, relative speed, and traffic density. When parameters indicate high risk, verification frequency increases; when parameters indicate low risk, verification frequency decreases. This adaptive parameter-based approach ensures reliability when needed while reducing computational resource consumption during normal operation.
Data Source
Figure 1
Figure 2~3
AI summary
The invention relates to a method for checking a planned trajectory (10) of a partly autonomous or autonomous vehicle (50), i) wherein a planned trajectory (10) of the vehicle (50) is transmitted to at least one other vehicle (60) in the surrounding area of the vehicle (50), wherein the transmitted planned trajectory (10) is checked in the at least one other vehicle (60) on the basis of a planned trajectory (11) of the at least one other vehicle (60), and wherein a result of the check (20) is transmitted to the vehicle (50), and/or ii) wherein a planned trajectory (11) and a current position (12) of at least one other vehicle (60) in the surrounding area of the vehicle (50) is inquired by the vehicle (50), wherein the planned trajectory (10) of the vehicle (50) is checked in the vehicle (50) on the basis of the transmitted planned trajectory (11) of the other vehicle (50). The invention also relates to a system (100).