throbber
Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 1 of 11
`
`UNITED STATES DISTRICT COURT
`
`FOR THE WESTERN DISTRICT OF TEXAS
`
`WACO DIVISION
`
`Plaintiff,
`
`
`
`v.
`
`
`
`Case No. 6:21-cv-00898-ADA
`
`
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`
`
`
`
`
`
`
`ALMONDNET, INC.,
`
`
`
`
`
`AMAZON.COM, INC.; AMAZON.COM
`SERVICES LLC; and AMAZON WEB
`SERVICES, INC.,
`
`
`
`
`
`Defendants.
`
`
`
`
`
`PLAINTIFF’S REPLY IN SUPPORT OF:
`
`(1) MOTION TO STRIKE AND EXCLUDE CERTAIN OPINIONS OF DR. HENRY
`HOUH REGARDING ENABLEMENT AND WRITTEN DESCRIPTION; AND
`
`(2) MOTION FOR PARTIAL SUMMARY JUDGMENT OF NO INVALIDITY BASED
`ON LACK OF ENABLEMENT AND LACK OF WRITTEN DESCRIPTION
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 2 of 11
`
`TABLE OF CONTENTS
`
`I. AMAZON FAILS TO SHOW DR. HOUH’S ENABLEMENT OPINIONS ARE
`RELIABLE ......................................................................................................................... 1
`
`II. AMAZON FAILS TO SHOW DR. HOUH’S WRITTEN DESCRIPTION
`OPINIONS ARE RELIABLE ........................................................................................... 5
`
`III. AMAZON’S “BURDEN AND ORDER OF PROOF” ARGUMENTS ARE NON-
`SEQUITURS ....................................................................................................................... 6
`
`
`
`
`
`
`
`i
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 3 of 11
`
`Cases
`
`TABLE OF AUTHORITIES
`
`Alcon Rsch. Ltd. v. Barr Lab'ys, Inc.,
`745 F.3d 1180 (Fed. Cir. 2014) ................................................................................................. 6
`
`Amgen Inc. v. Sanofi,
`598 U.S. 594 (2023) .............................................................................................................. 1, 2
`
`Auto. Techs. Int'l, Inc. v. BMW of N. Am., Inc.,
`501 F.3d 1274 (Fed. Cir. 2007) ................................................................................................. 5
`
`Baxalta Inc. v. Genentech, Inc.,
`579 F. Supp. 3d 595 (D. Del. 2022) .......................................................................................... 5
`
`Durel Corp. v. Osram Sylvania Inc.,
`256 F.3d 1298 (Fed. Cir. 2001) ................................................................................................. 5
`
`Effective Expl., LLC v. BlueStone Nat. Res. II, LLC,
`2017 WL 5895164 (E.D. Tex. Nov. 13, 2017) .......................................................................... 6
`
`Genentech, Inc. v. Novo Nordisk A/S,
`108 F.3d 1361 (Fed. Cir. 1997) ................................................................................................. 2
`
`Hybritech Inc. v. Monoclonal Antibodies, Inc.,
`802 F.2d 1367 (Fed. Cir. 1986) ................................................................................................. 2
`
`Idenix Pharms. LLC v. Gilead Sciences Inc.,
`941 F.3d 1149 (Fed. Cir. 2019) ................................................................................................. 2
`
`Koito Mfg. Co. v. Turn-Key-Tech, LLC,
`381 F.3d 1142 (Fed. Cir. 2004) ................................................................................................. 2
`
`Liebel-Flarsheim Co. v. Medrad, Inc.,
`481 F.3d 1371 (Fed. Cir. 2007) ................................................................................................. 5
`
`McRO, Inc. v. Bandai Namco Games Am. Inc.,
`959 F.3d 1091 (Fed. Cir. 2020) ............................................................................................. 1, 2
`
`Nuvo Pharms. (Ireland) Designated Activity Co. v. Dr. Reddy's Lab'ys Inc.,
`923 F.3d 1368 (Fed. Cir. 2019) ................................................................................................. 6
`
`TQ Delta, LLC v. 2Wire, Inc.,
`373 F. Supp. 3d 509 (D. Del. 2019) .......................................................................................... 3
`
`Trustees v. Everlight,
`896 F.3d 1357 (Fed. Cir. 2018) ................................................................................................. 2
`
`
`
`
`
`ii
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 4 of 11
`
`To save Dr. Houh’s enablement opinions from being precluded, Amazon fails to address
`
`the Federal Circuit’s guidance from McRO and—surprisingly—seems to make up a new test for
`
`enablement that requires looking only at the “express disclosure” of a specification, based
`
`supposedly on the Supreme Court’s recent Amgen decision. Amazon further fails to establish Dr.
`
`Houh should be permitted to
`
`
`
` To save Dr. Houh’s written description opinions, Amazon’s
`
`response, like Dr. Houh’s report, conflates the tests and analysis required for each of enablement
`
`and written description. It is true that courts have observed that the enablement and written
`
`description issues “rise and fall together,” but this neither absolves Dr. Houh’s failure to perform
`
`the required analysis with the correct legal test nor permits him to cure the failure by later
`
`reciting the correct legal test in deposition and claiming that he did, in fact, do the analysis.
`
`I.
`
`Amazon Fails to Show Dr. Houh’s Enablement Opinions are Reliable
`
`Amazon does not dispute that Dr. Houh’s enablement opinions are
`
`
`
`seriously dispute Dr. Houh never considered the scope of the prior art, the background
`
`knowledge of a POSITA, or the predictability of the art, in forming his enablement conclusions,
`
`. Amazon does not
`
`even though his ultimate conclusion is that
`
`
`
`
`
`
`
`
`
`. Amazon does not
`
`even try to reconcile the tension between Dr. Houh’s conclusion and his failure to perform the
`
`underlying analysis needed to make that conclusion reliable.
`
`Instead, Amazon makes up law. It argues that focusing exclusively on the express words
`
`
`
`1
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 5 of 11
`
`of the specification—while ignoring what is well known to a POSITA—is not only permitted,
`
`but supposedly required by Amgen Inc. v. Sanofi, 598 U.S. 594 (2023). See Dkt. 164, at 3
`
`(asserting the “required inquiry” under Amgen is analysis “based on the express disclosure in
`
`the specification” (emphasis by Amazon)). Amazon creates supposed precedent for this rule by
`
`selectively quoting Genentech, Inc. v. Novo Nordisk A/S, 108 F.3d 1361 (Fed. Cir. 1997) and
`
`Idenix Pharms. LLC v. Gilead Sciences Inc., 941 F.3d 1149, 1159 (Fed. Cir. 2019), and Trustees
`
`v. Everlight, 896 F.3d 1357, 1363 (Fed. Cir. 2018). Id. at 2, 4-6.
`
`No case cited by Amazon provides support for its rule about looking only at the “express
`
`disclosure” of the specification to analyze enablement. Amgen did not change the relevant law: a
`
`“patent need not teach, and preferably omits, what is well known in the art.” McRO, Inc. v.
`
`Bandai Namco Games Am. Inc., 959 F.3d 1091, 1102 (Fed. Cir. 2020). This rule remains
`
`undisturbed by Genentech and Idenix, whose language on which Amazon relies is about how the
`
`specification which “must supply the novel aspects of an invention in order to constitute
`
`adequate enablement.” Idenix, 941 F.3d at 1159 (quoting Genentech, 108 F.3d at 1366).
`
`Moreover, McRO’s reminder that a patent need not expressly teach well-understood and
`
`routine concepts for an invention to be enabled has been the law for decades. See Koito Mfg. Co.
`
`v. Turn-Key-Tech, LLC, 381 F.3d 1142, 1156 (Fed. Cir. 2004) (“This Court has repeatedly
`
`explained that a patent applicant does not need to include in the specification that which is
`
`already known to and available to one of ordinary skill in the art.”); Hybritech Inc. v.
`
`Monoclonal Antibodies, Inc., 802 F.2d 1367, 1384 (Fed. Cir. 1986) (specification “need not
`
`teach, and preferably omits, what is well known in the art”).
`
`Amazon’s treatment of McRO, Dkt. 164 at 3-4, simply ignores the law. Amazon does not
`
`deny the controlling effect of the McRO language, but, instead, misdirects the Court’s focus back
`
`to what the specification “expressly” teaches. Amazon says that Dr. Houh opined that “the
`
`
`
`2
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 6 of 11
`
`specification should have, but failed to, supply any description of how to make and use certain
`
`claimed limitations.” Id. at 4 (identifying “sharing and matching cookie information” as not
`
`described by the specification, saying “[n]othing in the record suggests … that the specification
`
`explicitly indicates that [the] claimed limitation was known to POSITA.”). First, no authority
`
`supports Amazon’s argument that a specification must “indicate” certain things were “known to
`
`a POSITA” for those things to be relevant to enablement.1 Second, Amazon’s argument
`
`underscores AlmondNet’s point: Dr. Houh’s opinion about
`
`
`
`.
`
`TQ Delta, LLC v. 2Wire, Inc., 373 F. Supp. 3d 509 (D. Del. 2019) is directly analogous.
`
`TQ Delta granted summary judgment to the patentee on lack of enablement where the
`
`defendant’s expert’s “report focuses wholly on what the specification discloses and ignores that
`
`information ‘already known to and available to one of ordinary skill in the art’ need not be
`
`included in the specification for the patent to be enabled.” Id. at 524-25. This failure is not
`
`simply one that renders the expert vulnerable to cross-examination. It means the defendant
`
`“failed to make a sufficient showing on an essential element of its case with respect to which it
`
`has the burden of proof.” Id. at 525.
`
`Amazon next attempts to transform its failure into a strawman dispute about whether
`
`application of the Wands factors is mandatory. Dkt. 164, at 2-4. But AlmondNet’s argument here
`
`is not that Dr. Houh failed to consider the Wands factors or that his failure to do any “explicit”
`
`analysis of one factor or another made his opinions unreliable. Rather, AlmondNet’s argument is
`
`that Dr. Houh drew conclusions that required a minimum amount of factual analysis that was
`
`
`1 Notably, McRO states the specification preferably “omits”—not “indicates”—known material.
`
`
`
`3
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 7 of 11
`
`neither performed nor provided, whether “explicitly” or not.2 Such baseless conclusions fail to
`
`raise a dispute of material fact and should be excluded as unreliable.
`
`Next, Amazon accuses AlmondNet of “mischaracterizing” Dr. Houh’s testimony. Dkt.
`
`164, at 5. But instead of explaining how the testimony quoted in the Motion “mischaracterizes”
`
`Dr. Houh’s testimony, Amazon excerpts another part of the testimony to assert that he was
`
`actually saying he had no opinions about “prior art invalidity,” as opposed having no opinions
`
`about the scope of prior art for the enablement. Id. This argument presents a false dichotomy.
`
`Both statements can be (and, in this case, are) true: Dr. Houh had no opinions about the prior art
`
`in Amazon’s invalidity case or any opinions about the scope of prior art for his Section 112
`
`analysis. Compare Ex. 2, 132:13-25 and 125:19-20, with id. at 132:7-12.
`
`Amazon’s wishful thinking can neither rewrite Dr. Houh’s deposition transcript nor
`
`change how his report contains no discussion or analysis about the scope of the prior art for
`
`enablement. Amazon’s quotations from Dr. Houh’s report (Dkt. 164, at 5-6) are not an analysis
`
`of what information is “already known … to one of ordinary skill in the art” and which “need not
`
`be included in the specification for the patent to be enabled.” TQ Delta, 373 F. Supp. 3d at 525.
`
`Amazon then asserts that it is entitled to have Dr. Houh opine on lack of enablement
`
`. Dkt. 164, at 6-8. It says the
`
`rule set forth in Durel and applied in Personalized Media need not be applied, because Durel
`
`was issued with a different procedural posture and the defendant in Personalized Media did not
`
`“establish[] whether such technology fell within the scope of the claims.” Id. These arguments
`
`are nonsense. That Durel involved a noninfringement finding does not diminish the rule:
`
`
`2 Incidentally, Dr. Houh’s report
`
`
`
`4
`
`
`
`.
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 8 of 11
`
`“enablement does not turn on whether the accused product is enabled.” Durel Corp. v. Osram
`
`Sylvania Inc., 256 F.3d 1298, 1306 (Fed. Cir. 2001). In fact, Durel faulted the invalidity
`
`challenger for failing to “show[] that a significant percentage of [combinations] within the scope
`
`of the claims were not enabled,” id. at 1306-07, something Amazon likewise does not show.3
`
`Amazon’s citations do not help its case. Baxalta did not say that a patent is invalid for
`
`lack of enablement if the accused product was not enabled by the patent, but that a patent’s claim
`
`to a wide range of therapeutic procoagulant activities (one of which was practiced by the accused
`
`antibody) was not enabled based on a large body of testimonial and other evidence. Baxalta Inc.
`
`v. Genentech, Inc., 579 F. Supp. 3d 595, 624 (D. Del. 2022). Both Automotive Technologies and
`
`Liebel-Flarsheim turned on their respective patents’ failure to enable a limitation as construed
`
`by the court, not whether (as Amazon implies) the accused products were enabled by the patent.4
`
`At bottom, Amazon fails to show RTB is anything other than a characteristic of the
`
`accused products that is orthogonal to its infringement of the asserted claims. That the accused
`
`products also include RTB technology does not make it proper to ask whether RTB systems are
`
`enabled by the patents, particularly where no party disputes that a POSITA would not consider
`
`whether the patents enabled real-time bidding at their priority dates.
`
`II.
`
`Amazon Fails to Show Dr. Houh’s Written Description Opinions Are Reliable
`
`Finally, Amazon says that Dr. Houh’s written description opinions are sound because he,
`
`. Dkt. 164, at 8-9. This does not solve Amazon’s problem, because
`
`
`
`
`3 Neither does the supposed failure by Zynga in Personalized Media to show the accused
`products “fell within the scope of the claims” (a question the court never addressed, much less
`decided) somehow cure Dr. Houh’s flawed analysis. Enablement is not tested by looking at
`whether the accused products “fall within the scope of the claims.”
`4 Auto. Techs. Int'l, Inc. v. BMW of N. Am., Inc., 501 F.3d 1274, 1282 (Fed. Cir. 2007); Liebel-
`Flarsheim Co. v. Medrad, Inc., 481 F.3d 1371, 1378 (Fed. Cir. 2007).
`
`
`
`5
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 9 of 11
`
`“Rule 26 does not allow parties to cure deficient expert reports by supplementing them with later
`
`deposition testimony.” Effective Expl., LLC v. BlueStone Nat. Res. II, LLC, 2017 WL 5895164,
`
`at *3 (E.D. Tex. Nov. 13, 2017) (quotations omitted).
`
`Amazon’s next argument is that Dr. Houh’s enablement analysis is “close enough” to the
`
`written description issue, and that both issues “rise and fall” together, so his written description
`
`opinions are “based in logic and not unreliable.” Dkt. 164, at 9-10. This argument, like Dr.
`
`Houh’s analysis, conflates the two requirements. “[W]ritten description is about whether the
`
`skilled reader of the patent disclosure can recognize that what was claimed corresponds to what
`
`was described; it is not about whether the patentee has proven to the skilled reader that the
`
`invention works, or how to make it work, which is an enablement issue.” Alcon Rsch. Ltd. v.
`
`Barr Lab'ys, Inc., 745 F.3d 1180, 1191 (Fed. Cir. 2014). One analysis cannot substitute for the
`
`other. Amazon’s own authority states plainly: “[T]he fact that an invention may be enabled does
`
`not mean it is adequately described, and vice versa.” Nuvo Pharms. (Ireland) Designated Activity
`
`Co. v. Dr. Reddy's Lab'ys Inc., 923 F.3d 1368, 1382 (Fed. Cir. 2019).
`
`III. Amazon’s “Burden and Order of Proof” Arguments Are Non-Sequiturs
`
`Finally, Amazon says that AlmondNet’s Motion “confuses the burdens and order of
`
`proof.” Dkt. 164, at 11-12. Amazon’s argument appears to be that it has met a “burden of
`
`production” on the Section 112 issues which makes them suitable to pass to the jury. AlmondNet
`
`is unaware of any burden-shifting rule that would give context to Amazon’s argument. Amazon
`
`identifies none. Thus, the usual rules apply: Amazon bears the burden of proof by clear and
`
`convincing evidence to show invalidity through lack of enablement or written description.
`
`Without expert testimony to show even a prima facie case of non-enablement or lack of written
`
`description, Amazon cannot show issues of material fact precluding summary judgment.
`
`
`
`6
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 10 of 11
`
`Date: September 15, 2023
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`
`By: /s/ James S. Tsuei
`
`Reza Mirzaie
`Marc A. Fenster
`Benjamin T. Wang
`Adam Hoffman
`James A. Milkey
`Amy E. Hayden
`James S. Tsuei
`Jonathan Ma
`Daniel B. Kolko
`Jason M. Wietholter
`RUSS AUGUST & KABAT
`12424 Wilshire Boulevard 12th Floor
`Los Angeles, California 90025
`Tel: 310-826-7474
`Fax: 310-826-6991
`rmirzaie@raklaw.com
`mfenster@raklaw.com
`bwang@raklaw.com
`ahoffman@raklaw.com
`jmilkey@raklaw.com
`ahayden@raklaw.com
`jtsuei@raklaw.com
`jma@raklaw.com
`dkolko@raklaw.com
`jwietholter@raklaw.com
`
`Counsel for Plaintiff ALMONDNET, INC.
`
`
`
`
`
`
`
`
`7
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00898-ADA Document 204 Filed 09/21/23 Page 11 of 11
`
`CERTIFICATE OF SERVICE
`
`Pursuant to the Federal Rules of Civil Procedure and Local Rule CV-5, I hereby certify
`
`that, on September 15, 2023, all counsel of record who have appeared in this case are being
`
`served with a copy of the foregoing via electronic mail.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ James S. Tsuei
`James S. Tsuei
`
`
`
`
`
`
`
` 1
`
`PUBLIC VERSION
`
`

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