Patent Grant
9067565
The present invention relates generally to a system and method for monitoring driver behavior and vehicle driving conditions and, more particularly, to a system and method for grading a driver's performance.
The present invention relates generally to asset management and, more particularly, to a fleet management system incorporating comprehensive driver monitoring/mentoring and asset monitoring capabilities in order to improve driver safety and reduce fuel and maintenance costs across a fleet of vehicles. Advantageously, the fleet management system is fully-configurable at all times including during installation of the system as well as during operation thereof. In addition, the present invention relates to a system and method for monitoring driver behavior for use by consumers or the general public such that parents may remotely mentor the driving habits of their teen children as well as allow for monitoring of geographic areas into which their children may enter. Also, the present invention provides a means for recording impulse forces experienced by a vehicle during a crash event in order to provide real-time notification to fleet management personnel as well as to provide data which may facilitate accident reconstruction and which may be used in the courtroom and by the auto insurance industry.
A recent study released by the Federal Motor Carrier Safety Administration (FMCSA) indicated that driver error was ten times more likely to be the cause of truck-related accidents as compared to other factors such as poor road conditions, weather and mechanical malfunctions. Specifically, the study indicated that certain driver factors such as speeding, inattention, fatigue and unfamiliarity with roads accounted for 88 percent of all crashes involving large trucks. As a means to reduce truck-related accidents, the FMCSA study recommended that greater attention be focused on developing systems for monitoring at-risk driver behavior in commercial motor vehicle fleets in order to improve driver safety.
Losses as a result of accidents involving large truck crashes includes property damage to vehicle and structures as well as personal injury to drivers, occupants and occasionally bystanders. In addition to the financial losses and injuries resulting from truck crashes, fleet operators incur losses as a result of excess fuel and maintenance costs, as well as losses due to inefficient management of individual vehicles in the fleet as well as groups of fleet vehicles such as those located in a specific geographic area. Fleet operators may also suffer losses as a result of vehicle theft, inefficient vehicle routing as a result of unforeseen adverse road conditions along a route, and human losses such as may occur when the driver is injured while performing extravehicular duties.
Included in the prior art are several systems which attempt to address either the problem of driver error as a cause of accidents or by attempting to reduce losses due to inefficient fleet management. For example, U.S. Patent Publication No. 2004/0039504 assigned to Fleet Management Services, Inc., discloses a fleet management information system for identifying the location and direction of movement of each vehicle in the fleet. The Fleet Management Services application discloses that each vehicle in the fleet is in communication directly with management offices in real-time to report vehicle location and heading as well as the status of certain events in which the vehicle may be engaged.
One of the stated objects of the fleet management system disclosed in the application is to improve the availability of fleet management information to owners and operators so as to improve vehicle tracking and enhanced communication within the fleet to increase asset profitability. The application indicates that the above-mentioned objects are facilitated by providing the capability to locate vehicles in the fleet in real-time as well as improving the efficiency of wireless communication within the fleet.
Although the application assigned to Fleet Management Services, Inc., as disclosed above is understood to provide improved fleet business management by minimizing gap times in time division multiple access (TDMA) networks during data transmissions, the application is not understood to address the issue of monitoring driver behavior and/or driver performance in order to improve driver safety and asset health. Furthermore, the application disclosed above is not understood to improve other aspects of fleet operation such as improving fuel economy and reducing maintenance costs of a fleet. In this regard, the application is only understood to improve communication within the fleet and is not understood to improve the amount of information available regarding the operation of each vehicle such that analysis of similar problems may be performed in order to establish trends and ultimately correct problems over time.
U.S. Pat. No. 6,124,810 issued to Segal et al. and assigned to Qualcomm, Inc. discloses a method for determining when a vehicle has arrived and departed from a specific location. More particularly, the Segal patent discloses an apparatus having an on-board mobile communication terminal for receiving destination information wirelessly from a central facility. The apparatus incorporates velocity data from a vehicle speedometer in combination with a communication satellite system in order to provide vehicle position data to a processor.
The processor, located on-board the vehicle, uses speed and position data to determine the vehicle arrival or departure times which is wireless transmitted to the central facility. Although the device of the Segal patent is understood to improve fleet efficiency due to its autonomous transmission of arrival and departure times between a vehicle and a dispatch center, the Segal patent is not understood to address the issue of reducing aggressive driver behavior such as reducing speeding which would improve fleet safety.
U.S. Pat. No. 5,638,077 issued to Martin and assigned to Rockwell International Corporation discloses a fleet management that transmits vehicle positional data to a base station with a time annotation. The positional data further includes velocity data as well as the identity of satellites observed. In this manner, the fleet management system of the Martin reference ostensibly improves fleet management capability by improving the accuracy of GPS positional and directional information. However, the device fails to address the above-noted problems associated with improving driver behavior in fleet operations in order to reduce accident rates and lower fleet operation costs.
As can be seen, there exists a need in the art for a driver mentoring system adaptable for use in commercial fleet operations that monitors at risk and/or unsafe driver behavior and provides mentoring to the driver in order to reduce adverse driver actions and inactions that may lead to accidents. In addition, there exists a need in the art for a driver mentoring system that allows for accurate vehicle tracking at a base station and which can incorporate a third party mapping database in order to provide maximum road speed data for any particular location on a road such that the driver may avoid speeding violations and/or maintain safe, legal, and established speed limits.
Furthermore, there exists a need in the art for a vehicle behavior monitoring system that records velocity and acceleration impulse forces imposed on a vehicle during a crash for use in accident reconstruction for insurance claim and courtroom purposes. Finally, there exists a need in the art for a vehicle behavior monitoring system that provides for real-time reconfiguration of driver performance and vehicle operation parameters from a base station to individual vehicles in a fleet and which allows for reporting of such data in order to generate driver profiles and trends, calculate fuel and mileage tax and create hours of service reports in compliance with federal requirements.
The present invention specifically addresses the above-mentioned needs associated with fleet management by providing a unique vehicle monitoring system specifically adapted to mentor driver performance in order to improve driver safety and reduce accident rates as well as reduce fuel and maintenance costs (as a secondary benefit to good driving behavior—driving the speed limit on paved roads and driving specified and/or configured speed limits on non-paved roads).
In another aspect of the invention, the vehicle monitoring system allows for the recording of crash impulse forces acting on the vehicle during an accident for accident reconstruction purposes and for insurance and injury claim purposes. Fleet utilization is improved by real-time or over-time tracking by GPS of all vehicles in the fleet or tracking per geographic zone, by group, and individually.
The present invention also generates automated International Fuel Tax Agreement (IFTA) reports, mileage reports, hours-of-service (HOS) reports required by the Department of Transportation (DOT) and provides real-time updates on driver behavior and vehicle operation that is accessible anywhere via the internet. Advantageously, the system is fully-configurable in all aspects and at any time including reconfiguring during installation of the system as well as during operation. For example, the invention provides a means by which fleet management can reconfigure the vehicle monitoring system by remote command in order to revise various system parameters such as the type of data to be reported and how often. Conversely, the system can be reconfigured at the vehicle in a comprehensive manner.
Two-way communication between the fleet vehicles and the base station or server allows for notification of fleet management and/or safety personnel during an emergency, during an exception event such as excessive speeding or swerving by a driver, or to allow drivers to report in at specific intervals and times or upon the occurrence of specific events.
These and other features and advantages of the various embodiments disclosed herein will be better understood with respect to the following description and drawings wherein:
The making and using of the presently preferred embodiments are discussed in detail below. It should be appreciated, however, that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed are merely illustrative of specific ways to make and use the invention, and do not limit the scope of the invention.
Referring now to the drawings wherein the showings are for purposes of illustrating preferred embodiments of the present invention and not for purposes of limiting the same, shown in
In one aspect of the invention, a vehicle monitoring system is provided for monitoring at least one vehicle 101-103 in the fleet as well as monitoring driver behavior in order to improve safety and reduce fuel and maintenance costs for the fleet. Driver behavior is monitored with the aid of an accelerometer module (XLM) 201 (
For example, excessive lateral acceleration may be an indication that the driver is operating the vehicle 101-103 at an excessive speed around a turn along a roadway. Furthermore, it is possible that the driver may be traveling at a speed well within the posted speed limit for that area of roadway. However, excessive lateral acceleration, defined herein as “hard turns,” may be indicative of aggressive driving by the driver and may contribute to excessive wear on tires and steering components as well as potentially causing the load such as a trailer to shift and potentially overturn.
Furthermore, such hard turns by a particular driver could eventually result in personal injury to the driver/occupants as well as property damage to the vehicle 101-103 and load carried thereby and damage to anything impacted by the vehicle 101-103 should it depart the roadway. Ultimately, such hard turns could result in loss of life if the vehicle is a large truck and the driver loses control resulting in a collision with a smaller vehicle such as a passenger automobile.
As such, it can be seen that monitoring and mentoring such driver behavior by providing warnings to the driver during the occurrence of aggressive driving such as hard turns can improve safety and reduce accidents. In addition, mentoring such aggressive driver behavior can reduce wear and tear on the vehicle and ultimately reduce fleet maintenance costs as well as reduce insurance costs and identify at risk drivers and driving behavior to fleet managers.
In one aspect, the vehicle monitoring system includes a master command module (MCM) 202 which may be in data communication with an on board diagnostic (OBD) II system 203 of the vehicle such as via a port. In some vehicle models, the MCM 202 is placed in data communication with a controller area network (CAN) system (bus) 203 to allow acquisition by the MCM of certain vehicle operating parameters including, but not limited to, vehicle speed such as via the speedometer, engine speed or throttle position such as via the tachometer, mileage such as via the odometer reading, seat belt status, condition of various vehicle systems including anti-lock-braking (ABS), turn signal, headlight, cruise control activation and a multitude of various other diagnostic parameters such as engine temperature, brake wear, etc.
All cars built since Jan. 1, 1996 have OBD-II systems. There are five basic OBD-II protocols in use, each with minor variations on the communication pattern between the on-board diagnostic computer and a maintenance scanner console or tool. By 2008, all vehicles sold in the United States will be required to implement the CAN bus (ISO 15765 CAN), thus eliminating the ambiguity of the existing five signaling protocols. While there are various electrical connection protocols, the command set is fixed according to the SAE J1979 standard. All OBD-II cars have a connector located in the passenger compartment easily accessible from the driver's seat, such as under the dash or behind or near the ashtray. The OBD-II standard specifies a 16-pin J1962 connector and its pinout, the electrical signaling protocols available, and the messaging format. It also includes a list of vehicle parameters to monitor and instructions regarding how to encode the data for each parameter. SAE J1962 defines the pinout of the connector and requires that pins 4 (battery ground) and 16 (battery positive) are present in all configurations.
The OBD or CAN 203 allows for acquisition of the above-mentioned vehicle parameters by the MCM 202 for processing thereby and/or for subsequent transmission to the database 106. In order to enhance reliability and extend its useful life, it is contemplated that the MCM 202 is housed in a sealable housing which may be configured to provide varying degrees of waterproof protection. For operation in extreme temperatures, a heater mechanism may be provided to the housing to enable reliable operation in cold and severe service environments. Ideally, the housing contents (e.g., MCM 202) or the housing itself is configured to withstand excessive vibration and/or shock. The MCM 202 may be mounted in any location in the vehicle such as underneath the seat. The MCM 202 may further include an external power source 204 such as a battery, fuel cell, recharger, AC/DC adapter, DC bus—accessory or cigarette lighter plug, hot lead to vehicle fuse panel, etc., for powering the MCM 202.
The vehicle monitoring system may further include a self-contained and tamper-resistant event data recorder or crash data recorder (CDR) 205 similar to that which is shown and disclosed in U.S. Pat. Nos. 6,266,588 and 6,549,834 issued to McClellan et al., (the disclosures of which are hereby incorporated by reference herein in their entirety) and which is commercially known as “Witness” and commercially available from Independent Witness, Inc. of Salt Lake City, Utah. The CDR 205 is adapted to continuously monitor vehicle motion and begin recording upon supra-threshold impacts whereupon it records the magnitude and direction of accelerations or G-forces experienced by the vehicle as well as recording an acceleration time-history of the impact event and velocity change between pre- and post-impact for a configurable duration following said impact. The recordings are time-date stamped and are providable to the MCM 202 for subsequent transmission to the server DCS 106 if accelerations exceed an impulse threshold.
In addition, the CDR 205 is configured such that data is downloadable such as via a laptop directly from the CDR 205 at the scene of the accident or the CDR itself can be removed from the vehicle for later downloading of data. As will be described in greater detail below, the data (e.g., crash impulses) recorded by the CDR 205 can be correlated to accident severity and injury potential. It is contemplated that CDR data can be combined with recording of driver behavior via the accelerometer module (XLM) 201 in order to determine the probability of crash impact as a cause of personal injury and/or property damage.
Furthermore, the CDR 205 such as that disclosed in the McClellan references is Society of Automotive Engineers (SAE) J211-compliant such that data recorded thereby is admissible in court and can be used to facilitate accident reconstruction as well as for insurance claim purposes. As was earlier mentioned, the CDR 205 is a self-contained component that includes its own power source such as a battery 206 such that the vehicle can operate regardless of the lack of power from the vehicle due to the accident.
Importantly, the XLM 201 may be integrated with the MCM 202 and mounted within the housing. The XLM 201 is operative to monitor driver performance by measuring vehicle acceleration in at least one of lateral, longitudinal and vertical directions over a predetermined time period such as over seconds or minutes. The XLM 201 may include a single uni-axial accelerometer to measure acceleration in any one of the three above-mentioned directions such as in the lateral direction.
Alternatively, the accelerometer may be a bi-axial or a tri-axial accelerometer for measuring acceleration in two or three of the above-mentioned directions or two or three uni-axial accelerometers may be combined to provide measurements. In addition, accelerometers may be oriented in the XLM 201 to measure centripetal, centrifugal, radial, tangential acceleration or acceleration in any other direction. The XLM 201 generates an input signal to the MCM 202 when measured acceleration exceeds a predetermined threshold. Similarly, the XLM 201 may be configured to monitor and record both the day-to-day driving performance as well as capture the crash pulse. Advantageously, the base station and/or MCM 202 is configured to filter out or compensate for gravitational effects on longitudinal, lateral and vertical acceleration measurements when the vehicle is moving on hilly terrain.
As was earlier noted, the vehicle monitoring system includes a GPS receiver 207 in each vehicle in the fleet and which is configured to track in at least one of real-time or over-time modes the location and directional movement of the vehicle. As is well known in the art, signals from at least three GPS satellites 107 (
The vehicle monitoring system may further include a mobile data terminal (MDT) 208 which may be conveniently mounted for observation and manipulation by the driver such as near the vehicle dash. The MDT 208 preferably has an operator interface 209 such as a keypad, keyboard, touch screen, display screen or any suitable user input device and may further include audio input capability such as a microphone to allow voice communications. Importantly, the MDT 208 may include at least one warning mechanism 210 such as an external speaker and/or a warning light 210 for warning the driver of violation of posted speed limits and/or exceeding acceleration thresholds in lateral, longitudinal and vertical directions as an indication of hard turns, hard braking or hard vertical, respectively. In addition, the MDT 208 may include a manual RF disable switch 211 to prevent RF emissions by the vehicle monitoring system in areas that are sensitive to RF energy.
As was earlier mentioned, the MCM 202 is adapted to receive input signals from the OBD or CAN 203, GPS receiver 207, CDR 205, MDT 208 and XLM 201 and, in this regard, may be hardwired such as to the OBD 203 and XLM 201. Alternatively, because of the small distances between the components installed in the vehicle, short range wireless methods such as infrared, ultrasonic, Bluetooth, and other mediums which may link such components. Regardless of the manner of interconnection (wireless or hardwired), the MCM 202 is operative to transmit to the base station 104 an output signal 212 representative of the measured parameters provided by each component according to a rule set or logic contained within the MCM 202.
Alternatively, the logic may be entirely contained in the database 106 at the server 105 such that all processing is performed at the base station 104 and the appropriate signals transmitted back to the MCM 202. In the latter scheme, the MCM 202 and base station 104 must preferably be in continuous two-way wireless communication which, at the time of this writing, is typically not cost-effective for most fleet operators. Therefore, wireless communication between the MCM 202 and the base station 104 is based on a protocol of information criticality, cost and system availability.
For example, in emergency situations wherein the base station 104 receives a signal from the MCM 202 associated with critical data such as an emergency, signal transmission is by the most expedient and reliable means available with cost being a secondary or tertiary consideration. On the other hand, for non-critical data such as an indication of low tire pressure as provided to the MCM 202 by the OBD 203, notification is transmitted to the base station 104 by the least expensive means and during a latent transmission.
Wireless communication 213 between the MCM 202 and the base station 104 may be provided by a variety of systems including, but not limited to, WiFi, cellular network 108, satellite 109, Bluetooth, infrared, ultrasound, short wave, microwave or any other suitable method. Hardwired communication 214 may be effected at close range such as when the vehicle is within a service yard or at a base station wherein an ethernet connection may suffice.
The DCS 106 is an asset information network that is accessible through at least one server portal 215 and is configured to receive data from the MCM 202 during predetermined time intervals, on demand, during critical events, or randomly. The DCS 106 is also configured to generate reports such as graphic report (e.g., bar charts) of driver performance. The DCS 106 can also be configured to cause the MCM 202 to transmit warning signals to the vehicle during driver violations such as speeding, hard turns, hard brake, hard vertical, seatbelt violation and can also be configured to send a notification to the server 105 during predetermined events such as panic, man down, exception, accident, unauthorized vehicle movement to alert fleet management or safety personnel.
The vehicle monitoring system is configured to monitor driver speed using OBD 203 data such as speedometer, odometer, tachometer data or speed inferred from GPS data. Speeding violations may be determined by comparing vehicle speed (as provided by the OBD 203 or as inferred from GPS data) to a speed-by-street database such as a generic third-party data set similar to that commercially available from NAVTEQ of Chicago, Ill., and generating a driver violation when the vehicle speed exceeds the speed-by-street. The driver violation causes the MCM 202 to generate an audible/visual warning to the driver in order to change driver behavior over time. In this manner, the vehicle monitoring system provides for mentoring of driver behavior in order to improve safety and reduce fleet management costs.
Furthermore, the MCM 202 may be configured to determine vehicle speed such as during a turn where the vehicle is moving slower than the speed limit but the lateral acceleration levels as measured by the XLM 201 exceed the threshold values. Such a situation may occur when the driver is turning aggressively in a parking lot (i.e., hard turning). By integrating lateral acceleration over time, it is possible to determine instantaneous velocity of the vehicle at any point in the turn. Importantly, in one aspect of the invention, the generation of the warning signal to the driver starts a count-down timer wherein the vehicle monitoring system transmits an exception signal to the base station when the timer duration expires.
Alternatively, an exception signal may be generated when certain measured parameters exceed a threshold value by a large margin such as when the magnitude of the speeding violation exceeds a threshold of 100 mph. An exception signal may then be transmitted to the base station 104 such that appropriate fleet management personnel may be alerted. Such notification may be by any predetermined means and may include cell phone voice or text communication, paging, etc. In addition to the warning signal at the vehicle, the driver may likewise be contacted by cell phone, page or other radio communications regarding the exception event.
The MCM 202 may be in receipt of numerous other sensors that may provide indication of driver violations. For example, the vehicle monitoring system may include a seat sensor 216 in communication with the MCM 202 and which is operative to generate a signal when the vehicle is moving and seatbelts of vehicle occupants are unfastened. In this regard, the vehicle monitoring system may include any number of mechanical and electronic sensors 217 in data communication with the MCM and which are configured to monitor at least one of the following vehicle parameters: low battery, engine temperature, ignition on/off, headlight turn indicator usage, ABS operability, trailer electrical/mechanical malfunction, proximity forward (tailgating) and proximity rearward (objects behind) and proximity sideways (swerving and lane departures) 218. Furthermore, mechanical and electronic sensors 219 may be provided to monitor at least one of the following driver parameters: blink rate (a sleep sensor), heart rate, blood pressure and any other physiological parameters.
The vehicle monitoring system may be operative to track and generate on-demand reports of hours-of-service (HOS) (e.g., on-duty/off-duty driving times, consecutive driving days) in compliance with Federal Motor Carrier Safety Administration regulations. The vehicle monitoring system may additionally be operative to facilitate apportionment of mileage tax by tracking vehicle mileage within a given geographic region by noting state and national border crossings. In another aspect of the invention, it is contemplated that correction for mileage errors can be compensated for by re-synchronizing the MCM 202.
More specifically, because of the drift in OBD 203 mileage data due to odometer error as a result of tire wear or variations in tire pressure and/or due to inconsistencies in the GPS receiver data as a result of multi-path errors due to interference with trees and buildings or signal delay errors caused by atmospheric interference, the present invention may include a process for re-synchronizing the MCM 202 during vehicle refueling. In this manner, fuel tax may be accurately tracked in order to reduce fleet fuel costs.
The MCM 202 may automatically send certain types of signals to the base station 104. For example, the vehicle monitoring system may further include a manually/automatically-activatable timer that is configured to generate a man down signal 220 that is sent to the base station when the timer duration is exceeded. For example, in remote job site locations such as at an oil well location where it is necessary for the driver to perform certain hazardous tasks outside of the vehicle, the driver may first activate a one-hour (or other duration) timer such that failure to deactivate the timer results in a man down signal being transmitted to the base station 104 so that help may be sent to the vehicle location. A similar message may be sent to the base station 104 via a panic button 221 activated by a driver, occupant or any nearby person and may operate similar to that of a fire alarm or emergency 9-1-1 phone call wherein fleet management may send help to the vehicle location.
As was earlier mentioned, the MCM 202 may be configured to send to the base station 104 an exception signal representative of a violation of one of a plurality of parameters comprising at least one of exceeding a predetermined speed along a given route, failure to wear seatbelt, failure to activate headlights, tailgating, excessive idle time, excessive engine RPM, engine parameters, tire condition, vehicle load condition, vehicle location violation. The parameter settings (i.e., logic) of the MCM 202 may be remotely changed by commands transmitted from the base station 104 to the MCM 202. More specifically, the rule sets that comprise the hierarchy (i.e., criticality) by which signals are transmitted from the MCM 202 to the base station 104 may be revised. For example, a hierarchy of signal transmission may be revised from: panic, man down, crash event, exception, non-urgent communication to a hierarchy of crash event, man down, panic, exception, non-urgent communication.
In this same regard, the MCM 202 in one aspect of the invention is configured to allow for wireless or remote manipulation from the base station 104 of vehicle settings through the OBD or CAN 203 and may allow for revising certain vehicle settings such as engine governor setting and ignition timing. In a further aspect, the vehicle monitoring system allows for generating reports or alerts (e.g., text and/or map) of recently-occurring accident locations and dangerous road conditions such that a warning signal may be provided to the driver when the vehicle approaches the accident location or road condition. Additionally, the system can be configured to geo-fence certain areas of interest and to notify specified and/or targeted individuals when the vehicle and its driver approaches or departs a geo-fenced area. As was earlier mentioned, the database 106 is configured to collect driver performance data over time, generate a driver performance database comprising vehicle type and driver profile, and generate reports of predictive driver behavior based on historical driver performance data with the option of generating a graphical representation such as a bar chart of driver performance.
Additional modifications and improvements of the present invention may also be apparent to those of ordinary skill in the art. Thus, the particular combination of parts described and illustrated herein is intended to represent only one embodiment of the present invention and is not intended to serve as limitations of alternative devices within the spirit and scope of the present invention.
Global Asset Information Network (GAIN) 110 (
MCM 202 can determine when an exception condition occurs or when a threshold is exceeded that requires an alarm 302 to be generated in the vehicle. The alarm 302 may be an audible or visual warning for the vehicle occupants. Additionally, any of the data collected may be passed on to database 106 at server 105 where it may be further processed or accessed by fleet managers via GAIN system 110.
In embodiments of the invention, a comprehensive driver monitoring and mentoring system installed in a vehicle has one or more of the following components. An on-board diagnostic (OBD) system operative to monitor vehicle parameters and to generate an OBD input signal representative thereof. The vehicle monitoring system may be enclosed in a sealable housing that is permanently or temporarily mountable on the vehicle. A crash data recorder (CDR) is included with the vehicle monitoring system and is configured to measure and record vehicle acceleration, including the magnitude, direction and profile of such accelerations, during a crash event and to generate CDR signals. An accelerometer module (XLM) contains at least one accelerometer, such as a tri-axial accelerometer, and is mounted within the housing. The XLM is operative to monitor driver performance by measuring acceleration in at least one of a lateral, longitudinal and/or vertical direction over a predetermined time period. The XLM generates an XL signal when acceleration exceeds a predetermined threshold. In one embodiment, the CDR and XLM may be combined so that one set of accelerometers serves both functions.
A GPS receiver mounted is preferably within the housing and is configured to track the location and directional movement of the vehicle and to generate a GPS signal. The vehicle's user may access the driver mentoring and monitoring system using a mobile data terminal (MDT), which preferably has a mechanism for communicating warnings to the user, such as a speaker or light. A master command module (MCM) mounted within the housing is operative to receive inputs from the CDR, XLM, OBD, GPS receiver, and MDT. The MCM is operative to transmit signals representative of one or more vehicle operating parameters. The MCM is further configured to generate audible and/or visual warning signals to the driver when at least one of the vehicle's movement characteristics exceed a predetermined threshold value.
A base station server is in communication with the driver mentoring and monitoring system and the MCM. The server has a data collection system (DCS) that is accessible through at least one server portal and being configured to receive data from the MCM at predetermined or random times and generate reports of driver performance. The server may also cause the MCM to transmit a warning signal to the vehicle when driver violations or exceptions are detected, such as speeding, hard turn, hard brake, hard vertical, cellular phone use, or a seatbelt violation. The MCM may send a notification to the server during other predetermined events, such as a panic alarm, man down, accident, uncorrected driver violations, or unauthorized vehicle movement.
The vehicle monitoring system is adapted to monitor driver performance and may be in continuous communication with a base station. The vehicle monitoring system comprises one or more of the following components. A self-contained CDR mountable on the vehicle and configured to measure vehicle crash impulses and generate CDR input signals representative thereof. An XL module mountable on the vehicle and operatable to measure vehicle acceleration in at least one of lateral, longitudinal and/or vertical directions and to generate XL input signals representative thereof. A mobile data terminal (MDT) mountable on the vehicle and operative to continuously transmit CDR and XL input signals from the vehicle to a base station. A driver warning device mounted on the vehicle.
In one embodiment, the base station is operative to receive the CDR input signals and to generate a crash signal when the crash impulses exceeds an impulse threshold value stored at the base station. The base station is operative to emit an alert signal at the base station to alert personnel of the accident. The base station is also operative to receive the XL input signals and generate an exception signal when vehicle acceleration exceeds an acceleration threshold value stored at the base station and transmit a command to the MDT to activate the driver warning device. The base station may have a data collection system (DCS) configured to receive data from the MCM and to record driver performance and to generate warnings for at least one of the following violations: hours of service (HOS), speeding, hard turn, hard braking, hard acceleration, hard vertical movement, failure to use seatbelt, failure to use headlights, and failure to use turn signal.
In addition to or in place of the logic contained in the base station, logic may also be included in the MCM to monitor the vehicle and driver performance and to generate warnings. The vehicle monitoring system may be in at least intermittent, if not continuous, communication with a base station. The vehicle monitoring system may comprise one or more of the following components. A self-contained CDR mountable on the vehicle and being configured to measure vehicle crash impulses and generate a crash signal when the crash impulses exceeds an impulse threshold value stored at the CDR. Software or firmware providing a methodology for collecting data at regular or non-regular intervals. An XL module mountable on the vehicle and operative to measure vehicle acceleration in at least one of lateral, longitudinal and/or vertical directions and to generate an exception signal when vehicle acceleration exceeds an acceleration threshold value stored at the XL module. A mobile data terminal (MDT) operative to intermittently transmit the crash and exception signals from the vehicle to the base station. A driver warning device may be mounted on the vehicle. The base station is operative to receive the crash and/or exception signals and to alert personnel.
The vehicle monitoring system may correlate accident data from the CDR and XL Modules to potential injuries. The present invention provides a system and method of correlating personal injury and property damage with driver behavior measured prior to a vehicle crash and impulse forces measured during the vehicle crash. The CDR may measure crash impulses and the XL module may monitor driver behavior in terms of hard turns, hard braking and hard vertical movement of the vehicle. In one embodiment of the present invention, a crash database comprising personal injury and property damage characteristics is generated. For example, characteristics of the injured person's age, gender, height, weight, occupation, hobbies, income, prior claims, physical condition, injury type and severity may be collected. Vehicle model, condition, damage type and location, as well as impact characteristics, such as acceleration magnitude and direction during the crash, change in velocity between the time of impact and at least one millisecond following impact.
The vehicle monitoring system records crash impulse forces acting upon the vehicle during the crash. Driver behavior prior to the accident is also recorded by measuring acceleration in at least one of lateral, longitudinal and/or vertical directions in order to identify hard turns, hard braking and hard vertical forces experienced by the vehicle up to the time of the accident. The vehicle crash impulse data is correlated to an injury characteristic, such as by correlating accident forces to bodily injury claims, in order to determine the probability of the vehicle crash as a causal factor of the bodily injury. The database may further include at least one of the following data sets: probability of settlement in an insurance claim filed in relation to the vehicle crash, average cost of settlement, and settlement structure.
The present invention may also be used for mentoring driver behavior using data collected from the XL module. In one embodiment, driver behavior may be monitored and/or modified in a vehicle having an OBD and/or GPS receiver and an accelerometer module, which may be an XL module containing at least one accelerometer. Preferably, the accelerometer module will be a tri-axial accelerometer. The system measures vehicle acceleration in at least one of lateral, longitudinal and/or vertical direction and may determine vehicle speed from a vehicle speedometer (via an OBD) or by inferring speed from GPS readings. The measured acceleration is compared to a predetermined threshold, and the speed is compared to a speed-by-street dataset. A warning signal is sent to the driver when the measured acceleration exceeds the threshold and/or when the speed exceeds those contained in the speed-by-street dataset. A timer may be started when the warning signal is sent to allow the driver a predetermined amount of time to reduce the acceleration or speed. A notification signal may be sent to a base station if the driver fails to reduce acceleration or speed during the predetermined amount of time. The timer may be configurable for any amount of time, including zero or no delay.
In order to provide more accurate measurements of driver behavior, in one embodiment, the present invention filters gravity out of accelerometer readings as the vehicle changes its horizontal surface orientation. Driver performance can be monitored and mentored in a vehicle having an accelerometer module, which may be an XL module containing at least one accelerometer. Preferably, the accelerometer module will be a tri-axial accelerometer. Acceleration is measured in at least one of lateral, longitudinal and/or vertical directions over a predetermined time period, which may be a period of seconds or minutes. An XL acceleration input signal is generated when a measured acceleration exceeds a predetermined threshold. Gravitational effects are filtered out of the longitudinal, lateral and vertical acceleration measurements when the vehicle is on an incline.
The present invention may also record road hazards at server database. This allows for optimization of vehicle routing in a fleet of vehicles each having a GPS receiver and a driver-activated hazard notation mechanism. The notation mechanism is activated by the driver of each vehicle when the vehicle encounters adverse road conditions, road hazards, or unsafe speed limits, for example. The notation mechanism generates a time-stamped notation signal including GPS positional data of the hazard along the road. The notation signal is transmitted to a base station for recording in a database. The location of the road hazard is then transmitted to other vehicles in the fleet.
The logic and rule sets used by the vehicle monitoring system described herein may be modified or reconfigure in real-time at the vehicle. The present invention provides for real-time revising of the reporting of vehicle behavior in a fleet management system. A base station is in communication with a fleet of vehicles each having an MCM or processor for receiving inputs from vehicle-mounted systems, including, for example, OBD, GPS receiver, CDR, MDT, and an XL module. The MCM contains an original rule set or logic for processing inputs from the vehicle-mounted systems. Commands may be transmitted from the base station to the MCM. The commands may include a revised rule set regarding processing of the inputs, such as the rules for comparing inputs to thresholds, reporting, and the like, at the MCM. The logic in the MCM is revised in response to the revised rule set command received from the base station. Inputs at the MCM are then processed according to the revised rule set. For example, the revised rule set may include a reduced lateral acceleration threshold as measured by the XL module and by which the measured lateral acceleration is compared to determine the occurrence of a driver violation. The revised rule set may also change reporting of the driver violation to the base station.
The present invention may also provide fleet location displays to a user. The location of a fleet of vehicles may be visualized in real-time on a web-based portal. The portal is linked to a server that is in communication with the vehicles. The vehicles each have an MCM for receiving inputs from vehicle-mounted systems, including an OBD, GPS receiver, CDR, MDT, and XL module. A number of display options may be selected for displaying the location of the vehicles on a geographic area or map. The options include, for example, displaying an entire fleet of vehicles, an individual vehicle in the fleet, a group of vehicles in the fleet wherein the vehicles are grouped by a predetermined set of criteria, such as by type of vehicle or load, vehicles in the fleet reporting exceptions to the base station with a previous time period of predetermined duration, or vehicles within a specific geographic zone.
The present invention also provides for modification of reporting intervals by the vehicle monitoring system. The reporting of fleet vehicle behavior characteristics to a base station or server may be configured in different ways. The following options are examples of vehicle behavior reporting characteristics: at predetermined time intervals, at random time intervals, upon request from the base station, upon occurrence of an exception, upon the occurrence of an emergency or specific event, such as panic alarm, man down, or theft. The reporting may be provided at the vehicle and/or at the base station by means of one of the following: e-mail, cell phone voice and/or text message, or pager message. The reporting includes the following driver violations, if they have occurred, hours of service, speeding, hard turn, hard braking, hard vertical, or failure to use seatbelt.
In one embodiment, the vehicle monitoring system of the present invention is an easily installed, all-in-one unit. Referring to
Vehicle monitoring system 601 may be securely mounted on dashboard 602, such as by a mounting bracket or Velcro 604. Alternatively, monitoring system may be positioned on dashboard 602 without using any attachment device as long as it does not move during operation of the vehicle. Accordingly, system 601 can be moved to different locations within the vehicle, if desired, or may be easily moved between different vehicles. However, during operation of the vehicle, it is important that vehicle monitoring system 601 be secured to the vehicle so that system 601 can properly measure and evaluate the vehicle's operating parameters, such as accelerations and location.
Vehicle monitoring system 601 may have any type of user interface 605, such as a screen capable of displaying messages to the vehicle's driver or passengers, and a keyboard, buttons or switches that allow for user input. User interface 605 may have one or more status LEDs or other indicators to provide information regarding the status of the device's operation, power, communications, GPS lock, and the like. Additionally, the LEDs or other indicators may provide feedback to the driver when a driving violation occurs. The monitoring system may also provide for emergency communications, such as a one-touch help (emergency/911) button on the user interface 605. Additionally, monitoring system 601 may have a speaker and microphone 606 integral to the device.
Monitoring system 601 may be self-powered, such as by a battery, or powered by the vehicle's battery. Access to the vehicle's batter power may be by accessing the power available on the vehicle's OBD and/or CAN bus. Power line 607 may connect to OBD connector 608, which is linked to OBD 609. Alternatively, power line 607 may be spliced or connected directly into the OBD bus during the installation of vehicle monitoring system 601. The noise and quality of the power available from the OBD or CAN bus is typically much better than the power that is directly available from the battery or other places in the vehicle's electrical system. By connecting to OBD 609, monitoring system 601 is able to obtain a minimum level of “clean” and reliable power for operation. On the other hand, vehicle monitoring system 602 is designed to limit the power drain on the OBD bus to prevent damage or adverse impact to the vehicle's OBD system.
Vehicle mounting system 601 may be easily mounted on the windshield 602 in any typical vehicle and easily connected to the OBD/CAN power supply. This would allow for monitoring of almost any vehicle, such as a fleet vehicle or private car, and for monitoring and mentoring of any driver, such as a fleet driver, teen driver, or driver using a particular insurance company, with little or no impact on the vehicle or the driver.
Vehicle monitoring system 601 is preferably self-orienting, which allows it to be mounted in any position, angle or orientation in the vehicle or on dashboard 602. The self-orienting capability gives drivers, installers and fleet owners more flexibility in deciding how and where to mount vehicle monitoring system 601. When vehicle monitoring system 601 is first installed on dashboard 602 or in some other location in the vehicle, it may be oriented at any angle or rotation. For example, dashboard 602 may be sloped so that system 601 may be mounted with some degree of pitch relative to the earth's surface. Therefore, system 601 cannot assume that the bottom of the device is parallel to the ground or that gravity acts perpendicular to the device. Furthermore, system 601 may not be aligned with the direction of movement of the vehicle, but instead may be mounted in a position such that user interface 605 is rotated to face the driver. Accordingly, system 601 cannot default to a setting that assumes that the device 601 is aligned with or parallel to the centerline of the vehicle. An incorrect assumption as to the alignment and orientation of device 601 may result in erroneous measurements of the vehicle's acceleration, orientation, location and movement.
In embodiments of the present invention, vehicle monitoring system is self-orienting, which allows it to determine a direction of gravity and a direction of vehicle movement. Using these two directional vectors, the monitoring system can determine the actual orientation of the device with respect to the vehicle.
To compensate for the mounting position of monitoring unit 701, a self-orienting application is started after installation. The self-orientation determines the mounting position of unit 701 and calculates how to compensate for that unit's particular installation orientation. The accelerometers in unit 701 determine gravity vector Vg 706 by observing the forces on the accelerometers when the vehicle is stopped. The only force on the vehicle should be a 1 G pull from gravity. The monitoring system can measure and store the gravity vector Vg 706 as reference for the vertical positioning of unit 701. The monitoring system can then calculate an offset angle Θm 708 representing the angular difference between vertical axis Vm 704 and gravity vector Vg 706.
After the vehicle begins to move, monitoring system 701 can determine the orientation of the centerline CLV 705 of the vehicle by observing forces that occur while the vehicle is moving. When a vehicle begins to move or is breaking, the vehicle is usually traveling in a straight line along CLV 705. The braking forces may be more noticeable to unit 701 because drivers often brake harder than they accelerate. Accordingly, it is typical for breaking or vehicle deceleration to be a stronger force than a normal acceleration. By measuring the breaking, vehicle acceleration, or both types of force, the accelerometers in monitoring system 701 can determine the orientation of vehicle centerline CLV 705. The monitoring system can then calculate an offset angle ΘCL 707 representing the angular difference between centerline of the monitor CLm 703 and the centerline of the vehicle CLV 705.
Measurement of gravity vector Vg 706 could be accomplished almost instantaneously in a vehicle that is stopped. However, it may take varying amounts of time to determine vehicle CLV 705 because that is based upon how the vehicle is moving. If the vehicle brakes hard a number of times in a straight line after the self-aligning application begins, then vehicle CLV 705 can be determined quickly. It may take longer to identify vehicle CLV 705, if the vehicle does not experience accelerations or decelerations of sufficient magnitude. Once the offset angles ΘCL 707 and Θm 708 can then be used as a reference framework to convert observed acceleration measurements at monitoring unit 701 to the actual accelerations experienced by the vehicle. In most embodiments, the self-orienting application will only need to be run one time after installation; however, the self-orienting application may run continuously or periodically to update the orientation of unit 701, if necessary.
Monitor 802 may includes any of the vehicle monitoring systems described herein or other features. Monitor 802 may be a self-orienting device that uses gravity and movement of the vehicle to determine its orientation relative to the vehicle as described herein. Monitor 802 may also include GPS capability to determine the vehicle's location and may use changes in the vehicle's location over time to determine vehicle speed. Monitor 802 may also incorporate accelerometers to identify aggressive driving and/or collisions. Warning indicators and input buttons 804 may include a one-touch help or emergency/911 button and may include at least one status LED for operations, power, communications, GPS lock, and driving violation. Monitor 802 may also include a speaker and a microphone internally for communication between the driver and a remote location and/or for providing audible warnings to the driver. Monitor 802 may also include a screen for displaying text or iconic messages and warnings to the driver.
It will be understood that the present invention may be used for both fleets of vehicles and for individual drivers. For example, the vehicle monitoring system described herein may be used by insurance providers to monitor the driving behavior of customers and to use collected data to set insurance rates. A private vehicle owner may also use the present invention to monitor the use of the vehicle. For example, a parent may use the system described herein to monitor a new driver or a teenaged driver.
The present system provides for improved safety and asset monitoring and management. In one embodiment, the vehicle monitoring system may include as few features as a wireless communication module and a GPS module. The communication module may be a cellular phone, satellite communication system, WiFi communication device, or any other wireless communication system. The GPS module would provide location information for the vehicle. This system could be installed in a vehicle, such as on a windshield or dashboard, and would transmit vehicle information to a central location regarding vehicle use. The system could accept inputs from an on-board diagnostic system, such as vehicle speed, engine parameters, or the like. The system could also be powered by the on-board diagnostic system or by the vehicle's battery or using its own power source. A housing may comprise both the wireless communication module and the GPS module. The housing may also comprise antennas for the communication and GSP modules. When mounted on a windshield, the antennas would be optimally positioned so that they are exposed to open sky and not obstructed by the vehicle. The housing could also be mounted on the vehicle dashboard.
One embodiment of the present invention is directed to a system and method for evaluating or grading driver performance. For example, a new driver, a teen driver, or an experienced driver's driving performance may be monitored using a vehicle monitoring system such as those disclosed herein or any other type of monitor. The driver's performance is monitored and graded against established criteria, such as occurrence and severity of speeding, occurrence and severity of excessive acceleration or braking, seatbelt use, mobile phone or wireless device use, turn signal use, or any other vehicle operation parameters. The driver's performance may be graded on an easy to understand scale, such as an A, B, C, D, F scale, or a numerical or other scale. The driver's performance grade may be provided to a third party such as, for example, a parent who wants information on their teen driver or an insurance company that can use the grades to set insurance rates or prices. The driver may be evaluated at regular intervals, which would allow them to improve their performance and grade.
As noted above, any vehicle parameter may be selected for evaluation of the driver's operation of the vehicle. Speeding incidents may be selected as a grading criteria. Each time the driver speeds, it may be recorded for that evaluation period. The determination of what is “speeding” may vary depending upon the preset criteria. One or more speeding thresholds may be set for the vehicle, and a speeding violation will be recorded any time the vehicle exceeds these thresholds. For example, a seventy (70) mile-per-hour (MPH) threshold may be set for all streets and, if the vehicle exceeds this threshold, then a speeding incident is recorded. A higher threshold may also be set, such as a ninety (90) MPH threshold, that results in an additional violation record if that higher threshold is exceeded. These preset MPH speeding thresholds may apply to every street or to streets in a certain area. Alternatively, speeding criteria may be applied on a street-by-street basis in which the specific speed limit on each street is taken into account. For example, speeding violations may be detected as disclosed in U.S. patent application Ser. No. 11/805,238, filed May 22, 2007, now U.S. Pat. No. 7,859,392 issued Dec. 28, 2010 entitled System and Method for Monitoring and Updating Speed-By-Street Data, the disclosure of which is hereby incorporated by reference herein, which allows the vehicle monitoring system to identify speeding incidents based upon the specific speed limit that is set of a street instead of using a generic speeding threshold.
Vehicle acceleration or braking may also be used to evaluate driver performance. For example, thresholds may be set to identify when the vehicle's acceleration from a stop exceeds a particular limit to detect “jackrabbit starts” or other displays of speed or performance. Lateral acceleration thresholds may also be set to detect when the vehicle takes a turn at a speed that is too fast for the curvature of the road. Additionally, hard braking may be detected using the vehicle monitoring system. Repeated incidents of hard braking may indicate that the driver is following other vehicles too closely or not paying attention to traffic conditions. The accelerometers on the vehicle monitoring system may detect and measure hard turns, hard acceleration, hard braking, and/or hard vertical movement. Any or all of these hard moves may be selected as driver performance criteria and may be used to grade or evaluate a driver.
Other information can also be used to grade the driver's performance. For example, the vehicle monitoring system may detect whether the driver and/or passengers are using seatbelts. Seatbelt use may be detected via the OBD or CAN bus if the monitoring system is coupled to one of those buses. If a driver does not use his seatbelt with the car in drive, typically a warning icon or caution light is illuminated on the dashboard to warn the driver. The vehicle monitoring system may capture that data from the OBD or CAN bus and use it to identify improper driving behavior.
Additionally, the vehicle monitoring system can be configured with a sensor to detect mobile phone or wireless device use while the vehicle is operating. Such a sensor detects wireless signals originating from within the vehicle. Criteria may be set up to evaluate if the driver is using a cell phone while driving. Turn signal use can also be detected. By comparing the vehicle's route to a map in the GPS system, for example, the vehicle monitoring system may identify when the driver fails to use a turn signal. Depending upon the accuracy of the street mapping data, the turn signal use can be evaluated for turns at an intersection, entering or exiting a highway, or changing lanes. Other vehicle operation parameters can be monitored and used to evaluate driver performance. For example, if a teen driver revs the engine during a stop, as indicated by engine RPM parameters, it may indicate aggressive driving behavior. Additionally, excessive horn use may indicate aggressive driving.
Other criteria that are not specific to operation of the vehicle may be used to evaluate the driver's overall performance. The driver may be restricted to a certain route or area. For example, a teen driver may be restricted to an area in the driver's neighborhood or to a route between home, school and/or work. If the driver goes outside these boundaries, then their driving grade may be lowered based upon an improper use of the vehicle, without regard to whether the vehicle was operated properly during that time. The time of day of use may also be set so that a driver is only allowed to use the vehicle at certain times. If the driver uses the vehicle outside that allowed time of day, such as late at night, then their grade may be lowered.
The duration of a drive or use may also be a grading criteria. For example, a teen driver's use might be limited to certain trips, such as driving to school or work. If the length of these trips would not reasonable exceed a certain time, then a trip duration threshold could be set so that the driver's grade is lowered if he uses the vehicle for too long of a time. If trips to and from school or work should not exceed 30 minutes, a limit of 45 minutes or an hour could be set in the grading system. If the driver uses the vehicle for more than the threshold time limit, then the driver's evaluation would suffer. Similarly, a trip length may be set so that any single vehicle use beyond a preset length would result in a lower grade.
In one embodiment, the driver may begin with a perfect grade or score, such as a “100” or an “A,” and for each violation of the preset criteria or for some number of violations, the driver's score or grade is reduced. Each type of violation may be weighted so that different violations have different effects on the grade. For example, a single speeding or acceleration violation in a day may be weighted to have little affect on a grade. On the other hand, two or more violations within a short period of time, such as speeding multiple times during one drive or within a number of minutes, may be weighted to have more effect on the driver's grade. The performance criteria may be set for an individual driver or vehicle or may be generic criteria that apply to a class of drivers or all drivers.
Table 1 illustrates exemplary vehicle performance criteria that may be used to evaluate a driver during a grading period. Each time a violation occurs, it is recorded. A weight factor may be applied against each of the criteria, so that the importance of each criteria can be adjusted. At the end of the evaluation period, the weighted violations are totaled and the driver's grade is determined.
In one embodiment, the driver is provided with a score that follows an A, B, C, D, F or other well-known letter grading format, including, for example, “+” and “−” variations of letter grades (e.g. A+, A, . . . , D, D−, F). Such a grading system is easily understood by drivers and others who review the driving grades. For example, parents and teen drivers can easily understand a driving evaluation that follows their school's grading format. The weighting of each of the performance criteria may be adjusted so that the driving grades would follow a Gaussian distribution when averaged over a group of drivers, such as high-school-aged drivers. Numerical grades may be used in the alternative or together with alphabetical grades, if, for example, a student's school used such a grading scale. Such numerical scores may be used to calculate a driver's grade, and the numerical score then converted to an alphabetical grade before being presented to the driver. In other embodiments, the grading format may use words, such as “excellent,” “good,” “fair,” “poor,” or “unsatisfactory.”
The tracking and calculation of the driver's driving performance, violations, scores and grades may be performed by the vehicle monitoring system or by a central server. The vehicle monitoring system itself may evaluate each vehicle use and, at the end of the evaluation period, display the driver's grade or send an email, text message or other communication containing the driver's grade. Alternatively, the vehicle monitoring system may send individual violations or regular reports to a central server that combines the reports and evaluates the driver's performance. In this way, a driver and other parties, such as parents or an insurance company, may review and evaluate the driver's grades. A parent may, for example, use driving grades to determine whether a teen driver is allowed to continue using the family car. An insurance company, for example, may use a driver's grade to set insurance rates wherein good driving performance results in lower insurance rates.
If multiple drivers use the same vehicle, then the vehicle monitoring system must determine who is driving the vehicle during each use so that the performance grading is specific to one driver. This determination may be manually accomplished such as by having the driver may enter his or her identification into the vehicle monitoring system at the beginning of each use. Alternatively, the vehicle monitoring system may use some other method to determine who is driving, such as via a fingerprint reader or other biometric or electrical system.
In one embodiment, the driver's grade is calculated on a running basis and is displayed to the driver while the vehicle is in use. Alternatively, the driver may receive a grade for each use of the vehicle, but a final grade report might not be sent to third parties until the end of the evaluation period. The vehicle monitoring system may also alert the driver or third party when specific events occur or when a major violation (e.g. excessive speeding) occurs that has a significant impact on the driving grade.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.
This application is a continuation-in-part of U.S. patent application Ser. No. 11/805,237, filed on May 22, 2007 now U.S. Pat. No. 8,630,768, entitled “System and Method for Monitoring Vehicle Parameters and Driver Behavior,” which claims the benefit of U.S. Provisional Application No. 60/802,478, filed on May 22, 2006, entitled “Driver Behavior Monitoring System,” and which applications are hereby incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3975708 | Lusk | Aug 1976 | A |
| 4344136 | Panik | Aug 1982 | A |
| 4369427 | Drebinger et al. | Jan 1983 | A |
| 4395624 | Wartski | Jul 1983 | A |
| 4419654 | Funk | Dec 1983 | A |
| 4458535 | Juergens | Jul 1984 | A |
| 4591823 | Horvat | May 1986 | A |
| 4785280 | Fubini | Nov 1988 | A |
| 4843578 | Wade | Jun 1989 | A |
| 4926417 | Futami | May 1990 | A |
| 4939652 | Steiner | Jul 1990 | A |
| 5006829 | Miyamoto et al. | Apr 1991 | A |
| 5032821 | Domanico | Jul 1991 | A |
| 5064151 | Cerimele et al. | Nov 1991 | A |
| 5074144 | Krofchalk et al. | Dec 1991 | A |
| 5119504 | Durboraw, III | Jun 1992 | A |
| 5223844 | Mansell et al. | Jun 1993 | A |
| 5225842 | Brown et al. | Jul 1993 | A |
| 5303163 | Ebaugh et al. | Apr 1994 | A |
| 5305214 | Komatsu | Apr 1994 | A |
| 5309139 | Austin | May 1994 | A |
| 5311197 | Sorden et al. | May 1994 | A |
| 5325082 | Rodriguez | Jun 1994 | A |
| 5347260 | Ginzel | Sep 1994 | A |
| 5353023 | Mitsugi | Oct 1994 | A |
| 5359528 | Haendel | Oct 1994 | A |
| 5365114 | Tsurushima | Nov 1994 | A |
| 5365451 | Wang et al. | Nov 1994 | A |
| 5381155 | Gerber | Jan 1995 | A |
| 5394136 | Lammers | Feb 1995 | A |
| 5400018 | Scholl | Mar 1995 | A |
| 5414432 | Penny, Jr. et al. | May 1995 | A |
| 5422624 | Smith | Jun 1995 | A |
| 5424584 | Matsuda | Jun 1995 | A |
| 5430432 | Camhi | Jul 1995 | A |
| 5436612 | Aduddell | Jul 1995 | A |
| 5436837 | Gerstung et al. | Jul 1995 | A |
| 5446659 | Yamawaki | Aug 1995 | A |
| 5453939 | Hoffman | Sep 1995 | A |
| 5457439 | Kuhn | Oct 1995 | A |
| 5475597 | Buck | Dec 1995 | A |
| 5485116 | Cserveny et al. | Jan 1996 | A |
| 5485161 | Vaughn | Jan 1996 | A |
| 5499182 | Ousborne | Mar 1996 | A |
| 5521579 | Bernhard | May 1996 | A |
| 5521580 | Kaneko | May 1996 | A |
| 5525960 | McCall | Jun 1996 | A |
| 5546305 | Kondo | Aug 1996 | A |
| 5548273 | Nicol | Aug 1996 | A |
| 5570087 | Lemelson | Oct 1996 | A |
| 5581464 | Woll | Dec 1996 | A |
| 5586130 | Doyle | Dec 1996 | A |
| 5600558 | Mearek | Feb 1997 | A |
| 5612875 | Haendel | Mar 1997 | A |
| 5625337 | Medawar | Apr 1997 | A |
| 5638077 | Martin | Jun 1997 | A |
| 5642284 | Parupalli | Jun 1997 | A |
| 5648755 | Yagihashi | Jul 1997 | A |
| 5659289 | Zonkoski | Aug 1997 | A |
| 5689067 | Klein | Nov 1997 | A |
| 5708417 | Tallman | Jan 1998 | A |
| 5717374 | Smith | Feb 1998 | A |
| 5719771 | Buck | Feb 1998 | A |
| 5723768 | Ammon | Mar 1998 | A |
| 5731285 | Pavone et al. | Mar 1998 | A |
| 5731785 | Lemelson et al. | Mar 1998 | A |
| 5740548 | Hudgens | Apr 1998 | A |
| 5742915 | Stafford | Apr 1998 | A |
| 5751245 | Janky et al. | May 1998 | A |
| 5764139 | Nojima | Jun 1998 | A |
| 5767767 | Lima | Jun 1998 | A |
| 5777580 | Janky et al. | Jul 1998 | A |
| 5795997 | Gittins | Aug 1998 | A |
| 5797134 | McMillan et al. | Aug 1998 | A |
| 5801618 | Jenkins | Sep 1998 | A |
| 5801948 | Wood | Sep 1998 | A |
| 5815071 | Doyle | Sep 1998 | A |
| 5819090 | Wolf et al. | Oct 1998 | A |
| 5819198 | Peretz | Oct 1998 | A |
| 5825283 | Camhi | Oct 1998 | A |
| 5825284 | Dunwoody | Oct 1998 | A |
| 5829782 | Breed et al. | Nov 1998 | A |
| 5844475 | Horie | Dec 1998 | A |
| 5847271 | Poublon | Dec 1998 | A |
| 5862500 | Goodwin | Jan 1999 | A |
| 5867093 | Dodd | Feb 1999 | A |
| 5877678 | Donoho | Mar 1999 | A |
| 5880674 | Ufkes | Mar 1999 | A |
| 5880958 | Helms et al. | Mar 1999 | A |
| 5883594 | Lau | Mar 1999 | A |
| 5892434 | Carlson | Apr 1999 | A |
| 5907277 | Tokunaga | May 1999 | A |
| 5914654 | Smith | Jun 1999 | A |
| 5918180 | Dimino | Jun 1999 | A |
| 5926087 | Busch | Jul 1999 | A |
| 5928291 | Jenkins et al. | Jul 1999 | A |
| 5933080 | Nojima | Aug 1999 | A |
| 5941915 | Federle et al. | Aug 1999 | A |
| 5945919 | Trask | Aug 1999 | A |
| 5949330 | Hoffman | Sep 1999 | A |
| 5949331 | Schofield | Sep 1999 | A |
| 5952941 | Mardirossian | Sep 1999 | A |
| 5954781 | Slepian | Sep 1999 | A |
| 5955942 | Slifkin | Sep 1999 | A |
| 5957986 | Coverdill | Sep 1999 | A |
| 5964816 | Kincaid | Oct 1999 | A |
| 5969600 | Tanguay | Oct 1999 | A |
| 5974356 | Doyle et al. | Oct 1999 | A |
| 5978737 | Pawlowski | Nov 1999 | A |
| 5982278 | Cuvelier | Nov 1999 | A |
| 5987976 | Sarangapani | Nov 1999 | A |
| 5999125 | Kurby | Dec 1999 | A |
| 6002327 | Boesch | Dec 1999 | A |
| 6008724 | Thompson | Dec 1999 | A |
| 6018293 | Smith | Jan 2000 | A |
| 6026292 | Coppinger et al. | Feb 2000 | A |
| 6028508 | Mason | Feb 2000 | A |
| 6028510 | Tamam | Feb 2000 | A |
| 6037861 | Ying | Mar 2000 | A |
| 6037862 | Ying | Mar 2000 | A |
| 6038496 | Dobler | Mar 2000 | A |
| 6044315 | Honeck | Mar 2000 | A |
| 6059066 | Lary | May 2000 | A |
| 6060989 | Gehlot | May 2000 | A |
| 6064886 | Perez et al. | May 2000 | A |
| 6064928 | Wilson | May 2000 | A |
| 6064970 | McMillan et al. | May 2000 | A |
| 6067008 | Smith | May 2000 | A |
| 6067009 | Hozuka | May 2000 | A |
| 6072388 | Kyrtsos | Jun 2000 | A |
| 6073007 | Doyle | Jun 2000 | A |
| 6075458 | Ladner et al. | Jun 2000 | A |
| 6078853 | Ebner | Jun 2000 | A |
| 6081188 | Kutlucinar | Jun 2000 | A |
| 6084870 | Wooten et al. | Jul 2000 | A |
| 6094149 | Wilson | Jul 2000 | A |
| 6098048 | Dashefsky | Aug 2000 | A |
| 6100792 | Ogino | Aug 2000 | A |
| 6104282 | Fragoso | Aug 2000 | A |
| 6108591 | Segal et al. | Aug 2000 | A |
| 6112145 | Zachman | Aug 2000 | A |
| 6121922 | Mohan | Sep 2000 | A |
| 6122591 | Pomerantz | Sep 2000 | A |
| 6124810 | Segal et al. | Sep 2000 | A |
| 6130608 | McKeown | Oct 2000 | A |
| 6131067 | Girerd et al. | Oct 2000 | A |
| 6133827 | Alvey | Oct 2000 | A |
| 6138516 | Tillman | Oct 2000 | A |
| 6141610 | Rothert | Oct 2000 | A |
| 6147598 | Murphy | Nov 2000 | A |
| 6172602 | Hasfjord | Jan 2001 | B1 |
| 6178374 | Mohlenkamp et al. | Jan 2001 | B1 |
| 6184784 | Shibuya | Feb 2001 | B1 |
| 6185501 | Smith | Feb 2001 | B1 |
| 6195015 | Jacobs et al. | Feb 2001 | B1 |
| 6198995 | Settles | Mar 2001 | B1 |
| 6204756 | Senyk | Mar 2001 | B1 |
| 6204757 | Evans | Mar 2001 | B1 |
| 6208240 | Ledesma | Mar 2001 | B1 |
| 6212455 | Weaver | Apr 2001 | B1 |
| 6216066 | Goebel | Apr 2001 | B1 |
| 6222458 | Harris | Apr 2001 | B1 |
| 6225898 | Kamiya | May 2001 | B1 |
| 6227862 | Harkness | May 2001 | B1 |
| 6229438 | Kutlucinar | May 2001 | B1 |
| 6232873 | Dilz | May 2001 | B1 |
| 6246933 | Bague | Jun 2001 | B1 |
| 6246948 | Thakker | Jun 2001 | B1 |
| 6247360 | Anderson | Jun 2001 | B1 |
| 6249219 | Perez | Jun 2001 | B1 |
| 6253129 | Jenkins et al. | Jun 2001 | B1 |
| 6253151 | Ohler et al. | Jun 2001 | B1 |
| 6255892 | Gartner et al. | Jul 2001 | B1 |
| 6255939 | Roth et al. | Jul 2001 | B1 |
| 6262657 | Okuda et al. | Jul 2001 | B1 |
| 6262658 | O'Connor | Jul 2001 | B1 |
| 6265989 | Taylor | Jul 2001 | B1 |
| 6266588 | McClellan | Jul 2001 | B1 |
| 6278361 | Magiawala | Aug 2001 | B1 |
| 6282491 | Bochmann et al. | Aug 2001 | B1 |
| 6285931 | Hattori | Sep 2001 | B1 |
| 6289332 | Menig | Sep 2001 | B2 |
| 6294988 | Shomura | Sep 2001 | B1 |
| 6294989 | Schofield | Sep 2001 | B1 |
| 6295492 | Lang | Sep 2001 | B1 |
| 6297768 | Allen, Jr. | Oct 2001 | B1 |
| 6301533 | Markow | Oct 2001 | B1 |
| 6306063 | Horgan et al. | Oct 2001 | B1 |
| 6308120 | Good | Oct 2001 | B1 |
| 6308134 | Croyle et al. | Oct 2001 | B1 |
| 6313742 | Larson | Nov 2001 | B1 |
| 6314367 | Ohler et al. | Nov 2001 | B1 |
| 6320497 | Fukumoto | Nov 2001 | B1 |
| 6331825 | Ladner et al. | Dec 2001 | B1 |
| 6333686 | Waltzer | Dec 2001 | B1 |
| 6337653 | Buchler | Jan 2002 | B1 |
| 6339739 | Folke | Jan 2002 | B1 |
| 6339745 | Novik | Jan 2002 | B1 |
| 6344805 | Yasui | Feb 2002 | B1 |
| 6351211 | Bussard | Feb 2002 | B1 |
| 6351709 | King et al. | Feb 2002 | B2 |
| 6356188 | Meyers | Mar 2002 | B1 |
| 6356822 | Diaz | Mar 2002 | B1 |
| 6356833 | Jeon | Mar 2002 | B2 |
| 6356836 | Adolph | Mar 2002 | B1 |
| 6359554 | Skibinski | Mar 2002 | B1 |
| 6362730 | Razavi | Mar 2002 | B2 |
| 6362734 | McQuade | Mar 2002 | B1 |
| 6366199 | Osborn | Apr 2002 | B1 |
| 6366207 | Murphy | Apr 2002 | B1 |
| 6378959 | Lesesky | Apr 2002 | B2 |
| 6389340 | Rayner | May 2002 | B1 |
| 6393348 | Ziegler | May 2002 | B1 |
| 6401029 | Kubota et al. | Jun 2002 | B1 |
| 6404329 | Hsu | Jun 2002 | B1 |
| 6405112 | Rayner | Jun 2002 | B1 |
| 6405128 | Bechtolsheim et al. | Jun 2002 | B1 |
| 6415226 | Kozak | Jul 2002 | B1 |
| 6417764 | Tonkin | Jul 2002 | B2 |
| 6424268 | Isonaga | Jul 2002 | B1 |
| 6427687 | Kirk | Aug 2002 | B1 |
| 6430488 | Goldman | Aug 2002 | B1 |
| 6433681 | Foo | Aug 2002 | B1 |
| 6438472 | Tano et al. | Aug 2002 | B1 |
| 6441732 | Laitsaari | Aug 2002 | B1 |
| 6449540 | Rayner | Sep 2002 | B1 |
| 6459365 | Tamura | Oct 2002 | B2 |
| 6459367 | Green | Oct 2002 | B1 |
| 6459369 | Wang | Oct 2002 | B1 |
| 6459961 | Obradovich | Oct 2002 | B1 |
| 6459969 | Bates | Oct 2002 | B1 |
| 6462675 | Humphrey | Oct 2002 | B1 |
| 6472979 | Schofield | Oct 2002 | B2 |
| 6476763 | Allen, Jr. | Nov 2002 | B2 |
| 6480106 | Crombez | Nov 2002 | B1 |
| 6484035 | Allen, Jr. | Nov 2002 | B2 |
| 6484091 | Shibata | Nov 2002 | B2 |
| 6493650 | Rodgers | Dec 2002 | B1 |
| 6512969 | Wang | Jan 2003 | B1 |
| 6515596 | Awada | Feb 2003 | B2 |
| 6519512 | Haas | Feb 2003 | B1 |
| 6523912 | Bond, III et al. | Feb 2003 | B1 |
| 6525672 | Chainer | Feb 2003 | B2 |
| 6526341 | Bird et al. | Feb 2003 | B1 |
| 6529159 | Fan et al. | Mar 2003 | B1 |
| 6535116 | Zhou | Mar 2003 | B1 |
| 6542074 | Tharman | Apr 2003 | B1 |
| 6542794 | Obradovich | Apr 2003 | B2 |
| 6549834 | McClellan et al. | Apr 2003 | B2 |
| 6552682 | Fan | Apr 2003 | B1 |
| 6556905 | Mittelsteadt | Apr 2003 | B1 |
| 6559769 | Anthony | May 2003 | B2 |
| 6564126 | Lin | May 2003 | B1 |
| 6567000 | Slifkin | May 2003 | B2 |
| 6571168 | Murphy | May 2003 | B1 |
| 6577946 | Myr | Jun 2003 | B2 |
| 6587759 | Obradovich | Jul 2003 | B2 |
| 6594579 | Lowrey | Jul 2003 | B1 |
| 6599243 | Woltermann | Jul 2003 | B2 |
| 6600985 | Weaver | Jul 2003 | B2 |
| 6604033 | Banet | Aug 2003 | B1 |
| 6609063 | Bender et al. | Aug 2003 | B1 |
| 6609064 | Dean | Aug 2003 | B1 |
| 6611740 | Lowrey | Aug 2003 | B2 |
| 6611755 | Coffee | Aug 2003 | B1 |
| 6615137 | Lutter et al. | Sep 2003 | B2 |
| 6622085 | Amita et al. | Sep 2003 | B1 |
| 6629029 | Giles | Sep 2003 | B1 |
| 6630884 | Shanmugham | Oct 2003 | B1 |
| 6631322 | Arthur et al. | Oct 2003 | B1 |
| 6633811 | Aumayer | Oct 2003 | B1 |
| 6636790 | Lightner | Oct 2003 | B1 |
| 6639512 | Lee | Oct 2003 | B1 |
| 6643578 | Levine | Nov 2003 | B2 |
| 6651001 | Apsell | Nov 2003 | B2 |
| 6654682 | Kane et al. | Nov 2003 | B2 |
| 6657540 | Knapp | Dec 2003 | B2 |
| 6662013 | Takiguchi et al. | Dec 2003 | B2 |
| 6662141 | Kaub | Dec 2003 | B2 |
| 6664922 | Fan | Dec 2003 | B1 |
| 6665613 | Duvall | Dec 2003 | B2 |
| 6674362 | Yoshioka | Jan 2004 | B2 |
| 6675085 | Straub | Jan 2004 | B2 |
| 6677854 | Dix | Jan 2004 | B2 |
| 6678612 | Khawam | Jan 2004 | B1 |
| 6696932 | Skibinski | Feb 2004 | B2 |
| 6701234 | Vogelsang | Mar 2004 | B1 |
| 6703925 | Steffel | Mar 2004 | B2 |
| 6710738 | Allen, Jr. | Mar 2004 | B2 |
| 6714894 | Tobey et al. | Mar 2004 | B1 |
| 6718235 | Borugian | Apr 2004 | B1 |
| 6718239 | Rayner | Apr 2004 | B2 |
| 6718258 | Barton | Apr 2004 | B1 |
| 6720889 | Yamaki et al. | Apr 2004 | B2 |
| 6727809 | Smith | Apr 2004 | B1 |
| 6728542 | Meda | Apr 2004 | B2 |
| 6728605 | Lash | Apr 2004 | B2 |
| 6732031 | Lowrey | May 2004 | B1 |
| 6732032 | Lowrey | May 2004 | B1 |
| 6737962 | Mayor | May 2004 | B2 |
| 6741169 | Magiawala | May 2004 | B2 |
| 6741170 | Alrabady | May 2004 | B2 |
| 6745153 | White | Jun 2004 | B2 |
| 6748322 | Fernandez | Jun 2004 | B1 |
| 6750761 | Newman | Jun 2004 | B1 |
| 6750762 | Porter | Jun 2004 | B1 |
| 6756916 | Yanai | Jun 2004 | B2 |
| 6759952 | Dunbridge | Jul 2004 | B2 |
| 6766244 | Obata et al. | Jul 2004 | B2 |
| 6768448 | Farmer | Jul 2004 | B2 |
| 6775602 | Gordon | Aug 2004 | B2 |
| 6778068 | Wolfe | Aug 2004 | B2 |
| 6778885 | Agashe et al. | Aug 2004 | B2 |
| 6784793 | Gagnon | Aug 2004 | B2 |
| 6784832 | Knockeart et al. | Aug 2004 | B2 |
| 6788196 | Ueda | Sep 2004 | B2 |
| 6788207 | Wilkerson | Sep 2004 | B2 |
| 6792339 | Basson | Sep 2004 | B2 |
| 6795017 | Puranik et al. | Sep 2004 | B1 |
| 6798354 | Schuessler | Sep 2004 | B2 |
| 6803854 | Adams et al. | Oct 2004 | B1 |
| 6807481 | Gastelum | Oct 2004 | B1 |
| 6813549 | Good | Nov 2004 | B2 |
| 6819236 | Kawai | Nov 2004 | B2 |
| 6822557 | Weber | Nov 2004 | B1 |
| 6832141 | Skeen et al. | Dec 2004 | B2 |
| 6845314 | Fosseen | Jan 2005 | B2 |
| 6845316 | Yates | Jan 2005 | B2 |
| 6845317 | Craine | Jan 2005 | B2 |
| 6847871 | Malik et al. | Jan 2005 | B2 |
| 6847872 | Bodin | Jan 2005 | B2 |
| 6847873 | Li | Jan 2005 | B1 |
| 6847887 | Casino | Jan 2005 | B1 |
| 6850841 | Casino | Feb 2005 | B1 |
| 6859039 | Horie | Feb 2005 | B2 |
| 6859695 | Klausner | Feb 2005 | B2 |
| 6865457 | Mittelsteadt | Mar 2005 | B1 |
| 6867733 | Sandhu et al. | Mar 2005 | B2 |
| 6868386 | Henderson et al. | Mar 2005 | B1 |
| 6870469 | Ueda | Mar 2005 | B2 |
| 6873253 | Veziris | Mar 2005 | B2 |
| 6873261 | Anthony | Mar 2005 | B2 |
| 6873998 | Dorum et al. | Mar 2005 | B1 |
| 6877007 | Hentzel et al. | Apr 2005 | B1 |
| 6879894 | Lightner | Apr 2005 | B1 |
| 6885293 | Okumura | Apr 2005 | B2 |
| 6888495 | Flick | May 2005 | B2 |
| 6892131 | Coffee | May 2005 | B2 |
| 6894606 | Forbes et al. | May 2005 | B2 |
| 6895332 | King | May 2005 | B2 |
| 6909398 | Knockeart et al. | Jun 2005 | B2 |
| 6909947 | Douros et al. | Jun 2005 | B2 |
| 6914523 | Munch | Jul 2005 | B2 |
| 6922133 | Wolfe | Jul 2005 | B2 |
| 6922616 | Obradovich | Jul 2005 | B2 |
| 6922622 | Dulin | Jul 2005 | B2 |
| 6925425 | Remboski | Aug 2005 | B2 |
| 6928348 | Lightner | Aug 2005 | B1 |
| 6931309 | Phelan et al. | Aug 2005 | B2 |
| 6937162 | Tokitsu | Aug 2005 | B2 |
| 6950013 | Scaman | Sep 2005 | B2 |
| 6954140 | Holler | Oct 2005 | B2 |
| 6957133 | Hunt et al. | Oct 2005 | B1 |
| 6958976 | Kikkawa | Oct 2005 | B2 |
| 6960168 | Yanagidaira et al. | Nov 2005 | B2 |
| 6965827 | Wolfson | Nov 2005 | B1 |
| 6968311 | Knockeart et al. | Nov 2005 | B2 |
| 6970075 | Cherouny | Nov 2005 | B2 |
| 6970783 | Knockeart et al. | Nov 2005 | B2 |
| 6972669 | Saito | Dec 2005 | B2 |
| 6980131 | Taylor | Dec 2005 | B1 |
| 6981565 | Gleacher | Jan 2006 | B2 |
| 6982636 | Bennie | Jan 2006 | B1 |
| 6983200 | Bodin | Jan 2006 | B2 |
| 6988033 | Lowrey | Jan 2006 | B1 |
| 6988034 | Marlatt et al. | Jan 2006 | B1 |
| 6989739 | Li | Jan 2006 | B2 |
| 7002454 | Gustafson | Feb 2006 | B1 |
| 7002579 | Olson | Feb 2006 | B2 |
| 7005975 | Lehner | Feb 2006 | B2 |
| 7006820 | Parker et al. | Feb 2006 | B1 |
| 7019641 | Lakshmanan | Mar 2006 | B1 |
| 7023321 | Brillon et al. | Apr 2006 | B2 |
| 7023332 | Saito | Apr 2006 | B2 |
| 7024318 | Fischer | Apr 2006 | B2 |
| 7027808 | Wesby | Apr 2006 | B2 |
| 7034705 | Yoshioka | Apr 2006 | B2 |
| 7038578 | Will | May 2006 | B2 |
| 7042347 | Cherouny | May 2006 | B2 |
| 7047114 | Rogers | May 2006 | B1 |
| 7049941 | Rivera-Cintron | May 2006 | B2 |
| 7054742 | Khavakh et al. | May 2006 | B2 |
| 7059689 | Lesesky | Jun 2006 | B2 |
| 7069126 | Bernard | Jun 2006 | B2 |
| 7069134 | Williams | Jun 2006 | B2 |
| 7072753 | Eberle | Jul 2006 | B2 |
| 7081811 | Johnston | Jul 2006 | B2 |
| 7084755 | Nord | Aug 2006 | B1 |
| 7088225 | Yoshioka | Aug 2006 | B2 |
| 7089116 | Smith | Aug 2006 | B2 |
| 7091880 | Sorensen | Aug 2006 | B2 |
| 7098812 | Hirota | Aug 2006 | B2 |
| 7099750 | Miyazawa | Aug 2006 | B2 |
| 7099774 | King | Aug 2006 | B2 |
| 7102496 | Ernst, Jr. | Sep 2006 | B1 |
| 7109850 | Kawazoe et al. | Sep 2006 | B2 |
| 7109853 | Mattson | Sep 2006 | B1 |
| 7113081 | Reichow | Sep 2006 | B1 |
| 7113107 | Taylor | Sep 2006 | B2 |
| 7113127 | Banet et al. | Sep 2006 | B1 |
| 7117075 | Larschan et al. | Oct 2006 | B1 |
| 7119696 | Borugian | Oct 2006 | B2 |
| 7124027 | Ernst, Jr. | Oct 2006 | B1 |
| 7124088 | Bauer et al. | Oct 2006 | B2 |
| 7129825 | Weber | Oct 2006 | B2 |
| 7132934 | Allison | Nov 2006 | B2 |
| 7132937 | Lu | Nov 2006 | B2 |
| 7132938 | Suzuki | Nov 2006 | B2 |
| 7133755 | Salman | Nov 2006 | B2 |
| 7135983 | Filippov | Nov 2006 | B2 |
| 7138916 | Schwartz | Nov 2006 | B2 |
| 7139661 | Holze | Nov 2006 | B2 |
| 7142196 | Connor et al. | Nov 2006 | B1 |
| 7145442 | Wai | Dec 2006 | B1 |
| 7149206 | Pruzan | Dec 2006 | B2 |
| 7155259 | Bauchot et al. | Dec 2006 | B2 |
| 7155321 | Bromley et al. | Dec 2006 | B2 |
| 7161473 | Hoshal | Jan 2007 | B2 |
| 7164986 | Humphries | Jan 2007 | B2 |
| 7170390 | Quiñones | Jan 2007 | B2 |
| 7170400 | Cowelchuk | Jan 2007 | B2 |
| 7174243 | Lightner | Feb 2007 | B1 |
| 7180407 | Guo | Feb 2007 | B1 |
| 7180409 | Brey | Feb 2007 | B2 |
| 7183942 | Rock et al. | Feb 2007 | B2 |
| 7187271 | Nagata | Mar 2007 | B2 |
| 7188025 | Hudson, Jr. | Mar 2007 | B2 |
| 7196629 | Ruoss | Mar 2007 | B2 |
| 7197500 | Israni et al. | Mar 2007 | B1 |
| 7216022 | Kynast et al. | May 2007 | B2 |
| 7216035 | Hörtner | May 2007 | B2 |
| 7218211 | Ho | May 2007 | B2 |
| 7222009 | Hijikata | May 2007 | B2 |
| 7225060 | O'Connor et al. | May 2007 | B2 |
| 7225065 | Hunt | May 2007 | B1 |
| 7228211 | Lowrey | Jun 2007 | B1 |
| 7233235 | Pavlish | Jun 2007 | B2 |
| 7236862 | Kanno | Jun 2007 | B2 |
| 7239948 | Nimmo | Jul 2007 | B2 |
| 7256686 | Koutsky | Aug 2007 | B2 |
| 7256700 | Ruocco | Aug 2007 | B1 |
| 7256702 | Isaacs | Aug 2007 | B2 |
| 7260497 | Watabe | Aug 2007 | B2 |
| RE39845 | Hasfjord | Sep 2007 | E |
| 7269507 | Cayford | Sep 2007 | B2 |
| 7269530 | Lin | Sep 2007 | B1 |
| 7271716 | Nou | Sep 2007 | B2 |
| 7273172 | Olsen, III | Sep 2007 | B2 |
| 7280046 | Berg | Oct 2007 | B2 |
| 7283904 | Benjamin | Oct 2007 | B2 |
| 7286917 | Hawkins | Oct 2007 | B2 |
| 7286929 | Staton | Oct 2007 | B2 |
| 7289024 | Sumcad | Oct 2007 | B2 |
| 7289035 | Nathan | Oct 2007 | B2 |
| 7292152 | Torkkola | Nov 2007 | B2 |
| 7292159 | Culpepper | Nov 2007 | B2 |
| 7298248 | Finley | Nov 2007 | B2 |
| 7298249 | Avery, Jr. | Nov 2007 | B2 |
| 7301445 | Moughler | Nov 2007 | B2 |
| 7317383 | Ihara | Jan 2008 | B2 |
| 7317392 | DuRocher | Jan 2008 | B2 |
| 7317927 | Staton | Jan 2008 | B2 |
| 7319848 | Obradovich | Jan 2008 | B2 |
| 7321294 | Mizumaki | Jan 2008 | B2 |
| 7321825 | Ranalli | Jan 2008 | B2 |
| 7323972 | Nobusawa | Jan 2008 | B2 |
| 7323974 | Schmid | Jan 2008 | B2 |
| 7323982 | Staton | Jan 2008 | B2 |
| 7327239 | Gallant | Feb 2008 | B2 |
| 7327258 | Fast | Feb 2008 | B2 |
| 7333883 | Geborek | Feb 2008 | B2 |
| 7339460 | Lane | Mar 2008 | B2 |
| 7349782 | Churchill | Mar 2008 | B2 |
| 7352081 | Taurasi | Apr 2008 | B2 |
| 7355508 | Mian | Apr 2008 | B2 |
| 7365639 | Yuhara | Apr 2008 | B2 |
| 7366551 | Hartley | Apr 2008 | B1 |
| 7375624 | Hines | May 2008 | B2 |
| 7376499 | Salman | May 2008 | B2 |
| 7378946 | Lahr | May 2008 | B2 |
| 7378949 | Chen | May 2008 | B2 |
| 7386394 | Shulman | Jun 2008 | B2 |
| 7397363 | Joao | Jul 2008 | B2 |
| 7421334 | Dahlgren et al. | Sep 2008 | B2 |
| 7433889 | Barton | Oct 2008 | B1 |
| 7447509 | Cossins et al. | Nov 2008 | B2 |
| 7474264 | Bolduc et al. | Jan 2009 | B2 |
| 7474269 | Mayer et al. | Jan 2009 | B2 |
| 7495547 | Lich et al. | Feb 2009 | B2 |
| 7499949 | Barton | Mar 2009 | B2 |
| 7565230 | Gardner et al. | Jul 2009 | B2 |
| 7584033 | Mittelsteadt et al. | Sep 2009 | B2 |
| 7646312 | Rosen | Jan 2010 | B2 |
| 7660658 | Sheynblat | Feb 2010 | B2 |
| 7671727 | Flick | Mar 2010 | B2 |
| 7671752 | Sofer | Mar 2010 | B2 |
| 7697917 | Camp et al. | Apr 2010 | B2 |
| 7739036 | Grimm et al. | Jun 2010 | B2 |
| 7747410 | Van Esch | Jun 2010 | B2 |
| 7859392 | McClellan et al. | Dec 2010 | B2 |
| 7880642 | Gueziec | Feb 2011 | B2 |
| 7898388 | Ehrman et al. | Mar 2011 | B2 |
| 7941258 | Mittelsteadt et al. | May 2011 | B1 |
| 8044809 | Farmer | Oct 2011 | B2 |
| 8090598 | Bauer et al. | Jan 2012 | B2 |
| 8131205 | Rosen | Mar 2012 | B2 |
| 8188887 | Catten et al. | May 2012 | B2 |
| 8233880 | Johnson | Jul 2012 | B2 |
| 8314708 | Gunderson et al. | Nov 2012 | B2 |
| 8384555 | Rosen | Feb 2013 | B2 |
| 8428307 | Bradai et al. | Apr 2013 | B2 |
| 8461973 | Reed et al. | Jun 2013 | B2 |
| 8630768 | McClellan et al. | Jan 2014 | B2 |
| 20010014849 | King et al. | Aug 2001 | A1 |
| 20010018628 | Jenkins et al. | Aug 2001 | A1 |
| 20020019703 | Levine | Feb 2002 | A1 |
| 20020024444 | Hiyama et al. | Feb 2002 | A1 |
| 20020026334 | Igoe | Feb 2002 | A1 |
| 20020029226 | Li et al. | Mar 2002 | A1 |
| 20020111725 | Burge | Aug 2002 | A1 |
| 20020116228 | Bauer et al. | Aug 2002 | A1 |
| 20020120371 | Leivian et al. | Aug 2002 | A1 |
| 20020126023 | Awada | Sep 2002 | A1 |
| 20020128000 | do Nascimento, Jr. | Sep 2002 | A1 |
| 20020173881 | Lash et al. | Nov 2002 | A1 |
| 20030013460 | Papadias et al. | Jan 2003 | A1 |
| 20030016636 | Tari et al. | Jan 2003 | A1 |
| 20030045273 | Pyhalammi et al. | Mar 2003 | A1 |
| 20030052797 | Rock et al. | Mar 2003 | A1 |
| 20030055555 | Knockeart et al. | Mar 2003 | A1 |
| 20030060950 | McKeown et al. | Mar 2003 | A1 |
| 20030069000 | Kindo et al. | Apr 2003 | A1 |
| 20030125854 | Kawasaki et al. | Jul 2003 | A1 |
| 20030134660 | Himmel et al. | Jul 2003 | A1 |
| 20030169185 | Taylor | Sep 2003 | A1 |
| 20030191564 | Haugse et al. | Oct 2003 | A1 |
| 20040039504 | Coffee et al. | Feb 2004 | A1 |
| 20040039609 | Burkitt | Feb 2004 | A1 |
| 20040054687 | McDonough | Mar 2004 | A1 |
| 20040056779 | Rast | Mar 2004 | A1 |
| 20040066330 | Knockeart et al. | Apr 2004 | A1 |
| 20040077339 | Martens | Apr 2004 | A1 |
| 20040083041 | Skeen et al. | Apr 2004 | A1 |
| 20040107037 | Straub | Jun 2004 | A1 |
| 20040107220 | Natesan et al. | Jun 2004 | A1 |
| 20040139034 | Farmer | Jul 2004 | A1 |
| 20040142672 | Stankewitz | Jul 2004 | A1 |
| 20040153362 | Bauer et al. | Aug 2004 | A1 |
| 20040172418 | Dorum et al. | Sep 2004 | A1 |
| 20040176083 | Shiao et al. | Sep 2004 | A1 |
| 20040186661 | Barton | Sep 2004 | A1 |
| 20040210353 | Rice | Oct 2004 | A1 |
| 20040225557 | Phelan et al. | Nov 2004 | A1 |
| 20040236474 | Chowdhary et al. | Nov 2004 | A1 |
| 20040236475 | Chowdhary | Nov 2004 | A1 |
| 20040252027 | Torkkola et al. | Dec 2004 | A1 |
| 20040254698 | Hubbard et al. | Dec 2004 | A1 |
| 20040257245 | Jo | Dec 2004 | A1 |
| 20040260579 | Tremiti | Dec 2004 | A1 |
| 20050021270 | Hong et al. | Jan 2005 | A1 |
| 20050049765 | Chetia et al. | Mar 2005 | A1 |
| 20050064835 | Gusler | Mar 2005 | A1 |
| 20050065711 | Dahlgren et al. | Mar 2005 | A1 |
| 20050070245 | Nath et al. | Mar 2005 | A1 |
| 20050091018 | Craft | Apr 2005 | A1 |
| 20050091175 | Farmer | Apr 2005 | A9 |
| 20050096809 | Skeen et al. | May 2005 | A1 |
| 20050102098 | Montealegre et al. | May 2005 | A1 |
| 20050107944 | Hovestadt et al. | May 2005 | A1 |
| 20050119002 | Bauchot et al. | Jun 2005 | A1 |
| 20050131597 | Raz et al. | Jun 2005 | A1 |
| 20050137757 | Phelan et al. | Jun 2005 | A1 |
| 20050143903 | Park et al. | Jun 2005 | A1 |
| 20050171663 | Mittelsteadt et al. | Aug 2005 | A1 |
| 20050184860 | Taruki et al. | Aug 2005 | A1 |
| 20050255874 | Stewart-Baxter et al. | Nov 2005 | A1 |
| 20050273218 | Breed et al. | Dec 2005 | A1 |
| 20060025894 | Oconnor et al. | Feb 2006 | A1 |
| 20060053038 | Warren et al. | Mar 2006 | A1 |
| 20060055565 | Kawamata et al. | Mar 2006 | A1 |
| 20060112573 | Hillman et al. | Jun 2006 | A1 |
| 20060121951 | Perdomo et al. | Jun 2006 | A1 |
| 20060154687 | McDowell | Jul 2006 | A1 |
| 20060193749 | Ghazarian et al. | Aug 2006 | A1 |
| 20060208169 | Breed et al. | Sep 2006 | A1 |
| 20060212195 | Veith et al. | Sep 2006 | A1 |
| 20060212495 | Tokunaga et al. | Sep 2006 | A1 |
| 20060220905 | Hovestadt | Oct 2006 | A1 |
| 20060234711 | McArdle | Oct 2006 | A1 |
| 20060253307 | Warren et al. | Nov 2006 | A1 |
| 20060265125 | Glaza | Nov 2006 | A1 |
| 20060281495 | Yang | Dec 2006 | A1 |
| 20060284769 | Bolduc et al. | Dec 2006 | A1 |
| 20070005404 | Raz et al. | Jan 2007 | A1 |
| 20070005609 | Breed | Jan 2007 | A1 |
| 20070027583 | Tamir et al. | Feb 2007 | A1 |
| 20070027726 | Warren et al. | Feb 2007 | A1 |
| 20070050130 | Grimm et al. | Mar 2007 | A1 |
| 20070057781 | Breed | Mar 2007 | A1 |
| 20070061155 | Ji et al. | Mar 2007 | A1 |
| 20070126601 | Park | Jun 2007 | A1 |
| 20070186923 | Poutiatine et al. | Aug 2007 | A1 |
| 20070202929 | Satake | Aug 2007 | A1 |
| 20070229234 | Smith | Oct 2007 | A1 |
| 20070236342 | Hines et al. | Oct 2007 | A1 |
| 20070260363 | Miller | Nov 2007 | A1 |
| 20070293206 | Lund | Dec 2007 | A1 |
| 20080027642 | Winberry et al. | Jan 2008 | A1 |
| 20080030316 | Flick | Feb 2008 | A1 |
| 20080046274 | Geelen et al. | Feb 2008 | A1 |
| 20080059055 | Geelen et al. | Mar 2008 | A1 |
| 20080064413 | Breed | Mar 2008 | A1 |
| 20080064446 | Camp et al. | Mar 2008 | A1 |
| 20080065325 | Geelen et al. | Mar 2008 | A1 |
| 20080082225 | Barrett | Apr 2008 | A1 |
| 20080120175 | Doering | May 2008 | A1 |
| 20080177469 | Geelen et al. | Jul 2008 | A1 |
| 20080221787 | Vavrus | Sep 2008 | A1 |
| 20080243558 | Gupte | Oct 2008 | A1 |
| 20080252487 | McClellan et al. | Oct 2008 | A1 |
| 20080255888 | Berkobin | Oct 2008 | A1 |
| 20080258890 | Follmer et al. | Oct 2008 | A1 |
| 20080296968 | Culbert | Dec 2008 | A1 |
| 20080319602 | McClellan et al. | Dec 2008 | A1 |
| 20090024273 | Follmer et al. | Jan 2009 | A1 |
| 20090024419 | McClellan et al. | Jan 2009 | A1 |
| 20090079555 | Aguirre De Carcer et al. | Mar 2009 | A1 |
| 20090085728 | Catten et al. | Apr 2009 | A1 |
| 20100030459 | Geelen et al. | Feb 2010 | A1 |
| 20100030586 | Taylor et al. | Feb 2010 | A1 |
| 20100035632 | Catten | Feb 2010 | A1 |
| 20100130182 | Rosen | May 2010 | A1 |
| 20100131189 | Geelen et al. | May 2010 | A1 |
| 20100131304 | Collopy et al. | May 2010 | A1 |
| 20100134182 | Kapoor et al. | Jun 2010 | A1 |
| 20100205012 | Mcclellan | Aug 2010 | A1 |
| 20100207751 | Follmer et al. | Aug 2010 | A1 |
| 20100207787 | Catten et al. | Aug 2010 | A1 |
| 20100265074 | Namba et al. | Oct 2010 | A1 |
| 20110115618 | Catten | May 2011 | A1 |
| 20110179080 | Miyazaki et al. | Jul 2011 | A1 |
| 20110267205 | McClellan et al. | Nov 2011 | A1 |
| 20120040650 | Rosen | Feb 2012 | A1 |
| 20120092148 | Santos | Apr 2012 | A1 |
| 20120181765 | Hill et al. | Jul 2012 | A1 |
| 20120295646 | Johnson | Nov 2012 | A1 |
| 20130150004 | Rosen | Jun 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 2071931 | Dec 1993 | CA |
| 2307259 | Oct 2001 | CA |
| 2631103 | Nov 2008 | CA |
| 197 00 353 | Jul 1998 | DE |
| 0843177 | May 1998 | EP |
| 0921509 | Jun 1999 | EP |
| 1811481 | Jul 2007 | EP |
| 2434346 | Jul 2007 | GB |
| 2454224 | May 2009 | GB |
| 2004326492 | Nov 2004 | JP |
| 2005-250825 | Sep 2005 | JP |
| 2007235530 | Sep 2007 | JP |
| WO 2004019646 | Mar 2004 | WO |
| WO 2005003885 | Jan 2005 | WO |
| WO 2005109273 | Nov 2005 | WO |
| WO2005109369 | Nov 2005 | WO |
| WO 2008045320 | Aug 2008 | WO |
| WO2008109477 | Sep 2008 | WO |
| WO 2013033756 | Mar 2013 | WO |
| WO 2013050548 | Apr 2013 | WO |
| Entry |
|---|
| Zhu et al., “A Small Low-Cost Hybrid Orientation system and Its Error Analysis”, Sensors Journal, IEEE—vol. 9, Issue 3, Digital Object Identifier: 10.1109/JSEN.2008.2012196; Publication Year: Mar. 2009, pp. 223-230. |
| Almazan et al., “Full auto-calibration of a smartphone on board a vehicle using IMU and GPS embedded sensors”, Intelligent Vehicles Symposium (IV), 2013 IEEE; Digital Object Identifier: 10.1109/IVS.2013.6629658; Publication Year: Jun. 2013, pp. 1374-1380. |
| Lupton et al., “Efficient Integration of Inertial Observations Into Visual SLAM Without Initialization”, Intelligent Robots and Systems, 2009, IROS 2009, IEEE/RSJ International Conference on: Digital Object Identifier: 10.1109/IROS.2009.5354267, Publication Year: Oct. 2009, pp. 1547-1552. |
| Mungula et al., “Attitude and Heading System Based on EKF Total State Configuration”, Industrial Electronics (ISIE), 2011 IEEE International Symposium on; Digital Object Identifier: 10.1109/ISIE.2011.5984493; Publication Year: Jun. 2011, pp. 2147-2152. |
| Huddle et al., “Application of Inertial Navigation Systems to Geodetic Position and Gravity Vector Survey”, Decision and Control including the 17th Symposium on Adaptive Processes, 1978 IEEE Conference on; vol. 17, Part 1; Digital Object Identifier: 10.1109/CDC.1978.267967; Publication Year: 1978, pp. 459-465. (The month of Publication is irrelevant since the year of Publication is clearly prior to the filing of the Application). |
| Zhao Yan et al., “Attitude Measurement of Drivers Head Based on Accelerometer and Magnetoresistive Sensor”, Fluid Power and Mechatronics (FPM), 2011 International Conference on; Digital Object Identifier: 10.1109/FPM.2011.6045836; Publication Year: Aug. 2011, pp. 613-617. |
| U.S. Appl. No. 11/805,237, filed Oct. 28, 2013, Notice of Allowance. |
| Ogle, et al.; Accuracy of Global Positioning System for Determining Driver Performance Parameters; Transportation Research Record 1818; Paper No. 02-1063; pp. 12-24. |
| Shen, et al.; A computer Assistant for Vehicle Dispatching with Learning Capabilities; Annals of Operations Research 61; pp. 189-211, 1995. |
| Tijerina, et al.; Final Report Supplement; Heavy Vehicle Driver Workload Assessment; Task 5: Workload Assessment Protocol; U.S. Department of Transportation; 69 pages, Oct. 1996. |
| Myra Blanco; Effects of In-Vehicle Information System (IVIS) Tasks on the Information Processing Demands of a Commercial Vehicle Operations (CVO) Driver; 230 pages, 1999. |
| Phuyal B., “An Experiment for a 2-D and 3-D GPS/INS configuration for land vehicle applications”, Position Location and Navigation Symposium, 2004, PLANS 2004, Digital Object Identifier: 10.1109/PLANS.2004.1308987; Publication Year: 2004, Page(s): 148-152. (The month of Publication is irrelevant since the year of Publication is clearly prior to the filing of the Application). |
| Roberts et al., “Position Control of VTOL UAVs using IMU and GPS Measurements”, Decision and Control and European Conference (CDC-ECC), 2011 50th IEEE Conference on, Digital Object Identifier, 10.1109/CDC.2011.6160854, Publication Year: Dec. 2011, pp. 8082-8087. |
| Cho et al., “Obeservability Analysis of the INS/GPS Navigation System on the Measurements in Land Vehicle Applications”, Control, Automation and Systems, 2007, ICCAS '07, International Conference on Digital Object Identifier: 10.1109/CCAS.2007.4407018, Publication Year: Oct. 2007, pp. 841-846. |
| Vukajovic et al., “The Practical Design of In-Vehicle Telematics Device with GPS and MEMS Accelerometers”, Telecommunications Forum (TELFOR), 2011 19th: Digital Object Identifier: 10.1109/TELFOR.2011.6143692, Publication Year: Nov. 2011, pp. 908-911. |
| U.S. Appl. No. 11/805,238, filed Jul. 30, 2009, Office Action. |
| U.S. Appl. No. 11/779,176, filed Mar. 17, 2010, Office Action. |
| U.S. Appl. No. 11/805,238, filed Apr. 26, 2010, Notice of Allowance. |
| U.S. Appl. No. 11/805,237, filed Nov. 8, 2010, Office Action. |
| U.S. Appl. No. 11/768,056, filed Jan. 18, 2011, Office Action. |
| U.S. Appl. No. 12/222,260, filed Jan. 19, 2011, Office Action. |
| U.S. Appl. No. 13/012,660, filed Feb. 16, 2011, Office Action. |
| U.S. Appl. No. 12/379,083, filed Apr. 8, 2011, Office Action. |
| U.S. Appl. No. 12/379,153, filed Jul. 29, 2011, Office Action. |
| U.S. Appl. No. 12/379,154, filed Aug. 1, 2011, Office Action. |
| U.S. Appl. No. 11/805,237, filed Aug. 8, 2011, Office Action. |
| U.S. Appl. No. 11/779,176, filed Aug. 18, 2011, Office Action. |
| U.S. Appl. No. 11/768,056, filed Sep. 16, 2011, Office Action. |
| U.S. Appl. No. 12/222,260, filed Oct. 14, 2011, Office Action. |
| U.S. Appl. No. 11/779,178, filed Nov. 2, 2011, Office Action. |
| U.S. Appl. No. 13/012,660, filed Nov. 14, 2011, Office Action. |
| U.S. Appl. No. 12/379,083, filed Nov. 23, 2011, Office Action. |
| U.S. Appl. No. 12/379,153, filed Dec. 16, 2011, Office Action. |
| U.S. Appl. No. 12/379,154, filed Jan. 2012, Notice of Allowance. |
| U.S. Appl. No. 11/805,237, filed Feb. 1, 2012, Office Action. |
| U.S. Appl. No. 12/379,083, filed Feb. 2, 2012, Office Action. |
| U.S. Appl. No. 11/768,056, filed Feb. 26, 2012, Office Action. |
| U.S. Appl. No. 12/222,260, filed Mar. 29, 2012, Office Action. |
| U.S. Appl. No. 13/012,660, filed Apr. 11, 2012, Office Action. |
| U.S. Appl. No. 11/779,178, filed May 31, 2012, Office Action. |
| U.S. Appl. No. 11/805,237, filed Jun. 15, 2012, Office Action. |
| U.S. Appl. No. 11/768,056, filed Jul. 19, 2012, Office Action. |
| U.S. Appl. No. 12/379,153, filed Jul. 31, 2012, Notice of Allowance. |
| U.S. Appl. No. 13/012,660, filed Aug. 1, 2012, Office Action. |
| U.S. Appl. No. 12/222,260, filed Nov. 7, 2012, Office Action. |
| U.S. Appl. No. 13/012,660, filed Nov. 26, 2012, Office Action. |
| U.S. Appl. No. 11/805,237, filed Dec. 3, 2012, Office Action. |
| U.S. Appl. No. 11/779,176, filed Dec. 3, 2012, Office Action. |
| U.S. Appl. No. 11/779,178, filed Dec. 20, 2012, Office Action. |
| U.S. Appl. No. 13/012,660, filed Mar. 18, 2013 Office Action. |
| U.S. Appl. No. 11/779,178, filed May 9, 2013, Office Action. |
| U.S. Appl. No. 12/379,083, filed May 23, 2013, Office Action. |
| U.S. Appl. No. 12/222,260, filed Jun. 5, 2013, Office Action. |
| U.S. Appl. No. 11/805,237, filed Jun. 6, 2013, Office Action. |
| U.S. Appl. No. 11/768,056, filed Jun. 21, 2013, Office Action. |
| U.S. Appl. No. 11/779,176, filed Jul. 1, 2013, Notice of Allowance. |
| U.S. Appl. No. 13/012,660, filed Jul. 8, 2013, Office Action. |
| U.S. Appl. No. 12/379,153, filed Aug. 14, 2013, Notice of Allowance. |
| U.S. Appl. No. 12/975,489, filed Oct. 3, 2013, Office Action. |
| U.S. Appl. No. 12/379,083, filed Jan. 3, 2014, Office Action. |
| U.S. Appl. No. 11/778,178, filed Feb. 6, 2014, Office Action. |
| U.S. Appl. No. 11/768,056, filed Feb. 6, 2014, Office Action. |
| U.S. Appl. No. 13/012,660, filed Feb. 13, 2014, Office Action. |
| U.S. Appl. No. 12/379,155, filed Jun. 19, 2014, Office Action. |
| U.S. Appl. No. 13/012,660, filed Jun. 6, 2014, Notice of Allowance. |
| U.S. Appl. No. 11/779,178, filed May 27, 2014, Notice of Allowance. |
| Google Maps, “Google Maps”, Available at least as early as Dec. 29, 2014. Whole Document. |
| U.S. Appl. No. 12/379,153, filed Mar. 17, 2014, Office Action. |
| U.S. Appl. No. 12/975,489, filed Oct. 1, 2014, Notice of Allowance. |
| U.S. Appl. No. 12/379,153, filed Oct. 6, 2014, Office Action. |
| U.S. Appl. No. 12/379,153, filed Jan. 9, 2015, Notice of Allowance. |
| Number | Date | Country | |
|---|---|---|---|
| 20080255722 A1 | Oct 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60802478 | May 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11805237 | May 2007 | US |
| Child | 11755556 | US |
