leading position at various SDN/NFV standardization and research activities 2010 2009 2008 2011 2012 2013 Reliability WG and Management WG Attending from the beginning and lead Reliability WG and Management WG R&D for OpenFlow controller and OpenFlow Switch R&D for OpenFlow controller and OpenFlow Switch NFV ISG Joined (Jan/2008) Joined Stanford Univ. Clean Slate Program (Jan/2008) Open Network Consorthium Open Network Consorthium Open Networking Foundation Open Networking Research Center member Attending as one of founding member Product launched as the world first OpenFlow SDN switch and controller Developed NEC’s unique Programmable Flow technology Open Daylight Gold member Global SDN Standardization activities of NEC ONOS 2014 Contributing carrier grade SDN controller development
in the market Aggregation Switches WDM Packet Transport Home Fiber Office Packet Transport Mobile PC Smartphone Aggregation Switches eNB OLT OLT eNB Core/Metro/ Access EPC, IMS, MVNO-GW, etc. Edge BRAS, SBC, CDN, Security-GW, etc. Microwave Data Centers (1) Data Center SDN Data Center/ Networks IaaS Platforms (2) Network Functions Virtualization vEPC vBRAS vCPE vIMS (3) Transport Packet /Optical SDN Wireless SDN SDN controller E2E Orchestration OSS/BSS
Vendor -B (OF 1.3+) Vendor -D (Non-OF) 10G links 10G links Datacenter Site 1 NEC Transport Network Coordinator Service orchestration Datacenter Site 2 Vendor-C Vendor-A Transport network PF 6800 OF controller PF 6800 OF controller PF 5240 OF switch PF 5240 OF switch NEC VTN web API OIF NBI service/topology API Video client Video server OF 1.3 OF 1.3 ▌ ONF-OIF Transport SDN Interop-2014 5 Carriers, 9 Vendors. ▌ Objectives: Open SDN-interconnect of distributed datacenter sites & multiple transport network WAN domains l Automation, orchestration, virtualization of multi-vendor, multi-layer networks Web client
SDN ▌ Multi-protocol southbound iterface capability - OpenFlow and non-OpenFlow NEC Transport NW Cordinator Controller 1 (Vendor B) Controller 2 (Vendor C) Controller 3 (Vendor A) OF 1.3+ Domain 1 1.A 1.Z Domain 2 2.A 2.Z Domain 3 3.A 3.Z Non-OF Non-OF OIF NBI Controller 4 (Vendor B) Domain 4 4.A 4.Z OF 1.3+ Cordinater: Coordinates multiple domains to provide inter-domain service Controller 1/2/3/4: Controls each domain, provide intra-domain connections NBI: OIF NBI (Service/Topology API) for inter-transport-domain connectivity
transport network l Conventional transport requirements • Important to provide high-integrity connections with pre-assigned routes and bandwidths • Basically no major network configuration changes assumed • IP service layer provides services thru transmission layer being "unaware of transmission" • "Static" operation provided by transport to IP services l Future transport requirements and issues "High-integrity" connection remains important as network infrastructure 1. Automation of network design, provisioning and operation to increase revenue 2. Multi-layer, multi-domain and multi vendor network optimization for OPEX reduction 3. Secure higher reliability and provide flexible availability menu with WAN scalability
transport network ü Increase revenue by reduction of TAT and flexible/efficient service delivery time ü Minimize network facility cost by “total” network optimization to absorb peak time traffic ü Increase revenue by flexibly accommodating diversified inter-DC traffic ü Accomplish prompt and automated network recovery in case of cable cut or major disaster Transport SDN Flexible and automated network operation 1 Issues and new requirements “Multi Layer/Domain/Vender Network Design" Ensure network robustness 2 “Flexible Node Technologies and Software Defined Optics” Network optimization in cooperation with services requirements "Network Virtualization and Programming“ 3
▌ Expansion of contributors and sponsors l Increase in the number of carriers and vendors l Close involvement of community- best of breed ideas l Place to talk real life carriers’ use cases to be implemented ▌ Evolution of functionality l Flexible southbound APIs • Providing the capability for ONOS to be trialed and deployed in multi-vendor environments l Flexible northbound APIs • Driven by requirements from a diversity of use-case and orchestration system developers. l Continued focus on performance and scale leadership • Continue to evaluate performance in different use cases and settings.
expecting ONOS to provide a common carrier-grade platform on which the operators and vendors can build new value-added SDN/NFV solutions for the industry with following Top-3 high level requirements 1. Multi-layer/domain/vender network operation 2. Network virtualization and network programming 3. Highly reliable network with geographical redundant controller ▌ SDN/NFV Industry needs scalable/robust/high performance open source platform for service provider/carrier space.