Setting the Precedence Range

When overlapping policy and charging control (PCC) quality of service (QoS) rules apply to the same Gx or Gxx Diameter session, precedence is applied to determine which rule is installed on the gateway. In the case of an overlap, the rule with the lower precedence value is installed. Some vendor gateways require unique precedence, or else reject rules. You can configure MPE devices to maximize the probability that all rules have unique PCC rule precedences. This is a global configuration setting that affects all MPE devices managed by this CMP system.
Note: This does not guarantee rule precedence uniqueness. Operator-defined rules are not validated to ensure precedence uniqueness; if you define such rules, you must track their precedence values yourself.

To set the precedence range:

  1. From the Global Configuration section of the navigation pane, select Global Configuration Settings.

    The content tree displays a list of global configuration settings.

  2. From the content tree, select the Precedence Range group.

    The Precedence Range Configuration page opens in the work area.

  3. Click Modify.

    The fields become editable.

  4. Enter values for the configuration attributes:
    1. AF-Triggered — Enter the minimum and maximum values for rules triggered by Rx requests. The default range is 400 to 899.
    2. UE-Triggered — Enter the minimum and maximum values for rules triggered by user equipment-initiated resource requests. This range cannot overlap with the AF range. The default range is 1000 to 1999.
    3. Default Session — If no other rules are installed when a Gx eHRPD, E-UTRAN, or GPRS session is established, a default rule is installed. Enter the default session precedence. The default precedence is 3000.
  5. Click Save.
The reserved precedence ranges are configured.
Precedence values not set aside here are available for your use in defining rules. By default, you can use:
  • 0–399
  • 900–999
  • 2000–2999
  • 301–4,294,967,295
Note: Range changes do not automatically redeploy rule with new precedence values. Also, range changes do not automatically cause the validation of defined traffic profiles.

When traffic profiles are imported, they are imported regardless of their configured precedence values. The CMP system displays a message reminding you to check the precedence values of the imported traffic profiles.

Parent topic: Global Configuration