Cloud Systems Holdco IP LLC v. Rain Bird Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Cloud Systems Holdco IP, LLC (Texas)
  • Defendant: Rain Bird Corporation (California)
  • Plaintiff's Counsel: Andrew M. Ling, P.C.
• Case Identification: 4:26-cv-00089, D. Ariz., 05/07/2026
• Venue Allegations: Venue is based on Defendant having a regular and established place of business in the District of Arizona.
• Core Dispute: Plaintiff alleges that Defendant's smart irrigation control systems, including its Rachio and IQ4 product lines, infringe a patent related to a networked architecture for managing and controlling multiple devices.
• Technical Context: The technology concerns a server-client system that uses a software model of a physical environment to enable hardware-independent control and dynamic reconfiguration of heterogeneous devices.
• Key Procedural History: This First Amended Complaint was filed in response to a Motion to Dismiss from the Defendant. The complaint notes that the asserted patent issued after a substantive examination where the USPTO Examiner identified specific claim limitations-related to an "output device configurator" and a "scheduling service"-as the basis for allowance over more than one hundred cited prior art references. Plaintiff, a non-practicing entity, also addresses potential patent marking issues related to prior settlement licenses.

Case Timeline

Date	Event
2006-05-03	'912 Patent Priority Date
2019-07-30	'912 Patent Issue Date
2025-10-01	Rain Bird acquisition of Rachio, Inc.
2026-05-07	Complaint Filing Date

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

U.S. Patent No. 10,367,912 - "System and Method for Automating the Management, Routing, and Control of Multiple Devices and Inter-Device Connections" (issued Jul. 30, 2019)

The Invention Explained

• Problem Addressed: The patent's background, and the complaint's summary thereof, describe a technical challenge existing at the time of invention (priority date 2006): networked control systems for heterogeneous devices (e.g., in AV or building automation) were plagued by hardware-dependent logic, brittle point-to-point integrations, and an inability to dynamically re-route connections or share devices across different environments without manual reprogramming Compl. ¶13 '912 Patent, col. 1:11-col. 2:67
• The Patented Solution: The invention proposes an integrated, server-based architecture to solve this problem. A central server hosts a database that creates a software "environment model" of the physical space, representing devices as "adaptable nodes" and their physical wiring as "static connections" '912 Patent, col. 5:62-col. 6:8 Compl. ¶14 A control client (e.g., a web application) renders a user interface with standard and specialized widgets, allowing a user to interact with the software model rather than directly with the hardware. A key aspect is a "scheduling service" that manages when and how "output devices" can be accessed and used, abstracting the hardware from the user and enabling dynamic control Compl. ¶12 '912 Patent, FIG. 3
• Technical Importance: This architectural approach enabled hardware-independent control, dynamic reconfiguration of device routing without physical rewiring, and software-mediated management of device access and conflict avoidance Compl. ¶16

Key Claims at a Glance

• The complaint asserts independent claims 1 (apparatus) and 10 (method) Compl. ¶¶30, 40, 49
• Claim 1 (Apparatus) Essential Elements:
  • A server hosting a database with information on "static connections" and "adaptable nodes," and configured to run a "scheduling service."
  • A control client to control an "output device" and communicate with the scheduling service.
  • A control client web application rendering a user interface with "standard widgets" and "specialized widgets" for control options based on the output device.
  • A control switch that communicates with the control client.
  • An "output device configurator" that sends access requests to the scheduling service, sends configuration and control information to the output device, with the scheduling service "configured to manage availability of the output device for access."
• The complaint explicitly reserves the right to assert other claims, including dependent claims 2-9 and 11-19 Compl. ¶41 Compl. ¶59

III. The Accused Instrumentality

Product Identification

• The complaint accuses two distinct product lines:
  1. The Accused Rachio System, which includes the Rachio 3 Smart Sprinkler Controller, the associated Rachio mobile and web applications, and the backend cloud servers and services Compl. ¶24
  2. The Accused IQ4 System, which includes the IQ4 Central Control System, IQ-Cloud servers, IQ-NCC communication cartridges, and ESP-LX Series Controllers Compl. ¶¶25-26

Functionality and Market Context

• The Rachio System is a consumer-focused smart irrigation platform that Rain Bird acquired in October 2025 Compl. ¶18 It operates via a cloud-based architecture hosted on Amazon Web Services (AWS), where users control their sprinkler systems through a mobile or web application. The system uses a database to store information about irrigation "zones," which are described as adaptable based on parameters like soil type, weather, and plant type, and a scheduling service to execute watering schedules Compl. ¶¶31-38
• The IQ4 System is described as Rain Bird's historical product line for commercial, municipal, and athletic-field irrigation environments Compl. ¶27 Compl. ¶50 It employs a centralized control architecture (IQ-Cloud or an IQ Central Computer) that communicates with and manages multiple on-site sprinkler controllers (termed "Satellites"). This communication is enabled by IQ-NCC cartridges that connect the controllers to the central system Compl. ¶¶26, 51 Control is exercised through a web application that provides standard and specialized functions like station priority and flow management Compl. ¶¶54-55

