Methods and apparatus for estimating power usage

Information

  • Patent Grant
  • 9459111
  • Patent Number
    9,459,111
  • Date Filed
    Wednesday, July 17, 2013
    10 years ago
  • Date Issued
    Tuesday, October 4, 2016
    7 years ago
  • CPC
  • Field of Search
    • US
    • 701 022000
    • 701 029500
    • 701 036000
    • 701 117000
    • 701 533000
    • 701 428000
    • 701 532000
    • 701 118000
    • 701 123000
    • 340 539110
    • 340 540000
    • 340 984000
    • 705 014100
    • 706 062000
    • 703 008000
    • CPC
    • G01C21/3469
    • G01C21/34
    • G01C21/32
    • G01C21/3446
    • G01C21/20
    • G01C21/3679
    • G01C21/3407
    • G01C21/3423
    • G01C21/3415
    • G01C21/3691
    • G01C21/36
    • G01C21/3484
    • G01C21/3617
    • B60K6/48
    • B60K35/00
    • B60K37/06
    • B60R16/0236
    • B63J99/00
    • G08B25/08
    • G06Q30/06
    • G06Q10/04
    • G06Q50/06
    • B60W40/09
    • G07C5/0816
    • G01R11/46
    • B69R16/0236
    • G08G1/0133
  • International Classifications
    • G01C21/34
    • Term Extension
      62
Abstract
A computer-implemented method includes establishing a road network model on which a plurality of simulated vehicles may be run. The method also includes setting up a plurality of scenarios under which vehicle driving conditions vary to be run on the road network model. The illustrative method includes receiving energy usage related data for a plurality of simulated vehicles run in at least one of the plurality of scenarios on the road network model. The method further includes calculating a total energy consumption for each of the vehicles. The method additionally includes repeating the receiving and calculating steps to determine how various elements of the road network model and scenarios effect vehicle energy consumption.
Description
TECHNICAL FIELD

The illustrative embodiments generally relate to methods and apparatus for estimating power usage.


BACKGROUND

Evaluating real world fuel consumption of a vehicle is useful in developing algorithms for low cost routing and distance-to-empty. This calculation enables vehicle features that can result in significant fuel and travel time savings. With advances in digital systems, there is an explosion of inputs available to electronic vehicle features that can influence emissions, energy consumption and travel time.


Traffic simulation tools help in replicating real life traffic and driver behavior. Different scenarios can be analyzed to understand vehicle behavior under varying conditions.


Marketing studies have revealed that range anxiety is the number one concern for battery electric vehicle (BEV) owners. The illustrative embodiments enable vehicle features that can eliminate range anxiety by presenting real-world estimates of distance to empty and also ensure the best fuel economy by presenting low energy routes.


SUMMARY

In a first illustrative embodiment, a computer-implemented method includes establishing a road network model on which a plurality of simulated vehicles may be run. The illustrative method also includes setting up a plurality of scenarios under which vehicle driving conditions vary to be run on the road network model.


Also, the illustrative method includes receiving energy usage related data for a plurality of simulated vehicles run in at least one of the plurality of scenarios on the road network model. The illustrative method further includes calculating a total energy consumption for each of the vehicles.


The illustrative method additionally includes repeating the receiving and calculating steps to determine how various elements of the road network model and scenarios effect vehicle energy consumption.


In a second illustrative embodiment, a computer implemented method includes breaking a route into a plurality of segments having the same or a similar energy use affecting characteristic. This illustrative method also includes assigning a total energy usage cost to the segment based on one or more energy use affecting characteristics of each segment.


Further, this illustrative method includes adding the total energy usage cost of all segments comprising a route to determine a total route energy cost and repeating the adding step for a plurality of routes comprised of varying segments between a current location and a destination. This illustrative method additionally includes presenting a driver with the route having the lowest total route energy cost.


In a third illustrative embodiment, a machine readable storage medium stores instructions that, when executed, cause a processor to perform the method including establishing a road network model on which a plurality of simulated vehicles may be run. The exemplary method also includes setting up a plurality of scenarios under which vehicle driving conditions vary to be run on the road network model.


Further, the illustrative method includes receiving energy usage related data for a plurality of simulated vehicles run in at least one of the plurality of scenarios on the road network model and calculating a total energy consumption for each of the vehicles. Also, the illustrative method includes repeating the receiving and calculating steps to determine how various elements of the road network model and scenarios effect vehicle energy consumption.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows an illustrative example of a fuel efficiency testing process;



FIG. 2 shows an illustrative example of a road network modeling process;



FIG. 3 shows an illustrative example of a scenario setup process; and



FIG. 4 shows an illustrative example of an energy consumption determination process.





DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.


Evaluating the real world fuel consumption of a vehicle is one method of developing algorithms for low-cost routing and distance-to-empty. This calculation enables vehicle features that can result in significant fuel and travel time savings. With advances in digital systems, there is an explosion of inputs available to electronic vehicle features that can influence emissions, energy consumption and travel time. Making use of this data will eventually result in cost savings for a consumer.


Traffic simulation tools help in replicating real life traffic and driver behavior. Different scenarios can be analyzed to understand the most important influencers on real world fuel economy. The energy consumption under different traffic and road conditions can also be evaluated using traffic simulation.


The illustrative embodiment reflect development of software modules for embedded and cloud-based applications that receives inputs such as driver characteristics, road topology, vehicle characteristics, weather, traffic, etc., and output energy consumption for route optimization and distance to empty computations. This can also enable applications on embedded platforms such as SYNC, mobile platforms such as smart phones and in web-based applications in the cloud.


The illustrative embodiments enable vehicle features that can eliminate range anxiety by presenting real-world estimates of distance to empty and also ensure the best fuel economy by presenting low energy routes.


The illustrative embodiments include a laboratory method of computing real-world fuel consumption from external data available in digital formats. The external data available in digital formats is used as an input into a traffic simulator called VISSIM2, which can generate realistic drive cycles. Drive cycles are then input into a powertrain simulation to compute energy along a specific route for a specific vehicle. The energies for the entire set of vehicles are statistically analyzed for average energy consumption and the expectation interval energy consumption along the route.


A method of computing energy from drive cycles called modeFrontier is introduced and makes the energy consumption analysis much simpler and more suitable for embedded processors and cloud-based applications. Four dimensional energy tables are populated with energy values using CVSP, with the dimensions being vehicle weight, speed, road gradient and accessory loads. Actual road gradient and vehicle acceleration from the VISSIM drive cycle are combined into a singled variable for use in the tables. Throughout any simulated drive only the speed and vehicle acceleration vary, so the table was divided into sub-tables for each accessory load and vehicle weight. A cubic spline surface was created in the speed and road gradient dimensions for each sub-table to more accurately estimate the fuel consumption.


sCVSP was also used to compute the maximum acceleration the vehicle is capable of at a specific weight, road gradient and speed. This was passed into VISSIM manually as an acceleration-velocity curve. If this curve was incorrect the accelerations would be either too large for the vehicle to achieve or never large enough to represent maximum vehicle acceleration.


VISSIM is a simulation package that can analyze private and public transport operations under constraints such as lane configuration, traffic composition, traffic signals, public transportation stops, etc., thus making it a useful tool for the evaluation of various alternatives based on transportation engineering and planning measures of effectiveness.


VISSIM can be applied as a useful tool in a variety of transportation problem settings. The following list provides a selective overview of previous applications of VISSIM:

  • a. Development, evaluation and fine-tuning of signal priority logic;
  • b. Evaluation and optimization of traffic operations in a combined network of coordinated and actuated traffic signals;
  • c. Feasibility and traffic impact studies of integrating light rail into urban street networks;
  • d. Analysis of slow speed weaving and merging areas;
  • e. Easy comparison of design alternatives including signalized and stop sign controlled intersections, roundabouts and grade separated interchanges;
  • f. Capacity and operations analysis of complex station layouts for light rail and bus systems;
  • g. With its built-in Dynamic Assignment model, VISSIM can answer route choice dependent questions such as the impacts of variable message signs or the potential for traffic diversion into neighborhoods for networks up to the size of medium sized cities; and
  • h. Modeling and simulating flows of pedestrians—in streets and buildings—allow for a wide range of new applications. VISSIM can also simulate and visualize the interactions between road traffic and pedestrians.


The traffic simulator is a microscopic traffic flow simulation model including the car following and lane change logic. The signal state generator is a signal control software pooling detector information from the traffic simulator on a discrete time step basis (down to 1/10 of a second). It then determines the signal status for the following time step and returns this information to the traffic simulator.


The accuracy of a traffic simulation model is mainly dependent on the quality of the vehicle modeling, e.g., the methodology of moving vehicles through the network. In contrast to less complex models using constant speeds and deterministic car following logic, VISSIM uses the psycho-physical driver behavior model developed by WIEDEMANN4. The basic concept of this model is that the driver of a faster moving vehicle starts to decelerate as he reaches his individual perception threshold when approaching a slower moving vehicle. Since he cannot precisely determine the speed of the other vehicle, his speed will fall below that vehicle's speed until he starts to slightly accelerate again after reaching another perception threshold. This results in an iterative process of acceleration and deceleration.


