Lone Star Document Management LLC v. Getbusy PLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Lone Star Document Management, LLC (Delaware)
  • Defendant: GetBusy plc (England) & GetBusy USA Corporation (Delaware)
  • Plaintiff's Counsel: Devlin Law Firm LLC
• Case Identification: 4:26-cv-05324, S.D. Tex., 07/06/2026
• Venue Allegations: Venue is based on Defendant GetBusy USA Corporation maintaining a "regular and established place of business" in Houston, Texas, within the Southern District of Texas, and allegedly committing acts of infringement in the district.
• Core Dispute: Plaintiff alleges that Defendant's SmartVault document management software infringes a patent related to systems for network-based electronic document proofing, versioning, and comment management.
• Technical Context: The technology addresses collaborative online document review, enabling multiple users to review, comment on, and manage different versions of electronic documents in a centralized, platform-agnostic manner.
• Key Procedural History: The complaint alleges that Plaintiff contacted Defendant with an offer to license the patent-in-suit on May 12, 2017, and that Defendant's counsel responded on May 23, 2017. This correspondence is cited to establish Defendant's pre-suit knowledge of the patent, which may be relevant to a claim of willful infringement.

Case Timeline

Date	Event
1998-12-17	Patent Priority Date ('082 Patent)
2005-07-12	U.S. Patent No. 6,918,082 Issues
2017-05-15	Plaintiff's license offer delivered to Defendant
2026-07-06	Complaint Filed

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

U.S. Patent No. 6,918,082 - "ELECTRONIC DOCUMENT PROOFING SYSTEM"

• Patent Identification: U.S. Patent No. 6,918,082 ("the '082 Patent"), "ELECTRONIC DOCUMENT PROOFING SYSTEM," issued July 12, 2005 Compl. ¶9

The Invention Explained

• Problem Addressed: The patent's background section describes the difficulties in collaborative document proofing that existed at the time of the invention Compl. ¶10 These problems included the need for collaborators to use the same software versions and operating systems, the use of proprietary file formats, and the lack of features for managing multiple document versions or tracking comment history, particularly over a network Compl. ¶16 '082 Patent, col. 1:32-36 '082 Patent, col. 1:50-54 Existing systems for delivering portable documents were said to "fail to provide a way to automatically display or track multiple versions of the electronic documents" or "simultaneously-display a particular document version and its current history" '082 Patent, col. 2:49-59
• The Patented Solution: The '082 Patent discloses a centralized, network-based system to solve these issues Compl. ¶12 The system uses a central computer to receive portable format documents from a creator, store them in a database with associated "proofer identifiers," and manage versioning Compl. ¶19 '082 Patent, abstract Authorized "proofers" can then request to review a document; the system retrieves the document and can format it for display along with a history of associated comments, allowing for simultaneous review of the document and its feedback '082 Patent, col. 4:6-11 '082 Patent, Fig. 1 The system is also designed to handle requests for multiple versions of a document for side-by-side comparison '082 Patent, col. 3:1-4
• Technical Importance: This approach provided a technical framework for a platform-agnostic, collaborative review process, intended to improve the efficiency of document distribution, proofing, and communication between creators and reviewers '082 Patent, col. 6:60-64

Key Claims at a Glance

• The complaint asserts independent claim 10, as modified by dependent claim 16 Compl. ¶¶12, 37
• The essential elements of independent claim 10, on which claim 16 depends, include:
  • A database for storing portable format documents with a "proofer identifier."
  • A computer for receiving comments about the documents.
  • A program for associating and storing those comments with the corresponding documents.
  • The computer receiving a request from an identified "proofer" to review a document.
  • The program retrieving and formatting the document with its associated comments for "simultaneous display."
• Dependent claim 16 adds the limitation that the program "retrieves a record corresponding to the requested document and assembles a URL pointing toward the document from data in the record."
• The complaint's attached claim chart notes that Plaintiff reserves the right to assert other claims of the '082 patent Compl. Ex. 2, p. 3

III. The Accused Instrumentality

Product Identification

• The accused instrumentalities are GetBusy's systems for content management, including the "SmartVault Document Management (DMS) document management solution" Compl. ¶37 Compl. Ex. 2, p. 2

Functionality and Market Context

• The complaint describes the SmartVault DMS as a cloud-based, centralized system for accountants and other professionals to "organize, access, and protect all your firm and client documents" Compl. Ex. 2, p. 4 A diagram provided in the complaint depicts a workflow for client onboarding, document collection, review, and delivery Compl. Ex. 2, p. 4
• Key functionalities alleged to be infringing include cloud storage for documents, role-based access controls for users, secure document sharing via authenticated links, and tools for annotating PDF documents with notes and other marks Compl. Ex. 2, p. 6 Compl. Ex. 2, p. 10 Compl. Ex. 2, p. 11
• The system is also alleged to maintain "Activity logs" and "version history" for documents, allowing users to track changes and access previous versions Compl. Ex. 2, p. 27 Compl. Ex. 2, p. 28 The complaint alleges these features provide significant convenience and efficiency, enhancing customer engagement Compl. ¶14

IV. Analysis of Infringement Allegations

The complaint alleges that the SmartVault DMS infringes at least claim 16 of the '082 patent Compl. ¶37 The infringement theory is detailed in a claim chart provided as Exhibit 2 to the complaint Compl. ¶38

'082 Patent Infringement Allegations

Claim Element (from Independent Claim 10 and Dependent Claim 16)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a database of portable format electronic documents stored together with at least one proofer identifier;	The SmartVault DMS uses a cloud-based database for storing documents, including PDFs. Access is controlled by user authentication and "Role-Based Access Controls," which allegedly function as the claimed "proofer identifier" Compl. Ex. 2, p. 6 Compl. Ex. 2, p. 10	¶37	col. 5:35-38
a computer connectable to the network for receiving a plurality of comments...;	The accused "Connected Desktop" feature allows users to receive and make annotations (comments) on PDF documents over a network. A screenshot shows the user interface for annotating a document (Compl. Ex. 2, p. 11; Compl. Ex. 2, p. 13).	¶37	col. 4:6-9
a program executing on said computer for associating and storing the received plurality of comments together with the... documents;	The SmartVault software allegedly associates and stores the annotations with the specific document in its database, which is part of the "Using Annotations in the Connected Desktop" functionality (Compl. Ex. 2, p. 17).	¶37	col. 3:28-30
said computer for receiving a request, from a proofer presenting the proofer identifier, to review a... document;	A user (proofer) requests a document by using a permission-based link or logging into the system, which requires authentication ("presenting the proofer identifier") to gain access (Compl. Ex. 2, p. 23).	¶37	col. 3:20-23
said program for retrieving and formatting the requested document together with the associated plurality of comments for simultaneous display...;	SmartVault's "Activity logs" and "version history" features are alleged to retrieve and display a document along with its associated history of comments and versions for review Compl. Ex. 2, p. 27 A screenshot shows the "Version history" interface (Compl. Ex. 2, p. 29).	¶37	col. 4:9-11
said program retrieves a record corresponding to the requested document and assembles a URL pointing toward the document from data in the record.	The "Get Link" feature in SmartVault generates a unique URL that points to a specific document. The complaint alleges this URL is assembled from data in the system's records (Compl. Ex. 2, p. 35). A screenshot shows the interface for generating such a link (Compl. Ex. 2, p. 39).	¶37	col. 5:55-61

• Identified Points of Contention:
  • Scope Questions: A potential dispute may arise over the meaning of "proofer identifier." The defense may argue that a standard user account login is not the specific "proofer identifier" linked to a "client" or "project" as described in an embodiment of the patent '082 Patent, col. 5:35-36 '082 Patent, col. 5:58-61 The question for the court may be whether the term covers any form of user authentication for document access.
  • Technical Questions: The infringement allegation for "simultaneous display" rests on features like "Activity logs" and "version history." A key technical question will be whether displaying a document in one part of a user interface while its comment history is available in another pane or log meets the claim requirement of formatting the document "together with" its comments for "simultaneous display" '082 Patent, col. 10:9-12 Another question is whether SmartVault's method of generating a sharing link constitutes the specific URL "assembly" process described in the patent's specification ('082 Patent, col. 5:55-61).

