Liveness monitoring in a publish/subscribe messaging system
First Claim
1. A publish/subscribe messaging system, comprising:
- at least one broker and at least one subscriber, wherein the at least one broker has means for sending a status request message to the at least one subscriber,means, responsive to a particular subscriber receiving the status request message from the at least one broker, for setting a timer for the particular subscriber of the at least one subscriber, andmeans, responsive to the timer expiring, for sending a multicast message claiming response to the at least one broker from the particular subscriber of the at least one subscriber.
1 Assignment
0 Petitions
Accused Products
Abstract
A variety of techniques are disclosed for efficient liveness monitoring in a reliable publish/subscribe multicast system having at least one broker and at least one subscriber, by: at the broker, sending (310) a status request message to the subscriber, and at the subscriber, sending (350) a status response message to the broker to indicate liveness. Status responses by subscribers may be suppressed when at least a chosen minimum number (>=1) of subscribers send a response. This suppression (320-340) uses a system of “response claim” messages and random back-off timers. These provide the advantage that the efficiency of network usage is improved by reducing the number of unwanted packets that are sent.
59 Citations
50 Claims
-
1. A publish/subscribe messaging system, comprising:
-
at least one broker and at least one subscriber, wherein the at least one broker has means for sending a status request message to the at least one subscriber, means, responsive to a particular subscriber receiving the status request message from the at least one broker, for setting a timer for the particular subscriber of the at least one subscriber, and means, responsive to the timer expiring, for sending a multicast message claiming response to the at least one broker from the particular subscriber of the at least one subscriber. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 50)
-
-
17. A method for liveness monitoring in a publish/subscribe messaging system having at least one broker and at least one subscriber, the method comprising:
-
sending a status request message from the at least one broker to the at least one subscriber, responsive to a particular subscriber receiving the status request message from the at least one broker, setting a timer for the particular subscriber of the at least one subscriber, and responsive to the timer expiring, sending a multicast message claiming response to the at least one broker from the particular subscriber of the at least one subscriber. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 49)
-
-
33. A system for indicating liveness to a broker in a multicast publish/subscribe messaging system comprising the broker and a plurality of subscribers, the system comprising:
-
means, responsive to a particular subscriber receiving a status request message from the broker, for setting a timer for each subscriber in the plurality of subscribers, and means, responsive to the timer expiring, for sending a multicast message claiming response to the broker from the particular subscriber in the plurality of subscribers. - View Dependent Claims (34, 35, 36, 37, 38, 39, 40)
-
-
41. A method for indicating liveness to a broker in a multicast publish/subscribe messaging system comprising the broker and a plurality of subscribers, the method comprising:
-
responsive to each subscriber receiving a status request message from the broker, setting a separate timer for each subscriber in the plurality of subscribers, and responsive to a timer of a particular subscriber in the plurality of subscribers expiring, sending a multicast message claiming response to the broker from the particular subscriber in the plurality of subscribers. - View Dependent Claims (42, 43, 44, 45, 46, 47, 48)
-
Specification