Stochastic distributions of speed and spacing thresholds replicate individual driver behavior characteristics. VISSIM's traffic simulator not only allows drivers on multiple lane roadways to react to preceding vehicles (4 by default), but also neighboring vehicles on the adjacent travel lanes are taken into account. The alertness of drivers approaching a traffic signal is increased within 100 meters of a stop line.


Some of the VISSIM model inputs are listed below:

  • a. Behavior of the driver-vehicle-unit;
  • b. Psycho-physical sensitivity thresholds;
  • c. Ability to estimate distance;
  • d. Aggressiveness;
  • e. Memory of the driver;
  • f. Actual acceleration/deceleration based on current speed and desired speed and aggressiveness;
  • g. Accessory usage based on weather, daylight and driver preferences;
  • h. Interdependence of driver-vehicle units;
  • i. Rules to define relationships between leading and following vehicles;
  • j. Rules to define the relationship between vehicles in adjacent travel lanes;
  • k. Rules to define behavior at intersections and traffic signals;
  • l. Actual speed and acceleration;
  • m. Behavior of driver-vehicle units with respect to the road;
  • n. Speed limits;
  • o. Number of lanes;
  • p. Behavior of driver-vehicle units with respect to traffic;
  • q. Road model with speed limits, lanes, and gradient;
  • r. Volume of vehicles in the road model;
  • s. Distribution of vehicle lengths, top speeds and maximum acceleration; and
  • t. Traffic control devices, timing, etc.


The ability of the simulator to depict real life traffic scenarios and driving behavior is extremely useful in understanding the different road or traffic or driver characteristics that affect the energy consumption of a battery electric vehicle.


sCVSP is the corporate standard tool for vehicle performance and fuel economy modeling and simulation. Among its main features are:

  • a. Used on Ford vehicle programs to set Performance & Fuel Economy targets;
  • b. Model architecture and subsystem interfaces allow interchange subsystem and component models based on vehicle hardware. A global bus enables the communication between the vehicle system control (VSC) and vehicle components;
  • c. Includes extensive set of component models that have been developed over the years and are validated with test data;
  • d. Includes extensive vehicle and component parameter database. These parameters can be calibrated and optimized to improve vehicle performance;
  • e. Supported by company-wide processes to generate vehicle and component parameter data for new programs;
  • f. Includes standard test management and report generating capabilities that allow design engineers understand the behavior of components, subsystems and the vehicle;
  • g. Features and capabilities can be extended by users;
  • h. New models can be added to existing libraries; and
  • i. New libraries with new models can be added;


In order to have an on-line capability to predict the distance to empty in BEVs, sCVSP energy usage results are computed in advance and recorded in a table as shown below. Each entry in the table is the work needed for locomotion in Wh/mile for a given speed, acceleration, ground grade, accessory load and vehicle weight. The vehicle weight was simplified and parameterized by the number of passengers in the vehicle assuming 150 lbs for a passenger. The work is provided at the battery terminals as well as at the wheels The former value includes parasitic losses in the powertrain but not parasitic losses in the battery.


In the calculation the large table is reduced to separate 2-dimensional sub-tables for a specific accLoad and number of passengers. The sub-tables have two variables remaining, % grade and VehSpeed, that are the only variables that change during a single drive cycle. The sub-tables are further reduced to a cubic spline surface dimensioned by % grade and vehicle speed. The values computed by sCVSP become the corner nodes for each value in the table. These cubic-spline surfaces are then used to estimate the power from the drive cycle, with vehicle acceleration and actual road grade combined into the single % grade value.























custom character


custom character


custom character


custom character


custom character


custom character


custom character


custom character


custom character


custom character


custom character



tacc_load_Wat
grade_perc
speed_kph
batt_whr
batt_whr
batt_whr
batt_whr
whl_whr
whl_whr
whl_whr
whl_whr

























400.000
−6.00
10.0
−212.72
−225.22
−237.70
−250.20
−376.63
−392.66
−408.67
−424.70


400.000
−6.00
30.0
−288.43
−302.73
−317.01
−331.31
−354.00
−369.90
−385.78
−401.68


400.000
−6.00
50.0
−273.35
−287.92
−302.46
−317.01
−318.89
−334.68
−350.45
−366.23


400.000
−6.00
70.0
−234.25
−248.99
−263.60
−278.22
−270.65
−286.35
−302.01
−317.68


400.000
−6.00
90.0
−177.01
−191.77
−206.49
−221.23
−208.58
−224.18
−239.75
−255.34


400.000
−6.00
110.0
−104.60
−119.24
−133.85
−148.47
−133.27
−148.79
−164.27
−179.77


