Cisco Cisco Packet Data Interworking Function (PDIF) Notas De La Versión
AAA Changes in Release 15.0
▀ AAA Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
52
Also, note that the FCI will be included in the CDRs only when the “furnish-charging-information” attribute is
configured in the GTPP Group configuration mode. By default, this attribute is disabled.
configured in the GTPP Group configuration mode. By default, this attribute is disabled.
Support for Sponsor Identity over Gx
Applicable Product(s): GGSN, P-GW
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 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.
Sponsored Data Connectivity feature is introduced in Rel. 10 of 3GPP TS 29.212 specification. If Sponsored Data
Connectivity is supported, the sponsor identity for a PCC rule identifies the 3rd party organization (the sponsor) who is
willing to pay for the operator's charge for connectivity required to deliver a service to the end user.
Connectivity is supported, the sponsor identity for a PCC rule identifies the 3rd party organization (the sponsor) who is
willing to pay for the operator's charge for connectivity required to deliver a service to the end user.
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 reporting at
Sponsor Connection level and two new AVPs “Sponsor-Identity” and “Application-Service-Provider-Identity” have
been introduced at the rule level.
sponsor. To support this, a new reporting level “SPONSORED_CONNECTIVITY_LEVEL” is added for reporting at
Sponsor Connection level and two new AVPs “Sponsor-Identity” and “Application-Service-Provider-Identity” have
been introduced at the rule level.
A new CLI command “
diameter encode-supported-features
” has been added in Policy Control Configuration
mode” to send supported features with Sponsor Identity. For more information on the command, see the Command Line
Interface Reference.
Interface Reference.
Sponsored connectivity feature will be supported only when both P-GW and PCRF support 3GPP Rel. 10. P-GW
advertises release as a part of supported features in CCR-I to PCRF. If P-GW supports Release 10 and also sponsored
connectivity but PCRF does not support it (as a part of supported features in CCA-I), this feature is turned off.
advertises release as a part of supported features in CCR-I to PCRF. If P-GW supports Release 10 and also sponsored
connectivity but PCRF does not support it (as a part of supported features in CCA-I), this feature is turned off.
This feature implementation impacts only the Gx dictionary “dpca-custom15”. Also note that this feature is supported
only for the dynamic rules.
only for the dynamic rules.
Modified Diameter Features
This section identifies Diameter features modified in release 15.0.
Assume Positive Gy Enhancements
Applicable Product(s): GGSN, HA, IPSG, PDSN, P-GW
The following are the enhancements implemented as part of the Assume Positive Gy feature:
Configurable per error code treatment to enter assume positive mode
Graceful session restart upon receipt of a 5002 error
Configurable per Error Code Treatment
This feature allows the customers to configure error result codes using the CLI command “
servers-unreachable
behavior-triggers
” that will trigger entering assume positive mode on the fly for CCR-Initial and CCR-Update
messages. CCR-Terminate message is currently not supported. Also to maintain backward compatibility i.e. in case of
no servers unreachable behavior triggers configured for error result codes, the default hard coded values are applicable.
no servers unreachable behavior triggers configured for error result codes, the default hard coded values are applicable.
Any error result codes from the range 3xxx to 5xxx can be specified using the CLI commands. For more information on
the command, refer to the
the command, refer to the
This feature has been implemented to provide more flexibility and granularity in the way assume positive mode is
triggered for error result codes.
triggered for error result codes.
Graceful Session Restart