throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`HTC CORPORATION, HTC AMERICA, INC.,
`and APPLE, INC.,
`Petitioner,
`
`v.
`
`PARTHENON UNIFIED MEMORY ARCHITECTURE LLC,
`Patent Owner.
`____________
`
`Case IPR2016-009231
`Patent 5,812,789
`____________
`
`Declaration of Mitchell A. Thornton, Ph. D., P.E.
`
`
`1 Case IPR2016-00847 has been joined with this proceeding.
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 1
`
`

`
`I.
`
`Introduction
`
`1.
`
`I am over the age of eighteen (18) and otherwise competent to make
`
`this declaration.
`
`2. My name is Mitchell Aaron Thornton. I am offering this declaration
`
`in the matter listed above on behalf of Parthenon Unified Memory Architecture
`
`LLC and at the behest of their attorneys Ahmad, Zavitsanos, Anaipakos, Alavi &
`
`Mensing P.C. I am being compensated at my usual rate and my compensation is
`
`not dependent on any opinions that I may take in this matter, any testimony, or any
`
`intermediate or final resolution in the matter.
`
`3.
`
`I understand that the Board has issued an institution Decision in the
`
`above-captioned IPR concluding that the Petitioner has established a reasonable
`
`likelihood of success with respect to the following grounds (collectively “Instituted
`
`Grounds”):
`
`a. Anticipation of claims 1, 3, 5, 11, and 13 by Lambrecht;
`
`b. Obviousness of claim 4 over Lambrecht and Artieri; and
`
`c. Obviousness of claim 6 over Lambrecht and Moore.
`
`4.
`
`This declaration is directed to an analysis of these Instituted Grounds.
`
`II. My Background and Qualifications
`
`5.
`
`I earned a Bachelor of Science degree in Electrical Engineering from
`
`Oklahoma State University in 1985. In 1990, I earned a Masters of Science degree
`
`1
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 2
`
`

`
`in Electrical Engineering from the University of Texas at Arlington. In 1993, I
`
`earned a Masters of Science degree in Computer Science from Southern Methodist
`
`University. I earned a Ph.D. in Computer Engineering from Southern Methodist
`
`University in 1995. I am a Licensed Professional Engineer in the states of Texas,
`
`Mississippi, and Arkansas. I also hold a Commercial General Radiotelephone
`
`Operator License (GROL) with Ship Radar endorsement issued by the Federal
`
`Communications Commission (FCC).
`
`6.
`
`I am currently the Cecil H. Green Chair of Engineering and Professor
`
`in the Department of Computer Science and Engineering and in the Department of
`
`Electrical Engineering at Southern Methodist University. Prior to 2002, I served as
`
`a faculty member at Mississippi State University in the Department of Electrical
`
`and Computer Engineering from 1999 through 2002. I served as a faculty member
`
`at the University of Arkansas from 1995 through 1999 in the Department of
`
`Computer Systems Engineering. In my university positions, my responsibilities
`
`are research, teaching, and providing service in my profession. My teaching and
`
`research area of expertise is generally in the area of computer engineering where I
`
`specialize in hardware design for information processing systems.
`
`7.
`
`In addition to my academic rank of professor, I am also the Associate
`
`and Technical Director of the Darwin Deason Institute for Cyber Security at
`
`Southern Methodist University. The Institute mission is to advance the science,
`
`2
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 3
`
`

`
`policy, application and education of cyber security through basic and problem-
`
`driven, interdisciplinary research. As Associate and Technical Director, I am
`
`responsible for the coordination and oversight of all research projects within the
`
`auspices of this multi-million dollar endowed research Institute that is comprised
`
`of 11 principal investigators and their associated research teams. In this role, I am
`
`routinely involved with several different state-of-the-art projects regarding the
`
`technical aspects of information processing system processes, methods, software,
`
`and hardware.
`
`8.
`
`Prior to my academic career, I was employed in the commercial sector
`
`as an engineer. I was employed full-time at E-Systems, Inc. (now L3
`
`Communications) in Greenville, Texas from 1986 through 1991 and resigned from
`
`my position as Senior Electronic Systems Engineer in 1991 to pursue full-time
`
`graduate studies in Computer Science and Computer Engineering. My duties at E-
`
`Systems involved the design, analysis, implementation, and test of a variety of
`
`different electronic systems including various information processing systems
`
`centered around signal processing, data transmission and processing, and
`
`communications systems. The communications systems I was involved with
`
`processed a variety of different types of signals including data, audio, and video
`
`systems. These systems were comprised of components such as receivers,
`
`transmitters, computers, and special purpose circuitry.
`
`3
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 4
`
`

