# US 2021/0173853 A1 · Selective synchronization of content items in a content management system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0173853 A1
- Document ID: US20210173853A1
- Status: Published application
- Kind: A1
- Application number: 17/179,946
- Filed: 2021-02-19
- Published: 2021-06-10
- Earliest claimed: 2017-12-28
- Assignees: Dropbox, Inc.
- Applicants: Dropbox, Inc.
- Inventors: Andrew Haven; Isaac Goldberg; Geoffry Song; Joshua Warner
- Web page: https://patentgrep.com/patent/US20210173853A1

## CPC

- G06F 16/11: File system administration, e.g. details of archiving or snapshots (error detection or correction of the data by redundancy in operations G06F11/14)
- G06F 1/04: Generating or distributing clock signals or signals derived directly therefrom
- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 3/0623: {in relation to content}
- G06F 3/0629: {Configuration or reconfiguration of storage systems}
- G06F 3/065: {Replication mechanisms}
- G06F 3/0652: {Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 11/1469: {Backup restoration techniques}
- G06F 12/1466: {Key-lock mechanism}
- G06F 16/113: {Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446)}
- G06F 16/116: {Details of conversion of file system types or formats}
- G06F 16/119: {Details of migration of file systems (migration mechanisms in storage systems G06F3/0647)}
- G06F 16/122: {using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185)}
- G06F 16/125: {characterised by the use of retention policies (retention policies for HSM systems G06F16/185)}
- G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)}
- G06F 16/13: File access structures, e.g. distributed indices (arrangements of input from, or output to, record carriers G06F3/06)
- G06F 16/137: {Hash-based (content-based indexing of textual data G06F16/31)}
- G06F 16/148: {File search processing}
- G06F 16/152: {using file content signatures, e.g. hash values}
- G06F 16/156: {Query results presentation}
- G06F 16/16: File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F 16/162: {Delete operations (erasing in storage systems G06F3/0652)}
- 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)}
- G06F 16/172: Caching, prefetching or hoarding of files
- G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs}
- G06F 16/1744: {using compression, e.g. sparse files}
- G06F 16/176: Support for shared access to files; File sharing support
- G06F 16/1767: {Concurrency control, e.g. optimistic or pessimistic approaches}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 16/1787: {Details of non-transparently synchronising file systems}
- G06F 16/18: File system types
- G06F 16/182: Distributed file systems
- G06F 16/1827: {Management specifically adapted to NAS (management of storage area networks [SAN] G06F3/067)}
- G06F 16/183: {Provision of network file services by network file servers, e.g. by using NFS, CIFS (network file access protocols H04L67/1097)}
- G06F 16/184: {implemented as replicated file system}
- G06F 16/1844: {Management specifically adapted to replicated file systems}
- G06F 16/185: Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof (details of archiving G06F16/11)
- G06F 16/2246: {Trees, e.g. B+trees}
- G06F 16/2255: {Hash tables}
- G06F 16/2322: {using timestamps}
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/24552: {Database cache management}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/275: {Synchronous replication}
- G06F 16/9027: {Trees}
- G06F 16/907: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F 16/951: Indexing; Web crawling techniques
- G06F 16/955: using information identifiers, e.g. uniform resource locators [URL]
- G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- 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]}
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- 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)}
- H04L 9/3247: {involving digital signatures}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- 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)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/101: {Access control lists [ACL]}
- H04L 63/102: {Entity profiles}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- 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]
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F 2212/1052: Security improvement
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- H04L 67/306: User profiles
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system can selectively synchronize content based on synchronization settings. In some examples, a client stores a local tree representing a local set of content items associated with an account on a content management system, the local tree including respective local nodes corresponding to the local set of content items. The client stores a remote tree representing a remote set of content items associated with the account, the remote set being stored at the content management system and including respective remote nodes corresponding to the remote set of content items. The client receives a synchronization setting disabling local storage of the content item. In response, the client deletes a local copy of the content item, removes a corresponding local node from the local tree, and adds, to a remote node on the remote tree, an attribute indicating that local storage of the content item has been disabled.

## Claims

### Claim 1

A method comprising:
receiving, at a client device, a synchronization setting for a content item associated with a user account of a content management system, the synchronization setting disabling local storage of a content item;
storing, at a client device, a local tree data structure representing content items in a file system on the client device, the local tree data structure excluding the content item for which synchronization is disabled; and
storing, at the client device, a remote tree data structure representing a remote set of content items associated with the user account, the remote tree data structure including the content item having an attribute indicating that local storage of the content item has been disabled, whereby the content item is excluded from being stored on the client device as a result of a future synchronization while the attribute remains associated with the content item in the remote tree data structure.

### Claim 2 (depends on 1)

The method of claim 1, wherein receiving the synchronization setting comprises:
deleting a local copy of the content item from the client device.

### Claim 3 (depends on 1)

The method of claim 1, wherein receiving the synchronization setting comprises receiving, via a graphical user interface on the client device, user input identifying the synchronization setting.

### Claim 4 (depends on 1)

The method of claim 1, further comprising presenting, via a graphical user interface, the content items in the file system on the client device and one or more graphical control elements for selecting respective synchronization settings for the content items in the file system on the client device.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
detecting a remote change to the content item; and
in response to the remote change, updating the representation of the content item on the remote tree data structure to reflect the change, the representation of the content item on the remote tree data structure being based on a server state associated with the content item.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
detecting one or more changes to at least one of the remote tree data structure or the local tree data structure; and
based on the one or more changes, synchronizing the remote tree data structure and the local tree data structure.

### Claim 7 (depends on 6)

