Support For Service-Based Qos - Cisco ASR 5000 Series Administration Manual

Enhanced Charging Service Overview
 Flow-Rate: Specifies max rate, max burst-size, conform action, and exceed action; individually for
 Volume Threshold: Thresholds are set for usage monitoring. PCRF can set threshold for a monitoring
 Flow-Status and Flow-Rate can be statically defined for a charging action, and thus applied to a ruledef. These
parameters may be over-ridden by PCRF over Gx. Volume-Threshold-Key (monitoring key) can be statically
defined for a ruledef in a rulebase. However, its value — the volume quota — can only be set over Gx.
Parameters set over Gx will always take precedence over any static configuration.

Support for Service-based QoS

As explained earlier, a service can be mapped in ECS to a set-of-ruledefs with the same charging-action applied to them.
This section explains the support for QoS control at the charging-action level:
 Flow-Status: In ECS, you can configure a flow-action in a charging-action. If flow-action is not configured for a
charging-action, it implies "Forward" action.
 Flow-Rate: ECS charging-action supports configuration of bandwidth limits for a flow. Flow limits can be
separately configured for uplink and downlink. ECS supports configuration of peak data-rate and burst-size as
well as committed data-rate and burst-size, along with corresponding exceed actions. Specification of
committed rate and burst-size is optional.
ECS does not support specifying conform-action (i.e. conform-action is always "Allow"). For exceeding traffic
it supports only "Drop" and "Set IP-TOS to 0" as actions. In ECS, traffic matching a flow — both conforming
and exceeding, cannot be marked with a specific DSCP mark.
In ECS, charging-action also contains a Content-Id. Multiple charging-actions can contain the same Content-
Id. ECS supports a bandwidth-limiting meter per charging action per subscriber session. This metering is
separate from traffic meters that are keyed on Content-Id.
 Volume Thresholds: ECS supports setting and monitoring Volume Threshold per flow using the "monitoring-
key" mechanism. Monitoring-key is specified in a rulebase configuration. Monitoring-key is associated with a
volume-threshold, which is set over Gx. A single monitoring-key can be specified for multiple ruledefs. This
allows sharing of assigned volume quota across all the ruledefs with the same Monitoring-Key ID. To
Important:
Important:
uplink and downlink traffic.
key, which is statically defined for a charging-action using CLI. Usage is reported when thresholds are
crossed, and at predefined events such as session termination and removal of QoS-group-of-ruledefs.
Important:
Triggers for threshold breached are same as the usage-reporting for static charging-action.
Important:
Time-Monitoring over Gx is not supported in this release.
Important:
Flow-Status value of "Append-Redirect" is not supported by ECS.
ECS does not support the Append-Redirect option.
Block can be for uplink, downlink, or both uplink and downlink traffic.
Monitoring-key is not received over Gx for static charging-action.
Cisco ASR 5x00 Enhanced Charging Services Administration Guide ▄
Enhanced Features and Functionality ▀
33