IP Library Granted Patent US 12,652,240
Granted Patent B2
US 12,652,240 · App. 18/786,458 · Granted Jun 9, 2026

Name-based routing through networks

Inventors: David Sutton (Monroe, LA); Steve Toms (Middleburg, FL); Shelley Goldner (Superior, CO); Shelli L. Hurd (Arvada, CO)
Assignee: Level 3 Communications, LLC
H04L45/42H04L41/0627H04L41/0631H04L45/02H04L45/306H04L45/54H04L63/0236
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,652,240
App. No.
18/786,458
Granted
Jun 9, 2026
Kind
B2
Abstract

Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.

Claims (54)

1 . A method, comprising:

receiving, using a first broker manager that is disposed within a first network among a plurality of networks and from a first client device, a request to establish a connection with a first network device over at least one network among the plurality of networks;

determining whether the first network device is listed within a stored list;

in response to the determining that the first network device is listed within the stored list, determining, using the first broker manager, whether any alerts associated with the first network device have been received by an alert manager that is communicatively coupled with the first broker manager, and performing, without polling other broker managers regarding a status of the first network device and without attempting to connect to the first network device via one or more brokers that are managed by the first broker manager, at least one of the following:

based on a determination that an alert has been received that indicates that the first network device is offline, sending or relaying, using the first broker manager, a message to the first client device indicating that the first network device is offline; or

based on a determination that an alert has been received that indicates that a connection to the first network device is currently lost, sending or relaying, using the first broker manager, a message to the first client device indicating that the connection to the first network device is currently lost;

in response to the determining that the first network device is not listed within the stored list, perform the following:

forwarding, using the first broker manager, the request via at least one of a local messaging broker or a downstream messaging broker;

after receiving a message from at least one other broker manager that is disposed within the plurality of networks indicating that the first network device is offline, updating, using the first broker manager, the stored list to indicate that the first network device is offline, and sending or relaying, using the first broker manager, a message to the first client device indicating that the first network device is offline; and

after receiving a message from at least one other broker manager that is disposed within the plurality of networks indicating that a connection to the first network device is currently lost, updating, using the first broker manager, the stored list to indicate that the connection to the first network device is currently lost, and sending or relaying, using the first broker manager, a message to the first client device indicating that the connection to the first network device is currently lost.

2 . The method of claim 1 , wherein:

the first client device is disposed within the first network;

receiving the request to establish the connection with the first network device from the first client device comprises receiving, using the first broker manager and from the first client device, the request via a client broker;

the one or more brokers comprise at least one of the local messaging broker or the downstream messaging broker;

the local messaging broker communicatively couples with a control channel associated with the first network; and

the downstream messaging broker communicatively couples with a control channel associated with one of a second network within which the first network device is located or an intermediate network among one or more intermediate networks between the first network and the second network.

3 . The method of claim 2 , wherein each of the control channel associated with the first network, the control channel associated with the second network, and the control channel associated with the intermediate network is clustered across multiple servers in its respective network.

4 . The method of claim 2 , wherein:

the first network device is determined to be locally accessible by the first broker manager when the first network device is not offline and when a connection to the first network device is not currently lost; and

the one or more brokers further comprise a mediator broker.

5 . The method of claim 4 , wherein the mediator broker comprises at least one of one or more serial line management (“SLM”) mediator brokers, one or more transmission control protocol (“TCP”) mediator brokers, one or more hypertext transfer protocol (“HTTP”) mediator brokers, one or more secure shell protocol (“SSH”) mediator brokers, or one or more simple network management protocol (“SNMP”) mediator brokers.

6 . The method of claim 5 , wherein each of at least one SLM mediator broker among the one or more SLM mediator brokers is configured to mediate multiple connections to multiple client devices regardless of whether the first network device to which it is communicatively coupled is only capable of single client-only connection.

7 . The method of claim 5 , wherein one or more of the client broker, the local messaging broker, the downstream messaging broker, or the mediator broker are modular, wherein the client broker is configured to be interchangeable with other client brokers, each messaging broker is configured to be interchangeable with other messaging brokers, and the mediator broker is configured to be interchangeable with other mediator brokers, wherein the first broker manager is communicatively coupled to and manages at least one of one or more client brokers, one or more messaging brokers, or one or more mediator brokers, wherein each client broker comprises one of a single-port client broker that communicatively couples with a single client device or a multi-port client broker that communicatively couples with each of a plurality of client devices.

8 . The method of claim 2 , further comprising at least one of:

