Table of Contents
Advertisement
▀ Features and Functionality - Base Software
Interim, and Event) to transfer charging records to the CDF/CGF. Each gateway relies on triggering conditions for
reporting chargeable events to the CDF/CGF. Typically as EPS bearers are activated, modified or deleted, charging
records are generated. The EPC platforms include information such as Subscription-ID (IMSI), Charging-ID (EPS
bearer identifier) and separate volume counts for the uplink and downlink traffic.
Peer GTP Node Profile Configuration Support
Provides flexibility to the operators to have different configuration for GTP-C and Lawful Intercept, based on the type
of peer or the IP address of the peer
Peer profile feature allows flexible profile based configuration to accommodate growing requirements of customizable
parameters with default values and actions for peer nodes of P-GW. With this feature, configuration of GTP-C
parameters and disabling/enabling of Lawful Intercept per MCC/MNC or IP address based on rules defined.
A new framework of peer-profile and peer-map is introduced. Peer-profile configuration captures the GTP-C specific
configuration and/or Lawful Intercept enable/disable configuration. GTP-C configuration covers GTP-C retransmission
(maximum number of retries and retransmission timeout) and GTP echo configuration. Peer-map configuration matches
the peer-profile to be applied to a particular criteria. Peer-map supports criteria like MCC/MNC (PLMN-ID) of the peer
or IP-address of the peer. Peer-map can then be associated with P-GW service.
Intent of this feature is to provide flexibility to operators to configure a profile which can be applied to a specific set of
peers. For example, have a different retransmission timeout for foreign peers as compared to home peers.
PMIPv6 Heartbeat
Proxy Mobile IPv6 (PMIPv6) is a network-based mobility management protocol to provide mobility without requiring
the participation of the mobile node in any PMIPv6 mobility related signaling. The core functional entities Mobile
Access Gateway (MAG) and the Local Mobility Anchor (LMA) set up tunnels dynamically to manage mobility for a
mobile node.
Path management mechanism through Heartbeat messages between the MAG and LMA is important to know the
reachability of the peers, to detect failures, quickly inform peers in the event of a recovery from node failures, and allow
a peer to take appropriate action.
PMIP heartbeats from the HSGW to the P-GW are supported per RFC 5847. Refer to the
LMA Service mode or MAG Service mode respectively to enable this heartbeat and configure the heartbeat variables.
Proxy Mobile IPv6 (S2a)
Provides a mobility management protocol to enable a single LTE-EPC core network to provide the call anchor point for
user sessions as the subscriber roams between native EUTRAN and non-native e-HRPD access networks
S2a represents the trusted non-3GPP interface between the LTE-EPC core network and the evolved HRPD network
anchored on the HSGW. In the e-HRPD network, network-based mobility provides mobility for IPv6 nodes without
host involvement. Proxy Mobile IPv6 extends Mobile IPv6 signaling messages and reuses the HA function (now known
as LMA) on the P-GW. This approach does not require the mobile node to be involved in the exchange of signaling
messages between itself and the Home Agent. A proxy mobility agent (e.g. MAG function on HSGW) in the network
performs the signaling with the home agent and does the mobility management on behalf of the mobile node attached to
the network.
The S2a interface uses IPv6 for both control and data. During the PDN connection establishment procedures the P-GW
allocates the IPv6 Home Network Prefix (HNP) via Proxy Mobile IPv6 signaling to the HSGW. The HSGW returns the
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
62
PDN Gateway Overview
command in the
heartbeat
Advertisement
Table of Contents
