Layered Software Defined Networking

  • Sudarshan Maurya
  • Naveen Kumar Tiwari
  • S. C. Gupta
Conference paper
Part of the Lecture Notes in Electrical Engineering book series (LNEE, volume 472)


Over last few decades, computer network has grown exceedingly complex due to advent of newer network protocols and exponential expansion of its size. A new network architecture named software defined networking (SDN) simplifies network by decoupling data plane and control plane. As per SDN, data plane is solely concerned with data forwarding while control plane takes care of logic, processing and management-related functions. But this concept is still evolving; on the other hand, we have witnessed the success of OSI reference architecture and TCP/IP suite. One of the prominent reasons of their success is the layered architecture, where each layer serves its upper layer and uses services of the layer below. On top of that, entire architecture can be viewed as a layered framework allowing proper abstraction and division of responsibilities. Thus, we are proposing seven-layer architectures for software defined networking, viz. physical layer, device link layer, service abstraction layer, worker layer, management layer, presentation layer and application layer. SDN controller consists of three layers, namely service abstraction layer, worker layer and management layer. Device link layer and presentation layer serves as south bound and north bound interfaces, respectively, of the controller. Application layer comprises of applications which are running on the controller, and physical layer consists of physical and/or virtual switches. The key idea of this architecture is to increase cohesion and reduce coupling between the immediate layers.


Software defined networking Network architecture SDN Controller design 


  1. 1.
    Erickson D (2013) The beacon OpenFlow controller, August 16Google Scholar
  2. 2.
  3. 3.
  4. 4.
    Khondoker R, Zaalouk A, Marx R, Bayarou K Feature-based comparison and selection of software defined networking (SDN) controllersGoogle Scholar
  5. 5.
    Yasunobu C, Kazushi S OpenFlow controller architecture for largescale SDN networksGoogle Scholar
  6. 6.
    Dixit A, Hao F, Mukherjee S, Lakshman TV, Kompella R (2013 ) Towards an elastic distributed SDN controller, sigcommGoogle Scholar
  7. 7.
  8. 8.
  9. 9.
    Das S, Parulkar G, McKeown N SDN based unified control architectureGoogle Scholar
  10. 10.
    de Tejada Muntaner GR (2012) Evaluation of OpenFlow controllers, October 15Google Scholar
  11. 11.
    Kepes B (2014) SDN meets the real-world: implementation benefits and challengesGoogle Scholar
  12. 12.
    Lin G (2012) Industry perspectives of SDN: technical challenges and business use casesGoogle Scholar
  13. 13.
    Monaco M, Michel O, Keller E (2013) Applying operating system principles to SDN controller designGoogle Scholar
  14. 14.
    Mogul JC, AuYoung A, Banerjee S, Popa L, Lee J, Mudigonda J, Sharma P, Turner Y (2013) Corybantic: towards the modular composition of SDN control programs, SeptemberGoogle Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2018

Authors and Affiliations

  • Sudarshan Maurya
    • 1
  • Naveen Kumar Tiwari
    • 2
  • S. C. Gupta
    • 3
  1. 1.Government Mahila Engineering CollegeAjmerIndia
  2. 2.Cognizant Technology SolutionsNoidaIndia
  3. 3.IIT DelhiNew DelhiIndia

Personalised recommendations