Metadata-based cross-region segment routing

Patent metadata

Field	Value
Publication number	US-11799755-B2
Application number	US-202117456549-A
Country	US
Kind code	B2
Filing date	Nov 24, 2021
Priority date	Nov 24, 2021
Publication date	Oct 24, 2023
Grant date	Oct 24, 2023

Abstract

Systems and methods are provided for management of network segments that cross geographic regions and/or other types of network divisions in a cloud-based network environment. Gateway may manage traffic across regions using routing metadata that includes a segment identifier. The gateways may also signal their routes across regions based on segment data, and implement the signaled routes using segment-based routing policies. Route selection may be performed using optimization data.

First claim

What is claimed is:

1. A system comprising:
a first gateway node associated with a first geographic region of a provider network, wherein a virtual private cloud-based wide area network is implemented on the provider network and wherein the first gateway node is configured to use a first route table to route traffic associated with a first segment of the virtual private cloud-based wide area network and a second route table to route traffic associated with a second segment of the virtual private cloud-based wide area network, wherein traffic associated with the first segment is isolated from traffic associated with the second segment based at least partly on the first route table being distinct from the second route table; and
a second gateway node associated with a second geographic region of the provider network, wherein the second gateway node is configured to use a third route table to route traffic associated with the first segment and a fourth route table to route traffic associated with the second segment;
wherein the first gateway node is further configured to:
send, to the second gateway node, first routing data representing at least a portion of routes identified in the first route table;
update the first route table based on second routing data, received from the second gateway node, representing at least a portion of routes identified in the third route table;
receive a packet associated with routing metadata representing at least a first source address in the first geographic region, a destination address in the second geographic region, and an identifier of the first segment;
identify the identifier of the first segment in the routing metadata;
determine, based at least partly on an assignment of the identifier directly to the first route table, to route the packet to the second gateway node using the first route table; and
route the packet to the second gateway node using the first route table;

wherein the second gateway node is further configured to:
send the second routing data to the first gateway node;
update the third route table based on the first routing data received from the first gateway node;
receive the packet from the first gateway node; and
route the packet to the destination address using the third route table based at least partly on the identifier of the first segment.

2. The system of claim 1 , wherein the second gateway node is further configured to modify the routing metadata associated with the packet to generate modified routing metadata, wherein the modified routing metadata represents a second identifier associated with the first segment.

3. The system of claim 1 , wherein the first gateway node is further configured to select a path to the destination address from a plurality of paths to the destination address, wherein the path is selected based on at least one of: a number of hops associated with the path, a physical distance between each hop associated with the path, a network latency between each hop associated with the path, a degree of packet loss between each hop associated with the path, a degree of jitter between each hop associated with the path, or a degree of link utilization between each hop associated with the path.

4. The system of claim 1 , further comprising a third gateway node associated with the first geographic region, wherein the third gateway node is configured to use a fifth route table to route traffic associated with the first segment and a sixth route table to route traffic associated with the second segment, wherein the first gateway node is in a first availability zone of the first geographic region, and wherein the third gateway node is in a second availability zone of the first geographic region.

5. A computer-implemented method comprising:
under control of a first gateway node associated with a first geographic region of a provider network:
receiving a packet comprising first routing metadata representing a first destination address and a first segment identifier, wherein the first segment identifier is associated with a first segment of a plurality of segments of a private wide area network implemented on the provider network;
identifying the first segment identifier in the first routing metadata;
determining, based at least partly on an assignment of the first segment identifier directly to a first route table of a plurality of route tables maintained by the first gateway node, to route the packet using the first route table, wherein the first route table is used to route traffic of the first segment, wherein a second route table of the plurality of route tables is used to route traffic of a second segment of the plurality of segments, and wherein traffic associated with the first segment is isolated from traffic associated with the second segment based at least partly on the first route table being distinct from the second route table; and
transmitting the packet based at least partly on first routing data from the first route table, wherein the first routing data is associated with the first destination address.

6. The computer-implemented method of claim 5 , wherein transmitting the packet comprises transmitting the packet to a second gateway node associated with a second geographic region of the provider network.

7. The computer-implemented method of claim 5 , wherein transmitting the packet comprises transmitting the packet to a second gateway node associated with an isolated virtual network in the first geographic region.

8. The computer-implemented method of claim 5 , further comprising modifying the first routing metadata to produce second routing metadata, wherein the second routing metadata comprises a second segment identifier associated with the first segment, wherein the second segment identifier is a region-specific segment identifier associated with the first geographic region.

9. The computer-implemented method of claim 5 , further comprising:
receiving a second packet comprising second routing metadata representing a second destination address and a second segment identifier associated with the first segment;
determining, based at least partly on the second segment identifier, to route the second packet based on the first route table; and
transmitting the second packet based at least partly on second routing data from the first route table, wherein the second routing data is associated with the second destination address.

10. The computer-implemented method of claim 5 , further comprising:
receiving a second packet comprising second routing metadata representing a second destination address and a second segment identifier associated with the second segment;
determining, based at least partly on the second segment identifier, to route the second packet based on the second route table; and
transmitting the second packet based at least partly on second routing data from the second route table, wherein the second routing data is associated with the second destination address.

11. The computer-implemented method of claim 5 , further comprising sending, to one or more other regions of the provider network, second routing data representing at least a portion of routes identified in the first route table, wherein the one or more other regions are associated with the first segment.

12. The computer-implemented method of claim 5 , further comprising updating the first route table based on second routing data, received from a second gateway node in a second region of the provider network, representing at least a portion of routes in a third route table maintained by the second gateway node, wherein the third route table is associated with the first segment.

Assignees

• Amazon Tech Inc

Inventors

• Dawani Anoop
• Deb Bashuman
• Qian Baihu
• Hashmi Omer
• Matthews Nick
• Kulkarni Shridhar
• Spendley Thomas Nguyen
• Pulla Indira Radhika
• Adams David Jonathan
• Lombardi Nicholas Ryan
• Larue Brandon Michael
• Debruin Aaron Scott
• Ali Dousti Ramin

Classifications

• H04L45/02

  Topology update or discovery · CPC title

• H04L45/04 Primary

  Interdomain routing, e.g. hierarchical routing · CPC title

• H04L45/306

  Route determination based on the nature of the carried application · CPC title

• H04L45/44 Primary

  Distributed routing · CPC title

• H04L45/566

  Routing instructions carried by the data packet, e.g. active networks · CPC title