SYSTEM AND METHOD FOR SIGNALING THROUGH DATA STORAGE

• US 20200137147A1
• Filed: 12/30/2019
• Published: 04/30/2020
• Est. Priority Date: 05/14/2015
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Olivier, Carl, Zolotarjov, Sergei, Velenko, Mihails, Liik, Devid, Tyazhelov, Artyom
• Granted Patent: US 11,265,367 B2
• Time in Patent Office: Days
• 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
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

An application platform system and method. A data synchronization instance manages a reference state object for a data synchronization system (DSS) account. A first local state object is stored at a first application system. The first application system receives update notifications provided by the DSS. A second local state object is stored at a second application system. The second application system receives update notifications provided by the DSS. An application instruction of the first application system is transformed into a state update, and the first local state object is modified to include the state update. The state update is provided to the DSS via a local update notification. The reference state object is modified to include the state update. The state update is provided to the second application system via a reference update notification. The second local state object is modified to include the state update.

Claims

1. A method comprising:

receiving, by a multi-tenant data synchronization system (DSS), a first Application Programming Interface (API) state update from a first client device, the first API state update being to update an API reference state object maintained by the multi-tenant DSS, the API reference state object being associated with a first application;

updating the API reference state object based on the first API state update;

transmitting, to an application server system associated with the first application, a first server state update to be performed to a server API state object maintained by the application server system, the first server state update including the first API state update.

2. The method of claim 1, wherein the first application facilitates chat communications and the first API state update indicates a modification made to an active chat communication on the first client device.

3. The method of claim 2, wherein the first client device maintains a first local state representation object corresponding to the active chat communication and the first API state update indicates an update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

4. The method of claim 3, wherein the application server system associated with the first application transmits a second API state update to a second client device engaged in the active chat communication with the first client device, the second API state update indicating the update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

5. The method of claim 3, wherein the second client device updates a second local state representation object corresponding to the active chat communication that is maintained by the second client device.

6. The method of claim 3, further comprising:

transmitting a second API state update to a second client device engaged in the active chat communication with the first client device, the second API state update indicating the update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

7. The method of claim 6, further comprising:

receiving, from the second client device, a third API state update to update the API reference state object maintained by the multi-tenant DSS, the third API state update indicating a modification made to the active chat communication on the second client device;

updating the API reference state object based on the second API state update;

transmitting, to the application server system, a second server state update to be performed to the server API state object maintained by the application server system, the second server state update including the second API state update; and

transmitting a fourth API state update to the first client device, the fourth API state update indicating the modification made to the active chat communication on the second client device.

8. A multi-tenant data synchronization system (DSS) comprising:

one or more computer processors; and

one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the multi-tenant DSS to perform operations comprising;

receiving a first Application Programming Interface (API) state update from a first client device, the first API state update being to update an API reference state object maintained by the multi-tenant DSS, the API reference state object being associated with a first application;

updating the API reference state object based on the first API state update;

transmitting, to an application server system associated with the first application, a first server state update to be performed to a server API state object maintained by the application server system, the first server state update including the first API state update.

9. The multi-tenant DSS of claim 8, wherein the first application facilitates chat communications and the first API state update indicates a modification made to an active chat communication on the first client device.

10. The multi-tenant DSS of claim 9, wherein the first client device maintains a first local state representation object corresponding to the active chat communication and the first API state update indicates an update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

11. The multi-tenant DSS of claim 10, wherein the application server system associated with the first application transmits a second API state update to a second client device engaged in the active chat communication with the first client device, the second API state update indicating the update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

12. The multi-tenant DSS of claim 10, wherein the second client device updates a second local state representation object corresponding to the active chat communication that is maintained by the second client device.

13. The multi-tenant DSS of claim 10, the operations further comprising:

transmitting a second API state update to a second client device engaged in the active chat communication with the first client device, the second API state update indicating the update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

14. The multi-tenant DSS of claim 13, the operations further comprising:

receiving, from the second client device, a third API state update to update the API reference state object maintained by the multi-tenant DSS, the third API state update indicating a modification made to the active chat communication on the second client device;

updating the API reference state object based on the second API state update;

transmitting, to the application server system, a second server state update to be performed to the server API state object maintained by the application server system, the second server state update including the second API state update; and

transmitting a fourth API state update to the first client device, the fourth API state update indicating the modification made to the active chat communication on the second client device.

15. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of a multi-tenant data synchronization system (DSS), cause the multi-tenant DSS to perform operations comprising:

receiving a first Application Programming Interface (API) state update from a first client device, the first API state update being to update an API reference state object maintained by the multi-tenant DSS, the API reference state object being associated with a first application;

updating the API reference state object based on the first API state update;

transmitting, to an application server system associated with the first application, a first server state update to be performed to a server API state object maintained by the application server system, the first server state update including the first API state update.

16. The non-transitory computer-readable medium of claim 15, wherein the first application facilitates chat communications and the first API state update indicates a modification made to an active chat communication on the first client device.

17. The non-transitory computer-readable medium of claim 16, wherein the first client device maintains a first local state representation object corresponding to the active chat communication and the first API state update indicates an update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

18. The non-transitory computer-readable medium of claim 17, wherein the application server system associated with the first application transmits a second API state update to a second client device engaged in the active chat communication with the first client device, the second API state update indicating the update to the first local state representation object made based on the modification made to the active chat communication on the first client device.

19. The non-transitory computer-readable medium of claim 17, wherein the second client device updates a second local state representation object corresponding to the active chat communication that is maintained by the second client device.

20. The non-transitory computer-readable medium of claim 17, the operations further comprising:

transmitting a second API state update to a second client device engaged in the active chat communication with the first client device, the second API state update indicating the update to the first local state representation object made based on the modification made to the active chat communication on the first client device.