Group membership discovery service

• US 8,880,670 B1
• Filed: 03/30/2011
• Issued: 11/04/2014
• Est. Priority Date: 03/30/2011
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Lansing, Lawrence
• Primary Examiner(s): Murray, Daniel C
• Application Number:
  US13/076,283
• Time in Patent Office: 1,315 Days
• Field of Search: 709/204, 709/223, 709/224, 370/254, 370/255, 707/625
• US Class Current: 709/223
• CPC Class Codes: H04L 12/1822 Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 67/1044 Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1048 Departure or maintenance mechanisms
• CPC Class Codes: H04L 67/1059 Inter-group management mechanisms, e.g. splitting, merging or interconnection of groups
• CPC Class Codes: H04L 67/1061 using node-based peer discovery mechanisms static access to replicated servers H04L67/1006; service discovery H04L67/51
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/1068 Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for providing a group membership discovery service. Join requests are received from clients, including a respective group and value pair. A respective count for each received pair is updated, the count indicating a count of a join events received by servers for the pair. Notification is sent to one or more other clients that have requested such notification, wherein the notification includes a first group and value pair having a respective count that was updated for a first time. A notification is received from a server regarding a different second group and value pair received by the server and a respective count for the second group and value pair is updated.

Claims

1. A computer-implemented method performed by a plurality of discovery servers, wherein each discovery server performs operations comprising:

maintaining by the discovery server a respective group name/value count for each of a plurality of group name/value pairs, each group name/value count being a count for a distinct name-value pair of a user-specified group name and value pair;

receiving a Watch command on a first user-specified group name from a first client device, wherein the Watch command comprises a request to receive Join events for newly added values in the first user-specified group;

receiving a first Join event from another discovery server, the first Join event including the first user-specified group name and a first value, wherein a Join event received from a particular discovery server comprises a notification of a Join command or a Join event being received by the particular discovery server;

incrementing the group name/value count for the first group name and the first value in response to receiving the first Join event;

determining that the group name/value count for the first group name and the first value transitioned from zero to nonzero in response to the discovery server incrementing the group name/value count for the first group name and the first value; and

in response to determining that the group name/value count for the first group name and the first value transitioned from zero to nonzero in response to the discovery server incrementing the group name/value count for the first group name and the first value, sending a second Join event to the first client in response to the Watch command received from the first client on the first user-specified group name, the second Join event having the first value of the first Join event.

2. The method of claim 1, wherein the operations further comprise:

receiving an initial notification of the first group name from a first discovery server;

issuing a Local Watch command on the first group name to the first discovery server, wherein the Local Watch command on the first group name is a request to receive Join events for the first group name from the first discovery server in response to the first discovery server receiving Join events for the first group name;

receiving a third Join event from the first discovery server, the third Join event having the first group name and the first value; and

incrementing the group name/value count for the first group name and the first value pair in response to receiving the third Join event from the first discovery server.

3. The method of claim 2, wherein the operations further comprise:

determining that the first discovery server has failed; and

in response to determining that first discovery server has failed, decrementing the group name/value count for the first group name and the first value.

4. The method of claim 1, wherein the operations further comprise:

receiving a Leave event from a second client device, the Leave event having the first user-specified group name and the first value; and

decrementing the group name/value count for the first user-specified group name and the first value in response to receiving the Leave event having the first user-specified group name and the first value.

5. The method of claim 4, wherein the operations further comprise:

determining that the group name/value count for the first user-specified group name and the first value is zero and that, before decrementing the group name/value count for the first user-specified group name and the first value in response to receiving the Leave event from the second client device, the group name/value count was nonzero;

determining that the Watch command on the first user-specified group name is pending; and

sending a second Leave event having the first value to the first client device.

6. The method of claim 1, wherein the operations further comprise providing a notification of the first group name to another discovery server using a metadata protocol, the metadata protocol being distinct from user-specified Join events and user-specified Leave events on user-specified group names.

7. The method of claim 6, wherein providing the notification of the first group name to another discovery server using the metadata protocol comprises sending a metadata Join event to each other discovery server in the plurality of discovery servers, the metadata Join event having a reserved metadata group name and having a second value that includes the first group name.

8. The method of claim 7, wherein the operations further comprise:

receiving a Local Watch command on the metadata group name from a second discovery server, wherein a Local Watch command on the metadata group name is a request issued to a particular discovery server to receive metadata Join events for the metadata group name from the particular discovery server in response to the particular discovery server receiving metadata Join events for the metadata group name; and

