Format-Preserving Date Tokenization Without Centralized Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing format-preserving solutions face challenges in adequately preserving calendar dates across various components that integrate applications and databases, as they require centralized servers for tokenization and detokenization, leading to inefficiencies and platform component constraints.
Innovation Solution
A decentralized system where each software connector generates its own shuffled date table from centrally defined parameters, allowing local tokenization and detokenization of calendar dates, ensuring consistency and reproducibility across disparate containers and platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If centralized server tokenization is used, then security and fault tolerance are improved, but network delays and system complexity increase
Solution Approach 1:
The patent divides the centralized tokenization system into distributed components. Each software connector generates and stores its own date table locally, eliminating the need for a central tokenization server. This segmentation reduces network dependencies and delays while maintaining security through distributed architecture.
Solution Approach 2:
Each software connector performs self-service by autonomously generating its own date table from centrally defined parameters and handling local tokenization/detokenization operations without requiring centralized server intervention. This self-service capability eliminates network delays while maintaining consistency across the system.
2Stability of the object's composition
If centralized tokenization server is used, then consistency is improved, but device complexity and scaling limitations increase
Solution Approach 1:
The patent creates a universal date table generation mechanism where centrally defined parameters are distributed to multiple software connectors. Each connector independently generates consistent date tables using the same parameters, enabling universal interoperability across different platforms and components without requiring a centralized server.
Solution Approach 2:
The patent extracts the date table generation logic from the centralized server architecture and embeds it directly into each software connector. This extraction eliminates the need for complex centralized server infrastructure while maintaining date format consistency through parameter distribution.
3Reliability
If format-preserving tokenization is implemented, then data privacy compliance is improved, but interoperability across platforms becomes more difficult
Solution Approach 1:
The patent uses parameter changes to achieve format-preserving tokenization. By modifying date values through mathematically equivalent transformations that preserve the date format structure, the system maintains PCI DSS compliance while ensuring tokens remain valid dates that can be universally processed across different platforms and applications.
Data Source
AI summary
Provided is a system and method for format preserving tokenization of calendar dates, whereby disparate software connectors of a product suite each receive parameters from a global policy, individually generate a look-up date table from these parameters, shuffle the date tables in a reproduceable manner in accordance with the policy, and then tokenize to produce a shuffled date table, and detokenize sensitive date data with it separately. The connectors are a family of software components associated with a product suite that integrate applications and databases with encryption, tokenization and cryptographic key operations. The shuffled date table is uniquely and locally generated on a connector to support cross platform integrations of various disparate containers, each with their own programming language, Application Programming Interface (API), and user supplied information. Other embodiments disclosed.