Book a demo

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

Try now
HP v. Inspur Group: Server & Data Center Patent Infringement Settlement | PatSnap
Explore in Eureka
Case ID4:24-cv-02220
FiledApr 2024
ClosedApr 2025
Patent Litigation

HP v. Inspur Group: 5-Patent Server Infrastructure Dispute Settles in N.D. California

Hewlett-Packard filed suit against Chinese server maker Inspur Group in April 2024, asserting five US patents covering server architecture, memory management, and data center infrastructure against 15 Inspur rack server models and ISPIM management software. The case resolved via stipulated settlement and was dismissed with prejudice after 351 days before Judge Jon S. Tigar.

Resolution time
351days
351 days — resolved within one year, faster than the N.D. California patent median
Patents asserted
5
US7634671B2 and 4 further patents asserted across server and data center infrastructure
Outcome
Case Stayed
Dismissed with prejudice following stipulated notice of settlement filed by both parties
Cost ruling
N/A
No public costs or fee-shifting order recorded; terms remain confidential
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

HP enforces server IP portfolio against Inspur’s US rack server line

Hewlett-Packard, Co. filed this patent infringement action on April 15, 2024 in the Northern District of California against Inspur Group Co., Ltd., a major Chinese server and data center hardware manufacturer. The complaint asserted five US patents — US7634671B2, US8218566B2, US8108508B1, US8335891B2, and US9229737B2 — covering server architecture, memory subsystem management, and infrastructure control technology. The accused products included at least 15 Inspur rack server SKUs across the KR and NF series, as well as Inspur’s Physical Infrastructure Manager (ISPIM) software platform.

The case concluded on April 1, 2025 when the parties filed a stipulated motion to stay all pending deadlines and notice of settlement. Judge Jon S. Tigar granted the motion and dismissed the matter with prejudice, meaning HP cannot re-file the same claims against Inspur on these patents. The court’s order included a 60-day unwind clause: if either party filed a notice that settlement had not in fact occurred after meeting and conferring, the dismissal order would be vacated — a standard protective mechanism in conditional settlement orders.

At 351 days, the case resolved faster than many multi-patent district court disputes, suggesting the parties reached commercial terms relatively efficiently once litigation pressure was established. The financial terms, licensing structure, and any ongoing royalty obligations remain confidential and are not reflected in the public docket. It is unclear from the record whether HP secured a cross-license, a lump-sum payment, or a market-exit commitment from Inspur regarding the US server market.

Case at a glance
Case no.4:24-cv-02220
CourtCalifornia Northern
JudgeJon S. Tigar
FiledApril 15, 2024
ClosedApril 1, 2025
Duration351 days
OutcomeCase Stayed
Verdict causeInfringement Action
BasisCase Stayed
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 Northern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Case Stayed in 351 days

351 days — resolved within one year, faster than the N.D. California patent median

Case timeline: Complaint filed APR 15 2024, OCT–NOV — 351 days total Horizontal timeline showing the three key events in Hewlett-Parkard, Co. v Inspur Group Co., Ltd. from filing to resolution. Source: PACER, California Northern District Court. APR 15 2024 Complaint filed Pre-trial proceedings APR 1 2025 Case Stayed 351 DAYS TOTAL
Settlement terms

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

Legal mechanism

Dismissal with prejudice bars HP from re-asserting these claims

A dismissal with prejudice is a final adjudication on the merits for res judicata purposes. HP cannot refile infringement claims against Inspur based on the same five patents and accused products. The stipulated nature of the dismissal confirms both parties agreed to end the litigation, distinguishing this from a unilateral withdrawal. The 60-day unwind clause suggests the settlement agreement itself was still being executed at the time of the court order.

Dismissed with prejudice
Patent holder outcome

HP converts litigation pressure into undisclosed settlement terms

By securing a with-prejudice dismissal, HP closed the case on terms it accepted. The five asserted patents remain valid and enforceable against third parties — the settlement does not impair HP’s ability to assert these patents in future actions against different defendants. What HP received from Inspur (monetary compensation, licensing, or behavioral commitments) is not in the public record, but the swift resolution is consistent with HP achieving commercially acceptable terms.

Patents remain enforceable
Defendant outcome

Inspur avoids a public merits ruling but faces ongoing HP portfolio risk