The method of claim 6, wherein synchronizing the remote tree data structure and local tree data structure comprises:
identifying the representation of the content item on the remote tree data structure;
determining that the hidden attribute is associated with representation of the content item in the remote tree data structure; and
based on the hidden attribute, continue excluding the representation of the content item from the local tree data structure.

### Claim 8 (depends on 7)

The method of claim 7, wherein the one or more changes represent a move operation at the content management system, the move operation moving a remote copy of the content item from a first path to a second path, and wherein the one or more changes comprise moving the representation of the content item associated with the content item to a different location within the remote tree data structure, the different location corresponding to the second path.

### Claim 9 (depends on 8)

The method of claim 8, wherein moving the representation of the content item to the different location comprises storing the representation of the content item at the different location in the remote tree data structure and retaining the hidden attribute associated with the representation of the content item.

### Claim 10 (depends on 7)

The method of claim 7, further comprising:
detecting an add operation at the client device, the add operation adding a second content item on the client device, the second content item being stored at a path associated with the representation of the content item and a remote copy of the content item;
determining that synchronization of the second content item at the client device would create a conflict with the remote copy of the content item based on the path comprising a same path for both the second content item and the remote copy of the content item;
in response to determining the conflict, modifying the path of the second content item on the client device to yield a second path; and
storing the second content item on the client device at the second path.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
adding a representation of the second content item to the local tree data structure, the representation of the second content item representing the second content item and associating the second content item with the second path; and
in response to adding the representation of the second content item to the local tree data structure, synchronizing the local tree data structure and the remote tree data structure, wherein synchronizing the local tree data structure and the remote tree data structure comprises adding a representation of the second content item to the remote tree data structure corresponding to a remote copy of the second content item.

### Claim 12 (depends on 11)

The method of claim 11, wherein the representation of the second content item on the remote tree data structure associates the remote copy of the second content item with the second path.

### Claim 13

A non-transitory computer readable medium comprising instructions, the instructions, when executed by a client device, cause the client device to:
receive, at a client device, a synchronization setting for a content item associated with a user account of a content management system, the synchronization setting disabling local storage of a content item;
store, at a client device, a local tree data structure representing content items in a file system on the client device, the local tree data structure excluding the content item for which synchronization is disabled; and
store, at the client device, a remote tree data structure representing a remote set of content items associated with the user account, the remote tree data structure including the content item having an attribute indicating that local storage of the content item has been disabled, whereby the content item is excluded from being stored on the client device as a result of a future synchronization while the attribute remains associated with the content item in the remote tree data structure.

### Claim 14 (depends on 13)

The non-transitory computer readable medium of claim 13, wherein receiving the synchronization setting comprises:
deleting a local copy of the content item from the client device.

### Claim 15 (depends on 13)

The non-transitory computer readable medium of claim 13, wherein receiving the synchronization setting comprises receiving, via a graphical user interface on the computing device, user input identifying the synchronization setting.

### Claim 16 (depends on 13)

The non-transitory computer readable medium of claim 13, storing instructions which, when executed by the client device, cause the client device to:
detect a remote change to the content item; and
in response to the remote change, update the representation of the content item on the remote tree data structure to reflect the change, the representation of the content item on the remote tree data structure being based on a server state associated with the content item.

### Claim 17 (depends on 13)

The non-transitory computer readable medium of claim 13, storing instructions which, when executed by the client device, cause the client device to:
detect one or more changes to at least one of the remote tree data structure or the local tree data structure; and
based on the one or more changes, synchronize the remote tree data structure and the local tree data structure;
wherein the one or more changes represent a move operation at the content management system, the move operation moving a remote copy of the content item from a first path to a second path, and wherein the one or more changes comprise moving the representation of the content item to a different location within the remote tree data structure, the different location corresponding to the second path.

### Claim 18 (depends on 16)

The non-transitory computer readable medium of claim 16, wherein synchronizing the remote tree data structure and the local tree data structure comprises:
identifying the representation of the content item on the remote tree data structure;
determining that the hidden attribute is associated with the representation of the content item; and
based on the hidden attribute, excluding the representation of the content item from the local tree data structure;
wherein moving the representation of the content item to the different location comprises storing the representation of the content item at the different location in the remote tree data structure and retaining the hidden attribute associated with the representation of the content item.

### Claim 19

A client device comprising:
one or more processors; and
at least one non-transitory computer readable medium having stored therein instructions which, when executed by the one or more processors, cause the client device to:
receive, at a client device, a synchronization setting for a content item associated with a user account of a content management system, the synchronization setting disabling local storage of a content item;
store, at a client device, a local tree data structure representing content items in a file system on the client device, the local tree data structure excluding the content item for which synchronization is disabled; and
store, at the client device, a remote tree data structure representing a remote set of content items associated with the user account, the remote tree data structure including the content item having an attribute indicating that local storage of the content item has been disabled, whereby the content item is excluded from being stored on the client device as a result of a future synchronization while the attribute remains associated with the content item in the remote tree data structure.

### Claim 20 (depends on 19)

The client device of claim 19, storing instructions which, when executed by the one or more processors, cause the client device to:
detect one or more changes to at least one of the remote tree data structure or the local tree data structure; and
based on the one or more changes, synchronize the remote tree data structure and
the local tree data structure, wherein synchronizing the remote tree data structure and the local tree data structure comprises:
identifying the representation of the content item on the remote tree data structure;
determining that the hidden attribute is associated with the representation of the content item on the remote tree data structure; and
based on the hidden attribute, excluding the representation of the content item from the local tree data structure.
