Method and system for providing feedback based on driving behavior

Information

  • Patent Grant
  • 9665997
  • Patent Number
    9,665,997
  • Date Filed
    Tuesday, January 8, 2013
    11 years ago
  • Date Issued
    Tuesday, May 30, 2017
    7 years ago
Abstract
Providing feedback based on driving behavior. At least some of the illustrative embodiments are methods including: determining an indication of driving behavior of a driver, the determining by: identifying the driver in a vehicle; detecting movement of the vehicle; collecting data related to the driving behavior of the driver; and issuing an alert related to the driving behavior of the driver for the purpose of providing feedback related to the driving behavior.
Description
BACKGROUND

Drivers, including new drivers, may not be aware of their driving habits and behaviors unless they have a passenger with them in the vehicle. Even in that instance, a driver may not be aware of whether his driving behaviors are rare or common, and whether they relate to an inefficient operation of the vehicle or whether they indicate unsafe or safe operation of the vehicle. Thus, any advancement that allows a driver to receive feedback related to his driving may be beneficial in improving driving related behaviors and habits.





BRIEF DESCRIPTION OF THE DRAWINGS

For a detailed description of exemplary embodiments, reference will now be made to the accompanying drawings in which:



FIG. 1 shows, in block diagram form, a system in accordance with at least some embodiments;



FIG. 2 shows, in block diagram form, a monitoring module in accordance with at least some embodiments;



FIG. 3 shows, in block diagram form, an identification module in accordance with at least some embodiments;



FIG. 4A shows example alert notifications in accordance with at least some embodiments;



FIG. 4B shows example alert notifications in accordance with at least some embodiments;



FIG. 4C shows example alert notifications in accordance with at least some embodiments;



FIG. 4D shows example alert notifications in accordance with at least some embodiments;



FIG. 5 shows, in block diagram form, an after-market system connected to a vehicle in accordance with at least some embodiments;



FIG. 6 shows, in block diagram form, a method in accordance with at least some embodiments; and



FIG. 7 shows, in block diagram form, a computer system in accordance with at least some embodiments.





NOTATION AND NOMENCLATURE

Certain terms are used throughout the following description and claims to refer to particular system components. As one skilled in the art will appreciate, companies may refer to a component by different names. This document does not intend to distinguish between components that differ in name but not function. In the following discussion and in the claims, the terms “including” and “comprising” are used in an open-ended fashion, and thus should be interpreted to mean “including, but not limited to . . . .” Also, the term “couple” or “couples” is intended to mean either an indirect, direct, optical or wireless electrical connection. Thus, if a first device couples to a second device, that connection may be through a direct electrical connection, through an indirect electrical connection via other devices and connections, through an optical electrical connection, or through a wireless electrical connection.


“Remote” shall mean one kilometer or more.


DETAILED DESCRIPTION

The following discussion is directed to various embodiments of the invention. Although one or more of these embodiments may be preferred, the embodiments disclosed should not be interpreted, or otherwise used, as limiting the scope of the disclosure, including the claims. In addition, one skilled in the art will understand that the following description has broad application, and the discussion of any embodiment is meant only to be exemplary of that embodiment, and not intended to intimate that the scope of the disclosure, including the claims, is limited to that embodiment.


Various embodiments are directed to issuing an alert to a driver or a third party related to the driving behavior of a driver in a vehicle. In particular, a driver is first identified as the driver for whom the driving behaviors will be monitored. Then, data related to the driver's operation of the vehicle is collected, and at least one alert may be issued based on the driving behavior of the driver. The alert may be issued in real-time in accordance with specific driving situations, or the alert may be sent at the end of a predetermined time period and may indicate an aggregation of driving behavior indications over the predetermined time period.



FIG. 1 shows, in block diagram form, a system in accordance with at least some embodiments. In particular, the system comprises an operations center 100 communicatively coupled to a vehicle 112 by way of a wireless network 110. The operations center 100 comprises a processor 102. In some embodiments, the processor 102 may be a stand-alone computer system, or the processor may comprise a plurality of computer systems communicatively coupled and performing the functions of the operations center, the functions discussed more thoroughly below. The processor 102 may couple to an administrative user interface 104. The administrative user interface may enable an administrative agent 106 to control or configure the operation of the system. The processor 102 may also couple to an owner/driver interface 126. The owner/driver interface may enable the owner 128 of the vehicle 112 to control or configure the operation of the system. In another embodiment, owner 128 may be the driver of the vehicle as well. In yet another embodiment, the driver 128 may not be the vehicle owner, but may also control or configure the operation of the system.


The operations center 100 may further comprise a mapping module 120 coupled to the processor 102. In accordance with at least some embodiments, the mapping module 120 is a stand-alone computer system executing software to perform a mapping function associated with the location of the vehicle 112. In yet still other embodiments, the mapping module 120 may be a computer program or program package that operates or executes on the processor 102.


In order to communicate with the vehicle 112, the operations center 100 may further comprise a network interface 108 communicatively coupled to the processor 102. By way of the network interface 108, the processor 102, and any programs executing thereon, may communicate with vehicle 112, such as by wireless network 110. Wireless network 110 is illustrative of any suitable communications network, such as a cellular network, a pager network, or other mechanism for transmitting information between the operations center 100 and the vehicle 112.


In accordance with at least some embodiments, the operations center 100 is remotely located from the vehicle 112. In some cases, the operations center 100 and vehicle 112 may be located within the same city or state. In other cases, the operations center 100 may be many hundreds or thousands of miles from vehicle 112, and thus the illustrative wireless network 110 may span several types of communication networks.


