Subqueue Suffix Logic for Message Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing message processing systems face inefficiencies and inaccuracies due to resource-intensive 'move' operations between queues, which can result in lost sender identity and incorrect delivery acknowledgments, leading to inappropriate message handling and potential resending issues.
Innovation Solution
The implementation of subqueues allows for logical message movement within the same queue by modifying the suffix value of the queue identifier, enabling efficient message partitioning and movement without physical relocation, thus retaining sender identity and preventing premature delivery acknowledgments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If messages are physically moved between queues using traditional move operations, then message routing and sorting can be achieved, but resource usage increases and sender identity may be lost
Solution Approach 1:
The patent segments a single queue into multiple subqueues by introducing a suffix value to the queue identifier. This allows messages to be logically partitioned into different subqueues (e.g., for different processing units or priorities) without physically moving messages between separate queue structures. The segmentation is achieved by modifying only the identifier suffix rather than relocating message data.
Solution Approach 2:
Instead of physically moving messages between queues, the patent creates a logical copy of the queue identifier with a modified suffix value. The message remains in its original location while a duplicate identifier pointing to a different subqueue is created, enabling routing decisions without data relocation.
2Ease of operation
If traditional move operations are used to sort messages into separate groups, then message sorting can be achieved, but sender identity information is lost
Solution Approach 1:
The queue identifier is segmented into a parent value (preserving original queue identity and sender information) and a suffix value (enabling subqueue differentiation). This segmentation allows messages to be sorted into different subqueues while the parent value portion maintains the original sender identity and routing information intact.
Solution Approach 2:
Instead of moving messages to different queues (spatial relocation), the patent adds a new dimension to the queue identifier by appending a suffix value. This dimensional addition allows messages to be logically assigned to different subqueues while remaining in the same physical queue location, preserving all original message attributes including sender identity.
3Productivity
If messages are moved between queues for processing, then message delivery can be managed, but incorrect delivery acknowledgments may be sent
Solution Approach 1:
The system performs preliminary actions by pre-configuring subqueue identifiers with appropriate suffix values before message movement. When messages need to be routed, the suffix value is already prepared and attached to the queue identifier, ensuring that delivery acknowledgments are sent to the correct destination without requiring post-movement corrections or re-routing operations.
Data Source
AI summary
The present invention extends to methods, systems, and computer program products for using subqueues to enhance local message processing. Messages include queue IDs comprised of a parent portion and a suffix portion. The parent portion identifies a parent queue and the suffix portion identifies a subqueue of the parent queue. Message are logically moved between queues by changing suffix values, such as, for example, between subqueues, between the parent queue and a subqueue, and between a subqueue and the parent queue. Applications can examine messages and route messages to specified subqueues based on message content (including message bodies and headers). Suffix values can be changed in place (e.g., while the message remains physically stored in the queue) so as to preserve message sender identity and to avoid prematurely acknowledging delivery (i.e., no return ACK is generated).