throbber
Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 1 of 10
`
`
`RFCYBER CORP.,
`
`
`
`
`v.
`
`
`APPLE, INC.,
`
`
`Plaintiff,
`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION

`

`Case No. 6:21-cv-00916-ADA

`
`JURY TRIAL DEMANDED

`







`
`
`Defendant.
`
`
`
`
`RFCYBER CORP.’S REPLY IN SUPPORT OF ITS MOTION
`FOR LEAVE TO FILE SECOND AMENDED COMPLAINT
`
`
`
`
`
`
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 2 of 10
`
`TABLE OF CONTENTS
`
`Page(s)
`
`A.
`
`B.
`
`C.
`
`D.
`
`The Amendment is Important and Presents an Exceptionally Strong Case ............ 2
`
`RFCyber Was Diligent in Pursuing Discovery ....................................................... 4
`
`Apple Would Not Be Unfairly Prejudiced By the Amendment ............................. 5
`
`No Continuance is Required ................................................................................... 5
`
`
`
`
`
`i
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 3 of 10
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`Cases
`
`Atlas Glob. Techs., LLC v. Sercomm Corp.,
`No. 6-21-CV-00818-ADA, 2022 WL 16557650 (W.D. Tex. Oct. 31, 2022)............................3
`
`BillJCo, LLC v. Apple Inc.,
`583 F. Supp. 3d 769 (W.D. Tex. 2022) ..................................................................................3, 4
`
`USC IP P’ship, L.P. v. Facebook, Inc.,
`No. 6:20-CV-00555-ADA, 2021 WL 3134260 (W.D. Tex. July 23, 2021) ..........................3, 4
`
`VLSI Tech., LLC v. Intel Corp.,
`No. 6:19-CV-000254-ADA, 2019 WL 11025759 (W.D. Tex. Aug. 6, 2019) .......................3, 4
`
`
`
`
`ii
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 4 of 10
`
`Apple’s Opposition resorts to a firehose of mischaracterizations and baseless accusations
`
`of misrepresentation. These dramatics indicate the weakness of Apple’s position. RFCyber
`
`uncovered evidence that Apple knew of the asserted patents, and either knew of or was willfully
`
`blind to infringement. Apple’s purportedly complete interrogatory responses omitted key
`
`information regarding its knowledge, and Mr. Lasker’s deposition was the first time these details
`
`came to light. There is no unfair prejudice to Apple and no continuance is required because Apple
`
`has already taken discovery of these communications, and of RFCyber’s non-involvement despite
`
`Dr. Zheng’s false claims to represent RFCyber. Each good cause factor therefore favors the
`
`amendment alleging willfulness and pre-suit indirect infringement.
`
`Apple’s central argument assumes the false premise that new evidence of its pre-suit
`
`indirect infringement and willfulness is the same as that before the Court when those claims were
`
`dismissed without prejudice. But the evidence showing that Apple knew of the asserted patents
`
`and that it infringed them, or was willfully blind to infringement, is new. First, Mr. Lasker admitted
`
`that Apple knew of the asserted patents. Dkt. 133-6, 128:9-129:1, 126:3-13. Second, Mr. Lasker
`
`testified
`
`
`
` Ex. V, Lasker Dep. 105:14-107:1. Third, Mr. Lasker testified regarding that process,
`
` Dkt. 133-6, 110:18-111:3 (emphasis added). Fourth, Mr. Lasker testified that
`
`
`
` Dkt. 133-6, 117:16-25. Fifth,
`
`
`
`
`
`.
`
`Finally, in view of Mr. Lasker’s admissions, the Dr. Zheng’s emails show that Apple knew
`
`of its infringement or was willfully blind. Dr. Zheng stated that
`
`
`
`
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 5 of 10
`
`
`
`” Dr. Zheng also made a claim chart available to Apple, which Apple declined to review.
`
`See Dkt. 133-4. Contrary to Apple’s suggestion, these emails were not before the Court when the
`
`renewed motion to dismiss was decided because Apple did not produce them until afterwards, and
`
`their significance was not clear until Mr. Lasker admitted to Apple’s review and knowledge based
`
`on those emails. Each good cause factor therefore weighs in favor of granting the Motion.
`
`A. The Amendment is Important and Presents an Exceptionally Strong Case
`Apple does not dispute that renewal of RFCyber’s knowledge and willfulness claims would
`
`be important. Instead, Apple takes the extreme position that these claims are futile. But Apple
`
`ignores the substance of the newly discovered evidence, and falsely asserts that new evidence of
`
`record is the same as when RFCyber’s claims were dismissed without prejudice. It is not.
`
`The new evidence supports an exceptionally strong case for pre-suit indirect infringement
`
`and willfulness. The evidence establishes Apple knew of the patents, and that Apple knew of its
`
`infringement of those patents at least based on: (1) Dr. Zheng’s communications; (2) Apple’s
`
`review of those patents when it cited to them in its own patent applications; and (3) Apple’s review
`
`. The evidence also establishes a strong case for
`
`willful blindness, at least because: (1) Apple deliberately structured its patent acquisition
`
`
`
` and designed policies
`
`disseminating information regarding its infringement
`
` and against
`
` so as to deliberately
`
`turn a blind eye toward infringement; (2) Apple declined to review the claim chart that Dr. Zheng
`
`prepared to avoid learning more about its infringement; (3) Apple continued to avoid review of
`
`those patents even after it cited them while prosecuting its own patents; and (4) Apple conducted
`
`patent searches regarding mobile payments which it is withholding.
`
`2
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 6 of 10
`
`Based on this new evidence, a jury could easily conclude that Apple both knew of the
`
`Asserted Patents (e.g., based on Mr. Lasker’s admissions), and knew that its acts (or induced acts
`
`of customers) constituted infringement (e.g., based on Dr. Zheng’s statements that
`
`
`
`
`
`). A jury could also conclude that Apple was willfully blind to infringement
`
`by taking deliberate actions to avoid learning of infringement (e.g., by declining to review Dr.
`
`Zheng’s claim charts and avoiding consultation with technical personnel) while subjectively aware
`
`of a high probability that it infringed (e.g., from its numerous reviews, and Dr. Zheng’s statements)
`
`Apple’s arguments that the amendment is futile boil down to evidentiary quibbles, not
`
`issues with RFCyber’s prima facie case. For example, Apple argues that it could have thought that
`
`the claim chart that Dr. Zheng made available for review was somehow directed to infringement
`
`by a different company. Dkt. 137 at 13. Apple’s interpretations strain credulity and cannot negate
`
`RFCyber’s prima facie case for pre-suit indirect infringement and willfulness. Apple further
`
`mischaracterizes RFCyber’s position in an attempt to equate it with inapposite case law concerning
`
`bare knowledge of the existence of a patent (citing Atlas Glob. Techs.), or complaints which did
`
`not actually allege knowledge of infringement based on notice letters (citing BillJCo).
`
`But unlike Atlas Glob. Techs., which concerned bare knowledge that a portfolio existed,
`
`here Apple was given notice that the asserted patents concerned mobile payments shortly after it
`
`launched Apple Pay, and were
`
`
`
` Atlas Glob. Techs., LLC, 2022 WL 16557650, at *5; Dkt. 133-2. Unlike VLSI and USC
`
`IP, which turned on mere existence of a policy or practice of not reviewing others patents, this
`
`case concerns Apple’s much more egregious decisions not to review claim charts it was given
`
`access to, and not to consult with its own technical personnel, even when it was both notified that
`
`3
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 7 of 10
`
`patents were
`
` shortly after launching Apple Pay,
`
`and when it cited those patents in its own patents concerning Apple Pay. VLSI Tech., LLC, 2019
`
`WL 11025759; USC IP P’ship, L.P., 2021 WL 3134260. A jury should be allowed to evaluate
`
`Apple’s outlandish claims that it thought Dr. Zheng’s claim charts could pertain to another
`
`company’s products. Finally, unlike BillJCo, RFCyber specifically asserts that Apple knew of, or
`
`was willfully blind to, its products infringement. BillJCo, LLC, 583 F. Supp. 3d 769. Indeed, Dr.
`
`Zheng’s brochure identified the portfolio as
`
` Dkt. 133-3
`
`
`
`
`
`
`
`(emphasis added). The court’s decision in BillJCo was also based on the peculiar fact that “the
`
`Court…[was] not privy to the June 2019 letter or its contents.” BillJCo, 583 F. Supp. 3d at 777.
`
`Finally, Apple’s suggestion
`
`that RFCyber somehow “disavowed” Dr. Zheng’s
`
`communications is both incorrect, and legally unsupported. Apple apparently conflates whether
`
`Dr. Zheng communications were offers for purposes of licensing (he admits he was not authorized,
`
`and RFCyber had no knowledge of those discussions until discovery in a prior action) with whether
`
`he provided notice for purposes of willfulness and indirect infringement (he did). Knowledge of
`
`the asserted patents does not need to come from an authorized representative, and Dr. Zheng’s
`
`authority is irrelevant to Apple’s knowledge of the patents and its willful infringement.
`
`This factor therefore weighs strongly in favor of allowing the amendment.
`
`B. RFCyber Was Diligent in Pursuing Discovery
`RFCyber diligently investigated Apple’s pre-suit knowledge of the asserted patents, and
`
`pre-suit knowledge of its infringement. But Apple waited until after the Court decided its renewed
`
`motion to dismiss to produce highly relevant email correspondence with Dr. Zheng, and omitted
`
`important details from purportedly complete interrogatory responses. See Ex. W; Dkt. 133-12 at
`
`4
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 8 of 10
`
`23-24, 35. RFCyber had no way of knowing Apple’s review procedures, and deliberate avoidance
`
`of information regarding infringement until Mr. Lasker’s deposition. Apple’s suggestion that
`
`RFCyber should have moved for leave to amend earlier, or somehow known to ask for this
`
`information before Mr. Lasker’s deposition, is a practical impossibility. Apple’s suggestion that
`
`RFCyber somehow failed to collect these emails is a distraction; Apple waited to produce them
`
`until after the Court decided Apple’s own motion, and neither RFCyber nor Dr. Zheng had access
`
`to the communications. This factor therefore weighs in favor of granting leave to amend.
`
`C. Apple Would Not Be Unfairly Prejudiced By the Amendment
`Apple’s argument regarding this factor boils down to an assertion that it could be
`
`prejudiced if it were found to indirectly or willfully infringe, and that it “would need time to
`
`prepare its defense to indirect and willful infringement claims.” Dkt. 137 at 14. But Apple fails to
`
`address how any such prejudice would be unfair. It would not be, particularly as Apple has actively
`
`prepared its defenses, and pursued relevant discovery (including by deposing Dr. Zheng).
`
`D. No Continuance is Required
`The amendment would not require any continuance, or even any additional discovery.
`
`Apple does not actually allege it would need a continuance. Nor can Apple identify specific
`
`“additional discovery” which it has not already taken. This is because Apple already subpoenaed
`
`Dr. Zheng, took his deposition on these exact issues, and issued relevant interrogatories. Dkt. 133-
`
`13 at 11. While Apple suggests it may require additional discovery from Dr. Zheng, he already
`
`searched his records and testified on these topics in a seven-hour deposition. Apple’s mudslinging
`
`accusations of spoliation based on the unsurprising fact that Dr. Zheng does not possess emails
`
`exchanged approximately seven years ago are unfounded and meritless. Any discovery would
`
`similarly be duplicative of that already taken. This factor favors leave to amend the complaint.
`
`RFCyber respectfully requests that the Court grant the Motion.
`
`5
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 9 of 10
`
`
`Dated: February 28, 2023
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
` /s/ Jacob Ostling
`Raymond W. Mort, III
`Texas State Bar No. 00791308
`Email: raymort@austinlaw.com
`THE MORT LAW FIRM, PLLC
`100 Congress Avenue, Suite 2000
`Austin, Texas 78701
`Tel/Fax: 512-865-7950
`
`OF COUNSEL:
`
`Alfred R. Fabricant (Admitted Pro Hac Vice)
`NY Bar No. 2219392
`Email: ffabricant@fabricantllp.com
`Peter Lambrianakos (Admitted Pro Hac Vice)
`NY Bar No. 2894392
`Email: plambrianakos@fabricantllp.com
`Vincent J. Rubino, III (Admitted Pro Hac Vice)
`NY Bar No. 4557435
`Email: vrubino@fabricantllp.com
`Richard M. Cowell (Admitted Pro Hac Vice)
`NY Bar No. 4617759
`Email: rcowell@fabricantllp.com
`Jacob Ostling (Admitted Pro Hac Vice)
`NY Bar No. 5684824
`Email: jostling@fabricantllp.com
`FABRICANT LLP
`411 Theodore Fremd Avenue, Suite 206 South
`Rye, New York 10580
`Telephone: (212) 257-5797
`Facsimile: (212) 257-5796
`
`ATTORNEYS FOR PLAINTIFF
`RFCYBER CORP.
`
`
`
`6
`
`

`

`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 10 of 10
`Case 6:21-cv-00916-ADA Document 146 Filed 03/13/23 Page 10 of 10
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that all counsel of record who have consented to electronic service are
`
`being served with a copy of this documentvia electronic mail on February 28, 2023.
`
`Talso herebycertify that all counsel of record who have consentedto electronic service are
`
`being served with a notice offiling of this document, under seal, pursuant to L-.R. CV-5(a)(7) on
`
`February 28, 2023.
`
`/s/ Jacob Ostling
`Jacob Ostling
`
`

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