Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

IMS-GWF

IMS Gateway Function

Core Network →

IMS-GWF is the IMS Gateway Function, a charging gateway that collects, correlates, and formats charging information from IMS elements for forwarding to the offline billing system.

Introduced
Rel-8
Where
Services
Specifications
4 specs
IMS-GWF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The IMS Gateway Function (IMS-GWF) is a standardized network function responsible for offline charging within the IP Multimedia Subsystem (IMS). It acts as a mediator between various IMS Charging Trigger Functions (CTFs)—such as the P-CSCF, I-CSCF, S-CSCF, Application Servers (AS), and the Media Resource Function Controller (MRFC)—and the network operator's central billing system, known as the Charging Data Function (CDF). The primary role of the IMS-GWF is to collect, aggregate, correlate, and format charging information before delivering it for long-term storage and billing processing.

Architecturally, the IMS-GWF receives charging events via the Rf reference point, which uses the Diameter protocol. Each IMS network element acting as a CTF generates Accounting Request (ACR) messages (Start, Interim, Stop) for a service session. These messages contain details like session identifiers, involved parties, service data volumes, and timestamps. The IMS-GWF processes these Diameter ACR messages. A critical task is correlation: it links multiple charging events from different network elements (e.g., S-CSCF for signaling and an AS for service logic) that all belong to the same end-user session. It uses identifiers like the IMS Charging Identifier (ICID) and Access Network Charging Identifier to perform this correlation.

After correlation and any necessary formatting or consolidation, the IMS-GWF forwards the complete charging information to the CDF via the Ga reference point. The Ga interface typically uses a file-based transfer protocol like FTP or SFTP, and the data is structured according to the 3GPP Charging Data Record (CDR) format defined in specification 32.297. The IMS-GWF may also perform functions like CDR pre-processing, error handling, and load distribution. It ensures that charging data from the real-time IMS environment is reliably converted into standardized records suitable for the offline, batch-oriented billing systems.

In the IMS charging architecture, the IMS-GWF decouples the real-time session control elements from the backend billing infrastructure. This separation allows the IMS core to focus on session delivery while delegating the resource-intensive tasks of charging data collection and formatting to a dedicated gateway. The IMS-GWF is a fundamental component for monetizing IMS services, enabling operators to bill for complex multimedia sessions that may involve voice, video, messaging, and other enriched communication services, based on detailed usage records.

Purpose & Motivation

The IMS-GWF was created to address the need for a standardized, scalable, and reliable offline charging mechanism for the IP Multimedia Subsystem. Prior to IMS, circuit-switched voice networks had well-defined charging mechanisms, but the packet-based, session-oriented nature of IMS introduced new complexities. IMS sessions could involve multiple network elements (different CSCFs, ASs), multiple media components, and dynamic changes mid-session, making it challenging to generate a single, accurate billing record.

The purpose of the IMS-GWF is to solve the problem of charging data collection and correlation in a distributed, multi-vendor IMS environment. Without a centralized gateway, each network element would need to interface directly with the billing system, leading to complexity, potential data loss, and inconsistent record formatting. The IMS-GWF provides a single, logical point of collection. It abstracts the heterogeneity of the IMS core from the billing domain, ensuring that charging records are complete, correlated across different network functions, and delivered in a uniform format.

Its introduction was motivated by the commercial requirement to bill for IMS services. It enables operators to implement flexible charging models (time-based, volume-based, event-based, or combination) for new multimedia services. By standardizing the Rf (collection) and Ga (delivery) interfaces, the IMS-GWF ensures interoperability between equipment from different vendors, which is crucial for the multi-vendor ecosystem of IMS deployments. It forms a core part of the 3GPP offline charging architecture, allowing operators to monetize their IMS investments effectively.

What changed in its specifications

The latest release-to-release comparison of specifications that define IMS-GWF. Each summary describes the whole specification, not only this term.

TS 32.260Rel-18 → Rel-19

Rel-19 adds PS Data Off for IMS Data Channel Service, introducing the Data Channel Signalling Function (DCSF) and its event-based charging with CHF for application download. It also adds IMS data channel charging for standalone and application usage in Next Generation Real-time Communication Phase 2.