400.000
−6.00
130.0
−19.74
−34.20
−48.60
−63.02
−44.44
−59.90
−75.31
−90.74


400.000
−4.00
10.0
−96.92
−104.94
−112.94
−120.95
−229.18
−239.28
−249.35
−259.44


400.000
−4.00
30.0
−154.64
−163.76
−172.86
−181.97
−206.56
−216.53
−226.47
−236.44


400.000
−4.00
50.0
−136.31
−145.50
−154.66
−163.83
−171.46
−181.32
−191.15
−200.99


400.000
−4.00
70.0
−95.61
−104.78
−113.93
−123.09
−123.23
−132.99
−142.71
−152.46


400.000
−4.00
90.0
−37.60
−46.74
−55.85
−64.97
−61.17
−70.84
−80.47
−90.12


400.000
−4.00
110.0
36.10
25.94
16.41
7.38
14.14
4.55
−5.00
−14.56


400.000
−4.00
130.0
131.83
121.66
111.53
101.38
102.95
93.43
83.95
74.46


400.000
−2.00
10.0
20.48
17.19
13.92
10.63
−81.38
−85.52
−89.64
−93.78


400.000
−2.00
30.0
−19.47
−23.15
−26.80
−30.47
−58.77
−62.78
−66.78
−70.79









sCVSP was also used to compute the maximum acceleration verses time as an input into VISSIM. sCVSP simulations of the three EPA cycles demonstrate the extremes of maximum accelerations imposed by the sCVSP model of the vehicle. It is necessary that VISSIM and sCVSP have the same acceleration limits or VISSIM will generate accelerations that cannot be achieved by the vehicle. The lower bound of acceleration (maximum deceleration) was −0.85 at zero mph, varying linearly to −0.75 at 80 mph; theoretically it may be possible to have greater decelerations.



FIG. 1 shows an illustrative example of a fuel efficiency testing process. In this illustrative embodiment, a road network model is first established 201. In at least one example, the model is established in a VISSIM environment.


Next, a plurality of scenarios is setup under which testing conditions can be performed on the road model 203. Multiple replications of the scenarios are run to establish baseline results 204, providing aggregate data with a high degree of accuracy.


For each relevant virtual vehicle in a given scenario, speed, acceleration, distance traveled, etc., are obtained 205, and this data is fed into calculation software 207. Fuel consumption for that vehicle is then calculated based on the inputs 208. From this data, total energy consumption can then be determined 209.


After a given scenario is completed, the process can advance to a next scenario 211.



FIG. 2 shows an illustrative example of a road network modeling process. The road network under consideration is set-up in the traffic simulator. The geometry 301 and length of the road 303, number of lanes 305, vehicle flows 307, vehicle compositions 309, desired speeds 311, traffic signal data 313, the driver model 315, etc. are some of the inputs that may need to be set-up before running the simulation. Additional inputs may be added to the simulator as desired, and not all of the previously mentioned inputs need to be used.



FIG. 3 shows an illustrative example of a scenario setup process. In this illustrative example, a particular scenario is selected for initialization 401. Road characteristics may be input 403 if desired. For example, without limitation, gradient 405 and/or number of lanes 407 may be adjusted.


Also, in this embodiment, traffic characteristics 409 may be input for the scenario. This may include, but are not limited to, a vehicle flow rate 411 and a vehicle mix 413.


Further, in this illustrative embodiment, driver characteristics may be input 415 to represent certain driving behaviors. These characteristics may include, but are not limited to, driver speeds 417 and cruise control usage data 419.


Also, in this example, weather data may be input for the scenario 421. This data may include, but is not limited to, visibility adjustments 423 and temperature adjustments 425.



FIG. 4 shows an illustrative example of an energy consumption determination process.


The parameters used to calculate the energy consumed by a particular battery electric vehicle during a simulation run may include: speed 503, acceleration 505, distance travelled 507, accessory loads and number of passengers. VISSIM can output the speed, acceleration and distance travelled by all the vehicles in the simulation at every instant (every second in this case). The number of passengers is fixed at one and the accessory loads are assumed to remain fixed throughout the simulation run. It should be noted that the accessory loads affect only the eventual energy consumption and not the drive cycle.


Using the energy tables from sCVSP the outputs from VISSIM are processed in MATLAB (or C-code on board the vehicle) 509 to get the energy consumption by the battery electric vehicles in a given scenario 511. The acceleration/deceleration values from VISSIM are mapped into corresponding gradient values and thereby taking into account the regenerative ability of a battery electric vehicle during braking 513. A MATLAB/C code calculates the energy consumed at each and every time instant for each electric vehicle and sums them to give the total energy consumption 515. Regenerative capability of a battery electric vehicle is considered in the energy tables.


