Thomas Patrick Yohe et al., U.S. Patent No. 5,835,943, “Apparatus and Method for
`Increased Data Access in a Network File Oriented Caching System,” issued Nov. 10, 1998 (“’943”)
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`MICROSOFT
`
`
`
`EXHIBIT 1010
`
`
`
`
`
`1
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`
`
`2
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`
`
`3
`
`
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`Reference
`
`Yohe discloses all of the elements and all of the functions of this claim arranged as
`they are arranged in the claim. See below. E.g.: “the present invention is directed
`to an apparatus for increased data access in a network, which includes a file server
`computer having a permanent storage memory, a cache verifying computer
`operably connected to the file server computer in a manner to form a network for
`rapidly transferring data, the cache verifying computer having an operating
`system, a first memory and a processor with means for performing an operation on
`data stored in the permanent storage memory of the file server computer to
`produce a signature of the data characteristic of one of a file and directory, a
`remote client computer having an operating system, a first memory, a cache
`memory and a processor with means for performing an operation on data stored in
`the cache memory to produce a signature of the data, a communication server
`operably connected to the remote client computer to the cache verifying computer
`and the file server computer and comparators operably associated with the cache
`verifying computer and remote client computer for comparing the signatures of
`data with one another to determine whether the signature of data of the remote
`client is valid.” (’943, 2:41-61).
`
`Yohe discloses “an apparatus for increased data access in a network” (’943, 2:41-
`42), such as the World Wide Web (’943, 4:23-27). Yohe discloses “a network file
`oriented caching system” (’943, title) which “increases the speed in which data in
`the form of files and directories are accessed.” (’943, 1:12-15; see also id. at 3:8-
`21, 4:22-24, 5:45-50, 5:59-60, 6:22-23).
`
`On the client side of the network, Yohe discloses “a remote client computer.”
`(’943, 2:51). On the server side of the network, Yohe discloses “a file server
`
`4
`
`Claim
`
`Claim 1 as a Whole
`
`1. A system for data access in
`a packet-switched network,
`comprising:
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`(a) a sender/computer
`including
`
` (i) an operating unit,
`
`computer having a permanent storage memory, a cache verifying computer
`operably connected to the file server computer in a manner to form a network for
`rapidly transferring data.” (’943, 2:43-46). Also, “a communication server is
`operably connected to the remote client computer to the cache verifying computer
`and the file server computer.” (’943, 2:54-57, Fig. 2). (See also ’943, claim 1).
`
`See above. Yohe discloses “a network computer system 10 having at least one
`remote client computer 12, cache verifying computer 14, communication server 16
`and file server computer 18.” (’943, 4:42-44). The sender computer system may
`comprise a Cache Verifying Computer, a File Server Computer, and a
`Communication Server. (’943, Fig. 2).
`
`“The cache verifying computer 14 includes a cache verifying agent (CVA) 54
`having a BSG [(block signature generator)] 56 (of the type described herein), a
`directory signature generator (DSG) 57 and a comparator 58.” (’943, 5:14-17).
`Yohe discloses alternative embodiments wherein “the cache verifying agent 54
`could reside as part of the communication server 16 or as a stand alone processor
`with its own memory and operating system.” (’943 patent, 5:33-36). (See also
`‘943, claim 1).
`
`See above. While the ’717 patent does not define the meaning of “operating unit,”
`the ’717 does not describe anything reasonably called an “operating unit” which is
`not also disclosed in this reference.
`
`Yohe discloses that the cache verifying computer includes “an operating system.”
`(’943, 2:46-47). The cache verifying computer includes “an OS [(operating
`system)] 60 having an FSI [(file system interface)] 62 operatively connected to
`
`5
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`Claim
`
`Reference
`
`CVA [(cache verifying agent)] 54.” (’943, 5:17-18). “The file server computer 18
`includes an OS 70 having an FSI 72 which is operatively connected to an LFS 74.”
`(’943, 5:22-23). (See also ’943, claim 1).
`
` (ii) a first memory,
`
`See above. Yohe discloses that the cache verifying computer includes “a first
`memory.” (’943, 2:47).
`
`Yohe discloses alternative embodiments wherein the cache verifying agent could
`be “a stand alone processor with its own memory and operating system.” (’943,
`5:34-36). (See also ’943, claim 1).
`
` (iii) a permanent storage
`memory and
`
`See above. Yohe discloses that the cache verifying computer includes “means for
`performing an operation on data stored in the permanent storage memory of the
`file server computer.” (’943, 2:47-49).
`
`“‘Permanent storage memory,’ as used herein, includes, but not limited to, disk
`drive, flash RAM or bubble memory, for example.” (’943, 3:5-7).
`
`Yohe discloses the file server computer includes “a DD [(disk driver)] 78 and a
`PSD [(permanent storage disk)] 80.” (’943, 5:24). (See also ‘943, claim 1).
`
` (iv) a processor and a
`
`See above. Yohe discloses that the cache verifying computer includes “a
`processor.” (’943, 2:47).
`
`Yohe discloses alternative embodiments wherein the cache verifying agent could
`be “a stand alone processor with its own memory and operating system.” (’943,
`5:34-36). (See also ’943, claim 1).
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`6
`
`

`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`Claim
`
`Reference
`
`(b) remote receiver/computer
`including
`
`See above. Yohe discloses “a network computer system 10 having at least one
`remote client computer 12.” (’943, 4:42-43). (See also ’943, claim 1).
`
` (i) an operating unit,
`
`See above. Yohe discloses that the remote client computer includes “an operating
`system.” (’943, 2:51-52). “The remote client computer 12 has an operating
`system (OS) 24 with a file system interface (FSI) 26.” (’943, 4:58-59). (See also
`’943, claim 1).
`
` (ii) a first memory,
`
`See above. Yohe discloses that the remote client computer includes “a first
`memory.” (’943, 2:52).
`
`Yohe discloses that the receiver computer includes “a RAM based disk cacher
`(RBDC) 30.” (’943, 4:61-62). (See also ’943, claim 1).
`
` (iii) a permanent storage
`memory and
`
`See above. Yohe discloses that the receiver computer includes a “disk driver (DD)
`32 and permanent storage disk (PSD) 34.” (’943, 4:62-63).
`
` (iv) a processor,
`
`See above. Yohe discloses that the remote client computer includes “a processor.”
`(’943, 2:52). (See also ’943, claim 1).
`
`(c) said sender/computer and
`said receiver/computer
`communicating through said
`network;
`
`(d) said sender/computer
`further including means for
`
`See above. Yohe discloses that the server-side computer(s) communicate with the
`remote client computer through the network. “[A] communication server [is]
`operably connected to the remote client computer[,] the cache verifying computer
`and the file server computer.” (’943, 2:54-57). “The remote client computer 12
`communicates via communication link 22 to the communication server 16.” (’943,
`4:51-52).
`
`As this element apparently is construed by Proxyconn, this reference discloses it.
`
`The ’717 patent does not define in a consistent manner the meaning of a “digital
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`7
`
`

`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`Claim
`
`Reference
`
`creating digital digests on
`data;
`
`digest.” The only mathematical functions it identifies for calculating a “digital
`digest” (both of which it rules out as well) are MD5 and CRC. Nevertheless, if
`this element is disclosed in the ’717 patent, then it likewise is disclosed in this
`reference.
`
`Yohe discloses that the cache verifying computer includes “a processor with
`means for performing an operation on data stored in the permanent storage
`memory of the file server computer to produce a signature of the data
`characteristic of one of a file and directory.” (’943, 2:47-51).
`
`“The cache verifying computer 14 includes a cache verifying agent (CVA) 54
`having a BSG [(block signature generator)] 56 (of the type described herein), a
`directory signature generator (DSG) 57….” (’943, 5:14-16).
`
`Yohe discloses “a network file oriented caching system” (’943, title) which
`“increases the speed in which data in the form of files and directories are
`accessed.” (’943, 1:12-15; see also id. at 3:8-21, 4:22-24, 5:45-50, 5:59-60, 6:22-
`23). The BSG (block signature generator) calculates a signature on such a “file” or
`other data object or sub-object, constituting “data.” Files stored in the file system
`are of arbitrary size, as are file directories. Both a BSG-calculated and a DSG-
`calculated signature is a fixed-size binary value calculated from arbitrary-size
`binary data in such a way that it depends only on the contents of the data (e.g., file
`or directory) and a “low” probability (at least as “low” as MD5) that two different
`data have the same signature value.
`
`The BSG uses MD5 or CRC to calculate signatures from data. In one
`embodiment, the DSG uses the BSG to calculate the signature of each directory
`
`8
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`sub-object, and then the DSG incorporates the signature values of the sub-objects
`into the directory signature. Hence the directory signature is generated from
`exclusive-OR’ing the signatures of the directory sub-objects.
`
`In the directory request primitive, “the NFC 42 [of the receiving computer] ‘sends’
`720 a directory verify request to CVA 54 via NTL 38. This triggers the steps 750
`(Fig. 16) wherein NFC 42 waits and ‘receives’ 721 signature from CVA 54.”
`(’943 patent, 8:7-9). When the sender’s CVA receives such a request, the CVA
`computes a directory signature. “As seen in FIG. 16, the steps 750 are performed
`by the CVA 54. Particularly, the DSG 57 ‘initializes’ 751 signature of a directory.
`The DSG 57 ‘retrieves’ 752 the first directory sub-object from the FS 18 via NTL
`66. The DSG 57 ‘asks’ 753 is this the last sub-object? If no, DSG 57 ‘factors’
`754 the signature of this sub-object into the overall signature of the directory. The
`DSG 57 then ‘retrieves’ 755 the next sub-object from FS 18 and returns to step
`753. If the last sub-object, CVA 54 ‘sends’ 756 back signature of directory to
`NFC 42.” (’943, 7:19-8:3).
`
`Yohe discloses that the sender’s “cache verifying agent 54 could reside as part of
`the communication server 16 or as a stand alone processor with its own memory
`and operating system.” (’943, 5:33-36). Elements of the CVA are disclosed in
`’943 Fig. 2. Within the sender’s CVA, there is “a BSG 56 (of the type described
`herein), a directory signature generator (DSG) 57 and a comparator 58.” (’943,
`5:14-17). The CVA “[i]nvokes BSG 56 to obtain [s]ignature of data.” (’943, Fig.
`8, step 354), and uses the DSG 57 “to generate the Signature of Directory.” (’943,
`13:40).
`
`9
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`Yohe discloses a flowchart (’943, Fig. 16) that shows the sender’s steps for
`calculating a directory signature. When the directory signature generator (DSG)
`computes a directory signature, it retrieves all the directory sub-objects (’943, Fig.
`16, steps 752 and 755). If the retrieved sub-object is not the last sub-object (’943,
`Fig. 16, step 753), the DSG “factors the signature of [the] sub-object into the
`overall signature of the directory.” (’943, 7:24-25; Fig. 16, step 754). Since the
`BSG 56 is the only block within the CVA that computes a signature of an object (a
`block of data), the DSG uses the BSG to calculate the signature of the directory
`sub-objects.
`
`Collectively, all the directory sub-objects combined make up the content of a
`directory object. Yohe defines that an “‘object’ is a sequence of data of variable
`length” (’943, 3:19) and hence a directory object is of arbitrary length.
`
`When the client-receiver receives the directory signature, the “NFC 42 ‘invokes’
`722 DSC 46 to compare whether signature matches the retrieved signature in
`719?” (’943, 8:9-11). The client-receiver’s NFC sees only the directory signature
`as a whole and not individual directory sub-object signatures. The directory
`signature corresponds to the “digital digest” in the claim. If the client decides to
`retrieve data content from the server because of a mismatch in the directory
`signature, the client retrieves the content of the entire directory from which the
`directory signature had been calculated. (’943, Fig. 15, steps 724-727).
`
`Yohe discloses that the signature calculated by the BSG can be either a cyclic
`redundancy check (CRC) or a signature such as MD5, which are fixed length
`output strings that depend only on the data.
`
`10
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`“In order to generate the signature, each BSG 44 and 56 employ a protocol for
`performing a cyclic redundancy check (CRC) on the specified data which includes
`signature and coordinates (an offset into the file and specifying length of the data).
`The protocol the CRC employs is a fast method for generating a 64 bit CRC on a
`32 bit CPU, The existing bit structure on a 32 bit CPU is that of the type
`‘pppfcs32’ algorithm described in ‘RFC1662.TXT’ by W. Simpson. The
`invention modifies the structure as follows: The 64 bit value will consist of two
`parts:
`1. The existing 32 bit value will be utilized.
`2. An additional 32 bits will be derived by dividing the length by four and
`performing the operation on four groups of the byte stream. On each of the four
`instances the least significant 8 bytes of the ‘in progress’ frame check sequence (a
`32 bit value computed by repetitively exclusive-oring a constant retrieved by
`indexing a character stream into a table of contents) will be appended to a second
`32 bit number which was initialized to zero.” (’943, 11:56-12:65).
`
`In addition to the flow chart (’943, Fig. 16), Yohe discloses an example function
`CSXorDirEntry() (’943, 14:1-12) for generating a directory signature from the
`signatures of the directory sub-objects. Consider a directory that includes N sub-
`objects. As described in an example in the previous two paragraphs, the signature
`of each sub-object is a 64-bit CRC. For each sub-object in the directory, the
`“CVA 54 factors 754 the signature of the sub-object into the signature of directory
`by invoking the logic CSXorDirEntry.” (’943, 13:65-67).
`
`Given a signature of a directory sub-object, the function CSXorDirEntry() updates
`
`11
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`Claim
`
`Reference
`
`the directory signature using an exclusive-OR operation within the code segment:
`
`“int j=0;
`
`for (i=0;i<(sizeof(OD_DIR_INFO)/sizeof(DWORD));i++,lpdDirInfo++)
`
`{
`
` lpdSign[j] ^= *lpdDirInfo;
`
` j=1-j;
`
`}” (’943, 14:7-12).
`
`The type definition section at ’943 patent col. 8, DWORD indicates that DWORD
`is a 16-bit data type. In the for loop, lpdDirInfo is a DWORD array that holds the
`signature of a directory sub-object, and lpdSign is a DWORD array that holds the
`directory signature. When the for loop is executed, the instructions sweep over the
`number of DWORDs required to store the signature of the directory sub-object.
`For each iteration in the for loop, a 16-bit segment of lpdDirInfo is exclusive-
`ORed with a 16-bit segment of lpdSign. The logic in the for loop shows that the
`value of the index j alternates between the values 0 and 1 from iteration to
`iteration. This means that only two elements of lpdSign is used, and hence the
`length of the directory signature is a 32-bit fixed length quantity, in this
`embodiment.
`
`In addition to CRC, Yohe discloses that “other types of verification tools may be
`employed to carry out the present invention such as the MD5 algorithm which is
`
`12
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`(e) said receiver/computer
`further including
`
` (i) a network cache memory
`and
`
`described in ‘RFC1322.TXT’ by R. Rivest.” (’943, 13:36-39). (See also ’943,
`claim 1).
`
`Yohe discloses a receiver computer that includes the following elements.
`
`As this element apparently is construed by Proxyconn, this reference discloses it.
`
`To the extent that a “network cache” merely designates an intended use for a
`memory device, not a structural limitation on that memory device, such an
`intended use has no patentable weight or consequence when comparing the claim
`as a whole to the reference, although it is a limitation in any infringement analysis.
`
`Although the ’717 patent does not define “network cache memory” or disclose any
`structure thereof distinguishing it from any other memory, to the extent it is
`disclosed in the ’717 patent this reference also discloses it.
`
`Yohe discloses that the remote client computer includes “a cache memory.” (’943,
`2:52).
`
`Yohe discloses that the remote client computer includes “a local file system, which
`in turn is connected to a RAM based disk cacher (RBDC) 30.” (’943, 4:60-62).
`
`Yohe defines the meanings of the terms caching and cache as follows: “‘Caching’
`is the function of retrieving an object from a relatively high speed storage device
`from a list of most-recently-used objects. ‘Cache’ is a file which resides in
`permanent storage and contains the most-recently-used blocks of data read from a
`remote file server.” (’943, 3:13-18). Thus, Yohe’s “cache memory” is permanent
`
`13
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`storage for storing copies of data received over the network.
`
`Yohe’s claims also disclose cache memory located in the permanent memory of
`the receiver:
`
`“1. An apparatus for increased data access from one of a file and a directory in a
`file oriented network, which comprises:
`
`a file server computer having an operating system, a first memory, a
`permanent storage memory and a processor;
`
`a cache verifying computer operably connected to said file server computer
`in a manner to form a network for rapidly transferring data, said cache verifying
`computer having an operating system, a first memory and a processor with means
`for performing an operation on data stored in said permanent storage memory of
`said file server computer to produce a signature of said data from one of the file
`and the directory;
`
`a remote client computer having an operating system, a first memory, a
`cache memory and a processor with means for performing an operation on data
`stored in said cache memory to produce a signature of said data;
`
`a communication server operably connecting to said remote client computer
`to said cache verifying computer and said file server computer;
`
`a first comparator operably associated with said cache verifying computer
`for comparing said signatures of data of said file with one another to determine
`whether said signature of data of said file of said remote client is valid; and
`
`a second comparator operably associated with said remote client computer
`for comparing said signatures of said data of said directory with one another to
`determine whether said signature of data of said directory of said remote client is
`
`14
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
` (ii) means for creating
`digital digests on data in said
`network cache memory; and
`
`valid.
`
`6. The invention in accordance with claim 1, wherein said first memory of said
`remote client computer is disposed in a RAM of said remote client computer, said
`first memory of said cache verifying computer is disposed in a RAM of said cache
`verifying computer, said first memory of said file server computer is disposed in a
`RAM of said file server computer and said permanent storage memory is disposed
`on a permanent storage disk of said file server computer and said cache memory is
`disposed on a permanent storage disk of said remote client computer.” (’943,
`14:40-15:3, 15:24-33).
`
`As this element apparently is construed by Proxyconn, this reference discloses it.
`
`The ’717 patent does not define in a consistent manner the meaning of a “digital
`digest.” The only mathematical functions it identifies for calculating a “digital
`digest” (both of which it rules out as well) are MD5 and CRC. Nevertheless, if
`this element is disclosed in the ’717 patent, then it likewise is disclosed in this
`reference.
`
`Yohe discloses that the remote client computer includes “means for performing an
`operation on data stored in the cache memory to produce a signature of the data.”
`(’943, 2:53-54).
`
`Yohe discloses that the remote client computer “includes a network file cacher
`(NFC) 42 which is operably disposed between and interconnects the FSI 26 and
`NFR 36. . . . The NFC 42 includes a block signature generator (BSG) 44.” (’943,
`
`15
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`4:66-5:5).
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`Yohe discloses that the receiver’s block signature generator (BSG 44) is capable of
`creating CRC or MD5 (’943, 13:36-39) hashes on data in the receiver’s cache.
`E.g., “In the case of a READ 108 requests, the computer 12 follows the operation
`300. Via the FSI 26 and LFS 28, the NFC 42 ‘determines if the requested data is in
`cache?’ 302. …. If the data is in cache, NFC 42 is triggered to ‘invoke’ 316 the
`BSG 44 to generate a signature of data. NFC 42 via NFR 36 and NTL 38 ‘sends’
`320 a VERIFY request having the first signature of data therein to CVA 54 which
`triggers 350.” (’943, 6:8-26).
`
`Yohe’s claims also describe this element: “a remote client computer having an
`operating system, a first memory, a cache memory and a processor with means for
`performing an operation on data stored in said cache memory to produce a
`signature of said data;” (’943, 14:53-57).
`
`“8. A method, performed by computers in a file oriented network for increased
`speed of access of data, which comprises:
`
`using a file server computer having an operating system, a first memory, a
`permanent storage memory and a processor;
`
`using a cache verifying computer operably connected to said file server
`computer in a manner to form a network for rapidly transferring data, said cache
`verifying computer having an operating system, a first memory and a processor;
`
`using a remote client computer having an operating system, a first memory,
`a cache memory and a processor,
`
`using a communication server operably connected to said remote client
`
`16
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`computer to said cache verifying computer and said file server computer;
`
`establishing a processor element in said cache verifying computer which
`recognizes a READ REQUEST and a DIRECTORY REQUEST by said remote
`client computer and obtains said data from said file server computer associated
`with one of a file and a directory and generates a signature of said data associated
`with of one of the file and the directory;
`
`establishing a processor element on said remote client computer which
`initiates upon one of a READ REQUEST and a DIRECTORY REQUEST from
`the cache memory to generate a signature of said data associated with of one of the
`file and the directory;
`
`using a first comparator operably associated with said cache verifying
`computer for comparing said signatures of data of the file with one another to
`determine whether said signature of data of the file of said remote client is valid;
`and
`using a second comparator operably associated with said remote client
`
`computer for comparing said signatures of data of the directory with one another to
`determine whether said signature of data of the directory of said remote client is
`valid.” (’943, 15:37-16:23).
`
`As this element apparently is construed by Proxyconn, this reference discloses it.
`
`The ’717 patent does not disclose or define sufficiently this element but to the
`extent that this element includes a processor configured to compare two
`cryptographic message digests or CRC values to determine whether they are the
`same or not, this reference discloses this element.
`
`“[T]he present invention is directed to an apparatus for increased data access in a
`
`17
`
` (iii) said receiver/computer
`including means for
`comparison between digital
`digests.
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`network, which includes a file server computer having a permanent storage
`memory, a cache verifying computer operably connected to the file server
`computer in a manner to form a network for rapidly transferring data, the cache
`verifying computer having an operating system, a first memory and a processor
`with means for performing an operation on data stored in the permanent storage
`memory of the file server computer to produce a signature of the data
`characteristic of one of a file and directory, a remote client computer having an
`operating system, a first memory, a cache memory and a processor with means for
`performing an operation on data stored in the cache memory to produce a signature
`of the data, a communication server operably connected to the remote client
`computer to the cache verifying computer and the file server computer and
`comparators operably associated with the cache verifying computer and remote
`client computer for comparing the signatures of data with one another to determine
`whether the signature of data of the remote client is valid.” (’943, 2:41-61).
`
`Yohe discloses that the remote client computer includes “comparators … for
`comparing the signatures of data with one another to determine whether the
`signature of data of the remote client is valid.” (’943, 2:58-61).
`
`“The NFC 42 has operatively associated therewith a directory cacher (DC) 43 and
`directory signature comparator (DSC) 46.” (’943, 5:1-3). In a step associated with
`the directory request primitive, “NFC 42 ‘invokes’ 722 DSC 46 to compare
`whether signature matches the retrieved signature in 729?” (’943, 8:9-11).
`
`If the result of the comparison is “no and the [directory] signature does not match,
`NFC 42 ‘invokes’ 724 NFR 36 to retrieve the first directory sub-object. NFC 42
`
`18
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`‘stores’ 725 the sub-object into cache via LFS 28. NFC 42 ‘asks’ 726 whether this
`is the last sub-object? If no and it is not the last sub-object, NFC 42 invokes NFR
`36 to ‘retrieve’ the next directory sub-object and returns to step 725. If yes and it is
`the last sub-object, NFC 42 ‘stores’ 728 the signature obtained via 721 or 711 into
`cache via LFS 28.” (’943, 8:13-21). Hence, the comparison associated with the
`directory request is done on the basis of the directory signature, and the retrieval of
`data is also based on the entire directory object.
`
`Yohe’s Abstract and claims also disclose this element: “An apparatus for
`increased data access in a network includes a file server computer having a
`permanent storage memory, a cache verifying computer operably connected to the
`file server computer in a manner to form a network for rapidly transferring data,
`the cache verifying computer having an operating system, a first memory and a
`processor with means for performing an operation on data stored in the permanent
`storage memory of the file server computer to produce a signature of the data
`characteristic of one of a file and directory, a remote client computer having an
`operating system, a first memory, a cache memory and a processor with means for
`performing an operation on data stored in the cache memory to produce a signature
`of the data, a communication server operably connected to the remote client
`computer to the cache verifying computer and the file server computer and
`comparators operably associated with the cache verifying computer and remote
`client computer for comparing the signatures of data with one another to determine
`whether the signature of data of the remote client is valid.” (’943, Abstract).
`
`“1. An apparatus for increased data access from one of a file and a directory in a
`file oriented network, which comprises:
`
`19
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`a file server computer having an operating system, a first memory, a
`
`permanent storage memory and a processor;
`
`a cache verifying computer operably connected to said file server computer
`in a manner to form a network for rapidly transferring data, said cache verifying
`computer having an operating system, a first memory and a processor with means
`for performing an operation on data stored in said permanent storage memory of
`said file server computer to produce a signature of said data from one of the file
`and the directory;
`
`a remote client computer having an operating system, a first memory, a
`cache memory and a processor with means for performing an operation on data
`stored in said cache memory to produce a signature of said data;
`
`a communication server operably connecting to said remote client computer
`to said cache verifying computer and said file server computer;
`
`a first comparator operably associated with said cache verifying computer
`for comparing said signatures of data of said file with one another to determine
`whether said signature of data of said file of said remote client is valid; and
`
`a second comparator operably associated with said remote client computer
`for comparing said signatures of said data of said directory with one another to
`determine whether said signature of data of said directory of said remote client is
`valid.” (’943, 14:40-15:3).
`
`“8. A method, performed by computers in a file oriented network for increased
`speed of access of data, which comprises:
`
`using a file server computer having an operating system, a first memory, a
`permanent storage memory and a processor;
`
`using a cache verifying computer operably connected to said file server
`
`20
`
`1 2 3 4 5 6 7 8 9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`

`
`Claim
`
`Reference
`
`SUPP. DEFS. INTERROG. RESP., EXHIBIT E
`USP 5,835,943, Yohe et al.
`Aug. 15, 2012
`
`
`computer in a manner to form a network for rapidly transferring data, said cache
`verifying computer having an operating system, a first memory and a processor;
`
`using a remote client computer having an operating system, a first memory,
`a cache memory and a processor,
`
`using a