Swarm Technology LLC v. Amazon.com Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Swarm Technology, LLC (Arizona)
  • Defendant: Amazon.com, Inc. (Delaware); Amazon Web Services, Inc. (Delaware)
  • Plaintiff’s Counsel: BEUS GILBERT McGRODER PLLC
• Case Identification: 2:21-cv-00438, D. Ariz., 08/26/2022
• Venue Allegations: Plaintiff alleges venue is proper in the District of Arizona because Defendants offer infringing products and services for sale to Arizona residents and maintain regular and established places of business in the state, including corporate offices and fulfillment centers.
• Core Dispute: Plaintiff alleges that Defendant’s Amazon Web Services (AWS) cloud computing products, specifically AWS IoT Core and AWS IoT Greengrass, infringe three patents related to a decentralized parallel processing architecture.
• Technical Context: The technology addresses inefficiencies in traditional multiprocessing by introducing a "task pool" from which autonomous co-processors proactively retrieve tasks, reducing the management burden on the central controller, a model particularly relevant to the Internet of Things (IoT) and large-scale distributed computing.
• Key Procedural History: The complaint alleges that Plaintiff and its counsel contacted Defendant Amazon on at least four separate occasions between November 2015 and July 2018 to announce the issuance of the patents-in-suit and to initiate licensing discussions. This alleged pre-suit knowledge forms the basis for the willfulness allegations. The initial complaint in the district was filed on March 15, 2021.

Case Timeline

Date	Event
2013-01-25	Priority Date for ’777, ’004, and ’275 Patents
2015-09-29	U.S. Patent No. 9,146,777 (’777 Patent) Issues
2015-11-23	Plaintiff’s counsel sends letter to Amazon re: ’777 Patent
2016-02-10	Inventor sends email to Amazon describing technology
2016-08-10	Inventor sends email to Amazon Robotics with links to videos
2017-12-26	U.S. Patent No. 9,852,004 (’004 Patent) Issues
2018-07-16	Plaintiff’s counsel sends license offer to Amazon for ’777, ’004 patents
2020-03-17	U.S. Patent No. 10,592,275 (’275 Patent) Issues
2021-03-15	Plaintiff files initial complaint in the District
2022-08-26	Plaintiff files First Amended Complaint

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

U.S. Patent No. 9,852,004 - "System and Method for Parallel Processing Using Dynamically Configurable Proactive Co-Processing Cells"

• Patent Identification: U.S. Patent No. 9,852,004, "System and Method for Parallel Processing Using Dynamically Configurable Proactive Co-Processing Cells," issued December 26, 2017 (Compl. ¶5).

The Invention Explained

