WO2007133992A2 - System and method for reducing driving risk with hindsight - Google Patents

System and method for reducing driving risk with hindsight Download PDF

Info

Publication number
WO2007133992A2
WO2007133992A2 PCT/US2007/068332 US2007068332W WO2007133992A2 WO 2007133992 A2 WO2007133992 A2 WO 2007133992A2 US 2007068332 W US2007068332 W US 2007068332W WO 2007133992 A2 WO2007133992 A2 WO 2007133992A2
Authority
WO
WIPO (PCT)
Prior art keywords
event
vehicle
data
evaluation server
vehicle accident
Prior art date
Application number
PCT/US2007/068332
Other languages
French (fr)
Other versions
WO2007133992A3 (en
Inventor
Charlie Gunderson
Tom Lafleur
Doron Lurie
Bruce Moeller
Original Assignee
Drivecam, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Drivecam, Inc. filed Critical Drivecam, Inc.
Publication of WO2007133992A2 publication Critical patent/WO2007133992A2/en
Publication of WO2007133992A3 publication Critical patent/WO2007133992A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/085Registering performance data using electronic data carriers
    • G07C5/0858Registering performance data using electronic data carriers wherein the data carrier is removable
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/0875Registering performance data using magnetic data carriers
    • G07C5/0891Video recorder in combination with video camera

Definitions

  • the present invention generally relates to computer assisted forensic analysis of vehicle accidents and more specifically relates to event based reconstruction and review of vehicle accidents to facilitate forensic analysis.
  • the present invention provides a system and method for computer assisted event based reconstruction and forensic analysis of vehicle accidents.
  • the system comprises an event capture device that records audio, video, and other information that collectively comprise an event.
  • the event data including the audio, video, and other related information, is provided to an evaluation server where it is stored in a database for storage and later forensic analysis of the events comprising the vehicle accident.
  • data for a specific automobile accident event can be analyzed and compared to similar type of automobile accident event data in order to forensically analyze the specific event and determine the cause of the accident.
  • information about the circumstances surrounding the event is captured during the event to provide an analyst with objective information about the event as it took place.
  • specific information may include (but are not limited to) the GPS location of the vehicle, the G-forces acting on the vehicle, the speed and direction of the vehicle, operation or status of vehicle systems such as lights or brakes or engine, and audio and video data from the vehicle during the automobile accident.
  • Figure 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
  • FIG. 2 is a block diagram illustrating an example event detector according to an embodiment of the present invention.
  • FIG. 3 is a block diagram illustrating an example event according to an embodiment of the present invention.
  • Figure 4 A is a block diagram illustrating an example event traveling from an event detector to an evaluation server according to an embodiment of the present invention
  • Figures 4B - 4D are network diagrams illustrating example routes for an event traveling from an event detector to an evaluation server according to various embodiments of the present invention
  • Figure 5 is a network diagram illustrating an example system for reducing driving risk according to an embodiment of the present invention.
  • Figure 6 is a network diagram illustrating an example route for a group of events traveling from an evaluation server to an analysis station according to an embodiment of the present invention
  • Figure 7 is a network diagram illustrating an example route for a coaching session and an event report traveling from an analysis station to an evaluation sever according to an embodiment of the present invention
  • Figure 8 is a network diagram illustrating an example route for a coaching session and an event report traveling from an evaluation sever to a coaching station and a supervisor station according to an embodiment of the present invention
  • Figure 9 is a block diagram illustrating an example evaluation server according to an embodiment of the present invention.
  • FIG. 10 is a block diagram illustrating an example hindsight module according to an embodiment of the present invention.
  • Figure 11 is a block diagram illustrating an example administrative module according to an embodiment of the present invention.
  • Figure 12 is a flow diagram illustrating an example process for forensic analysis of a vehicle accident according to an embodiment of the present invention
  • Figure 13 is a block diagram illustrating an example wireless communication device that may be used in connection with various embodiments described herein;
  • Figure 14 is a block diagram illustrating an example computer system that may be used in connection with various embodiments described herein.
  • Certain embodiments as disclosed herein provide for systems and methods for reducing driving risk that capture driving events and provide those events to an evaluation server where the events are analyzed and reported to management and also compiled into coaching sessions for individuals or groups of drivers to receive in order to demonstrate to them how to avoid risky behaviors while driving.
  • one method as disclosed herein allows for an event capture device to capture an event and send the event via a communication network to an evaluation server.
  • the evaluation server allows an analyst to review the raw event data and create a coaching session directed toward future avoidance of the risky behavior that caused the event.
  • the evaluation server compiles reports regarding the events for particular drivers or groups of drivers. The reports are then provided to management by the evaluation server and the coaching sessions are provided to the individual drivers or groups of drivers to improve their future avoidance of risky driving behaviors.
  • 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.
  • 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.
  • 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 an event detector 30 is later described with respect to Fig. 17.
  • 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. 16.
  • the event detector 30 instructs the one or more event capture devices 20 to record pre-event data, during the event data, and post- event data that is then provided to the event detector 30 and 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.
  • 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.
  • an 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 an event capture device 20 in order to provide a rich set of information about a detected event.
  • 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 30.
  • event detector 30 in combination with the one or more event capture devices 20 identifies an event and stores certain audio and video data along with related information about the event.
  • related information may include the speed of the vehicle when the event occurred, the direction the vehicle was traveling, the location of the vehicle (e.g., from a global positioning system (“GPS”) sensor), and other information from sensors located in and around the vehicle or from the vehicle itself (e.g., from a data bus integral to the vehicle such as an on board diagnostic (“OBD”) vehicle bus).
  • GPS global positioning system
  • OBD on board diagnostic
  • 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.
  • AV audio/video
  • 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.
  • 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 20 or external from the event detector 20.
  • an accelerometer may be integral to the event detector 20 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).
  • the communication module 120 is configured to manage communications between the event detector 20 and other devices and modules. For example, the communication module 120 may handle communications between the event detector 20 and the various event capture devices. The communication module 120 may also handle communications between the event detector 20 and a memory device, a docking station, or a server such as an evaluation server.
  • the communication module 120 is configured to communicate with these various types of devices and other types of devices via a direct wire link (e.g., USB cable, firewire cable), a direct wireless link (e.g., infrared, Bluetooth, ZigBee), or a wired or any wireless network link such as a local area network ("LAN”), a wide area network ("WAN"), a wireless wide area network (“WWAN”), an IEEE 802 wireless network such as an IEEE 802.16 (“WiFi”) network, a WiMAX network, satellite network, or a cellular network.
  • the control module 130 is configured to control the actions or remote devices such as the one or more event capture devices.
  • the control module 130 may be configured to instruct the event capture devices to capture an event and return the data to the event detector when it is informed by the sensor module 110 that certain trigger criteria have been met that identify an event.
  • Fig. 3 is a block diagram illustrating an example event 150 according to an embodiment of the present invention.
  • the event 150 comprises audio data 150, video data 160, and metadata 180.
  • the audio data 150 can be collected from inside the vehicle, outside the vehicle, and may 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.
  • Video data 170 may include still images or moving video captured by one or more cameras 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.
  • 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, but is not limited to, the velocity and direction of the vehicle, the GPS location of the vehicle, elevation, time, temperature, and vehicle engine and electrical component information, status of vehicle lights and signals, brake operation and position, throttle position, etc. 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 deployed, whether evasive maneuvering was attempted as determined by the route of the vehicle prior to the event.
  • 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.
  • Fig. 4A is a block diagram illustrating an example event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention.
  • events such as event 150 are captured by an event detector 30 and stored locally until they are provided to the evaluation server 50.
  • the means by which an event 150 can be provided to the evaluation server 50 can vary.
  • an event 150 may be provided from event detector 30 to 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 150 data structure and/or a secure channel between the event detector 30 and the evaluation server 50.
  • 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, ZigBee link, or an IEEE 802.11 point-to-point link, a WiMAX link, or a cellular 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.
  • Fig. 4B is a network diagram illustrating an example route for an event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention.
  • the event 150 travels over a network 70 from the event detector 30 to the evaluation server 50.
  • the network 70 may comprise any of a variety of network types and topologies and any combination of such types and topologies.
  • the network 70 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”), satellite network, or any combination of the these.
  • Network 70 may also include that particular combination of networks ubiquitously known as the Internet.
  • Fig. 4C is a network diagram illustrating an example route for an event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention.
  • the event 150 travels to a wireless network 72 by way of an access point 210 and then on to the evaluation server 50 via the wireless network 72.
  • the access point 210 may provide access via many different wireless network protocols as will be well understood by those having skill in the art.
  • the wireless network 72 may be a WWAN or a WiFi network.
  • the link between the event detector 30 and the access point 210 may be a short range direct link or a wide range direct link.
  • the access point 210 may be a large radio tower device or a small in-home wireless appliance.
  • the wireless network 72 may include over the air segments and also wired segments.
  • the last mile segments of wireless network 72 may be over the air while internal and back end segments may be wired segments.
  • the wireless network 72 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 the evaluation server 50.
  • Fig. 4D is a network diagram illustrating an example route for an event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention.
  • a docking station 200 is disposed between the event detector and the network 74.
  • an event 150 may be provided from the event detector 30 to the docking station 200 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 200 to convey the event 150 from the event detector 30 to the docking station 200.
  • the network 74 may be a wired or wireless network or a combination of the two.
  • the network 74 may also be private or public in whole or in part and may also include the Internet.
  • Fig. 5 is a network diagram illustrating an example system for driver improvement according to an embodiment of the present invention.
  • the system includes an event detector 30, a coaching station 40, a supervisor station 42, an evaluation server 50, and an analysis station 60, each coupled with a data storage area 35, 45, 47, 55, and 65, respectively. Additional event detectors 30, coaching stations 40, supervisor stations 42, evaluation servers 50, and analysis stations 60 may also be included.
  • the function of the event detector 30 is to identify and capture a plurality of events and send a data structure representing the audio, video, and other data related to the 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 event data (e.g., audio, video, and metadata) in order to make an analysis related to the event and create summary reports and the like.
  • an event After an event is reviewed, it may be discarded, incorporated into a coaching session, flagged for follow up, flagged for inclusion in one or more reports, or otherwise maintained for later coaching, reporting, or analysis. In one embodiment, certain portions of one or more events may be incorporated into a report or a coaching session and then sent back to the evaluation server 50 for storage.
  • the coaching station 40 is configured to play coaching sessions to a particular driver in order to educate the driver about his or her risky driving behavior and suggest alternative driving techniques that the driver may employ to reduce such risky behavior.
  • the coaching station 40 can access coaching sessions from the evaluation server 50 via the network 76 to view the coaching session.
  • the supervisor station 42 is configured to allow executives, managers, and supervisors to access reports on the evaluation server over network 76 and view coaching sessions and reports regarding driver behavior.
  • a conventional web browser utility can be used at either the coaching station 40 or the supervisor station 42 to view both reports and coaching stations, thereby making either device a coaching station or a supervisor station based on the type of information that is accessed from the evaluation server.
  • Fig. 6 is a network diagram illustrating an example route for a group of events 152 traveling from an evaluation server to an analysis station according to an embodiment of the present invention.
  • the group of events 152 is provided by the evaluation server 50 to the analysis station 60 via the network 76.
  • the group of events 152 may be identified 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.
  • 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.
  • the driver identifier may be obtained by the event detector by reading an infrared identification device, perhaps incorporated into the driver's identification badge or by receiving the identifier as input when the driver begins the shift, or by reading the identifier from a media card or other wired or wireless device associated with the driver.
  • 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 that reviews each event to identify those events that need to be reported or shown to the driver, for example as part of a coaching station.
  • Fig. 7 is a network diagram illustrating an example route for a coaching session 200 and an event report 210 traveling from an analysis station 60 to an evaluation sever 50 according to an embodiment of the present invention.
  • an operator at the analysis station 60 may create a coaching session 200 that is made up of all or a portion of a plurality of events (audio, video, and metadata).
  • the coaching session 200 may also include notes/comments from an operator who analyzed the event data or notes/comments from a supervisor or manager or executive. Such a coaching session 200 may be directed to an individual driver, a shift of drivers, or other classes of drivers for which the session may be beneficial (e.g., night time drivers, truck drivers, drivers of vehicles with trailers, etc.). The coaching session may also be directed to supervisors or managers or executives.
  • the operator may also create a report 210 that is made up of summary information about all notable events.
  • a notable event may be characterized as any event that the vehicle owner wants to know about.
  • a report 210 may be created that includes information about all captured events, whether the event reflects a pothole or an automobile accident.
  • one or more coaching sessions 200 and reports 210 can be provided from the analysis station 60 to the evaluation server 50. These coaching sessions and reports can then be maintained at the evaluation server 50 for later viewing by executives, managers, supervisors, drivers, and the like. Such reports 210 and coaching sessions 200 can also be compiled onto a portable media such as a CD for viewing by new employees during orientation sessions.
  • Fig. 8 is a network diagram illustrating an example route for a coaching session 200 and an event report 210 traveling from an evaluation sever 50 to a coaching station 40 and a supervisor station 42 according to an embodiment of the present invention.
  • the coaching session 200 and report 210 travel to one or more coaching stations
  • reports and coaching sessions can be sent to any remote device for review.
  • a conventional web browser utility can be used at a remote station to view both reports and coaching stations, thereby making the device both a coaching station and a supervisor station based on the type of information that is accessed from the evaluation server.
  • Fig. 9 is a block diagram illustrating an example evaluation server 50 according to an embodiment of the present invention.
  • the evaluation server 50 comprises a foresight module 250, a hindsight module 260, an insight module 270, and an administrative module 280.
  • the foresight module 250 is configured to monitor individual driver behavior and objectively score that behavior.
  • the driver score is provided to executives and managers who can use that information to make informed decisions about behavior modification to eliminate or reduce risky behavior of an individual driver.
  • reducing or eliminating risky behavior of a fleet of drivers may have a significant effect on the cost of insurance for the owner of the fleet of vehicles being driven.
  • the hindsight module 260 is configured to capture and store event data related to accidents, crashes, and other serious driving events in order to document for use by law enforcement in forensic analysis and insurance companies in coverage disputes.
  • the captured event information provides a purely objective reconstruction of what happened prior to, during, and after an event.
  • the insight module 270 is configured to aggregate event data into a database of driving events and correlate information in the database to identify trends in driving behavior that relate to risk factors. For example, information about the vehicle and its various components, the driver and occupants, the driving conditions, the driving environment, and other useful data can be employed.
  • the insight module 270 is additionally configured to correlate cause and effect relationships between data points and determine the effect of those relationships upon driver safety.
  • the insight module 270 additionally compares these correlations and driver safety trends with historical event information for individual drivers to provide a driver rating or driver score for an individual driver. The driver score can be used by insurance companies to establish individualized insurance rates.
  • Fig. 10 is a block diagram illustrating an example hindsight module according to an embodiment of the present invention.
  • the hindsight module 260 comprises a key element module 350, a correlation module 360, a factor module 370, a reporting module 380, and an other module 390.
  • the element module 350 is configured to identify particular elements in one or more events that comprise a vehicle accident.
  • an element may include the temperature or other weather related conditions (e.g., if it was raining), the number of vehicle occupants, road conditions (icy, wet, unpaved), traffic conditions (heavy, light), driving conditions (traffic light, stop sign, yield sign, one way street, divided highway, merging traffic, etc.), vehicle status (speed, accelerating, decelerating), interior noise level, and the like.
  • discrete data points related to one or more events comprising a vehicle accident can each be an element.
  • the element module is configured to identify such elements from the one or more events that comprise a vehicle accident.
  • the review can be conducted by an operator or by automated computer analysis.
  • the decibel level on the audio track can be analyzed by computer to determine the sound level inside the vehicle at certain times during the one or more events.
  • computer analysis of metadata fields can provide temperature information, vehicle status information (e.g., speed), and other information collected from an OBD vehicle bus without operator intervention.
  • the video track can be analyzed for indicators that point to elements of the vehicle accident, for example, significant color changes from frame to frame over large portions of the frame may indicate a rapid change in direction of the vehicle.
  • other computer facilitated analyses of the audio, video, and metadata information related to the one or more events can be performed without an operator.
  • the correlation module 360 is configured to manage a data storage area of historical correlations and identify causation and/or contributory correlations between elements and vehicle accidents.
  • correlation module 360 is configured to automatically review vehicle accident event data and elements identified by the element module 350 on an ongoing basis to further identify and refine causal and contributory correlations between one or more elements or combinations of elements and accidents.
  • the correlation module 360 may receive a group of elements from the element module 350 and analyze those elements to determine that the ice on the road caused the vehicle to crash.
  • the correlation module 360 analyzes each of the elements identified from one or more events of a vehicle accident and compares those elements to causal and contributory correlations stored in a data storage area accessible to the correlation module, e.g., in the data storage area of the evaluation server. By making such comparisons and identifying the elements that are present, the correlation module 360 can categorize the elements related to the vehicle accident, for example, those elements that are possibly causal and those elements that are possible contributory.
  • the factor module 370 is configured to receive information from the element module 350 and the correlation module 360 and identify those elements that are the likely factors that caused or contributed to the cause of the vehicle accident.
  • the element module
  • the correlation module 360 may categorize the ice road conditions as possibly causal and categorize normal vehicle speed as unrelated.
  • the factor module 370 may review the information from the element module 350 and the correlation module 360 and determine that the speed of the vehicle was the likely factor that caused the vehicle accident because the speed was too great under the specific conditions of the road.
  • the factor module 370 may also maintain a data storage area of historical factors that are continuously refined and updated so that future factor comparisons and judgments made by computer analysis can be more accurate.
  • Reporting module 330 is configured to compile reports based on individual and aggregate event data. Reports may be compiled for an individual driver, a particular shift, all day time drivers, all night time drivers, all twilight drivers (morning and evening), all drivers of particular vehicle types, and other groupings. These reports can be provided to supervisors, managers, and executives. The reports may also be provided to the individual drivers, for example, a report of the individual driver's events for the previous month, a report of a particularly significant individual event, etc.
  • reports can be included as part of a coaching session to provide the viewer with concise summary data about the events in the coaching session.
  • reports can be targeted for drivers, supervisors, managers, executives, public relations (e.g., reporters/press), insurance companies, government agencies, legal authorities, legal representatives and the like.
  • the reports may be used for a variety of purposes, including supplemental coaching of drivers to emphasize the benefits of reducing risky driving behavior.
  • Fig. 11 is a block diagram illustrating an example administrative module 280 according to an embodiment of the present invention.
  • the administrative module 280 comprises a communication module 450, an event detector module 460, a database module 470, and an other module 480.
  • the communication module 450 is configured to manage communications between the evaluation server 50 and the various stations and event detectors that are part of the system for reducing driving risk.
  • the communication module 450 may manage communications with individual event detectors, analysis stations, coaching stations, supervisor stations, docking stations, and the like.
  • communication module 450 may also manage communications between the various modules of the evaluation server 50. For example, communications between the foresight, hindsight, and insight modules may be managed by communication module 450.
  • the communication module 450 is configured to manage wireless and wired communications and send and receive communications over a wired or wireless network.
  • the communication module 450 is configured to send and receive communications to and from an event detector device, either directly or indirectly. For example, communications with an event detector device may take place through a docking station or a server that aggregates event data from multiple event detector devices before sending the event data to the evaluation server.
  • the event detector module 460 is configured to manage individual and groups of event detectors. In one embodiment, the event detector module 460 may manage software versions that are resident on individual event detector devices so that the overall system may be kept up to date with respect to the versions of software deployed in the field. [72] Event detector module 460 may also track the individual event detectors that have provided event data or otherwise reported back to the evaluation server during a given time period. For example, event detector module 460 may track those event detectors that have reported in during each day and provide summary reports so that managers and supervisors can determine if event data from each vehicle in use is being sent to the evaluation server. In one embodiment, the event detector module 460 may attempt to contact an individual event detector in order to determine the status of the event detector. Advantageously, the evaluation server can determine the efficacy of the overall system by periodic confirmation of the status of each event detector. If the event detector module 460 determines that a particular event detector is not working properly, then that event detector may be identified as needing service or replacement.
  • Database module 470 is configured to manage a database of information related to reducing driving risk. For example, event data, coaching sessions, and reports can be maintained in a data storage area by database module 470. Additionally, related information from sources other than event detectors and analysis stations may also be managed by the database module 470. For example, weather information can be obtained from third party sources and stored to provide objective information about the weather conditions during a particular event. Additional information may also include traffic congestion information and smog/visibility information. Other beneficial information may also be included and managed by database module 470.
  • Fig. 12 is a flow diagram illustrating an example process for forensic analysis of a vehicle accident according to an embodiment of the present invention. The illustrated process may be carried out by a hindsight module on an evaluation server previously described with respect to Fig. 9 and included in a system such as that previously described with respect to Fig. 5. The forensic analysis may also be carried out on an analysis station such as that described in the system of Fig. 5.
  • the system obtains event data related to a vehicle accident.
  • the event data may comprise one or more discrete events captured by an event detector in a vehicle, with each event comprising audio, video, and metadata from one or more event capture devices.
  • the event data may be obtained from a data storage area or from a companion application residing on a remote server across a network.
  • the event data may also be obtained directly from one or more event detectors.
  • the event data may include events from each vehicle involved in the accidents and other vehicles that were near the accident scene and captured information relevant to the event.
  • the event data is reviewed. The review may include computerized analysis of audio data, video data, and metadata.
  • the review may also include operator analysis of audio data, video data, and metadata.
  • the review may also include a combination of computerized and operator analysis.
  • the computerized analysis proceeds automatically and an operator reviews the results of the computerized analysis.
  • the operator may only review certain elements that are flagged by the computerized analysis as potentially benefiting from further operator analysis.
  • event elements are identified.
  • the elements may be from one or more events and may be identified by an operator review or by computerized review.
  • elements include individual data points that are included in the event data, for example, the weather conditions, speed of the vehicle, location of the vehicle, operational status of the vehicle, etc.
  • Elements may also include audio and video elements.
  • a plurality of elements can be identified by a combination of computerized analysis and operator analysis.
  • step 530 those elements are correlated with historical information about vehicle accidents. For example, the same or similar elements can be analyzed from a historical perspective to determine the likelihood that a particular element was a contributing factor to the vehicle accident or the cause of the vehicle accident.
  • a database of elements is maintained such that each element includes one or more relative weights that describe how often the particular element is the cause of an accident or a contributing factor to an accident. Relationships between elements may also be tracked historically so that, for example, the presence of a first element in combination with a second element may indicate a cause of a vehicle accident 90% of the time.
  • step 540 the particular factors that may have caused the vehicle accident and those that may have contributed to the vehicle accident are determined.
  • these factors are determined by ranking the relative correlations between identified elements singularly and also in the presence of others.
  • the system advantageously updates the data storage area that contains historical element, correlation, and factor data. This allows later forensic analyses to benefit from the aggregate historical data about the various elements, correlations, and factors.
  • the system can generate a forensic analysis report that details all of the information collected and analyzed and determined about the vehicle accident.
  • the report may be a multimedia document that includes audio, video, and other data that steps through (under computer control) the vehicle accident and plays audio and video data and displays critical information to provide an objective reconstruction of the vehicle accident and highlight the various factors that may be causal or contributory.
  • such a report may be later used by an insurance company, a legal team or the like to convey information about the accident.
  • Fig. 13 is a block diagram illustrating an exemplary wireless communication device 650 that may be used in connection with the various embodiments described herein.
  • the wireless communication device 650 may be used in conjunction with an event detector previously described with respect to Fig. 1, or an evaluation server, analysis station, coaching station, or supervisor station previously described with respect to Fig. 2.
  • an evaluation server previously described with respect to Fig. 1
  • an evaluation server previously described with respect to Fig. 2
  • analysis station previously described with respect to Fig. 2
  • coaching station or supervisor station
  • 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.
  • LNA low noise amplifier
  • PA power amplifier
  • modulation circuit 660 a baseband processor
  • baseband processor 662 a speaker 664
  • microphone 666 a microphone 666
  • CPU central processing unit
  • data storage area 670 a hardware interface 672.
  • RF radio frequency
  • 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.
  • 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.
  • 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.
  • 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 baseband 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.
  • 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.
  • 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.
  • Fig. 14 is a block diagram illustrating an exemplary computer system 750 that may be used in connection with the various embodiments described herein.
  • the computer system 750 may be used in conjunction with an event detector previously described with respect to Fig. 1, or an evaluation server, analysis station, coaching station, or supervisor station previously described with respect to Fig. 2.
  • the computer system 750 may be used in conjunction with an event detector previously described with respect to Fig. 1, or an evaluation server, analysis station, coaching station, or supervisor station previously described with respect to Fig. 2.
  • other computer systems and/or architectures may be used, as will be clear to those skilled in the art.
  • the computer system 750 preferably includes one or more processors, such as processor 752. Additional processors may be provided, such as an auxiliary processor to manage input/output, an auxiliary processor to perform floating point mathematical operations, a special-purpose microprocessor having an architecture suitable for fast execution of signal processing algorithms (e.g., digital signal processor), a slave processor subordinate to the main processing system (e.g., back-end processor), an additional microprocessor or controller for dual or multiple processor systems, or a coprocessor. Such auxiliary processors may be discrete processors or may be integrated with the processor 752.
  • the processor 752 is preferably connected to a communication bus 754.
  • the communication bus 754 may include a data channel for facilitating information transfer between storage and other peripheral components of the computer system 750.
  • the communication bus 754 further may provide a set of signals used for communication with the processor 752, including a data bus, address bus, and control bus (not shown).
  • the communication bus 754 may comprise any standard or non-standard bus architecture such as, for example, bus architectures compliant with industry standard architecture ("ISA"), extended industry standard architecture ("EISA”), Micro Channel Architecture (“MCA”), peripheral component interconnect (“PCI”) local bus, mini PCI express, or standards promulgated by the Institute of Electrical and Electronics Engineers (“IEEE”) including IEEE 488 general-purpose interface bus (“GPIB”), IEEE 696/S-100, and the like.
  • ISA industry standard architecture
  • EISA extended industry standard architecture
  • MCA Micro Channel Architecture
  • PCI peripheral component interconnect
  • mini PCI express mini PCI express
  • IEEE Institute of Electrical and Electronics Engineers
  • 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”).
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • 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”).
  • the secondary memory 758 may optionally include a hard disk drive 760 and/or a removable storage drive 762, for example a floppy disk drive, a magnetic tape drive, a compact disc (“CD”) drive, a digital versatile disc (“DVD”) drive, etc.
  • the removable storage drive 762 reads from and/or writes to a removable storage medium 764 in a well- known manner.
  • Removable storage medium 764 may be, for example, a floppy disk, magnetic tape, CD, DVD, memory stick, USB memory device, etc.
  • 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.
  • secondary memory 758 may include other similar means for allowing computer programs or other data or instructions to be loaded into the computer system 750. Such means may include, for example, an external storage medium 772 and an interface 770. Examples of external storage medium 772 may include an external hard disk drive or an external optical drive, or and external magneto-optical drive. [96] Other examples of secondary memory 758 may include semiconductor-based memory such as programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), electrically erasable read-only memory (“EEPROM”), or flash memory. Also included are any other 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.
  • PROM programmable read-only memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable read-only memory
  • 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.
  • external devices e.g. printers
  • 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.
  • 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.
  • 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.
  • 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.
  • RF radio frequency
  • Computer executable code i.e., computer programs or software
  • 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.
  • 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.
  • 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).
  • secondary memory 758 including hard disk drive 760, removable storage medium 764, and external storage medium 772
  • 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.
  • 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.
  • 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.
  • 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.
  • DSP digital signal processor
  • 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.
  • 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 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.

