Navigation Device Database Block-Level Map Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing navigation device database update methods face challenges such as significant data transfer requirements, complexity in ensuring consistency across map versions, and inefficiencies in handling repeated navigation tasks, especially in areas with poor data connections.

Innovation Solution

A method where a navigation device selectively downloads and stores only the necessary data blocks for a specific navigation task from a base digital map version, allowing for incremental updates without modifying the base version, and reusing previously downloaded data for subsequent tasks, using a block-level approach to manage different map versions and optimize data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If incremental update information is transferred to update the map database, then the database can be updated with recent changes, but the data transfer amount becomes very significant

Engineering Contradiction:
Improvedatabase update accuracyVSAvoiddata transfer amount
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the map database into multiple storage blocks organized in a hierarchical structure. Instead of transferring entire map versions or large incremental updates, only specific storage blocks containing required navigation data are transferred. This segmentation enables selective data transfer, significantly reducing the overall data transfer amount while maintaining update accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts and transfers only the necessary storage blocks containing specific navigation data required for the current task, rather than transferring complete map versions or all incremental updates. This extraction approach removes unnecessary data from the transfer process, reducing data transfer volume while preserving essential update information.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If map data is re-compiled using transferred incremental update information, then the database reflects recent changes, but the compilation process becomes complex and error-prone

Engineering Contradiction:
Improvedatabase consistencyVSAvoidcompilation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-compiling and organizing map data into structured storage blocks at the server side before transfer. The storage blocks are pre-processed with proper indexing and metadata, so that when transferred to the navigation device, they can be directly integrated without complex on-device compilation. This shifts the compilation complexity from the client device to the server, reducing errors and simplifying the client-side process.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If on-line navigation is performed with a central server, then navigation tasks can be executed remotely, but data transfer amounts add up significantly with repeated tasks

Engineering Contradiction:
Improvenavigation task executionVSAvoidcumulative data transfer
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent implements local quality by caching frequently accessed storage blocks locally in the navigation device after their first transfer from the server. When the same navigation tasks are repeated, the device uses the locally cached storage blocks instead of re-transferring data from the server. This creates a hybrid approach where critical data is locally available for immediate use, reducing cumulative data transfer while maintaining on-line navigation capabilities.

Inventive Principle:
Principle #3Local quality

4Reliability

If complete map versions are transferred for updates, then the database is fully updated, but the transfer time becomes unacceptable without high-speed network access

Engineering Contradiction:
Improveupdate completenessVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments complete map versions into smaller storage blocks that can be transferred incrementally. Instead of requiring full map version transfers that demand high-speed networks and long transfer times, the system transfers only the necessary storage blocks containing required navigation data. This segmentation enables faster, more flexible updates that can proceed over standard network connections without unacceptable delays.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP2543963B1Method of updating a database of a navigation device and navigation device associated thereto
Publication Date: 2020.05.13 HARMAN BECKER AUTOMOTIVE SYST GMBH
  • EP2543963B1 patent drawingFigure 1~2
  • EP2543963B1 patent drawingFigure 3~5
  • EP2543963B1 patent drawingFigure 6

AI summary

To update a database (3) of a navigation device (1) which stores at least a base version (6) of a digital map, versions (6-8) of the digital map which are available locally in the database (3) or remotely from the navigation device (1) are identified. To execute the navigation task, a version (7, 8) of the digital map is selected for execution of the navigation task. Data from a sub-set of storage blocks in which the selected version is stored is required to execute the navigation task. Depending on whether all storage blocks of the sub-set are already stored locally in the database (3), data stored in storage blocks of the sub-set which are not yet stored locally in the database (3) are downloaded via a wireless interface. The downloaded data are stored in the database (3) without modifying the base version (6) of the digital map.