Patent Grant
12135733
The present technology pertains to distributed storage, collaboration and synchronization systems.
Cloud storage systems allow users to store and access data on the cloud. Some cloud storage systems allow users to share data with other users and access the data in a collaborative fashion. In some cases, users may also store and access local copies of the data on their client devices. The local copies of the data may provide users with faster access to the data. Additionally, the local copies can allow the user to access the data when the user is offline. Cloud storage systems may also allow users to synchronize their local copies of the data with the data on the cloud to ensure consistency. Cloud storage systems may attempt to synchronize copies of data across a number of client devices and servers so each copy of data is identical. However, synchronization of data across multiple devices can be an extremely difficult task, often resulting in undesirable loss of data and inconsistencies.
The above-recited and other advantages and features of the present technology will become apparent by reference to specific implementations illustrated in the appended drawings. A person of ordinary skill in the art will understand that these drawings only show some examples of the present technology and would not limit the scope of the present technology to these examples. Furthermore, the skilled artisan will appreciate the principles of the present technology as described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Various examples of the present technology are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the present technology.
Cloud storage systems allow users to store and access content items across multiple devices. The content items may include, but are not limited to, files, documents, messages (e.g., email messages or text messages), media files (e.g., photos, videos, and audio files), folders, or any other unit of content. Content items may be shared with multiple users, edited, deleted, added, renamed, or moved. However, synchronizing content items shared or stored across several devices and user accounts has remained flawed and rife with technical obstacles.
To illustrate, a first machine (e.g., a client device or server) may send communications to a second machine that provides information about how a user's modification of content items on a cloud storage system. These communications may be used by the second machine to synchronize the content items on the second machine such that actions performed on content items on the first machine are reflected in content items on the second machine, and the content items on the first machine are substantially identical to the content items on the second machine.
However, in many cases, there may be several communications sent between the various machines, which may be difficult to manage. Moreover, some of the communications may be received out of order as a result of various issues, such as client or network problems. This often results in conflicts and errors between content items at the various machines. The user's activity may also generate a large number of revisions which can further complicate synchronization efforts and exacerbate inconsistencies. For example, a user may perform a large number of modifications to various content items, undo modifications in a short period of time, or quickly perform additional modifications to a previously modified content item. This increases the likelihood that changes and revisions from users are received out of order, causing outdated modifications and conflicting content items. As a result, some operations may not be compatible with the current state of the content items. Moreover, it can be extremely difficult to detect whether operations are in conflict.
There is also an inherent latency with synchronization actions. For example, actions taken on the first machine are first detected by the first machine, and a communication is then generated and transmitted through a network. The communication is received by the second machine which may still be processing previous communications, and actions detailed in the communications may be taken at the second machine. In this illustrative scenario, there are several possible points of latency, including the first machine, the second machine, and the network. As latency increases, the likelihood of conflicts between content items also increases. Processing such conflicted communications and resolving conflicts are extremely difficult and computationally expensive tasks.
Further complexity is introduced when the same or different user on the second machine or other machines with access to the content items make modifications to the content items. Additional technical issues arise when content items are modified locally and remotely in a large collaboration environment. As illustrated here, these issues can quickly multiply and grow in complexity, creating a wide array of problems and inconsistencies in the content items.
Content Management System
In some embodiments the disclosed technology is deployed in the context of a content management system having content item synchronization capabilities and collaboration features, among others. An example system configuration 100 is shown in
Accounts
Content management system 110 can store content items in association with accounts, as well as perform a variety of content item management tasks, such as retrieve, modify, browse, and/or share the content item(s). Furthermore, content management system 110 can enable an account to access content item(s) from multiple client devices.
Content management system 110 supports a plurality of accounts. An entity (user, group of users, team, company, etc.) can create an account with content management system, and account details can be stored in account database 140. Account database 140 can store profile information for registered entities. In some cases, profile information for registered entities includes a username and/or email address. Account database 140 can include account management information, such as account type (e.g. various tiers of free or paid accounts), storage space allocated, storage space used, client devices 150 having a registered content management client application 152 resident thereon, security settings, personal configuration settings, etc.
Account database 140 can store groups of accounts associated with an entity. Groups can have permissions based on group policies and/or access control lists, and members of the groups can inherit the permissions. For example, a marketing group can have access to one set of content items while an engineering group can have access to another set of content items. An administrator group can modify groups, modify user accounts, etc.
Content Item Storage
A feature of content management system 110 is the storage of content items, which can be stored in content storage 142. Content items can be any digital data such as documents, collaboration content items, text files, audio files, image files, video files, webpages, executable files, binary files, etc. A content item can also include collections or other mechanisms for grouping content items together with different behaviors, such as folders, zip files, playlists, albums, etc. A collection can refer to a folder, or a plurality of content items that are related or grouped by a common attribute. In some embodiments, content storage 142 is combined with other types of storage or databases to handle specific functions. Content storage 142 can store content items, while metadata regarding the content items can be stored in metadata database 146. Likewise, data regarding where a content item is stored in content storage 142 can be stored in content directory 144. Additionally, data regarding changes, access, etc. can be stored in server file journal 148. Each of the various storages/databases such as content storage 142, content directory 144, server file journal 148, and metadata database 146 can be comprised of more than one such storage or database and can be distributed over many devices and locations. Other configurations are also possible. For example, data from content storage 142, content directory 144, server file journal 148, and/or metadata database 146 may be combined into one or more content storages or databases or further segmented into additional content storages or databases. Thus, content management system 110 may include more or less storages and/or databases than shown in
In some embodiments, content storage 142 is associated with at least one content storage service 116, which includes software or other processor executable instructions for managing the storage of content items including, but not limited to, receiving content items for storage, preparing content items for storage, selecting a storage location for the content item, retrieving content items from storage, etc. In some embodiments, content storage service 116 can divide a content item into smaller chunks for storage at content storage 142. The location of each chunk making up a content item can be recorded in content directory 144. Content directory 144 can include a content entry for each content item stored in content storage 142. The content entry can be associated with a unique ID, which identifies a content item.
In some embodiments, the unique ID, which identifies a content item in content directory 144, can be derived from a deterministic hash function. This method of deriving a unique ID for a content item can ensure that content item duplicates are recognized as such since the deterministic hash function will output the same identifier for every copy of the same content item, but will output a different identifier for a different content item. Using this methodology, content storage service 116 can output a unique ID for each content item.
Content storage service 116 can also designate or record a content path for a content item in metadata database 146. The content path can include the name of the content item and/or folder hierarchy associated with the content item. For example, the content path can include a folder or path of folders in which the content item is stored in a local file system on a client device. While content items are stored in content storage 142 in blocks and may not be stored under a tree like directory structure, such directory structure is a comfortable navigation structure for users. Content storage service 116 can define or record a content path for a content item wherein the “root” node of a directory structure can be a namespace for each account. Within the namespace can be a directory structure defined by a user of an account and/or content storage service 116. Metadata database 146 can store the content path for each content item as part of a content entry.
In some embodiments the namespace can include additional namespaces nested in the directory structure as if they are stored within the root node. This can occur when an account has access to a shared collection. Shared collections can be assigned their own namespace within content management system 110. While some shared collections are actually a root node for the shared collection, they are located subordinate to the account namespace in the directory structure, and can appear as a folder within a folder for the account. As addressed above, the directory structure is merely a comfortable navigation structure for users, but does not correlate to storage locations of content items in content storage 142.
While the directory structure in which an account views content items does not correlate to storage locations at content management system 110, the directory structure can correlate to storage locations on client device 150 depending on the file system used by client device 150.
As addressed above, a content entry in content directory 144 can also include the location of each chunk making up a content item. More specifically, the content entry can include content pointers that identify the location in content storage 142 of the chunks that make up the content item.
In addition to a content path and content pointer, a content entry in content directory 144 can also include a user account identifier that identifies the user account that has access to the content item and/or a group identifier that identifies a group with access to the content item and/or a namespace to which the content entry belongs.
Content storage service 116 can decrease the amount of storage space required by identifying duplicate content items or duplicate blocks that make up a content item or versions of a content item. Instead of storing multiple copies, content storage 142 can store a single copy of the content item or block of the content item and content directory 144 can include a pointer or other mechanism to link the duplicates to the single copy.
Content storage service 116 can also store metadata describing content items, content item types, folders, file path, and/or the relationship of content items to various accounts, collections, or groups in metadata database 146, in association with the unique ID of the content item.
Content storage service 116 can also store a log of data regarding changes, access, etc. in server file journal 148. Server file journal 148 can include the unique ID of the content item and a description of the change or access action along with a time stamp or version number and any other relevant data. Server file journal 148 can also include pointers to blocks affected by the change or content item access. Content storage service can provide the ability to undo operations, by using a content item version control that tracks changes to content items, different versions of content items (including diverging version trees), and a change history that can be acquired from the server file journal 148.
Content Item Synchronization
Another feature of content management system 110 is synchronization of content items with at least one client device 150. Client device(s) can take different forms and have different capabilities. For example, client device 1501 is a computing device having a local file system accessible by multiple applications resident thereon. Client device 1502 is a computing device wherein content items are only accessible to a specific application or by permission given by the specific application, and the content items are typically stored either in an application specific space or in the cloud. Client device 1503 is any client device accessing content management system 110 via a web browser and accessing content items via a web interface. While example client devices 1501, 1502, and 1503 are depicted in form factors such as a laptop, mobile device, or web browser, it should be understood that the descriptions thereof are not limited to devices of these example form factors. For example a mobile device such as client 1502 might have a local file system accessible by multiple applications resident thereon, or client 1502 might access content management system 110 via a web browser. As such, the form factor should not be considered limiting when considering client 150's capabilities. One or more functions described herein with respect to client device 150 may or may not be available on every client device depending on the specific capabilities of the device—the file access model being one such capability.
In many embodiments, client devices are associated with an account of content management system 110, but in some embodiments client devices can access content using shared links and do not require an account.
As noted above, some client devices can access content management system 110 using a web browser. However, client devices can also access content management system 110 using client application 152 stored and running on client device 150. Client application 152 can include a client synchronization service 156.
Client synchronization service 156 can be in communication with server synchronization service 112 to synchronize changes to content items between client device 150 and content management system 110.
Client device 150 can synchronize content with content management system 110 via client synchronization service 156. The synchronization can be platform agnostic. That is, content can be synchronized across multiple client devices of varying type, capabilities, operating systems, etc. Client synchronization service 156 can synchronize any changes (new, deleted, modified, copied, or moved content items) to content items in a designated location of a file system of client device 150.
Content items can be synchronized from client device 150 to content management system 110, and vice versa. In embodiments wherein synchronization is from client device 150 to content management system 110, a user can manipulate content items directly from the file system of client device 150, while client synchronization service 156 can monitor directory on client device 150 for changes to files within the monitored folders.
When client synchronization service 156 detects a write, move, copy, or delete of content in a directory that it monitors, client synchronization service 156 can synchronize the changes to content management system service 116. In some embodiments, client synchronization service 156 can perform some functions of content management system service 116 including functions addressed above such as dividing the content item into blocks, hashing the content item to generate a unique identifier, etc. Client synchronization service 156 can index content within client storage index 164 and save the result in storage index 164. Indexing can include storing paths plus a unique server identifier, and a unique client identifier for each content item. In some embodiments, client synchronization service 156 learns the unique server identifier from server synchronization service 112, and learns the unique client identifier from the operating system of client device 150.
Client synchronization service 156 can use storage index 164 to facilitate the synchronization of at least a portion of the content within client storage with content associated with a user account on content management system 110. For example, client synchronization service 156 can compare storage index 164 with content management system 110 and detect differences between content on client storage and content associated with a user account on content management system 110. Client synchronization service 156 can then attempt to reconcile differences by uploading, downloading, modifying, and deleting content on client storage as appropriate. Content storage service 116 can store the changed or new block for the content item and update server file journal 148, metadata database 146, content directory 144, content storage 142, account database 140, etc. as appropriate.
When synchronizing from content management system 110 to client device 150, a mount, modification, addition, deletion, move of a content item recorded in server file journal 148 can trigger a notification to be sent to client device 150 using notification service 117. When client device 150 is informed of the change a request changes listed in server file journal 148 since the last synchronization point known to the client device. When client device 150 determines that it is out of synchronization with content management system 110, client synchronization service 156 requests content item blocks including the changes, and updates its local copy of the changed content items.
In some embodiments, storage index 164 stores tree data structures wherein one tree reflects the latest representation of a directory according to server synchronization service 112, while another tree reflects the latest representation of the directory according to client synchronization service 156. Client synchronization service can work to ensure that the tree structures match by requesting data from server synchronization service 112 or committing changes on client device 150 to content management system 110.
Sometimes client device 150 might not have a network connection available. In this scenario, client synchronization service 156 can monitor the linked collection for content item changes and queue those changes for later synchronization to content management system 110 when a network connection is available. Similarly, a user can manually start, stop, pause, or resume synchronization with content management system 110.
Client synchronization service 156 can synchronize all content associated with a particular user account on content management system 110. Alternatively, client synchronization service 156 can selectively synchronize a portion of the content of the total content associated with the particular user account on content management system 110. Selectively synchronizing only a portion of the content can preserve space on client device 150 and save bandwidth.
In some embodiments, client synchronization service 156 selectively stores a portion of the content associated with the particular user account and stores placeholder content items in client storage for the remainder portion of the content. For example, client synchronization service 156 can store a placeholder content item that has the same filename, path, extension, metadata, of its respective complete content item on content management system 110, but lacking the data of the complete content item. The placeholder content item can be a few bytes or less in size while the respective complete content item might be significantly larger. After client device 150 attempts to access the content item, client synchronization service 156 can retrieve the data of the content item from content management system 110 and provide the complete content item to accessing client device 150. This approach can provide significant space and bandwidth savings while still providing full access to a user's content on content management system 110.
Collaboration Features
Another feature of content management system 110 is to facilitate collaboration between users. Collaboration features include content item sharing, commenting on content items, co-working on content items, instant messaging, providing presence and seen state information regarding content items, etc.
Sharing
Content management system 110 can manage sharing content via sharing service 128. Sharing content by providing a link to the content can include making the content item accessible from any computing device in network communication with content management system 110. However, in some embodiments a link can be associated with access restrictions enforced by content management system 110 and access control list 145. Sharing content can also include linking content using sharing service 128 to share content within content management system 110 with at least one additional user account (in addition to the original user account associated with the content item) so that each user account has access to the content item. The additional user account can gain access to the content by accepting the content, which will then be accessible through either web interface service 124 or directly from within the directory structure associated with their account on client device 150. The sharing can be performed in a platform agnostic manner. That is, the content can be shared across multiple client devices 150 of varying type, capabilities, operating systems, etc. The content can also be shared across varying types of user accounts.
To share a content item within content management system 110 sharing service 128 can add a user account identifier or multiple user account identifiers to a content entry in access control list database 145 associated with the content item, thus granting the added user account access to the content item. Sharing service 128 can also remove user account identifiers from a content entry to restrict a user account's access to the content item. Sharing service 128 can record content item identifiers, user account identifiers given access to a content item, and access levels in access control list database 145. For example, in some embodiments, user account identifiers associated with a single content entry can specify different permissions for respective user account identifiers with respect to the associated content item.
To share content items outside of content management system 110, sharing service 128 can generate a custom network address, such as a uniform resource locator (URL), which allows any web browser to access the content item or collection in content management system 110 without any authentication. To accomplish this, sharing service 128 can include content identification data in the generated URL, which can later be used to properly identify and return the requested content item. For example, sharing service 128 can include the account identifier and the content path or a content item identifying code in the generated URL. Upon selection of the URL, the content identification data included in the URL can be transmitted to content management system 110, which can use the received content identification data to identify the appropriate content item and return the content item.
In addition to generating the URL, sharing service 128 can also be configured to record in access control list database 145 that a URL to the content item has been created. In some embodiments, the content entry associated with a content item can include a URL flag indicating whether a URL to the content item has been created. For example, the URL flag can be a Boolean value initially set to 0 or false to indicate that a URL to the content item has not been created. Sharing service 128 can change the value of the flag to 1 or true after generating a URL to the content item.
In some embodiments, sharing service 128 can associate a set of permissions to a URL for a content item. For example, if a user attempts to access the content item via the URL, sharing service 128 can provide a limited set of permissions for the content item. Examples of limited permissions include restrictions that the user cannot download the content item, save the content item, copy the content item, modify the content item, etc. In some embodiments, limited permissions include restrictions that only permit a content item to be accessed from with a specified domain, i.e., from within a corporate network domain, or by accounts associated with a specified domain, e.g., accounts associated with a company account (e.g., @acme.com).
In some embodiments, sharing service 128 can also be configured to deactivate a generated URL. For example, each content entry can also include a URL active flag indicating whether the content should be returned in response to a request from the generated URL. For example, sharing service 128 can only return a content item requested by a generated link if the URL active flag is set to 1 or true. Thus, access to a content item for which a URL has been generated can be easily restricted by changing the value of the URL active flag. This allows a user to restrict access to the shared content item without having to move the content item or delete the generated URL. Likewise, sharing service 128 can reactivate the URL by again changing the value of the URL active flag to 1 or true. A user can thus easily restore access to the content item without the need to generate a new URL.
In some embodiments, content management system 110 can designate a URL for uploading a content item. For example, a first user with a user account can request such a URL, provide the URL to a contributing user and the contributing user can upload a content item to the first user's user account using the URL.
Team Service
In some embodiments content management system 110 includes team service 130. Team service 130 can provide functionality for creating and managing defined teams of user accounts. Teams can be created for a company, with sub-teams (e.g., business units, or project teams, etc.), and user accounts assigned to teams and sub-teams, or teams can be created for any defined group of user accounts. Teams service 130 can provide a common shared space for the team, private user account folders, and access limited shared folders. Teams service can also provide a management interface for an administrator to manage collections and content items within team, and can manage user accounts that are associated with the team.
Authorization Service
In some embodiments, content management system 110 includes authorization service 132. Authorization service 132 ensures that a user account attempting to access a namespace has appropriate rights to access the namespace. Authorization service 132 can receive a token from client application 152 that follows a request to access a namespace and can return the capabilities permitted to the user account. For user accounts with multiple levels of access (e.g. a user account with user rights and administrator rights) authorization service 132 can also require explicit privilege escalation to avoid unintentional actions by administrators.
Presence and Seen State
In some embodiments, content management system can provide information about how users with which a content item is shared are interacting or have interacted with the content item. In some embodiments, content management system 110 can report that a user with which a content item is shared is currently viewing the content item. For example, client collaboration service 160 can notify notifications service 117 when client device 150 is accessing the content item. Notifications service 117 can then notify all client devices of other users having access to the same content item of the presence of the user of client device 150 with respect to the content item.
In some embodiments, content management system 110 can report a history of user interaction with a shared content item. Collaboration service 126 can query data sources such as metadata database 146 and server file journal 148 to determine that a user has saved the content item, that a user has yet to view the content item, etc., and disseminate this status information using notification service 117 to other users so that they can know who currently is or has viewed or modified the content item.
Collaboration service 126 can facilitate comments associated with content, even if a content item does not natively support commenting functionality. Such comments can be stored in metadata database 146.
Collaboration service 126 can originate and transmit notifications for users. For example, a user can mention another user in a comment and collaboration service 126 can send a notification to that user that he has been mentioned in the comment. Various other content item events can trigger notifications, including deleting a content item, sharing a content item, etc.
Collaboration service 126 can provide a messaging platform whereby users can send and receive instant messages, voice calls, emails, etc.
Collaboration Content Items
In some embodiments content management service can also include Collaborative document service 134 which can provide an interactive content item collaboration platform whereby users can simultaneously create collaboration content items, comment in the collaboration content items, and manage tasks within the collaboration content items. Collaboration content items can be files that users can create and edit using a collaboration content item editor, and can contain collaboration content item elements. Collaboration content item elements may include a collaboration content item identifier, one or more author identifiers, collaboration content item text, collaboration content item attributes, interaction information, comments, sharing users, etc. Collaboration content item elements can be stored as database entities, which allows for searching and retrieving the collaboration content items. Multiple users may access, view, edit, and collaborate on collaboration content items at the same time or at different times. In some embodiments this can be managed by requiring two users access a content item through a web interface and there they can work on the same copy of the content item at the same time.
Collaboration Companion Interface
In some embodiments client collaboration service 160 can provide a native application companion interface for the purpose of displaying information relevant to a content item being presented on client device 150. In embodiments wherein a content item is accessed by a native application stored and executed on client device 150, where the content item is in a designated location of the file system of client device 150 such that the content item is managed by content application 152, the native application may not provide any native way to display the above addressed collaboration data. In such embodiments, client collaboration service 160 can detect that a user has opened a content item, and can provide an overlay with additional information for the content item, such as collaboration data. For example, the additional information can include comments for the content item, status of the content item, activity of other users previously or currently viewing the content item. Such an overlay can warn a user that changes might be lost because another user is currently editing the content item.
In some embodiments, one or more of the services or storages/databases discussed above can be accessed using public or private application programming interfaces.
Certain software applications can access content storage 142 via an API on behalf of a user. For example, a software package such as an application running on client device 150, can programmatically make API calls directly to content management system 110 when a user provides authentication credentials, to read, write, create, delete, share, or otherwise manipulate content.
A user can view or manipulate content stored in a user account via a web interface generated and served by web interface service 124. For example, the user can navigate in a web browser to a web address provided by content management system 110. Changes or updates to content in the content storage 142 made through the web interface, such as uploading a new version of a content item, can be propagated back to other client devices associated with the user's account. For example, multiple client devices, each with their own client software, can be associated with a single account and content items in the account can be synchronized between each of the multiple client devices.
Client device 150 can connect to content management system 110 on behalf of a user. A user can directly interact with client device 150, for example when client device 150 is a desktop or laptop computer, phone, television, internet-of-things device, etc. Alternatively or additionally, client device 150 can act on behalf of the user without the user having physical access to client device 150, for example when client device 150 is a server.
Some features of client device 150 are enabled by an application installed on client device 150. In some embodiments, the application can include a content management system specific component. For example, the content management system specific component can be a stand-alone application 152, one or more application plug-ins, and/or a browser extension. However, the user can also interact with content management system 110 via a third-party application, such as a web browser, that resides on client device 150 and is configured to communicate with content management system 110. In various implementations, the client-side application 152 can present a user interface (UI) for a user to interact with content management system 110. For example, the user can interact with the content management system 110 via a file system explorer integrated with the file system or via a webpage displayed using a web browser application.
In some embodiments, client application 152 can be configured to manage and synchronize content for more than one account of content management system 110. In such embodiments client application 152 can remain logged into multiple accounts and provide normal services for the multiple accounts. In some embodiments, each account can appear as folder in a file system, and all content items within that folder can be synchronized with content management system 110. In some embodiments, client application 152 can include a selector to choose one of the multiple accounts to be the primary account or default account.
While content management system 110 is presented with specific components, it should be understood by one skilled in the art, that the architectural configuration of system 100 is simply one possible configuration and that other configurations with more or fewer components are possible. Further, a service can have more or less functionality, even including functionality described as being with another service. Moreover, features described herein with respect to an embodiment can be combined with features described with respect to another embodiment.
While system 100 is presented with specific components, it should be understood by one skilled in the art, that the architectural configuration of system 100 is simply one possible configuration and that other configurations with more or fewer components are possible.
File Journal and Storage Systems
Content storage interface 206 can manage communications, such as content requests or interactions, between client device 150 and content storage 142. Content storage interface 206 can process requests from client device 150 to upload and download content to and from content storage 142. Content storage interface 206 can receive content requests (e.g., downloads, uploads, etc.) from client device 150, verify permissions in access control list 145, communicate with authorization service 132 to determine if client device 150 (and/or the request from client device 150) is authorized to upload or download the content to or from content storage 142, and interact with content storage 142 to download or upload the content in content storage 142 to client device 150. If the request from client device 150 is a request to download a content item, content storage interface 206 can retrieve the content item from content storage 142 and provide the content item to client device 150. If the request from client device 150 is a request to upload a content item, content storage interface 206 can obtain the content item from client device 150 and upload the content item to content storage 142 for storage.
When processing content requests from client device 150, content storage interface 206 can communicate with storage index 210 to check the availability and/or storage location of the requested content in content storage 142, and track content items in content storage 142. Storage index 210 can maintain an index of content items on content storage 142 which identifies the content items on content storage 142 and can also identify a respective location of the content items within content storage 142. Thus, storage index 210 can track content items on content storage 142 as well as storage locations of the content items. Storage index 210 can track entire content items, such as files, and/or portions of the content items, such as blocks or chunks. In some cases, content items can be split into blocks or chunks which can be stored at content storage 142 and tracked in storage index 210. For example, content storage 142 can store a content item as blocks or chunks of data which include respective data portions of the content item. Storage index 210 can track the blocks or chunks of the content item stored in content storage 142.
File journal interface 202 can manage communications, such as metadata requests and content synchronizations and operations, between client device 150 and server file journal 148. For example, file journal interface 202 can translate, validate, authenticate, and/or process operations, configurations, and state information between client device 150 and server file journal 148. File journal interface 202 can verify permissions from an FSAuth token in a cursor or through authorization service 132 to authorize, or verify authorization of, requests sent by client device 150 to server file journal 148. When processing requests or operations from client device 150, file journal interface 202 can access namespace membership store 208 to determine or verify namespace ownership information for any namespaces associated with the requests or operations from client device 150, and retrieve permissions information from access control list 145 to verify permissions of content associated with the requests or operations from client device 150.
Translation service 204 in file journal interface 202 can perform linearization and translation operations for communications between client device 150 and server file journal 148. For example, translation service 204 can translate communications from client device 150 to a different format consistent with the structure and format of data in server file journal 148, and vice versa. To illustrate, in some cases, client device 150 can process content item information (e.g., state, changes, versions, etc.) at client device 150 as operations, while server file journal 148 can process the same information as content item revisions reflected by rows in a data structure such as a database table. To enable synchronization of content item information between client device 150 and server file journal 148, translation service 204 can translate operations from client device 150 into revisions suitable for server file journal 148, and can translate revisions reflected in rows of data on server file journal 148 to operations suitable for client device 150.
In some cases, authorization service 132 can generate a token that verifies or indicates that client device 150 is authorized to access, update, download, or upload a requested content item. The token can include a device identifier associated with client device 150, an account identifier associated with a user account authenticated or authorized at client device 150, a session identifier associated with an authorized session at client device 150, a view context, and access permissions to identified collections. The token can be included in a cryptographically signed data object called a cursor, which will be described in greater detail below. Content management system 110 and/or authorization service 132 can send the token(s) to client device 150, and client device 150 can provide the token to content management system 110 when requesting content item revisions and/or updates to server file journal 148 as further described below. Client device 150 can also provide the token to content storage interface 206 to validate any content requests (e.g., downloads, uploads, etc.). Content storage interface 206 can use the token to authorize queries to storage index 210 and upload or download content items to or from content storage 142.
For example, client device 150 can send to content storage interface 206 a request to upload a content item to content storage 142. The request can include the token and the content item to be uploaded. Content storage interface 206 can use the token to authorize a query to storage index 210 to check if the content item already exists on content storage 142, and authorize the upload of the content item to content storage 142. Client device 150 can also provide the token to file journal interface 202 to authorize a request to store metadata on server file journal 148 to track the upload and revision of the content item.
For example, content item 220 (e.g., MyFile.abc) can be split into blocks 220A, 220B, 220C, 220N. Content storage interface 206 can receive blocks 220A, 220B, 220C, 220N and send block data 222B to content storage 142 for storage at content storage 142. Block data 222B can include blocks 220A, 220B, 220C, 220N associated with content item 220.
Blocks 220A, 220B, 220C, 220N can be stored on one or more storage devices or volumes at content storage 142 and/or aggregated within one or more logical storage containers (e.g., buckets) or data clusters. In some cases, blocks 220A, 220B, 220C, 220N can be stored together on a same location (e.g., storage device, volume, container, and/or cluster). In other cases, some or all of blocks 220A, 220B, 220C, 220N can be stored on two or more different locations (e.g., two or more different storage devices, volumes, containers, and/or clusters).
Content storage interface 206 can also store block metadata 222A at storage index 210. Block metadata 222A can identify blocks 220A, 220B, 220C, 220N, and allows storage index 210 to track blocks 220A, 220B, 220C, 220N at content storage 142. Block metadata 222A can include an identifier for each block 220A, 220B, 220C, 220N. The identifier for a block can be a name or key, such as a hash of the block, which identifies the block.
Block metadata 222A can also include location information for blocks 220A, 220B, 220C, 220N, which indicates the respective storage location of blocks 220A, 220B, 220C, 220N. The location information of a block can identify the storage device or volume where the block is stored and/or a logical storage container or data cluster where the block is contained. The location information can be used to access or retrieve the associated block.
Content storage interface 206 can store block metadata 222A at storage index 210 before or after storing blocks 220A, 220B, 220C, 220N at content storage 142. For example, content storage interface 206 can store blocks 220A, 220B, 220C, 220N at content storage 142 and subsequently store block metadata 222A at storage index 210 to indicate that blocks 220A, 220B, 220C, 220N have been stored at content storage 142.
In some cases, content storage interface 206 can query storage index 210 prior to storing blocks 220A, 220B, 220C, 220N at content storage 142, to determine if (or where) blocks 220A, 220B, 220C, 220N are stored at content storage 142. For example, content storage interface 206 can query storage index 210 based on block metadata 222A to check if blocks 220A, 220B, 220C, 220N are stored at content storage 142. Storage index 210 can compare block identifiers in block metadata 222A with block identifiers at storage index 210 to check for any matches. A match between block identifiers indicates that an associated block is stored at content storage 142.
As previously mentioned, server file journal 148 tracks content item revisions, including content item adds, edits, moves or renames, deletes, etc. Accordingly, file journal interface 202 can store revision 222C at server file journal 148 to indicate that content item 220 and/or blocks 220A, 220B, 220C, 220N were added to content storage 142. Revision 222C can represent a revision of content item 220 within a journal of content item revisions at server file journal 148.
Revision 222C can identify content item 220 and an operation associated with content item 220, such as an add operation (e.g., upload), edit operation, move or rename operation, delete operation, etc. Revision 222C can also identify a namespace in content management system 110 where content item 220 is stored, and a row in a journal of content item revisions at server file journal 148 for storing revision 222C. The row within the journal of content item revisions can represent a revision number associated with revision 222C for content item 220.
File Journal Interface
To synchronize content item information (e.g., state, changes or revisions, etc.) with client device 150, server file journal 148 can send or receive revisions data 304 to or from file journal interface 202, which represent revisions tracked or stored in server file journal 148 for one or more content items. Revisions data 304 can include, for example, a log of content item revisions corresponding to rows in server file journal 148. Server file journal 148 can send revisions data 304 to file journal interface 204, which can translate revisions data 304 into operations data 302 for client device 150, as further described below.
Client device 150 can perform content operations to update or modify content items at client device 150. To synchronize content item information with server file journal 148, client device 150 can send or receive operations data 302 to or from file journal interface 202. Client device 150 can send operations data 302 to file journal interface 202 to report changes at client device 150 to content items, and receive operations data 302 from file journal interface 202 to obtain the latest state of content items from server file journal 148 (e.g., revisions data 304).
For example, client device 150 can edit content item A at client device 150 and report to file journal interface 202 an edit operation indicating the edit to content item A. The edit operation can be included in operations data 302 communicated with file journal interface 202 to indicate the revision to content item A. File journal interface 202 can receive operations data 302 including the edit operation and generate a revision for storage at server file journal 148, tracking the edit to content item A. File journal interface 202 can include the revision associated with the edit operation in revisions data 304 to server file journal 148, in order to update server file journal 148 to store the revision representing the edited state of content item A.
As further described below, operations data 302 can include a cursor which identifies the latest state or revision obtained by client device 150 for each namespace associated with client device 150. For example, the cursor can identify the latest revision in server file journal 148 obtained by client device 150 for each namespace associated with client device 150. The information in the cursor allows file journal interface 202 to determine whether an operation in operations data 302 from client device 150 reflects the latest state or revisions in server file journal 148 for the namespace(s) associated with the operation. This can help file journal interface 202 ensure that operations in operations data 302 from client device 150 that correspond to older revisions in server file journal 148 are not written to server file journal 148, which can create a conflict between existing revisions in server file journal 148 and revisions translated from operations data 302.
To enable synchronization of content item information between client device 150 and server file journal 148, file journal interface 202 can translate (e.g., via translation service 204) operations data 302 to revisions data 304, and vice versa. When receiving operations data 302 from client device 150, file journal interface 202 can convert operations data 302 to revisions data 304, which includes content item revisions interpreted from operations in operations data 302. When receiving revisions data 304 from server file journal 148, file journal interface 202 can convert revisions data 304 to operations data 302, which include operations for implementing revisions in revisions data 304 at client device 150. Revisions data 304 includes data in server file journal 148 describing what happened to one or more content items (i.e., revisions to the one or more content items), and operations data 302 includes operations that have been executed or should be executed at client device 150 to modify the one or more content items. Thus, file journal interface 202 can translate data describing revisions to one or more content items from server file journal 148 (e.g., operations data 304) to operations that have or should be executed at client device 150 to modify the one or more content items at client device 150.
As previously noted, in addition to translating operations data 302 from client device 150 to revisions data 304 for server file journal 148, file journal interface 202 can convert revisions data 304 from server file journal 148 to operations data 302 for client device 150. File journal interface 202 can obtain revisions data 304 from server file journal 148 and translate revisions in revisions data 304 to operations for execution at client device 150 to revise one or more content items at client device 150 according to such revisions. The operations generated from the revisions in revisions data 304 are included in operations data 302 provided by file journal interface 202 to client device 150. This translation between operations data 302 and revisions data 304 allows client device 150 and server file journal 148 to synchronize content item information with each other as necessary.
Prior to writing to server file journal 148 any revision data 304 generated from operations data 302 provided by client device 150, file journal interface 202 can check a cursor in operations data 302 and/or query server file journal 148 to ensure any revisions in revisions data 304 do not create a conflict in server file journal 148. For example, file journal interface 202 can query server file journal 148 to check whether the version of a content item associated with a revision in revisions data 304 is the same the version of the content item at server file journal 148, or whether the version of the content item at server file journal 148 is an updated or different version as the content item to which the revision in revisions data 304 pertains. If server file journal 148 shows that the latest version of the content item is a different version than the version to which revision data 304 pertains, the two versions are in conflict.
File journal interface 202 can update server file journal 148 to store new revisions included in revisions data 304 derived from operations data 302. When querying and/or updating revisions in server file journal 148, file journal interface 202 can query namespace membership store 208 to retrieve namespace ownership information associated with any namespaces affected by the revisions in revisions data 304. The namespace ownership information can indicate which user account(s) own or are members of a particular namespace, and thus are able to access the particular namespace. Thus, file journal interface 202 can analyze the namespace ownership information to ensure server file journal 148 is not updated to include a revision to a namespace from a user account that is not a member of the namespace.
With reference to
Journal 312 includes records containing an NSID, SJID, clock (e.g., timestamp), file identifier (FileID), extended attribute(s) (xattr), etc. The xattr can store metadata associated with content items or operations.
In some cases, journal 310 can include other fields such as a size field which represents the size of an associated content item, a directory field (e.g., Is_Dir) which can be set to indicate when a content item is a directory, a file identifier that uniquely identifies the associated file, a clock or timestamp field, etc.
File journal interface 202 can perform translation 320 based on operations data 302 and revisions data 304 as previously mentioned. When performing translation 320, translation service 204 can transform operations data 302 into revisions 322, which include linearized revisions for storage at server file journal 148. Translation service 204 can also transform revisions data 304 into linearized operations 324A, included in operations data 302 sent to client device 150, which can be applied by client device 150 to update content item information (e.g., state, changes, etc.) at client device 150. Translation service 204 can also generate or update cursor 324B and provide cursor 324B in operations data 302 to client device 150. Cursor 324B identifies a respective revision or row in server file journal 148 corresponding to each namespace and/or content item associated with linearized operations 324B.
For example, cursor 324B can identify a namespace (e.g., NSID) and row in server file journal 148 for that namespace (e.g., SJID), which indicate the latest revision in server file journal 148 for that namespace. The namespace and row in cursor 324B can be associated with an operation in linearized operations 324A. Cursor 324B can identify a specific position on a log of revisions in server file journal 148 for the particular namespace, indicating the revision or state of the namespace in server file journal 148 after and/or before linearized operations 324A are applied at client device 150. Thus, cursor 324B can indicate the state of a namespace and/or content item in server file journal 148 before or after linearized operations 324A, which can help avoid revision conflicts and track the order of revisions before and after linearized operations 324A are applied.
Each row (402) in journal 310 includes a namespace identifier field (NSID) for uniquely identifying a namespace associated with that row, a server journal identifier field (SJID) that includes monotonically increasing values which map to a row in a given namespace and provides an ordering of operations or revisions within that namespace.
Journal 310 also includes a path field (Path) for identifying a namespace-relative path of a content item, a block field (Block) for identifying a block or blocklist associated with the content item, a previous revision field (Prev_Rev) for identifying the row (i.e., SJID) in journal 310 that represents the previous state or revision of the content item, and a target namespace field (Target NS) for identifying a target namespace for a mount point of a mounted namespace (if the row corresponds to a mount). There is no data for the Target NS field for rows (e.g., revisions) which do not correspond to mount points.
The first of rows 402 in journal 310 identifies the first revision (SJID 1) for “File1” (Path field value File1) in namespace “100” (NSID 100), which corresponds to block “h1” and has no previous revisions (Prev_Rev) or target namespaces (Target NS). Since the row does not include a previous revision or a target namespace, the revision represented by the row corresponds to an addition at namespace “100” of “File1” associated with block “h1”.
The row in journal 310 containing SJID “4” represents the last revision in journal 310 for “File1” on namespace “100”, since this row is the last row or SJID in journal 310 corresponding to “File1” on namespace “100”. This row containing SJID “4” indicates that “File1” on namespace “100” was edited after being added in SJID “1”, and the edit corresponds to block “h4”.
Modifications 404 depict an example of modifications representing revisions 322. In this example, each of modifications 404 illustrates a content revision from a corresponding row (402) in journal 310. Each modification corresponds to an SJID and NSID in journal 310, and a file associated with the corresponding SJID and NSID in journal 310. In this example, the content associated with modifications 404 represents example content values of the blocks (e.g., “h1”, “h2”, “h3”, “h4”) in journal 310. The content values in modifications 404 are provided for illustration purposes to depict example modifications to content associated with each revision.
For example, the first modification in modifications 404 represents SJID “1” and NSID “100” in journal 310, and depicts “File1” in namespace “100” being added. Content “aaa” represents a value of “h1” for “File1” at SJID “1” of NSID “100”. Modifications 404 also depict an edit of “File1” in namespace “100” representing SJID “4” and NSID “100” in journal 310, which illustrates the content “aaa” (e.g., “h1”) associated with “File1” in namespace “100” being modified to “aa2” (e.g., “h4”).
In translation 320, revisions 322 from rows 402 in journal 310 are converted to linearized operations 324A. Linearized operations 324A are generated from revisions 322 in journal 310 and represent modifications 404 after linearization. As illustrated by linearized operations 324A, an operation in linearized operations 324A can be based on multiple revisions (322) and/or modifications (404), or a single revision (322) and/or modification (404).
For example, modifications 404 depict a revision adding “File1” to namespace “100”, which corresponds to SJID “1” and NSID “100” in journal 310, and a revision editing “File1” in namespace “100”, which corresponds to SJID “4” and NSID “100” in journal 310. The add revision can be inferred from the content value “aaa” (e.g., “h1”) associated with “File1” and NSID “100” and the lack of any previous revisions for “File1” and NSID “100”. In other words, the content “aaa” indicates that content (e.g., “h1”) was either added or edited, and the lack of a previous revision for “File1” and NSID “100” suggests that the content “aaa” represents content (e.g., “h1”) being added as opposed to edited. The edit revision can be inferred from the content value “aa2” (e.g., “h4”) associated with “File1” and NSID “100” and the previous revision (SJID “1” and NSID “100”) associated with “File1” and NSID “100”. In other words, the change from content “aaa” to “aa2” associated with “File1” and NSID “100” suggests that the content “aa2” represents an edit.
In linearized operations 324A, the add and edit modifications (404) corresponding to SJID “1” and SJID “4” for NSID “100” can be converted into a single linearized operation (Edit operation) which edits the content value associated with “File1” from “aaa” (e.g., “h1”) to “aa2” (e.g., “h4”). The single linearized operation editing content (e.g., “h1”) of “File1” to “aa2” (e.g., “h4”) reflects the modification adding “File1” associated with content “aaa” (e.g., “h1”) to namespace “100”, as well as the modification editing content “aaa” (e.g., “h1”) associated with “File1” in namespace “100” to “aa2” (e.g., “h4”).
Accordingly, this linearized operation is based on two modifications 404 and two corresponding revisions in revisions 322.
The modification in modifications 404 corresponding to SJID “2” and NSID “100” in journal 310 represents a revision adding “File2” associated with content “bbb” (e.g., “h2”) to namespace “100”. This modification represents the only revision 322 from journal 310 corresponding to “File2” on namespace “100”. Accordingly, linearized operations 324A include a single operation for “File2” on namespace “100”, which adds “File2” associated with content “bbb” (e.g., “h2”) to namespace “100” and is based on a single modification 404 (add of “File2” on namespace “100”) and revision 322.
Modifications 404 in this example also include for a modification adding “File3” associated with content “ccc” (e.g., “h3”) to namespace “100”, which corresponds to SJID “3” and NSID “100” in journal 310, and a delete (represented as “−1”) of “File3” from namespace “100”, which corresponds to SJID “5” and NSID “100” in journal 310. Thus, revisions 322 include two modifications 404 associated with “File3” on namespace “100”. Since the last revision in journal 310 associated with “File3” and namespace “100” corresponds to the delete modification representing SJID “5” and NSID “100” in journal 310, the add and delete modifications 404 associated with “File3” and namespace “100” from revisions 322 can be linearized to a single operation deleting “File3” from namespace “100”. Accordingly, linearized operations 324A include a single operation for “File3” and namespace “100”, which is the single operation deleting “File3” from namespace “100”.
SJIDs “6” and “7” for NSID “100” and SJID “1” for NSID “101” in journal 310 represent “Dir” being added to namespace “100” and later moved from namespace “100” to namespace “101”. For example, SJID “6” and NSID “100” identifies “Dir” and namespace “100” and does not include a previous revision, which indicates “Dir” was added to namespace “100” at SJID “6”. SJID “7” identifies “Dir” being moved from namespace “100” to namespace “101”, as reflected by the block field (“-”), the previous revision field (SJID “6”), and the target namespace field (“101”). SJID “1” for NSID “101” then identifies “Dir” being added to namespace “101”, as indicated by the lack of prior rows or revisions for “Dir” and namespace “101”. The add and move revisions in SJIDs “6” and “7” in NSID “100” and SJID “1” in NSID “8” are depicted by three modifications 404: an add of “Dir” to namespace “100” which corresponds to SJID “6” and NSID “100”, a delete of “Dir” from namespace “100” which corresponds to SJID “7” and NSID “100”, and an add of “Dir” to namespace “101” which corresponds to SJID “1” and NSID “101”.
The add and delete modifications 404 of “Dir” and namespace “100”, which respectively correspond to SJIDs “6” and “7” of NSID “100” in journal 310, are linearized to a single operation deleting “Dir” from namespace “100, since the last revision in journal 310 corresponding to “Dir” and namespace “100” is a delete of “Dir” from namespace “100” at SJID “7” and NSID “100”. The add of “Dir” to namespace “101”, which corresponds to SJID “1” and NSID “101” in journal 310, is the only modification 404 and revision 322 corresponding to “Dir” and namespace “101”. Accordingly, the add is provided in linearized operations 324A as a single mount operation for “Dir” and namespace “101”. Therefore, the three modifications 404 from revisions 322 corresponding to SJIDs “6” and “7” in NSID “100” and SJID “1” in NSID “101” (i.e., the add and delete of “Dir” on namespace “100”, and the add of “Dir” on namespace “101”), are linearized to two operations in linearized operations 324A: a delete operation for “Dir” in namespace “100” and a mount operation for “Dir” in namespace “101”.
As illustrated above, linearized operations 324A include an edit operation for “File1” and namespace “100”, an add operation for “File2” and namespace “100”, a delete operation of “File3” in namespace “100”, a delete operation for “Dir” in namespace “100”, and a mount operation for adding “Dir” to namespace “101”. These operations in linearized operations 324A are generated from revisions 322 and reflect the latest state of each content item in journal 310. File journal interface 202 can generate linearized operations 324A and send linearized operations 324A to client device 150 to ensure client device 150 contains the latest state from revisions 322 in journal 310.
When providing linearized operations 324A to client device 150, file journal interface 202 can include cursor 324B along with linearized operations 324A to client device 150. Cursor 324B can identify the last revision (SJID) for each namespace (NSID) in journal 310. In some embodiments, cursor 324B can also include an FSAuth token including the user ID, and the last observed access permissions to the NSID provided in the cursor. The last revision for each namespace can indicate a position in journal 310 corresponding to the latest revisions sent to client device 150 for each namespace.
In some cases, cursor 324B can also map each operation in linearized operations 324A to a namespace (NSID) and row (SJID) in journal 310. The namespace and row associated with an operation can indicate the position in journal 310 corresponding to the operation. In other words, the namespace and row associated with an operation can indicate the revision number in journal 310 represented by that operation. The namespaces and rows in cursor 324B correspond to the latest state in journal 310 for each namespace and content item associated with linearized operations 324A. Cursor 324B can provided to client device 150 as a tool for client device 150 to identify to file journal interface 202 the latest state or revisions obtained by client device 150 for one or more namespaces and/or content items when attempting to apply changes (e.g., via operations data 302) from client device 150 to the one or more namespaces and/or content items. When file journal interface 202 receives cursor 324B from client device 150, it can use cursor 324B to identify the position of client device 150 at journal 310 (e.g., the latest revisions from journal 310 obtained by client device 150) and detect oravoid conflicts caused by operations from client device 150.
For example, if file journal interface 202 receives an operation from client device 150 modifying “File1” in namespace “100”, file journal interface 202 can use cursor 324B, which it receives from client device 150 along with the operation, to check whether journal 310 has any newer revisions for “File1” in namespace “100” than the revision identified in cursor 324B from client device 150. If the revision in cursor 324B is the most current revision in journal 310, file journal interface 202 can commit the edit operation as a new revision in journal 310 (e.g., SJID “8” in NSID “100”) for “File1” in namespace “100”.
Alternatively, if the revision in cursor 324B is not the most current revision in journal 310 for “File1” in namespace “100”, file journal interface 202 can determine that the edit operation from client device 150 is not based on the most current version in journal 310 for “File1” in namespace “100”. For example, if cursor 324B identifies SJID “4” and NSID “100” in journal 310 and file journal interface 202 determines that journal 310 includes a revision at SJID “12” and NSID “100” for “File1” in namespace “100”, file journal interface 202 can determine that the edit operation from client device 150 pertains to an older version of “File1” on namespace “100” (e.g., SJID “4” and NSID “100”), and the edit operation can create a conflict as it edits a file that has since been modified. File journal interface 202 can detect this conflict created by the edit operation and reject the edit operation, attempt to reconcile the conflict, or provide the latest revisions to client device 150 and allow client device 150 to reconcile the conflict.
Each time file journal interface 202 sends linearized operations to client device 150, it can include a cursor as described here which identifies a respective position in journal 310 for each namespace and/or content item. Similarly, any time client device 150 sends an operation to file journal interface 202, it can include its latest cursor which file journal interface 202 can use to map the state at client device 150 with the state at journal 310.
Journal 310 in this example depicts a journal with multiple namespaces. As previously noted, in some examples, server file journal 148 can maintain namespace-specific journals. Cursor 324B may include an SJID and NSID for each namespace, to indicate the latest revision for each namespace. Based on cursor 324B, file journal interface 200 can query multiple journals, in embodiments where multiple journals are maintained, and/or retrieve revisions from multiple journals, as further explained herein.
Operations data 302 also includes cursor 324B previously received by client device 150 from file journal interface 202. Cursor 324B can identify the state (e.g., NSID and SJID) or latest revisions in journal 310 for one or more namespaces and/or content items. Client device 150 can provide cursor 324B to file journal interface 202 as a reference point for operations 412. In this example, cursor 324B provides the latest state for namespace “100”, which is represented by SJID “9”.
In some cases, the cursor is cryptographically signed by content management system 110, which allows file journal interface 202 to determine that the cursor has not been tampered with. Further, since client device 150 commit revisions to server file journal 148 when it has received the most recent revisions from server file journal 148 for the namespace, file journal interface 202 can accept that the last observed access permissions to the NSID are still valid, and therefore client device 150 has access to the namespace.
File journal interface 202 can receive operations 412 and cursor 324B and perform linearization 410, to linearize and transform operations 412 from client device 150 to revisions 322 for journal 310. Based on operations 412, file journal interface 202 can generate log 414 of operations. Log 414 can include a list of operations from operations 412 mapped to respective namespace(s) in journal 310. In some cases, log 414 can include linearized operations (324A) generated from operations 412 as previously explained.
File journal interface 202 can use cursor 324B to verify that operations 412 reflect the latest state or revisions in journal 310 before updating journal 310 to reflect the operations in log 414. If file journal interface 202 confirms that cursor 324B reflects the latest state or revisions in journal 310 for the namespaces and/or content items associated with log 414, file journal interface 202 can add revisions 322 to journal 310 based on log 414. Revisions 322 can include the latest state or revision of each content item and/or namespace associated with the operations in log 414.
The operations in log 414 include an add and edit operation for “File5”. Accordingly, revisions 322 include the edit of “File5”, which file journal interface 202 can write to journal 310 as the latest state of “File5” (i.e., the state after the add and edit operations are applied to “File5” in a linearized fashion). The operations in log 414 also include an add operation for “Dir2” as well as edit and delete operations for “File4” on namespace “100”. Revisions 322 can thus include an operation adding “Dir2” to namespace “100” and an operation deleting “File4” from namespace “100” as the latest state of “Dir2” and “File4” respectively.
In
File journal interface 202 can transform operations in log 414 to revisions 322 and update journal 310 to include revisions 322. File journal interface 202 can write revisions 322 to journal 310 at respective rows in journal 310. File journal interface 202 can add revisions 322 to the next available rows (e.g., SJIDs) in journal 310. In some cases, file journal interface 202 can add revisions 322 based on a relative order which can be determined based on linearization 410 and/or respective timestamps or clocks.
As shown in
Journal 310 in
When updating journal 310 to include revisions 322 based on log 414 and cursor 324B, translation service 204 can identify the path of each content item to include in the path field of journal 310. In some cases, translation service 204 can translate an identifier of a content item (e.g., File ID) to a path of the content item (e.g., /directory/filename). For example, client device 150 can use identifiers to identify content items (e.g., content items in operations data 302) without having to track or calculate respective paths for the content items. Journal 310 may instead use a content item's path to identify the content item. Translation service 204 can use the identifiers of content items from client device 150 to calculate the paths of the content items for journal 310, and update journal 310 using the paths calculated for the content items. Translation service 204 can also perform a reverse translation to obtain a content item's identifier based on the content item's path, and use the content item's identifier when referencing the content item in communications with client device 150.
For example, translation service 204 can use the path in journal 310, NSID in journal 310, and/or a directory field in journal 310 (or elsewhere in server file journal 148) to identify a content item and obtain an identifier (e.g., File ID) of that content item. If file journal interface 202 sends an update or information to client device 150 pertaining to that content item, file journal interface 202 can provide the identifier of the content item to client device 150, which client device 150 can use to identify the content item with or without the path of the content item.
As previously mentioned, before writing revisions 322 to journal 310 from operations 412, file journal interface 202 can check if cursor 324B reflects the latest state or revision in journal 310 for each namespace and/or content item associated with operations 412. In some cases, after confirming that cursor 324B reflects the latest state or revisions in journal 310, file journal interface 202 can also perform a second check to ensure that a revision generated from operations 412 will not conflict with an existing revision in journal 310. For example, if SJID “5” in namespace “100” at journal 310 represents a delete operation of “File5”, the edit revision 322 of “File5” depicted in SJID “14” emitted from operations 412 received by file journal interface 202 from client device 150 would create a conflict by attempting to edit “File5” even though “File5” was deleted at SJID “5”. Thus, file journal interface 202 can reject the edit operation and revision in this example, and communicate to client device 150 that the edit operation is invalid. File journal interface 202 can update cursor 324B and provide the updated cursor to client device 150 to inform client device 150 of the latest state or revision in journal 310 for “File5” (and any other content item) as necessary.
In this example, table 502A depicts SJIDs “100” and “101” for NSID “1”. SJID “100” is associated with an operation adding “foo.txt” to namespace “1” at timestamp “1000”, and SJID “101” is associated with an operation mounting namespace “2” at timestamp “1001”. Table 502B depicts SJIDs “1” and “2” for NSID “2”. SJID “1” is associated with an operation adding “bar.txt” to namespace “2” at timestamp “500”, and SJID “2” is associated with an operation editing “bar.txt” at timestamp “1002”.
A linearizer (e.g., translation service 204) can obtain the batch of operations in tables 502 and emit a single stream of operations (512) with a cursor (514). The linearizer can identify all namespaces having at least one operation in tables 502 and linearize the operations for all namespaces based on the respective timestamps, NSIDs, SJIDs. In this example, the batch of operations in tables 502 linearize to the stream of operations shown in table 504.
Table 504 includes NSID column 510 which includes NSID fields for identifying the namespace of each operation, operations column 512 which includes operation fields for identifying the operations in table 504, and cursor column 514 which includes cursor fields for identifying a cursor state for each operation. Row 504A in table 504 includes the add operation from SJID “100” of namespace “1” in table 502A. The cursor state in cursor column 514 for row 504A is namespace “1” and SJID “100”, which indicates the add operation corresponds to SJID “100” in namespace “1” shown in table 502A. Row 504B in table 504 does not include a value in NSID column 510 or operations column 512, but updates the cursor state in cursor column 514 to include a cross-namespace cursor state, which in this example adds SJID “0” for namespace “2”.
Row 504C in table 504 includes the add operation from SJID “1” in namespace “2” shown in table 502A. The cursor state in cursor column 514 for row 504C includes the respective SJIDs “100” and “1” for namespaces “1” and “2” associated with the add operation in row 504C. As shown, the cursor state indicates the cursor is at SJID “100” in namespace “1” and SJID “1” in namespace “2”. In other words, the row or SJID in namespace “1” has not increased as the add operation does not affect the state of namespace “1”, but the row or SJID in namespace “2” has increased by one as the add operation represents a revision in namespace “2” and affects the state of namespace “2”. Thus, the cursor state in row 504C tracks the respective SJIDs for namespace “1” and namespace “2” after the add operation at SJID “1” in namespace “2”.
Row 504D in table 504 includes the mount operation at SJID “101” and namespace “1” at table 502A. The mount operation mounts namespace “2” at namespace “1”. The mount operation increases the SJID in namespace “1” from “100” to “101”, but does not increase the SJID in namespace “2”. Accordingly, the cursor state in cursor column 514 for row 504D includes SJID “101” for namespace “1” and remains SJID “1” for namespace “2”. This cursor state reflects the state and/or order at namespaces “1” and “2”.
Row 504E in table 504 includes the edit operation at SJID “2” and namespace “2” in table 502A, which according to the respective timestamps of the mount and edit operations, is after the mount operation at SJID “101” in namespace “1”. The cursor state in cursor column 514 of row 504E maintains the cursor state for namespace “1” at SJID “101” but increases the cursor state for namespace “2” to SJID “2”.
As illustrated in table 504, operations 512 are listed as a stream of operations linearized based on causality and timestamps across namespaces “1” and “2”. Once operations 512 are linearized in table 504 to reflect cross-namespace causality and sequencing, operations 512 can be converted to revisions in server file journal 148 (e.g., revisions 322 in journal 310) and written to server file journal 148.
For example, a journal for namespace “1” in server file journal 148 can be updated to include a revision at SJID “100” representing the add operation adding “foo.txt” to namespace “1”, and a revision at SJID “101” representing the mount operation mounting namespace “2” on namespace “1”. Moreover, a journal for namespace “2” in server file journal 148 can be updated to include a revision at SJID “1” representing the add operation adding “bar.txt” to namespace “2”, and a revision at SJID “2” representing the edit operation editing “bar.txt” on namespace “2”.
Lamport Clocks
At NSID 1, operation 510 has SJID 1 and clock 1. At NSID 2, operation 516 has SJID 1 and clock 1. At NSID, operation 520 has SJID 1 and clock 1. Operations 510, 516, 520 span multiple namespaces and do not have causal relationships. Accordingly, operations 510, 516, 520 do not affect each other's clocks.
Ordering of operations within the namespace can be determined based on the SJID at the namespace. Clocks for operations within the same namespace can simply be incremented by 1. Thus, at SJID 2 in NSID 1, the clock for operation 512 is incremented to 2.
Operation 512 in NSID 1 is a move of File1 to NSID 2. Accordingly, operation 512 triggers operation 518 at NSID 2, which is the add of File1 at NSID 2. Since operation 518 at NSID 2 is causally dependent on another operation from a different namespace, namely operation 512 from NSID 1, the clock for operation 518 is calculated based on the clock at NSID 1 and the clock at NSID 2. The algorithm can be expressed as: TargetNS_clockt1=max(Source_NSclock, TargetNS_clockt0)+1. Thus, in this example, the clock for operation 518 at NSID 2 is 3 (e.g., max(2, 1)+1). Accordingly, operation 518 at NSID 2 has SJID 2 and clock 3.
Similarly, operation 516 at NSID is a move of File2 from NSID 2 to NSID 1. Operation 516 thus triggers operation 522 at NSID 1, for adding File2 at NSID 1. The clock for operation 522 is calculated based on the clock algorithm, which equals 3. Thus, operation 522 has SJID 3 at NSID 1 and clock 3.
Operation 522 at NSID 3 is causally dependent on an operation in the same namespace, namely operation 520 at NSID 3. Thus, the clock for operation 522 can be calculated by incrementing the clock of operation 520 at NSID 3. In this example, the clock for operation 522 is therefore 2. Operation 522 at NSID 3 has SJID 2 and clock 2. Since operation 522 is a move operation for moving Dir to NSID 1, operation 522 triggers operation 524 at NSID 1, adding Dir to NSID 1.
Since operation 524 is triggered by operation 522 in a different namespace (NSID 3), the clock for operation 524 is calculated based on the clock at NSID 1 and the clock for operation 522. Accordingly, the clock for operation 524 is set to 4 (e.g., max(2, 3)+1). Operation 524 thus has SJID 4 at NSID 1 and clock 4.
Operation 526 at NSID 1 adds File3 to NSID 1, and is not a cross-namespace operation. Accordingly, the clock for operation 526 is calculated by incrementing the clock at NSID 1. The clock for operation 526 is thus set to 5.
Operation 528 is causally dependent on operation 526 also within NSID 1. The clock for operation 528 is thus set to 6 by incrementing the clock of operation 526 at NSID 1. Operation 528 has SJID 6 at NSID 1 and clock 6.
Operation 528 is a move operation which moves File3 to NSID 3. Operation 528 thus triggers operation 530 at NSID 3. Since operation 530 is based on an operation from a different namespace, its clock is calculated using the clock algorithm based on the clock at NSID 3 and the clock of operation 528. In this case, the clock for operation 530 is set to 7. Operation 530 thus has SJID 3 at NSID 3 and clock 7.
Operations 532, 534 are not cross-namespace operations and are causally related to operation 530 at NSID 3. Thus, the clock for operations 532, 534 can be calculated by incrementing the clock of operation 530. In this example, the clocks for operations 532, 534 are set to 8 and 9 respectively.
Operations and Revisions Protocol Translations and Linearization
At step 602, file journal interface 202 receives a request from client device 150 to synchronize operations pertaining to content items associated with a user account registered at content management system 110. The request includes operations (e.g., 412) associated with the content items and a cursor (e.g., 324B) identifying a current position (e.g., NSID: SJID) of client device 150 in journal 310 at server file journal 148. Each of the operations can include a namespace or a content item associated with a namespace. For example, the operations can include an operation to mount a namespace and an operation to add, edit, or delete a content item on a namespace.
In some aspects, the cursor can include an FSAuth token including the user ID and the last observed access permissions to the NSID provided in the cursor. Moreover, the cursor can be cryptographically signed by content management system 110, which allows file journal interface 202 to verify that the cursor has not been tampered with.
Based on the operations, at step 604, file journal interface 202 generates a set of linearized operations (e.g., 324A) associated with the content items, the set of linearized operations including a respective operation for each content item. The respective operation can be derived from one or more of the operations in the request associated with the content item. For example, the respective operation can be based on a single operation for the content item or multiple operations in the request.
At step 606, file journal interface 202 converts each respective operation in the set of linearized operations (e.g., 324A) to a respective revision (e.g., 322) for journal 310. The respective revision can represent a row (e.g., 402) of values for journal 310, reflecting the respective operation. Based on the cursor, at step 608, file journal interface 202 determines whether each respective revision conflicts with one or more revisions in journal 310.
For example, if the cursor indicates that client device 150 had not obtained the most recent revisions in journal 310 prior to the respective operation associated with the respective revision, file journal interface 202 may determine that client device 150 does not have the most current state from journal 310 and the respective revision would create a conflict as it modifies an outdated content item or namespace. File journal interface 202 may then reject the respective revision, send an updated cursor and/or revision(s) to client device 150, or attempt to reconcile the conflict with the latest revisions/state in journal 310. As another example, if the cursor indicates that client device 150 has the latest revisions in journal 310, file journal interface 202 may accept the respective revision. In some cases, prior to accepting the revision, file journal interface 202 can compare the respective revision with one or more previous revisions in journal 310 to validate the respective revision and ensure it would not conflict with previous revisions in journal 310. For example, file journal interface 202 can identify the previous revision in journal 310 for the content item (e.g., namespace, directory, file, etc.) associated with the respective revision, and check to ensure the respective revision does not conflict with the previous revision in journal 310.
At step 610, when the respective revision does not conflict with one or more revisions in journal 310, file journal interface 202 can add the respective revision to journal 310. File journal interface 202 can add the respective revision in a particular row in journal 310, which it can identify based on the namespace associated with the respective revision. When new revisions are added to journal 310 and/or server file journal 148, file journal interface 202 can send an updated cursor to client device 150 to report the new revisions and synchronize the new revisions with client device 150. Client device 150 can also request an update to the cursor at client device 150. Client device 150 can store a copy of the last cursor received from file journal interface 202 as a reflection of the state of content items on client device 150 and/or a position of client device 150 in journal 310 indicating the last revision(s) obtained by client device 150.
At step 620, file journal interface 202 retrieves, from journal 310 of revisions at server file journal 148, a plurality of revisions (e.g., 322) associated with one or more content items stored at client device 150 for a user account registered at content management system 110. Each revision can modify a namespace, folder, file, or any content item. Moreover, each revision can be associated with a namespace and a journal identifier (SJID) for that namespace.
In some cases, file journal interface 202 can retrieve the plurality of revisions from journal 310 based on a determination that journal 310 has been updated to include revisions that are not available at client device 150. For example, file journal interface 202 can track new revisions added to journal 310 and/or compare revisions at journal 310 with the cursor at client device 150. In some cases, file journal interface 202 can query journal 310 to retrieve the plurality of revisions and/or check revisions available at journal 310.
At step 622, file journal interface 202 determines respective operations based on a respective set of revisions of each content item associated with the plurality of revisions. For example, file journal interface 202 can linearize any revisions of a content item and translate the revisions to one or more respective operations for that content item. In some cases, file journal interface 202 can also transform multiple operations for that content item into a single operation defining or reflecting the state or modification of the content item when the multiple operations are executed in linear fashion.
In some cases, when calculating the respective operations for of the plurality of revisions, file journal interface 202 can make inferences or calculations based on the number of revisions associated with a particular content item and/or the type of content item associated with such revisions. For example, if the plurality of revisions includes a single revision for a content item, file journal interface 202 can infer from the single revision (e.g., revisions 322) and/or a block or content associated with the revision (e.g., block or content in rows 402 of journal 310) a type of modification (e.g., 404) of the content item represented by that revision, and calculate the respective operation for that content item based on the type of modification represented by the revision.
To illustrate, as shown in
Thus, unless the content or block field associated with a revision (322) in journal 310 depicts a deletion (e.g., a minus symbol in the block or content field), the respective operation for a first or only revision of a content item can represent a mount or add operation depending on whether the content item is a namespace or another type of content item. This is based on the assumption that other operations, such as an edit, unmount, or delete operation, would be expected to include a previous revision for mounting or adding the associated content item. If a content item does not have a previous revision associated with it, file journal interface 202 can infer that a revision associated with the content item is likely not an edit, unmount, or delete operation, but rather an add or mount operation.
In some cases, file journal interface 202 can calculate an operation for a content item based on multiple revisions (322) for that content item and associated namespace. For example, file journal interface 202 may infer a delete, edit, or unmount operation from a revision representing an add or mount of the content item and a subsequent revision representing the delete, edit, or unmount. To illustrate, as shown in
Based on the respective operations, at step 624, file journal interface 202 generates a set of linearized operations (e.g., 322) for each content item. The set of linearized operations can reflect modifications 404 of each content item based on the plurality of revisions in journal 310. File journal interface 202 can convert the plurality of revisions (322) to the set of linearized operations (324A) by linearizing the respective operations calculated for each content item based on relative clocks and/or causality.
At step 626, file journal interface 202 generates a cursor (e.g., 324B) identifying a position in journal 310 represented by the set of linearized operations. At step 628, file journal interface 202 sends the set of linearized operations and cursor to client device 150. The cursor can include a respective namespace identifier (NSID) and journal identifier (SJID) for each namespace and/or operation. The combination of an NSID and SJID in the cursor can indicate a revision number in journal 310 for a particular namespace. Client device 150 can use the cursor to identify revisions obtained by client device 150 and a position of client device 150 in journal 310 corresponding to the revisions that have been obtained by client device 150. Client device 150 can also provide its latest cursor to file journal interface 202 to report to file journal interface 202 the current position of client device 150 in journal 310. For example, client device 150 can provide the cursor to file journal interface 202 to determine if client device 150 needs new revisions.
Client device 150 can also provide its cursor to file journal interface 202 when reporting operations at client device 150 to file journal interface 202. The cursor maps the operations to specific revisions in journal 310 and/or a position in journal 310. This allows file journal interface 202 to determine if the operations from client device 150 are based on the latest revisions to the content items being modified by the operations.
Client device 150 can receive the cursor and set of linearized operations and update the content items at client device 150 based on the operations. This way, client device 150 can synchronize content items between client device 150 and content management system 110. Client device 150 can store the cursor to provide its position in journal 310 to file journal interface 202.
Computing Hardware and Architecture
In some embodiments computing system 700 is a distributed system in which the functions described in this disclosure can be distributed within a datacenter, multiple datacenters, a peer network, etc. In some embodiments, one or more of the described system components represents many such components each performing some or all of the function for which the component is described. In some embodiments, the components can be physical or virtual devices.
Example system 700 includes at least one processing unit (CPU or processor) 710 and connection 705 that couples various system components including system memory 715, such as read only memory (ROM) 720 and random access memory (RAM) 725 to processor 710. Computing system 700 can include a cache of high-speed memory 712 connected directly with, in close proximity to, or integrated as part of processor 710.
Processor 710 can include any general purpose processor and a hardware service or software service, such as services 732, 734, and 736 stored in storage device 730, configured to control processor 710 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Processor 710 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.
To enable user interaction, computing system 700 includes an input device 745, which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. Computing system 700 can also include output device 735, which can be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input/output to communicate with computing system 700. Computing system 700 can include communications interface 740, which can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
Storage device 730 can be a non-volatile memory device and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs), read only memory (ROM), and/or some combination of these devices.
The storage device 730 can include software services, servers, services, etc., that when the code that defines such software is executed by the processor 710, it causes the system to perform a function. In some embodiments, a hardware service that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 710, connection 705, output device 735, etc., to carry out the function.
For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
Any of the steps, operations, functions, or processes described herein may be performed or implemented by a combination of hardware and software services or services, alone or in combination with other devices. In some embodiments, a service can be software that resides in memory of a client device and/or one or more servers of a content management system and perform one or more functions when a processor executes the software associated with the service. In some embodiments, a service is a program, or a collection of programs that carry out a specific function. In some embodiments, a service can be considered a server. The memory can be a non-transitory computer-readable medium.
In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, solid state memory devices, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include servers, laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.
This application is a divisional of and claims the benefit of U.S. application Ser. No. 16/991,798, filed on Aug. 12, 2020, entitled File Journal Interface For Synchronizing Content, which is a continuation of U.S. application Ser. No. 15/858,410, filed on Dec. 29, 2017, entitled, File Journal Interface For Synchronizing Content, which claims of priority under U.S.C. § 119(e) to U.S. provisional application No. 62/611,473, filed on Dec. 28, 2017, all of which are expressly incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5220665 | Coyle, Jr. et al. | Jun 1993 | A |
| 5335346 | Fabbio | Aug 1994 | A |
| 5574901 | Takahashi | Nov 1996 | A |
| 5665863 | Yeh | Sep 1997 | A |
| 5745750 | Porcaro | Apr 1998 | A |
| 5778389 | Pruett et al. | Jul 1998 | A |
| 5802253 | Gross et al. | Sep 1998 | A |
| 5802508 | Morgenstern | Sep 1998 | A |
| 5956715 | Glasser et al. | Sep 1999 | A |
| 6269371 | Ohnishi | Jul 2001 | B1 |
| 6408298 | Van et al. | Jun 2002 | B1 |
| 6421684 | Cabrera et al. | Jul 2002 | B1 |
| 6427123 | Sedlar | Jul 2002 | B1 |
| 6546466 | Elko et al. | Apr 2003 | B1 |
| 6560655 | Grambihler et al. | May 2003 | B1 |
| 6574665 | Khotimsky et al. | Jun 2003 | B1 |
| 6618735 | Krishnaswami et al. | Sep 2003 | B1 |
| 6665863 | Lord et al. | Dec 2003 | B1 |
| 6944623 | Kim et al. | Sep 2005 | B2 |
| 6978271 | Hoffman et al. | Dec 2005 | B1 |
| 7024392 | Stefik et al. | Apr 2006 | B2 |
| 7051039 | Murthy et al. | May 2006 | B1 |
| 7080041 | Nagel et al. | Jul 2006 | B2 |
| 7162477 | Mukherjee | Jan 2007 | B1 |
| 7240281 | Gomi et al. | Jul 2007 | B2 |
| 7263718 | O'Brien et al. | Aug 2007 | B2 |
| 7275177 | Armangau et al. | Sep 2007 | B2 |
| 7313598 | Sheth et al. | Dec 2007 | B1 |
| 7447709 | Rozenman et al. | Nov 2008 | B1 |
| 7487228 | Preslan et al. | Feb 2009 | B1 |
| 7526575 | Rabbers et al. | Apr 2009 | B2 |
| 7529931 | Vasishth et al. | May 2009 | B2 |
| 7567991 | Armangau et al. | Jul 2009 | B2 |
| 7606876 | Graves et al. | Oct 2009 | B2 |
| 7624106 | Manley et al. | Nov 2009 | B1 |
| 7631298 | Kaler et al. | Dec 2009 | B2 |
| 7634482 | Mukherjee et al. | Dec 2009 | B2 |
| 7634514 | Langan et al. | Dec 2009 | B2 |
| 7657769 | Marcy et al. | Feb 2010 | B2 |
| 7660809 | Cortright et al. | Feb 2010 | B2 |
| 7685206 | Mathew et al. | Mar 2010 | B1 |
| 7720892 | Healey, Jr. et al. | May 2010 | B1 |
| 7734690 | Moromisato et al. | Jun 2010 | B2 |
| 7761497 | O'Connell, Jr. et al. | Jul 2010 | B1 |
| 7805469 | Nagaralu et al. | Sep 2010 | B1 |
| 7809828 | Burnett et al. | Oct 2010 | B2 |
| 7886016 | Tormasov et al. | Feb 2011 | B1 |
| 7895158 | Bosloy et al. | Feb 2011 | B2 |
| 7917494 | Mueller et al. | Mar 2011 | B2 |
| 7925631 | Thillai et al. | Apr 2011 | B1 |
| 7962950 | Choo et al. | Jun 2011 | B2 |
| 8015204 | Kaler et al. | Sep 2011 | B2 |
| 8069226 | Momchilov et al. | Nov 2011 | B2 |
| 8099452 | Chkodrov et al. | Jan 2012 | B2 |
| 8117151 | Nakatani et al. | Feb 2012 | B2 |
| 8156151 | Sidman et al. | Apr 2012 | B2 |
| 8180747 | Marinkovic et al. | May 2012 | B2 |
| 8180983 | Jernigan et al. | May 2012 | B1 |
| 8190741 | Wong et al. | May 2012 | B2 |
| 8249885 | Berkowitz et al. | Aug 2012 | B2 |
| 8250397 | Marcy et al. | Aug 2012 | B2 |
| 8260742 | Cognigni et al. | Sep 2012 | B2 |
| 8301994 | Shah et al. | Oct 2012 | B1 |
| 8312242 | Casper et al. | Nov 2012 | B2 |
| 8326874 | Wright et al. | Dec 2012 | B2 |
| 8359467 | Subramanian et al. | Jan 2013 | B2 |
| 8417676 | Petri | Apr 2013 | B2 |
| 8516149 | Edmett Stacey | Aug 2013 | B1 |
| 8548992 | Abramoff et al. | Oct 2013 | B2 |
| 8554800 | Goldentouch | Oct 2013 | B2 |
| 8589349 | Grant et al. | Nov 2013 | B2 |
| 8661070 | Goldsmith et al. | Feb 2014 | B2 |
| 8661539 | Hodges | Feb 2014 | B2 |
| 8667034 | Simon et al. | Mar 2014 | B1 |
| 8688734 | Tidd | Apr 2014 | B1 |
| 8694564 | Guarraci et al. | Apr 2014 | B2 |
| 8700670 | Marathe et al. | Apr 2014 | B2 |
| 8706701 | Stefanov et al. | Apr 2014 | B1 |
| 8818951 | Muntz et al. | Aug 2014 | B1 |
| 8862644 | Lyle et al. | Oct 2014 | B2 |
| 8880474 | Mason et al. | Nov 2014 | B2 |
| 8904503 | Agbabian | Dec 2014 | B2 |
| 8949179 | Besen et al. | Feb 2015 | B2 |
| 8990924 | Chow | Mar 2015 | B2 |
| 8996884 | Hartley et al. | Mar 2015 | B2 |
| 9002805 | Barber et al. | Apr 2015 | B1 |
| 9087215 | Lafever et al. | Jul 2015 | B2 |
| 9129088 | Baschy | Sep 2015 | B1 |
| 9152466 | Dictos et al. | Oct 2015 | B2 |
| 9183303 | Goel et al. | Nov 2015 | B1 |
| 9210116 | Jeng et al. | Dec 2015 | B2 |
| 9218429 | Levy et al. | Dec 2015 | B2 |
| 9231988 | Holt et al. | Jan 2016 | B2 |
| 9239841 | Arnaudov et al. | Jan 2016 | B2 |
| 9251235 | Hurst et al. | Feb 2016 | B1 |
| 9294485 | Allain et al. | Mar 2016 | B2 |
| 9298384 | Kang et al. | Mar 2016 | B2 |
| 9300609 | Beausoleil et al. | Mar 2016 | B1 |
| 9310981 | Lynch et al. | Apr 2016 | B2 |
| 9311324 | Irizarry, Jr. et al. | Apr 2016 | B2 |
| 9325571 | Chen | Apr 2016 | B2 |
| 9330106 | Piasecki et al. | May 2016 | B2 |
| 9336219 | Makkar et al. | May 2016 | B2 |
| 9336227 | Eberlein et al. | May 2016 | B2 |
| 9361473 | Chou Fritz et al. | Jun 2016 | B2 |
| 9411966 | Smith | Aug 2016 | B1 |
| 9413708 | Michael et al. | Aug 2016 | B1 |
| 9424437 | Ancin et al. | Aug 2016 | B1 |
| 9426216 | Subramani et al. | Aug 2016 | B2 |
| 9430669 | Staley et al. | Aug 2016 | B2 |
| 9432457 | Marano et al. | Aug 2016 | B2 |
| 9444869 | Jellison, Jr. et al. | Sep 2016 | B2 |
| 9448893 | Whitehead et al. | Sep 2016 | B1 |
| 9449082 | Leonard | Sep 2016 | B2 |
| 9449182 | Dang et al. | Sep 2016 | B1 |
| 9454534 | Thomas et al. | Sep 2016 | B2 |
| 9471807 | Chakraborty et al. | Oct 2016 | B1 |
| 9477673 | Dwan et al. | Oct 2016 | B2 |
| 9479567 | Koorapati et al. | Oct 2016 | B1 |
| 9479578 | Swanson | Oct 2016 | B1 |
| 9483491 | Wijayaratne et al. | Nov 2016 | B2 |
| 9495478 | Hendrickson et al. | Nov 2016 | B2 |
| 9501490 | Evans et al. | Nov 2016 | B2 |
| 9507795 | Dorman et al. | Nov 2016 | B2 |
| 9529804 | Muddu et al. | Dec 2016 | B1 |
| 9529818 | Catmull et al. | Dec 2016 | B2 |
| 9542404 | Moore et al. | Jan 2017 | B2 |
| 9547559 | Whitehead et al. | Jan 2017 | B2 |
| 9552363 | Novak et al. | Jan 2017 | B2 |
| 9558202 | Lockhart et al. | Jan 2017 | B2 |
| 9563638 | Newhouse | Feb 2017 | B2 |
| 9565227 | Helter et al. | Feb 2017 | B1 |
| 9589131 | Austin | Mar 2017 | B2 |
| 9596246 | Peddada | Mar 2017 | B2 |
| 9614826 | McCorkendale | Apr 2017 | B1 |
| 9632528 | Miyashita et al. | Apr 2017 | B2 |
| 9633037 | Smith et al. | Apr 2017 | B2 |
| 9648088 | Pande et al. | May 2017 | B1 |
| 9652490 | Belanger et al. | May 2017 | B2 |
| 9652741 | Goldberg et al. | May 2017 | B2 |
| 9672261 | Holmes-Higgin et al. | Jun 2017 | B2 |
| 9703800 | Korshunov et al. | Jul 2017 | B1 |
| 9703801 | Melahn et al. | Jul 2017 | B2 |
| 9710535 | Aizman et al. | Jul 2017 | B2 |
| 9716753 | Piyush et al. | Jul 2017 | B2 |
| 9720926 | Aron et al. | Aug 2017 | B2 |
| 9720947 | Aron et al. | Aug 2017 | B2 |
| 9727394 | Xun et al. | Aug 2017 | B2 |
| 9747164 | Auchmoody et al. | Aug 2017 | B1 |
| 9747297 | Penangwala et al. | Aug 2017 | B2 |
| 9754119 | Kilday | Sep 2017 | B1 |
| 9767106 | Duggal et al. | Sep 2017 | B1 |
| 9773051 | Smith | Sep 2017 | B2 |
| 9805050 | Smith et al. | Oct 2017 | B2 |
| 9805054 | Davis et al. | Oct 2017 | B2 |
| 9805106 | McErlean et al. | Oct 2017 | B2 |
| 9817987 | Mityagin | Nov 2017 | B2 |
| 9824090 | Hayrapetian et al. | Nov 2017 | B2 |
| 9830345 | Baars | Nov 2017 | B1 |
| 9838424 | Brady et al. | Dec 2017 | B2 |
| 9852147 | Von Muhlen et al. | Dec 2017 | B2 |
| 9922201 | Von Muhlen et al. | Mar 2018 | B2 |
| 9936020 | Leggette et al. | Apr 2018 | B2 |
| 9953036 | Mackenzie et al. | Apr 2018 | B2 |
| 9971822 | Deardeuff et al. | May 2018 | B1 |
| 10009337 | Fischer et al. | Jun 2018 | B1 |
| 10013440 | Gupta et al. | Jul 2018 | B1 |
| 10037339 | Kleinpeter et al. | Jul 2018 | B1 |
| 10095879 | Kleinpeter et al. | Oct 2018 | B1 |
| 10198182 | Adler et al. | Feb 2019 | B2 |
| 10235378 | Mamidi et al. | Mar 2019 | B1 |
| 10250693 | Colrain et al. | Apr 2019 | B2 |
| 10324903 | Goldberg et al. | Jun 2019 | B1 |
| 10380076 | Wijayaratne et al. | Aug 2019 | B2 |
| 10425477 | Trandafir et al. | Sep 2019 | B2 |
| 10558375 | Muhlestein et al. | Feb 2020 | B2 |
| 10671638 | Goldberg et al. | Jun 2020 | B2 |
| 10671639 | Acheson et al. | Jun 2020 | B1 |
| 10733205 | Goldberg et al. | Aug 2020 | B2 |
| 10922333 | Lai et al. | Feb 2021 | B2 |
| 11288138 | Freilich et al. | Mar 2022 | B1 |
| 20020147742 | Schroeder | Oct 2002 | A1 |
| 20020184242 | Holtz et al. | Dec 2002 | A1 |
| 20020184252 | Holtz et al. | Dec 2002 | A1 |
| 20030033386 | Dahlen et al. | Feb 2003 | A1 |
| 20030145020 | Ngo et al. | Jul 2003 | A1 |
| 20030159136 | Huang et al. | Aug 2003 | A1 |
| 20030167317 | Deen et al. | Sep 2003 | A1 |
| 20030196119 | Raley et al. | Oct 2003 | A1 |
| 20030212657 | Kaluskar et al. | Nov 2003 | A1 |
| 20040002990 | Sander et al. | Jan 2004 | A1 |
| 20040080549 | Lord et al. | Apr 2004 | A1 |
| 20040098371 | Bayliss et al. | May 2004 | A1 |
| 20040098418 | Hein et al. | May 2004 | A1 |
| 20040199572 | Hunt et al. | Oct 2004 | A1 |
| 20040255048 | Lev Ran et al. | Dec 2004 | A1 |
| 20050125411 | Kilian et al. | Jun 2005 | A1 |
| 20050144308 | Harashima et al. | Jun 2005 | A1 |
| 20050149450 | Stefik et al. | Jul 2005 | A1 |
| 20050151738 | Lord et al. | Jul 2005 | A1 |
| 20050198385 | Aust et al. | Sep 2005 | A1 |
| 20050222996 | Yalamanchi | Oct 2005 | A1 |
| 20050256861 | Wong et al. | Nov 2005 | A1 |
| 20050289446 | Moncsko et al. | Dec 2005 | A1 |
| 20060070114 | Wood et al. | Mar 2006 | A1 |
| 20060111880 | Brown et al. | May 2006 | A1 |
| 20060136513 | Ngo et al. | Jun 2006 | A1 |
| 20060155776 | Aust | Jul 2006 | A1 |
| 20060184720 | Sinclair et al. | Aug 2006 | A1 |
| 20060253501 | Langan et al. | Nov 2006 | A1 |
| 20060271602 | Davis et al. | Nov 2006 | A1 |
| 20070016650 | Gilbert et al. | Jan 2007 | A1 |
| 20070016771 | Allison et al. | Jan 2007 | A1 |
| 20070022091 | Styles et al. | Jan 2007 | A1 |
| 20070067349 | Jhaveri et al. | Mar 2007 | A1 |
| 20070088744 | Webber et al. | Apr 2007 | A1 |
| 20070088764 | Yoon et al. | Apr 2007 | A1 |
| 20070130077 | Jagadeesan et al. | Jun 2007 | A1 |
| 20070136391 | Anzai et al. | Jun 2007 | A1 |
| 20070150595 | Bhorania et al. | Jun 2007 | A1 |
| 20070156670 | Lim | Jul 2007 | A1 |
| 20070185852 | Erofeev | Aug 2007 | A1 |
| 20070198540 | Kohl et al. | Aug 2007 | A1 |
| 20070198602 | Ngo et al. | Aug 2007 | A1 |
| 20070208715 | Muehlbauer et al. | Sep 2007 | A1 |
| 20070208763 | Muehlbauer et al. | Sep 2007 | A1 |
| 20070208948 | Costa-Requena et al. | Sep 2007 | A1 |
| 20070234398 | Muehlbauer et al. | Oct 2007 | A1 |
| 20070245353 | Ben-Dor | Oct 2007 | A1 |
| 20070250552 | Lango et al. | Oct 2007 | A1 |
| 20070282914 | Sivapragasam et al. | Dec 2007 | A1 |
| 20070283050 | Savage | Dec 2007 | A1 |
| 20070283403 | Eklund, II et al. | Dec 2007 | A1 |
| 20070288714 | Nakamura | Dec 2007 | A1 |
| 20070299882 | Padgett et al. | Dec 2007 | A1 |
| 20080005195 | Li et al. | Jan 2008 | A1 |
| 20080059474 | Lim | Mar 2008 | A1 |
| 20080104277 | Tian | May 2008 | A1 |
| 20080120129 | Seubert et al. | May 2008 | A1 |
| 20080168183 | Marcy et al. | Jul 2008 | A1 |
| 20080222296 | Lippincott et al. | Sep 2008 | A1 |
| 20080295081 | Albot et al. | Nov 2008 | A1 |
| 20080307255 | Chen et al. | Dec 2008 | A1 |
| 20090024671 | Johnson et al. | Jan 2009 | A1 |
| 20090055921 | Field et al. | Feb 2009 | A1 |
| 20090132400 | Conway | May 2009 | A1 |
| 20090150569 | Kumar et al. | Jun 2009 | A1 |
| 20090182778 | Tormasov | Jul 2009 | A1 |
| 20090183117 | Chang | Jul 2009 | A1 |
| 20090198719 | Dewitt | Aug 2009 | A1 |
| 20090228511 | Atkin et al. | Sep 2009 | A1 |
| 20090271412 | Lacapra et al. | Oct 2009 | A1 |
| 20090271447 | Shin et al. | Oct 2009 | A1 |
| 20090292640 | Heatherly | Nov 2009 | A1 |
| 20100058462 | Chow | Mar 2010 | A1 |
| 20100106687 | Marcy et al. | Apr 2010 | A1 |
| 20100235649 | Jeffries et al. | Sep 2010 | A1 |
| 20100242037 | Xie et al. | Sep 2010 | A1 |
| 20100293209 | Bireley et al. | Nov 2010 | A1 |
| 20100306283 | Johnson et al. | Dec 2010 | A1 |
| 20110014985 | Park et al. | Jan 2011 | A1 |
| 20110040793 | Davidson et al. | Feb 2011 | A1 |
| 20110066668 | Guarraci | Mar 2011 | A1 |
| 20110072143 | Kuo et al. | Mar 2011 | A1 |
| 20110082879 | Hazlewood et al. | Apr 2011 | A1 |
| 20110126296 | Moore | May 2011 | A1 |
| 20110137874 | Grosman et al. | Jun 2011 | A1 |
| 20110195485 | Kale | Aug 2011 | A1 |
| 20110196892 | Xia | Aug 2011 | A1 |
| 20110197196 | Felton et al. | Aug 2011 | A1 |
| 20110218964 | Hagan et al. | Sep 2011 | A1 |
| 20110248821 | Merten | Oct 2011 | A1 |
| 20110271084 | Moue et al. | Nov 2011 | A1 |
| 20110283185 | Obasanjo et al. | Nov 2011 | A1 |
| 20120011098 | Yamada | Jan 2012 | A1 |
| 20120079606 | Evans et al. | Mar 2012 | A1 |
| 20120102539 | Robb et al. | Apr 2012 | A1 |
| 20120254123 | Ferguson et al. | Oct 2012 | A1 |
| 20120254505 | Chishtie et al. | Oct 2012 | A1 |
| 20120278334 | Abjanic | Nov 2012 | A1 |
| 20130013560 | Goldberg et al. | Jan 2013 | A1 |
| 20130014023 | Lee et al. | Jan 2013 | A1 |
| 20130067542 | Gonsalves et al. | Mar 2013 | A1 |
| 20130080785 | Ruhlen et al. | Mar 2013 | A1 |
| 20130086640 | Hashimoto et al. | Apr 2013 | A1 |
| 20130124690 | Liebman | May 2013 | A1 |
| 20130133051 | Riemers | May 2013 | A1 |
| 20130138608 | Smith | May 2013 | A1 |
| 20130144834 | Lloyd et al. | Jun 2013 | A1 |
| 20130152047 | Moorthi et al. | Jun 2013 | A1 |
| 20130179480 | Agarwal et al. | Jul 2013 | A1 |
| 20130191339 | Haden et al. | Jul 2013 | A1 |
| 20130191631 | Ylonen et al. | Jul 2013 | A1 |
| 20130227015 | Mihara et al. | Aug 2013 | A1 |
| 20130238706 | Desai | Sep 2013 | A1 |
| 20130246527 | Viera | Sep 2013 | A1 |
| 20130254777 | Branson et al. | Sep 2013 | A1 |
| 20130258842 | Mizutani et al. | Oct 2013 | A1 |
| 20130262862 | Hartley et al. | Oct 2013 | A1 |
| 20130268480 | Dorman | Oct 2013 | A1 |
| 20130268559 | Reeves | Oct 2013 | A1 |
| 20130282657 | Besen et al. | Oct 2013 | A1 |
| 20130282658 | Besen et al. | Oct 2013 | A1 |
| 20130282785 | Besen et al. | Oct 2013 | A1 |
| 20130290323 | Saib | Oct 2013 | A1 |
| 20130304694 | Barreto et al. | Nov 2013 | A1 |
| 20130304765 | Failelson et al. | Nov 2013 | A1 |
| 20130318160 | Beraka et al. | Nov 2013 | A1 |
| 20130321306 | Bauermeister et al. | Dec 2013 | A1 |
| 20130346557 | Chang et al. | Dec 2013 | A1 |
| 20140033009 | Rein et al. | Jan 2014 | A1 |
| 20140033324 | Kiang et al. | Jan 2014 | A1 |
| 20140047261 | Patiejunas et al. | Feb 2014 | A1 |
| 20140059002 | Lockhart et al. | Feb 2014 | A1 |
| 20140075501 | Srinivasan et al. | Mar 2014 | A1 |
| 20140082145 | Lacapra | Mar 2014 | A1 |
| 20140122425 | Poirier et al. | May 2014 | A1 |
| 20140136635 | Jeng et al. | May 2014 | A1 |
| 20140143543 | Aikas et al. | May 2014 | A1 |
| 20140173694 | Kranz | Jun 2014 | A1 |
| 20140181021 | Montulli et al. | Jun 2014 | A1 |
| 20140181033 | Pawar et al. | Jun 2014 | A1 |
| 20140181053 | Belanger et al. | Jun 2014 | A1 |
| 20140181579 | Whitehead et al. | Jun 2014 | A1 |
| 20140188790 | Hunter et al. | Jul 2014 | A1 |
| 20140188798 | Mackenzie | Jul 2014 | A1 |
| 20140189051 | Hunter | Jul 2014 | A1 |
| 20140189118 | Hunter | Jul 2014 | A1 |
| 20140189355 | Hunter | Jul 2014 | A1 |
| 20140195485 | Dorman | Jul 2014 | A1 |
| 20140195638 | Houston | Jul 2014 | A1 |
| 20140201138 | Dorman et al. | Jul 2014 | A1 |
| 20140201145 | Dorman et al. | Jul 2014 | A1 |
| 20140208124 | Hartley | Jul 2014 | A1 |
| 20140215551 | Allain et al. | Jul 2014 | A1 |
| 20140229457 | Sydell | Aug 2014 | A1 |
| 20140250066 | Calkowski et al. | Sep 2014 | A1 |
| 20140258350 | Duval et al. | Sep 2014 | A1 |
| 20140258418 | Subramani et al. | Sep 2014 | A1 |
| 20140259005 | Jeffrey et al. | Sep 2014 | A1 |
| 20140280129 | Howarth et al. | Sep 2014 | A1 |
| 20140280463 | Hunter | Sep 2014 | A1 |
| 20140282313 | Alfieri | Sep 2014 | A1 |
| 20140282851 | Miller et al. | Sep 2014 | A1 |
| 20140289195 | Chan et al. | Sep 2014 | A1 |
| 20140297734 | Lacapra et al. | Oct 2014 | A1 |
| 20140297759 | Mody | Oct 2014 | A1 |
| 20140310175 | Coronel | Oct 2014 | A1 |
| 20140317128 | Simeonov et al. | Oct 2014 | A1 |
| 20140359085 | Chen | Dec 2014 | A1 |
| 20140372376 | Smith et al. | Dec 2014 | A1 |
| 20140375657 | Fortini et al. | Dec 2014 | A1 |
| 20140379647 | Smith et al. | Dec 2014 | A1 |
| 20150012616 | Pearl et al. | Jan 2015 | A1 |
| 20150026222 | Litzenberger et al. | Jan 2015 | A1 |
| 20150026597 | Gadamsetty et al. | Jan 2015 | A1 |
| 20150026604 | Mulukuri et al. | Jan 2015 | A1 |
| 20150026751 | Yokoi | Jan 2015 | A1 |
| 20150058932 | Faitelson et al. | Feb 2015 | A1 |
| 20150088817 | Dwan et al. | Mar 2015 | A1 |
| 20150089019 | Chou | Mar 2015 | A1 |
| 20150095641 | Drewry | Apr 2015 | A1 |
| 20150100482 | Zamer et al. | Apr 2015 | A1 |
| 20150100546 | Eberlein et al. | Apr 2015 | A1 |
| 20150100547 | Holmes-Higgin et al. | Apr 2015 | A1 |
| 20150100705 | Abe et al. | Apr 2015 | A1 |
| 20150101021 | Mc Erlean et al. | Apr 2015 | A1 |
| 20150120763 | Grue et al. | Apr 2015 | A1 |
| 20150134600 | Eisner et al. | May 2015 | A1 |
| 20150154418 | Redberg | Jun 2015 | A1 |
| 20150163206 | McCarthy et al. | Jun 2015 | A1 |
| 20150163302 | Armstrong et al. | Jun 2015 | A1 |
| 20150172283 | Omnes et al. | Jun 2015 | A1 |
| 20150172412 | Escriva et al. | Jun 2015 | A1 |
| 20150178516 | Mityagin | Jun 2015 | A1 |
| 20150186667 | Yao et al. | Jul 2015 | A1 |
| 20150186668 | Whaley et al. | Jul 2015 | A1 |
| 20150193347 | Kluesing et al. | Jul 2015 | A1 |
| 20150205977 | Rundle et al. | Jul 2015 | A1 |
| 20150207844 | Tataroiu et al. | Jul 2015 | A1 |
| 20150220917 | Aabye et al. | Aug 2015 | A1 |
| 20150222431 | Guido Van Rossum | Aug 2015 | A1 |
| 20150222580 | Grue | Aug 2015 | A1 |
| 20150222615 | Allain et al. | Aug 2015 | A1 |
| 20150242521 | Hunter et al. | Aug 2015 | A1 |
| 20150244692 | Liu et al. | Aug 2015 | A1 |
| 20150244795 | Cantwell et al. | Aug 2015 | A1 |
| 20150248384 | Luo et al. | Sep 2015 | A1 |
| 20150249647 | Mityagin et al. | Sep 2015 | A1 |
| 20150277802 | Oikarinen et al. | Oct 2015 | A1 |
| 20150277969 | Strauss et al. | Oct 2015 | A1 |
| 20150278024 | Barman et al. | Oct 2015 | A1 |
| 20150278323 | Melahn et al. | Oct 2015 | A1 |
| 20150278397 | Hendrickson et al. | Oct 2015 | A1 |
| 20150280959 | Vincent et al. | Oct 2015 | A1 |
| 20150281360 | Lacapra et al. | Oct 2015 | A1 |
| 20150286833 | Resch et al. | Oct 2015 | A1 |
| 20150288680 | Leggette | Oct 2015 | A1 |
| 20150296012 | Piyush et al. | Oct 2015 | A1 |
| 20150310035 | Godman et al. | Oct 2015 | A1 |
| 20150318941 | Zheng et al. | Nov 2015 | A1 |
| 20150356111 | Kalsi et al. | Dec 2015 | A1 |
| 20150358408 | Fukatani et al. | Dec 2015 | A1 |
| 20150370483 | Schoebel-Theuer et al. | Dec 2015 | A1 |
| 20150370825 | Outcalt et al. | Dec 2015 | A1 |
| 20160028796 | Garcia et al. | Jan 2016 | A1 |
| 20160034508 | Aron et al. | Feb 2016 | A1 |
| 20160036822 | Kim et al. | Feb 2016 | A1 |
| 20160042087 | Yang | Feb 2016 | A1 |
| 20160050177 | Cue et al. | Feb 2016 | A1 |
| 20160055021 | Beveridge et al. | Feb 2016 | A1 |
| 20160062839 | Kapoor | Mar 2016 | A1 |
| 20160065672 | Savage et al. | Mar 2016 | A1 |
| 20160070741 | Lin et al. | Mar 2016 | A1 |
| 20160085769 | Penangwala et al. | Mar 2016 | A1 |
| 20160085837 | Kotagiri et al. | Mar 2016 | A1 |
| 20160092312 | Dornquast et al. | Mar 2016 | A1 |
| 20160103750 | Cooper et al. | Apr 2016 | A1 |
| 20160110374 | Wetherall et al. | Apr 2016 | A1 |
| 20160112508 | Sher | Apr 2016 | A1 |
| 20160140139 | Torres et al. | May 2016 | A1 |
| 20160140197 | Gast et al. | May 2016 | A1 |
| 20160140201 | Cowling et al. | May 2016 | A1 |
| 20160182494 | Lissounov et al. | Jun 2016 | A1 |
| 20160188465 | Almasi et al. | Jun 2016 | A1 |
| 20160188628 | Hartman et al. | Jun 2016 | A1 |
| 20160205100 | Brannon | Jul 2016 | A1 |
| 20160210238 | Frank et al. | Jul 2016 | A1 |
| 20160224989 | Lissounov et al. | Aug 2016 | A1 |
| 20160285890 | Beausoleil et al. | Sep 2016 | A1 |
| 20160291856 | Von Muhlen et al. | Oct 2016 | A1 |
| 20160292179 | von Muhlen | Oct 2016 | A1 |
| 20160292443 | Von Muhlen et al. | Oct 2016 | A1 |
| 20160294916 | Daher et al. | Oct 2016 | A1 |
| 20160299917 | Koos et al. | Oct 2016 | A1 |
| 20160301619 | Bashir et al. | Oct 2016 | A1 |
| 20160308950 | Bouvrette et al. | Oct 2016 | A1 |
| 20160308966 | Zhang et al. | Oct 2016 | A1 |
| 20160315941 | Dang et al. | Oct 2016 | A1 |
| 20160321275 | Yap et al. | Nov 2016 | A1 |
| 20160321287 | Luthra et al. | Nov 2016 | A1 |
| 20160321293 | Auer | Nov 2016 | A1 |
| 20160323358 | Malhotra et al. | Nov 2016 | A1 |
| 20160330260 | Ruge | Nov 2016 | A1 |
| 20160334967 | Rottler et al. | Nov 2016 | A1 |
| 20160335278 | Tabaaloute et al. | Nov 2016 | A1 |
| 20160337356 | Simon et al. | Nov 2016 | A1 |
| 20160342479 | Chen et al. | Nov 2016 | A1 |
| 20160349999 | Adler et al. | Dec 2016 | A1 |
| 20160350322 | Fan et al. | Dec 2016 | A1 |
| 20160352752 | Bush et al. | Dec 2016 | A1 |
| 20160353447 | White et al. | Dec 2016 | A1 |
| 20160357720 | Thimbleby | Dec 2016 | A1 |
| 20160366118 | Wang | Dec 2016 | A1 |
| 20160371296 | Passey et al. | Dec 2016 | A1 |
| 20160371358 | Lee et al. | Dec 2016 | A1 |
| 20170005974 | Wheeler et al. | Jan 2017 | A1 |
| 20170006097 | Johnson et al. | Jan 2017 | A1 |
| 20170024410 | Pola | Jan 2017 | A1 |
| 20170026379 | Lu et al. | Jan 2017 | A1 |
| 20170039216 | Fan et al. | Feb 2017 | A1 |
| 20170052717 | Rawat et al. | Feb 2017 | A1 |
| 20170075907 | Goswami et al. | Mar 2017 | A1 |
| 20170075920 | McKay et al. | Mar 2017 | A1 |
| 20170075921 | Benton et al. | Mar 2017 | A1 |
| 20170078383 | Murstein et al. | Mar 2017 | A1 |
| 20170078384 | Trandafir et al. | Mar 2017 | A1 |
| 20170103754 | Higbie et al. | Apr 2017 | A1 |
| 20170109370 | Newhouse | Apr 2017 | A1 |
| 20170109385 | Aronovich et al. | Apr 2017 | A1 |
| 20170123931 | Aizman et al. | May 2017 | A1 |
| 20170124111 | Sharma | May 2017 | A1 |
| 20170124170 | Koorapati et al. | May 2017 | A1 |
| 20170131934 | Kaczmarczyk et al. | May 2017 | A1 |
| 20170132269 | Jiao et al. | May 2017 | A1 |
| 20170149885 | Kaplan et al. | May 2017 | A1 |
| 20170168670 | Sovalin et al. | Jun 2017 | A1 |
| 20170177613 | Sharma et al. | Jun 2017 | A1 |
| 20170185687 | Pai et al. | Jun 2017 | A1 |
| 20170192656 | Pedrick et al. | Jul 2017 | A1 |
| 20170192856 | Chin et al. | Jul 2017 | A1 |
| 20170192998 | Sergeev et al. | Jul 2017 | A1 |
| 20170193002 | Shvachko et al. | Jul 2017 | A1 |
| 20170193040 | Agrawal et al. | Jul 2017 | A1 |
| 20170193448 | Piyush et al. | Jul 2017 | A1 |
| 20170195457 | Smith, II et al. | Jul 2017 | A1 |
| 20170220596 | Smith et al. | Aug 2017 | A1 |
| 20170230702 | Sarosi et al. | Aug 2017 | A1 |
| 20170235759 | Altaparmakov et al. | Aug 2017 | A1 |
| 20170270136 | Chen et al. | Sep 2017 | A1 |
| 20170270306 | Dorwin | Sep 2017 | A1 |
| 20170289210 | Pai et al. | Oct 2017 | A1 |
| 20170300505 | Belmanu Sadananda et al. | Oct 2017 | A1 |
| 20170302521 | Lui et al. | Oct 2017 | A1 |
| 20170302737 | Piyush et al. | Oct 2017 | A1 |
| 20170308443 | Lai et al. | Oct 2017 | A1 |
| 20170308565 | Broll et al. | Oct 2017 | A1 |
| 20170308598 | Goldberg et al. | Oct 2017 | A1 |
| 20170308599 | Newhouse | Oct 2017 | A1 |
| 20170308602 | Raghunathan et al. | Oct 2017 | A1 |
| 20170308681 | Gould et al. | Oct 2017 | A1 |
| 20170314898 | Syverson et al. | Nov 2017 | A1 |
| 20170316032 | Kamalaksha et al. | Nov 2017 | A1 |
| 20170316222 | Muhlestein et al. | Nov 2017 | A1 |
| 20170331893 | Crofton et al. | Nov 2017 | A1 |
| 20170351701 | Aron et al. | Dec 2017 | A1 |
| 20170357663 | Giampaolo | Dec 2017 | A1 |
| 20180004442 | Hnanicek et al. | Jan 2018 | A1 |
| 20180018115 | Ikegame | Jan 2018 | A1 |
| 20180039652 | Nichols et al. | Feb 2018 | A1 |
| 20180039788 | Leggette | Feb 2018 | A1 |
| 20180084045 | Nichols et al. | Mar 2018 | A1 |
| 20180089349 | Rezgui | Mar 2018 | A1 |
| 20180121370 | Mukkamala et al. | May 2018 | A1 |
| 20180129821 | Havewala et al. | May 2018 | A1 |
| 20180144263 | Saxena et al. | May 2018 | A1 |
| 20180150477 | Jewell et al. | May 2018 | A1 |
| 20180157825 | Eksten et al. | Jun 2018 | A1 |
| 20180176082 | Katz et al. | Jun 2018 | A1 |
| 20180176093 | Katz et al. | Jun 2018 | A1 |
| 20180176120 | Katz et al. | Jun 2018 | A1 |
| 20180181549 | Hileman et al. | Jun 2018 | A1 |
| 20180189369 | Baek et al. | Jul 2018 | A1 |
| 20180196643 | Dolby et al. | Jul 2018 | A1 |
| 20180246946 | Sadhwani | Aug 2018 | A1 |
| 20180260125 | Botes et al. | Sep 2018 | A1 |
| 20180260411 | Deardeuff et al. | Sep 2018 | A1 |
| 20180270534 | Badawiyeh | Sep 2018 | A1 |
| 20180329969 | Abrams | Nov 2018 | A1 |
| 20180349408 | Jewell et al. | Dec 2018 | A1 |
| 20180364950 | Spillane et al. | Dec 2018 | A1 |
| 20180365236 | Wang et al. | Dec 2018 | A1 |
| 20190005139 | Ford et al. | Jan 2019 | A1 |
| 20190034507 | Duttagupta et al. | Jan 2019 | A1 |
| 20190050833 | Hu et al. | Feb 2019 | A1 |
| 20190073274 | Yokoyama | Mar 2019 | A1 |
| 20190102370 | Nelson et al. | Apr 2019 | A1 |
| 20190114427 | Suryanarayana et al. | Apr 2019 | A1 |
| 20190179714 | Karthikeyan et al. | Jun 2019 | A1 |
| 20190205407 | Ying et al. | Jul 2019 | A1 |
| 20190205423 | Haven et al. | Jul 2019 | A1 |
| 20190205424 | Jubb, IV | Jul 2019 | A1 |
| 20190205425 | Goldberg et al. | Jul 2019 | A1 |
| 20190205548 | Lee et al. | Jul 2019 | A1 |
| 20190207940 | Kleinpeter et al. | Jul 2019 | A1 |
| 20190208013 | Lai | Jul 2019 | A1 |
| 20190208014 | Goldberg et al. | Jul 2019 | A1 |
| 20190266342 | Kleinpeter et al. | Aug 2019 | A1 |
| 20190332231 | Rogers et al. | Oct 2019 | A1 |
| 20190332688 | Valentine et al. | Oct 2019 | A1 |
| 20190361793 | Goldberg | Nov 2019 | A1 |
| 20200249877 | McIlroy et al. | Aug 2020 | A1 |
| 20210042325 | Goldberg et al. | Feb 2021 | A1 |
| 20220019385 | Karr et al. | Jan 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2008202290 | May 2010 | AU |
| 2017100968 | Sep 2017 | AU |
| 2018395858 | Nov 2021 | AU |
| 2609083 | Apr 2009 | CA |
| 1255748 | May 2006 | CN |
| 101080714 | Nov 2007 | CN |
| 101460930 | Jun 2009 | CN |
| 101930442 | Dec 2010 | CN |
| 102413313 | Apr 2012 | CN |
| 102693302 | Sep 2012 | CN |
| 103412897 | Nov 2013 | CN |
| 103716364 | Apr 2014 | CN |
| 103812912 | May 2014 | CN |
| 104573127 | Apr 2015 | CN |
| 104685485 | Jun 2015 | CN |
| 104813685 | Jul 2015 | CN |
| 104885048 | Sep 2015 | CN |
| 105138478 | Dec 2015 | CN |
| 105474206 | Apr 2016 | CN |
| 105593839 | May 2016 | CN |
| 105740418 | Jul 2016 | CN |
| 106156359 | Nov 2016 | CN |
| 106462544 | Feb 2017 | CN |
| 106576078 | Apr 2017 | CN |
| 106657170 | May 2017 | CN |
| 106897352 | Jun 2017 | CN |
| 106941504 | Jul 2017 | CN |
| 107247749 | Oct 2017 | CN |
| 107426318 | Dec 2017 | CN |
| 1422901 | May 2004 | EP |
| 2757491 | Jul 2014 | EP |
| 2911068 | Aug 2015 | EP |
| 3707615 | Sep 2020 | EP |
| 2399663 | Sep 2004 | GB |
| 2494047 | Feb 2013 | GB |
| 2501008 | Oct 2013 | GB |
| 2524612 | Sep 2015 | GB |
| 2007102461 | Apr 2007 | JP |
| 2007115247 | May 2007 | JP |
| 2007527053 | Sep 2007 | JP |
| 2008250903 | Oct 2008 | JP |
| 2008541263 | Nov 2008 | JP |
| 2009505196 | Feb 2009 | JP |
| 2011128833 | Jun 2011 | JP |
| 2011233069 | Nov 2011 | JP |
| 2013088927 | May 2013 | JP |
| 2014026331 | Feb 2014 | JP |
| 2014524210 | Sep 2014 | JP |
| 2014524621 | Sep 2014 | JP |
| 2015527646 | Sep 2015 | JP |
| 2015210818 | Nov 2015 | JP |
| 2016181250 | Oct 2016 | JP |
| 2017182790 | Oct 2017 | JP |
| 2017529625 | Oct 2017 | JP |
| 100678921 | Feb 2007 | KR |
| 20110139739 | Dec 2011 | KR |
| 2007010100 | Jan 2007 | WO |
| 2008095375 | Aug 2008 | WO |
| 2009126941 | Oct 2009 | WO |
| 2014080547 | May 2014 | WO |
| 2015055035 | Apr 2015 | WO |
| 2017187311 | Nov 2017 | WO |
| 2019133230 | Jul 2019 | WO |
| Entry |
|---|
| Summons to attend oral proceedings pursuant to Rule 115(1) EPC for European Application No. 18837007.6 mailed on Feb. 15, 2023, 7 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/179,946, mailed Aug. 31, 2023, 34 pages. |
| Notice of Allowance for U.S. Appl. No. 16/935,995 mailed on Aug. 31, 2023, 2 pages. |
| Rejection Decision for Chinese Application No. 201880083815.7 mailed on Sep. 1, 2023, 12 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,486, mailed Mar. 2, 2023, 28 pages. |
| Notice of Allowance from U.S. Appl. No. 16/991,822, mailed Mar. 1, 2023, 07 pages. |
| Shields I., et al., “Learn Linux, 101: Manage File Permissions and Ownership,” https://developer.IBM.com/ technologies/linux/tutorials/l-Ipic1-104-5/, Jan. 27, 2016, 21 pages. |
| Tridgell A,., et al., “Rsync,” edited on Nov. 24, 2017, retrieved from https://en.wikipedia.org/wikipedia.org/w/index.php?title=Rsync&oldid=811846440#cite_note-pool-25, on Apr. 20, 2021, 7 pages. |
| UCAR, “Setting File and Directory Permissions,” Sep. 2017, retrieved from https://web.archive.org/web/20170920093821/https://www2.cisl.ucar.edu/user-support/setting-file-and-directory-permissions, on Dec. 8, 2019, 5 pages. |
| Communication under Rule 71(3) EPC for European Application No. 18830580.9 mailed on Mar. 17, 2023, 79 pages. |
| Communication under Rule 71(3) EPC for European Application No. 18839958.8 mailed on Mar. 17, 2023, 154 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880068962.7 mailed on Mar. 14, 2023, 26 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880073349.4 mailed on Mar. 13, 2023, 25 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880075620.8 mailed on Mar. 1, 2023, 22 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880077284.0 mailed on Feb. 27, 2023, 11 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880078587.4 malled on Mar. 9, 2023, 21 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880078715.5 mailed on Mar. 8, 2023, 11 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880079908.2 mailed on Mar. 13, 2023, 20 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880083720.5 malled on Mar. 13, 2023, 21 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880083815.7 mailed on Mar. 15, 2023, 18 pages. |
| Office Action for Canadian Application No. 3082925 mailed on Mar. 10, 2023, 3 pages. |
| Office Action for Canadian Application No. 3084056 mailed on Mar. 23, 2023, 5 pages. |
| Communication under Rule 71 (3) EPC of intention to grant for European Application No. 18836317.0 mailed on Feb. 10, 2023, 94 pages. |
| Notice of Allowance for U.S. Appl. No. 16/935,995 mailed on Feb. 1, 2023, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 16/935,995 mailed Feb. 8, 2023, 02 pages. |
| Notice of Allowance from U.S. Appl. No. 16/991,822 mailed Feb. 15, 2023, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 17/230,249, mailed Feb. 8, 2023, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 17/230,249 mailed Feb. 15, 2023, 02 pages. |
| Summons to attend oral proceedings pursuant to Rule 115(1) EPC for European Application No. 18833555.8, malled on Dec. 12, 2022, 7 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18836317.0 mailed on May 26, 2023, 95 pages. |
| Communication under Rule 71(3) EPC for European Application No. 18839958.8 mailed on Jun. 23, 2023, 154 pages. |
| Notice of Allowance from U.S. Appl. No. 16/935,995 mailed Jun. 28, 2023, 10 pages. |
| Notice of Reasons for Refusal for Japanese Application No. 2020-536083 mailed on May 26, 2023, 6 pages. |
| Office Action for Canadian Application No. 3083530 mailed on Jun. 22, 2023, 3 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 18840109.5 mailed on May 26, 2023, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,486, mailed Sep. 20, 2023, 10 pages. |
| Notification of the First Office Action and Search Report for Chinese Application No. 201880083719.2 mailed on Sep. 8, 2023, 17 pages. |
| Notification of the Second Office Action for Chinese Application No. 201880075620.8 mailed on Sep. 16, 2023, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/076,538, mailed May 31, 2023, 22 pages. |
| Notice of Allowance from U.S. Appl. No. 16/991,822, mailed May 5, 2023, 07 pages. |
| Advisory Action from U.S. Appl. No. 17/179,946, mailed Jul. 25, 2023, 3 pages. |
| Communication pursuant to Article 94(3) EPC for European Application No. 18836962.3 mailed on Apr. 26, 2023, 5 pages. |
| Communication under Rule 71(3) EPC for European Application No. 18839962.0 mailed on Apr. 4, 2023, 92 pages. |
| Final Office Action from U.S. Appl. No. 17/179,946, mailed Mar. 31, 2023, 32 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/187,942, mailed Apr. 27, 2023, 36 pages. |
| Notice of Allowance from U.S. Appl. No. 16/935,995, mailed Apr. 10, 2023, 02 pages. |
| Notice of Allowance from U.S. Appl. No. 16/991,822, mailed Apr. 25, 2023, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 17/204,208, mailed Apr. 10, 2023, 18 pages. |
| Notice of Allowance from U.S. Appl. No. 17/204,208, mailed Apr. 18, 2023, 15 pages. |
| Notice of Allowance from U.S. Appl. No. 17/230,249, mailed Apr. 4, 2023, 09 pages. |
| Notice of Allowance from U.S. Appl. No. 17/230,249, mailed Apr. 18, 2023, 02 pages. |
| Preliminary Opinion of the Examining Division for European Application No. 18836962.3 mailed on Apr. 20, 2023, 4 pages. |
| Final Office Action from U.S. Appl. No. 15/857,588, mailed Aug. 3, 2020, 16 pages. |
| Final Office Action from U.S. Appl. No. 16/991,822, mailed Jun. 13, 2022, 29 pages. |
| Final Office Action from U.S. Appl. No. 15/857,713, mailed Apr. 7, 2021, 22 pages. |
| Final Office Action from U.S. Appl. No. 15/857,713, mailed Jul. 16, 2020, 22 pages. |
| Final Office Action from U.S. Appl. No. 15/857,725, mailed Apr. 6, 2022, 13 pages. |
| Final Office Action from U.S. Appl. No. 15/857,725, mailed Jun. 1, 2021, 14 pages. |
| Final Office Action from U.S. Appl. No. 15/857,725, mailed Oct. 26, 2020, 14 pages. |
| Final Office Action from U.S. Appl. No. 15/857,729, mailed Dec. 7, 2020, 15 pages. |
| Final Office Action from U.S. Appl. No. 15/857,729, mailed Mar. 11, 2020, 16 pages. |
| Final Office Action from U.S. Appl. No. 15/857,732, mailed Feb. 26, 2021, 35 pages. |
| Final Office Action from U.S. Appl. No. 15/857,732, mailed May 1, 2020, 26 pages. |
| Final Office Action from U.S. Appl. No. 15/857,772, mailed Mar. 26, 2020, 12 pages. |
| Final Office Action from U.S. Appl. No. 15/857,772, mailed Nov. 12, 2020, 18 pages. |
| Final Office Action from U.S. Appl. No. 15/857,779, mailed Jun. 17, 2020, 25 pages. |
| Final Office Action from U.S. Appl. No. 15/857,779, mailed Mar. 2, 2021, 26 pages. |
| Final Office Action from U.S. Appl. No. 15/857,784, mailed Apr. 3, 2020, 18 pages. |
| Final Office Action from U.S. Appl. No. 15/857,784, mailed Oct. 30, 2020, 20 pages. |
| Final Office Action from U.S. Appl. No. 15/857,789, mailed Feb. 24, 2021, 21 pages. |
| Final Office Action from U.S. Appl. No. 15/857,789, mailed Jun. 5, 2020, 15 pages. |
| Final Office Action from U.S. Appl. No. 15/857,789, mailed Nov. 3, 2021, 17 pages. |
| Final Office Action from U.S. Appl. No. 15/858,125, mailed Jun. 26, 2020, 15 pages. |
| Final Office Action from U.S. Appl. No. 15/858,207, mailed Jul. 2, 2020, 16 pages. |
| Final Office Action from U.S. Appl. No. 15/858,430, mailed Apr. 15, 2021, 12 pages. |
| Final Office Action from U.S. Appl. No. 15/858,430, mailed Jun. 12, 2020, 11 pages. |
| Final Office Action from U.S. Appl. No. 15/863,748, mailed Dec. 20, 2019, 19 pages. |
| Final Office Action from U.S. Appl. No. 15/863,748, mailed Feb. 5, 2021, 24 pages. |
| Final Office Action from U.S. Appl. No. 15/863,751, mailed Dec. 16, 2020, 19 pages. |
| Final Office Action from U.S. Appl. No. 15/863,751, mailed Mar. 24, 2020, 16 pages. |
| Final Office Action from U.S. Appl. No. 15/867,486, mailed Aug. 9, 2021, 35 pages. |
| Final Office Action from U.S. Appl. No. 15/867,486, mailed Nov. 3, 2020, 38 pages. |
| Final Office Action from U.S. Appl. No. 15/867,486, mailed Oct. 5, 2022, 40 pages. |
| Final Office Action from U.S. Appl. No. 15/867,496, mailed Apr. 10, 2020, 14 pages. |
| Final Office Action from U.S. Appl. No. 15/867,505, mailed Feb. 8, 2021, 25 pages. |
| Final Office Action from U.S. Appl. No. 15/867,571, mailed Sep. 3, 2020, 34 pages. |
| Final Office Action from U.S. Appl. No. 15/867,612, mailed Sep. 28, 2020, 16 pages. |
| Final Office Action from U.S. Appl. No. 15/868,511, mailed Jul. 14, 2020, 10 pages. |
| Final Office Action from U.S. Appl. No. 15/870,179, mailed Apr. 16, 2020, 6 pages. |
| Final Office Action from U.S. Appl. No. 16/833,348, mailed Apr. 8, 2022, 14 pages. |
| Final Office Action from U.S. Appl. No. 16/887,714, mailed Dec. 13, 2021, 52 pages. |
| Final Office Action from U.S. Appl. No. 16/935,995, mailed Aug. 25, 2022, 11 pages. |
| Final Office Action from U.S. Appl. No. 16/991,798, mailed Jun. 24, 2022, 19 pages. |
| Final Office Action from U.S. Appl. No. 17/076,538, mailed Dec. 16, 2022, 21 pages. |
| Final Office Action from U.S. Appl. No. 17/204,208, mailed Oct. 18, 2022, 21 pages. |
| “Give Access to a Subdirectory Without Giving Access to Parent Directories,” Dec. 17, 2012, Superuser, https://superuser.com/questions/520537/give-access-to-a-subdirectory-without-giving-access-to-parent-directories, 5 pages. |
| Gladinet Inc., “CentreStack,” Boca Raton, FL, May 30, 2015, Available online at https://webcache.googleusercontent.com/search?q=cache:R3ogLpu7xJYJ and https://www.gladinet.com/library/admin/index.htm +&cd=1&hl=en&ct=clnk&gl=us, visited on Feb. 8, 2018. |
| Grunbacher., et al., “POSIX Access Control Lists on Linux,” Usenix, https://www.usenix.org/legacy/publications/library/proceedings/usenix03/tech/freenix03/full_papers/gruenbacher/gruenbacher_html/main.html, Apr. 4, 2003, pp. 1-23. |
| “How to Create Home Folders for User Accounts”, retrieved from https://www.manageengine.com/products/ad-manager/admanager-kb/create-home-folders-for-user-accounts.html 2015, pp. 1-5. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/065097 dated Mar. 19, 2019, 14 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/065347 dated Apr. 2, 2019, 16 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/064659 dated Mar. 19, 2019,13 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,789, mailed Mar. 14, 2022, 18 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,789, mailed Sep. 29, 2020, 19 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,110, mailed Feb. 24, 2020, 13 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,125, mailed Dec. 31, 2019, 12 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,146, mailed Apr. 1, 2020, 23 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,192, mailed Jun. 12, 2020, 13 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,207, mailed Jan. 22, 2020, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,207, mailed Sep. 30, 2020, 20 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,357, mailed Jan. 7, 2020, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,410, mailed Nov. 29, 2019, 14 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,430, mailed Jun. 24, 2021, 11 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,430, mailed Nov. 26, 2019, 10 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/858,430, mailed Oct. 6, 2020, 11 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/863,748, mailed Aug. 18, 2020, 25 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/863,751, mailed Jul. 7, 2020, 16 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/863,751, mailed Nov. 6, 2019, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/863,815, mailed Mar. 18, 2020, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,486, mailed Apr. 3, 2020, 36 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,486, mailed Feb. 5, 2021, 37 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,486, mailed Mar. 14, 2022, 55 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,496, mailed Nov. 13, 2019, 12 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,505, mailed Aug. 19, 2020, 21 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,571, mailed Feb. 26, 2020, 28 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,612, mailed Apr. 3, 2020, 14 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/867,612, mailed Dec. 8, 2020, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/868,505, mailed Apr. 13, 2020, 12 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/868,505, mailed Nov. 14, 2019, 7 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/870,179, mailed Oct. 7, 2019, 6 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/026,531, mailed Jul. 27, 2020, 22 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/118,514, mailed Nov. 27, 2019, 13 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/833,348, mailed Sep. 16, 2021, 22 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/887,714, mailed Jun. 28, 2021, 63 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/908,186, mailed Oct. 4, 2021, 7 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/935,995, mailed Feb. 9, 2022, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/991,822, mailed Dec. 8, 2021, 27 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/136,849, mailed Jun. 1, 2022, 12 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/179,946, mailed Oct. 5, 2022, 28 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/204,208, mailed Mar. 29, 2022, 24 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/230,249, mailed Nov. 4, 2022, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,732, mailed Jan. 4, 2022, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,715, mailed Aug. 7, 2020, 5 pages. |
| Notice of Acceptance for Australian Application No. 2018393933, mailed on Sep. 23, 2021, 3 pages. |
| Notice of Acceptance for Australian Application No. 2018395856, mailed on Aug. 27, 2021, 3 pages. |
| Notice of acceptance for Australian Application No. 2018395857, mailed on Jul. 20, 2021, 3 pages. |
| Notice of Acceptance for Australian Application No. 2018395858 dated Jul. 7, 2021, 3 pages. |
| Notice of acceptance for Australian Application No. 2018395919, mailed on Jul. 21, 2021, 3 pages. |
| Notice of Acceptance for Australian Application No. 2018395920 mailed on Apr. 27, 2021, 3 pages. |
| Notice of Acceptance for Australian Application No. 2018397572 dated Jul. 14, 2021, 3 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,588, mailed Oct. 7, 2020, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,713, mailed Oct. 1, 2021, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,221, mailed Apr. 10, 2020, 19 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,221, mailed Feb. 25, 2020, 19 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,221, mailed Jan. 17, 2020, 22 pages. |
| Notice of Allowance from U.S. Appl. No. 15/873,693, mailed Dec. 26, 2019, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/873,693, mailed Jan. 30, 2020, 5 pages. |
| Notice of Allowance from U.S. Appl. No. 15/873,693, mailed Oct. 29, 2019, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 16/026,531, mailed Apr. 6, 2021, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 16/026,531, mailed Jan. 29, 2021, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 16/118,514, mailed Apr. 8, 2020, 17 pages. |
| Notice of Allowance from U.S. Appl. No. 16/118,514, mailed May 20, 2020, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 16/887,714, mailed Apr. 28, 2022, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 16/887,714, mailed Jun. 2, 2022, 7 pages. |
| Notice of Allowance from U.S. Appl. No. 16/887,714, mailed May 16, 2022, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 16/897,884, mailed Feb. 7, 2022, 17 pages. |
| Notice of Allowance from U.S. Appl. No. 16/897,884, mailed Feb. 16, 2022, 14 pages. |
| Notice of Allowance from U.S. Appl. No. 16/908,186, mailed Feb. 17, 2022, 7 pages. |
| Notice of Allowance from U.S. Appl. No. 16/908,186, mailed Jun. 2, 2022, 7 pages. |
| Notice of Allowance from U.S. Appl. No. 17/077,719, mailed Apr. 28, 2022, 13 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,779, mailed Mar. 2, 2022, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,430, mailed Jul. 20, 2022, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 16/833,348, mailed Sep. 16, 2022, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 16/833,348, mailed Sep. 30, 2022, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 16/887,714, mailed Jul. 29, 2022, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 16/908,186, mailed Sep. 15, 2022, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 16/991,798, mailed Sep. 8, 2022, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 16/991,798, mailed Sep. 20, 2022, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 17/136,849, mailed Sep. 7, 2022, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 17/136,849, mailed Sep. 28, 2022, 2 pages. |
| Notice of Preliminary Rejection for Korean Application No. 10-2020-7016022 mailed on Dec. 15, 2021, 12 pages. |
| Notice of Preliminary Rejection for Korean Application No. 10-2020-7016208 mailed on Dec. 17, 2021, 6 pages. |
| Notice of Preliminary Rejection for Korean Application No. 10-2020-7018226 mailed on Jan. 20, 2022, 8 pages. |
| Notice of Preliminary Rejection for Korean Application No. 10-2020-7018240 mailed on Jan. 14, 2022, 10 pages. |
| Notice of Preliminary Rejection for Korean Application No. 10-2020-7018403 mailed on Jan. 20, 2022, 4 pages. |
| Notice of Reason for Refusal for Japanese Application No. 2020529752 mailed on Jun. 21, 2021, 13 pages. |
| Notice of Reasons for Refusal for Japanese Application No. 2020-521435, mailed on Aug. 6, 2021, 20 pages. |
| NTFS, “File and Folder Basic NTFS Permissions,” Dec. 7, 2016, retrieved from http://www.ntfs.com/ntfs-permissions-file-folder.htm, on Jan. 14, 2020, 9 Pages. |
| Office Action for Canada Application No. 3,081,372 mailed on Jun. 7, 2021, 4 pages. |
| Office Action for Canadian Application No. 3078982 mailed on Aug. 19, 2022, 6 pages. |
| Office Action for Canadian Application No. 3078982 mailed on Jun. 1, 2021, 3 pages. |
| Office Action for Canadian Application No. 3082925 mailed on Jun. 16, 2021, 4 pages. |
| Office Action for Canadian Application No. 3082925 mailed on Sep. 9, 2022, 5 pages. |
| Office Action for Canadian Application No. 3083530 mailed on Jul. 7, 2021, 4 pages. |
| Office Action for Canadian Application No. 3083530 mailed on Nov. 9, 2022, 6 pages. |
| Office Action for Canadian Application No. 3084056 mailed on Aug. 15, 2022, 4 pages. |
| Office Action for Canadian Application No. 3084056 mailed on Jul. 7, 2021, 4 pages. |
| Office Action for Canadian Application No. 3084060 mailed on Jul. 28, 2021, 3 pages. |
| Office Action for Canadian Application No. 3,084,312 mailed on Apr. 8, 2022, 3 pages. |
| Office Action for Canadian Application No. 3084312 mailed on Aug. 11, 2021, 5 pages. |
| Office Action for Canadian Application No. 3085998, mailed on Aug. 12, 2021, 4 pages. |
| Office Action for Canadian Application No. 3085998, mailed on Sep. 7, 2022, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,713, mailed Oct. 19, 2021, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,729, mailed Oct. 4, 2021, 13 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,729, mailed Oct. 25, 2021, 12 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,732, mailed Jan. 31, 2022, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,732, mailed Mar. 17, 2022, 6 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,766, mailed Apr. 7, 2020, 19 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,766, mailed Mar. 10, 2020, 20 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,772, mailed Sep. 15, 2021, 12 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,772, mailed Sep. 27, 2021, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/857,784, mailed Dec. 30, 2020, 15 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,110, mailed Dec. 11, 2020, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,110, mailed Jan. 6, 2021, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,110, mailed Sep. 3, 2020, 11 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,125, mailed Nov. 3, 2020, 17 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,125, mailed Sep. 9, 2020, 17 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,146, mailed Nov. 17, 2020, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,146, mailed Sep. 10, 2020, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,192, mailed Apr. 8, 2021, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,192, mailed Jan. 27, 2021, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,207, mailed Mar. 24, 2021, 17 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,207, mailed May 25, 2021, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,357, mailed Aug. 18, 2020, 12 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,357, mailed May 26, 2020, 22 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,410, mailed Jul. 14, 2020, 12 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,410, mailed May 22, 2020, 18 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,430, mailed Jun. 10, 2022, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/858,430, mailed May 12, 2022, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,748, mailed Aug. 11, 2021, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,748, mailed Jun. 15, 2021, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,751, mailed Apr. 15, 2021, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,751, mailed Mar. 24, 2021, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,815, mailed Jan. 21, 2021, 12 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,815, mailed Sep. 30, 2020, 13 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,819, mailed Apr. 7, 2020, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 15/863,819, mailed Mar. 6, 2020, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,496, mailed May 28, 2020, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,505, mailed Apr. 28, 2021, 14 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,505, mailed Jun. 28, 2021, 5 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,505, mailed May 5, 2021, 10 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,571, mailed Dec. 10, 2020, 16 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,571, mailed Jan. 19, 2021, 1 pages. |
| Notice of Allowance from U.S. Appl. No. 15/867,612, mailed Mar. 11, 2021, 5 pages. |
| Notice of Allowance from U.S. Appl. No. 15/868,489, mailed Dec. 27, 2019, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/868,489, mailed Feb. 20, 2020, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/868,489, mailed Jan. 24, 2020, 2 pages. |
| Notice of Allowance from U.S. Appl. No. 15/868,505, mailed Jul. 15, 2020, 8 pages. |
| Notice of Allowance from U.S. Appl. No. 15/868,511, mailed Jan. 25, 2021, 7 pages. |
| Notice of Allowance from U.S. Appl. No. 15/868,511, mailed Sep. 16, 2020, 9 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,179, mailed Aug. 12, 2020, 7 pages. |
| Notice of Allowance from U.S. Appl. No. 15/870,179, mailed Jun. 11, 2020, 7 pages. |
| Office Action for Canadian Application No. 3086004 mailed on Jul. 9, 2021, 4 pages. |
| Office Action for Canadian Application No. 3087087 mailed on Jul. 14, 2021, 4 pages. |
| Office Action For Japanese Application No. 2020-526431, mailed on Sep. 10, 2021, 9 pages. |
| Office Action For Japanese Application No. 2020-529314, mailed on Aug. 20, 2021, 11 pages. |
| Office Action for Japanese Application No. 2020-529761 mailed on Aug. 20, 2021, 20 pages. |
| Office Action For Japanese Application No. 2020-531088, mailed on Aug. 6, 2021, 7 pages. |
| Office Action For Japanese Application No. 2020-531974, mailed on Sep. 3, 2021, 9 pages. |
| Office Action For Japanese Application No. 2020-535976, mailed on Sep. 10, 2021, 11 pages. |
| Office Action For Japanese Application No. 2020-536083, mailed on Sep. 24, 2021, 13 pages. |
| Office Action for Korean Application No. 10-2020-7013685, mailed on Nov. 12, 2021, 11 pages. |
| Office Action for Korean Application No. 10-2020-7014986, mailed on Nov. 24, 2021, 11 pages. |
| Office Action for Korean Application No. 10-2020-7015491, mailed on Nov. 24, 2021, 13 pages. |
| Office Action for Korean Application No. 10-2020-7016617, mailed on Dec. 17, 2021, 10 pages. |
| Office Action for Korean Application No. 10-2020-7018242 mailed on Jan. 3, 2022, 13 pages. |
| Phan R.C.W., et al., “Security Considerations for Incremental Hash Functions Based on Pair Block Chaining,” Computers & Security, vol. 25 (2), Jan. 30, 2006, pp. 131-136. |
| Pollack K.T., et al., “Efficient Access Control for Distributed Hierarchical File Systems”, Jan. 2005, Proceedings of the 22nd IEEE / 13th NASA Goddard Conference on Mass Storage Systems and Technologies (MSST'05), pp. 1-8. |
| Prusty N., et al., “UNIX File System Permissions Tutorial,” retrieved from URL: http://qnimate.com/understanding-unix-filesystem-permissions/, 2014-2015, 8 pages. |
| Requirement for Restriction/Election from U.S. Appl. No. 15/857,588, mailed Jan. 29, 2020, 6 pages. |
| Requirement for Restriction/Election from U.S. Appl. No. 15/858,207, mailed Sep. 26, 2019, 6 pages. |
| Requirement for Restriction/Election from U.S. Appl. No. 15/858,410, mailed Sep. 19, 2019, 7 pages. |
| Rubyrailesguide, “Active Record Callbacks,” Nov. 18, 2016, retrieved from https://web.archive.org/web/20161118225731/http://guides.rubyonrails.org/active_record_callbacks.html, on Dec. 13, 2019, 11 Pages. |
| Search Query Report from IP.com (performed Jan. 7, 2022), 5 pages. |
| Search Query Report from IP.com (performed Feb. 25, 2020). |
| Search Query Report from Ip.com (performed Mar. 27, 2020). |
| Shields I., et al., “Learn Linux, 101: Manage File Permissions and Ownership,” https://developer.ibm.com/technologies/linux/tutorials/l-lpic1-104-5/, Jan. 27, 2016, 21 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 18830580.9, mailed on Mar. 24, 2022, 10 pages. |
| Summons to attend oral proceedings pursuant to Rule 115(1) EPC for European Application No. 18836317.0 mailed on Jun. 21, 2022, 15 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 18836962.3 dated Jul. 6, 2022, 8 pages. |
| Summons to Attend Oral Proceedings Pursuant to Rule 115(1) EPC for European Application No. 18839962.0 mailed on Feb. 22, 2022, 9 pages. |
| Swathy V., et al., “Providing Advanced Security Mechanism for Scalable Data Sharing in Cloud Storage,” 2016 International Conference on Inventive Computation Technologies (ICICT), 2016, vol. 3, pp. 1-6. |
| Tran T.T.G., et al., “Virtualization at File System Level: A New Approach to Secure Data in Shared Environment”, International Journal of Computer Theory and Engineering, vol. 8, No. 3, Jun. 2016, pp. 223-228. |
| Tridgell A,., et al., “Rsync,” edited on Nov. 24, 2017, retrieved from https://en.wikipedia.org/wikipedia.org/w/ Index.php?title=Rsync&oldid=811846440#cite_note-pool-25, on 2021-04-20, 7 pages. |
| Tridgell A., “Rsync(1),” XP055032454, Retrieved from http://sunsite.ualberta.ca/Documentation/Misc/rsync-2.6.6/rsync.1.html, Jul. 28, 2005, 33 pages. |
| JCAR, “Setting File and Directory Permissions,” Sep. 2017, retrieved from https://web.archive.org/web/20170920093821/https://www2.cisl.ucar.edu/user-support/setting-file-and-directory-permissions, on Dec. 8, 2019, 5 pages. |
| UNIX & Linux Stack Exchange, “Execute vs Read Bit. How do Directory Permissions in Linux Work?”, Dec. 15, 2016, retrieved from https://unix.stackexchange.com/questions/21251/execute-vs-read-bit-how-do-directory-permissions-in-linux-work, on Mar. 20, 2020, 3 pages. |
| Uploaded by Neeraj Singh, “Distributed System Answer Key,” retrieved from https://www.scribd.com/doc/80052663/Distributed-System-Answer-Key, 129 pages. |
| Uppoor S., et al., “Cloud-Based Synchronization of Distributed File System Hierarchies,” Oct. 2010, IEEE International Conference on Cluster Computing Workshops and Posters (Cluster Workshops), 5 pages. |
| Wang H., et al., “On the Impact of Virtualization on Dropbox-like Cloud File Storage/Synchronization Services,” IEEE, Jun. 4-5, 2012, pp. 1-9. |
| Wang Y., et al., “X-Diff: An Effective Change Detection Algorithm for XML Documents,” 2003 IEEE, Proceedings of the 19th International Conference on Data Engineering (ICDE'03), Mar. 5-8, 2003, pp. 519-530. |
| “What the Difference Between Remount to Umount/Mount?”, https://unix.stackexchange.com/questions/404006/what-the-difference-between-remount-to-umount-mount, Nov. 2017, pp. 1-3. |
| WINDOWS 7, “DOS/V Power Report,” 2010, vol. 20, No. 1, The plaintiff's knowledge of ** , Windows 7, which was examined thoroughly! Windows 7, which was found to be used by Windows, Inc, 7 pages. |
| Wolff D, “A Web-Based Tool for Managing the Submission of Student Work,” Journal of Computing Sciences in Colleges, Dec. 2004, vol. 20 (2), pp. 144-153. |
| Notice of Allowance from U.S. Appl. No. 15/857,779, mailed May 27, 2022, 10 pages. |
| “Active Directory Architecture”, retrieved from https:/technet.microsoft.com/en-us/library/bb727030.aspx, 2017, pp. 1-39. |
| Advisory Action from U.S. Appl. No. 15/857,725, mailed Aug. 20, 2021, 2 pages. |
| Advisory Action from U.S. Appl. No. 15/857,772, mailed Feb. 9, 2021, 4 pages. |
| Advisory Action from U.S. Appl. No. 15/867,486, mailed Dec. 7, 2021, 3 pages. |
| Advisory Action from U.S. Appl. No. 15/867,505, mailed Apr. 2, 2021, 4 pages. |
| Advisory Action from U.S. Appl. No. 15/857,772, mailed Jun. 12, 2020, 3 pages. |
| Advisory Action from U.S. Appl. No. 15/863,748, mailed Apr. 15, 2020, 3 pages. |
| Article Entitled “Cgconfig Doesn't Start at Boot Time”, by Redhat, dated Sep. 9, 2015, 2 pages. |
| Biztalkserver, “Optimizing Business Rule Engine (BRE) Performance,” Jun. 7, 2017, retrieved from https://docs.microsoft.com/en-us/biztalk/technical-guides/optimizing-business-rule-engine-bre-performance, on Oct. 22, 2019, 5 Pages. |
| Capra R., et al., “File Synchronization and Sharing: User Practices and Challenges”, 77th ASIS&T Annual Meeting, Seattle, WA, Oct. 31-Nov. 5, 2014, 10 pages. |
| Chiang J.K., et al., “Authentication, Authorization And File Synchronization On Hybrid Cloud—On Case of Google Docs, Hadoop, and Linux Local Hosts”, IEEE, Jul. 2-5, 2013, pp. 116-123. |
| Chris G., “Dropbox for Business 3.0”, retrieved from www.chrismgrant.com/product-design/dropbox-for-business, 2018, pp. 1-98. |
| Clercq J D., “How to Use the Bypass Traverse Checking User Right,” Aug. 27, 2008, ITProToday, https://www.itprotoday.com/print/20355, 2 pages. |
| Cobena G., et al., “Detecting Changes in XML Documents,” Proceedings of the 18th International Conference on Data Engineering, Jan. 1, 2002, pp. 41-52. |
| Communication under Rule 94(3) EPC for European Application No. 18839962.0 mailed on Oct. 26, 2020, 9 pages. |
| Communication Pursuant to Article 71(3) EPC for European Application No. 18829647.9 mailed on Aug. 25, 2022, 133 pages. |
| Communication Pursuant to Article 71(3) EPC for European Application No. 18830580.9 mailed on Oct. 31, 2022, 33 pages. |
| Communication pursuant to Article 94(3) EPC for EP Application No. 18833555.8, mailed on Jun. 8, 2021, 6 pages. |
| Communication pursuant to Article 94(3) EPC for European Application No. 18829647.9 mailed on Dec. 9, 2021, 7 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18830580.9 mailed on Jan. 14, 2021, 9 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18834121.8 mailed on Apr. 28, 2021, 10 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18834121.8 mailed on Feb. 9, 2022, pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18836317.0 mailed on Feb. 23, 2021, 9 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18836962.3 mailed on Jan. 14, 2020, 5 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18837007.6 mailed on Nov. 25, 2021, 9 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18839958.8 mailed on Feb. 22, 2022, 10 pages. |
| Communication Pursuant to Article 94(3) EPC for European Application No. 18840109.5 mailed on Feb. 23, 2022, 9 pages. |
| Daudjee K., et al., Article Entitled “Inferring a Serialization Order for Distributed Transactions”, 2006, 3 pages. |
| Decision of Refusal for Japanese Application No. 2020-521435 mailed on Feb. 25, 2022, 6 pages. |
| Decision of Refusal for Japanese Application No. 2020-531974 mailed on Apr. 8, 2022, 7 pages. |
| Decision of Refusal for Japanese Application No. 2020-536083 mailed on Aug. 12, 2022, 14 pages. |
| D'Silva A., “Undo Delete vs Confirm Delete,” Oct. 2, 2017, https://medium.com/@randomlies/undo-delete-vs-confirm-delete-31b04104c4a6, pp. 1-3. |
| Examination Report for Australian Application No. 2018395933 mailed on Sep. 30, 2020, 4 pages. |
| Examination Report No. 1, for Australian Application No. 2018393933, mailed on Mar. 9, 2021, 4 pages. |
| Examination Report No. 1, for Australian Application No. 2018395856, mailed on Dec. 14, 2020, 4 pages. |
| Examination Report No. 1, for Australian Application No. 2018395857, mailed on Mar. 9, 2021, 5 pages. |
| Examination Report No. 1, for Australian Application No. 2018395858, mailed on Feb. 5, 2021, 4 pages. |
| Examination Report No. 1, for Australian Application No. 2018397571, mailed on Mar. 4, 2021, 4 pages. |
| Examination Report No. 1 for Australian Application No. 2018397572 mailed on Feb. 8, 2021, 5 pages. |
| Examination Report No. 1 for Australian Application No. 2021203706 mailed on Mar. 31, 2022, 2 pages. |
| Examination Report No. 2, for Australian Application No. 2018393933, mailed on Jul. 23, 2021, 3 pages. |
| Examination Report No. 2, for Australian Application No. 2018395856, mailed on Mar. 18, 2021, 4 pages. |
| Examination Report No. 2, for Australian Application No. 2018397571, mailed on Mar. 30, 2021, 4 pages. |
| Examination Report No. 3, for Australian Application No. 2018395856, mailed on Jul. 2, 2021, 3 pages. |
| Examination Report No. 1, for Australian Application No. 2018395919, mailed on Dec. 22, 2020, 5 pages. |
| Examination Report No. 1 for Australian Application No. 2018395920 mailed on Oct. 16, 2020, 4 pages. |
| Examination Report No. 1, for Australian Application No. 2018397604, mailed on Dec. 22, 2020, 3 pages. |
| Examination Report No. 1 for Australian Application No. 2021261855 mailed on Nov. 15, 2022, 2 pages. |
| Examination Report No. 2, for Australian Application No. 2018395919, mailed on May 3, 2021, 3 pages. |
| Final Office Action from U.S. Appl. No. 15/858,430, mailed Dec. 29, 2021, 12 pages. |
| Notification of the First Office Action and for Chinese Application No. 201880083720.5 mailed on Sep. 28, 2023, 8 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/064670 dated Mar. 14, 2019, 13 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/064675 dated Mar. 13, 2019, 12 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/065091 dated Mar. 21, 2019, 16 bages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/065100 dated Mar. 19, 2019, 11 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/065352 dated Mar. 19, 2019, 13 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/065940 dated Mar. 14, 2019, 14 pages. |
| International Search Report and Written Opinion for PCT Application PCT/US2018/066193 dated Mar. 14, 2019, 12 pages. |
| Kappes G., et al., “Virtualization-Aware Access Control for Multitenant Filesystems,” MSST, Jun. 2-6, 2014, pp. 1-6. |
| Karjoth G., et al., “Implementing ACL-Based Policies in XACML,” 2008, Annual Computer Security Applications Conference, 10 pages. |
| Kher V., et al., “Securing Distributed Storage: Challenges, Techniques, and Systems,” ACM, Nov. 2005, pp. 9-25. |
| King E., “Linux Namespaces,” https://medium.com/@teddyking/linux-namespaces-850489d3ccf, Dec. 10, 2016, 3 pages. |
| Klein H., “Puzzle: Delete Directory Content Without Deleting the Directory Itself (on the Command Line)”, retrieved from https://helgeklein.com/blog/author/helge/, on Aug. 5, 2009, pp. 1-11. |
| Kotha R., “Fusion Middleware Language Reference for Oracle Business Process Management,” Oracle Fusion Middleware , Jan. 2011, 28 pages. |
| Kuo Y H., et al., “A Hybrid Cloud Storage Architecture for Service Operational High Availability”, COMPSACW, Jul. 2013, pp. 487-492. |
| Lindholm T., et al., “A Hybrid Approach To Optimistic File System Directory Tree Synchronization,” MobiDE 2005, Proceedings of 4th ACM International Workshop on Data Engineering for Wireless and Mobile Access, Jun. 12, 2005, pp. 49-56. |
| Lindholm T., “XML Three-way Merge as a Reconciliation Engine for Mobile Data,” Proceedings of the 3rd ACM International Workshop on Data Engineering for Wireless and Mobile Access, MobiDE'03, Sep. 19, 2003, pp. 93-97. |
| linux.org, “Mount a File System,” retrieved from https://www.linux.org/docs/man8/mount.html, Jan. 2012, pp. 1-17. |
| Liu G., et al., “Source Code Revision History Visualization Tools: Do They Work and What Would It Take to Put Them to Work?,” 2014 IEEE Access, Practical Innovations 1 Open Solutions, May 6, 2014, vol. 2, pp. 404-426. |
| Marshall C.C., et al., “Supporting Research Collaboration through Bi-Level File Synchronization,” ACM, Oct. 2012, pp. 165-174. |
| Mell P M., et al., “Linear Time Algorithms to Restrict Insider Access using Multi-Policy Access Control Systems,” Apr. 2013, retrieved from https://www.nist.gov/publications/linear-time-algorithms-restrict-insider-access-using-multi-policy-access-control, on Dec. 31, 2019, 2 Pages. |
| Microsoft Outlook, “Cannot Copy this Folder Because it May Contain Private Items,” Feb. 23, 2015, retrieved from http://techy-wire.blogspot.com/2015/02/cannot-copy-this-folder-because-it-may.html, 3 pages. |
| Niazi S., et al., “HopsFS: Scaling Hierarchical File System Metadata Using NewSQL Databases,” The 15th USENIX Conference on File and Storage Technologies (FAST 17), Feb. 22, 2017, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 16/991,798, mailed Jan. 6, 2022, 20 pages. |
| Non-Final Office Action from U.S. Appl. No. 17/076,538, mailed Jun. 29, 2022, 19 pages. |
| Non-Final Office Action for U.S. Appl. No. 15/868,511 mailed on Feb. 5, 2020, 11 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,588, mailed Apr. 2, 2020, 14 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,713, mailed Jan. 7, 2020, 16 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,713, mailed Nov. 25, 2020, 28 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,715, mailed Feb. 20, 2020, 8 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,725, mailed Feb. 25, 2021, 14 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,725, mailed Jan. 2, 2020, 10 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,725, mailed Jun. 18, 2020, 13 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,725, mailed Nov. 15, 2021, 13 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,729, mailed Jul. 21, 2020, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,729, mailed May 7, 2021, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,729, mailed Nov. 20, 2019, 12 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,732, mailed Aug. 6, 2021, 32 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,732, mailed Dec. 27, 2019, 29 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,732, mailed Sep. 17, 2020, 29 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,766, mailed Oct. 31, 2019, 27 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,772, mailed Apr. 20, 2021, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,772, mailed Jul. 23, 2020, 16 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,772, mailed Nov. 25, 2019, 11 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,779, mailed Jan. 17, 2020, 17 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,779, mailed Jul. 21, 2021, 24 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,779, mailed Oct. 15, 2020, 23 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,784, mailed Dec. 19, 2019, 18 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,784, mailed Jul. 24, 2020, 19 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,789, mailed Jan. 22, 2020, 15 pages. |
| Non-Final Office Action from U.S. Appl. No. 15/857,789, mailed Jun. 15, 2021, 18 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230101958 A1 | Mar 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62611473 | Dec 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16991798 | Aug 2020 | US |
| Child | 17993500 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15858410 | Dec 2017 | US |
| Child | 16991798 | US |
