EP1251335A2 - Navigation system with distributed computing architecture - Google Patents
Navigation system with distributed computing architecture Download PDFInfo
- Publication number
- EP1251335A2 EP1251335A2 EP02252660A EP02252660A EP1251335A2 EP 1251335 A2 EP1251335 A2 EP 1251335A2 EP 02252660 A EP02252660 A EP 02252660A EP 02252660 A EP02252660 A EP 02252660A EP 1251335 A2 EP1251335 A2 EP 1251335A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- parcels
- geographic
- server
- computing platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3863—Structures of map data
- G01C21/387—Organisation of map data, e.g. version management or database structures
- G01C21/3881—Tile-based structures
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3885—Transmission of map data to client devices; Reception of map data by client devices
- G01C21/3889—Transmission of selected map data, e.g. depending on route
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3885—Transmission of map data to client devices; Reception of map data by client devices
- G01C21/3896—Transmission of map data from central databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/29—Geographical information databases
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
Landscapes
- Engineering & Computer Science (AREA)
- Remote Sensing (AREA)
- Radar, Positioning & Navigation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Automation & Control Theory (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Navigation (AREA)
- Traffic Control Systems (AREA)
- Instructional Devices (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Telephonic Communication Services (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
- The present invention relates to a system that provides navigation-related services and data to end users throughout a geographic region, and more particularly, the present invention relates to a system that includes a centrally-located server that has a geographic database associated therewith and that provides navigation-related services and data to end users' computing platforms that are located throughout a serviced geographic region.
- Navigation systems provide various useful features, such as calculating routes to desired destinations, providing guidance for following calculated routes, displaying maps, and so on. There are various computer architectures for navigation systems that deliver navigation-related and map-related features. In one type of architecture for a navigation system, end users (such as vehicle drivers) have local navigation system units. These end users' local navigation system units obtain geographic data from a remotely-located geographic database. The remotely-located geographic database contains a relatively large amount of geographic data. A server associated with the remotely-located geographic database handles requests for navigation-related or map-related data from end users' local navigation system units. When an end user's local navigation system unit requests data, the server accesses the geographic database associated therewith to obtain the necessary data to respond to the request and then sends the data to the requesting end user's local navigation system unit.
- This type of navigation system architecture provides several advantages. One advantage relates to providing updated geographic data. There is a continuing need to update the geographic data used by a navigation system. For example, new streets are built, road construction closes roads, detours are established, new businesses open, posted speed limits change, new turn restrictions are established at intersections, streets are renamed, and so on. These kinds of changes can affect travel through a geographic region. Accordingly, the geographic data used by a navigation system should be updated on a regular basis in order to accurately reflect changes in the represented geographic features. A computer architecture in which individual local navigation system units obtain geographic data from a single geographic database affords an advantage with respect to the updating of the geographic data. With a computer architecture in which individual local navigation system units obtain data from a single geographic database associated with a central server, updates need to be applied only to the central database.
- Although there are advantages associated with a navigation system architecture in which individual navigation system units obtain data from a single geographic database associated with a central server, there are considerations that need to be addressed. One consideration relates to providing data for a variety of different computer platforms used by end users. It is preferable that the central server support various different types of end user computer platforms. These different end user computer platforms may have different resources, such as different amounts of memory, different processor speeds, different operating systems, etc. Some of these different types of end user computer platforms may include general purpose computing devices that run navigation applications. Other end user computer platforms may include dedicated devices, such as in-vehicle navigation systems. Some of these different end user computer platforms may provide both audio and visual information to an end user, whereas other end user computer platforms provide only audio or only video. It would be preferable that each computer platform receive geographic data that are appropriate for the resources of the platform. This includes sending sufficient data in order to utilize the available resources of the computing platform in a meaningful way, but not sending data that cannot be used on the platform.
- Thus, there is a need for an improvement that allows a server that provides navigation-related services and data to support different kinds of end user computing platforms.
- Further, in a navigation system architecture in which data are transmitted from a central server to end users' computing platforms, there is a need for an improvement that allows data to be managed efficiently on both the server and on the end users' computing platforms.
- To address these and other objectives, the present invention comprises a system and method for providing navigation-related services to end users' computing platforms. A server maintains downloadable geographic data that are organized into pre-computed parcels that correspond to pre-determined sub-areas into which the entire geographic region serviced by the server is divided. The server responds to requests for navigation services and data by sending selected pre-computed parcels of geographic data to end users' computing platforms. Each of the end users' computing platforms stores the parcels received from the server in a memory cache. The end users' computing platforms use the data in the parcels to provide navigation-related features locally.
-
- Figure 1 is a diagram illustrating components of a navigation system that sends geographic data to end users' computing platforms located throughout a geographic region.
- Figure 2 is a block diagram showing components of the navigation services provider in Figure 1.
- Figure 3 shows a map of the geographic region in Figure 1 and is used to describe an embodiment for organizing the downloadable geographic data stored on the navigation server.
- Figure 4 is a diagram that shows components of several of the collections of geographic data that are contained in the downloadable geographic data storage shown in Figure 2.
- Figure 5 is a diagram showing components of one of the collections of geographic data contained in the downloadable geographic data storage shown in Figure 4.
- Figure 6 is a diagram showing components of another of the collections of geographic data contained in the downloadable geographic data storage shown in Figure 4.
- Figure 7 is a diagram showing components of another of the collections of geographic data contained in the downloadable geographic data storage shown in Figure 4.
- Figure 8 is a diagram showing components of additional collections of geographic data contained in the downloadable geographic data storage shown in Figure 4.
- Figure 9 is a block diagram showing components of one of the end user's computing platforms shown in Figure 1.
- Figure 10 is a flowchart showing steps in a process performed on the navigation services server of Figure 1.
- Figure 11 is a block diagram showing components of the routing data that are sent from the navigation services server to the end user's computing platform according to the process shown in Figure 10.
- Figure 12 is a map used to illustrate part of the process of Figure 10.
- Figure 13 is a flowchart of the steps performed on the end user's computing platform after the navigation services server has performed the process in Figure 10.
-
- Figure 1 shows a
geographic region 100. Thegeographic region 100 may correspond to a metropolitan or rural area, a state, a country, or combinations thereof, or any other area of comparable size. Located in thegeographic region 100 is a road network 104. - A
navigation system 110 serves end users (e.g., vehicle drivers and passengers, as well as other persons) in thegeographic region 100. Thenavigation system 110 is used by the end users to obtain navigation-related and map-related services with respect to thegeographic region 100. The navigation-related and map-related services include information about travel along the road network 104, including route calculation and guidance, people and business finding services (e.g., electronic yellow and white pages), maps, point of interest searching, destination selection, and so on. - The
navigation system 110 is a combination of hardware, software and data. Thenavigation system 110 includes remote components (i.e., hardware, software or data located at a central location remote from the end users) and local components (i.e., hardware, software, or data located physically with each end user). - Included among the remote components of the
navigation system 110 is anavigation services server 120. Associated with thenavigation services server 120 are a workinggeographic database 122 and a downloadable geographic data storage (or repository) 124. Thenavigation services server 120, the workinggeographic database 122 and the downloadablegeographic data storage 124 are maintained and operated by anavigation services provider 128. - The local components of the
navigation system 110 include thevarious computer platforms 130 operated by the end users to request and obtain navigation-related and map-related features and geographic data from thenavigation services provider 128. These various computer platforms 130 (also referred to as "end user computing platforms" or "client computing platforms") may includenavigation system units 132 located invehicles 134,personal computers 140, personal organizers (e.g., PDAs, PalmPilot®-type devices) 150,portable phones 160, or other types of computing devices that have the appropriate hardware and software to access thenavigation services provider 128 over adata network 170. - The
data network 170 may use any suitable technology and/or protocols that are currently available, as well as technology and/or protocols that become available in the future. For example, the data network may use WAP, TCP/IP, etc. More than one protocol may be used in thedata network 170 with appropriate conversions. - The
data network 170 may be part of, or connected to, the Internet. - The
network 170 may include awireless portion 172. Thewireless portion 172 of thedata network 170 enables two-way communication between the mobile enduser computing platforms 130 and theservice provider 128. Thewireless portion 172 may be implemented by any suitable form of wireless communication, including cellular, PCS, satellite, FM, radio, or technologies that may be developed in the future. Thewireless portion 172 may include one ormore transmitters 174, such as a transponder tower, an antenna tower, an FM tower, satellites, or other suitable means. Thetransmitters 174 include anappropriate communication link 176 to thenetwork 170 and/orservice provider 128. Thislink 176 may be land-based or may be wireless. Thetransmitters 174 include suitable technology that enables two-way communication between theservice provider 128 and the mobile enduser computing platforms 130. - One of the features of the
navigation system 110 of Figure 1 is that it accommodates different types of enduser computing platforms 130. Thenavigation system 110 of Figure 1 allows end users who have different types ofcomputing platforms 130 to obtain navigation services from thenavigation services provider 128 and to obtain and use geographic data provided from thenavigation services provider 128. - Figure 2 is a block diagram showing some of the components of the
navigation services provider 128. Included on thenavigation services server 120 of thenavigation services provider 128 areserver applications 200. One of theserver applications 200 is asubscriber services application 204. In order to use some or all of the other services provided by thenavigation services provider 128, end users may be required to be subscribers. Thesubscriber services application 204 provides services that support this function. Some of the subscriber services include enrollment, payments, renewals, confirmation of subscriber status, targeted advertising, and so on. Thesubscriber services application 204 maintains and uses asubscriber database 208 that contains various kinds of information concerning the various subscribers. - Another of the
server applications 200 is acommunications application 212. Thecommunications application 212 interfaces with the data network (170 in Figure 1) in order to receive messages from and send messages to the end users. Thecommunications application 212 may also maintain and manage communications sessions with the end users. - Included among the
server applications 200 are navigation-relatedapplications 216. The navigation-relatedapplications 216 use the workinggeographic database 122 associated with thenavigation services server 120 in order to provide the various different types of navigation-related services. One of the navigation-related applications 126 is aroute calculation application 220. Given data that identify the positions of an origin and destination, theroute calculation application 220 calculates a route between the origin and the destination. Theroute calculation application 220 may use any of various means or algorithms for this purpose. Methods for calculating routes are disclosed in U.S. Pat. No. 6,192,314, the entire disclosure of which is incorporated by reference herein. For example, the method for calculating routes may include either the A* algorithm or the Dykstra algorithm. (The methods disclosed in the aforementioned patent represent only some of the ways that routes can be calculated and the claimed subject matter herein is not limited to any particular method of route calculation. Any suitable route calculation method now known or developed in the future may be employed.) - Regardless of the method used, the
route calculation application 220 provides an output in the form of a list identifying a continuous series of roads (or segments thereof) that form a legally valid solution route between an origin and a destination. A "legally valid solution route" conforms to known traffic restrictions, such as one way streets, turn restrictions, etc. The method used by theroute calculation application 220 may be designed to optimize the solution route to meet one or more predetermined criteria. Such criteria may include the least travel time, the shortest distance, the fewest turns, etc. If the method used by theroute calculation application 220 is designed to find a solution route that is optimized for one or more criteria, then the solution route also ideally meets these one or more criteria. - Another of the navigation-related
applications 216 is a business andperson finder application 224. The business andperson finder application 224 includes yellow and white pages-types of functions. The business andperson finder application 224 finds the location or address of a specific business or person, or possibly other information about a specific business or person. The business andperson finder application 224 also provides for finding locations or addresses of categories of businesses or persons based upon various criteria. For example, the business andperson finder application 224 provides for finding all the restaurants of a specific ethnic type (e.g., Chinese) or chain (e.g., McDonald's) within specified distance (e.g., 5 miles) of a specified location (e.g., an end user's location). The business andperson finder application 224 can assist end users to find businesses, persons, or points of interest that can be used as destinations to which theroute calculation application 220 can then determine solution routes. - In order to provide navigation-related features, the
route calculation application 220 and thefinder application 224 use data from the workinggeographic database 122. The workinggeographic database 122 includes data representing the roads and intersections in the geographic region (100 in Figure 1) and also includes information relating to the represented roads and intersections, such as turn restrictions at intersections, speed limits along the roads, street names of the various roads, address ranges along the roads, and so on. The workinggeographic database 122 also contains information about points of interest, businesses and other information. The workinggeographic database 122 may be organized to facilitate performing navigation-related functions. Methods of organizing a geographic database to enhance the performance of certain navigation-related functions are described in U.S. Pat. Nos. 5,974,419, 5,968,109 and 5,953,722, the entire disclosures of which are incorporated by reference herein. - Another of the navigation-related
applications 216 on thenavigation services server 120 is a geographic data providing application 228. The geographic data providing application 228 manages the downloading of geographic data to end users'computing platforms 130. According to one embodiment of the navigation system (110 in Figure 1), certain navigation-related functions are performed for the end users remotely on thenavigation services server 120 and other navigation-related functions are performed for the end users locally on their respective enduser computing platforms 130. For example, according to one embodiment, route calculation is performed on thenavigation services server 120 in order to take advantage of the latest traffic information. Route guidance is performed locally on the end users'respective computing platforms 130 in order to present the information in a manner preferred by each end user and compatible with the resources of each end user's respective computing platform. - In order to perform certain navigation-related functions locally on an end user's computing platform, a navigation application on the end user's computing platform may require geographic data. In a present embodiment, each end user's computing platform obtains from the
navigation services server 120 the geographic data needed to perform certain navigation-related functions locally. The data that thenavigation services server 120 sends to the end users'computing platforms 130 are obtained from the downloadablegeographic data storage 124. The geographic data providing application 228 on thenavigation server 120 manages the provision of geographic data from the downloadablegeographic data storage 124 to the end users'computing platforms 130. - The geographic data providing application 228 performs several functions. One function performed by the geographic data providing application 228 is determining the appropriate data to send from the downloadable
geographic data storage 124 to an end users' computing platform. This determination can take into account several factors. According to one embodiment, an end user's computing platform identifies a collection of geographic data. Thenavigation services provider 128 may maintaindifferent collections 232 of geographic data in the downloadablegeographic data storage 124. Eachseparate collection 232 is a separate representation of the entire geographic region (100 in Figure 1). The composition of thesedifferent collections 232 is explained in more detail below. Upon a determination of thecollection 232 of geographic data from which to send data, the geographic data providing application 228 selects particular portions of data from thecollection 232 and sends the selected portions of data to the end user's computing platform, as described in more detail below. - According to an alternative embodiment, the geographic data providing application 228 may determine the
appropriate collection 232 of geographic data from which to select data to send to a particular end user by referring to thesubscriber database 208. Thesubscriber database 208 may maintain information that identifies the collection of geographic data from which data is to be selected for sending to each end user. According to another alternative embodiment, the geographic data providing application 228 may determine the appropriate collection of geographic data from which to select data to send to a particular end user by any other means. - After determining the
collection 232 from the downloadablegeographic data storage 124 from which geographic data are to be selected to send to an end user's computing platform, the particular portions of geographic data to be sent are selected. In order to perform this function, the geographic data providing application 228 takes into account (1) the location of the end user's computing platform, (2) where the end user's platform is going, and (3) other factors. If the end user is following a route calculated by theroute calculation application 220, the geographic data providing application 228 selects data that represents an area along the route. An area along a route may be referred to as a "strip map." The dimensions of the strip map may be determined by the geographic data providing application 228. This determination may take into account specification of strip map dimensions by the end user. Alternatively, the geographic data providing application 228 may determine appropriate strip map dimensions based upon stored information about the end user's preferences or computer platform resources. This stored information may be maintained in thesubscriber database 208. - As mentioned above, the geographic data providing application 228 determines which data to send to the end users'
computing platforms 130. The data that the geographic data providing application 228 sends to the end users' computing platforms are obtained from the downloadablegeographic data storage 124 maintained on thenavigation services server 120. In order to facilitate the downloading of data from thenavigation service server 120 to the end users'computing platforms 130, the data are organized into one or morepredetermined collections 232. In addition, eachcollection 232 of data in the downloadablegeographic data storage 124 is organized into a plurality of groupings (or "parcels"). In one embodiment, the data contained in each parcel are determined spatially, i.e., the data in each parcel represent geographic features that are located close to each other. More specifically, the data contained in each parcel represent the geographic features contained in a separate, distinct one of a plurality of separate geographic areas into which the entire represented geographic region (100 in Figure 1) is divided. - As stated above, according to this embodiment, the downloadable
geographic data storage 124 includes severaldifferent collections 232. Each of thesecollections 232 comprises a separate representation of the entiregeographic region 100. Each of thesecollections 232 is organized into a plurality of parcels. - Figures 3 and 4 illustrate how the data contained in each
collection 232 of the downloadablegeographic data storage 124 are organized, according to one embodiment. Figure 3 shows themap 300 of thegeographic region 100, previously illustrated in - Figure 1. In Figure 3, a
grid 304 overlays themap 300 representing of thegeographic region 100. Thegrid 304 is formed of grid lines 308. The grid lines 308 divide the representedgeographic region 100 into a plurality ofareas 312. In this embodiment, theareas 312 are rectangular; however, in alternative embodiments theareas 312 may have other shapes. The grid lines 308 of thegrid 304 represent the boundaries of theareas 312. Theseareas 312 may have different dimensions, as shown in Figure 3. Alternatively, theareas 312 may all have the same dimensions. The dimensions of theareas 312, as well as whether all theareas 312 have the same dimensions, depend upon the procedure used for organizing the data that represent the geographic features contained in these geographic areas into parcels. Likewise, the locations of the boundaries of theareas 312 depend on the procedure used for organizing the data that represent the geographic features contained in these geographic areas into parcels. Methods for determining the boundaries of areas for forming parcels are disclosed in U.S. Pat. No. 5,974,419, the entire disclosure of which is incorporated by reference herein. - In forming each
parcel 312, theindividual data records 336 that represent the geographic features that are encompassed within eachseparate area 312 are gathered together in a separate parcel 320 (or grouping) of data. Thus, eachparcel 320 of data (in each collection 232) contains all thedata records 336 that represent the geographic features encompassed within a correspondinggeographic area 312. Thus, all the geographic areas 312 (corresponding to all theparcels 320 in a collection 232) make up theentire region 100. Thus, eachparcel 320 of data may contain a plurality ofdata records 336 that represent the roads, intersections, points of interest, and other features located within thegeographic area 312 corresponding to the parcel. - According to one embodiment, all the
parcels 320 within eachcollection 232 have a uniform parcel size. For example, eachparcel 320 of data may have a size of 1K, 2K, 4K, 8K, 16K, 32K, and so on. The parcel size for eachcollection 232 may be determined based upon several factors, including memory resources of the end users' computing platforms that are expected to use the data. According to this embodiment, theparcels 320 in onecollection 232 may have a different size than theparcels 320 in anothercollection 232. For example, onecollection 232 may have parcels that are 32K in size whereas another of thecollections 232 may have parcels that are 16K in size. - As shown in Figures 3 and 4, each of the
collections 232 includes a plurality ofparcels 320. Each of theparcels 320 in acollection 232 corresponds to a separate one of thegeographic areas 312 located within the entiregeographic region 100. In thedownloadable data storage 124, each of thecollections 232 and each of theparcels 320 in each of the collections is pre-computed. In other words, the determination and formation of eachcollection 232 and the determination and formation of all theparcels 320 that make up eachcollection 232 are performed prior to any of the data in the downloadeddata storage 124 being made available for downloading to any of the end users'computing platforms 130. In this manner, the determination of which data to send to an end user is facilitated. When an end user requires data for use locally in his/her computing platform, thenavigation services server 120 does not have to determine which specific data records the end user may need and then send these data records to the end user. Instead, thenavigation services server 120 determines whichgeographic areas 312 are required by the end user and then sends theentire parcels 320 that contain the data that represent all the geographic features in thesegeographic areas 312 to the end user. Theparcels 320 that are sent to the end user represent a clip or slice of all the data that represent the geographic region. Theseparcels 320 include all the individual data records that may be needed by the end user. This organization and process facilitate operations on thenavigation services server 120. The geographic providing application 228 on thenavigation services server 120 determines whether the end user needs any data corresponding to a definedgeographic area 312 corresponding to a parcel, and if so, sends the entire parcel corresponding to thegeographic area 312 to the end user. This organization and process also facilitate operations on the end user's computing platform by providing a way to manage memory resources, as explained in more detail below. - Except as noted below, when data are downloaded from the
downloadable data storage 124 to the end users' computing platforms, the data are downloaded in whole parcels. This means that all thedata records 336 that represent geographic features encompassed within eachgeographic area 312 are accessed together as a group. Thus, aparcel 320 represents a quantity of data records that are downloaded at the same time for use in the end user's computing platform. When a parcel of data is sent to an end user's computing platform, all of the data records in the parcel are available in the end user's computing platform. In one embodiment, all of the data records in a parcel are maintained in the memory of the end user's computing platform system at the same time. - As mentioned above, the downloadable
geographic data storage 124 containsdifferent collections 232 of geographic data. Thesedifferent collections 232 all represent the same geographic region (100 in Figure 1), but may include different types of data (or data organized differently). Thesedifferent collections 232 of data are all organized into parcels, as described above. As stated above, theparcels 232 in a collection preferably conform to a uniform parcel size. However, the uniform size of the parcels in onecollection 232 may be different than the uniform size of the parcels in anothercollection 232. The contents of some of thecollections 232 are described below. - Figure 5 is a diagram used to illustrate the contents of one of the
parcels 320 ofgeographic data 336 in one of the collections 232(1). Thedata 336 in theparcel 320 correspond to one of the geographic areas 312(1). In this embodiment, theparcel 320 contains all thedata 336 that represent all the features contained in the geographic area 312(1). As an example, theparcel 320 contains data that represents all the roads located in the geographic area 312(1) corresponding to theparcel 320. Each road is represented as a series of connected segments, wherein a segment corresponds to a portion of a road between adjacent intersections along the road or between an intersection and a location at which the road dead ends. In this embodiment, each road segment is represented by a separate data entity (or data record). Each data record that represents a road segment includes (or points to) data about the represented road segment, such as the speed limit (or speed category) of the road segment, the functional class (i.e., rank) of the road segment, the number of lanes along the road segment, and so on. - A data record that represents a road segment also includes data indicating the location of the road segment. In one embodiment, this information includes a reference to node records that represent the end points of the road segment. Associated with the node records are data indicating the locations (e.g., latitude, longitude, and optionally, altitude) of the road segment end points (i.e., nodes). For road segments that are not straight, additional data are included to indicate the shape of the road segment. In one embodiment, shape point data are used for this purpose. A shape point identifies a position (e.g., latitude, longitude, and optionally, altitude) of a location along a road segment between the end points thereof. Using one or more shape points, the shape of an other-than-straight road segment can be represented.
- A record that represents a road segment also includes data indicating the name(s) of the road segment. In one embodiment, this information includes a reference to one or more name records. In this embodiment, the name records for the roads and other named geographic features are included in the same parcel.
- In the embodiment shown in Figure 5, the
parcel 320 also includes point of interest data. The point of interest data includes information about points of interest. Points of interest include businesses, public facilities, etc. The point of interest data includes information about the represented points of interest, such as the names, type (e.g., hotel, restaurant, chain, museum, police station, etc.), address, phone, etc. In this embodiment, the data records for the point of interests contained in the geographic area are included in the same data parcel with the road segment data, the node data and the name data. - In the collection 232(1) of data in Figure 5, all the parcels are 16K in size (although any other data size may be used). Figure 6 shows another collection 232(2) of data. In Figure 6, the collection 232(2) is divided into
parcels 320 that include the same kinds of data, e.g., road segment records, node records, name records, and point of interest records, etc. However, in Figure 6, theparcels 320 that form the collection 232(2) have a different size than the parcels in the collection 232(1) in Figure 5. The parcels in the collection 232(2) in Figure 6 are each 32K in size. Because eachparcel 320 in Figure 6 contains more data than each parcel in Figure 5, each parcel can represent a larger geographic area. Thus, as shown in Figure 6, the geographic area 312(2) corresponding to theparcel 320 is larger in dimension than the geographic area 312(1) corresponding to theparcel 320 in Figure 5. - Figure 7 shows another collection 232(3) of data. The collection 232(3) of data shown in Figure 7 includes the same kinds of data, e.g., road segment records, node records, name records, and point of interest records, etc., as in the collections 232(1) and 232(2) shown in Figures 5 and 6, respectively. In addition, in the collection 232(3) of data in Figure 7, each
parcel 320 also includes pronunciation data. The pronunciation data corresponds to the names of the geographic feature and/or points of interest in the represented geographic area. The pronunciation data includes phonetic representations of the names of the geographic feature and/or points of interest in theparcel 320 so that these names can be audibly reproduced using appropriate hardware and software in the end user'scomputing platform 130. In the collection 232(3) of data in Figure 7, eachparcel 320 contains 64K of data, although any other data size may be used. - Figure 8 shows three more data collections 232(4)(1), 232(4)(2), and 232(4)(3). In this embodiment, each collection 232(4)(1), 232(4)(2) and 232(4)(2) includes only some of the types (or attributes) of data. For example, the collection 232(4)(1) includes only routing data, e.g., segment and node records. The collection 232(4)(2) includes only name records. The collection 232(4)(3) includes only point of interest records. Each of these collections 232(4)(1), 232(4)(2), and 232(4)(3) is organized into
separate parcels 320 that correspond to separate respectivegeographic areas 312. Accordingly, aparcel 320 of the collection 232(4)(1) includes the segment and node records that represent the roads and intersections in the geographic area 312(4). The collection 232(4)(2) includes the name records that represent names of the geographic features and/or points of interest in the geographic area 312(4). The collection 232(4)(3) includes the point of interest records that represent the points of interest located in the geographic area 312(4). In the collections 232(4)(1), 232(4)(2), and 232(4)(3) of data in Figure 8, eachparcel 320 contains 16K of data (although another uniform data size may be used). - The embodiments of the different data collections shown in Figure 5-8 represent only some of the different types of collections of data that can be maintained in the downloadable geographic data storage (124 in Figure 2) on the
navigation services server 120. The downloadablegeographic data storage 124 can include collections of data that have parcels of different sizes. In addition, the downloadablegeographic data storage 124 can includes collections of data that have parcels that are organized other than spatially. For example, the downloadablegeographic data storage 124 can include collections that have parcels of data organized alphabetically or by administrative hierarchy (e.g., city, county, state, and country). - As mentioned above, each end user uses a computing platform (130 in Figure 1) that obtains data from the
navigation services server 120. Also as stated above, some navigation-related functions are performed locally on an end user's computing platform using the data that are obtained from thenavigation services server 120. Because different end user computing platforms may have different hardware and software, the navigation-related functions that are performed on the end users' computing platforms may vary from one end user platform to another. Accordingly, in the section that follows, a configuration of an end user computing platform is described. It is understood that not all end user computing platforms may necessarily provide all the functions described below and that some end user computing platforms may provide additional or other functions. - Although the different end user computing platforms may have different hardware and software resources, all the end user computing platforms receive data from the navigation services server (120 in Figure 1). Some or all the end user computing platforms receive geographic data from the downloadable
geographic data storage 124 on thenavigation services server 120. Enduser computing platforms 130 that receive geographic data from the downloadablegeographic data storage 124 can use the memory management features, described below, to handle the parcels of data obtained from thenavigation services server 120. - Figure 9 shows a block diagram of some of the components of one of the end user's
computing platforms 130. The end user'scomputing platform 130 includes acommunications system 400. Thecommunications system 400 in the end user'scomputing platform 130 includes the hardware and software components needed to receive messages from and send messages to the navigation server (120 in Figure 1) over thedata network 170. Thecommunications system 400 interfaces with other components in the end user'scomputing platform 130. - The end user's
computing platform 130 also includes a user interface 410. The user interface 410 allows the end user to provide input to and receive information from the end user'scomputing platform 130. The user interface 410 includes hardware and software components. For example, the user interface 410 may include a display, a microphone, speakers, a keypad, or other kinds of means for inputting information into the computing platform and outputting information therefrom. The user interface 410 includes supporting software that may provide menus, prompts, audio, etc. The user interface 410 interfaces with other components in the end user'scomputing platform 130. - Included on the end user's
computing platform 130 are navigation-relatedapplications 420. The navigation-relatedapplications 420 use the geographic data obtained from thenavigation server 120 to provide various different types of navigation-related services. One of the navigation-relatedapplications 420 is a positioning application 420(1). The positioning application 420(1) uses the geographic data obtained from thenavigation server 120 to determine the position of the end user'scomputing platform 130 relative to data representing the road network. The positioning application 420(1) may also obtain data from apositioning system 430 which is part of the end user'scomputing platform 130. Thepositioning system 430 may use GPS, dead-reckoning, or a combination of these or other technologies to determine the location of the end user'scomputing platform 130. Methods for performing positioning are disclosed in U.S. Pat. No. 6,192,312, the entire disclosure of which is incorporated herein by reference. The positioning application 420(1) is optional, i.e., not all end users' computing platforms may provide for or support positioning. - Another of the
navigation applications 420 on the end user's computing platform is route guidance 420(2). The route guidance application 420(2) uses data from thenavigation server 120 to provide instructions for the end user to travel to a desired destination. Methods for performing route guidance using geographic data are disclosed in U.S. Pat. No. 6,199,013, the entire disclosure of which is incorporated herein by reference. - Another of the
navigation applications 420 on the end user's computing platform is map display 420(3). The map display 420(3) uses data from thenavigation services server 120 to provide maps graphically on the display screen of the user interface 410 of the end user's computing platform. The maps may show the area around the location of the end user's computing platform, the area along a route that the end user is following, the area around a location specified by the end user, or any other specified area. Methods for performing map display using geographic data are disclosed in U.S. Pat. Nos. 6,092,076 and 6,163,749, the entire disclosures of which are incorporated herein by reference. - Another of the
navigation applications 420 on the end user's computing platform is a re-routing application 420(4). The re-routing application 420(4) is used when the end user departs from a route to a destination for which the end user was receiving guidance for following. The re-routing application 420(4) uses data from thenavigation server 120 to calculate a new route to the destination or back to an original route. The re-routing application 420(4) may use the same methods for performing route calculation that are described in U.S. Pat. No. 6,129,314, the entire disclosure of which is incorporated herein by reference. - Another of the
navigation applications 420 on the end user's computing platform is a query application 420(5). The query application 420(5) is used to formulate queries (i.e., requests for information) for the navigation applications (216 in Figure 2) on thenavigation services server 120. The query may be a request to calculate a route using theroute calculation application 220, a request for information about a business, person, or point of interest using thefinder services 224, or any other service or application provided by thenavigation services server 120. The query application 420(5) manages sending a message to thenavigation services server 120, waiting for a response, receiving the response, and then using the requested data locally, e.g., inlocal applications 420. - Another of the
navigation applications 420 on the end user's computing platform is a point of interest look up application 420(6). The point of interest look up application 420(6) is used to look up (i.e., find) points of interest. The data describing the points of interest may be stored on thenavigation services server 120 or locally. - The end user's
computing platform 130 includes amemory manager application 500. Thememory manager application 500 manages the memory resources of the end user'scomputing platform 130. Among the functions performed by thememory manager application 500 is management of the geographic data that are received from thenavigation server 120. As part of this function, thememory manager application 500 manages theparcels 320 of geographic data that are received by the end user'scomputing platform 130 from the downloadablegeographic data storage 124 on thenavigation services server 120. Methods for managing parcels of geographic data in a memory are disclosed in U.S. Pat. Nos. 6,073,076 and 6,047,280, the entire disclosures of which are incorporated herein by reference. - Referring to Figure 9, the
memory manager application 500 reserves aportion 504 of thememory 506 of the end user'scomputing platform 130 for use by the navigation-relatedapplications 420 and reserves anotherportion 514 for use as aparcel cache 520. Thememory manager application 500 may determine the sizes of theseportions computing platform 130, or any time thereafter. This determination may take into account the total amount of installed memory that is available. In addition, thememory manager application 500 may determine aportion 528 of thememory 506 to be re-allocatable. Some or all of thisre-allocatable portion 528 may be used alternately for thenavigation applications 420 or for theparcel cache 520. Use of there-allocatable portion 528 is determined during runtime of the end user'scomputing platform 130 by thememory manager application 500 based on the needs of the end user. - During operation of the end user's
computing platform 130, the navigation-relatedapplications 420 on the end user'scomputing platform 130 use the data contained in theparcels 320 that are downloaded from thenavigation services server 120. To improve performance of the end user'scomputing platform 130, thecache 520 is provided in thememory 506 of the end user'scomputing platform 130. Thecache 520 is specifically used for storing a number ofparcels 320 of geographic data that have been downloaded from thenavigation services server 120. Storing parcels of geographic data in thecache 520 supports the navigation-relatedapplications 420 on the end user'scomputing platform 130 by maintaining a number of parcels in memory ready for use. Having parcels in memory ready to use avoids the relatively large delay associated with obtaining the parcels from thenavigation services server 120. Theparcel cache 520 may also be used to store parcels of geographic data that a navigation function predicts will be needed soon. As stated above, the formation and operation of theparcel cache 520 is performed by thememory manager application 500. - The size of the parcel cache depends upon several factors. One factor that affects the size of the parcel cache is the size(s) of the parcels. The size of the parcel cache relative to the size of the parcels determines how many parcels can be contained in the parcel cache. As mentioned above, in some embodiments, the parcels are stored in regular sizes, e.g., 2K, 4K, 8K, 16K, 32K, and so on, in the downloadable
geographic data storage 124 on thenavigation services server 120. Accordingly, the size of theparcel cache 520 on the end user's computing platform defines the number or parcels that can be stored locally. For example, a 384 K parcel cache can store a maximum of 24 parcels each 16K in size. Correspondingly fewer parcels of larger sizes can be stored and correspondingly more parcels of smaller sizes can be stored. In one embodiment, theparcel cache 520 is used to hold parcels of all the same size or in an alternative embodiment, theparcel cache 520 can hold parcels of varying sizes. - Another factor that affects the size of the parcel cache is the total available memory resources of the end user's
computing platform 130. Computing platforms with limited memory resources may provide a relatively small portion for the parcel cache, whereas computing platforms with greater memory resources may provide relatively more memory for a parcel cache. - Still another consideration that affects the amount of memory used for the
parcel cache 520 is the relative sizes of thememory 514 allocated to theparcel cache 520 and thememory 504 allocated to thenavigation applications 420. A relatively large allocation of memory for theparcel cache 520 may not necessarily improve performance of an end user's computing platform if the amount ofmemory 504 available for thenavigation applications 420 is constrained, and vice versa. Thememory manager application 500 may include algorithms that determine an appropriate balance between the allocation of memory for thenavigation applications 420 and the allocation of memory for use by the parcel cache. - If a parcel needed by a navigating application is not in the parcel cache 520 (as determined by the memory manager 500), the
memory manager 500 requests the parcel from thenavigation services server 120. - One of the functions performed by the
navigation system 110 is route guidance. Route guidance includes providing an end user with instructions to reach a desired destination. Figure 10 is a flow chart that shows the steps in aprocess 600 performed by thenavigation system 110 of Figure 1 for providing an end user with information for following a route to a desired destination. - Route guidance may be associated with, or preceded by, one or more other functions performed by the
navigation system 110. Before the information for following a route is provided to the end user, there is a step in which the origin and destination of the route are determined (Step 610 in Figure 10). Determination of a destination may involve providing the end user with a means to select a location in thegeographic region 100. Destination selection may include specification of a street address, street intersection, map location, or other location identification means. Alternatively, destination selection may include identification to the end user of locations that meet an end user's specified criteria or category, e.g., restaurants of a particular type within a specified distance of a location. - In the embodiment of Figures 1 and 10, the function of destination selection may be performed using a combination of locally available data, hardware or software and remotely located data, hardware or software. According to one embodiment, an end user uses locally available hardware and software (e.g., the query application 420(5) in Figure 9) on his/her
computing platform 130 to access the finder application (224 in Figure 2) on thenavigation services server 120. The end user uses this combination of local hardware and software and remote hardware and software to access the workingdatabase 122 on thenavigation services server 120 to identify a location as a destination. The destination may be an address, a person's name, a business address, or a business name. Alternatively, the end user may use the finder application (224 in Figure 2) to find a person, business, or point of interest by location, e.g., the bank that is closest to a specified location. - In some cases, the end user may first use the positioning application (420(1) in Figure 9), which is located locally on the end user's computing platform, to identify his/her current location, and then specify this location to the
finder application 224 on thenavigation services server 120 to use in a location-based search for persons, businesses, or points of interest. - In an alternative embodiment, an end user may use locally available data, hardware and software to determine a destination. According to another alternative, the function of destination selection may be performed on the end user's computing platform using locally available hardware and software but using data which have been obtained from the remotely located navigation services server.
- In order to calculate a route, a starting point (i.e., origin) is also required. In some cases, the end user's current location may be used as the origin. The end user's current location can be determined using the positioning application 420(1) which is located locally among the
navigation applications 420 on the end user'scomputing platform 130. When performing this function, the positioning application 420(1) may use locally available data. These locally available data may be part of a geographic database stored on-board the end user's computing platform. Alternatively, the locally available data have been previously obtained from thenavigation services server 120 in response to a prior request made by the end user using the query application 420(5). According to another alternative, the starting location may be determined in the same manner as the destination. According to another alternative, the end user's current location can be specified using coordinates determined using the positioning system (430 in Figure 9) in the end user's computing platform. According to yet another alternative, the user can explicitly indicate where the route is to start. This is equivalent to destination selection as explained above. - After the origin and destination are specified, the
process 600 includes a step in which the data indicating the origin and destination are received in theroute calculation application 220 on the navigation server 120 (Step 622 in Figure 10). As mentioned above, theroute calculation application 220 determines a solution route, which is a legally valid, continuous series of roads (or segments thereof) between the specified origin and destination (Step 636 in Figure 10). Theroute calculation application 220 uses the data in the workinggeographic database 122. Operation of theroute calculation application 220 has been described above. When the solution route has been calculated, a series of roads, or segments thereof, are identified that form a continuous, legally valid route from the origin to the destination. - After the
route calculation application 220 has calculated a solution route, anoutput 650 is provided. Figure 11 is a diagram representing the components of theoutput 650 of theroute calculation application 220. Theroute calculation output 650 contains an ordered list identifying a plurality of road segments. In Figure 11, the plurality of road segment are identified by data entity IDs. These IDs are assigned to the data entities that represent these road segments by the developer of the workinggeographic database 122. The plurality of road segment data entities in theoutput 650 of theroute calculation application 220 are labeled, seg1, seg2, seg3... seg(n). The plurality of data entities represent the road segments that form the continuous navigable route between the origin and the destination that has been calculated by theroute calculation application 220. Instead of using data entity IDs, theroute calculation application 220 may use any other means for identifying the road segments that make up the solution route. - The
route calculation output 650 may include other information in addition to the list of road segments. - After the solution route has been calculated by the
route calculation application 220 on thenavigation services server 120, thenavigation services server 120 sends data to the end user'scomputing platform 130 so that guidance for following the solution route can be provided to the end user. Thenavigation services server 120 sends two kinds of data to the end user'scomputing platform 130. First, thenavigation services server 120 sends to the end user'scomputing platform 130 theoutput 650 of theroute calculation application 220 that indicates the road segments that form the solution route (Step 656 in Figure 10). In addition to thedata 650 indicating the solution route, thenavigation services server 120 also sendsadditional data 660 relating to the solution route. The additional 660 data relating to the solution route are used in combination with thedata 650 indicating the solution route to provide the end user with meaningful guidance for traveling the route. - The
additional data 660 that are sent by thenavigation services server 120 to the end user'scomputing platform 130 are obtained from the downloadablegeographic data storage 124. After the solution route has been calculated (in Step 636), the geographic data providing application (228 in Figure 2) determines which data from the downloadablegeographic data storage 124 to send to the end user's computing platform 130 (Step 668 in Figure 10). As mentioned above, the data contained in the downloadablegeographic data storage 124 are organized into a plurality ofcollections 232, each of which is organized into a plurality of parcels (320 in Figure 4). Thus, when determining which geographic data to send to the end user'scomputing platform 130, the geographic data providing application 228 determines whichparcels 320 of data from aparticular collection 232 to send. - As mentioned above, the determination of which
collection 232 to use when sending geographic data can be determined in several different ways. One way is to have an application on the end user's computing platform identify the collection from which data are to be sent. Thecollection 232 can be identified by ID or by description. Alternatively, the geographic data providing application 228 may query thesubscriber database 208 in Figure 2 to determine whichcollection 232 to use for a particular end user. Alternatively, the geographic data providing application 228 may use one collection by default. Any other means may be used to determine the appropriate collection to use. - In addition to specifying which
collection 232 to use when sending geographic data, an application in the end user's computing platform may also indicate to the geographic data providing application 228 the memory resources that are available on the end user's computing platform for storing the data received from the navigation services server. Alternatively, the size of the memory resources available on the end user's computing platform can be stored as a configuration parameter in thesubscriber database 208 in Figure 2, or according to another alternative, a default memory size can be used. - After the
collection 232 of data to use is determined, thespecific parcels 320 in thecollection 232 are selected. Figure 12 illustrates how the geographic data providing application 228 determines which parcels of data to send to an end user's computing platform. Figure 12 shows amap 690 of a portion of theregion 100. Aroute 700 is shown on themap 690. Theroute 700 is shown as a plurality ofconnected road segments 706. Also shown on themap 690 are theoutlines 710 of geographic areas 312(A)-312(L). As described above, each of these geographic areas 312(A)-312(L) encompasses the geographic features that are represented by the data contained in aseparate parcel 320 of data into which theentire collection 232 of geographic data is divided. Using the locations of the road segments in thesolution route 650, as calculated by theroute calculation application 220, the geographic data providing application 228 identifies thegeographic areas 312 that are crossed by the solution route or that are within a specified distance from the road segments in the solution route. (The specified distance may be configurable.) The geographic areas that are crossed by or close to the solution route may be determined by any suitable means. For example, theroute calculation application 220 may store IDs of these geographic areas (or IDs of the parcels themselves), as the solution route is being calculated. - Once the geographic areas 312(A)-312(L) that are crossed by or close to the solution route are determined, the
parcels 320 that contain the data that represent the geographic features encompassed in these geographic areas are identified for sending to the end user'scomputing platform 130. - When the geographic data providing application 228 sends the parcels corresponding to the solution route to the end user's computing platform, the parcels are sent in the order in which they correspond to the route, starting from the origin. In this way, the end user's computing platform first receives the parcels that contain the data that represent the features around the origin and then receives the parcels that contain the data that represent the features along the subsequent portions of the route.
- When sending the parcels corresponding to the solution route to the end user's computing platform, the geographic data providing application 228 may send all the parcels corresponding to the solution route to the end user's computing platform immediately. Alternatively, the geographic data providing application 228 may send only some of the parcels initially and then send the remainder of the parcels at one or more subsequent times. If the end user's computing platform has sufficient memory resources to hold all the parcels identified as corresponding to the solution route, the geographic data providing application 228 may send all the parcels immediately to the end user's computing platform. However, if the end user's computing platform does not have sufficient memory resources to hold all the parcels identified as corresponding to the solution route, the geographic data providing application 228 sends only the number of parcels that the end user's computing platform can hold in memory. The parcels that are sent initially by the geographic data providing application 228 correspond to the initial portion of the route. When the geographic data providing application 228 initially sends only some of the parcels corresponding to the solution route, the geographic data providing application 228 maintains a list identifying the parcels that were not sent. According to this embodiment, after the end user has proceeded along the route through the areas represented by the parcels that were initially stored in memory, the end user's computing platform requests the navigation services server to send those parcels corresponding to the next portion of the route. The list of parcels corresponding to the solution route maintained by the geographic data providing application 228 is used to quickly identify which parcels to send next to the end user's computing platform.
- Referring back to the
process 600 in Figure 10, if all the parcels corresponding to the solution route are sent to the end user's computing platform, the process ends (Steps 722 and 724). If all the parcels corresponding to the solution route are not sent to the end user's computing platform (e.g., if the end user's computing platform does not have enough memory to hold all the parcels), data identifying the parcels that are not sent are stored (Step 725). Then, the process waits until the end user's computing platform requests the parcels corresponding to the next portion of the route (Step 726). When the request for the next portion of the route is received, additional parcels of data are sent to the end user's computing platform (Step 720, again). These steps are repeated until all the parcels corresponding to the solution route are sent (Steps 722 and 724). - Figure 13 shows a
process 750 performed on the end user's computing platform when it receives thedata 650 indicating the route and theadditional data 660 from thenavigation services server 120. First, thedata - The
memory manager application 500 reserves a portion of the memory of the end user's computing platform for use as aparcel cache 520, if it has not done so already (Step 764). When forming the parcel cache, thememory manager application 500 takes into account the size of the parcels that will be received. For example, if the parcels are 64K in size, thememory manager application 500 may reserve 1280K of memory, which will be enough to hold 20 parcels. Thememory manager application 500 stores theadditional data 660, which are in the form ofparcels 320, in the parcel cache 520 (Step 770). - The
parcel cache 520 formed by thememory manager application 500 may not be large enough to hold all the parcels for the entire route. If this is the case, thememory manager application 500 stores the parcels in the order in which they are sent by thenavigation services server 120 and stops storing any more parcels when the parcel cache is full. In this way, the parcels ofadditional data 660 corresponding to the beginning of the route are stored in the parcel cache. The parcels ofadditional data 660 corresponding to subsequent parts of the route are not stored in the parcel cache at this time. Thememory manager application 500 may send a message to the geographic data providing application 228 indicating the size of the cache (or the number of parcels that can be stored). Alternatively, thememory manager application 500 may send a message to the geographic data providing application 228 to stop sending parcels when the parcel cache is full. - On the end user's computing platform, the
data 650 indicating the solution route are not stored in theparcel cache 520. Instead, thedata 650 indicating the solution route are stored in the working portion of memory (504 in Figure 9), where the data are used by thevarious navigation applications 420 on the end user'scomputing platform 130. - On the end user's computing platform, the navigation applications (420 in Figure 9) use the
additional data 660 relating to the solution route, in combination with thedata 650 indicating the solution route, to provide navigation-related functions (Step 776). For example, theroute data 650 and theadditional data 660 may be used by the route guidance application 420(2) on the end user'scomputing platform 130 to provide maneuvering instructions at specific locations along the solution route. As an example, the route guidance application 420(2) uses theroute data 650 and theadditional data 660 to provide a maneuvering instruction, such as "TURN LEFT AT THE NEXT INTERSECTION." Theseadditional data 660 may be used to provide these instructions as text on a display screen or as audible instructions. - According to another example, the
route data 650 and theadditional data 660 relating to the solution route may be used by the map display application 420(3) on the end user'scomputing platform 130 to provide a map of the route on the display screen of the user interface (410 in Figure 9) of the end user's computing platform. The map of the route may be in the form of a "strip map." - According to yet another embodiment, the
route data 650 and theadditional data 660 may be used to indicate the positions of road segments that are not part of the solution route but that are close to the solution route. These data can be used by vehicle positioning hardware and software, e.g., the positioning application 420(1), in the end user's computing platform to determine whether the end user has departed from the solution route, and if so, how to travel back to the solution route (e.g., using the re-routing application 420(4)). - As mentioned above, it may not be possible to store initially all the
data parcels 320 that relate to the entire solution route represented by thedata 650. If this is the case, only the parcels that contain the data that represent the geographic features along a first portion of the route are stored initially in the parcel cache on the end user's computing platform. Then, after the end user has traveled part way along the route, the end user will eventually approach the location at which the coverage of the data in the parcel cache ends. For example, referring again to Figure 12, if the parcel cache on the end user's computing platform has room for only six parcels of data, the six parcels corresponding to the areas 312(A)-312(F) would be stored initially in the parcel cache. Then, after the end user has traveled along the route to the point labeled B, the end user would be close to the location at which the coverage of the additional data stored in the parcel cache ends. When the end user is at this point, thequery application 420 on the end user's computing platform sends a new request for navigation-related services and data to the navigation services server 120 (Steps 790 and 792). This new request may reference the prior request or may be handled as a request for new route. - According to one method, when the end user's computing platform approaches the end of the coverage areas corresponding to the parcels contained locally in its parcel cache and requests more parcels from the navigation services server (Step 792), this new request may reference the prior request. If the new request references the prior request, the process on the navigation services server uses the list identifying the parcels that were not previously sent to the end user's computing platform (in
Step 725 in Figure 10) to determine which parcels to send next. These parcels are obtained from thedownloadable data storage 124 and sent to the end user's computing platform. When these new parcels are received on the end user's computing platform, theprocess 750 starts over atStep 760. - According to an alternative method, when the end user's computing platform approaches the edge of the coverage areas corresponding to the parcels contained locally in its parcel cache and requests more parcels from the navigation services server (Step 792), the request may be handled by the navigation services server as a request for an entirely new route. The navigation services server performs the
process 600 in Figure 10, starting atStep 622. Thenavigation services server 120 uses theroute calculation application 220 to calculate a new route to the destination using the point B as a new origin (Step 636 in Figure 10, again). By treating the request for the next leg of the route as a request for a new route, theroute calculation application 220 on the navigation services server may take into account any changes in traffic conditions that may have occurred since the prior route was calculated. Thenavigation services server 120 then sends the new route (in the form of new route data 650) and parcels of new additional data 660 (in the form of parcels) to the end user's computing platform (Steps new route data 650 and new additional 660 data are received on the end user's computing platform, they are treated as an entirely new route. The parcels that had been stored in the parcel cache are replaced with the new parcels that are received that relate to the next leg of the route. - In another embodiment, the end user may request geographic data for map display without necessarily requesting a route. For example, an end user may want to have a map display of the area around his/her present location. In this case, the end user operates his/her computing platform to request a map display around his/her geographic location. The end user may use the query application 420(5) for this purpose. The end user may specify his/her location or alternatively, the query application 420(5) may obtain from the positioning system 430 (if present), data that indicates the end user's current position and include this information in the request for map display data.
- The request for map display data is handled on the
navigation services server 120 in a similar way as the request for route information, described above. In this case, a route does not have to be calculated. The navigation services server identifies the parcels that contain the geographic data that represent the features around the specified location. Then, the navigation services server sends these parcels to the end user's computing platform, as described above. On the end user's computing platform, these parcels are handled in a similar manner as described above in connection with Figure 14. - Instead of requesting map data for his/her end user's current location, the end user may request map data for any location. The end user may use any suitable means to identify the location for which map data are desired.
- Any of the functions provided on the end user's computing platform may be provided in combination with each other or separately. For example, the positioning function (i.e., using the positioning application 420(1) in Figure 9) may be performed without the map display or route guidance functions.
- In connection with Figure 8, collections of data were described that were organized by type (or function). Various types and functions of data collections may be provided. For example, different collections of data may be provided for route guidance, map display, vehicle positioning, audio data, non-audio data, etc. When an end user computing platform requests geographic data, the type of data are indicated to the navigation services server. The type can be specified depending upon the resources supported by the end user's computing platform. The type can also be specified depending upon the function that the end user's platform needs the data to perform. For example, if the end user intends only to perform map display and not route guidance, the end user's computing platform may specify that data from the map display collection be sent. In this manner, the end user's computing platform is not sent data that it does not need, thereby allowing more data of the specified type to be sent.
- In addition to the types of data collections (232 in Figures 5-8) described above, the
downloadable data storage 124 in Figure 2 can include collections based on layer. Collections based on layer use a ranking assigned to roads in a geographic region. The ranking can be related to a functional classification of the roads. Major roads upon which travel is generally faster are assigned a higher ranking and minor roads upon which travel is generally slower are assigned a lower ranking. Using these rankings, data representing the higher ranked roads are stored in one or more separate collections from the lower ranked roads. - In addition to data representing a route and additional data representing geographic features along the route (or around another location), there are other kinds of data and information that the end user computing platforms may obtain from the navigation services provider. According to one embodiment, the navigation services provider may send navigation applications to an end user's computing platform. The navigation applications that the navigation services server sends to the end user's computing platform may be new applications or updates for prior versions of the navigation applications. The navigation applications that the navigation services provider sends may include any of the applications that are run on the end users' computer platforms, including route guidance, map display, positioning, query services, re-routing, memory management, etc. In one embodiment, these navigation applications are sent as applets or plug-ins. Referring again to Figure 2, in one embodiment, the
navigation services provider 128 maintains navigation applets (or plug-ins) 800 in adownloadable storage 802 on thenavigation services server 120. Then, upon request from an end user, thenavigation services server 120 sends the navigation applet or plug-in to the end user's computing platform. The applet or plug-in can be used in the end user's computing platform. The applet or plug-in can be used with another application installed on the end user's computing platform, such as a browser. In this embodiment, the end user identifies the type of navigation function that is desired and then the navigation services server sends the navigation applet (or plug-in) as well as the data to be used by the applet (or plug-in). As an example, if the end user wants to obtain route guidance, the navigation services server sends a route guidance applet, data indicating the route, and additional data representing the geographic features along the route. The route guidance applet, when downloaded into the end user's computing platform and properly installed, operates similarly to the route guidance application (420(2) in Figure 9). In this manner, both the software and the data for a function desired by the end user can be provided from the navigation services provider. - Several advantages follow from embodiments of the disclosed systems.
- As mentioned above, the
navigation system 110 supports many different kinds of end user computing platforms. If a navigation server had to determine the appropriate type of data to send to each different type of computing platform, it would place a considerable burden on the navigation server. Accordingly, the navigation server uses pre-computed data parcels, thereby facilitating this process. - The pre-computed data parcels are designed to be handled as the minimum size units of data that are transferred from the navigation server to the end users' computing platforms for use therein. Because the pre-computed parcels have a uniform size, the end user's computing platform can manage them easily.
- Another advantage follows from having a separate working database (122 in Figure 2) used by the navigation services server and downloadable geographic data (124 in Figure 2) for use by the end user computing platforms. The working database can be optimized for use by the server and the data contained in the downloadable geographic data storage can be optimized for use by the end users' computing platforms.
- Another advantage of the disclosed embodiments is that the pre-computed data parcels that are sent from the navigation services provider to the end users can be ensured to have connectivity. When data representing features along a route are sent to an end user, it is preferred that all the road segments that can be reached by the end user are represented. This can involve a significant amount of processing. Using any of the disclosed embodiments, when the pre-computed data parcels are formed, the connectivity of all the represented roads can be ensured.
- It is intended that the foregoing detailed description be regarded as illustrative rather than limiting and that it is understood that the following claims including all equivalents are intended to define the scope of the invention.
Claims (46)
- A server that provides geographic data for client computing platforms comprising:a repository for geographic data,wherein the repository contains data that represent geographic features located in a serviced geographic region, wherein the geographic region is divided into a plurality of pre-determined smaller sub-areas,wherein the data contained in the repository are organized into a plurality of uniform-sized parcels of data,wherein each of said uniform-sized parcels includes data that represent the geographic features located in a separate respective one of the plurality of smaller sub-areas; anda data downloading application run on said server that downloads one or more of said whole uniform-sized parcels of data from said repository to said client computing platforms, as needed, for use therein.
- The invention of Claim 1 further comprising:a working geographic database associated with said server and used by a navigation application on said server to perform a navigation-related function.
- The invention of Claim 2 wherein the navigation related function is route calculation.
- The invention of Claim 1 further comprising:a finder application associated with said server and adapted to find information about businesses based upon specified criteria.
- The invention of Claim 4 wherein the specified criteria include location-based criteria.
- The invention of Claim 4 wherein the finder application also finds information about persons.
- The invention of Claim 1 further comprising:a subscriber services application associated with said server and adapted to provide subscriber services to end users who access the said server.
- The invention of Claim 1 wherein the repository includes a plurality of collections of geographic data, wherein each collection represents the entire geographic region, wherein each collection is organized into a plurality of parcels of a uniform size, and wherein the parcels in one of said plurality of collections has a different uniform size than the parcels in another of said plurality of collections.
- The invention of Claim 1 wherein the repository includes a plurality of collections of geographic data, wherein each collection represents the entire geographic region, wherein each collection is organized into a plurality of parcels of a uniform size, and wherein the parcels in one of said plurality of collections contains data that represents different attributes of the represented geographic features than the parcels in another of said plurality of collections.
- The invention of Claim 1 wherein the server also includes a repository of downloadable applications for downloading and running on client computing platforms.
- The invention of Claim 10 wherein the downloadable applications are applets.
- The invention of Claim 10 wherein the downloadable applications are plug-ins.
- The invention of Claim 10 wherein the downloadable applications include a memory manager application.
- The invention of Claim 10 wherein the downloadable applications include updates for applications already installed on client computing platforms.
- The invention of Claim 10 wherein the downloadable applications are applets that run in a browser installed on a client computing platform.
- A method of operation for a navigation system comprising:on a server, receiving a request for geographic data from a client computing platform;determining which pre-computed parcels of geographic data stored with said server to send to the client computing platform to respond to said request, wherein each of the pre-computed parcels of geographic data in a collection thereof corresponds to a separate one of a plurality of geographic sub-areas into which a geographic region is divided; andsending the pre-computed parcels of geographic data that had been determined to the client computing platform.
- The method of Claim 16 further comprising:on said server, determining a route between an origin and a destination.
- The method of Claim 17 further comprising:sending data that indicates the route to the client computing platform.
- The method of Claim 17 wherein the step of determining comprises:identifying which of the geographic sub-areas are located along the route; anddetermining to send the pre-computed parcels of geographic data that represent the geographic sub-areas identified as being located along the route.
- The method of Claim 16 further comprising:selecting the collection from a plurality of different collections of pre-computed data parcels.
- The method of Claim 20 further comprising:receiving from the client computing platform an indication of which of said plurality of different collections to send data from.
- The method of Claim 20 wherein the step of selecting is preceded by accessing a subscriber database that indicates which collection to send data from.
- An architecture for a navigation system comprising:a server;client computing platforms;a network over which said client computing platforms and said server can communicate with each other;a geographic database associated with said server;a geographic data repository associated with said server and containing pre-computed parcels of geographic data, wherein each parcel in a collection represents geographic features located in a separate one of a plurality of geographic sub-areas into which a geographic region is divided; anda geographic data providing application on the server that determines which of said pre-computed parcels of geographic data to send to each of said client computing platforms in response to requests therefrom for geographic data.
- The invention of Claim 23 wherein the pre-computed parcels of geographic data in the collection have a uniform data size.
- The invention of Claim 23 wherein the collection is one of a plurality of collections of geographic data, each of which is organized into a plurality of pre-computed parcels, and wherein the plurality of pre-computed parcels in one of said plurality of collections has a different uniform data size than the plurality of pre-computed parcels in another of said collections.
- A method of managing memory resources in a client computing platform comprising the steps of:receiving uniform-sized predetermined parcels of data from a server,wherein each uniform-sized predetermined parcel of data contains data that represent geographic features located within a separate respective one of a plurality of sub-areas into which a geographic region is divided; andstoring said uniform-sized predetermined parcels of data in corresponding-sized portions of a cache memory in said client computing platform.
- The method of Claim 26 further comprising:using said uniform-sized predetermined parcels of data to display a map on said client computing platform.
- The method of Claim 27 wherein said map is a strip map.
- The method of Claim 27 further comprising:showing a calculated route on said map.
- The method of Claim 26 wherein the sub-areas corresponding to said uniform-sized predetermined parcels of data received by said client computing platform overlap a portion of a calculated route.
- The method of Claim 30 wherein the route is calculated on the server.
- The method of Claim 26 wherein the uniform-sized predetermined parcels of data received by said client computing platform include separate types of data contained in separate uniform-sized predetermined parcels of data.
- The method of Claim 26 wherein the uniform-sized predetermined parcels of data received by said client computing platform include separate types of data contained in each uniform-sized predetermined parcels of data.
- The method of Claim 26 further comprising:prior to receiving the uniform-sized predetermined parcels of data from the server, on the client computing platform, identifying types of data needed to support functions provided by the client computing platform.
- The method of Claim 26 further comprising:using the data contained in said uniform-sized predetermined parcels of data to provide route guidance.
- The method of Claim 26 further comprising:using the data contained in said uniform-sized predetermined parcels of data to explicate a calculated route.
- The method of Claim 26 wherein the sub-areas corresponding to said uniform-sized predetermined parcels of data received by said client computing platform overlap an initial portion of a calculated route; and as the client computing platform travels along the calculated route, obtaining additional uniform-sized predetermined parcels of data corresponding to sub-areas that overlap subsequent portions of said calculated route.
- The method of Claim 26 further comprising:determining a position of the client computing platform relative to roads represented by data contained in said uniform-sized predetermined parcels of data received by said client computing platform.
- The method of Claim 26 further comprising:determining whether said client computing platform has departed from a calculated route.
- The method of Claim 39 further comprising:calculating a way back to said calculated route using data contained in said uniform-sized predetermined parcels of data received by said client computing platform.
- The method of Claim 26 further comprising:downloading an application from the server to be run on said client computing platform.
- The method of Claim 41 wherein the application downloaded from the server is an applet.
- The method of Claim 41 wherein the application downloaded from the server is a plug-in.
- The method of Claim 41 wherein the application downloaded from the server runs in a browser on the client computing platform.
- The method of Claim 26 further comprising:receiving data from the server that indicates a route between an origin and destination, wherein the route was calculated on the server.
- The method of Claim 45 further comprising:from the client computing platform, specifying the origin and destination to the server prior to receiving data from the server that indicates the route.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/838,094 US6691128B2 (en) | 2001-04-19 | 2001-04-19 | Navigation system with distributed computing architecture |
US838094 | 2001-04-19 |
Publications (3)
Publication Number | Publication Date |
---|---|
EP1251335A2 true EP1251335A2 (en) | 2002-10-23 |
EP1251335A3 EP1251335A3 (en) | 2007-03-14 |
EP1251335B1 EP1251335B1 (en) | 2010-01-06 |
Family
ID=25276244
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP02252660A Expired - Lifetime EP1251335B1 (en) | 2001-04-19 | 2002-04-15 | Navigation system with distributed computing architecture |
Country Status (5)
Country | Link |
---|---|
US (2) | US6691128B2 (en) |
EP (1) | EP1251335B1 (en) |
JP (2) | JP4460816B2 (en) |
AT (1) | ATE454609T1 (en) |
DE (1) | DE60234975D1 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1529196A1 (en) * | 2003-02-24 | 2005-05-11 | Harman Becker Automotive Systems GmbH | Navigation system with acoustic route information |
EP1909066A1 (en) * | 2006-10-05 | 2008-04-09 | Research In Motion Limited | Improved Data Retrieval Method for Location Based Services on a Wireless Device |
FR2924848A1 (en) * | 2008-03-25 | 2009-06-12 | Valeo Securite Habitacle Sas | Vehicle's localization indicating system, has CPU with data transmission units that transmit data towards data reception units, where data includes characteristic latitude and longitude of position of vehicle |
WO2009122851A1 (en) | 2008-03-31 | 2009-10-08 | Aisin Aw Co., Ltd. | Map updating system and map updating program using dynamic cache memory |
EP2144039A2 (en) | 2008-07-11 | 2010-01-13 | Samsung Electronics Co., Ltd. | Navigation Service System and Method Using Mobile Device |
EP2196772A1 (en) * | 2008-12-15 | 2010-06-16 | Research In Motion Limited | Pre-loading waypoint data |
WO2011122338A1 (en) * | 2010-03-31 | 2011-10-06 | Aisin Aw Co., Ltd. | Map data management device, map data management method, and information terminal |
EP2679957A1 (en) * | 2011-12-20 | 2014-01-01 | Technisat Digital Gmbh | Navigation device for outputting a speed value to a user |
US8682340B2 (en) | 2006-10-05 | 2014-03-25 | Blackberry Limited | Data retrieval method for location based services on a wireless device |
US9062982B2 (en) | 2008-12-15 | 2015-06-23 | Blackberry Limited | Pre-loading waypoint data |
WO2018218149A1 (en) * | 2017-05-26 | 2018-11-29 | Google Llc | Data fusion system |
EP2543963B1 (en) * | 2011-07-08 | 2020-05-13 | Harman Becker Automotive Systems GmbH | Method of updating a database of a navigation device and navigation device associated thereto |
US11187541B2 (en) | 2008-05-09 | 2021-11-30 | Blackberry Limited | Predictive downloading of map data |
US11885625B1 (en) | 2022-10-03 | 2024-01-30 | Googe Llc | Data fusion system |
Families Citing this family (101)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003042771A (en) * | 2001-07-31 | 2003-02-13 | Pioneer Electronic Corp | Method for updating map data in communication navigation system, server apparatus, record medium, and communication navigation terminal apparatus |
JP2003044992A (en) * | 2001-07-31 | 2003-02-14 | Pioneer Electronic Corp | Updating method for map data in communication navigation system, and server device, recording medium and communication navigation terminal device |
JP2003090734A (en) * | 2001-09-20 | 2003-03-28 | Pioneer Electronic Corp | Navigation information providing system, navigation server, and navigation terminal |
US7092957B2 (en) * | 2002-01-18 | 2006-08-15 | Boundary Solutions Incorporated | Computerized national online parcel-level map data portal |
JP3698106B2 (en) * | 2002-02-14 | 2005-09-21 | 日産自動車株式会社 | Information providing apparatus and method |
JP2003271052A (en) * | 2002-03-15 | 2003-09-25 | Denso Corp | Spot specifying code providing method |
US6847888B2 (en) * | 2002-08-07 | 2005-01-25 | Hrl Laboratories, Llc | Method and apparatus for geographic shape preservation for identification |
US8560223B2 (en) * | 2002-08-29 | 2013-10-15 | Mapquest, Inc. | Automated route determination |
US7474960B1 (en) | 2002-12-30 | 2009-01-06 | Mapquest, Inc. | Presenting a travel route |
JP4048994B2 (en) * | 2003-04-10 | 2008-02-20 | ソニー株式会社 | Navigation device |
US7099882B2 (en) * | 2003-04-29 | 2006-08-29 | Navteq North America, Llc | Method and system for forming, updating, and using a geographic database |
US7324896B1 (en) | 2003-08-04 | 2008-01-29 | Aol Llc | Using a corridor search to identify locations of interest along a travel route |
US6954697B1 (en) * | 2003-08-04 | 2005-10-11 | America Online, Inc. | Using a corridor search to identify locations of interest along a route |
JP2005181146A (en) * | 2003-12-19 | 2005-07-07 | Aisin Aw Co Ltd | Information delivery system and program for information delivery method |
US7146271B2 (en) * | 2003-12-23 | 2006-12-05 | Honda Motor Co., Ltd. | System and method for managing navigation information |
US7027916B2 (en) | 2003-12-23 | 2006-04-11 | Honda Motor Co., Ltd. | Method of formatting navigation information with varying levels of detail |
US7184888B2 (en) * | 2003-12-23 | 2007-02-27 | Honda Motor Co., Ltd. | System and method for transferring navigation information using different coordinate systems |
US7263438B2 (en) * | 2003-12-23 | 2007-08-28 | Honda Motor Co., Ltd. | Smart storage and transmission of navigation information |
US7480561B2 (en) * | 2003-12-23 | 2009-01-20 | Honda Motor Co., Ltd. | Prioritized delivery of navigation information |
US7206696B2 (en) * | 2004-05-19 | 2007-04-17 | Honda Motor Co., Ltd. | Method for modifying navigation information |
US7292936B2 (en) * | 2004-05-19 | 2007-11-06 | Honda Motor Co., Ltd. | System and method for displaying information |
US20050261829A1 (en) * | 2004-05-19 | 2005-11-24 | Honda Motor Co., Ltd. | System and method for off route processing |
US20050261824A1 (en) * | 2004-05-19 | 2005-11-24 | Honda Motor Co., Ltd. | System and method for varying content |
US7672778B1 (en) * | 2004-07-20 | 2010-03-02 | Navteq North America, Llc | Navigation system with downloaded map data |
KR100754168B1 (en) * | 2004-11-12 | 2007-09-03 | 삼성전자주식회사 | Method and apparatus for updating map data, and recording medium storing a program to implement thereof |
JP4271651B2 (en) * | 2004-12-13 | 2009-06-03 | 三菱電機株式会社 | Navigation system |
US20060235856A1 (en) * | 2004-12-16 | 2006-10-19 | Halcrow Michael A | Route generation for task completion by a location-aware device |
US7236882B2 (en) * | 2005-01-26 | 2007-06-26 | Broadcom Corporation | Downloading map segment(s) to a cell phone based upon its GPS coordinates and mobility |
US8635014B2 (en) * | 2005-03-22 | 2014-01-21 | The Invention Science Fund I, Llc | Map-based guide system and method |
US20060217880A1 (en) * | 2005-03-22 | 2006-09-28 | Jung Edward K | Map-based guide system and method |
DE102005008395A1 (en) * | 2005-02-24 | 2006-08-31 | Deutsche Telekom Ag | Navigation information delivering method e.g. for users of mobile telecommunication terminal, involves dialing telephone number of navigation value-added service provider from mobile terminal, and transmitting navigation request |
US9601015B2 (en) * | 2005-02-25 | 2017-03-21 | Concaten, Inc. | Maintenance decision support system and method for vehicular and roadside applications |
US20220343759A1 (en) * | 2005-02-25 | 2022-10-27 | Concaten, Inc. | Maintenance Decision Support System and Method for Vehicular and Roadside Applications |
US20060200302A1 (en) * | 2005-03-04 | 2006-09-07 | Twin Communications Of America, Inc. | Navigation system |
US20070266239A1 (en) * | 2006-03-08 | 2007-11-15 | David Vismans | Method for providing a cryptographically signed command |
US9953097B2 (en) * | 2006-03-16 | 2018-04-24 | Ebay Inc. | System and method for managing network traffic routing |
SG136825A1 (en) * | 2006-04-20 | 2007-11-29 | Mitac Int Corp | Navigation provision system and framework for providing content to an end user |
WO2007124504A2 (en) * | 2006-04-21 | 2007-11-01 | Mediamote, Inc. | Collection and distribution of sense-on-demand data |
US8630768B2 (en) | 2006-05-22 | 2014-01-14 | Inthinc Technology Solutions, Inc. | System and method for monitoring vehicle parameters and driver behavior |
US9067565B2 (en) | 2006-05-22 | 2015-06-30 | Inthinc Technology Solutions, Inc. | System and method for evaluating driver behavior |
US8775079B2 (en) * | 2006-07-07 | 2014-07-08 | General Motors Llc | Method for storing off-board navigation destination locations |
EP1879001B1 (en) * | 2006-07-10 | 2016-04-27 | Harman Becker Automotive Systems GmbH | Format description for a navigation database |
WO2008047448A1 (en) * | 2006-10-20 | 2008-04-24 | Pioneer Corporation | Map data updating device, map data updating method, map data updating program, and recording medium |
US7831431B2 (en) * | 2006-10-31 | 2010-11-09 | Honda Motor Co., Ltd. | Voice recognition updates via remote broadcast signal |
US9129460B2 (en) | 2007-06-25 | 2015-09-08 | Inthinc Technology Solutions, Inc. | System and method for monitoring and improving driver behavior |
US8818618B2 (en) * | 2007-07-17 | 2014-08-26 | Inthinc Technology Solutions, Inc. | System and method for providing a user interface for vehicle monitoring system users and insurers |
US9117246B2 (en) | 2007-07-17 | 2015-08-25 | Inthinc Technology Solutions, Inc. | System and method for providing a user interface for vehicle mentoring system users and insurers |
ES2562920T3 (en) * | 2007-09-13 | 2016-03-09 | Continental Teves Ag & Co. Ohg | Critical map update in terms of security through a data channel of a satellite navigation system |
US8359157B2 (en) * | 2008-04-07 | 2013-01-22 | Microsoft Corporation | Computing navigation device with enhanced route directions view |
JP4423349B2 (en) * | 2008-04-28 | 2010-03-03 | 株式会社ナビタイムジャパン | Route guidance system, route search server, route guidance method, and terminal device |
WO2009152515A2 (en) * | 2008-06-13 | 2009-12-17 | Blue Dasher Technologies, Inc. | Street-level routing |
US8103441B2 (en) * | 2008-06-26 | 2012-01-24 | Microsoft Corporation | Caching navigation content for intermittently connected devices |
US9200908B2 (en) * | 2008-07-17 | 2015-12-01 | Volkswagen Ag | Navigation system for a motor vehicle |
US9202375B2 (en) * | 2008-07-17 | 2015-12-01 | Volkswagen Ag | Navigation system for a motor vehicle |
US20100023251A1 (en) * | 2008-07-25 | 2010-01-28 | Gale William N | Cost based open area maps |
US8099237B2 (en) | 2008-07-25 | 2012-01-17 | Navteq North America, Llc | Open area maps |
US8417446B2 (en) * | 2008-07-25 | 2013-04-09 | Navteq B.V. | Link-node maps based on open area maps |
US8229176B2 (en) | 2008-07-25 | 2012-07-24 | Navteq B.V. | End user image open area maps |
US20100021013A1 (en) * | 2008-07-25 | 2010-01-28 | Gale William N | Open area maps with guidance |
US8825387B2 (en) * | 2008-07-25 | 2014-09-02 | Navteq B.V. | Positioning open area maps |
US8374780B2 (en) * | 2008-07-25 | 2013-02-12 | Navteq B.V. | Open area maps with restriction content |
US20100082564A1 (en) * | 2008-10-01 | 2010-04-01 | Navteq North America, Llc | Spatial Index for Locating Geographic Data Parcels Stored on Physical Storage Media |
US8832599B2 (en) * | 2008-10-03 | 2014-09-09 | Microsoft Corporation | Assisted navigation in virtual environments |
WO2010047580A1 (en) * | 2008-10-21 | 2010-04-29 | Telefonaktiebolaget Lm Ericsson (Publ) | Reporting of changes in navigation map data for navigation system |
JP5163427B2 (en) * | 2008-10-31 | 2013-03-13 | アイシン・エィ・ダブリュ株式会社 | In-vehicle navigation destination search apparatus and in-vehicle navigation destination search method |
US8219316B2 (en) * | 2008-11-14 | 2012-07-10 | Google Inc. | System and method for storing and providing routes |
US20100138412A1 (en) * | 2008-12-01 | 2010-06-03 | Ing-Kai Huang | Method for showing objects of geographic information by seriation of distance |
US8963702B2 (en) | 2009-02-13 | 2015-02-24 | Inthinc Technology Solutions, Inc. | System and method for viewing and correcting data in a street mapping database |
US20100222996A1 (en) * | 2009-02-27 | 2010-09-02 | Navteq North America, Llc | Dual Representation of an Address in a Database |
US20100250384A1 (en) * | 2009-03-28 | 2010-09-30 | Ashish Bhargava | Method and system for electronically ordering goods or services |
US8627007B1 (en) | 2009-10-28 | 2014-01-07 | Juniper Networks, Inc. | Use of cache to reduce memory bandwidth pressure with processing pipeline |
PT2325807E (en) * | 2009-11-23 | 2012-05-17 | Kapsch Trafficcom Ag | Method and device for generating toll information in a road toll system |
US8566346B2 (en) | 2010-08-06 | 2013-10-22 | Navteq B.V. | Page server for navigation data |
US8683008B1 (en) | 2011-08-04 | 2014-03-25 | Google Inc. | Management of pre-fetched mapping data incorporating user-specified locations |
US8280414B1 (en) | 2011-09-26 | 2012-10-02 | Google Inc. | Map tile data pre-fetching based on mobile device generated event analysis |
US8983973B2 (en) * | 2011-10-12 | 2015-03-17 | Mapquest, Inc. | Systems and methods for ranking points of interest |
US9275374B1 (en) | 2011-11-15 | 2016-03-01 | Google Inc. | Method and apparatus for pre-fetching place page data based upon analysis of user activities |
US9063951B1 (en) * | 2011-11-16 | 2015-06-23 | Google Inc. | Pre-fetching map data based on a tile budget |
US8711181B1 (en) | 2011-11-16 | 2014-04-29 | Google Inc. | Pre-fetching map data using variable map tile radius |
US8886715B1 (en) * | 2011-11-16 | 2014-11-11 | Google Inc. | Dynamically determining a tile budget when pre-fetching data in a client device |
US9305107B2 (en) | 2011-12-08 | 2016-04-05 | Google Inc. | Method and apparatus for pre-fetching place page data for subsequent display on a mobile computing device |
US9197713B2 (en) | 2011-12-09 | 2015-11-24 | Google Inc. | Method and apparatus for pre-fetching remote resources for subsequent display on a mobile computing device |
US8803920B2 (en) | 2011-12-12 | 2014-08-12 | Google Inc. | Pre-fetching map tile data along a route |
US9389088B2 (en) | 2011-12-12 | 2016-07-12 | Google Inc. | Method of pre-fetching map data for rendering and offline routing |
US8971928B2 (en) * | 2012-04-10 | 2015-03-03 | Here Global B.V. | Method and system for changing geographic information displayed on a mobile device |
US9453734B2 (en) * | 2012-06-05 | 2016-09-27 | Apple Inc. | Smart loading of map tiles |
US8949196B2 (en) | 2012-12-07 | 2015-02-03 | Google Inc. | Systems and methods for matching similar geographic objects |
US9689680B2 (en) * | 2013-06-04 | 2017-06-27 | Here Global B.V. | Method and apparatus for approaches to provide for combining contexts related to items of interest and navigation |
JP6145355B2 (en) * | 2013-08-07 | 2017-06-07 | Kddi株式会社 | Map display device, program, system and method for controlling scale of map image according to object distribution |
KR101734609B1 (en) * | 2013-11-12 | 2017-05-11 | 현대자동차주식회사 | Telematics system for guiding multiple path |
US10086857B2 (en) * | 2013-11-27 | 2018-10-02 | Shanmukha Sravan Puttagunta | Real time machine vision system for train control and protection |
US9796400B2 (en) | 2013-11-27 | 2017-10-24 | Solfice Research, Inc. | Real time machine vision and point-cloud analysis for remote sensing and vehicle control |
US9633474B2 (en) * | 2014-05-20 | 2017-04-25 | Here Global B.V. | Method and apparatus for generating a composite indexable linear data structure to permit selection of map elements based on linear elements |
US9569745B1 (en) * | 2015-07-27 | 2017-02-14 | Amazon Technologies, Inc. | Dynamic vehicle routing for regional clusters |
JP2017090092A (en) * | 2015-11-04 | 2017-05-25 | 株式会社デンソー | Onboard download control device, and download control method |
EP3196858B1 (en) | 2016-01-21 | 2020-10-21 | HERE Global B.V. | An apparatus and associated methods for indicating road data gatherer upload zones |
CN107806883B (en) * | 2016-09-08 | 2020-02-18 | 高德信息技术有限公司 | Navigation method and device |
US10959052B2 (en) * | 2016-12-13 | 2021-03-23 | Lenovo (Singapore) Pte. Ltd. | Local memory direction caching |
CN109241214B (en) * | 2018-07-27 | 2021-09-10 | 珠海国津软件科技有限公司 | Method for forming service map drawing according to service directory |
US11293770B2 (en) * | 2018-08-02 | 2022-04-05 | salesforces.com, Inc. | Geographic routing engine |
US10467562B1 (en) * | 2019-02-18 | 2019-11-05 | Coupang, Corp. | Systems and methods for computerized balanced delivery route assignment |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5953722A (en) | 1996-10-25 | 1999-09-14 | Navigation Technologies Corporation | Method and system for forming and using geographic data |
US5968109A (en) | 1996-10-25 | 1999-10-19 | Navigation Technologies Corporation | System and method for use and storage of geographic data on physical media |
US5974419A (en) | 1996-10-25 | 1999-10-26 | Navigation Technologies Corporation | Parcelization of geographic data for storage and use in a navigation application |
Family Cites Families (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4954958A (en) * | 1988-08-19 | 1990-09-04 | Hacowie Corporation | Directional information system |
US5636122A (en) * | 1992-10-16 | 1997-06-03 | Mobile Information Systems, Inc. | Method and apparatus for tracking vehicle location and computer aided dispatch |
US5408597A (en) * | 1993-07-29 | 1995-04-18 | Digital Equipment Corporation | Method and apparatus for schematic routing |
US5777618A (en) * | 1993-07-29 | 1998-07-07 | Digital Equipment Corporation | Method and apparatus for graphical panning |
US6321158B1 (en) * | 1994-06-24 | 2001-11-20 | Delorme Publishing Company | Integrated routing/mapping information |
US5848373A (en) * | 1994-06-24 | 1998-12-08 | Delorme Publishing Company | Computer aided map location system |
US5559707A (en) * | 1994-06-24 | 1996-09-24 | Delorme Publishing Company | Computer aided routing system |
US5543789A (en) | 1994-06-24 | 1996-08-06 | Shields Enterprises, Inc. | Computerized navigation system |
EP0805951B1 (en) * | 1994-10-07 | 2000-01-19 | MANNESMANN Aktiengesellschaft | Target input for a navigation system |
JPH09305108A (en) * | 1996-03-11 | 1997-11-28 | Denso Corp | Method and device for specifying location, and method and device for displaying map using them |
JPH09325040A (en) * | 1996-06-05 | 1997-12-16 | Matsushita Electric Ind Co Ltd | Map information display apparatus for vehicle |
JPH10103993A (en) * | 1996-10-01 | 1998-04-24 | Sumitomo Electric Ind Ltd | Map-data transmission system |
US6047280A (en) * | 1996-10-25 | 2000-04-04 | Navigation Technologies Corporation | Interface layer for navigation system |
US5944769A (en) | 1996-11-08 | 1999-08-31 | Zip2 Corporation | Interactive network directory service with integrated maps and directions |
JP3897134B2 (en) | 1997-03-11 | 2007-03-22 | ソニー株式会社 | Image display apparatus and method |
FR2761837B1 (en) | 1997-04-08 | 1999-06-11 | Sophie Sommelet | NAVIGATION AID DEVICE HAVING A DISTRIBUTED INTERNET-BASED ARCHITECTURE |
US6707421B1 (en) * | 1997-08-19 | 2004-03-16 | Siemens Vdo Automotive Corporation | Driver information system |
JP3317211B2 (en) * | 1997-09-24 | 2002-08-26 | 松下電器産業株式会社 | Map editing device |
JP3507309B2 (en) * | 1997-11-05 | 2004-03-15 | 株式会社日立製作所 | Travel support system and method |
US6121924A (en) * | 1997-12-30 | 2000-09-19 | Navigation Technologies Corporation | Method and system for providing navigation systems with updated geographic data |
US6014629A (en) * | 1998-01-13 | 2000-01-11 | Moore U.S.A. Inc. | Personalized health care provider directory |
US6332154B2 (en) * | 1998-09-11 | 2001-12-18 | Genesys Telecommunications Laboratories, Inc. | Method and apparatus for providing media-independent self-help modules within a multimedia communication-center customer interface |
US6112200A (en) * | 1998-03-16 | 2000-08-29 | Navigation Technologies Corporation | Interleaving of data types in a geographic database and methods for application |
US6038559A (en) * | 1998-03-16 | 2000-03-14 | Navigation Technologies Corporation | Segment aggregation in a geographic database and methods for use thereof in a navigation application |
US6073076A (en) * | 1998-03-27 | 2000-06-06 | Navigation Technologies Corporation | Memory management for navigation system |
US6184823B1 (en) * | 1998-05-01 | 2001-02-06 | Navigation Technologies Corp. | Geographic database architecture for representation of named intersections and complex intersections and methods for formation thereof and use in a navigation application program |
US6393149B2 (en) * | 1998-09-17 | 2002-05-21 | Navigation Technologies Corp. | Method and system for compressing data and a geographic database formed therewith and methods for use thereof in a navigation application program |
WO2000022593A1 (en) * | 1998-10-14 | 2000-04-20 | Siemens Automotive Corporation | Driver information system |
JP2000123290A (en) * | 1998-10-14 | 2000-04-28 | Toyota Motor Corp | Vehicle map data transmission and reception system |
US6212474B1 (en) * | 1998-11-19 | 2001-04-03 | Navigation Technologies Corporation | System and method for providing route guidance with a navigation application program |
JP3332225B2 (en) | 1998-11-24 | 2002-10-07 | 松下電器産業株式会社 | Map providing system |
US6154658A (en) * | 1998-12-14 | 2000-11-28 | Lockheed Martin Corporation | Vehicle information and safety control system |
BE1012457A3 (en) | 1999-02-02 | 2000-11-07 | Smartmove Nv | Process for the provision of navigation data to a vehicle and navigation system that applying this process. |
JP2000236571A (en) * | 1999-02-16 | 2000-08-29 | Toshiba Corp | Information management system in facilities and portable terminal |
US6513019B2 (en) * | 1999-02-16 | 2003-01-28 | Financial Technologies International, Inc. | Financial consolidation and communication platform |
DE19906863A1 (en) * | 1999-02-18 | 2000-10-19 | Nokia Mobile Phones Ltd | Procedure for navigating an object |
DE60027499T2 (en) * | 1999-03-05 | 2006-11-16 | Hitachi, Ltd. | Information presentation system for mobile units |
JP2001012960A (en) * | 1999-06-28 | 2001-01-19 | Hitachi Ltd | Information distribution system |
JP2000283777A (en) * | 1999-03-30 | 2000-10-13 | Alpine Electronics Inc | Car-carried navigation system |
AU4481600A (en) * | 1999-04-22 | 2000-11-10 | Qode.Com, Inc. | System and method for providing electronic information upon receipt of a scannedbar code |
JP2001012957A (en) | 1999-06-29 | 2001-01-19 | Mitsubishi Electric Corp | Map updating system for car navigator and car navigation terminal |
JP3225958B2 (en) | 1999-12-27 | 2001-11-05 | 株式会社エクォス・リサーチ | Navigation method, route providing device, route guidance device |
JP3596805B2 (en) | 1999-07-29 | 2004-12-02 | 松下電器産業株式会社 | Information terminal device and route guidance method |
WO2001013069A1 (en) * | 1999-08-12 | 2001-02-22 | Kivera, Inc. | Method and apparatus for providing location-dependent services to mobile users |
JP3772951B2 (en) * | 1999-09-13 | 2006-05-10 | 株式会社デンソー | Map information distribution center and map information display device |
GB2360421B (en) * | 1999-11-10 | 2004-02-18 | Ibm | Transmission of geographic information to mobile devices |
JP2001188734A (en) * | 1999-12-28 | 2001-07-10 | Honda Motor Co Ltd | Electronic mail transmitting and receiving system |
JP3475142B2 (en) * | 2000-03-01 | 2003-12-08 | 三菱電機株式会社 | Map data transmission device, map data transmission method, and computer-readable recording medium recording a program for causing a computer to execute the map data transmission method |
JP4467709B2 (en) * | 2000-03-29 | 2010-05-26 | 本田技研工業株式会社 | Mobile navigation device |
US6487495B1 (en) * | 2000-06-02 | 2002-11-26 | Navigation Technologies Corporation | Navigation applications using related location-referenced keywords |
US6278939B1 (en) * | 2000-07-24 | 2001-08-21 | Navigation Technologies Corp. | Method and system for providing data from a remotely located geographic database for use in navigation system units |
-
2001
- 2001-04-19 US US09/838,094 patent/US6691128B2/en not_active Expired - Lifetime
-
2002
- 2002-04-15 DE DE60234975T patent/DE60234975D1/en not_active Expired - Lifetime
- 2002-04-15 AT AT02252660T patent/ATE454609T1/en not_active IP Right Cessation
- 2002-04-15 EP EP02252660A patent/EP1251335B1/en not_active Expired - Lifetime
- 2002-04-19 JP JP2002154729A patent/JP4460816B2/en not_active Expired - Fee Related
-
2003
- 2003-11-25 US US10/721,660 patent/US7801904B2/en not_active Expired - Lifetime
-
2008
- 2008-03-26 JP JP2008080957A patent/JP4928490B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5953722A (en) | 1996-10-25 | 1999-09-14 | Navigation Technologies Corporation | Method and system for forming and using geographic data |
US5968109A (en) | 1996-10-25 | 1999-10-19 | Navigation Technologies Corporation | System and method for use and storage of geographic data on physical media |
US5974419A (en) | 1996-10-25 | 1999-10-26 | Navigation Technologies Corporation | Parcelization of geographic data for storage and use in a navigation application |
Cited By (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1529196A1 (en) * | 2003-02-24 | 2005-05-11 | Harman Becker Automotive Systems GmbH | Navigation system with acoustic route information |
EP1529196A4 (en) * | 2003-02-24 | 2011-06-01 | Harman Becker Automotive Sys | Navigation system with acoustic route information |
US8682340B2 (en) | 2006-10-05 | 2014-03-25 | Blackberry Limited | Data retrieval method for location based services on a wireless device |
EP1909066A1 (en) * | 2006-10-05 | 2008-04-09 | Research In Motion Limited | Improved Data Retrieval Method for Location Based Services on a Wireless Device |
FR2924848A1 (en) * | 2008-03-25 | 2009-06-12 | Valeo Securite Habitacle Sas | Vehicle's localization indicating system, has CPU with data transmission units that transmit data towards data reception units, where data includes characteristic latitude and longitude of position of vehicle |
WO2009122851A1 (en) | 2008-03-31 | 2009-10-08 | Aisin Aw Co., Ltd. | Map updating system and map updating program using dynamic cache memory |
RU2458392C2 (en) * | 2008-03-31 | 2012-08-10 | Аисин Ав Ко., Лтд. | Map updating system and map updating program using dynamic cache memory |
US8769237B2 (en) | 2008-03-31 | 2014-07-01 | Aisin Aw Co., Ltd. | Map updating system and map updating program using dynamic cache memory |
US11187541B2 (en) | 2008-05-09 | 2021-11-30 | Blackberry Limited | Predictive downloading of map data |
EP2144039A2 (en) | 2008-07-11 | 2010-01-13 | Samsung Electronics Co., Ltd. | Navigation Service System and Method Using Mobile Device |
EP2144039A3 (en) * | 2008-07-11 | 2010-03-17 | Samsung Electronics Co., Ltd. | Navigation Service System and Method Using Mobile Device |
US8775067B2 (en) | 2008-07-11 | 2014-07-08 | Samsung Electronics Co., Ltd. | Navigation service system and method using mobile device |
EP2196772A1 (en) * | 2008-12-15 | 2010-06-16 | Research In Motion Limited | Pre-loading waypoint data |
US9062982B2 (en) | 2008-12-15 | 2015-06-23 | Blackberry Limited | Pre-loading waypoint data |
CN102822629A (en) * | 2010-03-31 | 2012-12-12 | 爱信艾达株式会社 | Map data management device, map data management method, and information terminal |
WO2011122338A1 (en) * | 2010-03-31 | 2011-10-06 | Aisin Aw Co., Ltd. | Map data management device, map data management method, and information terminal |
EP2543963B1 (en) * | 2011-07-08 | 2020-05-13 | Harman Becker Automotive Systems GmbH | Method of updating a database of a navigation device and navigation device associated thereto |
EP2679957A1 (en) * | 2011-12-20 | 2014-01-01 | Technisat Digital Gmbh | Navigation device for outputting a speed value to a user |
WO2018218149A1 (en) * | 2017-05-26 | 2018-11-29 | Google Llc | Data fusion system |
WO2018218146A1 (en) * | 2017-05-26 | 2018-11-29 | Google Llc | Data layers for a vehicle map service |
WO2018218142A1 (en) * | 2017-05-26 | 2018-11-29 | Google Llc | Vehicle map service system |
US11436539B2 (en) | 2017-05-26 | 2022-09-06 | Google Llc | Vehicle map service system |
US11461705B2 (en) | 2017-05-26 | 2022-10-04 | Google Llc | Data fusion system |
US11838836B2 (en) | 2017-05-26 | 2023-12-05 | Google Llc | Data layers for a vehicle map service |
US11885625B1 (en) | 2022-10-03 | 2024-01-30 | Googe Llc | Data fusion system |
Also Published As
Publication number | Publication date |
---|---|
DE60234975D1 (en) | 2010-02-25 |
JP4460816B2 (en) | 2010-05-12 |
JP2008175830A (en) | 2008-07-31 |
US20040107220A1 (en) | 2004-06-03 |
US6691128B2 (en) | 2004-02-10 |
EP1251335A3 (en) | 2007-03-14 |
US7801904B2 (en) | 2010-09-21 |
JP4928490B2 (en) | 2012-05-09 |
JP2003090735A (en) | 2003-03-28 |
ATE454609T1 (en) | 2010-01-15 |
EP1251335B1 (en) | 2010-01-06 |
US20020169778A1 (en) | 2002-11-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6691128B2 (en) | Navigation system with distributed computing architecture | |
US6292745B1 (en) | Method and system for forming a database of geographic data for distribution to navigation system units | |
US11243088B2 (en) | System and method for storing and providing routes | |
US8010227B2 (en) | Navigation system with downloadable map data | |
US6278939B1 (en) | Method and system for providing data from a remotely located geographic database for use in navigation system units | |
US7079945B1 (en) | Geographic database including data indicating wireless coverage and method and system for use thereof | |
US6553310B1 (en) | Method of and apparatus for topologically based retrieval of information | |
US6947976B1 (en) | System and method for providing location-based and time-based information to a user of a handheld device | |
EP2351987B1 (en) | Method of operating a navigation system to provide geographic location information | |
EP1202029B1 (en) | Method and system for compact representation of routes | |
US20070233384A1 (en) | Method and system for off-board navigation with a portable device | |
US20100241351A1 (en) | Identifying a result responsive to a current location of a client device | |
WO2003063521A2 (en) | Routing framework | |
US6725156B2 (en) | Method and system for providing backup driving instructions with a navigation system | |
JP4243469B2 (en) | Navigation system that supports multiple languages and formats | |
Biswas et al. | Location-based Services |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
AX | Request for extension of the european patent |
Free format text: AL;LT;LV;MK;RO;SI |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NAVTEQ NORTH AMERICA, LLC |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G01C 21/34 20060101AFI20020814BHEP Ipc: G01C 21/32 20060101ALI20060920BHEP |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK RO SI |
|
17P | Request for examination filed |
Effective date: 20070502 |
|
17Q | First examination report despatched |
Effective date: 20070615 |
|
AKX | Designation fees paid |
Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NAVTEQ NORTH AMERICA, LLC |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAC | Information related to communication of intention to grant a patent modified |
Free format text: ORIGINAL CODE: EPIDOSCIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 60234975 Country of ref document: DE Date of ref document: 20100225 Kind code of ref document: P |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20100106 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100506 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100417 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100407 Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100430 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
26N | No opposition filed |
Effective date: 20101007 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100415 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100430 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100430 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100415 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100106 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20130410 Year of fee payment: 12 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20130625 Year of fee payment: 12 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20140415 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20141231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140415 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20140430 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 60234975 Country of ref document: DE Owner name: HERE GLOBAL B.V., NL Free format text: FORMER OWNER: NAVTEQ NORTH AMERICA, LLC, CHICAGO, ILL., US |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20210316 Year of fee payment: 20 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R071 Ref document number: 60234975 Country of ref document: DE |