throbber
Paper No. 12
`January 13, 2021
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`INTEL CORPORATION,
`Petitioner,
`v.
`FG SRC LLC,
`Patent Owner.
`
`
`
`
`
`
`
`IPR2020-01449
`Patent No. 7,149,867
`
`
`
`
`
`
`
`
`
`
`
`
`
`PATENT OWNER’S SUR-REPLY TO
`PETITIONER’S REPLY TO PRELIMINARY RESPONSE
`
`

`

`
`
`LIST OF EXHIBITS
`
`2004
`
`2005
`
`2006
`
`2007
`2008
`
`Exhibit No. Descriptions
`Declaration of Dr. Vojin Oklobdzija
`2001
`Cray, Britannica Online Encyclopedia
`2002
`Declaration of Brandon Freeman dated 10/25/18
`2003
`SRC Labs LLC and Saint Regis Mohawk Tribe v. Microsoft
`Corporation, No. 2:18-cv-00321-JLR, Dkt. 125 (W.D. Wash. Oct.
`25, 2018)
`Plaintiff’s Original Complaint For Patent Infringement in FG SRC
`LLC v. Intel Corp., No. 6:20-cv-00315-ADA (W.D. Texas), filed
`April 24, 2020
`Plaintiff’s First Amended Complaint For Patent Infringement in
`FG SRC LLC v. Intel Corp., No. 6:20-cv-00315-ADA (W.D.
`Texas), filed April 24, 2020
`Declaration of Mark Wollgast dated 09/10/18
`Xilinx, Inc. v. Saint Regis Mohawk Tribe, IPR2018-0195
`COTS Journal, UAVs Lead Push for Embedded Supercomputing
`Press Release: SRC Computers Chosen by Lockheed Martin for
`U.S. Army Program
`Declaration of Henning Schmidt
`Declaration of Henning Schmidt, Exhibit A, IEEE Xplore:
`Advanced Search
`Declaration of Henning Schmidt, Exhibit B, IEEE Xplore:
`Advanced Search Results
`Declaration Of Ryan Kastner, Ph.D. In Support Of FG SRC
`LLC’s Opening Claim Construction Brief in FG SRC LLC v. Intel
`Corp., No. 6:20-cv-00315-ADA (W.D. Texas), filed April 24,
`2020
`Peter McMahon, High Performance Reconfigurable Computing for
`Science and Engineering Applications (Thesis Oct. 2006).
`Caliga, Delivering Acceleration: The Potential for Increased HPC
`Application Performance Using Reconfigurable Logic
`D. A. Buell, D. Caliga, J. P. Davis, G. Quan, “The DARPA
`boolean equation benchmark on a reconfigurable computer,”
`Proceedings of the Military and Aerospace Programmable Logic
`Devices (MAPLD) Conference, Washington, DC, 8-10 September
`
`2009
`2009-1
`
`2009-2
`
`2010
`
`2011
`
`2012
`
`2013
`
`
`
`i
`
`

`

`
`
`
`
`
`
`Exhibit No. Descriptions
`2004
`
`2014
`
`2015
`
`2016
`
`2017
`
`2018
`
`2019
`
`2020
`
`2021
`
`2022
`2023
`
`2024
`
`2025
`
`2026
`
`El-Araby, The Promise of High-Performance Reconfigurable
`Computing
`FG SRC LLC’s Opening Claim Construction Brief in FG SRC
`LLC v. Intel Corp., No. 6:20-cv-00315-ADA (W.D. Texas),
`filed April 24, 2020
`Kerr Machine Co. d/b/a Kerr Pumps v. Vulcan Industrial
`Holdings, LLC, No. 6:20-cv-00200, Text Order dated Aug. 2, 2020
`(W.D. Tex.)
`MultiMedia Content Mgmt LLC v. Dish Network L.L.C., No. 6:18-
`cv-00207, Dkt. 73 (W.D. Tex.)
`Solas OLED v. Dell Techs. Inc., No. 6:19-cv-00514, Text Order
`dated June 23, 2020
`Kerr Machine Co. v. Vulcan Indus. Holdings, LLC, No. 6:20-cv-
`200, Dkt. 28 (W.D. Tex. July 31, 2020)
`Kerr Machine Co. v. Vulcan Indus. Holdings, LLC, No. 6:20-cv-
`200, Dkt. 24 (W.D. Tex. June 14, 2020)
`Kerr Machine Co. v. Vulcan Indus. Holdings, LLC, No. 6:20-cv-
`200, Dkt. 12 (W.D. Tex., June 14, 2020)
`Email from J. Yi to Counsel (Aug. 3, 2020)
`FG SRC LLC v. Intel Corp., No. 1:20-cv-00834, Dkt. 48 (W.D.
`Tex. Nov. 23, 2020) (Amended Schedule)
`Continental Intermodal Group - Trucking LLC v. Sand Revolution
`LLC, No. 7:18-cv-00147, Text Order dated July 22, 2020 (W.D.
`Tex.)
`Solas OLED v. Dell Techs. Inc., No. 6:19-cv-00515, Text Order
`dated Jun. 23, 2020
`2019-07-11 - DirectStream MSFT - Huppenthal Declaration
`
`ii
`
`

`

