throbber
IPR2021-01492 of Patent No. 10,257,319
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_________
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_________
`
`
`
`NETNUT LTD.,
`
`Petitioner,
`
`v.
`
`BRIGHT DATA LTD. (f/k/a Luminati Networks Ltd.),
`
`Patent Owner.
`
`_________
`
`
`
`Cases IPR2021-01492
`
`Patent No. 10,257,319
`
`_________
`
`
`
`PETITIONER’S PRE-INSTITUTION REPLY AS TO THE APPLE V. FIN-
`TIV ANALYSIS IN THE PATENT OWNER’S PRELIMINARY RESPONSE
`
`
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`The Petition in this case was filed very early. Unable to rebut Petitioner’s
`
`diligence in requesting this proceeding, Patent Owner’s Preliminary Response in-
`
`stead pursues lengthy arguments on a host of irrelevant considerations in an effort
`
`to create a false impression of delay. The POPR has little to offer on the merits,
`
`other than previously discredited claim construction arguments. The following will
`
`recap the Fintiv factors as they stand and reply to Patent Owner’s (Bright Data’s)
`
`erroneous and misplaced arguments.
`
`1. Stays. Patent Owner argues that the district court will not issue a stay, and
`
`that the Board should decline to act based on that prediction. But Patent Owner
`
`fails to account for the early stage of the district court litigation: Markman briefing
`
`has not begun and the district court has not issued any substantive orders. See Ex.
`
`2003 (district court Docket Control Order). Patent Owner also fails to acknowledge
`
`that the district court has demonstrated a willingness to stay proceedings where an
`
`IPR has actually been instituted. See, e.g., Uniloc USA, Inc. v. Ringcentral, Inc.,
`
`No. 17-cv-0354 (JRG) (Feb. 12, 2018) (benefits of stay post-institution outweighed
`
`costs of postponing resolution of case, where claims had not yet been construed,
`
`discovery was not complete, and there was “a significant likelihood that the out-
`
`come of the IPR proceedings will streamline the scope of th[e] case”). The reality
`
`is that this factor is neutral. See Google LLC v. RFCyber Corp., PGR2021-0029,
`
`
`
`- 1 -
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`Paper 10 at 18-19 (PTAB July 23, 2021); see also Apple Inc. v. Fintiv, Inc.,
`
`IPR2020-00019, Paper 15 at 12 (PTAB May 13, 2020).
`
`2. Proximity of trial date. Assuming matters proceed as currently sched-
`
`uled, the trial would begin in in September 2022, six months before a final written
`
`decision is due in this case. See Ex. 2003. However, trial dates for this Patent
`
`Owner have previously slipped, as reflected in the docket sheet (Ex. 1101) for Pa-
`
`tent Owner’s recent trial (jury selection delayed from May 3 (id., D.I. 65) to Nov.
`
`1, 2021 (id., D.I. 509)). Patent Owner has already sought two extensions in the re-
`
`lated court proceeding, Ex. 1102 (D.I. 79, 80), including an extension that would
`
`push back its own source code review by nearly a month, potentially impacting
`
`other schedules, which was partially granted (for a week). Ex. 1103. In sum, this
`
`factor does not favor discretionary denial nearly as strongly as Patent Owner ar-
`
`gues.
`
`3. Investment in parallel court proceedings; Petitioner’s diligence. The
`
`parties have completed only limited work in the district court proceeding, for ex-
`
`ample, only recently exchanging infringement and invalidity contentions and claim
`
`constructions. No depositions have been taken or noticed. The majority of work in
`
`fact discovery remains ahead—not to mention upcoming expert discovery, sum-
`
`mary judgment proceedings, pretrial proceedings, and a jury trial. Patent Owner
`
`
`
`- 2 -
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`dwells instead on what it says the parties “will have done” by March of 2023,
`
`which of course may be more than has been done to date, but is irrelevant.
`
`Patent Owner’s suggestion of “delay” from when “NetNut started its invalid-
`
`ity campaign at the USPTO” is misguided and erroneous rhetoric and not part of
`
`the Fintiv delay analysis. The events against which Patent Owner seeks to measure
`
`alleged delay concern other patents, parties, and types of proceedings, as well as
`
`the results of its own litigiousness; they lack the necessary nexus to what can fairly
`
`be charged against the Petitioner.
`
`In a case where court proceedings were in at least a comparable state, and
`
`where the petitioner filed its IPR eight months before its deadline to do so, the
`
`Board found that “Petitioner’s diligence in filing the Petition also weighs in favor
`
`of not exercising discretion to deny institution.” PEAG LLC v. VARTA Microbattery
`
`Gmbh, IPR2020-01212, Paper 8 at 20 (Jan. 6, 2021). Here, the Petition was filed
`
`ten months before the corresponding deadline—an even stronger showing of dili-
`
`gence. This strongly weighs against exercising discretion to deny institution.
`
`4. Overlap of issues. As the POPR acknowledges (at 29), there are four de-
`
`pendent claims in this proceeding and five in the related proceeding (IPR2021-
`
`01493), which are not at issue in the district court litigation. In addition, additional
`
`grounds of invalidity, as well as unenforceability for inequitable conduct, not reme-
`
`diable here, will be at issue in the district court case. See Ex. 1104. (NetNut’s
`
`
`
`- 3 -
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`invalidity contentions). There is overlap, but the overlap is not nearly complete,
`
`given the separate invalidity arguments made on the additional dependent claims in
`
`this proceeding and the additional grounds asserted in the district court.
`
`5. Identity of parties. The parties are the same.
`
`6. Other circumstances, including the merits. Patent Owner’s arguments
`
`about other USPTO proceedings challenging the ’319 and ’510 patents are irrele-
`
`vant. If anything, those are reasons for the Board to institute (and then consolidate
`
`or stay those other proceedings). The two granted reexaminations involving these
`
`patents indicate the questionable patentability of the claims, which favors institu-
`
`tion under Fintiv factor 6. Bright Data cites the fact that it won a jury verdict on
`
`one of the invalidity references in this case, a determination that has neither bind-
`
`ing (as against a third party) nor precedential weight (see Stevenson v. Sears, Roe-
`
`buck & Co., 713 F.2d 705, 711 (Fed. Cir. 1983)), and no relevance to institution.
`
`As to the merits, Bright Data continues to argue, using partial quotes that
`
`contradict applicable rulings (see, e.g., POPR at 37-38), that clients and servers are
`
`mutually exclusive categories, and that a “communication device” must somehow
`
`do something more than communicate. In addition to being incoherent on their
`
`face, these arguments have repeatedly been rejected by the court, which found that
`
`the devices in question may be configured to operate in different roles and are
`
`characterized by the function they perform (i.e., sending or receiving), not by any
`
`
`
`- 4 -
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`physical properties. Exs. 1017 at 12, 1020 at 10, 1021 at 64. The Board likewise al-
`
`ready rejected Patent Owner’s similar arguments in IPR2021-00458 and IPR2021-
`
`00465. See, e.g., Exs. 1105 at 18-21, 1106 at 13-15 (device assuming two or more
`
`roles, either at different times or simultaneously).
`
`Conclusion. The record reflects that Petitioner was extraordinarily diligent
`
`in filing its Petition, just two months after service in the district court and ten
`
`months prior to the time allowed; that there has not been substantial investment in
`
`the district court proceeding; the district court’s record of willingness to consider a
`
`stay where an IPR has been instituted; and that Petitioner presents a strong show-
`
`ing on the merits of unpatentability, with opposition of only a token nature. Patent
`
`Owner’s attempts to rely on irrelevant collateral developments, such as reexamina-
`
`tions on other patents and a prior jury determination, and to repeat previously re-
`
`jected substantive arguments, highlight its weak position. On balance, these facts
`
`outweigh the partial overlap of the issues between the proceedings and the fact that
`
`the trial date is currently (though not immovably) set for six months before a final
`
`written decision is due in this proceeding. The patent here cries out for Petitioner’s
`
`requested review.
`
`Accordingly, Petitioner respectfully submits that the Board should decline to
`
`exercise its discretion under 35 U.S.C. § 314(a) to deny institution.
`
`
`
`- 5 -
`
`
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`Respectfully submitted,
`
`/Ronald Abramson/
`Ronald Abramson, Reg. No. 34,762
`Ari J. Jaffess, Reg. No. 74,558
`M. Michael Lewis, Reg. No. 50,478
`
`
`Dated: January 18, 2022
`LISTON ABRAMSON LLP
`The Chrysler Building
`405 Lexington Avenue, 46 FL
`New York, NY 10174
`Telephone: (212) 822-0163
`
`
`
`
`
`- 6 -
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that on January 17, 2022, a complete and entire
`
`copy of this Petitioner’s Pre-Institution Reply to Patent Owner’s Preliminary Re-
`
`sponse was provided to the Patent Owner by filing through the PTAB E2E System
`
`and via email to Thomas M. Dunham <tomd@ruyakcherian.com> and Elizabeth A.
`
`O'Brien <elizabetho@ruyakcherian.com> as authorized in Patent Owner’s manda-
`
`tory notices.
`
`
`Dated: January 18, 2022
`
`/Ronald Abramson/
`Ronald Abramson
`
`
`
`- 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