Cisco Cisco ASR 5000
Serving GPRS Support Node (SGSN) Overview
▀ Features and Functionality
▄ SGSN Administration Guide, StarOS Release 18
Location Services
LoCation Services (LCS) on the SGSN is a 3GPP standards-compliant feature that enables the SGSN 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.
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 this
feature and the Lg interface is license controlled. This functionality is supported on the 2G and 3G SGSN.
support specialized mobile location services for operators, subscribers, and third party service providers. Use of this
feature and the Lg interface is license controlled. This functionality is supported on the 2G and 3G SGSN.
For details about basic location services and its configuration, refer to the Location Services section of the SGSN
Administration Guide.
Administration Guide.
With Release 15.0, supported functionality has expanded to include:
Mobile terminating deferred location requests are now supported
Mobile originating requests are now supported, both immediate and deferred
Differences between 2G and 3G LCS call flows are eliminated
Important:
With this release, expanded functionality for this feature is qualified for lab and field trials only.
Lock/Shutdown the BSC from the SGSN
When the SGSN returns to Active state, after scenarios such as rebooting or reloading, all the BSCs that had been
connected to the SGSN would attempt to re-establish connections. This could result in two serious problems for
operators:
connected to the SGSN would attempt to re-establish connections. This could result in two serious problems for
operators:
1. High CPU usage in the SGSN where too many BSC/RNCs were connected.
2. Network overload when other network nodes cannot match the SGSN's capacity.
2. Network overload when other network nodes cannot match the SGSN's capacity.
The SGSN now supports a Lock/Shutdown feature that provides a two prong solution. CPU Usage Solution: Staggering
the BSC auto-learning procedures when the SGSN re-loads will help to reduce the high CPU usage. This can be
achieved by the operator locking the NSE/BSCs from the SGSN before reboot/reload and then unlocking them one-by-
one to avoid high CPU usage.
the BSC auto-learning procedures when the SGSN re-loads will help to reduce the high CPU usage. This can be
achieved by the operator locking the NSE/BSCs from the SGSN before reboot/reload and then unlocking them one-by-
one to avoid high CPU usage.
Network Overload Solution: A new timer, SNS-GUARD, has been added to clean-up resources if the SNS procedure
does not complete properly, whether or not the BSC is administratively locked. Now the SGSN starts this timer after
sending SNS-SIZE-ACK and the BSC information will be removed, if the auto-learning clean-up procedure does not
complete before the timer expires.
does not complete properly, whether or not the BSC is administratively locked. Now the SGSN starts this timer after
sending SNS-SIZE-ACK and the BSC information will be removed, if the auto-learning clean-up procedure does not
complete before the timer expires.
A series of new commands and keywords has been added to enable the operator to configure this new administrative
Lock/Shutdown the BSC functionality as part of 'interface management' configuration. For details, refer to the SGSN
Global Interface Management section of the Command Line Interface Reference.
Lock/Shutdown the BSC functionality as part of 'interface management' configuration. For details, refer to the SGSN
Global Interface Management section of the Command Line Interface Reference.
Management System Overview
The system's management capabilities are designed around the Telecommunications Management Network (TMN)
model for management - focusing on providing superior quality network element (NE) and element management system
(Web Element Manager) functions. The system provides element management applications that can easily be integrated,
using standards-based protocols (CORBA and SNMPv1, v2), into higher-level management systems - giving wireless
operators the ability to integrate the system into their overall network, service, and business management systems. In
addition, all management is performed out-of-band for security and to maintain system performance.
model for management - focusing on providing superior quality network element (NE) and element management system
(Web Element Manager) functions. The system provides element management applications that can easily be integrated,
using standards-based protocols (CORBA and SNMPv1, v2), into higher-level management systems - giving wireless
operators the ability to integrate the system into their overall network, service, and business management systems. In
addition, all management is performed out-of-band for security and to maintain system performance.