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 ▄
507
synchronization activity will be done by the evlogd of standby SMC/MIO card, as the standby evlogd is less loaded and
the standby card has enough room for synchronization activity. Therefore the performance of the system will not be
affected.
the standby card has enough room for synchronization activity. Therefore the performance of the system will not be
affected.
Zero Volume S-CDR Suppression
This feature is developed to suppress the CDRs with zero byte data count, so that the OCG node is not overloaded with
a flood of CDRs. The CDRs can be categorized as follows:
a flood of CDRs. The CDRs can be categorized as follows:
Final-cdrs: These CDRs are generated at the end of a context.
Internal-trigger-cdrs: These CDRs are generated due to internal triggers such as volume limit, time limit, tariff
change or user generated interims through the CLI commands.
External-trigger-cdrs: These CDRs are generated due to external triggers such as QoS Change, RAT change and
so on. All triggers which are not considered as final-cdrs or internal-trigger-cdrs are considered as external-
trigger-cdrs.
trigger-cdrs.
The customers can select the CDRs they want to suppress. This feature is disabled by default to ensure backward
compatibility.
compatibility.
Modified SGSN Features
This section identifies SGSN features modified in release 15.0.
Important:
Note that the S4 functionality and Location Services funcationality noted below are qualified for Lab
and Field Trial deployments only.
Basic Location Service (LCS) Support
With Release 14.0 SGSN initial support was provided for basic Location Services (LCS) functionality to collect and use
or share location (geographical position) information for connected UEs in support of a variety of location services,
such as location-based charging and positioning services. The SGSN uses the Lg interface to the gateway mobile
location center (GMLC), which provides the mechanisms to support specialized mobile location services for operators,
subscribers, and third party service providers.
or share location (geographical position) information for connected UEs in support of a variety of location services,
such as location-based charging and positioning services. The SGSN uses the Lg interface to the gateway mobile
location center (GMLC), which provides the mechanisms to support specialized mobile location services for operators,
subscribers, and third party service providers.
Use of the Location Services (LCS) feature and the Lg interface is license controlled.
Basic LCS is now fully qualified. With this release, the functionality has been expanded - refer to R7 Location Services
(LCS) - Phase 2.
(LCS) - Phase 2.
The basic feature and configuration were described in the Location Services chapter in the Serving GPRS Support Node
Administration Guide. The commands listed in the configuration chapter (new in Release 14.0) are available in the
Command Line Interface Reference.
Administration Guide. The commands listed in the configuration chapter (new in Release 14.0) are available in the
Command Line Interface Reference.
Checksum Enabled With or With-out Optimization
The S4-SGSN now supports use of
no-optimize
keyword to enable/disable optimization for UDP checksum (refer to
the Command Line Interface Reference for information about the
udp-checksum
command in the GTPU Service
configuration mode).
Previous Behavior: By default, when UDP checksum was enabled, no optimization was attempted.
New Behavior: By default, the S4-SGSN now attempts optimization of UDP checksum in the UDP header of the GTPU
packet. As well, it is now possible for optimization to be enabled or disabled as the S4-SGSN now supports use of the
packet. As well, it is now possible for optimization to be enabled or disabled as the S4-SGSN now supports use of the
no-optimize
keyword.