CARRIER LANDSCAPE FOR SDN NEXT LEVEL OF TELCO INDUSTRILIZATION?

Transcription

1 CARRIER LANDSCAPE FOR SDN NEXT LEVEL OF TELCO INDUSTRILIZATION? Andreas Gladisch, Fritz-Joachim Westphal Deutsche Telekom Innovation Labs

2 COMPLEXITY BY DOZENS OF SPECIALIZED BOXES AND THOUSANDS OF PROTOCOLS. Message Router CDN Session Border Controller WAN Acceleration Video processing DPI Firewall Carrier Grade NAT Tester/QoE monitor Load Balancer SGSN/GGSN PE Router BRAS Radio Network Controller SGW, PGW How can we get rid of the specific boxes, especially gateways & middle-boxes? SDN promised a drastic simplification. 15/11/2013 2

3 Beside complexity, also Vendor lock-in makes live of operators difficult. High platform complexity Vendor lock-in style of eco-systems Vendor #1 Software* Vendor #2 Software* Vendor #X Software* Vendor #1 Hardware Vendor #2 Hardware Vendor #X Hardware New products with modifications of platform only Software implementation by vendor only Limited flexibility, slow implementation, Extended time-to-market 15/11/2013 3

4 DIFFICULT TO EFFICIENTLY REALIZE NETWORK SERVICE INNOVATIONS. 1 2 High complexity of platform architecture Coupling of softand hardware 3 New product with modification of platform only 4 Software implementation by vendor only Limited flexibility, Slow implementation Extended time-tomarket High OpEx 4

5 TRENDS IN IT: ORDER OF MAGNITUDE CHANGES ARE UN-STOPPABLE (JUNIPER S VIEW). 5

6 MODULARIZATION & STANDARIZED INTERFACES. MASSIVE LOWERING OF MARKET AND INNOVATION BARRIER. Today: Monolithic box Multifunctional switch/router/ middle-box Software & controller Split Architecture Network appl. plane OpenFlow controller Data forwarding & processing Forwarding plane Data processing plane Split of software centric and hardware centric part; Split of application and control (software); Split of forwarding and processing (hardware). 6

7 SDN. THE TECHNICAL SOURCES OF THE TREND. How to program forwarding decisions? Academic driven development to control flexibility of forwarding. Example: OpenFlow 1.3 Seamless DC virtualization/orchestr. Fast setup of virtual topologies integrated in virtualization /orchestration. framework Example: Open vswitch OpenStack Can we simplify the middle boxes? Virtual Firewall, virtual Loadbalancer, virtual epc on top of x86. Example: ETSI Group on NFV Missing: Abstraction of process. actions Higher level abstraction/ aggregation of functions Missing: L4-L7 integration Higher level of abstraction Missing: Activities just started Campus networks Enterprise Networks Inner DC SDN DC interconnect Virtualisation of network functions like epc 7

8 MANY USE CASE AREAS IN THE TELCO REALM. Customer Premise Telco Infrastructure 3 rd Party Infrastructure Cloud NW Datacenter Data Center Mobile Radio Network Enterprise & Home Network Access/Aggregation Network Carrier Network Global Packet Core Network = owned and operated by DT = owned and operated by other (e.g. content provider) 8

9 GOOGLE DATA-CENTER INTERCONNECTION Design Príncipes B4 routers built from merchant switch silicon Drive links to 100% utilization Centralized tra ffic engineering Separate hardware from softÿware Challenges Sacrifice hardware fault tolerance, deep buffering, and support for large routing tables. Packet loss becomes inevitable with substantial capacity loss during link/switch failure. No existing protocols for functionality. Requires knowledge about site to site demand and importance. Previously untested development model. Breaks fate sharing between hardware and soÿftware. 15/11/2013 9

