25.04.2014 Views

TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3.2.5 <strong>IP</strong> Signaling Protocols for <strong>Packet</strong> <strong>Video</strong> Applications<br />

Signaling protocols over <strong>IP</strong> networks such as the Internet offer intelligent network services to<br />

the applications in particular packet video applications. Two core signaling protocols are discussed<br />

in these subsections. The first category is related to QoS signaling protocol such as RSVP,<br />

RTP/RTCP, and COPS. The second category concerns session signaling protocol such as H.323,<br />

S<strong>IP</strong>, and MPEG-4 DMIF.<br />

3.2.5.1 QoS Control Signaling Protocols<br />

QoS Control signaling protocols are defined in order to provide Quality of Service support<br />

between network nodes and the applications. The signaling protocol defines a set of algorithms,<br />

messages, and parameters used by the network to assure Quality of Service to user traffic. In<br />

particular, QoS signaling helps to provide differentiated delivery services for individual flows or<br />

aggregates, network provisioning, admission control, service guarantee, control load service, etc.<br />

Dynamic QoS management could be provided using QoS signaling protocols.<br />

We present in the following subsections two QoS signaling mechanisms which were developed<br />

to implement Integrated Services Framework and Differentiated Services Framework. These<br />

protocols are RSVP (Resource Reservation Protocol) and COPS (Common Open Policy Service).<br />

3.2.5.1.1 RSVP<br />

RSVP (Resource Reservation Protocol) [136] is a signaling protocol for resource reservation in<br />

<strong>IP</strong> networks. Communally it is used for Intserv architecture (controlled load and guarantee service).<br />

RSVP is an object-based message protocol which provides mechanisms to the application to<br />

request a specific QoS from the network. RSVP carries the request through the network, visiting<br />

each network element and attempts to make a resource reservation for the stream. To make a<br />

resource reservation, the RSVP communicates with two local decision modules, admission control and<br />

policy control. Admission control determines whether the network element has sufficient available<br />

resources to supply the requested QoS. Policy control determines whether the user has<br />

administrative permission to make the reservation. RSVP supports both multicast and unicast<br />

traffic, for <strong>IP</strong>V4 and <strong>IP</strong>V6 clients.<br />

3.2.5.1.2 COPS Protocol<br />

The COPS (Common Open Policy Service) [137] Protocol is a QoS signaling protocols<br />

supporting policy control over a simple client/server model. The protocol describes a simple query<br />

and response protocol that can be used to exchange policy information between a policy server<br />

(Policy Decision Point or PDP) and its clients (Policy Enforcement Points or PEPs). One<br />

example of a policy client is an RSVP router that must exercise policy-based admission control over<br />

RSVP usage (COPS-RSVP) [138] or a Diffserv client that receives configuration information about<br />

Diffserv elements like meter, classifier, scheduler, shaper, etc. (COPS-PR) [139].<br />

3.2.5.2 Session Control Signaling Protocol<br />

<strong>Packet</strong> video application has grown rapidly in the last few years. This rapid expansion and<br />

potential is essentially due to standardization bodies that enable protocols and services. Actually, it<br />

appears likely that both IETF S<strong>IP</strong> (Session Initiation Protocol) [140] with SDP (Session<br />

58

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!