System, method, and computer program for enabling a user to access and edit via a virtual drive objects synchronized to a plurality of synchronization clients

Information

  • Patent Grant
  • 10805389
  • Patent Number
    10,805,389
  • Date Filed
    Wednesday, May 30, 2018
    6 years ago
  • Date Issued
    Tuesday, October 13, 2020
    4 years ago
Abstract
A system, method, and computer program for enabling a user to edit and access local and remote objects via a virtual drive, including objects synchronized to a plurality of synchronization clients. A virtual drive is displayed on the user's local client device with all objects, which a user has synchronized to a synchronization server. A user is able to access and edit any object displayed in the virtual drive. In response to detecting a change in an object in the virtual drive, the object is updated on the synchronization server. All remote clients of the user or of any other users who have access to the changed folder are identified and notified of the change. In response to the change being a change to content within the folder, the content of the folder is automatically updated on any identified remote clients that have a corresponding folder.
Description
BACKGROUND OF THE INVENTION
1. Field of the Invention

This invention relates generally to a synchronization system and, more particularly, to a system and method for enabling a user to access and edit, via a virtual drive, objects synchronized to a plurality of synchronization clients.


2. Description of the Background Art

Many users have multiple computing devices, such as a home computer, a work computer, and a mobile phone. Different files may be stored by synchronization software clients on different devices. Virtual drives enable a user to back up files on a computer to a server and have remote access to files stored on the server, presented as though the files exist on a locally mounted file system. However, in a synchronization system, a user may have synchronized an object to multiple clients, and known virtual drives do not enable a user to make a change to a remote file and then have that change automatically synchronized across multiple clients. As an example, User A has a folder that resides on his work and home computer. User A has also shared that folder with User B. User A desires not only to be able to remotely access the folder from another synchronization software client via a virtual drive, but also to have any changes made to the folder via the virtual drive automatically synchronized to his home and work computer, as well as any client devices of User B that have a corresponding copy of the folder. Therefore, there is a need for a system and method for enabling a user to access and edit via a virtual drive objects synchronized to a plurality of synchronization clients.


SUMMARY OF THE INVENTION

The present invention is directed to a synchronization system, method, and computer program for enabling a user to access and edit, via a virtual drive, local and remote objects, including objects synchronized to a plurality of synchronization software clients. The present invention enables a user to make a change to an object via a virtual drive and have that change automatically synchronized to a plurality of synchronization clients.


The method includes enabling a user to synchronize one or more objects using a synchronization software client, a synchronization server, and other synchronization clients. Objects may be folders, music files, video files, images, contacts, calendar items, and other types of electronic files or items. All objects, across a plurality of synchronization clients that a user has synchronized to the synchronization server, are identified. A virtual drive is displayed on the user's local client device with the identified objects. The virtual drive appears as a separate disk drive on the user's local client device and includes objects that reside on one or more remote clients. A user is able to access and edit any object displayed in the virtual drive, including objects that reside only on remote clients. In response to detecting a change in an object in the virtual drive, the object is updated on the synchronization server. All remote synchronization clients of the user are identified in the synchronization system, as well as all remote synchronization clients, if any, of other users whom have access to the changed object. The identified synchronization clients are notified of the change to the object. In response to the change being a change to content within the object, the content of the object is automatically updated on any identified remote clients that have a corresponding object.


In certain embodiments, a user is able to create a collection that comprises items across a plurality of synchronization clients that share one or more specified attributes, regardless of the folder(s) in which the items reside. The collection is displayed in the virtual drive. A user is able to access and edit items within the collection. In response to a user editing an item within a collection, a folder is identified in which the item resides. The folder is updated on the synchronization server with the edit to the item. All remote synchronization clients of the user in the synchronization system are identified, as well as all remote synchronization software clients, if any, of other users whom have access to the changed folder. The identified clients are notified of the change to the folder. In response to the change being a change to content within the folder, the content of the folder is automatically updated on any identified remote clients that have a corresponding folder. In certain embodiments, the items in the collection are not limited to files organized within folders on a file system, but are arbitrary objects existing within an arbitrary organizational scheme.


The attributes may be specified by the user, other software programs, or the synchronization system. The attributes may include one or more of the following: location associated with the file, version of the file, a time stamp associated with the file, client device on which the file resides, and the file type. The attributes may include a permission class associated with the shared files.


In one embodiment the user is able to perform share and synchronization functions via the virtual drive. The folders in the virtual drive may be organized by client device or may be client device-independent.





BRIEF DESCRIPTION OF THE DRAWINGS


FIGS. 1a-1b are a flowchart that illustrates a method, according to one embodiment of the invention, for enabling a user to access and edit, via a virtual drive, local and remote objects, including objects synchronized to a plurality of synchronization software clients.



FIGS. 1c-1d are a flowchart that illustrates a further embodiment of the invention in which a user is able to view, access, and synchronize collections via a virtual drive.



FIG. 2 is a block diagram of a synchronization system according to one embodiment of the invention.



FIG. 3 is a block diagram of a synchronization system according to one embodiment of the invention.



FIGS. 4a-4b are a flowchart that illustrates a method for enabling a user to change a remote folder via the virtual drive according to one embodiment of the invention.



