throbber

`
`Paper No.
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_____________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_____________________
`
`
`
`
`
`APPLE INC., HTC CORPORATION, AND HTC AMERICA INC.,
`Petitioners,
`
`v.
`
`PARTHENON UNIFIED MEMORY ARCHITECTURE LLC,
`Patent Owner
`
`_____________________
`
`
`
`Case IPR2016-00923
`Patent No. 5,812,789
`
`_____________________
`
`
`
`PETITIONER’S REPLY
`
`
`
`

`

`
`
`
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`
`
`
`
`
`TABLE OF CONTENTS
`
`I.
`
`II.
`
`Introduction ...................................................................................................... 1
`
`Lambrecht anticipates each and every limitation recited in
`claims 1, 3, 5, 11, and 13. ................................................................................ 2
`
`A.
`
`Lambrecht anticipates “a shared bus . . . having a
`sufficient bandwidth to enable the decoder to access the
`memory and operate in real time.” ........................................................ 3
`
`1.
`
`2.
`
`in Fig. 21 of Lambrecht
`The PCI bus
`communicates data between the memory and the
`multimedia devices when in the multimedia mode. ................... 3
`
`No additional logic is needed in the PCI bridge
`chipset in Fig. 21 for the multimedia devices
`communicate data
`to
`the main memory
`in
`multimedia mode.......................................................................12
`
`Lambrecht anticipates “a decoder that requires access to
`the memory sufficient to maintain real time operation.” ....................14
`
`Lambrecht anticipates “a shared bus . . . having sufficient
`bandwidth to enable the decoder to access the memory
`and operate in real time.” ....................................................................17
`
`Lambrecht anticipates “the bus having a sufficient
`bandwidth to enable the decoder to access the memory
`and operate
`in real
`time when
`the first device
`simultaneously accesses the bus.” .......................................................20
`
`B.
`
`C.
`
`D.
`
`III. The combination of Lambrecht and Artieri renders claim 4
`obvious. ..........................................................................................................22
`
`IV. The combination of Lambrecht and Moore renders claim 6
`obvious. ..........................................................................................................23
`
`V.
`
`Conclusion .....................................................................................................24
`
`VI. Certificate of Word Count .............................................................................25
`
`
`
`i
`
`

`

`
`
`
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`PETITIONER’S UPDATED EXHIBIT LIST
`
`
`
`
`
`February 24, 2017
`
`Description
`Exhibit
`Ex. 1001 U.S. Patent No. 5,812,789 (“the ’789 patent”)
`Ex. 1002 File History for U.S. Patent No. 5,812,789
`Ex. 1003 Reserved
`Ex. 1004
`ISO/IEC 11172-2: 1993: Information technology—Coding of moving
`pictures and associated audio for digital storage media at up to about
`1,5 Mbit/s—Part 2: Video, (1st ed. August 1, 1993) (“MPEG
`Standard”)
`Ex. 1005 S. Rathnam et al., “An Architectural Overview of the Programmable
`Multimedia Processor, TM-1,” IEEE Proceedings of COMPCON ’96,
`pp. 319-326 (1996) (“Rathnam”)
`Ex. 1006 R.J. Gove, “The MVP: A Highly-Integrated Video Compression
`Chip,” Proceedings of the IEEE Data Compression Conference (DCC
`’94), pp. 215-224 (March 29-31, 1994)
`Ex. 1007 U.S. Patent No. 5,774,676 (“Stearns”)
`Ex. 1008 Reserved
`Ex. 1009 Reserved
`Ex. 1010 WorldCat Entry for Rathnam
`Ex. 1011 Patent Owner Claim Construction Brief in Case No. 2: 14-cv-690,
`April 7, 2015
`Ex. 1012 Patent Owner Claim Construction Brief in Case No. 2: 14-cv-902, June
`18, 2015
`Ex. 1013 Reserved
`Ex. 1014 Brad Hansen, The Dictionary of Multimedia, 1997
`Ex. 1015 U.S. Patent No. 8,681,164
`Ex. 1016 Excerpt of File History for U.S. Patent No. 8,681,164
`Ex. 1017 Reserved
`
`
`
`ii
`
`

`

