Cisco Cisco Packet Data Gateway (PDG) Nota De Lançamento
P-GW Changes in Release 15.0
▀ P-GW Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
402
Previous Behavior: APN configuration did not include the mobile-ip min-reg-lifetime configuration.
New Behavior: CLI has been added to APN for mobile-ip min-reg-lifetime to configure a platform-wide NEMO
minimum registration timer to override the platform-wide default on an enterprise basis.
minimum registration timer to override the platform-wide default on an enterprise basis.
min-reg-lifetime taken from APN configuration if provisioned; otherwise, it will be taken from the HA service
configuration.
configuration.
P-GW 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.
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.
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.
Per RFC 5847, PMIP heartbeats from the HSGW to the P-GW are now supported. CLI has been added to configure the
heartbeat variables. Show commands have also been modified to display the heartbeat configuration and the statistics.
heartbeat variables. Show commands have also been modified to display the heartbeat configuration and the statistics.
Provide Dynamic Address Flag Extension from P-GW SM
When PAA contained single IP address for dual stack, P-GW SM was using the same macro for updating dyn_addr_flag
and dyn_ipv6_addr_flag, and used the same value for both flags. This has been corrected by introducing a new macro
for IPv6 addr.
and dyn_ipv6_addr_flag, and used the same value for both flags. This has been corrected by introducing a new macro
for IPv6 addr.
Provide dyn_ipv6_addr_flag
Code added to provide dyn_ipv6_addr_flag value to ECS.
S-GW Restoration Support on P-GW
S-GW Restoration helps in handling the S-GW failure in the EPC network in a graceful manner. It allows affected
PDNs due to S-GW failure to be restored by selecting another S-GW to serve the affected PDNs, thus avoiding
unnecessary flooding of signaling for PDN cleanup.
PDNs due to S-GW failure to be restored by selecting another S-GW to serve the affected PDNs, thus avoiding
unnecessary flooding of signaling for PDN cleanup.
S-GW Restoration is based on 3GPP Release 11. It requires enhancements at P-GW for maintaining the sessions in case
path failure is detected or when S-GW restart is detected via recovery IE on GTP-C signaling. P-GW shall ensure that
any dropped packets in this scenario are not charged and P-GW shall reject any bearer addition/modification request
received for the PDN connection maintained after the S-GW failure detection, till the time that PDN is restored again.
path failure is detected or when S-GW restart is detected via recovery IE on GTP-C signaling. P-GW shall ensure that
any dropped packets in this scenario are not charged and P-GW shall reject any bearer addition/modification request
received for the PDN connection maintained after the S-GW failure detection, till the time that PDN is restored again.
Once the session has been restored by the MME (i.e., P-GW receives a Modify Bearer Request from the restarted S-GW
or a different S-GW), P-GW shall resume forwarding any received downlink data and start charging them.
or a different S-GW), P-GW shall resume forwarding any received downlink data and start charging them.
When subscriber is in S-GW restoration phase, all RARs (expect for Session Termination) will be rejected by PCEF. P-
GW will reject all internal updates which can trigger CCR-U towards PCRF. P-GW shall trigger a CCR U with AN-
GW-Change for the PDNs that are restored if the S-GW has changed on restoration.
GW will reject all internal updates which can trigger CCR-U towards PCRF. P-GW shall trigger a CCR U with AN-
GW-Change for the PDNs that are restored if the S-GW has changed on restoration.
Important:
Only MME/S4-SGSN triggered S-GW restoration procedure will be supported. S-GW restoration
detection based on GTP-U path failure shall not be considered for this release. GTP-C path failure detection should be
enabled for enabling this feature.
enabled for enabling this feature.