ETSI ACTIVITIES ONNETWORK FUNCTIONS VIRTUALIZATIONLaurent VRECK, ETSI

GSC-18 Meeting, 22-23 July 2014, Sophia Antipolis, France

Document No:

GSC(14)18_033

Source: ETSI

Contact: Laurent Vreck

Agenda Item:

6.1

What is NFV about?

A means to make the network flexible, dynamic, and less dependent on hardware

v

Network Functions are software-based using common and well known hardware

Multiple roles using same hardware

ORCHESTRATION, AUTOMATION & REMOTE INSTALL

DPIBRAS

WANAccel.

Firewall

CG-NAT

Test/QoE

VIRTUAL APPLIANCES

STANDARD HIGH VOLUME SERVERS

Virtualised Network Model: VIRTUAL APPLIANCE APPROACHVirtualised Network Model: VIRTUAL APPLIANCE APPROACHv

Network Functions are based on dedicated hardware and software

One physical appliance per role

Session Border ControllerFirewall CG-NAT

Traditional Network Model: HARDWARE APPLIANCE APPROACHTraditional Network Model: HARDWARE APPLIANCE APPROACH

DPIBRAS

Transformation of network hardware

Network Function Virtualization, why ?

Traffic & Service trends Challenges for Network Operators

• Traffic evolutionvoice internet video.

• Services change rapidly, user behaviours as well

• User devices increase in sophistication

• Enterprises want a seamless networked cloud

• Lack of flexibility and agility

• Launching new services is difficult and takes long time

• Complexity

• Inefficiency

Benefits and Challenges of NFV

Benefits

• Flexibility to rapidly, dynamically instantiate services in different locations without installing new equipment.

• Faster time-to-market for new service introduction

• Improving operational efficiency by taking advantage of a homogeneous hardware network platform

• Reducing costs through leveraging the economies of scale of the IT industry

• Reducing operational costs: less power, less space, improving network monitoring

…

Benefits and Challenges of NFV

Challenges

ETSI ISG NFVFOUNDED OCTOBER 2012

• Global operators + ETSI • Address the needs of network operators, to develop common approaches to

Virtualisation• Goal = make NFV a reality in operators networks

– define requirements for NFV, – develop architectural frameworks, – identify the gaps in the industry and prepare cooperation with other organizations

• Industry Specification Group (ISG) = appropriate model – Quick to set-up– Open membership with small fees to encourage involvement of smaller players– Flexible: allows some (controlled) deviation from the ETSI rules– Binds all participants to ETSI IPR policy

• October 2012 : ISG NFV was formed

http://www.etsi.org/nfv

ISG NFV 18 MONTHS LATER

• 220 companies (including 34 global operators)

Provides an umbrella for the industry to converge requirements, share learning and coordinate wider effort through cooperation with external bodies.

Has become the “centre of gravity” for the global industry to collaborate on NFV

• Intensive work, tremendous effort

• 7 plenary meetings so far, 250-300 participants each

• ~100 F2F sessions (Drafting mtg, WG mtg, …)

• 500+ conference calls

• 10 Mailing lists1160 subscribers on the main mailing list

• some WG lists “exploded” to 200 + emails/day.

First 5 ISG NFV deliverablesOctober 2013

GS NFV 001

Use Cases

GS NFV PER 002

PoC Framework

GS NFV 004

Virtualization Requirements

GS NFV 002

Architectural Framework

GS NFV 003

NFVTerminology

Available from ETSI site free of charge: http://www.etsi.org/nfv

9 Use Cases that should be focussed on for developing future specifications.UCs range from VNF Iaas, VNF aas, VNF Platform aas, to… Mobile core (EPC) and IMS virtualisation, Mobile Base Station virtualisation, and others…

Documents a high-level functional architecture to identify which domain are subject to further specification and innovation and where there is a need for abstraction to enable to abstract the network functions from the hardware.

Not just a list of acronym, helps understanding what is meant by “Virtual Machine” or “Virtual Appliance” or a “Virtual Network Function” so that everyone (coming from IT, Telecom, …) is on the same page when it comes to communication of some of the basics NFV. *

Formalize high level business and technical requirements for virtualization.

“Proof of Concept” Framework: Describes a procedure to encourage growth of the NFV ecosystem through multi-party implementations of Proof of Concept demonstrations (PoCs).

NFV PoC framework

• NFV Proofs of Concept– 21 multi-vendor PoC projects

• Minimum 2 vendors and 1 network operator per PoC• Overall +50 vendors and +10 network operators

– Addressing NFV E2E concepts (Use cases, Requirements, Interfaces, …)• 80% of NFV use cases covered

• Goals– Provide feedback “from the field”

• Explore new areas and technology options• Validate assumptions or approaches• Facilitate gap analysis• Help to guide the future NFV ISG activity

– Develop Market awareness• Demonstrate NFV capabilities

12 NFV PoC Demos @ SDN & OpenFlow World Congress, Düsseldorf,14-17/10/2014

Second NFV operators White PaperPublished October 2013http://portal.etsi.org/NFV/NFV_White_Paper2.pdf

• Provides operator perspectives on progress made

• Brings attention to the first outputs and shows a broad operator support

• Initiates discussion on relationships with other bodies (SDO, Fora).

• Encourages industry involvement in PoCs

• Start discussion on the role of Open Source

25 operator signatories

GS NFV PER 002Public Demo NFV

PoCs

GS NFV PER 002Public Demo NFV

PoCs

WG approvedWGapp

GS NFV PER 001Perf & Portability Best Practises

GS NFV INF 007

Interfaces and

Abstractions

WGapp

GS NFV SEC 002Cataloguing

security features

GS NFV INF 010NFV Service

Quality Metrics

GS NFV SEC 003Security & Trust

Guidance

GS NFV 002ArchitecturalFramework

GS NFV 002ArchitecturalFramework

WI-10

PUBLISHED

New at last plenary Available in OPEN AREA: http://docbox.etsi.org/ISG/NFV/Open/

GS NFV INF 001Infrastructure Overview

WGapp

GS NFV INF 003

Compute Domain

GS NFV INF 004

Hypervisor Domain

GS NFV INF 005

Infrastructure Network Domain

GS NFV 003Terminology forMain Concepts

GS NFV 003Terminology forMain Concepts

WI-11

PUBLISHED

GS NFV 001 Use Cases

GS NFV 001 Use Cases

WI-09

PUBLISHED

GS NFV 004 VirtualisationRequirements

GS NFV 004 VirtualisationRequirements

WI-12

PUBLISHED

GS NFV 002ed121

ArchitecturalFramework

WI-02ed121

GS NFV 003ed121

Terminology forMain Concepts

WI-03ed121

GS NFV _ _ _Gap Analysis

WI-013

NEW

NEW

GS NFV REL 001

Resiliency Rqmts

WGapp

In Release 1In Release 1, Dec 2014, Dec 2014In Release 1In Release 1, Dec 2014, Dec 2014NOT IN Release 1NOT IN Release 1

WGapp

WGapp

WGappGS NFV SEC 001

Security Problem

Statement

WGapp

17 Documents in development

GS NFV SWA 001

VNF Architecture

GS NFV MAN 001Management and Orchestration

WGapp

WGapp

DecOctSepAugJulyJuneAprilMarchFebJan May Nov JuneAprilMarchFebJan May

NFV#7USA

NFV#6Japan

NFV#5Spain

NFV#9CZ

NFV#8USA

Release Maintenance(alignment phase)

Release ”Freeze”Release ”Freeze”

Progress NFV releaseProgress NFV release

Release Approval & PUBLICATION

Release Approval & PUBLICATION

Release stable,WG final check

NFVApproval

OPEN Area

WGApproval

All WG drafts WG-approved

Focus on Prep. for WG Approval

Focus on General Alignment

Focus on Final Release

Focus on Phase 2

ISG NFV Release Timeline

Phase 2Kick-off

Phase 2Kick-offFinalize Ph 2

plansFinalize Ph 2

plans

Ph2 Scope, contentToRs

Structure, Governance

Ph2 Time plan

Phase 2 executionPhase 2 executionPhase 2 inceptionPhase 2 inception

Appointment of New WGs/TF officials

• Documents now stabilized for alignment phase(i.e. now under formal Change Control)

• Alignment phase: July – November 2014 • Release date: December 2014

WHAT COMES IN PHASE2

• ISG NFV remains the centre of gravity for NFV • Interoperability as major goal• Build on Ph1 results to produce "normative" specifications • Develop cooperation (including Open Source)• Technical Content, Structure, governance proposals ready• Increased Vendors’ involvement• New test framework

– Interop testing– Develop the Proof of Concept framework

And more…

A New Open Source Initiative:Open Platform for NFV

• Project initiated by members of the NFV ISG leadership that will be coordinated by the Linux Foundation– Create an integrated (SW, HW) open platform

– Create an environment for continuous system level validation and integration

– Contribute changes to other open source projects used within the platform

– provide feedback to the NFV ISG

– Build new open source components within the project where needed

• Timescales: launch October 2014 to be ready for the NFV ISG release in December.

CONCLUSIONS

• Tremendous amount of work achieved• Big, well established and very active community• This is just a start• Next step

– implementation of these principles in specific Use Cases (eg: 3GPP, BBF, Linux foundation).

– Focus on interoperability through normative specs and tests– Cooperate to accelerate

Thanks for listening…

Useful links:

1. NFV ISG Published Documents http://www.etsi.org/nfv

2. Draft documents available prior to publication:http://docbox.etsi.org/ISG/NFV/Open/

3. #1 and #2 joint-operator white papers – (Oct 2012&2013)http://portal.etsi.org/NFV/NFV_White_Paper.pdf http://portal.etsi.org/NFV/NFV_White_Paper2.pdf

4. NFV ISG PoC Enquiries: http://www.etsi.org/nfv-poc

5. NFV ISG portal pages: http://portal.etsi.org/nfv