Enthr1-2--srv-mng-QoS-3 nov 2010-v0.3

8/3/2019 Enthr1-2--srv-mng-QoS-3 nov 2010-v0.3

1/138

ENTHRONE - service management

concepts for end to end QoS

assurance in multi-domain

environment

Presentation: Eugen Borcoci, UPB

2010

1

TSAC/SWMC course, October-Dec, 2010


2/138

CONTENTS

2

1. Enthrone Service management

2. Business actors in Enthrone framework

3. Inter-domain general peering model (I)

4. QoS parameters

5. SLA/SLS concepts applied in Enthrone

6. Peering models II

7. End to end QoS

8. Integrated management

9. Enthrone service management

10. Monitoring System

11. Service scenario example

12. Policy Based Management


3/138

1. Enthrone Service management - introduction

3

ENTHRONE IP Project FP6 507637 End-to-End QoS through Integrated

Management of Content, Networks and Terminals (www.enthrone.org)

Integrated management solution

E2E QoS architecture over het- nets

AV services, delivered at various user terminals

Distributed architecture

Heterogeneous networks (IP, DVB, different access types)

Concepts applied

PBM in IP and extended to het-netsSLA/SLS

MPEG-21 data model - support for multimedia content

generation, protection and delivery


4/138

1. Enthrone Service managementAbstraction levels of QoS-related information (mapped to the

SLA/SLS templates):QoS parameters:E2E perceived (PQoS), Application SW,

Transport/network

Constraints: ES (terminal) specific resource parameters

Enthrone

E2EQo

Sservice model (multi

-domain)

Content discovery by SP, set-up of pSLA : SP/CP

Initial Service Planning at SP

pSLA/pSLS chaining (forward cascade model)

Signalling at mng. level- for subscriptions

Individual cSLAs: CC/SP, then service invocations

AC functions (two levels)

Monitoring system: Node, domain, inter-domain

NQoS and pQoS monitoring, DIA (adaptation)

4


5/138


5

CC- Content consumer (Company, End users)Customer ( org)

End user

CP- Content ProviderCPM content provider manager

CS1, CS2, - Content Servers

SP- Service Provider (higher layer services)

NP- Network Provider (connectivity services)

ANP Access Network Providers


6/138


Customer requirements: ability toCustomer requirements: ability to dynamically subscribe/unsubscribe and invoke services

send/receive traffic with e2e QoS guarantees via different terminals

verify the fulfillment of contract

Provider requirementsProvider requirements

Extending the geographical span of its QoS services Generating, Protecting, and QoS delivery of the content

Service management including service advertisement, discovery, selection, requesthandling/ordering(cSLA, pSLS), and modifying the contracts

Ability to verify the fulfillment of the contracts, SerMon, NQoS, PQoS

Accounting, charging and billing

Ability for the proposed management system to function effectively in scalablemanner

Deployment easiness

Ability for the system to be managed easily

6


7/138

3. Inter-domain general peering models

Hub model

7

SERVICE

PROVIDER

USER

CUSTOMER

CONTENT

PROVIDER

CONTENT

MANAGER

CONTENT

SERVER

IP

NETWORK

PROVIDER

PROVIDER

1

543

2

7

8

IP

NETWORK

PROVIDER

PROVIDER

IP

NETWORK

PROVIDER

PHYSICAL

CONNECTIVITY

PROVIDER

PROVIDER

PHYSICAL

CONNECTIVITY

PROVIDER

PHYSICAL

CONNECTIVITY

PROVIDER

Data


8/138

3. Inter-domain peering general models

Cascade model

8

SERVICE

PROVIDER

USER

CUSTOMER

CONTENT

PROVIDER

CONTENT

MANAGER

CONTENT

SERVER

IP

NETWORK

PROVIDER

PROVIDER

1

54

3

2

7

8

IPNETWORK

PROVIDER

PROVIDER

IPNETWORK

PROVIDER

PHYSICAL

CONNECTIVITY

PROVIDER

PROVIDER

PHYSICALCONNECTIVITY

PROVIDER

PHYSICALCONNECTIVITY

PROVIDER

Data


9/138

4. QoS parameters

Abstraction levels of QoS-related information (mapped tothe SLA/SLS templates):

End-to-end perceivable QoS (PQoS) parameters

users perception of the performance of the distributed application. The

translation of the PQoS characteristics into more technical terms is usually

implemented inside the software application that offers the service.

Application QoS parameters

E2E appl. performance (e.g. video frame size, frame rate, visual quality, etc.), in

accordance with SW/HW resources of end systems/services. In E2E negotiation,

these parameters are negotiated between the peers for co-ordinating end-to-

end QoS, in the form of QoS contracts at application level.

9


10/138

4. QoS parameters

Abstraction levels of QoS-related information (mapped tothe SLA/SLS templates) cont. :

End system (terminal) specific resource parameters

available memory, CPU-power, battery power in mobile terminals, etc. They are

not negotiated, but may be applied to generate specific end system policies for

t h e e n d s y s t e m r e s o u r c e - r e s e r v a t i o n m a n a g e m e n t .

Transport/network QoS parameters

E2E requirements w.r.t. network resources. These values are derived based on

actual capabilities/codecs and their specific QoS configurations, media

characteristics, and available network access technology. In end-to-end

negotiations these parameters are associated with QoS contracts at transport

level

10


11/138

4. QoS parameters

QoS- mapping:E2E PQoS / application QoS parameters

can be derived by conducting subjective experiments.

application QoS parameters / transport/network QoS parameters

depends on codecs, codec-configurations, and the media characteristics

For audio content, this mapping is more straightforward (a codec together withits parameterisation results in network traffic requirements)

For variable bit-rate video streams, the mapping also depends on the target

visual quality and the amount of motion.

11


12/138

4. QoS parameters

12

Quality

considerationDescription Units/parameters

Requirement/Co

nstraint from

End-User View

Perceived QoS

(PQoS)Users perception

Platinum/Olympic, Gold, Silver,

Bronze

R

Application level

Application software

(e.g. NetMeeting,RealPlayer)

requirements

Video: Codec, frame size, frame rate,

colour depth.Audio: Number of channels, sampling

rate

R

Terminal Terminal characteristicsProcessing power, memory etc.For video terminals: Resolution,

number of colours, frame rate, encoders

C

AccessConnectivity

Access last milecharacteristics

Bandwidth, performance-relatedinformation

C

NetworkNetwork level QoS

parametersBandwidth/throughput, packet loss,

delay, jitterC

Table 1: Different service quality considerations (requirements/constraints)


13/138

5. SLA/SLS concepts- applied in Enthrone

13

SLA/S Service Level Agreements/Specifications

Table 2: SLA template with clauses (optional/mandatory)SLA Element/Clause Attributes/Parameters Description

Resource Digital Item Id Identifier for the Digital Item

Scope Addresses User end-point, Content end-point

Type of service Premium or Olympic Service User perception

Service schedule &Activation time

Service invocation time/date Content delivery start and stoptimes

Application level

(Traffic andPerformance)requirements/constraints

MPEG-7 Media Information and

Media Format, Service Classcanonical meanings

Application performance

requirements

Terminal capability MPEG-21 Terminals Descriptor(codecs, processing power)

Terminal capability constraints

Connectivity/Access Access Networks information(MPEG-21 Network Conditiondescriptor)

Last-mile connectivity information

Availability Guarantees Reliability, Outages, Interfacethroughput

Guarantees for service invocation

Reliability Guarantees Mean downtime (MDT), Meantime to repair/patch (MTTR)

Service guarantees in terms ofreliability

Security Authentication & authorisationparameters etc.

Information required for using theservice and accessing the content

Billing By DI content, SP contract, etc. Cost and payment aspects

Others


14/138


14


Table 3: SLS template

SLS Element/Clause Attributes Description

SLS Identification Key A unique identification key (set by service

provider).

Scope Ingress-Egress points Identifies the topological region over which the

QoS applies (IP addresses or layer 2 identifiers).

Flow Identification DSCP, source, destination,

application information

Defines the stream of IP datagrams.

Traffic Conformance

(TC)

TC Algorithm and

parameters for in and out of

profile packets

Describes the criteria that injected traffic should

comply with to get QoS guarantees specified by

Performance Guarantee clause. TC information is

required for configuring traffic conditioners at

the edge and border routers. TC algorithms are

leaky bucket, token bucket etc. and TC

parameters are peak rate, token bucket depth, etc.

Excess Treatment Action for out-of-profiles

packets

Describes how the excess traffic will be treated.

Network LevelPerformance

Guarantees

Delay, loss, jitter,throughput, error

