Giodi GiorgiPISATEL

Giodi Giorgi

Università degli Studi di PisaDipartimento di Ingegneria della Informazione: Elettronica, Informatica, Telecomunicazioni

Gruppo di Ricerca in Reti di Telecomunicazioniwwwtlc.iet.unipi.it

Dynamic MPEG-4 service setup in Multi-protocol Access Inter Domain

architecture

Slide 1Giodi Giorgi

PISATEL

Outline

• The Multi-protocol Access Inter Domain architecture– The Common Open Policy Service and its extensions– The seamless inter-domain QoS-IP services

• Inferring QoS-IP parameters from multimedia applications in the MAID architecture

– The QoS-IP generalized syntax

• Inter-working between the MPEG-4 DMIF and the MAID QoS-IP signaling– MPEG-4 architectural overview– MPEG-4 DMIF: message flow– DMIF IWU implementation

Slide 2Giodi Giorgi

PISATEL

Outline

• The Multi-protocol Access Inter Domain architecture– The Common Open Policy Service and its extensions– The seamless inter-domain QoS-IP services

• Inferring QoS-IP parameters from multimedia applications in the MAID architecture

– The QoS-IP generalized syntax

• Inter-working between the MPEG-4 DMIF and the MAID QoS-IP signaling– MPEG-4 architectural overview– MPEG-4 DMIF: message flow– DMIF IWU implementation

Slide 3Giodi Giorgi

PISATEL

QoS requirementsFrom the user perspective:

– the dynamism (e.g. the service should last as long as the user needs), – the tailoring (e.g. the network resources allocated for the service should fulfill exactly

the end-user requirements), – a seamless integration (e.g. the mechanisms involved in QoS support should be

transparent to end-user applications).… indeed, the main obstacles

– the different backbone networks technologies (e.g. DiffServ, MPLS, IPoATM, etc.), which make hard to guarantee end-to-end QoS, above all when the service has to be deployed across different administrative domains

– the number of different protocols used in the access networks (e.g. RSVP, H.323, SIP, MPEG-4..), which implies a per-service/per-protocol User-Network-Interface (UNI)

– … and the required QoS is often not explicitly declared in the access signaling flow (e.g. H.323)

From the Service Provider perspective:– interoperation of adjacent domains with the same or different technologies, which

implies a Network-to-Network-Interface (NNI),– interoperation of equipments from different vendors.

Slide 4Giodi Giorgi

PISATEL

Multi-Access Inter-Domain

H.323

RSVPSIP

MPEG-4

(G)MPLS/DSnetwork

Multi-Protocol Access network

Multi-AccessMPLS/DiffServBorder Router

MA-BR

Multi-AccessMPLS/DiffServBorder Router

MA-BR

Service RequestsService

Requests

Bandwidth Broker

MAID-BB

Bandwidth Broker

MAID-BB

COPS-MAID

MPLS

MAMAMAUNI

IDIDID

Slide 5Giodi Giorgi

PISATEL

The COPS protocol

PEP

PEP

PEP

PDP

PDP

BB

Client type = x

Client type = y

Client type = z

RAR

RARPEP

LPDP

PDP

Network Node Policy Server

COPS(RFC 2748)

PDP Policy Decision Point, COPS server

PEP Policy Enforcement Point,COPS client

• Different applications using different protocols → different client types.• The trend to define a new client type for each access network protocol results in

a hard limit to the system scalability (duplication of the states installed both in the COPS client and in the COPS server).

• A possible solution: the cluster of COPS server, each supporting one or few client-types.

• Disadvantage: all these COPS servers have either to exchange management information to perform a coherent resource allocation or should refer to a higher level ”omniscient” BB.

Slide 6Giodi Giorgi

PISATEL

COPS-MAID extensions• Solution proposed through the COPS-MAID architecture

– define a unified and extended COPS semantic, which integrate all the QoSinformation carried out by the different access protocols

