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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
video applications. There are many IETF working group that progress architecture and concept for<br />
QoS framework for <strong>IP</strong> as. They are summarized in what follows:<br />
• Intserv: Integrated service working group. Define a set of service models to support<br />
quality of service requirements of various applications.<br />
• Diffserv: Differentiated service working group. Differentiated traffic based on<br />
application type and provides appropriate service.<br />
• QoSr: QoS-based Routing working group. Provides a framework for QoS-based<br />
routing protocols. QoS Routing allows the network to determine a path that supports<br />
the QoS needs of one or more flows in the network [120].<br />
• RSVP: Resource reservation setup protocol working group. Design a signaling<br />
mechanism to reserve resources along the connection to support specially integrated<br />
service.<br />
• MPLS: Multi-protocol label switching. Provides standards for label switching which<br />
can be used for building fast routers/switches.<br />
3.2.4.1 Best Effort Services<br />
The best effort service model is the basic service provided by <strong>IP</strong>. All users’ packets, entering<br />
the network, compute equally for network resources. In best effort service model, the network<br />
would make its best attempt to deliver packets to their destination with no guarantees and no<br />
special resources allocated for any of the packets. Network elements use in general FIFO discipline<br />
as a simple queuing discipline.<br />
3.2.4.2 Integrated Services<br />
Integrated Service (IntServ) defines an architecture that is able to reserve network resources<br />
for individual flows in order to provide QoS guarantees to end users. The integrated service<br />
working group has specified Control Load Service (CLS) and Guaranteed Service (GS) in addition to the<br />
best effort service. RFC 2216 [121] gives a framework which specifies the functionalities of network<br />
components which can support multiple, dynamic quality of service. The framework defines a set<br />
of functionalities including the setup protocol needed to define the service and the end-to-end<br />
behavior.<br />
The control load service (CLS) [122] aims to provide a QoS to applications that closely<br />
approximating the QoS a flow would receive from an unloaded network. CLS uses capacity<br />
(admission) control to assure that the service is received even when the network element is<br />
overloaded. This assumption reposes on defining traffic specification (TSpec) [123] for each flow<br />
traversing the network. TSpec consists of a token bucket plus a peak rate, minimum policed unit,<br />
and a maximum packet size. Policy is applied for a particular traffic using a token bucket filter. The<br />
RSVP protocol is used to reserve the appropriate resource along the packet flow.<br />
The guaranteed Service (GS) [124] aims to deliver a guaranteed on delay and bandwidth of a<br />
particular flows in <strong>IP</strong>. It provides a mathematically provable approach for bounding the end-to-end<br />
delay. Thus, it provides a service that guarantees both delay and bandwidth. GS uses also TSpec to<br />
55