`I.
`
`INSTITUTION SHOULD BE DENIED UNDER FINTIV
`Fintiv Factor 1 strongly favors denial because Petitioner’s unsupported
`
`speculation that the Court might grant a post-institution stay (Paper 11, 1) is
`
`contradicted by Patent Owner’s direct evidence that a stay is highly unlikely. Paper
`
`9, 3-4. Regarding Factors 2-3, trial is set for November 8, 2021, and “the Court will
`
`not move the trial date except in extreme situations.” Order Governing Proceedings
`
`for Patent Cases (v3.2), available at https://tinyurl.com/y4nxokvz. Even assuming
`
`the “extreme situation” of a continuance of the trial date (commensurate with the
`
`one-month Markman extension), the related litigation will go to trial in December
`
`2021, two months before a final written decision. This schedule strongly favors
`
`denying institution. Philip Morris Prod., S.A. v. RAI Strategic Holdings, Inc.,
`
`IPR2020-00921, Paper 9, at 14-15 (PTAB Nov. 16, 2020). Petitioner’s Reply does
`
`not address the remaining Factors, which also favor denial.
`
`Given the specific factual circumstances here, an IPR would not be an
`
`“expeditious, efficient, and less expensive alternative to district court litigation,” as
`
`these proceedings would be needlessly duplicative of the district court action.
`
`II. THE PRINTED PUBLICATION STANDARD HAS NOT BEEN MET
`Petitioner’s Reply merely reinforces that Dr. Gupta only “believes” Zhang,
`
`Gupta, and Chien may have been disseminated based on an undefined “general
`
`practice in the scientific and engineering community.” This contrasts sharply with
`
`
`
`1
`
`

`

`
`
`cases in which the declarant unequivocally testified as to the specific practices of the
`
`specific organization, including that he actually received a copy of the asserted
`
`publication. Laboratory Corp. of America Holdings v. Quest Diagnostics, IPR2019-
`
`00738, Paper 14 at 13 (PTAB Sept. 4, 2019); IPR2019-00738, Ex. 1002, ¶34.
`
`As to online publication, typical direct evidence of publication is not present
`
`here. See Hulu, LLC v. Sound View Innovations, LLC, IPR2018-01039, Paper 39 at
`
`18 (PTAB POP Dec. 20, 2019) (online publication supported by “office manager of
`
`the Internet Archive”). An online search for the asserted publication is probative
`
`evidence if it includes terms that appear in the challenged patent’s specification. In
`
`re Lister, 583 F.3d 1307, 1315 (Fed. Cir. 2009). Patent Owner demonstrated that
`
`such an online search here is fruitless. Paper 9, 30-31. Under Lister and its progeny,
`
`Petitioner’s online publication theory therefore fails. See Acceleration Bay, LLC v.
`
`Activision Blizzard, Inc., 908 F.3d 765, 774 (Fed. Cir. 2018).
`
`Mr. Munford’s testimony likewise falls short. In Quest, the petitioner
`
`submitted a declaration containing specific information about the particular library
`
`and unequivocal testimony that a copy of the reference was actually received.
`
`IPR2019-00738 at 12-15. No such evidence is presented here. Petitioner’s assertion
`
`that shelving of a reference is unimportant (Paper 11, 4) is wrong: “[P]articularly for
`
`manuscripts or dissertations stored in libraries, courts may inquire whether a
`
`reference was sufficiently indexed, catalogued, and shelved.” Hulu, IPR2018-01239
`
`
`
`2
`
`

`

`
`
`at 9. Petitioner’s other authority does not relate to references stored in a library at
`
`all. Medtronic, Inc. v. Barry, 891 F.3d 1368, 1380-81 (Fed. Cir. 2018).
`
`III. PETITIONER MISCHARACTERIZES THE “RECONFIGURABLE
`PROCESSOR”
`Petitioner mischaracterizes the agreed construction of “reconfigurable
`
`processor” by omitting key language that contradicts its position. Paper 11, 4. The
`
`complete and correct construction is “a computing device
`
`that contains
`
`reconfigurable components such as FPGAs and can, through reconfiguration,
`
`instantiate an algorithm as hardware.” Conventional processors cannot instantiate an
`
`algorithm as hardware. Ex. 2001, ¶51 (“conventional computers utilize general
`
`purpose processors [whose] hardware is fixed.”); Id., ¶77 (Zhang “relies on a
`
`conventional processor, and does not disclose or even consider the use of
`
`reconfigurable processors as that term is used in the ’867 Patent. For that reason,
`
`Zhang’s application remains in software.”).
`
`Petitioner’s argument that a conventional processor can be a reconfigurable
`
`processor simply by utilizing the “small blocks of programmable logic implemented
`
`into key elements of a baseline architecture” to enable “the customization of
`
`architectural mechanisms and policies to match an application” is wrong for multiple
`
`reasons. First, Petitioner’s interpretation is indefinite because it is unclear how much
`
`reconfigurable
`
`logic
`
`is needed
`
`to convert a conventional processor
`
`to
`
`“reconfigurable processor.”
`
`
`
`3
`
`

`

