Service provider and content aware network provider cross layer optimisation of multimedia...

ICME 2011 Conference, WOMAN Workshop July 11 2011, Barcelona 1

SERVICE PROVIDER AND CONTENT AWARE NETWORK PROVIDER CROSS-LAYER

OPTIMISATION OF MULTIMEDIA DISTRIBUTION

Eugen Borcoci, Serban Obreja, Christian Timmerer, George Xilouris

Presentation: George Xilouris


Authors’ affiliation:

Eugen Borcoci, Serban ObrejaUniversity Politehnica of Bucharest, [email protected] Christian TimmererDepartment of Information Technology (ITEC)Alpen-Adria-Universität Klagenfurt, Austriae-mail: [email protected]

George Xilouris, NCSR Demokritos Institute of Informatics and Telecommunications, Athens, Greece, [email protected]

Acknowledgment: This work has been supported by the European Research Project FP7 “MediA Ecosystem Deployment Through Ubiquitous Content-Aware Network Environments” ALICANTE project No. 2010-2013.

mailto:[email protected]




1. Introduction

2. ALICANTE System Architecture

3. CAN Services and Resource Management

4. SP-CANP Service Level Agreements

5. Use case examples

6. Conclusions

CONTENTS


1. Introduction

• ALICANTE : New challenging concepts (Future Internet – oriented) – Content Aware Networking (CAN)– Network Aware Application (NAA)

• Novel virtual CAN layer – as a part of a full layered architecture– focused, but not limited to, on multimedia distribution with Quality

of Services (QoS) assurance• The paper focus:

– Service Provider and Content Aware Network Provider Cross-layer optimisation



• ALICANTE defines several environments containing business actors:

– User Environment (UE)• End-Users (EU)

– Service Environment (SE)• Service Providers (SP)• Content Providers (CP)

– Network Environment (NE) • CAN Providers (CANP) - new• Network Providers (NP)

– Home Box – new entity located at EU premises• Media flow processing, management, adaptation, routing, caching functions• HBs- form together a virtual layer included in SE

Environment : - grouping of functions defined around the same goal and possibly spanning, vertically, one or more several architectural (sub-) layers; it has a broader scope, than “layer”



• ALICANTE high level view

• User Environment

• Service Environment

– SP/CP layer

– HB Layer• Network

Environment– CAN layer– Network

layer

Network/Transport Layer

AN

End-Users premises

SP premisesIntraNRMIntraNRM

IntraNRM

AS3

AS2

AS1

Policy DB

Policy DB

Policy DB

Virtual CAN Layer

CAN 11

CAN 12CAN 22 CAN 31

CAN 32CAN 21

Dialogue between CAN managers

CP/SP Servers

SR

Virtual HomeBox Layer

CP/SP Servers

CANMng

Publishing content/services

Logical interconnection

SP premises

SP premises

AN

End-Users premises

AN

Physical View

User Environment

Content-aware

Network-aware

Context-aware

MANE

MANE

MANE

CANMng

CANMng

MANE

MANEMANE MANE

MANE

MANE

Service Environment

SR

IP&CAN Provider/Operator

Logical view


AS1

IntraNRM @NP

HB/ EU/ SB

AS2

IntraNRM @NP

MANE

CAN Manager

CAN Manager

Srv Mgr@SP

2

3 1

Multi-domain VCAN

NIA

HB + SP Environment

MANE MANE

Service Provider

5

CAN RM

CA Clasif Policing Labeling

Fwd. Adaptation

Queuing, Scheduling

Shaping

4

MANE

Mon. System

OL1

OL2

• Content and context aware architecture at network layer

• Two main optimisation loops

• provisioning loop (OL1) – CAN/NAA

• SP, CANP, (NP)

• adaptation loop (OL2)– Network– HB, terminals– monitoring system

• QoS, QoE probes

– ADTF



Type of ALICANTE services supported by VCANs Fully Managed Services (FM) Partially managed Services (PM) Unmanaged Services (UM) This split captures two point of views

Services: (degree) how strict the QoS requirements are CANP: shows the degree of the CAN layer freedom to perform autonomic

actions

Fully Managed Services High priority services in ALICANTE: delivered by the SP and the in some cases EU’s HB

SLAs exists agreed between SP and CANP

Services requirements: Guaranteed: (low) packet delay; bandwidth; (low) packet loss; possible secure, private connectivity

VCANs provisioned by the CANP to answer the requirements

Different levels of guarantees are possible

Services adaptation may be performed - if necessary- at HB and MANE level- but in the limits of the SLA

3. CAN Services and Network Resource Management


Type of ALICANTE services supported by VCANs Partially managed Services (PM)

The CAN layer has more freedom (to act upon flows) than in FM case Still one may have a contract SP-CANP specifying:

PM1: some minimum QoS guarantees (quantitative) – plus some extra, or PM2: only statistical/qualitative (weak) guarantees

CAN layer may apply adaptation if necessary: PM1 case: not to violate the contract (in normal network operation cases) PM2 case: any adaptation operation in the network is allowed to CAN layer

in order to do "its best”

Unmanaged Services: No contract SP – CANP CAN layer

Still may offer some QoS Is totally free to treat the traffic conforming the NP policy



Type of ALICANTE services supported by VCANs Hard Guarantees – HG

Statistical Quantitative Guarantees- SQnG

Statistical Qualititative Guarantees – SQlG

No guarantees (Best Effort) – BE

HG SQnG SQlG BE Bandwidth

assurance degree

Delay, Jitter, Loss

