Bulk Token Migration With Active-Token Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Migrating user identification tokens between transaction processing entities is tedious and resource-intensive, requiring significant memory and processor resources due to the token-by-token exchange process.
Innovation Solution
A system that disassociates and migrates user tokens in bulk from a first entity to a second entity, excluding inactive tokens and activating only active tokens for verification, thereby reducing memory and processor resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If token-by-token migration is performed, then complete token migration is achieved, but memory and processor resources are significantly consumed
Solution Approach 1:
The patent merges multiple individual token migration operations into a single bulk migration operation. Instead of processing each token separately with individual electronic messages, the system consolidates thousands of tokens into one migration batch, dramatically reducing the number of communication rounds and resource consumption while maintaining complete migration of all tokens.
Solution Approach 2:
The patent creates a universal bulk migration command that handles multiple token types and states (active, inactive, suspended) in a single operation. The system performs multiple functions simultaneously: filtering inactive tokens, migrating active tokens, and updating entity associations all through one bulk process rather than separate operations for each token.
2Measurement precision
If token-by-token migration is performed, then each token can be individually verified, but the migration process is extremely time-consuming
Solution Approach 1:
The patent combines individual token verification steps into a single bulk verification process. The system sends one migration command that triggers verification for all tokens simultaneously at the central token database server, rather than sequentially verifying each token, thus maintaining verification accuracy while reducing total migration time from potentially days to minutes.
Solution Approach 2:
The system performs preliminary filtering of inactive tokens before the bulk migration execution. By identifying and excluding inactive, suspended, or expired tokens in advance using inclusion/exclusion criteria, the system prepares a refined list of only migratable tokens, which accelerates the subsequent bulk verification and migration process.
3Reliability
If all user tokens are processed including inactive ones, then comprehensive token management is achieved, but resource consumption increases unnecessarily
Solution Approach 1:
The patent extracts and separates inactive tokens (suspended, expired, or invalid) from the total token set before bulk migration. By applying exclusion criteria to filter out tokens that cannot be migrated, the system processes only the necessary subset of active tokens, reducing data processing volume by potentially 90% or more while maintaining complete management of all relevant tokens.
Solution Approach 2:
The system performs partial processing by selectively migrating only active tokens rather than all tokens. This partial action approach processes exactly the right amount of data needed (active tokens) without the excessive processing of inactive tokens, optimizing resource utilization while achieving the migration goal.
Data Source
AI summary
A system that can, using reduced memory and processor resources, receive a list including active and inactive user tokens associated with a first entity, cause a central token database server to disassociate the stored user tokens associated with the first entity, subsequently receive a bulk file containing a listing of disassociated user tokens from the central token database server, compare the listing of disassociated user tokens identified in the bulk file with the list of user tokens, and in response, extract the active user tokens in the bulk file. The system can additionally cause the central token database server to associate the active user tokens with a second entity, receive confirmation of association from the central token database server, and output a command to activate at the second entity, user accounts that will use the extracted active user tokens for identity verification during processing of user electronic transactions.