Route advertisement by managed gateways
US-2024380696-A1 · Nov 14, 2024 · US
US2025071054A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2025071054-A1 |
| Application number | US-202418828467-A |
| Country | US |
| Kind code | A1 |
| Filing date | Sep 9, 2024 |
| Priority date | Sep 30, 2020 |
| Publication date | Feb 27, 2025 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A route processing method, implemented by a first device, includes: receiving a first route sent by a second network device, where the first route includes a first identifier; allocating, based on the first identifier, a second identifier corresponding to the first route; and sending a second route to a third network device based on the first route, where the second route includes the second identifier. The second network device is located in a first network domain, and the third network device is located in a second network domain.
Opening claim text (preview).
1 . A route processing method implemented by a first network device and comprising: receiving, from a second network device in a first network domain, a first route comprising a first identifier, wherein the first identifier instructs the first network device to forward a first packet to the second network device, and wherein the first identifier identifies a first service source corresponding to the first route; allocating, based on the first identifier, a second identifier corresponding to the first route, wherein the first identifier is a first Segment Routing over IPv6 (SRv6) segment identifier (SID) and the second identifier is a second Multiprotocol Label Switching (MPLS) label, or the first identifier is a first MPLS label and the second identifier is a second SRv6 SID; and sending, to a third network device in a second network domain and without transferring the first route to a virtual routing and forwarding (VRF) instance, a second route comprising the second identifier. 2 . The route processing method of claim 1 , wherein the first route further comprises an address of the second network device, and wherein the route processing method further comprises further allocating, based on the first identifier and the address, the second identifier. 3 . The route processing method of claim 1 , wherein the first service source comprises a virtual private network (VPN) instance connected to the second network device, an outbound interface on the second network device, or a virtual machine connected to the second network device. 4 . The route processing method of claim 1 , further comprising: receiving, from the second network device, a third route comprising an address of the second network device and a third identifier identifying a second service source; allocating, based on the address and the third identifier, a fourth identifier corresponding to the third route, wherein the third identifier is a third SRv6 SID and the fourth identifier is a fourth MPLS label, or the third identifier is a third MPLS label and the fourth identifier is a fourth SRv6 SID; and sending, to the third network device based on the third route, a fourth route comprising the fourth identifier. 5 . The route processing method of claim 1 , further comprising: receiving, from a fourth network device in the first network domain, a fifth route comprising the first identifier and an address of the fourth network device, wherein the first route and the fifth route have a same prefix address; allocating, to the fifth route based on the first identifier and the address, a fifth identifier instructing the third network device to forward a second packet to the first network device; and sending, to the third network device based on the fifth route, a sixth route comprising the fifth identifier. 6 . The route processing method of claim 1 , further comprising: establishing a correspondence between the first identifier and the second identifier; receiving, from the third network device, the first packet, wherein the first packet comprises the second identifier; updating the first packet based on the second identifier and the correspondence to obtain a second packet comprising the first identifier; and sending, to the second network device, the second packet. 7 . The route processing method of claim 6 , wherein the correspondence is among an address of the second network device, the first identifier, and the second identifier, and wherein the route processing method further comprises: determining the address based on the first identifier and the correspondence; and further sending, to the second network device based on the address, the second packet. 8 . The route processing method of claim 1 , wherein the first network domain uses a first MPLS tunnel and the second network domain uses a second SRv6 tunnel, or the first network domain uses a first SRv6 tunnel and the second network domain uses a second MPLS tunnel. 9 . The route processing method of claim 1 , wherein the first network device comprises a gateway device of a data center or an aggregation device of an Internet Protocol (IP) radio access network (RAN). 10 . The route processing method of claim 1 , wherein the second network device comprises a provider edge (PE) device. 11 . A first network device comprising: a memory configured to store instructions; and one or more processors coupled to the memory and configured to execute the instructions to cause the first network device to: receive, from a second network device in a first network domain, a first route comprising a first identifier, wherein the first identifier instructs the first network device to forward a first packet to the second network device, wherein the first identifier identifies a service source corresponding to the first route, and wherein the first identifier identifies a first service source corresponding to the first route; allocate, based on the first identifier, a second identifier corresponding to the first route, wherein the first identifier is a first Segment Routing over IPv6 (SRv6) segment identifier (SID) and the second identifier is a second Multiprotocol Label Switching (MPLS) label, or the first identifier is a first MPLS label and the second identifier is a second SRv6 SID; and send, to a third network device in a second network domain and without transferring the first route to a virtual routing and forwarding (VRF) instance, a second route comprising the second identifier. 12 . The first network device of claim 11 , wherein the first route further comprises an address of the second network device, and wherein the one or more processors are further configured to execute the instructions to cause the first network device to further allocate, based on the first identifier and the address, the second identifier. 13 . The first network device of claim 11 , wherein the first service source comprises a virtual private network (VPN) instance connected to the second network device, an outbound interface on the second network device, or a virtual machine connected to the second network device. 14 . The first network device of claim 11 , wherein the one or more processors are further configured to execute the instructions to cause the first network device to: receive, from the second network device, a third route comprising an address of the second network device and a third identifier identifying a second service source; allocate, based on the address and the third identifier, a fourth identifier corresponding to the third route, wherein the third identifier is a third SRv6 SID and the fourth identifier is a fourth MPLS label, or the third identifier is a third MPLS label and the fourth identifier is a fourth SRv6 SID; and send, to the third network device based on the third route, a fourth route comprising the fourth identifier. 15 . The first network device of claim 11 , wherein the one or more processors are further configured to execute the instructions to cause the first network device to: receive, from a fourth network device in the first network domain, a fifth route comprising the first identifier and an address of the fourth network device, wherein the first route and the fifth route have a same prefix address; allocate, to the fifth route based on the first identifier and the address, a fifth identifier instructing the third network device to forward a second packet to the first network device; and send, to the third network device based on the fifth route, a sixth route comprising the fifth identifier. 16 . The first network device of claim 11 ,
Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272) · CPC title
Involving tunnels, e.g. MPLS · CPC title
using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title
Interdomain routing, e.g. hierarchical routing · CPC title
Address processing for routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.