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 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 a current configuration hash value based on at least one software module by executing the smart contract code segment;
determine that the current configuration hash value is invalid based on the stored configuration hash value by executing the smart contract code segment; and
execute the 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 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.
3. The vehicle computer system of claim 2 , wherein the failsafe code segment is further configured to cause the vehicle computing system to generate a route to the failsafe destination not including smart roadways.
4. The vehicle computer system of claim 1 , wherein the failsafe code segment is configured to modify the at least one software module in response to determining the current configuration hash value is invalid.
5. The vehicle computer system of claim 4 , wherein the failsafe code segment is configured to cause the vehicle computing system to modify the at least one software module until the current vehicle configuration hash value matches a fallback configuration hash value included in the smart contract.
6. 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.
7. The vehicle computer system of claim 6 , wherein the failsafe code segment is further configured to cause the vehicle to exit a smart roadway before disabling autonomous driving functionality.
8. 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 a current configuration hash value based on at least one software module by executing the smart contract code segment;
determining that the current configuration hash value is invalid based on the stored configuration hash value by executing the smart contract code segment; and
executing the failsafe code segment, in response to determining that the current configuration hash value is invalid.
9. The method of claim 8 , wherein the smart contract 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.
10. The method of claim 9 , wherein the failsafe code segment is further configured to cause the vehicle computing system to generate a route to the failsafe destination not including smart roadways.
11. The method of claim 8 , wherein the failsafe code segment is configured to modify the at least one software module in response to determining the current configuration hash value is invalid.
12. The method of claim 11 , wherein the failsafe code segment is configured to cause the vehicle computing system to modify the at least one software module until the current vehicle configuration hash value matches a fallback configuration hash value included in the smart contract.
13. The method of claim 8 , wherein the failsafe code segment is configured to disable at least one autonomous driving functionality on the vehicle computing system.
14. The method of claim 13 , wherein the failsafe code segment is further configured to cause the vehicle to exit a smart roadway before disabling autonomous driving functionality.
15. 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 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 a current configuration hash value based on at least one software module by executing the smart contract code segment;
determine that the current configuration hash value is invalid based on the stored configuration hash value by executing the smart contract code segment; and
execute the failsafe code segment, in response to determining that the current configuration hash value is invalid.
16. The computer-readable storage media of claim 15 , wherein the smart contract 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-readable storage media of claim 16 , wherein the failsafe code segment is further configured to cause the vehicle computing system to generate a route to the failsafe destination not including smart roadways.
18. The computer-readable storage media of claim 15 , wherein the failsafe code segment is configured to modify the at least one software module in response to determining the current configuration hash value is invalid.
19. The computer-readable storage media of claim 18 , wherein the failsafe code segment is configured to cause the vehicle computing system to modify the at least one software module until the current vehicle configuration hash value matches a fallback configuration hash value included in the smart contract.
20. The computer-readable storage media of claim 15 , wherein the failsafe code segment is configured to disable at least one autonomous driving functionality on the vehicle computing system.
21. The computer-readable storage media of claim 20 , wherein the failsafe code segment is further configured to cause the vehicle to exit a smart roadway before disabling autonomous driving functionality.