Fallback messaging

• US 8,780,703 B1
• Filed: 02/27/2013
• Issued: 07/15/2014
• Est. Priority Date: 01/27/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Eidelson, Benjamin David, Chawla, Jagjit Singh, Prado, Jason
• Primary Examiner(s): Jung, Min
• Application Number:
  US13/778,308
• Time in Patent Office: 503 Days
• US Class Current: 370/228
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/52 for supporting social networking services
• 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

Abstract

A computing device may receive first message data associated with a messaging group. The computing device may associate the first message data with a messaging thread. The computing device may associate a unique session identifier with one or both of the messaging thread and the messaging group. For a first one or more user devices of the messaging group, the computing device may send the message data along with the unique identifier via a native messaging protocol. For a second one or more of the user devices of the messaging group, the computing device may associate a fallback identifier of each of the one or more second user devices with one or both of the messaging thread and the messaging group, and send the first message data and unique identifier via a fallback messaging protocol.

Claims

1. A method comprising:

receiving, at a computing device, first message data associated with (i) a messaging group exchanging messages and (ii) an active messaging thread, the messaging thread having a corresponding unique session identifier;

for a first one or more user devices of the messaging group;

sending, by the computing device, using a first messaging protocol, the first message data along with the unique session identifier corresponding to the messaging thread; and

for a second one or more of the user devices of the messaging group;

assigning, by the computing device, a fallback identifier of each of the one or more second user devices to the messaging thread; and

sending, by the computing device, using a second messaging protocol, the first message data along with the unique session identifier corresponding to the messaging thread.

2. The method of claim 1, further comprising:

receiving, at the computing device, a message via the first messaging protocol; and

responsive to detecting the unique session identifier in the received message, adding, by the computing device, data of the received message to the messaging thread.

3. The method of claim 1, further comprising:

receiving, at the computing device, a message via the first messaging protocol; and

responsive to detecting the unique session identifier in the received message, sending, by the computing device, data of the received message to one or more user devices of the messaging group.

4. The method of claim 1, further comprising:

receiving, at the computing device, a message via a fallback messaging protocol;

associating, by the computing device, the received message with the messaging thread in response to mapping a fallback identifier of the received message to the messaging thread; and

adding, by the computing device, data of the received message to the messaging thread.

5. The method of claim 1, further comprising:

receiving, at the computing device, a message via a fallback messaging protocol;

associating, by the computing device, the received message with the messaging thread in response to mapping a fallback identifier of the received message to the messaging thread; and

sending, by the computing device, data of the received message to one or more user devices of the messaging group.

6. The method of claim 1, wherein the second messaging protocol is one of a text messaging protocol, an email protocol, and an instant messaging protocol.

7. The method of claim 6, wherein the sending messaging protocol is short message service (SMS).

8. The method of claim 1, wherein the first messaging protocol is a native messaging protocol and the second messaging protocol is a fallback messaging protocol.

9. A non-transitory computer readable medium including a computer readable program that, when executed on a computer, causes the computer to:

receive first message data associated with (i) a messaging group exchanging messages and (ii) an active messaging thread, the messaging thread having a corresponding unique session identifier;

for a first one or more user devices of the messaging group;

send, using a first messaging protocol, the first message data along with the unique session identifier corresponding to the messaging thread; and

for a second one or more of the user devices of the messaging group;

assign a fallback identifier of each of the one or more second user devices with the messaging thread; and

send, using a second messaging protocol, the first message data along with the unique session identifier corresponding to the messaging thread.

10. The non-transitory computer readable medium of claim 9, wherein the computer readable program, when executed on the computer, further causes the computer to:

receive a message via the first messaging protocol; and

responsive to detecting the unique session identifier in the received message, add data of the received message to the messaging thread.

11. The non-transitory computer readable medium of claim 9, wherein the computer readable program, when executed on the computer, further causes the computer to:

receive a message via the first messaging protocol; and

responsive to detecting the unique session identifier in the received message, send data of the received message to one or more user devices of the messaging group.

12. non-transitory computer readable medium of claim 9, wherein the computer readable program, when executed on the computer, further causes the computer to:

receive a message via a fallback messaging protocol;

associate the received message with the messaging thread in response to mapping a fallback identifier of the received message to the messaging thread; and

add data of the received message to the messaging thread.

13. The non-transitory computer readable medium of claim 9, wherein the computer readable program, when executed on the computer, further causes the computer to:

receive a message via a fallback messaging protocol;

associate the received message with the messaging thread in response to mapping a fallback identifier of the received message to the messaging thread; and

send data of the received message to one or more user devices of the messaging group.

14. The non-transitory computer readable medium of claim 9, wherein the second messaging protocol is short message service (SMS).

15. The non-transitory computer readable medium of claim 9, wherein the first messaging protocol is a native messaging protocol and the second messaging protocol is a fallback messaging protocol.

16. A system, comprising:

a server configured to;

receive first message data associated with (i) a messaging group exchanging messages and (ii) an active messaging thread, the messaging thread having a corresponding unique session identifier;

for a first one or more user devices of the messaging group;

send, using a first messaging protocol, the first message data along with the unique session identifier corresponding to the messaging thread; and

for a second one or more of the user devices of the messaging group;

assign a fallback identifier of each of the one or more second user devices to the messaging thread; and

send, using a second messaging protocol, the first message data along with the unique session identifier corresponding to the messaging thread.

17. The system of claim 16, wherein the server is further configured to:

receive a message via the first messaging protocol; and

responsive to detecting the unique session identifier in the received message, add data of the received message to the messaging thread.

18. The system of claim 16, wherein the server is further configured to

receive a message via the first messaging protocol;

and

responsive to detecting the unique session identifier in the received message, send data of the received message to one or more user devices of the messaging group.

19. The system of claim 16, wherein the server is further configured to

receive a message via a fallback messaging protocol;

associate the received message with the messaging thread in response to mapping a fallback identifier of the received message to the messaging thread; and

add data of the received message to the messaging thread.

20. The system of claim 16, wherein the server is further configured to

receive a message via a fallback messaging protocol;

associate the received message with the messaging thread in response to mapping a fallback identifier of the received message to the messaging thread; and

send data of the received message to one or more user devices of the messaging group.

21. The system of claim 16, wherein the second messaging protocol is one of a text messaging protocol, an email protocol, and an instant messaging protocol.

22. The system of claim 21, wherein the second messaging protocol is short message service (SMS).

23. The system of claim 16, wherein the first messaging protocol is a native messaging protocol and the second messaging protocol is a fallback messaging protocol.