====== General description ======
{{indexmenu_n>1}}
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|]].

Policing is applied to 8 traffic classes, configured via [[en:dpi:dpi_options:opt_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>

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]].