ciavaglia univerself -filling the gap of a sdn management

Filling the gap of a SDN management layer

with the

Unified Management Framework (UMF)

3rd ETSI Workshop on Future Network Technologies

9-11 April 2013, Sophia Antipolis

WWW.UNIVERSELF-PROJECT.EU

9-11 April 2013, Sophia Antipolis

SOFTWARE-DEFINED AND SELF-MANAGED NETWORKSMUTUAL BENEFITS

2 MAJOR PHENOMENONS

IMPACTING THE DESIGN, DEVELOPMENT AND OPERATION

OF VIRTUALLY ALL NETWORKING TECHNOLOGIES

23rd ETSI Workshop On Future Network Technologies, 9-11 April 2013, Sophia Antipolis

MUTUAL BENEFITS

?

SDNSOFTWARE DEFINED NETWORKS

SMNSELF MANAGED NETWORKS

SDN SMN

COMMONALITIESDisruptive, challenging technologies

Carrier grade environment

Software centric



SDN SMN

Programmability

Virtualization

Control/Data decoupling

Closed control loop

Cognition

Management framework

PROGRAMMABILITY

Application Programming Interfaces

Open execution environment

SDN SMN

Benefits toProvides



SDN SMN

Programmability

Virtualization


Closed control loop

Cognition


Ability to trial and deploy innovative | autonomic functions

o more freely

o in a well-defined manner

o at lower risk

SDN SMN


MANAGEABILITY

Integrated management capabilities for

deployment, operation, information processing

Benefits to Provides


SDN SMN

Programmability

Virtualization


Closed control loop

Cognition


Injects

new requirements Adapt enablers

Ability to manage converged infrastructures based on a

unified and thin platform

Generic enablers for

o goal-driven operation and lifecycle management

o information exchange and analytics

o coordination of concurrent/competing mechanisms

o run-time trust assessment

Cutting-edge network empowerment portfolio

SDN SMN

APPLICABILITYInfrastructure heterogeneity and complexity

Proven feasibility, performance, flexibility

Trustworthy operation



SDN SMN

Programmability

Virtualization


Closed control loop

Cognition


SDN currently applied to some networking technologies

o flow-based networks, cloud/data centers

o heavy industry trend

o widening scope: optical/transport, mobile…

SMN already applied to multiple networking technologies

o large catalogue of experimentations

o leading case: 3GPP/LTE SON

o still tagged “research”/limited footprint in industry

SDN SMN

COMMONALITIESDisruptive, challenging technologies

Carrier grade environment

Software centric


MANAGEABILITY

Integrated management capabilities for

deployment, operation, information processing

FOCUS ON


SDN SMN

Programmability

Virtualization


Closed control loop

Cognition


APPLICABILITYInfrastructure heterogeneity and complexity

Proven feasibility, performance, flexibility

Trustworthy operation

PROGRAMMABILITY

Application Programming Interfaces

Open execution environment

SDN MANAGEABILITYSOME REQUIREMENTS

Req. 1 Ability to deploy and operate applications in a seamless, plug-and-play manner

Req. 2 Ability to configure applications using goal-driven, close-to-natural language

Req. 3 Ability to span across multiple technologies (e.g. fixed, mobile, service)

Req. 4 Ability to provide end-to-end, aggregated/service-oriented view(s)


Req. 4 Ability to provide end-to-end, aggregated/service-oriented view(s)

Req. 5 Ability to measure, assess, and report applications performance

Req. 6 Ability to guarantee stable behavior of individual and group(s) of application(s)

Req. 7 On par with existing technologies for scalability, efficiency, reliability, security…

* the list is not exhaustive and open for comments

UNIVERSELF VALUE PROPOSITIONFRAMEWORK, ENABLERS AND EMPOWERMENT MECHANISMS

NETWORK

EMPOWERMENT

MECHANISM

(NEM)

NEM = use of relevant method to solve a concrete operational problem

in a specific networking environment

o e.g. use of genetic algorithm for interference coordination in LTE

networks

NEM = a real autonomic function controlling network resources


NEM SKIN = unified abstraction of NEM

o common set of objects describing its properties and capabilities

e.g. manifest, mandate, instance description

o common set of interfaces to connect and interact with the UMF

and other NEMs

o set of technology-specific adaptors

NEM SKIN = vector of unification, re-usable software component, and

an accelerator for NEM implementation

UNIFIED

MANAGEMENT

FRAMEWORK

(UMF)

UNIVERSELF VALUE PROPOSITIONFRAMEWORK, ENABLERS AND EMPOWERMENT MECHANISMS

NETWORK

EMPOWERMENT

MECHANISM

(NEM)

NETWORK

EMPOWERMENT

MECHANISM

(NEM)

NETWORK

EMPOWERMENT

MECHANISM

(NEM)

One framework to manage multiple/any types of NEMs

Ability to cope with NEM ecosystem diversity

o heterogeneity of NEM function/goal

o multiple technology domains

o multiple roles and interactions among NEMs


UNIFIED

MANAGEMENT

FRAMEWORK

(UMF)

o multiple roles and interactions among NEMs

with same models and interfaces (cf previous slide)

Specification of core functions, workflows and NEM lifecycle

3 core functions:

o governance, coordination, knowledge

o and associated mechanisms e.g. conflict avoidance, data mining…

Responsible for:

� The interaction between human operator and

