2:26-cv-00134
Calibrate Networks LLC v. McDonalds Corp
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Calibrate Networks LLC (New Mexico)
- Defendant: McDonald's Corporation (Delaware)
- Plaintiff’s Counsel: Rabicoff Law LLC
- Case Identification: 2:26-cv-00134, E.D. Tex., 02/17/2026
- Venue Allegations: Plaintiff alleges venue is proper because Defendant maintains an established place of business in the Eastern District of Texas.
- Core Dispute: Plaintiff alleges that unspecified products and services from Defendant infringe a patent related to methods for managing network communications, specifically concerning how addresses are changed for processes within a network layer.
- Technical Context: The patent addresses inefficiencies in traditional layered network architectures, proposing a recursive model to simplify data processing and enable seamless address changes for mobile or re-routed network entities.
- Key Procedural History: The complaint does not reference any prior litigation, licensing history, or other procedural events related to the patent-in-suit.
Case Timeline
| Date | Event |
|---|---|
| 2013-03-15 | U.S. Patent No. 9,584,633 Priority Date |
| 2017-02-28 | U.S. Patent No. 9,584,633 Issued |
| 2026-02-17 | Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 9,584,633 - Method and system for managing network communications
- Patent Identification: U.S. Patent No. 9,584,633, "Method and system for managing network communications," issued February 28, 2017.
The Invention Explained
- Problem Addressed: The patent describes two core problems with traditional network architectures (col. 1:18-24; col. 1:55-62). First, processing network data (packets) through multiple, distinct protocol layers is inefficient, requiring data copies and task switching (col. 1:20-24). Second, changing the network address of a device or application without losing existing connections is "difficult," "complex, expensive and disruptive," which hinders mobility and efficient routing (col. 1:55-62).
- The Patented Solution: The patent proposes a "recursive network architecture" where the protocols used at different layers are fundamentally the same, which "flattens" the processing and improves efficiency (col. 3:6-9; col. 4:22-25). To solve the address-change problem, the invention describes a method where a network management system assigns a new address to an "Inter-Process Communication (IPC) process" while its old address is still active (col. 6:13-16). The IPC process then immediately begins using this new address as the source address for all its outgoing data traffic, allowing for a seamless transition without dropping connections (col. 6:18-21).
- Technical Importance: This approach aims to provide a more flexible and robust method for managing network identity and location, which is critical for supporting mobile devices and dynamically reconfiguring network paths in response to congestion or failure (col. 5:39-43).
Key Claims at a Glance
The complaint does not specify which claims it asserts, referring only to the "Exemplary '633 Patent Claims" Compl. ¶11 Independent claims 1 (method), 8 (system), and 15 (machine-readable storage medium) cover the core invention. The elements of independent claim 1 are representative:
- Determining that an address change is desired for an Inter-Process Communication (IPC) process.
- The IPC process has an old address that is "only known in a layer" and an application name that is "known globally."
- Assigning a new address to the IPC process, where the new address is also "only known in the layer."
- The IPC process then "utilizes the new address as a source address" in any outgoing data flows.
III. The Accused Instrumentality
Product Identification
The complaint does not identify any specific accused product, method, or service by name Compl. ¶11 It refers generally to "Exemplary Defendant Products" throughout the pleading Compl. ¶¶11-12 Compl. ¶14 Compl. ¶16
Functionality and Market Context
The complaint does not provide sufficient detail for analysis of the accused instrumentality's functionality or market context.
IV. Analysis of Infringement Allegations
The complaint references a claim-chart exhibit (Exhibit 2) that is not provided Compl. ¶17 The complaint’s narrative allegations state that the "Exemplary Defendant Products practice the technology claimed by the '633 Patent" and "satisfy all elements of the Exemplary '633 Patent Claims" Compl. ¶16 However, without the specific charts or identification of an accused product, it is not possible to conduct a detailed infringement analysis. The complaint provides no specific facts explaining how any McDonald's product or system performs the steps of the asserted claims. No probative visual evidence provided in complaint.
- Identified Points of Contention:
- Evidentiary Question: The primary question is one of identification: what specific product, system, or service is being accused of infringement? The complaint’s failure to name an instrumentality creates a fundamental ambiguity.
- Technical Question: Assuming an instrumentality is identified, a key technical question will be whether its architecture maps onto the specific "recursive" and "layered" framework described in the ’633 Patent. The infringement allegation appears to hinge on whether the accused system performs the specific claimed sequence of assigning a new, layer-specific address to a globally-known process and then using that new address as the source for outgoing traffic.
V. Key Claim Terms for Construction
"Inter-Process Communication (IPC) process"
- Context and Importance: This term defines the entity whose address is being changed. Its construction is critical to determining whether the claims read on modern software applications and network services. Practitioners may focus on this term because the patent appears to give it a specific meaning tied to its proposed "Recursive Inter Network Architecture (RINA)" (col. 5:43-45), defining it as an "Application Processes that are members of a DIF [Distributed IPC Facility]" (col. 5:54-56).
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The plain and ordinary meaning of "Inter-Process Communication" is well-established in computer science, potentially allowing the term to cover a wide range of software interactions beyond the patent's specific architecture.
- Evidence for a Narrower Interpretation: The specification explicitly links the term to its own RINA framework and defines it in the context of a "DIF" (col. 5:54-56). A defendant may argue this definition limits the claim scope to only those systems implementing such an architecture.
"only known in a layer"
- Context and Importance: This limitation, which applies to both the "old address" and the "new address," contrasts with the "application name that is known globally" (claim 1). The distinction between what is known "in a layer" versus "globally" is central to the claimed invention. The dispute will likely focus on whether the addresses used by the accused system have the limited scope required by this term.
- Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification does not provide a formal definition of "layer," which could support an argument that the term should be interpreted broadly to encompass various forms of logical separation in a network stack.
- Evidence for a Narrower Interpretation: The patent states that "a-old and a-new are only known within the layer," while the "A-Appl-name is known globally" (col. 6:16-18). This direct contrast suggests a specific, constrained meaning where the address is intentionally hidden from or irrelevant to other parts of the system, a key feature of the patented method for seamless transition.
VI. Other Allegations
- Indirect Infringement: The complaint alleges induced infringement, stating that Defendant sells products and distributes "product literature and website materials" that instruct end users on how to use the products in a manner that infringes the ’633 Patent Compl. ¶14
- Willful Infringement: The complaint alleges that Defendant has had "Actual Knowledge of Infringement" since the service of the complaint and its attached claim charts Compl. ¶13 This forms the basis for a claim of post-suit willfulness Compl. ¶14
VII. Analyst’s Conclusion: Key Questions for the Case
Identification and Specificity: The central threshold issue is the complaint's failure to identify any accused product. A primary question for the case will be whether the plaintiff can substantiate its general allegations by mapping the patent's claims to a specific McDonald's technology or service.
Architectural Congruence: A key technical question will be one of architectural mapping: does any accused McDonald's system, once identified, operate using a framework that corresponds to the patent's specific model of a globally-known "application name" tied to a layer-specific "IPC process" with layer-specific addresses? The viability of the infringement claim may depend on whether a modern, commercial network architecture can be shown to embody this particular structure.
Definitional Scope: The case may turn on a question of claim construction: can the term "Inter-Process Communication (IPC) process," which the patent defines within its specialized RINA architecture, be construed broadly enough to read on components of a general-purpose commercial IT system, or will it be limited to the specific context described in the specification?