throbber
Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 1 of 8 PageID #: 51358
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF DELAWARE
`
`
`
`
`
`C.A. No. 13-919-JLH
`
`
`
`)))))))))
`
`
`
`ARENDI S.A.R.L.,
`
`
`
`
`
`GOOGLE LLC,
`
`
`
`Plaintiff,
`
`
`
`v.
`
`
`
`Defendant.
`
`GOOGLE’S MOTION FOR JUDGMENT AS A
`MATTER OF LAW OF NO INDIRECT INFRINGEMENT
`
`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 27, 2023
`
`
`
`

`

`Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 2 of 8 PageID #: 51359
`
`I.
`
`INTRODUCTION
`
`Defendant Google LLC (“Google”), pursuant to Federal Rule of Civil Procedure 50(a),
`
`moves for a judgment as a matter of law (“JMOL”) of no indirect infringement. Arendi has
`
`presented no evidence that any third party infringes ’843 claims 23 or 30 (“Asserted Claims”), nor
`
`has Arendi presented any evidence that Google had the necessary scienter to commit secondary
`
`infringement or that the other elements of induced and contributory infringement are present. No
`
`reasonable juror could find Google liable for indirect infringement. Therefore, the Court should
`
`grant judgment of non-infringement as a matter of law.
`
`II.
`
`BACKGROUND
`
`In the Joint Preliminary and Final Jury Instructions filed on March 31, 2023, Arendi
`
`included instructions for induced and contributory infringement. D.I. 451 at 10; D.I. 452 at 25–30.
`
`Later, Arendi notified Google that it would not pursue infringement of any method claims of the
`
`’843 Patent. D.I. 474 at 1. That same day, the Court issued its proposed preliminary jury
`
`instructions. D.I. 470. The parties conferred on any edits they believed were needed, and Google
`
`indicated that it believed that a sentence regarding induced and contributory infringement should
`
`drop out with the removal of the method claims. D.I. 474 at 1. Arendi disagreed. Id.
`
`Accordingly, Arendi appears to still be pursuing claims of induced and contributory
`
`infringement.
`
`III. LEGAL STANDARD
`
`“In order to succeed on a claim of inducement, the patentee must show, first that there has
`
`been direct infringement . . . .” Minn. Mining & Mfg. Co. v. Chemque, Inc., 303 F.3d 1294, 1304–
`
`06 (Fed. Cir. 2002). Second, the alleged infringer must commit affirmative acts encouraging the
`
`infringing activity. See 35 U.S.C. § 271(b); Power Integrations, Inc. v. Fairchild Semiconductor
`
`Int’l, Inc., 843 F.3d 1315, 1331–32 (Fed. Cir. 2016). And that affirmative act must actually cause
`
`

`

`Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 3 of 8 PageID #: 51360
`
`the third-party’s infringement. See id. Third, the patentee must prove that “the alleged infringer
`
`knowingly induced and possessed specific intent to encourage another’s infringement.” Minn.
`
`Mining & Mfg. Co., 303 F.3d at 1305–06. To affirmatively induce infringing acts, the alleged
`
`infringer must have actual knowledge of the asserted patent. Commil USA, LLC v. Cisco Sys., Inc.,
`
`575 U.S. 632, 639 (2015). But mere knowledge of the patent is not sufficient. Id. The accused
`
`infringer must know that the induced act constitutes infringement of the asserted patent. Id.
`
`Alternatively, an accused infringer may be liable if she knows of the patent and is willfully blind
`
`to the infringing nature of the acts she induces—that is, she subjectively believes there is a high
`
`probability that the induced act infringes and takes deliberate action to avoid knowing that induced
`
`acts constitutes infringement. Glob.-Tech Appliances, Inc. v. SEB S.A., 563 U.S. 754, 768–770
`
`(2011).
`
`Like inducement, contributory infringement requires proof that some third party has
`
`directly infringed an asserted claim. See Fujitsu Ltd. v. Netgear Inc., 620 F.3d 1321, 1326 (Fed.
`
`Cir. 2010). To contributorily infringe, a party must also have knowledge of the asserted patent and
`
`sell, or offer to sell, a component of the claimed invention. Id.; i4i Ltd. P’ship v. Microsoft Corp.,
`
`598 F.3d 831, 850–51 (Fed. Cir. 2010). That “component” “must be a material part of the
`
`invention, have no substantial noninfringing uses, and be known (by the party) ‘to be especially
`
`made or especially adapted for use in an infringement of such patent.’” Id. (citation omitted).
`
`IV. ARGUMENT
`
`Arendi offers no evidence that a third party directly infringes any asserted claim. Dr.
`
`Smedley testified only that Google directly infringed the claims. See 4/25/23 Trial Tr. (Smedley)
`
`at 300:10–18, 373:14–18 (“Q. What’s your opinion about whether Google, the Google apps, and
`
`the Google smartphones practice the retrieving step? A. The Google apps and the Google
`
`smartphone practice all this step as well.”). Where a product has non-infringing uses, a patentee
`
`2
`
`

`

`Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 4 of 8 PageID #: 51361
`
`must show “specific instances of direct infringement” by third parties in order to prove secondary
`
`infringement. ACCO Brands, Inc. v. ABA Locks Mfrs. Co., 501 F.3d 1307, 1312–13 (Fed. Cir.
`
`2007). Arendi has not done that, and for that reason alone, a verdict of no indirect infringement
`
`must be entered.
`
`But even if Arendi established that third parties did infringe an asserted claim, it has failed
`
`to establish the other elements of induced and contributory infringement.
`
`A.
`
`Google Has Not Induced Infringement
`
`Arendi presented no evidence that Google affirmatively acted to induce infringement. The
`
`Federal Circuit has long held that that “inducement requires evidence of promotion, active steps,
`
`or encouragement”—that is, active encouragement of the infringing acts. Takeda Pharms. U.S.A.,
`
`Inc. v. W.-Ward Pharm. Corp., 785 F.3d 625, 631 n.3 (Fed. Cir. 2015). In particular, merely
`
`distributing a product with the knowledge that some users may use it to infringe is not inducement.
`
`Warner-Lambert Co. v. Apotex Corp., 316 F.3d 1348, 1363–64 (Fed. Cir. 2003); Rodime PLC v.
`
`Seagate Tech., Inc., 174 F.3d 1294, 1306 (Fed. Cir. 1999).
`
`1. Here, Dr. Smedley testified merely that Google makes its apps available to consumers.
`
`Arendi offered no evidence that Google affirmatively encourages users to download their apps or
`
`to use the allegedly infringing functions. Without “statements or actions directed to promoting
`
`direct infringement,” there can be no liability. Alpek Polyester, S.A. de C.V. v. Polymetrix AG,
`
`No. 2021-1706, 2021 WL 5974163, at *6 (Fed. Cir. Dec. 16, 2021).
`
`2. Additionally, Arendi presented no evidence that any inducing act by Google actually
`
`caused a third party to infringe. “To prevail under a theory of indirect infringement, [the patentee]
`
`must first prove that the defendants’ actions led to direct infringement . . . .” Dynacore Holdings
`
`Corp. v. U.S. Philips Corp., 363 F.3d 1263, 1274 (Fed. Cir. 2004) (emphasis added); Roche
`
`Diagnostics Corp. v. Meso Scale Diagnostics, LLC, 30 F.4th 1109, 1121 (Fed. Cir. 2022) (vacating
`
`3
`
`

`

`Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 5 of 8 PageID #: 51362
`
`jury verdict where patentee “didn’t provide evidence of causation between the allegedly inducing
`
`acts . . . and the direct infringement”). As these decisions (and the ones cited above) demonstrate,
`
`causation may not be inferred merely from a defendant’s making available a product, together with
`
`evidence of subsequent direct infringement. Rather, a plaintiff must present evidence that the
`
`defendant’s affirmative inducing acts—its inducing communications—reached users and caused
`
`them to engage in direct infringement.
`
`Here, Arendi presented no evidence that direct infringement, if any, occurred because of
`
`any inducing persuasion by Google. There is no evidence that Google affirmatively encouraged
`
`any downloads of its apps or instructed users on the allegedly infringing functionalities, much less
`
`that any users saw such communications and downloaded the apps as a result. And to the extent
`
`that Arendi contends that users directly infringed by using the allegedly infringing functionality,
`
`Arendi has presented no evidence of that use, much less that any active step by Google caused
`
`such use.1
`
`3. Arendi has not shown that Google had the necessary mens rea for inducement, i.e., that
`
`it knew that any induced act constituted infringement of the ’843 patent. See 4/26/23 Trial Tr.
`
`(Elbouchikhi) at 686:18–687:1 (“Q. Why didn’t Google change how STS worked given that
`
`Arendi had sued Google in 2013 for allegedly infringing the ’843 patent? A. Yeah. So going back
`
`
`1 As noted in Google’s parallel Rule 50(a) motion that there is no direct infringement, there is
`also an issue as to when the alleged infringement could have even begun, owing to the fact that
`STS functionality was not turned on until December 2017. Even after maintenance release 1 of
`Android 8 (O-MR1), the evidence at trial is that it would have taken at least several months for
`that release to have been implemented by Android handset manufacturers and distributed in the
`United States by carriers. 4/26/23 Trial Tr. (Elbouchikhi) at 682:3–683:5, 683:22–684:3; 4/27/23
`Trial Tr. (Choc) at 793:9–794:4 (explaining that that “lengthy process” takes “six months” on
`average). Furthermore, even after it was available, the undisputed testimony was that OMR-1
`was not distributed by many handset manufacturers. 4/26/23 Trial Tr. (Elbouchikhi) at 684:4–19;
`4/27/23 Trial Tr. (Choc) at 691:18–792:3. And, as detailed in another Google Rule 50(a) motion,
`there is no direct infringement with respect to Google apps on Samsung devices.
`
`4
`
`

`

`Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 6 of 8 PageID #: 51363
`
`to that timeline, you know, in 2017 when I was working on this feature, I had no idea about Arendi.
`
`I was not aware of any of this.”); 4/26/23 Trial Tr. (Toki) at 762:13–22 (“Q. Do you disagree that
`
`Google knew about the ’843 patent and Google knew that Arendi was protecting itself against the
`
`’843 patent and already filed suit against Google someone should have told you? A. I don’t know.
`
`I think Google can answer that question. My job is to think about experiences and build, you know,
`
`user experiences.”); 4/27/23 Trial Tr. (Choc) at 796:25–797:1 (“I didn’t know about this patent
`
`until 2019 when I was deposed.”).
`
`4. Arendi has not shown that Google was willfully blind to infringement of the ’843 patent.
`
`Willful blindness requires the defendant to take deliberate steps to avoid knowledge of
`
`infringement, with a subjective belief that it is highly likely that users are committing infringement.
`
`Glob.-Tech Appliances, 563 U.S. at 771. Arendi has not shown anything like that. See 4/27/23
`
`Trial Tr. (Choc) at 797:21–798:2 (confirming that Google makes an “effort to avoid infringing
`
`intellectual property” and “the legal team ensures that we are being appropriate”).
`
`Google’s mere awareness that Arendi had sued it for allegedly infringing the ’843 Patent,
`
`and its continuing to make and sell the Accused Products thereafter, is not sufficient to establish
`
`that Google subjectively believed there was a high likelihood of infringement. “Willful blindness
`
`is a standard of limited scope that surpasses recklessness and negligence.” Roche Diagnostics
`
`Corp., 30 F.4th at 1118. Allegations that a party should have known of infringement are therefore
`
`insufficient. So too are evidence of a party’s knowledge of the patent and engagement in conduct
`
`later held to be infringing. Id. Moreover, courts in this District have held that a claim for indirect
`
`patent infringement must fail “where the defendant’s alleged knowledge of the asserted patent[] is
`
`based solely on the content of that complaint or a prior version of the complaint filed in the same
`
`5
`
`

`

`Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 7 of 8 PageID #: 51364
`
`lawsuit.” ZapFraud, Inc. v. Barracuda Networks, Inc., 528 F. Supp. 3d 247, 250–52 (D. Del. Mar.
`
`24, 2021).
`
`Therefore, no reasonable juror could find that Google is liable for induced infringement.
`
`B.
`
`Google Has Not Contributed to Infringement
`
`1. Arendi offered no evidence that Google has sold or offered for sale a material component
`
`of the claimed invention. The Accused Apps are intangible software services, not “components.”
`
`See Cleveland Clinic Found. v. True Health Diagnostics LLC, 859 F.3d 1352, 1363–64 (Fed. Cir.
`
`2017); 35 U.S.C. § 271(c).
`
`2. Arendi has failed to offer any evidence that the Accused Apps are especially made or
`
`especially adapted for infringing the ’843 patent—that is, that they lack substantial non-infringing
`
`uses. To the contrary, evidence shows that the accused STS features provide non-infringing cut,
`
`copy, and share functionality. 4/26/23 Trial Tr. (Elbouchiki) at 675:25–676:2 (STS includes
`
`default actions including “copy, cut, and share”); 4/24/23 Trial Tr. (Hedloy) at 169:18–21
`
`(agreeing that “[o]ne purpose of your invention was to allow users to perform searches without
`
`having to cut, copy, or paste into a contact database”).
`
`3. Arendi has not offered any evidence that Google knew that the Accused Apps were
`
`especially made for infringement, for the same reasons stated above.
`
`4. Arendi has also presented no evidence that Google “offers to sell or sells” the Accused
`
`Apps. 35 U.S.C. § 271(c). The Accused Apps are offered to consumers for free.
`
`Therefore, no reasonable juror could find that Google is liable for contributory
`
`infringement.
`
`V.
`
`CONCLUSION
`
`For these reasons, the Court should grant judgment as a matter of law that Google is not
`
`liable for induced or contributory infringement of the ’843 patent.
`
`6
`
`

`

`Case 1:13-cv-00919-JLH Document 495 Filed 04/27/23 Page 8 of 8 PageID #: 51365
`
`
`
`
`
`
`
`POTTER ANDERSON & CORROON LLP
`
`By: /s/ David E. Moore
`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 27, 2023
`10780801 / 12599.00040
`
`
`
`7
`
`

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