Book a demo

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

Try now
IDrive v. Microsoft: Cloud Storage Patent Dismissal | PatSnap
Patent Litigation

IDrive v. Microsoft: Three Cloud Storage Patents, Dismissed With Prejudice in 118 Days

IDrive, Inc. asserted three patents covering cloud storage and data synchronisation against Microsoft's OneDrive service and multiple browsers before the California Central District Court. All claims were dismissed with prejudice via stipulation after just 118 days, with each party bearing its own fees and costs.

Resolution time
118days
118 days from filing to dismissal — resolved well under the median district court patent case lifecycle
Patents asserted
3
US8620957B1, US8224920B1, and US8099520B2 — three cloud storage and data-sync patents asserted
Outcome
Dismissed with Prejudice
All claims stipulated dismissed with prejudice; no counterclaims filed; each party bears own costs
Cost ruling
Own Costs
Each party bears its own attorneys' fees, costs, and expenses — no fee-shifting recorded
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Cloud Storage Patent Dispute: Swift Stipulated Exit Before Answer

On 13 February 2026, IDrive, Inc. filed an infringement action against Microsoft Corporation in the United States District Court for the Central District of California. IDrive asserted three patents — US8620957B1, US8224920B1, and US8099520B2 — covering cloud storage and data-synchronisation technology against Microsoft OneDrive as well as Chrome, Edge, Firefox, Safari, and mobile applications for Android and iOS tablets and phones.

The case closed on 11 June 2026. The recorded basis of termination is dismissed with prejudice. The docket order reflects a Fed. R. Civ. P. 41(a)(1)(A)(ii) stipulated dismissal of all claims with prejudice, noting that Microsoft had not yet filed an answer or counterclaims. Each party was to bear its own attorneys' fees, costs, and expenses.

Resolution in 118 days — before Microsoft had even responded to the complaint — is notably swift for a multi-patent infringement action in a busy California district. The early exit, before answer or counterclaim, leaves the substantive merits of the three asserted patents unadjudicated. The specific terms that may have informed the parties' agreement to dismiss are not disclosed in the available record.

See Complete Case & Patent Analysis →
Case at a glance
PlaintiffIDrive, Inc.
CourtCalifornia Central District Court
JudgeN/A
FiledFebruary 13, 2026
ClosedJune 11, 2026
Duration118 days
OutcomeDismissed with Prejudice
Verdict causeInfringement Action
BasisDismissed with Prejudice
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 / California Central District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Dismissed with Prejudice in 118 days

118 days from filing to dismissal — resolved well under the median district court patent case lifecycle

Case timeline: Complaint filed FEB 13 2026 — 118 days total Horizontal timeline showing the three key events in IDrive, Inc. v Microsoft, Co. from filing to resolution. Source: PACER, California Central District Court. FEB 13 2026 Complaint filed Pre-trial proceedings JUN 11 2026 Dismissed with Prejudice 118 DAYS TOTAL
Patent at issue

US8620957B1, US8224920B1 & US8099520B2 — Cloud Storage & Data Sync Patents

Publication No.US8620957B1
Application No.US13/947097
Patent details
Productcloud-based data storage and remote backup methods
Cited in actionFebruary 13, 2026

Publication No.US8224920B1
Application No.US13/420290
Patent details
Productcloud data synchronisation and file transfer methods
Cited in actionFebruary 13, 2026

Publication No.US8099520B2
Application No.US11/620936
Patent details
Productnetwork-based data storage and client-server sync systems
Cited in actionFebruary 13, 2026
Technical brief · sourced from PatSnap patent database
Patent figurePatent figure
Representative claim (1 of 3 independent)
1. A method comprising: providing a web-based data store, wherein the web-based data store comprises at least one database of commonly stored data, each database containing different categories of files; providing a shell interface for transmitting data between a client computing device and the web-based data store; configuring the shell interface to resemble a folder/file interface such that the shell interface is displayed as a local folder/file system of the operating system on the client computing device; allowing a connection to be established between the web-based data store and the shell interface; sending…
Technical background
CROSS REFERENCE TO RELATED APPLICATIONS This application is a continuation application of U.S. patent application Ser. No. 13/315,265, entitled “Displaying Advertising Content in a Shell Interface,” filed on Dec. 8, 2011, which is incorporated herein by reference. U.S. patent application Ser. No. 13/315,265 is a continuation application of U.S. patent application Ser. No. 11/620,936 now U.S. Pat. No. 8,099,520, entitled “System and Method for Storing and Accessing Data,” filed on Jan. 8, 2007, which is incorporated…
Patent family
6 family members across 1 jurisdiction (US)
PatSnap Eureka · FTO Search Agent
Should your team run an FTO against US8620957B1, US8224920B1 & US8099520B2?