Still referring to FIG. 1, the system further comprises a vehicle 112 communicatively coupled to operations center 100 by way of the illustrative wireless network 110. The vehicle 112 may comprise a computer system 116 communicatively coupled to a wireless network interface 114, a monitoring module 118, a mapping module 120, and an identification module 124. The wireless network interface 114 enables the computer system 116 to communicate with operations center 100 by way of a wireless transmission through the wireless network 110. The monitoring module 118 may assist the computer system 116 and/or the operations center 100 in collecting data related to the driving behavior of the driver. Mapping module 120 may assist the computer system 116 in performing a mapping function associated with the location of the vehicle 112. Identification module 124 may assist the computer system 112 and/or the operations center 100 in collecting data related to identifying which driver is operating the vehicle 112. Various techniques for monitoring the vehicle, as well as identifying the driver, will be discussed more thoroughly below.


In accordance with at least some embodiments, the operations center 100 may have the ability to send an alert 132 related to driving behavior to an administrative agent 106, a vehicle owner or driver 128, and/or a third party external agent 130. The alert related to driving behavior may be transmitted using any suitable communications system, including electronic mail, short messaging service (SMS), instant messaging, automated telephone calls, and the like. Likewise, the vehicle 112, in some embodiments, may have the ability to directly send the alert 132, by way of wireless network 110, to the administrative agent, vehicle owner or driver, and/or a third party external agent. However, in other cases, the alert 132 may be sent from the vehicle 112 by way of wireless network 110 to the operations center 100 before being sent to the administrative agent, the vehicle owner or driver, and/or the third party external agent.


The specification now turns to a high level description of detecting driving behaviors. In particular, driving behaviors may be detected, at least in part, by a device or devices in the monitoring module 118 coupled to the computer system 116. That is, either data gathered by the computer system 116 by way of the monitoring module 118 may determine driving behaviors, or data gathered by the monitoring module 118 and communicated by way of a wireless transmission to the operations center 100 may determine the driving behaviors of a driver operating vehicle 112. Various example embodiments of determining driving behaviors will be discussed more thoroughly below.


Turning now to FIG. 2, FIG. 2 shows, in block diagram form, monitoring module 118 in greater detail. In particular, in accordance with at least some embodiments, the monitoring module 118 may comprise a Global Positioning System (GPS) receiver 200. The GPS comprises a plurality of satellites broadcasting very precise timing signals. The GPS receiver 200, receiving a plurality of the timing signals, may determine not only the location of the GPS receiver 200 (and thus the vehicle 112), but may also establish navigation information, such as speed and direction of travel. In accordance with at least some embodiments, the navigation information derived from the GPS receiver 200 can be used to determine at least some driving behaviors. For example, in some embodiments, the monitoring module 118 may detect that the driver is exceeding speed limits by monitoring the speed of the vehicle 112 as received by the GPS receiver 200. In another embodiment, location information received by GPS receiver 200 may aid in detecting whether the driver slams on his brakes by recognizing a sudden deceleration over a short period of time (e.g., coming to a complete stop from 60 miles per hours in one second or less). Slamming on the brakes may be indicative of coming to an unexpected stop when speeding, when tailgating, or when not paying attention to other drivers. In yet another embodiment, the vehicle may experience one or more sudden changes of direction in the plane of travel (i.e., the plane on which the car rests. In one embodiment, if the vehicle is driving on a flat, non-sloped road, the plane of travel is the plane of the road itself) which may indicate a vehicle swerving in and out of traffic, or making quick, sudden lane changes.


In some cases, the computer system 116 communicating with GPS receiver 200 may make the determination that vehicle 112 is driving in a way that a real-time alert should be issued to an administrative agent, the vehicle owner or driver, or a third party. In other cases, however, the computer system 116 may read the data from the GPS receiver 200, and send the navigation data to the operations center 100 by the wireless network 110. In another embodiment, an indication of driving behavior may be stored in memory of computer system 116. In another embodiment, the indication of driving behavior may be sent from vehicle 112 over wireless network 110 to the operations center 100 and then stored for later access or transmission.


Still referring to FIG. 2, in addition to, or in place of, the GPS receiver 200, in accordance with at least some embodiments, the monitoring module 118 may comprise one or more accelerometers 202 communicatively coupled to the computer system 116. In some embodiments, a single accelerometer may be sufficient for determining the vehicle has applied the brakes, engaged the accelerator pedal, has changed lanes, and with what force and speed each action has occurred. In other embodiments, the accelerometer 202 may comprise a three-axis accelerometer, such that acceleration in all three dimensions can be determined. While a three-axis accelerometer 202 cannot determine absolute position, data read from a three axis-accelerometer may be helpful in determining driving behaviors. Consider, for example, the situation of a driver slamming on his brakes to avoid hitting a car that has stopped in front of him. In some embodiments using an accelerometer, the deceleration rate of a vehicle exceeding some predetermined value may be indicative of the driver slamming on his brakes to avoid a collision or to avoid running a red light. Similarly, if the driver swerves to avoid a collision, or to change lanes swiftly, as may occur when a driver is weaving in and out of traffic, the three-axis accelerometer may be able to determine a rate of change of direction in the z-plane exceeding a predetermined value within a predetermined time. While at some levels the determination discussed with respect to the accelerometers are somewhat duplicative of the determinations that may be made using the GPS receiver 200, determinations using the accelerometers 202 may be made more quickly than the same determinations made using GPS receivers 200, and may also provide a different overall picture of a driver's driving habits.


