System for capturing passenger and trip data for a vehicle

Information

  • Patent Grant
  • 10997669
  • Patent Number
    10,997,669
  • Date Filed
    Thursday, June 13, 2019
    5 years ago
  • Date Issued
    Tuesday, May 4, 2021
    3 years ago
Abstract
Telematics and external data relating to the real-time driving of a driver of a taxi vehicle may be collected and used to calculate a driving score. A telematics device installed in the taxi vehicle may collect vehicle data, trip data, and passenger data from one or more sensors. A computing device in communication with the telematics device may calculate a driving score for the taxi vehicle during a trip based on a type of vehicle, a type of trip, a number of miles driven during the trip, a duration of the trip, a number of passengers in the taxi vehicle during the trip, and a type of the passengers in the taxi vehicle during the trip. As one example, the driving score may be provided to an employer of a driver of the taxi vehicle.
Description
TECHNICAL FIELD

Aspects of the disclosure generally relate to the calculation and utilization of a driving score. In particular, various aspects of the disclosure include a framework for using telematics to calculate and utilize a driving score.


BACKGROUND

Telematics may be described as use of technology to communicate information from one location to another. Telematics has been used for various applications, including for the exchange of information with electronic sensors. As telematics technology has progressed, various communication methodologies have been incorporated into automobiles and other types of vehicles.


One example of telematics systems currently in use in automobiles are on-board diagnostics (OBD) systems. From early versions of OBD systems that included crude implementations of control for features such as fuel injection to more sophisticated and standardized OBD-I and OBD-II units, these units have served as an electronic gateway into the health of a vehicle. These systems have allowed users to monitor a wide variety of engine sensors and systems, including emissions control, coolant temperature, engine RPM, vehicle speed, timing advance, throttle position, and oxygen sensing, among other things. Moreover, handheld units, mobile devices, personal computers, data loggers, and other devices may be connected to the OBD systems to serve as the interface for displaying data outputted by the OBD system. Data obtained from OBD systems has been used for a variety of purposes, including maintenance, diagnosis, and analysis.


SUMMARY OF THE INVENTION

Aspects of the disclosure relate to methods and systems for calculating and utilizing a driving score. In at least one embodiment, a plurality of real-time driving data or inputs is captured by a telematics device. The real-time driving inputs may include one or more of one or more of speed, acceleration, braking, steering, user of turn signals, user of seat belts, use of radio, use of a phone, location, miles driven, type of trip, engine status, oil level, tire pressure, number of passengers, and lane departures. One or more driving conditions may be received. The driving conditions may be one or more of weather, road conditions, type of road, and time of day. A processor may calculate the driving score. The driving score may be based at least in part on the plurality of real-time driving inputs and the one or more driving conditions. The calculated driving score may be sent to one or more devices or entities, such as a portable device.


In at least one embodiment, the driving score is validated by a validating agency. The validated driving score may be sent to one or more third parties. The third parties may be one or more of a financial institution, an insurance company, a credit agency, a department of motor vehicles. The third party may utilize the driving score in aspects of its business. The driving score may be sent to and stored on a device. The device may be a computing device or may be a portable device, such as a key fob or a mobile telephone.


In at least one embodiment, the driving score is displayed to the driver. The driving score may be displayed on a device belonging to the driver, such as a key fob or a mobile telephone. Alternatively, the driving score may be displayed on an item within a vehicle, such as a windshield or rearview mirror. The driving score may be a numerical, alphabetical, or graphical value.


In at least one embodiment, a driving report is generated. The driving report may be sent to one or more individuals and/or entities. For example, the driving report may be sent to an insurance company or the driver. The driving report may contain information relating to the real-time driving inputs collected and the driving conditions received. The driving report may also include information relating to the driving score and the habits of the driver. The driving report may also include recommendations relating to the driver's habits and or the effects of the driver's habits.





BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and is not limited in the accompanying figures in which:



FIG. 1 shows a system involving an illustrative device through which various aspects of the disclosure may be implemented.



FIG. 2 is an illustrative block diagram of a system that may be used to implement the processes and functions of certain aspects of the present disclosure.



FIG. 3 illustrates a method for calculating and utilizing a driving score in accordance with certain aspects of the disclosure.





DETAILED DESCRIPTION OF THE INVENTION

Aspects of the disclosure relate to methods, computer readable media, and apparatuses for using telematics data and external data to calculate and utilize a driving score for a driver of a vehicle.



FIG. 1 illustrates a block diagram of a telematics device 101 (e.g., a computing device) in communication system 100 that may be used according to an illustrative embodiment of the disclosure. The device 101 may have a processor 103 for controlling overall operation of the telematics device 101 and its associated components, including RAM 105, ROM 107, input/output module 109, and memory 115. In certain embodiments, device 101 physically resides in an item (e.g., a vehicle, a mobile telephone, etc.) and receives information from sensors or other measurement devices incorporated into the item, and in other embodiments, device 101 may communicate from a remote location to sensors within an item.


I/O 109 may include a microphone, keypad, touch screen, and/or stylus through which a user of device 101 may provide input, and may also include one or more of a speaker for providing audio output and a video display device for providing textual, audiovisual and/or graphical output. Software may be stored within memory 115 and/or storage to provide instructions to processor 103 for enabling device 101 to perform various functions. For example, memory 115 may store software used by the device 101, such as an operating system 117, application programs 119, and an associated database 121. Processor 103 and its associated components may allow the device 101 to run a series of computer-readable instructions to read, store, and analyze various details about an item's operating parameters. For instance, the device 101 may capture data related to the real-time driving data of a driver of a vehicle. The device 101 may capture information related multiple parameters simultaneously and/or in real-time.


The device 101 may operate in a networked environment supporting connections to one or more remote computers, such as terminals 141 and 151. The terminals 141 and 151 may be personal computers or servers that include many or all of the elements described above relative to the device 101. Alternatively, terminal 141 and/or 151 may be storage servers for storing data associated with device 101. The network connections depicted in FIG. 1 includes a local area network (LAN) 125 and a wide area network (WAN) 129, but may also include other networks. When used in a LAN networking environment, the device 101 is connected to the LAN 125 through a network interface or adapter 123. When used in a WAN networking environment, the device 101 may include a modem 127 or other means for establishing communications over the WAN 129, such as the Internet 131. It will be appreciated that the network connections shown are illustrative and other means of establishing a communications link between the computers may be used. For example, the device 101 may communicate wirelessly with other computing systems and receivers. The existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed.


