Segment routing - egress peer engineering (sp-epe)
US-2015304206-A1 · Oct 22, 2015 · US
US10764173B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10764173-B2 |
| Application number | US-201815862918-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 5, 2018 |
| Priority date | Jul 6, 2015 |
| Publication date | Sep 1, 2020 |
| Grant date | Sep 1, 2020 |
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 controller, including a processor and a non-transitory computer-readable storage medium storing a program to be executed by the processor for managing a first autonomous system (AS), the program including instructions to receive a first Border Gateway Protocol (BGP) routing message, determine a destination node, the destination node belonging to the first AS, determine, according to a node that sends the first BGP routing message, whether to perform incoming-traffic adjustment and control, allocate a source node from a second AS directly connected to the first AS, obtain a preferred path between the source and destination nodes according to a network topology, determine a first BR and a second BR on the preferred path, and send a routing control message to a specified BR belonging to the first AS instructing the specified BR to use the first BR as a next hop for packet forwarding of the second BR.
Opening claim text (preview).
What is claimed is: 1. A controller, comprising: a processor configured to: determine a first border router (BR) and a second BR, wherein the first BR belongs to a first autonomous system (AS) and belongs to an inter-domain topology between BRs of the first AS and a second AS, and the second BR belongs to the second AS and belongs to the inter-domain topology; and a communications interface configured to send a routing control message to the first BR, wherein the routing control message comprises an identifier of the second BR and an AS quantity, wherein the routing control message instructs the first BR to, when advertising a Border Gateway Protocol (BGP) routing message to the second AS, process the BGP routing message according to the identifier of second BR and the AS quantity, wherein the first BR processing the BGP routing message includes increasing the AS quantity in an AS-path attribute value carried in the BGP routing message, and wherein the routing control message is a BGP update message. 2. The controller according to claim 1 , wherein the communications interface is further configured to receive a first BGP routing message from a node of the first AS; wherein the processor is configured to determine the first BR and the second BR comprises: wherein the processor is configured to determine a destination node according to the first BGP routing message, wherein the destination node belongs to the first AS; wherein the processor is further configured to determine, according to the node that sends the first BGP routing message to the controller, whether to perform incoming-traffic adjustment and control; wherein the processor is further configured to allocate a source node from a second AS in response to determining to perform incoming-traffic adjustment and control, wherein the second AS is at least one AS that is directly connected to the first AS; wherein the processor is further configured to obtain a preferred path between the source node and the destination node by using a network topology, wherein the network topology comprises an intra-domain topology of the first AS and the inter-domain topology; and wherein the processor is further configured to determine the first BR and the second BR on the preferred path according to the preferred path. 3. The controller according to claim 2 , wherein the processor being configured to determine, according to the node that sends the first BGP routing message to the controller, whether to perform incoming-traffic adjustment and control comprises the processor being configured to: search a first configuration information table according to the node that sends the first BGP routing message to the controller, as a first match item, to obtain an operation corresponding to the first match item, wherein the obtained operation includes performing the incoming-traffic adjustment and control. 4. The controller according to claim 2 , wherein the processor being configured to determine, according to the node that sends the first BGP routing message to the controller, whether to perform incoming-traffic adjustment and control comprises the processor being configured to: obtain, by the processor, a first destination prefix according to the first BGP routing message; and search, by the processor, a second configuration information table according to the node that sends the first BGP routing message to the controller and the first destination prefix, as a second match item, to obtain an operation corresponding to the second match item, wherein the obtained operation includes performing incoming-traffic adjustment and control. 5. The controller according to claim 2 , wherein the processor being configured to determine the destination node according to the first BGP routing message comprises the processor being configured to: determine whether at least two first BGP routing messages are received; and set, in response to the at least two first BGP routing messages being received, a virtual node in the first AS, and identify the virtual node as the destination node; and wherein the intra-domain topology of the first AS further comprises a link between the destination node and the node that sends the first BGP routing message to the controller. 6. The controller according to claim 2 , wherein the processor being configured to determine the destination node according to the first BGP routing message comprises the processor being configured to: set a virtual node in the first AS, and identify the virtual node as the destination node; wherein the intra-domain topology of the first AS further comprises a link between a border network device of the first AS and the destination node; and wherein the processor being configured to obtain the preferred path between the source node and the destination node comprises the processor being configured to: obtain a first affinity attribute constraint condition according to a link between the node that sends the first BGP routing message to the controller and the destination node; and obtain the preferred path according to the network topology and the first affinity attribute constraint condition. 7. The controller according to claim 2 , wherein the processor being configured to allocate the source node from the second AS comprises the processor being configured to: determine one AS that is directly connected to the first AS to be the second AS; and allocate the source node from the second AS. 8. The controller according to claim 2 , wherein the processor being configured to allocate the source node from the second AS comprises the processor being configured to: search a third configuration information table according to the node that sends the first BGP routing message to the controller, as a first match item, to obtain, a source node corresponding to the first match item, as the source node; or obtain a first destination prefix according to the first BGP routing message, and search a fourth configuration information table according to the node that sends the first BGP routing message to the controller and the first destination prefix, as a second match item, to obtain a source node corresponding to the second match item, as the source node. 9. The controller according to claim 2 , wherein the source node is a BR that is in the second AS and that is directly connected to the first AS, and wherein the inter-domain topology between the BRs of the first AS and the second AS comprises an inter-domain topology between a BR of the first AS and a BR of the second AS. 10. The controller according to claim 9 , wherein the processor is further configured to obtain the inter domain topology, and wherein the processor being configured obtain the inter domain topology comprises the processor being configured to: obtain a direct route of the BR of the first AS by using an Interior Gateway Protocol (IGP) routing message; determine whether the obtained direct route and a link identifier are stored in a match item of a link information configuration table; and establish, according to the link identifier and in response to the obtained direct route and the link identifier being stored in the match item of the link information configuration table, the inter-domain topology between the first AS and an AS that is directly connected to the first AS. 11. The controller according to claim 2 , wherein the source node is a virtual node that is set in the second AS, and the inter-domain topology between the BRs of the first AS and the second AS comprises an inter-domain topology between a BR of the first AS and a BR of the second AS, and further comprises a topology between the source node and the BR of the second AS.
by updating distance vector protocols · CPC title
Interdomain routing, e.g. hierarchical routing · CPC title
using an overlay routing layer · CPC title
by balancing the load, e.g. traffic engineering · CPC title
Distributed routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.