Signalling Connection Control Part

Description

The Signalling Connection Control Part (SCCP) is a critical Layer 4 (Transport Layer) protocol in the SS7 (Signalling System No. 7) protocol stack, defined by ITU-T and adopted by 3GPP for core network signaling. It sits above the Message Transfer Part (MTP) Level 3, which provides basic message routing based on point codes. SCCP enhances MTP by providing two key services: connectionless service (Class 0 and 1) for datagram-style signaling and connection-oriented service (Class 2 and 3) for reliable, sequenced data transfer, analogous to a virtual circuit.

Architecturally, SCCP introduces two primary addressing mechanisms beyond the MTP's Destination Point Code (DPC). These are Subsystem Numbers (SSN) and Global Titles (GT). An SSN identifies a specific application within a node (e.g., SSN=6 for HLR, SSN=8 for MSC). A Global Title is an address like an E.164 MSISDN or an IMSI that does not directly map to a network point code. SCCP's key function, Global Title Translation (GTT), involves querying a database to translate a GT into a combination of DPC and SSN, enabling flexible, destination-based routing independent of the physical network topology. This allows signaling messages to be routed to the correct network entity (like an HLR) based on a subscriber's number.

In operation, for a connectionless transaction like a location update, an MSC will send an SCCP Unitdata message containing the subscriber's IMSI as a Global Title. A Signal Transfer Point (STP) performs GTT, converting the IMSI into the DPC and SSN of the appropriate HLR, and forwards the message. For connection-oriented services, SCCP manages connection establishment, data transfer with sequence control, and connection release. This is used for transactions requiring a dialog, such as between an MSC and an EIR. Within 3GPP networks, SCCP is the transport for higher-layer protocols like TCAP (Transaction Capabilities Application Part), which carries MAP (Mobile Application Part) and CAP (CAMEL Application Part) messages, forming the backbone of all non-circuit-related signaling.

Purpose & Motivation

SCCP was created to address the limitations of the basic MTP routing in SS7 networks. MTP routing is based solely on static point codes, which represent physical network nodes. This model is inflexible for large, distributed, and subscriber-centric networks like GSM/UMTS, where signaling needs to be routed to a logical database (like an HLR) based on a subscriber's identity, not the physical location of the querying node. SCCP's Global Title capability solved this by decoupling logical addressing from physical routing.

Another key problem it solved was the need for both simple query-response signaling and extended dialog-oriented signaling. MTP only provides unsequenced, connectionless service. SCCP introduced connection-oriented services with flow control and in-sequence delivery, which are necessary for certain complex transactions and for managing signaling connections in evolving network architectures. This provided the reliable transport required for advanced intelligent network (AIN) services and database queries.

Its adoption by 3GPP was driven by the need for a robust, standardized signaling transport for the Mobile Application Part (MAP) protocol, which handles all mobility management, call routing, and subscriber data exchanges. SCCP enabled the scalable, hierarchical, and globally interoperable core network that made GSM and subsequent 3GPP technologies successful, allowing subscribers to roam worldwide by ensuring signaling messages could find their way to the correct home network databases.

Key Features

• Provides both connectionless (UDT) and connection-oriented services
• Enables Global Title addressing and routing (GTT) for logical destination routing
• Uses Subsystem Numbers (SSN) to identify specific applications within a node
• Supports segmentation and reassembly of long signaling messages
• Offers in-sequence delivery and flow control for connection-oriented services
• Serves as the transport layer for TCAP, MAP, and CAP protocols

Evolution Across Releases

Defining Specifications