Conflict management during data object synchronization between client and server

• US 9,131,024 B2
• Filed: 09/14/2012
• Issued: 09/08/2015
• Est. Priority Date: 12/30/2005
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Braginsky, David E., Rosenstein, Justin M., Uhrhane, Eric Joseph, Jeske, David
• Primary Examiner(s): Rostami, Mohammad S
• Application Number:
  US13/617,045
• Publication Number:
  US 20130124612A1
• Time in Patent Office: 1,089 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 server stores server metadata entries corresponding to data objects, each server metadata entry including a server file name and an identifier, distinct from the server file name, for a respective data object. The server receives client metadata entries from a client, each client metadata entry corresponding to a data object for which at least one metadata parameter has changed since a prior execution of a synchronization process. Each client metadata entry includes a client file name and an identifier, distinct from the client file name, for a respective data object corresponding to the client metadata entry. The server synchronizes the received client metadata entries with corresponding server metadata entries, if any, having identifiers that match said identifiers in the received client metadata entries, without regard to whether the corresponding server metadata entries include server file names that match the client file names in the received client metadata entries.

Claims

1. A method for synchronizing data objects, comprising:

at a computing device,

obtaining a first metadata entry associated with a first data object, the first metadata entry including;

(i) a first file name, wherein the first file name includes a directory path for the first data object; and

(ii) a first data object identifier distinct from the first file name;

obtaining a second metadata entry associated with a second data object, the second metadata entry including;

(i) a second file name, wherein the second file name includes a directory path for the second data object; and

(ii) a second data object identifier distinct from the second file name;

determining, using the first and second data object identifiers, whether the first data object and the second data object correspond to the same data object;

without regard to the first file name and the second file name; and

in accordance with a determination that the first data object and the second data object correspond to the same data object;

synchronizing the first data object with the second data object, including;

determining whether a third data object with a directory path matching the first directory path exists, wherein the third data object is stored on a computing devices different from a computing device on which the first data object is stored; and

in accordance with a determination that the third data object exists;

performing a conflict resolution action; and

in accordance with a determination that the third data object does not exist;

performing one or more synchronization operations on the first data object or the second data object.

2. The method of claim 1, wherein synchronizing the first data object with the second data object includes:

determining whether a conflict exists between the first data object and the second object; and

performing a conflict resolution action, in accordance with a determination that a conflict exists between the first data object and the second data object.

3. The method of claim 1, wherein the first data object is stored on a server;

and the second data object is stored on a client device.

4. The method of claim 1, wherein the first data object is stored on a first client device;

and the second data object is stored on a second client device distinct from the first client device.

5. The method of claim 1, wherein the first data object and the second data object correspond to different versions of the same data object.

6. A computer system, comprising:

one or more processors;

memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for;

obtaining a first metadata entry associated with a first data object, the first metadata entry including;

(i) a first file name, wherein the first file name includes a directory path for the first data object; and

(ii) a first data object identifier distinct from the first file name;

obtaining a second metadata entry associated with a second data object, the second metadata entry including;

(i) a second file name, wherein the second file name includes a directory path for the second data object; and

(ii) a second data object identifier distinct from the second file name;

determining, using the first and second data object identifiers, whether the first data object and the second data object correspond to the same data object, without regard to the first file name and the second file name; and

in accordance with a determination that the first data object and the second data object correspond to the same data object;

synchronizing the first data object with the second data object, including;

determining whether a third data object with a directory path matching the first directory path exists, wherein the third data object is stored on a computing device different from a computing device on which the first data object is stored; and

in accordance with a determination that the third data object exists;

 

performing a conflict resolution action; and

in accordance with a determination that the third data object does not exist;

 

performing one or more synchronization operations on the first data object or the second data object.

7. The system of claim 6, wherein the instructions for synchronizing the first data object with the second data object include instructions for:

determining whether a conflict exists between the first data object and the second object; and

performing a conflict resolution action, in accordance with a determination that a conflict exists between the first data object and the second data object.

8. The system of claim 6, wherein the first data object is stored on a server;

and the second data object is stored on a client device.

9. The system of claim 6, wherein the first data object is stored on a first client device;

and the second data object is stored on a second client device distinct from the first client device.

10. The system of claim 6, wherein the first data object and the second data object correspond to different versions of the same data object.

11. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computer system with one or more processors, cause the computer system to:

obtain a first metadata entry associated with a first data object, the first metadata entry including;

(i) a first file name, wherein the first file name includes a directory path for the first data object; and

(ii) a first data object identifier distinct from the first file name;

obtain a second metadata entry associated with a second data object, the second metadata entry including;

(i) a second file name, wherein the second file name includes a directory path for the second data object; and

(ii) a second data object identifier distinct from the second file name;

determine, using the first and second data object identifiers, whether the first data object and the second data object correspond to the same data object, without regard to the first file name and the second file name; and

in accordance with a determination that the first data object and the second data object correspond to the same data object;

synchronize the first data object with the second data object, including;

determine whether a third data object with a directory path matching the first directory path exists, wherein the third data object is stored on a computing device different from a computing device on which the first data object is stored; and

in accordance with a determination that the third data object exists;

perform a conflict resolution action; and

in accordance with a determination that the third data object does not exist;

perform one or more synchronization operations on the first data object or the second data object.

12. The non-transitory computer readable storage medium of claim 11, wherein the first data object is stored on a server;

and the second data object is stored on a client device.

13. The non-transitory computer readable storage medium of claim 11, wherein the first data object is stored on a first client device;

and the second data object is stored on a second client device distinct from the first client device.

14. The non-transitory computer readable storage medium of claim 11, wherein the first data object and the second data object correspond to different versions of the same data object.