General description

The bandwidth control for subscribers is similar to the overall bandwidth control. All options are available:

Bandwidth limitation by the traffic classes (for example: limit torrents

Traffic's prioritization within the subscriber's bandwidth with borrowing (HTB) or as "pipes" (TBF)

Protocols are divided into 8 classes. This number is limited by number of priorities set up by the option "Protocol dependent prioritizing of traffic". Placing of a particular protocol into its class is controlled by the same option: (class <-> priority).

The assignment of traffic control policies for subscribers is supported by Subscriber Management,SM.

Application of tariff plans per subscriber is possible using the PUSH method or via RADIUS for BRAS L3 and BRAS L2.

General description

Subscriber traffic is defined by a list of IP addresses or CIDR. Subscriber traffic can have Subcribers channel policing for IPv4 and IPV6 applied, but it is also subject to the policing of the General or Virtual channel in which the Subscriber resides. For more details, see General description of policing.

Policing is applied to 8 traffic classes, configured via Traffic prioritization depending on protocols and directions.

The mapping of a protocol to its class is also regulated by the option (class <-> priority). This approach makes it possible to combine external and internal policers in a compatible way.

Two policing mechanisms are available to choose from:

TBF without hierarchy (Token Bucket Function), used to limit/block a specific policing class. Bandwidth limitation with burst support.

HTB with hierarchy for 8 classes (Hierarchical Token Bucket), used for prioritization by traffic classes. Bandwidth limitation with borrowing.

Creation and assignment of policing (tariff plan) is performed via Subscriber Management (SM) commands.

Applying tariff plans to a subscriber is possible either using the PUSH method or through RADIUS for BRAS.