Multicast forwarding methods and apparatuses across autonomous systems
US-2024275714-A1 · Aug 15, 2024 · US
US9853881B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9853881-B2 |
| Application number | US-201414263738-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 28, 2014 |
| Priority date | Apr 28, 2014 |
| Publication date | Dec 26, 2017 |
| Grant date | Dec 26, 2017 |
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.
In one embodiment, an autonomous system border router (ASBR) advertises a same forwarding label for received advertised routes of a merging context that were advertised with a same forwarding label for the ASBR to use when sending corresponding packets. An ASBR receives via a routing protocol from a particular router in the same autonomous system, a plurality of same-labeled received routes advertised with a same first forwarding label within a merging context. In response to each of the plurality of same-labeled received routes having the same first forwarding label to use to forward packets to the particular router and being in the same merging context, the ASBR determines a merged forwarding label and advertises to a peer ASBR in another autonomous system (AS) each of the plurality of same-labeled received routes with the merged forwarding label for the peer ASBR to use to forward packets to the ASBR.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving, via a routing protocol by a first autonomous system border router (ASBR) from a particular router in the same autonomous system, a plurality of same-labeled received routes advertised with a same first forwarding label within a merging context; and in response to each of the plurality of same-labeled received routes having the same first forwarding label to use to forward packets to the particular router and being in the same merging context, the first ASBR determines a merged forwarding label and advertises to a peer ASBR in another autonomous system (AS) each of the plurality of same-labeled received routes with the merged forwarding label for the peer ASBR to use to forward packets to the first ASBR, with said advertising each of the plurality of same-labeled received routes with the merged forwarding label meaning that the value of each route of the plurality of same-labeled received route is advertised with the merged forwarding label to the peer ASBR. 2. The method of claim 1 , comprising: receiving, via the routing protocol by the first ASBR from the particular router, a plurality of received different forwarding-labeled advertised routes each with a different forwarding label; and for each particular received different forwarding-labeled advertised route of the plurality of received different forwarding-labeled advertised routes, the first ASBR determining a different second forwarding label and advertising via a routing protocol said particular received different forwarding-labeled advertised route being associated with the different second forwarding label, with each of said second forwarding labels and the merged forwarding label being different. 3. The method of claim 2 , comprising: the first ASBR identifying that each of the plurality of same-labeled received routes are in the merging context based on said advertisement associating each of the plurality of same-labeled received routes with a particular merged-label attribute identifying that they are part of a same merging context. 4. The method of claim 2 , wherein said advertisement of each route of the plurality of same-labeled received routes associates each of the plurality of same-labeled received routes with a merging flag that identifies that said route is a candidate for merging. 5. The method of claim 2 , comprising: the first ASBR identifying that each of the plurality of same-labeled received routes are in the merging context based on their having a same Border Gateway Protocol (BGP) next-hop or a same export route target (RT). 6. The method of claim 2 , wherein the merging context includes each of the plurality of same-labeled received routes advertised being within a same virtual private network (VPN). 7. The method of claim 6 , wherein each of the plurality of same-labeled received routes advertised is a VPN Internet Protocol version 4 (VPN-IPv4) route. 8. The method of claim 2 , comprising: receiving, via a routing protocol by the first ASBR from a second particular router in the same autonomous system, a plurality of additional same-labeled received routes advertised with a same first forwarding label within the merging context; and in response to each of the plurality of same-labeled received routes having the same first forwarding label to use to forward packets to the particular router and being in the same merging context, the first ASBR determining a merged forwarding label and advertising to a peer ASBR in another autonomous system (AS) each of the plurality of same-labeled received routes with the merged forwarding label for the peer ASBR to use to forward packets to the first ASBR. 9. The method of claim 1 , comprising: the first ASBR identifying that each of the plurality of same-labeled received routes are in the merging context based on said advertisement associating each of the plurality of same-labeled received routes with a particular merged-label attribute identifying that they are part of a same merging context. 10. The method of claim 1 , wherein said advertisement of each route of the plurality of same-labeled received routes associates each of the plurality of same-labeled received routes with a merging flag that identifies that said route is a candidate for merging. 11. The method of claim 1 , comprising: receiving, via a routing protocol by the first ASBR from a second particular router in the same autonomous system, a plurality of additional same-labeled received routes advertised with a same first forwarding label within the merging context; and in response to each of the plurality of same-labeled received routes having the same first forwarding label to use to forward packets to the particular router and being in the same merging context, the first ASBR determining a merged forwarding label and advertising to a peer ASBR in another autonomous system (AS) each of the plurality of same-labeled received routes with the merged forwarding label for the peer ASBR to use to forward packets to the first ASBR. 12. A method, comprising: receiving, via a routing protocol by a first autonomous system border router (ASBR) from a particular router in the same autonomous system, a plurality of same-labeled received routes advertised with a same merging group identifier; and in response to each of the plurality of same-labeled received routes having the same merging group identifier, the first ASBR determining a merged forwarding label and advertising to a peer ASBR in another autonomous system (AS) each of the plurality of same-labeled received routes with the merged forwarding label for the peer ASBR to use to forward packets to the first ASBR, with said advertising each of the plurality of same-labeled received routes with the merged forwarding label meaning that the value of each route of the plurality of same-labeled received route is advertised with the merged forwarding label to the peer ASBR. 13. The method of claim 12 , comprising: receiving, via the routing protocol by the first ASBR from the particular router, a plurality of received different forwarding-labeled advertised routes each with a different forwarding label; and for each particular received different forwarding-labeled advertised route of the plurality of received different forwarding-labeled advertised routes, the first ASBR determining a different second forwarding label and advertising via a routing protocol said particular received different forwarding-labeled advertised route being associated with the different second forwarding label, with each of said second forwarding labels and the merged forwarding label being different. 14. A first autonomous system border router (ASBR), comprising: one or more processing elements; memory; a plurality of interfaces that send and receive packets; and one or more packet switching mechanisms that packet switch packets among said interfaces; wherein the first ASBR performs operations, including: receiving, via a routing protocol by an autonomous system border router (ASBR) from a particular router in the same autonomous system, a plurality of same-labeled received routes advertised with a same first forwarding label within a merging context; and in response to each of the plurality of same-labeled received routes having the same first forwarding label to use to forward packets to the particular router and being in the same merging context, the first ASBR determining a merged forwarding label and advertising to a peer ASBR in another autonomous system (AS) each of the plurality of same-labeled received routes with the merged forwarding label for the peer ASBR to use to for
Topology update or discovery · CPC title
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
Interdomain routing, e.g. hierarchical routing · CPC title
using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title
by updating distance vector protocols · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.