Cisco Cisco Packet Data Gateway (PDG)
Feature Changes
This feature provides support to encode the MEID AVP and include it in the User-Equipment-Info grouped
AVP for eHRPD calls in all Gy CCR messages.
AVP for eHRPD calls in all Gy CCR messages.
Full Checkpointing of Diameter Peer Information During Session Recovery
CSCuu05894 - Add Diameter Peer to Micro checkpoint for all diameter interfaces
Applicable Products: ePDG, GGSN, P-GW
Feature Changes
Diameter applications like Gx and Gy does not checkpoint the Diameter peer information completely when
the ICSR or Session Recovery occurs. This resulted in the subscribers contacting a different set of peers when
the Diameter application level configuration is changed.
the ICSR or Session Recovery occurs. This resulted in the subscribers contacting a different set of peers when
the Diameter application level configuration is changed.
This feature is implemented to support the checkpoint and recovery of destination realm, bound peer, primary
peer and secondary peer (from application-specific configuration). The subscriber session will continue to
use the same peers even when the configuration changes on the standby chassis.
peer and secondary peer (from application-specific configuration). The subscriber session will continue to
use the same peers even when the configuration changes on the standby chassis.
Previous Behavior:Diameter peer information for all session supported Diameter applications were not
completely checkpointed when the ICSR and/or Session Recovery occurs.
completely checkpointed when the ICSR and/or Session Recovery occurs.
New Behavior:The primary and secondary peer information for Gx and Gy applications are checkpointed
and recovered during the failover scenario. If a session is using Gx and Gy applications, then the Diameter
peers for each of these services are micro checkpointed. After the switchover, the Diameter messages applicable
to the session are routed to the correct peers without being rejected.
and recovered during the failover scenario. If a session is using Gx and Gy applications, then the Diameter
peers for each of these services are micro checkpointed. After the switchover, the Diameter messages applicable
to the session are routed to the correct peers without being rejected.
New Diameter Attributes for Detecting Stale Message Requests
CSCuu11329, CSCus94250 - Diameter Support for Maintaining Session Uniqueness
Applicable Products: ePDG, eHRPD, GGSN, P-GW, SAE-GW
Related ID: CSCus87417, CSCut99086, CSCut88330, CSCuu01902
Feature Changes
When the ePDG/MME is reselected by the UE or when the ePDG/MME reselects a different P-GW during
timeout scenarios, it is possible that the old PDN connection request is still being processed in the network
and the session created by the new PDN connection request is overwritten by the stale procedure. VoLTE
calls fail when such race conditions occur. Also, other stale information existing in the network elements
might cause some unexpected issues.
timeout scenarios, it is possible that the old PDN connection request is still being processed in the network
and the session created by the new PDN connection request is overwritten by the stale procedure. VoLTE
calls fail when such race conditions occur. Also, other stale information existing in the network elements
might cause some unexpected issues.
In order to solve this problem, the implementation of ePDG/MME is modified to populate and send the
Timestamp and Maximum Wait Time (MWT) private extensions in Create Session Request towards P-GW
to be able to support session uniqueness.
Timestamp and Maximum Wait Time (MWT) private extensions in Create Session Request towards P-GW
to be able to support session uniqueness.
Release Change Reference, StarOS Release 19
35
AAA Changes in Release 19
Full Checkpointing of Diameter Peer Information During Session Recovery