V. Key Claim Terms for Construction

• The Term: "proofer identifier"

  • Context and Importance: This term is fundamental to the patent's access control mechanism. Its construction will be critical in determining whether modern, generalized user authentication systems fall within the scope of the claims.
  • Intrinsic Evidence for a Broader Interpretation: The patent states the system receives documents "together with at least one associated proofer identifier" without further restriction in the claim itself, which may support an interpretation that includes any unique user credential '082 Patent, col. 10:2-3
  • Intrinsic Evidence for a Narrower Interpretation: The specification describes a "client" as a "unique group/collection of proofers" and uses a <client> field in its exemplary URL structure '082 Patent, col. 5:35-36 '082 Patent, col. 5:59-60 This may support an argument that the "proofer identifier" must be tied to a specific project or client group structure, not just an individual user.

• The Term: "assembles a URL"

  • Context and Importance: This term is the central limitation of the asserted dependent claim 16. The infringement analysis for this claim will likely hinge on whether the accused product's functionality aligns with the patent's specific teaching of this term.
  • Intrinsic Evidence for a Broader Interpretation: The claim language states the program "assembles a URL pointing toward the document from data in the record," which could be read to encompass any method of dynamically generating a link based on database information '082 Patent, col. 10:48-50
  • Intrinsic Evidence for a Narrower Interpretation: The specification discloses a specific method where the URL is assembled using a hierarchical directory tree structure: <protocol>://<host>/<client>/<project>/<version>/<name>/ '082 Patent, col. 5:58-61 Practitioners may focus on this detailed embodiment to argue that the claim is limited to URLs constructed with this specific, human-readable format, as opposed to opaque, hash-based links common in modern cloud services.

