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

Glossary term · Core Network

ICCF

IMS CS Control Function

Core Network →

ICCF is a functional entity that enables IMS services to be controlled and accessed from legacy circuit-switched domains, bridging CS access with IMS service delivery to support IMS Centralized Services and consistent service experience across access types.

Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
2 specs
ICCF Description Purpose Neighbours Specifications

Description

The IMS CS Control Function (ICCF) is a key functional entity defined within the 3GPP IMS Centralized Services (ICS) architecture. ICS was introduced to allow operators to deliver a consistent set of IMS-based services to subscribers regardless of whether they access the network via a CS domain (e.g., GSM/UMTS circuit-switched voice) or a PS/IMS domain. The ICCF acts as the control point that enables IMS services to be invoked and controlled for users connected through the CS domain.

Architecturally, the ICCF sits between the CS domain and the IMS core. When a user attached via CS access originates or receives a session, the ICCF is responsible for anchoring that session into IMS so that IMS service logic (such as supplementary services, service centralization, and application servers) can be applied. It interacts with the MSC Server enhanced for ICS, the IMS core entities (such as the S-CSCF and application servers), and the user's service profile. The ICCF uses control signaling to coordinate call handling between the CS domain and IMS, ensuring that service invocation and session control remain consistent.

The ICCF performs several critical functions. It manages the mapping between CS-domain call control signaling and IMS session control, allowing IMS application servers to control CS-originated sessions. It supports service centralization by ensuring that the user's services are hosted and executed in IMS even when the access is CS. It also handles the routing of session control toward the appropriate IMS entities and coordinates with the MSC Server for call establishment and release. This enables features such as a single set of supplementary services, consistent service configuration, and unified service control across access technologies.

The introduction of ICCF and the broader ICS architecture was motivated by the operator desire to migrate service control to IMS while still supporting large installed bases of CS-only or CS-preferred devices. Rather than duplicating service logic in the CS domain, the ICCF allows the CS domain to act as an access mechanism while IMS remains the service control layer. This supports a smooth evolution path toward all-IP service delivery.

In the 3GPP specifications, the ICCF is described in the ICS study and stage-2 documents (notably 23.826 and 23.892). It is closely related to the MSC Server enhanced for ICS, the IMS Service Centralization and Continuity Application Server (SCC AS), and the overall ICS architecture. The ICCF remains an important reference concept for understanding how 3GPP bridged legacy CS access with IMS-based service control during the transition to all-IP networks.

Purpose & Motivation

The ICCF exists to solve the problem of delivering IMS-based services to subscribers who access the network through the circuit-switched domain. Before ICS, operators faced a fragmented service landscape: IMS services were available only to users on PS/IMS-capable access, while CS users relied on separate, duplicated service logic in the CS core. This duplication increased operational cost and created inconsistent user experiences across access types.

By introducing the ICCF, 3GPP enabled a centralized service control model in which IMS remains the single point of service execution, while the CS domain serves purely as an access path. This allowed operators to begin migrating service control to IMS without forcing immediate all-IP device upgrades, protecting investments in legacy devices and networks. It also simplified service provisioning and reduced the need to maintain parallel service implementations.

The ICCF was motivated by the broader industry goal of network evolution toward IMS and all-IP. It provided a standards-based mechanism to bridge two generations of technology, ensuring service continuity and consistency during the transition period. This made it possible for operators to offer a unified service set while progressively modernizing their networks.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial definition and introduction of the ICCF within the IMS Centralized Services architecture. Rel-8 established the functional entity, its role in bridging CS access with IMS service control, and its interactions with the MSC Server enhanced for ICS and IMS core entities.

The ICCF definition carried over unchanged from Rel-8; no revision to the term's definition text is indicated in the available material.

Defining Specifications

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

SpecificationTitleRelease
TS 23.826 v900 Voice Call Continuity for Emergency Calls Rel-9 read
TS 23.892 v801 IMS Centralized Services Feasibility Study Rel-8 read