US 12,219,023 B2
Systems and methods for vehicle configuration verification with failsafe code
Matthew Lewis Floyd, Alpharetta, GA (US); Leroy Luther Smith, Jr., Sandy Springs, GA (US); Brittney Benzio, Atlanta, GA (US); Nathan Barnard, Bloomington, IL (US); and Shannon Marie Lowry, Atlanta, GA (US)
Assigned to State Farm Mutual Automobile Insurance Company, Bloomington, IL (US)
Filed by State Farm Mutual Automobile Insurance Company, Bloomington, IL (US)
Filed on Feb. 20, 2023, as Appl. No. 18/171,567.
Application 18/171,567 is a continuation of application No. 17/080,470, filed on Oct. 26, 2020, granted, now 11,601,282.
Application 17/080,470 is a continuation of application No. 16/026,930, filed on Jul. 3, 2018, granted, now 10,826,706, issued on Oct. 14, 2020.
Claims priority of provisional application 62/655,524, filed on Apr. 10, 2018.
Claims priority of provisional application 62/639,606, filed on Mar. 7, 2018.
Claims priority of provisional application 62/623,983, filed on Jan. 30, 2018.
Prior Publication US 2023/0208927 A1, Jun. 29, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 67/00 (2022.01); B60W 50/02 (2012.01); B60W 50/029 (2012.01); B60W 50/04 (2006.01); G05D 1/00 (2024.01); G06F 21/54 (2013.01); G07C 5/00 (2006.01); H04L 9/06 (2006.01); H04L 9/32 (2006.01); H04L 67/12 (2022.01); H04W 4/40 (2018.01); H04W 12/06 (2021.01); H04W 12/30 (2021.01)
CPC H04L 67/34 (2013.01) [B60W 50/0205 (2013.01); B60W 50/029 (2013.01); B60W 50/045 (2013.01); G05D 1/0088 (2013.01); G05D 1/0214 (2013.01); G06F 21/54 (2013.01); G07C 5/008 (2013.01); H04L 9/0643 (2013.01); H04L 9/3236 (2013.01); H04L 9/3239 (2013.01); H04L 9/3242 (2013.01); H04L 9/3247 (2013.01); H04L 67/12 (2013.01); H04W 4/40 (2018.02); H04W 12/06 (2013.01); H04W 12/30 (2021.01); B60W 2050/0292 (2013.01); B60W 2050/046 (2013.01); H04L 2209/80 (2013.01); H04L 2209/84 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer system for remote verification of a vehicle software configuration stored within a vehicle, the computer system comprising:
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:
execute a smart contract code segment including a failsafe code segment and defining one or more actions associated with execution of the failsafe code segment, wherein the smart contract code segment, when executed by the processor, causes the processor to:
in response to determining that a current configuration hash value associated with the vehicle is invalid, generate a message including the failsafe code segment, the message configured to cause a vehicle computing system associated with the vehicle to execute the failsafe code segment; and
transmit the message to the vehicle computing system, thereby causing the vehicle computing system to execute the failsafe code segment.