US 8,989,959 B2Grant
Vehicle operator performance history recording, scoring and reporting systems
Issue Date:2015-03-24
•33 Claims
•6 Drawing Sheets
Abstract
Vehicle operator performance history recording and reporting systems include devices and methods of automatically collecting and processing vehicle crash or event data over time to form a driver history report. A driver history report may include many factors to express performance or quality of driver service, and these may be reduced to a single value normalized expression in view of a collection of many drivers. Vehicle event recorders are arranged to capture data relating to a particular event. These vehicle event recorders are further 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/her. 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 other mathematical analysis may be applied independently to various data elements or data “fields” to produce performance metrics and ratios which reflect performance. Together, these factors may each be weighted and summed in accordance with specially devised a formulae including those having a single value solution.
Metadata
Assignee
- SmartDrive Systems, Inc.
Inventors
- James Plante
- Ramesh Kasavaraju
- Gregory Mauro
- Andrew Nickerson
Application Information
Application Number:US 11/593,659
Filing Date:2006-11-07
Priority Date:2006-11-07
Art Unit:3664
Classifications
IPC:
G01M17/00G06F7/00G06F19/00G07C5/08
Patent Drawings (6 sheets)
Description
Background of the Inventions
[0001] 1. Field
[0002] 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.
[0003] 2. Prior Art
[0004] 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.
[0005] 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.
[0006] 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.
[0007] 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.
[0008] 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.
[0009] 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.
[0010] 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.
[0011] 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.
[0012] 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.
[0013] 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.
[0014] 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.
[0015] 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.
[0016] 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.
[0017] 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.
[0018] 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.
[0019] 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.
[0020] 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.
[0021] 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.
[0022] 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 patent having 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.
[0023] 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.
[0024] 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.
[0025] 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.
[0026] 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.
[0027] 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.
[0028] 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.
[0029] 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 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.
[0030] 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.
[0031] 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.
[0032] Also, inventor Boykin of Mt. Juliet Tennessee 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.
[0033] 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.
[0034] 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
[0035] 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.
[0036] 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.
[0037] 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 the Inventions
[0038] It is a primary object of these inventions to provide advanced recording and reporting systems for motor vehicle exception events.
[0039] It is an object of these inventions to provide automated vehicle operator performance measure, recording and reporting systems.
[0040] It is a further object to provide automated vehicle operator performance tracking and history systems.
[0041] 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
[0042] 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:
[0043] FIG. 1 is top-level block diagram to illustrate system primary elements;
[0044] FIG. 2 is a brief example collection of datasets to illustrate associations with a particular operator;
[0045] FIG. 3 is detailed block diagram further setting forth important elements of apparatus of these systems;
[0046] FIG. 4 illustrates in block diagram fundamental methods of these systems; and
[0047] FIG. 5 illustrates in further detail some preferred methods.
Glossary of Special Terms
[0048] 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
[0049] 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
[0050] 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
[0051] 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
[0052] 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
[0053] An event record dataset is a combination of an event record, a vehicle operator identifier and an association between the two.
Report
[0054] 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
[0055] A single value score is a vehicle operator performance parameter or metric expressed numerically as a single value.
Preferred Embodiments of these Inventions
[0056] 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.
[0057] 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.
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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.
[0071] 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.
[0072] 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.
[0073] 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’.
[0074] 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.
[0075] 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.
[0076] 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.
[0077] 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.
[0078] 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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).
[0083] 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.
[0084] 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.
[0085] 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.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] 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.
[0090] 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.
[0091] 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.
[0092] 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.
[0093] 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.
[0094] 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.
[0095] 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.
[0096] 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.
[0097] 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.
[0098] 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.
[0099] 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.
[0100] 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.
[0101] 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.
[0102] 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.
[0103] 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
It is claimed:
1. A system configured to determine a vehicle operator performance measure, the system comprising:
an operator identity system located remotely from the vehicle configured to receive entry and/or selection of operator identity information by operators of the vehicle that identifies periods of time individual operators operate the vehicle, the operator identity information including first operator identity information that identifies a first period of time a first operator operates the vehicle;
an associator configured to:
receive the first operator identity information;
receive event records that include information related to vehicle operation and/or performance during corresponding vehicle events that occur during operation of the vehicle, the event records including a first event record that corresponds to a first vehicle event and a second event record that corresponds to a second vehicle event;
associate the event records and the operator identity information such that, by virtue of the first vehicle event and the second vehicle event occurring during the first period of time the first operator operates the vehicle, the first event record is associated with the first operator identity information for the first operator via a first association, and the second event record is associated with the first operator identity information for the first operator via a second association;
form datasets comprising the operator identity information and the associated event records such that a first dataset includes the first operator identity information and the first associated event record, and a second dataset includes the first operator identity information and the second associated event record; and
transmit the datasets to a data store that is located remotely from the vehicle; and
an analyzer configured to retrieve the datasets from the data store and analyze the datasets, including the first dataset and the second dataset, to determine a vehicle operator performance measure for the first operator.
2. The system of claim 1, further comprising a set of electronic transducers, individual ones of the transducers being coupled to vehicle environments or vehicle systems and configured to generate output signals conveying information relating to vehicle operation and/or performance.
3. The system of claim 2, wherein the associator is configured such that the event records include the information conveyed by the output signals.
4. The system of claim 2, wherein the transducers include one or more of an imager; a video recorder; an accelerometer; a speedometer; a position sensor; an orientation sensor; a time sensor; or a vehicle systems status indicator, the vehicle systems status indicator including one or more of an engine speed indicator, a temperature indicator; a braking indicator; a gear ratio indicator; or a steering position indicator.
5. The system of claim 3, further comprising a vehicle event recorder, the vehicle event recorder being comprised of an imager, memory, and an event trigger, the vehicle event recorder arranged to produce event records in response to a toggle of said event trigger.
6. The system of claim 5, wherein the associator is configured such that toggling the event trigger causes the information conveyed by the output signals to be captured as a portion of an event record and to be associated with the first operator identity information.
7. The system of claim 1, wherein the associator is configured to form datasets comprising the first operator identity information and associated event records for one or more operation sessions by the first operator.
8. The system of claim 1, wherein the operator identity system includes a memory with stored values associated with at least the first operator of the vehicle.
9. The system of claim 8, wherein the operator identity system is integrated with a vehicle event recorder.
10. The system of claim 8, wherein the operator identity system includes an integrated download server.
11. A method for determining a vehicle operator performance measure with a determination system, the determination system comprising an associator, an operator identity system, and an analyzer, the method comprising:
receiving, with one or more processors of the associator, an event record, the event record including information related to vehicle operation and/or performance during a corresponding vehicle event that occurs during operation of the vehicle;
receiving, with one or more processors of the operator identity system, operator identity information, wherein receiving operator identity information includes receiving entry and/or selection of operator identity information by operators of the vehicle via an interface located remotely from the vehicle that identifies periods of time individual operators operate the vehicle, the operator identity information including first operator identity information that identifies a first period of time that a first operator operates the vehicle;
associating, with the one or more processors of the associator, the received event record and the received operator identity information such that, by virtue of the vehicle event occurring during the first period of time, the event record is associated with the first operator identity information for the first operator;
forming, with the one or more processors of the associator, a dataset record comprising the event record and the associated first operator identity information;
storing, with the one or more processors of the associator, said dataset record in a database with other dataset records;
recalling, with one or more processors of the analyzer, a plurality of dataset records from said database;
applying, with the one or more processors of the analyzer, a mathematical analysis upon elements of the dataset records; and
providing, with the one or more processors of the analyzer, an output report based upon results of the applied mathematical analysis.
12. The method of claim 11, wherein said ‘receiving an event record’ step is further characterized as receiving, with the one or more processors of the associator, from a vehicle event recorder information captured in response to a triggered event.
13. The method of claim 12, wherein said information captured in response to a triggered event includes a video record of environments about a subject vehicle.
14. The method of claim of claim 11, wherein said ‘receiving identity information’ step is further characterized as receiving, with the one or more processors of the associator, a unique identifier assigned to one or more of an individual operator, an individual vehicle, or a vehicle fleet.
15. The method of claim 11, wherein said ‘forming an association’ step is further characterized as connecting, joining, or associating received operator and/or vehicle information with a particular event record.
16. The method of claim 11, wherein said 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/or identity information.
17. The method of claim 11, wherein said ‘recalling a plurality of dataset records’ step is further characterized as recalling, with the one or more processors of the analyzer, only those records associated with the first operator.
18. The method of claim 11, wherein said ‘recalling a plurality of dataset records’ step is further characterized as recalling, with the one or more processors of the analyzer, only those records associated with a particular vehicle.
19. The method of claim 11, wherein said ‘recalling a plurality of dataset records’ step is further characterized as recalling, with the one or more processors of the analyzer, only those records associated with a particular fleet of vehicles.
20. The method of claim 16, wherein said ‘applying mathematical analysis’ step is further characterized as executing, with the one or more processors of the analyzer, an algorithm on a plurality of dataset records, each dataset record comprising therein information from an event record captured at a time different than the capture time of all other dataset records, the algorithm being applied to a common field of each recalled dataset record.
21. The method of claim 20, wherein said ‘applying mathematical analysis’ step is further characterized as executing, with the one or more processors of the analyzer, an algorithm to realize a ratio between the resultant of two algorithms applied to two different field elements.
22. The method of claim 21, wherein said ratio comprises a time based unit in the denominator.
23. The method of claim 21, wherein said ratio comprises a distance based unit in the denominator.
24. The method of claim 11, wherein said ‘providing an output report’ step is further characterized as a report having a plurality of resultants produced by application of the mathematical analysis.
25. The method of claim 24, wherein said output report comprises a single value operator performance coefficient produced by application of a prescribed algorithm having components driven by outputs of other algorithms.
26. The method of claim 25, wherein said single value is based upon weighted coefficients being applied to algorithm resultants.
27. The method of claim 11, wherein said ‘providing an output report’ step is further characterized as producing, with the one or more processors of the analyzer, a text and graphic indicia on printed media.
28. The method of claim 11, wherein said ‘providing an output report’ step is further characterized as producing, with the one or more processors of the analyzer, a text and graphic display at on an opto-electric display device.
29. The method of claim 28, wherein the report includes hyperlinks having URLs associated with video captured in response to an event trigger.
30. The system of claim 1, wherein the operator identity system is configured to receive entry and/or selection of the first operator identity information via one or more of tactile input through a user interface or a smart card reader.
31. The system of claim 1, wherein the analyzer is configured to apply the mathematical analysis to produce a first vehicle operator performance measure comprising a single score that reflects the performance of the first operator.
32. The system of claim 31, wherein the analyzer is configured such that the single score is a score between 0 and 1 and indicates a level of performance of the first operator relative to other operators.
33. The system of claim 32, wherein the analyzer is configured to assign a best performing operator a score of 1 and to assign a score between 0 and 1 to other individual operators to reflect the performance of an individual operator relative to the best performing operator.
Patent Citations (708)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US673203(A) | 1901-04-01 | Freund | Applicant |
| US673795(A) | 1901-05-01 | Hammer | Applicant |
| US673907(A) | 1901-05-01 | Johnson | Applicant |
| US676075(A) | 1901-06-01 | McDougall | Applicant |
| US679511(A) | 1901-07-01 | Richards | Applicant |
| US681036(A) | 1901-08-01 | Burg | Applicant |
| US681283(A) | 1901-08-01 | Waynick | Applicant |
| US681998(A) | 1901-09-01 | Swift | Applicant |
| US683155(A) | 1901-09-01 | Thompson | Applicant |
| US683214(A) | 1901-09-01 | Mansfield | Applicant |
| US684276(A) | 1901-10-01 | Lonergan | Applicant |
| US685082(A) | 1901-10-01 | Wood | Applicant |
| US685969(A) | 1901-11-01 | Campbell | Applicant |
| US686545(A) | 1901-11-01 | Selph | Applicant |
| US689849(A) | 1901-12-01 | Brown | Applicant |
| US691982(A) | 1902-01-01 | Sturgis | Applicant |
| US692834(A) | 1902-02-01 | Davis | Applicant |
| US694781(A) | 1902-03-01 | Prinz | Applicant |
| US2943141(A) | 1960-06-01 | Knight | Applicant |
| US3634866(A) | 1972-01-01 | Meyer | Applicant |
| US3781824(A) | 1973-12-01 | Caiati | Applicant |
| US3812287(A) | 1974-05-01 | Lemelson | Applicant |
| US3885090(A) | 1975-05-01 | Rosenbaum | Applicant |
| US3992656(A) | 1976-11-01 | Joy | Applicant |
| US4054752(A) | 1977-10-01 | Dennis | Applicant |
| US4271358(A) | 1981-06-01 | Schwarz | Applicant |
| US4276609(A) | 1981-06-01 | Patel | Applicant |
| US4280151(A) | 1981-07-01 | Tsunekawa | Applicant |
| US4281354(A) | 1981-07-01 | Conte | Applicant |
| US4401976(A) | 1983-08-01 | Stadelmayr | Applicant |
| US4409670(A) | 1983-10-01 | Herndon | Applicant |
| US4420773(A) | 1983-12-01 | Toyoda | Applicant |
| US4425097(A) | 1984-01-01 | Owens | Applicant |
| US4456931(A) | 1984-06-01 | Toyoda | Applicant |
| US4489351(A) | 1984-12-01 | d'Alayer de Costemore d'Arc | Applicant |
| US4496995(A) | 1985-01-01 | Colles | Applicant |
| US4500868(A) | 1985-02-01 | Tokitsu | Applicant |
| US4528547(A) | 1985-07-01 | Rodney | Applicant |
| US4533962(A) | 1985-08-01 | Decker | Applicant |
| US4558379(A) | 1985-12-01 | Huetter | Applicant |
| US4588267(A) | 1986-05-01 | Pastore | Applicant |
| US4593313(A) | 1986-06-01 | Nagasaki | Applicant |
| US4621335(A) | 1986-11-01 | Bluish | Applicant |
| US4625210(A) | 1986-11-01 | Sagl | Applicant |
| US4630110(A) | 1986-12-01 | Cotton | Applicant |
| US4632348(A) | 1986-12-01 | Keesling | Applicant |
| US4638289(A) | 1987-01-01 | Zottnik | Applicant |
| US4646241(A) | 1987-02-01 | Ratchford | Applicant |
| US4651143(A) | 1987-03-01 | Yamanaka | Applicant |
| US4671111(A) | 1987-06-01 | Lemelson | Applicant |
| US4718685(A) | 1988-01-01 | Kawabe | Applicant |
| US4754255(A) | 1988-06-01 | Sanders et al. | Examiner |
| US4758888(A) | 1988-07-01 | Lapidot | Applicant |
| US4763745(A) | 1988-08-01 | Eto | Applicant |
| US4785474(A) | 1988-11-01 | Bernstein | Applicant |
| US4789904(A) | 1988-12-01 | Peterson | Applicant |
| US4794566(A) | 1988-12-01 | Richards | Applicant |
| US4804937(A) | 1989-02-01 | Barbiaux | Applicant |
| US4806931(A) | 1989-02-01 | Nelson | Applicant |
| US4807096(A) | 1989-02-01 | Skogler | Applicant |
| US4814896(A) | 1989-03-01 | Heitzman | Applicant |
| US4837628(A) | 1989-06-01 | Sasaki | Applicant |
| US4839631(A) | 1989-06-01 | Tsuji | Applicant |
| US4843463(A) | 1989-06-01 | Michetti | Applicant |
| US4843578(A) | 1989-06-01 | Wade | Applicant |
| US4853856(A) | 1989-08-01 | Hanway | Applicant |
| US4853859(A) | 1989-08-01 | Morita | Applicant |
| US4866616(A) | 1989-09-01 | Takeuchi | Applicant |
| US4876597(A) | 1989-10-01 | Roy | Applicant |
| US4883349(A) | 1989-11-01 | Mittelhauser | Applicant |
| US4896855(A) | 1990-01-01 | Furnish | Applicant |
| US4926331(A) | 1990-05-01 | Windle | Applicant |
| US4930742(A) | 1990-06-01 | Schofield | Applicant |
| US4936533(A) | 1990-06-01 | Adams | Applicant |
| US4939652(A) | 1990-07-01 | Steiner | Applicant |
| US4942464(A) | 1990-07-01 | Milatz | Applicant |
| US4945244(A) | 1990-07-01 | Castleman | Applicant |
| US4949186(A) | 1990-08-01 | Peterson | Applicant |
| US4980913(A) | 1990-12-01 | Skret | Applicant |
| US4987541(A) | 1991-01-01 | Levente | Applicant |
| US4992943(A) | 1991-02-01 | McCracken | Applicant |
| US5012335(A) | 1991-04-01 | Cohodar | Applicant |
| US5027104(A) | 1991-06-01 | Reid | Applicant |
| US5046007(A) | 1991-09-01 | McCrery | Applicant |
| US5050166(A) | 1991-09-01 | Cantoni | Applicant |
| US5056056(A) | 1991-10-01 | Gustin | Applicant |
| US5057820(A) | 1991-10-01 | Markson | Applicant |
| US5096287(A) | 1992-03-01 | Kakinami | Applicant |
| US5100095(A) | 1992-03-01 | Haan | Applicant |
| US5111289(A) | 1992-05-01 | Lucas | Applicant |
| US5140434(A) | 1992-08-01 | Van Blessinger et al. | Applicant |
| US5140436(A) | 1992-08-01 | Blessinger | Applicant |
| US5140438(A) | 1992-08-01 | Kurahashi et al. | Applicant |
| US5144661(A) | 1992-09-01 | Shamosh | Applicant |
| US5178448(A) | 1993-01-01 | Adams | Applicant |
| US5185700(A) | 1993-02-01 | Bezos | Applicant |
| US5196938(A) | 1993-03-01 | Blessinger | Applicant |
| US5223844(A) | 1993-06-01 | Mansell | Applicant |
| US5224211(A) | 1993-06-01 | Roe | Applicant |
| US5262813(A) | 1993-11-01 | Scharton | Applicant |
| US5283433(A) | 1994-02-01 | Tsien | Applicant |
| US5305214(A) | 1994-04-01 | Komatsu | Applicant |
| US5305216(A) | 1994-04-01 | Okura | Applicant |
| US5308247(A) | 1994-05-01 | Dyrdek | Applicant |
| US5309485(A) | 1994-05-01 | Chao | Applicant |
| US5311197(A) | 1994-05-01 | Sorden | Applicant |
| US5321753(A) | 1994-06-01 | Gritton | Applicant |
| US5327288(A) | 1994-07-01 | Wellington | Applicant |
| US5330149(A) | 1994-07-01 | Haan | Applicant |
| US5343527(A) | 1994-08-01 | Moore | Applicant |
| US5353023(A) | 1994-10-01 | Mitsugi | Applicant |
| US5361326(A) | 1994-11-01 | Aparicio | Applicant |
| US5387926(A) | 1995-02-01 | Bellan | Applicant |
| US5388045(A) | 1995-02-01 | Kamiya | Applicant |
| US5388208(A) | 1995-02-01 | Weingartner | Applicant |
| US5404330(A) | 1995-04-01 | Lee | Applicant |
| US5408330(A) | 1995-04-01 | Squicciarini | Applicant |
| US5422543(A) | 1995-06-01 | Weinberg | Applicant |
| US5430431(A) | 1995-07-01 | Nelson | Applicant |
| US5430432(A) | 1995-07-01 | Camhi | Applicant |
| US5435184(A) | 1995-07-01 | Pineroli | Applicant |
| US5445024(A) | 1995-08-01 | Riley | Applicant |
| US5445027(A) | 1995-08-01 | Zoerner | Applicant |
| US5446659(A) | 1995-08-01 | Yamawaki | Applicant |
| US5455625(A) | 1995-10-01 | Englander | Applicant |
| US5455716(A) | 1995-10-01 | Suman | Applicant |
| US5465079(A) | 1995-11-01 | Bouchard | Applicant |
| US5473729(A) | 1995-12-01 | Bryant | Applicant |
| US5477141(A) | 1995-12-01 | Naether | Applicant |
| US5495242(A) | 1996-02-01 | Kick | Applicant |
| US5495243(A) | 1996-02-01 | McKenna | Applicant |
| US5497419(A) | 1996-03-01 | Hill | Examiner |
| US5499182(A) | 1996-03-01 | Ousborne | Examiner |
| US5504482(A) | 1996-04-01 | Schreder | Applicant |
| US5513011(A) | 1996-04-01 | Matsumoto | Applicant |
| US5515285(A) | 1996-05-01 | Garrett | Applicant |
| US5521633(A) | 1996-05-01 | Nakajima | Applicant |
| US5523811(A) | 1996-06-01 | Wada | Applicant |
| US5526269(A) | 1996-06-01 | Ishibashi | Applicant |
| US5530420(A) | 1996-06-01 | Tsuchiya | Applicant |
| US5537156(A) | 1996-07-01 | Katayama | Applicant |
| US5539454(A) | 1996-07-01 | Williams | Applicant |
| US5541590(A) | 1996-07-01 | Nishio | Applicant |
| US5544060(A) | 1996-08-01 | Fujii | Applicant |
| US5546191(A) | 1996-08-01 | Hibi | Applicant |
| US5546305(A) | 1996-08-01 | Kondo | Examiner |
| US5548273(A) | 1996-08-01 | Nicol | Applicant |
| US5552990(A) | 1996-09-01 | Ihara | Applicant |
| US5559496(A) | 1996-09-01 | Dubats | Applicant |
| US5568211(A) | 1996-10-01 | Bamford | Applicant |
| US5570087(A) | 1996-10-01 | Lemelson | Applicant |
| US5570127(A) | 1996-10-01 | Schmidt | Applicant |
| US5574424(A) | 1996-11-01 | Nguyen | Applicant |
| US5574443(A) | 1996-11-01 | Hsieh | Applicant |
| USD376571(S) | 1996-12-01 | Kokat | Applicant |
| US5581464(A) | 1996-12-01 | Woll et al. | Examiner |
| US5586130(A) | 1996-12-01 | Doyle | Applicant |
| US5590948(A) | 1997-01-01 | Moreno | Applicant |
| US5596382(A) | 1997-01-01 | Bamford | Applicant |
| US5600775(A) | 1997-02-01 | King | Applicant |
| US5610580(A) | 1997-03-01 | Lai | Applicant |
| US5612686(A) | 1997-03-01 | Takano | Applicant |
| US5631638(A) | 1997-05-01 | Kaspar | Applicant |
| US5638273(A) | 1997-06-01 | Coiner | Applicant |
| US5642106(A) | 1997-06-01 | Hancock | Applicant |
| US5646856(A) | 1997-07-01 | Kaesser | Applicant |
| US5652706(A) | 1997-07-01 | Morimoto | Applicant |
| USRE35590(E) | 1997-08-01 | Bezos | Applicant |
| US5654892(A) | 1997-08-01 | Fujii | Applicant |
| US5659355(A) | 1997-08-01 | Barron | Applicant |
| US5666120(A) | 1997-09-01 | Kline | Applicant |
| US5667176(A) | 1997-09-01 | Zamarripa | Applicant |
| US5669698(A) | 1997-09-01 | Veldman | Applicant |
| US5671451(A) | 1997-09-01 | Takahashi | Applicant |
| US5677979(A) | 1997-10-01 | Squicciarini | Applicant |
| US5680117(A) | 1997-10-01 | Arai | Applicant |
| US5680123(A) | 1997-10-01 | Lee | Applicant |
| US5686889(A) | 1997-11-01 | Hillis | Applicant |
| US5689442(A) | 1997-11-01 | Swanson | Applicant |
| US5696705(A) | 1997-12-01 | Zykan | Applicant |
| US5706362(A) | 1998-01-01 | Yabe | Applicant |
| US5712679(A) | 1998-01-01 | Coles | Applicant |
| US5717456(A) | 1998-02-01 | Rudt | Applicant |
| US5719554(A) | 1998-02-01 | Gagnon | Applicant |
| US5781145(A) | 1998-07-01 | Williams | Applicant |
| US5784021(A) | 1998-07-01 | Oliva | Applicant |
| US5784521(A) | 1998-07-01 | Nakatani | Applicant |
| US5790403(A) | 1998-08-01 | Nakayama | Applicant |
| US5790973(A) | 1998-08-01 | Blaker | Applicant |
| US5793308(A) | 1998-08-01 | Rosinski | Applicant |
| US5793420(A) | 1998-08-01 | Schmidt | Applicant |
| US5793739(A) | 1998-08-01 | Tanaka | Applicant |
| US5793985(A) | 1998-08-01 | Natarajan | Applicant |
| US5794165(A) | 1998-08-01 | Minowa | Applicant |
| US5797134(A) | 1998-08-01 | McMillan | Applicant |
| US5798458(A) | 1998-08-01 | Monroe | Applicant |
| US5800040(A) | 1998-09-01 | Santo | Applicant |
| US5802545(A) | 1998-09-01 | Coverdill | Applicant |
| US5802727(A) | 1998-09-01 | Blank | Applicant |
| US5805079(A) | 1998-09-01 | Lemelson | Applicant |
| US5813745(A) | 1998-09-01 | Fant | Applicant |
| US5815071(A) | 1998-09-01 | Doyle | Applicant |
| US5815093(A) | 1998-09-01 | Kikinis | Examiner |
| US5819198(A) | 1998-10-01 | Peretz | Applicant |
| US5825284(A) | 1998-10-01 | Dunwoody | Applicant |
| US5825412(A) | 1998-10-01 | Hobson | Applicant |
| US5844505(A) | 1998-12-01 | Van | Applicant |
| US5877897(A) | 1999-03-01 | Schofield | Applicant |
| US5896167(A) | 1999-04-01 | Omae | Applicant |
| US5897606(A) | 1999-04-01 | Miura | Applicant |
| US5899956(A) | 1999-05-01 | Chan | Applicant |
| US5901806(A) | 1999-05-01 | Takahashi | Applicant |
| US5914748(A) | 1999-06-01 | Parulski | Applicant |
| US5919239(A) | 1999-07-01 | Fraker | Applicant |
| US5926210(A) | 1999-07-01 | Hackett | Applicant |
| US5928291(A) | 1999-07-01 | Jenkins | Applicant |
| US5938321(A) | 1999-08-01 | Bos | Applicant |
| US5946404(A) | 1999-08-01 | Bakshi | Applicant |
| US5948038(A) | 1999-09-01 | Daly | Applicant |
| US5959367(A) | 1999-09-01 | Ofarrell | Applicant |
| US5978017(A) | 1999-11-01 | Tino | Applicant |
| US6002326(A) | 1999-12-01 | Turner | Applicant |
| US6006148(A) | 1999-12-01 | Strong | Applicant |
| US6008723(A) | 1999-12-01 | Yassan | Applicant |
| US6008841(A) | 1999-12-01 | Charlson | Applicant |
| US6009370(A) | 1999-12-01 | Minowa | Applicant |
| US6011492(A) | 2000-01-01 | Garesche | Applicant |
| USRE36590(E) | 2000-02-01 | Yanagi | Applicant |
| US6028528(A) | 2000-02-01 | Lorenzetti | Applicant |
| US6037860(A) | 2000-03-01 | Zander | Applicant |
| US6037977(A) | 2000-03-01 | Peterson | Applicant |
| US6049079(A) | 2000-04-01 | Noordam | Applicant |
| US6060989(A) | 2000-05-01 | Gehlot | Applicant |
| US6064792(A) | 2000-05-01 | Fox | Applicant |
| US6067488(A) | 2000-05-01 | Tano | Applicant |
| US6076026(A) | 2000-06-01 | Jambhekar | Applicant |
| US6084870(A) | 2000-07-01 | Wooten | Applicant |
| US6088635(A) | 2000-07-01 | Cox et al. | Applicant |
| US6092008(A) | 2000-07-01 | Bateman | Applicant |
| US6092193(A) | 2000-07-01 | Loomis | Applicant |
| US6100811(A) | 2000-08-01 | Hsu | Applicant |
| US6111254(A) | 2000-08-01 | Eden | Applicant |
| US6118768(A) | 2000-09-01 | Bhatia | Applicant |
| US6122738(A) | 2000-09-01 | Millard | Applicant |
| US6141611(A) | 2000-10-01 | Mackey et al. | Examiner |
| US6144296(A) | 2000-11-01 | Ishida | Applicant |
| US6147598(A) | 2000-11-01 | Murphy | Applicant |
| US6151065(A) | 2000-11-01 | Steed | Applicant |
| US6163338(A) | 2000-12-01 | Johnson | Applicant |
| US6167186(A) | 2000-12-01 | Kawasaki | Applicant |
| US6181373(B1) | 2001-01-01 | Coles | Applicant |
| US6185490(B1) | 2001-02-01 | Ferguson | Applicant |
| US6195605(B1) | 2001-02-01 | Tabler | Applicant |
| US6200139(B1) | 2001-03-01 | Clapper | Applicant |
| US6208919(B1) | 2001-03-01 | Barkesseh | Applicant |
| US6211907(B1) | 2001-04-01 | Scaman | Applicant |
| US6218960(B1) | 2001-04-01 | Ishikawa | Applicant |
| US6246933(B1) | 2001-06-01 | Bague | Applicant |
| US6246934(B1) | 2001-06-01 | Otake | Applicant |
| US6252544(B1) | 2001-06-01 | Hoffberg | Applicant |
| US6253129(B1) | 2001-06-01 | Jenkins | Applicant |
| US6259475(B1) | 2001-07-01 | Ramachandran | Applicant |
| US6263265(B1) | 2001-07-01 | Fera | Applicant |
| US6298290(B1) | 2001-10-01 | Abe et al. | Applicant |
| US6300875(B1) | 2001-10-01 | Schafer | Applicant |
| US6333759(B1) | 2001-12-01 | Mazzilli | Applicant |
| US6337622(B1) | 2002-01-01 | Sugano | Applicant |
| US6349250(B1) | 2002-02-01 | Hart | Applicant |
| US6353734(B1) | 2002-03-01 | Wright | Applicant |
| US6356823(B1) | 2002-03-01 | Iannotti | Applicant |
| US6360147(B1) | 2002-03-01 | Lee | Applicant |
| US6389339(B1) | 2002-05-01 | Just | Applicant |
| US6389340(B1) | 2002-05-01 | Rayner | Examiner |
| US6405112(B1) | 2002-06-01 | Rayner | Applicant |
| US6405132(B1) | 2002-06-01 | Breed | Applicant |
| US6408232(B1) | 2002-06-01 | Cannon | Applicant |
| US6411874(B2) | 2002-06-01 | Morgan | Applicant |
| US6421080(B1) | 2002-07-01 | Lambert | Applicant |
| US6434510(B1) | 2002-08-01 | Callaghan | Applicant |
| US6449540(B1) | 2002-09-01 | Rayner | Applicant |
| US6456321(B1) | 2002-09-01 | Ito | Applicant |
| US6459988(B1) | 2002-10-01 | Fan | Applicant |
| US6470241(B2) | 2002-10-01 | Yoshikawa | Applicant |
| US6472771(B1) | 2002-10-01 | Frese et al. | Applicant |
| US6493650(B1) | 2002-12-01 | Rodgers | Applicant |
| US6505106(B1) | 2003-01-01 | Lawrence | Applicant |
| US6507838(B1) | 2003-01-01 | Syeda-Mahmood | Applicant |
| US6516256(B1) | 2003-02-01 | Hartmann | Applicant |
| US6518881(B2) | 2003-02-01 | Monroe | Applicant |
| US6525672(B2) | 2003-02-01 | Chainer | Applicant |
| US6529159(B1) | 2003-03-01 | Fan | Applicant |
| US6535804(B1) | 2003-03-01 | Chun | Applicant |
| US6552682(B1) | 2003-04-01 | Fan | Applicant |
| US6556905(B1) | 2003-04-01 | Mittelsteadt et al. | Applicant |
| US6559769(B2) | 2003-05-01 | Anthony | Applicant |
| US6575902(B1) | 2003-06-01 | Burton | Applicant |
| US6580983(B2) | 2003-06-01 | Laguer-Diaz | Applicant |
| US6594576(B2) | 2003-07-01 | Fan | Applicant |
| US6611740(B2) | 2003-08-01 | Lowrey et al. | Applicant |
| US6611755(B1) | 2003-08-01 | Coffee | Applicant |
| US6624611(B2) | 2003-09-01 | Kirmuss | Applicant |
| US6629029(B1) | 2003-09-01 | Giles | Applicant |
| US6629030(B2) | 2003-09-01 | Klausner | Applicant |
| US6636791(B2) | 2003-10-01 | Okada | Applicant |
| US6664922(B1) | 2003-12-01 | Fan | Applicant |
| US6679702(B1) | 2004-01-01 | Rau | Applicant |
| US6684137(B2) | 2004-01-01 | Takagi | Applicant |
| US6694483(B1) | 2004-02-01 | Nagata | Applicant |
| US6701234(B1) | 2004-03-01 | Vogelsang | Applicant |
| US6714894(B1) | 2004-03-01 | Tobey | Applicant |
| US6718239(B2) | 2004-04-01 | Rayner | Applicant |
| US6721640(B2) | 2004-04-01 | Glenn | Applicant |
| US6728612(B1) | 2004-04-01 | Carver et al. | Applicant |
| US6732031(B1) | 2004-05-01 | Lightner | Applicant |
| US6732032(B1) | 2004-05-01 | Baner et al. | Applicant |
| US6735503(B2) | 2004-05-01 | Ames | Applicant |
| US6737954(B2) | 2004-05-01 | Chainer et al. | Applicant |
| US6738697(B2) | 2004-05-01 | Breed | Applicant |
| US6739078(B2) | 2004-05-01 | Morley et al. | Applicant |
| US6741168(B2) | 2004-05-01 | Webb | Applicant |
| US6745153(B2) | 2004-06-01 | White | Applicant |
| US6747692(B2) | 2004-06-01 | Patel | Applicant |
| US6748305(B1) | 2004-06-01 | Klausner | Applicant |
| US6760757(B1) | 2004-07-01 | Lundberg et al. | Applicant |
| US6762513(B2) | 2004-07-01 | Landgraf | Applicant |
| US6795017(B1) | 2004-09-01 | Puranik | Applicant |
| US6795111(B1) | 2004-09-01 | Mazzilli | Applicant |
| US6795759(B2) | 2004-09-01 | Doyle | Applicant |
| US6798743(B1) | 2004-09-01 | Ma | Applicant |
| US6804590(B2) | 2004-10-01 | Sato | Applicant |
| US6810362(B2) | 2004-10-01 | Adachi et al. | Applicant |
| US6812831(B2) | 2004-11-01 | Ikeda | Applicant |
| US6819989(B2) | 2004-11-01 | Maeda et al. | Applicant |
| US6831556(B1) | 2004-12-01 | Boykin | Applicant |
| US6832140(B2) | 2004-12-01 | Fan | Applicant |
| US6832141(B2) | 2004-12-01 | Skeen et al. | Applicant |
| US6836712(B2) | 2004-12-01 | Nishina | Applicant |
| US6842762(B2) | 2005-01-01 | Raither et al. | Applicant |
| US6847873(B1) | 2005-01-01 | Li | Applicant |
| US6850823(B2) | 2005-02-01 | Eun et al. | Applicant |
| US6859695(B2) | 2005-02-01 | Klausner | Applicant |
| US6862524(B1) | 2005-03-01 | Nagda | Applicant |
| US6865457(B1) | 2005-03-01 | Mittelsteadt et al. | Applicant |
| US6867733(B2) | 2005-03-01 | Sandhu | Applicant |
| US6873261(B2) | 2005-03-01 | Anthony | Applicant |
| US6882313(B1) | 2005-04-01 | Fan | Applicant |
| US6894606(B2) | 2005-05-01 | Forbes et al. | Examiner |
| US6895248(B1) | 2005-05-01 | Akyol | Applicant |
| US6898492(B2) | 2005-05-01 | de Leon et al. | Applicant |
| US6898493(B2) | 2005-05-01 | Ehrman | Applicant |
| US6919823(B1) | 2005-07-01 | Lock | Applicant |
| US6922566(B2) | 2005-07-01 | Puranik | Applicant |
| US6928348(B1) | 2005-08-01 | Lightner et al. | Applicant |
| US6931309(B2) | 2005-08-01 | Phelan | Applicant |
| US6947817(B2) | 2005-09-01 | Diem | Applicant |
| US6950122(B1) | 2005-09-01 | Mirabile | Applicant |
| US6954223(B2) | 2005-10-01 | Miyazawa | Applicant |
| US6988034(B1) | 2006-01-01 | Marlatt | Applicant |
| US7012632(B2) | 2006-03-01 | Freeman | Applicant |
| US7020548(B2) | 2006-03-01 | Saito | Applicant |
| US7023333(B2) | 2006-04-01 | Blanco | Applicant |
| US7039510(B2) | 2006-05-01 | Gumpinger | Applicant |
| US7076348(B2) | 2006-07-01 | Bucher | Applicant |
| US7079927(B1) | 2006-07-01 | Tano et al. | Examiner |
| US7082359(B2) | 2006-07-01 | Breed | Applicant |
| US7082382(B1) | 2006-07-01 | Rose et al. | Applicant |
| US7088387(B1) | 2006-08-01 | Freeman | Applicant |
| US7095782(B1) | 2006-08-01 | Cohen | Applicant |
| US7098812(B2) | 2006-08-01 | Hirota | Applicant |
| US7100190(B2) | 2006-08-01 | Johnson | Applicant |
| US7113853(B2) | 2006-09-01 | Hecklinger | Applicant |
| US7117075(B1) | 2006-10-01 | Larschan | Applicant |
| US7119832(B2) | 2006-10-01 | Blanco | Applicant |
| US7155321(B2) | 2006-12-01 | Bromley | Applicant |
| US7177738(B2) | 2007-02-01 | Diaz | Applicant |
| US7209833(B2) | 2007-04-01 | Isaji | Applicant |
| US7239252(B2) | 2007-07-01 | Kato | Applicant |
| US7265663(B2) | 2007-09-01 | Steele | Applicant |
| US7272179(B2) | 2007-09-01 | Siemens | Applicant |
| US7308341(B2) | 2007-12-01 | Schofield | Applicant |
| US7317974(B2) | 2008-01-01 | Luskin | Applicant |
| US7348895(B2) | 2008-03-01 | Lagassey | Applicant |
| US7349027(B2) | 2008-03-01 | Endo | Applicant |
| US7370261(B2) | 2008-05-01 | Winarski | Applicant |
| US7382933(B2) | 2008-06-01 | Dorai | Applicant |
| US7386376(B2) | 2008-06-01 | Basir | Applicant |
| US7389178(B2) | 2008-06-01 | Raz | Applicant |
| US7457693(B2) | 2008-11-01 | Olsen | Applicant |
| US7536457(B2) | 2009-05-01 | Miller | Applicant |
| US7561054(B2) | 2009-07-01 | Raz | Applicant |
| US7623754(B1) | 2009-11-01 | McKain | Applicant |
| US7659827(B2) | 2010-02-01 | Gunderson | Applicant |
| US7667731(B2) | 2010-02-01 | Kreiner | Applicant |
| US7702442(B2) | 2010-04-01 | Takenaka | Applicant |
| US7725216(B2) | 2010-05-01 | Kim | Applicant |
| US7768548(B2) | 2010-08-01 | Silvernail | Applicant |
| US7804426(B2) | 2010-09-01 | Etcheson | Applicant |
| US7821421(B2) | 2010-10-01 | Tamir | Applicant |
| US7853376(B2) | 2010-12-01 | Peng | Applicant |
| US7974748(B2) | 2011-07-01 | Goerick | Applicant |
| US8113844(B2) | 2012-02-01 | Huang | Applicant |
| US8140358(B1) | 2012-03-01 | Ling | Applicant |
| US8311858(B2) | 2012-11-01 | Everett | Applicant |
| US8314708(B2) | 2012-11-01 | Gunderson | Applicant |
| US8321066(B2) | 2012-11-01 | Becker | Applicant |
| US8508353(B2) | 2013-08-01 | Cook | Applicant |
| US8538696(B1) | 2013-09-01 | Cassanova | Applicant |
| US8564446(B2) | 2013-10-01 | Gunderson et al. | Examiner |
| US8635557(B2) | 2014-01-01 | Geise | Applicant |
| US2001/0005217(A1) | 2001-06-01 | Hamilton | Applicant |
| US2001/0005804(A1) | 2001-06-01 | Rayner | Applicant |
| US2001/0018628(A1) | 2001-08-01 | Jenkins | Applicant |
| US2001/0020204(A1) | 2001-09-01 | Runyon | Applicant |
| US2002/0019689(A1) | 2002-02-01 | Harrison | Applicant |
| US2002/0027502(A1) | 2002-03-01 | Mayor | Applicant |
| US2002/0029109(A1) | 2002-03-01 | Wong | Applicant |
| US2002/0035422(A1) | 2002-03-01 | Sasaki | Applicant |
| US2002/0044225(A1) | 2002-04-01 | Rakib | Applicant |
| US2002/0059453(A1) | 2002-05-01 | Eriksson | Applicant |
| US2002/0061758(A1) | 2002-05-01 | Zarlengo | Applicant |
| US2002/0087240(A1) | 2002-07-01 | Raithel | Applicant |
| US2002/0091473(A1) | 2002-07-01 | Gardner et al. | Applicant |
| US2002/0105438(A1) | 2002-08-01 | Forbes | Applicant |
| US2002/0107619(A1) | 2002-08-01 | Klausner | Applicant |
| US2002/0111725(A1) | 2002-08-01 | Burge | Applicant |
| US2002/0111756(A1) | 2002-08-01 | Modgil | Applicant |
| US2002/0118206(A1) | 2002-08-01 | Knittel | Applicant |
| US2002/0120374(A1) | 2002-08-01 | Douros | Applicant |
| US2002/0135679(A1) | 2002-09-01 | Scaman | Applicant |
| US2002/0138587(A1) | 2002-09-01 | Koehler | Applicant |
| US2002/0163532(A1) | 2002-11-01 | Thomas | Applicant |
| US2002/0169529(A1) | 2002-11-01 | Kim | Applicant |
| US2002/0169530(A1) | 2002-11-01 | Laguer-Diaz et al. | Applicant |
| US2002/0183905(A1) | 2002-12-01 | Maeda et al. | Applicant |
| US2003/0016753(A1) | 2003-01-01 | Kim | Applicant |
| US2003/0028298(A1) | 2003-02-01 | Macky et al. | Applicant |
| US2003/0053433(A1) | 2003-03-01 | Chun | Applicant |
| US2003/0055557(A1) | 2003-03-01 | Dutta | Applicant |
| US2003/0065805(A1) | 2003-04-01 | Barnes | Applicant |
| US2003/0067541(A1) | 2003-04-01 | Joao | Applicant |
| US2003/0079041(A1) | 2003-04-01 | Parrella | Applicant |
| US2003/0080713(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0080878(A1) | 2003-05-01 | Kirmuss | Examiner |
| US2003/0081121(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081122(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081127(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081128(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081934(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0081935(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0095688(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0112133(A1) | 2003-06-01 | Webb | Applicant |
| US2003/0125854(A1) | 2003-07-01 | Kawasaki | Applicant |
| US2003/0144775(A1) | 2003-07-01 | Klausner | Applicant |
| US2003/0154009(A1) | 2003-08-01 | Basir et al. | Applicant |
| US2003/0158638(A1) | 2003-08-01 | Yakes | Applicant |
| US2003/0177187(A1) | 2003-09-01 | Levine | Applicant |
| US2003/0187704(A1) | 2003-10-01 | Hashiguchi | Applicant |
| US2003/0191568(A1) | 2003-10-01 | Breed | Applicant |
| US2003/0195678(A1) | 2003-10-01 | Betters | Applicant |
| US2003/0214585(A1) | 2003-11-01 | Bakewell | Applicant |
| US2003/0220835(A1) | 2003-11-01 | Barnes | Applicant |
| US2003/0222880(A1) | 2003-12-01 | Waterman | Applicant |
| US2004/0008255(A1) | 2004-01-01 | Lewellen | Applicant |
| US2004/0033058(A1) | 2004-02-01 | Reich | Applicant |
| US2004/0039503(A1) | 2004-02-01 | Doyle | Applicant |
| US2004/0039504(A1) | 2004-02-01 | Coffee | Applicant |
| US2004/0044452(A1) | 2004-03-01 | Bauer et al. | Applicant |
| US2004/0044592(A1) | 2004-03-01 | Ubik | Applicant |
| US2004/0054444(A1) | 2004-03-01 | Abeska | Applicant |
| US2004/0054513(A1) | 2004-03-01 | Laird | Applicant |
| US2004/0054689(A1) | 2004-03-01 | Salmonsen | Applicant |
| US2004/0070926(A1) | 2004-04-01 | Boykin et al. | Applicant |
| US2004/0083041(A1) | 2004-04-01 | Skeen et al. | Applicant |
| US2004/0088090(A1) | 2004-05-01 | Wee | Applicant |
| US2004/0103008(A1) | 2004-05-01 | Wahlbin | Applicant |
| US2004/0103010(A1) | 2004-05-01 | Wahlbin | Applicant |
| US2004/0111189(A1) | 2004-06-01 | Miyazawa | Applicant |
| US2004/0138794(A1) | 2004-07-01 | Saito et al. | Applicant |
| US2004/0145457(A1) | 2004-07-01 | Schofield et al. | Applicant |
| US2004/0153244(A1) | 2004-08-01 | Kellum | Applicant |
| US2004/0153362(A1) | 2004-08-01 | Bauer | Applicant |
| US2004/0167689(A1) | 2004-08-01 | Bromley | Applicant |
| US2004/0179600(A1) | 2004-09-01 | Wells | Applicant |
| US2004/0181326(A1) | 2004-09-01 | Adams | Applicant |
| US2004/0184548(A1) | 2004-09-01 | Kerbiriou | Applicant |
| US2004/0209594(A1) | 2004-10-01 | Naboulsi | Applicant |
| US2004/0210353(A1) | 2004-10-01 | Rice | Applicant |
| US2004/0233284(A1) | 2004-11-01 | Lesesky | Applicant |
| US2004/0236474(A1) | 2004-11-01 | Chowdhary | Applicant |
| US2004/0243285(A1) | 2004-12-01 | Gounder | Applicant |
| US2004/0243308(A1) | 2004-12-01 | Irish | Applicant |
| US2004/0243668(A1) | 2004-12-01 | Harjanto | Applicant |
| US2004/0254698(A1) | 2004-12-01 | Hubbard | Applicant |
| US2005/0021199(A1) | 2005-01-01 | Zimmerman | Applicant |
| US2005/0043869(A1) | 2005-02-01 | Funkhouser | Applicant |
| US2005/0060070(A1) | 2005-03-01 | Kapolka | Applicant |
| US2005/0060071(A1) | 2005-03-01 | Winner | Applicant |
| US2005/0065716(A1) | 2005-03-01 | Timko | Applicant |
| US2005/0073585(A1) | 2005-04-01 | Ettinger | Applicant |
| US2005/0078423(A1) | 2005-04-01 | Kim | Applicant |
| US2005/0088291(A1) | 2005-04-01 | Blanco | Applicant |
| US2005/0099498(A1) | 2005-05-01 | Lao et al. | Applicant |
| US2005/0100329(A1) | 2005-05-01 | Lao et al. | Applicant |
| US2005/0102074(A1) | 2005-05-01 | Kolls | Applicant |
| US2005/0125117(A1) | 2005-06-01 | Breed | Applicant |
| US2005/0131585(A1) | 2005-06-01 | Luskin | Applicant |
| US2005/0131595(A1) | 2005-06-01 | Luskin | Applicant |
| US2005/0131597(A1) | 2005-06-01 | Raz | Applicant |
| US2005/0136949(A1) | 2005-06-01 | Barnes | Applicant |
| US2005/0137757(A1) | 2005-06-01 | Phelan | Applicant |
| US2005/0137796(A1) | 2005-06-01 | Gumpinger | Applicant |
| US2005/0146458(A1) | 2005-07-01 | Carmichael | Applicant |
| US2005/0149238(A1) | 2005-07-01 | Stefani | Applicant |
| US2005/0159964(A1) | 2005-07-01 | Sonnenrein | Applicant |
| US2005/0166258(A1) | 2005-07-01 | Vasilevsky | Applicant |
| US2005/0171692(A1) | 2005-08-01 | Hamblen | Applicant |
| US2005/0174217(A1) | 2005-08-01 | Basir | Applicant |
| US2005/0182538(A1) | 2005-08-01 | Phelan | Applicant |
| US2005/0182824(A1) | 2005-08-01 | Cotte | Applicant |
| US2005/0185052(A1) | 2005-08-01 | Raisinghani | Applicant |
| US2005/0185936(A9) | 2005-08-01 | Lao | Applicant |
| US2005/0192749(A1) | 2005-09-01 | Flann | Applicant |
| US2005/0197748(A1) | 2005-09-01 | Hoist | Applicant |
| US2005/0200714(A1) | 2005-09-01 | Marchese | Applicant |
| US2005/0203683(A1) | 2005-09-01 | Olsen | Applicant |
| US2005/0206741(A1) | 2005-09-01 | Raber | Applicant |
| US2005/0212920(A1) | 2005-09-01 | Evans | Applicant |
| US2005/0216144(A1) | 2005-09-01 | Baldassa | Applicant |
| US2005/0228560(A1) | 2005-10-01 | Doherty | Applicant |
| US2005/0233805(A1) | 2005-10-01 | Okajima | Applicant |
| US2005/0251304(A1) | 2005-11-01 | Cancellara | Applicant |
| US2005/0258942(A1) | 2005-11-01 | Manasseh | Applicant |
| US2005/0264691(A1) | 2005-12-01 | Endo | Applicant |
| US2005/0283284(A1) | 2005-12-01 | Grenier | Applicant |
| US2006/0001671(A1) | 2006-01-01 | Kamijo | Applicant |
| US2006/0007151(A1) | 2006-01-01 | Ram | Applicant |
| US2006/0011399(A1) | 2006-01-01 | Brockway | Applicant |
| US2006/0015233(A1) | 2006-01-01 | Olsen | Applicant |
| US2006/0022842(A1) | 2006-02-01 | Zoladek | Applicant |
| US2006/0025897(A1) | 2006-02-01 | Shostak | Applicant |
| US2006/0030986(A1) | 2006-02-01 | Peng | Applicant |
| US2006/0040239(A1) | 2006-02-01 | Cummins | Applicant |
| US2006/0047380(A1) | 2006-03-01 | Welch | Applicant |
| US2006/0053038(A1) | 2006-03-01 | Warren et al. | Examiner |
| US2006/0055521(A1) | 2006-03-01 | Blanco | Applicant |
| US2006/0057543(A1) | 2006-03-01 | Roald | Applicant |
| US2006/0058950(A1) | 2006-03-01 | Kato | Applicant |
| US2006/0072792(A1) | 2006-04-01 | Toda | Applicant |
| US2006/0078853(A1) | 2006-04-01 | Lanktree | Applicant |
| US2006/0092043(A1) | 2006-05-01 | Lagassey | Applicant |
| US2006/0095175(A1) | 2006-05-01 | deWaal et al. | Applicant |
| US2006/0095199(A1) | 2006-05-01 | Lagassey | Applicant |
| US2006/0095349(A1) | 2006-05-01 | Morgan | Applicant |
| US2006/0103127(A1) | 2006-05-01 | Lie | Applicant |
| US2006/0106514(A1) | 2006-05-01 | Liebl | Applicant |
| US2006/0111817(A1) | 2006-05-01 | Phelan | Applicant |
| US2006/0122749(A1) | 2006-06-01 | Phelan | Applicant |
| US2006/0142913(A1) | 2006-06-01 | Coffee | Applicant |
| US2006/0147187(A1) | 2006-07-01 | Takemoto | Applicant |
| US2006/0161960(A1) | 2006-07-01 | Benoit | Applicant |
| US2006/0168271(A1) | 2006-07-01 | Pabari | Applicant |
| US2006/0178793(A1) | 2006-08-01 | Hecklinger | Applicant |
| US2006/0209090(A1) | 2006-09-01 | Kelly et al. | Applicant |
| US2006/0209840(A1) | 2006-09-01 | Paatela | Applicant |
| US2006/0212195(A1) | 2006-09-01 | Veith | Applicant |
| US2006/0226344(A1) | 2006-10-01 | Werth | Applicant |
| US2006/0229780(A1) | 2006-10-01 | Underdahl | Applicant |
| US2006/0242680(A1) | 2006-10-01 | Johnson | Applicant |
| US2006/0247833(A1) | 2006-11-01 | Malhotra | Applicant |
| US2006/0253307(A1) | 2006-11-01 | Warren | Applicant |
| US2006/0259218(A1) | 2006-11-01 | Wu | Applicant |
| US2006/0261931(A1) | 2006-11-01 | Cheng | Examiner |
| US2007/0001831(A1) | 2007-01-01 | Raz et al. | Examiner |
| US2007/0005404(A1) | 2007-01-01 | Raz | Applicant |
| US2007/0027583(A1) | 2007-02-01 | Tamir | Applicant |
| US2007/0027726(A1) | 2007-02-01 | Warren | Applicant |
| US2007/0120948(A1) | 2007-05-01 | Fujioka | Applicant |
| US2007/0124332(A1) | 2007-05-01 | Ballesty et al. | Examiner |
| US2007/0132773(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0135979(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0135980(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0136078(A1) | 2007-06-01 | Plante | Examiner |
| US2007/0142986(A1) | 2007-06-01 | Alaous | Applicant |
| US2007/0143499(A1) | 2007-06-01 | Chang | Applicant |
| US2007/0150138(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0150140(A1) | 2007-06-01 | Seymour | Applicant |
| US2007/0173994(A1) | 2007-07-01 | Kubo | Applicant |
| US2007/0179691(A1) | 2007-08-01 | Grenn | Applicant |
| US2007/0183635(A1) | 2007-08-01 | Weidhaas | Applicant |
| US2007/0208494(A1) | 2007-09-01 | Chapman | Applicant |
| US2007/0216521(A1) | 2007-09-01 | Guensler | Applicant |
| US2007/0219685(A1) | 2007-09-01 | Plante | Applicant |
| US2007/0219686(A1) | 2007-09-01 | Plante | Applicant |
| US2007/0241874(A1) | 2007-10-01 | Okpysh | Applicant |
| US2007/0257781(A1) | 2007-11-01 | Denson | Applicant |
| US2007/0257782(A1) | 2007-11-01 | Etcheson | Applicant |
| US2007/0257804(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0257815(A1) | 2007-11-01 | Gunderson | Applicant |
| US2007/0260677(A1) | 2007-11-01 | DeMarco | Applicant |
| US2007/0268158(A1) | 2007-11-01 | Gunderson et al. | Applicant |
| US2007/0271105(A1) | 2007-11-01 | Gunderson | Applicant |
| US2007/0273480(A1) | 2007-11-01 | Burkman | Applicant |
| US2007/0279214(A1) | 2007-12-01 | Buehler | Applicant |
| US2007/0299612(A1) | 2007-12-01 | Kimura | Applicant |
| US2008/0059019(A1) | 2008-03-01 | Delia | Applicant |
| US2008/0111666(A1) | 2008-05-01 | Plante | Applicant |
| US2008/0143834(A1) | 2008-06-01 | Comeau | Applicant |
| US2008/0147267(A1) | 2008-06-01 | Plante et al. | Applicant |
| US2008/0157510(A1) | 2008-07-01 | Breed | Applicant |
| US2008/0167775(A1) | 2008-07-01 | Kuttenberger | Applicant |
| US2008/0169914(A1) | 2008-07-01 | Albertson | Applicant |
| US2008/0177436(A1) | 2008-07-01 | Fortson | Applicant |
| US2008/0252485(A1) | 2008-10-01 | Lagassey | Applicant |
| US2008/0269978(A1) | 2008-10-01 | Shirole | Applicant |
| US2008/0281485(A1) | 2008-11-01 | Plante | Applicant |
| US2008/0309762(A1) | 2008-12-01 | Howard et al. | Applicant |
| US2009/0043971(A1) | 2009-02-01 | Kim | Applicant |
| US2009/0216775(A1) | 2009-08-01 | Ratliff et al. | Applicant |
| US2009/0224869(A1) | 2009-09-01 | Baker | Applicant |
| US2009/0290848(A1) | 2009-11-01 | Brown | Applicant |
| US2009/0299622(A1) | 2009-12-01 | Denaro | Applicant |
| US2009/0312998(A1) | 2009-12-01 | Berckmans | Applicant |
| US2009/0326796(A1) | 2009-12-01 | Prokhorov | Applicant |
| US2010/0045451(A1) | 2010-02-01 | Periwal | Applicant |
| US2010/0063672(A1) | 2010-03-01 | Anderson | Applicant |
| US2010/0063850(A1) | 2010-03-01 | Daniel | Applicant |
| US2010/0070175(A1) | 2010-03-01 | Soulchin | Applicant |
| US2010/0085193(A1) | 2010-04-01 | Boss | Applicant |
| US2010/0085430(A1) | 2010-04-01 | Kreiner | Applicant |
| US2010/0087984(A1) | 2010-04-01 | Joseph | Applicant |
| US2010/0153146(A1) | 2010-06-01 | Angell | Applicant |
| US2010/0157061(A1) | 2010-06-01 | Katsman | Applicant |
| US2010/0220892(A1) | 2010-09-01 | Kawakubo | Applicant |
| US2010/0250021(A1) | 2010-09-01 | Cook | Applicant |
| US2010/0268415(A1) | 2010-10-01 | Ishikawa | Applicant |
| US2011/0035139(A1) | 2011-02-01 | Konlditslotis | Applicant |
| US2011/0043624(A1) | 2011-02-01 | Haug | Applicant |
| US2011/0060496(A1) | 2011-03-01 | Nielsen | Applicant |
| US2011/0077028(A1) | 2011-03-01 | Wilkes | Applicant |
| US2011/0091079(A1) | 2011-04-01 | Yu-Song | Applicant |
| US2011/0093159(A1) | 2011-04-01 | Boling | Applicant |
| US2011/0121960(A1) | 2011-05-01 | Tsai | Applicant |
| US2011/0125365(A1) | 2011-05-01 | Larschan | Applicant |
| US2011/0130916(A1) | 2011-06-01 | Mayer | Applicant |
| US2011/0173015(A1) | 2011-07-01 | Chapman | Applicant |
| US2011/0224891(A1) | 2011-09-01 | Iwuchukwu | Applicant |
| US2011/0273568(A1) | 2011-11-01 | Lagassey | Applicant |
| US2011/0283223(A1) | 2011-11-01 | Vattinen et al. | Applicant |
| US2011/0304446(A1) | 2011-12-01 | Basson | Applicant |
| US2012/0035788(A1) | 2012-02-01 | Trepagnier | Applicant |
| US2012/0046803(A1) | 2012-02-01 | Inou | Applicant |
| US2012/0071140(A1) | 2012-03-01 | Oesterling | Applicant |
| US2012/0100509(A1) | 2012-04-01 | Gunderson | Applicant |
| US2013/0006469(A1) | 2013-01-01 | Green | Applicant |
| US2013/0030660(A1) | 2013-01-01 | Fujimoto | Applicant |
| US2013/0332004(A1) | 2013-12-01 | Gompert et al. | Applicant |
| US2014/0226010(A1) | 2014-08-01 | Molin | Applicant |
| CA2469728(A1) | 2005-12-01 | Applicant | |
| CA2692415(A1) | 2011-08-01 | Applicant | |
| DE4416991(A1) | 1995-11-01 | Applicant | |
| DE20311262 | 2003-09-01 | Applicant | |
| DE202005008238 | 2005-09-01 | Applicant | |
| DE102004004669(A1) | 2005-12-01 | Applicant | |
| EP708427(A2) | 1996-04-01 | Applicant | |
| EP840270(A2) | 1998-05-01 | Applicant | |
| EP848270(A2) | 1998-05-01 | Applicant | |
| EP1170697(A2) | 2002-01-01 | Applicant | |
| EP1324274(A2) | 2003-07-01 | Applicant | |
| EP1355278(A1) | 2003-10-01 | Applicant | |
| EP1427165(A2) | 2004-06-01 | Applicant | |
| EP1818873(A1) | 2007-08-01 | Applicant | |
| GB2268608(A) | 1994-01-01 | Applicant | |
| GB2402530(A) | 2004-12-01 | Applicant | |
| GB2447184(B) | 2011-06-01 | Applicant | |
| JP58085110 | 1983-05-01 | Applicant | |
| JPS5885110(A) | 1983-05-01 | Applicant | |
| JP62091092 | 1987-04-01 | Applicant | |
| JPS6291092(A) | 1987-04-01 | Applicant | |
| JPS62166135(A) | 1987-07-01 | Applicant | |
| JP2056197 | 1990-02-01 | Applicant | |
| JPH0256197(A) | 1990-02-01 | Applicant | |
| JPH04257189(A) | 1992-09-01 | Applicant | |
| JPH05137144(A) | 1993-06-01 | Applicant | |
| JP5294188 | 1993-11-01 | Applicant | |
| JPH08124069(A) | 1996-05-01 | Applicant | |
| JPH09163357(A) | 1997-06-01 | Applicant | |
| JPH09272399(A) | 1997-10-01 | Applicant | |
| JP10076880 | 1998-03-01 | Applicant | |
| JPH1076880(A) | 1998-03-01 | Applicant | |
| JP2002191017(A) | 2002-07-01 | Applicant | |
| WO8809023(A1) | 1988-11-01 | Applicant | |
| WO9005076 | 1990-05-01 | Applicant | |
| WO9427844 | 1994-12-01 | Applicant | |
| WO9600957(A1) | 1996-01-01 | Applicant | |
| WO9701246 | 1997-01-01 | Applicant | |
| WO9726750(A1) | 1997-07-01 | Applicant | |
| WO9937503 | 1999-07-01 | Applicant | |
| WO9940545(A1) | 1999-08-01 | Applicant | |
| WO9962741 | 1999-12-01 | Applicant | |
| WO7150(A1) | 2000-02-01 | Applicant | |
| WO28410(A1) | 2000-05-01 | Applicant | |
| WO48033 | 2000-08-01 | Applicant | |
| WO77620 | 2000-12-01 | Applicant | |
| WO123214 | 2001-04-01 | Applicant | |
| WO125054 | 2001-04-01 | Applicant | |
| WO146710(A2) | 2001-06-01 | Applicant | |
| WO2006022824(A2) | 2006-03-01 | Applicant | |
| WO2011055743(A1) | 2011-05-01 | Applicant |
Non-Patent Literature (150)
- Hindsight 20/20 Software Version 4.0 User's Manual.Applicant
- Inovate Motorsports, OT-1 16 Channel OBD-II Interface User Manual, Version 1.0, Nov. 28, 2007, pp. 3, 4, 21 & 27.Applicant
- Trivinci Systems, LLC, Race-Keeper Systems User Guide, Jan. 2011, v1, 1.02, pp. 34 and 39.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 14/036,299, mailed Aug. 12, 2014.Applicant
- Adaptec published and sold its VideoOh! DVD software USB 2.0 Edition in at least Jan. 24, 2003.Applicant
- Ambulance Companies Use Video Technology to Improve Driving Behavior, Ambulance Industry Journal, Spring 2003.Applicant
- Amended Complaint for Patent Infringement, Trade Secret Misappropriation, Unfair Competition and Conversion in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California, Document 34, filed Oct. 20, 2011, pp. 1-15.Applicant
- Amendment filed Dec. 23, 2009 during prosecution of U.S. Appl. No. 11/566,424.Applicant
- Answer to Amended Complaint; Counterclaims; and Demand for Jury Trial in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 47, filed Dec. 13, 2011, pp. 1-15.Applicant
- U.S. Appl. No. 11/296,906, filed Dec. 8, 2005, File History.Applicant
- U.S. Appl. No. 11/297,669, filed Dec. 8, 2005, File History.Applicant
- U.S. Appl. No. 11/297,889, filed Dec. 8, 2005, File History.Applicant
- U.S. Appl. No. 11/298,069, filed Dec. 9, 2005, File History.Applicant
- U.S. Appl. No. 11/299,028, filed Dec. 9, 2005, File History.Applicant
- U.S. Appl. No. 11/593,659, filed Nov. 7, 2006, File History.Applicant
- U.S. Appl. No. 11/593,682, filed Nov. 7, 2006, File History.Applicant
- U.S. Appl. No. 11/593,882, filed Nov. 7, 2006, File History.Applicant
- U.S. Appl. No. 11/595,015, filed Nov. 9, 2006, File History.Applicant
- U.S. Appl. No. 11/637,754, filed Dec. 13, 2006, File History.Applicant
- U.S. Appl. No. 11/637,755, filed Dec. 13, 2006, File History.Applicant
- Bill, ‘DriveCam—FAQ’, Dec. 12, 2003.Applicant
- Bill Siuru, ‘DriveCam Could Save You Big Bucks’, Land Line Magazine, May-Jun. 2000.Applicant
- Chris Woodyard, ‘Shuttles save with DriveCam’, Dec. 9, 2003.Applicant
- Dan Carr, Flash Video Template: Video Presentation with Navigation, Jan. 16, 2006, http://www.adobe.com/devnet/fiash/articles/vidtemplate—mediapreso—flash8.html.Applicant
- David Cullen, ‘Getting a real eyeful’, Fleet Owner Magazine, Feb. 2002.Applicant
- David Maher, ‘DriveCam Brochure Folder’, Jun. 6, 2005.Applicant
- David Maher, “DriveCam Brochure Folder”, Jun. 8, 2005.Applicant
- David Vogeleer et al., Macromedia Flash Professional 8Unleashed (Sams Oct. 12, 2005).Applicant
- Del Lisk, ‘DriveCam Training Handout Ver4’, Feb. 3, 2005.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit A, U.S. Patent 6,389,340, Document 34.1, Oct. 20, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Patent 7,659,827. Aug. 19, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Patent 7,804,426, Document 34.2, Oct. 20, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Patent 7,659,827, Document 34.3, Oct. 20, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Patent 7,804,426. Aug. 19, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit D, Document 34.4, Oct. 20, 2011.Applicant
- DriveCam—Illuminator Data Sheet, Oct. 2, 2004.Applicant
- Drivecam.com as retrieved by the Internet Wayback Machine as of Mar. 5, 2005.Applicant
- DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Aug. 19, 2011.Applicant
- DriveCam Driving Feedback System, Mar. 15, 2004.Applicant
- DriveCam Extrinsic Evidence with Patent LR 4.1 .a Disclosures, Nov. 3, 2011.Applicant
- DriveCam Extrinsic Evidence with Patent LR 4.1 .a Disclosures, Nov. 8, 2011.Applicant
- Driver Feedback System, Jun. 12, 2001.Applicant
- First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 53, filed Dec. 20, 2011, pp. 1-48.Applicant
- First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 55, filed Jan. 1, 2012. pp. 86-103.Applicant
- First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 55, filed Jan. 3, 2012. pp. 86-103.Applicant
- 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.Applicant
- Franke, U., et al., Autonomous Driving Goes Downtown, IEEE Intelligent Systems, 13(6):40-48 (1988); Digital Object Identifier 10.1109/5254.736001.Applicant
- 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.Applicant
- 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.Applicant
- Gary and Sophia Rayner, Final Report for Innovations Deserving Exploratory Analysis (IDEA) Intelligent Transportation Systems (ITS) Programs' Project 84, I-Witness Black Box Recorder, San Diego, CA. Nov. 2001.Applicant
- GE published its VCR User's Guide for Model VG4255 in 1995.Applicant
- Glenn Oster, ‘Hindsight 20/20 v4.0 Software Installation’, 1 of 2, Jun. 20, 2003.Applicant
- Glenn Oster, ‘HindSight 20/20 v4.0 Software Installation’, 2 of 2, Jun. 20, 2003.Applicant
- Glenn Oster, ‘Illuminator Installation’, Oct. 3, 2004.Applicant
- Hans Fantel, Video; Search Methods Make a Difference in Picking VCR's, NY Times, Aug. 13, 1989.Applicant
- I/O Port Racing Supplies' website discloses using Traqmate's Data Acquisition with Video Overlay system in conjunction with professional driver coaching sessions (available at http://www.ioportracing.com/Merchant2/merchant.mvc?Screen=CTGY&Categorys- ub—Code=coaching)., printed from site on Jan. 11, 2012.Applicant
- Interior Camera Data Sheet, Oct. 26, 2001.Applicant
- International Search Report and Written Opinion issued in PCT/US07/68325 on Feb. 27, 2008.Applicant
- International Search Report and Written Opinion issued in PCT/US07/68328 on Oct. 15, 2007.Applicant
- International Search Report and Written Opinion issued in PCT/US07/68329 on Mar. 3, 2008.Applicant
- International Search Report and Written Opinion issued in PCT/US07/68332 on Mar. 3, 2008.Applicant
- International Search Report and Written Opinion issued in PCT/US07/68334 on Mar. 5, 2008.Applicant
- International Search Report for PCT/US2006/47055, Mailed Mar. 20, 2008 (2 pages).Applicant
- International Search Report issued in PCT/US2006/47042 mailed Feb. 25, 2008.Applicant
- J. Gallagher, ‘Lancer Recommends Tech Tool’, Insurance and Technology Magazine, Feb. 2002.Applicant
- Jean (DriveCam vendor), ‘DC Data Sheet’, Nov. 6, 2002.Applicant
- Jean (DriveCam vendor), ‘DriveCam brochure’, Nov. 6, 2002.Applicant
- Jean (DriveCam vendor), ‘Feedback Data Sheet’, Nov. 6, 2002.Applicant
- Jean (DriveCam vendor), ‘Hindsight 20-20 Data Sheet’, Nov. 4, 2002.Applicant
- Jessyca Wallace, ‘Analyzing and Processing DriveCam Recorded Events’, Oct. 6, 2003.Applicant
- Jessyca Wallace, ‘Overview of the DriveCam Program’, Dec. 15, 2005.Applicant
- Jessyca Wallace, ‘The DriveCam Driver Feedback System’, Apr. 6, 2004.Applicant
- Joint Claim Construction Chart, U.S. Patent No. 6,389,340, ‘Vehicle Data Recorder’ for Case No. 3:11-CV-00997-H-RBB, Document 43-1, filed Dec. 1, 2011, pp. 1-33.Applicant
- Joint Claim Construction Chart in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 11-CV-0997-H (RBB), for the Southern District of California, Document 43, filed Dec. 1, 2011, pp. 1-2.Applicant
- Joint Claim Construction Worksheet, U.S. Patent No. 6,389,340, ‘Vehicle Data Reporter’ for Case No. 3:11-CV-00997-H-RBB, Document 44-1, filed Dec. 1, 2011, pp. 1-10.Applicant
- Joint Claim Construction Worksheet, U.S. Patent No. 6,389,340, “Vehicle Data Reporter” for Case No. 3:11-CV-00997-H-RBB, Document 44-1, filed Dec. 1, 2011, pp. 1-10.Applicant
- Joint Claim Construction Worksheet in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 44, filed Dec. 1, 2011, pp. 1-2.Applicant
- Joint 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.Applicant
- Julie Stevens, ‘DriveCam Services’, Nov. 15, 2004.Applicant
- Julie Stevens, ‘Program Support Roll-Out & Monitoring’, Jul. 13, 2004.Applicant
- 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.Applicant
- JVC Company of America, JVC Video Cassette Recorder HR-IP820U Instructions (1996).Applicant
- 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).Applicant
- 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. pp. 853-858; Digital Object Identifier 10.1109/ITSC.2004.1399015.Applicant
- Karen, ‘Downloading Options to HindSight 20120’, Aug. 6, 2002.Applicant
- Karen, ‘Managers Guide to the DriveCam Driving Feedback System’, Jul. 30, 2002.Applicant
- Kathy Latus (Latus Design), ‘Case Study—Cloud 9 Shuttle’, Sep. 23, 2005.Applicant
- Kathy Latus (Latus Design), ‘Case Study—Lloyd Pest Control’, Jul. 19, 2005.Applicant
- Kathy Latus (Latus Design), ‘Case Study—Time Warner Cable’, Sep. 23, 2005.Applicant
- 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 pp. 255-259 Digital Object Identifier 10.1109/SERA.2006.8.Applicant
- Kitchin, Charles. “Understanding accelerometer scale factor and offset adjustments.” Analog Devices (1995).Applicant
- 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.Applicant
- Lisa McKenna, ‘A Fly on the Windshield?’, Pest Control Technology Magazine, Apr. 2003.Applicant
- 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.Applicant
- 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.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/296,907, Mailed Mar. 22, 2007 (17 pages).Applicant
- Non-final Office Action mailed Aug. 27, 2009 during prosecution of U.S. Appl. No. 11/566,424.Applicant
- Non-Final Office Action mailed Nov. 27, 2013 in U.S. Appl. No. 13/957,810, filed Aug. 2, 2013.Applicant
- Panasonic Corporation, Video Cassette Recorder (VCR) Operating Instructions for Models No. PV-V4020/PV-V4520.Applicant
- Passenger Transportation Mode Brochure, May 2, 2005.Applicant
- Patent Abstracts of Japan vol. 007, No. 180 (P-215), Aug. 9, 1983 & JP 58 085110 A (Mitsuhisa Ichikawa), May 21, 1983.Applicant
- Patent Abstracts of Japan vol. 011, No. 292 (E-543), Sep. 19, 1987 & JP 62 091092 A (OK ENG:KK), Apr. 25, 1987.Applicant
- Patent Abstracts of Japan vol. 012, No. 001 (M-656), Jan. 6, 1988 & JP 62 166135 A (Fuji Electric Co Ltd), Jul. 22, 1987.Applicant
- Patent Abstracts of Japan vol. 014, No. 222 (E-0926), May 10, 1990 & JP 02 056197 A (Sanyo Electric Co Ltd), Feb. 26, 1990.Applicant
- Patent Abstracts of Japan vol. 017, No. 039 (E-1311), Jan. 25, 1993 & JP 04 257189 A (Sony Corp), Sep. 11, 1992.Applicant
- Patent Abstracts of Japan vol. 017, No. 521 (E-1435), Sep. 20, 1993 & JP 05 137144 A (Kyocera Corp), Jun. 1, 1993.Applicant
- Patent Abstracts of Japan vol. 1996, No. 09, Sep. 30, 1996 & JP 08 124069 A (Toyota Motor Corp), May 17, 1996.Applicant
- Patent Abstracts of Japan vol. 1997, No. 10, Oct. 31, 1997 & JP 09 163357 A (Nippon Soken Inc), Jun. 20, 1997.Applicant
- Patent Abstracts of Japan vol. 1998, No. 02, Jan. 30, 1998 & JP 09 272399 A (Nippon Soken Inc), Oct. 21, 1997.Applicant
- Patent Abstracts of Japan vol. 1998, No. 8, Jun. 30, 1998 & JP 10 076880 A (Muakami Corp), Mar. 24, 1998.Applicant
- PCT/US2010/022012, Invitation to Pay Additional Fees with Communication of Partial International Search, Jul. 21, 2010.Applicant
- Peter G. Thurlow, Letter (including exhibits) Regarding Patent Owner's Response to Initial Office Action in Ex Parte Reexamination, Mar. 27, 2012.Applicant
- Preliminary Claim Construction and Identification of Extrinsic Evidence of Defendant/Counterclaimant SmartDriveSystems. Inc, in DriveCam, Inc. v. SmartDrive Systems. Inc. . . Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 8, 2011.Applicant
- Quinn Maughan, ‘DriveCam Enterprise Services’, Jan. 5, 2006.Applicant
- Quinn Maughan, ‘DriveCam Managed Services’, Jan. 5, 2006.Applicant
- Quinn Maughan, ‘DriveCam Standard Edition’, Jan. 5, 2006.Applicant
- Quinn Maughan, ‘DriveCam Unit Installation’, Jul. 21, 2005.Applicant
- Quinn Maughan, ‘Enterprise Services’, Apr. 17, 2006.Applicant
- Quinn Maughan, ‘Enterprise Services’, Apr. 7, 2006.Applicant
- Quinn Maughan, ‘Hindsight Installation Guide’, Sep. 29, 2005.Applicant
- Quinn Maughan, ‘Hindsight Users Guide’, Jun. 7, 2005.Applicant
- Ronnie Rittenberry, ‘Eyes on the Road’, Jul. 2004.Applicant
- SmartDrives Systems, Inc's Production, SO14246-S014255, Nov. 16, 2011.Applicant
- Supplement to DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions' in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Oct. 14, 2011.Applicant
- The DriveCam, Nov. 6, 2002.Applicant
- The DriveCam, Nov. 8, 2002.Applicant
- Traqmate GPS Data Acquisition's Traqmate Data Acquisition with Video Overlay system was used to create a video of a driving event on Oct. 2, 2005 (available at http://www.trackvision.net/phpBB2/viewtopic.php?t=51&sid=1184fbbcbe3be5c87ffa0f2ee6e2da76), printed from site on Jan. 11, 2012.Applicant
- U.S. Appl. No. 12/691,639, entitled ‘Driver Risk Assessment System and Method Employing Selectively Automatic Event Scoring’, filed Jan. 21, 2010.Applicant
- U.S. Appl. No. 11/377,167, Final Office Action dated Nov. 8, 2013.Applicant
- U.S. Appl. No. 11/377,157, filed Mar. 16, 2006 entitled, “Vehicle Event Recorder Systems and Networks Having Parallel Communications Links”.Applicant
- U.S. Appl. No. 11/377,167, filed Mar. 16, 2006 entitled, “Vehicle Event Recorder Systems and Networks Having Integrated Cellular Wireless Communications Systems”.Applicant
- USPTO Final Office Action for U.S. Appl. No. 13/957,810, mailed Jun. 27, 2014, 24 pages.Applicant
- USPTO Final Office Action for U.S. Appl. No. 11/297,669, mailed Nov. 7, 2011, 15 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/296,906, mailed Apr. 2, 2009, 7 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/296,906, mailed Nov. 6, 2009, 9 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/299,028, mailed Apr. 24, 2008, 9 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Nov. 19, 2007, 7 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Nov. 25, 2011, 9 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/377,164, mailed Sep. 11, 2008, 8 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/377,167, mailed Jun. 5, 2008, 11 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/800,876, mailed Dec. 1, 2010, 12 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/800,876, mailed Dec. 20, 2011, 8 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 12/096,591, mailed May 20, 2014, 19 pages.Applicant
- USPTO Non-Final Office Action for U.S. Appl. No. 11/297,669, mailed Apr. 28, 2011, 11 pages.Applicant
- 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.Applicant
- 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).Applicant
- 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.Applicant
- Written Opinion issued in PCT/US07/68328 on Oct. 15, 2007.Applicant
- Written Opinion of the International Searching Authority for PCT/US2006/47042. Mailed Feb. 25. 2008 (5 pages).Applicant
- Written Opinion of the International Searching Authority for PCT/US2006/47055, Mailed Mar. 20, 2008 (5 pages).Applicant