Byteweavr LLC v. Databricks Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Byteweavr, LLC (Texas)
  • Defendant: Databricks, Inc. (Delaware)
  • Plaintiff's Counsel: BRAGALONE OLEJKO SAAD PC
• Case Identification: 2:24-cv-00162, E.D. Tex., 07/18/2024
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant Databricks, Inc. has committed acts of infringement in the district and maintains a regular and established place of business in Plano, Texas, within Collin County.
• Core Dispute: Plaintiff alleges that Defendant's Databricks Lakehouse Platform, a cloud-based data management and analytics service, infringes seven patents related to extensible network systems, distributed computing, data compression, and automated workflow management.
• Technical Context: The lawsuit concerns the foundational architecture of large-scale data analytics and machine learning platforms, a market central to enterprise AI and business intelligence initiatives.
• Key Procedural History: The complaint does not reference any prior litigation, licensing history, or post-grant proceedings involving the Asserted Patents.

Case Timeline

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

U.S. Patent No. 6,839,733 - "Network system extensible by users"

• Issued: January 4, 2005

The Invention Explained

• Problem Addressed: The patent's background describes the process of customizing technological services for individual subscribers as expensive and time-consuming, as it requires human software developers to manually modify and test supporting software applications for each custom request '733 Patent, col. 1:5-29
• The Patented Solution: The invention proposes a network system that is extensible by its users through the use of software "agents" '733 Patent, col. 2:45-49 An "agent server" manages the system and allows users, via a user interface, to create or modify these agents to perform specific tasks '733 Patent, abstract '733 Patent, col. 3:3-9 The agents interact with various network "services" (e.g., e-mail, voice mail) through "service wrappers," which mediate the interaction and monitor the consumption of resources '733 Patent, Fig. 1 '733 Patent, col. 2:50-59
• Technical Importance: This architecture provided a framework for users to programmatically customize network services without direct intervention from the service provider's developers, aiming to increase flexibility and reduce costs.

Key Claims at a Glance

• The complaint asserts independent claim 37 '733 Patent, claim 37 Compl. ¶85
• The essential elements of claim 37 are:
  • A method comprising admitting a user to a network system wherein at least one agent is operable to consume a service resource while utilizing a service to perform a task for the user; and
  • allowing the user to create, modify, or delete the agent within the network system.
• The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 7,949,752 - "Network system extensible by users"

• Issued: May 24, 2011

The Invention Explained

• Problem Addressed: As a continuation of the '733 patent, the '752 Patent addresses the same general problem of enabling user-customizable network services '752 Patent, col. 1:12-32
• The Patented Solution: The patent focuses on a specific method for creating and invoking "network-based agents." The system receives data to create an agent, and the agent's execution is invoked in response to receiving a Uniform Resource Locator (URL) that defines an event type and identifies the agent '752 Patent, abstract This invocation uses a service and consumes a "discrete unit" of a service resource. The result of the agent's operation is then communicated back over a network link '752 Patent, col. 17:50-col. 18:10
• Technical Importance: This approach specified a web-native (URL-based) mechanism for triggering and managing the execution of user-defined software agents within a network service environment.

Key Claims at a Glance

• The complaint asserts independent claim 24 '752 Patent, claim 24 Compl. ¶96
• The essential elements of claim 24 are:
  • Receiving, using a computing device, data for creating a network-based agent;
  • Invoking, using the computing device, and in response to receiving a URL defining a type of event and identifying the network-based agent, execution of the network-based agent;
  • Wherein the invoking comprises using a service and a service resource configured to be consumed by the network-based agent, and wherein a discrete unit of the service resource is exhausted upon being consumed; and
  • Communicating, using the computing device, a result of the operation over a network communication link.
• The complaint does not explicitly reserve the right to assert dependent claims.

U.S. Patent No. 6,862,488 - "Automated validation processing and workflow management"

• Issued: March 1, 2005
• Technology Synopsis: The patent describes a system for automating the validation lifecycle for equipment and processes, particularly in regulated manufacturing environments like pharmaceuticals or biotechnology '488 Patent, col. 1:10-14 The system provides a user interface to accept and display data, and a validation processing engine with processing rules to generate and manage validation protocols '488 Patent, abstract
• Asserted Claims: The complaint asserts at least claim 11 Compl. ¶107
• Accused Features: The complaint alleges that the Databricks Lakehouse Platform, when used for pharmaceutical and biotech applications to automate analytics workflows, infringes the '488 patent Compl. ¶47 Compl. ¶108

