Co-hosting with TMC, we explore the complexities, myths and realities of NFV. What are the myths and reality of what an NFV environment can provide in the shorter term and what it will likely look like in the future? What attendees will learn: Xura has a front line view of the various approaches operators are taking to adopt the NFV concept for their messaging infrastructure. Join us as we explore: - How to de-risk the move to NFV by choosing services and steps that can be taken. - What orchestrated services really provide and how can they be plugged together? - Some of the realities of what is occurring within the market with NFV.

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

2. ||
Moderator:
NFV- TO BE OR NOT TO BE2
Dave Spann
VP Technology and
Architecture
Xura
Erik K Linask
Group Editorial Director
TMCnet
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 ?
3 NFV- TO BE OR NOT TO BE

4. ||
350 Operators140 Countries6 Continents
Global Market Leader
NFV- TO BE OR NOT TO BE4

5. |
|
The Path to NFV
NFV Considerations
Q&A
Agenda
5
The Promise of NFV…What & Why?
NFV- TO BE OR NOT TO BE

6. ||
What is NFV?
NFV- TO BE OR NOT TO BE6
• 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

7. ||
Goals
NFV- TO BE OR NOT TO BE7
Nirvāna:
?
NFV
Nirvana
Liberated from existence

8. ||
NFV Design Considerations
Management &
Orchestration
Network
Stability
Service
Continuity
Elasticity
Security
Resiliency
Energy
Efficiency
Portability/
Interoperability
Migration &
Co-Existence
Operations
Performance
NFV
Nirvana
NFV- TO BE OR NOT TO BE8

9. ||
Particular Constraints Highlighted
NFV- 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
Energy
Efficiency
• 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

10. ||
Deployment Project Types
NFV- TO BE OR NOT TO BE10
• 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
11
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

12. |
|
Promise of NFV… What & Why?
The Path to NFV
NFV Considerations
Q&A
Agenda
12
The Path to NFV
NFV- TO BE OR NOT TO BE

13. ||
Bare Metal Operator Services
Steps to NFV Using VAS Services
NFV- TO BE OR NOT TO BE13
NFV Environment
NFV
Management
&
Orchestration
VNF Environment
RCS
Voicemail
WebRTC GW
IP-SM GW
MMS
SMS
Voice TAS
Anti-SPAM
PCRF
HLR
HSS
PCEF

14. ||
Where Should You Start? How Do You Move Them All?
NFV- TO BE OR NOT TO BE14
VNF Environment
NFV Environment
Bare Metal Operator Services
RCS
Voicemail
WebRTC GW
IP-SM GW
MMS
SMS
Voice TAS
Anti-SPAM
PCRF
HLR
HSS
PCEF
NFV
Management
&
Orchestration
RCS
Voicemail
WebRTC GW
IP-SM GW
MMS
SMS
Voice TAS
Anti-SPAM
HLR/HSS
PCRF
PCEF

15. ||
Option - Staged Approach Starting with IP-SM Gateway
NFV- TO BE OR NOT TO BE15
NFV
Management
&
Orchestration
VNF Environment
NFV Environment
Bare Metal Operator Services
RCS
Voicemail
WebRTC GW
IP-SM GW
MMS
SMS
Voice TAS
Anti-SPAM
PCRF
HLR
HSS
PCEF
IP-SM GW

16. ||
Option - Augment with SMS/MMS
NFV- TO BE OR NOT TO BE16
NFV
Management
&
Orchestration
VNF Environment
NFV Environment
Bare Metal Operator Services
IP-SM GW
RCS
Voicemail
WebRTC GW
IP-SM GW
MMS
SMS
Voice TAS
Anti-SPAM
PCRF
HLR
HSS
PCEF
MMS
SMS

17. ||
Option - Augment with IP Services
NFV- TO BE OR NOT TO BE17
NFV
Management
&
Orchestration
VNF Environment
NFV Environment
Bare Metal Operator Services
IP-SM GW
RCS
Voicemail
WebRTC GW
IP-SM GW
MMS
SMS
Voice TAS
Anti-SPAM
PCRF
HLR
HSS
PCEF
RCS
WebRTC GW

18. ||
Bare Metal Operator Services
Option - Start with Legacy Voicemail
NFV- 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

19. ||
Logical Staged Results
NFV- TO BE OR NOT TO BE19
NFV
Management
&
Orchestration
VNF Environment
NFV Environment
Bare Metal Operator Services
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. ||
Messaging Services Consolidation
NFV- TO BE OR NOT TO BE20
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

21. |
|
Promise of NFV… What & Why?
The Path to NFV
NFV Considerations
Q&A
Agenda
21
NFV Considerations
NFV- TO BE OR NOT TO BE

22. ||
Constraints- Stack Duplication
NFV- TO BE OR NOT TO BE22
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 Duplication
NFV- TO BE OR NOT TO BE23
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 Families
NFV- TO BE OR NOT TO BE24
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

25. |
|
Promise of NFV… What & Why?
The Path to NFV
NFV Considerations
Q&A
Agenda
25
Q&A
NFV- TO BE OR NOT TO BE

26. ||
NFV, To Be Or Not To Be?
NFV- TO BE OR NOT TO BE26
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

27. ||
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: corporate.marketing@xura.com

28. |
www.xura.com
Thank You
NFV- TO BE OR NOT TO BE28