Cisco Cisco Packet Data Gateway (PDG) Manual De Manutenção
New Feature Summary
Generally Available 06-30-2010
1-52
Network-Initiated PDP Context Activation
SGSN now supports standards compliant network-initiated PDP context activation. The
network, or actually the GGSN, is not actually initiating the PDP context activation - it is
requesting the MS/UE to activate the PDP context.
network, or actually the GGSN, is not actually initiating the PDP context activation - it is
requesting the MS/UE to activate the PDP context.
QoS Traffic Policing per Subscriber
The SGSN now offers QoS traffic policing which enables the operator to configure and
enforce bandwidth limitations on individual PDP contexts of a particular traffic class.
Traffic policing typically deals with eliminating bursts of traffic and managing a traffic flow
in order to comply with a traffic contract.
enforce bandwidth limitations on individual PDP contexts of a particular traffic class.
Traffic policing typically deals with eliminating bursts of traffic and managing a traffic flow
in order to comply with a traffic contract.
The SGSN conforms to the DiffServ model for QoS by handling the 3GPP defined classes
of traffic, QoS negotiation, DSCP marking, traffic policing, and support for
HSDPA/HSUPA.
of traffic, QoS negotiation, DSCP marking, traffic policing, and support for
HSDPA/HSUPA.
The SGSN can police uplink and downlink traffic according to predefined QoS negotiated
limits fixed on the basis of individual contexts - either primary or secondary. The SGSN
employs the Two Rate Three Color Marker (RFC2698) algorithm for traffic policing.
limits fixed on the basis of individual contexts - either primary or secondary. The SGSN
employs the Two Rate Three Color Marker (RFC2698) algorithm for traffic policing.
For more information, see the SGSN Overview in the Product Overview and the Traffic
Policing and Shaping and Dynamic QoS Renegotiation chapter in System Enhanced
Feature Configuration Guide.
Policing and Shaping and Dynamic QoS Renegotiation chapter in System Enhanced
Feature Configuration Guide.
Session Recovery Support
The session recovery feature, now available for both 2G and 3G SGSNs, handles SGSN
services for all attached and/or activated subscribers. When enabled, session recovery
provides seamless failover and reconstruction of subscriber session information in the event
of a hardware or software fault within the system preventing a fully connected user session
from being disconnected.
services for all attached and/or activated subscribers. When enabled, session recovery
provides seamless failover and reconstruction of subscriber session information in the event
of a hardware or software fault within the system preventing a fully connected user session
from being disconnected.
This is an enhanced feature and requires a separate license key to be enabled with the SGSN
service. For more information on session recovery, refer to the System Enhanced Feature
Configuration Guide.
service. For more information on session recovery, refer to the System Enhanced Feature
Configuration Guide.
Short Message Service - SMS
The SGSN implements a configurable short message service (SMS) to send and receive 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).
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).
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
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