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

Glossary term · Core Network

IM-SSF

IP Multimedia Service Switching Function

Core Network →

IM-SSF is a core network gateway that translates between IMS SIP signaling and CAMEL protocols to enable legacy intelligent network services for subscribers using the IP Multimedia Subsystem.

Introduced
Rel-5
Where
Core Network › Evolved Packet Core
Specifications
5 specs
IM-SSF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The IP Multimedia Service Switching Function (IM-SSF) is a critical interworking node defined within the 3GPP IMS architecture. Its primary role is to bridge the SIP-based service control paradigm of IMS and the IN/CAMEL-based service control used in traditional GSM, UMTS, and GPRS networks. The IM-SSF appears as an Application Server (AS) within the IMS core, receiving SIP messages via the IMS Service Control (ISC) interface from a Serving-Call Session Control Function (S-CSCF).

Internally, the IM-SSF contains a CAMEL Service Switching Function (SSF) and a Call State Model. When triggered for a session, it maps the SIP dialog state (e.g., INVITE, 200 OK, BYE) onto an equivalent CAMEL call state model. It then formulates and sends corresponding CAMEL Application Part (CAP) operations (e.g., InitialDP, ApplyCharging, RequestReportBCSMEvent) to an external CAMEL Service Control Function (gsmSCF or SCP). The gsmSCF, hosting the service logic, returns CAP instructions (e.g., Continue, Connect, ApplyChargingReport) which the IM-SSF translates back into appropriate SIP message manipulations or policy enforcement actions within the IMS session.

Architecturally, the IM-SSF interfaces with the S-CSCF over ISC (using SIP), with the gsmSCF over the CAP interface, and with the Home Subscriber Server (HSS) over the Sh interface to retrieve CAMEL subscription information. It may also interact with a Media Resource Function Controller (MRFC) for announcements. By performing this protocol translation and state mapping, the IM-SSF allows a gsmSCF to control IMS sessions as if they were traditional circuit-switched calls, enabling service continuity and investment protection for network operators migrating to IMS.

Purpose & Motivation

The IM-SSF was created to solve a critical business and technical challenge during the transition from circuit-switched telephony to all-IP IMS networks. Operators had made massive investments in Intelligent Network (IN) platforms and CAMEL-based services (prepaid, virtual private networks, number translation, freephone). These services represented significant revenue streams and customer features. The introduction of IMS, with its native SIP service layer, threatened to render these legacy services obsolete, requiring a costly and risky redevelopment.

The IM-SSF provides a strategic migration path. It was motivated by the need for service continuity, allowing subscribers to use the same familiar services (like prepaid billing for voice calls) whether they are on a legacy CS call or an IMS-based VoLTE/VoWiFi call. It addresses the fundamental incompatibility between the event-driven, dialog-oriented SIP protocol and the call-stateful, transaction-oriented CAMEL protocol.

By standardizing the IM-SSF, 3GPP enabled operators to deploy IMS and introduce new SIP-based services gradually, while protecting their existing CAMEL service infrastructure. This reduced time-to-market for IMS deployments and lowered the financial and operational risk associated with a full, simultaneous replacement of both the network core and the service layer.

What changed in its specifications

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

TS 23.218Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.218: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.218 →
TS 28.705Rel-13 → Rel-14

Rel-14 brings only minor changes to TS 28.705: 2 clauses changed, with no change attributed to a release feature.

Full comparison in TS 28.705 →

Technology family

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW

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 7 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-5 introduced

IM-SSF is specified for the first time in Rel-5: a SIP application server interfacing SIP to CAP, hosting CAMEL state models, with Si interface to HSS and CAP mapping in TS 23.278/29.278.

  • “CAMEL functional entity that provides the interworking between SIP session control and the CAMEL state models.” TS 23.278 v5.6.0
  • “The IM‑SSF is a SIP Application Server that interfaces SIP to CAP.” TS 23.278 v5.6.0
  • “The IM-SSF shall map the CAP operations intended for the MRFC into a SIP based protocol” TS 29.278 v5.4.0
Rel-6 specification text

The Rel-6 text changes how the HSS interacts with the IM-SSF: HSS rather than HLR sends IM-CSI notifications, and the IM-SSF address handling and MAP interfaces are respecified.

  • “The IMSI shall be used for querying the HSS for CAMEL Subscription Information data via a MAP interface.” TS 23.278 v6.2.0
  • “The HSS shall overwrite the existing IM‑SSF address with the IM‑SSF address associated with the new S‑CSCF name.” TS 23.278 v6.2.0
  • “The Dh interface is between the SLF and the SIP Application Servers, the OSA SCS, and the IM-SSF” TS 23.218 v6.4.0
Rel-7 specification text

The gsmSCF Address information element, which identifies the interrogating IM-SSF, now must be in international E.164 format.

Rel-11 specification text

The IM-SSF functional architecture now covers CAMEL interactions with the Transit Function in addition to the S-CSCF.

  • “support CAMEL interactions with the S-CSCF and the Transit Function in the IP Multimedia Subsystem” TS 23.218 v11.6.0
Rel-12 specification text

The HSS–IM-SSF interface was extended so IMS CAMEL information is transferred over both Si and Sh, with Diameter added for the IM-SSF/HSS interface.

  • “The Si and the Sh interfaces between HSS and the IM-SSF Application Server are used for transferring IMS CAMEL specific information.” TS 23.218 v12.3.0
  • “Interface IM-SSF / HSS with Diameter” TS 23.218 v12.3.0
  • “IM-SSF Application Servers (downloaded via Si or Sh interface);” TS 23.218 v12.3.0
Rel-13 1 CR

A Rel-13 change request to TS 23.228 addressed the interface between the IM-SSF and the HSS.

  • Interface between IM-SSF and HSS TS 23.228CR1095
Rel-15 2 CRs

IM-SSF gained support for 5G location information, with a locationInformation5GS IE that is to be absent if the UE did not access via 5GS and IM-SSF.

  • “The locationInformation5GS IE should be absent if UE did not access via 5GS and IM-SSF.” TS 29.002 v15.7.0
  • Location Information used by IM-SSF in 5G TS 29.002CR1245
  • Correction on Location Information used by IM-SSF in 5G TS 29.002CR1253

Defining Specifications

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

SpecificationTitleRelease
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.278 vj00 CAMEL for IMS Stage 2 Specification Rel-19 read
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19 read
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read