Google LLC v. Valtrus Innovations Ltd

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Google LLC (Delaware)
  • Defendant: Valtrus Innovations Ltd. (Ireland) and Key Patent Innovations Ltd. (Ireland)
  • Plaintiff's Counsel: Hogan Lovells US LLP
• Case Identification: 3:26-cv-00363, N.D. Cal., 05/04/2026
• Venue Allegations: Venue is alleged to be proper because Defendants are foreign companies subject to personal jurisdiction in the district, and because a substantial part of the events giving rise to the action, including licensing communications and prior litigation directed at Google, occurred in the district.
• Core Dispute: Plaintiff Google LLC seeks a declaratory judgment that its cloud computing products, including managed services for Kubernetes, Apache Hadoop, and Apache Kafka, do not infringe four patents that Defendants have asserted against Google's customers.
• Technical Context: The technology at issue relates to the management of large-scale, distributed computing systems, covering model-driven system monitoring, application deployment, secure data storage, and fault-tolerant network communications.
• Key Procedural History: The complaint details a lengthy history of communications, beginning in April 2021, where Defendants, described as successors to a Hewlett Packard Enterprise patent portfolio, accused Google and its customers of infringing numerous patents, including the four Patents-in-Suit. Defendants have also filed infringement lawsuits against at least 20 other companies, including Google customers, asserting patents from this portfolio. This history of accusations against Google's customers establishes the "actual case and controversy" required for this declaratory judgment action.

Case Timeline

Date	Event
2003-07-25	U.S. Patent No. 7,936,738 Priority Date
2005-06-22	U.S. Patent No. 8,379,538 Priority Date
2006-12-27	U.S. Patent No. 7,640,332 Priority Date
2007-07-31	U.S. Patent No. 7,904,686 Priority Date
2009-12-29	U.S. Patent No. 7,640,332 Issued
2011-03-08	U.S. Patent No. 7,904,686 Issued
2011-05-03	U.S. Patent No. 7,936,738 Issued
2013-02-19	U.S. Patent No. 8,379,538 Issued
2021-04-14	Defendants send first asserted licensing letter to Google
2021-05-13	Defendants send letter to Google identifying the '538 patent
2021-06-09	Valtrus and Google enter into a non-disclosure agreement
2021-09-09	Defendants send third licensing letter to Google
2021-11-15	Defendants send fourth licensing letter to Google
2022-01-10	Defendants file first suit against Google on other patents
2024-01-15	Defendants assert '538 patent against SAP
2024-07-12	Defendants file another suit against Google on other patents
2024-12-27	Defendants file another suit against Google on another patent
2025-01-27	Defendants assert '332 patent against a Google customer (Home Depot)
2025-05-09	Defendants assert '332 and '686 patents against other companies
2025-08-25	Defendants file fourth suit against Google on another patent
2026-01-09	Defendants voluntarily dismiss the August 25, 2025 lawsuit
2026-05-04	Complaint Filing Date

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

U.S. Patent No. 8,379,538 - "Model-Driven Monitoring Architecture," issued February 19, 2013

The Invention Explained

• Problem Addressed: Traditional IT monitoring systems require manual reconfiguration when the environment being monitored changes (e.g., an application moves, or the way metrics are collected is altered) ʻ538 Patent, col. 2:1-22 This manual intervention is inefficient, error-prone, and struggles to keep up with dynamic, complex systems like data centers ʻ538 Patent, col. 3:3-12
• The Patented Solution: The invention proposes a "model-driven" architecture where a "machine-readable monitoring model" formally describes the configuration of the monitoring system ʻ538 Patent, abstract When the environment changes, the model is updated, and other elements, like monitoring tools, can read the updated model to "autonomously adapt" their operation without manual reprogramming ʻ538 Patent, col. 4:30-41 This decouples the monitoring tools from the specific implementation details of the data sources.
• Technical Importance: This architecture enables flexible and automated management of large-scale, dynamic computing environments, a key requirement for modern cloud computing and data center operations ʻ538 Patent, col. 2:40-45

Key Claims at a Glance