Any company shipping cloud storage, backup, or browser-based data-sync products — including mobile cloud clients for Android or iOS — should treat these three IDrive patents as live risk. The dismissal with prejudice in this case carries no invalidity finding and provides no freedom-to-operate protection for any party other than Microsoft. Product teams building OneDrive-competitive features or browser-integrated sync layers are particularly exposed.

Run FTO in Eureka
Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Official verdict

Official order — verbatim text

Pursuant to Fed. R. Civ. P. 41(a)(1)(A)(ii), Plaintiff IDrive, Inc. hereby stipulates to the dismissal of all claims in this action with prejudice, and Defendant Microsoft Corporation has no counterclaims to dismiss because it has not yet responded to Plaintiff’s complaint. Each party shall bear its own attorneys’ fees, costs, and expenses.
Source: PACER Docket, Case 2:26-cv-01556, California Central District Court

The stipulation records that IDrive dismissed all claims with prejudice under Rule 41(a)(1)(A)(ii) and that Microsoft had filed no counterclaims, having not yet responded to the complaint. The with-prejudice designation is the operative legal consequence: IDrive's claims against Microsoft on the three asserted patents are extinguished, though the patents themselves remain alive. No merits findings — on infringement, validity, or claim construction — are recorded.

PACER case 2:26-cv-01556 · Public docket record Explore in Eureka ↗
Dismissal terms

Dismissed with prejudice: what the stipulated exit means for both parties

Legal mechanism

Rule 41(a)(1)(A)(ii): stipulated dismissal with prejudice

A Fed. R. Civ. P. 41(a)(1)(A)(ii) dismissal requires the written consent of all parties who have appeared. Because Microsoft had not yet answered, both sides nonetheless stipulated to dismissal. The 'with prejudice' designation means IDrive cannot re-file the same claims against Microsoft on these three patents in federal court.

Bars re-filing on same claims
Patent holder outcome

IDrive loses the right to re-assert these three patents against Microsoft

Dismissal with prejudice extinguishes IDrive's ability to bring the same infringement claims against Microsoft on US8620957B1, US8224920B1, and US8099520B2. The patents themselves remain in force, so IDrive retains the right to assert them against other defendants. Whether any consideration passed between the parties is not disclosed in the available record.

Patents survive; claims against Microsoft barred
Defendant outcome

Microsoft exits without a merits ruling and bears its own costs

Microsoft secured a dismissal with prejudice — the strongest form of litigation exit short of a verdict — without filing an answer or incurring the cost of full patent discovery. No counterclaims for invalidity were filed or dismissed, so there is no declaratory judgment of invalidity on record. Microsoft bears its own legal costs under the stipulation.

Clean exit; no invalidity record
Commercial implications

No invalidity ruling leaves cloud-sync patent risk open for others

Because the case ended without any merits adjudication, the validity and enforceability of the three IDrive patents remain untested. Other cloud storage and browser-sync competitors — whose products may overlap with the same patent claims — receive no estoppel or invalidity shield from this case. The landscape for these patents remains live for third-party enforcement.

Patents untested; sector exposure remains
Legal analysis based on PACER docket records for case 2:26-cv-01556 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffIDrive, Inc.Company/Search in Eureka ↗
DefendantMicrosoft, Co.Company/Search in Eureka ↗
Plaintiff counselAaron Lewis RenfroAttorneyCounsel for IDrive, Inc.Search in Eureka ↗
Plaintiff counselArjun Padmanabhan NairAttorneyCounsel for IDrive, Inc.Search in Eureka ↗
Plaintiff counselJeffrey M SaltmanAttorneyCounsel for IDrive, Inc.Search in Eureka ↗
Plaintiff counselLaura Lisa SandovalAttorneyCounsel for IDrive, Inc.Search in Eureka ↗
Plaintiff counselRajkumar VinnakotaAttorneyCounsel for IDrive, Inc.Search in Eureka ↗
Plaintiff counselVishal H. PatelAttorneyCounsel for IDrive, Inc.Search in Eureka ↗
Plaintiff counselWilliam E ZapfAttorneyCounsel for IDrive, Inc.Search in Eureka ↗
Plaintiff law firmCall & Jensen APCLaw FirmRepresenting IDrive, Inc.Search in Eureka ↗
Plaintiff law firmCole Scholtz PCLaw FirmRepresenting IDrive, Inc.Search in Eureka ↗
Defendant counselAndrew V. DevkarAttorneyCounsel for Microsoft, Co.Search in Eureka ↗
Defendant law firmMorgan, Lewis & Bockius, LLPLaw FirmRepresenting Microsoft, Co.Search in Eureka ↗
Presiding judgeJudge N/AJudgeCalifornia Central District CourtSearch in Eureka ↗
R&D signals