in response to receiving the Local Watch command on the metadata group name from the second discovery server, issuing a respective Local Watch command on the metadata group name to every other discovery server of the plurality of discovery servers.

9. The method of claim 7, wherein the operations further comprise:

determining that the first Join event includes a group name for a new user-specified group; and

issuing a respective Local Watch command on the metadata group name to every other discovery server of the plurality of discovery servers, wherein a Local Watch command on the metadata group name is a request issued to a particular discovery server to receive metadata Join events for the metadata group name from the particular discovery server in response to the particular discovery server receiving metadata Join events for the metadata group name.

10. The method of claim 1, wherein the operations further comprise in response to receiving the Watch command from the first client device, sending, to the first client device, respective Join events having respective values of each nonzero group name/value count having the first group name.

11. A system comprising:

a plurality of discovery servers and one or more hardware storage devices storing instructions that are operable, when executed by each of the plurality of discovery servers, to cause each discovery server to perform operations comprising;

maintaining, by the discovery server a respective group name/value count for each of a plurality of group name/value pairs, each group name/value count being a count for a distinct name-value pair of a user-specified group name and value pair;

receiving a Watch command on a first user-specified group name from a first client device, wherein the Watch command comprises a request to receive Join events for newly added values in the first user-specified group;

receiving first Join event from another discovery server, the first Join event including the first user-specified group name and a first value, wherein a Join event received from a particular discovery server comprises a notification of a Join command or a Join event being received by the particular discovery server;

incrementing the group name/value count for the first group name and the first value in response to receiving the first Join event;

determining that the group name/value count for the first group name and the first value transitioned from zero to nonzero in response to the discovery server incrementing the group name/value count for the first group name and the first value; and

in response to determining that the group name/value count for the first group name and the first value transitioned from zero to nonzero in response to the discovery server incrementing the group name/value count for the first group name and the first value, sending second Join event to the first client in response to the Watch command received from the first client on the first user-specified group name, the second Join event having the first value of the first Join event.

12. The system of claim 11, wherein the operations further comprise:

receiving an initial notification of the first group name from a first discovery server;

issuing a Local Watch command on the first group name to the first discovery server, wherein the Local Watch command on the first group name is a request to receive Join events for the first group name from the first discovery server in response to the first discovery server receiving Join events for the first group name;

receiving a third Join event from the first discovery server having, the third Join event having the first group name and the first value; and

incrementing the group name/value count for the first group name and the first value pair in response to receiving the third Join event from the first discovery server.

13. The system of claim 12, wherein the operations further comprise:

determining that the first discovery server has failed; and

in response to determining that the first discovery server has failed, decrementing the group name/value count for the first group name and the first value.

14. The system of claim 11, wherein the operations further comprise:

receiving a Leave event from a second client device, the Leave event having the first user-specified group name and the first value; and

decrementing the group name/value count for the first user-specified group name and the first value in response to receiving the Leave event having the first user-specified group name and the first value.

15. The system of claim 14, wherein the operations further comprise:

determining that the group name/value count for the first user-specified group name and the first value is zero and that, before decrementing the group name/value count for the first user-specified group name and the first value in response to receiving the Leave event from the second client device, the group name/value count was nonzero;

determining that the Watch command on the first user-specified group name is pending; and

sending a second Leave event having the first value to the first client device.

16. The system of claim 11, wherein the operations further comprise providing a notification of the first group name to another discover server using a metadata protocol, the metadata protocol being distinct from user-specified Join events and user-specified Leave events on user-specified group names.

17. The system of claim 16, wherein providing the notification of the first group name to another discovery server using the metadata protocol comprises sending a metadata Join event to each other discovery server in the plurality of discovery servers, the metadata Join event having a reserved metadata group name and having a second value that includes the first group name.

18. The system of claim 17, wherein the operations further comprise:

determining that the first Join event includes a group name for a new user-specified group; and

issuing a respective Local Watch command on the metadata group name to every other discovery server of the plurality of discovery servers, wherein a Local Watch command on the metadata group name is a request issued to a particular discovery server to receive metadata Join events for the metadata group name from the particular discovery server in response to the particular discovery server receiving metadata Join events for the metadata group name.

19. The system of claim 11, wherein the operations further comprise in response to receiving the Watch command from the first client device, sending, to the first client device, respective Join events having respective values of each nonzero group name/value count having the first group name.

20. The system of claim 11, wherein the operations further comprise:

