Incremental Navigation Database Testing via Consistency Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Incremental updates to geographic map databases pose a risk of introducing inconsistencies, which can lead to system malfunctions, especially when replacing only a portion of the database, and are time-consuming and costly when performing complete replacements.

Innovation Solution

A testing procedure is implemented that includes generating a test script with a consistency check algorithm for updated map tiles, allowing for the validation of references before committing the update, thereby ensuring the integrity of the database and reducing the risk of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If incremental update of map database is performed, then update time and cost are reduced, but data consistency and reliability deteriorate

Engineering Contradiction:
Improveupdate timeVSAvoiddata consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs preliminary consistency checks on the incremental update package before applying it to the map database. The consistency check algorithm validates that all references in the update package point to valid objects in the base version, preventing inconsistent data from being merged. This preliminary validation ensures reliability is maintained while still allowing incremental updates to reduce time and cost.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If complete replacement of map database is performed, then data consistency is ensured, but update time and cost increase

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

Solution Approach 1:

The update process is segmented into two parts: a base version that remains unchanged and an incremental update package that contains only the changes. Instead of replacing the entire database, the system applies only the segmented incremental changes after validating them for consistency. This segmentation maintains data consistency while significantly reducing update time and cost compared to complete replacement.

Inventive Principle:
Principle #1Segmentation

3Productivity

If incremental update is performed without testing, then update speed is improved, but system functionality and reliability worsen

Engineering Contradiction:
Improveupdate speedVSAvoidsystem functionality
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The incremental update package includes self-contained consistency check algorithms that automatically validate the update against the base version without requiring external testing. The update package performs its own verification, checking that all references are valid and consistent with the base data. This self-service validation maintains update speed while ensuring system functionality and reliability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9075822B2Incremental testing of a navigation database
Publication Date: 2015.07.07 HERE GLOBAL BV
  • US9075822B2 patent drawing
  • US9075822B2 patent drawing
  • US9075822B2 patent drawing

AI summary

A navigation system utilizes a testing package tailor made for an incremental update to a map database. An incorrect incremental update may corrupt a navigation database. Testing an incrementally updated database after updating allows a corrupted database to be detected before the corrupted database is used by the map database system. Map tiles associated with a list of recompiled objects are used to populate a table. A test script is created from the list map tiles and, when executed, checks the validity of references in the map database associated with the map tiles. The test script generates a return value that indicates whether errors occurred, the type of the errors, the quantity of errors, or any combination thereof. The navigation system analyzes the errors and determines whether to finalize or roll back the update.