SRB

Signalling Radio Bearer

Protocol →
Introduced in Rel-5

SRB is a dedicated logical channel that carries control plane signalling messages between the UE and the network to ensure reliable delivery for connection establishment, mobility, and configuration.

Category
Protocol
Introduced
Rel-5
Where
Radio Access Network › NG-RAN (5G)
Specifications
14 specs
SRB Description Purpose Related Classification Detected Changes Specifications

Description

A Signalling Radio Bearer (SRB) is a fundamental concept in 3GPP cellular networks, referring to a logical channel specifically allocated for transporting control plane signalling messages between the User Equipment (UE) and the Radio Access Network (RAN). Unlike data radio bearers (DRBs) that carry user plane data, SRBs are exclusively used for signalling, which includes messages for radio resource control (RRC), non-access stratum (NAS), and other control protocols. SRBs are established and managed by the RRC protocol to ensure reliable and prioritized delivery of critical signalling information. They operate over the air interface (e.g., Uu in LTE/5G) and are mapped to specific transport channels and physical resources by the lower layers (MAC and PHY).

Architecturally, SRBs are defined as part of the radio interface protocol stack, with different SRB types serving distinct purposes. For example, SRB0 is used for initial RRC connection setup via common control channels, while SRB1 is dedicated to RRC messages and may also carry NAS messages before other SRBs are established. SRBs are characterized by their configuration parameters, such as RLC mode (typically acknowledged mode for reliability), logical channel identity, and prioritization settings. The network configures SRBs during states like RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED to facilitate signalling exchanges for functions like handover, bearer setup, and security activation.

How SRBs work involves the RRC layer in the UE and gNB (or eNB) establishing these bearers when needed. Signalling messages are encapsulated into RRC Protocol Data Units (PDUs) and transmitted over the assigned SRB. The RLC layer ensures reliable delivery through retransmissions if in acknowledged mode, while MAC handles scheduling and multiplexing with other logical channels. SRBs are crucial for network operations because they carry essential information for mobility management (e.g., handover commands), session management (e.g., PDN connectivity requests), and security procedures (e.g, authentication and key derivation). Their reliable operation is vital for maintaining network connectivity and service continuity.

Purpose & Motivation

SRBs exist to provide a dedicated and reliable channel for control plane signalling, separating critical network control messages from user data traffic. In early cellular systems, signalling and data often shared resources, leading to potential congestion and delays in essential control functions. The standardization of SRBs in 3GPP, starting from UMTS and evolving through LTE and 5G, addresses this by ensuring signalling has guaranteed resources and prioritization. This solves problems like slow connection setup, unreliable handovers, and inefficient resource management, which are critical for network stability and user experience.

Historically, SRBs were introduced to support the increasing complexity of mobile networks, which require extensive signalling for features like packet-switched services, quality of service (QoS) management, and advanced mobility. In Release 5 with HSDPA, SRBs became even more important for handling high-speed data session control. Over releases, SRBs have evolved to support new functionalities, such as carrier aggregation, dual connectivity, and network slicing, by carrying corresponding RRC configurations. Their purpose is to enable robust and efficient control plane communication, which is the backbone of cellular network operation, ensuring that UEs can reliably attach, move, and communicate within the network.

Classification

Part ofRRC
Related approachesDRB

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (10 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 5 changes

In Release 15, new capabilities for SRB duplication were introduced, including its configuration for carrier aggregation and its addition in the Secondary Cell Group. The release also specified procedures for PDCP re-establishment during SRB modification for E-UTRA connected to 5G Core and included corrections for the configuration of the split SRB.

  • CR on 36.300 for SRB cell mapping for CA duplication TS 36.300CR1235
  • Addition of SRB duplication in SCG TS 36.331CR3813
  • CR to 38331 on ul-DataSplitThreshold for SRB TS 38.331CR0248
  • PDCP re-establishment during SRB modification for EUTRA/5GC TS 38.331CR0938
  • Correction on the configuration of split SRB TS 38.331CR1375
Rel-16 3 changes

In Release 16, the SRB function was updated with corrections and clarifications for specific procedures. This included a correction for SRB handling during a Dual Active Protocol Stack Handover Failure and a correction on SRB duplication. Furthermore, the release provided clarification on SRB configuration for the fullConfig parameter during the RRC Resume procedure.

  • Correction for SRB handling of DAPS HOF (36.331) TS 36.331CR4411
  • Correction on SRB duplication TS 36.323CR0281
  • Clarification on the SRB configuration for fullConfig during RRC Resume procedure TS 38.331CR1986
Rel-17 1 change

In Release 17, the standardization work included a clarification on SRB duplication. This update specifically addressed the technical specification for the E1 application protocol (TS38.470) to provide clearer implementation guidance for Signalling Radio Bearer duplication procedures.

  • Clarification on SRB duplication for TS38.470 (R17) TS 38.470CR0092
Rel-18 1 change

In Release 18, the signalling radio bearer (SRB) function was enhanced by improving the handling of the default SRB configuration during LTM (Limited Service Mode) execution. This provides more robust and defined SRB behavior for devices operating in this mode. The update specifically addresses the procedural steps for configuring the default SRB when LTM is initiated.

  • Handling of the default SRB configuration upon LTM execution TS 38.331CR5285

Explore further

Broader topics and technologies where SRB plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 25.214 vj00 UTRA FDD Physical Layer Procedures Rel-19
TR 25.993 vj00 UTRA RAB Examples and Radio Interface Mapping Rel-19
TS 33.401 vj10 EPS Security Architecture Rel-19
TS 36.300 vj00 E-UTRAN Radio Interface Protocol Architecture Overview Rel-19
TS 36.314 vj00 E-UTRA Radio Measurements Specification Rel-19
TS 36.323 vj00 PDCP Protocol Specification Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 37.320 vj00 Minimization of Drive Tests (MDT) Overview Rel-19
TS 37.470 vj00 W1 Interface Introduction for ng-eNB Rel-19
TS 38.323 vj00 Packet Data Convergence Protocol (PDCP) Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.470 vj10 F1 Interface Introduction Rel-19
TS 44.160 vg00 GERAN Iu Mode RLC/MAC Protocol Specification Rel-16
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.