Systems and methods for storing and transferring message data

• US 10,389,674 B2
• Filed: 06/27/2018
• Issued: 08/20/2019
• Est. Priority Date: 10/09/2015
• Status: Active Grant

• Current Assignee: Satori Worldwide, LLC (AppLovin Corporation)
• Original Assignee: Satori Worldwide, LLC (AppLovin Corporation)
• Inventors: Milyakov, Igor
• Primary Examiner(s): Dinh, Khanh Q
• Application Number:
  US16/020,455
• Publication Number:
  US 20180331992A1
• Time in Patent Office: 419 Days
• Field of Search: 709220, 709224, 709226, 709228
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/10 Multimedia information
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/226 Delivery according to priorities
• 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 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/10 Streamlined, light-weight or high-speed protocols, e.g. express transfer protocol [XTP] or byte stream
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method includes storing, by one or more computer processors, a plurality of blocks in a queue, wherein each block includes at least one received message, and wherein each block is associated with a time that the block was stored in the queue. The method further includes designating, by the one or more computer processors, as inactive one or more blocks having associated storage times that are older than a first time. The method further includes reading, by the one or more computer processors, messages from inactive blocks until a second time that is older than the first time. The method further includes deleting, by the one or more computer processors, one or more inactive blocks from the queue having associated storage times that are older than the second time.

Claims

1. A method, comprising:

storing, by one or more computer processors, a plurality of blocks in a queue,

wherein each block includes at least one received message, and

wherein each block is associated with a time that the block was stored in the queue;

designating, by the one or more computer processors, as inactive one or more blocks having associated storage times that are older than a first time;

reading, by the one or more computer processors, messages from inactive blocks until a second time that is older than the first time; and

deleting, by the one or more computer processors, one or more inactive blocks from the queue having associated storage times that are older than the second time.

2. The method of claim 1, wherein the storage times increase from a block designating a head of the queue to a block designating a tail of the queue.

3. The method of claim 2, wherein new blocks are stored at the tail of the queue.

4. The method of claim 2, wherein messages from one or more blocks in the queue are read beginning at the head of the queue.

5. The method of claim 1, wherein each block is assigned a time-to-reside, and wherein a block is designated as inactive when the time-to-reside of the block expires.

6. The method of claim 1, wherein reading messages from inactive blocks until the second time that is older than the first time comprises:

providing additional time to read messages from a block after a time-to-reside for the block expires.

7. The method of claim 1, wherein each block is assigned a time-to-live, and wherein a block is deleted when the time-to-live of the block expires.

8. The method of claim 1, wherein the plurality of blocks are stored in the queue according to an order.

9. The method of claim 1, comprising:

sending read messages to a respective subscriber.

10. The method of claim 1, wherein the messages are received from at least one publisher for a single channel.

11. A system, comprising:

one or more computer processors programmed to perform operations to

store a plurality of blocks in a queue,

wherein each block includes at least one received message, and

wherein each block is associated with a time that the block was stored in the queue;

designate as inactive one or more blocks having associated storage times that are older than a first time;

read messages from inactive blocks until a second time that is older than the first time; and

delete one or more inactive blocks from the queue having associated storage times that are older than the second time.

12. The system of claim 11, wherein the storage times increase from a block designating a head of the queue to a block designating a tail of the queue.

13. The system of claim 12, wherein new blocks are stored at the tail of the queue.

14. The system of claim 12, wherein messages from one or more blocks in the queue are read beginning at the head of the queue.

15. The system of claim 11, wherein each block is assigned a time-to-reside, and wherein a block is designated as inactive when the time-to-reside of the block expires.

16. The system of claim 11, wherein to read the messages from inactive blocks until the second time that is older than the first time the one or more computer processors are further to:

provide additional time to read the messages from a block after a time-to-reside for the block expires.

17. The system of claim 11, wherein each block is assigned a time-to-live, and wherein a block is deleted when the time-to-live of the block expires.

18. The system of claim 11, wherein the plurality of blocks are stored in the queue according to an order.

19. The system of claim 11, wherein the operations are further to:

send read messages to a respective subscriber.

20. A non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more computer processors, cause the one or more computer processors to:

store a plurality of blocks in a queue,

wherein each block includes at least one received message, and

wherein each block is associated with a time that the block was stored in the queue;

designate as inactive one or more blocks having associated storage times that are older than a first time;

read messages from inactive blocks a second time that is older than the first time; and

delete one or more inactive blocks from the queue having associated storage times that are older than the second time.