Additionally, an application program 119 used by device 101 according to an illustrative embodiment of the disclosure may include computer executable instructions for invoking functionality related to capturing data associated with an item's operational state through sensors present on or around the item, processing this data, and/or storing the data locally and/or remotely. Device 101 and/or terminals 141 or 151 may also be mobile terminals including various other components, such as a battery, speaker, and antennas (not shown).


The disclosure is operational with numerous other general purpose and/or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the disclosure include, but are not limited to, personal computers, server computers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable user electronics, network PCs, minicomputers, mainframe computers, mobile telephones, smart phones, and distributed computing environments that include any of the above systems or devices, and the like.


Aspects of the disclosure may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.


Referring to FIG. 2, an illustrative system 200 for implementing methods according to the present disclosure is shown. As illustrated, system 200 may include a telematics device 101, a computing device 201, and one or more input/output devices 202. Computing device 201 may be a computing device for processing data generated by telematics device 101 and calculating a driving score based on the processed data. Computing device 101 may receive data from a variety of input/output devices 202, including vehicle telematics data, smartphone telematics data, data from service providers, and/or demographic/descriptive data from third parties 203. Computing device 201 may reside either remotely or local to an item in which device 101 resides. If computing device 201 resides local to the item along with telematics device 101, computing device 201 may be integrated with telematics device 101.


Computing device 201 may possess many of the same hardware/software components as telematics device 101 shown in FIG. 1. For instance, the computing device 201 may be used by a program manager and/or insurance provider associated with the item which accompanies telematics device 101 to apply various business logic rules for determining a driving score for one or more drivers. The program manager may be a separate entity that may oversee implementation and validation of a driving score program. Alternatively, the program manager may be one of the service providers already involved in the driving score program, including an insurance provider, original equipment manufacturer (OEM), maintenance provider, or other service provider. The program manager may be an entity that enables data exchange and transaction processing between all parties involved in a driving score program.


The telematics device 101 may capture or receive any type of data relating to real-time driving. For example, the telematics device 101 may collect data relating to the driver's speed, acceleration of a vehicle, braking of a vehicle and/or anti-lock braking system application, and/or steering of a vehicle. The telematics device 101 may collect data relating to the vehicle, such as airbag deployment, anti-theft system disablement, use of headlights, whether the back-up lights turn on, whether the brake lights are on, door opening, door locking, use of cruise control, use of hazard lights, use of wipers, horn application, whether turn signals are used, whether seat belts are worn, whether a driver plays the radio, and/or talks on a telephone. The telematics device 101 may also capture data relating to the observance of traffic signals and signs. The telematics device 101 may also collect data relating to other vehicles, such as the presence and distance of vehicles on the side, front or back of the vehicle being monitored.


Additionally, the telematics device 101 may capture data relating to vehicle maintenance, such as the engine status, oil level, engine coolant temperature, odometer reading, the level of fuel in a tank, engine revolutions per minute (RPM), and/or tire pressure. The type of vehicle driven may also be recorded. The type of vehicle driven may be determined from the vehicle itself or by accessing data from an entity, such as an insurance policy. If a driver has more than one vehicle available to drive, the choice of vehicle may be collected. The choice of vehicle may be determined by accessing data that lists the available vehicles, such as an insurance policy, and/or data from the vehicle itself.


The telematics device 101 may be configured to collect data regarding the passengers of the vehicle. For example, the number of passengers or types of passengers (e.g. adults, children, teenagers, pets, etc.) may be collected. The driver's route choice, whether the driver follows a given route, type of trip (e.g. commute, errand, new route, etc.) or whether the driver stays within the lane may be collected. In at least one embodiment, the telematics device 101 is configured to communicate with sensors and/or one or more cameras in a vehicle that determine whether the vehicle stays within a lane or strays into other lanes. The telematics device 101 may be configured to collect data from a vehicle when the vehicle prevents the driver from performing an action (e.g. changing lanes when a car is in a new lane, speeding, etc.)


The telematics device 101 may also be configured to collect data relating to a driver's movements or the condition of a driver. For example, the telematics device 101 may include or communicate with sensors that monitor a driver's movements, such as the driver's eye position and/or head position, etc. Additionally, the telematics device 101 may collect the condition of a driver, such as fatigue or intoxication. The condition of the driver may be determined through the movements of the driver or through sensors, for example, sensors that detect the content of alcohol in the air or blood alcohol content of the driver, such as a breathalyzer.


The telematics device 101 may collect or receive the real-time data from any type of input or output device 202. For example, the telematics device 101 may receive data from a mobile telephone, a Global Positioning System (GPS), sensors positioned inside a vehicle, or sensors or devices remote from the vehicle. The sensors may include any type of sensors, such as body sensors and electrical sensors. The telematics device 101 may also be configured to send the data or driving score to one or more output devices 202. For example, the telematics device 101 may send the driving score to a mobile telephone or a key fob. Additionally or alternatively, the telematics device 101 may be configured to display the driving score within the vehicle. For example, the telematics device 101 may project the score on a vehicle's windshield or on the rear view mirror.


The driving score may be stored by the computing device 201 or may be sent to a separate processor or server for storing. Alternatively, the driving score may be stored in the memory of an input/output device 202, such as a key fob or a mobile telephone. In at least one embodiment, the driving score may be stored in a portable device and transferred from the portable device to another device. For example, the driving score may be stored in a driver's mobile telephone and transferred to a device, such as a computer, at the department of motor vehicles.


In at least one embodiment, the telematics device 101 can determine the driver of the vehicle. The driver may be determined by any suitable means. For example, the driving behavior of the driver may determine the driver, each driver may have a specific key fob to start the vehicle, or sensors within the telematics device 101 or vehicle may determine the driver. This may be done in any suitable manner. For example, the weight of the driver may be sensed. The telematics device 101 may also identify the driver through voice recognition, codes, fingerprint or retinal recognition, etc.


