Service Centralization and Continuity Application Server

Description

The Service Centralization and Continuity Application Server (SCC AS) is a critical functional entity within the IP Multimedia Subsystem (IMS) architecture, defined by 3GPP to manage service continuity and centralization for multimedia sessions. It operates as an application server that anchors IMS sessions, particularly those involving voice or video communications, to facilitate seamless handovers between different access technologies, such as transitioning a voice call from LTE (packet-switched) to GSM or UMTS (circuit-switched). The SCC AS achieves this by implementing the IMS Service Continuity procedures, which involve session renegotiation and media path updates to maintain active sessions without interruption. Architecturally, it interfaces with other IMS nodes like the Serving-Call Session Control Function (S-CSCF) for session control and the Home Subscriber Server (HSS) for subscriber data, ensuring it can apply appropriate service logic based on user profiles and network conditions.

In operation, the SCC AS employs mechanisms like Single Radio Voice Call Continuity (SRVCC) and enhanced SRVCC (eSRVCC) to handle mobility events. When a UE moves from a VoLTE-capable LTE coverage area to a legacy 2G/3G network, the SCC AS coordinates with the Mobility Management Entity (MME) and the MSC Server to transfer the session anchor point and update the media path, minimizing service disruption. It manages the Access Transfer Control Function (ATCF) and Access Transfer Gateway (ATGW) in eSRVCC scenarios, which localize the media anchor to reduce handover latency. The SCC AS also supports mid-call features, such as adding or removing media components during a session, by leveraging IMS session control protocols like SIP.

Key components within the SCC AS include logic for session anchoring, continuity management, and interworking with circuit-switched networks via the IMS Centralized Services (ICS) framework. Its role extends beyond handovers to include service centralization, where it acts as a centralized point for applying service logic, ensuring consistent user experiences across multiple devices and access types. This is particularly important for enabling features like call forwarding, simultaneous ringing, and multimedia telephony. By decoupling service execution from access technology, the SCC AS simplifies network evolution and supports the convergence of fixed and mobile services.

Purpose & Motivation

The SCC AS was introduced in 3GPP Release 8 to address the challenge of maintaining service continuity for IMS-based multimedia services as networks evolved towards all-IP architectures like LTE. Prior to its development, voice services were predominantly circuit-switched, and handovers between packet-switched and circuit-switched domains were not standardized, leading to dropped calls during mobility events. The SCC AS solves this by providing a standardized mechanism to anchor IMS sessions, enabling seamless transitions and ensuring that users do not experience interruptions when moving between LTE and legacy networks.

Its creation was motivated by the industry's shift to VoLTE and the need to support rich communication services while leveraging existing 2G/3G infrastructure for coverage. By centralizing service logic, the SCC AS also reduces complexity in the network, allowing operators to deploy new features uniformly across different access technologies. This addresses limitations of earlier approaches, where service continuity was handled in a fragmented manner, often requiring proprietary solutions that hindered interoperability and scalability.