throbber

`Case: 24-2265 Document: 18 Page: 1 Filed: 09/18/2024
`
`No. 2024-2265
`
`UNITED STATES COURT OF APPEALS FOR THE FEDERAL CIRCUIT
`
`
`VIDSTREAM LLC,
`
`
`Plaintiff-Appellant,
`
`v.
`TWITTER, INC.,
`
`
`
`
`
`
`Defendant-Appellee.
`
`
`On Appeal from the United States District Court for The Northern District of Texas
`Case No. 3:16-cv-00764-N, Judge David C. Godbey
`
`APPELLANT VIDSTREAM, LLC’S REPLY TO MOTION TO EXPEDITE
`INTERLOCUTORY APPEAL
`
`Austin Curry
` Counsel of Record
`Bradley W. Caldwell
`Jason D. Cassady
`John F. Summers
`Hamad M. Hamad
`CALDWELL CASSADY & CURRY, PC
`2121 N. Pearl Street, Suite 1200
`Dallas, TX 75201
`(214) 888-4848 (telephone)
`(214) 888-4849 (fax)
`
`
`
`Counsel for VidStream, LLC
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`
`Case: 24-2265 Document: 18 Page: 2 Filed: 09/18/2024
`
`
`
` I. ARGUMENT IN REPLY .................................................................................... 1
`
`TABLE OF CONTENTS
`
`A. Twitter’s Request for Time to Draft “Alternative Arguments” Is
`Complication Only to Create Delay. ......................................................... 2
`B. VidStream Did Not Unreasonably Delay in Seeking Relief. .................... 4
`C. VidStream’s Motion to Expedite Is Not Premature. ................................. 5
`D. Twitter’s Other Arguments Are Wrong. ................................................... 5
`II. CONCLUSION .................................................................................................... 6
`
`
`
`
`
`
`i
`
`

`

`
`Case: 24-2265 Document: 18 Page: 3 Filed: 09/18/2024
`
`
`
`TABLE OF AUTHORITIES
`
`
`Cases
`
`Acumed LLC v. Stryker Corp.
` 483 F.3d 800 (Fed. Cir. 2007) ................................................................................ 3
`
`Apple, Inc. v. Samsung Electronics, Co., Ltd.
` 678 F.3d 1314 (Fed. Cir. 2012) .............................................................................. 3
`
`Duhart v. United States
` 143 F. App’x 355 (Fed. Cir. 2005) ......................................................................... 5
`
`Ecolab, Inc. v. FMC Corp.
` 569 F.3d 1335 (Fed. Cir. 2009) .............................................................................. 3
`
`Illumina, Inc. v. Qiagen, N.V.
` 207 F. Supp. 3d 1081 (N.D. Cal. 2016) .................................................................. 4
`
`Jack Guttman, Inc. v. Kopykake Enters., Inc.
` 302 F.3d 1352 (Fed. Cir. 2002) .............................................................................. 3
`
`Joshua v. United States
` 17 F.3d 378 (Fed. Cir. 1994) .................................................................................. 7
`
`Novartis Pharms. Corp. v. Accord Healthcare Inc.
` No. CV 18-1043-LPS, 2019 WL 2588450 (D. Del. June 24, 2019) ...................... 5
`
`Rules
`
`Fed. Cir. R. 31(c) ....................................................................................................... 5
`
`ii
`
`

`

`
`
`I.
`
`
`Case: 24-2265 Document: 18 Page: 4 Filed: 09/18/2024
`
`ARGUMENT IN REPLY
`Twitter’s opposition to VidStream’s Motion to Expedite serves only to
`
`highlight the need for this Court’s intervention to expedite this appeal. This appeal
`
`involves the denial of a preliminary injunction, and Twitter has filed a motion for
`
`summary affirmance.
`
`The Court should not countenance Twitter’s attempts to delay resolution of
`
`this appeal with unnecessary process. This is a one-issue appeal of a preliminary
`
`injunction request in a case that is already nine years old. In the district court
`
`briefing, Twitter was given seven weeks to respond to VidStream’s motion for
`
`preliminary injunction—a lengthy extension that VidStream did not oppose. D. Ct.
`
`Dkts. 262, 270, and 275. At this point, Twitter has had over nine months to
`
`evaluate its position. Certainly, Twitter can present whatever arguments it wants
`
`in its response brief. But if its position were truly so well-founded that summary
`
`affirmance were appropriate, then Twitter could simply present its same argument
`
`on an expedited basis. Twitter’s purported need for more time to present its
`
`alternative arguments suggests that Twitter lacks confidence in the argument it
`
`presented in its motion for summary affirmance.
`
`Moreover, Twitter’s “alternative grounds for affirmance” are almost
`
`certainly irrelevant. The district court did not make findings about delay, the
`
`likelihood of success on the merits, hardship, public interest, or any other ground
`
`1
`
`

