Cisco Cisco IOS Software Release 12.3(8)XU 集約されたデータ

Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com

Page 3 of 10

RADIUS Support

Configurable Radius Attribute for Backward Compatibility: GGSN needs to allow configuration of the RADIUS attributes for MSISDN and the

Account Session ID for a user to be able to support backward compatibility with WAP.

APN Based Features

•

Mapping Multiple APNs to a Single VRF: GGSN 5.0 needs to support more than one APN per VRF. The maximum number of APNs

per VRF need to be clearly documented in the SFS and the product bulletin and other customer documentation.

•

Enabling Charging per APN: GGSN 5.0 should allow enabling/ disabling of generation of CDRs per APN. This is the same feature

which is part of the Charging enhancements.

•

Rate Limit for users per APN: This feature should allow a controlled distribution of bandwidth per APN. Some APNs may be

recognized as those used for bandwidth intensive applications such as music mp3 hosts or others where image files or large file sizes

are involved. The GGSN is configurable on a per APN basis to restrict the transfer rate per subscriber to an operator defined limit that

would reduce the chance of a GGSN from being congested and thereby increase its availability. This is also part of the CAC and per

PDP policing feature suite.

Security Enhancements

Support of Multiple Trusted PLMN IDs: Access to certain partner roaming MSs should be allowed and by default other roamers should be

blocked on an APN basis. This allows the operators to provision access based on partner agreements. GGSN needs to allow more than one

trusted PLMN Id. This is for operators forming multiple alliances and they do not want the MSs from their partners to be blocked because they

do not belong to the home PLMN that the GGSN belongs to. This feature should allow the operator to configure multiple trusted MCC/MNCs.

Operation, Maintenance Features

•

Maintenance Mode: GGSN needs to allow key APN configuration when there are active PDP contexts. GGSN should allow the

operators to change the APN configuration in real-time, without tearing down any active PDP contexts on that APN. Example: This

is a big issue for VF, Spain, for Parking meters where new PDP requests keep coming in even as the old ones are being torn down for

maintenance purposes. They have 400 parking machines that use an APN, to change the APN, they must delete all PDP contexts, but

as soon as they delete them the machines restart the PDP contexts, so there is a very short time they can change the APN, they end up

having to unplug the cable or reboot, which is equivalent to loss of revenue.

•

Prevent Generation of CDRs for active PDP contexts: This was a request from Amena, Spain. Deactivation of generation of G-CDRs

for an active PDP context. Customers should be able to stop generation of G-CDRs when a PDP context is active without tearing

down the PDP context to be able to do this. This is related to the above maintenance mode feature for allowing key APN

configuration for active PDP contexts.

Policy Enforcement/IMS Enabling Features

•

UMTS CAC: UMTS Call Admission Control is used by the GGSN admission decisions based on the network resource availability

and the policy set by the PDF in case of IMS subsystem implementation. It can also downgrade a service if the policy parameters

from PDF do not match those from the SGSN. CAC is based on the parameters configured in the APN, such as max activated PDP,

max bitrate, guaranteed bitrate, etc., and bandwidth allocated to a particular traffic class the PDP belongs to.