SDN, NFV and their role in 5G - DCA | FEECchesteve/ppt/SIGCOMM16-Tutorial-5G-SD… · ACM SIGCOMM...
Transcript of SDN, NFV and their role in 5G - DCA | FEECchesteve/ppt/SIGCOMM16-Tutorial-5G-SD… · ACM SIGCOMM...
ACM SIGCOMM Tutorial | 2016-08-22 | Page 1
Tutorial
SDN, NFV and their role in 5G
PresentersKatia Obraczka UC Santa Cruz, USA
Christian Rothenberg UNICAMP, Brazil
Ahmad Rostami Ericsson Research, Sweden
ACM SIGCOMM Tutorial | 2016-08-22 | Page 2
Part I (9:00-10:30)
• 5G and the need for programmability • Software Defined Networking (SDN) • Network Function Virtualization (NFV)
Agenda
Part II (11:00-12:30)
• Research Efforts• Use Cases• Q&A
Coffee Break at 10:30 for 30 Min.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 3
› Introduction to 5G: we will present a brief overview of 5G including the reference architecture, opportunities, and challenges.
› SDN & NFV Concepts and their role in 5G: We will present SDN and NFV concepts and how they enable the vision of future 5G networks. Concepts such as network programmability and abstractions as well as network slicing will be introduced.
› SDN & NFV Enabling Technologies: SDN technologies for the control- and data planes will be presented.. Notable examples of APIs for network abstraction and programmability, hardware acceleration, as well as NFV-enabling features such as service function chaining and service personalization will be covered.
› Related Projects and Use Cases: We will briefly overview SDN and NFV efforts that target future 5G networks. We will also present use cases that can benefit from the synergy between SDN and NFV including dynamic service chaining, such as virtualized telecommunication services (e.g., vCPE, vIMS, vEPC, MEC) and NFV in radio access networks.
› Research Challenges and Future Directions: In addition to the challenges in realizing 5G networks, we will further discuss research challenges posed by SDN and NFV including performance monitoring, scalability, management and orchestration, security, portability and heterogeneous network support.
Outline
ACM SIGCOMM Tutorial | 2016-08-22 | Page 4
› Nunes, B. A., Mendonca, M., Nguyen, X. N., Obraczka, K., & Turletti, T. (2014). A survey of software-definednetworking: Past, present, and future of programmable networks. IEEE Communications Surveys & Tutorials.
› Kreutz, D., Ramos, F. M., Esteves Verissimo, P., Esteve Rothenberg, C., Azodolmolky, S., & Uhlig, S. (2015). Software-defined networking: A comprehensive survey. Proceedings of the IEEE.
› Rostami, A., "The Evolution of Programmable Networks: from Active Networks to Software Defined Networks (SDN)," Tutorial presented at 26th International Teletraffic Congress (ITC), 2014.
› Mijumbi, R., Serrat, J., Gorricho, J. L., Latré, S., Charalambides, M., & Lopez, D. (2016). Management andorchestration challenges in network functions virtualization. Communications Magazine, IEEE.
› S. Abdelwahab, B. Hamdaoui, M. Guizani and T. Znati, "Network function virtualization in 5G," in IEEE Communications Magazine, vol. 54, no. 4, pp. 84-91, April 2016.
› Ericsson White paper, "5G system – enabling industry and society transformation," 2015. https://www.ericsson.com/res/docs/whitepapers/what-is-a-5g-system.pdf
› Ericsson Mobility Report 2016. https://www.ericsson.com/res/docs/2016/ericsson-mobility-report-2016.pdf› Ericsson White Paper, “Cellular networks for massive IoT,”
https://www.ericsson.com/res/docs/whitepapers/wp_iot.pdf› Ericsson Technology Review, “A vision of the 5G core: flexibility for new business opportunities.” › Ericsson White Paper, “Cloud RAN – the benefits of virtualization, centralization and coordination,”
https://www.ericsson.com/res/docs/whitepapers/wp-cloud-ran.pdf
References / Literature (1/2)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 5
› I. T. Haque; N. Abu-Ghazaleh. 2016. Wireless Software Defined Networking: a Survey and Taxonomy," in IEEE Communications Surveys & Tutorials.
› Akram Hakiri and Pascal Berthou (2015) . Leveraging SDN for The 5G Networks: Trends, Prospects and Challenges. http://arxiv.org/abs/1506.02876
› Nachikethas A. Jagadeesan and Bhaskar Krishnamachari. 2014. Software-Defined Networking Paradigms in Wireless Networks: A Survey. ACM Comput. Surv.
› Akyildiz I.F., Wang P., Lin S.C. ‘SoftAir: A software defined networking architecture for 5G wireless systems’, Computer Networks 85 (2015) pp.1–18.
› Bradai A., Singh K., Ahmed T., and Rasheed T., ‘Cellular Software Defined Networking: A framework’. IEEE Communications Magazine — Communications Standards Supplement, June 2015, pp. 36-43
› Guerzoni R., Trivisonno R., Soldani D. ‘SDN-Based Architecture and Procedures for 5G Networks’. 5GU 2014, November 26-27, Levi, Finland, DOI 10.4108/icst.5gu.2014.258052
› Mao Yang, Yong Li, Depeng Jin, Lieguang Zeng, Xin Wu, and Athanasios V. Vasilakos. 2015. Software-Definedand Virtualized Future Mobile and Wireless Networks: A Survey. Mob. Netw. Appl. 20, 1
› Nguyen, V., Do, T. & Kim, Y. SDN and Virtualization-Based LTE Mobile Network Architectures: A Comprehensive Survey. Wireless Pers Commun (2016) 86: 1401. doi:10.1007/s11277-015-2997-7
References / Literature (2/2)
5g and the need for programmability
ACM SIGCOMM Tutorial | 2016-08-22 | Page 7
Driving forces behind 5g
Networked Society• Improved User Experience• Massive Traffic Volumes• Massive No. of Connected
Devices• Massive No. of Services
(e.g., IoT)• Transformed Industries
Technical Drivers• Network and Service
automation• Resource & Energy
Efficiency • Virtualization & Clouds• New HW and SW
Technologies (SDN & NFV)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 8
architecture
Transport
Access/Mobility Network Applications
Cloud/DC Infrastructure
Management & Control
IndustryClouds
Devices/IoT
source: Ericsson
ACM SIGCOMM Tutorial | 2016-08-22 | Page 9
Global mobile traffic (monthly ExaBytes)
12X Growth in smartphone traffic
Around 90% of mobile traffic will be from smartphones by the end of 2021
~45% CAGR
source: Ericsson Mobility Report
ACM SIGCOMM Tutorial | 2016-08-22 | Page 10
IOT TO surpass mobile phones in 2018
source: Ericsson Mobility Report
ACM SIGCOMM Tutorial | 2016-08-22 | Page 11
5G
1000xMobile Data
Volumes
10x-100xConnected
Devices 5xLower
Latency10x-100xEnd-user Data
Rates
10xBattery Life for
Low Power Devices
Source: METIS
Evolution Towards 5G
4G3G2G~1990
~2000 ~2010~2020
ACM SIGCOMM Tutorial | 2016-08-22 | Page 12
5gUSE CASES
SMART VEHICLES,TRANSPORT & INFRASTRUCTURE
BROADBAND EXPERIENCE EVERYWHERE, ANYTIME
INTERACTIONHUMAN-IOT
CRITICAL CONTROLOF REMOTE DEVICES
MEDIA EVERYWHERE
source: Ericsson 5G use cases
ACM SIGCOMM Tutorial | 2016-08-22 | Page 13
Diverse Requirements of IOT
source: Ericsson W.P. on cellular networks for massive IoT
ACM SIGCOMM Tutorial | 2016-08-22 | Page 14
One network – multiple industries
@
Several Network Slicessource: Ericsson W.P. on 5G Systems
ACM SIGCOMM Tutorial | 2016-08-22 | Page 15
Network as a service
Resources(Physical & Virtual)
Mobile Broadband
Nomadic Broadband
Industry Automation
Wireline Access
EnterpriseComm.
MassiveSensors/Act.
HealthCare
… …
… …
Network Service Catalog
NFConnectivity
CloudRadio NF
Service Composition Network Slices
Physical Resources (Access, Connectivity, Computing, Storage, …)
Service n
HealthRobotic communication
Premium CommunicationMedia
Mobile BroadbandBasic
source: Ericsson W.P. on 5G Systems
Network Service Orchestration
ACM SIGCOMM Tutorial | 2016-08-22 | Page 16
Network Architecture
Access
Transport Transport
Packet uW OpticalPacket Optical
Aggregation
Radio Cloud
BBU Pool
EPC
Core
Cloud
CoreRadio Access
BBU
ACM SIGCOMM Tutorial | 2016-08-22 | Page 17
Programmability in 5G Networks
Service AgilityShorten the time for service creation and service adaptation
(e.g., scaling).
Service DiversityShare a single
infrastructure among multiple services
with wide range of requirements.
Resource EfficiencyDynamically
allocate the right amount of
resources when and where needed.
High level of flexibility and programmability in individual domains (mobile core, radio access network and transport network).Cross-domain programmability and orchestration.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 18
Programmability in Mobile core
ACM SIGCOMM Tutorial | 2016-08-22 | Page 19
Current Mobile Core Architecture
• A single network architecture for multiple services
• Mix of control and user plane functions
• Appliance-based realization
• Difficult to customize • Scalability
S-GW
MME HSS
PCRFPDNGW
MME: Mobility Management EntityS-GW: Serving GatewayPDN: Packet Data Network PCRF: Policy & Charging Rules FunctionHSS: Home Subscriber Server
Internet
Evolved Packet Core (EPC)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 20
Flexible core architecture
• Separation of control and user-plane functions
• Decompose core functionality into granular functions
• Virtualize functions
• Customize realization per service/slice
• Centralized control functions
• Selective scaling • Utilize Cloud Environment • Flexible placement of functions
Source of fig.: Ericsson Review on 5G Core FlexibilityNetwork Function Virtualization (NFV) is an enabler for programmability in mobile core.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 21
Programmability in RAN
ACM SIGCOMM Tutorial | 2016-08-22 | Page 22
RAN Deployments – I
Core Network
Backhaul
Distributed Baseband
• Flat Architecture • Scaling
• IP connectivity between RAN and Core, and among sites
L3L2L1
ACM SIGCOMM Tutorial | 2016-08-22 | Page 23
RAN Deployments – II
Core Network
Backhaul
FronthaulCPRI
CPRI: Common Public Radio Interface BBU: Baseband processing Unit
Centralized Baseband (C-RAN)• Pooling gains• Efficient network management • Efficient coordination &
interference management• Less network signaling
• Stringent performance requirement on fronthaul (BW, delay and jitter)
• might not be scalable in all 5G scenarios
Need for more flexible split of RAN
BBU Pool
ACM SIGCOMM Tutorial | 2016-08-22 | Page 24
CLOUD RAN
Distributed
L1L2L3
Centralized
L1L2L3
Split 1
L2L3
L1
Split 2
L1L2
L3
Source of fig.: Ericsson W.P. on Cloud RAN
ACM SIGCOMM Tutorial | 2016-08-22 | Page 25
L3L2L1
L3L2L1
L2 lowL1
L3L2 high
Flexibility with cloud ran
Centralization gains as in C-RAN
• Pooling• Network Management• Coordination
Less Transport Requirements
Virtualization gains• Selective scaling (E.g.
User plane vs Control Plane)
• Cloud-based Realization
Collocation of RAN & Core
Source of fig.: Ericsson W.P. on Cloud RAN
ACM SIGCOMM Tutorial | 2016-08-22 | Page 26
Programmability in Transport
ACM SIGCOMM Tutorial | 2016-08-22 | Page 27
Current transport networks
Access Aggregation Core
Packet uW OpticalPacket
OpticalPacket uW Optical
ACM SIGCOMM Tutorial | 2016-08-22 | Page 28
Current transport network ISsues
• Monolithic realization of control and forwarding functions
• Proprietary Management Interfaces
• Complex control and management
• Several technology domains with independent control
• Lengthy and manual service creation/scaling
• Inefficient Resource Utilization
• Inefficient static sharing • Difficult cross-layer optimization
• Application Unaware
ACM SIGCOMM Tutorial | 2016-08-22 | Page 29
Programmable Transport
• Separation of control and forwarding functions
• Define interfaces between control and forwarding
• Open up the control plane for programming
• Develop Efficient sharing mechanisms
• Automation of network and services
• Dynamic creation/update of (virtual) connections/tunnels
• Resource-optimized operation
• Cross-layer optimization (e.g. packet-optical convergence)
• Radio-aware adaptations
Software-Defined Networking (SDN) is an enabler for programmability in transport networks.
Software-Defined Networking
Towards Network Programmability
ACM SIGCOMM Tutorial | 2016-08-22 | Page 31
Outline
› What’s Software-Defined Networking?› Why Software-Defined Networking?› Some History› SDN Architectures› Definitions, Terminology, Concepts› Example Applications
ACM SIGCOMM Tutorial | 2016-08-22 | Page 32
What’s Software-Defined Networking?
ACM SIGCOMM Tutorial | 2016-08-22 | Page 33
Network’s Functional Planes
Source: “Software-Defined Networking: A Comprehensive Survey”, Kreutz et al., https://arxiv.org/pdf/1406.0440.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 34
What’s Software-Defined Networking?
› Main principle: data plane decoupled from control plane.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 35
Why Software-Defined Networking?
› The Internet has been the victim of its own success!
› Extremely hard to configure, manage, and evolve.
› “Vertically integrated”: tight coupling of control- and data planes embedded/distributed in network devices.
› Proliferation of “middleboxes”.
Source: N. McKeown, Stanford, ONF
ACM SIGCOMM Tutorial | 2016-08-22 | Page 36
Why Software-Defined Networking?
Software-Defined Networking to the rescue!
› Separation of control plane from data plane.
– Network control “logically centralized” in the controller.
– Forwarding hardware simplified.
› Programmable networks to facilitate management and control and combat “network ossification”.
› Data plane “commoditization”.
• The Internet has been the victim of its own success!
• Extremely hard to configure, manage, and evolve.
• “Vertically integrated”: tight coupling of control- and data planes embedded/distributed in network devices.
• Proliferation of “middleboxes”.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 37
Software-Defined Networking:Some History
ACM SIGCOMM Tutorial | 2016-08-22 | Page 38
Programmable Networks: Some History
1990’s
Open Signaling
(OPENSIG)
General Switch
Management Protocol
(GSMPv3, RFC 3292, 2002)
Active Networking
User-Programmable
Switches
Capsules
Devolved Control of
ATM (DCAN)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 39
2000’s
4D Project
Separation between
routing and data plane
IETF NETCONF
SNMP successor
ETHANE
SDN predecessor
Programmable Networks: Some History
ACM SIGCOMM Tutorial | 2016-08-22 | Page 40
Software-Defined Networking Architectures
IETF ForCES› Forwarding Element (FE) and Control
Element (CE)› Both reside in the network device› FE and CE communicate using the
ForCES protocol
ONF OpenFlow› Decoupling between control- and
data planes› Controller and switch communicate
using the OpenFlow protocol
ACM SIGCOMM Tutorial | 2016-08-22 | Page 41
ONF OpenFlow Architecture
ACM SIGCOMM Tutorial | 2016-08-22 | Page 42
Source: The Stanford Clean Slate Program, http://cleanslate.stanford.edu
Controller
OpenFlow Switch
FlowTable
SecureChannel
PC
hw
sw
OpenFlow Switch specification
ONF OpenFlow Architecture
IANA port for OpenFlow Switch-Controller connection: 6653
ACM SIGCOMM Tutorial | 2016-08-22 | Page 43
Classifier Action
Modify FieldEnqueue
ForwardNORMALFLOOD
Virtual Port
Physical Port
Forward
Mandatory Action
Optional Action
StatisticsClassifier Action StatisticsClassifier Action Statistics
Classifier Action Statistics
…
Flow TableOF1.0 style
IngressPort
Ethernet
SA DA Type
IP
SA DA Proto
TCP/UDPSrc
VLAN
ID Priority TOS Dst
Virtual Port
ALLCONTROLLER
LOCALTABLE
IN_PORTDrop
Header Fields
Actions
OpenFlow 1.0 Flow Table & Fields
ACM SIGCOMM Tutorial | 2016-08-22 | Page 44
idle_timeoutseconds of no matching packetsafter which the flow is removedzero means never times-out
hard_timeoutseconds after which the flow isremovedzero mean never times-out
If both idle_timeout and hard_timeout are set, then the flow is removed when the first of the two expires.
Each Flow Table entry has two timers:
OpenFlow Table Entries
ACM SIGCOMM Tutorial | 2016-08-22 | Page 45
Evolution path:• OF 1.0 (03/2010): Most widely used version, MAC, IPv4, single table (from Stanford)• OF 1.1 (02/2011): MPLS tags/tunnels, multiple tables, counters (from Stanford)• OF 1.2 (12/2011): IPv6, extensible expression• OF-Config 1.0 (01/2012): Basic configuration: queues, ports, controller assign• OF 1.3.0 (04/2012): Tunnels, meters, PBB support, more IPv6 • OF-Config 1.1 (04/2012): Topology discovery, error handling• OF-Test 1.0 (2H2012): Interoperability conformance test processes, suites, labs• OF 1.3.2 (May 2013), 19 errata, final review • OF 1.4 (Aug. 2013), 9 changes + 13 extensions, More extensible wire protocol, Flow
monitoring, Eviction, Vacancy events, Bundles• OF 1.5.1 (Dec. 2014), Egress Tables, Packet type aware pipeline, Extensible flow entry
statistics
OpenFlow Standards
Source: ONF
ACM SIGCOMM Tutorial | 2016-08-22 | Page 46
SDN: Some Definitions
ACM SIGCOMM Tutorial | 2016-08-22 | Page 47
SDN: Some Definitions
› “The SDN architecture decouples the network control and forwarding functions enabling the network control to become directly programmable and the underlying infrastructure to be abstracted for applications and network services.” Open Networking Foundation (opennetworking.org)
› “Software Defined Networking (SDN) refactors the relationship between network devices and the software that controls them. Opening up the interfaces to programming the network enables more flexible and predictable network control, and makes it easier to extend the network with new functionality.” ACM Sigcomm Simposium on Software-DefinedNetworking Research 2016
ACM SIGCOMM Tutorial | 2016-08-22 | Page 48
SDN refers to software-defined networking architectures where:
• Data- and control planes decoupled from one another.
• Data plane at forwarding devices managed and controlled remotely by a “controller”.
• Well-defined programming interface between control- and data planes.
• Applications running on controller manage and control underlying data plane
SDN architecture
Source: “Software-Defined Networking: A Comprehensive Survey”, Kreutz et al., https://arxiv.org/pdf/1406.0440.
SDN: Definitions, Concepts, and Terminology
ACM SIGCOMM Tutorial | 2016-08-22 | Page 49
› Data plane: network infrastructure consisting of interconnected forwarding devices (a.k.a., forwarding plane).
› Forwarding devices: data plane hardware- or software devices responsible for data forwarding.
› Flow: sequence of packets between source-destination pair; flow packets receive identical service at forwarding devices.
› Flow rules: instruction set that act on incoming packets (e.g., drop, forward to controller, etc)
› Flow table: resides on switches and contains rules to handle flow packets.
Source: “Software-Defined Networking: A Comprehensive Survey”, Kreutz et al., https://arxiv.org/pdf/1406.0440.
SDN: Definitions, Concepts, and Terminology
ACM SIGCOMM Tutorial | 2016-08-22 | Page 50
› Control plane: controls the data plane; logically centralized in the “controller” (a.k.a., network operating system).
› Southbound interface:(instruction set to program the data plane) + (protocol between control- and data planes).
Source: “Software-Defined Networking: A Comprehensive Survey”, Kreutz et al., https://arxiv.org/pdf/1406.0440.
SDN: Definitions, Concepts, and Terminology
ACM SIGCOMM Tutorial | 2016-08-22 | Page 51
SDN: Definitions, Concepts, and Terminology
› Northbound interface: API offered by control plane to develop network control- and management applications.
› Management plane: functions, e.g., routing, traffic engineering, that use control plane functions and API to manage and control network infrastructure. Source:
“Software-Defined Networking: A Comprehensive Survey”, Kreutz et al., https://arxiv.org/pdf/1406.0440.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 52
SDN Applications
› Traffic engineering:– Provide adequate QoS, improve
network utilization, reduce power consumption, balance load.
› Wireless network management/control and mobility support:
– Seamless handover, load balancing, interoperability between heterogeneous networks, dynamic spectrum usage.
› Measurement and monitoring:– Packet sampling, traffic matrix
estimation › Security:
– Firewalling, access control, DoSattack detection/ mitigation, traffic anomaly detection.
› Data-center networking:– Data center QOS and traffic
engineering, fault detection and resilence, dynamic provisioning, security.
Source: “Software-Defined Networking: A Comprehensive Survey”, Kreutz et al., https://arxiv.org/pdf/1406.0440.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 53
ONF recursive SDN architecture
SDN controller B
(Physical) data plane
Manager B
Customer G application
Controller plane (Virtual) data plane (Virtual) data plane
Customer R application
SDN controller G
(Physical) data plane
Manager G
SDN controller R
(Physical) data plane
Manager R
Controller plane
Controller plane (Virtual) data plane
Source: ONF TR-504 : SDN Architecture Overview Version 1.1, https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/TR_SDN-ARCH-Overview-1.1-11112014.02.pdf
ACM SIGCOMM Tutorial | 2016-08-22 | Page 54
NetworkFunction Virtualization(NFV)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 55
Motivation
Source: Why Virtualization is Essential for 5G – Francis Chow (5G Summit 2015)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 56
ProblemStatement
• Complexcarriernetworks– withalargevarietyofproprietarynodesandhardwareappliances
• Launchingnewservicesisdifficultandtakestoolong• Spaceandpowertoaccommodate
– requiresjustanothervarietyofbox,whichneedstobeintegrated• Operationisexpensive
– Rapidlyreachendoflifedueto• existingprocure-design;• integrate-deploycycle
ACM SIGCOMM Tutorial | 2016-08-22 | Page 57
SomeChanges
Source: ETSI NFV ISG – DIRECTION & PRIORITIES – Steven Wright (NFV World Congress 2015)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 58
Transformation
Source: Adapted from D. Lopez Telefonica I+D, NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 59
WhyNFV?
1.Virtualization:Usenetworkresourcewithoutworryingaboutwhereitisphysicallylocated,howmuchitis,howitisorganized,etc.2.Orchestration:Managethousandsofdevices3.Programmable:Shouldbeabletochangebehavioronthefly.4.DynamicScaling:Shouldbeabletochangesize,quantity,asaF(load)5.Automation:Letmachines/softwaredohumans’work6.Visibility:Monitorresources,connectivity7.Performance:Optimizenetworkdeviceutilization8.Multi-tenancy:Slicethenetworkfordifferentcustomers(as-a-Service)9.ServiceIntegration: LetnetworkmanagementplaynicewithOSS/BSS10.Openness: Fullchoiceofmodularplug-insNote:Theseareexactlythesamereasonswhyweneed/wantSDN.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 60
A means to make the network more flexible and simple by minimising dependence on HW constraints
TheNFVConcept
Source: Adapted from D. Lopez Telefonica I+D, NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 61
TheMakingofNFV
Souce:NFVOrchestration|Fuelinginnovationinoperatornetworks - FedericoDescalzo(TMFORUM2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 62
Benefits &Promises of NFV
• Reducedequipmentcosts (CAPEX)– throughconsolidatingequipmentandeconomiesofscaleofITindustry.
• Increasedspeedoftimetomarket– byminimisingthetypicalnetworkoperatorcycleofinnovation.
• Availabilityofnetworkappliancemulti-version andmulti-tenancy,– allowsasingleplatformfordifferentapplications,usersandtenants.
• Enablesavarietyofeco-systems andencouragesopenness.• Encouraginginnovation tobringnewservicesandgeneratenewrevenuestreams.
Source: NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 63
Benefits &Promises of NFV
• Flexibility toeasily,rapidly,dynamicallyprovisionandinstantiatenewservicesinvariouslocations
• Improvedoperationalefficiency• bytakingadvantageofthehigheruniformityofthephysicalnetwork
platformanditshomogeneitytoothersupportplatforms.
• Software-orientedinnovationtorapidlyprototypeandtestnewservicesandgeneratenewrevenuestreams
• Moreservicedifferentiation&customization• Reduced(OPEX)operationalcosts:reducedpower,reduced
space,improvednetworkmonitoring• IT-orientedskillsetandtalent
Source: Adapted from D. Lopez Telefonica I+D, NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 64
ETSINFVArchitecturalFramework
Souce:ETSINFVWhitePaper2
ACM SIGCOMM Tutorial | 2016-08-22 | Page 65
NFV
Source:Viewon5GArchitecture- 5GPPPArchitectureWorkingGroup(2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 66
NFVLayers
NFV Infrastructure
EndPoint
EndPoint
E2E Network Service
Compute Storage NetworkHW Resources
Virtualization LayerVirtualizationSW
Virtual Compute
Virtual Storage
Virtual Network
VirtualResources
LogicalAbstractions
Network Service
VNF VNF VNF
VNF VNF
Logical Links
VNF Instances
VNF VNF VNFSWInstances
VNF:VirtualizedNetworkFunction
VNF
Source: Adapted from D. Lopez Telefonica I+D, NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 67
Rethinkingrelayering
ACM SIGCOMM Tutorial | 2016-08-22 | Page 68
NFVConcepts• NetworkFunction(NF):Functionalbuildingblockwithawelldefinedinterfacesandwelldefined
functionalbehavior• VirtualizedNetworkFunction(VNF):SoftwareimplementationofNFthatcanbedeployedina
virtualizedinfrastructure• VNFSet:ConnectivitybetweenVNFsisnotspecified,
e.g.,residentialgateways• VNFForwardingGraph:Servicechainwhennetworkconnectivityorderisimportant,e.g.,firewall,
NAT,loadbalancer• NFVInfrastructure(NFVI):Hardwareandsoftwarerequiredtodeploy,mangeandexecuteVNFs
includingcomputation,networking,andstorage.• NFVOrchestrator:Automatesthedeployment,operation,management,coordinationofVNFsand
NFVI.
Source: Adapted from Raj Jain
ACM SIGCOMM Tutorial | 2016-08-22 | Page 69
NFVConcepts• NFVIPointofPresence(PoP):LocationofNFVI• NFVI-PoP Network:Internalnetwork• TransportNetwork:NetworkconnectingaPoP tootherPoPs orexternalnetworks• VNFManager:VNFlifecyclemanagemente.g.,instantiation,update,scaling,query,monitoring,fault
diagnosis,healing,termination• VirtualizedInfrastructureManager:Managementofcomputing,storage,network,softwareresources• NetworkService:Acompositionofnetworkfunctionsanddefinedbyitsfunctionalandbehavioral
specification• NFVService:AnetworkservicesusingNFswithatleastoneVNF.
Source: Adapted from Raj Jain
ACM SIGCOMM Tutorial | 2016-08-22 | Page 70
NFVConcepts• UserService:Servicesofferedtoendusers/customers/subscribers.• DeploymentBehavior:NFVIresourcesthataVNFrequires,e.g.,NumberofVMs,memory,disk,
images,bandwidth,latency• OperationalBehavior:VNFinstancetopologyandlifecycleoperations,e.g.,start,stop,pause,
migration,…• VNFDescriptor:Deploymentbehavior+Operationalbehavior
Source: Adapted from Raj Jain
ACM SIGCOMM Tutorial | 2016-08-22 | Page 71
OverviewofETSINFVUseCases
Souce:ETSINFVWhitePaper2
ACM SIGCOMM Tutorial | 2016-08-22 | Page 72
ArchitecturalUseCases
• NetworkFunctions&VirtualisationInfrastructureasaService– Networkfunctionsgocloudlike
• VirtualNetworkFunctionasaService– Ubiquitous,delocalizednetworkfunctions
• VirtualNetworkPlatformasaService– Applyingmulti-tenancyattheVNFlevel
• VNFForwardingGraphs– BuildingE2Eservicesbycomposition
ACM SIGCOMM Tutorial | 2016-08-22 | Page 73
Service-OrientedUseCases• MobilecorenetworkandIMS
– Elastic,scalable,moreresilientEPC– Speciallysuitableforaphasedapproach
• Mobilebasestations– EvolvedCloud-RAN– EnablerforSON
• Homeenvironment– L2visibilitytothehomenetwork– Smoothintroductionofresidentialservices
• CDNs– Betteradaptabilitytotrafficsurges– Newcollaborativeservicemodels
• Fixedaccessnetwork– Offloadcomputationalintensiveoptimization– Enableon-demandaccessservices
ACM SIGCOMM Tutorial | 2016-08-22 | Page 74
NFVFrameworkRequirements
1.General:PartialorfullVirtualization,Predictableperformance2.Portability: Decoupledfromunderlyinginfrastructure3.Performance:ConformingandproportionaltoNFsspecificationsandfacilitiestomonitor4.Elasticity:ScalabletomeetSLAs.Movabletootherservers.5.Resiliency:Beabletorecreateafterfailure.Specifiedpacketlossrate,callsdrops,timetorecover,etc.6.Security:Role-basedauthorization,authentication7.ServiceContinuity:Seamlessornon-seamlesscontinuityafterfailuresormigration
ACM SIGCOMM Tutorial | 2016-08-22 | Page 75
NFVFrameworkRequirements
8.ServiceAssurance:TimestampandforwardcopiesofpacketsforFaultdetection9.EnergyEfficiencyRequirements:ShouldbepossibletoputasubsetofVNFinapowerconservingsleepstate10.OperationalandManagementRequirements:Incorporatemechanismsforautomationofoperationalandmanagementfunctions11.Transition:CoexistencewithLegacyandInteroperabilityamongmulti-vendorimplementations12.ServiceModels:OperatorsmayuseNFVinfrastructureoperatedbyotheroperators
...
ACM SIGCOMM Tutorial | 2016-08-22 | Page 76
Challenging Pathupfront:Not assimple ascloud applied to telco
The network differs from the computing environment in 2 key factors…
Dataplaneworkloads(whicharehuge!)
Networkrequiresshape(+E2Einterconnection)
HIGHPRESSUREONPERFORMANCE
GLOBALNETWORKVIEWISREQUIREDFORMANAGEMENT
1
2
…whicharebigchallengesforvanillacloudcomputing.ANADAPTEDVIRTUALISATIONENVIRONMENTISNEEDED
TOOBTAINCARRIER-CLASS BEHAVIOUR
Source: Adapted from D. Lopez Telefonica I+D, NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 77
TheRoadtoNFV
Source:GabrielBrown,HeavyReading
ACM SIGCOMM Tutorial | 2016-08-22 | Page 78
Fatvs.fitVNFs
Source: SDN and NFV Stepping Stones to the Telco Cloud – Prodip Sen (ONS 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 79
AlternativeoptionstovirtualizeNFVapps
ACM SIGCOMM Tutorial | 2016-08-22 | Page 80
PerformanceChallenges
Souce:ETSINFVWhitePaper2
ACM SIGCOMM Tutorial | 2016-08-22 | Page 81
PortabilityChallenges
Source:AdaptedfromD.LopezTelefonica I+D,NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 82
IntegrationChallenges
Source:AdaptedfromD.LopezTelefonica I+D,NFV
ACM SIGCOMM Tutorial | 2016-08-22 | Page 83
ElasticityChallenges
Source:UNIFYProjectResults
ACM SIGCOMM Tutorial | 2016-08-22 | Page 84
Management&OrchestrationChallenges
Source:IEEEPIMRC,2013
ACM SIGCOMM Tutorial | 2016-08-22 | Page 85
NFV&SDN
Source: SDN and NFV Stepping Stones to the Telco Cloud – Prodip Sen (ONS 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 86
SDN&NFV• SDNand NFVdoNOTdepend on each other
Source:UweMichel, T-Systems
ACM SIGCOMM Tutorial | 2016-08-22 | Page 87
NFVvs SDNSDN›››flexible forwarding &steering of traffic inaphysical orvirtualnetworkenvironment[NetworkRe-Architecture]
NFV›››flexible placement ofvirtualized networkfunctions acrossthe network&cloud[ApplianceRe-Architecture](initially)
›››SDN&NFVarecomplementarytoolsforachieving full networkprogrammability
ACM SIGCOMM Tutorial | 2016-08-22 | Page 88
Flexibility with SDN&NFV
Source: Ahmad Rostami, Ericsson Research (Kista): http://www.itc26.org/fileadmin/ITC26_files/ITC26-Tutorial-Rostami.pdf
ACM SIGCOMM Tutorial | 2016-08-22 | Page 89
SDN&NFVConvergence
Source: SDN and NFV Stepping Stones to the Telco Cloud – Prodip Sen (ONS 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 90
5G+(NFV&SDN)
Source:Viewon5GArchitecture- 5GPPPArchitectureWorkingGroup(2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 91
5GSoftwarizationandProgrammabilityFramework
Source:Viewon5GArchitecture- 5GPPPArchitectureWorkingGroup(2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 92
MultiAdministrative Domains
Source:Viewon5GArchitecture- 5GPPPArchitectureWorkingGroup(2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 93
TheBigPicture
Source:Viewon5GArchitecture- 5GPPPArchitectureWorkingGroup(2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 94
SDN/NFVOpenInnovation
Source: SDN and NFV Stepping Stones to the Telco Cloud – Prodip Sen (ONS 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 95
NFVenables MEC:MobileEdgeComputing• MECprovidesITandcloud-computingcapabilitieswithintheRANinclose
proximitytomobilesubscriberstoacceleratecontent,servicesandapplicationssoincreasingresponsivenessfromtheedge.
• Standardizationbodies:ETSI,3GPP,ITU-T• RANedgeoffersaserviceenvironmentwithultra-lowlatencyandhigh
bandwidthaswellasdirectaccesstoreal-timeradionetworkinformation(subscriberlocation,cellload,etc.)usefulforapplicationsandservicestooffercontext-relatedservices
• Operatorscanopentheradionetworkedgetothird-partypartners• Proximity,context,agilityandspeedcancreatevalueandopportunitiesfor
mobileoperators,serviceandcontentproviders,OvertheTop(OTT)playersandIndependentSoftwareVendors(ISVs)
• Source:https://portal.etsi.org/Portals/0/TBpages/MEC/Docs/Mobile-edge_Computing_-_Introductory_Technical_White_Paper_V1%2018-09-14.pdf
ACM SIGCOMM Tutorial | 2016-08-22 | Page 96
MEC:MobileEdgeComputing
• Source:https://portal.etsi.org/Portals/0/TBpages/MEC/Docs/Mobile-edge_Computing_-_Introductory_Technical_White_Paper_V1%2018-09-14.pdf
DeploymentscenariosoftheMobile-edgeComputingserver
ACM SIGCOMM Tutorial | 2016-08-22 | Page 97
MEC:MobileEdgeComputing
• Source:https://portal.etsi.org/Portals/0/TBpages/MEC/Docs/Mobile-edge_Computing_-_Introductory_Technical_White_Paper_V1%2018-09-14.pdf
MECserverplatformoverview
ACM SIGCOMM Tutorial | 2016-08-22 | Page 98
SummingUp
Source:Software-definednetworking(SDN):aDellpointofview- ADellWhitePaper(2015)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 99
Enabling Technologies&OpenSource Efforts
ACM SIGCOMM Tutorial | 2016-08-22 | Page 100
Enabling Technologies• Virtualization &Minimalistic OS
– Docker,ClickOS,Unikernel
• Improving LinuxI/O&x86forpacket processing– DPDK,Netmap,VALE,LinuxNAPI
• Programmable virtualswitches/bridges– OpenvSwitch,P4,OpenNetworkingLinux
• Example start-ups– LineRate Systems,6WIND,Midonet,Vyatta (bought by BCD)
Image source: NEC
Image source: ClickOS
ACM SIGCOMM Tutorial | 2016-08-22 | Page 101
Enabling Technologies:OpenSource
Why OpenSource inNetworking?• Higherreliability,moreflexibility• Faster,lowercost,andhigherqualitydevelopment• Collaborativedecisionsaboutnewfeaturesandroadmaps• Acommonenvironmentforusersandappdevelopers• Abilityforuserstofocusresourcesondifferentiatingdevelopment• Opportunitytodriveopenstandards
Bottom Line: The open source model significantly accelerates consensus, delivering high performing, peer-reviewed code that forms a basis for an ecosystem of solutions.
Source: Open Source in a Closed Network – Prodip Sen (OPNFV Summit 2015)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 102
SDN/NFV&OpenSource:Evolvingandacceleratingthepathofstandardization
Further Reading: • IETF Trends and Observations draft-arkko-ietf-trends-and-observations-00• Source of table: "When Open Source Meets Network Control Planes." In IEEE Computer
(Special Issue on Software-Defined Networking), vol.47, no.11, pp.46,54, Nov. 2014. • Source of figure: A. Manzalini et al., “Towards 5G Software-Defined Ecosystems”
ACM SIGCOMM Tutorial | 2016-08-22 | Page 103
Standard/OpenSource Organizations
Source: SDN IEEE Outreach, http://sdn.ieee.org/outreach
Academia
Industry
ACM SIGCOMM Tutorial | 2016-08-22 | Page 104
FoundationsTargetCollaboration• Neutralandnon-competing• Legalframeworkforlicensing,copyright,intellectualpropertymanagement
"Companies feel they can collaborate on an open source project through an independent, not-for-profit entity that they trust - this is incredibly important to them," --Allison Randa (Board President of Open Source Initiative)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 105
OpenSourceBuildingBlocks2015– 2016:SeveralNewProjects
Source: The Open Source NFV Eco-system and OPNFV’s Role Therein – Frank Brockners (OPNFV Summit 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 106
OpenSourrce SDNProjects(2014snapshot)
Source: "When Open Source Meets Network Control Planes." In IEEE Computer (Special Issue on Software-Defined Networking). 2014.
ACM SIGCOMM Tutorial | 2016-08-22 | Page 107
› https://goo.gl/XCGDGS› http://bit.do/oss-sdn-nfv
NEW: Please see andcontribute to
https://docs.google.com/spreadsheets/d/1NHI4MZZWVDpxF_Rs7OOSTUa_aHL2ACUVA_Ov-YQs1DA/edit#gid=0
ACM SIGCOMM Tutorial | 2016-08-22 | Page 108
Agrowing ecosystem...
ACM SIGCOMM Tutorial | 2016-08-22 | Page 109
5GRelatedOpenSource
ACM SIGCOMM Tutorial | 2016-08-22 | Page 110
Experimentation
ACM SIGCOMM Tutorial | 2016-08-22 | Page 111
Testbeds
Source: http://www.5g-berlin.org/ http://openfederatedtestbed.org/
ACM SIGCOMM Tutorial | 2016-08-22 | Page 112
ContinuousIntegrationEnvironment
• ContinuousIntegrationtoolchainspeedsdevelopmentandfacilitatescollaboration– Gerrit– codereviewtool– GitHub- coderepository– Jenkins– automatedbuildtool– Maven– codebuild– Ansible/Chef/Puppet– codedeploymenttool– Docker/Vagrant– deploymenttoContainers/VMs
Source: Open Source Carrier Networking – Chris Donley (OPNFV Summit 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 113
Example:NTT(TMFORUM2016)
Source: A Transformation From Legacy Operation to Agile Operation – Makoto Eguchi (TM FORUM 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 114
TheFrontierofNetworking
Adapted from: Kyle Mestery, Next Generation Network Developer Skills
ACM SIGCOMM Tutorial | 2016-08-22 | Page 115
SomeTakeaways• Opensourcespeedsupdevelopmentandpromotesinteroperability• RapidprototypesareagreatwaytoshowSDN/NFVvalue,andnow5Gtoo!• Developerramp-uptimeischallenging,
– butonceintegrated,wecanmakerapidprogress
• AcommonCIenvironmentfacilitatessharingbetweenprojects• Cadence,shortiterationcycles,fastfeedback• Somepeoplearesaying:
– “opensourceisthenewstandardization”– “codeisthecoinoftherealm”
• Staytuned:– http://www.sdn-os-toolkits.org/– http://sdn.ieee.org/outreach
ACM SIGCOMM Tutorial | 2016-08-22 | Page 116
Thank you!Questions?
ACM SIGCOMM Tutorial | 2016-08-22 | Page 117
BACKUP
ACM SIGCOMM Tutorial | 2016-08-22 | Page 118
Perspective
Source: Survey Results: Bridging the Gap Between Open Standards and Open Source - Elizabeth Rose (OPNFV Summit 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 119
Challenges:Closedvs.Open
Source: Open Source in a Closed Network – Prodip Sen (OPNFV Summit 2015)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 120
OpenSourceRoad
Source: The NFV Revolution Must Be Open – Dave Neary (OPNFV Summit 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 121
ApproachforContributions
• OpenSourceProjectsneedmorethancode!– Documentation– QA– Infrastructure– Blogs– IRC
• Evaluatehowyourprojectideacanfitwiththeexistingproject– Doesitoverlap?– Doesitprovideextravalue?– Cansomethingbeabstracted?– Isthecommunityinterested?– Doesitfitthecommunitiesgoals?– Doyouhaveaplanfortesting,documentationandsupport?
Source: Upstream Open Source Networking Development: The Good, The Bad, and the Ugly – Kyle Mestery, Justin Pettit, Russell Bryant (ONS 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 122
ProjectEvolution:Examples
Source: Upstream Open Source Networking Development: The Good, The Bad, and the Ugly – Kyle Mestery, Justin Pettit, Russell Bryant (ONS 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 123
BuildingonOpenSourceProjects
“Do NOT fall into the trap of addingmore and more stuff to an out-of-tree project. It just makes it harder and harder to get it merged. Thereare many examples of this.”-Andrew Morton
Source: Swimming Upstream – Dave Neary (OPNFV Summit 2016)
ACM SIGCOMM Tutorial | 2016-08-22 | Page 124
OpenEndedQuestions
• WhataretheinhibitorstoadoptionofOpenSourceImplementations?– Issuessurroundinglicensing(esp.GPL)– IndustryunderstandingofOpenSourcelicensing– Competitiveissuesandfragmentation– Security– Qualityandrobustness– Maintenanceandsupport
Source: Survey Results: Bridging the Gap Between Open Standards and Open Source - Elizabeth Rose (OPNFV Summit 2016)