Reporting Statistics And Usage To Pcrf; Time And Flow-Based Bearer Charging In Ecs - Cisco ASR 5000 Series Administration Manual

Enhanced Charging Service Overview
indicating the relevant threshold that was crossed. ECS will then disarm the trigger. If the trigger needs to be rearmed,
PCRF will explicitly enable it in the CCA-U message.
Important:
FUP Enforcement for Dynamic Rules
The chassis/PCEF supports dynamic rule installation using 3GPP-standards-based AVPs. The Charging-Rule-Definition
AVP is used to install dynamic rules and configure charging behavior and QoS parameters. For dynamic rules,
charging-action is part of the rule definition, and not a separate named entity. QoS parameters of a dynamic-rule are
changed using the same Charging-Rule-Definition AVP. For dynamic rules, per-service QoS control maps to per-
dynamic-rule QoS-control.
 For dynamic rules, service-level QoS control is supported using 3GPP-Standard AVPs. For hierarchical
enforcement of FUP parameters for a packet matching a dynamic rule, charging-action level parameters are
read from the dynamic rule itself. Hierarchical FUP enforcement will otherwise be similar to that for
predefined rules.
 Dynamic rule has a name associated with it. This name can be added to statically (CLI) defined QoS-group-of-
ruledefs. So, a dynamic rule can be configured to be part of a QoS-group-of-ruledefs. Multiple dynamic rules
can be part of a QoS-group-of-ruledefs. QoS control for a QoS-group-of-ruledefs is transparently enforced,
irrespective of whether constituent ruledefs are static, predefined, or dynamically installed.

Reporting Statistics and Usage to PCRF

The PCEF reports volume usage to the PCRF in CCR-U and RAR messages at the following events:
 Volume threshold for a charging-action is crossed, and an event trigger for that threshold breach is set by the
PCRF.
 Volume threshold for a QoS-group-of-ruledefs is crossed, and an event trigger for that threshold breach is set by
the PCRF.
 A QoS-group-of-ruledefs removed is the last using the shared volume-quota.
Monitoring and reporting of time-usage is not supported in this release. Also, packet drops due to enforcement of FUP-
QoS parameters is not reported in CDR.
Statistics pertaining to FUP enforcement are available through Show CLI commands for all active sessions.

Time and Flow-based Bearer Charging in ECS

ECS supports Time-based Charging (TBC) to charge customers on either actual consumed time or total session time
usage during a subscriber session. TBC generates charging records based on the actual time difference between
receiving the two packets, or by adding idle time when no packet flow occurs.
ECS also supports Flow-based Charging (FBC) based on flow category and type.
PDP context charging allows the system to collect charging information related to data volumes sent to and received by
the MS. This collected information is categorized by the QoS applied to the PDP context. FBC integrates a Tariff Plane
Function (TPF) to the charging capabilities that categorize the PDP context data volume for specific service data flows.
Service data flows are defined by charging rules. The charging rules use protocol characteristics such as:
 IP address
In 14.0 and later releases, Time Reporting over Gx is supported.
Cisco ASR 5x00 Enhanced Charging Services Administration Guide ▄
Enhanced Features and Functionality ▀
35