COORDINATIVE DATACENTER PROCESSING IN A NETWORK-BASED COMMUNICATION SYSTEM

• US 20160127235A1
• Filed: 11/03/2014
• Published: 05/05/2016
• Est. Priority Date: 11/03/2014
• Status: Active Grant

• Current Assignee: GOTO Communications Incorporated
• Original Assignee: Jive Communications Incorporated (LogMeIn, Inc.)
• Inventors: Zourzouvillys, Theo Peter
• Granted Patent: US 10,244,038 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

The present application details exemplary methods and systems for providing current state information to multiple active datacenters within a network-based communication system. For example, a datacenter can detect an event that occurs within the network-based communication system. Upon detecting the event, the datacenter can update a state table on the datacenter based on state information associated with the event. In addition, the datacenter can send a state information message to other datacenters in the network-based communication system. The state information message can include state information associated with the event. The other datacenters in the network-based communication system can update their respective state tables using the state information in the state information message without needing to individually process the event.

Claims

1. A method comprising:

maintaining a state table comprising a plurality of contexts, each of the plurality of contexts associated with a plurality of handles and entries;

detecting, using at least one processor, a first event associated with a first context from the plurality of contexts;

based on the first event, identifying a first handle corresponding to the first context and a first data element corresponding to the first context;

sending, to a datacenter, a first message comprising the first handle and the first data element;

updating, using the at least one processor, an entry associated with the first context in the state table based on the first handle and the first data element;

receiving, from the datacenter, a second message comprising a second handle corresponding to the first context and a second data element corresponding to the first context; and

updating the entry associated with the first context in the state table based on the second handle and the second data element.

2. The method of claim 1, wherein updating the entry in the state table based on the first handle and the first data element comprises adding an entry associated with the first context to the state table, the added entry having the first handle and the first data element.

3. The method of claim 2, wherein updating the entry in the state table based on the second handle and the second data element comprises removing the entry associated with the first context from the state table.

4. The method of claim 1, wherein the first message is configured to update an entry associated with the first context within the state table on the datacenter.

5. The method of claim 1, wherein the first message is one of an announce message, a replace message, and a withdraw message.

6. The method of claim 1, further comprising incrementing a message count associated with the second message upon receiving the second message from the datacenter.

7. The method of claim 6, further comprising sending the second message to a second datacenter.

8. The method of claim 7, wherein the second message is sent to the second datacenter based on the message count associated with the second message being below a threshold count.

9. The method of claim 7, further comprising:

receiving a copy of the second message from the second datacenter; and

incrementing the message count associated with the second message upon receiving the copy of the second message.

10. The method of claim 1, wherein the second data element comprises a former value and an updated value.

11. The method of claim 10, further comprising determining whether the former value of the second message matches a current value of the entry associated with the first context in the state table.

12. The method of claim 11, wherein updating the entry in the state table based on the second handle and the second data element comprises replacing the current value of the entry associated with the first context with the updated value of the second message.

13. A method comprising:

maintaining a state table comprising an entry, the entry comprising an entry handle, an entry former value, and an entry current value;

receiving, from a first datacenter, a first message comprising a first handle and a first data element, the first data element comprising a first message former value and a first message updated value;

comparing, using at least one processor, the entry current value to the first message former value to determine whether the entry current value matches the first message former value;

based on determining that the entry current value and the message former value match, updating the state table by replacing the entry former value with the entry current value and replacing the entry current value with the first message updated value;

receiving, from a second datacenter, a second message comprising a second handle and a second data element, the second data element comprising a send message former value and a second message updated value;

detecting a conflict in the entry in the state table when the current value in the state table does not match the former value of the second data element, and when the former value in the state table matches the former value of the second data element;

identifying a corrected current value by comparing the updated value of the first data element and the updated value of the second data element with the former value of the entity in the state table; and

updating the current value in the state table with the corrected current value.

14. The method of claim 13 further comprising replacing the former value in the state table with a conflict code upon updating the current value in the state table with the corrected current value.

15. The method of claim 13, further comprising:

setting a message count associated with the first message to one upon receiving the first message from the first datacenter;

receiving a copy of the first message from the second datacenter;

incrementing the message count associated with the first message upon receiving the copy of the first message from the second datacenter;

receiving a copy of the first message from a third datacenter;

incrementing the message count associated with the first message upon receiving the copy of the first message from the third datacenter.

16. The method of claim 14, further comprising sending the first message to the second datacenter and the third datacenter upon receiving the first message when the message count associated with the first message is equal to one.

17. The method of claim 13, further comprising sending a portion of the state table to the second datacenter based on receiving a request from the second datacenter to send the state table.

18. A system comprising:

at least one processor; and

at least one non-transitory computer readable storage medium storing instructions thereon that, when executed by the at least one processor, cause the system to;

maintain a state table comprising a plurality of contexts, each of the plurality of contexts associated with a plurality of handles and entries;

detect, using at least one processor, a first event associated with a first context from the plurality of contexts;

based on the first event, identify a first handle corresponding to the first context and a first data element corresponding to the first context;

send, to a datacenter, a first message comprising the first handle and the first data element;

update an entry associated with the first context in the state table based on the first handle and the first data element;

receive, from the datacenter, a second message comprising a second handle corresponding to the first context and a second data element corresponding to the first context; and

update the entry associated with the first context in the state table based on the second handle and the second data element.

19. The system of claim 18, further comprising sending the second message to a second datacenter.

20. The system of system 19, further comprising incrementing a message count associated with the second message upon receiving the second message.