2:25-cv-00579
Cloud Systems Holdco IP LLC v. Crestron Electronics Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Cloud Systems Holdco IP, LLC (Texas)
- Defendant: Crestron Electronics, Inc. (New Jersey)
- Plaintiff's Counsel: Ramey LLP
- Case Identification: 2:25-cv-00579, E.D. Tex., 07/14/2026
- Venue Allegations: Venue is alleged based on Defendant having a regular and established place of business in the district, having committed acts of infringement in the district, and conducting substantial business there.
- Core Dispute: Plaintiff alleges that Defendant's Crestron Fusion enterprise room-control and monitoring platform infringes a patent related to server-based methods for managing and controlling audiovisual and environmental devices.
- Technical Context: The technology concerns centralized, software-driven systems for controlling complex environments like conference rooms, aiming to replace prior-art solutions that were typically custom-wired, hardware-specific, and less flexible.
- Key Procedural History: This Second Amended Complaint was filed after the court dismissed the Plaintiff's First Amended Complaint without prejudice. The complaint states that Plaintiff is a non-practicing entity and that neither it nor its predecessor-in-interest has ever sold a product. It also discloses prior settlement licenses with other entities, arguing these do not trigger patent marking requirements under 35 U.S.C. § 287.
Case Timeline
| Date | Event |
|---|---|
| 2006-05-03 | '326 Patent Priority Date |
| 2013-09-10 | '326 Patent Issue Date |
| 2025-05-22 | Original Complaint Filing Date |
| 2026-06-30 | Court Dismissal of First Amended Complaint |
| 2026-07-14 | Second Amended Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
- Patent Identification: U.S. Patent No. 8,533,326, Method for Managing, Routing, and Controlling Devices and Inter-Device Connections, issued September 10, 2013 Compl. ¶7
The Invention Explained
- Problem Addressed: The patent addresses the limitations of prior art audiovisual management systems, which are described as "custom designed, closed-system, hardware specific solutions" that could not effectively coordinate numerous devices, store configurations for reuse, or manage permissions for different users in complex modern environments like conference rooms Compl. ¶9 '326 Patent, col. 2:58-col. 3:9
- The Patented Solution: The invention proposes a server-based architecture where the server maintains an "environment model"-a stored, logical representation of the devices, their interfaces, and their physical connections Compl. ¶10 '326 Patent, abstract This server receives commands from a control client and uses the model to generate and execute signal paths, or routes, between source and output devices by commanding switches and other hardware. This centralizes system intelligence in the software model rather than in the physical wiring, allowing for flexible, permission-based control of the environment '326 Patent, col. 5:40-col. 6:15
- Technical Importance: This server-centric approach enabled the control of diverse systems, such as audiovisual facilities and integrated buildings, in a "hardware-independent manner" that was alleged to be unconventional at the time of the invention Compl. ¶¶10-11
Key Claims at a Glance
- The complaint asserts independent claim 1 and notes that independent claim 13 recites a related method (Compl. ¶¶12; Compl. ¶26). The detailed allegations focus on claim 1.
- The essential elements of independent claim 1 include:
- accessing a server associated with the environment via a control client;
- logging into the server as a user and querying a user database to retrieve the user's rights and configuration data;
- rendering a control panel on the control client adapted to the environment based on the user's rights;
- creating a user-defined configuration of source, output, and environmental devices;
- generating a desired path based on an "environment model" stored on the server to connect the source and output devices;
- identifying an event from an event generator, which is handled by an event handler;
- triggering commands to selectively interconnect the source and output devices in response to the event;
- communicating the commands from the server to a "control switch";
- sending a command from the server to the source device to output a signal; and
- outputting the signal on the output device.
- The complaint reserves the right to assert other claims of the '326 patent as discovery proceeds Compl. ¶43
III. The Accused Instrumentality
Product Identification
- The "Accused Fusion System," which is a combination of Defendant's products and services Compl. ¶13 This system comprises the Crestron Fusion software (available as on-premises SW-FUSION-P-L or cloud-based SW-FUSION-C-3), Crestron control processors (e.g., 4-Series), Crestron switching hardware, and the Crestron Fusion SSI (Single System Interface) programming model Compl. ¶13
Functionality and Market Context
- The Accused Fusion System is marketed as an enterprise room-control and monitoring platform Compl. ¶13 Architecturally, it consists of a central Fusion server, which runs on a Microsoft Windows Server and uses a Microsoft SQL Server database to store data about rooms, assets, users, and configurations Compl. ¶14 In each room, a Crestron control processor communicates with the server over an IP network and controls local devices Compl. ¶15 Users interact with the system via a browser-based web client for functions like monitoring, scheduling, and remote "e-Control" of rooms (Compl. ¶¶17; Compl. ¶29).
No probative visual evidence provided in complaint.
IV. Analysis of Infringement Allegations
8,533,326 Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| accessing a server associated with the environment via a control client | A user opens the browser-based Fusion web client, which accesses the Fusion server. | ¶27 | col. 5:40-45 |
| logging into said server as a user, wherein said server queries a user database to retrieve rights and configuration data associated with said user | A Fusion user logs in with credentials, and the server retrieves the user's profile and security-group permissions from a user database (either internal to Fusion or an external Active Directory). | ¶28 | col. 11:4-9 |
| rendering a control panel on said control client, wherein said control panel is adapted to the environment based on said rights and said configuration data | After a user selects a room, the system renders a room-specific "e-Control" interface, but only if the user's security group has the required access rights. | ¶29 | col. 5:43-48 |
| creating a user defined configuration of a source device, an output device, and a device associated with the environment | A user defines a Fusion room by registering assets to it, such as an AirMedia source device, a room display, and environmental devices (e.g., lighting), with the configuration stored on the server. | ¶30 | col. 14:20-29 |
| generating a desired path in the environment based on an environment model to connect said source device to said output device... wherein said environment model is stored in a data structure on said server | This is alleged to occur in two acts: first, pairing a module in a room's program automatically generates signal pathways that connect the server's model to room devices; second, at runtime, the server consults this model (the SQL database) to direct the control switch to connect the source to the output. | ¶31 | col. 8:47-54 |
| identifying an event generated by an event generator, wherein an event handler responds to said event | Fusion's scheduling engine generates a "meeting-start" event, which is delivered via an SSI module to the room's program, whose logic responds to the event. | ¶32 | col. 22:45-51 |
| triggering one or more commands to selectively interconnect an output port of said source device to an input port of said output device in response to said event | In response to the meeting-start event, the system triggers commands that cause the control switch to route the signal from the source device's output port to the output device's input port. | ¶33 | col. 21:26-34 |
| communicating said one or more commands from said server to a control switch | The Fusion server sends commands over the IP network to the room's 4-Series control processor, which is identified as the "control switch." | ¶34 | col. 6:53-58 |
| sending a command from said server to command said source device to output a signal | The Fusion server, via the control switch, sends a command directing the source device (e.g., AirMedia) to present, causing it to output its signal. | ¶35 | col. 8:21-25 |
| outputting said signal on said output device | The routed audiovisual signal is displayed on the room display, and Fusion allegedly monitors and logs this usage. | ¶36 | col. 2:46-54 |
- Identified Points of Contention:
- Scope Questions: A central dispute may arise over whether the accused system's components and data structures fall within the scope of the claim terms. For instance, does the "control switch," which the complaint defines as a combination of a control processor and a presentation switcher Compl. ¶22, meet the singular claim limitation of "a control switch"?
- Technical Questions: The infringement theory for "generating a desired path" alleges a two-part process involving initial programming and subsequent runtime use of the resulting model Compl. ¶31 This raises the question of whether this bifurcated process meets the claim requirement of "generating a desired path," which the patent specification links to a "routing algorithm" that actively "identifies a desired path" '326 Patent, col. 35:4-7, suggesting a more dynamic, runtime computation.
V. Key Claim Terms for Construction
The Term: "environment model"
Context and Importance: This term is the technological core of the patent, representing the data structure upon which path generation depends. The complaint identifies the "Fusion server's stored, structured representation" in its SQL database as the "environment model" Compl. ¶19 The viability of the infringement case hinges on whether this database structure and its use align with the patent's description of the model.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent abstract describes the invention in general terms, stating the server "maintains a representation of the environment and the devices within the environment" '326 Patent, abstract This language may support a broader reading that covers any structured data store representing system components.
- Evidence for a Narrower Interpretation: The detailed description states that the "environment model" represents the "topology of these static connections" and is used by an "intelligent routing engine" to "identify the desired route" '326 Patent, col. 8:48-50 '326 Patent, col. 33:23-35:12 This may support a narrower construction requiring a specific data structure (e.g., a graph) that is actively traversed by an algorithm to "generate" paths, rather than simply being a repository of pre-configured options.
The Term: "generating a desired path"
Context and Importance: This active verb phrase is critical to how the system creates connections. The complaint alleges this step is met by a combination of a one-time programming act that "creates the stored model" and a runtime act where the server "uses that stored model" to direct a switch Compl. ¶31 Practitioners may focus on this term because the plaintiff's theory blends a configuration step with a runtime operational step to meet a single claim limitation.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent does not explicitly define the timing of "generating." It could be argued that the initial configuration that defines potential routes, which are later selected, constitutes a form of path generation.
- Evidence for a Narrower Interpretation: The specification repeatedly refers to a "routing algorithm" that "identifies a desired path" and "traverses" the system's nodes and connections '326 Patent, col. 35:1-30 This language strongly suggests a dynamic, computational process that occurs at runtime to discover or create a path, which may not align with the complaint's theory of selecting from pre-programmed routes.
VI. Other Allegations
- Indirect Infringement: The complaint alleges induced infringement, stating that Crestron instructs and encourages its customers and dealers to operate the Accused Fusion System in an infringing manner by providing materials like the "SSI Guide," online help, design guides, training, and technical support Compl. ¶49 These materials allegedly prescribe the infringing architecture and operational steps Compl. ¶49
- Willful Infringement: The willfulness claim is based on alleged knowledge of the '326 patent since at least May 22, 2025, the filing date of the original complaint Compl. ¶58 The complaint alleges that despite this knowledge, Crestron continued to infringe without a license or design-around, rendering the post-suit infringement deliberate and egregious Compl. ¶¶58-59
VII. Analyst's Conclusion: Key Questions for the Case
- A core issue will be one of definitional scope: can the term "environment model," which the patent links to an active "routing algorithm," be construed to cover the accused system's SQL database that stores pre-defined asset configurations and attributes? The outcome of this construction will likely determine whether the accused system's method of operation infringes.
- A key evidentiary question will concern functional operation: does the accused system's runtime selection of a pre-configured route satisfy the claim limitation "generating a desired path," or does the patent require a dynamic, computational path-finding process that is absent in the accused method?
- The case may also turn on component identity: does the complaint's aggregation of a general-purpose control processor and a separate hardware switcher Compl. ¶22 constitute the singular "control switch" recited in claim 1, or is this an impermissible attempt to map multiple, distinct accused components onto a single claimed element?