Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
SGSN Changes in Release 15.0
SGSN Enhancements for October 31, 2014 ▀
Cisco ASR 5x00 Release Change Reference ▄
469
New Behavior: The following defines how the SGSN now handles a duplicate primary Activation Request received
during deactivation of a duplicate PDP context:
during deactivation of a duplicate PDP context:
if the new (duplicate) Activation Request is a primary and if the duplicate PDP context is a primary/bundle PDP
context or a secondary PDP context, then the deactivation PDP context procedure continues and completes
before the new primary PDP activation proceeds.
before the new primary PDP activation proceeds.
Note that the behavior has not changed if the new (duplicate) Activation Request is secondary and:
If the duplicate PDP context is primary, then the new (duplicate) PDP Activation Request is rejected.
If the duplicate PDP context is secondary and also the bundle is under deactivation, then the SGSN sends SM-
STATUS.
If the duplicate PDP context is secondary, then the deactivation completes and the new secondary PDP
Activation Request is processed.
Note that ‘deactivation complete’ means the PDP context cleanup has occurred locally and disassociated the DPC
towards the GGSN.
towards the GGSN.
Impact on Customer: Duplicate PDP Activation Requests will be processed and sessions will be established by
contacting the GGSN identified in the PDP Activation Requests received during the deactivation stage.
contacting the GGSN identified in the PDP Activation Requests received during the deactivation stage.
CSCup14871 - Addition of logs/stats to analyze the call distribution issue.
Feature Changes
Analyzing Call Distribution Issues
New Behavior: New statistics were added for internal debugging purposes. These statistics are not available for
customer use.
customer use.
CSCup23087, CSCup94308 - Assertion failure with Invalid/unhandled event
PMM_EVT_SM_INC_HO_COMP
Feature Changes
Reaction to RNC Overload during SRNS
New Behavior: The RNC overload-action functionality has been enhanced so that it is now possible to configure the
SGSN to reject SRNS (RANAP Relocation-Required and GTP Forward-Relocation Request messages) if the target
RNC is in overload at a specified traffic level. This keyword setting is effective for both Inter-SGSN SRNS and Intra-
SGSN SRNS.
SGSN to reject SRNS (RANAP Relocation-Required and GTP Forward-Relocation Request messages) if the target
RNC is in overload at a specified traffic level. This keyword setting is effective for both Inter-SGSN SRNS and Intra-
SGSN SRNS.
will be rejected by SGSN if the target RNC is overloaded.
Command Changes
overload-action disable srns