its network→ express business goals report on

critical states of self-managed

operations/devices

� Driving NEMs’ behavior→ policy-based

framework for translating business-level,

service specific goals/requests into low level,

policies and configuration commands

UMF IN A NUTSHELLUMF CORE FUNCTIONAL BLOCKS

1

1

policies and configuration commands

GOVERNANCE �� NEM:

� Commands to set NEM’s status/mode (e.g.

active, idle, stopped) and configure its

operational parameters.

� Report on the NEM’s operational conditions

and configuration characteristics (e,g.

performance indicators,

capabilities/behaviour, interaction with other

NEMs).

Functional decomposition


Responsible for:

� Prevent the network from instabilities and

side effects due to the multiple NEMs running in

parallel

�Ensuring the proper sequence in triggering of

NEMs, their stable operations, and conditions

under which they will be executed taking into

account:

� Operator and service requirements,


1

2

� Operator and service requirements,

� Needs for Conflict avoidance, joint

optimization and stability control.

COORDINATION �� NEM:

� Commands to drive coordination including:

tokens, timing, constraints, status

(active/idle), etc.

� Information on the NEMs operation

including: parameters, metrics, scope, utility

functions, etc.



Responsible for:

�Providing the suitable probabilistic models

methods and mechanisms for processing and

exchange of knowledge, based on :

� Context and configuration information

from NEMs,

� Policies from Governance,

� Information on NEM interactions from

coordination Functional decomposition


1

3

coordination

KNOWLEDGE �� NEM:

� Commands to retrieve, share, derive and

manage knowledge including: publish,

subscribe, push, pull, request, store, notify …

messages.

� Registration of NEMs.



SDN MANAGEABILITYMATCHING REQUIREMENTS

Req. 1 Ability to deploy and operate applications in a seamless, plug-and-play manner Governance, Lifecycle, NEM Skin

Req. 2 Ability to configure applications using goal-driven, close-to-natural languageGovernance, Policy Continuum, Policy

language

Req. 3 Ability to span across multiple technologies (e.g. fixed, mobile, service)NEM Skin, Governance, Information

model

Req. 4 Ability to provide end-to-end, aggregated/service-oriented view(s)Governance, Knowledge, Information

model


Req. 4 Ability to provide end-to-end, aggregated/service-oriented view(s)model

Req. 5 Ability to measure, assess, and report applications performance Governance, Knowledge, Knowledge

building mechanisms

Req. 6 Ability to guarantee stable behavior of individual and group(s) of application(s)Coordination + orchestration

mechanisms

Req. 7 On par with existing technologies for scalability, efficiency, reliability, security… Partially covered/validated

JOINT STANDARDIZATION OPPORTUNITIESWHAT AND WHERE

What to do / standardize Where

Collaboration: SDN and SMN are studied in different bodies which may result in different specifications in managing applications/autonomic functions

All involved SDOs/fora

Definition of a reference set of requirements and design principles for SDN management

Multi-SDOs initiative

Design and specification of the management framework (functions, objects, states)

ETSI / IETF / ITU-T / ONF


Extension to information model(s) and techniques TMF

Applicability to technology domain(s) and adaptors, feasibility, proof of concepts ETSI AFI / ONF / IETF / …

Tests specifications, conformance testing, interoperability testing, certificationETSI AFI, MTS, CTI / 3rd

party org.

LTE SON coordination framework 3GPP / ETSI AFI

* the list is not exhaustive and open for comments

2 MAJOR PHENOMENONS IMPACTING THE DESIGN, DEVELOPMENT AND OPERATION

OF VIRTUALLY ALL NETWORKING TECHNOLOGIES

CONCLUSIONSTAKE AWAY MESSAGES

AUTONOMIC FUNCTION = [ SMART | ADAPTIVE | COGNITIVE ] SDN APPLICATION

ABILITY TO TRIAL AND DEPLOY NEW INNOVATIVE APPLICATIONS AT LOWER RISK

UNIFIED MANAGEMENT FRAMEWORK


UNIFIED MANAGEMENT FRAMEWORK

SPECIFIED, DEVELOPED, VALIDATED AND DEMONSTRATED ON REAL-LIFE USE CASES

NEED TO FOSTER JOINT DEVELOPMENT, DEPLOYMENT AND STANDARDIZATION FOR

A COMPREHENSIVE AND INTEGRATED TECHNOLOGY

WHAT ABOUT RELATIONSHIP WITH NFV…?

TOPIC OF ANOTHER PRESENTATION… WOULD BE HAPPY TO DISCUSS OFF-LINE

MEET US & OUR LIVE DEMOS AT…

Future Internet Assembly (FIA) Dublin, 8-10 May

Integrated Network Management (IM) Ghent, 27-31 May

Future Network and Mobile Summit (FUNEMS) Lisbon, 3-5 July


CONSORTIUM

18Event, Date, Location

Japan

PROJECT ID

� FP7 Call 5 Integrating Project

� Total Cost: ~16M€ ; EC Contribution: ~10M€

� 16 Partners (3 Vendors, 4 Operators, 4 Research Institutes, 5 Universities)

� Coordinator: Alcatel-Lucent

�� Duration: 36 months

� Start date: 01/09/2010

� Website: www.univerself-project.eu

19Event, Date, Location

ciavaglia univerself -filling the gap of a sdn management

Documents