The Virtual Brick Road Achievements and Challenges in NFV Space. Diego R. Lopez Telefónica NFV ISG Technical Manager October 2013

Transcription

1 The Virtual Brick Road Achievements and Challenges in NFV Space Diego R. Lopez Telefónica NFV ISG Technical Manager October 2013

2 The NFV Concept A means to make the network more flexible and simple by minimising dependence on HW constraints Traditional Network Model: APPLIANCE APPROACH v Virtualised Network Model: VIRTUAL APPLIANCE APPROACH v DPI Firewall BRAS CG-NAT GGSN/SGSN Session Border Controller PE Router Network Functions are based on specific HW&SW One physical node per role DPI CG-NAT GGSN/ BRAS SGSN Firewall PE Router VIRTUAL APPLIANCES ORCHESTRATION, AUTOMATION & REMOTE INSTALL STANDARD HIGH VOLUME SERVERS Network Functions are SW-based over well-known HW Multiple roles over same HW 2

3 The NFV Benefits Flexibility to easily, rapidly, dynamically provision and instantiate new services in various locations (i.e. no need for new equipment install) Increased speed of time-to-market by minimising the typical network operator cycle of innovation. More service differentiation & customization Improved operational efficiency by taking advantage of a homogeneous (physical) network platform Reduced equipment costs through equipment consolidation on high volume industry standard servers leveraging the economies of scale of the IT industry Reduced operational costs: reduced power, reduced space, improved network monitoring Software-oriented innovation (including Open Source) to rapidly prototype and test new services and generate new revenue streams IT-oriented skillset and talent (readily available in global geography, flexible) 3

4 The ETSI NFV ISG Global operators-led Industry Specification Group (ISG) under the auspices of ETSI ~150 member organisations Open membership ETSI members sign the Member Agreement Non-ETSI members sign the Participant Agreement Opening up to academia Operates by consensus Formal voting only when required Deliverables: White papers addressing challenges and operator requirements, as input to SDOs Not a standardisation body by itself Currently, four WGs and two EGs Infrastructure Software Architecture Management & Orchestration Reliability & Availability Performance & Portability Security 4

5 The Main Tracks Internal and external consolidation of the NFV Concept Community Impact Scopes Goals Procedures A holistic, E2E view Use cases Requirements Architecture Terminology Proofs of concept Make NFV live to its expectations Explore via direct experience Provide direct evidence to gap analysis 5

6 An E2E View: Architectural Use Cases Network Functions Virtualisation Infrastructure as a Service Network functions go to the cloud Virtual Network Function as a Service Ubiquitous, delocalized network functions Virtual Network Platform as a Service Applying multi-tenancy at the level Forwarding Graphs Building E2E services by composition 6

7 An E2E View: Service-Oriented Use Cases Mobile core network and IMS Elastic, scalable, more resilient EPC Specially suitable for a phased approach Mobile base stations Evolved Cloud-RAN Enabler for SON Home environment L2 visibility to the home network Smooth introduction of residential services CDNs Better adaptability to traffic surges New collaborative service models Fixed access network Offload computational intensive optimization Enable on-demand access services 7

8 An E2E View: Architecture OSS/BSS Service, and Infrastructure Description Os-Ma Se-Ma Orchestrator Or-Vnfm EMS 1 EMS 2 EMS 3 Ve-Vnfm Manager(s) Or-Vi NFVI Vn-Nf Vi-Vnfm Virtual Computing Computing Hardware Virtual Storage Virtualisation Layer Vl-Ha Storage Hardware Virtual Network Hardware resources Network Hardware Nf-Vi Virtualised Infrastructure Manager(s) Execution reference points Other reference points Main NFV reference points 8

9 It Ain t Cloud Applied to Carriers The network differs from the computing environment in 2 key factors 1 2 Data plane workloads (which are huge!) Network requires shape (+ E2E interconnection) HIGH PRESSURE ON PERFORMANCE GLOBAL NETWORK VIEW IS REQUIRED FOR MANAGEMENT which are big challenges for vanilla cloud computing. AN ADAPTED VIRTUALISATION ENVIRONMENT IS NEEDED TO OBTAIN CARRIER-CLASS BEHAVIOUR 9

10 XaaS for Network Services VNPaaS NSP Forwarding Graph User aas VNPaaS User Tenants Hosting Service Provider NFVI Provider aas User NFVIaaS IaaS NaaS IaaS PaaS 10

11 Counting a Few Orchestration has the key Pieces at all infrastructure layers Need to go beyond just fitting them together Big data in the loop The impact on operations Avoid he trap of just adding software appliances Seize the opportunity to simplify systems and processes Identify interstitial security threats Topologies Trusted boot Several identity layers and accounting Design patterns Big multi-user VMs vs small single-user ones Componentization Building services by composition Dealing with topology layers Up to three: infrastructural, virtualized, and service Mapping to current practices and protocols 11

12 The Need for an Evolutionary Approach NFV (and SDN) imply a significant change for current network infrastructures No zero-day approach is feasible Avoiding disruptions Identify relevant use cases Emerging services Reuse of equipment still in amortization Leverage on new planned elements in architecture Plan for phased deployments Interworking with existing infrastructure Not breaking current operational practice Take advantage of their advantages Flexibility Extensibility Reusability 12

13 Architectural Working Groups Related to functional requirements Have a clear location in the NFV architecture Keep consistency with both requirements and architecture INF The supporting infrastructure interfaces and elements MANO The external interfaces and behaviour of a SWA The internals of a Refining the architecture Addressing use cases Mostly oriented to produce reference documents 13

14 Transversal Working Groups Related to non-functional requirements Transversal to the architecture And influencing the architectural groups PER Predictability in the data plane and function portability REL Specify resiliency requirements, mechanisms, and architectures SEC Function by function and infrastructure Refining the requirements Assessing use cases Mostly concerned with recommendations and architecture models 14

15 Proofs of Concept Look for practical results Demonstrate and disseminate NFV capabilities Explore technology options Facilitate gap analysis Contribute to guide the future ISG activity Lightweight process Few (objective) requirements to file a PoC proposal At least two manufacturers plus one network operator as participants Describe the PoC according to a predefined template Including space-time coordinates Address at least one goal related to the E2E Use Cases, Requirements, or Architecture Run PoC project Commercial or academic event, operator s lab, experimental network Openly report results to the community At least one contribution to the ISG: the PoC Report According to a predefined template The community will assess the real value of the PoC through the normal contribution process The call is open along the ISG lifetime 15

16 Fine, Thanks! The NFV concepts have consolidated The word has spread First deliverables available Reasonably clear work plan Going well beyond the ISG Rules of engagement with SDOs as well as OS initiatives A focus on open PoCs Addressing first realizations Tests and plans reported everywhere First real pilots on their way So many things to do, so few folks to do them Always open recruiting office 16

17 17