SCCP Extended Unitdata

Description

The SCCP Extended Unitdata (XUDT) message is a protocol data unit within the Signaling System No. 7 (SS7) stack, specifically for the Signaling Connection Control Part (SCCP) in connectionless service class 0 or 1. SCCP itself sits atop the Message Transfer Part (MTP) and provides enhanced addressing (Global Title translation) and message transfer services. The XUDT message is designed to transport user data (the SCCP user message) in a connectionless manner, meaning no dedicated signaling connection is established beforehand. Its key architectural role is to overcome a limitation of the basic Unitdata (UDT) message: the UDT can only carry a limited amount of user data defined by the underlying MTP limits. The XUDT message introduces two critical optional parameters: Segmentation and Reassembly. When an SCCP user message is too large for a single XUDT, the originating SCCP node can segment it into multiple XUDT messages, each containing a segment of the original data and a segmentation parameter indicating its position. The receiving SCCP node uses this parameter to reassemble the original message before delivering it to the upper layer. Another important parameter is the Hop Counter, which is decremented at each intermediate SCCP node acting as a transfer point (e.g., during Global Title routing). If the counter reaches zero, the message is discarded, preventing endless looping in the network. The message structure includes mandatory parameters like the Protocol Class, Source and Destination Local References (set to zero for connectionless), and Called/Calling Party Addresses, along with the Data parameter containing the actual user payload. The XUDT is acknowledged at the MTP level but not at the SCCP level for connectionless service, making it a 'send and forget' datagram with segmentation support.

Purpose & Motivation

The XUDT message was created to address the need for transferring larger blocks of signaling data in a connectionless SS7 network without establishing a costly and stateful SCCP connection. The basic UDT message was sufficient for short queries and responses but became a bottleneck for applications requiring larger data transfers, such as certain MAP (Mobile Application Part) operations or bulk data exchanges. The primary problem XUDT solves is the size limitation. By enabling segmentation and reassembly, it allows SCCP to transparently handle user messages that exceed the maximum transmission unit of the underlying MTP, without requiring the application layer to manage the fragmentation. This enhances the flexibility and efficiency of the signaling network. The hop counter mechanism addresses network reliability by providing a simple loop prevention mechanism for messages that are routed through multiple SCCP nodes via Global Title Translation, a common scenario in international roaming or distributed network architectures. Its introduction supported the evolution of more complex telecommunication services in 2G (GSM) and 3G (UMTS) core networks that relied on SS7 signaling, providing a robust, connectionless transport mechanism for critical non-circuit-related signaling.

Key Features

• Supports connectionless transfer of SCCP user messages with segmentation capability.
• Includes optional Segmentation parameter to allow splitting a large message into multiple XUDT packets.
• Includes optional Hop Counter parameter for loop prevention during Global Title routing.
• Carries mandatory Called and Calling Party Address parameters for SCCP routing.
• Uses Protocol Class to define handling characteristics (e.g., with or without message sequence control).
• Enables transfer of user data larger than the maximum size supported by the basic UDT message.

Evolution Across Releases

Defining Specifications