7:25-cv-00134
Secure Matrix LLC v. Abatix Corp
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Secure Matrix LLC (Delaware)
- Defendant: Abatix Corp. (Delaware)
- Plaintiff’s Counsel: Rabicoff Law LLC
- Case Identification: 7:25-cv-00134, W.D. Tex., 03/21/2025
- Venue Allegations: Plaintiff alleges venue is proper because Defendant has an established place of business in the Western District of Texas and has committed acts of infringement in the district.
- Core Dispute: Plaintiff alleges that Defendant’s unspecified products infringe a patent related to methods for authenticating a user via a mobile device interacting with a computer system.
- Technical Context: The technology concerns secure user authentication, particularly for online services and payments, using a multi-device process to separate the presentation of a credential from its verification.
- Key Procedural History: The complaint does not mention any prior litigation, inter partes review proceedings, or licensing history related to the patent-in-suit. The complaint asserts that its service establishes actual knowledge for the purpose of ongoing and willful infringement.
Case Timeline
| Date | Event |
|---|---|
| 2012-11-21 | Earliest Priority Date for ’116 Patent |
| 2014-03-18 | U.S. Patent No. 8,677,116 Issues |
| 2025-03-21 | Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
- Patent Identification: U.S. Patent No. 8,677,116, "Systems and methods for authentication and verification", issued March 18, 2014.
The Invention Explained
- Problem Addressed: The patent identifies a "growing need to authenticate users" for secure internet portals, real-world devices, and online payments, seeking a method that is both secure and fast ('116 Patent, col. 1:19-29).
- The Patented Solution: The invention describes a three-party authentication system. A first computer (e.g., a web server) provides a "reusable identifier" (e.g., a QR code) to a user. A user's separate electronic device (e.g., a smartphone) captures this identifier and transmits it, along with "user verification information," to a distinct verification server. This verification server then evaluates the two signals to determine if the user is authorized and, if so, transmits an authorization signal to the first computer and/or the user's device to grant access ('116 Patent, Abstract; col. 6:4-33; Fig. 3A).
- Technical Importance: The system's use of a "reusable identifier" that does not contain user-specific or transaction-specific data is described as an advantage over conventional systems, suggesting it is simpler, faster to process, and enhances security by not transmitting sensitive data in the initial step ('116 Patent, col. 6:34-62).
Key Claims at a Glance
The complaint does not specify which claims are asserted, instead referring to "Exemplary '116 Patent Claims" identified in an unprovided exhibit (Compl. ¶11). The first independent method claim, Claim 1, includes the following essential elements:
- Using a computer system to receive a first signal from a computer that provides a secured capability, where the signal contains a "reusable identifier" assigned for a "finite period of time."
- Using the computer system to receive a second signal from a user's electronic device, where this second signal contains a copy of the reusable identifier and "user verification information."
- Using a processor to evaluate, based on the first and second signals, whether the user is authorized.
- Transmitting a third signal with "authorization information" to the user's device and/or the first computer in response to a successful evaluation.
III. The Accused Instrumentality
Product Identification
The complaint does not identify any specific accused products or services by name. It refers generally to "Defendant products" and "Exemplary Defendant Products" that are purportedly detailed in "charts incorporated into this Count" (Compl. ¶11). These charts were filed as Exhibit 2 and are not publicly available with the complaint.
Functionality and Market Context
The complaint does not provide sufficient detail for analysis of the accused instrumentality's specific functionality or market context. It alleges in conclusory fashion that the accused products "practice the technology claimed by the '116 Patent" (Compl. ¶16).
IV. Analysis of Infringement Allegations
The complaint alleges direct infringement by Defendant's making, using, and selling of the "Exemplary Defendant Products" (Compl. ¶11) and by its internal testing and use of these products (Compl. ¶12). However, the complaint's substantive infringement allegations are incorporated by reference from an external document, Exhibit 2, which was not provided with the complaint (Compl. ¶¶ 16-17). Without this exhibit, a detailed element-by-element analysis is not possible. The complaint contains only generalized allegations that the accused products "satisfy all elements of the Exemplary '116 Patent Claims" (Compl. ¶16).
No probative visual evidence provided in complaint.
V. Key Claim Terms for Construction
The Term: "reusable identifier" (Claim 1)
Context and Importance: This term appears central to the patent's asserted novelty, which distinguishes the invention from systems using "one-time-use" identifiers. The scope of "reusable" will be a key issue in determining infringement.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The plain language of the claim suggests any identifier that can be used more than once could fall within its scope.
- Evidence for a Narrower Interpretation: The specification repeatedly qualifies the term, stating that the reusable identifier "does not contain user-specific or transaction-specific information" ('116 Patent, col. 6:37-39, col. 9:13-15). A defendant may argue that this description limits the term to identifiers devoid of such data.
The Term: "user verification information" (Claim 1)
Context and Importance: The nature of the information sent from the user's device to the verification server is a critical part of the claimed method. Whether the accused system transmits data meeting this definition will be a point of contention.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The term itself is general and could be argued to cover any data used for verification, including an anonymous device token or hardware ID.
- Evidence for a Narrower Interpretation: The specification provides specific examples, including "the user's first name, family name, email address, phone number," and "hardware-specific information" ('116 Patent, col. 12:7-12). A party could argue that this phrase requires information that directly or indirectly identifies the specific user or their device, rather than a generic session token.
VI. Other Allegations
- Indirect Infringement: The complaint alleges induced infringement, stating that Defendant distributes "product literature and website materials" that instruct end users on how to use its products in a manner that allegedly infringes the '116 Patent (Compl. ¶14).
- Willful Infringement: The willfulness allegation is based on post-suit conduct. The complaint asserts that the service of the complaint itself "constitutes actual knowledge" and that Defendant's continued infringement thereafter is willful (Compl. ¶¶ 13-14).
VII. Analyst’s Conclusion: Key Questions for the Case
- Evidentiary Sufficiency: A threshold issue is the complaint's lack of factual specificity. A primary question will be what evidence Plaintiff produces to substantiate its conclusory allegations that unspecified "Exemplary Defendant Products" practice each element of the asserted claims, particularly since the core allegations are contained in an unprovided exhibit.
- Definitional Scope: The case may turn on claim construction, especially the meaning of "reusable identifier." The central question is whether this term can be limited by the specification to require an identifier that is devoid of user-specific or transaction-specific information, and whether the accused system's identifier meets that definition.
- Architectural Mismatch: A key technical question will be whether the accused system's architecture maps onto the three-party structure required by the claims (service computer, user device, and a distinct verification server). The infringement analysis will likely focus on whether the accused system uses a separate verification entity as described in the patent or a more conventional two-party client-server model.