# US 2025/0148134 A1 · Authenticated control sequences to initialize peripheral devices over a multi-target interface bus

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

- Number: US 2025/0148134 A1
- Document ID: US20250148134A1
- Status: Published application
- Kind: A1
- Application number: 19/015,384
- Filed: 2025-01-09
- Published: 2025-05-08
- Earliest claimed: 2023-02-24
- Assignees: NVIDIA Corporation
- Applicants: NVIDIA Corporation
- Inventors: Igor Mitsyanko; Aki Petteri Niemi; Junghyun Kim
- Web page: https://patentgrep.com/patent/US20250148134A1

## CPC

- G06F 13/1673: {using buffers}
- G06F 21/85: interconnection devices, e.g. bus-connected or in-line devices
- G06F 13/4282: {on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247)}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A controller device includes a memory storing instructions, an interface bus coupled to peripheral devices and configured to operate with a multi-target interface protocol, and a processor coupled to the memory and the interface bus. The processor broadcasts initialization data, according to the multi-target interface protocol, to the peripheral devices. The processor generates, from the initialization data, using at least one cryptographic function, an authentication tag for each peripheral device. Each authentication tag can be specific to a corresponding peripheral device. The processor creates client objects corresponding to each of the peripheral devices, each client object configured to unicast an authentication tag to the corresponding peripheral device based on a specific address. The processor unicasts, according to the multi-target interface protocol, using the client objects, each authentication tag to the corresponding peripheral device of the peripheral devices.

## Claims

### Claim 1

A controller device comprising:
a memory storing instructions;
an interface bus coupled to a plurality of peripheral devices and configured to operate with a multi-target interface protocol; and
a processor coupled to the memory and the interface bus, the processor to execute the instructions to perform operations comprising:
broadcasting initialization data, according to the multi-target interface protocol, to the plurality of peripheral devices;
generating, from the initialization data, using at least one cryptographic function, an authentication tag for each peripheral device of the plurality of peripheral devices;
creating client objects corresponding to each of the plurality of peripheral devices, each client object configured to unicast an authentication tag to the corresponding peripheral device based on a specific address generated according to the multi-target interface protocol; and
unicasting, according to the multi-target interface protocol, using the client objects, each authentication tag to the corresponding peripheral device of the plurality of peripheral devices.

### Claim 2 (depends on 1)

The controller device of claim 1, wherein the multi-target interface protocol is one of Inter-Integrated Circuit (I2C), Serial Peripheral Interface (SPI), Universal Serial Bus (USB), or Controller Area Network (CAN) communication protocol.

### Claim 3 (depends on 1)

The controller device of claim 1, further comprising a demultiplexer coupled to the interface bus and the processor, the demultiplexer configured to support the multi-target interface protocol.

### Claim 4 (depends on 1)

The controller device of claim 1, wherein generating each authentication tag further comprises:
employing a first cryptographic key associated with a first peripheral device of the plurality of peripheral devices; and
employing a second cryptographic key associated with a second peripheral device of the plurality of peripheral devices, the first cryptographic key being different than the second cryptographic key.

### Claim 5 (depends on 1)

The controller device of claim 1, wherein the operations further comprise:
registering one or more write listeners, of each client object, to monitor for and detect broadcast transactions directed at the plurality of peripheral devices; and
registering one or more read listeners, of each client object, to monitor for and detect memory transactions received from the plurality of peripheral devices.

### Claim 6 (depends on 1)

The controller device of claim 1, wherein the operations further comprise creating a plurality of peripheral device objects corresponding to respective peripheral devices of the plurality of peripheral devices, each peripheral device object associated with a write authentication buffer to store the initialization data.

### Claim 7 (depends on 6)

The controller device of claim 6, wherein each client object comprises a write listener that detects broadcast transactions associated with the initialization data, and wherein the operations further comprise registering, by each respective peripheral device object, a corresponding write listener with an original client object that is configured to broadcast the initialization data to the plurality of peripheral devices.

### Claim 8 (depends on 6)

The controller device of claim 6, wherein the initialization data is first initialization data that matches a capacity of each write authentication buffer, and wherein the operations further comprise:
detecting each write authentication buffer is at capacity;
receiving acknowledgments from the plurality of peripheral devices that the first initialization data has been authenticated;
clearing each write authentication buffer of the first initialization data; and
buffering second initialization data in each write authentication buffer broadcasted to the plurality of peripheral devices.

### Claim 9 (depends on 1)

