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

Glossary term · Identifier

EBI

EPS Bearer Identity

Identifier →

EBI is a unique numerical identifier assigned to each EPS bearer in LTE and 5G networks, used by network nodes to manage, differentiate, and ensure proper QoS handling for a UE's traffic flows.

Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
3 specs
EBI Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The EPS Bearer Identity (EBI) is a fundamental identifier within the Evolved Packet System (EPS) architecture, central to bearer management in LTE and continued into 5GS. It is a unique integer value, typically ranging from 5 to 15, assigned by the MME during the establishment of a dedicated bearer or as part of the default bearer setup. The EBI is not just a local tag; it is a globally significant identifier within a UE's PDN connection context, used across multiple network interfaces including the S1-MME, S11, and S5/S8. Its primary role is to provide an unambiguous reference for network entities—such as the MME, Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), and the UE itself—to identify a specific bearer and its associated QoS profile, traffic flow templates (TFTs), and charging rules.

From an operational perspective, the EBI is carried within key signaling messages. For instance, during a dedicated bearer activation, the P-GW initiates the procedure and includes the proposed EBI in the Create Bearer Request sent to the S-GW and MME. The MME then forwards this to the eNodeB and UE. All subsequent modifications, such as bearer resource modification or deactivation, reference the specific bearer using this EBI. This ensures that commands like updating a QoS parameter or tearing down a specific data flow are executed on the correct logical path. The EBI is also tightly coupled with the EPS bearer context stored in the UE and the network nodes, linking the radio bearer (DRB), S1 bearer, and S5/S8 bearer into a cohesive end-to-end pipe.

In the 5G Core (5GC) architecture, the concept evolves with the QoS Flow, but the EBI remains crucial for interworking scenarios and for UEs connected via E-UTRAN to the 5GC (non-standalone or EPS fallback). The 5GC maps 5G QoS Flows to EPS bearers when interfacing with LTE RAN or EPC, and the EBI is used to identify these mapped bearers. Therefore, understanding EBI is essential for managing mobility and session continuity between 4G and 5G networks, as it serves as a common reference point for bearer-level operations across different generations of core networks.

Purpose & Motivation

The EBI was introduced to solve the critical need for unambiguous bearer identification and management in the all-IP EPS architecture of LTE. Prior 3GPP systems like UMTS used RAB (Radio Access Bearer) IDs, but the flatter, more simplified architecture of EPS required a new, standardized identifier that could be used consistently from the UE through the RAN to the core network gateways. Without a unique identifier like the EBI, network nodes would be unable to coordinate the setup, modification, and teardown of multiple simultaneous bearers for a single UE, leading to potential misrouting of traffic, incorrect QoS application, and charging errors.

The creation of the EBI was motivated by the shift to multiple concurrent dedicated bearers per PDN connection, a feature enabling sophisticated service differentiation (e.g., separate bearers for voice, video, and best-effort data). Each of these bearers requires independent management. The EBI provides the handle for this management, allowing the network to instruct the UE and eNodeB to apply specific packet filters and QoS characteristics to a distinct set of IP flows. It is a cornerstone for enabling the promised QoS capabilities of LTE, such as guaranteed bit rate (GBR) bearers for real-time services.

Historically, its design ensures backward compatibility and forward flexibility. The value range is reserved to avoid conflicts with pre-existing identifiers. Its persistence across the network allows for efficient signaling; instead of sending full bearer contexts in every message, nodes can reference the compact EBI. This reduces signaling overhead and simplifies state management, which is crucial for scaling networks to support millions of devices and their complex service requirements.

What changed in its specifications

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

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 29.274Rel-18 → Rel-19

Rel-19 adds S-NSSAI text to the Create Session Request and Response procedures for edge computing phase 3. It also clarifies eMLPP priority values and GTP priority handling for MPS messaging and emergency traffic.

Full comparison in TS 29.274 →

Technology family

Sessions, bearers and QoS · Core Network

  1. R96 PDP context
  2. R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
  3. Rel-7 IP-CAN bearer, IP-CAN session, QCI
  4. Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
  5. Rel-9 Evolved ARP
  6. Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
  7. 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 sources

Documented 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 introduced

The EPS Bearer ID (EBI) information element is specified for the first time in TS 29.274, with its coding defined in Figure 8.8-1.

Rel-9 1 CR

TS 29.274 in Rel-9 specifies the EBI field's coding and value range by reference to TS 24.007, and a CR changes the NSAPI to EBI in the PFI IE.

  • “The coding of EBI field and its value range is specified in 3GPP TS 24.007 [30], subclause 11.2.3.1.5, bits 5 to 8.” TS 29.274 v9.14.0
  • Change the NSAPI to EBI in the PFI IE TS 29.274CR0455
Rel-10 1 CR

The Downlink Data Notification message in GTPv2-C (TS 29.274) was changed to carry EBI and ARP information elements.

Rel-11 specification text