• Problem Addressed: Conventional multiprocessor systems expend significant central processing unit (CPU) resources to distribute tasks to co-processors, which in turn often remain idle while waiting for the CPU to assign them new work (Compl. ¶76; ’004 Patent, col. 1:59-2:4).
• The Patented Solution: The invention proposes a new architecture featuring a "task pool" that acts as an intermediary between a central "controller" and multiple "co-processors" (Compl. ¶4). The controller populates the task pool with work, and the co-processors are configured to be autonomous and proactive, meaning they independently interrogate the task pool to retrieve tasks to perform without waiting for direct instructions from the controller (’004 Patent, abstract; ’004 Patent, col. 2:11-28). This architecture also supports the dynamic, "plug and play" addition of new co-processors to the system ('004 Patent, col. 3:34-40).
• Technical Importance: This decentralized model of task distribution was designed to improve the efficiency, scalability, and flexibility of parallel processing systems, particularly in contexts with many distributed components like the Internet of Things (IoT) (Compl. ¶85).

Key Claims at a Glance

• The complaint asserts independent claim 1 and dependent claims 2-12 (Compl. ¶107; Compl. ¶284).
• The essential elements of independent claim 1 include (Compl. ¶106):
  • A "task pool";
  • A "controller" configured to populate the task pool with tasks;
  • A "first co-processor" configured to successively retrieve, process, and update the task pool upon completion of a task, "all without any communication between the first co-processor and the controller";
  • A "second co-processor" configured to operate in the same manner as the first;
  • Wherein the processing system is configured to "dynamically accept" the co-processors on a "plug-and-play basis without any communication with the controller."

U.S. Patent No. 10,592,275 - "System and Method for Swarm Collaborative Intelligence Using Dynamically Configurable Proactive Autonomous Agents"

• Patent Identification: U.S. Patent No. 10592275, "System and Method for Swarm Collaborative Intelligence Using Dynamically Configurable Proactive Autonomous Agents," issued March 17, 2020 (Compl. ¶5).

The Invention Explained

• Problem Addressed: As with its parent patent, the ’275 Patent addresses the inefficiency and CPU overhead associated with centrally managed task distribution in multiprocessor environments (’275 Patent, col. 2:3-10).
• The Patented Solution: The patent describes the same fundamental architecture of a controller, task pool, and proactive co-processors, but adds a layer of "collaborative intelligence" (’275 Patent, abstract). The key additions are the requirements that the tasks in the pool are "associated with a common objective" and that the co-processors "autonomously work together in solidarity with the task pool to complete the common objective" (’275 Patent, claim 1). This reframes the system as a cooperative "swarm" working toward a shared goal.
• Technical Importance: By formalizing the concepts of a "common objective" and "solidarity," the invention provides a framework for coordinating large numbers of autonomous agents (e.g., IoT devices, robots) to perform complex, goal-oriented collective work, inspired by the swarm intelligence of ant colonies (Compl. ¶71; Compl. ¶75).

Key Claims at a Glance

• The complaint asserts independent claim 1 and dependent claims 2-17 (Compl. ¶112; Compl. ¶292).
• The essential elements of independent claim 1 are largely identical to claim 1 of the ’004 Patent, with the addition of the following limitations (Compl. ¶111):
  • "the plurality of first tasks and the plurality of second tasks are associated with a common objective";
  • "the first and second co-processors autonomously work together in solidarity with the task pool to complete the common objective."

U.S. Patent No. 9,146,777 - "Parallel Processing With Solidarity Cells By Proactively Retrieving From a Task Pool a Matching Task for the Solidarity Cell to Process"

• Patent Identification: U.S. Patent No. 9146777, "Parallel Processing With Solidarity Cells By Proactively Retrieving From a Task Pool a Matching Task for the Solidarity Cell to Process," issued September 29, 2015 (Compl. ¶5).
• Technology Synopsis: As the foundational patent in the family, the ’777 Patent introduces the core concept of an architecture where a CPU populates a "task pool" with computing tasks or threads ('777 Patent, abstract). Autonomous "solidarity cells" (co-processors) then proactively retrieve matching tasks from this pool using a software "agent" without requiring a direct instruction from the CPU, thereby alleviating the CPU's management workload (Compl. ¶115; ’777 Patent, col. 1:43-45).
• Asserted Claims: The complaint asserts independent claim 1 and dependent claims 2-14 (Compl. ¶117; Compl. ¶300).
• Accused Features: The complaint alleges that Amazon's AWS IoT Core and AWS Greengrass products, which manage distributed IoT devices, embody the claimed apparatus for parallel processing (Compl. ¶94; Compl. ¶117).

III. The Accused Instrumentality

Product Identification

• The complaint identifies "AWS IoT Core" and "AWS IoT Greengrass" as the "Infringing Products" (Compl. ¶94).

Functionality and Market Context

• The accused products are cloud-based services offered by Amazon Web Services that enable customers to connect, manage, and interact with large fleets of Internet of Things (IoT) devices (Compl. ¶86; Compl. ¶94).
• The complaint alleges that these services include features referred to by Amazon as a "device shadow" (a persistent, virtual version of a device's state) and "jobs" (a service to manage remote operations for devices), and that these features correspond to the "task pool" and "tasks" recited in the patents-in-suit (Compl. ¶255).
• The complaint highlights the commercial significance of AWS, describing it as Amazon's "wildly profitable cloud computing subsidiary" that registered operating income representing about 71% of the company's total in a 2019 report (Compl. ¶24).
• The complaint includes a "Swarm Architecture" diagram, which it alleges represents the patented invention and is infringed by Defendants' products (Compl. p. 3). This diagram shows a "Controller" populating a "Task Pool," from which a "Co-Processor" retrieves tasks.

IV. Analysis of Infringement Allegations

Since the complaint's claim-chart exhibits are not provided, the following analysis is based on the narrative infringement theory and element-by-element mapping presented in the body of the complaint.

U.S. Patent No. 9,852,004 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
A processing system, comprising:	The AWS IoT Core and AWS Greengrass platforms, which are described as systems for processing data from and for distributed devices (Compl. ¶94; Compl. ¶127).	¶125	col. 14:10
a task pool;	The "device shadow" and "jobs" features within AWS IoT, which allegedly function as a data structure to hold tasks for IoT devices (Compl. ¶129; Compl. ¶255; Compl. ¶259).	¶129	col. 14:11
a controller configured to populate the task pool with a plurality of first tasks and a plurality of second tasks;	An administrator or other AWS service that creates or updates the state of a "device shadow" or creates "jobs" to be performed by IoT devices (Compl. ¶134; Compl. ¶260).	¶134	col. 14:12-13
a first co-processor configured to successively: retrieve a first task from the task pool... all without any communication between the first co-processor and the controller;	An IoT device ("thing") that connects to AWS and is allegedly configured to proactively and independently retrieve its state from the "device shadow" service or a task from the "jobs" service, without direct instruction from the entity that created the task (Compl. ¶138; Compl. ¶139).	¶138	col. 14:14-19
wherein the processing system is configured to dynamically accept the first co-processor...on a plug-and-play basis without any communication with the controller.	The alleged ability of the AWS IoT platform to allow new IoT devices to be added to the network and interact with the task pool (shadow/jobs services) without reconfiguring the central controller (Compl. ¶143; Compl. ¶144).	¶143	col. 14:28-32

U.S. Patent No. 10,592,275 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
[Elements for task pool, controller, and co-processors as above]	[Alleged infringing functionality is identical to the '004 Patent allegations for these common elements]	¶¶164-178	col. 14:25-44
the plurality of first tasks and the plurality of second tasks are associated with a common objective;	The allegation that tasks ("jobs") created in the AWS IoT system are designed to collectively achieve a higher-level system goal, thereby sharing a common objective (Compl. ¶182; Compl. ¶184).	¶182	col. 14:45-46
the first and second co-processors autonomously work together in solidarity with the task pool to complete the common objective.	The allegation that multiple IoT devices, by each pulling tasks from the AWS "jobs" service, are effectively working together cooperatively to achieve the system's shared goal, analogous to a swarm (Compl. ¶186; Compl. ¶187).	¶186	col. 14:47-49

Identified Points of Contention

• Scope Questions: The dispute may center on whether Amazon's "device shadow" (a JSON document for state management) or "jobs" (a remote operation service) legally constitute a "task pool" as envisioned by the patents. A court may question if the term "task pool" requires a specific type of intermediary data structure or if it can be read more broadly to cover these cloud service features.
• Technical Questions: A key factual question is whether the accused systems operate "without any communication" between the co-processor (IoT device) and the controller (the service or user creating the job). The analysis will likely depend on the definition of "controller" and "communication," and whether background system-level messaging (e.g., for authentication or connection management) falls within the claim's prohibition.
• '275 Patent Specifics: For the ’275 Patent, a point of contention may be the standard for "work[ing] together in solidarity." The court will need to determine if this requires active, peer-to-peer coordination between the co-processors, or if it is satisfied by multiple devices independently pulling tasks from a common queue that contribute to a single "common objective."

V. Key Claim Terms for Construction

• The Term: "task pool"
  • Context and Importance: This term is the central architectural component of the invention. The infringement case hinges on whether Amazon's "device shadow" and "jobs" services meet this definition. Practitioners may focus on this term because its scope will likely determine the outcome for all asserted claims.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification describes the task pool as a location where a CPU can place "threads (tasks)" for co-processors to retrieve, which could support a broad interpretation covering any service or data structure holding work items (Compl. ¶130; ’004 Patent, col. 2:11-14).
    • Evidence for a Narrower Interpretation: The patent figures consistently depict the "task pool" as a distinct architectural block, and the specification refers to it as an "intermediary device," which may support a narrower construction requiring a specific, discrete component rather than a more abstract software service or state document (’004 Patent, FIG. 1; ’004 Patent, col. 2:29-31).
• The Term: "without any communication between the... co-processor and the controller"
  • Context and Importance: This negative limitation is a primary point of novelty over prior art where controllers directly managed co-processors. Its construction is critical for determining whether the accused system's operational model infringes.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation (Plaintiff-Favorable): The specification clarifies that in the inventive system, "the CPU communicates directly with the task pool, and communicates indirectly with the co-processors through the task pool" (’004 Patent, col. 2:24-28). This language may support an interpretation where "without any communication" means "without any direct task-assignment communication," while still permitting indirect information flow.
    • Evidence for a Narrower Interpretation (Defendant-Favorable): The plain language could be argued to prohibit all forms of communication, including any system-level, authentication, or status messaging that might occur between an IoT device and a central AWS service that could be defined as part of the "controller."
• The Term: "autonomously work together in solidarity" (’275 Patent, claim 1)
  • Context and Importance: This term is a key feature of the ’275 Patent's "collaborative intelligence" claims. Its definition will determine what level of cooperation is required among the accused devices.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification states that "solidarity implies that co-processing cells share a common objective in monitoring and executing all available tasks within the task pool" (’275 Patent, col. 2:51-54). This may support a construction where merely participating in the same task-pulling system toward a shared high-level goal is sufficient.
    • Evidence for a Narrower Interpretation: The patent's general theme of "swarm collaborative intelligence" and the complaint's reference to ant colonies could be used to argue for a higher standard of cooperation, a potentially requiring emergent, interactive, or peer-to-peer behavior between the co-processors themselves, rather than just independent actions coordinated through a central pool (Compl. ¶71; ’275 Patent, abstract).

VI. Other Allegations

• Indirect Infringement: The complaint alleges inducement of infringement based on Amazon providing published product descriptions, specifications, and instructions that allegedly encourage and guide customers to use the accused AWS services in a manner that infringes the patents-in-suit (Compl. ¶121).
• Willful Infringement: Willfulness is alleged based on both pre-suit and post-suit knowledge. The complaint details four alleged instances of pre-suit notice provided to Amazon between 2015 and 2018 regarding the patents and Plaintiff's interest in licensing them (Compl. ¶¶96-100). Post-suit knowledge is based on the filing of the original complaint on March 15, 2021 (Compl. ¶121).

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

1. Definitional Scope: A core issue will be one of claim construction: can the term "task pool," described in the patents as an intermediary architectural component, be construed to read on Amazon's "device shadow" and "jobs" services, which function as a state-management database and a remote-operation management service, respectively?
2. Functional Equivalence: A central evidentiary question will be whether the operational model of the accused AWS IoT platform meets the claim requirement of operating "without any communication" between the end device ("co-processor") and the task originator ("controller"). The outcome may depend on how the court defines these terms and analyzes the underlying communication protocols of the AWS system.
3. The Standard for "Solidarity": For the claims of the ’275 Patent, the dispute may turn on the legal and factual standard for "work[ing] together in solidarity." The court will need to decide whether this requires active, peer-to-peer coordination between distributed devices, or if it is satisfied by the devices independently pulling tasks from a common queue that all contribute to a single, high-level "common objective."