In a closely watched patentability dispute before the U.S. Court of Appeals for the Federal Circuit, Cloudflare, Inc. and Sable Networks, Inc. jointly agreed to dismiss Case No. 23-1612 on July 8, 2024, with each party bearing its own costs. The appeal, filed March 20, 2023, centered on U.S. Patent No. US8243593B2, which covers a mechanism for identifying and penalizing misbehaving flows in a network. Dismissed under Fed. R. App. P. 42(b) after 476 days, the resolution leaves the underlying patentability and invalidity questions formally unresolved, offering a nuanced signal to the broader networking and cybersecurity patent landscape.

For patent attorneys, in-house IP teams, and R&D leaders working in network traffic management and quality-of-service technologies, this voluntary dismissal carries strategic weight that extends well beyond the absence of a final ruling. The fate of US8243593B2 remains legally uncertain, making freedom-to-operate assessments for network flow management products a continued priority. Understanding why this appeal ended by mutual agreement — and what it means for patent validity in this technology space — is essential reading for anyone with exposure to misbehaving-flow detection or network policing IP.

Case Overview

The Parties

The Patent at Issue

U.S. Patent No. US8243593B2 (application no. US11/022599) covers a system and method for identifying network flows that behave outside acceptable parameters — commonly referred to as ‘misbehaving flows’ — and applying penalties or restrictions to those flows to protect overall network performance. In practical terms, the technology enables network devices such as routers and switches to detect when a particular data stream is consuming disproportionate bandwidth or otherwise disrupting fair resource sharing, and then throttle or deprioritize that stream accordingly. This type of flow-policing technology is foundational to quality-of-service (QoS) management in enterprise networks, internet service provider infrastructure, and large-scale cloud networking platforms.

• • US8243593B2

Legal Representation

Plaintiff Counsel: Charhon, Callahan, Robson & Garza PLLC (lead: Anthony Matthew Garza)
Defendant Counsel: Berger & Hipskind LLP; Lowenstein & Weatherwax, LLP (lead: Daniel P. Hipskind)

Litigation Timeline & Procedural History

Case No. 23-1612 was brought before the U.S. Court of Appeals for the Federal Circuit, the specialized appellate court with exclusive jurisdiction over patent law appeals in the United States. An appeal at this level indicates that the parties had already litigated or contested the patent’s validity at a lower tribunal — likely before the Patent Trial and Appeal Board (PTAB) or a federal district court — and that at least one party found grounds to challenge the outcome. The Federal Circuit’s role as the final arbiter on patent law questions means that any decision it issues carries significant precedential weight across all U.S. patent disputes in the relevant technology area.

The appeal ran for 476 days from its filing on March 20, 2023, to its closure on July 8, 2024 — a duration consistent with the Federal Circuit’s typical briefing and scheduling cycle, though ultimately no merits decision was reached. The case was resolved through a voluntary dismissal under Fed. R. App. P. 42(b), filed by stipulation of both parties and ordered by the court. This means the parties mutually agreed to end the appeal without a ruling, with each side absorbing its own legal costs. Such agreed dismissals at the appellate level frequently reflect a negotiated resolution of the underlying commercial dispute — whether through settlement, licensing, or a strategic business decision — though the specific terms of any agreement between Cloudflare and Sable Networks were not disclosed in the public record.

The Verdict & Legal Analysis

Outcome

The Federal Circuit dismissed the appeal in Case No. 23-1612 by joint stipulation of Cloudflare, Inc. and Sable Networks, Inc., pursuant to Fed. R. App. P. 42(b), with each party directed to bear its own costs. No damages were awarded, no injunctive relief was issued, and no merits ruling on the patentability or validity of U.S. Patent No. US8243593B2 was rendered. The underlying invalidity or cancellation claims were therefore left unresolved on the public record, meaning the patent’s legal status was not definitively adjudicated by the Federal Circuit.

Verdict Cause Analysis

The appeal arose from a patentability dispute — specifically an invalidity or cancellation action — targeting U.S. Patent No. US8243593B2, and its voluntary dismissal raises several important legal and procedural considerations.

• The verdict cause was classified as an Invalidity/Cancellation Action, indicating that Cloudflare challenged whether Sable Networks’ patent on misbehaving-flow identification met the statutory requirements for patentability, such as novelty and non-obviousness under 35 U.S.C. §§ 102 and 103.
• Because the dismissal was entered by mutual agreement rather than by court order on the merits, US8243593B2 retains its presumption of validity under 35 U.S.C. § 282, meaning it remains an active and enforceable patent that other parties must treat as valid unless and until successfully challenged.
• The cost-bearing arrangement — each side absorbing its own expenses — is a standard feature of Rule 42(b) dismissals and suggests neither party secured a clear litigation advantage, consistent with a negotiated resolution rather than a unilateral concession.
• The fact that both Cloudflare’s counsel (Charhon, Callahan, Robson & Garza PLLC) and Sable’s counsel (Berger & Hipskind LLP and Lowenstein & Weatherwax, LLP) agreed to this outcome signals that both sides found more value in resolution than in pursuing a Federal Circuit ruling, which may reflect broader commercial considerations including licensing arrangements or product roadmap changes.

Legal Significance

1. Because the Federal Circuit did not issue a merits decision, US8243593B2 has not been judicially invalidated and its claims have not been construed by the appellate court, leaving the patent’s scope and validity open to future litigation by any third party in the networking technology space.
2. The voluntary dismissal under Fed. R. App. P. 42(b) with agreed cost allocation sets no precedent on the invalidity grounds raised against flow-management patents, meaning the legal arguments developed during briefing — if any — remain unpublished and non-binding, preserving those arguments for use in future proceedings.
3. For companies in the network QoS and traffic-policing space, this outcome underscores that a patent surviving an invalidity challenge at the appellate level through voluntary dismissal — rather than a merits ruling — cannot be treated as having been validated; it remains a live IP risk requiring ongoing monitoring and FTO diligence.

Strategic Takeaways

For Patent Attorneys:

• File IPR or ex parte reexamination petitions against US8243593B2 before asserting invalidity in future litigation, as the Federal Circuit’s failure to rule on the merits leaves prior art arguments and §§ 102/103 grounds untested and available for fresh challenge.
• When advising clients on Rule 42(b) stipulated dismissals at the Federal Circuit, expressly negotiate the scope of any dismissal’s preclusive effect and ensure that settlement or licensing terms, if any, are documented to avoid future claim-preclusion or collateral estoppel arguments.
• Monitor Sable Networks’ continued enforcement activity regarding US8243593B2, as a patent owner who has weathered an invalidity challenge at the appellate level — even without a merits ruling — may become more aggressive in licensing negotiations, armed with the perception of patent durability.

For IP Professionals:

• In-house IP teams at companies deploying network traffic management, QoS, or flow-policing technologies should add US8243593B2 to their active patent watch list and conduct a fresh claim mapping exercise given the patent’s unresolved validity status following this dismissal.
• Consider whether a proactive licensing outreach to Sable Networks, or an inter partes review filing, would be more cost-effective than waiting for assertion, particularly if your organization’s products intersect with the misbehaving-flow identification claims of US8243593B2.

For R&D Teams:

• R&D teams building or enhancing network flow management features — including DDoS mitigation, bandwidth policing, or QoS enforcement modules — should conduct a targeted FTO analysis against US8243593B2’s claims before product launch, as the patent remains valid and enforceable.
• Explore design-around opportunities by architecting flow-penalty mechanisms that operate on different detection parameters or enforcement layers than those claimed in US8243593B2, and document the technical rationale to support a non-infringement position if challenged.