Cisco Cisco Mobility Unified Reporting User Guide
Serving GPRS Support Node (SGSN) Overview
▀ Features and Functionality
▄ Cisco ASR 5000 Series Product Overview
982
OL-24419-05
Ensures geographical redundancy, as a pool can be distributed across sites.
Minimizes subscriber impact during service, maintenance, or node additions or replacements.
Increases overall capacity via load sharing across the SGSNs in a pool.
Reduces the need/frequency for inter-SGSN RAUs. This substantially reduces signaling load and data transfer
delays.
Supports load redistribution with the SGSN offloading procedure.
Gb/Iu Flex Offloading
The SGSN supports Gb/Iu Flex subscriber offloading from one SGSN to another specific SGSN in a 2G/3G pool.
In addition, the operator can configure the offloading Target NRI in P-TMSI, and the quantity to offload to the Target.
This can be used to provide load balancing, or to offload a single node in pool, take it out of service for whatever reason
(e.g., maintenance).
In addition, the operator can configure the offloading Target NRI in P-TMSI, and the quantity to offload to the Target.
This can be used to provide load balancing, or to offload a single node in pool, take it out of service for whatever reason
(e.g., maintenance).
Short Message Service (SMS over Gd)
The SGSN implements a configurable Short Message Service (SMS) to support sending and receiving text messages up
to 140 octets in length. The SGSN handles multiple, simultaneous messages of both types: those sent from the MS/UE
(SMS-MO: mobile originating) and those sent to the MS/UE (SMS-MT: mobile terminating). Short Message Service is
disabled by default.
After verifying a subscription for the PLMN’s SMS service, the SGSN connects with the SMSC (short message service
center), via a Gd interface, to relay received messages (from a mobile) using MAP-MO-FORWARD-REQUESTs for
store-and-forward.
to 140 octets in length. The SGSN handles multiple, simultaneous messages of both types: those sent from the MS/UE
(SMS-MO: mobile originating) and those sent to the MS/UE (SMS-MT: mobile terminating). Short Message Service is
disabled by default.
After verifying a subscription for the PLMN’s SMS service, the SGSN connects with the SMSC (short message service
center), via a Gd interface, to relay received messages (from a mobile) using MAP-MO-FORWARD-REQUESTs for
store-and-forward.
In the reverse, the SGSN awaits messages from the SMSC via MAP-MT-FORWARD-REQUESTs and checks the
subscriber state before relaying them to the target MS/UE.
The SGSN will employ both the Page procedure and MNRG (mobile not reachable for GPRS) flags in an attempt to
deliver messages to subscribers that are absent.
The SGSN supports
subscriber state before relaying them to the target MS/UE.
The SGSN will employ both the Page procedure and MNRG (mobile not reachable for GPRS) flags in an attempt to
deliver messages to subscribers that are absent.
The SGSN supports
charging for SMS messages, and
lawful intercept of SMS messages
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.