throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_________________________
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_________________________
`
` NETNUT LTD.,
`
`Petitioner
`
`v.
`
`BRIGHT DATA LTD.,
`
`Patent Owner
`
`_________________________
`
`Case IPR2021-01492
`
`Patent No. 10,257,319
`
`_________________________
`
`
`
`
`
`PATENT OWNER’S SUR-REPLY TO PETITIONER’S REPLY TO
`PATENT OWNER’S PRELIMINARY RESPONSE UNDER
`AUTHORIZATION FROM THE BOARD1
`
`
`
`
`Mail Stop PATENT BOARD
`Patent Trial and Appeal Board
`United States Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`1 Authorized via email on January 7, 2022.
`
`
`
`i
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`PATENT OWNER’S LIST OF ADDITIONAL EXHIBITS
`
`Exhibit
`Number
`
`2011
`
`2012
`
`2013
`
`2014
`
`2015
`
`2016
`
`2017
`
`
`
`
`
`
`
`
`
`Description
`
`Order, Uniloc USA, Inc. v. Ringcentral, Inc., No. 2-17-cv-354, Dkt.
`100 (E.D. Tex. Feb. 12, 2018)
`
`Motion, Uniloc USA, Inc. v. Ringcentral, Inc., No. 2-17-cv-354,
`Dkt. 97 (E.D. Tex. Feb. 8, 2018)
`
`Order, Uniloc USA, Inc. v. Ringcentral, Inc., No. 2-17-cv-354, Dkt.
`99 (E.D. Tex. Feb. 9, 2018)
`
`Joint Motion, Bright Data Ltd. v. NetNut Ltd., No. 2:21-cv-225,
`Dkt. 79 (E.D. Tex. Dec. 22, 2021)
`
`Motion, Bright Data Ltd. v. NetNut Ltd., No. 2:21-cv-225, Dkt. 80
`(E.D. Tex. Dec. 23, 2021)
`
`Letter, dated Dec. 30, 2021, from Bright Data Ltd. to NetNut Ltd.
`regarding the scheduling of depositions in the case of Bright Data
`Ltd. v. NetNut Ltd., No. 2:21-cv-225 (E.D. Tex.)
`
`Declaration of Mr. Thomas M. Dunham
`
`
`
`
`ii
`
`
`
`
`
`

`

`
`
`IPR2021-01492 of Patent No. 10,257,319
`
`Patent Owner respectfully submits this Sur-Reply in response to Petitioner’s
`
`Reply (Paper 10) relating to the discretionary factors in Apple Inc. v. Fintiv, Inc.,
`
`IPR2020-0019, Paper 11 (PTAB March 20, 2020)(precedential)(“Fintiv”).
`
` Regarding Fintiv factor 1, Patent Owner has explained that it is unlikely that
`
`the judge will issue a stay, even if review is instituted, given that the NetNut
`
`Litigation will “clearly [be] at an advanced stage” as of the 3/27/2022 deadline for
`
`an institution decision. (See Patent Owner Preliminary Response (“POPR”)(Paper
`
`9)
`
`at
`
`19-20).
`
` Petitioner’s cited Uniloc case (Dkt. 100, dated 2/12/2018, EX. 2011) is
`
`inapplicable because (a) that Court had already granted an unopposed motion to stay
`
`(Dkt. 97, EX. 2012) filed by the plaintiff (see Dkt. 99, dated 2/9/2018, EX. 2013);
`
`and (b) the Board instituted review of every asserted claim of all asserted patents
`
`and as of the institution decision, the claims had not yet been construed by that Court.
`
`Uniloc USA, Inc. v. Ringcentral, Inc., No. 2-17-cv-354 (E.D. Tex.). Unlike Uniloc,
`
`the Board will not resolve every asserted claim of all asserted patents in the NetNut
`
`Litigation (see, e.g., POPR at 29; see also EX. 2002 at 22) and the Court has already,
`
`previously construed claim terms from the asserted ‘319 and ‘510 Patents (see, e.g.,
`
`POPR at 14). Accordingly,
`
`this
`
`factor weighs
`
`in
`
`favor of denial.
`
`
`2 There is a total of five asserted patents in the NetNut Litigation.
`
`
`
`1
`
`

`