The controller device of claim 1, wherein the initialization data is first initialization data, wherein the operations further comprise:
broadcasting second initialization data that follows the first initialization data, according to the multi-target interface protocol, to the plurality of peripheral devices;
generating, from the second initialization data, using the at least one cryptographic function, a second authentication tag for each peripheral device of the plurality of peripheral devices, wherein each second authentication tag is specific to a corresponding peripheral device of the plurality of peripheral devices; and
unicasting, according to the multi-target interface protocol, each second authentication tag to the corresponding peripheral device of the plurality of peripheral devices.

### Claim 10

A system comprising:
a plurality of peripheral devices;
an interface bus coupled to the plurality of peripheral devices and configured to operate with a multi-target interface protocol; and
a processor coupled to the interface bus, the processor to execute instructions to perform operations comprising:
broadcasting initialization data, according to the multi-target interface protocol, to the plurality of peripheral devices;
generating, from the initialization data, using at least one cryptographic function, an authentication tag for each peripheral device of the plurality of peripheral devices;
creating client objects corresponding to each of the plurality of peripheral devices, each client object configured to unicast an authentication tag to the corresponding peripheral device based on a specific address generated according to the multi-target interface protocol; and
unicasting, according to the multi-target interface protocol, using the client objects, each authentication tag to the corresponding peripheral device of the plurality of peripheral devices.

### Claim 11 (depends on 10)

The system of claim 10, wherein the multi-target interface protocol is one of Inter-Integrated Circuit (I2C), Serial Peripheral Interface (SPI), Universal Serial Bus (USB), or Controller Area Network (CAN) communication protocol.

### Claim 12 (depends on 10)

The system of claim 10, further comprising a demultiplexer coupled to the interface bus and the processor, the demultiplexer configured to support the multi-target interface protocol.

### Claim 13 (depends on 10)

The system of claim 10, wherein generating each authentication tag further comprises:
employing a first cryptographic key associated with a first peripheral device of the plurality of peripheral devices; and
employing a second cryptographic key associated with a second peripheral device of the plurality of peripheral devices, the first cryptographic key being different than the second cryptographic key.

### Claim 14 (depends on 10)

The system of claim 10, wherein the operations further comprise:
registering one or more write listeners, of each client object, to monitor for and detect broadcast transactions directed at the plurality of peripheral devices; and
registering one or more read listeners, of each client object, to monitor for and detect memory transactions received from the plurality of peripheral devices.

### Claim 15 (depends on 10)

The system of claim 10, wherein the operations further comprise creating a plurality of peripheral device objects corresponding to respective peripheral devices of the plurality of peripheral devices, each peripheral device object associated with a write authentication buffer to store the initialization data.

### Claim 16 (depends on 15)

The system of claim 15, wherein each client object comprises a write listener that detects broadcast transactions associated with the initialization data, and wherein the operations further comprise registering, by each respective client object, a corresponding write listener with an original client object that is configured to broadcast the initialization data to the plurality of peripheral devices.

### Claim 17 (depends on 15)

The system of claim 15, wherein the initialization data is first initialization data that matches a capacity of each write authentication buffer, and wherein the operations further comprise:
detecting each write authentication buffer is at capacity;
receiving acknowledgments from the plurality of peripheral devices that the first initialization data has been authenticated;
clearing each write authentication buffer of the first initialization data; and
buffering second initialization data in each write authentication buffer broadcasted to the plurality of peripheral devices.

### Claim 18 (depends on 10)

The system of claim 10, wherein the initialization data is first initialization data, wherein the operations further comprise:
broadcasting second initialization data that follows the first initialization data, according to the multi-target interface protocol, to the plurality of peripheral devices;
generating, from the second initialization data, using the at least one cryptographic function, a second authentication tag for each peripheral device of the plurality of peripheral devices, wherein each second authentication tag is specific to a corresponding peripheral device of the plurality of peripheral devices; and
unicasting, according to the multi-target interface protocol, each second authentication tag to the corresponding peripheral device of the plurality of peripheral devices.

### Claim 19

A non-transitory computer-readable storage medium storing instructions which, when executed by a processor coupled to an interface bus, cause the processor to perform operations comprising:
broadcasting initialization data, according to a multi-target interface protocol, to a plurality of peripheral devices;
generating, from the initialization data, using at least one cryptographic function, an authentication tag for each peripheral device of the plurality of peripheral devices;
creating client objects corresponding to each of the plurality of peripheral devices, each client object configured to unicast an authentication tag to the corresponding peripheral device based on a specific address generated according to the multi-target interface protocol; and
unicasting, according to the multi-target interface protocol, using the client objects, each authentication tag to the corresponding peripheral device of the plurality of peripheral devices.

### Claim 20 (depends on 19)

The non-transitory computer-readable storage medium of claim 19, wherein the multi-target interface protocol is one of Inter-Integrated Circuit (I2C), Serial Peripheral Interface (SPI), Universal Serial Bus (USB), or Controller Area Network (CAN) communication protocol.
