Systems and methods for ledger-based cookie management
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.
1 . A system for ledger-based cookie management, the system comprising:
one or more processors; and
one or more non-transient computer storage 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;
execute a gateway at the UE, wherein the gateway generates a cookie access token in response to receiving an authentication of a user of the UE, wherein the cookie access token comprises an authorization for the cloud-based service to access cookie data from the network-connected cookie ledger storing the plurality of cookie records;
transport the 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, wherein the cookie access token expires upon termination of the communication session.
2 . 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.
3 . 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.
4 . The system of claim 1 , wherein the cookie access token comprises a ledger reference identifier (ID) associated with the network-connected cookie ledger.
5 . 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.
6 . 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.
7 . 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.
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 at the UE, wherein the cookie service gateway is 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 and further in response to receiving an authentication of a user of the UE, wherein the cookie access token comprises an authorization for a cloud-based service to access cookie data from a network-connected cookie ledger storing a plurality of cookie records, wherein the cookie access token identifies the network-connected cookie ledger; and
communicate the cookie access token to the cloud-based service, wherein the cookie access token expires upon termination of the communication session.
9 . 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.
10 . 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.
11 . 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.
12 . 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.
13 . The system of claim 12 , 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.
14 . The system of claim 12 , wherein the cookie service gateway is configured to communicate with at least one smart contract stored in the network-connected cookie ledger.
15 . 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.
16 . 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, from the UE, a cookie access token generated by a cookie service gateway at the UE in response to receiving an authentication of a user of the UE, wherein the cookie access token comprises an authorization for the cloud-based service to access cookie data from a network-connected cookie ledger storing one or more cookie records associated with the cookie data and identifies the network-connected cookie ledger;
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, wherein the cookie access token expires upon termination of the communication session.
17 . The method of claim 16 , 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.
18 . The method of claim 16 , 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.
19 . The method of claim 16 , 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.