`
`
`IPR2021-01492 of Patent No. 10,257,319
`
` Regarding Fintiv factor 2, the NetNut Litigation has trial scheduled approx.
`
`6.5 months before the 3/27/2023 deadline for a final written decision (see POPR at
`
`21-22) and the Board has previously declined to speculate whether there may be
`
`further
`
`delays
`
`in
`
`the
`
`district
`
`court
`
`(see
`
`POPR
`
`at
`
`23).
`
` Petitioner’s implication regarding extensions (see Reply at 2) is misleading.
`
`First, the parties submitted a Joint Motion (Dkt. 79, EX. 2014) for a 1-month
`
`extension to continue additional mediation with the same Judge Gandhi, rather than
`
`the new Judge Folsom. That mediation occurred on 1/25/2022. Second, Patent
`
`Owner submitted a Motion (Dkt. 80, EX. 2015) for a 3-week extension to amend
`
`infringement contentions based on source code review given that (a) the expert could
`
`not begin his review until 1/5/2022 given the holidays and his work schedule and (b)
`
`this left insufficient time to amend infringement contentions by 1/13/2022 for the
`
`five asserted patents. The Court granted-in-part the Motion and extended the
`
`deadline to 1/26/2022. (EX. 1103). Neither of these requested extensions suggests
`
`Patent Owner intends to delay the 9/12/2022 trial date in the NetNut Litigation.
`
`Accordingly,
`
`this
`
`factor
`
`weighs
`
`in
`
`favor
`
`of
`
`denial.
`
` Regarding Fintiv factor 3, Patent Owner has explained that the parties will
`
`have invested significant resources in the NetNut Litigation by the 3/27/2022
`
`deadline for an institution decision (see POPR at 22 (citing section III.A.1 at 19-
`
`20)). This
`
`is consistent with
`
`the Fintiv analysis. (See Fintiv at 9-10).
`
`
`
`2
`
`

`

`
`
`IPR2021-01492 of Patent No. 10,257,319
`
`Also, Petitioner’s statement that “[n]o depositions have been taken or noticed” (see
`
`Reply at 2) is misleading. On 12/30/2021, Patent Owner sent a letter to Petitioner
`
`regarding the scheduling of depositions February 14-25, 2022 for seven of
`
`Petitioner’s employees. (EX. 2016). Petitioner sent a response on 1/11/2022 and
`
`there has been subsequent email correspondence regarding availability of witnesses.
`
` Moreover, “[t]his investment factor is related to the trial date factor”. (Fintiv
`
`at 10). Patent Owner anticipated Petitioner’s argument regarding the possibility of a
`
`delayed trial date (see Reply at 2) and has explained that the parties will have
`
`invested even more resources by the 3/27/2023 deadline for a final written decision
`
`(see POPR at 23-24). There are many asterisked deadlines in the Docket Control
`
`Order (EX. 2003) unlikely to change, even if the trial date is ultimately changed.
`
` Furthermore, Petitioner argues alleged diligence (see Reply at 3) based on the
`
`timing of the Petition relative to the statutory deadline. However, Petitioner attempts
`
`to minimize the timing of the Petition relative to the investment/progress in the
`
`NetNut Litigation. Also, Petitioner fails to explain its alleged diligence in view of
`
`its other litigation activity. Petitioner merely states that those “events… concern
`
`other patents, parties, and types of proceedings.” (Reply at 3). However, Petitioner
`
`has not explained (a) when it became aware of the ‘319 and ‘510 Patents and/or (b)
`
`when it became aware of the Crowds, Border, and Morphmix references, in order to
`
`justify why Petitioner could not have filed the Petitions before September 2021.
`
`
`
`3
`
`

`

`
`
`IPR2021-01492 of Patent No. 10,257,319
`
` Patent Owner has shown that Petitioner (a) was aware of unasserted patents in
`
`Patent Owner’s portfolio3 and (b) was aware of at least the Crowds and MorphMix
`
`references4, long before September 2021. (See POPR at 24-28). Because the
`
`Petitions could have been filed before significant investment/progress in the NetNut
`
`Litigation,
`
`this factor weighs
`
`in favor of denial. (See Fintiv at 11).
`
` Regarding Fintiv factor 4, given that there is only one independent claim in
`
`each of the ‘319 and ‘510 Patents, there is a high risk of inefficiency if institution is
`
`granted. (See POPR at 29-30). Patent Owner respectfully submits that it would be
`
`“inefficient to proceed because the district court may resolve validity of enough
`
`overlapping claims to resolve key issues in the petition.” (Fintiv at 13). Also,
`
`Petitioner did not address the absence of any prior art stipulation in its Reply.
`
` Regarding Fintiv factor 5, Petitioner did not address the duplicative
`
`costs/efforts in view of the other district court proceedings involving the ‘319 and
`
`‘510 Patents in its Reply. (See POPR at 30-33; see also Fintiv at 14).
`
`
`
`Regarding Fintiv factor 6, Patent Owner disagrees that the other proceedings
`
`
`3 Petitioner filed petitions in IPR2021-00458 and IPR2021-00465 against Patent
`
`Nos. 9,241,044 and 9,741,866 in January 2021. (See also POPR at 24-26).
`
`4 Petitioner cited Crowds and MorphMix in its invalidity contentions served
`
`November 2020. (See also POPR at 26-28).
`
`
`
`4
`
`

