Eight Deer Ventures LLC v. AT&T Mobility LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Eight Deer Ventures, LLC (Delaware)
  • Defendant: AT&T Mobility LLC (Delaware)
  • Plaintiff's Counsel: Susman Godfrey LLP; Miller Fair Henry PLLC
• Case Identification: 2:26-cv-00573, E.D. Tex., 07/10/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant is deemed to reside in the District, conducts substantial business there, and maintains regular and established places of business, including retail stores and the AT&T Foundry in Plano.
• Core Dispute: Plaintiff alleges that Defendant's network and device management platforms infringe three patents related to remote device deregistration, remote firmware upgrades, and remote modification of device attributes.
• Technical Context: The technology concerns the management of machine-to-machine (M2M) and Internet of Things (IoT) devices, a critical area for telecommunications providers managing vast fleets of connected endpoints.
• Key Procedural History: The complaint notes that in a separate, recent patent action, Defendant AT&T either admitted to or did not contest personal jurisdiction and venue in the Eastern District of Texas.

Case Timeline

Date	Event
2012-10-26	'355 Patent Priority Date
2012-10-29	'597 Patent Priority Date
2014-05-05	'628 Patent Priority Date
2017-05-23	'597 Patent Issued
2017-08-08	'355 Patent Issued
2020-07-14	'628 Patent Issued
2026-07-10	Complaint Filing Date

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

U.S. Patent No. 9,661,597 - Method and Device for Deregistering Terminal Peripheral

(Issued May 23, 2017; Compl. ¶11; Compl. ¶56)

The Invention Explained

• Problem Addressed: The patent's background section describes the problem of wasted storage resources and potential communication errors that arise when a gateway device retains registration information for terminal peripherals (e.g., M2M sensors) that are no longer active or have been replaced '597 Patent, col. 2:35-49
• The Patented Solution: The invention provides a method for a network gateway to proactively manage device lifecycle by initiating a deregistration process. A gateway sends a deregistration request message to a specific terminal peripheral and, in response, deletes the corresponding registration information that the gateway had stored for that peripheral, thereby cleaning up stale network data '597 Patent, abstract '597 Patent, col. 7:59-col. 8:4
• Technical Importance: This technology provides a network-initiated mechanism to maintain an accurate and efficient registry of active devices, which is critical for the stability and scalability of large-scale M2M and IoT networks '597 Patent, col. 2:32-34

Key Claims at a Glance

• The complaint asserts at least independent claims 1 and 10 Compl. ¶58 Claim 1 is representative.
• The essential elements of independent claim 1 include:
  • Receiving, by a gateway, a request message for deregistering a terminal peripheral sent from a Machine-to-Machine/Man (M2M) service platform or an M2M application.
  • Sending, by the gateway, the request message for deregistering the terminal peripheral to that peripheral.
  • Deleting, by the gateway, registration information of the terminal peripheral that is stored by the gateway.
• The complaint does not explicitly reserve the right to assert dependent claims but references "one or more claims" Compl. ¶58

U.S. Patent No. 9,729,355 - Method, Device, and System for Remote Management of Terminal Peripheral

(Issued August 8, 2017; Compl. ¶11; Compl. ¶67)

The Invention Explained

• Problem Addressed: The patent's background suggests that prior methods for remote device management were not "targeted" and lacked a mechanism for subsequent processing, rendering them ineffective for reliably managing remote devices '355 Patent, col. 1:15-22
• The Patented Solution: The invention discloses a closed-loop remote management system. A central platform sends a management operation (e.g., a firmware update) to a device via a gateway. The device executes the operation and sends feedback (e.g., "success" or "failure") back to the gateway. The gateway then "processes" this feedback by, for example, removing the pending operation upon success or re-sending it at a preset time upon failure '355 Patent, abstract '355 Patent, col. 2:9-41
• Technical Importance: This creates a state-aware and reliable framework for executing and confirming critical operations on remote devices, improving the integrity and security of M2M networks '355 Patent, col. 2:20-29

Key Claims at a Glance

• The complaint asserts at least independent claims 1 and 10 Compl. ¶69 Claim 1 is representative.
• The essential elements of independent claim 1 include:
  • Forwarding, by an M2M gateway, data from a terminal peripheral to an M2M application or service platform.
  • Sending, by the M2M application or service platform, a remote management operation to the peripheral through the M2M gateway.
  • Processing, by the M2M gateway, the remote management operation based on execution information fed back from the peripheral, which includes:
    • Upon success, removing the remote management operation.
    • Upon failure, re-sending the remote management operation at a preset time.
• The complaint references "one or more claims," suggesting other claims may be asserted Compl. ¶69

U.S. Patent No. 10,715,628 - Attribute Operating Method and Device

(Issued July 14, 2020; Compl. ¶11; Compl. ¶78)

Technology Synopsis

