e2e qos:the fundamental of the approach - etsi · agenda what is the qos ? the end to end...

21
E2E QoS: The fundamental of the approach Presenter : YIN Chunyang N. SIMONI [email protected] TELECOM ParisTech Computer of Science and Networks Department © ETSI 2009. All rights reserved STF 360 Workshop ETSI Sophia Antipolis

Upload: buitu

Post on 21-Apr-2018

248 views

Category:

Documents


6 download

TRANSCRIPT

E2E QoS: The fundamental of the approach

Presenter : YIN ChunyangN. SIMONI [email protected]

TELECOM ParisTechComputer of Science and Networks Department

© ETSI 2009. All rights reserved

STF 360

Workshop ETSI Sophia Antipolis

Agenda

� What is the QoS ?

� The End to End architecture

� The End-to-End cooperation

� The End-to-End QoS

� The modeling (5)

2

� The modeling (5)� QoS Model (3)

� QoS : towards a definition

� Vertical architecture vs. Horizontal architecture

� Towards an integration

� The End-to-End traceability

� Conclusion

What is the QoS ?

E800: Totality of characteristics of a telecommunications service that bear on its ability to satisfy stated and implied needs of the user of the service.

D esirable_Q oS C apable_Q oS

C onstra ints(dyna m ics)

3

N egotiation

U ser P rovider

P erceived_Q oS P rovided_Q oS

O ffered_Q oSD em a nded_ Q oS

C ontracted_Q oS

TR-126 (QoE): E2E (overall), service level performance from the perspective of the end user

Core Network

Service network

Serviceware

NGN/NGS Middleware

The E2E architecture

4

Core NetworkFixed network

Access Network 1Wireless network

Access Network 2Wired network

Access Network 3Wireless network

Seamless Userware

The End-to-End cooperation

5

PWR

OK

WIC0

ACT/CH

0

ACT/CH

1

WIC0

ACT/C

H0

ACT/CH

1

ETH

ACT

COL

E2E QoS: the characterization of the behavior User Level

(Service Access)

Service Level

Network Level

6

Equipment Level

The modeling : Level of visibility (1/5)

G1

ES3 ES2

User LevelG1

ES3 ES2

G1

ES3 ES2

User Level

7

Router Router

Router Router

Router

Server

Server

Server

Server

CA3

PoP

PoP

PoP

CA4CA1

PoPCA2

ES1

ES3 ES2

ES4 Service Level

Network Level

Equipment LevelRouter Router

Router Router

Router

Server

Server

Server

Server

CA3

PoP

PoP

PoP

CA4CA1

PoPCA2

ES1

ES3 ES2

ES4

Router Router

Router Router

Router

Server

Server

Server

Server

CA3

PoP

PoP

PoP

CA4CA1

PoPCA2

ES1

ES3 ES2

ES4 Service Level

Network Level

Equipment Level

The modeling : the abstraction (2/5)

The universal encyclopedia defines abstraction as « aformal work, structuring the data according tofour distinguished mental operations »

•• simplification (neglecting all the simplification (neglecting all the circumstance circumstance touring an act), touring an act),

8

touring an act), touring an act),

•• Generalization (identifying the general Generalization (identifying the general proprieties), proprieties),

•• Selection (isolating a specific feature),Selection (isolating a specific feature),

•• schematization (analyzing a phenomena and schematization (analyzing a phenomena and restorer it as a data system).restorer it as a data system).

The modeling of the real world (3/5)The modeling of the real world (3/5)

� “Node”: it is the abstraction representing an entit y, any element (server, router, terminal, etc) responsible of a sp ecific processing.

� “Link”: it is the abstraction representing the inte raction between two nodes. It designates any component (flow, virtu al circuit, cable, etc) offering its transfer capacities in ord er to provide to

9

cable, etc) offering its transfer capacities in ord er to provide to the nodes a support of interconnection.

� “Network”: is a set of nodes and links offering any global service (service component’s network, transport network, PA N, etc) in a transparent way.

Service Level modeling ….(4/5)� Our vision to build ⇒ service-oriented design

� The service node concept is considered as the basic entity to design and develop distributed applications

