XOR Encoded Route Fragments for Map Version Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Digital maps face issues with compatibility and data exchange between different map versions, leading to obsolete maps and inefficient route communication due to incompatible road segment identifiers, which results in increased bandwidth usage and processing demands.
Innovation Solution
The implementation of a method using XOR logic to correlate and translate road link identifiers between different map versions, allowing for the generation and communication of low-bandwidth, map-format-agnostic routes by employing XOR stable link identifiers and encoding routes with midpoints and fingerprints to reduce data transmission.
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 issues between different map versions worsen
Solution Approach 1:
The patent segments the route data into two distinct parts: version-independent geometric information (waypoints, midpoints, anchor points) and version-specific identifier information (road link IDs). This segmentation allows the geometric core to remain compatible across map versions while only the identifier layer needs updating, resolving the contradiction between currency and compatibility.
Solution Approach 2:
The patent introduces an intermediary translation layer that converts between different map version identifiers using a correspondence table. This intermediary mechanism enables routes generated with new map versions to be correctly interpreted by clients using older map versions, maintaining compatibility while allowing frequent server-side updates.
2Measurement precision
If complete route data is transmitted to ensure accuracy, then route precision is improved, but bandwidth consumption worsens
Solution Approach 1:
The patent extracts only the essential geometric components needed for route rendering (waypoints, midpoints, anchor points) and transmits them, while omitting redundant complete route data. The client reconstructs the full route using these extracted key points and its local map data, significantly reducing bandwidth consumption while preserving route accuracy.
Solution Approach 2:
Instead of transmitting complete route data, the patent transmits a simplified copy containing only critical geometric information (waypoints, midpoints, anchor points). The client then uses its local map data to reconstruct the complete route, creating a local copy that is both bandwidth-efficient and accurate.
3Measurement precision
If detailed route information is communicated to maintain accuracy, then route fidelity is improved, but data transmission complexity worsens
Solution Approach 1:
The patent segments route communication into two phases: server transmits simplified geometric data (waypoints, midpoints, anchor points), and client performs local reconstruction using its map data. This segmentation reduces transmission complexity while maintaining route fidelity through the client-side reconstruction process.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Provided herein is a method of generating low bandwidth map format agnostic routes between origins and destinations for route communication between different map formats or versions using reduced bandwidth. Methods may include: receiving an indication of a route request between an origin and a destination; generating a route between the origin starting road segment and the destination target road segment, the route including a plurality of road segments; identifying one or more intermediate segments from the plurality of road segments, each intermediate segment having an anchor point; generating a plurality of route fragments from the route; encoding each route fragment by applying an XOR algorithm to identifiers of route fragment road segments of a respective route fragment; and providing the encoded route fragments and one or more anchor points of the one or more intermediate segments in response to the route request.