Content Filtering Support - Cisco ASR 5000 Series Administration Manual

▀ Enhanced Features and Functionality
 TCP port
 Direction of flow
 Number of flows across system
 Number of flows of a particular type
FBC provides multiple service data flow counts, one each per defined service data flow. When FBC is configured in the
ECS, PDP context online charging is achieved by FBC online charging using only the wildcard service data flow.
When further service data flows are specified, traffic is categorized, and counted, according to the service data flow
specification. You can apply wildcard to service data flow that do not match any of the specific service data flows.
The following are the chargeable events for FBC:
 Start of PDP context—Upon encountering this event, a Credit Control Request (CCR) starts, indicating the start
of the PDP context, is sent towards the Online Charging Service. The data volume is captured per service data
flow for the PDP context.
 Start of service data flow—An interim CCR is generated for the PDP context, indicating the start of a new
service data flow, and a new volume count for this service data flow is started.
 Termination of service data flow—The service data flow volume counter is closed, and an interim CCR is
generated towards the Online Charging Service, indicating the end of the service data flow and the final
volume count for this service data flow.
 End of PDP context—Upon encountering this event, a CCR stop, indicating the end of the PDP context, is sent
towards the Online Charging Service together with the final volume counts for the PDP context and all service
data flows.
 Expiration of an operator configured time limit per PDP context—This event triggers the emission of an
interim CCR, indicating the elapsed time and the accrued data volume for the PDP context since the last report.
 Expiration of an operator configured time limit per service data flow—The service data flow volume
counter is closed and an interim CCR is sent to the Online Charging Service, indicating the elapsed time and
the accrued data volume since the last report for that service data flow. A new service data flow container is
opened if the service data flow is still active.
 Expiration of an operator configured data volume limit per PDP context—This event triggers the emission
of an interim CCR, indicating the elapsed time and the accrued data volume for the PDP context since the last
report.
 Expiration of an operator configured data volume limit per service data flow—The service data flow
volume counter is closed and an interim CCR is sent to the Online Charging Service, indicating the elapsed
time and the accrued data volume since the last report for that service data flow. A new service data flow
container is opened if the service data flow is still active.
 Change of charging condition—When QoS change, tariff time change are encountered, all current volume
counts are captured and sent towards the Online Charging Service with an interim CCR. New volume counts
for all active service data flows are started.
 Administrative intervention by user/service also force trigger a chargeable event.
The file naming convention for created xDRs (EDR/UDR/FDRs) are described in the
section.

Content Filtering Support

ECS provides off-line content filtering support and in-line static and dynamic content filtering support to control static
and dynamic data flow and content requests.
▄ Cisco ASR 5x00 Enhanced Charging Services Administration Guide
36
Enhanced Charging Service Overview
Impact on xDR File Naming