`
`
`Second, the ’867 Patent itself defines “reconfigurable processor” as: (1) a
`
`computing device that “contains reconfigurable components such as FPGAs,” and
`
`(2) a computing device that “can, through reconfiguration, instantiate an algorithm
`
`as hardware.” Even if a conventional processor utilized some reconfigurable
`
`components, it would not meet the second criteria because it is the computing
`
`device—i.e., the processor—that must instantiate an algorithm as hardware, which
`
`a conventional processor cannot do.
`
`Third, the specification of the ’867 Patent leaves no doubt that its
`
`“reconfigurable processor” must comprise a computational unit (i.e., computing
`
`device or processor) that is indeed reconfigurable, in addition to other reconfigurable
`
`components, such as a memory hierarchy: “A reconfigurable processor (RP) 100
`
`implements direct executable logic (DEL) to perform computation, as well [as] a
`
`memory hierarchy.” Ex. 1001, 5:59-61; see also id., Abstract; id., 6:15-16 (“The
`
`reconfigurable processor 100 also implements user-defined computational logic . . .
`
`constructed by programming an FPGA to implement a particular interconnection of
`
`computational functional units.”); id., Figs. 1 and 2; id., 4:2-3 (“the computational
`
`unit [is] configured by a program”); id., 4:24-26 (same).
`
`Fourth, the ’867 Patent explicitly contrasts the prior art (conventional
`
`microprocessor) with the invention (reconfigurable computational unit):
`
`In the common case in which static computing hardware resources are
`used (e.g., a conventional microprocessor), the computer program is
`
`
`
`4
`
`

`

`
`
`compiled into . . . [executable code that] is generated specifically for a
`particular hardware platform. In this manner, the computer program is
`adapted to conform to the limitations of the static hardware platform.
`However, the compilation process makes many compromises based on
`the limitations of the static hardware platform. … Alternatively, an
`algorithm can be defined in a high-level language then compiled into
`DEL. . . . Computation is performed by reconfiguring a reconfigurable
`processor with the DEL and flowing data through the computation.
`
`Ex. 1001, 6:32-46 (emphasis added). Nowhere does the ’867 Patent or Petitioner’s
`
`expert indicate that the computational unit of its RP may be a conventional
`
`processor. In fact, “the ’867 Patent teaches the use of reconfigurable processors in
`
`lieu of
`
`conventional microprocessors
`
`/ CPUs,”
`
`i.e.,
`
`“[conventional]
`
`microprocessors/CPUs are
`
`replaced with application
`
`specific
`
`functional
`
`units/computational elements implemented in reconfigurable logic.” Ex. 2001, ¶66
`
`(emphasis added); id., at ¶133. Petitioner’s interpretation is explicitly contradicted
`
`by the patent itself as well as the only expert testimony on record.
`
`Zhang, by contrast, explicitly teaches away from “the use of reconfigurable
`
`logic for application-specific functional units or computational logic.” Ex. 2001, ¶66
`
`(emphasis added). Zhang explicitly uses a conventional processor, and “envisions
`
`only small hardware adaptations in processor functional units (perhaps in the
`
`peripheral components).”
`
`Id., ¶65. Petitioner’s argument
`
`that Zhang’s
`
`“computational algorithms, including Zhang’s matrix multiplication algorithms, . . .
`
`are implemented in reconfigurable processing elements” (Paper 11, 5) is
`
`demonstrably false. Only the prefetching for the multiplication algorithm is
`
`
`
`5
`
`

`