No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

'912 Patent Infringement Allegations (vs. Rachio System)

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a server configured to host a database that includes information describing a set of static connections and information describing a set of adaptable nodes and that is further configured to run a scheduling service	Rachio's AWS-hosted cloud servers host a database. "Static connections" are the zone assignments mapping a physical zone to a controller terminal. "Adaptable nodes" are the zone records that dynamically adapt based on soil type, weather, etc. The servers run scheduling services (Flex Daily, Fixed Schedules) (Compl. ¶32).	¶32	col. 5:62-6:8
a control client that is configured to control at least one output device within the environment and to communicate with the scheduling service	The Rachio mobile and web applications function as the control client, used to control irrigation zones (output devices) and communicate with the cloud-based scheduling service (Compl. ¶33).	¶33	col. 7:10-24
a control client web application including one or more components configured to render a user interface on the control client	The Rachio web application, accessible at app.rach.io, includes components that render the user interface on a user's desktop or laptop browser (Compl. ¶34).	¶34	col. 12:40-52
wherein one or more standard widgets of the user interface provide one or more standard control options based at least in part on the at least one output device	The user interface includes standard widgets like the "Quick Run" feature for manual watering, zone on/off toggles, and start/stop/pause controls, which are keyed to the irrigation zone (output device) (Compl. ¶35).	¶35	col. 12:21-30
and one or more specialized widgets provide one or more customizable control options based at least in part on the at least one output device	The user interface includes specialized widgets for Flex Daily/Monthly schedule configuration, Weather Intelligence settings (e.g., Rain Skip, Wind Skip), and zone customization controls (soil type, sun exposure, etc.) (Compl. ¶36).	¶36	col. 12:31-48
a control switch that is configured to communicate with the control client	The Rachio 3 Smart Sprinkler Controller hardware, which communicates via Wi-Fi with the control client (the mobile/web apps) and switches electrical signals to irrigation zones (Compl. ¶37).	¶37	col. 5:4-10
and an output device configurator that is configured to send a request to access the output device to the scheduling service..., wherein the scheduling service is configured to manage availability of the output device for access	The Rachio cloud and application act as the configurator. It sends access requests to the scheduling service, sends configuration/control data to the zone via the controller, and the scheduling service manages zone availability via Smart Schedules and weather-based skips (Compl. ¶38).	¶38	col. 48:5-18

'912 Patent Infringement Allegations (vs. IQ4 System)

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a server configured to host a database that includes information describing a set of static connections and information describing a set of adaptable nodes and that is further configured to run a scheduling service	The IQ-Cloud and IQ Central Computer act as the server, hosting a database. "Static connections" are the hierarchy parameters linking the central system to controllers. "Adaptable nodes" are the per-station configuration data that changes based on programming updates. The server runs a scheduling service that coordinates execution across controllers (Compl. ¶51).	¶51	col. 5:62-6:8
a control client that is configured to control at least one output device within the environment and to communicate with the scheduling service	A computer or smart device running the IQ4 web application acts as the control client. It controls output devices (an IQ Satellite Controller, station, or zone) and communicates with the scheduling service on the IQ-Cloud/Central Computer to manage irrigation programs (Compl. ¶52).	¶52	col. 7:10-24
a control client web application including one or more components configured to render a user interface on the control client	The IQ4 web application, accessed via a web account, includes components that render the user interface, documented in various IQ4 training materials. It allows users to view status, configure controllers, and perform manual operations (Compl. ¶53).	¶53	col. 12:40-52
wherein one or more standard widgets of the user interface provide one or more standard control options based at least in part on the at least one output device	The IQ4 interface includes standard widgets like Program Setup controls, Start time selectors, and manual start-station controls that operate on specific stations, satellite controllers, or zones (the output devices) (Compl. ¶54).	¶54	col. 12:21-30
and one or more specialized widgets provide one or more customizable control options based at least in part on the at least one output device	The IQ4 interface provides specialized widgets for User-defined Station Priority, watering-window controls, User-defined SimulStations, and FloManager logic. These are based on the output device because they determine how specific stations are prioritized or grouped (Compl. ¶55).	¶55	col. 12:31-48
a control switch that is configured to communicate with the control client	The IQ-NCC and IQ-Cloud communication layer acts as the control switch, routing requests from the control client to the appropriate IQ Satellite Controller and routing status data back (Compl. ¶56).	¶56	col. 5:4-10
and an output device configurator that is configured to send a request to access the output device to the scheduling service..., wherein the scheduling service is configured to manage availability of the output device for access	The IQ4 software and communication architecture acts as the configurator. It sends access requests to the scheduling service when a user starts or modifies a program, sends configuration/control data via the IQ-NCC/IQ-Cloud layer, and the scheduling service manages availability by applying Station Priority and FloManager logic (Compl. ¶57).	¶57	col. 48:5-18

