Qos Policy - UTStarcom iSpirit 3026 Manual

DSCP-DSCP Mapping Table

4. QoS Policy

QoS policy includes two parts that is Policing and Mark. After data flow classified, certain QoS
policies needed to realize class QoS processing purpose. QoS policy mainly includes
Determine bandwidth limitation of class to find whether it is within or beyond bandwidth limitation
Determine PRI queue of class
Determine that whether or how to modify the data packet of class information
All input ports of iSpirit 3026 switch support that bandwidth limitation for all data flows, it can
realize class bandwidth limitation process in bucket algorithm, please refer to Figure 12-5.
Bucketsize indicates that the max. burst data flow size supported. If there are matched data flow
release from output port, it is equal to that release from bucket, Bucketcount moves down until
arrive at the lower than Threshold when matched data flow inflow from input port is limited to
"Out of Profile" status. Every 8 us the system will according to certain bandwidth limitation value
add flux of Refreshcount into bucket, Bucketcount increases until arrive at the upper than
Threshold, data flow will be permitted to release out when it is in "In Profile" status. When some
class is in Out of Profile status, throw away succeeding data flow, or to do further processing if it
is in In Profile status.
Figure 12-5. Bucket Algorithm For Bandwidth Limitation