SDN for Network Operators

1,185 views
1,042 views

Published on

Víctor López, Core Network Evolution, Global CTO Unit, Telefonica, 2nd Workshop FIBRE.

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,185
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
88
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

SDN for Network Operators

  1. 1. SDN for Network Operators Víctor López Core Network Evolution Global CTO Unit
  2. 2. Index 01 02 03 04 Core Network Evolution Telefónica I+D, Global CTO Cloud-Ready Transport Networks The SDN Concept SDN for Network Operators Concluding Remarks 2
  3. 3. 01 Cloud-Ready Transport Networks
  4. 4. Cloud-ready Transport Network Approach Cloud services Multilayer Coordination Network Routing, monitoring and automated Photonic network configuration Photonic control plane GMPLS + PCE Flexible Transport Optical Network Network Cross-Stratum Horizontal and Vertical Orchestration IP/MPLS Cross-Stratum Optimization Optimization Routing, monitoring and automated IP configuration Signalling L. M. Contreras, et all: “Towards Cloud-Ready Transport Networks”, in IEEE Communications Magazine, September 2012, Vol. 50, Issue. 9, pp. 48 - 55. Core Network Evolution Telefónica I+D, Global CTO 4
  5. 5. Cloud-ready Network Approach §  The target is an E2E network able to perform automated connectivity control between end users and cloud data centers Cloud Ready Networks rely on two main technological pillars §  This innovative network model aims to: ü  Accelerate service provisioning and performance monitoring ü  Enable on-demand connectivity configurations (e.g bandwidth) by end users Network Control Flexible Transport Network ü  Optimize both cloud costs and power consumption ü  Guarantee the required QoS/QoE (…) for real time and video services Cloud Services Leverage of API NetworkControl Network-Cloud interface: new services development Elasticity & QoS Resource Mngmt E2E MPLS photonic network Flexible transport network IP control and resource allocation (e.g IP v6) IP Forwarding CPE Mobile and Fixed Access Networks E2E MPLS OPTICAL TRANSPORT Core Network Evolution Telefónica I+D, Global CTO 5 Capacity
  6. 6. Traditional core/backbone network operation is very complex and expensive •  Core network operation is not adapted to flexible networking §  Multiple manual configuration actions are needed in core network nodes §  Network solutions from different vendors typically use particularized Network Management System (NMS) implementations §  Very long service provisioning times CURRENT APPROACH FOR NETWORK PROVISIONING Service Management Systems Internet Voice CDN Cloud Business Collection of Umbrella Systems (see next) Network Provisioning Systems Core Network Nodes Core Network Evolution Telefónica I+D, Global CTO Metro NMS IP Core NMS Complex and long workflows for network provisioning over different segments (metro, IP core, Optical transport) requiring multiple configurations over different NMS Optical Transport NMSs NMS NMS NMS NMS NMS NMS NMS NMS Vendor A Vendor B Vendor C Vendor D Vendor E Vendor A Vendor B Vendor C IP IP Metro IP Optical Optical Optical Metro Node Node Node Node Node Node Node Node Vendor A Vendor B Vendor C Vendor D Vendor E Vendor A Vendor B Vendor C 6
  7. 7. Now… Really complex •  Example: Telefonica Spain has 269 management systems and 795 interactions •  Plenty of Proprietary interfaces Core Network Evolution Telefónica I+D, Global CTO 7
  8. 8. Cloud Computing – Hype Cycle Souce: Gartner (2012) Core Network Evolution Telefónica I+D, Global CTO 8
  9. 9. Inter-data center traffic •  Standard cloud migration process in companies: 1.  Virtualization VM VM VM VM VM Hipervisor 2.  Private cloud Autoprovisioning Service Service VM VM VM VM VM 3.  Hybrid cloud Hipervisor Autoprovisioning Autoprovisioning Service Service Service VM VM VM VM VM VM VM VM VM VM Hipervisor Core Network Evolution Telefónica I+D, Global CTO Secure VPN 9 Service Hipervisor
  10. 10. Hybrid Cloud Computing - Elasticity •  Traditional IT and network dimensioning yields to this situations: Over-provisioning Capacity Resources Resources Under-provisioning Capacity •  The network and the cloud must adapt to the end users requirements. t Resources t Capacity t Core Network Evolution Telefónica I+D, Global CTO 10
  11. 11. Cloud Computing imposes new needs to fit by network providers •  Services hosted in datacenters spread at the network border •  Extremely high temporal bandwidth •  •  variability is shown in cloud traffic demand Strong need for high-capacity and ultra-long haul datacenter interconnection Service experience in cloud must be equivalent to the one perceived locally Source: “Towards predictable DC networks”, SIGCOMM, 2011 1Gbps 100Mbps Source: Amazon EC2 performance (http://bit.ly/48Wui) Impact on two main network axis: Capacity and Elasticity Core Network Evolution Telefónica I+D, Global CTO 11
  12. 12. The Vision User-centric connectivity experience To adapt our offer to users necessities A network that delivers the best connectivity experience in an efficient and flexible way Insight capabilities Mouldable infrastructures To understand changes inside-out and be able to decide in real time To cope with quick changes and uncertainty Core Network Evolution Telefónica I+D, Global CTO 12
  13. 13. 02 The SDN Concept
  14. 14. Software Defined Networking SDN Open interfaces (OpenFlow) for instructing the boxes what to do Network equipment as Black boxes FEATURE FEATURE OPERATING SYSTEM FEATURE SPECIALIZED PACKET FORWARDING HARDWARE FEATURE FEATURE FEATURE OPERATING SYSTEM OPERATING SYSTEM SPECIALIZED PACKET FORWARDING HARDWARE SPECIALIZED PACKET FORWARDING HARDWARE FEATURE FEATURE OPERATING SYSTEM SPECIALIZED PACKET FORWARDING HARDWARE SDN Boxes with autonomous behaviour FEATUR E FEATUR E OPERATING SYSTEM FEATUR E FEATUR E SPECIALIZED PACKET FORWARDING HARDWARE OPERATING SYSTEM SPECIALIZED PACKET FORWARDING HARDWARE FEATUR E FEATUR E OPERATING SYSTEM FEATUR E FEATUR E Decisions are taken out of the box SDN SPECIALIZED PACKET FORWARDING HARDWARE OPERATING SYSTEM SPECIALIZED PACKET FORWARDING HARDWARE Simpler OSS to manage the SDN controller Adapting OSS to manage black boxes Core Network Evolution Telefónica I+D, Global CTO 14
  15. 15. The Ossified Network •  Many complex functions •  baked into the infrastructure OSPF, BGP, multicast, differentiated services §  Traffic Engineering, NAT, firewalls, MPLS, redundant layers, … •  An industry with a “mainframe-mentality”, reluctant to change Core Network Evolution Telefónica I+D, Global CTO 15 15  
  16. 16. Extracting Simplicity vs Mastering Complexity Core Network Evolution Telefónica I+D, Global CTO 16
  17. 17. Out of the Boxes •  The network does not need to be •  •  FEATURE OPERATING SYSTEM seen any longer as a composition of individual elements User applications interact with the network controller(s) The network becomes a single entity FEATURE FEATURE SPECIALIZED PACKET FORWARDING HARDWARE OPERATING SYSTEM SPECIALIZED PACKET FORWARDING HARDWARE FEATURE FEATURE SPECIALIZED PACKET FORWARDING HARDWARE •  We can apply different levels of abstraction §  Think of a network design flow §  And even an IDE 17 FEATURE FEATURE OPERATING SYSTEM OPERATING SYSTEM §  Suitable to be programmed §  Aligned with current IT practices Core Network Evolution Telefónica I+D, Global CTO FEATURE SPECIALIZED PACKET FORWARDING HARDWARE
  18. 18. SDN Principles §  Even bypassing conventional layered protocols and their configuration Core Network Evolution Telefónica I+D, Global CTO 18 ." •  •  •  App" SDN Control Plane Software! •  Functions are split between per-packet rules on the switch and high-level decisions at the controller Open interface between control and data plane Open interface to the control plane Controllers actually program the network App" §  Simple packet processing elements (switches) §  Software-based controlling components (controllers) App" App" •  Make network behaviour programmable §  Beyond individual boxes •  Fully decouple data and control planes Switch " Switch" Switch" Switch" Switch"
  19. 19. The SDN Ocean Are w Core Network Evolution Telefónica I+D, Global CTO 19 e crea tin of pro g a new se tocols t ?
  20. 20. Basic SDN Approach for OpenFlow Domains Application Layer API ALTO TED SDN orchestrator OAM Handler         SDN Controller SDN CONTROLLER VNTM PCE Provisioning Manager OPENFLOW   Infrastructure     Layer  (e.g   DataCenter)     Core Network Evolution Telefónica I+D, Global CTO OpenFlow is based on the concept of actions that are applied to each packet of a given flow (Ethernet-level addresses, VLAN tags, IP addresses, MPLS labels or transport-level ports). The actions taken by SDN the controller comprise: inserting and removing tags (layer 2), performing routing (layer 3) and also providing differentiated treatment to packets (QoS) •  •  We can not have a centralized entity to configure all network devices. We need controllers which can talk each other. Is this another control plane? 20
  21. 21. 03 SDN for Network Operators
  22. 22. Which architecture fits in a Network Network Operators? SDN CONTROLLER Big black box controlling the network Centralize functionalities to enable automation Core Network Evolution Telefónica I+D, Global CTO Define simple standard interfaces 22
  23. 23. The path towards a unified network provisioning architecture •  Path towards a unified network provisioning architecture •  Key building block of such unified network provisioning architecture are: §  §  Multiservice provisioning over pseudowires Automated multidomain/vendor/layer operation by signaling Network configuration interface: Multivendor edge nodes configuration (e.g OLT and BRAS, IP core routers, etc) by standard interfaces (e.g OpenFlow) §  IT and network SDN orchestration: Coordinated network and datacenter resources control according to service requirements (e.g orchestrated Virtual Machine transfer among datacenters) §  Network-Service API: Application level API hiding details of the network §  Service Management Systems Internet CDN Cloud Business Network-Service API Multiservice network provisioning system (SDN Orchestrator) Network Provisioning Metro Node Vendor A Core Network Nodes Voice Metro Node Vendor B IP Node Vendor C IP Node Vendor D IP Node Vendor E Optical Node Vendor A Optical Node Vendor B Optical Node Vendor C Standard signaling mechanisms running over network nodes enabling flexible networking and automated network provisioning over different network segments (metro, core IP, optical transport) including multiple vendors Core Network Evolution Telefónica I+D, Global CTO 23 Network configuration interface
  24. 24. SDN controller definition •  NBI Interface to interface applications •  SBI with three main functionalities: GUI/NMS/Application §  Discover network resources North Bound Interface •  Example: IGP, BGP-LS, etc. §  Provision the request SDN Controller •  Ej: OF, PCEP, NetConf, etc. §  Monitor the network. Discovery Provisioning Monitoring Physical Network P. Pan, IPOP 2012 Core Network Evolution Telefónica I+D, Global CTO 24
  25. 25. Main actions to be taken by the SDN controller in E2E networks 1.  Discovery of network resources 2.  Routing, path computation 3.  Automated network orchestration in response to changing network conditions and service requirements 4.  Network resources abstraction to application layer 5.  QoS control and performance monitoring 6.  Multilayer interworking 7.  Multidomain/multivendor network resources provisioning through different control domains (e.g OpenFlow DataCenter, OpenFlow MAN, GMPLS optical transport…) E2E networks might be pure OpenFlow based one day, but the migration process will take some time Core Network Evolution Telefónica I+D, Global CTO 25
  26. 26. SDN controller based on IETF building blocks Applications (Internet, CDN, cloud…) 4- ALTO 3- ABNO controller 1- Topo Mod 2- PCE 5- OAM Handler     6- VNTM     SDN Controller 7- Provisioning Manager OPENFLOW OPENFLOW   OpenFLow   Data   Center     Core Network Evolution Telefónica I+D, Global CTO   OpenFlow   MAN   Domain     NETCONF   IP/MPLS   core     PCEP OPENFLOW   GMPLS   Op7cal   Domains   CLI   OpenFlow   Op7cal   Domain   D. King, et al. “A PCE-based Architecture for Application-based 26 Network Operations”, draft-farrkingel-pce-abno-architecture-06   MPLS   MAN  
  27. 27. Topology Module O. Gonzalez de Dios, V. López, C. Haya, C. Liou, P. Pan, G. Grammel, J. Antich, J.P. Fernández-Palacios: Traffic Engineering Database dissemination for Multi-layer SDN orchestration, in European Conference on Optical Communication (ECOC), Mo. 4.E.2, Sep 2013. •  Topology module has two main functions: §  Import the network state §  Export topologicla information to lements like PCE, VNTM or ALTO. Topology Module Topology Updater Web Service VNTM Information Retriever XML Parser ALTO Server BGP-LS PCE OSPF Network Elements Topology Database IP View Unique Topology Database Interlayer View Transport View Adapters Core Network Evolution Telefónica I+D, Global CTO 27
  28. 28. 04 Concluding Remarks
  29. 29. Key messages 1 Video and cloud computing demands are stressing the network 2 Flexible technologies are mandatory in transport network evolution 3 Horizontal and vertical orchestration allows an automatic network provisioning of network services in layered networks 4 SDN can help to define abstract interfaces for services thus reducing NMS complexity 5 SDN can not be a big black box, thus standard building blocks and interfaces are required and SDN should delegate functionalities to control plane Core Network Evolution Telefónica I+D, Global CTO 29
  30. 30. Core Network Evolution Telefónica I+D, Global CTO 30

×