N.2 Reporting for sponsored data connectivity

23.2033GPPPolicy and charging control architectureRelease 17TS

There are two deployment scenarios for usage reporting for sponsored data connectivity. The Sponsor Identifier and Application Service Provider Identifier are provided for sponsored services to the PCRF from the AF over the Rx interface.

In the first scenario the PCRF assigns a service specific Charging Key for a sponsored IP flow. The Charging key is used by the PCEF/TDF to generate separate accounting records for offline charging and and/or usage data records for online charging for the sponsored flows. Correlation of accounting records and usage data records from multiple users per sponsor and/or application service provider is then performed using the charging key.

In a second scenario the Sponsor Identifier and Application Service Provider Identity is included in PCC/ADC rules from the PCRF to the PCEF/TDF as defined in clause 6.3.1. For this scenario the same Charging Key may be used both for IP flows that are sponsored and for flows that are not sponsored. Accounting records generated by the PCEF/TDF for offline charging include the Sponsor Identity and the Application Service Provider Identity. Correlation of accounting records from multiple users per sponsor and/or application service provider can then be based on Sponsor Identity and Application Service Provider Identity instead of the Charging Key. Usage reporting for online charging including Sponsor Identity and Application Service Provider Identity has not been specified in this release of the specification. PCC/ADC rules that include a Sponsor Identity and an Application Service Provider Identity should include a Charging Method that indicates offline charging.

Annex P (normative):
Fixed Broadband Access Interworking with EPC

This annex specifies the enhancement to PCC framework for supporting dynamic QoS interworking with Policy Framework defined by Broadband Forum.