SYSTEM COUPLED TO VEHICULAR COMPUTING DEVICES AND SENSORS FOR MONITORING AND VERIFYING USAGE OF THE ASSOCIATED VEHICLE
20210056777 ยท 2021-02-25
Inventors
Cpc classification
G07C5/02
PHYSICS
B60R21/16
PERFORMING OPERATIONS; TRANSPORTING
G07C5/0816
PHYSICS
International classification
G07C5/02
PHYSICS
Abstract
A vehicular verification system is provided. The vehicular verification system couplable to the computer and sensors of a vehicle for monitoring and verifiable reporting events associated with the history and driving conditions of the vehicle. The vehicular verification system is programmable to establish thresholds for a plurality of such vehicular events, wherein for each vehicular event the vehicular verification system monitors related hardware components and sensors for values in excess of the associated threshold. The vehicular verification system is adapted to produce a usage report of all values in excess of the associated threshold for verifiably ascertaining the history and driving conditions of the vehicle.
Claims
1. A vehicular verification system, comprising: a vehicle having a plurality of hardware components; a computer; each hardware component electrically connected to the computer by way of at least one sensor; a programmable vehicular verification system couplable to said computer, the vehicular verification system configured to: associate each sensor with one or more event types; selectively establish a value threshold for each event type; repeatedly compare a sensed value of each sensor against the respective value threshold; and on-demand generation of a report of each event type comprising a threshold event each time the sensed value exceeds the respective value threshold.
2. The vehicular verification system of claim 1, comprising one or more databases coupled to the vehicular verification system for retrievably storing each event type and associated sensed values, the associated threshold values and the associated threshold events.
3. The vehicular verification system of claim 1, wherein a threshold event is determined by comparing the sensed value against an immediately previous sensed value.
4. The vehicular verification system of claim 1, wherein the one or more event types comprises an engine speed of an engine of the vehicle.
5. The vehicular verification system of claim 1, wherein the one or more event types comprises an airbag deployment speed of an airbag of the vehicle.
6. The vehicular verification system of claim 1, wherein the one or more event types comprises a toggling of windshield wipers of the vehicle.
7. The vehicular verification system of claim 1, wherein the one or more event types comprises a brake pressure of brakes the vehicle.
8. The vehicular verification system of claim 1, wherein the one or more event types comprises an overheating of an engine of the vehicle.
9. The vehicular verification system of claim 1, wherein the one or more event types comprises a usage of a throttle of the vehicle.
10. The vehicular verification system of claim 1, wherein the one or more event types comprises an oil pressure of the vehicle.
11. The vehicular verification system of claim 1, wherein the one or more event types comprises of a gear change of a plurality of gears of the vehicle.
12. The vehicular verification system of claim 1, wherein the one or more event types comprises of a start of an engine of the vehicle.
13. The vehicular verification system of claim 1, wherein the one or more event types comprises of an engagement of an anti-lock braking system of the vehicle.
14. A vehicular verification system, comprising: a vehicle having a plurality of hardware components; a computer; each hardware component electrically connected to the computer by way of at least one sensor; a programmable vehicular verification system couplable to said computer, the vehicular verification system configured to: associate each sensor with one or more event types; selectively establish a value threshold for each event type; repeatedly compare a sensed value of each sensor against the respective value threshold; and on-demand generation of a report of each event type comprising a threshold event each time the sense value exceeds the respective value threshold; one or more databases coupled to the vehicular system for retrievably storing each event type and associated sensed values, associated threshold values and associated threshold events, wherein the one or more event types comprises: an engine speed of an engine of the vehicle; an airbag deployment speed of an airbag of the vehicle; a toggling of windshield wipers of the vehicle; a brake pressure of brakes the vehicle; and overheating of the engine of the vehicle; a usage of a throttle of the vehicle; an oil pressure of the vehicle; a gear change of a plurality of gears of the vehicle; a start of an engine of the vehicle; and an engagement of an anti-lock braking system of the vehicle.
15. The vehicular verification system of claim 14, wherein the one or more database will be backed up to the cloud periodically to prevent tampering with the threshold events.
16. The vehicular verification system of claim 14, wherein a threshold event is determined by comparing the sensed value against an immediately previous sensed value.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0011]
[0012]
[0013]
[0014]
[0015]
DETAILED DESCRIPTION OF THE INVENTION
[0016] The following detailed description is of the best currently contemplated modes of carrying out exemplary embodiments of the invention. The description is not to be taken in a limiting sense, but is made merely for the purpose of illustrating the general principles of the invention, since the scope of the invention is best defined by the appended claims.
[0017] Broadly, an embodiment of the present invention provides a vehicular verification system couplable to the computer and sensors of a vehicle for monitoring verifiable reporting event types associated with the history and driving conditions of the vehicle. The vehicular verification system is programmable to establish thresholds for a plurality of such vehicular event types, wherein for each vehicular event type the vehicular verification system monitors related hardware components and/or sensors for values with respect to the associated thresholds and in some cases there are multiple thresholds for example speed increase from less than 10 mph to 10 mph is an event and speed increase from less than 15 mph to greater than 15 mph is an event. The vehicular verification system is adapted to produce a usage report of all values regarding the associated thresholds for verifiably ascertaining the history and driving conditions of the vehicle.
[0018] Referring to
[0019] The vehicular verification system may include inputs (hardware components), logic, one or more coupled databases, and report output functionality. For example, when the gas pedal is depressed more than a certain amount (the threshold) the program will insert a record into a relevant database, such as an event-history database. The event-history database is adapted to produce an event-history table containing a list of all the event types with their corresponding thresholds and associated input data.
[0020] Referring to
TABLE-US-00001 Event types key description Threshold Unit of Measure Engine Speed 1000 RPM Airbags deployed TRUE Deployed Windshield wipers Toggled Minutes Brake pressure 5 PSI Overheat 130 Degrees Throttle usage 25 % to the floor Low oil pressure 5 PSI Gear changes 1 Gear Start engine 1 Occurrence Stop engine 1 Occurrence Roadside assistance 1 Occurrence Speed 5 MPH ABS engaged 1 Occurrence Bucking TRUE/FALSE
[0021]
[0022] Referring to
[0023] The program product may be written in Java, in which case a JRE would be required. MySQL database will be used for the database(s). All files may be copied onto a chip which will be placed into the vehicle. The vehicular verification system may be coupled to the car's main computer via a standard interface. A display could be added to view the report from inside the vehicle, but otherwise the report can be exported via email or the like.
[0024] A method of using the present invention may include the following. The vehicular verification system disclosed above may be provided. A user-owner of a vehicle coupled to the vehicular verification system may generate the output TrUsage report, for instance when selling said vehicle. Likewise, the owner can use this information when composing an advertisement. Additionally, the present invention can also be used for boats and other motor vehicles that have sensors. The computer-based data processing system and method described above is for purposes of example only, and may be implemented in any type of computer system or programming or processing environment, or in a computer program, alone or in conjunction with hardware. The present invention may also be implemented in software stored on a computer-readable medium and executed as a computer program on a general purpose or special purpose computer. For clarity, only those aspects of the system germane to the invention are described, and product details well known in the art are omitted. For the same reason, the computer hardware is not described in further detail. It should thus be understood that the invention is not limited to any specific computer language, program, or computer. It is further contemplated that the present invention may be run on a stand-alone computer system, or may be run from a server computer system that can be accessed by a plurality of client computer systems interconnected over an intranet network, or that is accessible to clients over the Internet. In addition, many embodiments of the present invention have application to a wide range of industries. To the extent the present application discloses a system, the method implemented by that system, as well as software stored on a computer-readable medium and executed as a computer program to perform the method on a general purpose or special purpose computer, are within the scope of the present invention. Further, to the extent the present application discloses a method, a system of apparatuses configured to implement the method are within the scope of the present invention.
[0025] It should be understood, of course, that the foregoing relates to exemplary embodiments of the invention and that modifications may be made without departing from the spirit and scope of the invention as set forth in the following claims.