Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
Morris Routing Technologies v. Microsoft — Network Routing Patents | PatSnap
Explore in Eureka
Case ID1:25-cv-01254
FiledAug 2025
ClosedDec 2025
Patent Litigation

Morris Routing Technologies v. Microsoft: 7-Patent Routing Suit Dismissed With Prejudice

Morris Routing Technologies, LLC filed suit against Microsoft Corporation in the Western District of Texas asserting seven US patents covering Segment Routing technology aligned with IETF RFC standards. The case closed after just 124 days via voluntary dismissal with prejudice, with each party bearing its own costs.

Resolution time
124days
124 days — well under average district court resolution timeline of 2–3 years
Patents asserted
7
US10652134B1 and 6 further patents asserted covering Segment Routing (SR) network forwarding
Outcome
Voluntary dismissal
Voluntary dismissal with prejudice under Rule 41(a)(1)(A)(i); claim cannot be re-filed
Cost ruling
Own Costs
Each party bears its own costs, expenses, and attorneys’ fees — no fee-shifting awarded
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Seven Segment Routing Patents, One Early Exit: Microsoft Escapes Liability

On August 7, 2025, Morris Routing Technologies, LLC filed an infringement action against Microsoft Corporation in the Western District of Texas before Judge Alan D. Albright, asserting seven US patents — US10652134B1, US10757010B1, US10805204B1, US11784914B1, US10574562B1, US10652133B1, and US11757756B1 — all directed at Segment Routing (SR) technologies. The accused products were Microsoft’s implementations aligned with IETF RFC standards 8402, 8660, 8663, 8754, 8986, 9256, and 9352.

The case concluded on December 9, 2025, when Morris Routing Technologies filed a Notice of Voluntary Dismissal With Prejudice pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(i). The dismissal is with prejudice, meaning Morris Routing Technologies is permanently barred from re-asserting these seven patents against Microsoft on the same claims. The order further specified that each party shall bear its own costs, expenses, and attorneys’ fees, suggesting no settlement payment was publicly recorded, though the public record does not foreclose a confidential resolution.

A resolution within 124 days is notably fast for a seven-patent infringement suit in the Western District of Texas, which typically sees cases run 18–30 months to trial. The speed and with-prejudice nature of the dismissal — combined with the absence of any fee-shifting — is consistent with either a confidential licensing agreement reached quickly, or a strategic decision by the plaintiff to withdraw after early case assessment. What drove the dismissal remains undisclosed in the public record.

Case at a glance
Case no.1:25-cv-01254
CourtTexas Western
JudgeAlan D Albright
FiledAugust 7, 2025
ClosedDecember 9, 2025
Duration124 days
OutcomeVoluntary dismissal
Verdict causeInfringement Action
BasisVoluntary dismissal
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Texas Western District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Voluntary dismissal in 124 days

124 days — well under average district court resolution timeline of 2–3 years

Case timeline: Complaint filed AUG 7 2025, OCT–NOV — 124 days total Horizontal timeline showing the three key events in Morris Routing Technologies, LLC v Microsoft, Co. from filing to resolution. Source: PACER, Texas Western District Court. AUG 7 2025 Complaint filed Pre-trial proceedings DEC 9 2025 Voluntary dismissal 124 DAYS TOTAL
Dismissal terms

Dismissed with prejudice: what Rule 41 means for both parties

Legal mechanism

Rule 41(a)(1)(A)(i): plaintiff’s unilateral right to dismiss

Under FRCP 41(a)(1)(A)(i), a plaintiff may voluntarily dismiss an action without a court order if filed before the defendant serves an answer or motion for summary judgment. This is a unilateral right requiring no judicial approval. Here, the dismissal is expressly with prejudice — a stronger election than the default — meaning the plaintiff affirmatively surrendered all claims permanently against this defendant on these patents.

Rule 41(a)(1)(A)(i) — with prejudice
Finality of dismissal

With prejudice: no second bite at the apple against Microsoft

A dismissal with prejudice operates as a final adjudication on the merits under res judicata principles. Morris Routing Technologies cannot re-file these same patent claims against Microsoft in any US court. This is a materially different outcome from a without-prejudice dismissal, which would preserve the right to refile. The public record is silent on whether a confidential agreement accompanied this election, but the finality is absolute regardless.

