5G Network Management and Orchestration: Network … Network... · 5G Network Management and...

5G Network Management and

Orchestration: Network Slicing –

The CHARISMA approachVasilis Glykantzis

Research Engineer

FITCE 15/12/2017, Thessaloniki, Greece

5G Network Management and Orchestration: Network Slicing, FITCE 15/12/2017, Thessaloniki, Greece,

Introduction

Software Defined Networking (SDN)

+

Network Function Virtualization (NFV)

=

Reduced CAPEX/OPEX costs

Flexibility

Programmability2


Multi-tenancy

• Infrastructure operator: virtualized infrastructure

Compute, storage, network

• Network slices

Dedicated resources

Traffic isolation

Resource isolation

• Virtual Network Operators (VNOs)

Operating on network slices

Inter-VNO communication over Evolved Packet

Core (EPC)3

Tenant ATenant B

EPC

Acce

ss

Ne

two

rkB

ackh

au

lU

se

r

devic

es

Internet


CONTROL PLANE

INFRASTRUCTURE PLANE

OSS/BSS

CAL3 CAL2

Back-haul Back/Front-haul Edge-haul

100G OFDM-PON Optical fibre/mm-wave/FSO

Central OfficeOptical fibre/mm-wave/FSO

IMU

Computing Networking

Storage

IMU


Storage

IMU


Storage

Cloud and Network (SDN) controllersNon-virtualized resources

controllers

Open Access Manager

NFV OrchestratorMonitoring &

AnalyticsPolicy Management

VNF Manager

CONTROL, MANAGEMENT AND ORCHESTRATION

VNO1

VNO2

VNO3

CAL0CAL1

IMU


Storage

UEs

Met

ro /

Core

VIRTUALIZATION PLANE

VNFs VNFs VNFs

VirtualLinks

VirtualLinks

VirtualLinks

VirtualLinksVNFsVNO 1

Logical Control

Data PathWireline

Wireless

Charisma Architecture

4


SDN Wireless Backhaul Device

5

OpenFlow agent

• Device independent agent

• Enables support for OpenFlow

e.g. establishes connections and handles OpenFlow messaging on backhaul switches

Adaptation Layer

• Device-specific layer

• Translates OpenFlow rules to a proprietary language, understood by the packet processor

Enhanced with Openflow metrics

• e.g. Traffic Policing

DATA PATH

CONTROL

PATH

OPENFLOW AGENT

DATA PATH ABSTRACTION

HW Engine

HW Engine

...


Cache peering & multi-tenancy

• Take advantage of vCaches co-located at μDCs

• De-encapsulation and re-encapsulation can take place inside the

μDC to avoid traversing the EPC [1]

• Advantages:

Reduce costs of transit inter-domain traffic

Reduce latency

6

Content

ServerInternet

vCache

vCache

Client

Client

IMU/ MEC Server

Peering link

[1] M. Rodrigues et al., “Enabling transparent caching in lte mobile backhaul networks with sdn,” in Proc. IEEE INFOCOM WKSHPS, April 2016, pp. 724–729.


Traffic Peering Management

Requirements

1. Enable communication of vCaches

• Low latency and high bandwidth vCache communication link

2. Prevent other forms of traffic to traverse the inter-VNO communication link

3. Authentication/Authorization of the involved vCaches

Solutions

1. μDC network configuration (e.g. RBAC feature of Openstack)

2. VM-level configuration (e.g. iptables)

3. Application-level configuration (e.g. access control mechanisms of Squid)

7


High-level Design - vCache Peering Simplified

8

Network Node

Compute Host(s)

VNO A

vCache

VNO B

vCache

Internet

EPC

VNO A Client

VNO B Client

Shared network (RBAC)

(cross-slice

communication)

Application-level peering

Transparent Caching

VNO A

vCC

VNO B

vCC

Content Server


Preliminary results

9

• Increase of Cache Hit Ratio (CHR) by 15.3%

• Decrease of Average Download Time (ADT) by 2.55%

• Increase of CPU Utilization by 8.72%

Zipf-like popularity (s=0.8), C=1% Catalog Size, r=1 req/sec


Preliminary results

10