FIGS. 5-6 are screenshots of an exemplary user interface in a synchronization system according to one embodiment of the invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention provides a system, method, and computer program for enabling a user to access and edit, via a virtual drive, local and remote objects in a synchronization system, including objects synchronized to a plurality of synchronization software clients. Examples of synchronization systems are disclosed in (i) U.S. Pat. No. 7,885,925, titled “Method and Apparatus for File Sharing and Synchronization System,” and (ii) U.S. Pat. No. 8,019,900, titled “Opportunistic Peer to Peer Synchronization in a Synchronization System.” The contents of both of these patents are incorporated herein by reference as if fully disclosed herein. A person skilled in the art would understand that other synchronization systems may be used within the scope of the present invention.


As used herein, a virtual drive is a file system representation on the user's local client device, of data from a source that is external to the local file system. In the present invention, the virtual drive provides a file system representation, on the user's local client device, of all objects, across a plurality of clients including the local client, which a user has synchronized or otherwise saved to the synchronization system. In the preferred embodiment, a local sync database stores metadata about these objects, and this metadata is used to generate the virtual drive. As used herein, metadata is a collection of attributes that describe the state of an object and is used by the synchronization system to detect and orchestrate changes to the object.


As used herein, an object may be a folder, a file (e.g., a WORD document, an EXCEL spreadsheet, a POWERPOINT presentation, an email, contact, or calendar item, such as in MICROSOFT OUTLOOK), a media object (e.g., a video file, an audio or music file, an image file), or a collection. A person skilled in the art would understand that objects are not limited to the above-specified examples.


As used herein, a collection includes items, across a plurality of synchronization software clients, which share one or more specified attributes. An attribute is a property that the user can assign to any object or collection (e.g., client name). An attribute has an attribute value (i.e., the value that a user might assign to an attribute) and an attribute type (i.e., the data type of the attribute value). One example of a collection may be the user's recent photographs from Hawaii that are stored across the user's camera, mobile device, laptop, and home computer. Attributes may be specified automatically by the synchronization system, by another software program, or by the user. Types of attributes available for specification by the user include (i) permission class associated with a shared object, (ii) a file type associate with a file, (iii) a location associated with an object, (iv) version of the file, (v) time stamp associated with the file, (vi) client device on which the file resides, and (vii) an arbitrary attribute type defined by the user or other software program. A person skilled in the art would understand that other attributes may be assigned within the scope of the present invention.



FIGS. 1a-1b illustrate a method, according to one embodiment, for enabling a user to access and edit, via a virtual drive, local and remote objects in a synchronization system, including objects synchronized to a plurality of synchronization clients. In the preferred embodiment, the objects are folders that may contain documents (e.g., EXCEL, POWERPOINT, or WORD documents), email/calendar items, video files, and/or photos, but those skilled in the art will appreciate that the method of the present invention may be applied to other objects.


Referring to FIG. 1a, a user is enabled to synchronize one or more folders on any synchronization client to the synchronization server and other synchronization clients (step 105). All folders, across a plurality of synchronization clients that a user has backed up or synchronized to the synchronization server, are identified, as well as any folders that the user shares with other users (step 110). Each of the synchronization clients stores metadata with information on all folders shared with or by the user and all folders that the user has backed up or synced to the synchronization server (including the contents of the folder). The synchronization client on the client device uses this metadata to generate the virtual drive and the user interface.


A virtual drive is displayed on the user's local client device with the identified folders (step 115). The virtual drive appears as a separate disk drive on the user's local client device. The virtual drive includes all of the user's synced folders, regardless of whether a folder resides on the local client or only on a remote client. A user is enabled to access and edit any item within any folder displayed in the virtual drive, including folders that do not reside on the local client (step 120). In one embodiment, when a user double clicks on a file or item in a remote folder in the virtual drive, the server downloads its copy of the file/item to the local synchronization software client (i.e., the client currently being used by the user). The user can then edit the file/item as desired. In one embodiment, when a user double clicks on a local folder, the user is taken to the folder in the local file system view. In another embodiment, the server downloads its copy of the item/file in the local computer.


In response to detecting a change in a folder in the virtual drive, the folder is updated on the synchronization server (step 125). All remote clients of the user in the synchronization system are identified, as well as all remote synchronization clients, if any, of other users whom have access to the changed folder (step 130). In one embodiment, all synchronization clients that have an interest in updates to the folder “register” for notices of changes to the folder. The identified clients are notified of the change to the folder (step 135). In response to the change being a change to content within the folder, the content of the folder is automatically updated on any identified remote clients that have a corresponding folder. In one embodiment, the synchronization server first sends metadata to all the identified clients, notifying them of the change. The synchronization clients that have their own copy of the changed folder will then request the applicable file data from the server and the server will download the requested file data to the requesting synchronization clients.



FIGS. 1c-1d illustrate a further embodiment of the invention. In this embodiment, a user is enabled to create a collection that comprises items across a plurality of synchronization clients that share one or more specified attributes, regardless of the folder(s) in which the items reside (step 140). In certain embodiments, the collections and items within collections are not limited to files organized within folders on a file system, but are arbitrary objects existing within an arbitrary organizational scheme within an arbitrary data set.


The collection is displayed in the virtual drive (step 145). The collection may be displayed in the virtual drive as a folder, as a file, or as an object (e.g., a node). A user is enabled to access and edit items within the collection (step 150). In response to a user editing an item within a collection, a folder is identified in which the item resides (step 155). The folder is updated on the synchronization server with the edit to the item (step 160). All remote clients of the user in the synchronization system and all remote synchronization clients, if any, of other users whom have access to the changed folder are identified (step 165). The identified clients are notified of the change to the folder (step 170). In response to the change being a change to content within the folder, the content of the folder is automatically updated on any identified remote clients that have a corresponding folder. In the case where the items in the collection reside across an alternate organizational scheme (other than a file or folder system), the identified clients are notified of changes to any item. In response to the change being a change to content within the original physical or logical location, the content of the item is automatically updated on any identified remote clients that have a corresponding representation of the item.


The virtual drive may be organized by client device or may be client device-independent. A user may be able to perform share and synchronization management functions via the virtual drive. For example, a user may be able to right click on an object in the virtual drive to take a specific share action (e.g., share an object with another user or change the permission settings for another user with respect to the object) or alter the synchronization settings for the folder.



FIG. 2 illustrates an exemplary synchronization system 200 according to one embodiment. As a person skilled in the art would understand, the synchronization system 200 may be constructed in any number of ways within the scope of the present invention. The methods of FIGS. 1a-1d may be implemented in other systems, and the invention is not limited to system 200.


Synchronization system 200 includes a synchronization server (i.e., internet/network) 220, which provides synchronization and back up services to a plurality of end users. For example, all synchronized objects between a user's client devices and between users are stored on server 220 and are accessible from any client device having access to the server 220. Synchronization server 220 is representative of the server-side of a synchronization system and, in a large synchronization system, is likely a plurality of synchronization servers networked together. A person skilled in the art would understand that the synchronization system 200 may have any number of client devices, including one or more desktops, laptops, and mobile devices.


When a synchronization software client in the synchronization system detects a change to a local object, it notifies the synchronization server 220 of the change, and synchronization server 220 then modifies the corresponding object (and/or metadata related to the corresponding object) on the server as applicable. Server 220 notifies the user's other synchronization clients of the change, as well as any clients of other users with access to the changed object. If the content of the object has changed and a synchronization software client has a corresponding copy of the changed object, the synchronization software client requests the applicable content data from synchronizations sever 220.


Within client device 230 is local synchronization client software 240, which functions to synchronize client device 230 with the synchronization server 220. The local synchronization software 240 has a metadata manager 242 for receiving and sending change notices to and from synchronizations server 220. The metadata manager stores metadata about objects the user has synchronized or backed up to server 220 in the local sync database 245. Metadata for objects other users have shared with the user is also stored in the local sync database 245.


The local synchronization client software 240 includes a file data manager 243 for monitoring synchronized files (via operating system 255) on physical disk drive 260. Physical disk drive 260 stores the user's local files. When a user accesses a remote file via the virtual drive, a copy of such file is temporarily stored on a local physical disk drive 260. The file data manager 243 informs the metadata manager 242 if it detects a change to a synchronized object in physical disk drive 260. The metadata manager 242 then updates the applicable metadata in local sync database 245 and notifies server 220 of the change.


The local synchronization software 240 is operatively coupled to a file system abstraction module 250, within operating system 255. The operating system 255 is connected to one or more disk drives 260. The operating system 255 is also connected to a user interface 270 (e.g., MAC FINDER or WINDOWS EXPLORER) which displays the physical drive user interface 280 and the virtual drive user interface 290. The file system abstraction module 250 functions to process and normalize the metadata related to the synchronized objects so that the file system user interface module 270 is able to display the virtual drive 290.


The methods described with respect to FIGS. 1a-1d are embodied in software and performed by a computer system executing the software. A person skilled in the art would understand that a computer system has a memory or other physical, computer-readable storage medium for storing software instructions and one or more processors for executing the software instructions.



FIGS. 3-4
b illustrate a method for enabling a user to change a remote folder via the virtual drive according to one embodiment of the invention. The same method may be applied if a user changes a local folder. In FIG. 3, a synchronization server 320 communicates, via Internet/network 310, to four client devices, Client Device A, Client Device B, Client Device C, and Client Device D. Client Devices A-C belong to a first user (e.g., Elisabeth) and Client Device D belongs to a second user (e.g., Andrew). A person skilled in the art would understand that there may be more or less client devices connected to the cloud 310 within the scope of the present invention.


Each client device has a local synchronization client 340a-340d and a file system 350a-350d. Each file system stores one or more of Folders #1-9 on the local client device. For example, Client Device A has Folders #1-3 in its file system 350a, Client Device B has Folders #1, 3, and 5-7 in its file system 350b, Client Device C has Folders #3, 5, and 7 in its file system 350c, and Client Device D has Folders #8-9 in its file system 350d. In addition, the first user, Elisabeth, has shared Folder 5 with the second user, Andrew, which appears on the local synchronization client 340d of Client Device D. Database 360 is connected to synchronization server 320 and has all folders (i.e., Folders #1-9) of all synchronized client devices stored on it.


In FIGS. 4a-4b, the virtual drives on Elisabeth's Client Devices (A, B, C) display Folders #1-7. The virtual drive on Andrew's Client Device D displays Folders #5 (shared), 8, and 9 (step 405). Elisabeth double clicks on a file in Folder #5 via the virtual drive on Client Device A, and Client Device A requests a copy of the file from the synchronization server 320 (step 410). The synchronization server 320 sends Client Device A a copy of the selected file (step 420). Elisabeth changes the file on Client Device A (step 425). The local synchronization client 340a on Client Device A detects a change and notifies the synchronization server 320. The local synchronization client 340a also updates the local sync metadata on Client Device A to reflect change (step 430). Examples of metadata include file attributes (e.g., permissions, time stamp of last change, file type, file name). The synchronization server 320 obtains the relevant file data from Client Device A and updates its copy of Folder #5 in the Synchronization Database 360 (step 435).


The synchronization server 320 identifies Client Devices B and C as belonging to Elisabeth. Synchronization server 320 identifies Client Device D as belonging to Andrew, with whom Elisabeth has shared Folder #5 (step 440). Synchronization server 320 notifies Client Devices B, C, and D of the change to Folder #5 (step 450). The local synchronization clients 340b, 340c, 340d on Client Devices B, C, and D update the metadata for the virtual drive and synchronization user interface (step 460). The local synchronization clients 340b, 340c, 340d on Client Devices B and C each realizes that they have a Folder #5 and requests relevant file data from synchronization server 320 (step 470). The synchronization server 320 sends file data to Client Devices B and C (step 480). Client Devices B and C update corresponding Folder #5 on Client Devices B and C (step 490).



FIGS. 5-6 illustrate screenshots of an exemplary user interface that enables a user to easily synchronize a folder to the synchronization system. A person skilled in the art would understand that the present invention may be embodied on other user interfaces having more or less functionality within the scope of the present invention. As such, FIGS. 5-6 are intended to be illustrative and not limiting in any way.


In FIG. 5, an exemplary user interface 500 for a synchronization system that functions with the virtual drive is provided. The user interface has a content view 505, a sharing view 510, an activity view 515, and a search button 520. The content view 505 has three tabs, a My Cloud tab 525, a Shared folders tab 530, and a Web link tab 535. A more detailed description of an exemplary user interface 500 may be found in U.S. patent application Ser. No. 13/571,564, filed on Aug. 10, 2012, by Andrew Garcia, et al. entitled “System, Method, and Computer Program for Enabling a User to Synchronize, Manage, and Share Folders Across a Plurality of Client Devices and a Synchronization Server,” which is incorporated by reference in its entirety.



FIG. 5 also illustrates a virtual drive on an exemplary file system user interface, such as the MAC FINDER on a MACINTOSH-based computer. The virtual drive may also be embodied on a WINDOWS-based computer, such as using WINDOWS EXPLORER. Folders 540 include folders, across the synchronization software clients of the user's client devices, that (i) the user has synchronized or backed up in the synchronization system, (ii) have been shared with the user, or (iii) the user has shared with other users. Any file in folders 540 may be accessed through the virtual drive 545, including files in folders located only on a remote synchronization software client or synchronization server 220. That means that the folders 540 may be viewed as if they resided on the hard drive of the local client device and the user may add, edit, delete, and move files within the folders 540, which would result in the files being added, edited, deleted, or moved in corresponding folders on remote synchronization software clients and the synchronization server. Not only are all of the user's folders, which have been synchronized, accessible through the virtual drive, but all of the folders 550 shared with the user by other users.



FIG. 6 illustrates how a file may be opened via the virtual drive 545. The user can choose a file from any folder 540 in the virtual drive 545. The user may choose whether to open the original or a copy 605. After the user modifies and saves the document, any changes are uploaded to the synchronization server 220 and a copy of the changed metadata is pushed to all synchronization software clients that have registered for notices of changes to the folder.


As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the above disclosure of the present invention is intended to be illustrative and not limiting of the invention.

Claims
  • 1. A method, comprising: providing, on a local client device associated with a first user, a display of a virtual drive that appears as a local storage drive of the local client device;providing, within the display of the virtual drive, a plurality of items synchronized with a content management system, the plurality of items comprising: locally stored items that are stored on the local storage drive of the local client device; andremotely stored items that are stored in a remote storage location that does not reside on the local client device, wherein the locally stored items and remotely stored items are presented in the virtual drive without regard to a storage location of the locally stored items and the remotely stored items;in response to detecting a user interaction with an item from the plurality of items within the display of the virtual drive, providing an option to set permission attributes associated with the item; andin response to receiving an indication of a user selection of a permission attribute corresponding to the item based on the first user interacting with the option to set permission attributes, updating a remote client device associated with a second user to reflect the selected permission attribute of the item.
  • 2. The method of claim 1, wherein there is no visual distinction between the locally stored items and the remotely stored items within the display of the virtual drive.
  • 3. The method of claim 1, wherein the permission attribute corresponding to the item defines a sharing permission for the item.
  • 4. The method of claim 1, further comprising, based on a user interaction with a remotely stored item, adding the remotely stored item to the locally stored items by maintaining a local copy of the remotely stored item on the local storage drive of the local client device.
  • 5. The method of claim 1, wherein the permission attribute corresponding to the item defines an editing permission for the item.
  • 6. The method of claim 1, wherein the remote storage location is a synchronization server of a synchronization system.
  • 7. The method of claim 1, further comprising adding a shared item to the virtual drive based on a sharing user sharing the shared item with the first user associated with the local client device.
  • 8. The method of claim 7, further comprising storing the shared item on the local storage drive of the local client device as one of the locally stored items based on the first user associated with the local client device interacting with the shared item.
  • 9. The method of claim 8, further comprising: detecting a modification of the shared item; andproviding a notification of the modification to a synchronization system, wherein the notification causes the synchronization system to update a copy of the shared item on one or more of a synchronization server or a client device associated with the sharing user.
  • 10. A system, comprising: at least one processor; anda non-transitory computer readable medium comprising instructions that, when executed by the at least one processor, cause the system to:provide, on a local client device associated with a first user, a display of a virtual drive that appears as a local storage drive of the local client device;provide, within the display of the virtual drive, a plurality of items synchronized with a content management system, the plurality of items comprising: locally stored items that are stored on the local storage drive of the local client device; andremotely stored items that are stored in a remote storage location that does not reside on the local client device, wherein the locally stored items and remotely stored items are presented in the virtual drive without regard to a storage location of the locally stored items and the remotely stored items;in response to detecting a user interaction with an item from the plurality of items within the display of the virtual drive, provide an option to set permission attributes associated with the item; andin response to receiving an indication of a user selection of a permission attribute corresponding to the item based on the first user interacting with the option to set permission attributes, update a remote client device associated with a second user to reflect the selected permission attribute of the item.
  • 11. The system of claim 10, wherein there is no visual distinction between the locally stored items and the remotely stored items within the display of the virtual drive.
  • 12. The system of claim 10, wherein the permission attribute corresponding to the item defines a sharing permission for the item.
  • 13. The system of claim 10, further comprising instructions that, when executed by the at least one processor, cause the system to, based on a user interaction with a remotely stored item, add the remotely stored item to the locally stored items within the virtual drive by maintaining a local copy of the remotely stored item on the local storage drive of the local client device.
  • 14. The system of claim 10, further comprising instructions that, when executed by the at least one processor, cause the system to add a shared item to the virtual drive based on a sharing user sharing the shared item with the first user associated with the local client device.
  • 15. The system of claim 14, further comprising instructions that, when executed by the at least one processor, cause the system to store the shared item on the local storage drive of the local client device as one of the locally stored items based on the first user associated with the local client device interacting with the shared item.
  • 16. The system of claim 10, wherein the permission attribute corresponding to the item defines an editing permission for the item.
  • 17. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, causes a computer device to: provide, on a local client device associated with a first user, a display of a virtual drive that appears as a local storage drive of the local client device;provide, within the display of the virtual drive, a plurality of items synchronized with a content management system, the plurality of items comprising: locally stored items that are stored on the local storage drive of the local client device; andremotely stored items that are stored in a remote storage location that does not reside on the local client device, wherein the locally stored items and remotely stored items are presented in the virtual drive without regard to a storage location of the locally stored items and the remotely stored items;in response to detecting a user interaction with an item from the plurality of items within the display of the virtual drive, provide an option to set permission attributes associated with the item; andin response to receiving an indication of a user selection of a permission attribute corresponding to the item based on the first user interacting with the option to set permission attributes, update a remote client device associated with a second user to reflect the selected permission attribute of the item.
  • 18. The non-transitory computer-readable medium of claim 17, wherein the permission attribute corresponding to the item defines a sharing permission for the item.
  • 19. The non-transitory computer-readable medium of claim 17, wherein the permission attribute corresponding to the item defines an editing permission for the item.
  • 20. The non-transitory computer-readable medium of claim 17, wherein there is no visual distinction between the locally stored items and the remotely stored items within the display of the virtual drive.
CROSS REFERENCE TO OTHER APPLICATIONS

This present application is a continuation of U.S. patent application Ser. No. 14/873,004, filed Oct. 1, 2015, which is a continuation of U.S. patent application Ser. No. 13/571,512, filed Aug. 10, 2012. Each of the aforementioned applications are hereby incorporated by reference in their entirety.

US Referenced Citations (196)
Number Name Date Kind
5165031 Pruul et al. Nov 1992 A
5862346 Kley et al. Jan 1999 A
6052735 Ulrich et al. Apr 2000 A
6125369 Wu et al. Sep 2000 A
6256634 Moshaiov et al. Jul 2001 B1
6260040 Kauffman Jul 2001 B1
6272545 Flanagin et al. Aug 2001 B1
6348932 Nishikawa et al. Feb 2002 B1
6407750 Gioscia et al. Jun 2002 B1
6496979 Chen et al. Dec 2002 B1
6636873 Carini et al. Oct 2003 B1
6636888 Bookspan et al. Oct 2003 B1
6725281 Zintel et al. Apr 2004 B1
6795688 Plasson et al. Sep 2004 B1
6904185 Wilkins et al. Jun 2005 B1
6938076 Meyer et al. Aug 2005 B2
7039723 Hu et al. May 2006 B2
7103357 Kirani et al. Sep 2006 B2
7139555 Apfel Nov 2006 B2
7143194 Curley et al. Nov 2006 B1
7162454 Donner et al. Jan 2007 B1
7228352 Yaguchi et al. Jun 2007 B1
7263712 Spencer Aug 2007 B2
7317699 Godfrey et al. Jan 2008 B2
7319536 Wilkins et al. Jan 2008 B1
7321919 Jacobs et al. Jan 2008 B2
7369161 Easwar et al. May 2008 B2
7372485 Bodnar et al. May 2008 B1
7421458 Taylor et al. Sep 2008 B1
7441180 Kaczmarek et al. Oct 2008 B1
7502795 Svendsen et al. Mar 2009 B1
7576752 Benson et al. Aug 2009 B1
7644124 Porter Jan 2010 B1
7680067 Prasad et al. Mar 2010 B2
7707500 Martinez Apr 2010 B2
7747596 Bigioi et al. Jun 2010 B2
7773106 Serdy, Jr. et al. Aug 2010 B2
7774326 Arrouye et al. Aug 2010 B2
7809682 Paterson et al. Oct 2010 B2
7873353 Kloba et al. Jan 2011 B2
7885925 Strong et al. Feb 2011 B1
7917628 Hesselink et al. Mar 2011 B2
7930270 Tsang Apr 2011 B2
7962137 Coppinger et al. Jun 2011 B2
7962622 Friend et al. Jun 2011 B2
8019900 Sekar et al. Sep 2011 B1
8230026 Gilhuly et al. Jul 2012 B2
8321374 Holt et al. Nov 2012 B2
8341345 Tulskie et al. Dec 2012 B2
8370298 Strong et al. Feb 2013 B2
8600934 Strong et al. Dec 2013 B2
8612439 Prahlad et al. Dec 2013 B2
8620861 Uhrhane Dec 2013 B1
8650498 Mihovilovic Feb 2014 B1
8965847 Chang Feb 2015 B1
9037540 Strong et al. May 2015 B2
9131054 Vendrow et al. Sep 2015 B2
9501762 Babenko et al. Nov 2016 B2
9817878 Newhouse Nov 2017 B2
10057318 Rashid et al. Aug 2018 B1
10320904 Strong et al. Jun 2019 B2
20020013852 Janik Jan 2002 A1
20020044159 Kuroiwa et al. Apr 2002 A1
20020059604 Papagan et al. May 2002 A1
20020065848 Walker et al. May 2002 A1
20020066050 Lerman et al. May 2002 A1
20020099772 Deshpande et al. Jul 2002 A1
20020129096 Mansour et al. Sep 2002 A1
20020184264 Berg et al. Dec 2002 A1
20030004952 Nixon et al. Jan 2003 A1
20030014478 Noble Jan 2003 A1
20030037114 Nishio et al. Feb 2003 A1
20030041094 Lara Feb 2003 A1
20030055825 Chen et al. Mar 2003 A1
20030058277 Bowman-Amuah Mar 2003 A1
20030074418 Coker Apr 2003 A1
20030097361 Huang et al. May 2003 A1
20030131098 Huntington et al. Jul 2003 A1
20030159136 Huang et al. Aug 2003 A1
20030172127 Northrup et al. Sep 2003 A1
20030218633 Mikhail et al. Nov 2003 A1
20040024979 Kaminsky et al. Feb 2004 A1
20040044732 Fushiki et al. Mar 2004 A1
20040054736 Daniell et al. Mar 2004 A1
20040068524 Aboulhosn et al. Apr 2004 A1
20040088420 Allen et al. May 2004 A1
20040107236 Nakagawa et al. Jun 2004 A1
20040123048 Mullins et al. Jun 2004 A1
20040126750 Theilmann et al. Jul 2004 A1
20040148207 Smith et al. Jul 2004 A1
20040148375 Levett et al. Jul 2004 A1
20040172423 Kaasten et al. Sep 2004 A1
20040267905 McDonough et al. Dec 2004 A1
20040268364 Faraj Dec 2004 A1
20050015441 Attwood et al. Jan 2005 A1
20050038863 Onyon et al. Feb 2005 A1
20050044164 O'Farrell et al. Feb 2005 A1
20050044165 O'Farrell et al. Feb 2005 A1
20050091595 Shappell Apr 2005 A1
20050149481 Hesselink et al. Jul 2005 A1
20050149508 Deshpande Jul 2005 A1
20050165869 Huang et al. Jul 2005 A1
20050198015 Sezan et al. Sep 2005 A1
20050208803 Rohatgi et al. Sep 2005 A1
20050223061 Auerbach et al. Oct 2005 A1
20050246373 Faulkner et al. Nov 2005 A1
20050246374 Blinn et al. Nov 2005 A1
20050278458 Berger et al. Dec 2005 A1
20060018444 Pantana et al. Jan 2006 A1
20060052091 Onyon et al. Mar 2006 A1
20060085429 Wener et al. Apr 2006 A1
20060101053 Proctor May 2006 A1
20060101064 Strong et al. May 2006 A1
20060123010 Landry et al. Jun 2006 A1
20060156239 Jobs et al. Jul 2006 A1
20060168000 Bodlaender Jul 2006 A1
20060170669 Walker et al. Aug 2006 A1
20060184673 Liebman Aug 2006 A1
20060242206 Brezak et al. Oct 2006 A1
20060259957 Tam Nov 2006 A1
20070005581 Arrouye et al. Jan 2007 A1
20070005707 Teodosiu et al. Jan 2007 A1
20070016695 Rabbers et al. Jan 2007 A1
20070043830 Housenbold et al. Feb 2007 A1
20070078938 Xiao et al. Apr 2007 A1
20070156434 Martin et al. Jul 2007 A1
20070179989 Maes Aug 2007 A1
20070180075 Chasman et al. Aug 2007 A1
20070180084 Mohanty Aug 2007 A1
20070198473 Carrier Aug 2007 A1
20070209005 Shaver et al. Sep 2007 A1
20070239898 Friend et al. Oct 2007 A1
20070250645 Meadows et al. Oct 2007 A1
20070276836 Chatterjee et al. Nov 2007 A1
20070288614 May et al. Dec 2007 A1
20070294366 Ozzie Dec 2007 A1
20080109448 Aboel-Nil et al. May 2008 A1
20080126936 Williams May 2008 A1
20080140732 Wilson Jun 2008 A1
20080168185 Robbin et al. Jul 2008 A1
20080184125 Suleiman et al. Jul 2008 A1
20080189627 Nikitin et al. Aug 2008 A1
20080195729 Chand et al. Aug 2008 A1
20080195739 Ozzie Aug 2008 A1
20080208870 Tsang Aug 2008 A1
20080208998 Warren et al. Aug 2008 A1
20080250083 Kovacs et al. Oct 2008 A1
20080307504 Cisler Dec 2008 A1
20090024931 Bae Jan 2009 A1
20090064284 Poston et al. Mar 2009 A1
20090094252 Wong et al. Apr 2009 A1
20090183060 Heller et al. Jul 2009 A1
20090187609 Barton et al. Jul 2009 A1
20090300020 Chen et al. Dec 2009 A1
20090327900 Noll Dec 2009 A1
20100063670 Brzezinski et al. Mar 2010 A1
20100115614 Barile May 2010 A1
20100205196 Schreiber Aug 2010 A1
20100241980 Sosnosky et al. Sep 2010 A1
20100332682 Sharp et al. Dec 2010 A1
20110010332 Vasudevan Jan 2011 A1
20110106880 Strong et al. May 2011 A1
20120016915 Choi Jan 2012 A1
20120084355 Locker Apr 2012 A1
20120096389 Flam et al. Apr 2012 A1
20120197862 Woytowitz et al. Aug 2012 A1
20130007207 Dietrich et al. Jan 2013 A1
20130066975 Kantor Mar 2013 A1
20130067594 Kantor et al. Mar 2013 A1
20130091550 Joyce Apr 2013 A1
20130110903 Myerscough et al. May 2013 A1
20130117423 Gupta et al. May 2013 A1
20130198868 Georgiev Aug 2013 A1
20130205251 Cisler et al. Aug 2013 A1
20130212486 Joshi et al. Aug 2013 A1
20130232187 Workman Sep 2013 A1
20130275509 Micucci et al. Oct 2013 A1
20130282830 Besen Oct 2013 A1
20130305039 Gauda Nov 2013 A1
20130311598 Arrouye Nov 2013 A1
20130311986 Arrouye Nov 2013 A1
20130318582 McCann Nov 2013 A1
20140095457 Quan et al. Apr 2014 A1
20140181016 Whitehead et al. Jun 2014 A1
20150213101 Strong et al. Jul 2015 A1
20150264115 Reilly et al. Sep 2015 A1
20160026704 Strong et al. Jan 2016 A1
20160028809 Strong et al. Jan 2016 A1
20160028810 Strong et al. Jan 2016 A1
20160028811 Rashid et al. Jan 2016 A1
20160028812 Strong et al. Jan 2016 A1
20160028813 Strong et al. Jan 2016 A1
20160028814 Strong et al. Jan 2016 A1
20160028815 Strong et al. Jan 2016 A1
20160028852 Strong et al. Jan 2016 A1
20160055171 Araki et al. Feb 2016 A1
Non-Patent Literature Citations (62)
Entry
U.S. Appl. No. 14/873,004, Nov. 23, 2018, Office Action.
Jmans25, Map/Mount Dropbox as a network drive, Oct. 14, 2011, Youtube, p. 1.
Ed Rhee, How to map a drive letter to Google Drive in Windows, May 3, 2012, p. 1-2.
U.S. Appl. No. 13/571,512, Feb. 24, 2014, Office Action.
U.S. Appl. No. 13/571,512, Jun. 13, 2014, Office Action.
U.S. Appl. No. 13/571,512, Sep. 23, 2014, Office Action.
U.S. Appl. No. 13/571,512, Apr. 23, 2015, Office Action.
U.S. Appl. No. 13/571,512, May 19, 2016, Office Action.
U.S. Appl. No. 13/571,512, Oct. 20, 2016, Office Action.
U.S. Appl. No. 13/571,512, Oct. 26, 2017, Office Action.
U.S. Appl. No. 13/571,512, Apr. 6, 2018, Notice of Allowance.
U.S. Appl. No. 14/873,004, Oct. 26, 2017, Office Action.
U.S. Appl. No. 14/873,004, Feb. 9, 2018, Office Action.
U.S. Appl. No. 61/622,950 titled, “System and Method for Data Object Synchronization,” filed Apr. 11, 2012.
U.S. Appl. No. 14/873,004, Aug. 10, 2018, Office Action.
U.S. Appl. No. 14/873,004, Jul. 17, 2017, Office Action.
Final Office Action from U.S. Appl. No. 14/873,004, dated Feb. 12, 2020, 18 pages.
Advisory Action from U.S. Appl. No. 14/873,004, dated May 19, 2020, 3 pages.
Deshpande M., et al., “Item-Based Top-N. Recommendation Algorithms,” ACM Transactions on Information Systems, vol. 22, No. 1, Jan. 2004, pp. 143-177.
Non-Final Office Action from U.S. Appl. No. 14/873,187, dated Jan. 10, 2020, 17 pages.
Notice of Allowance from U.S. Appl. No. 14/873,004, dated Jun. 12, 2020, 11 pages.
Notice of Allowance from U.S. Appl. No. 14/873,187, dated Jun. 24, 2020, 13 pages.
Notice of Allowance for U.S. Appl. No. 12/157,772 dated Oct. 6, 2010, 15 pages.
Notice of Allowance for U.S. Appl. No. 12/928,998 dated Oct. 9, 2012, 13 pages.
Notice of Allowance for U.S. Appl. No. 13/757,024 dated Jul. 25, 2013, 11 pages.
Notice of Allowance for U.S. Appl. No. 13/757,024 dated Oct. 30, 2013, 7 pages.
Notice of Allowance for U.S. Appl. No. 14/075,598 dated Jan. 14, 2015, 10 pages.
Notice of Allowance for U.S. Appl. No. 14/683,341 dated Jun. 25, 2018, 10 pages.
Notice of Allowance for U.S. Appl. No. 14/873,199 dated Jan. 25, 2019, 16 pages.
Notice of Allowance for U.S. Appl. No. 14/873,197 dated Aug. 29, 2019, 14 pages.
Office Action for U.S. Appl. No. 14/873,187 dated Apr. 24, 2019, 21 pages.
Office Action for U.S. Appl. No. 11/269,498 dated Aug. 22, 2007, 18 pages.
Office Action for U.S. Appl. No. 11/269,498 dated Mar. 25, 2008, 17 pages.
Office Action for U.S. Appl. No. 11/269,498 dated Mar. 7, 2007, 14 pages.
Office Action forU.S. Appl. No. 12/928,998 dated Apr. 22, 2011, 26 pages.
Office Action for U.S. Appl. No. 12/928,998 dated Nov. 23, 2011, 24 pages.
Office Action for U.S. Appl. No. 14/683,341 dated Nov. 16, 2017, 14 pages.
Office Action for U.S. Appl. No. 14/872,004 dated Jan. 18, 2018, 8 pages.
Office Action for U.S. Appl. No. 14/872,004 dated Mar. 28, 2019, 19 pages.
Office Action for U.S. Appl. No. 14/872,004 dated Sep. 6, 2018, 11 pages.
Office Action for U.S. Appl. No. 14/872,019 dated Aug. 29, 2018, 13 pages.
Office Action for U.S. Appl. No. 14/872,019 dated Feb. 26, 2019, 15 pages.
Office Action for U.S. Appl. No. 14/872,019 dated Nov. 16, 2017, 14 pages.
Office Action for U.S. Appl. No. 14/872,943 dated Jul. 11, 2018, 12 pages.
Office Action for U.S. Appl. No. 14/872,943 dated Oct. 4, 2017, 13 pages.
Office Action for U.S. Appl. No. 14/872,943 dated Dec. 19, 2018, 19 pages.
Office Action for U.S. Appl. No. 14/873,186 dated Mar. 22, 2018, 24 pages.
Office Action for U.S. Appl. No. 14/873,186 dated Dec. 13, 2018, 33 pages.
Office Action for U.S. Appl. No. 14/873,187 dated Apr. 17, 2018, 15 pages.
Office Action for U.S. Appl. No. 14/873,187 dated Dec. 10, 2018, 18 pages.
Office Action for U.S. Appl. No. 14/873,195 dated Apr. 19, 2018, 14 pages.
Office Action for U.S. Appl. No. 14/873,197 dated Jul. 11, 2018, 13 pages.
Office Action for U.S. Appl. No. 14/873,197 dated Jun. 3, 2019, 20 pages.
Office Action for U.S. Appl. No. 14/873,197 dated Oct. 5, 2017, 13 pages.
Office Action for U.S. Appl. No. 14/873,197 dated Dec. 14, 2018, 16 pages.
Office Action for U.S. Appl. No. 14/873,199 dated Jun. 1, 2018, 16 pages.
Office Action for U.S. Appl. No. 14/872,943 dated Jun. 17, 2019, 19 pages.
Srinet K., et al., “10-605—HW 5—Distributed SGD for Matrix Factorization on Spark,” Carnegie Mellon University, Pittsburgh, PA, Nov. 12, 2015, pp. 1-11.
Non-Final Office Action from U.S. Appl. No. 15/964,267, dated Jul. 27, 2020, 21 pages.
Non-Final Office Action from U.S. Appl. No. 16/397,945, dated Jul. 23, 2020, 18 pages.
Notice of Allowance from U.S. Appl. No. 14/873,004, dated Aug. 12, 2020, 6 pages.
Notice of Allowance from U.S. Appl. No. 14/873,187, dated Jul. 30, 2020, 8 pages.
Related Publications (1)
Number Date Country
20180278684 A1 Sep 2018 US
Continuations (2)
Number Date Country
Parent 14873004 Oct 2015 US
Child 15992342 US
Parent 13571512 Aug 2012 US
Child 14873004 US