After more than four years of litigation in the Western District of Washington, the patent infringement action brought by individual inventor Royal J. O’Brien against Microsoft Corporation concluded on January 5, 2024, with a stipulated dismissal with prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(ii). The case, centered on U.S. Patent No. 8,380,808, alleged that Microsoft’s Windows 10 and Windows Server 2016 operating systems — specifically driver-related components — infringed O’Brien’s protected technology. The dismissal, agreed to by both parties, required each side to bear its own costs and fees, signaling a negotiated resolution rather than a merits-based adjudication.

This case is significant for IP strategists and patent practitioners navigating the increasingly contested landscape of software and operating system patents. An individual inventor sustaining litigation against one of the world’s largest technology companies for over 1,500 days underscores both the challenges and leverage points inherent in patent assertion. For in-house IP counsel at technology firms, R&D leaders developing OS-level software components, and patent prosecutors managing software claim portfolios, the trajectory and resolution of O’Brien v. Microsoft offers instructive lessons in litigation economics, claim scope, and defensive strategy.

Case Overview

The Parties

The Patent at Issue

U.S. Patent No. 8,380,808 (Application No. 12/276,998) covers technology relating to how software components — specifically device drivers — communicate within or interact with an operating system environment. The patent’s claims likely address methods or systems for managing data transmission or messaging between OS-level drivers and other system components. In practical terms, this technology underpins how Windows operating systems handle hardware device communication and system-level software interfaces, making it directly relevant to the accused Windows 10 and Windows Server 2016 products.

• • US8380808B2

Legal Representation

Plaintiff Counsel: Williams Kastner And Gibbs (SEA) (lead: Daniel Andrew Brown)
Defendant Counsel: Calfo Eakes LLP; MORGAN LEWIS & BOCKIUS LLP (WA); Norton Rose Fulbright (IL); SIDLEY Austin LLP (IL); Sidley Austin (SF); Sidley Austin, LLP (lead: Emily Dodds Powell)

Litigation Timeline & Procedural History

O’Brien v. Microsoft was filed on October 10, 2019, in the U.S. District Court for the Western District of Washington — a venue of strategic importance given its proximity to Microsoft’s Redmond headquarters and its established docket of technology-related IP disputes. The case was presided over by Chief Judge Richard A. Jones and proceeded as a first-instance district court matter, meaning no appellate record was created from this proceeding. The Western District of Washington, while not as historically prominent as the Eastern District of Texas in patent litigation, has become an increasingly relevant forum for technology patent cases involving Pacific Northwest-based defendants.

The litigation spanned 1,548 days — approximately four years and three months — before concluding via a stipulated dismissal filed January 4, 2024, and closed January 5, 2024. This extended duration is characteristic of complex software patent disputes, which often involve prolonged claim construction battles, extensive discovery, and multiple rounds of dispositive motions. The resolution via Rule 41(a)(1)(A)(ii) stipulation — with each party bearing its own costs — strongly suggests the parties reached a private settlement or licensing arrangement, or that O’Brien determined continued litigation was no longer economically viable. No damages were publicly awarded and no trial on the merits took place.

The Verdict & Legal Analysis

Outcome

The case was terminated by a stipulated dismissal with prejudice, jointly agreed upon by counsel for both Royal J. O’Brien and Microsoft Corporation on January 4, 2024. Under the stipulation, all claims brought by O’Brien against Microsoft were dismissed with prejudice, and each party agreed to bear its own attorneys’ fees and costs. No damages were adjudicated, no injunctive relief was ordered, and no court finding of infringement or non-infringement was made on the merits of U.S. Patent No. 8,380,808.

Verdict Cause Analysis

The dismissal with prejudice — while procedurally simple — carries substantive implications rooted in how patent infringement actions like this typically resolve after extended litigation:

• A stipulated dismissal with prejudice under Rule 41(a)(1)(A)(ii) requires agreement from all parties who have appeared, suggesting Microsoft actively negotiated the terms rather than simply acquiescing to plaintiff withdrawal.
• The mutual cost-bearing provision is a hallmark of confidential settlement arrangements, indicating the parties likely resolved the underlying dispute through a private agreement, potentially including a licensing component.
• No finding of invalidity or non-infringement was issued by the court, meaning U.S. Patent No. 8,380,808 retains its presumption of validity and could theoretically be asserted against other defendants in future litigation.
• The dismissal with prejudice bars O’Brien from re-filing the same infringement claims against Microsoft, providing Microsoft with finality and protection from re-litigation on the same accused Windows products.

Legal Significance

1. 1. Because the case resolved via stipulated dismissal rather than a merits ruling, no claim construction order or invalidity finding was issued, preserving the patent’s full legal force and leaving open interpretive questions about the scope of U.S. Patent No. 8,380,808 that could affect future defendants.
2. 2. The four-year duration without a dispositive ruling suggests the patent survived early validity challenges — such as a motion to dismiss under Alice/Mayo or an inter partes review petition — which may indicate the claims are directed to patent-eligible subject matter with sufficient specificity to withstand § 101 scrutiny.
3. 3. The resolution of this individual-inventor-versus-tech-giant dispute without a merits outcome reflects the broader trend of software patent cases settling before trial, reinforcing that litigation economics — not legal merit alone — often determine outcomes in small-plaintiff, large-defendant patent disputes.

Strategic Takeaways

For Patent Attorneys:

• When representing individual inventors against large technology defendants, develop a litigation budget and milestone-based settlement strategy from filing, as extended cases exceeding 1,500 days create significant financial pressure on smaller plaintiffs regardless of claim strength.
• The survival of this case for over four years without a reported Alice/§ 101 dismissal suggests that OS-driver-related software claims, when properly drafted with functional specificity, can withstand early dispositive challenges — a prosecution and litigation drafting lesson for software patent counsel.
• Counsel should consider filing inter partes review petitions early in parallel litigation when representing technology company defendants, as the absence of a reported IPR here may have contributed to the prolonged district court timeline.
• The mutual cost-bearing stipulation in the final order should be negotiated carefully — securing this provision protects technology defendants from exceptional case fee awards under Octane Fitness while giving plaintiff counsel a clean exit without financial exposure.

For IP Professionals:

• In-house IP teams at major software companies should maintain active watch on individually-held OS and driver-layer patents, as solo inventors with focused portfolios can sustain multi-year litigation campaigns and extract settlement value even against well-resourced defendants.
• The dismissal without prejudice to the patent’s validity means U.S. Patent No. 8,380,808 remains a live asset — IP portfolio managers at companies with Windows-adjacent products should monitor this patent for potential re-assertion or assignment to a more aggressive licensing entity.

For R&D Teams:

• Engineering teams developing Windows-compatible drivers, middleware, or OS-level communication components should conduct freedom-to-operate analysis against U.S. Patent No. 8,380,808, as the patent’s claims were never invalidated and remain enforceable against parties other than Microsoft.
• R&D leaders building operating system components should document design-around alternatives and prior art references during development, as driver communication architectures are an active area of patent assertion that can implicate product launches and OEM relationships.