Mirrored Token Vault Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional token processing systems are inefficient due to centralized storage of tokens, leading to potential data compromise and lack of comprehensive information for informed transaction decisions, with limited redundancy and fraud prevention.
Innovation Solution
Implementing a system where tokens and associated data are stored at multiple locations managed by different entities, with continuous synchronization between a primary and secondary token vault, allowing for division of processing responsibilities and enhanced fraud prevention through separate data analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If tokens are stored at a single centralized location, then the system is simpler to manage, but the system becomes vulnerable to data compromise and lacks redundancy
Solution Approach 1:
The patent divides the centralized token vault into multiple distributed token vaults (first token vault, second token vault, third token vault) managed by different entities. Each vault stores a portion of token data, and the system uses multiple authorization entities (first, second, third) to process transactions. This segmentation eliminates single-point failure and reduces the impact of any single vault compromise.
Solution Approach 2:
The patent introduces intermediary components including a token service provider that coordinates between multiple vaults, and uses encrypted token requests that are routed through multiple entities. The authorization process involves multiple intermediaries (different authorization entities) that collectively verify transactions without any single entity having complete access to all token data.
2Ease of operation
If the token service provider has complete information about all accounts, then transaction decisions can be made centrally, but the provider cannot access information about accounts issued by other entities
Solution Approach 1:
The patent creates a universal system where multiple authorization entities (first, second, third) each have specialized knowledge of different account types and issuers. The token vault system is designed to be multi-functional, serving both as a storage mechanism and as a coordination platform that enables any authorization entity to verify tokens issued by any other entity through the distributed vault structure.
Solution Approach 2:
The patent implements feedback mechanisms where authorization entities query the distributed token vaults and receive responses about token validity. The system uses encrypted token requests and responses that flow back through the network, allowing each authorization entity to obtain necessary information about accounts issued by other entities through the coordinated vault queries.
3Productivity
If all token data is stored in one vault, then data access is efficient, but a hack compromises all sensitive information
Solution Approach 1:
The patent segments token data storage across multiple vaults (first, second, third token vaults) managed by different entities. Each vault contains a subset of token information, so that compromise of one vault does not expose all sensitive data. The segmentation is implemented through distributed storage architecture where token mappings are split across multiple secure locations.
Solution Approach 2:
The patent applies local quality by giving each token vault specialized characteristics and storing different types or portions of token data in different vaults. Each authorization entity has local access optimized for its specific function, while the overall system maintains security through the distributed architecture where no single vault contains all sensitive information.
Data Source
AI summary
Embodiments are directed to a first token vault managed by a token service provider and a second token vault managed by a second entity. The first token vault is continuously synchronized with the second token vault in real-time. That is, the data in the second token vault is updated simultaneously with or immediately after the data in the first token vault is updated. In some embodiments, the first token vault may be a master token vault and the second token vault may be a mirror token vault. The mirror token vault may store the same information as the master token vault. Alternatively, the mirror token vault may store a subset of the information stored at the master token vault. In other embodiments, the information stored at the first token vault and the information stored at the second token vault may be mutually exclusive.