System and method for identifying non-event profiles
View Patent ↗Valid driving events and non-events are identified, and detailed information is stored for valid events. Valid events are those captured driving events that are essential to testing of a driver's risky behavior. Remaining captured events which are not identified as involving risky behavior are non-events. At least one event capture device captures location, trigger force, images, and other information that collectively comprise an event. An event detector compares the captured event data to previously created non-event profiles and determines whether the captured event is a non-event. An abbreviated record is created for each identified non-event. For valid driving events, detailed driving event records are created. The records are stored at an evaluation server and are accessible to an analysis station for scoring and review.
1. A system for identifying non-event profiles, comprising:
an event detector communicatively coupled with a vehicle, configured to capture driving events, store captured driving event data and receive non-event profiles;
at least one event capture device associated with the event detector for capturing the driving events;
a non-event profile module configured to compare non-event profiles with captured driving event data and to determine when a captured driving event is a non-event corresponding to a non-event profile based on the comparison of said captured driving event data to the non-event profiles; and
an event record creating module for creating a driving event record for each captured driving event not identified as a non-event by the non-event profile module.
2. The system of claim 1 , further comprising an abbreviated record module configured to create an abbreviated record for captured driving event data identified as a non-event.
3. The system of claim 1 , further comprising an evaluation server configured to receive driving event records from the event detector and to identify when a driving event record corresponds to a non-event.
4. The system of claim 3 , wherein the evaluation server is further configured to create a non-event profile in response to identification of a non-event, and to send non-event profiles to the event detector.
5. The system of claim 3 , wherein the evaluation server identifies the driving event as a non-event when the driving event record indicates a predetermined vertical axis force is in a trigger force range.
6. The system of claim 3 , wherein the evaluation server further comprises an abbreviated record module configured to receive abbreviated records from the event detector and to count the number of times an abbreviated record corresponding to each non-event profile is received.
7. The system of claim 6 , wherein the evaluation server further comprises an avoidance record module configured to create an avoidance record for a non-event when the number of abbreviated records corresponding to the non-event profile for the identified non-event exceeds a predetermined value.
8. The system of claim 7 , wherein the avoidance record comprises at least location information.
9. The system of claim 7 , wherein the evaluation server further comprises a plot generating module configured to generate frequency and location plots to indicate driving locations to be avoided, the plots being based on the driving event records, the non-event profiles, the avoidance records and the abbreviated records.
10. The system of claim 7 , wherein the evaluation server is further configured to remove the non-event profile, the abbreviated records and the avoidance record for the non-event when the non-event has expired.
11. The system of claim 1 , wherein the event capture device comprises a global positioning system unit.
12. The system of claim 1 , wherein the event capture device comprises a g-force sensing system for sensing g-forces along perpendicular x, y and z axes, wherein a g-force trigger measured along a vertical axis is a negative trigger.
13. The system of claim 12 , wherein the evaluation server is configured to identify a driving event as a non-event if the driving event data includes a negative trigger.
14. The system of claim 1 , comprising a plurality of said event capture devices associated with the event detector, the event capture devices comprising at least a timer for capturing event time information, a location sensing unit for capturing location information, a speed detecting unit for capturing speed information, and a video camera for capturing video data.
15. The system of claim 14 , wherein the event capture devices further comprise a g-force sensing system for capturing three axis g-force information.
16. A method for identifying non-event profiles, comprising:
capturing driving event data at an event detector;
determining whether captured driving event data corresponds to a non-event, by evaluating the driving event data and determining that there was no driver fault associated with the event to which said captured driving event data is related;
creating a driving event record for any captured driving event data which is not determined to correspond to a non-event;
creating an abbreviated record for any captured driving event data which is determined to be a non-event; and
sending driving event records and abbreviated records from the event detector to an evaluation server.
17. The method of claim 16 , wherein creating an abbreviated record for the non-event comprises saving at least location information and information identifying the range of trigger force equating to the non-event.
18. The method of claim 16 , wherein creating a driving event record comprises saving at least event time information, speed information, location information, range of trigger force information, and video data for the driving event and storing the information in the driving event record.
19. The method of claim 16 , further comprising creating and storing a non-event profile for any detected non-event, wherein the non-event profile comprises at least a unique identifier, location information and range of trigger force information.
20. The method of claim 19 , wherein the step of determining whether captured driving event data corresponds to a non-event comprises comparing the captured driving event data to stored non-event profiles and determining whether the captured driving event data corresponds to any stored non-event profile.
21. The method of claim 16 , further comprising evaluating driving event records received at the evaluation server and determining if a driving event record is a non-event, creating a non-event profile at the evaluation server for any non-event identified in said driving event records, sending each non-event profile to the event detector, and storing non-event profiles at the event detector, and the step of determining whether captured driving event data corresponds to a non-event comprises determining whether the captured driving event data corresponds to any stored non-event profile.
22. The method of claim 21 , wherein determining that driving event data corresponds to a non-event comprises determining whether a trigger force stored in the driving event record corresponds to a vertical trigger force exceeding a predetermined value.
23. The method of claim 21 , further comprising associating each abbreviated record with a unique identifier for the corresponding non-event profile, and counting the number of abbreviated records received for each unique identifier.
24. The method of claim 23 , further comprising creating an avoidance record for a non-event when the abbreviated record count for the unique identifier associated with the non-event exceeds a predetermined number, wherein the avoidance record comprises location information and trigger force range information.
25. The method of claim 24 , further comprising identifying a non-event that has expired; and
removing a non-event profile, an avoidance record and abbreviated records for the expired non-event.
26. The method of claim 24 , further comprising generating frequency and location plots from the non-event profiles, the avoidance records and the abbreviated records, wherein the frequency and location plots indicate driving locations to be avoided.
27. The method of claim 24 , further comprising selling at least the avoidance records to a third party.