Skip to content
  • There are no suggestions because the search field is empty.

QoS Policy Overview

A QoS policy is a set of guidelines that specify the levels of QoS assigned to different types of network traffic. It's crucial in ensuring reliable network performance, much like a security policy is for network safety. 

Traffic identification, classification, and policy definition

Defining QoS policies involves three essential steps:

  • Traffic Identification: Analyzing network traffic to determine its type and QoS requirements, such as voice, video, and data traffic.
  • Traffic Classification: Grouping traffic into classes with similar QoS requirements. For instance, segregate voice and video traffic into dedicated classes while placing all data traffic in a best-effort class.
  • Policy Definition: Defining QoS policies that align with the requirements of each traffic class. For example, assign top priority to voice traffic, video, and best-effort traffic, which transmits only when the network is idle.

Traffic Identification

Traffic identification in QoS involves recognizing the different types of traffic flowing across a network, such as voice, video, or data packets. This recognition is achieved through deep packet inspection, port-based classification, or application signatures. 

It's crucial because, without accurate identification, QoS classification cannot be performed, and policies cannot be applied effectively. By understanding the nature of traffic, networks can prioritize critical data, allocate bandwidth appropriately, and ensure optimal performance for various applications, enhancing the overall user experience.

Traffic Classification

Traffic classification is essential for effectively managing network resources and ensuring that critical applications receive the necessary priority and performance levels. This is the process of categorizing network traffic into different classes or groups based on specific characteristics or attributes. This categorization enables you to apply QoS policies and prioritize traffic accordingly.

The number of classes needed in a network depends on its specific requirements and the types of traffic it handles. Typically, networks use a few key classes to ensure appropriate treatment for different types of traffic, such as high-priority, best-effort, and low-priority classes. However, the exact number of classes can vary widely.

The number of QoS classes needed depends on factors like the complexity of the network, the variety of applications and services running on it, and the desired level of traffic differentiation. Smaller networks may require fewer classes, while larger and more diverse networks may need additional classes to manage traffic effectively. 

For instance, in an enterprise network, voice and video traffic can be classified into the voice class (the highest-priority class) and video classes, respectively, to ensure low latency and minimal jitter. Applications critical to the business can be classified into the mission-critical class for smooth real-time communication, regular data transfers like emails and web browsing can be in a best-effort class, and backup and file downloads can be placed in a low-priority class, such as the Scavenger class to prevent congestion.

Policy Definition

QoS policies are rules that define actions on how different types of traffic should be treated to meet specific service and performance objectives. They specify the prioritization, resource allocation, and traffic handling based on its characteristics, such as bandwidth requirements and latency sensitivity. The goal of QoS policies is to ensure that critical traffic, like voice or video, receives consistent and reliable service, while less critical traffic may experience some degradation during network congestion. 

These policies aim to optimize network performance, minimize delays, and enhance the overall service quality across the network. Creating a QoS policy for each traffic class involves establishing minimum and maximum bandwidth thresholds, allocating class priorities, and implementing congestion management.