Inspur avoided a jury verdict or claim construction ruling that could have set adverse precedent. The with-prejudice dismissal resolves this specific dispute, but Inspur remains exposed to HP’s broader IP portfolio if it continues selling accused server lines or software in the US. The absence of any invalidity counterclaim resolution means Inspur did not secure a formal finding that HP’s patents are invalid — a meaningful limitation on its freedom to operate going forward.

No invalidity ruling secured
Commercial implications

Server IP enforcement against Chinese OEMs is an escalating dynamic

This case is consistent with a broader pattern of US server and data center incumbents using patent portfolios to manage competitive pressure from Chinese hardware manufacturers entering US enterprise markets. The 15 accused Inspur SKUs represent a substantial portion of its US rack server catalog. Competitors and distributors in the x86 server market should note that HP’s five asserted patents survived without any invalidity challenge reaching resolution, suggesting continued enforcement risk across the sector.

Enforcement risk persists
Legal analysis based on PACER docket records for case 4:24-cv-02220 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffHewlett-Parkard, Co.CompanyGlobal enterprise technology company — holder of US7634671B2 and 4 further server infrastructure patentsSearch in Eureka ↗
DefendantInspur Group Co., Ltd.CompanyInspur Group Co., Ltd. — Chinese multinational server and data center hardware manufacturerSearch in Eureka ↗
Plaintiff counselAima MoriAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselAmy LydonAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselAngela WhitesellAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselBrent K. YamashitaAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselClaire E. SchusterAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselErin P GibsonAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselHelena Drake KiepuraAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselMichael L. Burns , IVAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselMichael SaulnierAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselSean C. CunninghamAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff counselStephanie Mary PiperAttorneyCounsel for Hewlett-Parkard, Co.Search in Eureka ↗
Plaintiff law firmDLA Piper US LLPLaw FirmRepresenting Hewlett-Parkard, Co.Search in Eureka ↗
Defendant counselAndrew SamuelsAttorneyCounsel for Inspur Group Co., Ltd.Search in Eureka ↗
Defendant counselKevin W. KirschAttorneyCounsel for Inspur Group Co., Ltd.Search in Eureka ↗
Defendant counselVictoria Leigh WeatherfordAttorneyCounsel for Inspur Group Co., Ltd.Search in Eureka ↗
Defendant counselYuanyuan QinAttorneyCounsel for Inspur Group Co., Ltd.Search in Eureka ↗
Defendant law firmBaker & Hostetler, LLPLaw FirmRepresenting Inspur Group Co., Ltd.Search in Eureka ↗
Presiding judgeJudge Jon S. TigarJudgeCalifornia Northern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“The parties have filed a stipulated motion to stay all pending deadlines and notice of settlement. ECF No. 113. The motion is granted. Accordingly, any scheduled hearings or deadlines are vacated, and this matter is dismissed with prejudice. The Clerk shall close the file. This order will be vacated if any party, after meeting and conferring with opposing parties, files a notice that settlement has not occurred within 60 days of the date of this order. IT IS SO ORDERED.”
Source: PACER Docket, Case 4:24-cv-02220, California Northern District Court

The court’s order reflects a conditional dismissal mechanism: the with-prejudice termination is granted on the strength of the parties’ joint settlement notice, but remains subject to a 60-day cure window. The phrasing ‘dismissed with prejudice’ carries full res judicata effect once the unwind period expires without challenge. Notably, the order does not contain any merits findings — no claim construction, no liability determination, and no damages assessment entered the record. This is a procedurally clean exit for both parties, preserving HP’s patent validity and leaving Inspur without any defensive invalidity holding.

PACER case 4:24-cv-02220 · Public docket record Explore in Eureka ↗
Patent at issue

US7634671B2 and 4 further patents — server architecture and infrastructure management

Publication No.US7634671B2
Application No.US11/492963
Patent details
ProductServer fault tolerance and availability architecture
Cited in actionApril 15, 2024

Publication No.US8218566B2
Application No.US11/245667
Patent details
ProductNetwork packet processing and switching in server environments
Cited in actionApril 15, 2024

Publication No.US8108508B1
Application No.US09/102207
Patent details
ProductServer memory and cache management systems
Cited in actionApril 15, 2024

