Coordinative datacenter processing in a network-based communication system

• US 10,244,038 B2
• Filed: 11/03/2014
• Issued: 03/26/2019
• 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
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): Mendaye, Kidest
• Application Number:
  US14/531,775
• Publication Number:
  US 20160127235A1
• Time in Patent Office: 1,604 Days
• 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, at a first voice over internet protocol (VoIP) datacenter that facilitates setting up communication sessions between VoIP network devices, a first state table comprising a plurality of entries, wherein each entry of the plurality of entries corresponds to a service account and comprises an event type and a data element;

detecting, using at least one processor at the first VoIP datacenter, a first event associated with a first service account and a first event type;

processing, at the first VoIP datacenter, the first event by generating a first data element for the first event type for the first service account;

sending, to a second VoIP datacenter that facilitates setting up communication sessions between VoIP network devices, a first message that comprises the first data element for first event type for the first service account that causes the second VoIP datacenter to update the first service account and the first event type in a second state table at the second VoIP datacenter with the first data element without the second VoIP datacenter processing the first event;

updating, using the at least one processor at the first VoIP datacenter, an entry associated with the first service account and the first event type in the first state table based on the first data element;

receiving, from the second VoIP datacenter based on the second VoIP datacenter generating the second data element by processing a second event associated with the first service account and the first event type, a second message associated with the first service account comprising the first event type and a second data element;

incrementing a message count associated with the second message upon receiving the second message from the VoIP second datacenter;

updating, at the first VoIP datacenter and without processing the second event, the entry associated with the first service account and the first event type in the first state table with the second data element; and

incrementing the message count associated with the second message upon receiving a copy of the second message from a third VoIP datacenter.

2. The method of claim 1, wherein updating the entry in the first state table for the first service account and the first event type based on the first data element comprises adding the entry associated with the first service account to the first state table, the added entry having the first data element for the first event type.

3. The method of claim 2, wherein updating the entry in the first state table for the first service account and the first event type based on the second data element comprises removing the entry associated with the first service account and the first event type from the first state table.

4. The method of claim 1, wherein the first message is configured to update an entry at the second VoIP datacenter associated with the first service account and the first event type within the second state table.

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:

sending the second message to a third VoIP datacenter; and

receiving a copy of the second message from the third VoIP datacenter.

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

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

9. The method of claim 8, further comprising determining whether the former value of the second message matches a current value of the entry associated with the first service account and first event type in the first state table.

10. The method of claim 9, wherein updating the entry in the first state table for the first service account and the first event type based on the second data element comprises replacing the current value of the entry associated with the first service account and the first event type with the updated value of the second message.

11. 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, at a first voice over internet protocol (VoIP) datacenter that facilitates setting up communication sessions between VoIP network devices, a first state table comprising a plurality of entries, wherein each entry of the plurality of entries corresponds to a service account and comprises an event type and a data element;

detect, at the first VoIP datacenter, a first event associated with a first service account and a first event type;

process, at the first VoIP datacenter, the first event by generating a first data element for the first event type for the first service account;

send, to a second VoIP datacenter that facilitates setting up communication sessions between VoIP network devices, a first message that comprises the first data element for first event type for the first service account that causes the second VoIP datacenter to update the first service account and the first event type in a second state table at the second VoIP datacenter with the first data element without the second VoIP datacenter processing the first event;

update, at the first VoIP datacenter, an entry associated with the first service account and the first event type in the first state table based on the first data element;

receive, from the second VoIP datacenter, a second message associated with the first service account comprising the first event type and a second data element based on the second VoIP datacenter generating the second data element by processing a second event associated with the first service account and the first event type;

increment a message count associated with the second message upon receiving the second message from the VoIP second datacenter;

update, at the first VoIP datacenter and without processing the second event, the entry associated with the first service account and the first event type in the first state table with the second data element; and

increment the message count associated with the second message upon receiving a copy of the second message from a third VoIP datacenter.

12. The system of claim 11, further comprising instructions that cause the system to:

send the second message to a third VoIP datacenter; and

receive a copy of the second message from the third VoIP datacenter.

13. The system of claim 12, wherein the second message is sent to the third VoIP datacenter based on the message count associated with the second message being below a threshold count.

14. The system of claim 11, updating the entry in the first state table for the first service account and the first event type based on the first data element comprises adding the entry associated with the first service account to the first state table, the added entry having the first data element for the first event type.

15. The system of claim 11, wherein the first message is one of an announce message, a replace message, and a withdraw message.

16. A non-transitory computer readable medium storing instructions that, when executed by at least one processor, cause a computer system to:

maintain, at a first voice over internet protocol (VoIP) datacenter that sets up direct media bridges between VoIP network devices to facilitate communication sessions, a first state table comprising a plurality of entries, wherein each entry of the plurality of entries corresponds to a service account and comprises an event type and a data element;

detect, using at least one processor at the first VoIP datacenter, a first event associated with a first service account and a first event type, wherein the first event occurs outside of the first VoIP datacenter;

process, at the first VoIP datacenter, the first event by generating a first data element for the first event type for the first service account;

send, to a second VoIP datacenter that sets up direct media bridges between VoIP network devices to facilitate communication sessions, a first message that comprises the first data element for first event type for the first service account that causes the second VoIP datacenter to update the first service account and the first event type in a second state table at the second VoIP datacenter with the first data element without the second VoIP datacenter processing the first event;

update, using the at least one processor at a first VoIP datacenter, an entry associated with the first service account and the first event type in the first state table based on the first data element;

receive, from the second VoIP datacenter, a second message associated with the first service account comprising the first event type and a second data element based on the second VoIP datacenter generating the second data element by processing a second event associated with the first service account and the first event type;

increment a message count associated with the second message upon receiving the second message from the VoIP second datacenter;

update, at a first VoIP datacenter and without processing the second event, the entry associated with the first service account and the first event type in the first state table with the second data element; and

increment the message count associated with the second message upon receiving a copy of the second message from a third VoIP datacenter.

17. The non-transitory computer readable medium of claim 16, wherein updating the entry in the first state table for the first service account and the first event type based on the first data element comprises adding the entry associated with the first service account to the first state table, the added entry having the first data element for the first event type.

18. The non-transitory computer readable medium of claim 17, wherein updating the entry in the first state table for the first service account and the first event type based on the second data element comprises removing the entry associated with the first service account and the first event type from the first state table.

19. The non-transitory computer readable medium of claim 16, wherein the first message is configured to update an entry at the second VoIP datacenter associated with the first service account and the first event type within the second state table.

20. The non-transitory computer readable medium method of claim 16, wherein the first message is one of an announce message, a replace message, and a withdraw message.