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

Glossary term · Core Network

IMS termination

IP Multimedia Subsystem Termination

Core Network →

IMS termination is the scenario where an incoming IMS session is terminated entirely in the IMS/PS domain without involving the CS domain on the terminating side, defining delivery to IMS-capable UEs versus CS fallback.

Introduced
Rel-7
Where
Services › IMS
Specifications
2 specs
IMS termination Description Purpose Neighbours Specifications

Description

IMS termination describes the terminating leg of a session in which the incoming session is delivered to the callee through the IP Multimedia Subsystem (IMS) and the Packet Switched (PS) domain, with no involvement of the Circuit Switched (CS) domain on the terminating side. It is the counterpart to IMS origination and is one of the fundamental session-delivery scenarios defined in 3GPP's IMS service centralization and continuity work (ICS), specified in TS 23.279 and TS 23.811. The concept matters because it determines whether a terminating user is reached via a pure IMS path (VoLTE, VoWiFi, or IMS over PS) or whether the session must be routed through CS fallback or a CS access leg.

Architecturally, IMS termination involves the terminating S-CSCF, which receives the initial INVITE from the originating side (via the I-CSCF), applies terminating service logic through the Service Centralization and Continuity Application Server (SCC AS), and routes the session to the registered contact of the callee. The SCC AS is the key functional entity: it maintains the state of the UE's access legs (PS, CS, and potentially multiple registrations) and decides which access leg to use for termination. When the UE is IMS-registered over PS access, the SCC AS selects the PS access leg and the session is delivered via the P-CSCF and the established IP-CAN bearer. The CS domain is not consulted, so no MSC/MGCF anchoring is required for the terminating part.

The definition's emphasis on 'the CS domain is not involved in the terminating part' is significant because it distinguishes IMS termination from hybrid scenarios such as SRVCC or ICS where the terminating leg may be served over CS access. In a pure IMS termination, the terminating UE must have an active IMS registration and a suitable PS bearer (e.g., QCI 1 for conversational voice, QCI 5 for SIP signalling). The P-CSCF performs policy and charging interactions via the PCRF/PCF, and the S-CSCF enforces terminating initial filter criteria (iFC) to invoke application servers such as MMTel or SCC AS.

Session setup in IMS termination follows the standard SIP signalling path: the originating network sends the INVITE to the terminating I-CSCF, which queries the HSS for the S-CSCF assignment, then forwards to the S-CSCF. The S-CSCF evaluates iFCs, invokes the SCC AS, and the SCC AS performs access domain selection (ADS). If the UE is reachable over PS, the INVITE is forwarded to the registered P-CSCF contact and then to the UE. Media is negotiated via SDP offer/answer, and the bearer is established or modified through the PCRF/PCF and the PGW/SMF. The entire terminating path stays within IMS/PS.

IMS termination is central to the migration from CS to all-IP voice. It underpins VoLTE, VoNR, and VoWiFi service delivery, and it is the baseline assumption for IMS-based supplementary services. Understanding it is essential for engineers designing session routing, access domain selection, and service continuity, because it defines the 'clean' all-IP terminating case against which fallback and SRVCC scenarios are contrasted.

Purpose & Motivation

IMS termination exists to define and standardize the all-IP terminating session delivery model introduced with the IMS. Before IMS, terminating calls were handled by the CS domain (MSC/MGCF), and the network had no standardized way to describe or implement a terminating session that bypassed CS entirely. As operators began deploying IMS for voice over PS (culminating in VoLTE), 3GPP needed precise terminology to distinguish pure IMS terminating delivery from CS fallback and SRVCC scenarios. TS 23.279 and TS 23.811 provide that terminology within the IMS service centralization and continuity framework.

The concept solves the ambiguity in multi-access environments where a user may be reachable via CS, PS, or both. By defining IMS termination as the case where CS is not involved on the terminating side, the standards enable clear architectural decisions: the SCC AS can select the PS access leg, the PCRF/PCF can apply IMS-specific policy, and the operator can offer IMS services without CS anchoring. This supports service continuity, consistent supplementary service behaviour, and efficient use of PS bearers.

Historically, the definition has been remarkably stable. From Rel-7 through Rel-19 the wording is essentially identical, reflecting that the fundamental concept of all-IP terminating delivery has not changed even as the underlying access technologies evolved from HSPA to LTE and 5G. The persistence of the term across thirteen releases underscores its role as a foundational reference point for IMS architecture.

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-7 Initial

Initial definition introduced in TS 23.279/23.811 within the IMS service centralization and continuity work: an IMS session terminated in the IMS/PS domain with the CS domain not involved in the terminating part.

Definition text carried over unchanged; context expanded with LTE/EPS access and the emergence of VoLTE as the primary application of IMS termination.

Definition unchanged; IMS termination continued to apply as SRVCC and ICS enhancements matured.

Definition unchanged; the concept remained the baseline all-IP terminating case.

Definition unchanged; carried forward as IMS centralization work stabilized.

Definition unchanged; the term continued to anchor terminating session delivery discussions.

Definition unchanged; carried over as VoLTE deployments scaled.

Definition unchanged; the concept persisted through further IMS service evolution.

Definition unchanged; carried forward into the 5G era as IMS over 5GS was introduced.

Definition unchanged; the term continued to apply to IMS termination over 5G access.

Definition text is identical in substance to prior releases (only whitespace/line-wrapping differs); no semantic change to the concept.

Definition unchanged; carried over as IMS continued to serve as the voice/session platform.

Definition text remains identical in substance; the term persists as a stable reference concept.

Defining Specifications

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

SpecificationTitleRelease
TS 23.279 vj00 Combined CS and IMS Services (CSI) Architecture Rel-19 read
TS 23.811 v800 SMS and IM Interworking Study Rel-8 read