Regional Gateway Tables for Navigational Database Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing navigational databases face impracticalities in storing and updating global gateway tables due to their large size and the high number of possible combinations of update regions, making it inefficient to manage and store all versions of the global gateway table for partial updates.
Innovation Solution
The solution involves creating a regional gateway table for each update region, which associates gateways with the region and other adjacent regions, allowing for partial updates without modifying the global index structure, and providing this information in a self-contained update package that can be used for route calculations without relying on the global gateway table.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a global gateway table is maintained to associate all gateways with update regions and tiles, then route calculation between regions is enabled, but the data size becomes large and storage becomes impractical when supporting all combinations of update regions
Solution Approach 1:
The global gateway table is segmented into multiple regional gateway tables, each associated with a specific update region. Each regional gateway table contains only the gateways relevant to that region, reducing the data size stored in each table while collectively maintaining comprehensive route calculation capability across all regions.
2Adaptability or versatility
If all versions of the global gateway table are stored to match every possible combination of update regions, then partial updating flexibility is improved, but the storage requirements become impractical
Solution Approach 1:
Instead of storing multiple versions of a global gateway table for different region combinations, the system stores a single version of each regional gateway table. The segmentation allows the system to flexibly combine regional tables as needed for partial updates, eliminating the need to pre-store all possible global table versions.
3Reliability
If SQL commands are used to update the global gateway table during incremental updates, then synchronization between the table and update regions is maintained, but the complexity of managing multiple table versions increases
Solution Approach 1:
The update process is segmented at the regional level rather than requiring global table updates. Each regional gateway table is updated independently using SQL commands during incremental updates, maintaining synchronization between regions and their corresponding gateway tables without the complexity of managing multiple global table versions.
Data Source
AI summary
A method for producing an update package for a navigational database comprises: —providing a first update region of the navigational database, and —providing a first gateway table of the first update region such that the first gateway table associates each gateway of the first update region with said first update region and with at least one other update region.