Fault-tolerant server for collaborative computing

• US 7,484,115 B2
• Filed: 11/12/2004
• Issued: 01/27/2009
• Est. Priority Date: 12/29/2000
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Zhao, Bin, Zhu, Min
• Primary Examiner(s): Maskulinski; Michael C
• Application Number:
  US10/987,245
• Publication Number:
  US 20050086556A1
• Time in Patent Office: 1,537 Days
• Field of Search: 714/4
• US Class Current: 714/4.12
• CPC Class Codes: H04L 1/22 using redundant apparatus to increase reliability
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1012 based on compliance of requirements or conditions with available server resources
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A distributed collaborative computer system is provided that comprises a plurality of server computers interconnected via a high-speed link. Client computers can connect to any available server computer and start or join a conference hosted on either the server computer to which the client computer is connected or any other server in the system. As a result, the system and method of the present invention is easily scalable to support an arbitrary number of participants to a conference by merely adding the appropriate number of server computers to the system. In addition, by replicating the conference information on more than one server computer, the single point of failure limitation is eliminated. In fact, if a server hosting or participating in a conference malfunctions, the failure is detected by other server computers and the client computer is able to reconnect to the conference through a new server computer.

Claims

1. A method of distributed collaborative computing comprising:

partitioning a collaborative function into a plurality of sub-functions;

assigning at least one of the plurality of sub-functions to each of a plurality of collaboration servers;

associating a zone manager with each of the plurality of collaboration servers and a zone manager with a meeting manager;

communicating state information for each of the plurality of collaboration servers to the meeting manager, wherein the step of communicating state information comprises communicating the state information for each of the plurality of collaboration servers from the respective zone manager to the zone manager of the meeting manager;

monitoring the plurality of collaboration servers for failures;

launching, upon detecting failure of one of the plurality of collaboration servers, a replacement collaboration server; and

recovering the state information for the failed collaboration server from the meeting manager into the replacement collaboration server.

2. The method of claim 1, wherein the recovering step comprises recovering the state information for the failed collaboration server from the zone manager of the meeting manager.

3. The method of claim 1, wherein the step of monitoring for failures comprises:

sending messages from each of the plurality of collaboration servers to the meeting manager; and

detecting failure of one of the collaboration servers when the meeting manager ceases to receive messages from the respective collaboration server.

4. The method of claim 3, wherein the messages comprise heartbeat messages.

5. The method of claim 1, wherein the state information for each of the plurality of collaboration servers comprises configuration information.

6. The method of claim 1, wherein the state information for each of the plurality of collaboration servers comprises quality of service parameters.

7. The method of claim 1, wherein the state information for each of the plurality of collaboration servers comprises current meeting data.

8. The method of claim 1, wherein the step of launching the replacement collaboration server comprises:

sending a request for the replacement collaboration server from the meeting manager to a process manager; and

launching the replacement collaboration server using the process manager.

9. A method of distributed collaborative computing comprising:

partitioning a collaborative function into a plurality of sub-functions;

assigning at least one of the plurality of sub-functions to each of a plurality of collaboration servers;

communicating state information for each of the plurality of collaboration servers to a meeting manager;

monitoring the plurality of collaboration servers for failures;

launching a plurality of application servers;

monitoring the plurality of application servers for failures;

launching, upon detecting failure of one of the plurality of collaboration servers, a replacement collaboration server;

recovering the state information for the failed collaboration server from the meeting manager into the replacement collaboration server; and

upon detecting failure of one of the plurality of application servers, launching a replacement application server.

10. The method of claim 9, further comprising:

connecting each of the plurality of application servers to one of the plurality of collaboration servers; and

upon detecting failure of one of the plurality of application servers, reconnecting the respective collaboration server to the replacement collaboration server.

11. The method of claim 10, wherein the step of monitoring the plurality of application servers for failures comprises monitoring each of the plurality of application severs for failure using the respective collaboration server.

12. The method of claim 11, wherein upon detecting failure of one of the plurality of application servers, the respective collaboration server sends a request to a process manager to launch the replacement application server.

13. The method of claim 10, wherein upon detecting failure of one of the plurality of application servers, the respective collaboration server is temporarily placed in a suspended state.

14. Software encoded in one or more computer-readable media and when executed operable to:

partition a collaborative function into a plurality of sub-functions;

assign at least one of the plurality of sub-functions to each of a plurality of collaboration servers;

communicate state information for each of the plurality of collaboration servers to a meeting manager;

monitor the plurality of collaboration servers for failures;

launch a plurality of application servers;

monitor the plurality of application servers for failures;

launch a replacement collaboration server upon detecting a failure of one of the plurality of collaboration servers;

recover the state information for the failed collaboration server from the meeting manager into the replacement collaboration server; and

launch a replacement application server upon detecting a failure of one of the plurality of application servers.

15. The software encoded in one or more computer-readable media as defined in claim 14 further operable to:

associate a zone manager with each of the plurality of collaboration servers;

associate a zone manager with the meeting manager; and

wherein the instructions operable to communicate the state information comprise instructions operable to communicate the state information for each of the plurality of collaboration servers from the respective zone manager to the zone manager of the meeting manager.

16. The software encoded in one or more computer-readable media as defined in claim 15 further operable to:

recover the state information for the failed collaboration server from the zone manager of the meeting manager.

17. The software encoded in one or more computer-readable media as defined in claim 14 further operable to:

send messages from each of the plurality of collaboration servers to the meeting manager; and

detect the failure of one of the collaboration servers when the meeting manager ceases to receive messages from the respective collaboration server.

18. The software encoded in one or more computer-readable media as defined in claim 14 further operable to:

send a request for the replacement collaboration server from the meeting manager to a process manager; and

launch the replacement collaboration server using the process manager.

19. The software encoded in one or more computer-readable media as defined in claim 14 further operable to:

connect each of the plurality of application servers to one of the plurality of collaboration servers; and

reconnect the respective collaboration server to the replacement collaboration server upon detecting a failure of one of the plurality of application servers.

20. The software encoded in one or more computer-readable media as defined in claim 19 further operable to:

place the respective collaboration server in a temporarily suspended state upon detecting failure of one of the plurality of application servers.

21. An apparatus comprising:

means for partitioning a collaborative function into a plurality of sub-functions;

means for assigning at least one of the plurality of sub-functions to each of a plurality of collaboration servers;

means for associating a zone manager with each of the plurality of collaboration servers;

means for associating a zone manager with a meeting manager;

means for communicating state information for each of the plurality of collaboration servers to the meeting manager, wherein the means for communicating state information comprise means for communicating the state information for each of the plurality of collaboration servers from the respective zone manager to the zone manager of the meeting manager;

means for monitoring the plurality of collaboration servers for failures;

means for launching a replacement collaboration server upon detecting a failure of one of the plurality of collaboration servers; and

means for recovering the state information for the failed collaboration server from the meeting manager into the replacement collaboration server.

22. The apparatus of claim 21, further comprising:

means for sending a request for the replacement collaboration server from the meeting manager to a process manager; and

means for launching the replacement collaboration server using the process manager.