Abstract

A system and method for computer assisted event based reconstruction and forensic analysis of vehicle accidents is provided. The system comprises an event capture device that records audio, video, and other information that collectively comprise one or more events related to a vehicle accident. The event data, including the audio, video, and other related information, is provided to an evaluation server where it is stored in a database for forensic analysis of the events comprising the vehicle accident. Event data for a specific automobile accident event is analyzed and compared to similar types of automobile accident event data in order to forensically analyze the specific event and correlate causal relationships with key elements of the event data to determine the likely cause of the accident or the factors contributing to the accident. Correlation information is also stored at the evaluation server to provide historical data points about causal relationships and key elements.

Description

SYSTEM AND METHOD FOR
REDUCING DRIVING RISK WITH HINDSIGHT
Background
1. Field of the Invention
[01] The present invention generally relates to computer assisted forensic analysis of vehicle accidents and more specifically relates to event based reconstruction and review of vehicle accidents to facilitate forensic analysis.
2. Related Art
[02] Conventional systems for conducting forensic analysis of vehicle accidents are necessarily after the fact reconstructions based on informed guesswork after a costly and detailed review of an accident scene. Additionally, analysis of the data produced by these reconstructions is extremely time consuming and expensive, requires a specific skill set developed over significant time, and in the end results in conclusions based on circumstantial evidence gathered after the accident took place. Accordingly, what is needed is an efficient system and method for capturing environmental data leading up, during, and after a vehicle accident to facilitate the forensic analysis of the vehicle accident with relevant real time information.
Summary
[03] The present invention provides a system and method for computer assisted event based reconstruction and forensic analysis of vehicle accidents. The system comprises an event capture device that records audio, video, and other information that collectively comprise an event. The event data, including the audio, video, and other related information, is provided to an evaluation server where it is stored in a database for storage and later forensic analysis of the events comprising the vehicle accident.
[04] In one embodiment, data for a specific automobile accident event can be analyzed and compared to similar type of automobile accident event data in order to forensically analyze the specific event and determine the cause of the accident. Advantageously, information about the circumstances surrounding the event is captured during the event to provide an analyst with objective information about the event as it took place. For example, specific information may include (but are not limited to) the GPS location of the vehicle, the G-forces acting on the vehicle, the speed and direction of the vehicle, operation or status of vehicle systems such as lights or brakes or engine, and audio and video data from the vehicle during the automobile accident.
[05] 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
[06] 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:
[07] Figure 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;
[08] Figure 2 is a block diagram illustrating an example event detector according to an embodiment of the present invention;
[09] Figure 3 is a block diagram illustrating an example event according to an embodiment of the present invention;
[10] Figure 4 A is a block diagram illustrating an example event traveling from an event detector to an evaluation server according to an embodiment of the present invention;
[11] Figures 4B - 4D are network diagrams illustrating example routes for an event traveling from an event detector to an evaluation server according to various embodiments of the present invention;
[12] Figure 5 is a network diagram illustrating an example system for reducing driving risk according to an embodiment of the present invention;
[13] Figure 6 is a network diagram illustrating an example route for a group of events traveling from an evaluation server to an analysis station according to an embodiment of the present invention; [14] Figure 7 is a network diagram illustrating an example route for a coaching session and an event report traveling from an analysis station to an evaluation sever according to an embodiment of the present invention;
[15] Figure 8 is a network diagram illustrating an example route for a coaching session and an event report traveling from an evaluation sever to a coaching station and a supervisor station according to an embodiment of the present invention;
[16] Figure 9 is a block diagram illustrating an example evaluation server according to an embodiment of the present invention;
[17] Figure 10 is a block diagram illustrating an example hindsight module according to an embodiment of the present invention;
[18] Figure 11 is a block diagram illustrating an example administrative module according to an embodiment of the present invention;
[19] Figure 12 is a flow diagram illustrating an example process for forensic analysis of a vehicle accident according to an embodiment of the present invention;
[20] Figure 13 is a block diagram illustrating an example wireless communication device that may be used in connection with various embodiments described herein; and
[21] Figure 14 is a block diagram illustrating an example computer system that may be used in connection with various embodiments described herein.
Detailed Description
[22] Certain embodiments as disclosed herein provide for systems and methods for reducing driving risk that capture driving events and provide those events to an evaluation server where the events are analyzed and reported to management and also compiled into coaching sessions for individuals or groups of drivers to receive in order to demonstrate to them how to avoid risky behaviors while driving. For example, one method as disclosed herein allows for an event capture device to capture an event and send the event via a communication network to an evaluation server. The evaluation server allows an analyst to review the raw event data and create a coaching session directed toward future avoidance of the risky behavior that caused the event. Additionally, the evaluation server compiles reports regarding the events for particular drivers or groups of drivers. The reports are then provided to management by the evaluation server and the coaching sessions are provided to the individual drivers or groups of drivers to improve their future avoidance of risky driving behaviors.
[23] 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.
[24] 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.
[25] 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 an event detector 30 is later described with respect to Fig. 17. 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. 16. [26] When the event detector 30 identifies an event, the event detector 30 instructs the one or more event capture devices 20 to record pre-event data, during the event data, and post- event data that is then provided to the event detector 30 and 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.
[27] 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, an 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 an event capture device 20 in order to provide a rich set of information about a detected event. [28] 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 30.
[29] In one embodiment, event detector 30 in combination with the one or more event capture devices 20 identifies an event and stores certain audio and video data along with related information about the event. For example, related information may include the speed of the vehicle when the event occurred, the direction the vehicle was traveling, the location of the vehicle (e.g., from a global positioning system ("GPS") sensor), and other information from sensors located in and around the vehicle or from the vehicle itself (e.g., from a data bus integral to the vehicle such as an on board diagnostic ("OBD") vehicle bus). This combination of audio, video, and other data is compiled into an event that can be stored in data storage 35 onboard the vehicle for later delivery to an evaluation server. [30] 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.
[31] 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 20 or external from the event detector 20. For example, an accelerometer may be integral to the event detector 20 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).
[32] The communication module 120 is configured to manage communications between the event detector 20 and other devices and modules. For example, the communication module 120 may handle communications between the event detector 20 and the various event capture devices. The communication module 120 may also handle communications between the event detector 20 and a memory device, a docking station, or a server such as an evaluation server. The communication module 120 is configured to communicate with these various types of devices and other types of devices via a direct wire link (e.g., USB cable, firewire cable), a direct wireless link (e.g., infrared, Bluetooth, ZigBee), or a wired or any wireless network link such as a local area network ("LAN"), a wide area network ("WAN"), a wireless wide area network ("WWAN"), an IEEE 802 wireless network such as an IEEE 802.16 ("WiFi") network, a WiMAX network, satellite network, or a cellular network. [33] The control module 130 is configured to control the actions or remote devices such as the one or more event capture devices. For example, the control module 130 may be configured to instruct the event capture devices to capture an event and return the data to the event detector when it is informed by the sensor module 110 that certain trigger criteria have been met that identify an event.
[34] Fig. 3 is a block diagram illustrating an example event 150 according to an embodiment of the present invention. In the illustrated embodiment, the event 150 comprises audio data 150, video data 160, and metadata 180. The audio data 150 can be collected from inside the vehicle, outside the vehicle, and may 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.
[35] Video data 170 may include still images or moving video captured by one or more cameras 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.
[36] 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, but is not limited to, the velocity and direction of the vehicle, the GPS location of the vehicle, elevation, time, temperature, and vehicle engine and electrical component information, status of vehicle lights and signals, brake operation and position, throttle position, etc. 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 deployed, whether evasive maneuvering was attempted as determined by the route of the vehicle prior to the event. The specific identification of the driver may also be included, for example as read by the event detector from a radio frequency identification ("RFID") badge worn by the driver or integrated with a vehicle key assigned to the driver. 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.
[37] Fig. 4A is a block diagram illustrating an example event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention. In one embodiment, events such as event 150 are captured by an event detector 30 and stored locally until they are provided to the evaluation server 50. The means by which an event 150 can be provided to the evaluation server 50 can vary. In various embodiments (or in a single embodiment), an event 150 may be provided from event detector 30 to 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 150 data structure and/or a secure channel between the event detector 30 and the evaluation server 50.
[38] 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, ZigBee link, or an IEEE 802.11 point-to-point link, a WiMAX link, or a cellular 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.
[39] The following figures 4B - 4D illustrate various embodiments for providing events to an evaluation server. [40] Fig. 4B is a network diagram illustrating an example route for an event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention. In the illustrated embodiment, the event 150 travels over a network 70 from the event detector 30 to the evaluation server 50. The network 70 may comprise any of a variety of network types and topologies and any combination of such types and topologies. For example, the network 70 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"), satellite network, or any combination of the these. Network 70 may also include that particular combination of networks ubiquitously known as the Internet.
[41] Fig. 4C is a network diagram illustrating an example route for an event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention. In the illustrated embodiment, the event 150 travels to a wireless network 72 by way of an access point 210 and then on to the evaluation server 50 via the wireless network 72. The access point 210 may provide access via many different wireless network protocols as will be well understood by those having skill in the art. The wireless network 72 may be a WWAN or a WiFi network. The link between the event detector 30 and the access point 210 may be a short range direct link or a wide range direct link. The access point 210 may be a large radio tower device or a small in-home wireless appliance. The wireless network 72 may include over the air segments and also wired segments. For example, the last mile segments of wireless network 72 may be over the air while internal and back end segments may be wired segments. In one embodiment, the wireless network 72 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 the evaluation server 50.
[42] Fig. 4D is a network diagram illustrating an example route for an event 150 traveling from an event detector 30 to an evaluation server 50 according to an embodiment of the present invention. In the illustrated embodiment, a docking station 200 is disposed between the event detector and the network 74. In such an embodiment, an event 150 may be provided from the event detector 30 to the docking station 200 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 200 to convey the event 150 from the event detector 30 to the docking station 200. Once the event
150 is received by the docking station 200, the event is then sent over the network 74 to the evaluation server 50. In the illustrated embodiment, the network 74 may be a wired or wireless network or a combination of the two. The network 74 may also be private or public in whole or in part and may also include the Internet.
[43] Fig. 5 is a network diagram illustrating an example system for driver improvement according to an embodiment of the present invention. In the illustrated embodiment, the system includes an event detector 30, a coaching station 40, a supervisor station 42, an evaluation server 50, and an analysis station 60, each coupled with a data storage area 35, 45, 47, 55, and 65, respectively. Additional event detectors 30, coaching stations 40, supervisor stations 42, evaluation servers 50, and analysis stations 60 may also be included. [44] The function of the event detector 30 is to identify and capture a plurality of events and send a data structure representing the audio, video, and other data related to the 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 event data (e.g., audio, video, and metadata) in order to make an analysis related to the event and create summary reports and the like.
[45] After an event is reviewed, it may be discarded, incorporated into a coaching session, flagged for follow up, flagged for inclusion in one or more reports, or otherwise maintained for later coaching, reporting, or analysis. In one embodiment, certain portions of one or more events may be incorporated into a report or a coaching session and then sent back to the evaluation server 50 for storage.
[46] The coaching station 40 is configured to play coaching sessions to a particular driver in order to educate the driver about his or her risky driving behavior and suggest alternative driving techniques that the driver may employ to reduce such risky behavior. The coaching station 40 can access coaching sessions from the evaluation server 50 via the network 76 to view the coaching session. The supervisor station 42 is configured to allow executives, managers, and supervisors to access reports on the evaluation server over network 76 and view coaching sessions and reports regarding driver behavior. In one embodiment, a conventional web browser utility can be used at either the coaching station 40 or the supervisor station 42 to view both reports and coaching stations, thereby making either device a coaching station or a supervisor station based on the type of information that is accessed from the evaluation server.
[47] Fig. 6 is a network diagram illustrating an example route for a group of events 152 traveling from an evaluation server to an analysis station according to an embodiment of the present invention. In the illustrated embodiment, the group of events 152 is provided by the evaluation server 50 to the analysis station 60 via the network 76. On the evaluation server, the group of events 152 may be identified 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. In one embodiment, the driver identifier may be obtained by the event detector by reading an infrared identification device, perhaps incorporated into the driver's identification badge or by receiving the identifier as input when the driver begins the shift, or by reading the identifier from a media card or other wired or wireless device associated with the driver.
[48] 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 that reviews each event to identify those events that need to be reported or shown to the driver, for example as part of a coaching station. [49] Fig. 7 is a network diagram illustrating an example route for a coaching session 200 and an event report 210 traveling from an analysis station 60 to an evaluation sever 50 according to an embodiment of the present invention. In the illustrated embodiment, an operator at the analysis station 60 may create a coaching session 200 that is made up of all or a portion of a plurality of events (audio, video, and metadata). The coaching session 200 may also include notes/comments from an operator who analyzed the event data or notes/comments from a supervisor or manager or executive. Such a coaching session 200 may be directed to an individual driver, a shift of drivers, or other classes of drivers for which the session may be beneficial (e.g., night time drivers, truck drivers, drivers of vehicles with trailers, etc.). The coaching session may also be directed to supervisors or managers or executives.
[50] Additionally, the operator may also create a report 210 that is made up of summary information about all notable events. A notable event may be characterized as any event that the vehicle owner wants to know about. In one embodiment, there can be certain variable criteria that each vehicle owner can set in order to determine the risk level for events that are compiled into a report 210. Additionally, a report 210 may be created that includes information about all captured events, whether the event reflects a pothole or an automobile accident.
[51] As shown in the illustrated embodiment, one or more coaching sessions 200 and reports 210 can be provided from the analysis station 60 to the evaluation server 50. These coaching sessions and reports can then be maintained at the evaluation server 50 for later viewing by executives, managers, supervisors, drivers, and the like. Such reports 210 and coaching sessions 200 can also be compiled onto a portable media such as a CD for viewing by new employees during orientation sessions.
[52] Fig. 8 is a network diagram illustrating an example route for a coaching session 200 and an event report 210 traveling from an evaluation sever 50 to a coaching station 40 and a supervisor station 42 according to an embodiment of the present invention. In the illustrated embodiment, the coaching session 200 and report 210 travel to one or more coaching stations
40 and supervisor stations 42 over network 76. Although as shown the report 210 goes to the supervisor station 42 and the coaching session 200 goes to the coaching station 40, reports and coaching sessions can be sent to any remote device for review. In one embodiment, a conventional web browser utility can be used at a remote station to view both reports and coaching stations, thereby making the device both a coaching station and a supervisor station based on the type of information that is accessed from the evaluation server.
[53] Fig. 9 is a block diagram illustrating an example evaluation server 50 according to an embodiment of the present invention. In the illustrated embodiment, the evaluation server 50 comprises a foresight module 250, a hindsight module 260, an insight module 270, and an administrative module 280.
[54] The foresight module 250 is configured to monitor individual driver behavior and objectively score that behavior. The driver score is provided to executives and managers who can use that information to make informed decisions about behavior modification to eliminate or reduce risky behavior of an individual driver. Advantageously, reducing or eliminating risky behavior of a fleet of drivers may have a significant effect on the cost of insurance for the owner of the fleet of vehicles being driven.
[55] The hindsight module 260 is configured to capture and store event data related to accidents, crashes, and other serious driving events in order to document for use by law enforcement in forensic analysis and insurance companies in coverage disputes. Advantageously, the captured event information provides a purely objective reconstruction of what happened prior to, during, and after an event.
[56] The insight module 270 is configured to aggregate event data into a database of driving events and correlate information in the database to identify trends in driving behavior that relate to risk factors. For example, information about the vehicle and its various components, the driver and occupants, the driving conditions, the driving environment, and other useful data can be employed. The insight module 270 is additionally configured to correlate cause and effect relationships between data points and determine the effect of those relationships upon driver safety. The insight module 270 additionally compares these correlations and driver safety trends with historical event information for individual drivers to provide a driver rating or driver score for an individual driver. The driver score can be used by insurance companies to establish individualized insurance rates.
[57] Fig. 10 is a block diagram illustrating an example hindsight module according to an embodiment of the present invention. In the illustrated embodiment, the hindsight module 260 comprises a key element module 350, a correlation module 360, a factor module 370, a reporting module 380, and an other module 390.
[58] The element module 350 is configured to identify particular elements in one or more events that comprise a vehicle accident. For example, an element may include the temperature or other weather related conditions (e.g., if it was raining), the number of vehicle occupants, road conditions (icy, wet, unpaved), traffic conditions (heavy, light), driving conditions (traffic light, stop sign, yield sign, one way street, divided highway, merging traffic, etc.), vehicle status (speed, accelerating, decelerating), interior noise level, and the like. Advantageously, discrete data points related to one or more events comprising a vehicle accident can each be an element. [59] The element module is configured to identify such elements from the one or more events that comprise a vehicle accident. This can be accomplished by reviewing metadata, the audio playback, and the video playback for the one or more events. The review can be conducted by an operator or by automated computer analysis. For example, the decibel level on the audio track can be analyzed by computer to determine the sound level inside the vehicle at certain times during the one or more events. Similarly, computer analysis of metadata fields can provide temperature information, vehicle status information (e.g., speed), and other information collected from an OBD vehicle bus without operator intervention. Similarly, the video track can be analyzed for indicators that point to elements of the vehicle accident, for example, significant color changes from frame to frame over large portions of the frame may indicate a rapid change in direction of the vehicle. Advantageously, other computer facilitated analyses of the audio, video, and metadata information related to the one or more events can be performed without an operator. Additionally, elements can also be identified by an operator reviewing the one or more events that comprise a vehicle accident. [60] The correlation module 360 is configured to manage a data storage area of historical correlations and identify causation and/or contributory correlations between elements and vehicle accidents. Advantageously, correlation module 360 is configured to automatically review vehicle accident event data and elements identified by the element module 350 on an ongoing basis to further identify and refine causal and contributory correlations between one or more elements or combinations of elements and accidents.
[61] For example, the correlation module 360 may receive a group of elements from the element module 350 and analyze those elements to determine that the ice on the road caused the vehicle to crash. In one embodiment, the correlation module 360 analyzes each of the elements identified from one or more events of a vehicle accident and compares those elements to causal and contributory correlations stored in a data storage area accessible to the correlation module, e.g., in the data storage area of the evaluation server. By making such comparisons and identifying the elements that are present, the correlation module 360 can categorize the elements related to the vehicle accident, for example, those elements that are possibly causal and those elements that are possible contributory.
[62] The factor module 370 is configured to receive information from the element module 350 and the correlation module 360 and identify those elements that are the likely factors that caused or contributed to the cause of the vehicle accident. For example, the element module
350 may identify certain elements related to an accident such as icy road conditions and vehicle speed within the posted speed limit. The correlation module 360 may categorize the ice road conditions as possibly causal and categorize normal vehicle speed as unrelated. The factor module 370 may review the information from the element module 350 and the correlation module 360 and determine that the speed of the vehicle was the likely factor that caused the vehicle accident because the speed was too great under the specific conditions of the road.
[63] Advantageously, the factor module 370 may also maintain a data storage area of historical factors that are continuously refined and updated so that future factor comparisons and judgments made by computer analysis can be more accurate.
[64] Reporting module 330 is configured to compile reports based on individual and aggregate event data. Reports may be compiled for an individual driver, a particular shift, all day time drivers, all night time drivers, all twilight drivers (morning and evening), all drivers of particular vehicle types, and other groupings. These reports can be provided to supervisors, managers, and executives. The reports may also be provided to the individual drivers, for example, a report of the individual driver's events for the previous month, a report of a particularly significant individual event, etc. Advantageously, reports can be included as part of a coaching session to provide the viewer with concise summary data about the events in the coaching session.
[65] In one embodiment, reports can be targeted for drivers, supervisors, managers, executives, public relations (e.g., reporters/press), insurance companies, government agencies, legal authorities, legal representatives and the like. The reports may be used for a variety of purposes, including supplemental coaching of drivers to emphasize the benefits of reducing risky driving behavior.
[66] Additional functionality may also be included in the hindsight module 260, as indicated by the other module 390. The other module 390 may be configured to perform a variety of tasks, including but not limited to: scoring driver behavior before during and after the accident, identifying the presence of additional passengers in the vehicle, integration and assimilation of accident event data into a common data storage area; and mining of accident event data from the data storage area, just to name a few. [67] Fig. 11 is a block diagram illustrating an example administrative module 280 according to an embodiment of the present invention. In the illustrated embodiment, the administrative module 280 comprises a communication module 450, an event detector module 460, a database module 470, and an other module 480.
[68] In one embodiment, the communication module 450 is configured to manage communications between the evaluation server 50 and the various stations and event detectors that are part of the system for reducing driving risk. For example, the communication module 450 may manage communications with individual event detectors, analysis stations, coaching stations, supervisor stations, docking stations, and the like.
[69] Additionally, communication module 450 may also manage communications between the various modules of the evaluation server 50. For example, communications between the foresight, hindsight, and insight modules may be managed by communication module 450. The communication module 450 is configured to manage wireless and wired communications and send and receive communications over a wired or wireless network. [70] The communication module 450 is configured to send and receive communications to and from an event detector device, either directly or indirectly. For example, communications with an event detector device may take place through a docking station or a server that aggregates event data from multiple event detector devices before sending the event data to the evaluation server.
[71] The event detector module 460 is configured to manage individual and groups of event detectors. In one embodiment, the event detector module 460 may manage software versions that are resident on individual event detector devices so that the overall system may be kept up to date with respect to the versions of software deployed in the field. [72] Event detector module 460 may also track the individual event detectors that have provided event data or otherwise reported back to the evaluation server during a given time period. For example, event detector module 460 may track those event detectors that have reported in during each day and provide summary reports so that managers and supervisors can determine if event data from each vehicle in use is being sent to the evaluation server. In one embodiment, the event detector module 460 may attempt to contact an individual event detector in order to determine the status of the event detector. Advantageously, the evaluation server can determine the efficacy of the overall system by periodic confirmation of the status of each event detector. If the event detector module 460 determines that a particular event detector is not working properly, then that event detector may be identified as needing service or replacement.
[73] Database module 470 is configured to manage a database of information related to reducing driving risk. For example, event data, coaching sessions, and reports can be maintained in a data storage area by database module 470. Additionally, related information from sources other than event detectors and analysis stations may also be managed by the database module 470. For example, weather information can be obtained from third party sources and stored to provide objective information about the weather conditions during a particular event. Additional information may also include traffic congestion information and smog/visibility information. Other beneficial information may also be included and managed by database module 470.
[74] Additional functionality may also be included in the administrative module 280, as indicated by the other module 480. The other module 480 may be configured to perform a variety of tasks, including but not limited to: obtaining related information (e.g., road conditions, traffic conditions, weather, etc.), providing reports about event detector status, and tracking overall system performance and facilitating system maintenance when appropriate. [75] Fig. 12 is a flow diagram illustrating an example process for forensic analysis of a vehicle accident according to an embodiment of the present invention. The illustrated process may be carried out by a hindsight module on an evaluation server previously described with respect to Fig. 9 and included in a system such as that previously described with respect to Fig. 5. The forensic analysis may also be carried out on an analysis station such as that described in the system of Fig. 5.
[76] Initially, in step 500 the system obtains event data related to a vehicle accident. The event data may comprise one or more discrete events captured by an event detector in a vehicle, with each event comprising audio, video, and metadata from one or more event capture devices. The event data may be obtained from a data storage area or from a companion application residing on a remote server across a network. The event data may also be obtained directly from one or more event detectors. In one embodiment, the event data may include events from each vehicle involved in the accidents and other vehicles that were near the accident scene and captured information relevant to the event. [77] Once the event data has been obtained, in step 510 the event data is reviewed. The review may include computerized analysis of audio data, video data, and metadata. The review may also include operator analysis of audio data, video data, and metadata. The review may also include a combination of computerized and operator analysis. In one embodiment, the computerized analysis proceeds automatically and an operator reviews the results of the computerized analysis. Alternatively, the operator may only review certain elements that are flagged by the computerized analysis as potentially benefiting from further operator analysis.
[78] Next, in step 520 event elements are identified. The elements may be from one or more events and may be identified by an operator review or by computerized review. In one embodiment, elements include individual data points that are included in the event data, for example, the weather conditions, speed of the vehicle, location of the vehicle, operational status of the vehicle, etc. Elements may also include audio and video elements. Advantageously, a plurality of elements can be identified by a combination of computerized analysis and operator analysis.
[79] Once the elements have been identified, in step 530 those elements are correlated with historical information about vehicle accidents. For example, the same or similar elements can be analyzed from a historical perspective to determine the likelihood that a particular element was a contributing factor to the vehicle accident or the cause of the vehicle accident. In one embodiment, a database of elements is maintained such that each element includes one or more relative weights that describe how often the particular element is the cause of an accident or a contributing factor to an accident. Relationships between elements may also be tracked historically so that, for example, the presence of a first element in combination with a second element may indicate a cause of a vehicle accident 90% of the time. [80] Accordingly, in step 540 the particular factors that may have caused the vehicle accident and those that may have contributed to the vehicle accident are determined. In one embodiment, these factors are determined by ranking the relative correlations between identified elements singularly and also in the presence of others. After the factors have been determined, in step 550 the system advantageously updates the data storage area that contains historical element, correlation, and factor data. This allows later forensic analyses to benefit from the aggregate historical data about the various elements, correlations, and factors. [81] Next, in step 560 the system can generate a forensic analysis report that details all of the information collected and analyzed and determined about the vehicle accident. In one embodiment, the report may be a multimedia document that includes audio, video, and other data that steps through (under computer control) the vehicle accident and plays audio and video data and displays critical information to provide an objective reconstruction of the vehicle accident and highlight the various factors that may be causal or contributory. Advantageously, such a report may be later used by an insurance company, a legal team or the like to convey information about the accident.
[82] Fig. 13 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 previously described with respect to Fig. 1, or an evaluation server, analysis station, coaching station, or supervisor station previously described with respect to Fig. 2. However, other wireless communication devices and/or architectures may also be used, as will be clear to those skilled in the art.
[83] 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. [84] 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. [85] 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 baseband 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.
[86] 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.
[87] 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.
[88] 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. [89] Fig. 14 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 previously described with respect to Fig. 1, or an evaluation server, analysis station, coaching station, or supervisor station previously described with respect to Fig. 2. However, other computer systems and/or architectures may be used, as will be clear to those skilled in the art.
[90] 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. [91] The processor 752 is preferably connected to a communication bus 754. The communication bus 754 may include a data channel for facilitating information transfer between storage and other peripheral components of the computer system 750. The communication bus 754 further may provide a set of signals used for communication with the processor 752, including a data bus, address bus, and control bus (not shown). The communication bus 754 may comprise any standard or non-standard bus architecture such as, for example, bus architectures compliant with industry standard architecture ("ISA"), extended industry standard architecture ("EISA"), Micro Channel Architecture ("MCA"), peripheral component interconnect ("PCI") local bus, mini PCI express, or standards promulgated by the Institute of Electrical and Electronics Engineers ("IEEE") including IEEE 488 general-purpose interface bus ("GPIB"), IEEE 696/S-100, and the like. [92] 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").
[93] The secondary memory 758 may optionally include a hard disk drive 760 and/or a removable storage drive 762, for example a floppy disk drive, a magnetic tape drive, a compact disc ("CD") drive, a digital versatile disc ("DVD") drive, etc. The removable storage drive 762 reads from and/or writes to a removable storage medium 764 in a well- known manner. Removable storage medium 764 may be, for example, a floppy disk, magnetic tape, CD, DVD, memory stick, USB memory device, etc.
[94] 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.
[95] In alternative embodiments, secondary memory 758 may include other similar means for allowing computer programs or other data or instructions to be loaded into the computer system 750. Such means may include, for example, an external storage medium 772 and an interface 770. Examples of external storage medium 772 may include an external hard disk drive or an external optical drive, or and external magneto-optical drive. [96] Other examples of secondary memory 758 may include semiconductor-based memory such as programmable read-only memory ("PROM"), erasable programmable read-only memory ("EPROM"), electrically erasable read-only memory ("EEPROM"), or flash memory. Also included are any other 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.
[97] 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. [98] 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.
[99] 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.
[100] 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. [101] 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.
[102] 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. [103] 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.
[104] 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. [105] 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. [106] 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 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.
[107] 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

