Method and architecture for synchronizing files

• US 20150347447A1
• Filed: 05/27/2014
• Published: 12/03/2015
• Est. Priority Date: 05/27/2014
• Status: Abandoned Application

• Current Assignee: Acer Cloud Technology, Inc. (Acer, Inc.)
• Original Assignee: Acer Cloud Technology, Inc. (Acer, Inc.)
• Inventors: Lo, Raymond, Ho, W. Wilson, Hirsch, David Edward, Lee, Yuk Kwai, Onorato, Steve Jason
• Application Number:
  US14/288,378
• Publication Number:
  US 20150347447A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems

Abstract

Techniques for providing pervasive synchronization services to digital assets are described. With the synchronization services, copies of a digital asset, regardless where they are physically located as long as they are in predefined or registered storage area (e.g., a folder or repository), are kept synchronized. In other words, when one has made a change to a file on one computer, copies of the file distributed on other computers are all updated with the change. The pervasive synchronization services are performed by using metadata sets of the digital assets without releasing the content of the digital assets. A metadata set includes some or all of header information of a file holding a digital asset and supplemental information generated about the file, wherein the supplemental information includes at least location information to indicate where there are copies of the file. The location information facilitates a computing device to synchronize all the copies of the file with a change made by a user to one of the copies.

Claims

1. A method for synchronizing digital assets via a server device, the method comprising:

updating a metadata set of a digital asset when there is a change made to a status of the digital asset, wherein the change is detected by monitoring the status of the digital asset, and the metadata set includes some or all of header information of the digital asset and supplemental information including at least a location of the digital asset; and

synchronizing the digital asset via the metadata set without releasing a copy of the digital asset to the server device.

2. The method as recited in claim 1, wherein the server is on a public network, and the status of the digital asset is being monitored by a client module running on each of computing devices coupled to a private network.

3. The method as recited in claim 2, wherein at least a first device and a second device each have the digital asset, the supplemental information of the digital asset including identifiers respectively identifying the first and second devices.

4. The method as recited in claim 3, wherein said synchronizing the digital asset via the metadata set comprises:

causing the digital asset in the first device to be automatically updated when the digital asset in the second device has been updated.

5. The method as recited in claim 4, further comprising:

maintaining a policy module to determine how to cause the first device or the second service to service a request to access the digital asset.

6. The method as recited in claim 5, wherein a decision to cause the first device or the second service to service the request to access the digital asset is based on one or more of:

respective geographic distances of the first and second devices to the requesting device, and available computing resources of the first and second devices at the time the request was made by the requesting device.

7. The method as recited in claim 3, further comprising:

allocating a predefined storage area for storing the digital asset;

registering an identifier identifying the predefined storage area; and

generating metadata for each of the digital assets moved into the predefined storage area, wherein the metadata for the each of the digital assets includes the identifier.

8. The method as recited in claim 7, wherein the predefined storage area is a folder or a repository.

9. The method as recited in claim 8, wherein said updating a metadata set of a digital asset comprises:

expanding the metadata to include another identifier when a copy of each of the digital assets is made into another folder identified by the other identifier.

10. The method as recited in claim 9, wherein said synchronizing the digital asset via the metadata set comprises:

receiving the change to the each of the digital assets in the folder; and

causing each of the digital assets in the folder in another folder to be updated with the change.

11. The method as recited in claim 1, wherein each of the digital assets is an electronic file in a file format with header information.

12. A system for synchronizing digital assets, the system comprising:

a server configured to update a metadata set of a digital asset when there is a change made to a status of the digital asset, wherein the change is detected by monitoring the status of the digital asset, and the metadata set includes some or all of header information of the digital asset and supplemental information including at least a location of the digital asset, the server is configured to maintain the metadata set but does not have an access to the digital asset, and is further configured to communicate with a computing device to receive an update to the metadata therefrom.

13. The system as recited in claim 12, wherein the server is coupled to a public network while the computing device is coupled to a private network.

14. The system as recited in claim 13, wherein the computing device is a client device used by a user to make the change to the digital asset.

15. The system as recited in claim 14, wherein the client device is executing a client module configured to monitor a status of the digital asset and send an update to the server when the status of the digital asset is updated.

16. The system as recited in claim 15, wherein the server is configured to update the metadata set when a copy of the digital asset is created, the metadata includes an indication where the copy of the digital asset is located.

17. The system as recited in claim 13, wherein the computing device is an internal repository to keep a latest version of the digital asset when the digital asset has been changed on a client device coupled to the internal network.

18. The system as recited in claim 17, wherein the server is configured to cause the latest version of the digital asset to be always used when another client device is caused to access the digital asset.

19. A software product, stored in a memory space and executed on a server, for synchronizing digital assets, the software product comprising:

program code for updating a metadata set of a digital asset when there is a change made to a status of the digital asset, wherein the change is detected by monitoring the status of the digital asset, and the metadata set includes some or all of header information of the digital asset and supplemental information including at least a location of the digital asset; and

program code for causing a first computing device to retrieve a latest version of the digital asset from a second computing device when the digital asset is attempted for access by a user on the first computing device, wherein the server does not have an access to the digital asset.

20. The software product as recited in claim 19, wherein the server is on a public network, and the status of the digital asset is being monitored by a client module running on each of the first and second computing devices coupled to a private network.

21. The software product as recited in claim 20, further comprising:

program code for maintaining a policy module to determine how to service a request from the first computing device when the user attempts to access the digital asset, wherein the second computing device is determined by the policy module from a plurality of client computing devices each of which includes a copy of the latest version of the digital asset.

22. The software product as recited in claim 21, wherein the policy module is pertaining to a geographic distance between the first and second computing devices and available computing resources at a time the request is created.

23. The software product as recited in claim 22, wherein the first computing device is a storage device designated to keep a latest version of some or all of managed digital assets for an enterprise.

24. The software product as recited in claim 21, wherein the software product is controlled by a service provider in a business to provide synchronization services for all business entities.