Vehicle operator performance history recording, scoring and reporting systems

Information

  • Patent Grant
  • 9761067
  • Patent Number
    9,761,067
  • Date Filed
    Thursday, October 30, 2014
    10 years ago
  • Date Issued
    Tuesday, September 12, 2017
    7 years ago
Abstract
A driver history report may include many factors to express performance or quality of driver service. Vehicle event recorders are coupled to systems which form an association between collected data and the vehicle operator in command of the vehicle at the event moment. Systems provide means for long-term storage of data particularly data in a structure which preserves the association between a driver and event records attributed to him. Special recall operations executed against stored data yields operator performance reporting—including a single value performance score indicative of a vehicle operator's performance and safety history. An analyzer system operates to recall data, particularly data from a plurality of events all associated with a single operator but recorded over an extended period of time. Data is arranged such that mathematical analysis may be applied independently to various data elements or data “fields” to produce performance metrics and ratios which reflect performance.
Description
BACKGROUND OF THE INVENTIONS

Field


The following invention disclosure is generally concerned with vehicle operator scoring and reporting and specifically concerned with automated systems which maintain a performance history associated with particular drivers.


Prior Art


The inventions presented in U.S. Pat. No. 6,947,817 by inventor Diem for non-intrusive diagnostic tools for testing oxygen sensor operation relates to a diagnostic system for testing a vehicle where such systems include a wireless communications link between a vehicle any remote network of server computers. In particular, a WiFi type access points allowed an analyzer to communicate by way the Internet with a server computer hosting and oxygen sensor SOAP (simple object access protocol) service. In a nutshell, the system relates to smog sensors for automobiles which communicate with remote servers by way of a WiFi communications links.


Video surveillance systems are used to provide video records of events, incidents, happenings, et cetera in locations of special interest. For example, retail banking offices are generally protected with video surveillance systems which provide video evidence in case of robbery. While video surveillance systems are generally used in fixed location scenarios, mobile video surveillance systems are also commonly used today.


In particular, video systems have been configured for use in conjunction with an automobile and especially for use with police cruiser type automobiles. As a police cruiser is frequently quite near the scene of an active crime, important image information may be captured by video cameras installed on the police cruiser. Specific activity of interest which may occur about an automobile is not always associated with crime and criminals. Sometimes events which occur in the environments immediately about an automobile are of interest for reasons having nothing to do with crime. In example, a simple traffic accident where two cars come together in a collision may be the subject of video evidence of value. Events and circumstances leading up to the collision accident may be preserved such that an accurate reconstruction can be created. This information is useful when trying come to a determination as to cause, fault and liability. As such, general use of video systems in conjunction with automobiles is quickly becoming an important tool useful for the protection of all. Some examples of the systems are illustrated below with reference to pertinent documents.


Inventor Schmidt presents in U.S. Pat. No. 5,570,127, a video recording system for a passenger vehicle, namely a school bus, which has two video cameras one for an inside bus view and one for a traffic view, a single recorder, and a system whereby the two cameras are multiplexed at appropriate times, to the recording device. A switching signal determines which of the two video cameras is in communication with the video recorder so as to view passengers on the passenger vehicle at certain times and passing traffic at other times.


Thomas Doyle of San Diego, Calif. and QUALCOMM Inc. also of San Diego, present an invention for a method and apparatus for detecting fault conditions in a vehicle data recording device to detect tampering or unauthorized access, in U.S. Pat. No. 5,586,130. The system includes vehicle sensors for monitoring one or more operational parameters of the vehicle. The fault detection technique contemplates storing a current time value at regular intervals during periods in which the recording device is provided with a source of main power. Inventor Doyle also teaches in the U.S. Pat. No. 5,815,071, a method and apparatus for monitoring parameters of vehicle electronic control units.


A “computerized vehicle log” is presented by Dan Kikinis of Saratoga Calif. in U.S. Pat. No. 5,815,093. The vehicle accident recording system employs a digital camera connected to a controller in nonvolatile memory, and an accident sensing interrupter. The oldest memory is overwritten by the newest images, until an accident is detected at which time the memory is blocked from further overwrites to protect the more vital images, which may include important information about the accident. Mr. Kikinis instructs that in preferred embodiments, the system has a communications port whereby stored images are downloaded after an accident to a digital device capable of displaying images. This feature is described in greater detail in the specification which indicates a wired download to a server having specialized image handling and processing software thereon.


Inventor Mr. Turner of Compton, Calif., no less, teaches an antitheft device for an automotive vehicle having both an audible alarm and visual monitor system. Video monitor operators are responsible for monitoring and handling an emergency situation and informing a 911 emergency station. This system is presented in U.S. Pat. No. 6,002,326.


A vehicle accident video recorder, in particular, a railroad vehicle accident video recorder, is taught by inventors Cox et al. In this system, a method and monitoring unit for recording the status of the railroad vehicle prior to a potential accident is presented. The monitoring unit continuously monitors the status of an emergency brake of the railroad vehicle and the status of a horn of the railroad vehicle. Video images are recorded and captured for a predetermined period of time after detecting that the emergency brake or horn blast has been applied as an event trigger. This invention is the subject of U.S. Pat. No. 6,088,635.


A vehicle crash data recorder is presented by inventor Ferguson of Bellaire, Ohio in U.S. Pat. No. 6,185,490. The apparatus is arranged with a three stage memory to record and retain information. And further it is equipped with a series and parallel connectors to provide instant on-scene access to accident data. It is important to note that Ferguson finds it important to include the possibility of on-site access to the data. Further, that Ferguson teaches use of a wired connection in the form of a serial or parallel hardwire connector. This teaching of Ferguson is common in many advanced systems configured as vehicle event recorders.


A traffic accident data recorder and traffic accident reproduction system and method is presented as U.S. Pat. No. 6,246,933. A plurality of sensors for registering vehicle operation parameters including at least one vehicle mounted digital video, audio camera is included for sensing storing and updating operational parameters. A rewritable, nonvolatile memory is provided for storing those processed operational parameters and video images and audio signals, which are provided by the microprocessor controller. Data is converted to a computer readable form and read by a computer such that an accident can be reconstructed via data collected.


U.S. Pat. No. 6,298,290 presented by Abe et al, teaches a memory apparatus for vehicle information data. A plurality of sensors including a CCD camera collision center of vehicle speed sensors, steering angle sensor, brake pressure sensor, acceleration sensor, are all coupled to a control unit. Further, the control unit passes information to a flash memory and a RAM memory subject to an encoder. The information collected is passed through a video output terminal. This illustrates another hardwire system and the importance placed by experts in the art on a computer hardware interface. This is partly due to the fact that video systems are typically data intensive and wired systems are necessary as they have bandwidth sufficient for transfers of large amounts of data.


Mazzilli of Bayside, N.Y. teaches in U.S. Pat. No. 6,333,759 a 360° automobile video camera system. A complex mechanical mount provides for a single camera to adjust its viewing angle giving a 360° range for video recording inside and outside of an automotive vehicle.


U.S. Pat. No. 6,389,339 granted to Inventor Just, of Alpharetta, Ga. teaches a vehicle operation monitoring system and method. Operation of a vehicle is monitored with an onboard video camera linked with a radio transceiver. A monitoring service includes a cellular telecommunications network to view a video data received from the transceiver to a home-base computer. These systems are aimed at parental monitoring of adolescent driving. The mobile modem is designed for transmitting live video information into the network as the vehicle travels.


Morgan, Hausman, Chilek, Hubenak, Kappler, Witz, and Wright with their heads together invented an advanced law enforcement and response technology in U.S. Pat. No. 6,411,874 granted Jun. 25, 2002. A central control system affords intuitive and easy control of numerous subsystems associated with a police car or other emergency vehicle. This highly integrated system provides advanced control apparatus which drives a plurality of detector systems including video and audio systems distributed about the vehicle. A primary feature included in this device includes an advanced user interface and display system, which permits high level driver interaction with the system.


Inventor Lambert teaches in U.S. Pat. No. 6,421,080 a “digital surveillance system with pre-event recording”. Pre-event recording is important in accident recording systems, because detection of the accident generally happens after the accident has occurred. A first memory is used for temporary storage. Images are stored in the temporary storage continuously until a trigger is activated which indicates an accident has occurred at which time images are transferred to a more permanent memory.


Systems taught by Gary Rayner in U.S. Pat. Nos. 6,389,340; 6,405,112; 6,449,540; and 6,718,239, each directed to cameras for automobiles which capture video images, both of forward-looking and driver views, and store recorded images locally on a mass storage system. An operator, at the end of the vehicle service day, puts a wired connector into a device port and downloads information into a desktop computer system having specialized application software whereby the images and other information can be played-back and analyzed at a highly integrated user display interface.


It is not possible in the systems Rayner teaches for an administrative operator to manipulate or otherwise handle the data captured in the vehicle at an off-site location without human intervention. It is necessary for a download operator to transfer data captured from the recorder unit device to a disconnected computer system. While proprietary ‘DriveCam’ files can be e-mailed or otherwise transferred through the Internet, those files are in a format with a can only be digested by desktop software running at a remote computer. It is necessary to have the DriveCam desktop application on the remote computer. In order that the files be properly read. In this way, data captured by the vehicles is totally unavailable to some parties having an interest in the data. Namely those parties who do not have access to a computer appropriately arranged with the specific DriveCam application software. A second and major disadvantage is systems presented by Rayner includes necessity that a human operator service the equipment each day in a manual download action.


Remote reporting and manipulation of automobile systems is not entirely new. The following are very important teachings relating to some automobile systems having a wireless communications link component.


Inventors Fan et al, teach inventions of methods and systems for detecting vehicle collision using global positioning system GPS. The disclosure of Jun. 12, 2001 resulted in granted U.S. Pat. No. 6,459,988. A GPS receiver is combined with wireless technology to automatically report accident and third parties remotely located. A system uses the GPS signals to determine when an acceleration value exceeds the preset threshold which is meant to be indicative of an accident having occurred.


Of particular interest include inventions presented by inventors Nagda et al., in the document numbered U.S. Pat. No. 6,862,524 entitled using location data to determine trafficking route information. In this system for determining and disseminating traffic information or route information, traffic condition information is collected from mobile units that provide their location or position information. Further route information may be utilized to determine whether a mobile unit is allowed or prohibited from traveling along a certain route.


A common assignee, @Road Inc., owns the preceding two patents in addition to the following: U.S. Pat. Nos. 6,529,159; 6,552,682; 6,594,576; 6,664,922; 6,795,017; 6,832,140; 6,867,733; 6,882,313; and 6,922,566. As such, @Road Inc., must be considered a major innovator in position technologies arts as they relate to mobile vehicles and remote server computers.


General Motors Corp. teaches in U.S. Pat. No. 6,728,612, an automated telematics test system and method. The invention provides a method and system testing a telematics system in a mobile vehicle a test command from a test center to a call center is based on a test script. The mobile vehicle is continuously in contact by way of cellular communication networks with a remotely located host computer.


Inventor Earl Diem and Delphi Technologies Inc., had granted to them on Sep. 20, 2005, U.S. Pat. No. 6,947,817. The non-intrusive diagnostic tool for sensing oxygen sensor operation include a scheme or an oxygen analyzer deployed in a mobile vehicle communicates by way of an access point to a remotely located server. A diagnostic heuristic is used to analyze the data and confirm proper operation of the sensor. Analysis may be performed by a mainframe computer quickly note from the actual oxygen sensor.


Similar patents including special relationships between mobile vehicles and remote host computers include those presented by various inventors in U.S. Pat. Nos. 6,735,503; 6,739,078; 6,760,757; 6,810,362; 6,832,141; and 6,850,823.


Another special group of inventions owned by Reynolds and Reynolds Holding Inc., is taught first by Lightner et al, in U.S. Pat. No. 6,928,348 issued Aug. 9, 2005. In these inventions, Internet based emission tests are performed on vehicles having special wireless couplings to computer networks. Data may be further transferred to entities of particular interest including the EPA or California Air Resources Board, for example, or particular insurance companies and other organizations concerned with vehicle emissions and environment.


Other patents held by Reynolds and Reynolds Holding Inc., include those relating to reporting of automobile performance parameters to remote servers via wireless links. Specifically, an onboard data bus OBD system is coupled to a microprocessor, by way of a standard electrical connector. The microprocessor periodically receives data and transmits it into the wireless communications system. This information is more fully described in U.S. patent granted Oct. 21, 2003 numbered U.S. Pat. No. 6,636,790. Inventors Lightner et al, present method and apparatus for remotely characterizing the vehicle performance. Data at the onboard data by his periodically received by a microprocessor and passed into a local transmitter. The invention specifically calls out transmission of data on a predetermined time interval. Thus these inventions do not anticipate nor include processing and analysis steps which result in data being passed at time other than expiration of the predetermined time period.


Reynolds and Reynolds Holding Inc., further describes systems where motor vehicles are coupled by wireless communications links to remote host servers in U.S. Pat. No. 6,732,031.


Additionally, recent developments are expressed in application for U.S. patent having document number: 2006/0095175 published on May 4, 2006. This disclosure describes a comprehensive systems having many important components. In particular, deWaal et al presents a ‘crash survivable apparatus’ in which information may be processed and recorded for later transmission into related coupled systems. An ability to rate a driver performance based upon data captured is particular feature described is some detail.


Also, inventor Boykin of Mt. Juliet Tenn. presents a “composite mobile digital information system” in U.S. Pat. No. 6,831,556. In these systems, a mobile server capable of transmitting captured information from a vehicle to a second location such as a building is described. In particular, a surveillance system for capturing video, audio, and data information is provided in a vehicle.


Inventors Lao et al, teach in their publication numbered 2005/0099498 of a “Digital Video System-Intelligent Information Management System” which is another application for U.S. patent published May 12, 2005. A digital video information management system for monitoring and managing a system of digital collection devices is specified. A central database receives similar information from a plurality of distributed coupled systems. Those distributed systems may also be subject to reset and update operations via the centralized server.


Finally, “Mobile and Vehicle-Based Digital Video System” is the title of U.S. patent application disclosure publication numbered 2005/0100329 also published on May 12, 2005. It also describes a vehicle based video capture and management system with digital recording devices optimized for field use. Because these systems deploy non-removable media for memory, they are necessarily coupled to data handling systems via various communications links to convey captured data to analysis servers.


SUMMARY OF THE INVENTIONS

