NFV: What Exactly Can Be Virtualized?

Transcription

1 NFV: What Exactly Can Be Virtualized? Jim Hodges d Senior Analyst, Heavy Reading

2 Agenda NFV Drivers ETSI NFV Use Cases Virtualization Criteria Applying the Criteria NFV Challenges Summary 2

3 NFV Adoption Factors Operator requirements 4G and mobile broadband scalability and cost challenges Moving datacenters to the cloud via virtualization Equipment vendor capabilities Both datacenter and telecom NEPS Shifting from hardware to software focus Fulfilling the promise of IP Why do I need to run two domains/networks once I have completed a TDM-to-IP transition and virtualized the DC? IP service framework tends to be distributed IP application performance and availability are end-user expectations 3

4 Virtualization & NFV 4

5 NFV Architectural Framework X X X X X Source: ETSI NFV White Paper 2, October

6 NFV Scope Source: ETSI NFV White Paper 2, October

7 NFV Use Cases Use Case Use Case #1: Network Function Virtualization Infrastructure as a Service Use Case #2: Virtual Network Function as a Service (VNFaaS) Use Case #3: Virtual Network Platform as a Service (VNPaaS) Use Case #4: VNF Forwarding Graphs Use Case #5: Virtualization of Mobile Core Network and IMS Use Case #6 :Virtualization of the Mobile Base Station Use Case #7: Virtualization of the Home Environment Description This use case provides an approach to mapping the Cloud Computing Service Models IaaS and NaaS as elements with the Network Function Virrtualization Infrastructure when it is provided as a service. Application of virtualization to the enterprise to enable a lower-cost model in which the operator provides services and the enterprise consumes the resources it requires. Similar to Use Case 2 but in this use case the enterprise has the opportunity to host and introduce VNFs instances on its own. A Network Function (NF) Forwarding Graph [1] defines the sequence that packets traverse. A simple Network Services [1] can be implemented in an NFV environment using point to point links. This use case demonstrates that more complex structure might be necessary as VNF Forwarding Graph (VNF FG) [1]. This use case encompasses virtualization of the mobile packet core and IMS (eg. HSS, CSCF). This use case encompasses virtualization of the mobile RAN onto standard IT servers. This use case encompasses virtualization of CPE such as set-to-boxes (STBs) and residential gateways (RGs). Use Case #8: Virtualization of CDNs (vcdn) Use Case #9: Fixed Access Network Functions Virtualization This use case encompasses virtualization of content delivery networks (CDNs) to enable a more scalable and lower-cost off-peak operational model. This use case encompass virtualization of fixed network access infrastructure (DSL cabinet ) to optimize deployment costs and enable co-location with wireless access nodes. Source: ETSI GS NFV 001 V1.1.1 ( ) 7

8 NFV Operator Strategies NFV implementation strategies will be operator specific What is the competitive landscape? Unique network architecture attributes How does NFV tie into my service strategy and use cases? How does NFV tie into my network strategic vision? Vendor incumbency (both datacenter and telco domains) Merger and acquisition strategies Organizational characteristics 8

9 NFV Virtualization Criteria Functional role and position in the network Service profile support Position in the network and connectivity level Signaling plane, media plane considerations Multi-layer aware Software compute requirements Software intelligence level Design level 9

10 Functional Role & Position in the Network: Service Profile Support Considerations include: Does the network node support specific niche or declining network functions? Does the network node support both voice and data services? 10

11 Functional Role & Position in the Network: Network position & connectivity level Considerations include: Does the network node run in a single home network, or is it deployed at the edge and therefore required to interface with other networks (e.g., mobile, fixed, cable, or OTT operators)? Does the position of the node and level of connectivity with other networks position it to adopt new software functions in response to the emergence of new service models including OTT services? Does the node support both the bearer and control plane? This is increasingly important given it provides an opportunity to virtualize both or adopt a singular approach such as the control plane which is well aligned conceptually with software-defined networking (SDN). 11

12 Functional Role & Position in the Network: Multi-layer aware Considerations include: Does the network node possess the capabilities to perform or directly influence both network and application control? 12

13 Software Compute Requirements: Service Intelligence Level Considerations include: To what extent does the network node software performance have a direct and perceivable impact on the customer service experience and QoS? Is the software simply in the call or session path, or does it control it and provide some form of orchestration? Does the software support multiple functions security, policy control, billing, admission control, control plane supervision, session layer supervision, and policy? 13