`
`
`
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`
`
`
`
`
`Description
`
`Exhibit
`Ex. 1018 Reserved
`Ex. 1019 Shanley, et al., “PCI System Architecture,”’ Addison-Wesley
`Publishing Company, 1995 (3rd ed.) (“Shanley”)
`Ex. 1020 Stone, H., “Microcomputer Interfacing,” Addison-Wesley Publishing
`Company, 1982
`Ex. 1021 Reserved
`Ex. 1022 Reserved
`Ex. 1023 U.S. Patent No. 5,797,028 (“Gulick 028”)
`Ex. 1024
`“Accelerated Graphics Port Interface Specification,” Intel Corporation,
`July 31, 1996 (Revision 1.0) (“AGP”)
`Ex. 1025 VESA Unified Memory Architecture Hardware Specifications
`Proposal, Version 1.0p (“VUMA”)
`Ex. 1026 Reserved
`Ex. 1027 Reserved
`Ex. 1028 Reserved
`Ex. 1029 Curriculum Vitae of Dr. Harold Stone
`Ex. 1030 Expert Declaration of Dr. Harold Stone (“Stone Decl.”)
`Ex. 1031 Reserved
`Ex. 1032 U.S. Patent No. 5,682,484 (“Lambrecht”)
`Ex. 1033 Reserved
`Ex. 1034 Slavenburg, G., “The TriMedia VLIW-Based PCI Multimedia
`Processor,” Microprocessor Forum 1995, Oct. 10-11, 1995
`(“Slavenburg”)
`Ex. 1035 G. Moore, “Cramming more components onto integrated circuits,”
`Electronics, Vol. 38, No. 8, Apr. 19, 1965 (“Moore”)
`Ex. 1036 U.S. Patent No. 5,579,052 (“Artieri”)
`Ex. 1037 Reserved
`Ex. 1038 Reserved
`Ex. 1039 Reserved
`
`
`
`iii
`
`

`

`
`
`
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`
`
`
`
`
`Description
`
`Exhibit
`Ex. 1040 Reserved
`Ex. 1041 Declaration of Curt Holbreich in Support of Motion for Pro Hac Vice
`Admission
`Ex. 1042 Declaration of Yakov Zolotorev in Support of Motion for Pro Hac
`Vice Admission
`Ex. 1043 Deposition Transcript of Dr. Mitchell A. Thornton
`Ex. 1044 Second Expert Declaration of Harold S. Stone, Ph.D.
`Ex. 1045 U.S. Patent No. 5,461,679 (“Normile”)
`Ex. 1046 Errata sheet for Deposition of Dr. Stone included as Ex. 2004
`
`
`
`iv
`
`

`

`
`
`
`Introduction
`
`I.
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`
`
`
`
`
`The Petition and the record as a whole provides detailed reasons why a
`
`person of skill in the art (“POSITA”) would have understood Lambrecht to either
`
`anticipate or render obvious (in combination) each and every limitation of the
`
`challenged claims of the ’789 patent. None of Patent Owner’s arguments overcome
`
`the express teachings of Lambrecht.
`
`Patent Owner’s primary argument is that the PCI bus in Lambrecht’s Fig. 21
`
`is not capable of communicating data between the multimedia devices (including a
`
`decoder) and the main system memory. This argument, though, is predicated on
`
`misunderstandings regarding the express teachings of Lambrecht and the state of
`
`the art at the time of the ’789 patent.
`
`First, Patent Owner attempts to impose limitations on the teachings of Fig.
`
`21 by importing characteristics described in other, distinct embodiments into the
`
`disclosures related to Fig. 21. But, as discussed below, Patent Owner
`
`misapprehends the teachings and disclosures of Lambrecht, while simultaneously
`
`rendering the teachings with respect Fig 21 redundant and nonsensical.
`
`Second, Patent Owner argues that the chipset that communicates with the
`
`PCI bus in Lambrecht’s Fig. 21 would require additional, special circuitry to
`
`operate. But, as discussed below, such argument contradicts the teachings in
`
`Lambrecht. No such special circuitry is required.
`
`
`
`1
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`Third, Patent Owner incorrectly argues that the video decoder disclosed in
`
`
`
`
`
`
`
`Lambrecht would not access the main memory because, at the time of Lambrecht,
`
`all video decoders included dedicated memory. As discussed below, this is a
`
`misunderstanding of the state of the art—POSITAs at the time knew that video
`
`decoders could directly access the main memory instead of requiring dedicated
`
`memory.
`
`Finally, Patent Owner raises other arguments regarding the whether the
`
`system in Lambrecht has sufficient bandwidth to maintain realtime operation and
`
`whether multimedia devices can use the shared bus simultaneously. Both of these
`
`arguments are incorrect as they fail to properly consider the teachings of
`
`Lambrecht and the knowledge of a POSITA.
`
`In sum, Patent Owner’s arguments are unpersuasive. Lambrecht anticipates
`
`claims 1, 3, 5, 11, and 13 and renders obvious claim 4 (in combination with
`
`Artieri) and claim 6 (in combination with Moore). For the reasons shown in the
`
`Petition and below, claims 1, 3-6, 11, and 13 of the ’789 patent are unpatentable.
`
`II. Lambrecht anticipates each and every limitation recited in claims 1, 3,
`5, 11, and 13.
`
`Patent Owner argues that Lambrecht does not anticipate each and every
`
`limitation of claims 1, 3, 5, 11, and 13. Patent Owner, however, focuses its
`
`arguments solely certain limitations of claim 1.
`
`
`
`2
`
`

`

