Cisco ASR 5000 Series Administration Manual page 26

▀ Basic Features and Functionality
 Deletion of ruledefs must be done during low load times. As described earlier, it is highly
Group of Ruledefs
Group-of-Ruledefs enable grouping ruledefs into categories. When a group-of-ruledefs is configured in a rulebase and
any of the ruledefs within the group matches, the specified charging-action is applied and action instances are not
processed further.
A group-of-ruledefs may contain optimizable ruledefs. Whether a group is optimized or not is decided on whether all
the ruledefs in the group-of-ruledefs can be optimized, and if the group is included in a rulebase that has optimization
turned on.
When a new ruledef is added, it is checked if it is included in any group-of-ruledefs, and whether it requires
optimization.
The group-of-ruledefs configuration enables setting the application for the group (group-of-ruledefs-application
parameter). When set to gx-alias, the group-of-ruledefs is expanded only to extract the rule names out of it (with their
original priority and charging actions) ignoring the field priority set within the group. This is just an optimization over
the PCRF to PCEF interface where a need to install/remove a large set of predefined rules at the same time exists.
Though this is possible over the Gx interface (with a limit of 256), it requires a large amount of PCRF resources to
encode each name. This also increases the message size.
This aliasing function enables to group a set of ruledef names and provides a simple one-name alias that when passed
over Gx, as a Charging-Rule-Base-Name AVP, is expanded to the list of names with each rule being handled
individually. From the PCEF point of view, it is transparent, as if the PCRF had activated (or deactivated) those rules by
naming each one.
In 14.1 and earlier releases, a maximum of 128 ruledefs can be added to a group-of-ruledefs, and a maximum of 64
group-of-ruledefs can be configured.
In 15.0 and later releases, a maximum of 128 ruledefs can be added to a group-of-ruledefs, and a maximum of 128
group-of-ruledefs can be configured.
Rulebase
A rulebase allows grouping one or more rule definitions together to define the billing policies for individual subscribers
or groups of subscribers.
A rulebase is a collection of ruledefs and their associated billing policy. The rulebase determines the action to be taken
when a rule is matched. A maximum of 512 rulebases can be specified in the ECS service.
It is possible to define a ruledef with different actions. For example, a Web site might be free for postpaid users and
charge based on volume for prepaid users. Rulebases can also be used to apply the same ruledefs for several subscribers,
which eliminate the need to have unique ruledefs for each subscriber.
Rulebase List
A rulebase list allows grouping one or more rulebases together, enabling the Online Charging System (OCS) to choose
the rulebase for a subscriber from the rulebase list.
A rulebase list enables a list of rulebases to be sent to the OCS over the Gy interface using a buffer. The OCS can then
select a specific rulebase from the rulebase list, and apply the ruledefs and billing policies associated with that rulebase
to subscribers.
▄ Cisco ASR 5x00 Enhanced Charging Services Administration Guide
26
recommended that ruledefs be added, modified, or deleted in bulk, as it results in optimization engine
updates.
Enhanced Charging Service Overview