DCT

4:26-cv-00626

Factor2 Multimedia Systems LLC v. Cigna Healtcare

Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
    • Plaintiff: Factor 2 Multimedia Systems, LLC (Virginia)
    • Defendant: Cigna Healthcare (Texas)
    • Plaintiff's Counsel: DNL Zito
  • Case Identification: 4:26-cv-00626, E.D. Tex., 06/10/2026
  • Venue Allegations: Venue is alleged to be proper because the Defendant maintains a regular and established place of business in the district and has committed alleged acts of infringement there.
  • Core Dispute: Plaintiff alleges that Defendant's online user portals infringe six U.S. patents related to systems and methods for multi-factor user authentication.
  • Technical Context: The technology at issue relates to two-factor and multi-factor authentication methods designed to enhance security for online transactions by verifying a user's identity through multiple credentials.
  • Key Procedural History: The complaint alleges that all six patents-in-suit are members of the same patent family.

Case Timeline

Date Event
2001-08-29 Earliest Priority Date for all Patents-in-Suit
2012-10-02 U.S. Patent No. 8,281,129 Issues
2017-07-11 U.S. Patent No. 9,703,938 Issues
2017-07-19 U.S. Patent No. 9,727,864 Issues
2017-12-27 U.S. Patent No. 9,870,453 Issues
2018-09-25 U.S. Patent No. 10,083,285 Issues
2020-09-08 U.S. Patent No. 10,769,297 Issues
2025-01-01 Cigna portals allegedly began requiring Multi-Factor Authentication
2026-06-10 Complaint Filed

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

U.S. Patent No. 8,281,129 - "Direct Authentication System And Method Via Trusted Authenticators"

  • Patent Identification: U.S. Patent No. 8,281,129, "Direct Authentication System And Method Via Trusted Authenticators," issued October 2, 2012.

The Invention Explained

  • Problem Addressed: The patent's background section describes the growing problem of online fraud and identity theft, which stems from the flawed assumption that a person possessing certain pieces of supposedly confidential information (like a Social Security Number) is who they claim to be '129 Patent, col. 1:16-2:5
  • The Patented Solution: The invention proposes a "two-factor" authentication method that relies on a "trusted-authenticator," such as a bank with which the user has a pre-existing relationship '129 Patent, col. 4:45-50 To complete a transaction with a business, the user combines "something the user knows" (a static key) with "something the individual receives" (a dynamic, single-use code requested from the trusted-authenticator) '129 Patent, col. 5:51-6:1 The business then communicates with the trusted-authenticator to verify both keys and confirm the user's identity, as illustrated in the patent's Figure 2a '129 Patent, Fig. 2a
  • Technical Importance: This approach sought to enhance security for online transactions by moving beyond static, knowledge-based credentials and introducing a trusted third party to the verification process.

Key Claims at a Glance

  • The complaint asserts claims 1-52, with independent claim 1 provided as exemplary Compl. ¶20 Compl. ¶30
  • The essential elements of independent claim 1, a method, are:
    • Receiving a request for a dynamic code from an individual at a trusted-authenticator's computer.
    • Calculating the dynamic code, which is valid for a predefined time and single use.
    • Sending the dynamic code to the individual.
    • Receiving an authentication request from an entity, which includes user information and the dynamic code.
    • Authenticating the individual's identity based on the user information and dynamic code, and providing the result to the entity.
  • The complaint reserves the right to assert the numerous dependent claims.

U.S. Patent No. 9,727,864 - "Centralized Identification and Authentication System and Method"

  • Patent Identification: U.S. Patent No. 9,727,864, "Centralized Identification and Authentication System and Method," issued July 19, 2017.

The Invention Explained

  • Problem Addressed: The patent identifies a need for a secure and scalable online authentication system that does not require financial institutions to change existing systems or users to manage special hardware, and which protects user privacy by limiting the distribution of personal information to various online merchants '864 Patent, col. 2:5-15
  • The Patented Solution: The invention describes a system centered on a "Central-Entity" that securely stores user information '864 Patent, col. 3:1-10 When a user wants to transact with an "External-Entity" (e.g., a merchant), the user requests a dynamic, time-dependent "SecureCode" from the Central-Entity. The user provides this code and a "UserName" to the External-Entity, which in turn forwards this "digital identity" to the Central-Entity for verification '864 Patent, Fig. 2 '864 Patent, col. 5:42-59
  • Technical Importance: This centralized architecture was designed to provide strong authentication for e-commerce while minimizing the exposure of a user's sensitive personal and financial data across multiple third-party websites.

