Storage and processing of ephemeral messages

Patent metadata

Field	Value
Publication number	US-9294425-B1
Application number	US-201514615553-A
Country	US
Kind code	B1
Filing date	Feb 6, 2015
Priority date	Feb 6, 2015
Publication date	Mar 22, 2016
Grant date	Mar 22, 2016

Abstract

A server includes volatile and non-volatile memories for storing messages received from a client device. A message reception module of the server stores a message received from a first client device in the volatile memory for an extended time period based on an indicator included in the message. The message reception module deletes the message from the volatile memory based on detection of a triggering event or stores the message in the non-volatile memory based on not detecting the triggering event before the extended time period has expired. The triggering event may include the message having been read by all specified recipients of the message. The indicator may be included in the message based on a relationship of the message to other messages. The message including the indicator may be related to other messages as part of a same conversation that has been determined to be suitable for short-term storage.

First claim

What is claimed is:

1. A server comprising:
at least one processor;
a volatile memory for storing messages received from client devices;
a non-volatile memory for storing messages received from client devices; and
a message reception module implemented by the at least one processor and configured to:
store a message received from a first client device in the volatile memory for an extended time period based on an indicator included in the message;
delete the message from the volatile memory based on detection of a triggering event; and
copy the message from the volatile memory to the non-volatile memory based on not detecting the triggering event during the extended time period.

2. The server of claim 1 , wherein the triggering event comprises the message having been read by all specified recipients of the message.

3. The server of claim 1 , wherein the indicator is included in the message based on at least one of: a mode of operation of the first client device; a relation of the message to another message; a count of messages related to the message; a size of the message; a recipient of the message; or a subject of the message.

4. The server of claim 3 , wherein the relation of the message to the other message including the indicator comprises being part of a same conversation as the other message wherein the other message was deleted within the extended time period.

5. The server of claim 3 , wherein the indicator is included in the message based on a chatroom mode of operation of the first client device, the triggering event comprises exiting the chatroom mode and the messaging module is further configured to transmit a warning to the first client device that the message will be automatically deleted upon exiting chatroom mode.

6. The server of claim 1 , further comprising a message transmission module implemented by the at least one processor and configured to:
transmit the message to a second client device associated with a recipient of the message upon receipt of a request from said second client device;
insert instructions in the message to instruct the second client device to display the message for only a specified time period; and
delete the message from at least one of the volatile memory and the non-volatile memory based on the specified time period expiring.

7. The server of claim 6 , wherein the triggering event comprises responding to the message at the second client device.

8. A method comprising:
storing a message received from a first client device in a volatile memory for an extended time period based on an indicator included in the message;
deleting the message from the volatile memory based on detection of a triggering event; and
copying the message from the volatile memory to a non-volatile memory based on not detecting the triggering event during the extended time period.

9. The method of claim 8 , wherein the triggering event comprises the message having been read by all specified recipients of the message.

10. The method of claim 8 , wherein the indicator is included in the message based on at least one of: a mode of operation of the first client device; a relation of the message to another message; a count of messages related to the message; a size of the message; a recipient of the message; or a subject of the message.

11. The method of claim 10 , wherein the relation of the message to the other message including the indicator comprises being part of a same conversation as the other message wherein the other message was deleted within the extended time period.

12. The method of claim 10 , wherein the indicator is included in the message based on a chatroom mode of operation of the first client device, the triggering event comprises exiting the chatroom mode and the messaging module is further configured to transmit a warning to the first client device that the message will be automatically deleted upon exiting chatroom mode.

13. The method of claim 8 , further comprising:
transmitting the message to a second client device associated with a recipient of the message upon receipt of a request from said second client device; and
inserting instructions in the message to instruct the second client device to display the message for only a specified time period; and
deleting the message from at least one of the volatile memory and the non-volatile memory based on the specified time period expiring.

14. The method of claim 13 , wherein the triggering event comprises responding to the message at the second client device.

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:
storing a message received from a first client device in a volatile memory for an extended time period based on an indicator included in the message;
deleting the message from the volatile memory based on detection of a triggering event; and
copying the message from the volatile memory to a non-volatile memory based on not detecting the triggering event during the extended time period.

16. The computer-readable medium of claim 15 , wherein the triggering event comprises the message having been read by all specified recipients of the message.

17. The computer-readable medium of claim 15 , wherein the indicator is included in the message based on at least one of: a mode of operation of the first client device; a relation of the message to another message; a count of messages related to the message; a size of the message; a recipient of the message; or a subject of the message.

18. The computer-readable medium of claim 15 , wherein the relation of the message to the other message including the indicator comprises being part of a same conversation as the other message wherein the other message was deleted within the extended time period.

19. The computer-readable medium of claim 15 , wherein the indicator is included in the message based on a chatroom mode of operation of the first client device and the triggering event comprises exiting the chatroom mode, the steps further comprising transmitting a warning to the first client device that the message will be automatically deleted upon exiting chatroom mode.

20. The computer-readable medium of claim 15 , the steps further comprising:
transmitting the message to a second client device associated with a recipient of the message upon receipt of a request from said second client device; and
inserting instructions in the message to instruct the second client device to display the message for only a specified time period; and
deleting the message from at least one of the volatile memory and the non-volatile memory based on the specified time period expiring;
wherein the triggering event comprises responding to the message at the second client device.

Assignees

• Snapchat Inc

Inventors

• Son Aaron

Classifications

• H04L51/34

  Electricity · mapped topic

• H04L51/18 Primary

  Commands or executable codes · CPC title

• H04L51/234

  for tracking messages · CPC title

• H04L51/42 Primary

  Mailbox-related aspects, e.g. synchronisation of mailboxes · CPC title

• H04L51/216

  Handling conversation history, e.g. grouping of messages in sessions or threads · CPC title