Hybrid Cloud Tokenization with Real-Time and Batch Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing tokenization systems face inefficiencies and delays when off-premises systems need real-time access to on-premises token databases, leading to synchronization challenges and security complexities, especially in hybrid cloud environments.
Innovation Solution
A system comprising a real-time tokenization server in a public cloud with an API endpoint and a batch tokenization server, along with local databases, ensures synchronized token generation and distribution across on-premises and off-premises systems, using a real-time and batch tokenization approach to maintain coherence in the token database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If obfuscation or masking is employed to conceal sensitive information, then security is improved, but data usability is worsened
Solution Approach 1:
The patent creates tokenized copies of sensitive data that preserve the original data's structure and relationships while replacing actual sensitive values with tokens. These tokenized copies can be safely used in public clouds for machine learning training and testing, maintaining data usability while ensuring security. The tokenization process generates surrogate data that mimics the statistical properties and patterns of the original sensitive data without containing the actual sensitive information.
2Reliability
If data is tokenized and stored in secure on-premises systems, then security is improved, but access speed for off-premises systems is worsened
Solution Approach 1:
The patent introduces a tokenization service as an intermediary between on-premises secure data stores and off-premises public cloud systems. This service receives requests from public clouds, performs tokenization on-demand, and returns tokenized data without requiring direct access to the secure on-premises systems. This mediator approach enables fast access for off-premises systems while maintaining the security boundaries of on-premises infrastructure.
3Productivity
If batch tokenization is used to process data, then processing efficiency is improved, but real-time access is worsened
Solution Approach 1:
The patent implements a dynamic tokenization architecture that can adapt its processing mode based on request characteristics. For high-volume, non-critical operations, it uses batch tokenization to maximize processing efficiency. For time-sensitive requests requiring immediate tokenization, it switches to on-demand real-time processing. This dynamic approach allows the system to optimize between batch processing efficiency and real-time responsiveness depending on the specific operational context.
Data Source
AI summary
Computer-implemented systems and methods for tokenization. The system includes a network, at least one token database coupled to the network, and a batch tokenization server coupled to the at least one token database via the network, the server having a token table. The server is configured to receive at least one batch request comprising a delta table. In response to the batch request, the server retrieves a plurality of recent tokens from the at least one token database and updates the token table with the plurality of recent tokens. The server determines whether at least one payload to be tokenized from the delta table has a respective at least one corresponding entry in the token table. For each of the at least one corresponding entry that is not found in the token table, the server generates a new token and updates the at least one token database.