System and method for transporting files between networked or connected systems and devices

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.

What is claimed is: 
     
         1 . A method comprising:
 obtaining a file to be transferred from a source system to a target system;   identifying a format of the file, the format defining logical components resident within the content of the file;   deconstructing, by use of a processor, the file into a plurality of logical components using a deconstruction method based on the format of the file, the plurality of logical components including a plurality of cacheable logical components and at least one non-cacheable component;   generating a plurality of component identifiers for the cacheable logical components;   storing the plurality of cacheable logical components in a parent cache of the source system as indexed by the component identifiers corresponding to the plurality of cacheable logical components;   generating an element list including the component identifiers corresponding to the plurality of cacheable logical components within the file;   delivering the element list to the target system;   causing the target system to fetch any of the plurality of cacheable logical components from a child cache of the target system using the corresponding component identifiers and causing the target system to not transfer from the source system any of the cacheable logical components fetched from the child cache of the target system; and   causing the target system to fetch any of the plurality of cacheable logical components from the parent cache of the source system using the corresponding component identifiers, if any of the plurality of cacheable logical components is not present in the child cache of the target system based on the corresponding component identifiers.   
     
     
         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 deconstructed from a file based on the format of the file, the format defining logical components resident within the content of the file, the format also defining one or more deconstruction methods used to deconstruct the file, the plurality of logical components including a plurality of cacheable logical components and at least one non-cacheable component, the element list including a plurality of component identifiers for the cacheable logical components, each component identifier uniquely identifying a different one of the plurality of logical components;   fetching any of the plurality of cacheable logical components from a child cache of the target system using the corresponding component identifiers and causing the target system to not transfer from the source system any of the cacheable logical components fetched from the child cache of the target system;   fetching any of the plurality of cacheable logical components from a parent cache of the source system using the corresponding component identifiers, if any of the plurality of cacheable logical components is not present in the child cache of the target system based on the corresponding component identifiers;   reconstructing the file by combining the fetched plurality of cacheable logical components and at least one non-cacheable component using the element list information; and   storing the plurality of cacheable logical components into the child cache, if the plurality of cacheable logical components are not present in the child cache.   
     
     
         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:
 obtain a file to be transferred from a source system to a target system; 
 identify a format of the file, the format defining logical components resident within the content of the file; 
 deconstruct the file into a plurality of logical components using a deconstruction method based on the format of the file, the plurality of logical components including a plurality of cacheable logical components and at least one non-cacheable component; 
 generate a plurality of component identifiers for the cacheable logical components, each component identifier uniquely identifying a different one of the plurality of logical components; 
 store the plurality of cacheable logical components in a parent cache of the source system as indexed by the component identifiers corresponding to the plurality of cacheable logical components; 
 generate an element list including the component identifiers corresponding to the plurality of cacheable logical components within the file; 
 deliver the element list to the target system; 
 cause the target system to fetch any of the plurality of cacheable logical components from a child cache of the target system using the corresponding component identifiers and cause the target system to not transfer from the source system any of the cacheable logical components fetched from the child cache of the target system; and 
 cause the target system to fetch any of the plurality of cacheable logical components from the parent cache of the source system using the corresponding component identifiers, if any of the plurality of cacheable logical components is not present in the child cache of the target system based on the corresponding component identifiers. 
   
     
     
         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.