Presentation on theme: "Video Services over Software-Defined Networks"— Presentation transcript:
1 Video Services over Software-Defined Networks A. Murat TekalpDecember 6, 2013
2 Outline Recent Trends in Video Recent Trends in Networking High-definition, Ultra-high definition3D VideoRecent Trends in NetworkingP2P VideoOpenFlow-based QoS architectures for VideoImplementation and Test NetworkOpen Problems
3 Recent Trends in Video High-definition Video ITU-R BT x 1080 x 50/60i (Full HD)Ultra high definition videoITU-R BT x 2160 x 50/60pITU-R BT x 4320 x 50/60pStereo videoMulti-view videoviews
5 Recent Trends in Networking Peer-to-Peer (P2P) NetworkingP2P video-on-demandP2P real-time broadcastingSoftware-Defined Networking (SDN)OpenFlow is the first successful implementation of SDN developed by Stanford UniversityStarted to be deployed throughout the world.Video with end-to-end quality of service (QoS)
6 P2P Multicast 3DTV Distribution Network An independent overlay tree for each stream.Clients subscribe only to overlay trees for the streams they want to receive.Synchronization with DVB-stereo broadcast3DTV ClientsMain 3DTVServerOverlay Multicast Content Distribution PeersFP6 NoE 3DTVFP7 Project DIOMEDES
7 SDN Decoupling control and forwarding layers of routing. Open Networking Foundation has been found in for standardization and commercialization of SDN.
8 Why OpenFlow? Centralized network management and control complete, end-to-end network resource visibilityProgrammabilityAbstraction of the underlying networkOpenFlow’s advanced network management capabilities allows sophisticated networking solutionsNetwork VirtualizationEnd-to-end Quality of Service (QoS)Applications inData centersCloud services
9 Existing QoS Mechanisms Several QoS mechanisms have been proposedIntServDiffservMultiprotocol Label Switching (MPLS)Problem: They are built on current Internet’s distributed (hop-by-hop) architecture which cannot have end-to-end network resource information
10 OpenFlow-based Quality of Service We propose two solutions for enabling QoS:priority queuing anddynamic QoS routing (shall be triggered when the QoS requirements are not met by queue management)OpenFlow’s roleproviding complete network resource visibilityinstant management over network devices seamlessly adapting end-to-end network behaviordifferentiate packet types on a per-flow basis
11 Open Problem OpenFlow (v.1.2) only support single controller Single controller does not scale for large and multi-domain OpenFlow networks:single controller may not be able to update flow tables in time due tolimited processing powerlatency introduced by physically distant forwardersthere would be a large volume of traffic towards the controller due to messaging between controller and all forwarders.
12 Distributed QoS Architecture for Large-Scale OpenFlow Networks For network scalability topology aggregationIn our distributed architecture:The overall network is divided into control domains.Each control domain is managed by one (or more) controller,Each controller is responsible forits dedicated intra-domain routingexchanging aggregated information with other controllers to help inter-domain routing.Controllers form a logically centralized control plane using the controller-controller interface.
13 OpenFlow-based QoS architecture Multimedia ServicesService LayerController – Service InterfaceController – Controller InterfaceController – Controller InterfaceControllerControl LayerController – Forwarder InterfaceForwardersForwarding LayerController – Controller Interface allows controllers to share the necessary information to cooperatively manage the whole network in a scalable manner. The single controller architecture does not scale well when the network is large.Controller – Service Interface allows service providers to set flow definitions for new data partitions and even to define new forwarding rules associated with these partitions13
14 OpenFlow-based QoS architecture Flow ManagementCall AdmissionTraffic PolicingController – Controller InterfaceController – Controller InterfaceStandard ControllerTopology ManagementResource ManagementRoute CalculationQueue ManagementControl LayerController – Forwarder InterfaceForwarding LayerForwardersTopology Management function is responsible for discovering and maintaining network connectivity through data received from forwarders.Resource Management function is responsible for determining the availability and collecting up-to-date network state information to aid the route calculation and/or queue management.Queue Management function provides QoS support based on prioritization of queues. One (or more) queues can be attached to a forwarder's physical port, and this function maps flows to pre-configured queues.Flow Management function is responsible for collecting the flow definitions received from the service provider through the controller-service interface, and may allow efficient flow management by aggregating flow definitions.Route Calculation function is responsible for determining routes (e.g. shortest path and QoS routes) for different types of flows. Several routing algorithms can run in parallel to meet the performance requirements and objectives of different flows.14
15 Controller-Controller Interface Features:It opens a semi-permanent TCP connection between controllers to share aggregated inter-domain routing information,ReachabilityQoS parametersLink statusIn the case of link failure or congestion, the interface informs other controllers actively.It periodically collects aggregated topology/state information, distributes and keep them in sync.
16 Control Plane Designs Fully Distributed Control Plane Hierarchically Distributed Control Plane
17 Fully Distributed Control Plane ControllerForwarding DomainControllersare responsible for both intra-domain and inter-domain routingadvertises the aggregated routing information of its domain to other controllerseach controller determines its own inter-domain routes to forward next domain
19 Hierarchically Distributed Control Plane ControllerForwarding DomainSuper ControllerSuper Controllerdetermines inter-domain routingpushes inter-domain routing decisions to controllersControllersare only responsible for intra-domain routingfor inter-domain routing each controller advertises the aggregated routing information to the super controller
20 Hierarchically Distributed Control Plane Super controller’stopological viewstsController
21 Distributed Optimization of QoS Routing Problem instance:stst
22 Application to Scalable Video and Multi-View Video Streaming Videos are encoded into layers;one base layer,one or more enhancement layers.Base layer is important than enhancement layers:Without base layers we cannot watch video, since the video’s enhancement layers depends on base layer.Assuming we get base layer packets, the more enhancement layers we get, the better video quality we receive.
23 OpenQoS Controller Implementation OpenQoS is implemented as an extension of an open-souce controller : Floodlight.Floodlight is written in Java, provides a modular programming environment.OpenQoS controller:periodically collects info on available bandwidth on all linksruns LARAC algorithm to find best route to carry video traffic
26 Conclusions: Open Problems Distributed architectures for OpenFlow-based end-to-end QoS by dynamically optimizing queue management and/or traffic re-routing.Distributed optimization framework for above architecturesController-to-controller interface and controller software to implement the proposed framework with minimum messagingP2P architectures over OpenFlow networksDeployment of an actual OpenFlow test network