The ingredients of the new

networks: SDN, NFV and Slicing

in the evolution towards 5G

Luis M. Contreras

Presentation at the

University of Tokyo, Japan

26.06.2016

2

1. Motivations for evolving existing networks

2. SDN for programming Transport Networks

3. NFV for agile deployment of services

4. On-going Relevant Innovation Actions

5. Challenges imposed by SDN and NFV

6. Conclusions

Index

01Motivations for

evolving existing networks

4

• Carrier networks are multi-technology, multi-vendor and multi-layer

• Legacy Carrier Networks were not designed to cope with customized service creation and delivery with very short lead times

o Dynamic traffic patterns

o Unpredictable patterns e.g. with cloud computing

• Requirements and attributes of Carrier Networks

o Ability to deliver managed services end-to-end.

o SLA compliance.

o Inter-Carrier interoperability.

o Inter-Vendor interoperability.

o Service Operations and Maintenance capabilities

o High availability, reliability and security

Context of current Carrier Networks

5

• Network Scale and Technology Diversity

o large numbers of physical NEs distributed over a multitude of

locations

o wide variety of technologies, provided by multiple vendors

o regional, national and global infrastructures

• Maintenance and OAM

o Difficult in-service replacement of carrier equipment

o Need to collect events for facilitating operation

o recovery from facility faults is a high priority

• Depreciation and ROI

o Reuse of network assets

• Migration

o Brown field scenario upgrade

Context of current Carrier Networks

6

Data traffic pressure

Metro Access Metro Aggr BRAS/PGW IP Edge IP Core / ICX

2G/3G/LTE

DSLAM / OLT

S/GWT S/GWD S/GWC

Long HaulMetro

Transport

Service Centers

CDN

Internet

OTT

Contentown

Content

InterconnectionBH

Bandwidth by peak and

average ratio [Analysys Mason]

35,0%

44,9%

38,6%

36,3%307,4%

7

• Traditional network dimensioning yields to this situations:

Looking for Elasticity

• Ideally, the network must dynamically be adapted to the end

users demands

Res

ourc

es

Capacity

t

Under-provisioning

Capacity

t

Res

ourc

es

Capacity

t

Res

ourc

es

Over-provisioning

8

Telco Cloud

Migration of workload might be

required; proximity → better experience

(Minimize CAPEX vs Increase Capacity)

User demand changes;

Maybe unexpectedly or bursty

Network capacity needs to be

adapted to the new situation

Cloud Data Center (CDC)

Network Provider 1

Network Provider 2

Compute (i.e. increase VMs) scales

up/out in response

(Minimize OPEX vs. Maintain QoS)

9

• Slow adaptation of the network to changing demands

• Complex procedures for service delivery

• High customization during service creation

• Difficulties on defining and standardizing services across the

affiliates’ networks

• Long time-to-market

The reality of an operator translates into …

Network Programmability and Network Function Virtualizationare expected to be the solution (or mitigation) for all of the

above issues

10

• Existing service innovation is tightly coupled to the product innovation cycles

• High variety of vendors in operators like Telefónica, each of them presenting

different operating systems, SDKs and APIs, in multiple node families and

functionalities

• Closed solutions per vendor, difficult to port

• Lack of automation in service delivery

• Complex procedures for service scaling in and out

SDN as a way towards network programmability

• Network programmability as the capability of installing and removing network

behavior, in real time

• This is not just to populate rules to simple switches or offering APIs

• End-to-end network abstraction is required for true technology and vendor integration

• Network services to be realized by programming instead of re-architecting the network

• Leveraging on existing and deployed network capacities (control plane functionalities)

• Managing the network in an integrated/coordinated way, not as a collection of individual

boxes/layers

• Stress on service modeling and network modeling, lately propagated through standard

interfaces (Netfconf, Yang, OpenFlow) cooperating with existing control plane capabilities

(GMPLS, etc.)

11

Network Function Virtualization (NFV) as a way to decouple

function capability from resource capacity

• Heterogeneous services on a homogeneous infrastructure

o The decoupling of functionality and capacity

• Support for dynamic management of network slices

o The basic construct for supporting the 5G application scenarios

• Function placement

o Following the users, accommodating to the needs

DPIBRAS

GGSN/SGSN

Firewall

CG-NAT

PE Router

VIRTUAL NETWORK FUNCTIONS

COMMON HW(Servers & Switches)

