IP Library Granted Patent US 12,388,741
Granted Patent B2
US 12,388,741 · App. 17/590,285 · Granted Aug 12, 2025

Routing for static border gateway protocol

Inventors: Bradford Sachin Chatterjee (Snohomish, WA); Thomas Bradley Scholl (Seattle, WA); Michael W. Palladino (Renton, WA); Cheng-Jia Lai (Redmond, WA); Christopher Jason Brown (Seattle, WA); Yao Liu (Beijing, CN); Sasha Robbins (Strathfield, AU); Blake Hoelzel (Woodinville, WA); Eric Charles Briffa (Kogarah, AU); Madhura Kale (Seattle, WA); Dennis Marinus (Seattle, WA); Matt Chung (Renton, WA); Ibn Wendell Archer (Issaquah, WA)
Assignee: Amazon Technologies, Inc.
H04L45/04H04L45/02H04L45/74
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,388,741
App. No.
17/590,285
Granted
Aug 12, 2025
Kind
B2
Abstract

A system can determine by which path/tunnel an Internet destination can be best reached for a user with an IP address from a static BGP range. The system looks up the destination address in an egress map. This map can either specify a tunnel that should be used for encapsulation for static BGP, or (when tunnel is not present) cause the system to send out unencapsulated traffic, in which the traffic follows normal BGP routing on a border network.

Claims (44)

1. A computer executable method of providing static Border Gateway Protocol (BGP) routing, the method comprising:

receiving a source IP address;

storing the source IP address in a static BGP pool, wherein the static BGP pool includes a range of IP addresses offered to users by a cloud service provider and the IP addresses within the BGP pool are static prefixes that are designated to use static BGP;

receiving network reachability data for one or more network destination addresses, wherein the network reachability data includes dynamic BGP data paths to reach the one or more network destination addresses;

receiving tunnel information of one or more tunnels;

analyzing the network reachability data and the tunnel information to create a routing map for using static BGP, wherein the routing map for using static BGP includes a destination address and a next-hop address;

receiving a data packet, the data packet including the source IP address and a packet destination IP address;

upon determining that the source IP address is in the static BGP pool, looking up a next-hop address for the packet destination IP address in the routing map, wherein the next-hop address belongs to a static BGP route; and

encapsulating the data packet for transport via a tunnel of the one or more tunnels to the next-hop address.

2. The method of claim 1 , further comprising receiving operational status of each of the one or more tunnels, traffic shift status of endpoints of the one or more tunnels, operational status of one or more devices associated with the one or more tunnels, and a dataset containing reachability information for networks behind the one or more tunnels.

3. The method of claim 2 , wherein creating the routing map for static BGP further includes analyzing the operational status of each of the one or more tunnels, the traffic shift status of the endpoints of the one or more tunnels, the operational status of the one or more devices associated with the one or more tunnels, and the dataset containing reachability information for networks behind the one or more tunnels.

4. The method of claim 2 further comprising:

receiving a change status in the reachability data or the operational status of the one or more devices; and

updating the routing map.

5. The method of claim 4 , wherein updating the routing map includes updating the next-hop address.

6. The method of claim 1 , wherein the packet destination IP address is one of the one or more network destination addresses.

7. The method of claim 1 , wherein the next-hop address causes the data packet to be sent to a transit center using static BGP.

8. A computer-readable medium, which is non-transitory, comprising computer-executable instructions that, when executed, cause a computing system to perform a method comprising:

receiving network reachability data for one or more network destination addresses;

analyzing the network reachability data to create a routing map for static Border Gateway Protocol (BGP) routing;

assigning, by a cloud service provider, a range of IP addresses to users to be used as static BGP addresses;

storing the range of IP addresses in the routing map within the cloud service provider;

receiving an outbound request including an IP address within the range of IP addresses; and

determining that the IP address is within the routing map for static BGP routing and using the routing map to determine a tunnel for which the IP address can be reached.

9. The computer-readable medium of claim 8 , wherein the network reachability data includes dynamic BGP data paths to reach the one or more network destination addresses.

10. The computer-readable medium of claim 8 , further comprising receiving tunnel information of one or more tunnels and operational status of each of the one or more tunnels, and wherein the tunnel information includes a next-hop address.

11. The computer-readable medium of claim 10 , further comprising analyzing the tunnel information of the one or more tunnels and the operational status of each of the one or more tunnels to create the routing map for static BGP routing.

12. The computer-readable medium of claim 8 , further comprising analyzing business logic data to create the routing map for static BGP routing.

13. The computer-readable medium of claim 8 , wherein the routing map for static BGP routing includes a destination address and a next-hop address.

14. A system for providing static Border Gateway Protocol (BGP) routing, the system comprising one or more processors configured to:

assign, by a cloud service provider, a range of IP addresses to a user to be used as static BGP addresses;

store the range of IP addresses in a routing map within the cloud service provider;

receive a data packet, the data packet including a source IP address and a destination IP address;

look up the source IP address in a list of IP addresses that includes the range of IP addresses within the routing map;

upon determining that the source IP address is in the list of IP address, lookup a next-hop address for the destination IP address in the routing map, wherein the next-hop address belongs to a static BGP route; and

encapsulate the data packet for transport via a tunnel to the next-hop address.

15. The system of claim 14 , wherein the next-hop address is a tunnel identification.

16. The system of claim 14 , wherein the routing map is created using at least network reachability data, tunnel information and router status.

17. The system of claim 16 , the one or more processors further configured to:

receive a change status in the reachability data or the router status; and

update the routing map.

18. The system of claim 17 , wherein updating the routing map includes updating the next-hop address.

19. The system of claim 14 , wherein the next-hop address is an interface address at a transit center.

20. The system of claim 14 , wherein the next-hop address causes the data packet to be sent to a transit center using static BGP.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 9, 2022
From: CHATTERJEE, BRADFORD SACHIN; SCHOLL, THOMAS BRADLEY; PALLADINO, MICHAEL W.; LAI, CHENG-JIA; BROWN, CHRISTOPHER JASON; ROBBINS, SASHA; HOELZEL, BLAKE; BRIFFA, ERIC CHARLES; KALE, MADHURA; MARINUS, DENNIS; LIU, YAO; CHUNG, MATT; ARCHER, IBN WENDELL
To: AMAZON TECHNOLOGIES, INC.
Reel/Frame 059356/0785 →
Continuity (1)
Related Publication 20230246943A1 · Aug 3, 2023
References Cited (13)
US 9019973B1 · Shukla · 2015 [cited by examiner]
US 20030039212A1 · Lloyd · 2003 [cited by examiner]
US 20110032843A1 · Papp · 2011 [cited by examiner]
US 20160380823A1 · Shen · 2016 [cited by examiner]
US 20180159790A1 · Wang · 2018 [cited by examiner]
US 20190081925A1 · Gottlieb · 2019 [cited by examiner]
US 20210036887A1 · Meng · 2021 [cited by examiner]
US 20210105209A1 · Tamizkar · 2021 [cited by examiner]
US 20210385155A1 · Suryanarayana · 2021 [cited by examiner]
US 20220045984A1 · Bareket · 2022 [cited by examiner]
WO WO2008092351A1 · 2008 [cited by examiner]
Mohapatra et al., RFC-5512 The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute, Apr. 2009 (Year: 2009). [cited by examiner]
Machine translation of WO 2008/092351 (Year: 2008). [cited by examiner]