Certified message delivery and queuing in multipoint publish/subscribe communications

• US 20060248143A1
• Filed: 07/17/2006
• Published: 11/02/2006
• Est. Priority Date: 08/18/1997
• Status: Active Grant

• Current Assignee: Cloud Software Group
• Original Assignee: TIBCO Software Incorporated (Cloud Software Group)
• Inventors: Collison, Derek L., Page, Dennis R., Leshchiner, Dan
• Granted Patent: US 7,530,078 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 51/234 for tracking messages

Abstract

A method for certified delivery of an outgoing message or messages in a multipoint anonymous, publish/subscribe telecommunications system. The system for utilizing the method and program product is one having at least one publisher (10) and at least one subscriber (20). The method is carried out by first establishing a certified delivery session ledger. Next each outgoing message is labeled with a label including the delivery session name and a sequence number. The labeled outgoing message or messages are then sent to subscribers, and received by a subscriber. Various protocols are described.

Claims

1. In a computer-based publish/subscribe system, a method for communicating a target message from a publisher application to a receiving member of a distributed queue of subscriber applications, wherein the distributed queue of subscriber applications comprises a plurality of members, the method comprising:

an initiating member of the distributed queue of subscriber applications subscribing to receive messages pertinent to a subject, wherein the target message is pertinent to the subject;

a detecting member of the distributed queue of subscriber applications detecting the target message, wherein the target message was sent from the publisher application; and

the receiving member of the distributed queue of subscriber applications receiving the target message.

2. The method of claim 1, wherein the initiating member, the detecting member, and the receiving member are all the same member of the distributed queue of subscriber applications.

3. The method of claim 1, wherein the target message is received by no more than one member of the distributed queue of subscriber applications.

4. The method of claim 1, wherein the receiving member of the distributed queue of subscriber applications comprises the member of the distributed queue of subscriber applications determined to be the member most capable of processing the message.

5. The method of claim 4, wherein the member of the distributed queue of subscriber applications determined to be the member most capable of processing the message is determined by a scheduling member of the distributed queue of subscriber applications, wherein the scheduling member routes the target message to the receiving member of the distributed queue of subscriber applications, and wherein the scheduling member receives message processing capability information from the plurality of members of the distributed queue of subscriber applications.

6. The method of claim 5, wherein the scheduling member of the distributed queue of subscriber applications comprises the member of the distributed queue of subscriber applications determined to be the member most capable of performing tasks associated with the scheduling member.

7. The method of claim 5, wherein the scheduling member communicates heartbeat messages to the plurality of members of the distributed queue of subscriber applications, the heartbeat messages indicating that the scheduling member is capable of performing tasks associated with the scheduling member.

8. The method of claim 7, wherein, upon the scheduling member ceasing to communicate heartbeat messages to the plurality of members of the distributed queue of subscriber applications, a new scheduling member is selected, the new scheduling member comprising the member of the distributed queue of subscriber applications determined to be the member most capable of performing tasks associated with the scheduling member.

9. The method of claim 1, further comprising:

a registering member of the distributed queue of subscriber applications registering with the publisher application for certified delivery of messages pertinent to the subject;

an accepting member of the distributed queue of subscriber applications receiving an acceptance of registration for certified delivery from the publisher application; and

after the target message is received, an acknowledging member of the distributed queue of subscriber applications acknowledging receipt of the target message to the publisher application.

10. The method of claim 9, wherein the initiating member, the registering member, the accepting member, the detecting member, the receiving member, and the acknowledging member are all the same member of the distributed queue of subscriber applications.

13. The distributed queue of subscriber applications of claim 11, wherein the target message is received by no more than one member.

11. A distributed queue of subscriber applications for receiving a target message from a publisher application in a computer-based publish/subscribe system, the distributed queue of subscriber applications comprising a plurality of members, the plurality of members comprising:

an initiating member, wherein the initiating member subscribes to receive messages pertinent to a subject, wherein the target message is pertinent to the subject;

a detecting member, wherein the detecting member detects the target message, and wherein the target message was sent from the publisher application; and

a receiving member, wherein the receiving member receives the target message.

12. The distributed queue of subscriber applications of claim 11, wherein the initiating member, the detecting member, and the receiving member are all the same member.

14. The distributed queue of subscriber applications of claim 11, wherein the receiving member comprises the member determined to be the member most capable of processing the message.

15. The distributed queue of subscriber applications of claim 14, wherein the member determined to be the member most capable of processing the message is determined by a scheduling member, wherein the scheduling member routes the target message to the receiving member, and wherein the scheduling member receives message processing capability information from the plurality of members.

16. The distributed queue of subscriber applications of claim 15, wherein the scheduling member comprises the member determined to be the member most capable of performing tasks associated with the scheduling member.

17. The distributed queue of subscriber applications of claim 15, wherein the scheduling member communicates heartbeat messages to the plurality of members, the heartbeat messages indicating that the scheduling member is capable of performing tasks associated with the scheduling member.

18. The distributed queue of subscriber applications of claim 17, wherein, upon the scheduling member ceasing to communicate heartbeat messages to the plurality of members, a new scheduling member is selected, the new scheduling member comprising the member determined to be the member most capable of performing tasks associated with the scheduling member.

19. The distributed queue of subscriber applications of claim 11, further comprising:

a registering member, wherein the registering member registers with the publisher application for certified delivery of messages pertinent to the subject;

an accepting member, wherein the accepting member receives an acceptance of registration for certified delivery from the publisher application; and

an acknowledging member, wherein the acknowledging member acknowledges receipt of the target message to the publisher application after the target message is received.

20. The method of claim 19, wherein the initiating member, the registering member, the accepting member, the detecting member, the receiving member, and the acknowledging member are all the same member of the distributed queue of subscriber applications.