issuing, using the alert manager, a trouble ticket for the first network device;

sending, using the alert manager, a message to a technician to repair at least one of the first network device or a connection to the first network device; or

sending, using the alert manager, an alert associated with the first network device to a fault management system.

9 . The method of claim 1 , wherein:

the first client device is disposed within a fourth network among the plurality of networks;

receiving the request to establish the connection with the first network device from the first client device comprises receiving, using the first broker manager and from the first client device, the request via a second broker manager that is locally coupled with the first client device via its client broker and via an upstream messaging broker that is communicatively coupled with a control channel associated with one of the fourth network or an intermediate network among one or more intermediate networks between the first network and the fourth network, the upstream messaging broker being managed by the first broker manager;

sending or relaying a message to the first client device comprises relaying, using the first broker manager, the message to the first client device via the upstream messaging broker and via the second broker manager; and

relaying a message to the first client device indicating that the first network device is offline or a message to the first device indicating that a connection to the first network device is currently lost comprises relaying the message to the first client device indicating that the first network device is offline or the message to the first device indicating that the connection to the first network device is currently lost via the second broker manager and via the upstream messaging broker.

10 . The method of claim 1 , wherein the stored list is maintained and updated within a network element database (“NED”).

11 . The method of claim 1 , wherein the plurality of networks is separated from each other by firewalls.

12 . The method of claim 1 , wherein the first network device comprises one of a network switch, an intermediary device, a multiservice provisioning platform, a gateway device, a network node, a router, a network security or firewall appliance, a telephone electronic switching system, an optical network switch and routing platform, a wavelength division multiplexing (“WDM”)-based optical transport network system, a network transmission system, a server, or a user device.

13 . The method of claim 1 , wherein:

the stored list comprises a subscription table associated with the first broker manager; and

receiving the request to establish the connection with the first network device from the first client device comprises receiving, using the first broker manager and from the first client device, a subscription request for subscribing to the first network device.

14 . The method of claim 13 , further comprising:

updating, using the first broker manager, the subscription table based at least in part on received status information associated with at least one of the first network device or a connection to the first network device.

15 . A system, comprising:

a computing system that is disposed within a first network among a plurality of networks, the computing system comprising:

a first broker manager;

at least one first processor; and

a first non-transitory computer readable medium communicatively coupled to the at least one first processor, the first non-transitory computer readable medium having stored thereon computer software comprising a first set of instructions that, when executed by the at least one first processor, causes the first broker manager to:

receive, from a first client device, a request to establish a connection with a first network device over at least one network among the plurality of networks;

determining whether the first network device is listed within a stored list;

in response to the determining that the first network device is listed within the stored list, determine whether any alerts associated with the first network device have been received by an alert manager that is communicatively coupled with the first broker manager, and perform, without polling other broker managers regarding a status of the first network device and without attempting to connect to the first network device via one or more brokers that are managed by the first broker manager, at least one of the following:

based on a determination that an alert has been received that indicates that the first network device is offline, sending or relaying a message to the first client device indicating that the first network device is offline; or

based on a determination that an alert has been received that indicates that a connection to the first network device is currently lost, sending or relaying a message to the first client device indicating that the connection to the first network device is currently lost;

in response to the determining that the first network device is not listed within the stored list, perform the following:

forwarding, using the first broker manager, the request via at least one of a local messaging broker or a downstream messaging broker;

after receiving a message from at least one other broker manager that is disposed within the plurality of networks indicating that the first network device is offline, updating, using the first broker manager, the stored list to indicate that the first network device is offline, and sending or relaying, using the first broker manager, a message to the first client device indicating that the first network device is offline; and

after receiving a message from at least one other broker manager that is disposed within the plurality of networks indicating that a connection to the first network device is currently lost, updating, using the first broker manager, the stored list to indicate that the connection to the first network device is currently lost, and sending or relaying, using the first broker manager, a message to the first client device indicating that the connection to the first network device is currently lost.

Assignments (3)
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (SECOND LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0749 →
NOTICE OF GRANT OF SECURITY INTEREST IN INTELLECTUAL PROPERTY (FIRST LIEN) Recorded Nov 4, 2024
From: LEVEL 3 COMMUNICATIONS, LLC; GLOBAL CROSSING TELECOMMUNICATIONS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 069295/0858 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 30, 2024
From: SUTTON, DAVID; TOMS, STEVE; GOLDNER, SHELLEY; HURD, SHELLI L.
To: LEVEL 3 COMMUNICATIONS, LLC
Reel/Frame 068125/0922 →