Description
The MIME ISDN User Part (ISUP) is a specification for encapsulating and transporting messages from the ISDN User Part protocol—a core component of Signaling System No. 7 (SS7) used for setting up, managing, and tearing down telephone calls in the Public Switched Telephone Network (PSTN)—within IP-based protocols. It utilizes the Multi-purpose Internet Mail Extensions (MIME) format to package the binary ISUP message content into a format suitable for transmission over TCP/IP networks, typically within the body of a Session Initiation Protocol (SIP) message or other IP signaling payload. This encapsulation allows a Media Gateway Controller (MGC) or Softswitch to interpret and generate ISUP signaling without a direct TDM-based SS7 link, enabling seamless call control between IP networks (like IMS) and the legacy PSTN or PLMN. The process involves a signaling gateway that performs protocol conversion, mapping ISUP parameters to and from the encapsulated MIME format. Key architectural components include the Signaling Gateway (SG) for SS7/IP interworking, the Media Gateway Controller for call control logic, and the application servers that handle the MIME-encoded content. Its role is critical in the transition to all-IP networks, providing a standardized method for preserving rich call-associated signaling information like caller ID, call forwarding indications, and cause codes during network traversal.
Purpose & Motivation
The MIME encapsulation for ISUP was developed to solve the problem of interworking between emerging IP-based telephony networks (such as those based on SIP) and the entrenched global PSTN/PLMN infrastructure that relies on SS7 and ISUP signaling. As operators began deploying Voice over IP (VoIP) and IMS networks, a method was needed to transparently carry the sophisticated call control information present in ISUP messages across IP boundaries without loss of functionality. Previous approaches involved simpler parameter mapping which could lose information or require proprietary extensions. The use of MIME provides a flexible, standardized container defined in IETF and 3GPP that can carry the complete, unaltered ISUP message payload, ensuring full feature transparency and supporting advanced telephony services during the migration phase. Its creation was motivated by the industry's move towards network convergence and the need for a future-proof, extensible mechanism to handle signaling interworking in Next Generation Networks (NGN).
Key Features
- Encapsulation of binary ISUP messages within MIME body parts
- Transport within SIP messages (e.g., in SIP INVITE or INFO requests)
- Support for transparency of all ISUP parameters and cause codes
- Enables interworking between IP-based call control and legacy SS7 networks
- Defined for use in 3GPP IMS and other NGN architectures
- Facilitates the implementation of trunking gateways and softswitches
Evolution Across Releases
Initial support for transporting ISUP signaling in the context of early UMTS and GSM network evolution towards IP. The architecture involved basic encapsulation methods to allow core network nodes to handle ISUP messages over IP transport as part of bearer-independent call control (BICC) and early VoIP interworking scenarios.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 23.226 | 3GPP TS 23.226 |
| TS 23.228 | 3GPP TS 23.228 |
| TS 23.806 | 3GPP TS 23.806 |
| TS 24.206 | 3GPP TS 24.206 |
| TS 24.259 | 3GPP TS 24.259 |
| TS 24.411 | 3GPP TS 24.411 |
| TS 24.504 | 3GPP TS 24.504 |
| TS 24.508 | 3GPP TS 24.508 |
| TS 24.604 | 3GPP TS 24.604 |
| TS 29.078 | 3GPP TS 29.078 |
| TS 29.278 | 3GPP TS 29.278 |
| TS 29.332 | 3GPP TS 29.332 |
| TS 29.424 | 3GPP TS 29.424 |
| TS 29.458 | 3GPP TS 29.458 |
| TS 29.658 | 3GPP TS 29.658 |
| TS 29.863 | 3GPP TS 29.863 |