`
`
`implemented in reconfigurable processing elements; the actual matrix multiplication
`
`runs on the host microprocessor. Ex. 2001, ¶79. Petitioner’s citations (Paper 11, 5)
`
`lend no support. See Paper 1, 42-43 (concerning only prefetch algorithm, not matrix
`
`multiplication; id., 64 (discussing only “computational unit” that runs on
`
`conventional CPU shown in Zhang Fig. 2); id., 67-68 (matrix multiplication not
`
`addressed at all).
`
`Petitioner’s new file history argument (Paper 11 at 4) is waived because it is
`
`a new argument in a Reply. CTPG at 14. Regardless, the Examiner noted that Paulraj
`
`shows reconfigurable logic “within” its CPU. Ex. 1002-105. Zhang does not.
`
`Paulraj, Fig. 6
`
`Zhang, Ex. 1003, Fig. 2
`
`
`
`
`Notably, Paulraj was unsuccessfully asserted as prior art to the ’867 Patent in SRC
`
`Labs, LLC et al., v. Amazon Web Services, Inc., et al., No. 2:18-cv-00317 (W.D.
`
`Washington), filed Feb. 26, 2018.
`
`Petitioner’s remaining arguments are contrary to the evidence: the claim
`
`language explicitly requires that “first memory and data prefetch unit are configured
`
`to conform to needs of the algorithm” (Ex. 1001, 12:51-52); the characterization of
`
`
`
`6
`
`

`

`
`
`Zhang (Paper 11, 6-7) is wrong because either the application remains in software
`
`and is executed on general purpose hardware, or it is used to render special purpose
`
`hardware, and Petitioner’s argument completely eliminates the difference between
`
`static and reconfigurable computing. Patent Owner’s positions (Paper 11, 7) are
`
`based on Zhang itself (Ex. 1003, Table 1) and expert testimony (Ex. 2001, ¶106(c)
`
`(“Zhang only discloses L1 and L2 cache line sizes of 32 or 64 bytes versus the matrix
`
`element size of 40 bytes.”); see also id., ¶¶92, 95, and 130).
`
`IV. PATENT OWNER HAS DEMONSTRATED A NEXUS
`The nexus between the success of Patent Owner’s MAP supercomputer and
`
`the ’867 Patent is directly established by the evidence. The ability to automatically
`
`instantiate algorithms resulted in improved processing capacity, such as giving “the
`
`MAP the ability to get data from a variety of memories, having different data widths,
`
`and reformat that data into the width of the function that is consuming it before it
`
`needs to consume it.” Ex. 2026, ¶73. The invention is thus directly responsible for
`
`performance improvements including, for example, processing speed gains because
`
`“a new data value can be input into the function unit every clock [cycle].” Ex. 2012,
`
`8. These advantages directly translated
`
`into commercial success: “These
`
`performance, size and power consumption improvements continue to demonstrate
`
`SRC/DirectStream’s leading edge capabilities that Lockheed Martin’s own
`
`procurement process showed no other vendor could match.” Ex. 2006, ¶¶20, 21.
`
`
`
`7
`
`

`

`
`
`
`
`
`
`Respectfully submitted,
`
`
`/s/ Jay P. Kesan
`
`DiMuroGinsberg, PC-
`DGKeyIP Group
`Jay P. Kesan
`Reg. No. 37,488
`Cecil E. Key (admission pro hac vice
`pending)
`1750 Tysons Blvd., Suite 1500
`Tysons Corner, VA 22102
`Phone: 703-289-5118
`jkesan@dimuro.com
`ckey@dimuro.com
`
`Michael W. Shore
`mshore@shorechan.com
`Alfonso G. Chan
`achan@shorechan.com
`Ari B. Rafilson
`arafilson@shorechan.com
`SHORE CHAN DEPUMPO LLP
`901 Main Street, Suite 3300
`Dallas, Texas 75202
`Telephone: 214-593-9110
`Facsimile: 214-593-9111
`
`
`
`
`
`
`
`
`
`8
`
`

`

`
`
`
`
`
`
`
`
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 C.F.R. §§ 42.6(e)(4) and 42.25(b), the undersigned certifies
`
`that on January 13, 2021, a complete copy of Patent Owner’s Sur-Reply to
`
`Petitioner’s Reply to Preliminary Response was filed electronically through the
`
`Patent Trial and Appeal Board’s PTABE2E System and provided, via electronic
`
`service, to the Petitioner by serving the correspondence address of record as
`
`follows:
`
`Brian C. Nash, brian.nash@pillsburylaw.com
`PILLSBURY WINTHROP SHAW PITTMAN LLP
`401 Congress Avenue, Ste. 1700
`Austin, Texas 78701
`
`Evan Finkel, evan.finkel@pillsburylaw.com
`PILLSBURY WINTHROP SHAW PITTMAN LLP
`725 South Figueroa Street, Ste. 2800
`Los Angeles, CA 90017-5406
`
`
`Matthew W. Hindman, matthew.hindman@pillsburylaw.com
`PILLSBURY WINTHROP SHAW PITTMAN LLP
`2550 Hanover Street
`Palo Alto, CA 94304
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Cecil E. Key
`Cecil E. Key
`
`
`
`
`
`
`
`9
`
`

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