SMS over IP MESSAGE

Description

SMSIP MESSAGE is a fundamental concept in the 3GPP architecture for delivering Short Message Service (SMS) over IP-based networks, specifically within the IP Multimedia Subsystem (IMS). It is defined as an immediate message as specified in TS 23.228, which encapsulates a Short Message (SM) in its text body. This means that the traditional SMS payload is carried within a SIP MESSAGE request, leveraging the Session Initiation Protocol (SIP) as the transport mechanism. The SIP MESSAGE method, defined in RFC 3428, is used for instant messaging and is ideal for transporting short, self-contained messages like SMS. The SMSIP MESSAGE thus enables the seamless integration of SMS into all-IP networks, such as LTE and 5G, where circuit-switched fallback may not be available or desirable.

The architecture for SMS over IP involves several key components. The User Equipment (UE) that supports SMSIP MESSAGE, known as an SMSIP UE, initiates the SIP MESSAGE request towards the IMS core network. The IMS core, comprising elements like the Call Session Control Function (CSCF) and the Telephony Application Server (TAS), routes the message appropriately. The TAS may interact with an IP-Short-Message-Gateway (IP-SM-GW) to interwork with legacy SMS infrastructure, such as SMSCs (Short Message Service Centers). The IP-SM-GW acts as a gateway between the SIP-based messaging and the traditional SS7/MAP-based SMS network, ensuring that SMS can be delivered to and from non-IMS devices. The SMSIP MESSAGE itself contains the SM in its text body, typically encoded in a format that preserves the original SMS characteristics, such as the TP-DU (Transport Protocol Data Unit) or a similar encapsulation.

How it works: When an SMSIP UE wants to send an SMS, it constructs a SIP MESSAGE request with the SM content in the body. The request is sent to the IMS core, which authenticates and authorizes the UE. The TAS or IP-SM-GW then processes the message. If the recipient is an SMS-capable device on the legacy network, the IP-SM-GW converts the SIP MESSAGE into a traditional SMS message and forwards it via the SMSC. Conversely, for terminating messages, the IP-SM-GW receives an SMS from the SMSC, encapsulates it into a SIP MESSAGE, and delivers it to the SMSIP UE via the IMS core. This process ensures that SMS remains a reliable and ubiquitous service even as networks evolve towards all-IP.

Key components include the SMSIP UE, the IMS core (P-CSCF, I-CSCF, S-CSCF), the TAS, and the IP-SM-GW. The SMSIP MESSAGE is typically transported over the Gm interface between the UE and P-CSCF, and over the ISC interface between the S-CSCF and TAS. The IP-SM-GW interfaces with the SMSC over the MAP protocol. The message format must adhere to 3GPP specifications to ensure interoperability. The SMSIP MESSAGE can carry various types of SMS, including point-to-point, broadcast, and concatenated messages, although concatenation is handled at the application layer.

In the context of 5G, SMS over IP continues to be supported, often via the 5G Core's IMS integration. The SMSIP MESSAGE remains the same, but the underlying transport may use HTTP/2 or other protocols for signaling. The term has been stable since its introduction in Release 8, with no changes to its definition, reflecting its mature and well-defined role. Its importance lies in enabling SMS as a service in packet-switched networks, ensuring continuity and interoperability with legacy systems.

Purpose & Motivation

SMSIP MESSAGE exists to enable the delivery of Short Message Service (SMS) over IP-based networks, particularly in the context of IMS and all-IP architectures like LTE and 5G. Traditionally, SMS was delivered over circuit-switched (CS) networks using SS7 signaling. However, as networks evolve towards all-IP, the CS domain is being phased out. Without a mechanism to carry SMS over IP, operators would lose a critical service that is still widely used for person-to-person messaging, two-factor authentication, and machine-to-machine communication. SMSIP MESSAGE solves this by encapsulating SMS within SIP MESSAGE requests, allowing SMS to be transported over the IMS.

The motivation for SMSIP MESSAGE was to provide a standardized way to support SMS in IMS-capable devices without requiring a CS fallback. Before its introduction, devices might need to fall back to CS networks to send or receive SMS, which was inefficient and could lead to delays or failures in areas with only packet-switched coverage. The 3GPP defined SMS over IP in Release 8 as part of the broader effort to integrate SMS into IMS. This allowed operators to offer SMS as an IMS service, leveraging the same core network for voice, video, and messaging. It also facilitated interworking with legacy SMS networks through the IP-SM-GW, ensuring that users on IMS networks could communicate with users on traditional networks.

Furthermore, SMSIP MESSAGE provides a foundation for advanced messaging services, such as SMS over IMS for emergency services and for IoT devices. It ensures that SMS remains a reliable and ubiquitous service, even as networks transition to 5G and beyond. The term's definition has remained unchanged since Release 8, indicating its stability and the maturity of the underlying technology.