Page Server for Navigation Data

• US 20120036150A1
• Filed: 08/02/2011
• Published: 02/09/2012
• Est. Priority Date: 08/06/2010
• Status: Active Grant

• Current Assignee: HERE Global B.V. (Nokia Corporation)
• Original Assignee: Navteq North America LLC (Nokia Corporation)
• Inventors: Richter, Jan, Pfeifle, Martin, Barthel, Alexander, Kaiser, Christof, Skvarenina, Peter
• Granted Patent: US 8,566,346 B2
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G01C 21/3896 Transmission of map data from central databases
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: H04L 67/01 Protocols

Abstract

A page server and method of using the page server is described. The page server stores versioned pages. The pages, which are equally sized data chunks, can be stored with identifiers and version data in a relational database, in separate files, or in a single file where pages are concatenated. The page server may be accessed via SQL, a web interface, a proprietary key/value/version interface on top of TCP/IP, or other method. The page server facilitates incremental updates.

Claims

1. A page server for updating database pages, comprising:

a data store that stores pages of data and associated version information, wherein the pages have an equal data size, and wherein the pages include data of one or more different data types; and

an interface that receives requests including version information from a client, retrieves pages from the data store responsive to the version information, and transmits the retrieved pages to the client.

2. The page server of claim 1, wherein the data store stores the pages of data and the associated version information in a relational database.

3. The page server of claim 1, wherein the data store stores the pages of data and the associated version information as separate files.

4. The page server of claim 1, wherein the data store stores the pages of data and the associated version information as concatenated pages within a single file.

5. The page server of claim 1, wherein the data store stores a binary difference between a current page and a previous version of the current page.

6. The page server of claim 1, wherein the data store stores compressed pages.

7. The page server of claim 1, wherein the client accesses the page server using SQL.

8. The page server of claim 1, wherein the client accesses the page server using a web interface.

9. The page server of claim 1, wherein the client accesses the page server using a proprietary key/value/version interface on top of TCP/IP.

10. The page server of claim 1, wherein an implementation of the interface stores pages in a database system.

11. The page server of claim 1, wherein the data is digital map data.

12. The page server of claim 1, wherein the data is music data.

13. A method for updating pages on a client device, comprising:

at the client device, receiving a request for data from an application;

transforming the request into a set of page requests, wherein the page requests include version information;

sending the page requests to a page server that stores pages of data and associated version information;

receiving pages from the page server, wherein the pages have an equal data size, and wherein the pages include data of one or more different data types;

replacing the pages stored in the client device with the pages received from the page server; and

providing data from the new pages to the application requesting the data.

14. The method of claim 13, wherein the client device is a hybrid navigation system.

15. The method of claim 14, further comprising determining whether the requested data is locally available prior to sending the page request to the page server and sending the page request only if the data is not locally available.

16. The method of claim 14, wherein the hybrid navigation system selectively pre-installs pages by sending page requests to the page server.

17. The method of claim 13, further comprising receiving a list of updated pages and retrieving the pages when the application needs the pages.

18. A client device that can access a page server for updating, versioning, and synchronization a client database, comprising:

a client database; and

a page access module that is implemented as a virtual file system layer, wherein the page access module receives requests for data from an application, transforms the data requests to page requests that include version information, sends the page requests to a page server instead of the client database, and stores pages received from the page server in the client database.

19. The client device of claim 18, wherein the version information includes a file incremental transaction identifier that identifies a number of times the file has been changed.

20. The client device of claim 18, wherein the version information includes a file base version identifier that identifies when a file was originally created.