Automated Interaction-Event Routing System for Digital Value Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer systems face challenges in efficiently routing interaction-events across multiple rails, as each rail requires specific input data and protocols, leading to suboptimal processing and potential delays in value transfer between accounts.
Innovation Solution
An automated interaction-event routing system that selects the optimal interaction-event rail based on request parameters, transforms the request into a rail-specific format, and submits it for processing, ensuring efficient digital value transfer using protocols specific to the selected rail.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple interaction-event rails are used to process different types of requests, then processing effectiveness is improved, but system complexity increases due to different protocols and data formats required by each rail
Solution Approach 1:
The patent introduces an interaction-event routing system as an intermediary layer between the application programming interface and multiple interaction-event rails. This routing system automatically selects the appropriate rail based on request parameters and transforms requests into rail-specific formats, thereby managing the complexity of multiple rails while maintaining high processing effectiveness.
Solution Approach 2:
The routing system serves multiple functions: it receives requests from a single API interface, automatically selects among multiple different rails, transforms requests into various rail-specific formats, and manages protocol differences. This multi-functional approach consolidates complexity into a single universal component rather than requiring separate handling logic for each rail.
2Productivity
If automatic rail selection is implemented based on request parameters, then processing efficiency is improved, but the complexity of request transformation increases
Solution Approach 1:
The routing system performs preliminary actions by pre-configuring knowledge of multiple rails, their protocols, and required data formats. When a request arrives, it already has the criteria and transformation rules ready, enabling rapid automatic selection and transformation without ad-hoc complexity during request processing.
Solution Approach 2:
The system automatically changes request parameters based on the selected rail's requirements. It transforms the standardized incoming request into rail-specific formats by modifying parameters such as data structure, protocol type, and field mappings, thereby adapting to different rails while maintaining a unified input interface.
3Adaptability or versatility
If interaction-event requests are routed through multiple rails with different protocols, then versatility in handling request types is improved, but processing delays may occur due to protocol conversion
Solution Approach 1:
The routing system acts as a mediator that maintains a mapping between standardized request types and rail-specific protocols. This pre-established mapping enables rapid protocol conversion without extensive real-time analysis, thereby maintaining versatility while minimizing conversion delays.
Solution Approach 2:
The system performs preliminary configuration of protocol mappings and transformation rules for all supported rails. This advance preparation ensures that when a request needs to be routed, the appropriate transformation logic is already in place, reducing the time required for protocol conversion compared to dynamic determination during request processing.
Data Source
AI summary
An interaction-event routing system can automatically select an optimal interaction-event rail (IER) to process an interaction-event request. For example, the interaction-event routing system can include a processor and a memory that includes instructions executable by the processor to perform operations. The operations can include receiving a request to process an interaction event from an application programming interface. The request can include at least one parameter. The operations can further include automatically selecting, based on the at least one parameter, an IER from among a plurality of IERs to process the interaction event. The plurality of IERs can be configured to digitally transfer value between accounts using different protocols. Additionally, the operations can include transforming the request into a rail specific request suitable for the selected IER. The operations can include submitting the rail specific request to the selected IER.