throbber
Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`ARM, Ltd.
`Petitioner
`
`v.
`
`GODO KAISHA IP BRIDGE 1
`Patent Owner
`
`
`
`
`
`
`
`
`Case IPR2016-00825
`Patent No. RE43,729
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`PETITION FOR INTER PARTES REVIEW OF
`U.S. PATENT NO. RE43,729
`UNDER 35 U.S.C. §§ 311-319 AND 37 C.F.R. § 42.100 ET SEQ.
`
`
`
`Mail Stop: Patent Board
`Patent Trial and Appeal Board
`United States Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`
`
`
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`TABLE OF CONTENTS
`INTRODUCTION ............................................................................................. 1
`
`I.
`
`II. BACKGROUND ................................................................................................ 4
`
`A. The Technology Of The Challenged Claims And State Of The Prior Art.... 4
`B. Summary of the Prosecution History of the ‘729 Patent. ............................. 5
`III. REQUIREMENTS FOR INTER PARTES REVIEW UNDER 37 C.F.R. §
`42.104 ................................................................................................................10
`
`A. Grounds for Standing under 37 C.F.R. § 42.104(a) ....................................10
`B. Identification of Challenge under 37 C.F.R. § 42.104(b) ...........................11
`1. Grounds for Challenge .......................................................................11
`2. How the Challenged Claims Are to be Construed under 37 C.F.R. §
`42.104 (b)(3) .....................................................................................................15
`3.
`Level of a Person Having Ordinary Skill in the Art ..........................19
`IV. THERE IS A REASONABLE LIKELIHOOD THAT THE
`CHALLENGED CLAIMS ARE UNPATENTABLE ..................................19
`
`A. Van Hook Anticipates Claim 21 and 22 under at least 35 U.S.C. 102(e)
`And / Or Alone Renders Claims 21 and 22 Obvious. .................................20
`B. Van Hook in View of the Knowledge of One Skilled in the Art, as
`Described in Patterson, Renders Claims 21 and 22 Obvious Under 35
`U.S.C. § 103(a)............................................................................................38
`C. The MMX References Render Claims 21 and 22 Obvious Under 35 U.S.C.
`§ 103(a). ......................................................................................................43
`D. The Bases for Invalidity Are Not Duplicative, and Petitioner Requests the
`Board to Consider all Bases for Invalidity. .................................................55
`V. SECONDARY CONSIDERATIONS ............................................................57
`
`VI. NOTICES, STATEMENTS AND PAYMENT OF FEES UNDER 37
`C.F.R. § 42.8(A)(1) ...........................................................................................57
`
`A. Real Party in Interest under 37 C.F.R. § 42.8(b)(1) ....................................57
`B. Related Matters Under 37 C.F.R. § 42.8(b)(2) ...........................................58
`
`i
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`C. Lead and Back-Up Counsel Under 37 C.F.R. § 42.8(b)(3) ........................59
`D. Service Information Under 37 C.F.R. § 42.8(b)(4) .....................................59
`E. Fees under 37 C.F.R. § 42.103 ....................................................................59
`VII. CONCLUSION ...............................................................................................59
`
`
`
`
`
`ii
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`PETITIONER’ EXHIBIT LIST
`
`
`Exhibit No.
`
`Description
`
`Exhibit 1001 U.S. Pat. No. 5,847,729 (the ‘729 patent)
`
`Exhibit 1002 U.S. Pat. No. 5,734,874 to Van Hook (“Van Hook”) based upon
`
`application Ser. No. 08/236,572, filed April 29, 1994.
`
`Exhibit 1003 U.S. Pat. No. 5,822,232 to Dulong (“Dulong”) based upon
`
`application Ser. No. 08/609,601, filed March 1, 1996.
`
`Exhibit 1004
`
`Intel MMX Technology Developers Guide, March 1996
`
`Exhibit 1005
`
`Intel Architecture MMX™ Technology Programmer’s Reference
`
`Manual, March 1996, Order No. 243007-002.
`
`Exhibit 1006 MMX Technology Extension To The Intel Architecture, Peleg et
`
`al., IEEE Micro, Volume 16, Issue 4, August 1996, Page 42-50,
`
`IEEE Computer Society Press, Los Alamitos, CA, USA.
`
`Exhibit 1007
`
`Patterson et al., Computer Organization & Design The Hardware
`
`Software Interface, Morgan Kaufman Publishers, Inc. (1994)
`
`(“Patterson”) (excerpted).
`
`Exhibit 1008 U. S. Pat. No. 4,722,066 to Armer (“Armer”) based upon
`
`application Ser. No. 06/760,382, filed July 30, 1985.
`
`iii
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`Exhibit 1009 U. S. Pat. No. 4,519,031 to Magar (“Magar) based upon
`
`application Ser. No. 06/350,953, filed February 22, 1982.
`
`Exhibit 1010 U.S. Pat. No. 5,801,977 to Karp (“Karp”) based upon application
`
`Ser. No. 08/826,817, filed April 7, 1997 and claiming priority to
`
`an application filed January 17, 1995
`
`Exhibit 1011 Complaint in Case No. 2:16-cv-00134-JRG-RSP in the Eastern
`
`District of Texas
`
`Exhibit 1012
`
`File History of application no. 10/366,502 (now U.S. Pat. No.
`
`RE39,121) (excerpted)
`
`Exhibit 1013
`
`File History of application no. 11/016,920 (now U.S. Pat. No.
`
`RE43,145) (excerpted)
`
`Exhibit 1014
`
`File History of application no. 13/092,453 (now U.S. Pat. No.
`
`RE43,729) (excerpted)
`
`Exhibit 1015
`
`IEEE Std 100-1996, The IEEE Standard Dictionary of Electrical
`
`and Electronics Terms, Published by the Institute of Electrical
`
`and Electronics Engineers, Inc. (approved December 10, 1996)
`
`(excerpted).
`
`Exhibit 1016 March 5, 1996 Intel MMX Press Release.
`
`iv
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`Exhibit 1017 Declaration of Internet Archive Manager, Chris Butler, with
`
`attached Exhibit A containing Internet Archive 1996 Printout of
`
`Intel Architecture MMX™ Technology, Programmer's Reference
`
`Manual (March 1996) and Internet Archive 1996 Printout of
`
`Intel MMX Technology Developers Guide, March 1996
`
`Exhibit 1018 University of Berkeley Card Catalog entry for Patterson (Exhibit
`
`1007)
`
`Exhibit 1019 U.S. Pat. No. 5,896,493 to Rao (“Rao”) based upon application
`
`Ser. No. 08/785,374, filed January 17, 1997
`
`Exhibit 1020 U.S. Pat. No. 3,930,232, to Nissen (“Nissen”) based upon
`
`application Ser. No. 04/418641, filed November 23, 1973
`
`Exhibit 1021 Declaration of V. Thomas Rhyne
`
`Exhibit 1022
`
`Printout from IEEE database identifying citations to Patterson
`
`(Exhibit 1007)
`
`Exhibit 1023 Copy of Exhibit 1020 from IPR2015-00081 (excerpts to
`
`Patterson, Exhibit 1007)
`
`
`
`
`
`v
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`I.
`
`INTRODUCTION
`
`Petitioner ARM, Ltd. (“ARM”) requests inter partes review of claims 21-22
`
`(the “challenged claims”) of U.S. Pat. No. RE43,729 (the “‘729 patent”). The
`
`challenged claims are unpatentable because the ‘729 patent merely applies known
`
`circuitry to perform a known function called “saturation,” which is described
`
`below. The prior art and the ‘729 patent implement the claimed saturation function
`
`using identical logical circuitry (with more detail in the prior art). During the
`
`prosecution of the challenged claims, the Patent Owner1 overcame the prior art by
`
`arguing and claiming that this saturation circuitry must “operate in a single cycle.”
`
`The fundamental problems with the Patent Owner’s argument are: (a)
`
`performing saturation in a single cycle is not novel and (b) the ‘729 patent has no
`
`discussion or disclosure of the saturation circuitry operating in “one cycle.” The
`
`‘729 patent does not recite the word “cycle” nor does it contain any discussion
`
`whatsoever of the concept of “cycles” or even the concept of clocking which can
`
`be related to cycles. When challenged during prosecution to provide support for
`
`the “one cycle” limitation in at least five separate rejections occurring over six
`
`years, the Patent Owner could point only to a standard five-stage RISC2 pipeline
`
`1 “Patent Owner” refers to the current and previous assignees as the current
`
`assignee is bound by the representations made to the PTO by any prior assignee.
`
`2 RISC stands for “Reduced Instruction Set Computer.” “CISC” stands for
`
`956888.06
`
`1
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`diagram (long known in the prior art) that contained a stage called the “execute
`
`stage” which purportedly implied a “one cycle” execution.
`
`The Patent Owner’s argument created at least two separate problems with
`
`the disclosure. First, the ‘729 patent does not link pipeline stages and cycles, and
`
`the Patent Owner was forced to expressly state that such a link would come from
`
`the knowledge of one skilled in the art – which, of course, is equally applicable to
`
`such diagrams found in the prior art. Second, disclosures of five-stage processor
`
`pipelines with “execution” stages long predate the ‘729 patent. If the ‘729 patent
`
`disclosure of a five-stage pipeline sufficiently describes the “one cycle” limitation
`
`(as was successfully argued by the Patent Owner to overcome the new matter
`
`rejections), then the prior art featuring five-stage pipelines with execution stages
`
`necessarily does so as well. The prior art need only disclose as much as the ‘729
`
`patent to be invalidating. See SRI Int'l, Inc. v. Internet Sec. Sys., 511 F.3d 1186,
`
`1194 (Fed. Cir. 2008) (recognizing that the prior art need only have the same
`
`“level of technical detail” as the asserted patent to be invalidating).
`
`The Petition presents four invalidity grounds detailed below. First, U.S. Pat.
`
`No. 5,734,874 (“Van Hook”) (Ex. 1002), which predates the ‘729 patent by
`
`several years, invalidates claims 21 and 22 of the ‘729 patent. Van Hook describes
`
`a new processor instruction called the FPACK16 instruction. As shown below, the
`
`“Complex Instruction Set Computer.” Ex. 1013 at 1013-0028.
`
`956888.06
`
`2
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`FPACK16 instruction converts signed 16-bit input data to unsigned 8-bit output
`
`data. During the conversion, if the result is less than 0, then the result is saturated
`
`to 0. If, alternatively, the result is too large to fit in the 8-bit result, then the result
`
`is saturated to 255 (which can be represented in hexadecimal format as “0xFF”),
`
`which is the largest value that can be represented in an 8-bit result. If the result
`
`falls between the maximum (255) and minimum (0) then it is passed through
`
`unchanged. As shown below, Van Hook teaches the same logical circuit that the
`
`‘729 patent uses to perform the saturation (with greater detail). Therefore, if the
`
`‘729 patent adequately teaches performing these operations in “one cycle,” then so
`
`does Van Hook and Van Hook either anticipates (ground one), or renders obvious
`
`(ground two), claims 21 and 22 of the ‘729 patent. Invalidity ground three is Van
`
`Hook combined with the Patterson textbook (Ex. 1007) which shows a five-stage
`
`pipeline with a single “execute stage,” like the Patent Owner cited as disclosure for
`
`the “one cycle” limitation during prosecution.
`
`The fourth invalidity ground relies upon four Intel-related documents from
`
`1996 that describe the operation of the PACKUS instruction that Intel included in
`
`its MMX instruction set. Collectively, these are referenced to herein as the “MMX
`
`References.” The MMX References each show relevant aspects of the PACKUS
`
`instruction. Specifically, the PACKUS instruction converts a signed 16-bit integer
`
`word into an unsigned 8-bit byte value. During the conversion, if the result would
`
`956888.06
`
`3
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`be less than 0, then the result is saturated to 0. If, alternatively, the resulting value
`
`is too large to fit in the 8-bit result memory location, then the result is saturated to
`
`255 (or, in hexadecimal, 0xFF), which is the largest value that can be represented
`
`in an 8-bit unsigned result. The MMX References confirm that the PACKUS
`
`instruction executes in one cycle. Indeed, one of the MMX references taught this
`
`limitation in haec verba: “[o]n the first implementation, a Pentium processor, all
`
`MMX instructions with the exception of the multiply instructions execute in
`
`one cycle.” Ex. 1006 at 0002 (p. 43) (emphasis added).
`
`Petitioners respectfully request that inter partes review be instituted for
`
`claims 21-22 of the ‘729 patent and that these claims be cancelled.
`
`II. BACKGROUND
`
`A. The Technology Of The Challenged Claims And State Of The Prior Art.
`
`The ‘729 patent is entitled: “[P]rocessor which can favorably execute a
`
`rounding process composed of positive conversion and saturation calculation.” Ex.
`
`1001, Title. The ‘729 patent generally relates to an operation known as
`
`“saturation” in computer processors. Id. at 2:41-43. “Saturation” is generally the
`
`process of ensuring that a value that is calculated in a processor is not too large nor
`
`too small to be accurately stored by the number of bits used to store and represent
`
`such values, such as registers. E.g., Ex. 1001 at 2:41-53. “Saturation” may also be
`
`referenced in the art as “rounding,” “clipping” or “clamping.” For example, when
`
`956888.06
`
`4
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`a processor is adding multiple 8-bit numbers together, the result might require
`
`more than 8 bits to represent the total. In this situation, the result is “saturated” –
`
`meaning that the result is set to the maximum value (e.g., 255) that can be
`
`represented in the available number of bits (e.g., 8). Exhibits 1008 and 1009 show
`
`examples of how such overflow or underflow conditions might result in saturation.
`
`The Karp patent (U.S. Pat. No. 5,801,977) (cited during the prosecution of the ‘729
`
`patent) describes saturation of an input value ix as (referenced as “clipping”):
`
`
`
`Ex. 1010 at 0009, 2:1-5.
`
`Claims 21 and 22 of the ‘729 patent seek to build on this well-known
`
`concept by asserting that this saturation operation be “performed within one
`
`cycle.” However, as discussed and shown below, claims 21 and 22 do not add
`
`anything that was not already well-known in the art.
`
`B. Summary of the Prosecution History of the ‘729 Patent.
`
`U.S. Pat. App. No. 13/092,453, which resulted in the ‘729 patent, was filed
`
`on April 22, 2011 and claims priority through a chain of applications to application
`
`No. 08/980,676 filed on December 1, 1997.
`
`The Patent Owner introduced the “one cycle” limitation in the prosecution of
`
`956888.06
`
`5
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`the grandparent application 10/366,502, filed February 13, 2003 (now U.S. Pat.
`
`No. RE39121) (the “’502 Application”). On February 13, 2004, the Patent Owner
`
`submitted a Preliminary Amendment with claims that included the “within one
`
`cycle” limitation. Ex. 1012 at 1012-0002 - 0004, pp. 2-3 (claims 67, 68, and 72).
`
`On September 14, 2004, the Examiner rejected this “within one cycle” as
`
`adding new matter:
`
`The added material which is not supported by the original disclosure is as
`
`follows: The recitation in claims 53-62, 67-68, and 72 that the operation
`
`occurs “within one cycle”. The originally filed specification gives no
`
`indication that the operation happens within one cycle, and as such, to
`
`claim that it occurs in one cycle is an addition of new matter to the
`
`specification.
`
`Ex.1012 at 1012-0025 - 0026, pp. 3-4. The Examiner also held that the claims
`
`containing the “within one cycle” limitation were invalid over various references.
`
`Id. at 1012-0028, 0032, 0033, 0038 (p. 6, 10, 11 and 16).
`
`
`
`On March 15, 2005, the Patent Owner cited only the following passage as
`
`support for the “one cycle” limitation (seemingly describing an interview with the
`
`Examiner): “Applicants further directed the Examiner to Figure 12B for providing
`
`support for performance of operations in one cycle.” Ex. 1012 at 1012-0057. The
`
`disputed claims were cancelled and moved to divisional application 11/016,920
`
`956888.06
`
`6
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`(the ‘920 application) that is the parent to the ‘729 patent via a preliminary
`
`amendment filed on December 21, 2004. Ex. 1013 at 1013-0243, (e.g., claim 21).
`
`On October 21, 2008, the Examiner again rejected the “within one cycle”
`
`limitation as adding new matter, noting that “the specification as originally filed
`
`makes absolutely no mention of the operation being performed in one cycle.” Ex.
`
`1013 at 1013-0213 – 0214, pp.4-6 (emphasis added). The Examiner also rejected
`
`the claims as obvious. Id. at 1013-0021 – 0035, pp. 12-26.
`
`The Patent Owner on November 13, 2009, submitted an Amendment with
`
`the following arguments related to the “within one cycle” limitation:
`
`Although the specification does not directly contain the phrase “one cycle,”
`
`as recited in the claims, the recited limitations can be directly derived from
`
`the disclosure provided in FIGS. 12A and 12B,and col. 11, lines 1-20 and
`
`col. 19, line 50 to col. 20, line 16 of [the parent] U.S. Pat. No. 6,237,084.
`
`To one of skill in the art, it would have been understood that each interval
`
`in the horizontal direction in FIGS. 12A and 12B represents one cycle.
`
`Further, from the explanation “that the processing can be seen to be
`
`performed without confusion in the pipeline" (col. 20, lines 6-8) and the
`
`subsequent discussion at col. 20, lines 9-16,it would have been clear to
`
`those skilled in the art that the processing is executed cycle by cycle, such
`
`that the recited operations are performed “within one cycle” as recited in
`
`956888.06
`
`7
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`the claims.
`
`Id. at 1013-0192, p. 20. On December 4, 2009, the Examiner once again rejected
`
`the Patent Owner’s purported support for the “within one cycle” limitation in an
`
`extensive discussion. Id. at 1013-0129 - 0133, pp. 3-7.
`
`
`
`During an interview held on April 21, 2010, the Patent Owner presented
`
`extensive arguments for support for the “within one cycle” limitation and that the
`
`Examiner indicated that he would withdraw the new matter rejection if these
`
`arguments were made of record in a response. Id. at 1013 - 1022 (p. 2).
`
`
`
`On May 10, 2010, the Patent Owner subsequently submitted arguments that
`
`resulted in the Examiner withdrawing the new matter rejections on the “within one
`
`cycle” limitation. Id. at 1013-0094 - 0099, pp. 20-24. These arguments focused on
`
`Figure 12B and its associated text.
`
`
`
`The Patent Owner argued that Figure 12B shows a standard RISC pipeline
`
`diagram – which has been long known in the art prior to the ‘729 patent:
`
`956888.06
`
`8
`
`
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
`
`The text associated with Fig. 12B merely describes the well-known
`
`operation of a five-stage pipeline:
`
`FIG. 12B shows the execution of the matrix multiplication subroutine
`
`according to a pipeline process composed of five stages which namely are
`
`an instruction fetch stage, an instruction decoding stage, an execution
`
`stage, a memory access stage, and a register write stage. … After this, the
`
`execution stage of instruction 10:“MCSST D1” is performed at the same
`
`time as the memory access stage of instruction 9:“BCS LP1_NEXT”. The
`
`positive conversion saturation calculation processing for the matrix
`
`multiplication result of one row of elements by one column of elements is
`
`performed when the instruction located before it is in the memory access
`
`stage ….
`
`Ex. 1001 at 19:50-20:6; see also id. at 11:9-19. According to the Patent Owner,
`
`“Figure 12B illustrates a pipeline with a latency of 5 cycles and a throughput of 1
`
`cycle.” Ex. 1013 at 1013-0095, p. 21.
`
`The Patent Owner argued specifically “Diagrams for illustrating pipelined
`
`execution, such as FIG 12B of this application, were used extensively in the art,
`
`and accordingly FIG 12B would have been understood by those of skill in the art
`
`that the recited operations are executed in a single cycle, as recited in claims 53
`
`and 54.” Id. at 1013-0096, p. 22 (emphasis added).
`
`956888.06
`
`9
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`
` After this representation by the Patent Owner, the Examiner did not assert
`
`the new matter rejections related to the “one cycle” limitation in the next office
`
`action on June 17, 2010. Id. at 1013-0067 - 0073 (no new matter rejection).
`
`The Patent Owner subsequently filed application 13/092,453, which ripened
`
`into the challenged ‘729 patent. Claims 21 and 22 (presently challenged) were
`
`added by an amendment dated March 26, 2012 and both recited that the “rounding
`
`… is performed within one execution cycle.” Ex. 1014 at 1014-0017. The
`
`Examiner rejected claims 21 and 22 over the prior art. Id. at 1014-0034. After an
`
`interview (id. at 1014-0044), the claims were amended to their now-issued form.
`
`Id. at 1014-0048. The Patent Owner did not explain the deletion of “execution”
`
`from the “one execution cycle.” Id. at 1014-0048 – 0051. Claims 21 and 22
`
`subsequently were allowed on October 5, 2012. Id. at 1014-0056.
`
`III. REQUIREMENTS FOR INTER PARTES REVIEW UNDER 37 C.F.R.
`
`§ 42.104
`
`A. Grounds for Standing under 37 C.F.R. § 42.104(a)
`
`
`
`Petitioner certifies pursuant to 37 C.F.R. § 42.104(a) that the ‘729 patent is
`
`available for inter partes review, and that no Petitioner is barred or estopped from
`
`requesting inter partes review based on the grounds herein. Petitioner certifies that
`
`(i) no Petitioner owns the ‘729 patent; (ii) no Petitioner has filed a civil action
`
`challenging the validity of any claim of the ‘729 patent, and (iii) no Petitioner has
`
`956888.06
`
`10
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`been served with a complaint alleging infringement of the ‘729 patent.
`
`B. Identification of Challenge under 37 C.F.R. § 42.104(b)
`
`In view of the prior art detailed in the claim charts below, claims 21 and 22
`
`of the ‘729 patent should be found to be unpatentable and cancelled. None of the
`
`prior art references relied upon herein was considered during prosecution.
`
`1. Grounds for Challenge
`
`
`
`Petitioner requests inter partes review of the challenged claims in view of
`
`the references, and on the grounds described, below:
`
`1.
`
`Claims 21 and 22 are anticipated under 35 U.S.C. §102(e) by U.S. Pat. No.
`
`5,734,879 to Van Hook, et al. (“Van Hook”) (based upon application Ser. No.
`
`08/236,572, filed April 29, 1994 and issued March 31, 1998). (Ex. 1002, which is
`
`prior art under 35 U.S.C. §102(e)).
`
`2.
`
`3.
`
`Claims 21 and 22 are rendered obvious by Van Hook alone.
`
`Claims 21 and 22 are rendered obvious by Van Hook in view of Patterson
`
`(1994) (Ex. 1007, which is prior art under 35 U.S.C. §102(b)). Multiple United
`
`States patents issued prior to the date of the ‘729 application cite Patterson thus
`
`confirming its public availability. E.g., U.S. Pat. No. 5,535,365 (filed on October
`
`22, 1993 and issued on July 9, 1996); U.S. Pat. No. 5,555,387 (filed on June 6,
`
`1995 and issued on September 10, 1996); U.S. Pat. No. 5,619,664 (filed on March
`
`956888.06
`
`11
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`10, 1995 and issued on April 8, 1997); U.S. Pat. No. 5,630,157 (filed on October
`
`25, 1994 and issued on May 13, 1997).
`
`
`
`Additionally, IEEE publication records indicate that Patterson was cited by
`
`at least 4 separate papers published by IEEE in 1994, by at least 10 separate papers
`
`published by IEEE in 1995, by at least 7 separate papers published by IEEE in
`
`1996 and by at least 9 separate papers published by IEEE in 1997. Exhibit 1022.
`
`Exhibit 1018 contains the online card catalog excerpt from the University of
`
`California at Berkeley for Patterson. The catalog shows a “MARC” tag 005 with a
`
`value of “19930817” indicating that this card catalog entry was last modified on
`
`August 17, 1993. As of at least that date, Patterson was indexed and available in
`
`that library. The PTAB has accepted Patterson in other Inter Partes Review
`
`proceedings. See Exhibit 1023 (a copy of Exhibit 1020 from IPR2015-00081
`
`showing that Patterson was available at the Library of Congress no later than
`
`November 8, 1994); see also IPR2015-00061 (Exhibit 1020 therein); IPR2015-
`
`00059 (Exhibit 1020 therein); IPR2015-02001 (Exhibit 1030 therein).
`
`4.
`
`Claims 21 and 22 are rendered obvious under 35 U.S.C. §103 by the
`
`combination of references which describe the PACKUS instruction implemented in
`
`Intel’s MMX instruction set: (1) U.S. Pat. No. 5,822,232 to Dulong et al.
`
`(“Dulong”) based upon application Ser. No. 08/609,601, filed March 1, 1996 and
`
`issued October 13, 1998 (Ex. 1003, which is prior art under 35 U.S.C. §102(e));
`
`956888.06
`
`12
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`(2) Intel MMX Technology Developers Guide, March 1996 (Ex. 1004, which is
`
`prior art under 35 U.S.C. §102(a) and (b)); (3) Intel Architecture MMX™
`
`Technology Programmer’s Reference Manual, March 1996, Order No. 243007-
`
`002 (Ex. 1005, which is prior art under 35 U.S.C. §102(a) and (b)); and (4) MMX
`
`Technology Extension To The Intel Architecture, Peleg et al., IEEE Micro,
`
`Volume 16, Issue 4, August 1996, Page 42-50, IEEE Computer Society Press, Los
`
`Alamitos, CA, USA (Ex. 1005, which is prior art under 35 U.S.C. §102(a) and (b))
`
`(collectively, the “MMX References”).
`
`
`
`The two Intel manuals (Exs. 1004 and 1005) were publicly available as of
`
`March 1996. Both exhibits are dated March 1996. See Ex. 1004 at 0002 (header);
`
`Ex. 1005 at 0001. Ex. 1004 states that the information is provided “for Developers
`
`and ISVs” and is distributed by “Intel® Developer Services” and lists the website
`
`“www.intel.com/IDS.” Ex. 1004 at 0001. Ex. 1005 states: “Copies of documents
`
`which have an ordering number and are referenced in this document, or other Intel
`
`literature, may be obtained from [Intel at the specified address and phone
`
`number].” Exhibit 1005 at 0002. On March 5, 1996, Intel announced the MMX
`
`technology with a press release. Ex. 1016. That press release states that the
`
`“Developers who are interested in obtaining additional information about MMX
`
`technology, including a Programmer's Reference Manual, should consult Intel's
`
`site
`
`on
`
`the World Wide Web
`
`at URL
`
`http://www.intel.com/pc-
`
`956888.06
`
`13
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`supp/multimed/mmx/index.htm.” Id. That these materials were available to third
`
`parties is also evidenced by U.S. Pat. 5,896,493, which issued from U.S. Pat.
`
`Application No. 08/785,374, filed in the United States Patent Office on January 17,
`
`1997, which expressly incorporated by reference the documents of Ex. 1004 and
`
`Ex.1005. See Ex. 1019 at 2:37-41 (“This processor and multimedia technology is
`
`described in the ‘Intel Architecture MMX(TM) Technology, Programmer’s
`
`Reference Manual,’ March 1996, and the ‘Intel MMX(TM) Technology.
`
`Developer's Guide’ which are hereby incorporated by reference in their entirety.”),
`
`
`
`Also, as of 1996, Intel’s internet website included copies of both the MMX
`
`Programmer’s Reference Manual (Ex. 1005) and the MMX Developers Guide (Ex.
`
`1004). Copies of these manuals are available from the Internet Archive on
`
`webpages dated from 1996. Ex. 1017 at 1017-0005 – 0062 (a copy of Ex. 1005
`
`that was archived in 1996 from the publicly accessible Intel website); Id. at 1017-
`
`0063 - 0098 (a copy of Ex. 1004 that was archived in 1996 from the publicly
`
`accessible Intel website). The Intel website is an “on-line database or Internet
`
`publication that is considered to be ‘printed publication’ within the meaning of 35
`
`U.S.C. §§ 102(a) and (b).” MPEP § 2128; see also Voter Verified, Inc. v. Premier
`
`Election Solutions, Inc., 698 F.3d 1374, 1380 (Fed. Cir. 2012) (online article that
`
`had been available on a public website by the critical date qualified as a “printed
`
`publication” under 35 U.S.C. § 102(b)). Moreover, the PTO has long accepted the
`
`956888.06
`
`14
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`Wayback Machine as a proper means for establishing a website as prior art. See
`
`IPR2013-00086, Paper 66 at 29-31 (accepting web sites as printed publications and
`
`citing cases accepting Wayback Machine materials as sufficient authentication).
`
`
`
`Also, the Intel MMX Technology Developers Guide cross-references, and
`
`explains that additional information on the instruction format can be found in, the
`
`“Intel Architecture MMXTM Technology Programmers Reference Manual, Intel
`
`Corporation (Order Number 243007)” which is Exhibit 1005. Ex. 1004 at 0007.
`
`
`
`To the extent that Patent Owner attempts to challenge the public availability
`
`of either of Exs. 1004 or 1005, Petitioner has included a declaration from the
`
`Internet Archive organization establishing the authenticity and date of the printouts
`
`in Exhibit 1017. Petitioner would also expect to introduce a declaration or
`
`deposition testimony from Intel Corporation confirming the public availability of
`
`Exhibits 1004 and 1005 prior to the earliest priority date of the ‘729 patent.
`
`
`
`Section IV identifies where the prior art teaches each element of claims 21
`
`and 22. 37 C.F.R. § 42.104(b)(4). Exhibit numbers of supporting evidence relied
`
`upon to support the challenges and the relevance of the evidence to the challenges
`
`raised are in a table at p. iii and in Section III.B. 37 C.F.R. § 42.104(b)(5).
`
`2.
`
`How the Challenged Claims Are to be Construed under 37 C.F.R. §
`
`42.104 (b)(3)
`
`In this proceeding, claim terms are given their broadest reasonable
`
`956888.06
`
`15
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`interpretation consistent with the specification and prosecution history. See Office
`
`Patent Trial Practice Guide, 77 Fed. Reg. 48756, 48766 (Aug. 14, 2012). The
`
`broadest reasonable interpretation of the relevant claim terms is discussed below.
`
`Claim terms that are not addressed below are believed to require no additional
`
`clarification for purposes of the present IPR.3
`
`a. “operations which are performed in one cycle”
`
`Based upon the Patent Owner’s statements and positions taken during
`
`prosecution, this claim term should be construed to mean that the cited operations
`
`are performed within a single processor stage.
`
`This claim term was a critical claim term during prosecution yet the
`
`specification does not provide any support or description of this term. As noted
`
`above, the Examiner rejected the “within one cycle” limitation as unsupported by
`
`the specification in at least five separate rejections over a period of six years.
`
`As discussed above, the Patent Owner overcame the at least five new matter
`
`rejections after six years by stating unequivocally that pipeline diagrams, such as in
`
`Figure 12B of the ‘729 patent, would be understood to disclose single cycle
`
`operation. See supra at 9-10. (discussing Ex. 1013 at 1013-0096, pp. 22).
`
`the Patent Owner’s express representations during
`If one accepts
`
`
`3 Petitioner does not acknowledge that any claim or claim term complies with 35
`
`U.S.C. § 112, through any construction for terms that follow, or otherwise.
`
`956888.06
`
`16
`
`

`
`Case IPR2016-00825
`Petition for Inter Partes Review of Patent RE43,729
`
`prosecution, the ‘729 specification might be said to teach that elements 21(a)
`
`through (c) occur in the “execution stage.” This is wholly unsurprising and not
`
`novel because all of the arithmetic operations performed in a standard five-cycle
`
`RISC processor are performed in the “executi

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