Swarm Technology LLC v. Hewlett Packard Enterprises Co

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Swarm Technology LLC (Arizona)
  • Defendant: Hewlett Packard Enterprise Company (Delaware)
  • Plaintiff's Counsel: Newman Jones, PLLC; The Lamberson Law Firm, PC
• Case Identification: 4:24-cv-04927, S.D. Tex., 08/14/2025
• Venue Allegations: Plaintiff alleges venue is proper in the Southern District of Texas because Defendant maintains its principal place of business in the district and has sold or offered for sale the accused products and services within the district.
• Core Dispute: Plaintiff alleges that Defendant's Aruba networking products and cloud management services infringe a patent related to a multiprocessor computing architecture that utilizes a "task pool" to decouple co-processors from a central controller.
• Technical Context: The technology concerns parallel processing architectures designed to improve efficiency and reduce CPU overhead, with specific applications alleged in the fields of cloud computing and the Internet of Things (IoT).
• Key Procedural History: The operative complaint is the Second Amended Complaint, filed on August 14, 2025, which supersedes an original complaint and a First Amended Complaint. Plaintiff alleges that Defendant had actual notice of the infringement allegations no later than January 30, 2025, the date the original complaint was served, forming a basis for the willfulness claim.

Case Timeline

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 12,159,161 - "System and Method For Swarm Collaborative Intelligence Using Dynamically Configurable Proactive Autonomous Agents"

• Patent Identification: U.S. Patent No. 12159161 ("System and Method For Swarm Collaborative Intelligence Using Dynamically Configurable Proactive Autonomous Agents"), issued December 3, 2024 (the "'161 Patent").

The Invention Explained

• Problem Addressed: The patent's background section describes inefficiencies in conventional multiprocessor systems where a central processing unit (CPU) directly manages and distributes computational tasks to co-processors Compl. ¶3 This direct-control approach consumes significant CPU bandwidth, causes co-processors to remain idle while awaiting new tasks, and creates a single point of failure if the CPU becomes overloaded or unavailable '161 Patent, col. 1:62-2:8 The complaint provides a diagram illustrating this conventional "controller/responder" architecture Compl. p. 3
• The Patented Solution: The invention proposes a new architecture that interposes an intermediary data structure, a "task pool," between the primary controller (CPU) and the co-processors (referred to as "cells") '161 Patent, abstract The controller populates the task pool with tasks, and the co-processors, acting as "autonomous agents," proactively retrieve tasks from the pool without waiting for direct commands from the controller '161 Patent, col. 2:16-24 This decouples the co-processors from the central controller, which is alleged to reduce CPU overhead, improve efficiency, and increase system resilience Compl. ¶¶7-8 The complaint includes a diagram illustrating this revised architecture, showing the task pool situated between the controller and the co-processors Compl. p. 4
• Technical Importance: This decentralized task management architecture is presented as a solution for efficiently controlling large networks of distributed devices, such as those found in modern cloud computing and Internet of Things (IoT) environments, without overburdening a central controller Compl. ¶44

Key Claims at a Glance

• The complaint provides a detailed infringement analysis for independent system claim 37 Compl. ¶¶65-95
• The essential elements of independent claim 37 are:
  • A system comprising a "task pool", a "primary controller", and a "first cell".
  • The "primary controller" is configured to populate the "task pool" with tasks.
  • The "first cell" includes a "first agent" and is programmed to "proactively search" the "task pool" for a task, retrieve the task, deliver it to the cell for processing, and send a notification to the "task pool" upon completion.
  • The "first cell" is configured to operate a device.
  • The system is capable of performing a "device function reconfiguration task", which comprises a reconfiguration of the device's function to perform a second, different task type.
• The complaint asserts numerous other claims, including independent method claims and dependent claims, and reserves the right to assert additional claims Compl. ¶145 Compl. Prayer A

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are Hewlett Packard Enterprise Company's (HPE) cloud computing and networking products and services, specifically including the Aruba product line, the Aruba GreenLake platform, and the Aruba Central management service Compl. ¶51 Compl. ¶99 Compl. ¶100

Functionality and Market Context

• The complaint alleges that HPE's Aruba architecture mirrors the patented system Compl. ¶13 It characterizes Aruba Central as a cloud-based management console that functions as the "primary controller", creating and populating configurations and tasks for network devices Compl., Ex. C, p. 80 The network devices themselves-such as Aruba Access Points (APs), Switches, and Gateways-are alleged to function as the "co-processors" or "cells" Compl., Ex. C, p. 81 The complaint alleges these devices proactively connect to Aruba Central to retrieve configuration tasks, thereby operating independently of direct, real-time commands from the central controller Compl. ¶¶6-7 The complaint includes a sequence diagram in an exhibit to illustrate the alleged communication flow where an "Aruba Device" sends a GET request to "Aruba Central" to retrieve its configuration Compl., Ex. C, p. 87