`
`9.
`
`During the time I was in graduate school pursuing the Ph.D. degree, I
`
`also worked part-time and full-time during the summer of 1992 at a commercial
`
`integrated circuit (IC) design company named the Cyrix Corporation. At Cyrix, I
`
`was a member of a design team that ultimately produced a microprocessor that is
`
`compatible with the Intel Pentium. My duties included the design of the bus
`
`controller and memory interface circuitry for this IC.
`
`10. My practice and research covers a range of topics centered around
`
`hardware design and analysis including secure circuit and embedded system
`
`design, electronic design automation (EDA) methods, and algorithms for quantum,
`
`classical digital systems, and large systems design. I have also maintained an
`
`independent professional engineering practice since 1993 as a sole proprietor that
`
`is a registered engineering firm in the state of Texas.
`
`11.
`
`I am a named inventor on four (4) issued patents and one (1) patent
`
`application under consideration at the USPTO. I have authored or coauthored over
`
`200 scholarly publications in the fields of electrical engineering and computer
`
`science.
`
`12. My curriculum vitae and testimony list are included in Appendix A to
`
`this declaration, which more fully sets forth my qualifications.
`
`4
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 5
`
`

`
`III. Documents Considered
`In addition to my knowledge and experience, I have reviewed and
`13.
`
`relied upon the following materials in performing my analysis:
`
`• The `789 Patent (and the publications incorporated by reference therein)
`
`and its file history;
`
`• Petition for Inter Partes Review of U.S. Patent No. 5,812,789 including
`
`all the exhibits [IPR2016-00923];
`
`• Decision on Institution in IPR2016-00923;
`
`• Shanley, et al., “PCI System Architecture,” Addison-Wesley Publishing
`
`Company, 1995 (3rd ed.) (“Shanley”)
`
`• Gordon E. Moore, Cramming More Components onto Integrated
`
`Circuits, 38 ELECTRONICS 114 (1965) [Ex. 1035] (“Moore”);
`
`• U.S. Patent No. 5,682,484 [Ex. 1032] (“Lambrecht”);
`
`• U.S. Patent No. 5,579,052 [Ex. 1036] (“Artieri”);
`
`• Declaration of Harold S. Stone, Ph.D. [Ex. 1030] (“Stone Decl.”); and
`
`• Deposition testimony of Harold S. Stone, Ph.D. dated November 16,
`
`2016 [Ex. 2004] (“Stone Depo.”).
`
`5
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 6
`
`

`
`IV. Summary of Opinions
`
`14. As detailed below, it is my opinion that the challenged independent
`
`claims are not anticipated by Lambrecht and that the challenged dependent claims
`
`are also not anticipated or obvious for at least the same reasons.
`
`V. Legal Standards
`
`15.
`
`I am not an attorney or patent agent, and thus, I have relied upon
`
`certain legal factors that have been explained to me. Some of these, which form the
`
`legal framework for the opinions I am providing, are summarized below.
`
`16.
`
`I understand that claims are to be interpreted from the perspective of
`
`one of ordinary skill in the art. I understand that in determining the level of
`
`ordinary skill in the art, the following factors may be considered: (1) the
`
`educational level of the inventor; (2) type of problems encountered in the art; (3)
`
`prior art solutions to those problems; (4) rapidity with which innovations are made;
`
`(5) sophistication of the technology; and (6) educational level of active workers in
`
`the field.
`
`17.
`
`I understand from reading the Board’s decision that in this inter partes
`
`review, claim terms are to be given their broadest reasonable construction in light
`
`of the patent specification. I also understand that claim terms are presumed to be
`
`given their ordinary and customary meaning as would be understood by one of
`
`ordinary skill in the art. Furthermore, I understand that an inventor may provide a
`
`6
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 7
`
`

`
`contrary definition of a term in the specification, if it is done with reasonable
`
`clarity, deliberateness, and precision. I also understand that care must be taken not
`
`to read a particular embodiment appearing in the specification into the claim if the
`
`claim language is broader than the embodiment.
`
`18.
`
`I understand that a claim may be invalid as anticipated or as being
`
`obvious.
`
`19.
`
`I understand that a claim is not patentable and is anticipated if a single
`
`prior art reference discloses each and every element recited in the claim, expressly
`
`or inherently, such that a person of ordinary skill in the art could practice the
`
`disclosed embodiment without undue experimentation. I also understand that the
`
`claim elements must be arranged in the reference in the same way as in the claim.
`
`20.
`
`I understand that an element is inherent in a reference if one of
`
`ordinary skill in the art would understand that the reference makes clear that the
`
`element, while not expressly disclosed, is necessarily present in the reference.
`
`Inherency, however, may not be established by probabilities or possibilities.
`
`21.
`
`I understand that the obviousness standard is defined in the patent
`
`statute (35 U.S.C. § 103(a)). I also understand that a claim is not patentable and is
`
`obvious if the differences between a claim and the prior art are such that the
`
`claimed subject matter as a whole would have been obvious to a person having
`
`ordinary skill in the art at the time the invention was made. I understand that this
`
`7
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 8
`
`

`
`inquiry involves examination of number of factors including: (1) determining the
`
`scope and content of the prior art; (2) ascertaining the differences between the
`
`claim and the prior art; (3) resolving the level of ordinary skill in the prior art; and
`
`(4) considering any secondary or objective evidence of non-obviousness. I
`
`understand that secondary or objective evidence of non-obviousness include
`
`factors such as commercial success, long felt need for the invention, and failure of
`
`others.
`
`22.
`
`I understand that an obviousness analysis involves comparing a claim
`
`to the prior art to determine whether the claimed invention would have been
`
`obvious to a Person of Ordinary Skill in the Art (“POSA”) in view of the prior art,
`
`and in light of the general knowledge in the art. I also understand when a POSA
`
`would have reached the claimed invention through routine experimentation, the
`
`invention may be deemed obvious.
`
`23.
`
`I also understand that obviousness can be established by combining or
`
`modifying the teachings of the prior art to achieve the claimed invention. It is also
`
`my understanding that where there is a reason to modify or combine the prior art to
`
`achieve the claimed invention, there must also be a reasonable expectation of
`
`success in so doing. I understand that the reason to combine prior art references
`
`can come from a variety of sources, not just the prior art itself or the specific
`
`problem the patentee was trying to solve. And I understand that the references
`
`8
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 9
`
`

`
`themselves need not provide a specific hint or suggestion of the alteration needed
`
`to arrive at the claimed invention; the analysis may include recourse to logic,
`
`judgment, and common sense available to a person of ordinary skill that does not
`
`necessarily require explication in any reference. Finally, it is my understanding that
`
`obviousness can be established by choosing from a finite number of identified,
`
`predictable solutions, with a reasonable expectation of success.
`
`24.
`
`I further understand that a patent composed of several elements is not
`
`proved obvious merely by demonstrating that each of its elements was,
`
`independently, known in the prior art. I further understand that a showing of a
`
`suggestion, teaching, or motivation to combine the prior art references is an
`
`essential evidentiary component of an obviousness conclusion. I further understand
`
`that a claim is not obvious if the references relied upon in a proposed combination
`
`teach away from the claimed combination in a way that would deter any
`
`investigation into such a combination. For instance, it is my understanding that a
`
`reference teaches way from a combination when using it in that combination would
`
`produce an inoperative result.
`
`VI. Level of Ordinary Skill in the Art
`
`25.
`
`In formulating my opinions, I have also considered the viewpoint of a
`
`person of ordinary skill in the art (“POSA”) at the time of the filing of the `789
`
`9
`
`Patent.
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 10
`
`

