# US 2003/0204529 A1 · File caching method and apparatus

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0204529 A1
- Document ID: US20030204529A1
- Status: Published application
- Kind: A1
- Application number: 10/128,916
- Filed: 2002-04-24
- Published: 2003-10-30
- Earliest claimed: 2002-04-24
- Assignees: Hewlett-Packard Development Company, L.P.
- Inventors: William Edward Hertling; Michael Dean Whitmarsh
- Web page: https://patentgrep.com/patent/US20030204529A1

## CPC

- G06F 16/9574: {of access to content, e.g. by caching}
- Y10S 707/99931: Database or file accessing
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

A method of managing data files in a file caching server provides access to a plurality of stored data files. The method is to receive a request for a file, which is identified by a cryptographically secure checksum. The availability of the file is determined using the cryptographically secure checksum and, if said file is available, retrieving the file. If the file is not available to said file caching server, then a file request is issued to, and the file is retrieved from another file server where the file with the cryptographically secure checksum exists.

## Claims

### Claim 1

A method of managing data files in a file caching server that provides access to a plurality of stored data files, said method comprising:
receiving a request for a file, identified by a cryptographically secure checksum;
determining if said file is available to said file caching server using said cryptographically secure checksum and, if said file is available, retrieving said file;
if said file is not available to said file caching server, then requesting from another file server, a remote file having said cryptographically secure checksum.

### Claim 2 (depends on 1)

The method of claim 1, comprising:
providing the file in response to the request.

### Claim 3 (depends on 1)

The method of claim 1, comprising:
receiving the remote file from the other file server.

### Claim 4 (depends on 3)

The method of claim 3, comprising:
providing the remote file in response to the request.

### Claim 5 (depends on 1)

The method of claim 1, wherein the request includes a first file name, further comprising: a string of characters.

### Claim 6

A method of managing data files between a file caching server and a file server, operatively coupled together to provide access to a plurality of stored data files, said method comprising:
receiving at said file server, a request for a file having a file name;
determining if said file name correlates to a cryptographically secure checksum for a data file directly accessible to said file server;
if said first file name correlates to a cryptographically secure file identifier of a file accessible to said file server, then retrieving said file and sending said first file to the file caching server.

### Claim 7

A method of managing data file storage in a file caching server and a file server, which provide access to a plurality of stored data files, said method comprising::
receiving at a file server, a request for a file from a caching server, said file being identified to said file server by a file name;
said file server calculating a cryptographically secure file identifier for said file;
said file server sending said cryptographically secure file identifier for said file to said caching server.

### Claim 8 (depends on 7)

The method of claim 7, further including: sending said file from said file server to said caching server.

### Claim 9

A method of managing files on a file caching server, comprising:
receiving, at said file caching server, a file save request including a file to be saved on said file caching server and a file name associated with said file under which said file is to be saved;
determining a cryptographically secure checksum from contents of said file;
prior to saving said file, determining if said file is stored on said file caching server by the presence of the cryptographically secure checksum in said file caching server;
if the cryptographically secure checksum is not present in said file caching server, then storing the file, the file name, and the cryptographically secure checksum within the file caching server.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
determining if the cryptographically secure checksum is present on a file server to which said file caching server is operatively coupled
if the cryptographically secure checksum is not present in said file server, then storing the file, the file name, and the cryptographically secure checksum within the file server.

### Claim 11

A method of storing files on a network data resource that provides access to a plurality of stored data files to a plurality of network users, said method comprised of the steps of:
storing a file and said file name on a network data resource;
calculating a cryptographically-secure file identifier from the contents of said file;
storing said cryptographically-secure file identifier on said network data resource;
locating said file on said network data resource using either of said file name and said file identifier.

### Claim 12 (depends on 1)

The method of claim 1 1 wherein said step of storing a file and a file name on said network data resource includes the step of storing said file and file name on a file caching server.

### Claim 13 (depends on 11)

The method of claim 11 wherein said step of storing a file and a file name on said network data resource includes the step of storing said file and file name on a file server.

### Claim 14

