KEYNOTE @ NFV World Congress 2017, San José Francisco-Javier Ramón | Head of Network Virtualisation, GCTO | Telefónica Chair | ETSI OSM ABSTRACT: - How Telefónica is architecting its new Core Network with NFV to enable the dynamic re-allocation of capacity wherever needed. - Why orchestration is the latest technical challenge to realize this vision, and what Telefónica is doing in this space. - How Open Source MANO (OSM) has become the reference platform for interoperability after the launch of its third release. - How this fits into Telefónica plans for virtualization.

1. GCTO Unit / Telefónica I+D
04.05.2017
Building the new
Telefónica Core
with NFV
Paving the way to
new business needs
FRANCISCO-JAVIER RAMÓN SALGUERO
Head of Network Virtualisation Initiative – GCTO Unit, Telefónica
Chair of ETSI Open Source MANO (ETSI OSM)
javier.ramon@telefonica.com / @fjramons

2. 2
OUR VISION IS TO HAVE A NETWORK THAT DELIVERS THE BEST
CONNECTIVITY EXPERIENCE IN AN EFFICIENT & FLEXIBLE WAY
Goal
To cope with
quick changes
and uncertainty
Mouldable infrastructures
To understand
changes
inside-out and be
able to decide in
real time
Insight capabilities
To adapt our
offer to users
necessities
User Centric Connectivity Experience
Need for a much more
flexible Network
How

3. 3
A NEW VIRTUALISED NETWORK DESIGNED TO RE-
ALLOCATE CAPACITY IN REAL TIME WHEREVER NEEDED
• Homogeneous and versatile infrastructure
• Commoditized infrastructure
• Easier interoperability
• Flexible and easy capacity addition
• Common IT+Network infrastructure operation
• Simplified & automated operation
• E2E lifecycle management
• Common information models
• Simple integration per VNF
• Lowering entry barriers
• Elastic and scalable networks
Infrastructure
Orchestration
Virtual
Network
Functions
• Wider and competitive vendor ecosystem
• Agile and open innovation
• Faster Time-to-market
• A way to differentiate
Key enabler for future 5G network architecture
MOULDABLE
HARDWARE
vv
COTS HW
LOCAL PoPs REGIONAL DATA CENTRES
Control Plane can
be Centralised
Data Plane must
be Distributed
OS + Hypervisor
SDN Switching
CDN Video
P-CSCF
S/PGW BNG
CGNATDPI
SDP
IMS
DHCP PCRF
DNS AAA
COTS HW
OS + Hypervisor
SDN Switching
SRVCC
IPv6 Router
PE
Security
NGIN
MME
DRA
SOFTWARE
DEFINED

4. MOULDING THE FUTURE
REQUIRES GETTING
YOUR HANDS DIRTY

5. 5
WE’VE BEEN REALLY COMMITTED TO CLOSE
ANY TECHNICAL GAPS TO REALISE THIS VISION
Management
environment
Execution environment
Commodity Servers
& Switches
OS + Hypervisor Virtualised
Infra
Manager
Virtual Network
Functions
VNF
Manager
NFVO
2013
2014
2010
(Bare
metal)
2015
2016
2017
(EPA ready)

6. 6
• Service agility by automation
• Minimize integration efforts
• Enable operation at global scale
• Efficient infrastructure sharing
After a lot of progress so far,
Orchestration appears as the
ultimate hurdle ahead

7. 7
NFV REQUIRES REPLACEABLE COMPONENTS
THAT CAN BE AUTOMATICALLY ASSEMBLED
HARD
ONBOARDING
INADEQUATE
VNF MODELLING
UNEVEN VNF
CATALOGUE
BASIC AND HAND-
MADE NETWORK
SERVICE
Ad hoc
integration
BASIC NSD
FROM…
VNFs AS REPLACEABLE
COMPONENTS
VNF
CATALOGUE
NETWORK
SERVICE
MANOONBOARDING
…TO NSD

