Distributed Tokenization Collision Avoidance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data protection techniques face challenges in minimizing processing and storage burdens while improving security and tracking data use information, often failing to effectively manage token collisions in distributed tokenization environments.
Innovation Solution
A central token management system is implemented to manage tokens generated by clients, avoiding collisions by determining whether candidate tokens cause collisions with tokens from other clients, and by assigning unique ranges of candidate token values to each client to ensure non-colliding tokens.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a distributed tokenization environment is used to protect data across multiple clients, then data protection coverage is improved, but token collisions between different clients occur
Solution Approach 1:
The patent combines distributed token generation capabilities with a centralized collision detection system. Multiple clients can independently generate tokens (distribution), but a central authority coordinates and detects collisions (centralization), merging the benefits of both approaches to resolve the contradiction between coverage and uniqueness.
Solution Approach 2:
The system implements feedback mechanisms where clients report generated tokens to a central registry, which provides feedback about collisions. This feedback loop allows clients to adjust their token generation strategies in real-time, ensuring uniqueness while maintaining distributed operation.
2Reliability
If extensive computing resources are used to encode and decode data, then data security is improved, but processing burden increases
Solution Approach 1:
The patent segments the heavy computational burden of token management into separate functions: clients perform lightweight token generation and encoding, while a central server handles collision detection and coordination. This segmentation allows security to be maintained without each client bearing the full processing burden.
Solution Approach 2:
A central token management server acts as an intermediary between clients, handling the computationally intensive tasks of collision detection and coordination. This mediator approach allows clients to maintain security through proper token usage while offloading processing burdens to the central system.
3Reliability
If distinct systems are used to store protected data in distinct repositories, then data isolation security is improved, but storage and processing burden increases
Solution Approach 1:
The patent creates a universal token management system that serves multiple functions: it maintains data isolation by allowing distinct repositories, provides centralized collision detection, and coordinates token generation across all clients. This multi-functional approach reduces overall system complexity while maintaining security benefits.
Data Source
AI summary
A client receives sensitive data to be tokenized. The client queries a token table with a portion of the sensitive data to determine if the token table includes a token mapped to the value of the portion of the sensitive data. If the mapping table does not include a token mapped to the value of the portion of the sensitive data, a candidate token is generated. The client queries a central token management system to determine if the candidate token collides with a token generated by or stored at another client. In some embodiments, the candidate token includes a value from a unique set of values assigned by the central token management system to the client, guaranteeing that the candidate token does not cause a collision. The client then tokenizes the sensitive data with the candidate token and stores the candidate token in the token table.