Systems and methods for event stream management

• US 10,110,727 B2
• Filed: 12/14/2017
• Issued: 10/23/2018
• Est. Priority Date: 01/20/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Prado, Jason, Renie, David Michael, Al-Naffouri, Basel, Ibrahim, Eahab, Pongsajapan, John
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US15/842,870
• Publication Number:
  US 20180109670A1
• Time in Patent Office: 313 Days
• Field of Search: 709206
• CPC Class Codes: H04L 41/5093 wherein the managed service relates to messaging or chat services
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/234 for tracking messages
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04M 1/72436 for text messaging, e.g. short messaging services [SMS] or e-mails

Abstract

A system for managing event streams is provided that includes a volatile memory, a non-volatile memory, and a processor. The volatile memory is configured to store, for each of a plurality of event streams associated with the client device, metadata indicative of events not yet delivered to a client device and the content associated with only a most recent event of the event stream. The non-volatile memory is configured to store the content associated with each of undelivered events. The processor is configured to, upon receiving a request from the client device, retrieve from the volatile memory, without accessing the non-volatile memory, data indicative of a current state of an event stream associated with the client device. The processor is further configured to deliver the retrieved data indicative of the current state of the event stream.

Claims

1. A method comprising:

receiving, by a processor, data of an event stream, each event in the event stream to be delivered electronically to a client device over a network;

storing a data structure indicative of one or more events in the event stream that are not yet delivered to the client device, wherein the event stream is assigned a unique conversation identifier, and wherein the data structure includes;

one or more entries corresponding to the one or more events in the event stream, wherein each of the one or more entries includes a communication number, a recipient identifier associated with a recipient, and a status; and

content of a most recent event of the one or more events in the event stream labeled with the communication number for the most recent event and a sender identifier associated with the most recent event;

retrieving, by the processor, from the data structure, data indicative of a current state of the event stream, wherein the current state of the event stream includes a number of events not yet delivered to the client device and the content of the most recent event in the event stream; and

sending, by the processor, the retrieved data indicative of the current state of the event stream to the client device.

2. The method of claim 1, further comprising receiving an event stream update request from the client device, wherein the retrieving is performed in response to receiving the event stream update request.

3. The method of claim 1, further comprising, after the sending, deleting the one or more entries corresponding to the one or more events in the event stream from the data structure.

4. The method of claim 1, wherein the client device is associated with the recipient.

5. The method of claim 1, wherein the communication number in each of the one or more entries is a timestamp used to identify the event.

6. The method of claim 1, wherein the status in each of the one or more entries is one of an undelivered event status or an unread event status.

7. The method of claim 1, wherein storing the data structure comprises storing an in-memory table in a volatile memory.

8. The method of claim 1, further comprising storing a second data structure in an on-disk table, wherein the second data structure includes one or more entries that each include content of a respective individual event of the one or more events and a sender identifier associated with the individual event, wherein each of the one or more entries is labeled by the unique conversation identifier and a communication number for the respective individual event.

9. The method of claim 1, further comprising:

receiving, by the processor, additional data of the event stream, wherein the additional data includes an additional event in the event stream to be delivered electronically to the client device over the network; and

in response to receiving the additional data, overwriting the content of the most recent event in the data structure with content of the additional event labeled with a communication number of the additional event and a sender identifier associated with the additional event.

10. The method of claim 9, wherein the additional event is associated with a timestamp that corresponds to a time that is later than a time corresponding to a timestamp of the most recent event.

12. The system of claim 8, the operations further comprising receiving an event stream update request from the client device, wherein the retrieving is performed in response to receiving the event stream update request.

13. The system of claim 8, the operations further comprising, after the sending, deleting the one or more entries corresponding to the one or more events in the event stream from the data structure.

14. The system of claim 8, wherein the communication number in each of the one or more entries is a timestamp used to identify the event.

15. The system of claim 8, the operations further comprising storing a second data structure in an on-disk table, wherein the second data structure includes one or more entries that each include content of a respective individual event of the one or more events and a sender identifier associated with the individual event, wherein each of the one or more entries is labeled by the unique conversation identifier and a communication number for the respective individual event.

11. A system comprising:

one or more processors; and

a non-transitory computer-readable medium including instructions that when operated upon by the one or more processors cause the one or more processors to perform operations comprising;

receiving data of an event stream, each event in the event stream to be delivered electronically to a client device over a network;

storing a data structure indicative of one or more events in the event stream that are not yet delivered to the client device, wherein the event stream is assigned a unique conversation identifier, and wherein the data structure includes;

one or more entries corresponding to the one or more events in the event stream, wherein each of the one or more entries includes a communication number, a recipient identifier associated with a recipient, and a status; and

content of a most recent event of the one or more events in the event stream labeled with the communication number for the most recent event and a sender identifier associated with the most recent event;

retrieving from the data structure, data indicative of a current state of the event stream, wherein the current state of the event stream includes a number of events not yet delivered to the client device and the content of the most recent event in the event stream; and

sending the retrieved data indicative of the current state of the event stream to the client device.

16. A non-transitory computer-readable medium storing a computer program that is executable by at least one processor, the computer program including instructions that cause the at least one processor to perform operations comprising:

receiving data of an event stream, each event in the event stream to be delivered electronically to a client device over a network;

storing a data structure indicative of one or more events in the event stream that are not yet delivered to the client device, wherein the event stream is assigned a unique conversation identifier, and wherein the data structure includes;

one or more entries corresponding to the one or more events in the event stream, wherein each of the one or more entries includes a communication number, a recipient identifier associated with a recipient, and a status; and

content of a most recent event of the one or more events in the event stream labeled with the communication number for the most recent event and a sender identifier associated with the most recent event;

retrieving from the data structure, data indicative of a current state of the event stream, wherein the current state of the event stream includes a number of events not yet delivered to the client device and the content of the most recent event in the event stream; and

sending the retrieved data indicative of the current state of the event stream to the client device.

17. The non-transitory computer-readable medium of claim 16, wherein the operations further comprise receiving an event stream update request from the client device, wherein the retrieving is performed in response to receiving the event stream update request.

18. The non-transitory computer-readable medium of claim 16, wherein the operations further comprise, after the sending, deleting the one or more entries corresponding to the one or more events in the event stream from the data structure.

19. The non-transitory computer-readable medium of claim 16, wherein the operations further comprise:

receiving additional data of the event stream, wherein the additional data includes an additional event in the event stream to be delivered electronically to the client device over the network; and

in response to receiving the additional data, overwriting the content of the most recent event in the data structure with content of the additional event labeled with a communication number of the additional event and a sender identifier associated with the additional event.

20. The non-transitory computer-readable medium of claim 19, wherein the additional event is associated with a timestamp that corresponds to a time that is later than a time corresponding to a timestamp of the most recent event.