– translate the different QoS information in a unique format • This solution transfers the system complexity on the border routers, in which

appropriate Inter Working Units (IWUs) are used to map protocol specific messages into generalized client messages.

• A unique COPS client-type (i.e. the COPS-MAID one) can transmit all the information to a unique COPS server, which can be located inside the BB itself.

PEP Client type = MAID

PDP

BB

MA-BR

PEP

MA-BRClient type = MAID

Slide 7Giodi Giorgi

PISATEL

COPS-MAID extensions

- start time- end time

Temporal info

- Recovery type (path prot., path rest., …)- Diversity type (node, link, SRLG)

LSP recovery behaviour

- Bandwidth, delay- Jitter, loss probability

QoSdescription

- resource class/color- setup/ holding lsp priority, - multiple {lsp diffserv type (e-lsp, l-lsp), traffic characterization (RP, LBAP, 3D-LBAP, etc.)}

Traffic description

- Destination host- Egress MA-BR I/F

Traffic Terminator

- Source host- Ingress MA-BR I/F + Label

Traffic originator

PEP PDP(MA-BR BB)

Request

ContentsDirectionMessage Type

- primary ERO- backup ERO

Explicit RouteObject

- DSCP,- LSPId

Label

- DiffServ,- ATM,- MPLS

Label typePDP PEP(BB MA-BR)

Decision

Slide 8Giodi Giorgi

PISATEL

Intra–domain signaling

MA-BR1 MA-BR2CR1

BB

Access Net signaling (e.g. RSVP)COPS Signaling Core net signaling (e.g. RSVP-TE)

Host2Host1

Slide 9Giodi Giorgi

PISATEL

MAIDcore network

Access Net signaling (e.g. RSVP)COPS-MAID Signaling Core net signaling (e.g. RSVP-TE)

MA-BR1 MA-BR2CR1

BBBB

MAIDcore network

Inter–domain signaling via COPS-MAID

Host2Host1

Slide 10Giodi Giorgi

PISATEL

MAIDcore network

Access Net signaling (e.g. RSVP)COPS-MAID Signaling Core net signaling (e.g. RSVP-TE)NNI signaling (e.g. NNI RSVP-TE)

MA-BR1 MA-BR2CR1

BBBB

MAIDcore network

Inter–domain signaling via NNI

Host2Host1

Slide 11Giodi Giorgi

PISATEL

Outline

• The Multi-protocol Access Inter Domain architecture– The Common Open Policy Service and its extensions– The seamless inter-domain QoS-IP services

• Inferring QoS-IP parameters from multimedia applications in the MAID architecture

– The QoS-IP generalized syntax

• Inter-working between the MPEG-4 DMIF and the MAID QoS-IP signaling– MPEG-4 architectural overview– MPEG-4 DMIF: message flow– DMIF IWU implementation

Slide 12Giodi Giorgi

PISATEL

The QoS-IP generalized syntax• There are 2 basic functionalities to be supported MA-BRs for QoS-IP

provisioning across the IP backbone:

– Understanding of as much as possible QoS semantics from the access net – Translating the access QoS into the interior QoS syntax

• … these requirements lead to the implementation of protocol-specific Inter-Working Units (x-IWU)

– x-IWU acts as on-line translators from the specific-QoS syntax to a generalized QoS-IP syntax (i.e. the UNI syntax !!)

• … in order to – accommodate the different QoS semantics from the access net – be independent of the underlying Data Plane technology

Protocol-specific QoSmessages

Generalized UNI messages with QoSProtocol

IWU

Slide 13Giodi Giorgi

PISATEL

The QoS-IP generalized syntax• The generalized UNI syntax for setting up a QoS-IP service might be comprised of:

– A traffic descriptor• A set of filters to be applied to the involved resources:

– case INTESERV: src_add, src_port, dst_add, dst_port, protocol (tcp, udp, other)– case DIFFSERV: dscp

• r-b plot, LBAP, 3D-LBAP, CODECS (g711Alaw64k, g711Ulaw64k, etc.)• traffic setup/holding priorities• resource affinities (Exclude-any/ Include-any/ Include-all color masks) • some recovery info (recovery type, diversity type)• some temporal info (start_time, end_time)

– A QoS descriptor• QoS Class of Service (EF, AF11, AF21, etc.)• bandwidth rates (rate_min, rate_max)• buffer sizes (size_min, size_max)• end-to-end delay (delay_max, delay_min)• end-to-end jitter (jitter_max, jitter_min)• loss probability (loss_max, loss_min)

Slide 14Giodi Giorgi

PISATEL

MA-BRRouter Manager

(MA-BR RM)

COPS Client

Signalling Translation

Module(STM)

RSVP-TEdaemon

MPLSTraffic Control

LSP database(LSP-DB)

to/fromBB

User space (Control & Mgmt Plane)

Kernel space(Data Plane)

H-323IWU

RSVPIWU

LSPIWU

LSP Policy database

(LSP-P- DB)

Policy Database

(P-DB)

MA-BRStats Collection

Module(MA-BR SCM)

Data-Plane Stats Database(BR-DPS DB)

SNMPAgent

Command Line Interface (CLI)

RSVPdaemon

Zebra OSPF-TEdaemons

to/fromneighb. router

HTTP daemon

H.323 GK

Netfilter Routing Table

MIBs

Acce

ss s

erve

rfu

ncs

Acce

ss r

oute

rfu

ncs

EBR Finder

to/fromEBRDMIF

IWUMPEG-4 server

UNI message flow

Protocol-specific message flow

COPS-MAID message flow

The QoS-IP generalized syntax

Slide 15Giodi Giorgi

PISATEL

Outline

• The Multi-protocol Access Inter Domain architecture– The Common Open Policy Service and its extensions– The seamless inter-domain QoS-IP services

• Inferring QoS-IP parameters from multimedia applications in the MAID architecture

– The QoS-IP generalized syntax

• Inter-working between the MPEG-4 DMIF and the MAID QoS-IP signaling– MPEG-4 architectural overview– MPEG-4 DMIF: message flow– DMIF IWU implementation

Slide 16Giodi Giorgi

PISATEL

MPEG-4 architectural overview

The multimedia content is

interactive and object-oriented

Slide 17Giodi Giorgi

PISATEL

MPEG-4 architectural overview

ES_Descriptor

ES_Descriptor

…

Scene Descriptor Stream

Audio Source

Movie Texture

Scene Description

Object Descriptor Stream

Object Descriptor Update

Object Descriptor

ES_D

ES_D

…

Object Descriptor

ES_D

ES_D

…

Object Descriptor

ES_D

ES_D

………

ES_id

ES_idES_id

ES_id

ES_id

Object_Description_id

Initial Object Descriptor

ES Elementary StreamES Elementary Stream

Visual Stream (e.g. base layer)

Visual Stream (e.g. temporal enhancement)

Audio Stream

Slide 18Giodi Giorgi

PISATEL

MPEG-4 architectural overview

FlexMux FlexMux FlexMux

PESMPEG-2

TS

AAL2ATM

RTPUDPIP

H.323PSTN

DABmux …

Transmission/Storage Medium

Multiplexed Streams

FlexMuxStreams

DeliveryLayer

SyncLayer

PacketizedStreams

UpstreamInfo

ElementaryStreams

Objectdescriptor

Scenedescription

infoAV object

data

SL … SL SL … SL SL … SL

CompressionLayer

DAI - DMIF Application Interface

Elementary Stream Interface

MPEG-4 Visual (ISO 14496-2)

&MPEG-4 Audio(ISO 14496-3)

MPEG-4 Systems(ISO 14496-1)

DMIF: Delivery Multimedia Integration Framework

(ISO 14496-6)

