# US 2025/0097707 A1 · Systems and methods for ledger-based cookie management

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

- Number: US 2025/0097707 A1
- Document ID: US20250097707A1
- Status: Published application
- Kind: A1
- Application number: 18/467,329
- Filed: 2023-09-14
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: T-Mobile Innovations LLC
- Applicants: T-Mobile Innovations LLC
- Inventors: Marouane BALMAKHTAR; Lyle Walter PACZKOWSKI; Galip Murat KARABULUT
- Web page: https://patentgrep.com/patent/US20250097707A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04W 12/084: using delegated authorisation, e.g. open authorisation [OAuth] protocol
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04W 12/02: Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
- H04L 67/104: Peer-to-peer [P2P] networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

In various embodiments, systems and methods for ledger-based cookie management are provided. Rather than store cookie data as text files on the local device drive, cookie data is recorded to a blockchain technology cookie ledger store on a network resource. When a client application (e.g., a browser) on the UE is directed to a cloud-based service, and that cloud-based service calls for access to a cookie, that call is processed by a cookie gateway executing on the UE. The cookie gateway may verify authenticity of the user and generate a cookie access token that it transmits to the cloud-based service. The cloud-based service may use the cookie access token to locate the cookie ledger and access one or more records storing cookie data used by the cloud-based service. The cookie access token may expire upon termination of the session between the user equipment and the cloud-based service.

## Claims

### Claim 1

A system for ledger-based cookie management, the system comprising:
one or more processors; and
one or more computer-readable media storing computer-usable instructions that, when executed by the one or more processors, cause the one or more processors to:
establish a communication session over a network between a user equipment (UE) and a cloud-based service, the UE coupled to the network through at least one access network;
activate for the UE a network service for storing cookies associated with the communication session to a network-connected cookie ledger, the network-connected cookie ledger storing a plurality of cookie records;
transport a cookie access token from the UE to the cloud-based service via the network, wherein the cookie access token identifies the network-connected cookie ledger;
receive a request from the cloud-based service to access the network-connected cookie ledger via the network, the request based at least in part on the cookie access token; and
transport, via a data channel, cookie data between the cloud-based service and the network-connected cookie ledger.

### Claim 2 (depends on 1)

The system of claim 1, the one or more processors further to:
terminate the data channel between the cloud-based service and the network-connected cookie ledger in response to a termination of the communication session.

### Claim 3 (depends on 1)

The system of claim 1, wherein the network comprises a telecommunications network, and the UE is coupled to the network through a cellular base station.

### Claim 4 (depends on 1)

The system of claim 1, wherein the cookie access token comprises a ledger reference identifier (ID) associated with the network-connected cookie ledger.

### Claim 5 (depends on 4)

The system of claim 4, wherein the ledger reference ID comprises at least one of:
a decentralized identifier (DID); and
a self-sovereign identity (SSI)-based identifier.

### Claim 6 (depends on 1)

The system of claim 1, wherein the network service establishes the data channel between the cloud-based service and the network-connected cookie ledger based at least in part on the cookie access token.

### Claim 7 (depends on 1)

The system of claim 1, wherein the network-connected cookie ledger comprises at least one of:
a Hyperledger technology-based ledger;
a blockchain technology-based ledger;
a distributed ledger network (DLN)-based ledger; and
a distributed ledger technology (DLT)-based ledger.

### Claim 8

A system for ledger-based cookie management, the system comprising:
a user equipment (UE) comprising one or more processors and one or more computer-readable media storing computer-usable instructions that, when executed by the one or more processors, cause the one or more processors to:
establish a communication session over a network between a cloud-based service and a client application of the UE, the UE coupled to the network through at least one access network;
execute a cookie service gateway in communication with the client application, wherein the cookie service gateway generates a cookie access token in response to a request from the client application for cookie data associated with the communication session, wherein the cookie access token identifies a network-connected cookie ledger; and
communicate the cookie access token to the cloud-based service.

### Claim 9 (depends on 8)

The system of claim 8, the one or more processors further to:
revoke the cookie access token in response to a termination of the communication session.

### Claim 10 (depends on 8)

The system of claim 8, the one or more processors further to:
generate the cookie access token to reference at least one cookie ledger record of the network-connected cookie ledger associated with the cookie data.

### Claim 11 (depends on 8)

The system of claim 8, wherein the ledger reference ID comprises at least one of:
a decentralized identifier (DID); and
a self-sovereign identity (SSI)-based identifier.

### Claim 12 (depends on 8)

The system of claim 8, wherein the network-connected cookie ledger comprises at least one of:
a Hyperledger technology-based ledger;
a blockchain technology-based ledger;
a distributed ledger network (DLN)-based ledger; and
a distributed ledger technology (DLT)-based ledger.

### Claim 13 (depends on 8)

The system of claim 8, the one or more processors further to:
execute a cookie service decentralized application (DApp) of the cookie service gateway in a trusted execution environment of the UE to generate the cookie access token.

### Claim 14 (depends on 13)

The system of claim 13, wherein the cookie service gateway is configured to communicate with at least one cookie access DApp used by the cloud-based service to interface with a smart contract stored in the network-connected cookie ledger.

### Claim 15 (depends on 13)

The system of claim 13, wherein the cookie service gateway is configured to communicate with at least one smart contract stored in the network-connected cookie ledger.

### Claim 16 (depends on 8)

The system of claim 8, wherein the UE further comprises a radio module, wherein the UE establishes the communication session over the network via the radio module.

### Claim 17

A method for ledger-based cookie management, the method comprising:
establishing a communication session over a network between a client application executing on a user equipment (UE) and a cloud-based service;
controlling the client application to request access to cookie data associated with the communication session with the cloud-based service;
receiving a cookie access token from the UE, wherein the cookie access token identifies a network-connected cookie ledger comprising one or more cookie records associated with the cookie data;
communicating with the network-connected cookie ledger to activate a smart contract associated with at least one cookie record of the one or more cookie records based on the cookie access token; and
controlling one or more functions of the smart contract to communicate the cookie data between the cloud-based service and the network-connected cookie ledger.

### Claim 18 (depends on 17)

The method of claim 17, wherein the at least one cookie record of the one or more cookie records is associated with a ledger reference identifier provided by the cookie access token.

### Claim 19 (depends on 17)

The method of claim 17, the method further comprising:
executing at least one decentralized application (DApp) based on the cookie access token to exchange the cookie data between the cloud-based service and the network-connected cookie ledger.

### Claim 20 (depends on 17)

The method of claim 17, wherein the network-connected cookie ledger comprises at least one of:
a Hyperledger technology-based ledger;
a blockchain technology-based ledger;
a distributed ledger network (DLN)-based ledger; and
a distributed ledger technology (DLT)-based ledger.
