Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 16
▀ AAA Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
58
cc-profile
is a new keyword in this command to specify the charging-characteristic preference for the credit-control-
group.
configure
context context_name
apn apn_name
credit-control-group cc_group_name [ cc-profile cc_profile_index ]
no credit-control-group cc_group_name [ cc-profile cc_profile_index ]
end
Notes:
cc_profile_index
must be an integer from 0 through 15. Note that one charging-characteristic value can be
mapped to only one credit-control-group inside one APN.
With this enhancement, the OCS selection can be done based on the CC value received via GTP request.
CSCtz62801, CSCtw75856, CSCty34184 - Processing Diameter Gx Messages in
the order in which they were received
Applicable Products: GGSN, P-GW
Feature Changes
Race Conditions and Parallel Processing
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.
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 (4198). Though the PCRF does not support this
functionality, the gateway will send the experimental result code (4198) if the CLI command “
Result-Code AVP set to DIAMETER_PENDING_TRANSACTION (4198). Though the PCRF does not support this
functionality, the gateway will send the experimental result code (4198) if the CLI command “
diameter encode-
supported-features pending-transactions
” is configured.
Previous Behavior: Currently, if PCEF receives a server initiated message while PCEF initiated message is still
pending and no response was received for the message, the PCEF rejects the server initiated message with
DIAMETER_UNABLE_TO_DELIVER or DIAMETER_UNABLE_TO_COMPLY. This causes the PCRF to
reject/abort the procedure based on configuration.
pending and no response was received for the message, the PCEF rejects the server initiated message with
DIAMETER_UNABLE_TO_DELIVER or DIAMETER_UNABLE_TO_COMPLY. This causes the PCRF to
reject/abort the procedure based on configuration.
New Behavior: As part of the enhanced behavior a new cause code DIAMETER_PENDING_TRANSACTION (4198)
is supported by PCEF to respond to the server when a pending client initiated procedure exists. The out of order RAR
message with session release cause is processed now.
is supported by PCEF to respond to the server when a pending client initiated procedure exists. The out of order RAR
message with session release cause is processed now.
Similarly, PCEF handles Experimental Result Code DIAMETER_PENDING_TRANSACTION (4198) whenever it is
received from PCRF in CCA-U and will retry.
received from PCRF in CCA-U and will retry.
Important:
This behavior change is currently applicable only to dpca-custom8 dictionary.