1 / 14

QoS -aware Network Operating System for Software Defined Networking with Generalized OpenFlows

QoS -aware Network Operating System for Software Defined Networking with Generalized OpenFlows. Kwangtae Jeong , Jinwook Kim and Young- Tak Kim 2012 IEEE/IFIP 4th Workshop on Management of the Future Internet. Outline. Introduction and related work Architecture

danyl
Download Presentation

QoS -aware Network Operating System for Software Defined Networking with Generalized OpenFlows

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. QoS-aware Network Operating System for Software Defined Networking with Generalized OpenFlows KwangtaeJeong, Jinwook Kim and Young-Tak Kim 2012 IEEE/IFIP 4th Workshop on Management of the Future Internet

  2. Outline • Introduction and related work • Architecture • The QoS-aware Network Operating System(QNOX) • Implementation and performance analysis • Conclusion

  3. Introduction and Related Work The SDN allows network operators to manage network elements using software running on an external server. It splits the network into forwarding and control elements, giving the operators more flexibility to configure their network. The OpenFlow framework provides standardized open protocol in switches and routers.

  4. Introduction and Related Work The network operating system (NOX) provides a programming interface with high-level abstractions of network resources. However, it fails in providing the necessary functions for QoS-guaranteed SDN service. In this paper, they proposed a QoS-aware network operating system (QNOX), providing QoS-aware virtual network embedding, end-to-end network QoS assessment, and collaborations among control elements in other domain network.

  5. Architecture SE: Service Element, providing a user interface and receiving the service request from users. CE: Control Element, end-to-end session control, routing path establishment, flow table update. ME: Management Element, resource discovery, virtual overlay network, performance monitoring. CKE: Cognitive Knowledge Element, mapping from virtual network topology to substrate network topology. FE: Forwarding Element, e.g., a switch.

  6. Architecture

  7. QNOX – Resource Discovery • When activating a new FE, an UPnP-based protocol is used to automatically connect to ME. • ME then informs CE, and then CEcalculates a new FIB (forwarding information base) and updates and installs on every FE in this domain. • Traditional shortest path spanning tree algorithm.

  8. QNOX – Resource Discovery

  9. QNOX – Manipulating Service Requests The SE receives service requests with attributes of the required QoS parameters(power of virtual node, delay, jitter, packet error rate, packet loss rate…). SE checks and evaluates the availability of network resources. If the requested QoS level is not available, there may be some negotiation among SE and user. SE also contains the service life-cycle management for the accepted services, and QoE/QoS monitoring modules.

  10. QNOX – Inter-Domain Routing PCE, a Path Computation Element, RFC 4655. Backward recursive PCE-based path computation.

  11. Implementation and Performance Analysis • Using modified Linux IP/MPLS router to emulate FE and CE. • Each element is individually running on a VMware virtual machine. Each 19 FEs are grouped and installed on a PC server. One of the 19 FEs in the group is providing a direct link to the CE. • One CE is configured for a domain network which contains 2~114 FEs.

  12. Implementation and Performance Analysis

  13. Implementation and Performance Analysis

  14. Conclusion A clear architecture that can run on OpenFlow and legacy network devices simultaneously. Need a mechanism that deals with the QoS problem in runtime. Miss some details and issues in this paper. The evaluation is not convincible.

More Related