IV. Analysis of Infringement Allegations

The complaint provides a detailed narrative breakdown of its infringement theory for Claim 37 but does not include a corresponding chart in its exhibits. The following table summarizes the allegations for Claim 37 based on the complaint's narrative section Compl. ¶¶65-95

'161 Patent Infringement Allegations

• Identified Points of Contention:
  • Scope Questions: The infringement theory equates the "task pool"-described in the patent as an intermediary component-with the entire Aruba Central cloud platform. A potential point of contention may be whether a comprehensive, multi-function cloud service platform can be construed as the claimed "task pool" '161 Patent, Fig. 1 Compl. ¶70
  • Technical Questions: The complaint alleges that Aruba devices "proactively search" for tasks. A central technical question may be whether the devices' mechanism for obtaining updates (e.g., periodic polling or checking in with a server) meets the inventive concept of a "proactive search" initiated by an "autonomous agent," or whether it is a more conventional client-server update process Compl. ¶79 The distinction between proactive "pull" and centrally managed "push" or scheduled polling may be a focus.
  • Scope Questions: The analysis of Claim 37 hinges on whether a standard network configuration update constitutes a "device function reconfiguration task" that enables the performance of a "second task type". A dispute may arise over whether changing operational parameters (e.g., routing rules) is equivalent to the patent's concept of reconfiguring a device to perform a fundamentally different class of function (e.g., re-tasking a processor from data encryption to graphics processing) '161 Patent, col. 6:6-15 Compl. ¶89

V. Key Claim Terms for Construction

• The Term: "proactively search"

• Context and Importance: This term is central to the patent's asserted departure from prior art, where co-processors passively awaited instructions. The construction of this term will be critical in determining whether the accused Aruba devices, which communicate with a central server for configuration updates, perform the claimed action.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification describes co-processors that "proactively retrieve threads (tasks) from the task pool" and "pings the task pool until another task becomes available" '161 Patent, col. 2:16-23 This language may support an interpretation where any task-seeking action initiated by the co-processor, rather than by a direct command from the CPU, is "proactive."
  • Evidence for a Narrower Interpretation: The patent uses terms like "autonomous co-processing cells each having an agent configured to proactively interrogate the task pool" '161 Patent, Abstract This may support a narrower construction requiring a degree of independent, agent-based intelligence beyond simple, scheduled polling for updates.

• The Term: "task pool"

• Context and Importance: Plaintiff's infringement case maps this term onto the entire Aruba Central cloud platform. The viability of this mapping depends on the term's construed scope.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent abstract describes a system with "a CPU, a task pool populated by the CPU, and a plurality of autonomous co-processing cells" '161 Patent, Abstract This high-level description may support a functional definition, where any intermediary that holds tasks for retrieval could be a "task pool".
  • Evidence for a Narrower Interpretation: The specification discloses embodiments where the task pool "may be physically located with the CPU in the same 2D or 3D monolithic IC, or it may be implemented as a stand-alone IC" '161 Patent, col. 7:7-10 This language, along with diagrams showing the task pool as a discrete component, may support a narrower definition that does not encompass a distributed, multi-service cloud platform Compl. p. 4 '161 Patent, Fig. 1

VI. Other Allegations

• Indirect Infringement: The complaint alleges that HPE induces infringement and is liable for contributory infringement, asserting that HPE's "detailed product literature evidences a specific intent to encourage others to participate in the infringement" Compl. ¶60 Compl. ¶146
• Willful Infringement: The complaint alleges willful infringement based on HPE's continued infringing conduct after receiving actual notice of the patent and infringement allegations via service of the original complaint on January 30, 2025 Compl. ¶16 Compl. ¶149 The complaint also alludes to "pre-suit correspondence" as a potential basis for knowledge Compl. ¶58

VII. Analyst's Conclusion: Key Questions for the Case

• A core issue will be one of definitional scope: can the term "task pool," described in the patent as a discrete data structure or component, be construed to read on a comprehensive, distributed cloud management platform like Aruba Central, or is there a fundamental mismatch in scale and architecture?
• A key evidentiary question will be one of functional interpretation: does the accused system's method for device configuration-where devices check in with a central server for updates-constitute the "proactive search" by an "autonomous agent" as required by the claims, or is it a technically distinct client-server interaction?
• The viability of the allegations concerning Claim 37 may turn on a question of technical classification: does a routine network configuration update qualify as a "device function reconfiguration task" that enables a new "task type," or do the claims require a more fundamental change in a device's core processing capabilities?