Database Network Router Tokenization Decoupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database applications face significant burdens and customization requirements due to their responsibility for tokenization tasks, limiting their ability to work with multiple database providers and tokenization vendors, and increasing resource usage.
Innovation Solution
The introduction of a Database Network Router (DNR) acts as an intermediary node that shifts tokenization and de-tokenization responsibilities from the application to the DNR and its software agent, allowing decoupling from the database and enabling compatibility with various tokenization APIs and vendors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the application is responsible for tokenization tasks, then data security is maintained, but the application complexity increases and customization requirements increase
Solution Approach 1:
The patent introduces a Database Network Router (DNR) as an intermediary component between the application and the database. The DNR handles all tokenization and de-tokenization operations, allowing the application to simply send queries to the DNR without managing sensitive data or tokenization logic. This resolves the contradiction by maintaining security through centralized tokenization while reducing application complexity through abstraction.
2Reliability
If the application is responsible for tokenization tasks, then data security is maintained, but the adaptability decreases due to heavy customization requirements
Solution Approach 1:
The DNR is designed as a universal intermediary that can work with multiple database providers and tokenization vendors through standardized interfaces. The system maintains security through centralized tokenization while achieving adaptability by allowing applications to interact with different database systems without customization, as the DNR handles the vendor-specific tokenization details.
3Reliability
If the application is responsible for tokenization tasks, then data security is maintained, but the resource requirements increase
Solution Approach 1:
The DNR consolidates all tokenization resource consumption into a single intermediary component rather than distributing it across multiple applications. This allows for more efficient resource management, as the DNR can cache tokenized data, maintain connection pools, and optimize tokenization operations centrally, thereby reducing overall system resource requirements while maintaining security.
4Reliability
If the application is responsible for tokenization tasks, then data security is maintained, but the productivity decreases due to additional processing steps
Solution Approach 1:
The DNR performs tokenization and de-tokenization operations transparently in the background, eliminating the need for applications to manually process these steps. The application simply sends queries to the DNR and receives results, with all security-related processing handled automatically by the intermediary, thereby improving productivity without compromising security.
Data Source
AI summary
An apparatus, computer-readable medium, and computer-implemented method for data tokenization are disclosed. The method includes receiving, at a database network router, a database access request directed to a tokenized database, the tokenized database containing one or more tokenized data values, applying one or more rules to the request, rewriting the request based on at least one of the one or more rules, such that data values being added to the database will be tokenized data values, and data values received from the database will be non-tokenized data values, and transmitting the rewritten request to the database.