• Identified Points of Contention:
  • Scope Question: A central dispute may concern the definition of "output device." The complaint anticipates this, arguing that the term should be read broadly as a "software-defined, addressable unit" (like an irrigation "zone"), not merely a passive physical endpoint like a sprinkler valve Compl. ¶¶68-71 The resolution of this issue will significantly impact the infringement analysis for both accused systems.
  • Attribution Question (Rachio System): The complaint includes detailed allegations of single-entity attribution, agency, and joint enterprise to address potential divided infringement issues, as end-users perform some actions and the accused system is operated by a subsidiary Compl. ¶¶21-23 Compl. ¶39 Whether Plaintiff can prove Defendant "directs or controls" all steps of the claimed methods will be a critical question.
  • Technical Question: The complaint highlights that the USPTO found the "scheduling service... configured to manage availability" to be a key patentable feature Compl. ¶11 Compl. ¶70 The analysis may turn on whether the accused scheduling functions (e.g., Fixed Schedules, Smart Schedules, FloManager) perform the specific type of "availability management" required by the claims, which could be construed to require more than simple time-based execution.

V. Key Claim Terms for Construction

• The Term: "output device"

  • Context and Importance: The viability of Plaintiff's infringement theory depends on construing "output device" to encompass a logical entity like an irrigation "zone," which can be software-defined and managed. A narrower construction limited to a simple physical endpoint (e.g., a valve) could undermine allegations that the device "receive[s] configuration information" or has its "availability managed" Compl. ¶¶68-69
  • Intrinsic Evidence for a Broader Interpretation: The specification describes "output devices" as "consumer devices" that "accept information" '912 Patent, col. 1:52-54 and exist within a software "environment model" '912 Patent, col. 5:62-col. 6:8, suggesting they are addressable entities, not just passive hardware.
  • Intrinsic Evidence for a Narrower Interpretation: The patent's figures depict concrete physical hardware like "Monitor," "Projector," and "Audio System" as exemplary output devices '912 Patent, FIG. 1a A party could argue that this context limits the term to the final physical component that produces a perceptible output.

• The Term: "scheduling service is configured to manage availability of the output device for access"

  • Context and Importance: The complaint identifies this limitation as a basis for allowance cited by the USPTO examiner, making its construction crucial for both infringement and validity Compl. ¶11 Compl. ¶70 Practitioners may focus on this term because the dispute will likely involve whether simple time-based scheduling meets this limitation, or if more complex, conflict-aware resource management is required.
  • Intrinsic Evidence for a Broader Interpretation: A party could argue that any server-side function that determines whether, when, and under what conditions a device can operate-including basic timers or weather-based skips-constitutes "managing availability."
  • Intrinsic Evidence for a Narrower Interpretation: The specification provides detailed examples of managing "pooled devices" shared across different sub-environments, avoiding scheduling conflicts, and allocating resources based on enterprise calendars '912 Patent, col. 21:23-44 '912 Patent, col. 29:4-30:54 This could support an argument that the term requires sophisticated, multi-user, conflict-avoidance logic, not just simple execution rules for a single user's device.

VI. Other Allegations

• Indirect Infringement: Pled in the alternative for both the Rachio and IQ4 systems, in case any claim limitations are found to be performed by end-users Compl. ¶45 Compl. ¶46
  • Inducement: The complaint alleges inducement based on Defendant's distribution of setup guides, support articles, and other instructional materials that allegedly direct users to operate the systems in an infringing manner. Specific intent is alleged on the basis that the systems are designed for no other purpose Compl. ¶45 Compl. ¶63
  • Contributory Infringement: The complaint alleges that key components, like the Rachio 3 controller and the IQ-NCC cartridges, are not staple articles of commerce suitable for substantial non-infringing use. It specifically alleges the IQ-NCC cartridge's only function is to enable communication with the IQ-Cloud infrastructure Compl. ¶46 Compl. ¶64
• Willful Infringement: The complaint alleges willfulness based on Defendant's continued infringement after receiving notice via the original complaint in this action Compl. ¶66 It also reserves the right to seek damages for pre-suit willfulness pending discovery of prior knowledge Compl. ¶66

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

1. A core issue will be one of definitional scope: can the term "output device," rooted in the patent's examples of audio-visual hardware, be construed to cover a logical, software-defined irrigation "zone" as alleged in the complaint? The outcome of this claim construction battle may be determinative.
2. A second central question, particularly for the Rachio system, will be one of infringement attribution: assuming claim limitations are performed by both Rain Bird's servers and its end users, can the Plaintiff present sufficient evidence of direction or control to satisfy the standard for single-entity liability under Akamai v. Limelight?
3. A key evidentiary question will be one of technical functionality: does the operation of the accused scheduling services (e.g., Rachio's "Weather Intelligence" or IQ4's "FloManager") meet the claimed requirement that the "scheduling service is configured to manage availability," a limitation the patent's prosecution history suggests is critical to its patentability?