Cisco Cisco Packet Data Interworking Function (PDIF) Documentation Roadmaps
Enhanced Charging Service Overview
▀ How ECS Works
▄ Cisco ASR 5000 Series Product Overview
OL-22938-01
Charging Ruledefs and the Charging Engine
This section describes details of how charging ruledefs are applied to the output from the Protocol Analyzer Stack.
The following figure and the steps that follow describe the process of charging ruledefs and charging engines.
Figure 180. Charging Ruledefs and Charging Engine
ruledef
Priority
. . .
Logical Expression
Boolean Expression
Logical Operator
+
+
Value
Logical
Expression
&
&…
Protocol field
(e.g. HTTP.URL, MMS.From, etc.)
Protocol State
(e.g. TCP.State, HTTP.State, etc.)
ruledef
Priority 1
Priority 2
Content ID
Usage
(e.g. IP, HTTP, TCP, UDP)
redirect-to
edr-type
Priority n
(rule-application charging)
(=, !=, endsWith,
startsWith, contains,…)
Charging Engine
block
Xmit
redirect
EDR
Redirection
data flow from
packet inspection
packet inspection
matched
ruledef with
highest priority
1
2
UDR
Step 1
In the Classification Engine, the output from the deep-packet inspection is compared to the charging ruledefs. The
priority configured in each charging ruledef specifies the order in which the ruledefs are compared against the packet
inspection output.
priority configured in each charging ruledef specifies the order in which the ruledefs are compared against the packet
inspection output.
Step 2
When a field or state from the output of the deep-packet inspection matches a field or state defined in a charging
ruledef, the ruledef action is applied to the packet. Actions can include redirection, charge value, or billing record
emission. It is also possible that a match does not occur and no action will be applied to the packet at all.
ruledef, the ruledef action is applied to the packet. Actions can include redirection, charge value, or billing record
emission. It is also possible that a match does not occur and no action will be applied to the packet at all.
Group-of-Ruledefs
Group-of-Ruledefs enable grouping ruledefs into categories. When a group-of-ruledefs is configured in a rulebase, if
any of the ruledefs within the group matches, the specified charging-action is performed, any more action instances are
not processed.
any of the ruledefs within the group matches, the specified charging-action is performed, any more action instances are
not processed.
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, then the group will be optimized.
the ruledefs in the group-of-ruledefs can be optimized, and if the group is included in a rulebase that has optimization
turned on, then the group will be optimized.