Version management for incrementally compiled map data

• US 10,002,156 B2
• Filed: 03/16/2015
• Issued: 06/19/2018
• Est. Priority Date: 03/16/2015
• Status: Active Grant

• Current Assignee: HERE Global B.V. (HERE Holding Corporation)
• Original Assignee: HERE Global B.V. (HERE Holding Corporation)
• Inventors: Lublinsky, Boris, Zhukov, Vladimir
• Primary Examiner(s): Stevens, Robert
• Application Number:
  US14/658,455
• Publication Number:
  US 20160275131A1
• Time in Patent Office: 1,191 Days
• Field of Search: 707695
• CPC Class Codes: G01C 21/3667 Display of a road map G01C21/3614 takes precedence; guidance using 3D or perspective road maps G01C21/3635
• CPC Class Codes: G01C 21/387 Organisation of map data, e.g. version management or database structures
• CPC Class Codes: G01C 21/3881 Tile-based structures
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06T 1/60 Memory management

Abstract

A map developer may maintain multiple versions of a geographic database including map tile data. Map tile data may be organized according to a versioning schema. A server, or an endpoint device in communication with the server, may receive a request for map data for a tile associated with a tile identifier and access a tile compatibility table with the tile identifier. The tile compatible table includes multiple tile version identifiers for the tile indexed by global map version identifiers and returns a compatible tile identifier and a compatible map version in response to the request for map data.

Claims

1. A method comprising:

receiving a request for map data for a tile associated with a first tile identifier;

accessing, by a processor, a tile compatibility table with the first tile identifier, wherein the tile compatible table includes a plurality of tile version identifiers for the tile indexed by a single monotonically ascending map version number;

receiving a second tile identifier from the tile compatibility table;

receiving data indicative of a compatible map version from the tile compatibility table, the data indicative of the compatible map version includes a first range of compatible map version identifiers from a first minimum chronological version identifier to a first maximum chronological version identifier for the first tile identifier,

the data indicative of a compatible map version includes a second range of compatible map version identifiers from a second minimum chronological version identifier to a second maximum chronological version identifier for the second tile identifier,

and providing the first range of compatible map version identifiers from the first minimum chronological version identifier to the first maximum chronological version identifier for the first tile identifier and the second range of compatible map version identifiers from the second minimum chronological version identifier to the second maximum chronological version identifier for the second tile identifier, in response to the request for map data.

2. The method of claim 1, further comprising:

assigning the single monotonically ascending map version number to a map starting from an initial value;

incrementing the map version number in response to an update to any tile or set of tiles of the map; and

assigning the map tile a version corresponding to the single monotonically ascending map version number for the map when the map tile is updated or created.

3. The method of claim 1, wherein the request for map data includes a vertical layer code.

4. The method of claim 1, wherein the request for map data includes geographic coordinates for a geographic area, the method further comprising:

selecting the tile version identifier based on the geographic area.

5. The method of claim 4, wherein a plurality of tile version identifiers are selected based on the geographic area.

6. The method of claim 1, wherein a route is selected based on the compatible tile identifier and the compatible map version.

7. The method of claim 1, further comprising:

reading the tile identifier from a versioning schema of the map tile; and

receiving a map update request based on the compatible map version derived from the tile identifier.

8. The method of claim 1, further comprising:

receiving a command declining a map update based on the compatible version.

9. An apparatus comprising:

at least one processor; and

at least one memory including computer program code for one or more programs;

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least perform;

receive a request for map data for a tile indexed by a first tile version identifier;

access a tile compatibility table with the tile version identifier, wherein the tile compatible table includes a plurality of tile version identifiers for the tile indexed by global map version identifiers;

receive a second tile version from the tile compatibility table;

receive data indicative of a compatible map version from the tile compatibility table, the data indicative of the compatible map version includes a first range of compatible map version identifiers from a first minimum chronological version identifier to a first maximum chronological version identifier for the first tile identifier,

the data indicative of a compatible map version includes a second range of compatible map version identifiers from a second minimum chronological version identifier to a second maximum chronological version identifier for the second tile identifier; and

send the second tile version and the compatible map version in response to the request for map data.

10. A method comprising:

receiving a request for map data for a tile indexed by a tile identifier;

accessing, by a processor, a tile compatibility table with the tile identifier, wherein the tile compatible table includes a plurality of tile version identifiers for the tile indexed by global map version identifiers;

receiving a range of compatible global map version identifiers from the tile compatibility table;

accessing a stored version of the tile from memory;

performing a comparison of the range of compatible global map version identifiers to the stored version; and

providing the requested map data based on the comparison.

11. The method of claim 10, wherein providing the requested map data based on the comparison comprises:

generating a route from an origin to a destination when the comparison indicates that the stored version of the tile is in the range of compatible global map version identifiers.

12. The method of claim 11, further comprising:

generating a request for a map update when the comparison indicates that the stored version of the tile is out of the range of compatible global map version identifiers.

13. The method of claim 10, wherein providing the requested map data based on the comparison comprises:

declining a map update option when the comparison indicates that the stored version of the tile is in the range of compatible global map version identifiers.

14. The method of claim 10, wherein providing the requested map data based on the comparison comprises:

determining, based on the comparison, whether a cached map tile is sufficient to provide the requested map data.

15. The method of claim 10, wherein the range of compatible global map version identifiers includes a minimum chronological version identifier and a maximum chronological version identifier.

16. The method of claim 10, further comprising:

calculating a route from an origin to a destination, wherein the tile identifier corresponds to a first tile from the route and the stored version corresponds to a second tile from the route.

17. The method of claim 16, further comprising:

calculating an alternative route to the destination when the comparison indicates that the stored version is outside of the range of compatible global map version identifiers.

18. An apparatus comprising:

at least one processor; and

at least one memory including computer program code for one or more programs;

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least perform;

receive a request for map data for a tile indexed by a tile identifier;

access a tile compatibility table with the tile identifier, wherein the tile compatible table includes a plurality of tile version identifiers for the tile labeled by a single numbering scheme;

receive a range of compatible global map version identifiers from the tile compatibility table;

access a stored version of the tile from memory;

perform a comparison of the range of compatible global map version identifiers to the stored version; and

providing a navigation function based on the comparison.

19. The apparatus of claim 18, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least perform:

calculate a route based on the comparison.

20. A method comprising:

assigning a single monotonically ascending map version number to a map starting from an initial value;

incrementing the single monotonically ascending map version number in response to an update to any tile or set of tiles of the map;

assigning the map tile a version corresponding to the single monotonically ascending map version number for the map when the map tile is updated or created;

receiving a request for map data with a tile identifier;

accessing, by a processor, a tile compatibility table with the tile identifier, wherein the tile compatibility table includes a plurality of tile version identifiers for the tile indexed by the single monotonically ascending map version identifiers;

receiving a range of compatible map version identifiers for the tile identifier from the tile compatibility table, the range of compatible map version identifiers indexed by the single monotonically ascending map version number; and

providing the map data according to the range of compatible map version identifiers from the tile compatibility table.