Permanent bar — res judicata applies
Plaintiff outcome

Morris Routing: closed exposure to cost sanctions, but permanent bar created

By dismissing with prejudice before Microsoft even filed an answer, Morris Routing Technologies avoided prolonged litigation costs and the risk of an adverse claim construction or fee-shifting motion under 35 U.S.C. § 285. However, the with-prejudice election signals either a negotiated exit or a recognition that the claims against Microsoft specifically could not withstand scrutiny. The seven patents remain enforceable against other defendants.

Patents survive — against other targets
Defendant outcome

Microsoft walks away clean — no injunction risk, no damages, own costs only

Microsoft faces no liability, injunction, or ongoing royalty obligation from this action. The with-prejudice dismissal eliminates any future re-filing of these specific claims. The own-costs order means Microsoft absorbed its own defense spend without recovery, which is consistent with a pre-answer settlement or a plaintiff withdrawal before significant defense expenditure was incurred. Microsoft’s SR/RFC-based product stack faces no judicially imposed encumbrance from this case.

Microsoft — no liability, no injunction
Legal analysis based on PACER docket records for case 1:25-cv-01254 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffMorris Routing Technologies, LLCCompanyPatent assertion entity — holder of 7 US Segment Routing network technology patentsSearch in Eureka ↗
DefendantMicrosoft, Co.CompanyMicrosoft Corporation — global cloud and enterprise software provider accused of SR RFC implementationsSearch in Eureka ↗
Plaintiff counselDerek F. DahlgrenAttorneyCounsel for Morris Routing Technologies, LLCSearch in Eureka ↗
Plaintiff counselTimothy DevlinAttorneyCounsel for Morris Routing Technologies, LLCSearch in Eureka ↗
Plaintiff law firmDevlin Law Firm LLCLaw FirmRepresenting Morris Routing Technologies, LLCSearch in Eureka ↗
Presiding judgeJudge Alan D AlbrightJudgeTexas Western District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Plaintiff Morris Routing technologies, LLC (“Plaintiff”) filed a Notice of Voluntary Dismissal With Prejudice of Defendant Microsoft Corporation (“Defendant”), pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(i). Accordingly, his action is dismissed with prejudice pursuant to Rule 41(a)(1)(A)(i). Each party shall bear its own costs, expenses, and attorneys’ fees. The Clerk of Court is requested to CLOSE the case.”
Source: PACER Docket, Case 1:25-cv-01254, Texas Western District Court

The dismissal order records an unambiguous with-prejudice election by the plaintiff under Rule 41(a)(1)(A)(i), filed before any responsive pleading by Microsoft. The own-costs rider — expressly allocating costs, expenses, and attorneys’ fees to each party — is consistent with a negotiated exit or early bilateral agreement, though the public record does not confirm a financial settlement. The finality of the with-prejudice designation means no further judicial analysis of the seven patents’ validity or infringement scope against Microsoft will occur in this action.

PACER case 1:25-cv-01254 · Public docket record Explore in Eureka ↗
Patent at issue

US10652134B1 and 6 further patents — Segment Routing network forwarding technology

Publication No.US10652134B1
Application No.US16/454043
Patent details
ProductSegment Routing network path forwarding and traffic engineering
Cited in actionAugust 7, 2025

Publication No.US10757010B1
Application No.US16/803978
Patent details
ProductSegment Routing packet forwarding and path computation methods
Cited in actionAugust 7, 2025

Publication No.US10805204B1
Application No.US16/796937
Patent details
ProductSegment Routing traffic steering and forwarding plane operations
Cited in actionAugust 7, 2025

Publication No.US11784914B1
Application No.US17/235923
Patent details
ProductSegment Routing policy and path management in IP networks
Cited in actionAugust 7, 2025

Publication No.US10574562B1
Application No.US16/454030
Patent details
ProductSegment Routing source routing and segment list encoding methods
Cited in actionAugust 7, 2025

Publication No.US10652133B1
Application No.US16/454040
Patent details
ProductSegment Routing label distribution and forwarding table management
Cited in actionAugust 7, 2025

Publication No.US11757756B1
Application No.US17/525840
Patent details
ProductSegment Routing over IPv6 (SRv6) path programming methods
Cited in actionAugust 7, 2025

