Description
The MSGin5G Server is a functional entity defined in 3GPP TS 23.554 (architecture) and described in TS 22.262 (service requirements) as part of the MSGin5G (Message Service in 5G) enabler. It sits within the 5G System and acts as the message routing and control node for a mobile network operator's native messaging service. Its primary role is to route messages between UEs (UE-to-UE), between application servers and UEs (AS-to-UE and UE-to-AS), and to support group and broadcast delivery. Unlike traditional SMS, which is bound to the circuit-switched or SMS-over-NAS infrastructure, the MSGin5G Server operates over the 5G user plane and control plane, allowing it to handle richer message types, larger payloads, and thing-to-thing traffic patterns.
Architecturally, the MSGin5G Server is reachable by UEs through the 5G Core (typically via the UPF and NEF/SCEF exposure functions) and by application servers through the NEF or dedicated APIs. The server maintains message routing information, subscription data, and delivery state. When a UE sends a message, the server authenticates and authorizes the request, determines the destination (another UE, a group, or an AS), and either delivers the message immediately or stores it for later delivery if the recipient is unreachable. This store-and-forward capability is essential for IoT devices that may be in power-saving mode (eDRX, PSM) or temporarily out of coverage.
The server supports several delivery modes: Point-to-Point (unicast between two endpoints), Application-to-Point and Point-to-Application (between an AS and a UE), Group messaging (one-to-many within a defined group), and Broadcast (to all UEs in an area or subscribed set). It also handles message delivery reports, so senders can confirm receipt, and it can apply policies such as message size limits, rate control, and priority handling. The server interacts with the UDM to retrieve subscription information and with the NEF to expose messaging capabilities to external application servers in a standardized way.
In the 5G core, the MSGin5G Server is not a mandatory node for all deployments; it is an optional service enabler that an operator can deploy to offer MSGin5G as a value-added service. When deployed, it integrates with the SMF/UPF for user-plane transport and with the AMF for paging and reachability of idle UEs. For group and broadcast messaging, it may rely on multicast/broadcast capabilities (5MBS) or on repeated unicast delivery depending on the deployment.
The MSGin5G Server is significant because it brings operator-grade messaging into the 5G era, supporting the massive number of IoT devices and the diverse communication patterns (thing-to-thing, person-to-thing) that 5G is designed to serve. It provides a standardized alternative to proprietary OTT messaging platforms and to legacy SMS, while offering reliability, security, and integration with 5G network functions.
Purpose & Motivation
The MSGin5G Server exists to provide a standardized, operator-controlled message routing function within the 5G System. Legacy messaging in mobile networks was dominated by SMS, which was designed for short text messages between humans and is tightly coupled to circuit-switched and NAS signaling. As 5G expanded to serve massive IoT, the industry needed a messaging service that could handle thing-to-thing communication, larger payloads, group and broadcast delivery, and integration with application servers. The MSGin5G Server was created to fill that gap.
A key motivation was the desire to avoid fragmentation: without a standardized server, operators and vendors would implement proprietary messaging solutions that do not interoperate. By defining the MSGin5G Server in TS 23.554, 3GPP ensures that UEs, application servers, and network functions from different vendors can exchange messages through a common architecture. The server also addresses the reachability problem for IoT devices: many devices sleep for long periods, so a store-and-forward server is needed to buffer messages until the device wakes up.
Finally, the server enables new business models for operators, such as offering messaging-as-a-service to enterprises and application providers via the NEF. It supports policy control, delivery reporting, and group management, which are essential for industrial IoT, public safety, and smart-city use cases.
What changed in its specifications
The latest release-to-release comparison of specifications that define MSGin5G Server. Each summary describes the whole specification, not only this term.
Message Service within the 5G system Phase 2 adds registration, bulk registration, charging, deployment, topic-based message delivery, aggregation, and segmentation. Generic group management enhancements add references to new group procedures and UE lacking a group management client behavior.
Full comparison in TS 23.554 →Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-16, normative work from Rel-17.
Defining Specifications
3GPP specifications that define or reference MSGin5G Server, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.262 vj00 | MSGin5G Service Requirements | Rel-19 read |
| TS 23.554 vj80 | MSGin5G Service Application Architecture | Rel-19 read |