Adaptive Routing for Multi-System Account Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service companies face difficulties in determining the appropriate back-end systems to access for customer account requests due to changing system topologies and numerous potential back-end systems, making it challenging to manage and route requests effectively.
Innovation Solution
A system that uses a routing information structure to match parameter values from account requests with a dynamic list of cases, where the cases are updated based on success and failure counters, and priority values to identify the correct back-end system, adapting to changes in the back-end systems' topology.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the web portal accesses multiple back-end systems to retrieve customer information, then the system can handle diverse account requests, but the complexity of tracking and determining which back-end system to access increases significantly
Solution Approach 1:
The patent introduces a routing information structure as an intermediary component that sits between the web portal and multiple back-end systems. This routing structure maintains case information including parameter values and routing information, acting as a mediator that simplifies the portal's task of determining which back-end system to access by providing a centralized lookup mechanism.
Solution Approach 2:
The system performs preliminary actions by pre-storing case information in the routing information structure before requests arrive. Each case contains parameter values and corresponding routing information, allowing the web portal to quickly determine the appropriate back-end system by matching request parameters against stored cases, rather than discovering the routing dynamically at request time.
2Ease of operation
If the system uses a static routing method to determine back-end systems, then the routing logic is simple, but it cannot adapt to changing system topologies and migrated accounts
Solution Approach 1:
The routing information structure is designed to be dynamic rather than static. Cases can be added, modified, or removed from the routing structure as back-end systems change topology or accounts are migrated. This allows the system to adapt to changing conditions while maintaining a relatively simple lookup-based routing mechanism.
Solution Approach 2:
The system incorporates feedback mechanisms where the web portal can update the routing information structure based on successful or unsuccessful access attempts. When the portal encounters a new back-end system configuration or migration scenario, it can add new cases to the routing structure, allowing the system to learn and adapt from operational experience.
3Reliability
If manual tracking of back-end systems is used, then the system can maintain accurate routing information, but the effort and time required to update routing information increases
Solution Approach 1:
The web portal performs self-service by automatically updating the routing information structure based on its operational experience. When the portal successfully accesses a back-end system or encounters a routing scenario, it can autonomously add or update cases in the routing structure, eliminating the need for manual tracking while maintaining accurate routing information.
Data Source
AI summary
A system receives a request from a client relating to an account associated with the client, and values associated with a set of parameters relating to the request. The system matches the values to a structure that includes cases of the set of parameters to determine one or more cases similar to the values associated with the set of parameters. The system accesses information for the account based on routing information corresponding to the determined one or more similar cases.