US20020087262A1 - Method of navigation guidance - Google Patents
Method of navigation guidance Download PDFInfo
- Publication number
- US20020087262A1 US20020087262A1 US09/753,833 US75383301A US2002087262A1 US 20020087262 A1 US20020087262 A1 US 20020087262A1 US 75383301 A US75383301 A US 75383301A US 2002087262 A1 US2002087262 A1 US 2002087262A1
- Authority
- US
- United States
- Prior art keywords
- communications node
- route
- remote communications
- location
- navigation route
- 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/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
- G01C21/3446—Details of route searching algorithms, e.g. Dijkstra, A*, arc-flags, using precalculated routes
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
- G08G1/0969—Systems involving transmission of navigation instructions to the vehicle having a display in the form of a map
Definitions
- This invention relates generally to navigation guidance and, in particular to a method of navigation guidance for a remote communications node.
- a distributed navigation system generally has a navigation server component where navigation data is stored and a client component for route guidance.
- the client component can be an in-vehicle device or some other portable wireless device with a method of determining position.
- Prior art methods of providing navigation guidance for client components have numerous deficiencies. For example, existing navigation systems that download route data only download a single route from an origin point to a destination point. When the client component is moving, the client's position changes between the time the route is requested and the time the route data arrives at the client. The client component may move a large distance during route download, and may in fact pass the first maneuver point on the route. If this happens, the entire route becomes useless and the client component must request a new route.
- Another problem with this method occurs where there are numerous routes available from the starting location of the client component.
- Existing guidance systems will only provide one route from the starting location, which may not even be available or accessible to the user of the client component. This can occur in vehicle applications where the vehicle is in a parking lot and the beginning of the route downloaded starts on a street that is not accessible from the parking lot, or a median prevents the vehicle from turning on a street in the direction given by the route. The route then becomes useless and the client component must request a new route once underway on the roadway network, where the timing of route download outlined above can occur further compounding the problem.
- FIG. 1 depicts an exemplary distributed communications system, according to one embodiment of the invention
- FIG. 2 depicts a remote communications node of an exemplary distributed communications system
- FIG. 3 depicts a local node of an exemplary distributed communications system
- FIG. 4 depicts a regional node of an exemplary distributed communications system
- FIG. 5 illustrates a simplified block diagram showing a navigation portion of distributed communications system according to one embodiment of the invention
- FIG. 6 depicts a simplified roadway network illustrating an exemplary embodiment of the invention
- FIG. 7 depicts a simplified roadway network illustrating another exemplary embodiment of the invention.
- FIG. 8 depicts a simplified roadway network illustrating another exemplary embodiment of the invention continued from FIG. 7;
- FIG. 9 shows a flow chart of a method of navigation guidance according to one embodiment of the invention.
- the present invention is a method of navigation guidance for a distributed communications system with software components running on mobile client platforms and on remote server platforms.
- FIG. 1 depicts an exemplary distributed communications system 100 with associated communications nodes 104 , 106 , 108 , according to one embodiment of the invention.
- Shown in FIG. 1 are examples of components of an distributed communications system 100 , which comprises a plurality of servers 102 coupled to a regional node 104 , and a plurality of local nodes 106 coupled to regional node 104 .
- the regional node 104 can be coupled to a network, such as the Internet 114 , and to any number of concierge services 112 .
- Servers 102 while illustrated as coupled to regional node 104 , could be implemented at any hierarchical level(s) within distributed communications system 100 .
- servers 102 could also be implemented within one or more local nodes 106 , concierge service 112 , and Internet 114 .
- local node 106 can be a kiosk, cell site, local area network (LAN), telephone company, cable company, satellite, or any other information service, structure, or entity that can transmit, receive, and/or communicate information.
- An information service can be any desired service including, but not limited to, telecommunications, broadband communications, entertainment, television, radio, recorded music, movies, computer-based games, Internet, and other types of public, private, personal, commercial, government, and military communications.
- Local node 106 is coupled to any number of remote communications nodes 108 via wireline or wireless interface means.
- remote communications nodes 108 can transmit and receive information using wireless communications means.
- Remote communications nodes 108 without limitation can include a wireless unit such as a cellular or Personal Communication Service (PCS) telephone, a pager, a hand-held computing device such as a personal digital assistant (PDA) or Web appliance, or any other type of communications and/or computing device.
- PCS Personal Communication Service
- PDA personal digital assistant
- one or more remote communications nodes 108 can be contained within, and optionally form an integral part of a vehicle, such as a car 109 , truck, bus, train, aircraft, or boat, or any type of structure, such as a house, office, school, commercial establishment, and the like.
- a remote communications node 108 can also be implemented in a device that can be carried by the user of the distributed communications system 100 .
- a remote communications node 108 comprises an in-vehicle information appliance comprising various interface elements such as a display 131 , a multi-position controller 113 , one or more control knobs 115 and 116 , one or more indicators 117 such as bulbs or light emitting diodes (LEDs), one or more control buttons 118 , one or more speakers 132 , a microphone 133 , and any other interface elements required by the particular applications to be utilized in conjunction with the information appliance.
- various interface elements such as a display 131 , a multi-position controller 113 , one or more control knobs 115 and 116 , one or more indicators 117 such as bulbs or light emitting diodes (LEDs), one or more control buttons 118 , one or more speakers 132 , a microphone 133 , and any other interface elements required by the particular applications to be utilized in conjunction with the information appliance.
- Remote communications nodes 108 can also transmit and/or receive data to and from devices and services other than local node 106 .
- remote communications nodes 108 can transmit and receive data to and from a satellite 110 .
- FIG. 2 depicts a remote communications node 108 of an exemplary distributed communications system 100 .
- remote communications node 108 can without limitation be located within or be an integral part of any vehicle, such as an automobile, truck, bus, train, aircraft, or boat, or be carried with a user, or be located in a stationary location or structure, and the like.
- the remote communications node 108 comprises a processor 120 with associated remote communications node memory 128 .
- Remote communications node memory 128 comprises remote communications node control algorithms 126 .
- Remote communications node memory 128 can include, but is not limited to, random access memory (RAM), read only memory (ROM), flash memory, and other memory such as a hard disk, floppy disk, and/or other appropriate type of memory.
- Remote communications node 108 can initiate and perform communications with other nodes shown in FIG. 1 in accordance with suitable computer programs, such as remote communications node control algorithms 126 , stored in remote communications node memory 128 .
- Remote communications node 108 also comprises a user interface device 130 that can include without limitation a tactile interface 134 , microphone 133 , speakers 132 , any number of displays 131 , and the like.
- Remote communications node 108 also comprises an extra-vehicle interface 122 , typically implemented as a transmitter/receiver for transmitting and receiving communications via a wireless link 144 among the various nodes depicted in FIG. 1.
- Extra-vehicle interface 122 also facilitates communications among other devices via wireless link 159 , for example, satellite 110 , and the like. Communications are transmitted and received through one or more antennas 142 of any type.
- Remote communications node 108 can also include positioning devices 124 of any type, for example, global positioning system (GPS), gyroscope, compass, accelerometer, altimeter, rate sensors, and other positioning devices 124 that can define the position, attitude, and/or motion vector of the remote communications node 108 .
- GPS global positioning system
- gyroscope gyroscope
- compass accelerometer
- altimeter altimeter
- rate sensors rate sensors
- Remote communications node 108 can also comprise an intra-vehicle interface 136 , which can include antenna 160 .
- Intra-vehicle interface 136 can include multiple types of transceivers (not shown) and antennas 160 to implement different short-range wireless protocols, such as BluetoothTM, IEEE wireless local area network (LAN) standard 802.11, and infrared.
- Intra-vehicle interface 136 is capable of short-range wireless communications, via wireless link 161 , with other wireless devices 138 and sensors 140 of any type, for example, wireless telephones, computers, pagers, PDA's, entertainment devices, printers, fax machines, wireless local networks such as BluetoothTM, vehicle sensors, vehicle actuators, vehicle displays, and the like.
- intra-vehicle interface 136 can be used to communicate with wireless devices that are physically outside the vehicle but close to the vehicle, such as a service station kiosk.
- One or more wireless devices 13 8 can comprise one or more antennas such as antenna 162 and communicate via wireless link 163 .
- One or more sensors 140 can comprise one or more antennas such as antenna 164 and communicate via wireless link 165 .
- the various components and systems in FIG. 2 can communicate with each other via a wireline link 135 , for example, a power/data/control bus, and the like. In another embodiment, some of the various components and systems in FIG. 2 could communicate via a wireless link.
- FIG. 3 depicts a local node 106 of an exemplary distributed communications system 100 .
- the local node 106 comprises a processor 121 with associated local node memory 148 .
- Local node memory 148 comprises local node control algorithms 146 .
- Local node memory 148 can include, but is not limited to, random access memory (RAM), read only memory (ROM), and other memory such as a hard disk, floppy disk, and/or other appropriate type of memory.
- Local node 106 can initiate and perform communications with other nodes shown in FIG. 1 in accordance with suitable computer programs, such as local node control algorithms 146 , stored in local node memory 148 .
- Local node 106 also comprises any number of transmitters/receivers 175 for transmitting and receiving communications via wireless link 144 to and from any number of remote communications nodes 108 . Communications are transmitted and received through antenna 166 .
- Local node 106 also comprises any number of transmitter/receivers 176 for transmitting and receiving communications via wireless link 168 to and from any number of regional nodes 104 . Communications are transmitted and received through antenna 167 . As shown in FIG. 3, the various components and systems can also communicate via terrestrial links such as wireline, radio frequency (RF), or optical links, and the like, with other local nodes 106 and regional nodes 104 .
- RF radio frequency
- the various components and systems in FIG. 3 can communicate with each other via a wireline link 135 , for example, a power/data/control bus, and the like. In another embodiment, some of the various components and systems in FIG. 3 could communicate via a wireless link.
- FIG. 4 depicts a regional node 104 of an exemplary distributed communications system 100 .
- the regional node 104 comprises a processor 123 with associated regional node memory 152 .
- Regional node memory 152 comprises regional node control algorithms 150 .
- Regional node memory 152 can include, but is not limited to, random access memory (RAM), read only memory (ROM), and other memory such as a hard disk, floppy disk, and/or other appropriate type of memory.
- Regional node 104 can initiate and perform communications with other nodes shown in FIG. 1 in accordance with suitable computer programs, such as regional node control algorithms 150 , stored in regional node memory 152 .
- Regional node 104 also comprises any number of transmitters/receivers 177 for transmitting and receiving communications via wireless link 171 to and from any number of local nodes 106 . Communications are transmitted and received through an antenna 170 .
- Regional node 104 also comprises any number of transmitters/receivers 178 for transmitting and receiving communications via wireless link 168 to and from any number of regional nodes 104 , servers 102 , and the like. Communications are transmitted and received through antenna 169 . As shown in FIG. 4, the various components and systems can also communicate, via terrestrial links such as wireline, radio frequency (RF), or optical links, and the like, with other local nodes 106 and regional nodes 104 .
- RF radio frequency
- the various components and systems in FIG. 4 can communicate with each other via a wireline link 135 , for example, a power/data/control bus, and the like. In another embodiment, some of the various components and systems in FIG. 4 could communicate via a wireless link.
- processors 120 , 121 , and 123 respectively, perform distributed, yet coordinated, control functions within distributed communications system 100 (FIG. 1).
- Processors 120 , 121 , and 123 are merely representative, and distributed communications system 100 can comprise many more processors within the distributed servers 102 , regional nodes 104 , local nodes 106 , and remote communications nodes 108 .
- Processors 120 , 121 , and 123 can be of any suitable type or types, depending upon the functional requirements of the overall distributed communications system 100 and its constituent elements, including servers 102 , regional nodes 104 , local nodes 106 , and remote communications nodes 108 .
- Processors 120 , 121 , and 123 comprise portions of data processing systems that perform processing operations on computer programs that are stored in computer memory such as, but not limited to, remote communications node memory 128 , local node memory 148 , and regional node memory 152 . Processors 120 , 121 , and 123 also read data from and store data to memory, and they generate and receive control signals to and from other elements within distributed communications system 100 .
- FIG. 5 illustrates a simplified block diagram showing a navigation portion of distributed communications system 100 according to one embodiment of the invention.
- servers 102 can comprise a navigation server gateway 180 coupled to various servers and software blocks, such as, a traffic server 182 , a route server 184 , and a point-of-interest (POI) server 186 .
- traffic server 182 a traffic server 182
- route server 184 a route server 184
- POI point-of-interest
- Traffic server 182 can contain traffic information including, but not limited to, traffic reports, traffic conditions, speed data, and the like.
- Route server 184 can contain information including, but not limited to, digital road map data, route alternatives, route guidance, and the like.
- Route server 184 is coupled to a map database 181 , which can be a distributed map database.
- Map database 181 contains additional digital roadmap data.
- POI server 186 can contain information for points of interests such as gasoline stations, restaurants, motels, movie theatres, and the like.
- Each of traffic server 182 , route server 184 , and POI server 186 can send and receive content data from external sources such as local traffic reports, news agencies, and the like, in addition to content data already stored on servers 102 .
- Each of servers 102 depicted in FIG. 5 communicate with remote communications node 108 through navigation server gateway 180 via wireless link 192 .
- Servers 102 communicate via any of communications nodes depicted in FIG. 1.
- Wireless link 192 couples navigation server gateway 180 with its counterpart, remote communications node gateway 188 .
- Remote communications node gateway 188 is coupled to various navigation applications, which can include, without limitation, route guidance application(s) 193 , traffic application(s) 194 , POI application(s) 195 , and the like.
- Navigation applications 193 , 194 , 195 are coupled to, and can process data received from servers 102 , positioning devices 124 , satellites 110 , and the like, to provide useful content to users of remote communications node 108 .
- User interface device(s) 130 are coupled to navigation applications 193 , 194 , 195 and can request and display route guidance data including, navigation route data, digital roadmap data, and the like.
- Software blocks that perform embodiments of the invention are part of computer program modules comprising computer instructions, such as local node control algorithms 146 (FIG. 3), that are stored in a computer-readable medium such as local node memory 148 .
- Computer instructions can instruct processors 120 , 121 , 123 to perform methods of operating communications node(s) 104 , 106 , 108 . Additionally, or alternatively, they can be implemented as regional node control algorithms 150 (FIG. 4), which are stored in regional node memory 152 .
- Software blocks and computer program modules can also be located in remote communications node 108 . In other embodiments, additional modules could be provided as needed, and/or unneeded modules could be deleted.
- FIG. 6 depicts a simplified roadway network 290 illustrating an exemplary embodiment of the invention.
- remote communications node 108 is in a location 202 , which can be a starting location.
- Remote communications node 108 can either be moving or stationary.
- remote communications node 108 can be mounted in a vehicle, carried with a user, and the like.
- remote communications node 108 at location 202 requests a navigation route 201 from location 202 to destination location 204 .
- Navigation route 201 is transmitted from communications node(s), which can be, without limitation, regional node 104 , local node 106 , satellite 110 , or other remote communications node 108 .
- Navigation route 201 is comprised of a plurality of route segments, which are depicted in FIG. 6 as lines with arrows in the roadway network 290 . Plurality of route segments are based on the location 202 of remote communications node 108 .
- Plurality of route segments of navigation route 201 comprise a set of multiple route threads from the location 202 of remote communications node 108 to destination location 204 .
- Set of multiple route threads comprise different routes from location 202 to destination location 204 .
- plurality of starting locations 206 , 208 , 209 based on location 202 are determined by route server 184 and transmitted to remote communications node 108 .
- plurality of starting locations 206 , 208 , 209 are determined by remote communications node 108 .
- plurality of starting locations 206 , 208 , 209 are determined by a combination of route server 184 and remote communications node 108 .
- the invention is not limited by the foregoing examples and can include any method or combination of elements to determine plurality of staring locations 206 , 208 , 209 .
- the plurality of staring locations 206 , 208 , 209 correspond to exits 281 , 282 (as shown by arrows) from a parking lot 280 .
- the invention includes any number of starting locations 206 , 208 , 209 .
- Plurality of starting locations 206 , 208 , 209 can be based on a locus of possible starting locations within a radius 220 of location 202 of remote communications node 108 .
- the radius 220 and hence the locus of possible starting locations can be user-defined and based on the number of exits 281 , 282 to the roadway network 290 .
- the locus of possible locations includes the plurality of starting locations 206 , 208 , 209 .
- Plurality of starting locations 206 , 208 , 209 can include starting locations based on all nearby road segments to location 202 .
- plurality of starting locations 206 , 208 , 209 can be based on the accuracy of location 202 of remote communications node 108 .
- the accuracy can be estimated using location 202 and a velocity vector, derived by utilizing data from positioning devices 124 and their accompanying accuracy, or calculated utilizing recent historical data on location 202 . These are only examples, other methods of determining accuracy of location 202 and combinations thereof are within the scope of the invention.
- Each of the plurality of starting locations 206 , 208 , 209 corresponds to at least one starting route segment 210 , 211 , 212 , 214 .
- starting location 206 corresponds to starting route segment 210 because if remote communications node 108 were to begin navigation route 201 at staring location 206 , it would proceed on starting route segment 210 first, in order to reach destination location 204 .
- starting location 208 corresponds to starting route segments 212 and 214 . If remote communications node 108 were to begin navigation route 201 at staring location 208 , either starting route 212 or 214 can be utilized depending on which direction remote communications node 108 takes.
- starting location 209 corresponds to starting route segment 211 .
- Each of the plurality of starting locations 206 , 208 , 209 comprises the beginning of at least one route thread in the set of multiple route threads transmitted to remote communications node 108 .
- a route thread comprises a unique set of route segments from location 202 of remote communications node 108 to destination location 204 . Together, the unique set of route segments make up one potential navigation route 201 .
- one route thread in the set of multiple route threads is based on starting location 206 and includes route segments 210 , 254 , and the like.
- Another route thread is based on starting location 208 and includes route segments 214 , 250 , 252 , 254 , and the like.
- Yet another route thread is based on starting location 208 and includes route segments 212 , 213 , 207 , 210 , 254 , and the like. Still another route thread is based on starting location 209 and includes route segments 211 , 213 , 207 , 210 , 254 , and the like, if a u-turn is legal at route segment 211 . If a u-turn is not legal at route segment 211 , then the route thread based on starting location 209 includes route segments 211 , 212 , 214 , 250 , 252 , 254 , and the like. Any route segment depicted in FIG. 6 can be further broken down into any number of smaller route segments. For example, route segment 254 can be broken down into any number of smaller route segments based on the number of maneuvers required. Route segment 254 is shown in FIG. 6 as a single segment for convenience, but can be parsed down to any number of smaller route segments.
- Plurality of starting locations 206 , 208 , 209 generally occur on the roadway network 290 because digital roadmap and navigation data is generally not available that specifically includes parking lots and private entrances to roadway network 290 . Because of this, plurality of starting locations 206 , 208 , 209 and corresponding starting route segments 210 , 211 , 212 , 214 are within the roadway network 290 . The invention is not limited to this configuration however. Other databases that incorporate private entrances to the roadway network 290 , roadway medians, parking lots, and other details can be incorporated into general navigation content and be included within the scope of the invention. If the aforementioned navigation content is incorporated, plurality of starting locations 206 , 208 , 209 and corresponding starting route segments 210 , 211 , 212 , 214 can extend into such detail.
- the embodiment of the invention offers numerous advantages. For example, transmitting multiple route threads based on location 202 of remote communications node 108 allows each possible starting location for navigation route 201 to be downloaded to remote communications node 108 based on location 202 .
- the optimum route from location 202 to location 204 will be computed. The optimum route would tend to have the user turn left from the parking lot onto route segment 210 . As can be seen in FIG. 6, a left turn onto route segment 210 is impossible because of the median.
- the map database 181 used to generate optimum routes may not have this information, so an optimum route may be erroneously generated showing an illegal left turn.
- route segment 211 As soon as the user turns right onto route segment 211 instead, the user will be off the optimum navigation route and the remote communications node 108 will be unable to provide navigation instructions to the user. In other cases, a turn or maneuver may be possible on the road network, but traffic or construction conditions make the turn or maneuver difficult, dangerous, or impossible. Therefore, if one or more starting locations and corresponding staring route segments are not accessible from location 202 (i.e. starting location 206 and starting route segment 210 are blocked by the road median), other starting locations and route segments are immediately available to remote communications node 108 and the corresponding user. This alleviates having to download a new navigation route 201 to remote communications node 108 .
- Another advantage is that after remote communications node 108 enters the roadway network 290 at any starting location, the route thread will already be downloaded along with the required maneuvers for remote communications node 108 to reach destination location 204 .
- the number of starting locations, starting route segments, route threads and the proximity of starting route segments to location 202 can be set or adjusted by the user of remote communications node 108 or a system administrator of the navigation system.
- the route guidance software detects the nearest route thread to the current location of remote communications node 108 and gives the user the appropriate maneuver instruction for that route thread. If the user is unable to utilize that route thread, they may turn in a different direction or onto a different road altogether. As this happens, the route guidance software detects the route segment that now most closely matches the location and heading of remote communications node 108 . The maneuver instruction corresponding to the matched route segment in the alternate route thread is given to the user and the route guidance commences. Many other route guidance strategies are possible and are included within the scope of the invention.
- FIG. 6 Another embodiment of the invention is depicted in FIG. 6.
- Multiple route threads can also be included for the proximity of destination location 204 . This has the advantage of avoiding similar difficulties that can develop at location 202 (for example, one or more entrances to destination location from the road network may be inaccessible due to medians, barriers, and the like).
- the number of route threads and the proximity of ending route segments to destination location 204 can be set or adjusted by the user of remote communications node 108 or a system administrator of the navigation system.
- Multiple route threads pertaining to destination location 204 can be transmitted to remote communications node 108 with the initial transmission of navigation route 201 , transmitted in route, transmitted on request, and the like.
- plurality of ending locations 270 , 271 , 272 , 273 are available at destination location 204 .
- Destination location 204 is inaccessible from ending locations 270 , 271 due to the road medians. However, destination location 204 is accessible from ending locations 272 and 273 . Since multiple route threads are already downloaded to remote communications node 108 , a route thread is already available to guide the user of remote communications node 108 to destination location 204 at ending location 272 via route segments 256 , 262 and 268 . An alternate route thread is available for ending location 272 via route segments 256 , 264 , 265 , 266 and 268 .
- Route segment 262 is shown as one segment for convenience, but could be shown as any number of smaller route segments, for example one route segment for each maneuver required. If a u-turn is not permitted at route segment 265 , ending location 273 is available via route segments 256 , 264 , 265 , and 267 .
- the route threads shown in FIG. 6 are representative and many other combinations of route threads are possible and within the scope of the invention.
- plurality of ending locations 270 , 271 , 272 , 273 occur on the roadway network 290 because data is generally not available that specifically includes parking lots and private entrances to the roadway network 290 . Because of this, plurality of ending locations 270 , 271 , 272 , 273 and corresponding ending route segments 254 , 262 , 264 , 268 are within the roadway network 290 .
- the invention is not limited to this configuration however.
- Other databases that incorporate private entrances to the roadway network 290 , roadway medians, parking lots, and other details can be incorporated into general navigation content and be included within the scope of the invention. If the aforementioned navigation content is incorporated, plurality of ending locations 270 , 271 , 272 , 273 and corresponding ending route segments 254 , 262 , 264 , 268 can extend into such detail as additional content is provided or available.
- remote communications node 108 can either request or have automatically updated the set of multiple route threads based on the present location of remote communications node 108 and destination location 204 . Updating can also occur as each of the plurality of route segments is completed. While remote communications node 108 is non-stationary, any updates to set of multiple route threads can be based on the location 202 and velocity vector of remote communications node 108 .
- the velocity vector can comprise velocity, heading, elevation, and the like, of remote communications node 108 .
- the velocity vector can be computed from positioning devices 124 utilizing route guidance applications 193 , with velocity vector and location data transmitted to communications nodes 104 , 106 and severs 102 .
- FIG. 7 depicts a simplified roadway network 390 illustrating another exemplary embodiment of the invention.
- remote communications node 108 is non-stationary on the roadway network 390 , located in first location 302 at a first time (T 1 ) with a velocity vector 303 .
- T 1 first time
- remote communications node 108 requests navigation route 301 to destination location 304 .
- remote communications node 108 also transmits first location 302 and velocity vector 303 to servers 102 via communications node 104 , 106 108 .
- Severs 102 at communications node 104 , 106 , 108 utilizes first location 302 and velocity vector 303 to calculate a locus of possible second locations 305 , 307 of remote communications node 108 at a second time (T 2 ). While the request of navigation route 301 occurs at T 1 , receipt of navigation route 301 occurs at T 2 . Navigation route 301 transmitted to remote communications node 108 is based on the locus of possible second locations 305 , 307 .
- Locus of possible second locations 305 , 307 includes all possible locations of remote communications node 108 on the roadway network 390 .
- the first location 302 and velocity vector 303 of remote communications node 108 indicate that remote communications node 108 can be in locus of possible second locations 305 if traveling at one velocity, and locus of possible second locations 307 if traveling at a larger velocity.
- a set of multiple route threads for the locus of possible second locations 307 is transmitted to remote communications node 108 .
- navigation route 301 has route segment 318 in common with each of the multiple route threads.
- the following set of multiple route threads are transmitted: 1) route segments 310 , 315 , 317 ; 2) route segments 312 , 315 , 317 ; 3) route segments 314 , 317 ; and 4) route segments 322 , 316 , with each of these four route threads having route segment 318 in common.
- several route threads have some route segments in common.
- route threads do not have any route segments in common.
- Route segment 318 is shown as one route segment for convenience and can be parsed to any number of smaller route segments based on the maneuvers required, and the like.
- navigation route 301 is transmitted sequentially with the route segments nearest the locus of possible second locations 307 transmitted first. This enables remote communications node 108 to begin maneuvers prior to receiving the entire navigation route 301 .
- the route guidance software uses the current location of remote communications node 108 to determine which of the downloaded route segments is closest to the vehicle position. The preferred route thread corresponding to that route segment is selected as the active route and the maneuver instructions are communicated to the user as appropriate.
- FIG. 8 depicts a simplified roadway network 390 illustrating another exemplary embodiment of the invention continued from FIG. 7.
- the actual second location 308 of remote communications node is determined and/or selected upon receipt of a portion of navigation route 301 .
- the actual second location 308 is determined utilizing positioning device(s) 124 , route guidance applications 193 and the like.
- the actual second location 308 is compared with the set of multiple route threads based on locus of possible second locations 307 calculated and transmitted from servers 102 via communications node 104 , 106 , 108 .
- remote communications node 108 can proceed utilizing the route thread associated with actual second location 308 to communicate the necessary maneuvers to arrive at destination location 304 .
- remote communications node 108 can either request or have automatically updated the set of multiple route threads based on the actual location 308 of remote communications node 108 and destination location 204 . Updating can also occur as each of the plurality of route segments is completed.
- remote communications node can request an update to navigation route 301 , which can incorporate content from other applications, such as traffic applications 194 , and the like.
- an update of navigation route 301 can incorporate traffic information such as that of an accident known to be blocking an intersection on the navigation route 301 .
- the accident is shown as an “X” and labeled 319 in FIG. 8.
- the update to navigation route 301 can include an additional set of multiple route threads that include one or more route segments 320 calculated to avoid the blocked intersection.
- route server 184 can anticipate one or more alternative route threads 320 along navigation route 301 other than in the vicinity of first location 302 and destination location 304 .
- the alternative route threads can be based on historical traffic data, user-driving patterns, and the like, in order to anticipate likely or often used deviations from navigation route 301 .
- alternative route threads 320 are already communicated to remote communications node 108 . So when the deviation occurs, a new route segment and route thread is selected based on a current location of remote communications node 108 , and corresponding maneuvers are communicated to the user of remote communications node 108 .
- FIG. 9 shows a flow chart of a method of navigation guidance according to one embodiment of the invention.
- remote communications node 108 requests navigation route 201 , 301 from it's present location to a destination location, and transmits the location 202 , 302 of remote communications node 108 (either a stationary location, i.e. location 202 , or first location, i.e. 302 ) and velocity vector 303 to servers 102 and communications node 104 , 106 .
- step 402 the locus of possible second locations is calculated. This can also include the set of multiple route threads if remote communications node 108 is stationary.
- step 404 navigation route 201 , 301 is transmitted to remote communications node 108 with multiple route threads and route segments.
- remote communications node 108 receives navigation route 201 , 301 .
- step 408 the actual second location 308 of remote communications node 108 is determined and the corresponding set of multiple route threads are utilized and maneuvers communicated to any interested actors, which can include a user of remote communications node 108 .
- Maneuvers are communicated to interested actors via wireless or wireline communication means, voice and visual communication means, and the like.
- a route thread is selected from the set of multiple route threads based on a current location of remote communications node 108 .
- the route thread representing the preferred route is selected.
- a set of maneuver instructions are communicated to a user of the remote communications node 108 based on the route thread selected.
- navigation route 201 , 301 including set of multiple route threads and route segments are updated either automatically or on request to take into account the present location of remote communications node 108 and optionally, any other road conditions, such as accidents, road closures, weather conditions, and the like. This process can repeat as often as necessary each time a new actual second location 308 is determined or updated.
Landscapes
- Engineering & Computer Science (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Navigation (AREA)
- Traffic Control Systems (AREA)
- Instructional Devices (AREA)
Abstract
Description
- This invention relates generally to navigation guidance and, in particular to a method of navigation guidance for a remote communications node.
- A distributed navigation system generally has a navigation server component where navigation data is stored and a client component for route guidance. The client component can be an in-vehicle device or some other portable wireless device with a method of determining position.
- Prior art methods of providing navigation guidance for client components have numerous deficiencies. For example, existing navigation systems that download route data only download a single route from an origin point to a destination point. When the client component is moving, the client's position changes between the time the route is requested and the time the route data arrives at the client. The client component may move a large distance during route download, and may in fact pass the first maneuver point on the route. If this happens, the entire route becomes useless and the client component must request a new route.
- Another problem with this method occurs where there are numerous routes available from the starting location of the client component. Existing guidance systems will only provide one route from the starting location, which may not even be available or accessible to the user of the client component. This can occur in vehicle applications where the vehicle is in a parking lot and the beginning of the route downloaded starts on a street that is not accessible from the parking lot, or a median prevents the vehicle from turning on a street in the direction given by the route. The route then becomes useless and the client component must request a new route once underway on the roadway network, where the timing of route download outlined above can occur further compounding the problem.
- Accordingly, there is a significant need for methods of navigation guidance that overcome the deficiencies of the prior art outlined above.
- Referring to the drawing:
- FIG. 1 depicts an exemplary distributed communications system, according to one embodiment of the invention;
- FIG. 2 depicts a remote communications node of an exemplary distributed communications system;
- FIG. 3 depicts a local node of an exemplary distributed communications system;
- FIG. 4 depicts a regional node of an exemplary distributed communications system;
- FIG. 5 illustrates a simplified block diagram showing a navigation portion of distributed communications system according to one embodiment of the invention;
- FIG. 6 depicts a simplified roadway network illustrating an exemplary embodiment of the invention;
- FIG. 7 depicts a simplified roadway network illustrating another exemplary embodiment of the invention;
- FIG. 8 depicts a simplified roadway network illustrating another exemplary embodiment of the invention continued from FIG. 7; and
- FIG. 9 shows a flow chart of a method of navigation guidance according to one embodiment of the invention.
- It will be appreciated that for simplicity and clarity of illustration, elements shown in the drawing have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to each other. Further, where considered appropriate, reference numerals have been repeated among the Figures to indicate corresponding elements.
- The present invention is a method of navigation guidance for a distributed communications system with software components running on mobile client platforms and on remote server platforms.
- FIG. 1 depicts an exemplary
distributed communications system 100 with associatedcommunications nodes communications system 100, which comprises a plurality ofservers 102 coupled to aregional node 104, and a plurality oflocal nodes 106 coupled toregional node 104. There can be any number ofservers 102,regional nodes 104, andlocal nodes 106 within the distributedcommunications system 100. Theregional node 104 can be coupled to a network, such as theInternet 114, and to any number ofconcierge services 112. -
Servers 102, while illustrated as coupled toregional node 104, could be implemented at any hierarchical level(s) within distributedcommunications system 100. For example,servers 102 could also be implemented within one or morelocal nodes 106,concierge service 112, andInternet 114. - Without limitation,
local node 106 can be a kiosk, cell site, local area network (LAN), telephone company, cable company, satellite, or any other information service, structure, or entity that can transmit, receive, and/or communicate information. An information service can be any desired service including, but not limited to, telecommunications, broadband communications, entertainment, television, radio, recorded music, movies, computer-based games, Internet, and other types of public, private, personal, commercial, government, and military communications. -
Local node 106 is coupled to any number ofremote communications nodes 108 via wireline or wireless interface means. In the embodiment depicted in FIG. 1,remote communications nodes 108 can transmit and receive information using wireless communications means.Remote communications nodes 108 without limitation can include a wireless unit such as a cellular or Personal Communication Service (PCS) telephone, a pager, a hand-held computing device such as a personal digital assistant (PDA) or Web appliance, or any other type of communications and/or computing device. Without limitation, one or moreremote communications nodes 108 can be contained within, and optionally form an integral part of a vehicle, such as acar 109, truck, bus, train, aircraft, or boat, or any type of structure, such as a house, office, school, commercial establishment, and the like. As indicated above, aremote communications node 108 can also be implemented in a device that can be carried by the user of the distributedcommunications system 100. - In one embodiment, a
remote communications node 108 comprises an in-vehicle information appliance comprising various interface elements such as adisplay 131, amulti-position controller 113, one ormore control knobs more indicators 117 such as bulbs or light emitting diodes (LEDs), one ormore control buttons 118, one ormore speakers 132, amicrophone 133, and any other interface elements required by the particular applications to be utilized in conjunction with the information appliance. -
Remote communications nodes 108 can also transmit and/or receive data to and from devices and services other thanlocal node 106. For example,remote communications nodes 108 can transmit and receive data to and from asatellite 110. - FIG. 2 depicts a
remote communications node 108 of an exemplary distributedcommunications system 100. As indicated above,remote communications node 108 can without limitation be located within or be an integral part of any vehicle, such as an automobile, truck, bus, train, aircraft, or boat, or be carried with a user, or be located in a stationary location or structure, and the like. As shown in FIG. 2, theremote communications node 108 comprises aprocessor 120 with associated remotecommunications node memory 128. Remotecommunications node memory 128 comprises remote communicationsnode control algorithms 126. Remotecommunications node memory 128 can include, but is not limited to, random access memory (RAM), read only memory (ROM), flash memory, and other memory such as a hard disk, floppy disk, and/or other appropriate type of memory.Remote communications node 108 can initiate and perform communications with other nodes shown in FIG. 1 in accordance with suitable computer programs, such as remote communicationsnode control algorithms 126, stored in remotecommunications node memory 128. -
Remote communications node 108 also comprises auser interface device 130 that can include without limitation atactile interface 134,microphone 133,speakers 132, any number ofdisplays 131, and the like. -
Remote communications node 108 also comprises anextra-vehicle interface 122, typically implemented as a transmitter/receiver for transmitting and receiving communications via awireless link 144 among the various nodes depicted in FIG. 1.Extra-vehicle interface 122 also facilitates communications among other devices viawireless link 159, for example,satellite 110, and the like. Communications are transmitted and received through one ormore antennas 142 of any type.Remote communications node 108 can also includepositioning devices 124 of any type, for example, global positioning system (GPS), gyroscope, compass, accelerometer, altimeter, rate sensors, andother positioning devices 124 that can define the position, attitude, and/or motion vector of theremote communications node 108. -
Remote communications node 108 can also comprise anintra-vehicle interface 136, which can includeantenna 160.Intra-vehicle interface 136 can include multiple types of transceivers (not shown) andantennas 160 to implement different short-range wireless protocols, such as Bluetooth™, IEEE wireless local area network (LAN) standard 802.11, and infrared.Intra-vehicle interface 136 is capable of short-range wireless communications, viawireless link 161, withother wireless devices 138 andsensors 140 of any type, for example, wireless telephones, computers, pagers, PDA's, entertainment devices, printers, fax machines, wireless local networks such as Bluetooth™, vehicle sensors, vehicle actuators, vehicle displays, and the like. In addition,intra-vehicle interface 136 can be used to communicate with wireless devices that are physically outside the vehicle but close to the vehicle, such as a service station kiosk. One or more wireless devices 13 8 can comprise one or more antennas such asantenna 162 and communicate viawireless link 163. One ormore sensors 140 can comprise one or more antennas such asantenna 164 and communicate viawireless link 165. - In one embodiment, the various components and systems in FIG. 2 can communicate with each other via a
wireline link 135, for example, a power/data/control bus, and the like. In another embodiment, some of the various components and systems in FIG. 2 could communicate via a wireless link. - FIG. 3 depicts a
local node 106 of an exemplary distributedcommunications system 100. As shown in FIG. 3, thelocal node 106 comprises aprocessor 121 with associatedlocal node memory 148.Local node memory 148 comprises localnode control algorithms 146.Local node memory 148 can include, but is not limited to, random access memory (RAM), read only memory (ROM), and other memory such as a hard disk, floppy disk, and/or other appropriate type of memory.Local node 106 can initiate and perform communications with other nodes shown in FIG. 1 in accordance with suitable computer programs, such as localnode control algorithms 146, stored inlocal node memory 148. -
Local node 106 also comprises any number of transmitters/receivers 175 for transmitting and receiving communications viawireless link 144 to and from any number ofremote communications nodes 108. Communications are transmitted and received throughantenna 166. -
Local node 106 also comprises any number of transmitter/receivers 176 for transmitting and receiving communications viawireless link 168 to and from any number ofregional nodes 104. Communications are transmitted and received throughantenna 167. As shown in FIG. 3, the various components and systems can also communicate via terrestrial links such as wireline, radio frequency (RF), or optical links, and the like, with otherlocal nodes 106 andregional nodes 104. - In one embodiment, the various components and systems in FIG. 3 can communicate with each other via a
wireline link 135, for example, a power/data/control bus, and the like. In another embodiment, some of the various components and systems in FIG. 3 could communicate via a wireless link. - FIG. 4 depicts a
regional node 104 of an exemplary distributedcommunications system 100. As shown in FIG. 4, theregional node 104 comprises aprocessor 123 with associatedregional node memory 152.Regional node memory 152 comprises regionalnode control algorithms 150.Regional node memory 152 can include, but is not limited to, random access memory (RAM), read only memory (ROM), and other memory such as a hard disk, floppy disk, and/or other appropriate type of memory.Regional node 104 can initiate and perform communications with other nodes shown in FIG. 1 in accordance with suitable computer programs, such as regionalnode control algorithms 150, stored inregional node memory 152. -
Regional node 104 also comprises any number of transmitters/receivers 177 for transmitting and receiving communications viawireless link 171 to and from any number oflocal nodes 106. Communications are transmitted and received through anantenna 170. -
Regional node 104 also comprises any number of transmitters/receivers 178 for transmitting and receiving communications viawireless link 168 to and from any number ofregional nodes 104,servers 102, and the like. Communications are transmitted and received throughantenna 169. As shown in FIG. 4, the various components and systems can also communicate, via terrestrial links such as wireline, radio frequency (RF), or optical links, and the like, with otherlocal nodes 106 andregional nodes 104. - In one embodiment, the various components and systems in FIG. 4 can communicate with each other via a
wireline link 135, for example, a power/data/control bus, and the like. In another embodiment, some of the various components and systems in FIG. 4 could communicate via a wireless link. - In FIGS.2-4,
processors -
Processors communications system 100 can comprise many more processors within the distributedservers 102,regional nodes 104,local nodes 106, andremote communications nodes 108. -
Processors communications system 100 and its constituent elements, includingservers 102,regional nodes 104,local nodes 106, andremote communications nodes 108. -
Processors communications node memory 128,local node memory 148, andregional node memory 152.Processors communications system 100. - The particular elements of the distributed
communications system 100, including the elements of the data processing systems, are not limited to those shown and described, and they can take any form that will implement the functions of the invention herein described. - To provide an example of one context in which the present invention may be used, an example of a method of navigation guidance applied to a remote communications node will now be described. The present invention is not limited to implementation by any particular set of elements, and the description herein is merely representational of one embodiment. The specifics of one or more embodiments of the invention are provided below in sufficient detail to enable one of ordinary skill in the art to understand and practice the present invention.
- FIG. 5 illustrates a simplified block diagram showing a navigation portion of distributed
communications system 100 according to one embodiment of the invention. As shown in FIG. 5,servers 102 can comprise anavigation server gateway 180 coupled to various servers and software blocks, such as, atraffic server 182, aroute server 184, and a point-of-interest (POI)server 186. -
Traffic server 182 can contain traffic information including, but not limited to, traffic reports, traffic conditions, speed data, and the like.Route server 184 can contain information including, but not limited to, digital road map data, route alternatives, route guidance, and the like.Route server 184 is coupled to amap database 181, which can be a distributed map database.Map database 181 contains additional digital roadmap data.POI server 186 can contain information for points of interests such as gasoline stations, restaurants, motels, movie theatres, and the like. - Each of
traffic server 182,route server 184, andPOI server 186 can send and receive content data from external sources such as local traffic reports, news agencies, and the like, in addition to content data already stored onservers 102. - Each of
servers 102 depicted in FIG. 5 communicate withremote communications node 108 throughnavigation server gateway 180 viawireless link 192.Servers 102 communicate via any of communications nodes depicted in FIG. 1.Wireless link 192, couplesnavigation server gateway 180 with its counterpart, remotecommunications node gateway 188. Remotecommunications node gateway 188 is coupled to various navigation applications, which can include, without limitation, route guidance application(s) 193, traffic application(s) 194, POI application(s) 195, and the like.Navigation applications servers 102,positioning devices 124,satellites 110, and the like, to provide useful content to users ofremote communications node 108. User interface device(s) 130 are coupled tonavigation applications - Software blocks that perform embodiments of the invention are part of computer program modules comprising computer instructions, such as local node control algorithms146 (FIG. 3), that are stored in a computer-readable medium such as
local node memory 148. Computer instructions can instructprocessors regional node memory 152. Software blocks and computer program modules can also be located inremote communications node 108. In other embodiments, additional modules could be provided as needed, and/or unneeded modules could be deleted. - FIG. 6 depicts a
simplified roadway network 290 illustrating an exemplary embodiment of the invention. As shown in FIG. 6,remote communications node 108 is in alocation 202, which can be a starting location.Remote communications node 108 can either be moving or stationary. In the embodiment shown,remote communications node 108 can be mounted in a vehicle, carried with a user, and the like. - In the embodiment depicted in FIG. 6,
remote communications node 108 atlocation 202 requests anavigation route 201 fromlocation 202 todestination location 204.Navigation route 201 is transmitted from communications node(s), which can be, without limitation,regional node 104,local node 106,satellite 110, or otherremote communications node 108.Navigation route 201 is comprised of a plurality of route segments, which are depicted in FIG. 6 as lines with arrows in theroadway network 290. Plurality of route segments are based on thelocation 202 ofremote communications node 108. Plurality of route segments ofnavigation route 201 comprise a set of multiple route threads from thelocation 202 ofremote communications node 108 todestination location 204. Set of multiple route threads comprise different routes fromlocation 202 todestination location 204. - In an embodiment of the invention, plurality of starting
locations location 202 are determined byroute server 184 and transmitted toremote communications node 108. In another embodiment, plurality of startinglocations remote communications node 108. In still another embodiment, plurality of startinglocations route server 184 andremote communications node 108. The invention is not limited by the foregoing examples and can include any method or combination of elements to determine plurality of staringlocations - In FIG. 6, the plurality of staring
locations exits 281, 282 (as shown by arrows) from aparking lot 280. Although three startinglocations locations locations radius 220 oflocation 202 ofremote communications node 108. Theradius 220 and hence the locus of possible starting locations can be user-defined and based on the number ofexits roadway network 290. In the embodiment shown in FIG. 6, the locus of possible locations includes the plurality of startinglocations locations location 202. - In an embodiment of the invention, plurality of starting
locations location 202 ofremote communications node 108. The accuracy can be estimated usinglocation 202 and a velocity vector, derived by utilizing data from positioningdevices 124 and their accompanying accuracy, or calculated utilizing recent historical data onlocation 202. These are only examples, other methods of determining accuracy oflocation 202 and combinations thereof are within the scope of the invention. - Each of the plurality of starting
locations route segment location 206 corresponds to startingroute segment 210 because ifremote communications node 108 were to beginnavigation route 201 at staringlocation 206, it would proceed on startingroute segment 210 first, in order to reachdestination location 204. In another example, startinglocation 208 corresponds to startingroute segments remote communications node 108 were to beginnavigation route 201 at staringlocation 208, either startingroute remote communications node 108 takes. In yet another example, startinglocation 209 corresponds to startingroute segment 211. - Each of the plurality of starting
locations remote communications node 108. A route thread comprises a unique set of route segments fromlocation 202 ofremote communications node 108 todestination location 204. Together, the unique set of route segments make up onepotential navigation route 201. For example, in the embodiment shown in FIG. 6, one route thread in the set of multiple route threads is based on startinglocation 206 and includesroute segments location 208 and includesroute segments location 208 and includesroute segments location 209 and includesroute segments route segment 211. If a u-turn is not legal atroute segment 211, then the route thread based on startinglocation 209 includesroute segments route segment 254 can be broken down into any number of smaller route segments based on the number of maneuvers required.Route segment 254 is shown in FIG. 6 as a single segment for convenience, but can be parsed down to any number of smaller route segments. - Plurality of starting
locations roadway network 290 because digital roadmap and navigation data is generally not available that specifically includes parking lots and private entrances toroadway network 290. Because of this, plurality of startinglocations starting route segments roadway network 290. The invention is not limited to this configuration however. Other databases that incorporate private entrances to theroadway network 290, roadway medians, parking lots, and other details can be incorporated into general navigation content and be included within the scope of the invention. If the aforementioned navigation content is incorporated, plurality of startinglocations starting route segments - The embodiment of the invention offers numerous advantages. For example, transmitting multiple route threads based on
location 202 ofremote communications node 108 allows each possible starting location fornavigation route 201 to be downloaded toremote communications node 108 based onlocation 202. In a classical route calculation scheme, the optimum route fromlocation 202 tolocation 204 will be computed. The optimum route would tend to have the user turn left from the parking lot ontoroute segment 210. As can be seen in FIG. 6, a left turn ontoroute segment 210 is impossible because of the median. However, themap database 181 used to generate optimum routes may not have this information, so an optimum route may be erroneously generated showing an illegal left turn. As soon as the user turns right ontoroute segment 211 instead, the user will be off the optimum navigation route and theremote communications node 108 will be unable to provide navigation instructions to the user. In other cases, a turn or maneuver may be possible on the road network, but traffic or construction conditions make the turn or maneuver difficult, dangerous, or impossible. Therefore, if one or more starting locations and corresponding staring route segments are not accessible from location 202 (i.e. startinglocation 206 and startingroute segment 210 are blocked by the road median), other starting locations and route segments are immediately available toremote communications node 108 and the corresponding user. This alleviates having to download anew navigation route 201 toremote communications node 108. Another advantage is that afterremote communications node 108 enters theroadway network 290 at any starting location, the route thread will already be downloaded along with the required maneuvers forremote communications node 108 to reachdestination location 204. In an embodiment, the number of starting locations, starting route segments, route threads and the proximity of starting route segments tolocation 202 can be set or adjusted by the user ofremote communications node 108 or a system administrator of the navigation system. - Once the remote communications node commences traveling to
destination location 204, the route guidance software detects the nearest route thread to the current location ofremote communications node 108 and gives the user the appropriate maneuver instruction for that route thread. If the user is unable to utilize that route thread, they may turn in a different direction or onto a different road altogether. As this happens, the route guidance software detects the route segment that now most closely matches the location and heading ofremote communications node 108. The maneuver instruction corresponding to the matched route segment in the alternate route thread is given to the user and the route guidance commences. Many other route guidance strategies are possible and are included within the scope of the invention. - Another embodiment of the invention is depicted in FIG. 6. Multiple route threads can also be included for the proximity of
destination location 204. This has the advantage of avoiding similar difficulties that can develop at location 202 (for example, one or more entrances to destination location from the road network may be inaccessible due to medians, barriers, and the like). The number of route threads and the proximity of ending route segments todestination location 204 can be set or adjusted by the user ofremote communications node 108 or a system administrator of the navigation system. Multiple route threads pertaining todestination location 204 can be transmitted toremote communications node 108 with the initial transmission ofnavigation route 201, transmitted in route, transmitted on request, and the like. - In the embodiment depicted in FIG. 6, plurality of ending
locations destination location 204.Destination location 204 is inaccessible from endinglocations destination location 204 is accessible from endinglocations remote communications node 108, a route thread is already available to guide the user ofremote communications node 108 todestination location 204 at endinglocation 272 viaroute segments location 272 viaroute segments Route segment 262 is shown as one segment for convenience, but could be shown as any number of smaller route segments, for example one route segment for each maneuver required. If a u-turn is not permitted atroute segment 265, endinglocation 273 is available viaroute segments - In the present embodiment, plurality of ending
locations roadway network 290 because data is generally not available that specifically includes parking lots and private entrances to theroadway network 290. Because of this, plurality of endinglocations route segments roadway network 290. The invention is not limited to this configuration however. Other databases that incorporate private entrances to theroadway network 290, roadway medians, parking lots, and other details can be incorporated into general navigation content and be included within the scope of the invention. If the aforementioned navigation content is incorporated, plurality of endinglocations route segments - In another embodiment, at any point along
navigation route 201,remote communications node 108 can either request or have automatically updated the set of multiple route threads based on the present location ofremote communications node 108 anddestination location 204. Updating can also occur as each of the plurality of route segments is completed. Whileremote communications node 108 is non-stationary, any updates to set of multiple route threads can be based on thelocation 202 and velocity vector ofremote communications node 108. The velocity vector can comprise velocity, heading, elevation, and the like, ofremote communications node 108. The velocity vector can be computed from positioningdevices 124 utilizingroute guidance applications 193, with velocity vector and location data transmitted tocommunications nodes - FIG. 7 depicts a
simplified roadway network 390 illustrating another exemplary embodiment of the invention. As shown in FIG. 7,remote communications node 108 is non-stationary on theroadway network 390, located infirst location 302 at a first time (T1) with avelocity vector 303. At T1,remote communications node 108requests navigation route 301 todestination location 304. At T1remote communications node 108 also transmitsfirst location 302 andvelocity vector 303 toservers 102 viacommunications node -
Severs 102 atcommunications node first location 302 andvelocity vector 303 to calculate a locus of possiblesecond locations remote communications node 108 at a second time (T2). While the request ofnavigation route 301 occurs at T1, receipt ofnavigation route 301 occurs at T2. Navigation route 301 transmitted toremote communications node 108 is based on the locus of possiblesecond locations - Locus of possible
second locations remote communications node 108 on theroadway network 390. For example, in FIG. 7, thefirst location 302 andvelocity vector 303 ofremote communications node 108 indicate thatremote communications node 108 can be in locus of possiblesecond locations 305 if traveling at one velocity, and locus of possiblesecond locations 307 if traveling at a larger velocity. - Taking the locus of possible
second locations 307 as an example, a set of multiple route threads for the locus of possiblesecond locations 307 is transmitted toremote communications node 108. As shown in FIG. 7,navigation route 301 hasroute segment 318 in common with each of the multiple route threads. In the example shown, the following set of multiple route threads are transmitted: 1)route segments route segments route segments route segments route segment 318 in common. In the embodiment shown, several route threads have some route segments in common. In another embodiment, route threads do not have any route segments in common.Route segment 318 is shown as one route segment for convenience and can be parsed to any number of smaller route segments based on the maneuvers required, and the like. - In an embodiment of the invention,
navigation route 301 is transmitted sequentially with the route segments nearest the locus of possiblesecond locations 307 transmitted first. This enablesremote communications node 108 to begin maneuvers prior to receiving theentire navigation route 301. The route guidance software uses the current location ofremote communications node 108 to determine which of the downloaded route segments is closest to the vehicle position. The preferred route thread corresponding to that route segment is selected as the active route and the maneuver instructions are communicated to the user as appropriate. - FIG. 8 depicts a
simplified roadway network 390 illustrating another exemplary embodiment of the invention continued from FIG. 7. As shown in FIG. 8, the actualsecond location 308 of remote communications node is determined and/or selected upon receipt of a portion ofnavigation route 301. Upon receipt of a portion ofnavigation route 301, the actualsecond location 308 is determined utilizing positioning device(s) 124,route guidance applications 193 and the like. The actualsecond location 308 is compared with the set of multiple route threads based on locus of possiblesecond locations 307 calculated and transmitted fromservers 102 viacommunications node second location 308 is determined,remote communications node 108 can proceed utilizing the route thread associated with actualsecond location 308 to communicate the necessary maneuvers to arrive atdestination location 304. - In another embodiment of the invention,
remote communications node 108 can either request or have automatically updated the set of multiple route threads based on theactual location 308 ofremote communications node 108 anddestination location 204. Updating can also occur as each of the plurality of route segments is completed. After determining actualsecond location 308, remote communications node can request an update tonavigation route 301, which can incorporate content from other applications, such astraffic applications 194, and the like. For example, after determining actualsecond location 308, an update ofnavigation route 301 can incorporate traffic information such as that of an accident known to be blocking an intersection on thenavigation route 301. The accident is shown as an “X” and labeled 319 in FIG. 8. In the present embodiment of the invention, the update tonavigation route 301 can include an additional set of multiple route threads that include one ormore route segments 320 calculated to avoid the blocked intersection. - In another embodiment,
route server 184 can anticipate one or morealternative route threads 320 alongnavigation route 301 other than in the vicinity offirst location 302 anddestination location 304. The alternative route threads can be based on historical traffic data, user-driving patterns, and the like, in order to anticipate likely or often used deviations fromnavigation route 301. In this manner, if theremote communications node 108 deviates from anavigation route 301 or route thread along thenavigation route 301,alternative route threads 320 are already communicated toremote communications node 108. So when the deviation occurs, a new route segment and route thread is selected based on a current location ofremote communications node 108, and corresponding maneuvers are communicated to the user ofremote communications node 108. - FIG. 9 shows a flow chart of a method of navigation guidance according to one embodiment of the invention. In
step 400,remote communications node 108requests navigation route location location 202, or first location, i.e. 302) andvelocity vector 303 toservers 102 andcommunications node - In step402, the locus of possible second locations is calculated. This can also include the set of multiple route threads if
remote communications node 108 is stationary. Instep 404,navigation route remote communications node 108 with multiple route threads and route segments. - In
step 406,remote communications node 108 receivesnavigation route step 408, the actualsecond location 308 ofremote communications node 108 is determined and the corresponding set of multiple route threads are utilized and maneuvers communicated to any interested actors, which can include a user ofremote communications node 108. Maneuvers are communicated to interested actors via wireless or wireline communication means, voice and visual communication means, and the like. - In step409 a route thread is selected from the set of multiple route threads based on a current location of
remote communications node 108. In the case of multiple route threads using the same route segment, the route thread representing the preferred route is selected. A set of maneuver instructions are communicated to a user of theremote communications node 108 based on the route thread selected. - In
optional step 410,navigation route remote communications node 108 and optionally, any other road conditions, such as accidents, road closures, weather conditions, and the like. This process can repeat as often as necessary each time a new actualsecond location 308 is determined or updated. - While we have shown and described specific embodiments of the present invention, further modifications and improvements will occur to those skilled in the art. We desire it to be understood, therefore, that this invention is not limited to the particular forms shown and we intend in the appended claims to cover all modifications that do not depart from the spirit and scope of this invention.
Claims (39)
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/753,833 US6421602B1 (en) | 2001-01-03 | 2001-01-03 | Method of navigation guidance for a distributed communications system having communications nodes |
EP01130927A EP1221588B1 (en) | 2001-01-03 | 2001-12-27 | Method of navigation guidance |
DE60144511T DE60144511D1 (en) | 2001-01-03 | 2001-12-27 | navigation methods |
EP11158134A EP2341315B1 (en) | 2001-01-03 | 2001-12-27 | Method of navigation guidance |
DK01130927.5T DK1221588T3 (en) | 2001-01-03 | 2001-12-27 | Navigation management method |
ES11158134T ES2392956T3 (en) | 2001-01-03 | 2001-12-27 | Navigation Guidance Method |
AT01130927T ATE507461T1 (en) | 2001-01-03 | 2001-12-27 | NAVIGATION METHOD |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/753,833 US6421602B1 (en) | 2001-01-03 | 2001-01-03 | Method of navigation guidance for a distributed communications system having communications nodes |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020087262A1 true US20020087262A1 (en) | 2002-07-04 |
US6421602B1 US6421602B1 (en) | 2002-07-16 |
Family
ID=25032346
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/753,833 Expired - Lifetime US6421602B1 (en) | 2001-01-03 | 2001-01-03 | Method of navigation guidance for a distributed communications system having communications nodes |
Country Status (6)
Country | Link |
---|---|
US (1) | US6421602B1 (en) |
EP (2) | EP1221588B1 (en) |
AT (1) | ATE507461T1 (en) |
DE (1) | DE60144511D1 (en) |
DK (1) | DK1221588T3 (en) |
ES (1) | ES2392956T3 (en) |
Cited By (70)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6567741B1 (en) * | 2001-11-01 | 2003-05-20 | General Motors Corporation | Method and system for reducing shape points for a navigation system |
US20040044466A1 (en) * | 2002-08-29 | 2004-03-04 | Nesbitt David W. | Automated route determination |
US7356405B1 (en) * | 2002-08-29 | 2008-04-08 | Aol Llc | Automated route determination to avoid a particular maneuver |
US20080140605A1 (en) * | 2006-07-10 | 2008-06-12 | Jens Gelhar | Database management using format description |
US20080147313A1 (en) * | 2002-12-30 | 2008-06-19 | Aol Llc | Presenting a travel route |
US20080168396A1 (en) * | 2007-01-07 | 2008-07-10 | Michael Matas | Portable Multifunction Device, Method, and Graphical User Interface for Providing Maps and Directions |
US20090178007A1 (en) * | 2008-01-06 | 2009-07-09 | Michael Matas | Touch Screen Device, Method, and Graphical User Interface for Displaying and Selecting Application Options |
US20090174680A1 (en) * | 2008-01-06 | 2009-07-09 | Freddy Allen Anzures | Portable Multifunction Device, Method, and Graphical User Interface for Viewing and Managing Electronic Calendars |
US20090237202A1 (en) * | 2008-03-18 | 2009-09-24 | Mullet Willis J | Operator system utilizing a position detector to initiate a closing sequence |
US20090289778A1 (en) * | 2005-02-10 | 2009-11-26 | Quentin King | System for applying tactile stimulation to the controller of unmanned vehicles |
DE102008059278A1 (en) * | 2008-11-27 | 2010-06-02 | GM Global Technology Operations, Inc., Detroit | Method for updating data of a navigation system |
US20100145569A1 (en) * | 2008-12-09 | 2010-06-10 | Francis Bourque | Method and System for Providing Environmentally-Optimized Navigation Routes |
US20100235079A1 (en) * | 2009-03-13 | 2010-09-16 | Denso Corporation | Navigation apparatus |
US20100241342A1 (en) * | 2009-03-18 | 2010-09-23 | Ford Global Technologies, Llc | Dynamic traffic assessment and reporting |
US7818116B1 (en) | 2002-12-30 | 2010-10-19 | Mapquest, Inc. | Presenting a travel route in a ground-based vehicle |
US20100309149A1 (en) * | 2009-06-07 | 2010-12-09 | Chris Blumenberg | Device, Method, and Graphical User Interface for Providing Maps, Directions, and Location-Based Information |
US7904238B2 (en) | 2002-12-30 | 2011-03-08 | Mapquest, Inc. | Presenting a travel route using more than one presentation style |
US7966003B2 (en) | 2004-07-09 | 2011-06-21 | Tegic Communications, Inc. | Disambiguating ambiguous characters |
US20110167058A1 (en) * | 2010-01-06 | 2011-07-07 | Van Os Marcel | Device, Method, and Graphical User Interface for Mapping Directions Between Search Results |
US20110163874A1 (en) * | 2010-01-06 | 2011-07-07 | Van Os Marcel | Device, Method, and Graphical User Interface for Tracking Movement on a Map |
US20110238285A1 (en) * | 2010-03-24 | 2011-09-29 | Telenav, Inc. | Navigation system with traffic estimation using pipeline scheme mechanism and method of operation thereof |
US20110246059A1 (en) * | 2010-03-31 | 2011-10-06 | Sony Corporation | Information processing apparatus, behavior prediction display method, and computer program therefor |
US20120029806A1 (en) * | 2010-07-30 | 2012-02-02 | Ford Global Technologies, Llc | Efficient Navigation Data Downloading |
WO2011084156A3 (en) * | 2010-01-06 | 2012-06-21 | Apple Inc. | Device, method, and graphical user interface for mapping directions between search results |
US20120202530A1 (en) * | 2002-04-10 | 2012-08-09 | Sheha Michael A | Method and System for Dynamic Estimation and Predictive Route Generation |
US8302033B2 (en) | 2007-06-22 | 2012-10-30 | Apple Inc. | Touch screen device, method, and graphical user interface for providing maps, directions, and location-based information |
US8335643B2 (en) | 2010-08-10 | 2012-12-18 | Ford Global Technologies, Llc | Point of interest search, identification, and navigation |
US20130116882A1 (en) * | 2007-05-03 | 2013-05-09 | Hughes Telematics, Inc. | Methods, systems, and apparatuses for telematics navigation |
US8483958B2 (en) | 2010-12-20 | 2013-07-09 | Ford Global Technologies, Llc | User configurable onboard navigation system crossroad presentation |
US20130184992A1 (en) * | 2012-01-17 | 2013-07-18 | International Business Machines Corporation | Method, apparatus and computer program for estimating driver's personality of route selection |
US8521424B2 (en) | 2010-09-29 | 2013-08-27 | Ford Global Technologies, Llc | Advanced map information delivery, processing and updating |
US8620579B1 (en) * | 2009-11-12 | 2013-12-31 | Google Inc. | Enhanced identification of interesting points-of-interest |
US8688321B2 (en) | 2011-07-11 | 2014-04-01 | Ford Global Technologies, Llc | Traffic density estimation |
US20140114566A1 (en) * | 2006-04-26 | 2014-04-24 | Aol Inc. | Biasing of search result clustering to ensure more effective point of interest (poi) targeting |
US8731814B2 (en) | 2010-07-02 | 2014-05-20 | Ford Global Technologies, Llc | Multi-modal navigation system and method |
US8768107B2 (en) | 2009-12-07 | 2014-07-01 | Google Inc. | Matching an approximately located query image against a reference image set |
US8774527B1 (en) | 2009-12-07 | 2014-07-08 | Google Inc. | Matching an approximately located query image against a reference image set using cellular base station and wireless access point information |
US8838385B2 (en) | 2011-12-20 | 2014-09-16 | Ford Global Technologies, Llc | Method and apparatus for vehicle routing |
US8849552B2 (en) | 2010-09-29 | 2014-09-30 | Ford Global Technologies, Llc | Advanced map information delivery, processing and updating |
US8977479B2 (en) | 2013-03-12 | 2015-03-10 | Ford Global Technologies, Llc | Method and apparatus for determining traffic conditions |
US9047774B2 (en) | 2013-03-12 | 2015-06-02 | Ford Global Technologies, Llc | Method and apparatus for crowd-sourced traffic reporting |
US9137636B2 (en) | 2005-03-07 | 2015-09-15 | Telecommunication Systems, Inc. | Method and system for identifying and defining geofences |
US9217651B2 (en) | 2003-02-14 | 2015-12-22 | Telecommunication Systems, Inc. | Method and system for saving and retrieving spatial related information |
US9400591B2 (en) | 2010-05-21 | 2016-07-26 | Telecommunication Systems, Inc. | Personal wireless navigation system |
US20160290819A1 (en) * | 2015-03-31 | 2016-10-06 | International Business Machines Corporation | Linear projection-based navigation |
US9483763B2 (en) | 2014-05-29 | 2016-11-01 | Apple Inc. | User interface for payments |
US9547419B2 (en) | 2014-09-02 | 2017-01-17 | Apple Inc. | Reduced size configuration interface |
US9574896B2 (en) | 2015-02-13 | 2017-02-21 | Apple Inc. | Navigation user interface |
US9574884B1 (en) * | 2015-09-22 | 2017-02-21 | Cerner Innovation, Inc. | Providing a route through a predefined space |
US9582177B2 (en) | 2002-03-01 | 2017-02-28 | Telecommunication Systems, Inc. | Method and apparatus for sending, retrieving, and planning location relevant information |
US9651385B2 (en) | 2015-09-22 | 2017-05-16 | Cerner Innovation, Inc. | Providing a route through a predefined space |
DK178984B1 (en) * | 2014-09-02 | 2017-07-24 | Apple Inc | Brugerinteraktioner for en kort-applikation |
US9713963B2 (en) | 2013-02-18 | 2017-07-25 | Ford Global Technologies, Llc | Method and apparatus for route completion likelihood display |
US9846046B2 (en) | 2010-07-30 | 2017-12-19 | Ford Global Technologies, Llc | Vehicle navigation method and system |
US9863777B2 (en) | 2013-02-25 | 2018-01-09 | Ford Global Technologies, Llc | Method and apparatus for automatic estimated time of arrival calculation and provision |
US9874452B2 (en) | 2013-03-14 | 2018-01-23 | Ford Global Technologies, Llc | Method and apparatus for enhanced driving experience including dynamic POI identification |
US9940637B2 (en) | 2015-06-05 | 2018-04-10 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US9967401B2 (en) | 2014-05-30 | 2018-05-08 | Apple Inc. | User interface for phone call routing among devices |
US20180335308A1 (en) * | 2017-05-22 | 2018-11-22 | At&T Intellectual Property I, L.P. | Systems and methods for providing improved navigation through interactive suggestion of improved solutions along a path of waypoints |
US10216351B2 (en) | 2015-03-08 | 2019-02-26 | Apple Inc. | Device configuration user interface |
US10250735B2 (en) | 2013-10-30 | 2019-04-02 | Apple Inc. | Displaying relevant user interface objects |
US10255595B2 (en) | 2015-02-01 | 2019-04-09 | Apple Inc. | User interface for payments |
US10272294B2 (en) | 2016-06-11 | 2019-04-30 | Apple Inc. | Activity and workout updates |
US10332079B2 (en) | 2015-06-05 | 2019-06-25 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US10339293B2 (en) | 2014-08-15 | 2019-07-02 | Apple Inc. | Authenticated device used to unlock another device |
US10621581B2 (en) | 2016-06-11 | 2020-04-14 | Apple Inc. | User interface for transactions |
US10860199B2 (en) | 2016-09-23 | 2020-12-08 | Apple Inc. | Dynamically adjusting touch hysteresis based on contextual data |
US11863700B2 (en) | 2019-05-06 | 2024-01-02 | Apple Inc. | Providing user interfaces based on use contexts and managing playback of media |
US12002042B2 (en) | 2016-06-11 | 2024-06-04 | Apple, Inc | User interface for transactions |
US12022359B2 (en) | 2020-05-18 | 2024-06-25 | Apple Inc. | User interfaces for viewing and refining the current location of an electronic device |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6405128B1 (en) * | 1999-12-20 | 2002-06-11 | Navigation Technologies Corp. | Method and system for providing an electronic horizon in an advanced driver assistance system architecture |
GB2360588B (en) * | 2000-03-23 | 2004-04-07 | Yeoman Group Plc | Navigation system |
GB0011797D0 (en) * | 2000-05-16 | 2000-07-05 | Yeoman Group Plc | Improved vehicle routeing |
GB0119391D0 (en) * | 2001-08-09 | 2001-10-03 | Koninkl Philips Electronics Nv | Handover in cellular radio systems |
JP2003106845A (en) * | 2001-09-28 | 2003-04-09 | Pioneer Electronic Corp | Navigation system, traveling member navigation apparatus and communication navigation apparatus as well as information server, method for navigation, method for navigating traveling member and method for communication navigating as well as method for processing server, navigation program, traveling member navigation program and communication navigation program as well as server processing program and information recording medium |
JP2003114133A (en) * | 2001-10-05 | 2003-04-18 | Pioneer Electronic Corp | Communication navigation method, communication navigation system, and terminal apparatus |
US7127271B1 (en) | 2001-10-18 | 2006-10-24 | Iwao Fujisaki | Communication device |
US7107081B1 (en) | 2001-10-18 | 2006-09-12 | Iwao Fujisaki | Communication device |
US7466992B1 (en) | 2001-10-18 | 2008-12-16 | Iwao Fujisaki | Communication device |
US6606557B2 (en) * | 2001-12-07 | 2003-08-12 | Motorola, Inc. | Method for improving dispatch response time |
JP2003240574A (en) * | 2002-02-14 | 2003-08-27 | Mitsubishi Electric Corp | Navigation apparatus and method therefor |
US6807129B1 (en) * | 2002-02-28 | 2004-10-19 | Sunflower Holdings Ltd. | Clock |
US6775613B2 (en) * | 2002-03-25 | 2004-08-10 | General Motors Corporation | Method and system for vehicle proximity searching |
US7243134B2 (en) * | 2002-06-25 | 2007-07-10 | Motorola, Inc. | Server-based navigation system having dynamic transmittal of route information |
CN1278501C (en) * | 2002-12-06 | 2006-10-04 | 国际商业机器公司 | Compressing method and compressing equipment for mobile target-position data |
KR100965662B1 (en) * | 2003-01-11 | 2010-06-24 | 삼성전자주식회사 | Navigation system using paging channel and method for providing traffic information |
US8229512B1 (en) | 2003-02-08 | 2012-07-24 | Iwao Fujisaki | Communication device |
US8241128B1 (en) | 2003-04-03 | 2012-08-14 | Iwao Fujisaki | Communication device |
US20040259573A1 (en) * | 2003-06-20 | 2004-12-23 | Steven D. Cheng | System and method for providing position alerting with a mobile device |
JP4390492B2 (en) * | 2003-07-30 | 2009-12-24 | パイオニア株式会社 | GUIDANCE GUIDE DEVICE, ITS SYSTEM, ITS METHOD, ITS PROGRAM, AND RECORDING MEDIUM CONTAINING THE PROGRAM |
US8090402B1 (en) | 2003-09-26 | 2012-01-03 | Iwao Fujisaki | Communication device |
US7917167B1 (en) | 2003-11-22 | 2011-03-29 | Iwao Fujisaki | Communication device |
US8041348B1 (en) | 2004-03-23 | 2011-10-18 | Iwao Fujisaki | Communication device |
US7418339B2 (en) * | 2005-02-14 | 2008-08-26 | Motorola, Inc. | Method for initiating navigation guidance in a distributed communications system |
US8208954B1 (en) | 2005-04-08 | 2012-06-26 | Iwao Fujisaki | Communication device |
US20070005239A1 (en) * | 2005-06-29 | 2007-01-04 | Franck Kirouchenaradje | Method and system for initialization in distributed navigation |
US20070191021A1 (en) * | 2006-02-13 | 2007-08-16 | Thomas Cantwell | Apparatus and methods for information handling system with flexible communication capabilities |
US7890089B1 (en) | 2007-05-03 | 2011-02-15 | Iwao Fujisaki | Communication device |
US8559983B1 (en) | 2007-05-03 | 2013-10-15 | Iwao Fujisaki | Communication device |
US8676273B1 (en) | 2007-08-24 | 2014-03-18 | Iwao Fujisaki | Communication device |
US8639214B1 (en) | 2007-10-26 | 2014-01-28 | Iwao Fujisaki | Communication device |
US8472935B1 (en) | 2007-10-29 | 2013-06-25 | Iwao Fujisaki | Communication device |
US8744720B1 (en) | 2007-12-27 | 2014-06-03 | Iwao Fujisaki | Inter-vehicle middle point maintaining implementer |
US8543157B1 (en) | 2008-05-09 | 2013-09-24 | Iwao Fujisaki | Communication device which notifies its pin-point location or geographic area in accordance with user selection |
US20090315766A1 (en) * | 2008-06-19 | 2009-12-24 | Microsoft Corporation | Source switching for devices supporting dynamic direction information |
US8700301B2 (en) | 2008-06-19 | 2014-04-15 | Microsoft Corporation | Mobile computing devices, architecture and user interfaces based on dynamic direction information |
US8467991B2 (en) | 2008-06-20 | 2013-06-18 | Microsoft Corporation | Data services based on gesture and location information of device |
US8340726B1 (en) | 2008-06-30 | 2012-12-25 | Iwao Fujisaki | Communication device |
US8452307B1 (en) | 2008-07-02 | 2013-05-28 | Iwao Fujisaki | Communication device |
WO2010072258A1 (en) * | 2008-12-23 | 2010-07-01 | Tomtom International B.V. | Navigation devices and methods for pre-calculating an alternate route |
US8872767B2 (en) | 2009-07-07 | 2014-10-28 | Microsoft Corporation | System and method for converting gestures into digital graffiti |
TWI472717B (en) * | 2010-02-24 | 2015-02-11 | 私立中原大學 | Help with active navigation system |
US20120323481A1 (en) * | 2011-06-20 | 2012-12-20 | International Business Machines Corporation | Navigating out of a parking lot |
US9780967B2 (en) | 2013-03-14 | 2017-10-03 | Telogis, Inc. | System for performing vehicle diagnostic and prognostic analysis |
WO2014159127A1 (en) | 2013-03-14 | 2014-10-02 | Telogis Inc. | System and method for crowdsourcing vehicle-related analytics |
WO2016065320A1 (en) * | 2014-10-24 | 2016-04-28 | Telogis, Inc. | System for performing vehicle diagnostic and prognostic analysis |
US9810541B2 (en) * | 2015-11-16 | 2017-11-07 | Honeywell International Inc. | Methods and apparatus for reducing the size of received data transmission during vehicle travel |
Family Cites Families (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5220507A (en) * | 1990-11-08 | 1993-06-15 | Motorola, Inc. | Land vehicle multiple navigation route apparatus |
WO1992014215A1 (en) * | 1991-02-01 | 1992-08-20 | Peterson Thomas D | Method and apparatus for providing shortest elapsed time route information to users |
AU671951B2 (en) * | 1991-06-05 | 1996-09-19 | Toshio Tsuyuki | Navigation apparatus and navigation method |
US5608635A (en) * | 1992-04-14 | 1997-03-04 | Zexel Corporation | Navigation system for a vehicle with route recalculation between multiple locations |
US5543789A (en) * | 1994-06-24 | 1996-08-06 | Shields Enterprises, Inc. | Computerized navigation system |
US5875412A (en) * | 1994-08-03 | 1999-02-23 | Siemens Automotive L.P. | Vehicle navigation and route guidance system |
KR100263982B1 (en) * | 1996-04-28 | 2000-08-16 | 모리 하루오 | Navigation apparatus |
JP2910674B2 (en) * | 1996-05-28 | 1999-06-23 | 日本電気株式会社 | Mobile phone navigation system by voice |
DE19640068A1 (en) * | 1996-09-28 | 1998-04-02 | Alsthom Cge Alcatel | Destination finder for vehicle |
US6249740B1 (en) * | 1998-01-21 | 2001-06-19 | Kabushikikaisha Equos Research | Communications navigation system, and navigation base apparatus and vehicle navigation apparatus both used in the navigation system |
DE19804060B4 (en) * | 1998-02-03 | 2005-08-18 | T-Mobile Deutschland Gmbh | Method for informing subscribers of a traffic telematics system |
FR2774468B1 (en) * | 1998-02-03 | 2000-03-17 | Renault | SYSTEM AND METHODS FOR DYNAMIC GUIDANCE OF A MOTOR VEHICLE |
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 |
DE60027499T2 (en) | 1999-03-05 | 2006-11-16 | Hitachi, Ltd. | Information presentation system for mobile units |
JP4084901B2 (en) * | 1999-03-05 | 2008-04-30 | 株式会社日立製作所 | Information provision system |
US6314365B1 (en) * | 2000-01-18 | 2001-11-06 | Navigation Technologies Corp. | Method and system of providing navigation services to cellular phone devices from a server |
-
2001
- 2001-01-03 US US09/753,833 patent/US6421602B1/en not_active Expired - Lifetime
- 2001-12-27 AT AT01130927T patent/ATE507461T1/en active
- 2001-12-27 EP EP01130927A patent/EP1221588B1/en not_active Expired - Lifetime
- 2001-12-27 DK DK01130927.5T patent/DK1221588T3/en active
- 2001-12-27 ES ES11158134T patent/ES2392956T3/en not_active Expired - Lifetime
- 2001-12-27 DE DE60144511T patent/DE60144511D1/en not_active Expired - Lifetime
- 2001-12-27 EP EP11158134A patent/EP2341315B1/en not_active Expired - Lifetime
Cited By (165)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6567741B1 (en) * | 2001-11-01 | 2003-05-20 | General Motors Corporation | Method and system for reducing shape points for a navigation system |
US9582177B2 (en) | 2002-03-01 | 2017-02-28 | Telecommunication Systems, Inc. | Method and apparatus for sending, retrieving, and planning location relevant information |
US20120202530A1 (en) * | 2002-04-10 | 2012-08-09 | Sheha Michael A | Method and System for Dynamic Estimation and Predictive Route Generation |
US9354069B2 (en) | 2002-04-10 | 2016-05-31 | Bluestone Ventures, Inc. | Method and system for dynamic estimation and predictive route generation |
US8577390B2 (en) * | 2002-04-10 | 2013-11-05 | Telecommunication Systems, Inc. | Method and system for dynamic estimation and predictive route generation |
US10718623B2 (en) | 2002-08-29 | 2020-07-21 | Verizon Patent And Licensing, Inc. | Automated route determination |
US8560223B2 (en) | 2002-08-29 | 2013-10-15 | Mapquest, Inc. | Automated route determination |
US8655583B2 (en) | 2002-08-29 | 2014-02-18 | Mapquest, Inc. | Automated route determination |
US20040052239A1 (en) * | 2002-08-29 | 2004-03-18 | Nesbitt David W. | Automated route determination |
US7356405B1 (en) * | 2002-08-29 | 2008-04-08 | Aol Llc | Automated route determination to avoid a particular maneuver |
US10697785B2 (en) | 2002-08-29 | 2020-06-30 | Verizon Patent And Licensing, Inc. | Automated route determination |
US8510040B2 (en) | 2002-08-29 | 2013-08-13 | Mapquest, Inc. | Automated route determination |
US20040044466A1 (en) * | 2002-08-29 | 2004-03-04 | Nesbitt David W. | Automated route determination |
US20100121562A1 (en) * | 2002-08-29 | 2010-05-13 | Aol Inc. | Automated route determination |
US8649975B2 (en) | 2002-08-29 | 2014-02-11 | Mapquest, Inc. | Automated route determination |
US10551203B2 (en) | 2002-08-29 | 2020-02-04 | Verizon Patent And Licensing Inc. | Automated route determination |
US8335646B2 (en) | 2002-12-30 | 2012-12-18 | Aol Inc. | Presenting a travel route |
US20110153187A1 (en) * | 2002-12-30 | 2011-06-23 | Mapquest, Inc. | Presenting a travel route using more than one presentation style |
US7818116B1 (en) | 2002-12-30 | 2010-10-19 | Mapquest, Inc. | Presenting a travel route in a ground-based vehicle |
US8954274B2 (en) | 2002-12-30 | 2015-02-10 | Facebook, Inc. | Indicating a travel route based on a user selection |
US7904238B2 (en) | 2002-12-30 | 2011-03-08 | Mapquest, Inc. | Presenting a travel route using more than one presentation style |
US7925430B2 (en) | 2002-12-30 | 2011-04-12 | Aol Inc. | Presenting a travel route |
US8977497B2 (en) | 2002-12-30 | 2015-03-10 | Aol Inc. | Presenting a travel route |
US10113880B2 (en) | 2002-12-30 | 2018-10-30 | Facebook, Inc. | Custom printing of a travel route |
US9599487B2 (en) | 2002-12-30 | 2017-03-21 | Mapquest, Inc. | Presenting a travel route |
US7702454B2 (en) | 2002-12-30 | 2010-04-20 | Mapquest, Inc. | Presenting a travel route |
US7474960B1 (en) * | 2002-12-30 | 2009-01-06 | Mapquest, Inc. | Presenting a travel route |
US20080147313A1 (en) * | 2002-12-30 | 2008-06-19 | Aol Llc | Presenting a travel route |
US8296061B2 (en) | 2002-12-30 | 2012-10-23 | Facebook, Inc. | Presenting a travel route using more than one presentation style |
US9217651B2 (en) | 2003-02-14 | 2015-12-22 | Telecommunication Systems, Inc. | Method and system for saving and retrieving spatial related information |
US7966003B2 (en) | 2004-07-09 | 2011-06-21 | Tegic Communications, Inc. | Disambiguating ambiguous characters |
US8583087B2 (en) | 2004-07-09 | 2013-11-12 | Nuance Communications, Inc. | Disambiguating ambiguous characters |
US20090289778A1 (en) * | 2005-02-10 | 2009-11-26 | Quentin King | System for applying tactile stimulation to the controller of unmanned vehicles |
US8299905B2 (en) * | 2005-02-10 | 2012-10-30 | Quentin King | System for applying tactile stimulation to the controller of unmanned vehicles |
US9137636B2 (en) | 2005-03-07 | 2015-09-15 | Telecommunication Systems, Inc. | Method and system for identifying and defining geofences |
US20140114566A1 (en) * | 2006-04-26 | 2014-04-24 | Aol Inc. | Biasing of search result clustering to ensure more effective point of interest (poi) targeting |
US9835461B2 (en) * | 2006-07-10 | 2017-12-05 | Harman Becker Automotive Systems Gmbh | Database management using format description |
US20080140605A1 (en) * | 2006-07-10 | 2008-06-12 | Jens Gelhar | Database management using format description |
US8607167B2 (en) | 2007-01-07 | 2013-12-10 | Apple Inc. | Portable multifunction device, method, and graphical user interface for providing maps and directions |
US20080168396A1 (en) * | 2007-01-07 | 2008-07-10 | Michael Matas | Portable Multifunction Device, Method, and Graphical User Interface for Providing Maps and Directions |
US9395186B2 (en) * | 2007-05-03 | 2016-07-19 | Verizon Telematics Inc. | Methods systems, and apparatuses for telematics navigation |
US20130116882A1 (en) * | 2007-05-03 | 2013-05-09 | Hughes Telematics, Inc. | Methods, systems, and apparatuses for telematics navigation |
US8302033B2 (en) | 2007-06-22 | 2012-10-30 | Apple Inc. | Touch screen device, method, and graphical user interface for providing maps, directions, and location-based information |
US10686930B2 (en) | 2007-06-22 | 2020-06-16 | Apple Inc. | Touch screen device, method, and graphical user interface for providing maps, directions, and location based information |
US11849063B2 (en) | 2007-06-22 | 2023-12-19 | Apple Inc. | Touch screen device, method, and graphical user interface for providing maps, directions, and location-based information |
US10521084B2 (en) | 2008-01-06 | 2019-12-31 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
US8327272B2 (en) | 2008-01-06 | 2012-12-04 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
US20090178007A1 (en) * | 2008-01-06 | 2009-07-09 | Michael Matas | Touch Screen Device, Method, and Graphical User Interface for Displaying and Selecting Application Options |
US11126326B2 (en) | 2008-01-06 | 2021-09-21 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
US8171432B2 (en) | 2008-01-06 | 2012-05-01 | Apple Inc. | Touch screen device, method, and graphical user interface for displaying and selecting application options |
US9330381B2 (en) | 2008-01-06 | 2016-05-03 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
US20090174680A1 (en) * | 2008-01-06 | 2009-07-09 | Freddy Allen Anzures | Portable Multifunction Device, Method, and Graphical User Interface for Viewing and Managing Electronic Calendars |
US9792001B2 (en) | 2008-01-06 | 2017-10-17 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
US10503366B2 (en) | 2008-01-06 | 2019-12-10 | Apple Inc. | Portable multifunction device, method, and graphical user interface for viewing and managing electronic calendars |
US20090237202A1 (en) * | 2008-03-18 | 2009-09-24 | Mullet Willis J | Operator system utilizing a position detector to initiate a closing sequence |
US8299893B2 (en) * | 2008-03-18 | 2012-10-30 | Homerun Holdings Corporation | Operator system utilizing a position detector to initiate a closing sequence |
DE102008059278A1 (en) * | 2008-11-27 | 2010-06-02 | GM Global Technology Operations, Inc., Detroit | Method for updating data of a navigation system |
US8775569B2 (en) | 2008-11-27 | 2014-07-08 | GM Global Technology Operations LLC | Method for updating the data of a navigation system |
US8255151B2 (en) | 2008-12-09 | 2012-08-28 | Motorola Mobility Llc | Method and system for providing environmentally-optimized navigation routes |
US20100145569A1 (en) * | 2008-12-09 | 2010-06-10 | Francis Bourque | Method and System for Providing Environmentally-Optimized Navigation Routes |
US20100235079A1 (en) * | 2009-03-13 | 2010-09-16 | Denso Corporation | Navigation apparatus |
US20100241342A1 (en) * | 2009-03-18 | 2010-09-23 | Ford Global Technologies, Llc | Dynamic traffic assessment and reporting |
US20100309149A1 (en) * | 2009-06-07 | 2010-12-09 | Chris Blumenberg | Device, Method, and Graphical User Interface for Providing Maps, Directions, and Location-Based Information |
US8464182B2 (en) | 2009-06-07 | 2013-06-11 | Apple Inc. | Device, method, and graphical user interface for providing maps, directions, and location-based information |
US8620579B1 (en) * | 2009-11-12 | 2013-12-31 | Google Inc. | Enhanced identification of interesting points-of-interest |
US8768107B2 (en) | 2009-12-07 | 2014-07-01 | Google Inc. | Matching an approximately located query image against a reference image set |
US8774527B1 (en) | 2009-12-07 | 2014-07-08 | Google Inc. | Matching an approximately located query image against a reference image set using cellular base station and wireless access point information |
US8862576B2 (en) | 2010-01-06 | 2014-10-14 | Apple Inc. | Device, method, and graphical user interface for mapping directions between search results |
WO2011084156A3 (en) * | 2010-01-06 | 2012-06-21 | Apple Inc. | Device, method, and graphical user interface for mapping directions between search results |
US10169431B2 (en) | 2010-01-06 | 2019-01-01 | Apple Inc. | Device, method, and graphical user interface for mapping directions between search results |
US20110167058A1 (en) * | 2010-01-06 | 2011-07-07 | Van Os Marcel | Device, Method, and Graphical User Interface for Mapping Directions Between Search Results |
US20110163874A1 (en) * | 2010-01-06 | 2011-07-07 | Van Os Marcel | Device, Method, and Graphical User Interface for Tracking Movement on a Map |
US8456297B2 (en) | 2010-01-06 | 2013-06-04 | Apple Inc. | Device, method, and graphical user interface for tracking movement on a map |
WO2011119314A1 (en) * | 2010-03-24 | 2011-09-29 | Telenav, Inc. | Navigation system with traffic estimation using pipeline scheme mechanism and method of operation thereof |
US10527448B2 (en) | 2010-03-24 | 2020-01-07 | Telenav, Inc. | Navigation system with traffic estimation using pipeline scheme mechanism and method of operation thereof |
CN102812331A (en) * | 2010-03-24 | 2012-12-05 | 泰为信息科技公司 | Navigation system with traffic estimation using pipeline scheme mechanism and method of operation thereof |
US20110238285A1 (en) * | 2010-03-24 | 2011-09-29 | Telenav, Inc. | Navigation system with traffic estimation using pipeline scheme mechanism and method of operation thereof |
US20110246059A1 (en) * | 2010-03-31 | 2011-10-06 | Sony Corporation | Information processing apparatus, behavior prediction display method, and computer program therefor |
US8918284B2 (en) * | 2010-03-31 | 2014-12-23 | Sony Corporation | Information processing apparatus, behavior prediction display method, and computer program therefor |
US9400591B2 (en) | 2010-05-21 | 2016-07-26 | Telecommunication Systems, Inc. | Personal wireless navigation system |
US8731814B2 (en) | 2010-07-02 | 2014-05-20 | Ford Global Technologies, Llc | Multi-modal navigation system and method |
US9846046B2 (en) | 2010-07-30 | 2017-12-19 | Ford Global Technologies, Llc | Vehicle navigation method and system |
US20120029806A1 (en) * | 2010-07-30 | 2012-02-02 | Ford Global Technologies, Llc | Efficient Navigation Data Downloading |
US8666654B2 (en) | 2010-08-10 | 2014-03-04 | Ford Global Technologies, Llc | Point of interest search, identification, and navigation |
US8335643B2 (en) | 2010-08-10 | 2012-12-18 | Ford Global Technologies, Llc | Point of interest search, identification, and navigation |
US8521424B2 (en) | 2010-09-29 | 2013-08-27 | Ford Global Technologies, Llc | Advanced map information delivery, processing and updating |
US8731823B2 (en) | 2010-09-29 | 2014-05-20 | Ford Global Technologies, Inc. | Advanced map information delivery, processing and updating |
US8849552B2 (en) | 2010-09-29 | 2014-09-30 | Ford Global Technologies, Llc | Advanced map information delivery, processing and updating |
US9568325B2 (en) | 2010-09-29 | 2017-02-14 | Ford Global Technologies, Llc | Advanced map information delivery, processing and updating |
US8483958B2 (en) | 2010-12-20 | 2013-07-09 | Ford Global Technologies, Llc | User configurable onboard navigation system crossroad presentation |
US8688321B2 (en) | 2011-07-11 | 2014-04-01 | Ford Global Technologies, Llc | Traffic density estimation |
US8838385B2 (en) | 2011-12-20 | 2014-09-16 | Ford Global Technologies, Llc | Method and apparatus for vehicle routing |
US8798910B2 (en) * | 2012-01-17 | 2014-08-05 | International Business Machines Corporation | Method, apparatus and computer program for estimating driver's personality of route selection |
US20130184992A1 (en) * | 2012-01-17 | 2013-07-18 | International Business Machines Corporation | Method, apparatus and computer program for estimating driver's personality of route selection |
US9713963B2 (en) | 2013-02-18 | 2017-07-25 | Ford Global Technologies, Llc | Method and apparatus for route completion likelihood display |
US10369897B2 (en) | 2013-02-18 | 2019-08-06 | Ford Global Technologies, Llc | Method and apparatus for route completion likelihood display |
US9863777B2 (en) | 2013-02-25 | 2018-01-09 | Ford Global Technologies, Llc | Method and apparatus for automatic estimated time of arrival calculation and provision |
US8977479B2 (en) | 2013-03-12 | 2015-03-10 | Ford Global Technologies, Llc | Method and apparatus for determining traffic conditions |
US9230431B2 (en) | 2013-03-12 | 2016-01-05 | Ford Global Technologies, Llc | Method and apparatus for determining traffic conditions |
US9047774B2 (en) | 2013-03-12 | 2015-06-02 | Ford Global Technologies, Llc | Method and apparatus for crowd-sourced traffic reporting |
US9530312B2 (en) | 2013-03-12 | 2016-12-27 | Ford Global Technologies, Llc | Method and apparatus for crowd-sourced traffic reporting based on projected traffic volume of road segments |
US9874452B2 (en) | 2013-03-14 | 2018-01-23 | Ford Global Technologies, Llc | Method and apparatus for enhanced driving experience including dynamic POI identification |
US10972600B2 (en) | 2013-10-30 | 2021-04-06 | Apple Inc. | Displaying relevant user interface objects |
US12088755B2 (en) | 2013-10-30 | 2024-09-10 | Apple Inc. | Displaying relevant user interface objects |
US11316968B2 (en) | 2013-10-30 | 2022-04-26 | Apple Inc. | Displaying relevant user interface objects |
US10250735B2 (en) | 2013-10-30 | 2019-04-02 | Apple Inc. | Displaying relevant user interface objects |
US10438205B2 (en) | 2014-05-29 | 2019-10-08 | Apple Inc. | User interface for payments |
US10482461B2 (en) | 2014-05-29 | 2019-11-19 | Apple Inc. | User interface for payments |
US9483763B2 (en) | 2014-05-29 | 2016-11-01 | Apple Inc. | User interface for payments |
US10043185B2 (en) | 2014-05-29 | 2018-08-07 | Apple Inc. | User interface for payments |
US11836725B2 (en) | 2014-05-29 | 2023-12-05 | Apple Inc. | User interface for payments |
US10977651B2 (en) | 2014-05-29 | 2021-04-13 | Apple Inc. | User interface for payments |
US10902424B2 (en) | 2014-05-29 | 2021-01-26 | Apple Inc. | User interface for payments |
US10796309B2 (en) | 2014-05-29 | 2020-10-06 | Apple Inc. | User interface for payments |
US10748153B2 (en) | 2014-05-29 | 2020-08-18 | Apple Inc. | User interface for payments |
US9911123B2 (en) | 2014-05-29 | 2018-03-06 | Apple Inc. | User interface for payments |
US10282727B2 (en) | 2014-05-29 | 2019-05-07 | Apple Inc. | User interface for payments |
US9967401B2 (en) | 2014-05-30 | 2018-05-08 | Apple Inc. | User interface for phone call routing among devices |
US10616416B2 (en) | 2014-05-30 | 2020-04-07 | Apple Inc. | User interface for phone call routing among devices |
US10178234B2 (en) | 2014-05-30 | 2019-01-08 | Apple, Inc. | User interface for phone call routing among devices |
US10339293B2 (en) | 2014-08-15 | 2019-07-02 | Apple Inc. | Authenticated device used to unlock another device |
US11126704B2 (en) | 2014-08-15 | 2021-09-21 | Apple Inc. | Authenticated device used to unlock another device |
US10936164B2 (en) | 2014-09-02 | 2021-03-02 | Apple Inc. | Reduced size configuration interface |
US10324590B2 (en) | 2014-09-02 | 2019-06-18 | Apple Inc. | Reduced size configuration interface |
US10914606B2 (en) | 2014-09-02 | 2021-02-09 | Apple Inc. | User interactions for a mapping application |
US11733055B2 (en) | 2014-09-02 | 2023-08-22 | Apple Inc. | User interactions for a mapping application |
DK178984B1 (en) * | 2014-09-02 | 2017-07-24 | Apple Inc | Brugerinteraktioner for en kort-applikation |
US10579225B2 (en) | 2014-09-02 | 2020-03-03 | Apple Inc. | Reduced size configuration interface |
US11609681B2 (en) | 2014-09-02 | 2023-03-21 | Apple Inc. | Reduced size configuration interface |
US10066959B2 (en) | 2014-09-02 | 2018-09-04 | Apple Inc. | User interactions for a mapping application |
US9547419B2 (en) | 2014-09-02 | 2017-01-17 | Apple Inc. | Reduced size configuration interface |
US10255595B2 (en) | 2015-02-01 | 2019-04-09 | Apple Inc. | User interface for payments |
US9574896B2 (en) | 2015-02-13 | 2017-02-21 | Apple Inc. | Navigation user interface |
US10024682B2 (en) | 2015-02-13 | 2018-07-17 | Apple Inc. | Navigation user interface |
US11079894B2 (en) | 2015-03-08 | 2021-08-03 | Apple Inc. | Device configuration user interface |
US10216351B2 (en) | 2015-03-08 | 2019-02-26 | Apple Inc. | Device configuration user interface |
US10254911B2 (en) | 2015-03-08 | 2019-04-09 | Apple Inc. | Device configuration user interface |
US20170120807A1 (en) * | 2015-03-31 | 2017-05-04 | International Business Machines Corporation | Linear projection-based navigation |
US20160290819A1 (en) * | 2015-03-31 | 2016-10-06 | International Business Machines Corporation | Linear projection-based navigation |
US9593959B2 (en) * | 2015-03-31 | 2017-03-14 | International Business Machines Corporation | Linear projection-based navigation |
US9925916B2 (en) * | 2015-03-31 | 2018-03-27 | International Business Machines Corporation | Linear projection-based navigation |
US11734708B2 (en) | 2015-06-05 | 2023-08-22 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US10332079B2 (en) | 2015-06-05 | 2019-06-25 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US10026094B2 (en) | 2015-06-05 | 2018-07-17 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US11783305B2 (en) | 2015-06-05 | 2023-10-10 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US11321731B2 (en) | 2015-06-05 | 2022-05-03 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US10990934B2 (en) | 2015-06-05 | 2021-04-27 | Apple Inc. | User interface for loyalty accounts and private label accounts for a wearable device |
US10600068B2 (en) | 2015-06-05 | 2020-03-24 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US9940637B2 (en) | 2015-06-05 | 2018-04-10 | Apple Inc. | User interface for loyalty accounts and private label accounts |
US9574884B1 (en) * | 2015-09-22 | 2017-02-21 | Cerner Innovation, Inc. | Providing a route through a predefined space |
US9651385B2 (en) | 2015-09-22 | 2017-05-16 | Cerner Innovation, Inc. | Providing a route through a predefined space |
US10621581B2 (en) | 2016-06-11 | 2020-04-14 | Apple Inc. | User interface for transactions |
US11918857B2 (en) | 2016-06-11 | 2024-03-05 | Apple Inc. | Activity and workout updates |
US11161010B2 (en) | 2016-06-11 | 2021-11-02 | Apple Inc. | Activity and workout updates |
US11660503B2 (en) | 2016-06-11 | 2023-05-30 | Apple Inc. | Activity and workout updates |
US11148007B2 (en) | 2016-06-11 | 2021-10-19 | Apple Inc. | Activity and workout updates |
US10272294B2 (en) | 2016-06-11 | 2019-04-30 | Apple Inc. | Activity and workout updates |
US12002042B2 (en) | 2016-06-11 | 2024-06-04 | Apple, Inc | User interface for transactions |
US11481769B2 (en) | 2016-06-11 | 2022-10-25 | Apple Inc. | User interface for transactions |
US10860199B2 (en) | 2016-09-23 | 2020-12-08 | Apple Inc. | Dynamically adjusting touch hysteresis based on contextual data |
US20180335308A1 (en) * | 2017-05-22 | 2018-11-22 | At&T Intellectual Property I, L.P. | Systems and methods for providing improved navigation through interactive suggestion of improved solutions along a path of waypoints |
US10677599B2 (en) * | 2017-05-22 | 2020-06-09 | At&T Intellectual Property I, L.P. | Systems and methods for providing improved navigation through interactive suggestion of improved solutions along a path of waypoints |
US11137257B2 (en) * | 2017-05-22 | 2021-10-05 | At&T Intellectual Property I, L.P. | Systems and methods for providing improved navigation through interactive suggestion of improved solutions along a path of waypoints |
US11863700B2 (en) | 2019-05-06 | 2024-01-02 | Apple Inc. | Providing user interfaces based on use contexts and managing playback of media |
US12022359B2 (en) | 2020-05-18 | 2024-06-25 | Apple Inc. | User interfaces for viewing and refining the current location of an electronic device |
Also Published As
Publication number | Publication date |
---|---|
ATE507461T1 (en) | 2011-05-15 |
DE60144511D1 (en) | 2011-06-09 |
US6421602B1 (en) | 2002-07-16 |
DK1221588T3 (en) | 2011-06-20 |
EP2341315B1 (en) | 2012-08-22 |
EP1221588A1 (en) | 2002-07-10 |
EP2341315A1 (en) | 2011-07-06 |
EP1221588B1 (en) | 2011-04-27 |
ES2392956T3 (en) | 2012-12-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6421602B1 (en) | Method of navigation guidance for a distributed communications system having communications nodes | |
US8494764B2 (en) | Method and system for coordinating the routes of a plurality of navigation devices | |
US6463382B1 (en) | Method of optimizing traffic content | |
US6970703B2 (en) | Integrated personal communications system and method | |
US10416980B2 (en) | Intelligent location based services and navigation hybrid system | |
US20050049785A1 (en) | Off-board navigation system | |
US8990005B2 (en) | System and method for providing georeferenced predictive information to motor vehicles | |
US20170010113A1 (en) | Method for associating a hazard with a zone of a digital map | |
JP4180837B2 (en) | Method and system for providing backup operation instruction using navigation system | |
US20040117113A1 (en) | Updating routing and traffic flow data and vehicle navigation device | |
JP2007318354A (en) | Communication device for mobile and communication method for mobile | |
US8615358B2 (en) | System and method for zone based initial route guidance within a telematics equipped mobile vehicle | |
US20040160359A1 (en) | Provision of navigation information | |
US6973324B2 (en) | Method of enabling the transmission of data in a wireless communication network | |
US20020132627A1 (en) | Information assisting system, information assisting method, information terminal apparatus, and information assisting apparatus | |
JP2006172061A (en) | Method, device and system for managing reservation object | |
US20030129961A1 (en) | Method of optimizing the transmission of data in a wireless communication network | |
JP2005063234A (en) | Portal server and cache server in content distribution system, and content distribution method and content distribution program | |
JP4075649B2 (en) | Vehicle information communication device | |
JP2004343618A (en) | On-vehicle electronic equipment and radio communication method using the same | |
WO2024031751A1 (en) | Navigation method, roadside unit, mobile terminal, navigation system and vehicle | |
CA2556640C (en) | Off-board navigational system | |
JP2008096449A (en) | Information terminal device | |
JP2004265040A (en) | Traveling body location management system | |
KR100536007B1 (en) | Course Guiding Method in Navigation System Using Mobile Terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MOTOROLA, INC., ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BULLOCK, JAMES BLAKE;SAAVEDRA, RAFAEL A.;REEL/FRAME:011450/0100 Effective date: 20001211 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: MOTOROLA MOBILITY, INC, ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA, INC;REEL/FRAME:025673/0558 Effective date: 20100731 |
|
AS | Assignment |
Owner name: MOTOROLA MOBILITY LLC, ILLINOIS Free format text: CHANGE OF NAME;ASSIGNOR:MOTOROLA MOBILITY, INC.;REEL/FRAME:029216/0282 Effective date: 20120622 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: GOOGLE TECHNOLOGY HOLDINGS LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA MOBILITY LLC;REEL/FRAME:034491/0001 Effective date: 20141028 |