Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

RRC Connection

Radio Resource Control Connection

Radio Access Network →

RRC Connection is a point-to-point bi-directional connection between a UE and the radio access network for control-plane signaling and radio resource management.

Introduced
Rel-4
Where
Services
Specifications
2 specs
RRC Connection Description Purpose What changed Neighbours Specifications

Description

The RRC (Radio Resource Control) connection is a fundamental concept in 3GPP radio access networks, representing a logical point-to-point bi-directional connection between the RRC entity in the User Equipment (UE) and the corresponding RRC entity in the radio access network. It is established over the radio interface and serves as the control-plane conduit for all signaling messages related to radio resource management, mobility, and connection control. The RRC connection is defined in TS 21.905 (Vocabulary) and TS 25.401 (UTRAN Overall Description), and its scope has evolved to cover GERAN, UTRAN, E-UTRAN, and NG-RAN.

In terms of architecture, the RRC connection is established when the UE transitions from idle mode to connected mode. The process begins with the UE sending an RRC Connection Request message to the network, followed by an RRC Connection Setup message from the network, and completed by an RRC Connection Setup Complete message from the UE. Once established, the RRC connection provides a reliable signaling link over which the network can configure radio bearers, manage mobility (handovers), control measurement reporting, and deliver paging and system information. The RRC connection is associated with a specific UE context in the network, which includes security parameters, radio bearer configurations, and mobility state.

The RRC connection is a key enabler for the UE's connected mode operation. In connected mode, the UE can transmit and receive user-plane data, perform handovers, and benefit from network-controlled mobility. The RRC connection also supports the establishment, modification, and release of radio bearers, which carry user data. The connection is maintained through periodic signaling and can be released by either the UE or the network. When released, the UE returns to idle mode, freeing network resources.

Over successive releases, the RRC connection concept has been adapted to new radio access technologies. In UTRAN (3G), the RRC connection is managed by the RNC (Radio Network Controller). In E-UTRAN (LTE), the RRC connection is terminated in the eNodeB, and the concept of RRC states (RRC_IDLE, RRC_CONNECTED) was introduced. In NG-RAN (5G NR), the RRC connection is terminated in the gNodeB, and additional states such as RRC_INACTIVE were introduced to support fast connection resumption with reduced signaling. The definition of RRC connection has been updated to reflect the inclusion of GERAN, E-UTRAN, and NG-RAN alongside UTRAN, as seen in Release 19.

The RRC connection is essential for the operation of the radio access network. It provides the control-plane foundation for all radio resource management functions, including connection establishment, radio bearer configuration, mobility management, and security activation. Without an RRC connection, the UE cannot exchange user-plane data or receive network-controlled mobility commands. The RRC connection also enables the network to page the UE, broadcast system information, and manage the UE's measurement and reporting behavior. Its design ensures efficient use of radio resources while providing reliable and secure signaling between the UE and the network.

Purpose & Motivation

The RRC connection exists to provide a reliable, secure, and standardized control-plane connection between the UE and the radio access network. Before its introduction, early cellular systems used less structured control mechanisms that were specific to each technology and lacked a unified framework for radio resource management. The RRC connection was introduced in Release 4 (for UTRAN) to formalize the signaling relationship between the UE and the network, enabling a wide range of control functions such as radio bearer setup, handover, measurement control, and security activation.

The primary problem it solves is the need for a dedicated signaling channel that can be used to manage the radio interface independently of user data. This separation of control and user planes allows the network to configure and reconfigure radio resources dynamically, adapt to changing radio conditions, and enforce operator policies without interrupting ongoing data sessions. It also enables the UE to request services, report measurements, and respond to network commands in a structured manner.

As radio access technologies evolved, the RRC connection concept was extended to support new architectures and capabilities. In LTE, the RRC connection became the foundation for the always-on connectivity model, with states like RRC_IDLE and RRC_CONNECTED. In 5G NR, the RRC_INACTIVE state was added to reduce signaling overhead and latency for UEs that are not actively transmitting data but need to remain reachable. The definition of RRC connection was updated to include GERAN, E-UTRAN, and NG-RAN, reflecting the multi-RAT nature of modern networks. This evolution ensures that the RRC connection remains a versatile and essential tool for radio resource management across all 3GPP access technologies.

What changed in its specifications

The latest release-to-release comparison of specifications that define RRC Connection. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

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 →
TS 25.401Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.401: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.401 →

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.

Rel-4 Initial

Initial definition: 'A point-to-point bi-directional connection between RRC peer entities on the UE and the UTRAN sides, respectively. An UE has either zero or one RRC connection.' Introduced for UTRAN (3G) to formalize control-plane signaling.

Definition unchanged from Rel-4.

Definition unchanged from Rel-4.

Definition unchanged from Rel-4.

Definition unchanged from Rel-4, though E-UTRAN (LTE) was introduced in this release with its own RRC connection procedures.

Definition unchanged from Rel-4.

Definition text carried over with minor formatting differences; no functional change.

Definition unchanged from Rel-4.

Definition unchanged from Rel-4.

Definition unchanged from Rel-4.

Definition text carried over with minor formatting differences; no functional change.

Definition text carried over with minor formatting differences; no functional change.

Definition unchanged from Rel-4.

Definition text carried over with minor formatting differences; no functional change.

Definition unchanged from Rel-4.

Wording changed to include GERAN, E-UTRAN, and NG-RAN: 'A point-to-point bi-directional connection between RRC peer entities on the UE and the GERAN/UTRAN/E-UTRAN/NG-RAN sides, respectively. An UE has either zero or one RRC connection.' This reflects the multi-RAT scope of modern 3GPP networks.

Defining Specifications

3GPP specifications that define or reference RRC Connection, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read