Lone Star Document Management LLC v. Ideagen Ltd

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Lone Star Document Management, LLC (Delaware)
  • Defendant: Ideagen, Ltd. (England)
  • Plaintiff's Counsel: BEUSSE SANKS, PLLC; DEVLIN LAW FIRM LLC
• Case Identification: 0:26-cv-62126, S.D. Fla., 08/03/2026
• Venue Allegations: Venue is alleged to be proper in the Southern District of Florida because the Defendant, Ideagen, maintains a regular and established place of business within the district.
• Core Dispute: Plaintiff alleges that Defendant's content management systems and related services infringe a patent related to a system for proofing and managing versions of electronic documents over a network.
• Technical Context: The technology concerns network-based systems for collaborative document review, a foundational element of modern enterprise content management and workflow solutions.
• Key Procedural History: The complaint alleges that Plaintiff's predecessor-in-interest contacted Defendant's predecessor, PleaseTech, Ltd., with an offer to license the patent-in-suit in October 2015. It further alleges that Defendant Ideagen acquired PleaseTech in March 2017 and has had knowledge of the patent since at least that time.

Case Timeline

Date	Event
1998-12-17	Priority Date for U.S. Patent No. 6,918,082
2005-07-12	U.S. Patent No. 6,918,082 Issued
2015-10-07	Plaintiff's predecessor allegedly offered a license to Defendant's predecessor
2015-10-22	Counsel for Defendant's predecessor allegedly responded to license offer
2017-03-23	Defendant Ideagen allegedly acquired PleaseTech, Ltd.
2026-08-03	Complaint Filed

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

U.S. Patent No. 6,918,082 - "Electronic Document Proofing System"

• Issued: July 12, 2005
• Asserted Claims: 16 (dependent on 10)

The Invention Explained

• Problem Addressed: At the time of the invention, collaboratively reviewing electronic documents over a network was difficult Compl. ¶16 Exchanging files often required all parties to use the exact same software version and operating system '082 Patent, col. 1:32-36 Existing systems that used portable document formats to solve platform dependency issues still lacked capabilities for managing multiple document versions, tracking comment histories, and allowing for simultaneous display of a document version and its associated comments '082 Patent, col. 2:49-59 Compl. ¶22
• The Patented Solution: The patent describes a centralized system for managing the proofing of electronic documents over a network '082 Patent, abstract A central computer receives document versions in a portable format, stores them in a database with associated "proofer identifiers," and assigns version numbers '082 Patent, col. 3:12-23 Proofers can then request a document, and the system retrieves and formats the document-along with its associated history of comments-for simultaneous display, facilitating review '082 Patent, col. 3:25-29 A key aspect is a "unique methodology for storing files" that uses a directory hierarchy to track versions and dynamically assembles a URL to display the requested document version to a proofer '082 Patent, col. 5:10-22
• Technical Importance: The invention aimed to solve persistent problems in network-based document collaboration by creating a unified system to manage versioning, commenting, and display, which was described as an improvement over then-existing, more fragmented methods Compl. ¶¶16-17

Key Claims at a Glance

• The complaint asserts claim 16 of the '082 Patent Compl. ¶37 Claim 16 depends on independent claim 10.
• The essential elements of independent claim 10 are:
  • a database of portable format electronic documents stored together with at least one proofer identifier;
  • a computer connectable to the network for receiving a plurality of comments, each concerning a particular one of the portable format documents;
  • a program executing on said computer for associating and storing the received plurality of comments together with the particular portable format electronic documents;
  • said computer for receiving a request, from a proofer presenting the proofer identifier, to review a particular portable format electronic document;
  • said program for retrieving and formatting the requested document together with the associated plurality of comments for simultaneous display to permit review.
• 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."

III. The Accused Instrumentality

Product Identification

• The complaint identifies the accused instrumentalities as "Ideagen systems, including one or more hardware and software products for content management and related services" Compl. ¶37 The complaint refers to, but does not include, Exhibits 2 and 4 for further identification Compl. ¶37

Functionality and Market Context

• The complaint alleges that Ideagen implemented products and services in network architectures that utilize the patented invention Compl. ¶14 The functionality is described in terms of a system that includes a database of documents, receives comments, associates comments with documents, receives requests from users to review documents, and retrieves and formats documents and comments for display (Compl. ¶¶23; Compl. ¶25; Compl. ¶28). The complaint alleges these features provide "convenience and efficiency for its customers" Compl. ¶14

No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint references an infringement analysis in an exhibit that was not provided Compl. ¶38 The following chart summarizes the infringement allegations for claim 10 and its asserted dependent claim 16, as constructed from the narrative descriptions within the complaint.

