US 8,373,567 B2Grant
System and method for identifying non-event profiles
Issue Date:2013-02-12
•27 Claims
•11 Drawing Sheets
Abstract
Valid driving events and non-events are identified, and detailed information is stored for valid events. Valid events are those captured driving events that are essential to testing of a driver's risky behavior. Remaining captured events which are not identified as involving risky behavior are non-events. At least one event capture device captures location, trigger force, images, and other information that collectively comprise an event. An event detector compares the captured event data to previously created non-event profiles and determines whether the captured event is a non-event. An abbreviated record is created for each identified non-event. For valid driving events, detailed driving event records are created. The records are stored at an evaluation server and are accessible to an analysis station for scoring and review.
Metadata
Assignee
- DriveCam, Inc.
Inventor
- Craig Denson
Application Information
Application Number:US 11/467,694
Filing Date:2006-08-28
Priority Date:2006-05-08
Art Unit:2612
Classifications
IPC:
G08B23/00
Patent Drawings (11 sheets)
Description
Related Application
[0001] The present application is a continuation-in-part of U.S. patent application Ser. Nos. 11/382,222 (now U.S. Pat. No. 7,659,827) and 11/382,239 (now abandoned) filed May 8, 2006, and Ser. Nos. 11/382,325 (now pending) and 11/382,328 (now abandoned), filed May 9, 2006, of concurrent ownership, all of which are incorporated herein by reference in their entirety.
Background
[0002] 1. Field of the Invention
[0003] The present invention generally relates to computer assisted capture of driving events and more specifically relates to streamlining the event capture and review process by identifying driving events that are non-events and thus, do not require review or analysis.
[0004] 2. Related Art
[0005] Conventional systems for identifying risky behavior by fleet drivers are usually cumbersome to manage because of the vast amount of information they collect. Those systems provide such an enormous amount of information because they usually collect more information than is actually required.
[0006] In many situations, conventional systems capture more driving information than is necessary. Quite often, event capture devices collect data continuously, and thus, some of the information is captured even though it does not relate to any risky driving behavior at all. For example, the capturing of information may be triggered by an incident that is beyond a driver's control, for example, by a pothole on a road, a railroad crossing, etc., and thus, the collection of the information in such a case is unnecessary.
[0007] Also quite often, the same driving event is captured by several event capture devices, and thus, some of the collected information is redundant. For these and several other reasons, the conventional systems usually provide a massive amount of information to be reviewed. Subsequently, the analysis of all collected data is time consuming because it requires identifying which information pertains to non-events and eliminating that information from further review.
[0008] Accordingly, what is needed is an efficient system and method for event capture and review that addresses the significant problems in the conventional systems described above.
Summary
[0009] Accordingly, a system and method for identifying non-event profiles is provided which determines those driving events that are non-events, stores only a minimal amount of information for non-events and eliminates captured non-events from review and analysis. The non-events are initially identified during operator review. During that review, non-event profiles are created and provided to an event detector for future use in identifying future events matching a previously created non-event profile. For identified non-events, only abbreviated records are created and sent to the evaluation server.
[0010] In one aspect, the system for identifying non-event profiles comprises an event detector, an evaluation server, a non-event profile module and an event record module. The event detector is communicatively coupled with a vehicle and is configured to capture driving events, store them and send them to the evaluation server. The evaluation server is communicatively coupled with the vehicle and is configured to receive, evaluate and store driving events (including non-events). The non-event profile module is configured to determine that a driving event is a non-event by comparing driving event data to non-event profiles for non-events. Finally, the event record module is configured to create an event record for any potentially valid driving event and send the event record from the event detector to the evaluation server.
[0011] In one aspect, the method for identifying non-event profiles comprises receiving a trigger from a sensing system coupled with an event detector and capturing a driving event at the event detector in response to the trigger. The method further comprises determining that the driving event is a non-event at the event detector, creating an abbreviated record for the non-event and sending the abbreviated record to an evaluation server for storage. The abbreviated record for the non-event can comprise an unique identifier, event time information, a GPS location and trigger force range information.
[0012] Other features and advantages of the present invention will become more readily apparent to those of ordinary skill in the art after reviewing the following detailed description and accompanying drawings.
Brief Description of the Drawings
[0013] The details of the present invention, both as to its structure and operation, may be gleaned in part by study of the accompanying drawings, in which like reference numerals refer to like parts, and in which:
[0014] FIG. 1 is a block diagram illustrating an example event detector in control of a plurality of event capture devices deployed in a vehicle according to an embodiment of the present invention;
[0015] FIG. 2 is a block diagram illustrating an example event detector according to an embodiment of the present invention;
[0016] FIG. 3 is a block diagram illustrating an example captured event according to an embodiment of the present invention;
[0017] FIG. 4A is a block diagram illustrating an example driving-event record according to an embodiment of the present invention;
[0018] FIG. 4B is a block diagram illustrating an example non-event profile according to an embodiment of the present invention;
[0019] FIG. 4C is a block diagram illustrating an example abbreviated record according to an embodiment of the present invention;
[0020] FIG. 4D is a block diagram illustrating an example avoidance record according to an embodiment of the present invention;
[0021] FIG. 5 is a network diagram illustrating an example system for identifying non-event profiles according to an embodiment of the present invention;
[0022] FIG. 6A is a block diagram illustrating an example control module according to an embodiment of the present invention;
[0023] FIG. 6B is a block diagram illustrating an example analysis module according to an embodiment of the present invention;
[0024] FIG. 6C is a block diagram illustrating an example data storage module according to an embodiment of the present invention;
[0025] FIG. 7 is a block diagram illustrating an example event detector and an example evaluation server processing events according to an embodiment of the present invention;
[0026] FIG. 8 is a flow diagram illustrating an example process for the detection of non-events by an event detector according to an embodiment of the present invention;
[0027] FIG. 9A is a flow diagram illustrating an example process for the identification and processing of abbreviated records by an evaluation server according to an embodiment of the present invention;
[0028] FIG. 9B is a flow diagram illustrating an example process for the identification and processing of driving event records by an evaluation server according to an embodiment of the present invention;
[0029] FIG. 10 is a block diagram illustrating an exemplary wireless communication device that may be used in connection with the various embodiments described herein; and
[0030] FIG. 11 is a block diagram illustrating an exemplary computer system as may be used in connection with various embodiments described herein.
Detailed Description
[0031] Certain embodiments as disclosed herein provide for systems and methods for identifying non-events, creating non-events profiles, storing only a minimal amount of information for non-events and storing detailed information for valid driving events. Valid events are those captured driving events that are essential to the testing of a driver's risky behavior. A driving event can be identified as a non-event if it involves circumstances not essential to the testing of a driver's risky behavior. For example, a driving event is a non-event if it involves instances beyond a driver's control such as driving over a pothole on the road, a railroad crossing, etc. For identified non-events, only abbreviated records are created and sent to the evaluation server. For all other events, full driving event records including audio, video, and other related information are created and stored for future evaluation and analyzing.
[0032] After reading this description, it will become apparent to one skilled in the art how to implement the invention in various alternative embodiments and alternative applications. However, although various embodiments of the present invention will be described herein, it is understood that these embodiments are presented by way of example only and not limitation. As such, this detailed description of various alternative embodiments should not be construed to limit the scope or breadth of the present invention as set forth in the appended claims.
[0033] FIG. 1 is a block diagram illustrating an example event detector 30 in control of a plurality of event capture devices 20 deployed in a vehicle 10 according to an embodiment of the present invention. In the illustrated embodiment, the event detector 30 is integrated with the vehicle 10 and is communicatively coupled with the event capture devices 20. The event detector 30 is also configured with data storage 35.
[0034] The event detector 30 can be any of a variety of types of computing devices with the ability to execute programmed instructions, receive input from various sensors, and communicate with one or more internal or external event capture devices 20 and other external devices (not shown). An example general purpose computing device that may be employed as all or a portion of the event detector 30 is later described with respect to FIG. 11 . An example general purpose wireless communication device that may be employed as all or a portion of an event detector 30 is later described with respect to FIG. 10 .
[0035] When the event detector 30 identifies a driving event particularly of interest for driving analysis purposes, the event detector 30 instructs one or more event capture devices 20 to send “pre-event” data, “during-the-event” data, and “post-event” data to the event detector 30 to be stored in the data storage area 35. Events may comprise a variety of situations, including automobile accidents, reckless driving, rough driving, or any other type of stationary or moving occurrence that the owner of a vehicle 10 may desire to know about.
[0036] The vehicle 10 may have a plurality of event capture devices placed in various locations around the vehicle 10. An event capture device 20 may comprise a video camera, still camera, microphone, and other types of data capture devices. For example, the event capture device 20 may include an accelerometer that senses changes in speed or direction. Additional sensors and/or data capture devices may also be incorporated into the event capture device 20 in order to provide a rich set of information about a detected event.
[0037] The data storage area 35 can be any sort of internal or external, fixed or removable memory device and may include both persistent and volatile memories. The function of the data storage area 35 is to maintain data for long-term storage and also to provide efficient and fast access to instructions for applications or modules that are executed by the event capture device 20.
[0038] In one embodiment, the event detector 30 in combination with one or more event capture devices 20 identifies an event and stores certain audio and video data along with related information about the event. For example, related information may include the speed of the vehicle when the event occurred, the direction the vehicle was traveling, the location of the vehicle (e.g., from a global positioning system (“GPS”) sensor), G-force data and other information from sensors located in and around the vehicle or from the vehicle itself (e.g., from a data bus integral to the vehicle such as a J-1850 vehicle bus). This combination of audio, video, and other data is compiled into an event that can be stored in the data storage 35 on board the vehicle for later delivery to an evaluation server.
[0039] FIG. 2 is a block diagram illustrating an example event detector 30 according to an embodiment of the present invention. In the illustrated embodiment, the event detector 30 comprises an audio/video (“AV”) module 100, a sensor module 110, a communication module 120, and a control module 130. Additional modules may also be employed to carry out the various functions of the event detector 30, as will be understood by those having skill in the art.
[0040] The AV module 100 is configured to manage the audio and video input from one or more event capture devices and storage of the audio and video input. The sensor module 110 is configured to manage one or more sensors that can be integral to the event detector 30 or external from the event detector 30. For example, an accelerometer may be integral to the event detector 30 or it may be located elsewhere in the vehicle. The sensor module 110 may also manage other types of sensor devices such as a GPS sensor, temperature sensor, moisture sensor, or the like (all not shown).
[0041] The communication module 120 is configured to manage communications between the event detector 30 and other devices and modules. For example, the communication module 120 may handle communications between the event detector 30 and the various event capture devices. The communication module 120 may also handle communications between the event detector 30 and a memory device, a docking station, or a server such as an evaluation server. The communication module 120 is configured to communicate with these various types of devices and other types of devices via a direct wire link (e.g., USB cable, firewire cable), a direct wireless link (e.g., infrared, Bluetooth), or a wired or wireless network link such as a local area network (“LAN”), a wide area network (“WAN”), a wireless wide area network (“WWAN”), or an IEEE 802 wireless network such as an IEEE 802.16 (“WiFi”) network.
[0042] The control module 130 is configured to control the actions of remote devices such as event capture devices. For example, the control module 130 may be configured to receive a trigger from the sensor module 110 indicating a valid event and to instruct the event capture devices to send the event data to the event detector.
[0043] FIG. 3 is a block diagram illustrating the basic data structure of an example event 150 according to an embodiment of the present invention. In the illustrated embodiment, the event 150 comprises audio data 160, video data 170, and metadata 180. Audio data 160 can be collected from inside the vehicle and/or outside the vehicle. Audio data 160 may also include information from an internal vehicle bus about the baseline noise level of the operating vehicle, if such information is available. Additional information about baseline noise level, radio noise level, conversation noise level, or external noise level may also be included in audio data 160.
[0044] Video data 170 may include still images or moving video captured by one or more cameras mounted in various locations in and around the vehicle. Video data 170 may include images or video from inside the vehicle, outside the vehicle, or both. In one particularly advantageous embodiment, still images and moving video that illustrate the entire area inside the vehicle and the entire 360 degree area surrounding the vehicle are captured by a plurality of image capture devices and included in video data 170.
[0045] Metadata 180 may include a variety of additional information that is available to the event detector 30 at the time of an event. Such additional data may include the velocity and direction of the vehicle, the GPS location of the vehicle, elevation, time, temperature, and vehicle engine and electrical component information captured from an internal vehicle bus, just to name a few. Additional information may also be included such as the number of occupants in the vehicle, whether seatbelts were fastened, whether airbags were deployed, whether evasive maneuvering was attempted as determined by the route of the vehicle prior to the event. As will be understood by those skilled in the art, metadata 180 may include an extremely rich variety of information limited only by the scope and type of information obtained prior to, during, and after an event.
[0046] FIG. 5 is a network diagram illustrating an example system for identifying non-events according to an embodiment of the present invention and for storing different types of event data depending on whether a captured driving event is a valid driving event requiring further evaluation, or a non-event. In this case, a non-event is an event which was out of the driver's control and did not involve any driver error or risky behavior. In the illustrated embodiment, the system includes an event detector 30, an evaluation server 50, and an analysis station 60. The event detector 30, the evaluation server 50 and the analysis station 60 communicate with each other via a network 76, each of them coupled with a data storage area 35, 55, and 65, respectively. Additional event detectors 30, evaluation servers 50, and analysis stations 60 may also be included. It will be understood that the analysis station 60 may be located at the same site as the evaluation server in alternative embodiments, and may be linked to the evaluation server via a local network or the like in that case.
[0047] The function of the event detector 30 is to identify and capture a plurality of events and send data structures representing the audio, video, and other related data (collectively called an “event”) to the evaluation server 50. The evaluation server maintains the captured events and provides them to the analysis station 60 where the events are reviewed. The analysis station 60 may be configured with certain hardware and software modules that allow an operator to review and analyze event data (e.g., audio, video, and metadata), create summary reports and the like.
[0048] In one embodiment, the event detector 30 is configured to create metadata tags and assign them to a variety of points. A metadata tag correlates to a particular moment in time and can be linked to a corresponding portion of a video and/or audio buffer. For example, for a given event, one metadata tag can be assigned to the beginning of the event and another metadata tag can be assigned to the end of the event.
[0049] After an event is reviewed, it may be discarded, flagged for follow up, flagged for inclusion in one or more reports, or otherwise maintained for later reporting or analysis. In one embodiment, certain portions of one or more events may be incorporated into a report and then sent to the evaluation server 50 for storage.
[0050] In one embodiment, an event 150 is captured by an event detector 30 and stored until it is provided to the evaluation server 50. The means by which an event 150 can be provided to the evaluation server 50 can vary. For example, an event 150 may be provided from event detector 30 to the evaluation server 50 by way of a portable media device, a direct wire link, a direct wireless link, an indirect wire link, an indirect wireless link, or any combination of these. Event 150 may be secured by encryption of the event-data structure and/or a secure channel between the event detector 30 and the evaluation server 50.
[0051] For example, a portable media device may include a USB drive, compact disc, thumb drive, media card, or other similar type of device. A direct wire link may include a USB cable, a firewire cable, an RS-232 cable, or the like. A direct wireless link may include an infrared link, a Bluetooth link, or an IEEE 802.11 point-to-point link, just to name a few. An indirect wired link may include a packet switched or circuit switched network connection configured for conveyance of data traffic. An Ethernet network connection is an example of a packet switched indirect wired link and a dial-up modem connection is an example of a circuit switched indirect wired link; both of which may be configured for conveyance of data traffic.
[0052] In the illustrated embodiment, the event 150 travels from the event detector 30 to the evaluation server 50 over the network 76. The network 76 may comprise any of a variety of network types and topologies and any combination of such types and topologies. For example, the network 76 may comprise a plurality of networks including private, public, circuit switched, packet switched, personal area networks (“PAN”), local area networks (“LAN”), wide area networks (“WAN”), metropolitan area networks (“MAN”), or any combination of these. The network 76 may also include that particular combination of networks universally known as the Internet.
[0053] In one embodiment, the event 150 travels to the wireless network 76 by way of an access point (not shown) and then on to the evaluation server 50 via the wireless network 76. The access point may provide access via many different wireless network protocols as will be well understood by those having skill in the art. The wireless network may be a WWAN or a WiFi network.
[0054] The link between the event detector 30 and the access point may be a short range direct link or a wide range direct link. The access point may be a large radio tower device or a small in-home wireless appliance. The wireless network 76 may include over the air segments and also wired segments. For example, the last mile segments of wireless network may be over the air, while internal and back end segments may be wired segments. In one embodiment, the wireless network 76 may provide a wireless interface to the event detector 30 and then have a wired interface on the back end to the Internet, which in turn connects to the evaluation server 50.
[0055] In one embodiment, an event 150 may be provided from the event detector 30 to a docking station (not shown), then to the network 76, and then to the evaluation server 50. Providing the event 150 from the event detector 30 to the docking station can be accomplished via a variety of means as described above, including portable media, direct wired or wireless link, and indirect wired or wireless link. The event detector 30 may also be physically coupled with the docking station to convey the event 150 from the event detector 30 to the docking station. Once the event 150 is received by the docking station, the event 150 is sent over the network 76 to the evaluation server 50.
[0056] The network 76 may be a wired or wireless or a combination of the two. The network 76 may also be private or public in whole or in part and may also include the Internet.
[0057] In one embodiment, the evaluation server 50 is configured to save the event data in a data buffer, create groups of events, and concatenate data from a number of data buffers.
[0058] In one embodiment, a group of events 152 traveling from the evaluation server 50 can be routed to the analysis station 60. The means by which the group of events 152 can be provided to the analysis station 60 can vary. In various embodiments (or in a single embodiment), the group of events 152 can be provided by the evaluation server 50 to the analysis station 60 via the network 76.
[0059] The group of events 152 may be identified, for example, by searching for all events that pertain to a particular driver. This may be accomplished by associating each event at the time it is captured with a particular driver. For example, the driver of a vehicle may have a unique identifier and that unique identifier may be included as part of the metadata for each event that is captured while that driver is operating the vehicle.
[0060] Groups of events 152 may also be identified by all events associated with a particular company, a particular shift, a particular supervisor, or other reporting structure or working structure combinations. Such a group of events 152, once provided to the analysis station 60, can then be analyzed by an operator who reviews each event and identifies those events that need to be reported or shown to the driver.
[0061] FIG. 4A is a block diagram illustrating an example of the data structure of a driving event record 300 according to an embodiment of the present invention. In the illustrated embodiment, the driving event record 300 is created by an event detector 30 when the event detector receives a new event captured by one or more event capture devices which is identified as a potentially valid driving event. Valid events are those captured driving events that are essential to the testing of a driver's risky behavior. If the event is potentially a valid driving event, the event detector stores a substantial amount of information about the event in the driving event record 300, and sends the driving event record to the evaluation server 50 for further review and data analysis. The driving event record 300 may comprise several types of information, including, but not limited to, time and GPS location data 740, speed data 742, trigger force range data 744, video data 746, audio data 748, etc.
[0062] FIG. 4B is a block diagram illustrating an example of the data structure of a non-event profile 310 according to an embodiment of the present invention. In the illustrated embodiment, the non-event profile 310 is created at the evaluation server 50 after an operator has identified a driving event as a non-event based on the contents of the driving event record, as described in more detail below in connection with FIGS. 7 and 9B . The non-event profiles are stored on the evaluation server and copies of non-event profiles are sent to the event detectors in the field. A typical non-event profile 310 contains less data than the driving event record 300. The non-event profile should contain just enough information to identify the non-event if it recurs. For example, a non-event profile 710 can comprise a unique identifier 743 created by the evaluation server for that particular non-event, time and GPS location information 740, speed information 742, and trigger force range information 744. In an alternative embodiment, time and/or speed information may be excluded from the non-event profile 710. The unique identifier 743 is used by the event detector to identify and refer to the appropriate non-event profile. After the unique identifier is created for the non-event profile, the evaluation server also creates an occurrence counter. The occurrence counter is used to keep track of future occurrences of non-events having the same non-event profile, as will be described in more detail below.
[0063] FIG. 4C is a block diagram illustrating an example of the data structure of an abbreviated record 320 according to an embodiment of the present invention. In the illustrated embodiment, the abbreviated records 320 are created by event detectors and sent to the evaluation server. If a captured event has a corresponding non-event profile, very little information about the event needs to be stored. In fact, the amount of information stored in the abbreviated record 320 can be even smaller than in the corresponding non-event profile 310. A typical abbreviated record 320 may comprise a unique identifier 743, time and GPS location information 740, and trigger force range information 744, although even less information than this may be required in other embodiments. The unique identifier assigned to the abbreviated record is the same as the unique identifier assigned to the corresponding non-event profile. The unique identifier 743 is used to identify and refer to the appropriate non-event profile.
[0064] FIG. 4D is a block diagram illustrating an example of the data structure of an avoidance record 330 according to an embodiment of the present invention. In the illustrated embodiment, the avoidance record 330 is created at an evaluation server when the evaluation server receives an abbreviated record for a particular identified non-event a specified number of times. If an event has a corresponding non-event profile and it has been captured a specified number of times, the evaluation server determines that the event which has that non-event profile should be avoided by drivers in the future. To facilitate that, the avoidance record 330 is created.
[0065] The avoidance records 330 are stored on the evaluation server. The amount of information stored in the avoidance record 330 can be even smaller than in the corresponding abbreviated record 320. A typical avoidance record 330 comprises a unique identifier 743, GPS location information 741, and trigger force range information 744. The unique identifier 743 is used to identify and refer to the appropriate non-event profile.
[0066] Operation of the event detector and evaluation server in identifying and handling non-events will now be described in more detail with reference to FIGS. 6 to 9 . In the illustrated embodiment, captured events are provided to the event detector in response to detection of a trigger, which may be a force above a certain threshold, for example. Other triggers may be used to trigger transmission of captured events to the event detector in alternative embodiments. The event detector compares received events 150 to previously stored non-event profiles, creates a full driving event record 300 (FIG. 4A ) if the event data does not match any stored non-event profile, and creates an abbreviated record 320 (FIG. 4C ) if the event data matches a stored non-event profile. The evaluation server or analysis station receives driving event records and abbreviated records from the event detector, and determines whether the driving event records match the criteria for a valid driving event. If not, a new non-event profile 310 (FIG. 4B ) is created and sent to all event detectors 30. If the same identified non-event occurs more than a predetermined number of times, avoidance record 330 is created. The accumulated group of avoidance records 330 could optionally be sold to a third party.
[0067] FIG. 6A is a block diagram illustrating an example control module 130 residing in the event detector according to an embodiment of the present invention. In the illustrated embodiment, the control module 130 comprises an event record creating module 134, a non-event profile module 136 and an abbreviated record module 138. The non-event profile module 136 is configured to compare captured event data with previously stored non-event profiles. Non-event profiles are created by the evaluation server for those events that are irrelevant to the analysis of driving behavior and thus, require storing only a minimal amount information, and are stored by the event detectors for later comparison purposes. It will be understood that the evaluation server may alternatively be responsible for comparing captured event data with previously identified non-event profiles, and for creating abbreviated records 320 if appropriate.
[0068] Storage of unnecessary and/or redundant information may be expensive. But, even if the cost of data storage is not an issue, the processing of data containing both relevant and irrelevant information may be time consuming. To save data storage space and shorten data processing time, detailed information about the event is stored only if the event is a valid driving event. Driving events that are actually non-events require storing only a minimal amount of information. If a captured event may be a valid driving event, a full detailed event record is created, whereas for an identified non-event only some information about the event is saved.
[0069] In one embodiment, when the event detector receives captured event data, it identifies some information about the event, such as GPS location information of the vehicle at the time of the event, speed information, trigger signal information, and the like. The non-event profile module 136 then compares that information to the information saved in non-event profiles stored at data storage 35. If the received event data matches information saved in any of the non-event profiles, the received event may be categorized as a non-event.
[0070] If the non-event profile module 136 determines that the received event matches a previously stored non-event profile, the abbreviated record module 138 creates an abbreviated record 320 (FIG. 4C ) for that non-event and sends the abbreviated record to the evaluation server. But, if the non-event profile module 136 determines that the received event does not match any previously stored non-event profiles, and is therefore potentially a valid driving event, the event record creating module 134 creates a full driving event record 300 (FIG. 4A ) for that event and sends it to the evaluation server.
[0071] FIG. 6B is a block diagram illustrating an example analysis module 260 at an evaluation server according to an embodiment of the present invention. In the illustrated embodiment, the analysis module 260 comprises a non-event identification module 264, an abbreviated record module 266, an avoidance record module 268 and a plot generating module 269. The analysis module 260 is configured to identify non-events and to create a variety of records, including non-event profiles and avoidance records.
[0072] The main function of the non-event identification module 264 is to identify non-events and to create non-event profiles 310 for non-events. An event may be identified as a non-event if the event data are irrelevant to the analysis of driving behavior. For example, an event may be a non-event if the event was related to the driving over a physical obstacle at a known location, such as driving over a pothole, a railroad crossing, etc., and the analysis does not focus on the driving over those obstacles. A non-event may be identified by checking if the event data contains a negative trigger force value along the “Z” axis. Such an event may represent a situation where the vehicle suddenly hit a pothole or ran over a railroad crossing.
[0073] In one embodiment, an operator identifies which events are non-events, flags those events as non-events and initiates the creating of non-event profiles with a unique identifier 743 associated with each non-event profile so that the later occurrence of the same set of data can be associated with the same unique identifier in a corresponding abbreviated record. The non-event identification module 264 creates non-event profiles for non-events, stores one copy of the non-event profiles in data storage 55 at the evaluation server and sends other copies of the non-event profiles to all event detectors in the system, or to those operating in an area which covers the location of the identified non-event.
[0074] An abbreviated record module 266 receives abbreviated records 320 for non events from event detectors, and maintains a non-event occurrence-counter associated with each non-event profile. Once the abbreviated record is received at the evaluation server, the abbreviated record module 266 advances a non-event occurrence-counter for the unique identifier associated with the abbreviated record, and determines whether that specific abbreviated record has been received at the evaluation server more than a predetermined number of times. If, so, the abbreviated record module 266 sends a signal to the avoidance record module 268.
[0075] In one embodiment, the main function of the avoidance record module 268 is to create avoidance records 330 (FIG. 4D ) for non-events. If a non-event was repeated certain number of times, the avoidance record module 268 creates an avoidance record 330 for that non-event and sends the avoidance record to event detectors.
[0076] The avoidance record module 268 can be invoked if a given non-event has been identified more than a predetermined number of times. An avoidance record is usually very short and contains a minimum amount of information about the non-event.
[0077] In one embodiment, the plot generating module 269 receives requests from an operator to produce data plots. After receiving the request, the plot generating module 269 analyzes the appropriate event records stored at the evaluation server and creates the requested plots using the data stored at the evaluation server. The plots may contain statistical information about valid-driving events, non-events, abbreviated records, avoidance records, etc. The plots may also represent a special relationship between non-events and a specified driving course or a specified location. Furthermore, the plots may represent statistical information about driving behavior of one driver or a group of drivers. A variety of other plots are also contemplated.
[0078] FIG. 6C is a block diagram illustrating an example evaluation server data storage 55 according to an embodiment of the present invention. In the illustrated embodiment, the data storage 55 comprises databases containing stored driving event records 300, non-event profiles 310, abbreviated records 320 and avoidance records 330.
[0079] FIG. 7 is a block diagram illustrating an example event detector 30 and an example evaluation server 50 processing captured events according to an embodiment of the present invention.
[0080] In one embodiment, potentially valid driving event records 300 are sent from the event detector 30 to the non-event identification module 264 of the evaluation server 50 and then stored at data storage 55 if they are identified as valid events. The non-event identification module 264 can provide driving event records 300 received from event detectors in the field to an operator, who reviews the records and determines whether any of the records should be identified as a non-event. As described above in connection with FIG. 6A , non-events are driving events that are irrelevant to the testing of driving behaviors. Such circumstances may include driving through physical obstacles at known locations such as potholes, railroad crossings, and the like, if driving over those obstacles is irrelevant to the testing.
[0081] If the non-event identification module determines that the received event record corresponds to a valid driving event requiring further study, the record is sent to the driving event records section of the data storage module 55. If the event is identified as a non-event, the operator initiates the creating of a non-event profile 310 for the non-event. A non-event profile 310 contains a smaller amount of information than the driving event record 300, as described above, but it contains just enough information to identify the non-event and flag a recurrence of the non-event in the future. One of the fields in a non-event profile 310 comprises a unique identifier which can be used by the evaluation server 50 to keep track of similar non-events captured in the future. The non-event profiles 310 are stored in the non-event profile section of the data storage module 55 at the evaluation server 50. Copies of non-event profiles 310 are also sent to event detectors and stored in the data storage modules 35 of event detectors in the field.
[0082] The event detectors 30 access non-event profiles in their data storage modules 35 to determine whether a newly captured event is a non-event. When the event detector 30 receives a new event, it passes the new event data to its non-event profile module 136. The non-event profile module 136 compares the new event data (including GPS location information, speed information, trigger signal information, and the like) to the stored non-event profiles 310 to determine if the detected event matches a previously stored non-event profile. If the parameters in the new event data match the parameters in any of the previously stored non-event profiles, the non-event profile module 136 determines that the event is a non-event and thus, needs only an abbreviated record 320. But, if the non-event profile module 136 does not find a “match” among the non-event profiles 310, the event is potentially a valid driving event and a full driving event record 300 is created by module 134 and sent to the evaluation server at the appropriate time.
[0083] In one embodiment, the abbreviated record module 138 creates abbreviated records 320 for non-events. The abbreviated records 320 are created to save system storage space and thus, improve efficiency of the review process. An abbreviated record 320 contains a smaller amount of information than the corresponding driving event record 300, and also contains the same unique identifier 743 as the non-event profile 310 matching the new driving event as identified by the non event profile matching module 136. Once an abbreviated record 320 for the non-event is created, the event detector 30 sends the abbreviated record 320 to the evaluation server 50. In the illustrated embodiment, abbreviated records are stored by the evaluation server 50 in the corresponding section of the data storage module 55, and are also monitored by the abbreviated record module 266.
[0084] In one embodiment, the abbreviated record module 266 residing in the evaluation server 50 monitors the receiving of each abbreviated record 320. The abbreviated record module 266 counts how many times the same non-event has recurred, i.e. it counts the number of times an abbreviated record with the same unique identifier 743 is received. If the non-event recurs a specified number of times, the analysis module 260 invokes the avoidance record module 268. The avoidance record module 268 creates an avoidance record 330 for that non-event, which is stored in the corresponding area of data storage module 55.
[0085] In one embodiment, the plot generating module 269 generates a variety of plots based on the collected driving event data. The plots may contain statistical information about valid driving events, non-events, abbreviated records, avoidance records, and the like. The plots may also represent a special relationship between non-events and a specified driving course or a specified location. Furthermore, the plots may represent statistical information about driving behavior of one driver or a group of drivers. A variety of other plots are also contemplated.
[0086] FIG. 8 is a flow diagram illustrating an example process for the identification and processing of captured events by an event detector according to an embodiment of the present invention. In the illustrated embodiment, the event detector receives an event from one or more event capture devices, determines whether the captured event is potentially a valid-driving event or matches a previously stored non-event profile, and creates appropriate data records.
[0087] At a step 800, the event detector receives new event data from an event capture device (or more than one such device). As described above in connection with FIG. 3 , event capture devices may comprise audio, video and/or metadata sensing devices. Once the event detector receives an event trigger, the event detector selects one or more event capture devices, and passes the trigger to selected event capture devices. In response, each selected event capture device sends captured event data to the event detector.
[0088] At a step 802, the event detector compares the event data received from the event capture devices (e.g., GPS location information, speed information, trigger signal information, etc.) to the previously stored non-event profiles to determine whether the received event is a non-event.
[0089] At a step 804, the event detector checks if the received event corresponds to a previously stored non-event profile. If it does, then the event detector stores only a minimal amount of information for the event, along with the unique identifier 743 of the corresponding non-event profile 310. But, if the received event does not correspond to the data in any previously stored non-event profile, the event is identified as a potentially valid driving event and thus, the event detector stores a full driving event record 300 (FIG. 4A ) for the event (step 812).
[0090] At a step 808, the event detector creates and stores an abbreviated record for any received event corresponding to a non-event profile. Since the received event is a non-event (i.e., the event is not a valid-driving event), there is no need to store full driving event data for it. Thus a shorter, abbreviated record is sufficient for the received non-event. As described above in connection with FIG. 4C , a typical abbreviated record comprises a unique identifier 743 which is the same as the unique identifier of the non-event profile identified as matching that event, time and GPS location information 740, and trigger force range information 744. The unique identifier is used to identify and refer to future occurrences of the same non-event.
[0091] At a step 810, the event detector sends the abbreviated record to the evaluation server where the abbreviated record is stored and used in further data processing.
[0092] At the step 812, the event detector creates a full driving event record 300 for a received event which does not have data matching a previously stored non event profile 310. As described above in connection with FIG. 4A , a typical driving event record 300 comprises detailed information about the event, including time and GPS location data, speed data, trigger force range data, video data, audio data, etc.
[0093] At a step 814, the event detector sends the full driving record 300 to the evaluation server where the driving record is stored and used in further data processing.
[0094] FIG. 9A is a flow diagram illustrating an example process for the identification and processing of abbreviated records by an evaluation server according to an embodiment of the present invention. In the illustrated embodiment, the evaluation server receives abbreviated records for non-events and creates additional data records for the non-event if it is needed.
[0095] At a step 902, the evaluation server receives an abbreviated record from the event detector. As described above in connection with FIG. 8 , the event detector creates abbreviated records for those driving events that correspond to previously identified non-events. Each abbreviated record has a unique identifier which corresponds to the unique identifier included with the non-event profile for the non-event.
[0096] At a step 904, the evaluation server retrieves from its database an occurrence-counter that has the same unique identifier as the unique identifier included in the abbreviated record. The evaluation server maintains an occurrence-counter for each non-event profile. An occurrence-counter is used to keep track of the number of occurrences of non-events that have the same non-event profile. Each time the non-event having a corresponding non-event profile is captured, the occurrence-counter is advanced until it reaches a predefined maximum number of occurrences for the non-event.
[0097] At a step 906, the evaluation server advances the occurrence-counter for the abbreviated record having the same unique identifier as the occurrence-counter.
[0098] At a step 908, the evaluation server checks whether the evaluation server has received more than “N” abbreviated records for a given non-event having the same unique identifier 743. If not, the abbreviated record is stored (step 912). If the non-event occurrence-counter has received more than N occurrences for the same unique non event identifier, the evaluation server determines that this non-event has to be “avoided” in the future.
[0099] At a step 910, the evaluation server has determined that there have been more than “N” abbreviated records for a given non-event. At the step 910, the evaluation server creates and stores an avoidance record 930 containing minimum information about the non-event.
[0100] As described above in connection with FIG. 4D , a typical avoidance record 930 comprises the unique identifier for that non-event, GPS location information, and trigger force range information. The unique identifier assigned to the avoidance record is the same as the unique identifier assigned to the abbreviated record and the corresponding non-event profile. At step 912, the evaluation server stores the received abbreviated record.
[0101] In one embodiment, the evaluation server checks periodically to determine whether an operator has sent information that the non-event had expired (not shown in FIG. 9A ). A non-event expires, for example, when the pothole is repaired, the obstacle on the road is removed, a specified amount of time has passed since a non-event profile was created for the non-event involving given obstacle, or the like. The information about an expired non-event can be entered by an operator who works at the evaluation server. Alternatively, the evaluation server can periodically check the time-stamp information saved in the non-event profiles. Event detectors 30 may also be instructed to remove the corresponding non-event profile from their records.
[0102] If a non-event has expired, collecting further information about the non-event is unnecessary. Thus, in that situation, the evaluation server can remove the appropriate non-event profile, appropriate abbreviated records and all other records related to the expired non-event.
[0103] In one embodiment, the evaluation server checks periodically whether an operator had requested plotting of data (not shown in FIG. 9A ). An operator can send a request during the driving experiment (“on-line processing”) or during data analysis (“off-line post-processing”). As described above in connection with FIG. 6B , the evaluation server in one embodiment includes a plot generating module. The plot generating module analyzes the records stored on the evaluation server and, using that data, creates plots requested by an operator. The plots may contain statistical information about the number of valid-driving events, non-events, abbreviated records for given non-events, number of avoidance records, etc. In addition, the plots may represent a special relationship between non-events identified during a specified driving course or location. The plots may also represent statistical information about driving behavior of one driver, or a group of drivers.
[0104] FIG. 9B is a flow diagram illustrating an example process for the identification and processing of driving event records by an evaluation server according to an embodiment of the present invention. In the illustrated embodiment, the evaluation server receives driving event records for potentially valid driving events and creates additional data records for the event if it is needed.
[0105] At a step 920, the evaluation server receives a full driving event record from the event detector. As described above in connection with FIG. 8 , the event detector creates full driving records for those driving events that are potentially valid driving events (i.e., that are not identical to previously identified non-events). The evaluation server receives the full driving records from the event detector after the event detector receives the data from the selected event capture device or devices.
[0106] At a step 922, the evaluation server determines whether the data corresponds to a valid driving event or may be an actual non-event. As described above in connection with FIG. 8 , non-events are driving events that are connected to events that are irrelevant to the testing of driving behaviors. Examples of such irrelevant events include driving over physical obstacles at known driving locations, such as driving over potholes, railroad crossings, and the like Such irrelevant events do not require storing full driving event records. For such irrelevant events only a minimal amount of information needs to be stored. The operator determines whether the event is a non-event by examining the data associated with the event. If the event is a valid driving event, the driving event record is stored (step 928) and may be used in subsequent analysis of driver behavior.
[0107] If the evaluation server determines that the event was actually a non-event, a non-event profile is created (step 924) and the non-event profile is sent to event detectors in the field (step 926).
[0108] In the embodiment described above, non-events are initially identified by examining event data during operator review at the evaluation server and a non-event profile is created for each non-event and provided to the event detectors for future use, The event detector may identify an event corresponding to a non-event profile by comparison of the GPS information, trigger force, and the like, and create a corresponding abbreviated event record for use in counting the number of times that particular event has occurred. Recurring events may be flagged through cumulative identification, for example by using the occurrence counter as described above. Information on such recurring non-events can be provided to government entities and the like to locate and identify necessary road repairs.
[0109] FIG. 10 is a block diagram illustrating an exemplary wireless communication device 650 that may be used in connection with the various embodiments described herein. For example, the wireless communication device 650 may be used in conjunction with an event detector or an evaluation server previously described with respect to FIG. 5 . However, other wireless communication devices and/or architectures may also be used, as will be clear to those skilled in the art.
[0110] In the illustrated embodiment, wireless communication device 650 comprises an antenna 652, a multiplexor 654, a low noise amplifier (“LNA”) 656, a power amplifier (“PA”) 658, a modulation circuit 660, a baseband processor 662, a speaker 664, a microphone 666, a central processing unit (“CPU”) 668, a data storage area 670, and a hardware interface 672. In the wireless communication device 650, radio frequency (“RF”) signals are transmitted and received by antenna 652. Multiplexor 654 acts as a switch, coupling antenna 652 between the transmit and receive signal paths. In the receive path, received RF signals are coupled from a multiplexor 654 to LNA 656. LNA 656 amplifies the received RF signal and couples the amplified signal to a demodulation portion of the modulation circuit 660.
[0111] Typically, modulation circuit 660 will combine a demodulator and modulator in one integrated circuit (“IC”). The demodulator and modulator can also be separate components. The demodulator strips away the RF carrier signal, leaving a base-band receive audio signal, which is sent from the demodulator output to the base-band processor 662.
[0112] If the base-band receive audio signal contains audio information, then base-band processor 662 decodes the signal and converts it to an analog signal. Then the signal is amplified and sent to the speaker 664. The base-band processor 662 also receives analog audio signals from the microphone 666. These analog audio signals are converted to digital signals and encoded by the base-band processor 662. The base-band processor 662 also codes the digital signals for transmission and generates a base-band transmit audio signal that is routed to the modulator portion of modulation circuit 660. The modulator mixes the base-band transmit audio signal with an RF carrier signal, generating an RF transmit signal that is routed to the power amplifier 658. The power amplifier 658 amplifies the RF transmit signal and routes it to the multiplexor 654 where the signal is switched to the antenna port for transmission by antenna 652.
[0113] The baseband processor 662 is also communicatively coupled with the central processing unit 668. The central processing unit 668 has access to a data storage area 670. The central processing unit 668 is preferably configured to execute instructions (i.e., computer programs or software) that can be stored in the data storage area 670. Computer programs can also be received from the baseband processor 662 and stored in the data storage area 670 or executed upon receipt. Such computer programs, when executed, enable the wireless communication device 650 to perform the various functions of the present invention as previously described.
[0114] In this description, the term “computer readable medium” is used to refer to any media used to provide executable instructions (e.g., software and computer programs) to the wireless communication device 650 for execution by the central processing unit 668. Examples of these media include the data storage area 670, microphone 666 (via the baseband processor 662), antenna 652 (also via the baseband processor 662), and hardware interface 672. These computer readable mediums are means for providing executable code, programming instructions, and software to the wireless communication device 650. The executable code, programming instructions and software, when executed by the central processing unit 668, preferably cause the central processing unit 668 to perform the inventive features and functions previously described herein.
[0115] The central processing unit is also preferably configured to receive notifications from the hardware interface 672 when new devices are detected by the hardware interface. Hardware interface 672 can be a combination electromechanical detector with controlling software that communicates with the CPU 668 and interacts with new devices.
[0116] FIG. 11 is a block diagram illustrating an exemplary computer system 750 that may be used in connection with the various embodiments described herein. For example, the computer system 750 may be used in conjunction with an event detector or an evaluation server previously described with respect to FIG. 5 . However, other computer systems and/or architectures may be used, as will be clear to those skilled in the art.
[0117] The computer system 750 preferably includes one or more processors, such as processor 752. Additional processors may be provided, such as an auxiliary processor to manage input/output, an auxiliary processor to perform floating point mathematical operations, a special-purpose microprocessor having an architecture suitable for fast execution of signal processing algorithms (e.g., digital signal processor), a slave processor subordinate to the main processing system (e.g., back-end processor), an additional microprocessor or controller for dual or multiple processor systems, or a coprocessor. Such auxiliary processors may be discrete processors or may be integrated with the processor 752.
[0118] The processor 752 is preferably connected to a communication bus 754. The communication bus 754 may include a data channel for facilitating information transfer between storage and other peripheral components of the computer system 750. The communication bus 754 further may provide a set of signals used for communication with the processor 752, including a data bus, address bus, and control bus (not shown). The communication bus 754 may comprise any standard or non-standard bus architecture such as, for example, bus architectures compliant with industry standard architecture (“ISA”), extended industry standard architecture (“EISA”), Micro Channel Architecture (“MCA”), peripheral component interconnect (“PCI”) local bus, or standards promulgated by the Institute of Electrical and Electronics Engineers (“IEEE”) including IEEE 488 general-purpose interface bus (“GPIB”), IEEE 696/S-100, and the like.
[0119] Computer system 750 preferably includes a main memory 756 and may also include a secondary memory 758. The main memory 756 provides storage of instructions and data for programs executing on the processor 752. The main memory 756 is typically semiconductor-based memory such as dynamic random access memory (“DRAM”) and/or static random access memory (“SRAM”). Other semiconductor-based memory types include, for example, synchronous dynamic random access memory (“SDRAM”), Rambus dynamic random access memory (“RDRAM”), ferroelectric random access memory (“FRAM”) and the like, including read only memory (“ROM”).
[0120] The secondary memory 758 may optionally include a hard disk drive 760 and/or a removable storage drive 762, for example, a floppy disk drive, a magnetic tape drive, a compact disc (“CD”) drive, a digital versatile disc (“DVD”) drive, etc. The removable storage drive 762 reads from and/or writes to a removable storage medium 764 in a well-known manner. Removable storage medium 764 may be, for example, a floppy disk, magnetic tape, CD, DVD, etc.
[0121] The removable storage medium 764 is preferably a computer readable medium having stored thereon computer executable code (i.e., software) and/or data. The computer software or data stored on the removable storage medium 764 is read into the computer system 750 as electrical communication signals 778.
[0122] In alternative embodiments, secondary memory 758 may include other similar means for allowing computer programs or other data or instructions to be loaded into the computer system 750. Such means may include, for example, an external storage medium 772 and an interface 770. Examples of external storage medium 772 may include an external hard disk drive or an external optical drive and/or external magneto-optical drive.
[0123] Other examples of secondary memory 758 may include semiconductor-based memory such as programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), electrically erasable read-only memory (“EEPROM”), or flash memory (block oriented memory similar to EEPROM). Also included are any other removable storage units 772 and interfaces 770, which allow software and data to be transferred from the removable storage unit 772 to the computer system 750.
[0124] Computer system 750 may also include a communication interface 774. The communication interface 774 allows software and data to be transferred between computer system 750 and external devices (e.g., printers), networks, or information sources. For example, computer software or executable code may be transferred to computer system 750 from a network server via communication interface 774. Examples of communication interface 774 include a modem, a network interface card (“NIC”), a communications port, a PCMCIA slot and card, an infrared interface, and an IEEE 1394 fire-wire, just to name a few.
[0125] Communication interface 774 preferably implements industry promulgated protocol standards, such as Ethernet IEEE 802 standards, Fiber Channel, digital subscriber line (“DSL”), asynchronous digital subscriber line (“ADSL”), frame relay, asynchronous transfer mode (“ATM”), integrated digital services network (“ISDN”), personal communications services (“PCS”), transmission control protocol/Internet protocol (“TCP/IP”), serial line Internet protocol/point to point protocol (“SLIP/PPP”), and so on, but may also implement customized or non-standard interface protocols as well.
[0126] Software and data transferred via communication interface 774 are generally in the form of electrical communication signals 778. These signals 778 are preferably provided to communication interface 774 via a communication channel 776. Communication channel 776 carries signals 778 and can be implemented using a variety of wired or wireless communication means including wire or cable, fiber optics, conventional phone line, cellular phone link, wireless data communication link, radio frequency (RF) link, or infrared link, just to name a few.
[0127] Computer executable code (i.e., computer programs or software) is stored in the main memory 756 and/or the secondary memory 758. Computer programs can also be received via communication interface 774 and stored in the main memory 756 and/or the secondary memory 758. Such computer programs, when executed, enable the computer system 750 to perform the various functions of the present invention as previously described.
[0128] In this description, the term “computer readable medium” is used to refer to any media used to provide computer executable code (e.g., software and computer programs) to the computer system 750. Examples of these media include main memory 756, secondary memory 758 (including hard disk drive 760, removable storage medium 764, and external storage medium 772), and any peripheral device communicatively coupled with communication interface 774 (including a network information server or other network device). These computer readable mediums are means for providing executable code, programming instructions, and software to the computer system 750.
[0129] In an embodiment that is implemented using software, the software may be stored on a computer readable medium and loaded into computer system 750 by way of removable storage drive 762, interface 770, or communication interface 774. In such an embodiment, the software is loaded into the computer system 750 in the form of electrical communication signals 778. The software, when executed by the processor 752, preferably causes the processor 752 to perform the inventive features and functions previously described herein.
[0130] Various embodiments may also be implemented primarily in hardware using, for example, components such as application specific integrated circuits (“ASICs”), or field programmable gate arrays (“FPGAs”). Implementation of a hardware state machine capable of performing the functions described herein will also be apparent to those skilled in the relevant art. Various embodiments may also be implemented using a combination of both hardware and software.
[0131] Furthermore, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and method steps described in connection with the above described figures and the embodiments disclosed herein can often be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled persons can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the invention. In addition, the grouping of functions within a module, block, circuit or step is for ease of description. Specific functions or steps can be moved from one module, block or circuit to another without departing from the invention.
[0132] Moreover, the various illustrative logical blocks, modules, and methods described in connection with the embodiments disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (“DSP”), an ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0133] Additionally, the steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium including a network storage medium. An exemplary storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can also reside in an ASIC.
[0134] The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles described herein can be applied to other embodiments without departing from the spirit or scope of the invention. Thus, it is to be understood that the description and drawings presented herein represent a presently preferred embodiment of the invention and are, therefore, representative of the subject matter which is broadly contemplated by the present invention. It is further understood that the scope of the present invention fully encompasses other embodiments that may become obvious to those skilled in the art and that the scope of the present invention is accordingly limited by nothing other than the appended claims.
Claims
The invention claimed is:
1. A system for identifying non-event profiles, comprising:
an event detector communicatively coupled with a vehicle, configured to capture driving events, store captured driving event data and receive non-event profiles;
at least one event capture device associated with the event detector for capturing the driving events;
a non-event profile module configured to compare non-event profiles with captured driving event data and to determine when a captured driving event is a non-event corresponding to a non-event profile based on the comparison of said captured driving event data to the non-event profiles; and
an event record creating module for creating a driving event record for each captured driving event not identified as a non-event by the non-event profile module.
2. The system of claim 1, further comprising an abbreviated record module configured to create an abbreviated record for captured driving event data identified as a non-event.
3. The system of claim 1, further comprising an evaluation server configured to receive driving event records from the event detector and to identify when a driving event record corresponds to a non-event.
4. The system of claim 3, wherein the evaluation server is further configured to create a non-event profile in response to identification of a non-event, and to send non-event profiles to the event detector.
5. The system of claim 3, wherein the evaluation server identifies the driving event as a non-event when the driving event record indicates a predetermined vertical axis force is in a trigger force range.
6. The system of claim 3, wherein the evaluation server further comprises an abbreviated record module configured to receive abbreviated records from the event detector and to count the number of times an abbreviated record corresponding to each non-event profile is received.
7. The system of claim 6, wherein the evaluation server further comprises an avoidance record module configured to create an avoidance record for a non-event when the number of abbreviated records corresponding to the non-event profile for the identified non-event exceeds a predetermined value.
8. The system of claim 7, wherein the avoidance record comprises at least location information.
9. The system of claim 7, wherein the evaluation server further comprises a plot generating module configured to generate frequency and location plots to indicate driving locations to be avoided, the plots being based on the driving event records, the non-event profiles, the avoidance records and the abbreviated records.
10. The system of claim 7, wherein the evaluation server is further configured to remove the non-event profile, the abbreviated records and the avoidance record for the non-event when the non-event has expired.
11. The system of claim 1, wherein the event capture device comprises a global positioning system unit.
12. The system of claim 1, wherein the event capture device comprises a g-force sensing system for sensing g-forces along perpendicular x, y and z axes, wherein a g-force trigger measured along a vertical axis is a negative trigger.
13. The system of claim 12, wherein the evaluation server is configured to identify a driving event as a non-event if the driving event data includes a negative trigger.
14. The system of claim 1, comprising a plurality of said event capture devices associated with the event detector, the event capture devices comprising at least a timer for capturing event time information, a location sensing unit for capturing location information, a speed detecting unit for capturing speed information, and a video camera for capturing video data.
15. The system of claim 14, wherein the event capture devices further comprise a g-force sensing system for capturing three axis g-force information.
16. A method for identifying non-event profiles, comprising:
capturing driving event data at an event detector;
determining whether captured driving event data corresponds to a non-event, by evaluating the driving event data and determining that there was no driver fault associated with the event to which said captured driving event data is related;
creating a driving event record for any captured driving event data which is not determined to correspond to a non-event;
creating an abbreviated record for any captured driving event data which is determined to be a non-event; and
sending driving event records and abbreviated records from the event detector to an evaluation server.
17. The method of claim 16, wherein creating an abbreviated record for the non-event comprises saving at least location information and information identifying the range of trigger force equating to the non-event.
18. The method of claim 16, wherein creating a driving event record comprises saving at least event time information, speed information, location information, range of trigger force information, and video data for the driving event and storing the information in the driving event record.
19. The method of claim 16, further comprising creating and storing a non-event profile for any detected non-event, wherein the non-event profile comprises at least a unique identifier, location information and range of trigger force information.
20. The method of claim 19, wherein the step of determining whether captured driving event data corresponds to a non-event comprises comparing the captured driving event data to stored non-event profiles and determining whether the captured driving event data corresponds to any stored non-event profile.
21. The method of claim 16, further comprising evaluating driving event records received at the evaluation server and determining if a driving event record is a non-event, creating a non-event profile at the evaluation server for any non-event identified in said driving event records, sending each non-event profile to the event detector, and storing non-event profiles at the event detector, and the step of determining whether captured driving event data corresponds to a non-event comprises determining whether the captured driving event data corresponds to any stored non-event profile.
22. The method of claim 21, wherein determining that driving event data corresponds to a non-event comprises determining whether a trigger force stored in the driving event record corresponds to a vertical trigger force exceeding a predetermined value.
23. The method of claim 21, further comprising associating each abbreviated record with a unique identifier for the corresponding non-event profile, and counting the number of abbreviated records received for each unique identifier.
24. The method of claim 23, further comprising creating an avoidance record for a non-event when the abbreviated record count for the unique identifier associated with the non-event exceeds a predetermined number, wherein the avoidance record comprises location information and trigger force range information.
25. The method of claim 24, further comprising identifying a non-event that has expired; and
removing a non-event profile, an avoidance record and abbreviated records for the expired non-event.
26. The method of claim 24, further comprising generating frequency and location plots from the non-event profiles, the avoidance records and the abbreviated records, wherein the frequency and location plots indicate driving locations to be avoided.
27. The method of claim 24, further comprising selling at least the avoidance records to a third party.
Patent Citations (257)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2943141(A) | 1960-06-01 | Knight | Applicant |
| US3634866(A) | 1972-01-01 | Meyer | Applicant |
| US3781824(A) | 1973-12-01 | Caiati et al. | 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, Jr. et al. | Applicant |
| US4271358(A) | 1981-06-01 | Schwarz | Applicant |
| US4280151(A) | 1981-07-01 | Tsunekawa et al. | Applicant |
| US4281354(A) | 1981-07-01 | Conte | Applicant |
| US4401976(A) | 1983-08-01 | Stadelmayr | Applicant |
| US4409670(A) | 1983-10-01 | Herndon et al. | Applicant |
| US4420773(A) | 1983-12-01 | Toyoda et al. | Applicant |
| US4425097(A) | 1984-01-01 | Owens | Applicant |
| US4456931(A) | 1984-06-01 | Toyoda et al. | Applicant |
| US4489351(A) | 1984-12-01 | d'Alayer de Costemore d'Arc | Applicant |
| US4496995(A) | 1985-01-01 | Colles et al. | Applicant |
| US4500868(A) | 1985-02-01 | Tokitsu et al. | Applicant |
| US4533962(A) | 1985-08-01 | Decker et al. | Applicant |
| US4558379(A) | 1985-12-01 | Hutter et al. | Applicant |
| US4593313(A) | 1986-06-01 | Nagasaki et al. | Applicant |
| US4621335(A) | 1986-11-01 | Bluish et al. | Applicant |
| US4625210(A) | 1986-11-01 | Sagl | Applicant |
| US4630110(A) | 1986-12-01 | Cotton et al. | Applicant |
| US4632348(A) | 1986-12-01 | Keesling et al. | Applicant |
| US4638289(A) | 1987-01-01 | Zottnik | Applicant |
| US4646241(A) | 1987-02-01 | Ratchford et al. | Applicant |
| US4651143(A) | 1987-03-01 | Yamanaka | Applicant |
| US4758888(A) | 1988-07-01 | Lapidot | Applicant |
| US4763745(A) | 1988-08-01 | Eto et al. | Applicant |
| US4785474(A) | 1988-11-01 | Bernstein et al. | Applicant |
| US4789904(A) | 1988-12-01 | Peterson | Applicant |
| US4794566(A) | 1988-12-01 | Richards et al. | Applicant |
| US4804937(A) | 1989-02-01 | Barbiaux et al. | Applicant |
| US4806931(A) | 1989-02-01 | Nelson | Applicant |
| US4814896(A) | 1989-03-01 | Heitzman et al. | 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 |
| US4876597(A) | 1989-10-01 | Roy et al. | Applicant |
| US4883349(A) | 1989-11-01 | Mittelhauser | Applicant |
| US4896855(A) | 1990-01-01 | Furnish | Applicant |
| US4930742(A) | 1990-06-01 | Schofield et al. | Applicant |
| US4936533(A) | 1990-06-01 | Adams et al. | 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 et al. | Applicant |
| US4992943(A) | 1991-02-01 | McCracken | Applicant |
| US5012335(A) | 1991-04-01 | Cohodar | Applicant |
| US5027104(A) | 1991-06-01 | Reid | Applicant |
| US5056056(A) | 1991-10-01 | Gustin | Applicant |
| US5057820(A) | 1991-10-01 | Markson et al. | Applicant |
| US5096287(A) | 1992-03-01 | Kakinami et al. | Applicant |
| US5100095(A) | 1992-03-01 | Haan et al. | Applicant |
| US5111289(A) | 1992-05-01 | Lucas et al. | Applicant |
| US5140434(A) | 1992-08-01 | Van Blessinger et al. | Applicant |
| US5140436(A) | 1992-08-01 | Blessinger | Applicant |
| US5144661(A) | 1992-09-01 | Shamosh et al. | Applicant |
| US5178448(A) | 1993-01-01 | Adams et al. | Applicant |
| US5196938(A) | 1993-03-01 | Blessinger | Applicant |
| US5223844(A) | 1993-06-01 | Mansell et al. | Applicant |
| US5262813(A) | 1993-11-01 | Scharton | Applicant |
| US5308247(A) | 1994-05-01 | Dyrdek | Applicant |
| US5309485(A) | 1994-05-01 | Chao | Applicant |
| US5311197(A) | 1994-05-01 | Sorden et al. | Applicant |
| US5321753(A) | 1994-06-01 | Gritton | Applicant |
| US5327288(A) | 1994-07-01 | Wellington et al. | Applicant |
| US5330149(A) | 1994-07-01 | Haan et al. | Applicant |
| US5343527(A) | 1994-08-01 | Moore | Applicant |
| US5353023(A) | 1994-10-01 | Mitsugi | Applicant |
| US5361326(A) | 1994-11-01 | Aparicio, IV et al. | Applicant |
| US5387926(A) | 1995-02-01 | Bellan | Applicant |
| US5388045(A) | 1995-02-01 | Kamiya et al. | Applicant |
| US5404330(A) | 1995-04-01 | Lee et al. | Applicant |
| US5408330(A) | 1995-04-01 | Squicciarini et al. | Applicant |
| US5422543(A) | 1995-06-01 | Weinberg | Applicant |
| US5430431(A) | 1995-07-01 | Nelson | Applicant |
| US5430432(A) | 1995-07-01 | Camhi et al. | Applicant |
| US5435184(A) | 1995-07-01 | Pineroli et al. | Applicant |
| US5445024(A) | 1995-08-01 | Riley, Jr. et al. | Applicant |
| US5445027(A) | 1995-08-01 | Zorner | Applicant |
| US5446659(A) | 1995-08-01 | Yamawaki | Applicant |
| US5455625(A) | 1995-10-01 | Englander | Applicant |
| US5455716(A) | 1995-10-01 | Suman et al. | Applicant |
| US5465079(A) | 1995-11-01 | Bouchard et al. | Applicant |
| US5473729(A) | 1995-12-01 | Bryant et al. | Applicant |
| US5477141(A) | 1995-12-01 | Nather et al. | Applicant |
| US5495242(A) | 1996-02-01 | Kick et al. | Applicant |
| US5497419(A) | 1996-03-01 | Hill | Applicant |
| US5499182(A) | 1996-03-01 | Ousborne | Applicant |
| US5504482(A) | 1996-04-01 | Schreder | Applicant |
| US5515285(A) | 1996-05-01 | Garrett, Sr. et al. | Applicant |
| US5521633(A) | 1996-05-01 | Nakajima et al. | Applicant |
| US5523811(A) | 1996-06-01 | Wada et al. | Applicant |
| US5526269(A) | 1996-06-01 | Ishibashi et al. | Applicant |
| US5530420(A) | 1996-06-01 | Tsuchiya et al. | 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 et al. | Applicant |
| US5546191(A) | 1996-08-01 | Hibi et al. | Applicant |
| US5546305(A) | 1996-08-01 | Kondo | Applicant |
| US5548273(A) | 1996-08-01 | Nicol et al. | Applicant |
| US5552990(A) | 1996-09-01 | Ihara et al. | Applicant |
| US5559496(A) | 1996-09-01 | Dubats | Applicant |
| US5568211(A) | 1996-10-01 | Bamford | Applicant |
| US5570127(A) | 1996-10-01 | Schmidt | Applicant |
| US5574443(A) | 1996-11-01 | Hsieh | Applicant |
| USD376571(S) | 1996-12-01 | Kokat | Applicant |
| US5581464(A) | 1996-12-01 | Woll et al. | Applicant |
| US5590948(A) | 1997-01-01 | Moreno | Applicant |
| US5596382(A) | 1997-01-01 | Bamford | Applicant |
| US5600775(A) | 1997-02-01 | King et al. | Applicant |
| US5610580(A) | 1997-03-01 | Lai | Applicant |
| US5612686(A) | 1997-03-01 | Takano et al. | Applicant |
| US5631638(A) | 1997-05-01 | Kaspar et al. | Applicant |
| US5638273(A) | 1997-06-01 | Coiner et al. | Applicant |
| US5642106(A) | 1997-06-01 | Hancock et al. | Applicant |
| US5646856(A) | 1997-07-01 | Kaesser | Applicant |
| US5652706(A) | 1997-07-01 | Morimoto et al. | Applicant |
| USRE35590(E) | 1997-08-01 | Bezos et al. | Applicant |
| US5654892(A) | 1997-08-01 | Fujii et al. | Applicant |
| US5659355(A) | 1997-08-01 | Barron et al. | Applicant |
| US5667176(A) | 1997-09-01 | Zamarripa et al. | Applicant |
| US5669698(A) | 1997-09-01 | Veldman et al. | Applicant |
| US5671451(A) | 1997-09-01 | Takahashi et al. | Applicant |
| US5677979(A) | 1997-10-01 | Squicciarini et al. | Applicant |
| US5680117(A) | 1997-10-01 | Arai et al. | Applicant |
| US5680123(A) | 1997-10-01 | Lee | Applicant |
| US5689442(A) | 1997-11-01 | Swanson et al. | 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 et al. | Applicant |
| US5719554(A) | 1998-02-01 | Gagnon | Applicant |
| US5784521(A) | 1998-07-01 | Nakatani et al. | Applicant |
| US5790403(A) | 1998-08-01 | Nakayama | Applicant |
| US5790973(A) | 1998-08-01 | Blaker et al. | Applicant |
| US5793420(A) | 1998-08-01 | Schmidt | Applicant |
| US5794165(A) | 1998-08-01 | Minowa et al. | Applicant |
| US5797134(A) | 1998-08-01 | McMillan et al. | 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 et al. | Applicant |
| US5815093(A) | 1998-09-01 | Kikinis | Applicant |
| US5825412(A) | 1998-10-01 | Hobson et al. | Applicant |
| US5844505(A) | 1998-12-01 | Van Ryzin | Applicant |
| US5896167(A) | 1999-04-01 | Omae et al. | Applicant |
| US5897606(A) | 1999-04-01 | Miura et al. | Applicant |
| US5899956(A) | 1999-05-01 | Chan | Applicant |
| US5901806(A) | 1999-05-01 | Takahashi | Applicant |
| US5914748(A) | 1999-06-01 | Parulski et al. | Applicant |
| US5926210(A) | 1999-07-01 | Hackett et al. | Applicant |
| US5946404(A) | 1999-08-01 | Bakshi et al. | 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 et al. | Applicant |
| US6011492(A) | 2000-01-01 | Garesche | Applicant |
| US6028528(A) | 2000-02-01 | Lorenzetti et al. | Applicant |
| US6037860(A) | 2000-03-01 | Zander et al. | Applicant |
| US6037977(A) | 2000-03-01 | Peterson | Applicant |
| US6064792(A) | 2000-05-01 | Fox et al. | Applicant |
| US6092193(A) | 2000-07-01 | Loomis et al. | Applicant |
| US6122738(A) | 2000-09-01 | Millard | Applicant |
| US6141611(A) | 2000-10-01 | Mackey et al. | Applicant |
| US6144296(A) | 2000-11-01 | Ishida et al. | Applicant |
| US6151065(A) | 2000-11-01 | Steed et al. | Applicant |
| US6163338(A) | 2000-12-01 | Johnson et al. | Applicant |
| US6167186(A) | 2000-12-01 | Kawasaki et al. | Applicant |
| US6181373(B1) | 2001-01-01 | Coles | Applicant |
| US6185490(B1) | 2001-02-01 | Ferguson | Applicant |
| US6211907(B1) | 2001-04-01 | Seaman et al. | Applicant |
| US6218960(B1) | 2001-04-01 | Ishikawa et al. | Applicant |
| US6246933(B1) | 2001-06-01 | Bague | Applicant |
| US6253129(B1) | 2001-06-01 | Jenkins et al. | Applicant |
| US6337622(B1) | 2002-01-01 | Sugano | Applicant |
| US6389340(B1) | 2002-05-01 | Rayner | Applicant |
| US6405112(B1) | 2002-06-01 | Rayner | Applicant |
| US6405132(B1) | 2002-06-01 | Breed et al. | Applicant |
| US6408232(B1) | 2002-06-01 | Cannon et al. | Applicant |
| US6449540(B1) | 2002-09-01 | Rayner | Applicant |
| US6611755(B1) | 2003-08-01 | Coffee et al. | Applicant |
| US6679702(B1) | 2004-01-01 | Rau | Applicant |
| US6714894(B1) | 2004-03-01 | Tobey et al. | Applicant |
| US6718239(B2) | 2004-04-01 | Rayner | Applicant |
| US6895248(B1) | 2005-05-01 | Akyol et al. | Applicant |
| US7100190(B2) | 2006-08-01 | Johnson et al. | Applicant |
| US2001/0005804(A1) | 2001-06-01 | Rayner | Applicant |
| US2002/0035422(A1) | 2002-03-01 | Sasaki | Applicant |
| US2002/0059453(A1) | 2002-05-01 | Eriksson et al. | Applicant |
| US2002/0111725(A1) | 2002-08-01 | Burge | Applicant |
| US2002/0163532(A1) | 2002-11-01 | Thomas et al. | Applicant |
| US2002/0169529(A1) | 2002-11-01 | Kim | Applicant |
| US2003/0080878(A1) | 2003-05-01 | Kirmuss | Applicant |
| US2003/0125854(A1) | 2003-07-01 | Kawasaki et al. | 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 et al. | Applicant |
| US2003/0187704(A1) | 2003-10-01 | Hashiguchi et al. | Applicant |
| US2003/0191568(A1) | 2003-10-01 | Breed | Applicant |
| US2003/0214585(A1) | 2003-11-01 | Bakewell | Applicant |
| US2004/0039503(A1) | 2004-02-01 | Doyle | Applicant |
| US2004/0103010(A1) | 2004-05-01 | Wahlbin et al. | Applicant |
| US2004/0209594(A1) | 2004-10-01 | Naboulsi | Applicant |
| US2005/0021199(A1) | 2005-01-01 | Zimmerman et al. | Applicant |
| US2005/0159964(A1) | 2005-07-01 | Sonnenrein et al. | Applicant |
| US2005/0166258(A1) | 2005-07-01 | Vasilevsky et al. | Applicant |
| US2005/0171692(A1) | 2005-08-01 | Hamblen et al. | Applicant |
| US2005/0185936(A9) | 2005-08-01 | Lao et al. | Applicant |
| US2005/0258942(A1) | 2005-11-01 | Manasseh et al. | Applicant |
| US2006/0007151(A1) | 2006-01-01 | Ram | Applicant |
| US2006/0015233(A1) | 2006-01-01 | Olsen et al. | Applicant |
| US2006/0025897(A1) | 2006-02-01 | Shostak et al. | Applicant |
| US2006/0040239(A1) | 2006-02-01 | Cummins et al. | Applicant |
| US2006/0053038(A1) | 2006-03-01 | Warren et al. | Applicant |
| US2006/0055521(A1) | 2006-03-01 | Blanco et al. | Applicant |
| US2006/0057543(A1) | 2006-03-01 | Roald | 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/0095349(A1) | 2006-05-01 | Morgan et al. | Applicant |
| US2006/0212195(A1) | 2006-09-01 | Veith et al. | Applicant |
| US2006/0242680(A1) | 2006-10-01 | Johnson et al. | Applicant |
| US2007/0001831(A1) | 2007-01-01 | Raz et al. | Applicant |
| US2007/0124332(A1) | 2007-05-01 | Ballesty et al. | Applicant |
| US2007/0135979(A1) | 2007-06-01 | Plante | Examiner |
| US2007/0136078(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0143499(A1) | 2007-06-01 | Chang | Applicant |
| US2007/0150140(A1) | 2007-06-01 | Seymour | Applicant |
| US2007/0241874(A1) | 2007-10-01 | Okpysh et al. | Applicant |
| US2007/0260677(A1) | 2007-11-01 | DeMarco et al. | Applicant |
| EP1355278 | 2003-10-01 | Applicant | |
| GB2268608 | 1994-01-01 | Applicant | |
| JP5-137144 | 1993-06-01 | Applicant | |
| JP5-294188 | 1993-11-01 | Applicant | |
| JP8-124069 | 1996-05-01 | Applicant | |
| JP10-076880 | 1998-03-01 | Applicant | |
| WO88/09023 | 1988-11-01 | Applicant | |
| WO90/05076 | 1990-05-01 | Applicant | |
| WO94/27844 | 1994-12-01 | Applicant | |
| WO96/00957 | 1996-01-01 | Applicant | |
| WO97/01246 | 1997-01-01 | Applicant | |
| WO99/37503 | 1999-07-01 | Applicant | |
| WO99/40545 | 1999-08-01 | Applicant | |
| WO99/62741 | 1999-12-01 | Applicant | |
| WO/07150 | 2000-02-01 | Applicant | |
| WO/48033 | 2000-08-01 | Applicant | |
| WO/77620 | 2000-12-01 | Applicant | |
| WO1/25054 | 2001-04-01 | Applicant |
Non-Patent Literature (92)
- International Search Report and Written Opinion issued in PCT/US07/68325 on Feb. 27, 2008.Applicant
- DRIVECAM, Inc., User's Manual for DRIVECAM Video Systems' Hindsight 20/20 Software Version 4.0 (2003).Applicant
- Gary and Sophia Rayner, Final Report for Innovations Deserving Exploratory Analysis (IDEA) Intelligent Transportation Systems (ITS) Programs' Project 84, I-Witness Black Box Recorder, San Diego, CA. Nov. 2001.Applicant
- Panasonic Corporation, Video Cassette Recorder (VCR) Operating Instructions for Models No. PV-V4020/PV-V4520.Applicant
- JVC Company of America, JVC Video Cassette Recorder HR-IP820U Instructions (1996).Applicant
- Hans Fantel, Video; Search Methods Make a Difference in Picking VCR's, NY Times, Aug. 13, 1989.Applicant
- Dan Carr, Flash Video template: Video Presentation with Navigation, Jan. 16, 2006.Applicant
- I/O Port Racing Supplies' website discloses using Traqmate's Data Acquisition with Video Overlay system in conjunction with professional driver coaching sessions (available at http://www.ioportracing.com/Merchant2/merchant.mvc?Screen=CTGY&Category—Code=coaching)., printed from site on Jan. 11, 2012.Applicant
- GE published its VCR User's Guide for Model VG4255 in 1995.Applicant
- Adaptec published and sold its VideoOh! DVD software USB 2.0 Edition in at least Jan. 24, 2003.Applicant
- Traqmate GPS Data Acquisition's Traqmate Data Acquisition with Video Overlay system was used to create a video of a driving event on Oct. 2, 2005 (available at http://www.trackvision.net/phpBB2/viewtopic.php?t=51&sid=1184fbbcbe3be5c87ffa0f2ee6e2da76), printed from site on Jan. 11, 2012.Applicant
- David Vogeleer et al., Macromedia Flash Professional 8UNLEASHED (Sams Oct. 12, 2005)d in Nov. 2005.Applicant
- Jean (DriveCam vendor), “DriveCam brochure”, Nov. 6, 2002.Applicant
- “The DriveCam”, Nov. 6, 2002.Applicant
- Jean (DriveCam vendor), “DC Data Sheet”, Nov. 6, 2002.Applicant
- “Driver Feedback System”, Jun. 12, 2001.Applicant
- Jean (DriveCam vendor), “Feedback Data Sheet”, Nov. 6, 2002.Applicant
- “Interior Camera Data Sheet”, Oct. 26, 2001.Applicant
- Jean (DriveCam vendor), “HindSight 20-20 Data Sheet”, Nov. 4, 2002.Applicant
- “DriveCam Driving Feedback System”, Mar. 15, 2004.Applicant
- 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
- Julie Stevens, “DriveCam Services”, Nov. 16, 2004.Applicant
- Julie Stevens, “Program Support Roll-Out & Monitoring”, Jul. 13, 2004.Applicant
- Jessyca Wallace, “The DriveCam Driver Feedback System”, Apr. 6, 2004.Applicant
- Karen, “Managers Guide to the DriveCam Driving Feedback System”, Jul. 30, 2002.Applicant
- Jessyca Wallace, “Analyzing and Processing DriveCam Recorded Events”, Oct. 6, 2003.Applicant
- Del Lisk, “DriveCam Training Handout Ver4”, Feb. 3, 2005.Applicant
- Jessyca Wallace, “Overview of the DriveCam Program”, Dec. 15, 2005.Applicant
- “DriveCam—Illuminator Data Sheet”, Oct. 2, 2004.Applicant
- Karen, “Downloading Options to HindSight 20/20”, Aug. 6, 2002.Applicant
- Bill, “DriveCam—FAQ”, Dec. 12, 2003.Applicant
- David Maher, “DriveCam Brochure Folder”, Jun. 6, 2005.Applicant
- “Passanger Transportation Mode Brochure”, May 2, 2005.Applicant
- Quinn Maughan, “DriveCam Unit Installation”, Jul. 21, 2005.Applicant
- Glenn Oster, “Illuminator Installation”, Oct. 3, 2004.Applicant
- Quinn Maughan, “HindSight Installation Guide”, Sep. 29, 2005.Applicant
- Quinn Maughan, “HindSight Users Guide”, Jun. 20, 2005.Applicant
- “World News Tonight”, CBS Television New Program discussing teen drivers using the DriveCam Program and DriveCam Technology, Oct. 10, 2005, On PC formatted CD-R, World News Tonight.wmv, 7.02 MB, Created Jan. 12, 2011.Applicant
- “World News Tonight”, PBS Television New Program discussing teen drivers using the DriveCam Program and DriveCam Technology, Oct. 10, 2005, on PC formatted CD-R, Teens Behind the Wheel.wmv, 236 MB, Created Jan. 12, 2011.Applicant
- Quinn Maughan, “Enterprise Services”, Apr. 17, 2006.Applicant
- Quinn Maughan, “DriveCam Enterprise Services”, Jan. 5, 2006.Applicant
- Quinn Maughan, “DriveCam Managed Services”, Jan. 5, 2006.Applicant
- Quinn Maughan, “DriveCam Standard Edition”, Jan. 5, 2006.Applicant
- Kathy Latus (Latus Design), “Case Study—Time Warner Cable”, Sep. 23, 2005.Applicant
- Kathy Latus (Latus Design), “Case Study—Cloud 9 Shuttle”, Sep. 23, 2005.Applicant
- Kathy Latus (Latus Design), “Case Study—Lloyd Pest Control”, Jul. 19, 2005.Applicant
- Bill Siuru, “DriveCam Could Save You Big Bucks”, Land Line Magazine, May-Jun. 2000.Applicant
- J. Gallagher, “Lancer Recommends Tech Tool”, Insurance and Technology Magazine, Feb. 2002.Applicant
- “Ambulance Companies Use Video Technology to Improve Driving Behavior”, Ambulance Industry Journal, Spring 2003.Applicant
- Lisa McKenna, “A Fly on the Windshield?”, Pest Control Technology Magazine, Apr. 2003.Applicant
- Chris Woodyard, “Shuttles save with DriveCam”, Dec. 9, 2003.Applicant
- David Cullen, “Getting a real eyeful”, Fleet Owner Magazine, Feb. 2002.Applicant
- Ronnie Rittenberry, “Eyes on the Road”, Jul. 2004.Applicant
- U.S. Appl. No. 11/296,906, filed Dec. 8, 2005, File History.Applicant
- U.S. Appl. No. 11/298,069, filed Dec. 9, 2005, File History.Applicant
- U.S. Appl. No. 11/299,028, filed Dec. 9, 2005, File History.Applicant
- U.S. Appl. No. 11/593,659, filed Nov. 7, 2006, File History.Applicant
- U.S. Appl. No. 11/593,682, filed Nov. 7, 2006, File History.Applicant
- U.S. Appl. No. 11/595,015, filed Nov. 9, 2006, File History.Applicant
- U.S. Appl. No. 11/637,754, filed Dec. 13, 2006, File History.Applicant
- U.S. Appl. No. 11/637,755, filed Dec. 13, 2006, File History.Applicant
- U.S. Appl. No. 11/297,669, filed Dec. 8, 2005, File History.Applicant
- “DriveCam, Inc's Disclosure of Proposed Constructions and Extrinsic Evidence Pursuant to Patent L.R. 4.1.a & 4.1.b” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Nov. 8, 2011.Applicant
- “Preliminary Claim Construction and Identification of Extrinsic Evidence of Defendant/Counterclaimant SmartDriveSystems, Inc.” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 8, 2011.Applicant
- “DriveCam, Inc's Disclosure of Responsive Constructions and Extrinsic Evidence Pursuant to Patent L.R. 4.1.c & 4.1d” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Nov. 15, 2011.Applicant
- “Responsive Claim Construction and Identification of Extrinsic Evidence of Defendant/Counterclaimant SmartDrive Systems, Inc.” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H (RBB), for the Southern District of California. Nov. 15, 2011.Applicant
- “Joint Claim Construction Chart” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 11-CV-0997-H (RBB), for the Southern District of California, Document 43, filed Dec. 1, 2011, pp. 1-2.Applicant
- Joint Claim Construction Chart, U.S. Patent No. 6,389,340, “Vehicle Data Recorder” for Case No. 3:11-CV-00997-H-RBB, Document 43-1, filed Dec. 1, 2011, pp. 1-33.Applicant
- “Joint Claim Construction Worksheet” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 44, filed Dec. 1, 2011, pp. 1-2.Applicant
- Joint Claim Construction Worksheet, U.S. Patent No. 6,389,340, “Vehicle Data Reporter” for Case No. 3:11-CV-00997-H-RBB, Document 44-1, filed Dec. 1, 2011, pp. 1-10.Applicant
- “Answer to Amended Complaint; Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 47, filed Dec. 13, 2011, pp. 1-15.Applicant
- “First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 53, filed Dec. 20, 2011, pp. 1-48.Applicant
- “First Amended Answer to Amended Complaint and First Amended Counterclaims; and Demand for Jury Trial” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997 H (RBB), for the Southern District of California, Document 55, filed Jan. 1, 2012, pp. 86-103.Applicant
- DriveCam, User's Manual for DriveCam Video Systems', HindSight 20/20 Software Version 4.0, S002751-S002804 (2003).Applicant
- SmartDrives Systems, Inc.'s Production, S014246-S014255, Nov. 16, 2011.Applicant
- “HindSight v4.0 Users Guide”, DriveCam Video Systems, Apr. 25, 2005.Applicant
- “Supplement to DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Oct. 14, 2011.Applicant
- “DriveCam's Disclosure of Asserted Claims and Preliminary Infringement Contentions” in DriveCam, Inc. v. SmartDrive Systems, Inc., Case No. 3:11-CV-00997-H-RBB, for the Southern District of California. Aug. 19, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit A, U.S. Patent 6,389,340. Aug. 11, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit B, U.S. Patent 7,659,827. Aug. 19, 2011.Applicant
- DriveCam, Inc.'s Infringement Contentions Exhibit C, U.S. Patent 7,804,426. Aug. 19, 2011.Applicant
- DriveCam Extrinsic Evidence with Patent LR 4.1.a Disclosures, Nov. 8, 2011.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
- Panasonic Corporation, Video Cassette Recorder (VCR) Operating Instructions for Models No. PV-V4020/PV-V4520 (1998) (Exhibit 8) (hereinafter “Panasonic”).Applicant
- Drivecam.com as retrieved by the Internet Wayback Machine as of Mar. 5, 2005.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/68333 on Mar. 5, 2008.Applicant
- International Search Report and Written Opinion issued in PCT/US07/68334 on Mar. 5, 2008.Applicant
- International Search Report issued in PCT/US07/68328 on Oct. 15, 2007.Applicant
- 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