Key Claims at a Glance

  • The complaint asserts claims 1-15 Compl. ¶38 A claim chart exhibit is provided for independent claim 1 Compl. Ex. to '864 Patent
  • The essential elements of independent claim 1, a system, are:
    • A dynamic-code generator, a computer-readable memory, a timer, a network receiver, and a network transmitter.
    • A computer processor coupled to these components.
    • The processor is configured to receive a request for a digital code, transmit the code to the user, and then receive an authentication request from the transaction computer system that includes the user-entered code.
    • The system then determines if the code is valid (e.g., not expired and not previously used) and, if so, transmits an approval message.
  • The complaint reserves the right to assert dependent claims.

U.S. Patent No. 9,703,938 - "Direct Authentication System and Method Via Trusted Authenticators"

  • Patent Identification: U.S. Patent No. 9,703,938, "Direct Authentication System and Method Via Trusted Authenticators," issued July 11, 2017.
  • Technology Synopsis: As a member of the same patent family as the '129 Patent, the '938 patent addresses the problem of identity theft in online transactions '938 Patent, col. 1:29-2:65 It discloses a two-factor authentication method involving a user, a business, and a "trusted-authenticator" that validates the user's identity using a combination of a static key and a dynamic key '938 Patent, col. 7:5-16
  • Asserted Claims: Claims 1-26 Compl. ¶34
  • Accused Features: The authentication system used in Cigna's online portals (CignaforHCP, myCigna.com, MyChart) (Compl. ¶¶21; Compl. ¶34).

U.S. Patent No. 9,870,453 - "Direct Authentication System and Method Via Trusted Authenticators"

  • Patent Identification: U.S. Patent No. 9,870,453, "Direct Authentication System and Method Via Trusted Authenticators," issued December 27, 2017.
  • Technology Synopsis: As a member of the same patent family, the '453 patent addresses online identity theft by proposing a two-factor authentication system '453 Patent, col. 1:21-2:65 The system uses a "trusted-authenticator" to issue a time-sensitive, single-use "dynamic key" to a user, which is used in combination with a "static key" to verify the user's identity during a transaction with a business '453 Patent, col. 7:1-12
  • Asserted Claims: Claims 1-26 Compl. ¶42
  • Accused Features: The authentication system used in Cigna's online portals (CignaforHCP, myCigna.com, MyChart) (Compl. ¶¶21; Compl. ¶42).

U.S. Patent No. 10,083,285 - "Direct Authentication System and Method Via Trusted Authenticators"

  • Patent Identification: U.S. Patent No. 10,083,285, "Direct Authentication System and Method Via Trusted Authenticators," issued September 25, 2018.
  • Technology Synopsis: This patent also addresses the inadequacy of traditional authentication in preventing online fraud '285 Patent, col. 1:49-2:24 It discloses a two-factor authentication method where a "trusted-authenticator" provides a time-limited "dynamic key" to a user, which is used along with a "static key" for verification by a business, with the trusted-authenticator confirming the validity of both keys '285 Patent, col. 7:22-38
  • Asserted Claims: Claims 1-30 Compl. ¶46
  • Accused Features: The authentication system used in Cigna's online portals (CignaforHCP, myCigna.com, MyChart) (Compl. ¶¶21; Compl. ¶46).

U.S. Patent No. 10,769,297 - "Centralized Identification and Authentication System and Method"

  • Patent Identification: U.S. Patent No. 10,769,297, "Centralized Identification and Authentication System and Method," issued September 8, 2020.
  • Technology Synopsis: Like the '864 patent, this patent addresses the need for a secure e-commerce system that protects user privacy '297 Patent, col. 2:5-15 It describes a "Central-Entity" that provides a user with a dynamic, time-dependent "SecureCode," which the user then presents to an "External-Entity" to be authenticated without revealing underlying personal data '297 Patent, col. 3:1-33
  • Asserted Claims: Claims 1-29 Compl. ¶50
  • Accused Features: The authentication system used in Cigna's online portals (CignaforHCP, myCigna.com, MyChart) (Compl. ¶¶21; Compl. ¶50).