• The complaint identifies independent Claim 7 as an exemplary asserted claim Compl. ¶43
• Essential elements of Claim 7:
  • A method comprising: providing a machine-readable monitoring model that defines configuration of a monitoring environment;
  • responsive to a change occurring in said monitoring environment's configuration, said machine-readable monitoring model updating to reflect said change; and
  • an element of said monitoring environment reading said machine-readable model and autonomously adapting its operation to the changed configuration.
• The complaint does not explicitly reserve the right to assert dependent claims but seeks a declaration of non-infringement for the entire patent Compl. ¶46

U.S. Patent No. 7,640,332 - "System and Method for Hot Deployment/Redeployment in Grid Computing Environment," issued December 29, 2009

The Invention Explained

• Problem Addressed: In grid computing environments, applications run on diverse, heterogeneous platforms ʻ332 Patent, col. 1:47-54 Updating or deploying new applications in such an environment is complex and often requires services to be suspended or reinitialized, causing significant overhead and downtime ʻ332 Patent, col. 1:55-62
• The Patented Solution: The invention describes a "hot deployment" system. A central repository stores application bundles ʻ332 Patent, col. 2:36-39 When a new version is added, a discovery service identifies which grid nodes are running the application ʻ332 Patent, col. 2:40-45 A "client application manager" on each relevant node is then notified not only of the update but also of the specific "data transfer protocol" to use ʻ332 Patent, col. 2:45-50 The manager then invokes an "appropriate hot deployment plug-in" to perform the update without interrupting running services ʻ332 Patent, col. 2:50-56
• Technical Importance: The method facilitates zero-downtime application updates in complex, distributed "grid" environments, enhancing system availability and operational efficiency ʻ332 Patent, col. 2:26-31

Key Claims at a Glance

• The complaint identifies independent Claim 1 as an exemplary asserted claim Compl. ¶49
• Essential elements of Claim 1:
  • A method for hot deployment and/or redeployment in a grid computing environment... comprising: adding a new version of an application release bundle in a repository server;
  • determining by a discovery services module which of the one or more grid nodes are running an application associated with the added new version...;
  • notifying a client application manager... about adding the new version of the application release bundle along with a type of data transfer protocol to use; and
  • hot deploying/redeploying the new version of the application release bundle... using an appropriate hot deployment plug-in based on the data transfer protocol by a respective one of the client application managers.
• The complaint seeks a declaration of non-infringement for all claims of the patent Compl. ¶52

Multi-Patent Capsule

• U.S. Patent No. 7,904,686, "Data Security for use with a File System," issued March 8, 2011

  • Technology Synopsis: The patent addresses the problem of securing file data on a storage device from unauthorized reconstruction, which can occur if an attacker accesses a file's index node (inode) to find its data blocks ʻ686 Patent, col. 1:26-34 The solution is a "block distribution engine" that applies a mapping function to the standard data block numbers listed in the inode, generating new "mapped data block numbers" that correspond to the actual, non-linear storage addresses of the data ʻ686 Patent, abstract '686 Patent, col. 3:4-13 This obfuscates the physical layout of the file on the disk.
  • Asserted Claims: Claim 1 is identified as an example claim Compl. ¶55
  • Accused Features: Google's Managed Service for Hadoop is accused of infringement Compl. ¶55

• U.S. Patent No. 7,936,738, "Fault Tolerant Systems," issued May 3, 2011

  • Technology Synopsis: The patent addresses the need for "task preservation" in high-availability (HA) systems, where the state of an ongoing task (like a phone call) must be preserved across a system failure and switchover ʻ738 Patent, col. 1:30-44 The invention provides a method where context information from a protocol stack layer is selectively obtained and added to an outgoing message, ensuring that any response to that message will contain the same context ʻ738 Patent, abstract This allows the newly active system to use the context from the response message to rebuild its state and seamlessly continue the task ʻ738 Patent, col. 2:29-39
  • Asserted Claims: Claim 1 is identified as an example claim Compl. ¶61
  • Accused Features: Google's Managed Service for Kafka is accused of infringement Compl. ¶61

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are Google's cloud services, specifically Google Kubernetes Engine (GKE), Managed Service for Hadoop, and Managed Service for Kafka Compl. ¶¶11, 13-15

