Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 56 of 169
`
`PRIOR ART CLAIM CHART
`
`P 6,895/149's Claim Language
`
`DAS M~FG M
`
`Dependent Claim 6:
`6. An interface device in accordance with
`
`”The DASM—FGM captures Video
`data at 30 frames/sec from a wide
`
`claim 1 wherein, in response to a request from the
`host to read a boot sequence, the processor is
`arranged to send a virtual boot sequence to the host.
`
`Variety of NTSC/RS-170 or PAL-
`B/CCIR Video sources, and can
`
`store video frames in up to eight
`megabytes of buffer memory that
`appears to the host as a SCSI disk
`drive. Software applications
`communicate with the frame
`
`grabber using the host's existing
`SCSI facility.” DASM—FGM
`Brochure.
`
`”The DASM—FGM emulates a
`
`SCSI disk drive logically and
`physically." DASM—FGM
`Brochure.
`
`”The DASM—FGM contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully conforming to the
`SCSI Common Command Set."
`
`HUAWEI EX. 1002 - 1351/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 57 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`Dependent Claim 7:
`7. An interface device in accordance with
`
`claim 6 wherein the virtual boot sequence includes a
`starting position and a length of a file allocation table,
`an indication of a type of the storage device or a
`number of sectors of the storage device.
`
`Dependent Claim 8:
`8. An interface device in accordance with
`
`claim 7 wherein, in response to a request from the
`host to display a directory of the storage device, a
`processor is arranged for transferring the file
`allocation table and the directory structure to the host.
`
`Dependent Claim 9:
`9. An interface device in accordance with
`claim 1 wherein the file allocation table and the
`
`directory structure is transferred to the host in
`response to a request from the host to read data from
`or store data to the storage device.
`
`DAS M~FG M
`
`DASM-FGM Brochure.
`
`”The DASM-FGM contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully conforming to the
`SCSI Common Command Set.
`
`Image memory is segmented into
`SCSI—defined 512-byte blocks and
`is used for image storage as well
`as command and status
`
`handshaking with the host
`application. The host sends
`commands, receives status, and
`
`reads or loads images by
`accessing the appropriate blocks
`in the DASM-FGM image
`memory using the host's existing
`SCSI facility.” DASM-FGM
`Brochure.
`
`See above, ‘449 claim 6, row N*8.
`
`See above ‘449 claim 6, row N*8.
`
`”The DASM-FGM captures video
`data at 30 frames/sec from a wide
`
`variety of NTSC/RS-I70 or PAL-
`B/CCIR video sources, and can
`
`store video frames in up to eight
`megabytes of buffer memory that
`appears to the host as a SCSI disk
`drive. Software applications
`communicate with the frame
`
`grabber using the host‘s existing
`SCSI facility.” DASM-FGM
`Brochure.
`
`HUAWEI EX. 1002 - 1352/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 58 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`DASM~FGM
`”The DASM—FGM emulates a
`
`SCSI disk drive logically and
`physically." DASM—FGM
`Brochure.
`
`”The DASM—FGM contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully conforming to the
`SCSI Common Command Set.”
`DASM—FGM Brochure.
`
`”The DASM—FGM contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully conforming to the
`SCSI Common Command Set.
`
`Image memory is segmented into
`SCSI—defined 512-byte blocks and
`is used for image storage as well
`as command and status
`
`handshaking with the host
`application. The host sends
`commands, receives status, and
`
`reads or loads images by
`accessing the appropriate blocks
`in the DASM—FGM image
`memory using the host's existing
`SCSI facility.” DASM—FGM
`Brochure.
`
`HUAWEI EX. 1002 - 1353/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 59 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`DAS M~FG M
`
`Dependent Claim 12
`12. An interface device in accordance with
`claim 1 wherein the file allocation table includes
`
`information on numbers of blocks occupied by the
`data file wherein the interface device is arranged for
`receiving block numbers or a block number range
`from the host when the host wants to read the data
`
`file, and wherein the interface device is arranged to
`start a data transfer to the host, when the block
`
`numbers or the block number range is received from
`the host.
`
`”The DASM-FGM captures video
`data at 30 frames/sec from a wide
`
`variety of NTSC/RS-170 or PAL-
`B/CCIR video sources, and can
`
`store video frames in up to eight
`megabytes of buffer memory that
`appears to the host as a SCSI disk
`drive. Software applications
`communicate with the frame
`
`grabber using the host's existing
`SCSI facility.” DASM-FGM
`Brochure.
`
`”The DASM-FGM emulates a
`
`SCSI disk drive logically and
`physically." DASM-FGM
`Brochure.
`
`”The DASM-FGM contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully conforming to the
`SCSI Common Command Set."
`DASM-FGM Brochure.
`
`”The DASM-FGM contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully Conforming to the
`SCSI Common Command Set.
`
`Image memory is segmented into
`SCSI-defined 512-byte blocks and
`is used for image storage as well
`as command and status
`
`handshaking with the host
`application. The host sends
`commands, receives status, and
`
`reads or loads images by
`
`HUAWEI EX. 1002 - 1354/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 60 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`DAS M~FG M
`
`accessing the appropriate blocks
`in the DASM—FGM image
`memory using the host's existing
`SCSI facility.” DASM—FGM
`Brochure.
`
`Dependent Claim 13:
`13. An interface device in accordance with
`
`”The DASM—FGM captures video
`data at 30 frames/sec from a wide
`
`claim 12 wherein the processor is arranged for
`formatting the data acquired by the second connecting
`device into blocks having a predetermined size, the
`predetermined size being suited for the storage
`device.
`
`variety of NTSC/RS-I70 or PAL-
`B/CCIR video sources, and can
`
`store video frames in up to eight
`megabytes of buffer memory that
`appears to the host as a SCSI disk
`drive. Software applications
`communicate with the frame
`
`grabber using the host‘s existing
`SCSI facility.” DASM—FGM
`Brochure.
`
`”The DASM—FGM emulates a
`
`SCSI disk drive logically and
`physically.” DASM—FGM
`Brochure.
`
`”The DASM—FGM contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully conforming to the
`SCSI Common Command Set.”
`DASM—FGM Brochure.
`
`”The DASM—FGM Contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully conforming to the
`SCSI Common Command Set.
`
`Image memory is segmented into
`SCSI—defined 512—byte blocks and
`is used for image storage as well
`as command and status
`
`handshaking with the host
`application. The host sends
`commands, receives status, and
`
`reads or loads images by
`accessing the appropriate blocks
`in the DASM—FGM ima e
`
`HUAWEI EX. 1002 - 1355/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 61 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`DASM~FGM
`
`memory using the host's existing
`SCSI facility.” DASM—FGM
`Brochure.
`
`""i5}{e;{a;1{t ¢1;....;1a
`15. An interface device in accordance with
`claim 1 wherein the storage device is a hard disk.
`
`tag; 1j2$;éi§’4§i%&§i\ZE;;1§£L;}§;‘ Vida;
`data at 30 frames/sec from '3 Wide
`Variety Of NTSC/R5470 Or PAL‘
`B/CCIR video sources, and can
`
`store video frames in up to eight
`megabytes of buffer memory that
`appears to the host as a SCSI disk
`drive. Software applications
`communicate with the frame
`
`grabber using the host's existing
`SCSI facility.” DASM—FGM
`Brochure.
`
`”The DASM—FGM emulates a
`
`SCSI disk drive logically and
`physically." DASM—FGM
`Brochure.
`
`HUAWEI EX. 1002 - 1356/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 62 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`DASM~FGM
`”The DASM-FGM Contains from
`
`256 KBytes to 8 MBytes of on-
`board image memory that
`appears to the host as a SCSI disk
`drive fully Conforming to the
`SCSI Common Command Set."
`DASM-FGM Brochure.
`
`Dependent Claim 16:
`6. An interface device in accordance with
`
`See ‘399 claim 3, row E*.
`
`claim 1 wherein the memory has a data buffer for
`permitting independence in terms of time of the data
`transmit/receive device attachable to the second
`
`connecting device from the host device attachable to
`the first connecting device.
`
`CH01/256273231
`
`HUAWEI EX. 1002 - 1357/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 63 of 169
`
`Exhibit A92
`
`HUAWEI EX. 1002 - 1358/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 64 of 169
`
`PRIOR ART CLAIM CHART
`
`Reference: “Cheops: A Reconfigurable Data-Flow System for Video Processing”, V. M. Bove,
`Jr., J. A. Watlington, IEEE Trans. Circ. Sys. Video Tech. Vol.5, No. 2, April 1995, p.140-149.1
`
`Code
`
`USP 6,470,399’s Claim Language
`
`Independent Claim 1:
`1. An interface device for communication between
`
`a host device, which comprises drivers for
`input/output devices customary in a host device and a
`multi-purpose interface, and
`
`a data transmit/receive device,
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`E.g., (”Reasonably inexpensive
`adlunct to 3 Workstafion - -H) P-
`141, Right; FIG. 1
`
`The workstation. E.g.,
`("Reasonably inexpensive
`adjunct to a worl<station...”) p.
`141, Right; FIG. 1.
`("Analog or digital video in”)
`FIG. 1, and accompanying
`description. This input reflects
`that a number of dissimilar
`
`analog or digital devices can be
`connected to the interface device.
`
`the data transmit/receive device being arranged for
`providing analog data, comprising:
`
`See '399 claim 1, row C.
`
`a processor;
`
`a memory;
`
`("[M]ultiple stream
`processors. . .,” ”Cheops allows
`for three different module types,
`processor, input/memory and
`output”) p. 141, Right; FIGS. 1, 2
`and 3.
`
`("[M]ultiple stream
`processors. . .,” "Cheops allows
`for three different module types,
`processor, input/memory and
`output.”) p. 141, Right; FIGS. 1, 2
`and 3.
`
`1 For similar and supporting disclosures, see also “A Field Programmable Gate Array Based Stream Processor for
`the Cheops Imaging System”, R.A. Yu, master thesis, MIT, August l6, 1996. This is an additional publication
`regarding the Cheops system, and it would therefore have been readily apparent and obvious to one skilled in the art
`that the two Cheops articles could be combined.
`
`In addition, the Cheops reference(s) can be combined with the The SCSI Bus and IDE Interface Book (Friedhelm
`Schmidt, 1995) to render obvious each of the asserted patent claims. (Sec claim chart for The SCSI Bus and IDE
`Interface Book for the teachings that could be combined With Cheops for any given claim limitation.) One skilled in
`the art would have been motivated to combine these references because they both involve SCSI interfacing and
`SCSI command sets. Further, the general similarity of technology of the references would have motivated one
`skilled in the art to combine the references.
`
`\\ \LA - 088570/000200 - 386026 v3
`
`1
`
`HUAWEI EX. 1002 - 1359/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 65 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`a first connecting device for interfacing the
`host device with the interface device via the multi-
`
`purpose interface of the host device; and
`
`a second connecting device for interfacing the
`interface device with the data transmit/receive device,
`
`the second connecting device including
`
`a sampling circuit for sampling the analog
`data provided by the data transmit/receive device and
`
`\\ \LA - 088570/000200 - 386026 V3
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`E.g.: (”Host Connect
`(SCSI/RS232)”) FIG. 1; (”The
`
`processor module communicates
`with the host computer using the
`SCSI (Small Computer Systems
`Interface) bus.") p. 143, Left;
`("Two RS-232 ports are available,
`one for debugging and
`diagnostics and the other for user
`interface devices such as serial
`
`knob boxes, mice or touch
`
`sensitive screens. If only a low-
`bandwidth host device interface
`
`is desired , one of the ports may
`substitute for the SCSI
`
`p. 143, Left; (”A
`Cheops system acts as a
`peripheral to one of a variety of
`host computers.”) p.144, Right.
`
`E.g.: ("Analog/Digital Video in”)
`FIG. 1; (’’Two RS-232 ports are
`available one for debugging and
`diagnostics and the other for user
`interface devices such as serial
`knob boxes mice or touch
`
`p. 143, Left;
`
`("The memory input
`module. . .allows a single remote
`device, located on a daughter
`card. . .We have built a high-
`5peed (I-liPI’l) daughter card, and
`are developing another which
`accepts various analog and
`digital video formats." p. 144,
`Left
`
`See G above.
`
`(”On the Nile Buses, image data
`(pixels) being transferred to or
`from an I O device are
`
`represented as three
`independent 8—b component
`channels packed into a 24—b
`word. ...Internal to a
`rocessin;
`
`HUAWEI EX. 1002 - 1360/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 66 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`module, component channels are
`stored independently, using a 16-
`b, fixed point, signed two's
`complement representation
`referred to hereafter as a
`
`sample.” p. 142, left; (”EaCh
`memory unit is made up of dual
`ported dynamic memory
`(VRAM) and a two-dimensional
`
`direct memory access (DMA)
`controller for transferring a
`stream of data through the
`crosspoint at up to 40 M
`sample[s.”) p. 142, left;
`("[F]ractional sampling rate
`conversion can be performed in a
`single transfer through a filter
`stream processor/’) p. 142, Right.
`
`Further, to the extent that Cheops
`alone does not anticipate or
`render obvious the " sampling
`circuit" limitation of the asserted
`
`claims of the '399 patent, the
`limitation would be obvious
`
`when combining Cheops with
`The SCSI Bus and IDE Interface
`
`Book (Friedhelm Schmidt,
`1995). One skilled in the art
`would have been motivated to
`combine these references because
`
`they both involve SCSI
`interfacing and SCSI command
`sets. Further, the general
`similarity of technology of the
`references would have motivated
`one skilled in the art to combine
`the references.
`
`Similarly, to the extent that
`Cheops alone does not anticipate
`or render obvious the "sampling
`circuit" limitation of the asserted
`
`claims of the '399 patent, the
`limitation would be obvious
`
`\\ \LA - 088570/000200 - 386026 v3
`
`HUAWEI EX. 1002 - 1361/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 67 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`an analog-to-digital converter for converting
`data sampled by the sampling circuit into digital data,
`
`wherein the interface device is configured by
`the processor and the memory
`
`\\ \LA - 088570/000200 - 386026 v3
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`when combining
`the Cheops with the textbook by
`Kenneth Short, Microprocessors
`and Programmed Logic,
`Prentice-Hall, Inc., 1981, pp. 424-
`426 ("Microprocessor and
`Programmed Logic"). One
`skilled in the art would have
`been motivated to combine these
`
`references because the Cheops
`discloses using an A/D converter,
`and Microprocessors and
`Programmed Logic teaches using
`a sample and hold circuit with an
`A/D converter. The general
`similarity of technology of the
`references would have motivated
`one skilled in the art to combine
`the references.
`
`See G and G1 above.
`
`Further, to the extent that Cheops
`alone does not anticipate or
`render obvious the "analog-to-
`digital converter " limitation of
`the asserted claims of the '399
`
`patent, the limitation would be
`obvious when combining
`Cheops with The SCSI Bus and
`IDE Interface Book (Friedhelm
`Schmidt, 1995). One skilled in
`the art would have been
`motivated to combine these
`
`references because they both
`involve SCSI interfacing and
`SCSI command sets. Further, the
`
`general similarity of technology
`of the references would have
`motivated one skilled in the art
`to combine the references.
`
`See F above; FIG. 3 — Block
`
`diagram of a typical stream
`processor (includes Static RAM).
`
`HUAWEI EX. 1002 - 1362/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 68 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`to include a first command interpreter and a
`second command interpreter,
`
`wherein the first command interpreter is
`configured in such a way that the command
`interpreter, when receiving an inquiry from the host
`device as to a type of a device attached to the multi-
`purpose interface of the host device
`
`sends a signal, regardless of the type of the
`data transmit/receive device attached to the second
`
`connecting device of the interface device, to the host
`device
`
`which signals to the host device that it is an
`input/output device customary in a host device
`
`whereupon the host device communicates
`with the interface device by means of the driver for
`the input/output device customary in a host device,
`and
`
`wherein the second command interpreter is
`configured to interpret a data request command from
`the host device to the type of input/output device
`signaled by the first command interpreter as a data
`transfer command for initiating a transfer of the
`digital data to the host device.
`
`Independent claim 11:
`11. An interface device for communication between
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`Inherently disclosed in the
`operation as a SCSI client. See F
`above; (”Cheops is solely a target
`device on the SCSI bus.. .”) p.
`144, Left
`
`Inherent disclosed as a SCSI
`
`target. See H1 above.
`
`Inherent disclosed as a SCSI
`
`target. See H1 above.
`
`E.g.: (”Each processor module
`appears as a fixed disk
`device. . .”) p. 143, Left
`
`E.g.: (”[I]n most cases no special
`host device driver is needed/’) p.
`143, Left
`
`Inherent in the use of SCSI
`standard for communication
`
`between the host and Cheops
`system. See, e.g.: p. 143, Left
`
`See ’399 claim 1, row A.
`
`\\ \LA - 088570/000200 - 386026 v3
`
`HUAWEI EX. 1002 - 1363/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 69 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`a host device, which comprises a multi-
`purpose interface and a specific driver for this
`interface, and
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`E.g.: (”The processor module
`communicates with the host
`com uter usin the SCSI Small
`
`Computer Svstems Interface)
`bus. Each processor module
`appears as a fixed disk device,
`therefore in most cases no special
`host device driver is needed.
`
`Cheops systems have proven to
`be compatible with existing
`UNIX disk device drivers on
`
`DECStations, SunSPARCStations,
`
`IBM RS/6000 systems, and Silicon
`Graphics workstations. Two RS-
`232 ports are available, one for
`debugging and diagnostics and
`the other for user interface
`
`devices such as serial knob boxes,
`mice or touch sensitive screens.
`
`If only a low-bandwidth host
`device interface is desired , o_ne
`
`of the ports may substitute for
`the SCSI connection." p. 143,
`Left.
`
`a data transmit/rcccivc dcvicc
`
`See '399 claim 1, row C.
`
`the data transmit/receive device being
`arranged for providing analog data, comprising:
`
`See ‘399 claim 1, row C1.
`
`a processor;
`
`a memory;
`
`a first connecting device for interfacing the
`host device with the interface device via the multi-
`
`purpose interface of the host device; and
`
`See ‘399 claim 1, row D.
`
`See ’399 claim 1, row E.
`
`See ‘399 claim 1, row F.
`
`a second connecting device for interfacing
`the interface device with the data transmit/receive
`
`See ‘399 claim 1, row G.
`
`device, the second connecting device including
`
`a sampling circuit for sampling the analog
`data provided by the data transmit/receive device
`and
`
`an analog-to-digital converter for converting
`data sampled by the sampling circuit into digital
`data,
`
`See ‘399 claim 1, row G1.
`
`See ‘399 claim 1, row G2.
`
`\\ \LA - 088570/000200 - 386026 v3
`
`HUAWEI EX. 1002 - 1364/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 70 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`where the interface device is configured
`using the processor and the memory
`
`to include a first command interpreter and a
`second command interpreter,
`
`wherein the first command interpreter is
`configured in such a way that the interface device,
`when receiving an inquiry from the host device as to
`the type of a device attached at the multi-purpose
`interface of the host device
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`See '399 claim 1, row H.
`
`See '39,‘) claim 1, row l-ll.
`
`See ’399 claim 1, row 1.
`
`sends a signal, regardless of the type of the
`data transmit/receive device attached to the second
`
`See '399 claim 1, row I.
`
`connecting device of the interface device, to the host
`device,
`
`which signals to the host device that it is an
`input/output device customary in a host device,
`
`whereupon the host device communicates
`with the interface device by means of the specific
`driver for the multi-purpose interface, and
`
`wherein the second command interpreter is
`configured to interpret a data request command
`from the host device to the type of input/output
`device signaled by the first command interpreter as
`a data transfer command for initiating a transfer of
`the digital data to the host device.
`
`Independent Claim 14:
`14. A method of communication between
`
`a host device, which comprises drivers for
`input/output devices customary in a host device and a
`multi—purpose interface, and
`
`a data transmit/receive device
`
`the data transmit/receive device being
`arranged for providing analog data, Via an interface
`device, comprising:
`
`interfacing of the host device with a first
`connecting device of the interface device via the
`multi-purpose interface of the host device;
`
`interfacing of the data transmit/receive device
`with a second connecting device of the interface
`device, the second connecting device including
`
`a sampling circuit for sampling the analog
`data provided by the data/transmit/receive device and
`
`See ’399 claim 1, row K1.
`
`See '399 claim 1, row M.
`
`See ’399 claim 1, row A.
`
`See '399 claim 1, row B1
`
`See '399 claim 1, row C.
`
`See '399 claim 1, row C1.
`
`See ’399 claim 1, row F.
`
`See '399 claim 1, row G.
`
`See '399 claim 1, row G1.
`
`\\ \LA - 088570/000200 - 386026 V3
`
`HUAWEI EX. 1002 - 1365/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 71 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`an analog-to-digital converter for converting
`data sampled by the sampling circuit into digital data;
`
`inquiring by the host device at the interface
`device as to the type of device to which the multi-
`purpose interface of the host device is attached;
`
`regardless of the type of the data
`transmit/receive data attached to the second
`
`connecting device of the interface device, responding
`to the inquiry from the host device by the interface
`device
`
`in such a way that it is an input/output device
`customary in a host device,
`
`whereupon the host device communicates
`with the interface device by means of the usual driver
`for the input/output device, and
`
`interpreting a data request command from the
`host device to the type of input/output device
`customary in the host device as a data transfer
`command for initiating a transfer of the digital data to
`the host device.
`
`Dependent Claim 2:
`
`2. An interface device according to claim 1,
`wherein the drivers for input/output drivers
`customary in a host device comprise a hard disk
`driver, and the signal indicates to the host device that
`the host device is communicating with a hard disk.
`
`Dependent Claim 3:
`
`3. An interface device according to claim 1,
`wherein the memory means comprises a buffer to
`buffer data to be transferred between the data
`
`transmit/receive device and the host device.
`
`Dependent Claim 5:
`
`5. An interface device according to claim 1,
`wherein the processor is a digital signal processor.
`
`\\ \LA - 088570/000200 - 386026 v3
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`See '399 claim 1, row G2.
`
`See '399 claim 1, row I.
`
`See ’399 claim 1, row I.
`
`See ’399 claim 1, row K1.
`
`See ’399 claim 1, row L1.
`
`See '399 claim 1, row M.
`
`E.g.: (”The processor module
`communicates with the host
`
`computer using the SCSI (Small
`Computer Systems lnterface)
`bus. Each processor module
`appears as a fixed disk device,
`therefore in most cases no special
`host device driver is needed.”) p.
`143, Left.
`
`E.g.: (”[I]f the delay between
`input and output is very long
`and the processor can itself hold
`an entire transfer’s worth of data
`
`the processor operates in a two-
`state fashion...”) p. 143, Left;
`("[B]uffers larger than 256x256
`must thus be tiled...”) p. 143,
`Right
`
`Each stream processor is a digital
`signal processor, p. 143.
`
`HUAWEI EX. 1002 - 1366/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 72 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,4’70,399’s Claim Language
`
`Cheops: A Reconfigurable Data-
`-Flow System for Video
`Processing
`
`E.g.: (”Along the way it [Cheops]
`Dependent Claim 7:
`has become a neatly Complete
`7. An interface device according to claim 2,
`which further comprises a root directory and virtual Watkstatto“ 1" ‘ts OW" ttgtatr Wtttt
`files which are present on the signaled hard disk drive
`the ttmttatton that 1t d0e5 not
`and which can be accessed from the host device.
`maintain its OW“ tile System but
`(transparently to the
`programmer) depends on the file
`system of its host computer.”) p.
`141, Right.
`
`Dependent Claim 15:
`
`See ’399 claim 1, row B*1.
`
`15. A method according to claim 14, wherein
`the drivers for input/output devices customary in a
`host device comprise a driver for a storage device and
`in particular for a hard disk drive.
`
`\\ \LA - 088570/000200 - 386026 v3
`
`HUAWEI EX. 1002 - 1367/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 73 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895,449’s Claim Language
`
`Independent Claim 1:
`1. An interface device for communication between
`
`a host device, which comprises drivers for
`input/output devices customary in a host device and a
`multi-purpose interface, and
`
`a data transmit/receive device comprising the
`following features:
`
`61 PFOCESSOI,‘
`
`a memory;
`
`a first connecting device for interfacing the
`host device with the interface device via the multi-
`
`purpose interface of the host device; and
`
`a second connecting device for interfacing the
`interface device with the data transmit/receive device,
`
`wherein the interface device is configured by
`the processor and the memory
`
`in such a way that the interface device, when
`receiving an inquiry from the host device as to the
`type of a device attached to the multi-purpose
`interface of the host device,
`
`sends a signal, regardless of the type of the
`data transmit/receive device attached to the second
`
`connecting device of the interface device, to the host
`device
`
`which signals to the host device that it is a
`storage device customary in a host device,
`
`whereupon the host device communicates
`with the interface device by means of the driver for
`the storage device customary in a host device, and
`
`wherein the interface device is arranged for
`simulating a virtual file system to the host, the virtual
`file system including a directory structure.
`
`Prior Art Reference
`
`See ’399 claim 1, row A.
`
`See ’399 claim 1, row B1.
`
`See ’399 claim 1, row C.
`
`See ’399 claim 1, row D.
`
`See '399 claim 1, row E.
`
`See ’399 claim 1, row F.
`
`See '399 claim 1, row G.
`
`See '399 claim 1, row H.
`
`See ’399 claim 1, row I.
`
`See '399 claim 1, row I.
`
`Inherent disclosed. E.g.: ("Each
`processor module appears as a
`fixed disk device.. .") p. 143, Left
`
`Inherent disclosed. E.g.:
`("[T]herefore in most cases no
`
`special host device driver is
`needed...”) p. 143, Left
`
`E.g.: (”Along the way it
`[Cheops] has become a nearly
`complete workstation in its own
`right, with the limitation that it
`does not maintain its own file
`
`system but (transparently to the
`programmer) depends on the file
`system of its host computer.”) p.
`141, Right.
`
`\\ \LA - 088570/000200 - 386026 v3
`
`HUAWEI EX. 1002 - 1368/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 74 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`Independent claim 17:
`17. An interface device for communication between
`
`a host device, which comprises a multi-
`purpose interface and a specific driver for this
`interface,
`and a data transmit/receive device
`
`comprising the following features:
`
`El pI'OCCSSOI';
`
`a memory;
`
`a first connecting device for interfacing the
`host device with the interface device via the multi-
`
`purpose interface of the host device; and
`
`a second connecting device for interfacing
`the interface device with the data transmit/receive
`
`device,
`
`where the interface device is configured
`using the processor and the memory
`
`in such a way that the interface device, when
`receiving an inquiry from the host device as to the
`type of a device attached at the multi—purpose
`interface of the host device,
`
`Prior Art Reference
`
`See ’399 Claim 1, row A.
`
`See ’399 Claim 11, row B2.
`
`See ’399 Claim 1, row C.
`
`See '399 claim 1, row D.
`
`See ’399 Claim 1, row E.
`
`See ’399 claim 1, row F.
`
`See ’399 Claim 1, row G.
`
`See ’399 claim 1, row H.
`
`See ’399 Claim 1, row I.
`
`sends a signal, regardless of the type of the
`data transmit/receive device attached to the second
`
`See ’399 claim 1, row I.
`
`connecting device of the interface device, to the host
`device
`
`which signals to the host device that it is a
`storage device customary in a host device,
`
`whereupon the host device communicates
`with the interface device by means of the specific
`driver for the multi-purpose interface, and
`
`wherein the interface device is arranged for
`simulating a virtual file system to the host, the
`virtual file system including a file allocation table
`and a directory structure.
`
`See ’449 Claim 1, row K2.
`
`See ’399 Claim 11, row L3.
`
`See ’399 Claim 1, N*1.
`
`\\ \LA - 088570/000200 - 386026 V3
`
`HUAWEI EX. 1002 - 1369/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11
`
`Page 75 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895,449’s Claim Language
`
`Independent Claim 18:
`18. A method of communication between
`
`a host device, which comprises drivers for
`input/output devices customary in a host device and a
`multi—purpose interface,
`
`Prior Art Reference
`
`See ’399 claim 1, row A.
`
`See ’399 claim 1, row B1.
`
`and a data transmit/receive device via an
`
`See ’399 claim 1, row C.
`
`See ’399 Claim 1, row F.
`
`See ’399 claim 1, row G.
`
`See '399 claim 1, row I.
`
`See ’399 claim 1, row I.
`
`See ’449 claim 1, row K2.
`
`See ’449 claim 1, row L2.
`
`See ’449 claim 17, row N2.
`
`interface device comprising the following steps:
`
`interfacing of the host device with a first
`connecting device of the interface device via the
`multi-purpose interface of the host device;
`
`interfacing of the data transmit/receive device
`with a second connecting device of the interface
`device;
`
`inquiring by the host device at the interface
`device as to the type of device to which the multi-
`purpose interface of the host device is attached;
`
`regardless of the type of the data
`transmit/receive device attached to the second
`
`connecting device of the interface device, responding
`to the inquiry from the host device by the interface
`device
`
`in such a way that it is a storage device
`customary in a host device,
`
`whereupon the host device communicates
`with the interface device by means of the usual driver
`for the storage device, and
`
`wherein the interface device is arranged for
`simulating a virtual file system to the host, the virtual
`file system including a file allocation table and a
`directory structure.
`
`Dependent Claim 2:
`2. An interface device in accordance with
`
`claim 1, in which the directory structure has a
`configuration file for setting and controlling functions
`of the interface device or an executable or a batch file
`
`for conducting a routine stored in the memory or a
`data file used for transferring data from the data
`transmit/receive device to the host device or a help file
`for giving help on handling the interface device.
`
`\\ \LA - 088570/000200 - 386026 v3
`
`HUAWEI EX. 1002 - 1370/2201
`
`

`
`Case 1:07-mc-00493-RMC Document 414-7
`
`Filed 01/20/11 Page 76 of 169
`
`PRIOR ART CLAIM CHART
`
`USP 6,895/149's Claim Language
`
`Prior Art Reference
`
`Dependent Claim 6:
`6. An interface device in accordance with
`
`claim 1 wherein, in response to a request from the
`host to read a boot sequence, the processor is