| Method and apparatus for accelerating and improving access to network files -> Monitor Keywords |
|
|
 
Method and apparatus for accelerating and improving access to network filesRelated Patent Categories: Data Processing: Database And File Management Or Data Structures, Database Or File Accessing, Access Augmentation Or OptimizingMethod and apparatus for accelerating and improving access to network files description/claimsThe Patent Description & Claims data below is from USPTO Patent Application 20070203886, Method and apparatus for accelerating and improving access to network files. Brief Patent Description - Full Patent Description - Patent Application Claims
RELATED APPLICATIONS [0001] This application is a divisional of U.S. application Ser. No. 10/174,735, filed Jun. 18, 2002, the contents of which are incorporated herein by reference as if fully set forth herein. FIELD OF THE INVENTION [0002] The present invention relates to accessing network files and more specifically to accelerating and improving access to network files. BACKGROUND OF THE INVENTION [0003] In the early days of computing, a computer only had access to data that was on that computer's local disk. As time progressed, computers were connected together using networks. Thus, there was a possibility that each computer could access data on other computer's local disks (hereinafter referred to as "decentralized file systems"). FIG. 1 is a block diagram of a decentralized file system with three computers (110, 120, and 130). Each of these three computers is associated with a corresponding local disk (111, 121, 131). Using a decentralized file system mechanism, computer 110 can access data on disk 131, which is associated with computer 130. [0004] However, the problem with decentralized file systems is that managing the data is difficult because the data is spread out. Furthermore, decentralized file systems make file sharing difficult. For example, a department may have files that each person in the department needs to update on a regular basis. If these files are spread among various computer systems, all of those various systems must constantly remain online for the files to be available. Furthermore, because of the critical nature of these files, these files need to be backed up on a regular basis. Backing up files that are spread across many systems can by a complex, and time and resource-consuming, operation. A decentralized file system is not convenient for file sharing or managing files. [0005] The next step in the evolution of file systems was to centralize important data onto one or more centralized shared disks (hereinafter referred to as a "centralized file system"). FIG. 2 is a block diagram of a centralized file system. The shared files reside on the shared disk 240. The computers (210, 220, and 230) have access to the files on shared disk 240. This is a more convenient topology for sharing files among many people and for managing files, for example, by backing up the files. However, there are also problems with centralized file systems. For example, if the bandwidth of the connection 250 between the shared disk 240 and the computer 210 is low, then computer 210 will have slow access to the files on shared disk 240. Worse yet, if connection 250 is down, computer 210 will not be able to access files on shared disk 240 at all. [0006] A third approach to file sharing is where not only do computers share data using shared disks but also the data on the shared disks is replicated. The replicated data is "pushed" to local disks associated with the individual computers (hereinafter referred to as a "hybrid file system"). FIG. 3 is a block diagram of a hybrid file system. The computers (310, 320, 330, 350, and 360) share files that are on the shared disks (341 and 342), but do so by accessing the replicated versions of those files on their local disks (311, 321, 331, 351, and 361). [0007] To address potential problems with speed of access and connections going down, the data on the shared disks (341 and 342) is periodically replicated and this replicated data is pushed to the individual computers (310, 320, 330, 350, and 360) that are interested in the replicated data. Then the replicated data is stored on the local disks (311, 321, 331, 351, and 361). Policies are used to determine which computers are interested in what shared files and at what intervals the shared files of interest are to be transmitted to the interested computers. For example, assume there is a slide-presentation file on shared disk 341 that computer 350 is interested in. A policy is set up indicating that this slide-presentation file on shared disk 341 is replicated every 24 hours and sent to computer 350 where the slide-presentation file is then stored on the local disk 351. [0008] Such a hybrid file system addresses the problem of access speed because computer 350 accesses the local version. However, other problems are associated with hybrid file systems. For example, the slide-presentation file on shared disk 341 may be transmitted to computer 350 at 2:00 AM and stored locally on disk 351. Then, at 2:05 AM on the same day, someone modifies the slide-presentation file on shared disk 341. The person using computer 350 will be using an old version of the slide-presentation file until the next time the slide-presentation file is transmitted to computer 350. Furthermore, a hybrid file system is not an efficient use of resources such as CPU cycles or storage space. Additional CPU cycles are needed to replicate data and transmit the replicated data to the interested parties. Additional storage space is needed to store the various versions of replicated data on all the computers that are interested in this replicated data. The problem of connections having low bandwidth or going down still exists. Policies for replicating the shared data are also needed, increasing the complexity of setup and maintenance. [0009] Based on the foregoing, it is clearly desirable to provide techniques and mechanisms for sharing data that avoids problems associated with current approaches. SUMMARY OF THE INVENTION [0010] Techniques are provided for accelerating and improving access to network files. One technique for providing data quickly and efficiently is to send a thumbnail of a file to a user rather than sending the entire file. The thumbnail has enough information to convey the contents of the full version of the file, but contains less data. According to one embodiment, the thumbnail version is accompanied by address data that allows the full version of the file to be easily retrieved if, after inspecting the thumbnail, a user determines that the full version is needed. [0011] Another technique for providing data quickly and efficiently is to generate, at a "parent" component that is remote relative to the requester, the difference between a current version of data and a non-current version of data. The parent component then transmits this difference to a "child" component that is located closer to the requester. The child component uses the difference to update the non-current version of data the requesting user currently has access to, and to provide the current version thus created to the requestor. [0012] A third technique that can be used in combination with the first two techniques is to use the parent component to compress data (either the entire file, the thumbnail or file difference) before transmitting the data to the child component. The child component decompresses the data prior to providing the data to the requester. A fourth technique that can be used in combination with the third technique is to securely transmit the compressed data between the parent and child component. BRIEF DESCRIPTION OF THE DRAWINGS [0013] The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which: [0014] FIG. 1 is a block diagram of a decentralized file system; [0015] FIG. 2 is a block diagram of a centralized file system; [0016] FIG. 3 is a block diagram of a hybrid file system; [0017] FIG. 4 is a block diagram of system that implements an embodiment of the invention; and [0018] FIG. 5 is a block diagram of a computer system on which embodiments of the invention may be implemented. DETAILED DESCRIPTION OF THE INVENTION Continue reading about Method and apparatus for accelerating and improving access to network files... Full patent description for Method and apparatus for accelerating and improving access to network files Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Method and apparatus for accelerating and improving access to network files patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Method and apparatus for accelerating and improving access to network files or other areas of interest. ### Previous Patent Application: System and method for retrieving files from a file server using file attributes Next Patent Application: Method for efficiently retrieving entity beans in an ejb container Industry Class: Data processing: database and file management or data structures ### FreshPatents.com Support Thank you for viewing the Method and apparatus for accelerating and improving access to network files patent info. IP-related news and info Results in 0.11232 seconds Other interesting Feshpatents.com categories: Novartis , Pfizer , Philips , Polaroid , Procter & Gamble , 174 |
 * Protect your Inventions * US Patent Office filing 
PATENT INFO |
|
