Multi-Queue Transaction Manager for Scalable Asynchronous Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing transaction managers lack scalability and efficiency in handling large numbers of transactions across network entities, particularly in asynchronous environments, leading to increased processing overhead and resource wastage.

Innovation Solution

Implementing a transaction manager that utilizes multiple transaction request and response queues with load balancing, allowing parallel processing and dynamic adaptation of queue configurations, along with time limits for transaction handling to manage resources effectively.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a single transaction queue is used to manage transactions, then the device complexity is low, but the productivity and transaction throughput are limited

Engineering Contradiction:
Improvetransaction throughputVSAvoidqueue management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent divides a single transaction queue into multiple separate queues (first queue, second queue, third queue, fourth queue). Each queue handles specific transaction types or stages independently, allowing parallel processing and increasing overall throughput. The transaction manager selectively routes transactions to appropriate queues based on transaction characteristics, resolving the contradiction by segmenting the monolithic queue structure into specialized sub-queues.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension of queue organization by creating multiple queues with different characteristics (request queues vs. response queues, synchronous vs. asynchronous queues). This multi-dimensional queue architecture allows transactions to be processed along different paths simultaneously, increasing throughput without proportionally increasing management complexity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If multiple transaction queues are implemented to increase throughput, then the productivity improves, but the device complexity increases

Engineering Contradiction:
Improvetransaction processing capacityVSAvoidqueue selection and management overhead
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The transaction manager acts as an intermediary that simplifies the complexity of managing multiple queues. It automatically selects appropriate queues for incoming transactions based on predefined rules and transaction characteristics, shielding upper-level applications from the complexity of queue management while enabling high-throughput parallel processing through multiple specialized queues.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter of queue organization from a single queue to multiple queues with different characteristics. By introducing parameters such as queue type (request/response), processing mode (synchronous/asynchronous), and priority levels, the system increases processing capacity while the transaction manager handles the complexity of selecting among these parameterized queues.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If synchronous transaction processing is used, then the transaction consistency is maintained, but the productivity and response time are reduced

Engineering Contradiction:
Improvetransaction processing speedVSAvoidtransaction consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments transaction processing into synchronous and asynchronous paths using separate queues. The synchronous queue maintains strict consistency for transactions requiring immediate confirmation, while the asynchronous queue enables faster processing for transactions where eventual consistency is acceptable. This segmentation allows the system to optimize for both speed and consistency depending on transaction requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The transaction manager dynamically selects between synchronous and asynchronous queue processing based on transaction characteristics and system state. This dynamic approach allows the system to adaptively balance between consistency requirements and processing speed, maintaining reliability when needed while maximizing productivity when possible.

Inventive Principle:
Principle #15Dynamics

4Productivity

If transaction queues are expanded to handle more concurrent transactions, then the productivity increases, but the loss of time for queue management increases

Engineering Contradiction:
Improveconcurrent transaction handlingVSAvoidqueue selection and processing overhead
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-organizing multiple queues with specific purposes and characteristics before transactions arrive. The transaction manager has pre-established routing rules and queue assignments, allowing it to quickly direct transactions to appropriate queues without extensive real-time analysis. This preliminary organization reduces the time overhead for queue management while maintaining high concurrent processing capacity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250390854A1Transaction manager
Publication Date: 2025.12.25 VOCALINK LTD
  • US20250390854A1 patent drawing
  • US20250390854A1 patent drawing
  • US20250390854A1 patent drawing

AI summary

A method performed by a transaction manager comprising: receiving, from a first network entity, a first request to perform a transaction with a second network entity; selecting a request queue from a plurality of transaction request queues; adding the first request to the back of the selected request queue; when the first request reaches the front of the selected request queue, processing the first request by a request handler and sending a second request to the second network entity; receiving a first response from the second network entity, in response to the second request; selecting a response queue from a plurality of transaction response queues; adding the first response to the back of the selected response queue; and when the first response reaches the front of the selected response queue, processing the first response by a response handler and sending a second response to the first network entity.