Cisco Cisco ASR 5000
Serving GPRS Support Node (SGSN) Overview
Features and Functionality ▀
SGSN Administration Guide, StarOS Release 18 ▄
SMS Authentication Repetition Rate
The SGSN provides an authentication procedures for standard GMM events like Attach, Detach, RAU, and Service-
Request, and SMS events such as Activate, all with support for 1-in-N Authenticate functionality. The SGSN did not
provide the capability to authenticate MO/MT SMS events.
Request, and SMS events such as Activate, all with support for 1-in-N Authenticate functionality. The SGSN did not
provide the capability to authenticate MO/MT SMS events.
Now, the authentication functionality has been expanded to the Gs interface where the SGSN now supports
configuration of the authentication repetition rate for SMS-MO and SMS-MT, for every nth event. This functionality is
built on existing SMS CLI, with configurable MO and/or MT. The default is not to authenticate.
configuration of the authentication repetition rate for SMS-MO and SMS-MT, for every nth event. This functionality is
built on existing SMS CLI, with configurable MO and/or MT. The default is not to authenticate.
SMSC Address Denial
Previously, the SGSN supported restricting MO-SMS and MT-SMS only through SGSN operator policy configuration.
Now, the SGSN can restrict forwarding of SMS messages to specific SMSC addresses, in order to allow operators to
block SMS traffic that cannot be charged for. This functionality supports multiple SMSCs and is configurable per
SMSC address with a maximum of 10 addresses. It is also configurable for MO-SMS and/or MT-SMS messages.
block SMS traffic that cannot be charged for. This functionality supports multiple SMSCs and is configurable per
SMSC address with a maximum of 10 addresses. It is also configurable for MO-SMS and/or MT-SMS messages.
Status Updates to RNC
During MMGR recovery due to memory overload or demux migration leads to missing status updates for RNC.As the
result RNC status remains unavailable even when links towards RNC are up. The Session Controller allows the Standby
Session Managers along with Active Session Managers to fetch the status updates.
result RNC status remains unavailable even when links towards RNC are up. The Session Controller allows the Standby
Session Managers along with Active Session Managers to fetch the status updates.
Topology-based Gateway (GW) Selection
Topology-based gateway selection is a mechanism defined by 3GPP to choose a gateway based on the geographical
(topological) proximity of the GGSN to the SGSN or the P-GW to the S-GW. The two being co-located would have the
highest priority. Topology-based selection is not allowed for roamers connected to HPLMN access points (Home
Routed Scenario).
(topological) proximity of the GGSN to the SGSN or the P-GW to the S-GW. The two being co-located would have the
highest priority. Topology-based selection is not allowed for roamers connected to HPLMN access points (Home
Routed Scenario).
DNS S-NAPTR returns a candidate list of GW nodes for each of the DNS queries. 3GPP TS 29.303 provides an
algorithm to feed these candidate lists and choose the topologically closer nodes among them. S-NAPTR DNS query is
supported by default on the S4-SGSN and, with Release 16, can be enabled for the Gn/Gp-SGSN.
algorithm to feed these candidate lists and choose the topologically closer nodes among them. S-NAPTR DNS query is
supported by default on the S4-SGSN and, with Release 16, can be enabled for the Gn/Gp-SGSN.
The SGSN’s Topology-based GW Selection feature supports two levels of sorting, first level is degree and second level
is order/priority, where order is for NAPTR records and priority is for SRV Records. Degree has the highest preference.
is order/priority, where order is for NAPTR records and priority is for SRV Records. Degree has the highest preference.
For details on the use and configuration of this feature, refer to the Topology-based Gateway Selection section in the
SGSN Administration Guide.
SGSN Administration Guide.
Threshold Crossing Alerts (TCA) Support
Thresholding on the system is used to monitor the system for conditions that could potentially cause errors or outage.
Typically, these conditions are temporary (i.e high CPU utilization, or packet collisions on a network) and are quickly
resolved. However, continuous or large numbers of these error conditions within a specific time interval may be
indicative of larger, more severe issues. The purpose of thresholding is to help identify potentially severe conditions so
that immediate action can be taken to minimize and/or avoid system downtime.
Typically, these conditions are temporary (i.e high CPU utilization, or packet collisions on a network) and are quickly
resolved. However, continuous or large numbers of these error conditions within a specific time interval may be
indicative of larger, more severe issues. The purpose of thresholding is to help identify potentially severe conditions so
that immediate action can be taken to minimize and/or avoid system downtime.