Description
A signalling connection in 3GPP terminology refers to an acknowledged-mode logical link established between the User Equipment (UE) and the core network (CN) to transport Non-Access Stratum (NAS) messages. This connection is essential for control-plane procedures such as authentication, security mode control, tracking area updates, and session management. Unlike the signalling link, which operates at the access stratum level between the UE and the radio access network (RAN), the signalling connection spans the entire path from the UE to the core network, traversing the RAN as a transparent conduit.
The signalling connection is typically established during initial UE attachment or when the UE transitions from idle to connected mode. In LTE, this involves the UE sending an RRC Connection Request to the eNodeB, which then forwards a NAS Attach Request to the MME. The MME and UE then exchange NAS messages over this connection, which is maintained as long as the UE remains in connected mode or until the connection is released due to inactivity or explicit detach. The connection is identified by a unique identifier, such as the S-TMSI (SAE Temporary Mobile Subscriber Identity) or a globally unique temporary identity (GUTI), which allows the core network to route messages to the correct UE.
In 5G, the signalling connection is similarly established between the UE and the AMF (Access and Mobility Management Function). The UE may be in CM-IDLE or CM-CONNECTED state. In CM-CONNECTED, a signalling connection exists, enabling the AMF to send and receive NAS messages. The connection is maintained even if the UE moves between different gNodeBs, thanks to the N2 interface between the RAN and AMF. This mobility support is crucial for seamless service continuity.
The signalling connection provides reliability through acknowledged-mode transmission, meaning that messages are retransmitted if not acknowledged. This is typically handled by the underlying RRC and PDCP layers, which ensure integrity and ciphering. The connection also supports multiple NAS messages in a single RRC message (piggybacking) to reduce overhead. Security is enforced via NAS integrity protection and ciphering, preventing eavesdropping and tampering.
Key procedures that rely on the signalling connection include: initial attach, service request, tracking area update, handover, and detach. For example, during a handover, the source RAN forwards the UE's NAS messages to the target RAN, which then relays them to the core network, maintaining the signalling connection. If the connection is lost, the UE must re-establish it, which may involve re-authentication and re-establishment of radio bearers.
The signalling connection is distinct from the signalling link, which is the lower-layer acknowledged-mode link between the UE and the RAN. The signalling connection is an end-to-end concept, while the signalling link is hop-by-hop. Together, they form the complete control plane path for NAS signalling. The signalling connection is also different from a user-plane connection (e.g., EPS bearer), which carries actual data. The separation allows the core network to manage control and user planes independently, a key principle of 3GPP architecture.
In summary, the signalling connection is a fundamental enabler of UE-core network communication, providing a reliable, secure, and mobile-aware channel for NAS signalling. Its design ensures that control procedures can be performed efficiently and securely, regardless of the UE's location or access technology.
Purpose & Motivation
The signalling connection exists to provide a reliable and secure channel for Non-Access Stratum (NAS) signalling between the UE and the core network. It solves the problem of how to transport control messages that are not specific to the radio access technology but are essential for core network functions like authentication, mobility management, and session management. Without it, the UE would not be able to register with the network, establish data sessions, or maintain connectivity while moving.
Historically, in 2G and 3G networks, signalling connections were managed by the Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN) for packet-switched services, and by the Mobile Switching Center (MSC) for circuit-switched services. These connections were often complex and tied to specific access technologies. With the advent of LTE, 3GPP introduced a flatter, all-IP architecture where the MME handles NAS signalling, and the signalling connection became a well-defined concept between the UE and MME. This simplified the core network and improved scalability.
The motivation for a dedicated signalling connection includes: (1) decoupling core network signalling from radio access signalling, allowing independent evolution; (2) enabling mobility across different RAN nodes without re-establishing NAS connections; (3) providing security through NAS-level ciphering and integrity protection; and (4) supporting efficient paging and reachability. In 5G, the signalling connection is further enhanced to support network slicing, where different slices may have different signalling requirements. Thus, the signalling connection remains a cornerstone of 3GPP control plane design.
What changed in its specifications
The latest release-to-release comparison of specifications that define Signalling connection. Each summary describes the whole specification, not only this term.
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 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Signalling connection, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |