webinar: to be or not to be...nfv

|1

To be or not to be NFV?NFV- TO BE OR NOT TO BE

||

Moderator:

NFV- TO BE OR NOT TO BE2

Dave SpannVP Technology and ArchitectureXura

Erik K Linask Group Editorial DirectorTMCnet

Presenter:

|3 |

Market Leader in Voicemail, Messaging, Monetization, Enterprise

Top Tier Customer BaseExpansive Presence in over 350 Service Providers

Worldwide

Headquartered in Wakefield, MA,

USA

Ticker (NASDAQ): MESG

Who is Xura ?NFV- TO BE OR NOT TO BE

| NFV- TO BE OR NOT TO BE|

350 Operators140 Countries6 Continents

Global Market Leader4

| NFV- TO BE OR NOT TO BE5

|

The Path to NFV

NFV Considerations

Q&A

Agenda

The Promise of NFV…What & Why?

|6 |

What is NFV?NFV- TO BE OR NOT TO BE

• A new way to design, deploy and manage networking services• Decouples network functions, such as network address translation,

firewalling, and domain name service (DNS) from proprietary hardware appliances

• Allows network elements (functions) to run as software-only on shared generic hardware

• Designed to consolidate and deliver the networking components needed to support a fully virtualized infrastructure

• Uses standard IT virtualization technologies that run on high-volume service, switch and storage hardware to virtualize network functions

||

GoalsNFV- TO BE OR NOT TO BE7

Nirvāna:?

NFVNirvana

Liberated from existence

||

NFV Design Considerations

Management & Orchestration

NetworkStability

ServiceContinuity

Elasticity

Security

Resiliency

EnergyEfficiency

Portability/Interoperability

Migration &Co-Existence

OperationsPerformance


||

Particular Constraints HighlightedNFV- TO BE OR NOT TO BE9

NFV will be an evolution not a revolution

Portability/Interoperability

• Mixed environments won’t be needed in first phases – operators picking a single environment to start with• Different VIMs unlikely to be

plugged together on day 1• Will still require some

localization to a particular VIM

EnergyEfficiency

• Likely not an initial driver or benefit until more applications are moved into NFV• Will require more breakdown

and knowledge of VNFs to host on the right types of VM/HW combinations

Elasticity

• Likely bounded scaling to begin• As applications and VIMs

become more advanced smaller incremental growth of the capacity will be achieved• Remember that physical HW

will still be a constraint here

| NFV- TO BE OR NOT TO BE10 |

Deployment Project Types

• Software only, running on top of Hypervisor (VMs)•Minimal lifecycle management –

orchestration of virtual resources (compute/network/storage)•Minimal auto-scaling capabilities• Typically OpenStack environment and

terminology• Could be a step towards NFV• EMS collaborates with OSS

Virtualization

• Software only, running on top of Hypervisor(s) (VMs)• Extended lifecycle management –

orchestration of:• Virtual resources (compute/network/storage)• VNFs• Network Services (i.e. graph of connected VNFs

• Integration with MANO stack• Potentially multiple VIMs in later phases• Adherence to ETSI requirements and

terminology• EMS collaborates with OSS and MANO

NFV

|11 |

Virtualization is a Logical Step Towards NFV

Cost Efficiency• Fewer servers• Reduced power costs• Reduced cooling costs• Smaller data center footprint• Minimized staffing requirements• Extending legacy applications

Quality of Service• Faster server provisioning• Elastic capacity• Improved system utilization• Improved disaster recovery• Increase uptime• High availability• Distributed resourcing

Business Agility• Reduced HW vendor lock-in• Easy SW migrations• Simplified management• Improves IT domain flexibility• Supports aggressive growth

NFV- TO BE OR NOT TO BE


|

Promise of NFV… What & Why?

The Path to NFV

NFV Considerations

Q&A

Agenda

The Path to NFV

| NFV- TO BE OR NOT TO BE13 |

Bare Metal Operator Services

Steps to NFV Using VAS Services

NFV Environment

NFV Management

&Orchestration

VNF Environment

RCS

Voicemail

WebRTC GW

IP-SM GW

MMS

SMS

Voice TAS

Anti-SPAM

PCRF

HLR

HSS

PCEF

||

Where Should You Start? How Do You Move Them All?


VNF Environment

NFV Environment


RCS

Voicemail

WebRTC GW

IP-SM GW

MMS

SMS

Voice TAS

Anti-SPAM

PCRF

HLR

HSS

PCEF

NFV Management

&Orchestration

RCS

Voicemail

WebRTC GWIP-SM GW

MMSSMS

Voice TAS

Anti-SPAM

HLR/HSS

PCRF

PCEF

||

Option - Staged Approach Starting with IP-SM Gateway


NFV Management

&Orchestration

VNF Environment

NFV Environment


RCS

Voicemail

WebRTC GW

IP-SM GW

MMS

SMS

Voice TAS

Anti-SPAM

PCRF

HLR

HSS

PCEF

IP-SM GW

||

Option - Augment with SMS/MMSNFV- TO BE OR NOT TO BE16

NFV Management

&Orchestration

VNF Environment

NFV Environment


IP-SM GW RCS

Voicemail

WebRTC GW

IP-SM GW

MMS

SMS

Voice TAS

Anti-SPAM

PCRF

HLR

HSS

PCEF

MMS

SMS

||

Option - Augment with IP ServicesNFV- TO BE OR NOT TO BE17

NFV Management

&Orchestration

VNF Environment

NFV Environment


IP-SM GW RCS

Voicemail

WebRTC GW

IP-SM GW

MMS

SMS

Voice TAS

Anti-SPAM

PCRF

HLR

HSS

PCEF

RCS

WebRTC GW

||


Option - Start with Legacy VoicemailNFV- TO BE OR NOT TO BE18

NFV Management

&Orchestration

VNF Environment

NFV Environment

RCS

Voicemail

WebRTC GW

IP-SM GW

MMS

SMS

Voice TAS

Anti-SPAM

PCRF

HLR

HSS

PCEF

Voicemail

Migration of Subscribers

||

Logical Staged ResultsNFV- TO BE OR NOT TO BE19

NFV Management

&Orchestration

VNF Environment

NFV Environment


RCS

WebRTC GW

IP-SM GW

Voicemail

Voice TAS

MMS

SMS

Anti-SPAM

RCS

Voicemail

WebRTC GW

IP-SM GW

MMS

SMS

Voice TAS

Anti-SPAM

PCRF

HLR

HSS

PCEF

|20 |

RCS

MMS

SMS

VM

Messaging Services ConsolidationNFV- TO BE OR NOT TO BE

Service consolidation will be a natural step in the evolution of messaging infrastructure reducing complexities dealing with multiple vendors and eliminating multiple hardware and software silos Consolidated

Services

Platform


|


The Path to NFV

NFV Considerations

Q&A

Agenda

NFV Considerations

|22 |

Constraints- Stack DuplicationNFV- TO BE OR NOT TO BE

NFV Management

&Orchestration

VNF Environment

NFV Environment

Orchestration or service chaining will not magically reduce number of stacks/components in the overall solution.

For a VNF to interact with other VNFs via SIP it needs it’s own SIP stack.

A SIP stack as a VNF will need an interface to be able to use it. If not SIP then another agreed standard will be required.

VNFSIP

SIP

VNFSIP VNFSIP

|23 |

Constraints- Stack DuplicationNFV- TO BE OR NOT TO BE

NFV Management

&Orchestration

VNF Environment

NFV Environment

What a SIP VNF Router can do:

1. Aggregate traffic towards other resources instead of having to have every system connected to every other system

2. Provide a way to manage additional security

3. Act as a gateway to Charging based services

VNFSIP VNFSIP VNFSIP

SIP

|24 |

Constraints- VNF FamiliesNFV- TO BE OR NOT TO BE

Likely that initial plugging together of services between VNFs will be app specific, standards guided and pre-wired

As interfaces open up and clear building blocks become available new services can interject in flows and change behavior

Orchestration can plug together some of the main interfaces between network components.

NFV Management

&Orchestration

VNF Environment

NFV Environment


|


The Path to NFV

NFV Considerations

Q&A

Agenda

Q&A

|26 |

NFV, To Be Or Not To Be?NFV- TO BE OR NOT TO BE

Yes - NFV will happen but in carefully planned stages

Success will be based on

Choosing which services to start with Building your knowledge base Having flexible, agile partners

||

What next?NFV- TO BE OR NOT TO BE27

Exclusive: NFV Operator Survey with Heavy Reading - the results of the report in April will be shared with everyone who has registered

White Paper: NFV and the Evolution of Messaging Infrastructure

Contact: [email protected]

NFV- TO BE OR NOT TO BE28 |

www.xura.com

Thank You

webinar: to be or not to be...nfv

Mobile