Skip to content

Charging interworking function

Bridge charging systems across network generations through seamless protocol interworking.

The Slicce Charging IWF enables real-time charging interoperability across INAP, CAMEL, Diameter, and HTTP/2-based interfaces. Through flexible protocol conversion and mediation, it unifies charging operations across different network technologies.

Capabilities

Different Networks. One Charging Logic.

Handling of simultaneous conversion schemes

Supports conversion mode for any to any simultaneous conversion schemes for CAP, INAP, Diameter CC and HTTP/2 N28/N40/Nchf or proxy mode for same protocol mediation. (E.g. CAPv1 to CAPv2)

Cross-technology billing

Enables sending CAP and INAP signals to the same Diameter element, allowing two networks with different technologies to operate with one single billing system (OCS).

Programmable via a simple scripting

Provides ability to quickly and easily implement conversion and mediation call flows using simple scripting language to shorten time-to-market.

Real-time control using the Diameter protocol

Extends standard Diameter Credit Control AVP set to enables complete call control by any connected OCS to the southbound protocols.

Architecture

Bridging Protocols. Connecting Generations.

CHF-IWF conversion & mediation engine protocol stack diagram

What makes CHF-IWF unique is its support for simultaneous conversion of both technologies within the same CAMEL SCP, and unifying the converted signaling to the same billing server (OCS). This enables operators managing multi-technology and multi-generational networks to use one billing system for all of their different network infrastructures, saving huge expenditures on upgrading entire network infrastructures or purchasing entirely new billing systems.

Another feature that makes the CHF-IWF special is the ability to customize the scenarios and the interfaces involved in a specific call flow. For example, you could easily translate an IDP message (service request) into a Diameter request toward a third-party system.

This approach is much more flexible in comparison with traditional SCP architecture because the solution provider receives a powerful and flexible tool for creating new services without creating any constraint on the development environment he is familiar with. The manufacturer can dramatically decrease time to market while deploying innovative services that will enrich its offering and strengthen competitive standing.

Technical specifications

SCTP

RFC 2960

RFC 3309

MTP

ITU-T Q.700 through Q.707, Q.781, Q.782, Q.791

M2PA

RFC 4165

M3UA

RFC 3332

SCCP

ITU-T Q.711 through Q.714 Connectionless Class 0 & 1

TCAP

ITU-T Q.700 through Q.707, Q.781, Q.782, Q.791

INAP

ETSI ETS 300 374-1

ITU-T Q.1218 CS-1R

HTTP/2

RFC 9113

RFC 7541

CAP

GSM 09.78 (ETSI TS 101 046 - V5.6.0) CAMEL Phase 1

GSM 09.78 (ETSI TS 101 046 - V6.3.0) CAMEL Phase 2

GSM 09.78 (ETSI TS 129 078 - V4.6.0) CAMEL Phase 3

3GPP TS 29.078 V7.3.0 R7, 3GPP TS 29.278 V7.0.0 R7 (IMS) CAMEL Phase 4

Diameter

RFC 4006 - Diameter Credit-Control Application

RFC 3588 / 6733 - Diameter base Protocol

3GPP TS 32.299 - Telecommunication management; Charging management; Diameter charging applications.

Check out some CHF-IWF use cases

Go to the use case page >