Patent Grant
10289651
Modern vehicles are often equipped with sophisticated controllers that enable vehicle performance characteristics to be optimized for specific needs. An engine manufacturer may use different programming to logic to vary the engine performance characteristics, including horsepower delivered, according to the needs of a specific customer or class of customers. For example, trucks sold for use in over the road trucking, operating for most of their service life on highways, require different performance characteristics than similar trucks operating for most of their service life on city streets in stop-and-go traffic. A fuel map refers to a set of programming instructions that can be input into an engine control unit (an ECU) to modify performance characteristics of an engine.
As used herein and in the claims that follow, the term fuel map refers to a specific program (i.e., a set of machine instructions) used by an engine control unit (ECU) to determine how to respond to various sensor inputs (i.e., changes in driving conditions). The ECU generally responds to changing inputs by changing at least one of the following parameters: fuel flow rate, spark timing, and idle speed. Changing the fuel map (i.e., the instruction set used by the ECU) will change the performance characteristics of the engine. Manufacturers generally select a fuel map to provide satisfactory vehicle performance over a wide range of conditions.
Other ECU programming instructions sets can be used to modify other performance characteristics, such as maximum road speed, maximum RMP, maximum idle time, etc.
In general, modification of such programming instructions sets requires a replacement instruction set, a hardware interface to be coupled to a vehicle data port (enabling the instruction set to be sent to the appropriate ECU), and a software interface or software application to manage the replacement. Some third party vendors sells kits enabling vehicle owners to perform their own ECU reprogramming using a laptop and a custom hardware interface, programming set, and software application (generally the hardware interface, programming set, and software application are sold together as a kit). Otherwise, vehicle operators need to bring their vehicle to a mechanic to have such ECU reprogramming performed.
It would be desirable to provide vehicle operators with the ability to more readily implement ECU reprogramming. Fuel mapping and other performance related instructions set, customized to the specific performance requirements of a vehicle for a specific route or trip, may lead to more cost efficient operations.
One aspect of the novel concepts presented herein is a method of enabling vehicle operators to more readily implement ECU reprogramming, so that the operator can tailor their vehicle's current ECU programming to current operational requirements, which may be different than the operational characteristics selected by the manufacturer when initially programming the vehicle ECU (or ECUs) with specific instruction sets, such as fuel maps.
In one embodiment, a controller monitors the current operational characteristics of the vehicle, determines the current ECU programming, and determines if a different programming set would be better suited to the current operating conditions. In the event that the current programming set should be replaced, the controller implements the ECU reprogramming. In at least one embodiment, that controller is at the vehicle, while in at least one other embodiment the controller is part of a remote computing system logically connected to the vehicle via a wireless data link.
Significantly, the monitoring of vehicle operational data (the term vehicle operational data includes, but is not limited to; vehicle speed, vehicle location, engine RPMs, engine load, vehicle mass, engine temperature, coolant temperature, engine oil temperature, brake temperature, tire pressure, tire temperature, and fuel use, noting that such parameters are exemplary and not limiting) is done in real-time, either via a controller at the vehicle or a controller remote from the vehicle (where operational data is conveyed from the vehicle to the remote controller in real-time). The term real-time as used herein and the claims that follow is not intended to imply the data is analyzed or transmitted instantaneously, rather the data is collected over a relatively short period of time (over a period of seconds or minutes), and analyzed (or transmitted to the remote computing device on an ongoing basis and analyzed) in a compressed time frame, as opposed to storing the data at the vehicle or remotely for an extended period of time (hour or days) before analysis.
In at least one embodiment, the vehicle is equipped with a position sensor, such as a Global Position System (GPS) device. A controller, either part of the GPS device or another controller at the vehicle uses GPS derived slope data to determine a vehicle's mass, and then uses the vehicle mass data to determine if the current vehicle ECU programming is appropriate. For example, a vehicle operating with a relatively light load may be operated more efficiently using a first set of ECU programming (i.e., a first fuel map), whereas a vehicle operating with a relatively heavy load may be operated more efficiently using a second set of ECU programming (i.e., a second fuel map). Using vehicle mass determined while the vehicle is operating based on GPS derived slope data represents one input that can be used to determine if current ECU programming is appropriate. In the event that the current programming set should be replaced, the controller implements the ECU reprogramming.
Fundamentally, GPS systems calculate velocity in three components (X, Y, Z or N/S, E/W, and Up/Down) based on a Doppler shift of the GPS satellite signals. Scalar speeds can then be calculated from those three components. For example, absolute speed or actual vehicle speed can be determined, as well as ground speed based on the shortest distance between two points (i.e., based on distance as the crow flies). Horizontal ground speed (VHGS) can be calculated using the Pythagorean Theorem. To calculate a grade (G) the vehicle is traveling over (as a percentage), one can take the Z/Up magnitude and divide it by the horizontal ground speed. Replacing Z, x and y with directional vectors (such as Up for Z, West for x and North for y, recognizing that such directional vectors are exemplary, and may change based on the actual GPS data collected from the vehicle) enables one to calculate slope. The slope data is then used to determine the mass of the vehicle at that time. Previous techniques to calculate mass use torque output, engine RPMs, and vehicle velocity to calculate a vehicle's mass or weight, but did not factor in slope, and thus are not accurate over routes including variable slopes (which most routes include). An improved mass metric (by including the GPS derived slope data in a mass calculation) enables a more accurate vehicle weight to be provided.
Note the calculation of vehicle mass using GPS derived slope data can be performed a plurality of times during a specific vehicle trip, and changes in the vehicle mass over time (due to partial unloading or fuel consumption) could trigger additional ECU reprogramming.
Another input that can be used by the controller monitoring the current vehicle ECU programming is vehicle load data entered into an input device by a driver of the vehicle. Such vehicle load data can be based on a vehicle weight provided by a scale, or can be made available on shipping documentation provided to the driver when picking up a load, or can be provided to the driver via a communication from a dispatcher, agent or customer having access to the data defining the load being picked up by the vehicle. The driver will use an input device to provide the vehicle load data to the controller, which then uses the vehicle load data to determine if the current vehicle ECU programming is appropriate. As noted above, using a different fuel map may result in more efficient vehicle operation when a fuel map is correlated to the actual load of the vehicle. Again, the controller will compare the current ECU programming to the loaded state of the vehicle and available ECU programming sets, and in the event that the current programming set should be replaced, the controller implements the ECU reprogramming.
Still another input that can be used by the controller monitoring the current vehicle ECU programming is vehicle load data entered into an input device by a dispatcher or agent at a location remote from the vehicle. In such a case, the controller needs to be coupled to the remote input via a wireless data link, so that vehicle load data input from a remote site can be conveyed to the controller at the vehicle. A GSM or other type of cellular modem can be employed as such a data link (noting that such a data link is exemplary, and not limiting, and other wireless data links, including satellite based data links, can also be employed). Such remotely input vehicle load data can be based on information provided to a dispatcher or broker coordinating transportation of a load by the vehicle in question. The controller uses the remotely input vehicle load data to determine if the current vehicle ECU programming is appropriate, generally as discussed above.
Still another input that can be used by the controller monitoring the current vehicle ECU programming is vehicle routing data. When a vehicle route is known in advance, an analysis of the route can be performed to optimize ECU programming parameters based on the route characteristics. For example, where a first portion of the route involves mountainous terrain, and a second portion of the route involves relatively flat terrain, a first set of ECU programming may provide more efficient vehicle operation for the first portion of the route, while a second set of ECU programming may provide more efficient vehicle operation for the second portion of the route. The analysis of the route and the selected ECU programming parameters may be based on empirical data collected during previous trips over the same route, or may be based on knowledge about the terrain, or combinations thereof. Particularly where a route is repeatedly traversed under similar load conditions, a carrier may vary ECU parameters on different trips while collecting empirical data, so the most efficient ECU parameters can be determined, and used for future trips. The controller at the vehicle tasked with ECU reprogramming can use ECU programming assigned to specific portions of the route, and GPS data collected during operation of the vehicle, to vary the ECU parameters based on the location of the vehicle.
In a related embodiment, the controller at the vehicle that monitors ECU programming states is logically coupled to a GPS device (or other position sensing system) in the vehicle, such that the controller changes the ECU programming based on the GPS location of the vehicle. Predefined ECU programming parameters can be assigned to downhill segments, to uphill segments, to specific altitudes, to relatively flat terrain, and to route segments where speed and heading may remain constant for extended periods (such as long stretches of highway).
It should be understood that in addition to GPS parameters, the controller determining which ECU programming parameters are appropriate for a vehicle based on current operational data inputs can also use other types of data input, such as ambient temperature, time, and date. For example, empirical data or user knowledge might indicate that a first set of ECU programming may lead to more efficient vehicle operation when the ambient temperature is relatively low, while a second set of ECU programming may lead to more efficient vehicle operation when the ambient temperature is relatively high. The ambient temperature can be measured by a sensor in the vehicle, or the ambient temperature can be estimated remotely and conveyed to the vehicle (such as by a weather reporting/predicting service). Similarly, empirical data or user knowledge might indicate that a first set of ECU programming may lead to more efficient vehicle operation during nighttime vehicle operation, while a second set of ECU programming may lead to more efficient vehicle operation during daylight vehicle operation. Daylight/nighttime conditions can be determined remotely and conveyed to the vehicle, or can be measured at the vehicle using light sensors and/or clocks. Similarly, empirical data or user knowledge might indicate that a first set of ECU programming may lead to more efficient vehicle operation during a first season (i.e., summer, fall, winter, spring), while a second set of ECU programming may lead to more efficient vehicle operation during a different season. The current season can be determined remotely and conveyed to the vehicle, or can be measured at the vehicle using a clock/calendar function.
Other operational data that can be used as an input for the controller tasked with reprogramming the vehicle ECU to enhance vehicle efficiency includes engine load (a parameter based in part on vehicle weight and engine RPMs), engine RPMs, engine oil temperature, engine coolant temperature, vehicle speed, transmission gear selection, vehicle weight, cruise control status, accessory device status (such as the use of supplementary cooling fans or power take off units). Different combinations and permeations of such inputs may change the optimal ECU programming selected by the controller. The assignment of optimal ECU programming sets to specific combinations of operation data inputs can be based on empirical data or user knowledge, as well as combinations thereof.
The status of a power take off unit is a special case that may significantly alter the ECU programming associated with optimal efficiency. For example, a power take off unit is used when the engine in the vehicle is not being used to generate horsepower to move the vehicle over the road, but rather to generate horsepower to be used by a mechanical or hydraulic accessory, or to generate electricity to drive an electrically energized accessory. Lift buckets, ladders, hoists are exemplary but not limiting types of accessory units associated with a power take off unit. Often the power required by such accessory units is much less than required for over the road operation, and such accessory components may be used for extended periods of time. Changing ECU programming to optimize efficiency can result in significant performance improvements in fuel consumption, particularly where required performance characteristics for over the road operation vary widely from the required performance characteristics for power take off operation. In some jurisdictions, PTO unit use may not trigger the same emission control requirements, such that it may be possible to bypass emission control systems during PTO, generally for enhanced fuel economy.
While fuel maps have been discussed above as a parameter that can be modified by ECU reprogramming, it should be understood that other parameters can also be modified in accord with the concepts disclosed herein. For example, ECU parameters controlling vehicle shifting patterns can be similarly modified. Different operational input conditions can result in changes to one or more ECU parameters, including but not limited to fuel maps and shift patterns.
In at least some embodiments, ECU programming changes can be done during vehicle operation. In other embodiments, a driver interface component is used to alert the driver that an ECU programming change is required, and the driver will be trained to respond to such an alert by pulling over at a safe location to shut down the vehicle (or idle the vehicle) while the programming change is carried out. Whether or not ECU programming changes are performed during active vehicle operation, vehicle shut done, or vehicle idle will sometimes be based on operator policy (some operators may demand such changes be done at idle or while the vehicle is shut down for safety reasons), and will sometimes be based on the design parameters of the specific ECU being reprogrammed.
In at least one embodiment, the ECU reprogramming is related to a vehicle speed limiter. Some jurisdictions have different speed laws. In such an embodiment, a driver or dispatcher can convey a command to the controller at the vehicle managing the ECU reprogramming to instruct a change in the speed limiter settings. Thus, if a driver (or dispatcher) knows the vehicle is approaching a locality with different speed rules, the driver (or dispatcher, via a remote data link) can instruct the controller to initiate such a change. For example, when a vehicle operating in the US enters Canada, failing to change the speed limiting settings can lead to a fine. Providing an owner/operator or driver with the ability to correct or change the settings when needed will aid in compliance, and reduce liability for drivers. In one related embodiment the driver will have the ability to make an ECU programming regarding speed limit settings by inputting a command in an input device in the vehicle, where the input device is coupled to the controller at the vehicle. In a related embodiment, a third party can remotely access the controller that is able to effect an ECU programming, and will effect such a programming change when requested to do so by a driver or dispatcher (the term dispatcher being intended to encompass any individual authorized to request such a change on behalf of the operator of a vehicle, regardless of their actual title or job duty). In an exemplary embodiment, the third party offers telematics services to the vehicle operator, such as GPS data collection and storage.
This Summary has been provided to introduce a few concepts in a simplified form that are further described in detail below in the Description. However, this Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Various aspects and attendant advantages of one or more exemplary embodiments and modifications thereto will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Figures and Disclosed Embodiments are not Limiting
Exemplary embodiments are illustrated in referenced Figures of the drawings. It is intended that the embodiments and Figures disclosed herein are to be considered illustrative rather than restrictive. No limitation on the scope of the technology and of the claims that follow is to be imputed to the examples shown in the drawings and discussed herein. Further, it should be understood that any feature of one embodiment disclosed herein can be combined with one or more features of any other embodiment that is disclosed, unless otherwise indicated.
Newly Disclosed Subject Matter
The concepts disclosed herein relate to both newly disclosed subject matter and subject matter presented in a previously filed and unpublished application. The previously filed but not published subject matter provides contextual information that is relevant to the new disclosure, hence it inclusion. The newly disclosed subject matter begins with
Exemplary Logic for Determining Driver Performance
GPS unit 44 preferably includes or is connected to a wireless transmitter (not separately shown), such that the GPS data can be wirelessly transmitted to a remote computing device, preferably in real-time. The remote computing device can be programmed to manipulate the GPS data to determine a plurality of metrics, which can then be used to calculate a driver's performance ranking, generally as described above. It should be recognized that as an alternative, GPS unit 44 can include an onboard memory, such that the GPS data are stored in the GPS unit, to be uploaded to a remote computing device at a later time (for example, using a wireless or hardwired data link). Significantly, GPS unit 44 enables driver performance rankings to be determined, even if the vehicle is not equipped with separate other sensors of the metric data or an onboard computer (as are required in the embodiments of
In a block 54, the remote computing device uses the GPS data to determine metrics corresponding to acceleration time and acceleration magnitude. In a block 56, the remote computing device uses the GPS data to determine metrics corresponding to deceleration time and deceleration magnitude. In a block 58, the remote computing device uses the GPS data to determine whether a driver has exceeded a speed limit. Those of ordinary skill in the art will readily recognized that several mapping databases exist that include a database of speed limits and which enable a speed limit for a specific portion of a route being driven by a vehicle to be determined based on a particular geographical coordinate of the vehicle following that route. GPS data includes an indication of the speed of the vehicle at a particular time while the vehicle is at a particular geographical location. Once the vehicle speed has been determined for a particular geographical position, a database can be consulted to determine the speed limit associated with that position along the route, thereby enabling a determination to be made as to whether the driver has exceeded the speed limit. In a block 60, the plurality of metrics calculated from the GPS data are used to determine the driver's performance ranking, generally as described above in connection with
It should be recognized that the GPS data can be used to calculate fewer metrics than those described above in connection with
Preferably, performance rankings are determined for each driver in a company (or each driver of a vehicle for which driver performance is of interest), and posted publicly so that drivers can compare each other's individual performance rankings. The public display of driver performance is expected to provide an incentive for drivers to improve their driving performance rankings.
It should be understood that the concepts disclosed herein encompass many differ types of performance metrics, and different techniques for collecting them. In at least some embodiments, as exemplified by
While specific parameters or metrics used to derive a driver performance metric have been discussed above, it should be recognized that the following different parameters/metrics are specifically encompassed herein. One or more embodiments in which the performance metric is based at least in part from data collected from one or more engine control units (or vehicle computer) in a vehicle operated by the driver whose performance is being measured. One or more embodiments in which the performance metric is based at least in part on fuel economy. One or more embodiments in which the performance metric is based at least in part on carbon footprint reduction. One or more embodiments in which the performance metric is based at least in part on minimizing fuel efficiency robbing behavior, including sudden braking, rapid acceleration and downshifting too early. One or more embodiments in which the performance metric is based at least in part on maximizing fuel efficiency enhancing behavior, including coasting to a stop (instead of staying on the accelerator until the last minute and then braking hard), high average vehicle speeds with minimum time spent at maximum vehicle speed, high percent trip distance in top gear (90+% recommended), high percent distance in cruise control, minimum percent idle/PTO operation, minimum service brake activity, low number of sudden decelerations, and low service brake actuations/1000 miles.
Another aspect of the concepts disclosed herein is a technique to monitor vehicle location data (i.e., GPS data) over time to determine the actual operating speed of a fleet vehicle. Many fleet operators have the ability to define maximum speed parameters on their vehicles. Maximum speed parameters are defined to enhance safety and to reduce fuel costs (statistics indicated that for heavy trucks every MPH over 62 MPH reduces fuel economy by 0.1 MPG). However, these speed settings can fail due to maintenance issues, or driver manipulations. The maximum speed setting is based on understanding the size of the vehicle's tires. If during maintenance a different size tire is used as a replacement, the predefined speed settings will be inaccurate. Because drivers are often paid by the mile, drivers have an incentive to defeat the maximum speed settings, and drivers may encourage the use of different tire sizes, so they can go faster than the maximum speed setting, to increase their earnings. Drivers can also purchase and install aftermarket kits designed to bypass speed governors, again so they can go faster than the maximum speed setting, to increase their earnings. The concepts disclosed herein encompass collecting GPS data during the operation of a fleet vehicle, and analyzing the location and time parameters of that data to identify when a fleet vehicle exceeds a predefined maximum speed. The GPS verified speed metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
Another aspect of the concepts disclosed herein is to monitor manual overrides for cooling fans in fleet vehicles. Such cooling fans, generally controlled by a vehicle engine control unit (ECU) or vehicle computer, consume up to 50-70 HP, and measurably reduce fuel economy. Drivers who habitually override the automatic fan settings can consume unnecessary amounts of fuel. Thus the concepts disclosed herein encompass monitoring a driver's use of cooling fan manual override, to facilitate an evaluation of a driver's performance, and to enable drivers who use such overrides excessively to be identified and trained to reduce their use of manual cooling fan overrides. The cooling fan manual override metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
Another aspect of the concepts disclosed herein is to monitor engine RPMs during a driver's operation of a vehicle. Over revving an engine can lead to increased fuel use and engine wear. Drivers who habitually over rev their vehicles engines can consume unnecessary amounts of fuel. Thus the concepts disclosed herein encompass monitoring the RPM parameters while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently over rev their vehicle's engines to be identified and trained to reduce their over revving behavior. The over revving metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
Another aspect of the concepts disclosed herein is to monitor the shifting behavior during a driver's operation of a vehicle. Not running a heavy truck in the highest possible gear when possible can lead to increased fuel use and engine wear. Statistics indicate that every 10% drop of time in top gear results in a 0.5% mpg loss. Thus the concepts disclosed herein encompass monitoring shifting behavior while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently under shift to be identified and trained to reduce their over revving behavior. The shifting pattern metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
Another aspect of the concepts disclosed herein is to monitor the amount if idle time during a driver's operation of a vehicle. Increased idle leads to increased fuel use and engine wear. Thus the concepts disclosed herein encompass monitoring idle time behavior while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who excessively allow their vehicle to idle to be identified and trained to reduce their excess idle behavior. The excessive idle metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
Another aspect of the concepts disclosed herein is to monitor a load placed upon a vehicle's engine during a driver's operation of a vehicle. While related to RPM, load is not equivalent. An estimation of engine load is sometimes calculated by a vehicle ECU, and different manufacturers use different combinations of parameters to calculate engine load, including but not limited to throttle position, RPM, manifold pressure, air flow, temperature, air conditioning clutch status, power steering pressure, and transmission gear status. Where engine load is increased without performing more useful work (i.e., carrying more cargo), increased fuel use and engine wear result without a net benefit. Drivers who habitually operate their vehicles under higher engine loads than required consume unnecessary amounts of fuel. Thus the concepts disclosed herein encompass monitoring engine load while a driver operates a vehicle, to facilitate an evaluation of a driver's performance, and to enable drivers who consistently over load their vehicle's engines to be identified and trained to reduce their over loading behavior. The engine load metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
Calculation of an Exemplary Performance Ranking
The calculation of an exemplary performance ranking is described below in regard to one exemplary embodiment. It should be recognized that this approach for determining the performance ranking is not intended to be limiting, but rather to be illustrative of one contemplated valuation scheme and performance ranking implementation. In the exemplary performance ranking, a relatively higher numerical ranking value is generally indicative of relatively poorer driver performance. Thus, in this example, the lower the numerical performance ranking, the better the driver's performance.
In this example, the sensor data are collected for various metrics corresponding to vehicle acceleration, vehicle deceleration, vehicle idle time, and vehicle speed. Each minute of acceleration time will be assigned one point. Each minute of deceleration time will be assigned one point. Each minute of idle time will be assigned one point. In this example, the fleet operator is also particularly concerned with drivers who violate speed limits on the freeway. Thus, each minute where the vehicle speed exceeds 60 miles an hour while the driver is driving the vehicle on the freeway will result in five points (the fleet operator weighting excessive vehicle speed five times greater than the other metrics). The points are added together to achieve a combined total. The total is then normalized to derive a numerical ranking value for the driver. As noted above, the normalization can be based on either distance driven or time of operation, or a combination thereof.
Calculation of a Work Based Performance Ranking Using GPS Derived Slope Data
The concepts disclosed herein encompass using data collected during the operation of a vehicle to calculate a weight of the vehicle, and then using the calculated weight in a performance analysis of the vehicle. The novel vehicle weight calculation disclosed herein employs in part vehicle position data collected while a vehicle is moving. The position metric can be automatically determined using a global positioning satellite (GPS) receiver installed in the vehicle, to track the vehicle's change in position over time. It should be recognized that the GPS system is but one of a plurality of different vehicle position sensing technologies that can be employed.
Fundamentally, GPS systems calculate velocity in three components (X, Y, Z or N/S, E/W, and Up/Down) based on a Doppler shift of the GPS satellite signals. Scalar speeds can then be calculated from those three components. For example, absolute speed or actual vehicle speed can be determined, as well as ground speed based on the shortest distance between two points (i.e., based on distance as the crow flies).
Horizontal ground speed (VHGS) can be calculated using the following relationship based on the Pythagorean theorem:
VHGS=√{square root over (x2+y2)} (1)
To calculate a grade (G) the vehicle is traveling over (as a percentage), one can take the Z/Up magnitude and divide it by the horizontal ground speed, VHGS, which results in the following relationship:
Replacing Z, x and y with directional vectors (such as Up for Z, West for x and North for y, recognizing that such directional vectors are exemplary, and may change based on the actual GPS data collected from the vehicle) results in the following relationship:
Once one has derived G as discussed above, very useful vehicle performance metrics can be determined.
One exemplary use of the slope data is to determine the mass of the vehicle at that time. Mass is a useful metric that can be used as a feedback metric for controlling certain vehicle systems. Some vehicle engine control units (ECUs) use torque output, engine RPMs, and vehicle velocity to calculate a vehicle's mass or weight (as used herein and in the claims that follow, the terms mass and weight are used synonymously, because on the surface of the Earth, the acceleration due to gravity (the “strength of gravity”) is approximately constant; thus the ratio of the weight force of a motionless object on the surface of the Earth to its mass is almost independent of its location, so that an object's weight force can stand as a proxy for its mass, and vice versa). That ECU weight/mass determination technique is error prone, because it does not take into account any slope conditions. Even though the ECU weight/mass determination technique is error prone, the ECU weight/mass determination technique mass estimation provides a metric that can be used to as a feedback metric for various vehicle systems, including transmission shift points, engine RPM control, and emission controls. Having more accurate mass metrics (by including the GPS derived slope data in a mass calculation) will provide an improved mass metric. The concepts disclosed herein specifically encompass a GPS unit configured to use GPS data to calculate slope, to use the slope data and other vehicle parameters to determine vehicle mass (generally as discussed below), and then to provide a GPS slope based vehicle mass metric to a vehicle ECU to be used as a metric to control vehicle operation.
Vehicle mass can also be used as an analytical metric to determine how much work a vehicle has performed. Being able to accurately determine the amount of work a vehicle is performing will help vehicle operators analyze their use patterns to seek out efficiency improvements. The GPS derived slope data enables more accurate vehicle mass calculations to be determined, which in turn will provide an improved vehicle performance data set that can be mined to identify areas in which efficiency improvements could be made.
Having described the GPS based slope determination technique; the following relationships will be used to obtain vehicle mass from the GPS determined slope (G). These relationships define the forces acting on the vehicle, and include a force related to a grade the vehicle is traveling over, an aerodynamic force, a frictional force, and a force applied by the vehicle to overcome the forces acting on the vehicle. The understanding of these forces is not new, but what is novel are techniques disclosed herein to measure certain parameters that are used to calculate such forces. Being able to measure those parameters, such as a grade the vehicle is traveling over, enables more accurate force calculations to be performed, which in turn enables a better understanding of vehicle operational efficiency.
A first force opposing a motion of the vehicle relates to a grade or slope the vehicle is traveling over, which can be defined using the relationship of Equation (4).
fgrade=m*g*G (4)
where m is vehicle mass and g is the local gravitational field (i.e., Earth's gravity).
A second force opposing a motion of the vehicle relates to aerodynamic forces acting on the vehicle, which can be defined using the relationship of Equation (5).
fareo=½*p*Cd*A*v2 (5)
where ρ is air density, Cd is the coefficient of drag of the vehicle, A is the frontal area of the vehicle, and v is the vehicle velocity (which can be obtained from the vehicle data bus or from GPS data).
A third force opposing a motion of the vehicle relates to frictional forces acting on the vehicle, which can be defined using the relationship of Equation (6).
fFriction=Crr*m*g*(1−G) (6)
where Crr is the coefficient of rolling resistance of the vehicle (which is assumed to be constant), m is vehicle mass, g is the local gravitational field (i.e., Earth's gravity), and G is the slope, which is calculated using the GPS data as discussed above.
The force generated by the vehicle to overcome these opposing forces can be defined using the relationship of Equation (7).
where τ is engine output torque (as measured at the vehicle by vehicle sensors/reported by the vehicle data bus), N is engine RMPs (as measured at the vehicle by vehicle sensors/reported by the vehicle data bus), v is the vehicle velocity (which can be obtained from the vehicle data bus or from GPS data), π is the mathematical constant defined as the ratio of any circle's circumference to its diameter, and r is the radius of the vehicles tires.
Vehicle mass is a parameter in the grade and frictional force relationships, of Equations (4) and (6), respectively. The mass parameter itself can be defined using the relationship of Equation (8).
where m is vehicle mass and α is acceleration (which can be obtained from the vehicle data bus or from GPS data). In an exemplary embodiment, acceleration is obtained from the vehicle sensors.
Equations (4)-(8) can be solved to obtain mass, as defined using the relationship of Equation (9).
Note that the following parameters will be measured during vehicle operation in order for mass to be calculated: velocity, torque, RPM. Those parameters, combined with the GPS derived slope data, and known parameters (gravity, air density, rolling resistance, frontal area, drag, pi, and tire radius) can be used by a processor in the vehicle to calculate mass. Velocity, torque, and RPM represent metrics that many vehicles already measure during vehicle operation, and thus can be accessed by tapping into a vehicle ECU or data bus. The concepts disclosed herein specifically encompass a GPS unit (or other position sensing unit) including a data port coupled to a vehicle ECU/data bus and a processor configured to calculate a GPS derived slope metric (generally as discussed herein) and a vehicle mass metric (generally as discussed herein, using in part the GPS derived slope data).
Having an accurate mass parameter, determined in real-time during the operation of the vehicle, will enable a more accurate measurement of the work being performed by the vehicle to be measured. The work metric can be used as a driver performance metric on its own, or be combined with other metrics to generate a driver performance metric.
In an optional block 126, the slope data is used to calculate a mass of the vehicle, using the relationship of Equation (9). In at least some embodiments, the data processing of blocks 122, 124, and 126 are performed by a remote computing device. however, the concepts disclosed herein encompass embodiments where some or all of the data processing of blocks 122, 124, and 126 are performed by a processor or logic circuit in the vehicle. In at least some embodiments in which the data processing is implemented in the vehicle, the mass parameter is used by an ECU in the vehicle to control operating parameters of the vehicle. For example, vehicle mass can be used as a feedback parameter for controlling vehicle operations, including engine speed (RPM), transmission gear selection, and fuel flow/mixture (to control vehicle emissions). While using vehicle mass data used as a feedback parameter for controlling vehicle operations has been implemented before, those implementations have not used GPS derived slope data as a parameter to determine vehicle mass.
Fleet operators recognize that cost per loaded is a metric that can be analyzed to improve the efficiency of their fleets, by allowing driver performance to be evaluated, and by allowing different routes to be analyzed, to determine the actual cost of servicing a particular route. While these concepts are not new, what is new is the improved vehicle mass metric that can be calculate in real-time while the vehicle is operated, or at a later, where the mass metric is available for the duration of the vehicle operating segment (or trip). Note that in the prior art, unless the vehicle was weighed during the trip (i.e., before the trip, after the trip, or during the trip at a scale stop) such accurate vehicle mass data was not available, so the cost per loaded metric was error prone, or accurate based on data collected at only a few selected segments of the trip. The concepts disclosed herein are based on collecting vehicle operational data (fuel use, mileage, position data, etc.) frequently (i.e., multiple times a minute, or at least once every few minutes, such intervals being exemplary) so that vehicle mass can be accurately calculated at almost any time during the operation of a vehicle.
An exemplary data set collected from a vehicle will include time indexed position data, engine RPM data, vehicle torque data, and vehicle speed. This data will be collected frequently (multiple times per minute, or a plurality of times over a ten minute period) while the vehicle is operational. Note that vehicle speed can be determined by analyzing position data over time, or can be measured using a vehicle sensor (note that comparing vehicle speed obtained from vehicle sensors with vehicle speed calculated based on GPS data can identify errors in the vehicle speed sensor, which can be caused by incorrect tire sizes, or driver added speed cheating devices designed to override vehicle speed governors). Such a data set can also include other types of vehicle data, including, but not limited to, data relating to the vehicle transmission (so drivers can be evaluated based on percentage of time spent in the most efficient gear), data relating to the vehicle braking system (so drivers can be evaluated based on their braking behavior), data relating to the use of cooling fan overrides (so drivers can be evaluated based on how often they such an override that reduces fuel efficiency), data relating to idle time (so drivers can be evaluated based on percentage of time spent in wasting fuel by idling, noting that idle time can be evaluated in light of position data, so that drivers are not penalized for idling at traffic lights), data relating to the use of a vehicle's cruise control system (so drivers can be evaluated based on percentage of time spent driving at fuel efficient speeds). Note this exemplary data set includes the data required to calculate vehicle mass using GPS derived slope data, generally as discussed above.
Hosted Website for Tracking Driver Performance Data
One aspect of the concepts disclosed herein is a hosted website, enabling drivers and fleet operators to monitor the performance of drivers, based on data collected during the drivers operation of a vehicle. In at least one embodiment, drivers can compare their performance metrics to their peers, although the concepts disclosed herein also encompass embodiments where individual drivers can only see their own performance scores. Fleet operators can use these performance metrics as incentives, by linking driver pay with performance.
In general, one or more performance metrics are automatically collected while a driver is operating a vehicle, and that data is used to generate a score or rating of the driver's performance. In at least one embodiment, the score is normalized to enable driver scores from other types of vehicles to be compared. Then, the driver performance data is posted to the hosted website.
In at least one related embodiment, fleet operators will pay drivers using a mileage component (i.e., paying drivers a fixed rate per loaded mile), while also making additional payments to drivers meeting predefined performance characteristics. The hosted website can be used as a forum to enable drivers to track their progress in achieving their pay for performance goals. Fleet operators will have a wide degree of freedom in designing pay for performance goals or campaigns. For example, Fleet A can design a campaign in which only drivers having performance scores in the top 10% of the fleet will earn performance pay. Fleet B can design a campaign in which only the top 25 scoring will earn performance pay during a particular campaign. Fleets can predefine the amount of performance pay each driver can earn. Fleets can also predefine a performance pay pool, such that the share of the pool earned by each driver is a function of the number of drivers meeting predefined performance goals for the campaign.
In at least one embodiment, the performance metric will be a work based performance metric whose calculation involves using vehicle mass determined using GPS derived slope data, generally as discussed above.
It should be recognized that performance campaigns can be metric specific (hard braking performance, idle time performance, such metrics being exemplary and not limiting), or can be based on a single normalized score (cost per loaded mile), but will share in common the characteristic of being implemented for a defined period of time. Drivers will learn to associate such campaigns with opportunities to increase their pay by meeting the performance goals of individual campaigns.
In at least one embodiment, the campaign duration is open ended, in that the hosted website will track a driver's performance data over time, so the driver can use that data to look for other employment opportunities. For example, fleets would likely compete among themselves for drivers having a combination of experience and high performance rankings.
In a block 64, driver performance data is posted to the hosted website. The concepts disclosed herein encompass permutations and combinations of the following: embodiments in which fleet operators can view performance rankings for all of their drivers, but not drivers of other fleets, embodiments in which drivers can only view their own personal performance ranking, embodiments in which drivers can view performance ranking for all of the drivers in their fleet, but not drivers of other fleets, and very transparent embodiments, in which interested parties can visit the website and peruse driver performance rankings with little restrictions.
In a block 66, at the end of the defined campaign, the winning driver (or drivers) are announced and paid a performance pay bonus.
As noted above, in some embodiments, campaign participants are limited to drivers in a specific fleet (i.e., an intra-company or intra-fleet campaign). In such embodiments, that fleet generally will be paying the performance bonuses for the campaign. In other embodiments, campaign participants are not limited to drivers in only one specific fleet (i.e., an inter-company or inter-fleet campaign). In such an embodiment, a third party may be paying the performance bonuses for the campaign. For example, companies providing goods and services to the trucking or vehicle transportation industry may sponsor such a campaign for advertising purposes. A particular fleet operator seeking to attract the attention of drivers in other fleets might also be a sponsor of an inter-company campaign.
In at least one aspect of the concepts disclosed herein, the performance metric is designed to facilitate comparison of driver performance data across different fleets, and different vehicles. This will enable individual campaigns to include more participating drivers, which in turn will bring in more advertising revenue to fund bigger performance bonuses. In at least one embodiment, such a metric is mutually agreed upon by a plurality of different fleet operators. Adoption of a common performance metric across multiple fleets will enable top performing drivers to be able to show their cumulative performance scores to other participating fleet operators, providing an additional tool for fleets to use when evaluating potential new hires. Such a common performance metric will also enable participating fleet operators to appear more attractive as potential employers than non-participating fleet operators, who will not be offering the drivers the potential of earning the additional performance based income (i.e., income in addition to the industry standard pay by the mile driver compensation).
The concepts disclosed herein encompass embodiments in which individual fleet operators host their own website, where driver rankings in that fleet can be compared. In other embodiments, the website is hosted by a third party, and multiple fleet operators participate. The third party can offset their costs for operating the website by charging participating fleet operators a fee, and/or by advertising revenue. In some embodiments, all driver performance data is displayed in an anonymous format, so that individual drivers cannot be identified unless the driver shares their user ID. In some embodiments, drivers can only compare their score with drivers in their own fleet, while in other embodiments drivers can see the performance data of drivers in other fleets.
It should be understood that monitoring service 150 is implemented using a remote computing device, and that the term remote computing device is intended to encompass networked computers, including servers and clients, in private networks or as part of the Internet. The monitoring of the vehicle/driver performance data and driver performance ranking by monitoring service 150 can be performed by multiple different computing devices, such that performance data is stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network.
Referring to
Referring to first portion 102, a driver has selected driver number ZONA0047 (noting that any type of driver identification can be employed), such that the data displayed in results section 104 and performance tip section 106 relate to driver ZONA0047. As shown in
Referring to results section 104, exemplary (but not limiting) information displayed herein includes details on the campaign, whether the campaign is inter-company or intra-company, and the driver's performance ranking for that campaign. A visual guide to the driver's relative performance is displayed using a plurality of fuel pump icons (where a greater number of fuel pump icons, or other graphical icons, indicates a better performance rating). As shown, webpage 100 is based on displaying 10 fuel pump icons for each campaign (icons 108a-108c), enabling the driver's performance to be graphically displayed on a scale of 1 to 10. Thus, a driver whose performance ranking is in the top 80th percentile would have 8 solid or un-shadowed fuel pumps. Recognizing that while only full icons are displayed in this example, partial fuel pump icons can be used as well, to provide fractional ratings, or numbers between 0 and 10 can be rounded up to the next whole number. Radio buttons 110a-c can be used by the driver to select performance tips for the particular campaign to be displayed in section 106.
With respect to webpage 100, it should be understood that the design of webpage 100 is intended to be exemplary, and different webpage designs can be employed; and further, that the data on webpage 100 can be provided to the vehicle operator on more than one webpage. If desired, access to webpage 100 can be restricted only to the fleet operator employer the driver and the driver themself. However, providing other drivers access to webpage 100 will enable drivers to see how they rank compared to their peers, encouraging drivers to compete amongst themselves to collect the performance bonus available in campaigns.
Referring once again to section 104 of webpage 100, note that a first campaign (associated with radio button 110a) is identified as INTRA-COMPANY RANKING. This campaign is a fleet sponsored campaign for all of the fleet drivers to compete with each other for a performance bonus. Driver ZONA0047 ranks as 83rd out of 225 drivers, with lower numbers indicating better performance (i.e., the top ranking driver would be ranked as 1, noting that the fleet operator could have reversed the logic, such that 225 was the top ranking driver). Being the 83rd lowest ranking driver out of a fleet of 225 drivers places driver ZONA0047 in the top 63% ((225−83)/(225*100)=63.11%). Six fuel pump icons 108a are filled in. The campaign parameters are summarized, indicating that drivers having rankings from 1-25 (i.e., the top 88.89%) across the entire fleet share in the bonus pool assigned to this campaign. Driver ZONA0047 needs to increase his ranking from 83rd to 25th in order to be eligible for a share in the bonus pool. Note that campaigns can be configured such that the top 25 drivers earn equal shares of the bonus pool, and campaigns can also be configured such that higher ranking drivers (i.e., closer to #1) earn a proportionally larger share of the bonus pool.
Referring once again to section 104 of webpage 100, note that a second campaign (associated with radio button 110b) is identified as INTRA-COMPANY CAMPAIGN XYZ. This campaign is a fleet sponsored campaign for all of the fleet drivers to compete with each other for a performance bonus. Driver ZONA0047 has no ranking indicated in the campaign, thus all ten fuel pump icons 108b are shadowed or empty. The campaign parameters are summarized, indicating that Campaign XYZ includes a bonus pool to be shared by the 10 fleet drivers having the most improved performance scores for December 2011. Driver ZONA0047 has selected radio button 110b so that performance tips and additional information related to Campaign XYZ are displayed in section 106. Those performance tips include a first tip indicating that late shifting reduced Driver ZONA0047's performance ranking by 9.2% over the last 14 days. A second performance tip indicates that hard breaking events reduced Driver ZONA0047's performance ranking by 5.3% over the last 19 days. Finally, the last performance tip indicates that excessive idling on Dec. 11, 2011 disqualified Driver ZONA0047 from Campaign XYZ. It should be recognized that the specific performance tips shown in section 106 are intended to be exemplary, and not limiting. The actual performance tips displayed will be related to the specific campaign, and designed to provide feedback to individual driver's to enable them to identify behaviors that have reduced their performance ranking.
In some embodiments section 112 includes banner ads targeted to drivers. In other embodiments section 112 includes advertising from vendors who are sponsoring specific campaigns, or who are sponsoring hosting of the driver performance ranking website. The advertising can be a mixture of those different types, and other types of advertising.
Exemplary System Environment
In some embodiments, an output 138 is also included, to provide information to the driver in a form that can be easily understood by the driver. Output 138 can be implemented using a speaker providing an audible output, and using a display providing a visual output. Note that output 138 can be combined into a single component with the data buffer and the data link, so only a single additional component is added to the vehicle (recognizing that most vehicles already include the additional required components, such as the operational data collecting components and the processor).
While not specifically shown in
As indicated in
The concepts disclosed herein are in at least some embodiments intended to be used by fleet owners operating multiple vehicles, and the performance data conveyed to the remote location for diagnosis will include an ID component that enables each enrolled vehicle to be uniquely identified.
Exemplary Computing Environment
Also included in processing unit 254 are a random access memory (RAM) 256 and non-volatile memory 260, which can include read only memory (ROM) and may include some form of memory storage, such as a hard drive, optical disk (and drive), etc. These memory devices are bi-directionally coupled to CPU 258. Such storage devices are well known in the art. Machine instructions and data are temporarily loaded into RAM 256 from non-volatile memory 260. Also stored in the non-volatile memory are operating system software and ancillary software. While not separately shown, it will be understood that a generally conventional power supply will be included to provide electrical power at voltage and current levels appropriate to energize computing system 250.
Input device 252 can be any device or mechanism that facilitates user input into the operating environment, including, but not limited to, one or more of a mouse or other pointing device, a keyboard, a microphone, a modem, or other input device. In general, the input device will be used to initially configure computing system 250, to achieve the desired processing (i.e., to monitor vehicle performance data over time to detect a mechanical fault). Configuration of computing system 250 to achieve the desired processing includes the steps of loading appropriate processing software into non-volatile memory 260, and launching the processing application (e.g., loading the processing software into RAM 256 for execution by the CPU) so that the processing application is ready for use. In embodiments where computing system 250 is implemented in a vehicle, the computing system 250 can be configured to run autonomously, such that a user input device not regularly employed.
Output device 262 generally includes any device that produces output information, but will most typically comprise a monitor or computer display designed for human visual perception of output. Use of a conventional computer keyboard for input device 252 and a computer display for output device 262 should be considered as exemplary, rather than as limiting on the scope of this system. In embodiments where computing system 250 is implemented in a vehicle, the computing system 250 can be vehicle performance data (and position data when desired) collected in connection with operation of enrolled vehicles to configured to run autonomously, such that a user output device not regularly employed.
Data link 264 is configured to enable data to be input into computing system 250 for processing. Those of ordinary skill in the art will readily recognize that many types of data links can be implemented, including, but not limited to, universal serial bus (USB) ports, parallel ports, serial ports, inputs configured to couple with portable memory storage devices, FireWire ports, infrared data ports, wireless data communication such as Wi-Fi and Bluetooth™, network connections via Ethernet ports, and other connections that employ the Internet.
Note that vehicle/driver performance data from the enrolled vehicles will be communicated wirelessly in at least some embodiments, either directly to the remote computing system that analyzes the data to evaluate the driver's performance, or to some storage location or other computing system that is linked to computing system 250.
It should be understood that the term “remote computer” and the term “remote computing device” are intended to encompass a single computer as well as networked computers, including servers and clients, in private networks or as part of the Internet. The vehicle/driver performance data received by the monitoring service from the vehicle can be stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network. While implementation of the method noted above has been discussed in terms of execution of machine instructions by a processor (i.e., the computing device implementing machine instructions to implement the specific functions noted above), the method could also be implemented using a custom circuit (such as an application specific integrated circuit or ASIC).
The concepts disclosed herein encompass collecting data from a vehicle during operation of the vehicle. The data collected is used to analyze the performance of at least one of the driver and the vehicle. In preferred embodiments, the data is collected during operation of the vehicle and wirelessly transmitted from the vehicle during its operation to a remote computing device using a cellular phone network based data link. The frequency of such data transmissions can be varied significantly. In general, more data is better, but data transmission is not free, so there is a tension between cost and performance that is subject to variation based on an end user's needs and desires (some users will be willing to pay for more data, while other users will want to minimize data costs by limiting the quantity of data being transferred, even if that results in a somewhat lower quality data set). The artisan of skill will be able to readily determine a degree to which data quality can be reduced while still provide useful data set.
Exemplary GPS Device with Onboard Computing Environment
An exemplary telematics unit 160 includes a controller 162, a wireless data link component 164 (an RF data link being exemplary, but not limiting), a memory 166 in which data and machine instructions used by controller 162 are stored (again, it will be understood that a hardware rather than software-based controller can be implemented, if desired), a position sensing component 170 (such as a GPS receiver), and a data input component 168 configured to extract vehicle data from the vehicle's data bus and/or the vehicle's onboard controller (noting that the single input is exemplary, and not limiting, as additional inputs can be added, and such inputs can be bi-directional to support data output as well).
The capabilities of telematics unit 160 are particularly useful to fleet operators. Telematics unit 160 is configured to collect position data from the vehicle (to enable vehicle owners to track the current location of their vehicles, and where they have been) and to collect vehicle operational data (including but not limited to engine temperature, coolant temperature, engine speed, vehicle speed, brake use, idle time, and fault codes), and to use the RF component to wirelessly convey such data to vehicle owners. The exemplary data set discussed above in connection with calculated loaded cost per mile can also be employed. These data transmission can occur at regular intervals, in response to a request for data, or in real-time, or be initiated based on parameters related to the vehicle's speed and/or change in location. The term “real-time” as used herein is not intended to imply the data are transmitted instantaneously, since the data may instead be collected over a relatively short period of time (e.g., over a period of seconds or minutes), and transmitted to the remote computing device on an ongoing or intermittent basis, as opposed to storing the data at the vehicle for an extended period of time (hour or days), and transmitting an extended data set to the remote computing device after the data set has been collected. Data collected by telematics unit 160 can be conveyed to the vehicle owner using RF component 164. If desired, additional memory can be included to temporarily store data id the RF component cannot transfer data. In particularly preferred embodiments the RF components is GSM or cellular technology based.
In at least one embodiment, the controller is configured to implement the method of
In another embodiment, the controller is configured to implement steps of the method of
Newly Disclosed Subject Matter
It should be understood that vehicle 180 can include more than one ECU 182 whose programming can be changed to enhance the efficiency of the vehicle operation. In most cases, enhanced efficiency means better fuel efficiency, although it should be recognized that in certain applications other factors, such as available horsepower, load rating, shift patterns (logic determining under what conditions an automatic transmission will change gears) RPM settings, and/or speed settings can be changed by changing the ECU programming to suit current conditions. So while the concepts disclosed herein can be used to modify ECU programming based on current operating conditions to improve fuel efficiency, the concepts disclosed herein can also be used to optimize performance based on some other parameter than fuel efficiency. It should be understood that the concepts disclosed herein can be applied to change ECU programming on more than one ECU in a vehicle. Furthermore, it should be understood that certain conditions might trigger multiple ECU reprogramming. For example, the detection of a certain predefined condition could trigger ECU programming changes that modify one or more of fuel flow settings, RPM settings, and transmission shift patterns, noting that such parameters are exemplary and not limiting.
In at least one embodiment, the ECU reprogramming includes modifying a fuel map.
Controller 184 is tasked with comparing the current operating conditions with the current ECU programming, and determining if the ECU programming should be changed to optimize vehicle performance (according to some predetermined characteristic, such as max fuel efficiency, max power, etc.). Controller 184 can implemented by a general purpose computing device executing machine instructions to implement such a task, or by a custom circuit designed to implement the specific function. In general, controller 184 is located at the vehicle, although it should be recognized that if controller 184 is logically coupled to a data link at the vehicle, and the data link is logically coupled to ECU 182 (or a vehicle data bus coupled to the vehicle ECU), that controller 184 can be disposed at a location remote from the vehicle.
In embodiments where controller 184 is remote from the vehicle, input 188 can be at the vehicle, and coupled to the data link in the vehicle communicating with controller 184. Alternatively, where controller 184 is remote from the vehicle, a non-vehicle based input can be used by a dispatcher/operator remote from the vehicle to provide input to controller 184.
Controller 184 can select a different ECU programming set based on empirical data indicating that a particular programming set is preferred based on specific operating conditions, or based on a user knowledge base that suggests that a certain programming set is more appropriate for certain operating conditions (such suppositions based on user knowledge may or may not have been confirmed with empirical data).
In at least one embodiment, controller 184 of
Memory 186 includes a plurality of different ECU programming sets, each of which can be selected to optimize certain vehicle performance characteristics (such as fuel efficiency, speed settings, engine RPM settings, available power settings, etc.) according to current operating conditions at the vehicle (it should also be understood that the concepts disclosed herein will enable operators to specifically select particular programming sets, irrespective of current conditions). Further, it should be understood that current operating conditions can be based on current sensor data, as well as a specific input before such sensor data is collected (such specific inputs can include a specific route the vehicle will be following, or a particular load the vehicle will be carrying).
In general, memory 186 is located at the vehicle, although it should be recognized that if memory 186 is logically coupled to a data link at the vehicle, and the data link is logically coupled to controller 184 at the vehicle, that memory 186 can be disposed at a location remote from the vehicle. Further, if controller 184 is located at a remote location, memory 186 need not be at the vehicle, but at some location where controller 184 can access memory 186.
Input 188 represents an input device at the vehicle, which is used to convey one or more data inputs to controller 184. In some embodiments, input 188 is a sensor disposed at the vehicle, which detects an ambient condition, so that controller 184 can determine if the current ECU programming is appropriate for the current conditions. Exemplary sensors include temperature sensors, GPS devices (including GPS devices that are configured to provide GPS derived slope data and vehicle mass data, generally as discussed above), speed sensors, inclinometers, weight sensors, oil pressure sensors, oil temperature sensors, coolant temperature sensors, tire temperature sensors, and tire pressure sensors. It should be recognized that the concepts disclosed herein encompass the use of only a single sensor input, as well as embodiments wherein controller 184 receives multiple different sensors inputs, and selects an ECU programming set based on multiple sensor inputs. In such an embodiment, controller 184 can be configured to assign different priorities to different sensor inputs.
In at least one embodiment, input 188 is a controller or processor in the vehicle that detects a condition, and conveys an indication of that condition to controller 184. For example, a processor in the vehicle might detect that the vehicle is idling, and may be likely to continue idling for an extended period, such that controller 184 modifies ECU programming to reduce fuel consumption during a period of extended idle conditions. One technique for detecting or predicting extended idle conditions is based on historical data (vehicle regularly idles at the same time or location), as well as using location data (i.e., a terminal or loading facility where a vehicle might logically idle while waiting to be loaded). Furthermore, if a processor detects that a vehicle is in neutral or park, and running for more than 90 seconds (or some other predetermined period of time), that processor could indicate to controller 184 that an idle state has been entered. Another technique for detecting an idle condition is determining if a PTO unit has been active. Activation of such a unit often indicates that the engine is being used to drive the PTO rather than for over the road operation, such that different ECU programming sets can be implemented to reduce fuel consumption (as PTO units generally require much less horsepower than over the road travel).
In at least one embodiment, input 188 is (or is logically coupled to) a PTO, such that activation of the PTO triggers a change in ECU programming. As noted above, PTO units generally require much less horsepower than over the road travel.
In at least one embodiment, input 188 is a user interface that a vehicle operator can use to either convey an indication of a specific condition to controller 184, or to specifically request a particular ECU programming change. In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 that the vehicle will be entering an extended idle state (for example, due to traffic conditions, loading wait times, PTO use, or some other condition that requires the driver keep the vehicle running but not moving, or moving at very low speeds). Controller 184 can then respond by selecting ECU programming that reduces available horsepower but maximized fuel efficiency.
In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 that the vehicle will be entering a jurisdiction or region where a different max speed setting needs to be implemented. Controller 184 can then respond by selecting ECU programming that matches the speed setting to the jurisdiction or region selected by the driver.
In one exemplary embodiment, the vehicle operator enters into a business relationship with a third party. The third party modifies a vehicle as indicated in
In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 that the vehicle will be entering an uphill segment of a route (generally this will be implemented where the uphill segment is relatively long, as there may be minimal benefit to implementing an ECU programming change for a shorter segment). Controller 184 can then respond by selecting ECU programming that is more suited to larger horsepower requirements for uphill travel.
In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 that the vehicle will be entering a downhill segment of a route (generally this will be implemented where the downhill segment is relatively long, as there may be minimal benefit to implementing an ECU programming change for a shorter segment). Controller 184 can then respond by selecting ECU programming that is more suited to reduced horsepower requirements for downhill travel (or increased braking, or a change in shift patterns more suited to downhill travel).
In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 the current load conditions for the vehicle (for example, a weight of the material loaded onto the vehicle). Controller 184 can then respond by selecting ECU programming that is more suited to the current load.
In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 the specific route for the vehicle). Controller 184 can then respond by selecting ECU programming that is more suited to that route. In some embodiments, the controller is coupled to a GPS unit, so that different ECU parameters can be implemented for different portions of the route. Vehicle operators that continually traverse the same route under similar load conditions can perform empirical studies to determine optimal ECU programming patterns for different portions of that route.
In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 the current road conditions (for example, elevation, night time operation, day time operation, heavy traffic conditions, the presence of snow or ice, relatively cold ambient temperatures, or relatively hot ambient temperatures). Controller 184 can then respond by selecting ECU programming that is more suited to the current road conditions. As discussed above, empirical data or user knowledge can be used to determine which ECU programming sets are most suited to certain conditions.
In at least one embodiment, the vehicle operator uses input 188 to tell controller 184 the identity of the current operator. Controller 184 can then respond by selecting ECU programming that is more suited to the skill set of the current driver. For example, fleet operators may understand that relatively less experienced drivers are less able to operate vehicles at peak fuel efficiency, and certain ECU programming can be used to manage their relative inefficiencies. More experienced drivers may be able to achieve better fuel efficiency with different ECU programming. As discussed above, empirical data or user knowledge can be used to determine which ECU programming sets are most suited to certain drivers.
Data link 190 can be used in lieu of or in addition to input 188 as a mechanism to provide data input to controller 184, to prompt controller 184 to review current ECU programming in light of the data input in order to determine if ECU programming should be changed (it should be understood that the concepts disclosed herein also encompass embodiments in which the data input is actually an instruction to change the ECU programming, such that to controller 184 does not need to analyze the input to determine if a change is required, but simply executes the instructed ECU programming change).
In embodiments wherein controller 184 is disposed at the vehicle, data link 190 can be used to send data acquired remotely to controller 184. In embodiments wherein controller 184 is disposed remote from the vehicle (not separately shown), a similar data link at the vehicle can be logically coupled to ECU 182, so that controller 184 can reprogram the ECU remotely.
In at least one embodiment, data link 190 receives input from a controller or processor remote from the vehicle that detects a condition, and conveys an indication of that condition to controller 184 via the data link. For example, a processor remote from the vehicle might detect that the vehicle is idling, and may be likely to continue idling for an extended period, such that controller 184 modifies ECU programming to reduce fuel consumption during a period of extended idle conditions. One technique for detecting or predicting extended idle conditions is based on historical data (GPS data acquired from the vehicle and sent to the remote processor indicates the vehicle is currently at a location that past data indicates is associated with extended idle conditions, or time records available to the remote processor indicates the vehicle regularly idles at a particular point in time. Furthermore, if the remote processor (using data conveyed from the vehicle) detects that a vehicle is in neutral or park, and running for more than 90 seconds (or some other periods of time), that processor could indicate to controller 184 that an idle state has been entered. Another technique for detecting an idle condition is determining if a PTO unit has been active (again, using data conveyed from the vehicle to the remote processor). Activation of such a unit often indicates that the engine is being used to drive the PTO rather than for over the road operation, such that different ECU programming sets can be implemented to reduce fuel consumption (as PTO units generally require much less horsepower than over the road travel). It might seem that sending data from the vehicle to a remote processor, which analyzes the data to detect conditions that may indicate ECU programming changes should be implemented is based on data transfer that could be eliminated by having the processor detecting the condition at the vehicle. While that is true, collecting data from a vehicle and conveying that data to a remote site for storage and analysis is a legitimate business model; and such data transmission already occurs. Performing analysis remote from the vehicle reduces the computational load at the vehicle, so if the data is already being sent from the vehicle to a remote server, processing the data remotely is a functional alternative to analyzing data at the vehicle. Such offsite processing is also useful in embodiments where controller 184 is located remote from the vehicle.
In at least one embodiment, data link 190 receives input from a weather service that provides weather information for the vehicles general location. Controller 184 can then determine if current ECU programming matches the weather conditions from the weather service, and if not, controller 184 selects more appropriate ECU programming sets and reprograms the ECU.
In at least one embodiment, data link 190 receives input from a user interface disposed remote from the vehicle that a dispatcher can use to either convey an indication of a specific condition to controller 184, or to specifically request a particular ECU programming change. In at least one embodiment, the dispatcher uses the remote input device and data link 190 to tell controller 184 that the vehicle will be entering a jurisdiction or region where a different max speed setting needs to be implemented. Controller 184 can then respond by selecting ECU programming that matches the speed setting to the jurisdiction or region selected by the driver.
In at least one embodiment, data link 190 receives input from a user interface disposed remote from the vehicle that a dispatcher can use to tell controller 184 the current load conditions for the vehicle (for example, a weight of the material loaded onto the vehicle). Dispatchers will often have access to that information even though they are remote from the vehicle. Controller 184 can then respond by selecting ECU programming that is more suited to the current load.
In at least one embodiment, data link 190 receives input from a user interface disposed remote from the vehicle that a dispatcher can use to tell controller 184 the specific route for the vehicle. Controller 184 can then respond by selecting ECU programming that is more suited to that route. In some embodiments, the controller is coupled to a GPS unit, so that different ECU parameters can be implemented for different portions of the route. Vehicle operators that continually traverse the same route under similar load conditions can perform empirical studies to determine optimal ECU programming patterns for different portions of that route.
In at least one embodiment, data link 190 receives input from a user interface disposed remote from the vehicle that a dispatcher can use tell controller 184 the identity of the current operator (dispatchers often have access to driver data even though they are remote from the vehicle). Controller 184 can then respond by selecting ECU programming that is more suited to the skill set of the current driver. For example, fleet operators may understand that relatively less experienced drivers are less able to operate vehicles at peak fuel efficiency, and certain ECU programming can be used to manage their relative inefficiencies. More experienced drivers may be able to achieve better fuel efficiency with different ECU programming. As discussed above, empirical data or user knowledge can be used to determine which ECU programming sets are most suited to certain drivers.
In a block 190, input data is conveyed to a processor tasked with evaluating ECU programming in light of the input data. In some embodiments, the processor is located at the vehicle, while in other embodiments the processor is spaced apart from the vehicle, and is logically coupled to the vehicle ECU (or a data bus coupled to the ECU) via a wireless data link.
In a block 192, the processor tasked with evaluating current ECU programming in light of the input data determines if more efficient ECU programming sets exist. If not, the logic loops back to block 190. If in block 192 it is determined that a better ECU programming set exists, then in a block 194 the current ECU programming is replaced with the more efficient ECU programming (based on the input from block 190).
As noted above, either empirical data or user knowledge can be used to assign specific ECU programming sets to specific conditions/inputs. Thus in block 192 the processor simply matches the available ECU programming sets to the input.
In an exemplary embodiment, block 192 is implemented using the following steps. A plurality of different ECU programming sets are provided For each ECU programming set, the current vehicle operational data is used as an input, and based on those inputs at least one vehicle performance characteristic that would result in using that ECU programming set is determined in light of current vehicle operational data. Note that in some embodiments, the output of using the current vehicle operational data and a specific ECU programming set is a single vehicle performance characteristic (such as horsepower or fuel economy), while in other embodiments the output includes a plurality of different vehicle performance characteristics. The determination as to whether the output should include a single or multiple vehicle performance characteristics is based on what the vehicle operator hopes to achieve. In many embodiments, the vehicle operator will be hoping to achieve improved fuel economy, thus in at least some embodiments the only output will be an indication of what fuel economy will be achieved based on current vehicle operational data inputs and a particular set of ECU programming. Other vehicle operators may want to emphasize fuel economy, subject to certain other limitations involving factors such as speed, horsepower, or engine load. For example, max fuel economy under certain conditions might be achieved by using an unacceptably low vehicle speed. In other conditions, max fuel economy may result when placing an unacceptable (for that operator at least) load on the engine (which may lead to reduced service life), so engine load may be an output important to some users. The specific output (or outputs) will also be related to the parameters (or parameters) that are being optimized. Most users will not really want maximum fuel economy, because to achieve max fuel economy an unrealistically low vehicle speed will be required (thus, even when fuel economy is a parameter to be optimized, one really is seeking to determine which ECU programming set will deliver max fuel economy at current conditions while maintaining vehicle speed, engine load, and/or engine RPMs within certain ranges selected by the user, such parameters being exemplary, not limiting). While considering ECU programming sets in light of optimizing fuel economy will likely be important to many users, some users (such as racing car drivers) may want to compare different ECU programming sets in light of optimizing horsepower (other users might want to optimize torque, or top speed). Thus, the output will be related to some predetermined vehicle characteristic that one seeks to optimize.
Thus block 192 involves comparing the results from each ECU programming set based on current vehicle operating conditions to identify the ECU programming set that optimizes vehicle performance based on predetermined parameters. Then it is determined if the current ECU programming set is the ECU programming set that that optimizes vehicle performance based on the predetermined parameters. It should be understood that the functions of block 192 can be implemented by a processor implementing suitable machine instructions, or a custom circuit,
In a block 196, a driver, a remote dispatcher, or processor determines that current ECU programming needs to be changed. Often such a change will be directed to changing speed limiting settings due to crossing a jurisdictional border, although changes for other purposes are encompassed by the concepts disclosed herein.
In a block 198, the current ECU programming set is changed as specified in block 196.
Although the concepts disclosed herein have been described in connection with the preferred form of practicing them and modifications thereto, those of ordinary skill in the art will understand that many other modifications can be made thereto within the scope of the claims that follow. Accordingly, it is not intended that the scope of these concepts in any way be limited by the above description, but instead be determined entirely by reference to the claims that follow.
This application is a continuation of U.S. patent application Ser. No. 13/854,913, filed on Apr. 1, 2013, which claims the benefit of U.S. Provisional Patent Application, Ser. No. 61/618,827, filed on Apr. 1, 2012, the benefit of the filing date of which is hereby claimed under 35 U.S.C. § 120.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3573620 | Ashley et al. | Apr 1971 | A |
| 3990067 | Van Dusen et al. | Nov 1976 | A |
| 4025791 | Lennington et al. | May 1977 | A |
| 4092718 | Wendt | May 1978 | A |
| 4258421 | Juhasz et al. | Mar 1981 | A |
| 4258521 | Fricker et al. | Mar 1981 | A |
| 4263945 | Van Ness | Apr 1981 | A |
| 4325057 | Bishop | Apr 1982 | A |
| 4469149 | Walkey et al. | Sep 1984 | A |
| 4602127 | Neely et al. | Jul 1986 | A |
| 4651157 | Gray et al. | Mar 1987 | A |
| 4658371 | Walsh et al. | Apr 1987 | A |
| 4688244 | Hannon et al. | Aug 1987 | A |
| 4750197 | Denekamp et al. | Jun 1988 | A |
| 4763356 | Day, Jr. et al. | Aug 1988 | A |
| 4799162 | Shinkawa et al. | Jan 1989 | A |
| 4804937 | Barbiaux et al. | Feb 1989 | A |
| 4814711 | Olsen et al. | Mar 1989 | A |
| 4846233 | Fockens | Jul 1989 | A |
| 4897792 | Hosoi | Jan 1990 | A |
| 4934419 | Lamont et al. | Jun 1990 | A |
| 4935195 | Palusamy et al. | Jun 1990 | A |
| 5006847 | Rush et al. | Apr 1991 | A |
| 5058044 | Stewart et al. | Oct 1991 | A |
| 5068656 | Sutherland | Nov 1991 | A |
| 5072380 | Randelman et al. | Dec 1991 | A |
| 5120942 | Holland et al. | Jun 1992 | A |
| 5128651 | Heckart | Jul 1992 | A |
| 5132906 | Sol et al. | Jul 1992 | A |
| 5163000 | Rogers et al. | Nov 1992 | A |
| 5204819 | Ryan | Apr 1993 | A |
| 5206643 | Eckelt | Apr 1993 | A |
| 5223844 | Mansell et al. | Jun 1993 | A |
| 5243323 | Rogers | Sep 1993 | A |
| 5243343 | Moriyasu | Sep 1993 | A |
| 5321629 | Shirata et al. | Jun 1994 | A |
| 5337003 | Carmichael et al. | Aug 1994 | A |
| 5359522 | Ryan | Oct 1994 | A |
| 5359528 | Haendel et al. | Oct 1994 | A |
| 5394136 | Lammers et al. | Feb 1995 | A |
| 5399844 | Holland | Mar 1995 | A |
| 5442553 | Parrillo | Aug 1995 | A |
| 5459304 | Eisenmann | Oct 1995 | A |
| 5459660 | Berra | Oct 1995 | A |
| 5479479 | Braitberg et al. | Dec 1995 | A |
| 5488352 | Jasper | Jan 1996 | A |
| 5499182 | Ousborne | Mar 1996 | A |
| 5541845 | Klein | Jul 1996 | A |
| 5546305 | Kondo | Aug 1996 | A |
| 5557254 | Johnson et al. | Sep 1996 | A |
| 5557268 | Hughes et al. | Sep 1996 | A |
| 5557628 | Kuba et al. | Sep 1996 | A |
| 5572192 | Berube | Nov 1996 | A |
| 5585552 | Heuston et al. | Dec 1996 | A |
| 5594650 | Shah et al. | Jan 1997 | A |
| 5596501 | Comer et al. | Jan 1997 | A |
| 5600323 | Boschini | Feb 1997 | A |
| 5610596 | Petitclerc | Mar 1997 | A |
| 5623258 | Dorfman | Apr 1997 | A |
| 5629678 | Gargano et al. | May 1997 | A |
| 5657010 | Jones | Aug 1997 | A |
| 5671158 | Fournier et al. | Sep 1997 | A |
| 5680328 | Skorupski et al. | Oct 1997 | A |
| 5711712 | Graf | Jan 1998 | A |
| 5719771 | Buck et al. | Feb 1998 | A |
| 5731893 | Dominique | Mar 1998 | A |
| 5732074 | Spaur et al. | Mar 1998 | A |
| 5742915 | Stafford | Apr 1998 | A |
| 5745049 | Akiyama et al. | Apr 1998 | A |
| 5748106 | Schoenian et al. | May 1998 | A |
| 5754965 | Hagenbuch | May 1998 | A |
| 5758299 | Sandborg et al. | May 1998 | A |
| 5758300 | Abe | May 1998 | A |
| 5768382 | Schneier et al. | Jun 1998 | A |
| 5781871 | Mezger et al. | Jul 1998 | A |
| 5794164 | Beckert et al. | Aug 1998 | A |
| 5804937 | Sasajima et al. | Sep 1998 | A |
| 5808565 | Matta et al. | Sep 1998 | A |
| 5809437 | Breed | Sep 1998 | A |
| 5815071 | Doyle | Sep 1998 | A |
| 5835871 | Smith et al. | Nov 1998 | A |
| 5838251 | Brinkmeyer et al. | Nov 1998 | A |
| 5839112 | Schreitmueller et al. | Nov 1998 | A |
| 5867404 | Bryan | Feb 1999 | A |
| 5871871 | Hogan et al. | Feb 1999 | A |
| 5874891 | Lowe | Feb 1999 | A |
| 5884202 | Arjomand | Mar 1999 | A |
| 5890061 | Timm et al. | Mar 1999 | A |
| 5890080 | Coverdill | Mar 1999 | A |
| 5890520 | Johnson, Jr. | Apr 1999 | A |
| 5892346 | Moroto et al. | Apr 1999 | A |
| 5894617 | Liou | Apr 1999 | A |
| 5913180 | Ryan | Jun 1999 | A |
| 5919239 | Fraker et al. | Jul 1999 | A |
| 5922037 | Potts | Jul 1999 | A |
| 5923572 | Pollock | Jul 1999 | A |
| 5928291 | Jenkins et al. | Jul 1999 | A |
| 5933844 | Young | Aug 1999 | A |
| 5942753 | Dell | Aug 1999 | A |
| 5956259 | Hartsell, Jr. et al. | Sep 1999 | A |
| 5983154 | Morisawa | Nov 1999 | A |
| 5987377 | Westerlage et al. | Nov 1999 | A |
| 5995895 | Watt et al. | Nov 1999 | A |
| 5995898 | Tuttle | Nov 1999 | A |
| 6009355 | Obradovich et al. | Dec 1999 | A |
| 6009363 | Beckert et al. | Dec 1999 | A |
| 6016457 | Toukura et al. | Jan 2000 | A |
| 6016795 | Ohki | Jan 2000 | A |
| 6024142 | Bates | Feb 2000 | A |
| 6025776 | Matsuura | Feb 2000 | A |
| 6038500 | Weiss | Mar 2000 | A |
| 6043661 | Gutierrez | Mar 2000 | A |
| 6049755 | Lou et al. | Apr 2000 | A |
| 6054950 | Fontana | Apr 2000 | A |
| 6061614 | Carrender et al. | May 2000 | A |
| 6064299 | Lesesky et al. | May 2000 | A |
| 6070118 | Ohta et al. | May 2000 | A |
| 6070156 | Hartsell, Jr. | May 2000 | A |
| 6078255 | Dividock et al. | Jun 2000 | A |
| 6084870 | Wooten et al. | Jul 2000 | A |
| 6092021 | Ehlbeck et al. | Jul 2000 | A |
| 6107915 | Reavell et al. | Aug 2000 | A |
| 6107917 | Carrender et al. | Aug 2000 | A |
| 6112152 | Tuttle | Aug 2000 | A |
| 6127947 | Uchida et al. | Oct 2000 | A |
| 6128551 | Davis | Oct 2000 | A |
| 6128959 | McGovern et al. | Oct 2000 | A |
| 6134499 | Goode et al. | Oct 2000 | A |
| 6169938 | Hartsell, Jr. | Jan 2001 | B1 |
| 6169943 | Simon et al. | Jan 2001 | B1 |
| 6199099 | Gershman et al. | Mar 2001 | B1 |
| 6202008 | Beckert et al. | Mar 2001 | B1 |
| 6208948 | Klingler et al. | Mar 2001 | B1 |
| 6236911 | Kruger | May 2001 | B1 |
| 6240365 | Bunn | May 2001 | B1 |
| 6253129 | Jenkins et al. | Jun 2001 | B1 |
| 6256579 | Tanimoto | Jul 2001 | B1 |
| 6259358 | Fjordbotten | Jul 2001 | B1 |
| 6263273 | Henneken et al. | Jul 2001 | B1 |
| 6263276 | Yokoyama et al. | Jul 2001 | B1 |
| 6278928 | Aruga et al. | Aug 2001 | B1 |
| 6278936 | Jones | Aug 2001 | B1 |
| 6285953 | Harrison et al. | Sep 2001 | B1 |
| 6295492 | Lang et al. | Sep 2001 | B1 |
| 6330499 | Chou et al. | Dec 2001 | B1 |
| 6339745 | Novik | Jan 2002 | B1 |
| 6362730 | Razavi et al. | Mar 2002 | B2 |
| 6370454 | Moore | Apr 2002 | B1 |
| 6374176 | Schmier et al. | Apr 2002 | B1 |
| 6396413 | Hines et al. | May 2002 | B2 |
| 6411203 | Lesesky et al. | Jun 2002 | B1 |
| 6411888 | Weisman, II | Jun 2002 | B1 |
| 6411891 | Jones | Jun 2002 | B1 |
| 6417760 | Mabuchi et al. | Jul 2002 | B1 |
| 6421790 | Fruehling et al. | Jul 2002 | B1 |
| 6438471 | Katagishi | Aug 2002 | B1 |
| 6438472 | Tano et al. | Aug 2002 | B1 |
| 6450411 | Rash et al. | Sep 2002 | B1 |
| 6456039 | Lauper et al. | Sep 2002 | B1 |
| 6502030 | Hilleary | Dec 2002 | B2 |
| 6505106 | Lawrence et al. | Jan 2003 | B1 |
| 6507810 | Razavi et al. | Jan 2003 | B2 |
| 6529723 | Bentley | Mar 2003 | B1 |
| 6529808 | Diem | Mar 2003 | B1 |
| 6535811 | Rowland et al. | Mar 2003 | B1 |
| 6539296 | Diaz et al. | Mar 2003 | B2 |
| 6571168 | Murphy et al. | May 2003 | B1 |
| 6587768 | Chene et al. | Jul 2003 | B2 |
| 6594579 | Lowrey et al. | Jul 2003 | B1 |
| 6594621 | Meeker | Jul 2003 | B1 |
| 6597973 | Barich et al. | Jul 2003 | B1 |
| 6604033 | Banet et al. | Aug 2003 | B1 |
| 6608554 | Lesesky et al. | Aug 2003 | B2 |
| 6609082 | Wagner | Aug 2003 | B2 |
| 6611740 | Lowrey et al. | Aug 2003 | B2 |
| 6614392 | Howard | Sep 2003 | B2 |
| 6616036 | Streicher et al. | Sep 2003 | B2 |
| 6621452 | Knockeart et al. | Sep 2003 | B2 |
| 6636790 | Lightner et al. | Oct 2003 | B1 |
| 6664897 | Pape et al. | Dec 2003 | B2 |
| 6671646 | Manegold et al. | Dec 2003 | B2 |
| 6680694 | Knockeart et al. | Jan 2004 | B1 |
| 6708113 | Von Gerlach et al. | Mar 2004 | B1 |
| 6714857 | Kapolka et al. | Mar 2004 | B2 |
| 6714859 | Jones | Mar 2004 | B2 |
| 6727818 | Wildman et al. | Apr 2004 | B1 |
| 6732031 | Lightner et al. | May 2004 | B1 |
| 6732032 | Banet et al. | May 2004 | B1 |
| 6735542 | Burgett et al. | May 2004 | B1 |
| 6744352 | Lesesky et al. | Jun 2004 | B2 |
| 6748318 | Jones | Jun 2004 | B1 |
| 6754183 | Razavi et al. | Jun 2004 | B1 |
| 6757606 | Gonring | Jun 2004 | B1 |
| 6768994 | Howard et al. | Jul 2004 | B1 |
| 6795761 | Lee et al. | Sep 2004 | B1 |
| 6801841 | Tabe | Oct 2004 | B2 |
| 6801901 | Ng | Oct 2004 | B1 |
| 6804606 | Jones | Oct 2004 | B2 |
| 6804626 | Manegold et al. | Oct 2004 | B2 |
| 6816762 | Hensey et al. | Nov 2004 | B2 |
| 6834259 | Markwitz et al. | Dec 2004 | B1 |
| 6839619 | Bellinger | Jan 2005 | B2 |
| 6847887 | Casino | Jan 2005 | B1 |
| 6856820 | Kolls | Feb 2005 | B1 |
| 6856897 | Phuyal et al. | Feb 2005 | B1 |
| 6876642 | Adams et al. | Apr 2005 | B1 |
| 6879894 | Lightner et al. | Apr 2005 | B1 |
| 6880390 | Emord | Apr 2005 | B2 |
| 6894617 | Richman | May 2005 | B2 |
| 6899151 | Latka et al. | May 2005 | B1 |
| 6904359 | Jones | Jun 2005 | B2 |
| 6909947 | Douros et al. | Jun 2005 | B2 |
| 6924750 | Flick | Aug 2005 | B2 |
| 6928348 | Lightner et al. | Aug 2005 | B1 |
| 6946953 | Lesesky et al. | Sep 2005 | B2 |
| 6952645 | Jones | Oct 2005 | B1 |
| 6954689 | Hanson et al. | Oct 2005 | B2 |
| 6957133 | Hunt et al. | Oct 2005 | B1 |
| 6972668 | Schauble | Dec 2005 | B2 |
| 6980093 | Oursler et al. | Dec 2005 | B2 |
| 6988033 | Lowrey et al. | Jan 2006 | B1 |
| 7022018 | Koga | Apr 2006 | B2 |
| 7027955 | Markwitz et al. | Apr 2006 | B2 |
| 7035733 | Alwar et al. | Apr 2006 | B1 |
| 7048185 | Hart | May 2006 | B2 |
| 7068301 | Thompson | Jun 2006 | B2 |
| 7103460 | Breed | Sep 2006 | B1 |
| 7113127 | Banet et al. | Sep 2006 | B1 |
| 7117121 | Brinton et al. | Oct 2006 | B2 |
| 7129852 | Aslund et al. | Oct 2006 | B2 |
| 7155199 | Zalewski et al. | Dec 2006 | B2 |
| 7171372 | Daniel et al. | Jan 2007 | B2 |
| 7174243 | Lightner et al. | Feb 2007 | B1 |
| 7174277 | Vock et al. | Feb 2007 | B2 |
| 7177750 | Schröder | Feb 2007 | B2 |
| 7184866 | Squires et al. | Feb 2007 | B2 |
| 7202801 | Chou | Apr 2007 | B2 |
| 7225065 | Hunt et al. | May 2007 | B1 |
| 7228211 | Lowrey et al. | Jun 2007 | B1 |
| 7254516 | Case, Jr. et al. | Aug 2007 | B2 |
| 7343252 | Wiens | Mar 2008 | B2 |
| 7362229 | Brinton et al. | Apr 2008 | B2 |
| 7366589 | Habermas | Apr 2008 | B2 |
| 7424414 | Craft | Sep 2008 | B2 |
| 7447574 | Washicko et al. | Nov 2008 | B1 |
| 7477968 | Lowrey et al. | Jan 2009 | B1 |
| 7480551 | Lowrey et al. | Jan 2009 | B1 |
| 7523159 | Williams et al. | Apr 2009 | B1 |
| 7532962 | Lowrey et al. | May 2009 | B1 |
| 7532963 | Lowrey et al. | May 2009 | B1 |
| 7590768 | Gormley | Sep 2009 | B2 |
| 7596437 | Hunt et al. | Sep 2009 | B1 |
| 7604169 | Demere | Oct 2009 | B2 |
| 7627546 | Moser et al. | Dec 2009 | B2 |
| 7640185 | Giordano et al. | Dec 2009 | B1 |
| 7650210 | Breed | Jan 2010 | B2 |
| 7660658 | Sheynblat | Feb 2010 | B2 |
| 7672756 | Breed | Mar 2010 | B2 |
| 7672763 | Hunt et al. | Mar 2010 | B1 |
| 7692552 | Harrington et al. | Apr 2010 | B2 |
| 7774123 | Schröder | Aug 2010 | B2 |
| 7778752 | Hunt et al. | Aug 2010 | B1 |
| 7783507 | Schick et al. | Aug 2010 | B2 |
| 7831368 | Schröder | Nov 2010 | B2 |
| 7841317 | Williams et al. | Nov 2010 | B2 |
| 7913664 | Williams et al. | Mar 2011 | B2 |
| 7925426 | Koebler et al. | Apr 2011 | B2 |
| 8014915 | Jeon | Sep 2011 | B2 |
| 8046501 | Gormley | Oct 2011 | B2 |
| 8090598 | Bauer et al. | Jan 2012 | B2 |
| 8140265 | Grush | Mar 2012 | B2 |
| 8140358 | Ling et al. | Mar 2012 | B1 |
| 8185293 | Jiang et al. | May 2012 | B2 |
| 8204634 | Schwarz et al. | Jun 2012 | B2 |
| 8219796 | Weiberle et al. | Jul 2012 | B2 |
| 8280573 | Sudou et al. | Oct 2012 | B2 |
| 8527132 | Mineta | Sep 2013 | B2 |
| 8560996 | Brebner et al. | Oct 2013 | B1 |
| 8577703 | McClellan et al. | Nov 2013 | B2 |
| 8604920 | Armitage et al. | Dec 2013 | B2 |
| 8849501 | Cook et al. | Sep 2014 | B2 |
| 8882634 | Banker et al. | Nov 2014 | B2 |
| 8914184 | McQuade et al. | Dec 2014 | B2 |
| 8918229 | Hunt et al. | Dec 2014 | B2 |
| 8924138 | Chauncey et al. | Dec 2014 | B2 |
| 8930040 | Gompert et al. | Jan 2015 | B2 |
| 8949008 | Krengiel | Feb 2015 | B2 |
| 8996287 | Davidson et al. | Mar 2015 | B2 |
| 9162573 | Grajkowski et al. | Oct 2015 | B2 |
| 9170913 | Hunt et al. | Oct 2015 | B2 |
| 9229906 | McQuade et al. | Jan 2016 | B2 |
| 9358986 | Hunt | Jun 2016 | B2 |
| 9393954 | Gibson et al. | Jul 2016 | B2 |
| 9447747 | Gibson et al. | Sep 2016 | B2 |
| 9527515 | Hunt et al. | Dec 2016 | B2 |
| 9631528 | Bradley et al. | Apr 2017 | B2 |
| 9747254 | McQuade et al. | Aug 2017 | B2 |
| 10056008 | Sweany et al. | Aug 2018 | B1 |
| 20010047283 | Melick et al. | Nov 2001 | A1 |
| 20010053983 | Reichwein et al. | Dec 2001 | A1 |
| 20020016655 | Joao | Feb 2002 | A1 |
| 20020022979 | Whipp et al. | Feb 2002 | A1 |
| 20020107833 | Kerkinni | Aug 2002 | A1 |
| 20020107873 | Winkler et al. | Aug 2002 | A1 |
| 20020111725 | Burge | Aug 2002 | A1 |
| 20020116122 | Satonaka | Aug 2002 | A1 |
| 20020132699 | Bellinger | Sep 2002 | A1 |
| 20020133275 | Thibault | Sep 2002 | A1 |
| 20020150050 | Nathanson | Oct 2002 | A1 |
| 20020165669 | Pinto et al. | Nov 2002 | A1 |
| 20020178147 | Arroyo et al. | Nov 2002 | A1 |
| 20030030550 | Talbot | Feb 2003 | A1 |
| 20030033071 | Kawasaki | Feb 2003 | A1 |
| 20030036823 | Mahvi | Feb 2003 | A1 |
| 20030060966 | MacPhail et al. | Mar 2003 | A1 |
| 20030120745 | Katagishi et al. | Jun 2003 | A1 |
| 20030132699 | Yamaguchi et al. | Jul 2003 | A1 |
| 20030146854 | Jones | Aug 2003 | A1 |
| 20030182033 | Underdahl et al. | Sep 2003 | A1 |
| 20030195696 | Jones | Oct 2003 | A1 |
| 20030195697 | Jones | Oct 2003 | A1 |
| 20030195698 | Jones | Oct 2003 | A1 |
| 20030195699 | Jones | Oct 2003 | A1 |
| 20030216847 | Bellinger | Nov 2003 | A1 |
| 20040006421 | Yanase | Jan 2004 | A1 |
| 20040039504 | Coffee et al. | Feb 2004 | A1 |
| 20040044452 | Bauer | Mar 2004 | A1 |
| 20040054470 | Farine et al. | Mar 2004 | A1 |
| 20040133336 | Fosseen | Jul 2004 | A1 |
| 20040230346 | Brooks et al. | Nov 2004 | A1 |
| 20040236596 | Chowdhary et al. | Nov 2004 | A1 |
| 20040243368 | Hiemer et al. | Dec 2004 | A1 |
| 20040249558 | Meaney | Dec 2004 | A1 |
| 20050010479 | Hannigan et al. | Jan 2005 | A1 |
| 20050021222 | Minami et al. | Jan 2005 | A1 |
| 20050072384 | Hadley et al. | Apr 2005 | A1 |
| 20050107946 | Shimizu et al. | May 2005 | A1 |
| 20050131625 | Birger et al. | Jun 2005 | A1 |
| 20050206534 | Yamane et al. | Sep 2005 | A1 |
| 20050209775 | Entenmann | Sep 2005 | A1 |
| 20050273250 | Hamilton et al. | Dec 2005 | A1 |
| 20060041337 | Augsburger | Feb 2006 | A1 |
| 20060047381 | Nguyen | Mar 2006 | A1 |
| 20060047384 | Robinson et al. | Mar 2006 | A1 |
| 20060106510 | Heffington | May 2006 | A1 |
| 20060111868 | Beshears et al. | May 2006 | A1 |
| 20060232406 | Filibeck | Oct 2006 | A1 |
| 20060246918 | Fok et al. | Nov 2006 | A1 |
| 20070001831 | Raz et al. | Jan 2007 | A1 |
| 20070038343 | Larschan et al. | Feb 2007 | A1 |
| 20070050193 | Larson | Mar 2007 | A1 |
| 20070069947 | Banet et al. | Mar 2007 | A1 |
| 20070083314 | Corigliano et al. | Apr 2007 | A1 |
| 20070143002 | Crowell et al. | Jun 2007 | A1 |
| 20070149184 | Viegers et al. | Jun 2007 | A1 |
| 20070156337 | Yanni | Jul 2007 | A1 |
| 20070168125 | Petrik | Jul 2007 | A1 |
| 20070174683 | Gehring et al. | Jul 2007 | A1 |
| 20070179709 | Doyle | Aug 2007 | A1 |
| 20070192012 | Letang | Aug 2007 | A1 |
| 20070256481 | Nishiyama et al. | Nov 2007 | A1 |
| 20070293369 | Hornbrook et al. | Dec 2007 | A1 |
| 20080027591 | Lenser et al. | Jan 2008 | A1 |
| 20080077299 | Arshad et al. | Mar 2008 | A1 |
| 20080086241 | Phillips et al. | Apr 2008 | A1 |
| 20080109122 | Ferguson et al. | May 2008 | A1 |
| 20080121443 | Clark et al. | May 2008 | A1 |
| 20080154489 | Kaneda et al. | Jun 2008 | A1 |
| 20080154712 | Wellman | Jun 2008 | A1 |
| 20080167767 | Brooks et al. | Jul 2008 | A1 |
| 20080243389 | Inoue et al. | Oct 2008 | A1 |
| 20080262646 | Breed | Oct 2008 | A1 |
| 20080269974 | Schwarz et al. | Oct 2008 | A1 |
| 20080319602 | McClellan et al. | Dec 2008 | A1 |
| 20080319665 | Berkobin et al. | Dec 2008 | A1 |
| 20090037033 | Phillips et al. | Feb 2009 | A1 |
| 20090069999 | Bos | Mar 2009 | A1 |
| 20090093941 | Drazich | Apr 2009 | A1 |
| 20090126691 | Bach | May 2009 | A1 |
| 20090143923 | Breed | Jun 2009 | A1 |
| 20090156310 | Fargo | Jun 2009 | A1 |
| 20090157267 | Shin et al. | Jun 2009 | A1 |
| 20090160675 | Piccinini et al. | Jun 2009 | A1 |
| 20090164081 | Meloche et al. | Jun 2009 | A1 |
| 20090177350 | Williams et al. | Jul 2009 | A1 |
| 20090186325 | Kumar | Jul 2009 | A1 |
| 20090222200 | Link, II et al. | Sep 2009 | A1 |
| 20090240391 | Duddle et al. | Sep 2009 | A1 |
| 20090254259 | The | Oct 2009 | A1 |
| 20100005280 | Wagner | Jan 2010 | A1 |
| 20100009696 | Fok et al. | Jan 2010 | A1 |
| 20100017236 | Duddle et al. | Jan 2010 | A1 |
| 20100082238 | Nakamura | Apr 2010 | A1 |
| 20100088127 | Betancourt et al. | Apr 2010 | A1 |
| 20100114404 | Donnelly | May 2010 | A1 |
| 20100121539 | Price et al. | May 2010 | A1 |
| 20100145550 | Ross-Martin | Jun 2010 | A1 |
| 20100145600 | Son et al. | Jun 2010 | A1 |
| 20100152941 | Skaff et al. | Jun 2010 | A1 |
| 20100160013 | Sanders | Jun 2010 | A1 |
| 20100161172 | Bjelkstal | Jun 2010 | A1 |
| 20100191403 | Krause | Jul 2010 | A1 |
| 20100198466 | Eklund et al. | Aug 2010 | A1 |
| 20100204882 | Giovaresco et al. | Aug 2010 | A1 |
| 20100207760 | Stomski | Aug 2010 | A1 |
| 20100209884 | Lin et al. | Aug 2010 | A1 |
| 20100209890 | Huang et al. | Aug 2010 | A1 |
| 20100209891 | Lin et al. | Aug 2010 | A1 |
| 20100211278 | Craig et al. | Aug 2010 | A1 |
| 20100250056 | Perkins | Sep 2010 | A1 |
| 20100265034 | Cap et al. | Oct 2010 | A1 |
| 20100305819 | Pihlajamaki | Dec 2010 | A1 |
| 20100324955 | Rinehart et al. | Dec 2010 | A1 |
| 20110098898 | Stählin et al. | Apr 2011 | A1 |
| 20110106374 | Margol | May 2011 | A1 |
| 20110106388 | Boeckenhoff et al. | May 2011 | A1 |
| 20110112739 | O'Dea et al. | May 2011 | A1 |
| 20110137773 | Davis, III et al. | Jun 2011 | A1 |
| 20110148618 | Harumoto et al. | Jun 2011 | A1 |
| 20110161116 | Peak et al. | Jun 2011 | A1 |
| 20110172895 | Fukumoto et al. | Jul 2011 | A1 |
| 20110178684 | Umemoto et al. | Jul 2011 | A1 |
| 20110184642 | Rotz et al. | Jul 2011 | A1 |
| 20110276209 | Suganuma et al. | Nov 2011 | A1 |
| 20110279255 | Miyoshi | Nov 2011 | A1 |
| 20110307166 | Hiestermann et al. | Dec 2011 | A1 |
| 20110307336 | Smirnov et al. | Dec 2011 | A1 |
| 20110313647 | Koebler et al. | Dec 2011 | A1 |
| 20120041638 | Johnson et al. | Feb 2012 | A1 |
| 20120083958 | Ballard | Apr 2012 | A1 |
| 20120087771 | Wenzel | Apr 2012 | A1 |
| 20120136539 | Bryant et al. | May 2012 | A1 |
| 20120143484 | Sawada | Jun 2012 | A1 |
| 20120191269 | Chen et al. | Jul 2012 | A1 |
| 20120221216 | Chauncey et al. | Aug 2012 | A1 |
| 20120221234 | Sujan et al. | Aug 2012 | A1 |
| 20120226391 | Fryer et al. | Sep 2012 | A1 |
| 20120239279 | Stuart et al. | Sep 2012 | A1 |
| 20120239462 | Pursell et al. | Sep 2012 | A1 |
| 20120253744 | Schmidt | Oct 2012 | A1 |
| 20120256770 | Mitchell | Oct 2012 | A1 |
| 20120268587 | Robbins et al. | Oct 2012 | A1 |
| 20120277949 | Ghimire et al. | Nov 2012 | A1 |
| 20120296532 | Murakami et al. | Nov 2012 | A1 |
| 20120296549 | Adams | Nov 2012 | A1 |
| 20120323402 | Murakami | Dec 2012 | A1 |
| 20130006469 | Green et al. | Jan 2013 | A1 |
| 20130030660 | Fujimoto | Jan 2013 | A1 |
| 20130030667 | Fujimoto et al. | Jan 2013 | A1 |
| 20130046559 | Coleman et al. | Feb 2013 | A1 |
| 20130061044 | Pinkus et al. | Mar 2013 | A1 |
| 20130079950 | You | Mar 2013 | A1 |
| 20130138288 | Nickolaou et al. | May 2013 | A1 |
| 20130158838 | Yorke et al. | Jun 2013 | A1 |
| 20130164712 | Hunt et al. | Jun 2013 | A1 |
| 20130164713 | Hunt et al. | Jun 2013 | A1 |
| 20130164715 | Hunt et al. | Jun 2013 | A1 |
| 20130166170 | Hunt et al. | Jun 2013 | A1 |
| 20130184965 | Hunt et al. | Jul 2013 | A1 |
| 20130209968 | Miller et al. | Aug 2013 | A1 |
| 20130238182 | Osagawa et al. | Sep 2013 | A1 |
| 20130261939 | McQuade et al. | Oct 2013 | A1 |
| 20130261942 | McQuade et al. | Oct 2013 | A1 |
| 20130274955 | Rosenbaum | Oct 2013 | A1 |
| 20130345914 | Love et al. | Dec 2013 | A1 |
| 20130345927 | Cook et al. | Dec 2013 | A1 |
| 20140012634 | Pearlman et al. | Jan 2014 | A1 |
| 20140109075 | Hoffman et al. | Apr 2014 | A1 |
| 20140195106 | McQuade et al. | Jul 2014 | A1 |
| 20140257943 | Nerayoff et al. | Sep 2014 | A1 |
| 20140309844 | Breed | Oct 2014 | A1 |
| 20140309849 | Ricci | Oct 2014 | A1 |
| 20140350777 | Kawai et al. | Nov 2014 | A1 |
| 20140365070 | Yano et al. | Dec 2014 | A1 |
| 20150291176 | Jeong et al. | Oct 2015 | A1 |
| 20170066453 | Hunt | Mar 2017 | A1 |
| 20170067385 | Hunt | Mar 2017 | A1 |
| 20170084091 | McQuade et al. | Mar 2017 | A1 |
| 20170123784 | Zymeri et al. | May 2017 | A1 |
| 20170329742 | McQuade et al. | Nov 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2138378 | Nov 1994 | CA |
| 2 326 892 | Oct 1999 | CA |
| 2 388 572 | May 2001 | CA |
| 0 755 039 | Jan 1997 | EP |
| 0 814 447 | Dec 1997 | EP |
| 0 926 020 | Jun 1999 | EP |
| 1 067 498 | Jan 2001 | EP |
| 1 271 374 | Jan 2003 | EP |
| 1 005 627 | Oct 2003 | EP |
| 1 027 792 | Jan 2004 | EP |
| 2 116 968 | Nov 2009 | EP |
| 2001-280985 | Oct 2001 | JP |
| 9726750 | Jul 1997 | WO |
| 9803952 | Jan 1998 | WO |
| 9830920 | Jul 1998 | WO |
| 03023550 | Mar 2003 | WO |
| 2007092711 | Aug 2007 | WO |
| Entry |
|---|
| “Nextel, Motorola and Symbol Technologies Offer First Wireless Bar Code Scanner for Mobile Phones,” The Auto Channel, Jun. 11, 2003, URL=https://www.theautochannel.com/news/2003/06/11/162927.html, download date Aug. 28, 2017, 4 pages. |
| “ObjectFX Integrates TrackingAdvisor with QUALCOMM's FleetAdvisor System; Updated Version Offers Benefit of Visual Display of Vehicles and Routes to Improve Fleet Productivity,” Business Wire, Oct. 27, 2003, URL=https://www.thefreelibrary.com/_/print/PrintArticle.aspx?id=109283193, download date Aug. 28, 2017, 3 pages. |
| “Private fleets moving to wireless communications,” Drivers, May 1, 1997, URL=https://web.archive.org/web/20060511114359/driversmag.com/ar/fleet_private_fleets_moving/index.html, download date Aug. 28, 2017, 4 pages. |
| Albright, “Indiana embarks on ambitious RFID roll out,” Frontline Solutions, May 20, 2002, URL=https://web.archive.org/web/20021102141244/http://www.frontlinetoday.com/frontline/article/articleDetail.jsp?id=19358, download date Aug. 28, 2017, 3 pages. |
| Anonymous, “Transit agency builds GIS to plan bus routes”, American City & Country 118(4):14-16, Apr. 1, 2003. (4 pages). |
| Banks et al., “DATATRAK Automatic Vehicle Location and Position Reporting System,” Vehicle Navigation and Information Systems Conference, Toronto, Canada, Sep. 11-13, 1989, pp. 214-218. |
| Banks, “Integrated Automatic Vehicle Location and Position Reporting System,” 2nd International Conference on Road Traffic Monitoring, London, United Kingdom, Feb. 7-9, 1989, pp. 195-199. |
| Black, “OBD II Up Close,” MOTOR:28-34, Jul. 1998. (6 pages). |
| Child Checkmate Systems Inc., “What is the Child Check-Mate Safety System,” URLs=http://www.childcheckmate.com/what.html, http://www.childcheckmate.com/overview.html, http://www.childcheckmate.com/how.html, download date Apr. 7, 2004, 5 pages. |
| Detex, “Detex Announces the Latest Innovation in Guard Tour Verification Technology,” Jan. 1, 2003, URL=https://web.archive.org/web/20031208082505/http://www.detex.com/NewsAction.jspa?id=3, download date Aug. 28, 2017, 1 page. |
| Dwyer et al., “Analysis of the Performance and Emissions of Different Bus Technologies on the City of San Francisco,” SAE Commercial Vehicle Engineering Congress and Exhibition, Rosemont, Illinois, USA, Oct. 26-28, 2004. (Abstract only) (2 pages). |
| FleeTTrakkeR, “D.O.T. Driver Vehicle Inspection Reports on your wireless phone?,” ReporTTrakkeR, URL=http://www.fleettrakker.com/web/index.jsp, download date Mar. 12, 2004, 3 pages. |
| GCS General Control Systems, “The Data Acquisition Unit Escorte,” Nov. 20, 2001, URL=http://www.gcs.at/eng/produkte/hw/escorte.htm, download date Apr. 21, 2005, 4 pages. |
| GCS General Control Systems, “The PenMaster,” and “The PSION Workabout,” Nov. 20, 2001, URL=http://www.gcs.at/eng/produkte/hw/penmaster.htm, download date Apr. 5, 2007, 3 pages. |
| GCS General Control Systems, News, Dec. 11, 2002, URL=http://www.gcs.at/eng/news/allgemein.htm, download date Apr. 21, 2005, 2 pages. |
| Ghilardelli et al., “Path Generation Using η4-Splines for a Truck and Trailer Vehicle,” IEEE Transactions on Automation Science and Engineering 11(1):187-203, 2014. |
| Guensler et al., “Development of a Comprehensive Vehicle Instrumentation Package for Monitoring Individual Tripmaking Behavior,” Technical Specifications and Analysis, Georgia Institute of Technology, School of Civil and Environmental Engineering, Atlanta, Georgia, USA, Feb. 1999, 31 pages. |
| Jenkins et al., “Real-Time Vehicle Performance Monitoring Using Wireless Networking,” Proceedings of the 3rd IASTED International Conference on Communications, Internet and Information Technology, St. Thomas, US Virgin Islands, Nov. 22-24, 2004, pp. 375-380. |
| Kurtz, “Indiana's E-Government: A Story Behind Its Ranking,” INContext 4(1):6-8, 2003. |
| Kwon, “Networking Technologies of In-Vehicle,” Seoul National University, School of Electrical Engineering, Seoul, South Korea, Mar. 8, 2000, 44 pages. |
| Leavitt, “The Convergence Zone,” FleetOwner, Jun. 1, 1998, URL=http://www.driversmag.com/ar/fleet_convergence_zone/index.html, download date Aug. 24, 2010, 4 pages. |
| MIRAS, “About SPS Technologies,” as archived on May 7, 1999, URL=http://replay.waybackmachine.org/19990507195047/http://www.miras.com/html/about_sps_technologies.html, download date Sep. 29, 2010, 1 page. |
| MIRAS, “How MIRAS Works,” as archived on Apr. 29, 1999, URL=http://replay.waybackmachine.org/19990429144910/http://www.miras.com/html/products.html, download date Sep. 29, 2010, 1 page. |
| MIRAS, “MIRAS Unit,” as archived on May 4, 1999, URL=http://replay.waybackmachine.org/19990504052250/http://www.miras.com/html/1000unit.html, download date Sep. 29, 2010, 1 page. |
| MIRAS, “Monitoring Vehicle Functions,” as archived on Apr. 27, 1999, URL=http://replay.waybackmachine.org/19990427152518/http://www.miras.com/html/monitoring.html, download date Sep. 29, 2010, 1 page. |
| MIRAS, “Remote Control,” as archived on Apr. 29, 1999, URL=http://replay.waybackmachine.org/19990429145717/http://www.miras.com/html/remote_control.html, download date Sep. 29, 2010, 1 page. |
| MIRAS, “Tracking & Monitoring Software,” as archived on Apr. 29, 1999, URL=http://replay.waybackmachine.org/19990429160322/http://www.miras.com/html/software.html, download date Sep. 29, 2010, 1 page. |
| MIRAS, MIRAS 4.0 Screenshot, as archived on May 7, 1999, URL=http://replay.waybackmachine.org/19990507205618/http://www.miras.com/html/largescreen.html, download date Sep. 29, 2010, 1 page. |
| “MIRAS GPS vehicle tracking using the Internet,” Business Wire, Nov. 22, 1996, URL=https://www.thefreelibrary.com/_/print/PrintArticle.aspx?id=18878231, download date Aug. 28, 2017, 2 pages. |
| Pan et al., “Simulation-Based Optimization for Split Delivery Vehicle Routing Problem: A Report of Ongoing Study,” Proceedings of the 2013 Winter Simulation Conference, Washington D.C., USA, Dec. 8-11, 2013, pp. 1089-1096. |
| Papadoglou et al., “Short message service link for automatic vehicle location reporting,” Electronics Letters 35(11):876-877, 1999. |
| Quaan et al., Guard Tour Systems, post dates Sep. 16, 2003, Oct. 3, 2003, and Sep. 4, 2004, URL=http://www.securitymanagement.com/ubb/Forum30/HTML/000066.html, download date Mar. 8, 2005, 1 page. |
| Rehman et al., “Characterisation of System Performance of GPS Antennas in Mobile Terminals Including Environmental Effects,” 3rd European Conference on Antennas and Propagation, Berlin, Germany, Mar. 23-27, 2009, pp. 1832-1836. |
| Senger, “Inside RF/ID: Carving A Niche Beyond Asset Tracking,” Business Solutions, Feb. 1, 1999, 3 pages. |
| Sterzbach et al., “A Mobile Vehicle On-Board Computing and Communication System,” Computers & Graphics 20(4):659-667, 1996. |
| The Gale Group, “Tracking out of route: software helps fleets compare planned routes to actual miles.(Technology),” Commercial Carrier Journal 162(10):S46, 2005. (4 pages). |
| TISCOR, “Inspection Manager 6.0,” Product User Guide, 2004, 73 pages. |
| TISCOR, “Inspection Manager: An Introduction,” Sep. 27, 2004, 19 pages. |
| Tsakiri et al., “Urban Fleet Monitoring with GPS and GLONASS,” The Journal of Navigation 51(3):382-393, 1998. (Abstract only) (2 pages). |
| Tuttle, “Digital RF/ID Enhances GPS,” Proceedings of the 2nd Annual Wireless Symposium, Santa Clara, California, USA, Feb. 15-18, 1994, pp. 406-411. |
| Want, “RFID: A Key to Automating Everything,” Scientific American 290(1):56-65, 2004. |
| Zujkowski, “Savi Technology, Inc.: Savi Security and Productivity Systems,” Remarks, ATA Security Forum, Chicago, Illinois, USA, May 15, 2002, 21 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170322907 A1 | Nov 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61618827 | Apr 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13854913 | Apr 2013 | US |
| Child | 15657023 | US |
