Description
The Signalling Transport Network (STN) refers to the underlying transport architecture responsible for carrying signalling protocol messages within and between Public Land Mobile Network (PLMN) domains. Unlike the user plane, which transports the actual voice, video, or data payload, the signalling plane carries the control messages that establish, manage, and tear down these communication sessions. The STN provides the reliable, low-latency, and secure pathways for these critical messages. It is not a single protocol but a network concept that encompasses physical links, switching nodes, and the transport layer protocols (like SCTP, M3UA, SUA) that ensure signalling message delivery.
Architecturally, the STN interconnects all core network signalling nodes, such as the Mobile Switching Center (MSC), Visitor Location Register (VLR), Home Location Register (HLR), Serving GPRS Support Node (SGSN), and later the Mobility Management Entity (MME) and Home Subscriber Server (HSS). In traditional circuit-switched (CS) networks, signalling often used Time-Division Multiplexing (TDM) based SS7 (Signalling System No. 7) networks. With the evolution to all-IP core networks, the STN migrated to an IP-based infrastructure, using protocols like SIGTRAN (Signalling Transport) to adapt traditional SS7 signalling (like MAP, CAP) over IP transport layers such as Stream Control Transmission Protocol (SCTP). This IP-based STN provides greater flexibility, scalability, and cost-efficiency compared to legacy TDM networks.
How the STN works involves layered protocol stacks. At the lowest level, it relies on standard IP network infrastructure (routers, switches). On top of this, SCTP provides a connection-oriented, reliable transport service with multi-homing and multi-streaming capabilities, which are crucial for signalling availability and load distribution. Adaptation layers like M3UA (MTP3 User Adaptation) or SUA (SCCP User Adaptation) then map the native signalling application parts (e.g., ISUP, MAP) to the SCTP transport. The STN's role is to route these encapsulated signalling messages based on destination point codes or IP addresses. Network elements use the STN to query subscriber databases (HLR/HSS), perform handovers, authenticate users, and manage charging sessions. Its performance directly impacts key network metrics like call setup time, handover success rate, and overall network reliability.
Purpose & Motivation
The STN concept was formalized to address the growing complexity and scale of signalling in modern mobile networks, which far exceeded the capabilities of in-band or channel-associated signalling. Early mobile networks relied on dedicated timeslots for signalling within the traffic channels, which was inefficient and limited scalability. The creation of a separate, common channel signalling network—initially based on SS7—solved this by providing a high-performance, out-of-band network dedicated solely to control messages. This separation allowed for more sophisticated services, faster call setup, and efficient network-wide database queries.
The evolution to an IP-based STN, prominently from 3GPP Release 8 onwards with the System Architecture Evolution (SAE), was motivated by several factors. Legacy TDM-based SS7 networks were expensive to maintain and scale, used proprietary hardware, and were not well-suited for the data explosion and new IP-based services. The industry's move towards all-IP core networks (IMS, LTE) necessitated a converged IP transport layer for both user and control planes. An IP-based STN, using SIGTRAN, allowed operators to leverage cheaper, standardized IP equipment, simplify network architecture, and seamlessly integrate with emerging IP-based services and network functions. It solved the problem of interworking between legacy circuit-switched signalling and new IP-based application servers, enabling a smoother transition to next-generation networks.
Key Features
- Dedicated infrastructure for reliable, out-of-band signalling transport
- Supports both legacy SS7 and IP-based (SIGTRAN) signalling paradigms
- Utilizes SCTP for reliable, connection-oriented transport with multi-homing
- Enables interconnection between circuit-switched and packet-switched core network domains
- Critical for mobility management, session control, and subscriber database access
- Provides the foundation for signalling security and network resiliency
Evolution Across Releases
The STN was formally addressed in the context of IP Multimedia Subsystem (IMS) and Evolved Packet Core (EPC) architecture. The initial architecture emphasized the transition to an all-IP signalling transport layer, defining the use of SIGTRAN protocols (SCTP, M3UA) to carry legacy MAP and CAP signalling over IP networks between entities like the MSC Server and the HSS/HLR, facilitating CS-EPC interworking.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.237 | 3GPP TS 23.237 |
| TS 24.216 | 3GPP TS 24.216 |
| TS 24.237 | 3GPP TS 24.237 |
| TS 28.734 | 3GPP TS 28.734 |
| TS 28.735 | 3GPP TS 28.735 |
| TS 28.736 | 3GPP TS 28.736 |
| TS 29.165 | 3GPP TS 29.165 |
| TS 32.741 | 3GPP TR 32.741 |
| TS 32.742 | 3GPP TR 32.742 |
| TS 32.743 | 3GPP TR 32.743 |
| TS 32.745 | 3GPP TR 32.745 |
| TS 32.746 | 3GPP TR 32.746 |