Single Program Call Message Retrieval API

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current message queues require multiple method calls for message retrieval, which is inefficient and burdensome, as they do not provide a single method call to retrieve messages, leading to resource allocation issues and increased complexity.

Innovation Solution

A message queue API is introduced with a single program call that enables the opening, retrieval, and closing of a queuing resource, allowing for efficient single program code message retrieval without the need for separate commands, thereby reducing resource allocation and complexity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If multiple method calls are used for message retrieval, then the message queue can maintain resource allocation control, but the operation complexity and number of API calls increase

Engineering Contradiction:
Improvemessage retrieval operationVSAvoidAPI call sequence
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines multiple separate method calls (OPEN, READ, CLOSE) into a single integrated method call that performs all three operations atomically. This merging eliminates the need for sequential API calls and reduces operation complexity while maintaining resource control.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal method call that can retrieve messages without requiring separate resource management calls. This multi-functional approach allows a single API call to handle both resource acquisition and message retrieval, simplifying the interface.

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

2Productivity

If multiple method calls are required for message retrieval, then resource management can be controlled, but the time and number of operations increase

Engineering Contradiction:
Improvemessage retrieval efficiencyVSAvoidAPI call duration
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

By merging OPEN, READ, and CLOSE operations into a single method call, the patent eliminates the time overhead of multiple sequential API invocations. The combined operation executes in a single call, improving productivity and reducing time loss.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent performs resource opening and closing as preliminary actions within the single method call, so that resource management overhead does not add to the external caller's operation time. The resource lifecycle is managed internally without extending the visible operation duration.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If separate method calls are used for opening, reading, and closing, then resource control is maintained, but the overall system complexity increases

Engineering Contradiction:
Improveresource managementVSAvoidmethod call sequence
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges resource management operations with message retrieval into a single atomic method call. This maintains reliability by ensuring resources are properly managed while reducing system complexity by eliminating the need for callers to orchestrate multiple separate calls.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9588827B2Single program call message retrieval
Publication Date: 2017.03.07 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9588827B2 patent drawing
  • US9588827B2 patent drawing

AI summary

Embodiments of the present invention provide a method, system and computer program product for single program code message retrieval for message queues. In an embodiment of the invention, a message queue data processing system can be configured for single program code message retrieval for message queues. The system can include a message queue executing in a host server and providing an API to applications communicatively coupled to the message queue over a computer communications network. The API exposed by the message queue can include a single program call including program code enabled to open a queuing resource in the message queue, to retrieve all messages in a message buffer from the queuing resource and to close the queuing resource.