# US 2026/0254639 A1 · Llm protection through end-to-end crypto broadcasing protocols

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

- Number: US 2026/0254639 A1
- Document ID: US20260254639A1
- Status: Published application
- Kind: A1
- Application number: 19/062,268
- Filed: 2025-02-25
- Published: 2026-08-27
- Earliest claimed: 2025-02-25
- Assignees: Lenovo (United States) Inc.
- Applicants: Lenovo (United States) Inc.
- Inventors: Christian De Hoyos; Igor Stolbikov; Scott Li; Joshua N. Novak; Scott Kelso
- Web page: https://patentgrep.com/patent/US20260254639A1

## CPC

- H04L 9/3093: {involving Lattices or polynomial equations, e.g. NTRU scheme}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 9/0822: {using key encryption key}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/0869: {involving random numbers or seeds}
- H04L 63/045: {wherein the sending and receiving network entities apply hybrid encryption, i.e. combination of symmetric and asymmetric encryption (cryptographic mechanisms or cryptographic arrangements using a plurality of keys or algorithms H04L9/14)}
- H04L 9/0866: {involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics}
- H04L 9/3066: {involving algebraic varieties, e.g. elliptic or hyper-elliptic curves}
- H04L 9/3247: {involving digital signatures}
- H04L 2463/062: applying encryption of the keys
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one aspect, a system is implemented for large language model (LLM) protection through end-to-end cryptography broadcasting protocols. The system uses an elliptic-curve cryptography (ECC) broadcast schema and post-quantum module lattice-based key encapsulation mechanism (ML-KEM) encapsulation for LLM file distribution. The system can include one or both of the client device(s) and cloud-based server(s) that communicate with each other for download of the LLM files to the client device(s).

## Claims

### Claim 1

An apparatus, comprising:
a processor system; and
storage accessible to the processor system and comprising instructions executable by the processor system to:
send, from a first device to a second device, a request related to acquisition of a large language model (LLM);
send, from the first device to the second device, a device identifier (ID) and an LLM protection key, the LLM protection key as sent to the second device being encapsulated with a public module lattice-based key encapsulation mechanism (ML-KEM) key associated with the second device;
in response to the request, receive, from the second device, a signed uniform resource locator (URL) and encryption header data for decrypting files related to the LLM;
download the files related to the LLM to the first device from a location accessible via the signed URL;
receive a command to access the LLM; and
responsive to receipt of the command, use the encryption header data to decrypt the files related to the LLM.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the instructions are executable to:
use an upload protection key indicated via the encryption header data to decrypt the files related to the LLM.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the upload protection key is a master key.

### Claim 4 (depends on 2)

The apparatus of claim 2, wherein the instructions are executable to:
determine the upload protection key using a private ML-KEM key associated with the first device and using a private elliptic-curve cryptography (ECC) key associated with the first device.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the instructions are executable to:
encapsulate the LLM protection key with the public ML-KEM key associated with the second device.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the LLM protection key is a 256-bit key.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the instructions are executable to:
prior to sending the request, generate the LLM protection key.

### Claim 8 (depends on 7)

The apparatus of claim 7, wherein the LLM protection key is generated as a secure random value.

### Claim 9

A method, comprising:
receiving, from a first device and at a second device, a request related to acquisition of a large language model (LLM);
receiving, from the first device and at the second device, a device identifier (ID) and an LLM protection key;
encrypting an access key using a private elliptic-curve cryptography (ECC) key associated with the second device, the access key being usable to decrypt the files related to the LLM;
encapsulating the encrypted access key using a public module lattice-based key encapsulation mechanism (ML-KEM) key associated with the first device; and
in response to receiving the request, sending, from the second device to the first device, both a uniform resource locator (URL) for downloading the files related to the LLM and the encapsulated, encrypted access key.

### Claim 10 (depends on 9)

The method of claim 9, wherein the encapsulated, encrypted access key is indicated as part of encryption header data.

### Claim 11 (depends on 9)

The method of claim 9, comprising:
decapsulating the LLM protection key using a private ML-KEM key associated with the second device.

### Claim 12

An apparatus, comprising:
at least one computer readable storage medium (CRSM) that is not a transitory signal, the at least one CRSM comprising instructions executable by a processor system to:
use an elliptic-curve cryptography (ECC) broadcast schema and post-quantum module lattice-based key encapsulation mechanism (ML-KEM) encapsulation for file distribution.

### Claim 13 (depends on 12)

The apparatus of claim 12, wherein the file distribution relates to large language model (LLM) distribution.

### Claim 14 (depends on 12)

The apparatus of claim 12, wherein the instructions are executable to:
send, from a first device to a second device, a request related to acquisition of a large language model (LLM);
send, from the first device to the second device, a device identifier (ID) and an LLM protection key, the LLM protection key as sent to the second device being encapsulated with a public ML-KEM key associated with the second device;
in response to the request, receive, from the second device, a signed uniform resource locator (URL) and encryption header data for decrypting files related to the LLM;
download the files related to the LLM to the first device from a location accessible via the signed URL; and
use the encryption header data to decrypt the files related to the LLM.

### Claim 15 (depends on 14)

The apparatus of claim 14, wherein the instructions are executable to:
use an upload protection key indicated via the encryption header data to decrypt the files related to the LLM.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the instructions are executable to:
determine the upload protection key using a private ML-KEM key associated with the first device and using a private ECC key associated with the first device.

### Claim 17 (depends on 14)

The apparatus of claim 14, comprising the first device.

### Claim 18 (depends on 14)

The apparatus of claim 14, wherein the instructions are executable to:
receive a command to access the LLM; and
responsive to receipt of the command, use the encryption header data to decrypt the files related to the LLM.

### Claim 19 (depends on 12)

The apparatus of claim 12, wherein the instructions are executable to:
receive, from a first device and at a second device, a request related to acquisition of a large language model (LLM);
receive, from the first device and at the second device, a device identifier (ID) and an LLM protection key;
encrypt an access key using a private ECC key associated with the second device, the access key being usable to decrypt the files related to the LLM;
encapsulate the encrypted access key using a public ML-KEM key associated with the first device; and
send, from the second device to the first device, both a uniform resource locator (URL) for downloading the files related to the LLM and the encapsulated, encrypted access key.

### Claim 20 (depends on 19)

The apparatus of claim 19, wherein the instructions are executable to:
decapsulate the LLM protection key using a private ML-KEM key associated with the second device.
