Cisco Cisco Packet Data Gateway (PDG) Nota De Lançamento
SGSN Changes in Release 15.0
▀ SGSN Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
514
S4-SGSN Support for Fallback to V1 Cause Code in GTPv2 Context Response
Previous Behavior: The SGSN rejects Context Response message with cause code “Fallback to GTP-V1”.
New Behavior: If the SGSN accepts a Context Response message with cause code “Fallback to GTP-V1”, it then
performs a GTP-v1 SGSN Context Request, Context Response and Context Ack with the peer SGSN to obtain the
subscribers MM and PDP contexts.
performs a GTP-v1 SGSN Context Request, Context Response and Context Ack with the peer SGSN to obtain the
subscribers MM and PDP contexts.
Security Modes in MM Context
Previous Behavior: In case of 2G- 4G handover (new node is MME), the SGSN was sending context response with
MM Context Type “105” & Security Mode as “Type 2 - GSM Key,Used Cipher and Quintuplets”. But if the Peer is a
MME, SGSN should send Security Mode as “Type 3" in the Context Response.
MM Context Type “105” & Security Mode as “Type 2 - GSM Key,Used Cipher and Quintuplets”. But if the Peer is a
MME, SGSN should send Security Mode as “Type 3" in the Context Response.
New Behavior: In the above mentioned scenario, the SGSN now sends context response with MM Context Type “106”
and Security Mode “Type 3 - UMTS Key and Quintuplets”.
and Security Mode “Type 3 - UMTS Key and Quintuplets”.
Separate Statistics for Supplementary Services
Previous Behavior: The Supplementary Service Statistics messages are displayed as a part of the show command
show
gmm-sm statistics
.
New Behavior: New show and clear commands have been added to display and clear Supplementary Service
Information. Counters related to Supplementary Service are removed from the show command
Information. Counters related to Supplementary Service are removed from the show command
show gmm-sm
statistics
.
SGSN Allows Re-configuration of Mode For Peer-Server
Previous Behavior: The mode under Peer-Server configuration is not re-configurable.
New Behavior: The mode under Peer-Server configuration is re-configurable as long as routing context is not
configured.
configured.
SGSN Support of LLC UI PDU (TOM 8 sapi)
Previous Behavior: There was no support for TOM8 SAPI in LLC messages.
New Behavior: TOM8 SAPI is implemented to support LCS in 2G. BSSGP messages are also implemented .
SM Cause ‘Collision with network initiated request’
In compliance with changes to 3GPP specifications, all forms of the SGSN now support the SM cause “Collision with
network initiated request".
network initiated request".
Previous Behavior: SM cause “Collision with network initiated request" was not supported.
New Behavior: On receiving a corresponding EGTP cause in an EGTP message by SGSN, the SGSN will map the
EGTP cause to the SM cause "Collision with network initiated request". New stats, listed under Performance Indicator
Changes, have been added to track mapping to this SM cause.
EGTP cause to the SM cause "Collision with network initiated request". New stats, listed under Performance Indicator
Changes, have been added to track mapping to this SM cause.
SRNS Relocation Feature Enhancement
Previous Behavior: The SGSN did not support Intra-SRNS relocation if the source-rnc itself was behaving as the
target-rnc.
target-rnc.
New Behavior: The software has been enhanced so that the SGSN now can be configured to support Intra-SRNS
relocation if the source-rnc itself is behaving as the target-rnc.
relocation if the source-rnc itself is behaving as the target-rnc.