Method and system for load balancing at a data network
US-9338097-B2 · May 10, 2016 · US
US10356011B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10356011-B2 |
| Application number | US-201614990026-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 7, 2016 |
| Priority date | May 12, 2014 |
| Publication date | Jul 16, 2019 |
| Grant date | Jul 16, 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 claimed subject matter is directed to novel methods and systems for a network topology wherein an Internet Protocol (IP) network is partially integrated and enhanced with a relatively small number of Software Defined Network (SDN)-Openflow (SDN-OF) enabled network devices to provide a resilient network that is able to quickly recover from a network failure and achieves post-recovery load balancing while minimizing cost and complexity. The SDN-OF Controller, or a management node, determines such a minimum set of SDN-OF enabled devices and establishes IP tunnels to route traffic from nodes affected by failure to designated SDN-OF switches and finally to the final destination without looping back to the failed link or node. By combining SDN-OF enabled switches with IP nodes such as routers, a novel network architecture and methods are described herein that allows for ultra-fast and load balancing-aware failure recovery of the data network.
Opening claim text (preview).
What is claimed is: 1. A controller node comprising: a receiver configured to receive network state information including an internet protocol (IP) network topology of a network comprising a plurality of IP nodes and the controller and a bandwidth utilization for each link in the IP network topology; a processor coupled to the receiver and configured to: obtain the network state information including the IP network topology; determine a subset of the IP nodes in an IP network topology to be upgraded to Software Defined Network (SDN) nodes to form a hybrid IP/SDN network configuration that provides network wide SDN path failure protection such that the hybrid IP/SDN network provides network wide SDN path failure protection; and dynamically designate an SDN node for each un-upgraded IP node based on an expected bandwidth utilization after a network entity failure based reroute; and an output interface coupled to the processor and configured to output the hybrid IP/SDN network configuration. 2. The controller node of claim 1 , wherein the output interface comprises a transmitter, and wherein outputting the hybrid IP/SDN network configuration comprises transmitting an SDN capable software module to at least one IP node in the subset of the IP nodes to upgrade the at least one IP node to an SDN node. 3. The controller node of claim 1 , wherein the output interface is configured to display the hybrid IP/SDN network configuration to indicate to a system administrator the subset of the IP nodes to be upgraded to the SDN nodes. 4. The controller node of claim 1 , wherein the processor determines the subset of the IP nodes to be upgraded to the SDN nodes such that for a network entity failure, each IP node coupled to a failed network entity is configured to route data packets to a designated SDN node without traversing the failed network entity. 5. The controller node of claim 4 , wherein there exists at least one intermediate node reachable for the designated SDN node for each possible destination without traversing the failed network entity. 6. The controller node of claim 1 , wherein the processor determines the subset of the IP nodes to be upgraded to the SDN nodes based on a network state change or based on traffic fluctuations. 7. The controller node of claim 1 , wherein the subset of the IP nodes to be upgraded to the SDN nodes is determined such that for a network entity failure, each IP node coupled to a failed network entity is configured to route data packets to N designated SDN nodes without traversing the failed network entity, where N is a value greater than one. 8. The controller node of claim 1 , wherein the output interface is further configured to output control data to an un-upgraded IP node to indicate a corresponding designated SDN node for routing data packets upon network entity failure. 9. The controller node of claim 8 , wherein the output interface is further configured to output control data to the designated SDN node indicating an intermediate node for each destination to support IP tunnel based rerouting between the un-upgraded IP node and the intermediate node via the designated SDN node. 10. A method comprising: determining, by a processor of an Software Defined Network (SDN) controller, a subset of Internet Protocol (IP) nodes in an Internet Protocol (IP) network topology to be upgraded to Software Defined Network (SDN) nodes to create a hybrid IP/SDN network such that the hybrid IP/SDN network provides network wide SDN path failure protection; determining, by the processor of the SDN controller, a designated SDN node for each un-upgraded IP node in the hybrid SDN/IP network, the designated SDN node being reachable by the un-upgraded IP node via an IP tunnel upon a network entity failure; and transmitting, by a transmitter in the SDN controller, control data to each un-upgraded IP node indicating a corresponding designated SDN node. 11. The method of claim 10 , further comprising receiving, by a receiver in the SDN controller, network state information comprising bandwidth utilization for each link in the hybrid SDN/IP network, wherein each designated SDN node is determined based on expected bandwidth utilization after the network entity failure. 12. The method of claim 10 , further comprising transmitting, by the transmitter, control data to the designated SDN node indicating a designated intermediate node for each potential destination to support IP tunnel based rerouting between each corresponding un-upgraded IP node and the potential destination via the designated SDN node. 13. The method of claim 10 , wherein N designated SDN nodes are selected for each un-upgraded IP node to support link utilization weighted hash based rerouting to each of the designated SDN nodes by the corresponding un-upgraded IP node, and wherein N is a value greater than one. 14. The method of claim 10 , wherein the subset of the IP nodes to be upgraded to the SDN nodes is determined such that for the network entity failure, each un-upgraded IP node coupled to a failed network entity is configured to route data packets to a corresponding designated SDN node without traversing the failed network entity. 15. A method for re-routing data due to link failure in a hybrid network, the method comprising: receiving, in a designated Software Defined Network (SDN)-Openflow(SDN-OF) enabled networking device, a plurality of data packets to be routed through a failed networking entity, the plurality of data packets being received from a first networking device corresponding to the failed network entity via an established Internet Protocol (IP) tunnel between the designated SDN-OF enabled networking device and the first networking device, the designated SDN-OF enabled networking device being determined as one of a subset of a plurality of IP nodes in a network to be upgraded to a SDN node based on an IP network topology of the network; receiving a traffic routing configuration indicating an intermediate networking device from an SDN controller; referencing the traffic routing configuration in the designated SDN-OF enabled networking device to determine the intermediate networking device between the designated SDN-OF enabled networking device and a destination node based on an amount of congestion for each candidate intermediate networking device; and forwarding the plurality of data packets from the designated SDN-OF enabled networking device toward the destination node via the intermediate networking device. 16. The method of claim 15 , wherein the designated SDN-OF enabled networking device is one of a plurality of designated SDN-OF enabled networking devices for the first networking device, and wherein the plurality of data packets are routed to the designated SDN-OF enabled networking device based on a weighted hash performed by the first networking device on link utilization of the established IP tunnel. 17. The method of claim 15 , wherein the designated SDN-OF enabled networking device is designated to protect an IP node associated with the failed network entity. 18. The method of claim 15 , wherein the designated SDN-OF enabled networking device is designated dynamically by the SDN controller based on network traffic conditions.
Involving tunnels, e.g. MPLS · CPC title
Error correction, e.g. fault recovery or fault tolerance · CPC title
Routing or path finding in a switch fabric · CPC title
Performing the actions predefined by failover planning, e.g. switching to standby network elements · CPC title
Virtual switches · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.