Description
The SCCP Unitdata (UDT) message is a fundamental component of the Signaling Connection Control Part (SCCP) protocol within the SS7/C7 signaling system, which is integral to traditional circuit-switched and early packet-switched core networks in 3GPP architectures. SCCP operates at Layer 4 of the SS7 protocol stack, providing enhanced routing and management capabilities above the basic Message Transfer Part (MTP). The UDT message is a connectionless service, meaning it does not require the establishment and maintenance of a logical connection or virtual circuit between signaling points before data transfer. Each UDT message is an independent datagram containing the complete addressing information—specifically the Called Party Address (CdPA) and Calling Party Address (CgPA)—along with the user data, or signaling information, that needs to be delivered. The SCCP layer at the originating node routes the UDT based on the CdPA, utilizing MTP services for actual transmission across the signaling network. Upon receipt, the destination node's SCCP layer processes the message and delivers the user data to the appropriate upper-layer application, such as Mobile Application Part (MAP) or Base Station System Application Part (BSSAP).
The architecture supporting UDT involves the SCCP protocol entity at each signaling point, which interfaces with the MTP below and various application parts above. Key components within the UDT message format include the protocol discriminator to identify SCCP, the message type code for UDT, and parameters for length, mandatory fixed parts (like CdPA and CgPA), and optional variable parts containing the actual user data and any optional parameters like segmentation or sequencing indicators, though full segmentation is not supported by the basic UDT. The routing capability of SCCP, using Global Title (GT) translation, allows UDT messages to be routed based on dialed digits or other identifiers, enabling flexible and scalable signaling across international and national networks without requiring each node to have point-code knowledge of every other node.
In the 3GPP network context, UDT messages are employed in numerous procedures, especially in early releases (R99 and Rel-4), for non-circuit-related signaling where a persistent connection is not justified. For instance, they are used for location updates, subscriber authentication, and short message service (SMS) delivery between core network elements like the Home Location Register (HLR), Visitor Location Register (VLR), and Mobile Switching Center (MSC). The role of UDT is to provide a lightweight, efficient mechanism for transferring discrete units of signaling data, minimizing signaling load and delay for transactions that are brief and self-contained. While later 3GPP architectures evolved towards IP-based signaling protocols like SIGTRAN and Diameter, the UDT message and SCCP connectionless service remained a cornerstone for legacy interworking and certain administrative functions, ensuring backward compatibility and reliable signaling transport in hybrid network environments.
Purpose & Motivation
The SCCP Unitdata message was created to fulfill the need for a simple, efficient, and connectionless signaling transport mechanism within telecommunication networks based on the SS7 standard. Prior to SCCP's development, signaling was primarily handled by the Message Transfer Part (MTP), which provided basic message routing based on physical point codes but lacked the flexibility for advanced, application-level addressing and global routing. This limitation became acute with the growth of mobile networks and intelligent network services, which required signaling transactions between nodes that might not have direct point-code relationships or that needed to be identified by logical addresses (like subscriber numbers). The UDT service addresses this by allowing signaling messages to be routed using Global Titles, enabling databases like HLRs to be queried from any network node without pre-configured direct signaling links.
The motivation for a connectionless service, as opposed to a connection-oriented one, stems from the nature of many signaling transactions, which are short, request-response interactions that do not justify the overhead of establishing and tearing down a virtual circuit. Examples include querying a database for subscriber data or delivering a single SMS. Establishing an SCCP connection would involve additional messages (connection request and confirm) and state maintenance at both ends, consuming network resources and increasing latency for simple transactions. UDT provides a datagram-like service that minimizes this overhead, offering lower latency and reduced signaling load for such applications. It solves the problem of efficient, scalable signaling for non-circuit-related functions, which was essential for the deployment of advanced mobile services like roaming and SMS in GSM and UMTS networks.
Historically, UDT was introduced in 3GPP R99 as part of the inherited GSM/SS7 core network signaling framework. Its creation was motivated by the need to support the burgeoning signaling traffic associated with mobility management, call-independent supplementary services, and SMS in a standardized, interoperable manner. While later 3GPP releases introduced IP-based alternatives, UDT remained relevant for interworking with legacy SS7 networks and for certain internal core network procedures, ensuring continuity and reliability as networks evolved. The limitations it addressed—namely, inefficient circuit-oriented signaling for brief transactions and inflexible MTP-based routing—were critical bottlenecks in early digital telecommunication networks, and UDT's connectionless model provided a robust solution that underpinned decades of reliable signaling.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, no new technical specifications or changes were introduced for the SCCP Unitdata (UDT) message function itself within the provided grounding context. The listed Change Request titles focus entirely on new 5GS NAS message types, security headers, and session identities, which are unrelated to the legacy SCCP transport mechanisms used for LCS signaling like the UDT. The grounding context describes the existing, unchanged use of SCCP connection-oriented and connectionless signaling, including UDT messages, for transporting positioning protocols like BSSLAP and SMLCPP in GSM/UMTS networks.
In Release 16, the SCCP Unitdata (UDT) message function was updated to support the transport of Proximity Services (ProSe) signalling messages. Specifically, the enhancements enabled these new ProSe messages to be sent over the PC3 and PC5 reference point interfaces. This extended the use of SCCP connectionless signaling to facilitate direct device-to-device communication scenarios.
- Updates due to ProSe signalling messages sent over the PC3 or PC5 interfaces TS 24.007CR0138
In Release 17, the enhancements for the SCCP Unitdata (UDT) message function focused on providing corrections to Layer 3 messages to ensure reliable transport. Specifically, the updates reinforced the segmentation mechanisms for large LCS messages, such as SMLCPP and BSSLAP, to guarantee their reliable and sequenced delivery when using SCCP connectionless signaling. These corrections ensured that positioning-related message flows between network entities like the SMLC, MSC, and BSC remained robust over the supported transport protocols.
- Corrections to L3 Messages description TS 24.007CR0141
In Release 19, the updates to the SCCP Unitdata (UDT) function primarily involved corrections to ensure proper message routing and transfer. Specifically, this included a correction to the EPD (External Part of Destination address) for 5GS message routing and a correction to the sequenced message transfer operation. These changes aimed to maintain reliable transport of LCS signaling messages, such as BSSLAP and SMLCPP, over interfaces like Ls and Lb where SCCP is used.
- AIoT NAS message type extension for future use TS 24.007CR0172
- Correction of EPD for 5GS message routing TS 24.007CR0161
- Correction to message type octet (when accessing Release 99 and newer networks) TS 24.007CR0169
- Correction to sequenced message transfer operation and figure naming TS 24.007CR0170
- Correction to AIoT NAS message type TS 24.007CR0173
Explore further
Broader topics and technologies where UDT plays a role.
Defining Specifications
3GPP specifications that define or reference UDT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 03.071 v7b0 | Location Services (LCS) Stage 2 Description | Rel-7 |
| TS 23.171 v1300 | LCS Stage 2 Specification for UMTS | Rel-4 |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 |
| TS 24.007 vj40 | GSM Um Interface Layer 3 Architecture | Rel-19 |
| TS 29.204 vj00 | SS7 Security Gateway Functional Description | Rel-19 |
| TS 43.059 vj00 | GERAN LCS Stage 2 Specification | Rel-19 |