SP SDN/NFV Use Cases. Mike McBride Sr. Director of Innovation, Huawei. India Symposium, January 31 February 1, 2016, Bangalore. Networking Foundation

Transcription

1 SP SDN/NFV Use Cases Mike McBride Sr. Director of Innovation, Huawei Open 2014 Open Networking Networking Foundation India Symposium, January 31 February 1, 2016, Bangalore

2 This is the year of open source in networking 2

3 Collision of SDO s and open source Standards Open Source 3

4 The New Lifecycle Implementations Use Cases Use Cases Architecture OSS Components Standards OSS Reference Platforms Architecture

5 ONOS Partnership ON.LAB SERVICE PROVIDER PARTNERS VENDOR PARTNERS COLLABORATORS

6 China Unicom Agile VPN Solution VPN application(easy setup fast add/remove VPN Site bandwidth on demand) Restful Java North Bound API ONOS Distributed core South bound API Legacy Protocol OF1.3 Branch 1 P Branch 3 C E Branch 2 PE P P P PE CE Easy Setup ONOS Based Controller Services for VPN User Fast VPN Provision/Deprovision Add/Remove a site Service data consistency is maintained by ONOS (HA) Scale out when more NB APPs run and network increases in size (Scalability) Low latency in network state notification Time/Event based BoD Congestion Control VPN Path Protection

7 CORD Virtualization Sliced Network Infra Slices Residential Virtual infra + ONOS + volt, vcpe, vbng, vcdn 5G Virtual infra + ONOS + mobile edge over multi- RAT 4G Virtual infra + ONOS + mobile edge over multi- RAT Enterprise Virtual infra + ONOS + VPN, TE, vcdn Spin up POD Resources & Services On Demand ONOS (Virtualization, Slicing) + OpenStack (Multi Domain) + XOS Leaf-Spine Fabric Enterprise Metro Ethernet BBUs (Multi- RATs) PON OLT MACs ROADM (Core) Commodity Servers, Storage, Switches, and I/O PODs

8 CORD Roadmap R-CORD Support residential customers over GPON Services: standard (volt, vsg, vrouter) + cloud (CDN) Access rack: OLT white box AT&T field trial: Q1, 2016 Subsequent phases: Q2, Q3, 2016 Production deployment in 2016 E-CORD Support enterprise customers over metro Ethernet Services: standard (VPN, E-Line, E-LAN) + cloud (CDN) Access rack: Ethernet, ROADM POC at ONS in March 2016 Hopefully a trial in Q4, 2016 Potential Collaboration with MEF M-CORD Support mobile customers over multiple RATs Services: standard (mobile VNFs) + mobile edge comp Access: vbbus, disaggregated enodeb POC: ONS in March 2016 Integration with disaggregated enodeb Closed source è Open source Common Infrastructure: servers, fabric, ONOS, OpenStack, XOS, services Open Reference Implementation, Q1, 2016

9 Mobile Edge Problem Statement All traffics are gathered to the center of mobile core: load on backhaul, backbone transport and core systems like SGW/PGW Lack of operator s flexibility for localized customer optimization Deterioration on QoE It is expensive to cope with unpredictable peak traffic Inefficient to have surplus capacity everywhere to handle peak traffic Deploying new infrastructure & services takes long time Traffic surge varies with time and location 9

10 M-Cord POC Scenario Non-Local Traffic Local Video Traffic Local DNS Internet Local EPC Video Cache Mobile CORD Local Communication Traffic Enterprise Intranet Non-local traffic like web and traverse to central core same as before Local video traffic is served by local cache Traffic of Local communication or Intranet is diverted to local network 10

11 IoT Edge Computing over VSER Pull Monitoring Service Republished Service Controller App. Push: Interest{/sensor-service-x: {SensorID=0xabcd Temp=Value} } Sensor-App Sensor Service-x Caching ICN-R Health Service-x Caching ICN-VSER Push MCORD Caching ICN-R Interval : ~1hr User Interval : RT First Responde Personal Health Monitoring Healthcare Provider ICN Allows Push/Pull simultaneous mode, Cache improves Scalability + Reliability of the system Here consumers need to be notified based on their varying criticality E.g. User/First-Responder/Healthcare Provider Less critical consumers can rely on cache while more critical consumers rely on notification. Notifications lost cannot be reproduced, cache helps from this perspective too. Increases the Scalability + Reliability of the IoT system. Interval : 30mins [1] Li, S., Zhang, Y., Raychaudhuri, D., Ravindran, R., Zheng, Q., Wang, GQ., and L. Dong, "IoT Middleware over Information-Centric Network", Global Communications Conference (GLOBECOM) ICN Workshop, 2015.

12 MEF UNITE Program Launched to coordinate internal & external engagement with Open Source Projects, Standards Development Organizations, Associations & to lead the industry migration to agile, assured and orchestrated services.

13 MEF LSO: Lifecycle Service Orchestration Self-service Web Portal Service Provider Business Applications LSO$Capabili+es$ Fulfillment$ $Performance$ $Control$ $Assurance$ Usage$ $Analy+cs$ $Security$ $Policy$ Infrastructure & Element Control & Management Infrastructure & Element Control & Management User Service Endpoint Operator Service Endpoint User Service Endpoint Ethernet Access MPLS Core OTN Core Ethernet Access Network Operator 1 (Retail Service Provider) Operator Virtual Connection Network Operator 2 (Wholesale Access Provider) Operator Virtual Connection End-to-End Network as a Service

14 Third Network Pillars: LSO / SDN / NFV

15 POF - Reinvent Network Data Plane High Level Language Compile Abstract IR Runtime Standard Config/ Runtime interface(s) Programmable Chips match key param. dynamically loaded entry dynamically loaded entry pointe r action (instruction block in POF- FIS) action (instruction block in POF- FIS) dynamically shared global resource (e.g., counter, meter, flow metadata, etc.)

16 What POF promises Flexibility l Match-action pipeline l Match on anything l Customized action Agility l Software-based deployment l Runtime reconfigurable Low Cost l Same device, multiple purpose l Upgrade on software only l Open ecosystem

17 Conclusions Opensource in networking is happening now SDOs and Opensource must collaborate Several compelling use cases 17