Description
In 3GPP networks, a bearer is a logical channel that provides the capability for information transfer between network elements, such as between a user equipment (UE) and the core network. It is characterized by a set of parameters that define its quality of service (QoS), including capacity, delay, bit error rate, and traffic class. Bearers are essential for establishing, modifying, and releasing data connections in response to service requests, and they form the basis for QoS management in both circuit-switched and packet-switched domains.
The concept of a bearer was first introduced in Release 99 (R99) as part of the Universal Mobile Telecommunications System (UMTS) specifications. In UMTS, bearers are classified into two main categories: real-time (RT) and non-real-time (NRT). RT bearers are designed for services that require strict delay guarantees, such as voice and video calls, while NRT bearers support applications that are more tolerant to delay, such as web browsing and file downloads. Each bearer class is associated with a set of QoS parameters, such as guaranteed bit rate (GBR), maximum bit rate (MBR), and allocation and retention priority (ARP), which are used by the network to allocate resources and enforce policies.
With the evolution to Long Term Evolution (LTE) and the System Architecture Evolution (SAE), the bearer concept was refined to support an all-IP network. In LTE, bearers are established between the UE and the Packet Data Network Gateway (P-GW) and are known as EPS bearers. An EPS bearer is composed of a radio bearer between the UE and the eNodeB, an S1 bearer between the eNodeB and the Serving Gateway (S-GW), and an S5/S8 bearer between the S-GW and the P-GW. This hierarchical structure allows for flexible QoS management across different network segments. The concept of a default bearer and dedicated bearers was introduced, where the default bearer provides basic connectivity and dedicated bearers are used for specific services with distinct QoS requirements.
In 5G, the bearer concept has evolved further with the introduction of QoS flows. A QoS flow is the finest granularity of QoS treatment in the 5G System (5GS), and it is mapped to data radio bearers (DRBs) over the air interface. Unlike EPS bearers, which are established per UE, QoS flows are established per PDU session and can be dynamically added or modified to meet changing service requirements. The 5G QoS model supports both GBR and non-GBR flows, as well as reflective QoS, which allows the UE to derive QoS rules from downlink packets. This evolution reflects the need for more granular and dynamic QoS management in 5G to support diverse use cases like URLLC and mMTC.
Despite the evolution, the fundamental purpose of a bearer remains the same: to provide a defined quality of service for information transfer. Bearers are used for both user plane data and control plane signaling, and they are managed by the core network's policy and charging control (PCC) framework. The establishment, modification, and release of bearers are triggered by events such as session initiation, handover, or changes in network conditions, and they are governed by QoS rules and policies configured by the operator. Understanding bearers is essential for anyone working with mobile networks, as they are the building blocks for delivering services with guaranteed performance.
Purpose & Motivation
The bearer concept exists to provide a standardized mechanism for establishing and managing information transmission paths with specific quality of service characteristics in mobile networks. It solves the problem of how to differentiate and prioritize different types of traffic, ensuring that real-time services like voice receive the necessary resources while non-real-time services can tolerate lower quality. Before bearers, networks lacked a unified way to define and enforce QoS, leading to inconsistent user experiences and inefficient resource utilization.
The motivation for creating bearers in R99 was to support the diverse QoS requirements of UMTS services, which ranged from circuit-switched voice to packet-switched data. By defining bearers with parameters like bit rate, delay, and error rate, operators could offer service level agreements (SLAs) and manage network resources effectively. In LTE, the bearer concept was adapted to an all-IP architecture, introducing EPS bearers and the concept of default and dedicated bearers to simplify connectivity and enable differentiated services. This allowed for more scalable and flexible QoS management, which was crucial for the success of mobile broadband.
In 5G, the bearer concept evolved into QoS flows to meet the demands of new use cases that require ultra-low latency, high reliability, and massive connectivity. QoS flows provide finer granularity and dynamic control, enabling the network to adapt to changing conditions and service requirements in real-time. This evolution ensures that the bearer concept remains relevant and capable of supporting the advanced services envisioned for 5G and beyond.
What changed in its specifications
The latest release-to-release comparison of specifications that define Bearer. 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 →Rel-17 added support for Multi-USIM devices, emergency call handling, and definitions for MUSIM UEs.
Full comparison in TS 22.101 →Technology family
Sessions, bearers and QoS · Core Network
- R96 PDP context
- R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
- Rel-7 IP-CAN bearer, IP-CAN session, QCI
- Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
- Rel-9 Evolved ARP
- Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
- Rel-16 MA PDU Session
- Bearer counterpart in another generation: PDP context
“The SGSN sets the EPS Bearer Identity to an equivalent value as the NSAPI for the Bearer associated with the MS.” TS 23.060
- Bearer counterpart in another generation: QoS Flow
“If QoS Flow is mapped to one EPS bearer, ARP, GBR and MBR of the EPS Bearer is set to the ARP, GFBR and MFBR of the corresponding QoS Flow, respectively.” TS 23.502
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 12 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Rel-8 first specifies bearer handling in the EPS GTPv2-C protocol, with Create/Modify/Update/Delete Bearer messages and piggybacking, and defines dedicated and default EPS bearers in the stage-2 text.
- “The Create Bearer Request message shall be sent on the S5/S8 interface by the PGW to the SGW” TS 29.274 v8.12.0
- “The always-on IP connectivity for UE/users of the EPS is enabled by establishing a default EPS bearer during Network Attachment.” TS 23.401 v8.18.0
- “The MSC server shall use the Modify Bearer Characteristics procedure for A interface TDM termination” TS 23.205 v8.10.0
Bearer handling changed in Rel-9: Bearer QoS added to Modify Bearer Request, Release Access Bearer Request introduced, and bearer context content in Create Session messages and bearer resume behaviour revised.
- “the SGW/PGW clears suspended status for all the non-GBR bearers. The PGW shall forward packets it receives for the UE.” TS 29.274 v9.14.0
- Bearer QoS in Modify Bearer Request TS 29.274CR0359
- HSS/PGW initiated Bearer QoS Modification procedure TS 29.274CR0516
Bearer-related GTPv2 and EPS procedures were changed: ISR deactivation via Delete Bearer Request, Bearer Context handling per SGW change, and a TFT now allowed on the default EPS bearer.
- “Every dedicated EPS bearer is associated with a TFT. A TFT may be also assigned to the default EPS bearer.” TS 23.401 v10.13.0
- “Delete Bearer Request during a TAU/RAU/Handover procedure if ISR is being deactivated.” TS 29.274 v10.15.0
- Unsupported Bearer Handling for LIPA TS 29.274CR0887
Bearer handling changed: ISR deactivation now triggers Delete Bearer Request with Cause "ISR deactivation", and bearer procedures are temporarily rejected during handover/TAU/RAU in progress.
- “the SGW shall delete the bearer resources by sending Delete Bearer Request to the MME/SGSN on which ISR was activated with the same Cause value "ISR deactivation"” TS 29.274 v11.14.0
- “is used by the MME/S4-SGSN for the bearer related procedure initiated by the PGW.” TS 29.274 v11.14.0
- Delete Bearer Request with ISR deactivation TS 29.274CR1291
Bearer-related GTPv2 and EPS procedures were changed in Rel-12: Presence Reporting Area information was added to Modify Bearer and Create Bearer messages, and bearer context handling and bearer removal notification were corrected.
- “If the MME has been requested to report a change of UE presence in Presence Reporting Area, the MME includes in this message the Presence Reporting Area Information” TS 23.401 v12.11.0
- Bearer Context to be modified in Modify Bearer Request TS 29.274CR1329
- HPLMN Notification with specific indication due to MME initiated Bearer removal TS 23.401CR2622
Bearer signalling and handling were changed in Rel-13: Create Bearer, Modify Bearer and Delete Bearer messages gained new contents and conditions, including piggybacking with handover from non-3GPP access and RAN/NAS cause in Delete Bearer Response.
- “a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN” TS 29.274 v13.13.0
- Inclusion of RAN/NAS Cause in Delete Bearer Response TS 23.401CR2928
- Bearer mismatching handling TS 29.274CR1710
Bearer-related procedures and signalling were corrected in Rel-14, including Bearer Contexts in Delete Bearer Failure Indication, IP address instance in Create Bearer Response, and bearer synchronization for UP CIoT EPS optimisation.
Bearer-related procedures and signalling were changed in Rel-15, e.g. Modify Bearer Request handling, Extended EPS Bearer Identity and INOBEAR support in GTP-C, and Bearer Context procedures in E1AP.
- “the old MME/SGSN shall only include the Bearer Contexts to be modified IE.” TS 29.274 v15.9.0
- Extended EPS Bearer Identity for INOBEAR TS 29.274CR1900
- Correction to the Modify Bearer Request TS 29.274CR1939
Bearer handling was extended in Rel-16, including support for dedicated bearers of Ethernet type in EPC and RAN interfaces, and a new MME function to control the Emergency Call Bearer Support Indicator.
Bearer handling in EPC signalling changed: PGW Change Info is added to Create/Update/Delete Bearer Request, and Bearer Level QoS is used when restoring PDN connections after a PGW-C/SMF change.
- “Table 7.2.3-5: PGW Change Info within Create Bearer Request” TS 29.274 v17.12.0
- “this IE shall be set to the Bearer Level QoS that was set by the PGW-C/SMF before the restoration of the PDN connection.” TS 29.274 v17.12.0
- Correction on Bearer Context Status Change TS 37.483CR0096
Bearer-related procedures and signalling were corrected, e.g. the gNB-CU-UP must now allocate new shared NG-U resources on a BC Bearer Context modification request and the Bearer Context NG-U TNL information for MBS sessions was fixed.
- “the gNB-CU-UP, shall, if supported, consider the shared NG-U resources for the indicated broadcast MBS session being released, and allocate new shared NG-U resources accordingly” TS 37.483 v18.6.0
- Correction on Bearer Context NG-U TNL Information for an MBS Session TS 37.483CR0160
- PGW-C TEID in Update Bearer Response during PGW triggered PDN connection restoration TS 23.007CR0386
Bearer-related procedures changed: the gNB-CU-UP now returns shared NG-U resource info on a new MC Bearer Context NG-U TNL Info Replace Request, and Bearer Context Setup/Modification interaction with data collection reporting was corrected.
- “the gNB-CU-UP shall, if supported, consider the shared NG-U resources for the indicated multicast MBS session being released, and allocate new shared NG-U resources accordingly” TS 37.483 v19.4.0
- Correction for Data Collection Reporting Initiation and Data Collection Reporting procedures' interaction with Bearer Context Setup and Bearer Context Modification procedures TS 37.483CR0202
Defining Specifications
3GPP specifications that define or reference Bearer, 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 |
| TS 22.101 vl00 | 3GPP Service Principles for PLMNs | Rel-21 read |
| TS 23.050 | 3GPP TS 23.050 | Rel-8 read |