SYSTEM AND METHOD FOR TRANSPORTING FILES BETWEEN NETWORKED OR CONNECTED SYSTEMS AND DEVICES

• US 20130103786A1
• Filed: 10/20/2011
• Published: 04/25/2013
• Est. Priority Date: 10/20/2011
• Status: Active Grant

• Current Assignee: Allen Miglore
• Original Assignee: Allen Miglore
• Inventors: Miglore, Allen
• Granted Patent: US 8,898,244 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 13/00 Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units interface circuits for specific input/output devices G06F3/00 ; multiprogram control therefor G06F9/46; multiprocessor systems G06F15/16
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/152 using file content signatures, e.g. hash values
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/5681 Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

Abstract

A system and method for file transfer management are disclosed. An example embodiment includes: initiating a transfer of a file from a source system to a target system; deconstructing a file into logical components based on the format of the file; storing the cacheable logical components in a parent cache; generating an element list including a component identifier of the cacheable logical components; and delivering the element list to the target system. The example embodiment includes: receiving, at the target system the element list; determining if cacheable logical components are present in a child cache; fetching the cacheable logical components from the child cache; fetching other cacheable logical components and non-cacheable gap components from the source system; reconstructing the file by combining the fetched components; storing the missing cacheable logical components into the child cache; and delivering the reconstructed file to a destination.

Claims

1. A method comprising:

initiating, by use of a processor, a transfer of a file from a source system to a target system;

identifying a format of the file;

deconstructing the file into a plurality of logical components based on the format of the file, the deconstructing including identifying a position of a logical component within the file, the plurality of logical components including at least one cacheable logical component and at least one non-cacheable gap component;

generating a plurality of component identifiers, each component identifier being unique to a particular logical component of the file;

storing the at least one cacheable logical component in a parent cache as indexed by the component identifier of the at least one cacheable logical component;

generating an element list including the component identifier of the at least one cacheable logical component and the at least one non-cacheable gap component within the file; and

delivering the element list to the target system.

2. The method as claimed in claim 1 wherein the plurality of component identifiers are generated using a hash process.

3. The method as claimed in claim 1 wherein the parent cache is maintained by the source system.

4. The method as claimed in claim 1 wherein the element list includes information indicative of a classification as to whether a particular logical component is cacheable or non-cacheable.

5. The method as claimed in claim 1 wherein the element list includes a component identifier corresponding to a particular logical component.

6. The method as claimed in claim 1 wherein the element list includes information indicative of a source system identifier corresponding to a particular logical component.

7. The method as claimed in claim 1 wherein the source system is further configured to determine where the at least one non-cacheable gap component is located within the file.

8. A method comprising:

receiving, by use of a processor, at a target system an element list comprising information related to a plurality of logical components corresponding to a file, the plurality of logical components including at least one cacheable logical component and at least one non-cacheable gap component, the element list including a component identifier of the at least one cacheable logical component and at least one non-cacheable gap component within the file;

determining if the at least one cacheable logical component is present in a child cache;

fetching the at least one cacheable logical component from the child cache using the component identifier, if the at least one cacheable logical component is present in the child cache;

fetching the at least one cacheable logical component from a source system cache using the component identifier, if the at least one cacheable logical, component is not present in the child cache;

fetching the at least one non-cacheable gap component from the source system;

reconstructing the file by combining the fetched at least one cacheable logical component and the fetched at least one non-cacheable gap component using the element list information;

storing the at least one cacheable logical component into the child cache, if the at least one cacheable logical component is not present in the child cache; and

delivering the reconstructed file to a destination.

9. The method as claimed in claim 8 wherein the plurality of component identifiers are generated using a hash process.

10. The method as claimed in claim 8 wherein the child cache is maintained by the target system.

11. The method as claimed in claim 8 wherein the element list includes information indicative of a classification as to whether a particular logical component is cacheable or non-cacheable.

12. The method as claimed in claim 8 wherein the element list includes a component identifier corresponding to a particular logical component.

13. The method as claimed in claim 8 wherein the element list includes information indicative of a source system identifier corresponding to a particular logical component.

14. The method as claimed in claim 8 wherein the target system is further configured to determine where the at least one non-cacheable gap component is located within the file.

15. A system, comprising:

a data processor;

a cache, in data communication with the processor, for storage of logical components and related, information; and

a transfer management module, executable by the processor, to;

initiate, by use of the data processor, a transfer of a file from a source system to a target system;

identify a format of the file;

deconstruct the file into a plurality of logical components based on the format of the file, the deconstructing including identifying a position of a logical component within the file, the plurality of logical components including at least one cacheable logical component and at least one non-cacheable gap component;

generate a plurality of component identifiers, each component identifier being unique to a particular logical component of the file;

store the at least one cacheable logical component in a parent cache as indexed by the component identifier of the at least one cacheable logical component;

generate an element list including the component identifier of the at least one cacheable logical component and the at least one non-cacheable gap component within the file; and

deliver the element list to the target system.

16. The system as claimed in claim 15 wherein the plurality of component identifiers are generated using a hash process.

17. The system as claimed in claim 15 wherein the parent cache is maintained by the source system.

18. The system as claimed in claim 15 wherein the element list includes information indicative of a classification as to whether a particular logical component is cacheable or non-cacheable.

19. The system as claimed in claim 15 wherein the element list includes a component identifier corresponding to a particular logical component.

20. The system as claimed in claim 15 wherein the element list includes information indicative of a source system identifier corresponding to a particular logical component.

21. A method comprising:

initiating, by use of a processor, a transfer of a file from a source system to a target system;

identifying a format of the file;

deconstructing the file into a plurality of logical components based on the format of the file, the deconstructing including identifying a position of a logical component within the file, the plurality of logical components including at least one cacheable logical component and at least one non-cacheable gap component;

generating a plurality of component identifiers, each component identifier being unique to a particular logical component of the file;

storing the at least one cacheable logical component in a parent cache as indexed by the component identifier of the at least one cacheable logical component;

generating an element list including the component identifier of the at least one cacheable logical component, the position of the at least one cacheable logical component within the file, and information indicative of the at least one non-cacheable gap component within the file; and

delivering the element list to the target system.