Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
SGSN Changes in Release 15.0
▀ SGSN Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
502
UL-UNITDATA message:
Redirect Attempt Flag
IMSI
Unconfirmed Send State variable
Direct Tunnel Support on S4-SGSN
Direct tunnelling of user plane data between the RNC and the S-GW can be employed to scale UMTS system
architecture to support higher traffic rates. The direct tunnel (DT) approach optimizes core architecture without impact
to UEs and can be deployed independently of the LTE/SAE architecture.
architecture to support higher traffic rates. The direct tunnel (DT) approach optimizes core architecture without impact
to UEs and can be deployed independently of the LTE/SAE architecture.
SGSN always supported DT in the 3G Gn/Gp SGSN and now DT support is added to the S4-SGSN to enable the
establishment of a direct tunnel over the S12 interface between an RNC and an S-GW in a PS domain under a range of
scenarios, such as (but not limited to):
establishment of a direct tunnel over the S12 interface between an RNC and an S-GW in a PS domain under a range of
scenarios, such as (but not limited to):
Primary PDP activation
Secondary PDP activation
Service Request Procedure
Intra SGSN Routing Area Update without SGW change
Intra SGSN Routing Area Update with SGW change
Intra SGSN SRNS relocation without SGW change
Intra SGSN SRNS relocation with SGW change
Network-Initiated PDP Activation
The following scenarios (and others) exhibit procedural differences when an S4-SGSN DT is established:
RAB Release
Iu Release
Error Indication from RNC
For a complete list of scenarios and a fuller description of this feature and its configuration requirements, refer to the S4-
SGSN Direct Tunnel Solution chapter in the Serving GPRS Support Node Administration Guide
SGSN Direct Tunnel Solution chapter in the Serving GPRS Support Node Administration Guide
EDR Enhancements
A new event-logging handle has been introduced. In earlier releases the EDR module was used for event logging
purpose, from this release onwards CDR_MODULE_EVENT_RECORD is used instead of CDR_MODULE_EDR. In
Release 12.0, for generating event logs the SGSN re-used the existing ‘EDR” module which is primarily used for
charging records. But from Release 15.0 onwards, the session-event module will be used by SGSN for event logging.
The CLI options present under the EDR Module are also present under the Session Event Module.
purpose, from this release onwards CDR_MODULE_EVENT_RECORD is used instead of CDR_MODULE_EDR. In
Release 12.0, for generating event logs the SGSN re-used the existing ‘EDR” module which is primarily used for
charging records. But from Release 15.0 onwards, the session-event module will be used by SGSN for event logging.
The CLI options present under the EDR Module are also present under the Session Event Module.
Enhancement to S4-SGSN Statistics
A new counter has been added to the output of the
show s4-sgsn statistics
command. This counter increments
when a PDP is removed upon receiving a Delete Bearer Request (DBR) from a New SGW during Intra-SRNS
relocation. This scenario can occur if the DBR is initiated from a New SGW before a Modify is received at its end.
relocation. This scenario can occur if the DBR is initiated from a New SGW before a Modify is received at its end.
Expanded LCS Support