The patent describes a method to solve the inefficiency of modifying a device or user "attribute" in M2M systems, where a minor change (e.g., adding a phone number) would require deleting and re-creating the entire resource '628 Patent, col. 1:61-col. 2:8 The invention allows for direct operations (create, delete, update) on an attribute itself via a structured request message, without needing to reconstruct the associated resource '628 Patent, abstract

Asserted Claims

At least independent claims 1 and 9 Compl. ¶80

Accused Features

The complaint accuses AT&T's "Office@Hand Platform" of infringing by allowing administrators to perform remote operations on user attributes, such as adding new users or managing extensions, without having to reconstruct the entire user profile from scratch Compl. ¶¶14, 40, 43

III. The Accused Instrumentality

Product Identification

The complaint identifies three main categories of accused instrumentalities:

1. The AT&T "Control Center" platform for device management Compl. ¶12
2. Firmware update capabilities, including AT&T's "Enterprise Firmware Over-the-Air," "Home Base" Wireless Internet Manager, and "Internet Air for Business 5G Gateway" Compl. ¶¶24, 27, 31
3. The AT&T "Office@Hand Platform," a Unified Communications as a Service (UCaaS) offering Compl. ¶40

Functionality and Market Context

• The complaint alleges the Control Center is a web-based portal, underpinned by Cisco's Gateway Management Module, that allows customers to manage their devices on AT&T's network, including activating and deactivating SIM cards (Compl. ¶16; Compl. ¶17, Compl. ¶footnote 2). The "Deactivate" feature allegedly removes the device from network management Compl. ¶18 A screenshot in the complaint shows a user interface for selecting a gateway and choosing to "Deactivate" it within the Control Center Compl. p. 6
• The firmware update platforms are described as web-based consoles or device dashboards that permit IT administrators and customers to trigger, schedule, and monitor firmware upgrades for various AT&T-connected devices, such as Samsung phones and internet gateways Compl. ¶¶24, 27, 31 These platforms allegedly provide status updates on the success or failure of an upgrade and allow for reattempts of unsuccessful upgrades Compl. ¶¶25-26
• The Office@Hand Platform is a cloud-based communication platform that enables administrators to manage user accounts and their associated attributes, such as adding new users, assigning extensions, and managing phone numbers, through a web interface and API Compl. ¶40 Compl. ¶¶43-45

IV. Analysis of Infringement Allegations

'597 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving, by a gateway, the request message for deregistering the terminal peripheral sent from a Machine-to-Machine/Man (M2M) service platform and/or an M2M application	Accountholders use the AT&T Control Center portal to initiate a "Deactivation Request" for a device.	¶16	col. 8:6-12
sending, by a gateway, a request message for deregistering the terminal peripheral to the terminal peripheral	The AT&T Control Center allegedly sends a "Cancel Location" command to the device, which forces the device to reregister on the network, an action the complaint equates with a deregistration command. The complaint provides a screenshot illustrating the "Cancel Location" feature Compl. p. 8	¶21	col. 7:59-62
deleting, by the gateway, registration information of the terminal peripheral stored by the gateway	Deactivating a device's SIM card via the Control Center ends its network connectivity and makes it unmanageable until reactivated, which the complaint alleges constitutes removing the device from the network.	¶¶18-19; Compl. ¶22	col. 8:1-4

• Identified Points of Contention:
  • Scope Question: A primary point of contention may be whether the accused "Deactivation" of a SIM card Compl. ¶17, which renders a device "offline" Compl. ¶19, is equivalent to "deregistering a terminal peripheral" as required by the claim. The defense may argue that temporarily deactivating a SIM is functionally distinct from permanently deleting registration records as contemplated by the patent.
  • Technical Question: The complaint alleges that a "Cancel Location" command, which forces a device "to reregister on the network" Compl. ¶21, satisfies the claim limitation of sending a "request message for deregistering." This raises the question of whether a command to reregister can be interpreted as a command to deregister, as the plain language suggests opposing functions.

'355 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
forwarding, by a Machine-to-Machine/Man (M2M) gateway, data sent from the terminal peripheral to an M2M application or an M2M service platform	Accused devices, such as the "Home Base" manager, communicate identifying information like the current firmware version to AT&T's servers when checking for updates. A screenshot shows the system "Checking for Updates" (Compl. p. 11).	¶29; Compl. ¶34	col. 6:35-40
sending, by the M2M application or the M2M service platform, a remote management operation to the terminal peripheral through the M2M gateway...	AT&T's "Enterprise Firmware Over-the-Air" platform allows administrators to use a web console to push a selected OS version to devices at a specified time and date.	¶24	col. 6:41-47
processing, by the M2M gateway, the remote management operation according to remote management operation execution information fed back by the terminal peripheral...	The platforms allegedly provide notifications on the success or failure of upgrades and allow for reattempts. The "Enterprise Firmware Over-the-Air" capabilities are alleged to allow the system to "reattempt the upgrade if it was at first unsuccessful." A screenshot highlights a "Monitor dashboard for update status" feature (Compl. p. 9).	¶¶25-26	col. 6:48-55

