RELATED APPLICATION

Benefit is claimed to India Provisional Application No. 4045/CHE/2010, titled "SYSTEM AND METHOD FOR AUTHENTICATING A DRIVER OF A VEHICLE" by Shanmugasundaram Murugesan, et Al., filed on 31st December 2010, which is herein incorporated in its entirety by reference for all purposes.

FIELD OF THE INVENTION

The present invention relates to the field of vehicle security systems, and more particularly relates to authentication of a driver and communication of vehicle data.

BACKGROUND OF THE INVENTION

The widespread usage of motor vehicles for both personal and work related activities places millions of vehicles on roads each day with their operation being largely unmonitored. Equally, stealing of vehicles is also increasing day by day. Various antitheft devices have conventionally been proposed to prevent the robbery and theft of vehicles. Some of the techniques used to prevent the theft of vehicles include locking systems, tracking of vehicles using GPS etc. In these techniques, vehicle's various parameters like speed, direction are considered for monitoring the vehicle.

To achieve the monitoring a driver of a vehicle, many types of anti-theft apparatuses are being introduced that permits the driver to start the vehicle only after authentication of the driver. These apparatus consume extra space in the vehicle and may not be efficient in communicating with an on-board diagnostics present in the vehicle.

SUMMARY OF THE INVENTION

The present invention provides a driver authentication and vehicle data communication apparatus. In one aspect, a vehicular system includes an identity dongle having information associated with a driver of a vehicle, a vehicle charger adapted for receiving the identity dongle, a on-board diagnostic (OBD) unit connected to the vehicle charger via a battery line, where the OBD unit is configured for authenticating the driver of the vehicle based on the driver information in the identity dongle, and where the OBD unit is configured for providing a signal to an Engine Control Unit (ECU) upon successfully authenticating the driver.

The OBD unit is configured for obtaining vehicle data from the ECU, processing the vehicle data obtained from the ECU, and communicating the vehicle data to the identity dongle. The identity dongle is configured for storing the vehicle data received from the OBD unit and transmitting the stored vehicle data to a backend server via a communication channel.

In another aspect, a device includes at least one port adapted to connect a vehicle charger of vehicle, a processor coupled to the port, a memory unit coupled to the processor, where the memory unit includes information associated with a driver of the vehicle, and where the memory unit includes instructions stored therein that when executed by the processor, cause the processor to perform steps which includes performing a search for authentication devices connected to the vehicle charger via a battery line when plugged into the vehicle charger port, connecting to one of authentication devices coupled to the vehicle charger, and providing the information associated with the driver to the connected authentication device so that the authentication device authenticates the driver based on the information associated with the driver.

Other features of the embodiments will be apparent from the accompanying drawings and from the detailed description that follows.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

Figure 1 is a schematic diagram of a vehicular system for authenticating a driver of a vehicle using an identity dongle and communicating vehicle data to a backend server via the identity dongle, according to one embodiment.

Figure 2 is a block diagram showing various components of an identity dongle such as those shown in Figure 1, according to one embodiment.

The drawings described herein are for illustration purposes only and are not intended to limit the scope of the present disclosure in any way.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides a driver authentication and vehicle data communication apparatus. In the following detailed description of the embodiments of the invention, reference is made to the accompanying drawings that form a part hereof and in which are shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.

Figure 1 is a schematic diagram of a vehicular system 100 for authenticating a driver of a vehicle using an identity dongle 102 and communicating vehicle data to a backend server 110 via the identity dongle 102, according to one embodiment. In Figure 1, the system includes an identity dongle 102, a vehicle charger 104, an on-board diagnostic (OBD) unit 106, an engine control unit (ECU) 108.

The identity dongle 102 is a device storing information associated with a driver of a vehicle (not shown). The information of the driver may include name of the driver, address of the driver, a unique identifier assigned to the driver and vehicle identification number, the like. As shown in Figure 1, the vehicle charger 104 in the dashboard of the vehicle is adapted to receive the identity dongle 102. The OBD unit 106 is coupled to the vehicle charger 104 via a battery line 112. Also, the OBD unit 106 is connected to the engine control unit (ECU) 108.

When the driver of the vehicle carrying the identity dongle 102 plugs the identity dongle 102 in the vehicle charger 104, the identity dongle 102 search for devices connected to the vehicle charger 104 for authenticating the driver. The identity dongle 102 latches with one of the devices found during the search. For the purpose of illustration, the device to which the identity dongle 102 is considered as the OBD unit 106.

Upon connecting with the identity dongle 102, the OBD unit 106 retrieves the information associated with the driver from the identity dongle 102 via the battery line 112. The OBD unit 106 determines whether the retrieved information matches with information stored in it. The stored information includes information associated with one or more drivers who are allowed to driver a particular vehicle. If the information matches, the OBD unit 106 authenticates the driver of the vehicle and provides a signal to the ECU 108 that the driver of the vehicle is authenticated to use the vehicle. Accordingly, the ECU 108 starts vehicle engine when the driver initiates ignition of the vehicle engine.