• Seemingly modest benefits, BUT:

Peering CHR improvement equivalent to that of a 33%

increase of cache capacity,

o Though not reducing ADT as much

• Non-symmetric cache sizes:

(Non-linear) benefits, for both VNOs

s=0.8, r=1 req/sec s=0.8, r=1 req/sec


Preliminary results

11

• Non-symmetric load (request rates)

Modest impact on peering VNO

o e.g., 400% load on peer only 15.8% CPU

• Maximized peering benefits for similar catalogs

s=0.8, C=1% s=0.8, C=1%, r=1 req/sec,

q=0s=0.8, C=1%, r=1 req/sec,

p=1


Beyond CHARISMA

vCache peering

• Resource accounting

• Multi-party peering

• Traffic optimizations for hierarchical relationships

Traffic Handling

• Integration with CDN Management System

• Purging of inactive flow rules

• Enhancing flow rule extraction process

Multi-site/instance access log aggregation and weighting

Multi-criteria rule extraction e.g., low byte hit ratio

12

Vasileios Glykantzis

[email protected]

Supplementary Slides


In Brief

15

A global telecommunication systems and solutions vendor with extensive know-how and a proven track record.

67%international

activities

1,722employees

worldwide

70countries we

export to

19countries with

local presence

40years of

experience

3R&D

centers


In Brief

16

Intracom Telecom

designs, installs and

commissions energy-

related systems, providing

Smart Grids and Energy

Management solutions.

Intracom Telecom strategically

focuses on the delivery and

operation of top-notch services

for converged networking and

cloud computing solutions. The

company also offers a range or

Smart City solutions.

Intracom Telecom has been

building and enriching a wide

portfolio of advanced telco

software solutions, enabling

Operators to generate new

revenues and boost their

Customers’ Experience.

Intracom Telecom products

employ the most advanced

field-proven technologies

achieving and exceeding the

level of performance

required by the modern

applications for wireless

access and backhaul.

Wireless Access

& Transmission

Telco Software

Solutions

ICT Services &

Smart City Solutions

Energy

Solutions

Telecom

Operators

Utility

Companies

Large

Enterprises

Healthcare

Institutions

Public

Authorities

Core Offerings

Markets Served


High-level Design - vCache Peering

Internet

EPC

VNO A Client

VNO B Client

Content Server

Transparent Caching

VNO A

vCache

peering

Compute Host(s)

Vir

tua

lize

d In

fra

str

uc

ture

VNF LB VNF LB

VNO B

vCache

peering

VNO A

vCache 1

VNO A

vCache 2VNO B

vCache 1VNO B

vCache 2

Network Node

Shared network (RBAC)

(cross-slice

communication)

Reverse Proxy

Forwarding requests w/o caching

• Peering configured as a child of Local vCaches

Access to local content

• Local vCaches configured with peering as sibling

Querying on local miss


vCaching

Problem: Rapidly increased traffic in mobile networks

Counter-measure: Caching

Optimization: Caching using NFV + SDN in 5G Networks (vCaching):

• Flexibility

• Elasticity

• Traffic Handling

Challenge:

• Virtualization overheads (out of scope)

• Excessive redundancy in multi-tenancy environments

18


Cache peering

• Started for Web caching in the 90s

• Peering / Sibling caches

Forward a request on a client’s cache miss

Only if the content exists (case a)

o Re-active: Internet Cache Protocol (ICP)

o Proactive: Cache digests

Otherwise: reject (case b)

i.e., never further forward a peering request

• Motivation:

Assuming peers are closer than the Content server

Take advantage of already cached content

o Reduce delay & traffic overheads

19

Cache Cache

Client

Content

Server

Internet

1. Content

request2. Content availability

3b. Content

request 3a. Content

request


Setup pitfalls …

• Peering over EPC

• Highly inefficient when vCaches close to the edge

• Multiple traversals of the entire infrastructure

Both control & data plane traffic

• Delay & traffic overheads

20

Tenant ATenant B

vCache

EPC

Acce

ss

Ne

two

rkB

ackh

au

lU

se

r

devic

es

vCache

Internet


Traffic Peering Management

Requirements

1. Communication of vCaches

