Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

ISUP

MIME ISDN User Part Multi-purpose Internet Mail Extension

Protocol →

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.

Introduced
Rel-2
Where
Services › IMS
Specifications
17 specs
Also in
Core Network
ISUP Description Purpose What changed Neighbours 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).

What changed in its specifications

The latest release-to-release comparison of specifications that define ISUP. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.228Rel-18 → Rel-19

Rel-19 TS 23.228 adds SBI service operations for IMS data channels, event subscription, and user information, plus HSS lookup of the serving IMS AS. It adds PS Data Off handling for IMS Data Channel services and Multimedia Priority Service for Messaging.

Full comparison in TS 23.228 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-2 Initial

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

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.226 vj00 Global Text Telephony (GTT) Stage 2 Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.806 v700 Voice Call Continuity between CS and IMS Rel-7 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TS 24.411 v830 3GPP TS 24411 v830: Anonymous Communication Rejection and Communication Barring Rel-8 read
TS 24.504 v8m0 Communication Diversion (CDIV) Protocol Specification Rel-8 read
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8 read
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19 read
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19 read
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19 read
TS 29.332 vj00 MGCF-IM-MGW Interface Protocol (Mn) Rel-19 read
TS 29.424 v801 H.248 Profile for Trunking Media Gateways Rel-8 read
TS 29.458 v850 SIP Transfer of Tariff Info for Charging Rel-8 read
TS 29.658 vj00 SIP Transfer of Tariff Information Rel-19 read
TS 29.863 v820 IMS-CS Multimedia Interworking Feasibility Study Rel-8 read