QoS Scheduler Policies
Quality of Service Guide 511
preferentially allocate bandwidth within a service or subscriber or multi-service site context
through the service or subscriber or multi-service site level policy without affecting the
overall bandwidth allocation to each service or subscriber or multi-service site. Figure 22
shows a per-service bandwidth allocation using the two scheduler policy model. While the
figure shows services grouped by scheduling priority, it is expected that many service models
will place the services in a common port priority and use weights to provide a weighted
distribution between the service instances. Higher weights provide for relatively higher
amounts of bandwidth.
Figure 22: Schedulers on SAP or Multi-Service Site Receive Bandwidth From Port Priority Levels
Direct Service or Subscriber or Multi-service site Queue Association to Port
Scheduler Parents
The second model of bandwidth allocation on an egress access port is to directly associate a
service or subscriber or multi-service site queue to a port-level scheduler. This model allows
the port scheduler hierarchy to allocate bandwidth on a per class or priority basis to each
service or subscriber or multi-service site queue. This allows the provider to manage the
available egress port bandwidth on a service tier basis ensuring that during egress port
congestion, a deterministic behavior is possible from an aggregate perspective. While this
OSSG132
SAP or MSS
Port
SAP or MSS
SAP or MSS
SAP or MSS
SAP or MSS
SAP or MSS
Priority 1
Weighted
Rate Limiting
Scheduler
Priority 2
Weighted
Rate Limiting
Scheduler
Port
Strict Rate
Limiting
Scheduler
Priority n
Weighted
Rate Limiting
Scheduler
To Next Page
Loading...
