Vehicle Text-Cell Sensor

• US 20130253760A1
• Filed: 12/07/2012
• Published: 09/26/2013
• Est. Priority Date: 12/08/2011
• Status: Abandoned Application

• Current Assignee: Kenneth Alvin Hosfeld, Michael J. Berman
• Original Assignee: Kenneth Alvin Hosfeld, Michael J. Berman
• Inventors: Berman, Michael J., Hosfeld, Kenneth Alvin
• Application Number:
  US13/708,907
• Publication Number:
  US 20130253760A1
• Time in Patent Office: Days
• US Class Current: 701/32.2
• CPC Class Codes: G07C 5/08 Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
• CPC Class Codes: G07C 5/0841 Registering performance data recording measured values G01D; information storage G11B

Abstract

A multi-port, multi access system that allows for any automotive impact to register exact time and quadrant of impact in a way that will allow it to be cross referenced to the driver'"'"'s (of one or more vehicles) mobile cellular telephone usage at the time impact occurred, as an aid in determining and assigning accident responsibility.

Claims

1. A device that logs the date and time of any collision or impact consisting of:

a cpu with tamperproof clock;

a battery backup;

nonvolatile and tamper resistant memory that securely stores an event log consisting, at a minimum, of the exact date and time of any impacts or collisions that are detected by the attached sensors;

an input for external power from the vehicles power system;

a secure data extraction port that allows the secure transfer of the event log;

a programming and/or test port;

a status light indicating the device is on;

a status light indicating the device is correctly functioning;

a status light indicating an impact event has occurred;

one or more acceleration/inertia and/or impact sensors, said sensors may be any combination of built-in and/or externally mounted and connected utilizing wired, wireless or fiber optic mechanisms.

2. Device of claim one further comprising an OBD-II data logger port used to obtain vehicle status information such as speed, throttle position, status of breaks, etc.

6. Device of claim two further comprising a wide band receiver capable of detecting the presence of near field radio in the proximity of the driver.

7. Device of claim two further comprising additional status indicator light or lights as necessary.

8. Device of claim two that upon detection attempts to tamper or intrude cause an event log include date and time of event.

12. Device of claim 6 further comprising additional status indicator light or lights as necessary.

13. Device of claim 6 that upon detection attempts to tamper or intrude cause an event log include date and time of event.

3. Device of claim one further comprising a wide band receiver capable of detecting the presence of near field radio in the proximity of the driver.

9. Device of claim three further comprising additional status indicator light or lights as necessary.

10. Device of claim three that upon detection attempts to tamper or intrude cause an event log include date and time of event.

14. Device of claim 9 that upon detection attempts to tamper or intrude cause an event log include date and time of event.

4. Device of claim one further comprising additional status indicator light or lights as necessary.

11. Device of claim four that upon detection attempts to tamper or intrude cause an event log include date and time of event.

5. Device of claim one that upon detection attempts to tamper or intrude cause an event log include date and time of event.

15. Device of 12 that upon detection attempts to tamper or intrude cause an event log include date and time of event.

16. A system that logs the date and time of any collision or impact consisting of:

a software program;

nonvolatile and tamper resistant memory that securely stores an event log consisting, at a minimum, of the exact date and time of any impacts or collisions that are detected by available sensors;

said system having a means to securely transfer or extract the event log;

17. A system of claim 16 that can operate in a smartphone.

18. A system of claim 17 that automatically starts when the smartphone is powered on.

19. A system of claim 18 that automatically restarts whenever the software exits.

20. A system of claim 17 that logs date and time of phone use in the event queue.

21. A system of claim 17 that logs date and time of send and received text messages in the event queue.

22. A system of claim 18 that logs date and time of phone use in the event queue.

23. A system of claim 18 that logs date and time of send and received text messages in the event queue.

24. A system of claim 19 that logs date and time of phone use in the event queue.

25. A system of claim 19 that logs date and time of send and received text messages in the event queue.