The models used by the traffic simulator are stochastic in nature. Hence, for a given scenario and a particular simulation run, each of the battery electric vehicles will have a different drive cycle and therefore different energy usage. A characteristic of a particular simulation is the statistical variance of the energy utilization of large samples of vehicle. The sample size can be determined by plotting the variance (or standard deviation) verses sample size and observing the point at which the variance approaches a steady state. Based this analysis 120 vehicles was selected as a reasonable sample size.


It was observed that, in this example, variation in standard deviation is negligible once the sample size is more than 120. Hence, averaging the energy values of 120 vehicles for each scenario would provide good statistics. In order to get a sample size of at least 120 vehicles, the simulation needs to be run multiple times depending on the scenario being tested. For example, assuming the flow to be 2000 vehicle per hour with 2% battery electric vehicles and a simulation time of one hour, at least 4 simulation runs need to be performed to get a good sample of 120 vehicles. It should be noted that in a particular run, only those vehicles are chosen which traverse the whole road length. Vehicles which are unable to complete the whole trip are excluded from the energy calculations.


Presenting the mean energy consumed in a given scenario is not enough. It is important to know the variation in the values. Hence, the mean energy values are associated with a ‘confidence interval’. A confidence interval is a range of numbers relevant to the parameter of interest. For example, a 95% confidence interval means that if we repeatedly draw samples of a given size N from a certain population and we construct a confidence interval for each sample, then 95% of these intervals on average will contain the true value of the unknown parameter as an interior point. It is incorrect to interpret a 95% confidence interval to mean that there is a 95% chance that the interval contains the true value of the unknown parameter as an interior point. This is because there is one value of the unknown parameter, and the confidence interval either contains this value or does not contain it.


Thus, confidence intervals should not be interpreted as probabilities but should rather be interpreted in the context of repeated sampling.


Through testing, it can be seen that gradient has a prominent effect on the energy consumption of a battery electric vehicle. There is a rapid increase in the energy values as we move from a gradient of −4% to 4%. This is because, the vehicle needs more energy to climb uphill (positive gradient) and it can gain energy through regenerative braking while going downhill (negative gradient). Relatively, congestion doesn't seem to have a big effect on the energy usage.


There is a slight reduction in energy as the flow conditions approach a congested scenario. This effect is directly related to the decrease in the speeds for congested flows.


Also, speed of the vehicles has a big impact on the energy consumption. A vehicle travelling at around 100 km/hr will consume about 30% more energy than a vehicle travelling at around 80 km/hr. Also, the number of lanes on the freeway doesn't seem to have an effect on the overall energy consumption.


It can be seen that the vehicles travelling in cruise control use significantly lower energy than the vehicles travelling without cruise. The fluctuations in acceleration/deceleration and hence the speed results in higher energy consumption for vehicles which are not using cruise control. The drop in energy consumption with increase in flow values is directly related to the drop in speeds as the flow conditions become congested. It should also be noted that the energy consumption and its variation remains fixed across different flow values when the cruise control is set to 80 km/hr. But, in the case of cruise control at 100 km/hr, there is a larger statistical variance in energy usage (dotted lines diverge) as the flow values increase. This is because at high flows, the vehicles are unable to maintain a cruise speed of 100 km/hr due to the increase in flow density. But, the vehicles seem to maintain a cruise speed of 80 km/hr even when the traffic flow increases.


The effect of accessory loads is comparable to the effect of flow conditions. For example, a vehicle travelling in a congested road (6000 vehicles per hour) and a hot weather (2000 W accessory load) uses almost the same energy as that used by a vehicle travelling in free flow (2000 vehicles per hour) and a cold weather (800 W accessory load).


For a given accessory load the energy usage is the lowest for a residential road and highest for a freeway, mainly because of low speeds and stop-go nature of traffic on a residential road.


In fact, the energy usage per mile with 400 W accessory load is more than halved from a freeway to a residential road. But, the travel time on a residential road is almost four times that on a freeway. This shows a trade-off between travel times and energy usage. Increase in the accessory loads has very little impact on the energy usage on a freeway where high speed is the primary driver of energy consumed. On the other hand, the accessory loads drastically affect the energy usage on a residential road to such an extent that, the energy used per mile with 2000 W accessory load is almost the same as that on an urban road.


The energy consumption results from various scenarios across different road types have been analyzed to understand the various factors that affect energy consumption of a battery electric vehicle. The results show that road gradient has a very significant effect on the energy usage across all the three road types—freeway, urban roads and residential roads. Accessory loads have a strong effect across different road types. The results show that at very high accessory loads the energy usage on a residential road is equal to the energy used on an urban road, although there is a difference in the desired speeds on these road types.


