Patent Grant
12118112
The present application relates to cloud-based content management systems. More specifically, the example embodiment(s) described herein relate to cloud-based content management systems for storing, managing, sharing and accessing digital content such as digital documents and content items.
Traditionally, businesses and other organizations have stored their digital content, such as documents, files, and other digital information, on network file servers. Such file servers are typically located on-site behind a network firewall that prevents unauthorized network access to the content items stored on the file server. Content created by employees belongs to the business. On a file server, such content is centralized, allowing a business to easily segregate personal content items from content belonging to the business. That is, the business treats all items residing on the file server as business-owned content. Furthermore, this centralized view allows a business to easily manage the content. For example, the IT manager or administrator can set access control permissions on content stored on the company file server.
To work remotely, employees often store content items locally at their personal computers, personal accounts, and/or personal storage devices so that they can work with the content items offline or otherwise while not connected to the file server. This is less than ideal from the employer's perspective because the employer has less control over the locally stored content items when compared to the content items stored on the file server. This poses risk such as when, for example, the employee's personal computing device is lost, damaged, or stolen. Furthermore, the employer loses control of access of an offline copy outside of the file server.
A business may use a cloud-based content management service to “host” their content on servers operated by the service in addition to or instead of storing content on their own file servers. Cloud-based storage provides a number of benefits to businesses and their employees alike. One example of an online content management service is the “Dropbox” service provided by Dropbox, Inc. of Sa Francisco, CA. The Dropbox service offers the ability to synchronize and share hosted content items among multiple devices and users. This flexibility, which stems for storing and synchronizing content both at end-user devices and on Dropbox, Inc. servers, supports a variety of different on-site and remote working arrangements.
With some existing cloud-based content management systems, the content storage model is less centralized than the traditional file server model. In particular, with these systems, each user of the system has their own individual synchronization repository on their personal computing device where content items synchronized with the system are stored. Further, each user maintains their individual synchronization repository independently of each other.
Some existing systems provide mechanisms to share selected content items between synchronization repositories. For example, with some existing systems, user Alice can share a folder in her synchronization repository with user Bob such that updates Bob makes to the shared folder in his synchronization repository are seen by Alice in her synchronization repository, and vice versa. However, with existing system, ownership of the shared folder is tied to an individual. This is problematic if Alice leaves the company and decommissions her synchronization repository or simply deletes the shared folder from her synchronization repository. In this case, the folder she shared with Bob may no longer be accessible to Bob. In the worst case, all of the work accumulated in the shared folder is lost.
Another problem with shared folders on existing systems is that hierarchical information pertaining to the shared folder may be lost when the shared folder is incorporated into another's synchronization repository. For example, assume Alice has a folder in her synchronization repository with the path /A/B/C. With existing systems, if Alice shares folder /A/B/C with Chris, the folder appears as /C in Chris' synchronization repository with the hierarchical information about parent folders “A” and “B” lost. Thus, different hierarchical information may be available to different users with respect to the same resource, making it difficult to communicate about the exact location of the resource. Furthermore, additional sharing of the resource or parent resources is constrained. For example, a system may prevent Alice from sharing folder /A/B with Bob after sharing folder /A/B/C with Chris.
Overall, existing cloud-based content management systems, due to the individualized and distributed nature of synchronization repositories, increase coordination costs for a business when used for managing and storing content items belonging to the business. Given the increasing amount of digital information generated by businesses, hosting of content items by businesses with cloud-based content management services can only be expected to increase. This trend is coupled with a desire of the businesses to retain a level of control over the content they host with such services and to provide more customizable permissions over such content. The present invention fulfills this and other needs.
The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.
The example embodiment(s) of the present invention are illustrated by way of example, and not in way by limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the example embodiment(s) the present invention. It will be apparent, however, that the example embodiment(s) may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the example embodiment(s).
A client device 102-104 executes a client application 112. As used herein, the term “application” refers generally to a unit of executable software that implements a certain functionality or theme. The themes of an application vary broadly across any number of disciplines and functions (such as on-demand content management, e-commerce transactions, brokerage transactions, home entertainment, calculator etc.), and one application may have more than one theme. The unit of executable software generally runs in a predetermined environment. The client application 112 may cause one or more components to become available on the client devices 102-104, such as but not limited to a graphical user interface (GUI) 110, access to content 114 stored in association with one or more namespaces, and namespace metadata 116.
The client devices 102-104 are configured to connect to a communications network 106. The communications network 106 may include one or more communications networks such as, but not limited to, local area networks, cellular networks, wireless networks, an intranet, the Internet, and/or any other communications link over which data may be transferred. The communications network 106 connects the clients 102-104 to a cloud-based content management system 108.
The content management system 108 manages and stores managed content “in the cloud” that is accessible by users. For example, a user using a client device 102-104 may access managed content managed by the content management system 108 via a desktop application, a mobile application, a web application, or through an application program interface (API). A user may use one or more client devices 102-104. For example, a user may log into an associated account from one or more devices. In some embodiments, a user may register one or more devices with the content management system 108. Permissions for accessing content may be managed on a per-user basis and/or a per-device basis, and any combination thereof may be implemented for any subset of content.
In some embodiments, a user can access managed content through a synchronization process that synchronizes a local copy of specific content on one or more client devices 102-104 with content on one or more other client devices 102-104 and/or content stored in content management system 108. For example, a user may create or modify a document on a laptop computer device linked to the user's account, and that update is automatically replicated through the content management system 108 to a desktop computer device also linked to the user's account. Alternatively and/or in addition, an updated version of the document may be stored by the content management system 108, such as in a content item server 118, and the user may access the document over the Internet, such as from a browser or an application executing on a smartphone computer device.
Content management system 108 includes a content item server 118 and a control server 120 connected to the communications network 106, content item storage servers 122-124, a user account database 126, and a namespace metadata database 128. As used herein, the term “server” refers to any computerized component, system or entity regardless of form which is adapted to provide data, files, applications, content, or other services to one or more other devices or entities on a computer network. In accordance with some embodiments, content management system 108 is implemented on one or more conventional computing devices, such as but not limited to a server computer, a network device, a laptop computer, a desktop computer, a workstation computer, a blade server, a mainframe computer, other types of computing device, or any combination thereof.
The content management system 108 provides content management services to clients 102-104 for content, such as content items and folders stored in association with one or more namespaces. The folders may include shared folders, and the namespaces may include nested namespaces, all of which shall be described in greater detail hereafter. As used herein, the term “manage” refers to storing and providing content, storing and providing content metadata, authentication, managing permissions, creating and managing accounts, and any other function including but not limited to all the functions described herein with respect to the content management system 108.
In some embodiments, the content management system 108 is an Internet content management service for managing content over the Internet or other public network and/or an intranet content management service for managing content over a local area network (LAN) or other private network. It should be appreciated that the configuration of components within the content management system 108 is merely an example configuration, and the components within the content management system 108 may be arranged in any suitable configuration.
A content item managed by content management system 108 may be a logical collection of digital information including, but not limited to, a digital document, file, or other logical collection of digital information. Often, a content item corresponds to a known media type such as, for example, an image (e.g., JPEG, TIFF, GIF, etc.), music (e.g., .MP3, AIFF, M4A, WAV, etc.), a movie (e.g., MOV, MP4, M4V, etc.), a word processing document (e.g., DOC, DOCX, PAGES, etc.), other document (e.g., PDF, etc.), a spreadsheet document (e.g., XLS, XLSX, NUMBERS, etc.), a presentation document (e.g., PPT, PPTX, KEY, etc.), a web page (e.g., HTM, HTMLS, etc.), or a text file (e.g., TXT, RTF, etc.). However, a content item managed by content management system 108 is not limited to being a particular media type, and the content item may encompass any logical collection of digital information including binary data, text data, or other digital information.
The content management system 108 may also manage one or more folders. A folder managed by the content management system 108 is a named collection of one or more content items and/or other folders. A folder may be empty, meaning it contains no content items or other folders. Because folders can be nested in other folders, the content items and folders are arranged in a plurality of hierarchies. Leaf nodes of a hierarchy either represent a content item or an empty folder with no contents.
The content management system 108 may include multiple data centers that house backend systems comprising one or more servers such as content item servers 118, control servers 120, storage servers 122-124, and/or other servers. The data centers may be geographically dispersed from one another, such as across the continental United States. Network requests from one of the clients 102-104 to the content management system 108 are routed to an appropriate data center with a particular backend system based on a variety of possible factors such as, but not limited to the content, nature, or type of the request and/or geographic location of the network request.
In some embodiments, each backend system includes multiple control servers, such as control server 120, and/or multiple content item servers, such as content item server 118, each coupled to a communications network 106 via a respective network communication module (e.g., 132 or 136). The communications network 106 may be the Internet, but may also be any local area network (LAN) and/or wide area network (WAN).
In some embodiments, each content item server 118 and each control server 120 is a Web server that receives network requests from the client application 112 and delivers network responses to the client application 112 via HTTP, HTTPS or similar protocol. In essence, the content item servers 118 are configured to store and retrieve blocks of content items stored in storage servers 122-124 as requested by the client application 112. The control servers 120 are configured to control the content item management process in conjunction with client application 112, including providing access to content 114 stored in association with one or more namespaces, and selectively synchronizing content 114 between content management system 108 and clients 102-104 in conjunction with the client application 112 as described below.
The content item server 118 typically includes a network communication module 132 and a block request module 134. The network communications module 132 connects the content item server 118 to the communication network 106 and enables receipt of communications from the communication network 106 and the provision of communications to the communication network 106 bound for a client device 102-104 or other destinations. The block request module 134 is primarily responsible for receiving requests for content item blocks, processing them and returning the requested blocks to the client device 102 via the network communication module 132.
The storage servers 122-124 store content item blocks. Each content item block may contain all of or a portion of a content item managed by the content management system 108. Each content item block may be a fixed size such as, for example, 4 Megabytes (MB). Depending on the size of the content item, the content item may be stored on one or more of the storage servers 122-124 in one or more content item blocks, with the last content item block potentially having less than the fixed block size amount of data. For example, the block request module 134 may receive and process is “store” requests and/or “retrieve” requests to store one or more blocks of data B1, B2, . . . BN corresponding to one or more specified content items.
The control server 120 includes a network communications module 136, a namespace management module 138, and a synchronization module 140, which are in communication with each other. The network communications module 136 connects the control server 120 to the communication network 106 and enables receipt of communications from the communication network 106 and the provision of communications to the communication network 106 bound for the client application 112 at a client device 102 or other destinations.
The namespace management module 138 is primarily responsible for receiving requests to view or change (i.e., add, edit, or delete) namespace metadata in the namespace metadata database 128, processing the requests, and returning a response to the requesting client device 102 via the communication module 136. In some embodiments, the namespace management module 138 maintains permissions that grant access to a particular namespace to a set of users. Permissions shall be discussed in greater detail hereafter.
In some embodiments, a user with access to a namespace may synchronize content 114 stored in association with the namespace on the client devices 102-104 with the corresponding content items managed by content management system 108. For example, the synchronization module 140 may periodically synchronize content 114 stored in association with a particular namespace and stored at a client device 102-104 with the corresponding content (e.g. content items and/or folders) stored in storage servers 122-124. When content, such as a content item or a folder, descends from a folder to which a particular namespace is rooted, then the content belongs to the particular namespace. Namespaces shall be described in greater detail hereafter.
In some embodiments, the synchronization module 140 periodically synchronizes namespace metadata 116 stored at a client device 102-104 with namespace metadata stored in namespace metadata database 128. Synchronization may be initiated when changes are detected for the content 114 belonging to the namespace, such as by long polling or short polling techniques between the client devices 102-104 and the content management system 108.
The account database 126 stores information about accounts that are created and/or managed by the content management system 108. In some embodiments, the content management system 108 supports individual accounts that each correspond to an individual user. Alternatively and/or in addition, the content management system 108 may support entity accounts. An entity account corresponds to an entity that is associated with a set of users. The set of users may be limited to users with individual accounts, or may include one or more users that do not have an account with the content management system 108. Each account may have a record in the account database 126. In some embodiments, a record for an individual account in the account database 126 includes the following information, or a subset or a superset thereof:
In some embodiments, fewer and/or additional modules, functions, or databases are included in content management system 108. The modules shown in
Although
Moreover, one or more blocks in
Namespace
A namespace is a collection of content that is under common access control in content management system 108. A namespace has permissions comprising access control information that allows a set of users to access content in the namespace. Permissions can specify different types of access granted to different users for a particular namespace. Permissions shall be described in greater detail hereafter.
A namespace can be rooted to a particular folder. However, a namespace is not equivalent to a folder, and not every folder has a namespace rooted to it. When content, such as a content item or a folder, descends from a folder to which a particular namespace is rooted, then the content belongs to the particular namespace. The content that belongs to a particular namespace are also in a hierarchy that descends from the folder to which the namespace is rooted. Thus, the root folder of the namespace is the root of a particular hierarchy containing the contents that belong to the namespace.
According to some embodiments, only a subset of the content items in a namespace are synchronized with a client device 102 at any given time. For example, in some embodiments, when a user is granted access to a namespace and connects an associated client device 102 with the namespace, only a subset of data associated with the namespace is automatically downloaded from content management system 108 and stored at the client device 102, such as namespace metadata 116 and/or hierarchical data that describes the hierarchy containing the contents that belong to the namespace. In some embodiments, the hierarchical data that describes the hierarchy is treated as namespace metadata 116 and is included in the namespace metadata 116.
When only a subset of the data associated with the namespace is automatically downloaded, the user can join the client device 102 to the namespace more quickly because at least some of the content 114 stored in association with one or more namespaces in the namespace is not downloaded to the client device 102 over the communications network 106 from the content item server 118. Furthermore, this allows the user to join the client device 102 to the namespace even if the amount of available storage space at the client device 102 is less than the amount that would be needed to store most or all of the content 114 that belongs to the namespace.
In some embodiments, the GUI 110 that is presented includes a user browse-able and interactive representation of the hierarchy of the namespace. This may apply to one or more of the types of namespaces described hereafter, such as but not limited to the root namespace, a shared namespace, a nested namespace, or any combination thereof. According to some embodiments, a user can browse the hierarchy of at a client device 102 using a file system browser provided by an operating system of the client device 102, such as but not limited to the Finder on MAC OS devices or the WINDOWS EXPLORER on WINDOWS devices.
According to some embodiments, after a client device 102 becomes a member of a namespace, an actionable icon appears in the GUI 110 at the client device 102. For example, the icon may appear on the desktop of the GUI 110 provided by an operating system on the client device 102. The user may interact with the icon (e.g., double-click on the icon) to open a file explorer like-view of the content item hierarchy of the namespace. Further, an icon or other indication of the namespace may also be displayed with other resources in an interface provided by the operating system on the client device 102. For example, an actionable icon or text may be listed in the GUI 110 along with mounted drives, shared drives, network drives, or other connected resources of the client device 102. By doing so, the user can access the namespace from a familiar location where the user knows to access other connected resources such as mounted drives, external disks, and network drives.
Root Namespace
One particular type of namespace is a root namespace. In some embodiments, a root namespace is rooted to a root folder of an individual account and/or an entity account.
In some embodiments, a root namespace is rooted to a root folder of an individual account. The content items and folders associated with the user's account are arranged in a hierarchy that includes the root folder, which is the root node of the hierarchy. The root namespace includes content items and folders associated with a user's account with a cloud data storage service such as, for example, the aforementioned DROPBOX content management service. By successfully authenticating against the account (e.g., with a valid username/password), a user implicitly has access to the documents in the root namespace associated with the user's account.
In some embodiments, an individual account may be associated with multiple root namespaces, each rooted to a root folder. For example, in an implementation, multiple root namespaces may emulate multiple mounted drives in a file system. Alternatively and/or in addition, some embodiments may restrict each individual account to one root folder and one root namespace. In this case, multiple mounted drives in a file system would be emulated by child folders of the root folder.
In some embodiments, a root namespace is rooted to a root folder of an entity account. An entity account is associated with a set of users or individual accounts. Thus, a root folder of an entity account can be considered a shared folder, and the root namespace of the entity account may be considered a shared root namespace. In some embodiments, an entity account may be associated with multiple root namespaces, each rooted to a root folder of the entity account. Permissions may be managed separately for these root namespaces. Alternatively and/or in addition, some embodiments may restrict each entity account to one root folder and one root namespace.
In some embodiments, a team folder is implemented that is associated with a team. A team comprises a set of one or more users, or individual accounts. However, an entity account is not maintained for the team. The content items and folders associated with the team are arranged in a hierarchy that descends from the team folder, which is the root node of the hierarchy of content belonging to the team folder. A team namespace is rooted to the team folder. In some embodiments, the team namespace is treated as a root namespace. Alternatively and/or in addition, in some embodiments, the team namespace is treated as a shared namespace that is not a root namespace.
Shared Namespaces
In some embodiments, the content management system 108 manages one or more shared folders. The content management system 108 associates the shared folder with a namespace, which is considered a shared namespace. As used herein, the term shared namespace refers to a namespace rooted to a shared resource that multiple user can have access to, such as a shared folder.
The content management system 108 maintains permissions for the shared namespace. The permissions grant access to content that is in a shared folder, such as the folders and content items that are in a hierarchy that descends from the shared folder. This content is considered as “belonging to” the namespace rooted to the shared folder.
In some embodiments, a root folder may be a shared folder—that is, a shared namespace may be rooted to the root folder. For example, the root folder associated with an entity account may be accessible by a set of users associated with a group. A shared root folder may be implemented as a distinct type of shared folder, as a generic shared folder. In some embodiments, a shared root folder may exist in association with a group, or team, comprising a set of users; such a shared root folder does not need to be associated with a specific account, such as an entity account.
The content management system 108 maintains permissions for the shared namespace that grant access to the shared namespace to a set of users. Permissions shall be discussed in greater detail hereafter. The set of users granted access to the namespace are considered members of the namespace. In some embodiments, a namespace for which sharing is enabled is considered a shared namespace even if the number of members of the shared namespace falls to one or zero.
The permissions may grant access to the shared namespace to a set of users. Different users in the set of users may have different access types, which shall be described in greater detail hereafter. The shared namespace is used by the content management system 108 to maintain permissions that allow multiple users to access the content belonging to the shared namespace. However, in some embodiments, the set of users that are granted access to the shared namespace may fall to one user or zero users.
A shared namespace may be a shared root namespace. A shared root namespace is rooted to a root folder of an account, such as the root folder of an entity account. A shared namespace may also be rooted to a folder that is not a root folder of any account. For example, a shared namespace may be rooted to a shared folder that is a child folder of a parent folder rooted to a second namespace. As used herein, a child folder of a parent folder is a folder that descends from the parent folder in a hierarchy, either directly or indirectly. That is, a parent folder may be an ancestor with intermediate folders between the parent folder and the child folder. Thus, the second namespace is a parent namespace of the shared namespace. That is, this shared folder is in a hierarchy beginning with the parent folder to which the parent namespace is rooted. In this case, the shared namespace is a child shared namespace of the parent namespace, and is mounted at a path that is relative to the parent namespace, which is also referred to as a mounting location of a shared namespace. For example, in
In some embodiments, when a first namespace is mounted to a path in a second namespace, the path is specified relative to the second namespace. Nested namespaces shall be described in greater detail hereafter.
In some embodiments, a shared namespace can have different synchronization configurations. These synchronization configurations can be set for all users with access to the shared namespace, or they may be set independently for each user and/or each client device 102-104. In a cloud-only synchronization configuration, the contents in the shared namespace are configured for cloud-access only. In an offline synchronization configuration, the content 114 belonging to a namespace is synchronized at the client device 102 and available for offline access. Alternatively and/or in addition, the synchronization status may be set for any shared folder and/or content item in a shared folder.
A synchronization configuration status icon may be displayed in association with the shared namespace, shared folder, and/or content item so that a user of a client device 102-104 can quickly discern the current synchronization configuration status of content. For example, GUI 110 may display the synchronization configuration status icon in association with the content that a particular user of the client device 102-104 can visually determine which content he has offline access to.
Nested Namespaces
As noted above, a namespace is a collection of content that is under common access control, and has permissions comprising access control information that allows a set of users to access content in the namespace. At the highest level, a nested namespace is a collection of content that is under common access control that may be distinct from the permissions for the parent namespace. A nested namespace may be rooted to a folder that is in a hierarchy that descends from a parent folder to which the parent namespace is rooted. The nested namespace is mounted to the parent namespace at a path relative to the parent namespace. Mounting a nested namespace is described in greater detail hereafter.
In some embodiments, a nested namespace is rooted to a shared folder within a parent shared folder, and is the nested namespace created to allow distinct permissions to be maintained for the nested folder that are distinct from permissions maintained for the parent namespace rooted to the parent shared folder. For example, a nested namespace may be created to distinctly manage access control when a user with management access to the parent namespace shares a content item or folder in the parent namespace with another user who is not a member of the parent namespace.
In some embodiments, nested namespaces are not created for content items and/or folders unless an instruction is received to create distinct permissions for the content item or folder. In some embodiments, namespaces are only rooted to folders, and unique permissions for individual content items are maintained on a per-item basis without using a namespace.
In some embodiments, the content management system 108 continues to maintain one or more nested namespaces even if the permissions for the nested namespace match the permissions for the parent namespace. For example, if a nested namespace is created because a subfolder of a parent namespace is shared to a first user who is not a member of the parent namespace, the nested namespace may be maintained even if access to the subfolder by the first user is revoked or if the first user becomes a member of the parent namespace.
Alternatively and/or in addition, the nested namespace may be removed when the permissions of the parent namespace match the permissions of the child nested namespace. The content management system 108 may implement both behaviors, either behavior, or another behavior. The behavior may depend on user input, such as a setting selected by a member with permissions to set the setting. In one embodiment, a garbage collection mechanism periodically removes nested namespaces that are no longer necessary because the permissions of the nested namespace are identical and may be merged with the permissions of a parent namespace.
A nested namespace may be mounted in different namespaces. For example, in
The content management system 108 manages a shared folder F1. Namespace NS_1 is rooted to shared folder F1. The content management system 108 maintains permissions for namespace NS_1 that grant access to namespace NS_1 to a first set of users. The permissions for namespace NS_1 grant access to both user A and user B, since namespace NS_1 is available to both users. Both users have mounted namespace NS_1 to their root folders, A_ROOT and B_ROOT, respectively.
The content management system 108 also manages folder F2. Folder F2 is a child folder of folder F1. Folder F2 is a shared folder, but no special permissions are defined for folder F2. Folder F2 is available to both user A and user B based on the permissions for namespace NS_1. In some embodiments, no namespace is rooted to F2 unless the permissions for the shared folder F2 will be maintained independently from the namespace in which the folder F2 resides, namespace NS_1.
The content management system 108 also manages folder F3. Namespace NS_3 is rooted to shared folder F3. The content management system 108 maintains permissions for namespace NS_3 that grant access to namespace NS_3 to a second set of users. The permissions for namespace NS_3 grant access to user A. User A has mounted namespace NS_3 to the root namespace NS_A. In some embodiments, the permissions for namespace NS_3 do not grant access to user B, or user B has chosen not to access NS_3.
The content management system 108 also manages folder F4. Folder F4 is a child folder of folder F3. Folder F4 is a shared folder, but no special permissions are defined for folder F4. Folder F4 is available to user A based on the permissions for namespace NS_3.
The content management system also manages folder F5. Namespace NS_5 is rooted to shared folder F5. The content management system maintains permissions for namespace NS_5 that grants access to namespace NS_5 to a third set of users. The permissions for namespace NS_5 grant access to namespace NS_5 both user A and user B, since namespace NS_5 is available to both users. User A has mounted namespace NS_5 to folder F3, while User A has mounted namespace NS_5 to its root folder B_ROOT.
The content management system also manages folder F6. F6 is a private folder of user B that is not shared. No namespace is established for folder F6.
The mount location to which a namespace is mounted can be described by a path relative to another namespace. In some embodiments, the mount location of a namespace is described by a path relative to a root namespace associated with an account. In some embodiments, a mount table is kept for multiple root namespaces. The mount table includes an identifier of the mounted namespace and a path relative to the root namespace. For example, the mount table for NS_A includes (relative to root namespace NS_A):
The mount table for NS_B includes (relative to root namespace NS_B):
In some embodiments, one or more types of namespaces (e.g. root namespaces, shared namespaces, nested namespaces, or any combination thereof) are implemented using the same data structure, object type, and/or other implementation mechanism. Alternatively and/or in addition, one or more types of namespaces may be implemented using a distinct data structure, distinct object type, or other distinct implementation mechanism.
Example Process for Creating a Namespace
At block 302, a computing device, such as a content item server 118, stores content in a content management system, such as content management system 108, for a plurality of users. The content includes a plurality of content items and a plurality of folders that are arranged in a plurality of hierarchies.
At block 304, a computing device, such as a control server 120, establishes a plurality of root namespaces. Each root namespace is associated a root folder of an account corresponding to one or more users. For example, a root namespace may be rooted to a root folder of an individual account of a user. Alternatively and/or in addition, a root namespace may be rooted to a root folder of an entity account that is associated with a set of users with permissions to access the root namespace of the entity account.
At block 306, a computing device, such as the control server 120, establishes a first namespace rooted to a first folder selected from the plurality of folders. In some embodiments, the first namespace is a root namespace of an individual account and/or an entity account. In some embodiments, the first namespace is a namespace rooted to a team folder which is associated with a set of individual accounts. In some embodiments, the first namespace is a shared namespace other than a root namespace of an individual account or an entity account.
At block 308, a computing device, such as the control server 120, maintains first permissions for the first namespace. The first permissions grant access to the first namespace to a first set of users of the plurality of users.
At block 310, a computing device, such as the control server 120, receives a request to share a second folder that is a child of the first folder in a particular hierarchy of the plurality of hierarchies.
At block 312, a computing device, such as the control server 120, establishes a second namespace rooted to the second folder. In some embodiments, the second namespace is a nested namespace.
At block 314, a computing device, such as the control server 120, maintains second permissions for the second namespace. The second permissions grant access to the second namespace to a second set of users of the plurality of users.
At block 316, process 300 returns and/or terminates. For example, processing may continue to processing a successive request, passing control to a calling process, generating any appropriate record or notification, returning after a method or function invocation, or terminating.
Namespace Metadata
The namespace metadata database 128 stores information about namespaces, which may be synchronized with namespace metadata 116 on the client devices 102-104. For example, the namespace database 128 may store information about root namespaces of individual accounts that are unshared, root namespaces of entity accounts that are shared, other shared namespaces, and/or other unshared namespaces.
According to some embodiments, the namespace metadata database 128 includes hierarchical data that describes a hierarchy of content items and/or folders that belong to each corresponding namespace. In some embodiments, a set of records are kept for each namespace, where each record indicates a content item or folder and a path of the content item or folder relative to the namespace. Such records may also include one or more namespaces that are mounted in the current namespace, along with a path relative to the current namespace indicating a mounting location within the current namespace.
According to some embodiments, the namespace metadata database 128 includes permissions comprising access control information for namespaces. In some embodiments, permissions are only maintained for shared namespaces, or namespaces that are rooted to a shared folder. In some embodiments, the permissions grant access to content in the namespace to a set of users. Such permissions may be subject to the permissions maintained for a nested namespace within a parent namespace. That is, a user that is a member of a parent namespace is not necessarily be a member of a child namespace. In some embodiments, even if a user is a member of both a parent namespace and a child namespace, the user may not have the same access type with respect to the parent namespace and the child namespace.
Permissions
Permissions are maintained that specify or otherwise indicate which user(s) and/or group(s) of users have access to content that belongs to a namespace. When the permissions for a particular namespace grant access to the particular namespace to a particular user, the content in the particular namespace is available to the user. The permissions may specify different levels of access, or access types, which shall be described in greater detail hereafter.
Although one or more embodiments described hereafter refer to permissions that grant access to a user without specifying a device, the permissions in any embodiment may be also implemented such that permissions are specifically granted to all devices of a user, a specific device of a user, or any combination thereof.
The permissions corresponding to a particular namespace can be based on explicit and/or implicit permissions specifying and/or indicating which user(s) and/or group(s) of users have access to the content, such as content items and folders, that belong to the namespace. The permissions corresponding to a particular namespace may also specify the access type granted to a user. Some example access types are described below; a subset of access types, a superset of access types, an overlapping set of access types, or other access types may be implemented:
In some embodiments, the permissions corresponding to a particular namespace are maintained as one or more access control records. An access control record can correspond to individual content items, individual folders, or a collection of content, such as a namespace that corresponds to a particular shared folder. The access control records may be grouped, indexed, or otherwise sorted by namespace, another property. In some embodiments, access control records are maintained for namespaces, content items and/or folders that are not shared. Alternatively, access control records may be maintained for shared namespaces, content items and/or folders that belong to a shared workspace.
In some embodiments, a user does not have access to a particular namespace, content item or folder unless the there is an access control record in the namespace metadata database 128 that grants explicit access or implicit access to the user.
In some embodiments, the permissions for a namespace grant explicit access to a particular user. Explicit access may come in the form of, for example, one or more access control lists (ACLs) and/or other data associated with the namespace, or an identifier thereof. For example, when a particular shared folder is shared with one or more users, the one or more users are explicitly added to the permissions maintained for the shared namespace rooted to the particular shared folder. The one or more users are explicit members of the shared namespace.
In some embodiments, the permissions for a namespace grant implicit access to a particular user. Implicit permissions are derived from explicit permissions for another namespace. For example, if the permissions for a particular namespace specify that permissions are inherited from a parent namespace in which the particular namespace is mounted, then users with access to the parent namespace will have access to the particular namespace based on the permissions maintained for the parent namespace. These members are implicit members of the particular namespace.
In some embodiments, implicit permissions for a particular namespace may be derived from an ancestor namespace that is higher than a parent namespace when the permissions for the particular namespace and the relevant ancestor namespace/s specify that permission are inherited. For example, when a client device requests access to particular content that belongs to a particular namespace, a traversal of the hierarchy of namespaces may be performed to evaluate the corresponding permissions and to determine whether the user is an implicit member of the particular namespace.
In some embodiments, an access control record for a particular namespace, content item, or folder includes all of the following information, or a subset or a superset thereof:
In some embodiments, a shared nested namespace is created when unique permissions are requested for a shared folder within a parent shared namespace to which the shared folder belongs. Example situations include, but are not limited to the sharing of a subfolder with a user who is not a member of the parent shared namespace, the granting of different permission types to the subfolder to a user who is a member of the parent shared namespace, or further restricting access to the subfolder.
In some embodiments, creating the shared nested namespace comprises setting the Parent Namespace ID to identify the parent shared namespace, and setting the Inherit Flag based to indicate whether permissions should be inherited from the parent namespace. Permissions are maintained for the shared nested namespace as well as the parent namespace. Depending on the value of the Inherit Flag, permissions for the shared nested namespace may or may not be inherited from the parent shared namespace.
Traversal Rights
In an example configuration, a first namespace is a shared namespace that is rooted to a first folder, and a second namespace is a nested shared namespace that is rooted to a second folder contained in the first folder in a particular hierarchy of content items and folders. Thus, the first namespace is a parent namespace of the second namespace.
When a user has access to the first namespace and the second namespace, the user is provided access to the first folder and its children in the particular hierarchy, including the second folder. When a user has access to the first namespace and does not have access to the second namespace, the user is provided access the first folder and its children in the particular hierarchy, excluding the second folder. That is, the exclusion of the user from the second namespace acts to negate permissions for contents of the first folder that belong to the second namespace; but for the negative permissions (i.e. the user not having access to the second namespace), the user would otherwise have been granted access to the contents of the first folder. When a user does not have access to the first namespace and has access to the second namespace, the user is provided access to the second folder and not the first folder.
In some embodiments, content management system 108 may provide the client devices 102-104 hierarchical data describing one or more hierarchies of content, such as content items and folders. For example, the hierarchical data may allow the client devices 102-104 to display the a file-system like hierarchy to a user, synchronize a local copy of the available content using a file-system like hierarchy, and/or otherwise access the content based on the file-system like hierarchy. In some embodiments, permissions to access one or more namespaces may include an access type (e.g. exist) that restricts access to knowing about the existence of content items and/or folders in the namespace. The exist access type allows a user to view the hierarchical data.
When a second user has at least exist access to a first namespace NS_1 but not the second namespace NS_2, the client device of the second user can display, store and/or otherwise use the hierarchical data 402 describing the particular hierarchy from the first folder F1, excluding the second folder F2 and its descendants. NS_1 is shown as being mounted in another namespace rooted to and/or containing folder 412, which may be the root folder of the second user, or another folder that the second user has access to.
In one embodiment, when a third user has at least exist access to the second namespace NS_2 but does not have at least view access to the first namespace NS_1, the client device of the third user can neverless display, store and/or otherwise use the portion of the hierarchical data 402 describing just the second folder F2 and its descendants. That is, the user is provided the information that folder F2 is a child of folder F1, even if the user cannot access the other contents of the first folder F1. NS_2 is shown as being mounted in another namespace rooted to and/or containing folder 422, which may the root folder of the third user, or another folder that the third user has access to.
Mounting a Namespace
A nested namespace may be mounted to the parent namespace at a path relative to the parent namespace. As used herein, a mounting operation refers to an operation that mounts or unmounts one or more namespaces from one or more mounting locations. In some embodiments, a shared namespace, may be mounted by multiple users. In some embodiments, a user can mount a shared namespace to either his root namespace, or another namespace that descends from his root namespace. That is, the shared namespace will be mounted in a mounting location comprising a path relative to the root namespace. When there is one or more intermediate namespaces, a path relative to the root namespace may be constructed by traversing a hierarchy of namespaces.
A nested namespace may be mounted in another nested namespace, creating a namespace hierarchy. In some embodiments, a limit to the levels of nesting may be implemented. For example, a limit may be implemented as a constraint that must be satisfied before a mounting operation is performed. Constraints shall be described in greater detail hereafter.
In some embodiments, only users who are explicit members are allowed to directly mount a shared namespace. That is, the content management system 108 may disallow a user from mounting a namespace when the user is only an implicit member of the namespace, such as a user who has access to a namespace because the namespace inherits permissions from a parent namespace of which the user is a member. Such a user will still be able to access the namespace through the parent namespace.
Actions Involving a Mounting Operation
The following example actions involve a mounting operation (e.g. mounting or unmounts one or more namespaces from one or more mounting locations). Other actions that involve mounting operation/s may be implemented based on nested namespaces and the permissions maintained for the nested namespaces. In some embodiments, the following actions and/or mounting operations are implemented, or a subset or a superset thereof. Any of these actions and/or mounting operations may be implemented as a default operation, or the relevant users may be prompted to allow the actions and/or mounting operations to proceed. Other behaviors other than the mounting operations described may be implemented in response to any of these actions.
In some embodiments, one action that causes one or more mounting operations is when a user creates a shared folder with distinct permissions, where the shared folder is in a parent shared folder. A nested namespace is created that is rooted to the new shared folder. Members of a parent namespace rooted to the parent shared folder may or may not see the change based on whether they are members of the nested namespace. For example, if the nested namespace does not inherit permissions and a particular member of the parent namespace is not a member of the nested namespace, then the contents of the nested namespace will be removed from the member's client device/s. In some embodiments, if a particular user is a member of both the nested namespace and the parent namespace, the namespace metadata for the new nested namespace is synchronized. In some embodiments, a GUI on a client device of the particular user may indicate that the shared folder has distinct permissions. If a particular user is only a member of the nested namespace, the particular user will not receive hierarchical data outside of the nested namespace. Such a user is referred to herein as an external user because the user is unaware of the parent namespace.
In some embodiments, one action that causes one or more mounting operations is when a member of a child namespace is added as a member of a parent namespace in which the child namespace is mounted. When a user gains access to the parent namespace, if the child namespace is mounted in the root namespace of the user, the child namespace may be unmounted from the root namespace of the user, and the parent namespace may be mounted in the root namespace of the user. The user may be retained as an explicit member of the child namespace.
In some embodiments, one action that causes one or more mounting operations is when a user deletes a shared folder to which a namespace is rooted that is mounted in the user's root namespace. In response, a mounting operation may be performed that unmounts the namespace rooted to the shared folder that the user wishes to delete. The shared folder and the corresponding namespace may still be available to other users, and the mounting of the corresponding namespace with respect to other users (e.g. other users' namespaces) is unaffected.
In some embodiments, one action that causes one or more mounting operations is when a user deletes a child shared folder that they have mounted in a team folder to which a shared namespace is rooted. The user may be required to have Manage access to the child shared folder and Modify access to parent shared folder. The child shared folder may be unshared for all users, including external users. In some embodiments, the content management system retains the content associated with the child namespace and the child shared folder. This allows for data to restored with respect to the child shared folder and its contents.
In some embodiments, one action that causes one or more mounting operations is when a user moves a child shared folder outside of parent shared folder to a different namespace than the parent namespace rooted to or containing the parent shared folder. The user may be required to have Modify access to the parent namespace, Modify access to the destination namespace, and Manage access to the child namespace rooted to the child shared folder being moved. External members are retained for the child namespace, but any implicit members who inherited permissions based on their membership in the parent namespace may no longer have access to the child namespace. In one embodiment, when a child shared folder is moved outside of the parent shared folder, an explicit member of the child namespace with access to the parent namespace will unmount the child namespace from the parent namespace and remount the child namespace.
In some embodiments, one action that causes one or more mounting operations is when permissions granting a user access to a parent namespace are revoked, but the user still has access to a child namespace of the parent namespace. In this case, the parent namespace is unmounted from the root namespace of the user, and the child namespace is mounted to the root namespace of the user.
In some embodiments, one action that causes one or more mounting operations is when a user renames a shared folder to which a particular namespace is rooted. The user may be required to have Modify access to the particular namespace. In some embodiments, the change is implemented by unmounting the shared namespace from its current parent namespace and then remounting the modified shared namespace to the current parent namespace. This action will cause the synchronization of the change in all users who have permissions to access both the parent namespace and the particular namespace.
Mount Constraints
In some embodiments, one or more constraints are imposed on the mounting of namespaces. For example, content management system 108 may require that a set of one or more constraints is satisfied before completing an action that requires a mounting operation. Such constraints may be used to prevent recursive loops, prevent ambiguities in access permissions, prevent errors, control complexity, and/or for any other reason. For example, one or more constraints may enforce a traditional file system hierarchy within a namespace associated with an account, which does not include cyclic graphs.
In some embodiments, a first constraint requires that a namespace cannot be mounted to more than one path in any shared namespace that is not a root namespace. That is, a namespace cannot have more than one parent namespace that is not a root namespace. The first constraint is analogous to restricting the hierarchy of content contained in a shared namespace, other than a root namespace, to a simple directory tree. In some embodiments, a version of the first constraint is implemented that does not allow a namespace to be mounted in more than one path in any shared namespace, including a root namespace that is also a shared namespace.
In some embodiments, the first constraint is implemented by associating the namespace with a single parent pointer identifying a single parent namespace other than root namespaces. For example, the parent-child relationship between a parent root namespace and child shared namespace may be maintained in the namespace metadata for the parent root namespace. Thus, the single parent pointer does not need to refer to the root namespace for any account that has the child shared namespace mounted in the respective root namespace.
In some embodiments, a second constraint requires that a namespace cannot be mounted to more than one path in a root namespace, or a child namespace thereof, for any user. That is, each namespace can only be mounted once in a root namespace, including in any intermediate namespaces that the root namespace is an ancestor of. When implemented, the second constraint will prevent looping scenarios, which is consistent with a traditional file system hierarchy. For example, if a nested namespace B is nested within namespace A, then a user cannot mount both B and A directly to a root namespace of the user, since namespace A includes nested namespace B; this would result in namespace B being mounted twice in the root namespace of the user.
The content management system 108 may require a set of constraints to be satisfied that includes one or more of the first constraints, the second constraint, and one or more other constraints. In one embodiment, when the content management system 108 receives a request from a particular user to mount the second namespace to a particular path in a particular namespace, the content management system 108 determines whether a set of one or more constraints is satisfied. When the set of one or more constraints is satisfied, mounting the second namespace to the particular path in the particular namespace. When any constraint in the set of one or more constraints is not satisfied, the content management system 108 may indicate that the action requiring the mounting operation has failed. Alternatively and/or in addition, the content management system 108 may perform a default operation, prompt a user with one or more alternative solutions, perform one or more alternative solutions, resolve the request in a manner that satisfies the one or more constraints, and/or any combination thereof.
Mount Lock
In some embodiments, one or more constraints are enforced using mount locks. As used herein, the term mount lock refers to a synchronization mechanism associated with individual namespaces to control access to the corresponding namespace with respect to mounting location changes. For one or more constraints, satisfying the constraint comprises obtaining mount locks for affected namespaces. To successfully perform a mounting operation, the mount lock must be obtained for each affected namespace.
As used herein, the term “affected namespace” refers to any namespace whose corresponding mount lock must be held in order to perform a particular mounting operation. In some embodiments, the affected namespaces for a mounting operation include the target namespace on which the mounting operation is performed, any ancestor namespaces of the target namespace, and when the mounting operation specifies a new parent namespace for the target namespace, the new parent namespace and any ancestor namespaces of the new parent namespace.
In some embodiments, mount locks are obtained for the following mounting operations:
In some embodiments, root namespaces are excluded from the set of affected namespaces. For example, excluding the root namespaces from the set of affected namespaces can help enforce the constraint a second namespace cannot be mounted to more than one path in any shared namespace that is not a root namespace. One way of excluding a root namespace is to not require a mount lock for the root namespace. In some embodiments, only root namespaces of individual accounts are excluded from the set of affected namespaces, while root namespaces of entity accounts are included.
The arrow indicates that user C attempts to move folder F13 to folder F12. To perform this action, namespace NS_13 must be unmounted from root namespace NS_C, and namespace NS_13 must be mounted to namespace NS_12. To successfully perform the mounting operation/s, the mount lock must be obtained for each affected namespace.
In some embodiments, the affected namespaces include the target namespace and its ancestors, excluding any root namespace. NS_13 is an affected namespace because it is the target namespace on which the mounting operation is performed. Thus, mount lock 504 is obtained for NS_13.
In some embodiments, the affected namespaces include the new parent namespace and its ancestors, excluding any root namespace. NS_12 is an affected namespace because it a new parent namespace for the target namespace. Thus, mount lock 506 is obtained for NS_12. NS_11 is an affected namespace because it an ancestor of NS_12. Thus, mount lock 508 is obtained for NS_12.
In this case, all the mount locks for the affected namespaces are successfully obtained. Thus, the content management system proceeds to perform the mounting operation and release the mount locks.
To successfully perform the mounting operation, the mount lock must be obtained for each affected namespace. NS_14 is an affected namespace because it is the target namespace on which the mounting operation is performed. Thus, mount lock 604 is obtained for NS_14.
In some embodiments, the affected namespaces include the ancestors of the target namespace, excluding any root namespace. Thus, mount locks 606-610 are obtained for namespaces NS_13, NS_12, and NS_11.
In some embodiments, the affected namespaces include the new parent namespace and its ancestors, excluding any root namespace. In this case, because user D is attempting to mount NS_14 to NS_12, the affected namespaces includes NS_12 and its ancestor namespace NS_11. However, because the mount lock 608 for NS_12 is already held, mount lock 612 cannot be obtained. Likewise, because the mount lock 610 for NS_11 is already held, mount lock 614 cannot be obtained.
If a mount lock for an affected namespace is not successfully obtained, then the constraint fails. In some embodiments, when the constraint fails, the action requiring the mounting operation and the failure is reported, such as to other components of content management system 108 and/or client devices 102-104. In some embodiments, a mounting operation can be salvaged, such as by automatically performing a default legal mounting operation, prompting the user with one or more possible legal mounting operations, and/or determining a compatible mounting operation that will resolve cause of failure and satisfy the constraint.
Example Process for Mounting a Namespace
At block 702, a computing device, such as the control server 120, receives a request to perform a mounting operation on a target namespace. For example, the request may comprise an action that requires one or more namespaces to be mounted and/or unmounted from another namespace.
At block 704, the computing device determines a set of one or more affected namespaces for the mounting operation. In some embodiments, in addition to the target namespace, the set of one or more affected namespaces includes the target namespace on which the mounting operation is performed, any ancestor namespaces of the target namespace, and when the mounting operation specifies a new parent namespace for the target namespace, the new parent namespace and any ancestor namespaces of the new parent namespace.
At block 706, the computing device attempts to obtain the mount locks for the affected namespaces in the set of affected namespaces.
At decision block 708, it is determined whether the mount locks for the affected namespaces were successfully obtained. If it is determined that the mount locks for the affected namespaces were successfully obtained, processing proceeds to block 710.
At block 710, the computing device performs the mounting operation while holding the mount locks for the set of affected namespaces.
At block 712, the computing device releases the mount locks for the set of affected namespaces.
Returning to decision block 404, if it is determined that the mount locks for the affected namespaces were not successfully obtained, processing proceeds to block 714. At block 714, the requested mounting operation is not performed and the failure to perform the mounting operation is handled. In some embodiments, handling the failure comprises reporting the failure to one or more other components, such as another component of content management system 108 and/or one or more client devices 102-104. In some embodiments, handling the failure comprises salvaging the mounting operation, such as by automatically performing a default legal mounting operation, prompting the user with one or more possible legal mounting operations, and/or determining a compatible mounting operation that will resolve cause of failure and satisfy the constraint.
At block 716, process 700 returns and/or terminates. For example, processing may continue to processing a successive request, passing control to a calling process, generating any appropriate record or notification, returning after a method or function invocation, or terminating.
Example Computing Device
Computing device 800 may include a bus 802 or other communication mechanism for addressing main memory 806 and for transferring data between and among the various components of device 800.
Computing device 800 may also include one or more hardware processors 804 coupled with bus 802 for processing information. A hardware processor 804 may be a general purpose microprocessor, a system on a chip (SoC), or other processor.
Main memory 806, such as a random access memory (RAM) or other dynamic storage device, also may be coupled to bus 802 for storing information and software instructions to be executed by processor(s) 804. Main memory 806 also may be used for storing temporary variables or other intermediate information during execution of software instructions to be executed by processor(s) 804.
Software instructions, when stored in computer-readable media accessible to processor(s) 804, render computing device 800 into a special-purpose computing device that is customized to perform the operations specified in the software instructions. The terms “software”, “software instructions”, “computer program”, “computer-executable instructions”, and “processor-executable instructions” are to be broadly construed to cover any machine-readable information, whether or not human-readable, for instructing a computing device to perform specific operations, and including, but not limited to, application software, desktop applications, scripts, binaries, operating systems, device drivers, boot loaders, shells, utilities, system software, JAVASCRIPT, web pages, web applications, plugins, embedded software, microcode, compilers, debuggers, interpreters, virtual machines, linkers, and text editors.
Computing device 800 also may include read only memory (ROM) 808 or other static storage device coupled to bus 802 for storing static information and software instructions for processor(s) 804.
One or more mass storage devices 810 may be coupled to bus 802 for persistently storing information and software instructions on fixed or removable media, such as magnetic, optical, solid-state, magnetic-optical, flash memory, or any other available mass storage technology. The mass storage may be shared on a network, or it may be dedicated mass storage. Typically, at least one of the mass storage devices 810 (e.g., the main hard disk for the device) stores a body of program and data for directing operation of the computing device, including an operating system, user application programs, driver and other support files, as well as other data files of all sorts.
Computing device 800 may be coupled via bus 802 to display 812, such as a liquid crystal display (LCD) or other electronic visual display, for displaying information to a computer user. In some configurations, a touch sensitive surface incorporating touch detection technology (e.g., resistive, capacitive, etc.) may be overlaid on display 812 to form a touch sensitive display for communicating touch gesture (e.g., finger or stylus) input to processor(s) 804.
An input device 814, including alphanumeric and other keys, may be coupled to bus 802 for communicating information and command selections to processor 804. In addition to or instead of alphanumeric and other keys, input device 814 may include one or more physical buttons or switches such as, for example, a power (on/off) button, a “home” button, volume control buttons, or the like.
Another type of user input device may be a cursor control 816, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 804 and for controlling cursor movement on display 812. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
While in some configurations, such as the configuration depicted in
Functions of the disclosed systems, methods, and modules may be performed by computing device 800 in response to processor(s) 804 executing one or more programs of software instructions contained in main memory 806. Such software instructions may be read into main memory 806 from another storage medium, such as storage device(s) 810. Execution of the software instructions contained in main memory 806 cause processor(s) 804 to perform the functions of the example embodiment(s).
While functions and operations of the example embodiment(s) may be implemented entirely with software instructions, hard-wired or programmable circuitry of computing device 800 (e.g., an ASIC, a FPGA, or the like) may be used in other embodiments in place of or in combination with software instructions to perform the functions, according to the requirements of the particular implementation at hand.
The term “storage media” as used herein refers to any non-transitory media that store data and/or software instructions that cause a computing device to operate in a specific fashion. Such storage media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, non-volatile random access memory (NVRAM), flash memory, optical disks, magnetic disks, or solid-state drives, such as storage device 810. Volatile media includes dynamic memory, such as main memory 806. Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid-state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, flash memory, any other memory chip or cartridge.
Storage media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 802. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
Various forms of media may be involved in carrying one or more sequences of one or more software instructions to processor(s) 804 for execution. For example, the software instructions may initially be carried on a magnetic disk or solid-state drive of a remote computer. The remote computer can load the software instructions into its dynamic memory and send the software instructions over a telephone line using a modem. A modem local to computing device 800 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 802. Bus 802 carries the data to main memory 806, from which processor(s) 804 retrieves and executes the software instructions. The software instructions received by main memory 806 may optionally be stored on storage device(s) 810 either before or after execution by processor(s) 804.
Computing device 800 also may include one or more communication interface(s) 818 coupled to bus 802. A communication interface 818 provides a two-way data communication coupling to a wired or wireless network link 820 that is connected to a local network 822 (e.g., Ethernet network, Wireless Local Area Network, cellular phone network, Bluetooth wireless network, or the like). Communication interface 818 sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information. For example, communication interface 818 may be a wired network interface card, a wireless network interface card with an integrated radio antenna, or a modem (e.g., ISDN, DSL, or cable modem).
Network link(s) 820 typically provide data communication through one or more networks to other data devices. For example, a network link 820 may provide a connection through a local network 822 to a host computer 824 or to data equipment operated by an Internet Service Provider (ISP) 826. ISP 826 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 828. Local network(s) 822 and Internet 828 use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link(s) 820 and through communication interface(s) 818, which carry the digital data to and from computing device 800, are example forms of transmission media.
Computing device 800 can send messages and receive data, including program code, through the network(s), network link(s) 820 and communication interface(s) 818. In the Internet example, a server 830 might transmit a requested code for an application program through Internet 828, ISP 826, local network(s) 822 and communication interface(s) 818.
The received code may be executed by processor 804 as it is received, and/or stored in storage device 810, or other non-volatile storage for later execution.
Example Software System
Software system 900 is provided for directing the operation of computing device 800. Software system 900, which may be stored in system memory (RAM) 806 and on fixed storage (e.g., hard disk or flash memory) 810, includes a kernel or operating system (OS) 910. The OS 910 manages low-level aspects of computer operation, including managing execution of processes, memory allocation, file input and output (I/O), and device I/O. One or more application programs, represented as 902A, 902B, 902C . . . 902N in
Software system 900 includes a graphical user interface (GUI) 915, for receiving user commands and data in a graphical (e.g., “point-and-click” or “touch gesture”) fashion. These inputs, in turn, may be acted upon by the system 900 in accordance with instructions from operating system 910 and/or application(s) 902. The GUI 915 also serves to display the results of operation from the OS 910 and application(s) 902, whereupon the user may supply additional inputs or terminate the session (e.g., log off).
OS 910 can execute directly on the bare hardware 920 (e.g., processor(s) 804) of device 800. Alternatively, a hypervisor or virtual machine monitor (VMM) 930 may be interposed between the bare hardware 920 and the OS 910. In this configuration, VMM 930 acts as a software “cushion” or virtualization layer between the OS 910 and the bare hardware 920 of the device 800.
VMM 930 instantiates and runs one or more virtual machine instances (“guest machines”). Each guest machine comprises a “guest” operating system, such as OS 910, and one or more applications, such as application(s) 902, designed to execute on the guest operating system. The VMM 930 presents the guest operating systems with a virtual operating platform and manages the execution of the guest operating systems.
In some instances, the VMM 930 may allow a guest operating system to run as if it is running on the bare hardware 920 of device 800 directly. In these instances, the same version of the guest operating system configured to execute on the bare hardware 920 directly may also execute on VMM 930 without modification or reconfiguration. In other words, VMM 930 may provide full hardware and CPU virtualization to a guest operating system in some instances.
In other instances, a guest operating system may be specially designed or configured to execute on VMM 930 for efficiency. In these instances, the guest operating system is “aware” that it executes on a virtual machine monitor. In other words, VMM 930 may provide para-virtualization to a guest operating system in some instances.
The above-described basic computer hardware and software is presented for purpose of illustrating the basic underlying computer components that may be employed for implementing the example embodiment(s). The example embodiment(s), however, are not necessarily limited to any particular computing environment or computing device configuration. Instead, the example embodiment(s) may be implemented in any type of system architecture or processing environment that one skilled in the art, in light of this disclosure, would understand as capable of supporting the features and functions of the example embodiment(s) presented herein.
In the foregoing specification, the example embodiment(s) of the present invention have been described with reference to numerous specific details. However, the details may vary from implementation to implementation according to the requirements of the particular implement at hand. The example embodiment(s) are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
This application is a continuation and claims the benefit of U.S. application Ser. No. 16/914,341, filed on Jun. 27, 2020, entitled “NESTED NAMESPACES FOR SELECTIVE CONTENT SHARING,” which is a continuation and claims the benefit of U.S. application Ser. No. 15/891,296, filed on Feb. 7, 2018, entitled “NESTED NAMESPACES FOR SELECTIVE CONTENT SHARING,” which is a continuation and claims the benefit of U.S. application Ser. No. 14/961,067, filed on Dec. 7, 2015, entitled “NESTED NAMESPACES FOR SELECTIVE CONTENT SHARING,” which is a provisional and claims priority to U.S. Provisional Patent Application No. 62/141,577, filed on Apr. 1, 2015, entitled “CLOUD-BASED CONTENT MANAGEMENT SYSTEM PROVIDING SHARED WORKSPACES WITH SELECTIVE CONTENT ITEM SYNCHRONIZATION.” All of which are expressly incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5581765 | Munroe et al. | Dec 1996 | A |
| 5893116 | Simmonds et al. | Apr 1999 | A |
| 5907848 | Zaiken et al. | May 1999 | A |
| 5926821 | Hirose et al. | Jul 1999 | A |
| 6061743 | Thatcher et al. | May 2000 | A |
| 6065018 | Beier et al. | May 2000 | A |
| 6108703 | Leighton et al. | Aug 2000 | A |
| 6336173 | Day, III et al. | Jan 2002 | B1 |
| 6470329 | Livschitz et al. | Oct 2002 | B1 |
| 6473426 | Killian et al. | Oct 2002 | B1 |
| 6560591 | Memmott et al. | May 2003 | B1 |
| 6728723 | Kathail et al. | Apr 2004 | B1 |
| 6834284 | Acker et al. | Dec 2004 | B2 |
| 6915315 | Autrey et al. | Jul 2005 | B2 |
| 7035847 | Brown et al. | Apr 2006 | B2 |
| 7117303 | Zayas et al. | Oct 2006 | B1 |
| 7308545 | Kekre et al. | Dec 2007 | B1 |
| 7318134 | Oliveira et al. | Jan 2008 | B1 |
| 7340723 | Antonov et al. | Mar 2008 | B2 |
| 7401089 | Benton | Jul 2008 | B2 |
| 7437405 | Theis et al. | Oct 2008 | B1 |
| 7512638 | Jhaveri et al. | Mar 2009 | B2 |
| 7558926 | Oliveira et al. | Jul 2009 | B1 |
| 7599941 | Bahar et al. | Oct 2009 | B2 |
| 7685171 | Beaverson et al. | Mar 2010 | B1 |
| 7689510 | Lamkin et al. | Mar 2010 | B2 |
| 7716180 | Vermeulen et al. | May 2010 | B2 |
| 7814499 | Straube et al. | Oct 2010 | B2 |
| 7865571 | Ho et al. | Jan 2011 | B2 |
| 7869425 | Elliott et al. | Jan 2011 | B2 |
| 7870355 | Erofeev et al. | Jan 2011 | B2 |
| 7890646 | Khosravy et al. | Feb 2011 | B2 |
| 7925966 | Kaler | Apr 2011 | B2 |
| 7937686 | Sorensen et al. | May 2011 | B2 |
| 7953785 | Li et al. | May 2011 | B2 |
| 8015491 | Shaver et al. | Sep 2011 | B2 |
| 8019900 | Sekar et al. | Sep 2011 | B1 |
| 8082231 | McDaniel et al. | Dec 2011 | B1 |
| 8112505 | Ben-Shaul et al. | Feb 2012 | B1 |
| 8140473 | Sun et al. | Mar 2012 | B2 |
| 8185601 | Rauhala et al. | May 2012 | B2 |
| 8214747 | Yankovich et al. | Jul 2012 | B1 |
| 8301597 | Zhou et al. | Oct 2012 | B1 |
| 8307028 | Kakivaya | Nov 2012 | B2 |
| 8312046 | Eisler et al. | Nov 2012 | B1 |
| 8341532 | Ryan et al. | Dec 2012 | B2 |
| 8429540 | Yankovich et al. | Apr 2013 | B1 |
| 8458299 | Lin | Jun 2013 | B2 |
| 8484260 | Caso et al. | Jul 2013 | B2 |
| 8503984 | Winbush, III et al. | Aug 2013 | B2 |
| 8527549 | Cidon | Sep 2013 | B2 |
| 8533231 | Aizman et al. | Sep 2013 | B2 |
| 8650159 | Zhang et al. | Feb 2014 | B1 |
| 8656218 | Erofeev et al. | Feb 2014 | B2 |
| 8661428 | Clark et al. | Feb 2014 | B2 |
| 8713106 | Spataro et al. | Apr 2014 | B2 |
| 8775374 | Araki et al. | Jul 2014 | B2 |
| 8805793 | Patiejunas et al. | Aug 2014 | B2 |
| 8819587 | Shrum et al. | Aug 2014 | B1 |
| 8825597 | Houston et al. | Sep 2014 | B1 |
| 8874799 | Derbeko et al. | Oct 2014 | B1 |
| 8880538 | Petersson et al. | Nov 2014 | B1 |
| 8892679 | Destagnol et al. | Nov 2014 | B1 |
| 8930412 | Nelson et al. | Jan 2015 | B2 |
| 8949179 | Besen et al. | Feb 2015 | B2 |
| 8949208 | Xu et al. | Feb 2015 | B1 |
| 8959067 | Patiejunas et al. | Feb 2015 | B1 |
| 8959607 | Yadav et al. | Feb 2015 | B2 |
| 9037556 | Castellano et al. | May 2015 | B2 |
| 9037797 | McGroddy-Goetz et al. | May 2015 | B2 |
| 9043567 | Modukuri et al. | May 2015 | B1 |
| 9183303 | Goel et al. | Nov 2015 | B1 |
| 9185164 | Newhouse | Nov 2015 | B1 |
| 9213709 | Patiejunas et al. | Dec 2015 | B2 |
| 9253166 | Gauda et al. | Feb 2016 | B2 |
| 9282169 | Chang | Mar 2016 | B1 |
| 9286102 | Harel et al. | Mar 2016 | B1 |
| 9294558 | Mncent et al. | Mar 2016 | B1 |
| 9361349 | Newhouse | Jun 2016 | B1 |
| 9384226 | Goel et al. | Jul 2016 | B1 |
| 9479548 | Jensen et al. | Oct 2016 | B2 |
| 9479567 | Koorapati et al. | Oct 2016 | B1 |
| 9479578 | Swanson | Oct 2016 | B1 |
| 9563681 | Patiejunas et al. | Feb 2017 | B1 |
| 9652741 | Goldberg et al. | May 2017 | B2 |
| 9697269 | Koorapati et al. | Jul 2017 | B2 |
| 9727470 | Cande et al. | Aug 2017 | B1 |
| 9773051 | Smith | Sep 2017 | B2 |
| 9817878 | Newhouse | Nov 2017 | B2 |
| 9819740 | Tataroiu et al. | Nov 2017 | B2 |
| 9852147 | Von Muhlen et al. | Dec 2017 | B2 |
| 9852150 | Sharpe et al. | Dec 2017 | B2 |
| 9961149 | Poletto et al. | May 2018 | B2 |
| 10037339 | Kleinpeter | Jul 2018 | B1 |
| 10116732 | Canton et al. | Oct 2018 | B1 |
| 10198452 | Habouzit et al. | Feb 2019 | B2 |
| 10324903 | Goldberg et al. | Jun 2019 | B1 |
| 10685038 | Koorapati et al. | Jun 2020 | B2 |
| 10691718 | Koorapati et al. | Jun 2020 | B2 |
| 10803020 | Desai et al. | Oct 2020 | B1 |
| 20020048174 | Pederson | Apr 2002 | A1 |
| 20020078174 | Sim et al. | Jun 2002 | A1 |
| 20020112058 | Weisman et al. | Aug 2002 | A1 |
| 20020120763 | Miloushev et al. | Aug 2002 | A1 |
| 20020174180 | Brown et al. | Nov 2002 | A1 |
| 20030018878 | Dorward et al. | Jan 2003 | A1 |
| 20040024786 | Anderson et al. | Feb 2004 | A1 |
| 20040034712 | Rajwan et al. | Feb 2004 | A1 |
| 20040064488 | Sinha et al. | Apr 2004 | A1 |
| 20040068523 | Keith et al. | Apr 2004 | A1 |
| 20040133573 | Miloushev et al. | Jul 2004 | A1 |
| 20040133606 | Miloushev et al. | Jul 2004 | A1 |
| 20040133607 | Miloushev et al. | Jul 2004 | A1 |
| 20040133652 | Miloushev et al. | Jul 2004 | A1 |
| 20040162900 | Bucher et al. | Aug 2004 | A1 |
| 20050071336 | Najork et al. | Mar 2005 | A1 |
| 20050091672 | Debique et al. | Apr 2005 | A1 |
| 20050262371 | Luke et al. | Nov 2005 | A1 |
| 20050289237 | Matsubara et al. | Dec 2005 | A1 |
| 20060041844 | Homiller et al. | Feb 2006 | A1 |
| 20060064467 | Libby | Mar 2006 | A1 |
| 20060116985 | Thind | Jun 2006 | A1 |
| 20060117056 | Havewala et al. | Jun 2006 | A1 |
| 20060179083 | Kulkarni et al. | Aug 2006 | A1 |
| 20060206547 | Kulkarni et al. | Sep 2006 | A1 |
| 20060224602 | Rawat | Oct 2006 | A1 |
| 20060235895 | Rodriguez et al. | Oct 2006 | A1 |
| 20060277196 | Oosawa et al. | Dec 2006 | A1 |
| 20070024919 | Wong et al. | Feb 2007 | A1 |
| 20070028215 | Kamath et al. | Feb 2007 | A1 |
| 20070043747 | Benton et al. | Feb 2007 | A1 |
| 20070055703 | Zimran | Mar 2007 | A1 |
| 20070079083 | Gladwin et al. | Apr 2007 | A1 |
| 20070088702 | Fridella et al. | Apr 2007 | A1 |
| 20070100829 | Allen et al. | May 2007 | A1 |
| 20070100913 | Sumner et al. | May 2007 | A1 |
| 20070136308 | Tsirigotis et al. | Jun 2007 | A1 |
| 20070198710 | Gopalakrishnan | Aug 2007 | A1 |
| 20070214497 | Montgomery et al. | Sep 2007 | A1 |
| 20070220220 | Ziv et al. | Sep 2007 | A1 |
| 20070250552 | Lango et al. | Oct 2007 | A1 |
| 20070294366 | Ozzie et al. | Dec 2007 | A1 |
| 20080005195 | Li et al. | Jan 2008 | A1 |
| 20080046218 | Dontcheva et al. | Feb 2008 | A1 |
| 20080141250 | Dorn et al. | Jun 2008 | A1 |
| 20080208870 | Tsang | Aug 2008 | A1 |
| 20080212616 | Augustine et al. | Sep 2008 | A1 |
| 20080267221 | Ozzie et al. | Oct 2008 | A1 |
| 20090030986 | Bates | Jan 2009 | A1 |
| 20090037514 | Lankford et al. | Feb 2009 | A1 |
| 20090055464 | Multer et al. | Feb 2009 | A1 |
| 20090083394 | Diot et al. | Mar 2009 | A1 |
| 20090094252 | Wong et al. | Apr 2009 | A1 |
| 20090125522 | Kodama et al. | May 2009 | A1 |
| 20090138529 | Bellessort et al. | May 2009 | A1 |
| 20090144784 | Li et al. | Jun 2009 | A1 |
| 20090192845 | Gudipaty et al. | Jul 2009 | A1 |
| 20090216745 | Allard et al. | Aug 2009 | A1 |
| 20090222741 | Shaw et al. | Sep 2009 | A1 |
| 20090271412 | Lacapra et al. | Oct 2009 | A1 |
| 20090271502 | Xue et al. | Oct 2009 | A1 |
| 20090271779 | Clark | Oct 2009 | A1 |
| 20090300071 | Arcese et al. | Dec 2009 | A1 |
| 20090313353 | Lou et al. | Dec 2009 | A1 |
| 20090327405 | Fitzgerald et al. | Dec 2009 | A1 |
| 20100011088 | Gautier et al. | Jan 2010 | A1 |
| 20100146569 | Janardhan et al. | Jun 2010 | A1 |
| 20100198944 | Ho et al. | Aug 2010 | A1 |
| 20100241711 | Ansari et al. | Sep 2010 | A1 |
| 20100293147 | Snow et al. | Nov 2010 | A1 |
| 20100332401 | Prahlad et al. | Dec 2010 | A1 |
| 20110153759 | Rathod et al. | Jun 2011 | A1 |
| 20110154431 | Walsh et al. | Jun 2011 | A1 |
| 20110225293 | Rathod et al. | Sep 2011 | A1 |
| 20110258488 | Nightingale et al. | Oct 2011 | A1 |
| 20120084379 | Peng et al. | Apr 2012 | A1 |
| 20120151201 | Clerc et al. | Jun 2012 | A1 |
| 20120197844 | Wang et al. | Aug 2012 | A1 |
| 20120203817 | Hu et al. | Aug 2012 | A1 |
| 20120221520 | Garrett et al. | Aug 2012 | A1 |
| 20120221811 | Sparkes et al. | Aug 2012 | A1 |
| 20120226649 | Kovacs et al. | Sep 2012 | A1 |
| 20130013560 | Goldberg et al. | Jan 2013 | A1 |
| 20130014023 | Lee et al. | Jan 2013 | A1 |
| 20130041872 | Aizman et al. | Feb 2013 | A1 |
| 20130073689 | Kolam et al. | Mar 2013 | A1 |
| 20130080919 | Kiang et al. | Mar 2013 | A1 |
| 20130094445 | De Foy et al. | Apr 2013 | A1 |
| 20130135608 | Payne et al. | May 2013 | A1 |
| 20130138608 | Smith | May 2013 | A1 |
| 20130160072 | Reus et al. | Jun 2013 | A1 |
| 20130191339 | Haden et al. | Jul 2013 | A1 |
| 20130198600 | Lockhart et al. | Aug 2013 | A1 |
| 20130212112 | Blom et al. | Aug 2013 | A1 |
| 20130212484 | Joshi et al. | Aug 2013 | A1 |
| 20130212485 | Yankovich et al. | Aug 2013 | A1 |
| 20130218837 | Bhatnagar et al. | Aug 2013 | A1 |
| 20130227083 | Kim et al. | Aug 2013 | A1 |
| 20130268480 | Dorman | Oct 2013 | A1 |
| 20130275398 | Dorman et al. | Oct 2013 | A1 |
| 20130275509 | Micucci et al. | Oct 2013 | A1 |
| 20130297887 | Woodward et al. | Nov 2013 | A1 |
| 20130318229 | Bakre et al. | Nov 2013 | A1 |
| 20130332418 | Kim | Dec 2013 | A1 |
| 20130339407 | Sharpe et al. | Dec 2013 | A1 |
| 20130346374 | Wolf et al. | Dec 2013 | A1 |
| 20130346557 | Chang et al. | Dec 2013 | A1 |
| 20140025948 | Bestler et al. | Jan 2014 | A1 |
| 20140046906 | Patiejunas et al. | Feb 2014 | A1 |
| 20140047070 | Lee et al. | Feb 2014 | A1 |
| 20140053227 | Ruppin et al. | Feb 2014 | A1 |
| 20140059642 | Deasy et al. | Feb 2014 | A1 |
| 20140074663 | Alsina et al. | Mar 2014 | A1 |
| 20140074783 | Alsina et al. | Mar 2014 | A1 |
| 20140101310 | Savage et al. | Apr 2014 | A1 |
| 20140115115 | Kuang et al. | Apr 2014 | A1 |
| 20140122428 | Zhou et al. | May 2014 | A1 |
| 20140126800 | Lang et al. | May 2014 | A1 |
| 20140143446 | Jacobson et al. | May 2014 | A1 |
| 20140156793 | Chan et al. | Jun 2014 | A1 |
| 20140172783 | Suzuki et al. | Jun 2014 | A1 |
| 20140173027 | Kappes et al. | Jun 2014 | A1 |
| 20140173137 | Jacobson et al. | Jun 2014 | A1 |
| 20140181697 | Kirigin | Jun 2014 | A1 |
| 20140188803 | James et al. | Jul 2014 | A1 |
| 20140195652 | Yerkes | Jul 2014 | A1 |
| 20140208220 | Watal | Jul 2014 | A1 |
| 20140215436 | Deluca et al. | Jul 2014 | A1 |
| 20140215551 | Allain | Jul 2014 | A1 |
| 20140215568 | Kirigin et al. | Jul 2014 | A1 |
| 20140229839 | Lynch et al. | Aug 2014 | A1 |
| 20140250073 | Zalpuri et al. | Sep 2014 | A1 |
| 20140280602 | Quatrano | Sep 2014 | A1 |
| 20140304384 | Varenhorst et al. | Oct 2014 | A1 |
| 20140304618 | Carriero et al. | Oct 2014 | A1 |
| 20140324777 | Novak et al. | Oct 2014 | A1 |
| 20140324945 | Novak et al. | Oct 2014 | A1 |
| 20140330874 | Novak et al. | Nov 2014 | A1 |
| 20140358860 | Wautier et al. | Dec 2014 | A1 |
| 20140359465 | Litan et al. | Dec 2014 | A1 |
| 20140365432 | Jain | Dec 2014 | A1 |
| 20140379586 | Sawyer | Dec 2014 | A1 |
| 20150006146 | Wilkes et al. | Jan 2015 | A1 |
| 20150006475 | Guo et al. | Jan 2015 | A1 |
| 20150019432 | Burns et al. | Jan 2015 | A1 |
| 20150046557 | Rosenberg | Feb 2015 | A1 |
| 20150052392 | Mickens et al. | Feb 2015 | A1 |
| 20150058932 | Faitelson | Feb 2015 | A1 |
| 20150082198 | Destagnol et al. | Mar 2015 | A1 |
| 20150113222 | Naik et al. | Apr 2015 | A1 |
| 20150134808 | Fushman | May 2015 | A1 |
| 20150142742 | Hong | May 2015 | A1 |
| 20150161016 | Bulkowski et al. | Jun 2015 | A1 |
| 20150180948 | Shao | Jun 2015 | A1 |
| 20150186395 | Yan et al. | Jul 2015 | A1 |
| 20150207844 | Tataroiu et al. | Jul 2015 | A1 |
| 20150227757 | Bestler et al. | Aug 2015 | A1 |
| 20150249647 | Mityagin et al. | Sep 2015 | A1 |
| 20150254320 | Cowling et al. | Sep 2015 | A1 |
| 20150278884 | Manzari et al. | Oct 2015 | A1 |
| 20150288754 | Mosko et al. | Oct 2015 | A1 |
| 20150288755 | Mosko et al. | Oct 2015 | A1 |
| 20150347552 | Habouzit et al. | Dec 2015 | A1 |
| 20150347553 | Aizman et al. | Dec 2015 | A1 |
| 20150358373 | Famaey et al. | Dec 2015 | A1 |
| 20160006646 | Lin et al. | Jan 2016 | A1 |
| 20160021172 | Mahadevan et al. | Jan 2016 | A1 |
| 20160044126 | Mahadevan et al. | Feb 2016 | A1 |
| 20160050177 | Cue et al. | Feb 2016 | A1 |
| 20160055248 | Goel et al. | Feb 2016 | A1 |
| 20160057217 | Beaverson et al. | Feb 2016 | A1 |
| 20160062963 | Umapathy | Mar 2016 | A1 |
| 20160078068 | Agrawal et al. | Mar 2016 | A1 |
| 20160087931 | Kim et al. | Mar 2016 | A1 |
| 20160092443 | Hayes et al. | Mar 2016 | A1 |
| 20160127855 | Zhang | May 2016 | A1 |
| 20160164761 | Sathyanarayana et al. | Jun 2016 | A1 |
| 20160217387 | Okanohara et al. | Jul 2016 | A1 |
| 20160226970 | Newhouse et al. | Aug 2016 | A1 |
| 20160267103 | Slik et al. | Sep 2016 | A1 |
| 20160292179 | Von Muhlen et al. | Oct 2016 | A1 |
| 20160292443 | von Muhlen | Oct 2016 | A1 |
| 20160313934 | Isherwood et al. | Oct 2016 | A1 |
| 20160321338 | Isherwood et al. | Nov 2016 | A1 |
| 20170024166 | Singh | Jan 2017 | A1 |
| 20170109370 | Newhouse | Apr 2017 | A1 |
| 20170124111 | Sharma et al. | May 2017 | A1 |
| 20170124170 | Koorapati et al. | May 2017 | A1 |
| 20170126782 | Koorapati et al. | May 2017 | A1 |
| 20170126800 | Koorapati et al. | May 2017 | A1 |
| 20170126802 | Koorapati et al. | May 2017 | A1 |
| 20170177332 | Deluca et al. | Jun 2017 | A1 |
| 20170195417 | Brand | Jul 2017 | A1 |
| 20170208125 | Jai et al. | Jul 2017 | A1 |
| 20170222865 | Koorapati et al. | Aug 2017 | A1 |
| 20170255687 | Koorapati et al. | Sep 2017 | A1 |
| 20180048687 | Bryant et al. | Feb 2018 | A1 |
| 20180060410 | Stading et al. | Mar 2018 | A1 |
| 20200293548 | Koorapati et al. | Sep 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 1517260 | Mar 2005 | EP |
| 2924244 | May 2009 | FR |
| H0816444 | Jan 1996 | JP |
| 2003030026 | Jan 2003 | JP |
| 2005011354 | Jan 2005 | JP |
| 2005141475 | Jun 2005 | JP |
| 2008538843 | Nov 2008 | JP |
| 2008305221 | Dec 2008 | JP |
| 2010074604 | Apr 2010 | JP |
| 2012079042 | Apr 2012 | JP |
| 2012079043 | Apr 2012 | JP |
| 2012093911 | May 2012 | JP |
| 2012513632 | Jun 2012 | JP |
| 2012182292 | Sep 2012 | JP |
| 2013182292 | Sep 2013 | JP |
| 2014038569 | Feb 2014 | JP |
| 2015505627 | Feb 2015 | JP |
| 2015058627 | Mar 2015 | JP |
| 6309969 | Apr 2018 | JP |
| 2005060387 | Apr 2009 | WO |
| 2009124014 | Oct 2009 | WO |
| 2010073110 | Jul 2010 | WO |
| 2014099044 | Jun 2014 | WO |
| 2015031755 | Mar 2015 | WO |
| 2015153045 | Oct 2015 | WO |
| Entry |
|---|
| Office action for European Application No. 20152072.3 mailed on Mar. 25, 2024, 4 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,365, mailed Jan. 23, 2020, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,365, mailed Nov. 8, 2019, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 15/891,296, mailed Apr. 29, 2020, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 15/984,968, mailed Dec. 15, 2020, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/984,968, mailed Mar. 3, 2021, 5 pages. |
| Notice of Allowance from U.S. Appl. No. 16/888,362, mailed Aug. 20, 2021, 16 pages. |
| Notice of Allowance from U.S. Appl. No. 16/914,341, mailed Nov. 14, 2022, 09 pages. |
| Notice of Allowancefor U.S. Appl. No. 15/010,220 malled on Feb. 22, 2018, 9 pages. |
| Office Action for U.S. Appl. No. 14/961,067 mailed on July 7, 2017, 13 pages. |
| Office Action for U.S. Appl. No. 14/979,226 mailed on Jun. 16, 2016, 8 pages. |
| Office Action for U.S. Appl. No. 14/979,226 mailed on Mar. 23, 2017, 10 pages. |
| Office Action for U.S. Appl. No. 14/979,226 mailed on Nov. 16, 2016, 10 pages. |
| Office Action for U.S. Appl. No. 14/979,252 mailed on May 23, 2016, 17 pages. |
| Office Action for U.S. Appl. No. 14/979,252 mailed on Oct. 26, 2017, 24 pages. |
| Office Action for U.S. Appl. No. 14/979,252 mailed onDecember 14, 2018, 30 pages. |
| Office Action for U.S. Appl. No. 14/979,256 mailed on May 4, 2016, 11 pages. |
| Office Action for U.S. Appl. No. 14/979,268 mailed on May 18, 2016, 20 pages. |
| Office Action for U.S. Appl. No. 15/010,220 mailed on Oct. 25, 2016, 15 pages. |
| Office Action for U.S. Appl. No. 15/010,220 mailed on Sep. 28, 2017, 24 pages. |
| Office Action for U.S. Appl. No. 15/010,235 mailed on May 12, 2016, 11 pages. |
| Office Action for U.S. Appl. No. 15/332,782 mailed on Oct. 5, 2018, 39 pages. |
| Office Action for U.S. Appl. No. 15/355,286 mailed on Mar. 19, 2019, 17 pages. |
| Office Action for U.S. Appl. No. 15/355,305 mailed on May 22, 2017, 11 pages. |
| Office Action for U.S. Appl. No. 15/603,193 malled on Sepetember 11, 2017, 11 pages. |
| Office Action for U.S. Appl. No. 15/870,365 mailed on Jul. 25, 2019, 14 pages. |
| Provision of the minutes in accordance with Rule 124(4) EPC for European application No. 16791146.0 mailed on Feb. 1, 2021, 4 pages. |
| Search Report for Japanese Application No. 2017-550811 dated Dec. 20, 2018, 6 pages. |
| Search Report for Japanese Application No. 2017-550817 dated Dec. 25, 2018, 8 pages. |
| Second Examination Report for Australian Application No. 2016243644 dated Dec. 18, 2018, 4 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for EP Application No. 16791146.0 dated Jan. 13, 2020, 13 pages. |
| Summons to attend oral proceedings pursuant to Rule 115(1) EPC for European Application No. 17703601.9 mailed on May 28, 2021, 11 pages. |
| Syncovery, “Syncovery: Blocking Level Copying,” downloaded from www.synovery.com/block-level-copying/ on May 22, 2014, 2 pages. |
| Tridgell A., et al., “TR-CS-96-05 The Rsync Algorithm,” Jun. 1996, 8 pages. |
| White T., “Chapter 3: The Hadoop Distributed Filesystem,” Hadoop—The Definitive Guide, 4th Edition, Apr. 17, 2015, pp. 43-78. |
| Zhu Z., et al., “Let's ChronoSync: Decentralized Dataset State Synchronization in Named Data Networking,” 21st IEEE International Conference on Network Protocols (ICNP), 2013, 10 pages. |
| Final Office Action for U.S. Appl. No. 15/603,193 mailed on Jan. 29, 2018, 21 pages. |
| Final Office Action from U.S. Appl. No. 15/332,782, mailed Jan. 22, 2020, 20 pages. |
| Final Office Action from U.S. Appl. No. 15/984,968, mailed Feb. 3, 2020, 20 pages. |
| Final Office Action from U.S. Appl. No. 15/984,968, mailed Sep. 8, 2020, 24 pages. |
| First Examination Report for Australian Application No. 2016346892 dated Jan. 21, 2019, 3 pages. |
| First Office Action for Japanese Application No. 2018-504709 dated May 31, 2019, 12 pages. |
| Freeplant et al., “Comments from Freeplant,” Support for Multiple Servers/Mirrors, X055738599, retrieved from https://github.com/haiwen/seafile/issues/110#issuecomment-13728419, Feb. 18, 2013, 13 pages. |
| Ganzha M., et al., “Identifier Management in Semantic Interoperability Solutions for IoT,” IEEE International Conference on Communications Workshops, Jul. 12, 2018, downloaded from the Internet: https://www.researchgate.net/publication/326218197_Identifier_Management_in_Semantic_Interoperabilit . . . , 7 pages. |
| Griffith-Jones G., “Log file,” Wikipedia, XP055701533, Aug. 21, 2015, Retrieved from https://en.wikipedia.org/w/index.php?title=Log_file&oldid=677169702on Jun. 5, 2020, 3 pages. |
| Hendrickson M., “Dropbox: The Online Storage Solution We've Been Waiting for?,” TechCrunch.com, Mar. 11, 2008, Downloaded from https://techcrunch.com/2008/03/11/dropbox-the-online-storage-solution-wev-e-been-waiting-for/, 6 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/025014, dated Jul. 14, 2016, 11 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/025015, dated Jun. 16, 2016, 11 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/056344, dated Feb. 28, 2017, 22 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/056345, dated Feb. 28, 2017, 20 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2016/056346, dated Jan. 5, 2017, 11 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2017/014945, dated Mar. 14, 2017, 11 pages. |
| International Search Report and Written Opinionfor PCT Application No. PCT/US2016/0056349, dated Jan. 18, 2017, 12 pages. |
| International Search Report for PCT Application No. PCT/US2016/056348, dated Jan. 19, 2007, 14 pages. |
| Interview Summary for U.S. Appl. No. 14/961,067 malled on Oct. 11, 2017, 2 pages. |
| Interview summary for U.S. Appl. No. 14/979,252 mailed on Aug. 27, 2019, 3 Pages. |
| Interview Summary for U.S. Appl. No. 14/979,252 mailed on Mar. 15, 2019, 4 pages. |
| Interview Summary for U.S. Appl. No. 15/332,782 mailed on Oct. 23, 2019, 3 pages. |
| Jia A.L., et al., “Designs and Evaluation of a Tracker in P2P Networks”, Peer-to-Peer Computing , 2008, P2P'08, Eighth International Conference on IEEE, Piscataway, NJ, USA, ISBN 978-0-7695-3318-6, Sep. 8, 2008, pp. 227-230. |
| Koorapati N., “Streaming File Synchronization,” Dropbox Tech Blog, Jul. 11, 2014, 14 pages. |
| Lefebvre R., “Mastering iCloud on Your Mac: Use IClouDrive to Access Your Files Like Dropbox [OS X Tips],” Posted on Mar. 28, 2013 at Cult of Mac, retrieved on Oct. 17, 2016, 3 pages. |
| Li B., “Simplifying Data Management: NFS access to HDFS,” Hortonworks, May 13, 2013, retrieved from http://hortonworks.com/blog/simplifying-data-management-nfs-access-to-hdfs/, 13 pages. |
| Nikkei Business Publications Inc., “One Device for on the Go or at Home! Evolution of the Notebook PC, Windows Tablet Complete Strategy, PC Cooperation Volume: Simple File Sharing Via Cloud”, Nikkei PC21,Aug. 24, 2014, vol. 19(14), pp. 30-35 (11 pages). |
| Non-Final Office Action from U.S. Appl. No. 15/870,365, mailed Apr. 15, 2020, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/891,296, mailed Jan. 16, 2020, 12 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/984,968, mailed May 20, 2020, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/984,968, mailed Oct. 3, 2019, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/702,648, mailed Jul. 9, 2020, 10 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/914,341, mailed Sep. 7, 2022, 15 pages. |
| Notice of Acceptance for Australian Application No. 2016242857 dated Dec. 18, 2018, 3 pages. |
| Notice of Allowance for U.S. Appl. No. 14/961,067 mailed on Nov. 6, 2017, 10 pages. |
| Notice of Allowance for U.S. Appl. No. 14/979,234 mailed on Jun. 13, 2016, 14 pages. |
| Notice of Allowance for U.S. Appl. No. 14/979,256 mailed on Aug. 5, 2016, 8 pages. |
| Notice of Allowance for U.S. Appl. No. 14/979,268 mailed on Mar. 23, 2017, 9 pages. |
| Notice of Allowance for U.S. Appl. No. 15/010,235 mailed on Aug. 30, 2016, 7 pages. |
| Notice of Allowance for U.S. Appl. No. 15/355,305 mailed on Sep. 22, 2017, 5 pages. |
| Notice of Allowance for U.S. Appl. No. 15/603,193 malled on Jul. 10, 2018, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 14/979,252, mailed Apr. 2, 2020, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 14/979,252, mailed Apr. 24, 2020, 3 pages. |
| Notice of Allowance from U.S. Appl. No. 14/979,252, mailed Dec. 11, 2019, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 14/979,252, mailed May 19, 2020, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/332,782, mailed Apr. 6, 2020, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 15/332,782, mailed Apr. 29, 2020, 13 pages. |
| Notice of Allowance from U.S. Appl. No. 15/355,286, mailed Jan. 15, 2020, 5 pages. |
| Notice of Allowance from U.S. Appl. No. 15/355,286, mailed Jul. 8, 2020, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,365, mailed Aug. 17, 2020, 12 pages. |
| Australian Claims in application No. 2016346892, dated Jan. 2019, 9 pages. |
| Barr, J., “Amazon S3: Multipart Upload,” Nov. 10, 2010, Retrieved from https://aws.amazon.com/blogs/aws/amazon-s3-multipart-upload/ on Feb. 3, 2015, 3 pages. |
| Bonadea, et al., “Cloud Storage,” Wikipedia, Oct. 28, 2015, downloaded from https://en.wikipedia.org/w/index.php?title=Cloud_storage&oldid=687899972 on Dec. 20, 2016, 5 pages. |
| Brim M., “Control and Inspection of Distributed Process Groups at Extreme Scale via Group File Semantics,” ProQuest Dissertations Publishing, 2012, Dissertation/thesis No. 3508182, 202 pages. |
| Camacho H.E., et al., “A Cloud Environment for Backup and Data Storage”, International Conference on Electronics, Communications and Computers (CONIELECOMP), 2014, 7 pages. |
| Claims for Japanese Application No. 2017-550811 dated Dec. 2018, 4 pages. |
| Claims for Japanese Application No. 2017-550817 dated Dec. 2018, 4 pages. |
| Claims for Japanese Application No. 2018-504709 dated May 2019, 9 pages. |
| Claims in AustralianApplication No. 2016242857, dated Dec. 2018, 4 pages. |
| Claims inAustralianApplication No. 2016243644, dated Dec. 2018, 4 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 16791147.8 mailed on Nov. 28, 2019, 4 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 17703601.9 mailed on Mar. 4, 2020, 8 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 20152072.3 mailed on Oct. 1, 2021, 9 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 20197908.5, mailed on Nov. 14, 2022, 13 pages. |
| Communication Pursuant to Article 94(3) for EP Application No. 16715433.5 dated Oct. 9, 2019, 6 pages. |
| Communication Pursuant to Article 94(3) for EP Application No. 16791147.8 dated Feb. 18, 2019, 5 pages. |
| Communication under rule 71(3) EPC for European Application No. 16715433.5 mailed on Jan. 12, 2021, 42 pages. |
| Communication under rule 71(3) EPC for European Application No. 16715433.5 mailed on Jul. 20, 2020, 42 pages. |
| Communication under rule 71(3) EPC Intention to Grant for European Application No. 16791147.8 mailed on Apr. 30, 2020, 7 pages. |
| Communication under rule 71(3) EPC Intention to Grant for European Application No. 16791148.6 mailed on Nov. 12, 2020, 7 pages. |
| Communication under Rule 71(3) EPC of Intention to Grant for European Application No. 16790778.1 mailed on May 4, 2020, 7 pages. |
| Communication under Rule 71(3) EPC of Intention to Grant for European Application No. 16790778.1 mailed on Oct. 2, 2020, 7 pages. |
| Communication under Rule 71(3) EPC of Intention to Grant for European Application No. 16791148.6 mailed on May 11, 2020, 7 pages. |
| Result of consultation for European Application No. 16715433.5 malled on May 28, 2020, 3 pages. |
| Result of Consultation for European Application No. 16791146.0 mailed on Nov. 6, 2020, 10 pages. |
| Current Claims in PCT Application No. PCT /US2016/0056349, dated Jan. 2017, 3 pages. |
| Current Claims in PCT Application No. PCT/US2016/056348, dated Jan. 2017, 4 pages. |
| Decision to refuse European Patent Application No. 17703601.9 mailed on Oct. 10, 2022, 13 pages. |
| Decision to refuse European Patent Application No. 16791146.0 mailed on Feb. 4, 2021, 31 pages. |
| Dee M., “Inside LAN Sync”, DropBox Tech Blog, Oct. 13, 2015, 9 pages. |
| Drago I., et al., “Inside Dropbox: Understanding Personal Cloud Storage Services,” Proceedings of the 2012 ACM Conference on Internet Measurement Conference, IMC, XP055131706, Nov. 14, 2012, vol. 16, 14 pages. |
| “Dropbox Screenshot,” Publically available Jul. 3, 2013, retrieved from http://www.filewin.net/Dropbox/] via Internet Archive on Oct. 17, 2016, 2 pages. |
| European Claims in application No. 16791146.0, dated Dec. 2018, 4 pages. |
| European Claims in application No. 16791147.8, dated Feb. 2019, 5 pages. |
| European Claims in PCT Application No. PCT/US2016/025014, dated Jul. 2016, 7 pages. |
| European Claims in PCT Application No. PCT/US2016/025015, dated Jun. 2016, 6 pages. |
| European Claims in PCT Application No. PCT/US2016/056344, dated Feb. 2017, 4 pages. |
| European Claims in PCT Application No. PCT/US2016/056345, dated Feb. 2017, 6 pages. |
| European Claims in PCT Application No. PCT/US2016/056346, dated Jan. 2017, 9 pages. |
| European Claims in PCT Application No. PCT/US2017/014945, dated Mar. 2017, 4 pages. |
| European Search Report for EP Application No. 16791146.0 dated Dec. 7, 2013, 15 pages. |
| Extended European Search Report for EP Application No. 20152072.3 dated Jun. 16, 2020, 11 pages. |
| Extended European Search Report for European Application No. 20197908.5 dated Oct. 30, 2020, 11 pages. |
| Final Office Action for U.S. Appl. No. 14/979,252 mailed on Jul. 1, 2019, 24 pages. |
| Final Office Action for U.S. Appl. No. 14/979,252 mailed on May 3, 2018, 27 pages. |
| Final Office Action for U.S. Appl. No. 14/979,252 malled on Nov. 21, 2016, 22 pages. |
| Final Office Action for U.S. Appl. No. 14/979,268 malled on Nov. 18, 2016, 15 pages. |
| Final Office Action for U.S. Appl. No. 15/010,220 mailed on Feb. 22, 2017, 22 pages. |
| Final Office Action for U.S. Appl. No. 15/332,782 malled on Feb. 7, 2019, 28 pages. |
| Final Office Action for U.S. Appl. No. 15/355,286 malled on Aug. 29, 2019, 12 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 20152072.3 mailed on Aug. 31, 2023, 13 pages. |
| Communication under Rule 71 (3) EPC of Intention to Grant for European Application No. 20152072.3 mailed on Apr. 19, 2024, 95 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 20197908.5 mailed on Apr. 26, 2024, 10 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230185946 A1 | Jun 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62141577 | Apr 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16914341 | Jun 2020 | US |
| Child | 18107194 | US | |
| Parent | 15891296 | Feb 2018 | US |
| Child | 16914341 | US | |
| Parent | 14961067 | Dec 2015 | US |
| Child | 15891296 | US |
