Message queues for rapid re-hosting of client devices

• US 9,313,154 B1
• Filed: 03/25/2015
• Issued: 04/12/2016
• Est. Priority Date: 03/25/2015
• Status: Active Grant

• Current Assignee: Snapchat Inc (Snap, Inc.)
• Original Assignee: Snapchat Inc (Snap, Inc.)
• Inventors: Son, Aaron
• Primary Examiner(s): Patel, Chirag R
• Application Number:
  US14/668,336
• Time in Patent Office: 384 Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 51/06 Message adaptation to terminal or network requirements
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/234 for tracking messages
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 67/01 Protocols
• 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/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

Connected gateway servers relay an electronic message from a first client device to a second client device by storing the message in respective user message queues associated with the sender and/or recipient of the message and then sending the message along a sequence of gateway servers to a gateway server that hosts the second client device. Upon receiving the electronic message at a first gateway server, a second gateway server that is hosting the second client device is identified and a sequence of gateway servers starting at the first gateway server and ending at the second gateway server is determined. Each gateway server in the sequence relays the message to the following gateway server in the sequence while maintaining user message queues. Failure of the last gateway server in the sequence results in the penultimate gateway server in the sequence assuming the responsibility of hosting the second client device.

Claims

1. A method for relaying electronic messages between connected gateway servers, the method comprising:

receiving an electronic message at a first gateway server of a plurality of gateway servers from a first client device associated with a sender of the electronic message;

identifying a second gateway server, of the plurality of gateway servers, that is hosting a second client device that is associated with a recipient of the electronic message;

determining a sequence of gateway servers, of the plurality of gateway servers, that starts at the first gateway server and ends at the second gateway server;

performing by each gateway server in the sequence of the gateway servers;

storing the electronic message in respective user message queues associated with at least one of the sender and the recipient of the electronic message, and

sending the electronic message to a subsequent gateway server in the sequence based on the subsequent gateway server following it in the sequence;

detecting that the last gateway server in the sequence is not functioning; and

hosting the second client device by the penultimate gateway server in the sequence.

2. The method of claim 1, further comprising each of the gateway servers in the sequence acknowledging receipt of the electronic message after receiving the electronic message.

3. The method of claim 2, wherein detecting that the last gateway server in the sequence is not functioning is based on the last gateway server failing to acknowledge receipt of the electronic message.

4. The method of claim 1, further comprising:

assigning a first chain of the gateway servers in the sequence to the sender of the message, the first chain starting at the first gateway server and ending at a third gateway server of the sequence that is prior to the second gateway server;

assigning a second chain of the gateway servers in the sequence to the recipient of the message, the second chain starting at the gateway server of the sequence that follows the third gateway server in the sequence and ending at the second gateway server; and

storing the electronic message in user message queues associated with the sender in the gateway servers of the first chain and storing the electronic message in user message queues associated with the recipient in the gateway servers of the second chain.

5. The method of claim 1, further comprising deleting the electronic message from the respective user message queues of each of the gateway servers in the sequence based on detection of a triggering event.

6. The method of claim 5, wherein the triggering event comprises the electronic message being received at the second client device or a response to the electronic message being sent from the second client device.

7. The method of claim 5, further comprising:

each gateway server in the sequence removing the electronic message from their respective user message queues based on expiration of a specified time period;

storing a copy of the electronic message in an external storage based on expiration of the specified time period; and

deleting the electronic message from the external storage based on detection of the triggering event.

8. A system comprising:

a plurality of gateway servers connected via a network, each of the plurality of gateway servers configured to relay an electronic message by;

storing the electronic message in respective user message queues associated with at least one of a sender and a recipient of the electronic message; and

sending the electronic message to another gateway server of the plurality of gateway servers; and

a message module implemented by at least one processor and configured to;

detect that the electronic message, sent from a first client device associated with the sender, has been received at a first gateway server of the plurality of gateway servers;

