Mavenir’s Charging Control Function (CCF) solves the challenge of collection, aggregation, processing and transfer of charging data from multiple components in an all IP IMS network. Due to the distributed nature of IMS, Charging Data Records (CDRs) are generated from multiple IMS network elements such as Call Session Control Function (CSCF), Application Servers, Session Border Controller (SBC), etc.

The CCF serves as a single point to operator’s billing domain from multiple different components. CCF is mainly used for offline charging and acts as a billing gateway, which is a single node that collects charging data from several network elements in real time, processes that data, generates charging data records (CDRs) and transfers them to the Billing Domain.

With a single, common CCF, mobile operators manage just a single unified interface towards their billing domain, thus eliminating the complexity associated with maintaining reliable links, managing various transfer modes and handling failover mechanisms. Since CCF aggregates charging data from various IMS nodes, it becomes possible for operators to not only correlate that data but also to make decisions regarding the charging data record (CDR) generation and manipulation. 

The CCF acts as a combined Charging Data Function (CDF) and Charging Gateway Function (CGF) but if required can be deployed as standalone CDF or CGF. This provides deployment flexibility for MNO to decide the architecture based on existing OSS/BSS.  The standalone nodes benefits operators who are already invested in charging architecture capable of one of the other functions.

Based on Mavenir''s software-based mOne® convergence platform, the CCF is a highly scalable and flexible platform designed to support charging for various network elements. Similar to other Mavenir products CCF is fully virtualized and software based.

Key Features & Benefits

  • Minimum or No Disruption to existing billing system
  • Flexible CDR design and manipulation rules
  • Interfaces with any IMS /Non IMS network element on Rf
  • Editable/Private AVPs for multivendor environments
  • Support for geo-redundant deployments
  • Multiple Rf i/f support over single address or FQDN