Describes the performance guarantees a provideragrees to offer to the packets entitled to this SLS.

Service Schedule

(optional)

Timetable for delivery

planning

Describes possible time intervals allowed for

service invocation.

Reliability (optional) MDT per-year etc. Describes the allowed figure of non-availability

of the service


15/138


15


QoS classes definitions

A QoS transfer capability, is a set of attribute-value pairs, where the attributes express

various packet transfer performance parameterssuch as one-way transit delay, packet

loss, and inter-packet delay variation (jitter), and their particular values.

A provider domainssupported QCs are divided into local QoSclasses(l-QCs) and

extendedQ

oSclasses

(e

-QCs), to allo

wus

to capture t

he not

ion of QoS capa

bilitie

sacross domains.

From a service offeringperspective, QoS classes correspond to the performance

(transfer quality) guarantees expressed in contracts as SLSs.

From a service provisioningperspective, QoS classessplit the network QoS space

into a number of distinct classes, and hence set the traffic-related objectives of trafficengineering functions. The concept of l-QC could be compared to the differentiated

services (DiffServ) per domain behaviors (PDBs).


16/138


16


QoS classes definitions (contd)

QoSclass(QC): is a basic network-wide QoS transfer capabilityof a single

providers domain. It is defined (in Diffserv technology,but not only) as a set of

parameters expressed in terms of {Delay, Jitter, Latency}.

Local QC(l-QC): a QC that spans a singleAutonomous System (AS). Thisis

a notion similar to Per Domain Behaviour (PDB) in Diffserv technology).

ExtendedQC(e -QC): a QC that spansseveralASes.

It consists of an ordered set of, l-QCs.

The topological scope of an e-QC therefore usually extends outside the

boundaries of the local domain.


17/138


17

Centralised/hub ModelsThe central point communicate with all NP to construct an e2e path.

It shouldknowthee2etopologyof inter-domain network.

SP has to manage all of the pSLSs.

Ingress Domain

AS1

Egress DomainTransit Domain

AS2 AS3

PE PE

P

P

P

P P

P

BRBRBRBR

pSLS3

pSLS2

cSLS

Service Provider

pSLS1

PE / P / BR: Provider Edge / Provider (Core) / Border Router

SLS OrderHandling

pSLSOrdering

Mgt. Plane

cSLS

Ordering

Customer B

SLS OrderHandling

pSLSOrdering

SP Mgt. Plane

SLS OrderHandling

pSLSOrdering

Mgt. Plane

SLS OrderHandling

pSLSOrdering

Mgt. Plane

cSLS

Ordering

Customer B


18/138


18

Reverse Cascaded ModelReverse build up of the cascade.

Only neighbourASs negotiate directly.

Each NP can makepSLScontractswith the immediately adjacent interconnected

NPs as long asit offer QoS-based services

Inter-domain routing information needed in NPs

Ingress Domain

AS1


AS3

PE PE

P

P

P

P P

P

BRBRBRBR

pSLS2vpSLS1

cSLS


l-QC2 l-QC1l-QC3

e-QC1

e-QC2

cSLS

Ordering

CustomerA

cSLS

Ordering

Customer B

SLS Order

Handling

pSLSOrdering

Mgt. Plane

SLS Order

Handling

pSLSOrdering

Mgt. PlaneSLS OrderHandling

pSLSOrdering

Mgt. Plane

Forward

DirectionUpstream

Downstream

AS2


19/138


19

Inter-domain peering for QoS chaining:forward cascaded modelForward Cascaded Model (this model is adopted in Enthrone)

Building the cascaded model in forward direction.BGP route isused to form the pSLS negotiations aswell as QoS-enabled traffic routing

Ingress Domain

AS 1


AS 3

PE PE

PP

P P

BRBR

pSLS3pSLS2

cSLS

Ordering

Customer A

cSLS

Ordering

Customer B

SLSOrder

Handling

pSLSOrdering

Mgt. Plane

SLSOrder

Handling

pSLSOrdering

Mgt. Plane

Downstream

P

P

BRBR

Upstream

AS 2

Forward

Direction

cSLS

Service Provider

pSLS1

SLSOrder

Handling

pSLSOrdering

SP Mgt. Plane

P

P

BRBR

AS 5P

P

BRBR

AS 4

SLSOrder

Handling

pSLSOrdering

Mgt. Plane

BGP best-effortroute

Transit Domain

Transit Domain Transit Domain

AS1_Local-QCEF

BBBBBB

AS2_Local-QCEFAS3_Local-QCEF

PE: Provider Edge router; P: Provider (Core) router; BR: Border Router


20/138


20

Reserving the network resources at aggregated levelSLS subscription is a promise only - to allow a certain amount of resource usage ( logical

reservation - at the pSLS aggregated level )A pSLS chain need to be established (subscription phase)

After the pSLS chain issubscribed, the pSLSs pipe/link ( composed of link segments)

can be ( invoked) i.e.installed in the network and resources are actually allocated-

through the intra-domain res. Mng.i.e.RM)Invocation may be commanded by the SP orby the CP ( in this figure the CP is

initiating the invocation)

Ingress Domain

AS1

Transit Domain

AS2

PE

P

P

P

P

BRBRBR


pSLS1

cSLS

Egress Domain

AS4

PE

P

P

BR

pSLS3

Transit Domain

AS3

PE

P

P

BR

pSLS2

SLSM

RAM

RM

SLSM

RAM

RM

RAM

RM

SLSM

RAM

RM

SLSM

cSLS Sub.

CP - A

cSLS Invoc

cSLS Sub.

CC - B

cSLS Invoc

1

2 34

5

6

789

10

SLSM SLS Manager;

RM Resource Manager;RAM ResourceAvailability Matrix


21/138

21

l-QC1l-QC4 l-QC3 l-QC2

AS1

AS2 AS4

AS6

B

AS3

cSLS3

pSLS8

cSLS2

pSLS1

pSLS7 pSLS3

pSLS2

pSLS6

AS7

E

pSLS4

l-QC7l-QC6 l-QC2

l-QC5

AS5

l-QC0

l-QC8

pSLS5

pSLS9

cSLS1

CCon

sumer/Customer

D

A

Content/Customer

l-QC: Local-QC

cSLS pipes and pSLS pipes usage

Inside a pSLS-pipe there can be many cSLS-pipes

Aggregation of pSLS-Pipesis possible



22/138


22


Enthrone- summary of contract types:

pSLA, pSLS- between providers- aggregated level (scalability)

SP/CP, SP/NP, NP/NP,

cSLA/cSLS

cSLA: CC/SP

cSLS: SP/NP

Two phase approach for service management

Service subscription ; e.g. pSLS subscription

Service invocation


23/138

7. End to end QoS

Enthrone

E2E

QoS

assurancepSLA/pSLS, cSLA/SLS chaining

Admission control (AC) functions - two levels

Subscription phase ( yes/no AC decision depends on resource availability considering previous subscriptions)

Invocation phase

yes/no AC decision depends on

Subscription parameters

Invocation parameters (subset)

network status

Newtwork Monitoring system

Node, domain, inter-domain

Service level monitoringpQoS monitoring

DIA (adaptation)

23


24/138

7. End to end QoSExample: Enthrone multi-domain environment

24

AS4

