System and method for monitoring and improving driver behavior

Information

  • Patent Grant
  • 9129460
  • Patent Number
    9,129,460
  • Date Filed
    Monday, June 25, 2007
    17 years ago
  • Date Issued
    Tuesday, September 8, 2015
    9 years ago
Abstract
System and method for providing feedback to drivers. The system monitors selected vehicle parameters while a vehicle is being driven, and detects one or more vehicle operation violations by comparing the selected vehicle parameters to predetermined thresholds. A mentoring message is provided to the driver if the threshold is exceeded. If a vehicle operation violation has not been corrected within a preselected time period, then a violation report may be sent to a third party or a central server and/or a different mentoring message may be provided to the driver. Vehicle parameter data may be monitored from an on-board vehicle diagnostic system. The mentoring message may be an audible warning, such as a spoken message, or a visual warning, such as a text message. The selected vehicle parameters may be a vehicle speed, a vehicle acceleration, or a vehicle seatbelt use.
Description
TECHNICAL FIELD

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 monitoring driving against minimum standards and for improving driver behavior


BACKGROUND

Currently there are systems that allow a fleet manager or vehicle owner to track the location of their vehicle(s) such as by using a GPS reporting capability of a cellular phone or other wireless device. These devices may provide additional notification, such as when a vehicle leaves or enters a predefined area (i.e. a geofence) or when the vehicle exceeds a certain speed. However, other than providing such warnings or notifications to a fleet manager, vehicle owner, parent or other supervisor, the current systems provide little or no real-time feedback to the driver to correct their behavior.


