DCT

1:19-cv-00179

Data Scape Ltd v. Barracuda Networks Inc

Key Events
Complaint
complaint

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:19-cv-00179, E.D. Cal., 02/07/2019
  • Venue Allegations: Plaintiff alleges venue is proper because Defendant is registered to do business in California, has transacted business and committed acts of infringement in the Eastern District of California, and maintains regular and established places of business within the district.
  • Core Dispute: Plaintiff alleges that Defendant’s Barracuda Backup products and cloud services infringe four patents related to methods for managing and communicating data between a primary storage apparatus and a secondary apparatus.
  • Technical Context: The technology at issue falls within the domain of data backup, replication, and synchronization, a critical market for enterprise data protection and disaster recovery.
  • Key Procedural History: The complaint alleges that Defendant has had knowledge of the patents-in-suit since at least the filing of an "original Complaint in this action," suggesting the current complaint may be an an amended version or part of a longer-running dispute, though no further details of prior proceedings are provided.

Case Timeline

Date Event
1999-09-21 Earliest Priority Date (’929, ’581, ’751 Patents)
2002-06-12 Earliest Priority Date (’893 Patent)
2010-05-18 U.S. Patent No. 7,720,929 Issued
2013-02-26 U.S. Patent No. 8,386,581 Issued
2017-07-25 U.S. Patent No. 9,715,893 Issued
2018-07-17 U.S. Patent No. 10,027,751 Issued
2019-02-07 Complaint Filed

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

U.S. Patent No. 7,720,929 - Communication System And Its Method and Communication Apparatus And Its Method

  • Patent Identification: U.S. Patent No. 7,720,929, “Communication System And Its Method and Communication Apparatus And Its Method,” issued May 18, 2010.

The Invention Explained

  • Problem Addressed: The patent’s background section describes the process of transferring data (such as music) from a primary device (e.g., a music server) to a portable device as cumbersome, particularly when selecting and transferring numerous individual files. Furthermore, creating lists for batch transfers can create confusion as to whether the list is for organizing local files or for transferring them. (’929 Patent, col. 2:42-60).
  • The Patented Solution: The invention proposes a two-apparatus system that decouples data selection from the physical act of data transfer. A user can select data on a source apparatus and edit a "transfer list," regardless of whether the destination apparatus is connected. When a connection is detected, the system automatically initiates the transfer of the selected data, comparing management information between the devices to determine what data needs to be sent. (’929 Patent, Abstract; col. 3:4-14).
  • Technical Importance: This approach simplified the process of synchronizing large media libraries between a host computer and a portable device, addressing a key usability challenge during the rise of digital media players. (’929 Patent, col. 2:42-49).

Key Claims at a Glance

  • The complaint asserts infringement of at least Claim 1 of the ’929 Patent (Compl. ¶9).
  • Independent Claim 1 of the ’929 Patent recites a communication system with essential elements including:
    • A first apparatus having a first storage medium.
    • A second apparatus comprising:
      • a second storage medium for storing management information of data to be transferred;
      • a communicator for data communication with the first apparatus;
      • a detector to detect if the apparatuses are connected;
      • an editor to select data and edit the management information "without regard to the connection"; and
      • a controller to control the data transfer based on the edited information when a connection is detected, wherein the controller is configured to compare management information between the two apparatuses and transmit data based on the comparison.

U.S. Patent No. 8,386,581 - Communication System And Its Method and Communication Apparatus And Its Method

  • Patent Identification: U.S. Patent No. 8,386,581, “Communication System And Its Method and Communication Apparatus And Its Method,” issued February 26, 2013.

The Invention Explained

  • Problem Addressed: The patent addresses the same general problem space as the ’929 Patent: the cumbersome nature of managing and transferring data between a host device and portable players. (’581 Patent, col. 1:50-col. 2:60).
  • The Patented Solution: This invention focuses on managing data transfers to multiple, distinct external devices from a single host. The solution is a communication apparatus that can create and edit a content list and "uniquely associate the list with the external apparatus using a unique identification." When a specific external apparatus connects, the host can extract the correct list from a plurality of lists and transfer the appropriate content. (’581 Patent, Abstract; col. 12:44-55; FIG. 12A).
  • Technical Importance: This technology provided a framework for a single host device, such as a home computer, to manage different synchronization profiles and content libraries for multiple different portable devices, enhancing usability in multi-user or multi-device environments.

Key Claims at a Glance

  • The complaint asserts infringement of at least Claim 1 of the ’581 Patent (Compl. ¶27).
  • Independent Claim 1 of the ’581 Patent recites a communication apparatus with essential elements including:
    • A storage unit to store content data.
    • A communication unit to communicate with an external apparatus.
    • A controller configured to:
      • edit a list so that content data is registered in it;
      • uniquely associate the list with the external apparatus using a unique identification;
      • extract the associated list from a plurality of lists when the external apparatus is connected; and
      • control the transfer of content data from the extracted list.