`

`
`Case: 24-2265 Document: 18 Page: 5 Filed: 09/18/2024
`
`
`
`that might justify withholding equitable relief. The district court did not even
`
`disagree that, under the traditional principles of equity as reflected by Chancery
`
`practice, ongoing infringement, when the plaintiff established it, was recognized as
`
`irreparable injury. The district court denied VidStream’s motion because this
`
`Court has not previously applied these traditional principles of equity. VidStream
`
`is asking for the district court to be appropriately instructed on this narrow issue.
`
`On remand, the district court might still decline to enjoin Twitter for delay, the
`
`likelihood of success on the merits, etc. But, as this Court has repeatedly
`
`recognized, it is the district court who should be the first to make findings of fact
`
`on any and all of Twitter’s alternative arguments.
`
`For these reasons and those described in more detail below, the Court should
`
`grant expedited consideration.
`
`A. Twitter’s Request for Time to Draft “Alternative Arguments” Is
`Complication Only to Create Delay.
`To avoid expedited consideration, Twitter first points out that “this Court
`
`
`
`may affirm below on any ground apparent in the record,” and contends that
`
`“considering other possible grounds for denial . . . would be most efficient”—
`
`threatening to present a morass of alternative arguments for the Court to “wad[e]
`
`through.” Opp. at 6-7. But there is no need for Twitter to brief these “many
`
`alternative arguments,” Dkt. 5 at 2 n.2, as the Court is nearly certain not to
`
`entertain them. This Court has repeatedly and routinely refused to act as a “first-
`
`2
`
`

`

`
`Case: 24-2265 Document: 18 Page: 6 Filed: 09/18/2024
`
`
`
`line court of equity,” a role that belongs “exclusively to the district court.”
`
`Acumed LLC v. Stryker Corp., 483 F.3d 800, 811 (Fed. Cir. 2007). See also Apple,
`
`Inc. v. Samsung Electronics, Co., Ltd., 678 F.3d 1314, 1332-33 (Fed. Cir. 2012)
`
`(remanding to the district court for consideration of remaining factors because “[i]t
`
`is normally not appropriate for this court to make such highly factual inquiries for
`
`the first time on appeal.”); Jack Guttman, Inc. v. Kopykake Enters., Inc., 302 F.3d
`
`1352, 1362-63 (Fed. Cir. 2002) (holding that “the appropriate remedy is not to
`
`reverse with instructions to enter the injunction . . . but rather to vacate the trial
`
`court’s previous order and remand for furthering proceedings”). Twitter’s
`
`opposition demanding time to brief these arguments fails to cite a single instance in
`
`which this Court has decided substantive issues related to injunctive relief in the
`
`first instance, nor does Twitter explain how this Court could even do so when the
`
`Court’s review of injunction issues is abuse of discretion. See Ecolab, Inc. v. FMC
`
`Corp., 569 F.3d 1335, 1352 (Fed. Cir. 2009) (“[W]e decline to analyze the eBay
`
`factors in the first instance.”).
`
`
`
`While VidStream cannot stop Twitter from wasting its own resources in
`
`briefing irrelevant alternative issues, Twitter’s apparent intention to do so is no
`
`legitimate basis to avoid expedited consideration of this one-issue appeal.
`
`3
`
`