Still referring to FIG. 2, monitoring module 118 may also comprise vehicle sensors 204. In one embodiment, vehicle sensor 204 may comprise a seat belt sensor 206 coupled to the computer system 116. The computer system 116 or the operations center 100 may collect data regarding whether or not the seat belts have been fastened. In another embodiment, vehicle sensors 204 may comprise a turn signal sensor 208 coupled to the computer system. The turn signal sensor, in addition to the GPS receiver and/or accelerometers, may indicate whether a driver is using turn signals before turning or changing lanes.


Although not specifically shown in FIG. 2, monitoring module 118 may also comprise a plurality of other information and data gathering tools and devices. For example, in one embodiment, the monitoring module 118 may communicate with a lane departure warning system coupled to the onboard vehicle computer in order to receive data on whether the vehicle is drifting out of the lane in which it is currently traveling. In another embodiment, the monitoring module 118 may comprise technology to monitor changes in head and eye movement which may indicate whether the driver is or is not fully alert. In particular, changes in head and eye movement may be used to determine whether the driver is falling asleep at the wheel, is operating the radio or navigation system, or is using a mobile device for phone calls, internet use, or text messaging. In yet another embodiment, monitoring module 118 may utilize technology coupled to the onboard vehicle computer which monitors the distance between neighboring vehicles to determine whether the driver of the vehicle is tailgating or is otherwise driving at an unsafe distance from other vehicles. The monitoring module 118 is not limited to the technologies shown in FIG. 2 or to the additional technologies described herein, but may include any technologies and devices which may provide information and data related to the operation of the vehicle. The specification now turns to a high level description of identifying which driver is operating the vehicle for which data will be collected.


Turning now to FIG. 3, FIG. 3 shows, in block diagram form, an identification module 124. Identification module 124 is coupled to computer system 116 and wireless network interface 114, and may comprise a plurality of identification systems used to identify which driver is operating the vehicle. In particular, one vehicle may be driven by any number of drivers. For example, a family of four may have one vehicle which is driven by each of the four family members. In order to correctly assign an indication of driving behavior to the correct driver, the identification module 124 identifies which driver is operating the vehicle. The method of identifying a specific driver will be discussed more thoroughly below.


In one embodiment, identification module 124 may comprise a radio frequency (RF) receiver 306. The RF receiver 306 may establish which driver is operating the vehicle by way of receiving an RF signal from a key fob assigned to the driver. A driver may be assigned a unique key fob which allows him to, among other possibilities, unlock the vehicle, configure the interior to his preset preferences, and identify him as the driver for whom operation of the vehicle will be monitored.


In yet another embodiment, identification module 124 may comprise a fingerprint scanner 304 operatively coupled to the computer system 116. The fingerprint scanner may establish which driver is operating the vehicle by way of receiving a scan of the driver's fingerprint. The scanned fingerprint is matched to fingerprint images stored in memory, and the driver is identified. In yet still another embodiment, identification module 124 may comprise a microphone 300 operatively coupled to the computer system 116. The microphone 300 may help establish which driver is operating the vehicle by way of voice recognition. In particular, the microphone receives audio signals representing the driver's voice and subsequently matches the signals to voice files stored in a computer system, such as within computer system 116 or processor 102. The driver is then identified and associated with the subsequent vehicle operation.


In yet still another embodiment, identification module 124 may comprise an ocular scanner 302 operatively coupled to the computer system 116. The ocular scanner 302 may help establish which driver is operating the vehicle by way of scanning the driver's eye. In one embodiment, the ocular scanner 302 may be an iris scanner, and in another embodiment, the ocular scanner 302 may be a retinal scanner, however the scanning is not limited to only iris and retinal scans. A driver may have his eye scanned, and then eye scan is then matched to ocular maps stored in memory, and the driver is associated with the subsequent vehicle operation.


In yet still another embodiment, the driver may be identified by way of the wireless network 110 receiving a signal from the driver's mobile device located within the vehicle. In particular, the wireless network 110 may communicate with the driver's mobile device (e.g., such as through Bluetooth communications), to determine the mobile device is located within the vehicle, and thus associates the presence of the mobile device with the driver operating the vehicle.


While the above discussion provides a variety of ways in which the driver may be identified and subsequently linked to the operation of the vehicle, the ways in which the driver may be identified are not limited to the above examples.


The specification now turns to issuing an alert related to the driving behavior of the driver. Once a driver has been identified, the system begins collecting data related to the driving behavior of the driver. As discussed previously, a plurality of driving behavior data may be collected including, but not limited to, the speed of travel; braking force applied; z-plane movement; seat belt usage; and turn signal usage. In addition, in one embodiment, the location of the vehicle may be monitored to determine whether the driver is driving the vehicle in locations that are considered safe or dangerous (e.g., a neighborhood with a low or high crime rate). In another embodiment, the location of the vehicle in real-time combined with a weather report and an indication of driving behavior may indicate whether or not the driver has driving behaviors that vary based on the weather (e.g., driving slower in rain).


As data is collected, an alert may be received related to the driver's driving behavior. Turning now to FIGS. 4A-D, there may be a plurality of ways in which a driver may receive an alert. In particular, FIG. 4A shows the driver's view 400 from behind the wheel of the vehicle. When the driver drives in such a way that an alert may be issued, a head-up-display 402 on the windshield may display an alert containing the relevant alert information. In another embodiment, such as in FIG. 4B, the driver may receive the alert on a navigation computer system 406 coupled to the dashboard 404 of the vehicle. In yet another embodiment, such as in FIG. 4C, the driver may receive the alert 410 on a handheld wireless device 408 (e.g., a smartphone). In yet still another embodiment, FIG. 4D shows an example in which the driver may receive an alert 414 in the form of an electronic mail message; a pop-up alert; or an instant message on a display device 412, such as a laptop monitor or desktop monitor.