receiving a Local Watch command on the metadata group name from a second discovery server, wherein a Local Watch command on the metadata group name is a request issued to a particular discovery server to receive metadata Join events for the metadata group name from the particular discovery server in response to the particular discovery server receiving metadata Join events for the metadata group name; and

in response to receiving the Local Watch command on the metadata group name from the second discovery server, issuing a respective Local Watch command on the metadata group name to every other discovery server of the plurality of discovery servers.

21. A computer program product, encoded on one or more non-transitory computer storage media, comprising instructions that when executed by each discovery server of a plurality of discovery servers cause the discovery server to perform operations comprising:

maintaining, by the discovery server a respective group name/value count for each of a plurality of group name/value pairs, each group name/value count being a count for a distinct name-value pair of a user-specified group name and value pair;

receiving a Watch command on a first user-specified group name from a first client device, wherein the Watch command comprises a request to receive Join events for newly added values in the first user-specified group;

receiving a first Join event from another discovery server, the first Join event including the first user-specified group name and a first value, wherein a Join event received from a particular discovery server comprises a notification of a Join command or a Join event being received by the particular discovery server;

incrementing the group name/value count for the first group name and the first value in response to receiving the first Join event;

determining that the group name/value count for the first group name and the first value transitioned from zero to nonzero in response to the discovery server incrementing the group name/value count for the first group name and the first value; and

in response to determining that the group name/value count for the first group name and the first value transitioned from zero to nonzero in response to the discovery server incrementing the group name/value count for the first group name and the first value, sending a second Join event to the first client in response to the Watch command received from the first client on the first user-specified group name, the second Join event having the first value of the first Join event.

22. The computer program product of claim 21, wherein the operations further comprise:

receiving an initial notification of the first group name from a first discovery server;

issuing a Local Watch command on the first group name to the first discovery server, wherein the Local Watch command on the first group name is a request to receive Join events for the first group name from the first discovery server in response to the first discovery server receiving Join events for the first group name;

receiving a third Join event from the first discovery server having, the third Join event having the first group name and the first value; and

incrementing the group name/value count for the first group name and the first value pair in response to receiving the third Join event from the first discovery server.

23. The computer program product of claim 22, wherein the operations further comprise:

determining that the first discovery server has failed; and

in response to determining that the first discovery server has failed, decrementing the group name/value count for the first group name and the first value.

24. The computer program product of claim 21, wherein the operations further comprise:

receiving a Leave event from a second client device, the Leave event having the first user-specified group name and the first value; and

decrementing the group name/value count for the first user-specified group name and the first value in response to receiving the Leave event having the first user-specified group name and the first value.

25. The computer program product of claim 24, wherein the operations further comprise:

determining that the group name/value count for the first user-specified group name and the first value is zero and that, before decrementing the group name/value count for the first user-specified group name and the first value in response to receiving the Leave event from the second client device, the group name/value count was nonzero;

determining that the Watch command on the first user-specified group name is pending; and

sending a second Leave event having the first value to the first client device.

26. The computer program product of claim 21, wherein the operations further comprise providing a notification of the first group name to another discovery server using a metadata protocol, the metadata protocol being distinct from user-specified Join events and user-specified Leave events on user-specified group names.

27. The computer program product of claim 26, wherein providing the notification of the first group name to another discovery server using the metadata protocol comprises sending a metadata Join event to each other discovery server in the plurality of discovery servers, the metadata Join event having a reserved metadata group name and having a second value that includes the first group name.

28. The computer program product of claim 21, wherein the operations further comprise in response to receiving the Watch command from the first client device, sending, to the first client device, respective Join events having respective values of each nonzero group name/value count having the first group name.

29. The computer program product of claim 21, wherein the operations further comprise:

receiving a Local Watch command on the metadata group name from a second discovery server, wherein a Local Watch command on the metadata group name is a request issued to a particular discovery server to receive metadata Join events for the metadata group name from the particular discovery server in response to the particular discovery server receiving metadata Join events for the metadata group name; and

in response to receiving the Local Watch command on the metadata group name from the second discovery server, issuing a respective Local Watch command on the metadata group name to every other discovery server of the plurality of discovery servers.

30. The computer program product of claim 29, wherein the operations further comprise:

determining that the first Join event includes a group name for a new user-specified group; and

issuing a respective Local Watch command on the metadata group name to every other discovery server of the plurality of discovery servers, wherein a Local Watch command on the metadata group name is a request issued to a particular discovery server to receive metadata Join events for the metadata group name from the particular discovery server in response to the particular discovery server receiving metadata Join events for the metadata group name.