Components in the DiffServ Model

The DiffServ model consists of four QoS components. Traffic classification and re-marking provide a basis for differentiated services. Traffic policing and shaping, congestion management, and congestion avoidance control network traffic and resource allocation in different ways and allow the system to provide differentiated services.

Classification and Marking: classification classifies packets while keeping the packets unchanged. Traffic marking sets different priorities for packets and therefore changes the packets.

Traffic marking refers to external re-marking, which is implemented on outgoing packets. Re-marking modifies the priority field of packets to relay QoS information to the next-hop device.

Internal marking is used for internal processing and does not modify packets. Internal marking is implemented on incoming packets for the device to process the packets based on the marks before forwarding them. The concept of internal marking is discussed later in this document.
Policing and Shaping: restricts the traffic rate to a specific value. When traffic exceeds the specified rate, traffic policing drops excess traffic, and traffic shaping buffers excess traffic.
Congestion management: places packets in queues for buffering when traffic congestion occurs and determines the forwarding order based on a specific scheduling algorithm.
Congestion avoidance: monitors network resources. When network congestion intensifies, the device proactively drops packets to regulate traffic so that the network is not overloaded.

The four QoS components are performed in a specific order, as shown in the following figure.

Figure 1 QoS implementation
Click to enlarge

As shown in the Figure 2, the QoS components are performed at different locations on the network, as shown in the following figure. In principle, traffic classification, traffic re-marking, and traffic policing are implemented on the inbound user-side interface, and traffic shaping is implemented on the outbound user-side interface (if packets of various levels are involved, queue scheduling and a packet drop policy must be configured on the outbound user-side interface). Congestion management and congestion avoidance are configured on the outbound network-side interface.

Figure 2 QoS Components
Click to enlarge