UC SDN Use Case
•
0 likes•1,382 views
This document discusses software defined networking (SDN) and its opportunities and use cases for unified communications (UC). SDN allows the separation of the control plane from the forwarding plane, enabling centralized control of network elements. This centralized control allows UC applications to explicitly identify traffic, request quality of service treatments, and prevent network overload through admission control. Specific UC SDN use cases discussed are automated quality of experience (QoE) through dynamic QoS marking, admission control, and dynamic traffic engineering to optimize media paths and class of service bandwidth.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to UC SDN Use Case
Similar to UC SDN Use Case (20)
More from IMTC
More from IMTC (20)
Recently uploaded
Recently uploaded (20)
UC SDN Use Case
- 1. UC SDN Use Case Chris Lauwers—Ubicity Corp.
- 2. •SDN Explained in Two Minutes •Why Should We Care? •SDN Opportunities for Unified Communications •UC SDN Use Cases –Automating QoE –Diagnostics –Orchestration •Automating QoE –Dynamic QoS Marking –Admission Control –Dynamic Traffic Engineering Agenda
- 3. SDN EXPLAINED IN 2 MINUTES
- 4. •Software Defined Networking is: –The physical separation of the network control plane from the forwarding plane –Where a control plane controls several devices. Definition from Open Networking Foundation (ONF) Forwarding Control Forwarding Control Forwarding Control Forwarding Control Forwarding Control
- 5. •Software Defined Networking is: –The physical separation of the network control plane from the forwarding plane –Where a control plane controls several devices. Definition from Open Networking Foundation (ONF) Forwarding Forwarding Forwarding Forwarding Forwarding Logically Centralized Control Plane
- 6. •Controller-Based Network Architecture SDN Architecture SDN North-Bound Interface Network Controller Topology Network Element SDN Protocols SDN Applications Inventory Path Calculation Flow Programming Statistics SDN Applications Network Element Network Element Network Element
- 7. WHY SHOULD WE CARE?
- 8. SDN Benefits for End-User Applications •End-user application programmers have surprisingly little control over the network –Limited to “connect my port to some endpoint” •Application programmers have surprisingly little visibility into the network –Limited to connectivity failures •Available abstractions limited to connectivity Connectivity Connections Addresses Protocols Ports Interfaces Network Element
- 9. NBIs Provide End-to-End Network Abstractions Topology Network Element SDN Protocols Inventory Path Calculation Flow Programming Statistics Network Element Network Element Network Element Performance Packet Loss Jitter Delay Topology Paths Proximity Distance Location Network Graph Status Utilization Congestion Path Status Link Status Trends Error Rates Peak Load Usage Connectivity Connections Addresses Protocols Interfaces Ports Bandwidth
- 10. SDN OPPORTUNITIES FOR UC
- 11. It’s the Network, Stupid •60% to 80% of Quality of Experience (QoE) problems are caused by issues with the underlying network –Improper QoS configuration –Wireless access point issues –Interfaces between networks •Limited troubleshooting support –Because of lack of network visibility •No options for corrective actions –Aside from error concealment
- 12. Allow UC Applications to Communicate with SDN Controllers to: Explicitly identify voice, video, and other UC traffic Versus: •Using dedicated voice VLAN •Network-based application recognition Explicitly requesting QoS treatment for UC traffic on a session-by-session basis Versus “one-size-fits-all” static QoS markings Preventing network overload through centralized admission control Versus per-application call admission control Resolving situations where insufficient bandwidth is available Versus ??? SDN Opportunity: Closing the Loop between Network and UC
- 13. Automated QoE Service Automated QoE API Network Controller Topology Network Element SDN Protocols UC&C Application Inventory Path Calculation Flow Programming Statistics UC&C Application Network Element Network Element Network Element Automated QoE Service Dynamic QoS Marking Admission Control Dynamic Traffic Engineering Policy Administrator Interface
- 14. UC SDN USE CASES
- 15. Automated QoE Service Deployment Options QoS Marking Admission Control Traffic Engineering Option 2 Policy Policy Admission Control QoS Marking Option 1 QoS Marking Policy Mandatory
- 17. Dynamic QoS Marking: Example Configuration Access Switch Automated QoE Service Access Switch AP Wi-Fi UC&C Infrastructure
- 18. UC&C Startup: Install Static QoS Policy for Signaling Traffic Access Switch Automated QoE Service Access Switch Create Policy AP Wi-Fi UC&C Infrastructure
- 19. UC&C Startup: Install Static QoS Policy for Signaling Traffic Access Switch Automated QoE Service Access Switch AP Wi-Fi Set Static QoS Policies UC&C Infrastructure
- 20. Call Setup—Signaling Traffic Receives QoS Treatment Access Switch Automated QoE Service Access Switch AP Wi-Fi BE CS3 CS3 CS3 CS3 CS3 BE CS3 CS3 CS3 CS3 UC&C Infrastructure
- 21. Call Setup—UC&C Requests QoS Treatment for Session Media Access Switch Automated QoE Service Access Switch AP Wi-Fi BE CS3 CS3 CS3 CS3 CS3 BE CS3 CS3 CS3 CS3 UC&C Infrastructure Create Session
- 22. Call Setup—UC&C Requests QoS Treatment for Session Media Access Switch Automated QoE Service Access Switch AP Wi-Fi BE CS3 CS3 CS3 CS3 CS3 BE CS3 CS3 CS3 CS3 UC&C Infrastructure Create Session BE BE BE BE BE BE
- 23. Call Setup—UC&C Requests QoS Treatment for Session Media Access Switch Automated QoE Service Access Switch AP Wi-Fi UC&C Infrastructure BE BE BE BE BE BE Set Session QoS Policies
- 24. Call Setup—UC&C Requests QoS Treatment for Session Media Access Switch Automated QoE Service Access Switch AP Wi-Fi UC&C Infrastructure BE EF EF EF EF BE Set Session QoS Policies EF EF
- 25. UC&C QoS is Secured Access Switch Automated QoE Service Access Switch AP Wi-Fi UC&C Infrastructure BE EF EF EF EF BE EF EF
- 26. Automated QoE API •Session-Based Model –Dynamic –Used for media traffic •Operations session_start(session) session_read(session) session_update(session) session_end (session) session_changed(session, reason) •Policy-Based Model –Static –Used for signaling •Operations policy_add(policy) policy_read(policy) policy_update(policy) policy_delete(policy) 26
- 27. Automated QoE Information Model Session Element Start Time Description Group ID Media Media User Media ° ° ° Session ID User Element User ID User Name Realm Media Element Flow Description QoS Requested Age-Out Timer QoS Granted User ID Flow Element Source IP Address IP Address Type Dest IP Address Transport Dest IP Port Source IP Port QoS Requested Average Bandwidth Application Class Max. Bandwidth Min. Bandwidth QoS Granted Granted Bandwidth Actual Class DSCP
- 28. Dynamic QoS Marking—Control Flow Parse Session For Each Media Element Map Granted CoS to QoS Markings QoS Setup Complete QoS Mapping Apply QoS Markings at Network Ingress Parse Requested CoS for Media Element Determine Granted CoS QoS Policy
- 29. Dynamic QoS Marking—Policy Decisions •Define available Classes of Service •Map Classes of Service to QoS markings •Control access to Classes of Service Parse Session For Each Media Element Map Granted CoS to QoS Markings QoS Setup Complete QoS Mapping Apply QoS Markings at Network Ingress Parse Requested CoS for Media Element Determine Granted CoS QoS Policy
- 31. Admission Control—Control Flow •Centralized –As opposed to per- application –Accounts for all traffic •Accurate topology model –As opposed to administrator- configured Parse Session For Each Media Element Determine Granted CoS and Bandwidth Dynamic QoS Marking Admission Control Policy Calculate Path Parse Requested CoS and Bandwidth No Sufficient BW in CoS Reject Call Yes
- 32. •What action to take when insufficient bandwidth in requested Class of Service: –Grant less than requested –Re-allocate bandwidth by reducing bandwidth for “lower-priority” sessions –Relegate flow to “lower” Class of Service –Relegate flow to Best Efforts –Reject call Admission Control—Policy
- 34. Dynamic Traffic Engineering— Control Flow •TE of CoS Bandwidth •TE of Media Paths No Yes Determine Granted CoS and BW Sufficient BW in CoS For Each Media Element Parse Session Parse Requested CoS and BW Admission Control Policy Calculate Path No Call Resources CoS BW Increased? Alternate Path? Yes No Dynamic CoS Traffic Engineering Traffic Engineering Policy No Yes Dynamic Path Traffic Engineering Dynamic QoS Marking