HyperFlow: A Distributed Control Plane for OpenFlow

By Yashar Ganjali, Amin Tootoonchian. INM/WREN, 2010

1,075 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/f7bddc08b9d9e2993b363972b89e08e67dd8518b

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Security for 5G and Beyond (2019, background): “For example, the security of the centralized control for resource exhaustion is considered mainly in the form of either increasing its resource capacity [217] or distributing the control planes [212], [213].”
A Survey on Software-Defined Network and OpenFlow: From Concept to Implementation (2014, methodology): “As an example, HyperFlow [132] uses a logically centralized but physically distributed control panel to achieve a synchronized view of the entire SDN.”
Maestro: A System for Scalable OpenFlow Control (2010, unknown): “HyperFlow [18], like Maestro, aims at improving the performance of the OpenFlow control plane.”
A Survey on Software-Defined Wireless Sensor Networks: Challenges and Design Requirements (2017, methodology): “[13] state that to achieve a reliable and robust scalability, the logically distributed controllers should also be physically distributed as in [92].”
Revisiting Traffic Anomaly Detection Using Software Defined Networking (2011, background): “Many SDN controllers are now being developed to manage Openflow compliant switches [20, 23, 33, 29].”
Survey on Network Virtualization Hypervisors for Software Defined Networking (2015, background): “The main motivation for the development of FlowVisor was to provide a hardware abstraction layer that facilitates innovation above and below the virtualization layer.”
On Controller Performance in Software-Defined Networks (2012, unknown): “, [15]) is feasible.”
Software-defined networking (SDN): a survey (2016, methodology): “These scalability solution proposals include DIFANE [16], DevoFlow [39], software-de ﬁ ned counters [40], Onix [41], Kandoo [42], HyperFlow [17], Maestro [33] and NOX-MT [43], which mainly aim at reducing the overhead of the control plane by delegating some work to the forwarding devices or trying…”
Hybrid SDN Networks: A Survey of Existing Approaches (2018, background): “Flowvisor [338], Hyperflow [339], and the Optical Flowvisor [340] are prominent network virtualization approaches for pure SDN networks [93].”
Distributed SDN Control: Survey, Taxonomy, and Challenges (2018, methodology): “Onix [60], Hyperflow [61] and ONOS [58] are typical examples of flat physically-distributed controller platforms which are initially designed to improve control plane scalability through the use of multiple interconnected controllers sharing a global network-wide view and allowing for the developmen”
Combining OpenFlow and sFlow for an effective and scalable anomaly detection and mitigation mechanism on SDN environments (2014, background): “HyperFlow [10] is another distributed event-based control plane that is logically centralized, but physically distributed, which allows network operators to deploy any number of controllers in their networks.”
On scalability of software-defined networking (2013, unknown): “HyperFlow [8], on the other hand, synchronizes network state among multiple controller instances, giving the control applications (running on every controller instance) an illusion of control over the whole network.”
Security in Software Defined Networks: A Survey (2015, unknown): “In SDNs, as the network size and diameter grows, the amount of control trafﬁc destined towards the centralized controller increases and as a result the ﬂow setup time grows [63].”