Cisco Cisco Packet Data Gateway (PDG) Manual De Mantenimiento
New Feature Summary
Generally Available 06-30-2010
1-58
Limiting Iu Connections in RANAP Messages
A new command has been created to enable the operator to further control message length
by configuring the number of
by configuring the number of
IuConIDs
sent in each SGSN Init Reset Resource message.
This change will have no impact on current or future configurations as the previously coded
system value was 250.
system value was 250.
Refer to the RNC Configuration Mode chapter of the Command Line Interface Reference
for additional information.
for additional information.
Local QoS Capping
The operator can configure a cap or limit for the QoS bit rate.
The SGSN can now be configured to cap the QoS bit rate parameter when the subscribed
QoS provided by the HLR is lower than the locally configured value.
QoS provided by the HLR is lower than the locally configured value.
Depending upon the keywords included in the command, the SGSN can: take the QoS
parameter configuration from the HLR configuration. take the QoS parameter configuration
from the local settings for use in the APN policy. during session establishment, apply the
lower of either the HLR subscription or the locally configured values.
parameter configuration from the HLR configuration. take the QoS parameter configuration
from the local settings for use in the APN policy. during session establishment, apply the
lower of either the HLR subscription or the locally configured values.
Refer to the SGSN APN Policy Configuration Mode chapter of the Command Line Interface
Reference for the qos command.
Reference for the qos command.
Multiple PLMN Support (2.5G only)
With this new feature, the 2.5G SGSN supports cell-sites with more than one PLMN-ID.
Operators can now assign a different PLMN-ID to each cell in the network (typically, there
are no more than 3 or 4 PLMN-IDs in a single network). This multiple PLMN support also
enables an operator to 'hire out' their infrastructure to other operators who wish to use their
own PLMN-IDs. Each cell can be part of only one PLMN (one GRPS service). By
configuring the GPRS service for each PLMN-ID, this feature allows the 2.5G SGSN to
perform handovers between the service instances.
Operators can now assign a different PLMN-ID to each cell in the network (typically, there
are no more than 3 or 4 PLMN-IDs in a single network). This multiple PLMN support also
enables an operator to 'hire out' their infrastructure to other operators who wish to use their
own PLMN-IDs. Each cell can be part of only one PLMN (one GRPS service). By
configuring the GPRS service for each PLMN-ID, this feature allows the 2.5G SGSN to
perform handovers between the service instances.
Configuring Multiple PLMN Support:
The 2.5G SGSN supports MS handover from one PLMN to another PLMN by configuring
multiple instances of the GPRS service, each with a different PLMN-ID, in the same
context. Each of the GPRS services must use the same MAP, SGTPU and GS services so
these only need to be defined one-time per context. For command details, refer to the GPRS
Service Configuration Mode and MAP, SGTP, and GS Service Configuration Mode chapters
in the Command Line Interface Reference.
multiple instances of the GPRS service, each with a different PLMN-ID, in the same
context. Each of the GPRS services must use the same MAP, SGTPU and GS services so
these only need to be defined one-time per context. For command details, refer to the GPRS
Service Configuration Mode and MAP, SGTP, and GS Service Configuration Mode chapters
in the Command Line Interface Reference.
To enable appropriate S-CDR generation in a multiple PLMN-ID scenario, use the
plmn-id-change
keyword for the
gtpp trigger
command in the GTPP Group
Configuration Mode also documented in the CLI Reference.