2. Prevent other forms of traffic to traverse the inter-VNO communication link

3. Authentication/Authorization of the involved vCaches

4. Low latency and high bandwidth vCache communication link

21

VNO A VNO B

Compute Host(s)Client

OSS/BSS

Virtualized Infrastructure / MEC Server

Os-M

aN

f-Vi

VNF

Manager(s)

Or-V

i

Or-Vnfm

Vi-Vnfm

Ma

na

ge

me

nt &

Orc

he

stra

tion

Orchestrator

Virtualised

Infrastructure

Manager(s)

Ve

-Vn

fm

Shared

network Peering / sibling link

VNFvCache

VNFvCache

Internet

Content

Server

Ne

two

rk

No

de


Resource accounting

Requirements

5. Increased load on the peering link should not affect local vCaches

22

VNO A VNO B

VNF

vCache

peering

Compute Host(s)

Client

OSS/BSS

External

Network

Vir

tua

lize

d In

fra

str

uc

ture

Os-M

aN

f-Vi

VNF

Manager(s)

Or-V

i

Or-Vnfm

Vi-Vnfm

Ma

na

ge

me

nt &

Orc

he

stra

tion

Orchestrator

Virtualised

Infrastructure

Manager(s)

Ve

-Vn

fm

VNF LB

Shared

network

VNF LB

VNF

vCache

peering

Client

VNF

vCache 1

VNF

vCache 2VNF

vCache 1VNF

vCache 2

Cache sibling link

(application level)

Network Node

Parent link

Shortcomings:• Content fetched by

peering vCache

• Local vCaches depend

on the peering vCache


vCache peering with prefetching

VNO A VNO B

VNF

vCache

peering

Compute Host(s)

Client

OSS/BSS

External

Network

Vir

tua

lize

d In

fra

str

uc

ture

Os-M

aN

f-Vi

VNF

Manager(s)

Or-V

i

Or-Vnfm

Vi-Vnfm

Ma

na

ge

me

nt &

Orc

he

stra

tion

Orchestrator

Virtualised

Infrastructure

Manager(s)

Ve

-Vnfm

VNF LB

Shared

network

VNF LB

VNF

vCache

peering

Client

VNF

vCache 1

VNF

vCache 2VNF

vCache 1VNF

vCache 2

Cache sibling link

(application level)

Network Node

Prefetching

23

Shotcomings:

• Complexity introduced from the prefetching mechanism

Content fetched

by local vCache


Experimental Testbed

24


Experimental Testbed


Adaptation layer on Network Processor + OpenFlow agent

SDN controller (OpenDaylight) with Carrier Ethernet application

Southbound interface → OpenFlow

Northbound interface → Rest API

802.1ad (QinQ) standard through OpenFlow -> S-VLAN (TPID 0x88A8) identifies the VNO and C-VLAN (TPID 0x8100) the customer of each VNO

Open Access Manager which interacts with the SDN controller’s REST API in order to deploy E-LINE EVPL services

SDN Wireless Backhaul


1. Backhaul switches initially connected to the controller.

The controller identifies each switch Datapath ID (DPID) and port names.

2. Link Layer Discovery Protocol (LLDP) to identify the network topology.

3. OAM sends a request to the SDN controller (REST API), describing

Switches/ports where the services are going to be deployed

A set of VNOs and the C-VLANs per VNO

4. Graph traversal algorithm to calculate an end-to-end path between the selected network

nodes

Loop prevention

5. OpenFlow modification messages to the backhaul switches to deploy slices

Adding flow entries

Services based on 802.1ad standard

Control plane


Conclusion & further steps

• Virtualization presents opportunities for new service setups:

vCache peering now builds on co-location

Establishing high performance inter-domain links

• Programmability/MANO capabilities in 5G networks present opportunities for:

Automatic establishment of a cache peering agreement

Monitoring of the business agreement

• Challenges:

Security

Virtualization overheads

Performance/resource isolation

• Next steps:

Quantify benefits

Full-blown experimentation

28

5G Network Management and Orchestration: Network … Network... · 5G Network Management and...

Documents

Transcript of 5G Network Management and Orchestration: Network … Network... · 5G Network Management and...