IP Multimedia Service Switching Function

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.

Key Features

• Protocol interworking between SIP (IMS) and CAMEL Application Part (CAP)
• Maps IMS session states (SIP dialogs) to CAMEL call state models
• Appears as an IMS Application Server (AS) to the S-CSCF
• Retrieves CAMEL subscription data from HSS via Sh interface
• Enables gsmSCF to control charging, routing, and user interaction for IMS sessions
• Supports legacy CAMEL phases (e.g., CAMEL Phase 2, 3, 4) for IMS service control

Evolution Across Releases

Defining Specifications