When the engine is running, the OBD unit 104 obtains vehicle data (e.g., vehicle speed, intake air temperature, revolutions per minute, manifold air pressure, manifold air flow and so on) associated with the vehicle from the ECU 108. The OBD unit 104 processes the vehicle data and communicates the vehicle data to the identity dongle 102 via the battery line 112. The identity dongle 102 stores the vehicle data received via the battery line 112. In one embodiment, the identity dongle 102 transmits the vehicle data collected in real-time to the backend server 110 via a communication channel. In another embodiment, the identity dongle 102 pairs with a handheld device (e.g., mobile phone of the driver) via a communication channel (e.g., Bluetooth) and shares the vehicle data stored in the identity dongle 102. Accordingly, the handheld device transmits the vehicle data to the backend server 110 via a communication channel. In yet another embodiment, the identity dongle 102 stores the vehicle data in a removable storage device so that the driver can transfer the vehicle data in a computing device (e.g., laptop, smart phone, etc.) through the removable storage device once the trip is over. The driver can then send the vehicle data to the backend server 110 using the Internet. The backend server 110 processes the vehicle data to compute driver rating, green index and so on. Also, the backend server 110 can locate geographical location of the vehicle using a GPS module installed in the identity dongle 102.

Figure 2 is a block diagram showing various components of the identity dongle 102 such as those shown in Figure 1, according to one embodiment. The identity dongle includes a port 202, a processor 204 is coupled to the port 202, a memory unit 206 coupled to the processor 204, and a transceiver 208.

The port 202 is adapted to connect the vehicle charger 104 of the vehicle. The memory unit 206 includes information 214 associated with a driver of the vehicle. Also, the memory unit 206 includes instructions 212 stored therein that when executed by the processor 204, cause the processor 204 to perform following steps.

In one embodiment, the processor 204 performs a search for authentication devices connected to the vehicle charger 104 via the battery line 112 when plugged the identity dongle 102 is into the vehicle charger 104. The processor 204 connects the identity dongle 102 to the OBD unit 106 coupled to the vehicle charger 104. Then, the processor 204 provides the information 214 associated with the driver to the OBD unit 104 so that the OBD unit 104 authenticates the driver based on the information 214 associated with the driver.

In another embodiment, the processor 204 receives vehicle data 216 associated with the vehicle from the OBD unit 106 and stores the vehicle data 216 associated with the vehicle. In one exemplary implementation, the transceiver 208 transmits the stored vehicle data 216 to the backend server 110 via a communication channel. In another exemplary implementation, the transceiver 208 transmits the stored vehicle data 216 to a handheld device (e.g., mobile device of the driver). In yet another exemplary implementation, the port 202 is adapted to behave as a USB port and transfer the vehicle data 216 to a computing device (e.g., laptop, smart phone, etc.) so that the vehicle data 216 is communicated to the backend server 110 via the Internet. The identity dongle 102 also includes a GPS module 210 configured for determining geo-positioning system coordinates associated with the location of the vehicle and communicating the GPS coordinates to the backend server 110.

The present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. Furthermore, the various devices, modules, selectors, estimators, and the like described herein may be enabled and operated using hardware circuitry, for example, complementary metal oxide semiconductor based logic circuitry, firmware, software and/or any combination of hardware, firmware, and/or software embodied in a machine readable medium. For example, the various electrical structure and methods may be embodied using transistors, logic gates, and electrical circuits, such as application specific integrated circuit.

We Claim:

1. A vehicular system comprising:
an identity dongle having information associated with a driver of a vehicle;
a vehicle charger adapted for receiving the identity dongle;
a on-board diagnostic (OBD) unit connected to the vehicle charger via a battery line, wherein the OBD unit is configured for authenticating the driver of the vehicle based on the driver information in the identity dongle, and wherein the OBD unit is configured for providing a signal to an Engine Control Unit (ECU) upon successfully authenticating the driver.

2. The system of claim 1, wherein the identity dongle is configured for:
performing a search for devices connected to the vehicle charger when
plugged into the vehicle charger port; and
connecting to one of devices coupled to the vehicle charger, wherein the one of devices found during the search operation comprises an OBD unit.

3. The system of claim 2, wherein the OBD unit is configured for:
retrieving the information associated with the driver from the identity dongle through the vehicle charger;
determining whether the retrieved information matches with information stored in the OBD unit; and
authenticating the driver of the vehicle based on the determination.

4. The system of claim 1, wherein the OBD unit is configured for:
obtaining vehicle data from the ECU;
processing the vehicle data obtained from the ECU; and communicating the vehicle data to the identity dongle.

5. The system of claim 4, wherein the identity dongle is configured for:
storing the vehicle data received from the OBD unit; and
transmitting the stored vehicle data to a backend server via a communication channel.

6. The system of claim 5, wherein the identity dongle is configured for:
transmitting the stored vehicle data to the backend server using a handheld device associated with the driver of the vehicle.

7. A device comprising:
at least one port adapted to connect a vehicle charger of vehicle; a processor coupled to the port;

a memory unit coupled to the processor, wherein the memory unit includes information associated with a driver of the vehicle, and wherein the memory unit includes instructions stored therein that when executed by the processor, cause the processor to perform steps comprising:

performing a search for authentication devices connected to the vehicle charger via a battery line when plugged into the vehicle charger port;
connecting to one of authentication devices coupled to the vehicle charger;
providing the information associated with the driver to the connected authentication device so that the authentication device authenticates the driver based on the information associated with the driver.

8. The device of claim 7, wherein the one of authentication devices comprises an on-board diagnostic (OBD) unit.

9. The device of claim 7, wherein the steps further comprises:
receiving parameters associated with the vehicle from the authentication device; and
storing the parameters associated with the vehicle.

10. The device of claim 9 further comprising:
a transceiver configured for transmitting the stored parameters to a backend server via a communication channel.

11 The device of claim 10, wherein the transceiver is configured for transmitting the stored parameters to a handheld device.

12. The device of claim 10, wherein the at least one port is configured for transmitting the stored parameters to a handheld device.

13. The device of claim 10, further comprising:
a GPS module configured for determining geo-positioning system coordinates associated with the location of the vehicle and communicating the GPS coordinates to the backend server.