The SGSN may now provide EBI(s) without S12 RNC F-TEID (or S4-U SGSN F-TEID) in certain Direct Tunnel scenarios, and the SGW must handle such bearer contexts.

  • “the SGSN shall provide EBI(s) without S12 RNC F-TEID(s) for these bearer context(s) without corresponding radio access bearer(s) being established” TS 29.274 v11.14.0
  • “In those scenarios, the SGSN shall provide EBI(s) without S12 RNC F-TEID(s) and S4-U SGSN F-TEID.” TS 29.274 v11.14.0
Rel-12 1 CR

GTPv2-C (TS 29.274) now specifies which EBI value to use in Downlink Data Notification for dedicated bearer activation with ISR active, and requires the MME to give the EBI for all bearers in Modify Bearer Request.

  • “The MME shall provide in the Bearer Contexts to be modified IE, for a UE entering or being in CONNECTED state, the EBI” TS 29.274 v12.15.0
  • EBI value to use in Downlink Data Notification Triggered by a Dedicated Bearer Activation procedure when ISR is active TS 29.274CR1523
Rel-13 3 CRs

In TS 29.274 Rel-13, EBI handling in GTPv2 messages changed: EBI is included in Delete Bearer Request, EBI and ARP in DDN to S4-SGSN, and Modify Access Bearer Request with only EBI is clarified.

  • Inclusion of EBI in Delete Bearer Request message TS 29.274CR1578
  • EBI and ARP in DDN message sent to S4-SGSN TS 29.274CR1605
  • Essential clarification for Modify Access Bearer Request when only EBI is present TS 29.274CR1740
Rel-15 specification text

Rel-15 specifies EBI assignment for 5GS-EPS interworking: AMF allocates, revokes by ARP priority and releases EBIs for PDU sessions, with mapping between EBI and QFI; GTPv2 EBI value range extended.

  • “The AMF uses the ARP list (including ARP priority level, the pre-emption capability and the pre-emption vulnerability) and the S-NSSAI to prioritize the EBI request” TS 23.502 v15.17.0
  • “to request the AMF to allocate EPS bearer ID(s) towards EPS bearer(s) mapped from QoS flow(s) for an existing PDU Session for a given UE” TS 29.518 v15.13.0
  • “it supports to use EPS Bearer ID with a value between '1' and '15'” TS 29.274 v15.9.0
Rel-16 specification text

In Rel-16 EBI handling changed: the AMF determines which EBIs cannot be transferred to EPS, EBI assignment gets new failure causes and handover handling, and EBI/ARP mapping updates are added.

  • “The EBI values(s) that cannot be transferred is determined by the AMF if the target MME does not support 15 EPS bearers” TS 23.502 v16.19.0
  • “EBI_REJECTED_LOCAL_POLICY, if the EBI allocation is rejected due to local policies at the AMF” TS 29.518 v16.19.0
  • “the V-SMF or I-SMF shall request the AMF to update the mapping of EBI and ARP.” TS 29.502 v16.17.0
Rel-17 1 CR

Rel-17 adds an EBI-to-ARP mapping update to the AMF EBIAssignment service operation (EAEA feature), so the SMF can update the mapping when a QoS flow's ARP changes.

  • “to request the AMF to update the mapping of EBI and ARP, if the ARP for a QoS flow that has already been allocated an EBI is changed” TS 29.518 v17.18.0
  • “the AMF shall store the association of the assigned EBI and ARP pair to the corresponding PDU Session ID” TS 29.518 v17.18.0
  • EBI and ARP mapping update TS 29.518CR0424
Rel-18 2 CRs

EBI allocation is now restricted to PDU Sessions using SSC mode 1 and no longer applies to SSC mode 2 or 3, with a corresponding CR in TS 29.518.

  • “EBI allocation shall also not apply to PDU Session using SSC mode 2 or SSC mode 3.” TS 23.502 v18.14.0
  • EBI allocation applying to PDU sessions using SSC mode 1 TS 29.518CR1084
  • Correction on EBI Assignment over N16/N16a TS 29.502CR0626
Rel-19 specification text

EBI handling in EPS interworking and handover changed: the 5GS-to-EPS handover procedure now covers EBI assignment failure, and the PDN connection is no longer released locally in SMF+PGW-C when seamless continuity is unsupported.

  • “or the EBI assignment fails due to an ongoing Xn, N2, or 5GS to EPS handover procedure.” TS 29.518 v19.8.0
  • “within the N2 SM Information and release the PDN connection locally in the SMF+PGW-C.” TS 23.502 v19.9.0
  • “This IE shall be present and set to "true" during a 5GS to EPS Idle mode mobility or handover” TS 29.502 v19.8.0
Rel-20 specification text

The AMF should indicate EBI assignment failure for NSSAA-subject S-NSSAIs unless the UE and the SMF+PGW-C both support NSSAA over EPC (Annex L).

  • “unless the UE has indicated that it supports NSSAA over EPC as defined in Annex L and the SMF+PGW-C also supports NSSAA over EPC” TS 23.502 v20.3.0

Defining Specifications

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

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 29.274 vk00 GTPv2-C Control Plane Protocol Rel-20 read
TS 29.518 vk10 AMF Service Based Interface Rel-20 read