Description
Simple Mail Transfer Protocol (SMTP) is an application-layer Internet standard protocol (RFC 5321) for electronic mail transmission. Within the 3GPP architecture, SMTP is leveraged as a transport protocol, primarily for the Multimedia Messaging Service (MMS). It operates on a client-server model, where an SMTP client (sender) establishes a TCP connection to an SMTP server (receiver) on port 25 (or 587 for submission) to relay mail messages.
The protocol works through a series of text-based commands and replies. A typical session involves the client initiating a connection, the server responding with a greeting. The client then issues commands like EHLO/HELO (identification), MAIL FROM (sender address), RCPT TO (recipient address), DATA (message body transmission), and finally QUIT. The server responds with numeric reply codes (e.g., 250 for OK, 550 for failure) after each command. SMTP is primarily a 'push' protocol for delivering mail to a recipient's mail server; retrieval of messages from a mailbox is handled by other protocols like POP3 or IMAP.
In the 3GPP context, specific network elements act as SMTP clients or servers. For example, an MMSC (Multimedia Messaging Service Centre) uses SMTP to forward MMS messages to other MMSCs, to email servers, or to receive messages from them. The protocol carries the MMS message content encapsulated within a standard MIME (Multipurpose Internet Mail Extensions) format. 3GPP specifications define the exact profiles and usage of SMTP for ensuring interoperability between different vendors' MMS systems and for interfacing with the global Internet email infrastructure.
The role of SMTP is transport-centric. It does not define the structure or content of the message itself (that is handled by MIME and the MMS specifications), but it provides a reliable, widely-supported mechanism for store-and-forward message transfer. Its use in 3GPP highlights the convergence of cellular messaging services with Internet standards.
Purpose & Motivation
SMTP was incorporated into 3GPP standards to solve the problem of inter-system messaging transport for services like MMS. Early proprietary messaging systems lacked a universal transport method for delivering rich content between different operator networks and between cellular networks and the Internet. The creation of MMS required a reliable, standardized, and widely deployed transport protocol that could handle binary attachments and work over IP networks.
The adoption of SMTP was motivated by its status as the de facto global standard for email transmission. By using SMTP, 3GPP-based MMS could seamlessly interconnect with Internet email, allowing users to send MMS messages to email addresses and vice-versa. This bridged the gap between cellular-specific messaging and the broader Internet. It solved the interoperability problem between different vendors' MMSC implementations by providing a common, well-understood protocol layer.
Historically, SMTP's use predates 3GPP, originating in the early 1980s for ARPANET. Its integration into 3GPP, starting from the specifications around MMS, represented a pragmatic choice to leverage existing, robust Internet infrastructure rather than inventing a new transport protocol. This approach accelerated MMS deployment and ensured its longevity by aligning with global Internet standards.
What changed in its specifications
The latest release-to-release comparison of specifications that define SMTP. Each summary describes the whole specification, not only this term.
Rel-6 added online charging reference point IM9 and updated MMS charging details.
Full comparison in TS 23.140 →Rel-19 adds CMCD reporting, multi-source media delivery, content steering, QoS enhancements, and QUIC-based streaming.
Full comparison in TS 26.804 →Defining Specifications
3GPP specifications that define or reference SMTP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.945 v300 | Fax Services Guidance for GSM/UMTS | R99 read |
| TS 23.140 v690 | MMS Stage 2 & 3 Specification | Rel-6 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TS 29.198 v340 | OSA R99 API Stage 3 Specification | R99 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |