Patent Grant
9141483
1. Field of the Invention
This invention relates generally to synchronization/back-up server systems, and more, specifically, to a method for multi-tier synchronization.
2. Description of the Background Art
Real-time synchronization systems, including client-server solutions such as MICROSOFT EXCHANGE (email/PIM) and SHARPCAST's first photo synchronization system, only synchronize data between a client and a server, where the client communicates with the server via the Internet. The advantage of client/server synchronization over the Internet is that the client device can access the server anytime it has an Internet connection. Also, by storing files on the server, the files can be easily recovered should the files on the client device be lost. There are at least two disadvantages with client/server synchronization over the Internet. Transferring files over the Internet is slower than transferring files over a local area network or an Intranet. Also, if a master server stores all synchronized files from many client devices, the master server has to have very large storage capabilities, which can be quite expensive.
An example of master server-client synchronization is described in U.S. patent application Ser. No. 11/269,498 titled “Method and Apparatus for a File Sharing and Synchronization System,” and filed on Nov. 8, 2005 with first-named inventor Jack B. Strong, the contents of which are incorporated by reference as if fully disclosed herein.
Known multi-tier data management systems, such as web proxies, content delivery networks, or file replication technologies, such as “rsync,” distribute file storage over the network. This means that client devices can retrieve files from intermediate sources instead of downloading then from a master server. Such intermediate sources may be connected to client devices over a local area network, where file transfers typically occur at a faster rate that transfers over the Internet. A disadvantage with known multi-tier data management systems is that data is not synchronized in real-time, which comprises user experience.
It would be desirable to have a synchronization system that was able to take advantage of the best of both multi-tier data management and client-server synchronization.
The present invention provides a system and method for multi-tiered data synchronization. Data is synchronized between a master synchronization server, one or more proxy synchronization servers, and client devices.
Client devices establish synchronization sessions with either a proxy synchronization server or a master synchronization server, depending on which server provides the “best” available connection to that client device. “Best” means fastest, cheapest, or more secure, as per the client device's requirements. In one embodiment, client devices that can communicate with a proxy synchronization server over a local area network or intranet establish synchronization sessions with the proxy synchronization server instead of the master synchronization server.
Each proxy synchronization server synchronizes data with client devices “connected” to it (i.e., client devices that have established a synchronization session with the proxy synchronization server). The master synchronization server synchronizes data with client devices connected to it (i.e., client devices that have established a synchronization session with the master synchronization server via the Internet). Each proxy synchronization server synchronizes data with the master synchronization server.
In the preferred embodiment, metadata associated with synchronized files or data objects is synchronized throughout the system in real-time. Files may be synchronized in real-time or at a delayed time.
The present invention provides a system and method for multi-tiered data synchronization. Data is synchronized between a “master” synchronization server, one or more “proxy” synchronization servers, and client devices.
Master synchronization servers may, for example, be servers that are hosted in a data center and that are accessible via the Internet. Proxy synchronization servers may, for example, be included with Network Attached Storage (NAS) devices found in homes and offices, in media center or set top box systems found in home networks, in broadband routers found in home networks, and in dedicated appliances found in offices and home offices. Types of client devices include personal computers, mobile phones, PDAs, and other networked devices.
In the preferred embodiment, client devices that can communicate with a proxy synchronization server over a local area network or intranet (“local client devices”) establish synchronization sessions with the proxy synchronization server instead of the master synchronization server. Online client devices that are unable to communicate with the proxy synchronization server via a local area network or intranet (“remote client devices”) establish synchronization sessions with a master synchronization server.
Consider for example, client device 10 in
Referring again to
Metadata associated with synchronized files is synchronized throughout the system in real-time. The master synchronization server stores all metadata associated with synchronized files/data objects in the system. Each client device and proxy synchronization server stores all metadata relevant to such device. Copies of synchronized files/data objects may be transferred along with the metadata or may be retrieved “on demand.” The master server and the client devices may or may not store actual copies of synchronized files. However, in one embodiment, all files are backed up on to one or more of the proxy synchronization servers. In the preferred embodiment, files are synchronized in real-time between the proxy synchronization servers and interest client devices connected to it (i.e., client devices that have established a synchronization session with the proxy synchronization server). Similarly, in such embodiment, files are synchronized in real-time between the master synchronization server and interested client devices connected to it. Files may be synchronized between the master synchronization server and each proxy synchronization server either in real time or at a delayed time. In one embodiment, two devices (where client devices or a server) that have established a synchronization session between themselves maintain a dedicated connection to each other throughout the synchronization session, thereby enabling data (e.g., metadata, files, data objects) to be synchronized in real time.
The multi-tiered synchronization method of the present invention can be used to more effectively utilize network bandwidth than traditional client-server architectures. Multi-tier synchronization can be configured to utilize less bandwidth over the Internet during peak usage hours, when that connection may be in high demand by other applications. For example, a client device may synchronize a new file to a proxy synchronization server. This transfer may happen at a high bitrate, as it is likely over a local area network, or high speed intranet. The proxy synchronization server makes this file immediately available to other client devices connected to the proxy synchronization server. The file is backed up on the proxy synchronization server, and, thus, if the client device's hard disk fails, the file can be restored from the proxy. However, the proxy synchronization server need not synchronize the file to the master synchronization server immediately. It could defer syncing the file until the Internet connection (which is often slower and more contentious than the connection from the local client devices to the proxy synchronization server) until an idle period (e.g., the middle of the night). Alternately, the proxy synchronization server may sync files with the master synchronization server throughout the day, but only use a low percentage of Internet bandwidth while other applications require bandwidth, and a high percentage when the Internet connection is idle. Despite this variable bandwidth synchronization to the master synchronization server over the Internet, the proxy synchronization server is able to synchronize files at a high speed to client devices connected to the proxy synchronization server.
In the preferred embodiment, metadata is synchronized in real-time, even if files may are synchronized on a deferred schedule. Since metadata takes very little bandwidth to synchronize, metadata changes can be synchronized up from the proxy synchronization server to the master synchronization server in real time, providing all clients with up-to-date metadata. This can, for example, prevent clients from making conflicting changes to a file even if that file has not been synchronized to the master synchronization server (pending an idle period), since the file's revision information can be described in metadata.
In one embodiment, conflict resolution is employed hierarchically. A conflict resolution algorithm can be applied on the proxy synchronization server when conflicting changes are synced to it, or on the master synchronization server when receiving conflicting changes from any combination of proxies or directly connected clients.
File storage requirements on the master synchronization server may be minimized by relying on proxy synchronization servers to back up files. In one embodiment, the master synchronization server stores only metadata and no files. In an alternate embodiment, the master synchronization server stores only select files. For example, the proxy synchronization server could store all versions of a file, and the master synchronization server could store only the most recent version of a file. As another example, the master synchronization server could store only files having a specific tag or rating (music files rated with 5 stars). As yet another example, the master synchronization server could store only files of a certain media type (e.g., photo files, music files).
In one embodiment, client devices will first attempt to synchronize with a proxy synchronization server if that option is available. If a proxy synchronization server is not available for synchronization, then, in such embodiment, the client device will synchronize with a peer client device if a peer client device is available for synchronization. If neither a proxy synchronization server nor a peer client device is available for synchronization, then the client device will synchronize with the master synchronization server. Peer-to-peer synchronization is described in U.S. Patent Application titled “Opportunistic Peer-to-Peer Synchronization in a Synchronization System” filed on Mar. 24, 2009 and having inventors Kiren R. Sekar and Jack B. Strong, the contents of which are incorporated herein by reference as if fully disclosed herein.
Examples of files include photos, music files, word processing documents, spreadsheets, slide presentations, and video files.
The methods disclosed herein can be used to synchronize data objects, such as email messages, text messages, contact items, and calendar items, in the same way that files are synchronized.
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.
This application claims the benefit of U.S. Provisional Application No. 61/072,008 filed on Mar. 27, 2008 with inventors Kiren Sekar and Jack B. Strong and titled “System and Method for Multi-Tier Synchronization,” the contents of which are incorporated by reference as if fully disclosed herein
| Number | Name | Date | Kind |
|---|---|---|---|
| 5862346 | Kley et al. | Jan 1999 | A |
| 6348932 | Nishikawa et al. | Feb 2002 | B1 |
| 6407750 | Gioscia et al. | Jun 2002 | B1 |
| 6636873 | Carini et al. | Oct 2003 | B1 |
| 6636888 | Bookspan et al. | Oct 2003 | B1 |
| 6904185 | Wilkins et al. | Jun 2005 | B1 |
| 7039723 | Hu et al. | May 2006 | B2 |
| 7103357 | Kirani et al. | Sep 2006 | B2 |
| 7139555 | Apfel | Nov 2006 | 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 |
| 7441180 | Kaczmarek et al. | Oct 2008 | B1 |
| 7502795 | Svendsen et al. | Mar 2009 | B1 |
| 7576752 | Benson et al. | Aug 2009 | B1 |
| 7680067 | Prasad et al. | Mar 2010 | B2 |
| 7707500 | Martinez | Apr 2010 | B2 |
| 7747596 | Bigioi et al. | Jun 2010 | B2 |
| 7774326 | Arrouye et al. | Aug 2010 | B2 |
| 7809682 | Paterson et al. | Oct 2010 | B2 |
| 7930270 | Tsang | Apr 2011 | B2 |
| 8321374 | Holt et al. | Nov 2012 | 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 |
| 20030004952 | Nixon et al. | Jan 2003 | A1 |
| 20030014478 | Noble | Jan 2003 | A1 |
| 20030131098 | Huntington et al. | Jul 2003 | A1 |
| 20030159136 | Huang et al. | Aug 2003 | A1 |
| 20030218633 | Mikhail et al. | Nov 2003 | A1 |
| 20040024979 | Kaminsky et al. | Feb 2004 | A1 |
| 20040044732 | Fushiki et al. | Mar 2004 | A1 |
| 20040088420 | Allen et al. | May 2004 | A1 |
| 20040148207 | Smith et al. | Jul 2004 | A1 |
| 20040148375 | Levett et al. | Jul 2004 | A1 |
| 20050044164 | O'Farrell et al. | Feb 2005 | A1 |
| 20050165869 | Huang et al. | Jul 2005 | A1 |
| 20060052091 | Onyon et al. | Mar 2006 | A1 |
| 20060156239 | Jobs et al. | Jul 2006 | A1 |
| 20060242206 | Brezak et al. | Oct 2006 | A1 |
| 20070005581 | Arrouye et al. | Jan 2007 | A1 |
| 20070005707 | Teodosiu et al. | Jan 2007 | A1 |
| 20070043830 | Housenbold et al. | Feb 2007 | A1 |
| 20070156434 | Martin et al. | Jul 2007 | A1 |
| 20070179989 | Maes | Aug 2007 | A1 |
| 20070180075 | Chasman et al. | Aug 2007 | A1 |
| 20070209005 | Shaver et al. | Sep 2007 | A1 |
| 20070250645 | Meadows et al. | Oct 2007 | A1 |
| 20070276836 | Chatterjee et al. | Nov 2007 | A1 |
| 20080109448 | Aboel-Nil et al. | May 2008 | A1 |
| 20080126936 | Williams | May 2008 | A1 |
| 20080168185 | Robbin et al. | Jul 2008 | A1 |
| 20080208870 | Tsang | Aug 2008 | A1 |
| 20090094252 | Wong et al. | Apr 2009 | A1 |
| 20090183060 | Heller et al. | Jul 2009 | A1 |
| 20090187609 | Barton et al. | Jul 2009 | A1 |
| 20100063670 | Brzezinski et al. | Mar 2010 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 61072008 | Mar 2008 | US |
