EPS Bearer Identity

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.

Key Features

• Unique numerical identifier for an EPS bearer within a UE's PDN connection context
• Globally significant across UE, eNodeB, MME, S-GW, and P-GW interfaces
• Used in all bearer-related signaling procedures (activation, modification, deactivation)
• Assigned by the MME, often based on a request from the P-GW (PCRF)
• Essential for mapping between QoS profiles, TFTs, and the actual bearer resources
• Critical for interworking between 4G EPS and 5G Core network architectures

Evolution Across Releases

Defining Specifications