Cisco Cisco Packet Data Gateway (PDG)
Policy Control Configuration Mode Commands
▀ diameter encode-supported-features
▄ Command Line Interface Reference, StarOS Release 18
8094
In a scenario wherein RAR is received while waiting for CCA-U, Gx application rejects RAR with
Experimental-Result-Code AVP set to DIAMETER_PENDING_TRANSACTION. This should be done only
if PCRF supports this functionality otherwise Gx client should continue with the current implementation.
If race conditions are not processed properly, it can lead to unpredictable behavior from each node, resulting
in subscriber disconnection. With this feature, the outcome in such situation is deterministic and operator has
the ability to influence the node behavior aligned with their policy.
Experimental-Result-Code AVP set to DIAMETER_PENDING_TRANSACTION. This should be done only
if PCRF supports this functionality otherwise Gx client should continue with the current implementation.
If race conditions are not processed properly, it can lead to unpredictable behavior from each node, resulting
in subscriber disconnection. With this feature, the outcome in such situation is deterministic and operator has
the ability to influence the node behavior aligned with their policy.
Important:
Currently only one pending transaction is supported. So, all other transactions (like handoffs, etc)
while one is pending will be rejected.
In 17.0 and later releases, in order to comply with 4G Network Upgrade 3GPP Standard, the following
changes are implemented:
changes are implemented:
Support for Negotiation of PT in initial session establishment.
Support for receiving/sending 4144 with 3GPP Vendor ID in CCA/RAA.
Retry of CCR-U when 4144 is received from PCRF.
No Support for 4198 with Proprietary Vendor ID.
Recovery of negotiated Supported features.
session-recovery
Enables the Session Recovery feature. This functionality helps ensure that the PCRF and P-GW can be in
sync on session information and recover any lost Gx sessions. By default, session recovery and session sync
features are not enabled.
Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a
message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to
allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers,
etc. In this release, the Gx interface between P-GW and PCRF has been enhanced to allow the PCRF and P-
GW to sync-up. This is currently not part of 3GPP 29.212.
sync on session information and recover any lost Gx sessions. By default, session recovery and session sync
features are not enabled.
Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a
message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to
allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers,
etc. In this release, the Gx interface between P-GW and PCRF has been enhanced to allow the PCRF and P-
GW to sync-up. This is currently not part of 3GPP 29.212.
Important:
In this release, the Session Recovery and Sync will be supported only for the IMS APN.
This keyword is used to achieve the session recovery. When this feature is enabled, P-GW and PCRF will
exchange session information and P-GW provides the complete subscriber session information to enable
PCRF to build the session state.
exchange session information and P-GW provides the complete subscriber session information to enable
PCRF to build the session state.
session-sync
Enables the Session Synchronization feature. This functionality helps ensure that the PCRF and P-GW can be
in sync on session information and recover any lost Gx sessions. By default, Session Recovery and Session
Sync features will not be enabled.
Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a
message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to
allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers,
etc. The Gx interface between P-GW and PCRF is enhanced to allow the PCRF and P-GW to sync-up. This is
currently not part of 3GPP 29.212.
in sync on session information and recover any lost Gx sessions. By default, Session Recovery and Session
Sync features will not be enabled.
Gx sessions typically tend to be long-lived. In case of session loss in PCRF (e.g. due to software failure), or a
message loss in PCRF (e.g. Gx:RAA is dropped due to overload control), there is no existing mechanism to
allow the PCRF and P-GW to sync-up on session state like Rules Status, APN-AMBR, QoS, Event Triggers,
etc. The Gx interface between P-GW and PCRF is enhanced to allow the PCRF and P-GW to sync-up. This is
currently not part of 3GPP 29.212.
Important:
In this release, the Session Recovery and Sync will be supported only for the IMS APN.