Hierarchical publish/subscribe system performed by multiple central relays

• US 9,569,753 B2
• Filed: 06/27/2012
• Issued: 02/14/2017
• Est. Priority Date: 10/30/2009
• Status: Active Grant

• Current Assignee: VeriSign, Inc.
• Original Assignee: VeriSign, Inc.
• Inventors: Gallant, John K., Henderson, Karl M., Verd, Brad
• Primary Examiner(s): Park, Jeong S
• Application Number:
  US13/534,786
• Publication Number:
  US 20130024529A1
• Time in Patent Office: 1,693 Days
• Field of Search: 709/206
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 12/1854 with non-centralised forwarding system, e.g. chaincast
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A method for transmitting messages in a publish/subscribe message system. The method also includes: receiving, at a first relay, a subscription request from a first client; recording, at the first relay, subscription information of the first client based on the subscription request; receiving, at the first relay, a publication request from a second client, wherein the publication request includes a message; and transmitting the message to the first client.

Claims

1. A method for transmitting messages in a publish/subscribe message system, the method comprising:

receiving, at a central relay of a first group of more than one co-located central relays, a subscription request from a first remote relay on behalf of a first client;

recording, at the central relay of the first group, subscription information of the first client based on the subscription request;

receiving, at the central relay of the first group of more than one co-located central relays, a publication request from a second remote relay on behalf of a second client, wherein the publication request includes a message;

recording, at the central relay, publication information from the message;

transmitting, by the central relay, the publication information to other members of the first group of co-located central relays and to each member of second group of more than one co-located central relays in a different geographic location than the first group; and

transmitting the message to the first client.

2. The method of claim 1, wherein the subscription request includes a request to subscribe to all messages received by the central relay, the first remote relay, the second remote relay, or any combination thereof.

3. The method of claim 1, further comprising:

determining, by the central relay, if the second client is connected to the central relay; and

transmitting the message to the first client only if the second client is determined to be connected to the central relay.

4. The method of claim 1, wherein the first client is connected to the central relay.

5. The method of claim 1, further comprising:

storing a black list at the central relay; and

ignoring the publication request from the second client if the second client is on the black list.

6. The method of claim 1, wherein the first remote relay and the second remote relay are the same remote relay.

7. The method of claim 1, wherein the message comprises statistics related to any, or combinations of, the following:

SDNS, WHOIS, TGV, or CRL.

8. The method of claim 1, further comprising:

storing the messages; and

performing a statistical analysis on at least a portion of the messages to determine, at least in part, a performance metric of a central relay.

9. A central relay group in a publish/subscribe message system, the central relay croup is configured to:

receive, at each central relay of a first group of more than one co-located central relays, a subscription request from a first remote relay on behalf of a first client;

record, at the each central relay of the first group, subscription information of the first client based on the subscription request;

receive, at only one of central relay of the first group of more than one co-located central relays, a publication request from a second remote relay on behalf of a second client, wherein the publication request includes a message;

record, at the only one of the central relay, publication information from the message;

transmit, by the only one of the central relay, the publication information to other members of the first group of co-located central relays and to each member of second group of more than one co-located central relays in a different geographic location than the first group; and

transmit the message to the first client.

10. The central relay group of claim 9, wherein the subscription request includes a request to subscribe to all messages received by each central relay, the first remote relay, the second remote relay, or any combinations thereof.

11. The central relay group of claim 9, further configured to:

determine if the second client is connected to a first central relay in the first group; and

transmit the message to the first client only if the second client is determined to be connected to the first central relay.

12. The central relay group of claim 9, wherein the first client is connected to one of the central relays.

13. The central relay group of claim 9, further configured to:

store a black list; and

ignore the publication request from the second client if the second client is on the black list.

14. The central relay of claim 9, wherein the first remote relay and the second remote relay are the same remote relay.

15. The central relay group of claim 9, wherein the message comprises statistics related to any, or combinations of, the following:

SDNS, WHOIS, TGV, or CRL.

16. The central relay group of claim 9, wherein each central relay is further configured to:

store the messages; and

perform a statistical analysis on at least a portion of the messages to determine, at least in part, a performance metric of a central relay.