Comes now, James Plante, Gregory Mauro, Ramesh Kasavaraju and Andrew Nickerson with inventions of vehicle operator performance history recording and reporting systems including devices and methods of automatically collecting and processing data over time to form a driver history report comprising performance information collected over a discrete time period.


Vehicle event recorders arranged to capture data relating to a particular event are additionally coupled to a system which forms an association between collected data and the vehicle operator. These systems further provide means for long-term storage of data relating to particular operators and events. Special recall operations executed against data stored as described, permits compilation of an operator performance report including a single value performance score. The single value operator performance score is indicative of a vehicle operator's performance and safety history.


A special system is provided to connect and associate collected data to the operator responsible for triggering an event. Once an appropriate association is made, information is kept in long-term storage where it may be joined by data from events occurring at a later time. An analyzer system operates to recall data, particularly data from a plurality of events all associated with a single operator but recorded over an extended period of time. Data is arranged in a manner such that algorithms and other mathematical analysis may be applied independently to various data elements or “fields” to produce performance metrics and ratios. Together, these factors may each be weighted and summed in accordance with specially devised a formulae including those having a single value solution. In best versions, this performance score may be normalized to a value between one and zero, where values closer to one represent the best operators enrolled in the program and values nearer zero reflect those operators of lowest performance. Thus, these systems provide a highly useful metric which quantifies operator performance history.


Objectives of these Inventions

It is a primary object of these inventions to provide advanced recording and reporting systems for motor vehicle exception events.


It is an object of these inventions to provide automated vehicle operator performance measure, recording and reporting systems.


It is a further object to provide automated vehicle operator performance tracking and history systems.


A better understanding can be had with reference to detailed description of preferred embodiments and with reference to appended drawings. Embodiments presented are particular ways to realize these inventions and are not inclusive of all ways possible. Therefore, there may exist embodiments that do not deviate from the spirit and scope of this disclosure as set forth by appended claims, but do not appear here as specific examples. It will be appreciated that a great plurality of alternative versions are possible.





BRIEF DESCRIPTION OF THE DRAWING FIGURES

These and other features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims and drawings where:



FIG. 1 is top-level block diagram to illustrate system primary elements;



FIG. 2 is a brief example collection of datasets to illustrate associations with a particular operator;



FIG. 3 is detailed block diagram further setting forth important elements of apparatus of these systems;



FIG. 4 illustrates in block diagram fundamental methods of these systems; and



FIG. 5 illustrates in further detail some preferred methods.





GLOSSARY OF SPECIAL TERMS

Throughout this disclosure, reference is made to some terms which may or may not be exactly defined in popular dictionaries as they are defined here. To provide a more precise disclosure, the following terms are presented with a view to clarity so that the true breadth and scope may be more readily appreciated. Although every attempt is made to be precise and thorough, it is a necessary condition that not all meanings associated with each term can be completely set forth. Accordingly, each term is intended to also include its common meaning which may be derived from general usage within the pertinent arts or by dictionary meaning. Where the presented definition is in conflict with a dictionary or arts definition, one must use the context of use and liberal discretion to arrive at an intended meaning. One will be well advised to error on the side of attaching broader meanings to terms used in order to fully appreciate the depth of the teaching and to understand all the intended variations.


Vehicle Event Recorder—VER


A vehicle event recorder is an electronic instrument coupled to an automobile and its environments to capture data in response to a detected exception or prescribed condition or ‘event’.


Vehicle Operator


The terms: ‘operator’, ‘vehicle operator’, or ‘driver’ herein means a person who operates or has operated a motor vehicle—for purposes of these inventions, a vehicle operator has one and only one unique identifying code associated therewith.


Event


An exception event occurs in a discrete time period surrounding detection of a prescribed condition. An exception event is declared upon toggle of a trigger mechanism which may be coupled to manual or automatic means of activating the trigger mechanism. An example of an exception event of particular interest, a vehicle involved in a crash subject high impact forces causes an accelerometer type trigger to be toggled resulting in a data capture action where data collected both before and after the event is captured and stored.


Event Record


An ‘event record’ is captured data associated with a particular event relating to the use and performance of an automobile including video and discrete numeric data. Event Record Dataset


An event record dataset is a combination of an event record, a vehicle operator identifier and an association between the two.


Report


A report is an output compiled from information stored in time from a plurality of exception events captured separately over an extended period.


Single Value Score


A single value score is a vehicle operator performance parameter or metric expressed numerically as a single value.


PREFERRED EMBODIMENTS OF THESE INVENTIONS

In accordance with each of the preferred embodiments of these inventions, apparatus for and methods of providing vehicle operator performance history recording and reporting are provided. It will be appreciated that each of embodiments described include both apparatus and method and that the apparatus and method of one preferred embodiment may be different than the apparatus and method of another embodiment.


Vehicle event recorders are arranged to capture video and discrete numeric data associated with a specific exception event in connection with a trigger; the captured video relating in-part to vehicle and driver performance. A vehicle event recorder also captures vehicle systems status information similarly in connection with a triggered event. Together, these data form an ‘event record’, which is effectively a detailed documentation of conditions relating to the nature of the event.


While a vehicle event recorder may include digitized and system status information, the data is not otherwise associated or connected with any vehicle operator. That is, an event record does not include attachment to the vehicle operator. Vehicle event recorders and their associated processing systems heretofore have not included automated means of identifying a unique driver. In some versions, event recorders of the arts may include one or more images of a driver, images from which a driver identity might be taken in a mental step process, i.e. a human recognition process, event recorders otherwise contain no discrete identity information with respect to operators.


In the systems first presented, a system component is an associator arranged to receive event records, further to receive discrete identity information from an operator ID system, and to form an association between the two thus connecting and enjoining them as an event record dataset. The associator, then transmits the dataset to a database for long-term storage. An analyzer may query the database to fetch select records in accordance with a particular request design. In some preferred versions, such requests may come from a user interface which permits human configuration of such requests.


Datasets/resultset may be recalled and transmitted from the database to the analyzer which includes an algorithm library. These datasets/resultset are formed of many elements or sometimes “data fields”. Algorithms may include mathematical operations which operate with regard to a particular data field or fields to produce a desired output. For example, when a group of datasets are recalled each having the same operator as defined by the operator ID, an algorithm may be applied to make a determination as to driving performance with particular regard to a specific vehicle operator. A group of data sets, all relating to a different event associated with the same driver can be analyzed for speed violations in example. It may be determined for example, that a particular driver had three speed violations during the last month. A report to reflect such a determination is prepared as an operator performance measure.


The system is comprised of the primary elements including: and associator; a database; and an analyzer. The associator receives as input event records and vehicle operator identification information. The associator forms an association between these data elements. Operator identification information which identifies a “current operator”, i.e. the operator who is operating the vehicle at the time of the occurrence of a declared exception event. Event record information is produced as a result of the event having occurred. Thus, it is some instant in time which connects a vehicle operator with captured event data. The associator forms the event record dataset and transmits that dataset as output to a database with which it is in communicative relation.


The database is arranged to receive event record datasets in a form which contains information about the physical nature of a vehicle and its environment during an event; information about driver/vehicle identity; as well as an association between these information records, whereby precisely one driver identity is associated with each event. The database is further arranged to provide output in response to requests or queries from exterior data consumers. Responses may be provided whereby a search filtered on specific indices produces a resultset comprising a plurality of datasets with a common factor; for example a unique vehicle operator. In this way, the database may provide a resultset to an analyzer of all events having an association with a specific driver. Of course other result sets of various specification are similarly arranged.


An analyzer is communicatively coupled to a database whereby it may make queries or requests for information and further receive data provided as database responses. The analyzer is provided with means to process received data to form statistical results. The analyzer might apply select algorithms to received data, the algorithms operating on specific elements of the datasets to yield a mathematical conclusion.


Thus, an associator is arranged to: receive event records; receive identification information; to form an association therebetween this forming prescribed data sets; and further to transmit those datasets to a database of suitable structure. The database is arranged to pass resultsets to an analyzer which applies various analysis in producing a statistical representation of a plurality of associated events. These are the primary elements of preferred versions of these systems.


While the preceding description presents in detail some important key elements and their relationships with others, important minority elements are also present and arranged to cooperate with those key elements as well as other minority elements. Minority elements include: operator/vehicle identification systems; vehicle event recorders; vehicle systems sensors and transducers; event trigger; user interface; algorithm library; operator performance measure reports; and finally an operator performance coefficient.


In these systems, some preferred versions include means of conveyance of vehicle operator identity. Vehicle operator identity must first be discretized and further must be unique with respect to each person authorized to operate suitably equipped vehicles. While persons in a room, each being familiar with the other, may identify which of the others is “Fred”, such human recognition is a straightforward operation for the human mind—but providing unique identities of persons in computer systems demand a bit of overhead. A discrete value identity code assignment is made for each valid operator. When an operator initiates use of a vehicle, an operator ID system determines the identity code associated with the operator and provides if to the associator.


In some preferred implementations, operator ID systems include a tactile input which permits users to express their identity by a key pad entry. Once a user keys in his/her code, the operator identity system can thereafter report accurately to the associator who is operating the vehicle. Events occurring during periods following ID entry can be properly allocated to the actual operator of the vehicle. Other operator ID schemes may be deployed in alternative versions of operator ID systems. In one such alternative, a scheduling program may assign a particular driver a particular vehicle on a certain day and at a certain time report the assignment to the operator ID system which then passes the ID info into the associator as it receives event records. Accordingly, some operator ID systems are “on-board” and some are “off-board”. While in some preferred versions it is anticipated that an operator ID system will be established as an on-board integrated with a vehicle event recorder; it is important to point out that this is entirely possible to create an alternative where the operator ID system is instead deployed as a subsystem exterior to the vehicle and vehicle event recorder.


An event record dataset is prepared by the associator for long-term storage in a database. An event record dataset includes an event record; an operator identifier and sometimes a vehicle identifier; and an association therebetween. As soon as event record data is joined with an operator/vehicle identifier, it is an event record dataset for purposes of this disclosure.


Since an event record arises from a single event in which only one operator may be on station, there exists a certain ‘one-to-one’ correspondence between any vehicle operator and any single event record. However many event record datasets may be compiled over time and each of those may include the same operator. So, there is a ‘one-to-many’ relationship between any vehicle operator and the event record datasets which may be stored in a database. In fact, an event record dataset only comes into existence as a result of an event having occurred and in these systems it is preferred that for each event which occurs, an event record dataset is formed.


An analyzer further includes an algorithm library. An algorithm library is stored set of algorithms which may be selectively invoked and applied to a group of datasets. Algorithms may be applied individually, or may be applied serially one after another. A properly arranged algorithm applied to a select group of datasets can yield a performance metric result. In best versions, an operator performance measure output is generated as a result of an algorithm being applied to a select group of datasets. And operator performance measure may include statistical compilation and presentation of data analysis which reflects performance with regard to particular operator, group of operators, vehicle or group of vehicles.


An operator or vehicle performance report O/V-PR is a report containing statistical information regarding the performance of a vehicle operator or vehicle operation. An operator performance report is an output from an analyzer which applies any of a prescribed group of algorithms to a plurality of event record dataset records; those datasets having been created over some extended period of time. Thus an O/V-PR is and historical account of events having occurred with particular connection to a certain driver or vehicle. Exception events which may occur from time-to-time result in production of data describing and documenting the event. Those data are associated with a particular operator identity and stored over time. An analyzer applies certain algorithms to data recalled from memory to produce a statistical report; an O/V-PR is therefore a compilation of analyzed data to produce results which expresses the historical nature of a vehicle operator's or vehicle's performance. An O/V-PR may be based upon all events captured over a specified period of time and is sometimes comprised of a plurality of weighted factors.



FIG. 1 illustrates an example arrangement of major system components from which these systems are formed. In brief, these systems are primarily comprised of an associator 1, connected via communications link to computer based relational database 2, further in communications with an analyzer 3 implemented as a computer system. The associator is arranged to receive an information package formed as an event record 4, as well as operator identification and sometimes vehicle identification information. Upon receipt of these information elements, the associator forms an association between them to effect an event record dataset. A single data record is formed in a structure which preserves the association between the event record and the operator/vehicle identification information and which further supports storage and manipulation by relational database type computing and storage systems. These arrangements of information may be embodied as a dataset which is assigned an ‘index’ or ‘key’ value to further assure and maintain the integrity of the information collection as a single unit. An analyzer is in two-way communication 7 with the database such that it can run queries against data stored therein and receive resultsets after those queries are executed. Finally, the analyzer is arranged to assemble process and analyze results received from the database and to output an operator performance measures to external systems.


A vehicle event recorder captures data relative to the operational states of vehicle subsystems as well as video images of environments about a vehicle while in use. Operational states of a vehicle may be reported to the vehicle event recorder by way of an on-board diagnostics system OBD which maintains monitoring of vehicle subsystems by various sensors so arranged. Data is captured upon detection of a special circumstance or unusual condition. A trigger may be devised to detect an unusual physical condition such as heavy shock or excessive speed. Upon detection of the condition, the trigger declares an exception event and initiates a data capture operation. An exception event is declared and the data capture action is performed during a brief time around the declared event moment. This captured information is connected with the particular vehicle operator authorized to use the vehicle at the time the information is captured by way of an operator identity code. Together, this information is stored at the database as a single information unit or ‘record’.


While it is possible to perform limited analysis on single event records, the true value of these systems is only realized when a plurality of events are analyzed via mathematical relationships which are applied to common elements (fields) between separate records captured at various times. That is, a first event record is stored in the database until another independent event occurs and that event record data is also added to the database. Under such circumstances, certain algorithms become very useful in expressing the performance quality of a particular operator of a vehicle or operators of a fleet of vehicles. A database may be arranged to receive records for many different operators, different vehicles, and even different fleets. When analysis is performed, records may be sorted and included/excluded from analysis on the basis of many considerations embodied as data fields.



FIG. 2 is provided to illustrate a database grid comprising 11 separate dataset records each associated with an exception event occurring at a different time. All 11 records are associated with a unique vehicle operator 21 identified as “Jones”. The event data records illustrated include information relating to whether an infraction 22 is involved, whether it is a speeding 23 case, and whether the event involves an accident 24. In addition, the date 25 of the event is recorded and a ‘miles-year-to-date’ 26 numeric value is included as part of the dataset. The data grid presented is for illustration purposes only and the reader will readily understand that any real system would certainly include many more data fields which contribute ultimately to the expression of an operator performance measure. For example, detailed speed data, braking and acceleration measurements, engine speed, steering position, et cetera. These factors and many others are omitted from the diagram to avoid a crowded illustration, but are explicitly meant to be included as part of any high performance system.