`
`
`
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`A. Lambrecht anticipates “a shared bus . . . having a sufficient
`bandwidth to enable the decoder to access the memory and
`operate in real time.”
`
`
`
`Patent Owner argues that Lambrecht does not anticipate “a shared bus . . .
`
`having a sufficient bandwidth to enable the decoder to access the memory and
`
`operate in real time,” as recited in claim 1 of the ’789 patent, because Lambrecht
`
`allegedly fails to teach a bus that allows a decoder to access the memory and
`
`operate in real time. Response, Paper No. 22, at 6. Patent Owner’s argument fails
`
`because it ignores Lambrecht’s express teachings of Fig. 21, and improperly
`
`incorporates purported technical limitations from other embodiments taught in
`
`Lambrecht.
`
`1.
`
`The PCI bus in Fig. 21 of Lambrecht communicates data
`between the memory and the multimedia devices when in
`the multimedia mode.
`
`Lambrecht is directed to “[a] computer system optimized for real-time
`
`applications which provides increased performance over current computer
`
`architectures.” Ex. 1032, Abstract. Lambrecht’s computer system achieves this
`
`increased performance by including “a standard local system bus, such as the PCI
`
`bus” and also including “a dedicated real-time bus or multimedia bus.” Id. This
`
`allows “multimedia devices such as video cards, audio cards, etc.” to transfer real-
`
`time data through the bus. Id. As a result, the computer system “provides much
`
`greater performance for real-time applications than prior systems.” Id.
`
`
`
`3
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`The embodiment in Fig. 21 describes a system to achieve the express
`
`
`
`
`
`
`
`purpose of Lambrecht:
`
`
`
`Id., Fig. 21 (annotated).
`
`The computer system of Fig. 21, specifically referenced in the Petition,
`
`discloses a computer system that “includes an expansion bus, preferably a PCI bus
`
`120, and which includes mode logic which selects between different modes of the
`
`PCI bus 120.” Id. at 26:48-51. The mode logic, contained within the PCI bridge
`
`chipset, “is operable to place the PCI bus 120 in either a normal PCI mode or in a
`
`real-time/multimedia mode optimized for multimedia transfers of periodic data.”
`
`Id. at 26:53-56. The computer system in Fig. 21 also includes multimedia devices
`
`142D-146D that:
`
`communicate with each other and with the CPU 102 and main
`memory 110 via the PCI bus 120, as is well known in the art. The
`
`
`
`4
`
`

