Cisco Cisco Packet Data Gateway (PDG) Nota De Lançamento
AAA Changes in Release 15.0
▀ AAA Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
56
With this enhancement, it is now possible to populate the AF-Charging Identifier AVP and send it over the Gx interface.
Support for AF-Correlation-Information AVP at MSCC Level
Applicable Product(s): GGSN, P-GW, SAEGW
With this enhancement request, AF-Charging Identifier is received over the Gx interface. The charging ID received
from PCRF is passed to OCS using the AF-Correlation-Information AVP. This AVP is now supported at Multiple-
Services-Credit-Control (MSCC) level.
from PCRF is passed to OCS using the AF-Correlation-Information AVP. This AVP is now supported at Multiple-
Services-Credit-Control (MSCC) level.
The Gy dictionary “dcca-custom7” is modified to include AF-Correlation-Information AVP as part of the grouped AVP
“Multiple-Services-Credit-Control” in the CCR messages. The AF-Correlation-Information AVP is parsed in MSCC if
the reporting level is SERVICE_IDENTIFIER_LEVEL and the respective parameters are received from PCRF.
“Multiple-Services-Credit-Control” in the CCR messages. The AF-Correlation-Information AVP is parsed in MSCC if
the reporting level is SERVICE_IDENTIFIER_LEVEL and the respective parameters are received from PCRF.
Important:
The AF-Correlation-Information AVP is included only if AF-Charging-Id is received from PCRF.
Also, note that this enhancement applies to dynamic rule only.
Support for PCRF Reconnection after Applying Continue Failure Handling Action
Applicable Product(s): GGSN, P-GW
Previous Behavior: If failure-handling action “continue” is applied to a subscriber’s session, there was no further
interaction with PCRF. The usage monitoring information was lost in the event of message delivery failure.
interaction with PCRF. The usage monitoring information was lost in the event of message delivery failure.
New Behavior: If this new CLI “
continue retry-server-on-event
” is configured in the Policy Control
Configuration mode or with failure-handling template, CCR-U is sent to PCRF, even after failure action continue is
taken for the subscriber.
taken for the subscriber.
When the message delivery fails, the usage monitoring information is restored at ECS (except last rule removal or if
monitoring stopped) and reported in CCR-T or in the next CCR-U (if CLI “
monitoring stopped) and reported in CCR-T or in the next CCR-U (if CLI “
event-update send-usage-report
” is
configured).
Support for Service-Start-Time AVP in dcca-custom28 Gy Dictionary
Applicable Product(s): GGSN
The Diameter AVP "Service-Start-Time" is added as part of the CCR-I and CCR-U messages in the Gy dictionary
"dcca-custom28". With the inclusion of this AVP in dcca-custom28, the operators can charge the subscriber's usage
based on the start time of the services / rating group accordingly.
"dcca-custom28". With the inclusion of this AVP in dcca-custom28, the operators can charge the subscriber's usage
based on the start time of the services / rating group accordingly.
Note the subsequent CCR-Us for that rating group retains the same Service Start Timestamp value. After Quota Holding
Timer (QHT) expiry, the relevant service / rating group is considered closed once the CCA-U is received. The Service-
Start-Timestamp AVP should be set according to the Event-Timestamp of the next CCR-U sent for that rating group.
Timer (QHT) expiry, the relevant service / rating group is considered closed once the CCA-U is received. The Service-
Start-Timestamp AVP should be set according to the Event-Timestamp of the next CCR-U sent for that rating group.
Support for Sponsor Identity
Applicable Product(s): GGSN, P-GW
Previous Behavior: Only two reporting levels (0 – SERVICE_IDENTIFIER and 1 – RATING_GROUP) were intially
supported.
supported.
New Behavior: One more reporting level (2 – SPONSORED_CONNECTIVITY_LEVEL) is now supported for
reporting at Sponsor Connection level. This reporting level is currently applicable only for the dynamic-rules and if
offline charging is enabled.
reporting at Sponsor Connection level. This reporting level is currently applicable only for the dynamic-rules and if
offline charging is enabled.
If the offline charging is enabled and the reporting level is 2 then both the AVPs “Sponsor-Identity” and “Application-
Service-Provider-Identity” must be present for the rule installation/update procedure to succeed.
Service-Provider-Identity” must be present for the rule installation/update procedure to succeed.