Issue alerts are not limited to being received by a driver. In another embodiment, a third party may receive an alert related to the driving behavior of the driver. For example, a parent may receive alerts related to the driving behavior of a child. In another embodiment, an insurance company may receive alerts related to the driving behavior of an insured driver.


Alerts may be issued in real-time as driver drives in such a way to warrant an alert. For example, if the driver exceeds the speed limit, an excessive speed alert may be issued. In another embodiment, however, data related to driving behavior may be stored, or aggregated and stored, for issuing an alert at a later time. As discussed previously, data related to driving behavior may be stored within computer system 116, or at a remote computer system. Regardless of where the indication of driving behavior may be stored, an alert may be issued that indicates an aggregate of driving behavior at the end of a selected time period. In one embodiment, the system may collect data related to driving behavior for each time period between the ignition being turned on and it being turned off (i.e., each car trip). In another embodiment, the system may collect data and report it by way of an alert at the end of an hour long period. In yet another embodiment, the system may collect data and report it by way of an alert at the end of a day period, or month.


Alerts related to driving behavior may be used as driving behavior feedback. If the alerts are issued to the driver, either in real time or at a later time period, the driver may be able to utilize driving behavior data to improve the efficiency and/or safety of operating the vehicle. For example, if a driver is receiving an alert indicative of an aggregation of data over the period of a week, the driver may notice a pattern of excessive speeds, or a tendency to make panic stops. Knowledge of these behaviors may result in the driver slowing down or being more aware of vehicles nearby that have come to a stop.


In another embodiments, alerts being issued to a third party may provide an indication of the type of driving in which the driver engages. In one embodiment, feedback related to the driver's driving behavior may be provided to an insurance company, which may affect the driver's insurance policy. For example, if the insurance company rarely receives alerts related to safe driving, the insurance company may lower the driver's premium or deductible. On the other hand, if the insurance company receives alerts indicating unsafe driving, the insurance company may increase the costs of being insured. In another embodiment, alerts may be issued to a financing company. For example, alerts indicating safe driving may lower the interest rate the driver is paying on a car loan. Regardless to whom the alerts are being issued, or whether they are being issued in real time, or after a set period of time, a driver or a third party may consider the alerts as feedback related to the driver's driving behavior.


Referring now to FIG. 5, in some embodiments, the wireless network interface 114, computer system 116, monitoring module 118, mapping module 120 and identification module 124 may be part of the vehicle 112 as purchased from the manufacturer or dealer. In other embodiments, however, the wireless network interface, computer system, monitoring module, mapping module, and identification module may be part of a third-party after-market system 502. In particular, FIG. 5 shows, in block diagram form, after-market system 502 coupled to vehicle 112 by way of an electrical connector 504, and comprises wireless network interface 506; computer system 508, mapping module 510, identification module 512, and monitoring module 514. In some embodiments, the after-market system 502 may be mechanically coupled to the inside of a vehicle 112, such as within the dashboard. In other embodiments, the after-market system 502 may be coupled at any suitable location, such as within the engine compartment, or in the trunk.


The method of determining an indication of driving behavior and issuing an alter related to driving behaviors will be discussed in more detail. FIG. 6 shows a flow diagram depicting an overall method of issuing an alert related to the driving behavior of a driver: The method starts (block 600), then moves to determining an indication of driving behavior of a driver (block 602), the determining by: identifying the driver in a vehicle (block 604); detecting movement of the vehicle (block 606); collecting data related to the driving behavior of the driver (block 608); and issuing an alert related to the driving behavior of the driver for the purpose of providing feedback related to driving behavior (block 610). Thereafter, the method ends (block 612).



FIG. 7 shows a computer system 700 which is illustrative of a computer system upon which the various embodiments may be practiced. The computer system 700 may be illustrative of, for example, computer system 116 coupled to the vehicle 112. In another embodiment, computer system 700 may be illustrative of processor 102. In yet another embodiment, the computer system could be illustrative of computer system 508 coupled to third-party after-market system 502. The computer system 700 comprises a processor 702, and the processor couples to a main memory 704 and a storage device 708 by way of a bridge device 706. Programs executable by the processor 702 may be stored on the storage device 708 (e.g., a hard drive, solid state disk, memory stick, optical disc), and accessed when needed by the processor 702. The program stored on the storage device 708 may comprise programs to implement the various embodiments of the present specification, such as determining driving habits of a driver. In some cases, the programs are copied from the storage device 708 to the main memory 704, and the programs are executed from the main memory 704. Thus, both the main memory 704 and storage device 708 shall be considered computer-readable storage mediums.


From the description provided herein, those skilled in the art are readily able to combine software created as described with appropriate general-purpose or special-purpose computer hardware to create a computer system and/or computer sub-components in accordance with the various embodiments, to create a computer system and/or computer sub-components for carrying out the methods of the various embodiments and/or to create a non-transitory computer-readable medium (i.e., not a carrier wave) that stores a software program to implement the method aspects of the various embodiments.


References to “one embodiment,” “an embodiment,” “some embodiment,” “various embodiments,” or the like indicate that a particular element or characteristic is included in at least one embodiment of the invention. Although the phrases may appear in various places, the phrases do not necessarily refer to the same embodiment.


