Description
The Charging Collection Function (CCF) is a critical component within the 3GPP charging architecture, specifically part of the Offline Charging System (OFCS). Its primary role is to act as a central collection point for Charging Data Records (CDRs) generated by various network functions (NFs) involved in a subscriber's session. These NFs include the Serving GPRS Support Node (SGSN), Gateway GPRS Support Node (GGSN), Call Session Control Function (CSCF), and later evolved nodes like the Mobility Management Entity (MME), Serving Gateway (S-GW), and Packet Data Network Gateway (P-GW). The CCF receives these CDRs via standardized interfaces, primarily using the Rf reference point based on the Diameter protocol.
Architecturally, the CCF sits between the network elements generating charging information and the Billing Domain (BD). Upon receiving CDRs, the CCF performs several key processing steps. First, it performs correlation, which involves linking multiple partial CDRs generated by different network nodes for a single subscriber session (e.g., a voice call or data session) into a single, coherent record. This is crucial because a session may traverse multiple network domains (e.g., access, core). The CCF uses correlation identifiers provided within the CDRs to perform this task accurately.
After correlation, the CCF formats and consolidates the records. It may apply validation checks to ensure data integrity and completeness. The processed and aggregated CDRs are then forwarded to the Billing Domain for rating, invoicing, and settlement. The CCF's operation can be session-based, where it collects records for the duration of a service, or event-based, for one-time transactions. Its design ensures reliability, often involving mechanisms to handle CDR storage, duplication detection, and guaranteed delivery to prevent revenue loss.
In the evolved 5G architecture, while the term CCF is less frequently used in its original form, its functional responsibilities are distributed and evolved within the Charging Function (CHF) as part of the 5G Charging Framework. However, the core principles of collection, correlation, and forwarding of charging information remain fundamental. The CCF's implementation is vital for supporting complex charging scenarios, including those for roaming, inter-operator settlements, and the detailed accounting required for service-based architectures and network slicing.
Purpose & Motivation
The CCF was created to address the growing complexity of charging in mobile networks, especially with the introduction of packet-switched data services in 3GPP Release 99 (UMTS). Prior circuit-switched systems had relatively straightforward charging models based on call duration. The advent of GPRS and later IP Multimedia Subsystem (IMS) services introduced multi-session, multi-service, and multi-operator scenarios where charging data was generated by numerous, geographically distributed network nodes. Without a centralized collection and correlation function, it would be nearly impossible to accurately reconstruct a complete billing record for a single user's activity, leading to billing errors, revenue leakage, and an inability to support advanced tariff models.
The CCF solved the problem of fragmented charging information. It provided a standardized, reliable mechanism to gather CDRs from all involved network functions, correlate them into a unified session record, and deliver them securely to the billing system. This enabled operators to implement detailed, accurate billing for new data services like internet browsing, video streaming, and IMS-based voice (VoIP). It also became foundational for inter-operator accounting in roaming scenarios, where charging data must be exchanged between home and visited networks.
Furthermore, the CCF's introduction formalized the offline charging architecture within 3GPP, separating the real-time charging control (handled by the Online Charging System) from the post-event billing data collection. This separation allowed for scalable, high-performance billing systems capable of handling the massive volume of CDRs generated in modern mobile networks. Its evolution has been driven by the need to support ever-more complex services, quality-of-service (QoS) differentiated charging, and ultimately the service-based architecture of 5G, where its functions are integrated into a more flexible Charging Function.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (51 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Charging Collection Function (CCF) was enhanced to improve the UE location description for IMS charging when the user is connected over a WLAN access network. Additionally, the release resolved editorial notes regarding the Access Network charging identifier to ensure consistent and clear application within the charging framework.
In Release 16, the enhancements for the Charging Collection Function (CCF) primarily focused on IMS service-based charging, introducing a dedicated IMS charging interface and refining the CHF selection mechanism for IMS. The updates also provided a more detailed general description of IMS charging and clarified the procedures for IMS charging triggers. Furthermore, specific improvements were made to the description of volume-based charging within the IMS framework.
In Release 17, the CCF saw a primary expansion with the introduction of a new Service-Based Architecture for offline charging and the specific architectural integration for IMS converged charging. This release defined new charging data descriptions and information elements specifically for IMS within the converged charging framework, and updated the principles and handling of Charging Data Records (CDRs) for this context. Furthermore, enhancements were made to clarify charging service selection and update converged charging trigger tables utilizing the IMS node.
- 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 Charging Collection Function (CCF) was enhanced to support a new duration-based charging principle specifically for the IMS data channel, including defined termination processes for this method. The release also provided clarifications on the CCF's role in service publish scenarios. Furthermore, improvements were made for IMS Charging Diagnostics to aid in troubleshooting.
In Release 19, the Charging Collection Function (CCF) was enhanced to support new service-specific charging principles and information for IMS Data Channel application download, Avatar communication, and UE-satellite-UE communication. It also introduced new charging data types and OpenAPI extensions to enable converged charging for Ranging and Sidelink Positioning services. Furthermore, the release added charging support for AIoT services and introduced attributes for charging Layer 3 multi-hop ProSe UE-to-UE relay communication.
- 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
+ 19 more changes
Explore further
Broader topics and technologies where CCF plays a role.
Defining Specifications
3GPP specifications that define or reference CCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.066 vj00 | Mobile Number Portability Technical Realization | Rel-19 |
| TS 23.125 v1700 | Flow Based Charging Architecture | Rel-7 |
| TS 23.205 vj00 | Bearer Independent CS Core Network Stage 2 | Rel-19 |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 |
| TS 23.234 vd10 | 3GPP-WLAN Interworking Index | Rel-13 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 23.804 v1700 | SMS/MMS over IP Access Support | Rel-7 |
| TS 23.815 v1500 | IMS Charging Implications | Rel-5 |
| TR 23.958 vj00 | EDGEAPP alignment with ETSI MEC and GSMA OP | Rel-19 |
| TR 23.979 vj00 | PoC over 3GPP Systems Architectural Requirements | Rel-19 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 28.849 vj10 | CAPIF Phase2 Charging Study | Rel-19 |
| TS 28.879 vj10 | OAM for Service Management Exposure Study | Rel-19 |
| TS 29.078 vj00 | CAMEL Phase 4 CAP Specification | Rel-19 |
| TS 29.222 vj40 | Common API Framework (CAPIF) for 3GPP Northbound APIs | Rel-19 |
| TS 29.234 vb20 | WLAN-3GPP Interworking Stage-3 Protocol | Rel-11 |
| TS 29.819 vd00 | Diameter Base Protocol Update Analysis | Rel-13 |
| TS 31.115 vj00 | Secured Packet Structure for UICC Applications | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.254 vj21 | Charging for Northbound APIs | Rel-19 |
| TS 32.260 vj10 | IMS Charging Management | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.278 vj00 | Monitoring Events Offline Charging Specification | Rel-19 |
| TS 32.280 vj00 | Advice of Charge (AoC) Framework | Rel-19 |
| TS 32.291 vj40 | Charging Management: Service-Based Interface Protocol | Rel-19 |
| TS 33.122 vj20 | Security Architecture for CAPIF | Rel-19 |
| TS 33.700 | 3GPP TR 33.700 | R99 |
| TS 33.790 vj10 | Security for Next-Gen Real-Time Communication Phase 2 | Rel-19 |
| TS 36.742 vf00 | SON for Enhanced Coordinated Multi-Point (eCoMP) | Rel-15 |