Navigation Device Map Correction Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing navigation device map data is often outdated due to the lengthy process of reporting and verifying errors, which can take months to years, and does not allow for immediate corrections to be applied directly on the device.
Innovation Solution
A method for users to load, select, implement, and store map alterations on a navigation device, enabling immediate corrections to be made and shared, bypassing the need for external verification, with features such as user interfaces for creating, viewing, and sharing corrections, and the ability to associate corrections with transportation types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If map errors are reported through external verification processes, then correction accuracy is improved, but update time is significantly increased (months to years)
Solution Approach 1:
The patent segments the map correction process into two independent parts: (1) local on-device correction application, and (2) optional external verification. This allows corrections to be applied immediately on the device without waiting for external verification, while still allowing verification to occur separately for accuracy-critical corrections.
Solution Approach 2:
The patent enables preliminary action by allowing users to apply map corrections directly on their devices immediately upon receiving correction data, without waiting for the traditional external verification process to complete. This preliminary correction application happens in advance of formal verification, reducing the overall update time.
2Reliability
If centralized map verification processes are used, then data reliability is improved, but device productivity is reduced due to waiting for external updates
Solution Approach 1:
The patent divides the correction workflow into independent segments that can execute in parallel: local correction application on devices and centralized verification processes. This segmentation allows devices to remain productive with local corrections while verification proceeds separately, maintaining both reliability and productivity.
Solution Approach 2:
The patent implements feedback mechanisms where correction results from multiple devices are aggregated and fed back to the verification system. This allows the system to learn from actual field usage and improve verification efficiency, maintaining data reliability while reducing overall update cycles.
3Loss of information
If manual error reporting by users is used, then map completeness is improved, but processing complexity increases due to free text format verification
Solution Approach 1:
The patent enables self-service by allowing devices to automatically process and apply structured correction data without requiring manual verification of free-text reports. Users can directly contribute corrections in standardized formats that devices can process automatically, reducing processing complexity while maintaining map completeness.
Solution Approach 2:
The patent changes the parameter format of user submissions from unstructured free text to structured correction data with standardized parameters. This transformation enables automated processing by devices, reducing the complexity of verification while capturing complete map information.
4Measurement precision
If frequent map updates are implemented, then navigation accuracy is improved, but device memory requirements increase
Solution Approach 1:
The patent extracts only the essential correction data needed for navigation accuracy from complete map updates. Instead of storing entire updated maps, devices receive and store only the differential correction parameters, significantly reducing memory requirements while maintaining navigation accuracy.
Solution Approach 2:
The patent segments map data into base map layers and incremental correction layers. Devices store the base map once and apply multiple correction segments as needed, allowing frequent updates without proportionally increasing total memory usage.
Data Source
AI summary
An end-user can input a correction to a map error, directly on the device. The device is then able to use the correction without external processing of the correction. Hence, it is no longer necessary for an end-user to simply report errors to the map vendor over a web link, then wait for that map vendor to verify the error, update its maps and finally supply the end-user with updates—a cycle that can take months and sometimes years to complete. Instead, the navigation device can use the correction immediately. End-users can also share corrections with other end-users and also with a shared remote server that aggregates, validates and distributes correction.