� A global service can thus be built by dynamically c omposing modular services, thus obtaining service-level

10

� Our approach to service is based on Virtual Private Service Network (VPSN) concept

⇒⇒⇒⇒ But why the vision

General approach (5/5)

� VPSN (Virtual Private Service Network)

� Network of service components which provides a personalized value-added

service according to the user requirements (preference, QoS,…)

� Follows a « Node-Link-Network » model

� Service-level overlay

11

� Example of a vocal SMS service composed of three components

Service component

Audio output

Text-to-speech

(provider 2)

Codec conversion

Media link

VPSN

SMS Server

Text-to-speech

(provider 1)

QoS of each level: which model? (1/3)

� Temporal transparency: transfer the information onc e the user creates it

and as long time as the duration of its transferrin g ( ), without

changing the temporal relation intrinsic with the generated information

(Delay).

� Spatial transparency: transfer the volume of the in formation

Availability

Delay

12

� Spatial transparency: transfer the volume of the in formation instantaneously generated ( Capacity ),

� Semantic transparency: the transfer is done totally and without content alteration ( Reliability ).Reliability

Capacity

A same model : QoS criteria (2/3)� Availability indicates the accessibility rate for t he nodes and the logical

links we defined in our Meta model as well.

� Reliability indicates the involuntary modification rate of the information concerning the nodes and the links during their tre atment.

� Delay indicates the treatment’s duration of the nod es and the mean delay

13

� Delay indicates the treatment’s duration of the nod es and the mean delay of the routing information of the links.

� Capacity indicates the maximum charge of the servic e nodes and the usable bandwidth of the links.

The conceptual tools (3/3)

User

Service

Visibility Levels

QoS Evaluation•••• Availability

Location Semantic

14

Network

Equipment

•••• Reliability

•••• Delay

•••• CapacityThe source behaviorDistance

QoS : towards a definition

� SLA (Service Level Agreement) between a service pr ovider and a client.

� It is defined through a contract.

� It is evaluated through all the criteria.

� It is measured through the relevant parameters in each visibility level .

15

� It is measured through the relevant parameters in each visibility level .

� It formalizes the no-functional aspects of each function.

� It is aggregated for an End-to-End flow.

Vertical architecture vs. Horizontal architecture

Virtual Telecommunications Community

Userware

16

Userware

N1 N2 N4N3

Towards an integration

SCA

SCA

SCASCN SCNSCUSCUSCUSCU

SCUSCUSCUSCUSCUSCU

17

Access Level

Service Level

Network Level

SCA

SCA

SCASCN

SCNSCNSCUSCU

SCUSCU SCUSCU

SCUSCU

SCA: Servcie Component for ApplicationSCN: Service Component for NetworkSCU: Service Component for User

The End-to-End traceability

SE1SE3SE2

BE4BE1BE3BE2Business Visibility Level

Service Visibility Level

18Visibility Level � Operator’s Decision Level

SE4SE1

PoP

PoP PoP

PoP NE3

NE4NE1

NE2Network Visibility Level

Equipment Visibility Level

A first conclusion : A methodology for E2E QoS

� Identifying all the actors on the End-to-End chain

� Positioning according to the visibility’s level

� Study the four criteria of the QoS at each level

� Identification the measurable parameters associated to each

19

� Identification the measurable parameters associated to each

criteria at each level.

References

� ITU-T Recommendation E800: TERMS AND DEFINITIONSRELATED TO QUALITY OF SERVICE. AND NETWORK PERFORMANCE INCLUDING DEPENDABILITY, revised in 200 8

� TR-126: Triple-play Services, Quality of Experience (QoE) Requirements, 13 December 2006, DSL Forum Technical Report

� H. Huynh, N. Simoni, E. Lavinal, “A Dynamic QoS Man agement for

20

� H. Huynh, N. Simoni, E. Lavinal, “A Dynamic QoS Man agement for Next Generation of Services”, ICAS’07 Jun. 2007, At hens, Greece

� Z. Benahmed Daho, N. Simoni, “Towards Dynamic Virtu al Private Service Networks: Design and Self-Management”, IEEE /IFIP NOMS 2006, April 2006, Vancouver, Canada

Thank you and questions?

21