DCT

5:26-cv-02379

Valtrus Innovations Ltd v. Google LLC

Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 5:26-cv-02379, N.D. Cal., 03/18/2026
  • Venue Allegations: Venue is asserted based on Defendant's corporate headquarters and regular and established places of business within the Northern District of California, where acts of infringement are alleged to occur.
  • Core Dispute: Plaintiffs allege that Defendant's Google Search and Google Cloud products infringe three patents related to merging search engine result lists, hardware-based processor utilization metering, and ranking hypertext search results.
  • Technical Context: The patents-in-suit concern foundational technologies in internet search result aggregation, cloud computing resource management, and search result quality ranking.
  • Key Procedural History: The complaint alleges that Defendant had pre-suit knowledge of all asserted patents. This knowledge is alleged to stem from Defendant's own patents citing the patents-in-suit, Defendant's hiring of the named inventors, and a prior lawsuit filed by Plaintiff Valtrus against Defendant on January 10, 2022, asserting infringement of the same three patents. The complaint also notes that for one patent, language regarding a "predetermined manner" was added during prosecution to secure allowance.

Case Timeline

Date Event
1999-10-15 '604 Patent Priority Date
2001-08-27 '704 Patent Priority Date
2002-07-23 '809 Patent Priority Date
2004-04-27 '704 Patent Issue Date
2004-11-09 '809 Patent Issue Date
2008-03-18 '604 Patent Issue Date
2012-06-26 Alleged date of Google's knowledge of '604 Patent
2013-01-01 Alleged date of Google's knowledge of '704 Patent
2021-04-14 Alleged date of Google's knowledge of '809 Patent
2022-01-10 Prior complaint filed by Valtrus against Google asserting the patents-in-suit
2026-03-18 Complaint Filing Date

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

U.S. Patent No. 6,728,704 - "Method and apparatus for merging result lists from multiple search engines," issued April 27, 2004

The Invention Explained

  • Problem Addressed: At the time of the invention, merging result lists from multiple search engines was computationally expensive because it typically required examining and ranking every single entry from every list, which could "nullify any advantage gained by operating multiple search engines at the same time" Compl. ¶16 '704 Patent, col. 2:48-56
  • The Patented Solution: The invention proposes a more efficient method that avoids examining every entry Compl. ¶17 Instead, it selects a smaller "subset of entries" from each list, assigns a "representative value" to the entire list based on the scores within that subset, and then merges the lists based on these representative values '704 Patent, abstract '704 Patent, col. 3:1-10 The patent also describes this representative value changing "in a predetermined manner" as the merged list is produced Compl. ¶22
  • Technical Importance: This approach sought to reduce computational overhead and improve response time for meta-search engines or systems that aggregate results from various specialized search sources '704 Patent, col. 3:20-24

Key Claims at a Glance

  • The complaint asserts independent claim 1 and reserves the right to assert dependent claims Compl. ¶¶11-73
  • Claim 1 Elements:
    • transmitting a query to a set of search engines;
    • receiving a result list from each search engine;
    • selecting a subset of entries from each result list to form a set of selected entries;
    • assigning to each selected entry of said set of selected entries a scoring value according to a scoring function;
    • assigning to each subset a representative value according to the scoring values assigned to its entries; and
    • producing a merged list of entries in a predetermined manner based on the representative value assigned to each result list, wherein the representative value varies in accordance with predetermined manner.

U.S. Patent No. 6,816,809 - "Hardware based utilization metering," issued November 9, 2004

The Invention Explained

  • Problem Addressed: In computer systems with partitioned hardware, where different operating systems might run separately, gathering processor utilization data via software was challenging Compl. ¶79 Software-based agents on each operating system were required, but communication between them could be unreliable or impossible, leading to inaccurate metering '809 Patent, col. 1:18-36
  • The Patented Solution: The patent proposes a hardware-based solution that operates independently of the operating systems '809 Patent, col. 2:50-62 It claims a device comprising three core hardware components: an "idle indicator" to detect when a processor is busy, a "counter" that tracks time based on a system clock only when the indicator signals a busy state, and a "data usage provider" to store and provide the counter's value '809 Patent, col. 7:30-43
  • Technical Importance: This hardware-centric approach was designed to provide reliable processor utilization data, particularly for pay-per-use billing in complex, partitioned server environments, without depending on inter-OS software communication '809 Patent, col. 1:6-8