`

`
`
`
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`multimedia devices 142D-146D also communicate data between using
`the PCI bus signal lines 120 when the PCI bus 120 is in the
`multimedia mode.
`Id. at 27:57-62 (emphasis added). In this way, the Fig. 21 embodiment includes a
`
`
`
`PCI bus (i.e., a shared bus) that has sufficient bandwidth to enable the multimedia
`
`devices (including a decoder) to access the memory and operate in real time.
`
`Patent Owner, however, argues that the multimedia devices 142D-146D in
`
`Lambrecht’s Fig. 21 are not able to access the main memory when the PCI bus 120
`
`is in “multimedia mode.” Response at 6-8. Patent Owner’s reasoning is that,
`
`because Lambrecht states that Fig. 21 is “similar” to Fig. 1, the portions of
`
`Lambrecht that describe Fig. 1 automatically and unequivocally apply to Fig. 21.
`
`Id. But “similar” does not mean identical, as Patent Owner essentially argues, and
`
`its attempt to limit the disclosure of Fig. 21 by improperly importing limitations of
`
`Fig. 1 and other embodiments into its disclosures fails.
`
`In describing Fig. 1, Lambrecht states that “the multimedia devices 142-146
`
`communicate with each other via the PCI bus 120 and also communicate with the
`
`CPU and main memory 110 via the PCI bus 120” and that “[t]he multimedia
`
`devices 142-146 also communicate data between each other using the real-time bus
`
`or multimedia bus 130.” Ex. 1032 (Lambrecht) at 8:20-25. Patent Owner and its
`
`expert, Dr. Thornton, thus conclude, based solely on the disclosure with reference
`
`to Fig. 1, that the multimedia mode in Fig. 21 is the same as the multimedia bus
`5
`
`
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`130 in Fig. 1, and therefore operates in exactly the same manner to only
`
`
`
`
`
`
`
`communicate data between multimedia devices. Response at 7-8 (citing Ex. 2003
`
`(Thornton Decl.) ¶ 41). Patent Owner’s reliance on the description of Fig. 1,
`
`however, is incorrect because it ignores the entire description of Fig. 21 as well as
`
`Lambrecht’s other teachings. See Ex. 1044 (Stone decl.) ¶ 2.
`
`As seen in the comparison below, Fig. 21 differs from Fig. 1 in significant
`
`ways. Fig. 1 has two individualized buses (a real-time bus and a PCI expansion
`
`bus), whereas Fig. 21 has (i) a single PCI bus 120 that provides real-time data
`
`transfer and (ii) additional mode logic in the PCI bridge chipset 106.
`
`Ex. 1032, Fig. 21
`
`Ex. 1032, Fig. 1
`
`
`
`The mode logic “is operable to place the PCI bus 120 in either a normal PCI
`
`mode or in a real-time/multimedia mode optimized for multimedia transfers of
`
`periodic data.” Ex. 1032 at 26:53-56. This allows the multimedia devices to
`
`
`
`6
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`“communicate with each other and with the CPU 102 and main memory 110 via
`
`
`
`
`
`
`
`the PCI bus 120, as is well known in the art.” Id. at 27:57-59 (emphasis added).
`
`The mode logic also allows the multimedia devices to communicate data “using
`
`the PCI bus signal lines 120 when the PCI bus 120 is in the multimedia mode.” Id.
`
`at 27:59-62 (emphasis added). Thus, Lambrecht literally teaches that the PCI bus
`
`provides for real-time multimedia data transfers and communicating between the
`
`multimedia devices and the main memory via the PCI bus. See Ex. 1044 ¶ 4.
`
`Accordingly, Patent Owner’s argument—that the limited functionality of the
`
`separate real-time bus of Fig 1 somehow transfers its limited functionality to the
`
`multimedia mode of the PCI in Fig. 21—is simply conjecture, while contradicting
`
`the actual teachings with respect to Fig. 21.
`
`Moreover, there is nothing in reference to Fig. 21 that restricts the
`
`multimedia mode of the PCI bus 120 to data communication only between
`
`multimedia devices. See Ex. 1044 ¶ 5. Instead, the computer system in Fig. 21
`
`provides an optional multimedia bus 130 “to augment or supplement the PCI bus
`
`120 when the PCI bus 120 is in multimedia mode.” Ex. 1032 at 27:30-31. This
`
`optional multimedia bus 130 is included so that the multimedia devices can
`
`“communicate data between each other using the real-time bus or multimedia bus
`
`130. When the multimedia devices 142-146 communicate using the real-time bus
`
`130, the devices are not required to obtain PCI bus mastership and they consume
`
`
`
`7
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`little or no PCI bus cycles.” Id. at 8:24-28 (referencing Fig. 1). Thus, including the
`
`
`
`
`
`
`
`optional multimedia bus 130 into the Fig. 21 embodiment provides a second bus
`
`dedicated to enabling the multimedia devices to “communicate data between each
`
`other” so that “the devices are not required to obtain PCI bus mastership and they
`
`consume little or no PCI bus cycles” on the PCI bus 120. See id. at 8:24-28; Ex.
`
`1044 ¶ 5.
`
`Patent Owner’s argument that the PCI bus 120 is restricted to only
`
`communicate data between multimedia devices when in the multimedia mode
`
`would make the optional inclusion of the multimedia bus 130 redundant and
`
`unnecessary. See Ex. 1044 ¶ 6. Under Patent Owner’s theory, the multimedia mode
`
`of the PCI bus 120 would allegedly provide data communication only between the
`
`multimedia devices, which would be the identical function of the optional
`
`multimedia bus 130 (which provides data communication only between the
`
`multimedia devices). See id. This is contrary to the express purpose of Lambrecht.
`
`See id. Such a configuration would provide data communication only between the
`
`multimedia devices via multimedia bus 130 while also consuming cycles on PCI
`
`bus 120 in order to perform the exact same function of communicating data only
`
`between the multimedia devices. See id.
`
`Additionally, contrary to Patent Owner’s argument that the multimedia bus
`
`130 can only be used to communicate between multimedia devices, other
`
`
`
`8
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`embodiments of Lambrecht disclose the opposite. In particular, the embodiment in
`
`
`
`
`
`
`
`Fig. 6, shown below, is similar to Fig. 1 except that the multimedia bus in Fig. 6 is
`
`not only connected to the multimedia devices but is also connected to the PCI
`
`bridge chipset that connects the CPU and memory. Ex. 1032 at 12:22-25.
`
`Ex. 1032, Fig. 6
`
`Ex. 1032, Fig. 1
`
`
`
`The additional connection of the multimedia bus to the chipset in Fig. 6 is “to
`
`accommodate peripheral device accesses through the real-time bus 130A and
`
`chipset logic 106A to main memory 110.” Id. at 12:29-31 (emphasis added). In
`
`other words, in Fig. 6, “one or more of the multimedia devices 142-146 can use the
`
`multimedia bus 130A to interface through the chipset logic 106A to the main
`
`memory 110 as desired.” Ex. 1032 at 12:43-45 (emphasis added). Thus, despite
`
`Patent Owner’s argument to the contrary, Lambrecht does in fact teach that when
`
`the multimedia bus is connected to the PCI bridge chipset, it can be used to
`
`
`
`9
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`communicate data between the multimedia devices and the CPU and memory in
`
`
`
`
`
`
`
`real-time. Ex. 1044 ¶ 8.
`
`Patent Owner does not reference this aspect of the multimedia bus in Fig. 6
`
`in its Response but instead focuses exclusively on the more limiting embodiment
`
`of Fig. 1. Moreover, in preparing his declaration, Patent Owner’s expert
`
`acknowledged that he never considered the embodiment in Fig. 6 but “only used
`
`Figure 1 and Figure 21” in forming his opinion. Ex. 1043 (Thornton Depo.) at p.79
`
`ln.15-16.
`
`Further, Patent Owner’s argument is contrary to the disclosed purpose of the
`
`invention as it fails to explain how the system in Fig. 21 would continue to
`
`“provide[] much greater performance for real-time applications” (Ex. 1032,
`
`Abstract) if the multimedia mode of the PCI bus is limited to only communicating
`
`data between the multimedia devices. See Ex. 1044 ¶ 9. In this alleged
`
`configuration, both the PCI bus and the optional multimedia bus would be
`
`dedicated to transfers between multimedia devices, which would result in the CPU
`
`and the memory not being able to interface with the multimedia devices. See id.
`
`Any operations requiring interface between the multimedia devices would
`
`therefore be paused until the PCI bus return to the normal mode. See id. This
`
`alleged configuration also negates the entire point of the multimedia bus being
`
`optionally included since the multimedia devices would be “required to obtain PCI
`
`
`
`10
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`bus mastership” and would consume all of the PCI bus cycles while in the
`
`
`
`
`
`
`
`multimedia mode. Ex. 1032 at 8:25-28; see Ex. 1044 ¶ 9.
`
`Accordingly, Patent Owner’s argument that the multimedia mode of the PCI
`
`bus 120 in Fig. 21 can only communicate data between the multimedia devices
`
`because the multimedia bus 130 of Fig. 1 can only communicate data between the
`
`multimedia devices is incorrect. See Ex. 1044 ¶ 10. Patent Owner’s argument fails
`
`to account for the optional inclusion of the multimedia bus 130 in Fig. 21 to
`
`perform the same alleged function and it fails to explain why the multimedia mode
`
`of the PCI bus 120 (which is connected to the PCI chipset) would operate the same
`
`as the multimedia bus of Fig. 1 (which is not connected to the PCI chipset) rather
`
`than operate the same as the multimedia bus of Fig. 6 (which is connected to the
`
`PCI chipset). See id.
`
`In sum, Lambrecht discloses that “multimedia devices 142-146
`
`communicate with each other via the PCI bus 120 and also communicate with the
`
`CPU and main memory 110 via the PCI bus 120” and that “[t]he multimedia
`
`devices 142-146 also communicate data between each other using the real-time bus
`
`or multimedia bus 130.” Ex. 1032 (Lambrecht) at 8:20-25. Thus contrary to Patent
`
`Owner’s argument, the bus of Lambrecht enables the decoder device (i.e., a
`
`multimedia device) to access the main memory and operate in real-time.
`
`
`
`
`
`11
`
`

`