Claims
1. A method for forensic analysis of a vehicle accident, comprising: capturing a driving event at an event capture device coupled with a vehicle, the driving event associated with a vehicle accident and comprising video data from before and during the vehicle accident; providing the driving event to an evaluation server; analyzing the driving event to determine one or more key elements related to the vehicle accident; determining one or more factors that contributed to the cause of the vehicle accident; providing the one or more factors to the evaluation server; and generating a report identifying the one or more factors that contributed to the cause of the vehicle accident.
2. The method of claim 1, wherein the determining step further comprises: correlating the one or more key elements with causation data stored at the evaluation server; and identifying key elements with the highest correlation for causing the vehicle accident.
3. The method of claim 1, wherein the determining step further comprises: correlating the one or more factors with causation data stored at the evaluation server; and identifying factors with the highest correlation for causing the vehicle accident.
4. The method of claim 1, wherein the providing step further comprises updating causation data in a data storage area to reflect the one or more key elements.
5. The method of claim 1, wherein the providing step further comprises updating causation data in a data storage area to reflect the one or more factors.
6. A system for forensic analysis of a vehicle accident, comprising: an event detector coupled with a vehicle, the event detector configured to capture a driving event associated with a vehicle accident, the driving event captured in response to a trigger and comprising audio, video, and metadata information; a communication link configured to convey the driving event from the event detector to an evaluation server; and an evaluation server comprising an element module, a correlation module, and a factor module, said modules configured to analyze the audio, vide, and metadata information to identify a cause of the vehicle accident.
7. The system of claim 6, wherein the communication link is a wired network.
8. The system of claim 7, wherein the wired network comprises a private network.
9. The system of claim 7, wherein the wired network comprises a public network.
10. The system of claim 6, wherein the communication link is a wireless network.
11. The system of claim 10, wherein the wireless network comprises a ZigBee link.
12. The system of claim 10, wherein the wireless network comprises a Bluetooth link.
PCT/US2007/068332 2006-05-09 2007-05-07 System and method for reducing driving risk with hindsight WO2007133992A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/382,325 US9836716B2 (en) 2006-05-09 2006-05-09 System and method for reducing driving risk with hindsight
US11/382,325 2006-05-09

