IP Library Patent Application 18886658
Patent Application
App. No. 18/886,658

NF REROUTING CONTROL IN TELECOMMUNICATIONS NETWORKS

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 None
App. No.
18/886,658
Abstract

Systems and methods of managing network function routing perform or comprise determining that a first network node has been rendered inoperable, wherein the first network node is associated with a first Session Management Function (SMF); retrieving a list of tracking area codes (TACs), the list of TACs corresponding to one or more network components serviced by the first network node via a second network node, wherein the second network node is associated with an Access and Mobility Management Function (AMF); transmitting the list of TACs to a third network node, wherein the third network node is associated with a second SMF; and causing the second network node to clear its cache.

Claims (52)

1 . A method of managing network function routing in a telecommunications network, the method comprising:

determining that a first network node has been rendered inoperable, wherein the first network node is associated with a first Session Management Function (SMF);

retrieving a list of tracking area codes (TACs), the list of TACs corresponding to one or more network components serviced by the first network node via a second network node, wherein the second network node is associated with an Access and Mobility Management Function (AMF);

transmitting the list of TACs to a third network node, wherein the third network node is associated with a second SMF; and

causing the second network node to clear its cache.

2 . The method of claim 1 , wherein the operation of determining that the first network node has been rendered inoperable includes determining that a disaster case scenario has affected the first network node.

3 . The method of claim 1 , further comprising:

after the operation of causing the second network node to clear its cache:

receiving a query from the second network node at a fourth network node, wherein the fourth network node is associated with a Network Repository Function (NRF), and

instructing the second network node to associate with the third network node.

4 . The method of claim 1 , further comprising:

in response to the operation of determining that the first network node has been rendered inoperable, initiating a script, wherein the script is configured to automatically cause performance of the operations of retrieving the list of TACs, transmitting the list of TACs to the third network node, and causing the second network node to clear its cache.

5 . The method of claim 4 , wherein the operation of initiating the script is manually performed by a network operator.

6 . The method of claim 4 , further comprising:

automatically monitoring a connection metric associated with the first network node; and

in response to a determination that the connection metric indicates that the first network node has been rendered inoperable, automatically performing the operation of initiating the script.

7 . The method of claim 1 , wherein the first network node, the second network node, and the third network node are physically located within a same geographical region of the telecommunications network.

8 . A telecommunications network comprising:

at least one processor in communication with a network management node; and

a memory storing instructions that, when executed by the at least one processor, cause the network management node to:

determine that a first network node has been rendered inoperable, wherein the first network node is associated with a first Session Management Function (SMF),

retrieve a list of tracking area codes (TACs), the list of TACs corresponding to one or more network components serviced by the first network node via a second network node, wherein the second network node is associated with an Access and Mobility Management Function (AMF),

transmit the list of TACs to a third network node, wherein the third network node is associated with a second SMF, and

cause the second network node to clear its cache.

9 . The network of claim 8 , wherein the operation of determining that the first network node has been rendered inoperable includes determining that a disaster case scenario has affected the first network node.

10 . The network of claim 8 , wherein the instructions, when executed by the at least one processor, further cause the network management node to:

after the operation of causing the second network node to clear its cache:

receive a query from the second network node at a fourth network node, wherein the fourth network node is associated with a Network Repository Function (NRF), and

instruct the second network node to associate with the third network node.

11 . The network of claim 8 , wherein the instructions, when executed by the at least one processor, further cause the network management node to:

in response to the operation of determining that the first network node has been rendered inoperable, initiate a script, wherein the script is configured to automatically cause performance of the operations of retrieving the list of TACs, transmitting the list of TACs to the third network node, and causing the second network node to clear its cache.

12 . The network of claim 11 , wherein the operation of initiating the script is manually performed by a network operator.

13 . The network of claim 11 , wherein the instructions, when executed by the at least one processor, further cause the network management node to:

automatically monitoring a connection metric associated with the first network node; and

in response to a determination that the connection metric indicates that the first network node has been rendered inoperable, automatically performing the operation of initiating the script.

14 . The network of claim 8 , wherein the first network node, the second network node, and the third network node are physically located within a same geographical region of the telecommunications network.

15 . A non-transitory computer-readable medium storing instructions that, when executed by at least one processor of a network management node in a telecommunications network, cause the network management node to perform operations comprising:

determining that a first network node has been rendered inoperable, wherein the first network node is associated with a first Session Management Function (SMF);

retrieving a list of tracking area codes (TACs), the list of TACs corresponding to one or more network components serviced by the first network node via a second network node, wherein the second network node is associated with an Access and Mobility Management Function (AMF);

transmitting the list of TACs to a third network node, wherein the third network node is associated with a second SMF; and

causing the second network node to clear its cache.

16 . The non-transitory computer-readable medium of claim 15 , wherein the operation of determining that the first network node has been rendered inoperable includes determining that a disaster case scenario has affected the first network node.

17 . The non-transitory computer-readable medium of claim 15 , the operations further comprising:

after the operation of causing the second network node to clear its cache:

receiving a query from the second network node at a fourth network node, wherein the fourth network node is associated with a Network Repository Function (NRF), and

instructing the second network node to associate with the third network node.

18 . The non-transitory computer-readable medium of claim 15 , the operations further comprising:

in response to the operation of determining that the first network node has been rendered inoperable, initiating a script, wherein the script is configured to automatically cause performance of the operations of retrieving the list of TACs, transmitting the list of TACs to the third network node, and causing the second network node to clear its cache.

19 . The non-transitory computer-readable medium of claim 18 , the operations further comprising:

automatically monitoring a connection metric associated with the first network node; and

in response to a determination that the connection metric indicates that the first network node has been rendered inoperable, automatically performing the operation of initiating the script.

20 . The non-transitory computer-readable medium of claim 15 , wherein the first network node, the second network node, and the third network node are physically located within a same geographical region of the telecommunications network.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2025
From: DISH WIRELESS L.L.C.
To: BOOST SUBSCRIBERCO L.L.C.
Reel/Frame 073066/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE TYPOGRAPHICAL ERROR IN THE FIRST NAME OF INVENTOR DAWOOD SHAHDAD PREVIOUSLY RECORDED ON REEL 68626 FRAME 701. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 21, 2025
From: SARATH, ARJUN; MADHAVAN, RAVI; WEBER, KENNETH WILLIAM, JR.; SHAHDAD, MOHAMMAD DAWOOD
To: DISH WIRELESS L.L.C.
Reel/Frame 070292/0485 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 18, 2024
From: SARATH, ARJUN; MADHAVAN, RAVI; WEBER, KENNETH WILLIAM, JR.; SHAHDAD, DAWOOD
To: DISH WIRELESS L.L.C.
Reel/Frame 068626/0701 →