Simple Message Transfer Protocol

Description

The Simple Message Transfer Protocol (SMTP) in the 3GPP context is a specialized protocol profile based on the Internet Engineering Task Force (IETF) SMTP standard (RFC 5321). It is used as a transport mechanism for Short Message Service (SMS) messages within IP-based network architectures, such as those defined for the IP Multimedia Subsystem (IMS) or for direct interconnection with Internet email services. The protocol operates between an IP Short Message Gateway (IP-SM-GW) or another SMS application server and external IP-based entities like email servers. When an SMS message needs to be delivered to an email recipient, the 3GPP network entity (e.g., IP-SM-GW) encapsulates the SMS TPDU (Transfer Protocol Data Unit, defined in TS 23.040) within an SMTP message. The SMS content is typically placed in the body of the email, while SMTP headers and envelope information are used for routing and indicating the source/destination. The 3GPP specifications (e.g., TS 23.040 and TS 29.198) define the exact mapping rules, content-type headers (often text/plain or application/vnd.3gpp.sms), and handling of delivery reports. For messages originating from the Internet (email) destined for an MSISDN, the reverse process occurs: the IP-SM-GW receives an SMTP email, extracts the content, reformats it into a standard SMS TPDU, and injects it into the mobile network's SMS routing infrastructure (e.g., via MAP to an SMSC). The protocol supports essential features like sender/recipient addressing translation (between MSISDN and email addresses), submission port specification, and basic reliability mechanisms inherent to SMTP.

Purpose & Motivation

3GPP defined its profile of SMTP to bridge the world of cellular SMS with the ubiquitous Internet email system, a need that arose as networks evolved towards all-IP architectures. Initially, SMS was carried over circuit-switched signaling channels (like SDCCH in GSM). With the introduction of packet-switched cores (GPRS, later EPS and IMS), a method was needed to transport SMS over IP for efficiency and to enable new service paradigms. The adoption of SMTP solved the problem of interworking between the mobile messaging domain and the fixed Internet email domain. It allowed mobile operators to offer services like 'email to SMS' and 'SMS to email', creating new revenue streams and enhancing service accessibility. Its creation was motivated by the convergence of communication technologies in the early 2000s (Rel-4/5 timeframe), where separating service logic from the underlying transport became a key design principle. Using a well-established, robust protocol like SMTP provided a standardized, reliable, and widely understood mechanism for this gateway function, avoiding the need to invent a completely new IP messaging protocol and ensuring interoperability with the vast existing email infrastructure.

Key Features

• Based on IETF SMTP (RFC 5321) for reliable message transfer over IP
• Defines mapping rules between SMS TPDU format and SMTP email format
• Used by network elements like the IP-SM-GW for SMS-email interworking
• Supports both mobile-originated and mobile-terminated SMS over IP scenarios
• Handles address translation between MSISDN and email addresses
• Specifies content-type headers for proper identification of SMS payload in email

Evolution Across Releases

Defining Specifications