Description
The default bearer is an EPS bearer that gets established with every new PDN connection. Its context remains established throughout the lifetime of that PDN connection, and it is always a non-GBR (non-Guaranteed Bit Rate) bearer. It provides the UE with always-on IP connectivity to the PDN and serves as the anchor bearer for that PDN connection. Any traffic not matching the packet filters of a dedicated bearer is carried on the default bearer, making it the fundamental connectivity vehicle in the EPS architecture defined by 3GPP TS 23.401.
When a UE attaches to the LTE network or initiates a new PDN connection, the MME selects a P-GW and S-GW and triggers the creation of a default bearer. This involves establishing a radio bearer over the LTE-Uu interface, an S1-U bearer between the eNodeB and S-GW, and an S5/S8 bearer between the S-GW and P-GW. The default bearer is assigned a QCI (typically QCI 9 for best-effort or QCI 8/9 depending on operator policy), an ARP, and a set of QoS parameters. Because it is a non-GBR bearer, it does not reserve bandwidth; instead, it provides best-effort or differentiated best-effort treatment based on the QCI.
The default bearer is established using NAS signaling procedures defined in 3GPP TS 24.301. During the initial Attach procedure, the UE includes a PDN Connectivity Request, and the network responds with an Activate Default EPS Bearer Context Request that contains the EPS bearer identity, the QCI, the APN, the PDN address, and other parameters. The UE then completes the establishment by sending an Activate Default EPS Bearer Context Accept. For additional PDN connections, the UE initiates a separate PDN Connectivity Request procedure, each resulting in a new default bearer with its own IP address and APN.
Each PDN connection has exactly one default bearer, and the default bearer cannot be deleted without deleting the entire PDN connection. Dedicated bearers, by contrast, can be added and removed dynamically within the same PDN connection. The default bearer's EPS bearer identity is used as the reference for the PDN connection, and its TFT is typically empty or contains only a match-all filter, meaning it carries all traffic not explicitly matched by a dedicated bearer's TFT.
The default bearer plays a critical role in mobility and session management. During handovers, the default bearer is always maintained to preserve IP connectivity, while dedicated bearers may be subject to admission control and could be dropped if resources are insufficient in the target cell. The default bearer also carries the signaling traffic for the UE's NAS layer and is used for EPS session management procedures. In 5G, the equivalent concept is the default QoS flow within a PDU session, which similarly provides always-on connectivity and is established when the PDU session is created.
Purpose & Motivation
The default bearer was introduced in Release 8 as part of the EPS architecture to provide always-on IP connectivity to UEs. In earlier GPRS and UMTS networks, PDP contexts had to be explicitly activated for each service, and there was no concept of an always-on connection that persisted for the lifetime of a PDN session. The default bearer solves this by ensuring that whenever a UE connects to a PDN, a bearer is automatically established and maintained, giving the UE continuous IP connectivity without requiring repeated activation procedures.
This design supports the smartphone era's requirement for always-on applications such as push email, instant messaging, and background synchronization. It also simplifies session management by providing a stable anchor for the PDN connection, to which dedicated bearers can be added for specific QoS needs. The default bearer's non-GBR nature ensures that it can always be established without requiring bandwidth reservation, making it universally available even in congested conditions.
By separating the always-on default bearer from service-specific dedicated bearers, the EPS architecture achieves both ubiquitous connectivity and service differentiation. The default bearer guarantees that the UE can always reach the network and that basic IP services work, while dedicated bearers provide enhanced treatment for applications that need it. This model has been carried forward into 5G as the default QoS flow, demonstrating its enduring value.
What changed in its specifications
The latest release-to-release comparison of specifications that define Default Bearer. Each summary describes the whole specification, not only this term.
Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Rel-19 adds store-and-forward satellite operation for NTN, control plane CIoT data overhead reduction via EMM TRANSPORT and Data container IE, and RAT utilization control. It also adds disaster roaming indications and MINT-EPS support, plus MPS priority for messaging paging.
Full comparison in TS 24.301 →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
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 6 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.
TS 23.401 first defines the Default Bearer as the EPS bearer first established for a new PDN connection and kept for the connection's lifetime, and uses it in attach and PDN connectivity procedures.
- “The EPS bearer which is first established for a new PDN connection and remains established throughout the lifetime of the PDN connection.” TS 23.401 v8.18.0
- “If the UE provides an APN, this APN shall be employed for default bearer activation.” TS 23.401 v8.18.0
Default bearer creation signalling in TS 23.401 was extended: Create Session Request/Response carrying Default EPS Bearer QoS now includes UE Time Zone and User CSG Information, and emergency APN checks were added for Create Default Bearer Request.
- “P-GWs shall not perform any checks of Maximum APN Restriction if Create Default Bearer Request includes emergency APN.” TS 23.401 v9.16.0
- “The IMSI, APN, UE IP address, User Location Information (ECGI), UE Time Zone, Serving Network, RAT type, APN-AMBR, Default EPS Bearer QoS are provided to the PCRF” TS 23.401 v9.16.0
Default bearer establishment signalling changed: the PDN GW now passes ETFTU (extended TFT filter format support) to the PCRF with the Default EPS Bearer QoS, and emergency APN handling in Create Default Bearer Request was specified.
- “PDN GWs shall not perform any checks of Maximum APN Restriction if Create Default Bearer Request includes the emergency APN.” TS 23.401 v11.11.0
- “ETFTU (if ETFTU is not provided it means UE and/or the PDN GW does not support the extended TFT filter format)” TS 23.401 v11.11.0
For non-IP PDN type with Control plane CIoT EPS optimisations, if subscription indicates SCEF, the MME allocates a Default Bearer EPS Bearer Identity and connects to the SCEF instead of selecting a Serving GW and PDN GW.
- “if APN subscription data indicate a SCEF connection needs to be used, then the MME allocates an EPS Bearer Identity for the Default Bearer” TS 23.401 v13.14.0
- “If the subscription context does not indicate that the APN is for a PDN connection to an SCEF, the new MME selects a Serving GW” TS 23.401 v13.14.0
TS 36.508 corrected the default message contents of the Activate Default EPS Bearer Context Request message, including its Transaction Identifier settings.
- Correction to Activate Default EPS Bearer Context Request message TS 36.508CR1486
- “Correction of the default message contents of Transaction Identifiers in Activate Default EPS Bearer Context and Activate Dedicated EPS Bearer Context messages” TS 36.508 v18.11.0
36.508 test specification corrected the default message contents for Activate Default EPS Bearer Context Request and its transaction identifiers, and added a note on releasing a PDN via its Default EPS Bearer identity.
- “Correction to Activate Default EPS Bearer Context Request message” TS 36.508 v19.3.1
- “Correction of the default message contents of Transaction Identifiers in Activate Default EPS Bearer Context and Activate Dedicated EPS Bearer Context messages” TS 36.508 v19.3.1
Defining Specifications
3GPP specifications that define or reference Default Bearer, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 24.301 vk10 | EPS NAS Mobility and Session Management | Rel-20 read |
| TS 24.801 v810 | CT1 SAE NAS Aspects for EPC | Rel-8 read |
| TS 29.804 v801 | CT3 Aspects of System Architecture Evolution | Rel-8 read |