IP Library Granted Patent US 11,954,949
Granted Patent B2
US 11,954,949 · App. 17/248,021 · Granted Apr 9, 2024

Systems and methods for identifying a vehicle based on messages received by a control area network bus of the vehicle

Inventors: Louis Burger (Dublin, IE); Sean McGinn (Dublin, IE)
Assignee: Verizon Connect Development Limited
G07C5/008B60W40/08G07C5/0841H04L12/40H04L2012/40215
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,954,949
App. No.
17/248,021
Granted
Apr 9, 2024
Kind
B2
Abstract

In some implementations, a vehicle device may receive, from a controller area network (CAN) bus of a vehicle and for a time period, messages received by the CAN bus after an engine of the vehicle is turned on. The vehicle device may combine identifiers provided in unique addresses, of the messages received by the CAN bus, to generate a unique identifier, and may utilize the unique identifier to determine data identifying a year, a make, and a model of the vehicle. The vehicle device may utilize the data identifying the year, the make, and the model of the vehicle to determine non-standard parameter identifiers associated with an engine control module of the vehicle.

Claims (69)

1. A method, comprising:

receiving, by a vehicle device, from a controller area network (CAN) bus of a vehicle, and for a time period, messages received by the CAN bus after an engine of the vehicle is turned on;

combining, by the vehicle device, unique addresses associated with one or more vehicle systems of the vehicle, of the messages received by the CAN bus, to generate a unique identifier;

utilizing, by the vehicle device, the unique identifier to determine data identifying a year, a make, and a model of the vehicle; and

determining, by the vehicle device, non-standard parameter identifiers from an engine control module of the vehicle utilizing an association between the non-standard parameter identifiers and the year, the make, and the model of the vehicle.

2. The method of claim 1 , wherein utilizing the unique identifier to determine the data identifying the year, the make, and the model of the vehicle comprises:

comparing the unique identifier with vehicle data to identify the data identifying the year, the make, and the model of the vehicle,

wherein the vehicle data includes data mapping unique identifiers with years, makes, and models of different vehicles.

3. The method of claim 1 , wherein utilizing the unique identifier to determine the data identifying the year, the make, and the model of the vehicle comprises:

providing the unique identifier to a server device that determines the data identifying the year, the make, and the model of the vehicle; and

receiving the data identifying the year, the make, and the model of the vehicle from the server device based on providing the unique identifier to the server device.

4. The method of claim 3 , further comprising:

utilizing the non-standard parameter identifiers to obtain parameters from the vehicle; and

providing the parameters to the server device.

5. The method of claim 1 , further comprising:

utilizing the non-standard parameter identifiers to obtain parameters from the vehicle; and

performing one or more actions based on the parameters.

6. The method of claim 5 , wherein performing the one or more actions based on the parameters comprises one or more of:

generating a notification based on the parameters;

causing an adjustment of an operation of the vehicle based on the parameters;

causing an adjustment of an operation of the engine of the vehicle based on the parameters; or

providing the parameters to a server device or a client device associated with a driver of the vehicle.

7. The method of claim 1 , wherein the messages received by the CAN bus are included in logs captured by the CAN bus for the time period.

8. A vehicle device, comprising:

one or more processors configured to:

receive, from a controller area network (CAN) bus of a vehicle and for a time period, messages received by the CAN bus after one or more components of the vehicle are turned on;

combine unique addresses associated with one or more vehicle systems of the vehicle, of the messages received by the CAN bus, to generate a unique identifier;

utilize the unique identifier to determine data identifying a year, a make, and a model of the vehicle;

determine non-standard parameter identifiers associated with one or more modules of the vehicle utilizing an association between the non-standard parameter identifiers and the year, the make, and the model of the vehicle;

utilize the non-standard parameter identifiers to obtain parameters from the vehicle; and

perform one or more actions based on the parameters.

9. The vehicle device of claim 8 , wherein the one or more processors are further configured to:

identify duplicate addresses of the messages received by the CAN bus; and

remove the duplicate addresses, from the messages, to determine the unique addresses of the messages received by the CAN bus.

10. The vehicle device of claim 8 , wherein the vehicle device includes a vehicle tracking unit.

11. The vehicle device of claim 8 , wherein the non-standard parameter identifiers include codes used to request data from the vehicle.

12. The vehicle device of claim 8 , wherein the one or more processors, when combining the unique addresses, of the messages received by the CAN bus, to generate the unique identifier, are configured to:

identify duplicate addresses of the messages received by the CAN bus;

remove the duplicate addresses, from the messages, to determine the unique addresses of the messages received by the CAN bus; and

combine the unique addresses to generate the unique identifier.

13. The vehicle device of claim 8 , wherein the messages received by the CAN bus are included in logs captured by the CAN bus for the time period.

14. The vehicle device of claim 8 , wherein the one or more processors, when performing the one or more actions based on the parameters, are configured to:

provide the parameters to a user device associated with a driver of the vehicle.

15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a vehicle device, cause the vehicle device to:

receive, from a controller area network (CAN) bus of a vehicle and for a time period, messages received by the CAN bus after one or more components of the vehicle are turned on;

combine unique addresses associated with one or more vehicle systems of the vehicle, of the messages received by the CAN bus, to generate a unique identifier;

utilize the unique identifier to determine data identifying a year, a make, and a model of the vehicle;

determine non-standard parameter identifiers associated with one or more control modules of the vehicle utilizing an association between the non-standard parameter identifiers and the year, the make, and the model of the vehicle;

obtain parameters from the vehicle based on the non-standard parameter identifiers; and

perform one or more actions based on the parameters.

16. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the vehicle device to utilize the unique identifier to determine the data identifying the year, the make, and the model of the vehicle, cause the vehicle device to:

compare the unique identifier and vehicle data to identify the data identifying the year, the make, and the model of the vehicle,

wherein the vehicle data includes data mapping unique identifiers with years, makes, and models of different vehicles.

17. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the vehicle device to utilize the unique identifier to determine the data identifying the year, the make, and the model of the vehicle, cause the vehicle device to:

provide the unique identifier to a server device that determines the data identifying the year, the make, and the model of the vehicle; and

receive the data identifying the year, the make, and the model of the vehicle from the server device based on providing the unique identifier to the server device.

18. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the vehicle device to perform the one or more actions based on the parameters, cause the vehicle device to:

generate a notification based on the parameters;

cause an adjustment of an operation of the vehicle based on the parameters;

cause an adjustment of an operation of an engine of the vehicle based on the parameters; or

provide the parameters to a server device.

19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the vehicle device to:

identify duplicate addresses of the messages received by the CAN bus; and

remove the duplicate addresses, from the messages, to determine the unique addresses of the messages received by the CAN bus.

20. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the vehicle device to combine the unique addresses, of the messages received by the CAN bus, to generate the unique identifier, cause the vehicle device to:

identify duplicate addresses of the messages received by the CAN bus;

remove the duplicate addresses, from the messages, to determine the unique addresses of the messages received by the CAN bus; and

combine the unique addresses to generate the unique identifier.

Assignments (2)
CHANGE OF NAME Recorded Apr 13, 2021
From: VERIZON CONNECT IRELAND LIMITED
To: VERIZON CONNECT DEVELOPMENT LIMITED
Reel/Frame 055911/0506 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 6, 2021
From: BURGER, LOUIS; MCGINN, SEAN
To: VERIZON CONNECT IRELAND LIMITED
Reel/Frame 054823/0997 →
Continuity (1)
Related Publication 20220215693A1 · Jul 7, 2022