•Important: For more information on requirement of licenses for optional enhanced features, refer to Features and Functionality - Optional Enhanced Feature Software section.
• System Management Cards (SMCs): Provides full system control and management of all cards within the ASR 5000 platform. Up to two SMC can be installed; one active, one redundant.
• Packet Processing Cards (PSCs/PSC2s/PPCs):In the ASR 5000 platform, packet processing cards provide high-speed, multi-threaded PDP context processing capabilities for GGSN services. Up to 14 packet processing cards can be installed, allowing for multiple active and/or redundant cards.
• Switch Processor Input/Outputs (SPIO): Installed in the upper-rear chassis slots directly behind the SMCs, SPIOs provide connectivity for local and remote management, central office (CO) alarms. Up to two SPIOs can be installed; one active, one redundant.
• Line Cards: The following rear-loaded line cards are currently supported by the system:
• Ethernet 10/100 and/or Ethernet 1000 Line Cards: Installed directly behind packet processing cards, these cards provide the physical interfaces to elements in the LTE/SAE network. Up to 26 line cards should be installed for a fully loaded system with 13 active packet processing cards, 13 in the upper-rear slots and 13 in the lower-rear slots for redundancy. Redundant packet processing cards do not require line cards.
• Quad Gig-E Line Cards (QGLCs): The 4-port Gigabit Ethernet line card is used in the ASR 5000 system only and is commonly referred to as the Quad-GigE Line Card or the QGLC. The QGLC is installed directly behind its associated packet processing card to provide network connectivity to the packet data network.
• 10 Gig-E Line Cards (XGLCs): The 10 Gigabit Ethernet Line Card is used in the ASR 5000 system only and is commonly referred to as the XGLC. The XGLC supports higher speed connections to packet core equipment, increases effective throughput between the ASR 5000 and the packet core network, and reduces the number of physical ports needed on the ASR 5000.
• Redundancy Crossbar Cards (RCCs): Installed in the lower-rear chassis slots directly behind the SMCs, RCCs utilize 5 Gbps serial links to ensure connectivity between Ethernet 10/100 or Ethernet 1000 line cards/QGLCs and every packet processing card in the system for redundancy. Two RCCs can be installed to provide redundancy for all line cards and packet processing cards.Important: Additional information pertaining to each of the application and line cards required to support GPRS/UMTS wireless data services is located in the Hardware Platform Overview chapter of the Product Overview Guide.
• Gn: This is the interface used by the GGSN to communicate with SGSNs on the same GPRS/UMTS Public Land Mobile Network (PLMN). This interface serves as both the signaling and data path for establishing and maintaining subscriber PDP contexts.
• Ga: This is the interface used by the GGSN to communicate with the Charging Gateway (CG). The charging gateway is responsible for sending GGSN Charging Data Records (G-CDRs) received from the GGSN for each PDP context to the billing system. System supports TCP and UDP as transport layer for this interface.
• Gc: This is the interface used by the GGSN to communicate with the Home Location Register (HLR) via a GTP-to-MAP (Mobile Application Part) protocol convertor. This interface is used for network initiated PDP contexts.
• Gi: This is the interface used by the GGSN to communicate with Packet Data Networks (PDNs) external to the PLMN. Examples of PDNs are the Internet or corporate intranets.
• Gp: This is the interface used by the GGSN to communicate with GPRS Support Nodes (GSNs, e.g. GGSNs and/or SGSNs) on different PLMNs. Within the system, a single interface can serve as both a Gn and a Gp interface.
• AAA: This is the interface used by the GGSN to communicate with an authorization, authentication, and accounting (AAA) server on the network. The system GGSN communicates with the AAA server using the Remote Authentication Dial In User Service (RADIUS) protocol.
• DHCP: This is the interface used by the GGSN to communicate with a Dynamic Host Control Protocol (DHCP) Server. The system can be configured as DHCP-Proxy or DHCP Client to provide IP addresses to MS on PDP contexts activation the DHCP server dynamically.
• Gx: This is an optional Diameter protocol-based interface over which the GGSN communicates with a Charging Rule Function (CRF) for the provisioning of charging rules that are based on the dynamic analysis of flows used for an IP Multimedia Subsystem (IMS) session. The system provides enhanced support for use of Service Based Local Policy (SBLP) to provision and control the resources used by the IMS subscriber. It also provides Flow based Charging (FBC) mechanism to charge the subscriber dynamically based on content usage.Important: The Gx interface is a license-enabled support. For more information on this support, refer Gx Interface Support in Features and Functionality - Optional Enhanced Feature Software section.
• Gy: This is an optional Diameter protocol-based interface over which the GGSN communicates with a Charging Trigger Function (CTF) server that provides online charging data. Gy interface support provides an online charging interface that works with the ECS deep packet inspection feature. With Gy, customer traffic can be gated and billed in an “online” or “prepaid” style. Both time- and volume-based charging models are supported. In all of these models, differentiated rates can be applied to different services based on shallow or deep packet inspection.Important: This interface is supported through Enhanced Charging Service. For more information on this support, refer Enhanced Charging Service Administration Guide.
• GRE: This new protocol interface in GGSN platform adds one additional protocol to support mobile users to connect to their enterprise networks: Generic Routing Encapsulation (GRE). GRE Tunneling is a common technique to enable multi-protocol local networks over a single-protocol backbone, to connect non-contiguous networks and allow virtual private networks across WANs. This mechanism encapsulates data packets from one protocol inside a different protocol and transports the data packets unchanged across a foreign network. It is important to note that GRE tunneling does not provide security to the encapsulated protocol, as there is no encryption involved (like IPSEC offers, for example).Important: The GRE protocol interface is a license-enabled support. For more information on this support, refer GRE Protocol Interface Support in Features and Functionality - Optional Enhanced Feature Software section.
• S6b: This is an optional Diameter protocol-based interface over which the GGSN communicates with 3G AAA/HSS in LTE/SAE network for subscriber authorization.Important: This interface is supported through license-enabled feature. For more information on this support, refer Common Gateway Access Support in guide.
Important: GGSN Software also supports additional interfaces. For more information on additional interfaces, refer Features and Functionality - Optional Enhanced Feature Software section.
Important: To configure the basic service and functionality on the system for GGSN service, refer configuration examples provide in the GGSN Administration Guide.
Important: Due to additional memory requirements, this service can only be used with 8GB minimum packet processing cards.
Important: For more information on AAA Server Group configuration, refer AAA Interface Administration and Reference.
Important: For more information on Access Control List configuration, refer IP Access Control List chapter in System Enhanced Feature Configuration Guide.
• Accounting: RADIUS, GTPP or none. Server group to use. Charging characteristics. Interface with mediation servers.
• Authentication: Protocol, such as, CHAP or PAP or none. Default username/password. Server group to use. Limit for number of PDP contexts.
• Enhanced Charging: Name of rulebase to use, which holds the enhanced charging configuration (e.g., eG-CDR variations, charging rules, prepaid/postpaid options, etc.).
• IP: Method for IP address allocation (e.g., local allocation by GGSN, Mobile IP, DHCP, DHCP relay, etc.). IP address ranges, with or without overlapping ranges across APNs.
• Tunneling: PPP may be tunneled with L2TP. IPv4 may be tunneled with GRE, IP-in-IP or L2TP. Load-balancing across multiple tunnels. IPv6 is tunneled in IPv4. Additional tunneling techniques, such as, IPsec and VLAN tagging may be selected by the APN, but are configured in the GGSN independently from the APN.
• QoS: IPv4 header ToS handling. Traffic rate limits for different 3GPP traffic classes. Mapping of R98 QoS attributes to work around particular handset defections. Dynamic QoS renegotiation (described elsewhere).Important: For more information on APN configuration, refer APN Configuration in GGSN Service Configuration.
• System: Provides system-level statistics
• Card: Provides card-level statistics
• Port: Provides port-level statistics
• FA: Provides FA service statistics
• HA: Provides HA service statistics
• IP Pool: Provides IP pool statistics
• PPP: Provides Point-to-Point Protocol statistics
• GTPC: Provides GPRS Tunneling Protocol - Control message statistics
• GTPP: Provides GPRS Tunneling Protocol - Prime message statistics
• APN: Provides Access Point Name statistics
• RADIUS: Provides per-RADIUS server statistics
• ECS: Provides Enhanced Charging Service Statistics
• DHCP-proxy: The system acts as a proxy for client (MS) and initiates the DHCP Discovery Request on behalf of client (MS). Once it receives an allocated IP address from DHCP server in response to DHCP Discovery Request, it assigns the received IP address to the MS. This allocated address must be matched with the an address configured in an IP address pool on the system. This complete procedure is not visible to MS.
• DHCP-relay: The system acts as a relay for client (MS) and forwards the DHCP Discovery Request received from client (MS). Once it receives an allocated IP address from DHCP server in response to DHCP Discovery Request, it assigns the received IP address to the MS.Important: For more information on DHCP service configuration, refer DHCP Configuration section in GGSN Service Configuration chapter.
• 3GPP TS 32.015 v3.12.0 (2003-12): 3rd Generation Partnership project; Technical Specification Group Services and System Aspects; Telecommunication Management; Charging and billing; GSM call and event data for the Packet Switched (PS) domain (Release 1999) for support of Charging on GGSN
• 3GPP TS 32.215 v5.9.0 (2005-06): 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain (Release 4)
• 3GPP TS 29.060 v7.9.0 (2008-09): Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network; General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface (Release 6)Important: For more information on GTPP group configuration, refer GTPP Accounting Configuration in GGSN Service Configurationchapter.
A configuration explicit-route-advertise is provided to the IP pool configuration and when this option is enabled, the subnet(s) of the pool are not added to routing table and routing protocols like OSPF and BGP do not know of these addresses and hence do not advertise the subnet(s).
• IP Pool-based Next Hop Forwarding - Forwards data packets based on the IP pool from which a subscriber obtains an IP address.
• ACL-based Policy Forwarding - Forwards data packets based on policies defined in Access Control Lists (ACLs) and applied to contexts or interfaces.
• Subscriber specific Next Hop Forwarding - Forwards all packets for a specific subscriber.Important: For more information on IP Policy Forwarding configuration, refer Policy Forwarding chapter in System Enhanced Feature Configuration Guide.
Important: For more information on IP header compression support, refer IP Header Compression chapter in System Enhanced Feature Configuration Guide.
Important: Native IPv6 is only available on the ASR 5000 or higher platform. In Release 9.0 Native IPv6 is available on the GGSN.
•Important: GGSN management functionality is enabled by default for console-based access. For GUI-based management support, refer Web Element Management System section.
Important: For more information on command line interface based management, refer Command Line Interface Reference and GGSN Administration Guide.
Important: For more information on IP pool overlapping configuration, refer VLANs chapter in System Enhanced Feature Configuration Guide.
• 3GPP TS 23.060 v7.4.0 (2007-9): 3rd Generation Partnership project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description (Release 1999) as an additional reference for GPRS/UMTS procedures
• 3GPP TS 29.061 v7.6.0 (2008-09): 3rd Generation Partnership Project; Technical Specification Group Core Network; Packet Domain; Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN) (Release 4)Important: For more information on enhanced charging service, refer Enhanced Charging Service Administration Guide.
Important: The feature described here is internal prioritization and DiffServ remarking for external prioritization. For additional QoS capabilities of the GGSN, refer Features and Functionality - Optional Enhanced Feature Software section.
• Priority: Dictates the order in which the servers are used allowing for multiple servers to be configured in a single context.
• Routing Algorithm: Dictate the method for selecting among configured servers. The specified algorithm dictates how the system distributes AAA messages across the configured AAA servers for new sessions. Once a session is established and an AAA server has been selected, all subsequent AAA messages for the session will be delivered to the same server.Important: For more information on RADIUS AAA configuration, refer AAA Interface Administration and Reference.
Important: For more information on VLAN support, refer VLANs chapter in System Enhanced Feature Configuration Guide.
• Static Routes: The system supports the configuration of static network routes on a per context basis. Network routes are defined by specifying an IP address and mask for the route, the name of the interface in the currant context that the route must use, and a next hop IP address.
• Open Shortest Path First (OSPF) Protocol: A link-state routing protocol, OSPF is an Interior Gateway Protocol (IGP) that routes IP packets based solely on the destination IP address found in the IP packet header using the shortest path first. IP packets are routed “as is”, meaning they are not encapsulated in any further protocol headers as they transit the network.
• Border Gateway Protocol version 4 (BGP-4): The system supports a subset of BGP (RFC-1771, A Border Gateway Protocol 4 (BGP-4)), suitable for eBGP support of multi-homing typically used to support geographically redundant mobile gateways, is supported.
•
•
• Route Policy: Routing policies modify and redirect routes to and from the system to satisfy specific routing needs. The following methods are used with or without active routing protocols (i.e. static or dynamic routing) to prescribe routing policy:
• Route Access Lists: The basic building block of a routing policy, route access lists filter routes based upon a specified range of IP addresses.
• IP Prefix Lists: A more advanced element of a routing policy. An IP Prefix list filters routes based upon IP prefixes
• AS Path Access Lists: A basic building block used for Border Gateway Protocol (BGP) routing, these lists filter Autonomous System (AS) paths.
• Route Maps: Route-maps are used for detailed control over the manipulation of routes during route selection or route advertisement by a routing protocol and in route redistribution between routing protocols. This detailed control is achieved using IP Prefix Lists, Route Access Lists and AS Path Access Lists to specify IP addresses, address ranges, and Autonomous System Paths.
• Equal Cost Multiple Path (ECMP): ECMP allows distribution of traffic across multiple routes that have the same cost to the destination. In this manner, throughput load is distributed across multiple path, typically to lessen the burden on any one route and provide redundancy. The mobile gateway supports from four to ten equal-cost paths.Important: For more information on IP Routing configuration, refer Routing chapter in System Enhanced Feature Configuration Guide.
The RADIUS attribute 3GPP-Chrg-Char can be used to get the charging characteristics from RADIUS in Access-Accept message. Accepting the RADIUS returned charging characteristic profile must be enabled per APN. The CC profile returned by AAA will override any CC provided by the SGSN, the GGSN or per APN configuration. All 16 profile behaviors can be defined explicitly or the default configuration for that profile is used.
• Alert: A value is monitored and an alert condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.
• Alarm: Both high and low threshold are defined for a value. An alarm condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.
• SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or clear) of each of the monitored value.
• Logs: The system provides a facility called threshold for which active and event logs can be generated. As with other system facilities, logs are generated Log messages pertaining to the condition of a monitored value are generated with a severity level of WARNING
• Alarm System: High threshold alarms generated within the specified polling interval are considered “outstanding” until a the condition no longer exists or a condition clear alarm is generated. “Outstanding” alarms are reported to the system's alarm subsystem and are viewable through the Alarm Management menu in the Web Element Manager.Important: For more information on threshold crossing alert configuration, refer Thresholding Configuration Guide.
For more information on this product, refer Common Gateway Access Support section in GGSN Service Administration Guide.
• Change of Authorization: The system supports CoA messages from the AAA server to change data filters associated with a subscriber session. The CoA request message from the AAA server must contain attributes to identify NAS and the subscriber session and a data filter ID for the data filter to apply to the subscriber session.
• Disconnect Message: The DM message is used to disconnect subscriber sessions in the system from a RADIUS server. The DM request message should contain necessary attributes to identify the subscriber session.Important: For more information on dynamic RADIUS extensions support, refer CoA, RADIUS, And Session Redirection (Hotlining) chapter in System Enhanced Feature Configuration Guide.
Important: For more information on Gx interface support, refer Gx Interface Support chapter in System Enhanced Feature Configuration Guide.
Important: For more information on inter-chassis session recovery support, refer Interchassis Session Recovery chapter in System Enhanced Feature Configuration Guide.
• PDN Access: Subscriber IP traffic is routed over an IPSec tunnel from the system to a secure gateway on the Packet Data Network (PDN) as determined by Access Control List (ACL) criteria.
• Mobile IP: Mobile IP control signals and subscriber data is encapsulated in IPSec tunnels that are established between Foreign Agents (FAs) and Home Agents (HAs) over the Pi interfaces.Important: Once an IPSec tunnel is established between an FA and HA for a particular subscriber, all new Mobile IP sessions using the same FA and HA are passed over the tunnel regardless of whether or not IPSec is supported for the new subscriber sessions. Data for existing Mobile IP sessions will be unaffected.
• L2TP: L2TP-encapsulated packets are routed from the system to an LNS/secure gateway over an IPSec tunnel.Important: For more information on IPSec support, refer IP Security chapter in System Enhanced Feature Configuration Guide.
Important: Native IPv6 is available only on ASR 5000 or higher platforms. In Release 9.0 Native IPv6 is available on the GGSN.
Important: For more information on this feature support, refer L2TP Access Concentrator chapter in System Enhanced Feature Configuration Guide.
Important: For more information on this feature support, refer L2TP Network Server chapter in System Enhanced Feature Configuration Guide.
Caution: This capacity improvement impacts performance over various network scenario and in order to reach the full target of 20000 LI targets, it is required that the used platform have at least 12 active packet processing cards installed.
Important: For more information on this feature support, refer Lawful Intercept Configuration Guide.
• Mobile IP HA Session Rejection/Redirection: Enables the HA service to either reject new calls or redirect them to another HA when a destination network connection failure is detected. When network connectivity is re-established, the HA service begins to accept calls again in the normal manner. This feature provides the benefit of reducing OpEx through increased operational efficiency and limiting of system downtime.
• Mobile IP Registration Revocation: Registration Revocation is a general mechanism whereby the HA providing Mobile IP or Proxy Mobile IP functionality to a mobile node can notify the GGSN/FA of the termination of a binding. Mobile IP Registration Revocation can be triggered at the HA by any of the following:Important: For more information on Mobile IP HA service and FA service configuration, refer HA Administration Guide and GGSN Administration Guide respectively
Important: For more information on this feature, refer MIP NAT Traversal chapter in System Enhanced Feature Configuration Guide.
Important: For more information on this feature, refer Multicast Broadcast Service chapter in System Enhanced Feature Configuration Guide.
Important: For more information on this feature, refer Subscriber Overcharging Protection chapter in System Enhanced Feature Configuration Guide.
Important: For more information on this feature, refer Proxy Mobile IP chapter in System Enhanced Feature Configuration Guide.
Important: Other licenses (i.e. IP Security and L2TP) may be additionally required depending on your network deployment and implementation.
• Task recovery mode: Wherein one or more session manager failures occur and are recovered without the need to use resources on a standby packet processing card. In this mode, recovery is performed by using the mirrored “standby-mode” session manager task(s) running on active packet processing cards. The “standby-mode” task is renamed, made active, and is then populated using information from other tasks such as AAA manager.
• Full packet processing card recovery mode: Used when a packet processing card hardware failure occurs, or when a packet processing card migration failure happens. In this mode, the standby packet processing card is made active and the “standby-mode” session manager and AAA manager tasks on the newly activated packet processing card perform session recovery.Important: For more information on this feature, refer Session Revocery chapter in System Enhanced Feature Configuration Guide.
• Committed Data Rate (CDR): The guaranteed rate (in bits per second) at which packets may be transmitted/received for the subscriber during the sampling interval.
• Peak Data Rate (PDR): The maximum rate (in bits per second) that packets may be transmitted/received for the subscriber during the sampling interval.
• Burst-size: The maximum number of bytes that may be transmitted/received for the subscriber during the sampling interval for both committed (CBS) and peak (PBS) rate conditions. This represents the maximum number of tokens that can be placed in the subscriber's “bucket”. Note that the committed burst size (CBS) equals the peak burst size (PBS) for each subscriber.
• Drop: The offending packet is discarded.
• Transmit: The offending packet is passed.
• Lower the IP Precedence: The packet's ToS octet is set to “0”, thus downgrading it to Best Effort, prior to passing the packet.
• Buffer the Packet: The packet stored in buffer memory and transmitted to subscriber once traffic flow comes in allowed bandwidth.Important: For more information on this feature, refer Traffic Policing and Shaping chapter in System Enhanced Feature Configuration Guide.
• Type: The system supports IPv4, IPv6, and PPP PDP contexts.
• Accounting protocol: Support is provided for using either the GTPP or Remote Authentication Dial-In User Service (RADIUS) protocols. In addition, an option is provided to disable accounting if desired.
• Authentication protocol: Support is provided for using any of the following:
• Charging characteristics: Each APN template can be configured to either accept the charging characteristics it receives from the SGSN for a PDP context or use it’s own characteristics.
• IP address allocation method: IP addresses for PDP contexts can be assigned using one of the following methods:
• Statically: The APN template can be configured to provide support for MS-requested static IP addresses. Additionally, a static address can be configured in a subscriber’s profile on an authentication server and allocated upon successful authentication.Important: Static IP addresses configured in subscriber profiles must also be part of a static IP address pool configured locally on the system.
• Dynamically :The APN template can be configured to dynamically assign an IP address from locally configured address pools or via a Dynamic Host Control Protocol (DHCP) server. Additional information on dynamic address assignment can be found in the Dynamic IP Address Assignment section that follows.
• Selection mode: The MS’s right to access the APN can be either verified or unverified. For verified access, the SGSN specifies the APN that should be used. For unverified access, the APN can be specified by either the SGSN or the MS.
• Timeout: Absolute and idle session timeout values specify the amount of time that an MS can remain connected.
• Mobile IP configuration: Mobile IP requirements, HA address, and other related parameters are configured in the APN template.
• Proxy Mobile IP support: Mobile IP support can be enabled for all subscribers facilitated by the APN. Alternatively, it can be enabled for individual subscribers via parameters in their RADIUS or local-user profiles.
• Quality of Service: Parameters pertaining to QoS feature support such as for Dynamic Renegotiation, Traffic Policing, and DSCP traffic class.As previously described in the PDP Context Processing section of this chapter, the method by which IP addresses are assigned to a PDP context is configured on an APN-by-APN basis. Each APN template dictates whether it will support static or dynamic addresses. If dynamic addressing is supported, the following methods can be implemented:
• Local pools: The system supports the configuration of public or private IP address pools. Addresses can be allocated from these pools as follows:
• Public pools: Provided that dynamic assignment is supported, a parameter in the APN configuration mode specifies the name of the local public address pool to use for PDP contexts facilitated by the APN.
• Private pools: Provided that dynamic assignment is supported, the name of the local private pool can be specified in the subscriber’s profile. The receipt of a valid private pool name will override the APN’s use of addresses from public pools.
• Dynamic Host Control Protocol (DHCP): The system can be configured to use DHCP PDP context address assignment using either of the following mechanisms:
• DHCP-proxy: The system acts as a proxy for client (MS) and initiates the DHCP Discovery Request on behalf of client (MS). Once it receives an allocated IP address from DHCP server in response to DHCP Discovery Request, it assigns the received IP address to the MS. This allocated address must be matched with the an address configured in an IP address pool on the system. This complete procedure is not visible to MS.
• DHCP-relay: The system acts as a relay for client (MS) and forwards the DHCP Discovery Request received from client (MS). Once it receives an allocated IP address from DHCP server in response to DHCP Discovery Request, it assigns the received IP address to the MS.
• Transparent IP: The subscriber is provided basic access to a PDN without the GGSN authenticating the subscriber. Either a static or dynamic IP address can be assigned to the MS in this scenario.
• Non-transparent IP: The GGSN provides subscriber authentication services for the data session. Either a static or dynamic IP address can be assigned to the MS in this scenario.
• Network-initiated: An IP Packet Data Unit (PDU) is received by the GGSN from the PDN for a specific subscriber. If configured to support network-initiated sessions, the GGSN, will initiate the process of paging the MS and establishing a PDP context.
• PPP Direct Access: The GGSN terminates the subscriber’s PPP session and provides subscriber authentication services for the data session. Either a static or dynamic IP address can be assigned to the MS in this scenario.
• Virtual Dialup Access: The GGSN functions as an LAC, encapsulates subscriber packets using L2TP, and tunnels them directly to an LNS for processing.
• Corporate IP VPN Connectivity: Similar to the Virtual Dialup Access model, however, the GGSN is configured to tunnel subscriber packets to a corporate server using IP-in-IP.
• Mobile IP: Subscriber traffic is routed to their home network via a tunnel between the GGSN/FA and an HA. The subscriber’s IP PDP context is assigned an IP address from the HA.
• Proxy Mobile IP: Provides a mobility solution for subscribers whose Mobile Nodes (MNs) do not support the Mobile IP protocol. The GGSN/FA proxy the Mobile IP tunnel with the HA on behalf of the MS. The subscriber receives an IP address from their home network. As the subscriber roams through the network, the IP address is maintained providing the subscriber with the opportunity to use IP applications that require seamless mobility such as transferring files.
• IPv6 Stateless Address Autoconfiguration: The mobile station may select any value for the interface identifier portion of the address. The only exception is the interface identifier for the link-local address used by the mobile station. This interface identifier is assigned by the GGSN to avoid any conflict between the mobile station link-local address and the GGSN address. The mobile station uses the interface ID assigned by the GGSN during stateless address auto-configuration procedure (e.g., during the initial router advertisement messages). Once this is over, the mobile can select any interface ID for further communication as long as it does not conflict with the GGSN’s interface ID (that the mobile would learn through router advertisement messages from the GGSN).If the MS required the dynamic assignment of an IP address (i.e., the PDP Address received from the mobile was null), the GGSN will assign one. The IP address assignment methods supported by the system GGSN are described in the Dynamic IP Address Assignment section of this guide.If the MS required the dynamic assignment of an IP address (i.e., the PDP Address received from the mobile was null), the GGSN will assign one. The IP address assignment methods supported by the system GGSN are described in the Dynamic IP Address Assignment section of this chapter.
7. The MS begins the PDP Context Activation procedure as described in step 2 through step 5 of the Transparent Session IP Call Flow section of this chapter.
8. The MS can terminate the data session at any time. To terminate the session, the MS begins the PDP Context De-Activation procedure as described in step 6 through step 11 of the Transparent Session IP Call Flow section of this chapter.
9. The GGSN assigns an IP address to the MS and completes the PPP negotiation process. More information about IP addressing for PDP contexts is located in the PDP Context Processing and Dynamic IP Address Assignment sections of this chapter.If the MS required the dynamic assignment of an IP address (i.e., the PDP Address received from the mobile was null), the GGSN will assign one. The IP address assignment methods supported by the system GGSN are described in the Dynamic IP Address Assignment section of this chapter.
•
•
•
•
•
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |