Conflict Management During Data Object Synchronization Between Client and Server

• US 20090216815A1
• Filed: 05/04/2009
• Published: 08/27/2009
• Est. Priority Date: 12/30/2005
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: David E. Braginsky, David Jeske, Eric Joseph Uhrhane, Justin M. Rosenstein
• Inventors: Rosenstein, Justin M., Braginsky, David E., Uhrhane, Eric Joseph, Jeske, David
• Granted Patent: US 8,311,981 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1787 Details of non-transparently synchronising file systems
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A client stores client metadata entries corresponding to a plurality of data objects. During a first phase of a synchronization process, the client sends one or more client metadata entries to a server. Each client metadata entry sent corresponds to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process. During a second phase of the synchronization process, the client receives from the server one or more server metadata entries, each having at least one parameter that has changed since a prior execution of the synchronization process. The client identifies any received server metadata entry that conflicts with a corresponding client metadata entry, requests a user to select from among a predefined set of conflict resolutions to resolve the conflict, and the performs an action in accordance with the conflict resolution selected by the user.

Claims

1. A computer implemented method for synchronizing data objects stored on a server and a client, comprising:

at the server, storing server metadata entries corresponding to a plurality of data objects, wherein each server metadata entry associates both an identifier and a server file name, distinct from the identifier, with a respective data object, the server file name including a directory path;

at the server;

during a first phase of a synchronization process, receiving one or more client metadata entries from the client, each of the client metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process, wherein each client metadata entry associates both an identifier and a client file name, distinct from the identifier, with a respective data object, the client file name including a directory path;

during the first phase of the synchronization process, rejecting any received client metadata entry that contains one or more updated metadata parameters that conflict with metadata parameters of a corresponding server metadata entry, and accepting any received client metadata entry that does not conflict with a corresponding server metadata entry, wherein a server metadata entry corresponds to a received client metadata entry when the received client metadata entry contains a same identifier as the server metadata entry without regard to whether the server file name and client file name of the server metadata entry and client metadata entry match; and

during a second phase of the synchronization process, sending to the client one or more server metadata entries, each of the server metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process;

wherein, when a client metadata entry has been rejected at the server during the first phase, the one or more server metadata entries sent to the client include at least one server metadata entry that conflicts with the rejected client metadata entry.

2. The method of claim 1, including, at the server, during the first phase of the synchronization process, accepting any received client metadata entry for which the server does not have a corresponding server metadata entry.

3. The method of claim 1, including, at the server, during the first phase of the synchronization process, rejecting any received client metadata entry that specifies a file path for a respective data object that matches the file path specified in a server metadata entry having a different identifier than the received client metadata entry.

4. The method of claim 1, including, at the server, during a subsequent phase of the synchronization process, performing a content update operation comprising at least one of a content upload operation and a content download operation.

5. The method of claim 4, wherein the content upload operation comprises uploading to the client one or more server content updates, each of the server content updates corresponding to a data object for which at least one content parameter has changed since a prior execution of the synchronization process;

wherein the one or more server content updates uploaded to the client are associated with the one or more server metadata entries sent to the client during the second phase of the synchronization process.

6. The method of claim 4, wherein the content download operation comprises downloading from the client one or more client content updates, each of the client content updates corresponding to a data object for which at least one content parameter has changed since a prior execution of the synchronization process;

wherein the one or more client content updates downloaded from the client are associated with the one or more client metadata entries received from the client during the first phase of the synchronization process.

7. The method of claim 1, wherein the server receives the one or more client metadata entries from the client via a wide area network.

8. The method of claim 1, wherein the server metadata entries comprises data selected from a group consisting of a data object identifier, an identifier of a parent of said data object, a version number, a data object name, a size of said data object, a size of said data object when encrypted, a checksum, a date and time when the data object was last modified, a date and time when the data object was created, attributes of said data object, flags related to said data object, an indicator of whether said data object is available locally, an indicator of whether said server has data for the data object, and a timestamp of when the data object was last changed on said server.

9. A computer implemented method for synchronizing data objects stored on a server and a client, comprising:

at the client, storing client metadata entries corresponding to a plurality of data objects, wherein each client metadata entry associates both an identifier and a client file name, distinct from the identifier, with a respective data object, the client file name including a directory path;

at the client;

during a first phase of a synchronization process, sending one or more client metadata entries to the server, each of the client metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process;

during a second phase of the synchronization process, receiving from the server one or more server metadata entries, each of the server metadata entries corresponding to a data object for which at least one metadata parameter has changed in the server metadata entry since a prior execution of the synchronization process, wherein each server metadata entry associates both an identifier and a server file name, distinct from the identifier, with a respective data object, the server file name including a directory path;

wherein, when a client metadata entry has been rejected at the server during the first phase, the one or more server metadata entries sent to the client include at least one server metadata entry that conflicts with rejected client metadata entry;

during the second phase of the synchronization process, identifying any received server metadata entry that contains one or more updated metadata parameters that conflict with metadata parameters of a corresponding client metadata entry, requesting a user to select from among a predefined set of conflict resolutions to resolve the conflict, performing an action in accordance with the conflict resolution selected by the user, and accepting any received server metadata entry that does not conflict with a corresponding server metadata entry, wherein a client metadata entry corresponds to a received server metadata entry when the received server metadata entry contains a same identifier as the client metadata entry without regard to whether the server file name and client file name of the server metadata entry and client metadata entry match.

10. The method of claim 9, wherein performing an action in accordance with the conflict resolution selected by the user comprises updating one or more client metadata entries in accordance with the user selected conflict resolution.

11. The method of claim 9, including, at the client, during the second phase of the synchronization process, accepting any received server metadata entry for which the client does not have a corresponding client metadata entry.

12. The method of claim 9, including, at the client, during the second phase of the synchronization process, responding to any received server metadata entry that specifies a file path for a respective data object that matches the file path specified in a client metadata entry having a different identifier than the received server metadata entry by requesting a user to select from among the predefined set of conflict resolutions to resolve the conflict, and updating one or more client metadata entries in accordance with the user selected conflict resolution.

13. The method of claim 9, including, at the client, during a subsequent phase of the synchronization process, performing a content update operation comprising at least one of a content upload operation and a content download operation.

14. The method of claim 13, wherein the content upload operation comprises uploading to the server one or more client content updates, each of the client content updates corresponding to a data object for which at least one content parameter has changed since a prior execution of the synchronization process;

wherein the one or more client content updates uploaded to the server are associated with the one or more client metadata entries sent to the server during the first phase of the synchronization process.

15. The method of claim 13, wherein the content download operation comprises downloading from the server one or more server content updates, each of the server content updates corresponding to a data object for which at least one content parameter has changed since a prior execution of the synchronization process;

wherein the one or more server content updates downloaded from the server are associated with the one or more server metadata entries received from the server during the second phase of the synchronization process.

16. The method of claim 9, wherein the client receives the one or more server metadata entries from the server via a wide area network.

17. The method of claim 9, wherein the server metadata entries comprises data selected from a group consisting of a data object identifier, an identifier of a parent of said data object, a version number, a data object name, a size of said data object, a size of said data object when encrypted, a checksum, a date and time when the data object was last modified, a date and time when the data object was created, attributes of said data object, flags related to said data object, an indicator of whether said data object is available locally, an indicator of whether said server has data for the data object, and a timestamp of when the data object was last changed on said server.

18. The method of claim 9, wherein performing an action in accordance with the conflict resolution selected by the user comprises performing an action selected from a group consisting of:

modifying a client metadata entry so as to discard a corresponding data object stored in the client, modifying a client metadata entry so as to overwrite a corresponding data object stored in the server with a client data object identified by the client metadata entry, renaming a data object stored in the client, moving a data object stored in the client, and copying a data object stored in the client.

19. A computer program product for synchronizing data objects stored on a server and a client, the computer program product comprising a computer readable storage and a computer program stored therein, the computer program comprising instructions for:

storing, at the server, server metadata entries corresponding to a plurality of data objects, wherein each server metadata entry associates both an identifier and a server file name, distinct from the identifier, with a respective data object, the server file name including a directory path;

during a first phase of a synchronization process, receiving, at the server, one or more client metadata entries from the client, each of the client metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process, wherein each client metadata entry associates both an identifier and a client file name, distinct from the identifier, with a respective data object, the client file name including a directory path;

during the first phase of the synchronization process, at the server, rejecting any received client metadata entry that contains one or more updated metadata parameters that conflicts with metadata parameters of a corresponding server metadata entry, and accepting any received client metadata entry that does not conflict with a corresponding server metadata entry, wherein a server metadata entry corresponds to a received client metadata entry when the received client metadata entry contains a same identifier as the server metadata entry without regard to whether the server file name and client file name of the server metadata entry and client metadata entry match;

during a second phase of the synchronization process, at the server, sending to the client one or more server metadata entries, each of the server metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process;

wherein, when a client metadata entry has been rejected at the server during the first phase, the one or more server metadata entries sent to the client include at least one server metadata entry that conflicts with rejected client metadata entry.