`
`
`
`
`2.
`
`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`No additional logic is needed in the PCI bridge chipset in
`Fig. 21 for the multimedia devices communicate data to the
`main memory in multimedia mode.
`
`
`
`
`
`Patent Owner further argues that the multimedia devices are not able to
`
`access the main memory when PCI bus 120 is in “multimedia mode” because only
`
`the multimedia devices include a special multimedia mode interface logic 966
`
`(shown in Fig. 22). Response at 10-13. Patent Owner errs in its position that the
`
`addition of special multimedia mode interface logic 966 circuitry is required in
`
`order for the main memory to use the multimedia mode.
`
`Patent Owner argues that “one of ordinary skill in the art would recognize
`
`that only the multimedia devices (142D, 144D, 146D) are equipped to utilize the
`
`‘multimedia mode’ of the PCI Expansion Bus (120)” since only these devices “are
`
`equipped with the interface logic (966) of the bus interface circuitry (962).” Id. at
`
`13. While it certainly is the case that the multimedia devices in Fig. 21 include
`
`interface logic 966 in order to interface with the multimedia mode (see Ex. 1032 at
`
`27:38-40), Patent Owner overlooks the other teachings of Lambrecht.
`
`Lambrecht teaches that the “a host/PCI/cache bridge or chipset 106” already
`
`has the capability of communicating with the PCI bus when in multimedia mode.
`
`As shown in Fig. 21, the chipset logic 106 is coupled to a CPU 102 and a main
`
`memory 110. Id. at 26:65-67, 27:4-5. “The chipset logic 106 preferably includes a
`
`memory controller for interfacing to the main memory 110.” Id. at 27:8-9. The
`
`
`
`12
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`chipset logic 106 also includes a “mode logic 960 [that] is operable to place the
`
`
`
`
`
`
`
`PCI bus 120 in either a normal PCI mode or in a real-time/multimedia mode
`
`optimized for multimedia transfers of periodic data.” Id. at 27:19-22. Since chipset
`
`106 interfaces the CPU and the main memory with the PCI bus, and has mode
`
`logic for placing the PCI bus into multimedia mode (and for returning the PCI bus
`
`to normal PCI mode), it is clear that Lambrecht teaches that the chipset 106 is
`
`capable of communicating with the PCI bus when the PCI bus is in multimedia
`
`mode. Ex. 1030 at p.43-51; see Ex. 1044 ¶ 12.
`
`This is further evidenced from Lambrecht’s disclosure of Fig. 6. As
`
`discussed above, Fig. 6 includes chipset logic 106A that “is connected to both the
`
`local expansion bus 120 as well as the real-time [multimedia] bus 130A.” Ex. 1032
`
`at 12:23-25; see Ex. 1044 ¶ 13. The chipset 106A “can communicate directly to the
`
`PCI bus 120, and can also communicate directly with the real-time or multimedia
`
`bus 130.” Ex. 1032 at 12:37-40. This allows the multimedia devices (that include
`
`both PCI bus and multimedia bus interface logic, see Fig. 2) to communicate with
`
`the CPU and the memory via either the PCI bus or the multimedia bus. See id. at
`
`12:40-45; see Ex. 1044 ¶ 13.
`
`Thus, based on the entire disclosure of Lambrecht’s Fig. 21 and the
`
`examples from Lambrecht’s other embodiments, Lambrecht teaches that the
`
`multimedia mode of the PCI bus 120 in Fig. 21 communicates data between the
`
`
`
`13
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`multimedia devices, the CPU, and the memory in real-time while in the multimedia
`
`
`
`
`
`
`
`mode. Ex. 1030 at p.43-51.
`
`B.
`
`Lambrecht anticipates “a decoder that requires access to the
`memory sufficient to maintain real time operation.”
`
`Patent Owner argues that Lambrecht does not anticipate “a decoder” because
`
`“Lambrecht does not disclose a bus that would allow the alleged decoder (144D) to
`
`access the alleged main memory (110) in real time.” Response at 14. Patent Owner
`
`reasons that Lambrecht’s “multimedia devices may have their own dedicated
`
`multimedia memory (160)” and in one embodiment (Figs. 15 and 16) use this
`
`dedicated memory “in real time through the multimedia/real-time bus.” Id. at 14-
`
`15.
`
`First, Patent Owner’s argument fails because it relies on a feature of a
`
`different embodiment of Lambrecht and assumes that this feature applies to Fig. 21
`
`of Lambrecht. As stated in the Petition and discussed above, Lambrecht’s
`
`embodiment in Fig. 21 discloses a number of multimedia devices 142D-146D that
`
`are each coupled to the PCI bus 120. Ex. 1032 at 27:32-33. These multimedia
`
`devices “may comprise video accelerator or graphics accelerator cards, video
`
`playback cards, MPEG decoder cards, sound cards, network interface cards, SCSI
`
`adapters for interfacing to various input/output devices, such as CD-ROMS and
`
`tape drives, or other devices as desired.” Id. at 27:51-56 (emphasis added). Thus,
`
`
`
`14
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`since Lambrecht specifically teaches an MPEG decoder as one of the multimedia
`
`
`
`
`
`
`
`devices coupled to the PCI bus 120 in Fig. 21 and, as discussed above, also teaches
`
`that the multimedia devices can access the CPU and the main memory when the
`
`PCI bus is in the multimedia mode, Lambrecht does in fact anticipate “a decoder
`
`that requires access to the memory.” Indeed, Patent Owner’s expert admits that
`
`Lambrecht discloses requiring such cards to have their own memory is undesirable
`
`at least because it adds additional cost to the system. Ex. 1043 at 54:15-20; see
`
`also Ex. 1032 at 2:3-11. To argue that the multimedia devices must have their own
`
`dedicated memory runs directly counter to the purpose of the Lambrecht invention.
`
`Second, Patent Owner’s argument also fails because it relies on an incorrect
`
`understanding of the state of the art. In particular, Patent Owner’s expert claims
`
`that “traditional MPEG decoders require a 2 Mbyte dedicated memory that is
`
`utilized during the decoding process.” Ex. 2003 ¶ 31. Patent Owner’s expert cites
`
`no evidence or support for such statement. See Ex. 1044 ¶ 14. Based on this
`
`unsupported statement, Patent Owner’s expert thus assumes that the video
`
`decoders discussed in Lambrecht also require dedicated multimedia memory and
`
`that such decoders could not use the main memory in Fig. 21. See Ex. 2003 ¶ 48;
`
`Ex. 1043 at 88:23-89:1 (“And if [the multimedia device] were assumed to be a
`
`video decoder, one skilled in the art in 1997, when this was issued, would presume
`
`that there would be multimedia memory”); see also Response at 22-23.
`
`
`
`15
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`Patent Owner’s expert, however, is incorrect that video decoders known in
`
`
`
`
`
`
`
`the art prior to the filing of the ’789 patent in 1996 or Lambrecht in 1995 required
`
`dedicated multimedia memory. See Ex. 1044 ¶ 15. For example, U.S. Patent No.
`
`5,797,028 to Gulick et al. (“Gulick”) (Ex. 1023) (in which Lambrecht is a co-
`
`inventor) that was filed on September 11, 1995 (almost a year prior to the ’789
`
`patent) and shared the same original assignee as Lambrecht, teaches a digital
`
`system chip 112 that “is programmable to perform various functions, such as
`
`MPEG decoding.” Ex. 1023 at 6:21-22. Gulick describes, in certain instances, that
`
`the decoder chip 112 can include “multimedia memory (not shown) for storing
`
`multimedia data, such as video data and audio data.” Id. at 6:37-39. Gulick,
`
`however, also discloses that, in other instances, the decoder chip 112 “does not
`
`include multimedia memory, but rather video data and audio so data are stored in
`
`the system memory 110 according to a unified memory architecture.” Id. at 6:48-
`
`51. Other systems that also predate the ’789 patent disclosed a video decoder that
`
`used shared memory. See Ex. 1007 (disclosing a system that uses either system
`
`memory or dedicated memory for at least some video decoding operations); Ex.
`
`1045 (disclosing a system with shared memory that is used by multiple peripheral
`
`devices including video decoders); See Ex. 1044 ¶ 16.
`
`Thus, it is clear that a POSITA, before the filing of the ’789 patent, had full
`
`knowledge that video decoders could use main system memory according to a
`
`
`
`16
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`unified memory architecture for video decoding operations. See id. ¶ 17. Patent
`
`
`
`
`
`
`
`Owner’s expert’s naked assertion that video decoders at the time of the ’789 patent
`
`required dedicated multimedia memory is incorrect. See id. Instead, it was known
`
`in the art that video decoders could utilize either dedicated multimedia memory, as
`
`shown in Lambrecht’s Figs. 15 and 16, or the main memory, as shown in
`
`Lambrecht’s Figs. 6, 19, and 21, and the evidence of record shows that it was
`
`known to POSITAs that decoders could use the main system memory. See id.
`
`Consequently, Patent Owner’s argument that Lambrecht’s decoder required
`
`multimedia memory is entirely predicated on an incorrect understanding of the
`
`state of the art. Thus, contrary to Patent Owner’s argument, Lambrecht’s Fig. 21
`
`does in fact anticipate “a decoder that requires access to the memory.”
`
`C. Lambrecht anticipates “a shared bus . . . having sufficient
`bandwidth to enable the decoder to access the memory and
`operate in real time.”
`
`Patent Owner argues that Lambrecht fails to anticipate “a shared bus” that
`
`“enable[s] the decoder to access the memory and operate in real time” for two
`
`reasons—(1) the multimedia mode of Fig. 21 allegedly only allowing data transfers
`
`between multimedia devices and (2) Lambrecht’s failure to specifically state that
`
`the PCI bus 120, the PCI bridge chipset 106, and the memory bus 108 are capable
`
`of facilitating real-time data transfers. See Response at 16-21. Both of these
`
`arguments are incorrect because they fail to consider the entire description with
`
`
`
`17
`
`