8. 8
LEVERAGE ON
ETSI NFV WORK
READY FOR GREENFIELD AND
BROWNFIELD
PERFORMANCE MATTERS FOR THE
BUSINESS CASE
OPEN SOURCE AS TOOL TO
FACILITATE CONVERGENCE
FOCUS ON WHAT WE HAVE IN
COMMON WITH OTHERS
Key is INTEROPERABILITY, not full architecture
MULTIPLE VIMS & SDNs ARE HERE
TO STAY (public clouds too!)
STRATEGY FOR A SMART CONVERGENCE
x100

9. 9
FROM… … TO
Vertical integration INTEROPERABILITY
One technology per element Several options per element
(but still coherently modelled)
Single-vendor Multi-vendor by design
Vendor roadmap Community roadmap
Request Convince and/or compromise
Large and Comprehensive Lean and Reliable
Design on paper Get your hands dirty!
CHANGING THE MINDSET

10. 10
1. To accelerate the availability
of a reference standard
2. To build a wide and competitive market of producers and
consumers
3. To answer the
BUY vs. MAKE question
3 REASONS TO GO TO OPEN SOURCE
PRODUCT
SOLUTION
BUY
MAKE
OPEN SOURCE
as bridge
SDO as
de iure
standard
OS as
de facto
standard

11. 11
• Open to new technologies
o Key for future-proof
• AND READY TO DELIVER!
• Open to players of all sizes
o Need of a diverse community
o Adding expertise & demand
• Sustainable and reliable
o The leaner, the better
o Focus on the core, leave
the rest to INTEROP
SOME REQUIREMENTS TO MAKE
OPEN SOURCE MANO FIT FOR PURPOSE

12. SO, HOW IS OSM DOING?

13. 13
LED BY SERVICE PROVIDERS, OSM COMMUNITY
HAS GROWN TO 65+ MEMBERS IN THIS PERIOD
• 9 Global Service Providers
• Leading IT/Cloud players
• VNF providers
MeadowCom

14. 14
OSM HAS DELIVERED 3 RELEASES WITH
EXCELLENT RECEPTION, AIMING PRODUCTION
READINESS FOR 2017

15. 15
OSM HAS DELIVERED 3 RELEASES WITH
EXCELLENT RECEPTION, AIMING PRODUCTION
READINESS FOR 2017
3600+ downloads
70+ countries
6500+ installs &
upgrades

16. 16
1ST NFV PLUGTEST WAS AN EXCELLENT REALITY
CHECK IN TERMS OF INTEROPERABILITY
OpenStack Newton OpenStack Newton OpenStack Kilo OpenVIM OpenStack+ODL OpenStack+ODL OpenStack Mitaka
OpenStack Mitaka
w/ regions
OpenStack Mitaka
w/ regions
VIM 1 VIM 2 VIM 3 VIM 4 VIM 5 VIM 6 VIM 7 VIM 8 VIM 9 VIM 10
FW VNF 1 Ok Ok 2
LB VNF 2 Ok 1
Probe VNF 3 Ok Ok Ok 3
IMS VNF 4 Ok 1
FW VNF 5 Ok Ok 2
Enterprise Messaging VNF 6 Ok Ok 2
Probe
VNF 7
Ok Ok
Ok
(minor issue with
LCM update)
Ok Ok
5
PCRF VNF 8 Ok 1
FW VNF 9 Ok 1
Probe/LB VNF 10 Ok Ok 2
DPI VNF 11 Ok 1
SBC VNF 12 Ok Ok Ok 3
Tester VNF 13 Ok Ok Ok 3
Tester VNF 14 Ok Ok 2
Probe VNF 15 Ok Ok Ok 3
1 5 2 1 2 2 3 8 7 1 32
OSM interoperated with all VIMs and all VNFs in the PlugTest
(*) Blank = combinations not assigned during the Plugtest (likely to work too)
All scheduled (random) tests were passed (32 test sessions in 8 days)
… and was extremely useful to accelerate the maturation of OSM SW

17. 17
THE NEW RELEASE TWO BRINGS ALREADY A
REALLY COMPREHENSIVE SET OF CAPABILITIES
Release TWO
Available at:
osm.etsi.org
Multi-VIM
Multi-SDN
SDN assist for underlay chaining with EPA
Enables EPA deployments E2E for VIMs with no underlay support
One-click installer
(multiple formats)
Full Day 0 & Day 1
operations
… and many improvements in interoperability, stability, security, etc.
Network Service
scaling
Multi-site Network
Services

