Systems and methods for vehicle configuration verification with failsafe code
A computer system for verifying vehicle software configuration may be provided. 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: (1) transmit, to a vehicle computing system, an authentication request including a hash algorithm specification; (2) receive, from the vehicle computing system, a current configuration hash value and a vehicle identifier; (3) retrieve a trusted data block from a memory based upon the vehicle identifier, the trusted data block including a stored configuration hash value and a smart contract code segment; (4) execute the smart contract code segment, the smart contract code segment including a failsafe code segment; and/or (5) transmit the authentication response to the vehicle computing system, and cause the vehicle computing system to execute the failsafe code segment.
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.
2. The computer system of claim 1 , wherein the message is associated with an authentication response.
3. The computer system of claim 1 , wherein the instructions further cause the processor to determine that the current configuration hash value associated with the vehicle is invalid based on a stored configuration hash value included in a trusted data block.
4. The computer system of claim 1 , wherein the instructions further cause the processor to:
receive, from the vehicle computing system, the current configuration hash value and a vehicle identifier; and
retrieve a trusted data block from a memory based upon the vehicle identifier, the trusted data block including the smart contract code segment.
5. The computer system of claim 1 , wherein the instructions further cause the processor to transmit, to the vehicle computing system, an initial message including a hash algorithm specification.
6. The computer system of claim 5 , wherein the initial message is associated with an authentication request requesting the current configuration hash value associated with the vehicle.
7. The computer system of claim 1 , wherein the smart contract code segment further includes a failsafe destination, and wherein the failsafe code segment is configured to cause the vehicle computing system to autonomously navigate to the failsafe destination.
8. The computer system of claim 1 , wherein the failsafe code segment is configured to revert one or more configuration changes made to the vehicle computing system.
9. The computer system of claim 1 , wherein the failsafe code segment is configured to disable at least one autonomous driving functionality on the vehicle computing system.
10. A computer-implemented method for remote verification of a vehicle software configuration stored within a vehicle, using one or more processors, the method comprising:
executing 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 one or more processors, causes:
in response to determining that a current configuration hash value associated with the vehicle is invalid, generating 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
transmitting the message to the vehicle computing system, thereby causing the vehicle computing system to execute the failsafe code segment.
11. The computer-implemented method of claim 10 , wherein the message is associated with an authentication response.
12. The computer-implemented method of claim 10 , wherein the smart contract code segment, when executed by the one or more processors, further causes determining that the current configuration hash value associated with the vehicle is invalid based on a stored configuration hash value included in a trusted data block.
13. The computer-implemented method of claim 10 , wherein the smart contract code segment, when executed by the one or more processors, further causes:
receiving, from the vehicle computing system, the current configuration hash value and a vehicle identifier; and
retrieving a trusted data block from a memory based upon the vehicle identifier, the trusted data block including the smart contract code segment.
14. The computer-implemented method of claim 10 , wherein the smart contract code segment, when executed by the one or more processors, further causes transmitting, to the vehicle computing system, an initial message including a hash algorithm specification.
15. The computer-implemented method of claim 14 , wherein the initial message is associated with an authentication request requesting the current configuration hash value associated with the vehicle.
16. The computer-implemented method of claim 10 , wherein the smart contract code segment further includes a failsafe destination, and wherein the failsafe code segment is configured to cause the vehicle computing system to autonomously navigate to the failsafe destination.
17. The computer-implemented method of claim 10 , wherein the failsafe code segment is configured to revert one or more configuration changes made to the vehicle computing system.
18. The computer-implemented method of claim 10 , wherein the failsafe code segment is configured to disable at least one autonomous driving functionality on the vehicle computing system.
19. A non-transitory computer-readable storage medium having computer-executable instructions embodied thereon, wherein when executed by a computing device including at least one processor coupled to a memory device, the computer-executable instructions cause the at least one 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 at least one processor, causes the at least one processor to:
in response to determining that a current configuration hash value associated with a 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.
20. The non-transitory computer-readable storage medium of claim 19 , wherein the computer-executable instructions further cause the at least one processor to determine that the current configuration hash value associated with the vehicle is invalid based on a stored configuration hash value included in a trusted data block.