Description
The Short Message Service Interworking MSC (SMS-IWMSC) is the functional counterpart to the SMS-GMSC, handling the outbound path for Mobile-Originated Short Messages (MO-SM) within 2G/3G Circuit-Switched core networks. When a mobile subscriber sends an SMS, the message is first delivered over the radio interface to their current serving MSC. The serving MSC, recognizing the message as mobile-originated, then forwards it to the SMS-IWMSC. The SMS-IWMSC serves as the designated gateway from the PLMN to the external Short Message Service Centre (SMSC). Like the SMS-GMSC, it is typically a functional role collocated within a physical MSC.
The SMS-IWMSC receives the MO-SM from the serving MSC via internal MAP signaling (MAP_FORWARD_SHORT_MESSAGE). Its key responsibility is to determine the correct destination SMSC for the message. This routing decision is often based on configuration, such as a default SMSC for the subscriber's home network or a specific SMSC address provided by the HLR during subscriber profile retrieval. The SMS-IWMSC then performs any necessary protocol adaptation and submits the message to the identified external SMSC, usually using the same MAP-based interface (e.g., MAP_MT_FORWARD_SHORT_MESSAGE) over SS7 or IP links.
This entity also manages delivery reports and failures in the mobile-originated direction. If the external SMSC confirms successful receipt, the SMS-IWMSC may relay a positive delivery report back through the serving MSC to the originating mobile device. Conversely, if the SMSC rejects the message or is unreachable, the SMS-IWMSC handles the error and may inform the serving MSC. The SMS-IWMSC provides a single, controlled egress point for all MO-SM traffic, allowing for centralized billing, lawful interception, and message screening before messages leave the operator's network. It works in tandem with the SMS-GMSC to form the complete SMS gateway functionality for the CS domain.
Purpose & Motivation
The SMS-IWMSC was standardized to provide a controlled and standardized exit point from the PLMN for subscriber-originated text messages, mirroring the entry-point function of the SMS-GMSC. Its creation solved the problem of how a serving MSC, which handles subscriber mobility, should route an outgoing SMS to a potentially external and fixed SMSC. Without a dedicated interworking function, each MSC would need direct connectivity and routing configurations for all possible SMSCs, leading to operational complexity and scaling issues.
This architecture centralizes the interworking function, simplifying network management and enabling features like centralized billing for originated messages and consistent application of regulatory requirements (e.g., content filtering, lawful interception) at the network border. It addresses the limitation of having mobile-originated traffic exit the network in an ad-hoc manner from any MSC. By funneling all MO-SM traffic through the SMS-IWMSC, operators gain a strategic point of control and visibility for outbound messaging services. It was a key component in making SMS a reliable, billable, and manageable service for network operators.
Key Features
- Gateway function for Mobile-Originated SMS to external SMSCs
- Receives MO-SM from the serving MSC via MAP forwarding
- Determines and routes messages to the appropriate destination SMSC
- Handles delivery reports and error notifications from the SMSC
- Provides a centralized PLMN exit point for outbound SMS traffic
- Enables centralized billing, filtering, and lawful interception for MO-SM
Evolution Across Releases
Introduced the SMS-IWMSC as a standardized functional entity complementary to the SMS-GMSC. Defined its role in the Mobile-Originated SMS procedure, specifying the reception of the MAP_FORWARD_SHORT_MESSAGE from the serving MSC and the subsequent submission to the external SMSC. Established it as the designated gateway for all outbound SMS traffic from the PLMN.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.060 | 3GPP TS 23.060 |
| TS 28.702 | 3GPP TS 28.702 |
| TS 29.338 | 3GPP TS 29.338 |
| TS 32.401 | 3GPP TR 32.401 |
| TS 32.622 | 3GPP TR 32.622 |
| TS 32.632 | 3GPP TR 32.632 |
| TS 32.732 | 3GPP TR 32.732 |
| TS 52.402 | 3GPP TR 52.402 |