`

`
`Case: 24-2265 Document: 18 Page: 7 Filed: 09/18/2024
`
`
`
`B. VidStream Did Not Unreasonably Delay in Seeking Relief.
`Twitter next opposes expedited briefing by implying that VidStream’s
`
`alleged delay in filing its preliminary injunction motion is grounds to deny
`
`expedited consideration as well. Twitter argues that VidStream was somehow
`
`responsible for this case’s lengthy pendency. Opp. at 3, 8 n.4. But while the
`
`Court’s stay was required by the bankruptcy, the delay in the case (and a
`
`contributing factor for the bankruptcy, itself) was due to the pending IPR
`
`proceedings. It was only after Twitter had lost its IPR petitions, conducted oral
`
`argument on its appeal, and heard from VidStream that VidStream would seek to
`
`lift the district court’s stay that Twitter made any argument at the district court that
`
`VidStream had unreasonably delayed anything. See D. Ct. Dkt. 167 at 7-9.
`
`Contrary to its current arguments, Twitter previously recognized that “[t]he parties
`
`had good reason not to litigate the Asserted Patents until [May 2022]” because the
`
`case was mired in procedure. See D. Ct. Dkt. 217 at 6 n.2.
`
`VidStream also filed its motion for preliminary injunction only three weeks
`
`after Twitter’s invalidity arguments based on indefiniteness were rejected. District
`
`courts have recognized that patent owners are permitted to wait until validity issues
`
`are resolved without prejudicing requests for injunctive relief. See Illumina, Inc. v.
`
`Qiagen, N.V., 207 F. Supp. 3d 1081, 1093 (N.D. Cal. 2016) (finding patent
`
`owner’s alleged delay justified where “the validity [of the asserted patent] hung in
`
`4
`
`

`

`
`Case: 24-2265 Document: 18 Page: 8 Filed: 09/18/2024
`
`
`
`limbo until the Federal Circuit upheld the PTAB’s decision [finding the patent not
`
`invalid in IPR].”); Novartis Pharms. Corp. v. Accord Healthcare Inc., No. CV 18-
`
`1043-LPS, 2019 WL 2588450, at *5 (D. Del. June 24, 2019) (finding irreparable
`
`harm despite accusation that patentee unduly delayed in awaiting results of IPR
`
`petitions).
`
`C. VidStream’s Motion to Expedite Is Not Premature.
`Twitter also contends that VidStream’s request to expedite proceedings is
`
`
`
`“premature” because it has filed a motion that would “terminate [the] appeal” and
`
`thus under Federal Circuit Rule 31(c) “there is no briefing schedule to expedite.”
`
`Opp. at 5. Twitter is wrong. This Court may always alter the briefing schedule,
`
`and “Fed. Cir. R. 31(c) does not excuse the failure to comply with a court order.”
`
`Duhart v. United States, 143 F. App’x 355 (Fed. Cir. 2005) (nonprecedential).
`
`D. Twitter’s Other Arguments Are Wrong.
`Twitter makes two additional arguments against expedited consideration.
`
`
`
`First, Twitter contends that VidStream’s Motion to Expedite improperly seeks a
`
`ruling on its appeal on the irreparable harm issue subject to VidStream’s merits
`
`appeal. Opp. at 5-6. Not so. While the harm that VidStream continues to suffer
`
`from Twitter’s ongoing infringement is a basis to expedite (in addition to the
`
`single-legal-issue nature of the appeal), this Court can certainly expedite briefing
`
`without a showing of irreparable injury. It was Twitter, not VidStream, that
`
`5
`
`

`

`
`Case: 24-2265 Document: 18 Page: 9 Filed: 09/18/2024
`
`
`
`suggested conflating the issues by assuming that irreparable harm is required to
`
`expedite briefing. See Add008-009. The Court can expedite briefing for any
`
`reason, including the harm caused by Twitter’s ongoing infringement, the single-
`
`issue nature of the appeal, the fact the appeal involves a preliminary injunction, or
`
`the upcoming April 2025 trial date.
`
` Finally, Twitter opposes VidStream’s Motion to Expedite because
`
`VidStream “does not even try to show that Twitter has infringed the ’304 patent.”
`
`Opp. at 7. This is a straw-man argument. The district court made no finding about
`
`VidStream’s likelihood of success, and VidStream’s is not asking this Court to
`
`enjoin Twitter at this time. Again, the district court denied VidStream’s motion on
`
`a very narrow issue: that this Court has not yet applied the traditional principles of
`
`equity post-eBay. VidStream is asking this Court to remedy that and instruct the
`
`district court about how those principles worked. From there, on remand, the
`
`district court can evaluate infringement and the other issues that courts should
`
`evaluate when deciding whether to withhold equitable relief.
`
`II. CONCLUSION
`Boiled down, Twitter opposes an accelerated resolution of this appeal
`
`because it intends to present “many alternative arguments,” Dkt. 5 at 2 n.3, that
`
`this Court will likely refuse to consider in the first instance. Twitter’s reluctance to
`
`focus on its primary argument demonstrates that it is not “so clearly correct as a
`
`6
`
`

`

`
`Case: 24-2265 Document: 18 Page: 10 Filed: 09/18/2024
`
`
`
`matter of law that no substantial question regarding the outcome of the appeal
`
`exists.” Dkt. 5 at 2 (quoting Joshua v. United States, 17 F.3d 378, 380 (Fed. Cir.
`
`1994)). In any event, Twitter’s alternative arguments are no reason for further
`
`delay. This is an exceedingly old case, and far too much of the patent’s limited
`
`term has been destroyed by Twitter’s infringement. For the reasons described
`
`above and in VidStream’s Motion, VidStream respectfully requests the Court to
`
`grant VidStream’s request for expedited consideration and to enter VidStream’s
`
`proposed briefing schedule.
`
`
`
`7
`
`

`

`
`Case: 24-2265 Document: 18 Page: 11 Filed: 09/18/2024
`
`
`
`September 18, 2024
`
`
`
`
`
`
`
`Respectfully submitted,
`
`/s/ Austin Curry
`Austin Curry
`Bradley W. Caldwell
`Jason C. Cassady
`John F. Summers
`Hamad M. Hamad
`CALDWELL CASSADY & CURRY, PC
`2121 N. Pearl Street, Suite 1200
`Dallas, TX 75201
`(214) 888-4848 (telephone)
`(214) 888-4849 (fax)
`
`Counsel for VidStream, LLC
`
`
`
`
`
`
`
`
`

`

`
`Case: 24-2265 Document: 18 Page: 12 Filed: 09/18/2024
`
`
`
`CERTIFICATE OF COMPLIANCE
`
`This brief complies with the Federal Rules of Appellate Procedure and Federal
`
`Circuit Rules because:
`
`1. The filing has been prepared using a proportionally spaced typeface and
`
`includes 1,482 words.
`
`2. The foregoing has been prepared using Microsoft Word for Office 365 in
`
`14-Point Times New Roman font.
`
`September 18, 2024
`
`
`
`
`
`
`
`
`
`
`
`/s/ Austin Curry
`
`
`
`
`
`
`
`
`
`

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