# US 12,192,380 B2 · Systems and methods for enabling trusted communications between controllers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,192,380 B2
- Document ID: US12192380B2
- Status: Granted
- Kind: B2
- Application number: 18/325,385
- Filed: 2023-05-30
- Published: 2023-11-30
- Granted: 2025-01-07
- Earliest claimed: 2016-05-05
- Assignees: Neustar, Inc.
- Applicants: Neustar, Inc.
- Inventors: Brian R. Knopf
- Web page: https://patentgrep.com/patent/US12192380B2

## CPC

- H04L 9/3247: {involving digital signatures}
- H04L 9/006: {involving public key infrastructure [PKI] trust models (network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/321: {involving a third party or a trusted authority}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 2209/84: Vehicles
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods are described that enable trusted communications between two entities. In one implementation, a controller of a vehicle may include one or more processors configured to receive data and a controller signature from a second controller of the vehicle. The controller signature may be generated based on at least a first portion of the data. The one or more processors may be further configured to transmit the data and the controller signature to a gateway of the vehicle and receive a gateway signature from the gateway. The gateway signature may be generated based on at least a second portion of the data and transmitted to the controller after the gateway verified the controller signature. In addition, the one or more processors may be configured to verify the gateway signature and process the data.

## Claims

### Claim 1

A method implemented on a controller of a vehicle for communicating with a second controller of the vehicle, comprising:
receiving data and a controller signature from the second controller, wherein the data is destined for the controller and intended to be processed by the controller, and wherein the controller signature is generated by generating a hash value of the data and encrypting the generated hash value with a private key;
verifying the controller signature received from the second controller using a public key of the second controller;
transmitting the data and controller signature to a gateway of the vehicle;
receiving a gateway signature from the gateway, wherein the gateway signature is generated based on at least a portion of the data and transmitted to the controller after the gateway verifies the controller signature;
verifying the gateway signature; and
in response to verifying the gateway signature, processing the data.

### Claim 2 (depends on 1)

The method of claim 1, wherein the data is transmitted between the controller, the second controller, and the gateway by any of an internet connection, a private wide-area network connection, or a private local-area network connection.

### Claim 3 (depends on 1)

The method of claim 1, further comprising receiving a notification from the gateway that at least one of the data and the controller contains malicious software.

### Claim 4 (depends on 1)

The method of claim 1, wherein the gateway signature is transmitted to the controller after the gateway verifies that the controller is authorized to receive communications from the second controller.

### Claim 5 (depends on 1)

The method of claim 1, wherein the controller, the second controller, and the gateway are connected to a bus system.

### Claim 6 (depends on 5)

The method of claim 5, wherein the bus system is a controller-area network (CAN) bus system.

### Claim 7 (depends on 5)

The method of claim 5, wherein the data, the controller signature, and the gateway signature are received via the bus system and the data and the controller signature are transmitted via the bus system.

### Claim 8 (depends on 1)

The method of claim 1, wherein the controller signature is generated by the second controller using a private key associated with the second controller.

### Claim 9

A controller of a vehicle, the controller comprising one or more processors configured to:
receive data and a controller signature from a second controller, wherein the data is destined for the controller and intended to be processed by the controller, and wherein the controller signature is generated by generating a hash value of the data and encrypting the generated hash value with a private key;
verify the controller signature received from the second controller using a public key of the second controller;
transmit the data and the controller signature to a gateway of the vehicle;
receive a gateway signature from the gateway, wherein the gateway signature is generated based on at least a second portion of the data and transmitted to the controller after the gateway verifies the controller signature;
verify the gateway signature; and
in response to verifying the gateway signature, process the data.

### Claim 10 (depends on 9)

The controller of claim 9, wherein the controller, the second controller, and the gateway are connected to a bus system.

### Claim 11 (depends on 10)

The controller of claim 10, wherein the bus system is a controller-area network (CAN) bus system.

### Claim 12 (depends on 10)

The controller of claim 10, wherein the data, the controller signature, and the gateway signature are received via the bus system, and the data and the controller signature are transmitted via the bus system.

### Claim 13 (depends on 9)

The controller of claim 9, wherein the gateway signature is transmitted to the controller after the gateway verifies that the controller is authorized to receive communication from the second controller.

### Claim 14 (depends on 9)

The controller of claim 9, wherein the controller signature is generated by the second controller using a private key associated with the second controller.

### Claim 15 (depends on 9)

The controller of claim 9, wherein the vehicle is one of a car, a motorbike, a boat, or an aircraft.

### Claim 16

A non-transitory computer-readable storage medium storing instructions that when executed by a controller of a vehicle cause the controller to perform a method for communicating with a second controller of the vehicle, the method comprising:
receiving data and a controller signature from the second controller, wherein the data is destined for the controller and intended to be processed by the controller, and wherein the controller signature is generated by generating a hash value of the data and encrypting the generated hash value with a private key;
verifying the controller signature received from the second controller using a public key of the second controller;
transmitting the data and controller signature to a gateway of the vehicle;
receiving a gateway signature from the gateway, wherein the gateway signature is generated based on at least a portion of the data and transmitted to the controller after the gateway verifies the controller signature;
verifying the gateway signature; and
in response to verifying the gateway signature, processing the data.

### Claim 17 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein the controller signature is generated by the second controller using a private key associated with the second controller.

### Claim 18 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein the controller, the second controller, and the gateway are connected to a controller-area network (CAN) bus system.