Description
Multi-purpose Internet Mail Extensions (MIME) is an Internet standard (originally defined in IETF RFCs) that fundamentally enhances the capabilities of Internet mail by allowing the inclusion of diverse content types beyond plain ASCII text. Its core mechanism is the use of standardized headers within the email message structure to describe the nature of the content. The most important header is `Content-Type`, which specifies the media type (e.g., `text/plain`, `image/jpeg`, `application/pdf`) and often a subtype, effectively telling the receiving mail client how to interpret the message body. Another key header is `Content-Transfer-Encoding`, which specifies how the binary or non-ASCII data is encoded into a ASCII-compatible format (like Base64 or quoted-printable) for safe transmission through legacy mail systems.
Within the 3GPP architecture, MIME is not used for email per se but is leveraged as a generic and powerful framework for structuring and describing content in various protocols and services. Its primary application is as a container format. For example, in the Multimedia Messaging Service (MMS), the entire multimedia message (comprising text, images, audio clips) is packaged as a MIME multipart message, allowing a single message entity to contain multiple body parts of different types. Similarly, in the IP Multimedia Subsystem (IMS), SIP (Session Initiation Protocol) messages use MIME to carry session description information (using the `application/sdp` type) and other application-specific payloads. The Session Description Protocol (SDP) body describing a multimedia session is attached to a SIP message as a MIME part.
The technical operation involves the sender's application constructing a MIME entity according to the relevant 3GPP specification. This involves setting the appropriate headers (`Content-Type`, `Content-ID`, `Content-Location`) and encoding the body data. For multipart messages, boundaries are defined to separate each body part. This structured entity is then transmitted over the network protocol (e.g., HTTP for MMS, SIP for IMS). The receiver's application parses the MIME headers to identify the content type of each part, decodes the transfer encoding if necessary, and then dispatches each part to the appropriate handler (e.g., an image decoder, an audio player, or a session management function for SDP). This abstraction allows 3GPP services to handle rich, complex content in a standardized and interoperable way, independent of the underlying transport mechanism.
Purpose & Motivation
MIME was created to solve the severe limitations of the original Internet email standard (RFC 822), which only supported 7-bit ASCII text. This made it impossible to send messages in non-Latin alphabets (like Japanese or Cyrillic), and impossible to include binary files like software, images, or sound. The purpose of MIME was to break these barriers, enabling global, multimedia communication via email without requiring changes to the existing mail transport infrastructure. It did this by adding descriptive headers to messages, allowing the mail content to be labeled and encoded appropriately.
3GPP adopted MIME extensively because it provided a ready-made, robust, and widely implemented standard for content encapsulation and description. As 3GPP developed multimedia services like MMS and IMS, they faced the same fundamental problem: how to package and signal a mixture of different media types (text, image, video, control information) over various transport protocols. Developing a new, proprietary content format would have been inefficient and hindered interoperability. MIME offered a proven solution. For MMS, it provided the perfect envelope for a multimedia message. For IMS, it allowed SIP, a text-based signaling protocol, to carry binary or structured session data (like SDP) in a self-describing manner. Its adoption solved the problem of content negotiation and handling in a multi-vendor, multi-operator environment, ensuring that a picture message sent from a phone on one network could be correctly displayed on a phone from a different manufacturer on another network.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (64 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-2, normative work from Rel-15.
In Release 15, the MIME function was enhanced to support new IP Multimedia Core Network (IM CN) subsystem-based services, including Message Waiting Indication (MWI), Completion of Communications (CCBS/CCNR), and Advice of Charge (AOC). These additions expanded the use of MIME-based messaging protocols within the MMSE architecture for supplementary service delivery. Furthermore, support for Group Configuration Multi-Talker and multiple devices was introduced, integrating these capabilities into the existing MMS framework and its associated interfaces.
- IMS multimedia telephony communication service and supplementary services TS 24.173CR0122
- Support for multiple devices TS 24.281CR0044
- Group Configuration Multi-Talker TS 24.481CR0028
- Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.606CR0020
- Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.642CR0088
- Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem TS 24.647CR0030
+ 1 more changes
In Release 16, the MIME function was enhanced to support new Multi-Device and Multi-Identity services, enabling interactions for these services within the MMSE. These additions allowed the MMS User Agent to operate on behalf of multiple identities and devices, expanding the service's flexibility. Furthermore, the release introduced mechanisms for the notification of downlink data delivery status and availability after a DDN failure notification across multiple Application Functions.
- Multi-Device and Multi-Identity services TS 24.173CR0137
- Adding interactions with "Multi-Device" and "Multi-Identity" services TS 24.606CR0026
- Adding interactions with "Multi-Device" and "Multi-Identity" services TS 24.642CR0089
- Adding interactions with "Multi-Device" and "Multi-Identity" services TS 24.647CR0031
- Notification of Downlink data delivery status and availability after DDN failure notification for multiple Afs TS 29.122CR0156
- Initial report for multiple PDN connections TS 29.122CR0277
In Release 17, the key new feature for the MIME function was the introduction of integrity protection for specific MIME body types, namely `pidf+xml` and `xcap-diff+xml`. This enhancement addressed security by ensuring these XML-based content formats could be verified for tampering during transmission. No other MIME-specific changes are indicated by the provided CR titles or grounding context.
- Data types applicable to multiple resource representations TS 24.546CR0015
- [5MBP3] User Service Extensions for 5GMS via eMBMS TS 26.346CR0660
- Support for Multiple QoS Class in deferred location request TS 29.122CR0491
- Supporting multiple events per subscription on MonitoringEvent API TS 29.122CR0534
- Integrity protection of pidf+xml and xcap-diff+xml MIME bodies TS 24.281CR0119
- Add support for multiple IPConn communications TS 24.282CR0318
+ 2 more changes
In Release 18, the MIME function was enhanced with corrections and clarifications for the inclusion of multiple MIME bodies, specifically for ad-hoc group call and data communication requests in MCVideo and MCData services. The release also included fixes to the references for the `application/resource-lists+xml` MIME body type and corrections to the `application/pidf+xml` MIME body extensions. These updates ensured proper protocol implementation for general ad-hoc group communication procedures across multiple systems.
- MCVideo support of multiplexing - SDP offers and answers TS 24.281CR0215
- General adhoc group call procedures in multiple systems - Protoc impl for MCVideo TS 24.281CR0235
- General adhoc group comm procedures in multiple systems - Protoc impl for MCData TS 24.282CR0377
- MCPTT support of multiplexing - SDP offers and answers TS 24.379CR0889
- General adhoc group call procedures in multiple systems - Protoc impl for MCPTT TS 24.379CR0927
- Changes to support Multiparty RTT in TS 26.114 TS 26.114CR0558
+ 22 more changes
In Release 19, the MIME function was updated to add missing MIME bodies in the service procedures and to update the specified MIME types for CBOR payloads. These changes ensured the Multimedia Messaging Service (MMS) encapsulation protocols remained complete and aligned with current data formats. The updates were made to maintain the service's foundation, which relies on MIME for the realization of non-realtime multimedia messaging.
- Audio mixing is performed in the UE or in the network to support multi-talker control TS 24.481CR0093
- Multi-talker configuration TS 24.484CR0283
- Support for Multi-modal flows synchronization monitoring TS 24.543CR0081
- Addition of IMS DC multiplexing support TS 26.114CR0579
- [FS_AMD] Update to multiple service location media delivery recommendations for stage 3 TS 26.804CR0027
- Introduce (S)RTP Multiplexed Media Information TS 29.122CR0889
+ 9 more changes
Explore further
Broader topics and technologies where MIME plays a role.
Defining Specifications
3GPP specifications that define or reference MIME, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.140 v1600 | MMS Non-Realtime Service Definition | Rel-6 |
| TS 24.141 vj00 | Presence Service Protocol Details | Rel-19 |
| TS 24.173 vj00 | Multimedia Telephony Service and Supplementary Services in IMS | Rel-19 |
| TS 24.281 vj40 | MCVideo Signalling Control Specification | Rel-19 |
| TS 24.282 vj50 | MCData Signalling Control Protocols | Rel-19 |
| TS 24.334 vj00 | ProSe Protocols and Procedures | Rel-19 |
| TS 24.379 vj50 | Mission Critical Push To Talk (MCPTT) call control | Rel-19 |
| TS 24.406 v810 | Message Waiting Indication (MWI) Protocol | Rel-8 |
| TS 24.423 v850 | PSTN/ISDN Simulation Services XCAP Protocol | Rel-8 |
| TS 24.447 v800 | Advice Of Charge (AOC) Service Protocol | Rel-8 |
| TS 24.481 vj20 | Mission Critical Services (MCS) group management | Rel-19 |
| TS 24.484 vj30 | MCS Configuration Management | Rel-19 |
| TS 24.543 vj50 | SEAL Data Delivery Management Protocol | Rel-19 |
| TS 24.544 vj00 | SEAL Group Management Protocol | Rel-19 |
| TS 24.546 vj10 | SEAL Configuration Management Protocol Specification | Rel-19 |
| TS 24.583 vj00 | Application Layer Support for Personal IoT Network | Rel-19 |
| TS 24.606 vj00 | MWI Service Protocol Description | Rel-19 |
| TS 24.623 vj00 | XCAP Protocol for Supplementary Services | Rel-19 |
| TS 24.642 vj00 | CCBS/CCNR/CCNL SIP Protocol Specification | Rel-19 |
| TS 24.647 vj00 | Advice of Charge (AOC) service protocol | Rel-19 |
| TS 24.802 vc10 | IMS II-NNI Traversal Scenario Determination Study | Rel-12 |
| TS 24.841 v1600 | Presence Service IP Multimedia Subsystem | Rel-6 |
| TS 26.114 vj10 | IMS Multimedia Telephony Media Handling | Rel-19 |
| TS 26.118 vj00 | Virtual Reality Media Formats | Rel-19 |
| TS 26.140 vj00 | MMS Media Formats and Codecs Specification | Rel-19 |
| TS 26.141 vj00 | IMS Messaging & Presence Media Formats | Rel-19 |
| TS 26.142 vj00 | 3GPP TS 26.142: Dynamic and Interactive Multimedia Scenes (DIMS) | Rel-19 |
| TS 26.143 vj00 | 5G Messaging Media Types and Codecs | Rel-19 |
| TS 26.223 vj00 | IMS Telepresence Client Specification | Rel-19 |
| TS 26.234 vj00 | 3GPP PSS Protocols and Codecs Specification | Rel-19 |
| TS 26.244 vj00 | 3GPP File Format (3GP) Specification | Rel-19 |
| TS 26.246 vj00 | 3GPP SMIL Language Profile Specification | Rel-19 |
| TS 26.247 vj00 | 3GPP Progressive Download & DASH over HTTP | Rel-19 |
| TS 26.346 vj20 | MBMS User Services Media Codecs & Protocols | Rel-19 |
| TS 26.512 vj10 | 5G Media Streaming Protocols & APIs | Rel-19 |
| TS 26.804 vj10 | 5G Media Streaming Extensions Study | Rel-19 |
| TS 26.841 vj00 | Study on Media Messaging Enhancements | Rel-19 |
| TS 26.849 vc10 | MBMS Operation on Demand (MooD) | Rel-12 |
| TS 26.851 vb20 | Enhancements to Multimedia (EMM) for PSS, MMS, MBMS | Rel-11 |
| TS 26.852 ve20 | MBMS user service profiles, APIs and transport enabler study | Rel-14 |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 |
| TR 26.946 vj00 | MBMS User Services Overview | Rel-19 |
| TR 26.955 vj00 | Video Codec Analysis for 5G Services | Rel-19 |
| TS 29.122 vj40 | T8 Reference Point for Northbound APIs | Rel-19 |
| TS 29.231 vj00 | Application of SIP-I Protocols to CS Core Network | Rel-19 |
| TS 29.235 vj00 | SIP-I CS Core Network Interworking | Rel-19 |
| TS 29.332 vj00 | MGCF-IM-MGW Interface Protocol (Mn) | Rel-19 |
| TS 29.414 vj00 | Nb Interface Bearer Transport & Control Protocols | Rel-19 |
| TS 29.598 vj40 | UDSF Service Based Interface Stage 3 Protocol | Rel-19 |
| TS 32.270 vj00 | MMS Charging Management Specification | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 34.229 vj21 | IMS SIP/SDP UE Conformance Testing for 5GS | Rel-19 |
| TS 36.579 | 3GPP TR 36.579 | Rel-2 |
| TS 37.579 vi40 | Mission Critical services conformance testing | Rel-18 |