Description
The Short Message Service Centre (SMSC) is a critical network element within the GSM and UMTS architecture, specifically designed for the Short Message Service (SMS). It functions as a store-and-forward system, meaning it receives messages from a sending entity, stores them temporarily, and then attempts to deliver them to the intended recipient. The SMSC's primary role is to ensure reliable SMS delivery, handling scenarios where the recipient's device is turned off or out of coverage by retrying delivery for a configurable period. It interfaces with various other network components, including the Mobile Switching Centre (MSC) for circuit-switched SMS and the IP Short Message Gateway (IP-SM-GW) for SMS over IP networks, to route messages appropriately.
Architecturally, the SMSC consists of several functional components. The core is the message store, which holds messages awaiting delivery or retrieval. It includes routing logic to determine the destination network and the appropriate signaling path, such as via MAP (Mobile Application Part) over SS7 or Diameter over IP. The SMSC also manages subscriber data relevant to SMS, such as service settings and whether a subscriber is barred from the service. It generates charging data records (CDRs) for billing purposes and implements protocols defined in specifications like 3GPP TS 23.040 (technical realization) and TS 23.078 (customized applications).
In operation, when a mobile-originated (MO) SMS is sent, the handset forwards it via the radio access and core network to the SMSC. The SMSC acknowledges receipt and then initiates the mobile-terminated (MT) delivery procedure. It queries the Home Location Register (HLR) or Home Subscriber Server (HSS) to obtain the current routing information (e.g., the serving MSC or SGSN/MME address) for the recipient. The message is then forwarded to that network node for delivery to the mobile device. If delivery fails, the SMSC schedules retries based on its configuration. This decoupled, asynchronous model is key to SMS reliability.
The SMSC's role expanded with the introduction of SMS over IP and IMS. In later releases, it interfaces with the IP-SM-GW, which acts as an interworking function between the legacy MAP-based SMS and the SIP-based messaging in IMS, as defined in TS 23.204. This allows SMS services to continue seamlessly as networks evolve towards all-IP cores. Furthermore, the SMSC supports value-added services through interfaces to external application servers (like SMS gateways for content delivery) and enables features such as SMS broadcasting and premium-rated messages, making it a versatile platform for both person-to-person and application-to-person messaging.
Purpose & Motivation
The SMSC was created to enable the Short Message Service (SMS), a foundational mobile data service specified in the early GSM standards. Its primary purpose is to provide a reliable, store-and-forward messaging mechanism that works independently of voice call connectivity. Before widespread mobile data, SMS offered a simple, efficient way to send brief text messages, leveraging unused capacity in the signaling channels used for network control (the Stand-alone Dedicated Control Channel, SDCCH). The SMSC solves the problem of delivering messages to mobile devices that may be temporarily unreachable, ensuring no message is permanently lost due to network or device status.
Historically, the motivation was to utilize existing network signaling infrastructure for a new, revenue-generating service without requiring major network upgrades. The store-and-forward model was chosen over a real-time delivery attempt because it accommodated the limitations of early mobile networks, where devices were frequently powered off or out of range. This design also allowed for features like deferred delivery and message waiting indicators. The SMSC standardized the central point for SMS routing, inter-operator interconnection, and billing, which was crucial for the interoperability that made SMS a global success.
As networks evolved, the SMSC's purpose extended to maintaining SMS service continuity during the transition to packet-switched and IMS-based networks. It addressed the challenge of supporting legacy SMS in new IP-based architectures, ensuring backward compatibility for billions of subscribers. Its enduring role is to provide a proven, reliable messaging transport that underpins not only consumer texting but also critical machine-to-machine (M2M) communication, two-factor authentication, and various alerting systems, making it an indispensable component of mobile telecommunications.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (28 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the SMSC function saw corrections and refinements to several core messaging procedures, including message delivery to the Message Gateway, message aggregation, and segment recovery. The updates also involved alignment on Information Element (IE) naming for the Message Gateway and the removal of one IE from the AS originating message send request. Furthermore, enhancements were made to point-to-point message segmentation and reassembly, and a new capability for message topic unsubscription was introduced.
- Message topic unsubscription TS 23.554CR0014
- Correction on message delivery procedure to Message Gateway TS 23.554CR0006
- Alignment on Message Gateway IE name TS 23.554CR0017
- Remove one IE from AS originating message send request TS 23.554CR0018
- Correction on Message Aggregation TS 23.554CR0019
- Correction on Message Segment Recovery TS 23.554CR0021
+ 1 more changes
In Release 18, the SMSC function was enhanced with new procedures for Broadcast Message delivery and inter-PLMN Message delivery based on Messaging Topic. It introduced capabilities for MSGin5G message aggregation and segmentation, along with updates for Message Aggregation at both the MSGin5G Client and Server. The release also included corrections for message segmentation and refined the Message Gateway interactions with SEAL services.
- Broadcast Message delivery procedure TS 23.554CR0031
- Message delivery based on Messaging Topic for different PLMNs TS 23.554CR0044
- MSGin5G message aggregation and segment TS 23.554CR0037
- Broadcast Message Gateway additions TS 23.554CR0053
- Aggregated message handling at the MSGin5G Server TS 23.554CR0051
- Security credentials IE in Message Gateway registration aligned with 33501 TS 23.554CR0064
+ 12 more changes
In Release 19, the SMSC function introduced new capabilities for application interaction, including an API for the Application Server to receive originating message response notifications and a mechanism for an Application Client to request updates to a stored message. Additionally, a correction was made to the message response procedure. These enhancements were implemented within the framework of the existing proprietary SC to SME interface protocols, such as SMPP, as the core SMSC functionality remains outside the scope of 3GPP standardization.
Explore further
Broader topics and technologies where SMSC plays a role.
Defining Specifications
3GPP specifications that define or reference SMSC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.039 v1400 | SMSC to SME Interface Protocols | Rel-5 |
| TS 23.078 vj00 | CAMEL Phase 4 Stage 2 Specification | Rel-19 |
| TS 23.554 vj70 | MSGin5G Service Application Architecture | Rel-19 |
| TR 23.976 vj00 | Push Service Requirements Analysis | Rel-19 |
| TS 29.078 vj00 | CAMEL Phase 4 CAP Specification | Rel-19 |