Key Claims at a Glance

  • The complaint primarily asserts dependent claim 2, which relies on independent claim 1, and reserves the right to assert other claims, including independent claim 13 (Compl. ¶92; Compl. ¶93; Compl. ¶94; Compl. ¶95; Compl. ¶96; Compl. ¶97; Compl. ¶98; Compl. ¶99; Compl. ¶100; Compl. ¶101).
  • Claim 1 Elements:
    • an idle indicator coupled to a processor, wherein the idle indicator receives an indication when the processor is in a first state;
    • a counter coupled to the idle indicator and a system clock, wherein the counter generates a counter value indicative of time the processor is in the first state; and
    • a data usage provider coupled to the counter, capable of providing the counter value.
  • Claim 2 adds the limitation:
    • wherein the first state is a busy state.

U.S. Patent No. 7,346,604 - "Method for ranking hypertext search results by analysis of hyperlinks from expert documents and keyword scope," issued March 18, 2008

Technology Synopsis

The patent addresses the problem of distinguishing authoritative, high-quality search results from "spam pages" created to mislead search engines Compl. ¶138 The proposed solution is a two-phase process: first, a pre-processing step identifies "expert documents" (pages that link to many non-affiliated pages on a given topic) without reference to a specific query; second, when a query is received, the system ranks these pre-identified experts and then ranks the "target documents" to which those experts link to generate the final search results Compl. ¶141 '604 Patent, col. 2:53-54

Asserted Claims

The complaint asserts independent claim 1 Compl. ¶147

Accused Features

The complaint alleges that Google Search infringes the '604 Patent, particularly through its use of an algorithm known as "Hilltop" to build a "special index of expert documents" that serves as a basis for determining authority and trustworthiness Compl. ¶151

III. The Accused Instrumentality

Product Identification

  • For the '704 and '604 Patents: Google Search and its associated features and back-end systems, such as "Universal Search" Compl. ¶27 Compl. ¶135
  • For the '809 Patent: Google Cloud products, including virtual machines (VMs) such as C3D, N2D, T2D, and C2D that utilize AMD EPYC processors, and internal systems like Google's "Borg" cluster manager Compl. ¶86 Compl. ¶89

Functionality and Market Context

  • Google Search: The complaint alleges that Google Search integrates results from multiple specialized search "corpora" or "engines" (e.g., Web, Maps, News, Images) into a single, merged search results page presented to the user Compl. ¶27 Compl. ¶31 This functionality is central to the user experience of Google's dominant search engine Compl. ¶6
  • Google Cloud: The complaint alleges that Google Cloud services rely on processors with built-in hardware performance counters, such as MPERF and APERF counters Compl. ¶96 These counters are allegedly used for functions like "predictive autoscaling," which forecasts future CPU demand to manage VM resources efficiently Compl. ¶88 The complaint provides a table from Google's marketing materials showing the accused AMD EPYC processor families used in its cloud offerings Compl. ¶86, p. 32

IV. Analysis of Infringement Allegations

'704 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
selecting a subset of entries from each result list to form a set of selected entries Google Search returns millions of results but selects only a small subset for display on the first results page. The screenshot highlighting the number of results versus those displayed illustrates this selection process (Compl. ¶37, p. 13). ¶37 col. 8:9-10
assigning to each subset a representative value according to the scoring values assigned to its entries For a given query, Google Search allegedly orders the result groups (e.g., Maps, News) based on a representative value assigned to each group that reflects its relevance to the query. For a location-based query, the Maps group is alleged to receive a higher value and appear higher on the page (Compl. ¶43). ¶41; ¶43 col. 8:12-13
producing a merged list of entries in a predetermined manner based on the representative value assigned to each result list Google Search produces a single, merged list where the different result groups are ordered based on the representative values assigned to them. A screenshot shows distinct groups for Web, Maps, and News results presented in a single list (Compl. ¶35, p. 12). ¶42 col. 8:14-16
wherein the representative value varies in accordance with predetermined manner The representative value that determines the ranking of result groups allegedly varies based on the nature of the user's query. The complaint presents screenshots showing different result groupings for a "hospital" query versus a "target" query to support this (Compl. ¶45, p. 17). ¶44; ¶45 col. 8:17-18
  • Identified Points of Contention:
    • Scope Questions: A central question may be the interpretation of "varies in accordance with predetermined manner." The patent specification describes an embodiment where a representative value is decremented during the process of building a single merged list '704 Patent, col. 6:15-18 The complaint, however, alleges infringement based on the representative value being different for different types of queries (e.g., location vs. general) Compl. ¶45 The dispute may focus on whether the claim language covers this inter-query variation.
    • Technical Questions: What evidence does the complaint provide that Google's internal ranking systems (e.g., Tangram) actually assign a discrete "representative value" to entire result subsets as required by the claim, rather than simply ranking individual entries from all sources in a unified process? The complaint alleges this occurs "on information and belief" Compl. ¶41

'809 Patent Infringement Allegations

