Cisco Cisco Packet Data Interworking Function (PDIF)
AAA Changes in Release 17
AAA Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
47
AAA Enhancements for 17.1
This section identifies all of the AAA (including RADIUS and Diameter) enhancements included in this release:
Feature Changes - new or modified feature or behavior changes. For details, refer to the AAA Interface Administration
and Reference for this release.
and Reference for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line Interface
Reference for this release.
Reference for this release.
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
CSCtz79646, CSCuh67284 - PCSCF discovery - v4/v6 addresses not sent
always for v4/v6 pdn req
Applicable Products: GGSN, P-GW
Feature Changes
Send P-CSCF Address Based on PCO Request
Previous Behavior: IMSA will select the servers if requested server address type and selected row server-address type
are the same. Otherwise, it will return NULL.
are the same. Otherwise, it will return NULL.
New Behavior: P-CSCF server selection algorithm is modified such that the P-CSCF server selection now happens
based on UE-requested server-type.
based on UE-requested server-type.
CSCud26703 - Enable / disable multiple back to back CCR-Us from PGW/GGSN
Applicable Products: GGSN, HA, PDSN, P-GW, S-GW
Feature Changes
Multiple CCR-Us Support Over Gx Interface
Previous Behavior: ASR5K node earlier supported only one pending CCR-U message per session over Gx interface.
Any request to trigger CCR-U (for access side updates/internal updates) were ignored/dropped, when there was already
an outstanding message pending at the node. PCEF and PCRF were out of synch if CCR-U for critical update was
dropped (like RAT change/ULI change).
Any request to trigger CCR-U (for access side updates/internal updates) were ignored/dropped, when there was already
an outstanding message pending at the node. PCEF and PCRF were out of synch if CCR-U for critical update was
dropped (like RAT change/ULI change).
New Behavior: ASR5K supports a configurable CLI command “
max-outstanding-ccr-u
” under IMS
Authorization Service configuration mode to allow multiple CCR-Us towards PCRF. That is, this CLI will allow the
user to configure a value of up to 12 as the maximum number of CCR-U messages per session.
user to configure a value of up to 12 as the maximum number of CCR-U messages per session.
The CLI-based implementation allows sending request messages as and when they are triggered and processing the
response when they are received. The gateway does re-ordering if the response messages are received out of sequence.
response when they are received. The gateway does re-ordering if the response messages are received out of sequence.