`
`26.
`
`I understand that Dr. Stone has opined that a person of ordinary skill
`
`in the art as of the effective filing date of the `789 Patent would have held an
`
`accredited Bachelor’s degree in Electrical Engineering and/or Computer Science
`
`and/or Computer Engineering and had three years’ experience in the fields of data
`
`compression and overall computer system architecture. [Stone Decl., Ex 1030,
`
`¶75].
`
`27. Based upon my knowledge of this field, I conclude that a person of
`
`ordinary skill in this art at the time of the filing of the `789 Patent, and for that
`
`matter, at all subsequent times through the present, would have held at least a
`
`Bachelor’s degree in electrical engineering, computer engineering, or an equivalent
`
`degree in a related discipline from an accredited institution of higher learning and
`
`at least two to three years’ experience in signal and/or image processing and
`
`computer architecture at both the systems and micro-architecture level. In lieu of
`
`two to three years of experience, a person of ordinary skill in the art may hold, in
`
`addition to a Bachelor’s degree as described above, a Master’s or other graduate
`
`degree in electrical or computer engineering with a focus in computer architecture
`
`and signal and/or image processing with one year of relevant experience.
`
`28. My analysis was performed from the perspective of such a person. If
`
`I were to apply the level of ordinary skill as proffered by Dr. Stone in his
`
`declaration, my analysis and conclusions would remain unchanged.
`
`10
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 11
`
`

