Lane Assignment Correction via GNSS Offset Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for assigning vehicles to lanes in lane-level traffic-based functions suffer from map matching errors due to changes in lane geometry and GNSS signal distortions, leading to inaccuracies in navigation and autonomous driving systems.
Innovation Solution
A method and system that determine lane-specific offsets using GNSS-based position data from probes to correct for lane geometry changes and GNSS signal reflections, enabling accurate lane assignments and reducing map matching errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If GNSS-based position data is used for lane assignment, then vehicle positioning is enabled, but map matching errors increase due to lane geometry changes and signal reflections
Solution Approach 1:
The patent introduces an intermediary processing system that receives GNSS position data and applies corrections based on stored lane geometry information and signal reflection models. This intermediary layer processes the raw GNSS data through multiple correction steps before outputting the final lane assignment, thereby mediating between the imperfect GNSS measurements and the required accurate lane identification
Solution Approach 2:
The system performs preliminary actions by pre-storing lane geometry information, reflection coefficients, and correction parameters in a database before actual lane assignment operations. These pre-computed correction models and geometric data are prepared in advance to quickly compensate for known sources of error during real-time positioning
2Measurement precision
If lane-level functions are implemented, then navigation precision is improved, but system complexity increases due to additional processing requirements
Solution Approach 1:
The patent segments the lane assignment problem into distinct processing modules: GNSS position reception, lane geometry lookup, reflection correction application, and final lane determination. Each module handles a specific aspect of the correction process independently, making the overall complex system more manageable and maintainable through functional decomposition
Solution Approach 2:
An intermediary processing system is introduced that acts as a bridge between simple GNSS reception and complex lane-level navigation functions. This intermediary layer encapsulates the complexity of corrections and transformations, providing a simplified interface while maintaining high precision through multiple internal processing steps
3Measurement precision
If probe data from multiple probes is processed, then lane-specific data accuracy improves, but data processing time increases
Solution Approach 1:
The system performs preliminary actions by pre-aggregating and storing lane-specific data from probe data in advance. Correction parameters, lane geometry information, and statistical lane characteristics are computed and stored before actual lane assignment queries, enabling fast retrieval and application during real-time operations without reprocessing raw probe data
Solution Approach 2:
The patent applies partial correction actions by selectively applying corrections based on the specific conditions detected. Not all probes require the full suite of corrections - the system applies only the necessary corrections based on probe location, lane configuration, and detected error sources, reducing unnecessary processing while maintaining accuracy where needed
Data Source
Figure 1~2
Figure 3~4
Figure 5~7
AI summary
To improve prove lane assignment for performing at least one lane level traffic-based function, a processing system (20) processes probe data (48) from a plurality of probes travelling on a navigable network. The probe data (48) comprises global navigation satellite system (GNSS)-based position data. The processing system (20) determines a lane-specific offset in a direction transverse to an extension direction of the segment based at least on the probe data (48) from probes on the segment.