The seven asserted patents — US10652134B1, US10757010B1, US10805204B1, US11784914B1, US10574562B1, US10652133B1, and US11757756B1 — cover methods and systems relating to Segment Routing (SR), a modern network source-routing architecture. SR allows a network node to steer packets through a specified sequence of segments defined at ingress, reducing per-flow state in the network core. The patents span application numbers filed between 2019 and 2021, capturing innovations aligned with the IETF’s SR standardisation work under RFC 8402 (architecture), RFC 8660 and 8663 (MPLS dataplane), RFC 8754 and 8986 (SRv6), RFC 9256 and 9352 (SR Policy and SRv6 SID).

The strategic significance of this portfolio lies in its alignment with mandatory IETF RFC compliance. Segment Routing has been widely adopted in hyperscaler, carrier, and enterprise WAN environments. If claims within these patents read on RFC-compliant SR implementations, potential infringers include not only cloud platform vendors but also network equipment manufacturers and managed service providers. The with-prejudice dismissal against Microsoft does not affect enforceability against other implementors, and the portfolio’s breadth across both SR-MPLS and SRv6 dataplane variants suggests wide potential coverage of deployed infrastructure.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should you run an FTO against the Morris Routing Technologies SR patent portfolio?

Any organisation deploying Segment Routing in production environments — whether on cloud WAN, data centre fabrics, or carrier IP/MPLS networks — should consider freedom-to-operate analysis against these seven patents. The accused product category (SPRING SR aligned with RFC 8402, 8660, 8663, 8754, 8986, 9256, and 9352) encompasses widely deployed SR and SRv6 implementations. Network equipment vendors, cloud providers, and telcos building RFC-compliant SR stacks are directly within scope of the assertion theory presented in this case.

PatSnap Eureka’s FTO Search Agent enables R&D and IP teams to map product implementations against claim-level coverage across all seven asserted patents simultaneously. By ingesting RFC specification language alongside claim text, Eureka can identify where your SR implementation may overlap with protected claim scope — and surface prior art or design-around options. Given the portfolio remains active and unencumbered against non-Microsoft targets, proactive FTO analysis now is materially lower cost than reactive defence later.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US10652134B1 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar Segment Routing and network patent cases in W.D. Texas

Explore comparable network routing and SR patent infringement actions litigated in the Western District of Texas, including cases before Judge Albright involving RFC-standard aligned assertions.

🔍
Access 40+ similar cases in PatSnap Eureka
Morris Routing Technologies, LLC patent enforcement history, Texas Western case history, Morris Routing Technologies, LLC’s full IP portfolio, and comparable case analysis
SR patent cases W.D. TexasMorris Routing other defendantsRFC SEP infringement suitsJudge Albright early dismissals
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the Segment Routing IP landscape

A seven-patent suit resolved in 124 days with prejudice raises pointed questions about assertion strategy, claim strength, and licensing dynamics in SR networking.

Early dismissal with prejudice narrows the plaintiff’s assertion map

Morris Routing Technologies permanently closed off Microsoft as a defendant across all seven asserted patents. Any future licensing campaign for this portfolio must exclude Microsoft, which may reduce aggregate licensing value if Microsoft’s SR implementations are a primary market reference. Other potential defendants — cloud providers, router OEMs, network equipment vendors — remain fair targets, but the Microsoft precedent may affect negotiating leverage.

Seven RFC-aligned patents signal a standards-essential assertion strategy

Asserting patents against products implementing IETF RFC standards (8402, 8660, 8663, 8754, 8986, 9256, 9352) is a recognized strategy in networking IP. If any of the seven patents read on mandatory RFC compliance, the universe of potential infringers is broad. Companies implementing Segment Routing in cloud, WAN, or data centre environments should assess FTO exposure against this portfolio, particularly given the patents remain active and unencumbered by this case outcome.

🔒
Full strategic analysis in PatSnap Eureka
Unlock gated analysis on Segment Routing patent strategy, RFC standards exposure, and district court early dismissal signals in W.D. Texas.
Claim construction riskRFC SEP exposure mapRemaining defendant targets
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Morris v Microsoft — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Protect your SR network stack: run FTO before the next filing

The Morris Routing Technologies portfolio remains active against all non-Microsoft targets. PatSnap Eureka maps your SR and SRv6 implementations against claim-level patent coverage so your IP and R&D teams can act before litigation reaches your door.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.