The speed of the vehicles also has a prominent effect on the energy usage. Cruise control on freeways helps in reducing the energy cost. Also, significant energy gains are possible in stop-go traffic scenarios because of regenerative braking in a battery electric vehicle. Hence, urban roads with traffic signals and residential roads are likely to be preferred over freeways to achieve lower energy consumption. But, it should be noted that there is a trade-off here, between energy consumed and travel times.


The results can be used to develop cost functions that can evaluate the total energy consumed along various possible routes between an origin and destination and finally give the customer the minimum energy route. One way of using the results in the cost function is through the use of energy look-up tables and polynomial curve fitting. For example, any route can be broken up into segments which have the same characteristic, (either road type or gradient or speed limits, etc.) and each segment can be assigned a cost which is equal to the energy consumed by the vehicle to travel that segment. Adding up the costs across all the segments will give the overall cost to travel that particular route. This can be done for all possible routes between two locations and the final output could be the route which uses the lowest amount of energy. Energies on different segments can be calculated by fitting a polynomial curve to available data.


Accessory loads can be related to the weather and temperature conditions. Hence, overall, accessory loads will have a significant effect in deciding which road type to choose while making a certain trip.


There is hardly any change in the energy consumption of a battery electric vehicle when the % of heavy goods vehicles is increase from 4% to 10%. A significant change in energy consumption ‘might’ occur when the % of heavy goods vehicles is increased to an even higher value.


While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention.

Claims
  • 1. A computer-implemented routing method comprising: by at least one processor at a server, receiving, via a web-based application executing on a computer in communication with the server, a route origin and a route destination,identifying alternative routes between the route origin and route destination;in response to identified alternative routes between the route origin and route destination, segmenting each of the identified alternative routes based on at least one of a different road, road type and speed limit;calculating an estimated monetary fuel consumption cost for each of the alternative routes based on a calculated cost for each segment in an alternative route and a fuel economy target for a specific vehicle, andoutputting for display at the computer, via the web-based application, the estimated monetary fuel consumption costs together with the alternative routes.
  • 2. The computer-implemented routing method of claim 1 further comprising identifying one of the alternative routes as a minimum energy route based on the estimated monetary fuel consumption costs.
  • 3. The computer-implemented routing method of claim 1 further comprising outputting for display segments for at least one of the alternative routes.
  • 4. The computer-implemented routing method of claim 1 further comprising, outputting for display traffic operations, speed limit, number of lanes, or road gradient for at least one of the alternative routes.
  • 5. A computer system comprising: a processor in an embedded platform configured toreceive input for a specific vehicle including a route origin and a route destination,receive at least one vehicle characteristic including fuel economy for the specific vehicle,identify alternative routes between the route origin and route destination,segment each of the identified alternative routes based on at least one of a different road, road type and speed limit,calculate a monetary energy consumption cost for each of the alternative routes based on each segment and the vehicle characteristics, andoutput for display the monetary energy consumption costs together with the alternative routes.
  • 6. The computer system of claim 5 wherein the embedded platform is a vehicle system.
  • 7. The computer system of claim 5 wherein the processor is further configured to enable a web-based application to receive the origin, destination and at least one vehicle characteristic.
  • 8. The computer system of claim 5 wherein the processor is further configured to enable a web-based application to display the monetary energy consumption costs with the alternative routes.
  • 9. The computer system of claim 5 wherein the processor is further configured to output for display the segments for at least one of the alternative routes.
  • 10. The computer system of claim 5 wherein the monetary energy consumption costs are a monetary value associated with energy consumption of a battery or fuel consumption of an engine.
  • 11. A non-transitory computer readable storage medium storing instructions that, when executed by a processor, cause the processor to in response to a route origin and a route destination, identify alternative routes sharing a segment between the route origin and route destination;calculate an estimated fuel consumption cost for each of the alternative routes based on fuel economy targets for a specific vehicle; anddisplay the estimated fuel consumption costs together with the alternative routes.
  • 12. The non-transitory computer readable storage medium of claim 11 wherein the instructions, when executed by the processor, further cause the processor to identify one of the alternative routes as a minimum energy route based on the estimated fuel consumption costs.
  • 13. The non-transitory computer readable storage medium of claim 11 wherein the instructions, when executed by the processor, further cause the processor to segment at least one of the identified alternative routes.
  • 14. The non-transitory computer readable storage medium of claim 11 wherein the instructions, when executed by the processor, further cause the processor to output for display the segments for at least one of the alternative routes.
  • 15. The non-transitory computer readable storage medium of claim 11 wherein the instructions, when executed by the processor, further cause the processor to output for display traffic operations, speed limit, number of lanes, or road gradient for at least one of the alternative routes.
  • 16. The non-transitory computer readable storage medium of claim 11 wherein the instructions, when executed by the processor, further cause the processor to enable a web-based application to receive the origin, destination and fuel economy targets for the vehicle.
  • 17. The non-transitory computer readable storage medium of claim 11 wherein the instructions, when executed by the processor, further cause the processor to enable a web-based application to display the estimated fuel consumption costs with the alternative routes.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 13/207,566 filed Aug. 11, 2011, the disclosure of which is incorporated in its entirety by reference herein.

