Cisco Cisco Packet Data Gateway (PDG)
ECS Changes in Release 17
ECS Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
129
ECS Enhancements for 17.1
This section identifies all of the ECS enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the ECS Administration Guide
for this release.
for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line Interface
Reference for this release.
Reference for this release.
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
CSCul22770 - SFR - PSP algorithm modification
Applicable Products: GGSN, P-GW
Feature Changes
PSP Algorithm Modification
Since Radius selects the policing to be applied including Bandwidth policy, validation of the policy before its
application is critical. In case Bandwidth policy received from RADIUS is invalid, that is, absent in the configuration, a
fallback mechanism is required to select another policy so that subscriber call remains active.
application is critical. In case Bandwidth policy received from RADIUS is invalid, that is, absent in the configuration, a
fallback mechanism is required to select another policy so that subscriber call remains active.
Previous Behavior: A single bandwidth policy was being sent from SM to ECS for validation. When invalid
bandwidth policy was received from RADIUS, call used to get terminated.
bandwidth policy was received from RADIUS, call used to get terminated.
New Behavior: Primary and fallback policies are sent from SM to ECS. When invalid bandwidth policy is received
from RADIUS,
from RADIUS,
When bandwidth policy is configured under APN and fallback mechanism is also enabled, then Bandwidth
policy from APN is applied, if it is valid and call remains active.
When no bandwidth policy is configured under APN or fallback mechanism is disabled under APN
configuration, then Bandwidth policy from Rulebase is applied if it is valid and fallback mechanism is
configured under rulebase and call remains active.
configured under rulebase and call remains active.
In case, both Primary and fallback policies are found to be invalid, the call is terminated.
Customer Impact: This will help to prevent termination of calls when incorrect bandwidth policy is sent through
RADIUS.
RADIUS.
Command Changes
fallback-enabled
A new keyword
fallback-enabled
has been added to the CLI
active-charging bandwidth-policy
to control
the fallback bandwidth mechanism. This keyword fills the bandwidth policy value.
If fallback is enabled, both primary and secondary BW policy is filled with Bandwidth Policy configured in the APN.