Migrating data and software from one system to another system can often be complicated. The volume of data, complexity of the file structure, and/or the complexity of the software configuration on the first system can make moving data and software to the second system very risky. Moreover, merging the two systems into a single system can be complicated and prone to problems as the two systems may not work well together once merged.
Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be obvious from the description, or can be learned by practice of the herein disclosed principles. The features and advantages of the disclosure can be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and appended claims, or can be learned by the practice of the principles set forth herein.
Disclosed are systems, methods, and non-transitory computer-readable storage media for managing content across discrete systems. A content management system can be implemented to manage content items and synchronize content items across devices. A content collaboration system can be implemented to generate documents and facilitate collaboration on documents. To take advantage of the content management system's functionality to manage and synchronize content items while also providing the collaboration functionality of the content collaboration system, the content management system can store and manage references to documents created in the content collaboration system. A reference can be a content item managed by the content management system that includes an identifier for the referenced document, but does not include the content of the referenced document.
When metadata for a document in the content collaboration system changes, the content management system can synchronize the updated metadata with client devices so that the metadata for the corresponding references matches the metadata for the document in the content collaboration system. Similarly, when a document is deleted from the content collaboration system, the content management system can delete references to the deleted document from client devices. Users can interact with references in the content management system just like other content items. For example, a user can select a reference to cause the user's device to present the corresponding document in the content management system. Thus, to users of the content management system, the reference appears to be the referenced document.
The above-recited and other advantages and features of the disclosure will become apparent by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only example embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Various embodiments of the disclosure 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 disclosure.
The disclosed technology addresses the need in the art for a safe and convenient way to migrate and/or merge data and/or software configured on one system to another system.
With respect to implementing various embodiments of the disclosed technology, an example system configuration 100 is shown in
In system 100, a user can interact with content management system 106 (e.g., an online synchronized content management system) through client devices 1021, 1022, . . . , 102n (collectively “102”) connected to network 104 by direct and/or indirect communication. Content management system 106 can support connections from a variety of different client devices, such as: desktop computers; mobile computers; mobile communications devices, e.g. mobile phones, smart phones, tablets; smart televisions; set-top boxes; and/or any other network enabled computing devices. Client devices 102 can be of varying type, capabilities, operating systems, etc. Furthermore, content management system 106 can concurrently accept connections from and interact with multiple client devices 102.
A user can interact with content management system 106 via a client-side application installed on client device 102i. In some embodiments, the client-side application can include a content management system specific component. For example, the component can be a stand-alone application, one or more application plug-ins, and/or a browser extension. However, the user can also interact with content management system 106 via a third-party application, such as a web browser, that resides on client device 102i and is configured to communicate with content management system 106. In either case, the client-side application can present a user interface (UI) for the user to interact with content management system 106. For example, the user can interact with the content management system 106 via a client-side application integrated with the file system or via a webpage displayed using a web browser application.
Content management system 106 can enable a user to store content, as well as perform a variety of content management tasks, such as retrieve, modify, browse, and/or share the content. Furthermore, content management system 106 can enable a user to access the content from multiple client devices 102. For example, client device 102i can upload content to content management system 106 via network 104. Later, the same client device 102i or some other client device 102j can retrieve the content from content management system 106.
To facilitate the various content management services, a user can create an account with content management system 106. User account database 150 can maintain the account information. User account database 150 can store profile information for registered users. In some cases, the only personal information in the user profile can be a username and/or email address. However, content management system 106 can also be configured to accept additional user information such as birthday, address, billing information, etc.
User account database 150 can include account management information, such as account type (e.g. free or paid), usage information, (e.g. file edit history), maximum storage space authorized, storage space used, content storage locations, security settings, personal configuration settings, content sharing data, etc. Account management module 124 can be configured to update and/or obtain user account details in user account database 150. The account management module 124 can be configured to interact with any number of other modules in content management system 106.
An account can be used to store content, such as digital data, documents, text files, audio files, video files, etc., from one or more client devices 102 authorized on the account. The content can also include collections for grouping content items together with different behaviors, such as folders, playlists, albums, etc. For example, an account can include a public folder that is accessible to any user. The public folder can be assigned a web-accessible address. A link to the web-accessible address can be used to access the contents of the public folder. In another example, an account can include: a photos collection that is intended for photos and that provides specific attributes and actions tailored for photos; an audio collection that provides the ability to play back audio files and perform other audio related actions; or other special purpose collection. An account can also include shared collections or group collections that are linked with and available to multiple user accounts. The permissions for multiple users may be different for a shared collection.
The content can be stored in content storage 160. Content storage 160 can be a storage device, multiple storage devices, or a server. Alternatively, content storage 160 can be a cloud storage provider or network storage accessible via one or more communications networks. Content management system 106 can hide the complexity and details from client devices 102 so that client devices 102 do not need to know exactly where or how the content items are being stored by content management system 106. In some embodiments, content management system 106 can store the content items in the same collection hierarchy as they appear on client device 102i. However, content management system 106 can store the content items in its own order, arrangement, or hierarchy. Content management system 106 can store the content items in a network accessible storage (NAS) device, in a redundant array of independent disks (RAID), etc. Content storage 160 can store content items using one or more partition types, such as FAT, FAT32, NTFS, EXT2, EXT3, EXT4, HFS/HFS+, BTRFS, and so forth.
Content storage 160 can also store metadata describing content items, content item types, and the relationship of content items to various accounts, collections, or groups. The metadata for a content item can be stored as part of the content item or can be stored separately. In one variation, each content item stored in content storage 160 can be assigned a system-wide unique identifier.
Content storage 160 can decrease the amount of storage space required by identifying duplicate content items or duplicate segments of content items. Instead of storing multiple copies, content storage 160 can store a single copy and then use a pointer or other mechanism to link the duplicates to the single copy. Similarly, content storage 160 can store content items more efficiently, as well as 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. The change history can include a set of changes that, when applied to the original content item version, produce the changed content item version.
Content management system 106 can be configured to support automatic synchronization of content from one or more client devices 102. The synchronization can be platform agnostic. That is, the content can be synchronized across multiple client devices 102 of varying type, capabilities, operating systems, etc. For example, client device 102i can include client software, which synchronizes, via a synchronization module 132 at content management system 106, content in client device 102i's file system with the content in an associated user account. In some cases, the client software can synchronize any changes to content in a designated collection and its sub-collections, such as new, deleted, modified, copied, or moved content items or collections. The client software can be a separate software application, can integrate with an existing content management application in the operating system, or some combination thereof. In one example of client software that integrates with an existing content management application, a user can manipulate content items directly in a local collection, while a background process monitors the local collection for changes and synchronizes those changes to content management system 106. Conversely, the background process can identify content that has been updated at content management system 106 and synchronize those changes to the local collection. The client software can provide notifications of synchronization operations, and can provide indications of content statuses directly within the content management application. Sometimes client device 102i may not have a network connection available. In this scenario, the client software can monitor the linked collection for content item changes and queue those changes for later synchronization to content management system 106 when a network connection is available. Similarly, a user can manually start, stop, pause, or resume synchronization with content management system 106.
A user can view or manipulate content via a web interface generated and served by user interface module 122. For example, the user can navigate in a web browser to a web address provided by content management system 106. Changes or updates to content in the content storage 160 made through the web interface, such as uploading a new version of a content item, can be propagated back to other client devices 102 associated with the user's account. For example, multiple client devices 102, 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 102.
Content management system 106 can include a communications interface 120 for interfacing with various client devices 102, and can interact with other content and/or service providers 1091, 1092, . . . , 109n (collectively “109”) via an Application Program Interface (API). Certain software applications can access content storage 160 via an API on behalf of a user. For example, a software package, such as an app running on a smartphone or tablet computing device, can programmatically make calls directly to content management system 106, when a user provides credentials, to read, write, create, delete, share, or otherwise manipulate content. Similarly, the API can allow users to access all or part of content storage 160 through a web site.
Content management system 106 can also include authenticator module 126, which can verify user credentials, security tokens, API calls, specific client devices, and so forth, to ensure only authorized clients and users can access content items. Further, content management system 106 can include analytics module 134 module that can track and report on aggregate file operations, user actions, network usage, total storage space used, as well as other technology, usage, or business metrics. A privacy and/or security policy can prevent unauthorized access to user data stored with content management system 106.
Content management system 106 can include sharing module 130 for managing sharing content publicly or privately. Sharing content publicly can include making the content item accessible from any computing device in network communication with content management system 106. Sharing content privately can include linking a content item in content storage 160 with two or more user accounts so that each user account has access to the content item. The sharing can be performed in a platform agnostic manner. That is, the content can be shared across multiple client devices 102 of varying type, capabilities, operating systems, etc. The content can also be shared across varying types of user accounts.
In some embodiments, content management system 106 can be configured to maintain a content directory identifying the location of each content item in content storage 160. The content directory can include a unique content entry for each content item stored in the content storage.
A content entry can include a content path that can be used to identify the location of the content item in a content management system. For example, the content path can include the name of the content item and a 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 placed as well as the name of the content item. Content management system 106 can use the content path to present the content items in the appropriate folder hierarchy.
A content entry can also include a content pointer that identifies the location of the content item in content storage 160. For example, the content pointer can include the exact storage address of the content item in memory. In some embodiments, the content pointer can point to multiple locations, each of which contains a portion of the content item.
In addition to a content path and content pointer, a content entry can also include a user account identifier that identifies the user account that has access to the content item. In some embodiments, multiple user account identifiers can be associated with a single content entry indicating that the content item has shared access by the multiple user accounts.
To share a content item privately, sharing module 130 can be configured to add a user account identifier to the content entry associated with the content item, thus granting the added user account access to the content item. Sharing module 130 can also be configured to remove user account identifiers from a content entry to restrict a user account's access to the content item.
To share content publicly, sharing module 130 can be configured to generate a custom network address, such as a uniform resource locator (URL), which allows any web browser to access the content in content management system 106 without any authentication. To accomplish this, sharing module 130 can be configured to 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 module 130 can be configured to include the user account identifier and the content path in the generated URL. Upon selection of the URL, the content identification data included in the URL can be transmitted to content management system 106 which can use the received content identification data to identify the appropriate content entry and return the content item associated with the content entry.
In addition to generating the URL, sharing module 130 can also be configured to record 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 module 130 can be configured to change the value of the flag to 1 or true after generating a URL to the content item.
In some embodiments, sharing module 130 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 module 130 can be configured to 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 module 130 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.
While content management system 106 is presented with specific components, it should be understood by one skilled in the art, that the architectural configuration of system 106 is simply one possible configuration and that other configurations with more or fewer components are possible.
The term “document” is used herein as a convenient way to distinguish a content item created, managed, and/or stored by collaboration system 222 from content items managed by content management system 106, as described above. A “document” can be any type of content item (e.g., file, image, word processing file, a presentation, a spreadsheet, a bundle of files, etc.). The term “reference” is used herein to refer to a content item managed by content management system 106 that includes a reference to a document of collaboration system 222. For example, the reference can be a file that includes a unique identifier (e.g., a number, sequence of characters and numbers, etc.) for the corresponding document in collaboration system 222. The file can have a unique file extension (e.g., file.ref, file.paper. file.note, etc.) that identifies the file as a reference to a document in collaboration system 222. Unless otherwise stated, the description below assumes that all users described herein have accounts with both content management system 106 and collaboration system 222 and are logged into the respective accounts.
In some embodiments, system 200 can include collaboration server 220. For example, collaboration server 220 can be a computing device or computing devices configured to run software of collaboration system 222. Collaboration system 222 can be software (e.g., a web server, collaboration server, document editor, etc.) configured on collaboration server 220 that allows users of collaboration system 222 to collaborate on creating, editing, and/or otherwise manipulating documents. For example, a user of user device 230 can invoke web browser 232 and navigate to collaboration server 220 using well-known mechanisms. For example, user device 230 can correspond to client device 102i of
In some embodiments, web browser 232 can receive web page 233 from collaboration system 222 that allows the user to create, modify, delete, rename, etc., documents (e.g., document 224) managed by collaboration system 222. For example, the user can provide input to web page 233 through web browser 232 to create a new document in collaboration system 222. In response to receiving the user input, web browser 232 can send a request to collaboration system 222 to create document 224. When the request is received, collaboration system 222 can create document 224 and/or document metadata 226 corresponding to document 224. For example, document metadata 226 can be stored in document 224. Document metadata 226 can be stored separately from document 224 (e.g., as a distinct file or object).
In some embodiments, web browser 232 can receive user input to save document 224. For example, web page 233 received from collaboration system 222 and presented by web browser 232 on user device 230 can present an option to save document 224 in content management system 106. Upon receiving user input selecting the save option, web browser 232 can present a graphical user interface (e.g., file system browser) that allows the user to specify a location (e.g., file system location, specific folder, etc.) in the user's account on content management system 106 where the document should be stored. After the user has provided input specifying the location where the document should be stored, web browser 232 can send the location to collaboration system 222.
In some embodiments, upon receiving the save location, collaboration system 222 can save the current state of document 224. For example, collaboration system 222 can save the contents of document 224 and/or document metadata 226. If document 224 has been modified, collaboration system 222 can, for example, save a timestamp indicating the time when document 224 was last modified in document metadata 226. If the user provided a new name for document 224 when specifying the save location, collaboration system 222 can rename document 224 according to the new name.
In some embodiments, upon receiving the save location, collaboration system 222 can send a request to content management system 106 to generate a reference for document 224. For example, if document 224 is a new document, then a new reference 212 can be created on content management system 106 for the new document. The new reference request can include the new name for document 224, the user-specified location (e.g., document save location) where the reference should be stored, a unique identifier for document 224, and/or metadata 226 for document 224, for example.
In some embodiments, upon receiving the new reference request, content management system 106 can generate a new reference to document 224. For example, content management system 106 can create document reference 212 having the same name as document 224. Content management system 106 can store or save reference 212 in the requesting user's account of content management system 106 at the user-specified location in the request. Content management system 106 can store the received document metadata 226 as reference metadata 214. For example, reference metadata 214 can be stored in document reference 214. Reference metadata 214 can be stored separately (e.g., as a distinct file or object) from document reference 212.
In some embodiments, content management system 106 can generate reference map 228. For example, reference map 228 can include data that maps or associates the identifier for document 224 to user accounts and locations where references to document 224 exist within content management system 106. For example, once document 224 and corresponding document reference 212 are created, the user of user device 230 can share document reference 212 just like any other content item in content management system 106. Each time a new reference to document 224 is created (e.g., copied, shared, added, etc.) in content management system 106 (e.g., by the user of user device 230 or by another user), content management system 106 can add a new mapping identifying the document referenced, the user account associated with the new reference, and the location of the new reference in the user account (e.g., “docID:user1:/home/folder1/doc.paper”).
In some embodiments, reference map 228 can be a database that stores reference mappings for all documents in collaboration system 224. In some embodiments, reference map 228 can correspond to a single document (e.g., document 224). For example, content management system 106 can store a distinct reference map 228 for each document in collaboration system 222 that identifies user accounts and locations where references exist within content management system 106 that correspond to a specific document. For example, reference map 228 can identify user accounts and locations for references to document 224 only. For example, while reference 212 includes an identifier that allows content management system 106 to identify corresponding document 224 to collaboration system 222, reference map 228 includes information that allows content management system 106 to locate references to document 224 within content management system 106.
In some embodiments, content management system 106 can synchronize document reference 212 with user device 230. As described above with reference to
In some embodiments, content management system 106 can send reference 212 and metadata 214 to content management system (CMS) client 234 (e.g., client-side application of
In some embodiments, CMS client 234 can store a local copy of document 224 in local cache 250. For example, cache 250 can be a hidden cache of documents corresponding to document references stored in file system 240. Cache 250 can be stored within file system 240. Cached document 252 can correspond to document reference 242, for example. For example, when a user selects document reference 240 and opens document 224, as described below, CMS client 234 can store a local copy of document 224 and document metadata 226 in cache 250 as document 252 and document metadata 256, respectively. In some embodiments, CMS client 234 can automatically request the current version of document 224 from collaboration system 222 when a new document reference 242 or updated metadata 244 is received by CMS client 234 from content management system 106. Thus, the user of user device 230 can still view documents of collaboration system 222 even when user device 230 is offline (e.g., not connected to network 104).
In some embodiments, cache 250 can be a read-only cache. For example, when the user of user device 230 opens document 252, the user may view the document but may not be able to edit the document. In some embodiments, cache 250 can be a read-write cache that allows the user to both view and edit document 252. In some embodiments, cache 250 can include document metadata 256 corresponding to document 252. Thus, when a user opens document 252, the corresponding metadata 256 can be read and a graphical user interface can be presented that presents the metadata for document 256.
In some embodiments, a user can open document 224 managed by collaboration system 222 through CMS client 234 by selecting document reference 242 stored on user device 242. For example, CMS client 234 can be a native client specifically built for the operating environment (e.g., operating system, device specifications, etc.) of user device 230. For example, a user can browse the local file system 240 on user device 230 using a well-known file browser or other operating system file browser. The user can locate document reference 242 within file system 240 and provide user input to user device 230 selecting document reference 242. Upon receipt of the user input selecting document reference 242, user device 230 (e.g., the operating system of user device 230) can invoke CMS client 234. For example, document reference 242 can have a file extension (e.g., .ref, .paper, .notes, etc.) associated with CMS client 234. The operating system of user device 230 can be configured to invoke CMS client 234 when a file with the appropriate extension is selected by a user, for example.
In some embodiments, CMS client 234 can open document 224 on collaboration system 222. For example, when the operating system of user device 230 invokes CMS client 234, the operating system can provide document reference 242 to CMS client 234. The operating system can, for example, provide the file system path for document reference 242 to CMS client 234 as a parameter to the invocation of CMS client 234. Upon receiving document reference 242, CMS client 234 can determine that document reference 242 is a reference to document 224 on collaboration system 222 and present document 224 on a display of user device 230.
In some embodiments, CMS client 234 can open document 224 on collaboration server 220. For example, when CMS client 234 determines that user device 230 is connected to network 104 (e.g., the Internet, a LAN, a WAN, etc.), then CMS client 234 can invoke collaboration client 236 to present document 224 on a display of user device 230. In some embodiments, collaboration client 236 can be a web client viewed through an internal web browser of CMS client 234. For example, CMS client 234 can obtain a document identifier from document reference 242. In some embodiments, CMS client 234 can invoke a web browser and pass a URL (e.g., “http://www.collaborator.com/editor/12345”) that includes an address for collaboration system 222 (e.g., “http://www.collaborator.com”) and the identifier (e.g., “12345”) for document 224. The web browser can use the URL to obtain a web page for the web client (e.g., collaboration client 236) from collaboration system 222 that presents document 224. The user can then view or edit document 224 using various features of the web client.
In some embodiments, CMS client 234 can open document 252 on user device 230. For example, when CMS client 234 determines that user device 230 is not connected to network 104 (e.g., the Internet, a LAN, a WAN, etc.), then CMS client 234 can invoke collaboration client 236 to present document 252 on a display of user device 230. In some embodiments, collaboration client 236 can be an internal document viewer of CMS client 234. For example, collaboration client 236 can open document 252 and/or document metadata 256 locally and provide a read-only view of document 252 so that a user can view the contents of document 224 (e.g., represented by document 252) even when user device 230 is offline.
In some embodiments, a user can open document 224 managed by collaboration system 222 through a web client (e.g., web page) of content management system 106 presented by web browser 232. For example, the user can invoke web browser 232 and navigate through network 104 to content management system 106. Web browser 232 can receive a web page from content management system 106 that presents content items associated the user's account and managed by content management system 106. For example, the web page can include a representation of document reference 212 and reference metadata 214.
In some embodiments, upon receiving user input selecting document reference 212 on the web page, web browser 232 can send the selection to content management system 106. For example, upon receiving the selection of document reference 212, content management system 106 can determine that the selected content item is a collaboration document reference (e.g., based on the file extension, content item type, etc.) and redirect web browser 232 to collaboration system 222. For example, content management system 106 can send web browser 232 a URL that specifies an address for collaboration server 220 and identifies document 224, as described above. For example, the redirection can cause web browser 232 to receive collaboration system web page 233 for viewing and/or editing document 224. When web browser 232 receives web page 233, web browser 232 can present web page 233, including a representation of the contents of document 224 and/or metadata 226, on a display of computing device 230 for editing and/or viewing.
In some embodiments, the user can interact with collaboration system 222 through collaboration client 302 to change the name of document 224. For example, collaboration client 302 can present an option to rename document 224. The user can select the option to rename document 224 and provide a new name for document 224. Upon receiving the new name, collaboration client 302 can send the new name to collaboration system 222. When collaboration system 222 receives the new name, collaboration system 222 can rename document 224 according to the user-specified name. For example, collaboration system 222 can store the user-specified name in document metadata 226 corresponding to document 224 in collaboration system 222.
Similarly, the user can interact with collaboration system 222 through collaboration client 302 to change the location of document 224. For example, collaboration client 302 can present an option to move document 224. The user can select the option to move document 224 and provide a new location (e.g., folder, file system path, etc.) within the user's account on content management system 106 for document 224. Upon receiving the new location, collaboration client 302 can send the new location to collaboration system 222. When collaboration system 222 receives the new location, collaboration system 222 can store the new location for document 224 in document metadata 226 corresponding to document 224 in collaboration system 222.
In some embodiments, the user can cause document metadata 226 to change by editing document 224. For example, document metadata 226 can include a timestamp indicating when the most recent modification (e.g., edit) to document 224 occurred. When the user uses collaboration client 302 to edit document 224, collaboration system 222 will update this “last modified” timestamp in document metadata 226 to reflect the date and time of the latest modification to document 224.
In some embodiments, collaboration system 222 can send metadata updates to content management server 106. For example, collaboration system 222 can detect when a change to document metadata 226 occurs. When collaboration system 222 detects a change to document metadata 226, collaboration system 222 can send metadata update message 320 to content management server 106. For example, metadata update message 320 can include the unique collaboration system identifier for document 224 and any changes to document metadata 226. For example, if the name, location and/or last modified timestamp in document metadata 226 has changed, metadata update message 320 can include the new name, the new location and/or the new timestamp.
In some embodiments, content management system 106 can update document reference metadata to reflect document changes received in metadata update message 320. For example, content management system 106 can determine which document references need to be updated in response to receiving metadata update message 320 based on the document identifier in metadata update message 320. Content management system 106 can, for example, compare the document identifier in message 320 to reference map 228 to determine the user accounts and locations of references to document 224. For example, a copy of reference 212 may have been shared with multiple user accounts and the each user account may store a copy of reference 212 in a different location. Reference map 228 provides a mechanism by which content management server 106 can find the various copies of document reference 212 in content management system 106.
After content management system 106 determines the locations of references (e.g., reference 212) corresponding to document 224, content management system 106 can update the metadata (e.g., metadata 214) for each reference (e.g., reference 212) associated with document 224 to reflect the changes to document metadata 226. Reference metadata 214 can then be used to present a representation of document reference 212 having the new name, location, and/or last modified timestamp on a web client of content management system 106. Thus, the representation of document reference 212 on the graphical user interface of the web client will appear as if it is document 224 when viewed by a user.
In some embodiments, content management server 106 can synchronize reference metadata with client devices. For example, since reference metadata 214 is a content item managed by content management server 106, content management server 106 can synchronize reference metadata 214 managed by content management system 106 with reference metadata 244 on user device 230. For example, content management server 106 can send a reference update message 324 that identifies document reference 242 and contains information describing the changes to reference metadata 214.
If reference update 324 includes information indicating that the name of document 224 has changed, then CMS client 234 can change the name of document reference 242 on user device 230. If reference update 324 includes information indicating that the location of document 224 has changed, then CMS client 234 can move document reference 242 to a new location within file system 240 on user device 230. If reference update 324 includes information indicating that the last modified timestamp of document 224 has changed, then CMS client 234 can update the last modified timestamp of document reference 242 so that the correct timestamp is presented when document reference 242 is viewed in file system 240 on user device 230.
In some embodiments, system 300 can include user device 310. For example, user device 310 can be a device of another user (e.g., second user) with which document reference 212 has been shared. The user (e.g., first user) of user device 230 may have, for example, sent document reference 212 to the second user in an email message, instant message, or using some other electronic communication mechanism. The user of user device 310 can have a user account with content management system 106. The second user can save document reference 212 as document reference 314 on user device 310 in a file system of user device 310 managed by content management system 106.
Upon detecting the new content item in the managed file system, CMS client 312 can synchronize document reference 314 and/or reference metadata 316 with the user's account on content management system 106. When content management system 106 detects another copy of document reference 212 and/or reference metadata 214 in content management system 106, content management system 106 can update reference map 228 to map the user account and location of the new document reference to document 224, as described above. When changes to document reference 212 and/or reference metadata 214 received in metadata update message 320 from collaboration system 222, content management system 106 can synchronize the changes with user device 310 in the same way as changes are synchronized with user device 230, as described above. For example, content management system 106 can update the reference to document 224 in the second user's account on content management system 106 and send reference update message 322 to CMS client 312. For example, reference update message 322 can include an identifier (e.g., path and/or file name) for document reference 314 and describe the changes (e.g., new name, new location, new last modified timestamp, etc.) to the metadata for the reference to document 224 in the user's account.
Upon receiving reference update message 322, CMS client 312 on user device 310 can update document reference 314 and/or reference metadata 316 with the metadata changes described in reference update message 322. For example, CMS client 312 can rename document reference 314 to the new name specified by the user of user device 230 and described in reference update message 322. CMS client 312 can move document reference 314 to a new file system location (e.g., new folder, new director, etc.) specified by the user of user device 230 and described in reference update message 322. Thus, when the user (e.g., the second user) of user device 310 views or browses for document reference 314 in a file browser on user device 310, document reference 314 will be presented to the user with new name and/or at the new location specified by the user (e.g., the first user) of user device 230.
In some embodiments, the user may change reference metadata 244 through the file browser. For example, the user may provide input to cause the file browser on user device 230 to perform a rename operation on document reference 242 on user device 230 using the file browser. The user may provide input to cause the file browser on user device 230 to perform a move operation to move document reference 242 to another directory or folder in file system 240 on user device 230. After the move or rename operation is performed, the file browser can store the new name and/or new location in reference metadata 244.
In some embodiments, CMS client 234 on user device 230 can update reference metadata 214 on content management server 106 when reference metadata 244 has been modified on user device 230. For example, CMS client 234 can monitor file system 240 on user device 230 and detect changes to content items (e.g., including document reference 242 and/or reference metadata 244) in file system 240. When CMS client 234 detects changes to reference metadata 244, CMS client 234 can send synchronization message 402 to content management system 106. Synchronization message 402 can, for example, describe the changes the user made to reference metadata 244, such as changes to the name and/or location of document reference 242 within file system 240, as described above. Upon receiving synchronization message 402, content management system 106 can update reference metadata 214 with the metadata changes described in synchronization message 402.
Alternatively, the user of user device 230 can modify reference metadata 214 directly using web browser 232. For example, the user can used web browser 232 to navigate to a web page of content management system 106. The web page can present the content items in the user's account on content management system 106, such as document reference 212. The web page can present some or all of the data in reference metadata 214 when presenting document reference 212. For example, the metadata presented for document reference 212 can include a name for document reference 212 (e.g., document 224), a last modified timestamp for document 244, a location for document reference 212, and/or other metadata for document reference 212 and/or document 244.
In some embodiments, the user can provide input to web browser 232 to change metadata associated with document reference 212. For example, the user can provide input to the web page of content management system 106 to change the name and/or location of document reference 212. In response to receiving the user input, web browser 232 can send the new name and/or location for document reference 211 to content management system 106. Upon receipt of the new name and/or location, content management system can update reference metadata 214 with the new name and/or location for document reference 211.
In some embodiments, content management system 106 can send changed document metadata to collaboration system 222. For example, upon receiving changes or modifications to document reference 212 and/or reference metadata 214, content management system 106 can send document update message 404 describing changes made to document reference 212 and/or reference metadata 214 to collaboration system 222. Document update message 404 can include, for example, the identifier corresponding to document 244 and a description of the metadata changes to be applied to document metadata 226 (e.g., the new user-specified name and/or location for document 224). Upon receipt of document update 404, collaboration system 222 can identify and/or locate document 244 based on the document identifier and update the document metadata 226.
In some embodiments, collaboration system 222 can cause content management system 106 to update document references in response to receiving changes to document 224 and/or document metadata 226. As described above with reference to
In some embodiments, content management system 106 can update references to document 224 based on metadata update message 320. For example, content management system 106 can use the document identifier in metadata update message 320 to find the locations of all references to document 244 in reference map 228. The document identifier can be used as an index to find all of the user accounts and locations within user accounts where a copy of document reference 212 exists within content management system 106, for example.
After content management system 106 determines where each reference to document 224 is within content management system 106, content management system 106 can update the metadata for each reference with the metadata changes described in metadata update message 320. For example, content management system 106 can update each reference to document 224 (e.g., update the metadata for the reference) with the name and/or location changes specified by the user of user device 230.
After the metadata changes are applied to each reference to document 224 within content management system 106, content management system 322 can send the metadata changes for references to document 224 to other user devices, such as user device 310, in reference update message 322. For example, reference update message 322 can include an identifier for document reference 314 (e.g., current path and/or file name) and a description of the metadata changes to be applied to reference metadata 316. For example, reference update message 322 can include the new name and/or location for document 224 specified by the user of user device 230.
Upon receiving reference update message 322, CMS client 312 on user device 310 can update document reference 314 and/or reference metadata 316 with the metadata changes described in reference update message 322. For example, CMS client 312 can rename document reference 314 to the new name specified by the user of user device 230 and described in reference update message 322. CMS client 312 can move document reference 314 to a new file system location (e.g., new folder, new director, etc.) specified by the user of user device 230 and described in reference update message 322. Thus, when the user (e.g., the second user) of user device 310 views or browses for document reference 314 in a file browser on user device 310, document reference 314 will be presented to the user with new name and/or at the new location specified by the user (e.g., the first user) of user device 230.
In some embodiments, user device 230 can delete document reference 242 upon receiving user input indicating the user's intent to delete document reference 242. For example, rather than causing document 224 to be deleted from collaboration system 222, user device 230 can delete document reference 242 and/or reference metadata 244 from user device 230. Since document reference 242 and reference metadata 244 are content items managed by CMS client 234, CMS client 234 will send a synchronization update to content management system 106 which will cause these content items to be deleted from the user's account on content management system 106. For example, CMS client 234 can send delete document message 502 that identifies the corresponding document reference 212 on content management system 106. Upon receiving message 502, content management system 106 can delete the corresponding document reference 212, delete corresponding metadata 214, and update reference map 228 to remove the entry for document reference 212. Thus, in some embodiments, deleting a document reference only causes removal of that specific document reference (and corresponding metadata) from the user's device and removal of the corresponding document reference (and corresponding metadata) from the user's account on content management system 106.
In some embodiments, deletion of a document reference on a user device can cause the deletion of the corresponding referenced document from collaboration system 222. For example, a user of user device 230 can provide input to the file browser on user device 230 to delete document reference 242. In response to receiving the input, user device 230 can delete document reference 242 and/or reference metadata 244. Since document reference 242 and reference metadata 244 are content items managed by CMS client 234, CMS client 234 will send a synchronization update to content management system 106 which will cause these content items to be deleted from the user's account on content management system 106. For example, CMS client 234 can send delete document message 502 that identifies the corresponding document reference 212 on content management system 106. Upon receiving message 502, content management system 106 can delete the corresponding document reference 212, delete corresponding metadata 214, and update reference map 228 to remove the entry for document reference 212.
Upon deleting document reference 214 from content management system 106, content management system 106 can send delete document message 504 to collaboration system 222 to cause collaboration system 222 to delete document 224 and corresponding document metadata 226. Message 504 can, for example, include the unique identifier for document 224. Upon receiving message 504, collaboration system 222 can remove document 224 and/or document metadata 226 from collaboration system 222.
Alternatively, the user of user device 230 can delete document 224 through collaboration client 302. For example, the user can view document 224 through collaboration client 302, as described above, and provide input to collaboration client 302 to delete document 224 from collaboration system 222. Collaboration client 302 can invoke an programming interface of collaboration system 222 for deleting documents from collaboration system 222 and provide the unique identifier for document 224 as a parameter to the invocation. Upon receiving the unique identifier, collaboration system 222 can remove document 224 and/or document metadata 226 from collaboration system 222.
In some embodiments, deletion of a document from collaboration system 222 causes all reference to the document to be deleted. For example, when collaboration system 222 removes document 224 from collaboration system 222, collaboration system 222 can send delete references message 506 (e.g., a delete command, API invocation, etc.) to content management system 106. Message 506 can include for, for example, the unique identifier corresponding to document 224. When content management system 106 receives delete references message 506, content management system 106 can determine the locations of all references to document 224 in content management system 106. For example, content management system 106 can look up the locations of references to document 224 in reference map 224 using the identifier for document 224 received in message 506. After the locations of each reference to document 224 are determined using reference map 228, content management system 106 can remove each of the references to document 224 from content management system 106. Since the references (e.g., document reference 212) are content items managed by content management system 106, content management system 106 can cause the document references (and corresponding metadata) on each user device to be deleted when performing normal synchronization operations.
In some embodiments, content management system 106 can send delete references messages 508 and 510 to user devices 230 and 310, respectively, to cause user devices 230 and 310 to delete document references corresponding to document 224. For example, message 508 can identify document reference 242 on user device 230. CMS client 234 can use the identifier (e.g., file name, path, serial number, etc.) of document reference 242 to find document reference 242 and/or metadata 244 on user device 230. Once found, user device 230 can delete document reference 242 and/or metadata 244. Similarly, message 510 can identify document reference 314 on user device 310. CMS client 312 can use the identifier (e.g., file name, path, serial number, etc.) of document reference 314 to find document reference 314 and/or metadata 316 on user device 230. Once found, user device 310 can delete document reference 314 and/or metadata 316.
At step 602, a user device can receive a selection of a document reference stored on the user device. For example, a user of user device 230 can use a file browser on user device 230 to browse file system 240 and view a representation of document reference 242 and/or corresponding reference metadata 244. Document reference 242 can, for example, include a unique identifier for identifying a document within collaboration system 222. Document reference 242 can have a file extension or file type associated with CMS client 234. Reference metadata 244 can include, for example, a name, location, last modified timestamp, and/or other metadata that can be presented when presenting the representation of document reference 242, as described above.
At step 604, the user device can present a view of the document on the collaboration system corresponding to the document reference on the user device. For example, the user can select document reference 242 on user device 230 to invoke collaboration client 302 on user device 230, as described above. For example, user device 230 can be configured to open or invoke collaboration client 302 and/or CMS client 234 based on the file extension and/or file type of document reference 242. Collaboration client 302 can obtain the contents of document 224 from collaboration system 222 and present the contents of document 224 on a display of user device 230.
At step 606, the user device can receive user input modifying the document on the collaboration system. For example, the user can provide input to collaboration client 302 to edit the contents of document 224 on collaboration system 222. The user can provide input to collaboration client 302 to change the name of document 224. The user can provide input to collaboration client 302 to change the location where document 224 (e.g., reference 212) is stored in the file system of the user's account in content management system 106.
At step 608, the user device can send the document modification to the collaboration system. For example, collaboration client 302 can send information describing the edits and/or metadata changes (e.g., name change, location change, last modified timestamp change, etc.) to collaboration system 222.
At step 610, the collaboration system can update the state of the document and/or document metadata. For example, upon receiving the information describing the edits and/or metadata changes for document 224, collaboration system 222 can modify document 224 and/or document metadata 226 to reflect the edits and/or changes received from collaboration client 302.
At step 612, the collaboration system can send reference update information to the content management system. For example, after collaboration system 222 updates document 224 and/or document metadata 226 to reflect the edits and/or changes received from collaboration client 302, collaboration system 222 can send a document reference update message to content management system 106. The reference update message can include the unique identifier for document 224 and a description of changes made to document metadata 226.
At step 614, the content management system can update references to the document in the collaboration system based on the reference update information. For example, upon receipt of the reference update message, content management system 106 can identify document references in content management system 106 that refer to document 224. Content management system 106 can, for example, compare the unique identifier received in the reference update message to reference map 228 to identify and/or locate document references in content management system 106 that correspond to document 224. Content management system 106 can then update the reference metadata for each identified reference to reflect the changes made to document metadata 226.
At step 616, the content management system can synchronize references and/or reference metadata with user devices. For example, since the document references and/or reference metadata are content items managed by content management system 106, content management system 106 can synchronize the references and/or reference metadata with user devices similarly to other content items managed by content management system 106. Thus, user device 230 can present a representation of document reference 242 to a user that appears as if document reference 242 is the referenced document 224 on collaboration server 220.
At step 702, a user device can receive input renaming a document reference stored on the user device. For example, a user of user device 230 can use a file browser on user device 230 to browse file system 240 and view a representation of document reference 242 and/or corresponding reference metadata 244. Document reference 242 can, for example, include a unique identifier for identifying a document within collaboration system 222. Reference metadata 244 can include, for example, a name, location, last modified timestamp, and/or other metadata that can be presented when presenting the representation of document reference 242 on user device 230, as described above. The user can select an option in the file browser to rename document reference 242 and can provide input specifying a new name for document reference 242. The file browser can rename document reference 242 on user device 230 according to the new name specified by the user.
At step 704, the user device can synchronize the modified document reference with the user's account in the content management system. For example, since document reference 242 and/or reference metadata 244 are content items in file system 240 managed by CMS client 234 and content management system 106, CMS client 234 can automatically send information describing the change (e.g., the new name) to reference 242 and/or reference metadata 244 to content management system 106 upon detecting a change to document reference 242 and/or reference metadata 244.
In some implementations, upon receiving the information describing the change to reference 242 and/or reference metadata 244, content management system 106 can automatically update other references (e.g., reference and/or reference metadata) to document 224 managed by content management system 106. Alternatively, content management system 106 can wait for instructions from collaboration system 222 before updating references to document 224.
At step 706, the content management system can send a message to the collaboration system to rename the document corresponding to the renamed document reference. For example, content management system 106 can determine that the renamed content item (e.g., document reference 242) is a reference to a document in collaboration system 222 based on the type or extension of the content item. Based upon this determination, content management system 106 can send a message to collaboration system 222 to rename the document referenced by document reference 242. For example, content management system 106 can obtain an identifier for document 224 in collaboration system 222 from document reference 242. Content management system 106 can include the document identifier and the new name in the message sent to collaboration system 222.
At step 708, the collaboration system can rename the document corresponding to the renamed document reference. For example, upon receipt of the message from content management system 106, collaboration system 222 can rename the document (e.g., document 224) identified by the message according to the new name in the message. For example, collaboration system 222 can update document metadata 226 to reflect the new name for document 224.
At step 710, the collaboration system can send reference update information to the content management system. For example, after collaboration system 222 updates document 224 and/or document metadata 226 to reflect the new name specified by the user of user device 230, collaboration system 222 can send a document reference update message to content management system 106. The reference update message can include the unique identifier for document 224 and a description of changes (e.g., the new name) made to document metadata 226.
Alternatively, if content management system 106 is configured to update references at step 704, collaboration system 222 may not send reference update information to content management system 106 and process 700 can stop at step 708. For example, steps 712 and 714 can be performed at step 704.
At step 712, the content management system can update references to the document in the collaboration system based on the reference update information. For example, upon receipt of the reference update message, content management system 106 can identify document references in content management system 106 that refer to document 224. Content management system 106 can, for example, compare the unique identifier received in the reference update message to reference map 228 to identify and/or locate document references in various user accounts of content management system 106 that correspond to document 224. Content management system 106 can then update the reference metadata for each identified reference to reflect the changes made to document metadata 226.
At step 714, the content management system can synchronize references and/or reference metadata with user devices. For example, since the document references and/or reference metadata are content items managed by content management system 106, content management system 106 can synchronize the references and/or reference metadata with user devices similarly to other content items managed by content management system 106 so that all references to document 224 have the same name. Thus, user device 230 can present a representation of document reference 242 to a user that appears as if document reference 242 is the referenced document 224 on collaboration server 220.
8A and
To enable user interaction with the computing device 800, an input device 845 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 and so forth. An output device 835 can also 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 to communicate with the computing device 800. The communications interface 840 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 830 is a non-volatile memory 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) 825, read only memory (ROM) 820, and hybrids thereof.
The storage device 830 can include software modules 832, 834, 836 for controlling the processor 810. Other hardware or software modules are contemplated. The storage device 830 can be connected to the system bus 805. In one aspect, a hardware module 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 the processor 810, bus 805, display 835, and so forth, to carry out the function.
Chipset 860 can also interface with one or more communication interfaces 890 that can have different physical interfaces. Such communication interfaces can include interfaces for wired and wireless local area networks, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 810 analyzing data stored in storage 870 or 875. Further, the machine can receive inputs from a user via user interface components 885 and execute appropriate functions, such as browsing functions by interpreting these inputs using processor 810.
It can be appreciated that example systems 800 and 850 can have more than one processor 810 or be part of a group or cluster of computing devices networked together to provide greater processing capability.
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 modules, alone or in combination with other devices. In an embodiment, a software module 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 module. 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, 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 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 is a continuation of U.S. application Ser. No. 16/135,316, filed Sep. 19, 2018, which is a continuation of U.S. application Ser. No. 14/978,653, filed Dec. 22, 2015, now U.S. Pat. No. 10,108,688, issued Oct. 23, 2018, which are incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5634129 | Dickinson et al. | May 1997 | A |
5781732 | Adams | Jul 1998 | A |
6370567 | Ouchi | Apr 2002 | B1 |
6505236 | Pollack et al. | Jan 2003 | B1 |
6697838 | Jakobson | Feb 2004 | B1 |
6828992 | Freeman et al. | Dec 2004 | B1 |
6839741 | Tsai et al. | Jan 2005 | B1 |
6970906 | Parsons et al. | Nov 2005 | B1 |
7039678 | Halahmi et al. | May 2006 | B1 |
7266553 | Anderson et al. | Sep 2007 | B1 |
7386535 | Kalucha et al. | Jun 2008 | B1 |
7543237 | Kontny et al. | Jun 2009 | B2 |
7584199 | Matsusaka | Sep 2009 | B2 |
7689510 | Lamkin et al. | Mar 2010 | B2 |
7693958 | Teodosiu et al. | Apr 2010 | B2 |
7774710 | Krishnan et al. | Aug 2010 | B2 |
7818678 | Massand | Oct 2010 | B2 |
7865394 | Calloway et al. | Jan 2011 | B1 |
8015491 | Shaver et al. | Sep 2011 | B2 |
8117271 | McConn et al. | Feb 2012 | B2 |
8122015 | Liu et al. | Feb 2012 | B2 |
8122051 | Spring et al. | Feb 2012 | B2 |
8161120 | Tan et al. | Apr 2012 | B2 |
8196029 | Rucker et al. | Jun 2012 | B1 |
8214747 | Yankovich et al. | Jul 2012 | B1 |
8219407 | Roy et al. | Jul 2012 | B1 |
8245141 | Fuller et al. | Aug 2012 | B1 |
8250150 | Beck et al. | Aug 2012 | B2 |
8316128 | Beck et al. | Nov 2012 | B2 |
8341532 | Ryan et al. | Dec 2012 | B2 |
8438185 | Teranishi et al. | May 2013 | B2 |
8489676 | Chaplin et al. | Jul 2013 | B1 |
8533268 | Vernon et al. | Sep 2013 | B1 |
8543926 | Giles et al. | Sep 2013 | B2 |
8595642 | Lagassey | Nov 2013 | B1 |
8655943 | Gill | Feb 2014 | B2 |
8700719 | Covitz et al. | Apr 2014 | B1 |
8706760 | Edelstein et al. | Apr 2014 | B2 |
8713106 | Spataro et al. | Apr 2014 | B2 |
8793324 | Schabes et al. | Jul 2014 | B1 |
8881129 | McKinnon et al. | Nov 2014 | B1 |
8892679 | Destagnol et al. | Nov 2014 | B1 |
8930412 | Nelson et al. | Jan 2015 | B2 |
8959242 | Barrall | Feb 2015 | B1 |
8977722 | Tsao | Mar 2015 | B2 |
8984536 | Hushon, Jr. et al. | Mar 2015 | B1 |
8990151 | Savage et al. | Mar 2015 | B2 |
9002962 | Lynch et al. | Apr 2015 | B2 |
9166954 | Swineford et al. | Oct 2015 | B2 |
9235268 | Arrasvuori et al. | Jan 2016 | B2 |
9240962 | Jung et al. | Jan 2016 | B2 |
9251114 | Ancin et al. | Feb 2016 | B1 |
9251360 | Meyer et al. | Feb 2016 | B2 |
9298355 | Beausoleil et al. | Mar 2016 | B1 |
9300609 | Beausoleil et al. | Mar 2016 | B1 |
9361349 | Newhouse | Jun 2016 | B1 |
9395892 | Beausoleil et al. | Jul 2016 | B1 |
9395893 | Beausoleil et al. | Jul 2016 | B1 |
9436635 | Hushon, Jr. et al. | Sep 2016 | B1 |
9542391 | Eisner et al. | Jan 2017 | B1 |
9559996 | Clark et al. | Jan 2017 | B1 |
9641488 | Mityagin et al. | May 2017 | B2 |
9646010 | Mokhtarzada et al. | May 2017 | B2 |
9667676 | Lo et al. | May 2017 | B1 |
9727470 | Cande et al. | Aug 2017 | B1 |
9767101 | Abramson et al. | Sep 2017 | B2 |
9785658 | Suarez et al. | Oct 2017 | B2 |
9836549 | Heinrich et al. | Dec 2017 | B2 |
9846528 | Eccleston et al. | Dec 2017 | B2 |
9946691 | Grigorovitch et al. | Apr 2018 | B2 |
9959280 | Whitehead et al. | May 2018 | B1 |
9978040 | Lee et al. | May 2018 | B2 |
10007804 | Redberg | Jun 2018 | B2 |
10013574 | Hore | Jul 2018 | B2 |
10057140 | Fulton et al. | Aug 2018 | B2 |
10157084 | Nachtrab et al. | Dec 2018 | B2 |
10291395 | Nenov et al. | May 2019 | B1 |
10296594 | Datta | May 2019 | B1 |
10467426 | Esposito et al. | Nov 2019 | B1 |
10476758 | Marvin et al. | Nov 2019 | B2 |
10657228 | Kaplan et al. | May 2020 | B1 |
10664319 | Kaplan et al. | May 2020 | B1 |
10708273 | Tan | Jul 2020 | B2 |
10715524 | Paulus et al. | Jul 2020 | B1 |
10754827 | Kaplan et al. | Aug 2020 | B2 |
10762472 | Miller et al. | Sep 2020 | B1 |
20020062397 | Chang et al. | May 2002 | A1 |
20020120485 | Kirkconnell-Ewing et al. | Aug 2002 | A1 |
20020138582 | Chandra et al. | Sep 2002 | A1 |
20020169650 | Dougherty et al. | Nov 2002 | A1 |
20030046134 | Frolick et al. | Mar 2003 | A1 |
20030131062 | Miyashita et al. | Jul 2003 | A1 |
20030135565 | Estrada | Jul 2003 | A1 |
20040117445 | Lee et al. | Jun 2004 | A9 |
20040117839 | Watson et al. | Jun 2004 | A1 |
20040162878 | Lewis et al. | Aug 2004 | A1 |
20040187140 | Aigner et al. | Sep 2004 | A1 |
20040225647 | Connelly et al. | Nov 2004 | A1 |
20050022931 | Min et al. | Feb 2005 | A1 |
20050028008 | Kumar | Feb 2005 | A1 |
20050091289 | Shappell et al. | Apr 2005 | A1 |
20050097440 | Lusk et al. | May 2005 | A1 |
20050097441 | Herbach et al. | May 2005 | A1 |
20050108293 | Lipman et al. | May 2005 | A1 |
20050198125 | Macleod et al. | Sep 2005 | A1 |
20050198299 | Beck et al. | Sep 2005 | A1 |
20050222931 | Mamou et al. | Oct 2005 | A1 |
20050223315 | Shimizu et al. | Oct 2005 | A1 |
20050289512 | Matsusaka | Dec 2005 | A1 |
20060020904 | Aaltonen et al. | Jan 2006 | A1 |
20060080432 | Spataro et al. | Apr 2006 | A1 |
20060101443 | Nasr | May 2006 | A1 |
20060136821 | Barabe et al. | Jun 2006 | A1 |
20070005449 | Mathew et al. | Jan 2007 | A1 |
20070033088 | Aigner et al. | Feb 2007 | A1 |
20070050324 | Trinkel et al. | Mar 2007 | A1 |
20070050733 | Lee et al. | Mar 2007 | A1 |
20070067726 | Flynt et al. | Mar 2007 | A1 |
20070100829 | Allen et al. | May 2007 | A1 |
20070150551 | Krishnan et al. | Jun 2007 | A1 |
20070237153 | Slaughter | Oct 2007 | A1 |
20070276795 | Poulsen et al. | Nov 2007 | A1 |
20070277098 | Shahar et al. | Nov 2007 | A1 |
20070288839 | Kurosawa et al. | Dec 2007 | A1 |
20080028323 | Rosen et al. | Jan 2008 | A1 |
20080040388 | Petri | Feb 2008 | A1 |
20080059539 | Chin et al. | Mar 2008 | A1 |
20080077614 | Roy et al. | Mar 2008 | A1 |
20080091761 | Tsao | Apr 2008 | A1 |
20080120382 | Heidloff et al. | May 2008 | A1 |
20080140732 | Wilson et al. | Jun 2008 | A1 |
20080195659 | Rawle | Aug 2008 | A1 |
20080201422 | Peccora et al. | Aug 2008 | A1 |
20080243846 | Rasmussen | Oct 2008 | A1 |
20080256458 | Aldred et al. | Oct 2008 | A1 |
20080288453 | Smetters et al. | Nov 2008 | A1 |
20090013043 | Tan | Jan 2009 | A1 |
20090043733 | Kingsford et al. | Feb 2009 | A1 |
20090064284 | Poston et al. | Mar 2009 | A1 |
20090131116 | Tsuchiya et al. | May 2009 | A1 |
20090138808 | Moromisato et al. | May 2009 | A1 |
20090158167 | Wang et al. | Jun 2009 | A1 |
20090177754 | Brezina et al. | Jul 2009 | A1 |
20090182778 | Tormasov | Jul 2009 | A1 |
20090235182 | Kagawa et al. | Sep 2009 | A1 |
20090249244 | Robinson et al. | Oct 2009 | A1 |
20090282421 | Jaffer et al. | Nov 2009 | A1 |
20090307605 | Ryan et al. | Dec 2009 | A1 |
20100024011 | Fukuoka | Jan 2010 | A1 |
20100082713 | Frid-Nielsen et al. | Apr 2010 | A1 |
20100095198 | Bultrowicz et al. | Apr 2010 | A1 |
20100138503 | Ishikawa et al. | Jun 2010 | A1 |
20100151431 | Miller et al. | Jun 2010 | A1 |
20100180196 | Matsusaka | Jul 2010 | A1 |
20100211621 | Hariharan et al. | Aug 2010 | A1 |
20100241711 | Ansari et al. | Sep 2010 | A1 |
20100251175 | Brunkhorst et al. | Sep 2010 | A1 |
20100262435 | Smith et al. | Oct 2010 | A1 |
20100299763 | Marcus et al. | Nov 2010 | A1 |
20100325199 | Park et al. | Dec 2010 | A1 |
20100332453 | Prahlad et al. | Dec 2010 | A1 |
20110014524 | Skotheim et al. | Jan 2011 | A1 |
20110022662 | Barber-Mingo et al. | Jan 2011 | A1 |
20110055385 | Tung et al. | Mar 2011 | A1 |
20110119353 | Tsao | May 2011 | A1 |
20110145245 | Choi et al. | Jun 2011 | A1 |
20110161795 | Bellwood et al. | Jun 2011 | A1 |
20110202430 | Narayanan et al. | Aug 2011 | A1 |
20110214088 | Sandru et al. | Sep 2011 | A1 |
20110247031 | Jacoby | Oct 2011 | A1 |
20110249024 | Arrasvuori et al. | Oct 2011 | A1 |
20110258554 | Sidenur et al. | Oct 2011 | A1 |
20110301982 | Green, Jr. et al. | Dec 2011 | A1 |
20120011102 | Borden | Jan 2012 | A1 |
20120079389 | Tsao | Mar 2012 | A1 |
20120089610 | Agrawal et al. | Apr 2012 | A1 |
20120124092 | Teranishi et al. | May 2012 | A1 |
20120143917 | Prabaker et al. | Jun 2012 | A1 |
20120151379 | Schultz et al. | Jun 2012 | A1 |
20120166516 | Simmons et al. | Jun 2012 | A1 |
20120182384 | Anderson et al. | Jul 2012 | A1 |
20120192055 | Antebi et al. | Jul 2012 | A1 |
20120192086 | Ghods et al. | Jul 2012 | A1 |
20120221520 | Garrett et al. | Aug 2012 | A1 |
20120284290 | Keebler et al. | Nov 2012 | A1 |
20120290531 | Kallakuri et al. | Nov 2012 | A1 |
20120290926 | Kapadia et al. | Nov 2012 | A1 |
20120297183 | Mukkara et al. | Nov 2012 | A1 |
20120311060 | Beck et al. | Dec 2012 | A1 |
20120317239 | Mulder et al. | Dec 2012 | A1 |
20120331108 | Ferdowsi et al. | Dec 2012 | A1 |
20130013560 | Goldberg et al. | Jan 2013 | A1 |
20130014023 | Lee et al. | Jan 2013 | A1 |
20130024788 | Olsen et al. | Jan 2013 | A1 |
20130073971 | Huang et al. | Mar 2013 | A1 |
20130080919 | Kiang et al. | Mar 2013 | A1 |
20130110903 | Myerscough et al. | May 2013 | A1 |
20130117376 | Filman et al. | May 2013 | A1 |
20130124638 | Barreto et al. | May 2013 | A1 |
20130138608 | Smith | May 2013 | A1 |
20130138723 | Ku et al. | May 2013 | A1 |
20130173798 | Micucci et al. | Jul 2013 | A1 |
20130179799 | Savage | Jul 2013 | A1 |
20130191339 | Haden et al. | Jul 2013 | A1 |
20130198600 | Lockhart et al. | Aug 2013 | A1 |
20130212112 | Blom et al. | Aug 2013 | A1 |
20130218829 | Martinez | Aug 2013 | A1 |
20130227015 | Mihara et al. | Aug 2013 | A1 |
20130246901 | Massand | Sep 2013 | A1 |
20130254699 | Bashir et al. | Sep 2013 | A1 |
20130275509 | Micucci et al. | Oct 2013 | A1 |
20130285893 | Hanes | Oct 2013 | A1 |
20130297317 | Lee et al. | Nov 2013 | A1 |
20130305165 | Zuber et al. | Nov 2013 | A1 |
20130311557 | Motes et al. | Nov 2013 | A1 |
20130325822 | Sambamurthy et al. | Dec 2013 | A1 |
20140012836 | Bercovici et al. | Jan 2014 | A1 |
20140013246 | Beechuk et al. | Jan 2014 | A1 |
20140019498 | Cidon et al. | Jan 2014 | A1 |
20140029751 | Swineford et al. | Jan 2014 | A1 |
20140047560 | Meyer et al. | Feb 2014 | A1 |
20140068401 | Kirigin | Mar 2014 | A1 |
20140082073 | Wable et al. | Mar 2014 | A1 |
20140082101 | Wable et al. | Mar 2014 | A1 |
20140089406 | Gniffke et al. | Mar 2014 | A1 |
20140101310 | Savage et al. | Apr 2014 | A1 |
20140122569 | Abel et al. | May 2014 | A1 |
20140122592 | Houston et al. | May 2014 | A1 |
20140133632 | Wakai et al. | May 2014 | A1 |
20140136989 | Choi et al. | May 2014 | A1 |
20140156416 | Goenka et al. | Jun 2014 | A1 |
20140164535 | Lynch et al. | Jun 2014 | A1 |
20140172925 | Goldbrenner et al. | Jun 2014 | A1 |
20140181153 | Moore et al. | Jun 2014 | A1 |
20140208220 | Watal | Jul 2014 | A1 |
20140210756 | Lee et al. | Jul 2014 | A1 |
20140215551 | Allain et al. | Jul 2014 | A1 |
20140222917 | Poirier | Aug 2014 | A1 |
20140229839 | Lynch et al. | Aug 2014 | A1 |
20140237464 | Waterman et al. | Aug 2014 | A1 |
20140258350 | Duval et al. | Sep 2014 | A1 |
20140280484 | Klemenz et al. | Sep 2014 | A1 |
20140289351 | Chen et al. | Sep 2014 | A1 |
20140289645 | Megiddo et al. | Sep 2014 | A1 |
20140289658 | Gelernter et al. | Sep 2014 | A1 |
20140294167 | Kim et al. | Oct 2014 | A1 |
20140297759 | Mody | Oct 2014 | A1 |
20140298207 | Ittah et al. | Oct 2014 | A1 |
20140304618 | Carriero et al. | Oct 2014 | A1 |
20140304836 | Velamoor et al. | Oct 2014 | A1 |
20140344739 | Yoon | Nov 2014 | A1 |
20140358882 | Diab | Dec 2014 | A1 |
20140359465 | Litan et al. | Dec 2014 | A1 |
20140365263 | Honeyman et al. | Dec 2014 | A1 |
20140372539 | Zaveri | Dec 2014 | A1 |
20140372906 | Campbell et al. | Dec 2014 | A1 |
20140372923 | Rossi et al. | Dec 2014 | A1 |
20150019480 | Maquaire et al. | Jan 2015 | A1 |
20150026260 | Worthley et al. | Jan 2015 | A1 |
20150026604 | Mulukuri et al. | Jan 2015 | A1 |
20150032829 | Barshow et al. | Jan 2015 | A1 |
20150039360 | Gowdra et al. | Feb 2015 | A1 |
20150074044 | Metreveli et al. | Mar 2015 | A1 |
20150095799 | Tsao | Apr 2015 | A1 |
20150100889 | Tuchman et al. | Apr 2015 | A1 |
20150134751 | Meyers, Jr. et al. | May 2015 | A1 |
20150135097 | Carriero et al. | May 2015 | A1 |
20150135300 | Ford et al. | May 2015 | A1 |
20150142742 | Hong | May 2015 | A1 |
20150149929 | Shepherd et al. | May 2015 | A1 |
20150156274 | Alten et al. | Jun 2015 | A1 |
20150160989 | Maes et al. | Jun 2015 | A1 |
20150169566 | Yang et al. | Jun 2015 | A1 |
20150188960 | Alhaidar et al. | Jul 2015 | A1 |
20150200885 | Sharp et al. | Jul 2015 | A1 |
20150213037 | Baldwin et al. | Jul 2015 | A1 |
20150286371 | Degani et al. | Oct 2015 | A1 |
20150288775 | Larabie-Belanger | Oct 2015 | A1 |
20150294024 | Zhang | Oct 2015 | A1 |
20150302338 | Zaveri | Oct 2015 | A1 |
20150302421 | Caton et al. | Oct 2015 | A1 |
20150304265 | Vincent et al. | Oct 2015 | A1 |
20150365497 | Zhao et al. | Dec 2015 | A1 |
20150370796 | Abramson et al. | Dec 2015 | A1 |
20150378974 | Massand | Dec 2015 | A1 |
20160034844 | Kofman | Feb 2016 | A1 |
20160062839 | Kapoor | Mar 2016 | A1 |
20160072889 | Jung et al. | Mar 2016 | A1 |
20160085421 | Feeney | Mar 2016 | A1 |
20160094495 | Ahuja et al. | Mar 2016 | A1 |
20160098493 | Primke et al. | Apr 2016 | A1 |
20160127452 | Newman et al. | May 2016 | A1 |
20160132529 | Acharya | May 2016 | A1 |
20160140139 | Torres et al. | May 2016 | A1 |
20160179967 | Sa et al. | Jun 2016 | A1 |
20160182515 | Barraclough et al. | Jun 2016 | A1 |
20160241509 | Akcin | Aug 2016 | A1 |
20160247245 | Baic et al. | Aug 2016 | A1 |
20160259413 | Anzures et al. | Sep 2016 | A1 |
20160259508 | Eccleston et al. | Sep 2016 | A1 |
20160269335 | Kell | Sep 2016 | A1 |
20160275303 | Narayanaswamy et al. | Sep 2016 | A1 |
20160277537 | Liang et al. | Sep 2016 | A1 |
20160283085 | Beausoleil et al. | Sep 2016 | A1 |
20160283502 | Beausoleil et al. | Sep 2016 | A1 |
20160283567 | Beausoleil et al. | Sep 2016 | A1 |
20160285702 | Beausoleil et al. | Sep 2016 | A1 |
20160285795 | Beausoleil et al. | Sep 2016 | A1 |
20160285796 | Beausoleil et al. | Sep 2016 | A1 |
20160285797 | Beausoleil et al. | Sep 2016 | A1 |
20160285817 | Beausoleil et al. | Sep 2016 | A1 |
20160285818 | Beausoleil et al. | Sep 2016 | A1 |
20160285890 | Beausoleil et al. | Sep 2016 | A1 |
20160328522 | Howley | Nov 2016 | A1 |
20170006102 | Mody et al. | Jan 2017 | A1 |
20170024392 | Shah et al. | Jan 2017 | A1 |
20170024410 | Pola | Jan 2017 | A1 |
20170046531 | Roberts | Feb 2017 | A1 |
20170078302 | Mellor et al. | Mar 2017 | A1 |
20170192656 | Pedrick et al. | Jul 2017 | A1 |
20170214726 | Malatesha et al. | Jul 2017 | A1 |
20170220605 | Nivala et al. | Aug 2017 | A1 |
20170220657 | Nivala et al. | Aug 2017 | A1 |
20170250969 | O'Brien et al. | Aug 2017 | A1 |
20170272335 | Hamlin et al. | Sep 2017 | A1 |
20170279859 | Pogorelik | Sep 2017 | A1 |
20170285928 | Beausoleil et al. | Oct 2017 | A1 |
20170315790 | Samatov et al. | Nov 2017 | A1 |
20170359353 | Tan | Dec 2017 | A1 |
20180027006 | Zimmermann et al. | Jan 2018 | A1 |
20180063143 | Wilson et al. | Mar 2018 | A1 |
20180063258 | Wang et al. | Mar 2018 | A1 |
20180067811 | Mowatt | Mar 2018 | A1 |
20180074786 | Oberbreckling et al. | Mar 2018 | A1 |
20180113870 | Rogers | Apr 2018 | A1 |
20180150477 | Jewell et al. | May 2018 | A1 |
20180150552 | Wang | May 2018 | A1 |
20180198742 | Subramani et al. | Jul 2018 | A1 |
20180285206 | Mehta et al. | Oct 2018 | A1 |
20180300756 | Saxena et al. | Oct 2018 | A1 |
20180322510 | Cleaver et al. | Nov 2018 | A1 |
20180349408 | Jewell et al. | Dec 2018 | A1 |
20190121518 | Anima et al. | Apr 2019 | A1 |
20190121863 | Embiricos et al. | Apr 2019 | A1 |
20190121875 | Niu et al. | Apr 2019 | A1 |
20190205474 | Pawar et al. | Jul 2019 | A1 |
20190272281 | Hawa et al. | Sep 2019 | A1 |
20190278589 | Cook et al. | Sep 2019 | A1 |
20190318015 | Cheesman | Oct 2019 | A1 |
20190339843 | Yost | Nov 2019 | A1 |
20200026532 | Bill et al. | Jan 2020 | A1 |
20200053111 | Jakobsson | Feb 2020 | A1 |
20200076862 | Eliason et al. | Mar 2020 | A1 |
20200099772 | Ray et al. | Mar 2020 | A1 |
20200133982 | Thangeswaran et al. | Apr 2020 | A1 |
20200142549 | Kaplan et al. | May 2020 | A1 |
20200142750 | Kaplan et al. | May 2020 | A1 |
20200142751 | Kaplan et al. | May 2020 | A1 |
20200142863 | Kaplan et al. | May 2020 | A1 |
20200142936 | Kaplan et al. | May 2020 | A1 |
20200143011 | Kaplan et al. | May 2020 | A1 |
20200143074 | Steinberg et al. | May 2020 | A1 |
20200145499 | Kaplan et al. | May 2020 | A1 |
20200265014 | Kaplan et al. | Aug 2020 | A1 |
20200265015 | Kaplan et al. | Aug 2020 | A1 |
20200279028 | Kaplan et al. | Sep 2020 | A1 |
20200293356 | Bonaud et al. | Sep 2020 | A1 |
Number | Date | Country |
---|---|---|
2016201472 | Dec 2016 | AU |
2017201395 | Mar 2017 | AU |
2016201019 | Apr 2017 | AU |
2017204625 | Jul 2017 | AU |
2016235983 | Oct 2017 | AU |
2016236015 | Oct 2017 | AU |
2016235985 | Jun 2018 | AU |
2016235984 | Oct 2018 | AU |
104506527 | Apr 2015 | CN |
105100170 | Nov 2015 | CN |
107431631 | Dec 2017 | CN |
107438840 | Dec 2017 | CN |
3073674 | Sep 2016 | EP |
3251290 | Dec 2017 | EP |
3251305 | Dec 2017 | EP |
3251288 | Sep 2019 | EP |
3073673 | Jul 2020 | EP |
3251289 | Sep 2020 | EP |
S61279916 | Dec 1986 | JP |
2000060803 | Feb 2000 | JP |
2001202405 | Jul 2001 | JP |
2002244988 | Aug 2002 | JP |
2002297883 | Oct 2002 | JP |
2003256323 | Sep 2003 | JP |
2004013267 | Jan 2004 | JP |
2004046796 | Feb 2004 | JP |
2004362118 | Dec 2004 | JP |
2006092074 4 | Apr 2006 | JP |
2006189958 | Jul 2006 | JP |
2007072523 | Mar 2007 | JP |
2009069899 | Apr 2009 | JP |
2013161481 | Aug 2013 | JP |
2013175059 | Sep 2013 | JP |
2014134961 | Jul 2014 | JP |
2015032092 | Feb 2015 | JP |
6028118 | Oct 2016 | JP |
2016181250 | Oct 2016 | JP |
2016184404 | Oct 2016 | JP |
2017084356 | May 2017 | JP |
2017182790 | Oct 2017 | JP |
6416806 | Oct 2018 | JP |
2010102296 | Sep 2010 | WO |
2013033144 | Mar 2013 | WO |
2016085822 | Jun 2016 | WO |
2016106088 | Jun 2016 | WO |
2016153676 | Sep 2016 | WO |
2016153735 | Sep 2016 | WO |
2016153736 | Sep 2016 | WO |
2016153737 | Sep 2016 | WO |
2016168748 | Oct 2016 | WO |
Entry |
---|
Office Action for Chinese Applications No. 201980057741.4, dated Aug. 13, 2021, 9 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,674, dated Jul. 15, 2021, 12 pages. |
Wikihow, “How to Use Facebook(with cheat sheet)”, 2013, retrieved from http://www.wikihow.com/Use-Facebook on Mar. 28, 2019, 7 pages. |
Beliz System, “Making Documents on Google Drive,” Digital Documents Laboratories, Jul. 18, 2014, Retrieved from: https://watasu.com/dedoken/cloud/page2.html, 9 pages. |
Communication Pursuant to Article 94(3) EPC for European Application No. 17805064.7 dated Nov. 5, 2019, 4 pages. |
Crucial Works Inc, “Sharing Folders,” Apps x Support, Jan. 29, 2013, Retrieved from: https://web.archive,org/web/20130129101828/http://www.appsupport.jp/drive/share-folder on Aug. 29, 2017, 8 pages. |
Examination Report No. 1, for Australian Application No. 2017385026, dated Nov. 28, 2019, 6 pages. |
Examination Report No. 2, for Australian Application No. 2017385026, dated Apr. 30, 2020, 5 pages. |
Examination Report No. 3, for Australian Application No. 2017385026, dated Aug. 4, 2020, 6 pages. |
White C., “5 Unusual Ways to Use Dropbox You Might Not Have Thought Of,” Dec. 18, 2010, retrieved from http://mashable.com/2010/12/18/dropbox-uses/ on Sep. 15, 2017, 3 pages. |
Voida S., et al., “Share and Share Alike: Exploring the User Interface Affordances of File Sharing,” Proceedings of the ACM Conference on Human Factors in Computing Systems (CHI 2006), Apr. 22-27, 2006, ACM, 10 pages. |
Summons to attend oral proceedings pursuant to Rule 115(1) EPC for European Application No. 17805064.7 mailed on Apr. 21, 2020, 9 pages. |
Freedman V., et al., “A Collaborative Extensible User Environment for Simulation and Knowledge Management,” IEEE, 2015, pp. 280-286. |
Google Inc., “View and Create Documents on Android,” Mar. 19, 2015, Wayback Machine, Google Docs, downloaded from https://web.archive.org/web/20150319022434/https://support.google.com/docs/answer/3420399? hl=en, May 30, 2016, 3 pages. |
Hoomey, Estyle Inc., “Google Drive How to Use Leverage Surgery “spreadsheet” that can be used in Excel instead!,” Nov. 9, 2013, retrieved from https://web.archive.org/web/20131109104805/http:/1hoomey.net/googledrive-study-4 on Jun. 30, 2016, 18 pages. |
International Appl. No. PCT/US2019/057636, International Search Report and Written Opinion dated Apr. 1, 2020, 18 pages. |
International Search Report and Written Opinion for PCT Application No. PCT/US16/19052, dated Nov. 7, 2016, 9 pages. |
International Search Report and Written Opinion for PCT Application No. PCT/US16/20117, dated May 13, 2016, 10 pages. |
International Search Report and Written Opinion for PCT Application No. PCT/US16/20124, dated May 24, 2016, 10 pages. |
International Search Report and Written Opinion for PCT Application No. PCT/US16/20132, dated May 24, 2016, 9 pages. |
International Search Report and Written Opinion for PCT Application No. PCT/US2017/061204 dated Dec. 21, 2017, 9 pages. |
International Search Report and Written Opinion for PCT Application No. PCT/US2017/061206 dated Jan. 3, 2018, 11 pages. |
“Intralinks VIA,” 2015, Retrieved from https://www/intralinks.com/sites/default/files/file_attach/intralinks_via_brochure.pdf, 13 pages. |
Iwashi, “How to Use Google Documents,” Wind-mill Iwashi Blog, Dec. 17, 2014, retrieved from http://wind-mill.co.jp/iwashiblog/2014/12/google-document/, Mar. 27, 2019, 12 pages. |
Mislove A., et al., “Post: A secure, resilient, cooperative messaging system,” Conference: Proceedings of HotOS'03: 9th Workshop on Hot Topics in Operating Systems, Lihue (Kauai), Hawaii, USA, May 18-21, 2003, 6 pages. |
Nelson J C., “Wide-Area Software-Defined Storage,” Jun. 2018, ProQuest Dissertations & Theses Global:The Sciences and Engineering Collection, 267 Pages. |
Non-Final Office Action from U.S. Appl. No. 16/582,361, dated Jan. 8, 2020, 8 pages. |
Non-Final Office Action from U.S. Appl. No. 16/582,425, dated Jan. 13, 2020, 8 pages. |
Non-Final Office Action from U.S. Appl. No. 16/582,685, dated Jun. 23, 2020, 37 pages. |
Shimada H., “Online Storage Service having Documents-Editing Functions: Introduction to Google Drive for a Person that Missed the Wave,” ITmedia Inc., Feb. 7, 2014, retrieved from internet URL: https://web.archive.org/web/20140207083317/ and http://www.atmarkit.co.jp/ait/articles/1303/13/news1 05.html on May 27, 2016, 21 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,361, dated Mar. 30, 2020, 10 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,455, dated Dec. 12, 2019, 9 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,455, dated May 18, 2020, 5 pages. |
Notice of Allowance from U.S. Appl. No. 16/866,228, dated Sep. 9, 2020, 13 pages. |
Notification of Reason(s) for Refusal for Japanese Application No. 2019-508895 dated Aug. 21, 2020, 7 pages. |
Notice of Allowance from U.S. Appl. No. 16/866,253, dated Sep. 8, 2020, 12 pages. |
Notice of Allowance from U.S. Appl. No. 16/877,196, dated Nov. 3, 2020, 10 pages. |
Notice of Allowance from U.S. Appl. No. 16/877,196, dated Sep. 23, 2020, 13 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,685, dated Sep. 30, 2021, 13 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,809, dated Oct. 13, 2021, 9 pages. |
Advisory Action from U.S. Appl. No. 16/135,316, dated Jun. 5, 2020, 3 pages. |
Examination Report No. 4, for Australian Application No. 2017385026, dated Nov. 20, 2020, 5 pages. |
Final Office Action from U.S. Appl. No. 16/135,316, dated Mar. 30, 2020, 24 pages. |
Final Office Action from U.S. Appl. No. 16/582,685, dated Jan. 27, 2021, 52 pages. |
Notice of Allowance from U.S. Appl. No. 16/135,316, dated Dec. 4, 2020, 14 pages. |
Notice of Allowance from U.S. Appl. No. 16/866,253, dated Nov. 27, 2020, 9 pages. |
Advisory Action from U.S. Appl. No. 16/588,628, dated Dec. 15, 2020, 3 pages. |
Andrew, “What's new in Syncdocs 0.52”, May 9, 2011, retrieved from http://syncdocs.com/2011/05/what%E2%80%99s-new-in-syncdocs-0-52/, on Apr. 23, 2020, 5 pages. |
Final Office Action from U.S. Appl. No. 16/588,628, dated Sep. 8, 2020, 25 pages. |
Metactrl.com, “Google Drive: Multiple Files with the Same Path”, retrieved from https://metactri.com/docs/gdrive-same-path/ archived on Jun. 19, 2016, at http://web.archive.org, 4 pages. |
Non-Final Office Action from U.S. Appl. No. 16/588,628, dated Apr. 28, 2020, 22 pages. |
Non-Final Office Action from U.S. Appl. No. 16/588,628, dated Feb. 8, 2021, 30 pages. |
Notice of Allowance from U.S. Appl. No. 16/588,628, dated May 10, 2021, 15 pages. |
Decision to refuse European Patent Application No. 17805064.7 dated Feb. 12, 2021, 32 pages. |
Non-Final Office Action from U.S. Appl. No. 16/582,809, dated Apr. 27, 2021, 15 pages. |
Communication pursuant to Rules 161(1) and 162 EPC for European application No. 19805433.0 dated Mar. 3, 2021, 16 pages. |
Non-Final Office Action from U.S. Appl. No. 16/582,685, dated Mar. 30, 2021, 51 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,425, dated Mar. 25, 2020, 10 pages. |
Notice of Allowance from U.S. Appl. No. 16/582,674, dated Apr. 7, 2021, 12 pages. |
Notice of Reasons for Refusal for Japanese Application No. 2021-512397, dated Nov. 22, 2021, 6 pages. |
Examination Report No. 1 for Australian Application No. 2021203780 dated Feb. 22, 2022, 2 pages. |
Communication pursuant to Rules 94(3) EPC for European application No. 19805433.0 dated Nov. 7, 2022, 14 pages. |
Notice of Allowance from U.S. Appl. No. 17/336,835, dated Nov. 18, 2022, 07 pages. |
Non-Final Office Action from U.S. Appl. No. 17/336,835, dated Sep. 2, 2022, 24 pages. |
Number | Date | Country | |
---|---|---|---|
20210149914 A1 | May 2021 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16135316 | Sep 2018 | US |
Child | 17162254 | US | |
Parent | 14978653 | Dec 2015 | US |
Child | 16135316 | US |