Method and system for delivering object update messages including payloads

• US 8,667,057 B1
• Filed: 09/30/2011
• Issued: 03/04/2014
• Est. Priority Date: 10/01/2010
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Adya, Atul, Myers, Daniel Sumers, Cooper, Gregory H., Piatek, Michael
• Primary Examiner(s): Dalencourt, Yves
• Application Number:
  US13/251,017
• Time in Patent Office: 886 Days
• Field of Search: 709/203, 709/219
• US Class Current: 709/203
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 67/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 67/5683 Storage of data provided by user terminals, i.e. reverse caching

Abstract

A distributed network system includes at least one server and one client device, each having memory and one or more processors. The server performs the following operations: selecting a first client-object registration record including a first client identifier and a first object identifier; retrieving a pair of server-side object version and client-side object version from the first client-object registration record; determining a first set of incremental payloads to be delivered to the client device associated with the first client identifier in accordance with the pair of server-side object version and client-side object version; retrieving the first set of incremental payloads from a first object update record including the first object identifier; and sending a first object update message to the first client device, wherein the first object update message includes the first object identifier, the server-side object version and the retrieved first set of incremental payloads.

Claims

1. A computer-implemented method, comprising:

at a server having memory and one or more processors, wherein the server has access to, respectively, a plurality of client-object registration records, each record including a client identifier, an object identifier, and a pair of server-side object version and client-side object version associated with the object identifier, and a plurality of object update records, each record including an object identifier and a plurality of incremental payloads, each incremental payload corresponding to a respective object version;

selecting a first client-object registration record including a first client identifier and a first object identifier;

retrieving a pair of server-side object version and client-side object version from the first client-object registration record;

determining a first set of incremental payloads to be delivered to a first client device associated with the first client identifier in accordance with the pair of server-side object version and client-side object version;

retrieving the first set of incremental payloads from a first object update record including the first object identifier; and

sending a first object update message to the first client device, wherein the first object update message includes the first object identifier, the server-side object version and the retrieved first set of incremental payloads.

2. The method of claim 1, further comprising:

receiving an object update confirmation message from the first client device; and

updating the first client-object registration record using the received object update confirmation message.

3. The method of claim 2, wherein the first client-object registration record is updated so that the client-side version is the same as the server-side version.

4. The method of claim 2, further comprising:

repeating an attempt of sending the first object update message to the first client device if no object update confirmation message is returned from the first client device until after a predefined number of attempts; and

updating the first client-object registration record to stop sending object update messages to the first client device.

5. The method of claim 1, wherein the first client-object registration record includes a payload filter and determining the first set of incremental payloads includes applying the payload filter to each incremental payload so that the determined set includes incremental payloads that satisfy the payload filter.

6. The method of claim 1, further comprising:

after retrieving the first set of incremental payloads,

combining the retrieved first set of incremental payloads into a merged incremental payload in accordance with their respective object versions; and

sending the merged incremental payload as a member of the first object update message to the first client device.

7. The method of claim 1, further comprising:

after retrieving the first set of incremental payloads,

determining whether the retrieved first set of incremental payloads has missed any incremental payload whose object version is between the pair of server-side object version and client-side object version; and

sending the first object update message excluding any of the first set of incremental payloads to the first client device if there is at least one missed incremental payload.

8. The method of claim 1, wherein one or more of the plurality of incremental payloads are stored in an in-memory data structure of the server, further comprising:

before retrieving the first set of incremental payloads from the first object update record;

retrieving a first subset of the first set of incremental payloads from the in-memory data structure if the first subset is found in the in-memory data structure; and

retrieving a second subset of the first set of incremental payloads from the first object update record if the second subset is not found in the in-memory data structure.

9. The method of claim 1, further comprising:

before selecting the first client-object registration record,

receiving an object update message from a server-side application, wherein the object update message includes the first object identifier, a latest object version, and a first incremental payload;

updating the first object update record using the latest object version and the first incremental payload;

propagating the update to the first object update record to the first client-object registration record by setting the server-side object version to be the latest object version.

10. The method of claim 9, further comprising:

after updating the first object update record, sending an object update confirmation message to the server-side application.

11. The method of claim 9, wherein the first object update record is not updated in response to the object update message if the object'"'"'s version information in the first object update record is more recent than the latest object version.

12. The method of claim 1, further comprising:

receiving a request for object updates from a second client device, wherein the request includes the first object identifier, the object'"'"'s version at the second client device, and a second client identifier;

determining a second set of incremental payloads to be delivered to the second client device in accordance with the server-side object version and the object'"'"'s version at the second client device;

retrieving the second set of incremental payloads from the first object update record; and

sending a second object update message to the second client device, wherein the second object update message includes the first object identifier, the server-side object version and the retrieved second set of incremental payloads.

13. The method of claim 1, wherein the first object identifier corresponds to one selected from the group consisting of a web-based calendar, a browser bookmark, an address book, and a set of email messages associated with a user.

14. The method of claim 1, wherein the first client device corresponds to one selected from the group consisting of a desktop, a laptop, a tablet, a smartphone, and a netbook.

15. A server system, wherein the server system has access to, respectively, a plurality of client-object registration records, each record including a client identifier, an object identifier, and a pair of server-side object version and client-side object version associated with the object identifier, and a plurality of object update records, each record including an object identifier and a plurality of incremental payloads, each incremental payload corresponding to a respective object version, comprising:

one or more processors for executing programs; and

memory to store data and to store one or more programs to be executed by the one or more processors, the one or more programs including instructions for;

selecting a first client-object registration record including a first client identifier and a first object identifier;

retrieving a pair of server-side object version and client-side object version from the first client-object registration record;

determining a first set of incremental payloads to be delivered to a first client device associated with the first client identifier in accordance with the pair of server-side object version and client-side object version;

retrieving the first set of incremental payloads from a first object update record including the first object identifier; and

sending a first object update message to the first client device, wherein the first object update message includes the first object identifier, the server-side object version and the retrieved first set of incremental payloads.

16. A non-transitory computer readable-storage medium storing one or more programs for execution by one or more processors of a server system, wherein the server system has access to, respectively, a plurality of client-object registration records, each record including a client identifier, an object identifier, and a pair of server-side object version and client-side object version associated with the object identifier, and a plurality of object update records, each record including an object identifier and a plurality of incremental payloads, each incremental payload corresponding to a respective object version, the one or more programs comprising instructions for:

selecting a first client-object registration record including a first client identifier and a first object identifier;

retrieving a pair of server-side object version and client-side object version from the first client-object registration record;

determining a first set of incremental payloads to be delivered to a first client device associated with the first client identifier in accordance with the pair of server-side object version and client-side object version;

retrieving the first set of incremental payloads from a first object update record including the first object identifier; and

sending a first object update message to the first client device, wherein the first object update message includes the first object identifier, the server-side object version and the retrieved first set of incremental payloads.