Queue Migration for Message Serialization in Multi-Queue Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-queue messaging environments, maintaining the serialized order of messages across multiple queues is challenging, leading to potential message delivery errors and inefficient processing due to the complexity of managing multiple serialization contexts and queues.

Innovation Solution

A computer system with a queue assignment handler, queue monitor, and queue scheduler that manages the transition of serialization contexts from source queues to target queues, suspends and resumes message transmission, and ensures that messages are sent in serialized order by buffering and scheduling messages appropriately across queues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If messages are processed through multiple queues in a multi-queue messaging environment, then processing flexibility and queue organization are improved, but maintaining serialized order of messages becomes difficult and error-prone

Engineering Contradiction:
Improveprocessing flexibilityVSAvoidmessage serialization order
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a queue migration mechanism that acts as an intermediary between source queues and target queues. During queue assignment changes, the system uses a coordinated transition process with suspension and resumption of message transmission to ensure serialized order is maintained even as messages move between multiple queues. This intermediary mechanism resolves the contradiction by enabling flexible queue reorganization while preserving message serialization through controlled migration protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically adjusts message transmission by suspending and resuming operations during queue assignment changes. The queue monitor dynamically tracks message positions across queues, and the queue scheduler dynamically recalculates transmission timing to maintain serialized order. This dynamic approach allows the system to adapt to queue reorganization while preserving reliability of message ordering.

Inventive Principle:
Principle #15Dynamics

2Productivity

If queue assignment changes are made to improve processing speed or organization, then productivity is improved, but message transmission order may be disrupted

Engineering Contradiction:
Improveprocessing speedVSAvoidmessage transmission order
Core Design Contradiction:
ProductivityVSStability of the object's composition

Solution Approach 1:

The system performs preliminary actions by suspending message transmission before queue assignment changes take effect. The queue assignment handler pre-coordinates the migration process, and the queue monitor prepares tracking mechanisms in advance. This preliminary preparation ensures that when queue assignments change to improve productivity, the serialized order of messages is preserved through pre-established control mechanisms.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The queue monitor provides continuous feedback on message positions and transmission status during queue assignment changes. This feedback loop allows the queue scheduler to adjust transmission timing in real-time, ensuring that productivity improvements from queue reorganization do not compromise message ordering. The feedback mechanism detects and corrects potential disruptions to serialized order.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If multiple serialization contexts are managed across multiple queues, then queue organization is improved, but system complexity increases

Engineering Contradiction:
Improvequeue organizationVSAvoidserialization context management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The queue monitor serves multiple functions: it tracks message positions, monitors transmission status, coordinates queue migrations, and maintains serialization contexts across multiple queues. This universal component reduces overall system complexity by consolidating diverse management functions into a single multi-functional entity, making the system easier to operate despite managing multiple serialization contexts.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges the management of multiple serialization contexts into a unified queue migration framework. Instead of managing each serialization context separately across multiple queues, the system combines them under a coordinated migration process that handles all contexts simultaneously. This merging reduces operational complexity while maintaining proper queue organization.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9141446B2Maintenance of message serialization in multi-queue messaging environments
Publication Date: 2015.09.22 SAP SE
  • US9141446B2 patent drawing
  • US9141446B2 patent drawing
  • US9141446B2 patent drawing

AI summary

Messages may be provided to a source queue in serialized order, each message associated with a serialization context. The messages may be buffered in the source queue until a transmission time is reached, in turn, for each buffered message. Transmission-ready messages may be sent from the source queue according to the serialized order, using the serialization context, while continuing to store existing messages that are not yet transmission-ready. A queue assignment of the serialization context may be changed to a target queue. Subsequent messages may be provided with the serialization context to the target queue for buffering therein, while remaining transmission-ready messages may be continued to be sent from the source queue. The existing messages from the source queue associated with the serialization context may be determined to have been sent, and the subsequent messages may be sent from the target queue in serialized order, using the serialization context.