7:25-cv-00116
Secure Matrix LLC v. Twin Liquors LP
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Secure Matrix LLC (DE)
- Defendant: Twin Liquors LP (TX)
- Plaintiff’s Counsel: Rabicoff Law LLC
- Case Identification: 7:25-cv-00116, W.D. Tex., 04/30/2025
- Venue Allegations: Plaintiff alleges venue is proper because Defendant has an established place of business within the Western District of Texas.
- Core Dispute: Plaintiff alleges that Defendant infringes a patent related to systems and methods for authenticating users for secure online interactions.
- Technical Context: The lawsuit concerns multi-factor authentication technology used to secure access to digital systems, a critical component of e-commerce and online security.
- Key Procedural History: The complaint alleges that Defendant gained actual knowledge of the patent-in-suit and the infringement allegations upon service of an original complaint on March 12, 2025, which may form the basis for a post-suit willfulness claim.
Case Timeline
| Date | Event |
|---|---|
| 2012-11-21 | '116 Patent Priority Date |
| 2013-08-09 | '116 Patent Application Filed |
| 2014-03-18 | '116 Patent Issue Date |
| 2025-03-12 | Original Complaint Filed |
| 2025-04-30 | First Amended Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 8,677,116 - “Systems and methods for authentication and verification”
- Patent Identification: U.S. Patent No. 8,677,116, issued March 18, 2014 (the “’116 Patent”).
The Invention Explained
- Problem Addressed: The patent and complaint describe conventional authentication methods as being vulnerable to security breaches and inconvenient for users, who had to remember numerous complex passwords for different websites, leading to high customer support costs for businesses (Compl. ¶¶10-12; ’116 Patent, col. 1:20-29).
- The Patented Solution: The invention is a multi-factor authentication system. A computer providing a secure service (e.g., a web server) sends a "reusable identifier" to both a user's device and a central verification server. The user's device (e.g., a smartphone) receives the identifier (e.g., by scanning a QR code), combines it with "user verification information," and sends this combined package to the verification server. The verification server then evaluates both signals to determine if the user is authorized (’116 Patent, Abstract; ’116 Patent, col. 6:4-33). This process aims to create a universal login system that enhances security without relying on traditional passwords (Compl. ¶15).
- Technical Importance: The complaint asserts that this approach provides "a level of safety over a million times greater than systems that utilize just a login and password" by creating a time-sensitive, multi-channel verification process (’116 Patent, col. 33:3-4; Compl. ¶16).
Key Claims at a Glance
- The complaint asserts infringement of Claim 1 of the ’116 Patent (Compl. ¶22).
- Independent Claim 1 requires a method of using a computer system to authenticate a user, comprising the steps of:
- using the computer system to receive a first signal from the computer providing the secured capability, the first signal comprising a reusable identifier... assigned for use... for a finite period of time;
- using the computer system to receive a second signal from an electronic device being used by the user, the second signal comprising a copy of the reusable identifier and user verification information;
- using a processor of the computer system to evaluate, based at least on the first signal and the second signal, whether the user is authorized...; and
- in response to an indication from the processor that the user is authorized..., using the computer system to transmit a third signal comprising authorization information...
- The complaint reserves the right to assert other claims, referring to the "Exemplary '116 Patent Claims" (Compl. ¶25).
III. The Accused Instrumentality
The complaint does not provide sufficient detail for analysis of the accused instrumentality. It refers to "Exemplary Defendant Products" that are identified in claim charts attached as Exhibit 2 (Compl. ¶25, ¶30). However, Exhibit 2 was not filed with the complaint. The complaint alleges in general terms that Defendant makes, uses, sells, and internally tests products that practice the claimed technology (Compl. ¶¶25-26).
IV. Analysis of Infringement Allegations
The complaint alleges infringement but does not contain a claim chart or specific factual allegations mapping product features to claim elements, instead incorporating by reference an unfiled Exhibit 2 (Compl. ¶31). The narrative infringement theory alleges that Defendant’s products practice the inventive concepts of the ’116 Patent as recited in Claim 1 (Compl. ¶22). Specifically, the complaint alleges Defendant’s systems use a "time-limited reusable identifier" to prevent replay attacks and provide a multi-factor authentication approach that improves upon conventional systems (Compl. ¶¶20-21).
No probative visual evidence provided in complaint.
- Identified Points of Contention:
- Evidentiary Question: A threshold issue for the court will be identifying the accused products and their specific functionalities, as the complaint lacks this detail. The analysis will depend entirely on evidence produced during discovery that shows how Defendant's authentication systems operate.
- Scope Questions: The dispute may turn on the scope of several key terms. For instance, what constitutes a "reusable identifier" that is "assigned for use... for a finite period of time"? The analysis will question whether the accused system's tokens, if any, meet this specific temporal and functional limitation as described in the patent.
- Technical Questions: A key technical question will be whether the accused system performs the claimed method. Specifically, does it receive two distinct signals—one from the service provider and one from the user's device, containing the specified information—and evaluate them at a central verification system as required by Claim 1?
V. Key Claim Terms for Construction
The Term: "reusable identifier... assigned for use... for a finite period of time" (Claim 1)
Context and Importance: This term is the technological core of the claim, distinguishing the invention from both static passwords and "one-time-use" tokens. The infringement analysis will depend on whether the accused system's authentication tokens are "reusable" yet also time-limited in the manner claimed. Practitioners may focus on this term because its construction will determine whether a wide range of modern authentication tokens fall within the claim's scope.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification describes the identifier as not containing "user-specific or transaction-specific information," which could support a broad reading covering any generic, time-limited token used to initiate an authentication session (’116 Patent, col. 6:36-42).
- Evidence for a Narrower Interpretation: The specification provides specific examples, such as identifiers that are valid for "one or more minutes, one or more hours, one or more days" and are used in a "round robin" fashion where they are deactivated and later reused (’116 Patent, col. 9:42-54; col. 13:43-47). The complaint emphasizes this time-sensitive nature as a way to prevent replay attacks, suggesting a specific security function beyond mere expiration (Compl. ¶20-21).
The Term: "user verification information" (Claim 1)
Context and Importance: This term defines the second factor in the claimed multi-factor authentication scheme. The case may hinge on whether the information provided by the user's device in the accused system qualifies as "verification information" separate from the "reusable identifier."
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification gives a wide range of examples, including information "specific to the user" (e.g., name, email address) or "specific to the first electronic device" (e.g., a device ID string, hardware-specific information) (’116 Patent, col. 12:5-14). This could support an interpretation covering many different types of secondary data.
- Evidence for a Narrower Interpretation: The objective of providing a "verifiable 'fingerprint' of the user and mobile device" could suggest a narrower construction requiring information that uniquely and securely identifies the device or user, rather than generic data that could be easily replicated (’116 Patent, col. 12:6-7).
VI. Other Allegations
- Indirect Infringement: The complaint alleges induced infringement, stating that Defendant distributes "product literature and website materials" that instruct customers and end-users on how to use the accused products in a manner that infringes the ’116 Patent (Compl. ¶28, ¶29).
- Willful Infringement: The willfulness allegation is based on post-suit conduct. Plaintiff alleges that Defendant had "actual knowledge" of its infringement at least as of the service of the original complaint on March 12, 2025, and continued to infringe despite this knowledge (Compl. ¶27-28).
VII. Analyst’s Conclusion: Key Questions for the Case
- A primary issue will be one of evidence: given the complaint's lack of specificity, the case will depend on whether discovery reveals an accused system that performs the precise, multi-step authentication protocol recited in Claim 1. The absence of this information in the pleading stage raises a significant hurdle for assessing the merits of the infringement claim.
- The case will also turn on claim construction: can the term "reusable identifier... assigned for use... for a finite period of time" be construed to read on the specific type of authentication tokens used by Defendant's system? The outcome will likely depend on whether the accused tokens are merely ephemeral or if they operate within a time-limited, reusable framework as described in the patent's "round robin" embodiment.
- A final key question involves infringement mapping: does the accused system architecturally separate the required signals and evaluation steps? The court will need to determine if the system truly uses a central processor to evaluate a "first signal" from a service computer and a "second signal" from a user device, or if it employs a different, non-infringing authentication architecture.