throbber
Case 1:13-cv-00919-JLH Document 610 Filed 01/12/24 Page 1 of 3 PageID #: 62477
`
`
`
`
`
`
`
`January 12, 2024
`
`Via CM/ECF
`
`The Honorable Jennifer L. Hall
`J. Caleb Boggs Federal Building
`844 N. King Street
`Unit 17, Room 3124
`Wilmington, DE 19801-3555
`
`
`
`Re: Arendi S.A.R.L. v. Google LLC (13-919-JLH)
`
`Dear Judge Hall:
`
`
`Pursuant to the Court’s Order of January 5, 2024, Arendi submits this letter after meeting
`and conferring with Google LLC on January 10, 2024. D.I. 609.
`
`The proper course is for the Court to amend its existing judgment (D.I. 545) to remove
`references to the issue of patent validity and clarify that the judgment is based on the jury’s non-
`infringement verdict at trial. If the Court does so, the law is clear that the Court can then decline
`to address Arendi’s post-trial motion concerning validity issues. D.I. 559.
`
`There is no need for the Court to incorporate a validity determination into the judgment, or
`further consider the validity issue at all, because Google only raised it as an affirmative defense
`and the defense became moot when the jury found non-infringement. Many courts confronted with
`this situation have declined to rule on post-trial motions regarding validity because of the mootness
`of the issue, including Judge Noreika in Agrofresh Inc. v. Essentiv LLC, No. CV 16-662 (MN),
`2020 WL 7024867, at *17 (D. Del. Nov. 30, 2020) (“In light of the finding of no infringement, the
`affirmative defenses of invalidity are now moot and the Court declines to reach the issue of
`validity.”). See also IPPV Enterprises, LLC v. EchoStar Commc'ns Corp., No. CIV.A.99-577-
`KAJ, 2003 WL 723260, at *10 (D. Del. Feb. 27, 2003) (declining “to reach the issue of invalidity”
`upon entering judgment of non-infringement).1
`
`
`
`1 See also, e.g., Optolum, Inc. v. Cree, Inc., No. 1:17CV687, 2022 WL 1632916, at *1-2 (M.D.N.C.
`Jan. 31, 2022) (holding that “this court need not address the parties’ motions on validity and
`damages” because “those issues are moot” given jury’s non-infringement verdict where “[n]either
`party sought a declaratory judgment as to any of the issues addressed in the pending motions”);
`ClearPlay, Inc. v. Dish Network L.L.C., No. 2:14-CV-00191-DN-CMR, 2023 WL 3805596, at *29
`(D. Utah June 2, 2023) (denying motion for judgment as a matter of law on validity as moot
`following non-infringement verdict).
`
`
`
`

