DCT

1:26-cv-02880

Ubqs IP LLC v. Atlassian Corp

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:26-cv-02880, S.D.N.Y., 04/08/2026
  • Venue Allegations: Plaintiff alleges venue is proper because Defendant maintains a regular and established place of business in the Southern District of New York and has committed the alleged acts of infringement in the district.
  • Core Dispute: Plaintiff alleges that Defendant's collaborative editing software infringes a patent related to methods for sharing and synchronizing a document among a group of users in a decentralized manner.
  • Technical Context: The technology concerns systems for collaborative work, where multiple users can edit a shared document, a domain central to modern enterprise and team productivity software.
  • Key Procedural History: The complaint discloses that Plaintiff is a non-practicing entity and that it and its predecessors-in-interest have previously entered into settlement licenses with other entities concerning its patents.

Case Timeline

Date Event
2005-02-08 U.S. Patent No. 7,313,580 Priority Date
2007-12-25 U.S. Patent No. 7,313,580 Issue Date
2026-01-23 Assignment of U.S. Patent No. 7,313,580 Recorded
2026-03-26 U.S. Patent No. 7,313,580 Expiration Date (as alleged)
2026-04-08 Complaint Filing Date

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

U.S. Patent No. 7,313,580 - "Systems and Methods for Sharing Information between a User Group and Associated Document"

  • Patent Identification: U.S. Patent No. 7,313,580, titled "Systems and Methods for Sharing Information between a User Group and Associated Document," issued on December 25, 2007.

The Invention Explained

  • Problem Addressed: The patent background describes conventional client-server frameworks for project collaboration as having high requirements for physical and computational resources, as well as for qualified technical personnel to manage the system ʼ580 Patent, col. 1:25-33 The patent identifies a need for a "distributed information framework without the need for a project management server" ʼ580 Patent, col. 1:65-col. 2:2
  • The Patented Solution: The invention describes a decentralized method for document sharing where each member of a user group possesses an identical local copy of a shared document ʼ580 Patent, col. 2:14-16 When a user modifies their local copy, the changes are packaged and shared with the rest of the group following a "synchronization stage," which updates all other copies ʼ580 Patent, abstract This process is initiated when a user "issues the synchronization order" and is designed to function without reliance on a dedicated client-server architecture, for example, by using electronic mail as a transport mechanism ʼ580 Patent, col. 2:29-32 ʼ580 Patent, col. 6:20-22
  • Technical Importance: The described approach sought to enable collaborative work with lower infrastructure overhead by leveraging peer-to-peer communication principles instead of a centrally managed server architecture ʼ580 Patent, col. 2:29-32

Key Claims at a Glance

  • The complaint asserts infringement of one or more of claims 1-20 Compl. ¶9 The independent claims are 1 and 12.
  • Independent Claim 1 recites a method for sharing information comprising the steps of:
    • Providing decentralized storage of a shared document where each user has a copy.
    • Allowing users to make changes to their local copy.
    • Synchronizing the document through a series of stages, including:
      • Saving new information into a local storage unit and an "information packet" available in a "spooler or waiting area."
      • Issuing a "synchronization order" to encode, package, and sequence the packet data for a transport manager.
      • Sending the encoded packets from the spooler to other users.
      • Receiving and decoding the packets at other users' computers.
      • Generating resources to update the document from the decoded packet.
      • Processing the document so that all users have an exact copy after the synchronization is complete.
  • Independent Claim 12 recites "[t]he electronic document to be shared according to the method" of the other claims, wherein the document includes elements such as a group identifier, a list of users, a viewing structure, a group of objects, and storage space.

III. The Accused Instrumentality

Product Identification

  • The complaint identifies the accused instrumentality as a "system with methods and user interface that allow collaborative editing for multiple people to concurrently edit a single page or blog post" Compl. ¶9 Specific Atlassian product names are not provided.