III. The Accused Instrumentality

Product Identification

The accused instrumentalities are Defendant Cigna's online portals, identified as CignaforHCP, myCigna.com, and MyChart, as well as the associated "back end systems and backbone" that provide authentication services (Compl. ¶¶3; Compl. ¶21).

Functionality and Market Context

The complaint alleges that these portals implement "two-factor authentication (2FA) or as also referred to, multi-factor authentication (MFA)" to secure user access Compl. ¶25 The alleged functionality requires a user to employ a time-limited, single-use "message code sent to a separate device" to complete the login process Compl. ¶25 A screenshot provided in the complaint indicates that Cigna portals began requiring this form of authentication in 2025 Compl. p. 8 This screenshot from a Cigna website explains the need to update a connection due to the implementation of Multi-Factor Authentication Compl. p. 8

IV. Analysis of Infringement Allegations

The complaint's infringement theory is that the standard operation of the MFA systems used by Cigna's portals performs the steps and utilizes the components recited in the asserted claims Compl. ¶25

'129 Patent Infringement Allegations

The complaint does not provide a detailed element-by-element claim chart for the '129 patent. The following table synthesizes the general allegations regarding the accused MFA system (Compl. ¶24; Compl. ¶25) against the elements of claim 1.

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
receiving electronically a request for a dynamic code for the individual, which request is received from the individual by a trusted-authenticator's computer... The user's login attempt on a Cigna portal allegedly triggers a request for an authentication code from Cigna's back-end authentication system. ¶¶24-25 col. 7:45-50
calculating by the trusted-authenticator's computer the dynamic code for the individual... wherein the dynamic code is valid for a predefined time and becomes invalid after being used Cigna's authentication system allegedly generates a message code that is time-limited and for one-time use. ¶25 col. 8:14-20
sending by the trusted-authenticator's computer electronically the dynamic code to the individual... The generated one-time code is allegedly sent to the user's separate device (e.g., phone or email). ¶25 col. 8:21-25
receiving by the trusted-authenticator's computer electronically an authentication request from the entity to authenticate the individual... After the user enters the code into the portal, the portal allegedly sends an authentication request to the back-end system. ¶25 col. 8:51-61
authenticating by the trusted-authenticator's computer an identity of the individual based on the user information and the dynamic code included in the authentication request... Cigna's back-end system allegedly validates the code to confirm the user's identity and grants access. ¶¶24-25 col. 9:11-25

'864 Patent Infringement Allegations

The following table is based on the claim chart exhibit for the '864 patent provided with the complaint Compl. Ex. to '864 Patent

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
An authentication computer system...comprising: a dynamic-code generator to generate a plurality of substantially non-predictable digital codes; Cigna's system allegedly includes a generator for one-time security codes sent to a user's email or mobile phone. ¶¶24-25; ¶38 col. 5:18-24
a timer to generate an electronic timer signal; The generated code allegedly expires after a set time (e.g., 30 minutes), which is said to require a timer. ¶¶24-25; ¶38 col. 6:49-53
a computer processor electronically coupled to the timer...to: during an electronic transaction...receive a digital request for a digital code for authenticating the user... When a user logs in, the processor allegedly receives a digital request to initiate the two-step authentication process. ¶¶24-25; ¶38 col. 6:11-20
...transmit one of the generated digital codes for the user to one of the electronic devices of the user... The system allegedly sends a one-time security code to the user's email or mobile phone. ¶¶24-25; ¶38 col. 6:21-28
...receive a digital authentication request for authenticating the user from the transaction computer system...the digital identity including the digital code, After the user enters the code, the transaction computer system (the web portal) allegedly forwards the code to the authentication system for verification. ¶¶24-25; ¶38 col. 6:49-65
...determine if there is a match between the received digital code and one of the generated digital codes and the received digital code is valid to authenticate the user... The authentication system allegedly compares the user-entered code against the stored, generated code and checks its time-based validity. ¶¶24-25; ¶38 col. 7:13-22
if there is a match and the received digital code is valid, (i) transmit a digital authentication approval message to the transaction computer system... Upon successful verification, the authentication system allegedly signals the web portal to grant the user access. ¶¶24-25; ¶38 col. 7:23-31
  • Identified Points of Contention:
    • Scope Question: A central point of contention for all asserted patents may be the structural definition of the claimed systems. The patents, particularly the '129, '938, '453, and '285 patents, describe a three-party system involving a user, a business, and a separate "trusted-authenticator." The complaint alleges infringement by Cigna's system, where Cigna appears to act as both the "business" (via its content portals) and the "authenticator" (via its back-end servers). This raises the question of whether a two-party arrangement can infringe claims that may be construed to require a three-party architecture.
    • Technical Question: The infringement allegations in the complaint and its exhibit rely on high-level descriptions from user guides and marketing materials Compl. ¶25 Compl. Ex. to '864 Patent A key question for the court will be whether the evidence, once developed, shows that the accused Cigna systems actually operate in the specific manner required by the claim limitations, or if there is a fundamental mismatch in technical operation. For example, does Cigna's system generate, transmit, receive, and evaluate codes in the precise sequence and manner claimed?

