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

Glossary term · Services

IMS origination

IMS origination

Services →

IMS origination is the scenario in which a UE initiates an IMS session while the CS domain is not involved in the originating part, a key concept for IMS service continuity and interworking with CS networks.

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

Description

IMS origination refers to the case where a User Equipment (UE) initiates one or more IMS sessions and the Circuit Switched (CS) domain is not involved in the originating part of those sessions. This definition, found in 3GPP specifications 23.279 (Combining Circuit Switched and IMS Services) and 23.811 (Service Continuity), is fundamental to understanding how IMS services are established and how they interact with legacy CS networks.

In the IMS architecture, sessions are initiated using SIP signalling. When a UE originates an IMS session, it sends a SIP INVITE (for session-based services) or other SIP request through the IMS core, typically via the P-CSCF and S-CSCF. The phrase "CS domain is not involved in the originating part" means that the session setup does not rely on CS signalling or CS bearer establishment at the originating side. This distinguishes IMS origination from scenarios where a session might be initiated in the CS domain and then transferred to IMS, or where CS and IMS are combined for a service.

The concept is particularly important in the context of IMS Centralised Services (ICS) and Service Continuity. In ICS, a UE can use both CS and IMS domains, and the network provides service continuity when the UE moves between domains. IMS origination describes the pure IMS case, which serves as a baseline for comparing more complex hybrid scenarios. It is also relevant to the evaluation of service continuity procedures, such as Single Radio Voice Call Continuity (SRVCC), where a session originated in IMS may later be transferred to the CS domain.

Specification 23.279 defines the requirements for combining CS and IMS services, including the ability for a UE to originate sessions in either domain. 23.811 covers service continuity, including the procedures for transitioning between domains. The definition of IMS origination helps specify the behaviour of the UE and network when the session starts in IMS, ensuring that the CS domain is not inadvertently involved in the originating leg.

From an implementation perspective, IMS origination requires the UE to be registered with IMS and to have IP connectivity. The session setup follows standard IMS procedures, including resource reservation and policy control. The absence of CS involvement in the originating part simplifies the signalling and allows the session to benefit from IMS features such as multimedia and presence. Understanding this concept is essential for engineers working on IMS service design, interworking, and continuity.

Purpose & Motivation

IMS origination exists as a defined concept to clearly delineate the pure IMS session initiation scenario from hybrid CS-IMS scenarios. As networks evolved from CS-only to IMS-based, operators needed precise terminology to describe how sessions are established and how they can be transferred between domains. The term provides that precision.

It solves the problem of ambiguity in service continuity and ICS specifications. When describing procedures such as SRVCC or reverse SRVCC, it is crucial to know whether the originating part of a session involved the CS domain. By defining IMS origination, 3GPP enables unambiguous specification of UE and network behaviour, which is essential for interoperability and testing.

The motivation stems from the migration to all-IP networks. Operators wanted to offer IMS services while maintaining continuity with legacy CS networks. The concept of IMS origination helps ensure that IMS sessions are set up correctly and that continuity procedures can be applied when needed. It also supports the goal of a smooth transition from CS to IMS, allowing UEs to use IMS for new services while still falling back to CS when necessary.

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 of IMS origination as the case where a UE initiates an IMS session and the CS domain is not involved in the originating part. This established the concept for ICS and service continuity work.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition text is identical to Rel-7; only formatting (line breaks) differs, with no substantive change.

Definition carried over unchanged from Rel-7.

Definition text is identical to Rel-7; only formatting (line breaks) differs, with no substantive change.

Defining Specifications

3GPP specifications that define or reference IMS origination, 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