For this example, each record belongs to the vehicle operator named ‘Jones’ 27. A binary indication 28 marks the record capture on Jul. 14, 2005 as one in which an exception event is characterized as including a speeding incident. The event record captured Jul. 8, 2005 includes data 29 which indicates the event was classified as an ‘accident’. An event record of these example systems preferably includes date and mileage information which is useful for providing ‘related rate’ type performance measures. For example, we can use two separate event records 210, applying subtraction analysis therebetween to conclude that Jones has committed to speeding violations in a 31 day period. Another way to express Jones' performance with regard to speeding is to consider that mileage in computing a “speeding infractions per mile” measure, we can say that Jones has attracted two speeding violations in 248 miles or approximately equivalent to 0.8 violations per hundred miles. Of course, if we consider Jones' entire recorded history, we can figure Jones makes 0.02 speeding violations per hundred miles or: (3×100/14845). These illustrate very simplified mathematical analysis between related (by operator) event record data which express a driver performance measure.


It is important to direct attention to the automated nature of these systems. While it may not be precisely novel to merely compute “violations per mile” in connection with some particular vehicle operator, these systems stand alone and in stark contrast as they are based upon automated collection of event data in response to a triggered exception event and automated association of the captured data and the identity of operators to which it belongs. Further, these systems are based upon analysis which may be applied to so captured organized and stored data to yield a vehicle operator performance measure which expresses the quality of a vehicle operator. All systems not having vehicle mounted trigger event data capture devices, rely on manual manipulation and management of information to arrive at similar descriptions of driver performance. Presently one need only visit the local Department of Motor Vehicles to receive a computerized record of driving performance from data stored this way. However this record of driving performance is not compiled from automated systems which connect user identity with data captured in real-time on a vehicle mounted system.


Better appreciation is realized in a further consideration of the block diagram illustrated as FIG. 3. An associator 31 is coupled to a database 32 and analyzer 33 as shown. The associator is connected to receive event records 34 from a vehicle event recorder 35. When an event trigger 36 fires, an exception event is declared and data is captured by the vehicle event recorder, particularly: camera 37, and various vehicle subsystems coupled sensors 38. Captured data is assembled together to form an event record including both discrete numeric data and non-discrete data for example video image series. In addition to receiving event records from time-to-time, an associator also is coupled to a vehicle event recorder to receive operator identity information and sometimes vehicle identity information. An operator identity system 39 is provided to pass a unique identifier which is assigned to precisely one single vehicle operator to the associator. In some versions a vehicle identity system is similarly devised to pass vehicle identity information to the associator. The associator thereafter effects a connection or association between received event record and vehicle operator identity to perfect an event record dataset. An event record dataset 311 is comprised of event record data, operator and/or vehicle identity information, and association therebetween the two. As such, this information is passed into a data storage system configured as an electronic relational database. The event record dataset may be inserted into the database and created as a new record having an index value assigned thereto which assures the record can be distinguished from any other which may arrive later or has already arrived in the database.


In some best versions, and analyzer may include a user interface 312 which might be used to call prepared algorithms from a library 313 or alternatively might be used to manually form queries 314 which can be run against data stored in the database. Alternatively, procedures may be embodied as “stored procedures” in the database may be called by the analyzer in response to user inputs received at the user interface. Upon successful execution of a query or stored procedure, a resultset 315 is passed back to the analyzer. A resultset can be used to drive external systems. In a first instance, a result set can be used in a simple report 317 which expresses an operator performance measure. Just as financial and credit worthiness of us all are measured via a so called ‘FICO’ score, these systems will permit professional drivers to be easily measured and associated with a running single-value performance score or measure. Of course the systems will be adopted early by professional fleets and their employees, however it is entirely possible that all permitted drivers will soon benefit from these systems which operate to measure vehicle operator performance.


Output results (resultsets) may also be compared to a prescribed threshold value in an external system which takes an action based upon values arrived at in these resultsets. When an operator performance value or coefficient 318 exceeds a prescribed limit, an action may be set into motion. For example, if the driver performance value falls below some predetermined level, a driver may be subject to a counseling session. Thus, these resultsets can be used to automate a program of driver education and guidance in response to poor driving as detected in a vehicle event recorder.


Methods of these systems are similar in nature. They are nicely illustrated by block diagrams of FIGS. 4 and 5. In a first process, an associator is arranged to receive an event record 41. From a coupled vehicle event recorder in response to a triggered event, data captured during the event is passed to the associator. The associator further is connected to systems which provide identity indication with respect to vehicle operators and/or vehicles, and identity information is received 42 accordingly. In possession of data described, an association is formed 43 to connect the captured data which characterizes the event to the vehicle operator who was operating the vehicle at the time of the event declaration. A machine processable identity code for example is joined with the video and other data to form a complete event record dataset. A event record dataset is then in proper form to be conveyed 44 to a relational database system. In a process step, the associator in communication via prescribed database interfaces with the database system, conveys an event record comprising: event data, operator/vehicle identity information, and an association therebetween. The database system receives event record datasets from the associator and stores 45 them in durable memory. A relational database provides indexing means to assure record integrity and these event record datasets are handled in this manner. Each received event record data set is automatically assigned a unique identifier which maintains a connection between all fields or data elements of the record. While the data is in storage and under safekeeping at the database, a process loop 46 resets the vehicle event recorder to receive and convey additional event record datasets not related in time to the earlier received conveyance.


A database system in communicative relation with an analyzer conveys 47 resultsets to the analyzer for application of algorithms and mathematical analysis 48. In some preferred versions, the analyzer sends queries into the database system or calls stored procedures therein which may be executed to produce highly directed results sets. A final process may be initiated where an output action 49 is taken. In a simple first example of an output action, a report is produced where the report includes an operation performance measure. Another example includes that where an external system is prompted to begin. If a performance measure exceeds a prescribed value, a call to the external system is made as a result. This may be as simple as sending an e-mail warning via an electronic mail server (i.e. the external system).



FIG. 5 illustrates these methods in more detail. And associator forms an association 51 between event data including video and numeric data captured to characterize an exception event in a motor vehicle. The event record dataset is stored 52 with a unique identifier via an index scheme whereby the data can be sorted and processed as distinguishable from all similar records. To a collection of event records so stored in the database mathematical analysis may be applied 53 to produce an output 54 to a display, printer or other external system.


The method starts in response to an event trigger 55 of a vehicle event recorder which indicates the occurrence of an exception. In response thereto, video data is preserved 56 from periods before and after the event moment. In addition, discrete value data is also collected 57 from the electronic detectors coupled to vehicle subsystems. Data which characterizes the event is assembled together as an information packet to form an event record 58. The event record is passed 59 to the associator. Aside from this process, additional information is prepared and passed into the associator. In some versions, a user input is received 510 for example at a login keypad or smartcard reader, that user input specifying an authorized operator identity. A coded input prearranged with an association to a particular vehicle operator is received to alert the system as to the identity of the driver. An authorization check 511 may be used to verify a valid code. The current vehicle operator identity is conveyed 512 to the associator any time an event occurs such that it may be appropriately combined with and connected to the event data. The associator modifies the event record by adding operator and sometimes vehicle identity information thus forming an association therebetween to form an event record dataset. The dataset is arranged in a form suitable for cooperation with relational database structures including data type and indices considerations such that when conveyed to the database via an “insert” operation, the data is placed in table(s) as one of a plurality of similarly arranged records. The preceding portion of the method may be executed repeatedly in a loop to effect capture of many event record datasets that each have its own association with a particular single.


The method continues with the steps where analysis of collected data is applied. An analyzer is arranged to read database records and process them to arrive at a result which is based upon the information contained therein especially as it applies to a particular vehicle operator. The system is extremely powerful in-part because it can consider a plurality of event records each associated with a different event but identical operator. Accordingly, these analysis yield valuable performance indicators which relate to a vehicle operator.


In preferred embodiments, and analyzer includes an administrator workstation having a graphical user interface 514 whose state as manipulated by the administrator controls 515 how the analysis is taken up. A database query is formed 516 and transmitted 517 over a communications link to the database where the query may be applied against the stored data. After execution of the query, the database produces a resultset and conveys 518 that back to the analyzer as a query response.


From the input at the administrator database, an appropriate algorithm is selected 519 and applied to the resultset to further process the data. One important aspect includes forming an operator performance report 520 which reflects the quality of performance by a single or selected group of vehicle operators. In addition to a compound report which may include many separate factors, a single value performance score is computed 521. Separate performance measures are combined via weighted coefficients to arrive at a normalized single-value score. The score is particularly valuable because it is easily standardized and permits a relative basis upon which all participating drivers may be accurately compared. For example, highest performance driver in the system may be assigned a score of 1 and all others some value between 1 and 0 to reflect their performance in relation to the system the universe of operators.


A vehicle operator performance measure may be provided by a system having an associator; a data store; and an analyzer. The associator ‘connects’ or forms an association between event records and an operator identity as part of a dataset which is transmitted to the data store. An analyzer is arranged to apply mathematical processing and analysis against stored datasets to produce a vehicle operator performance measure.


In a vehicle event recorder, an exception event results in the capture of information which may be used to characterize the event and status of the vehicle and operator. Once information relating to a particular event is captured, that information is associated with a particular vehicle operator to form a dataset suitable for long term storage in a database. Events taking place at a later time which might be similarly stored, may include the same vehicle operator. As such, it is possible to run a statistical analysis on all events associated with a particular vehicle operator and to draw performance algorithms which yield a performance measure type result. For example, a first performance measure might simply include the number of events occurred per mile driven. Another performance indicator might be number of crash type incidents per mile driven. An more complex algorithm might include both of these measures and a weighting factor for each. For example: performance measure=(Events/Mile)*3+(Crashes/Mile)*8; where 3 and 8 are weighting factors.


As such, an associator is a subsystem arranged to form a connection between information captured in an event and information which uniquely identifies a vehicle operator; namely the vehicle operator responsible for the vehicle at the time of the event—a logged on driver. An associator comprises a logic processor arranged to receive both event data information and operator identity information and to assemble that information according to protocol demanded at a database. A database record structure having a one-to-one correspondence between events and vehicle operators is an example of an enforced relationship in such record structures prepared by an associator.


An analyzer is provided with a priori knowledge of these data structures such that it might execute machine operations against stored data which effect analysis on several event records; each of which may be associated with a particular vehicle operator or vehicle operator group. An analyzer might include: a graphical user interface; a query facility; and an algorithm library as part of its subsystems. The graphical user interface can be arranged to: receive inputs from a user; to drive query formation in agreement with received inputs; and further to select algorithms from the algorithm library. In this way, an analyzer reads and processes stored event data to formulate a result which is a vehicle operator performance measure.


These systems for producing a vehicle operator performance measure may include a set of electronic transducers coupled to various of the vehicle environments and systems to capture information relating to vehicle operation or performance. Outputs from these electronic transducers are assembled together in an ‘information package’ together as event records which may be taken up by the associator. By example, these sensors may include any of those from the group: imager; accelerometer; speedometer; position; orientation; time; and any of standard vehicle systems status indicators including: engine speed, temperature; braking; gear ratio; and steering wheel position.


In addition to these electronic transducers, a system also includes an operator identity system to make discrete and provide an indication which expresses a vehicle operator's identity. The expression of a vehicle operator's identity may be conveyed from the operator identity system to the associator where that identity indicator may become associated with various event data.


In a more complete sense, these systems are considered to also include the vehicle event recorder which has at least one imager, memory; and an event trigger. This vehicle event recorder being arranged to produce event records in response to a toggle action of an event trigger. Toggle of the event trigger not only causes information from said sensors to be captured, but also to be further associated with a particular vehicle operator identity.


In best versions, an operator identity system includes a memory with stored values each associated with at least one particular vehicle operator. An operator identity system may be at least partly integrated with a vehicle event recorder; or in contrast may be implemented in part at a download server.


This invention disclosure also includes methods. In particular, these methods may be expressed in general terms as including the following steps. A ‘receiving an event record’ step where a vehicle event recorder captures information relating to a declared exception event, i.e. in response to a trigger; for example a video record of environments about a subject vehicle and sensor data relating to a vehicles systems. A ‘receiving identity information’ step is performed where a discrete indication of a particular vehicle operator, or a unique identifier assigned to a particular vehicle or vehicle fleet, is received at an associator where the associator performs the next step.


A ‘forming an association’ step connects the event record with received vehicle operator identity information thus forming a dataset record having: event record, identity information, and the association therebetween. A well-formed database record might include: event record information, identity information, and an association therebetween. The database record includes a plurality of field elements, each field element having a prescribed data type and value assigned thereto, the values reflecting information received as an event record and identity information.


Further, the methods include storing the dataset record in a database for long term storage. Ideally, for a term long enough where other event records are also added to the database. Each dataset record has information from an event record captured at a time different than the capture time of all other dataset records.


Dataset records are recalled in a query step where they may be sorted and selectively chosen in accordance with an index—for example, all event records of the month of September associated with a certain driver. Upon the carefully selected records recalled as described, a mathematical analysis may be applied to produce an output which might reflect a vehicle operators performance. executing an algorithm to realize a ratio between the resultant of two algorithms applied to two different field elements.


A mathematical analysis is applied in a method step directed to address any plurality of event records. An prescribed algorithm arranged to effect a ratio between any two field elements is particularly useful in expressing some driver performance measures and those are explicitly part of these teachings. A ratio with a time based unit in the denominator is exemplary. For example, the “number of infractions per year” is a ratio of considerable importance for expressing a driver performance. Another is “number of infractions per mile”. Of course, reciprocals are equally effective in expressing the same information and are considered included alternatives.


Results from mathematical analysis may be expressed in several ways including real-time graphical display, printed reports, as inputs to triggers. Thus, methods of these inventions include ‘providing an output report’ step is further characterized as a report having a plurality of resultants produced by application of the mathematical analysis.


A driver performance report of particular importance includes a single-value performance coefficient which is derived from the results of and plurality of analysis. Weighted coefficients applied to algorithm resultants form basis for such single-value output in best arrangements.


One will now fully appreciate how video event recording systems provide foundation for systems which yield driver performance measures. Although the present inventions have been described in considerable detail with clear and concise language and with reference to certain preferred versions thereof including best modes anticipated by the inventors, other versions are possible. Therefore, the spirit and scope of the invention should not be limited by the description of the preferred versions contained therein, but rather by the claims appended hereto.