FUNCTION

CAPACITY

12

5G Architecture from NGMN White Paper

5G System Requirements and Architecture

Performance• 1000x higher mobile data volumes• 10x – 100x higher number of connected devices• 10x – 100x typical end-user data rates• 5x lower latency• 10x longer battery life

Flexibility• Network programmability• Agile service deployment• Affordable and sustainable

13

5G Network Architecture - Slicing

Smartphones

UPUP

CP/UP

CP/UP

CP

…

Massive IoT devices

UP

CP

Automotive devices

CP/UP

CP/UPVerticalVertical

AP

14

• Not unique definition nowadays

• Infrastructure Resources partition (either physical or virtual)

o Compute, storage, networking (up to a Gateway)

• Connectivity Services

o Services that handle the transport of digital data between nodes

o The digital information exiting the Node does not differ from the incoming one

• Nodal/Function Services

o Services that involve manipulation / processing of data (payload) within a node

o The digital information exiting the Node differs from the incoming one

• Bundling of all of them

• All forming an E2E logical network, on top of a sharedinfrastrcuture, isolated from other slices, and withindependent control and management

What is a slice?

02 SDN for programmingTransport Networks

16

Core network operation is not adapted to flexible networking

• Multiple manual configuration actions are needed in core network nodes

• Hundreds of thousands of core nodes configurations per year in mid-size network operators

• Network solutions from different vendors typically use propietary Network Management System

(NMS) implementations

• More than 8 specific management implementations for service provisioning in multivendor core

networks (e.g Telefónica in Spain)

• Very long service provisioning times

• Up to two weeks for Internet service provisioning. More than 6 weeks for core routers connectivity

services

Traditional core network operation

Internet Voice CDN Cloud Business

Service

Management

Systems

Network

Provisioning

Systems

Metro

NMS

NMS

Vendor

A

IP Core

NMS

Optical Transport

NMS

Umbrella Provisioning System

Complex and long workflows for

network provisioning over

different segments (metro, IP core,

Optical transport) requiring

multiple configurations over

different NMS

NMS

Vendor B

NMS

Vendor C

NMS

Vendor

D

NMS

Vendor E

NMS

Vendor C

NMS

Vendor

A

NMS

Vendor B

Metro

Node

Vendor

A

Metro

Node

Vendor B

IP

Node

Vendor C

IP

Node

Vendor

D

IP

Node

Vendor E

Optical

Node

Vendor

A

Optical

Node

Vendor B

Optical

Node

Vendor C

Core Network

Nodes

CURRENT APPROACH FOR NETWORK PROVISIONING

17

Automated Network Creation

Hours

Hours/Days

Hours

Hours/Days

Very costly• Time• Money• Human dependent• Network Human

Middleware Can’t Scale

CURRENT NETWORK CREATION PROCESS

Ex. Infrastructure service

for new IP link in backbone

18

Automated Network Creation

< 1 second

Seconds

< 1 second

AUTOMATED NETWORK CREATION PROCESSController

Controller with multi-layer

orchestration capabilites

19

• Evolution towards an Elastic Core Network paves the way towards a unified

network provisioning architecture

• Multiservice provisioning

• Automated multidomain/vendor/layer operation by signaling

• Key building blocks of such unified network provisioning architecture are

• Network configuration interface: Multivendor edge nodes configuration (e.g OLT and BRAS,

IP core routers, Optical equipment, etc) by standard interfaces (e.g Netconf)

• IT and network SDN orchestration: Coordinated network and datacenter resources control

according to service requirements (e.g orchestrated Virtual Machine transfer among DCs)

• Network-Service API: Application level API hiding details of the network

Elastic core network operation

Internet Voice CDN Cloud Business

Multiservice network provisioning system

(SDN Orchestrator)

Standard signaling mechanisms running over network nodes enabling flexible

networking and automated network provisioning over different network

segments (metro, core IP, optical transport, MW) including multiple vendors

Metro

Node

Vendor

A

Metro

Node

Vendor

B

IP

Node

Vendor

C

IP

Node

Vendor

D

IP

Node

Vendor

E

Optical

Node

Vendor

A

Optical

Node

Vendor

B

Optical

Node

Vendor

C

Service

Management

Systems

Network

Provisioning

Core Network

Nodes

Network-Service API

Network configuration

interface

20

• Decoupling of Network

and Support Systems