'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 complaint alleges a system that includes a database of portable format electronic documents stored with a proofer identifier.	¶28	col. 3:12-23
a computer connectable to the network for receiving a plurality of comments, each concerning a particular one of the portable format documents;	The complaint alleges a system with a computer connectable to a network for receiving comments on the portable format documents.	¶28	col. 4:6-11
a program executing on said computer for associating and storing the received plurality of comments together with the particular portable format electronic documents;	The complaint alleges a system with a program for associating and storing the received comments with the particular documents.	¶28	col. 4:6-11
said computer for receiving a request, from a proofer presenting the proofer identifier, to review a particular portable format electronic document;	The complaint alleges the system's computer is configured to receive a request from a proofer to review a document.	¶28	col. 3:66-4:2
said program for retrieving and formatting the requested document together with the associated plurality of comments for simultaneous display to permit review.	The complaint alleges the system's program retrieves and formats the requested document with its comments for simultaneous display.	¶28	col. 3:25-29
(from Claim 16) ...wherein said program retrieves a record corresponding to the requested document and assembles a URL pointing toward the document from data in the record	The complaint alleges the system's program is configured to retrieve a record for a document and assemble a URL pointing toward it from data in that record.	¶28	col. 6:25-34

Identified Points of Contention

• Scope Questions: The complaint's infringement theory appears to rely heavily on the specific URL assembly method recited in dependent claim 16 Compl. ¶29 A central question will be whether the accused Ideagen systems "assemble a URL pointing toward the document from data in the record" in a manner consistent with the patent's disclosure, which describes a specific methodology using a hierarchical directory structure generated from document information '082 Patent, col. 5:10-22
• Technical Questions: A factual dispute may arise over whether the accused systems perform "simultaneous display" of a document and its associated comments as required by claim 10. The complaint asserts this capability Compl. ¶28, but its implementation in the accused products relative to the patent's description will be a key point of evidence.

V. Key Claim Terms for Construction

The Term: "assembles a URL pointing toward the document from data in the record"

• Context and Importance: This term is the sole additional limitation of asserted claim 16 and is highlighted by the complaint as an "unconventional" feature Compl. ¶29 Its construction will be critical to infringement, as the Plaintiff's theory appears to center on this specific technical implementation. Practitioners may focus on this term because the patent describes it as part of a "unique methodology" involving a "dynamic interaction between 3 types of entities: a relational database, a directory tree file storage system, and URL strings" '082 Patent, col. 5:17-22
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: Parties advocating for a broader scope may argue that the claim language itself does not require the specific three-entity interaction mentioned in the specification, but more generally covers any process of dynamically creating a URL from record data.
  • Evidence for a Narrower Interpretation: Parties advocating for a narrower scope may point to the detailed description of the "storage methodology" as the only disclosed embodiment for performing this function, arguing that the claim should be limited to that specific implementation '082 Patent, col. 5:10-22 The patent states this methodology "enables system 50 to keep track of numerous versions of numerous documents" and that the "directory hierarchy is generated from information about a particular document and is also used to formulate the URL" '082 Patent, col. 5:12-18

The Term: "portable format electronic documents"

• Context and Importance: This term defines the object of the entire claimed system. The patent's background distinguishes "portable document formats" from proprietary formats that create platform-dependency issues '082 Patent, col. 1:50-59 The definition of what constitutes a "portable format" in the context of the accused system will be important for determining the scope of infringement.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: A party could argue the term should be given its plain and ordinary meaning, covering any file format designed to be viewable independent of the authoring software or platform. The specification gives examples but does not appear to limit the term to them '082 Patent, col. 1:59-64
  • Evidence for a Narrower Interpretation: A party might argue that the context requires a format that, like the examples given (Adobe Acrobat, Envoy, FlashPix), preserves the "exact appearance" and "original visual and print integrity" of the source file '082 Patent, col. 1:59-col. 2:6

VI. Other Allegations

Indirect Infringement

• The complaint does not contain a specific count for indirect infringement, but alleges Defendant is liable for "causing to be used Ideagen systems" Compl. ¶37 The complaint does not, however, plead specific facts regarding inducement, such as referencing user manuals or instructions.

Willful Infringement

• The complaint alleges that Defendant Ideagen has had knowledge of the '082 patent since at least March 23, 2017, the date it allegedly acquired PleaseTech, Ltd. Compl. ¶13 This allegation of pre-suit knowledge is based on a 2015 letter offering a license to PleaseTech Compl. ¶13 This forms the basis for a potential willfulness claim.

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

1. A core issue will be one of technical implementation: does the accused Ideagen system "assemble a URL" using "data in the record" as recited in claim 16 and disclosed in the patent's "unique methodology," or does it employ a different, non-infringing architecture for locating and serving documents?
2. A second central question will be one of claim scope: can the term "portable format electronic document" be construed to cover the file types managed by the accused systems, and does the evidence show that those systems provide for the "simultaneous display" of documents and comments as required by the base independent claim?
3. An evidentiary question regarding willfulness will turn on whether Plaintiff can prove that Ideagen had the requisite knowledge of the '082 patent and infringement, stemming from the alleged pre-acquisition notice to its predecessor, PleaseTech, Ltd.