`
`VII. State of the Prior Art and the `789 Patent
`
`29. The computer memory storage requirements of a digital representation
`
`of an uncompressed image is dependent on its resolution, color depth, and size in
`
`pixels. Video files are comprised of sequences of images that are further enhanced
`
`with a corresponding audio track to accompany them. As a result, a video file
`
`quickly becomes large in size. The transmission of uncompressed video files is
`
`prohibitively expensive.
`
`30. Accordingly, video files are typically compressed at a transmitting
`
`device. The compressed file is then transmitted to a receiving device where it is
`
`decompressed. To that end, an encoder at the transmitter compresses the video file
`
`and a decoder decompresses the file received at the receiver in order to retrieve a
`
`facsimile of the original video and audio data. In order to ensure compatibility
`
`between devices, a number of standards for encoding and decoding video files
`
`were developed. One of those standards was developed by the Motion Picture
`
`Experts Group (“MPEG”) and has been adopted as a standard for the
`
`communication of video.
`
`31.
`
`If a decoder does not operate in real time, the decoded video being
`
`displayed would stop periodically between images until the decoder can access the
`
`memory and process the subsequent image frame. Moreover, when using a
`
`temporal (intercompression) technique such as the MPEG Standard, some of the
`
`11
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 12
`
`

`
`images are decoded based on previous images and some based on previous and
`
`subsequent images. Accordingly, dropping an image on which the decoding of
`
`other images depends is unacceptable as it can result in poor or unrecognizable
`
`decoded images. Therefore, it is typically the case that a decoder requires its own
`
`dedicated memory. For instance, traditional MPEG decoders require a 2 Mbyte
`
`dedicated memory that is utilized during the decoding process. This dedicated
`
`memory is necessary to allow the decoder to decode images in real-time without
`
`dropping frames that would result in a deterioration of the video quality at the
`
`receiver.
`
`32.
`
`It is generally desirable to reduce the die area of an integrated circuit
`
`device for a given functionality. Such a reduction allows for an increase in the
`
`number of the die that can be manufactured on a silicon wafer having a given size.
`
`For example, a video decoder die would be reduced in size if it did not include a
`
`dedicated memory circuit. Moreover, such a dedicated memory of a decoder may
`
`remain unused when an image is not being decoded which is inefficient.
`
`Accordingly, it is desirable to permit the decoder to share the main memory of the
`
`system with other system components.
`
`33. To that end, the `789 Patent is generally directed to sharing both a
`
`memory interface and a memory between a video and/or audio decoder and
`
`another device contained in an electronic system. [`789 Pat. [Ex. 1001],
`
`12
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 13
`
`

`
`Abstract; 4:12-22; 4:30-34; 4:40-48; independent claim 1]. Accordingly, the
`
`electronic system includes a first device that requires access to the memory and
`
`a decoder that requires access to the memory sufficient to maintain real time
`
`operation. Id. at claim 1. A memory interface is coupled to the memory, the first
`
`device and the decoder. Id. The memory interface includes an arbiter for
`
`selectively providing access for the first device and the decoder to the memory.
`
`Id. A shared bus is coupled to the memory, the first device and the decoder. Id.
`
`The shared bus has sufficient bandwidth to enable the decoder to access the
`
`memory and operate in real time when the first device simultaneously accesses
`
`the shared bus. Id.
`
`34. A video decoder only requires access to memory during its operation.
`
`In accordance with the implementation of the `789 Patent, other devices such as a
`
`first device may have exclusive access to a shared memory when the decoder is not
`
`operating. In such instances, the first device can use the entire bandwidth of the
`
`fast bus to support memory accesses.
`
`35. The fast bus (70) of the `789 Patent has a bandwidth that is at least
`
`twice the required bandwidth to support the memory accesses needed to support
`
`real time video decoding. [`789 Pat., 6:67-7:2]. Accordingly, the video decoder
`
`will typically be using less than 40% of the bandwidth of the fast bus (70) during
`
`decoding. [`789 Pat., 7:18-20]. This frees up the remaining bandwidth to be used
`13
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 14
`
`

`
`by other devices such as a first device during the decoder operation. [`789 Pat.,
`
`7:20-22]. Because the decoder does not use the entire available bandwidth of the
`
`fast bus (70) during real time decoding, the remaining bus bandwidth may be used
`
`by other devices, such as a first device, simultaneously while real time decoding is
`
`occurring. [`789 Pat., 7:5-15].
`
`VIII. Claim Construction
`I understand that the Board has construed the term “video decoder” to
`36.
`
`mean “hardware and/or software
`
`that
`
`translates data streams
`
`into video
`
`information.” (Institution Decision, Paper 10, at 8-9).
`
`37.
`
`I understand that the Board has construed the term “real time” as
`
`“pertaining to a data-processing system that controls an ongoing process and
`
`delivers its outputs (or controls its inputs) not later than the time when these are
`
`needed for effective control.” (Institution Decision, Paper 10, at 11).
`
`38.
`
`I have used the Board’s construction of the terms “video decoder” and
`
`“real time” in performing my analysis. I have used the plain and ordinary meaning
`
`of the remaining claim terms when performing my analysis.
`
`IX. Analysis of Instituted Grounds
`
`A. Anticipation of Claims 1, 3, 5, 11, and 13 by Lambrecht
`
`1) Lambrecht does not disclose “a shared bus … having a sufficient
`bandwidth to enable the decoder to access the memory and operate in
`real time” [Independent claim 1]
`
`14
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 15
`
`