DNI - DMIF Network Interface

Interactive Audio/Visual

Scene

Composition & Rendering

Slide 19Giodi Giorgi

PISATEL

MPEG-4 architectural overview

• MPEG-4 multimedia contents are based on the compression and delivery of different objects via the DMIF signaling protocol

• The DMIF signaling protocol is a medium-independent session level protocol (somehow equivalent to the FTP)

– 1st step: opening a session with a peer entity {+ authorization and security checks}– 2nd step: delivering of user data

• Each object is delivered on an independent channel with specific parameters describing the multimedia content (Elementary Stream descriptor)

Slide 20Giodi Giorgi

PISATEL

MPEG-4 DMIF: message flow

DA_ServiceAttachReqDN_SessionSetupReq

DN_SessionSetupCnf

DN_ServiceAttachReqDA_ServiceAttachReq

DA_ServiceAttachResp DN_ServiceAttachCnfDA_ServiceAttachResp

DA_ChannelAddReqDN_ChannelAddReq

DA_ChannelAddReq

DA_ChannelAddRespDN_TransMuxSetupReq

DN_TransMuxSetupCnf

DN_ChannelAddCnfDA_ChannelAddResp

DA_UserCommandReqDN_UserCommandReq

DA_UserCommandReq

SendData DATA TRANSFER RecvData

DMIF DAI APPLICATION

MPEG4 ClientMPEG4 Client

DNIDMIFDAIAPPLICATION

MPEG4 ServerMPEG4 Server

Requestservice

Confirmservice

RequestChannel

AddChannel

••••••••

With QoS params

RequestOther

AdditionalChannels

Ready toreceive

Providedata

Slide 21Giodi Giorgi

PISATEL

MPEG-4 DMIF: message flow

• Some of the delivered descriptors are related to the QoS…

• … since the DAI is designed to operate with any kind of multimedia applications, its QoS descriptor is generic.

Maximum bit rate measured on a a time windowMAX_RATE

Average bit rate measured on a a time windowAVG_RATE

Maximum size of a PDUMAX_PDU_SIZE

A priority identifier of the streamTRAFFIC_TYPE

Maximum delay variation to be experienced by any PDUJITTER_TOLERANCE

Allowable probability of loss of any PDULOSS_PROBABILITY

Average delay to be experienced by any PDUAVG_DELAY

Maximum delay to be experienced by any PDUMAX_DELAY

DescriptionMetrics

End-to-end scope

Traffic description

Slide 22Giodi Giorgi

PISATEL

MPEG-4 DMIF: message flow

DN_TransMuxSetupRequest DN_TransMuxSetupConfirm+-------------------------------------------+| Network Session ID (10 bytes) |+-------------------------------------------+| Descriptors Count (1 byte) |+-------------------------------------------+| Transmux Association Tag – TAT (2 bytes) |+-------------------------------------------+| Direction (1 byte) |+-------------------------------------------+| QoS Descriptors Count (1 byte) |+-------------------------------------------+| QoS_Tag (1 byte) |+------------------------------------ ------+| QoS_DataLen (1 byte) |+-------------------------------------------+| QoS_Data (variable) |+-------------------------------------------+// ... // +-------------------------------------------+| Resources Descriptor Count (2 bytes) |+-------------------------------------------+| Resources Descriptor Type (2 bytes) |+-------------------------------------------+| Resources Descriptor Length (2 bytes) |+-------------------------------------------+| Resources Data Field Count (2 bytes) |+-------------------------------------------+| Resource Descriptor Data Fieds (variable)|+-------------------------------------------+// ... // +-------------------------------------------+// ... // +-------------------------------------------+

Resources

QoSdescriptors

