Systems and methods for vehicle configuration verification using smart contracts
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) retrieve a trusted data block from a memory, the trusted data block including a stored configuration hash value, a smart contract code segment, and a failsafe code segment; (2) generate a current configuration hash value based on at least one software module by executing the smart contract code segment; (3) determine that the current configuration hash value is invalid based on the stored configuration hash value by executing the smart contract code segment; and/or (4) execute the failsafe code segment, in response to determining that the current configuration hash value is invalid.
1. A vehicle computer system for verifying software stored on a vehicle computing system of a vehicle, the vehicle computing system comprising:
a processor; and
a non-transitory, tangible, computer-readable storage medium having computer-executable instructions stored thereon that, in response to execution by the processor, cause the processor to:
retrieve a trusted data block from a memory, the trusted data block including a stored configuration hash value, a smart contract code segment, and a failsafe code segment;
generate, by executing a smart contract code segment, a current configuration hash value to determine whether the current configuration hash value is invalid; and
execute a failsafe code segment, in response to determining that the current configuration hash value is invalid.
2. The vehicle 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; and
cause the vehicle computing system to generate a route to the failsafe destination not including smart roadways.
3. The vehicle computer system of claim 1 , wherein the failsafe code segment is configured to:
modify at least one software module in response to determining the current configuration hash value is invalid; and
cause the vehicle computing system to modify the at least one software module until the current configuration hash value matches a fallback configuration hash value included in the smart contract code segment.
4. The vehicle 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; and
cause the vehicle to exit a smart roadway before disabling autonomous driving functionality.
5. The vehicle computer system of claim 1 , wherein the smart contract code segment is executed to determine that the current configuration hash value is invalid based on the stored configuration hash value.
6. A computer-implemented method for verifying software stored on a vehicle computing system of a vehicle, the method implemented using the vehicle computing system having one or more processors, said method comprising:
retrieving a trusted data block from a memory, the trusted data block including a stored configuration hash value, a smart contract code segment, and a failsafe code segment;
generating, by executing the smart contract code segment, a current configuration hash value of software stored on the vehicle computing system to determine whether the current configuration hash value is invalid; and
executing the failsafe code segment, in response to determining that the current configuration hash value is invalid.
7. The method of claim 6 , 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; and
cause the vehicle computing system to generate a route to the failsafe destination not including smart roadways.
8. The method of claim 6 , wherein the failsafe code segment is configured to:
modify at least one software module in response to determining the current configuration hash value is invalid; and
cause the vehicle computing system to modify the at least one software module until the current configuration hash value matches a fallback configuration hash value included in the smart contract code segment.
9. The method of claim 6 , wherein the failsafe code segment is configured to:
disable at least one autonomous driving functionality on the vehicle computing system; and
cause the vehicle to exit a smart roadway before disabling autonomous driving functionality.
10. The method of claim 6 , wherein the smart contract code segment is executed to determine that the current configuration hash value is invalid based on the stored configuration hash value.
11. A non-transitory computer-readable storage medium having computer-executable instructions embodied thereon, wherein when executed by a vehicle computer device including at least one processor coupled to a memory, the computer-executable instructions cause the vehicle computer device to:
retrieve a trusted data block from a memory, the trusted data block including a stored configuration hash value, a smart contract code segment, and a failsafe code segment;
generate, by executing the smart contract code segment, a current configuration hash value based on at last one software of software stored on the vehicle computer device to determine whether the current configuration hash value is invalid; and
execute the failsafe code segment, in response to determining that the current configuration hash value is invalid.
12. The computer-readable storage medium of claim 11 , wherein the smart contract code segment further includes a failsafe destination, and wherein the failsafe code segment is configured to:
cause the vehicle computer device to autonomously navigate to the failsafe destination; and
cause the vehicle computer device to generate a route to the failsafe destination not including smart roadways.
13. The computer-readable storage medium of claim 11 , wherein the failsafe code segment is configured to:
modify at least one software module in response to determining the current configuration hash value is invalid; and
cause the vehicle computer device to modify the at least one software module until the current configuration hash value matches a fallback configuration hash value included in the smart contract code segment.
14. The computer-readable storage medium of claim 11 , wherein the failsafe code segment is configured to:
disable at least one autonomous driving functionality on the vehicle computer device; and
cause a vehicle associated with the vehicle computer device to exit a smart roadway before disabling autonomous driving functionality.
15. The vehicle computer system of claim 1 , wherein the smart contract code segment is executed to generate the current configuration hash value based on at least one software module.
16. The method of claim 6 , wherein the smart contract code segment is executed to generate the current configuration hash value based on at least one software module.
17. The computer-readable storage medium of claim 11 , wherein the smart contract code segment is executed to generate the current configuration hash value based on at least one software module.