Each entity ( CP-M, CC-M, SP-M,AN-M,AS-Mcan be modelled as an SDL block

pSLA

AS3

AS2

AS1

AN3

AN5

AN4

AN1

CP1

CC2

SP1

CC3

CC1

CC4 CC5

cSLA

M

M

M

M

M

M

M

cSLA

pSLS1

pSLS2 pSLS3

M other manager (may be not Enthrone)

MM

CS1

Enthrone compliant manager

End to end QoS-enabled path

for DI delivery


25/138

8. Integrated management

25

Architectural planes ( ITU-T specs)

Data Plane, Control Plane and Mng. Planes functions all are

present in ENTHRONE


26/138

8. Enthrone Integrated management

26

Architectural planes

Generic view

Service Plane

Control Plane

Management Plane

Data Plane

CC ANP CP/CSSPNP

IntegratedManager

(Policy BasedMana ement


27/138


27

IM vertical extensions- in different AS context

IMi IMj IMk

ASi

ASj

ASk

Integratedmanager (IM)- Network independent

- Inter-domain

AS Intradomain

Manager

Networkspecific

technologies

AS withown PBMmanager

AS withoutown PBMmanager

Network

specific I/Fs

IM Intradomainextension

Networkindependent

I/F


28/138

8. Enthrone Integrated management Functional Architecture

28

Data Plane

Traffic Condition ing , PHB EnforcementIP Forwarding , QoS probes, DIA

Resource Mng &TE(1 ) (2)Network Policies and Planning

Resource Control &TE (2)

Local Admission controlNetwork &SLS Monitoring

EQoS RM

IMSInter -domain:Network Control Plane

IMSInter-domain : Network M anagement Plane

EQoS PATH

SLS invocation handling (AC), pSLS invocationResource Control &TE (dynamic) (2)QoS Routing

Network &SLS Monitoring

EQoS RA (3)

Network

independent

Intra -domain : NetworkManagement PlaneNetworkdependent

Intra -domain : Network Control Plane

Data Flow

Service Policies and Planning

SLA/SLS negotiation Mn g.SLA/SLS Monitoring Mng.

IMSSLSManagement :Service Plane

Traffic Forecast (1 )Resource Mng &TE (1 ) (2)

EQoS SLS


29/138


The

C

ontent Manager (C

M) keeps information related to the content,and supports operations related to any subscriptions for the use of

content, the management of and interaction with content.

The Terminal Device Manager (TDM) deals with service

subscription/negotiation and monitoring.

The IMS Dispatcher has components:

SM located at the SP deals with the customer subscriptions (cSLAs),

contracts with NPs (pSLSs), the services and the access to the chosen service.

This is limited to the services owned by the SP

The SM at the NPs deals with pSLSs inter-domain

29


30/138

8. Enthrone Integrated management (cont)

The

N

etwork Manager (N

M) deals with inter-domain issues: QoS

discovery, QoS-based route selection and the different types of QoS

services that can be offered. TheNM has some knowledge of the

resources and control layers, with the inter-domain vision for QoS service

set-up in advance.

The Intra-domain Resource Manager (RM) does not belong to IMS, but

is owned by the AS. It controls and manages the resources inside the

domain to support QoS, and is technology-dependent.

30


31/138


Main signalling phases for service management

31

Multi-domainheterogeneous

network

(1)

(2)

(3)

CS1Data pipe

(4)

SP1 CP1

CC1


32/138


Main signalling phases for service management

32

SP2

CP1

Content Provider

(1) for CP1 Content X

Content X

(CP1)

Content Y

(CP1)

Service

Discovery

Repository(SDR)

SP1 Populate SDR

(6)

CC1

(8)

cSLA1Request

(9)

cSLA1Response

(2)

pSLS1

Bi-directional QoS-enabled pipehttp

Content ID = yyy

Content Key = xxx

cSLS1(11)

Pipe is established in advance by SP1 to provide specific

content delivery service/s that satisfy a number of cSLSs

(5)

cSLS1(10)

cSLS1 Invocation(12)

DI Search(7)

Service Type 1:

VoD Gold - SP1, Cost

VoD Silver - SP1, Cost



Service Type 2:

-----

WEB SERVER

SPsADVERTISEMENT PORTAL

Access

Network

AS1

IMS

RM

NM

SLSMgt.

NP1

AS2

IMS

RM

NM

SLSMgt.

NP2

AS3

IMS

RM

NM

SLSMgt.

NP3

Content Dispatch(13)

Service Scenario

(Explicit Invocation)

(4)

pSLS3

(3)

pSLS2

A B

DC E

F

Content

Manager

Network

Manager

Terminal

Manager

Front

End

IMS

Dispatcher

Service

Manager

SLS

Mgt.

SLA

Mgt.

Service

Provider SP1

pSLAA

pSLAB

NM: Inter-domain Network Manager

RM: Intra-domain Resource Manager


33/138

9. Enthrone Service managementInitially, before accepting any customer cSLA, the SP, through its IMS-SM, establish

pSLAs with some CPs based on its initial knowledge delivered by a service discovery

function

Then a set ofQoS-enabled paths (aggregated pipes) between NPs are established, viapSLS, agreed between SP and access NP, and between pairs ofNPs (cascaded model) from the ingress points of CSs up the egress points ( routers) wher potentialcustomers exist

The inter-domain paths - obtained by special path finding protocols (e.g. BGP orqBGP, etc.)

Then the associated pipes (means for distributing contents from CS of CPs to severaldestinations) - are installed (put in place) i.e invoked

Appropriate network configurations are performed

The appropriate NM, through the domains SM, sends an ack back to the IMSSM of

the SP

Now the SP can accept customer requests (cSLAs)

33


34/138


Theportal - I/F through which user select a service with a given or chosen QoS

Through a portal I/Fs, users can negotiate access to a wide choice of services.

(details, costs of the services - retrieved from a Service Discovery Repository

(SDR)

The SPs, through associations with CPs, offer a number of services through theSDR

Each SP is responsible for the creation of new services and their presentation in

the SDR

The SP maps the pSLS- > cSLAs for offering to customers and also maps the cSLA

-> cSLS(s) to be instantiated in co-operation with the NMs ofNPs

The cSLA is seen as an interface between the customer and the SP.

34


35/138


I/FSP/NP is the c/pSLS, ensuring the independence from both the high level view

of a service and the specific network architecture employed. SLS enforcement is

achieved by means of a PBM - approach

IMS Dispatcher receives a cSLA (e.g.., VoD/gold) from the front-end and performs

initial checks

IMS Disp can also do some adaptation for a cSLA req. ( e.g. considering the

initial CC selection, the IMS can provide the appropriate and best QoS level

by executing an adaptation procedure (based on the terminal capability, user

profile: financial restriction, network path capacity, etc.)

the adapted cSLA request is passed to the IMS Disp SM

SM translates cSLAs into cSLSs. After retrieving the service availability from an

SLS repository, the SM performs admission control to decide whether to accept

or reject the request.

35


36/138


T0 phase: Service and QoS framework set-up: first phase of the

ENTHRONE life cycle model; the service and QoS framework of the

system (SP and the ASs of each participatingNP) is initially set-up

The necessary pSLSs are established between all NPs along the delivery

chain from the DI Content of CP1 to the requesting CC1. (Steps (1) to (6)).

(1) SP/CP: pSLA Negotiation

(2-4) SP/NP & NP/NP: pSLS Negotiations

(5) Uni-directional QoS-enabledPipe (can also bi-

directional if required)

(6) SP/SDR:ServiceAdvertisement

36


37/138


Service Requestphase:

ACCrequests a service from a SP (for delivery of a DI), resulting in a

cSLA agreement. The agreement of a cSLA assumes that a particular

path has been chosen for the provision of the specific DI.

Some form of provisioning/reservation at the network level is already

carried out, through pSLSs, in order to offer some guarantee that the

DI can be supplied at the agreed QoS level. (Steps (7) to (9)).

(7) CC/SPs Web Server: DI Search

(8) CC/SP: cSLA Request

(9) SP1/CC1: cSLA Response

37


38/138


Service Invocationphase:

This refers to the time directly preceding the actual DI content

transfer, during which any admission control and resource

commitments required on the access network for the content transfer

are made.

The invocation phase is not mandatory to be separate; it could

happen implicitly at the subscription phase, depending on the service

schedule. (Steps (10) to (12))

(10) SP/NP:Access Network Resource Provisioning

(11) SP/NP: Traffic Conditioning

(12) CC/CP server:Content Request

Data Transferphase: The DI is transferred between the CS on the

network providing it and the CC. (Step (13))

13) CP server-to-CC1: Content Dispatch

38


39/138


Service Completion Phase:

Once the DI request has been completed (and the service schedule

is complete), the current data transfer is terminated

The relevant cSLA in the repository is deleted or updated if the CC

requests this.

Note that the cSLA can remain valid to allow future invocations.

39


40/138


QoS C

apability Discovery Domains advertise their QoS capabilities with their associated scope (source

domain to target domain) through suitable methods.

The discovery operation enables a provider domain to locate and find out the QoS-

classes offered by other provider domains.

This is to discover the QoS capabilities, capacities, destination prefixes and costs

offered by service peer providers. All providers will implement a small number of well-known QoS classes.

Inter-domain QoS services are created by constructing paths across those domains

that support a particular QoS class.

The BGP information is used to find destination prefixes. QoS capabilities, capacities

and costs can be determined during pSLS negotiations.

All the involved providers will advertise their QoS class capability andreachability through a protocol.

Inter-domain QoS services are then created by constructing paths (e.g. by BGP

path) across those domains that support a particular QoS class. This is path

advertisement through a protocol.

40


41/138

41

SP2

CP1

Content Provider

pSLA2pSLA1

(1) for CP1 Content X

Content X

(CP1)

Content Y

(CP1)

Service

Discovery

Repository

(SDR)

SP1 Populate SDR

(6)

CC1

(8)

cSLA1Request

(9)

cSLA1Response

(2)

pSLS1

Bi-directional QoS-enabled pipehttp

cSLS1(11)

Pipe is established in advance by SP1 to provide specificcontent delivery service/s that satisfy a number of cSLSs

(5)

cSLS1(10)

DI Search (7)

Service Type 1:





Service Type 2:-----

WEB SERVERSPsADVERTISEMENT PORTAL

AccessNetwork

AS1

IMS

RM

NM

SLSMgt.

NP1

AS2

IMS

RM

NM

SLSMgt.

NP2

AS3

IMS

RM

NM

SLSMgt.

NP3

cSLS for CP1 Content X (12)

Request to send content to CC1according to service schedule (13)

Content Dispatch(14)

Service Scenario

(Implicit Invocation)

(4)

pSLS3

(3)

pSLS2

A B

DC E

F

Content

Manager

Network

Manager

Terminal

Manager

Front

End

IMS

Dispatcher

Service

Manager

SLS

Mgt.

SLA

Mgt.

Service

Provider SP1


42/138

42

Content

Provider

AdaptationDecision

Engine

pSLS

Invocation

pSLSRequest

SLARequest

IMS-Service Manager at Service Provider

Service

Forecast

ServiceProvisioning

Service Planning

SLA RequestHandler

SLA to SLSTranslation

cSLSSubscription

AC

SLA RequestHandling

cSLS

pSLS-EQoS

pSLS-EQoS response

Install new pSLSs

Policy

Install

cSLS

Response

related to

cSLA

cSLA

Initial

PASS

cSLA

responseRejected

cSLAscSLA

offering

cSLA (EQoS-cSLA)

cSLA response (proposed, agreed, rejected)

DI Content

Information

Service Management (SLA & SLS Mgt.) @

Service Provider

AC: Admission Control

Service

Discovery

Repository

(SDR)

Service

offering

pSLS

request

pSLS

response

Content Consumer

Front EndClient

TDM

QoSCapability

Discoveryof NPs

cSLSs

Network Provider

IMS Service Manager

pSLS

Request

Handling

c/pSLS

Invocation

Handlers

pSLS

SLA/SLS

Repository

cSLA1/cSLS1

cSLA2/cSLS2

cSLA3/cSLS3

cSLA4/cSLS

4

...

pSLS1

pSLS2

pSLS3

IMS Content

Manager

FrontEnd

Server

cSLA

request

cSLA

response


43/138

43

ResourceManager

pSLSSubscription

AC

pSLS RequestHandler Traffic

Forecast

pSLSRequest

pSLSpSLS

response

(accept,wait, reject)

pSLS request

Install new

pSLS

pSLS response

New pSLS to set-up

TMSet of accepted

c/pSLSs

Set of accepted

& rejected pSLSs

pSLS

Request

Handling

pSLS Invocation

HandlerpSLS

Policy

IMS Service Management (SLS Mgt.) @

NetworkProvider

pSLS-EQoS

request

pSLS-EQoS

response

NPs Intra-domain

Resource Manger(RM)

Inter-domainNetwork Manger

(IMS-NM)

Resource

Provisioning

&Traffic

EngineeringService

Provisioning

(pSLS)

Service

Forecast

(pSLS)

Service Planning

pSLSSplitter

pSLS-EQoS

request

pSLS-EQoS

response

pSLS response

Route (e.g., BGP)

& QoS info

QoS

Capability

Discovery

of NPs

Domains

Resource

Availability,

etc.

cSLS InvocationHandler @ AN

Customer cSLS

Invocation

cSLS

pSLSInvocation

pSLS1

pSLS2

pSLS3

cSLS1

cSLS2

Non-

Enthrone

purposes

SLSRepository

IMS Service Manager

pSLS

Request

Handling

pSLS

Invocation

Handlers

Downstream NP

SP / Upstream NP

IMS Service Manager

pSLS

Request

pSLS

Invocation

cSLA

Request

Handling

@ SP

cSLS


44/138


45/138

4545

ContentProvider

ContentServer

EIMS@Service

Provider

NP1

NSM&RM@NP

NSM&RM Network Service and Resource Manager

NP2

NSM&RM@NP

AN

RM@AN

ContentConsumers

SP-CP dialogue

pSLSreq-subscribe

pSLSrsp-subscribe AC

AC

pSLS link provisioned

It will be installed at invocation

time after similar set of actions

11. Service scenario exampleConnectivity Service Scenario Example pSLSestablishment

pSLS-

link

installed


46/138

4646

ContentProvider

ContentServer

NSM@Service

Provider

NP1

NSM&RM@NP

NSM&RM Network Service and Resource Manager

NP2

NSM&RM@NP

AN

RM@AN

ContentConsumers

AC

cSLS reqcSLSrsp

DI flow

11. Service scenario exampleConnectivity Service Scenario Example cSLSestablishment


47/138

11. Service scenario example Basic proposed model

47

---- Control Plane for out of band signalling

___ Data Plane

___ Internal SDL channels of a business entity

(1)

(2) (3)

(6)

(7)

(8-9)(10)

(10)

(11)

(12)

(13)

(13)

CPM

CS

SM

NM

RM

NET

NP3

SM

NM

RM

NET

NP2

SM

NM

RM

NET

NP1

CM

IMSdisp

NM

SMFEclnt

CC

NETi/f

TDM

FEsrv

SP

TM

WEBsrv

SDR

(4)

(14)

(5) (5) (5)


48/138

11. Service scenario example Basic target MSC (1/3)

48

o

NP3.IMS.SMNP1.IMS.SM

(1 ) D24i

(2-4 ) D24i

pSLS invocation

(5) D24i

Install_req( )

Config_rsp( )

Inform CP about invocation

(6) D24i

CP1.Cnt_mng

New_serv( )pSLS_req( )

SP/CP_pSLA_req( )

SP1.Cnt_mng

SP/CP_pSLA_rsp( )

SP1.IMS.SM.Srv_plan NP2.IMS.SM

pSLS_req( )pSLS_req( )

pSLS_rsp( )

pSLS_rsp( )pSLS_rsp( )

CS1.Mng

Cnfig_req( )

SP1.Srv_Disc_repWeb_srv

New_srv_req( )Adv_new_srv_req( )

Adv_new_srv_rsp( )New_srv_rsp( )

pSLS_inv( )pSLS_inv( ) pSLS_inv( )

pSLS_inv_rsp( )

pSLS_inv_rsp( )pSLS_inv_rsp( )

Install_rsp( )

Negotiation


49/138


49

(11)Vertical signaling

to NM, RM

CP1.Cnt_mng

CS1.Mng

New_cSLA( )

New_CSLA-accept_req( )

New_cSLA-accept_rsp ( )

NP1.IMS.SM

(7) D24i

(8-9) D24i

(10) D24i

(12) D24i

CC1.TD_mng

DI_search_req( )

SP1.IMS.SM.ADE&SLA_req_H

SP1.IMS.SM.

Srv_plan

SP1.FE_srv

New_cSLA-established( )

Web_srv

DI_search_res( )

DI_select_req( )

DI_select_redirect( )

cSLA_req( )cSLA_req( )

cSLA_rsp( )cSLA_rsp( )

NP2.IMS.SM

NP3.IMS.SM

RESV_req( )

RESV_rsp( )

RESV_req( )

RESV_rsp( )


50/138


50

CS1.MngNP1.IMS.M

Content_req( )

Content_rsp( )

(13)D24i DIdelivery()

Invoke_req( )

Invoke_end_req( )

Invoke_end_rsp( )

Content_end_req( )

Content_end_rsp(

NP3.IMS.SM

NP2.IMS.

cSLAt_end_req( )

cSLAt_end_rsp( )

CC1.TD_mng SP1.TM SP1.SM.Srv_plan

SP1.SLA_rep

cSLA_delete_req( ) cSLA_delete_req( )

cSLA_delete_rsp( )

cSLA_delete_rsp( )

Servicecompletionphase(D24i)

(12)D24iInvoke_rsp( )


51/138

51

Powerful approach for network management by defining high level objectives of

network and system management based on a set of policies that can be enforced in thenetwork

PBMpolicies : set of pre-defined rules (conditions actions) that determine allocationand control of network resources

these conditions and actions can be established by the network administration withparameters that determine when the policies are to be implemented in the network

Policies specifies the regulation of access to network resources and services based on administrative

criteria.

control which users, applications, or hosts should have access to which resources and servicesand under what conditions

Advantage ofPBM: instead of configuring individual network devices, ISPs and corporateadministrators regulate the network through policy infrastructure, which provide supports forallowing administrative intentions to be translated into differential packet treatment of trafficflows

Slide 51

ANNEX : Policy based Management


52/138

52

Policies - usually defined based on the high-level business objectives ofthe network operator or service provider

- service contracts: SLA/SLS agreed between the und user customers and theService Provider or between the providers themselves

Typical Providers: Network Provider (NP), Service Provider (SP), Content

Provider (CP)

Main PBM goals:

to support the QoS management

But also can cover a larger area of network management aspects, like securityand also interact with mobility management.

PBM - high-abstraction view of a network to its operator helping theoperator in the deployment of new IP QoS services

Slide 52



53/138

53

PBM logical components

Policy Management Tool PolicyStoring Service

PolicyConsumers (or Policy Decision Points -PDPs)

Policy EnforcementPoints (PEP)

The PDP is represented by the Bandwidth Broker(BB) concept

- policy management tool - create an environment where policies are defined in ahigh-level declarative language; after validation and static conflict detection tests,they are translated into object-oriented representation (information objects) andstored in the repositories

- a unique logical repository can be seen as a logically centralized component but

it may be physically distributed using the technology offered by the LightweightDirectoryAccess Protocol (LDAP) directory

- after the policies are stored, activation information may be passed to theresponsible PDP in order to retrieve and enforce them

Slide 53



54/138

54

The functional groupings within a high level architecture can be mapped topolicy

consumers

Slide 54


Policy ManagentTool

Functionalblock (PDP)

Policy StoringService

Generic PolicyConsumer



Router (PEP) Router (PEP)

End of Annex


55/138

12. Policy Based Management

PBM functional entities- Enthrone approach

ePEP

Managed

"Edge Device"

cPEP

Managed

"Core Device"

ePEP

Managed

"Edge Device"

PDP

IMS dispatcher / IMSNet Manager

IMS NetMgr

IMS PolicyEditing T ool

PDP

IMS NetMgr

IMS Dispatcher / IMSNet Manager

IMS

Policy Store

Domain

Policy

Editing ToolDomain

Policy Store

Policy ConfigurationData

Policy ConfigurationData

55


56/138

12. Policy Based Mangement

PBM functional entities- Enthrone approach

56

ePEP

Admission

Control

Agent

Traffic Policy

Agent

Node

Monitoring

Agent

MIBPIB

cPEP

Traffic PolicyAgent

PIB

Inter PDP

Intra PDP

Admission

Control

Manager

TrafficPolicy

Manager

Intra-domain

NetworkMonitoring

Manager

PDP (Policy Decision Point)

IMS Network Manager

Intra DomainManagement Plane

Inter DomainManagement Plane

Service Plane

SLA/SLS Negotiation Manager

Inter domain

Routing

Control Plane

Management Plane

TVM

Processor

TVMProcessor

core Policy Enforcement Pointedge Policy Enforcement Point

inter domain NetworkMonitoring Manager

EQoS SLS

Service Level Monitoring Manager EQoS RM

Route and ResourceAssignment

Manager

EQOS RA

PQM

Proprietaryor SNMP

or XML


57/138

THANK YOU

57


58/138

ENTHRONE II service management concepts for

end to end QoS assurance in multi-domain

environment

(Extension ofENTHRONE I )

End-to-End QoS through Integrated Management ofContent, Networks and

Terminals (www.enthrone.org)

58


59/138

CONTENTS1. ENTHRONEpartners

2. ENTHRONE Business Actors

3. Objectives

4. Architecture5. NetworkService Management

6. ENTHRONE Intl Pilot

7. Conclusions

59

2 ENTHRONE II B i A t


60/138

2. ENTHRONE II Business Actors

60

ContentProvider

ContentServer

ServiceProvider

NP1

SM&RM

SM&RM -Service and Resource Manger

NP2

SM&RM

NP3

SM&RM

ContentConsumers


61/138

2. ENTHRONE II Business Actors

61

Business Actors:

CC- Content consumer (Company, End users)

Customer ( org)

End user

CP- Content Provider

CPM content provider manager

CS1, CS2, - Content Servers

SP- Service Provider (higher layer services)

NP- Network Provider (connectivity services)

ANP Access Network Providers


62/138

3. ENTHRONE II Objectives

62

To develop an MPEG-21 based QoS managementarchitecture and solutions,for

transport (QoS enabled) over multi-domain

heterogeneous network infrastructures including ANs

( new)

cross-layer adaptation New function

of protected multimedia content

to diverse terminals (fixed or mobile)

ContentServer

NP1

ENTHRONE

NP2AN

ContentConsumers


63/138


63

Offering High level services:

Video on Demand (VoD), Streaming, E-learning,

Multimedia distribution, IPTV (basically uni-directional)

To demonstrate the solution in a large-scale intl pilot, in

preparation for bringing it to the market:

large scale E2E pilot to demonstrate the capability

to manage,in an integrated way

the whole chain of protected content handling

transport and

delivery to

user term

inal

sacro

ssheterogeneo

usnet

work

s,while offering QoS-enabled services


64/138


64


65/138

4. ENTHRONE II Architecture

65

Business

Actors

End to end Quality of Services

Content

ProviderCore

Network

Providers

Service

Provider omerrCustomer

Managementand control

pSLS based IP multi-domainQoS enabled Data pipe

UniversalMultimedia

Access

Metadata

Multimediacontent

AccessNetworkProvider

AccessNetwork

Provider

AccessSpecific Pipe Access

Specific Pipes


66/138


66

Appl.andHighLevelServices

Content

Preparation

ContentHandling &Adaptation

Content

AdaptationContent

consumption

Media control middleware

Service Management (Planning, Provisioning,Offering and Monitoring)

Service and Session control

TransportServices

Inter-domain Network Resources

Management and Control

Access and Core (*)

Managementand

Contro

lPlanes

DataPlane

ApplicationsApplications

EIMS scope

Intra-domain Network ResourcesManagement and Control

Access and Core (*)

Media FlowControl FlowControl Flow Media Flow

ControlFlow


67/138


67

Adapters

Delivery

layer

Metadata Management Model

Metadata Management

and Search (MATool)Enhanced FeaturesQuality ofService

and Adaptation

ENTHRONE Integrated Management Supervision

EIMS Supervision

layer

Interfaces

BusinessActors

Business

level

(simplified)

- Multicast management

- Content caching and

CDN management

Generic model for- Metadata management

- Metadata storage

MAtool implementation using

MPEG-7/-21, TV-anytime,...

-Adaptation management

And extended functionalities:

- End to end QoS management

- Service management (SM)

- Terminal Device Management (TDM)

New entity.

More open business models


68/138


68

Metadata Manager

Inter domain Resource Manager

Inter-domainTransportServicesManagers

Service Manager

E2E QoSManager

AdaptationManager

FE

Manager

TDManager

Appl. & High LevelServicesManagers

Interfaces

ENTHRONE Adapters

Basic Services Manager

CustomerService Manager

Network Service Manager

ContentService Manager

Multicast

E-castService

Manager

Transport

Manager

CCDNCCDNService

Manager

TransportManager

Search Manager

Belong to the Mangement andpartially to Control Planes


69/138

5. NetworkService management

69

Objectives To provide to upper layersQoS enabled connectivity

services with controlled level of guarantees

over multi-domains IP based

and various access networks ( LANs, WLANs, WMANs)

While preserving each domain resource managementindependency

To accommodate variousbusiness actors: SP, NP,ANP,

CM/CS

Scalable solution:

aggregated level processing ofinter-domain resources atvirtual level (abstraction of actual network topologies)

Avoid per/flow-call signalling in the core region


70/138


70

Solution

Cascaded mode domain peering (SP does not need inter-domain

routing information)

Provider and Customer Service LevelAgreements/Specification

( pSLA/SLS, cSLA/SLS)

pSLS between providers establish pSLS-links

- in advance to real traffic flow transport- based on forecasted

data

From CS regions to CC regions

Two phase approach

pSLS subscription (quasistatic)- logical reservation

pSLS invocation (dynamic) : actual Installation in the network via

Intra-domain Resource Managers

cSLS between CCs and SP in order to getslices of pSLS links

for their Digital Items flows


71/138


71

Solution (contd)

New ENTHRONE II features (partial list)

Cache and Content Distribution network supported by

ENTHRONE architecture

Multicast transport

at overlay level inter and intra-domain

but IP multicast level (PIM-SM/SSM) possible inside each

core IP domains

PQoS- to NQoS bi-directional mapping

Cross layer optimization

Individual flow adaptation (scalable TVMs)


72/138


72

AchievementsEnthrone provides E2E QoS capable offering a number of classes ofserviceswith different levels of guarantees

Accommodates various non-transport business actors (CP/CS, SP,etc.),while interacting only minimally with them

Supports multiple domain,unicast and or multicast transport

Optimized transportation of multimedia-content (VoD,streaming,IPTV, etc.)

Utilises an Intl transport system, multiple-domain spanned, capableof offering E2E QoS,but managed at virtual overlay level,withoutintervening in each domain resource management


73/138


73

AchievementsEnthrone provides E2E QoS capable offering a number of classes ofserviceswith different levels of guarantees

Supports different network level QoS-enabledtechnologies/mechanismsin the core IP domains (DiffServ, MPLS)while offering additionally E2E controlled capabilities

Allows different types of access networks (LANs, WLANs, WMANs)

ProvidesAN Resource Manager forsome access technologiesand mechanisms for cooperative actionsbetween ENTHRONEand some other access technologiesin order to exploit the lastmile QoS offering true E2E QoS

5 N t k S i M t


74/138

5. NetworkService Management

74

Advantages: Network Operator point of view (contd)

Enthrone provides E2E QoS capable offering a number of classes ofservices

with different levels of guarantees

Accommodates various non-transport business actors (CP/CS, SP, etc.),whileinteracting only minimally with them

Supports multiple domain,unicast and or multicast transport

Optimized transportation of multimedia-content (VoD,streaming, IPTV, etc.)

Utilises an Intl transport system, multiple-domain spanned, capable of offeringE2E QoS,but managed at virtual overlay level,without intervening in each domainresource management

Supports different network level QoS-enabled technologies/mechanismsin the

core IP domains (DiffServ, MPLS) while offering additionally E2E controlled

capabilities

Allows different types of access networks (LANs, WLANs, WMANs)

ProvidesAN Resource Manager forsome access technologies andmechanisms for cooperative actionsbetween ENTHRONE and some

other access technologiesin order to exploit the last mile QoS offering

true E2E QoS

5 Network Service Management


75/138

5. NetworkService Management

75


Enthrone creates traffic-engineered connectivity paths that meet userbandwidth

requests,based on SLSsCreates a differentiated services connectivity network,where

qualitative/quantified performance guarantees are provided.

Providesscalable solution for resource management by creating a traffic-

engineered environment where traffic is loaded evenly across the network/s

Aggregated level allocation ofinter-domain resources at virtual level

(abstraction of actual network topologies)

Reduces the amount of call set-up and control signalling

Avoid per/flow-call signalling in the core region

Enthrone allows efficient exploitation (via controllable policies) of transport

resources (bandwidth) versus a controllable degree ofusersatisfaction from QoS

aspects

The control policies presentshigh degrees of customisation to business

and operations regarding service provisioning. Providers may control theexpense, through appropriate policy settings reflecting their own 'style' in

service provisioning while meeting the user requirements.

5. NetworkService


76/138

Management

76


Provides efficient Bandwidthutilization

The traffic load is distributed evenly across the intra-domain network by

setting up TE paths compare to solutionswhich load one part of the

network heavily while leaving other parts lightly loaded.

The multiplexing of traffic on aggregated pipes combined with TE

techniques ( including Network Dimensioning algorithm based on

forecasted demand) allow - if ENTHRONE applied in comparison withconventional resource management:

bandwidthsavingswhile the same amount of overall load

or equivalent, may admit more unguaranteed traffic load while using

the same network capacity

ProvidesAdmission Control based approachOffers guarantees of QoS improving the network performance in terms

of QoS traffic throughput (goodput).


77/138



78/138

78

QoS provisioning- bi directional mapping

5. Network Service Management

At the service layer

Expected PQoSis defined as the perceived quality that a customer or end-user

expects from a contracted service described in a cSLA. This may be determined

by the customers previous experience of the similarservices orby service

providers offering. The Expected PQoSis dependent on the user QoS

preferences and the capabilities and constraints of the terminal that he/she utilizes

At the application layer

ApQoS is defined as application quality to express these needs and constraintsin technical terms

ApQoS is characterised by encoding and transmission parameterssuch as

frame rate, resolution, coding format, latency, latency variation, loss ratio, etc.

At service set-up time, the expected application quality that the user envisages

(i.e.,UserExpected ApQoS) is obtained from the usersExpected PQoSviaAQoS(Adaptation QoS) tool.

AQoS is the means that provides the required metadata support for context-aware quality based adaptation/mapping expressing the relation between

resources or constraints, adaptation operation, and quality.



79/138

79



TheApQoS bound is formed by the Content Generation/Adaptation entity specifying

the boundaries that application can operate based on the application QoS profiles

determined by application encoding and transmission requirement and distortion that

application can tolerate.

Based on theApQoS bound and user expectation (UserExpected ApQoS), the QoS

parameters that form theAdoptedApQoS providing the lowest distortion and satisfy

th

e range of applicat

ion q

ual

ity req

uirement

will

be c

ho

sen

TheAdopted ApQoSis formed to classify the application in terms ofits quality

requirements. If there is no application class available (represented by Link 1) to

support thisuser request, the user QoS preference must be changed andApQoS

bound may need to be adjusted.

If the user request can be satisfied, the transmission requirements encoded in theAdopted ApQoSmust then be mapped into network-level parameters to specify the

networking needs of the application. This operation resultsin the applications required

NQoS (i.e.,Requested NQoS)



80/138

80



NQoS : quality targeted for (or experienced by) a network connectivity service and

expressed by one or more performance parameters (i.e., throughput, delay, loss,

delay variation) that are quantified.A connectivity service is a 'get-through'/ 'traverse'

service for reaching particular destination(s) from specific source(s) in the IP address

space.

An NQoS-classis a set of packet transfer performance parameters (attributes)

ass

ociated

with

spec

ific performance target

s(val

ue

s).T

he concept of NQoS cla

sscanbe compared to the notion of Per Domain Behaviours (PDBs),specified in the IETFs

DiffServ framework.

NQoS-classes are distinguished into different types according to how performance

target values are assumed.



81/138

81



NQoS-classes are building blocks for offering and provisioning QoS-based

connectivity servicesbut not the services themselves. Conversely, QoS-based

connectivity services are mapped to NQoS-classes

From the perspectives ofservice offering, NQoS-classes express the transfer quality

aspects of the QoS-based connectivity services

From the perspectives ofservice provisioning, NQoS-classessegregate the networkQoS-space into a number of distinct classes, aggregating user QoS traffic accordingly.



82/138

82



NP managesits resources; from this point of view one distinguishesseveral NQoS-

classes:

Engineered NQoS: the quality targeted for connectivity services that an NP

engineersits network to offer them to its customers. Its values are the results of

network dimensioning by taking into account the characteristics of the physical

network configuration, topology, customers/providers QoS needs and trafficdemand, and forecast. NPs assign NQoS values to a number of network level

QoS classes (NQoS-class)

Offered NQoS: quality actually set by the provider, assigned to NQoS-classes

and deemed appropriate for creating competitive network connectivity serviceofferings to its customers or providers. The Offered NQoSvaluesshould be as

close as to the corresponding Engineered NQoSvalues. These values maychange as the corresponding policies forservice offering change.



83/138

83



The Requested NQoSis mapped to Offered NQoS,i.e., mapping of attributes-values

ofRequetsed NQoSto an NQoS class attributes-values.

Thisidentifies the service class that assigned to the application for allowing

transportation of the stream across the networkswith the desired quality.

The performance values ofselected NQoS classshould be as good as orbetter than

the corresponding Requetsed NQoSvalues.

The values ofselected NQoS class are exported to the cSLS.

After the selection of NQoS-class, the content can be generated according to the

agreed QoS parameters. The Content Generation/Adaptation entity isinformed to

generate the content bit-stream.

If there is no NQoS-class available to satisfy all requirements and constraints

(represented by Link 2), it implies that the current network capabilities cannot meet

the application quality requirement.



84/138

84



Therefore,user QoS preference must be changed andApQoS bound may need to beadjusted.

The network informs the decision-making sub-systems for changing the user QoS

preferences and requesting Content Generation/Adaptation entity to adjust the QoS

bound.

This feedback link may make the system not scalable, asit may require for every

service request. Thisshould not happen as the Service Management sub-system atthe EIMS performs an admission control prior to go through the mapping process. The

admission control entity makessure the network level service classis available to

support the requested service.

The decision-making sub-systemsinstruct (represented by Link 3) Content

Generation/Adaptation entity to:

Generate/adapt the content based on the agreed QoS parameters and any application layer

mapping policy.

Change the application quality requirements and adjust theApQoS bound based on the

network (access and core) constraints and application requirementsif necessary.



85/138

85



The Measured NQoS isused forservice and network monitoring purposes.is defined as the network quality actually experienced by QoS-based connectivity

services offered by one/more NPs and deduced by actual measurement during

network operation.

The Measured NQoS values change as network traffic conditions change but

they should not on average- over a timescale, violate the selected QoS classvalues (SLS).

The Delivered PQoSis the quality that a customer or end-user actually perceiveswhen consumes the service at his/her terminal.

The Delivered PQoSrelated parameters could be acquired during service

delivery by subjective/objective measurements.

The result isused forservice monitoring and service fulfilment purposes

including QoS adaptation.

The Delivered PQoSmonitoring is normally performed at level of an individualapplication stream.Forscalability reasons, the NQoS is measured (i.e.,Measured

NQoS) for a specific QoS class and at aggregated level



86/138

86



It might be necessary to find out about the PQoS experienced by a number ofapplication streams collectively delivered at an NQoS-class level.

By using thisMeasured NQoS,it is possible to deduce an approximation of PQoS

(i.e.,Derived PQoS) delivered to a number of application streams.

Different techniques may be used to obtain values ofDerived PQoSparameters from

Measured NQoSparameters observed across network boundaries or end-to-end.

The result of this mapping can be used forservice assurance purposes and as

feedback to SPs decision-making process to compute a new content adaptation if

necessary.

Upon detection ofservice degradation during its delivery, adjustment of QoS

parameters and adaptation of content will be needed. This may resultsin the changeof NQoS-class.



87/138

87



QoS atvarious levels Definition/Characteristic/Parameter/Measurement

User QoS Preferences Expressed by high-level terms e.g., Gold, silver, bronze (Olympic Services)

Terminal chars and

constraints

Characterised by Processing power, memory, jitter buffer size, codec, video playback

frame rate, etc.

Expected PQoS Defined as the perceived quality that a customer or end-user expects from a

contracted service described in cSLA.

Delivered PQoS The quality that a customer or end-user actually perceives when consumes the service

at his/her terminal measured by subjective/objective methods. It is expressed asPerfect, Excellent, Very Good, Good, Moderately Good, Fair, Somewhat Poor, Poor,

Very Poor, Bad, or Useless. PQoS evaluated using: SNR, MOS, Structural Similarity

Index (SSIM) techniques.

Derived PQoS An approximation of PQoS delivered to a number of application streams deduced by

usingMeasuredNQoS.

ApQoS Defined as application quality to express the application needs and constraints in

technical terms. ApQoS is characterised by encoding and transmission parameters

such as frame rate, resolution, coding format, latency, jitter, loss ratio/BER, aspect

ratio, etc.



88/138

88



User Expected ApQoS Defined as the expected application quality the user envisages and obtained from the

users ExpectedPQoSvia AQoS tool.

AQoS (Adaptation

QoS)

AQoS is the means that provides the required metadata support for context-aware

quality based adaptation/mapping expressing the relation between resources or

constraints, adaptation operation, and quality.

ApQoS Bound Specifies the boundaries that application can operate, based on the application QoS

profiles determined by application encoding and transmission requirement anddistortion that application can tolerate.

Adopted ApQoS Is used to classify the applications in terms of their tolerable distortion and encoding

and transmission quality requirements within ApQoS Bound.

NQoS Generally defined as the quality targeted for (or experienced by) a network

connectivity service and expressed by one or more performance parameters (i.e.,

One-way delay, round-trip delay, One-way packet loss, delay variation, offered load,throughput) that are quantified.

Requested NQoS Specifies the networking quality needs of the application.



89/138

89



Engineered NQoS Defined as the quality targeted for network connectivity services that

an NP engineers its network to offer them to its customers.

NQoS-class An NQoS-class is identified by a set of packet transfer performance

parameters (attributes) associated with specific performance targets

(values).

OfferedNQoS The quality actually set by the provider, assigned toNQoS-classes and

deemed appropriate for creating competitive network connectivity

service offerings to its customers or providers.

Measured NQoS Defined as the network quality actually experienced by QoS-based

connectivity services offered by one/more NPs and deduced by actualmeasurement during network operation.

5.Network Service Management


90/138

90

Network Service Manager at SP (NetSrvMngr@SP)

Role:

Management (by provisioning) of the virtual transportresources at aggregated level (multi-domain QoS enabledpSLS links), in unicast/ multicast mode and triggering theirinstallation/modification/deletion in the networks; executionof the cSLS individual CC requests

Interfacing with: other SP modules (mainly to CustomerService Manager) - to

deliver information on pSLS links status and to process therequests for connectivity services - in aggregated (pSLS), orindividual (cSLS) mode

NetworkService Managers at core IP domains - to trigger the

required actions related to pSLS aggregated links in unicast ormulticast mode

Access Network Resource Managers - to control the last/first milesegment (cSLS link) of the QoS enabled pipes

g



91/138

91

Network Service Manager at SP (NetSrvMngr@SP)

Achievements: specification, design implementation and validation

of:

pSLS processing: (quasi-static) subscription and dynamic invocation of

aggregated pipes; complex negotiation handshaking; alternative

routes for aggregated pSLS pipes

pSLS links support for overlay multicast tree and dynamic tree

management

pSLS support for IP multicast in the last core IP domain

pSLS links support for CD Networks

Unicast cSLS processing: cSLS dynamic subscription and invocation

cSLS support for multicast service

5. Network Service Management@


92/138

92

EIMSatSP

Network ServiceManager

FrontEnd

Client

ContentConsumer

TerminalDevice

Manager

SPFront

End

Service Provider

ContentProvider

(EIMS part)

ServiceDiscoveryRepository

Customer

ServiceManager

ServicePlanning

SLA/SLSRepository

QoScapability

Discoveryof NPs

pSLS

processing

Network Provider(EIMS part)

cSLA/SLSProcessing

Policies

pSLSpSLA

cSLA cSLA

cSLA/cSLS

cSLS

E2EQoSManager

SearchManager

Service Manager

Content

ServiceManager

MonitoringManager

MulticastManager

CDNManager

MetadataManager

NSM@SP- generic architecture

5. Network Service management


93/138

93

Network Service Manager at SP(contd) - Implementation

Implemented Modules:

Network Service PlanningpSLS processing

cSLS processing

Multicast c/pSLS processing

Repositories: pSLS, cSLS,

Allocated ResourcesRepository

WSDL Interfaces to:

Customer Service Manager@SP

General Multicast Manager @SP

Graphical interface for administration

Monitoring System

Network Service Manager @NP

Resource Manager@ANP

cSLS

processing

pSLS

processingCustSvcMngr

WSDLinterface

NetSrvMngr@NP

interface

cSLS

Repository

Graphical

interface

McastMngr

WSDL interface

Allocated Resources

Repositor

pSLS

Repository

ANMngr

WSDL in terface

SrvMon

interface

Multicastp/cSLSprocessing

ServicePlanning

NetworkService

Manager@SP

WP3 functionalitiesWP6

functionalities

Validation:Operational scenarios

High level servicesscenarios



94/138

94

Network Service Manager at SP (contd)

Scenario Example:Message Sequence showing the pSLS status query and cSLSsubscription related actions (bold line - dotted arrows); Notations: cSLS RqH

cSLS RequestHandler ; ResMngr@ANP ResourceManager at ANP

94

SP

CC

CustSrvMngSPFE

NetSrvMng @SP

1

cSLA

Access

Network

ResMng@ANP

Core Network (s)

CS/

sTVM1

(NSM&RM)@NP

Exis ting pSLSlinks - installed

2

4

ER

cSLS ReqHndl

pSLS/

cSLS

Rep

4.1

7

7.2

9

SplitcSLS(7.1)

AC(7.5)

8

4.2

CS/sTVM2

AR

ER

5

Network

Service

Provisioning

7.4

7.6 10

(3) (6)

(7.3)



95/138

95

Network Service Manager at NP (NetSrvMngr@NP)

Role: Management (by provisioning) of the intra and inter-domain virtual

transport resources at aggregated level (QoS enabled pSLS links), by

cooperating with NetSrvMngr@SP and other NetSrvMngr@NP(s);

commands for their actual installation/modification/deletion in the

networks Interfacing with

NetworkService Managers atSP - to process and solve the requests for

multi-domain pSLS-links in unicast or multicast mode

Upstream and downstream NetworkService Managers at NPs

to negotiate pSLS links and ask for

subscription/invocation/modification/deletion of these links (

ENTHRONE EQoS protocols)

to exchange routing information

9

5



96/138

96

Network Service Manager at NP (NetSrvMngr@NP)

Interfacing with

Intra-domain Network Resource Managerat IP domain

to ask it the required actions related to pSLS links installation in the

network

to receive intra-domain and inter-domain network resource

information in terms of traffic trunks

to receive the topology information in case of IP multicast in the last

core domain

9

6



97/138

97

Network Service Manager at NP (contd)

Achievements: specification, design, implementation and validation of

Interaction with Intra-domain Network Resource Manager - to receive

the Resource Availability Matrix information (intra and inter-domain)

Interaction (upstream) with NetSrvMngr@SPs for pSLS processing:

Interaction (upstream and downstream) with other NetSrvMngr@NPs

(EQoS

protocols/WS

DL

based ) for pSLS

processing: (quasi-static) pSLS subscription

negotiation, splitting, Admission Control (AC), storing,

modification, deletion

pSLS dynamic invocation

Negotiation, AC, modification, deletion

97



98/138

98

Network Service Manager at NP (contd)

Interaction with Intra-domain

N

etwork ResourceM

anager - to commandinstallation/modification/deletion of the pSLS-links

pSLS links support for overlay multicast tree and dynamic tree

management

5.Network Service management


99/138

99

Network Service Manager at NP (contd) - Implementation

TrafficForecast &Planning

pSLS

splitting

EQoS

WSDLinterface

Inter/intra

domainResource

Repository

pSLSProvisioning

pSLS

AC

InterdomainOverlaypaths

repository

Interdomain

overlaypathfinding

Policies

In

ter-domainPath

W

SDLinterface

EQoS

WSDLinterface

Intra-domain

Resource ManagerWSDL interface

Intra-domain

NetworkManagerWSDL interface

Web Management

interface

EIMS@NP

Multicast

Manager

SrvMon

interface

pSLS

Repository

Inter-doma

in

ResourceMan

ager

WSDLinterface

Implemented

Modules:Network Service

Provisioning

pSLS Splitter,

pSLSAdmission Control

Multicast Manager

Inter-domain overlay pathfinding

Traffic Forecast and

planning

Repositories:

pSLS

Intra/inter domain

resource Inter-domain

overlay path

5.Network Service management


100/138

100100

Implemented WSDL I/Fs to: Net SrvMngr@SP and NP (EQoS interface),Monitoring System, Intra-domain Network Resource Manager, Inter-domain path I/F

Validation: 1.Operational scenarios; 2. HL servicesscenariosSample example: pSLS invocation over three IP domains

Admin@SP

SrvProv@SP

SP

NetSrvMngr@NP1

Intra-NRM@NP1

NP1

Invocatio n Initiation

1.2.pSLS_i_req

11

1.1

NetSrvMngr@S P

NetSrvMngr@NP2

Intra-NRM@NP2

NP2

NetSrvMngr@NP3

Intra-NRM@NP3

NP3

2.1

2.2.pSLS_s_req

EQoS-pSLS-S/I-NP

3 4..pSLS_i_req

5, 6,78. pSLS_s_req

9.Internal NP actions

10

13.pSLS_i_rsp(acc)

pSLS_i_rsp(acc)

. pSLS_i_rsp(acc)

15 pSLS_i_rsp(acc)

16

EQoS-pSLS-S/I-NPEQoS-pSLS -S/I-NP

Last IP domain

M1

M4

M3

M2

12

1417

5.MPLS based QoS provision


101/138

101101

Mapping of pSLS-pipe to

SLS in MPLS domains

Development of cooperation between MPLS control plane and

ENTHRONE management/control plane. The approach used was to

map each pSLS on to a single MPLS LSP

In (5) appropriate

command from EIMSNSM@NP is sent to the

ingress LSR router

5. MPLS based QoS provision


102/138

102102

CLASSES DSCP EXP LSP LSP_ label

iLER-LSR-eLER

LSP

BW

EF 0x2e 0x01

LSP1 1000010001 2 MbitAF11 0x0a 0x02

AF22 0x14 0x06

LSP2 2000020001 2 MbitBE 0x00 0x00

Two LSPswere allocated : LSP1 for EF andAF11 traffic classes LSP2 forAF22 and BE traffic classes

Intra-domain NM : controls the allocation of traffic

flows to DiffServ/MPLS classes Distributes the labels for LSP

assignment Interfaceswith NSM@NP

5.ENTHRONE Multicast


103/138

103

Overall Goal:

QoS enabled multicast transport service of DI media flows over multi-domains (core plusheterogeneous access networks) while seamlessly integrated in the ENTHRONE architecture

Multicast support inter and intra-domain

Flexible overlay (at EIMS level) solution, based on existing pSLS/cSLS-linksconcepts- SLA/SLS controlled

Scaleable and efficient solution in terms of inter-domain signalling

Independent on IP multicast deployment in the core domain

But capable to use IP multicast where it exist

103103

5. ENTHRONE Multicast


104/138

104

ENTHRONE- new multicast solution : E-cast system

Built on existing ENTHRONE management infrastructure

Multicast aggregated tree:

Overlay multicast (E-cast(o)) for multi-domain

May include IP multicast (E-cast(ip)) if available, in the leaf IP coreof the domains of the overlay multicast trees

E-cast tree set of of QoS enabled unicast pSLS-links (mcast-pSLS-tree)

A mcast-pSLS-tree holds resource slices : mcast-cSLS-trees

The mcast-cSLS-tree : a set of unicast cSLS-links, for a single multicast stream - e.g.an IPTV channel

E-cast(ip), based on standardized PIM-SM/SSM

Additionally to best-effort PIM-SM/SSM, the E-cast(ip) provides QoS guarantees

by creating at IP level, a single domain tree based on pSLSs.

104104

5. ENTHRONE Multicast


105/138

105

E-cast system:

Data Plane: multicast p/cSLS based

Management and

C

ontrol Plane:E-C

ast Manager andC

ontrol (Central) EIMS Multicast Manager at SP: communicates with EIMS Customer Manager tohandle CCs requests and with EIMSNetwork Manager to subscribe and invoke mc_pSLSand mc_cSLS.

Service Manager (McastMngr SM)

communicates with EIMSSearch & Customer Service Manager tohandle multicast service requests

map requests at application level to network level Network Manager (McastMngr NM)

communicates with EIMSNetwork Service Manager to configure,administrate overlay multicast network

interacts with IP multicast in the last core domain

Network Service Manager at SP

Intermediates the pSLS support for E-cast(o)

Multicast Manager at NP

Manages and controls the E-cast(ip)

105

SM

EIMS MM

NM

Search MngrSearch Mngr

CustSrvMngrCustSrvMngr

NetSrvMngrNetSrvMngr



106/138

106106106

ASm

CS

E-cast Root

AN3

DR1

AN1

DR2

DR3

ASp CC1

CC2AN2

CC3ASi

AN1

E-cast RootNode (EN1)

ASk CC1

AN2

ASj

IP PIM-SM/SSMdomain

CC2

E-cast intermediate node

E-cast cross-layer node

Ordinary IP router

PIM-SM/SSM router

E-cast

Overlaytree

PIM-SM/SSMtree

Unicast pSLS-link

E-cast proxy node

Segment of IPIM-SM/SSM tree( based also on pSLS-links

EN2

EXN3

EN4

EN5

EN6

EN7

NSM&RM@ NP

NSM&RM@ NP

NSM&RM@ NP

NSM&RM@ NP NSM&RM

@ NP

SP

NetSrvMngr

McastMngr

2.1

2.3

2.2

1

3*

Overall E-cast topology: pSLS support and PIM/SM support



107/138

107

E-cast(o) Achievements

Components:

McastMngr@S

P, McastMngr@EN

(other no rootE-

castN

ode),S

tream Replicator(S

R)

Operations: E-cast mesh construction

E-cast tree construction

E-cast service configuration

E-cast service retrievement

Tools: User interfaces using Web application;

E-cast system in JAVA (GUI, Dijkstras algorithm);

Interfaces (& Signaling) in web service (wsdl);

Stream Replicator: modified VLC;

Basic database operation on MySQL Main Page

Administration

( SP)

List of

ENs

Mesh

configuration

Tree

configuration

List of

Trees

Deployed

Services

IPTV

services

Add Modify

Main Page

Administration

( EN)

List of trees List ofservices



108/138

108

Entities of IP

multicast

E-cast (Ip) Achievements (validated in RP testbed)

PIM-SM (XORP) - intra-domain i

Documents

Enthr1-2--srv-mng-QoS-3 nov 2010-v0.3