Lone Star Document Management LLC v. Feith Systems Software Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Lone Star Document Management, LLC (Delaware)
  • Defendant: Feith Systems and Software, Inc. (Pennsylvania)
  • Plaintiff's Counsel: Devlin Law Firm LLC
• Case Identification: 2:26-cv-04471, E.D. Pa., 06/29/2026
• Venue Allegations: Venue is alleged to be proper in the Eastern District of Pennsylvania because the defendant, Feith, maintains a regular and established place of business within the district.
• Core Dispute: Plaintiff alleges that Defendant's content management systems infringe a patent related to a system for the collaborative proofing of electronic documents over a network.
• Technical Context: The technology concerns network-based systems that allow multiple users to review, comment on, and manage different versions of electronic documents, overcoming platform and software incompatibilities.
• Key Procedural History: The complaint alleges that Plaintiff contacted Defendant on November 13, 2014, with an offer to license the patent-in-suit, putting Defendant on notice of the patent more than a decade before the complaint was filed. The complaint also dedicates significant sections to arguing for the patent eligibility of the asserted claim under 35 U.S.C. § 101, anticipating a potential defense.

Case Timeline

Date	Event
1998-12-17	'082 Patent Priority Date
2005-07-12	'082 Patent Issue Date
2014-11-13	Plaintiff sends license offer letter to Defendant
2026-06-29	Complaint Filing Date

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.

The Invention Explained

• Problem Addressed: At the time of the invention, collaboratively reviewing electronic documents over a network was difficult. It often required all parties to use the exact same software and operating system '082 Patent, col. 1:30-36 Existing systems that used portable document formats to solve platform dependency still lacked the ability to automatically track multiple document versions, manage a history of comments, or allow for the simultaneous display of a document version and its associated commentary '082 Patent, col. 2:49-59 Compl. ¶¶21-22
• The Patented Solution: The patent describes a centralized, network-based system to manage the document proofing lifecycle '082 Patent, abstract A creator uploads a portable format document, which is stored in a database with version numbers and proofer identifiers '082 Patent, col. 3:57-64 Authorized proofers can then request a document for review. The system retrieves the document and its associated comments, formatting them for simultaneous display '082 Patent, col. 4:11-14 A key aspect is the system's methodology for dynamically assembling a URL from database records to locate and display specific document versions '082 Patent, col. 5:10-22
• Technical Importance: The invention aimed to facilitate more efficient electronic document distribution and proofing by centralizing version control and comment history in a platform-agnostic manner, which was crucial for industries like graphic design and law that rely on collaborative review '082 Patent, col. 6:60-64

Key Claims at a Glance

• The complaint asserts independent Claim 10 via its assertion of dependent Claim 16 '082 Patent, col. 10:9-52 Compl. ¶¶37-38
• The essential elements of the system, combining Claim 10 and Claim 16, include:
  • A database for storing portable format electronic documents with a proofer identifier.
  • A computer connected to a network for receiving comments about the documents.
  • A program that associates and stores the comments with their corresponding documents.
  • The computer is configured to receive a request from an identified proofer to review a specific document.
  • The program is configured for retrieving and formatting the requested document together with its associated comments for simultaneous display.
  • 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 does not explicitly reserve the right to assert other claims but notes its infringement analysis is preliminary Compl. ¶38

III. The Accused Instrumentality

Product Identification

The complaint identifies the accused instrumentalities as "Feith products and services identified in Exhibit 2 hereto" and "shown in Exhibit 4 hereto" Compl. ¶37 These exhibits were not attached to the publicly filed complaint. The body of the complaint describes the products generally as "one or more hardware and software products for content management and related services" Compl. ¶37

Functionality and Market Context

• The complaint does not provide specific details on the functionality of the accused Feith products. It alleges in general terms that Feith "implemented their products and services in network architectures having features which utilized the patented invention of at least claim 16" Compl. ¶14
• The complaint alleges these products provide "convenience and efficiency for its customers, enhancing the customer engagement and experience" and have "significant commercial value" Compl. ¶14
• No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint states that an "Exemplary infringement analysis showing infringement of claim 16 of the '082 patent is set forth in Exhibit 2" Compl. ¶38 As this exhibit was not provided, a detailed claim chart analysis is not possible.