Functionality and Market Context

  • The relevant functionality is the system's capacity to enable multiple users to edit a single document concurrently Compl. ¶9 The complaint does not provide further technical details on the operation of the accused system or its market positioning.

IV. Analysis of Infringement Allegations

The complaint alleges that Defendant's system for concurrent, collaborative editing directly infringes one or more claims of the '580 Patent Compl. ¶9 Compl. ¶11 Specific support for these allegations is said to be contained in an attached claim chart (Exhibit B), which was not provided with the complaint document itself Compl. ¶10 The body of the complaint does not contain a detailed mapping of the accused system's features to the specific limitations of any asserted claim.

No probative visual evidence provided in complaint.

  • Identified Points of Contention:
    • Scope Questions: A central dispute may arise over the meaning of "decentralized storage." The patent's specification describes the invention as "avoiding the use of a dedicated client-server structure" ʼ580 Patent, abstract The infringement analysis may therefore turn on whether Defendant's system, which is generally understood to operate on a client-server model, can be considered to have "decentralized storage" if users maintain local or cached copies of documents that are synchronized with a central server.
    • Technical Questions: The complaint does not explain how the accused collaborative editing system performs the specific, multi-stage synchronization process of claim 1. This raises the question of what evidence will be offered to show that the accused system's functionality corresponds to a user "issu[ing] a synchronization order" and utilizing a "spooler or waiting area for data to sent" ʼ580 Patent, col. 9:46-48, as distinct from the continuous or automatic saving and updating processes common in modern collaborative software.

V. Key Claim Terms for Construction

  • The Term: "decentralized storage" (from claim 1)

    • Context and Importance: This term is foundational to the patent's stated departure from prior art client-server models. Its construction will be critical to determining whether the patent's scope covers modern, cloud-based collaborative platforms.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: A party may argue that any system where users maintain local copies or caches of a document, even if synchronized with a central server, practices "decentralized storage." The claim language itself does not explicitly forbid a server's existence.
      • Evidence for a Narrower Interpretation: A party may argue that the specification defines the term by distinguishing it from a client-server system. Language such as "avoiding the use of a dedicated client-server structure" ʼ580 Patent, abstract and the background's critique of the client-server framework ʼ580 Patent, col. 1:25-33 could be cited to argue that "decentralized storage" requires the absence of a central, authoritative document server.

  • The Term: "a synchronization order is issued" (from claim 1)

    • Context and Importance: This phrase appears to define a discrete, active step in the claimed method. Its interpretation will be central to comparing the patented method with the update mechanisms of the accused system.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: This could be construed to cover any user action or automated process that triggers the sharing of changes, such as an auto-save function or navigating away from an editing field.
      • Evidence for a Narrower Interpretation: The specification states that when a user "decides to share information or modifications... he issues the synchronization order" ʼ580 Patent, col. 6:20-22 This language suggests a deliberate, user-initiated command to begin the process of packaging and sending accumulated local changes, as opposed to a continuous or automatic background process.

VI. Other Allegations

  • Willful Infringement: The complaint makes a contingent allegation of willfulness, requesting a finding of willful infringement and enhanced damages should discovery reveal that Defendant knew of the '580 patent and its infringement prior to the lawsuit Compl. p. 6, prayer e

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

  • A core issue will be one of architectural scope: can the claim term "decentralized storage," which the patent describes as part of a solution that "avoid[s] the use of a dedicated client-server structure," be construed to cover the architecture of Defendant's server-based collaborative software? The resolution may depend on whether the patent's repeated contrasts with client-server models are treated as a defining limitation of the claims or merely as a description of one embodiment's benefits.
  • A key evidentiary question will be one of procedural equivalence: does the accused system's method for updating documents, which likely involves continuous and automated syncing, perform the discrete, user-initiated, multi-stage process recited in claim 1, including the specific steps of issuing a "synchronization order" and using a "spooler"? The complaint does not provide the specific facts necessary to evaluate this potential operational mismatch.
Loading Complaint