SMS-SC

Short Message Service - Service Centre

Core Network →
Introduced in Rel-5 Also in: Security

SMS-SC is the central network element responsible for storing, forwarding, and routing SMS messages, acting as the critical hub for all SMS traffic.

Category
Core Network
Introduced
Rel-5
Where
Services
Also touches
1 segments
Specifications
6 specs
SMS-SC Description Purpose Related Classification Detected Changes Specifications

Description

The SMS-SC (Short Message Service – Service Centre) is a standalone network entity within the 3GPP architecture that serves as the central switching and management point for SMS messages. It is not a subscriber-facing element but a core network server that communicates with MSCs, SGSNs, MMEs, and IMS nodes (via IP-SM-GW) on one side, and with the HLR/HSS on the other. Its primary function is to receive messages from originating users or external applications, store them temporarily, determine the route to the recipient, and forward them for delivery. If the recipient is unavailable, the SMS-SC queues the message and initiates retry attempts based on operator-defined policies.

Architecturally, the SMS-SC connects to the network via standardized interfaces, primarily using the MAP protocol for communication with circuit-switched and packet-switched core network elements (MSC, SGSN, HLR) in 2G/3G/4G networks, and Diameter or SIP for communication with the 5G Core or IMS. When an SMS-SC receives a Mobile Originated message, it processes the message, which may involve checking subscriber validity, applying service logic (e.g., for premium services), and then querying the HLR/HSS to obtain routing information (the address of the MSC, SGSN, or MME currently serving the recipient). For Mobile Terminated messages from external applications (like news alerts), the SMS-SC performs the same routing lookup and delivery procedure.

The SMS-SC also handles essential supplementary functions such as generating delivery reports, which are sent back to the originator to confirm successful receipt or indicate failure. It manages message validity periods, after which undelivered messages are discarded. Furthermore, the SMS-SC is the gateway for value-added services (VAS), enabling applications like ringtone downloads, voting, and mobile banking by providing a standardized interface (often SMPP - Short Message Peer-to-Peer protocol) for external application servers. In 5G networks, the SMS-SC interfaces with the SMSF (SMS Function), which adapts the SMS for transport over the 5G Core, but the store-and-forward and routing intelligence largely remains within the SMS-SC.

Purpose & Motivation

The SMS-SC was created to solve the fundamental problem of asynchronous, store-and-forward messaging in mobile networks. Without a central service centre, delivering a text message would require the sender and recipient to be simultaneously attached and reachable on the network, which is impractical. The SMS-SC decouples transmission from reception, storing messages when the recipient is offline and retrying delivery, thereby guaranteeing service reliability.

Historically, as SMS gained popularity in GSM, a centralized management point was needed to handle routing between different network operators (interworking), apply billing logic, and manage the flood of messages efficiently. The SMS-SC provided this centralized intelligence, interfacing with the HLR to find subscribers anywhere in the world. It also enabled the commercial ecosystem of value-added services by acting as a secure, controlled gateway between mobile operators and third-party content providers. Its creation standardized what was initially a network-specific implementation, allowing for global SMS interoperability and roaming, which was crucial for the service's worldwide success.

Classification

Part ofSMS-PP
Specific typesIP-SM-GW
Related approachesHLRSMPP

Detected Changes Across Releases

from 3GPP Change Requests

Specific 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-5, normative work from Rel-15.

Rel-15 3 changes

In Release 15, the SMS-SC function was updated with specific corrections and procedure changes for Group Message Delivery. These enhancements particularly addressed the Group Message Delivery Procedure when utilizing Non-IP Data Delivery (NIDD) mechanisms. The changes focused on ensuring the proper handling of multicast service messages within the connectionless bearer services framework.

  • Group Message Delivery Procedure changes due to NAPS TS 23.682CR0260
  • Corrections of Group Message Delivery via NIDD TS 23.682CR0384
  • Correction to the group message delivery TS 23.682CR0395
Rel-16 2 changes

In Release 16, the SMS-SC function was enhanced with new capabilities for group message delivery. Specifically, the release introduced mechanisms to deliver a single message to multiple recipients, including a method utilizing Multimedia Broadcast Multicast Service (MBMS) via the xMB interface for efficient mass distribution.

  • Group message delivery TS 23.682CR0437
  • Group message delivery using MBMS via xMB TS 23.682CR0451

Explore further

Broader topics and technologies where SMS-SC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 22.142 vj00 Value-added Services for SMS Requirements Rel-19
TR 22.942 vj00 SMS Value-Added Services Requirements Rel-19
TS 23.048 v1400 Secured Packets for UICC Remote Management Rel-5
TS 23.682 vj30 3GPP TS 23682: MTC Architecture Enhancements Rel-19
TS 31.115 vj00 Secured Packet Structure for UICC Applications Rel-19