Description
The CPM Application Server (CPM AS) is a functional entity within the IP Multimedia Subsystem (IMS) architecture that provides Converged IP Messaging (CPM) services. CPM, specified in 3GPP TS 23.204, is the 3GPP adaptation of the OMA Converged IP Messaging enabler, designed to unify messaging across multiple service paradigms — including paging-mode messaging, session-mode messaging, large message mode, and store-and-forward messaging — over a single IMS-based infrastructure. The CPM AS is the server-side node that realizes this functionality by hosting one or both of the two core CPM roles defined by OMA: the CPM Participating Function and the CPM Controlling Function.
The CPM Participating Function is the entity that a CPM client attaches to. It handles message submission, delivery, and storage on behalf of a specific user, and it interacts with the user's CPM client over the reference point defined in the OMA CPM architecture. The CPM Controlling Function, by contrast, is responsible for network-level message routing and interworking between participating functions, including distribution of messages to multiple recipients in group communications. A single CPM AS may implement either role or both, depending on deployment; a network may deploy a single combined CPM AS or separate participating and controlling servers. This flexibility allows operators to scale the participating tier (which is user-facing and stateful per user) independently from the controlling tier (which handles routing and fan-out).
The CPM AS sits in the IMS core and uses standard IMS capabilities: SIP signalling for session-mode and paging-mode messaging, the ISC interface towards the S-CSCF for service triggering, and the Ut interface towards the XCAP server for management of CPM service settings and group definitions. Media and message content are transported using MSRP where session-based or large-message delivery is required, while smaller messages may be carried directly in SIP requests. The CPM AS also interfaces with the IMS messaging store (for deferred delivery), with the presence service for availability information, and with interworking functions to reach non-CPM messaging systems such as SMS, MMS, and OMA SIMPLE IM.
From a service perspective, the CPM AS enables a converged user experience: a subscriber can send a message from one device and have it delivered to another, participate in group chats, exchange large files, and have messages stored and forwarded when the recipient is offline. Because CPM is built on IMS, it inherits IMS authentication, authorization, charging, and roaming capabilities, and it can interwork with the underlying circuit-switched and packet-switched domains. The CPM AS is therefore a key enabler of operator-provided rich messaging that competes with over-the-top messaging services while remaining standards-based and interoperable.
In 3GPP specifications, the CPM AS is referenced in TS 23.204 (Support of Short Message Service over generic 3GPP IP access) and in the study documented in TR 23.824, which examined CPM-related architectural enhancements. The definition of the term has remained stable across Releases 10 through 19, with only editorial normalization of the OMA reference document identifier over time, reflecting the maturity and stability of the CPM architecture.
Purpose & Motivation
The CPM AS exists to give operators a standardized, IMS-native platform for delivering converged messaging services that span multiple message types and access technologies. Before CPM, messaging in 3GPP networks was fragmented: SMS was handled by the circuit-switched core and its own service centres, MMS by a separate MMSC architecture, and instant messaging by proprietary or OMA SIMPLE IM enablers. Each system had its own addressing, storage, charging, and interworking model, which made it expensive for operators to offer a unified messaging experience and difficult for users to move seamlessly between message types.
CPM, and the CPM AS that implements it, solves this by defining a single messaging service layer on top of IMS. It reuses IMS registration, authentication, and session control, so messaging inherits the security and mobility properties of the IMS core. It introduces a common message model that covers paging-mode (small, SIP-carried), session-mode (MSRP-based conversational), large-message-mode, and store-and-forward messaging, and it defines how these interwork with legacy systems such as SMS and MMS. The split into Participating and Controlling Functions allows a clean separation between per-user message handling and network-wide routing, which supports scalable group messaging and multi-device delivery.
The CPM AS was introduced in Release 10 as part of 3GPP's adoption of the OMA CPM enabler into the IMS specifications. Its motivation was to provide a standards-based alternative to proprietary over-the-top messaging, preserving operator control over addressing, policy, charging, and lawful interception while offering a richer feature set than SMS or MMS alone. Because it is defined by reference to the OMA CPM architecture, the CPM AS also benefits from the OMA enabler's well-defined client-server and server-server interfaces, enabling multi-vendor deployment.
What changed in its specifications
The latest release-to-release comparison of specifications that define CPM AS. Each summary describes the whole specification, not only this term.
Rel-19 adds Multimedia Priority Service (MPS) for Messaging to TS 23.204. The MPS indication is stored in HSS/UDM, and Resource-Priority and transport priority are set in P-CSCF, IP-SM-GW and SMS-GMSC.
Full comparison in TS 23.204 →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.
Initial definition introduced: an application server supporting the functionality of a CPM Participating Function and/or a CPM Controlling Function as defined in OMA-RD-CPM-V1_0-20091218-D. Establishes the CPM AS as the IMS server-side entity for converged messaging.
Defining Specifications
3GPP specifications that define or reference CPM AS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.204 vj10 | SMS over generic IP access; Stage 2 | Rel-19 read |
| TS 23.824 va00 | IP-SM-GW Enhancements for CPM-SMS Interworking | Rel-10 read |