U.S. Patent No. 10,027,751 - Communication system and its method and communication apparatus and its method

  • Patent Identification: U.S. Patent No. 10,027,751, “Communication system and its method and communication apparatus and its method,” issued July 17, 2018 (Compl. ¶40).
  • Technology Synopsis: This patent, from the same family as the ’929 Patent, describes a similar system for selecting data for transfer irrespective of connection status. It adds limitations requiring the controller to "determine a size of the selected data" and transmit the data based on both the comparison of management information and this size determination, suggesting a pre-transfer check for available storage space on the destination device. (’751 Patent, Abstract).
  • Asserted Claims: Claim 1 (Compl. ¶42).
  • Accused Features: The complaint accuses Barracuda's system of infringing by allowing users to select data for backup, detecting network connectivity, comparing data to determine what to transfer (deduplication), determining the size of the selected data, and transmitting it based on these factors (Compl. ¶¶47-54).

U.S. Patent No. 9,715,893 - Recording apparatus, server apparatus, recording method, program and storage medium

  • Patent Identification: U.S. Patent No. 9,715,893, “Recording apparatus, server apparatus, recording method, program and storage medium,” issued July 25, 2017 (Compl. ¶58).
  • Technology Synopsis: This patent describes a system for efficiently synchronizing data between two storage mediums. The invention involves automatically reading management data from both the source and destination, identifying which source files are "absent from the second storage medium," automatically transferring only those absent files, and then outputting the transfer status using a "symbolic figure" for user feedback. (’893 Patent, Abstract).
  • Asserted Claims: Claim 32 (Compl. ¶60).
  • Accused Features: The complaint alleges that Barracuda's backup systems infringe by automatically identifying files on a source that are absent from a destination storage medium (source-based deduplication), transferring only the absent data, and displaying the transfer status to the user (Compl. ¶¶65-68).

III. The Accused Instrumentality

Product Identification

  • The accused instrumentalities are Barracuda Backup Physical Appliance Models (e.g., 190, 295, etc.), Barracuda Backup Virtual Appliances, and the Barracuda Cloud service (Compl. ¶8).

Functionality and Market Context

  • The complaint describes the accused products as forming an "all-in-one data protection solution" for businesses (Compl. ¶12). The system allows users to back up data from various sources (e.g., physical servers, virtual environments, Microsoft Office 365) to a local physical or virtual Barracuda Backup appliance. This data can then be replicated to an off-site location, such as the Barracuda Cloud, Amazon Web Services (AWS), or another backup appliance, to protect against local disasters and data loss (Compl. ¶12, ¶14). A key feature alleged is the use of deduplication to compare data on the source and destination to transmit only new or changed information, thereby minimizing bandwidth and storage usage (Compl. ¶20). The complaint includes a diagram illustrating this architecture, showing data flowing from sources to backup appliances and then replicating to cloud or other long-term retention targets (Compl. p. 7).

IV. Analysis of Infringement Allegations

'7,720,929 Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
a communication system comprising: a first apparatus having a first storage medium, and a second apparatus... The system comprises Barracuda Backup appliances and cloud storage ("first apparatus") and clients like mobile or desktop devices ("second apparatus") (Compl. ¶14, ¶15). ¶14, ¶15 col. 3:4-6
a second storage medium configured to store management information of data to be transferred... Client devices include storage media and a "BackUp Agent" configured to synchronize selected folders, which constitutes storing management information (Compl. ¶15). ¶15 col. 3:8-10
a detector configured to detect whether said first apparatus and said second apparatus are connected... The system includes a detector to determine if network connectivity is online between the client and the backup target (Compl. ¶17). A provided screenshot shows a target's status as "Online" (Compl. p. 9). ¶17 col. 4:33-36
an editor configured to select certain data to be transferred and to edit said management information...without regard to the connection of said first apparatus... The system provides an interface for users to select folders or files to synchronize, and this selection can be done regardless of the connection status to the backup appliance (Compl. ¶18). ¶18 col. 4:37-41
a controller configured to control transfer of the selected data...when said detector detects that said first apparatus and said second apparatus are connected... The system transfers the selected files to the backup appliance or cloud service when it determines the devices are connected (Compl. ¶19). A diagram shows data replication to various targets (Compl. p. 12). ¶19 col. 4:42-47
wherein said controller is configured to compare said management information...with management information of data stored in said first storage medium and to transmit data...based on the results of the comparison. The system uses deduplication to compare information to be transmitted with information already stored on the backup appliance and transmits only the data that has not already been sent (Compl. ¶20). A diagram illustrates source-based deduplication (Compl. p. 15). ¶20 col. 4:48-54