identify a second gateway server, of the plurality of gateway servers, that is hosting a second client device that is associated the recipient of the electronic message;

determine a sequence of gateway servers that starts at the first gateway server and ends at the second gateway server;

instruct each of the gateway servers in the sequence to relay the electronic message to a subsequent gateway server in the sequence based on the subsequent gateway server following it in the sequence;

detect that the last gateway server in the sequence is not functioning; and

instruct the penultimate gateway server in the sequence to host the second client device.

9. The system of claim 8, wherein each of the gateway servers is further configured to acknowledge receipt of the electronic message after storing the electronic message.

10. The system of claim 9, wherein the message module is further configured to detect that the last gateway server in the sequence is not functioning based on the last gateway server failing to acknowledge receipt of the electronic message.

11. The system of claim 8, wherein the message module is further configured to:

assign a first chain of the gateway servers in the sequence to the sender of the message, the first chain starting at the first gateway server and ending at a third gateway server of the sequence that is prior to the second gateway server;

assign a second chain of the gateway servers in the sequence to the recipient of the message, the second chain starting at the gateway server of the sequence that follows the third gateway server in the sequence and ending at the second gateway server; and

store the electronic message in user message queues associated with the sender in the gateway servers of the first chain and store the electronic message in user message queues associated with the recipient in the gateway servers of the second chain.

12. The system of claim 8, wherein the message module is further configured to instruct each gateway server in the sequence to delete the electronic message from their respective user message queues based on detection of a triggering event.

13. The system of claim 12, wherein the triggering event comprises the electronic message being received at the second client device or a response to the electronic message being sent from the second client device.

14. The system of claim 12, wherein the message module is further configured to:

instruct each gateway server in the sequence to remove the first electronic message from their respective user message queues based on expiration of a specified time period;

store a copy of the first electronic message in an external storage based on expiration of the specified time period; and

instruct the external storage to delete the first electronic message based on detection of the triggering event.

15. A non-transitory computer-readable medium storing program code which, when executed, is operative to cause a computing device to perform the steps of:

receiving an electronic message at a first gateway server of a plurality of gateway servers from a first client device associated with a sender of the electronic message;

identifying a second gateway server, of the plurality of gateway servers, that is hosting a second client device that is associated with a recipient of the electronic message;

determining a sequence of gateway servers, of the plurality of gateway servers, that starts at the first gateway server and ends at the second gateway server;

performing by each of the gateway servers in the sequence;

storing the electronic message in respective user message queues associated with the sender and the recipient of the electronic message, and

sending the electronic message to a subsequent gateway server in the sequence based on the subsequent gateway server following it in the sequence;

detecting that the last gateway server in the sequence is not functioning; and

hosting the second client device by the penultimate gateway server in the sequence.

16. The computer-readable medium of claim 15, the steps further comprising each of the gateway servers in the sequence acknowledging receipt of the electronic message after storing the electronic message, wherein detecting that the last gateway server in the sequence is not functioning is based on the last gateway server not acknowledging receipt of the electronic message.

17. The computer-readable medium of claim 15, the steps further comprising:

synchronizing the user message queues of the gateway servers in the sequence and the user message queues of the last gateway server based on the last gateway server functioning again; and

resuming hosting of the second client device by the last gateway server.

18. The computer-readable medium of claim 15, the steps further comprising deleting the electronic message from the respective user message queues of each of the gateway servers in the sequence based on detection of a triggering event.

19. The computer-readable medium of claim 18, wherein the triggering event comprises the electronic message being received at the second client device or a response to the electronic message being sent from the second client device.

20. The computer-readable medium of claim 18, the steps further comprising:

removing the electronic message from their respective user message queues of each of the gateway servers in the sequence based on expiration of a specified time period;

storing a copy of the electronic message in an external storage based on expiration of the specified time period; and

deleting the electronic message from the external storage based on detection of the triggering event.