The above discussion is meant to be illustrative of the principles and various embodiments of the present invention. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. For example, while the various embodiments have been described in terms of issuing alerts related to driving behaviors, this context shall not be read as a limitation as to the scope of one or more of the embodiments described—the same techniques may be used for other embodiments. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims
  • 1. A method comprising: communicating, by way of a wireless cellular network, between an identification module coupled within a vehicle and an operations center remote from the vehicle;determining an indication of driving behavior of a driver in the vehicle, the determining by: detecting, by the identification module, a wireless cellular signal transmitted from a mobile device associated with the driver wherein the mobile device is different from the identification module;identifying the driver in the vehicle by way of the detected wireless cellular signal;collecting data, by a monitoring module coupled to the vehicle, related to the driving behavior of the driver;issuing an alert to a third party, the alert providing the indication of driving behavior of the driver, wherein an interest rate of a vehicle loan currently issued to the driver is adjusted based on the alert.
  • 2. The method of claim 1 further comprising displaying the alert to the driver.
  • 3. The method of claim 2 wherein displaying the alert further comprises displaying the alert by way of at least one selected from the group consisting of: an alert sent to a smartphone application; a visual alert sent to a navigation system coupled to the vehicle; and an alert sent to a heads-up display (HUD) coupled to the vehicle.
  • 4. The method of claim 1 wherein collecting data further comprises collecting at least one selected from the group consisting of: location of the vehicle; speed of the vehicle; acceleration of the vehicle; deceleration of the vehicle; turn signal usage of the vehicle; and seat belt usage of the vehicle.
  • 5. The method of claim 1 further comprising: receiving, by a Global Positioning Receiver, Global Positioning System signals;creating, by the Global Positioning Receiver, location information based on the Global Positioning System signals; andmonitoring the movement of the vehicle based, at least in part, on the location information.
  • 6. The method of claim 1 further comprising: monitoring the movement of the vehicle based on movement detected by a three-axis accelerometer associated with the vehicle.
  • 7. A method comprising: communicating, by way of a wireless cellular network, between an identification module coupled within a vehicle and an operations center remote from the vehicle;determining an indication of driving behavior of a driver, the determining by: identifying, by the identification module, the driver in a vehicle by way of a wireless cellular signal transmitted from a mobile device associated with the driver;detecting movement of the vehicle;collecting data related to the driving behavior of the driver; andissuing an alert comprising the indication of driving behavior of the driver,wherein an interest rate of a vehicle loan currently issued to the driver is adjusted based on the alert.
  • 8. A system comprising: an onboard device comprising:a processor;a global positioning system receiver coupled to the processor;a wireless interface coupled to the processor;a memory coupled to the processor, the memory storing a program that, when executed by the processor, causes the processor to: identify a driver in a vehicle by way of a wireless cellular signal transmitted from a mobile device associated with the driver, wherein the mobile device is different from the onboard device;detect a movement of the vehicle;collect data related to the driving behavior of the driver; andissue an alert related to the driving behavior of the driver, wherein an interest rate of a vehicle loan currently issued to the driver is adjusted based on the alert.
  • 9. The system of claim 8 wherein when the processor issues the alert, the program further causes the processor to issue the alert to the driver.
  • 10. The system of claim 8 wherein when the processor issues the alert, the program further causes the processor to issue the alert to a third party.
  • 11. The system of claim 8 wherein when the processor collects, the program further causes the processor to collect data related to at least one selected from the group comprising: location of the vehicle; speed of the vehicle; acceleration of the vehicle; deceleration of the vehicle; turn signal usage of the vehicle; and seat belt usage of the vehicle.
  • 12. The method of claim 8 wherein when the processor detects, the program further causes the processor to detect based on Global Positioning System signals received.
  • 13. The method of claim 8 further comprising: a three-axis accelerometer coupled to the processor;wherein when the processor detects, the program further causes the processor to detect based on movement detected by the three-axis accelerometer.
  • 14. The method of claim 1 further comprising: receiving information from an individual, corresponding to configuring a set of boundaries, the configuration related to determining the indication of driving behavior and relating to issuing the alert.
  • 15. The method of claim 7 further comprising: receiving information from an individual, corresponding to configuring a set of boundaries, the configuration related to determining the indication of driving behavior and relating to issuing the alert.
  • 16. The system of claim 8 wherein when the processor collects data, the data is collected based on a configuration determined by the driver.
  • 17. The method of claim 1 wherein issuing the alert to the third party further comprises issuing the alert to a financing company in real-time as the driver drives.
  • 18. A system comprising: a processor;a wireless interface coupled to the processor;a memory coupled to the processor, the memory storing a program that, when executed by the processor, causes the processor to: receive an identity of a driver from an onboard device coupled to a vehicle;receive data collected by the onboard device coupled to the vehicle, the data related to the driving behavior of the driver; andissue an alert to a third party that causes an adjustment to an interest rate of a vehicle loan currently issued to the driver, wherein the alert is based on the data collected related to the driving behavior of the driver.
  • 19. The method of claim 1 wherein a frequency of alerts issued determines at least one selected from the group consisting of: an interest rate; a loan premium; and a deductible amount.
  • 20. The method of claim 1, wherein the operations center is remotely located from the vehicle.
  • 21. The method of claim 1, wherein collecting data related to the driving behavior of the driver comprises collecting data related to at least one selected from the group comprising: location of the vehicle; speed of the vehicle; acceleration of the vehicle; deceleration of the vehicle; turn signal usage of the vehicle; and seat belt usage of the vehicle.
  • 22. The method of claim 18, wherein receive data collected by the onboard device further comprises data received in real-time as the driver drives.
