Calibrate Networks LLC v. FedEx Corp

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Calibrate Networks LLC (New Mexico)
  • Defendant: FedEx Corporation (Delaware)
  • Plaintiff's Counsel: Rabicoff Law LLC
• Case Identification: 2:26-cv-00658, E.D. Tex., 08/07/2026
• Venue Allegations: Venue is alleged to be proper in the Eastern District of Texas because the defendant maintains an established place of business in the District and has allegedly committed acts of patent infringement there.
• Core Dispute: Plaintiff alleges that Defendant's internal network systems and/or products infringe a patent related to methods for managing network communications and dynamically changing network addresses.
• Technical Context: The lawsuit concerns foundational network architecture technology for improving the efficiency and flexibility of routing data packets, particularly in complex, large-scale networks.
• Key Procedural History: The complaint does not mention any prior litigation, Inter Partes Review (IPR) proceedings, or licensing history related to the patent-in-suit.

Case Timeline

Date	Event
2013-03-15	'633 Patent Priority Date
2017-02-28	'633 Patent Issued
2026-08-07	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, titled "Method and system for managing network communications," issued on February 28, 2017. Compl. ¶9 '633 Patent, front page

The Invention Explained

• Problem Addressed: The patent's background describes inefficiencies in traditional layered network architectures, where passing data packets (Protocol Data Units or PDUs) between layers requires data copies and task switching ʻ633 Patent, col. 1:20-28 It also notes the difficulty of changing network addresses for entities (e.g., for mobility or re-routing) without disrupting or losing connections ʻ633 Patent, col. 1:56-61
• The Patented Solution: The patent discloses a "recursive network architecture" where the protocol procedures are consistent across different layers, aiming to simplify processing ʻ633 Patent, col. 4:23-26 A core aspect of the solution is a method for changing the address of a network process without losing data or connections. This is achieved by assigning a "new address" to a process while the "old address" is still active, allowing a transition period during which the process has multiple identifiers, before the old address is phased out ʻ633 Patent, col. 5:41-col. 6:46 The system treats PDUs like a "serial tape" to be processed by a single state machine, which avoids the need to pass messages up and down a multi-layer protocol stack ʻ633 Patent, col. 3:3-9
• Technical Importance: The proposed methods aim to create more efficient, flexible, and robust networks by simplifying protocol processing and enabling dynamic renumbering of network entities without service disruption ʻ633 Patent, col. 5:41-46

Key Claims at a Glance

• The complaint alleges infringement of one or more "exemplary claims" without specifying them in the complaint body Compl. ¶11 Independent claim 1 is analyzed here as a representative claim.
• The essential elements of independent claim 1 are:
  • 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 uses the "new address" as a source address in its ongoing data transfer flows.
• The complaint notes that the infringement allegations are not limited to the exemplary claims identified in the referenced charts Compl. ¶11

III. The Accused Instrumentality

Product Identification

The complaint does not name specific products or services. It refers generally to "Exemplary Defendant Products" that are identified in charts incorporated by reference as Exhibit 2 Compl. ¶11 Given the defendant is FedEx Corporation, these are presumed to be internal network management systems, logistics platforms, tracking services, or other software and hardware infrastructure used in its global operations Compl. ¶11 Compl. ¶12

Functionality and Market Context

The complaint alleges that FedEx directly infringes by "making, using, offering to sell, selling and/or importing" the accused products and by having its "employees internally test and use these Exemplary Products" Compl. ¶11 Compl. ¶12 This suggests the allegations are primarily focused on FedEx's internal use of its own complex networking infrastructure for logistics and package tracking, a mission-critical component of its business. No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint incorporates infringement allegations by referencing claim charts in an external exhibit not included with the complaint document Compl. ¶16 Compl. ¶17 Therefore, a detailed claim chart summary cannot be constructed.

The narrative theory of infringement alleges that the "Exemplary Defendant Products" practice the technology claimed by the '633 Patent Compl. ¶16 This suggests Plaintiff will attempt to show that FedEx's network systems and/or software perform a method of managing network communications, specifically for changing addresses of network entities, that maps onto the elements of the asserted claims. For example, Plaintiff may allege that when a device or process on FedEx's network changes its network address, it does so using a method equivalent to the one described in claim 1 of the '633 Patent Compl. ¶11

• Identified Points of Contention:
  • Architectural Questions: A central issue may be whether FedEx's network infrastructure, which is likely based on standard TCP/IP protocols, can be shown to practice the specific, non-standard "recursive" architecture and "serial tape" processing model described in the patent ('633 Patent, col. 3:3-9; '633 Patent, col. 5:35-40).
  • Technical Questions: What evidence does the complaint provide that FedEx's systems distinguish between a "globally" known "application name" and a "layer-specific" address in the manner required by the claim? The infringement analysis will depend on whether the actual operation of FedEx's network can be mapped to these specific claim limitations.

V. Key Claim Terms for Construction

• The Term: "Inter-Process Communication (IPC) process"
  • Context and Importance: This term defines the entity whose address is being changed. Its scope is critical, as it determines whether the claim applies to the types of network nodes, applications, or devices operating on the accused FedEx network.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification suggests an "IPC Process" can be an "Application Process" that is a member of a "Distributed IPC Facility," which could be argued to encompass a wide variety of software applications communicating over a network '633 Patent, col. 5:50-52
    • Evidence for a Narrower Interpretation: The patent repeatedly discusses the term in the context of a "Recursive Inter Network Architecture (RINA)" '633 Patent, col. 5:41-44 A party could argue the term is limited to processes operating within such a specific, non-standard architecture, and not in a general-purpose TCP/IP network.
• The Term: "only known in a layer"
  • Context and Importance: This limitation, applied to both the "old address" and "new address," creates a distinction between the scope of an address and a "globally" known application name. The viability of the infringement allegation depends heavily on whether addresses in the accused system can be characterized as being confined to a "layer" in the way the patent describes.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: A party might argue this phrasing simply reflects the common networking concept where network-layer addresses (e.g., IP addresses) are distinct from higher-level application identifiers (e.g., DNS names), making the claim broadly applicable.
    • Evidence for a Narrower Interpretation: The patent describes a recursive architecture where "the protocols are the same" for each layer '633 Patent, col. 4:23-24, which is fundamentally different from the standard OSI or TCP/IP models. A party could argue that "layer" should be construed narrowly, tied to this specific and unconventional architectural context, thus limiting the claim's reach.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that since the service of the complaint, FedEx has knowingly sold products and distributed "product literature and website materials" that instruct users to infringe Compl. ¶14 Compl. ¶15 This allegation is based on post-suit conduct.
• Willful Infringement: The complaint alleges that service of the complaint itself provides FedEx with "Actual Knowledge of Infringement" and that FedEx "continues to make, use, test, sell, offer for sale, market, and/or import" the infringing products despite this knowledge Compl. ¶13 Compl. ¶14 This forms the basis for a claim of post-suit willful infringement, supporting a request for enhanced damages under 35 U.S.C. § 284 and a declaration that the case is "exceptional" under § 285 Prayer ¶D Prayer ¶E.i

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

• A core issue will be one of architectural mismatch: Can Plaintiff prove that FedEx's network, which is likely built on standard, well-established protocols, practices the specific and unconventional "recursive" method of address management described in the '633 patent, or will the technical differences be too great to support a finding of infringement?
• The case will also likely involve a key definitional dispute: Can the claim term "only known in a layer," which is rooted in the patent's unique architectural description, be construed to read on the behavior of addresses within a conventional, non-recursive network architecture like that presumably used by FedEx?