ISUP

MIME ISDN User Part Multi-purpose Internet Mail Extension

Protocol →
Introduced in Rel-2 Also in: Core Network

ISUP is the adaptation of the traditional ISDN User Part signaling protocol for transport over IP networks using MIME encapsulation, enabling legacy call control signaling within SIP frameworks for network interworking.

Category
Protocol
Introduced
Rel-2
Where
Services › IMS
Also touches
1 segments
Specifications
17 specs
ISUP Description Purpose Related Classification Detected Changes Specifications

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).

Classification

Part ofSS7
Specific typesBCICICIAMNOASS7UUIUUS
Related approachesSIPIMS

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (14 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-2, normative work from Rel-16.

Rel-16 1 change

In Release 16, the ISUP function was enhanced to support new interactions with "Multi-Device" and "Multi-Identity" services. These additions address service requirements for an End-User associated with multiple subscriptions through identities and for communications involving multiple parties or connections within a single session. This enables more complex multimedia service configurations.

  • Adding interactions with "Multi-Device" and "Multi-Identity" services TS 24.604CR0188
Rel-18 1 change

In Release 18, the new development for the ISUP function was the introduction of multiplexing for IMS data channels. This enhancement allows for the simultaneous handling of multiple data streams within a single communication session. It supports services characterized by the transfer of multiple types of media, such as audio and video, in a synchronized way.

  • Multiplexing of IMS data channels TS 23.228CR1444
Rel-19 12 changes

In Release 19, the primary new work for ISUP focused on enhancing the multiplexing of multiple Data Channel (DC) applications over a single SCTP connection. This included updates, corrections, and clarifications to the multiplexing and de-multiplexing procedures, specifically addressing capability negotiation and handling to prevent multiple Application Data Channels (ADCs) from using the same stream identifier. The refinements aimed to ensure robust and efficient support for multiplexed data streams within the IMS framework.

  • Support of multiplexing multiple DC applications over single SCTP connection TS 23.228CR1511
  • Updates to support multiplexing multiple DC applications over single SCTP connection TS 23.228CR1552
  • Service updates to support multiplexing multiple DC applications over single SCTP connection TS 23.228CR1586
  • Update on multiplexing handling TS 23.228CR1583
  • Correction on DC multiplexing capability negotiation TS 23.228CR1622
  • De-multiplexing ADC to avoid multiplexing ADCs with same stream ID TS 23.228CR1584

+ 6 more changes

Explore further

Broader topics and technologies where ISUP plays a role.

Defining Specifications

3GPP specifications that define or reference ISUP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.226 vj00 Global Text Telephony (GTT) Stage 2 Rel-19
TS 23.228 vj50 IMS Stage-2 Service Description Rel-19
TS 23.806 v1700 Voice Call Continuity between CS and IMS Rel-7
TS 24.206 v1700 Voice Call Continuity Between CS and IMS Rel-7
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19
TS 24.411 v1830 ACR and CB Service Protocol Specification Rel-8
TS 24.504 v8m0 Communication Diversion Services Stage 3 Rel-8
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19
TS 29.332 vj00 MGCF-IM-MGW Interface Protocol (Mn) Rel-19
TS 29.424 v801 H.248 Profile for Trunking Media Gateways Rel-8
TS 29.458 v850 SIP Transfer of Tariff Info for Charging Rel-8
TS 29.658 vj00 SIP Transfer of Tariff Information Rel-19
TS 29.863 v820 IMS-CS Multimedia Interworking Feasibility Study Rel-8