Systems, methods, and apparatuses are described for updating navigational map data. A routing request is received for routing data. A version compatibility matrix may be accessed that corresponds to the routing request. An analysis is performed of a cache database, a main database, and the version compatibility matrix. A number of version conflicts between the cache database and main database are identified based on the analysis. Using these version conflicts, one or more routes based on the routing request are generated.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method comprising: receiving a routing request for routing data; accessing a tile version compatibility matrix; performing, by a navigation device, an analysis of a first database, a second database, and the tile version compatibility matrix; identifying a number of version conflicts between the first and second databases based on the analysis; and generating, by the navigation device, a route based on the routing request and the number of version conflicts.
A navigation system updates map data by receiving a route request and accessing a tile version compatibility matrix. The system analyzes a cache database (faster access, potentially outdated), a main database (authoritative, but slower), and the version compatibility matrix to find version conflicts between the two databases. Based on these conflicts, the system generates a route that considers the data inconsistencies, ensuring reliable navigation even with outdated cache data.
2. The method of claim 1 , wherein when one or more version conflicts exist generating the route using the second database.
When generating a route and the navigation system identifies one or more version conflicts between the cache database and the main database, as determined by analyzing both databases against a tile version compatibility matrix, the route is generated using data from the main database. This prioritizes accuracy over speed by relying on the most up-to-date information when discrepancies exist.
3. The method of claim 1 , wherein when no version conflicts exist, generating the route using the first and second database.
When generating a route and the navigation system identifies no version conflicts between the cache database and the main database, as determined by analyzing both databases against a tile version compatibility matrix, the route is generated using data from both the cache and main databases. This potentially allows for faster route calculation by leveraging the cache when data consistency is confirmed.
4. The method of claim 1 , wherein identifying comprises: accessing tile data, wherein the tile data has version data, stored in the first and second database; comparing the version data to the tile version compatibility matrix; and determining version conflicts from the version data.
Identifying version conflicts between a cache database and a main database during route generation involves accessing tile data (map sections) with associated version data from both databases. The system compares the version data of corresponding tiles against a tile version compatibility matrix. Version conflicts are determined based on discrepancies found during this comparison, indicating potential inconsistencies in map data.
5. The method of claim 1 , wherein the first database, second database, and tile version compatibility matrix have tile data, and tile data corresponds to routing information for a region, city, state, or country, or a combination thereof.
The cache database, main database, and tile version compatibility matrix all contain tile data. Tile data represents routing information for a specific geographic area, such as a region, city, state, country, or a combination of these. Each tile includes the map information and version data relevant to that area, which the navigation system uses for route calculation and conflict resolution.
6. The method of claim 1 , wherein the tile version compatibility matrix for a first tile describes consistency of the first tile and at least one second tile.
The tile version compatibility matrix defines the consistency between different map tiles. Specifically, the entry for a first tile describes its compatibility with at least one other second tile. This means the matrix indicates whether the map data and routing information in the first tile is consistent with the data in the second tile, helping to ensure smooth transitions between map sections during navigation.
7. The method of claim 6 , further comprising: accessing a first set of version data for the at least one second tile stored in the tile version compatibility matrix for the first tile; comparing the first set of version data to a second set of version data stored in the second database; and determining a compatibility of the first and second set of version data.
To determine the compatibility between two map tiles, the system accesses a first set of version data for a second tile from the tile version compatibility matrix associated with a first tile. It then compares this first set of version data to a second set of version data stored in the main database for the same second tile. Based on the comparison, the system determines whether the two tiles are compatible, indicating data consistency for routing.
8. The method of claim 6 , wherein when the tile version compatibility matrix indicates the first tile and the second tile are consistent, the route extends from the first tile to the second tile.
If the tile version compatibility matrix indicates that a first tile and a second tile are consistent (i.e., their map data versions align), the generated route is allowed to extend seamlessly from the first tile to the second tile. This ensures that the route can smoothly transition between these map sections without encountering data inconsistencies.
9. The method of claim 6 , wherein when the tile version compatibility matrix indicates the first tile and the second tile are inconsistent, the route does not extend from the first tile to the second tile.
If the tile version compatibility matrix indicates that a first tile and a second tile are inconsistent (i.e., their map data versions do not align), the generated route is prevented from directly extending from the first tile to the second tile. This avoids routing through potentially conflicting or outdated map data, ensuring a more reliable navigation experience.
10. The method of claim 6 , wherein when the tile version compatibility matrix indicates the first tile and the second tile are inconsistent, the route is generated using the first and second database and compared against a generated route using the second database.
If the tile version compatibility matrix indicates that a first tile and a second tile are inconsistent, the navigation system generates a first route using both the cache and main databases, and compares it against a second route generated solely using the main database. This comparison helps determine the best route, potentially prioritizing accuracy by favoring the route based only on the main database when inconsistencies are detected.
11. The method of claim 1 , further comprising: providing the route to a display.
After generating a route that considers potential version conflicts between map tiles, the system provides the generated route to a display, such as a screen in a car or on a mobile device. This allows the user to visualize the route and receive turn-by-turn directions.
12. The method of claim 11 , wherein the first database tiles are a function of travel of the navigation device.
The tiles stored in the cache database are dynamically determined as a function of the navigation device's travel. This means the system prioritizes caching tiles that are relevant to the device's current location and recent travel history, optimizing performance by keeping frequently accessed map data readily available.
13. An apparatus comprising: at least one memory configured to store a version compatibility matrix; a processor configured to: receive a route request for routing data; access a version compatibility matrix from the at least one memory; perform an analysis of a cache database, a main database, and the version compatibility matrix; identify a number of version conflicts between the cache and main databases based on the analysis, wherein the number of version conflicts describes how many version differences are identified between tiles of the cache database and tiles of the main database; and generate a route based on the route request and the number of version conflicts.
A navigation apparatus includes memory storing a version compatibility matrix and a processor. The processor receives a route request and accesses the compatibility matrix. It analyzes a cache database, a main database, and the matrix to identify version conflicts. The number of conflicts indicates how many version differences exist between tiles in the cache and main databases. Based on these conflicts and the route request, the processor generates a route that considers data consistency.
14. The apparatus of claim 13 , wherein when one or more version conflicts exist generating the route using the main database, and wherein when no version conflicts exist generating the route using the cache and main databases.
An apparatus that generates a route: when one or more version conflicts exist between the cache database and the main database, as determined by analyzing both databases against a tile version compatibility matrix, the route is generated using data from the main database; when no version conflicts exist, the route is generated using data from both the cache and main databases.
15. The apparatus of claim 13 , wherein the version compatibility matrix for a first tile describes consistency of the first tile and at least one second tile.
In a navigation apparatus, the version compatibility matrix defines the consistency between different map tiles. Specifically, the entry for a first tile describes its compatibility with at least one other second tile. This means the matrix indicates whether the map data and routing information in the first tile is consistent with the data in the second tile, helping to ensure smooth transitions between map sections during navigation.
16. The apparatus of claim 15 , wherein the processor is configured to: access a first set of version data for the at least one second tile stored in the version compatibility matrix for the first tile; compare the first set of version data to a second set of version data stored in the main database; and determine a compatibility of the first and second set of version data.
To determine tile compatibility, the processor accesses a first set of version data for a second tile stored in the version compatibility matrix associated with a first tile. It compares this first set of version data to a second set of version data stored in the main database for the same second tile. Based on the comparison, the processor determines the compatibility of the first and second set of version data.
17. The apparatus of claim 16 , wherein when the version compatibility matrix indicates the first tile and the second tile are consistent, the route extends from the first tile to the second tile, and wherein when the version compatibility matrix indicates the first tile and the second tile are inconsistent, the route does not extend from the first tile to the second tile.
If the version compatibility matrix indicates that a first tile and a second tile are consistent, the generated route extends from the first tile to the second tile. Conversely, if the version compatibility matrix indicates that the first tile and the second tile are inconsistent, the route does not extend from the first tile to the second tile, avoiding potentially conflicting map data.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
June 17, 2015
March 14, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.