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

Glossary term · Services

MSGin5G Service

Message Service in 5G

Services →

MSGin5G Service is an MNO-provided 5G messaging service supporting point-to-point, AS-to-point, point-to-AS, group, and broadcast delivery for thing-to-thing and person-to-thing communication, standardized to replace legacy SMS in IoT and enterprise contexts.

Introduced
Rel-16
Where
Services
Specifications
2 specs
MSGin5G Service Description Purpose What changed Neighbours Detected Changes Specifications

Description

MSGin5G Service is a mobile network operator message service defined in 3GPP TS 22.262 (service requirements) and TS 23.554 (architecture). It uses the 5G System to deliver messages between endpoints, supporting Point-to-Point (UE-to-UE), AS-to-Point (application server to UE), Point-to-AS (UE to application server), Group, and Broadcast delivery. The service is designed for both thing-to-thing communication (IoT devices, sensors, machines) and person-to-thing communication (a human interacting with a device or application). It is delivered by the operator's network using the MSGin5G Server as the central routing entity.

The service operates over the 5G user plane and control plane rather than the legacy SMS infrastructure. A UE registers with the 5G core and obtains connectivity; when it wants to send a message, it uses an application-layer protocol to submit the message to the MSGin5G Server, typically via a data connection through the UPF. The server authenticates the sender, checks authorization and subscription (via UDM), and routes the message to the destination. For AS-originated messages, the application server accesses the service through the NEF, which exposes standardized APIs and enforces policies. The service supports store-and-forward, so messages destined for sleeping or unreachable devices are buffered and delivered when the device becomes reachable.

Key service capabilities include message delivery reports, group management (creation, membership, and deletion of groups), broadcast delivery to a geographic area or a subscribed set of UEs, and policy control for message size, rate, and priority. The service can also support message priority and pre-emption for critical communications, and it can integrate with 5G multicast/broadcast services (5MBS) for efficient group and broadcast delivery. Security is provided through 5G authentication and authorization mechanisms, and messages can be protected end-to-end depending on operator policy.

The MSGin5G Service is positioned as an operator-grade alternative to OTT messaging and to legacy SMS. It is particularly valuable for IoT deployments where devices need to send small data payloads without establishing a full data session, and for enterprise applications that need reliable, policy-controlled messaging to and from devices. Because it is standardized, it enables interoperability between UEs, application servers, and network functions from different vendors.

In terms of deployment, the service is optional and can be offered by operators as a value-added service. It leverages existing 5G core functions (AMF, SMF, UPF, UDM, NEF) and does not require a separate radio access technology. This makes it cost-effective to deploy and integrate with existing 5G networks.

Purpose & Motivation

MSGin5G Service was created to provide a standardized, operator-controlled messaging service for the 5G era. Legacy SMS was designed for short human-to-human text messages and is tied to circuit-switched and NAS signaling, which is inefficient for IoT and does not support modern requirements such as group messaging, broadcast, large payloads, or application-server integration. As 5G networks began serving massive numbers of IoT devices, operators needed a messaging service that could handle thing-to-thing and person-to-thing communication efficiently.

The service also addresses the fragmentation problem: before MSGin5G, messaging for IoT was often implemented through proprietary platforms or OTT services, which lack standardized interoperability and operator control. By defining MSGin5G in 3GPP specifications, the industry ensures that devices and application servers can use a common service with predictable behavior, security, and policy enforcement. The service also enables operators to offer messaging-as-a-service to enterprises, creating new revenue opportunities.

Another motivation was reachability: many IoT devices use power-saving features such as eDRX and PSM, making them unreachable for extended periods. MSGin5G Service includes store-and-forward and delivery reporting, which are essential for reliable communication with such devices. Finally, the service supports group and broadcast delivery, which are important for public safety, smart cities, and industrial automation.

What changed in its specifications

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

TS 23.554Rel-17 → Rel-18

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 Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 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-18.

Rel-18 1 change
  • Adds new group management capabilities to MSGin5G service TS 23.554CR0101
Rel-19 1 change
  • MSGin5G service in Data delivery management service TS 23.554CR0207

Defining Specifications

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

SpecificationTitleRelease
TS 22.262 vj00 MSGin5G Service Requirements Rel-19 read
TS 23.554 vj80 MSGin5G Service Application Architecture Rel-19 read