Path continuity determination in an aggregate flow environment
US-2017324625-A1 · Nov 9, 2017 · US
US10506037B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10506037-B2 |
| Application number | US-201615377735-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 13, 2016 |
| Priority date | Dec 13, 2016 |
| Publication date | Dec 10, 2019 |
| Grant date | Dec 10, 2019 |
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.
The present disclosure generally discloses improvements in computer performance in communication networks, which may include improvements in computer performance in supporting discovery of ingress provider edge (PE) devices in a communication network using egress peer engineering (EPE) and software defined networking (SDN). The ingress PE devices of a network may have peering relationships with an egress peer link of an egress peer node of the network. The ingress PE devices may be discovered by identifying a set of traffic flows on an egress peer link of an egress peer node, identifying a set of ingress PE devices that have peering relationships with the egress peer node, determining bandwidth usage information, selecting, from the set of ingress PE devices based on the bandwidth usage information, a set of selected ingress PE devices, and initiating a management action for at least one of the selected ingress PE devices.
Opening claim text (preview).
What is claimed is: 1. An apparatus, comprising: a processor and a memory communicatively connected to the processor, the processor configured to: identify a traffic flow on an egress peer link of an egress peer node; identify a set of ingress provider edge (PE) devices that have peering relationships with the egress peer node; determine, for the ingress PE devices based on respective sets of flow statistics associated with the respective ingress PE devices, respective bandwidth usages of the egress peer link by the respective ingress PE devices for the traffic flow; select, from the set of ingress PE devices based on the respective bandwidth usages of the egress peer link by the respective ingress PE devices for the traffic flow, a selected ingress PE device; and initiate a management action for the selected ingress PE device. 2. The apparatus of claim 1 , wherein, to identify the traffic flow on the egress peer link, the processor is configured to: receive, from the egress peer node, flow statistics associated with the traffic flow on the egress peer link of the egress peer node; and identify the traffic flow based on the flow statistics associated with the traffic flow on the egress peer link of the egress peer node. 3. The apparatus of claim 1 , wherein, to identify the traffic flow on the egress peer link, the processor is configured to: receive, from the egress peer node, a plurality of sets of flow statistics associated with a respective plurality of traffic flows supported by the egress peer link of the egress peer node; and identify the traffic flow, from the plurality of traffic flows supported by the egress peer link of the egress peer node, based on the plurality of sets of flow statistics associated with the respective plurality of traffic flows supported by the egress peer link of the egress peer node. 4. The apparatus of claim 3 , wherein the traffic flow comprises one of the plurality of traffic flows having a largest bandwidth on the egress peer link of the egress peer node. 5. The apparatus of claim 1 , wherein the peering relationship is based on Egress Peer Engineering (EPE). 6. The apparatus of claim 1 , wherein the processor is configured to: obtain, from the respective ingress PE devices, the respective sets of flow statistics associated with the respective ingress PE devices. 7. The apparatus of claim 6 , wherein, to obtain the respective sets of flow statistics associated with the respective ingress PE devices, the processor is configured to: send, toward the respective ingress PE devices, respective flow rules configured to cause the respective ingress PE devices to collect the respective sets of flow statistics for the traffic flow on the egress peer link of the egress peer node; and receive, from the respective ingress PE devices, the respective sets of flow statistics for the traffic flow on the egress peer link of the egress peer node. 8. The apparatus of claim 1 , wherein, to select the selected ingress PE device, the processor is configured to: select, from the set of ingress PE devices, one of the ingress PE devices for which the respective bandwidth usage is largest. 9. The apparatus of claim 1 , wherein, to initiate the management action, the processor is configured to: initiate, for the selected ingress PE device, redirection of the traffic flow from being directed from the selected ingress PE device to the egress peer link of the egress peer node to being directed from the selected ingress PE device to a second egress peer link of the egress peer node or a second egress peer node. 10. The apparatus of claim 9 , wherein, to initiate redirection of the traffic flow, the processor is configured to: send, toward the selected ingress PE device, a set of flow forwarding rules configured to cause the selected ingress PE device to direct traffic of the traffic flow toward the second egress peer link instead of toward the egress peer link of the egress peer node. 11. The apparatus of claim 1 , wherein the apparatus comprises a software defined networking (SDN) controller. 12. A method, comprising: identifying, by a processor, a traffic flow on an egress peer link of an egress peer node; identifying, by the processor, a set of ingress provider edge (PE) devices that have peering relationships with the egress peer node; determining, by the processor for the ingress PE devices based on respective sets of flow statistics associated with the respective ingress PE devices, respective bandwidth usages of the egress peer link by the respective ingress PE devices for the traffic flow; selecting, by the processor from the set of ingress PE devices based on the respective bandwidth usages of the egress peer link by the respective ingress PE devices for the traffic flow, a selected ingress PE device; and initiating, by the processor, a management action for the selected ingress PE device. 13. An apparatus, comprising: a processor and a memory communicatively connected to the processor, the processor configured to: identify a set of traffic flows on an egress peer node; identify a set of ingress provider edge (PE) devices that have peering relationships with the egress peer node; determine bandwidth usage information comprising, for each combination of each of the traffic flows and each of the ingress PE devices, a respective bandwidth usage of the egress peer link by the respective ingress PE device for the respective traffic flow; select, from a set of ingress PE devices based on the bandwidth usage information, a set of selected ingress PE devices; and initiate a management action for one of the selected ingress PE devices.
Peer-to-peer [P2P] networks · CPC title
Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title
Management of faults, events, alarms or notifications · CPC title
Centralised routing · CPC title
Routing software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.