Content management client synchronization service

• US 10,324,903 B1
• Filed: 01/11/2018
• Issued: 06/18/2019
• Est. Priority Date: 12/28/2017
• Status: Active Grant

• Current Assignee: Dropbox, Inc.
• Original Assignee: Dropbox, Inc.
• Inventors: Goldberg, Isaac, Jubb, IV, Elmer Charles, Jayakar, Sujay, Lai, John, Ying, Robert, Koorapati, Nipunn, Gupta, Gautam, Song, Geoffry
• Primary Examiner(s): Morrison, Jay A
• Application Number:
  US15/868,518
• Publication Number:
  US 20190205428A1
• Time in Patent Office: 523 Days
• CPC Class Codes: G06F 1/04 Generating or distributing clock signals or signals derived directly therefrom
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 12/1466 Key-lock mechanism
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/116 Details of conversion of file system types or formats
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/125 characterised by the use of retention policies retention policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/137 Hash-based content-based indexing of textual data G06F16/31
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/152 using file content signatures, e.g. hash values
• CPC Class Codes: G06F 16/156 Query results presentation
• CPC Class Codes: G06F 16/16 File or folder operations, e.g. details of user interfaces specifically adapted to file systems
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/168 Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs query results presentation G06F16/156
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/1744 : using compression, e.g. sparse files
• CPC Class Codes: G06F 16/176 : Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/1767 : Concurrency control, e.g. optimistic or pessimistic approaches
• CPC Class Codes: G06F 16/178 : Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/1787 : Details of non-transparently synchronising file systems
• CPC Class Codes: G06F 16/18 : File system types
• CPC Class Codes: G06F 16/182 : Distributed file systems
• CPC Class Codes: G06F 16/1827 : Management specifically adapted to NAS management of storage area networks [SAN] G06F3/067
• CPC Class Codes: G06F 16/183 : Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 16/184 : implemented as replicated file system
• CPC Class Codes: G06F 16/1844 : Management specifically adapted to replicated file systems
• CPC Class Codes: G06F 16/185 : Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof details of archiving G06F16/11
• CPC Class Codes: G06F 16/2246 : Trees, e.g. B+trees
• CPC Class Codes: G06F 16/2255 : Hash tables
• CPC Class Codes: G06F 16/2322 : using timestamps
• CPC Class Codes: G06F 16/2358 : Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 : Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 : Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/24552 : Database cache management
• CPC Class Codes: G06F 16/27 : Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 : Synchronous replication
• CPC Class Codes: G06F 16/9027 : Trees
• CPC Class Codes: G06F 16/907 : Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/951 : Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/955 : using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 16/958 : Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 21/10 : Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/604 : Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6218 : to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2201/84 : Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 2212/1052 : Security improvement
• CPC Class Codes: G06F 2221/2141 : Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 3/0619 : in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0623 : in relation to content
• CPC Class Codes: G06F 3/0629 : Configuration or reconfiguration of storage systems
• CPC Class Codes: G06F 3/065 : Replication mechanisms
• CPC Class Codes: G06F 3/0652 : Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
• CPC Class Codes: G06F 3/067 : Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 9/547 : Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0853 : using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 : Access control lists [ACL]
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 : for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 9/3213 : using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3247 : involving digital signatures

Abstract

The disclosed technology relates to a system configured to obtain a set of tree data structures including a remote tree representing a server state of content items associated with a user account on a content management system, a local tree representing a file system state of content items associated with the user account on a client device, and a sync tree representing a known sync state between the content management system and the client device. The system is configured to determine that the user account on the content management system includes at least one modification not synchronized to the client device by comparing the remote tree and the sync tree.

Claims

1. A computer-implemented method for synchronizing content items between a user account on a content management system and a client device authorized to access the user account, the method comprising:

obtaining a set of tree data structures including

a remote tree representing a server state of content items associated with the user account on the content management system during a current time period,

a local tree representing a file system state of content items associated with the user account on the client device during the current time period, and

a sync tree representing a known sync state during a previous time period where the sync tree, the local tree, and the remote tree were identical, wherein the sync tree includes representations of content items that, during the previous time period, were included in both the local tree and the remote tree;