V. Key Claim Terms for Construction

  • Term 1 ('129 Patent): "trusted-authenticator's computer"
    • Context and Importance: The infringement analysis for the '129 patent may depend on whether Cigna's own authentication servers can be defined as a "trusted-authenticator's computer" separate from the "entity" (the Cigna portal) that the user is accessing. Practitioners may focus on this term because the patent's specification appears to frame the "trusted-authenticator" as a distinct third party.
    • Intrinsic Evidence for a Broader Interpretation: The claims themselves do not explicitly state that the "trusted-authenticator's computer" must be owned or operated by a separate commercial entity from the "entity" being accessed.
    • Intrinsic Evidence for a Narrower Interpretation: The specification consistently uses a bank or other financial institution with a pre-existing relationship as the canonical example of a trusted-authenticator, distinguishing it from the "creditor" or "business" the user is transacting with '129 Patent, col. 4:45-50 '129 Patent, col. 7:60-67 This context suggests an intended structural separation.
  • Term 2 ('864 Patent): "Central-Entity"
    • Context and Importance: Infringement of the '864 patent hinges on whether Cigna's authentication system functions as the claimed "Central-Entity". The core purpose of the "Central-Entity" described in the patent is to serve multiple, disparate "External-Entities" without distributing the user's private data to them. Practitioners may focus on whether Cigna's system, which authenticates users for its own portals, meets this architectural role.
    • Intrinsic Evidence for a Broader Interpretation: Claim 1 recites an "authentication computer system" and a "transaction computer system" without explicitly requiring they be operated by different commercial parties. One could argue Cigna's authentication servers are a "Central-Entity" for its various web portals, which act as "transaction computer systems."
    • Intrinsic Evidence for a Narrower Interpretation: The patent's summary and detailed description emphasize that the invention is for a centralized service that provides identification for users to transact with a plurality of external merchants or service providers '864 Patent, Fig. 1 '864 Patent, col. 3:1-21 This framing suggests the "Central-Entity" is architecturally distinct from the "External-Entities" it serves.

VI. Other Allegations

  • Indirect Infringement: The complaint does not contain specific allegations of indirect infringement (inducement or contributory infringement). It alleges direct infringement under 35 U.S.C. § 271(a) Compl. ¶22
  • Willful Infringement: The complaint does not use the term "willful," but it requests enhanced damages and a finding that the case is "exceptional" under 35 U.S.C. §§ 284 and 285, which are remedies for willful or egregious infringement (Compl. p. 11, ¶¶B, D, F). The complaint does not allege any facts to support pre-suit knowledge of the patents by the Defendant.

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

  1. A question of architectural scope: Can the terms "trusted-authenticator" (from the '129 patent family) and "Central-Entity" (from the '864 patent family), which are described in the patent specifications within a three-party framework (user, business, authenticator), be construed to cover the two-party arrangement allegedly used by Cigna, where Cigna's own systems appear to function as both the "business" and the "authenticator"?

  2. An evidentiary question of operational function: The complaint relies heavily on marketing documents and user guides to allege infringement. A central issue will be whether discovery reveals that Cigna's MFA systems technically operate in the precise manner and sequence recited by the asserted claims, or if there is a material difference between the high-level descriptions and the actual implementation.

Loading Complaint