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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

epresent user traffic. The delay can be bounded using an envelope curve calculated for each<br />

network element. Thus, the transfer delay of a particular packet is computed from the time it enters<br />

the network until it leaves a particular network element [125]. Furthermore, policy is done at the<br />

edge router of the network to check weather a particular flow is conforming to TSpec or not. When<br />

non-conforming packet arrives, they receive best-effort service. Appropriate scheduling<br />

mechanisms, such as WFQ (Weighted Fair Queuing), are used each network element.<br />

Intuitively, the most straightforward method for assuring service guarantees to packet video<br />

applications is to reserve resources according to an application’s request. However, reservation<br />

based schemes involve admission control algorithms, reservation protocols such as RSVP,<br />

monitoring protocols to track the change in network conditions, and signaling mechanisms. These<br />

kinds of schemes are generally complex and require extensive network support. This can lead to<br />

network scalability and robustness problems.<br />

3.2.4.3 Differentiated Services<br />

The Differentiated Service Architecture (Diffserv) [126] has been motivated by the market<br />

need for immediate deployment of a QoS solution for <strong>IP</strong> networks. In contrast to the per-flow<br />

orientation of RSVP, Diffserv networks classifies packets into one of a small number of aggregated<br />

classes, based on the DSCP (Diffserv Code Point) in the packet’s <strong>IP</strong> header [127]. At each Diffserv<br />

router, packets are subjected to a PHB (Per-Hop Behavior), which is invoked by the DSCP. A PHB<br />

is defined to provide a specific forwarding behavior at each router within the Diffserv domain.<br />

Two PHB schemas known as EF (Expedited Forwarding) [128] and AF (Assured Forwarding)<br />

[129] has been proposed to provide differential treatment of traffic. The EF PHB can be used to<br />

build a low loss, low delay, low jitter, assured bandwidth, and end-to-end service through Diffserv<br />

domains, while AF PHB group provides different levels of forwarding assurance for <strong>IP</strong> packets by<br />

discarding more low priority packets during times of congestion than high priority packets. AF<br />

PHB provides four <strong>IP</strong> packet forwarding classes. Within each AF class, an <strong>IP</strong> packet is assigned one<br />

of the three different levels of drop precedence (i.e. a total of twelve code points).<br />

Diffserv architecture defines, at a lower level, four types of data-path elements: traffic<br />

classifiers, actions elements, meters and queuing elements as shown in Figure 3-11.<br />

Meter<br />

Input traffic<br />

Classifier Marker Scheduler<br />

Output traffic<br />

Figure 3-11: <strong>IP</strong> differentiated service components<br />

• The Classifier performs the classification of traffic based on multiples fields in the <strong>IP</strong><br />

packet such as source / destination address, source / destination port, Type of Service<br />

(TOS) field, etc.<br />

• The Meter measures the amount of traffic received of a particular flows. It checks<br />

weather the traffic is conforming to the traffic specification or not. It also apply some<br />

policy on confirming and non-conforming traffic.<br />

56

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

Saved successfully!

Ooh no, something went wrong!