The telematics device 101 or computing device 201 may also capture or receive external data such as the location of the vehicle, weather, the traffic, the type of road, barometric pressure, and/or the time of day the vehicle is being driven. The external data may be collected from components within a vehicle or received from a third party 203. The number of miles driven, number of miles driven at certain times of the day, the number of miles per trip, the duration of the trip, the number of trips over a certain time, such as a day, month, or week, and/or the time of day the vehicle is driven may also be collected and/or received. In at least one embodiment, the driver's score may be generated and assigned to an autonomous car based on the autonomous car's driving performance.


The computing device 201 may calculate the driving score in any suitable manner. For example, the computing device 201 may apply weights to any of the collected or received data described above. The driving score may take into account data relating to the driver. For example, the driving score may take into account the driver's age, the driver's medical history and/or the driver's vision. The driving score may increase or decrease based on the real-time data collected by the telematics device 101 and the external data received. For example, if a driver consistently abides by the posted speed limits, wears a seatbelt, and keeps the vehicle in good repair, the driver's score may be increased. Alternatively, if the driver regularly speeds, does not repair the vehicle, and regularly brakes hard, the driver's score may be negatively affected.


The driving score may be any type of value, such as a numerical or alphabetical value. For example, the driving score may be a number between 0 and 800, similar to a credit score, or a score between 0 and 1.0, a letter grade, such as A, B, C, D, or F, with plus/minus gradients.


In at least one embodiment, a validating agency may validate the driving score calculated by the computing device 201. The driving score may be validated by verifying the accuracy of the collected real-time data inputs or external data. Additionally, the driving score may be validated by verifying the calculation of the driving score and the output, i.e. value of the driving score. In at least one embodiment, the validating agency may be an insurance company. The validating agency may standardize the driving scores and/or rules and algorithms for calculating the driving score and may provide the driving scores to other agencies or entities. The validating agency may charge a requesting agency or entity for receiving driving scores. The requesting agencies or entities may be charged on a usage basis or subscription basis.


The telematics device 101 may include an alert device that provides an audible or visual alert. For example, the telematics device 101 may send a text or SMS message to a mobile phone or may send email to a driver to give the driver feedback about the driving. The alert may be sent at any time. For example, the alert may be sent in real-time, e.g. at the time of an event. Alternatively, a driving report may be generated. The driving report may be sent to one or more third parties, such as the driver, an insurance agency, a credit agency, and/or a governmental agency. The driving report may be sent at any time. In one embodiment, the driving report is sent at a predetermined frequency, for example monthly or weekly. The audible alert may be a tone or a voice that beeps when a specific event happens, such as a driver exceeding a speed limit or a voice that instructs the driver that the vehicle is travelling above the speed limit. A driver may be alerted, in the driving report or through the audible or visual alert of his or her driving score, his or her driving habits, and/or the effect of the driver's habits. The effect of the habit may include any type of information, such as information relating to the damage to or wear upon a vehicle or the effect of the driver's habits on the driving score. For example, the driver may be alerted that frequent hard braking is negatively affecting his/her driving score and/or may cause excessive wear to the brake pads.


The driving score may be utilized in any suitable way. For example, a driving score may be used to rent a car. Generally, a driver must be over the age of 25 to rent a car. However, car rental agencies may use the driving score to remove the age requirement for renting a car. For example, a car rental agency may allow anyone with a driving score above a certain threshold to rent a car. Alternatively, or additionally, the driving score may be used by the car rental agencies to determine a rental rate or an insurance rate for a rental car.


The driving score may be used by employers that require an employee to drive a vehicle (e.g. a taxi, trucker, delivery person, etc.). The employer may submit a request for a driver's driving score to the entity that collects and/or verifies the driving score, such as an insurance agency.


The driving score may be used by government agencies, such as the department of motor vehicles (DMV). The DMV may use the driving score in lieu of a driver taking a driving test. In this embodiment, the DMV may require a driver to log a specific number of hours driving and/or reach a threshold driving score. If the DMV's requirements are reached, the DMV may issue a license or a probationary license to a driver. The DMV may also require a driver that has a license to maintain a driving score above a threshold to keep his/her license. The driving score may be checked periodically by the DMV to determine whether the driver's score is above the threshold limit. If the driver's score falls below a threshold limit, the driver's license may be revoked, the driver may receive a ticket, and/or or the driver may be required to attend driving classes or driving training.


The driving score may be used and accepted by all insurance companies. The insurance companies may use the driving score to determine an appropriate insurance policy or an appropriate rate for an insurance policy of a customer. In at least one embodiment, the driving score may be used by a customer to evaluate and select the best insurance policy from a plurality of insurance companies.


The driving score may be sent to credit agencies and used in establishing or altering a credit score. The driving score may also be used in credit card, mortgage, lease, loan, and/or school applications for individuals who have little to no credit. For example, the driving score may be used as a predictor for determining whether the applicant will fulfill his or her obligations. As described in U.S. Pat. No. 8,086,523, which is incorporated by reference herein in its entirety, a user's credit score or may be generated by a statistical credit-scoring model, which is used to objectively evaluate information that pertains to making a credit or credit-related decision. The statistical model may consider conventional credit risk information (e.g., a user's FICO score, payment history, length of credit history, amount owed, types of credit used, new credit, etc.) as well as a driving score to calculate credit score.


The driving score may be used to prevent individuals from driving in certain areas or drivers may be charged for entering certain areas. Additionally, the driving score may be used by an agency, such as a governmental agency, to tax a driver. The tax may relate to gas taxes, taxes for using a certain road, and/or taxes for driving at a certain time or using a certain road at a specific time.


The steps that follow may be implemented by one or more of the components in FIGS. 1 and 2 and/or other components, including other computing devices. FIG. 3 illustrates a method 300 of calculating and utilizing a driving score according to one or more aspects of the invention. As illustrated in step 301, a telematics device 101 captures real-time driving inputs for one or more drivers, as discussed in detail above. In step 302, external or driving conditions may be captured or received, as discussed above. The external or driving conditions may be provided by a third party, may be determined from databases or files, and/or may be captured by the telematics device 101.


