Lab Technology LLC v. Greenlight Financial Technology Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Lab Technology LLC (New Mexico)
  • Defendant: Greenlight Financial Technology, Inc. (Delaware)
  • Plaintiff's Counsel: Silverman, McDonald & Friedman; Rabicoff Law LLC
• Case Identification: 1:25-cv-01356, D. Del., 04/06/2026
• Venue Allegations: Plaintiff alleges venue is proper in the District of Delaware because Defendant is a Delaware corporation and has an established place of business in the district.
• Core Dispute: Plaintiff alleges that Defendant's unspecified products infringe a patent related to methods for automatically refreshing a telephone's display to show services based on the user's current context, such as location.
• Technical Context: The technology at issue falls within the domain of context-aware user interfaces for mobile devices, a foundational concept for modern smartphone applications that adapt their content based on user data like time and location.
• Key Procedural History: The complaint notes that the patent-in-suit's eligibility under 35 U.S.C. § 101 has been upheld in two prior district court cases, which may be raised to preemptively counter potential invalidity arguments on that basis.

Case Timeline

Date	Event
2006-06-22	U.S. Patent No. 9,219,982 Priority Date
2015-12-22	U.S. Patent No. 9,219,982 Issue Date
2018-04-06	Prior Litigation Decision Upholding Patent Eligibility (HTC America)
2026-01-30	Prior Litigation Decision Upholding Patent Eligibility (USAA)
2026-04-06	Complaint Filing Date

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

U.S. Patent No. 9,219,982 - Apparatus and method for automatically refreshing a display of a telephone

(Issued December 22, 2015; referred to as the "'982 Patent")

The Invention Explained

• Problem Addressed: The patent's background describes that prior to the invention, users of telephones had to "navigate through many menu displays in order to find a desired service" Compl. ¶10 '982 Patent, col. 1:30-32 This manual navigation was described as inefficient and cumbersome, as it failed to account for the fact that users often access specific services based on their location or the time of day Compl. ¶10 '982 Patent, col. 1:33-48 For example, a user might need train services when at a train station and mall services when at a mall, but conventional systems presented the same static menus regardless of context Compl. ¶12 '982 Patent, col. 1:67-2:3
• The Patented Solution: The invention claims a method for a telephone to automatically refresh its display to present communication services that are relevant to the user's current situation Compl. ¶13 As depicted in the patent's figures and description, the telephone's "function selector" connects to a "location server" to obtain the device's current location '982 Patent, Fig. 5 '982 Patent, col. 6:59-63 Based on this location, the selector chooses a predefined "function" from a datastore, where a function represents a set of conditions (e.g., "user at the office") associated with specific services (e.g., "conference call service") '982 Patent, abstract '982 Patent, col. 2:20-27 The telephone display is then automatically refreshed to show the services linked to that selected function Compl. ¶19
• Technical Importance: The claimed method represents a shift from static, user-driven menu navigation to dynamic, context-aware interfaces that proactively anticipate user needs, thereby improving user interface efficiency Compl. ¶17

Key Claims at a Glance

• The complaint focuses on independent claim 13 Compl. ¶19
• Essential elements of Claim 13 include:
  • A method of refreshing a display panel of a telephone.
  • Obtaining a current location of the telephone using a location server.
  • Selecting a function from the datastore.
  • Refreshing a screen on the display panel to include at least one communication service associated with the selected function.
  • This refreshing is based at least in part on the current location of the telephone.
• The complaint does not explicitly reserve the right to assert other claims but states infringement of "one or more claims" Compl. ¶23

III. The Accused Instrumentality

Product Identification

The complaint does not identify any specific accused products by name. It refers generally to "Exemplary Defendant Products" and incorporates by reference allegations from an unattached Exhibit 2 Compl. ¶¶23, 29

Functionality and Market Context

The complaint does not provide sufficient detail for analysis of the accused instrumentality's specific functionality. It alleges in general terms that the accused products "practice the technology claimed by the '982 Patent" Compl. ¶28 Given that Defendant Greenlight is a financial technology company, the accused products are presumably related to its mobile banking or financial management applications. However, the complaint provides no specific details about which features of these applications are alleged to infringe.

