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); G05D 2201/0213 (2013.01); H04L 2209/80 (2013.01); H04L 2209/84 (2013.01)] | 17 Claims |
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 a processor, the remote backend computing system remote from the vehicle; 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:
receive a vehicle data file including a vehicle identifier for identifying the vehicle, a trusted software version identifier for identifying a version of a software stored on the vehicle, and a digital signature for validating the software as a compliant and trusted software, wherein validating the software as the compliant and trusted software includes determining the software has been validated against one or more safety and compliance standards;
generate a first data block including a configuration hash value of the trusted software version identifier, the digital signature, and the vehicle identifier;
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.
|