Without having a driving instructor or other operator in the vehicle, there is currently no system or method available for providing real-time feedback, training and mentoring to drivers based upon the actual operation of the vehicle (i.e. based upon the driver's behavior while driving). Accordingly, aggressive driver behavior and driver inattention may not be detected and/or corrected, thereby reducing driver and vehicle safety. The absence of feedback as a means to identify unsatisfactory driving behavior dissociates the driver from the infraction; denial is the likely result. However, immediate feedback to infractions or undesirable driving behavior has enormous benefit in mentoring the driver and delineating acceptable from unacceptable driving behavior.


BRIEF SUMMARY

There exists a need in the art for a driver mentoring system that is adaptable for use in various settings, including commercial fleet operators, teen drivers, and new drivers, 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. The present invention relates to a system and method for monitoring driver behavior for use by companies, government agencies, consumers, or the general public. For example, the present invention allows parents to remotely mentor the driving habits of their teen children as well as allow for monitoring of geographic areas into which their children may enter. Moreover, the present invention may also be used by fleet operators to monitor and mentor the driving behavior of experienced drivers.


The vehicle behavior monitoring system disclosed herein provides for real-time reconfiguration of driver performance and vehicle operation parameters and which allows for reporting of such data in order to generate driver profiles and trends. The present invention provides a unique vehicle monitoring system specifically adapted to mentor driver performance in order to improve driver safety and reduce accident rates and formulate various methods to establish and/or delineate “good” driving behavior from “bad” driving behavior.


In one embodiment, the invention is directed to a system and method for providing feedback to drivers. The system monitors selected vehicle parameters while a vehicle is being driven, and detects one or more vehicle operation violations by comparing the selected vehicle parameters to predetermined thresholds. A mentoring message is provided to the driver if the threshold is exceeded. If a vehicle operation violation has not been corrected within a preselected time period, then a violation report may be sent to a third party or a central server. If a vehicle operation violation has not been corrected within a preselected time period, then a different mentoring message may be provided to the driver. Vehicle parameter data may be monitored from an on-board vehicle diagnostic system. The mentoring message may be an audible warning, such as a spoken message, or a visual warning, such as a text message. The selected vehicle parameters may be a vehicle speed, a vehicle speed for the specific road conditions, a vehicle acceleration, an errant lane departure, following too close to a subsequent vehicle, a vehicle seatbelt use, the use of a mobile phone, the detection of unlawful ethanol concentrations, the detection of fatigue (blink rate) and/or other traceable, detectable activities, elements, and/or behaviors.


In another embodiment, a system and method for monitoring vehicle operation, comprises installing a monitoring device in a vehicle, wherein the monitoring device monitors vehicle operation parameters, and wherein the vehicle monitoring device is capable of providing mentoring feedback to a driver. The vehicle operation is monitored without providing the mentoring feedback during a baseline period and baseline vehicle operation data is collected for the baseline period. Baseline vehicle operation data may be collected for multiple vehicles.


After the baseline period, vehicle operation is monitored and mentoring feedback is provided to the driver. Mentored vehicle operation data is collected after the baseline period. The mentored vehicle operation data is compared to the baseline vehicle operation data to determine driving improvement. The vehicle operation parameters for monitoring during the baseline period may be selected by the user. The baseline vehicle operation data and/or mentored vehicle operation data can be transmitted to a central server.


A system and method for establishing a vehicle operation profile, comprises installing a monitoring device in a vehicle, wherein the monitoring device monitors vehicle operation parameters, monitoring vehicle operation during a training period, collecting vehicle operation training data for the training period, and creating the vehicle operation profile based upon the vehicle operation training data. The vehicle operation is then monitored during a monitoring period; and vehicle operation data during the monitoring period is compared to the vehicle operation profile.


Mentoring messages can be provided to a driver based upon differences between the vehicle operation data and the vehicle operation profile. The vehicle operation profile comprises thresholds for the vehicle operation parameters, and vehicle operation data observed during the monitoring period is compared to the thresholds. The vehicle operation parameters to be monitored during the training period and/or during the mentoring period may be selected by a user.


Thresholds are established for vehicle operation parameters based upon the vehicle operation training data. The thresholds correspond to an average observed value of the vehicle operation parameters, a maximum observed value of the vehicle operation parameters, or a selected percentage above a value of the vehicle operation parameters. The user may adjust the thresholds for vehicle operation parameters from an observed value. Alternatively, a user may adjust the thresholds for vehicle operation parameters from value established by the vehicle monitoring system.





BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:



FIG. 1 is a diagram of a system incorporating embodiments of the invention mounted in a vehicle;



FIG. 2 is a diagram of possible locations of cameras and/or other technologies used in embodiments of the invention;



FIG. 3 is a flowchart illustrating one process for implementing the present invention;



FIG. 4 illustrates a process for measuring baseline data; and



FIG. 5 illustrates a process for creating an acceptable driving profile.





DETAILED DESCRIPTION

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.


With reference now to FIG. 1, there is shown a vehicle 101 in which a vehicle monitoring device is installed. The monitoring device may be self contained, such as a single unit mounted on a windshield 105 or dashboard 106. Alternatively, the monitoring device may include multiple components, such as a processor or central unit mounted under a car seat 103 or in a trunk 104. Similarly, the monitoring device may have a self-contained antenna in the unit (105), or may be connected to remotely mounted antennas 107. The vehicle monitoring units may be connected to an on-board diagnostic (OBD) system or bus in the vehicle. Information and data associated with the operation of the vehicle may be collected from the OBD system, such as engine operating parameters, vehicle identification, seatbelt use, door position, etc. The OBD system may also be used to power the vehicle monitoring device. In one embodiment, the vehicle monitoring device is of the type described in U.S. patent application Ser. No. 11/755,556, filed on May 30, 2007, entitled “System and Method for Evaluating Driver Behavior,” the disclosure of which is hereby incorporated by reference herein in its entirety.


Information may be exchanged between the vehicle monitoring system and a central monitoring system or server in real-time or at intervals. For example, the vehicle operation parameters may be transmitted to server 109 via communication network 108, which may be a cellular, satellite, WiFi, Bluetooth, infrared, ultrasound, short wave, microwave or any other suitable network. Server 109 may process the parameters and/or store the data to database 110, which may be part of server 109 or a separate device located nearby or at a remote location. Users can access the data on server 109 and database 110 using terminal 111, which may be co-located with server 109 and database 110 or coupled via the Internet or other network connection. Is some embodiments, the data captured by the monitoring system in vehicle 101 may be transmitted via a hardwired communication connection, such as an Ethernet connection that is attached to vehicle 101 when the vehicle is within a service yard or at a base station. Alternatively, the data may be transferred via a flash memory, diskette, or other memory device that can be directly connected to server 109 or terminal 111. Data, such as driving performance or warning thresholds, may also be uploaded from the central server to the vehicle monitoring device in a similar manner.


In one embodiment of the invention, the data captured by the vehicle monitoring system is used to monitor, mentor or other wise analyze a driver's behavior during certain events. For example, if the vehicle is operated improperly, such as speeding, taking turns too fast, colliding with another vehicle, or driving in an unapproved area, then a supervisor may want to review the data recorded during those events to determine what the driver was doing at that time and if the driver's behavior can be improved. Additionally, if the driver's behavior is inappropriate or illegal, such as not wearing a seatbelt or using a cell phone while driving, but does not cause the vehicle to operate improperly, a supervisor may also want to review the data recorded during those events.


Referring to FIG. 2, exemplary mounted locations for the vehicle monitoring system are illustrated, such as on a dashboard 201, windshield 202, or headliner 203. It will be understood that all or parts of the vehicle monitoring system may be mounted in any other location that allows for audio and/or visual feedback to the driver of the vehicle while the vehicle is in operation. Monitoring device 201 is illustrated as being coupled to OBD 102, from which it may receive inputs associated with vehicle operating parameters. Monitoring devices 202 and 203 may be similarly coupled to OBD 102 (connections not shown). Moreover, the vehicle monitoring system may be coupled to other sensors, such as a sensor for detecting the operation and use of a cellular or wireless device in the vehicle.


In one aspect of the invention, the vehicle monitoring system includes an accelerometer module (XLM) that includes at least one accelerometer for measuring at least one of lateral (sideways), longitudinal (forward and aft) and vertical acceleration in order to determine whether the driver is operating the vehicle in an unsafe or aggressive manner. For example, excessive lateral acceleration may be an indication that the driver is operating the vehicle 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.


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.


The vehicle monitoring system may further include a self-contained and tamper-resistant event data recorder or crash data recorder (CDR), such as, for example, the CDR 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 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 the impact. The CDR may be separate from the accelerometer module (XLM) or may be the same device.


In one aspect, the vehicle monitoring system may be in data communication with an on board diagnostic (OBD) TI system of the vehicle such as via a port. In some vehicle models, the vehicle monitoring system is in data communication with a controller area network (CAN) system (bus) to allow acquisition 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, and the like. The OBD or CAN allows for acquisition of the above-mentioned vehicle parameters for processing thereby and/or for subsequent transmission to the central server 109.


The vehicle monitoring system may also include a GPS receiver (or other similar technology designed to track location) configured to track the location and directional movement of the vehicle in either real-time or over-time modes. As is well known in the art, GPS signals may be used to calculate the latitude and longitude of a vehicle as well as allowing for tracking of vehicle movement by inferring speed and direction from positional changes. Signals from GPS satellites also allow for calculating the elevation and, hence, vertical movement, of the vehicle.


Embodiments of the vehicle monitoring system may further include a mobile data terminal (MDT) mounted for observation and manipulation by the driver, such as near the vehicle dash. The MDT preferably has an operator interface 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. The MDT may include at least one warning mechanism such as a speaker and/or a warning light 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.


The vehicle monitoring system receives inputs from a number of internal and external sources. The OBD II/CAN bus, which provides data from the vehicle's on-board diagnostic system, including engine performance data and system status information. A GPS receiver provides location information. The CDR, XLM, or accelerometers provide information regarding the vehicle's movement and driving conditions. Any number of other sensors, such as but not limited to, a seat belt sensor, proximity sensor, driver monitoring sensors, or cellular phone use sensors, also provide inputs to the vehicle monitoring system.


The vehicle monitoring system compares these inputs to preset thresholds and determines when an exception condition occurs or when a threshold is exceeded that requires an alarm to be generated in the vehicle. The alarm may be an audible and/or visual warning for the vehicle occupants. Additionally, any of the data collected may be passed on to server 109 or database 110 where it may be further processed or accessed. The vehicle operation thresholds may be entered directly into the vehicle monitoring system or may be received as updated, revised, or corrected rule sets, commands or logic from server 109.


The vehicle monitoring system may have any type of user interface, 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. The system or the user interface 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. Additionally, monitoring system may have a speaker and microphone integral to the device.


The monitoring system may be self-powered, such as by a battery, or powered by the vehicle's battery and/or power generating circuitry. Access to the vehicle's battery power may be by accessing the power available on the vehicle's OBD and/or CAN bus.


The vehicle monitoring system may be self-orienting, which allows it to be mounted in any position, angle or orientation in the vehicle or on the dashboard. In embodiments of the invention, the vehicle monitoring system determines a direction of gravity and a direction of vehicle movement and determines its orientation within the vehicle using this information. In order to provide more accurate measurements of driver behavior, in one embodiment, the present invention filters gravitational effects out of the longitudinal, lateral and vertical acceleration measurements when the vehicle is on an incline or changes its horizontal surface orientation. Driver performance is monitored and mentored using the accelerometer module, which preferably 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 acceleration input signal is generated when a measured acceleration exceeds a predetermined threshold.


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 and/or mentor 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.


An embodiment of the invention provides real-time mentoring, training, or other feedback to a driver while operating the vehicle. The mentoring is based upon observed operation of the vehicle and is intended to change and improve driver behavior by identifying improper or illegal operation of the vehicle. Using preset criteria or thresholds, the vehicle monitoring system identifies when the vehicle is operated outside the criteria or beyond the preset thresholds to determine that a violation has occurred.


Numerous parameters may be measured by the vehicle monitoring system and used to provide driver mentoring. Speeding criteria, such as driving above a maximum speed limit, violation of a posted speed limit in a speed-by-street database, or violating a speed limit in a designated zone, may cause the vehicle monitoring system to warn the driver. U.S. patent application Ser. No. 11/805,238, filed May 22, 2007, entitled “System and Method for Monitoring and Updating Speed-By-Street Data,” the disclosure of which is hereby incorporated by reference herein in its entirety, describes the use of speed-by-street information by a vehicle monitoring system. Upon detection of the speeding violation, the monitoring system will provide an audible and/or visual warning to the driver. For example, a spoken message identifying the speeding condition or a spoken message instructing the driver to slow down may be played to the driver. Alternatively, a selected tone or buzzer may sound when a speeding violation occurs. A visual warning, such as an LED warning light may illuminate or flash to notify the driver of a violation.


The vehicle monitoring system may identify aggressive driving violations. For example, based upon the inputs from an acceleration module or CDR, aggressive driving events may be detected, such as exceeding acceleration thresholds in a lateral, longitudinal, or vertical direction, hard turns, hard acceleration or jackrabbit starts, hard braking, and/or hard vertical movement of the vehicle. Visual and/or audible warnings may be played or displayed to the driver upon a violation of an acceleration threshold.


Other violations, such as operating the vehicle outside or inside a specific area or off of a specific route can trigger a visual or audible mentoring message to the driver. Areas and routes may be defined, for example, using a geofence that is compared to the vehicle's current location as determined by the GPS system. Seat belt use violation, such as failing to use a seatbelt while driving, may be detected, for example, via the OBD bus and may trigger a mentoring message to use the seatbelt. Sensors that detect exposure to ethanol (EtOH) vapor and/or detect blood EtOH levels, may be used to determine if a driver has been drinking and may have a blood alcohol level that is illegal. Based upon inputs from an EtOH sensor, the vehicle monitoring device may provide mentoring feedback to the driver or may disable the vehicle. Other sensors may detect the use of wireless devices, such as cell phones, in the vehicle. Upon detecting cell phone use, the vehicle monitoring system may issue a warning to the driver to stop using the cell phone.


In one embodiment, the present invention provides real-time automatic exception alerts and reporting in the form of e-mail, phone calls, or pages to facilitate intervention and to change driver behavior. Such reporting, such as to a parent, fleet manager, supervisor, or other authority, may be made immediately upon detection of the violation or may occur if the violation is not corrected within a predetermined period of time. The alerts may contain, for example, driver performance reports such as a speeding index, “harsh” driving (e.g. acceleration, braking, turning, vertical indices) conditions, a seatbelt index and the like. The vehicle monitoring system may be configured to provide an immediate alert, or a grace period may be configured to allow the driver to correct the violation. If the violation is corrected by the driver, then no alert is sent to report the violation, thereby allowing the vehicle monitoring system to mentor the driver without human intervention.


The present invention to combines triggering events with visual and/or audible warning to change driver behavior. The mentoring messages may be configured by event or violation. For a selected parameter, such as vehicle speed, a user may configure one or more thresholds that, when exceeded, trigger a mentoring message. The type and content of the mentoring messages are also configurable. For example, audible and/or visual warnings may be assigned to each threshold criteria so that, upon reaching the threshold speed, for example, a selected warning is played or displayed. The warnings may be further configured to change over time. For example, audible warnings, such as tones or buzzers, may increase in volume or frequency or may change to different sound if the triggering violation is not corrected. A spoken message warning, such as “speeding violation” or “slow down,” may be repeated more frequently and/or louder if the speeding violation is not corrected. Alternatively, the spoken message may change to a different message and/or a different voice if the triggering event is not stopped. Visual messages, such as warning lights, may change from flashing to steady (or visa versa) if the violation continues. Text warning messages may also be displayed to the user and may change over time.



FIG. 3 is a flowchart illustrating one process for implementing the present invention. In step 301, a user selects and configures one or more threshold levels for parameters associated with vehicle operation and driver behavior. As noted above, these parameters may be a speeding parameter, an acceleration parameter, a seatbelt notice parameter, or any other parameter that may be measured by the vehicle monitoring system. Multiple thresholds may be assigned to a parameter, such as multiple levels of speeding thresholds to detect progressively worse speeding violations. In step 302, the user assigns audible and visual mentoring messages to each threshold level that was selected in step 301. For example, a visual mentoring message, such as a warning light, may be assigned to a first speeding threshold, the warning light may be assigned to flash if a second speeding threshold is exceeded, and an audible message may be played if a third speeding threshold is exceeded.


For thresholds assigned in step 301, a grace period is assigned in step 303. The grace period may be a number of seconds or minutes. The grace period corresponds to a period of time in which the driver is allowed to correct a violation without triggering a report to a third party. The grace period may also be zero (i.e. no time for correction of the violation). In step 304, alerts are selected for the thresholds assigned in step 301. The alerts are messages or reports to be sent to third parties, such as a fleet manager, parent or supervisor, if the grace period expires and the violation has not been corrected.


In step 305, the vehicle monitoring device monitors vehicle parameters and thereby monitors the driver's performance while operating the vehicle. When a vehicle parameter exceeds the corresponding threshold set in step 301, the violation is detected in step 306. The vehicle monitoring system broadcasts the selected mentoring message to the driver. The mentoring message may be played and/or displayed one time or may be configured to repeat. If the violation has not been corrected, and the parameter is not back within the threshold criteria upon expiration of the grace period, then the selected alert is sent to the designated recipient in step 308.


The threshold criteria, mentoring messages, grace periods, and alerts selected and configured in steps 301-304 may be specific to a particular vehicle or driver. Alternatively, the variables may be selected for a group of drivers based on employer, age, experience or other criteria, for a type of vehicle, for an entire fleet of drivers or vehicles, or for any other group of one or more vehicles or drivers. The threshold criteria may be manually entered into the monitoring system on a vehicle-by-vehicle basis. Alternatively, an operator may select the threshold criteria on terminal 111, for example, and then transmit the criteria wirelessly or by wireline connection to the monitoring system in one or more vehicles.


In one embodiment, a baseline measurement is made for driver performance before the vehicle monitoring system begins providing mentoring to the driver. The baseline data can later be used to measure improvement in driver performance. The baseline data may be specific to single driver or to individual drivers. Alternatively, the baseline data may represent information from a fleet of drivers.



FIG. 4 illustrates a process for measuring baseline data. In step 401, vehicle monitoring systems are installed in one or more vehicles. Multiple vehicles in a fleet with many drivers or a single vehicle driven by a single driver may be used to determine the baseline data. In step 402, all driver warnings, mentoring messages and alerts are disabled or turned off so that the drivers will not receive any feedback during the baseline measurement. It is important for the drivers to operate their vehicles “normally” during the baseline measurement and for them to drive as they have historically. By turning off all feedback from the monitoring devices, the driver will be less likely to change his usually driving behavior during the baseline period. In step 403, the vehicle monitoring system monitors the driver's performance and the vehicle's parameters while the vehicle is being driven. In step 404, data is collected during the baseline period for selected vehicle parameters. Data for all of the measurable or detectable parameters may be collected during this period, or data for only selected parameters may be recorded. Finally, in step 405, the data from multiple vehicles, trips, or users is collected and compiled to create a baseline measurement for a fleet of vehicles.


Following the baseline period, the monitoring system will have collected information such as an average number of seatbelt violations for a driver per day, an average number of speeding violations per day, an average amount of excess speed (MPH) per speeding violation, an average number of jackrabbit starts per trip, and similar measurements. It will be understood that the collected data may be analyzed in any number of ways depending upon the requirements of a user. For example, data such as the total number of violations per parameter, an average number of violations per time period, or an average number of violations per driver, may be determined. Additional data, such as the amount of time elapsed until a violation is corrected, may also be collected.


The baseline data may be collected by individual vehicle monitoring systems and then uploaded, such as wirelessly, by wireline connection or by memory device, to server 109. A user can then review and analyze the baseline data via terminal 111. By reviewing the baseline data, the user may be able to identify violations that occur most frequently, that take the longest to correct, or that are most dangerous. The baseline data can then be used to determine and set mentoring thresholds for drivers. The mentoring thresholds may be set as single standard for an entire fleet, or may be tailored to individual drivers. For example, if the baseline data shows few incidents of seatbelt violations, the user may decide not to provide mentoring feedback for seatbelt violations or that a low-key mentoring message would be used. On the other hand, if speeding violations were more common than expected, the user could set multiple speeding thresholds with progressively shrill mentoring message to focus the driver feedback on the speeding violations.


In another embodiment, the monitoring system or device installed in a vehicle may be placed in a training mode. While in the training mode, the vehicle monitoring device observes the operation of the vehicle over a period of time and establishes a profile of good or acceptable driving behavior. The training mode allows the vehicle monitoring system to learn how the vehicle should be operated by observing an experienced driver, for example. When the device training period is completed, the vehicle monitoring system is switched to a monitoring mode. In the monitoring mode, the vehicle monitoring system provides feedback to the driver based upon the driving profile observed and recorded while in the training mode.


The training mode may be used, for example, by a parent who has installed a vehicle monitoring device in a family car. After installation, the vehicle monitoring device is set to training mode and the parent drives the car for sufficient time, such as for several days or weeks, to create a profile of acceptable driving. After the device has observed sufficient vehicle use in the training mode, the vehicle monitoring system is set to monitoring mode and a new driver, teen driver, or any other family members will get feedback and mentoring from the vehicle monitoring system based upon the driving behavior observed in the training mode. Similarly, a vehicle monitoring device installed in a commercial, government, or fleet vehicle may be placed in a training mode while an experienced driver, supervisor, or driving instructor operates the vehicle. Once a driving profile has been created for the vehicle, the monitoring system is switched to monitoring mode and other drivers will receive feedback and mentoring from the device based upon the learned profile.


The parameters observed during a training mode may be a default standard for all users or may be selected by individual users, thereby allowing each user to highlight particular areas of interest. While in the training mode, for example, the vehicle monitoring system may observe the experienced driver's compliance with speed limits as compared to a speed-by-street database, the average and maximum speeds driven on various types of roads, the typical starting and braking accelerations, typical lateral acceleration in turns, and occurrences seatbelt or cellular phone use. The vehicle monitoring system stores or remembers the measured parameters, such as acceleration, deceleration, signaling in lane changes, degree of aggressiveness in turns, and the like. The vehicle monitoring system collects this data and establishes thresholds for various vehicle operation parameters, such as speeding and acceleration thresholds. These thresholds establish a good or acceptable driving standard for that vehicle. There may be one or more drivers of the vehicle during the training mode, such as both parents driving a family car. The vehicle monitoring device may or may not be notified that different drivers are using the vehicle. The vehicle monitoring device may create a single acceptable driving profile based upon all users of the vehicle. Alternatively, multiple acceptable profiles may be created, such as one per driver in the training mode. One of the training profiles may then be selected for use in the monitoring mode.


Using the training or learning mode, the present invention allows the vehicle monitoring system to provide appropriate feedback to drivers based upon the typical use of that vehicle by experience drivers. For example, during a training mode, if a parent typically exceeds speed limits by 5 MPH, uses the seatbelt for each drive, never does jackrabbit starts, and tends to brake hard in stops, then those parameters will be applied to a teen driver in the monitoring mode. For example, the vehicle monitoring system may set a first speeding threshold at 5 MPH above posted speed limits. If the teen driver operates the vehicle in the same manner as the parent, few or no mentoring messages would be broadcast to the teen driver. However, if the teen driver does not use a seatbelt and tends to do jackrabbit starts, then those events will trigger mentoring messages or warnings from the vehicle monitoring system.


When the training mode is completed, and the vehicle monitoring system has created a profile of acceptable driving parameters, those parameters are stored in memory in the monitoring device. The acceptable driving parameters may be reviewed by the experienced driver, such as via a display on the vehicle monitoring system. The acceptable driving parameters may also be sent to central server 109 or other computer for review by the experienced driver or others, such as via terminal 111. The parameters and thresholds observed during the training mode may be reviewed at any time during the training period or after the training is completed. The parent, supervisor or experienced driver accept all of the parameters and thresholds established during the training period for use during the monitoring mode, or those parameters and thresholds may be used as initial values that can be further adjusted for use in the monitoring mode. For example, a parent reviewing his driving parameters captured during training period may determine that certain features of his driving should not be emulated, such as excessive speeding violations or failure to use seatbelts. The parent may adjust the thresholds for these elements to require more strict compliance by the teen driver in the monitoring mode.



FIG. 5 illustrates a process for creating an acceptable driving profile. In step 501, a vehicle monitoring system is installed and the training mode is started. In step 502, the vehicle is operated by a parent, driving instructor or other experienced driver in the training mode during a training period. In step 503, the vehicle monitoring system observes all or selected vehicle parameters during the training period. The observed parameters may be all of the parameters measurable by the monitoring system or a default subset of those parameters, or a user may select specific parameters to be observed. In step 504, the vehicle monitoring system creates an acceptable driving profile based upon the observed parameters. The parent or experienced driver may review the acceptable driving profile parameters and thresholds in step 505. The parent, experienced driver or other authority may change the selection of parameters to be observed during the training period. The thresholds generated by the vehicle monitoring system during the training mode may also be adjusted, if, for example, those thresholds are too strict or lenient. In step 506, the training mode ends and a profile representing acceptable driving behavior is selected. The monitoring mode is started in step 507, and from that point on, in step 508, the monitoring device provides mentoring and warning messages to the driver based upon selected acceptable driving profile.


In one embodiment, the vehicle monitoring system does not immediately apply the thresholds set in the training mode. Instead, when the monitoring mode starts, the vehicle monitoring device sets the mentoring and warning thresholds at values 30%, for example, above those set during the training mode. Then after some period of time, such as after one week, the thresholds are moved to 20%, for example, of the training mode values. This stair-step approach would allow the driver in the training mode to improve his or her performance over time without having to be “perfect” or having to meet the training mode criteria immediately. Ultimately, the vehicle monitoring system may set the thresholds to the values established during a training mode, or the monitoring mode thresholds may always remain at some value above the training mode, such as 5-10% higher than what was observed during the training mode.


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.

Claims
  • 1. A computer-implemented method for monitoring driver behavior and for providing corresponding feedback, the method comprising: a computing system that includes at least one processor, monitoring at least one vehicle parameter during operation of a vehicle;the computing system detecting a vehicle operation violation when the at least one vehicle parameter exceeds a corresponding threshold associated with the at least one vehicle parameter;the computing system causing a first warning to be rendered to a driver at one or more feedback devices in the vehicle in response to detecting that the at least one vehicle parameter exceeds the corresponding threshold;the computing system, in response to detecting that the vehicle operation violation continues to persist without being corrected for a first predetermined period of time after the first warning is rendered, causing a corresponding report violation to be generated; andthe computing system, in response to detecting that the vehicle operation violation continues to persist without being corrected after the first warning is rendered, causing a second warning to be rendered to the driver at the one or more feedback devices in the vehicle, wherein the second warning is rendered differently or is of a different type than the first warning.
  • 2. The method of claim 1, wherein the method further includes monitoring a plurality of different types of parameters associated with a plurality of different corresponding thresholds.
  • 3. The method of claim 2, wherein the method further includes generating a different type of alert for each different type of violation that occurs when the plurality of different types of parameters exceed the corresponding thresholds.
  • 4. The method of claim 2, wherein the plurality of different types of parameters includes a proximity of the vehicle to another vehicle.
  • 5. The method of claim 2, wherein the plurality of different types of parameters includes a fatigue level measured by at least a blink rate of the driver.
  • 6. The method of claim 2, wherein the plurality of different types of parameters includes ethanol detection.
  • 7. The method of claim 2, wherein the plurality of different types of parameters includes detected phone use.
  • 8. The method of claim 2, wherein the plurality of different types of parameters includes hard turns.
  • 9. The method of claim 2, wherein the plurality of different types of parameters includes accelerations.
  • 10. The method of claim 2, wherein the plurality of different types of parameters includes seat belt use.
  • 11. The method of claim 1, wherein the second warning is rendered at a different volume than the first warning.
  • 12. The method of claim 1, wherein the second warning is rendered with different content than the first warning.
  • 13. The method of claim 1, wherein the second warning includes visual and aural warnings.
  • 14. The method of claim 1, wherein the method further includes increasing a frequency for rendering warnings over time as the vehicle operation violation continues to persist without being corrected.
  • 15. The method of claim 1, wherein the method further includes setting the corresponding threshold from data obtained while monitoring the at least one vehicle parameter from the vehicle during a baseline period.
  • 16. The method of claim 1, wherein the one or more feedback devices includes one or more speakers.
  • 17. The method of claim 1, wherein the one or more feedback devices includes one or more visual feedback devices.
  • 18. The method of claim 1, wherein the method includes sending the report to a third party.
  • 19. A vehicle monitoring system comprising: one or more sensors connected to a vehicle;one or more feedback devices;at least one processor; andone or more monitoring devices connected to the one or more sensors, the one or more feedback devices and the at least one processor, the one or more monitoring devices being configured to implement a method for monitoring driver behavior detected by the one or more sensors and for providing corresponding feedback at the one or more feedback devices, wherein the method includes:monitoring at least one vehicle parameter during operation of the vehicle;detecting a vehicle operation violation when the at least one vehicle parameter exceeds a corresponding threshold associated with the at least one vehicle parameter;causing a first warning to be rendered to a driver at the one or more feedback devices in the vehicle in response to detecting that the at least one vehicle parameter exceeds the corresponding threshold;in response to detecting that the vehicle operation violation continues to persist without being corrected for a first predetermined period of time after the first warning is rendered, causing a corresponding report violation to be generated; andin response to detecting that the vehicle operation violation continues to persist without being corrected after the first warning is rendered, causing a second warning to be rendered to the driver at the one or more feedback devices in the vehicle, wherein the second warning is rendered differently or is of a different type than the first warning.
  • 20. The vehicle monitoring system of claim 19, wherein the method further includes monitoring a plurality of different types of parameters associated with a plurality of different corresponding thresholds.
  • 21. The vehicle monitoring system of claim 20, wherein the plurality of different types of parameters includes detected phone use.
  • 22. The vehicle monitoring system of claim 21, wherein the computer monitoring system is a distributed computing system.
  • 23. The vehicle monitoring system of claim 20, wherein the method further includes generating a different type of alert for each different type of violation that occurs when the plurality of different types of parameters exceed the corresponding thresholds.
  • 24. The vehicle monitoring system of claim 20, wherein the plurality of different types of parameters includes a proximity of the vehicle to another vehicle.
  • 25. The vehicle monitoring system of claim 20, wherein the plurality of different types of parameters includes a fatigue level measured by at least a blink rate of the driver.
  • 26. The vehicle monitoring system of claim 20, wherein the plurality of different types of parameters includes ethanol detection.
  • 27. The method of claim 20, wherein the plurality of different types of parameters includes jack rabbit starts.
  • 28. The vehicle monitoring system of claim 19, wherein the second warning is rendered at a different volume than the first warning.
  • 29. The vehicle monitoring system of claim 19, wherein the second warning is rendered with different content than the first warning.
  • 30. The vehicle monitoring system of claim 19, wherein the second warning includes visual and aural warnings.
  • 31. The vehicle monitoring system of claim 19, wherein the method further includes increasing a frequency for rendering warnings over time as the vehicle operation violation continues to persist without being corrected.
  • 32. The vehicle monitoring system of claim 19, wherein the method further includes setting the corresponding threshold from data obtained while monitoring the at least one vehicle parameter during a baseline period.
  • 33. The vehicle monitoring system of claim 19, wherein the method includes sending the report to a third party.
  • 34. The vehicle monitoring system of claim 19, wherein the computing system is a distributed computing system.
  • 35. The vehicle monitoring system of claim 19, wherein the one or more feedback devices includes one or more speakers.
  • 36. The vehicle monitoring system of claim 19, wherein the one or more feedback devices includes one or more lights.
  • 37. A hardware storage device having stored computer-executable instructions which, when executed by at least one processor of a computer monitoring system, implement a method for the computer monitoring system monitoring driver behavior detected by one or more sensors and for providing corresponding feedback at one or more feedback devices, wherein the method includes: the computer monitoring system monitoring at least one vehicle parameter during operation of the vehicle;the computer monitoring system detecting a vehicle operation violation when the at least one vehicle parameter exceeds a corresponding threshold associated with the at least one vehicle parameter;the computer monitoring system causing a first warning to be rendered to a driver at the one or more feedback devices in the vehicle in response to detecting that the at least one vehicle parameter exceeds the corresponding threshold;the computer monitoring system, in response to detecting that the vehicle operation violation continues to persist without being corrected for a first predetermined period of time after the first warning is rendered, causing a corresponding report violation to be generated; andthe computer monitoring system, in response to detecting that the vehicle operation violation continues to persist without being corrected after the first warning is rendered, causing a second warning to be rendered to the driver at the one or more feedback devices in the vehicle, wherein the second warning is rendered differently or is of a different type than the first warning.
  • 38. The hardware storage device of claim 37, wherein the method further includes: monitoring a plurality of different types of parameters associated with a plurality of different corresponding thresholds; andgenerating a different type of alert for each different type of violation that occurs when the plurality of different types of parameters exceed the corresponding thresholds.
  • 39. The hardware storage device of claim 38, wherein the plurality of different types of parameters includes at least one of proximity of the vehicle to another vehicle, jack rabbit starts or hard turns.
  • 40. The hardware storage device of claim 38, wherein the plurality of different types of parameters includes at least one of driver fatigue level, ethanol detection, seat belt use or phone use.
  • 41. The hardware storage device of claim 37, wherein the second warning is rendered differently than the first warning.
  • 42. The hardware storage device of claim 37, wherein the second warning is of a different type than the first warning.
  • 43. The hardware storage device of claim 37, wherein the method further includes setting the corresponding threshold based on monitoring the at least one vehicle parameter from the vehicle during a baseline period.
  • 44. The hardware storage device of claim 37, wherein the method includes sending the report to a third party.
US Referenced Citations (660)
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 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 et al. 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
5617086 Klashinsky et al. Apr 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
6161072 Clapper Dec 2000 A
6172602 Hasfjord Jan 2001 B1
6178374 Möhlenkamp 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 Jul 2001 B1
6255939 Roth 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 Bchler Jan 2002 B1
6339739 Folke Jan 2002 B1
6339745 Novik Jan 2002 B1
6343301 Halt et al. 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
6385533 Halt et al. May 2002 B1
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 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
6587759 Obradovich Jul 2003 B2
6594579 Lowrey Jul 2003 B1
6599243 Woltermann et al. 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 Lightner May 2004 B1
6732032 Banet 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
6853910 Oesterling 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
6934611 McKeown 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 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 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
7176813 Kawamata et al. Feb 2007 B2
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 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
7295921 Spencer et al. Nov 2007 B2
7298248 Finley Nov 2007 B2
7298249 Avery 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
7362239 Franczyk et al. Apr 2008 B2
7365639 Yuhara Apr 2008 B2
7366551 Hartley Apr 2008 B1
7375624 Hines et al. 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
7398153 Workman et al. 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 Middelsteadt et al. Sep 2009 B2
7589643 Dagei et al. Sep 2009 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
7783406 Rothschild Aug 2010 B2
7821421 Tamir et al. Oct 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
8188887 Catten et al. May 2012 B2
8314708 Gunderson et al. Nov 2012 B2
8428307 Bradai et al. Apr 2013 B2
8630768 McClellan et al. Jan 2014 B2
20010014849 King et al. Aug 2001 A1
20010018628 Jenkins et al. Aug 2001 A1
20010048364 Kalthoff et al. Dec 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
20020111844 Vanstory et al. 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 Sep 2002 A1
20020173881 Lash et al. Nov 2002 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
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
20050273218 Breed et al. Dec 2005 A1
20060022842 Zoladeck et al. Feb 2006 A1
20060025894 Oconner 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
20060220905 Hovestadt Oct 2006 A1
20060224306 Workman et al. Oct 2006 A1
20060234711 McArdle Oct 2006 A1
20060253307 Warren et al. Nov 2006 A1
20060265125 Glaza Nov 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
20070139189 Helmig 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
20080065325 Geelen et al. Mar 2008 A1
20080082221 Nagy Apr 2008 A1
20080082225 Barrett Apr 2008 A1
20080086508 Ballew 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
20080255722 McClellan et al. Oct 2008 A1
20080255888 Berkobin Oct 2008 A1
20080262670 McClellan et al. Oct 2008 A1
20080294690 McClellan et al. Nov 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 Apr 2009 A1
20100030459 Geelen et al. Feb 2010 A1
20100030586 Taylor et al. 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
20120181765 Hill et al. Jul 2012 A1
Foreign Referenced Citations (22)
Number Date Country
2071931 Dec 1993 CA
2 307 259 Oct 2001 CA
2631103 Nov 2008 CA
197 00 353 Jul 1998 DE
19700353 Jul 1998 DE
0 843 177 May 1998 EP
0921509 Jun 1999 EP
1811481 Jul 2007 EP
2434346 Jul 2007 GB
2454224 May 2009 GB
2004326492 Nov 2004 JP
2005-223791 Aug 2005 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
Non-Patent Literature Citations (72)
Entry
European Patent Office; European Search Report for Application No. 08779728.8-1229 / 2165321 PCT/US2008007820; 6 pages, Dec. 27, 2011.
Australian Government; IP Australia; Examiner's First Report for Patent Application No. 2008269142; 3 pages, Jun. 4, 2012.
Ogle, et al.; Accuracy of Global Positioning System for Determining Driver Performance Parameters; Transportation Research Record 1818; Paper No. 02-1063; pp. 12-24, Unknown.
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.
The State Intellectual Property Office of P. R. China; English Translation of the First Office Action; for Application No. 200880101242.2; 15 pages, Dec. 7, 2011.
English Translation of the Patent Abstracts of Japan for Publication No. JP2005-250825; 42 pages, Sep. 15, 2005.
Japanese Office Action and English Translation of the Text of the First Office Action for Application No. 2010-514773; 7 pages, Sep. 4, 2012.
Chinese Office Action for Application No. 200880101242.2; 7 pages, Sep. 24, 2012.
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 Driver's 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.
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, pp. 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, Jul. 30, 2009, Office Action.
U.S. Appl. No. 11/755,556, Sep. 1, 2009, Office Action.
U.S. Appl. No. 11/779,176, Mar. 17, 2010, Office Action.
U.S. Appl. No. 11/805,238, Apr. 26, 2010, Notice of Allowance.
U.S. Appl. No. 11/755,556, May 4, 2010, Office Action.
U.S. Appl. No. 11/758,444, Jul. 20, 2010, Office Action.
U.S. Appl. No. 11/805,237, Nov. 8, 2010, Office Action.
U.S. Appl. No. 13/012,660, Feb. 16, 2011, Office Action.
U.S. Appl. No. 12/379,083, Apr. 8, 2011, Office Action.
U.S. Appl. No. 12/379,153, Jul. 29, 2011, Office Action.
U.S. Appl. No. 12/379,154, Aug. 1, 2011, Office Action.
U.S. Appl. No. 11/805,237, Aug. 8, 2011, Office Action.
U.S. Appl. No. 11/779,176, Aug. 18, 2011, Office Action.
U.S. Appl. No. 11/779,178, Nov. 2, 2011, Office Action.
U.S. Appl. No. 13/012,660, Nov. 14, 2011, Office Action.
U.S. Appl. No. 12/379,083, Nov. 23, 2011, Office Action.
U.S. Appl. No. 12/379,153, Dec. 16, 2011, Office Action.
U.S. Appl. No. 12/379,154, Jan. 30, 2012, Notice of Allowance.
U.S. Appl. No. 11/805,237, Feb. 1, 2012, Office Action.
U.S. Appl. No. 12/379,083, Feb. 2, 2012, Office Action.
U.S. Appl. No. 13/012,660, Apr. 11, 2012, Office Action.
U.S. Appl. No. 11/779,178, May 31, 2012, Office Action.
U.S. Appl. No. 11/805,237, Jun. 15, 2012, Office Action.
U.S. Appl. No. 12/379,153, Jul. 31, 2012, Notice of Allowance.
U.S. Appl. No. 13/012,660, Aug. 1, 2012, Office Action.
U.S. Appl. No. 13/012,660, Nov. 26, 2012, Office Action.
U.S. Appl. No. 11/805,237, Dec. 3, 2012, Office Action.
U.S. Appl. No. 11/779,176, Dec. 3, 2012, Office Action.
U.S. Appl. No. 11/779,178, Dec. 20, 2012, Office Action.
U.S. Appl. No. 13/012,660, Mar. 18, 2013, Office Action.
U.S. Appl. No. 11/779,178, May 9, 2013, Office Action.
U.S. Appl. No. 12/379,083, May 23, 2013, Office Action.
U.S. Appl. No. 11/805,237, Jun. 6, 2013, Office Action.
U.S. Appl. No. 11/779,176, Jul. 1, 2013, Notice of Allowance.
U.S. Appl. No. 13/012,660, Jul. 8, 2013, Office Action.
U.S. Appl. No. 12/379,153, Aug. 14, 2013, Notice of Allowance.
U.S. Appl. No. 12/975,489, Oct. 3, 2013, Office Action.
U.S. Appl. No. 11/755,556, Jun. 10, 2014, Office Action.
U.S. Appl. No. 13/012,660, Jun. 6, 2014, Notice of Allowance.
U.S. Appl. No. 11/758,444, Jun. 27, 2014, Office Action.
U.S. Appl. No. 11/779,178, 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, Mar. 17, 2014, Office Action.
U.S. Appl. No. 12/975,489, Oct. 1, 2014, Notice of Allowance.
U.S. Appl. No. 12/379,153, Oct. 6, 2014, Office Action.
U.S. Appl. No. 12/379,153, Jan. 9, 2015, Notice of Allowance.
U.S. Appl. No. 12/379,083, Jan. 3, 2014, Office Action.
U.S. Appl. No. 11/778,178, Feb. 6, 2014, Office Action.
U.S. Appl. No. 13/012,660, Feb. 13, 2014, Office Action.
U.S. Appl. No. 11/758,444, Feb. 21, 2014, Office Action.
U.S. Appl. No. 12/379,083, Mar. 17, 2015, Office Action.
U.S. Appl. No. 11/755,556, Mar. 30, 2015, Notice of Allowance.
Related Publications (1)
Number Date Country
20080319602 A1 Dec 2008 US