Map Version Agnostic Route Generation via XOR Link Correlation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Digital maps face issues with compatibility and data exchange between different versions, leading to obsolete maps and inefficient route communication due to incompatible road segment identifiers, which hinders navigation and route guidance across varying map formats.

Innovation Solution

The implementation of a method using an XOR function to correlate and translate road link identifiers between different map versions, allowing for the generation and communication of low bandwidth map format agnostic routes, ensuring compatibility and reducing the need for identical map versions between servers and clients.

Engineering Contradictions & Design Principles

VSEngineering 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

Engineering Contradiction:

Improvemap data currencyVSAvoidmap version compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the route data into individual road link identifiers that can be independently correlated between map versions. By breaking down the route into discrete segments with unique identifiers, the system can match and correlate these segments across different map versions without requiring complete version compatibility, thus resolving the contradiction between frequent updates and version compatibility.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary correlation system that uses unique road link identifiers as mediators between different map versions. These identifiers serve as a common language that allows routes generated from newer map versions to be accurately represented on older map versions without direct version compatibility, enabling frequent updates while maintaining cross-version functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Measurement precision

If complete route data is transmitted from server to client, then route communication accuracy is improved, but bandwidth consumption increases

Engineering Contradiction:

Improveroute communication accuracyVSAvoidbandwidth consumption

Core Design Contradiction:

Measurement precisionVSLoss of energy

Solution Approach 1:

The patent extracts only the essential route information in the form of unique road link identifiers from the complete route data and transmits only these extracted elements from server to client. This extraction approach maintains route communication accuracy by preserving the essential path information while dramatically reducing bandwidth consumption by eliminating redundant geographic and descriptive data.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses a copying mechanism where the client reconstructs the complete route representation locally by copying and assembling the received road link identifiers against its stored map data. This allows the client to generate an accurate route visualization and navigation guidance without receiving the complete original route data, thereby reducing bandwidth usage while maintaining route accuracy.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If identical map versions are required between server and client, then data compatibility is improved, but system complexity and update synchronization worsen

Engineering Contradiction:

Improvedata compatibilityVSAvoidversion synchronization complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal road link identifier system that functions across multiple map versions simultaneously. These identifiers are designed to be version-agnostic, allowing the same identifier to represent the same road link across different map versions. This universality enables data compatibility without requiring identical map versions, eliminating the need for complex version synchronization mechanisms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP3919861B1Method, apparatus, and computer program product for generating and communicating low bandwidth map version agnostic routes

Publication Date: 2024.11.13 HERE GLOBAL BV

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 one or more intermediate segment anchor points and encoded server-provided route fragments for a requested route between an origin and a destination; identifying one or more intermediate segments corresponding to the one or more intermediate segment anchor points; generating a route between the origin and the destination, the route including the one or more intermediate segments and a plurality of client-generated route fragments; encoding each client-generated route fragment by application of an XOR algorithm to the client-generated route fragment road segments; comparing the encoded client-generated route fragments to the encoded server-provided route fragments; and providing navigational assistance for traveling along the route in response to the encoded client-generated route fragments corresponding with the encoded server-provided route fragments.