Publications (2)

Publication Number Publication Date
WO2007133992A2 true WO2007133992A2 (en) 2007-11-22
WO2007133992A3 WO2007133992A3 (en) 2008-05-08

Family

ID=38694614

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/068332 WO2007133992A2 (en) 2006-05-09 2007-05-07 System and method for reducing driving risk with hindsight

Country Status (2)

Country Link
US (2) US9836716B2 (en)
WO (1) WO2007133992A2 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3009990A1 (en) * 2014-10-18 2016-04-20 Tata Consultancy Services Limited Method and system for performing crash analysis of one or more vehicles
US20160247538A1 (en) * 2015-02-25 2016-08-25 Industrial Technology Research Institute Event reconstruction system and method thereof
US9610955B2 (en) 2013-11-11 2017-04-04 Smartdrive Systems, Inc. Vehicle fuel consumption monitor and feedback systems
US9663127B2 (en) 2014-10-28 2017-05-30 Smartdrive Systems, Inc. Rail vehicle event detection and recording system

Families Citing this family (77)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8520069B2 (en) 2005-09-16 2013-08-27 Digital Ally, Inc. Vehicle-mounted video system with distributed processing
US10878646B2 (en) 2005-12-08 2020-12-29 Smartdrive Systems, Inc. Vehicle event recorder systems
US20070150138A1 (en) 2005-12-08 2007-06-28 James Plante Memory management in event recording systems
US8996240B2 (en) 2006-03-16 2015-03-31 Smartdrive Systems, Inc. Vehicle event recorders with integrated web server
US9201842B2 (en) 2006-03-16 2015-12-01 Smartdrive Systems, Inc. Vehicle event recorder systems and networks having integrated cellular wireless communications systems
US8269617B2 (en) 2009-01-26 2012-09-18 Drivecam, Inc. Method and system for tuning the effect of vehicle characteristics on risk prediction
US8508353B2 (en) * 2009-01-26 2013-08-13 Drivecam, Inc. Driver risk assessment system and method having calibrating automatic event scoring
US8849501B2 (en) 2009-01-26 2014-09-30 Lytx, Inc. Driver risk assessment system and method employing selectively automatic event scoring
US8989959B2 (en) 2006-11-07 2015-03-24 Smartdrive Systems, Inc. Vehicle operator performance history recording, scoring and reporting systems
US8649933B2 (en) 2006-11-07 2014-02-11 Smartdrive Systems Inc. Power management systems for automotive video event recorders
US8868288B2 (en) 2006-11-09 2014-10-21 Smartdrive Systems, Inc. Vehicle exception event management systems
US8111839B2 (en) * 2007-04-09 2012-02-07 Personics Holdings Inc. Always on headwear recording system
US8239092B2 (en) 2007-05-08 2012-08-07 Smartdrive Systems Inc. Distributed vehicle event recorder systems having a portable memory data transfer system
US20090171528A1 (en) * 2007-12-27 2009-07-02 Sandisk Il Ltd. Apparatus and process for recording data associated with a vehicle
US9818157B2 (en) 2008-10-07 2017-11-14 State Farm Mutual Automobile Insurance Company Method for using electronic metadata to verify insurance claims
US8503972B2 (en) 2008-10-30 2013-08-06 Digital Ally, Inc. Multi-functional remote monitoring system
US8854199B2 (en) * 2009-01-26 2014-10-07 Lytx, Inc. Driver risk assessment system and method employing automated driver log
US20110313593A1 (en) * 2010-06-21 2011-12-22 Cohen Meir S Vehicle On Board Diagnostic Port Device with GPS Tracking, Auto-Upload, and Remote Manipulation
US9087362B2 (en) * 2010-11-08 2015-07-21 International Business Machines Corporation Traffic collision incident visualization with location context
US8731736B2 (en) * 2011-02-22 2014-05-20 Honda Motor Co., Ltd. System and method for reducing driving skill atrophy
EP2723069B1 (en) * 2011-06-16 2017-10-18 Aisin Seiki Kabushiki Kaisha Vehicle periphery monitoring device
DE112012003061T5 (en) 2011-07-21 2014-05-15 Bendix Commercial Vehicle Systems, Llc Vehicle Fleet Management System and Methods to Control and Improve Driver Performance in Fleet Vehicles
US8606492B1 (en) 2011-08-31 2013-12-10 Drivecam, Inc. Driver log generation
US8744642B2 (en) 2011-09-16 2014-06-03 Lytx, Inc. Driver identification based on face data
US8996234B1 (en) 2011-10-11 2015-03-31 Lytx, Inc. Driver performance determination based on geolocation
US9298575B2 (en) 2011-10-12 2016-03-29 Lytx, Inc. Drive event capturing based on geolocation
US8989914B1 (en) 2011-12-19 2015-03-24 Lytx, Inc. Driver identification based on driving maneuver signature
US9240079B2 (en) 2012-04-17 2016-01-19 Lytx, Inc. Triggering a specialized data collection mode
US8676428B2 (en) 2012-04-17 2014-03-18 Lytx, Inc. Server request for downloaded information from a vehicle-based monitor
US9728228B2 (en) 2012-08-10 2017-08-08 Smartdrive Systems, Inc. Vehicle event playback apparatus and methods
WO2014052898A1 (en) 2012-09-28 2014-04-03 Digital Ally, Inc. Portable video and imaging system
US10272848B2 (en) 2012-09-28 2019-04-30 Digital Ally, Inc. Mobile video and imaging system
US9344683B1 (en) 2012-11-28 2016-05-17 Lytx, Inc. Capturing driving risk based on vehicle state and automatic detection of a state of a location
WO2014159127A1 (en) 2013-03-14 2014-10-02 Telogis Inc. System and method for crowdsourcing vehicle-related analytics
US9780967B2 (en) 2013-03-14 2017-10-03 Telogis, Inc. System for performing vehicle diagnostic and prognostic analysis
US9958228B2 (en) 2013-04-01 2018-05-01 Yardarm Technologies, Inc. Telematics sensors and camera activation in connection with firearm activity
US9159371B2 (en) 2013-08-14 2015-10-13 Digital Ally, Inc. Forensic video recording with presence detection
US9253452B2 (en) 2013-08-14 2016-02-02 Digital Ally, Inc. Computer program, method, and system for managing multiple data recording devices
US10075681B2 (en) 2013-08-14 2018-09-11 Digital Ally, Inc. Dual lens camera unit
US10390732B2 (en) 2013-08-14 2019-08-27 Digital Ally, Inc. Breath analyzer, system, and computer program for authenticating, preserving, and presenting breath analysis data
US10311749B1 (en) * 2013-09-12 2019-06-04 Lytx, Inc. Safety score based on compliance and driving
US9501878B2 (en) 2013-10-16 2016-11-22 Smartdrive Systems, Inc. Vehicle event playback apparatus and methods
US9349228B2 (en) 2013-10-23 2016-05-24 Trimble Navigation Limited Driver scorecard system and method
CN104766472A (en) * 2014-01-03 2015-07-08 上海通用汽车有限公司 Vehicle state monitoring method
US9511778B1 (en) * 2014-02-12 2016-12-06 XL Hybrids Controlling transmissions of vehicle operation information
US8892310B1 (en) 2014-02-21 2014-11-18 Smartdrive Systems, Inc. System and method to detect execution of driving maneuvers
US10759442B2 (en) * 2014-05-30 2020-09-01 Here Global B.V. Dangerous driving event reporting
US9428195B1 (en) * 2014-07-24 2016-08-30 Lytx, Inc. Back-end event risk assessment with historical coaching profiles
KR101936891B1 (en) * 2014-08-05 2019-01-10 런치 테크 컴퍼니 리미티드 Method and device for generating driving behavior guidance information
US10161746B2 (en) 2014-08-18 2018-12-25 Trimble Navigation Limited Systems and methods for cargo management
US9714037B2 (en) 2014-08-18 2017-07-25 Trimble Navigation Limited Detection of driver behaviors using in-vehicle systems and methods
US10686976B2 (en) 2014-08-18 2020-06-16 Trimble Inc. System and method for modifying onboard event detection and/or image capture strategy using external source data
CA2964772C (en) 2014-10-20 2020-09-01 Taser International, Inc. Systems and methods for distributed control
US9418488B1 (en) * 2014-10-24 2016-08-16 Lytx, Inc. Driver productivity snapshots and dynamic capture of driver status
US11069257B2 (en) 2014-11-13 2021-07-20 Smartdrive Systems, Inc. System and method for detecting a vehicle event and generating review criteria
WO2016100356A1 (en) 2014-12-15 2016-06-23 Yardarm Technologies, Inc. Camera activation in response to firearm activity
US9679420B2 (en) 2015-04-01 2017-06-13 Smartdrive Systems, Inc. Vehicle event recording system and method
US9841259B2 (en) 2015-05-26 2017-12-12 Digital Ally, Inc. Wirelessly conducted electronic weapon
US10013883B2 (en) 2015-06-22 2018-07-03 Digital Ally, Inc. Tracking and analysis of drivers within a fleet of vehicles
US10192277B2 (en) 2015-07-14 2019-01-29 Axon Enterprise, Inc. Systems and methods for generating an audit trail for auditable devices
US10204159B2 (en) 2015-08-21 2019-02-12 Trimble Navigation Limited On-demand system and method for retrieving video from a commercial vehicle
EP3159853B1 (en) * 2015-10-23 2019-03-27 Harman International Industries, Incorporated Systems and methods for advanced driver assistance analytics
US10904474B2 (en) 2016-02-05 2021-01-26 Digital Ally, Inc. Comprehensive video collection and storage
CN109070825B (en) 2016-03-15 2021-08-31 福特全球技术公司 Determining impact location using vehicle dynamics
CN110139780B (en) 2016-03-15 2021-09-03 福特全球技术公司 Detecting mild impact of a vehicle using low computational overhead
US10521675B2 (en) 2016-09-19 2019-12-31 Digital Ally, Inc. Systems and methods of legibly capturing vehicle markings
US10911725B2 (en) 2017-03-09 2021-02-02 Digital Ally, Inc. System for automatically triggering a recording
US11024137B2 (en) 2018-08-08 2021-06-01 Digital Ally, Inc. Remote video triggering and tagging
KR20200092472A (en) 2019-01-09 2020-08-04 현대자동차주식회사 Method and system for managing edr data in a cloud-based manner
KR20200092471A (en) * 2019-01-09 2020-08-04 현대자동차주식회사 Method and system for managing edr data in a cloud-based manner
CN110308715A (en) * 2019-06-25 2019-10-08 重庆长安汽车股份有限公司 Reading data shows that equipment, automatic Pilot critical data read display system and method
CN110377799A (en) * 2019-06-26 2019-10-25 深圳市轱辘汽车维修技术有限公司 A kind of vehicle assessment data checking method and device
US11107355B2 (en) * 2019-12-05 2021-08-31 Toyota Motor North America, Inc. Transport dangerous driving reporting
US10832699B1 (en) * 2019-12-05 2020-11-10 Toyota Motor North America, Inc. Impact media sharing
US11270118B2 (en) 2020-04-10 2022-03-08 Toyota Motor Engineering & Manufacturing North America, Inc. Creating a valuable video clip using metadata flagging
CN112073490B (en) * 2020-08-31 2022-12-30 中科美络科技股份有限公司 Driving event monitoring method and system based on Internet of things technology
CN113962249B (en) * 2021-12-06 2022-04-19 浙江大华技术股份有限公司 Line pressing identification method and device, electronic equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6246933B1 (en) * 1999-11-04 2001-06-12 BAGUé ADOLFO VAEZA Traffic accident data recorder and traffic accident reproduction system and method
US6408232B1 (en) * 2000-04-18 2002-06-18 Agere Systems Guardian Corp. Wireless piconet access to vehicle operational statistics
US20030154009A1 (en) * 2002-01-25 2003-08-14 Basir Otman A. Vehicle visual and non-visual data recording system
US20040103008A1 (en) * 2002-11-27 2004-05-27 Stefan Wahlbin Computerized method and system for estimating liability for an accident from an investigation of the accident

