User's Manual
Table Of Contents
- 1 Preface
- 2 Overview
- 3 Features
- 3.1 Main Features
- 3.2 Adaptive Coding and Modulation (ACM)
- 3.3 Transmit Power Control (TPC)
- 3.4 2x2 Multiple-input and Multiple-output (2x2 MIMO)
- 3.5 Dynamic Frequency Selection (DFS)
- 3.6 Dynamic Channel Selection (DCS)
- 3.7 Retransmission
- 3.8 Configurable Uplink/Downlink Ratio
- 3.9 Quality of Service (QoS)
- 3.10 Power over Ethernet
- 3.11 Synchronization
- 3.12 Co-site Synchronization
- 3.13 OFDM Modulation
- 3.14 Low-density Parity Check (LDPC) Encoding
- 3.15 LLDP
- 3.16 Radio Port Performance Monitoring
- 3.17 Adaptive Noise Immunity (ANI)
- 4 Mechanical Structure and Interfaces
- 5 Product Structure
- 6 Management
- 7 Technical Specification
- 8 Standards
20
DragonWave Inc.Features
3.9 Quality of Service (QoS)
Figure 7 shows the QoS architecture of Lite with the following main components.
• Priority determination (classification)
• Scheduling
• CoS queue and egress port rate limiting (shaping).
Figure 7 QoS Architecture
3.9.1 Priority Determination (Classification)
Lite supports service priority determination based on the 802.1p byte/DSCP. Depending
on the priority determination of the data, the system will direct the data into different
queues.
3.9.2 Scheduling
Lite supports 8 queues on each port, each queue corresponding to one priority, from the
highest CoS7 to the lowest CoS0. The following scheduling methods are supported by
Lite:
• Strict priority (SP)
The SP mothod schedules access to the egress port between the QoS queues, from
the highest QoS queue index to the lowest. The purpose is to provide a lower latency
service to the higher QoS class of traffic.
Traffic in higher priority queues is scheduled first until all demand is met or until all
available bandwidth is used.
Strict priority queues have no limit or CIR so it will get all the bandwidth required if it
is available, before bandwidth is offered to other queues.