U.S. Patent No. 6,965,897 - "Data Compression Method and Apparatus"

• Issued: November 15, 2005
• Technology Synopsis: The patent discloses a data compression method for large database tables that uses a "mixed format physical layout" comprising fixed-sized fields, variable-sized fields, and offset slots '897 Patent, abstract This structure is designed to improve compression ratios by encoding column-wise redundancy while maintaining fast random access required by relational database management systems '897 Patent, col. 1:5-13
• Asserted Claims: The complaint asserts at least claim 1 Compl. ¶118
• Accused Features: The infringement allegation targets Databricks' use of the Avro data format, which supports fixed and variable-sized fields, in conjunction with "deflate" compression, which allegedly utilizes offset slots Compl. ¶¶60-63 Compl. ¶119

U.S. Patent No. 7,082,474 - "Data sharing and file distribution method and associated distributed processing system"

• Issued: July 25, 2006
• Technology Synopsis: This patent describes a method for operating a distributed processing system where a Server system selectively distributes workloads to a multiplicity of Host distributed devices '474 Patent, abstract The method includes sending the host device an index of data addresses required to process the workload and later updating that index to include a storage address on the host device itself, facilitating data sharing and distribution '474 Patent, col. 36:1-27
• Asserted Claims: The complaint asserts at least claim 1 Compl. ¶129
• Accused Features: The complaint alleges that the Databricks platform infringes by having a cluster manager (Server system) distribute workloads to multi-node clusters (Host distributed devices) and sending an index of data locations (e.g., cloud object storage locations) to process the workload Compl. ¶¶53-56 Compl. ¶130

U.S. Patent No. 8,275,827 - "Software-based network attached storage services hosted on massively distributed parallel computing networks"

• Issued: September 25, 2012
• Technology Synopsis: The invention relates to providing software-based Network Attached Storage (NAS) services on a distributed computing network '827 Patent, abstract Client agent programs running on distributed devices include a software NAS component that assesses and utilizes unused or under-utilized storage resources on those devices, making them appear to client devices as dedicated NAS devices '827 Patent, col. 1:49-60
• Asserted Claims: The complaint asserts at least claims 2 and 14 Compl. ¶140
• Accused Features: The complaint alleges that Databricks' clusters (distributed devices) and their included worker nodes (client agents) have corresponding software-based NAS components (e.g., instances) that use dedicated storage resources for workload processing Compl. ¶¶66-69 Compl. ¶141

U.S. Reissued Patent No. RE42153 - "Dynamic coordination and control of network connected devices for large-scale network site testing and associated architectures"

• Issued: February 15, 2011
• Technology Synopsis: The patent describes a method for dynamic coordination of distributed client systems in a computing platform. A server distributes workloads and initial parameters to client systems, receives "poll communications" from them during processing, and analyzes these communications to determine whether to modify the parameters, such as by adding or reducing the number of actively participating clients RE42153 Patent, abstract
• Asserted Claims: The complaint asserts at least claim 1 Compl. ¶153
• Accused Features: The complaint alleges that Databricks' "Enhanced Autoscaling" functionality infringes by monitoring worker nodes (client systems) and dynamically allocating or removing cluster resources (adding/reducing clients) based on workload volume Compl. ¶72 Compl. ¶76 Compl. ¶154

III. The Accused Instrumentality

Product Identification

• The complaint identifies the "Accused Instrumentalities" as Databricks' data management and analytics products and services, primarily the Databricks Lakehouse Platform and its components Compl. ¶27 These components include, but are not limited to, Databricks SQL, Delta Lake, Unity Catalog, Databricks Marketplace, the Data Intelligence Platform, and Databricks Spark Applications Compl. ¶27

Functionality and Market Context