Publication No.US8335891B2
Application No.US12/502485
Patent details
ProductServer configuration and boot management
Cited in actionApril 15, 2024

Publication No.US9229737B2
Application No.US12/694954
Patent details
ProductData center infrastructure and physical resource management software
Cited in actionApril 15, 2024

The five asserted patents — US7634671B2, US8218566B2, US8108508B1, US8335891B2, and US9229737B2 — span application dates from the late 1990s through the early 2010s, reflecting HP’s longstanding R&D in enterprise server architecture and data center management. The portfolio covers technical domains including server fault resilience, memory subsystem control, network processing within server environments, boot and configuration management, and physical infrastructure monitoring software — the latter directly implicated by Inspur’s ISPIM platform.

For competitors in the x86 rack server market, this portfolio represents a strategic enforcement asset that HP has now demonstrated willingness to deploy against Chinese OEMs selling into US enterprise channels. The breadth of accused products — 15 SKUs across multiple generations — suggests HP conducted a thorough mapping exercise before filing. Any server manufacturer whose products implement comparable fault tolerance, memory management, or infrastructure monitoring functions should treat these patent families as material FTO risks, particularly given that no claim narrowing occurred during this litigation.

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

Should you run an FTO against US7634671B2 and HP’s server infrastructure portfolio?

If your organisation designs, manufactures, imports, or resells rack servers, blade systems, or infrastructure management software in the US, HP’s five-patent portfolio asserted in this case warrants a formal FTO assessment. The accused Inspur products span entry-level to high-density configurations, suggesting the patents read broadly across server form factors — not merely premium or hyperscale deployments. Software-side risk from the ISPIM infringement theory also implicates vendors of BMC, DCIM, or physical infrastructure management platforms.

PatSnap Eureka’s FTO Search Agent allows R&D and IP teams to map product features against the claim landscapes of US7634671B2, US8218566B2, US8108508B1, US8335891B2, and US9229737B2 simultaneously. Eureka surfaces prosecution history, claim amendments, and related continuation families — critical context given that no court-ordered claim construction is available from this case to guide interpretation. Use Eureka to identify design-around opportunities and assess whether successor product generations fall within the asserted claim scope.

PatSnap Eureka FTO Search

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

Run FTO in Eureka →
Related litigation

Related server infrastructure patent disputes in N.D. California and beyond

Cases involving server architecture, data center management patents, and Chinese OEM defendants in US federal courts — especially N.D. California — follow a recurring enforcement pattern.

🔍
Access 40+ similar cases in PatSnap Eureka
Hewlett-Parkard, Co. patent enforcement history, California Northern case history, Hewlett-Parkard, Co.’s full IP portfolio, and comparable case analysis
HP v. competitor server casesInspur US litigation historyServer OEM patent settlementsDCIM software IP disputes
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the server and data center IP landscape

HP’s swift settlement with Inspur reinforces the leverage that incumbent US server OEMs hold over emerging Chinese competitors in the US enterprise market.

Multi-patent filing against broad product lines maximises settlement leverage

Asserting five patents across 15 SKUs and a software platform creates a large damages surface and raises the cost of defence. This approach — well-executed by DLA Piper for HP — signals to defendants that trial preparation costs will be substantial. Companies facing similar portfolios should conduct early FTO assessments before entering contested US markets.

With-prejudice settlement preserves HP’s patent enforceability against third parties

The dismissal terms leave HP’s five patents fully intact and enforceable against other server manufacturers. No claim construction order, no invalidity finding, and no narrowing of claim scope entered the record. For competitors in the rack server and ISPIM-equivalent software space, this outcome strengthens — not weakens — the threat posed by HP’s portfolio.

🔒
Full strategic analysis in PatSnap Eureka
Unlock sector-specific IP enforcement analysis for the US server and data center market at district court level.
Inspur US product roadmap riskHP patent family claim scopeChinese OEM enforcement trends
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Hewlett-Parkard v Inspur — key questions answered

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

Map your server infrastructure IP exposure before it becomes litigation

HP’s five-patent assertion against 15 Inspur SKUs demonstrates the breadth of enforcement risk in the US rack server market. Run an FTO against US7634671B2 and related HP patent families in PatSnap Eureka to identify design-around opportunities and monitor for new assertions.

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.