A predictive load balancing technique for software defined networked cloud services

Chao Tung Yang, Shuo Tsung Chen, Jung Chun Liu, Yi Wei Su, Deepak Puthal, Rajiv Ranjan

Research output: Contribution to journalArticlepeer-review

17 Scopus citations


With the advent of OpenFlow, the concept of Software-Defined Networking (SDN) becomes much popular. In the past, SDN had often been used for network virtualization; however, with the rise of OpenFlow, which speeds up network performance by separating the control layer from the data layer, SDN can be further used to manage physical network facilities. Currently, some OpenFlow controller providers have already provided users with load balancer packages in their controllers for virtual networks, such as the Neutron package in OpenStack; nevertheless, the existing load balancer packages work in the old fashion that causes extra delay since they poll controllers for every new coming connection. In this paper, we use the wildcard mask to implement the load balance method directly on switches or routers and add a user prediction mechanism to change the range of the wildcard mask dynamically. In this way, the load balance mechanism can be applied conforming to real service situations. In our experiment, we test the accuracies of flow prediction for different predicted algorithms and compare the delay times and balance situations of the proposed method with other load balancers. With the popularity of cloud computing, the demand for cloud infrastructure also increases. As a result, we also apply our load balance mechanism on cloud services and prove that the proposed method can be implemented to varieties of service platforms.

Original languageBritish English
Pages (from-to)211-235
Number of pages25
Issue number3
StatePublished - 12 Mar 2019


  • Cloud services
  • Load balance
  • OpenFlow
  • Prediction mechanism
  • SDN


Dive into the research topics of 'A predictive load balancing technique for software defined networked cloud services'. Together they form a unique fingerprint.

Cite this