Claim Element (from Dependent Claim 2, incorporating Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
an idle indicator coupled to a processor Processors used in Google Cloud allegedly contain a "hardware idle indicator" that stops and starts performance counters. This is alleged to occur when the processor enters or exits a non-processing state Compl. ¶96 Compl. ¶104 ¶95; ¶96 col. 4:36-56
wherein the first state is a busy state The accused hardware performance counters (MPERF and APERF) allegedly increment only when the processor core is in a "C0 (busy) state" Compl. ¶96 A diagram from a Google presentation shows CPU utilization metrics allegedly derived from this hardware Compl. ¶100, p. 34 ¶101 col. 7:30-31
a counter coupled to the idle indicator ... [that] generates a counter value indicative of time the processor is in the first state The MPERF and APERF counters are allegedly started and stopped by the hardware idle indicator and generate a value indicating the time the processor is in a busy state Compl. ¶98 ¶97; ¶98 col. 4:8-23
a data usage provider coupled to the counter... capable of providing the counter value The processor allegedly has a "data usage provider coupled to the counter" that is capable of providing the counter value to an external network, as evidenced by Google Cloud's public metrics API Compl. ¶100 ¶99; ¶100 col. 4:8-13
  • Identified Points of Contention:
    • Scope Questions: Does a standard, multi-purpose hardware performance counter found in a modern CPU (like AMD EPYC's MPERF/APERF counters) meet the definition of the claimed "hardware based utilization metering device"? The defense may argue the patent claims a specific, dedicated device for pay-per-use billing, not general-purpose processor state counters.
    • Technical Questions: Does the "idle indicator" function as alleged in the complaint operate as a distinct hardware component coupled to the counter as claimed, or is it an integrated function of the processor's own power management unit that is not separately "coupled" in the manner described by the patent?

V. Key Claim Terms for Construction

For the '704 Patent:

  • The Term: "varies in accordance with predetermined manner" (Claim 1)
  • Context and Importance: This limitation was added during prosecution to overcome a prior art rejection, making its interpretation critical Compl. ¶26 The dispute will likely center on whether "varies" refers to a dynamic change during the merging of a single query's results or a static difference between the results of different query types.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Narrower Interpretation: The specification describes an embodiment where the representative value is "decremented by a fixed amount" after an entry is selected from its list, suggesting a dynamic, intra-query process '704 Patent, col. 6:15-18
    • Evidence for a Broader Interpretation: The plaintiff may argue that the claim is not limited to the specific decrementing embodiment and that any rule-based variation, including one based on query type, meets the "predetermined manner" requirement.

For the '809 Patent:

  • The Term: "hardware based utilization metering device" (Claim 1)
  • Context and Importance: This term defines the overall invention. The case may turn on whether general-purpose performance monitoring hardware integrated into a modern CPU constitutes the specific "device" contemplated by the patent, which was described in the context of solving metering problems for billing in partitioned systems.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Narrower Interpretation: The patent's background and summary repeatedly frame the invention as a solution for "pay-per-use systems" and "billing" '809 Patent, col. 1:6-8 '809 Patent, col. 2:44-48 This context may support an argument that the claimed "device" is one purposed for commercial metering, not general performance monitoring.
    • Evidence for a Broader Interpretation: The claims themselves define the device structurally (indicator, counter, provider) without explicitly limiting its purpose to billing. The plaintiff may argue that any hardware structure meeting these elements infringes, regardless of its ultimate use in the accused system.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges induced infringement for all three patents. It asserts that by offering Google Search and Google Cloud products, Defendant knowingly encourages and facilitates infringing uses by the public in the United States Compl. ¶71 Compl. ¶127 Compl. ¶174
  • Willful Infringement: The complaint makes detailed allegations of willful infringement for all three patents. It alleges Defendant had knowledge based on: (1) a prior lawsuit filed on January 10, 2022, asserting the same patents Compl. ¶70 Compl. ¶126 Compl. ¶173; (2) Defendant's own patents citing the patents-in-suit, with the earliest alleged knowledge date being June 2012 Compl. ¶69 Compl. ¶172; and (3) Defendant's hiring of several of the named inventors, who hold or have held senior roles related to the accused technologies Compl. ¶69 Compl. ¶134

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

  • A core issue will be one of temporal scope: for the '704 Patent, can the term "varies," described in the specification as an intra-query, step-by-step change, be construed to cover the accused system's alleged practice of assigning different static values based on inter-query characteristics?
  • A second central question will be one of definitional scope: for the '809 Patent, do general-purpose, integrated CPU performance counters, which are standard components in modern processors, constitute the specific "hardware based utilization metering device" claimed in a patent that was framed as a solution for pay-per-use billing systems?
  • A key evidentiary question will be one of scienter and willfulness: given the allegations of a prior lawsuit, patent citations, and employment of the inventors, what level of knowledge and intent can Plaintiffs establish, and from what date, to support their claims for enhanced damages?