Functionality and Market Context

• The complaint describes these products as managed services for popular open-source technologies that are fundamental to modern cloud computing Compl. ¶11
  • Google Kubernetes Engine (GKE) is a service for deploying and managing containerized applications. The complaint highlights two specific functionalities: the "Horizontal Pod Autoscaler (HPA)," which automatically scales the number of application replicas based on observed metrics like CPU utilization, and the rolling update mechanism, where new application versions are deployed by creating new "pods" (application instances) and then removing the old ones Compl. ¶43 Compl. ¶49
  • Managed Service for Hadoop is a service for processing large datasets. The complaint focuses on the Hadoop Distributed File System (HDFS) component, where a "NameNode" determines the location for storing data blocks across the cluster Compl. ¶55
  • Managed Service for Kafka is a distributed event streaming platform. The complaint alleges that this service "always adds any existing protocol header information to its API messages" as part of its normal operation Compl. ¶61
  • These services are alleged to be core components of Google's cloud offerings and are widely used by its customers Compl. ¶¶5, 7

IV. Analysis of Infringement Allegations

No probative visual evidence provided in complaint.

U.S. Patent No. 8,379,538 Infringement Allegations

Claim Element (from Independent Claim 7)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
providing a machine-readable monitoring model that defines configuration of a monitoring environment	The configuration of the monitoring environment within Google Kubernetes Engine (GKE) is the functionality that Defendants would allege meets this element.	¶43	col. 4:30-33
responsive to a change occurring in said monitoring environment's configuration, said machine-readable monitoring model updating to reflect said change	The update of GKE's configuration in response to changes in the operating environment.	¶43	col. 8:1-14
an element of said monitoring environment reading said machine-readable model and autonomously adapting its operation to the changed configuration	The GKE Horizontal Pod Autoscaler (HPA) automatically adjusting the number of pod replicas in a deployment.	¶43	col. 4:35-41

• Identified Points of Contention:
  • Technical Question: The complaint raises a direct technical dispute by stating that GKE's HPA adapts based on "observed metrics" (e.g., CPU load) rather than reading a "changed configuration" of the monitoring model itself Compl. ¶43 The key question for the court will be whether adapting to a dynamic performance metric constitutes adapting to a change in the "configuration" as contemplated by the patent.
  • Scope Questions: A central question will be what constitutes a "machine-readable monitoring model" within GKE. The court will need to determine if GKE's configuration files and state repositories function as the specific, centralized "model" required by the claim, or if the system's architecture is fundamentally different.

U.S. Patent No. 7,640,332 Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
adding a new version of an application release bundle in a repository server	A user or system adding a new container image to an image repository for deployment with GKE.	¶49	col. 2:36-39
determining by a discovery services module which of the one or more grid nodes are running an application associated with the added new version...	The GKE control plane identifying the nodes running the application that is scheduled for an update.	¶49	col. 2:40-45
notifying a client application manager... about adding the new version... along with a type of data transfer protocol to use	The GKE control plane notifying the Kubelet agent on a node about a new container image to be pulled for deployment.	¶49	col. 2:45-50
hot deploying/redeploying the new version of the application release bundle... using an appropriate hot deployment plug-in...	GKE's process of deploying new pods with the updated application image and subsequently terminating the old pods.	¶49	col. 2:50-56

• Identified Points of Contention:
  • Scope Questions: The complaint creates a clear point of contention around the term "hot deploying... using an appropriate hot deployment plug-in" Compl. ¶49 Google argues that its process-deploying new pods, waiting for them to start, and then removing old pods-is technically distinct from the "hot deployment" described in the patent. The case may turn on whether the claim term can be construed to cover modern "rolling update" strategies.
  • Technical Questions: Does the Kubernetes architecture, on which GKE is based, contain discrete components that map to the "discovery services module" and "client application manager" that perform the specific, sequential steps of the claim? The court will need to examine whether the integrated nature of the Kubernetes control plane avoids a literal infringement of the claimed method.

