US 8,854,199 B2Grant
Driver risk assessment system and method employing automated driver log
Issue Date:2014-10-07
•24 Claims
•8 Drawing Sheets
Abstract
A Driver Risk Assessment System and Method Employing Automated Driver Log. The system and method provides robust and reliable event scoring and reporting, while also optimizing data transmission bandwidth. The system includes onboard vehicular driving event detectors that record data related to detected driving events, vehicle condition and/or tasking, roadway environmental conditions, selectively store or transfer data related to said detected driving events. If elected, the onboard vehicular system will “score” a detected driving event, compare the local score to historical values previously stored within the onboard system, and upload selective data or data types if the system concludes that a serious driving event has occurred. The system may respond to independent user requests by transferring select data to said user at a variety of locations and formats. Furthermore, by tracking driver identity and other environmental factors, the system may be configured to generate a driver score, a driver log, and a dispatch log. The driver score can be normalized by consideration of environmental factors related to the strenuousness of the driver's driving or the driving challenges experienced by the driver during his or her driving trip.
Metadata
Assignee
- Lytx, Inc.
Inventors
- Bryon Cook
- Jamie Etcheson
Application Information
Application Number:US 12/793,362
Filing Date:2010-06-03
Priority Date:2009-01-26
Art Unit:2684
Classifications
IPC:
B60Q1/00
Patent Drawings (8 sheets)
Description
[0001] This application is an improvement upon the systems, methods and devices previously disclosed in application Ser. No. 11/382,222, filed May 8, 2006, Ser. No. 11/382,239 filed May 8, 2006, Ser. No. 11/566,539 filed May 8, 2006, Ser. No. 11/467,694 filed May 9, 2006, Ser. No. 11/382,328 filed May 9, 2006, Ser. No. 11/382,325 filed May 9, 2006, Ser. No. 11/465,765 filed Aug. 18, 2006, Ser. No. 11/467,486 filed Aug. 25, 2006, Ser. No. 11/566,424 filed Dec. 4, 2006, Ser. No. 11/566,526 filed Dec. 4, 2006, and Ser. No. 12/359,787 filed Jan. 26, 2009 all now pending (the “Prior applications”), and as such, the discloses of those Prior applications are incorporated herein by reference.
[0002] This application is a continuation-in-part of application Ser. No. 12/359,787, filed Jan. 26, 2009, now U.S. Pat. No. 8,269,617 application Ser. No. 12/691,639, filed Jan. 21, 2010, and Ser. No. 12/691,639, filed Jan. 21, 2010, (the “Continuation applications”).
Background of the Invention
[0003] 1. Field of the Invention
[0004] This invention relates generally to systems for analyzing driving events and risk and, more specifically, to a Driver Risk Assessment System and Method Employing Automated Driver Log.
[0005] 2. Description of Related Art
[0006] The surveillance, analysis and reporting of vehicular accidents and “events” has, for some time, been the focus of numerous inventive and commercial efforts. These systems seek to monitor a vehicle's condition while being driven by a driver, and then record and report whenever a “hazardous” condition is detected. What vehicle (and/or driver) symptoms are to constitute a “hazardous” event or condition is defined in the context of a particular monitoring system. Each system will monitor one or more sensor devices located in the vehicle (e.g. shock sensors, location sensors, attitude/orientation sensors, sound sensors), and will generally apply a threshold alarm level (of a variety of levels of sophistication) to the sensor(s) output to assign an event or a non-event. Prior systems of note include the following patents and printed publications: Guensler, et al. US2007/0216521 describes a “Real-time Traffic Citation Probability Display System and Method” incorporates environmental factors and geocentric risk elements to determine driver risk of citation in real-time. Gunderson, et al., US2007/0257804 describes a “System and Method for Reducing Driving Risk with Foresight.” The Gunderson system and method introduces driver coaching into the driver risk analysis system and method. Warren, et al., US2007/0027726 is a system for “Calculation of Driver Score Based on Vehicle Operation for Forward-looking insurance Premiums.” Warren calculates insurance premiums using geomapping to subdivide underwriting areas. Gunderson, et al., US2007/0271105 is a “System and Method for Reducing Risk with Hindsight” that provides forensic analysis of a vehicle accident, including video of the driver and area in front of the vehicle. Gunderson, et al., US2007/0268158 is a “System and Method for Reducing Risk with Insight.” This Gunderson method and system monitors driving for the purpose of analyzing and reporting events on a driver-centric basis. Gunderson, et al., US2007/0257815 is a “System and Method for Taking Risk out of Driving,” and introduces the creation of a driver coaching session as part of the driving monitoring system. Warren, et al., US2006/0253307 describes “Calculation of Driver Score based on Vehicle Operation” in order to assess driver risk based upon a vehicle/driver geolocation and duration in risky locations. Warren, et al. US20060053038 is related to the '307 Warren, that farther includes activity parameters in determining driver risk. Kuttenberger, et al. is a “Method and Device for Evaluating Driving Situations.” This system does calculate driving risk based upon accelerometers and other vehicle characteristics. Finally, Kuboi, et al. is a “Vehicle Behavior Analysis System” that includes GPS, video and onboard triggers for notification/storing/uploading data related to the vehicle behavior.
[0007] There are other prior references dealing with the analysis of the detected data to identify occurrences that would be classified as “driving events” of significance to the driver or driver's supervisory organization. These references include: Raz, et al. U.S. Pat. No. 7,389,178 for “System and Method for Vehicle Driver Behavior Analysis and Evaluation”, Raz, et al., U.S. Pat. No. 7,561,054 for “System and Method for Displaying a Driving Profile,” and Raz, et al., U.S. Patent Application Publication No. 2007/0005404 for “System and Method for Providing Driving Insurance.” All of these Raz references are based upon a system and method that analyzes the raw data collected by the vehicle data sensors and generates a “string” of “maneuvers” that the system recognizes from a database of data that has been previously been identified as representing such maneuvers.
[0008] A detailed review of each of these prior systems has been conducted, and while each and every one of them discloses what is purported to be a novel system for vehicle risk monitoring, reporting and/or analysis, none of these prior systems suggests a system that not only identifies and reports risky driving behavior, but also creates a driver score based not only upon the frequency and severity of driving events, but also adjusted (if appropriate) for different external factors that may cause the driver to experience particularly challenging or easy driving conditions.
Summary of the Invention
[0009] In light of the aforementioned problems associated with the prior systems and methods, it is an object of the present invention to provide a Driver Risk Assessment System and Method Employing Automated Driver Log. The system and method should provide robust and reliable event scoring and reporting, while also optimizing data transmission bandwidth. The system should include onboard vehicular driving event detectors that record data related to detected driving events, vehicle condition and/or tasking, roadway environmental conditions, selectively store or transfer data related to said detected driving events. If elected, the onboard vehicular system should “score” a detected driving event, compare the local score to historical values previously stored within the onboard system, and upload selective data or data types if the system concludes that a serious driving event has occurred. The system should respond to independent user requests by transferring select data to said user at a variety of locations and formats. Furthermore, by tracking driver identity and other environmental factors, the system should be configured to generate a driver score, a driver log, and a dispatch log. Preferably, the driver score should be normalized by consideration of environmental factors related to the strenuousness of the driver's driving.
Brief Description of the Drawings
[0010] The objects and features of the present invention, which are believed to be novel, are set forth with particularity in the appended claims. The present invention, both as to its organization and manner of operation, together with further objects and advantages, may best be understood by reference to the following description, taken in connection with the accompanying drawings, of which:
[0011] FIG. 1 is a block diagram of a conventional vehicle having a preferred embodiment of the system of the present invention installed therein;
[0012] FIG. 2 is a block diagram illustrating an example event detector according to an embodiment of the present invention;
[0013] FIG. 3 is a block diagram of a conventional computing device suitable for executing the method described herein;
[0014] FIG. 4 is a block diagram of a conventional wireless communications device suitable for communicating between the event detector of FIG. 2 and a remote base unit;
[0015] FIG. 5 is a block diagram depicting exemplary inputs to the event detector of FIGS. 1 and 2 , and the potential response results and destinations for detected events;
[0016] FIG. 6 is a block diagram of the logic flow related to driver score normalization and reporting;
[0017] FIG. 7 is an example dispatch log generated by the system and method of the present invention; and
[0018] FIG. 8 is a block diagram depicting the group of potential driver identification parameters.
Detailed Description of the Preferred Embodiments
[0019] The following description is provided to enable any person skilled in the art to make and use the invention and sets forth the best modes contemplated by the inventor of carrying out his invention. Various modifications, however, will remain readily apparent to those skilled in the art, since the generic principles of the present invention have been defined herein specifically to provide a Driver Risk Assessment System and Method Employing Automated Driver Log.
[0020] The present invention can best be understood by initial consideration of FIG. 1 . FIG. 1 is a block diagram of a conventional vehicle 10 having a preferred embodiment of the system 11 of the present invention installed therein. The event detector 30A is in control of a one or more event capture devices 20 that are attached to the vehicle 10. The event detector 30A communicates with the capture devices 20 via wired or wireless interface. There is a data storage area 35 also associated with the event detector 30A, as will be expanded upon below in connection with other drawing figures.
[0021] The event detector 30A can be any of a variety of types of computing devices with the ability to execute programmed instructions, receive input from various sensors, and communicate with one or more internal or external event capture devices 20 and other external devices (not shown). The detector 30A may utilize software, hardware and/or firmware in a variety of combinations to execute the instructions of the disclosed method.
[0022] An example general purpose computing device that may be employed as all or a portion of an event detector 30A is later described in connection with the discussion related to FIG. 4 , hereinbelow. Similarly, an example general purpose wireless communication device that may be employed as all or a portion of an event detector 30A is later described in connection with the discussion related to FIG. 5 hereinbelow.
[0023] When the event detector 30A identifies an event, the event detector 30A instructs the one or more event capture devices 20 to record pre-event data, during the event data, and post-event data that is then provided to the event detector 30A and stored in the data storage area 35. In reality, the event capture devices 20 constantly save data in a buffer memory, which allows the system to actually obtain data that was first-recorded (into a buffer memory) prior to the event itself.
[0024] Events may comprise a variety of situations, including automobile accidents, reckless driving, rough driving, or any other type of stationary or moving occurrence that the owner of a vehicle 10 may desire to know about, and is more fully described below in connection with other drawing figures.
[0025] The system 11 installed within the vehicle 10 may have a plurality of event capture devices 20 placed in various locations around the vehicle 10. An event capture device 20 may comprise a video camera, still camera, microphone, and other types of data capture devices. For example, an event capture device 20 may include an accelerometer that senses changes in speed, direction, and vehicle spatial orientation. Additional sensors and/or data capture devices may also be incorporated into an event capture device 20 in order to provide a rich set of information about a detected event. In that event capture devices 20 may include the capability to record video data, certain of these devices 20 may be used in concert with the event detector 30A to record data to be used in order to identify the driver. For example, video data could be obtained of the driver's face in order to conduct facial recognitions analysis/processing. As the system 11 becomes more automated, and particularly with regard to the features provided by the instant embodiment, coupling the identity of the driver to any event data is critical.
[0026] The data storage area 35 can be any sort of internal or external, fixed or removable memory device and may include both persistent and volatile memories. The function of the data storage area 35 is to maintain data for long term storage and also to provide efficient and fast access to instructions for applications or modules that are executed by the event detector 30A.
[0027] In one embodiment, event detector 30A in combination with the one or more event capture devices 20 identifies an event and stores certain audio and video data along with related information about the event. For example, related information may include the speed of the vehicle when the event occurred, the direction the vehicle was traveling, the location of the vehicle (e.g., from a global positioning system “GPS” sensor), and other information from sensors located in and around the vehicle or from the vehicle itself (e.g., from a data bus integral to the vehicle such as an on board diagnostic “OBD” vehicle bus). This combination of audio, video, and other data is compiled into an event that can be stored in data storage 35 onboard the vehicle for later delivery to an evaluation server. Data transfer to a remote user or server could be via conventional wired connection, or via conventional wireless connections (such as using antennae 652). Turning to FIG. 2 , we can examine some of the internal details regarding the event detector 30A.
[0028] FIG. 2 is a block diagram illustrating an example event detector 30A according to an embodiment of the present invention. In the illustrated embodiment, the event detector 30A comprises an audio/video (“AV”) module 100, a sensor module 110, a communication module 120, a control module 130, and a spatial behavior module (not shown). Additional modules may also be employed to carry out the various functions of the event detector 30A, as will be understood by those having skill in the art.
[0029] The AV module 100 is configured to manage the audio and video input from one or more event capture devices and storage of the audio and video input. The sensor module 110 is configured to manage one or more sensors that can be integral to the event detector 30A or external from the event detector 30A. For example, an accelerometer may be integral to the event detector 30A or it may be located elsewhere in the vehicle 10. The sensor module 110 may also manage other types of sensor devices such as a GPS sensor, temperature sensor, moisture sensor, and the OBD, or the like (all not shown).
[0030] The communication module 120 is configured to manage communications between the event detector 30A and other devices and modules. For example, the communication module 120 may handle communications between the event detector 30A and the various event capture devices 20. The communication module 120 may also handle communications between the event detector 30A and a memory device, a docking station, or a server such as an evaluation server. The communication module 120 is configured to communicate with these various types of devices and other types of devices via a direct wire link (e.g., USB cable, firewire cable), a direct wireless link (e.g., infrared, Bluetooth, ZigBee), or a wired or any wireless network link such as a local area network (“LAN”), a wide area network (“WAN”), a wireless wide area network (“WWAN”), an IEEE 802 wireless network such as an IEEE 802.16 (“WiFi”) network, a WiMAX network, satellite network, or a cellular network. The particular communications mode used will determine which, if any, antennae 652 is used.
[0031] The control module 130 is configured to control the actions or remote devices such as the one or more event capture devices. For example, the control module 130 may be configured to instruct the event capture devices to capture an event and return the data to the event detector when it is informed by the sensor module 110 that certain trigger criteria have been met that identify an event.
[0032] The Local Event Scoring Module 140 and the Event Data Management Module 150 were first introduced in the Continuing Applications. While these two modules 140, 150 are referred to as separate subsystems, it should be understood that some or all of the functionality of each could be integrated into the Control Module 130 (or other subsystem associated with the event detector 30A).
[0033] The Local Event Scoring Module 140 will review the raw data streams from the individual sensors 20 (see FIG. 1 ), or the sensor module 110, and will use one or more mathematic algorithms to calculate a local event score. While t′ais local event score is not expected to be as robust or potentially accurate as the remote event scoring system described by the Parent Applications, it is not necessarily a requirement that this be the case, because a remote score may still be determined independent of the local score. The purpose for calculating the local event score is to enable the event detector 30A to optimize the use of the data transfer bandwidth by only selectively uploading the full event data to the remote server for review/display/analysis. Through extensive observation, the values produced by the various sensors (either alone or in combination) can be analyzed mathematically to produce a product that accurately predicts whether or not a serious accident or other driving event has occurred. Combinations of acceleration, velocity, video and event sound can reliably detect that an accident has happened.
[0034] If the local event scoring module 140 determines that the local event score of a particular driving event meets pre-determined criteria, it will direct the Event Data Management Module 150 to upload the appropriate data received from the sensors 20 (see FIG. 1 ) and stored locally within the vehicle (within a storage device associated with the event detector 30A).
[0035] The Event Data Management Module 150 may also be responsive to a remote request for additional data. For example, in circumstances where the remote user (i.e. remote to the vehicle being monitored) may receive a notice of a particular “incident” of interest, that remote user may be able to manually request audio, video or other locally-recorded data. This requested data would then be transmitted (via the communications module 120) to the remote user for review/analysis/display.
[0036] The Driver I.D. Module 116 is a new feature incorporated into the present invention. While the specific details will be discussed more fully below in connection with FIG. 9 , we will summarize here for the purpose of understanding the general functional scope and purpose of this feature. The Driver I.D. Module 116 determines the vehicle driver's identity (or perhaps disables the vehicle if the driver's I.D. is either not obtainable, or not recognized as being associated with an authorized driver of the vehicle). While, generally speaking, all driving events identified by the system 10 will be associated with the particular vehicle, in the instant system 11 there is the added feature that each driver's performance and statistics will be analyzed and reported on its own. With this new system, the drivers and/or their managers will be able to periodically check on the driving performance of each individual driver, as well as generate appropriate auditing or regulatory reports for each driver.
[0037] Regarding the performance monitoring of each driver, it is believed that substantial value is added by the instant system. Rather than simply tabulating and reporting the risky driving event data for each driver, this system refines this analysis substantially by normalizing each driver's data based upon a number of factors that will be described more fully below. The purpose of the normalization is to give credit to drivers that are placed in driving circumstances that more difficult than their peers. The thinking is that the more difficult the driving circumstances, the more likely that a driver is to have a risky driving event. The converse is also taken into account—that drivers who tend to have less challenging driving circumstances should be free (or nearly so) from risky driving events.
[0038] As discussed in the Continuing Applications, the event detector 30A has the ability to reduce, or at least regulate, the amount of data that flows from it to the remote user(s). When fully enabled, for example, large bandwidth data streams such as video and audio data will not regularly be transmitted to the remote server unless by direction of either the Local Event Scoring Module 140, or by manual or remote user request. This reduction of flow translates into significant cost savings, since most of these systems utilize expensive cellular telephone or satellite networks for vehicle-to-remote server communications. FIGS. 3 and 4 depict conventional hardware used to construct the functional elements of the Event Detector 30A and associated subsystems.
[0039] FIG. 3 is a block diagram of a conventional computing device 750 suitable for executing the method described hereinbelow. For example, the computer system 750 may be used in conjunction with an event detector previously described with respect to FIGS. 1 and 2 , or an evaluation server, analysis station, counseling station, or supervisor station described in the Prior Applications. However, other computer systems and/or architectures may be used, as will be clear to those skilled in the art. The computer system 750 preferably includes one or more processors, such as processor 752. Additional processors may be provided, such as an auxiliary processor to manage input/output, an auxiliary processor to perform floating point mathematical operations, a special-purpose microprocessor having an architecture suitable for fast execution of signal processing algorithms (e.g., digital signal processor), a slave processor subordinate to the main processing system (e.g., back-end processor), an additional microprocessor or controller for dual or multiple processor systems, or a coprocessor. Such auxiliary processors may be discrete processors or may be integrated with the processor 752.
[0040] The processor 752 is preferably connected to a communication bus 754. The communication bus 754 may include a data channel for facilitating information transfer between storage and other peripheral components of the computer system 750. The communication bus 754 further may provide a set of signals used for communication with the processor 752, including a data bus, address bus, and control bus (not shown). The communication bus 754 may comprise any standard or non-standard bus architecture such as, for example, bus architectures compliant with industry standard architecture (“ISA”), extended industry standard architecture (“EISA”), Micro Channel Architecture (“MCA”), peripheral component interconnect (“PCI”) local bus, mini PCI express, or standards promulgated by the Institute of Electrical and Electronics Engineers (“IEEE”) including IEEE 488 general-purpose interface bus (“GPIB”), IEEE 696/S-100, and the like.
[0041] Computer system 750 preferably includes a main memory 756 and may also include a secondary memory 758. The main memory 756 provides storage of instructions and data for programs executing on the processor 752. The main memory 756 is typically semiconductor-based memory such as dynamic random access memory (“DRAM”) and/or static random access memory (“SRAM”). Other semiconductor-based memory types include, for example, synchronous dynamic random access memory (“SDRAM”), Rambus dynamic random access memory (“RDRAM”), ferroelectric random access memory (“FRAM”), and the like, including read only memory (“ROM”).
[0042] The secondary memory 758 may optionally include a hard disk drive 760 and/or a removable storage drive 762, for example a floppy disk drive, a magnetic tape drive, a compact disc (“CD”) drive, a digital versatile disc (“DVD”) drive, etc. The removable storage drive 762 reads from and/or writes to a removable storage medium 764 in a well-known manner. Removable storage medium 764 may be, for example, a floppy disk, magnetic tape, CD, DVD, memory stick, USB memory device, etc.
[0043] The removable storage medium 764 is preferably a computer readable medium having stored thereon computer executable code (i.e., software) and/or data. The computer software or data stored on the removable storage medium 764 is read into the computer system 750 as electrical communication signals 778.
[0044] In alternative embodiments, secondary memory 758 may include other similar means for allowing computer programs or other data or instructions to be loaded into the computer system 750. Such means may include, for example, an external storage medium 772 and an interface 770. Examples of external storage medium 772 may include an external hard disk drive or an external optical drive, or and external magneto-optical drive.
[0045] Other examples of secondary memory 758 may include semiconductor-based memory such as programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), electrically erasable read-only memory (“EEPROM”), or flash memory. Also included are any other external storage medium 772 and interfaces 770, which allow software and data to be transferred from external storage medium 772 to the computer system 750.
[0046] Computer system 750 may also include a communication interface 774. The communication interface 774 allows software and data to be transferred between computer system 750 and external devices (e.g. printers), networks, or information sources. For example, computer software or executable code may be transferred to computer system 750 from a network server via communication interface 774. Examples of communication interface 774 include a modem, a network interface card (“NIC”), a communications port, a PCMCIA slot and card, an infrared interface, and an IEEE 1394 fire-wire, just to name a few.
[0047] Communication interface 774 preferably implements industry promulgated protocol standards, such as Ethernet IEEE 802 standards, Fiber Channel, digital subscriber line (“DSL”), asynchronous digital subscriber line (“ADSL”), frame relay, asynchronous transfer mode (“ATM”), integrated digital services network (“ISDN”), personal communications services (“PCS”), transmission control protocol/Internet protocol (“TCP/IP”), serial line Internet protocol/point to point protocol (“SLIP/PPP”), and so on, but may also implement customized or non-standard interface protocols as well.
[0048] Software and data transferred via communication interface 774 are generally in the form of electrical communication signals 778. These signals 778 are preferably provided to communication interface 774 via a communication channel 776. Communication channel 776 carries signals 778 and can be implemented using a variety of wired or wireless communication means including wire or cable, fiber optics, conventional phone line, cellular phone link, satellite link, wireless data communication link, radio frequency (RF) link, or infrared link, just to name a few.
[0049] Computer executable code (i.e., computer programs or software) is stored in the main memory 756 and/or the secondary memory 758. Computer programs can also be received via communication interface 774 and stored in the main memory 756 and/or the secondary memory 758. Such computer programs, when executed, enable the computer system 750 to perform the various functions of the present invention as previously described.
[0050] In this description, the term “computer readable medium” is used to refer to any media used to provide computer executable code (e.g., software and computer programs) to the computer system 750. Examples of these media include main memory 756, secondary memory 758 (including hard disk drive 760, removable storage medium 764, and external storage medium 772), and any peripheral device communicatively coupled with communication interface 774 (including a network information server or other network device). These computer readable mediums are means for providing executable code, programming instructions, and software to the computer system 750.
[0051] In an embodiment that is implemented using software, the software may be stored on a computer readable medium and loaded into computer system 750 by way of removable storage drive 762, interface 770, or communication interface 774. In such an embodiment, the software is loaded into the computer system 750 in the form of electrical communication signals 778. The software, when executed by the processor 752, preferably causes the processor 752 to perform the inventive features and functions to be described hereinbelow.
[0052] Various embodiments may also be implemented primarily in hardware using, for example, components such as application specific integrated circuits (“ASICs”), or field programmable gate arrays (“FPGAs”). Implementation of a hardware state machine capable of performing the functions described herein will also be apparent to those skilled in the relevant art. Various embodiments may also be implemented using a combination of both hardware and software.
[0053] Furthermore, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and method steps described in connection with the above described figures and the embodiments disclosed herein can often be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled persons can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the invention. In addition, the grouping of functions within a module, block, circuit or step is for ease of description. Specific functions or steps can be moved from one module, block or circuit to another without departing from the invention.
[0054] Moreover, the various illustrative logical blocks, modules, and methods described in connection with the embodiments disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (“DSP”), an ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0055] Additionally, the steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium including a network storage medium. An exemplary storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can also reside in an ASIC.
[0056] FIG. 4 is a block diagram of a conventional wireless communications device 650 suitable for communicating between the event detector 30A of FIG. 2 and a remote base unit. For example, the wireless communication device 650 may be used in conjunction with an event detector previously described with respect to FIGS. 1 and 2 , or an evaluation server, analysis station, counseling station, or supervisor station previously described in the Prior Applications. However, other wireless communication devices and/or architectures may also be used, as will be clear to those skilled in the art.
[0057] In the illustrated embodiment, wireless communication device 650 comprises an antenna 652, a multiplexor 654, a low noise amplifier (“LNA”) 656, a power amplifier (“PA”) 658, a modulation/demodulation circuit 660, a baseband processor 662, a speaker 664, a microphone 666, a central processing unit (“CPU”) 668, a data storage area 670, and a hardware interface 672. In the wireless communication device 652, radio frequency (“RF”) signals are transmitted and received by antenna 652. Multiplexor 654 acts as a switch method to couple two or more transmit and receive paths to two or more antennae paths, coupling antenna 652 between the transmit and receive signal paths. In the receive path, received RF signals are coupled from a multiplexor 654 to LNA 656. LNA 656 amplifies the received RF signal and couples the amplified signal to a demodulation portion of the modulation circuit 660.
[0058] Typically modulation circuit 660 will combine a demodulator and modulator in one integrated circuit (“IC”). The demodulator and modulator can also be separate components. The demodulator strips away the RF carrier signal leaving a base-band receive audio/data signal, which is sent from the demodulator output to the base-band processor 662.
[0059] If the base-band receive audio signal contains audio information (or really any data in the digital domain), then base-band processor 662 decodes the signal and converts it to an analog signal. Then the signal is amplified and sent to the speaker 664. The base-band processor 662 also receives analog audio signals from the microphone 666. These analog audio signals are converted to digital signals and encoded by the base-band processor 662. The base-band processor 662 also codes the digital signals for transmission and generates a base-band transmit audio signal that is routed to the modulator portion of modulation circuit 660. The modulator mixes the base-band transmit audio signal with an RF carrier signal generating an RF transmit signal that is routed to the power amplifier 658. The power amplifier 658 amplifies the RF transmit signal and routes it to the multiplexor 654 where the signal is switched to the antenna port for transmission by antenna 652.
[0060] The baseband processor 662 is also communicatively coupled with the central processing unit 668. The central processing unit 668 has access to a data storage area 670. The central processing unit 668 is preferably configured to execute instructions (i.e., computer programs or software) that can be stored in the data storage area 670. Computer programs can also be received from the baseband processor 662 and stored in the data storage area 670 or executed upon receipt. Such computer programs, when executed, enable the wireless communication device 650 to perform the various functions of the present invention as previously described.
[0061] In this description, the term “computer readable medium” is used to refer to any media used to provide executable instructions (e.g., software and computer programs) to the wireless communication device 650 for execution by the central processing unit 668. Examples of these media include the data storage area 670, microphone 666 (via the baseband processor 662), antenna 652 (also via the baseband processor 662), and hardware interface 672. These computer readable mediums are means for providing executable code, programming instructions, and software to the wireless communication device 650. The executable code, programming instructions, and software, when executed by the central processing unit 668, preferably cause the central processing unit 668 to perform the inventive features and functions previously described herein. It should be noted that the firmware used by the device 650 (or CPU 668) can be replaced/modified/upgraded via wired or wireless network transfer.
[0062] The central processing unit is also preferably configured to receive notifications from the hardware interface 672 when new devices are detected by the hardware interface. Hardware interface 672 can be a combination electromechanical detector with controlling software that communicates with the CPU 668 and interacts with new devices. FIG. 5 depicts how the system of the present invention handles the data from the different sensor devices.
[0063] FIG. 5 is a block diagram depicting exemplary inputs to the event detector 30A of FIGS. 1 and 2 , and the potential response results and destinations for detected events. The communications with an external evaluation server is extensively discussed in the Parent Applications, and is therefore not reproduced there, but is rather incorporated herein by reference.
[0064] As shown, event capture devices 20 (including inputs from the OBD and other vehicle equipment) can generate captured event data for velocity, acceleration (linear), pitch, roll, yaw. Center of gravity and CG offset may also be used. Vehicle orientation relative to compass heading, as well as vehicle location may be included in event data. Finally, audio, video and metadata (including driver ID) will likely be included.
[0065] The captured data 29 may be filtered by a real-time tunable raw data filter 31 before it is analyzed by the event detector 30A to determine whether or not a driving event of note has occurred. The criteria for making a type of driving event of note could be user-defined for their particular reason; such events of note may or may not otherwise be considered to be risky driving events, but are otherwise of interest to the user.
[0066] As discussed above in connection with FIG. 2 , different types of sensor data 29 will be handled in different manners by the present system. For the purpose of clarity, we have here divided the sensor data 29 into two groups of data: regularly uploaded data 54 and selectively uploaded data 52. The idea is that primarily the less bandwidth-demanding data is regularly uploaded to the remote server from the vehicle. The higher bandwidth data would be retained aboard the vehicle until it is manually requested, automatically identified as being “of interest”, or for periodic record-keeping purposes (which very well may be accomplished via wired or wireless connection while the vehicle is under a maintenance status).
[0067] Here, the video and audio data and telemetry data have been included within the selectively uploaded data 52. As mentioned above, the expectation would be that this data would not normally be included in the regular wireless data flow from the event detector 30A to the remote sewer unless certain conditions are met. Since the audio and particularly the video data demands large bandwidth for transfer, the data of these streams would generally be stored locally. Driver ID is also included within the selectively uploaded data 52, since the objective evidence of the driver's identity (such as a video clip) may not be obtained until commanded as such by the event detector 30A (such as right after the local event scoring module 140 (see FIG. 2 ) determines that an event of interest has transpired. At that point, any remote user receiving the video and audio data would most likely be very interested in confirming the identity of the driver (since the goal would be to transfer the data 52 when there is a vehicular crash or near miss).
[0068] One factor that might be used to determine whether or not an “event of interest” has transpired is related to the nature of the forces (i.e. of the accelerometer) being sensed. Certain forces (e.g. shock) have been identified as being automatically “of interest,” even without any real onboard analysis of the entire set of data streams being analyzed.
[0069] The regularly uploaded data 54 is handled as discussed in the prior applications, that is, initial filtering 31 may be performed on the data in order to reduce false event occurrences. The event detector 30A will convey the regularly uploaded data 54 as described in the Parent Applications (incorporated herein by reference) and identified as the prior data output options 41 (summarized below in connection with FIG. 6 ).
[0070] If activated, the local event scoring module 140 (see FIG. 2 ) will conduct local analysis 56 of the regularly uploaded data 54 in order to calculate a local event score. If the local event score so determines, the selectively uploaded event data 52 will be transmitted to remote storage 34 (at the remote server) for display/review/analysis (e.g. scoring) remote to the vehicle.
[0071] A remote request 58 (from a remote user or system) will also trigger the data 52 to be uploaded to remote storage 34 for remote display and analysis 36A. As should be apparent, those transfer paths responsive to the local analysis 56 or remote request 58 are identified by dashed lines.
[0072] It should be understood that the depicted classifications of data as being part of the “selectively uploaded” data 52 versus the “regularly uploaded” data 54 is only one possible arrangement. In other forms, and when certain system settings are chosen, the system (either the local system aboard the vehicle or the remote server) may send one or more designated persons a message (email, SMS, etc.) that will include a brief alert message that there has been an “incident” in a vehicle (or more than one vehicle). The user may then be able to select a “hyperlink” that will act as a user request to download the selected data from the system (either the vehicle or the central remote server or related assemblies). The data being downloaded in response to the user request would normally be video and/or audio data, but it could also include other data points or data streams, such as vehicle location coordinates (e.g. via GPS), incident type or classification (e.g. “crash,” “vehicle flipover,” “excessive speed,” etc.).
[0073] Furthermore, the user's request after being alerted of the incident may either be serviced by the remote server system, or by the vehicle-borne system. As such, the selectively uploaded data 52 may not be uploaded to the server until after a user has requested it. Also, the alert message to the user (which usually would not include any large bandwidth, selectively uploaded data 52) may have more than one data upload option. For example, the user may be given the options of: (a) uploading a short video clip including vehicle GPS location and speed; (b) uploading actively streaming video and audio directly from the vehicle; or (c) uploading current video/audio data plus similar data from some period of time prior to the incident having occurred.
[0074] If neither the local analysis 56, or remote request 58 is received by the event detector 30A, then the data 52 will be handled according to the prior data output options as more fully described in the Continuation Applications, herein incorporated by reference. Having now reviewed the basic arrangement of the system of the present invention and critical elements thereof, we can direct our attention to the driver-centric features of the latest improvement to the inventions of the Parent and Continuation Applications.
[0075] FIG. 6 is a block diagram of the logic flow related to driver score normalization and reporting of the present invention. The sensors and/or event detector identifies driving events 60 (or suspected driving events) based upon the data detected by the sensors themselves (and their respective threshold settings). Once triggered, the event data is analyzed either locally 56 or remotely 36A, to determine a score for each event. As discussed in the Parent and Continuation Applications, the “score” as it applies to a driving event is the result of a qualitative review of the triggered event—as such, it can also be viewed as a “verification” that the triggered driving event is an actual risky driving occurrence. Therefore, the “score” of a driving event 60 is actually a confidence level that that is determined either by a human reviewer of the recorded video/audio and other sensor data, or via automated scoring where the historical accuracy of certain system-predicted driving events is used to either confirm or disprove the predicted driving events 60.
[0076] Once scored 56, 36A, the event reporting 41, 36A will proceed as previously discussed in the Parent and Continuation Applications.
[0077] While driving events 60 are monitored, analyzed and reported in a vehicle-centric perspective; that is to say that within a fleet of vehicles, it is the vehicle and its equipment and condition that is tracked by the client/owner. Of course, the vehicle does not operate itself. While certain vehicle traits or conditions may impact the propensity for its experiencing risky driving events, it is generally believed that the primary contributor to vehicle safe (or unsafe) operations is the driver of the vehicle. Consequently, it is also important to compile vehicle event data in a driver-centric way. Tracking a driver's driving event history opens up the possibility for much more effective driver supervision, coaching, and performance accountability. This should translate into fewer risky driving events.
[0078] The problem with comparing one driver's risky driving history with that of other drivers is that not all drivers engage in the same driving experience. One would expect that a driver that drives only in daytime hours, in good weather, and in low traffic conditions will exhibit riskier driving behavior than a driver who drives in traffic in poor visibility and/or weather. The vehicle event recording system 10 is not generally configured to take such factors into account in generating driving events 60 because there is a potential for the under-reporting of driving events. It is preferable to focus on the vehicle's spatial motion when generating driving event reports, since it is the spatial motion of the vehicle that actually defines whether or not risky driving behavior is observed.
[0079] In order to conduct driver-centric driving event analysis, each scored driving event 65 must include the driver I.D. 67. Each of these scored driving events 65 are then adjusted by a normalization factor 76 before being finally attributed to the identified driver. The purpose behind the application of a normalization factor 76 to a scored driving event is to give the driver credit for driving well under below-average conditions (or vice-versa).
[0080] The normalization factor 76 is derived from consideration of a series of driver challenge factors 62. Example of potential challenge factors 62 are depicted here in FIG. 6 . Not all of these factors 62 are necessarily included in arriving at each normalization factor 76, since data for all factors 62 may not be available for each and every vehicle and/or scored event 65.
[0081] The amount of mileage 63 driven by a particular driver during a standardized period of time (e.g. by shift, day or week) is expected to have an affect on driver performance. It is expected that the more miles driven by a driver, the better the odds that the driver will experience a risky driving event. Consequently, a driver having a higher number of miles without incident is given credit as compared to a driver having fewer miles without incident. The mileage traveled by a driver in a vehicle is generally reported by the vehicles onboard computer (measuring from when the driver commences each trip to when the driver concludes each trip). In other embodiments, mileage may be computed from GPS data (again measuring driver trip lengths).
[0082] Duration (time) driven 64 by a driver, such as during a shift or day, is also considered in arriving at the normalization factor 76. A driver driving for longer periods of time within a standard period of time would be expected to have a higher likelihood of a risky driving event. Therefore, total elapsed trip time by driver is considered in arriving at the normalization factor 76. Driver trip time would generally be sensed by the vehicle onboard computer, but the event detector/driver identification module could also be configured to monitor trip duration by driver.
[0083] The road condition and/or terrain 66 over which a driver's vehicle travels can impact the difficulty that the driver has in avoiding accidents or other driving incidents. Poor road conditions could impact steering accuracy, tire traction, and vehicle tracking (tendency to go straight). Similarly, hilly roads would generally create an elevated risk for accidents. The road condition and/or terrain could be obtained by a variety of approaches. A library of road terrains and/or conditions could provide a basic level of information. Sensors in the vehicle (e.g. accelerometers, orientation detectors, audio sensors) could also detect sound, vibrations, pitch/yaw, etc. to conclude what the road condition and/or terrain conditions are.
[0084] The amount of vehicular traffic or traffic density 68 in which a vehicle is immersed certainly will affect the level of driving hazard to a driver. Traffic density can be determined (or estimated) by a variety of methods: (1) through video recognition of vehicle density; (2) by geographic mapping to indicate predicted traffic patterns for different time periods (and days of the week); (3) by detecting vehicle speed and stop-starting as compared to posted speed limits and traffic control devices. Other methods may also be contrived to use new or existing vehicle sensors or library data.
[0085] Environmental conditions 70, such as ambient lighting, visibility, weather status and other factors will either raise or lower the propensity for vehicle accidents or incidents. Broadcast weather information could be coupled with event detection, or onboard sensors could detect or predict the weather and other environmental conditions. Video and/or audio sensors could detect ambient light conditions, existence of precipitation and even visibility.
[0086] The type of vehicle 72 being driven could have substantial affect on a driver's incident risk. A passenger vehicle would tend to be safer (and less likely by its nature to be risky to drive) than a city bus or some utility vehicle. While onboard sensors could detect vehicle motion characteristics in order to provide some level of vehicle type or classification conclusion, it usually is also a part of the initialization data for the event recording system, since the vehicle type is an important factor used in the interpretation of accelerometer and other data.
[0087] Finally (in this example), vehicle tasking 74 can have an affect on the hazards presented to a driver. A delivery vehicle would generally have a tendency to be more risky than a salesperson's vehicle. Similarly, a dump truck might have a tendency to be more risky to drive than a delivery vehicle. Vehicle tasking 74 may or may not be directly connected to the vehicle type 72. Consequently, the initialization data for the vehicle might be the source of the vehicle tasking 74 data.
[0088] Some or all of these driver challenge factors 62 could be used to create one or a series of normalization factors 76 to be applied to an individual driver driving record. The result is a final driver score 78. The score 78 could be relative to a particular fleet of drivers, or it could be relative to all drivers for which driving performance is being monitored, or trends for individual drivers could be scored/monitored. Driver score 78 is a numerical representation meant to rank or grade a driver, based upon the challenge factors 62 and their effect on scored driving events occurring during a driver's trip(s). This differs from the event score, which is more of a representation of the confidence in the predicted event.
[0089] FIG. 7 is an example dispatch log 82 generated by the system and method of the present invention. The dispatch log 82 created by the system of the present invention is an automated series of trip log entries 83 for a particular operational group of vehicles and drivers. A trip log entry 83 is created each time that a vehicle is used for a driving trip. The entries 83 include driver identification 84, vehicle identification 85 and elapsed time information 87. Other trip-related information 91 may be included, either directly or indirectly, in each trip log entry 83, such as the driver challenge factors identified above in connection with the discussion related to FIG. 6 . For example, mileage, terrain, traffic density, environmental conditions may be included in the trip log entry 83. Vehicle type and vehicle tasking may be treated as vehicle characteristics or factors that are coupled or linked to the vehicle information or identity 85.
[0090] The driver log discussed above in connection with FIG. 6 would be a compilation or sorting of trip log entries from the dispatch log 82 that are those trips driven by a particular driver. A normalization factor (see FIG. 6 ) may be assigned “on the fly” in real-time as another piece of other trip-related information 91 within the trip log entries 83, or it may be produced by the system on demand at some later time. The driver score (see FIG. 6 ) could be a compilation of driving events (or non-events) experienced during a particular trip, or alternatively it could be updated on an ongoing basis on a pre-established periodicity (e.g. weekly, by a certain elapsed mileage, or by a pre-determined number of trips).
[0091] FIG. 8 is a block diagram depicting the group of potential driver identification parameters. As discussed above, identifying the driver 84 for each driving trip is a critical aspect of the functionality of the system of the present invention. This is the functional purpose of the driver ID module 116.
[0092] The module 116 may identify the vehicle driver via facial recognition methodology 86. That approach begins by taking a video sample of the driver's face (typically using one of the pre-existing video recorders incorporated within the vehicle event recorder), and applying facial recognition methodology to create a data file representing that driver's face. The driver's facial data file is compared to a repository of data files for all eligible drivers of the vehicle; the driver's identity is ascertained when a match is achieved.
[0093] Fingerprints, retinal scan, voice recognition, or other biometric identification approaches 88 may be used. Again, the vehicle driver's biometric data is compared to data retained in a driver data repository for biometric identity data.
[0094] The drivers may be issued security tokens 90 that cycle through a series of passwords synchronously with an internal password generator within the remote sewer computer. The driver would enter his or her password, as obtained from the token, into the event recorder system before the vehicle was activated and the driving trip commenced. Similarly, yet less securely, a simple keypad password entry 92 could be used to identify the driver from a group of authorized drivers.
[0095] A stand-alone, external system or subsystem 94 might be used to identify the driver. For example, a dispatcher may remotely “issue” a vehicle to a driver. Until the vehicle is returned to “inventory” (after the driver's trip or shift is complete), driving trips using that vehicle would be attributed to that driver.
[0096] A final example would be to use the driver seat sensors within the vehicle to weigh the driver when he or she sits in the driver's seat 96. While this approach may not be accurate enough to operate as a stand-alone method for driver I.D., it might be used to supplement one of the other aforementioned methods.
[0097] The individual driver identity data repositories may be combined into a single data repository containing all driver identity data (i.e. for all of the different identification methods), or there may be a series of separate data repositories.
[0098] While there is a long list of approaches listed herein, these are exemplary only—other methods or approaches might be utilized, depending upon the particular system (and vehicle) design.
[0099] Those skilled in the art will appreciate that various adaptations and modifications of the just-described preferred embodiment can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.
Claims
What is claimed is:
1. A system for reducing risk in driving, comprising:
at least one event capture device associated with a vehicle, said event capture device or devices detecting data related to the physical condition of said vehicle during a driving trip;
at least one event detector device coupled with the vehicle and configured to communicate with said event capture device or devices and to predict, responsive to analysis of the group of data captured by said event capture devices, whether or not data captured by said event capture devices represents a driving event, and assigning a unique risk identifier selected from a group of risk identities to said driving event;
an event scoring module attached to or otherwise associated to communicate with said event detector for generating an event score based upon the assigned said risk identifier data from said event capture device or devices and applying risk confidence data related to the specific risk;
an event data management module communicating with said event detector for uploading data from said event capture devices to a remote computing device, with said uploading being responsive to said event score;
a driver scoring module in communication with said remote computing device or said event data module, said driver scoring module configured to correlate said scored event and said uploaded data to an individual driver and generating a normalized driver score, said generated driver score is based at least in part on one or more driver challenge factors representing driving difficulty during one or more driving trips in one or more said vehicles,
wherein the one or more driver challenge factors include a type of the vehicle and one or more tasks associated with the vehicle and/or the driver for said driving trip.
2. The system of claim 1, wherein said driver scoring module is further configured to generate a driver driving data log for said driving trips, said driver data log comprising a record of said drivers driving trips and indicia regarding whether or not said driver's driving trips are in compliance with pre-established limitations imposed on a driver's driving trips.
3. The system of claim 2, wherein said driver scoring module is further configured to generate a dispatch driving data log for a dispatch group of said vehicles, said dispatch driving data log comprising a record of drivers' driving trips in said vehicles of said dispatch group.
4. The system of claim 3, wherein said one or more driver challenge factors are used by said driver scoring module to generate a normalization factor, said normalization factor applied to a raw driver score based only on said scored events occurring during said driver's driving trip to generate said normalized driver score.
5. The system of claim 1, further comprising a driver identification module for identifying the driver of said vehicle during said driving trip and providing said driver identity to said driver scoring module.
6. The system of claim 5, wherein said driver identification module comprises facial recognition means for analyzing video of said driver's face and comparing it to a data repository of pre-existing driver facial configurations to determine which of said driver facial configurations is represented by said driver's face.
7. The system of claim 5, wherein said driver identification module includes a driver weight sensor for measuring a driver's weight when said driver is in said vehicle, for use in identifying said driver as compared to a data repository of pre-existing driver weight data.
8. The system of claim 5, wherein said driver identification module includes biometric sensing means for comparing biometric data of a driver to a data repository of pre-existing driver biometric data to determine which of said drivers is represented by said biometric data.
9. The system of claim 5, wherein said driver identification module includes password entry means associated with said event detector device for password entry by a driver for the purpose of identifying said driver.
10. The system of claim 1, further comprising a driver identification module for identifying the driver of said vehicle during said driving trip and providing said driver identity to said driver scoring module.
11. The system of claim 10, wherein said driver scoring module is further configured to generate a driver driving data log for said driving trips, said driver data log comprising a record of said drivers driving trips and indicia regarding whether or not said driver's driving trips are in compliance with pre-established limitations imposed on a driver's driving trips.
12. The system of claim 11, wherein said driver scoring module is further configured to generate a dispatch driving data log for a dispatch group of said vehicles, said dispatch driving data log comprising a record of drivers' driving trips in said vehicles of said dispatch group.
13. The system of claim 1, wherein the normalized driver score is normalized with respect to a plurality of drivers.
14. The system of claim 1, wherein the one or more driver challenge factors further include an amount of mileage driven by the driver and/or a duration of time during which the driver has operated a vehicle during a standardized period.
15. The system of claim 14, wherein the standardized period is a shift, a day, or a week.
16. The system of claim 1, wherein the type of the vehicle include: a passenger vehicle, a bus, a truck, or a utility vehicle.
17. A method for evaluating risk in driving, comprising the steps of:
capturing driving event data at one or more event capture devices coupled with said vehicle;
associating the identification of the driver with said captured event data;
analyzing the driving event data with at least one event detector device to assign a predicted driving event identifier selected from a pre-determined group of driving event identifiers;
assigning an event score to said predicted driving event identifier, said event score being either the result of actual human review of said driving event data associated with said predicted driving event identifier, or the historical confidence that prior human review of driving event data leading to the same predicted driving event identifier was confirmed;
selectively uploading all or part of said captured data to a remote computing device, said selective uploading being responsive to said assigned event score; and
correlate said scored event and said uploaded data to an individual driver and generating a normalized driver score, said generated driver score is based at least in part on one or more driver challenge factors representing driving difficulty during one or more driving trips in one or more said vehicles,
wherein the one or more driver challenge factors include a type of the vehicle and one or more tasks associated with the vehicle and/or the driver for said driving trip.
18. The method of claim 17, further generating a driver driving data log for said driving trips, said driver data log comprising a record of said drivers driving trips and indicia regarding whether or not said driver's driving trips are in compliance with pre-established limitations imposed on a driver's driving trips.
19. The method of claim 18, further generating a dispatch driving data log for a dispatch group of said vehicles, said dispatch driving data log comprising a record of drivers' driving trips in said vehicles of said dispatch group.
20. The method of claim 19, wherein said one or more driver challenge factors of said driver correlation step are used to generate a normalization factor, said normalization factor applied to a raw driver score based only on said scored events occurring during said driver's driving trip to generate said normalized driver score.
21. The method of claim 17, wherein the one or more driver challenge factors further include an amount of mileage driven by the driver and/or a duration of time during which the driver has operated a vehicle during a standardized period.
22. The method of claim 21, wherein the standardized period is a shift, a day, or a week.
23. The method of claim 17, wherein the type of the vehicle include: a passenger vehicle, a bus, a truck, or a utility vehicle.
24. A method for reducing risk in driving, comprising:
obtaining a plurality of driving event data for the individual driver, said event data comprising video or audio data and velocity, acceleration, vehicle spatial orientation and heading, vehicle metadata vehicle location data, and driver identity, the driving event data obtained from a data storage area comprising a plurality of captured driving event data for a plurality of drivers each including a driver identity selected from a group of known drivers;
analyzing the plurality of driving event data; analyzing demographic data for the individual driver, said demographic data obtained from a data storage area comprising a plurality of driver records, said records comprising demographic data; and
scoring the individual driver based at least in part on the analysis of the plurality of driving event data, the analysis of the demographic data, and one or more driver challenge factors related to how challenging a driving trip was for a driver; and
uploading relevant portions of said video and audio data to a remote computing device responsive to a two-stage analysis of said driving event data, said first stage being the numerical analysis of the driving event data in order to generate a predicted event identifier selected from a group of potential event identities, and the second stage being the assignment of a confidence score to the generated predicted event identifier, with said confidence score being responsive to intermittent human review of predicted driving events,
wherein the one or more driver challenge factors include a type of the vehicle and one or more tasks associated with the vehicle and/or the driver for said driving trip.
Patent Citations (62)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4281354(A) | 1981-07-01 | Conte | Applicant |
| US4718685(A) | 1988-01-01 | Kawabe et al. | Applicant |
| US5140436(A) | 1992-08-01 | Blessinger | Applicant |
| US5497419(A) | 1996-03-01 | Hill | Applicant |
| US5546191(A) | 1996-08-01 | Hibi et al. | Applicant |
| US5574424(A) | 1996-11-01 | Nguyen | Examiner |
| US5600775(A) | 1997-02-01 | King et al. | Applicant |
| US5689442(A) | 1997-11-01 | Swanson et al. | Applicant |
| US5815093(A) | 1998-09-01 | Kikinis | Applicant |
| US5825284(A) | 1998-10-01 | Dunwoody et al. | Applicant |
| US6141611(A) | 2000-10-01 | Makey et al. | Applicant |
| US6163338(A) | 2000-12-01 | Johnson et al. | Applicant |
| US6389340(B1) | 2002-05-01 | Rayner | Applicant |
| US6405132(B1) | 2002-06-01 | Breed et al. | Applicant |
| US6449540(B1) | 2002-09-01 | Rayner | Applicant |
| US6575902(B1) | 2003-06-01 | Burton | Applicant |
| US6718239(B2) | 2004-04-01 | Rayner | Applicant |
| US7209833(B2) | 2007-04-01 | Isaji et al. | Applicant |
| US7702442(B2) | 2010-04-01 | Takenaka | Applicant |
| US7821421(B2) | 2010-10-01 | Tamir et al. | Applicant |
| US2001/0005804(A1) | 2001-06-01 | Rayner | Applicant |
| US2002/0111725(A1) | 2002-08-01 | Burge | Examiner |
| US2002/0163532(A1) | 2002-11-01 | Thomas et al. | Examiner |
| US2003/0080878(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2004/0039503(A1) | 2004-02-01 | Doyle | Applicant |
| US2004/0054513(A1) | 2004-03-01 | Laird et al. | Applicant |
| US2004/0103010(A1) | 2004-05-01 | Wahlbin et al. | Applicant |
| US2004/0153362(A1) | 2004-08-01 | Bauer et al. | Examiner |
| US2004/0236474(A1) | 2004-11-01 | Chowdhary et al. | Applicant |
| US2005/0073585(A1) | 2005-04-01 | Ettinger et al. | Applicant |
| US2005/0137757(A1) | 2005-06-01 | Phelan et al. | Examiner |
| US2005/0166258(A1) | 2005-07-01 | Vasilevsky et al. | Applicant |
| US2006/0053038(A1) | 2006-03-01 | Warren et al. | Examiner |
| US2006/0103127(A1) | 2006-05-01 | Lie et al. | Applicant |
| US2006/0212195(A1) | 2006-09-01 | Veith et al. | Applicant |
| US2006/0253307(A1) | 2006-11-01 | Warren et al. | Applicant |
| US2007/0001831(A1) | 2007-01-01 | Raz et al. | Applicant |
| US2007/0027583(A1) | 2007-02-01 | Tamir et al. | Applicant |
| US2007/0027726(A1) | 2007-02-01 | Warren et al. | Applicant |
| US2007/0124332(A1) | 2007-05-01 | Ballesty et al. | Applicant |
| US2007/0135979(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0136078(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0150140(A1) | 2007-06-01 | Seymour | Applicant |
| US2007/0173994(A1) | 2007-07-01 | Kubo et al. | Applicant |
| US2007/0216521(A1) | 2007-09-01 | Guensler et al. | Applicant |
| US2007/0241874(A1) | 2007-10-01 | Okpysh et al. | Applicant |
| US2007/0257781(A1) | 2007-11-01 | Denson | Applicant |
| US2007/0257804(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0257815(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0260677(A1) | 2007-11-01 | DeMarco et al. | Applicant |
| US2007/0268158(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0271105(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0299612(A1) | 2007-12-01 | Kimura et al. | Applicant |
| US2008/0167775(A1) | 2008-07-01 | Kuttenberger et al. | Applicant |
| US2008/0269978(A1) | 2008-10-01 | Shirole | Applicant |
| US2009/0224869(A1) | 2009-09-01 | Baker et al. | Applicant |
| US2010/0063672(A1) | 2010-03-01 | Anderson | Applicant |
| US2010/0070175(A1) | 2010-03-01 | Soulchin et al. | Applicant |
| US2010/0085193(A1) | 2010-04-01 | Boss et al. | Applicant |
| US2011/0077028(A1) | 2011-03-01 | Wilkes et al. | Applicant |
| DE4416991 | 1995-11-01 | Applicant | |
| EP1818873 | 2007-08-01 | Applicant |
Non-Patent Literature (84)
- Jessyca Wallace, “Analyzing and Processing DriveCam Recorded Events”, Oct. 6, 2003.Applicant
- PCT/US2010/022012, Invitation to Pay Additional Fees with Communication of Partial International Search, Jul. 21, 2010.Applicant
- “World News Tonight”, CBS Television New Program discussing teen drivers using the DriveCam Program and DriveCam Technology, Oct. 10, 2005, on PC formatted CD-R, World News Tonight.wmv, 7.02 MB, Created Jan. 12, 2011.Applicant
- “World News Tonight”, PBS Television New Program discussing teen drivers using the DriveCam Program and DriveCam Technology, Oct. 10, 2005, on PC formatted CD-R, Teens Behind the Wheel.wmv, 236 MB, Created Jan. 12, 2011.Applicant
- David Cullen, “Getting a real eyeful”, Fleet Owner Magazine, Feb. 2002.Applicant
- Ronnie Rittenberry, “Eyes on the Road”, Jul. 2004.Applicant
- “HindSight v4.0 Users Guide”, DriveCam Video Systems, Apr. 25, 2005.Applicant
- Glenn Oster, “HindSight 20/20 v4.0 Software Installation”, 1 of 2, Jun. 20, 2003.Applicant
- Glenn Oster, “HindSight 20/20 v4.0 Software Installation”, 2 of 2, Jun. 20, 2003.Applicant
- DriveCam Extrinsic Evidence with Patent LR 4.1.a Disclosures, Nov. 8, 2011.Applicant
- “DriveCam, Inc's Disclosure of Proposed Constructions and Extrinsic Evidence Pursuant to Patent L.R. 4.1.a & 4.1.b” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Nov. 8, 2011.Applicant
- “Preliminary Claim Construction and Identification of Extrinsic Evidence of Defendant/Counterclaimant SmartDriveSystems, Inc.” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 8, 2011.Applicant
- “DriveCam, Inc's Disclosure of Responsive Constructions and Extrinsic Evidence Pursuant to Patent L.R. 4.1.c & 4.1d” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Nov. 15, 2011.Applicant
- “Responsive Claim Construction and Identification of Extrinsic Evidence of Defendant/Counterclaimant SmartDrive Systems, Inc.” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 15, 2011.Applicant
- “Joint Claim Construction Chart” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 11-CV-0997-H (RBB), for the Southern District of California, Document 43, filed Dec. 1, 2011, pp. 1-2.Applicant
- Joint Claim Construction Chart, U.S. Patent No. 6,389,340, “Vehicle Data Recorder” for Case No. 3:11-CV-00997-H-RBB, Document 43-1, filed Dec. 1, 2011, pp. 1-33.Applicant
- “Joint Claim Construction Worksheet” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 44, filed Dec. 1, 2011, pp. 1-2.Applicant
- Joint Claim Construction Worksheet, U.S. Patent No. 6,389,340, “Vehicle Data Reporter” for Case No. 3:11-CV-00997-H-RBB, Document 44-1, filed Dec. 1, 2011, pp. 1-10.Applicant
- “Answer to Amended Complaint; Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 47, filed Dec. 13, 2011, pp. 1-15.Applicant
- “First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 53, filed Dec. 20, 2011, pp. 1-48.Applicant
- “First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 55, filed Jan. 3, 2012, pp. 86-103.Applicant
- DriveCam, User's Manual for DriveCam Video Systems', HindSight 20/20 Software Version 4.0, S002751-S002804(2003).Applicant
- SmartDrives Systems, Inc.'s Production, S014246-S014255, Nov. 16, 2011.Applicant
- “Supplement to DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions” in DriveCam, Inc. v. SmartDrive Systems, Inc, Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Oct. 14, 2011.Applicant
- “DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Aug. 19, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit A, U.S. Patent 6,389,340. Aug. 11, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Patent 7,659,827. Aug. 19, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Patent 7,804,426. Aug. 19, 2011.Applicant
- U.S. Appl. No. 11/297,669, filed Dec. 8, 2005, File History.Applicant
- “Amended Complaint for Patent Infringement, Trade Secret Misappropriation, Unfair Competition and Conversion” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California, Document 34, filed Oct. 20, 2011, pp. 1-15.Applicant
- U.S. Appl. No. 11/296,906, filed Dec. 8, 2005, File History.Applicant
- U.S. Appl. No. 11/298,069, filed Dec. 9, 2005, File History.Applicant
- U.S. Appl. No. 11/299,028, filed Dec. 9, 2005, File History.Applicant
- U.S. Appl. No. 11/593,659, filed Nov. 7, 2006, File History.Applicant
- U.S. Appl. No. 11/593,682, filed Nov. 7, 2006, File History.Applicant
- U.S. Appl. No. 11/595,015, filed Nov. 9, 2006, File History.Applicant
- U.S. Appl. No. 11/637,754, filed Dec. 13, 2006, File History.Applicant
- U.S. Appl. No. 11/637,755, filed Dec. 13, 2006, File History.Applicant
- DriveCam, Inc., User's Manual for DriveCam Video Systems' Hindsight 20/20 Software Version 4.0 (2003).Applicant
- Gary and Sophia Rayner, Final Report for Innovations Deserving Exploratory Analysis (IDEA) Intelligent Transportation Systems (ITS) Programs' Project 84, I-Witness Black Box Recorder, San Diego, CA. Nov. 2001.Applicant
- Panasonic Corporation, Video Cassette Recorder (VCR) Operating Instructions for Models No. PV-V4020/PV-V4520 (1998) (Exhibit 8) (hereinafter “Panasonic”).Applicant
- JVC Company of America, JVC Video Cassette Recorder HR-IP820U Instructions (1996).Applicant
- Hans Fantel, Video; Search Methods Make a Difference in Picking VCR's, NY Times, Aug. 13, 1989.Applicant
- Dan Carr, Flash Video template: Video Presentation with Navigation, Jan. 16, 2006.Applicant
- I/O Port Racing Supplies' website discloses using Traqmate's Data Acquisition with Video Overlay system in conjunction with professional driver coaching sessions (available at http://www.ioportracing.com/Merchant2/merchant.mvc?Screen=CTGY&Category—Code=coaching)., printed from site on Jan. 11, 2012.Applicant
- GE published its VCR User's Guide for Model VG4255 in 1995.Applicant
- Adaptec published and sold its VideoOh! DVD software USB 2.0 Edition in at least Jan. 24, 2003.Applicant
- Traqmate GPS Data Acquisition's Traqmate Data Acquisition with Video Overlay system was used to create a video of a driving event on Oct. 2, 2005 (available at http://www.trackvision.net/phpBB2/viewtopic.php?t=51&sid=1184fbbcbe3be5c87ffa0f2ee6e2da76), printed from site on Jan. 11, 2012.Applicant
- David Vogeleer et al., Macromedia Flash Professional 8UNLEASHED (Sams Oct. 12, 2005) in Nov. 2005.Applicant
- Jean (DriveCam vendor), “DriveCam brochure”, Nov. 6, 2002.Applicant
- “The DriveCam”, Nov. 6, 2002.Applicant
- Jean (DriveCam vendor), “DC Data Sheet”, Nov. 6, 2002.Applicant
- “Driver Feedback System”, Jun. 12, 2001.Applicant
- Jean (DriveCam vendor), “Feedback Data Sheet”, Nov. 6, 2002.Applicant
- “Interior Camera Data Sheet”, Oct. 26, 2001.Applicant
- Jean (DriveCam vendor), “HindSight 20-20 Data Sheet”, Nov. 4, 2002.Applicant
- “DriveCam Driving Feedback System”, Mar. 15, 2004.Applicant
- Chris Woodyard, “Shuttles save with DriveCam”, Dec. 9, 2003.Applicant
- Julie Stevens, “DriveCam Services”, Nov. 15, 2004.Applicant
- Julie Stevens, “Program Support Roll-Out & Monitoring”, Jul. 13, 2004.Applicant
- Jessyca Wallace, “The DriveCam Driver Feedback System”, Apr. 6, 2004.Applicant
- Karen, “Managers Guide to the DriveCam Driving Feedback System”, Jul. 30, 2002.Applicant
- Del Lisk, “DriveCam Training Handout Ver4”, Feb. 3, 2005.Applicant
- Jessyca Wallace, “Overview of the DriveCam Program”, Dec. 15, 2005.Applicant
- “DriveCam—Illuminator Data Sheet”, Oct. 2, 2004.Applicant
- Karen, “Downloading Options to HindSight 20/20”, Aug. 6, 2002.Applicant
- Bill, “DriveCam—FAQ”, Dec. 12, 2003.Applicant
- David Maher, “DriveCam Brochure Folder”, Jun. 6, 2005.Applicant
- “Passenger Transportation Mode Brochure”, May 2, 2005.Applicant
- Quinn Maughan, “DriveCam Unit Installation”, Jul. 21, 2005.Applicant
- Glenn Oster, “Illuminator Installation”, Oct. 3, 2004.Applicant
- Quinn Maughan, “HindSight Installation Guide”, Sep. 29, 2005.Applicant
- Quinn Maughan, “HindSight Users Guide”, Jun. 20, 2005.Applicant
- “Ambulance Companies Use Video Technology to Improve Driving Behavior”, Ambulance Industry Journal, Spring 2003.Applicant
- Lisa Mckenna, “A Fly on the Windshield?”, Pest Control Technology Magazine, Apr. 2003.Applicant
- Quinn Maughan, “Enterprise Services”, Apr. 17, 2006.Applicant
- Quinn Maughan, “DriveCam Enterprise Services”, Jan. 5, 2006.Applicant
- Quinn Maughan, “DriveCam Managed Services”, Jan. 5, 2006.Applicant
- Quinn Maughan, “DriveCam Standard Edition”, Jan. 5, 2006.Applicant
- Kathy Latus (Latus Design), “Case Study—Time Warner Cable”, Sep. 23, 2005.Applicant
- Kathy Latus (Latus Design), “Case Study—Cloud 9 Shuttle”, Sep. 23, 2005.Applicant
- Kathy Latus (Latus Design), “Case Study—Lloyd Pest Control”, Jul. 19, 2005.Applicant
- Bill Siuru, “DriveCam Could Save You Big Bucks”, Land Line Magazine, May-Jun. 2000.Applicant
- J. Gallagher, “Lancer Recommends Tech Tool”, Insurance and Technology Magazine, Feb. 2002.Applicant