CT and IT architecture reconstruction based on - …...(software defined, NFV) CAPACITY (Homogeneous...
Transcript of CT and IT architecture reconstruction based on - …...(software defined, NFV) CAPACITY (Homogeneous...
CT and IT architecture
reconstruction based on
software_ Global CTO
09.09.2015
We are evolving towards a Hyper Connected and Intelligent Digital World*
The explosion of digital services makes connectivity
services more needed than ever
Reduction of Time to Market
Radical increase of traffic in telco networks
New ways of communication and increasing number of “always-on” users
Smartphone is changing everything
We need to adapt and define the change to lead in the Digital era
• Very intensive in hardware
• Capital intensive
• Software is not a core
Telco players Internet players
• Very intensive in software
• Can have global impact with not too much capital
• Hardware is a support, and is located in the network periphery
Today DIGITAL means SOFTWARE!
x
HARaDWARE SOFTWARE +
-
+
-
Our vision is to have a software-based network that delivers the best connectivity
experience in an efficient and 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
DIGITAL TELCO
To adapt our offer to users necessities
User Centric Connectivity Experience
How
• Making infrastructure uniform
• Facilitating interoperability
• Improving risk management in a changing environment
• Fostering competition & innovation
• Minimizing entry barriers
• Making capacity addition flexible and easy
• Simplifying network operation
NFV promises to transform the Telco industry, being operation one of the key levers
Architectural principles for the virtualization of everything
Common homogeneous and versatile infrastructure based on x86
Orchestration = automatized management
1. Based on the right abstraction layers
2. Based on standards & non-proprietary solutions
3. Based on modular blocks that allow different paces
of evolution
Abstraction and multi-tenancy layer
Workloads (IT, B2B, NFV)
Execution environment Management environment
Customers Operation
FUNCTION
(Logic)
CAPACITY
(Infrastructure)
Decoupling
ETSI's NFV architecture provides a framework to apply virtualisation technologies
to a network environment Management environment
Execution environment
Virtual Machines Commodity Servers
OS + Hypervisor
Commodity Switching infrastructure
Virtualised Infrastructure
Manager
Virtual Network Functions
INFRASTRUCTURE
Network
Functions VNF Manager
VM
VM VM
VM
VM
VM VM
VM VM VNF
VNF
VNF
SW NODE LIFECYCLE
VNF
VNF VNF
VNF VNF
Legacy OSS/BSS
Orchestrator NETWORK SERVICE
Network
Scenarios
VM
VM
VM
VM
VM
VM
VM
VM
Our target is virtualizing most of the network functions, not just cloud-like
workloads like control functions…
Manage users and sessions,
Managed local services
Capillarity, Capacity,
Mobility support Multiplexing Switching,
Transport
Control functions,
Managed regional services
Devices
Places
Users Access Aggregation Local Points of Presence Core Regional Data Centres
Interconnection
4G++
FTTx
COTS HW
LOCAL PoPs REGIONAL DATA CENTRES
Control Plane can be Centralised Data Plane must be Distributed
OS + Hypervisor
SDN Switching
Infrastructure Domain
Service Domain
Network Domain
CDN (*) Video (*)
P-CSCF (*)
S/PGW (*) BNG (*)
CGNAT (*) DPI (*)
SDP (*)
IMS (*)
DHCP (*) PCRF (*)
DNS (*) SPR (*)
COTS HW
OS + Hypervisor
SDN Switching
SRVCC (*)
HW and SW
decoupling
HW and SW
decoupling
IPv6 Router (*)
PE (*)
Security (*)
NGIN (*)
FUNCTION (software defined, NFV)
CAPACITY (Homogeneous infrastructure)
(*) Illustrative, since final VNFs deployed will depend on a natural selection processes regarding traffic and digital world evolution and requirements.
MME (*)
DRA (*)
DESIGN PRINCIPLES
• Enhanced user-centric connectivity experience
• Homogeneous and versatile infrastructure and simplified and automated operations
• Mouldable software-defined functionality
• Agile and open innovation
… since data plane virtualization has a potential higher economic impact than just
control plane virtualization
Source:Technology Strategy estimates based on Infonetics “Cpx Rev and Cpx by Eqpmt Analysis 2ndEd.”, Ovum (“Telecom Equipment Capex and Revenue Highlights 4Q13”, “Wireless Backhaul Forecast Spreadsheet- 2013-18”).
Data plane
Control plane
Mobile
Fixed
Backhaul
Optical Networking
IP Switching & Routing
4%
60%
9%
14%
9% by Network Layer $64bn
$4bn
$10bn
$15bn
$10bn
Main Network Equipment Global Capex Breakdown (2012, $bn)
Platforms 3% $3bn
N/A
E2E ORCHESTRATION
AS SIMPLE AS POSSIBLE
We need a reference architecture to ensure carrier class, operability and a healthy
ecosystem
AVOID VERTICAL INTEGRATION WHILE ASSURING PERFORMANCE
FOSTER A NEW ECOSYSTEM
Software appliances
(network functions) must be
portable
• Lowering entry barriers for new players
• Engaging established vendors
Network Virtualisation is not Cloud Computing
The network differs from the computing environment in 2 key factors:
Data plane workloads
(which are huge!)
Network requires shape
(+ E2E interconnection)
NEED OF HIGH AND PREDICTABLE PERFORMANCE (as with current
equipment)
GLOBAL NETWORK VIEW IS REQUIRED FOR MANAGEMENT
1
2
…which are big challenges for vanilla cloud computing
…and most of industry is offering to Telcos just IT based cloud products as network virtualization environments
NFV technology is almost there, but focus is needed to ensure readiness
CARRIER-GRADE PERFORMANCE CLOSE GAPS IN UNDERLYING TECHNOLOGIES
(HW, OS/hypervisor & VIM)
Main challenges Our strategy to make NFV happen:
AVOID VENDOR LOCK-IN CONTRIBUTE TO KEY OPEN SOURCE PROJECTS
(KVM and OpenStack)
AVOID COSTLY INTEGRATION PRE-PRODUCTION REFERENCE IMPLEMENTATION (NFV Reference Lab) INVOLVING ALL INDUSTRY,
to minimize integration efforts
Our NFV Reference Lab: fostering the ecosystem while minimizing integration
efforts and avoiding vendor lock-in
NFVO
Proper HW & Hypervisor config
VENDOR VALIDATION HERE:
Network Orchestration on top of
Carrier-grade OpenStack
VN
Fs VENDOR CERTIFICATION HERE:
Simplest integration
NFVI VIM = OpenStack++ OFC++
BASELINE TECHNOLOGIES (commodity, non-proprietary)
ECOSYSTEM
ECOSYSTEM
Others to come New VNFs to be added here
Carrier-grade OpenStack
going to upstream
development
Some players have already accepted to play out of their comfort
zone, while others are gradually coming
This new network model will help us to deeply transform our factory…
Global E2E vision instead traditional silo model,
not linked to monolithic OSS Breaking the traditional model mapping isolated network domains
• Computing principles used in IT world are beginning to be applied in telecoms by the means of Network Virtualization
• IP as common language for all services, included traditional Telco ones
• Network virtualisation enabling network re-programmability & agile service creation
Operation Model Change
Network Paradigm Change
Organization Model Change
…provided we overcome existing difficulties
Global E2E vision instead traditional silo model, not linked to monolithic OSS Breaking the traditional model mapping isolated network domains
• Computing principles used in IT world are beginning to be applied in telecoms by the means of Network Virtualization
• IP as common language for all services, included traditional Telco ones
• Network virtualisation enabling network re-programmability & agile service creation
Operation Model Change
Network Paradigm Change
Organization Model Change
Source: Deloitte. Feb 2015
Ultra-Broadband Forum 2015
Thank you