+-------------------------------------------+| Descriptors Count (1 byte) |+-------------------------------------------+| Response (2 byte) |+-------------------------------------------+| Resources Descriptor Count (2 bytes) |+-------------------------------------------+| Resources Descriptor Type (2 bytes) |+-------------------------------------------+| Resources Descriptor Length (2 bytes) |+-------------------------------------------+| Resources Data Field Count (2 bytes) |+-------------------------------------------+| Resource Descriptor Data Fieds (variable)|+-------------------------------------------+| Resources Descriptor Type (2 bytes) |+-------------------------------------------+| Resources Descriptor Length (2 bytes) |+-------------------------------------------+| Resources Data Field Count (2 bytes) |+-------------------------------------------+| Resource Descriptor Data Fieds (variable)|+-------------------------------------------+// // +-------------------------------------------+// ... // +-------------------------------------------+

Resources

e.g. IP resource Descriptor:• IP_src_addr, IP_src_port• IP_dst_addr, IP_dst_port• IP_proto(TCP, UDP, etc.)

Slide 23Giodi Giorgi

PISATEL

DMIF IWU implementation• The basic action of the DMIF-IWU is to “sniff” the DMIF signaling

• When needed the DMIF-IWU triggers the setup of QoS-IP services across the MAID network

– The trigger messages are the DN_TransMuxSetupReq that may carry the QoSdescriptor …

– … and the DN_TransMuxSetupCnf that carries the final resource descriptors (e.g. addresses, ports, protocol)

Max rate

Min rate

Min delay

Max delay

MAX_RATERate range

AVG_RATE

Buffer sizeMAX_PDU_SIZE

LSP setup priorityTRAFFIC_TYPE

End-to-end delay jitterJITTER_TOLERANCE

Loss probabilityLOSS_PROBABILITY

AVG_DELAYEnd-to-end delay

MAX_DELAY

Generalized UNIDMIF QoS Descriptor

Used to determine the

QoS class (EF, AF11, etc.)

Slide 24Giodi Giorgi

PISATEL

DMIF IWU implementation• Two roles are possible for this IWU

– Active: IWU blocks the DMIF channel setup until the Authorization/Admission Control phases are completed on MA-BR (if the requested QoS level cannot be guaranteed the channel is rejected)

– Passive: IWU acts as a passive translator of the DMIF signaling• the call signaling flow proceeds unchanged towards the requesting client

• if the requested QoS level cannot be guaranteed by the MAID network, the channel experiences a Best Effort treatment in the IP network

• the user will decide if the quality of the received streaming is acceptable or not ( stop playing)

Slide 25Giodi Giorgi

PISATEL

DMIF IWU implementation• IWU modular/functional decomposition (passive role)

process_msg_queue

proc_msg_thread

snif_thread

processing_msg_queue processed_msg_queue

DMIF signalling

DNI

DN_TransMuxSetupCnf(with res descr.)

stm_request to/from stm

DN_TransMuxSetupReq (with QoS)

sniffer

Pop

Push

Update

UpdateConnection_Id

Trans_Id

Slide 26Giodi Giorgi

PISATEL

DMIF IWU implementation• IWU modular/functional decomposition (passive role)

process_msg_queue

snif_thread

processing_msg_queue processed_msg_queue

DMIF signalling

DNI

DN_TransMuxReleaseReq(with TAT)

sniffer

Pop

Delete

TAT

proc_msg_threadstm_delete to/from

stm

Slide 27Giodi Giorgi

PISATEL

DMIF-IWU: QoS-IP service setup

B

E

A

C

F

BBDM3

DM2

D

DMIF signalingCOPS-MAID Signaling Core net signaling (e.g. RSVP-TE)BB to Core signaling (e.g. dummy RSVP-TE)NNI signaling (e.g. NNI RSVP-TE)

DN_TransMuxSetupReq DN_TransMuxSetupReq

DN_TransMuxSetupCnfDN_TransMuxSetupCnf

Slide 28Giodi Giorgi

PISATEL

Experimental results

Guaranteed QoS serviceProtected MPEG-4 streaming

Not differentiated trafficBest Effort treatment