Cisco Cisco Packet Data Interworking Function (PDIF) Notas De La Versión
ECS Changes in Release 15.0
▀ ECS Enhancements for April 15, 2014
▄ Cisco ASR 5x00 Release Change Reference
144
ECS Enhancements for April 15, 2014
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 Enhanced Charging Services
Administration Guide for this release.
Administration Guide for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the ASR 5x00 Command Line
Interface Reference for this release.
Interface 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 ASR 5x00 Statistics and
Counters Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the ASR 5x00 Statistics and
Counters Reference for this release.
CSCuj77690 - Session Recovery Improvements for GGSN and PGW
Applicable Products: GGSN, P-GW
Feature Changes
Session Recovery Improvements
Previous Behavior: There were only 10 PCC rules that were recovered per bearer in the event of a session manager
crash.
crash.
New Behavior: In this release, this limit has been increased to 24. That is, up to 24 PCC rules can be recovered post
ICSR.
ICSR.
With the increase in the limit of PCC rules that can be recovered, the rules are not lost and hence the charging applied to
the end users are not impacted.
the end users are not impacted.
CSCul61892 - Ran b/w optimization performed for flow-status other than
DISABLED
Applicable Products: P-GW
Feature Changes
RAN Bandwidth Optimization for Uni-directional Flows
Previous Behavior: The rules with flow-status = ENABLE_UPLINK and ENABLE_DOWNLINK were treated
similar to the rules with flow-status = DISABLED when the CLI command
similar to the rules with flow-status = DISABLED when the CLI command
ran bandwidth optimize
was
configured under rulebase configuration mode. This resulted in allocating lesser bandwidth to the subscriber call.
New Behavior: Rules with flow-status = ENABLE_UPLINK and ENABLE_DOWNLINK are now treated similar to
the rules with flow-status = ENABLED, thus resulting in sufficient RAN bandwidth allocation for the bearer.
the rules with flow-status = ENABLED, thus resulting in sufficient RAN bandwidth allocation for the bearer.
Customer Impact: Subscriber calls with bearers containing rules with uni-directional flows will now see sufficient
RAN bandwidth allocated for them.
RAN bandwidth allocated for them.