Unreported / Non-Citable
Background
Authentixx LLC owns U.S. Patent No. 10,355,863, titled “System and method for authenticating electronic content,” which addresses a recognized security problem: traditional webpage authentication relies on logos and symbols that are identical for all users and easily spoofed by fraudsters. The patent teaches a personalized verification system where a website server displays a unique “authenticity stamp” (specific to each user) alongside generic webpage content, allowing users to verify they are visiting the legitimate site rather than a spoofed domain.
Authentixx filed suit against Pickleball OpCo LLC, which operates a website for finding recreational pickleball leagues. Authentixx alleged that Pickleball’s website infringes Claims 9 and 11 of the ‘863 Patent by displaying users’ profile images (the “authenticity stamp”) alongside league information. The patent’s method comprises eleven sequential steps: storing an authenticity stamp in a preferences file at a file location (Step A); creating an authenticity key to locate that file (Step B); receiving webpage requests and creating corresponding data (Steps C–D); and retrieving and displaying the authenticity stamp alongside the requested content (Steps E–K). Claim 11 adds that the file location should be “random” and “not readily known” to obscure it.
After Authentixx filed its original complaint, Pickleball moved to dismiss for patent ineligibility and failure to allege plausible infringement. Authentixx amended its complaint to add factual allegations regarding prior art and the patent’s improvements thereover. Pickleball renewed its motion to dismiss on identical grounds.
The Court’s Holding
The court granted Pickleball’s motion to dismiss with prejudice, holding that the ‘863 Patent claims a patent-ineligible abstract idea and therefore is invalid under 35 U.S.C. § 101. Applying the two-step framework from Alice Corp. v. CLS Bank International, the court first identified the patent’s “focus” as simultaneously displaying generic webpage content alongside a user-specific symbol to authenticate a webpage—an abstract end-result. Although such a result might be achieved by specific means, the eleven steps in Claim 9 employ only “result-based functional language” without describing how to achieve each result in a non-abstract way. Examples include: “store,” “create,” “receive,” “process,” “locate,” “retrieve,” and “enable.” Step A instructs storing the stamp in a “random, not readily known” location but does not explain how to select such a location beyond the abstract notion of randomness. This vague functional language parallels prior cases finding patent ineligibility, such as claims using terms like “converting,” “routing,” “monitoring,” “authenticating,” and “permitting access” without technical specificity.
Authentixx argued the patent resembles Ancora Technologies v. HTC America, where a patent claiming software license verification achieved eligibility by specifically teaching use of a particular, modifiable, non-volatile portion of a computer’s BIOS memory—a specific hardware component with unique security characteristics not previously exploited in that manner. The court rejected this analogy, finding that the ‘863 Patent lacks comparable specificity. While Ancora identified particular computer components and their unique characteristics to achieve a measurable functional improvement (resistance to hacking), the ‘863 Patent merely instructs an abstract goal (“obscure” the file location) without teaching specific programming methods or non-conventional technical implementation details. At step two of the Alice analysis, the patent fails to contain an “inventive concept” that transforms the abstract idea into patent-eligible subject matter. An inventive concept must be “significantly more than the abstract idea itself” and cannot merely be “an instruction to implement or apply the abstract idea on a computer.” The ‘863 Patent’s result-focused, functional claims entirely lack inventive subject matter and thus fail § 101’s eligibility requirement.
Key Takeaways
- Software patents claiming authentication, security, or verification methods face heightened § 101 scrutiny under Alice and survive only if they teach specific, non-conventional implementation details—not merely abstract functional steps or intended results.
- Vague functional language (e.g., “store,” “process,” “retrieve,” “enable”) without explanation of technical implementation does not satisfy patent eligibility, even when combined with a technological environment or security goal.
- Simply storing data in an “obscured” or “random” location or adding boilerplate references to servers and client computers does not constitute an inventive concept capable of transforming an abstract idea into patent-eligible subject matter.
- Patents claiming improvements to authentication systems must identify specific, unexpected technical characteristics or implementations—analogous to Ancora’s use of particular BIOS memory—rather than rely on generic computer-system architecture.
Why It Matters
This decision reinforces the difficulty of securing patent protection for software-based authentication and security methods under modern patent eligibility doctrine. Many cybersecurity and user-verification innovations employ similar architectures: server-side data storage, client requests, and personalized responses. The court’s holding signals that claiming such methods through abstract functional steps—however well-intentioned for security—will not survive § 101 challenge. Patent applicants in the authentication space must now identify and claim specific technical implementations: particular data structures, unconventional memory usage, algorithmic specificity, or measurable improvements to computing systems themselves, rather than merely describing the end-user experience of security or the general arrangement of servers and clients.
For practitioners and inventors, the decision underscores the necessity of thorough technical specification in software patents, particularly in cybersecurity. Drafting that treats functional outcomes as claim elements—receiving requests, storing data, processing keys, enabling display—invites dismissal under § 101. The path forward for authentication patents lies in identifying and claiming the particular technical means by which those functions are accomplished, with specificity comparable to Ancora’s identification of BIOS memory as a unique, previously unused technical solution.