A data network comprised of:
a file caching server capable of receiving requests for files from client computers operatively coupled to said file caching server, the file caching server identifying requested files by at least one of: a file name and a cryptographically secure checksum, said file caching server delivering to a client a locally stored copy of the requested file if said requested file is identified as being stored on said file caching server by the presence of said cryptographically secure checksum, and said file caching server delivering to the client a remotely stored copy of the requested file obtained from a file server if said requested file is not identified by said cryptographically secure checksum.

### Claim 15

A data network comprised of:
a file server capable of storing files from a file caching server operatively coupled to said file server, the file server identifying a file to be stored by a cryptographically secure checksum, said file server storing said file from said file caching server if said file is not identified as being stored on said file sever by the presence in said file server of said cryptographically secure checksum.

### Claim 16

Data storage media configured to store executable computer program instructions to cause a computer to:
receive a request for a file, which is identified by a cryptographically secure checksum;
determine if said file is available to said computer using said cryptographically secure checksum and, if said file is available, retrieving said file;
if said file is not available to said computer, then requesting from a second computer a remote file having said cryptographically secure checksum.

### Claim 17

A method of managing the transfer of a plurality of associated data files between a server and a client having a plurality of files to send to said server, said method comprising:
said client calculating a cryptographically secure checksum for at least a first file of said plurality of files;
said client determining if said server has a file with an identical cryptographically secure checksum;
if said server has a file with an identical cryptographically secure checksum, determining that said server has a copy of said first file;
if said server does not have a file with an identical cryptographically secure checksum, sending said first file to said server by said client.

### Claim 18 (depends on 17)

The method of claim 17 wherein said plurality of files are print job files.

### Claim 19 (depends on 17)

The method of claim 17 wherein said server is an on-line print service provider computer.

### Claim 20 (depends on 17)

The method of claim 17 wherein said client is a computer of a customer to an on-line print service provider.

### Claim 21 (depends on 17)

The method of claim 17 wherein the step of said client determining if said server has a file with an identical cryptographically secure checksum comprises: said client transmitting said checksums to said server and receiving from said server an identification of the checksums on the server that do not match checksums received from said client.

### Claim 22 (depends on 17)

The method of claim 17 wherein the step of said client determining if said server has a file with an identical cryptographically secure checksum comprises: said client transmitting said checksums to said server and receiving from said server an identification of the checksums on the server that do match checksums received from said client.

### Claim 23

A method of managing the transfer of a plurality of associated data files between a server and a client having a plurality of files to send to a server, said method comprising:
said client calculating a checksum for each file of said plurality of files;
said client sending each of said plurality of files to said server;
modifying at least one of said plurality of files;
said client recalculating the checksum for each of said plurality of files;
said client determining which of the files stored on said server have checksums that do not match the recalculated checksums;
said client re-sending to said server, only the files stored on the server whose checksums do not match the recalculated checksums on the client.

### Claim 24 (depends on 23)

The method of claim 23 wherein said step of modifying at least one of said plurality of files comprises: said client modifying said at least one of said files.

### Claim 25 (depends on 23)

The method of claim 23 wherein said step of modifying at least one of said plurality of files comprises: modifying said at least one of said files by a computer other than said client and said server.

### Claim 26 (depends on 23)

The method of claim 23 wherein said plurality of files are print job files.

### Claim 27 (depends on 23)

The method of claim 23 wherein said server is an on-line print service provider computer.

### Claim 28 (depends on 23)

The method of claim 23 wherein said client is a computer of a customer to an on-line print service provider.

### Claim 29

A method of managing the transfer of a plurality of associated data files between a server and a client having a plurality of files to send to said server, said method comprising:
said server receiving said plurality of files;
said server calculating a checksum for each file and storing the server-calculated checksums in a first list;
said server receiving a second list of client-calculated checksums from said client;
said server identifying to said client, checksums in the second list that are not in the first list;
said server receiving from said client, files whose checksums were not in the second list.

### Claim 30 (depends on 29)

The method of claim 29 wherein said files are print job files.

### Claim 31 (depends on 29)

The method of claim 29 wherein said step of identifying to said client, checksum in the second list that are not in the first list is comprised of the steps of: comparing the contents of said first list to the contents of said second list and identifying elements of the second list that are not in the first list.