In step 303, the computing device 201 calculates or generates a driving score for one or more drivers, as discussed in detail above. The driving score may be based at least in part on the real-time driving inputs and the external or driving conditions captured and/or received in steps 301 and 302. In step 304, the calculated driving score may be validated. The driving score may be validated by a validating entity or by the entity that oversees the calculation/generation of the driving score. The driving score may be validated by verifying the inputs and outputs of the calculation. The driving score may be any numerical, alphabetical, or graphical value.


In step 305, the driving score may be sent to an individual and/or an entity. For example, the driving score may be sent to a computing device, an input/output device 202, such as a portable device, the driver, or an insurance or governmental agency. The driving score may also be displayed, as illustrated in step 306. The driving score may be displayed on any type of device. For example, the driving score may be displayed on a computing device, mobile telephone, key fob, or may be displayed on items within the vehicle, such as the windshield or rearview mirror. As illustrated in step 307, the driving score may be stored. The driving score may be stored on any type of device including memory. For example, the computing device 201 and/or input/output devices 202 may store in the driving score. In at least one embodiment, the driving score is stored in the non-volatile memory of a key fob for a vehicle.


The computing device 201 may generate a driving report for one or more drivers, as illustrated in step 308. The driving report may contain any type of information. For example, the driving report may contain the driver's name, the vehicle(s) driven, the driving score, the driving habits of a driver, and/or the effect of the driver's driving habits on the vehicle. Additionally or alternatively, the driving report may contain information regarding the calculation of the driving score and or the potential changes to the driving score based on the information within the driving report. As an example, the driving report may contain information such as the name and an identifier of the driver, such as a driver's license number, the vehicle description, the driver's habits, such as excessive braking and routine speeding, and the effects of the excessive braking to the vehicle and the potential decrease to a driver's score because of the excessive braking and routine speeding. As illustrated in step 309, the driving report may be sent to individuals or entities. For example the driving report may be sent to the driver or may be sent to an insurance agency or credit agency, as discussed above.


Aspects of the disclosure have been described in terms of illustrative embodiments thereof. Numerous other embodiments, modifications and variations will occur to persons of ordinary skill in the art from a review of this disclosure. For example, one of ordinary skill in the art will appreciate that the steps illustrated in the illustrative figures may be performed in other than the recited order, and that one or more steps illustrated may be optional in accordance with aspects of the disclosure. Additionally, those skilled in the art will appreciate that there are numerous variations and permutations of the above-described systems and techniques that fall within the spirit and scope of the invention as set forth in the appended claims.

Claims
  • 1. A system comprising: a telematics device installed in a vehicle, the telematics device comprising: one or more sensors;an alert device;a first processor; andfirst memory storing instructions that, when executed by the first processor, cause the telematics device to: capture an indication of the vehicle;capture, from the one or more sensors, trip data comprising a type of a trip taken by the vehicle and a number of miles driven during the trip; andcapture, from the one or more sensors, passenger data; anda computing device communicatively coupled to the telematics device over a network, the computing device comprising:a second processor; andsecond memory storing second instructions that, when executed by the second processor, cause the computing device to: receive the indication of the vehicle, the trip data, and the passenger data from the telematics device;determine, based on comparing the indication of the vehicle with a plurality of available vehicles, an identity of the vehicle;generate a driving score for the vehicle based, at least in part, on the identity of the vehicle, the type of the trip, the number of miles driven during the trip, and the passenger data; andprovide the driving score, wherein providing the driving score comprises: providing, to a driver of the vehicle and via the alert device, an audible or visual alert of the driving score; andbased on receiving a request from an entity different than the driver of the vehicle, provide, to at least one device associated with the entity, the driving score.
  • 2. The system of claim 1, wherein the entity is an owner of the vehicle.
  • 3. The system of claim 1, wherein the passenger data further comprises a number of passengers in the vehicle during the trip, and wherein the computing device generates the driving score for the vehicle further based, at least in part, on the number of passengers in the vehicle.
  • 4. The system of claim 1, wherein the trip data further comprises a duration of the trip, and wherein the computing device generates the driving score for the vehicle further based, at least in part, on the duration of the trip.
  • 5. The system of claim 1, wherein the entity determines an insurance policy for the vehicle based, at least in part, on the driving score.
  • 6. The system of claim 1, wherein the entity determines an insurance rate for an insurance policy associated with the vehicle based, at least in part, on the driving score.
  • 7. The system of claim 1, wherein the entity manages the plurality of available vehicles, and wherein the plurality of available vehicles comprises the vehicle.
  • 8. The system of claim 1, wherein the computing device generates the driving score for the vehicle further based, at least in part, on a type of the vehicle.
  • 9. A method comprising: capturing, by a telematics device installed in a vehicle, an indication of the vehicle;capturing, by the telematics device and from one or more sensors of the telematics device, trip data comprising a type of a trip taken by the vehicle and a number of miles driven during the trip;capturing, by the telematics device and from the one or more sensors of the telematics device, passenger data;receiving, by a computing device communicatively coupled to the telematics device over a network and from the telematics device: the indication of the vehicle;the trip data; andthe passenger data;determining, by the computing device and based on comparing the indication of the vehicle with a plurality of available vehicles, an identity of the vehicle;generating, by the computing device, a driving score for the vehicle based, at least in part, on the identity of the vehicle, the type of the trip, the number of miles driven during the trip, and the passenger data; andproviding, by the computing device, the driving score, wherein providing the driving score comprises: providing, by the computing device and to a driver of the vehicle and via an alert device of the telematics device, an audible or visual alert of the driving score; andbased on receiving a request from an entity different than the driver of the vehicle, providing, by the computing device and to at least one device associated with the entity, the driving score.
  • 10. The method of claim 9, wherein the entity owns the vehicle.
  • 11. The method of claim 9, wherein the passenger data comprises a number of passengers in the vehicle during the trip, and wherein generating the driving score for the vehicle is further based, at least in part, on the number of passengers in the vehicle.
  • 12. The method of claim 9, wherein the trip data further comprises a duration of the trip, and wherein generating the driving score is further based, at least in part, on the duration of the trip.
  • 13. The method of claim 9, wherein the entity determines an insurance policy for the vehicle based, at least in part, on the driving score.
  • 14. The method of claim 9, wherein the entity determines an insurance rate for an insurance policy associated with the vehicle based, at least in part, on the driving score.
  • 15. The method of claim 9, wherein the entity manages the plurality of available vehicles.
  • 16. An apparatus comprising: one or more processors; andmemory storing instructions that, when executed by the one or more processors, cause the one or more processors to: capture, via a telematics device installed in a vehicle, an indication of the vehicle;capture, via one or more sensors of the telematics device, trip data comprising a type of a trip taken by the vehicle and a number of miles driven during the trip;capture, via the one or more sensors of the telematics device, passenger data;receive: the indication of the vehicle;the trip data; andthe passenger data;determine, based on comparing the indication of the vehicle with a plurality of available vehicles, an identity of the vehicle;generate a driving score for the vehicle based, at least in part, on the identity of the vehicle, the type of the trip, the number of miles driven during the trip, and the passenger data; andprovide the driving score, wherein providing the driving score comprises: providing, to a driver of the vehicle and via an alert device of the telematics device, an audible or visual alert of the driving score; andbased on receiving a request from an entity different than the driver of the vehicle, providing, to at least one device associated with the entity, the driving score.
  • 17. The apparatus of claim 16, wherein the entity owns the vehicle.
  • 18. The apparatus of claim 16, wherein the passenger data comprises a number of passengers in the vehicle during the trip, and wherein the instructions, when executed by the one or more processors, cause the apparatus to generate the driving score based, at least in part, on the number of passengers in the vehicle.
  • 19. The apparatus of claim 16, wherein the trip data further comprises a duration of the trip, and wherein the instructions, when executed by the one or more processors, cause the apparatus to generate the driving score based, at least in part, on the duration of the trip.
  • 20. The apparatus of claim 16, wherein the entity determines an insurance policy for the vehicle based, at least in part, on the driving score.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/160,208 which is a continuation of U.S. patent application Ser. No. 13/564,524, entitled “Calculation and Utilization of a Driving Score,” filed Aug. 1, 2012, the disclosure of which is incorporated herein by reference.

