Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Broadband Subscriber Services User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring Policy and Charging Control Rules

date_range 06-Dec-23

A policy and charging control (PCC) rule defines the treatment to be applied to packets associated with specific applications or to specific service data flows.

You can configure PCC rules for Junos OS Subscriber Aware or for Junos OS Broadband Subscriber Management, but you use a different CLI hierarchy level for each product.

  • If you are using Junos OS Subscriber Aware, configure PCC rules at the [edit unified-edge pcef] hierarchy level.

  • If you are using Junos OS Broadband Subscriber Management, configure PCC rules at the [edit services pcef] hierarchy level.

Note:

If you are using Junos OS Subscriber Aware, you must be in maintenance mode to make a change to a PCC rule. (See Changing PCEF Profiles, PCC Rules, PCC Rulebases, Diameter Profiles, Flow Descriptions, and PCC Action Profiles).

Note:

If you are using Junos OS Broadband Subscriber Management, you cannot change a PCC rule while it is being used by a subscriber. To modify the rule, you must log off the subscribers that are using the rule.

Before you configure PCC rules, you must do the following:

  • Configure the service data flow (SDF) filters that the PCC rules reference.

  • Configure the application groups and any custom applications that you want to reference in application-aware PCC rules.

  • Configure the PCC action profiles that the PCC rules reference.

Note:

When specifying application-aware PCC rules in a PCEF profile, you must also configure a default Layer 3 or Layer 4 wildcard PCC rule to ensure that the default charging characteristics are applied to unmatched subscriber traffic without dropping that traffic. For example, the default Layer 3 or Layer 4 wildcard PCC rule prevents traffic based on DNS queries from being dropped. In addition, the policy (PCEF profile) that includes application-aware PCC rules must also include a wildcard Layer 3 or Layer 4 PCC rule at a lower precedence.

To configure PCC rules:

  1. Specify a name for the PCC rule.

    For Junos OS Subscriber Aware:

    content_copy zoom_out_map
    [edit unified-edge pcef]
    user@host# edit pcc-rules rule-name
    

    For Junos OS Broadband Subscriber Management:

    content_copy zoom_out_map
    [edit services pcef]
    user@host# edit pcc-rules rule-name
    
  2. In a from statement, specify an SDF filter to use Layer 3 or Layer 4 match conditions for filtering subscriber traffic.

    For Junos OS Subscriber Aware:

    content_copy zoom_out_map
    [edit unified-edge pcef pcc-rules  rule-name]
    user@host# set from flows flow-identifier
    

    For Junos OS Broadband Subscriber Management:

    content_copy zoom_out_map
    [edit services pcef pcc-rules  rule-name]
    user@host# set from flows flow-identifier
    

    If you do not want to filter subscriber traffic based on SDF filters, use the any option.

    For Junos OS Subscriber Aware:

    content_copy zoom_out_map
    [edit unified-edge pcef pcc-rules  rule-name]
    user@host# set from flows any
    

    For Junos OS Broadband Subscriber Management:

    content_copy zoom_out_map
    [edit services pcef pcc-rules  rule-name]
    user@host# set from flows any
    
  3. (Optional) Specify an application as a match condition for filtering subscriber traffic.

    For Junos OS Subscriber Aware:

    content_copy zoom_out_map
    [edit unified-edge pcef pcc-rules  rule-name]
    user@host# set from applications application-name
    

    For Junos OS Broadband Subscriber Management:

    content_copy zoom_out_map
    [edit services pcef pcc-rules  rule-name]
    user@host# set from applications application-name
    
  4. (Optional) Specify multiple applications instead of specifying each application separately by specifying an application group as a match condition for filtering subscriber traffic.

    For Junos OS Subscriber Aware:

    content_copy zoom_out_map
    [edit unified-edge pcef pcc-rules rule-name]
    user@host# set from application-groups application-group-name
    

    For Junos OS Broadband Subscriber Management:

    content_copy zoom_out_map
    [edit services pcef pcc-rules rule-name]
    user@host# set from application-groups application-group-name
    
  5. Specify the PCC rules action profile that defines the treatment to be applied to specific service data flows or to packets associated with specific applications.
    Note:

    You can use PCC action profiles with HTTP redirection or HCM profiles only in PCC rules that match only HTTP-based applications and any flows.

    For Junos OS Subscriber Aware:

    content_copy zoom_out_map
    [edit unified-edge pcef pcc-rules rule-name]
    user@host# set then pcc-action-profile profile-name
    

    For Junos OS Broadband Subscriber Management:

    content_copy zoom_out_map
    [edit services pcef pcc-rules rule-name]
    user@host# set then pcc-action-profile profile-name
    
footer-navigation