V. Key Claim Terms for Construction

For the '538 Patent:

• The Term: "change occurring in said monitoring environment's configuration"
• Context and Importance: This term is central because Google's primary non-infringement defense is that its GKE HPA scales based on "observed metrics" (like CPU usage), which it argues is not a "change in... configuration" Compl. ¶43 The definition will determine if responding to performance data falls within the claim's scope.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification discusses the model being updated in response to changes in the "monitored or monitoring environments" ʻ538 Patent, col. 3:4-6 A party could argue that a significant change in a performance metric is a change in the state of the "monitored environment," thus triggering the claimed functionality.
  • Evidence for a Narrower Interpretation: The patent repeatedly emphasizes the model's role in defining the structure of the monitoring system, such as defining "metric models," "topology," and "data consumer desires" ʻ538 Patent, FIG. 2B This suggests "configuration" refers to the schema and relationships of the monitoring system, not the dynamic data values flowing through it.

For the '332 Patent:

• The Term: "hot deployment plug-in"
• Context and Importance: Google explicitly denies infringement because its GKE update process (deploying new pods and removing old ones) is allegedly not a "hot deployment... using an appropriate... plug-in" Compl. ¶49 Practitioners may focus on this term because its construction could exclude modern, widely-used rolling update strategies from the patent's scope.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent's background focuses on the problem of needing to "shutdown/restart an application container" ʻ332 Patent, col. 1:41-42 One could argue that any mechanism, modular or not, that achieves an update without service interruption functions as a "hot deployment plug-in" in the context of the invention's purpose.
  • Evidence for a Narrower Interpretation: The specification describes the "plug-in" as a distinct component that is "selected and invoked" by a "client application manager" based on a received "data transfer protocol" ʻ332 Patent, col. 3:12-16 This language supports a narrower definition requiring a specific, modular architecture where a manager component explicitly chooses and runs a separate plug-in, a process potentially different from the integrated control loop of Kubernetes.

VI. Other Allegations

• Indirect Infringement: The complaint seeks a declaratory judgment of non-infringement, including no indirect infringement Compl., Prayer for Relief B Google's position is that since its products do not directly infringe, it cannot be liable for inducing or contributing to infringement by its customers Compl. ¶44 Compl. ¶50 Compl. ¶56 Compl. ¶62 The complaint further alleges that the accused Google products have substantial non-infringing uses, a statutory defense to contributory infringement Compl. ¶44 Compl. ¶50 Compl. ¶56 Compl. ¶62
• Willful Infringement: Willfulness is not directly alleged by Google, as it is the plaintiff. However, the complaint establishes a long history of pre-suit communications starting in April 2021, where Defendants allegedly put Google on notice of the patents-in-suit Compl. ¶¶9-15 Should Defendants counterclaim for infringement, this extensive history could be used to support an allegation of willful infringement against Google based on pre-suit knowledge.

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

• A primary issue will be one of technical mechanism and scope: Do the accused Google products, which are based on modern open-source architectures, operate according to the specific, sequential steps laid out in the patent claims? For example, does GKE's metric-based autoscaling constitute adapting to a "configuration" change ('538 patent), and is its rolling-update procedure equivalent to a "hot deployment" using a "plug-in" ('332 patent)?
• A second central conflict will be one of claim construction: Can claim terms rooted in the specific technological context and architecture of the early-to-mid-2000s (e.g., "hot deployment plug-in," "model-driven monitoring") be interpreted broadly enough to read on the functionally similar but architecturally distinct methods used in today's dominant cloud-native technologies like Kubernetes?
• Strategically, a key question is the jurisdictional battle: By filing this declaratory judgment action in the Northern District of California, Google is proactively seeking to litigate in its home forum, preempting an anticipated infringement suit from Defendants, who have a pattern of filing cases in the Eastern District of Texas Compl. ¶¶21-22 The outcome of any early jurisdictional motions could significantly influence the posture of the case.