GGSN Configuration Example


GGSN Configuration Example
 
This chapter provides information for configuring the system to function as a Gateway GPRS Support Node (GGSN) in General Packet Radio Service (GPRS) or Universal Mobile Telecommunications System (UMTS) wireless data networks.
Important: This chapter does not discuss the configuration of the local context. Information about the local context can be found in the Command Line Interface Overview chapter of the System Administration Guide and the Command Line Interface Reference.
The most simple configuration that can be implemented on the system to support GGSN functionality requires that two contexts (one source and one destination) be configured on the system as shown in the following figure.
The source context facilitates the following:
 
The destination context facilitates the following:
 
This configuration supports IP (transparent and non-transparent) and PPP PDP contexts as well as network requested PDP contexts.
GGSN Support Using a Single Source and Destination Context
Information Required
The following sections describe the minimum amount of information required to configure and make the GGSN operational on the network. To make the process more efficient, it is recommended that this information be available prior to configuring the system.
There are additional configuration parameters that are not described in this section. These parameters deal mostly with fine-tuning the operation of the GGSN in the network. Information on these parameters can be found in the appropriate sections of the Command Line Reference.
Source Context Configuration
The following table lists the information that is required to configure the source context.
Required Information for Source Context Configuration
Mobile Country Code (MCC):The MCC can be configured to any integer value from 0 to 999.
Mobile Network Code (MNC):The MNC can be configured to any integer value from 0 to 999.
Behavior Bits:If charging characteristics will be configured on the GGSN, behavior bits for the following conditions can be configured:
Profile Index:If the GGSN’s charging characteristics will be used for subscriber PDP contexts, profile indexes can be modified/configured for one or more of the following conditions:
IP address:The IP address of the CGF server to which the GGSN will send accounting information.
Priority:If more than on CGF is configured, this is the server’s priority. It is used to determine the rotation order of the CGFs when sending accounting information.
Maximum number of messages:The maximum number of outstanding or unacknowledged GTPP messages allowed for the CGF.
IP address:The static IP address of the mobile station’s for which network-requested PDP context activation will be supported.
Destination context name:The name of the destination context configured on the system that contains the IP address pool containing the mobile station’s static address.
International Mobile Subscriber Identity (IMSI):The IMSI of the mobile station.
APN:The name of the access point that will be passed to the SGSN by the GGSN for the mobile station.
Destination Context Configuration
The following table lists the information that is required to configure the destination context.
Required Information for Destination Context Configuration
NOTE: For this configuration, the destination context name should not match the domain name of a specific APN.
NOTE: The examples discussed in this chapter assumes GTPP is used.
NOTE: The profile index parameters are configured as part of the GGSN service.
Dynamic: Address can be dynamically assigned from one of the sources.
Dynamic Host Control Protocol (DHCP) server: The system can be configured to act as a DHCP proxy and receive address from the server in advance and assign them as needed or it can relay DHCP messages from the MS.
Local address pools: The system can be configured with local address pools.
Static: MS IP addresses can be permanently assigned.
Minimum Lease Time: Measured in seconds and can be configured to any integer value from 600 to 3600. The default is 600 seconds.
Maximum Lease Time: Measured in seconds and can be configured to any integer value from 10800 to 4294967295. The default is 86400 seconds.
IP Address: Specifies the IP address of the RADIUS authentication server the system will communicate with to provide subscriber authentication functions.
Shared Secret: The shared secret is a string between 1 and 15 characters (alpha and/or numeric) that specifies the key that is exchanged between the RADIUS authentication server and the source context.
UDP Port Number: Specifies the port used by the source context and the RADIUS authentication server for communications. The UDP port number can be any integer value between 1 and 65535. The default value is 1812.
IP Address: Specifies the IP address of the RADIUS accounting server that the source context will communicate with to provide subscriber accounting functions.
Shared Secret: The shared secret is a string between 1 and 15 characters (alpha and/or numeric) that specifies the key that is exchanged between the RADIUS accounting server and the source context.
UDP Port Number:Specifies the port used by the source context and the RADIUS Accounting server for communications. The UDP port number can be any integer value between 1 and 65535. The default value is 1813.
How This Configuration Works
This section provides a description of how the information detailed in the previous sections of this chapter are used in the processing of the following types of subscriber sessions:
 
 
Transparent IP PDP Context Processing
The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a transparent IP PDP context.
Transparent IP PDP Context Call Processing
 
1.
2.
3.
4.
5.
6.
7.
Non-transparent IP PDP Context Processing
The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a non-transparent IP PDP context.
Non-transparent IP PDP Context Call Processing
 
1.
2.
3.
4.
5.
6.
7.
8.
PPP PDP Context Processing
The following figure and the following text describe how this configuration with a single source and destination context would be used by the system to process a PPP PDP context.
 
PPP PDP Context Call Processing
 
1.
2.
3.
4.
5.
6.
7.
8.
9.
Network-requested PDP Context Processing
The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a network-requested PDP context.
Network-requested PDP Context Call Processing
 
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883