Description
The Content Provider Charging Function (CPCF) is a specialized network element defined within the 3GPP architecture to facilitate charging for services that involve third-party content. It acts as a mediator between external content providers and the mobile operator's core charging infrastructure, specifically the Online Charging System (OCS) and Offline Charging System (OFCS). The CPCF's primary role is to translate content-specific service usage and events into standardized charging data records (CDRs) or Diameter-based charging messages that the operator's systems can process. This involves identifying the content provider, the type of content (e.g., video stream, game download, sponsored application), and applying the relevant tariff or charging policy agreed upon in the business relationship between the operator and the content provider.
Architecturally, the CPCF is typically positioned within the service layer or as part of a dedicated charging gateway function. It interfaces with application servers (like those in the IP Multimedia Subsystem or IMS) or directly with content delivery platforms to receive notifications about content service initiation, modification, and termination. Key internal components include a policy enforcement module, which applies charging rules based on service identifiers and user profiles, and a mediation function that formats charging information into 3GPP-compliant formats such as Diameter Credit-Control-Request (CCR) and Credit-Control-Answer (CCA) messages for online charging, or creates Charging Data Records (CDRs) for offline charging. The CPCF may also maintain a database or interface with a subscription profile repository to validate user entitlements to specific content services.
In operation, when a user accesses a charged content service, the serving network node (e.g., a Proxy-Call Session Control Function or an application server) sends a charging request to the CPCF. The CPCF authenticates the request, identifies the involved content provider via parameters like the content provider identifier, and determines the applicable charging model—which could be event-based (e.g., a one-time fee for downloading an app), session-based (e.g., charging per minute of video streaming), or volume-based (e.g., charging for data consumed). For online charging, it interacts with the OCS in real-time to check credit and reserve units before allowing the service to proceed. For offline charging, it generates CDRs that are later transferred to the billing domain for invoicing. This separation ensures that content providers can have flexible, customized charging arrangements without requiring deep integration into the operator's core network charging systems.
The CPCF's role is crucial for enabling modern mobile service ecosystems. It supports complex business models such as 'toll-free' or sponsored data, where a content provider pays for the data usage incurred by end-users accessing its service, thereby removing cost barriers for users. It also allows for premium content offerings, where operators can bundle specific content with data plans. By providing a standardized interface (specified in 3GPP TS 32.260 for charging management), the CPCF reduces integration complexity for both operators and content providers, fostering a more vibrant and monetizable mobile content market. Its functionality is often integrated with broader policy and charging control (PCC) architectures to ensure cohesive service delivery and monetization.
Purpose & Motivation
The CPCF was created to address the growing need for mobile operators to effectively monetize third-party content and services delivered over their networks. Prior to its standardization, charging for content was often handled through ad-hoc, proprietary interfaces between content platforms and billing systems, leading to integration challenges, limited scalability, and difficulties in supporting real-time charging scenarios. This hindered the development of innovative service offerings like sponsored data, premium video, and application-based billing. The CPCF provides a standardized, 3GPP-defined mechanism to bridge this gap, enabling clear, auditable, and flexible financial settlements between operators and content providers.
Historically, as mobile networks evolved from primarily voice-centric to data-centric platforms with the introduction of 3G and later 4G, the value shifted towards over-the-top (OTT) content and applications. Operators sought to move beyond being mere 'bit pipes' and participate in the revenue streams generated by content. The CPCF, introduced in 3GPP Release 5 alongside the IP Multimedia Subsystem (IMS), was part of a broader framework to enable service-based charging. It solved the problem of how to attribute network usage and service consumption to specific content providers in a standardized way, allowing for sophisticated charging models like reverse billing (where the provider pays) or split billing.
The technology addresses limitations of previous approaches by decoupling content charging logic from core network charging. Instead of requiring every content provider to directly interface with complex telecom charging systems like the OCS, the CPCF acts as a unified gateway. This simplifies the business and technical onboarding process for content providers, reduces operator overhead, and ensures that charging data conforms to 3GPP standards for consistency and reliability in billing. It enables operators to offer new, competitive service packages and partnerships, ultimately driving data usage and customer satisfaction.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (34 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-5, normative work from Rel-15.
In Release 15, the CPCF was enhanced to support more detailed UE location descriptions specifically for IMS charging when the UE is connected over WLAN access. Furthermore, editorial issues regarding the Access Network Charging Identifier were resolved to ensure clarity and consistency in the charging data.
In Release 16, key enhancements for the CPCF included the formal introduction of a service-based charging interface for IMS, refinements to the description of volume-based charging within IMS, and improved mechanisms for CHF selection to support IMS charging. These updates built upon the existing architecture, which already supported charging per media component and correlation between transport, service, and content charging levels.
In Release 17, the CPCF saw significant updates primarily focused on integrating IMS (IP Multimedia Subsystem) with the converged charging architecture. This included the introduction of a new service-based architecture for offline charging and the addition of specific IMS converged charging information and data descriptions. These enhancements clarified charging service selection and updated Charging Data Record (CDR) handling procedures for IMS nodes within the converged charging framework.
- Adding data description for IMS converged charging TS 32.260CR0405
- Add service based architecture for offline charging TS 32.260CR0407
- Add IMS offline only charging information TS 32.260CR0410
- Update of converged charging trigger tables using IMS node TS 32.260CR0412
- Addition of converged charging IMS information TS 32.260CR0413
- Clarify Charging service selection TS 32.260CR0415
+ 9 more changes
In Release 18, the key new feature for the Content Provider Charging Function (CPCF) was the introduction of a duration-based charging principle specifically for the IMS data channel. This included defining a corresponding termination process for this type of charging. Additionally, the release introduced enhanced IMS Charging Diagnostics capabilities.
In Release 19, the CPCF was enhanced with new charging principles and information models to support emerging services. Specifically, the standard introduced dedicated charging support for IMS Data Channel application downloads, Avatar communication, and direct UE-to-UE communication via satellite. These additions define the necessary charging triggers, information elements, and message flows for these new service paradigms.
- Rel-19 CR 32.260 Support duration-based charging for standalone IMS data channel TS 32.260CR0438
- Rel-19 CR 32.260 Charging architecture for IMS DC application download charging charging TS 32.260CR0439
- Rel-19 CR 32.260 Charging principle for IMS DC application download charging TS 32.260CR0440
- Rel-19 CR 32.260 Charging information for IMS DC application download charging TS 32.260CR0441
- Add charging principle for UE-satellite-UE communication TS 32.260CR0443
- Add charging trigger and charging information for UE-satellite-UE communication TS 32.260CR0444
+ 3 more changes
Explore further
Broader topics and technologies where CPCF plays a role.
Defining Specifications
3GPP specifications that define or reference CPCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.815 v1500 | IMS Charging Implications | Rel-5 |
| TS 32.260 vj10 | IMS Charging Management | Rel-19 |