Cisco Cisco Packet Data Interworking Function (PDIF) Manuale Di Manutenzione
Generally Available 06-30-2010
SGSN Features in Release 8.0
1-53
employ both the Page procedure and MNRG (mobile not reachable for GPRS) flags in an
attempt to deliver messages to subscribers that are absent.
attempt to deliver messages to subscribers that are absent.
The SGSN supports both charging for SMS messages (MO - mobile originating and MT -
mobile terminating) and lawful intercept of SMS-MO and SMS-MT messages.
mobile terminating) and lawful intercept of SMS-MO and SMS-MT messages.
Configuration for the service is explained in the SGSN Administration Guide. The various
CLI used to enable and configure the SMS service are defined in the Command Line
Interface Reference.
CLI used to enable and configure the SMS service are defined in the Command Line
Interface Reference.
CLI
●
SMS is enabled with the
short-message-service
command in the MAP Service
configuration mode. Entering this command accesses the SMS Service configuration
mode with the commands to define the SMS service operational configuration:
mode with the commands to define the SMS service operational configuration:
[cntxt_name]st40(config-map-service-serv_name)# short-message-service
[cntxt_name]st40(config-map-service-serv_name-sms-service)#
HSPA Fallback (aka Data Rate Management per RNC)
Benefits
Configurable control of data rates on a per RNC basis enables operators to allow subscribers
to roam in and out of coverages areas with different QoS levels.
to roam in and out of coverages areas with different QoS levels.
Description
The SGSN can now limit data rates (via QoS) on a per-RNC basis. Some RNCs support
HSPA rates (up to 16 Mbps in the downlink and 8 Mbps in the uplink) and cannot support
higher data rates - such as those enabled by HSPA+ (theoretically, up to 256 Mbps both
downlink and uplink). Being able to specify the QoS individually for each RNC makes it
possible for operators to allow their subscribers to move in-and-out of coverage areas with
different QoS levels, such as those based on 3GPP Release 6 (HSPA) and 3GPP Release 7
(HSPA+).
HSPA rates (up to 16 Mbps in the downlink and 8 Mbps in the uplink) and cannot support
higher data rates - such as those enabled by HSPA+ (theoretically, up to 256 Mbps both
downlink and uplink). Being able to specify the QoS individually for each RNC makes it
possible for operators to allow their subscribers to move in-and-out of coverage areas with
different QoS levels, such as those based on 3GPP Release 6 (HSPA) and 3GPP Release 7
(HSPA+).
For example, when a PDP established on an RNC with 21 Mbps is handed off to an RNC
supporting only 16 Mbps, the end-to-end QoS will be re-negotiated to 16 Mbps. Note that
an MS/UE may choose to drop the PDP during the QoS renegotiation to a lower value.
supporting only 16 Mbps, the end-to-end QoS will be re-negotiated to 16 Mbps. Note that
an MS/UE may choose to drop the PDP during the QoS renegotiation to a lower value.
This data rate management per RNC functionality is enabled, in the RNC configuration
mode, by specifying the type of 3GPP release specific compliance, either release 7 for
HSPA+ rate or pre-release 7 for HSPA rates. For configuration details, refer to the RNC
Configuration Mode chapter in the Command Line Interface Reference (version 8.x).
mode, by specifying the type of 3GPP release specific compliance, either release 7 for
HSPA+ rate or pre-release 7 for HSPA rates. For configuration details, refer to the RNC
Configuration Mode chapter in the Command Line Interface Reference (version 8.x).
Tracking Usage of GPRS Encryption Algorithm
Usage of the GPRS encryption algorithm (GEA) significantly affects the SGSN processing
capacity depending upon the GEAx level used - GEA1, GEA2, or GEA3.
capacity depending upon the GEAx level used - GEA1, GEA2, or GEA3.