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

Glossary term · Services

IMS Messaging services

IP Multimedia Subsystem Messaging Services

Services →

IMS Messaging services is a family of IMS-based services enabling users to send and receive messages over the IP Multimedia Subsystem, covering immediate, session-based, and deferred delivery modes.

Introduced
Rel-2
Where
Services › Codecs
Specifications
2 specs
IMS Messaging services Description Purpose What changed Neighbours Specifications

Description

IMS Messaging services are a group of services supported by the capabilities of the 3GPP IP Multimedia Subsystem (IMS) as defined in 3GPP TS 22.228. They allow an IMS user to send and receive messages to other users through the operator's IMS core network, leveraging SIP-based session control and the IMS service architecture. The services are specified primarily in 3GPP TS 22.340 (IMS Messaging) and 3GPP TS 26.141 (IMS Messaging Media Handling and Interaction), which together define the service requirements and the media formats and interaction procedures.

The service is composed of one or more messaging types. Immediate messaging provides near-real-time message delivery, where the message is sent to the recipient as soon as it is submitted, without establishing a persistent session. Session based messaging establishes a SIP session between the communicating parties, within which messages are exchanged as part of an ongoing conversational context, similar to a chat session. Deferred delivery messaging stores the message in the network when the recipient is unavailable and delivers it later, providing store-and-forward behavior analogous to traditional messaging services.

Architecturally, IMS Messaging relies on the IMS core elements: the Call Session Control Functions (P-CSCF, I-CSCF, S-CSCF) for registration and session control, the Home Subscriber Server (HSS) for subscriber data, and application servers that host the messaging service logic. The messaging application server may implement the Message Session Relay Protocol (MSRP) for session-based messaging and SIP MESSAGE for immediate messaging. Media handling, including message composition, formats, and interaction with other IMS services, is covered by TS 26.141.

IMS Messaging is significant because it integrates messaging into the same all-IP service architecture used for voice and multimedia telephony, enabling a unified service experience, common authentication and charging, and interoperability with other IMS services. It also allows operators to offer rich, presence-aware, and multimedia-capable messaging without relying solely on circuit-switched or proprietary over-the-top solutions.

Over successive releases, the definition has remained remarkably stable, reflecting the maturity of the service concept. The only notable textual change occurred in Rel-7, where the definition temporarily omitted 'Deferred delivery messaging' from the enumerated types, but this was restored from Rel-8 onward. From Rel-8 to Rel-19 the definition is essentially unchanged, indicating a consolidated and stable specification baseline.

Purpose & Motivation

IMS Messaging exists to provide a standardized, operator-controlled messaging capability within the IP Multimedia Subsystem, so that messaging becomes an integral part of the same all-IP service platform that delivers voice and multimedia telephony. Before IMS messaging, messaging services were fragmented across SMS/MMS in circuit-switched and early packet domains, proprietary instant messaging platforms, and other non-interoperable solutions. This fragmentation made it difficult to offer consistent identity, presence, charging, and policy control across messaging and conversational services.

By defining messaging as an IMS service, 3GPP enables operators to reuse IMS registration, authentication, security, and QoS mechanisms for messaging. It also allows different delivery semantics — immediate, session-based, and deferred — to be offered under a common service umbrella, matching the diverse user expectations from instant chat to store-and-forward messaging. The inclusion of regulatory considerations and supplementary services in related IMS service definitions further motivates a converged architecture.

The service also addresses the need for interoperability and roaming: because IMS Messaging is built on SIP and IMS procedures, messages can traverse operator boundaries and be delivered to users on different access networks, while the home operator retains control over service policy and charging. This makes IMS Messaging a foundational enabler for rich communication services (RCS) and other advanced messaging offerings.

What changed in its specifications

The latest release-to-release comparison of specifications that define IMS Messaging services. Each summary describes the whole specification, not only this term.

TS 22.340Rel-7 → Rel-8

Adds requirements for service-level interworking between IMS messaging and SMS, EMS, MMS, and fixed Internet services.

Full comparison in TS 22.340 →
TS 26.141Rel-17 → Rel-18

Rel-18 added 3D scenes and assets support, updated video, speech, and audio capabilities, and relaxed several media format requirements for 5G-Advanced messaging media profiles.

Full comparison in TS 26.141 →

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

Initial definition introduced IMS Messaging as a group of services supported by IMS capabilities, comprising immediate messaging, session based messaging, and deferred delivery messaging. This established the foundational service taxonomy that persists to later releases.

The definition carried over unchanged from Rel-2, maintaining the same three messaging types and IMS-based service description.

The definition was revised to list only 'Immediate messaging and Session based messaging', omitting deferred delivery messaging from the enumerated types. This narrowing of scope was later reversed.

The definition was restored to include deferred delivery messaging alongside immediate and session based messaging, and the IMS reference was updated to TS 22.228 [54]. This restored the full three-type taxonomy.

The definition carried over unchanged from Rel-8, retaining the three messaging types and the updated IMS specification reference.

The definition carried over unchanged from Rel-8, with no textual modification to the service description.

The definition carried over unchanged from Rel-8, maintaining the same messaging service taxonomy.

The definition carried over unchanged from Rel-8, with no changes to the enumerated messaging types or IMS reference.

The definition carried over unchanged from Rel-8, preserving the established service description.

The definition carried over unchanged from Rel-8, with no textual modification.

The definition carried over unchanged from Rel-8, maintaining the same three messaging types.

The definition carried over unchanged from Rel-8, with no changes to the service definition.

The definition carried over unchanged from Rel-8, retaining the same wording and IMS reference.

The definition carried over unchanged from Rel-8, with no textual modification.

The definition carried over unchanged from Rel-8, preserving the established IMS Messaging service description.

Defining Specifications

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

SpecificationTitleRelease
TS 22.340 vj00 IMS Messaging Stage 1 Requirements Rel-19 read
TS 26.141 vj00 IMS Messaging & Presence Media Formats Rel-19 read