18. 18
FEEDBACK TO ETSI NFV AFTER REL ONE WAS
REALLY WELL RECEIVED…
In/Out Title Date Comments
Out
(to ETSI)
VNFD Implementation
Challenges
(NFVIFA(15)0001351)
2015
(pre-
OSM)
Findings based on implementation of
ETSI-NFV ISG Phase 1 models. Partially
incorporated in phase 2 models
Out
(to ETSI)
OSM Release ONE
Feedback on Phase 2
VNFD and NSD
(NFVIFA(16)0001511r1)
Dec 13th
2016
Overview of clarifications, defects
(sightings) and feature requests related
to the VNFD and NSD
~100 comments to the current specs, around these areas:
• Enhanced Platform Awareness
• Lifecycle management in NSD and VNF
• VNFD connection points and L2/L3 addresses
• VNFFGD
• Deployment flavours
• Nested services
• Local Affinity Rules vs. Local Affinity Groups

19. 19
• 3600+ downloads & 6500 installs/upgrades just of Rel ONE!
• This huge amount of activity brings a wealth of useful
feedback from user community (e.g. via OSM_TECH ML)
o Early bug detection
o Usability improvements
o Feature priorities
o Focus on most relevant use cases
• All-in-one installer and
small footprint are being essential
o OSM community keeps pushing to make
installer even easier and code even leaner!
… WHILE OSM HAS BEEN CONTINUOUSLY OPEN
TO FEEDBACK TO MAKE OSM BETTER

20. 20
HOW DOES THIS FIT
INTO TELEFÓNICA
STRATEGY?

21. 21
Virtualisation is one of the levers of TEF’s “CORE Ready” program
OSM becomes the orchestration module on top of UNICA Infra
OSM HAS JUST BECOME A KEY PIECE IN
TELEFÓNICA’S VIRTUALISATION STRATEGY
Virtualization
Legacy Evolution
IP & Transport
Transformation
Business Intelligence
& 4t Platform

22. 22
ONBOARDING OF COMMERCIAL VNFs WITH OSM SINCE Q1
o NFV Reference Lab operating only with OSM since January
SELECTION OF OSM PROVIDER/INTEGRATOR JUST STARTED
o PHASE 1: RFI to select short list (just launched)
 Timing aligned with Release TWO launch
o PHASE 2: RFQ to award integrator (Q4)
 Timing aligned with Release THREE and OSM production readiness
Some key aspects
 Product support in Telefónica footprint (21 countries)
 Supply of all core modules (RO, SO, VCA)
 Solid contributor to upstream community
PROCESS TO DEPLOY OSM IN TELEFÓNICA’S
FOOTPRINT HAS STARTED IN Q1

23. 23
SAME PLACE, DIFFERENT APPROACHES
1957: 13 people deliver a computer
2017: One person holding 13
computers in one hand
Only
ACTUAL UTILITY
and
BUSINESS
OPPORTUNITIES
matter, not clutter
SOURCE:
https://twitter.com/ValaAfshar/status/856255901937934336

24. osm.etsi.org
E-Mail: javier.ramon@telefonica.com
Twitter: @fjramons
COMMENTS / QUESTIONS

25. 25
History of NFV and SDN - Telefónica role
2007 2008 2009 2010 2011 2012 2013 2014 2015
Development of a
low cost traffic
probe based on
x86 Intel
architecture
First Proof of
Concept of a
fully virtualized
Customer
Premise
Equipment
(vCPE)
Deeper: first fully
virtualized Deep
Packet Inspection
probe processing over
80 Gbps of traffic
ETSI NFV white
paper backed
by 13 operators
Telefónica NFV
Reference Lab
Field trial vCPE
in Vivo (Brazil)
OpenMANO NFV
orchestration stack
Telefónica
UNICA
Infrastructure
Plans
ETSI NFV ISG
Telefónica NFV
and SDN
operator of the
Year
2016
OSM hosted at
ETSI, endorsed
by 20+ companies
OSM Rel
ZERO
(May’16)
OSM Rel
ONE
(Oct’16)
2017
OSM Rel
TWO
(Apr’17)
Host of
1st ETSI NFV
Plugtest
(Jan’17)

