With the previous
implementation, subscriber bandwidth is limited based on QoS provided by PCRF
in order to comply with 3GPP standards. In this release, subscriber is provided
with unlimited bandwidth by allowing QoS override based on LAC and/or TAC
(individual or range) configured in a local-policy (LP) rule on the gateway. If
the subscriber is in the LAC or TAC region and hits the LP rule, the gateway
ignores the QoS limits imposed by PCRF and allows the subscriber to have
requires the license to configure local-policy. For more information on the
licensing requirements, contact Cisco account representative.
changes are performed at both ECS and local-policy to achieve this
For this feature to
work, the following operations must be performed in the order as specified
subscriber is in the configured RAI or TAI range, the local-policy identifies
the associated local-policy rule and sends the rule to ECS for activation.
ECS provides a
configuration in the service scheme, which matches the active lp-rules
trigger-condition and associates the trigger-action to be taken when a
local-policy rule activation is received. ECS then performs throttle
suppression to provide unlimited bandwidth based on the subscriber location.
service-scheme is associated with the subscriber based on the conditions
configured under subscriber-class at call setup time.
based throttle suppress will override the existing functionality of time based
throttle suppression. Irrespective of the configured time delay, if the
subscriber is in a particular location for which throttle suppression has been
configured then it will hold effect.
Whenever there is
new-call or location-change event, the rulebase is checked for location and the
LP rules to add and delete are passed to ECS module.
By default, the
Change Reporting Action (CRA) notification is sent to MME when ULI-Change,
TAI-Change and/or ECGI-Change are installed as part of actiondef configuration.
New CLI configuration is provided to control the CRA notification towards MME.
The QoS Override
feature can be enabled for subscribers classified based on APN, virtual-APN,
rulebase or a combination of these.
This feature works
in local-policy fallback, dual-policy mode, and dual-fallback modes. In
local-policy fallback mode, irrespective of where the event triggers are being
registered, all the event triggers will be reported to local-policy and the
corresponding actions will be taken. Whereas in the dual-policy and
dual-fallback modes, the event triggers are sent to both local-policy and PCRF
depending on where the triggers are registered. Local-policy module handles all
the location related events and PCRF handles all other event triggers.