• Multivendor systems

interoperability

• Network domains

(MW, Metro-IP)

combining network

elements from

different vendors

E2E SDN Orchestration

• What is needed?

o Common SBI per technology for MW, Metro/MBH and IP

o Common SDN controller per technology. Mediation layer in first

deployments while a common SBI is defined.

o Standard NBI between towards current systems and controllers

21

The fundamental change of SDNProprietary Firmware

- Proprietary OSS

- Proprietary services- Processing only in the NE

- Open interfaces

- One model for all

(abstraction)

- Fully disclosed to public

- Applications can be provided

by any SW-vendor

- Processing anywhere

VendorA

VendorB

VendorC

Common Information Models are

key to achieve the proper level of

abstraction among vendors,

facilitating a common and unique

control of the network elements

- Multilayer approach for

performing combined

optimization

- Standard interfaces simplify

heterogeneous device

management

- Interconnection of controllers

for e2e optimization

22

Common SBI?? Standard NBI??

03NFV for agile

deployment of services

24

• Traditional telecommunications industry

o Based on deploying physical proprietary equipment for each function that is part of a given service

o Service components have strict chaining/ordering that must be reflected in the network topology

o Requirements for high quality, stability and protocol adherence

� This has led to long product cycles, very low service agility and heavydependence on specialized hardware

• Users (including verticals) increasingly demand more diverse and short-lived services with high data rates

o Need for purchase, store and operate new physical equipment

o New and rapidly changing skills to operate and manage the equipment

o Dense deployment of network equipment

o Cannot be translated in higher subscription costs

o Providers forced to find new ways of building more dynamic and service-aware networks, with shorter product cycles, cheaper and more agile

Motivation for NFV

25

Implications of NFV

� NFV implies a decoupling of the network functions from

the supporting hardware

� Arbitrary distribution of service (network function)

capabilities across the network

� NFV will allow a rapid and

flexible deployment of

services

• Then rapid and

flexible network

connectivity is

required

• … in an optimal way

26

Network Functions - Resource Requirements

Business CPEBusiness CPE

ServiceAppliances

(L4-L7)

ServiceAppliances

(L4-L7)

Core Backbone Routing,CE Access-Aggregation

and DC switching

Core Backbone Routing,CE Access-Aggregation

and DC switching

Wireline GWsWireline GWs

Home CPEHome CPE

Wireless GWs

Wireless GWs

CPU

Reqs

0 10Mbps 100Mbps 1Gbps 10Gbps 100Gbps 1Tbps 10Tbps 100Tbps 1Pbps

High

Low

Distributed: CPUs

Distributed: Lots of CPUs CPU

Centralized: CPU

Variable CPU / FPGA / NPU

OSS/BSS, subsystemand N/W control

OSS/BSS, subsystemand N/W control

27

NFVIDeployment of computing

facilities across operator’s

networks brings the

opportunity of offering

part of such infrastructure

to third parties

The way of sharing

those facilities is

foreseen to take

place by means of

open interfaces

Ex. Verticals in NGMN in

5G White Paper

28

• Reduced equipment costs through consolidating equipment and exploiting the economies of scale of the IT industry

• Increased velocity of Time to Market by minimizing the typical network operator cycle of innovation

• Much more efficient test and integration

o Production, test and reference facilities can be run on the same infrastructure

• Targeted service introduction based on geography or customer sets is possible

o Services can be rapidly scaled up/down as required

o Service velocity is improved by provisioning remotely in software without any site visits required

• Enabling a wide variety of eco-systems and encouraging openness

• Optimizing network configuration and/or topology in near real time based on the actual traffic/mobility patterns and service demand

Benefits of NFV

29

• Supporting multi-tenancyo operators can provide tailored services for multiple users, applications or

internal systems or other network operators

o co-existence on the same infrastrcuture with appropriate secure separation of administrative domains

• Reduced energy consumption by exploiting power management features in standard servers and storage, as well as workload consolidation and location optimizationo E.g., to concentrate the workload on a smaller number of servers during

off-peak hours (e.g. overnight) so that all the other servers can be switched off

• Improved operational efficiency o higher uniformity of the physical network platform, eliminating the need

for application-specific hardware, with a reduction in variety of equipment for planning & provisioning

o IT orchestration mechanisms provide automated installation, scaling-up and scaling-out of capacity, and re-use of Virtual Machine (VM) builds