US Referenced Citations (111)
Number Name Date Kind
5202617 Nor Apr 1993 A
5301113 To et al. Apr 1994 A
5539399 Takahira et al. Jul 1996 A
5686895 Nakai et al. Nov 1997 A
5790976 Boll et al. Aug 1998 A
5892346 Moroto et al. Apr 1999 A
5913917 Murphy Jun 1999 A
5916298 Kroiss et al. Jun 1999 A
6198995 Settles et al. Mar 2001 B1
6337621 Ogino et al. Jan 2002 B1
6587787 Yokota Jul 2003 B1
6591185 Polidi et al. Jul 2003 B1
6836728 Shimabara Dec 2004 B2
6864807 Todoriki et al. Mar 2005 B2
6947732 Fraser Sep 2005 B2
7127350 Oikubo Oct 2006 B2
7142664 Seligmann Nov 2006 B2
7149623 Flick Dec 2006 B2
7274987 Ishiguro Sep 2007 B2
7277780 Meier-Arendt et al. Oct 2007 B2
7346630 Eichstaedt et al. Mar 2008 B2
7402978 Pryor Jul 2008 B2
7433714 Howard et al. Oct 2008 B2
7444384 Horvitz Oct 2008 B2
7586956 Mishra et al. Sep 2009 B1
7668644 Tengler et al. Feb 2010 B2
7873466 Kong Jan 2011 B2
7925426 Koebler et al. Apr 2011 B2
8000842 Yi et al. Aug 2011 B2
8005453 Van Bosch et al. Aug 2011 B2
8103434 Helbing et al. Jan 2012 B2
8239127 Kono et al. Aug 2012 B2
8255152 Barth et al. Aug 2012 B2
8284039 Baker et al. Oct 2012 B2
8290695 Hiestermann et al. Oct 2012 B2
8290701 Mason et al. Oct 2012 B2
8294286 Hunter Oct 2012 B2
8401792 Yeh et al. Mar 2013 B2
8478642 Dey et al. Jul 2013 B2
8504236 Guo et al. Aug 2013 B2
20020164998 Younis Nov 2002 A1
20030023374 Shimabara Jan 2003 A1
20040073643 Hayes et al. Apr 2004 A1
20040162669 Nagamasa Aug 2004 A1
20040243307 Geelen Dec 2004 A1
20050080552 Feldman et al. Apr 2005 A1
20060002413 Tsutazawa et al. Jan 2006 A1
20060007022 Endo et al. Jan 2006 A1
20060167601 Henning et al. Jul 2006 A1
20060290490 Kraus et al. Dec 2006 A1
20070052552 Suzuki Mar 2007 A1
20070112475 Koebler et al. May 2007 A1
20070150171 Tengler et al. Jun 2007 A1
20070271035 Stoschek et al. Nov 2007 A1
20080027606 Helm Jan 2008 A1
20080042489 Lewis et al. Feb 2008 A1
20080294330 Sasano Nov 2008 A1
20090021218 Kelty et al. Jan 2009 A1
20090099992 Horvitz Apr 2009 A1
20090109022 Gangopadhyay et al. Apr 2009 A1
20090110163 Gupta Apr 2009 A1
20090119385 Horvitz May 2009 A1
20090138188 Kores et al. May 2009 A1
20090141173 Pugel Jun 2009 A1
20090265099 Gottlieb Oct 2009 A1
20090287408 Gerdes Nov 2009 A1
20090309709 Bevacqua et al. Dec 2009 A1
20100010732 Hartman Jan 2010 A1
20100017249 Fincham et al. Jan 2010 A1
20100060016 Hunter Mar 2010 A1
20100070253 Hirata et al. Mar 2010 A1
20100094496 Hershkovitz et al. Apr 2010 A1
20100106514 Cox Apr 2010 A1
20100106603 Dey et al. Apr 2010 A1
20100110077 Grossman et al. May 2010 A1
20100131188 Yeh et al. May 2010 A1
20100138142 Pease Jun 2010 A1
20100169008 Niwa et al. Jul 2010 A1
20100207772 Yamamoto Aug 2010 A1
20100235076 Ofek et al. Sep 2010 A1
20100237985 Landau-Holdsworth et al. Sep 2010 A1
20100256830 Kressner et al. Oct 2010 A1
20100274689 Hammad et al. Oct 2010 A1
20100286909 Tate, Jr. et al. Nov 2010 A1
20110040438 Kluge et al. Feb 2011 A1
20110060495 Kono et al. Mar 2011 A1
20110060517 Kono et al. Mar 2011 A1
20110080282 Kleve et al. Apr 2011 A1
20110095914 Velado Apr 2011 A1
20110125357 Harumoto et al. May 2011 A1
20110166748 Schneider Jul 2011 A1
20110191265 Lowenthal et al. Aug 2011 A1
20110224841 Profitt-Brown et al. Sep 2011 A1
20110224852 Profitt-Brown et al. Sep 2011 A1
20110225105 Scholer et al. Sep 2011 A1
20110238457 Mason et al. Sep 2011 A1
20110251789 Sanders et al. Oct 2011 A1
20110307166 Hiestermann et al. Dec 2011 A1
20110309926 Eikelenberg et al. Dec 2011 A1
20120016551 Krause et al. Jan 2012 A1
20120016576 Huang et al. Jan 2012 A1
20120022904 Mason et al. Jan 2012 A1
20120029800 Kluge et al. Feb 2012 A1
20120065831 Ross et al. Mar 2012 A1
20120072096 Chapman Mar 2012 A1
20120158299 Cerecke et al. Jun 2012 A1
20120179315 Tate et al. Jul 2012 A1
20120179362 Stille Jul 2012 A1
20120209579 Fansler Aug 2012 A1
20120232783 Calkins et al. Sep 2012 A1
20120271542 Arcot et al. Oct 2012 A1
Foreign Referenced Citations (4)
Number Date Country
2102598 Jan 2013 EP
WO 2009031021 Mar 2009 WO
2011035427 Mar 2011 WO
2011035427 Mar 2011 WO
Non-Patent Literature Citations (15)
Entry
Ford Motor Company, “SYNC with Navigation System,” Owner's Guide Supplement, SYNC System Version 1 (Jul. 2007).
Ford Motor Company, “SYNC,” Owners's Guide Supplement, SYNC System Version 1 (Nov. 2007).
Ford Motor Company, “SYNC with Navigation System,” Owner's Guide Supplement, SYNC System Version 2 (Oct. 2008).
Ford Motor Company, “SYNC,” Owner's Guide Supplement, SYNC System Version 2 (Oct. 2008).
Ford Motor Company, “SYNC with Navigation System,” Owner's Guide Supplement, SYNC System Version 3 (Jul. 2009).
Ford Motor Company, “SYNC,” Owner's Guide Supplement, SYNC System Version 3 (Aug. 2009).
Kermit Whitfield, “A hitchhiker's guide to the telematics ecosystem,” Automotive Design & Production, Oct. 2003, http://findarticles.com, pp. 103.
News Release, “Chevrolet and OnStar Give Volt Owners 24/7 Connection and Control via Wireless Smartphone Application”, released Jan. 5, 2010.
Josie Garthwaite, “GM's Volt to Launch With Cell Phone App for Remote Control”, Jan. 6, 2010, printed from http:/gigaom.com/cleantech/gms-volt-to-launch-with-cell-phone-app-for-remote-control/, Dec. 30, 2010.
GM Onstar Mobile Demonstration Capability for Volt img. retrieved from: Hayes, JW, “GM OnStar App for Chevy Volt”. Auto and Racing News, Jan. 6, 2010. <http://autoandracingnews.wordpress.com/2010/01/06/gm-onstar-app-for-chevy-volt/>.
BlackBerry Curve Series, BlackBerry Curve 9300/9330—Smartphones User Guide, Version: 6.0 (2011), pp. 144.
BlackBerry Curve Series, BlackBerry Curve 9300/9330—Smartphones User Guide, Version: 6.0 (2011).
ACDelco, TechConnect, Battery Killers Common Causes of Battery Failure, Jan. & Feb. 2012, pp. 1-8.
Ford Motor Company, “SYNC,” Owner's Guide Supplement, SYNC System Version 1 (Nov. 2007).
Kermit Whitfield, “A hitchhiker's guide to the telematics ecosystem”, Automotive Design & Production, Oct. 2003, http://findarticles.com, pp. 1-3.
Related Publications (1)
Number Date Country
20130304380 A1 Nov 2013 US
Continuations (1)
Number Date Country
Parent 13207566 Aug 2011 US
Child 13944470 US