Cisco Cisco Packet Data Gateway (PDG)
Policy Control Configuration Mode Commands
▀ diameter encode-supported-features
▄ Command Line Interface Reference, StarOS Release 16
7850
diameter encode-supported-features
This command enables/disables encoding and sending of Supported-Features AVP.
Product
GGSN
P-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > IMS Authorization Configuration > Policy Control
Configuration
Configuration
configure > context context_name > ims-auth-service service_name > policy-control
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-imsa-dpca)#
Syntax
diameter encode-supported-features { pending-transactions | sponsored-connectivity }
{ default | no } diameter encode-supported-features
pending-transactions
Configures the Pending Transactions feature as part of supported features. This keyword addition is to handle
race conditions on Gx i.e. process the Diameter messages in the order they are received.
Gx-based applications are vulnerable to certain race conditions (e.g. concurrent RAR/CCR). Enhancements
are done on the Diameter protocol to deterministically handle the race conditions on Gx.
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.
race conditions on Gx i.e. process the Diameter messages in the order they are received.
Gx-based applications are vulnerable to certain race conditions (e.g. concurrent RAR/CCR). Enhancements
are done on the Diameter protocol to deterministically handle the race conditions on Gx.
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.
Important:
Currently only one pending transaction is supported. So, all other transactions (like handoffs, etc)
while one is pending will be rejected.
sponsored-connectivity
Enables the Sponsored (data) Connectivity feature.
With sponsored data connectivity, the sponsor has a business relationship with the operator and the sponsor
reimburses the operator for the user's data connectivity in order to allow the user access to an associated
Application Service Provider's (ASP) services. Alternatively, the user pays for the connectivity with a
transaction which is separate from the subscriber's charging. It is assumed the user already has a subscription
with the operator.
The purpose of this feature is to identify the data consumption for a certain set of flows differently and charge
it to sponsor. To support this, a new reporting level “SPONSORED_CONNECTIVITY_LEVEL” is added for
With sponsored data connectivity, the sponsor has a business relationship with the operator and the sponsor
reimburses the operator for the user's data connectivity in order to allow the user access to an associated
Application Service Provider's (ASP) services. Alternatively, the user pays for the connectivity with a
transaction which is separate from the subscriber's charging. It is assumed the user already has a subscription
with the operator.
The purpose of this feature is to identify the data consumption for a certain set of flows differently and charge
it to sponsor. To support this, a new reporting level “SPONSORED_CONNECTIVITY_LEVEL” is added for