10 MANY USE CASE AREAS IN THE TELCO REALM. EXAMPLE: CLOUD NETWORK CE NTRIC SERVICES. Home network Telco infrastucture Global infrastructure Cloud NW Datacenter Datacenter Mobile Radio Network Home Network Access Network Carrier Network Global Packet Core Network 15/11/

11 THERE ARE TO MANY NETWORKS. HARMONIZE ARCHITECTURE OF FIXED, MOBILE AND WIRELESS. Motivation for harmonization Customers using several mobile devices in addition to fixed Count the # of attachment points you use per day! Customers are missing consistent user experience Different network interfaces use entirely different network architectures. Paths from user to the same content converge only deep in the network, if at all. We know the disadvantages in terms of operations, complexity, cost. 11

12 LINUX FOUNDATION PROJECTS RELEVANT FOR TELCOS Carrier Grade LINUX (self telling name: defining requirements) CGL has two main functions. First, interface with network equipment providers & carriers to gather requirements & produce specifications that Linux distribution vendors can implement. Second, to take unimplemented requirements & foster development projects that will meet these requirements & assist in their upstream integration. Yocto (Build System and Production) Yocto provides open source, high-quality infrastructure and tools to help developers create their own custom Linux distributions for any hardware architecture and across multiple market segments. Yocto is intended to provide a helpful starting point for developers. Open Daylight (SDN Applications) With Open Daylight, a community has come together...through the combination of open community developers & open source code & project governance that guarantees an open, community decision making process on business & technical issues. Establishing an open source project in this way is designed to help accelerate the development of technology available to users & enable widespread adoption of Software-Defined Networking. strictly confidential, confidential, internal, public 11/15/

13 SDN STANDARDIZATION. CAN WE ACHIEVE A LINUX LIKE OPEN SOURCE MODEL? streng vertraulich, vertraulich, intern, öffentlich 13

14 RELEVANCE OF OPEN SOURCE SOFTWARE IS INCREASING. MPLS components at : Multitechnology Soft L3/L2 Switch (like OpenVswitch for x86) : SDN library for building recursive controller and data-path elements: Experimental Network Virtualization Vertigo Experimental Network Virtualisation Toolkit 15/11/

15 TODAY S ARCHITECURE. Limited option to optimize placement over time. Programmability in data center only. Service related functionality Replacement & configuration Configuration & customization Programmability Distribution of service functionality Home & enterprise network CPE Access node IP edge Data center 15

16 VISION, ASSUMING SDN PROGRAMMING OF TRANSPORT & SERVICES: SERVICE CHAINING. Flexible service programmability will allow optimised and dynamic placement of recources. Service related functionality Flexible service programmability Distribution of service functionality Home & enterprise network CPE Access node IP edge Data center 16

17 EXAMPLE OF SERVICE CHAINING: ADVANCED VPN L2 or L3 VPN TIED WITH VALUE ADDED SERVICES DMZ handling Mobile access from APN HTTP header enrichment Perimeter protection between corp/guest access Path optimisation NAT Firewall AV scanner Cache Spam filter DPI IPS, IDS Content filtering Internet access gateway Load balancing Traffic shaping Storage Customer s cloud scale-out AAA for each leg DHCP Expandability to VPSs Cloud Client App. Client App. BS Internet Client App. CE DSL Client App. CE CPE Transport infrastructure DataCenter

18 KEY ISSUES FOR OPERATION OF FUTURE NETWORKS: COMBINATION OF DEVELOPER AND OPERATOR Support service velocity by being close to developers DEV Testing and runtime metrics OPS Automation to drive operational excellence Verification, Observability, Activation ITIL etom Service Transition High-velocity releases

19 THE PROMISE OF SDN & VIRTUALIZATION FOR AN OPERATOR. Accelerated Time-to-Market Service Differentiation Improved B2B Positioning Ease of Operations SDN & Virtualization Enhanced Security 19

20 SDN NEXT STEP IN INDUSTRALIZATION 20

21 THANK YOU. WE SHAPE THE FUTURE Telekom Innovation Laboratories 21