VI. Other Allegations

• Indirect Infringement: The complaint does not include a separate count for indirect infringement, but its allegation that Defendant infringed by "causing to be used" its systems suggests a theory of inducement Compl. ¶37 The factual basis for this appears to be that Defendant provides user-facing tools (like annotation and sharing) and implicitly instructs customers on how to use them in an allegedly infringing manner.
• Willful Infringement: The complaint explicitly alleges that Defendant has had knowledge of the '082 patent since at least May 15, 2017, due to a letter from Plaintiff offering a license Compl. ¶13 This allegation of pre-suit knowledge forms the basis for the claim of willfulness and the request for enhanced damages and attorneys' fees Compl. p. 13, Prayer for Relief C

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

1. Patent Eligibility: The complaint dedicates substantial attention to arguing that claim 16 is patent-eligible under 35 U.S.C. § 101, framing it as a specific improvement to computer functionality rather than an abstract idea Compl. ¶¶27-33 A primary battleground will likely be a defense motion challenging the patent on these grounds, arguing the claims are directed to the abstract idea of organizing and reviewing documents, simply implemented on a generic computer.
2. Definitional Scope: The case will involve a critical analysis of claim construction. A core issue will be one of definitional scope: can terms like "proofer identifier", rooted in a specific client-group context within the patent's examples, be construed broadly enough to encompass the generalized user authentication and role-based access controls of a modern SaaS product?
3. Technical Equivalence: A key evidentiary question will be one of functional equivalence, particularly for claim 16. Does the accused product's generation of a sharing link perform the same function in substantially the same way as the patent's specific disclosure of "assembling" a URL from a hierarchical directory structure (/client/project/version/name)? The degree of similarity between the accused method and the patent's detailed embodiment will be a central point of contention.