• The complaint describes the Databricks Lakehouse Platform as a "unified, open analytics platform" that combines features of data lakes and data warehouses to manage and analyze large-scale data Compl. ¶4 The platform is used by customers for data engineering workflows, machine learning model development, and business intelligence analytics Compl. ¶32 A screenshot provided in the complaint shows Databricks describing its platform as for "building, deploying, sharing, and maintaining enterprise-grade data, analytics, and AI solutions at scale" Compl. p. 13
• The platform integrates with a customer's cloud storage and deploys cloud infrastructure on the customer's behalf Compl. ¶32 A key component highlighted is MLflow, an open-source framework integrated with the platform to "manage the complete Machine Learning lifecycle" Compl. ¶32 Compl. p. 13
• The complaint notes Databricks' significant market position, citing a valuation of $43 billion and use by over 50% of Fortune 500 companies Compl. ¶3

IV. Analysis of Infringement Allegations

'733 Patent Infringement Allegations

'752 Patent Infringement Allegations

Identified Points of Contention

• Scope Questions: A primary point of contention may be whether the term "agent" (or "network-based agent"), as defined in a patent family with a 1998 priority date, can be construed to read on modern, cloud-based constructs such as an "MLflow model" or a "Databricks cluster." The defense may argue that the patent's description of agents as potentially mobile software objects '733 Patent, col. 9:66-col. 10:2 is fundamentally different from the accused instrumentalities.
• Technical Questions: The infringement theory for the '752 patent hinges on the user's click of a "Run now" button (Compl. p. 22) constituting "receiving a URL" that both "defin[es] a type of event" and "identif[ies] the network-based agent." The analysis may turn on whether this modern UI interaction performs the specific function required by the claim language, or if there is a technical distinction between this action and the explicit URL-based invocation described in the patent.

V. Key Claim Terms for Construction

• The Term: "agent" (and "network-based agent")
• Context and Importance: This term is central to the infringement allegations for both the '733 and '752 patents. The plaintiff's case depends on construing this term broadly enough to cover Databricks' "MLflow models" and "clusters." Practitioners may focus on this term because its construction will likely determine whether the core infringement theories are viable.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The specification provides a broad definition, stating an agent may be a "software application, program, or process which autonomously, and possibly continuously, runs on behalf of its principal" '733 Patent, col. 8:38-41 This language could support an interpretation that covers complex software constructs like ML models or compute clusters that execute tasks.
  • Evidence for a Narrower Interpretation: The specification also describes agents in a manner that suggests mobility, stating that an agent "may direct its own movement (i.e., transportation) through a computer-based system" '733 Patent, col. 9:66-col. 10:2 This could support a narrower construction limited to mobile software agents, which may not describe a Databricks cluster.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement of the '827 patent Compl. ¶143 The allegations are based on Databricks providing documentation, manuals, technical support, and a "Partner Connect" program that allegedly instruct and encourage customers and partners to use the platform in an infringing manner Compl. ¶143 Compl. ¶75 Compl. ¶76
• Willful Infringement: Willfulness is alleged for the '827 patent, based on the allegation that Databricks continued its infringing conduct despite having knowledge of the patent Compl. ¶144 For all asserted patents, the complaint alleges knowledge "at least as early as the filing date of this Complaint" (e.g., Compl. ¶87; Compl. ¶98), which may support a claim for post-suit willfulness.

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

• A core issue will be one of definitional scope: can the term "agent," rooted in the patent family's 1998 description of user-programmable, potentially mobile software objects, be construed to cover modern, cloud-native constructs like "MLflow models" or "Databricks clusters" that operate within a managed platform? The outcome of this claim construction battle will be pivotal for several of the asserted patents.
• A key evidentiary question will be one of functional correspondence: does the interaction with the Databricks graphical user interface, such as clicking a "Run now" button to initiate a job, perform the specific, multi-part function of "receiving a URL defining a type of event and identifying the network-based agent" as required by the claims, or is there a fundamental mismatch in technical operation between the accused system and the patented method?
• A third central question will be one of technological evolution: how will the court view infringement allegations that map concepts from patents filed in the late 1990s and early 2000s onto a sophisticated, multi-component cloud platform developed more than a decade later? The case will likely involve significant expert testimony on whether the accused functionalities are merely new implementations of the old, patented ideas or represent a distinct technological paradigm.