`
`39. The Petition identifies multimedia device (142D) as the first device;
`
`the main memory (110) as the memory; the multimedia device (144D) as the
`
`decoder; and the PCI expansion bus (120) as the shared bus. [Pet. at 16]. The
`
`Petitioner then contends that the PCI expansion bus (120) provides real time
`
`access by the multimedia device (144D) (alleged decoder) to the main memory
`
`(110) (alleged memory) when operating in the multimedia mode, which is a
`
`special mode, optimized for real-time data transfers. [Pet. at 17-19]. I disagree
`
`with that conclusion. Specifically, in my opinion, when operating in the
`
`multimedia mode, the PCI expansion bus (120) does not enable the multimedia
`
`device (144D) (alleged decoder) to access the main memory (110) (alleged
`
`memory). Accordingly,
`
`the PCI expansion bus (120) does not permit
`
`communication between multimedia device (144D) and the main memory (110)
`
`when it is placed in the multimedia mode.
`
`40. The petitioner relies on the embodiment of Figure 21 of Lambrecht
`
`for its contention that independent claim 1 is anticipated. [Pet. at 10-19]. With
`
`respect to the embodiment of Figure 21, Lambrecht states that “[t]he computer
`
`system of FIG. 21 is similar to the computer system of FIG. 1” except that “the
`
`mode logic in the computer system of FIG. 21 is operable to place the PCI bus
`
`120 in either a normal PCI mode or in a real-time/multimedia mode optimized
`
`15
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 16
`
`

`
`for multimedia transfers of periodic data.” [Lambrecht, Ex. 1032, 26:48-56].
`
`Accordingly, the embodiment of Figure 21 replaces the PCI expansion bus
`
`(120) and the real time bus (130) of Figure 1 with a single PCI expansion bus
`
`(120) which has two different modes of operation: (1) a first mode of operation
`
`where the PCI Expansion Bus (120) operates like the PCI Expansion Bus (120)
`
`of Figure 1; and (2) a second mode of operation where the PCI Expansion Bus
`
`(120) operates like the real time bus (130) of Figure 1. The mode logic (960)
`
`selects which of the two modes is enabled. [Lambrecht, 27:18-22]. Figure 1 and
`
`Figure 21 of Lambrecht are reproduced below, highlighting the difference
`
`between the two systems:
`
`
`
`41. Because Lambrecht states that “[t]he computer system of FIG. 21 is
`
`similar to the computer system of FIG. 1,” one of ordinary skill in the art would
`
`understand that when the PCI Expansion Bus (120) of Figure 21 is in the
`
`“normal PCI mode” it operates like the PCI Expansion Bus of the embodiment
`
`16
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 17
`
`

