Open In App

Computer Network | Quality of Service and Multimedia

Quality-of-Service (QoS) refers to traffic control mechanisms that seek to either differentiate performance based on application or network-operator requirements or provide predictable or guaranteed performance to applications, sessions, or traffic aggregates. Basic phenomenon for QoS means in terms of packet delay and losses of various kinds.

Need for QoS –



QoS Specification –
QoS requirements can be specified as:

  1. Delay
  2. Delay Variation(Jitter)
  3. Throughput
  4. Error Rate

There are two types of QoS Solutions:



  1. Stateless Solutions –
    Routers maintain no fine-grained state about traffic, one positive factor of it is that it is scalable and robust. But it has weak services as there is no guarantee about the kind of delay or performance in a particular application which we have to encounter.
  2. Stateful Solutions –
    Routers maintain a per-flow state as flow is very important in providing the Quality-of-Service i.e. providing powerful services such as guaranteed services and high resource utilization, providing protection, and is much less scalable and robust.

Integrated Services(IntServ) –

  1. An architecture for providing QoS guarantees in IP networks for individual application sessions.
  2. Relies on resource reservation, and routers need to maintain state information of allocated resources and respond to new call setup requests.
  3. Network decides whether to admit or deny a new call setup request.

IntServ QoS Components –

RSVP-Internet Signaling –
It creates and maintains distributed reservation state, initiated by the receiver and scales for multicast, which needs to be refreshed otherwise reservation times out as it is in soft state. Latest paths were discovered through “PATH” messages (forward direction) and used by RESV messages (reserve direction).

Call Admission –

Diff-Serv –
Differentiated Service is a stateful solution in which each flow doesn’t mean a different state. It provides reduced state services i.e. maintaining state only for larger granular flows rather than end-to-end flows tries to achieve the best of both worlds.

Intended to address the following difficulties with IntServ and RSVP:

  1. Flexible Service Models:
    IntServ has only two classes, want to provide more qualitative service classes: want to provide ‘relative’ service distinction.
  2. Simpler signaling:
    Many applications and users may only want to specify a more qualitative notion of service.

Streaming Live Multimedia –

Article Tags :