| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:dpi_options:opt_bandwidth_mgmt:bandwidth_description [2024/09/26 15:29] – external edit 127.0.0.1 | en:dpi:dpi_options:opt_bandwidth_mgmt:bandwidth_description [2025/09/22 07:51] (current) – elena.krasnobryzh |
|---|
| ====== General description ====== | ====== General description ====== |
| {{indexmenu_n>1}} | {{indexmenu_n>1}} |
| The bandwidth control for subscribers is similar to [[en:dpi:dpi_options:opt_shaping|the overall bandwidth control]]. All options are available: | Subscriber traffic is defined by a list of IP addresses or CIDR. Subscriber traffic can have [[en:dpi:dpi_options:opt_bandwidth_mgmt|]] applied, but it is also subject to the policing of the General or Virtual channel in which the Subscriber resides. For more details, see [[en:dpi:dpi_options:opt_shaping:shaping_description|]]. |
| - 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 [[en:dpi:dpi_options:opt_priority|"Protocol dependent prioritizing of traffic"]]. | Policing is applied to 8 traffic classes, configured via [[en:dpi:dpi_options:opt_priority|]]. |
| Placing of a particular protocol into its class is controlled by the same option: ([[en:dpi:dpi_options:opt_priority:dscp_table|class <-> priority]]). | <note important>The mapping of a protocol to its class is also regulated by the option ([[en:dpi:dpi_options:opt_priority:dscp_table|class <-> priority]]). |
| | This approach makes it possible to combine external and internal policers in a compatible way. |
| | </note> |
| |
| The assignment of traffic control policies for subscribers is supported by [[en:dpi:dpi_components:platform:subscriber_management|Subscriber Management,SM]]. | Two policing mechanisms are available to choose from: |
| | - TBF without hierarchy ([[https://en.wikipedia.org/wiki/Token_bucket|Token Bucket Function]]), used to limit/block a specific policing class. Bandwidth limitation with burst support. |
| | - HTB with hierarchy for 8 classes ([[http://www.opennet.ru/base/net/htb_manual.txt.html|Hierarchical Token Bucket]]), used for prioritization by traffic classes. Bandwidth limitation with borrowing. |
| | |
| | Creation and assignment of policing (tariff plan) is performed via [[en:dpi:dpi_components:platform:subscriber_management| Subscriber Management (SM) commands]]. |
| | |
| | Applying tariff plans to a subscriber is possible either [[en:dpi:dpi_components:platform:dpi_billing|using the PUSH method]] or [[en:dpi:bras_bng:radius_integration:radius_auth_server_integration:radius_auth_response#vasexperts-policing-profile|through RADIUS for BRAS]]. |
| |
| Application of tariff plans per subscriber is possible using the [[en:dpi:dpi_components:platform:dpi_billing|PUSH method]] or via RADIUS for [[en:dpi:bras_bng:general_setup#fastdpi_l3_bras_setup|BRAS L3]] and [[en:dpi:bras_bng:general_setup#fastdpi_l2_bras_setup|BRAS L2]]. | |
| |
