The present invention relates to navigation systems and more specifically to navigation systems for suggesting routes for vehicles navigating streets where the suggested routes are based at least partially on fuel efficiency for the vehicle even more specifically the present invention relates to suggesting a route based on at least one estimated speed for the suggested route.
Global Positioning Systems (“GPS”) enable a device to determine its location on the surface of the Earth. Many systems have been developed that utilize GPS to assist drivers in navigating their vehicles. Before GPS, the driver had a difficult time not only finding a route between their current location and a selected destination, but also in selecting the best route to meet the driver's goals.
One goal some drivers have is to minimize the amount of fuel usage required to travel between the current location and a selected destination. This goal has become even more pronounced with the rising cost of fuel. Finding the street route that will use the minimum fuel usage can be very difficult as it can depend on many factors, including the grade of the streets, the traffic conditions, the number and length of stops in the route, the speed limits of the street route, and the effect of speed on the fuel efficiency of the vehicle. This is further complicated because the exact conditions of the vehicle and the route may not be known. And further, it may be that the driver desires to avoid problems in the route such as dangerous intersections.
U.S. Pat. No. 5,742,922 entitled “Vehicle Navigation System and Method for Selecting a Route According to Fuel Consumption” provides for determining a least fuel consumption route in view of the altitude information of the route, but does not account for the effect of speed on the fuel efficiency of the vehicle and does not account for the usage of fuel for stopping or slowing down to turn.
Accordingly, it would be advantageous to provide methods and apparatus that allow for determining a route having a minimum fuel usage for a vehicle based on the estimated effect of speed on the fuel consumption of the vehicle and estimated speeds for the street route as well as an estimated amount of fuel used based on an estimated number of stops the vehicle will make and an estimated number of times the vehicle will slow down to turn. It would be further advantageous to take into account the driver's preferences for a route.
It is therefore an object of the present invention to provide a method for a navigation system to determine an estimated minimum fuel usage route for a vehicle based at least on the estimated effect of speed of the vehicle on the efficiency of fuel consumption. In one embodiment, the estimated fuel consumption is further based on the number of estimated stops in a route and on the estimated number of times the vehicle will slow down to turn.
In another embodiment, for example, a method for determining a suggested route having an estimated minimum fuel usage from a start location to a destination location for a vehicle based on estimated fuel efficiency for the vehicle and further based on at least one estimated speed for at least a portion of the route. In some embodiments, the suggested route has constraints placed on it by user preferences. In some embodiments, in addition to route information, real-time information and actual driver behavior data is used in computing the estimated amount of fuel usage.
In another embodiment, an apparatus is illustrated for determining a suggested route having an estimated minimum fuel usage from a start location to a destination location for a vehicle based on estimated fuel efficiency for the vehicle and further based on at least one estimated speed for at least a portion of the route. The apparatus comprises an antenna for receiving signals from GPS satellites, and a GPS operable to determine the current location of the vehicle based on the received signals from the GPS satellites. The apparatus further comprises a navigation system having a route determiner operable to determine the suggested route based on estimated fuel efficiency for the vehicle and further based on at least one estimated speed for at least a portion of the route. The estimated fuel efficiency for the vehicle is based on at least aggregated data for the vehicle or at least on aggregated data for the class of vehicle.
Still other objects and advantages of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein the preferred embodiments of the invention are shown and described, simply by way of illustration of the best mode contemplated of carrying out the invention. As will be realized, the invention is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the invention. Accordingly, the drawings and description thereof are to be regarded as illustrative in nature, and not as restrictive.
The present invention is illustrated by way of example, and not by limitation, in the figures of the accompanying drawings, wherein elements having the same reference numeral designations represent like elements throughout and wherein:
The vehicle 22 is a means of transport on land such as a passenger car, sport utility vehicle, truck, scooter, or motorcycle. The vehicle 22 includes a user 24, a motive source 26, a fuel 28, and a fuel efficiency curve 30. The user 24 is a person such as the driver of the vehicle 22 or a passenger of the vehicle 22. Alternatively, in other embodiments the user 24 is remotely located from the vehicle 22 and communicates remotely with the navigation system 20. For example, the user 24 can be a person remotely located assisting the driver of the vehicle 22 in navigating the vehicle 22. The motive source 26 is an internal combustion engine running on gasoline, or one of the many alternatives such as an electric motor using electricity. The motive source 26 uses the fuel 28. For an internal combustion engine the fuel 28 is gasoline, or a substitute or alternative such as diesel gasoline, alcohol, ethanol, hydrogen, natural gas, etc. For an electric motor the fuel 28 is a battery or alternatively a fuel cell. The fuel efficiency curve 30 is how efficiently the motive source 26 uses the fuel 28 to propel the vehicle 22 at different speeds of the vehicle 22. For example, a typical passenger car might get 30 miles/gallon for a speed of 55 miles/hour, but only get 20 miles/gallon for a speed of 85 miles/hour. The fuel efficiency curve 30 in this case would have miles/gallon on the vertical axis and miles/hour on the horizontal axis. There are many reasons why the efficiency of the motive source 26 varies depending on the speed of the vehicle 22. The reasons include reasons inherent to the design of the motive source 26, reasons inherent to the design of the fuel 28, e.g. a battery, reasons inherent to the design of the vehicle 22, and reasons inherent to the physics of moving a vehicle 22 on the surface of the earth, including wind resistance.
The navigation system 20 includes a CPU 34, a memory 36, a communication device 38, a GPS system 40, a display device 42, and an input device 44, all of which are communicatively coupled with one each other. In some embodiments, the communication device 38 and/or the GPS system 40 are not included. The navigation system 20 further includes a route determiner 46 disposed in the memory 36 and a street and road data 46 disposed in the memory 36. The CPU 34 is a central processing unit (“CPU”), or alternatively any device disposed for processing the instructions and data contained in the memory 36. The memory 36 is random access memory (“RAM”), and non-volatile storage of read-only memory (“ROM”), or alternatively a hard-disk, or flash memory. Alternatively, the memory 36 is remotely located and accessed by the navigation system 20 by using the communication device 38. The communication device 38 has an antenna and electronics for transmitting and receiving signals such as GSM, or alternatively a local area network (LAN) signals such as 802.11. Alternatively, the communication device 38 is shared with the GPS system 40. For example, in an embodiment, there is only a single antenna shared by the navigation system 20 and the GPS system 40. The display device 42 is an LCD display within the vehicle 22 or alternatively a speaker giving voice commands. The input device 44 is a touch screen or alternatively a microphone with the CPU 34 disposed for voice recognition, or input device can be a keyboard. Further, in some embodiments the display device 42 and the input device 44 can be remotely located and in communication with the navigation system 20 over the communication device 38. For example, the display device 42 can be a home computer LCD monitor and the input device 44 can be the mouse on the home computer with a friend of the driver of the vehicle 22 remotely aiding the driver in navigating the vehicle 22.
The GPS system 40 includes an antenna 48, a signal processor 50, CPU 52, and a memory 54. GPS systems 40 are well-known in the art. The antenna 48 is for receiving signals from the GPS satellite constellation 60. The signal processor 50 is for processing the signals received from the GPS satellite constellation 60 into a digital format that the CPU 52 can process. The GPS system 40 includes a separate CPU 52 and memory 54 enabled to process the signals received from the satellite constellation 60 and calculate a location on the surface of the Earth based on the received signals. Alternatively, the GPS system 40 shares one or more of the antenna 48, the signal process 50, the CPU 52, and the memory 54, with the navigation system 20.
The aggregated efficiency data 64 includes efficiency data that is not specific to the particular vehicle 22, but rather based on aggregated efficiency data 64 for the vehicle 22, such as the year the vehicle 22 was manufactured, or the number of cylinders of the vehicle 22, or the make and the model of the vehicle 22. Table 4 below is an example of aggregated efficiency data 64 showing the estimated fuel efficiency curves 30 for vehicles 22 manufactured in the years 1973, 1984, or 1997. The aggregated efficiency data 64 is used to approximate the fuel efficiency curve 30 for the vehicle 22. User route preferences data 66 includes, but is not necessarily limited to, data relevant to user route preferences such as whether the user 24 would like to avoid dangerous intersection, whether the user 24 would like to avoid frequent stops, and whether the user 24 would like to avoid highways or backstreets. Real-time route information data 68 includes current traffic conditions, current accident reports, weather information, current construction sites, etc. Actual driver behavior data 70 includes data collected from the driving behavior of a user 20 such as whether a user 20 regularly speeds, whether the user 20 accelerates fast and thus uses more fuel in a stop then a typical driver, etc. Segment information data 72 includes the speed limit of streets, the direction of travel for streets, whether there is a stop sign or stop light at an intersection, bends in streets, length of streets, whether a vehicle 22 will need to slow down to turn, whether a vehicle will have to slow down due to a bend in the street, etc. The data 64, 66, 68, 70, 72 is locally stored, or in the alternative the data 64, 66, 68, 70, 72 can be remotely stored. In some embodiments, the data 64, 66, 68, 70, 72 is partially stored locally and partially stored remotely.
The route 60 is a route from a start location 76 of a vehicle 22 to a destination location 78 for the vehicle 22 having one or more of a segment 80. The start location 76 and the destination location 78 are places on the surface of the Earth. The segment 80 is a street, road, turnpike, or other path for a vehicle with a speed limit. In some embodiments, the speed limit for a segment 80 is estimated based on data in street and road data 58. The route 60 may contain turn information between two of the segments 80 and information regarding the intersection between two of the segments 80.
The suggested route 62 is a selected one of one or more of the routes 60 having an estimated minimum fuel usage 74. The estimated minimum fuel usage 74 is calculated by the route determiner 46. In some embodiments the estimated minimum fuel usage 74 is discarded and only the suggested route 62 is retained.
The route determiner 46 determines the suggested route 62 having an estimated minimum fuel usage 74 from a start location 76 of a vehicle 22 to a destination location 78 for the vehicle 22 based on estimated fuel efficiency for the vehicle 22 and further based on at least one estimated speed for the vehicle 22 for at least one segment 80 of the suggested route 62.
The route determiner 46 is arranged to determine the start location 76 for the vehicle 22 by receiving input from the user 24 of the navigation system 20 using the input device 44 or in the alternative the route determiner 46 can determine a start location 76 for the vehicle 22 by receiving the current location from the GPS system 40. The route determiner 46 is arranged to receive the destination location 78 for the vehicle 22 from the user 24 using the input device 44.
In some embodiments, the route determiner 46 determines the route 60 by developing partial routes from both the start location 76 and the destination location 78, always keeping the lower fuel use partial routes as the partial routes are expanded. Eventually the partial routes that started from the destination location 78 and the partial routes that started from the start location 76 meet to form complete routes 60 and these complete routes 60 are used to choose the suggested route 62 having the estimated minimum fuel usage 74. The route determiner 46 uses the data in segment information data 72 for estimating the number of stops and the estimated speed, and the estimated number of times the vehicle 22 will slow down to turn, and the estimated number of times the vehicle 22 will slow down due to a bend in the segment 80. The route determiner 46 uses the data in aggregated efficiency data 64 for estimating the fuel efficiency of the vehicle 22 which is based on aggregated data for the vehicle 22. Table 4 is an example of the type of data that is in aggregated efficiency data 64 and which is used to estimate the amount of fuel the vehicle 22 will use for a route 60. Alternatively, the route determiner 46 uses data gathered from the operation of the vehicle 22 for estimating the fuel efficiency of the vehicle 22. After the suggested route 62 is determined, preferably, the route determiner 46 displays turn-by-turn instructions on display device 42, guiding the driver of the vehicle 22 to the destination location 78. In some embodiments, the route determiner 46 is arranged to continuously display on the display device 42 a recommended speed for the vehicle 22 to travel in order to attain the estimated minimum fuel usage 74 that was calculated for the suggested route 62. In some embodiments, the route determiner 46 is arranged to continuously recalculate a new suggested route 62 based on the current location of the vehicle 22.
In some embodiments, the route determiner 46 is arranged to adjust calculations based on actual driver behavior data 70 in building the route 60. For example, the route determiner 46 uses the speed limit of a segment 80 plus 10 miles per hour for the estimated speed in calculating the estimated amount of fuel that will be used for a user 22 that typically speeds 10 miles per hour over the speed limit. In some embodiments, the route determiner 46 is arranged to output for consumption by the user 22 a list of driving styles, for example “like to speed”, “don't usually speed”, etc., and receive from the input device 44 a selected driving style from the user 24, and then determine the suggested route 62 based on this received driving style by basing calculations of estimated fuel usage using the received driving style of the user 24. In some embodiments, the route determiner 46 is arranged to build the route 60 based on the real-time route information 68 by adjusting the estimated fuel usage for segments 80 with traffic delays. In some embodiments, the route determiner 46 is arranged to adjust the estimated speed of segments based on the use of real time route information 68. In some embodiments, real time route information 68 includes historical route traffic information. In some embodiments, the route determiner 46 is arranged to reject one or more of the segment 80 or to add fuel usage to one or more of the segment 80 based on the user route preferences data 66. For example, if a user 24 chooses to avoid dangerous intersections, the route determiner 46 will then in some embodiments not include a segment 80 if that segment 80 includes a dangerous intersection. In another example, the route determiner 46 only chooses a route 60 that does not include traveling on highways.
Referring to Table 1 and to
Table 2 and
Table 3 and
The route determiner 46 will determine which of the three candidate routes A, B, and C from the start location 76 to the destination location 78, has the estimated minimum fuel usage 74 for a vehicle 22.
Table 4 illustrates expected miles per gallon for a typical vehicle 22 manufactured in 1973, 1984, and 1997. The data in Table 4 is stored in aggregated efficiency data 64.
92
94
96
For example, for a 1997 vehicle 22 the estimated fuel efficiency is 30.5 miles/fuel unit 92 for a speed of 25 miles/hour; 31.2 miles/fuel unit 94 for a speed of 35 miles/hour; and, 29.2 miles/fuel unit 96 for a speed of 65 miles/hour. The estimated fuel efficiency is for a typical vehicle 22 manufactured in 1973, 1984, or 1997. This data is then being used to estimate the actual fuel efficiency curve 30 of the vehicle 22. For this example, we assume the vehicle 22 was manufactured in 1997.
The aggregated data in Table 4 is for a typical vehicle 22 manufactured in 1997, where relative measures of fuel efficiency were aggregated. The reason relative data was aggregated rather than absolute data is partially due to the differences in vehicle weight. When using this data for comparing routes A, B, and C, the relative estimated fuel consumed is compared by the route determiner 46. For example, for a 1997 vehicle 22 the estimated fuel efficiency for 15 miles/hour is 24.4 miles/gallon and the estimated fuel efficiency for 55 miles/hour is 32.4, so for any particular 1997 vehicle 22, the fuel efficiency can be compared between the two speeds with, (32.4/24.4)*100, or a 1997 vehicle 22 is estimated to be 133 percent more efficient using fuel at 55 miles per hour than at 15 miles per hour.
The numbers in the column “Fuel” of Tables 1, 2, and 3 represent the application of the embodiment of route determiner 46 depicted in
Applying the embodiment of route determiner 46 depicted in
For route A there are 5 segments depicted in
Note that route B illustrated in Table 2 is the shortest in length at 16 miles, but uses more fuel than route A illustrated in Table 1. And note that Route C illustrated in Table 3 has the fastest estimated time at 0.5213 hours, compared to 0.5906 hours for Route A.
It should now be apparent that a navigation system has been described that determines an estimated minimum fuel usage route 74 from a start location 76 to a destination location 78 for a vehicle 22 based at least on the estimated effect of speed of the vehicle on the efficiency of fuel consumption.
It will be readily seen by one of ordinary skill in the art that the present invention fulfills all of the objects set forth above. After reading the foregoing specification, one of ordinary skill will be able to affect various changes, substitutions of equivalents and various other aspects of the invention as broadly disclosed herein. It is therefore intended that the protection granted hereon be limited only by the definition contained in the appended claims and equivalents thereof.
Number | Name | Date | Kind |
---|---|---|---|
5515283 | Desai et al. | May 1996 | A |
5742922 | Kim | Apr 1998 | A |
5802492 | DeLorme et al. | Sep 1998 | A |
6067502 | Hayashida et al. | May 2000 | A |
6078864 | Long et al. | Jun 2000 | A |
6081609 | Narioka | Jun 2000 | A |
6084989 | Eppler | Jul 2000 | A |
6092076 | McDonough et al. | Jul 2000 | A |
6107944 | Behr et al. | Aug 2000 | A |
6108603 | Karunanidhi | Aug 2000 | A |
6108604 | Fukaga et al. | Aug 2000 | A |
6115669 | Watanabe et al. | Sep 2000 | A |
6124826 | Garthwaite et al. | Sep 2000 | A |
6125326 | Ohmura et al. | Sep 2000 | A |
6141621 | Piwowarski et al. | Oct 2000 | A |
6148261 | Obradovich et al. | Nov 2000 | A |
6151552 | Koizumi et al. | Nov 2000 | A |
6154699 | Williams | Nov 2000 | A |
6163269 | Millington et al. | Dec 2000 | A |
6172641 | Millington | Jan 2001 | B1 |
6175801 | Millington | Jan 2001 | B1 |
6177943 | Margolin | Jan 2001 | B1 |
6178380 | Millington | Jan 2001 | B1 |
6184823 | Smith et al. | Feb 2001 | B1 |
6189130 | Gofman et al. | Feb 2001 | B1 |
6201540 | Gallup et al. | Mar 2001 | B1 |
6204778 | Bergan et al. | Mar 2001 | B1 |
6205397 | Eslambolchi et al. | Mar 2001 | B1 |
6212474 | Fowler et al. | Apr 2001 | B1 |
6223118 | Kobayashi et al. | Apr 2001 | B1 |
6229546 | Lancaster et al. | May 2001 | B1 |
6249740 | Ito et al. | Jun 2001 | B1 |
6252814 | Polidi et al. | Jun 2001 | B1 |
6253151 | Ohler et al. | Jun 2001 | B1 |
6256029 | Millington | Jul 2001 | B1 |
6278942 | McDonough | Aug 2001 | B1 |
6308134 | Croyle et al. | Oct 2001 | B1 |
6320517 | Yano et al. | Nov 2001 | B1 |
6321158 | DeLorme et al. | Nov 2001 | B1 |
6349257 | Liu et al. | Feb 2002 | B1 |
6356210 | Ellis | Mar 2002 | B1 |
6360167 | Millington et al. | Mar 2002 | B1 |
6362751 | Upparapalli | Mar 2002 | B1 |
6363322 | Millington | Mar 2002 | B1 |
6370475 | Breed et al. | Apr 2002 | B1 |
6377278 | Cutright et al. | Apr 2002 | B1 |
6381536 | Satoh et al. | Apr 2002 | B1 |
6385535 | Ohishi et al. | May 2002 | B2 |
6385542 | Millington | May 2002 | B1 |
6397145 | Millington | May 2002 | B1 |
6405130 | Piwowarski | Jun 2002 | B1 |
6408243 | Yofu | Jun 2002 | B1 |
6427115 | Sekiyama | Jul 2002 | B1 |
6430501 | Slominski | Aug 2002 | B1 |
6453235 | Endo et al. | Sep 2002 | B1 |
6484089 | Millington | Nov 2002 | B1 |
6487494 | Odinak et al. | Nov 2002 | B2 |
6515595 | Obradovich et al. | Feb 2003 | B1 |
6529822 | Millington et al. | Mar 2003 | B1 |
6529824 | Obradovich et al. | Mar 2003 | B1 |
6539301 | Shirk | Mar 2003 | B1 |
6565610 | Wang et al. | May 2003 | B1 |
6574551 | Maxwell et al. | Jun 2003 | B1 |
6609062 | Hancock | Aug 2003 | B2 |
6631322 | Arthur et al. | Oct 2003 | B1 |
6671617 | Odinak et al. | Dec 2003 | B2 |
6704649 | Miyahara | Mar 2004 | B2 |
6728608 | Ollis et al. | Apr 2004 | B2 |
6728636 | Kokojima et al. | Apr 2004 | B2 |
6748323 | Lokshin et al. | Jun 2004 | B2 |
6765554 | Millington | Jul 2004 | B2 |
6774932 | Ewing | Aug 2004 | B1 |
6782319 | McDonough | Aug 2004 | B1 |
6816596 | Peinado et al. | Nov 2004 | B1 |
6819301 | Nagamatsu et al. | Nov 2004 | B2 |
6842695 | Tu | Jan 2005 | B1 |
6873907 | Millington et al. | Mar 2005 | B1 |
6885874 | Grube et al. | Apr 2005 | B2 |
6917982 | Dueck et al. | Jul 2005 | B1 |
6938028 | Ito | Aug 2005 | B1 |
7031834 | Ito et al. | Apr 2006 | B2 |
7031836 | Branch | Apr 2006 | B2 |
7058504 | McDonough et al. | Jun 2006 | B2 |
7170518 | Millington et al. | Jan 2007 | B1 |
7233860 | Lokshin et al. | Jun 2007 | B2 |
7260475 | Suzuki | Aug 2007 | B2 |
7321826 | Sheha et al. | Jan 2008 | B2 |
7333820 | Sheha et al. | Feb 2008 | B2 |
7343242 | Breitenberger et al. | Mar 2008 | B2 |
7353107 | Breitenberger et al. | Apr 2008 | B2 |
7379812 | Yoshioka et al. | May 2008 | B2 |
7421334 | Dahlgren | Sep 2008 | B2 |
7512487 | Golding et al. | Mar 2009 | B1 |
7546202 | Oh | Jun 2009 | B2 |
7590490 | Clark | Sep 2009 | B2 |
20010018628 | Jenkins et al. | Aug 2001 | A1 |
20020151315 | Hendrey | Oct 2002 | A1 |
20030036842 | Hancock | Feb 2003 | A1 |
20030036848 | Sheha et al. | Feb 2003 | A1 |
20030167120 | Kawasaki | Sep 2003 | A1 |
20030182052 | DeLorme et al. | Sep 2003 | A1 |
20030191578 | Paulauskas et al. | Oct 2003 | A1 |
20040049339 | Kober et al. | Mar 2004 | A1 |
20050021226 | Kustosch | Jan 2005 | A1 |
20050107948 | Catalinotto | May 2005 | A1 |
20060080031 | Cooper et al. | Apr 2006 | A1 |
20060089788 | Laverty | Apr 2006 | A1 |
20060106534 | Kawamata et al. | May 2006 | A1 |
20060212217 | Sheha et al. | Sep 2006 | A1 |
20060265422 | Ando et al. | Nov 2006 | A1 |
20070027628 | Geelen | Feb 2007 | A1 |
20070073480 | Singh | Mar 2007 | A1 |
20070088494 | Rothman et al. | Apr 2007 | A1 |
20070130153 | Nachman et al. | Jun 2007 | A1 |
20070204218 | Weber et al. | Aug 2007 | A1 |
20070213929 | Tanizaki et al. | Sep 2007 | A1 |
20070233384 | Lee et al. | Oct 2007 | A1 |
20080076451 | Sheha et al. | Mar 2008 | A1 |
20080125958 | Boss et al. | May 2008 | A1 |
20080133120 | Romanick | Jun 2008 | A1 |
20080134088 | Tse et al. | Jun 2008 | A1 |
20080177470 | Sutardja | Jul 2008 | A1 |
20080270016 | Proietty et al. | Oct 2008 | A1 |
20090138190 | Kulik | May 2009 | A1 |
20090150064 | Geelen | Jun 2009 | A1 |
20090171584 | Liu | Jul 2009 | A1 |
20090177360 | Kustosch | Jul 2009 | A1 |
20090182498 | Seymour | Jul 2009 | A1 |
20090182500 | Dicke | Jul 2009 | A1 |
20090187340 | Vavrus | Jul 2009 | A1 |
20090187341 | Vavrus | Jul 2009 | A1 |
20090187342 | Vavrus | Jul 2009 | A1 |
Number | Date | Country |
---|---|---|
2001194172 | Jul 2001 | JP |
2002048574 | Feb 2002 | JP |
2006250875 | Sep 2006 | JP |
2007155582 | Jun 2007 | JP |
2007178182 | Jul 2007 | JP |
2008002978 | Jan 2008 | JP |
19990011004 | Feb 1999 | KR |
19990040849 | Jun 1999 | KR |
20020084716 | Nov 2002 | KR |
20040063088 | Jul 2004 | KR |
20040106688 | Dec 2004 | KR |
20060028237 | Mar 2006 | KR |
20060101929 | Sep 2006 | KR |
20070080726 | Aug 2007 | KR |
Number | Date | Country | |
---|---|---|---|
20080221787 A1 | Sep 2008 | US |