Claims
  • 1. A system configured to determine vehicle operator performance measures for a group of vehicle operators associated with a group of vehicles, wherein the group of vehicle operators includes a first vehicle operator and a second vehicle operator, wherein the group of vehicles includes a first vehicle and a second vehicle, the system comprising: an operator identity system configured to receive operator identity information that identifies periods of time a vehicle operator operates a vehicle, the operator identity information including a vehicle operator identifier, a vehicle identifier, and time ranges that correspond to the periods of time the vehicle operator operates the vehicle, wherein the vehicle operator is included in the group of vehicle operators, and wherein the vehicle is included in the group of vehicles;an associator configured to: obtain the operator identity information for the first vehicle operator and the second vehicle operator;receive first event records that include information related to vehicle operation during vehicle events from a first vehicle event recorder associated with the first vehicle;receive second event records that include information related to vehicle operation during vehicle events from a second vehicle event recorder associated with the second vehicle;associate the first event records for vehicle events that occur while the first vehicle operator operates the first vehicle with the operator identity information for the first vehicle operator;associate the second event records for vehicle events that occur while the second vehicle operator operates the second vehicle with the operator identity information for the second vehicle operator;form datasets comprising the operator identity information and the associated first and second event records; andtransmit the datasets to a data store; andan analyzer configured to determine, based on the datasets, a first vehicle operator performance measure for the first vehicle operator and a second vehicle operator performance measure for the second vehicle operator, wherein the determination uses a mathematical algorithm.
  • 2. The system of claim 1, wherein the operator identity system is configured to receive entry and/or selection of the operator identity information via a tactile input device, the tactile input device housed by a first housing that is physically separate and distinct from a vehicle event recorder housing that houses the first vehicle event recorder.
  • 3. The system of claim 1, wherein the analyzer is configured to select the mathematical algorithm from an algorithm library.
  • 4. The system of claim 3, wherein the analyzer is configured such that at least one of the algorithms in the algorithm library is a machine learning algorithm.
  • 5. The system of claim 4, wherein the analyzer is configured such that the machine learning algorithm fits historical data for multiple vehicle operators to a vehicle operator performance measure function, the vehicle operator performance measure function including one or more of a linear regression, a logistic regression, or a neural network.
  • 6. The system of claim 1, wherein the analyzer is configured such that the first vehicle operator performance measure indicates one or more of how well the first vehicle operator minimizes exposure to a risk of being in a vehicle accident, how well the first vehicle operator minimizes an amount of fuel consumed while operating the first vehicle, how well the first vehicle operator maximizes a usable life of mechanical components of the first vehicle, how well the first vehicle operator meets expectations while performing scheduled tasks, or how well the first vehicle operator meets corporate compliance standards and procedures associated with the first vehicle.
  • 7. The system of claim 1, wherein the second vehicle operator performance measure for the second vehicle operator is based on the first vehicle operator performance measure for the first vehicle operator.
  • 8. A system configured to determine vehicle operator performance measures for a group of vehicle operators associated with a group of vehicles, wherein the group of vehicle operators includes a first vehicle operator and a second vehicle operator, wherein the group of vehicles includes a first vehicle and a second vehicle, and wherein the system is further configured to improve vehicle operator performance, the system comprising: an operator identity system configured to receive operator identity information that identifies periods of time a vehicle operator operates a vehicle, wherein the vehicle operator is included in the group of vehicle operators, and wherein the vehicle is included in the group of vehicles;an associator configured to: obtain the operator identity information for the first vehicle operator and the second vehicle operator;receive first event records that include information related to vehicle operation during vehicle events from a first vehicle event recorder associated with the first vehicle;receive second event records that include information related to vehicle operation during vehicle events from a second vehicle event recorder associated with the second vehicle;associate the first event records for vehicle events that occur while the first vehicle operator operates the first vehicle with the operator identity information for the first vehicle operator;associate the second event records for vehicle events that occur while the second vehicle operator operates the second vehicle with the operator identity information for the second vehicle operator; andform datasets comprising the operator identity information and the associated first and second event records; andan analyzer configured to: analyze the datasets to determine a first vehicle operator performance measure for the first vehicle operator and a second vehicle operator performance measure for the second vehicle operator;generate vehicle operator performance counseling information based on the first vehicle operator performance measure and the second vehicle operator performance measure; andfacilitate presentation of the vehicle operator performance counseling information to the first vehicle operator and the second vehicle operator.
  • 9. The system of claim 8, wherein the analyzer is configured to generate the vehicle operator performance counseling information for the first vehicle operator responsive to the first vehicle operator performance measure breaching a vehicle operator performance measure threshold.
  • 10. The system of claim 8, wherein the associator is configured to receive the first event records that include information related to vehicle operation during multiple vehicle events that occur during the periods of time the first vehicle operator operates the first vehicle; and wherein the analyzer is configured to generate the vehicle operator performance counseling information for the first vehicle operator based on the multiple vehicle events.
  • 11. The system of claim 10, wherein the analyzer is configured such that the vehicle operator performance counseling information for the first vehicle operator changes based on one or more of a number of vehicle events that occur while the first vehicle operator operates the first vehicle, or a type of vehicle event that occurs while the first vehicle operator operates the first vehicle.
  • 12. The system of claim 8, wherein the analyzer is configured such that the generated vehicle operator performance counseling information is an alert.
  • 13. The system of claim 12, wherein the analyzer is configured to communicate the alert to an external computing system.
  • 14. The system of claim 8, wherein the analyzer is configured such that the vehicle operator performance counseling information includes progressive discipline information determined based on one or more of a quantity, a type, or a severity of vehicle events during the periods of time the first vehicle operator operates the first vehicle; and/or a number of prior counselling sessions; the progressive discipline information including an assessment of whether performance of the first vehicle operator improved in response to prior counselling sessions.
  • 15. A method for determining vehicle operator performance measures for a group of vehicle operators associated with a group of vehicles that include vehicle event recorders, wherein the group of vehicle operators includes a first vehicle operator and a second vehicle operator, wherein the group of vehicles includes a first vehicle and a second vehicle, the method comprising: receiving operator identity information that identifies periods of time a vehicle operator operates a vehicle, the operator identity information including a vehicle operator identifier, a vehicle identifier, and time ranges that correspond to the periods of time the vehicle operator operates the vehicle, wherein the vehicle operator is included in the group of vehicle operators, and wherein the vehicle is included in the group of vehicles;receiving, through transmission over a communications link, first event records that include information related to vehicle operation during vehicle events from a first vehicle event recorder associated with the first vehicle, wherein the first vehicle event recorder has captured sensor data from on-board diagnostics systems (OBDs);receiving, through transmission over the communications link, second event records that include information related to vehicle operation during vehicle events from a second vehicle event recorder associated with the second vehicle, wherein the second vehicle event recorder has captured sensor data from on-board diagnostics systems (OBDs);associating the first event records for vehicle events that occur while the first vehicle operator operates the first vehicle with the operator identity information for the first vehicle operator;associating the second event records for vehicle events that occur while the second vehicle operator operates the second vehicle with the operator identity information for the second vehicle operator;forming datasets comprising the operator identity information and the associated first and second event records;transmitting the datasets to a data store;determining, based on the datasets, a first vehicle operator performance measure for the first vehicle operator and a second vehicle operator performance measure for the second vehicle operator, wherein the determination uses a mathematical algorithm; andfacilitate presentation of the first vehicle operator performance measure and the second vehicle operator performance measure through a user interface.
  • 16. The method of claim 15, further comprising receiving entry and/or selection of the operator identity information via a tactile input device, the tactile input device housed by a first housing that is physically separate and distinct from a vehicle event recorder housing that houses the first vehicle event recorder.
  • 17. The method of claim 15, further comprising selecting the mathematical algorithm from an algorithm library.
  • 18. The method of claim 17, wherein at least one of the algorithms in the algorithm library is a machine learning algorithm.
  • 19. The method of claim 18, wherein the machine learning algorithm fits historical data for multiple vehicle operators to a vehicle operator performance measure function, the vehicle operator performance measure function including one or more of a linear regression, a logistic regression, or a neural network.
  • 20. The method of claim 15, wherein the vehicle operator performance measure indicates one or more of how well the first vehicle operator minimizes exposure to a risk of being in a vehicle accident, how well the first vehicle operator minimizes an amount of fuel consumed while operating the first vehicle, how well the first vehicle operator maximizes a usable life of mechanical components of the first vehicle, how well the first vehicle operator meets expectations while performing scheduled tasks, or how well the first vehicle operator meets corporate compliance standards and procedures associated with the first vehicle.
  • 21. The method of claim 15, wherein the second vehicle operator performance measure for the second vehicle operator is based on the first vehicle operator performance measure for the first vehicle operator.
  • 22. A method for determining vehicle operator performance measures for a group of vehicle operators associated with a group of vehicles that include vehicle event recorders, wherein the group of vehicle operators includes a first vehicle operator and a second vehicle operator, wherein the group of vehicles includes a first vehicle and a second vehicle, and wherein the method further improves vehicle operator performance, the method comprising: receiving operator identity information that identifies periods of time a first vehicle operator operates a first vehicle and a second vehicle operator operates a second vehicle;receiving, through transmission over a communications link, first event records from a first vehicle event recorder associated with the first vehicle, wherein the first event records include information related to vehicle operation during vehicle events, wherein the first vehicle event recorder has captured sensor data from on-board diagnostics systems (OBDs);receiving, through transmission over the communications link, second event records from a second vehicle event recorder associated with the second vehicle, wherein the second event records include information related to vehicle operation during vehicle events, wherein the second vehicle event recorder has captured sensor data from on-board diagnostics systems (OBDs);associating the first event records for vehicle events that occur while the first vehicle operator operates the first vehicle with the operator identity information for the first vehicle operator;associating the second event records for vehicle events that occur while the second vehicle operator operates the second vehicle with the operator identity information for the second vehicle operator;forming datasets comprising the operator identity information and the associated first and second event records;determining, based on the datasets, a first vehicle operator performance measure for the first vehicle operator and a second vehicle operator performance measure for the second vehicle operator;generating vehicle operator performance counseling information based on the first vehicle operator performance measure and the second vehicle operator performance measure; andfacilitating presentation of the vehicle operator performance counseling information, through a user interface, to the first vehicle operator and the second vehicle operator.
  • 23. The method of claim 22, further comprising generating the vehicle operator performance counseling information for the first vehicle operator responsive to the first vehicle operator performance measure breaching a vehicle operator performance measure threshold.
  • 24. The method of claim 22, further comprising receiving first event records that include information related to vehicle operation during multiple vehicle events that occur during the periods of time the first vehicle operator operates the first vehicle; and generating the vehicle operator performance counseling information for the first vehicle operator based on the multiple vehicle events.
  • 25. The method of claim 24, wherein the vehicle operator performance counseling information for the first vehicle operator changes based on one or more of a number of vehicle events that occur while the first vehicle operator operates the first vehicle, or a type of vehicle event that occurs while the first vehicle operator operates the first vehicle.
  • 26. The method of claim 22, wherein the generated vehicle operator performance counseling information is an alert.
  • 27. The method of claim 26, further comprising communicating the alert to an external computing system.
  • 28. The method of claim 22, wherein the vehicle operator performance counseling information includes progressive discipline information determined based on one or more of a quantity, a type, or a severity of vehicle events during the periods of time the first vehicle operator operates the first vehicle; and/or a number of prior counselling sessions; the progressive discipline information including an assessment of whether performance of the first vehicle operator improved in response to prior counselling sessions.
