# US 2026/0019281 A1 · Systems and methods for generating a device certificate defining privileges of a secondary controller by a primary controller

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

- Number: US 2026/0019281 A1
- Document ID: US20260019281A1
- Status: Published application
- Kind: A1
- Application number: 19/336,195
- Filed: 2025-09-22
- Published: 2026-01-15
- Earliest claimed: 2020-11-10
- Assignees: Thirdwayv, Inc.
- Applicants: Thirdwayv, Inc.
- Inventors: Michael Atef Ayoub; Nabil Wasily
- Web page: https://patentgrep.com/patent/US20260019281A1

## CPC

- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- G16H 20/17: delivered via infusion or injection
- G16H 40/63: for local operation
- G16H 40/67: for remote operation
- G06F 21/33: using certificates
- G06F 21/44: Program or device authentication
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 2221/2143: Clearing memory, e.g. to prevent the data from being stolen
- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/126: {the source of the received data}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems, methods and devices for generating a device certificate for determining control privileges for a primary controller and a secondary controller. The system may also include an embedded device. The primary controller may include a first memory configured to store a root certificate that includes a first set of device control privileges, and a first processor coupled to the first memory. The first processor may be configured to determine that the first set of device control privileges allow the primary controller to generate a device certificate for the secondary controller, generate the device certificate with a second set of device control privileges, and assign the device certificate to the secondary controller. The first processor may be configured to issue or send the device certificate to the secondary controller and send a public key of the root certificate to the embedded device to verify the device certificate.

## Claims

### Claim 1

A system for generating a device certificate for determining control privileges for controllers, comprising:
an embedded device having an embedded device processor; and
a plurality of controllers including a primary controller and a secondary controller, the primary controller including:
a first memory configured to store a root certificate that includes a first set of device control privileges; and
a first processor coupled to the first memory and configured to:
determine that the first set of device control privileges allow the primary controller to generate a device certificate for the secondary controller,
generate the device certificate with a second set of device control privileges, and
issue or send the device certificate to the secondary controller.

### Claim 2 (depends on 1)

The system of claim 1, wherein the first processor is further configured to digitally sign the device certificate prior to issuing or sending the device certificate to the secondary controller using a private key of the root certificate, and send a public key of the root certificate to the embedded device to verify the device certificate.

### Claim 3 (depends on 2)

The system of claim 2, wherein the embedded device has an embedded device memory that is configured to store the public key of the root certificate and an embedded device processor, wherein the embedded device processor of the embedded device is configured to:
receive the public key of the root certificate;
receive the device certificate;
determine that the device certificate is valid using the public key of the root certificate to authenticate the secondary controller; and
allow the secondary controller to access the embedded device based on the second set of device control privileges when the first set of device control privileges permit access by the secondary controller.

### Claim 4 (depends on 3)

The system of claim 3, wherein to determine that the device certificate is valid, the embedded device processor of the embedded device is configured to validate a digital signature on the device certificate using the public key of the root certificate.

### Claim 5 (depends on 2)

The system of claim 2, wherein the embedded device limits operation of the embedded device by the secondary controller based on the second set of device control privileges and limits operations of the embedded device by the primary controller based on the first set of device control privileges, wherein the second set of device control privileges is a subset of the first set of device control privileges.

### Claim 6 (depends on 1)

The system of claim 1, wherein the first processor of the primary controller is configured to:
revoke the device certificate;
add the device certificate to a revocation list; and
send the revocation list to the embedded device.

### Claim 7 (depends on 6)

The system of claim 6, wherein the embedded device processor of the embedded device is configured to:
determine that the device certificate is invalid based on the revocation list; and
deny or prevent access to the embedded device by the secondary controller based on the determination.

### Claim 8 (depends on 1)

The system of claim 1, wherein the first processor is further configured to assign the device certificate to the secondary controller.

### Claim 9

A system for generating a device certificate for determining control privileges for controllers, comprising:
an embedded device having an embedded device processor; and
a plurality of controllers including a primary controller and a secondary controller, the primary controller including:
a first memory configured to store a root certificate that includes a first set of device control privileges; and
a first processor coupled to the first memory and configured to:
determine that the first set of device control privileges allow the primary controller to generate a device certificate for the secondary controller,
generate the device certificate with a second set of device control privileges,
assign the device certificate to the secondary controller,
issue or send the device certificate to the secondary controller, and
send a public key of the root certificate to the embedded device to verify the device certificate.

### Claim 10 (depends on 9)

The system of claim 9, wherein the first processor is configured to digitally sign the device certificate prior to issuing or sending the device certificate to the secondary controller using a private key of the root certificate.

### Claim 11 (depends on 10)

The system of claim 10, wherein the embedded device has an embedded device memory that is configured to store the public key of the root certificate and an embedded device processor, wherein the embedded device processor of the embedded device is configured to:
receive the public key of the root certificate;
receive the device certificate;
determine that the device certificate is valid using the public key of the root certificate to authenticate the secondary controller; and
allow the secondary controller to access the embedded device based on the second set of device control privileges when the first set of device control privileges permit access by the secondary controller.

### Claim 12 (depends on 11)

The system of claim 11, wherein to determine that the device certificate is valid, the embedded device processor of the embedded device is configured to validate a digital signature on the device certificate using the public key of the root certificate.

### Claim 13 (depends on 10)

The system of claim 10, wherein the embedded device limits operation of the embedded device by the secondary controller based on the second set of device control privileges and limits operations of the embedded device by the primary controller based on the first set of device control privileges, wherein the second set of device control privileges is a subset of the first set of device control privileges.

### Claim 14 (depends on 9)

The system of claim 9, wherein the first processor of the primary controller is configured to:
revoke the device certificate;
add the device certificate to a revocation list; and
send the revocation list to the embedded device.

### Claim 15 (depends on 14)

The system of claim 14, wherein the embedded device processor of the embedded device is configured to:
determine that the device certificate is invalid based on the revocation list; and
deny or prevent access to the embedded device by the secondary controller based on the determination.

### Claim 16

An identification and authentication system comprising:
a plurality of controllers including a first controller and a second controller; and
an embedded device including:
an embedded device memory configured to store a first long-term shared secret; and
an embedded device processor configured to:
derive a second long-term shared secret using the first long-term shared secret,
obtain a third long-term shared secret from the second controller, and
authenticate the second controller when the second long-term shared secret matches the third long-term shared secret.

### Claim 17 (depends on 16)

The identification and authentication system of claim 16, wherein the first controller includes:
a first memory configured to store the first long-term shared secret; and
a first processor configured to:
derive the third long-term shared secret using the first long-term shared secret, and
provide the third long-term shared secret to the second controller.

### Claim 18 (depends on 17)

The identification and authentication system of claim 17, wherein the second controller includes:
a second memory configured to store the third long-term shared secret; and
a second processor configured to provide the third long-term shared secret to the embedded device.

### Claim 19 (depends on 18)

The identification and authentication system of claim 18, wherein the first processor of the first controller is configured to derive the third long-term shared secret further using an identifier of the second controller including a Bluetooth Low Energy (BLE) Media-Access-Control (MAC) address or a nonce.

### Claim 20 (depends on 19)

The identification and authentication system of claim 19, wherein the embedded device processor of the embedded device is configured to derive the second long-term shared secret further using the identifier of the second controller and independently of the derivation of the third long-term shared secret derived by the first controller.
