IP Library Granted Patent US 12,267,397
Granted Patent B2
US 12,267,397 · App. 18/495,557 · Granted Apr 1, 2025

Cryptographic hash chain for vehicle configuration verification

Inventors: Matthew Lewis Floyd (Alpharetta, GA); Leroy Luther Smith, Jr. (Sandy Springs, GA); Brittney Benzio (Atlanta, GA); Nathan Barnard (El Paso, IL); Shannon Marie Lowry (Bloomington, IL)
Assignee: State Farm Mutual Automobile Insurance Company
H04L67/34B60W50/0205B60W50/029B60W50/045G05D1/0088G05D1/0214G06F21/54G07C5/008H04L9/0643H04L9/3236H04L9/3239H04L9/3242H04L9/3247H04L67/12H04W4/40H04W12/06H04W12/30B60W2050/0292B60W2050/046H04L2209/80H04L2209/84
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 12,267,397
App. No.
18/495,557
Filed
Oct 26, 2023
Granted
Apr 1, 2025
Kind
B2
Art Unit
2492
USPC
701/32.6
Abstract

In one aspect, a computer system for vehicle configuration verification, and/or detecting unauthorized vehicle modification may be provided. In some exemplary embodiments, the computer system may include a processor and a non-transitory, tangible, computer-readable storage medium having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations including: (1) receiving a vehicle image, including a vehicle identifier and at least one software module; (2) calculating a configuration hash value of the at least one software module; generating a first data block including the configuration hash value, a first index value, the vehicle identifier, and a digital signature; (3) storing the first data block in a memory; and/or (4) transmitting the first data block to any number of network participants using a distributed network to facilitate vehicle software configuration verification.

Claims (32)

1. A computer system for creating trusted cryptographic hash values for verifying a vehicle software configuration of a vehicle, the computer system comprising:

a remote backend computing system including at least one processor; and

a non-transitory, tangible, computer-readable storage medium having computer-executable instructions stored thereon that, in response to execution by the at least one processor, cause the at least one processor to:

receive a vehicle data file including a vehicle identifier for identifying the vehicle and a digital signature for determining that the vehicle software has been validated against one or more safety and compliance standards;

generate a first data block including a configuration hash value of the digital signature and the vehicle identifier, and append the digital signature to the first data block;

store the first data block in a memory; and

transmit the first data block to any number of network participants using a distributed network, wherein the any number of network participants validate the digital signature of the first data block before storing the first data block.

2. The computer system of claim 1 , wherein the vehicle data file further includes a trusted software version identifier for identifying a version of a software stored on the vehicle.

3. The computer system of claim 2 , wherein the first data block further includes a configuration hash value of the trusted software version identifier.

4. The computer system of claim 2 , wherein the computer-executable instructions further cause the at least one processor to calculate the configuration hash value of the trusted software version identifier and the vehicle identifier.

5. The computer system of claim 1 , wherein the any number of network participants validate the digital signature to verify the authenticity of the first data block.

6. The computer system of claim 1 , wherein the remote backend computing system remote from the vehicle.

7. A computer-implemented method for creating trusted cryptographic hash values for verifying a vehicle software configuration of a vehicle using a computing system including a remote backend computing system that includes one or more processors, the method comprising:

receiving a vehicle data file including a vehicle identifier for identifying the vehicle and a digital signature for determining that the vehicle software has been validated against one or more safety and compliance standards;

generating a first data block including a configuration hash value of the digital signature and the vehicle identifier, and appending the digital signature to the first data block;

storing the first data block in a memory; and

transmitting the first data block to any number of network participants using a distributed network, wherein the any number of network participants validate the digital signature of the first data block before storing the first data block.

8. The computer-implemented method of claim 7 , wherein the vehicle data file further includes a trusted software version identifier for identifying a version of a software stored on the vehicle.

9. The computer-implemented method of claim 8 , wherein the first data block further includes a configuration hash value of the trusted software version identifier.

10. The computer-implemented method of claim 8 further comprising calculating the configuration hash value of the trusted software version identifier and the vehicle identifier.

11. The computer-implemented method of claim 7 , wherein the any number of network participants validate the digital signature to verify the authenticity of the first data block.

12. The computer-implemented method of claim 7 , wherein the remote backend computing system remote from the vehicle.

13. At least one non-transitory computer-readable storage medium having computer-executable instructions embodied thereon, wherein when executed by a computing system including a remote backend computing system that includes at least one processor coupled to a memory device, the computer-executable instructions cause the at least one processor to:

receive a vehicle data file including a vehicle identifier for identifying a vehicle and a digital signature for determining that a vehicle software of the vehicle has been validated against one or more safety and compliance standards;

generate a first data block including a configuration hash value of the digital signature and the vehicle identifier, and append the digital signature to the first data block;

store the first data block in a memory; and

transmit the first data block to any number of network participants using a distributed network, wherein the any number of network participants validate the digital signature of the first data block before storing the first data block.

14. The computer-readable storage medium of claim 13 , wherein the vehicle data file further includes a trusted software version identifier for identifying a version of a software stored on the vehicle.

15. The computer-readable storage medium of claim 14 , wherein the computer-executable instructions further cause the at least one processor to calculate the configuration hash value of the trusted software version identifier and the vehicle identifier.

16. The computer-readable storage medium of claim 13 , wherein the any number of network participants validate the digital signature to verify the authenticity of the first data block.

17. The computer-readable storage medium of claim 13 , wherein the remote backend computing system remote from the vehicle.