US Referenced Citations (841)
Number Name Date Kind
673203 Freund Apr 1901 A
673795 Hammer May 1901 A
673907 Johnson May 1901 A
676075 McDougall Jun 1901 A
679511 Richards Jul 1901 A
681036 Burg Aug 1901 A
681283 Waynick Aug 1901 A
681998 Swift Sep 1901 A
683155 Thompson Sep 1901 A
683214 Mansfield Sep 1901 A
684276 Lonergan Oct 1901 A
685082 Wood Oct 1901 A
685969 Campbell Nov 1901 A
686545 Selph Nov 1901 A
689849 Brown Dec 1901 A
691982 Sturgis Jan 1902 A
692834 Davis Feb 1902 A
694781 Prinz Mar 1902 A
2943141 Knight Jun 1960 A
3634866 Meyer Jan 1972 A
3781824 Caiati Dec 1973 A
3812287 Lemelson May 1974 A
3885090 Rosenbaum May 1975 A
3992656 Joy Nov 1976 A
4054752 Dennis Oct 1977 A
4072850 McGlynn Feb 1978 A
4258421 Juhasz Mar 1981 A
4271358 Schwarz Jun 1981 A
4276609 Patel Jun 1981 A
4280151 Tsunekawa Jul 1981 A
4281354 Conte Jul 1981 A
4401976 Stadelmayr Aug 1983 A
4409670 Herndon Oct 1983 A
4420773 Toyoda Dec 1983 A
4425097 Owens Jan 1984 A
4456931 Toyoda Jun 1984 A
4489351 d'Alayer de Costemore Dec 1984 A
4496995 Colles Jan 1985 A
4500868 Tokitsu Feb 1985 A
4528547 Rodney Jul 1985 A
4533962 Decker Aug 1985 A
4558379 Hutter Dec 1985 A
4588267 Pastore May 1986 A
4593313 Nagasaki Jun 1986 A
4621335 Bluish Nov 1986 A
4625210 Sagl Nov 1986 A
4630110 Cotton Dec 1986 A
4632348 Keesling Dec 1986 A
4638289 Zottnik Jan 1987 A
4646241 Ratchford Feb 1987 A
4651143 Yamanaka Mar 1987 A
4671111 Lemelson Jun 1987 A
4718685 Kawabe Jan 1988 A
4754255 Sanders Jun 1988 A
4758888 Lapidot Jul 1988 A
4763745 Eto Aug 1988 A
4785474 Bernstein Nov 1988 A
4789904 Peterson Dec 1988 A
4794566 Richards Dec 1988 A
4804937 Barbiaux Feb 1989 A
4806931 Nelson Feb 1989 A
4807096 Skogler Feb 1989 A
4814896 Heitzman Mar 1989 A
4837628 Sasaki Jun 1989 A
4839631 Tsuji Jun 1989 A
4843463 Michetti Jun 1989 A
4843578 Wade Jun 1989 A
4853856 Hanway Aug 1989 A
4853859 Morita Aug 1989 A
4866616 Takeuchi Sep 1989 A
4876597 Roy Oct 1989 A
4883349 Mittelhauser Nov 1989 A
4896855 Furnish Jan 1990 A
4926331 Windle May 1990 A
4930742 Schofield Jun 1990 A
4936533 Adams Jun 1990 A
4939652 Steiner Jul 1990 A
4942464 Milatz Jul 1990 A
4945244 Castleman Jul 1990 A
4949186 Peterson Aug 1990 A
4980913 Skret Dec 1990 A
4987541 Levente Jan 1991 A
4992943 McCracken Feb 1991 A
4993068 Piosenka Feb 1991 A
4995086 Lilley Feb 1991 A
5012335 Cohodar Apr 1991 A
5027104 Reid Jun 1991 A
5046007 McCrery Sep 1991 A
5050166 Cantoni Sep 1991 A
5056056 Gustin Oct 1991 A
5057820 Markson Oct 1991 A
5096287 Kakinami Mar 1992 A
5100095 Haan Mar 1992 A
5111289 Lucas May 1992 A
5140434 Van Aug 1992 A
5140436 Blessinger Aug 1992 A
5140438 Kurahashi et al. Aug 1992 A
5144661 Shamosh Sep 1992 A
5178448 Adams Jan 1993 A
5185700 Bezos Feb 1993 A
5196938 Blessinger Mar 1993 A
5223844 Mansell Jun 1993 A
5224211 Roe Jun 1993 A
5262813 Scharton Nov 1993 A
5283433 Tsien Feb 1994 A
5294978 Katayama Mar 1994 A
5305214 Komatsu Apr 1994 A
5305216 Okura Apr 1994 A
5308247 Dyrdek May 1994 A
5309485 Chao May 1994 A
5311197 Sorden May 1994 A
5321753 Gritton Jun 1994 A
5327288 Wellington Jul 1994 A
5330149 Haan Jul 1994 A
5343527 Moore Aug 1994 A
5353023 Mitsugi Oct 1994 A
5361326 Aparicio Nov 1994 A
5387926 Bellan Feb 1995 A
5388045 Kamiya Feb 1995 A
5388208 Weingartner Feb 1995 A
5404330 Lee Apr 1995 A
5408330 Squicciarini Apr 1995 A
5422543 Weinberg Jun 1995 A
5430431 Nelson Jul 1995 A
5430432 Camhi Jul 1995 A
5435184 Pineroli Jul 1995 A
5445024 Riley Aug 1995 A
5445027 Zoerner Aug 1995 A
5446659 Yamawaki Aug 1995 A
5455625 Englander Oct 1995 A
5455716 Suman Oct 1995 A
5465079 Bouchard Nov 1995 A
5473729 Bryant Dec 1995 A
5477141 Naether Dec 1995 A
5495242 Kick Feb 1996 A
5495243 McKenna Feb 1996 A
5497419 Hill Mar 1996 A
5499182 Ousborne Mar 1996 A
5504482 Schreder Apr 1996 A
5513011 Matsumoto Apr 1996 A
5515285 Garrett May 1996 A
5519260 Washington May 1996 A
5521633 Nakajima May 1996 A
5523811 Wada Jun 1996 A
5526269 Ishibashi Jun 1996 A
5530420 Tsuchiya Jun 1996 A
5532678 Kin Jul 1996 A
5537156 Katayama Jul 1996 A
5539454 Williams Jul 1996 A
5541590 Nishio Jul 1996 A
5544060 Fujii Aug 1996 A
5546191 Hibi Aug 1996 A
5546305 Kondo Aug 1996 A
5548273 Nicol Aug 1996 A
5552990 Ihara Sep 1996 A
5559496 Dubats Sep 1996 A
5568211 Bamford Oct 1996 A
5570087 Lemelson Oct 1996 A
5570127 Schmidt Oct 1996 A
5574424 Nguyen Nov 1996 A
5574443 Hsieh Nov 1996 A
D376571 Kokat Dec 1996 S
5581464 Woll Dec 1996 A
5586130 Doyle Dec 1996 A
5590948 Moreno Jan 1997 A
5596382 Bamford Jan 1997 A
5596647 Wakai Jan 1997 A
5600775 King Feb 1997 A
5610580 Lai Mar 1997 A
5612686 Takano Mar 1997 A
5631638 Kaspar May 1997 A
5638273 Coiner Jun 1997 A
5642106 Hancock Jun 1997 A
5646856 Kaesser Jul 1997 A
5652706 Morimoto Jul 1997 A
RE35590 Bezos Aug 1997 E
5654892 Fujii Aug 1997 A
5659355 Barron Aug 1997 A
5666120 Kline Sep 1997 A
5667176 Zamarripa Sep 1997 A
5669698 Veldman Sep 1997 A
5671451 Takahashi Sep 1997 A
5677979 Squicciarini Oct 1997 A
5680117 Arai Oct 1997 A
5680123 Lee Oct 1997 A
5686765 Washington Nov 1997 A
5686889 Hillis Nov 1997 A
5689442 Swanson Nov 1997 A
5696705 Zykan Dec 1997 A
5706362 Yabe Jan 1998 A
5706909 Bevins Jan 1998 A
5712679 Coles Jan 1998 A
5717456 Rudt Feb 1998 A
5719554 Gagnon Feb 1998 A
5758299 Sandborg May 1998 A
5781101 Stephen Jul 1998 A
5781145 Williams Jul 1998 A
5784007 Pepper Jul 1998 A
5784021 Oliva Jul 1998 A
5784521 Nakatani Jul 1998 A
5790403 Nakayama Aug 1998 A
5790973 Blaker Aug 1998 A
5793308 Rosinski Aug 1998 A
5793420 Schmidt Aug 1998 A
5793739 Tanaka Aug 1998 A
5793985 Natarajan Aug 1998 A
5794165 Minowa Aug 1998 A
5797134 McMillan Aug 1998 A
5798458 Monroe Aug 1998 A
5800040 Santo Sep 1998 A
5802545 Coverdill Sep 1998 A
5802727 Blank Sep 1998 A
5805079 Lemelson Sep 1998 A
5813745 Fant Sep 1998 A
5815071 Doyle Sep 1998 A
5815093 Kikinis Sep 1998 A
5819198 Peretz Oct 1998 A
5825284 Dunwoody Oct 1998 A
5825412 Hobson Oct 1998 A
5844505 Van Dec 1998 A
5845733 Wolfsen Dec 1998 A
5867802 Borza Feb 1999 A
5877897 Schofield Mar 1999 A
5896167 Omae Apr 1999 A
5897602 Mizuta Apr 1999 A
5897606 Miura Apr 1999 A
5899956 Chan May 1999 A
5901806 Takahashi May 1999 A
5914748 Parulski Jun 1999 A
5919239 Fraker Jul 1999 A
5926210 Hackett Jul 1999 A
5928291 Jenkins Jul 1999 A
5938321 Bos Aug 1999 A
5946404 Bakshi Aug 1999 A
5948038 Daly Sep 1999 A
5959367 Ofarrell Sep 1999 A
5978017 Tino Nov 1999 A
6002326 Turner Dec 1999 A
6006148 Strong Dec 1999 A
6008723 Yassan Dec 1999 A
6008841 Charlson Dec 1999 A
6009370 Minowa Dec 1999 A
6011492 Garesche Jan 2000 A
6028528 Lorenzetti Feb 2000 A
6037860 Zander Mar 2000 A
6037977 Peterson Mar 2000 A
6041410 Hsu Mar 2000 A
6049079 Noordam Apr 2000 A
6060989 Gehlot May 2000 A
6064792 Fox May 2000 A
6067488 Tano May 2000 A
6076026 Jambhekar Jun 2000 A
6084870 Wooten Jul 2000 A
6088635 Cox Jul 2000 A
6092008 Bateman Jul 2000 A
6092021 Ehlbeck Jul 2000 A
6092193 Loomis Jul 2000 A
6100811 Hsu Aug 2000 A
6111254 Eden Aug 2000 A
6118768 Bhatia Sep 2000 A
6122738 Millard Sep 2000 A
6141611 Mackey Oct 2000 A
6144296 Ishida Nov 2000 A
6147598 Murphy Nov 2000 A
6151065 Steed Nov 2000 A
6163338 Johnson Dec 2000 A
6163749 McDonough Dec 2000 A
6167186 Kawasaki Dec 2000 A
6170742 Yacoob Jan 2001 B1
6181373 Coles Jan 2001 B1
6185490 Ferguson Feb 2001 B1
6195605 Tabler Feb 2001 B1
6200139 Clapper Mar 2001 B1
6208919 Barkesseh Mar 2001 B1
6211907 Scaman Apr 2001 B1
6218960 Ishikawa Apr 2001 B1
6246933 Bague Jun 2001 B1
6246934 Otake Jun 2001 B1
6252544 Hoffberg Jun 2001 B1
6253129 Jenkins Jun 2001 B1
6259475 Ramachandran Jul 2001 B1
6263265 Fera Jul 2001 B1
6266588 McClellan Jul 2001 B1
6298290 Abe Oct 2001 B1
6300875 Schafer Oct 2001 B1
6324450 Iwama Nov 2001 B1
6333759 Mazzilli Dec 2001 B1
6337622 Sugano Jan 2002 B1
6349250 Hart Feb 2002 B1
6353734 Wright Mar 2002 B1
6356823 Iannotti Mar 2002 B1
6360147 Lee Mar 2002 B1
6366207 Murphy Apr 2002 B1
6389339 Just May 2002 B1
6389340 Rayner May 2002 B1
6400835 Lemelson Jun 2002 B1
6405112 Rayner Jun 2002 B1
6405132 Breed Jun 2002 B1
6408232 Cannon Jun 2002 B1
6411874 Morgan Jun 2002 B2
6421080 Lambert Jul 2002 B1
6434510 Callaghan Aug 2002 B1
6449540 Rayner Sep 2002 B1
6456321 Ito Sep 2002 B1
6459988 Fan Oct 2002 B1
6470241 Yoshikawa Oct 2002 B2
6472771 Frese Oct 2002 B1
6490513 Fish Dec 2002 B1
6493650 Rodgers Dec 2002 B1
6505106 Lawrence Jan 2003 B1
6507838 Syeda-Mahmood Jan 2003 B1
6508400 Ishifuji Jan 2003 B1
6516256 Hartmann Feb 2003 B1
6518881 Monroe Feb 2003 B2
6525672 Chainer Feb 2003 B2
6529159 Fan Mar 2003 B1
6535804 Chun Mar 2003 B1
6552682 Fan Apr 2003 B1
6556905 Mittelsteadt Apr 2003 B1
6559769 Anthony May 2003 B2
6574538 Sasaki Jun 2003 B2
6575902 Burton Jun 2003 B1
6580983 Laguer-Diaz Jun 2003 B2
6594576 Fan Jul 2003 B2
6611740 Lowrey Aug 2003 B2
6611755 Coffee Aug 2003 B1
6624611 Kirmuss Sep 2003 B2
6629029 Giles Sep 2003 B1
6629030 Klausner Sep 2003 B2
6636791 Okada Oct 2003 B2
6664922 Fan Dec 2003 B1
6679702 Rau Jan 2004 B1
6684137 Takagi Jan 2004 B2
6694483 Nagata Feb 2004 B1
6701234 Vogelsang Mar 2004 B1
6714894 Tobey Mar 2004 B1
6718239 Rayner Apr 2004 B2
6721640 Glenn Apr 2004 B2
6728612 Carver Apr 2004 B1
6732031 Lightner May 2004 B1
6732032 Banet May 2004 B1
6735503 Ames May 2004 B2
6737954 Chainer May 2004 B2
6738697 Breed May 2004 B2
6739078 Morley May 2004 B2
6741168 Webb May 2004 B2
6745153 White Jun 2004 B2
6747692 Patel Jun 2004 B2
6748305 Klausner Jun 2004 B1
6760757 Lundberg Jul 2004 B1
6762513 Landgraf Jul 2004 B2
6779716 Grow Aug 2004 B1
6795017 Puranik Sep 2004 B1
6795111 Mazzilli Sep 2004 B1
6795759 Doyle Sep 2004 B2
6798743 Ma Sep 2004 B1
6804590 Sato Oct 2004 B2
6810362 Adachi Oct 2004 B2
6812831 Ikeda Nov 2004 B2
6819989 Maeda Nov 2004 B2
6831556 Boykin Dec 2004 B1
6832140 Fan Dec 2004 B2
6832141 Skeen Dec 2004 B2
6836712 Nishina Dec 2004 B2
6842762 Raithel Jan 2005 B2
6847873 Li Jan 2005 B1
6850823 Eun Feb 2005 B2
6859695 Klausner Feb 2005 B2
6862524 Nagda Mar 2005 B1
6865457 Mittelsteadt Mar 2005 B1
6867733 Sandhu Mar 2005 B2
6873261 Anthony Mar 2005 B2
6882313 Fan Apr 2005 B1
6882912 DiLodovico Apr 2005 B2
6894606 Forbes May 2005 B2
6895248 Akyol May 2005 B1
6898492 De Leon May 2005 B2
6898493 Ehrman May 2005 B2
6919823 Lock Jul 2005 B1
6922566 Puranik Jul 2005 B2
6928348 Lightner Aug 2005 B1
6931309 Phelan Aug 2005 B2
6947817 Diem Sep 2005 B2
6950122 Mirabile Sep 2005 B1
6954223 Miyazawa Oct 2005 B2
6988034 Marlatt Jan 2006 B1
7012632 Freeman Mar 2006 B2
7020548 Saito Mar 2006 B2
7023333 Blanco Apr 2006 B2
7039510 Gumpinger May 2006 B2
7076348 Bucher Jul 2006 B2
7079927 Tano Jul 2006 B1
7082359 Breed Jul 2006 B2
7082382 Rose et al. Jul 2006 B1
7088387 Freeman Aug 2006 B1
7095782 Cohen Aug 2006 B1
7098812 Hirota Aug 2006 B2
7100190 Johnson Aug 2006 B2
7113853 Hecklinger Sep 2006 B2
7117075 Larschan Oct 2006 B1
7119832 Blanco Oct 2006 B2
7138904 Dutu Nov 2006 B1
7155321 Bromley Dec 2006 B2
7177738 Diaz Feb 2007 B2
7209833 Isaji Apr 2007 B2
7239252 Kato Jul 2007 B2
7265663 Steele Sep 2007 B2
7266507 Simon Sep 2007 B2
7272179 Siemens Sep 2007 B2
7308341 Schofield Dec 2007 B2
7317974 Luskin Jan 2008 B2
7348895 Lagassey Mar 2008 B2
7349027 Endo Mar 2008 B2
7370261 Winarski May 2008 B2
7382933 Dorai Jun 2008 B2
7386376 Basir Jun 2008 B2
7389178 Raz Jun 2008 B2
7457693 Olsen Nov 2008 B2
7471189 Vastad Dec 2008 B2
7471192 Hara Dec 2008 B2
7536457 Miller May 2009 B2
7548586 Mimar Jun 2009 B1
7561054 Raz Jul 2009 B2
7584033 Mittelsteadt Sep 2009 B2
7623754 McKain Nov 2009 B1
7659827 Gunderson Feb 2010 B2
7667731 Kreiner Feb 2010 B2
7689001 Kim Mar 2010 B2
7702442 Takenaka Apr 2010 B2
7725216 Kim May 2010 B2
7768548 Silvernail Aug 2010 B2
7783956 Ko Aug 2010 B2
7804426 Etcheson Sep 2010 B2
7821421 Tamir Oct 2010 B2
7845560 Emanuel Dec 2010 B2
7853376 Peng Dec 2010 B2
7868912 Venetianer Jan 2011 B2
7893958 D'Agostino Feb 2011 B1
7940250 Forstall May 2011 B2
7941258 Mittelsteadt May 2011 B1
7974748 Goerick Jul 2011 B2
8068979 Breed Nov 2011 B2
8090598 Bauer Jan 2012 B2
8113844 Huang Feb 2012 B2
8139820 Plante Mar 2012 B2
8140358 Ling Mar 2012 B1
8239092 Plante Aug 2012 B2
8311858 Everett Nov 2012 B2
8314708 Gunderson Nov 2012 B2
8321066 Becker Nov 2012 B2
8417562 Siemens Apr 2013 B1
8508353 Cook Aug 2013 B2
8538696 Cassanova Sep 2013 B1
8564426 Cook Oct 2013 B2
8564446 Gunderson Oct 2013 B2
8571755 Plante Oct 2013 B2
8577703 McClellan Nov 2013 B2
8606492 Botnen Dec 2013 B1
8634958 Chiappetta Jan 2014 B1
8635557 Geise Jan 2014 B2
8676428 Richardson Mar 2014 B2
8744642 Nemat-Nasser Jun 2014 B2
8775067 Cho Jul 2014 B2
8781292 Ross Jul 2014 B1
8803695 Denson Aug 2014 B2
8805110 Rhoads Aug 2014 B2
8849501 Cook Sep 2014 B2
8855847 Uehara Oct 2014 B2
8862395 Richardson Oct 2014 B2
8868288 Plante Oct 2014 B2
8880279 Plante Nov 2014 B2
8892310 Palmer Nov 2014 B1
8989959 Plante Mar 2015 B2
8996240 Plante Mar 2015 B2
9085362 Kilian Jul 2015 B1
9607526 Hsu-Hoffman Mar 2017 B1
20010005217 Hamilton Jun 2001 A1
20010005804 Rayner Jun 2001 A1
20010018628 Jenkins Aug 2001 A1
20010020204 Runyon Sep 2001 A1
20010052730 Baur Dec 2001 A1
20020019689 Harrison Feb 2002 A1
20020027502 Mayor Mar 2002 A1
20020029109 Wong Mar 2002 A1
20020035422 Sasaki Mar 2002 A1
20020044225 Rakib Apr 2002 A1
20020059453 Eriksson May 2002 A1
20020061758 Zarlengo May 2002 A1
20020067076 Talbot Jun 2002 A1
20020087240 Raithel Jul 2002 A1
20020091473 Gardner Jul 2002 A1
20020105438 Forbes Aug 2002 A1
20020107619 Klausner Aug 2002 A1
20020111725 Burge Aug 2002 A1
20020111756 Modgil Aug 2002 A1
20020118206 Knittel Aug 2002 A1
20020120374 Douros Aug 2002 A1
20020135679 Scaman Sep 2002 A1
20020138587 Koehler Sep 2002 A1
20020163532 Thomas Nov 2002 A1
20020169529 Kim Nov 2002 A1
20020169530 Laguer-Diaz Nov 2002 A1
20020183905 Maeda Dec 2002 A1
20030016753 Kim Jan 2003 A1
20030028298 Macky Feb 2003 A1
20030053433 Chun Mar 2003 A1
20030055557 Dutta Mar 2003 A1
20030065805 Barnes Apr 2003 A1
20030067541 Joao Apr 2003 A1
20030079041 Parrella Apr 2003 A1
20030080713 Kirmuss May 2003 A1
20030080878 Kirmuss May 2003 A1
20030081121 Kirmuss May 2003 A1
20030081122 Kirmuss May 2003 A1
20030081127 Kirmuss May 2003 A1
20030081128 Kirmuss May 2003 A1
20030081934 Kirmuss May 2003 A1
20030081935 Kirmuss May 2003 A1
20030095688 Kirmuss May 2003 A1
20030112133 Webb Jun 2003 A1
20030125854 Kawasaki Jul 2003 A1
20030144775 Klausner Jul 2003 A1
20030152145 Kawakita Aug 2003 A1
20030154009 Basir Aug 2003 A1
20030158638 Yakes Aug 2003 A1
20030177187 Levine Sep 2003 A1
20030187704 Hashiguchi Oct 2003 A1
20030191568 Breed Oct 2003 A1
20030195678 Betters et al. Oct 2003 A1
20030214585 Bakewell Nov 2003 A1
20030220835 Barnes Nov 2003 A1
20030222880 Waterman Dec 2003 A1
20040008255 Lewellen Jan 2004 A1
20040033058 Reich Feb 2004 A1
20040039503 Doyle Feb 2004 A1
20040039504 Coffee Feb 2004 A1
20040044452 Bauer Mar 2004 A1
20040044592 Ubik Mar 2004 A1
20040054444 Abeska Mar 2004 A1
20040054513 Laird Mar 2004 A1
20040054689 Salmonsen Mar 2004 A1
20040064245 Knockeart Apr 2004 A1
20040070926 Boykin Apr 2004 A1
20040083041 Skeen Apr 2004 A1
20040088090 Wee May 2004 A1
20040103008 Wahlbin May 2004 A1
20040103010 Wahlbin May 2004 A1
20040104842 Drury Jun 2004 A1
20040111189 Miyazawa Jun 2004 A1
20040117638 Monroe Jun 2004 A1
20040138794 Saito Jul 2004 A1
20040145457 Schofield et al. Jul 2004 A1
20040153244 Kellum Aug 2004 A1
20040153362 Bauer Aug 2004 A1
20040167689 Bromley Aug 2004 A1
20040179600 Wells Sep 2004 A1
20040181326 Adams Sep 2004 A1
20040184548 Kerbiriou Sep 2004 A1
20040203903 Wilson Oct 2004 A1
20040209594 Naboulsi Oct 2004 A1
20040210353 Rice Oct 2004 A1
20040230345 Tzamaloukas Nov 2004 A1
20040230370 Tzamaloukas Nov 2004 A1
20040230373 Tzamaloukas Nov 2004 A1
20040230374 Tzamaloukas Nov 2004 A1
20040233284 Lesesky Nov 2004 A1
20040236474 Chowdhary Nov 2004 A1
20040236476 Chowdhary Nov 2004 A1
20040243285 Gounder Dec 2004 A1
20040243308 Irish Dec 2004 A1
20040243668 Harjanto Dec 2004 A1
20040254689 Blazic Dec 2004 A1
20040254698 Hubbard Dec 2004 A1
20040267419 Jeng Dec 2004 A1
20050021199 Zimmerman Jan 2005 A1
20050043869 Funkhouser Feb 2005 A1
20050060070 Kapolka Mar 2005 A1
20050060071 Winner Mar 2005 A1
20050065716 Timko Mar 2005 A1
20050073585 Ettinger Apr 2005 A1
20050078423 Kim Apr 2005 A1
20050088291 Blanco Apr 2005 A1
20050099498 Lao May 2005 A1
20050100329 Lao May 2005 A1
20050102074 Kolls May 2005 A1
20050125117 Breed Jun 2005 A1
20050131585 Luskin Jun 2005 A1
20050131595 Luskin Jun 2005 A1
20050131597 Raz Jun 2005 A1
20050136949 Barnes Jun 2005 A1
20050137757 Phelan Jun 2005 A1
20050137796 Gumpinger Jun 2005 A1
20050146458 Carmichael Jul 2005 A1
20050149238 Stefani Jul 2005 A1
20050149259 Cherveny Jul 2005 A1
20050152353 Couturier Jul 2005 A1
20050159964 Sonnenrein Jul 2005 A1
20050166258 Vasilevsky Jul 2005 A1
20050168258 Poskatcheev Aug 2005 A1
20050171692 Hamblen Aug 2005 A1
20050174217 Basir Aug 2005 A1
20050182538 Phelan Aug 2005 A1
20050182824 Cotte Aug 2005 A1
20050185052 Raisinghani Aug 2005 A1
20050185936 Lao Aug 2005 A9
20050192749 Flann Sep 2005 A1
20050197748 Hoist Sep 2005 A1
20050200714 Marchese Sep 2005 A1
20050203683 Olsen Sep 2005 A1
20050206741 Raber Sep 2005 A1
20050212920 Evans Sep 2005 A1
20050216144 Baldassa Sep 2005 A1
20050228560 Doherty Oct 2005 A1
20050233805 Okajima Oct 2005 A1
20050251304 Cancellara Nov 2005 A1
20050258942 Manasseh Nov 2005 A1
20050264691 Endo Dec 2005 A1
20050283284 Grenier Dec 2005 A1
20060001671 Kamijo Jan 2006 A1
20060007151 Ram Jan 2006 A1
20060011399 Brockway Jan 2006 A1
20060015233 Olsen Jan 2006 A1
20060022842 Zoladek Feb 2006 A1
20060025897 Shostak Feb 2006 A1
20060030986 Peng Feb 2006 A1
20060040239 Cummins Feb 2006 A1
20060047380 Welch Mar 2006 A1
20060053038 Warren Mar 2006 A1
20060055521 Blanco Mar 2006 A1
20060057543 Roald Mar 2006 A1
20060058950 Kato Mar 2006 A1
20060072792 Toda Apr 2006 A1
20060078853 Lanktree Apr 2006 A1
20060092043 Lagassey May 2006 A1
20060095175 Dewaal May 2006 A1
20060095199 Lagassey May 2006 A1
20060095349 Morgan May 2006 A1
20060103127 Lie May 2006 A1
20060106514 Liebl May 2006 A1
20060111817 Phelan May 2006 A1
20060122749 Phelan Jun 2006 A1
20060129578 Kim Jun 2006 A1
20060142913 Coffee Jun 2006 A1
20060143435 Kwon Jun 2006 A1
20060147187 Takemoto Jul 2006 A1
20060161960 Benoit Jul 2006 A1
20060168271 Pabari Jul 2006 A1
20060178793 Hecklinger Aug 2006 A1
20060184295 Hawkins Aug 2006 A1
20060200008 Moore-Ede Sep 2006 A1
20060209090 Kelly et al. Sep 2006 A1
20060209840 Paatela Sep 2006 A1
20060212195 Veith Sep 2006 A1
20060226344 Werth Oct 2006 A1
20060229780 Underdahl Oct 2006 A1
20060242680 Johnson Oct 2006 A1
20060247833 Malhotra Nov 2006 A1
20060253307 Warren Nov 2006 A1
20060259218 Wu Nov 2006 A1
20060261931 Cheng Nov 2006 A1
20070001831 Raz Jan 2007 A1
20070005404 Raz Jan 2007 A1
20070027583 Tamir Feb 2007 A1
20070027726 Warren Feb 2007 A1
20070043487 Krzystofczyk Feb 2007 A1
20070120948 Fujioka May 2007 A1
20070124332 Ballesty May 2007 A1
20070127833 Singh Jun 2007 A1
20070132773 Plante Jun 2007 A1
20070135979 Plante Jun 2007 A1
20070135980 Plante Jun 2007 A1
20070136078 Plante Jun 2007 A1
20070142986 Alaous Jun 2007 A1
20070143499 Chang Jun 2007 A1
20070150138 Plante Jun 2007 A1
20070150140 Seymour Jun 2007 A1
20070173994 Kubo Jul 2007 A1
20070179691 Grenn Aug 2007 A1
20070183635 Weidhaas Aug 2007 A1
20070208494 Chapman Sep 2007 A1
20070213920 Igarashi Sep 2007 A1
20070216521 Guensler Sep 2007 A1
20070219685 Plante Sep 2007 A1
20070219686 Plante Sep 2007 A1
20070241874 Okpysh Oct 2007 A1
20070244614 Nathanson Oct 2007 A1
20070257781 Denson Nov 2007 A1
20070257782 Etcheson Nov 2007 A1
20070257804 Gunderson Nov 2007 A1
20070257815 Gunderson Nov 2007 A1
20070260677 DeMarco Nov 2007 A1
20070262855 Zuta Nov 2007 A1
20070263984 Sterner Nov 2007 A1
20070268158 Gunderson Nov 2007 A1
20070271105 Gunderson Nov 2007 A1
20070273480 Burkman Nov 2007 A1
20070279214 Buehler Dec 2007 A1
20070299612 Kimura Dec 2007 A1
20080035108 Ancimer Feb 2008 A1
20080059019 Delia Mar 2008 A1
20080071827 Hengel Mar 2008 A1
20080111666 Plante May 2008 A1
20080122603 Plante May 2008 A1
20080137912 Kim Jun 2008 A1
20080143834 Comeau Jun 2008 A1
20080147267 Plante et al. Jun 2008 A1
20080157510 Breed Jul 2008 A1
20080167775 Kuttenberger Jul 2008 A1
20080169914 Albertson Jul 2008 A1
20080177436 Fortson Jul 2008 A1
20080195261 Breed Aug 2008 A1
20080204556 de Miranda Aug 2008 A1
20080234920 Nurminen Sep 2008 A1
20080252485 Lagassey Oct 2008 A1
20080269978 Shirole Oct 2008 A1
20080281485 Plante Nov 2008 A1
20080309762 Howard et al. Dec 2008 A1
20080319604 Follmer Dec 2008 A1
20090009321 McClellan Jan 2009 A1
20090043500 Satoh Feb 2009 A1
20090043971 Kim Feb 2009 A1
20090051510 Follmer Feb 2009 A1
20090138191 Engelhard May 2009 A1
20090157255 Plante Jun 2009 A1
20090216775 Ratliff et al. Aug 2009 A1
20090224869 Baker Sep 2009 A1
20090290848 Brown Nov 2009 A1
20090299622 Denaro Dec 2009 A1
20090312998 Berckmans Dec 2009 A1
20090326796 Prokhorov Dec 2009 A1
20090327856 Mouilleseaux Dec 2009 A1
20100030423 Nathanson Feb 2010 A1
20100045451 Periwal Feb 2010 A1
20100047756 Schneider Feb 2010 A1
20100054709 Misawa Mar 2010 A1
20100057342 Muramatsu Mar 2010 A1
20100063672 Anderson Mar 2010 A1
20100063850 Daniel Mar 2010 A1
20100070175 Soulchin Mar 2010 A1
20100085193 Boss Apr 2010 A1
20100085430 Kreiner Apr 2010 A1
20100087984 Joseph Apr 2010 A1
20100100315 Davidson Apr 2010 A1
20100103165 Lee Apr 2010 A1
20100149418 Freed Jun 2010 A1
20100153146 Angell Jun 2010 A1
20100157061 Katsman Jun 2010 A1
20100191411 Cook Jul 2010 A1
20100201875 Rood Aug 2010 A1
20100220892 Kawakubo Sep 2010 A1
20100250021 Cook Sep 2010 A1
20100250022 Hines Sep 2010 A1
20100250060 Maeda Sep 2010 A1
20100268415 Ishikawa Oct 2010 A1
20100312464 Fitzgerald Dec 2010 A1
20110035139 Konlditslotis Feb 2011 A1
20110043624 Haug Feb 2011 A1
20110060496 Nielsen Mar 2011 A1
20110077028 Wilkes Mar 2011 A1
20110091079 Yu-Song Apr 2011 A1
20110093159 Boling Apr 2011 A1
20110112995 Chang May 2011 A1
20110121960 Tsai May 2011 A1
20110125365 Larschan May 2011 A1
20110130916 Mayer Jun 2011 A1
20110145042 Green Jun 2011 A1
20110153367 Amigo Jun 2011 A1
20110161116 Peak Jun 2011 A1
20110166773 Raz Jul 2011 A1
20110172864 Syed Jul 2011 A1
20110173015 Chapman Jul 2011 A1
20110208428 Matsubara Aug 2011 A1
20110213628 Peak Sep 2011 A1
20110224891 Iwuchukwu Sep 2011 A1
20110251782 Perkins Oct 2011 A1
20110273568 Lagassey Nov 2011 A1
20110282542 Nielsen Nov 2011 A9
20110283223 Vattinen et al. Nov 2011 A1
20110304446 Basson Dec 2011 A1
20120021386 Anderson Jan 2012 A1
20120035788 Trepagnier Feb 2012 A1
20120041675 Juliver Feb 2012 A1
20120046803 Inou Feb 2012 A1
20120071140 Oesterling Mar 2012 A1
20120078063 Moore-Ede Mar 2012 A1
20120100509 Gunderson Apr 2012 A1
20120109447 Yousefi May 2012 A1
20120150436 Rossano Jun 2012 A1
20120176234 Taneyhill Jul 2012 A1
20120190001 Knight Jul 2012 A1
20120198317 Eppolito Aug 2012 A1
20120210252 Fedoseyeva Aug 2012 A1
20120277950 Plante Nov 2012 A1
20120280835 Raz Nov 2012 A1
20120330528 Schwindt Dec 2012 A1
20130004138 Kilar Jan 2013 A1
20130006469 Green Jan 2013 A1
20130021148 Cook Jan 2013 A1
20130028320 Gardner Jan 2013 A1
20130030660 Fujimoto Jan 2013 A1
20130073112 Phelan Mar 2013 A1
20130073114 Nemat-Nasser Mar 2013 A1
20130127980 Haddick May 2013 A1
20130145269 Latulipe Jun 2013 A1
20130151980 Lee Jun 2013 A1
20130170762 Marti Jul 2013 A1
20130197774 Denson Aug 2013 A1
20130209968 Miller Aug 2013 A1
20130274950 Richardson Oct 2013 A1
20130278631 Border Oct 2013 A1
20130317711 Plante Nov 2013 A1
20130332004 Gompert Dec 2013 A1
20130345927 Cook Dec 2013 A1
20130345929 Bowden Dec 2013 A1
20140025254 Plante Jan 2014 A1
20140032062 Baer Jan 2014 A1
20140046550 Palmer Feb 2014 A1
20140047371 Palmer Feb 2014 A1
20140058583 Kesavan Feb 2014 A1
20140089504 Scholz Mar 2014 A1
20140094992 Lambert Apr 2014 A1
20140098228 Plante Apr 2014 A1
20140152828 Plante Jun 2014 A1
20140226010 Molin Aug 2014 A1
20140232863 Paliga Aug 2014 A1
20140279707 Joshua Sep 2014 A1
20140280204 Avery Sep 2014 A1
20140300739 Mimar Oct 2014 A1
20140309849 Ricci Oct 2014 A1
20140336916 Yun Nov 2014 A1
20150035665 Plante Feb 2015 A1
20150057836 Plante Feb 2015 A1
20150105934 Palmer Apr 2015 A1
20150112542 Fuglewicz Apr 2015 A1
20150112545 Binion Apr 2015 A1
20150134226 Palmer May 2015 A1
20150135240 Shibuya May 2015 A1
20150156174 Fahey Jun 2015 A1
20150189042 Sun Jul 2015 A1
20150222449 Salinger Aug 2015 A1
20160054733 Hollida Feb 2016 A1
Foreign Referenced Citations (62)
Number Date Country
2469728 Dec 2005 CA
2692415 Aug 2011 CA
2692415 Aug 2011 CA
4416991 Nov 1995 DE
20311262 Sep 2003 DE
202005008238 Sep 2005 DE
102004004669 Dec 2005 DE
0708427 Apr 1996 EP
0840270 May 1998 EP
0848270 May 1998 EP
1170697 Jan 2002 EP
1324274 Jul 2003 EP
1355278 Oct 2003 EP
1427165 Jun 2004 EP
1818873 Aug 2007 EP
2320387 May 2011 EP
2407943 Jan 2012 EP
2268608 Jan 1994 GB
2402530 Dec 2004 GB
2451485 Feb 2009 GB
2447184 Jun 2011 GB
2446994 Aug 2011 GB
58085110 May 1983 JP
S5885110 May 1983 JP
62091092 Apr 1987 JP
S6291092 Apr 1987 JP
S62166135 Jul 1987 JP
02056197 Feb 1990 JP
H0256197 Feb 1990 JP
H04257189 Sep 1992 JP
H05137144 Jun 1993 JP
5294188 Nov 1993 JP
H08124069 May 1996 JP
H09163357 Jun 1997 JP
H09272399 Oct 1997 JP
10076880 Mar 1998 JP
H1076880 Mar 1998 JP
2002191017 Jul 2002 JP
1000588169 Dec 2000 KR
8809023 Nov 1988 WO
9005076 May 1990 WO
9427844 Dec 1994 WO
9600957 Jan 1996 WO
9701246 Jan 1997 WO
9726750 Jul 1997 WO
9937503 Jul 1999 WO
9940545 Aug 1999 WO
9962741 Dec 1999 WO
0007150 Feb 2000 WO
0028410 May 2000 WO
0048033 Aug 2000 WO
0077620 Dec 2000 WO
0123214 Apr 2001 WO
0125054 Apr 2001 WO
0146710 Jun 2001 WO
03045514 Jun 2003 WO
2006022824 Mar 2006 WO
2007067767 Jun 2007 WO
2009081234 Jul 2009 WO
2011055743 May 2011 WO
2013072939 May 2013 WO
2013159853 Oct 2013 WO
Non-Patent Literature Citations (196)
Entry
Adaptec published and sold its VideoOh! DVD software USB 2.0 Edition in at least Jan. 24, 2003.
Ambulance Companies Use Video Technology to Improve Driving Behavior, Ambulance Industry Journal, Spring 2003.
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.
Amendment filed Dec. 23, 2009 during prosecution of U.S. Appl. No. 11/566,424.
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.
U.S. Appl. No. 11/296,906, filed Dec. 8, 2005, File History.
U.S. Appl. No. 11/297,669, filed Dec. 8, 2005, File History.
U.S. Appl. No. 11/297,889, filed Dec. 8, 2005, File History.
U.S. Appl. No. 11/298,069, filed Dec. 9, 2005, File History.
U.S. Appl. No. 11/299,028, filed Dec. 9, 2005, File History.
U.S. Appl. No. 11/593,659, filed Nov. 7, 2006, File History.
U.S. Appl. No. 11/593,682, filed Nov. 7, 2006, File History.
U.S. Appl. No. 11/593,882, filed Nov. 7, 2006, File History.
U.S. Appl. No. 11/595,015, filed Nov. 9, 2006, File History.
U.S. Appl. No. 11/637,754, filed Dec. 13, 2006, File History.
U.S. Appl. No. 11/637,755, filed Dec. 13, 2006, File History.
Bill, ‘DriveCam—FAQ’, Dec. 12, 2003.
Bill Siuru, ‘DriveCam Could Save You Big Bucks’, Land Line Magazine, May-Jun. 2000.
Chris Woodyard, ‘Shuttles save with DriveCam’, Dec. 9, 2003.
Dan Carr, Flash Video Template: Video Presentation with Navigation, Jan. 16, 2006, http://www.adobe.com/devnet/fiash/articles/vidtemplate—mediapreso—flash8.html.
David Cullen, ‘Getting a real eyeful’, Fleet Owner Magazine, Feb. 2002.
David Maher, ‘DriveCam Brochure Folder’, Jun. 6, 2005.
David Maher, “DriveCam Brochure Folder”, Jun. 8, 2005.
David Vogeleer et al., Macromedia Flash Professional 8UNLEASHED (Sams Oct. 12, 2005).
Del Lisk, ‘DriveCam Training Handout Ver4’, Feb. 3, 2005.
Drivecam, Inc., User's Manual for Drivecam Video Systems' Hindsight 20/20 Software Version 4.0 (2003).
DriveCam, Inc.'s Infringement Contentions Exhibit A, U.S. Pat. No. 6,389,340, Document 34.1, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Pat. No. 7,659,827. Aug. 19, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Pat. No. 7,804,426, Document 34.2, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Pat. No. 7,659,827, Document 34.3, Oct. 20, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Pat. No. 7,804,426. Aug. 19, 2011.
DriveCam, Inc.'s Infringement Contentions Exhibit D, Document 34.4, Oct. 20, 2011.
DriveCam—Illuminator Data Sheet, Oct. 2, 2004.
Drivecam.com as retrieved by the Internet Wayback Machine as of Mar. 5, 2005.
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.
DriveCam Driving Feedback System, Mar. 15, 2004.
DriveCam Extrinsic Evidence with Patent LR 4.1 .a Disclosures, Nov. 3, 2011.
DriveCam Extrinsic Evidence with Patent LR 4.1 .a Disclosures, Nov. 8, 2011.
Driver Feedback System, Jun. 12, 2001.
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.
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. 1, 2012, pp. 86-103.
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.
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, Exhibit A, Document 55, filed Jan. 3, 2012, pp. 49-103.
Franke, U., et al., Autonomous Driving Goes Downtown, IEEE Intelligent Systems, 13(6):40-48 (1988); Digital Object Identifier 10.1109/5254.736001.
Gallagher, B., et al., Wireless Communications for Vehicle Safety: Radio Link Performance and Wireless Connectivity Methods, Vehicular Technology Magazine, IEEE, 1(4):4- 24 (2006); Digital Object Identifier 10.1109/MVT.2006.343641.
Gandhi, T., et al., Pedestrian Protection Systems: Issues, Survey, and Challenges, IEEE Transactions on Intelligent Transportation Systems, 8(3):413- 430 (2007); Digital Object Identifier 10.1109/TITS.2007.903444.
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.
GE published its VCR User's Guide for Model VG4255 in 1995.
Glenn Oster, ‘Hindsight 20/20 v4.0 Software Installation’, 1 of 2, Jun. 20, 2003.
Glenn Oster, ‘HindSight 20/20 v4.0 Software Installation’, 2 of 2, Jun. 20, 2003.
Glenn Oster, ‘Illuminator Installation’, Oct. 3, 2004.
Hans Fantel, Video; Search Methods Make a Difference in Picking VCR's, NY Times, Aug. 13, 1989.
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&Categorys- ub.--Code=coaching)., printed from site on Jan. 11, 2012.
Inovate Motorsports, OT-1 16 Channel OBD-II Interface User Manual, Version 1.0, Nov. 28, 2007, pp. 3, 4, 21 & 27.
Interior Camera Data Sheet, Oct. 26, 2001.
International Search Report and Written Opinion issued in PCT/US07/68325 on Feb. 27, 2008.
International Search Report and Written Opinion issued in PCT/US07/68328 on Oct. 15, 2007.
International Search Report and Written Opinion issued in PCT/US07/68329 on Mar. 3, 2008.
International Search Report and Written Opinion issued in PCT/US07/68332 on Mar. 3, 2008.
International Search Report and Written Opinion issued in PCT/US07/68334 on Mar. 5, 2008.
International Search Report for PCT/US2006/47055, Mailed Mar. 20, 2008 (2 pages).
International Search Report issued in PCT/US2006/47042 mailed Feb. 25, 2008.
J. Gallagher, ‘Lancer Recommends Tech Tool’, Insurance and Technology Magazine, Feb. 2002.
Jean (DriveCam vendor), ‘DC Data Sheet’, Nov. 6, 2002.
Jean (DriveCam vendor), ‘DriveCam brochure’, Nov. 6, 2002.
Jean (DriveCam vendor), ‘Feedback Data Sheet’, Nov. 6, 2002.
Jean (DriveCam vendor), ‘Hindsight 20-20 Data Sheet’, Nov. 4, 2002.
Jessyca Wallace, ‘Analyzing and Processing DriveCam Recorded Events’, Oct. 6, 2003.
Jessyca Wallace, ‘Overview of the DriveCam Program’, Dec. 15, 2005.
Jessyca Wallace, ‘The DriveCam Driver Feedback System’, Apr. 6, 2004.
Joint Claim Construction Chart, U.S. Pat. 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.
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.
Joint Claim Construction Worksheet, U.S. Pat. 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.
Joint Claim Construction Worksheet, U.S. Pat. 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.
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.
Joint Motion for Leave to Supplement Disclosure of Asserted Claims and Preliminary Infringement Contentions in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-cv-00997-H-Rbb, Document 29, filed Oct. 12, 2011, pp. 1-7.
Julie Stevens, ‘DriveCam Services’, Nov. 15, 2004.
Julie Stevens, ‘Program Support Roll-Out & Monitoring’, Jul. 13, 2004.
Jung, Sang-Hack, et al., Egomotion Estimation in Monocular Infra-red Image Sequence for Night Vision Applications, IEEE Workshop on Applications of Computer Vision (WACV '07), Feb. 2007, pp. 8-8; Digital Object Identifier 10.1109/WACV.2007.20.
JVC Company of America, JVC Video Cassette Recorder HR-IP820U Instructions (1996).
Kamijo, S., et al., A Real-Time Traffic Monitoring System by Stochastic Model Combination, IEEE International Conference on Systems, Man and Cybernetics, 4:3275-3281 (2003).
Kamijo, S., et al., An Incident Detection System Based on Semantic Hierarchy, Proceedings of the 7th International IEEE Intelligent Transportation Systems Conference, Oct. 3-6, 2004, page(s):853-858; Digital Object Identifier 10.1109/ITSC.2004.1399015.
Karen, ‘Downloading Options to HindSight 20120’, Aug. 6, 2002.
Karen, ‘Managers Guide to the DriveCam Driving Feedback System’, Jul. 30, 2002.
Kathy Latus (Latus Design), ‘Case Study—Cloud 9 Shuttle’, Sep. 23, 2005.
Kathy Latus (Latus Design), ‘Case Study—Lloyd Pest Control’, Jul. 19, 2005.
Kathy Latus (Latus Design), ‘Case Study—Time Warner Cable’, Sep. 23, 2005.
Ki, Yong-Kul, et al., A Traffic Accident Detection Model using Metadata Registry, Proceedings of the Fourth International Conference on Software Engineering Research, Management and Applications; Aug. 9-11, 2006 p. 255-259 Digital Object Identifier 10.1109/SERA.2006.8.
Kitchin, Charles. “Understanding accelerometer scale factor and offset adjustments.” Analog Devices (1995).
Lin, Chin-Teng et al., EEG-based drowsiness estimation for safety driving using independent component analysis; IEEE Transactions on Circuits and Systems-I: Regular Papers, 52(12):2726-2738 (2005); Digital Object Identifier 10.1109/TCSI.2005.857555.
Lisa McKenna, ‘A Fly on the Windshield?’, Pest Control Technology Magazine, Apr. 2003.
Miller, D.P., Evaluation of Vision Systems for Teleoperated Land Vehicles. Control Systems Magazine, IEEE, 8(3):37-41 (1988); Digital Identifier 10.1109/37.475.
Munder, S., et al., Pedestrian Detection and Tracking Using a Mixture of View-Based Shape-Texture Models, IEEE Transactions on Intelligent Transportation Systems, 9(2):333-343 (2008); Digital Identifier 10.1109/TITS.2008.922943.
Panasonic Corporation, Video Cassette Recorder (VCR) Operating Instructions for Models No. PV-V4020/PV-V4520.
Passenger Transportation Mode Brochure, May 2, 2005.
Patent Abstracts of Japan vol. 007, No. 180 (P-215), Aug. 9, 1983 (Aug. 9, 1983) & JP 58 085110 A (Mitsuhisa Ichikawa), May 21, 1983 (May 21, 1983).
Patent Abstracts of Japan vol. 011, No. 292 (E-543), Sep. 19, 1987 (Sep. 19, 1987) & JP 62 091092 A (OK Eng:KK), Apr. 25, 1987 (Apr. 25, 1987).
Patent Abstracts of Japan vol. 012, No. 001 (M-656), Jan. 6, 1988 (Jan. 6, 1988) & JP 62 166135 A (Fuji Electric Co Ltd), Jul. 22, 1987 (Jul. 22, 1987).
Patent Abstracts of Japan vol. 014, No. 222 (E-0926), May 10, 1990 (May 10, 1990) & JP 02 056197 A (Sanyo Electric Co Ltd), Feb. 26, 1990 (Feb. 26, 1990).
Patent Abstracts of Japan vol. 017, No. 039 (E-1311), Jan. 25, 1993 (Jan. 25, 1993) & JP 04 257189 A (Sony Corp), Sep. 11, 1992 (Sep. 11, 1992).
Patent Abstracts of Japan vol. 017, No. 521 (E-1435), Sep. 20, 1993 (Sep. 20, 1993) & JP 05 137144 A (Kyocera Corp), Jun. 1, 1993 (Jun. 1, 1993).
Patent Abstracts of Japan vol. 1996, No. 09, Sep. 30, 1996 (Sep. 30, 1996) & JP 08 124069 A (Toyota Motor Corp), May 17, 1996 (May 17, 1996).
Patent Abstracts of Japan vol. 1997, No. 10, Oct. 31, 1997 (Oct. 31, 1997) & JP 09 163357 A (Nippon Soken Inc), Jun. 20, 1997 (Jun. 20, 1997).
Patent Abstracts of Japan vol. 1998, No. 02, Jan. 30, 1998 (Jan. 30, 1998) & JP 09 272399 A (Nippon Soken Inc), Oct. 21, 1997 (Oct. 21, 1997).
Patent Abstracts of Japan vol. 1998, No. 8, Jun. 30, 1998 (Jun. 30, 1998) & JP 10 076880 A (Muakami Corp), Mar. 24, 1998 (Mar. 24, 1998).
PCT/US2010/022012, Invitation to Pay Additional Fees with Communication of Partial International Search, Jul. 21, 2010.
Peter G. Thurlow, Letter (including exhibits) Regarding Patent Owner's Response to Initial Office Action in Ex Parte Reexamination, Mar. 27, 2012.
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.
Quinn Maughan, ‘DriveCam Enterprise Services’, Jan. 5, 2006.
Quinn Maughan, ‘DriveCam Managed Services’, Jan. 5, 2006.
Quinn Maughan, ‘DriveCam Standard Edition’, Jan. 5, 2006.
Quinn Maughan, ‘DriveCam Unit Installation’, Jul. 21, 2005.
Quinn Maughan, ‘Enterprise Services’, Apr. 17, 2006.
Quinn Maughan, ‘Enterprise Services’, Apr. 7, 2006.
Quinn Maughan, ‘Hindsight Installation Guide’, Sep. 29, 2005.
Quinn Maughan, ‘Hindsight Users Guide’, Jun. 7, 2005.
Ronnie Rittenberry, ‘Eyes on the Road’, Jul. 2004.
SmartDrives Systems, Inc's Production, SO14246-S014255, Nov. 16, 2011.
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.
The DriveCam, Nov. 6, 2002.
The DriveCam, Nov. 8, 2002.
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.
Trivinci Systems, LLC, Race-Keeper Systems User Guide, Jan. 2011, v1, 1.02, pp. 34 and 39.
U.S. Appl. No. 12/691,639, entitled ‘Driver Risk Assessment System and Method Employing Selectively Automatic Event Scoring’, filed Jan. 21, 2010.
U.S. Appl. No. 11/377,167, Final Office Action dated Nov. 8, 2013.
U.S. Appl. No. 11/377,157, filed Mar. 16, 2006 entitled, “Vehicle Event Recorder Systems and Networks Having Parallel Communications Links”.
U.S. Appl. No. 11/377,167, filed Mar. 16, 2006 entitled, “Vehicle Event Recorder Systems and Networks Having Integrated Cellular Wireless Communications Systems”.
USPTO Final Office Action for U.S. Appl. No. 11/297,669, mailed Nov. 7, 2011, 15 pages.
USPTO Final Office Action for U.S. Appl. No. 13/957,810, mailed Jun. 27, 2014, 24 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/296,906, mailed Apr. 2, 2009, 7 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/296,906, mailed Nov. 6, 2009, 9 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/297,669, mailed Apr. 28, 2011, 11 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/299,028, mailed Apr. 24, 2008, 9 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Nov. 19, 2007, 7 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Nov. 25, 2011, 9 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Sep. 11, 2008, 8 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,167, mailed Jun. 5, 2008, 11 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/800,876, mailed Dec. 1, 2010, 12 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/800,876, mailed Dec. 20, 2011, 8 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 12/096,591, mailed May 20, 2014, 19 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 14/036,299, mailed Aug. 12, 2014.
USPTO Non-Final Office Action for U.S. Appl. No. 11/296,907, Mailed Mar. 22, 2007 ( 17 pages).
USPTO Non-final Office Action mailed Aug. 27, 2009 during prosecution of U.S. Appl. No. 11/566,424.
USPTO Non-Final Office Action mailed Nov. 27, 2013 in U.S. Appl. No. 13/957,810, filed Aug. 2, 2013.
Veeraraghavan, H., et al., Computer Vision Algorithms for Intersection Monitoring, IEEE Transactions on Intelligent Transportation Systems, 4(2):78- 89 (2003); Digital Object Identifier 10.1109/TITS.2003.821212.
Wijesoma, W.S., et al., Road Curb Tracking in an Urban Environment, Proceedings of the Sixth International Conference of Information Fusion, 1:261-268 (2003).
World News Tonight, CBC 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.
Written Opinion issued in PCT/US07/68328 on Oct. 15, 2007.
Written Opinion of the International Searching Authority for PCT/US2006/47042. Mailed Feb. 25. 2008 (5 pages).
Written Opinion of the International Searching Authority for PCT/US2006/47055, Mailed Mar. 20, 2008 (5 pages).
DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Pat. No. 7,659,827. Aug. 19, 2011. (29 pgs.).
DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Pat. No. 7,804,426. Aug. 19, 2011. (47 pgs.).
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. (6 pgs.).
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. (13 pgs.).
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. (7 pgs.).
Notice of Allowance for U.S. Appl. No. 13/957,810, mailed Jun. 8, 2015, 10 pages.
Trivinci Systems, LLC, “Race-Keeper System User Guide”, V1 .1.02, Jan. 2011, p. 21.
“DriveCam, Inc's Disclosure of Proposed Constructions and Extrinsic Evidence Pursuant to Patent L.R. 4.1.a & 4.1.b” Disclosure and Extrinsic Evidence in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Nov. 8, 2011.
“DriveCam Driving Feedback System”, DriveCam brochure, Jun. 12, 2001, Document #6600128.
“DriveCam Driving Feedback System” DriveCam brochure, Mar. 15, 2004.
“DriveCam Passenger Transportation Module”, DriveCam brochure, Oct. 26, 2001.
“DriveCam Video Event Data Recorder”, DriveCam brochure, Nov. 6, 2002, Document #6600127.
“Responsive Claim Construction and Identification of Extrinsic Evidence of Defendani/Counterclaimant SmartDrive Systems, Inc.” Claim Construction and and Extrinsic Evidence in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 15, 2011.
“Sonic MyDVD 4.0: Tutorial: Trimming video segments”. Tutorial for software bundled with Adaptec VideoOh! DVD USB 2.0 Edition, 2003.
“User's Manual for DriveCam Video Systems' HindSight 20/20 Software Version 4.0” DriveCam Manual, San Diego, 2003, Document #6600141-1.
Canadian Office Action issued in Application No. 2,632,685 dated Jan. 30, 2015; 5 pages.
Dan Maher, “DriveCam Taking Risk Out of Driving”, DriveCam brochure folder, Jun. 6, 2005.
Del Lisk, “DriveCam Training Seminar” Handout, 2004.
European Examination Report issued in EP 07772812.9 on Jan. 22, 2015; 5 pages.
Jean (DriveCam vendor) “DriveCam Driving Feedback System”, DriveCam brochure, Nov. 6, 2002, Document #6600128-1.
Notice of Allowance Allowance for U.S. Appl. No. 14/036,299, mailed Mar. 20, 2015, xx pages.
Notice of Allowance Application for U.S. Appl. No. 11/566,424, mailed Feb. 26, 2010, 6 pages.
Notice of Allowance for U.S. Appl. No. 11/377,164, mailed Dec. 3, 2014, 5 pages.
Notice of Allowance for U.S. Appl. No. 11/377,164, mailed Feb. 13, 2015, 2 pages.
Notice of Allowance for U.S. Appl. No. 11/377,164, mailed Feb. 25, 2014, 2 pages.
Notice of Allowance for U.S. Appl. No. 11/377,164, mailed Nov. 18, 2013, 7 pages.
Notice of Allowance for U.S. Appl. No. 11/377,167, mailed Apr. 1, 2015, 7 pages.
Notice of Allowance for U.S. Appl. No. 11/800,876, mailed Apr. 19, 2012, 8 pages.
USPTO Final Office Action for U.S. Appl. No. 11/296,906, mailed Aug. 8, 2012, 15 pages.
USPTO Final Office Action for U.S. Appl. No. 12/096,591, mailed Dec. 5, 2014, 23 pages.
USPTO Final Office Action for U.S. Appl. No. 12/096,591, mailed Jul. 18, 2012, 15 pages.
USPTO Final Office Action for U.S. Appl. No. 12/096,591, mailed Nov. 7, 2013, 14 pages.
USPTO Final Office Action for U.S. Appl. No. 13/957,810, mailed Jun. 27, 2014, 22 pages.
USPTO Final Office Action for U.S. Appl. No. 14/036,299, mailed Feb. 24, 2015, 9 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/296,906, mailed Apr. 8, 2014, 19 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/296,906, mailed Jun. 12, 2012, 13 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Apr. 7, 2014, 7 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Aug. 18, 2014, 5 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Sep. 10, 2012, 10 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 11/377,167, mailed Jun. 27, 2013, 11 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 12/096,591, mailed Jun. 14, 2011, 8 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 12/096,591, mailed Mar. 27, 2013, 16 pages.
USPTO Non-Final Office Action for U.S. Appl. No. 13/957,810, mailed Apr. 17, 2015, 6 pages.
USPTO Non-final Office Action for U.S. Appl. No. 13/957,810, mailed Nov. 27, 2013, 18 pages.
PCT International Search Report and Written Opinion for PCT/1B16/51863, dated Sep. 16, 2016.
PCT International Search Report and Written Opinion for PCT/US15/60721 dated Feb. 26, 2016, 11 pages.
Related Publications (1)
Number Date Country
20150057836 A1 Feb 2015 US
Continuations (1)
Number Date Country
Parent 11593659 Nov 2006 US
Child 14529134 US