R&D signals in the cloud storage and data-sync patent space

Forward-looking patent and innovation intelligence derived from IDrive's assertion of three cloud-sync patents against Microsoft OneDrive and major browser platforms.

Patent portfolio

IDrive's cloud storage patent portfolio: breadth and filing activity

IDrive holds at least three granted US patents covering cloud backup and sync methods, with application dates ranging from the mid-2000s to the early 2010s. Mapping IDrive's full portfolio — including continuations, divisionals, and forward citations — can reveal whether further enforcement campaigns against cloud competitors are in preparation or likely.

Portfolio monitoring signal
Technology landscape

Filing trends in browser-integrated cloud sync technology

The assertion of these patents against Chrome, Edge, Firefox, Safari, and mobile apps signals growing IP activity around browser-based and client-side cloud data synchronisation. Tracking recent patent filings in this space — by both incumbents and challengers — can identify where claim density is building and where design-around space remains available.

Browser cloud sync IP trend
Competitor IP posture

Microsoft's defensive patent position in cloud storage and backup

Microsoft's exit before answering means no invalidity contentions were placed on the public record. Analysing Microsoft's own patent portfolio in cloud storage, OneDrive sync architecture, and browser-based data access can reveal defensive assets that may be relevant to future disputes — and signal where Microsoft is innovating in this domain.

Microsoft cloud IP posture
White space

Design-around and white-space opportunities near the asserted patents

Because no claim construction ruling was issued, the boundaries of US8620957B1, US8224920B1, and US8099520B2 remain judicially undefined. R&D teams can use prior art searches and claim mapping to identify design-around architectures for cloud backup and sync — particularly for mobile-first or edge-cached implementations not contemplated in patents filed before 2013.

Cloud sync design-around space
Related litigation

Similar cloud storage patent infringement cases in C.D. Cal.

Browse related patent infringement actions asserting cloud storage and data-synchronisation patents before the California Central District Court.

🔍
Access 40+ similar cases in PatSnap Eureka
IDrive, Inc. patent enforcement history, California Central District Court case history, IDrive, Inc.'s full IP portfolio, and comparable case analysis
Cloud sync patent casesIDrive enforcement historyOneDrive patent disputesC.D. Cal. tech dismissals
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the cloud storage IP landscape

A pre-answer dismissal with prejudice involving three asserted cloud-sync patents leaves the market with unresolved questions about enforceability.

IDrive's three patents remain enforceable against other cloud competitors

The dismissal with prejudice only bars IDrive from re-suing Microsoft on these patents. The patents are not invalidated. Any competing cloud storage or browser-sync provider whose products touch the same claims should treat these patents as live enforcement risk and consider FTO analysis before assuming this outcome provides cover.

Pre-answer resolution limits discovery exposure for both sides

Microsoft's exit before answering meant no invalidity contentions, no claim construction briefing, and no source-code discovery on OneDrive's sync architecture. This limits the public record for parties seeking insight into how the patented methods compare to Microsoft's implementation — a gap that competitors and counsel should note.

🔒
Full strategic analysis in PatSnap Eureka
Unlock enforcement pattern analysis and claim-scope intelligence for cloud storage patent disputes in the C.D. Cal. district court.
Claim scope analysisIDrive portfolio trendsC.D. Cal. cloud cases
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

IDrive v Microsoft — key questions answered

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

Monitor cloud storage patent risk before it reaches litigation

Use PatSnap Eureka to run FTO analysis on US8620957B1, US8224920B1, and US8099520B2 and track IDrive's enforcement activity across cloud and browser-sync product categories.

Disclaimer

This page is compiled from public court dockets and third-party patent and litigation data via PatSnap Eureka, and is provided for general informational purposes only. The information shown — including party names, patent and application numbers, dates, case status, outcomes, and any analysis — may be incomplete, may not reflect the most recent filings or legal status, and may contain errors or omissions. Verify all details against official court records (for example, PACER) and the relevant patent office before relying on them.

Nothing on this page constitutes legal advice or a legal opinion on the validity, infringement, enforceability, or scope of any patent or case, and no attorney‑client relationship is created by its use. Any description of an outcome (such as a dismissal, settlement, or consent judgment) is a general summary, not a legal determination. All patents, trademarks, and company or law‑firm names are the property of their respective owners. PatSnap makes no warranty as to the accuracy or completeness of this content and disclaims, to the fullest extent permitted by law, all liability for reliance on it. For advice on a specific matter, consult qualified legal counsel.

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.