Valtrus Innovations Ltd v. TRG Datacenters LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Valtrus Innovations Ltd. and Key Patent Innovations Limited (Ireland)
  • Defendant: TRG Datacenters, LLC (Texas)
  • Plaintiff's Counsel: Reichman Jorgensen Lehman & Feldberg LLP; Findlay Craft, P.C.
• Case Identification: 4:26-cv-06818, S.D. Tex., 08/18/2026
• Venue Allegations: Venue is asserted based on Defendant's residence in the district, where it maintains a regular and established place of business and has allegedly committed acts of infringement.
• Core Dispute: Plaintiffs allege that Defendant's methods for cooling its data centers, which utilize equipment from third-party suppliers, infringe a patent related to agent-based energy management for data center cooling systems.
• Technical Context: The lawsuit concerns technology for dynamically managing the cooling systems in data centers to improve energy efficiency by responding to localized and distributed heat loads.
• Key Procedural History: The asserted patent has expired, meaning Plaintiffs can only seek damages for past infringement. Plaintiffs allege they provided Defendant with pre-suit notice of infringement on March 29, 2024, via a letter that included claim charts for the patent-in-suit. Subsequent licensing discussions were unsuccessful. The complaint also notes a prior representation by Valtrus in a separate matter not to assert a related patent against customers of Vertiv, a supplier whose products are accused in this case.

Case Timeline

Date	Event
2003-01-16	'682 Patent Priority Date
2005-03-22	'682 Patent Issue Date
2024-03-29	Plaintiff sent pre-suit notice letter to Defendant
2026-08-18	Complaint Filing Date

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

U.S. Patent No. 6,868,682 - "Agent Based Control Method and System for Energy Management"

• Patent Identification: U.S. Patent No. 6,868,682, issued March 22, 2005.

The Invention Explained

• Problem Addressed: The patent describes conventional data center cooling systems as inefficient because they typically operate at or near maximum capacity to handle a "worst-case scenario" heat load, regardless of the actual, distributed needs of the equipment Compl. ¶5 '682 Patent, col. 2:11-18 This approach consumes excessive energy, as cooling can account for a significant portion of a data center's power consumption '682 Patent, col. 1:45-49
• The Patented Solution: The invention proposes a distributed, intelligent control system using a "hierarchy of agents" to manage cooling more efficiently '682 Patent, abstract Lower-level "rack agents" monitor and control cooling for individual equipment racks, while higher-level "row agents" and "CRAC agents" manage broader areas and the overall cooling system output, respectively '682 Patent, Fig. 4 If a local agent cannot meet its temperature objectives, it can request assistance from an agent higher in the hierarchy, which can then redistribute cooling resources or increase overall cooling capacity as needed '682 Patent, abstract '682 Patent, col. 3:10-18
• Technical Importance: This agent-based, hierarchical control model represented a method for shifting data center cooling from a static, monolithic approach to a dynamic, demand-responsive system, which could yield significant energy savings '682 Patent, col. 7:42-50

Key Claims at a Glance

• The complaint asserts infringement of at least claim 1 '682 Patent, claim 1 Compl. ¶22
• The essential elements of independent claim 1 are:
  • Receiving sensory data corresponding to a temperature from a subsystem in a data center.
  • Processing the sensory data by a first agent in a hierarchy of agents to determine if the subsystem is operating within a predetermined temperature range.
  • Adjusting a delivery rate for a cooling fluid using the first agent to keep the subsystem within the predetermined temperature range.
  • Requesting a second agent from the hierarchy to process the sensory data when the first agent cannot maintain the temperature range on its own, unless the second agent redistributes the cooling fluid.
• The complaint does not explicitly reserve the right to assert dependent claims, though this is common practice.

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are the methods performed by Defendant TRG Datacenters for cooling its data centers in Texas Compl. ¶13 Compl. ¶22

Functionality and Market Context

• The complaint alleges that Defendant designs, constructs, and operates data centers that implement cooling equipment and control software from various suppliers, including Vertiv (specifically, Liebert cooling systems), Stulz, Trane, Schneider Electric, and DataAire Compl. ¶14 Compl. ¶15 Compl. ¶22
• The allegedly infringing conduct is the performance of cooling methods using this equipment, which Plaintiffs claim embodies the patented agent-based control system Compl. ¶22
• A video tour of a TRG Datacenter facility, which the complaint alleges shows Vertiv cooling equipment in use, is cited as evidence of the use of accused systems Compl. ¶14, fn. 5
• The complaint alleges Defendant operates a data center in Houston and is building additional facilities in Dallas and Austin, suggesting an expanding presence in the Texas market Compl. ¶10

IV. Analysis of Infringement Allegations

The complaint alleges that Defendant's methods of cooling its data centers, using equipment and software from suppliers like Vertiv, perform the steps of the claimed method Compl. ¶22 While the complaint references exemplary claim charts in exhibits that were not provided, its narrative allegations map to the elements of claim 1 as follows.