`

`Petitioner’s Reply
`IPR2016-00923 (Patent No. 5,812,789)
`
`
`reference to Fig. 21 as well as the technical functionality of PCI bus referenced in
`
`
`
`
`
`
`
`Fig. 21.
`
`First, Patent Owner reiterates its argument previously used in its Response
`
`(see p.6-13) that the multimedia mode of the PCI bus in Fig. 21 is only used for
`
`data transfers between the multimedia devices. Response at 18-21. This time,
`
`though, Patent Owner attempt to rely not only on disclosure related to Lambrecht’s
`
`Fig. 1, but also relies on Figs. 7 and 20. This argument, however, fails for the same
`
`reason as discussed above in section II.A.1. Fig. 21 teaches that the multimedia
`
`devices can access the main memory via the PCI bus (the only bus in Fig. 21) in
`
`either the normal mode or the multimedia mode. See section II.A.1, above.
`
`Second, Patent Owner’s assertion—that Lambrecht’s system in Fig. 21
`
`cannot facilitate real time data transfers because the PCI bus 120, the PCI bridge
`
`chipset 106, and the memory bus 108 are not specifically described as being
`
`capable of such—also fails in the face of the ’789 patent’s own disclosure.
`
`According to the ’789 patent, the bus must have “a bandwidth greater than the
`
`bandwidth required for the decoder/encoder 45 to operate in real time.” Ex. 1001 at
`
`6:29-32. In the ’789 patent, the decoder/encoder 45 operates according to the
`
`MPEG-1 or MPEG-2 standard. See id. at 7:45-54. In two examples provided by the
`
`’789 patent, the bus “is capable of having a bandwidth of approximately 400
`
`Mbytes/s. This bandw

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket