Calibrate Networks LLC v. CVS Pharmacy Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Calibrate Networks LLC (New Mexico)
  • Defendant: CVS Pharmacy, Inc. (Rhode Island)
  • Plaintiff’s Counsel: Rabicoff Law LLC
• Case Identification: 2:26-cv-00133, 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 and has committed acts of infringement in the district.
• Core Dispute: Plaintiff alleges that unspecified products and services from Defendant infringe a patent related to methods for managing network communications, specifically concerning address changes within a layered network architecture.
• Technical Context: The patent-in-suit addresses methods for improving the efficiency and flexibility of computer networking protocols, particularly in managing device addresses without disrupting active connections.
• Key Procedural History: The complaint does not mention any prior litigation, licensing history, or administrative proceedings related to the patent-in-suit.

Case Timeline

Date	Event
2013-03-15	U.S. Patent 9,584,633 Priority Date (Provisional App.)
2014-03-14	Application for U.S. Patent 9,584,633 Filed
2017-02-28	U.S. Patent 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 (“the ’633 Patent”), “Method and system for managing network communications,” issued February 28, 2017.

The Invention Explained

• Problem Addressed: The patent’s background section describes conventional layered network architectures as inefficient due to the need to pass data packets (Protocol Data Units or PDUs) through multiple processing stages at each layer, which can involve data copying and task switching ’633 Patent, col. 1:19-28 The patent also identifies the difficulty of changing a device’s network address without losing data or destroying active connections as a critical problem for mobility and routing efficiency ’633 Patent, col. 1:55-64
• The Patented Solution: The invention proposes a method for changing the address of a network entity (an "Inter-Process Communication (IPC) process") in a way that avoids connection loss ’633 Patent, abstract This is achieved by assigning a "new address" to the process while its "old address" is still active. The process begins using the new address as its source address for outgoing communications, while other network entities learn of the change and update their records, allowing for a seamless transition ’633 Patent, col. 6:14-30 This process is situated within a recursive network architecture where addresses may be known only within a specific "layer," while the process also has a "globally" known application name ’633 Patent, col. 11:36-47
• Technical Importance: The described method aims to provide a robust mechanism for renumbering network devices or entire networks with minimal disruption, a feature that supports network mobility and simplifies administration ’633 Patent, col. 5:41-47

Key Claims at a Glance

The complaint alleges infringement of "one or more claims" and refers to "Exemplary '633 Patent Claims" identified in an external exhibit that was not filed with the complaint Compl. ¶11 Assuming Claim 1 is representative of the asserted claims:

• Independent Claim 1 (Method):
  • determining that an address change is desired for an Inter-Process Communication (IPC) process that has an old address and a globally known application name;
  • assigning a new address to the IPC process, where the new address is only known in the layer; and
  • the IPC process utilizing the new address as a source address in any Data Transfer Process (DTP) flows originating from it.
• The complaint does not specify whether dependent claims are asserted but makes a general allegation of infringement of "one or more claims" Compl. ¶11

III. The Accused Instrumentality

Product Identification

The complaint does not name any specific accused products, services, or systems Compl. ¶11 It refers generally to "Defendant products identified in the charts incorporated into this Count below" and "Exemplary Defendant Products," but these charts are part of an exhibit that was not provided with the publicly filed complaint Compl. ¶11 Compl. ¶16

Functionality and Market Context

The complaint does not provide sufficient detail for analysis of the functionality or market context of any accused instrumentality.

IV. Analysis of Infringement Allegations

The complaint states that infringement allegations are detailed in "charts of Exhibit 2," which was not filed with the complaint Compl. ¶17 The body of the complaint contains no specific factual allegations mapping any feature of an accused product to the limitations of the patent claims. It alleges conclusorily that "the Exemplary Defendant Products practice the technology claimed by the '633 Patent" Compl. ¶16 As such, a claim chart summary cannot be constructed.

No probative visual evidence provided in complaint.

Identified Points of Contention

Based on the asserted technology and the likely nature of the Defendant's business, several points of contention may arise once infringement contentions are detailed.

• Architectural Mismatch: A primary question will be whether Defendant’s network infrastructure can be characterized as having the specific "Inter-Process Communication (IPC) process," "layer," and "globally known application name" architecture described and claimed in the patent. The patent describes a specific recursive networking model ’633 Patent, col. 4:15-18, and a potential dispute may center on whether a conventional enterprise network meets these structural limitations.
• Scope Questions: The analysis may raise the question of whether standard network address management functionalities, such as those in DHCP (Dynamic Host Configuration Protocol) or mobile IP, perform the same steps in the same way as the claimed method, which appears tied to the patent's unique architectural concepts.

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 construction is critical to determine if the claims apply to generic network devices or applications, or if they are limited to entities within the specific recursive network architecture described in the patent. Practitioners may focus on this term to dispute the fundamental applicability of the patent to the accused systems.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: The term itself is a general term of art in computer science. Plaintiff may argue it should be given its plain and ordinary meaning, covering any software processes communicating over a network.
  • Evidence for a Narrower Interpretation: The specification consistently links the term to a specific context: "IPC Processes are Application Processes that are members of a DIF [Distributed IPC Facility]" ’633 Patent, col. 5:54-56 Defendant may argue this definition, tied to the patent's specialized architecture, limits the term's scope.

The Term: "wherein the new address is only known in the layer"

• Context and Importance: This limitation is central to the claimed method, distinguishing it from systems where addresses might have global scope. The infringement analysis for any accused system will depend heavily on whether it can be shown to possess distinct "layers" in which addresses have such limited visibility.
• Intrinsic Evidence for Interpretation:
  • Evidence for a Broader Interpretation: Plaintiff could argue that "layer" should be interpreted broadly to mean any logical segmentation in a network where addressing might be localized, such as within a subnet or a virtual private network (VPN).
  • Evidence for a Narrower Interpretation: The patent's detailed description discusses a "recursive architecture" where protocols are replicated at each layer ’633 Patent, col. 4:26-30 Defendant may argue that the term "layer" is not a general networking concept but is instead inextricably linked to this specific, non-conventional architecture, thereby narrowing the claim's reach.

VI. Other Allegations

Indirect Infringement

The complaint alleges induced 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. ¶14 The allegation is made "on information and belief" and is tied to the unfiled Exhibit 2 Compl. ¶14

Willful Infringement

The complaint bases its willfulness allegation on post-suit knowledge. It asserts that the filing and service of the complaint and its associated (unfiled) claim charts provide Defendant with "actual knowledge of infringement" and that any subsequent infringement is therefore willful Compl. ¶¶13-14

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

• Pleading Sufficiency: A threshold issue is whether the complaint, which contains no factual allegations of infringement and relies entirely on an unfiled external exhibit, meets federal pleading standards. The case may face early challenges regarding the sufficiency of notice provided to the Defendant.
• Architectural Applicability: A core technical question will be one of architectural mismatch: can the specific terminology of the claims—such as "Inter-Process Communication (IPC) process" and an address "only known in a layer"—be mapped onto the components and operation of Defendant's conventional enterprise network systems, or are the claims limited to the specialized, recursive network architecture described in the patent?
• Observability and Proof: A key evidentiary question will be one of technical proof: assuming the accused systems are identified, what evidence can Plaintiff provide to demonstrate that they implement the specific, multi-step address-changing process of Claim 1, particularly the limitations regarding how and where old and new addresses are "known" within the network?