14 Software Compute Requirements: Design Level Considerations include: Is the software designed to run on a proprietary hardware platform, or does it utilize open, conventional, industry-accepted software coding practices, and is it designed to run independently of hardware? To what extent does the product support software-based network intelligence functions (e.g., the ability to inspect or extract information from packet flows) vs. a hardware-centric network intelligence function design model? Is the software highly extensible and modular, or does it employ hard coded parameters and monolithic design? 14

15 Applying the Criteria: IMS Core Key questions: What do I want to accomplish? Lower-cost model core or access? What types of savings will be achieved? New service model (VNFaaS)? Linkage to other network strategies CDN? How formidable are the challenges? Is VNF Forwarding Graphs mandatory from initial deployment? What are the orchestration implications? Use Case H M L Use Case #1: Network Function Virtualization Infrastructure as a Service Criteria: IMS CSCF Service profile: Increasing value: voice and data Position in the network and connectivity level: Core and edge Multi-layer aware: Yes Service intelligence level: High Design level: High Use Case #2: Virtual Network Function as a Service (VNFaaS) Use Case #3: Virtual Network Platform as a Service (VNPaaS) Use Case #4: VNF Forwarding Graphs Use Case #5: Virtualization of Mobile Core Network and IMS Use Case #6 :Virtualization of the Mobile Base Station Use Case #7: Virtualization of the Home Environment Use Case #8: Virtualization of CDNs (vcdn) Use Case #9: Fixed Access Network Functions Virtualization 15

16 Applying the Criteria: EPC Key questions: What do I want to accomplish? Lower-cost model core or access? What types of savings will be achieved? New service model (VNFaaS)? Linkage to other network strategies CDN? How formidable are the challenges? Is VNF Forwarding Graphs mandatory from initial deployment? What are the orchestration implications? Use Case H M L Use Case #1: Network Function Virtualization Infrastructure as a Service Use Case #2: Virtual Network Function as a Service (VNFaaS) Criteria: EPC Use Case #3: Virtual Network Platform as a Service (VNPaaS) Service profile: Increasing value data services Use Case #4: VNF Forwarding Graphs Position in the network and connectivity level: Core and edge Use Case #5: Virtualization of Mobile Core Network and IMS Multi-layer aware: Yes Service intelligence level: High Design level: Medium Use Case #6 :Virtualization of the Mobile Base Station Use Case #7: Virtualization of the Home Environment Use Case #8: Virtualization of CDNs (vcdn) Use Case #9: Fixed Access Network Functions Virtualization 16

17 Applying the Criteria: Home Network Key questions: What do I want to accomplish? Lower-cost model core or access? What types of savings will be achieved? New service model (VNFaaS)? Linkage to other network strategies CDN? How formidable are the challenges? Is VNF Forwarding Graphs mandatory from initial deployment? What are the orchestration implications? Use Case H M L Use Case #1: Network Function Virtualization Infrastructure as a Service Criterion: CPE Service profile: Stable: voice and data Position in the network and connectivity level: Edge Multi-layer aware: Yes Service intelligence level: Medium Design level: Medium Use Case #2: Virtual Network Function as a Service (VNFaaS) Use Case #3: Virtual Network Platform as a Service (VNPaaS) Use Case #4: VNF Forwarding Graphs Use Case #5: Virtualization of Mobile Core Network and IMS Use Case #6 :Virtualization of the Mobile Base Station Use Case #7: Virtualization of the Home Environment Use Case #8: Virtualization of CDNs (vcdn) Use Case #9: Fixed Access Network Functions Virtualization 17

18 Orchestration Considerations NFV and SDN both leverage the concept of orchestration at various layers (2/3-7) Orchestration benefits include: Shortening provisioning cycles for new applications Assists in determining where to deploy VNFs More flexible service model, any application anywhere aligned with the fully programmable service model Fosters ecosystem innovation 18

19 NFV Challenges Don t lose sight of the NFV framework reference Objective is to evolve to a fully virtualized and orchestrated application framework Porting software is an important but initial step Application orchestration Latency and security Application failover and troubleshooting OSS/BSS integration Vendor fine print commitment Cultural implications Linking virtualization to a services strategy 19

20 Conclusion There is no right or wrong answer for a first-wave network function virtualization strategy. The key is to identify which function best meets your criteria and has vendor buy-in. Do your homework: ensure there are internal PoC resources, and that the VNF has a strong business case with minimal customer impact. Linking virtualization candidates with the ETSI use cases helps to put the journey in context and justify the business plan. Remember that NFV is not just porting software to another platform, it introduces a completely new approach to IP service delivery (e.g., orchestration) 20