US7289904B2 - Vehicle navigation system and methods for incorporating user preferences into same - Google Patents

Vehicle navigation system and methods for incorporating user preferences into same Download PDF

Info

Publication number
US7289904B2
US7289904B2 US11/040,710 US4071005A US7289904B2 US 7289904 B2 US7289904 B2 US 7289904B2 US 4071005 A US4071005 A US 4071005A US 7289904 B2 US7289904 B2 US 7289904B2
Authority
US
United States
Prior art keywords
traffic information
user
commute
preference
traffic
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.)
Active, expires
Application number
US11/040,710
Other versions
US20050222763A1 (en
Inventor
Robert Uyeki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honda Motor Co Ltd
Original Assignee
Honda Motor Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Honda Motor Co Ltd filed Critical Honda Motor Co Ltd
Priority to US11/040,710 priority Critical patent/US7289904B2/en
Assigned to HONDA MOTOR CO., LTD. reassignment HONDA MOTOR CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: UYEKI, ROBERT
Publication of US20050222763A1 publication Critical patent/US20050222763A1/en
Application granted granted Critical
Publication of US7289904B2 publication Critical patent/US7289904B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G01MEASURING; TESTING
    • G01CMEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/26Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
    • G01C21/34Route searching; Route guidance
    • G01C21/3453Special cost functions, i.e. other than distance or default speed limit of road segments
    • G01C21/3492Special cost functions, i.e. other than distance or default speed limit of road segments employing speed data or traffic data, e.g. real-time or historical
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096708Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
    • G08G1/096716Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096733Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place
    • G08G1/096741Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place where the source of the transmitted information selects which information to transmit to each vehicle
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0967Systems involving transmission of highway information, e.g. weather, speed limits
    • G08G1/096766Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission
    • G08G1/096775Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission where the origin of the information is a central station
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968Systems involving transmission of navigation instructions to the vehicle
    • G08G1/096805Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route
    • G08G1/096827Systems involving transmission of navigation instructions to the vehicle where the transmitted instructions are used to compute a route where the route is computed onboard
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968Systems involving transmission of navigation instructions to the vehicle
    • G08G1/096833Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route
    • G08G1/096838Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route where the user preferences are taken into account or the user selects one route out of a plurality
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968Systems involving transmission of navigation instructions to the vehicle
    • G08G1/096833Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route
    • G08G1/096844Systems involving transmission of navigation instructions to the vehicle where different aspects are considered when computing the route where the complete route is dynamically recomputed based on new data
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968Systems involving transmission of navigation instructions to the vehicle
    • G08G1/096877Systems involving transmission of navigation instructions to the vehicle where the input to the navigation device is provided by a suitable I/O arrangement
    • G08G1/096883Systems involving transmission of navigation instructions to the vehicle where the input to the navigation device is provided by a suitable I/O arrangement where input information is obtained using a mobile device, e.g. a mobile phone, a PDA
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/09Arrangements for giving variable traffic instructions
    • G08G1/0962Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
    • G08G1/0968Systems involving transmission of navigation instructions to the vehicle
    • G08G1/096877Systems involving transmission of navigation instructions to the vehicle where the input to the navigation device is provided by a suitable I/O arrangement
    • G08G1/096888Systems involving transmission of navigation instructions to the vehicle where the input to the navigation device is provided by a suitable I/O arrangement where input information is obtained using learning systems, e.g. history databases

Definitions

  • the present invention relates to a system and method for providing traffic related information between a vehicle and a remote location. More specifically, the present invention relates to a vehicle navigation system that provides personalized traffic information to a user of the vehicle navigation system based at least in part on user preferences.
  • Navigation systems for determining a route from a start point to a destination point are well known in the art.
  • navigation systems having capabilities for determining the geographic position of a reference point are also well known in the art (e.g., a Global Positioning System (GPS) or a self-contained system having distance and bearing sensors).
  • GPS Global Positioning System
  • a commonly used navigation system allows a user (or driver) of a vehicle to enter a destination place into the navigation system.
  • the navigation system looks up an appropriate route from an original point (using its geographic positioning capabilities) to the destination point in a road map database (e.g., the route may be a route having the shortest distance from the start point to the destination, one which would take the vehicle the least time, or some other route), and guides the user to the destination point along the searched route through a visual display or vocal guide.
  • a road map database e.g., the route may be a route having the shortest distance from the start point to the destination, one which would take the vehicle the least time, or some other route
  • traffic information e.g., position data on traffic jams; information on roads closed by accidents, construction, or maintenance; lane-regulated locations
  • traffic information supplier in addition to using the road map database.
  • known methods for providing and utilizing the above-described traffic information for navigation remain very inflexible, cumbersome, and inefficient.
  • one method uses a one-to-one communication system to individually send traffic information streams to a particular vehicle in an attempt to send vehicle specific data to the particular vehicle.
  • a drawback with this method is that many vehicles require the same information. For example, several vehicles might require the same regional traffic information. This method, therefore, requires the transmittal of the same information several times to a plurality of vehicles, which results in a waste of precious bandwidth.
  • wireless network bandwidth is extremely sensitive to network capacity.
  • the same traffic information is transmitted to all vehicles.
  • the drawback with these methods is that many vehicles are inundated with a large amount of unwanted traffic information. Users and/or navigation systems are required to sift through the redundant, superfluous, or otherwise unwanted information to pick out pertinent traffic information.
  • the present invention addresses the shortcomings of the prior art systems and methods.
  • the present invention is directed to a vehicle navigation system that provides automated and personalized traffic information so that a user of the vehicle navigation system does not have to wait for traffic information.
  • One aspect of the present invention allows a user of the vehicle navigation system to preset commute preferences so that traffic information from a traffic information supplier is pre-broadcast to the vehicle navigation device.
  • a user of the vehicle navigation system sets commute preferences in a database (e.g., spreadsheet) on the user's home computer, which is then transmitted to the vehicle navigation system.
  • the destination address and preferred roads may be specified in the database.
  • a user manually enters commute preferences by using touch-sensitive pads on the visual display screen of the vehicle navigation system. The travel route calculated by the vehicle navigation system then becomes a personalized route based at least in part in the user's commute preferences.
  • Another aspect of the present invention provides a vehicle navigation system that stores historical commute patterns to determine when traffic information should be pre-provided to the vehicle navigation system.
  • the historical traffic information data e.g. start times and addresses
  • the vehicle navigation system automatically acquires traffic information from the remote location when the vehicle navigation system is located near an address or a start time occurs.
  • the calculation of a travel route is based on the traffic information and is preferably performed before the user enters the vehicle with the vehicle navigation system.
  • FIG. 1 a is a schematic diagram of a first embodiment of a system pursuant to aspects of the invention
  • FIG. 1 b is a schematic diagram of a broadcast communication network pursuant to aspects of the invention.
  • FIG. 1 c is a schematic diagram of a navigation device in communication with a mobile unit pursuant to aspects of the invention
  • FIG. 2 is a schematic diagram of an alternate embodiment of a system pursuant to aspects of the invention.
  • FIG. 3 a is a flow diagram of an embodiment for ensuring quality and reliability of traffic information provided to a vehicle pursuant to aspects of the invention
  • FIG. 3 b is a flow diagram of an alternate embodiment for ensuring quality and reliability of traffic information provided to a vehicle pursuant to aspects of the invention
  • FIG. 4 is a schematic diagram of an embodiment of a system for coordinating traffic signals pursuant to aspects of the invention
  • FIG. 5 is a flow diagram of an embodiment for coordinating traffic signals pursuant to aspects of the invention.
  • FIG. 6 is a schematic diagram of an embodiment of a system for providing automated and personalized traffic information pursuant to aspects of the invention.
  • FIG. 7 is a schematic diagram of an alternate embodiment of a system for providing automated and personalized traffic information pursuant to aspects of the invention.
  • FIG. 8 is a schematic diagram of an embodiment for filtering traffic information pursuant to aspects of the invention.
  • FIG. 9 a is a flow diagram of an embodiment for filtering traffic information pursuant to aspects of the invention.
  • FIG. 9 b is a flow diagram of an alternate embodiment for filtering traffic information pursuant to aspects of the invention.
  • FIG. 9 c is a flow diagram of an another embodiment for filtering traffic information pursuant to aspects of the invention.
  • FIG. 10 is a flow diagram of an embodiment for providing weight factors and threshold prioritizing pursuant to aspects of the invention.
  • FIG. 11 is a schematic diagram of an embodiment of a system that initiates a recalculation of a route when there is an upcoming turn pursuant to aspects of the invention
  • FIG. 12 is another schematic diagram of an embodiment of a system that initiates a recalculation of a route when there is a upcoming turn pursuant to aspects of the invention
  • FIG. 13 is a schematic diagram of an embodiment of a system that performs a route calculation using traffic information broadcast from a remote location and/or a traffic supplier pursuant to aspects of the invention
  • FIG. 14 is another schematic diagram of an embodiment of a system that performs a route calculation using traffic information broadcast from a remote location and/or a traffic supplier pursuant to aspects of the invention
  • FIG. 15 is a flow diagram of an embodiment that uses every traffic information update to act as a trigger for route calculation and recalculation pursuant to aspects of the invention
  • FIG. 16 is a flow diagram of an embodiment that uses every traffic information update to act as a trigger for route calculation but does not recalculate to anticipate user error pursuant to aspects of the invention
  • FIG. 17 is a flow diagram of an embodiment that uses streaming traffic information and an internal clock to trigger route calculation and/or recalculation pursuant to aspects of the invention
  • FIG. 18 is a flow diagram of an embodiment that waits for a recalculation to finish and then calculates a new alternate route with traffic information pursuant to aspects of the invention
  • FIG. 19 is a flow diagram of an embodiment that store the traffic information when recalculation is taking place pursuant to aspects of the invention.
  • FIGS. 20 and 20 a illustrate an embodiment that stream traffic information and varies traffic information update triggers for route calculation and/or recalculation pursuant to aspects of the invention
  • FIG. 21 illustrates an embodiment of a display system pursuant to aspects of the invention
  • FIGS. 22 a and 22 b illustrate a case where only traffic incident information is available and addressed by an embodiment of the invention
  • FIG. 23 is a flow diagram of an embodiment for combining actual and historical traffic information pursuant to aspects of the invention.
  • FIG. 24 is a flow diagram of an embodiment for providing a time stamp to traffic incident information and for using the time stamp to determine a route for calculation pursuant to aspects of the invention
  • FIG. 25 is a schematic diagram of an embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention.
  • FIG. 26 is a flow diagram of an embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention.
  • FIG. 27 is a schematic diagram of an alternative embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention.
  • FIG. 28 a is a flow diagram of an embodiment for manual filtering traffic information without the need of a position determination unit pursuant to aspects of the invention
  • FIG. 28 b is a flow diagram of an embodiment for automatic filtering traffic information without the need of a position determination unit pursuant to aspects of the invention
  • FIG. 29 is a schematic diagram of an another embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention.
  • FIG. 30 is a flow diagram of an embodiment for filtering traffic information using time zones pursuant to aspects of the invention.
  • FIGS. 31 a and 31 b illustrate an embodiment of a display system having traffic flow information and traffic incident information pursuant to aspects of the invention
  • FIGS. 32 a and 32 b illustrate an alternative embodiment of a display system having traffic flow information and traffic incident information pursuant to aspects of the invention
  • FIG. 33 illustrates another embodiment of a display system having traffic flow information and traffic incident information pursuant to aspects of the invention
  • FIG. 34 illustrates yet another embodiment of a display system pursuant to aspects of the invention.
  • FIG. 35 is a flow diagram of an embodiment for providing a pop-up window to convey certain traffic information details pursuant to aspects of the invention.
  • FIGS. 36 a and 36 b illustrate an embodiment of a display system that displays only traffic information indicating traffic problems pursuant to aspects of the invention
  • FIG. 37 is a flow diagram of an embodiment for showing a free-flow icon when no data is received on a particular traffic information sensor pursuant to aspects of the invention
  • FIG. 38 is a schematic diagram of an embodiment for adding a header pursuant to aspects of the invention.
  • FIG. 39 is a flow diagram of an embodiment for adding a header and utilizing the header pursuant to aspects of the invention.
  • FIGS. 40 and 42 are schematic diagrams of an embodiment for using triangulation of a plurality of repeaters to determine a position and for using the determined position to filter traffic information pursuant to aspects of the invention
  • FIGS. 41 and 43 are flow diagrams of an embodiment for using triangulation to determine a position and for using the determined position to filter traffic information pursuant to aspects of the invention
  • FIG. 44 is a flow diagram of an embodiment for allowing a user to scroll to a needed traffic information pursuant to aspects of the invention.
  • FIG. 45 is a flow diagram of an embodiment for filtering traffic information based on a plurality of parameters entered by a user pursuant to aspects of the invention.
  • FIG. 46 is a schematic diagram of an embodiment for reducing the broadcast of redundant and/or static traffic information pursuant to aspects of the invention.
  • FIG. 47 is a flow diagram of an embodiment that provide an option for a user to avoid a traffic incident and/or congestion pursuant to aspects of the invention.
  • FIGS. 48 a and 48 b illustrate an embodiment for avoiding a zigzag route pursuant to aspects of the invention
  • FIG. 49 is a flow diagram of an embodiment that reduces zigzagging pursuant to aspects of the invention.
  • FIGS. 50 , 51 , 52 , 53 a , and 53 b illustrate embodiments for calculating and utilizing a distance threshold that provides a distance value at which it is likely that a traffic problem location that exists past this distance value from a current location of a vehicle will expire before the vehicle can reach the problem location pursuant to aspects of the inventions.
  • the present invention is directed to a system and method for facilitating the exchange of traffic information between a remote location and a vehicle.
  • the present invention is directed to a system and method that includes a vehicle that exchanges traffic information with the remote location by way of one or more communication networks in a manner that conserves bandwidth while providing sufficient traffic information to the vehicle.
  • FIG. 1 a shows a first embodiment of a system for facilitating the exchange of information between a remote location 10 and a vehicle 12 pursuant to aspects of the invention.
  • the vehicle 12 includes a navigation device 14 .
  • the navigation device 14 may include an output unit 21 , a receiver unit 22 , an input unit 23 , a position detection unit 25 , a navigation memory unit 30 , a navigation processor unit 26 , and an RF transceiver unit 52 that are all in electrical communication with one another.
  • the navigation memory unit 30 includes at least a portion of a user profile and, in some embodiments, includes the entire user profile.
  • the navigation memory unit 30 includes a road map database portion and, in some embodiments, includes a disk reading unit for reading road map information not built into the navigation device 14 .
  • the user profile and/or the road map database stored in the memory 30 may be updated in the vehicle by way of the input unit 23 , which includes at least one of a keyboard, a touch sensitive display, and a microphone.
  • the user profile and/or the road map database may also be updated by way of information received through the receiver unit 22 and/or the RF transceiver unit 52 .
  • the receiver unit 22 receives information from the remote location 10 and, in one embodiment, is in communication with the remote location by way of a one-to-many communication system.
  • One-to-many communication systems include systems that can send information from one source to a plurality of receivers, such as a broadcast network 31 .
  • Broadcast networks include television, radio, and satellite networks.
  • the broadcast network 31 is the XM Radio satellite network 40 , which comprises broadcast towers 42 , satellite servers (not shown), and satellites 43 .
  • the broadcast towers 42 transmit information to the satellites 43 , which bounce the information back down to the receiver unit 22 of the navigation device 14 .
  • the information received by the receiver 22 may be processed by the navigation processor unit 26 .
  • the processed information may then be displayed by way of the output unit 21 , which includes at least one of a display and a speaker.
  • the receiver unit 22 , the navigation processor unit 26 and the output unit 21 are provided access to only subsets of the received broadcast information based on user preferences and/or traffic information demands.
  • the user preferences, as well as user identity information and traffic-related information, can be part of the user profile.
  • the position detection unit 25 may include a GPS receiver that communicates with a plurality of GPS satellites (separate from the XM satellites) to determine the position of the vehicle 12 .
  • the GPS receiver searches for and collects GPS information (or signals) broadcast from four or more GPS satellites that are in view of the GPS receiver.
  • the GPS receiver uses the time interval between the broadcast time and reception time of each broadcast signal, calculates the distance between the GPS receiver and each of the four or more GPS satellites. These distance measurements, along with the position and time information received in the broadcast signals, allow the GPS receiver to calculate the geographic position of the vehicle 12 .
  • the mobile unit 18 is used to receive and transmit information from and to the remote location 10 ; and, in an alternate embodiment shown in FIG. 2 , an RF transceiver 252 is used to receive and transmit information from and to the remote location 210 .
  • the mobile unit 18 may be a wireless phone or any other device that communicates with other devices by way of the wireless communication network 46 .
  • the mobile unit 100 of the present invention includes a wireless receiver 32 , a wireless transmitter 34 , a mobile unit processor 40 , and an RF transceiver unit 54 that are in communication with one another.
  • the mobile unit 18 is in two-way communication with the remote location 10 by way of the receiver 32 , the transmitter 34 , and the wireless communication network 46 , which comprises numerous base stations.
  • information is transmitted from or to the vehicle or remote location over a high bandwidth GPRS/1XRTT channel of the wireless communication network 46 . If the high bandwidth channel is unavailable, a low bandwidth DTMF channel is used.
  • the receiver 32 receives information from the remote location 10 , and the transmitter 34 transmits information to the remote location 10 . In other embodiments described below in greater detail, the transmitter 34 also transmits information to suppliers of traffic or other information 48 , 50 .
  • the information received from and transmitted to the remote location 10 by way of the mobile unit 18 is accessed by the user through the navigation device 14 , which is in communication with the mobile unit 18 .
  • the mobile unit 18 may be embedded in the vehicle 12 and be in communication with the navigation device 14 by, for example, a cable (not shown).
  • the navigation device 14 and mobile unit 18 are in communication with one another by way of RF transceiver units 54 and 52 .
  • Both the navigation device 14 and the mobile unit 18 include RF transceiver units 52 , 54 , which, in one embodiment, comply with the Bluetooth® wireless data communication format.
  • the RF transceiver units 52 , 54 allow the navigation device 14 and the mobile unit 18 to communicate with one another.
  • the receiver 32 and transmitter 14 of the mobile unit 18 and the receiver unit 20 of the navigation device 14 allow the navigation device 14 and mobile unit 18 to communicate with one another.
  • the navigation device 214 transmits and receives information to and from the remote location 210 by way of the RF transceiver 252 , access points 270 , 272 , and gateways 274 , 276 that are in communication with the network 262 .
  • the RF transceiver 252 and the access points 270 , 272 are compliant with the IEEE 802.11 specification, and such transceivers and access points include Wi-Fi®-certified equipment.
  • the access points 270 , 272 are typically in communication with the gateways 274 , 276 by way of a cable, and the gateways are in communication with the remote location 210 by way of the network 262 .
  • the access points 270 , 272 are in communication with the RF transceiver 252 and have a limited range over which they can communicate with the RF transceiver 252 .
  • the RF transceiver 252 effectively exchanges information with the access points 270 , 272 and, thus, the remote location 210 .
  • the navigation device 214 also includes input and output units, a receiver unit, a memory unit, and a processor unit, none of which are shown.
  • the components of the alternate navigation device embodiment 214 have the same functionality as do the components of the navigation device 14 of the first embodiment.
  • the remote location 10 , 210 includes a remote server 44 , 244 , a remote transmitter 56 , 256 and receiver 58 , 258 , and a remote memory 60 , 260 that are in communication with one another.
  • the remote transmitter and receiver 56 , 58 communicate with the navigation device 14 and mobile unit 100 by way of the broadcast 31 and wireless 46 communication networks, respectively.
  • the remote transmitter and receiver 256 , 258 communicate with the navigation device 214 , including the RF transceiver 252 , by way of the broadcast communication network 231 and a network 262 .
  • the remote location 10 , 210 is also in communication with suppliers of traffic and/or other information 48 , 50 , 248 , 250 such as government traffic information suppliers, private traffic information suppliers, and users of other vehicles, by way of the network 62 , 262 .
  • the network 62 , 262 is typically a wide area network (WAN) such as the Internet.
  • WAN wide area network
  • some of the information suppliers 48 , 50 , 248 , 250 may be in communication with the remote location 10 , 210 by way of a local area network (LAN), while other information providers 48 , 50 , 248 , 250 such as the vehicle users, are in communication with the remote location by way of the Internet.
  • the RF transceiver 252 is in communication with the remote location 210 and/or the information providers 248 , 250 by way of a network 262 that is an LAN.
  • the LAN 262 is compliant with the IEEE 802.3 specification or is an Ethernet network.
  • the information suppliers 48 , 50 , 248 , 250 may transmit updated user profiles and traffic-related information to the remote location 10 , 210 .
  • a plurality of user profiles are in a user profile database, which, along with traffic-related information, is stored in the remote memory 60 , 260 .
  • the updated user profiles and new traffic-related information are transmitted from the remote location 10 , 210 to the navigation device 14 , 214 by way of the broadcast network 31 , 231 .
  • the new traffic-related information and updated user profiles may be transmitted to the vehicles 12 , 212 by way of the wireless network 46 or the network 262 .
  • the user profile stored in the memory 30 of the navigation device 14 is updated, and the vehicle-related information is made accessible to the user by way of the output unit 26 of the navigation device 14 .
  • the information providers may communicate directly with the mobile unit 18 or RF transceiver 252 by way of the wireless communication network 46 or the network 262 .
  • FIG. 3 a shows an embodiment for ensuring quality and reliability of traffic information provided to the navigation device 14 , 214 pursuant to aspects of the invention.
  • the embodiment uses the navigation device 14 , 214 (including its position detection unit 24 ) on the vehicle 12 , 212 to determine vehicle location and to detect sensor error or errors on a road segment/lane (e.g., speed sensors on a freeway lane/segment).
  • the embodiment uses the wireless network 46 or the network 262 to communicate the position determination and the error detection data from the navigation device 14 , 214 to the remote location 10 , 610 and/or traffic information suppliers 48 , 248 in an effort to refine the traffic information provided.
  • the navigation device 14 , 214 uses its position detection unit 24 to determine vehicle location and speed data.
  • the vehicle's location and speed data is then communicated over the wireless communication network 46 or the network 262 to the remote location 10 , 210 .
  • the remote location 14 , 214 via its remote server or servers 44 , 244 , processes and passes the vehicle location and speed data to traffic information supplier or suppliers 48 , 248 .
  • the data from the remote location is transmitted over the network 62 or the network 262 to the traffic information supplier or suppliers 48 , 248 .
  • the data is processed at the remote location 14 , 214 by filtering the information based on predetermined criteria and translating the information into a format acceptable to the traffic information supplier or suppliers 48 , 248 .
  • the transmitted vehicle location and vehicle speed data is processed at a database of the traffic information supplier or suppliers 48 , 248 .
  • the vehicle's location and speed data (i.e., the back channel data) is compared with sensor data from a speed sensor on a lane of a freeway to determine the difference between the vehicle speed data and the sensor speed data.
  • the location of the speed sensor corresponds to the location of the vehicle where the vehicle's location and speed data was detected.
  • a quantized differential action scheme based on a range of the speed differences between the vehicle speed data and the sensor speed data is used to determine action items.
  • the refined traffic information data (e.g., with corrected speed sensor data) is broadcast to a plurality of vehicles that may include vehicle 12 , 212 , by way of the broadcast network 31 , 231 .
  • FIG. 3 b shows an alternate embodiment that uses a quantized percentage differential method.
  • a percentage difference between the vehicle speed data and the speed sensor data is used to select an action item from a plurality of action items rather than using the actual differences between the vehicle speed data and the speed sensor data. That is, at step 330 , the vehicle's location and speed data (i.e., the back channel data) is compared with sensor data from a speed sensor on a lane of a freeway to determine a percentage (%) difference in speed of the vehicle speed data and the sensor speed data.
  • a percentage quantized differential action scheme based on a range of the percentages of difference of the sensor speed data to the back channel data is used to select an action from a plurality of action items to be taken.
  • FIG. 3 b shows that a difference of less than 20% of the sensor speed data to the back channel data is acceptable, a 21% to 30% difference triggers an automatic alert to check the speed sensor, a 31% to 40% difference triggers an automatic alert to monitor the speed of the sensor, a 41% to 50% difference triggers an automatic replacement alert, and a greater than 50% difference triggers the automatic replacement or maintenance of the sensor.
  • the embodiment also includes the transmission and processing steps 300 , 305 , 310 , and 325 described above for FIG. 3 a .
  • the steps of FIG. 3 b use the same devices, units, and/or components as the embodiment shown in FIG. 3 a .
  • FIG. 4 shows an embodiment for coordinating traffic signals pursuant to aspects of the invention.
  • the embodiment uses the navigation device's position determination unit (e.g., the GPS) and back channel capabilities (e.g., the wireless communication network 46 or the network 262 ).
  • the embodiment includes a navigation device (e.g., a device 14 , 214 shown in FIGS. 1 a , 2 ) having a position detection unit (e.g., unit 24 shown in FIG. 1 c ).
  • the navigation device is located on a vehicle 412 and is used to determine the location and speed of the vehicle 412 and to coordinate traffic signals 445 (e.g., freeway off-ramp signals).
  • traffic signals 445 e.g., freeway off-ramp signals
  • the embodiment uses back channel communication 446 to communicate the speed and location of the vehicle 412 detected from the navigation device (e.g., 14 , 214 ) to a remote location 410 .
  • the remote location 410 then transmits the speed and location of the vehicle to a traffic information supplier 448 that passes this information to a signal control center 450 (e.g., a city traffic center).
  • the signal control center then adjusts, coordinates, and manages the traffic signals 445 based on the information from the traffic information supplier 448 .
  • the embodiment provides a method for coordinating traffic signals, as diagrammed in FIG. 5 .
  • the method receives probe and flow sensor data (e.g., data on the position of the vehicle, the speed of the vehicle, and the average speed of vehicles on a lane of a road).
  • the method displays the flow-sensor data.
  • the difference in speed between various lanes 460 of a roadway (e.g., a freeway) and the location of the vehicle 412 are determined.
  • the signal length or signal timing for the traffic signals 455 is increased pursuant to step 520 and the chart shown below.
  • Distance from off-ramp Increase signal length >0.25 miles 10% >0.5 miles 15% >0.75 miles 20% >1.0 miles 30% >1.25 miles 40% >1.5 miles 50%
  • FIG. 6 shows an embodiment for providing automated and personalized traffic information so that a user of a navigation device 614 located on a vehicle 612 does not have to wait for traffic information.
  • the embodiment allows the user of the navigation device 614 to preset its commute preferences (e.g., 7 a.m. home to work; 5 p.m. work to home) so that traffic information from the traffic information supplier 648 and/or remote location 610 can be pre-provided or pre-broadcast to the navigation device 614 via a broadcast network 631 . More specifically, rather than require the user to input its destination point in the navigation device 614 , the present embodiment allows the user to store an address/destination in a memory unit (e.g., unit 30 in FIG. 1 c ) of the navigation device 614 .
  • a memory unit e.g., unit 30 in FIG. 1 c
  • the present embodiment allows the user to set its commute preferences in an owner link 615 (e.g., a database) located in the remote location 610 so that traffic information can be pre-broadcast to the navigation device 614 . That is, the present embodiment allows a user to (1) set an address/destination in a memory unit (e.g., unit 30 in FIG. 1 c ) of the navigation device 614 and (2) set its commute preferences in an owner link 615 (e.g., a database) via the remote location 610 so that traffic information can be pre-broadcast to the navigation device 614 .
  • an owner link 615 e.g., a database
  • FIG. 7 shows an alternate embodiment that automatically stores historical data of the user to determine when traffic information should be pre-provided.
  • the embodiment uses back channel communication 746 to store start times and addresses on a remote location 710 such that no address input is required.
  • This embodiment automates an owner link function (e.g., 615 on FIG. 6 ) for traffic information by storing the pertinent commute information to memory with an internal clock (e.g., a GPS internal clock) of the navigation device 714 to determine when to gather traffic information data and begin route calculations.
  • an owner link function e.g., 615 on FIG. 6
  • an internal clock e.g., a GPS internal clock
  • the gathering of the traffic information data and the calculation of routes are performed before the user enters the vehicle 712 with the navigation device 714 . It should be appreciated by those skilled in the art that the above method further increases the convenience for providing automated and personalized traffic reports as compared to the method and system described with respect to FIG. 6 .
  • FIG. 8 shows a method for filtering traffic information.
  • Traffic information broadcast from a traffic information supplier to a fifteen (15) mile radius 800 from a user's location is filtered to expedite traffic calculation.
  • This filtering embodiment saves on processing hardware and/or a bandwidth requirement of a navigation device and/or the traffic supplier. More specifically, the traffic information supplier broadcasts nationwide traffic information into twenty (20) smaller metropolitan area-wide information (or metros).
  • the present filtering embodiment uses position information (e.g., GPS location information) at the start-up of the navigation device or from the memory of the navigation device if the navigation device is unable to acquire position information not only to filter the needed metro from the nationwide traffic information but also to filter down the needed metro to specific user applicable area. That is, in the present embodiment, each traffic communication packet between the navigation device and its traffic supplier includes information on metro location and filtering information for further filtering the traffic information to a fifteen (15) mile radius from a user's location.
  • position information e.g., GPS location information
  • the embodiment provides a method for real time filtering of traffic updates, as diagrammed in FIG. 9 a .
  • the method determines the location of the navigation device (e.g., a GPS location).
  • the method receives traffic information (e.g., U.S. traffic information).
  • the method determines whether the traffic information is within a predetermined radius of the navigation device or fifteen (15) mile radius of the navigation device. If the traffic information is within the predetermined radius, the navigation device then calculates a route for the user of the navigation device using the filtered traffic information at step 915 . However, if the traffic information is not within the predetermined radius, then the traffic information is discarded at step 920 .
  • FIG. 9 b shows an alternate method that uses GPS location information to automatically filter traffic information based on a location of the navigation device.
  • the method uses decreasing radius(es) to display/calculate information in the specific metro.
  • a location of a navigation device e.g., a GPS location
  • the method receives traffic information for a specific metro.
  • the method determines whether the traffic information is approaching a memory capacity level (e.g., a 90% memory capacity level) of the navigation device. If the traffic information is approaching the memory capacity, the method then selects a step-to-step criteria for filtering the traffic information pursuant to steps 935 , 940 , and 945 and the chart shown below. Steps 935 , 940 , and 945 are repeated until the memory capacity of the navigation device is below the predetermined capacity level. The method then move to step 950 to calculate a route using the filtered traffic information. The calculated result is displayed at step 955 .
  • a memory capacity level e.g., a 90% memory capacity level
  • FIG. 9 c shows another method for filtering traffic information.
  • This method monitors memory capacity to maximize an available metro traffic information and to increase the traffic information available for calculation by a navigation device.
  • the method determines a location of a navigation device (e.g., a GPS location).
  • the method receives traffic information for a specific metro.
  • the method determines whether the traffic information is approaching a memory capacity level (e.g., a 90% memory capacity level) of the navigation device.
  • a memory capacity level e.g., a 90% memory capacity level
  • the method selects a step-to-step criteria for reverse-filtering (or increasing) the available traffic information pursuant to steps 960 , 965 , 970 , 975 , and 980 and the chart shown below. Steps 960 , 965 , 970 , 975 , and 980 are repeated until the memory capacity of the navigation device is approaching the predetermined capacity level. The method then calculates a route using the reverse-filtered traffic information at step 985 and displays the calculated route at step 990 .
  • FIG. 10 shows a method for providing weight factors and threshold prioritization when a broadcast limit (e.g., an XM bandwidth limit) is close to being reached.
  • the method is utilized with a broadcast network (e.g., an XM broadcast network) that broadcasts traffic information initially, for example, to twenty metropolitan areas (metros).
  • the method prioritizes traffic information and maintains maximum bandwidth availability by assigning weight factors to each reported incident and broadcasting the traffic information based on the assigned weight factors.
  • the assigning of the weight factors and the broadcasting of traffic information based on these factors would occur only when a certain preset broadcast threshold is met (e.g., 80% capacity of the network has been reached).
  • a central processor at a remote location e.g., 10 in FIG.
  • a network broadcast threshold e.g., 80% of the capacity of the broadcast network. If the broadcast threshold has been met, weight factors are assigned to each piece of the traffic information (e.g., traffic information packets) based on the subject matter of the traffic information pursuant to step 1015 and the chart shown below.
  • FIG. 11 shows an embodiment of a navigation device that initiates a recalculation of a route 1100 when there is a upcoming turn 1105 to anticipate a user of the navigation device missing the turn 1105 .
  • the navigation device makes an assumption that a vehicle's starting point 1214 is somewhere ahead of its actual starting point 1212 , not on the route 1200 , to anticipate a user of the navigation device missing a turn 1205 .
  • recalculation refers to all possible routes that the user may take when an error occurs (e.g., user should go left but goes right). Recalculation can also be referred to as pre-calculation or error anticipating calculation.
  • the recalculations can be made at variable times 1110 a 1110 b , 1110 c , 1110 d.
  • FIG. 13 shows an embodiment of a navigation device that performs a route calculation using traffic information broadcast from a remote location and/or a traffic information supplier.
  • the traffic information updates may be provided to the navigation device every one (1) minute or five (5) minutes, and the navigation device calculates a new route with every traffic information update for better route guidance. That is, referring now also to FIG. 14 , once traffic information has been completely refreshed or updated, a route calculation is triggered using a vehicle's current position 1412 as the starting point.
  • FIG. 15 shows an embodiment of a method that uses every traffic information update to act as a trigger for calculation and recalculation (i.e., anticipation of a user error).
  • a navigation device is set at a route guidance mode.
  • the navigation device determines whether to recalculate (i.e., pre-calculate) a new route. For example, the navigation device anticipates a user error as shown in FIG. 12 and determines that a new route (e.g., one based on an anticipated user error) should be calculated. If the navigation device recalculates the new route, the new route is displayed to a user of the navigation device at step 1510 , and the method moves to step 1515 .
  • a new route e.g., one based on an anticipated user error
  • step 1515 the navigation device determines whether a traffic information update has been provided to the navigation device. If the traffic information update has not been provided, the method moves to step 1500 . If the traffic information update has been provided, the navigation device calculates a new alternative route with the updated traffic information at step 1520 , and the method moves to step 1525 . At step 1525 , the method determines whether the alternative route is better (e.g., whether it has a shorter estimated travel time) than the route previously displayed to the user. If the alternative route is better, the navigation device displays the alternative route with the traffic information at step 1530 , and then moves to step 1500 .
  • the alternative route is better (e.g., whether it has a shorter estimated travel time) than the route previously displayed to the user. If the alternative route is better, the navigation device displays the alternative route with the traffic information at step 1530 , and then moves to step 1500 .
  • FIG. 16 shows an embodiment of a method that uses every traffic information update to act as a trigger for recalculation but does not recalculate to anticipate user error.
  • the embodiment is designed to reduce processing requirements at the navigation device. That is, at step 1600 , a navigation device is set at a route guidance mode, and the method moves immediately to step 1605 . At step 1605 , the navigation device determines whether a traffic information update has been provided to the navigation device. If the traffic information update has not been provided, the method moves to step 1600 .
  • the navigation device calculates a new alternative route with the updated traffic information at step 1610 , and the method moves to step 1615 .
  • the method determines whether the alternative route is better (e.g., whether it has a shorter estimated travel time) than the route previously displayed to the user. If the alternative route is better, the navigation device displays the alternative route with the traffic information at step 1620 , and then moves to step 1600 .
  • FIG. 17 shows an embodiment of a method that uses streaming (non-static or constantly changing) traffic information data and an internal processing clock to trigger route calculation at fixed and/or variable time intervals.
  • a navigation device is set at a route guidance mode.
  • the navigation device determines whether a predetermined amount of time (e.g., one minute) has elapsed using an internal processing clock (e.g., one located in a processor unit and/or a position determination unit of the navigation device). If the predetermined amount of time has not elapsed, the method moves to step 1700 .
  • a predetermined amount of time e.g., one minute
  • the navigation device calculates a new alternative route with the updated traffic information at step 1710 , and the method moves to step 1715 .
  • the method determines whether the alternative route is better (e.g., whether it has a shorter estimated travel time) than the route previously displayed to the user. If the alternative route is better, the navigation device displays the alternative route with the traffic information at step 1720 and then moves to step 1700 .
  • FIG. 18 shows an embodiment of a method that waits for a recalculation (i.e., an anticipation of a user error) to finish and then calculates a new alternate route with traffic information to determine the best route. That is, in the method shown in FIG. 18 , the recalculation (without traffic information) always takes precedence over the calculation with traffic information.
  • the steps shown in FIG. 18 are similar to those shown for FIG. 15 with the exception of additional step 1512 (located between the recalculation step 1510 and the traffic information update determination step 1515 ) that determines whether the recalculation (at step 1510 ) has been completed.
  • FIG. 19 shows an embodiment of a method that stores the traffic information data when a navigation device is recalculating a route and/or receiving a traffic information update. After the recalculation is completed, the method then resumes route calculation with the traffic information data. In addition, the method of FIG. 19 takes the previous traffic information calculated route and compares it with the new recalculated route (e.g., to determine the best route) when the method is between traffic information updates. That is, the method uses its old traffic information until new traffic information has been completely provided to the navigation device.
  • FIGS. 20 and 20 a show an embodiment of a method that streams traffic information data to provide users with the most up to date information.
  • the method varies the traffic information update triggers such that, at peak commute times, the recalculation (and calculation) triggers are increased and, at off peak commute times, the triggers are decreased.
  • the method of FIGS. 20 and 20 a minimizes the amount of time needed for updated traffic information to trigger a new calculation and provides updated traffic information based on a need use basis.
  • FIG. 20 shows a method for increasing and decreasing amounts and/or numbers of broadcast traffic information (e.g., via an XM network) based on commute times. More specifically, the method varies the broadcast of traffic information data based on commute times in each time zone, as shown in the following chart.
  • the above broadcast method can vary the broadcast time or rate in the specific metro as shown in the following chart.
  • variable broadcast rate allows a navigation device to receive quicker and more accurate broadcast traffic information. It should also be appreciated that the above-described mechanisms and processes for variable broadcasting are for exemplary purposes only, and the invention is not limited thereby.
  • FIG. 21 shows an embodiment of a display system that, when a user is rerouted by a navigation device, displays the new route's mileage 2100 and/or estimated time of arrival (ETA) 2105 and/or differences compared to the original route 2110 so that the user can make a direct comparison of the two routes. More specifically, the present display system allows the navigation device using broadcast traffic information to convey reasons why a new route using the traffic information has been calculated, selected, and/or displayed to the user (e.g., because it has a shorter travel time even if the actual distance may be longer). It should also be appreciated that the above-described display system is for exemplary purposes only and that the invention is not limited thereby.
  • FIG. 22 a shows a case where the traffic incident information is available but the flow information is not available.
  • a navigation device may determine that a route 2200 b is free flowing and direct the users to that route 2200 b instead of route 2200 a or route 2200 c .
  • route 2200 b is actually congested and route 2200 c with an reported incident may actually be better (i.e., a faster route).
  • the embodiment of the present invention provides a method for combining actual and historical traffic information to predict traffic congestion, as diagrammed in FIG. 23 .
  • a navigation device e.g., the navigation device 14 shown in FIG. 1 a
  • the navigation device determines if the route calculation has the required traffic flow information. If the required traffic flow information is available, the navigation device then calculates the best route and displays this route to a user of the navigation device at step 2330 . If the required traffic flow information is not available or cannot be provided, the navigation device contacts a database (e.g., a database in the remote location 10 shown in FIG.
  • a database e.g., a database in the remote location 10 shown in FIG.
  • the navigation device via its back-channel capabilities to receive historical traffic flow information at step 2310 .
  • the historical traffic flow information is then broadcast over a broadcast communication network (e.g., 31 in FIG. 1 a ) to the navigation device at step 2320 .
  • the navigation device then calculates the best route and displays this route to a user of the navigation device at step 2330 .
  • FIG. 24 shows an embodiment for providing a time stamp to traffic incident information and for using the time stamp to determine a route for calculation by a navigation device.
  • the embodiment can be applicable to a case when traffic flow information is not available, for example, due to sensor not available, damaged, malfunctioning, etc.
  • the embodiment can also be applicable to a case where traffic information that is provided does not report details of the extent of the congestion (e.g., from where to where is traffic congested) and/or a case where delays occur in providing incident details other than a location of an incident.
  • the embodiment provides a method that time stamps traffic incident information (having a location of the incident) and calculates a route by avoiding latest traffic incidents.
  • the method begins a route calculation process.
  • the route calculation process determines if traffic flow information or if traffic incident information with extent information (e.g., extent information from where to where is traffic congested) is available. If the determined traffic information is available, the method moves to step 2412 to perform a route calculation based on the traffic information. The calculated route is then displayed at step 2420 .
  • the method moves to 2410 to determine a time from traffic incident reported for each reported traffic incident.
  • the method at step 2415 , then performs a route calculation based on a route having the traffic incidents with the greatest total time (i.e., by avoiding the latest traffic incidents).
  • the calculated route (not having the latest traffic incidents) is then displayed at step 2420 .
  • the above method for providing a time stamp to traffic incident information and for using the time stamp to determine a route calculation alleviates problems that occur when only basic traffic incident information is available and provides a user of a navigation device (e.g. a device 14 , 214 shown in FIGS. 1 a , 2 ) with a way to automatically avoid traffic incidents based on a timer-based incident avoidance scheme.
  • a navigation device e.g. a device 14 , 214 shown in FIGS. 1 a , 2
  • the above-described mechanisms and process for route calculations based on an automatic timer based incident avoidance scheme are for exemplary purposes only and the invention is not limited thereby.
  • the traffic information supplier broadcasts nationwide traffic information into twenty (20) smaller metropolitan area-wide information (or metros) so that embodiments of the present invention can use position information (e.g., GPS location information) to filter the needed traffic information.
  • position information e.g., GPS location information
  • not all vehicles have GPS navigation systems, and/or receive GPS signals to identify their specific geographic location, and triangulation methodology may not be reliable and/or available due to repeater locations and/or building interference.
  • FIG. 25 an embodiment of the invention provides a reliable method for filtering traffic updates without the need of GPS navigation systems, GPS signals, repeaters, and/or repeater signals.
  • the embodiment provides a method for a user on a vehicle 2512 to specify its home address and applicable metro location via an owner link 2515 (e.g., a website of the owner link 2515 ) so that a specific traffic information can be received by the vehicle 2512 .
  • an owner link 2515 e.g., a website of the owner link 2515
  • FIG. 25 provides a method that allows a user to manually enter a metro location, as diagrammed in FIG. 26 .
  • a user registers (or specifies) its home address and applicable metro location via an owner link 2515 .
  • specific traffic information for various regions (or metros) are broadcasted.
  • the method determines whether a specific part of the broadcasted traffic information is in a user-specified metro. If the specific part of the broadcasted traffic information is in the user-specified metro, the method then displays (or calculates a route for the user via a navigation device) using the filtered traffic information at step 2620 . However, if the specific part of the traffic information is not in the user-specified metro, then the specific part of the information is discarded at step 2615 .
  • FIG. 27 shows an embodiment that allows a user to manually enter its metro location via a menu on a radio of a vehicle 2712 .
  • a method of FIG. 27 begins with a user inputting its applicable metro via a control on a radio at step 2800 .
  • the radio of the invention interfaces with broadcasted traffic information to filter the traffic information.
  • the method determines whether a specific part of the broadcasted traffic information is in a user-specified metro.
  • the method displays (or calculates a route for the user via a navigation device) using the filtered traffic information at step 2820 .
  • the specific part of the traffic information is not in the user-specified metro, then the specific part of the information is discarded at step 2815 .
  • FIG. 28 b shows another embodiment of a method for filtering traffic information.
  • This embodiment uses a user's FM radio station presets and/or radio station settings on a radio of a vehicle 2712 to automatically receive and/or filter applicable metro traffic information.
  • the user can also have the option of inputting its specific location manually via the radio.
  • the method of FIG. 28 b receives traffic information (e.g., U.S. traffic information) at step 2830 .
  • the method determines if a radio of the vehicle 2712 is powered on. If the radio is on, the method then checks the user's current radio station with a table or database 2845 to determine a location of the user's vehicle 2712 at step 2840 .
  • traffic information e.g., U.S. traffic information
  • the method checks the user's preset radio station with a table or database 2845 to determine a location of the user's vehicle 2712 at step 2850 .
  • the method determines whether it can use this automatically determined location to determine a metro. If the metro can not be determined from the automatically determined location, the method then requests the user to manually specify a metro at step 2860 . If the automatically determined location can determine the metro, then the method determines if traffic information for the automatically determined metro is available at step 2865 . If the traffic information for the automatically determined metro is not available, the method displays a “traffic information not applicable” indication to the user at step 2870 . If the traffic information for the automatically determined metro is available, the method then displays (or calculates a route for the user via a navigation device) using the automatically filtered traffic information at step 2875 .
  • FIG. 29 shows an embodiment for allowing a vehicle 2912 to automatically update via an internal clock of the vehicle 2912 to determine which time zone the vehicle 2912 is in and filters traffic information for the vehicle via the determined time zone.
  • the embodiment broadcasts traffic information based on time zones (e.g., Pacific Time Zone, Mountain Time Zone, Central Time Zone, and Eastern Time Zone) 2920 and the vehicle 2912 then filters 2935 out the non-matching time zone traffic information 2930 .
  • time zones e.g., Pacific Time Zone, Mountain Time Zone, Central Time Zone, and Eastern Time Zone
  • the embodiment of FIG. 29 provides a method that automatically filters traffic information based on time zones, as diagrammed in FIG. 30 .
  • the method determines an internal clock setting of a vehicle 2912 .
  • the method receives traffic information (e.g., U.S. traffic information).
  • the method determines whether a specific part of the received traffic information is in a user's or a vehicle's identified time zone. If the specific part of the received traffic information is in the vehicle's identified time zone, the method then displays (or calculates a route for the user via a navigation device) using the filtered traffic information at step 3015 . However, if the specific part of the traffic information is not in the vehicle's identified time zone, then the specific part of the information is discarded at step 3020 .
  • traffic information e.g., U.S. traffic information
  • the method determines whether a specific part of the received traffic information is in a user's or a vehicle's identified time zone. If the specific part of the received traffic information is in the vehicle'
  • FIG. 31 b shows an embodiment of a display system that displays traffic flow information 3100 and incident icons 3110 in the direction that a user is traveling.
  • the system only displays the roadways or freeways 3115 that the user would be driving on (i.e., if a vehicle is heading south, no northbound freeways will be displayed by the display system).
  • the above-described display systems allows the present display system to convey information to a user in a clear, concise, and understandable manner without inundating the user with redundant, useless, and/or superfluous information as compared with the embodiment shown in FIG. 31 a.
  • FIGS. 32 a and 32 b show an embodiment of a display system that allows a user to use a cursor 3230 of a navigation device so that the user can click on an actual roadway or freeway to get traffic flow information (and/or traffic incident information) 3200 on the roadway or freeway.
  • FIG. 33 shows an embodiment of a display system that, when a navigation device is providing a route guidance for a user, the display system of the navigation device provides a display icon 3310 on a road segment so the user can visually see an upcoming incident.
  • the display system can also provides a turn-by-turn guidance display as shown in the following chart.
  • FIG. 34 shows a window 3400 for displaying traffic information on a travel route 3405 .
  • the window 3400 is utilized by a navigation device (e.g., 14 in FIG. 1 a ) after the navigation device detects a traffic incident on a route ahead.
  • the navigation device displays the traffic incident details in the window 3400 .
  • the window 3400 appears or pops up on an output unit (e.g., 21 in FIG. 1 a ) of the navigation device that is displaying a map 3410 of the route ahead 3405 .
  • the window 3400 informs a user of the navigation device of the traffic condition ahead.
  • the pop-up window 3400 informs the user of a location of the incident, distance from a current location of the user, incident details, and/or possible effects on the route calculated by the navigation device.
  • the navigation device should also provide an option 3415 to the user for requesting a new route that avoids the traffic incident.
  • the navigation device should include an option 3420 to keep the current route, an option 3422 to allow the user to read the incident details, an option 3430 to go to the next traffic incident information, and/or an option 3425 to display all details received for an incident.
  • the embodiment of FIG. 34 provides a method, as diagrammed in FIG. 35 .
  • the method calculates a route to a destination.
  • the method receives traffic information (e.g., U.S. traffic information).
  • traffic information e.g., U.S. traffic information
  • the method determines whether the received traffic information is referring to roads on the calculated route to the destination. If the received traffic information is not referring to the roads on the calculated route, the method moves back to step 3505 . If the received traffic information is referring to the roads on the calculated route, the method displays or shows the traffic information to a user via a map 3410 of the route and a pop-up window 3400 at step 3515 .
  • the method determines whether to calculate a new route for the destination to avoid a traffic incident reported using the received traffic information. If the new route is to be calculated, the method moves to step 3500 to calculate the new route to the destination.
  • An embodiment of the invention reduces the bandwidth requirement for broadcasting traffic information by utilizing a method that does not broadcast free-flow traffic information.
  • a user of this embodiment only receives traffic information regarding known conditions affecting traffic or only sees traffic information when there is a traffic problem.
  • FIG. 36 b shows an embodiment of a display system that displays only traffic information indicating traffic problems and does not show free-flow traffic icons on the display system, as compared with the embodiment shown in FIG. 36 a.
  • FIG. 37 shows an alternate embodiment that uses a method that shows free-flow traffic icons by storing the locations of the flow sensors on another medium and cross-referencing with broadcast traffic information data. If no information is received regarding a particular sensor location, the method assumes free-flowing traffic and indicates that particular location with a free-flow icon. More specifically, at step 3700 , the method retrieves sensor location information for a sensor. At step 3705 , the method receives traffic information associated with the location of the sensor or traffic information from the senor. At step 3710 , the method determines whether the received traffic information has data indicating heavy traffic for the location.
  • the method displays a poor traffic icon at the location of the sensor at step 3715 .
  • the method determines whether the received traffic information has data indicating moderate traffic for the location. If the traffic information has data indicating moderate traffic, the method displays a moderate traffic icon at the location of the sensor at step 3725 .
  • the method determines whether the received traffic information has data indicating that the sensor is broken. If the traffic information has data indicating that the sensor is broken, the method displays a sensor inoperable icon at the location of the sensor at step 3735 .
  • the method determines whether the received traffic information has no data at all. If the traffic information has no data, the method displays a free-flow traffic icon at the location of the sensor at step 3745 .
  • FIG. 38 shows an embodiment that adds a header 3800 to each traffic information report pursuant to aspects of the invention.
  • the header 3800 allows the embodiment to skip or filter broadcast reports that the embodiment has already processed.
  • the embodiment of FIG. 38 provides a method for adding a header to allow a navigation device to read only updated traffic information in order to reduce a processing requirement of the navigation device, as diagrammed in FIG. 39 .
  • a navigation device e.g., the navigation device 14 shown in FIG. 1 a
  • the navigation device determines if the header of the received traffic report is the same as a previously received header. If the header is the same as the previously received header, the traffic report is discarded at step 3910 . If the header is not the same as the previously received header, the navigation device processes the received traffic report at step 3915 . It should be appreciated that the above-described mechanisms and process for adding a header to a traffic report are for exemplary purposes only and that the invention is not limited thereby.
  • FIG. 40 shows an embodiment of a navigation device that uses triangulation of repeaters 4000 a , 4000 b to determine a specific location or position 4010 of the navigation device.
  • the navigation device does not need a GPS navigation system to determine location. More specifically, the embodiment of FIG.
  • the method determines whether there is a reception from repeaters 4000 a , 4000 a . In addition, the method may determine whether there is a reception from a satellite 4020 . If there is (or are) the necessary reception(s), the method receives a signal or signals from each of the repeaters 4000 a , 4000 b and/or the satellite 4020 at step 4110 . The method then calculates a current position 4010 (e.g., a current position of a vehicle) by triangulation at step 4115 and determines the current position 4010 at step 4120 .
  • a current position 4010 e.g., a current position of a vehicle
  • the method can then filter traffic information as described in the embodiment shown in FIG. 42 . That is, the embodiment may filter the traffic information down to first radius 4200 a and/or a second radius 4200 b of a determined current position 4010 .
  • the first radius 4200 a and/or second radius 4200 b can be a five, ten, twenty, and/or thirty mile radius of the current position 4010 .
  • the embodiment of FIG. 42 provides a method for filtering of traffic information, as diagrammed in FIG. 43 .
  • the method determines whether there is a specific radius 4200 a , 4200 b for traffic filtering.
  • the method uses the traffic information only inside the parameter of the specific radius 4200 a , 4200 b to filter traffic information at steps 4310 and 4320 . If there is no specific radius, the method sets a radius 4200 a , 4200 b to filter at step 4305 and then moves to steps 4310 and 4320 .
  • FIG. 44 shows an embodiment of a method that requires a user to scroll to the needed traffic information in order to reduce display distractions.
  • a navigation device e.g., a navigation device having no GPS
  • receives filtered traffic information at step 4400 .
  • a user of the navigation device scrolls down a traffic display of the navigation device to select an applicable area (e.g., an applicable freeway).
  • the user selects or picks the applicable area (e.g., the applicable freeway).
  • the user pushes a detail button (e.g., 3425 shown in FIG. 34 ) on the navigation device and the navigation device list all applicable details of the applicable area at step 4430 .
  • a detail button e.g., 3425 shown in FIG. 34
  • an embodiment of the invention uses four parameters to define specific traffic information for a user in a vehicle.
  • the four parameters are a user's state, metro, county, and city.
  • FIG. 45 shows a method of the present embodiment that determines and filters traffic information for the user based on the four parameters.
  • the navigation device calculates approximate position from the delay of the multiple source broadcast signal(s) (e.g., via repeaters 4000 b , 4000 c in FIG. 40 ).
  • the navigation device displays (or filters) traffic information of the determined current position (e.g., 4010 in FIGS. 40 , 42 ) of the vehicle at step 4530 .
  • each broadcasted traffic information of an embodiment may include a header written such that it allows the navigation device to extract information associated with the four parameters. It should be appreciated the addition of the header allows the navigation device to filter out traffic information having headers (e.g., with parameters) not specified by the user. Moreover, if the location information is successfully provided to the user, an embodiment of the invention reduces location header information until the user specifies other parameters so that the provision of redundant header information can be reduced.
  • FIG. 46 shows an embodiment of a broadcast methodology that reduces the broadcasting of redundant traffic information.
  • a navigation device of the embodiment includes a static map 4600 of a metro or a city.
  • a traffic supplier (and/or a remote location) of the embodiment only broadcasts traffic information data 4620 having traffic speed graphic data and a map number.
  • the embodiment does not have to broadcast the static map 4600 .
  • the navigation device includes a filter that displays detailed traffic flow data 4630 around a current position 4610 (e.g., determined via embodiments of FIGS. 40 and 42 ) on the map 4600 and displays less traffic flow data far from the current position 4600 .
  • the current position can be determined by a GPS navigation system.
  • the increasing traffic-jam portion of the traffic information should have top priority for display in the embodiment and the reducing traffic-jam portion of the traffic information should disappear from the display of the navigation device faster than other traffic jam information in the embodiment. It should be appreciated that the embodiment of FIG. 46 allows a driver to focus on the important information and reduces the amount of driver distractions.
  • a user may travel on a route and receive traffic information about a traffic incident and/or a traffic congestion ahead of the route. If the user is unfamiliar with the area of the route, a user may not know how to avoid the traffic incident and/or congestion.
  • FIG. 47 shows an embodiment of a method that provides an option for a user of a navigation device (e.g., 14 in FIG. 1 a ) to request a calculation of a new route that will avoid the traffic incident and/or the congestion.
  • the method calculates a route to a destination.
  • the method receives traffic information (e.g., U.S. traffic information).
  • the method displays or shows to a user the traffic information on the current calculated route to the destination.
  • the method determines whether to calculate a new route (or reroute) for the user so that the user can avoid the traffic shown by the traffic information. If the new route is to be calculated, the method calculates the new route at step 4720 . If the new route is not to be calculated, the method moves to step 4725 and keeps the current calculated route.
  • an embodiment of a navigation device of the invention calculates a new route (or recalculate a new route) that avoids the traffic incident and/or the congestion after the user goes off-route. It should be appreciated that this embodiment increases the convenience of the user by providing a recalculation function (e.g., anticipating a user mistake) based on traffic information.
  • an embodiment of the invention provides a method to limit the reroute onto an existing route to avoid zigzagging. More specifically, FIG. 48 b shows an embodiment of the invention that considers factors, such as a vehicle's position, speed, heading, destination, incident severity, time of reported traffic information, and/or estimated time for a traffic to clear, to calculate an optimized route 4810 .
  • the embodiment pursuant to aspects of the invention limits the new optimized route 4810 to no more than two reroutes back to an existing route 4800 within a predetermined distance. This embodiment reduces zigzigging effect of recalculating and returning to the existing route as compared with the embodiment shown in FIG. 48 a.
  • FIG. 49 shows a method of the embodiment of FIG. 48 b that reduces a zigzagging effect.
  • a navigation device is set at a route guidance mode.
  • the navigation device calculate an existing route 4800 .
  • the navigation device receives new traffic information.
  • the navigation device determines whether to reroute a user of the navigation to a new route 4810 . If the navigation device calculates the new route 4810 with the new traffic information, the new route 4810 is compared with the existing route 4800 to determine whether the new route 4810 has been rerouted back to the existing route 4800 for more than two times at step 4920 .
  • the method moves back to 4925 and maintains the existing route 4800 for the user. If the route 4810 has not been rerouted more than twice back to the existing route 4800 , the navigation device displays the new alternative route calculated with the traffic information at step 4930 .
  • Embodiments of the invention use a routing algorithm having a cost function that takes into account road speed, distance, road class, and/or other factors to calculate the cost of taking a certain route (or road) to a destination.
  • Traffic information wherever available can also be used by the routing algorithm to calculate the cost of a road link when finding the best route.
  • An easy method for a routing algorithm to calculate a good route using traffic information is to translate traffic information into an appropriate speed and then substitute this speed into the cost function.
  • some traffic information is already transmitted with a speed value that can be directly substituted into the cost function.
  • it might not be a good idea to directly substitute the speed into the cost function depending on the location of the traffic information and the lifetime of a specific piece of traffic information, it might not be a good idea to directly substitute the speed into the cost function. For example, there may a fatal accident reported close to San Francisco that has reduced the speed of a major road in San Francisco down to zero (0) mph and at the point of leaving Los Angeles to San Francisco, it usually does not make sense to substitute that speed (i.e., 0 mph) in San Francisco into the cost function to cause the routing algorithm to avoid that road in San Francisco because by the time that the accident location is reached it is very likely that the incident will be cleared. Accordingly, an embodiment of the invention modulates the speed calculated from traffic information to take into account the location of traffic information and/or its expected expiration time.
  • FIG. 50 shows an embodiment of the invention that provides a method for calculating a distance threshold (D T ).
  • the distance threshold (D T ) specifies a distance value at which it is likely that traffic information (i.e., a problem location) that exists past this distance value from a current location of a vehicle will expire before the vehicle can reach the traffic problem (i.e., the location reported by the traffic information).
  • an expiration time should be assigned to each piece of traffic information. This expiration time can be calculated based on historical data for similar types of incidents in similar types of road conditions.
  • the threshold distance (D T ) should be calculated such that it increases as the expiration time increases.
  • FIG. 51 shows an alternate embodiment that provides a method for determining the distance threshold (D T ) based on the density of the road network (e.g., the road network is more dense in city areas than in rural areas).
  • the distance threshold (D T ) is determined such that it decreases as the road network becomes more dense.
  • FIG. 52 shows another embodiment of the invention that provides a method for calculating a speed of a link for a route calculation using a distance threshold (D T ) from a current vehicle position to the location of the traffic information.
  • D T distance threshold
  • S T speed specified by the traffic information
  • S DB speed included in the onboard database
  • a further embodiment of the invention provides a method in which the speed of a link used by the routing algorithm is calculated by taking into account both the dynamic speed from real-time traffic information (S T ) and the static speed stored in a map database (S DB ).
  • Traffic information that is located far away from the vehicle's current position should have less effect on routing than information that is close to the vehicle.
  • One way to do this is to calculate the speed of the link as shown FIG. 52 a or 52 b . That is, as shown by the linear process of FIG. 52 a and the non-linear process of 52 b , for traffic information located very close to the current location, the speed from the live traffic information (S T ) is used for the link. However, as the location traffic information approaches some threshold distance (D T ), the speed of the link should be calculated such that it asymptotically approaches the value of the speed in the database (S DB ).

Abstract

Traffic information, including traffic flow information and traffic incident information, obtained through a traffic management system for providing and facilitating the exchange of traffic information between a remote location and a vehicle may be presented to a user on a user display in the vehicle. The traffic information may be presented to the user in several circumstances, either as cued by the user, or automatically presented by the traffic management system. The present invention discloses a vehicle navigation system for providing personalized traffic information to a user of the vehicle navigation system and methods for the same. The personalized traffic information is based at least in part on user preferences, either manually input by the user or automated by the vehicle navigation system.

Description

RELATED APPLICATION INFORMATION
This application claims priority to U.S. Provisional Patent Application Ser. No. 60/560,087, entitled “Method and System for Traffic Management Between a Vehicle and Remote Location,” which was filed with the U.S. Patent and Trademark Office on Apr. 6, 2004.
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to a system and method for providing traffic related information between a vehicle and a remote location. More specifically, the present invention relates to a vehicle navigation system that provides personalized traffic information to a user of the vehicle navigation system based at least in part on user preferences.
2. Description of Related Art
Navigation systems for determining a route from a start point to a destination point are well known in the art. In addition, navigation systems having capabilities for determining the geographic position of a reference point are also well known in the art (e.g., a Global Positioning System (GPS) or a self-contained system having distance and bearing sensors). As an example, a commonly used navigation system allows a user (or driver) of a vehicle to enter a destination place into the navigation system. The navigation system then looks up an appropriate route from an original point (using its geographic positioning capabilities) to the destination point in a road map database (e.g., the route may be a route having the shortest distance from the start point to the destination, one which would take the vehicle the least time, or some other route), and guides the user to the destination point along the searched route through a visual display or vocal guide.
In searching the appropriate route, some types of mobile navigation system use traffic information (e.g., position data on traffic jams; information on roads closed by accidents, construction, or maintenance; lane-regulated locations) delivered from a traffic information supplier in addition to using the road map database. Conventionally, however, known methods for providing and utilizing the above-described traffic information for navigation remain very inflexible, cumbersome, and inefficient. For example, one method uses a one-to-one communication system to individually send traffic information streams to a particular vehicle in an attempt to send vehicle specific data to the particular vehicle. A drawback with this method is that many vehicles require the same information. For example, several vehicles might require the same regional traffic information. This method, therefore, requires the transmittal of the same information several times to a plurality of vehicles, which results in a waste of precious bandwidth. As known in the art, wireless network bandwidth is extremely sensitive to network capacity.
In other methods, the same traffic information is transmitted to all vehicles. The drawback with these methods is that many vehicles are inundated with a large amount of unwanted traffic information. Users and/or navigation systems are required to sift through the redundant, superfluous, or otherwise unwanted information to pick out pertinent traffic information.
As a result, there remains a need for systems and methods that allow for the transmittal of vehicle-related traffic information from a remote location to a vehicle and that allow for the selective transmittal of vehicle related information from a vehicle to a remote location. Moreover, it is desired that the navigation system be provided with enough information to properly determine efficient routes without being inundated with redundant, useless, and/or superfluous information. There is also a need that the information be provided to a user in a useful, efficient, and easily understandable manner.
Accordingly, it would be very desirable to provide a traffic management architecture that overcomes the above-described shortcomings of the prior art while retaining their advantages.
SUMMARY OF THE INVENTION
The present invention addresses the shortcomings of the prior art systems and methods. In particular, the present invention is directed to a vehicle navigation system that provides automated and personalized traffic information so that a user of the vehicle navigation system does not have to wait for traffic information.
One aspect of the present invention allows a user of the vehicle navigation system to preset commute preferences so that traffic information from a traffic information supplier is pre-broadcast to the vehicle navigation device. In one embodiment, a user of the vehicle navigation system sets commute preferences in a database (e.g., spreadsheet) on the user's home computer, which is then transmitted to the vehicle navigation system. For example, the destination address and preferred roads may be specified in the database. In another embodiment, a user manually enters commute preferences by using touch-sensitive pads on the visual display screen of the vehicle navigation system. The travel route calculated by the vehicle navigation system then becomes a personalized route based at least in part in the user's commute preferences.
Another aspect of the present invention provides a vehicle navigation system that stores historical commute patterns to determine when traffic information should be pre-provided to the vehicle navigation system. In one embodiment, the historical traffic information data (e.g. start times and addresses) is gathered by the vehicle navigation system and transmitted to a remote location. The vehicle navigation system automatically acquires traffic information from the remote location when the vehicle navigation system is located near an address or a start time occurs. The calculation of a travel route is based on the traffic information and is preferably performed before the user enters the vehicle with the vehicle navigation system.
A more complete understanding of the vehicle navigation system and method will be afforded to those skilled in the art, as well as a realization of additional advantages and objects thereof, by a consideration of the following detailed description of the preferred embodiment. Reference will be made to the appended sheets of drawings which will first be described briefly.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 a is a schematic diagram of a first embodiment of a system pursuant to aspects of the invention;
FIG. 1 b is a schematic diagram of a broadcast communication network pursuant to aspects of the invention;
FIG. 1 c is a schematic diagram of a navigation device in communication with a mobile unit pursuant to aspects of the invention;
FIG. 2 is a schematic diagram of an alternate embodiment of a system pursuant to aspects of the invention.
FIG. 3 a is a flow diagram of an embodiment for ensuring quality and reliability of traffic information provided to a vehicle pursuant to aspects of the invention;
FIG. 3 b is a flow diagram of an alternate embodiment for ensuring quality and reliability of traffic information provided to a vehicle pursuant to aspects of the invention;
FIG. 4 is a schematic diagram of an embodiment of a system for coordinating traffic signals pursuant to aspects of the invention;
FIG. 5 is a flow diagram of an embodiment for coordinating traffic signals pursuant to aspects of the invention;
FIG. 6 is a schematic diagram of an embodiment of a system for providing automated and personalized traffic information pursuant to aspects of the invention;
FIG. 7 is a schematic diagram of an alternate embodiment of a system for providing automated and personalized traffic information pursuant to aspects of the invention;
FIG. 8 is a schematic diagram of an embodiment for filtering traffic information pursuant to aspects of the invention;
FIG. 9 a is a flow diagram of an embodiment for filtering traffic information pursuant to aspects of the invention;
FIG. 9 b is a flow diagram of an alternate embodiment for filtering traffic information pursuant to aspects of the invention;
FIG. 9 c is a flow diagram of an another embodiment for filtering traffic information pursuant to aspects of the invention;
FIG. 10 is a flow diagram of an embodiment for providing weight factors and threshold prioritizing pursuant to aspects of the invention.
FIG. 11 is a schematic diagram of an embodiment of a system that initiates a recalculation of a route when there is an upcoming turn pursuant to aspects of the invention;
FIG. 12 is another schematic diagram of an embodiment of a system that initiates a recalculation of a route when there is a upcoming turn pursuant to aspects of the invention;
FIG. 13 is a schematic diagram of an embodiment of a system that performs a route calculation using traffic information broadcast from a remote location and/or a traffic supplier pursuant to aspects of the invention;
FIG. 14 is another schematic diagram of an embodiment of a system that performs a route calculation using traffic information broadcast from a remote location and/or a traffic supplier pursuant to aspects of the invention;
FIG. 15 is a flow diagram of an embodiment that uses every traffic information update to act as a trigger for route calculation and recalculation pursuant to aspects of the invention;
FIG. 16 is a flow diagram of an embodiment that uses every traffic information update to act as a trigger for route calculation but does not recalculate to anticipate user error pursuant to aspects of the invention;
FIG. 17 is a flow diagram of an embodiment that uses streaming traffic information and an internal clock to trigger route calculation and/or recalculation pursuant to aspects of the invention;
FIG. 18 is a flow diagram of an embodiment that waits for a recalculation to finish and then calculates a new alternate route with traffic information pursuant to aspects of the invention;
FIG. 19 is a flow diagram of an embodiment that store the traffic information when recalculation is taking place pursuant to aspects of the invention;
FIGS. 20 and 20 a illustrate an embodiment that stream traffic information and varies traffic information update triggers for route calculation and/or recalculation pursuant to aspects of the invention;
FIG. 21 illustrates an embodiment of a display system pursuant to aspects of the invention;
FIGS. 22 a and 22 b illustrate a case where only traffic incident information is available and addressed by an embodiment of the invention;
FIG. 23 is a flow diagram of an embodiment for combining actual and historical traffic information pursuant to aspects of the invention;
FIG. 24 is a flow diagram of an embodiment for providing a time stamp to traffic incident information and for using the time stamp to determine a route for calculation pursuant to aspects of the invention;
FIG. 25 is a schematic diagram of an embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention;
FIG. 26 is a flow diagram of an embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention;
FIG. 27 is a schematic diagram of an alternative embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention;
FIG. 28 a is a flow diagram of an embodiment for manual filtering traffic information without the need of a position determination unit pursuant to aspects of the invention;
FIG. 28 b is a flow diagram of an embodiment for automatic filtering traffic information without the need of a position determination unit pursuant to aspects of the invention;
FIG. 29 is a schematic diagram of an another embodiment for filtering traffic information without the need of a position determination unit pursuant to aspects of the invention;
FIG. 30 is a flow diagram of an embodiment for filtering traffic information using time zones pursuant to aspects of the invention;
FIGS. 31 a and 31 b illustrate an embodiment of a display system having traffic flow information and traffic incident information pursuant to aspects of the invention;
FIGS. 32 a and 32 b illustrate an alternative embodiment of a display system having traffic flow information and traffic incident information pursuant to aspects of the invention;
FIG. 33 illustrates another embodiment of a display system having traffic flow information and traffic incident information pursuant to aspects of the invention;
FIG. 34 illustrates yet another embodiment of a display system pursuant to aspects of the invention;
FIG. 35 is a flow diagram of an embodiment for providing a pop-up window to convey certain traffic information details pursuant to aspects of the invention;
FIGS. 36 a and 36 b illustrate an embodiment of a display system that displays only traffic information indicating traffic problems pursuant to aspects of the invention;
FIG. 37 is a flow diagram of an embodiment for showing a free-flow icon when no data is received on a particular traffic information sensor pursuant to aspects of the invention;
FIG. 38 is a schematic diagram of an embodiment for adding a header pursuant to aspects of the invention;
FIG. 39 is a flow diagram of an embodiment for adding a header and utilizing the header pursuant to aspects of the invention;
FIGS. 40 and 42 are schematic diagrams of an embodiment for using triangulation of a plurality of repeaters to determine a position and for using the determined position to filter traffic information pursuant to aspects of the invention;
FIGS. 41 and 43 are flow diagrams of an embodiment for using triangulation to determine a position and for using the determined position to filter traffic information pursuant to aspects of the invention;
FIG. 44 is a flow diagram of an embodiment for allowing a user to scroll to a needed traffic information pursuant to aspects of the invention;
FIG. 45 is a flow diagram of an embodiment for filtering traffic information based on a plurality of parameters entered by a user pursuant to aspects of the invention;
FIG. 46 is a schematic diagram of an embodiment for reducing the broadcast of redundant and/or static traffic information pursuant to aspects of the invention;
FIG. 47 is a flow diagram of an embodiment that provide an option for a user to avoid a traffic incident and/or congestion pursuant to aspects of the invention;
FIGS. 48 a and 48 b illustrate an embodiment for avoiding a zigzag route pursuant to aspects of the invention;
FIG. 49 is a flow diagram of an embodiment that reduces zigzagging pursuant to aspects of the invention; and
FIGS. 50, 51, 52, 53 a, and 53 b illustrate embodiments for calculating and utilizing a distance threshold that provides a distance value at which it is likely that a traffic problem location that exists past this distance value from a current location of a vehicle will expire before the vehicle can reach the problem location pursuant to aspects of the inventions.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
The present invention is directed to a system and method for facilitating the exchange of traffic information between a remote location and a vehicle. In particular, the present invention is directed to a system and method that includes a vehicle that exchanges traffic information with the remote location by way of one or more communication networks in a manner that conserves bandwidth while providing sufficient traffic information to the vehicle.
FIG. 1 a shows a first embodiment of a system for facilitating the exchange of information between a remote location 10 and a vehicle 12 pursuant to aspects of the invention. The vehicle 12 includes a navigation device 14. Referring now also to FIG. 1 c, the navigation device 14 may include an output unit 21, a receiver unit 22, an input unit 23, a position detection unit 25, a navigation memory unit 30, a navigation processor unit 26, and an RF transceiver unit 52 that are all in electrical communication with one another. The navigation memory unit 30 includes at least a portion of a user profile and, in some embodiments, includes the entire user profile. In addition, the navigation memory unit 30 includes a road map database portion and, in some embodiments, includes a disk reading unit for reading road map information not built into the navigation device 14. As is provided in greater detail below, the user profile and/or the road map database stored in the memory 30 may be updated in the vehicle by way of the input unit 23, which includes at least one of a keyboard, a touch sensitive display, and a microphone. The user profile and/or the road map database may also be updated by way of information received through the receiver unit 22 and/or the RF transceiver unit 52.
The receiver unit 22 receives information from the remote location 10 and, in one embodiment, is in communication with the remote location by way of a one-to-many communication system. One-to-many communication systems include systems that can send information from one source to a plurality of receivers, such as a broadcast network 31. Broadcast networks include television, radio, and satellite networks. Referring now to FIG. 1 b, in one embodiment, the broadcast network 31 is the XM Radio satellite network 40, which comprises broadcast towers 42, satellite servers (not shown), and satellites 43. The broadcast towers 42 transmit information to the satellites 43, which bounce the information back down to the receiver unit 22 of the navigation device 14.
Referring now back to FIG. 1 a, the information received by the receiver 22 may be processed by the navigation processor unit 26. The processed information may then be displayed by way of the output unit 21, which includes at least one of a display and a speaker. In one embodiment, the receiver unit 22, the navigation processor unit 26 and the output unit 21 are provided access to only subsets of the received broadcast information based on user preferences and/or traffic information demands. The user preferences, as well as user identity information and traffic-related information, can be part of the user profile.
The position detection unit 25 may include a GPS receiver that communicates with a plurality of GPS satellites (separate from the XM satellites) to determine the position of the vehicle 12. For example, the GPS receiver searches for and collects GPS information (or signals) broadcast from four or more GPS satellites that are in view of the GPS receiver. Next, using the time interval between the broadcast time and reception time of each broadcast signal, the GPS receiver calculates the distance between the GPS receiver and each of the four or more GPS satellites. These distance measurements, along with the position and time information received in the broadcast signals, allow the GPS receiver to calculate the geographic position of the vehicle 12.
In the embodiment shown in FIG. 1 a, the mobile unit 18 is used to receive and transmit information from and to the remote location 10; and, in an alternate embodiment shown in FIG. 2, an RF transceiver 252 is used to receive and transmit information from and to the remote location 210. The mobile unit 18 may be a wireless phone or any other device that communicates with other devices by way of the wireless communication network 46. As shown in FIG. 1 c, the mobile unit 100 of the present invention includes a wireless receiver 32, a wireless transmitter 34, a mobile unit processor 40, and an RF transceiver unit 54 that are in communication with one another. The mobile unit 18 is in two-way communication with the remote location 10 by way of the receiver 32, the transmitter 34, and the wireless communication network 46, which comprises numerous base stations. In one embodiment, information is transmitted from or to the vehicle or remote location over a high bandwidth GPRS/1XRTT channel of the wireless communication network 46. If the high bandwidth channel is unavailable, a low bandwidth DTMF channel is used. The receiver 32 receives information from the remote location 10, and the transmitter 34 transmits information to the remote location 10. In other embodiments described below in greater detail, the transmitter 34 also transmits information to suppliers of traffic or other information 48, 50.
In one embodiment, the information received from and transmitted to the remote location 10 by way of the mobile unit 18 is accessed by the user through the navigation device 14, which is in communication with the mobile unit 18. The mobile unit 18 may be embedded in the vehicle 12 and be in communication with the navigation device 14 by, for example, a cable (not shown).
In another embodiment, the navigation device 14 and mobile unit 18 are in communication with one another by way of RF transceiver units 54 and 52. Both the navigation device 14 and the mobile unit 18 include RF transceiver units 52, 54, which, in one embodiment, comply with the Bluetooth® wireless data communication format. The RF transceiver units 52, 54 allow the navigation device 14 and the mobile unit 18 to communicate with one another. In other embodiments not shown, the receiver 32 and transmitter 14 of the mobile unit 18 and the receiver unit 20 of the navigation device 14 allow the navigation device 14 and mobile unit 18 to communicate with one another. In yet other embodiments, there may be an RF transceiver that is separate from the navigation device 14 and the mobile unit 18 and that allows the navigation device 14 and mobile unit 18 to communicate with one another.
In the alternate embodiment shown in FIG. 2, the navigation device 214 transmits and receives information to and from the remote location 210 by way of the RF transceiver 252, access points 270, 272, and gateways 274, 276 that are in communication with the network 262. In one embodiment, the RF transceiver 252 and the access points 270, 272 are compliant with the IEEE 802.11 specification, and such transceivers and access points include Wi-Fi®-certified equipment. The access points 270, 272 are typically in communication with the gateways 274, 276 by way of a cable, and the gateways are in communication with the remote location 210 by way of the network 262. The access points 270, 272 are in communication with the RF transceiver 252 and have a limited range over which they can communicate with the RF transceiver 252. Thus, it is preferable that there be numerous access points 270, 272 positioned so that the distance between the access points and the areas through which a vehicle 12 might pass is less than or equal to the limited range of the access points. When the access points 270, 272 are so positioned, the RF transceiver 252 effectively exchanges information with the access points 270, 272 and, thus, the remote location 210.
Note that in the alternate embodiment of FIG. 2, the navigation device 214 also includes input and output units, a receiver unit, a memory unit, and a processor unit, none of which are shown. The components of the alternate navigation device embodiment 214 have the same functionality as do the components of the navigation device 14 of the first embodiment.
The remote location 10, 210 includes a remote server 44, 244, a remote transmitter 56, 256 and receiver 58, 258, and a remote memory 60, 260 that are in communication with one another. As provided above, in the first embodiment, the remote transmitter and receiver 56, 58 communicate with the navigation device 14 and mobile unit 100 by way of the broadcast 31 and wireless 46 communication networks, respectively. In the alternate embodiment, the remote transmitter and receiver 256, 258 communicate with the navigation device 214, including the RF transceiver 252, by way of the broadcast communication network 231 and a network 262. The remote location 10, 210 is also in communication with suppliers of traffic and/or other information 48, 50, 248, 250 such as government traffic information suppliers, private traffic information suppliers, and users of other vehicles, by way of the network 62, 262.
In both the first and alternate embodiments shown in FIGS. 1 and 2, the network 62, 262 is typically a wide area network (WAN) such as the Internet. In other embodiments, some of the information suppliers 48, 50, 248, 250, such as the government and private traffic information suppliers, may be in communication with the remote location 10, 210 by way of a local area network (LAN), while other information providers 48, 50, 248, 250 such as the vehicle users, are in communication with the remote location by way of the Internet. In yet other embodiments, the RF transceiver 252 is in communication with the remote location 210 and/or the information providers 248, 250 by way of a network 262 that is an LAN. In these other embodiments, the LAN 262 is compliant with the IEEE 802.3 specification or is an Ethernet network.
As provided in greater detail below, the information suppliers 48, 50, 248, 250 may transmit updated user profiles and traffic-related information to the remote location 10, 210. A plurality of user profiles are in a user profile database, which, along with traffic-related information, is stored in the remote memory 60, 260. The updated user profiles and new traffic-related information are transmitted from the remote location 10, 210 to the navigation device 14, 214 by way of the broadcast network 31, 231. In other embodiments, the new traffic-related information and updated user profiles may be transmitted to the vehicles 12, 212 by way of the wireless network 46 or the network 262. At the vehicle, the user profile stored in the memory 30 of the navigation device 14 is updated, and the vehicle-related information is made accessible to the user by way of the output unit 26 of the navigation device 14. In other embodiments, the information providers may communicate directly with the mobile unit 18 or RF transceiver 252 by way of the wireless communication network 46 or the network 262.
FIG. 3 a shows an embodiment for ensuring quality and reliability of traffic information provided to the navigation device 14, 214 pursuant to aspects of the invention. The embodiment uses the navigation device 14, 214 (including its position detection unit 24) on the vehicle 12, 212 to determine vehicle location and to detect sensor error or errors on a road segment/lane (e.g., speed sensors on a freeway lane/segment). The embodiment then uses the wireless network 46 or the network 262 to communicate the position determination and the error detection data from the navigation device 14, 214 to the remote location 10, 610 and/or traffic information suppliers 48, 248 in an effort to refine the traffic information provided. At step 300, the navigation device 14, 214 uses its position detection unit 24 to determine vehicle location and speed data. The vehicle's location and speed data is then communicated over the wireless communication network 46 or the network 262 to the remote location 10, 210.
At step 305, the remote location 14, 214, via its remote server or servers 44, 244, processes and passes the vehicle location and speed data to traffic information supplier or suppliers 48, 248. The data from the remote location is transmitted over the network 62 or the network 262 to the traffic information supplier or suppliers 48, 248. In one embodiment, the data is processed at the remote location 14, 214 by filtering the information based on predetermined criteria and translating the information into a format acceptable to the traffic information supplier or suppliers 48, 248. At step 310, the transmitted vehicle location and vehicle speed data is processed at a database of the traffic information supplier or suppliers 48, 248. At step 315, the vehicle's location and speed data (i.e., the back channel data) is compared with sensor data from a speed sensor on a lane of a freeway to determine the difference between the vehicle speed data and the sensor speed data. The location of the speed sensor corresponds to the location of the vehicle where the vehicle's location and speed data was detected. At step 320, a quantized differential action scheme based on a range of the speed differences between the vehicle speed data and the sensor speed data is used to determine action items. FIG. 3 shows that a difference of zero (0) to ten (10) mph is acceptable, a difference of eleven (11) to fifteen (15) mph triggers an automatic alert to check the speed difference and speed sensor, a difference of sixteen (16) to twenty (20) mph triggers an automatic alert to monitor the speed of the sensor, a difference of twenty-one (21) to twenty-five (25) mph triggers an automatic replacement alert, and a difference of twenty-six (26) or more mph triggers automatic replacement or maintenance of the sensor. Once the appropriate action item has been determined, at step 325, the refined traffic information data (e.g., with corrected speed sensor data) is broadcast to a plurality of vehicles that may include vehicle 12, 212, by way of the broadcast network 31, 231.
The above-described mechanisms and process for ensuring quality and reliability of traffic information are for exemplary purposes only, and the invention is not limited thereby. For example, FIG. 3 b shows an alternate embodiment that uses a quantized percentage differential method. In this method, as shown in steps 330 and 335, a percentage difference between the vehicle speed data and the speed sensor data is used to select an action item from a plurality of action items rather than using the actual differences between the vehicle speed data and the speed sensor data. That is, at step 330, the vehicle's location and speed data (i.e., the back channel data) is compared with sensor data from a speed sensor on a lane of a freeway to determine a percentage (%) difference in speed of the vehicle speed data and the sensor speed data. At step 335, a percentage quantized differential action scheme based on a range of the percentages of difference of the sensor speed data to the back channel data is used to select an action from a plurality of action items to be taken. FIG. 3 b shows that a difference of less than 20% of the sensor speed data to the back channel data is acceptable, a 21% to 30% difference triggers an automatic alert to check the speed sensor, a 31% to 40% difference triggers an automatic alert to monitor the speed of the sensor, a 41% to 50% difference triggers an automatic replacement alert, and a greater than 50% difference triggers the automatic replacement or maintenance of the sensor.
Note that, in the alternate embodiment of FIG. 3 b, the embodiment also includes the transmission and processing steps 300, 305, 310, and 325 described above for FIG. 3 a. In addition, the steps of FIG. 3 b use the same devices, units, and/or components as the embodiment shown in FIG. 3 a. Moreover, those skilled in the art will appreciate that there are other ways to process the traffic-related information to ensure quality and reliability.
FIG. 4 shows an embodiment for coordinating traffic signals pursuant to aspects of the invention. The embodiment uses the navigation device's position determination unit (e.g., the GPS) and back channel capabilities (e.g., the wireless communication network 46 or the network 262). The embodiment includes a navigation device (e.g., a device 14, 214 shown in FIGS. 1 a, 2) having a position detection unit (e.g., unit 24 shown in FIG. 1 c). The navigation device is located on a vehicle 412 and is used to determine the location and speed of the vehicle 412 and to coordinate traffic signals 445 (e.g., freeway off-ramp signals). More specifically, the embodiment uses back channel communication 446 to communicate the speed and location of the vehicle 412 detected from the navigation device (e.g., 14, 214) to a remote location 410. The remote location 410 then transmits the speed and location of the vehicle to a traffic information supplier 448 that passes this information to a signal control center 450 (e.g., a city traffic center). The signal control center then adjusts, coordinates, and manages the traffic signals 445 based on the information from the traffic information supplier 448.
In general, according to FIG. 4, the embodiment provides a method for coordinating traffic signals, as diagrammed in FIG. 5. At step 505, the method receives probe and flow sensor data (e.g., data on the position of the vehicle, the speed of the vehicle, and the average speed of vehicles on a lane of a road). At step 510, the method displays the flow-sensor data. At step 515, the difference in speed between various lanes 460 of a roadway (e.g., a freeway) and the location of the vehicle 412 are determined. If the difference in speed between lanes 460 is less then twenty (20) mph and the vehicle 412 is within an amount of miles from the off-ramp (e.g., within a predetermined amount miles of the off-ramp), the signal length or signal timing for the traffic signals 455 is increased pursuant to step 520 and the chart shown below.
Distance from off-ramp Increase signal length
>0.25 miles 10%
>0.5 miles 15%
>0.75 miles 20%
>1.0 miles 30%
>1.25 miles 40%
>1.5 miles 50%
Those skilled in the art will appreciate that the above method for coordinating traffic signals (e.g., by using lane averaging to clear freeway off-ramps) alleviates problems that occur when traffic-flow sensors are not available or not accurate and reduces the potential for accidents. It should be appreciated that the above-described mechanisms and process for coordinating traffic signals are for exemplary purposes only and that the invention is not limited thereby.
FIG. 6 shows an embodiment for providing automated and personalized traffic information so that a user of a navigation device 614 located on a vehicle 612 does not have to wait for traffic information. The embodiment allows the user of the navigation device 614 to preset its commute preferences (e.g., 7 a.m. home to work; 5 p.m. work to home) so that traffic information from the traffic information supplier 648 and/or remote location 610 can be pre-provided or pre-broadcast to the navigation device 614 via a broadcast network 631. More specifically, rather than require the user to input its destination point in the navigation device 614, the present embodiment allows the user to store an address/destination in a memory unit (e.g., unit 30 in FIG. 1 c) of the navigation device 614. In addition, rather than requiring the user to wait for the traffic information to be updated by the traffic information supplier 648 and for the user route to be calculated by the navigation device 614, the present embodiment allows the user to set its commute preferences in an owner link 615 (e.g., a database) located in the remote location 610 so that traffic information can be pre-broadcast to the navigation device 614. That is, the present embodiment allows a user to (1) set an address/destination in a memory unit (e.g., unit 30 in FIG. 1 c) of the navigation device 614 and (2) set its commute preferences in an owner link 615 (e.g., a database) via the remote location 610 so that traffic information can be pre-broadcast to the navigation device 614.
The above-described mechanisms and process for providing automated and personalized traffic reports are for exemplary purposes only and the invention is not limited thereby. For example, FIG. 7 shows an alternate embodiment that automatically stores historical data of the user to determine when traffic information should be pre-provided. In this embodiment, based on historical commute patterns, the embodiment uses back channel communication 746 to store start times and addresses on a remote location 710 such that no address input is required. This embodiment automates an owner link function (e.g., 615 on FIG. 6) for traffic information by storing the pertinent commute information to memory with an internal clock (e.g., a GPS internal clock) of the navigation device 714 to determine when to gather traffic information data and begin route calculations. The gathering of the traffic information data and the calculation of routes are performed before the user enters the vehicle 712 with the navigation device 714. It should be appreciated by those skilled in the art that the above method further increases the convenience for providing automated and personalized traffic reports as compared to the method and system described with respect to FIG. 6.
FIG. 8 shows a method for filtering traffic information. Traffic information broadcast from a traffic information supplier to a fifteen (15) mile radius 800 from a user's location is filtered to expedite traffic calculation. This filtering embodiment saves on processing hardware and/or a bandwidth requirement of a navigation device and/or the traffic supplier. More specifically, the traffic information supplier broadcasts nationwide traffic information into twenty (20) smaller metropolitan area-wide information (or metros). The present filtering embodiment uses position information (e.g., GPS location information) at the start-up of the navigation device or from the memory of the navigation device if the navigation device is unable to acquire position information not only to filter the needed metro from the nationwide traffic information but also to filter down the needed metro to specific user applicable area. That is, in the present embodiment, each traffic communication packet between the navigation device and its traffic supplier includes information on metro location and filtering information for further filtering the traffic information to a fifteen (15) mile radius from a user's location.
In general, according to FIG. 8, the embodiment provides a method for real time filtering of traffic updates, as diagrammed in FIG. 9 a. At step 900, the method determines the location of the navigation device (e.g., a GPS location). At step 905, the method receives traffic information (e.g., U.S. traffic information). At step 910, the method determines whether the traffic information is within a predetermined radius of the navigation device or fifteen (15) mile radius of the navigation device. If the traffic information is within the predetermined radius, the navigation device then calculates a route for the user of the navigation device using the filtered traffic information at step 915. However, if the traffic information is not within the predetermined radius, then the traffic information is discarded at step 920.
The above-described method for real time traffic update filtering are for exemplary purposes only and the invention is not limited thereby. For example, FIG. 9 b shows an alternate method that uses GPS location information to automatically filter traffic information based on a location of the navigation device. However, if there is still too much traffic information due to additional congestion in a specific metro for the navigation device to display/calculate effectively, the method uses decreasing radius(es) to display/calculate information in the specific metro. In this method, as shown in step 900, a location of a navigation device (e.g., a GPS location) is determined. At step 907, the method receives traffic information for a specific metro. At step 930, the method determines whether the traffic information is approaching a memory capacity level (e.g., a 90% memory capacity level) of the navigation device. If the traffic information is approaching the memory capacity, the method then selects a step-to-step criteria for filtering the traffic information pursuant to steps 935, 940, and 945 and the chart shown below. Steps 935, 940, and 945 are repeated until the memory capacity of the navigation device is below the predetermined capacity level. The method then move to step 950 to calculate a route using the filtered traffic information. The calculated result is displayed at step 955.
Step Criteria
1 Entire Metro incident and flow (i/f info)
2 distance = 15 miles (i/f info)
3 distance = 10 mi (i/f info)
4 Distance = 7.5 mi (i/f info)
5 Dist = 5 mi (i/f info)
FIG. 9 c shows another method for filtering traffic information. This method monitors memory capacity to maximize an available metro traffic information and to increase the traffic information available for calculation by a navigation device. As shown in step 900, the method determines a location of a navigation device (e.g., a GPS location). At step 907, the method receives traffic information for a specific metro. At step 960, the method determines whether the traffic information is approaching a memory capacity level (e.g., a 90% memory capacity level) of the navigation device. If the traffic information is not approaching the memory capacity, the method then selects a step-to-step criteria for reverse-filtering (or increasing) the available traffic information pursuant to steps 960, 965, 970, 975, and 980 and the chart shown below. Steps 960, 965, 970, 975, and 980 are repeated until the memory capacity of the navigation device is approaching the predetermined capacity level. The method then calculates a route using the reverse-filtered traffic information at step 985 and displays the calculated route at step 990.
Step Criteria
1 distance = 15 miles (i/f info)
2 distance = 25 miles (i/f info)
3 Entire Metro incident and flow (i/f info)
4 Metro + adjacent Metro(s)
FIG. 10 shows a method for providing weight factors and threshold prioritization when a broadcast limit (e.g., an XM bandwidth limit) is close to being reached. The method is utilized with a broadcast network (e.g., an XM broadcast network) that broadcasts traffic information initially, for example, to twenty metropolitan areas (metros). The method prioritizes traffic information and maintains maximum bandwidth availability by assigning weight factors to each reported incident and broadcasting the traffic information based on the assigned weight factors. The assigning of the weight factors and the broadcasting of traffic information based on these factors would occur only when a certain preset broadcast threshold is met (e.g., 80% capacity of the network has been reached). At step 1005 of FIG. 10, a central processor at a remote location (e.g., 10 in FIG. 1 a) and/or at a navigation device (e.g., 12 in FIG. 1 a) determines if a network broadcast threshold has been met (e.g., 80% of the capacity of the broadcast network). If the broadcast threshold has been met, weight factors are assigned to each piece of the traffic information (e.g., traffic information packets) based on the subject matter of the traffic information pursuant to step 1015 and the chart shown below.
Item Description Weight Factor
Severity Accident
10
Incident 9
Construction 8
Weather 8
Location within city metro 10
outside city metro 8
Date Weekday 10
Weekend 9
Holiday 8
Time 6-9 AM 10
9-4 AM 6
4-7 PM 10
7 PM-6 AM 2
Weight factor Ambulance responding 9
Fatality 10
>30 min. delay 2
>1 hr. delay 4
>1.5 hr. delay 6
>2 hr. delay 8
>2.5 hr. delay 10
Those skilled in the art will appreciate that the above method for the management of traffic information and broadcast bandwidth provides a proactive approach to ensure most critical traffic information or incidents are reported while still maintaining bandwidth requirements. It should also be appreciated that the above-described mechanisms and process for bandwidth management are for exemplary purposes only and that the invention is not limited thereby.
FIG. 11 shows an embodiment of a navigation device that initiates a recalculation of a route 1100 when there is a upcoming turn 1105 to anticipate a user of the navigation device missing the turn 1105. For example, referring now also to FIG. 12, the navigation device makes an assumption that a vehicle's starting point 1214 is somewhere ahead of its actual starting point 1212, not on the route 1200, to anticipate a user of the navigation device missing a turn 1205. In the present context, recalculation refers to all possible routes that the user may take when an error occurs (e.g., user should go left but goes right). Recalculation can also be referred to as pre-calculation or error anticipating calculation. Referring now back to FIG. 11, the recalculations can be made at variable times 1110 a 1110 b, 1110 c, 1110 d.
FIG. 13 shows an embodiment of a navigation device that performs a route calculation using traffic information broadcast from a remote location and/or a traffic information supplier. For example, referring now to FIG. 13, the traffic information updates may be provided to the navigation device every one (1) minute or five (5) minutes, and the navigation device calculates a new route with every traffic information update for better route guidance. That is, referring now also to FIG. 14, once traffic information has been completely refreshed or updated, a route calculation is triggered using a vehicle's current position 1412 as the starting point.
FIG. 15 shows an embodiment of a method that uses every traffic information update to act as a trigger for calculation and recalculation (i.e., anticipation of a user error). At step 1500, a navigation device is set at a route guidance mode. At step 1505, the navigation device determines whether to recalculate (i.e., pre-calculate) a new route. For example, the navigation device anticipates a user error as shown in FIG. 12 and determines that a new route (e.g., one based on an anticipated user error) should be calculated. If the navigation device recalculates the new route, the new route is displayed to a user of the navigation device at step 1510, and the method moves to step 1515. If the navigation device does not recalculate the new route, the method moves directly to step 1515. At step 1515, the navigation device determines whether a traffic information update has been provided to the navigation device. If the traffic information update has not been provided, the method moves to step 1500. If the traffic information update has been provided, the navigation device calculates a new alternative route with the updated traffic information at step 1520, and the method moves to step 1525. At step 1525, the method determines whether the alternative route is better (e.g., whether it has a shorter estimated travel time) than the route previously displayed to the user. If the alternative route is better, the navigation device displays the alternative route with the traffic information at step 1530, and then moves to step 1500.
The above-described mechanisms and process for route calculation and recalculation using traffic information are for exemplary purposes only, and the invention is not limited thereby. For example, FIG. 16 shows an embodiment of a method that uses every traffic information update to act as a trigger for recalculation but does not recalculate to anticipate user error. The embodiment is designed to reduce processing requirements at the navigation device. That is, at step 1600, a navigation device is set at a route guidance mode, and the method moves immediately to step 1605. At step 1605, the navigation device determines whether a traffic information update has been provided to the navigation device. If the traffic information update has not been provided, the method moves to step 1600. If the traffic information update has been provided, the navigation device calculates a new alternative route with the updated traffic information at step 1610, and the method moves to step 1615. At step 1615, the method determines whether the alternative route is better (e.g., whether it has a shorter estimated travel time) than the route previously displayed to the user. If the alternative route is better, the navigation device displays the alternative route with the traffic information at step 1620, and then moves to step 1600.
FIG. 17 shows an embodiment of a method that uses streaming (non-static or constantly changing) traffic information data and an internal processing clock to trigger route calculation at fixed and/or variable time intervals. At step 1700, a navigation device is set at a route guidance mode. At step 1705, the navigation device determines whether a predetermined amount of time (e.g., one minute) has elapsed using an internal processing clock (e.g., one located in a processor unit and/or a position determination unit of the navigation device). If the predetermined amount of time has not elapsed, the method moves to step 1700. If the predetermined amount of time has elapsed, the navigation device calculates a new alternative route with the updated traffic information at step 1710, and the method moves to step 1715. At step 1715, the method determines whether the alternative route is better (e.g., whether it has a shorter estimated travel time) than the route previously displayed to the user. If the alternative route is better, the navigation device displays the alternative route with the traffic information at step 1720 and then moves to step 1700.
FIG. 18 shows an embodiment of a method that waits for a recalculation (i.e., an anticipation of a user error) to finish and then calculates a new alternate route with traffic information to determine the best route. That is, in the method shown in FIG. 18, the recalculation (without traffic information) always takes precedence over the calculation with traffic information. In addition, it should be appreciated that the steps shown in FIG. 18 are similar to those shown for FIG. 15 with the exception of additional step 1512 (located between the recalculation step 1510 and the traffic information update determination step 1515) that determines whether the recalculation (at step 1510) has been completed.
FIG. 19 shows an embodiment of a method that stores the traffic information data when a navigation device is recalculating a route and/or receiving a traffic information update. After the recalculation is completed, the method then resumes route calculation with the traffic information data. In addition, the method of FIG. 19 takes the previous traffic information calculated route and compares it with the new recalculated route (e.g., to determine the best route) when the method is between traffic information updates. That is, the method uses its old traffic information until new traffic information has been completely provided to the navigation device.
FIGS. 20 and 20 a show an embodiment of a method that streams traffic information data to provide users with the most up to date information. In addition, depending on the time of day, the method varies the traffic information update triggers such that, at peak commute times, the recalculation (and calculation) triggers are increased and, at off peak commute times, the triggers are decreased. Those skilled in the art will appreciate that the method of FIGS. 20 and 20 a minimizes the amount of time needed for updated traffic information to trigger a new calculation and provides updated traffic information based on a need use basis.
In addition, FIG. 20 shows a method for increasing and decreasing amounts and/or numbers of broadcast traffic information (e.g., via an XM network) based on commute times. More specifically, the method varies the broadcast of traffic information data based on commute times in each time zone, as shown in the following chart.
Pacific Mountain Central Eastern
Broadcast Broadcast Broadcast Broadcast
Time rate rate Time rate Time rate
1:00 AM 5 min 2:00 AM 5 min 3:00 AM 5 min 4:00 AM 5 min
2:00 AM 5 min 3:00 AM 5 min 4:00 AM 5 min 5:00 AM 5 min
3:00 AM 5 min 4:00 AM 5 min 5:00 AM 5 min 6:00 AM 30 sec
4:00 AM 5 min 5:00 AM 5 min 6:00 AM 30 sec 7:00 AM 30 sec
5:00 AM 5 min 6:00 AM 30 sec 7:00 AM 30 sec 8:00 AM 30 sec
6:00 AM 30 sec 7:00 AM 30 sec 8:00 AM 30 sec 9:00 AM 30 sec
7:00 AM 30 sec 8:00 AM 30 sec 9:00 AM 30 sec 10:00 AM 5 min
8:00 AM 30 sec 9:00 AM 30 sec 10:00 AM 5 min 11:00 AM 5 min
9:00 AM 30 sec 10:00 AM 5 min 11:00 AM 5 min 12:00 PM 5 min
10:00 AM 5 min 11:00 AM 5 min 12:00 PM 5 min 1:00 PM 5 min
11:00 AM 5 min 12:00 PM 5 min 1:00 PM 5 min 2:00 PM 5 min
12:00 PM 5 min 1:00 PM 5 min 2:00 PM 5 min 3:00 PM 5 min
1:00 PM 5 min 2:00 PM 5 min 3:00 PM 5 min 4:00 PM 30 sec
2:00 PM 5 min 3:00 PM 5 min 4:00 PM 30 sec 5:00 PM 30 sec
3:00 PM 5 min 4:00 PM 30 sec 5:00 PM 30 sec 6:00 PM 30 sec
4:00 PM 30 sec 5:00 PM 30 sec 6:00 PM 30 sec 7:00 PM 30 sec
5:00 PM 30 sec 6:00 PM 30 sec 7:00 PM 30 sec 8:00 PM 5 min
6:00 PM 30 sec 7:00 PM 30 sec 8:00 PM 5 min 9:00 PM 5 min
7:00 PM 30 sec 8:00 PM 5 min 9:00 PM 5 min 10:00 PM 5 min
8:00 PM 5 min 9:00 PM 5 min 10:00 PM 5 min 11:00 PM 5 min
9:00 PM 5 min 10:00 PM 5 min 11:00 PM 5 min 12:00 AM 5 min
10:00 PM 5 min 11:00 PM 5 min 12:00 AM 5 min 1:00 AM 5 min
11:00 PM 5 min 12:00 AM 5 min 1:00 AM 5 min 2:00 AM 5 min
12:00 AM 5 min 1:00 AM 5 min 2:00 AM 5 min 3:00 AM 5 min
In addition, if certain metros have more congestions, user demands, vehicles, etc., the above broadcast method can vary the broadcast time or rate in the specific metro as shown in the following chart.
Broadcast
Metro time rate
6:00 to 9:00 AM Every 30 sec.
9:01 AM to 3:59 PM Every 5 min.
4:00 PM to 7:00 PM Every 30 sec.
7:01 PM to 5:59 AM Every 5 min.
Those skilled in the art will appreciate that the above method for providing a variable broadcast rate allows a navigation device to receive quicker and more accurate broadcast traffic information. It should also be appreciated that the above-described mechanisms and processes for variable broadcasting are for exemplary purposes only, and the invention is not limited thereby.
FIG. 21 shows an embodiment of a display system that, when a user is rerouted by a navigation device, displays the new route's mileage 2100 and/or estimated time of arrival (ETA) 2105 and/or differences compared to the original route 2110 so that the user can make a direct comparison of the two routes. More specifically, the present display system allows the navigation device using broadcast traffic information to convey reasons why a new route using the traffic information has been calculated, selected, and/or displayed to the user (e.g., because it has a shorter travel time even if the actual distance may be longer). It should also be appreciated that the above-described display system is for exemplary purposes only and that the invention is not limited thereby.
In general there are two types of traffic information: traffic flow information and traffic incident information. Ideally, both types of information should be available to a navigation device (e.g. 14 in FIG. 1) so that the navigation device can use the incident information to avoid a traffic incident and the flow information to avoid traffic congestion. To illustrate a particular problem that an embodiment of the present invention addresses, FIG. 22 a shows a case where the traffic incident information is available but the flow information is not available. In this case, a navigation device may determine that a route 2200 b is free flowing and direct the users to that route 2200 b instead of route 2200 a or route 2200 c. However, as shown in FIG. 22 b, route 2200 b is actually congested and route 2200 c with an reported incident may actually be better (i.e., a faster route).
In general, according to problems illustrated in FIGS. 22 a and 22 b, the embodiment of the present invention provides a method for combining actual and historical traffic information to predict traffic congestion, as diagrammed in FIG. 23. At step 2300, a navigation device (e.g., the navigation device 14 shown in FIG. 1 a) calculates a route using traffic information that has been provided. At step 2305, the navigation device determines if the route calculation has the required traffic flow information. If the required traffic flow information is available, the navigation device then calculates the best route and displays this route to a user of the navigation device at step 2330. If the required traffic flow information is not available or cannot be provided, the navigation device contacts a database (e.g., a database in the remote location 10 shown in FIG. 1 a) via its back-channel capabilities to receive historical traffic flow information at step 2310. The historical traffic flow information is then broadcast over a broadcast communication network (e.g., 31 in FIG. 1 a) to the navigation device at step 2320. At step 2325, the navigation device then calculates the best route and displays this route to a user of the navigation device at step 2330. Again, it should be appreciated that the above-described mechanisms and process for combining actual and historical traffic information are for exemplary purposes only and that the invention is not limited thereby.
FIG. 24 shows an embodiment for providing a time stamp to traffic incident information and for using the time stamp to determine a route for calculation by a navigation device. The embodiment can be applicable to a case when traffic flow information is not available, for example, due to sensor not available, damaged, malfunctioning, etc. The embodiment can also be applicable to a case where traffic information that is provided does not report details of the extent of the congestion (e.g., from where to where is traffic congested) and/or a case where delays occur in providing incident details other than a location of an incident. Specifically, if traffic flow information is not available, traffic incident information with extent of where to where traffic congestion is occurring is not available, and/or there are equal numbers of traffic incidents to avoid, the embodiment provides a method that time stamps traffic incident information (having a location of the incident) and calculates a route by avoiding latest traffic incidents. At step 2400, the method begins a route calculation process. At step 2405, the route calculation process determines if traffic flow information or if traffic incident information with extent information (e.g., extent information from where to where is traffic congested) is available. If the determined traffic information is available, the method moves to step 2412 to perform a route calculation based on the traffic information. The calculated route is then displayed at step 2420. If the traffic flow information and the traffic incident information with extent details are not available, the method moves to 2410 to determine a time from traffic incident reported for each reported traffic incident. The method, at step 2415, then performs a route calculation based on a route having the traffic incidents with the greatest total time (i.e., by avoiding the latest traffic incidents). The calculated route (not having the latest traffic incidents) is then displayed at step 2420.
Those skilled in the art will appreciate that the above method for providing a time stamp to traffic incident information and for using the time stamp to determine a route calculation alleviates problems that occur when only basic traffic incident information is available and provides a user of a navigation device (e.g. a device 14, 214 shown in FIGS. 1 a, 2) with a way to automatically avoid traffic incidents based on a timer-based incident avoidance scheme. It should be appreciated that the above-described mechanisms and process for route calculations based on an automatic timer based incident avoidance scheme are for exemplary purposes only and the invention is not limited thereby.
Referring now back to FIG. 8 and FIGS. 9 a to 9 c, the traffic information supplier broadcasts nationwide traffic information into twenty (20) smaller metropolitan area-wide information (or metros) so that embodiments of the present invention can use position information (e.g., GPS location information) to filter the needed traffic information. However, not all vehicles have GPS navigation systems, and/or receive GPS signals to identify their specific geographic location, and triangulation methodology may not be reliable and/or available due to repeater locations and/or building interference. Accordingly, referring now to FIG. 25, an embodiment of the invention provides a reliable method for filtering traffic updates without the need of GPS navigation systems, GPS signals, repeaters, and/or repeater signals. The embodiment provides a method for a user on a vehicle 2512 to specify its home address and applicable metro location via an owner link 2515 (e.g., a website of the owner link 2515) so that a specific traffic information can be received by the vehicle 2512.
Specifically, the embodiment of FIG. 25 provides a method that allows a user to manually enter a metro location, as diagrammed in FIG. 26. At step 2600, a user registers (or specifies) its home address and applicable metro location via an owner link 2515. At step 2605, specific traffic information for various regions (or metros) are broadcasted. At step 2610, the method determines whether a specific part of the broadcasted traffic information is in a user-specified metro. If the specific part of the broadcasted traffic information is in the user-specified metro, the method then displays (or calculates a route for the user via a navigation device) using the filtered traffic information at step 2620. However, if the specific part of the traffic information is not in the user-specified metro, then the specific part of the information is discarded at step 2615.
The above-described method for real time traffic filtering is for exemplary purposes only and the invention is not limited thereby. For example, FIG. 27 shows an embodiment that allows a user to manually enter its metro location via a menu on a radio of a vehicle 2712. As diagrammed in FIG. 28 a, a method of FIG. 27 begins with a user inputting its applicable metro via a control on a radio at step 2800. At step 2805, the radio of the invention interfaces with broadcasted traffic information to filter the traffic information. At step 2810, the method determines whether a specific part of the broadcasted traffic information is in a user-specified metro. If the specific part of the broadcasted traffic information is in the user-specified metro, the method then displays (or calculates a route for the user via a navigation device) using the filtered traffic information at step 2820. However, if the specific part of the traffic information is not in the user-specified metro, then the specific part of the information is discarded at step 2815.
FIG. 28 b shows another embodiment of a method for filtering traffic information. This embodiment uses a user's FM radio station presets and/or radio station settings on a radio of a vehicle 2712 to automatically receive and/or filter applicable metro traffic information. As envisioned, the user can also have the option of inputting its specific location manually via the radio. More specifically, the method of FIG. 28 b receives traffic information (e.g., U.S. traffic information) at step 2830. At step 2805, the method determines if a radio of the vehicle 2712 is powered on. If the radio is on, the method then checks the user's current radio station with a table or database 2845 to determine a location of the user's vehicle 2712 at step 2840. If the radio is not on, the method then checks the user's preset radio station with a table or database 2845 to determine a location of the user's vehicle 2712 at step 2850. At step 2855, the method determines whether it can use this automatically determined location to determine a metro. If the metro can not be determined from the automatically determined location, the method then requests the user to manually specify a metro at step 2860. If the automatically determined location can determine the metro, then the method determines if traffic information for the automatically determined metro is available at step 2865. If the traffic information for the automatically determined metro is not available, the method displays a “traffic information not applicable” indication to the user at step 2870. If the traffic information for the automatically determined metro is available, the method then displays (or calculates a route for the user via a navigation device) using the automatically filtered traffic information at step 2875.
FIG. 29 shows an embodiment for allowing a vehicle 2912 to automatically update via an internal clock of the vehicle 2912 to determine which time zone the vehicle 2912 is in and filters traffic information for the vehicle via the determined time zone. The embodiment broadcasts traffic information based on time zones (e.g., Pacific Time Zone, Mountain Time Zone, Central Time Zone, and Eastern Time Zone) 2920 and the vehicle 2912 then filters 2935 out the non-matching time zone traffic information 2930.
More particularly, the embodiment of FIG. 29 provides a method that automatically filters traffic information based on time zones, as diagrammed in FIG. 30. At step 3000, the method determines an internal clock setting of a vehicle 2912. At step 3005, the method receives traffic information (e.g., U.S. traffic information). At step 3010, the method determines whether a specific part of the received traffic information is in a user's or a vehicle's identified time zone. If the specific part of the received traffic information is in the vehicle's identified time zone, the method then displays (or calculates a route for the user via a navigation device) using the filtered traffic information at step 3015. However, if the specific part of the traffic information is not in the vehicle's identified time zone, then the specific part of the information is discarded at step 3020.
FIG. 31 b shows an embodiment of a display system that displays traffic flow information 3100 and incident icons 3110 in the direction that a user is traveling. In addition, the system only displays the roadways or freeways 3115 that the user would be driving on (i.e., if a vehicle is heading south, no northbound freeways will be displayed by the display system). The above-described display systems allows the present display system to convey information to a user in a clear, concise, and understandable manner without inundating the user with redundant, useless, and/or superfluous information as compared with the embodiment shown in FIG. 31 a.
FIGS. 32 a and 32 b show an embodiment of a display system that allows a user to use a cursor 3230 of a navigation device so that the user can click on an actual roadway or freeway to get traffic flow information (and/or traffic incident information) 3200 on the roadway or freeway.
FIG. 33 shows an embodiment of a display system that, when a navigation device is providing a route guidance for a user, the display system of the navigation device provides a display icon 3310 on a road segment so the user can visually see an upcoming incident. In addition, the display system can also provides a turn-by-turn guidance display as shown in the following chart.
Route Miles Time Incidents on route
 60 East 3 15 min
Figure US07289904-20071030-P00001
710 South 8 35 min
Figure US07289904-20071030-P00002
Figure US07289904-20071030-P00001
105 West 15 16 min
405 North 10 45 min
Figure US07289904-20071030-P00001
Those skilled in the art will appreciate that the above display systems for reducing non-essential traffic information alleviate problems associated with driver distractions. It should be appreciated that the above-described mechanisms and processes for displaying traffic information are for exemplary purposes only and the invention is not limited thereby.
FIG. 34 shows a window 3400 for displaying traffic information on a travel route 3405. The window 3400 is utilized by a navigation device (e.g., 14 in FIG. 1 a) after the navigation device detects a traffic incident on a route ahead. The navigation device displays the traffic incident details in the window 3400. The window 3400 appears or pops up on an output unit (e.g., 21 in FIG. 1 a) of the navigation device that is displaying a map 3410 of the route ahead 3405. The window 3400 informs a user of the navigation device of the traffic condition ahead. For example, the pop-up window 3400 informs the user of a location of the incident, distance from a current location of the user, incident details, and/or possible effects on the route calculated by the navigation device. The navigation device should also provide an option 3415 to the user for requesting a new route that avoids the traffic incident. In addition, the navigation device should include an option 3420 to keep the current route, an option 3422 to allow the user to read the incident details, an option 3430 to go to the next traffic incident information, and/or an option 3425 to display all details received for an incident.
More specifically, the embodiment of FIG. 34 provides a method, as diagrammed in FIG. 35. At step 3500, the method calculates a route to a destination. At step 3505, the method receives traffic information (e.g., U.S. traffic information). At step 3510, the method determines whether the received traffic information is referring to roads on the calculated route to the destination. If the received traffic information is not referring to the roads on the calculated route, the method moves back to step 3505. If the received traffic information is referring to the roads on the calculated route, the method displays or shows the traffic information to a user via a map 3410 of the route and a pop-up window 3400 at step 3515. At step 3520, the method determines whether to calculate a new route for the destination to avoid a traffic incident reported using the received traffic information. If the new route is to be calculated, the method moves to step 3500 to calculate the new route to the destination.
An embodiment of the invention reduces the bandwidth requirement for broadcasting traffic information by utilizing a method that does not broadcast free-flow traffic information. Thus, a user of this embodiment only receives traffic information regarding known conditions affecting traffic or only sees traffic information when there is a traffic problem. More specifically, FIG. 36 b shows an embodiment of a display system that displays only traffic information indicating traffic problems and does not show free-flow traffic icons on the display system, as compared with the embodiment shown in FIG. 36 a.
The above-described embodiment for simplifying a display is for exemplary purposes only and the invention is not limited thereby. For example, FIG. 37 shows an alternate embodiment that uses a method that shows free-flow traffic icons by storing the locations of the flow sensors on another medium and cross-referencing with broadcast traffic information data. If no information is received regarding a particular sensor location, the method assumes free-flowing traffic and indicates that particular location with a free-flow icon. More specifically, at step 3700, the method retrieves sensor location information for a sensor. At step 3705, the method receives traffic information associated with the location of the sensor or traffic information from the senor. At step 3710, the method determines whether the received traffic information has data indicating heavy traffic for the location. If the traffic information has data indicating the heavy traffic, the method displays a poor traffic icon at the location of the sensor at step 3715. At step 3720, the method determines whether the received traffic information has data indicating moderate traffic for the location. If the traffic information has data indicating moderate traffic, the method displays a moderate traffic icon at the location of the sensor at step 3725. At step 3730, the method determines whether the received traffic information has data indicating that the sensor is broken. If the traffic information has data indicating that the sensor is broken, the method displays a sensor inoperable icon at the location of the sensor at step 3735. At step 3740, the method determines whether the received traffic information has no data at all. If the traffic information has no data, the method displays a free-flow traffic icon at the location of the sensor at step 3745. Those skilled in the art will appreciate that the above method broadcasts data for indicating broken sensors.
In general, a traffic information report (i.e., a complete national traffic report) is updated at every five (5) minute intervals but broadcast of the traffic information report can occur at a faster cycle (e.g., every minute). FIG. 38 shows an embodiment that adds a header 3800 to each traffic information report pursuant to aspects of the invention. The header 3800 allows the embodiment to skip or filter broadcast reports that the embodiment has already processed. More specifically, the embodiment of FIG. 38 provides a method for adding a header to allow a navigation device to read only updated traffic information in order to reduce a processing requirement of the navigation device, as diagrammed in FIG. 39. At step 3900, a navigation device (e.g., the navigation device 14 shown in FIG. 1 a) receives a traffic report. At step 3905, the navigation device determines if the header of the received traffic report is the same as a previously received header. If the header is the same as the previously received header, the traffic report is discarded at step 3910. If the header is not the same as the previously received header, the navigation device processes the received traffic report at step 3915. It should be appreciated that the above-described mechanisms and process for adding a header to a traffic report are for exemplary purposes only and that the invention is not limited thereby.
In general, when a traffic supplier via a one-to-many network broadcasts traffic information (e.g., U.S. traffic information), a navigation device needs to filter the broadcasted information down to information relating to a specific location of the device or the device would have to receive and process non-related or useless traffic information. FIG. 40 shows an embodiment of a navigation device that uses triangulation of repeaters 4000 a, 4000 b to determine a specific location or position 4010 of the navigation device. In this embodiment, it should be appreciated that the navigation device does not need a GPS navigation system to determine location. More specifically, the embodiment of FIG. 40 provides a method for filtering of traffic information through triangulation of repeaters 4000 a, 4000 b to determine a specific location, as diagrammed in FIG. 41. At step 4105, the method determines whether there is a reception from repeaters 4000 a, 4000 a. In addition, the method may determine whether there is a reception from a satellite 4020. If there is (or are) the necessary reception(s), the method receives a signal or signals from each of the repeaters 4000 a, 4000 b and/or the satellite 4020 at step 4110. The method then calculates a current position 4010 (e.g., a current position of a vehicle) by triangulation at step 4115 and determines the current position 4010 at step 4120.
Once the current position has been determined, the method can then filter traffic information as described in the embodiment shown in FIG. 42. That is, the embodiment may filter the traffic information down to first radius 4200 a and/or a second radius 4200 b of a determined current position 4010. The first radius 4200 a and/or second radius 4200 b can be a five, ten, twenty, and/or thirty mile radius of the current position 4010. More specifically, the embodiment of FIG. 42 provides a method for filtering of traffic information, as diagrammed in FIG. 43. At step 4300, the method determines whether there is a specific radius 4200 a, 4200 b for traffic filtering. If there is the specific radius 4200 a, 4200 b, the method uses the traffic information only inside the parameter of the specific radius 4200 a, 4200 b to filter traffic information at steps 4310 and 4320. If there is no specific radius, the method sets a radius 4200 a, 4200 b to filter at step 4305 and then moves to steps 4310 and 4320.
FIG. 44 shows an embodiment of a method that requires a user to scroll to the needed traffic information in order to reduce display distractions. Specifically, at step 4400, a navigation device (e.g., a navigation device having no GPS) receives filtered traffic information. At step 4405, a user of the navigation device scrolls down a traffic display of the navigation device to select an applicable area (e.g., an applicable freeway). At step 4410, the user selects or picks the applicable area (e.g., the applicable freeway). At step 4420, the user pushes a detail button (e.g., 3425 shown in FIG. 34) on the navigation device and the navigation device list all applicable details of the applicable area at step 4430.
As envisioned, an embodiment of the invention uses four parameters to define specific traffic information for a user in a vehicle. The four parameters are a user's state, metro, county, and city. FIG. 45 shows a method of the present embodiment that determines and filters traffic information for the user based on the four parameters. At step 4520, when a navigation device is in a range of a multiple source data broadcast area, the navigation device calculates approximate position from the delay of the multiple source broadcast signal(s) (e.g., via repeaters 4000 b, 4000 c in FIG. 40). The navigation device then displays (or filters) traffic information of the determined current position (e.g., 4010 in FIGS. 40, 42) of the vehicle at step 4530. However, if the vehicle is out of the range of the multiple source broadcast signal area (i.e., the navigation device can not calculate the current position) then the navigation device displays a candidate area menu to the user at step 4500. At step 4510, the user then selects one or more of the four parameters described above until a desired traffic broadcast information signal is obtained (or filtered). In addition, each broadcasted traffic information of an embodiment may include a header written such that it allows the navigation device to extract information associated with the four parameters. It should be appreciated the addition of the header allows the navigation device to filter out traffic information having headers (e.g., with parameters) not specified by the user. Moreover, if the location information is successfully provided to the user, an embodiment of the invention reduces location header information until the user specifies other parameters so that the provision of redundant header information can be reduced.
FIG. 46 shows an embodiment of a broadcast methodology that reduces the broadcasting of redundant traffic information. More specifically, a navigation device of the embodiment includes a static map 4600 of a metro or a city. A traffic supplier (and/or a remote location) of the embodiment only broadcasts traffic information data 4620 having traffic speed graphic data and a map number. The embodiment does not have to broadcast the static map 4600. In addition, the navigation device includes a filter that displays detailed traffic flow data 4630 around a current position 4610 (e.g., determined via embodiments of FIGS. 40 and 42) on the map 4600 and displays less traffic flow data far from the current position 4600. The current position can be determined by a GPS navigation system. In addition, the increasing traffic-jam portion of the traffic information should have top priority for display in the embodiment and the reducing traffic-jam portion of the traffic information should disappear from the display of the navigation device faster than other traffic jam information in the embodiment. It should be appreciated that the embodiment of FIG. 46 allows a driver to focus on the important information and reduces the amount of driver distractions.
As envisioned in an embodiment of the invention, a user may travel on a route and receive traffic information about a traffic incident and/or a traffic congestion ahead of the route. If the user is unfamiliar with the area of the route, a user may not know how to avoid the traffic incident and/or congestion. FIG. 47 shows an embodiment of a method that provides an option for a user of a navigation device (e.g., 14 in FIG. 1 a) to request a calculation of a new route that will avoid the traffic incident and/or the congestion.
At step 4700 of FIG. 47, the method calculates a route to a destination. At step 4705, the method receives traffic information (e.g., U.S. traffic information). At step 4710, the method displays or shows to a user the traffic information on the current calculated route to the destination. At step 4715, the method determines whether to calculate a new route (or reroute) for the user so that the user can avoid the traffic shown by the traffic information. If the new route is to be calculated, the method calculates the new route at step 4720. If the new route is not to be calculated, the method moves to step 4725 and keeps the current calculated route.
Alternatively, in a case where a user is familiar with the area of the route and goes off-route to avoid the traffic incident and/or congestion, an embodiment of a navigation device of the invention calculates a new route (or recalculate a new route) that avoids the traffic incident and/or the congestion after the user goes off-route. It should be appreciated that this embodiment increases the convenience of the user by providing a recalculation function (e.g., anticipating a user mistake) based on traffic information.
To avoid zigzag routing during a reroute function, an embodiment of the invention provides a method to limit the reroute onto an existing route to avoid zigzagging. More specifically, FIG. 48 b shows an embodiment of the invention that considers factors, such as a vehicle's position, speed, heading, destination, incident severity, time of reported traffic information, and/or estimated time for a traffic to clear, to calculate an optimized route 4810. In addition, the embodiment pursuant to aspects of the invention limits the new optimized route 4810 to no more than two reroutes back to an existing route 4800 within a predetermined distance. This embodiment reduces zigzigging effect of recalculating and returning to the existing route as compared with the embodiment shown in FIG. 48 a.
FIG. 49 shows a method of the embodiment of FIG. 48 b that reduces a zigzagging effect. At step 4900, a navigation device is set at a route guidance mode. At step 4905, the navigation device calculate an existing route 4800. At step 4910, the navigation device receives new traffic information. At step 4915, the navigation device determines whether to reroute a user of the navigation to a new route 4810. If the navigation device calculates the new route 4810 with the new traffic information, the new route 4810 is compared with the existing route 4800 to determine whether the new route 4810 has been rerouted back to the existing route 4800 for more than two times at step 4920. If the route 4810 has been rerouted more than twice back to the existing route 4800, the method moves back to 4925 and maintains the existing route 4800 for the user. If the route 4810 has not been rerouted more than twice back to the existing route 4800, the navigation device displays the new alternative route calculated with the traffic information at step 4930.
Embodiments of the invention use a routing algorithm having a cost function that takes into account road speed, distance, road class, and/or other factors to calculate the cost of taking a certain route (or road) to a destination. Traffic information wherever available can also be used by the routing algorithm to calculate the cost of a road link when finding the best route. An easy method for a routing algorithm to calculate a good route using traffic information is to translate traffic information into an appropriate speed and then substitute this speed into the cost function.
In certain embodiments, some traffic information is already transmitted with a speed value that can be directly substituted into the cost function. However, depending on the location of the traffic information and the lifetime of a specific piece of traffic information, it might not be a good idea to directly substitute the speed into the cost function. For example, there may a fatal accident reported close to San Francisco that has reduced the speed of a major road in San Francisco down to zero (0) mph and at the point of leaving Los Angeles to San Francisco, it usually does not make sense to substitute that speed (i.e., 0 mph) in San Francisco into the cost function to cause the routing algorithm to avoid that road in San Francisco because by the time that the accident location is reached it is very likely that the incident will be cleared. Accordingly, an embodiment of the invention modulates the speed calculated from traffic information to take into account the location of traffic information and/or its expected expiration time.
FIG. 50 shows an embodiment of the invention that provides a method for calculating a distance threshold (DT). The distance threshold (DT), specifies a distance value at which it is likely that traffic information (i.e., a problem location) that exists past this distance value from a current location of a vehicle will expire before the vehicle can reach the traffic problem (i.e., the location reported by the traffic information). In this embodiment, an expiration time should be assigned to each piece of traffic information. This expiration time can be calculated based on historical data for similar types of incidents in similar types of road conditions. As is shown in FIG. 50, the threshold distance (DT) should be calculated such that it increases as the expiration time increases.
FIG. 51 shows an alternate embodiment that provides a method for determining the distance threshold (DT) based on the density of the road network (e.g., the road network is more dense in city areas than in rural areas). The distance threshold (DT) is determined such that it decreases as the road network becomes more dense.
FIG. 52 shows another embodiment of the invention that provides a method for calculating a speed of a link for a route calculation using a distance threshold (DT) from a current vehicle position to the location of the traffic information. For any traffic information that is located within the distance threshold (DT), the speed specified by the traffic information (ST), should be used. Otherwise, if the traffic information lies outside of the threshold distance then the speed included in the onboard database (SDB) should be used for route calculation purposes.
A further embodiment of the invention provides a method in which the speed of a link used by the routing algorithm is calculated by taking into account both the dynamic speed from real-time traffic information (ST) and the static speed stored in a map database (SDB). Traffic information that is located far away from the vehicle's current position should have less effect on routing than information that is close to the vehicle. One way to do this is to calculate the speed of the link as shown FIG. 52 a or 52 b. That is, as shown by the linear process of FIG. 52 a and the non-linear process of 52 b, for traffic information located very close to the current location, the speed from the live traffic information (ST) is used for the link. However, as the location traffic information approaches some threshold distance (DT), the speed of the link should be calculated such that it asymptotically approaches the value of the speed in the database (SDB).
It should be appreciated that the above-described mechanisms and process for using a distance threshold (DT), a dynamic speed from real-time traffic information (ST), and a static speed stored in a map database (SDB) are for exemplary purposes only and that the invention is not limited thereby.
Having thus described a preferred embodiment of a method and system for traffic management between a vehicle and a remote location, it should be apparent to those skilled in the art that certain advantages of the within system have been achieved. It should also be appreciated that various modifications, adaptations, and alternative embodiments thereof may be made within the scope and spirit of the present invention. For example, the use of broadcast communication networks has been illustrated, but it should be apparent that many of the inventive concepts described above would be equally applicable to the use of other non-broadcast communication networks.

Claims (23)

1. A vehicle navigation system providing a travel route to a user of a vehicle based on traffic information received from a remotely located supplier, comprising:
a navigation device including a processor, a memory unit, and a receiver adapted to receive the traffic information; and
an owner link device located outside the vehicle enabling manual entry of a commute preference by the user and in communication with said navigation device to transmit the commute preference thereto;
wherein said processor filters the received traffic information to extract a subset of the received traffic information based at least in part on the commute preference, discards an unextracted portion of the received traffic information, and calculates the travel route based at least in part on the extracted traffic information.
2. The system as recited in claim 1, wherein said commute preference is stored in said memory unit.
3. The system as recited in claim 2, wherein said receiver receives traffic information from the remote location based at least in part on the commute preference.
4. The system as recited in claim 1, wherein said owner link device comprises a computer.
5. The system as recited in claim 1, wherein said owner link device comprises a personal digital assistant.
6. The system as recited in claim 1, wherein said navigation device is located in the vehicle.
7. The system as recited in claim 6, wherein said owner link device transmits the commute preference to said navigation device before the user enters the vehicle.
8. The system as recited in claim 1, wherein said owner link device transmits the commute preference via a wireless communication network.
9. The system as recited in claim 1, wherein said owner link device transmits the commute preference via a satellite communication network.
10. The system as recited in claim 1, wherein the commute preference comprises a destination address.
11. The system as recited in claim 1, wherein the commute preference comprises a time that a user of the navigation device begins travel.
12. The system as recited in claim 1, wherein the commute preference comprises a travel route that a user of the navigation device prefers to travel along between a first location and a second location.
13. The system as recited in claim 1, wherein said navigation device further includes a visual display screen.
14. The system as recited in claim 13, wherein said visual display screen includes touch-sensitive pads enabling user entry of the commute preference.
15. A vehicle navigation device providing a travel route to a user and receiving traffic information from a remote location, comprising:
a processor;
a receiver operatively coupled to said processor and adapted to receive the traffic information from the remote location;
a visual display screen operatively coupled to said processor and having touch-sensitive pads enabling user entry of a commute preference; and
a memory unit operatively coupled to said processor and adapted to store the commute preference;
wherein said processor filters the received traffic information to extract a subset of the received traffic information based at least in part on the commute preference, discards an unextracted portion of the received traffic information, and calculates the travel route based at least in part on the extracted traffic information.
16. The device as recited in claim 15, further comprising a position detection device.
17. The device as recited in claim 16, wherein said position detection device comprises a satellite navigation system.
18. A method for providing personalized traffic information to a user of a vehicle navigation system that receives traffic information from a remote location, comprising the steps of:
(a) receiving a commute preference from the user;
(b) receiving traffic information from the remote location;
(c) filtering the received traffic information to extract a subset of the received traffic information based at least in part on the commute preference and to discard an unextracted portion of the received traffic information;
(d) calculating a travel route, based at least in part on the extracted traffic information in said step (c); and
(e) displaying the travel route calculated in said step (d);
wherein said step (a) further comprises receiving the commute preference via a wireless communication network.
19. A method for providing personalized traffic information to a user of a vehicle navigation system that receives traffic information from a remote location, comprising the steps of:
(a) receiving a commute preference from the user;
(b) receiving traffic information from the remote location;
(c) filtering the received traffic information to extract a subset of the received traffic information based at least in part on the commute preference and to discard an unextracted portion of the received traffic information;
(d) calculating a travel route, based at least in part on the extracted traffic information in said step (c); and
(e) displaying the travel route calculated in said step (d);
wherein said step (a) further comprises receiving the commute preference via a satellite communication network.
20. A method for providing personalized traffic information to a user of a vehicle navigation system that receives traffic information from a remote location, comprising the steps of:
(a) receiving a commute preference from the user;
(b) receiving traffic information from the remote location;
(c) filtering the received traffic information to extract a subset of the received traffic information based at least in part on the commute preference and to discard an unextracted portion of the received traffic information; (d) calculating a travel route, based at least in part on the extracted traffic information in said step (c); and
(e) displaying the travel route calculated in said step (d);
wherein said step (b) further comprises receiving the traffic information via a satellite communication network.
21. A method for providing traffic information to a user of a vehicle navigation system that receives traffic information from a remotely located supplier, comprising the steps of:
(a) establishing a commute pattern of the user;
(b) receiving traffic information from the supplier, based at least in part on the commute pattern established in said step (a);
(c) receiving at least one commute preference from the user;
(d) filtering the received traffic information to extract a subset of the received traffic information based at least in part on the at least one commute preference and to discard an unextracted portion of the received traffic information;
(e) calculating a travel route, based at least in part on the extracted traffic information in said step (d); and
(f) displaying the travel route calculated in said step (e);
wherein establishing a commute pattern in said step (a) comprises storing a plurality of addresses that the user has visited.
22. A method for providing traffic information to a user of a vehicle navigation system that receives traffic information from a remotely located supplier, comprising the steps of:
(a) establishing a commute pattern of the user;
(b) receiving traffic information from the supplier, based at least in part on the commute pattern established in said step (a);
(c) receiving at least one commute preference from the user;
(d) filtering the received traffic information to extract a subset of the received traffic information based at least in part on the at least one commute preference and to discard an unextracted portion of the received traffic information;
(e) calculating a travel route, based at least in part on the extracted traffic information in said step (d); and
(f) displaying the travel route calculated in said step (e);
wherein steps (a) through (e) are completed before the user enters the vehicle.
23. A method for providing traffic information to a user of a vehicle navigation system that receives traffic information from a remotely located supplier, comprising the steps of:
(a) establishing a commute pattern of the user;
(b) receiving traffic information from the supplier, based at least in part on the commute pattern established in said step (a);
(c) receiving at least one commute preference from the user;
(d) filtering the received traffic information to extract a subset of the received traffic information based at least in part on the at least one commute preference and to discard an unextracted portion of the received traffic information;
(e) calculating a travel route, based at least in part on the extracted traffic information in said step (d); and
(f) displaying the travel route calculated in said step (e);
wherein establishing a commute pattern in said step (a) comprises storing a plurality of addresses that the user has visited;
wherein traffic information is received in said step (b) when the vehicle navigation system is located within a predetermined distance from each one of the plurality of addresses stored in said step (a).
US11/040,710 2004-04-06 2005-01-21 Vehicle navigation system and methods for incorporating user preferences into same Active 2025-04-20 US7289904B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/040,710 US7289904B2 (en) 2004-04-06 2005-01-21 Vehicle navigation system and methods for incorporating user preferences into same

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US56008704P 2004-04-06 2004-04-06
US11/040,710 US7289904B2 (en) 2004-04-06 2005-01-21 Vehicle navigation system and methods for incorporating user preferences into same

Publications (2)

Publication Number Publication Date
US20050222763A1 US20050222763A1 (en) 2005-10-06
US7289904B2 true US7289904B2 (en) 2007-10-30

Family

ID=35055465

Family Applications (1)

Application Number Title Priority Date Filing Date
US11/040,710 Active 2025-04-20 US7289904B2 (en) 2004-04-06 2005-01-21 Vehicle navigation system and methods for incorporating user preferences into same

Country Status (1)

Country Link
US (1) US7289904B2 (en)

Cited By (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050137795A1 (en) * 2002-04-03 2005-06-23 Kiyomi Sakamoto Navigation system
US20060173618A1 (en) * 2005-02-01 2006-08-03 Mark Eyer Intelligent travel assistant
US20060238380A1 (en) * 2005-04-21 2006-10-26 Microsoft Corporation Maintaining user privacy in a virtual earth environment
US20060238383A1 (en) * 2005-04-21 2006-10-26 Microsoft Corporation Virtual earth rooftop overlay and bounding
US20070150175A1 (en) * 2005-12-12 2007-06-28 Microsoft Corporation Augmented navigation system
US20070210937A1 (en) * 2005-04-21 2007-09-13 Microsoft Corporation Dynamic rendering of map information
US20070225902A1 (en) * 2004-03-15 2007-09-27 Tomtom International B.V. Navigation Device Displaying Dynamic Travel Information
US20070273558A1 (en) * 2005-04-21 2007-11-29 Microsoft Corporation Dynamic map rendering as a function of a user parameter
US20080167804A1 (en) * 2007-01-10 2008-07-10 Pieter Geelen Traffic delay indication
US20080215236A1 (en) * 2007-01-10 2008-09-04 William Deurwaarder Navigation device and method for using a traffic message channel
US20100114485A1 (en) * 2008-11-06 2010-05-06 Bhogal Kulvir S Providing Popular Global Positioning Satelite (GPS) Routes
US20100118025A1 (en) * 2005-04-21 2010-05-13 Microsoft Corporation Mode information displayed in a mapping application
US20100216402A1 (en) * 2009-02-26 2010-08-26 International Business Machines Corporation Proximity based smart collaboration
US20110130962A1 (en) * 2009-12-02 2011-06-02 Larry Damell Lindsey Navigation system for delivery vehicles
US20110153191A1 (en) * 2009-12-18 2011-06-23 Telenav, Inc. Navigation system with location profiling and method of operation thereof
US8121777B2 (en) 2008-03-07 2012-02-21 Microsoft Corporation Wireless broadcasting of drive-times data
US20120158283A1 (en) * 2010-12-16 2012-06-21 Research In Motion Limited Changing Frequency of Navigational Notifications Based On Travel Patterns
US8345835B1 (en) 2011-07-20 2013-01-01 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8385964B2 (en) 2005-04-04 2013-02-26 Xone, Inc. Methods and apparatuses for geospatial-based sharing of information by multiple devices
US8406388B2 (en) 2011-07-18 2013-03-26 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8452771B2 (en) 2011-01-03 2013-05-28 Honda Motor Co., Ltd. Method for differentiating traffic data obtained from probe vehicles
TWI404916B (en) * 2009-05-08 2013-08-11 Mitac Int Corp Methods of creating and playing customizable audio alerts and related devices
US8537989B1 (en) 2010-02-03 2013-09-17 Tal Lavian Device and method for providing enhanced telephony
US8548135B1 (en) 2010-02-03 2013-10-01 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8548131B1 (en) 2010-02-03 2013-10-01 Tal Lavian Systems and methods for communicating with an interactive voice response system
US8553859B1 (en) 2010-02-03 2013-10-08 Tal Lavian Device and method for providing enhanced telephony
US8572303B2 (en) 2010-02-03 2013-10-29 Tal Lavian Portable universal communication device
US8583367B2 (en) 2011-01-07 2013-11-12 Honda Motor Co., Ltd. System and method for displaying a route based on a vehicle state
US8594280B1 (en) 2010-02-03 2013-11-26 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8625756B1 (en) 2010-02-03 2014-01-07 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8681951B1 (en) 2010-02-03 2014-03-25 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8687777B1 (en) 2010-02-03 2014-04-01 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8700327B2 (en) 2010-04-27 2014-04-15 Honda Motor Co., Ltd. Method of determining routes for use in navigation
US8706458B2 (en) * 2011-10-05 2014-04-22 International Business Machines Corporation Traffic sensor management
US8731148B1 (en) 2012-03-02 2014-05-20 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8867708B1 (en) 2012-03-02 2014-10-21 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8879698B1 (en) 2010-02-03 2014-11-04 Tal Lavian Device and method for providing enhanced telephony
US9001819B1 (en) 2010-02-18 2015-04-07 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US9123345B2 (en) 2013-03-14 2015-09-01 Honda Motor Co., Ltd. Voice interface systems and methods
US20160091333A1 (en) * 2014-09-25 2016-03-31 International Business Machines Corporation Travel routes based on communication channel availability
US9612128B2 (en) 2015-04-29 2017-04-04 Microsoft Technology Licensing, Llc Controlling travel route planning module based upon user travel preference
US9696173B2 (en) 2014-12-10 2017-07-04 Red Hat, Inc. Providing an instruction notification for navigation
US9739632B2 (en) 2012-10-17 2017-08-22 Tomtom Navigation B.V. Methods and systems of providing information using a navigation apparatus
US10612935B2 (en) 2012-10-17 2020-04-07 Tomtom Navigation B.V. Methods and systems of providing information using a navigation apparatus

Families Citing this family (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4561139B2 (en) * 2004-03-22 2010-10-13 アイシン・エィ・ダブリュ株式会社 Navigation system
US7680596B2 (en) 2004-04-06 2010-03-16 Honda Motor Co., Ltd. Route calculation method for a vehicle navigation system
US7680594B2 (en) 2004-04-06 2010-03-16 Honda Motor Co., Ltd. Display method and system for a vehicle navigation system
US7671764B2 (en) * 2004-04-06 2010-03-02 Honda Motor Co., Ltd. Method and system for using traffic flow data to navigate a vehicle to a destination
TWI258719B (en) * 2005-05-02 2006-07-21 Mitac Int Corp Driving route planning system and method
KR100754690B1 (en) * 2006-02-22 2007-09-03 삼성전자주식회사 Method and apparatus for setting destination in navigation terminal
US7912628B2 (en) 2006-03-03 2011-03-22 Inrix, Inc. Determining road traffic conditions using data from multiple data sources
US7912627B2 (en) * 2006-03-03 2011-03-22 Inrix, Inc. Obtaining road traffic condition data from mobile data sources
US8014936B2 (en) * 2006-03-03 2011-09-06 Inrix, Inc. Filtering road traffic condition data obtained from mobile data sources
JP4050309B2 (en) * 2006-05-16 2008-02-20 松下電器産業株式会社 Traffic information providing apparatus, method, and program
US8068981B2 (en) * 2006-05-26 2011-11-29 C.R.F. Societa Consortile Per Azioni Off-board navigation system for vehicles
US8073681B2 (en) 2006-10-16 2011-12-06 Voicebox Technologies, Inc. System and method for a cooperative conversational voice user interface
US7818176B2 (en) 2007-02-06 2010-10-19 Voicebox Technologies, Inc. System and method for selecting and presenting advertisements based on natural language processing of voice-based input
JP4623050B2 (en) * 2007-04-25 2011-02-02 アイシン・エィ・ダブリュ株式会社 Road information generation apparatus, road information generation method, and road information generation program
US8175802B2 (en) * 2007-06-28 2012-05-08 Apple Inc. Adaptive route guidance based on preferences
US8332402B2 (en) 2007-06-28 2012-12-11 Apple Inc. Location based media items
US9109904B2 (en) 2007-06-28 2015-08-18 Apple Inc. Integration of map services and user applications in a mobile device
US8108144B2 (en) 2007-06-28 2012-01-31 Apple Inc. Location based tracking
US8290513B2 (en) 2007-06-28 2012-10-16 Apple Inc. Location-based services
US8762056B2 (en) 2007-06-28 2014-06-24 Apple Inc. Route reference
US8204684B2 (en) 2007-06-28 2012-06-19 Apple Inc. Adaptive mobile device navigation
US8385946B2 (en) 2007-06-28 2013-02-26 Apple Inc. Disfavored route progressions or locations
US8275352B2 (en) 2007-06-28 2012-09-25 Apple Inc. Location-based emergency information
US8774825B2 (en) 2007-06-28 2014-07-08 Apple Inc. Integration of map services with user applications in a mobile device
US8180379B2 (en) 2007-06-28 2012-05-15 Apple Inc. Synchronizing mobile and vehicle devices
US8311526B2 (en) 2007-06-28 2012-11-13 Apple Inc. Location-based categorical information services
US9066199B2 (en) 2007-06-28 2015-06-23 Apple Inc. Location-aware mobile device
US8099308B2 (en) 2007-10-02 2012-01-17 Honda Motor Co., Ltd. Method and system for vehicle service appointments based on diagnostic trouble codes
US8140335B2 (en) 2007-12-11 2012-03-20 Voicebox Technologies, Inc. System and method for providing a natural language voice user interface in an integrated voice navigation services environment
US8355862B2 (en) 2008-01-06 2013-01-15 Apple Inc. Graphical user interface for presenting location information
US9250092B2 (en) 2008-05-12 2016-02-02 Apple Inc. Map service with network-based query for search
US8855899B2 (en) * 2008-05-15 2014-10-07 Garmin Switzerland Gmbh Virtual traffic sensors
US8644843B2 (en) 2008-05-16 2014-02-04 Apple Inc. Location determination
US9305548B2 (en) 2008-05-27 2016-04-05 Voicebox Technologies Corporation System and method for an integrated, multi-modal, multi-device natural language voice services environment
CA2726103A1 (en) * 2008-06-24 2009-12-30 Tele Atlas North America Inc. Methods and systems for dynamically adaptive road network hierarchy and routing
US8369867B2 (en) 2008-06-30 2013-02-05 Apple Inc. Location sharing
US8359643B2 (en) 2008-09-18 2013-01-22 Apple Inc. Group formation using anonymous broadcast information
US8260320B2 (en) 2008-11-13 2012-09-04 Apple Inc. Location specific content
US8326637B2 (en) 2009-02-20 2012-12-04 Voicebox Technologies, Inc. System and method for processing multi-modal device interactions in a natural language voice services environment
US8666367B2 (en) 2009-05-01 2014-03-04 Apple Inc. Remotely locating and commanding a mobile device
US8660530B2 (en) 2009-05-01 2014-02-25 Apple Inc. Remotely receiving and communicating commands to a mobile device for execution by the mobile device
US8670748B2 (en) 2009-05-01 2014-03-11 Apple Inc. Remotely locating and commanding a mobile device
US8135804B2 (en) 2009-07-07 2012-03-13 Honda Motor Co., Ltd. Method for scheduling and rescheduling vehicle service appointments
US9638537B2 (en) 2012-06-21 2017-05-02 Cellepathy Inc. Interface selection in navigation guidance systems
US20150168174A1 (en) * 2012-06-21 2015-06-18 Cellepathy Ltd. Navigation instructions
WO2013190380A2 (en) 2012-06-21 2013-12-27 Cellepathy Ltd. Device context determination
US9772196B2 (en) 2013-08-23 2017-09-26 Cellepathy Inc. Dynamic navigation instructions
EP3036924A4 (en) 2013-08-23 2017-04-12 Cellepathy Ltd. Mobile device context aware determinations
WO2016044290A1 (en) 2014-09-16 2016-03-24 Kennewick Michael R Voice commerce
WO2016044321A1 (en) 2014-09-16 2016-03-24 Min Tang Integration of domain information into state transitions of a finite state transducer for natural language processing
US9747896B2 (en) 2014-10-15 2017-08-29 Voicebox Technologies Corporation System and method for providing follow-up responses to prior natural language inputs of a user
US10431214B2 (en) 2014-11-26 2019-10-01 Voicebox Technologies Corporation System and method of determining a domain and/or an action related to a natural language input
US10614799B2 (en) 2014-11-26 2020-04-07 Voicebox Technologies Corporation System and method of providing intent predictions for an utterance prior to a system detection of an end of the utterance
JP6529429B2 (en) * 2015-12-22 2019-06-12 本田技研工業株式会社 Traffic information output system and traffic information output method
CN107228677B (en) * 2016-03-23 2019-03-26 腾讯科技(深圳)有限公司 Yaw recognition methods and device
CN105825699B (en) * 2016-05-24 2018-09-18 腾讯科技(深圳)有限公司 Road conditions display methods and device
WO2018023106A1 (en) 2016-07-29 2018-02-01 Erik SWART System and method of disambiguating natural language processing requests
US11513537B2 (en) * 2019-05-09 2022-11-29 Toyota Motor Eng & Mfg North America, Inc. Managing drones in vehicular system

Citations (101)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5173691A (en) 1990-07-26 1992-12-22 Farradyne Systems, Inc. Data fusion process for an in-vehicle traffic congestion information system
US5182555A (en) 1990-07-26 1993-01-26 Farradyne Systems, Inc. Cell messaging process for an in-vehicle traffic congestion information system
US5303401A (en) 1989-11-03 1994-04-12 Robert Bosch Gmbh RDS receiver with automatic region recognition
US5406490A (en) 1990-03-16 1995-04-11 Robert Bosch Gmbh Navigation system responsive to traffic bulletins
US5465088A (en) 1992-03-13 1995-11-07 Robert Bosch Gmbh Receiver for traffic messages
US5608635A (en) 1992-04-14 1997-03-04 Zexel Corporation Navigation system for a vehicle with route recalculation between multiple locations
US5636245A (en) 1994-08-10 1997-06-03 The Mitre Corporation Location based selective distribution of generally broadcast information
US5635924A (en) 1996-03-29 1997-06-03 Loral Aerospace Corp. Travel route information monitor
US5649300A (en) 1994-04-13 1997-07-15 Rotec, A Nevada General Partnership Message delivery system and method therefor
US5648768A (en) 1994-12-30 1997-07-15 Mapsys, Inc. System and method for identifying, tabulating and presenting information of interest along a travel route
US5682525A (en) 1995-01-11 1997-10-28 Civix Corporation System and methods for remotely accessing a selected group of items of interest from a database
US5699056A (en) 1994-12-28 1997-12-16 Omron Corporation Traffic information system
US5774827A (en) 1996-04-03 1998-06-30 Motorola Inc. Commuter route selection system
US5822712A (en) 1992-11-19 1998-10-13 Olsson; Kjell Prediction method of traffic parameters
US5842146A (en) 1996-05-10 1998-11-24 Honda Giken Kogyo Kabushiki Kaisha Method and apparatus of setting clock time and using time data in a vehicle navigation system
US5862510A (en) 1995-09-06 1999-01-19 Mitsubishi Jidosha Kogyo Kabushiki Kaisha Navigation device
US5864305A (en) 1994-03-04 1999-01-26 Ab Volvo Traffic information system
US5892463A (en) 1996-09-05 1999-04-06 Mitsubishi Denki Kabushiki Kaisha Mobile navigation system
US5911773A (en) 1995-07-24 1999-06-15 Aisin Aw Co., Ltd. Navigation system for vehicles
US5928307A (en) 1997-01-15 1999-07-27 Visteon Technologies, Llc Method and apparatus for determining an alternate route in a vehicle navigation system
US5959577A (en) 1997-08-28 1999-09-28 Vectorlink, Inc. Method and structure for distribution of travel information using network
US5982298A (en) 1996-11-14 1999-11-09 Microsoft Corporation Interactive traffic display and trip planner
US5999882A (en) 1997-06-04 1999-12-07 Sterling Software, Inc. Method and system of providing weather information along a travel route
US6078865A (en) 1996-10-17 2000-06-20 Xanavi Informatics Corporation Navigation system for guiding a mobile unit through a route to a destination using landmarks
US6085146A (en) 1997-04-24 2000-07-04 Sony Corporation Information receiving method, navigation apparatus and motorcar
US6111521A (en) 1996-09-18 2000-08-29 Mannesmann Vdo Ag Apparatus for supplying traffic-related information
US6163751A (en) 1996-10-26 2000-12-19 Mannesmann Vdo Ag Navigation system for a vehicle
US6169894B1 (en) 1998-11-25 2001-01-02 Lucent Technologies, Inc. Apparatus, method and system for mobile broadcast of information specific to a geographic region
US6178378B1 (en) * 1998-05-23 2001-01-23 General Motors Corporation Method for operating a navigation system for motor vehicles
US6204778B1 (en) 1998-05-15 2001-03-20 International Road Dynamics Inc. Truck traffic monitoring and warning systems and vehicle ramp advisory system
US6208935B1 (en) 1998-05-01 2001-03-27 Hitachi, Ltd. Map application system
US6208932B1 (en) 1996-09-30 2001-03-27 Mazda Motor Corporation Navigation apparatus
US20010001848A1 (en) 1998-06-25 2001-05-24 Hidekazu Oshizawa Vehicle navigation system providing traffic advisories based on traffic information and learned route
US6240364B1 (en) 1999-02-06 2001-05-29 Daimlerchrysler Ag Method and device for providing traffic information
US6253146B1 (en) 1999-12-06 2001-06-26 At&T Corp. Network-based traffic congestion notification service
US6255963B1 (en) 1997-02-04 2001-07-03 Mannesmann Ag Method for transmitting traffic information and devices for implementing said method
US6266608B1 (en) 1998-10-16 2001-07-24 Nokia Mobile Phones Limited Method and apparatus for the selection of traffic information for a motor vehicle
US6266607B1 (en) 1996-12-16 2001-07-24 Mannesmann Ag Process for selecting the traffic information transmitted by a traffic information center which concerns a route of a vehicle equipped with a terminal in a road network
US6298302B2 (en) 1997-07-01 2001-10-02 Mannesman Vdo Navigation system for providing an optimal route from traffic messages
US20010029425A1 (en) 2000-03-17 2001-10-11 David Myr Real time vehicle guidance and traffic forecasting system
US6317685B1 (en) 2000-03-13 2001-11-13 Navigation Technologies Corp. Method and system for providing alternate routes with a navigation system
US6317686B1 (en) 2000-07-21 2001-11-13 Bin Ran Method of providing travel time
US6321158B1 (en) * 1994-06-24 2001-11-20 Delorme Publishing Company Integrated routing/mapping information
US20020016655A1 (en) 2000-08-01 2002-02-07 Joao Raymond Anthony Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information
US6349211B2 (en) 1995-07-25 2002-02-19 Ace K Computer Co., Ltd. Position display system of mobile terminal
US6349261B1 (en) 1999-03-08 2002-02-19 Navitime Japan Co., Ltd. Method and apparatus for determining route within traffic network
US6351709B2 (en) 1998-12-02 2002-02-26 Lear Automotive Dearborn, Inc. Vehicle navigation system with route updating feature
US6370454B1 (en) 2000-02-25 2002-04-09 Edwin S. Moore Iii Apparatus and method for monitoring and maintaining mechanized equipment
US6438490B2 (en) 1998-04-28 2002-08-20 Xanavi Informatics Corporation Route searching device
US6453230B1 (en) 1997-12-02 2002-09-17 Mannesmann Vdo Ag Apparatus for handling a traffic message
US6480783B1 (en) 2000-03-17 2002-11-12 Makor Issues And Rights Ltd. Real time vehicle guidance and forecasting system under traffic jam conditions
US6522250B1 (en) 2001-08-14 2003-02-18 The Mitre Corporation Movement history based selective distribution of generally broadcast information
US6526335B1 (en) 2000-01-24 2003-02-25 G. Victor Treyz Automobile personal computer systems
US6529143B2 (en) 1998-10-23 2003-03-04 Nokia Mobile Phones Ltd. Information retrieval system
US6539302B1 (en) 2000-09-06 2003-03-25 Navigation Technologies Corporation Method, system, and article of manufacture for providing notification of traffic conditions
US6542822B1 (en) 2001-07-24 2003-04-01 Trimble Navigation Limited Directed user-based dynamic advertising
US6546333B2 (en) 2000-08-01 2003-04-08 Sony Corporation Car navigation apparatus, traffic information providing apparatus, program recording medium for car navigation apparatus, and program recording medium for traffic information providing apparatus
US6549833B2 (en) 2001-05-08 2003-04-15 Hitachi, Ltd. Repair and maintenance support system and a car corresponding to the system
US6553313B1 (en) 2001-07-24 2003-04-22 Trimble Navigation Limited Method and system for updating directed user-based dynamic advertising
US6552682B1 (en) 1997-08-28 2003-04-22 At Road, Inc. Method for distributing location-relevant information using a network
US6583734B2 (en) 2001-07-18 2003-06-24 International Business Machines Corporation Enhanced vehicle hazard warning and safety features integrated with an onboard navigation system
US6584401B2 (en) * 2001-11-27 2003-06-24 Hewlett-Packard Development Company, Lp. Automatic gathering and analysis of data on commute paths
US6587785B2 (en) 2001-09-21 2003-07-01 General Motors Corporation Method and system for mobile vehicle re-routing
US6587777B1 (en) 2000-10-23 2003-07-01 Sun Microsystems, Inc. System and method for location based traffic reporting
US6587787B1 (en) 2000-03-15 2003-07-01 Alpine Electronics, Inc. Vehicle navigation system apparatus and method providing enhanced information regarding geographic entities
US6590507B2 (en) 2001-03-05 2003-07-08 Hrl Laboratories, Llc Method and system for providing personalized traffic alerts
US6591188B1 (en) * 2000-11-01 2003-07-08 Navigation Technologies Corp. Method, system and article of manufacture for identifying regularly traveled routes
US6594576B2 (en) 2001-07-03 2003-07-15 At Road, Inc. Using location data to determine traffic information
US6603405B2 (en) 2000-12-05 2003-08-05 User-Centric Enterprises, Inc. Vehicle-centric weather prediction system and method
US6611753B1 (en) 1998-04-17 2003-08-26 Magellan Dis, Inc. 3-dimensional intersection display for vehicle navigation system
US6615133B2 (en) * 2001-02-27 2003-09-02 International Business Machines Corporation Apparatus, system, method and computer program product for determining an optimum route based on historical information
US6618669B2 (en) 2001-04-12 2003-09-09 Mitsubishi Denki Kabushiki Kaisha Navigation apparatus, navigation method and navigation program
US6622083B1 (en) * 1999-06-01 2003-09-16 Siemens Vdo Automotive Corporation Portable driver information device
US6622087B2 (en) * 2000-12-26 2003-09-16 Intel Corporation Method and apparatus for deriving travel profiles
US6650948B1 (en) 2000-11-28 2003-11-18 Applied Generics Limited Traffic flow monitoring
US6657558B2 (en) 1999-08-31 2003-12-02 Hitachi, Ltd. Broadcasting system, broadcast receiving hardware systems, and navigation terminal
US6664922B1 (en) 1997-08-28 2003-12-16 At Road, Inc. Method for distributing location-relevant information using a network
US6680694B1 (en) 1997-08-19 2004-01-20 Siemens Vdo Automotive Corporation Vehicle information system
US6680674B1 (en) 1994-04-13 2004-01-20 Seiko Instruments Inc. Adaptive geographic mapping in vehicle information systems
US6707421B1 (en) 1997-08-19 2004-03-16 Siemens Vdo Automotive Corporation Driver information system
US6730940B1 (en) 2002-10-29 2004-05-04 Lumileds Lighting U.S., Llc Enhanced brightness light emitting device spot emitter
US6741188B1 (en) 1999-10-22 2004-05-25 John M. Miller System for dynamically pushing information to a user utilizing global positioning system
US6760661B2 (en) 2000-08-25 2004-07-06 Siemens Aktiengesellschaft Method for operating a navigation appliance, and arrangement for carrying out the method
US6785606B2 (en) 1999-04-19 2004-08-31 Dekock Bruce W. System for providing traffic information
US6785551B1 (en) 2000-04-07 2004-08-31 Ford Motor Company Method of providing dynamic regionally relevant data to a mobile environment
US6798358B2 (en) 2001-07-03 2004-09-28 Nortel Networks Limited Location-based content delivery
US6810323B1 (en) 2000-09-25 2004-10-26 Motorola, Inc. System and method for storing and using information associated with geographic locations of interest to a mobile user
US6810328B2 (en) 2002-11-23 2004-10-26 Alpine Electronics, Inc Navigation method and system for indicating area-specific traffic information
US6812860B1 (en) 2000-03-22 2004-11-02 Ford Global Technologies, Llc System and method of providing information to an onboard information device in a vehicle
US6823263B1 (en) 2000-04-12 2004-11-23 Weather Central, Inc. System and method for providing personalized weather reports and the like
US6836667B1 (en) 2000-09-19 2004-12-28 Lucent Technologies Inc. Method and apparatus for a wireless telecommunication system that provides location-based messages
US6850842B2 (en) 2001-10-31 2005-02-01 Samsung Electronics Co., Ltd. Navigation system for providing real-time traffic information and traffic information processing method by the same
US20050027442A1 (en) * 2003-07-31 2005-02-03 Kelley Edward E. Agenda replicator system and method for travelers
US6859728B2 (en) 2002-04-03 2005-02-22 Matsushita Electric Industrial Co., Ltd. Navigation system
US6859720B2 (en) 2002-03-26 2005-02-22 Alpine Electronics, Inc. Traffic-information distribution method on-vehicle navigation apparatus
US6859726B2 (en) 2003-02-08 2005-02-22 Samsung Electronics Co., Ltd. Navigation apparatus and method for calculating optimum travel route using the same
US6868331B2 (en) 1999-03-01 2005-03-15 Nokia Mobile Phones, Ltd. Method for outputting traffic information in a motor vehicle
US6973384B2 (en) * 2001-12-06 2005-12-06 Bellsouth Intellectual Property Corporation Automated location-intelligent traffic notification service systems and methods
US7006903B2 (en) 2002-02-28 2006-02-28 Sabre Inc. Method and system for routing mobile vehicles and scheduling maintenance for those vehicles related application
US7096115B1 (en) 2003-09-23 2006-08-22 Navteq North America, Llc Method and system for developing traffic messages
US7155376B2 (en) 2001-06-22 2006-12-26 Caliper Corporation Traffic data management and simulation system

Patent Citations (108)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5303401A (en) 1989-11-03 1994-04-12 Robert Bosch Gmbh RDS receiver with automatic region recognition
US5406490A (en) 1990-03-16 1995-04-11 Robert Bosch Gmbh Navigation system responsive to traffic bulletins
US5182555A (en) 1990-07-26 1993-01-26 Farradyne Systems, Inc. Cell messaging process for an in-vehicle traffic congestion information system
US5173691A (en) 1990-07-26 1992-12-22 Farradyne Systems, Inc. Data fusion process for an in-vehicle traffic congestion information system
US5465088A (en) 1992-03-13 1995-11-07 Robert Bosch Gmbh Receiver for traffic messages
US5608635A (en) 1992-04-14 1997-03-04 Zexel Corporation Navigation system for a vehicle with route recalculation between multiple locations
US5822712A (en) 1992-11-19 1998-10-13 Olsson; Kjell Prediction method of traffic parameters
US5864305A (en) 1994-03-04 1999-01-26 Ab Volvo Traffic information system
US5649300A (en) 1994-04-13 1997-07-15 Rotec, A Nevada General Partnership Message delivery system and method therefor
US6680674B1 (en) 1994-04-13 2004-01-20 Seiko Instruments Inc. Adaptive geographic mapping in vehicle information systems
US6321158B1 (en) * 1994-06-24 2001-11-20 Delorme Publishing Company Integrated routing/mapping information
US5636245A (en) 1994-08-10 1997-06-03 The Mitre Corporation Location based selective distribution of generally broadcast information
US5699056A (en) 1994-12-28 1997-12-16 Omron Corporation Traffic information system
US5648768A (en) 1994-12-30 1997-07-15 Mapsys, Inc. System and method for identifying, tabulating and presenting information of interest along a travel route
US6408307B1 (en) 1995-01-11 2002-06-18 Civix-Ddi, Llc System and methods for remotely accessing a selected group of items of interest from a database
US5682525A (en) 1995-01-11 1997-10-28 Civix Corporation System and methods for remotely accessing a selected group of items of interest from a database
US5911773A (en) 1995-07-24 1999-06-15 Aisin Aw Co., Ltd. Navigation system for vehicles
US6349211B2 (en) 1995-07-25 2002-02-19 Ace K Computer Co., Ltd. Position display system of mobile terminal
US5862510A (en) 1995-09-06 1999-01-19 Mitsubishi Jidosha Kogyo Kabushiki Kaisha Navigation device
US5635924A (en) 1996-03-29 1997-06-03 Loral Aerospace Corp. Travel route information monitor
US5774827A (en) 1996-04-03 1998-06-30 Motorola Inc. Commuter route selection system
US5842146A (en) 1996-05-10 1998-11-24 Honda Giken Kogyo Kabushiki Kaisha Method and apparatus of setting clock time and using time data in a vehicle navigation system
US5892463A (en) 1996-09-05 1999-04-06 Mitsubishi Denki Kabushiki Kaisha Mobile navigation system
US6111521A (en) 1996-09-18 2000-08-29 Mannesmann Vdo Ag Apparatus for supplying traffic-related information
US6208932B1 (en) 1996-09-30 2001-03-27 Mazda Motor Corporation Navigation apparatus
US6078865A (en) 1996-10-17 2000-06-20 Xanavi Informatics Corporation Navigation system for guiding a mobile unit through a route to a destination using landmarks
US6163751A (en) 1996-10-26 2000-12-19 Mannesmann Vdo Ag Navigation system for a vehicle
US6297748B1 (en) 1996-11-14 2001-10-02 Microsoft Corporation Interactive traffic display and trip planner
US5982298A (en) 1996-11-14 1999-11-09 Microsoft Corporation Interactive traffic display and trip planner
US6266607B1 (en) 1996-12-16 2001-07-24 Mannesmann Ag Process for selecting the traffic information transmitted by a traffic information center which concerns a route of a vehicle equipped with a terminal in a road network
US5928307A (en) 1997-01-15 1999-07-27 Visteon Technologies, Llc Method and apparatus for determining an alternate route in a vehicle navigation system
US6255963B1 (en) 1997-02-04 2001-07-03 Mannesmann Ag Method for transmitting traffic information and devices for implementing said method
US6085146A (en) 1997-04-24 2000-07-04 Sony Corporation Information receiving method, navigation apparatus and motorcar
US5999882A (en) 1997-06-04 1999-12-07 Sterling Software, Inc. Method and system of providing weather information along a travel route
US6298302B2 (en) 1997-07-01 2001-10-02 Mannesman Vdo Navigation system for providing an optimal route from traffic messages
US6680694B1 (en) 1997-08-19 2004-01-20 Siemens Vdo Automotive Corporation Vehicle information system
US6812888B2 (en) 1997-08-19 2004-11-02 Siemens Vdo Automotive Corporation Driver information system
US6707421B1 (en) 1997-08-19 2004-03-16 Siemens Vdo Automotive Corporation Driver information system
US6664922B1 (en) 1997-08-28 2003-12-16 At Road, Inc. Method for distributing location-relevant information using a network
US6552682B1 (en) 1997-08-28 2003-04-22 At Road, Inc. Method for distributing location-relevant information using a network
US5959577A (en) 1997-08-28 1999-09-28 Vectorlink, Inc. Method and structure for distribution of travel information using network
US6453230B1 (en) 1997-12-02 2002-09-17 Mannesmann Vdo Ag Apparatus for handling a traffic message
US6611753B1 (en) 1998-04-17 2003-08-26 Magellan Dis, Inc. 3-dimensional intersection display for vehicle navigation system
US6438490B2 (en) 1998-04-28 2002-08-20 Xanavi Informatics Corporation Route searching device
US6208935B1 (en) 1998-05-01 2001-03-27 Hitachi, Ltd. Map application system
US6204778B1 (en) 1998-05-15 2001-03-20 International Road Dynamics Inc. Truck traffic monitoring and warning systems and vehicle ramp advisory system
US6178378B1 (en) * 1998-05-23 2001-01-23 General Motors Corporation Method for operating a navigation system for motor vehicles
US20010001848A1 (en) 1998-06-25 2001-05-24 Hidekazu Oshizawa Vehicle navigation system providing traffic advisories based on traffic information and learned route
US6266608B1 (en) 1998-10-16 2001-07-24 Nokia Mobile Phones Limited Method and apparatus for the selection of traffic information for a motor vehicle
US6529143B2 (en) 1998-10-23 2003-03-04 Nokia Mobile Phones Ltd. Information retrieval system
US6169894B1 (en) 1998-11-25 2001-01-02 Lucent Technologies, Inc. Apparatus, method and system for mobile broadcast of information specific to a geographic region
US6351709B2 (en) 1998-12-02 2002-02-26 Lear Automotive Dearborn, Inc. Vehicle navigation system with route updating feature
US6240364B1 (en) 1999-02-06 2001-05-29 Daimlerchrysler Ag Method and device for providing traffic information
US6868331B2 (en) 1999-03-01 2005-03-15 Nokia Mobile Phones, Ltd. Method for outputting traffic information in a motor vehicle
US6349261B1 (en) 1999-03-08 2002-02-19 Navitime Japan Co., Ltd. Method and apparatus for determining route within traffic network
US6785606B2 (en) 1999-04-19 2004-08-31 Dekock Bruce W. System for providing traffic information
US6622083B1 (en) * 1999-06-01 2003-09-16 Siemens Vdo Automotive Corporation Portable driver information device
US6657558B2 (en) 1999-08-31 2003-12-02 Hitachi, Ltd. Broadcasting system, broadcast receiving hardware systems, and navigation terminal
US6741188B1 (en) 1999-10-22 2004-05-25 John M. Miller System for dynamically pushing information to a user utilizing global positioning system
US6253146B1 (en) 1999-12-06 2001-06-26 At&T Corp. Network-based traffic congestion notification service
US6526335B1 (en) 2000-01-24 2003-02-25 G. Victor Treyz Automobile personal computer systems
US6370454B1 (en) 2000-02-25 2002-04-09 Edwin S. Moore Iii Apparatus and method for monitoring and maintaining mechanized equipment
US6317685B1 (en) 2000-03-13 2001-11-13 Navigation Technologies Corp. Method and system for providing alternate routes with a navigation system
US6587787B1 (en) 2000-03-15 2003-07-01 Alpine Electronics, Inc. Vehicle navigation system apparatus and method providing enhanced information regarding geographic entities
US20010029425A1 (en) 2000-03-17 2001-10-11 David Myr Real time vehicle guidance and traffic forecasting system
US6615130B2 (en) 2000-03-17 2003-09-02 Makor Issues And Rights Ltd. Real time vehicle guidance and traffic forecasting system
US6480783B1 (en) 2000-03-17 2002-11-12 Makor Issues And Rights Ltd. Real time vehicle guidance and forecasting system under traffic jam conditions
US6812860B1 (en) 2000-03-22 2004-11-02 Ford Global Technologies, Llc System and method of providing information to an onboard information device in a vehicle
US6785551B1 (en) 2000-04-07 2004-08-31 Ford Motor Company Method of providing dynamic regionally relevant data to a mobile environment
US6823263B1 (en) 2000-04-12 2004-11-23 Weather Central, Inc. System and method for providing personalized weather reports and the like
US6317686B1 (en) 2000-07-21 2001-11-13 Bin Ran Method of providing travel time
US20020016655A1 (en) 2000-08-01 2002-02-07 Joao Raymond Anthony Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information
US6546333B2 (en) 2000-08-01 2003-04-08 Sony Corporation Car navigation apparatus, traffic information providing apparatus, program recording medium for car navigation apparatus, and program recording medium for traffic information providing apparatus
US6760661B2 (en) 2000-08-25 2004-07-06 Siemens Aktiengesellschaft Method for operating a navigation appliance, and arrangement for carrying out the method
US6539302B1 (en) 2000-09-06 2003-03-25 Navigation Technologies Corporation Method, system, and article of manufacture for providing notification of traffic conditions
US6836667B1 (en) 2000-09-19 2004-12-28 Lucent Technologies Inc. Method and apparatus for a wireless telecommunication system that provides location-based messages
US6810323B1 (en) 2000-09-25 2004-10-26 Motorola, Inc. System and method for storing and using information associated with geographic locations of interest to a mobile user
US6587777B1 (en) 2000-10-23 2003-07-01 Sun Microsystems, Inc. System and method for location based traffic reporting
US6591188B1 (en) * 2000-11-01 2003-07-08 Navigation Technologies Corp. Method, system and article of manufacture for identifying regularly traveled routes
US6650948B1 (en) 2000-11-28 2003-11-18 Applied Generics Limited Traffic flow monitoring
US6603405B2 (en) 2000-12-05 2003-08-05 User-Centric Enterprises, Inc. Vehicle-centric weather prediction system and method
US6622087B2 (en) * 2000-12-26 2003-09-16 Intel Corporation Method and apparatus for deriving travel profiles
US6615133B2 (en) * 2001-02-27 2003-09-02 International Business Machines Corporation Apparatus, system, method and computer program product for determining an optimum route based on historical information
US6590507B2 (en) 2001-03-05 2003-07-08 Hrl Laboratories, Llc Method and system for providing personalized traffic alerts
US6618669B2 (en) 2001-04-12 2003-09-09 Mitsubishi Denki Kabushiki Kaisha Navigation apparatus, navigation method and navigation program
US6549833B2 (en) 2001-05-08 2003-04-15 Hitachi, Ltd. Repair and maintenance support system and a car corresponding to the system
US6735504B2 (en) 2001-05-08 2004-05-11 Hitachi, Ltd. Repair and maintenance support system and a car corresponding to the system
US6920382B2 (en) 2001-05-08 2005-07-19 Hitachi, Ltd. Repair and maintenance support system and a car corresponding to the system
US7155376B2 (en) 2001-06-22 2006-12-26 Caliper Corporation Traffic data management and simulation system
US6862524B1 (en) 2001-07-03 2005-03-01 At Road, Inc. Using location data to determine traffic and route information
US6798358B2 (en) 2001-07-03 2004-09-28 Nortel Networks Limited Location-based content delivery
US6594576B2 (en) 2001-07-03 2003-07-15 At Road, Inc. Using location data to determine traffic information
US6583734B2 (en) 2001-07-18 2003-06-24 International Business Machines Corporation Enhanced vehicle hazard warning and safety features integrated with an onboard navigation system
US6553313B1 (en) 2001-07-24 2003-04-22 Trimble Navigation Limited Method and system for updating directed user-based dynamic advertising
US6542822B1 (en) 2001-07-24 2003-04-01 Trimble Navigation Limited Directed user-based dynamic advertising
US6522250B1 (en) 2001-08-14 2003-02-18 The Mitre Corporation Movement history based selective distribution of generally broadcast information
US6587785B2 (en) 2001-09-21 2003-07-01 General Motors Corporation Method and system for mobile vehicle re-routing
US6850842B2 (en) 2001-10-31 2005-02-01 Samsung Electronics Co., Ltd. Navigation system for providing real-time traffic information and traffic information processing method by the same
US6584401B2 (en) * 2001-11-27 2003-06-24 Hewlett-Packard Development Company, Lp. Automatic gathering and analysis of data on commute paths
US6973384B2 (en) * 2001-12-06 2005-12-06 Bellsouth Intellectual Property Corporation Automated location-intelligent traffic notification service systems and methods
US7006903B2 (en) 2002-02-28 2006-02-28 Sabre Inc. Method and system for routing mobile vehicles and scheduling maintenance for those vehicles related application
US6859720B2 (en) 2002-03-26 2005-02-22 Alpine Electronics, Inc. Traffic-information distribution method on-vehicle navigation apparatus
US6859728B2 (en) 2002-04-03 2005-02-22 Matsushita Electric Industrial Co., Ltd. Navigation system
US6730940B1 (en) 2002-10-29 2004-05-04 Lumileds Lighting U.S., Llc Enhanced brightness light emitting device spot emitter
US6810328B2 (en) 2002-11-23 2004-10-26 Alpine Electronics, Inc Navigation method and system for indicating area-specific traffic information
US6859726B2 (en) 2003-02-08 2005-02-22 Samsung Electronics Co., Ltd. Navigation apparatus and method for calculating optimum travel route using the same
US20050027442A1 (en) * 2003-07-31 2005-02-03 Kelley Edward E. Agenda replicator system and method for travelers
US7096115B1 (en) 2003-09-23 2006-08-22 Navteq North America, Llc Method and system for developing traffic messages

Cited By (110)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050137795A1 (en) * 2002-04-03 2005-06-23 Kiyomi Sakamoto Navigation system
US7406380B2 (en) * 2002-04-03 2008-07-29 Matsushita Electric Industrial Co., Ltd. Navigation system
US20070225902A1 (en) * 2004-03-15 2007-09-27 Tomtom International B.V. Navigation Device Displaying Dynamic Travel Information
US7865304B2 (en) * 2004-03-15 2011-01-04 Tomtom International B.V. Navigation device displaying dynamic travel information
US20060173618A1 (en) * 2005-02-01 2006-08-03 Mark Eyer Intelligent travel assistant
US9736618B1 (en) 2005-04-04 2017-08-15 X One, Inc. Techniques for sharing relative position between mobile devices
US10165059B2 (en) 2005-04-04 2018-12-25 X One, Inc. Methods, systems and apparatuses for the formation and tracking of location sharing groups
US8831635B2 (en) 2005-04-04 2014-09-09 X One, Inc. Methods and apparatuses for transmission of an alert to multiple devices
US8798647B1 (en) 2005-04-04 2014-08-05 X One, Inc. Tracking proximity of services provider to services consumer
US8798593B2 (en) 2005-04-04 2014-08-05 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
US11778415B2 (en) 2005-04-04 2023-10-03 Xone, Inc. Location sharing application in association with services provision
US8385964B2 (en) 2005-04-04 2013-02-26 Xone, Inc. Methods and apparatuses for geospatial-based sharing of information by multiple devices
US11356799B2 (en) 2005-04-04 2022-06-07 X One, Inc. Fleet location sharing application in association with services provision
US10856099B2 (en) 2005-04-04 2020-12-01 X One, Inc. Application-based two-way tracking and mapping function with selected individuals
US8798645B2 (en) 2005-04-04 2014-08-05 X One, Inc. Methods and systems for sharing position data and tracing paths between mobile-device users
US8750898B2 (en) 2005-04-04 2014-06-10 X One, Inc. Methods and systems for annotating target locations
US9031581B1 (en) 2005-04-04 2015-05-12 X One, Inc. Apparatus and method for obtaining content on a cellular wireless device based on proximity to other wireless devices
US8712441B2 (en) 2005-04-04 2014-04-29 Xone, Inc. Methods and systems for temporarily sharing position data between mobile-device users
US10791414B2 (en) 2005-04-04 2020-09-29 X One, Inc. Location sharing for commercial and proprietary content applications
US9167558B2 (en) 2005-04-04 2015-10-20 X One, Inc. Methods and systems for sharing position data between subscribers involving multiple wireless providers
US9185522B1 (en) 2005-04-04 2015-11-10 X One, Inc. Apparatus and method to transmit content to a cellular wireless device based on proximity to other wireless devices
US10750311B2 (en) 2005-04-04 2020-08-18 X One, Inc. Application-based tracking and mapping function in connection with vehicle-based services provision
US9253616B1 (en) 2005-04-04 2016-02-02 X One, Inc. Apparatus and method for obtaining content on a cellular wireless device based on proximity
US9467832B2 (en) 2005-04-04 2016-10-11 X One, Inc. Methods and systems for temporarily sharing position data between mobile-device users
US9854402B1 (en) 2005-04-04 2017-12-26 X One, Inc. Formation of wireless device location sharing group
US10750309B2 (en) 2005-04-04 2020-08-18 X One, Inc. Ad hoc location sharing group establishment for wireless devices with designated meeting point
US9584960B1 (en) 2005-04-04 2017-02-28 X One, Inc. Rendez vous management using mobile phones or other mobile devices
US9615204B1 (en) 2005-04-04 2017-04-04 X One, Inc. Techniques for communication within closed groups of mobile devices
US10341809B2 (en) 2005-04-04 2019-07-02 X One, Inc. Location sharing with facilitated meeting point definition
US10341808B2 (en) 2005-04-04 2019-07-02 X One, Inc. Location sharing for commercial and proprietary content applications
US10313826B2 (en) 2005-04-04 2019-06-04 X One, Inc. Location sharing and map support in connection with services request
US10299071B2 (en) 2005-04-04 2019-05-21 X One, Inc. Server-implemented methods and systems for sharing location amongst web-enabled cell phones
US10200811B1 (en) 2005-04-04 2019-02-05 X One, Inc. Map presentation on cellular device showing positions of multiple other wireless device users
US9654921B1 (en) 2005-04-04 2017-05-16 X One, Inc. Techniques for sharing position data between first and second devices
US9749790B1 (en) 2005-04-04 2017-08-29 X One, Inc. Rendez vous management using mobile phones or other mobile devices
US10750310B2 (en) 2005-04-04 2020-08-18 X One, Inc. Temporary location sharing group with event based termination
US10149092B1 (en) 2005-04-04 2018-12-04 X One, Inc. Location sharing service between GPS-enabled wireless devices, with shared target location exchange
US9967704B1 (en) 2005-04-04 2018-05-08 X One, Inc. Location sharing group map management
US9955298B1 (en) 2005-04-04 2018-04-24 X One, Inc. Methods, systems and apparatuses for the formation and tracking of location sharing groups
US8538458B2 (en) 2005-04-04 2013-09-17 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
US9942705B1 (en) 2005-04-04 2018-04-10 X One, Inc. Location sharing group for services provision
US9883360B1 (en) 2005-04-04 2018-01-30 X One, Inc. Rendez vous management using mobile phones or other mobile devices
US9854394B1 (en) 2005-04-04 2017-12-26 X One, Inc. Ad hoc location sharing group between first and second cellular wireless devices
US20100118025A1 (en) * 2005-04-21 2010-05-13 Microsoft Corporation Mode information displayed in a mapping application
US7777648B2 (en) 2005-04-21 2010-08-17 Microsoft Corporation Mode information displayed in a mapping application
US8843309B2 (en) 2005-04-21 2014-09-23 Microsoft Corporation Virtual earth mapping
US10182108B2 (en) 2005-04-21 2019-01-15 Microsoft Technology Licensing, Llc Obtaining and displaying virtual earth images
US8103445B2 (en) 2005-04-21 2012-01-24 Microsoft Corporation Dynamic map rendering as a function of a user parameter
US20060238380A1 (en) * 2005-04-21 2006-10-26 Microsoft Corporation Maintaining user privacy in a virtual earth environment
US7920072B2 (en) 2005-04-21 2011-04-05 Microsoft Corporation Virtual earth rooftop overlay and bounding
US9383206B2 (en) 2005-04-21 2016-07-05 Microsoft Technology Licensing, Llc Obtaining and displaying virtual earth images
US20060241859A1 (en) * 2005-04-21 2006-10-26 Microsoft Corporation Virtual earth real-time advertising
US20060238383A1 (en) * 2005-04-21 2006-10-26 Microsoft Corporation Virtual earth rooftop overlay and bounding
US20070210937A1 (en) * 2005-04-21 2007-09-13 Microsoft Corporation Dynamic rendering of map information
US7564377B2 (en) * 2005-04-21 2009-07-21 Microsoft Corporation Real-time virtual earth driving information
US20060238382A1 (en) * 2005-04-21 2006-10-26 Microsoft Corporation Real-time virtual earth driving information
US8850011B2 (en) 2005-04-21 2014-09-30 Microsoft Corporation Obtaining and displaying virtual earth images
US20090073191A1 (en) * 2005-04-21 2009-03-19 Microsoft Corporation Virtual earth rooftop overlay and bounding
US7466244B2 (en) 2005-04-21 2008-12-16 Microsoft Corporation Virtual earth rooftop overlay and bounding
US20070273558A1 (en) * 2005-04-21 2007-11-29 Microsoft Corporation Dynamic map rendering as a function of a user parameter
US7509215B2 (en) * 2005-12-12 2009-03-24 Microsoft Corporation Augmented navigation system
US20070150175A1 (en) * 2005-12-12 2007-06-28 Microsoft Corporation Augmented navigation system
US7974777B2 (en) 2007-01-10 2011-07-05 Tomtom International B.V. Navigation device and method for using a traffic message channel
US20080167804A1 (en) * 2007-01-10 2008-07-10 Pieter Geelen Traffic delay indication
US20080215236A1 (en) * 2007-01-10 2008-09-04 William Deurwaarder Navigation device and method for using a traffic message channel
US20080221782A1 (en) * 2007-01-10 2008-09-11 William Deurwaarder Navigation device and method providing a traffic message channel resource
US8751152B2 (en) 2007-01-10 2014-06-10 Tomtom International B.V. Traffic delay indication
US8335637B2 (en) * 2007-01-10 2012-12-18 Tomtom International B.V. Navigation device and method providing a traffic message channel resource
US8121777B2 (en) 2008-03-07 2012-02-21 Microsoft Corporation Wireless broadcasting of drive-times data
US20100114485A1 (en) * 2008-11-06 2010-05-06 Bhogal Kulvir S Providing Popular Global Positioning Satelite (GPS) Routes
US8649970B2 (en) * 2008-11-06 2014-02-11 International Business Machines Corporation Providing popular global positioning satellite (GPS) routes
US8219027B2 (en) 2009-02-26 2012-07-10 International Business Machines Corporation Proximity based smart collaboration
US20100216402A1 (en) * 2009-02-26 2010-08-26 International Business Machines Corporation Proximity based smart collaboration
TWI404916B (en) * 2009-05-08 2013-08-11 Mitac Int Corp Methods of creating and playing customizable audio alerts and related devices
US20110130962A1 (en) * 2009-12-02 2011-06-02 Larry Damell Lindsey Navigation system for delivery vehicles
US20110153191A1 (en) * 2009-12-18 2011-06-23 Telenav, Inc. Navigation system with location profiling and method of operation thereof
US8234063B2 (en) 2009-12-18 2012-07-31 Telenav, Inc. Navigation system with location profiling and method of operation thereof
US8572303B2 (en) 2010-02-03 2013-10-29 Tal Lavian Portable universal communication device
US8548135B1 (en) 2010-02-03 2013-10-01 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8681951B1 (en) 2010-02-03 2014-03-25 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8625756B1 (en) 2010-02-03 2014-01-07 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8594280B1 (en) 2010-02-03 2013-11-26 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8879698B1 (en) 2010-02-03 2014-11-04 Tal Lavian Device and method for providing enhanced telephony
US8687777B1 (en) 2010-02-03 2014-04-01 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8537989B1 (en) 2010-02-03 2013-09-17 Tal Lavian Device and method for providing enhanced telephony
US8553859B1 (en) 2010-02-03 2013-10-08 Tal Lavian Device and method for providing enhanced telephony
US8548131B1 (en) 2010-02-03 2013-10-01 Tal Lavian Systems and methods for communicating with an interactive voice response system
US9001819B1 (en) 2010-02-18 2015-04-07 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8700327B2 (en) 2010-04-27 2014-04-15 Honda Motor Co., Ltd. Method of determining routes for use in navigation
US8688362B2 (en) * 2010-12-16 2014-04-01 Blackberry Limited Changing frequency of navigational notifications based on travel patterns
US20120158283A1 (en) * 2010-12-16 2012-06-21 Research In Motion Limited Changing Frequency of Navigational Notifications Based On Travel Patterns
US8452771B2 (en) 2011-01-03 2013-05-28 Honda Motor Co., Ltd. Method for differentiating traffic data obtained from probe vehicles
US8583367B2 (en) 2011-01-07 2013-11-12 Honda Motor Co., Ltd. System and method for displaying a route based on a vehicle state
US8406388B2 (en) 2011-07-18 2013-03-26 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8903073B2 (en) 2011-07-20 2014-12-02 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8345835B1 (en) 2011-07-20 2013-01-01 Zvi Or-Bach Systems and methods for visual presentation and selection of IVR menu
US8706459B2 (en) * 2011-10-05 2014-04-22 International Business Machines Corporation Traffic sensor management
US8706458B2 (en) * 2011-10-05 2014-04-22 International Business Machines Corporation Traffic sensor management
US8867708B1 (en) 2012-03-02 2014-10-21 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US8731148B1 (en) 2012-03-02 2014-05-20 Tal Lavian Systems and methods for visual presentation and selection of IVR menu
US9739632B2 (en) 2012-10-17 2017-08-22 Tomtom Navigation B.V. Methods and systems of providing information using a navigation apparatus
US10612935B2 (en) 2012-10-17 2020-04-07 Tomtom Navigation B.V. Methods and systems of providing information using a navigation apparatus
US9123345B2 (en) 2013-03-14 2015-09-01 Honda Motor Co., Ltd. Voice interface systems and methods
US20160091334A1 (en) * 2014-09-25 2016-03-31 International Business Machines Corporation Travel routes based on communication channel availability
US10712164B2 (en) * 2014-09-25 2020-07-14 International Business Machines Corporation Travel routes based on communication channel availability
US10712165B2 (en) * 2014-09-25 2020-07-14 International Business Machines Corporation Travel routes based on communication channel availability
US20160091333A1 (en) * 2014-09-25 2016-03-31 International Business Machines Corporation Travel routes based on communication channel availability
US10488210B2 (en) 2014-12-10 2019-11-26 Red Hat, Inc. Providing an instruction notification for navigation
US9696173B2 (en) 2014-12-10 2017-07-04 Red Hat, Inc. Providing an instruction notification for navigation
US9612128B2 (en) 2015-04-29 2017-04-04 Microsoft Technology Licensing, Llc Controlling travel route planning module based upon user travel preference

Also Published As

Publication number Publication date
US20050222763A1 (en) 2005-10-06

Similar Documents

Publication Publication Date Title
US7289904B2 (en) Vehicle navigation system and methods for incorporating user preferences into same
US7319931B2 (en) Methods for filtering and providing traffic information
US7680596B2 (en) Route calculation method for a vehicle navigation system
US7877206B2 (en) Display method and system for a vehicle navigation system
US7366606B2 (en) Method for refining traffic flow data
US7451042B2 (en) Bandwidth and memory conserving methods for a vehicle navigation system
US7671764B2 (en) Method and system for using traffic flow data to navigate a vehicle to a destination
US7439878B2 (en) Apparatus and method for processing and displaying traffic information in an automotive navigation system
US6401027B1 (en) Remote road traffic data collection and intelligent vehicle highway system
US7289039B2 (en) Apparatus and method for processing and displaying traffic information in an automotive navigation system
ES2306531T3 (en) INSTANT TRAFFIC CONTROL SYSTEM.
EP1316079B1 (en) Method and system for providing traffic and related information
US20030069683A1 (en) Traffic monitoring system and methods for traffic monitoring and route guidance useful therewith
CN102024338B (en) On-vehicle information terminal and information distribution system
US20040102893A1 (en) Traffic monitoring system
JPH08287393A (en) Traveling time providing device and route calculating device
JP4142802B2 (en) Vehicle navigation device

Legal Events

Date Code Title Description
AS Assignment

Owner name: HONDA MOTOR CO., LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:UYEKI, ROBERT;REEL/FRAME:016527/0616

Effective date: 20050426

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12