US Referenced Citations (205)
Number Name Date Kind
5467388 Redd, Jr. et al. Nov 1995 A
5499182 Ousborne Mar 1996 A
5619568 Miller Apr 1997 A
6175803 Chowanic et al. Jan 2001 B1
6233445 Boltz et al. May 2001 B1
6351698 Kubota et al. Feb 2002 B1
6629029 Giles Sep 2003 B1
6868386 Henderson et al. Mar 2005 B1
7167787 Bastian et al. Jan 2007 B2
7292152 Torkkola et al. Nov 2007 B2
7356516 Richey et al. Apr 2008 B2
7535344 Obradovich May 2009 B2
7565230 Gardner et al. Jul 2009 B2
7657441 Richey et al. Feb 2010 B2
7659827 Gunderson et al. Feb 2010 B2
7742792 Matsui Jun 2010 B2
8090598 Bauer et al. Jan 2012 B2
8180655 Hopkins, III May 2012 B1
8270933 Riemer et al. Sep 2012 B2
8275348 Yen et al. Sep 2012 B2
8311858 Everett et al. Nov 2012 B2
8314708 Gunderson et al. Nov 2012 B2
8332242 Medina, III Dec 2012 B1
8355818 Nielsen et al. Jan 2013 B2
8489433 Altieri et al. Jul 2013 B2
8506512 Aklog et al. Aug 2013 B2
8508353 Cook et al. Aug 2013 B2
8538687 Plocher et al. Sep 2013 B2
8566126 Hopkins, III Oct 2013 B1
8606512 Bogovich et al. Dec 2013 B1
8612139 Wang et al. Dec 2013 B2
8620575 Vogt et al. Dec 2013 B2
8626444 Li et al. Jan 2014 B2
8655965 McWithey et al. Feb 2014 B2
8682699 Collins et al. Mar 2014 B2
8686872 Szczerba et al. Apr 2014 B2
8712429 Nagorniak Apr 2014 B2
8731768 Fernandes et al. May 2014 B2
8744492 Kuo Jun 2014 B2
8805707 Schumann, Jr. et al. Aug 2014 B2
8810425 Hyde et al. Aug 2014 B2
8824997 Gehlen et al. Sep 2014 B2
8860564 Rubin et al. Oct 2014 B2
8930229 Bowne et al. Jan 2015 B2
8971927 Zhou et al. Mar 2015 B2
8996234 Tamari et al. Mar 2015 B1
9020749 Aso et al. Apr 2015 B2
9020751 Bogovich et al. Apr 2015 B1
9066210 Kalita et al. Jun 2015 B2
9082072 Wedding, Jr. et al. Jul 2015 B1
9104535 Brinkmann et al. Aug 2015 B1
9112937 Warden et al. Aug 2015 B1
9142142 Nath et al. Sep 2015 B2
9150154 Miller et al. Oct 2015 B2
9177427 Briggs Nov 2015 B1
9207675 Walser et al. Dec 2015 B1
9317980 Cook et al. Apr 2016 B2
9519670 Stanek et al. Dec 2016 B2
9574888 Hu et al. Feb 2017 B1
9805601 Fields et al. Oct 2017 B1
9851214 Chintakindi Dec 2017 B1
10019904 Chan Jul 2018 B1
20020046064 Maury et al. Apr 2002 A1
20020059084 Wahlbin et al. May 2002 A1
20040210353 Rice Oct 2004 A1
20040214615 Entenmann et al. Oct 2004 A1
20050060069 Breed et al. Mar 2005 A1
20050086227 Sullivan et al. Apr 2005 A1
20060053038 Warren et al. Mar 2006 A1
20060200008 Moore-Ede Sep 2006 A1
20060247852 Kortge et al. Nov 2006 A1
20060253307 Warren et al. Nov 2006 A1
20070027726 Warren et al. Feb 2007 A1
20070080816 Haque et al. Apr 2007 A1
20070136107 Maguire et al. Jun 2007 A1
20070226014 Alemayehu et al. Sep 2007 A1
20070268158 Gunderson et al. Nov 2007 A1
20080016145 Takase et al. Jan 2008 A1
20080059351 Richey et al. Mar 2008 A1
20080065427 Helitzer et al. Mar 2008 A1
20080120175 Doering May 2008 A1
20080243321 Walser et al. Oct 2008 A1
20080243558 Gupte Oct 2008 A1
20080255722 McClellan et al. Oct 2008 A1
20080255888 Berkobin et al. Oct 2008 A1
20080262670 McClellan et al. Oct 2008 A1
20080270519 Ekdahl et al. Oct 2008 A1
20080294060 Haro et al. Nov 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
20090132294 Haines May 2009 A1
20100030582 Rippel et al. Feb 2010 A1
20100030592 Evans et al. Feb 2010 A1
20100042314 Vogt et al. Feb 2010 A1
20100057358 Winer et al. Mar 2010 A1
20100063850 Daniel Mar 2010 A1
20100087984 Joseph Apr 2010 A1
20100131303 Collopy et al. May 2010 A1
20100131304 Collopy et al. May 2010 A1
20100157061 Katsman et al. Jun 2010 A1
20100174566 Helitzer et al. Jul 2010 A1
20100205012 McClellan Aug 2010 A1
20100211259 McClellan Aug 2010 A1
20100238009 Cook et al. Sep 2010 A1
20100250021 Cook et al. Sep 2010 A1
20100292886 Szczerba et al. Nov 2010 A1
20100323673 Etram et al. Dec 2010 A1
20110009107 Guba et al. Jan 2011 A1
20110039581 Cai et al. Feb 2011 A1
20110054716 Stahlin et al. Mar 2011 A1
20110090221 Ren Apr 2011 A1
20110092159 Park et al. Apr 2011 A1
20110106370 Duddle et al. May 2011 A1
20110144909 Ren et al. Jun 2011 A1
20110161116 Peak et al. Jun 2011 A1
20110196571 Foladare et al. Aug 2011 A1
20110205043 Fujiki et al. Aug 2011 A1
20110213628 Peak et al. Sep 2011 A1
20110219080 McWithey et al. Sep 2011 A1
20110269441 Silver Nov 2011 A1
20110320492 Inghelbrecht Dec 2011 A1
20120004933 Foladare et al. Jan 2012 A1
20120010906 Foladare et al. Jan 2012 A1
20120021386 Anderson et al. Jan 2012 A1
20120072243 Collins et al. Mar 2012 A1
20120072244 Collins et al. Mar 2012 A1
20120083287 Casto et al. Apr 2012 A1
20120089423 Tamir et al. Apr 2012 A1
20120095646 Ghazarian Apr 2012 A1
20120101855 Collins et al. Apr 2012 A1
20120109692 Collins et al. May 2012 A1
20120123806 Schumann, Jr. et al. May 2012 A1
20120166229 Collins et al. Jun 2012 A1
20120197669 Kote et al. Aug 2012 A1
20120209632 Kaminski et al. Aug 2012 A1
20120226421 Kote et al. Sep 2012 A1
20120246192 Kenyon Sep 2012 A1
20120253586 Sakakibara Oct 2012 A1
20120289214 Hynes et al. Nov 2012 A1
20120303392 Depura Nov 2012 A1
20120311416 Richter et al. Dec 2012 A1
20120316933 Pentland et al. Dec 2012 A1
20130006674 Bowne et al. Jan 2013 A1
20130006675 Bowne et al. Jan 2013 A1
20130006715 Warkentin et al. Jan 2013 A1
20130024060 Sukkarie et al. Jan 2013 A1
20130046559 Coleman et al. Feb 2013 A1
20130073321 Hofmann et al. Mar 2013 A1
20130078963 Prasad et al. Mar 2013 A1
20130090803 Stahlin et al. Apr 2013 A1
20130110310 Young May 2013 A1
20130124082 Cho May 2013 A1
20130137404 Kuo May 2013 A1
20130151288 Bowne et al. Jun 2013 A1
20130157640 Aycock Jun 2013 A1
20130166325 Ganapathy et al. Jun 2013 A1
20130217331 Manente Aug 2013 A1
20130238233 Kim et al. Sep 2013 A1
20130297097 Fischer et al. Nov 2013 A1
20130304514 Hyde et al. Nov 2013 A1
20130317736 Fernandes et al. Nov 2013 A1
20130344856 Silver Dec 2013 A1
20140019170 Coleman et al. Jan 2014 A1
20140067434 Bourne et al. Mar 2014 A1
20140074402 Hassib et al. Mar 2014 A1
20140080100 Phelan et al. Mar 2014 A1
20140167946 Armitage et al. Jun 2014 A1
20140180723 Cote et al. Jun 2014 A1
20140207497 Collins et al. Jul 2014 A1
20140222280 Salomonsson et al. Aug 2014 A1
20140226010 Molin et al. Aug 2014 A1
20140257869 Binion et al. Sep 2014 A1
20140257871 Christensen et al. Sep 2014 A1
20140267263 Beckwith et al. Sep 2014 A1
20140267627 Freeman et al. Sep 2014 A1
20140268353 Fujimura et al. Sep 2014 A1
20140277939 Ren et al. Sep 2014 A1
20140278574 Barber Sep 2014 A1
20140322676 Raman Oct 2014 A1
20140336866 Kloeden et al. Nov 2014 A1
20140350970 Schumann, Jr. et al. Nov 2014 A1
20140358840 Tadic et al. Dec 2014 A1
20150006207 Jarvis et al. Jan 2015 A1
20150056973 Efrati Feb 2015 A1
20150066360 Kirsch Mar 2015 A1
20150112545 Binion et al. Apr 2015 A1
20150112730 Binion et al. Apr 2015 A1
20150112800 Binion et al. Apr 2015 A1
20150172450 Singhal Jun 2015 A1
20150187016 Adams et al. Jul 2015 A1
20150187019 Fernandes et al. Jul 2015 A1
20150241226 Engelman et al. Aug 2015 A1
20160039426 Ricci Feb 2016 A1
20160047666 Fuchs Feb 2016 A1
20160050315 Malhotra et al. Feb 2016 A1
20160073240 Helm Mar 2016 A1
20160134744 de la Fuente Sanchez May 2016 A1
20160182707 Gabel Jun 2016 A1
20160231278 Goroshevskiy et al. Aug 2016 A1
20170122989 Ho May 2017 A1
20180158334 Perez Barrera et al. Jun 2018 A1
20180162410 Skillsater et al. Jun 2018 A1
20180362026 Heimberger et al. Dec 2018 A1
Foreign Referenced Citations (7)
Number Date Country
0700009 Mar 1996 EP
2937844 Oct 2015 EP
2015169472 Sep 2015 JP
2007008924 Jan 2007 WO
2008001125 Jan 2008 WO
2010011806 Jan 2010 WO
2011004372 Jan 2011 WO
Non-Patent Literature Citations (95)
Entry
“Warn me now or inform me later: Drivers' acceptance of real-time and post-drive distraction mitigation systems,” by Shannon C. Roberts, Mahtab Ghazizadeh and John D. Lee. International Journal of Human-Computer Studies 70 (2012). Available online at www.sciencedirect.com (Year: 2012).
Nov. 13, 2019—U.S. Final Office Action—U.S. Appl. No. 15/052,291.
Sep. 30, 2019—(CA) Notice of Allowance—Application No. 2,999,498.
Dec. 19, 2019—(IN) Office Action—Application No. 201644037045.
Dec. 23, 2019—U.S. Notice of Allowance—U.S. Appl. No. 15/268,750.
Feb. 7, 2020—U.S. Final Office Action—U.S. Appl. No. 14/863,476.
Nov. 8, 2019—(IN) Examination Report—Application No. 201644035721.
Nov. 14, 2014—U.S. Non-Final Office Action—U.S. Appl. No. 16/287,022.
Jun. 13, 2019—(CA) Office Action—Application No. 3,015,235.
Sep. 6, 2019—(EP) Extended Search Report—Application No. 16891883.7.
Mar. 27, 2020—U.S. Non-Final Office Action—U.S. Appl. No. 15/052,291.
Apr. 22, 2020—U.S. Non-Final Office Action—U.S. Appl. No. 15/295,317.
May 14, 2020—U.S. Notice of Allowance—U.S. Appl. No. 15/268,750.
Oct. 2, 2019—U.S. Non-Final Office Action—U.S. Appl. No. 15/268,750.
“Autonomous Cars from Berlin” website: http://autonomos-labs.com/research/ website last visited on Apr. 30, 2015.
“Axeda and Walsh Vision Announce Alliance for Cloud Telematics Solutions” retrieved Sep. 6, 2011 from http://www.cbs19.tv/story/15234817/axeda-and-walsh-vision-announce-alliance-for-cloud-telematics-solutions pp. 1-4.
“Continental Head-up Display Augmented Reality HUD” http://continental-head-up-display.com/ website last visited on Apr. 30, 2015.
“Drive Control—For When you Need a Little More Self Control,” retrieved Apr. 8, 2016 from https://drivecontrolapp.com, 2 pages.
“In the Future, Your Car's Windscreen Will Be an Augmented Reality Display” https://transportevolved.com/2014/09/29/future-cars-windscreen-will-augmented-reality-display/ website last visited on Apr. 30, 2015.
“Road Asset Management”, https://www.arrb.com/au/Infrastructure/Road-asset-management.aspx, Last visited Oct. 8, 2015, pp. 1-5.
“Telematics: Reinventing Auto Insurance,” retrieved Sep. 6, 2011 from http://www.insurancetech.com/blog/archives/2010/03/telematics_the.html, 10 pages.
Jun. 2, 2011—“Drivers have an IQ, EQ and now with car insurance also a DQ” http://www.insurancechat.co.za/2011-06/drivers-have-an-iq-eq-and-now-with-car-insurance-also-a-dq/.
Oct. 8, 2013—U.S. Non-Final Office Action—U.S. Appl. No. 13/564,524.
Feb. 4, 2014—U.S. Final Office Action—U.S. Appl. No. 13/564,524.
Jul. 13, 2015 U.S. Non-Final Office Action—U.S. Appl. No. 14/066,988.
Jul. 20, 2015—U.S. Non-Final Office Action—U.S. Appl. No. 13/564,524.
Nov. 23, 2015—U.S. Final Office Action—U.S. Appl. No. 13/564,524.
Nov. 23, 2015—U.S. Final Office Action—U.S. Appl. No. 14/066,988.
Sep. 30, 2015 U.S. Non-Final Office Action—U.S. Appl. No. 14/227,740.
2016—“Driver Safety Quotient” http://www.geninfo.com/assessments/driver-safety-quotient.asp.
Dec. 5, 2016 (WO)—International Search Report and Written Opinion—App. PCT/US2016/052877.
Jun. 10, 2016 U.S. Non-Final Office Action—U.S. Appl. No. 14/066,988.
Mar. 23, 2016—U.S. Final Office Action—U.S. Appl. No. 14/227,740.
Mar. 28, 2016—U.S. Non-Final Office Action—U.S. Appl. No. 13/564,524.
Nov. 22, 2016—U.S. Final Office Action—U.S. Appl. No. 14/066,988.
Sep. 1, 2016—U.S. Final Office Action—U.S. Appl. No. 13/564,524.
Apr. 18, 2017—(WO) International Search Report—PCT/IN2016/050355.
Aug. 9, 2017—U.S. Final Office Action—U.S. Appl. No. 15/284,801.
Feb. 2, 2017—(WO) International Search Report—App PCT/US2016/063527.
Jan. 31, 2017—U.S. Non-Final Office Action—U.S. Appl. No. 14/227,740.
Jun. 23, 2017—U.S. Non-Final Office Action—U.S. Appl. No. 15/284,728.
Jun. 6, 2017—U.S. Non-Final Office Action—U.S. Appl. No. 13/564,524.
Jun. 7, 2017—U.S. Final Office Action—U.S. Appl. No. 14/227,740.
Mar. 3, 2017—U.S. Non-Final Office Action—U.S. Appl. No. 15/284,801.
May 19, 2017 (WO) International Search Report and Written Opinion—App. PCT/IN2016/050370.
May 24, 2017—(WO) International Search Report and Written Opinion—PCT/IN16/50369.
Nov. 16, 2017—U.S. Non-Final Office Action—U.S. Appl. No. 14/863,476.
Nov. 22, 2017—U.S. Notice of Allowance—U.S. Appl. No. 15/284,728.
Sep. 12, 2017—U.S. Final Office Action—U.S. Appl. No. 13/564,524.
Sep. 13, 2017—U.S. Non-Final Office Action—U.S. Appl. No. 14/066,988.
Aug. 3, 2018—U.S. Final Office Action—U.S. Appl. No. 14/863,476.
Dec. 5, 2018—U.S. Notice of Allowance—U.S. Appl. No. 15/284,728.
Feb. 26, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 14/227,740.
Jan. 24, 2018—U.S. Notice of Allowance—U.S. Appl. No. 15/284,801.
Jun. 29, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/959,527.
Mar. 1, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/284,728.
Mar. 20, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/052,291.
Nov. 2, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/160,208.
Nov. 28, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/268,750.
Nov. 29, 2018—U.S. Notice of Allowance—U.S. Appl. No. 15/959,527.
Oct. 17, 2018 U.S. Final Office Action—U.S. Appl. No. 15/052,291.
Sep. 4, 2018—U.S. Notice of Allowance—U.S. Appl. No. 15/284,728.
Apr. 2, 2019—U.S. Non-Final Office Action—U.S. Appl. No. 15/052,291.
Chalon Smith, Mark—Pay-As-You-Drive Discounts: A Guide, http://www.insurance.com/auto-insurance/saving-money/low-mileage-discounts-guide.html, Apr. 22, 2015, Insurance.com.
Dewri, Rinku et al—Inferring Trip Destinations From Driving Habits Data, http://www.cs.du.edu/—rdewri/data/MyPapers/Conferences/2013WPES-Extended.pdf, Last Visited Feb. 25, 2016.
How's My Driving?—http://www.economist.com/news/finance-and-economics/21572237-gizmos-track-driving-habits-are-changing-face-car-insurance-hows-my—Feb. 23, 2013—Print Edition of The Economist.
Insurance Companies Utilizing Technology Fairbault Daily News, May 10, 2011, http://www.fairbault.com/print/11435 pp. 1-3.
Li, Z et. al.: “Road Risk Modeling and Cloud-Aided Safety-Based Route Planning”, Published in Cybernetics, IEEE Translations dated Oct. 2, 2015, pp. 1-2.
Martin Demers, “Waste Fleet Safety: Influencing Driver Behavior” 2010 Waste Management Magazine, pp. 1-3.
Rafter, Michelle—Use-Based Insurance Shifts Into High Gear, http://www.edmunds.com/auto-insurance/pay-as-you-drive-insurance-goes-into-high-gear.html, Feb. 27, 2014, Edmunds.
Rosolino, V. et al: “Road Safety Performance Assessment: A New Road Network Risk Index for Info Mobility”, ScienceDirect: Procedia—Social and Behavioral Sciences 111 (2014) pp. 624-633.
Shabeer, et. al, “Mobile Communication Safety on Road Transport,” WSEAS Transactions on Communications, E-ISSN: 2224-2864, Issue 3, vol. 12, Mar. 2013, 12 pages.
Usage-Based Insurance and Telematics, http://www.naic.org/cipr_topics/topic_usage_based_insurance.htm, Last Updated Dec. 14, 2015—National Association of Insurance Commissioners & The Center for Insurance Policy and Research.
Williams, Geoff—Should You Try Pay-As-You-Drive Insurance?, Jan. 13, 2014, http://money.usnews.com/money/personal-finance/articles/2014/01/13/should-you-try-pay-as-you-drive-insurance, U.S. News & World Report.
Apr. 12, 2019—U.S. Final Office Action—U.S. Appl. No. 15/268,750.
Apr. 17, 2019—U.S. Notice of Allowance—U.S. Appl. No. 15/160,208.
“Usage-Based Auto Insurance (UBI): A Revolution Is Underway. Is Your Company Ready?”, Robin Harbage, FCAS, MAAA, published Dec. 2011, Copyright Towers Watson (hereinafter Harbage), Year 2011.
May 24, 2019—(EP) Extended Supplemental Search Report—EP Application No. 16849502.6.
“Junior: The Stanford Entry in the Urban Challenge”, Michael Montemerlo et al., Journal of Field Robotics, vol. 25, No. 9, Sep. 1, 2008, pp. 569-597, XP055169616.
“Moving Object Detection with Laser Scanners”, Christoph Mertz et al., Journal of Field Robotics, vol. 30, No. 1, Jul. 3, 2012, pp. 17-43, XP055460334.
May 31, 2019 U.S. Non-Final Office Action—U.S. Appl. No. 14/863,476.
Nov. 20, 2020—U.S. Notice of Allowance—U.S. Appl. No. 14/863,476.
Jun. 23, 2020—(EP) Extended Search Report—App. No. EP16918214.
Jul. 13, 2020—(EP) Office Action—App. No. 16891883.7.
Jul. 28, 2020—U.S. Notice of Allowance—U.S. Appl. No. 16/287,022.
Jul. 22, 2020—(CA) Office Action—App. No. 3015235.
Aug. 24, 2020—(EP) Examination Report—App. No. 16849502.6.
Aug. 18, 2020—(IN) Examination Report—App. No. 201817034104.
Oct. 15, 2020—U.S. Non-Final Office Action—U.S. Appl. No. 16/905,215.
Mar. 2, 2020—(EP) Partial Search Report—App. No. EP16918214.
Mar. 18, 2020—(EP) Partial Search Report—App. No. EP16918215.
Sep. 23, 2020—U.S. Final Office Action—U.S. Appl. No. 15/052,291.
Oct. 1, 2020—U.S. Final Office Action—U.S. Appl. No. 15/295,317.
Mar. 12, 2021—(US) Non-Final Office Action—U.S. Appl. No. 15/295,317.
Sun, et al., “Context-aware smart car: from model to prototype”, Journal of Zhejiang University-Science A 10, 1049-1059(2009) (Year: 2009).
Continuations (2)
Number Date Country
Parent 15160208 May 2016 US
Child 16440429 US
Parent 13564524 Aug 2012 US
Child 15160208 US