• Identified Points of Contention:
  • Technical Question: The claim requires the M2M gateway to perform the "processing" of the operation based on feedback. The complaint describes functionality of platforms like a "web-based console" Compl. ¶24 and central servers Compl. ¶29 A key dispute may be whether the plaintiff can establish that the gateway device at the network edge, rather than a centralized server, performs the claimed logic of re-sending a failed operation.
  • Evidentiary Question: The claim requires processing based on "execution information fed back by the terminal peripheral." The complaint alleges the system can "reattempt the upgrade" Compl. ¶26, but it does not explicitly detail the mechanism that triggers this reattempt. A central question will be what evidence shows that a reattempt is automatically triggered by a specific failure message sent from the peripheral, as opposed to being a pre-scheduled or manually initiated action.

V. Key Claim Terms for Construction

• Term ("'597 Patent"): "deregistering a terminal peripheral"

  • Context and Importance: This term is the central action of the asserted claims. Its construction will determine whether AT&T's "deactivation" features fall within the patent's scope.
  • Intrinsic Evidence for a Broader Interpretation: The patent specification describes the goal as deleting "unnecessary information" to "save the storage space" '597 Patent, col. 2:37-39 A plaintiff may argue this supports a functional definition where any action that logically removes a device from active management qualifies as "deregistering."
  • Intrinsic Evidence for a Narrower Interpretation: Claim 1 recites a multi-step process involving a request sent from a platform to a gateway, then from the gateway to the peripheral. An embodiment further describes the peripheral deleting its own local registration information and sending a confirmation message back to the gateway before the gateway deletes its records '597 Patent, Fig. 6 '597 Patent, col. 5:60-64 A defendant may argue that "deregistering" requires this specific, coordinated deletion of registration data by both parties, not merely making a device inactive on the network.

• Term ("'355 Patent"): "processing, by the M2M gateway"

  • Context and Importance: The location of the claimed "processing" logic (i.e., handling success or failure of an operation) is critical. The claim explicitly places this function "by the M2M gateway."
  • Intrinsic Evidence for a Broader Interpretation: The patent's background describes the M2M system in general terms, and a plaintiff could argue that "gateway" should be interpreted as a logical system component that could encompass functions distributed between an on-premise device and a cloud platform working in concert.
  • Intrinsic Evidence for a Narrower Interpretation: The patent's figures and description consistently depict the gateway as an intermediary between the "terminal peripheral" and the "M2M service platform" '355 Patent, Fig. 1 '355 Patent, Fig. 3 A defendant will likely argue that "M2M gateway" refers to this distinct intermediary device, and if the processing logic resides exclusively on the "M2M service platform" (i.e., AT&T's central servers), then the infringement allegation fails.

VI. Other Allegations

• Indirect Infringement: For all three patents-in-suit, the complaint alleges induced infringement under 35 U.S.C. § 271(b), stating that AT&T provides instructions, product manuals, and promotional materials that encourage customers to use the accused platforms in an infringing manner Compl. ¶60 Compl. ¶71 Compl. ¶82 The complaint also alleges contributory infringement under 35 U.S.C. § 271(c), asserting the accused features are "especially designed or adapted" for infringement and are not staple articles of commerce suitable for substantial non-infringing use Compl. ¶62 Compl. ¶73 Compl. ¶84
• Willful Infringement: The complaint alleges that AT&T has had notice of the patents-in-suit "at least as of the date of this Complaint" and that it is "aware" its conduct infringes, yet continues its infringing activities Compl. ¶63 Compl. ¶65 Compl. ¶74 Compl. ¶76 Compl. ¶85 Compl. ¶87 This forms the basis for a claim of willful infringement and a request for enhanced damages, seemingly focused on post-suit conduct as no pre-suit knowledge is alleged.

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

• A core issue will be one of definitional scope: Can the patent term "deregistering," which the '597 patent frames as a process for deleting stale registration records, be construed to cover the accused "SIM deactivation" and "Cancel Location" functionalities, which primarily affect a device's immediate network connectivity and registration status?
• A key architectural question will be one of location of function: Does the logic for handling firmware update failures, such as re-sending a failed operation as claimed in the '355 patent, reside "by the M2M gateway" (i.e., the edge device), or is this "processing" performed exclusively by AT&T's centralized cloud platforms, creating a potential mismatch with the claim language?
• A central validity and infringement question for the '628 patent will be one of technical distinction: Can the plaintiff demonstrate that the accused "Office@Hand" platform's method for modifying user attributes is functionally equivalent to the patent's claimed method of operating directly on an "attribute," and that this method was a non-obvious improvement over prior art systems that allegedly required re-creating the entire "resource"?