20. A computer program product for synchronizing data objects stored on a server and a client, the computer program product comprising a computer readable storage and a computer program stored therein, the computer program comprising instructions for:

storing, at the client, client metadata entries corresponding to a plurality of data objects, wherein each client metadata entry associates both an identifier and a client file name, distinct from the identifier, with a respective data object, the client file name including a directory path;

during a first phase of a synchronization process, sending, from the client, one or more client metadata entries from the client to the server, each of the client metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process;

during a second phase of the synchronization process, receiving at the client from the server one or more server metadata entries, each of the server metadata entries corresponding to a data object for which at least one metadata parameter has changed in the server metadata entry since a prior execution of the synchronization process, wherein each server metadata entry associates both an identifier and a server file name, distinct from the identifier, with a respective data object, the server file name including a directory path;

wherein, when a client metadata entry has been rejected at the server during the first phase, the one or more server metadata entries sent to the client include at least one server metadata entry that conflicts with rejected client metadata entry;

during the second phase of the synchronization process, at the client, identifying any received server metadata entry that contains one or more updated metadata parameters that conflicts with metadata parameters of a corresponding client metadata entry, requesting a user to select from among a predefined set of conflict resolutions to resolve the conflict, performing an action in accordance with the conflict resolution selected by the user, and accepting any received server metadata entry that does not conflict with a corresponding server metadata entry, wherein a client metadata entry corresponds to a received server metadata entry when the received server metadata entry contains a same identifier as the client metadata entry without regard to whether the server file name and client file name of the server metadata entry and client metadata entry match.

21. A data objects synchronization system, comprising:

one or more processors;

memory; and

one or more programs stored in the memory, the one or more programs comprising;

instructions to store, at a server, server metadata entries corresponding to a plurality of data objects, wherein each server metadata entry associates both an identifier and a server file name, distinct from the identifier, with a respective data object, the server file name including a directory path;

instructions, to be executed during a first phase of a synchronization process, to receive at the server one or more client metadata entries from a client, each of the client metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process, wherein each client metadata entry associates both an identifier and a client file name, distinct from the identifier, with a respective data object, the client file name including a directory path;

instructions, to be executed during the first phase of the synchronization process, to reject at the server any received client metadata entry that contains one or more updated metadata parameters that conflicts with metadata parameters of a corresponding server metadata entry, and accepting any received client metadata entry that does not conflict a corresponding server metadata entry, wherein a server metadata entry corresponds to a received client metadata entry when the received client metadata entry contains a same identifier as the server metadata entry without regard to whether the server file name and client file name of the server metadata entry and client metadata entry match;

instructions, to be executed during a second phase of the synchronization process, to send from the server to the client one or more server metadata entries, each of the server metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process;

wherein, when a client metadata entry has been rejected at the server during the first phase, the one or more server metadata entries sent to the client include at least one server metadata entry that conflicts with rejected client metadata entry.

22. A data objects synchronization system, comprising:

one or more processors;

memory; and

one or more programs stored in the memory, the one or more programs comprising;

instructions to store, at a client, client metadata entries corresponding to a plurality of data objects, wherein each client metadata entry associates both an identifier and a client file name, distinct from the identifier, with a respective data object, the client file name including a directory path;

instructions, to be executed during a first phase of a synchronization process, to send, from the client, one or more client metadata entries from the client to a server, each of the client metadata entries corresponding to a data object for which at least one metadata parameter has changed since a prior execution of the synchronization process;

instructions, to be executed during a second phase of the synchronization process, to receive at the client from the server one or more server metadata entries, each of the server metadata entries corresponding to a data object for which at least one metadata parameter has changed in the server metadata entry since a prior execution of the synchronization process, wherein each server metadata entry associates both an identifier and a server file name, distinct from the identifier, with a respective data object, the server file name including a directory path;

wherein, when a client metadata entry has been rejected at the server during the first phase, the one or more server metadata entries sent to the client include at least one server metadata entry that conflicts with rejected client metadata entry;

instructions, to be executed during the second phase of the synchronization process, to identify at the client any received server metadata entry that contains one or more updated metadata parameters that conflicts with metadata parameters of a corresponding client metadata entry, requesting a user to select from among a predefined set of conflict resolutions to resolve the conflict, performing an action in accordance with the conflict resolution selected by the user, and accepting any received server metadata entry that does not conflict a corresponding server metadata entry, wherein a client metadata entry corresponds to a received server metadata entry when the received server metadata entry contains a same identifier as the client metadata entry without regard to whether the server file name and client file name of the server metadata entry and client metadata entry match.