determining that the user account on the content management system includes at least one modification not synchronized to the client device by comparing the remote tree and the sync tree; and

determining that the client device includes at least one modification not synchronized to the content management system by comparing the sync tree and the local tree.

2. The computer-implemented method of claim 1, wherein the set of tree data structures is stored on the client device.

3. The computer-implemented method of claim 1, wherein the determining that the user account on the content management system includes at least one modification not synchronized to the client device comprises generating a set of operations.

4. The computer-implemented method of claim 3, wherein the set of operations is configured to operate on the content items stored on the client device to converge the server state and the file system state.

5. The computer-implemented method of claim 1, wherein the determining that the client device includes at least one modification not synchronized to the content management system comprises generating a set of operations.

6. The computer-implemented method of claim 5, wherein the set of operations is configured to operate on the content items stored by the content management system to converge the server state and the file system state.

7. The computer-implemented method of claim 1, further comprising:

receiving client modification data for content items stored on the client device; and

updating, based on the client modification data, the local tree.

8. The computer-implemented method of claim 7, further comprising updating, based on the client modification data, the sync tree.

9. The computer-implemented method of claim 1, further comprising:

receiving, from the content management system, server modification data for content items stored by the content management system; and

updating, based on the server modification data, the remote tree.

10. The computer-implemented method of claim 9, further comprising updating, based on the server modification data, the sync tree.

11. A non-transitory computer readable medium comprising instructions, the instructions, when executed by a computing system, cause the computing system to:

obtain a set of tree data structures including

a remote tree representing a server state of content items associated with a user account on a content management system during a current time period,

a local tree representing a file system state of content items associated with the user account on a client device during the current time period, and

a sync tree representing a known sync state during a previous time period where the sync tree, the local tree, and the remote tree were identical, wherein the sync tree includes representations of content items that, during the previous time period, were included in both the local tree and the remote tree; and

determine that the user account on the content management system includes at least one modification not synchronized to the client device by comparing the remote tree and the sync tree.

12. The non-transitory computer readable medium of claim 11, wherein instructions further cause the computing system to generate a set of operations configured to operate on the content items stored on the client device to converge the server state and the file system state.

13. The non-transitory computer readable medium of claim 11, wherein instructions further cause the computing system to determine that the client device includes at least one modification not synchronized to the content management system by comparing the sync tree and the local tree.

14. The non-transitory computer readable medium of claim 13, wherein instructions further cause the computing system to generate a set of operations configured to operate on the content items stored by the content management system to converge the server state and the file system state.

15. The non-transitory computer readable medium of claim 11, wherein the set of tree data structures is stored on the client device.

16. A system comprising:

a processor; and

a non-transitory computer-readable medium storing instructions that, when executed by the processor, cause the processor to;

obtain a set of tree data structures including

a remote tree representing a server state of content items associated with a user account on a content management system during a current time period,

a local tree representing a file system state of content items associated with the user account on a client device during the current time period, and

a sync tree representing a known sync state during a previous time period where the sync tree, the local tree, and the remote tree were identical, wherein the sync tree includes representations of content items that, during the previous time period, were included in both the local tree and the remote tree; and

determine that the client device includes at least one modification not synchronized to the content management system by comparing the sync tree and the local tree.

17. The system of claim 16, wherein instructions further cause the processor to generate a set of operations configured to operate on the content items stored by the content management system to converge the server state and the file system state.

18. The system of claim 16, wherein instructions further cause the processor to:

determine that the user account on the content management system includes at least one modification not synchronized to the client device by comparing the remote tree and the sync tree; and

generate a set of operations configured to operate on the content items stored on the client device to converge the server state and the file system state.

19. The system of claim 16, wherein instructions further cause the processor to:

receive client modification data for content items stored on the client device; and

update, based on the client modification data, at least one of the local tree or the sync tree.

20. The system of claim 16, wherein instructions further cause the processor to:

receive, from the content management system, server modification data for content items stored by the content management system; and

update, based on the server modification data, at least one of the remote tree or the sync tree.