U.S. Patent No. 6,868,682 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving sensory data corresponding to a temperature from a subsystem in a data center;	Defendant's cooling methods in its data centers, which are generally directed to controlling temperature based on sensory data, necessarily receive temperature data from the equipment being cooled.	¶21; ¶22	col. 3:1-3
processing the sensory data by a first agent in a hierarchy of agents to determine if the subsystems in the data center is operating within a predetermined temperature range;	The "control software" used with the cooling equipment (e.g., from Vertiv) allegedly processes this sensory data using a system that corresponds to the claimed "hierarchy of agents" to manage temperature.	¶22	col. 3:3-6
adjusting a delivery rate for a cooling fluid using the first agent to keep the temperature range of the subsystem within the predetermined temperature range;	The accused methods allegedly involve adjusting cooling delivery to maintain temperature, which Plaintiffs map to the claimed function of the "first agent" autonomously managing its local environment.	¶22	col. 3:6-10
requesting a second agent from the hierarchy of agents to process the sensory data when the first agent cannot keep the temperature range within the predetermined temperature range unless the second agent redistributes the cooling fluid...	The accused methods, enabled by the control software, allegedly include a hierarchical escalation where a local control function's inability to maintain temperature triggers a higher-level function to redistribute cooling resources.	¶22	col. 3:10-18

• Identified Points of Contention:
  • Technical Question: The central technical dispute will likely be whether the accused control software (e.g., from Vertiv) actually operates using a "hierarchy of agents" as described in the patent. The complaint does not provide specific facts showing that the accused systems feature a "first agent" that autonomously attempts to resolve a cooling issue and then explicitly "requests" assistance from a distinct "second agent" that "redistributes" cooling fluid. Evidence of this specific, two-level escalation protocol will be critical.
  • Scope Question: A key legal question will be how broadly the term "hierarchy of agents" is construed. Does it cover any modern, multi-level distributed control system, or is it limited by the specification's examples of a "rack agent" reporting to a "row agent"? (e.g., '682 Patent, Fig. 4).

V. Key Claim Terms for Construction

• The Term: "a hierarchy of agents"
• Context and Importance: This term is the architectural backbone of the asserted claim. The infringement analysis will depend entirely on whether the accused control software can be characterized as a "hierarchy of agents." Practitioners may focus on this term because its construction will determine if the claim reads on a broad class of distributed control systems or is limited to the specific rack/row/CRAC agent structure detailed in the patent's embodiments.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim language itself does not specify the number of levels or the nature of the agents, referring only to "a hierarchy" with a "first agent" and a "second agent" '682 Patent, claim 1 This lack of specific structural limitations in the claim itself may support a broader construction.
  • Evidence for a Narrower Interpretation: The specification consistently and repeatedly illustrates the invention using a specific three-tiered structure: "rack agents," "row agents," and "CRAC agents" '682 Patent, Fig. 4 '682 Patent, col. 13:9-14 A defendant may argue this consistent description limits the claim scope to that particular architecture.
• The Term: "requesting a second agent"
• Context and Importance: This term defines the critical interaction between the hierarchical levels. Its construction will clarify what type of evidence is needed to prove infringement. If "requesting" is construed narrowly to mean a formal, explicit software communication, Plaintiff's evidentiary burden would be higher than if it is construed broadly to include any implicit triggering of a higher-level control loop.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The claim does not define "requesting," which may allow for an interpretation that covers any form of control escalation, whether it is an explicit message or an implicit trigger based on unmet conditions.
  • Evidence for a Narrower Interpretation: The patent's flowcharts depict explicit communication steps, such as when a "Rack Agent Communicates With Row Agent And Provides Input" '682 Patent, Fig. 5, step 510 This language suggests a deliberate, directed communication protocol, which may support a narrower definition of "requesting."

VI. Other Allegations

• Indirect Infringement: The complaint does not include specific counts or factual allegations for indirect infringement. The allegations focus on Defendant's direct performance of the claimed methods Compl. ¶22
• Willful Infringement: The complaint alleges that Plaintiffs provided Defendant with pre-suit notice of infringement on March 29, 2024 Compl. ¶17 This notice allegedly included "claim charts demonstrating infringement of seven patents, including the '682 Patent," which may establish a basis for alleging willful infringement from that date forward Compl. ¶17 The prayer for relief also seeks a finding of an "exceptional case" under 35 U.S.C. § 285 Compl. Prayer D

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

1. Architectural Equivalence: A core issue will be one of architectural mapping: can Plaintiffs produce evidence that the accused third-party control software operates using the specific, multi-level "hierarchy of agents" with the claimed "requesting" and "redistributing" functionality, or will discovery reveal a fundamentally different control logic that falls outside the scope of the claims?

2. Claim Scope and Embodiment Limitation: The case will likely involve a significant claim construction dispute over whether the term "hierarchy of agents" is limited to the rack/row/CRAC agent structure consistently described in the patent's specification. The outcome of this dispute could either confine the patent to a narrow set of embodiments or allow it to cover a wider range of modern distributed cooling control systems.

3. Evidentiary Challenge for Method Claims: As the patent is expired and the case concerns past infringement of a method claim, a key challenge for Plaintiffs will be an evidentiary one: gathering sufficient evidence (e.g., software configurations, operational logs, and expert testimony) to prove how Defendant's data centers actually operated to meet each and every limitation of the asserted claim prior to the patent's expiration.