`

`Case 1:13-cv-00919-JLH Document 610 Filed 01/12/24 Page 2 of 3 PageID #: 62478
`
`The Honorable Jennifer L. Hall
`January 12, 2024
`Page 2
`
`Judge Noreika’s decision in Agrofresh cited the relevant Federal Circuit decisions, which
`have uniformly held that if a defendant raises invalidity as an affirmative defense rather than a
`counterclaim, then a jury’s non-infringement verdict makes any invalidity determination
`unnecessary to the judgment. See, e.g., Lighting World, Inc. v. Birchwood Lighting, Inc., 382 F.3d
`1354, 1366 (Fed. Cir. 2004) (“Because Birchwood raised invalidity only as an affirmative defense
`and not as a counterclaim, it became unnecessary for the court to enter a judgment as to the
`invalidity issue when the court entered judgment of noninfringement”); see also PODS, Inc. v.
`Porta Stor, Inc., 484 F.3d 1359, 1368 (Fed. Cir. 2007) (“We have no need to consider Porta Stor’s
`arguments related to invalidity, since our finding of non-infringement moots any affirmative
`defense of invalidity, and Porta Stor has not argued its invalidity counterclaim on appeal.”); Boss
`Control, Inc. v. Bombardier Inc., 410 F.3d 1372, 1376 n.1 (Fed. Cir. 2005) (“As noted above,
`Bombardier only filed affirmative defenses and not counterclaims. Since there are no pending
`counterclaims with respect to invalidity, the district court entered a proper final judgment.”).
`
`Because the issue of validity in this case was mooted by the jury’s non-infringement
`verdict, and is unnecessary to the judgment, the proper course is to conserve the Court’s judicial
`resources and amend the judgment to remove references to the validity issue and make clear that
`judgment is predicated on the jury’s non-infringement finding.
`
`Following the guidance of the many courts that have exercised their discretion not to
`expend judicial resources addressing a moot validity issue will not create complexity on appeal.
`Should the Court limit judgment to the issue of non-infringement, Arendi’s affirmative appeal will
`be limited to challenging the non-infringement finding and Court orders that predicated it. These
`orders include the Court’s claim construction order of August 19, 2019 (D.I. 143, 144); the Court’s
`order granting Defendants’ Rule 12(c) motions for judgment on the pleadings under Section 101
`concerning U.S. Patent No. 7,496,854, U.S. Patent No. 7,921,356, and U.S. Patent No. 8,306,993
`(D.I. 201); and the Court’s grant of partial summary judgment against Arendi on March 31, 2022,
`including the Court’s construction of the “document” claim term therein (D.I. 393, 394).
`
`To the extent Google asserts that the judgment should incorporate a finding on validity so
`that the Federal Circuit may consider the issue as an alternative basis for affirmance, Google is
`asking both this Court and the Federal Circuit to do unnecessary work to which Google is not
`entitled. Had Google wanted to preserve an appellate point, it should have brought a counterclaim
`for invalidity. It did not. Google made a conscious choice to raise the invalidity issue only as an
`affirmative defense. Because of that choice, the invalidity issue was mooted by the jury’s non-
`infringement verdict and is unnecessary to the judgment.
`
`Indeed, any resources this Court dedicates to the validity issue at this point are likely to be
`wasted. If the Federal Circuit affirms the non-infringement judgment, it will not reach the validity
`issue and there will have been no reason for this Court to address it. See Hill-Rom Co. v. Kinetic
`Concepts, Inc., 209 F.3d 1337, 1344 (Fed. Cir. 2000) (upholding non-infringement judgment and
`declining to reach validity issue because “the district court’s resolution of the issue of invalidity
`was not necessary to the judgment”). Alternatively, if the Federal Circuit reverses the non-
`infringement judgment, it is unlikely that it will then proceed to consider validity as an alternative
`basis for affirmance. Because the validity issue depends on the application of specific claim
`
`

`

`Case 1:13-cv-00919-JLH Document 610 Filed 01/12/24 Page 3 of 3 PageID #: 62479
`
`The Honorable Jennifer L. Hall
`January 12, 2024
`Page 3
`
`constructions, any decision by the Federal Circuit that alters any claim construction in reversing
`the non-infringement judgment would necessitate further proceedings in the District Court
`regarding validity. Thus, regardless of how the Federal Circuit rules on Arendi’s appeal of the non-
`infringement judgment, it is unlikely that the Federal Circuit would even consider this Court’s
`entirely discretionary determination on validity.
`
`Similarly, to the extent Google asserts that the Court should amend its judgment to
`generically enter “judgment in favor of the Defendant” and that Arendi should then withdraw its
`post-trial motion, this is unwarranted. Arendi’s withdrawal of its motion under these circumstances
`could wrongly suggest that Arendi accepted the jury’s invalidity finding and create confusion as
`to whether the Court’s amended judgment was exclusively based on the jury’s non-infringement
`finding.
`
`Google cannot rewrite the procedural history of this case to alter the mootness of the
`invalidity issue it raised only as a defense, and there is no basis for this Court to expend its judicial
`resources addressing a moot issue. The proper course, as illustrated by the cases cited above, is to
`enter a judgment of non-infringement that does not reference the issue of validity and decline to
`substantively address or deny as moot Arendi’s post-trial motion for judgment as a matter of law.
`
`Respectfully,
`
`Neal C. Belgam
`
`Neal C. Belgam (No. 2721)
`
`cc:
`
`
`
`
`Clerk of Court (via CM/ECF)
`All Counsel of Record (via CM/ECF)
`
`

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