Session Transfer Identifier

Description

The Session Transfer Identifier (STI) is a critical parameter within the 3GPP IP Multimedia Subsystem (IMS) architecture, specifically defined for service continuity mechanisms. It is a globally unique identifier assigned to a multimedia session (e.g., a voice or video call) at the point where a session transfer procedure is initiated. The primary role of the STI is to correlate the original session (the session to be transferred) with the new, replacing session that is established on the target device or access network. This correlation is essential for network entities to correctly anchor, control, and bill the continuous service.

Architecturally, the STI is generated and managed by the Service Centralization and Continuity Application Server (SCC AS), which is the central node for IMS Service Continuity (ISC). When a user decides to transfer an ongoing session from one User Equipment (UE) to another (e.g., from a smartphone to a tablet) or between different access types (e.g., from LTE to Wi-Fi), the SCC AS initiates the transfer procedure. As part of this, it generates a unique STI and includes it in the SIP INVITE request used to establish the new session leg towards the target. This STI is also communicated back to the source leg and stored in context.

The identifier works by being carried within SIP signaling, typically in dedicated header fields or SIP URI parameters as specified in relevant TS 24.237 and TS 24.294. All involved IMS nodes, including the SCC AS, Proxy-CSCF (P-CSCF), and Serving-CSCF (S-CSCF), inspect and process the STI to identify the session transfer context. This allows the SCC AS to perform key functions like session anchoring, where it remains in the media path to facilitate the transfer, and to execute the precise moment of switching the remote party's media flow from the source to the target leg. The STI ensures stateful handling, preventing issues like duplicate sessions or incorrect teardown of the original session, thereby maintaining a single, logical session from the perspective of the remote party and billing systems.

Purpose & Motivation

The STI was created to solve the problem of seamless session mobility in IMS-based networks. Before its standardization, transferring an active multimedia session between devices or networks was problematic, often requiring the user to hang up and redial, leading to service interruption. The driving force was the desire for a "follow-me" user experience where services like voice calls could move with the user across different terminals and access technologies without dropping.

It addresses the core technical challenge of correlating two distinct SIP dialogs (the original session and the new session) as part of a single user service instance. Without a unique identifier like the STI, network servers would perceive the new session establishment as an entirely separate call, leading to confusion in service logic, charging, and potentially causing the remote party to see two simultaneous call legs. The STI, introduced as part of the IMS Service Continuity (ISC) framework from Release 8, provided the necessary glue. It evolved from earlier concepts like Voice Call Continuity (VCC) but was generalized for all multimedia sessions within IMS. Its creation was motivated by the convergence of fixed, mobile, and corporate networks under a single IMS core, demanding robust and standardized mobility management for premium telephony and conversational video services.