Token Linking via Stable Alias for Anonymous Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for managing user anonymity in network interactions face challenges in linking user data across different servers while maintaining security and privacy, particularly in advertising and content delivery, as they often rely on third-party cookies or intermediate network devices that compromise user anonymity and security.
Innovation Solution
A method that involves a server receiving a first token associated with a user account, determining a stable alias, and providing a second token linked to the alias, allowing clients to link the first token with data without knowledge of the stable alias, enabling anonymous data linking and improved user security and privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If third-party cookies are used to link user data across servers, then data consistency and user identification are improved, but user anonymity and security are compromised
Solution Approach 1:
The patent introduces a server as an intermediary that receives first tokens from clients, determines stable aliases, and provides second tokens. This intermediary server enables data linking across servers without requiring clients to directly share or store third-party cookies, thus maintaining user anonymity while achieving data consistency. The stable alias acts as a mediator between the transient first token and the persistent user identity.
Solution Approach 2:
The patent segments the identification process into multiple components: first tokens (transient, client-specific), stable aliases (persistent, server-managed), and second tokens (derived, usable across contexts). This segmentation allows different parts of the system to use appropriate identifiers for their needs while the server coordinates them, enabling data consistency without exposing the full identification chain to any single client.
2Object-affected harmful factors
If temporary tokens are assigned to users for anonymous interactions, then user security and privacy are improved, but the ability to store and access user data across sessions is worsened
Solution Approach 1:
The server performs preliminary actions by determining the stable alias associated with a first token before providing a second token. This preliminary determination of the stable alias enables subsequent data storage and retrieval operations to be performed consistently across sessions. The stable alias is established in advance as the key for persistent data storage, while the first token remains transient for security.
Solution Approach 2:
The stable alias acts as an intermediary between the transient first token and the persistent data storage requirements. The server uses the stable alias as a key to store and retrieve user data, while clients only interact with the transient first token or the derived second token. This intermediary mechanism enables data accessibility across sessions without requiring clients to manage persistent identifiers directly.
3Adaptability or versatility
If multiple servers need to access the same user data, then service consistency is improved, but user anonymity is compromised due to identifier sharing
Solution Approach 1:
The patent introduces the server and stable alias as an intermediary layer between multiple client servers. Instead of client servers directly sharing third-party cookies or user identifiers, they each independently interact with the central server using their own first tokens. The central server translates these to second tokens based on the stable alias, enabling service consistency without direct identifier sharing between client servers.
Solution Approach 2:
The server creates copies of the identification mechanism tailored to each client's context. Each client receives a second token that is derived from the stable alias but is specific to that client's interactions. This copying approach allows multiple servers to access user data consistently while each server only possesses its own copy of the token, preventing unauthorized sharing or exposure of the underlying stable alias.
Data Source
Figure 1A~1B
Figure 2A
Figure 2B
AI summary
A method of a server 100 enabling a client 130 to link data with a token associated with a user account is provided. The method comprises receiving a first token associated with the user account. The method further comprises determining a stable alias associated with the token, wherein the stable alias is associated with the user account. The method further comprises determining a second token associated with the stable alias. The method further comprises providing the second token to the client 130. One of the first token and the second token are associated with data, such that providing the second token to the client enables the client to link the other of the first token and the second token with the data, without knowledge of the stable alias.