'8,386,581 Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
a communication apparatus comprising: a storage unit configured to store content data to a storage medium... The accused system includes Barracuda Backup appliances and replication zones (e.g., Barracuda Cloud, AWS) that have storage media for storing backup data (Compl. ¶32). ¶32 col. 3:26-28
a communication unit configured to communicate with an external apparatus... The system can "replicate data securely from an on-premises physical or virtual backup appliance to Barracuda Cloud, a remote physical appliance, a remote virtual appliance, or Amazon Web Services (AWS)" (Compl. ¶33). ¶33 col. 3:28-29
a controller configured to edit a list so that content data is registered in the list... The system allows a user to select files and folders for backup, which constitutes editing a list of content data to be transferred (Compl. p. 21, ¶15). ¶15 (re-alleged), ¶35 col. 3:30-31
to uniquely associate the list with the external apparatus using a unique identification of the external apparatus... The system provides a "unique icon and name for every storage medium that is being backed up and for each backup storage medium" (Compl. ¶34). A screenshot shows distinct replication targets such as "Receiver Vx (ATL)" and "Barracuda Cloud" (Compl. p. 21). ¶34 col. 3:31-33
to extract the list associated with the external apparatus from a plurality of lists...when the external apparatus is connected... The complaint alleges the system monitors and controls the transfer of data from the client device to the backup storage based on user selections (Compl. ¶35). ¶35 col. 3:33-37
and to control transferring of content data registered in the extracted list to the external apparatus. The system controls the transfer of content selected by the user to the designated backup location (Compl. ¶35). ¶35 col. 3:37-39

Identified Points of Contention

  • Scope Questions: A central question for the '929, '581, and '751 patents may be whether the term "apparatus," which the patents describe in the context of discrete consumer electronics like a music server and a portable player, can be construed to read on the accused distributed, client-server architecture of enterprise backup software agents, appliances, and cloud services. Another scope question for the ’581 Patent is whether a user-facing "icon and name" for a backup target in a software interface meets the claim requirement of "uniquely associate[ing] the list with the external apparatus using a unique identification."
  • Technical Questions: For the ’929 and ’751 patents, a technical question is whether the accused system's data deduplication process, which typically involves comparing cryptographic hashes of data blocks, performs the specific function of "compar[ing] said management information...with management information of data stored in said first storage medium" as required by the claims, or if there is a fundamental operational difference.

V. Key Claim Terms for Construction

The Term: "apparatus" (from ’929 Patent, Claim 1 and others)

  • Context and Importance: The infringement theory depends on casting the distributed components of the Barracuda system (clients, local appliances, cloud services) as the claimed "first apparatus" and "second apparatus." The construction of this term will determine if the claims can map onto the accused product architecture.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification discloses communication between apparatuses via an "Internet server" and a "public telephone line," which suggests the apparatuses need not be physically co-located or of a specific hardware type, potentially supporting application to a distributed software and cloud system (’929 Patent, col. 5:50-61).
    • Evidence for a Narrower Interpretation: The patent’s figures and primary embodiments consistently depict two distinct, self-contained physical devices: a "music server" and a "portable recording and playback apparatus" (’929 Patent, FIG. 1, FIG. 11), which could support a narrower construction limited to discrete hardware units.

The Term: "management information" (from ’929 Patent, Claim 1 and others)

  • Context and Importance: Infringement requires the accused system's deduplication to be a comparison of "management information." Practitioners may focus on this term because deduplication often compares data content (via hashes) rather than what is traditionally considered management information (e.g., file names, dates, sizes, or a list thereof).
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent does not narrowly define the term. It is described as "management information of data to be transferred" and is something that can be edited by an "editor" based on data selection, which could arguably be interpreted broadly to include any metadata or pointers used to manage the transfer, potentially including the hash identifiers used in deduplication. (’929 Patent, col. 3:8-14).
    • Evidence for a Narrower Interpretation: The detailed description discusses "management information" in the context of a user-editable "transfer list" containing "titles of musical data" (’929 Patent, FIG. 10; col. 11:36-44), suggesting it refers to metadata about the files themselves, not hashes of their underlying data content.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges both induced and contributory infringement for all asserted patents. Inducement is alleged based on Defendant’s user manuals, marketing materials, product support, and demonstrations that allegedly instruct customers to use the accused products in an infringing manner (Compl. ¶12, ¶30, ¶45, ¶63). Contributory infringement is alleged on the basis that the accused products' components are especially made for infringing use and are not staple articles of commerce (Compl. ¶13, ¶31, ¶46, ¶64).
  • Willful Infringement: The complaint alleges that Defendant has had knowledge of the asserted patents since at least the filing of an "original Complaint," establishing a basis for potential post-suit willful infringement (Compl. ¶10, ¶28, ¶43, ¶61). It further alleges that Defendant acted with knowledge or "willful blindness to the probability, that the induced acts would constitute infringement" (Compl. ¶12, ¶26, ¶45, ¶63).

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

  • A core issue will be one of definitional scope: can the term "apparatus," rooted in the patent family's original context of discrete consumer electronic devices like a music server and a portable player, be construed to cover the components of a distributed, enterprise-grade data backup system composed of software agents, on-premises appliances, and cloud infrastructure?
  • A key technical question will be one of operational equivalence: does the accused products' data deduplication functionality, which typically compares hashes of data content, constitute the claimed act of "compar[ing]...management information," or is there a fundamental mismatch in the technical operation that places it outside the scope of the claims?
  • A central question for the ’581 Patent will be one of structural correspondence: does a named replication target within a software graphical user interface meet the claim limitation of a "unique identification" used to "uniquely associate" a transfer list with an external apparatus, as that structure is described in the patent?