o Option to temporarily repair failures by automated re-configuration and moving network workloads onto spare capacity using IT orchestration mechanisms

Benefits of NFV

30

NFV framework at high level

NFV Infrastructure (NFVI)

Hardware resources

Virtualized Network Functions (VNFs)

VNF VNF VNF VNF

Virtual

Compute

Virtual

Storage

Virtual

Network

Virtualization Layer

Compute Storage Network

NFV

Management

and

Orchestration

Services

Virtual

resources

Physical

resources

31

NFV Reference Architecture

Virtualized

Infrastructure

Manager(s)

Virtualized

Infrastructure

Manager(s)

NFVI

Hardware resources

VNF 1 VNF 2 VNF 3

Virtual

Computing

Virtual

Storage

Virtual

Network

Virtualization Layer

Computing

Hardware

Storage

Hardware

Network

Hardware

EM 1 EM 2 EM 4

Vi-Ha

VNF

Manager(s)

NFV

Orchestrator

OSS/BSS

Virtualized

Infrastructure

Manager(s)

Nf-Vi Or-Vi

Vi-Vnfm

Ve-Vnfm-vnf

Os-Ma-nfvo

Or-Vnfm

NFV Management and Orchestration

Vn-

Nf

Execution reference points Other reference points

Main NFV reference points

Ve-Vnfm-em

VNF 4

EM 3Service, VNF and

Infrastructure

Description

04 On-going Relevant Innovation Actions

33

Ongoing Innovation Actions

Metro Access Metro Aggr BRAS/PGW IP Edge IP Core / ICX

2G/3G/LTE

DSLAM / OLT

S/GWT S/GWD S/GWC

Long HaulMetro

Transport

Service Centers

CDN

Internet

