WiFi & QoS

802.11

With the 802.11 protocol, it is not possible to prioritize between packets. Other methods must be used to successfully implement QoS. In this post you can gain some practical knowledge about how things (in overall terms) are brought together.

Distributed coordinated function (DCF)

Without going into too detailed explanation about wireless vs. wired networks, we will just relate to wireless network use CSMA/CA instead of the wired method CSMA/CD. Why is that you might ask yourself?

The wireless system is a distributed system which means that all “players” (Client and AP) share the overall media. The AP cannot control who sends a packet first. It works by the method called Distributed Coordinated Function (DCF).

Every Client starts the conversation by picking a random number and start a countdown. When the countdown reaches zero, the client will “fire” its packet (if the media is available). If the media is busy, the client doubles it counters and starts all over.

802.11e /WMM

The 802.11e protocol is designed to overcome issues regarding missing QoS on wireless network. The WMM divides the traffic into 4 categories, so instead of having only a single queue for all clients, we now have four (for WMM enabled clients). Each queue has different back-off timers and thereby different countdown windows.

This four queue-systems is called “Enhanced Distributed Channel Access” (EDCA)

Access Category and “Timing”

Based on the WMM functionality, the data-application will be assigned and placed in one of the four queues. In each queue, a different set of rules will decide the countdown starting value. Traffic in the Platinum queue will start with a lower counter than ex. traffic in the silver queue, and therefore reach zero first, which is a simple but effective way of prioritizing traffic in the network.

The NAV value

The basic function for this: A Counter value maintained by each station with an amount of time that must run until the medium will be free. It contains the time that the currently transmitting station will use the medium and information for how long it will require the air to transmit the frame. Remember! A station cannot transmit until the NAV = 0 (zero)

Each station will try to calculate how long it will take to transmit the frame. The calculation is based on data rate and frame length. It’s quite practical information and is included in the Duration field of the frame header. The information is used by all other stations, in the same area to set their NAV.

IEEE 802.11e, IEEE 802.1P, and DSCP Mapping

When an 802.11e (WMM) client send a frame, it will need an IEEE 802.1P classification in the frame. The AP needs to translate this classification into a DSCP value for the LWAPP/CAPWAP packet carrying the frame. This is the only way to make sure that the packet is treated with the correct priority on its way to the WLC. The same has to occur on the WLC, when it forwards packets to the AP and the connected clients.

Translation DSCP to 802.11p to 802.11e

Cisco uses the encapsulation-method “CAPWAP tunnel” to run the wireless data within.
Because the QoS value must be contained within the packet it’s somehow necessary to contain the QoS classification that has been applied to the WLAN frame. This is done by a simple mapping on classifications to and from DSCP to Class of Service, (CoS).

IEEE / IETF / Cisco

• The IEEE organization is who designed the 802.11p and the 802.11e protocol.
• The possible mapping/classification verves from 0-7, meaning eight classifications can be set.
• The IETF-organization and Cisco do not quite agree on the way to look at the IEEE QoS settings.

They both agree that 7 is to be used for emergency and there by actually never to be used on the network.

• IETF claim the most important packets (for data) are voice packets.
• Cisco claim the most important packets is the LWAPP/CAPWAP packets, cause without them we do not have any network and thereby no voice. At some point Cisco has a point here.

Information About QoS Profiles

Cisco WLAN’s by default support four levels of QoS: Platinum/Voice, Gold/Video, Silver/Best Effort (which is default), and Bronze/Background. It’s recommended to configure:

• The voice WLAN to use Platinum.
• The Video WLAN to user Gold.
• The Normal WLAN to use Silver
• Assign a lower (Bronze) QoS setting for the less important WLAN´s.

Wired to wireless and vice versa

Below an example of the traffic flow/classification for a WMM client, an AP, and a WLC connected to the network.

• 1 and 2 = Traffic from the wired side to the wireless side.
• 3, 4 and 5 = Traffic from the wireless side to the wired side.

1. A frame with 802.1p marking and a packet with an IP DSCP marking arrive on the wired interface on the Controller. The DSCP marking are used for the DSCP “setting” for the CAPWAP/LWAPP packet leaving the WLC and traveling to the wireless client.

2. The 802.1p value on the frame depends on the QoS translation table and the QoS profile for the configured WLAN. The QoS setting on the WLAN is just an expected normal setting.

3. The IP DSCP part of the packet reaching the AP and the AP will translate THE DSCP to an 802.11e CoS (Class of Service) marking that the client will understand.

4. The 802.11e CoS marking on a frame arriving at the AP is translated to an CAPWAP/LWAPP DSCP value at the maximum value for that QoS profile on the WLC.

The DSCP marking on the packet leaving the WLC on its way to the wired net, will by default have the DSCP setting equal to the packet that left the WLAN client. From the WLC to the AP it’s the DSCP marking that’s converted to 802.11e setting for CoS.

• On the trunk ports/link both the DSCP and the 802.1p marking will be transported.
• On the access port/link only the DSCP marking will be transported.

*** Reference: www.wificert.org