`

`
`
`IPR2021-01492 of Patent No. 10,257,319
`
`involving the ‘319 and ‘510 Patents (see POPR, section II, at 10-17) have “no
`
`relevance” (Reply at 4) to the Board’s exercise of discretion. As explained in the
`
`POPR, there is a high risk of duplicative efforts at the USPTO and in district court.
`
` Petitioner did not address the lack of merit in the substantially similar
`
`Code200/Teso Petitions5 or the issues of hindsight bias in its Reply. Instead,
`
`Petitioner repeats unsuccessful arguments about the solely-role-based distinction of
`
`“client device” vs. “second server.” Patent Owner maintains its claim construction
`
`arguments (see POPR at 37-38) are consistent with the Court’s orders. (See also
`
`POPR, section IV.D, at 48-52). Moreover, Petitioner’s reference to IPR2021-00458
`
`and -00465, involving different patent specifications and claims, is misleading. (See
`
`Reply at 5). The Court explicitly stated that, in the context of the ‘319 and ‘510
`
`Patents, a “component can be configured to operate in different roles –so long as it
`
`does not “simultaneously serve as more than one of: the client device, the first
`
`server/second server, and the web server.”” (EX. 1020 at 10 (emphasis added)).
`
` On balance, as discussed in the POPR and this Sur-Reply, Patent Owner
`
`respectfully submits that there is a high risk of duplicative costs/efforts and
`
`therefore, granting institution would be an inefficient use of the Board’s resources.
`
`
`5 The merits did not outweigh the other Fintiv factors when trial was approx. 7
`
`months before the deadline for a final written decision. (See POPR at 15-16).
`
`
`
`5
`
`

`

`
`
`
`Date: January 28, 2022
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`IPR2021-01492 of Patent No. 10,257,319
`
`Respectfully submitted,
`
`
`
`
`
`By: /s/ Thomas M. Dunham
`Thomas M. Dunham
`Reg. No. 39,965
`
`RuyakCherian LLP
`1901 L Street NW, Suite 700
`Washington, D.C. 20036
`(202) 838-1567
`
`ATTORNEY FOR PATENT OWNER,
`BRIGHT DATA LTD.
`
`6
`
`

`

`IPR2021-01492 of Patent No. 10,257,319
`
`CERTIFICATE OF COMPLIANCE WITH TYPE-VOLUME LIMITS
`
`
`
`
`
`This Paper consists of no more than 5 pages, excluding certificate of service,
`
`this certificate, or table of exhibits. The Paper complies with the type-volume
`
`limitation of 5 pages as authorized by the Board via email on January 7, 2022.
`
`
`
`
`Date: January 28, 2022
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`By: /s/ Thomas M. Dunham
`
`Thomas M. Dunham
`Reg. No. 39,965
`
`RuyakCherian LLP
`1901 L Street NW, Suite 700
`Washington, D.C. 20036
`(202) 838-1567
`
`ATTORNEY FOR PATENT OWNER,
`BRIGHT DATA LTD.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`7
`
`

`

`
`
`IPR2021-01492 of Patent No. 10,257,319
`
`CERTIFICATE OF SERVICE
`
`
`Pursuant to 37 C.F.R. § 42.6(e), the undersigned hereby certifies this Paper
`
`and all exhibits thereto were served on the undersigned date via email, as authorized
`
`by Petitioner, at the following email addresses:
`
`ron.abramson@listonabramson.com
`
`ari.jaffess@listonabramson.com
`
`michael.lewis@listonabramson.com
`
`
`
`
`
`
`
`
`
`Date: January 28, 2022
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`By: /s/ Thomas M. Dunham
`
`Thomas M. Dunham
`Reg. No. 39,965
`
`RuyakCherian LLP
`
`1901 L Street NW, Suite 700
`
`Washington, D.C. 20036
`
`(202) 838-1567
`
`ATTORNEY FOR PATENT OWNER,
`BRIGHT DATA LTD.
`
`8
`
`

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