IV. Analysis of Infringement Allegations

The complaint references claim charts in an "Exhibit 2" to detail its infringement allegations but does not attach this exhibit Compl. ¶28 The narrative infringement theory alleges that unspecified "Exemplary Defendant Products" practice the method of Claim 13 Compl. ¶¶19, 28 The core of the allegation is that these products obtain a user's current location via a location server, select a function from a datastore, and refresh a screen to display a communication service based on that location Compl. ¶19 No probative visual evidence provided in complaint.

• Identified Points of Contention:
  • Evidentiary Question: The primary point of contention will be factual. The complaint's lack of specificity regarding the accused product's operation raises the question of what evidence Plaintiff will present to demonstrate that Defendant's products perform each step of the claimed method.
  • Scope Question: A dispute may arise over whether the features of Defendant's financial technology application constitute "communication services" as that term is used in the patent, which provides examples such as telephone services, directory services, and fund transfer services '982 Patent, col. 1:21-28 The applicability of this term to modern app features like spending alerts or chore management will likely be a central issue.
  • Technical Question: It will be a matter of dispute whether the accused product's architecture maps onto the claimed elements. For example, does the product "obtain[] a current location... using a location server" as distinct from using the phone's integrated GPS and operating system-level location APIs? The interpretation of "location server" will be critical.

V. Key Claim Terms for Construction

• The Term: "communication service"

• Context and Importance: This term is the object of the claimed method-it is what gets displayed on the refreshed screen. Its definition is critical because a mismatch between the patent's technologically-grounded examples and the functionality of the accused fintech product could be dispositive. Practitioners may focus on this term to determine if the patent's scope can extend beyond the telecommunications-centric context of the early 2000s to cover modern application features.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent provides a non-exhaustive list, including "personal communication services," "information services," and "commercial services, such as fund transfer services" '982 Patent, col. 1:21-26, which could suggest the term is meant to be expansive.
  • Evidence for a Narrower Interpretation: The specific examples provided are all tethered to traditional telecommunications or early internet services, such as "telephone services," "voice messaging," "yellow page services," "stock quote services," and "movie ticketing services" '982 Patent, col. 1:21-28 This context may support a narrower construction limited to services of that type.

• The Term: "location server"

• Context and Importance: Claim 13 requires "obtaining a current location of the telephone using a location server." The architectural relationship between the telephone and the source of its location data is a key limitation. Whether a modern smartphone's internal use of OS-provided location data from GPS/cellular/Wi-Fi signals meets this limitation will be a central technical question.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The term is not explicitly defined, which may support an argument that it covers any component, internal or external, that serves location data to an application.
  • Evidence for a Narrower Interpretation: Figure 5 depicts the "Location Server" (570) as a distinct architectural block separate from the "Telephone" (550), connected via a network '982 Patent, Fig. 5 This diagram, along with the description of connecting "over a network," could support an interpretation requiring a discrete, network-accessible server rather than an integrated, on-device capability '982 Patent, col. 6:64-7:2

VI. Other Allegations

• Indirect Infringement: The complaint alleges inducement of infringement, stating that Defendant distributes "product literature and website materials" that instruct end users on how to use the accused products in an infringing manner Compl. ¶26
• Willful Infringement: Willfulness is alleged based on knowledge of the '982 Patent obtained "at least since being served by this Complaint" Compl. ¶27 The allegation is therefore based on post-suit conduct.

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

• A core issue will be one of definitional scope: can the term "communication service," which is rooted in the patent's context of telecommunications and early web services, be construed to cover the features presented within a modern financial technology application?
• A second key issue will be one of technical mapping: does the accused product's architecture, which presumably leverages a smartphone's integrated operating system for location data, meet the claim requirement of "obtaining a current location... using a location server" as depicted and described in the patent?
• Finally, a central evidentiary question will be one of factual basis: given the complaint's lack of specificity, what evidence will emerge in discovery to show that the accused product actually performs the claimed steps of selecting a "function" from a "datastore" to contextually refresh its display, or is there a fundamental mismatch in technical operation?