IP Library Granted Patent US 8,812,172
Granted Patent B2
US 8,812,172 · App. 12/559,293 · Granted Aug 19, 2014

Method for generating a vehicle identifier

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 8,812,172
App. No.
12/559,293
Granted
Aug 19, 2014
Kind
B2
Abstract

Upon initial boot-up, a telematics device receives a PID map in response to a PID map request. The TCU may send multiple PID map requests for different mode and PID combinations over a vehicles communication bus, and then may append each received PID map to the already-received PID maps. The multiple PID maps appended to one another form a composite bit value, or composite PID map. The composite PID map is processed according to a hash algorithm, resulting in a pseudo-VIN. Upon subsequent boot-ups of the TCU, the TCU sends the multiple PID map requests over the vehicle's bus and generates a pseudo VIN following the same steps as it did at initial boot-up. The TCU compares the currently generated pseudo-VIN to the initial pseudo VIN; if it determines a mismatch, it sends a notification to an interested third party that indicates improper usage of the TCU.

Claims (14)

1. A system comprising a server configured to communicate with a telematics control unit, wherein the telematics control unit is configured to perform a method for identifying a vehicle based on equipment installed on it, the method comprising: receiving bits, generated by one, or more, of a plurality of devices installed on the vehicle, in response to a PID map request; processing the received bits according to an algorithm that transforms the received bits into a result representative of the bits received in response to the PID map request; and storing the representative result from the algorithm to a memory.

2. The system of claim 1 wherein the telematics control unit is further configured to perform the step of using the stored representative result from the algorithm as a basis for determining the identity of the vehicle.

3. The system of claim 1 wherein the telematics control unit is further configured to perform the steps of comparing the representative result from a subsequent iteration to the representative result from an initial iteration of the method and determining that the same vehicle's device, or devices, that generated the bits received in the subsequent iteration did not generate the bits in the initial iteration if the representative results from the initial and subsequent iterations do not match.

4. The system of claim 3 wherein the telematics control unit is further configured to perform the step of notifying an interested party if the same vehicle's device, or devices, that generated the subsequent representative result did not generate the initial representative result.

5. The system of claim 1 wherein the vehicle identified by the initial iteration is owned, or operated, by a customer of the interested party.

6. The system of claim 3 wherein the telematics control unit is further configured to perform the step of notifying an interested party if the same vehicle's device that generated the subsequent representative result also generated the initial representative result.

7. The system of claim 3 wherein the telematics control unit is further configured to perform the step of disabling itself if the representative results from the initial and subsequent iterations do not match.

8. A server configured to communicate with a telematics control unit, the server configured to perform a method for identifying a vehicle based on equipment installed on it, the method comprising: receiving bits, generated by one, or more, of a plurality of devices installed on the vehicle, in response to a PID map request; processing the received bits according to an algorithm that transforms the received bits into a result representative of the bits received in response to the PID map request; and storing the representative result from the algorithm to at memory.

9. The server of claim 8 further configured to perform the step of using the stored representative result from the algorithm as a basis for determining the identity of the vehicle.

10. The server of claim 8 further configured to perform the steps of comparing the representative result from a subsequent iteration to the representative result from an initial iteration of the method and determining that the same vehicle's device, or devices, that generated the bits received in the subsequent iteration did not generate the bits in the initial iteration if the representative results from the initial and subsequent iterations do not match.

11. The server of claim 10 further configured to perform the step of notifying an interested party if the same vehicles device, or devices, that generated the subsequent representative result did not generate the initial representative result.

12. The server of claim 8 wherein the vehicle identified by the initial iteration is owned, or operated, by a customer of the interested party.

13. The server of claim 10 further configured to perform the step of notifying an interested party if the same vehicle's device, or devices, that generated the subsequent representative result also generated the initial representative result.

14. The server of claim 10 further configured to perform the step of disabling a telematics control unit of the vehicle that generated the subsequent iteration if the representative results from the initial and subsequent iterations do not match.

Assignments (8)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 11, 2018
From: VERIZON CONNECT INC.
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 047469/0089 →
CHANGE OF NAME Recorded Apr 11, 2018
From: VERIZON TELEMATICS INC.
To: VERIZON CONNECT INC.
Reel/Frame 045911/0801 →
MERGER Recorded Feb 16, 2016
From: HTI IP, LLC
To: VERIZON TELEMATICS INC.
Reel/Frame 037827/0964 →
RELEASE OF ALL PRIOR SECURITY INTERESTS HELD BY PLASE Recorded Jul 29, 2012
From: PLASE HT, LLC
To: HTI IP, LLC
Reel/Frame 028667/0310 →
RELEASE OF ALL PRIOR SECURITY INTERESTS HELD BY MORGAN STANLEY Recorded Jul 29, 2012
From: MORGAN STANLEY & CO
To: HTI IP, LLC
Reel/Frame 028667/0240 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2010
From: BERKOBIN, ERIC C.; BERKOBIN, ALEX; KALINADHABHOTLA, DEEP
To: HTI IP, L.L.C.
Reel/Frame 024102/0976 →
GRANT OF SECURITY INTEREST IN US PATENTS AND APPLICATIONS Recorded Dec 21, 2009
From: HTI IP, LLC
To: MORGAN STANLEY & CO. INCORPORATED, AS COLLATERAL AGENT
Reel/Frame 023679/0419 →
SECURITY AGREEMENT Recorded Dec 18, 2009
From: HTI IP, LLC
To: PLASE HT, LLC
Reel/Frame 023668/0894 →