US Referenced Citations (257)
Number Name Date Kind
4335370 Scalley et al. Jun 1982 A
4592443 Simon Jun 1986 A
4624578 Green Nov 1986 A
4688026 Scribner et al. Aug 1987 A
4700296 Palmer, Jr. et al. Oct 1987 A
4736294 Gill et al. Apr 1988 A
4738333 Collier et al. Apr 1988 A
4800590 Vaughan Jan 1989 A
5014206 Scribner et al. May 1991 A
5132968 Cephus Jul 1992 A
5228083 Lozowick et al. Jul 1993 A
5359528 Haendel Oct 1994 A
5426415 Prachar et al. Jun 1995 A
5490200 Snyder et al. Feb 1996 A
5495531 Smiedt Feb 1996 A
5510780 Norris et al. Apr 1996 A
5619573 Brinkmeyer et al. Apr 1997 A
5673318 Bellare et al. Sep 1997 A
5708712 Brinkmeyer et al. Jan 1998 A
5775290 Staerzi et al. Jul 1998 A
5797134 McMillan et al. Aug 1998 A
5818725 McNamara et al. Oct 1998 A
5819869 Horton Oct 1998 A
5857024 Nishino Jan 1999 A
5898391 Jefferies et al. Apr 1999 A
5917405 Joao Jun 1999 A
5928291 Jenkins Jul 1999 A
5940812 Tengel et al. Aug 1999 A
5969633 Rosler Oct 1999 A
5970143 Schneier et al. Oct 1999 A
5970481 Westerlage Oct 1999 A
6025774 Forbes Feb 2000 A
6026922 Horton Feb 2000 A
6032258 Godoroja et al. Feb 2000 A
6064970 McMillan et al. May 2000 A
6088143 Bang Jul 2000 A
6130621 Weiss Oct 2000 A
6157317 Walker Dec 2000 A
6185307 Johnson, Jr. Feb 2001 B1
6195648 Simon et al. Feb 2001 B1
6225890 Murphy May 2001 B1
6232874 Murphy May 2001 B1
6233566 Levine et al. May 2001 B1
6249217 Forbes Jun 2001 B1
6249227 Brady et al. Jun 2001 B1
6278936 Jones Aug 2001 B1
6353776 Rohrl et al. Mar 2002 B1
6370649 Angelo et al. Apr 2002 B1
6380848 Weigl et al. Apr 2002 B1
6401204 Euchner et al. Jun 2002 B1
6429773 Schuyler Aug 2002 B1
6489897 Simon Dec 2002 B2
6587739 Abrams et al. Jul 2003 B1
6601175 Arnold et al. Jul 2003 B1
6611201 Bishop et al. Aug 2003 B1
6611686 Smith et al. Aug 2003 B1
6615186 Kolls Sep 2003 B1
6665613 Duvall Dec 2003 B2
6693517 McCarthy et al. Feb 2004 B2
6714859 Jones Mar 2004 B2
6717527 Simon Apr 2004 B2
6741927 Jones May 2004 B2
6804606 Jones Oct 2004 B2
6812829 Flick Nov 2004 B1
6816089 Flick Nov 2004 B2
6816090 Teckchandani et al. Nov 2004 B2
6828692 Simon Dec 2004 B2
6868386 Henderson et al. Mar 2005 B1
6870467 Simon Mar 2005 B2
6873824 Flick Mar 2005 B2
6888495 Flick May 2005 B2
6917853 Chirnomas Jul 2005 B2
6924750 Flick Aug 2005 B2
6950807 Brock Sep 2005 B2
6952645 Jones Oct 2005 B1
6961001 Chang et al. Nov 2005 B1
6972667 Flick Dec 2005 B2
6985583 Brainard et al. Jan 2006 B1
6993658 Engberg et al. Jan 2006 B1
7005960 Flick Feb 2006 B2
7015830 Flick Mar 2006 B2
7020798 Meng et al. Mar 2006 B2
7031826 Flick Apr 2006 B2
7031835 Flick Apr 2006 B2
7039811 Ito May 2006 B2
7053823 Cervinka et al. May 2006 B2
7061137 Flick Jun 2006 B2
7091822 Flick et al. Aug 2006 B2
7103368 Teshima Sep 2006 B2
7123128 Mullet et al. Oct 2006 B2
7124088 Bauer et al. Oct 2006 B2
7133685 Hose et al. Nov 2006 B2
7142089 Yamagishi Nov 2006 B2
7149623 Flick Dec 2006 B2
7205679 Flick Apr 2007 B2
7224083 Flick May 2007 B2
7228417 Roskind Jun 2007 B2
7266507 Simon et al. Sep 2007 B2
7292152 Torkkola et al. Nov 2007 B2
7299890 Mobley Nov 2007 B2
7310618 Libman Dec 2007 B2
7323982 Staton et al. Jan 2008 B2
7327250 Harvey Feb 2008 B2
7379805 Olsen, III et al. May 2008 B2
7389916 Chirnomas Jun 2008 B2
7427924 Ferrone et al. Sep 2008 B2
7542921 Hildreth Jun 2009 B1
7561102 Duvall Jul 2009 B2
7814005 Imrey et al. Oct 2010 B2
7818254 Ma Oct 2010 B1
7823681 Crespo et al. Nov 2010 B2
7873455 Arshad et al. Jan 2011 B2
7877269 Bauer et al. Jan 2011 B2
7904332 Merkley Mar 2011 B1
7930211 Crolley Apr 2011 B2
8018329 Morgan et al. Sep 2011 B2
8086523 Palmer Dec 2011 B1
8095394 Nowak et al. Jan 2012 B2
8140358 Ling et al. Mar 2012 B1
8217772 Morgan et al. Jul 2012 B2
8325025 Morgan et al. Dec 2012 B2
8344894 Szczerba et al. Jan 2013 B2
8370027 Pettersson et al. Feb 2013 B2
8370925 Childress et al. Feb 2013 B2
8510556 Cao et al. Aug 2013 B2
8630768 McClellan et al. Jan 2014 B2
8653956 Berkobin et al. Feb 2014 B2
8754751 Piccoli Jun 2014 B1
8841987 Stanfield et al. Sep 2014 B1
9002536 Hatton Apr 2015 B2
9053516 Stempora Jun 2015 B2
20010034577 Grounds Oct 2001 A1
20010040503 Bishop Nov 2001 A1
20020019055 Brown Feb 2002 A1
20020091473 Gardner Jul 2002 A1
20020099596 Geraghty Jul 2002 A1
20020120371 Leivian et al. Aug 2002 A1
20020120374 Douros et al. Aug 2002 A1
20020193926 Katagishi et al. Dec 2002 A1
20030036823 Mahvi Feb 2003 A1
20030095046 Borugian May 2003 A1
20030101120 Tilton May 2003 A1
20030151501 Teckchandani et al. Aug 2003 A1
20030191583 Uhlmann et al. Oct 2003 A1
20030231550 Macfarlane Dec 2003 A1
20040088345 Zellner et al. May 2004 A1
20040153362 Bauer et al. Aug 2004 A1
20040176978 Simon et al. Sep 2004 A1
20040177034 Simon et al. Sep 2004 A1
20040203974 Seibel et al. Oct 2004 A1
20040204795 Harvey et al. Oct 2004 A1
20040239510 Karsten Dec 2004 A1
20040252027 Torkkola et al. Dec 2004 A1
20050017855 Harvey Jan 2005 A1
20050024203 Wolfe Feb 2005 A1
20050030184 Victor Feb 2005 A1
20050033483 Simon et al. Feb 2005 A1
20050128080 Hall et al. Jun 2005 A1
20050134438 Simon Jun 2005 A1
20050162016 Simon Jul 2005 A1
20050200453 Turner et al. Sep 2005 A1
20050231323 Underdahl Oct 2005 A1
20050270178 Ioli Dec 2005 A1
20060028431 Leong Feb 2006 A1
20060059109 Grimes Mar 2006 A1
20060080599 Dubinsky Apr 2006 A1
20060100944 Reddin et al. May 2006 A1
20060108417 Simon May 2006 A1
20060111822 Simon May 2006 A1
20060122748 Nou Jun 2006 A1
20060136314 Simon Jun 2006 A1
20070010922 Buckley Jan 2007 A1
20070021100 Haave et al. Jan 2007 A1
20070038351 Larschan et al. Feb 2007 A1
20070082614 Mock Apr 2007 A1
20070139189 Helmig Jun 2007 A1
20070146146 Kopf et al. Jun 2007 A1
20070176771 Doyle Aug 2007 A1
20070179692 Smith et al. Aug 2007 A1
20070185728 Schwarz et al. Aug 2007 A1
20070194881 Schwarz et al. Aug 2007 A1
20070222588 Wolfe Sep 2007 A1
20070224939 Jung et al. Sep 2007 A1
20070285207 Bates Dec 2007 A1
20070288271 Klinkhammer Dec 2007 A1
20070299567 Simon et al. Dec 2007 A1
20080042814 Hurwitz et al. Feb 2008 A1
20080109378 Papadimitriou May 2008 A1
20080114541 Shintani et al. May 2008 A1
20080150683 Mikan et al. Jun 2008 A1
20080162034 Breen Jul 2008 A1
20080221743 Schwarz et al. Sep 2008 A1
20080223646 White Sep 2008 A1
20080231446 Cresto Sep 2008 A1
20080243558 Gupte Oct 2008 A1
20080245598 Gratz et al. Oct 2008 A1
20080255722 McClellan Oct 2008 A1
20080294302 Basir Nov 2008 A1
20080301038 Anderson Dec 2008 A1
20090043409 Ota Feb 2009 A1
20090051510 Follmer et al. Feb 2009 A1
20090182216 Roushey, III et al. Jul 2009 A1
20090234770 Simon Sep 2009 A1
20090237249 Bielas Sep 2009 A1
20090248222 McGarry et al. Oct 2009 A1
20090284359 Huang et al. Nov 2009 A1
20090284367 Pfafman et al. Nov 2009 A1
20090295537 Lane et al. Dec 2009 A1
20100030586 Taylor et al. Feb 2010 A1
20100045452 Periwal Feb 2010 A1
20100063850 Daniel Mar 2010 A1
20100075655 Howarter et al. Mar 2010 A1
20100090826 Moran et al. Apr 2010 A1
20100131303 Collopy May 2010 A1
20100148947 Morgan et al. Jun 2010 A1
20100238009 Cook et al. Sep 2010 A1
20100268402 Schwarz et al. Oct 2010 A1
20100312691 Johnson, Jr. Dec 2010 A1
20110040630 Weiss Feb 2011 A1
20110050407 Schoenfeld et al. Mar 2011 A1
20110057800 Sofer Mar 2011 A1
20110084820 Walter et al. Apr 2011 A1
20110148626 Acevedo Jun 2011 A1
20110153143 O'Neil et al. Jun 2011 A1
20110210867 Benedikt Sep 2011 A1
20110270779 Showalter Nov 2011 A1
20120066011 Ichien et al. Mar 2012 A1
20120068858 Fredkin Mar 2012 A1
20120068886 Torres Mar 2012 A1
20120089423 Tamir et al. Apr 2012 A1
20120098678 Rathmacher Apr 2012 A1
20120158356 Prochaska et al. Jun 2012 A1
20120203441 Higgins et al. Aug 2012 A1
20120212353 Fung et al. Aug 2012 A1
20120221216 Chauncey et al. Aug 2012 A1
20130018677 Chevrette Jan 2013 A1
20130074107 Hyde et al. Mar 2013 A1
20130074111 Hyde et al. Mar 2013 A1
20130074112 Hyde et al. Mar 2013 A1
20130074115 Hyde et al. Mar 2013 A1
20130099892 Tucker et al. Apr 2013 A1
20130127617 Baade et al. May 2013 A1
20130138460 Schumann et al. May 2013 A1
20130141252 Ricci Jun 2013 A1
20130144460 Ricci Jun 2013 A1
20130144461 Ricci Jun 2013 A1
20130144469 Ricci Jun 2013 A1
20130144770 Boling et al. Jun 2013 A1
20130144771 Boling et al. Jun 2013 A1
20130144805 Boling Jun 2013 A1
20130204455 Chia Aug 2013 A1
20130338914 Weiss Dec 2013 A1
20140191858 Morgan Jul 2014 A1
20140225724 Rankin et al. Aug 2014 A1
20140358896 Camacho et al. Dec 2014 A1
20160090923 Al Salah Mar 2016 A1
20160371788 Rackley, III Dec 2016 A1
Foreign Referenced Citations (10)
Number Date Country
1557807 Jul 2005 EP
10-2004-0073816 Aug 2004 KR
1020040073816 Aug 2004 KR
9616845 Jun 1996 WO
2007092272 Aug 2007 WO
2007092287 Aug 2007 WO
2010068438 Jun 2010 WO
2010062899 Jun 2010 WO
2012097441 Jul 2012 WO
2012097441 Jul 2012 WO
Non-Patent Literature Citations (34)
Entry
US 5,699,633, 10/1999, Roser (withdrawn)
Schwarz et al. Office Action dated Aug. 21, 2009; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, p. 18.
Schwarz et al., Response to Office Action dated Aug. 21, 2009; filed Jan. 21, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 36 p.
Schwarz et al., Final Office Action dated May 4, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 19 p.
Schwarz et al., RCE and Response to Final Office Action dated May 4, 2010, filed Jul. 12, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 40 p.
Schwarz et al., Office Action dated Oct. 26, 2010; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 16 p.
Schwarz et al., Response to Office Action dated Oct. 26, 2010, filed Feb. 21, 2011; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 27 p.
Schwarz et al., Final Office Action dated Apr. 28, 2011; U.S. Appl. No. 11/349,523, filed Feb. 7, 2006, 17 p.
Schwarz et al., Preliminary Amendment filed Mar. 16, 2007; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 28 p.
Schwarz et al., Office Action dated Jul. 22, 2009; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 22 p.
Schwarz et al., Office Action dated May 14, 2010; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 13 p.
Schwarz et al., Response to Office Action dated May 14, 2010, filed Jul. 12, 2010; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 50 p.
Schwarz et al., Office Action dated Oct. 15, 2010; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 13 p.
Schwarz et al., Response to Office Action dated Oct. 15, 2010 filed Feb. 15, 2011; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 36 p.
Schwarz et al., Final Office Action dated May 26, 2011; U.S. Appl. No. 11/539,292, filed Oct. 6, 2006, 16 p.
Gordon*Howard Associates, Inc., International Search Report and Written Opinion of the International Searching Authority dated Nov. 29, 2007 in PCT Patent Application No. PCT/US07/02816, 6 p.
Gordon*Howard Associates, Inc., International Search Report and Written Opinion of the International Searching Authority dated Dec. 4, 2007 in PCT Patent Application No. PCT/US07/02840, 6 p.
On Time Payment Protection Systems, printed Jan. 2, 2004 from www.ontime-pps.com/how.html.
Aircept Products, printed Jan. 2, 2004 from www.aircept.com/products.html.
How PayTeck Works, printed Jan. 2, 2004 from www.payteck.cc/aboutpayteck.html.
Article: “Pager Lets You Locate Your Car, Unlock and Start It”, published Dec. 10, 1997 in USA Today.
Article: “Electronic Keys Keep Tabs on Late Payers”, published Sep. 22, 1997 in Nonprime Auto News.
Article: “PASSTEC Device Safely Prevents Vehicles from Starting”, published Jul. 19, 1999 in Used Car News.
Payment Clock Disabler advertisement, published, May 18, 1998.
Secure Your Credit & Secure Your Investment (Pay Teck advertisement), printed Jan. 2, 2004 from www.payteck.cc.
iMetrik Company Information, printed Dec. 21, 2006 from imetrik.com.
About C-CHIP Technologies, printed Dec. 21, 2006 from www.c-chip.com.
HI-Tech tools to solve traditional problems, printed Dec. 21, 2006 from www.c-chip.com.
C-CHIP Technologies Products: Credit Chip 100, Credit Chip 100C, Credit Chip 200, printed Dec. 21, 2006 from www.c-chip.com.
The Credit Chip 100, printed Dec. 21, 2006 from www.c-chip.com.
PCT Search Report and Written Opinion, Application No. PCT/2014/010282, mailed May 8, 2014 (11 pages).
EEC-EN0F204RK Panasonic Electronic Components | P14164CT-ND | DigiKey. Web. Accessed Feb. 13, 2013. www.digikey.com/product-detail/en/EEC-EN0F204RK/P14164CT-ND/1937322.
Fogerson, R. et al. “Qualitative Detection of Opiates in Sweat by EIA and GC-MS”. Journal of Analytical Toxicology. Oct. 6, 1997, vol. 21, No. 6, pp. 451-458(8) (Abstract).
De La Torre, R. et al. “Usefulness of Sweat Testing for the Detection of Cannabis Smoke.” 2004 American Association for Clinical Chemistry, Inc. 29th Arnold O. Beckman Conference. Apr. 12-13, 2011. San Diego, CA.
Related Publications (1)
Number Date Country
20140191858 A1 Jul 2014 US