BQ1 BQ2 BQ3 BQ4 NA

DJL-Q1 DJL-Q2

HG

DJL-Q3

FM

DJL-Q4

PM1 SQnG DJL-Q5

PM1 SQlG

DJL-Q5

PM2

BE

NA

UM

Increasing permission for adaptation

Lower limit guaranteed plus some chances for more resources

Only statistical values guaranteed

Adaptation view

Notations:

BQ1, BQ2, .. Different sets of Bandwidth reqs.

(decreasing QoS order)

DLJ-Q1, 2, ..- different sets of DJL reqs (decreasing QoS order)

QoS classes

Well known- int’l (Meta QC)

Local (LQC) composition



• Resource provisioning: interactions and contracts between business actors


Access Network AS1

NRM@NP

HB1

AS2

NRMr@NP

MANE

CANMgr CANMgr

Service Manager@SP

2

3

NRM@ANP

1

CAN layer Management

NIA 4

Multi-domain VCAN

HB-SW

NIA

NIA

HB + SP Environment

EU host

PHY connection

Contract(SLA/SLS) or interaction in Mng. Plane or Control Plane

Logical relationship

Data and signalling connections (PHY and/or logical)

Network elements configuration commands

MANE

MANE MANE AR

Service Provider

Media flow Input

Output

5

Adaptation


• Optimisation Loop 1:– Resource provisioning: interactions and contracts between business actors

• contracts/interactions of SLA/SLS types performed in the Management and Control Plane and the appropriate I/Fs exist:

• SP-CANP(1): the SP requests to CANP to provision/ modify/ terminate new VCANs and the CANP to inform SP about its capabilities

• • CANP-NP(2) - the NP offers or commits to offer resources to CANP (this data are

topological, QoS and capacity-related)

• CANP-CANP(3) - to extend a VCAN upon several NP domains; • -Network Interconnection Agreements (NIA) (4) between the NPs or between NPs

and ANPs – these are not innovative ALICANTE functionalities but are necessary for NP cooperation.

• After the SP negotiates a desired VCAN with CANP, – it will issue the installation commands to CANP– which in turn configures via IntraNRM (5) the MANE functional blocks (input and output).



• Content awareness at CAN Layer• three ways:

1. by concluding an SLA between SP and CANP, concerning different VCAN(s) construction.

• The content servers are instructed by the SP to insert some special Content Aware Transport Information (CATI).

• This simplifies the media flow classification and treatment by the MANE.

2. the SLA is concluded, but no CATI information is inserted in the data packets.

– The MANE applies Deep Packet Inspection for data flow classification and assignment to VCANs.

– The treatment of the flows is based on VCANs characteristics defined in the SLA.

3. no SLA exists between SP and CANP– No CATI is inserted in the data packets– The treatment of the data flows can still be CA-style, but conforming to

the local policy established at CANP and IntraNRM.




• SP-CANP SLS clauses and

SLS Element/Clause

SLS Identification

VCAN Associated CATI

VCAN Connectivity Services Req .

Topology & scope: (pipe, hose, funnel, multicast tree, etc.) and scope (ingress, egress points)

Connectivity class (guarantees): quantitative/qualitative: delay, jitter, loss, availability

Bandwidth (capacity)

VCAN Traffic Processing Req.

Access and transfer rules: Ingress flow Id, Egress flow Id, Ingress point, Egress point

Access and transfer rules: QoS Guarantees: Class, (dropping, re-marking, shaping)

Access and transfer rules: QoS guarantees: Conformance algorithm

Access and transfer rules: QoS Guarantees: Excess traffic treatment

Routing and Forwarding rules

Security requirements

Adaptation requirements

Reliability



• SP-CANP SLS clauses (cont’d)VCAN Services Assessment Req.

Monitoring methodology

Monitoring tasks

Notification and Reports

VCAN Allowed actions

Availability and VCAN service schedule

Invocation methods

Modification permission (of): Connectivity services; Traffic Processing; Service Assessment


VCAN types and QoS - examplesTopologies: 1-1, 1-Any_n, Any_n-1, nxm, multicast (1-m), combinations

Example: Multicast + SVC based adaptation

Multicast

VCAN

B A

C D

MANE

Multi-domain peering and QoS classes VCAN based on well known QCs ( Meta

QC) VCAN as a composition of Local QC Hierarchical VCAN + local QC

5. Use case examples

User1

User2 HD-Ready TV

Full-HD TV

HB1

HB2

HB3

SP/CP

MANE1 MANE2

Mobile

Codec: MPEG-2 Resolution: 576i Framerate: 25 Hz

Codec: AVC Resolution: 720p Framerate: 50 Hz

Codec: SVC Resolution:1080p Framerate:50 Hz

SVC-BL: 720x576@25 EL1: 1280x720@50 EL2: 1920x1080@50

Codec: AVC Resolution: 1080p Framerate: 50 Hz

User3


6. Conclusions

• ALICANTE: New architecture media and FI oriented , based on:– Content aware networking– Network aware applications– QoS capable

• Different classes of services, Level of guarantees• Use traditional network layer QoS technologies: MPLS, Diffserv

• Two main cross- layer optimisation loops– Resource provisioning ( SP-CANP-NRM cooperation)– Media flow adaptation (see slide 8)

• Future work– Specification refinements, Design, Implementation, Integration ,

Use case experiments– Performances analysis or different solutions


• THANK YOU

• Questions?

Service provider and content aware network provider cross layer optimisation of multimedia...

Technology

Transcript of Service provider and content aware network provider cross layer optimisation of multimedia...