26. 26
The short history of OSM
Kick-off
(Apr)
MWC demo
(Feb)
Release
ZERO
(May)
Release
ONE
(Oct)
1st ETSI NFV
Plugtest
(Jan)
Release
TWO
(Apr)
2016 2017
Release
THREE
target
(Oct-Nov)
Production
Readiness

27. 27
THE FOCUS SHOULD BE ON WHAT WE HAVE IN
COMMON WITH OTHERS Key is INTEROPERABILITY,
not full architecture
S
D
N
b
VIM A
+
SDN a
VIM B VIM C
OSS
BSS 2BSS 1
EMS
MANO
P
N
FVIM B
MANO
E
M
S
OSS
S
D
N
a
BSS 2
VIM A
MANO
OSS
BSS 1
SERVICE PROVIDER 1 SERVICE PROVIDER 2 SERVICE PROVIDER 3
MANO MANO
MANO
WHAT WE HAVE IN
COMMON

28. ACCELERATING CONVERGENCE
ON ORCHESTRATION

29. 29
… THERE ARE MANY INTERPRETATIONS OF THE MANO STACK
o What does it take to onboard VNF “X” in this MANO environment?
o Would VNF “X” work as expected?
o How could I operate the Network Service in practice?
o How can I integrate it with the rest of my network and OSS/BSS?
… INDUSTRY FRAGMENTATION and ENTRY BARRIERS do not
help to real deployments!
NEED TO ACCELERATE CONVERGENCE ON A TELCO-READY
MANO SOLUTION
o Drive NFV Ecosystem and Adoption
Management and orchestration are key
functions for NFV, but…

30. 30
RECALL: NFV REQUIRES REPLACEABLE COMPONENTS THAT
CAN BE SAFELY & AUTOMATICALLY ASSEMBLED…
VNF CATALOGUE NETWORK SERVICE
VNF
VNFD
NSD
ONBOARDING
MANO

31. 31
… BUT CURRENT MODELLING IS NOT YET THERE!
HARD
ONBOARDING
INADEQUATE
VNF MODELLING
UNEVEN VNF
CATALOGUE
Basic NSD
BASIC AND HAND-
MADE NETWORK
SERVICE
Ad hoc
integration
often
needed

32. 32
1. Accurate assignment of resources at VM level
2. Proper assignment of I/O interfaces to the VM
3. SDN gives the ability to create
underlay L2 connections
o Interconnecting VMs
o Attaching external traffic sources
Current EPA support combined with SDN
connectors enables high performance VNFs

33. 33
Technology Levers. Cloud timeline for
Telefónica network platforms
Technology
availability and
maturity
Baremetal Virtualised
Cloud
Telefonica
UNICA Target
Telefonica lead
UNICA development
Standard
availability
(Openstack
)
Include OSM service
orchestration as part
of UNICA
architecture

34. GCTO Unit / Telefónica I+D
34
Technology Levers. Service Orchestration
Network Virtualization Orchestration: OSM
Goal: Production-quality orchestration stack that
captures and automates real production complexity
• Covering e2e lifecycle of network services and VNFs
through both service and resource orchestration on top of
UNICA
Capable of consuming openly published information
and data models aligned with ETSI NFV
• Avoiding complex integration efforts
A community Open Source project as a way to
• to accelerate maturity of the technology and standards,
• enable a broad ecosystem of VNF vendors
• Architectural principles: Layering,
abstraction, modularity, simplicity
• Main features: Carrier grade
performance, multi-VIM, multi-site,
e2e automation
OSM is the orchestration
module within UNICA
• >45 players
• 7 Global Service Providers
• Leading IT/Cloud players
Kick-
off
(April)
(October)
Proof that the
Community can do
anything together
Demo MWC16
(Feb)
Seed
code
(May)
Sound starting
point for joint
evolutionary work
Community release
with more desired
features