Transferring files

• US 10,528,547 B2
• Filed: 03/25/2016
• Issued: 01/07/2020
• Est. Priority Date: 11/13/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Hayworth, Christopher Robert, Zhang, Dachuan
• Primary Examiner(s): Nguyen, Cam Linh T
• Application Number:
  US15/081,111
• Publication Number:
  US 20170139978A1
• Time in Patent Office: 1,383 Days
• Field of Search: 707693, 707736
• CPC Class Codes: G06F 11/1004 to protect a block of data words, e.g. CRC or checksum G06F11/1076 takes precedence; security arrangements for protecting computers or computer systems against unauthorized activity G06F21/00
• CPC Class Codes: G06F 16/1748 De-duplication implemented within the file system, e.g. based on file segments de-duplication techniques in storage systems for the management of data blocks G06F3/0641
• CPC Class Codes: G06F 16/2255 Hash tables
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

Systems, components, devices, and methods for transferring files are provided. An example file is a container file comprising a plurality of component files. A non-limiting example method is a method for transferring a container file over a network to a remote device. The method includes the step of accessing a container file, the container file comprising a plurality of components. The method also includes the step of transmitting metadata information for the plurality of components to the remote device. The method further includes the step of determining components from the plurality of components to transmit to the remote device. The method additionally includes the step of transmitting component data items for the determined components to the remote device.

Claims

1. A system for transferring a container file over a network to a remote device, the system comprising:

at least one processor; and

memory, operatively connected to the at least one processor and storing;

a container editor application; and

instructions that, when executed by the at least one processor, cause the at least one processor to perform a method comprising;

loading a container file using the container editor application, the container file comprising a plurality of component files;

obtaining the plurality of component files from the container file;

transmitting metadata information for each component file in the plurality of component files to the remote device; and

based on a determination that one or more component files in the plurality of component files are not available to the remote device, transmitting component data for the determined one or more component files to the remote device.

2. The system of claim 1, further comprising instructions for generating metadata information for each component file in the plurality of component files, wherein the metadata information for each component file comprises a component file name, size information for the component file, and a fingerprint value for the component file.

3. The system of claim 2, wherein the size information comprises at least one of an uncompressed size for the component file and a compressed size for the component file.

4. The system of claim 2, wherein the fingerprint value for the component file comprises a cyclic redundancy code calculated on the component file.

5. The system of claim 1, further comprising instructions for determining, prior to transmitting the component data to the remote device, whether each component file in the plurality of component files is available to the remote device, the determining comprising:

querying a remote cache index at the remote device to determine whether each component file in the plurality of component files is identified in the remote cache index as being available to the remote device; and

determining to transmit the one or more component files in the plurality of component files to the remote device based on the one or more component files not identified in the remote cache index as being available to the remote device.

6. The system of claim 5, wherein:

the remote cache index stores a first hash value for each component file available to the remote device, the first hash value generated based on data associated with the component file; and

the system further comprises instructions for;

transmitting a query to the remote device that includes a second hash value for a respective component file in the plurality of component files; and

receiving, from the remote device, a response that indicates whether the respective component file is available to the remote device, the response based on a determination of whether the second hash value matches the first hash value.

7. The system of claim 6, wherein:

the remote cache index stores with each first hash value a first identifier of the remote device;

the query includes the second hash value and a second identifier of the remote device; and

the response from the remote device indicating whether the respective component file is available to the remote device is based on a determination of whether the second hash value matches the first hash value and the second identifier matches the first identifier.

8. The system of claim 5, further comprising instructions for updating the remote cache index based on the transmitted component data.

9. The system of claim 1, further comprising instructions for:

determining, prior to transmitting the component data to the remote device, whether each component file in the plurality of component files is not available to the remote device, the determining comprising receiving a request from the remote device for component data for at least one component file in the plurality of component files.

10. The system of claim 1, further comprising instructions for determining, prior to transmitting the component data to the remote device, which component files in the plurality of component files is not available to the remote device, the determining comprising:

searching a common component index for one or more component files in the plurality of component files, wherein the common component index comprises component files identified as being usable in multiple container files; and

determining to transmit the respective component file to the remote device based on the search of the common component index.

11. The system of claim 1, wherein:

the container file comprises a presentation file;

the container editor application comprises a presentation application; and

loading the container file comprises loading the presentation file using the presentation application.

20. The system of claim 1, further comprising instructions for:

determining, prior to transmitting the component data to the remote device, which component files in the plurality of component files is not available to the remote device, the determining comprising;

accessing a list that is received from the remote device to determine which component files in the plurality of component files is available to the remote device; and

determining to transmit the one or more component files in the plurality of component files based on a determination that the one or more component files are not included in the list.

12. A method of transferring a container file over a network to a remote device, the method comprising:

accessing a container file, using a container editor application, to obtain a plurality of component files and a directory listing of the plurality of component files;

generating, by a processor, metadata information for the plurality of component files based on the directory and header data extracted from the plurality of component files;

transmitting the metadata information for the plurality of component files to the remote device for use in reconstructing the container file on the remote device; and

based on a determination that one or more component files in the plurality of component files is not stored on the remote device, transmitting component data for the one or more component files to the remote device.

13. The method of claim 12, further comprising prior to accessing the container file, receiving a request from the remote device for component data for at least one component file in the plurality of component files.

14. The method of claim 12, wherein:

the metadata information comprises first metadata information;

the container file comprises a first container file; and

the method further comprises;

storing, at the remote device, component data for at least one of the plurality of component files in a component data cache;

receiving, at the remote device, second metadata information for a second plurality of component files in a second container file;

reconstructing, at the remote device, the second container file, wherein the second container file is reconstructed based on the received second metadata information and at least some of the component data stored in the component data cache.

15. The method of claim 14, wherein the second container file comprises a version of the first container file that has been revised on the remote device.

16. The method of claim 14, wherein reconstructing the second container file further comprises using the received second metadata information to determine whether component data for a component file of the second plurality of component files is stored in the component data cache.

17. The method of claim 16, wherein:

reconstructing the second container file further comprises comparing a second fingerprint value for a component file of the second plurality of component files to a first fingerprint value for component data stored in the component data cache; and

based on a determination that the second fingerprint value matches the first fingerprint value, determining that component data for the component file of the second plurality of component data files is stored in the component data cache.

18. A system for transferring a container file over a network to a remote device, the system comprising:

at least one processor; and

memory, operatively connected to the at least one processor and storing instructions that, when executed by the at least processor, cause the at least one processor to perform operations comprising;

loading a presentation container file using a presentation editor, the presentation container file comprising a plurality of component files and a directory listing of the plurality of component files;

generating, by the at least one processor, metadata information for the plurality of component files based on the directory and header data extracted from the plurality of component files, the header data comprising a name, size information for the component file, and a fingerprint value for the data of the component file;

transmitting the metadata information for the plurality of component files to the remote device for use in reconstructing the presentation container file on the remote device;

determining one or more component files in the plurality of component files not stored on the remote device; and

transmitting component data for the determined one or more component files to the remote device.

19. The system of claim 18, wherein determining the one or more component files not stored on the remote device comprises:

querying a remote cache index at the remote device to determine which component files in the plurality of component files are identified in the remote cache index as being stored on the remote device; and

determining to transmit the one or more component files in the plurality of component files to the remote device based on the one or more component files not identified in the remote cache index as being stored on the remote device.