Token Vault Self-Cleaning via Level Flag Storage Duration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems store all generated tokens, including unused or expired ones, indefinitely, leading to inefficient memory usage and increased costs, and lack the ability to assign contextual importance levels to tokens, resulting in inefficient token management.
Innovation Solution
A token manager is introduced to monitor and automatically remove expired or redundant tokens from the token vault, allowing resource providers to assign level flags with specific rules for managing tokens based on importance, such as deleting tokens after first use or storing them indefinitely.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all generated tokens are stored indefinitely in conventional systems, then token availability is maintained, but memory space usage increases and costs increase
Solution Approach 1:
The patent applies parameter changes by introducing level flags with different level values (1-5) that modify the storage duration parameter of tokens. Tokens are no longer stored with a fixed indefinite duration, but rather their storage duration is dynamically adjusted based on their assigned level value, resolving the contradiction between maintaining token availability and reducing memory space usage.
Solution Approach 2:
The patent implements dynamics by making the token storage duration flexible rather than static. The level flag system allows tokens to have different lifecycles (e.g., level 1 tokens stored indefinitely, level 5 tokens deleted after first use or short duration), enabling the system to adapt storage behavior to token importance and usage patterns, thus reducing overall memory space consumption while maintaining necessary token availability.
2Reliability
If all generated tokens are stored indefinitely in conventional systems, then token access is maintained, but operational costs increase
Solution Approach 1:
The patent changes the operational cost parameter by linking storage duration to token importance levels. High-importance tokens (level 1) continue to be stored indefinitely ensuring access, while low-importance tokens (level 5) are deleted after short durations or first use, significantly reducing the operational costs associated with token storage and management without compromising access to critical tokens.
Solution Approach 2:
The patent applies local quality by treating different tokens differently based on their individual importance levels rather than applying a uniform storage policy. Each token receives localized storage treatment according to its level flag, allowing the system to optimize operational costs by storing only the necessary subset of tokens indefinitely while disposing of less critical tokens.
3Reliability
If all generated tokens are stored indefinitely in conventional systems, then token supply is maintained, but the limited number of tokens is exhausted faster
Solution Approach 1:
The patent implements discarding and recovering by systematically deleting expired or low-importance tokens (level 5) from the system, thereby recovering and making available the limited token supply for new uses. This ensures that tokens are not permanently consumed by indefinitely storing low-value tokens, allowing the system to maintain token supply sustainability while still providing necessary token access for high-importance cases.
4Device complexity
If conventional systems store all tokens without contextual information, then storage simplicity is maintained, but contextual value cannot be assigned to tokens
Solution Approach 1:
The patent applies the nested doll principle by embedding level flags and contextual information within the token data structure itself. The level flag is nested as an attribute of each token, allowing the system to store contextual value information (importance level, usage characteristics) alongside the token without requiring separate complex storage structures, thus achieving adaptability while maintaining relative storage simplicity.
Data Source
AI summary
Embodiments are directed to a self-cleaning token vault for managing tokens generated on behalf of a resource provider. The generated tokens may be stored at the token vault. Embodiments provide a token manager (which can be embodied in the token vault or provided as a separate module) that continuously monitor the token vault for expired or redundant tokens. The token manager may enable the resource provider to assign level flags to the tokens and assign level values to the level flags. The level value may indicate an importance or a use characteristic of the token. Upon identifying tokens that are no longer necessary, the self-cleaning token vault or the token manager may automatically remove the tokens from the token vault.