18. The computer-readable storage medium of claim 13 , wherein the computer-executable instructions further cause the at least one processor to append the digital signature to the first data block.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2023
From: FLOYD, MATTHEW LEWIS; LOWRY, SHANNON MARIE; SMITH, LEROY LUTHER, JR.; BARNARD, NATHAN; BENZIO, BRITTNEY
To: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Reel/Frame 065362/0494 →
Continuity (6)
Continuation 17824698 · May 25, 2022
Continuation 16026865 · Jul 3, 2018
Provisional Application 62655524 · Apr 10, 2018
Provisional Application 62639606 · Mar 7, 2018
Provisional Application 62623983 · Jan 30, 2018
Related Publication 20240056508A1 · Feb 15, 2024
References Cited (68)
US 7841010B2 · Lerouge et al. · 2010 [cited by applicant]
US 8832464B2 · Olson · 2014 [cited by examiner]
US 8949611B1 · Kimberly · 2015 [cited by examiner]
US 9132790B2 · Miyake · 2015 [cited by applicant]
US 9141372B1 · Sarkar et al. · 2015 [cited by applicant]
US 9215071B2 · Billau et al. · 2015 [cited by applicant]
US 9536076B2 · Gajulapalli et al. · 2017 [cited by applicant]
US 9607147B2 · Chen · 2017 [cited by examiner]
US 9830748B2 · Rosenbaum · 2017 [cited by applicant]
US 9990782B2 · Rosenbaum · 2018 [cited by applicant]
US 10158480B1 · Winklevoss et al. · 2018 [cited by applicant]
US 10185553B2 · Annapureddy et al. · 2019 [cited by applicant]
US 10269190B2 · Rosenbaum · 2019 [cited by applicant]
US 10423401B2 · Tschache · 2019 [cited by applicant]
US 10445493B2 · Suzuki et al. · 2019 [cited by applicant]
US 10447483B1 · Su · 2019 [cited by applicant]
US 10467824B2 · Rosenbaum · 2019 [cited by applicant]
US 10481896B2 · Rocci et al. · 2019 [cited by applicant]
US 10666767B1 · Floyd et al. · 2020 [cited by applicant]
US 10826706B1 · Floyd et al. · 2020 [cited by applicant]
US 11227452B2 · Rosenbaum · 2022 [cited by applicant]
US 11288373B2 · Zhou · 2022 [cited by examiner]
US 11407410B2 · Rosenbaum · 2022 [cited by applicant]
US 11524707B2 · Rosenbaum · 2022 [cited by applicant]
US 11594083B1 · Rosenbaum · 2023 [cited by applicant]
US 20030159044A1 · Doyle et al. · 2003 [cited by applicant]
US 20110093701A1 · Etchegoyen · 2011 [cited by applicant]
US 20110138188A1 · Lee · 2011 [cited by examiner]
US 20110307336A1 · Smirnov et al. · 2011 [cited by applicant]
US 20130036103A1 · Lawson et al. · 2013 [cited by applicant]
US 20130073864A1 · Sarkar et al. · 2013 [cited by applicant]
US 20140114497A1 · Miyake · 2014 [cited by examiner]
US 20140129871A1 · Poenaru et al. · 2014 [cited by applicant]
US 20150026826A1 · Allegri et al. · 2015 [cited by applicant]
US 20150113520A1 · Kotani et al. · 2015 [cited by applicant]
US 20160013934A1 · Smereka · 2016 [cited by examiner]
US 20170093896A1 · Poornachandran et al. · 2017 [cited by applicant]
US 20170147356A1 · Kotary et al. · 2017 [cited by applicant]
US 20170346693A1 · Dix · 2017 [cited by examiner]
US 20170372143A1 · Barcus et al. · 2017 [cited by applicant]
US 20180006810A1 · Ideguchi · 2018 [cited by examiner]
US 20180122237A1 · Nascimento et al. · 2018 [cited by applicant]
US 20180254906A1 · Tofts · 2018 [cited by examiner]
US 20180308098A1 · Ebrahimi · 2018 [cited by examiner]
US 20180316502A1 · Nadeau et al. · 2018 [cited by applicant]
US 20190007215A1 · Hakuta · 2019 [cited by examiner]
US 20190146775A1 · Wang et al. · 2019 [cited by applicant]
US 20190160660A1 · Husain · 2019 [cited by examiner]
US 20190160675A1 · Paschall, II et al. · 2019 [cited by applicant]
US 20190178974A1 · Droz · 2019 [cited by applicant]
US 20190260763A1 · Okabe · 2019 [cited by examiner]
US 20190295336A1 · Jones · 2019 [cited by examiner]
US 20200007316A1 · Krishnamacharya et al. · 2020 [cited by applicant]
US 20200089487A1 · Ramic et al. · 2020 [cited by applicant]
US 20200233950A1 · Assenmacher et al. · 2020 [cited by applicant]
US 20220092893A1 · Rosenbaum · 2022 [cited by applicant]
US 20220340148A1 · Rosenbaum · 2022 [cited by applicant]
US 20230060300A1 · Rosenbaum · 2023 [cited by applicant]
EP 3239686A1 · 2017 [cited by applicant]
EP 3283996A1 · 2018 [cited by applicant]
EP 3316513A1 · 2018 [cited by applicant]
EP 3445017A1 · 2019 [cited by applicant]
EP 3578433B1 · 2020 [cited by applicant]
EP 3730375B1 · 2021 [cited by applicant]
EP 3960576A1 · 2022 [cited by applicant]
EP 4190659A1 · 2023 [cited by applicant]
EP 4190660A1 · 2023 [cited by applicant]
WO 2002065258A2 · 2002 [cited by applicant]