IP Library › Granted Patent US 10,715,415
Granted Patent B2
US 10,715,415 · App. 15/825,070 · Granted Jul 14, 2020

Remotely and dynamically injecting routes into an IP network

Inventors: John Tappin (Bellevue, WA); Rahul Amin (Issaquah, WA); Samih Shahin (Redmond, WA); Senad Mrndic (Renton, WA)
Assignee: T-Mobile USA, Inc.
H04L45/02H04L41/0806H04L45/38H04L45/74H04L41/0213H04L61/20
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 10,715,415
App. No.
15/825,070
Granted
Jul 14, 2020
Kind
B2
Abstract

Systems and methods are described herein for remotely and dynamically injecting or installing routes into an Internet Protocol (IP) network. In some embodiments, the systems and methods provide a route injection server as a peer or neighbor node with an IP network. The systems and methods then utilize the route injection server (e.g., remote and dynamic route injection server, or RDRIS) to advertise IP routes to other nodes within the IP network. For example, the RDRIS may send UPDATE messages to other nodes within an IP network, such as via the Border Gateway Protocol (BGP) in order to advertise the IP routes to the other nodes of the IP network.

Claims (38)

1. A method performed within an Internet Protocol (IP) network, the method comprising:

receiving a request at a route injection server to inject a specified IP route to one or more nodes of the IP network;

transmitting, from the route injection server to the one or more nodes of the IP network, an UPDATE message that includes information identifying the specified IP route;

wherein, in response to the UPDATE message, each node of the one or more nodes that meets a specified route injection criteria defined by an entity that transmitted the request to the route injection server:

installs the specified IP route in a routing table associated with the node; and

advertises the installed IP route to other nodes of the IP network;

receiving, at the route injection server, an indication of the advertised IP route from at least one of the one or more nodes that installed the specified IP route in an associated routing table; and

in response to receiving the indication of the advertised IP route, transmitting a notification from the route injection server to the entity that transmitted the request to the route injection server.

2. The method of claim 1 , wherein a first node of the one or more nodes of the IP network, in response to the UPDATE message, installs the specified IP route in the routing table associated with the first node so that:

when a next hop entry of the routing table associated with the first node of the one or more nodes includes a directly attached or connected network that matches first network layer reachability information (NLRI) within the UPDATE message, the first node installs the first NLRI to the routing table associated with the first node without changing the next hop entry; or

when a next hop entry of the routing table associated with the first node of the one or more nodes matches second NLRI of an UPDATE message configured to withdraw an IP route from one or more nodes, the first node deletes the second NLRI from the routing table associated with the first node.

3. The method of claim 1 , wherein the IP network utilizes a border gateway protocol (BGP).

4. The method of claim 1 , wherein the one or more nodes of the IP network include border gateway protocol (BGP) peers within an IP routing network.

5. The method of claim 1 , wherein the receiving a request at a route injection server to inject a specified IP route to one or more nodes of the IP network includes receiving the request from an Internal Operation and Management (OAM) requestor that transmits the request to inject the specified IP route in order to provision routing for applications within the IP network.

6. The method of claim 1 , wherein the receiving a request at a route injection server to inject a specified IP route to one or more nodes of the IP network includes receiving the request from an external server of the entity in order to dynamically change routing paths for mobile devices associated with the entity that are roaming on the IP network.

7. The method of claim 1 , wherein the IP network is a border gateway protocol (BGP) routed network, and the method further comprises:

provisioning the route injection server as a BGP peer within a control plane or application layer of the BGP routed network.

8. The method of claim 1 , wherein the transmitting an UPDATE message that includes information identifying the specified IP route includes transmitting the UPDATE message having a modified next hop field to facilitate injection of the specified IP route.

9. The method of claim 1 , wherein the transmitting an UPDATE message that includes information identifying the specified IP route includes advertising the specified IP route to the one or more nodes of the IP network.

