Closed-loop Resource Event Processing Logic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face inefficiencies in processing resource events in real-time, as they often require unnecessary processing through external real-time processing networks, leading to increased burden and reduced processing speed.
Innovation Solution
A closed-loop system determines whether a resource event can be processed within the event initiating entity system or an external network, routing it accordingly to minimize external network usage, utilizing a closed loop network group or real-time processing network based on the location of the user-specific resource depository.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all resource events are routed through external real-time processing networks, then processing coverage is comprehensive, but processing speed decreases and network burden increases
Solution Approach 1:
The patent segments resource events into two categories: those that can be processed internally within the entity system and those requiring external network processing. This segmentation allows internal events to be processed quickly without external network overhead, while external events receive comprehensive network-based processing, thus resolving the contradiction between processing coverage and speed.
Solution Approach 2:
The entity system acts as an intermediary that filters and pre-processes resource events before they reach the external real-time processing network. By determining whether an event implicates a user-specific resource depository held at the entity system or another entity system, the intermediary function reduces unnecessary external network traffic while ensuring appropriate events receive external processing.
2Reliability
If all resource events are processed through external real-time processing networks, then processing thoroughness is ensured, but network burden increases
Solution Approach 1:
The patent extracts and handles internally processable resource events within the entity system before they reach the external network. By taking out events that can be resolved using internal resource depositories and logic, the system reduces the volume of events requiring external network processing, thereby decreasing network burden while maintaining thorough processing for events that do require external handling.
3Speed
If internal processing is used for all events, then processing speed increases, but processing capability is limited
Solution Approach 1:
The patent implements a dynamic routing mechanism that adapts the processing path based on the specific characteristics of each resource event. Events are dynamically assessed to determine whether they can be handled internally or require external network processing, allowing the system to optimize for speed when appropriate while maintaining the capability to handle complex events that require external processing resources.
Data Source
AI summary
Embodiments of the invention are directed to closed-loop resource event processing in which an initial determination as to whether a resource event requiring real-time processing can be processed absent an external real-time processing network. In the event that a determination is made that the resource event can by processed absent the external real-time processing network, a closed network group is created internally within the event-initiating system and the event is processed internally within the event initiating-system. By limiting the use of the real-time processing network to only those resource event that require such processing, less burden is placed on real-time processing network, meaning less processing resources are required and the processing that is required on the real-time processing network can occur more efficiently and effectively.