Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Understanding PCC Rules for Subscriber Management

Note:

Starting in Junos OS Release 19.3R2, PCC rules are also supported if you have enabled Next Gen Services on the MX240, MX480 or MX960 router with the MX-SPC3 card.

Policy and charging control (PCC) rules define the treatment to apply to subscriber traffic based on the application being used by the subscriber (for example, Facebook) or based on the Layer 3 and Layer 4 service data flow (SDF) information for the IP flow (for example, the source and destination IP addresses). You configure PCC rules, and PCC rules are then activated by either the subscriber’s dynamic profile or by a PCRF. PCC rules include the following components:

Application Filters

Applications and application groups are specified in the from clause of a PCC rule to identify IP packets belonging to a specific application. If the IP packet is for an application identified in a PCC rule, the treatment specified in the PCC action profile in the then clause of the rule is applied.

To configure application-aware PCC rules, you can specify one or more of the following parameters:

  • application—Specifies the name of an application. This can be a Layer 7 protocol (for example, HTTP) or a particular application running on a Layer 7 protocol, such as Facebook and Yahoo Messenger.

  • application-group—Specifies the name of an application group, which represents a collection of Layer 7 applications that can be processed at the same time.

Note:

Application-aware PCC rules that reference specified applications can include wildcard or specific Layer-3 SDF filters, Layer-4 SDF filters, or both.

You can see a list of all the applications and application groups by using the show services application-identification application command. To configure a custom application, see Configuring Custom Application Signatures.

Service Data Flow Filters

SDF filters (flow identifiers) are specified in the from clause of a PCC rule to identify IP packets belonging to a particular Layer 3 or Layer 4 service data flow. If the IP packet matches the SDF filter in a PCC rule, the treatment specified in the PCC action profile in the then clause of the rule is applied.

To configure Layer 3 or Layer 4 SDF filters, you specify one or more of the following parameters:

  • Source IP address

  • Destination IP address

  • Source port

  • Destination port

  • Layer 4 protocol (UDP or TCP)

PCC Action Profiles

A PCC rule configuration includes an action profile in the then clause that defines the treatment to apply to a packet belonging to an application or to an SDF identified in the from clause of the rule. You can configure a PCC action profile that is used in one or more PCC rules to provide the following functionality:

  • HTTP redirection—Specifies HTTP redirection to a URL. You can use this action only for PCC rules that match only HTTP-based applications and all flows.

  • HTTP Steering path—Specifies an IPv4 or IPv6 address for steering HTTP packets. You can use this action only for PCC rules that match only HTTP-based applications and all flows.

    Note:

    A single PCC rule can support either HTTP redirection or HTTP steering path, but not both.

  • Steering with a routing instance—Specifies a routing instance for steering of packets. You can configure different routing instances for traffic from the subscriber (uplink) and traffic to the subscriber (downlink).

  • Forwarding class—Specifies the forwarding class that you want assigned to the packet.

  • Maximum bit rate—Specifies the maximum bit rate for uplink and for downlink traffic.

  • Gating status—Specifies whether to block or to forward IP packets.

Related Documentation