Road Link Identifier Correlation for Map Version Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Digital maps face issues with compatibility and data exchange between different map versions due to incompatible road link identifiers, leading to obsolete maps and navigation errors.
Innovation Solution
The use of an XOR function to correlate road link identifiers between different map versions, allowing for the translation of identifiers from one version to another, ensuring compatibility and enabling seamless data exchange and route guidance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If digital maps are updated frequently to maintain accuracy, then map data currency is improved, but compatibility between map versions deteriorates
Solution Approach 1:
The system performs preliminary actions by generating and storing multiple map versions with incremental updates before compatibility issues arise. Route requests are processed against historical map versions, allowing the system to proactively handle version transitions and maintain compatibility without waiting for conflicts to occur.
Solution Approach 2:
The system introduces an intermediary compatibility layer that translates route requests between different map versions. This intermediary mechanism allows seamless communication between clients using older map versions and servers using newer map versions, resolving the compatibility conflict without sacrificing update frequency.
2Measurement precision
If map updates are implemented regularly to reflect infrastructure changes, then navigation accuracy is improved, but data exchange compatibility between versions worsens
Solution Approach 1:
The system implements a universal route request processing mechanism that can handle multiple map versions simultaneously. The route request processor is designed to work with any map version, allowing the system to maintain high navigation accuracy with frequent updates while preserving data exchange compatibility across all versions through a unified interface.
3Reliability
If road link identifiers are changed in newer map versions to reflect updates, then map accuracy is improved, but compatibility with older map versions deteriorates
Solution Approach 1:
The system implements dynamic version handling where the route request processor can adapt to different map versions based on the client's capabilities. When processing route requests, the system dynamically selects the appropriate map version and identifier scheme, allowing accurate routing with updated identifiers while maintaining ease of operation through automatic adaptation to the client's map version.
Data Source
AI summary
Provided herein is a method of generating and communicating map version agnostic road identifiers. Methods may include: providing an indication of a route request between an origin and a destination; receiving a list of road link identifiers in response to the route request; in response to the first road link identifier not corresponding to a road link identifier of a network of road link identifiers: applying an XOR function to the first road link identifier and a subsequent road link identifier in the list of road link identifiers; in response to a result of the XOR function applied to the first road link identifier and the subsequent identifier corresponding with a road link identifier of the network of road link identifiers, adding the road link identifier of the network of road link identifiers to the route.