Systems and methods for state synchronization

Patent metadata

Field	Value
Publication number	US-2023421522-A1
Application number	US-202218048012-A
Country	US
Kind code	A1
Filing date	Oct 19, 2022
Priority date	Jun 24, 2022
Publication date	Dec 28, 2023
Grant date	—

Abstract

A computer-implemented method for state synchronization may include (i) identifying a type of a message from a client device to a server that includes an intended update to content hosted on the server, (ii) determining, based on the type of the message, whether to direct the message to a best-effort publisher-subscriber module or a lossless publisher-subscriber, (iii) directing the message to the best-effort publisher-subscriber module based on the type of the message, (iv) identifying a different type of an additional message from the client device to the server that includes a new intended update to the content, and (v) directing the additional message to the lossless publisher-subscriber module based on the different type of the additional message. Various other methods, systems, and computer-readable media are also disclosed.

First claim

What is claimed is:

1 . A computer-implemented method comprising:
identifying a type of a message from a client device to a server comprising an intended update to content hosted on the server; determining, based on the type of the message, whether to direct the message to a best-effort publisher-subscriber module that processes messages with low latency but does not store the messages to a persistence layer or a lossless publisher-subscriber module that processes the messages with a higher latency but does store the messages to the persistence layer; directing the message to the best-effort publisher-subscriber module based on the type of the message; identifying a different type of an additional message from the client device to the server comprising a new intended update to the content; and directing the additional message to the lossless publisher-subscriber module based on the different type of the additional message.

2 . The computer-implemented method of claim 1 , wherein directing the message to the best-effort publisher-subscriber module based on the type of the message comprises determining that the intended update within the message comprises a portion of a multi-message update that is expected to span multiple additional messages.

3 . The computer-implemented method of claim 2 , further comprising sending complete content of the multi-message update to the lossless publisher-subscriber module in response to determining that the best-effort publisher-subscriber module has received the last message of the multi-message update and is not expecting further additional messages with content for the multi-message update.

4 . The computer-implemented method of claim 1 , wherein directing the additional message to the lossless publisher-subscriber module based on the different type of the additional message comprises determining that the new intended update within the additional message comprises a complete update contained in the additional message that is not expected to span any additional messages.

5 . The computer-implemented method of claim 1 , wherein each step of the method is performed by the client device.

6 . The computer-implemented method of claim 1 , wherein each step of the method is performed by the server.

7 . The computer-implemented method of claim 1 , wherein the content hosted on the server comprises content of a persistent digital multimedia room.

8 . The computer-implemented method of claim 1 , further comprising sending, by the lossless publisher-subscriber module, the additional message to the persistence layer.

9 . A system comprising:
at least one physical processor; physical memory comprising computer-executable instructions that, when executed by the physical processor, cause the physical processor to:
identify a type of a message from a client device to a server comprising an intended update to content hosted on the server;
determine, based on the type of the message, whether to direct the message to a best-effort publisher-subscriber module that processes messages with low latency but does not store the messages to a persistence layer or a lossless publisher-subscriber module that processes the messages with a higher latency but does store the messages to the persistence layer;
direct the message to the best-effort publisher-subscriber module based on the type of the message;
identify a different type of an additional message from the client device to the server comprising a new intended update to the content; and
direct the additional message to the lossless publisher-subscriber module based on the different type of the additional message.

10 . The system of claim 9 , wherein directing the message to the best-effort publisher-subscriber module based on the type of the message comprises determining that the intended update within the message comprises a portion of a multi-message update that is expected to span multiple additional messages.

11 . The system of claim 10 , wherein the computer-executable cause the physical processor to send complete content of the multi-message update to the lossless publisher-subscriber module in response to determining that the best-effort publisher-subscriber module has received the last message of the multi-message update and is not expecting further additional messages with content for the multi-message update.

12 . The system of claim 9 , wherein directing the additional message to the lossless publisher-subscriber module based on the different type of the additional message comprises determining that the new intended update within the additional message comprises a complete update contained in the additional message that is not expected to span any additional messages.

13 . The system of claim 9 , wherein the physical processor is housed on the client device.

14 . The system of claim 9 , wherein the physical processor is housed on the server.

15 . The system of claim 9 , wherein the content hosted on the server comprises content of a persistent digital multimedia room.

16 . The system of claim 9 , wherein the computer-executable cause the physical processor to send, by the loss-less publisher-subscriber module, the additional message to the persistence layer.

17 . A non-transitory computer-readable medium comprising one or more computer-readable instructions that, when executed by at least one processor of a computing device, cause the computing device to:
identify a type of a message from a client device to a server comprising an intended update to content hosted on the server; determine, based on the type of the message, whether to direct the message to a best-effort publisher-subscriber module that processes messages with low latency but does not store the messages to a persistence layer or a lossless publisher-subscriber module that processes the messages with a higher latency but does store the messages to the persistence layer; direct the message to the best-effort publisher-subscriber module based on the type of the message; identify a different type of an additional message from the client device to the server comprising a new intended update to the content; and direct the additional message to the lossless publisher-subscriber module based on the different type of the additional message.

18 . The non-transitory computer-readable medium of claim 17 , wherein directing the message to the best-effort publisher-subscriber module based on the type of the message comprises determining that the intended update within the message comprises a portion of a multi-message update that is expected to span multiple additional messages.

19 . The non-transitory computer-readable medium of claim 18 , wherein the computer-readable cause the computing device to send complete content of the multi-message update to the lossless publisher-subscriber module in response to determining that the best-effort publisher-subscriber module has received the last message of the multi-message update and is not expecting further additional messages with content for the multi-message update.

20 . The non-transitory computer-readable medium of claim 17 , wherein directing the additional message to the lossless publisher-subscriber module based on the different type of the additional message comprises determining that the new intended update within the additional message comprises a complete update contained in the additional message that is not expected to span any additional messages.

Assignees

• Meta Platforms Inc

Inventors

• Jazayeri Vahid
• Malkani Zahan Jagdish
• Tang Brian Laphun
• Nguyen Tuan
• Huettl Ryan Edward
• Lin Yonghua
• Dimri Ritu
• Khomchenko Oleksii
• Ghodasara Dharaben
• Feiereisel Evan
• Pyla Rama Praveen
• Srikanth Abhishek
• Zhu Kancheng

Classifications

• H04L51/226 Primary

  Delivery according to priorities · CPC title

• H04L12/1859 Primary

  adapted to provide push services, e.g. data channels · CPC title

• H04L12/1827

  Network arrangements for conference optimisation or adaptation · CPC title