Queuing System Segregates Requests for Ordered Processing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprise systems often fail to process multiple related transactions in the correct order, leading to errors due to out-of-sequence processing, especially when parallel processing is employed, causing dependent requests to be completed before their prerequisites.

Innovation Solution

A queuing system with a pending request queue, a related request queue, an in-process queue, and an adapter that monitors and manages requests to ensure they are processed in the correct order by segregating requests and holding dependent requests until their prerequisites are completed, using a retry queue for failed requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If parallel processing is employed to increase productivity, then processing speed is improved, but request processing order reliability deteriorates

Engineering Contradiction:

Improveprocessing speedVSAvoidrequest processing order

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system segments requests into different queues based on their processing requirements: a pending request queue for new requests, a related request queue for dependent requests, and an in-process queue for active processing. This segmentation allows parallel processing of independent requests while maintaining sequential processing for related requests, thus resolving the contradiction between productivity and reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The adapter acts as an intermediary component that monitors all queues and manages the flow of requests between them. It ensures that related requests are processed in the correct sequence by coordinating between the pending request queue, related request queue, and in-process queue, thereby maintaining reliability while enabling parallel processing of unrelated requests.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If requests are processed in sequence to maintain order, then processing reliability is improved, but productivity deteriorates

Engineering Contradiction:

Improveprocessing orderVSAvoidprocessing efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

By dividing requests into related and unrelated groups and placing them in separate queues, the system can process unrelated requests in parallel (improving productivity) while maintaining strict sequential processing for related requests (preserving reliability). This segmentation eliminates the need to serialize all requests while ensuring dependent requests maintain their order.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts processing behavior based on request characteristics. The adapter monitors queue states and determines whether requests can be processed in parallel or must wait in sequence. This dynamic approach allows the system to maximize parallel processing opportunities while maintaining required sequential processing, thus improving productivity without sacrificing reliability.

Inventive Principle:

Principle #15Dynamics

3Manufacturing precision

If dependent requests are held until prerequisites are completed, then processing accuracy is improved, but processing time increases

Engineering Contradiction:

Improveprocessing accuracyVSAvoidprocessing delay

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by placing requests in the pending request queue and pre-identifying related requests in the related request queue before actual processing begins. The adapter proactively monitors and prepares dependent requests, so when prerequisites are completed, dependent requests can be immediately processed without excessive delay. This preliminary organization maintains processing accuracy while minimizing unnecessary waiting time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The adapter implements feedback mechanisms by continuously monitoring the in-process queue and detecting when prerequisite requests are completed. Once a prerequisite is finished, the adapter immediately notifies the related request queue and triggers the processing of dependent requests. This real-time feedback minimizes the holding time for dependent requests while ensuring they are processed only after their prerequisites are complete, thus balancing accuracy and time efficiency.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS7673302B1System and method for managing messages in a queuing system

Publication Date: 2010.03.02 T MOBILE INNOVATIONS LLC

AI summary

A system for processing multiple potentially related requests is provided. The system includes a pending request queue, a related request queue, an in-process queue, and an adapter. The pending request queue receives requests from at least one application. The in-process queue receives a first request from the pending request queue when no other requests are present in the in-process queue related to the first request. The related request queue receives the first request from the pending request queue when other requests are present in the in-process queue related to the first request. The adapter monitors the pending request queue, related request queue, and in-process queue. The adapter also communicates information related to the requests from the pending request queue to the related request and in-process queues as appropriate. The adapter also communicates information related to the requests from the in-process queue to a processor for processing the requests.