Map Tile Versioning for Bandwidth-Constrained Navigation Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern navigation systems face challenges in maintaining fresh and consistent map data, especially in highly automated driving applications, where data must be up-to-date and compatible across different geographic regions, and updating all tiles can be costly and time-consuming, especially when there is no internet connection.

Innovation Solution

The use of a compatibility matrix to determine which map tiles have changed and only download those tiles, employing a cache database to store new data and merge it with the main database when connected, ensuring consistency and freshness of data, and using a version compatibility matrix to identify compatible tile versions for routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all map tiles are updated to maintain data freshness, then data consistency is improved, but bandwidth usage and update time increase significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidbandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments map data into individual tiles with unique identifiers, allowing selective updating of only those tiles that have changed. Instead of updating all tiles, the system identifies and downloads only the specific tiles that contain updates, significantly reducing bandwidth consumption while maintaining data consistency for the areas that matter.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs partial updates by downloading only the necessary portion of map data (specific tiles that have changed) rather than performing a complete update of all tiles. This partial action approach maintains data freshness where needed while avoiding unnecessary bandwidth consumption for unchanged areas.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If all map tiles are updated to ensure data freshness, then data consistency is improved, but update time increases significantly

Engineering Contradiction:
Improvedata freshnessVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By segmenting map data into discrete tiles with version identifiers, the system can quickly identify which specific tiles need updating. This segmentation enables parallel downloading of multiple small tiles instead of downloading one large complete map update, significantly reducing total update time while ensuring data freshness for all necessary areas.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The server performs preliminary action by maintaining version information for all tiles and pre-identifying which tiles have changed. When a client requests an update, the server has already prepared the list of updated tiles, allowing the client to immediately download only what is necessary without performing a full update, thus reducing update time while maintaining data freshness.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If tile version checking is implemented to maintain data consistency, then routing reliability is improved, but system complexity increases

Engineering Contradiction:
Improverouting reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements preliminary action by pre-calculating and storing version compatibility information on the server. Before routing calculations are performed, the system checks tile versions and compatibility in advance, ensuring that only consistent tile combinations are used for routing. This preliminary version checking maintains routing reliability while keeping the actual routing algorithm relatively simple.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from version identifiers to automatically determine tile compatibility. When tiles are downloaded or cached, their version information is recorded and used as feedback to verify consistency before routing operations. This automated feedback mechanism ensures routing reliability without requiring complex manual verification processes.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3368861B1Tile versioning to improve usability of streamed navigation data
Publication Date: 2024.08.28 HERE GLOBAL BV
  • EP3368861B1 patent drawingFigure 1
  • EP3368861B1 patent drawingFigure 2
  • EP3368861B1 patent drawingFigure 3

AI summary

Systems, methods, and apparatuses are described for updating navigational map data. A routing request is received from a user or device. From the routing request, a first map tile and a second map tile are identified. A new version of the first map tile is identified, and a compatibility matrix for at least the first map tile is accessed. An analysis of the compatibility matrix is performed to determine whether objects of the new version of the first map tile are compatible with the second map tile.