Reframe Tech LLC v. Moo Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Reframe Technologies LLC (New Mexico)
  • Defendant: MOO Inc. (Delaware)
  • Plaintiff's Counsel: Silverman, McDonald & Friedman; Rabicoff Law LLC
• Case Identification: 1:26-cv-00332, D. Del., 03/26/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant is incorporated in Delaware and has an established place of business in the district.
• Core Dispute: Plaintiff alleges that Defendant's unidentified products and services infringe a patent related to a system for trading network access resources.
• Technical Context: The technology enables owners of network access points (e.g., Wi-Fi hotspots) to earn credits for providing access to others, which can then be used to "pay" for network access when roaming on other participating access points.
• Key Procedural History: The complaint asserts that its own service provides Defendant with actual knowledge of infringement for the purposes of indirect and willful infringement allegations. No other procedural events are mentioned.

Case Timeline

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

U.S. Patent No. 7,552,870 - "Trading network resources"

The Invention Explained

• Problem Addressed: The patent describes a market failure where millions of individual wireless access gateways (e.g., home or small business Wi-Fi routers) exist but are not part of a cohesive network, leading to sparse coverage for any single billing provider and discouraging users from paying for roaming access '870 Patent, col. 2:1-17 This makes it difficult for hotspot operators to generate revenue from their underutilized network infrastructure '870 Patent, col. 2:8-12
• The Patented Solution: The invention proposes a "Network Resource Trading Exchange" '870 Patent, abstract This system allows an owner of an access gateway to earn credits when other users connect through their gateway. These earned credits can then be used by the owner to pay for network access when they are roaming and connect to another gateway within the same trading system '870 Patent, col. 2:21-27 The architecture, as shown in Figure 1, involves a user device, an access gateway, and a central "Trading System" that manages requests, authorizations, and account balances '870 Patent, FIG. 1
• Technical Importance: The system is designed to convert a fragmented landscape of private, underutilized network access points into a large-scale, monetizable roaming network without relying on a traditional financial payment systems for each transaction '870 Patent, col. 2:18-27

Key Claims at a Glance

• The complaint does not identify specific claims asserted against the Defendant, instead referring to "Exemplary '870 Patent Claims" detailed in an attached Exhibit 2, which was not provided with the complaint Compl. ¶11 Compl. ¶16 The analysis below focuses on independent claim 1 as a representative claim.
• Independent Claim 1:
  • storing data in "first type accounts" for a network resource user, each with a balance;
  • storing data in "second type accounts" for a network resource access gateway operator;
  • wherein credit on a second type account "acts as credit" on a first type account;
  • receiving a request to authorize network access, identifying a specific first type account and a specific second type account;
  • sending a reply authorizing or denying access based at least partially on the balance of the identified first type account; and
  • adjusting the balances of the identified first and second type accounts based on the network resources used.
• The complaint generally alleges infringement of "one or more claims" of the '870 Patent Compl. ¶11

III. The Accused Instrumentality

Product Identification

The complaint does not name any specific accused products or services Compl. ¶11 It refers generally to "Exemplary Defendant Products" that are identified in claim charts attached as Exhibit 2, which was not provided Compl. ¶11 Compl. ¶16

Functionality and Market Context

The complaint does not provide sufficient detail for analysis of the accused instrumentality's functionality. It only makes the conclusory allegation that the "Exemplary Defendant Products practice the technology claimed by the '870 Patent" Compl. ¶16

IV. Analysis of Infringement Allegations

The complaint incorporates infringement allegations by reference to claim charts in Exhibit 2, which was not provided Compl. ¶17 Consequently, a detailed claim chart summary cannot be constructed. The complaint's narrative theory is that the unidentified "Exemplary Defendant Products" satisfy all elements of the unidentified "Exemplary '870 Patent Claims" Compl. ¶16

No probative visual evidence provided in complaint.

Identified Points of Contention

Based on the language of the '870 Patent and the general nature of the allegations, several points of contention may arise.

• Scope Questions: A central question may be whether the Defendant's system architecture includes the distinct "first type accounts" (for users) and "second type accounts" (for gateway operators) as recited in claim 1. The interpretation of this structural requirement-whether it demands separate database entities or can be met by logical distinctions within a single user record-could be determinative '870 Patent, claim 1
• Technical Questions: The mechanism by which "credit... acts as credit" between the two account types will likely be a key technical issue '870 Patent, claim 1 The complaint provides no information on how the accused products perform this function, raising the question of what evidence Plaintiff will offer to show that the Defendant's settlement process performs the specific "trading" function claimed by the patent, rather than a conventional payment or subscription model.

V. Key Claim Terms for Construction

"first type accounts" / "second type accounts"

• Context and Importance: The claim structure is predicated on the existence of and interaction between these two distinct types of accounts. The viability of the infringement case will depend on whether the Defendant's system can be shown to map onto this two-account architecture.
• Evidence for a Broader Interpretation: The specification notes that in some embodiments, "a single account might be used, with earned credits and cash credits being made to the same account" '870 Patent, col. 5:48-52 This language may support an argument that the "types" are merely logical categories of credit rather than structurally separate accounts.
• Evidence for a Narrower Interpretation: Claim 1 recites the two account types as separate limitations. The detailed description further distinguishes them by assigning separate unique identifiers, such as an "Earned Balance UniqueID" and a "Cash Balance UniqueID," which are keys to different records in the "Account Record Table" '870 Patent, col. 5:42-48 This suggests the patent contemplates formally distinct data structures.

"credit... acts as credit"

• Context and Importance: This phrase defines the core "trading" functionality of the invention. Whether the Defendant's system infringes will depend on whether its method for settling balances between users and operators meets this functional requirement.
• Evidence for a Broader Interpretation: The plain meaning of "acts as" suggests functional equivalence. A party might argue that any system where earned credit from an operator's activity can be used to offset a user's roaming charges satisfies this limitation, regardless of the specific transactional implementation.
• Evidence for a Narrower Interpretation: The patent specification describes a system where a user's device can be configured to use an "Earned Balance i) First, ii) Last or iii) Never" when settling charges '870 Patent, col. 14:50-57 This hierarchical, rule-based application of different credit sources suggests a more complex and specific interaction than simple equivalence and may support a narrower construction requiring a defined payment waterfall.

VI. Other Allegations

Indirect Infringement

The complaint alleges induced infringement, asserting that the Defendant sells products to customers and distributes "product literature and website materials" that instruct them to use the products in an infringing manner Compl. ¶14 Compl. ¶15

Willful Infringement

The willfulness allegation is based on post-suit conduct. The complaint alleges that the service of the complaint itself provides "actual knowledge of infringement" and that the Defendant's continued business activities thereafter constitute willful infringement Compl. ¶13 Compl. ¶14

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

Architectural Mapping

A core issue will be one of structural equivalence: does the Defendant's system, once revealed, utilize the specific two-account architecture (a "first type" for users and a "second type" for operators) required by the patent, or does it operate on a fundamentally different data model that falls outside the claim scope?

The "Trading" Function

A key evidentiary question will be one of functional operation: how does the accused system facilitate payment for roaming network access? The case will likely turn on whether its method of applying credits and debits constitutes the "trading" mechanism wherein credit from an operator account "acts as credit" for a user account, as claimed in the '870 Patent.

Pleading Sufficiency

Given the complaint's reliance on un-provided exhibits to identify the accused products, their functionality, and the asserted claims, a threshold issue may be whether the pleading provides the Defendant with fair notice of infringement sufficient to satisfy federal pleading standards.