Dynamic Transaction Routing Module for Dead Node Elimination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Financial instrument processing systems face inefficiencies due to dead nodes and bottlenecks in transaction processing, leading to slow processing and potential exceptions in document reconciliation.

Innovation Solution

A monitoring system that dynamically maps transaction flow, identifies dead and bottleneck nodes, and automatically re-routes transaction flows or updates code to optimize node usage, ensuring efficient processing by removing dead nodes and re-directing transactions through faster pathways.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If transaction files are processed through all designated nodes in the system, then processing completeness is maintained, but processing time increases and system efficiency decreases due to dead nodes and bottlenecks

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoidprocessing time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system dynamically determines transaction pathways by evaluating node status in real-time. The monitoring module continuously tracks node performance metrics, and the routing module adapts transaction routes based on current system conditions, allowing the system to respond to changing loads and node availability rather than following static predefined paths

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The routing module acts as an intermediary between transaction files and processing nodes. It receives transaction requests, evaluates available pathways using monitoring data, selects optimal routes avoiding dead and bottleneck nodes, and directs transactions accordingly, thereby mediating between the need for complete processing and efficient time-bound execution

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the system maintains a fixed transaction flow configuration, then system stability is preserved, but the system cannot adapt to changing node performance and accumulates dead nodes and bottlenecks

Engineering Contradiction:
Improvesystem adaptability to node changesVSAvoidtransaction flow configuration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The monitoring module continuously collects performance data from processing nodes and feeds this information back to the routing module. This feedback loop enables the system to detect dead nodes and bottlenecks automatically and adjust transaction pathways dynamically, maintaining adaptability without requiring manual reconfiguration

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs self-diagnosis and self-optimization through automated monitoring and dynamic routing. The monitoring module independently identifies performance issues, and the routing module automatically reroutes transactions around problems without human intervention, allowing the system to maintain itself and adapt to changes autonomously

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10115081B2Monitoring module usage in a data processing system
Publication Date: 2018.10.30 BANK OF AMERICA CORP
  • US10115081B2 patent drawing
  • US10115081B2 patent drawing
  • US10115081B2 patent drawing

AI summary

Embodiments of the invention monitor node usage in a transaction processing system. Embodiments include accessing a dynamic mapping of transaction flow in the transaction processing system, the dynamic mapping including a plurality of transaction pathways interconnected by transaction nodes, wherein the transaction nodes represent an automated processing step or action taken by a manual station of the transaction processing system on transactions files that are received at the transaction nodes; wherein the transaction processing system processes a transaction file at a first node and stores information corresponding to the first node and the type of processing that occurred at the first node with the transaction file; determining that the transaction file was processed at the first node; accessing the transaction file to determine the type of processing that occurred at the first node; and performing an action related to the type of processing that occurred at the first node.