Automated Access Data Change Detection via Pattern Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of updating account information across multiple entities is inefficient, leading to obsolete information being used, which results in declined access requests and unnecessary processing loads on computer systems.
Innovation Solution
A method where a server computer identifies recurring access requests and automatically transmits updated account information to associated resource provider computers, reducing the need for manual updates and minimizing obsolete data usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual account information update process is used across multiple entities, then users can update their information, but the process becomes time-consuming and cumbersome
Solution Approach 1:
The system enables automatic detection and propagation of account information changes without requiring user intervention. When account information is updated at one entity, the system automatically identifies and notifies other entities that store the same account information, allowing the system to serve itself rather than requiring manual user updates at each entity.
Solution Approach 2:
A central system acts as an intermediary between multiple entities to coordinate account information updates. This intermediary system receives notifications of account information changes, identifies which entities need updates, and automatically propagates the changes, eliminating the need for users to manually contact each entity.
2Reliability
If users manually update account information at each entity, then all entities can have current information, but the process is inefficient and repetitive
Solution Approach 1:
The system automatically ensures all entities have current account information through machine-to-machine communication. When an update occurs, the system self-propagates the information to all relevant entities without requiring repetitive manual intervention, maintaining information reliability while dramatically improving efficiency.
Solution Approach 2:
The system pre-identifies which entities store account information for a user by analyzing access request patterns. This preliminary mapping allows the system to quickly notify only the relevant entities when an update occurs, rather than requiring users to manually update all possible entities.
3Productivity
If obsolete account information is used by entities, then access requests may be processed, but the requests are ultimately declined and computing resources are wasted
Solution Approach 1:
The system implements a feedback mechanism where entities notify the central system when account information changes. This feedback loop allows the system to proactively update all relevant entities before they attempt to process access requests with obsolete information, preventing wasted computing resources on doomed transactions.
Solution Approach 2:
The system performs preliminary updates of account information across all entities before access requests are made. By proactively propagating changes and ensuring all entities have current information beforehand, the system prevents the processing of access requests that would ultimately be declined due to obsolete data.
4Adaptability or versatility
If users have account information stored by multiple entities, then service availability is improved, but the complexity of managing updates across all entities increases
Solution Approach 1:
A central system acts as an intermediary that manages the complexity of coordinating updates across multiple entities. Users interact with this intermediary, which then handles the complex task of identifying and notifying all entities that store the user's account information, simplifying the user experience while maintaining service availability across multiple entities.
Solution Approach 2:
The system automatically manages the complexity of multi-entity account information management through self-service mechanisms. When account information is updated, the system autonomously identifies which entities need updates and propagates the changes, eliminating the need for users to manually manage updates across multiple entities while preserving broad service availability.
Data Source
AI summary
A user may conduct a plurality of access requests with a plurality of resource provider computers. A processor server computer may determine whether resource provider computers store access data associated with the user in various ways, including detecting patterns in sets of a plurality of access requests conducted between the user and each of the plurality of resource provider computers. Upon detecting that access data has changed, the processor server computer may automatically send the updated access data to each of the identified resource provider computer.