throbber
Case 1:13-cv-00919-JLH Document 507 Filed 04/29/23 Page 1 of 3 PageID #: 52262
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT DELAWARE
`
`
`
`
`
`
`
`
`
`
`
`C.A. No. 13-919-JLH
`
`JURY TRIAL DEMANDED
`
`
`
`
`)))))))))
`
`Plaintiff,
`
`
`
`v.
`
`ARENDI S.A.R.L.,
`
`
`
`
`
`GOOGLE LLC,
`
`
`
`
`Defendant.
`
`
`LETTER TO THE HONORABLE JENNIFER L. HALL FROM DAVID E. MOORE
`REGARDING UPDATE ON ISSUE RELATED TO THE PARTIES’
`PROPOSED FINAL JURY INSTRUCTIONS AND PROPOSED VERDICT FORM
`
`POTTER ANDERSON & CORROON LLP
`
`David E. Moore (#3983)
`Bindu A. Palapura (#5370)
`Andrew L. Brown (#6766)
`Hercules Plaza, 6th Floor
`1313 N. Market Street
`Wilmington, DE 19801
`Tel: (302) 984-6000
`dmoore@potteranderson.com
`bpalapura@potteranderson.com
`abrown@potteranderson.com
`
`Attorneys for Defendant Google LLC
`
`OF COUNSEL:
`
`Robert W. Unikel
`John Cotiguala
`Matt Lind
`PAUL HASTINGS LLP
`71 South Wacker Drive, Suite 4500
`Chicago, IL 60606
`Tel: (312) 449-6000
`
`Robert R. Laurenzi
`Chad J. Peterman
`PAUL HASTINGS LLP
`200 Park Avenue
`New York, NY 10166
`Tel: (212) 318-6000
`
`Ginger D. Anders
`MUNGER, TOLLES & OLSON LLP
`601 Massachusetts Avenue NW, Suite 500E
`Washington, D.C. 20001
`Tel: (202) 220-1100
`
`Vincent Y. Ling
`MUNGER, TOLLES & OLSON LLP
`350 S. Grand Avenue, 50th Floor
`Los Angeles, CA 90071
`Tel: (213) 683-9100
`
`Dated: April 29, 2023
`
`

`

`Case 1:13-cv-00919-JLH Document 507 Filed 04/29/23 Page 2 of 3 PageID #: 52263
`
`
`
`Dear Judge Hall:
`
`
`April 29, 2023
`
`Google writes regarding two updates on the parties’ Proposed Final Jury instructions and
`
`Proposed Verdict Form being filed this morning:
`1. The Court’s proposal regarding an effective royalty rate on the verdict form
`
`During the hearing in this case on April 28, 2023, the Court raised concerns about Arendi’s
`royalty base calculation, which Google has submitted to the Court is a flawed calculation as to all
`twelve accused apps and four accused devices. See 4/28/23 Trial Tr. (Rough) at 1061:1–19,
`1070:1–13; D.I. 479 (4/23 Letter Motion Regarding Arendi’s New Damages and Willfulness
`Theories) at 2–3; D.I. 496 (4/27 Motion for JMOL of No Damages or, in the Alternative, Nominal
`or Limited Damages) at 3–6. The Court therefore asked the parties to consider whether the Verdict
`Form should ask the jury for a reasonable royalty rate, “to try to avoid any downstream issues.”
`4/28/23 Trial Tr. (Rough) at 1070:8–1071:3.
`
`While Google appreciates the Court’s proposal, it believes that asking the jury for a royalty
`rate would be highly prejudicial and confusing and constitute error for several reasons:
`
`First, asking the jury for a royalty rate would endorse the methodology of Arendi’s
`damages expert, Mr. Weinstein, over Google’s damages expert, Mr. Kidder. Mr. Weinstein has
`opined on a damages methodology that calculates and uses effective per-unit royalty rates.
`4/26/23 Trial Tr. (Rough) at 589:15–599:3; 615:15–616:6. Mr. Kidder (who has not yet taken the
`stand) took a different approach: he calculated a lump sum royalty that is not tied to accused units
`and did not calculate or use any effective royalty rate.
`
`Second, asking the jury for a royalty rate would put a heavy thumb on the scale of damages
`in favor of Arendi. As a practical matter, the jury is highly unlikely to set any royalty rate lower
`than a $0.01 per unit, effectively setting a floor on damages that would be inappropriate and
`inconsistent with Google’s damages theories. The Court would effectively remove from the jury
`its freedom to render a verdict adopting Google’s damages theories.
`
`Third, asking the jury for a royalty rate is likely to cause jury confusion because there is
`no evidence of any single “blended” royalty rate that could apply in this case, where there are two
`categories of accused products (apps and mobile devices). Even Mr. Weinstein calculates and uses
`two royalty rates, not one, for those two categories. See 4/26/23 Trial Tr. (Rough) (Weinstein) at
`596:3–25; 4/28/23 Trial Tr. (Rough) (Hearing) at 1070:20–1071:1.
`
`Fourth, because an effective royalty rate does not comport with either party’s damages
`theories, there would be heightened risk that any damages verdict might deviate from both parties’
`damages theories. A damages verdict that is unexplainable based on the record might require a
`new trial on damages. See, e.g., Trustees of Bos. Univ. v. Everlight Elecs. Co., 199 F. Supp. 3d
`473, 474 (D. Mass. 2016).
`
`Google appreciates the Court’s effort to address Arendi’s failure to apportion its damages
`
`request, and is open to considering other alternatives to ensure that, as the law requires, any jury
`award is limited to infringing accused products. It bears repeating, though, that Arendi has the
`burden of presenting sufficient evidence to support a damages award that is both nonspeculative
`
`
`
`

`

`Case 1:13-cv-00919-JLH Document 507 Filed 04/29/23 Page 3 of 3 PageID #: 52264
`
`The Honorable Jennifer L. Hall
`April 29, 2023, Page 2
`
`and properly apportioned to infringing (not non-infringing) products. Arendi’s failure to do so—
`a product of its failure to account for how its infringement claims changed at summary judgment
`and then on the eve of trial—should not require Google to accede to a likely prejudicial
`compromise means of calculating damages through a royalty rate.
`
`2. License or Release Defense – The Samsung Agreement
`
`At the April 28, 2023 hearing, the Court also asked the parties to further discuss how to
`address the Samsung Agreement issue—whether that agreement covers accused Google apps on
`Samsung devices—in the Final Proposed Jury Instructions and Final Proposed Verdict Form. See
`4/28/23 Trial Tr. (Rough) at 1117:2–7. As Google does not believe that a per-unit royalty rate is
`appropriate, that proposal does not resolve the Samsung Agreement issue for purposes of the jury
`instructions and verdict form.
`
`Although the parties remain at an impasse over how to interpret the Samsung Agreement,
`there seems to be agreement that it would be challenging to instruct and ask the jury about this
`issue without further guidance from the Court. For instance, Arendi proposes two alternative jury
`instructions, the first of which would require a ruling on the law in its favor, and the second of
`which assumes the Court has held that the Samsung Agreement is ambiguous. Either of these
`proposed instructions would be improper without a ruling on whether or not the Samsung
`Agreement is ambiguous. Alternatively, accounting for that open question in a jury instruction (as
`Google has proposed and believes is necessary) might also invite error. A ruling before final jury
`instructions and closing argument on whether or not the Agreement is ambiguous would address
`these concerns. The parties appear to agree that, until answered, that predicate question may
`prevent the jury from being properly instructed. See D.I. 469 (4/20/23 Google letter brief) at 3;
`D.I. 472 (4/21/23 Arendi response letter) at 1–2 (“On the merits of what the Agreement means,
`there are three possibilities: the contract is unambiguous in Arendi’s favor; it is ambiguous; or it
`is unambiguous in Google’s favor. An appropriate jury instruction can be crafted at the charging
`conference to reflect any of those rulings.” (emphasis added) (footnote omitted)).
`
`Respectfully,
`
`/s/ David E. Moore
`
`David E. Moore
`
`DEM:nmt/10782914/12599.00040
`
`cc:
`
`Clerk of the Court (via hand delivery)
`Counsel of Record (via electronic mail)
`
`
`
`
`
`

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