Family Cites Families (275)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US2943141A (en) 1955-01-07 1960-06-28 Servo Corp Of America Automatic baseball umpire or the like
US3812287A (en) 1969-05-12 1974-05-21 J Lemelson Video detection system
US3634866A (en) 1969-07-24 1972-01-11 Howard P Meyer Vehicle and driver monitoring system
US3781824A (en) 1972-11-20 1973-12-25 Gen Motors Corp Solid state crash recorder
US3885090A (en) 1973-03-20 1975-05-20 Richard W Rosenbaum Continuous automatic surveillance system
US3992656A (en) 1975-09-11 1976-11-16 Joy Ivan L Siren detector
US4054752A (en) 1976-01-30 1977-10-18 Dennis Jr Clay E Cash register protection recording and alarm system
US4280151A (en) 1978-02-24 1981-07-21 Canon Kabushiki Kaisha High speed image recording system
IT1095061B (en) 1978-05-19 1985-08-10 Conte Raffaele EQUIPMENT FOR MAGNETIC REGISTRATION OF CASUAL EVENTS RELATED TO MOBILE VEHICLES
US4271358A (en) 1979-11-13 1981-06-02 Frank Schwarz Selective infrared detector
DE3001452A1 (en) 1980-01-16 1981-07-23 Hans-Günther 8100 Garmisch-Partenkirchen Stadelmayr ALARM, SECURING AND MONITORING SYSTEM
US4420773A (en) 1980-06-30 1983-12-13 Nippon Kogaku K.K. Electronic photographic camera
JPS5778286A (en) 1980-10-31 1982-05-15 Nippon Kogaku Kk <Nikon> Electronic camera
JPS5790106A (en) 1980-11-26 1982-06-04 Nippon Denso Co Ltd Driving indicator for automobile
US4409670A (en) 1981-06-26 1983-10-11 United Technologies Corporation Solid-state digital flight data recorder
US4425097A (en) 1981-09-08 1984-01-10 Owens Lawrence L Apparatus for training equipment operators
BE890517A (en) 1981-09-28 1982-01-18 Staar Sa ELECTRONIC IMAGE STORAGE DEVICE
US4496995A (en) 1982-03-29 1985-01-29 Eastman Kodak Company Down converting a high frame rate signal to a standard TV frame rate signal by skipping preselected video information
US4533962A (en) 1982-08-05 1985-08-06 Decker Ronald R Vehicle performance detection and recording apparatus
DE3405757A1 (en) 1983-02-26 1984-10-04 Edmund 7016 Gerlingen Zottnik ACCIDENT RECORDER
US4621335A (en) 1983-05-31 1986-11-04 Allied Corporation Real time recall feature for an engine data processor system
EP0130428B1 (en) 1983-06-24 1987-05-27 Siemens Aktiengesellschaft Disturbances detecting and recording system
JPH0785135B2 (en) 1983-09-05 1995-09-13 オリンパス光学工業株式会社 Endoscope device
US4630110A (en) 1984-02-15 1986-12-16 Supervision Control Systems, Inc. Surveillance system
CA1187601A (en) 1984-03-27 1985-05-21 B.E.L-Tronics Limited Construction for a portable radar detector having a mirror
US4646241A (en) 1984-06-21 1987-02-24 United Technologies Corporation Solid-state flight data recording system
JPS6177484A (en) 1984-09-25 1986-04-21 Mitsubishi Electric Corp Security system
US4843578A (en) 1984-10-01 1989-06-27 Wade Ted R Vehicle speed monitoring and logging means
JPS61260391A (en) 1985-05-14 1986-11-18 三菱電機株式会社 Monitor/controller
JPH07115649B2 (en) 1985-05-24 1995-12-13 豊田工機株式会社 Vehicle running condition determination device
US4632348A (en) 1985-12-12 1986-12-30 General Motors Corporation Mounting arrangement for a mirror
GB2187006B (en) 1986-02-25 1990-01-10 Sony Corp Random access memory apparatus
US4837628A (en) 1986-07-14 1989-06-06 Kabushiki Kaisha Toshiba Electronic still camera for recording still picture on memory card with mode selecting shutter release
HU206415B (en) 1986-12-29 1992-10-28 Karolyne Otta Method for recording travel data of a motor vehicle into the memory of electronic tachograph, and device for implementing said method
US4949186A (en) 1987-02-13 1990-08-14 Peterson Roger D Vehicle mounted surveillance system
US4789904A (en) 1987-02-13 1988-12-06 Peterson Roger D Vehicle mounted surveillance and videotaping system
US4758888A (en) 1987-02-17 1988-07-19 Orbot Systems, Ltd. Method of and means for inspecting workpieces traveling along a production line
US4814896A (en) 1987-03-06 1989-03-21 Heitzman Edward F Real time video data acquistion systems
US4759069A (en) 1987-03-25 1988-07-19 Sy/Lert System Emergency signal warning system
WO1988009023A1 (en) 1987-05-08 1988-11-17 Viktor Szabo Accident data recorder
US4804937A (en) 1987-05-26 1989-02-14 Motorola, Inc. Vehicle monitoring arrangement and system
US4876597A (en) 1987-09-04 1989-10-24 Adt Security Systems, Inc. Video observation systems
DE3734393A1 (en) 1987-10-10 1989-04-20 Bernhard Mittelhaeuser REAR VIEW MIRROR FOR MOTOR VEHICLES
US4806931A (en) 1988-01-25 1989-02-21 Richard W. Clark Sound pattern discrimination system
DE3807727A1 (en) 1988-03-09 1989-09-21 Robot Foto Electr Kg MONITORING DEVICE FOR SECURING AUTOMATES
US4939652A (en) 1988-03-14 1990-07-03 Centrodyne Inc. Trip recorder
US4930742A (en) 1988-03-25 1990-06-05 Donnelly Corporation Rearview mirror and accessory mount for vehicles
US4980913A (en) 1988-04-19 1990-12-25 Vindicator Corporation Security system network
US4843463A (en) 1988-05-23 1989-06-27 Michetti Joseph A Land vehicle mounted audio-visual trip recorder
US5012335A (en) 1988-06-27 1991-04-30 Alija Cohodar Observation and recording system for a police vehicle
GB8825446D0 (en) 1988-10-31 1988-11-30 Lawrence M J Vehicle security camera
US4936533A (en) 1988-11-15 1990-06-26 Donnelly Corporation Mounting assembly for vehicle accessories
US4896855A (en) 1988-11-21 1990-01-30 Cincinnati Microwave, Inc. Pivotal windshield mount
US4945244A (en) 1988-12-23 1990-07-31 Castleman Robert D Electronic infrared detector
US5712679A (en) 1989-01-16 1998-01-27 Coles; Christopher Francis Security system with method for locatable portable electronic camera image transmission to a remote receiver
US5056056A (en) 1989-02-02 1991-10-08 Systems Research Laboratories, Inc. Data recorder including a recirculating non-volatile memory
US4992943A (en) 1989-02-13 1991-02-12 Mccracken Jack J Apparatus for detecting and storing motor vehicle impact data
US5057820A (en) 1989-05-01 1991-10-15 Airborne Research Associates, Inc. Optical warning system
DE68918115T2 (en) 1989-06-08 1995-01-05 Bosch Gmbh Robert VEHICLE NAVIGATION SYSTEM.
US5065321A (en) 1989-06-15 1991-11-12 Pulse Electronics, Inc. Solid state event recorder
US5140436A (en) 1989-11-02 1992-08-18 Eastman Kodak Company Pre-event/post-event recording in a solid state fast frame recorder
US5196938A (en) 1989-11-20 1993-03-23 Eastman Kodak Company Solid state fast frame recorder having independently selectable frame rate and exposure
US5140434A (en) 1990-01-29 1992-08-18 Eastman Kodak Company Record on command recording in a solid state fast frame recorder
US5027104A (en) 1990-02-21 1991-06-25 Reid Donald J Vehicle security device
EP0667609B1 (en) 1990-03-09 2000-05-24 Canon Kabushiki Kaisha Signal recording system
JP2920653B2 (en) 1990-03-15 1999-07-19 アイシン精機株式会社 In-vehicle imaging device
US5111289A (en) 1990-04-27 1992-05-05 Lucas Gary L Vehicular mounted surveillance and recording system
JPH0715391B2 (en) 1990-05-09 1995-02-22 矢崎総業株式会社 Digital operation recording device
US5455716A (en) 1990-08-14 1995-10-03 Prince Corporation Vehicle mirror with electrical accessories
US5144661A (en) 1991-02-11 1992-09-01 Robert Shamosh Security protection system and method
US5100095A (en) 1991-03-01 1992-03-31 Donnelly Corporation Breakaway vehicle accessory mount
US5469360A (en) 1991-03-10 1995-11-21 Matsushita Electric Industrial Co., Ltd. Vehicle position detecting apparatus
US5408330A (en) 1991-03-25 1995-04-18 Crimtec Corporation Video incident capture system
JP3058942B2 (en) 1991-06-27 2000-07-04 三菱電機株式会社 Navigation device
US5321753A (en) 1991-07-08 1994-06-14 The United States Of America As Represented By The United States Department Of Energy Secure communication of static information by electronic means
DE4127395A1 (en) 1991-08-19 1993-02-25 Siemens Ag METHOD AND DEVICE FOR DETECTING AND LOCATING CHANGES ON A COMPONENT OF A TURBINE
US5178448A (en) 1991-09-13 1993-01-12 Donnelly Corporation Rearview mirror with lighting assembly
US5327288A (en) 1991-09-13 1994-07-05 Donnelly Corporation Reduced vibration day/night rearview mirror assembly
US5544060A (en) 1991-10-16 1996-08-06 Zexel Usa Corporation Vehicle mounted navigation system with preview function
US5654892A (en) 1991-10-18 1997-08-05 Zexel Usa Corporation Navigation system displaying forthcoming turns
WO1993009008A1 (en) 1991-10-31 1993-05-13 Bruno Pineroli Device for detecting running variables in a motor vehicle
JP3273800B2 (en) 1991-11-11 2002-04-15 茂 近藤 Car driving analysis diagnosis method and device
JPH05137144A (en) 1991-11-15 1993-06-01 Kyocera Corp Accident monitoring system using digital electronic camera
US5294978A (en) * 1991-12-17 1994-03-15 Eastman Kodak Company Visualization techniques for temporally acquired sequences of images
US5644851A (en) 1991-12-20 1997-07-08 Blank; Rodney K. Compensation system for electronic compass
US5361326A (en) 1991-12-31 1994-11-01 International Business Machines Corporation Enhanced interface for a neural network engine
US5546191A (en) 1992-02-25 1996-08-13 Mitsubishi Denki Kabushiki Kaisha Recording and reproducing apparatus
US5223844B1 (en) 1992-04-17 2000-01-25 Auto Trac Inc Vehicle tracking and security system
US5523811A (en) 1992-04-17 1996-06-04 Canon Kabushiki Kaisha Camera device for moving body
JPH05294188A (en) 1992-04-23 1993-11-09 Toshiba Corp On-vehicle image recording system
DE4218397A1 (en) 1992-06-04 1993-12-09 Mannesmann Kienzle Gmbh Short path registration device for motor vehicles
GB2268608A (en) 1992-06-10 1994-01-12 Norm Pacific Automat Corp Vehicle accident prevention and recording system
US5387926A (en) 1992-06-30 1995-02-07 California Institute Of Technology High speed digital framing camera
US5309485A (en) * 1992-07-06 1994-05-03 General Electric Company Core automated monitoring system
JPH0785280B2 (en) 1992-08-04 1995-09-13 タカタ株式会社 Collision prediction judgment system by neural network
US5465079A (en) 1992-08-14 1995-11-07 Vorad Safety Systems, Inc. Method and apparatus for determining driver fitness in real time
CA2141971C (en) 1992-08-14 2001-12-25 Jerry D. Woll Recording of operational events in an automotive vehicle
DE69330482T2 (en) 1992-08-19 2001-12-13 Aisin Aw Co Vehicle navigation system
JPH0674086A (en) 1992-08-27 1994-03-15 Nippondenso Co Ltd Self-diagnostic device for vehicle
US5521633A (en) 1992-09-25 1996-05-28 Yazaki Corporation Motor vehicle obstacle monitoring system using optical flow processing
US5473729A (en) 1992-09-30 1995-12-05 Bryant; David P. Critical incident recorder
KR950008673B1 (en) 1992-12-05 1995-08-04 삼성전자주식회사 Wordline boosting and the same control circuit of semiconductor intergrated circuit
US5430432A (en) 1992-12-14 1995-07-04 Camhi; Elie Automotive warning and recording system
US5308247A (en) 1993-01-21 1994-05-03 Dyrdek Robert D Electrical connector assembly for automobile rearview mirror and light assembly and method of assembling the same
US5330149A (en) 1993-01-28 1994-07-19 Donnelly Corporation Breakaway accessory mounting for vehicles
US5311197A (en) 1993-02-01 1994-05-10 Trimble Navigation Limited Event-activated reporting of vehicle location
US5262813A (en) 1993-02-09 1993-11-16 Scharton Terry D Impact triggering mechanism for a camera mounted in a vehicle
JP2983407B2 (en) 1993-03-31 1999-11-29 三菱電機株式会社 Image tracking device
JP2521024B2 (en) 1993-04-20 1996-07-31 淡路フェリーボート株式会社 Traffic accident data recorder and traffic accident reproduction system
US5559496A (en) 1993-05-19 1996-09-24 Dubats; William C. Remote patrol system
PT101282B (en) 1993-05-28 1999-12-31 Ermida Inocencio Valentim Frei AUTOMATIC SAFETY DEVICE FOR VEHICLES, WITH INVIOLABLE REGISTRY OF SOUNDS AND IMAGE
US5504482A (en) 1993-06-11 1996-04-02 Rockwell International Corporation Automobile navigation guidance, control and safety system
BR9302188A (en) 1993-06-25 1995-01-17 Metagal Ind & Comercio Improvement in internal rear view mirror with courtesy lights
US5548273A (en) 1993-06-29 1996-08-20 Competition Components International Pty Ltd Vehicle driving monitor apparatus
DE4322937A1 (en) 1993-07-09 1995-01-12 Hohe Kg Information device in a motor vehicle
EP0636955B1 (en) 1993-07-26 1998-11-04 Hitachi, Ltd. Control unit for vehicle and total control system therefor
US6009370A (en) 1993-07-26 1999-12-28 Hitachi, Ltd. Control unit for vehicle and total control system therefor
US5495242A (en) 1993-08-16 1996-02-27 C.A.P.S., Inc. System and method for detection of aural signals
US5445024A (en) 1993-09-07 1995-08-29 Riley, Jr.; Claude R. Automotive motion recorder
US5455625A (en) 1993-09-23 1995-10-03 Rosco Inc. Video camera unit, protective enclosure and power circuit for same, particularly for use in vehicles
US5422543A (en) 1993-09-27 1995-06-06 Weinberg; Stanley Flash monitor alarm system
JP3064759B2 (en) 1993-09-28 2000-07-12 株式会社日立製作所 Apparatus for monitoring surroundings of vehicle, driving support system for vehicle, and driving support apparatus
US5343527A (en) 1993-10-27 1994-08-30 International Business Machines Corporation Hybrid encryption method and system for protecting reusable software components
JP3252040B2 (en) 1993-11-19 2002-01-28 本田技研工業株式会社 Vehicle collision judgment device
US5515285A (en) 1993-12-16 1996-05-07 Car Trace, Incorporated System for monitoring vehicles during a crisis situation
JP3522317B2 (en) 1993-12-27 2004-04-26 富士重工業株式会社 Travel guide device for vehicles
US5430431A (en) 1994-01-19 1995-07-04 Nelson; Louis J. Vehicle protection system and method
US5537156A (en) 1994-03-24 1996-07-16 Eastman Kodak Company Frame buffer address generator for the mulitple format display of multiple format source video
US5497419A (en) 1994-04-19 1996-03-05 Prima Facie, Inc. Method and apparatus for recording sensor data
US5403432A (en) * 1994-06-20 1995-04-04 Burch; Teresa G. Suspendible wallpaper applicator
US5574443A (en) 1994-06-22 1996-11-12 Hsieh; Chi-Sheng Vehicle monitoring apparatus with broadly and reliably rearward viewing
IT1271654B (en) 1994-06-28 1997-06-04 Sistemi Per L Intelligenza Art METHOD AND DEVICE IN PARTICULAR SUITABLE FOR ALLOWING TO VERIFY THE CAUSES OF AN ACCIDENT IN WHICH A VEHICLE IS INVOLVED THROUGH THE IMAGES OF THE ENVIRONMENT IN WHICH IT IS LOCATED IN THE MOTORCYCLE OR PARKING STATE
JP3357749B2 (en) 1994-07-12 2002-12-16 本田技研工業株式会社 Vehicle road image processing device
US5600775A (en) 1994-08-26 1997-02-04 Emotion, Inc. Method and apparatus for annotating full motion video and other indexed data structures
BR9403037A (en) 1994-09-02 1996-09-03 Metagal Ind & Comercio Improvement together with courtesy lighting of internal rear-view mirror
US6002326A (en) 1994-09-19 1999-12-14 Valerie Turner Automotive vehicle anti-theft and anti-vandalism and anti-carjacking system
US5784007A (en) * 1994-09-27 1998-07-21 Pepper; Jeffrey W. Traffic signal sound monitor
JPH08124083A (en) 1994-10-21 1996-05-17 Toyota Motor Corp Mobile object photographing device
JPH08124069A (en) 1994-10-25 1996-05-17 Toyota Motor Corp Vehicle accident information transmitter
US5570127A (en) 1994-10-28 1996-10-29 Schmidt; William P. Video recording system for passenger vehicle
US5793420A (en) 1994-10-28 1998-08-11 Schmidt; William P. Video recording system for vehicle
US5659355A (en) 1994-10-31 1997-08-19 Eastman Kodak Company CCD dark mean level correction circuit employing digital processing and analog subtraction requiring no advance knowledge of dark mean level
US6008723A (en) 1994-11-14 1999-12-28 Ford Global Technologies, Inc. Vehicle message recording system
US6008841A (en) 1994-12-05 1999-12-28 Charlson; Reginald T. Vehicle surveillance camera system actuated upon passenger entry
US5499182A (en) 1994-12-07 1996-03-12 Ousborne; Jeffrey Vehicle driver performance monitoring system
JP2659694B2 (en) 1994-12-16 1997-09-30 山一電機株式会社 Shock vibration memory method
US6037977A (en) 1994-12-23 2000-03-14 Peterson; Roger Vehicle surveillance system incorporating remote video and data input
US5642106A (en) 1994-12-27 1997-06-24 Siemens Corporate Research, Inc. Visual incremental turn detector
US5539454A (en) 1995-02-06 1996-07-23 The United States Of America As Represented By The Administrator, National Aeronautics And Space Administration Video event trigger and tracking system using fuzzy comparators
US5717456A (en) 1995-03-06 1998-02-10 Champion International Corporation System for monitoring a continuous manufacturing process
US5689442A (en) 1995-03-22 1997-11-18 Witness Systems, Inc. Event surveillance system
US5638273A (en) 1995-03-29 1997-06-10 Remote Control Systems, Inc. Vehicle data storage and analysis system and methods
US5568211A (en) 1995-04-10 1996-10-22 Terry D. Scharton Impact activated triggering mechanism for a camera mounted in a vehicle
US5596382A (en) 1995-04-10 1997-01-21 Terry D. Scharton Impact activated triggering mechanism for a camera mounted anywhere in a vehicle
JPH08286257A (en) 1995-04-18 1996-11-01 Konica Corp Data recorder for camera
US5669698A (en) 1995-05-24 1997-09-23 Veldman; Roger L. Modular rearview mirror assembly and method for making same
US5946404A (en) 1995-06-01 1999-08-31 Silent Witness Enterprises Ltd. Audio/video surveillance and recording system
US6768944B2 (en) 2002-04-09 2004-07-27 Intelligent Technologies International, Inc. Method and system for controlling a vehicle
US6405132B1 (en) * 1997-10-22 2002-06-11 Intelligent Technologies International, Inc. Accident avoidance system
US6151065A (en) 1995-06-20 2000-11-21 Steed; Van P. Concealed integrated vehicular camera safety system
US5926210A (en) 1995-07-28 1999-07-20 Kalatel, Inc. Mobile, ground-based platform security system which transmits images that were taken prior to the generation of an input signal
US5610580A (en) 1995-08-04 1997-03-11 Lai; Joseph M. Motion detection imaging device and method
US5696705A (en) 1995-08-29 1997-12-09 Laser Technology, Inc. System and method for reconstruction of the position of objects utilizing a signal transmitting and receiving distance determining device
USD376571S (en) 1995-10-31 1996-12-17 Kokat John J Combined automobile eyeglass holder and mirror
US5667176A (en) 1995-12-04 1997-09-16 Zamarripa; Michael P. Radar detector unit mounting device for attachment to rearview mirror
US5790973A (en) 1995-12-19 1998-08-04 Prince Corporation Last exit warning system
US5797134A (en) 1996-01-29 1998-08-18 Progressive Casualty Insurance Company Motor vehicle monitoring system for determining a cost of insurance
US5825412A (en) 1996-05-20 1998-10-20 Esco Electronics Corporation Video detection apparatus for monitoring a railroad crossing
US5802545A (en) 1996-05-23 1998-09-01 Freightliner Corporation Method and system for recording vehicle data relative to vehicle standard time
US5815093A (en) 1996-07-26 1998-09-29 Lextron Systems, Inc. Computerized vehicle log
US5680123A (en) 1996-08-06 1997-10-21 Lee; Gul Nam Vehicle monitoring system
US5914748A (en) 1996-08-30 1999-06-22 Eastman Kodak Company Method and apparatus for generating a composite image using the difference of two images
JP3384939B2 (en) 1996-09-05 2003-03-10 株式会社村上開明堂 Rearview mirror with shooting function
US5798458A (en) 1996-10-11 1998-08-25 Raytheon Ti Systems, Inc. Acoustic catastrophic event detection and data capture and retrieval system for aircraft
JP2991980B2 (en) 1996-11-07 1999-12-20 三菱電機株式会社 Video recording device
JP3468001B2 (en) 1996-12-16 2003-11-17 日産自動車株式会社 Travel control device for vehicles
US5719554A (en) 1997-02-24 1998-02-17 Gagnon; Richard B. Automobile erratic behavior monitoring apparatus
US6253129B1 (en) 1997-03-27 2001-06-26 Tripmaster Corporation System for monitoring vehicle efficiency and vehicle and driver performance
US5844505A (en) 1997-04-01 1998-12-01 Sony Corporation Automobile navigation system
US5978017A (en) 1997-04-08 1999-11-02 Tino; Jerald N. Multi-camera video recording system for vehicles
US6092193A (en) 1997-05-29 2000-07-18 Trimble Navigation Limited Authentication of accumulated instrument data
US6006148A (en) 1997-06-06 1999-12-21 Telxon Corporation Automated vehicle return system
US6064792A (en) 1997-08-02 2000-05-16 Fox; James Kelly Signal recorder with deferred recording
US7088387B1 (en) 1997-08-05 2006-08-08 Mitsubishi Electric Research Laboratories, Inc. Video recording device responsive to triggering event
DE19741631B4 (en) 1997-09-20 2013-08-14 Volkswagen Ag Method and device for avoiding and / or minimizing conflict situations in road traffic
JPH11118497A (en) 1997-10-15 1999-04-30 Nissan Diesel Motor Co Ltd Vehicular monitor system
US6028528A (en) 1997-10-24 2000-02-22 Mobile-Vision, Inc. Apparatus and methods for managing transfers of video recording media used for surveillance from vehicles
US6163338A (en) 1997-12-11 2000-12-19 Johnson; Dan Apparatus and method for recapture of realtime events
US6690268B2 (en) 2000-03-02 2004-02-10 Donnelly Corporation Video mirror systems incorporating an accessory module
DE19801884A1 (en) 1998-01-20 1999-07-22 Mannesmann Vdo Ag CCTV monitoring system for blind spots around motor vehicle
US6122738A (en) 1998-01-22 2000-09-19 Symantec Corporation Computer file integrity verification
US6252544B1 (en) 1998-01-27 2001-06-26 Steven M. Hoffberg Mobile communication device
US6389340B1 (en) 1998-02-09 2002-05-14 Gary A. Rayner Vehicle data recorder
US6718239B2 (en) 1998-02-09 2004-04-06 I-Witness, Inc. Vehicle event data recorder including validation of output
WO1999040545A1 (en) 1998-02-09 1999-08-12 I-Witness, Inc. Sequential image storage system with pre-event history
US6405112B1 (en) 1998-02-09 2002-06-11 Gary A. Rayner Vehicle operator performance monitor with enhanced data retrieval capabilities
US6449540B1 (en) 1998-02-09 2002-09-10 I-Witness, Inc. Vehicle operator performance recorder triggered by detection of external waves
US5899956A (en) 1998-03-31 1999-05-04 Advanced Future Technologies, Inc. Vehicle mounted navigation device
WO1999062741A2 (en) 1998-06-01 1999-12-09 Robert Jeff Scaman Secure, vehicle mounted, incident recording system
US6895248B1 (en) 1998-06-02 2005-05-17 The Board Of Trustees Of The Leland Stanford Junior University Dynamic resource allocation and media access control for a wireless ATM network
US6011492A (en) 1998-06-30 2000-01-04 Garesche; Carl E. Vehicle warning system for visual communication of hazardous traffic conditions
NL1009775C2 (en) * 1998-07-30 2000-02-01 Univ Twente System and method for the efficient driving of a motor vehicle.
US6141611A (en) 1998-12-01 2000-10-31 John J. Mackey Mobile vehicle accident data system
KR100507789B1 (en) 1999-02-10 2005-08-17 마쯔시다덴기산교 가부시키가이샤 Reflection solid-state optical device, imaging device comprising this, video camera, and monitoring device mounted on vehicle
US6200139B1 (en) 1999-02-26 2001-03-13 Intel Corporation Operator training system
JP4287532B2 (en) 1999-03-01 2009-07-01 矢崎総業株式会社 Vehicle rear side monitoring device
US6185490B1 (en) 1999-03-15 2001-02-06 Thomas W. Ferguson Vehicle crash data recorder
DE60030114D1 (en) 1999-06-14 2006-09-28 Sun Microsystems Inc COMPUTER-ASSISTED VEHICLE NETWORK SYSTEM AND METHOD
US6885920B2 (en) 1999-07-30 2005-04-26 Oshkosh Truck Corporation Control system and method for electric vehicle
DE19947766A1 (en) 1999-10-02 2001-05-10 Bosch Gmbh Robert Device for monitoring the surroundings of a parking vehicle
US20050021197A1 (en) 1999-12-06 2005-01-27 Zimmerman Kelly L. Methods and systems for communicating vehicle data
US6611755B1 (en) 1999-12-19 2003-08-26 Trimble Navigation Ltd. Vehicle tracking, communication and fleet management system
DE10007218B4 (en) 2000-02-17 2009-11-26 Robert Bosch Gmbh Method for event interpretation and issuing of operating instructions in motor vehicles
JP3672793B2 (en) 2000-04-06 2005-07-20 三菱電機株式会社 DSRC OBE
US20020111725A1 (en) 2000-07-17 2002-08-15 Burge John R. Method and apparatus for risk-related use of vehicle communication system data
JP2002042288A (en) 2000-07-26 2002-02-08 Yazaki Corp Running state recording device and running control system using it
US7143171B2 (en) 2000-11-13 2006-11-28 Telefonaktiebolaget Lm Ericsson (Publ) Access point discovery and selection
DE10102771A1 (en) 2001-01-23 2002-07-25 Bosch Gmbh Robert Motor vehicle object distance and relative speed signal provision device, generates function-specific output signals which are stored in memory
US7143353B2 (en) 2001-03-30 2006-11-28 Koninklijke Philips Electronics, N.V. Streaming video bookmarks
EP1256919A3 (en) 2001-05-11 2003-11-05 KS Telecom Co., Ltd. Vehicle management system using mobile communication terminal
US7100190B2 (en) 2001-06-05 2006-08-29 Honda Giken Kogyo Kabushiki Kaisha Automobile web cam and communications system incorporating a network of automobile web cams
US6714894B1 (en) 2001-06-29 2004-03-30 Merritt Applications, Inc. System and method for collecting, processing, and distributing information to promote safe driving
US7119832B2 (en) 2001-07-23 2006-10-10 L-3 Communications Mobile-Vision, Inc. Wireless microphone for use with an in-car video system
US6559769B2 (en) 2001-10-01 2003-05-06 Eric Anthony Early warning real-time security system
US8301108B2 (en) 2002-11-04 2012-10-30 Naboulsi Mouhamad A Safety control system for vehicles
US20030080878A1 (en) 2001-10-30 2003-05-01 Kirmuss Charles Bruno Event-based vehicle image capture
US20030081122A1 (en) 2001-10-30 2003-05-01 Kirmuss Charles Bruno Transmitter-based mobile video locating
US7415670B2 (en) * 2001-11-19 2008-08-19 Ricoh Co., Ltd. Printer with audio/video localization
US6873261B2 (en) 2001-12-07 2005-03-29 Eric Anthony Early warning near-real-time security system
US6679702B1 (en) 2001-12-18 2004-01-20 Paul S. Rau Vehicle-based headway distance training system
EP1324274A3 (en) 2001-12-28 2005-11-02 Matsushita Electric Industrial Co., Ltd. Vehicle information recording system
US7262790B2 (en) 2002-01-09 2007-08-28 Charles Adams Bakewell Mobile enforcement platform with aimable violation identification and documentation system for multiple traffic violation types across all lanes in moving traffic, generating composite display images and data to support citation generation, homeland security, and monitoring
AU2002252630A1 (en) 2002-02-08 2003-09-02 David Lively Centralized digital video recording system with bookmarking and playback from multiple locations
WO2003074326A1 (en) 2002-03-07 2003-09-12 Nice Systems Ltd. Method and apparatus for internal and external monitoring of a transportation vehicle
DE10210973A1 (en) 2002-03-13 2003-09-25 Bosch Gmbh Robert Method for recording operational data from a motor vehicle, e.g. for use with an electronic log book, involves generating command sequences which are used to control a monitoring unit when processed within its computer
JP4416374B2 (en) 2002-03-26 2010-02-17 富士通株式会社 Insurance premium setting method, insurance premium setting program, and insurance premium setting device
US6950122B1 (en) 2002-04-08 2005-09-27 Link Communications, Ltd. Integrated video data capture system
EP1355278A1 (en) 2002-04-18 2003-10-22 Logosystem S.p.A. A computerized system for managing motor-vehicle maintenance
NO317200B1 (en) 2002-08-09 2004-09-13 Best Practice Deployment As Traffic training system in a vehicle
US6795759B2 (en) 2002-08-26 2004-09-21 International Business Machines Corporation Secure logging of vehicle data
US20050185936A9 (en) 2002-11-08 2005-08-25 Ich-Kien Lao Mobile and vehicle-based digital video system
US7792690B2 (en) * 2002-11-27 2010-09-07 Computer Sciences Corporation Computerized method and system for estimating an effect on liability of the speed of vehicles in an accident and time and distance traveled by the vehicles
US6853919B2 (en) 2003-02-04 2005-02-08 General Motors Corporation Method for reducing repeat false alarm indications in vehicle impact detection systems
GB2421824A (en) 2003-09-29 2006-07-05 Micro News Network Llc Information acquisition and distribution system
US7023333B2 (en) 2003-10-22 2006-04-04 L-3 Communications Mobile Vision, Inc. Automatic activation of an in-car video recorder using a vehicle speed sensor signal
US20070143499A1 (en) 2003-12-30 2007-06-21 Ting-Mao Chang Proximity triggered job scheduling system and method
US7246009B2 (en) 2004-02-02 2007-07-17 Glacier Northwest, Inc. Resource management system, for example, tracking and management system for trucks
US7983835B2 (en) 2004-11-03 2011-07-19 Lagassey Paul J Modular intelligent transportation system
US20060007151A1 (en) 2004-06-08 2006-01-12 Pranil Ram Computer Apparatus with added functionality
US7379805B2 (en) 2004-07-14 2008-05-27 United Parcel Service Of America, Inc. Wirelessly enabled trailer locking/unlocking
US7089099B2 (en) 2004-07-30 2006-08-08 Automotive Technologies International, Inc. Sensor assemblies
US20060040239A1 (en) 2004-08-02 2006-02-23 J. J. Keller & Associates, Inc. Driving simulator having articial intelligence profiles, replay, hazards, and other features
US7695282B2 (en) 2004-09-03 2010-04-13 Gold Cross Safety Corp. Driver safety program
US20060053038A1 (en) 2004-09-08 2006-03-09 Warren Gregory S Calculation of driver score based on vehicle operation
US20060055521A1 (en) 2004-09-15 2006-03-16 Mobile-Vision Inc. Automatic activation of an in-car video recorder using a GPS speed signal
ES2391566T3 (en) 2004-10-29 2012-11-27 Skyhook Wireless, Inc. Database and location beacon server, method to build a location beacon database, and location-based service that uses it
CA2587740A1 (en) 2004-11-03 2006-05-11 Thomas Dewaal Method system, and apparatus for monitoring vehicle operation
US7348895B2 (en) 2004-11-03 2008-03-25 Lagassey Paul J Advanced automobile accident detection, data recordation and reporting system
US20060161960A1 (en) 2005-01-20 2006-07-20 Benoit Brian V Network security system appliance and systems based thereon
JP2006199204A (en) 2005-01-21 2006-08-03 Sanyo Electric Co Ltd Drive recorder and control method therefor
US20060212195A1 (en) 2005-03-15 2006-09-21 Veith Gregory W Vehicle data recorder and telematic device
AU2006256372B2 (en) 2005-06-09 2009-10-22 Greenroad Driving Technologies Ltd. System and method for displaying a driving profile
US7768548B2 (en) 2005-08-12 2010-08-03 William Bradford Silvernail Mobile digital video recording system
US7593963B2 (en) 2005-11-29 2009-09-22 General Electric Company Method and apparatus for remote detection and control of data recording systems on moving systems
US8842197B2 (en) * 2005-11-30 2014-09-23 Scenera Mobile Technologies, Llc Automatic generation of metadata for a digital image based on ambient conditions
US10878646B2 (en) 2005-12-08 2020-12-29 Smartdrive Systems, Inc. Vehicle event recorder systems
US20070135979A1 (en) 2005-12-09 2007-06-14 Smartdrive Systems Inc Vehicle event recorder systems
US20070150140A1 (en) 2005-12-28 2007-06-28 Seymour Shafer B Incident alert and information gathering method and system
WO2007109162A2 (en) 2006-03-17 2007-09-27 Viddler, Inc. Methods and systems for displaying videos with overlays and tags
US20070241874A1 (en) 2006-04-17 2007-10-18 Okpysh Stephen L Braking intensity light
US7804426B2 (en) 2006-05-08 2010-09-28 Drivecam, Inc. System and method for selective review of event data
US20070257782A1 (en) 2006-05-08 2007-11-08 Drivecam, Inc. System and Method for Multi-Event Capture
US7671728B2 (en) 2006-06-02 2010-03-02 Sensormatic Electronics, LLC Systems and methods for distributed monitoring of remote sites
EP2097846A1 (en) 2006-11-22 2009-09-09 Solidica Inc. Diagnostic and telematic system
US7792328B2 (en) 2007-01-12 2010-09-07 International Business Machines Corporation Warning a vehicle operator of unsafe operation behavior based on a 3D captured image stream

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6246933B1 (en) * 1999-11-04 2001-06-12 BAGUé ADOLFO VAEZA Traffic accident data recorder and traffic accident reproduction system and method
US6408232B1 (en) * 2000-04-18 2002-06-18 Agere Systems Guardian Corp. Wireless piconet access to vehicle operational statistics
US20030154009A1 (en) * 2002-01-25 2003-08-14 Basir Otman A. Vehicle visual and non-visual data recording system
US20040103008A1 (en) * 2002-11-27 2004-05-27 Stefan Wahlbin Computerized method and system for estimating liability for an accident from an investigation of the accident

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9610955B2 (en) 2013-11-11 2017-04-04 Smartdrive Systems, Inc. Vehicle fuel consumption monitor and feedback systems
EP3009990A1 (en) * 2014-10-18 2016-04-20 Tata Consultancy Services Limited Method and system for performing crash analysis of one or more vehicles
US9663127B2 (en) 2014-10-28 2017-05-30 Smartdrive Systems, Inc. Rail vehicle event detection and recording system
US20160247538A1 (en) * 2015-02-25 2016-08-25 Industrial Technology Research Institute Event reconstruction system and method thereof
TWI582724B (en) * 2015-02-25 2017-05-11 財團法人工業技術研究院 Event reconstruction system and method