The complaint's narrative infringement theory is that Defendant's content management systems and services practice the invention of the '082 patent Compl. ¶37 The allegations suggest that Feith's systems provide a network-based architecture for managing and reviewing documents that incorporates the features recited in Claim 16, thereby infringing the '082 patent Compl. ¶14 The analysis is described as "necessarily preliminary," with Plaintiff reserving the right to amend it after discovery Compl. ¶38

Identified Points of Contention

• Technical Questions: A central factual question will be whether the accused Feith systems perform the specific functions required by the claims. For example, what evidence shows that the accused systems "retrieve and format" a document "together with the associated plurality of comments for simultaneous display" as claimed?
• Scope Questions: The infringement analysis may turn on the interpretation of key claim terms. A likely point of dispute is whether the accused systems "assemble a URL pointing toward the document from data in the record" in the manner contemplated by the patent. The patent describes a specific method of dynamically creating a URL string from database fields (e.g., client, project, name), and a key question will be whether the functionality of the accused products falls within the scope of this limitation '082 Patent, col. 6:25-34

V. Key Claim Terms for Construction

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

• Context and Importance: This limitation is the inventive feature added by dependent Claim 16 and is described in the patent as part of a "unique methodology" '082 Patent, col. 5:10-12 Its construction will be critical to determining infringement, as it defines how the system locates and accesses the document versions. Practitioners may focus on this term because its scope could determine whether the claim reads on modern web application architectures or is limited to the specific implementation described in the patent.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: A party might argue that the term should cover any programmatic generation of a link to a resource based on database information, as the core concept is using record data to create an address.
  • Evidence for a Narrower Interpretation: The specification provides a specific example: "system 50 pastes together as a string the , , , and from the tag and record to assemble on the fly a URL/path to the requested document" '082 Patent, col. 6:27-31 This description of concatenating specific data fields into a string could support a narrower construction limited to this type of dynamic URL formulation.

The Term: "portable format electronic documents"

• Context and Importance: This term defines the type of files the patented system is designed to handle. The defendant may argue its system handles files that do not qualify as "portable format electronic documents," thus avoiding infringement. The construction will determine whether the claim is limited to static, self-contained files or can cover content dynamically rendered in a web browser.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The patent defines these formats as those that "allow a user to view the file, preserving its exact appearance, without need for the original authoring program" '082 Patent, col. 2:1-3 This functional definition could be argued to encompass a wide range of file types, including modern ones not explicitly listed.
  • Evidence for a Narrower Interpretation: The specification provides specific examples from the 1990s, including "Adobe System's Acrobat Portable Document Format, Envoy's portable document format, and FlashPix" '082 Patent, col. 1:60-64 An argument could be made that the term should be construed in light of these examples, limiting its scope to similar self-contained, layout-preserving file formats.

VI. Other Allegations

Willful Infringement

The complaint does not contain a formal count for willful infringement. However, it alleges that Defendant has had knowledge of the '082 patent since at least November 13, 2014, when Plaintiff sent a letter offering to license the patent Compl. ¶13 In its prayer for relief, Plaintiff requests a declaration that the case is "exceptional" and an award of attorneys' fees under 35 U.S.C. § 285 Compl., Prayer C, which is typically predicated on allegations of willful or egregious conduct.

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

1. Patent Eligibility: The complaint proactively argues that Claim 16 is not directed to an abstract idea and recites an inventive concept, improving computer performance Compl. ¶¶27-33 A primary question for the court will be whether the claim, which organizes a human activity (document proofing), is patent-eligible under 35 U.S.C. § 101 or is an abstract idea implemented with conventional computer components.

2. Definitional Scope: The case will likely depend heavily on claim construction. A core issue will be whether the term "assembles a URL... from data in the record," as described in the context of 1998 technology, can be construed to cover the methods used by Defendant's modern content management systems for accessing documents.

3. Evidentiary Sufficiency: As the complaint provides a high-level infringement theory without specific, publicly available evidence mapping product features to claim limitations, a key challenge for the Plaintiff will be to develop sufficient evidence in discovery to prove that the accused Feith systems practice each and every element of the asserted claim, particularly the "simultaneous display" and URL assembly requirements.