System and method for managing messages in a queuing system

• US 7,673,302 B1
• Filed: 08/26/2004
• Issued: 03/02/2010
• Est. Priority Date: 08/26/2004
• Status: Active Grant

• Current Assignee: T-Mobile Innovations LLC (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Katzer, Robin D.
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): Tang; Kenneth
• Application Number:
  US10/927,454
• Time in Patent Office: 2,014 Days
• Field of Search: 718/101, 719/314, 710/39, 710/54
• US Class Current: 718/101
• CPC Class Codes: G06F 11/1479 Generic software techniques for error detection or fault masking
• CPC Class Codes: G06F 9/5038 considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration scheduling strategies G06F9/4881 and subgroups
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

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.

Claims

1. A system for processing multiple potentially related requests comprising:

a pending request queue stored on a computer readable storage medium that receives requests from at least one application;

an in-process queue stored on a computer readable storage medium that 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;

a related request queue stored on a computer readable storage medium that receives a second request from the pending request queue when the second request is related to the first request present in the in-process queue;

a retry queue stored on a computer readable storage medium that receives the first request when an error occurs during processing the first request from the in-process queue and further maintains the first request until the second request is processed directly or indirectly from the related request queue, wherein when the retry queue receives the first request, the first request is processed directly or indirectly from the retry queue; and

an adapter stored on a computer readable storage medium that monitors the pending request queue, related request queue, retry queue, and in-process queue and to communicates information related to the requests from the pending request queue to the related request and in-process queues, the adapter further communicates information related to the requests from the in-process queue to a processor for processing the requests from the in process queue.

2. The system of claim 1 wherein the adapter is programmed to communicate information related to the requests from the pending request queue in a parallel manner.

3. The system of claim 1 wherein the adapter is programmed to communicate information related to the requests from the in-process queue in a parallel manner.

4. The system of claim 1 wherein the adapter moves the requests from the in-process queue in a parallel manner.

5. The system of claim 1 further comprising a data storage medium that stores information related to requests for retrieval.

6. The system of claim 1, wherein indirectly processing the second request from the related request queue comprises sending the second request to the in-process queue and processing the second request from the in-process queue.

7. The system of claim 1, wherein indirectly processing the first request from the retry queue comprises sending the first request to the in-process queue and processing the first request from the in-process queue.

8. A system for processing multiple potentially related requests comprising:

a pending request queue that receives requests from at least one application;

an in-process queue that 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;

a related request queue that receives a second request from the pending request queue when the second request is related to the first request present in the in-process queue;

a processor that processes the first request from the in-process queue;

a retry queue that receives the first request when the first request is returned upon error during processing by the processor and further maintains the first request until the second request is processed directly or indirectly from the related request queue, wherein when the retry queue receives the first request, the first request is processed directly or indirectly from the retry queue; and

an adapter that monitors the pending request queue, related request queue, retry queue, and in-process queue and communicates information related to the requests from the pending request queue to the related request and in-process queues, the adapter further communicates information related to requests from the in-process queue to the processor for processing the requests from the in-process queue.

9. The system of claim 8, wherein the adapter processes information related to requests in parallel from the pending request queue, related request queue, and in-process queue.

10. The system of claim 8, further comprising a storage medium that stores requests returned on error during processing by the processor.

11. The system of claim 8, further comprising a console for arbitrating requests returned on error during processing by the processor.

12. The system of claim 11, further comprising a graphical user interface that identifies the requests returned on error during processing by the processor, and enables a user to manage any requests in error.

13. The system of claim 8, wherein indirectly processing the second request from the related request queue comprises sending the second request to the in-process queue and processing the second request from the in-process queue.

14. The system of claim 8, wherein indirectly processing the first request from the retry queue comprises sending the first request to the in-process queue and processing the first request from the in-process queue.

15. The system of claim 8, wherein indirectly processing the first request from the retry queue comprises sending the first request to the related request queue when there is a third request related to the first request in the in-process queue and processing the first request from the related request queue after the third request is processed.

16. The system of claim 8, wherein indirectly processing the first request from the retry queue comprises sending the first request to the related request queue when there is a third request related to the first request in the in-process queue, sending the first request to the in-process queue after the third request is processed, and processing the first request from the in-process queue.

17. A method for processing multiple potentially related requests comprising:

receiving requests from at least one application at a pending request queue stored on a computer readable storage medium;

comparing a first request in the pending request queue to requests in an in-process queue stored on a computer readable storage medium;

sending the first request from the pending request queue to the in-process queue when the first request is not related to at least one of the requests in the in-process queue;

comparing a second request in the pending request queue to the first request in the in-process queue;

sending the second request from the pending request queue to a related request queue stored on a computer readable storage medium when the second request is related to the first request in the in-process queue;

sending the first request from the in-process queue to a retry queue stored on a computer readable storage medium when an error occurs during processing of the first request from the in-process queue;

maintaining the first request in the retry queue until the second request is directly or indirectly processed from the related request queue;

processing the first request directly or indirectly from the retry queue; and

monitoring, by an adapter stored on a computer readable storage medium, the pending request queue, related request queue, retry queue, and in-process queue and communicating, by the adapter, information related to requests from the pending request queue to the related request and in-process queues.

18. The method of claim 17, wherein indirectly processing the second request from the related request queue comprises sending the second request to the in-process queue and processing the second request from the in-process queue.

19. The method of claim 17 further comprising:

processing the first request directly or indirectly from the retry queue when the first request is maintained by the retry queue.

20. The method of claim 17 further comprising storing in a data storage medium information related to requests, and when requests are lost, retrieving the information related to the lost requests from the storage medium.