Also Published As

Publication number Publication date
US20180130012A1 (en) 2018-05-10
US20070271105A1 (en) 2007-11-22
US9836716B2 (en) 2017-12-05
WO2007133992A3 (en) 2008-05-08
US10235655B2 (en) 2019-03-19

Similar Documents

Publication Publication Date Title
US10235655B2 (en) System and method for reducing driving risk with hindsight
US7659827B2 (en) System and method for taking risk out of driving
US8564446B2 (en) System and method for reducing driving risk with foresight
US20070268158A1 (en) System and Method for Reducing Driving Risk With Insight
US20210407015A1 (en) Methods of determining accident cause and/or fault using telematics data
US9275090B2 (en) System and method for identifying non-event profiles
US8854199B2 (en) Driver risk assessment system and method employing automated driver log
US8463487B2 (en) Systems and methods for complex event processing based on a hierarchical arrangement of complex event processing engines
US20140358394A1 (en) Jolt and Jar Recorder System and Methods of Use Thereof
CN108074396A (en) The evaluation method that drives safely and system
KR20090040622A (en) Method and apparatus for providing vehicle accident information
US20210409651A1 (en) Highway Infrastructure Inventory and Assessment Device
US20240029576A1 (en) Systems and methods for delivering vehicle-specific educational content for a critical event
WO2011019706A1 (en) Systems and methods for complex event processing of vehicle information and image information relating to a vehicles
US9792319B2 (en) System and method for identifying non-event profiles
KR102295427B1 (en) System and method for detecting status of vehicle based on data collected by obd
US20230319524A1 (en) Collaborative monitoring of location conditions
AU2010282634B2 (en) Systems and methods for complex event processing of vehicle information and image information relating to a vehicles

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07761938

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07761938

Country of ref document: EP

Kind code of ref document: A2