`
`of Figure 1. Conversely, when the PCI Expansion Bus (120) of Figure 21 is in
`
`the multimedia mode it operates like the multimedia bus (130) of the
`
`embodiment of Figure 1. Therefore, for at least three reasons, the PCI Expansion
`
`Bus (120) of the embodiment of Figure 21 does not enable the multimedia device
`
`(144D) (alleged decoder) to access the main memory (110) (alleged memory)
`
`when operating in the multimedia mode.
`
`42. First, as shown in Figure 1, the multimedia bus (130) (which
`
`operates “similar” to the PCI Expansion Bus (120) of Figure 21 operating in the
`
`multimedia mode) is not in communication with the PCI Bridge Chipset (106)
`
`and the main memory (110) and cannot transfer data from the multimedia
`
`device (144) (alleged decoder) to the main memory (110) (alleged memory).
`
`Second, with respect to the operation of the multimedia bus (130) of Figure 1,
`
`Lambrecht explicitly states
`
`that
`
`the multimedia bus (130) facilitates
`
`communication between the multimedia devices (142-146) – not between the
`
`multimedia device (144D) (alleged decoder) and the main memory (110)
`
`(alleged memory):
`
`The multimedia devices 142-146 use the multimedia bus 130 to
`communicate data, preferably only periodic data, between the
`respective devices. … Thus, 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, as is well known in the art. The multimedia devices 142-146
`17
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 18
`
`

`
`also 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 little or no
`PCI bus cycles.”
`
`
`[Lambrecht, Ex. 1032, 8:8-28 (emphasis added)]. Accordingly, the multimedia
`
`bus (130) of Figure 1 does not enable the multimedia device (144D) (alleged
`
`decoder) to access the main memory (110) (alleged memory). Because the
`
`multimedia mode of the PCI Expansion Bus (120) of the embodiment of Figure
`
`21 operates similar to the multimedia bus (130) of the embodiment of Figure 1
`
`[Lambrecht, 26:51-52], the PCI Expansion Bus (120) of Figure 21 operating in
`
`the multimedia mode also does not enable the multimedia device (144D)
`
`(alleged decoder) to access the main memory (110) (alleged memory).
`
`43. Third, that the multimedia mode of the PCI Expansion Bus (120) does
`
`not enable the multimedia device (144D) (alleged decoder) to access the main
`
`memory (110) (alleged memory) is evident from a closer analysis of the
`
`embodiment of Figure 21. As is well known to those of ordinary skill in the art,
`
`bus standards such as the PCI standard are not defined solely based on their
`
`physical hardware assets. Instead, a bus is typically defined as a collection of
`
`assets including the hardware and the protocol for data transfer. For example,
`
`the Peripheral Component Interconnect (or PCI) specification is one that defines
`
`18
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 19
`
`

`
`the PCI bus. The PCI bus is intended to define the interconnect and bus transfer
`
`protocol between highly-integrated peripheral adapters that reside on a common
`
`local bus on a system board or add-in expansion cards that are on the PCI bus
`
`[Shanley, Ex. 1019, p. 545]. Accordingly, Lambrecht introduces the use of a
`
`new, non-standard bus referred to as the “real-time/multimedia mode” or
`
`“multimedia mode” of the PCI Expansion Bus (120). The purpose of this new
`
`“multimedia mode” of the PCI Expansion Bus (120) is to allow periodic data
`
`transfers. [Lambrecht, 26:53-60]. In order to support the use of this new
`
`“multimedia mode” of the PCI Expansion Bus (120), specialized hardware
`
`(and/or software) must be included with all devices that enable them to use this
`
`new and non-standard protocol for data transmission. Accordingly, Lambrecht
`
`discloses interface logic (966) “for interfacing to the PCI bus 120 when the PCI
`
`bus 120 is in the multimedia mode.” [Lambrecht, 27:38-40] (“The bus interface
`
`circuitry 962 also includes interface logic 966 for interfacing to the PCI bus 120
`
`when the PCI bus 120 is in the multimedia mode. The bus interface circuitry 962
`
`also includes interface logic 968 for interfacing to the optional multimedia bus
`
`130”). As a result, all devices disclosed in Figure 21 that benefit from the new
`
`and non-standard “multimedia mode” of the PCI Expansion Bus (120) which
`
`enables real-time data transmission must necessarily include the interface logic
`
`19
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 20
`
`

`
`(966) of the bus interface circuitry (962) to enable the use of the real-time
`
`multimedia mode of the PCI Expansion Bus (120). In contrast, one of ordinary
`
`skill in the art would appreciate that the components in Figure 21 which do not
`
`have the interface logic (966) of the bus interface circuitry (962) cannot utilize
`
`the “multimedia mode” of the PCI Expansion Bus (120) because they are not
`
`equipped to interface with it.
`
`44. Furthermore, because the new non-standard multimedia mode
`
`utilizes the same collection of signal lines as those used for the bus when it is in
`
`the standard or “normal” PCI mode of operation, a controlling circuit referred to
`
`as “mode logic” (960) must be present within the system 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. [Lambrecht, 26:48-
`
`56; 27:18-22]. The mode logic 960 is disclosed as being present in the chipset
`
`(106). [Lambrecht, 27:2-3; FIG. 21]. A POSA would therefore appreciate that
`
`the PCI bus (120) in Figure 21 of Lambrecht must either be operable in a
`
`normal PCI mode or in a non-standard real-time/multimedia mode optimized for
`
`multimedia transfers, but that the PCI bus cannot simultaneously support both
`
`modes of operation. [Lambrecht, 27:18-22]. A POSA would further appreciate
`
`that the non-standard real-time/multimedia mode is used only for periodic
`
`20
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 21
`
`

`
`multimedia data and the normal PCI mode is utilized for addressing and control
`
`data. [Lambrecht, 26:56-60; 27:57-62; 27:66-28:11; 28:15-19].
`
`45. The only devices in Figure 21 that are equipped with the interface
`
`logic (966) of the bus interface circuitry (962) are the multimedia devices 142D,
`
`144D, and 146D. [Lambrecht, Figure 22; 27:32-42]. Therefore, 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). The main memory (110) is not equipped with the interface logic (966) of
`
`the bus interface circuitry (962) nor is the PCI bridge chipset (106). This further
`
`underscores the fact that the multimedia mode of the PCI Expansion (120) can
`
`only be used for data transmission between the multimedia devices (142D,
`
`144D, 146D), not between the multimedia device (144D) (alleged decoder) and
`
`the main memory (110) (alleged memory).
`
`2) Lambrecht does not disclose “a decoder that requires access to the
`memory sufficient to maintain real time operation” [Independent
`claim 1]
`46. The Petition identifies the multimedia device (144D) as the
`
`decoder; the PCI expansion bus (120) as the shared bus, and the main memory
`
`(110) as the memory. [Pet. at 11, 16]. The alleged decoder (144D) does not have
`
`the capability to maintain real time operation while also accessing the alleged
`
`21
`
`
`
`PUMA Exhibit 2003
`HTC v. PUMA, IPR 2016-00923
`Page 22
`
`

`
`main memory (110). As discussed in Section IX.A.1), supra, Lambrecht does
`
`not disclose a bus that would allow the alleged decoder (144D) to access the
`
`alleged main memory (110) in real time.
`
`47.
`
`In fact, Lambrecht contemplates multimedia devices that contain
`
`dedicated multimedia memory. [See, e.g., Lambrecht Figs. 15 & 16 and related
`
`text]. The multimedia devices have access to this dedicated multimedia memory
`
`(160) in real time through the multimedia/real-time bus. [Lambrecht, 20:57-65
`
`(“In one embodiment, devices use the PCI bus 120 for arbitration, addressing
`
`and setup, and devices use the multimedia or real-time bus 130 for high speed
`
`data transfers between each other and also to/from the multimedia memory 160.
`
`Thus, in one embodiment, devices use the PCI bus 120 to provide addressing
`
`and control signa

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