Full comparison in TS 32.260 →
TS 32.272Rel-6 → Rel-7

Rel-7 adds new PoC charging procedures for participant number and type, plus new charging fields.

Full comparison in TS 32.272 →

Technology family

Charging architecture · Core Network

  1. R99 CDR, CGF
  2. Rel-5 OCS
  3. Rel-6 ABMF, BD, CDF, CTF, EBCF, OCF, OFCS, RF, SBCF
  4. Rel-8 IMS-GWF
  5. Rel-15 CCS, CHF
  6. Rel-16 CEF

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-8 introduced

In 32260 Rel-8 the online charging flows were reworked so the IMS-GWF/AS jointly exchange Diameter credit control with the OCS, and 32280 introduced the IMS-GWF term and its ISC and Ro reference points.

  • “The IMS-GWF/AS sends a Debit Unit Request (CC-Request-Type=EVENT_REQUEST) to the OCS, requesting units in order to provide the service.” TS 32.260 v8.19.0
  • “Online Charging Reference Point between an AS, MRFC or the IMS-GWF and the OCS” TS 32.280 v8.4.0
  • “An initial SIP Invite Request is received in the S-CSCF. This request is forwarded to the IMS-GWF/AS.” TS 32.260 v8.19.0
Rel-9 specification text

IMS-GWF gains a role in online charging for RTTI tariff information, sending charging information over Ro to the OCS and triggering credit control requests on SIP 200 OK.

  • “For online charging, the AS and the IMS-GWF may send charging information related to the content body of RTTI message over Ro interface to the OCS.” TS 32.260 v9.20.0
  • “the 200 OK answer triggers a Reserve Unit Request (CC-Request-Type =UPDATE_REQUEST) in the IMS-GWF/AS” TS 32.260 v9.20.0
Rel-13 specification text

IMS-GWF gains a role in the new Announcement service, rendering OCS-requested announcements, and its online charging procedures for session release and Reserve Units are specified in more detail.

  • “The AS or the IMS-GWF is responsible for determining the MRF handling the announcement.” TS 32.281 v13.0.0
  • “the OCS may utilize the Announcement service specified in TS 32.281 [41] to request the IMS-GWF or AS to render video or audio announcements” TS 32.260 v13.9.0
  • “the IMS-GWF/AS sends a Reserve Units Request [Terminate] reporting charging information (e.g. user location received in SIP 200 OK)” TS 32.260 v13.9.0
Rel-16 specification text

In Rel-16 the IMS-GWF's announcement handling is respecified to interface with the CHF/OCS in the converged charging architecture instead of having Ro interfaces to the OCS only.

  • “In the IMS online and converged charging architecture specified in TS 32.260 [20], both the AS and the IMS-GWF interfaces the CHF/OCS.” TS 32.281 v16.1.0
  • “both the AS and the IMS-GWF have Ro interfaces to the OCS and are connected to the S-CSCF via the ISC reference point” TS 32.281 v16.1.0
Rel-17 specification text

In TS 32.260 the IMS-GWF is now covered by the Nchf converged charging architecture, valid only with the converged charging method, and appears in CHF CDR content, replacing the Ro/ISC-based online charging text.

  • “except the IMS-GWF for which only the "converged charging" method is valid” TS 32.260 v17.5.0
  • “The IMS Nodes for which this architecture applies are the MRFC, IMS-GWF (connected to S-CSCF using ISC) and SIP AS” TS 32.260 v17.5.0
  • “IMS nodes (except IMS-GWF) may consume offline only charging service via Nchf interface.” TS 32.260 v17.5.0
Rel-19 specification text

IMS-GWF charging now covers UE-Satellite-UE communication: IMS-GWF/AS (CTF) sends a charging data request to CHF with satellite communication charging information when supported.

  • “the IMS-GWF/AS (CTF) sends a charging data request to CHF with charging information about UE-Satellite-UE communication by the trigger events” TS 32.260 v19.3.0

Defining Specifications

3GPP specifications that define or reference IMS-GWF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19 read
TS 32.281 vj00 Announcement Service for Online Charging Rel-19 read