5G-Crosshaul (http://5g-crosshaul.eu/)

5G-Transformer (http://5g-transformer.eu/)

5GEx (http://www.5gex.eu/)

Verticals

5TONIC Innovation Lab (https://www.5tonic.org/)

34

Crosshaul: Fronthaul & Backhaul Integration

Crosshaul: 5G Mobile Transport Network

5G C-RAN will be transformed to a packet-basednetwork (NGFI/IEEE 1914). FH and BH will converge toan integrated transport network (Crosshaul):

• BW usage dependent on user’s load

� Higher efficiency

• Enables path diversity – Packet-based Routing

� Higher fault tolerance/Load balancing

• Unified management platform (FH + BH)

� Lower management complexity and cost

• C-RAN Functional split and placement

� Variable – Support of different functional splits

� Dynamic – NFV-based 5G networks

Today’ s C-RAN Mobile Transport NetworkCPRI transports IQ data via point-to-point optical links ina fronthaul (FH) network. Pain points:• BW usage is independent on user’s load

� Highly inefficient• No path diversity

� Low fault tolerance• Separated management platforms (FH - BH)

� Management complexity and cost• C-RAN Functional split and placement

� Fixed and Static

Processingcloud

Core Backhaul (BH) Fronthaul (FH)

CPRI

CPRI

CPRI

Point-to-point network

Processing UnitsRemote Radio Unit Core network functionForwarding Node

Processingcloud

Core Crosshaul: 5G Integrated FH/BH

Packet-based network

35

Geographical non-uniformity of usage of the radio

access

90% of the data is consumed in less than 5% of the area

90% of the data is consumed in less than 5% of the area

50% of the data is consumed in less than 0.35% of the area!50% of the data is consumed

in less than 0.35% of the area!

Transparently and dynamically

deliver mobile front-/back-haul in a

converged metro/access

environment, through elastic

networking for taking advantage of

the already deployed fiber

infrastructure

36

Converged Fronthaul and Backhaul under common

SDN/NFV-based control, capable of supporting new 5G

RAN architectures (V-RAN) and performance requirements

RMA EMMAXCF – Common Frame capable of

transporting the mixture of various

Fronthaul and backhaul traffic

XFE – Forwarding Element for

forwarding the Crosshaul traffic in the

XCF format under the XCI control

XPU – Processing Unit for executing

virtualized network functions and/or

centralized access protocol functions (V-

RAN)

XCI – Control Infrastructure that is SDN-

based and NFV-enabled for executing

the orchestrator’s resource allocation

decisions

Novel network apps on top to achieve

certain KPIs or services (Multi.tenancy,

CDN, TV Bcast, Resource Mngmt, Energy

Mngmt, Planning, etc)

Main building blocks

Partners: UC3M, NEC, Ericsson, Atos, Nokia,

InterDigital, Telefónica, Telecom Italia, Orange,

Visiona, Nextworks, Telnet, Fraunhofer, CTTC,

CreateNet, Politecnico de Torino, Lund Univ., ITRI

37

High-level Arch.

Data

plane

Control

plane

Management

and orchestration

plane

SDN

nets.

Network

Controller

Domain Orch

Packet/

Opto

Network

Controller

Domain Orch

Legacy

nets.

Network

Controller

Domain Orch

Network

Controller

PacketDatacenter

Network

Controller

Domain Orchestrator

Provider A administration Provider B administrationENNI

Network

Controller

PacketDatacenter

Network

Controller

Domain Orchestrator

Provider C administration

ENNI

Multi-

provider

OrchestratorAdministration A

Multi-

provider

OrchestratorAdministration B

Multi-

provider

OrchestratorAdministration C

Packet Packet

B2B

B2B

B2C

B2B

1

223 33

3

Business

Mgmt/Orch

Data

Control

3

5GEx focusWholesale

buyer interface

Customer

(Tenant)

2

Objective:

From dedicated physical

networks with dedicated

control and dedicated

services and resources for

different applications…

…to a “network factory”

where resources and network

functions are traded and

provisioned: new

infrastructures and services

are “manufactured by SW”

Partners include: Telenor,

Deutsche Telekom, Telecom

Italia, Orange, Telefónica,

Ericsson, Huawei, HPE, ATOS,

BISDN, RedZinc, UCL, UC3M,

AUEB, BME, KTH , MNS

38

5G-Exchange vision

Infrastructure owner

Wholesale provider

Retail provider

Content provider

End user

1. Resources are traded along a chain.

XY

2. Can buy from and sell to multiple partners

WZ

AB

3. Not only networking, compute/storage, too

Network Compute

Network Compute

Network Compute

Network Compute

VNFs

VNFs

VNFs

VNFs

VNFs

39

Use cases

NFVO

VNFM

VNFaaS provider OSS/BSS

NFVI

VNF

EM

VIM

NFVIaaS

End-Customer Facing Service Enablers

Slice as a Service

Config,Admin

&SupportServices

Value Added Connectivity

(VAC) Services

&

VNFaaS

ASQ Infrastructure Connectivity

Customer

Customer OSS/BSS

NFVI

VIM

VNFMVNFM

NFVO

VNF

EM

VNF

EM

3rd party OSS/BSS

40

New interconnection and wholesale model

• More efficient, flexible and globally

controlled interconnection models

via SDN

• New business and partnership

ecosystem enabled through APIs

• New potential revenue sources

• Deployment of VNFs working cleanly in

NFVI PoPs

• Capability for trading slices of

resources

3rd

Parties

Access level / Domestic Networks

Global

Direct interconnection deeper in the network with global SDN

control

Traditional interconnection at global level will be maintained for conventional services

Centralized Interconn.

control

Flexible Multilayer Peering

VNFs for 3 rd Parties

New interconnection model based on NFs instantiated in NFVI

POPs / Slice of resources

Multi-Domain Orchestrator

Domain Orchestrator

41

• 5G-Transformer aims to transform today’s mobile transportnetwork into an SDN/NFV-based Mobile Transport andComputing Platform (MTP)

• Technical approach

o Enable Vertical Industries to meet their servicerequirements within customized MTP slices; and

o Aggregate and Federate transport networking andcomputing fabric, from the edge up to the core and cloud,to create and manage MTP slices throughout a federatedvirtualized infrastructure

• Partners: Univ. Carlos III of Madrid, NEC Europe, Ericsson TI, ATOS, NOKIA, Interdigital Europe, Telefonica, Orange, Centro Richerche Fiat, Ayuntamiento de Madrid, BCOM, Nextworks, Mirantis, CTTC, Politecnico di Torino, EURECOM, SSSA, ITRI

5G-Transformer

42

• Vertical Slicer - logical entry point for verticals to support the

creation of their transport slices in a short time-scale

• Service Orchestrator - federation of transport networking

and computing resources from multiple domains

• Mobile Transport and Computing Platform - underlying

unified transport stratum

5G-Transformer

building blocks

43

5G-Transformer Concept

44

• 5TONIC is an open research and innovation ecosystem in the area of 5G

Products and Services

o Based on the direct collaboration between Telefónica and IMDEA

Networks

� Other members: Ericsson, Intel, Commscope, UC3M, Cohere

Technologies, Artesyn

� New members under negotiation

o Make industry and academia come together

o Boost technology and innovative business models

• Goal of becoming a central hub for knowledge sharing and industry

collaboration in the area of 5G technologies

o Across Europe, associated with the European 5G initiatives

• Initially focused on two main technology areas

o 5G Virtual Software Network Area

o 5G Wireless System Area

5TONIC lab as innovation facility

05Challenges

imposed by SDN and NFV

46

Challenged areas

Business

Organization

Operation

� Network buildingand running

� Business sustainability

� Operator evolution

47

• Network Operation

o Abstraction, APIs and information

models as a common way of

operating a variety of transport

technologies

o Self-learning and self-healing

o Resiliency

o Multi-tenancy, migration

o Networking, computing and storage

• Service provisioning

o Separation of service from transport

o Mapping of service requirements

and network capabilities

• Investment protection and migration

o Interworking between conventional

and SDN/NFV enabled assets

• Network planningo Change in the traffic patterns, less

predictability

o Need for smart and dynamic traffic engineering mechanisms

o Multi-layer coordination

• Network deploymentso Shortening time for introduction of

network elements

o Product homologation

o Function instantiation changes the way of commissioning functions in the network

o Co-existence of large and micro DCs

o Slicing

• Supportive systemso Smooth integration with OSS/BSS

o FCAPS and Inventory (for both service and transport)

o Configuration and activation decoupled

o Open Source

Operational challenges

48

• Departmental organization

o Department frontiers and technical boundaries are blurred

• Skills and know how

o SDN and NFV highly relay in software

o Multidisciplinary teams

• Partnership ecosystem

o Broader ecosystem of vendors and partners (atomization)

o Open Source

Organizational challenges

49

• Network and IT equipment

lifetime

o Re-programmability to extend

lifetime of networking gear

o Handling of IT gear offering

shorter lifecycles

• Procurement

o Atomization of the components

o Benchmarking

o Pricing models

o Guarantees (Atoms, Open

Source, in-house code, …)

o Spare parts

• Innovation and experimentation

o Fostering service innovation

o Shortening time to market

o Easier roll-back

• Analyticso Collection of information

requires to consider transport and service plane

o Billing and accounting

• Customizationo Programmability triggered by

the operator or by external customers

o APIs to minimize impacts on changes

o Isolation and security become essential

• Capabilities for sharing network infrastructureso Automatic and dynamic

configuration

o Business models

o Regulation

Business challenges

06 Conclusions

51

The Future

Scenario

Manage users and sessions,Local managed services

Capillarity, Capacity,Mobility support

Multiplexing Switching,Transport

Control functions,Regional managed services

Devices

Places

UsersUsers AccessAccess AggregationAggregation Local Points of PresenceLocal Points of Presence CoreCoreRegional Data

CentresRegional Data

Centres

Interconnection

Radio

Fiber

vv

COTS HW

LOCAL PoPs REGIONAL DATA CENTRES

Control Plane can be Centralised

Data Plane must be Distributed

OS + Hypervisor

SDN Switching

InfrastructureDomain

Service Domain

Network Domain

CDN Video

P-CSCF

S/PGW BNG

CGNATDPI

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)

CAPACITY(Homogeneous infrastructure)

MME

DRA

Slice 1

UP

CP

Slice N

52

• SDN, NFV and Slicing are the ingredients of the new 5G

Networks

• Important aspects not yet covered and in progress

• Multi-domain, SLA/Monitoring, Resiliency, Business negotiation, etc

• Automated and simplified/flexible network service

provisioning is a must

• Applies to different network segments (metro, core, data center…)

and technologies (IP/MPLS, optical, MW, OpenFlow…)

• Also to federated / multiple administrative domains

• The whole industry is challenged by SDN and NFV, in transition

towards a new reality promoted by the support of 5G slices for

vertical customers

Conclusions

53

Questions?

Thanks for your attention

This work is partially funded by the European Commission within

the H2020 Research and Innovation program 5G-Crosshaul (grant

no. 671598), 5GEx (grant no. 671636) and 5G-Transformer (grant

no. 761536) projects