10. At least one non-transitory computer-readable medium, carrying instructions which when executed by at least one data processing platform, implement a method within an Internet Protocol (IP) network, the instructions comprising:

receiving a request at a route injection server to inject a specified IP route to one or more nodes of the IP network;

transmitting, from the route injection server to the one or more nodes of the IP network, an UPDATE message that includes information identifying the specified IP route;

wherein, in response to the UPDATE message, each node of the one or more nodes that meets a specified route injection criteria defined by an entity that transmitted the request to the route injection server:

installs the specified IP route in a routing table associated with the node; and

advertises the installed IP route to other nodes of the IP network;

receiving, at the route injection server, an indication of the advertised IP route from at least one of the one or more nodes that installed the specified IP route in an associated routing table; and

in response to receiving the indication of the advertised IP route, transmitting a notification from the route injection server to the entity that transmitted the request to the route injection server.

11. The computer-readable medium of claim 10 , wherein a first node of the one or more nodes of the IP network, in response to the UPDATE message, installs the specified IP route in the routing table associated with the first node so that:

when a next hop entry of the routing table associated with the first node of the one or more nodes includes a directly attached or connected network that matches first network layer reachability information (NLRI) within the UPDATE message, the first node installs the first NLRI to the routing table associated with the first node without changing the next hop entry; or

when a next hop entry of the routing table associated with the first node of the one or more nodes matches second NLRI of an UPDATE message configured to withdraw an IP route from one or more nodes, the first node deletes the second NLRI from the routing table associated with the first node.

12. The computer-readable medium of claim 10 , wherein the IP network utilizes a border gateway protocol (BGP).

13. The computer-readable medium of claim 10 , wherein the one or more nodes of the IP network include border gateway protocol (BGP) peers within an IP routing network.

14. The computer-readable medium of claim 10 , wherein the receiving a request at a route injection server to inject a specified IP route to one or more nodes of the IP network includes receiving the request from an Internal Operation and Management (OAM) requestor that transmits the request to inject the specified IP route in order to provision routing for applications within the IP network.

15. The computer-readable medium of claim 10 , wherein the receiving a request at a route injection server to inject a specified IP route to one or more nodes of the IP network includes receiving the request from an external server of the entity in order to dynamically change routing paths for mobile devices associated with the entity that are roaming on the IP network.

16. The computer-readable medium of claim 10 , wherein the IP network is a border gateway protocol (BGP) routed network, and the instructions further comprise:

provisioning the route injection server as a BGP peer within a control plane or application layer of the BGP routed network.

17. The computer-readable medium of claim 10 , wherein the transmitting an UPDATE message that includes information identifying the specified IP route includes transmitting the UPDATE message having a modified next hop field to facilitate injection of the specified IP route.

18. The computer-readable medium of claim 10 , wherein the transmitting an UPDATE message that includes information identifying the specified IP route includes advertising the specified IP route to the one or more nodes of the IP network.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Aug 23, 2022
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: IBSV LLC; LAYER3 TV, LLC; PUSHSPRING, LLC; T-MOBILE CENTRAL LLC; T-MOBILE USA, INC.; ASSURANCE WIRELESS USA, L.P.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; SPRINTCOM LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM LLC
Reel/Frame 062595/0001 →
SECURITY AGREEMENT Recorded Apr 2, 2020
From: T-MOBILE USA, INC.; ISBV LLC; T-MOBILE CENTRAL LLC; LAYER3 TV, INC.; PUSHSPRING, INC.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; CLEARWIRE LEGACY LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM L.P.; ASSURANCE WIRELESS USA, L.P.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS
Reel/Frame 053182/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 12, 2018
From: TAPPIN, JOHN; AMIN, RAHUL; SHAHIN, SAMIH; MRNDIC, SENAD
To: T-MOBILE USA, INC.
Reel/Frame 045921/0600 →
Continuity (1)
Related Publication 20190166036A1 · May 30, 2019