A vehicle receives a first portion of content via ATSC broadcast, generates a random nonce, responsive to receiving the content, and sends the nonce and a request for content verification to a remote server. The vehicle receives a message from the remote server indicating whether the first portion of content is likely valid, the message including a second portion of content and a hash value when the content is likely valid. The vehicle then calculates a second hash value, using the random nonce and the first portion of content. The vehicle compares the second hash value to the first hash value, and responsive to the second hash value matching the first hash value, combines the second portion of content and the first portion of content to create combined content. The vehicle then uses a security strategy to convert the combined content into utilizable content, and utilizes the content.

A method comprises receiving vehicle data comprising information associated with a plurality of sensors of autonomous vehicle and segmenting the received vehicle data into non-public data and public data. The method further comprises partitioning the public data into a plurality of data partitions and generating a plurality of data levels of the public data. Each data level of the plurality of data levels is generated according to an access level of a plurality of access levels and includes one or more data partitions of the plurality of data partitions in an encrypted form. The method further comprises transmitting the generated plurality of data levels to a group of electronic devices. Each electronic device of the group of electronic devices retrieves, according to one of the plurality of access levels, at least a portion of the public data from the transmitted plurality of data levels.

In one implementation, a method for providing security on an externally connected controller includes launching, by the controller, a security layer that includes a whitelist of permitted processes on the controller, the whitelist including (i) signatures for processes that are authorized to be executed and (ii) context information identifying permitted controller contexts within which the processes are authorized to be executed; determining, by the security layer, whether the particular process is permitted to be run on the controller based on a comparison of the determined signature with a verified signature for the particular process from the whitelist; identifying, by the security layer, a current context for the controller; determining by the security layer, whether the particular process is permitted to be run on the controller based on a comparison of the current context with one or more permitted controller contexts for the particular process from the whitelist.

A method and device for establishing a communication along a communications channel between a first device (200A) and a second device (200B) is disclosed. The method comprises mutually discovering the first device (200A) and the second device (200B), validating (F5, F6, F7) the communications channel between the first device (200A) and the second device (200B) by exchange of data messages, exchanging a secret between the first device (200A) and the second device (200B) and then exchanging encrypted messages along the communications channel.

Systems and methods for secure peer-to-peer communications are described. Devices registered into trusted network may be capable of establishing a shared data encryption key (DEK). In embodiments, each device may be configured to obtain a share of a data encryption key (DEKi) that can be stored locally. The shares may be shares in an M of N Secret Sharing Scheme. This may involve a network that includes an integer, N, devices, and in which M devices may share a secret (i.e. the DEK) during communications, M being an integer less than or equal to N. To obtain the entire DEK during encryption/decryption, a requesting device may send requests to M of N devices for their shares of the DEK. Once M shares are obtained, they may be used generate the DEK for encrypting/decrypting data between the devices.

Disclosed herein are techniques for analyzing software delta changes based on functional line-of-code behavior and relation models. Techniques include identifying a prompt to change a first version of code on a controller to a second version of code; constructing, based on the identified prompt, a line-of-code behavior and relation model representing execution of functions of the controller based on the second version of code; performing a signature operation on the generated line-of-code behavior and relation model to produce a signature value; and sending the signature value to the controller; wherein the controller is configured to compare the signature value to a computed signature value that the controller is configured to compute based on the second version of code and determine, based on the comparison, whether to validate the second version of code.

A method assists with driving a client vehicle upon detection of a current driving situation in a current time context. The method includes identifying a set of surrounding vehicles located in a neighboring area of the client vehicle; determining an identifier associated with each surrounding vehicle; transmitting a request for characterizing the driving behavior of each surrounding vehicle to a driving assistance server, the characterization request including the identifier associated with each surrounding vehicle, the current driving situation, and the current time context; determining a driving behavior score in association with each identifier using a database of driving behavior scores, with each driving behavior score in the database being associated with a vehicle identifier, in a given driving situation and in a given time context; and determining a driving maneuver as a function of the driving behavior scores associated with the identifiers of the surrounding vehicles.

A vehicle certificate application method implemented by a vehicle-mounted device includes sending a certificate proxy application message to a roadside unit RSU in response to determining that the Uu interface of the vehicle-mounted device is unavailable or the signal quality of the Uu interface is lower than the threshold. The certificate proxy application message includes certificate application information of a vehicle to which the vehicle-mounted device is mounted. The certificate application information is forwarded by the RSU to a third-party authority. The vehicle-mounted device receives, from the RSU, a certificate proxy application response that includes an identity certificate of the vehicle generated by the third-party authority based on the certificate application information.

A method includes storing a detected event code in a first blockchain, wherein each electronic control unit (ECU) in a plurality of ECUs in a vehicle includes a first blockchain node of the first blockchain; determining a validity of each first blockchain node of the first blockchain by determining that the event code is one of (a) stored in the respective first blockchain node of the first blockchain and valid or (b) not stored in the respective first blockchain node of the first blockchain and invalid; and providing the event code and the validity of each first blockchain node of the first blockchain to a second blockchain maintained at least one second blockchain node via a network outside the vehicle.

Methods and systems for maintaining a distributed ledger and/or blockchain of transactions and/or events pertaining to autonomous vehicles and/or smart contracts. An enforcement server may receive indications of transactions and/or events generated by one or more autonomous vehicles. The transactions and/or events may include information relating to a trigger condition and/or a decision condition associated with one or more smart contracts. The enforcement server may route the transaction to the appropriate smart contract to determine whether a trigger condition has been satisfied. When a trigger condition is satisfied, the enforcement server may automatically perform an action to enforce the smart contract and/or update the distributed ledger. In some aspects, the distributed ledger may record events associated with autonomous and semi-autonomous vehicle technology or system usage, including events associated with transitioning between manual and autonomous control, or vice versa, of one or more autonomous or semi-autonomous vehicles.