throbber
Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 1 of 21
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`RFCYBER CORP.,
`
`Plaintiff,
`
`v.
`
`APPLE INC.,
`
`Defendant.
`
`Civil Action No. 6:21-cv-00916-ADA
`
`JURY TRIAL DEMANDED
`
`
`
`APPLE’S OPPOSITION TO PLAINTIFF RFCYBER’S
`MOTION FOR LEAVE TO FILE SECOND AMENDED COMPLAINT
`
`WEST\301808056.6
`
`PUBLIC VERSION
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 2 of 21
`
`TABLE OF CONTENTS
`
`Page
`
`I.
`
`II.
`
`INTRODUCTION ...............................................................................................................1
`
`BACKGROUND .................................................................................................................2
`
`III.
`
`LEGAL STANDARDS .......................................................................................................4
`
`A.
`
`B.
`
`C.
`
`Good Cause Is Required For Untimely Amendment of Pleadings. .........................4
`
`Courts Have Discretion To Deny A Futile Motion To Amend. ..............................4
`
`Pre-Suit Indirect And Willful Infringement Require Actual Knowledge Of
`The Patents And Of Alleged Infringement. .............................................................5
`
`IV.
`
`RFCYBER CANNOT ESTABLISH GOOD CAUSE TO AMEND ITS
`COMPLAINT. .....................................................................................................................6
`
`A.
`
`B.
`
`C.
`
`D.
`
`RFCyber Has No Plausible Explanation For Its Failure To Timely Move
`For Leave To Amend. ..............................................................................................6
`
`RFCyber’s Proposed Amendment Is Not Important Because It Is Futile. ...............7
`
`1.
`
`2.
`
`3.
`
`The Emails Between Dr. Zheng And Apple Do Not Support
`Claims Of Pre-Suit Indirect Or Willful Infringement. .................................8
`
`Mr. Lasker’s Deposition Testimony Cannot Support Claims Of
`Pre-Suit Indirect Or Willful Infringement. ................................................10
`
`RFCyber’s Willful Blindness Allegations Also Are Futile. ......................11
`
`Apple Will Be Unfairly Prejudiced By RFCyber’s Futile Attempt To
`Reinject Its Dismissed Claims Of Pre-Suit Indirect And Willful
`Infringement. ..........................................................................................................14
`
`The Availability-Of-A-Continuance Factor Also Favors Denying
`RFCyber’s Motion To Amend At This Late Stage Of The Case. ..........................14
`
`V.
`
`CONCLUSION ..................................................................................................................15
`
`WEST\301808056.6
`
`i
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 3 of 21
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`Cases
`
`Affinity Labs of Tex., LLC v. Toyota Motor N. Am.,
`No. W:13-cv-365, 2014 WL 2892285 (W.D. Tex. May 12, 2014) ...........................................5
`
`Ashcroft v. Iqbal,
`556 U.S. 662 (2009) ...................................................................................................................4
`
`Atlas Glob. Techs., LLC v. Sercomm Corp.,
`No. 6-21-CV-00818-ADA, 2022 WL 16557650 (W.D. Tex. Oct. 31, 2022)......................6, 12
`
`Bell Atl. Corp. v. Twombly,
`550 U.S. 544 (2007) ...................................................................................................................4
`
`BillJCo, LLC v. Apple Inc.,
`583 F. Supp. 3d 769 (W.D. Tex. 2022)......................................................................................9
`
`DSU Med. Corp. v. JMS Co.,
`471 F.3d 1293 (Fed. Cir. 2006)..................................................................................................5
`
`Fahim v. Marriott Hotel Servs., Inc.,
`551 F.3d 344 (5th Cir. 2008) ...............................................................................................4, 14
`
`Filgueira v. U.S. Bank Nat. Ass’n,
`734 F.3d 420 (5th Cir. 2013) .................................................................................................7, 8
`
`Flypsi, Inc. v. Google LLC,
`No. 6:22-CV-0031-ADA, 2022 WL 3593053 (W.D. Tex. Aug. 22, 2022) .............................12
`
`Fujitsu Ltd. v. Netgear Inc.,
`620 F.3d 1321 (Fed. Cir. 2010)..................................................................................................5
`
`Glob.-Tech Appliances, Inc. v. SEB S.A.,
`563 U.S. 754 (2011) .....................................................................................................5, 6, 8, 11
`
`Halo Elecs., Inc. v. Pulse Elecs., Inc.,
`579 U.S. 93 (2016) .....................................................................................................................5
`
`Kirsch Rsch. & Dev., LLC v. Tarco Specialty Prods., Inc.,
`No. 6:20-cv-00318-ADA, 2021 WL 4555802 (W.D. Tex. Oct. 4, 2021) ..................................5
`
`Meetrix IP, LLC v. Cisco Sys., Inc.,
`No. 1-18-CV-309-LY, 2018 WL 8261315 (W.D. Tex. Nov. 30, 2018) ....................................6
`
`WEST\301808056.6
`
`ii
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 4 of 21
`
`Parity Networks, LLC v. Cisco Sys., Inc.,
`No. 6:19-CV-00207-ADA, 2019 WL 3940952 (W.D. Tex. July 26, 2019) ....................5, 8, 10
`
`SiOnyx, LLC v. Hamamatsu Photonics K.K.,
`330 F. Supp. 3d 574 (D. Mass. 2018) ........................................................................................5
`
`Stripling v. Jordan Prod. Co., LLC,
`234 F.3d 863 (5th Cir. 2000) .................................................................................................4, 7
`
`Sw. Bell Tel. Co. v. City of El Paso,
`346 F.3d 541 (5th Cir. 2003) .....................................................................................................4
`
`Teradyne, Inc. v. Astronics Test Sys., Inc.,
`No. 20-cv-2713, 2020 WL 8173024 (C.D. Cal. Nov. 6, 2020) .................................................9
`
`USC IP P’ship, L.P. v. Facebook, Inc.,
`No. 6:20-CV-00555-ADA, 2021 WL 3134260 (W.D. Tex. July 23, 2021) ........................6, 13
`
`VLSI Tech., LLC v. Intel Corp.,
`No. 6:19-CV-000254-ADA, 2019 WL 11025759 (W.D. Tex. Aug. 6, 2019) .....................6, 13
`
`Court Rules
`
`Fed. R. Civ. Proc. 12(b)(6) ........................................................................................................4, 14
`
`Fed. R. Civ. Proc. 15(a) ...................................................................................................................4
`
`Fed. R. Civ. Proc. 16(b) ...............................................................................................................1, 4
`
`WEST\301808056.6
`
`iii
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 5 of 21
`
`Apple respectfully opposes the motion by Plaintiff RFCyber for leave to file a second
`
`amended complaint (ECF No. 133), which should be denied with prejudice and without further
`
`leave to amend.
`
`I.
`
`INTRODUCTION
`
`On September 12, 2022, the Court granted Apple’s renewed motion to dismiss
`
`RFCyber’s claims of pre-suit indirect and willful infringement, correctly finding that “RFCyber’s
`
`Amended Complaint does not plead sufficient facts that would support an allegation of pre-suit
`
`knowledge of the patents.” ECF No. 98 at 5. In that Order, the Court set a specific deadline of
`
`“ninety (90) days after the start of fact discovery” for RFCyber to try to reallege its dismissed
`
`claims. Id. That deadline came and went nearly five months ago. Now, with less than one month
`
`left in an already-extended fact discovery period, RFCyber is trying to reinject its dismissed
`
`claims back into this case based on the same facts and circumstances the Court already found did
`
`not withstand pleading scrutiny. See ECF No. 98. This is the opposite of good cause for
`
`amending a complaint under Federal Rule 16(b).
`
`Despite its effort to repackage the evidence by citing recent discovery responses and
`
`deposition testimony, RFCyber presents no new facts or circumstances that differ from those
`
`analyzed by the Court in its September 2022 Order dismissing RFCyber’s claims of pre-suit
`
`indirect and willful infringement. See id. The Court therefore should deny with prejudice
`
`RFCyber’s futile motion for the same reasons the Court granted Apple’s renewed motion to
`
`dismiss last September. And RFCyber provides no reason for missing the amendment deadline
`
`by nearly five months, especially where Apple produced all of the documents RFCyber relies on
`
`more than five months ago. RFCyber’s allegations were insufficient in September 2022 when the
`
`Court granted Apple’s renewed motion to dismiss, and they are insufficient now. RFCyber
`
`therefore has no good cause for this late amendment to its pleading.
`
`WEST\301808056.6
`
`1
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 6 of 21
`
`II.
`
`BACKGROUND
`
`On January 31, 2022, Apple filed its renewed motion to dismiss RFCyber’s indirect and
`
`willful infringement claims alleged in RFCyber’s Amended Complaint. See ECF No. 31.
`
`RFCyber’s primary basis for pleading that Apple had knowledge of the asserted patents was a
`
`four-page “Acquisition Opportunity” brochure emailed to Apple by a third-party broker called
`
`LogicPatents. See ECF No. 31 at 2. The “Acquisition Opportunity” brochure provided a brief
`
`summary of RFCyber’s patent portfolio and listed the asserted ’218, ’855, ’787, and ’009 patents
`
`and the applications that later issued as the ’046 and ’724 patents as part of that portfolio. Id.
`
`Neither that brochure nor the related emails alleged infringement by Apple, nor did they identify
`
`any allegedly infringing Apple product or act. Id.
`
`On September 12, 2022, the Court granted-in-part Apple’s renewed motion to dismiss,
`
`dismissing RFCyber’s claims of pre-suit indirect and willful infringement claims and giving
`
`RFCyber until September 20, 2022 (90 days after the start of fact discovery) to reallege those
`
`claims. See ECF No. 98 at 5. RFCyber filed this motion to amend on February 6, 2023, nearly
`
`five months after the Court’s deadline.
`
`Much of RFCyber’s purportedly “new” evidentiary support is based on emails between
`
`Apple and Dr. Joe Zheng, the LogicPatents representative who contacted Apple and who
`
`RFCyber has identified in its initial disclosures as “the patent prosecuting attorney of record for
`
`the Asserted Patents” and one “who is knowledgeable concerning the prosecution of those
`
`patents . . .
`
`
`
`” Apple Ex. 1, RFCyber’s Corrected Second Supplemental Initial Disclosures.
`
`These emails are the very same emails set forth in Apple’s renewed motion to dismiss; namely,
`
`Dr. Zheng’s email attaching the “Acquisition Opportunity” brochure—which does not allege
`
`infringement or identify any allegedly infringing product—and Apple’s response passing on the
`
`WEST\301808056.6
`
`2
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 7 of 21
`
`opportunity to purchase RFCyber’s portfolio. See ECF No. 31 at 2 (“Importantly, the
`
`‘Acquisition Opportunity’ brochure and related emails do not allege infringement by Apple and
`
`do not identify any allegedly infringing Apple product or act.”).
`
`Apple witness Jeff Lasker’s deposition testimony confirms what was set forth in Apple’s
`
`renewed motion to dismiss—namely, that Apple was aware of four of the five remaining asserted
`
`patents and that some Apple patents cite two of RFCyber’s asserted patents and one published
`
`application. See ECF No. 31 at 2-3. During Mr. Lasker deposition, Apple made proper privilege
`
`objections that have no bearing on Apple’s knowledge of the asserted patents or any alleged
`
`willful blindness. The questions RFCyber asked that drew proper privilege objections did not
`
`relate to the asserted patents, to RFCyber, or to Apple’s knowledge of any purported
`
`infringement of RFCyber’s patents, including the following:
`
`
`
`
`
`“And does Apple look at patents in a specific area before launching its products?”
`
`“Did Apple look at patents in this specific area before launching its Apple Pay
`
`product?”
`
`
`
`“Was Apple aware that there are patents in this area before launching its Apple Pay
`
`products?”
`
`
`
`“Generally does Apple conduct an investigation of patents in a specific area before
`
`launching its products?”
`
`RFCyber Ex. F, Lasker Depo. at 129:7-9; 129:20-22; 130:1-3; 130:10-12. None of these
`
`questions relate to the question at issue in this motion—Apple’s purported pre-suit knowledge of
`
`the asserted patents. At most, they relate to Apple’s general practice of patent clearance before
`
`launching products.
`
`WEST\301808056.6
`
`3
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 8 of 21
`
`III.
`
`LEGAL STANDARDS
`A.
`Good Cause Is Required For Untimely Amendment of Pleadings.
`
`Under Fifth Circuit law, “a party ‘must show good cause for not meeting the deadline
`
`before the more liberal standard of Rule 15(a) will apply to the district court’s denial of leave to
`
`amend.’” Fahim v. Marriott Hotel Servs., Inc., 551 F.3d 344, 348 (5th Cir. 2008) (quoting Sw.
`
`Bell Tel. Co. v. City of El Paso, 346 F.3d 541, 546 (5th Cir. 2003)) (“Federal Rule of Civil
`
`Procedure 16(b) governs amendment of pleadings after a scheduling order’s deadline to amend
`
`has expired . . .”). Four factors are relevant to establishing good cause for such an amendment:
`
`“(1) the explanation for the failure to timely move for leave to amend; (2) the importance of the
`
`amendment; (3) potential prejudice in allowing the amendment; and (4) the availability of a
`
`continuance to cure such prejudice’” Id. Here, RFCyber’s proposed amendment meets none of
`
`those four factors.
`
`B.
`
`Courts Have Discretion To Deny A Futile Motion To Amend.
`
`“It is within the district court’s discretion to deny a motion to amend if it is futile . . . .
`
`[The Fifth Circuit has] interpreted it to mean that the amended complaint would fail to state a
`
`claim upon which relief could be granted . . . [and] will apply ‘the same standard of legal
`
`sufficiency as applies under Rule 12(b)(6).’” Stripling v. Jordan Prod. Co., LLC, 234 F.3d 863,
`
`872-73 (5th Cir. 2000). “To survive a [Rule 12(b)(6)] motion to dismiss, a complaint must
`
`contain sufficient factual matter, accepted as true, to state a claim to relief that is plausible on its
`
`face. A claim has facial plausibility when the plaintiff pleads factual content that allows the court
`
`to draw the reasonable inference that the defendant is liable for the misconduct alleged.”
`
`Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (internal quotation marks and citations omitted).
`
`Where the plaintiff has “not nudged [its] claims across the line from conceivable to plausible,
`
`[its] complaint must be dismissed.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007).
`
`WEST\301808056.6
`
`4
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 9 of 21
`
`Pre-Suit Indirect And Willful Infringement Require Actual Knowledge Of
`C.
`The Patents And Of Alleged Infringement.
`
`To state a claim for induced infringement, RFCyber must plausibly allege Apple (1) had
`
`knowledge of the patent; (2) had “knowledge that the induced acts constitute patent
`
`infringement” (Glob.-Tech Appliances, Inc. v. SEB S.A., 563 U.S. 754, 766 (2011)), and (3)
`
`“possessed specific intent to encourage another’s infringement” (DSU Med. Corp. v. JMS Co.,
`
`471 F.3d 1293, 1306 (Fed. Cir. 2006)). To state a claim for contributory infringement, RFCyber
`
`must plausibly allege facts demonstrating: “(1) that there is direct infringement, (2) that the
`
`accused infringer had knowledge of the patent, (3) that the component has no substantial
`
`noninfringing uses, and (4) that the component is a material part of the invention.’” Affinity Labs
`
`of Tex., LLC v. Toyota Motor N. Am., No. W:13-cv-365, 2014 WL 2892285, at *8 (W.D. Tex.
`
`May 12, 2014) (quoting Fujitsu Ltd. v. Netgear Inc., 620 F.3d 1321, 1326 (Fed. Cir. 2010)).
`
`To state a claim for willful infringement, RFCyber must plausibly allege that Apple: “(1)
`
`knew of the patent-in-suit; (2) after acquiring that knowledge, it infringed the patent; and (3) in
`
`doing so, it knew, or should have known, that its conduct amounted to infringement of the
`
`patent.” Parity Networks, LLC v. Cisco Sys., Inc., No. 6:19-CV-00207-ADA, 2019 WL 3940952,
`
`at *3 (W.D. Tex. July 26, 2019). RFCyber must also allege facts demonstrating “subjective
`
`willfulness of a patent infringer, intentional or knowing.” Halo Elecs., Inc. v. Pulse Elecs., Inc.,
`
`579 U.S. 93, 105 (2016).
`
`“Multiple district courts, post-Halo, have held that . . . general knowledge of a patent
`
`portfolio without more . . . is [insufficient] even to plausibly allege knowledge of a particular
`
`asserted patent.” Kirsch Rsch. & Dev., LLC v. Tarco Specialty Prods., Inc., No. 6:20-cv-00318-
`
`ADA, 2021 WL 4555802, at *2 (W.D. Tex. Oct. 4, 2021) (quoting SiOnyx, LLC v. Hamamatsu
`
`Photonics K.K., 330 F. Supp. 3d 574, 608 (D. Mass. 2018)). Moreover, prosecution activity such
`
`WEST\301808056.6
`
`5
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 10 of 21
`
`as the disclosure of an asserted patent’s application or the disclosure of the asserted patent by the
`
`Examiner is “too attenuated to plausibly infer that [Defendant] had pre-suit knowledge of the
`
`Asserted Patents.” Meetrix IP, LLC v. Cisco Sys., Inc., No. 1-18-CV-309-LY, 2018 WL
`
`8261315, at *2 (W.D. Tex. Nov. 30, 2018).
`
`A showing of willful blindness requires that “(1) [t]he defendant must subjectively
`
`believe that there is a high probability that a fact exists and (2) the defendant must take deliberate
`
`actions to avoid learning of that fact.” Glob.-Tech Appliances, 563 U.S. at 769. “Merely pleading
`
`that the defendant was aware of a patent portfolio without more . . . is not enough [to support a
`
`willful blindness claim].” Atlas Glob. Techs., LLC v. Sercomm Corp., No. 6-21-CV-00818-ADA,
`
`2022 WL 16557650, at *5 (W.D. Tex. Oct. 31, 2022); see also USC IP P’ship, L.P. v. Facebook,
`
`Inc., No. 6:20-CV-00555-ADA, 2021 WL 3134260, at *1-2 (W.D. Tex. July 23, 2021) (granting
`
`motion to dismiss where the plaintiff alleged the defendant had “a policy or practice of not
`
`reviewing the patents of others . . . and thus ha[d] been willfully blind of [its] patent rights”);
`
`VLSI Tech., LLC v. Intel Corp., No. 6:19-CV-000254-ADA, 2019 WL 11025759, at *1 (W.D.
`
`Tex. Aug. 6, 2019) (“The Court finds that Intel’s policy that forbids its employees from reading
`
`patents held by outside companies or individuals is insufficient to meet the test of willful
`
`blindness.”).
`
`RFCYBER CANNOT ESTABLISH GOOD CAUSE TO AMEND ITS
`IV.
`COMPLAINT.
`A.
`RFCyber Has No Plausible Explanation For Its Failure To Timely Move For
`Leave To Amend.
`
`The first good cause factor, the explanation for the failure to timely move for leave to
`
`amend, strongly favors denying this motion. RFCyber has no explanation for its nearly five-
`
`month delay after the deadline set by the Court in its September 12, 2022 Order. Apple timely
`
`produced the emails between Dr. Zheng (RFCyber’s patent agent) and Apple on September 28,
`
`WEST\301808056.6
`
`6
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 11 of 21
`
`2022—nearly five months ago and just two weeks after the Court granted Apple’s renewed
`
`motion to dismiss. Apple Ex. 2, Sept. 28, 2022 Letter. Dr. Zheng is RFCyber’s patent agent
`
`responsible for its patent prosecution efforts and is represented by RFCyber’s counsel in this
`
`lawsuit, so RFCyber has no excuse for not collecting and producing all of Dr. Zheng’s relevant
`
`emails on the day fact discovery opened. See Apple Ex. 3, Zheng Depo. at 10:6-12; 8:5-15.
`
`Indeed, Apple is the only party that produced Dr. Zheng’s emails with Apple—RFCyber
`
`apparently did not even bother to collect them. Furthermore, Mr. Lasker’s deposition testimony
`
`merely confirmed facts that RFCyber already knew—namely, that there was an exchange of
`
`emails between Mr. Zheng and Apple about acquiring RFCyber’s portfolio that led nowhere. See
`
`RFCyber Ex. F, Lasker Depo. at 126:20-127:5, 143:4-144:10; see also ECF No. 31 at 2, 7.
`
`In ruling on Apple’s renewed motion to dismiss, the Court analyzed these email
`
`exchanges and rightly concluded they did not support a claim of pre-suit indirect or willful
`
`infringement. See ECF No. 98 at 3-4. And as demonstrated below, Mr. Lasker’s testimony about
`
`Apple’s
`
` has nothing to do with the
`
`asserted patents and therefore has nothing to do with this motion to amend. RFCyber’s failure to
`
`explain why it delayed nearly five months after the Court’s deadline to move to amend negates
`
`any showing of good cause.
`
`B.
`
`RFCyber’s Proposed Amendment Is Not Important Because It Is Futile.
`
`Under the second good cause factor, the importance of the amendment, “it is within the
`
`district court’s discretion to deny a motion to amend if it is futile.” Stripling, 234 F.3d at 872-73.
`
`See also Filgueira v. U.S. Bank Nat. Ass’n, 734 F.3d 420, 423 (5th Cir. 2013) (affirming district
`
`court’s “good cause” analysis where the court found that the second factor, the importance of
`
`plaintiff’s amendment, weighed heavily in favor of the defendants because “any amendment by
`
`[plaintiff] would be futile”). Just like RFCyber’s prior attempt to plead pre-suit indirect and
`
`WEST\301808056.6
`
`7
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 12 of 21
`
`willful infringement, the amendment RFCyber proposes now does not clear the legal sufficiency
`
`standard required by the Fifth Circuit. See id. As the Court recognized in its September 2022
`
`Order, indirect and willful infringement require factual allegations demonstrating pre-suit
`
`knowledge of the asserted patents and pre-suit knowledge of the acts that allegedly constitute
`
`patent infringement. See ECF No. 98 at 3-4; see also Glob.-Tech Appliances, 563 U.S. at 765-66
`
`(indirect infringement requires “knowledge of the existence of the patent that is [allegedly]
`
`infringed” and “knowledge that the induced acts constitute patent infringement”); Parity
`
`Networks, 2019 WL 3940952, at *3 (willful infringement requires knowledge of the asserted
`
`patent by alleged infringer and knowledge “that its conduct amounted to infringement of the
`
`patent”).
`
`In the time between the Court’s September 2022 Order and today, RFCyber has
`
`uncovered no new information relevant to its pre-suit indirect and willful infringement claims.
`
`The only difference between September 2022 and today is that RFCyber can now cite to two
`
`emails and deposition testimony it obtained during the intervening months. But those two emails
`
`and the deposition testimony merely corroborate the same facts briefed in Apple’s renewed
`
`motion to dismiss and considered by the Court in ruling on that motion. See ECF No. 98 at 3-4.
`
`RFCyber has not pled any additional facts, so the Court should deny with prejudice this motion
`
`for the same reasons it granted Apple’s renewed motion to dismiss. See id.
`
`The Emails Between Dr. Zheng And Apple Do Not Support Claims Of
`1.
`Pre-Suit Indirect Or Willful Infringement.
`
`As the Court correctly ruled in September 2022, the emails between Dr. Zheng and Apple
`
`are legally insufficient to support claims of pre-suit indirect or willful infringement. See id.
`
`RFCyber has not sufficiently alleged that Apple had pre-suit knowledge of the ’724 patent
`
`(RFCyber has since dropped the ’046 patent) because, as Apple successfully argued, “notice of a
`
`WEST\301808056.6
`
`8
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 13 of 21
`
`pending patent application is not sufficient to provide notice of a not-yet-issued patent.” Id. at 3.
`
`And as to the other asserted patents, RFCyber has not sufficiently alleged Apple had pre-suit
`
`knowledge of any allegedly infringing acts because “RFCyber has not sufficiently alleged pre-
`
`suit knowledge of any allegedly infringing acts.” Id. Neither the “Acquisition Opportunity”
`
`brochure nor the emails between Dr. Zheng and Apple mention infringement or identify any
`
`allegedly infringing Apple products. The closest RFCyber comes to alleging an actual
`
`identification of an infringing act are vague allusions in Dr. Zheng’s August 10, 2016 email that
`
`
`
`. See RFCyber Ex. A. But those statements fall well short of identifying
`
`any products that allegedly infringe any specific patent in RFCyber’s portfolio. See BillJCo, LLC
`
`v. Apple Inc., 583 F. Supp. 3d 769, 777 (W.D. Tex. 2022) (“The Complaint does not allege that
`
`BillJCo’s June 2019 Letter notified Apple that it infringed the Asserted Patents or identified
`
`Apple products accused of infringement here . . . .”); see also Teradyne, Inc. v. Astronics Test
`
`Sys., Inc., No. 20-cv-2713, 2020 WL 8173024, at *3-5 (C.D. Cal. Nov. 6, 2020) (finding
`
`insufficient a letter that did not identify any specific product that allegedly infringed the asserted
`
`patent). Indeed, Dr. Zheng’s reference to
`
` is so broad in the
`
`context of Apple’s product offerings that it cannot confer knowledge on Apple of a specific
`
`RFCyber patent and a specific allegedly infringing Apple product. As before, the Zheng emails
`
`are legally insufficient to sustain claims of pre-suit indirect and willful infringement. See ECF
`
`No. 98 at 3-4; BillJCo, 583 F. Supp. 3d at 777.
`
`The Zheng emails cannot support claims of pre-suit indirect or willful infringement for
`
`another basic reason—RFCyber has improperly tried to disavow Dr. Zheng’s communications
`
`with third parties, including Apple, because he purportedly was not authorized to conduct
`
`WEST\301808056.6
`
`9
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 14 of 21
`
`negotiations on RFCyber’s behalf. See Apple Ex. 4, Jan. 20, 2023 Hr’g Tr. at 10:19-11:11
`
`).
`
`,
`
`
`
`
`
`
`
`
`
`
`
`
`
`131:18;
`
` See Apple Ex. 5, Pan Depo. at 133:4-10, 130:19-
`
`. Regardless which
`
`is true, RFCyber cannot on the one hand rely on Dr. Zheng’s outreach to Apple to try to allege
`
`claims of pre-suit indirect and willful infringement, while at the same time falsely denying that
`
`Dr. Zheng had any authority to speak on RFCyber’s behalf.
`
`Mr. Lasker’s Deposition Testimony Cannot Support Claims Of Pre-
`2.
`Suit Indirect Or Willful Infringement.
`
`Similarly, Mr. Lasker’s deposition testimony about the Zheng emails does not and cannot
`
`support RFCyber’s effort to reinject pre-suit indirect and willful infringement into this case. At
`
`the outset, RFCyber misrepresents Mr. Lasker’s testimony about Apple’s knowledge of the
`
`asserted patents. Mr. Lasker was clear that Apple had knowledge of the RFCyber portfolio,
`
`including four of the five asserted patents (RFCyber Ex. F, Lasker Depo. at 126:3-24, 128:2-
`
`129:1), but he never testified that “Apple reviewed the Asserted Patents” as RFCyber claims in
`
`its motion. ECF No. 133 at 9-10. RFCyber is essentially trying to equate Apple’s generic
`
`knowledge of the asserted patents with Apple’s patent intake review procedure to manufacture a
`
`willfulness claim. But RFCyber’s speculative position about Apple’s patent intake review
`
`procedures does not trump the settled law that RFCyber must allege facts showing that Apple
`
`“knew, or should have known, that its conduct amounted to infringement of the patent.” Parity
`
`WEST\301808056.6
`
`10
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 15 of 21
`
`Networks, 2019 WL 3940952, at *3. Mr. Lasker’s deposition testimony gets RFCyber nowhere
`
`close to that showing.
`
`RFCyber also baselessly claims that Apple’s proper privilege objections during Mr.
`
`Lasker’s deposition “demonstrate that Apple analyzed patents related to Apple Pay” which
`
`“weighs toward a finding that Apple knew of, or was willfully blind to, its infringement.” ECF
`
`No. 133 at 5. However, none of RFCyber’s questions to which Apple properly objected had
`
`anything to do with (1) the asserted patents, (2) RFCyber, or (3) any actual or implied knowledge
`
`of Apple’s alleged infringement of RFCyber’s patents. See RFCyber Ex. F, Lasker Depo. at
`
`129:7-9 (“And does Apple look at patents in a specific area before launching its products?”);
`
`129:20-22 (“Did Apple look at patents in this specific area before launching its Apple Pay
`
`product?”); 130:1-3 (“Was Apple aware that there are patents in this area before launching its
`
`Apple Pay products?”); 130:10-12 (“Generally does Apple conduct an investigation of patents in
`
`a specific area before launching its products?”). Simply put, none of RFCyber’s improper efforts
`
`to invade the attorney-client privilege relate to any knowledge, review, or analysis of the asserted
`
`patents—at best, they relate to the Apple’s general practice of patent clearances or analysis prior
`
`to the launching of its products.
`
`3.
`
`RFCyber’s Willful Blindness Allegations Also Are Futile.
`
`For similar reasons, RFCyber’s willful blindness allegations also are futile because
`
`RFCyber relies entirely on attorney argument, not facts, to assert that Apple deliberately avoided
`
`learning of its alleged infringement. However, the Supreme Court has held that a showing of
`
`willful blindness requires that “(1) [t]he defendant must subjectively believe that there is a high
`
`probability that a fact exists and (2) the defendant must take deliberate actions to avoid learning
`
`of that fact.” Glob.-Tech Appliances, 563 U.S. at 769.
`
`WEST\301808056.6
`
`11
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 16 of 21
`
`According to RFCyber’s interpretation of the willful blindness doctrine, a defendant
`
`would have to affirmatively establish that it does not infringe a patent anytime it learns about a
`
`patent. Tellingly, RFCyber fails to cite to a single case for this proposition, because all authority
`
`is to the contrary: “Merely pleading that the defendant was aware of a patent portfolio without
`
`more . . . is not enough [to support a willful blindness claim].” Atlas Glob. Techs., 2022 WL
`
`16557650, at *5; see also Flypsi, Inc. v. Google LLC, No. 6:22-CV-0031-ADA, 2022 WL
`
`3593053, at *4 (W.D. Tex. Aug. 22, 2022) (dismissing willful blindness claim in part because
`
`“[n]o facts [were] alleged that the discussions specifically centered on the Patents-In-Suit”).
`
`Here, Dr. Zheng generally informed Apple about the RFCyber patent portfolio, but there
`
`was no discussion about any specific patents or any Apple products, and no suggestion that
`
`Apple products infringed those patents, so there was nothing to be “willfully blind” about. And
`
`RFCyber’s claim that Apple affirmatively elected not to receive a “claim chart” from Dr. Zheng
`
`to avoid learning about its alleged infringement is nothing more than attorney argument. For
`
`starters, RFCyber’s proposed amended pleading does not identify the alleged “claim chart.” And
`
`Dr. Zheng’s email made Apple’s receipt of that claim chart optional, stating
`
`
`
` See RFCyber Ex. A (emphasis added). Dr. Zheng
`
`could have easily attached a claim chart to his email, but did not. Even after Apple passed on the
`
`opportunity to purchase the portfolio (see RFCyber Ex. C), Dr. Zheng could have sent the
`
`purported claim chart to Apple at that time, but again did not. Dr. Zheng’s email also does not
`
`say what patent, product, or even general technology the purported “claim chart” relates to. See
`
`RFCyber Ex. A. The brochure attached to Mr. Zheng’s email contains a laundry list of
`
`companies, including
`
`—followed immediately by the words:
`
`WEST\301808056.6
`
`12
`
`
`
`
`
`

`

`Case 6:21-cv-00916-ADA Document 140 Filed 02/28/23 Page 17 of 21
`
`RFCyber Ex. B. Thus, the “claim chart” referenced in Dr. Zheng’s email could just as easily
`
`have referred to products from any one of these other companies, or another company, or nothing
`
`at all. Thus, this purported “claim chart,” and the fact that Apple never received it, cannot
`
`support a claim of willful blindness.
`
`Finally, RFCyber’s argument that “Mr. Lasker’s testimony suggests that Apple
`
`deliberately structure its ‘patent acquisition team’ to avoid finding that it infringed the Asserted
`
`Patents” (ECF No. 133 at 10) is both baseless and speculative. First, as demonstrated above,
`
`neither RFCyber nor Dr. Zheng accused Apple of infringement nor suggested that any Apple
`
`products allegedly infringed the asserted patents. Second, RFCyber cites no legal authority to
`
`suggest that the structure of Apple’s patent acquisition team could possibly form the basis of a
`
`claim for willful blindness. All of the relevant authority, including from this Court, is to the
`
`contrary. See USC IP P’ship, 2021 WL 3134260, at *1-2 (gr

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