DEI

Drop Eligible Indicator

QoS →
Introduced in Rel-15

DEI is a 1-bit header field that marks a packet as eligible for dropping during network congestion to preserve quality of service for higher-priority traffic.

Category
QoS
Introduced
Rel-15
Where
Core Network › 5G Core
Specifications
4 specs
DEI Description Purpose Related Classification Detected Changes Specifications

Description

The Drop Eligible Indicator (DEI) is a fundamental Quality of Service (QoS) mechanism defined in 3GPP specifications that operates at the packet level to manage network congestion. It is a single-bit field embedded within various protocol headers, including Ethernet frames (as part of the VLAN tag's Priority Code Point field) and potentially within GTP-U or other transport protocol extensions used in 5G transport networks. When a network node (such as a router, switch, or User Plane Function) experiences congestion, it can examine the DEI bit of queued packets. Packets marked with DEI=1 are considered 'drop eligible' and can be selectively discarded before packets marked with DEI=0, which are treated as higher priority and should be preserved as long as possible. This mechanism is a form of Active Queue Management (AQM).

The operation of DEI is tightly coupled with traffic classification and marking policies. Typically, network functions like the Session Management Function (SMF) or Policy Control Function (PCF) define QoS rules that map specific data flows (identified by 5-tuple, QoS Flow Identifier, or application) to a QoS profile. Part of this profile can include a marking policy that specifies whether packets from that flow should be marked as drop eligible (DEI=1) or not (DEI=0) under certain conditions, such as when the flow exceeds its guaranteed bit rate but remains within its maximum bit rate. The marking is usually performed by the User Plane Function (UPF) for downlink traffic or the User Equipment (UE) for uplink traffic, based on these enforced policies.

Architecturally, DEI functions within a broader QoS framework that includes other markers like the Differentiated Services Code Point (DSCP) for per-hop behavior and the 5G QoS Identifier (5QI) for end-to-end service characteristics. While DSCP/5QI defines the scheduling priority and resource type (e.g., Guaranteed Bit Rate, Delay Critical GBR), DEI provides an additional, orthogonal dimension for congestion management within a given priority class. For example, two flows with the same 5QI (and thus similar latency and priority requirements) can be differentiated during congestion: one might be marked as drop eligible if it is a best-effort component of a service, while the other remains non-drop-eligible if it carries essential control information.

In the 5G system, DEI's role is crucial in the transport network segments (N3, N6, N9 interfaces) that carry user plane traffic. It enables transport nodes to implement simple, efficient congestion actions without needing deep packet inspection or understanding of 3GPP-specific QoS parameters. This decoupling allows for scalable network design where the core network controls the intent (via marking policies), and the underlying IP transport infrastructure executes the congestion response based on the standard DEI bit. The effectiveness of DEI depends on proper configuration of queue management algorithms (like Weighted Random Early Detection - WRED) on network equipment to utilize the DEI bit for drop decisions.

Purpose & Motivation

DEI exists to provide a scalable and standardized method for managing network congestion in packet-switched networks, particularly within the transport segments of 3GPP systems. Prior to such explicit marking schemes, networks often relied on tail-drop during congestion, where packets are discarded indiscriminately once a queue fills, leading to global synchronization problems, high latency, and poor fairness between traffic flows. DEI, as part of a broader Differentiated Services (DiffServ) architecture, allows for more intelligent congestion management by enabling selective packet discarding based on operator policy.

The primary problem DEI solves is the efficient utilization of network resources during periods of overload while protecting the performance of mission-critical or revenue-generating traffic. In mobile networks, where bandwidth can be variable and expensive, it is essential to ensure that high-priority services like voice calls, emergency communications, or low-latency industrial IoT commands are not impacted by congestion caused by less critical traffic like background file downloads or software updates. DEI provides a simple binary signal that transport equipment can use to make immediate drop decisions without complex processing, aligning with the need for high-speed forwarding in core networks.

Historically, as 3GPP networks evolved from circuit-switched to all-IP architectures (starting with 4G EPS and fully realized in 5GS), the need for IP-compatible QoS mechanisms became paramount. DEI, borrowed and adapted from IEEE Ethernet and IETF DiffServ standards, was integrated into 3GPP's QoS framework to bridge the gap between the radio-aware QoS parameters (like 5QI) and the QoS capabilities of the underlying transport infrastructure. It addresses the limitation of having rich QoS classification within the 3GPP core but no efficient way to convey drop precedence information to the transport network, which is often comprised of multi-vendor IP routers and switches that operate on standard IP/Ethernet headers.

Classification

Part of5QI
Related approachesUPF

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 6 changes

In Release 15, the DEI (Drop Eligible Indicator) function was not explicitly mentioned in the provided grounding context or change request titles. The new indicators introduced in this release, as detailed in the context, include the MPS (Access Identity 1) and MCS (Access Identity 2) indicators for priority services, an Emergency Services Support indicator for non-3GPP access, and a VoPS (Voice over PS) indicator, alongside mechanisms for dynamically updating the routing indicator stored on the USIM and ME.

  • Dynamic Routing indicator update description TS 24.501CR0395
  • MCS Indicator and Access Identity 2 TS 24.501CR0614
  • Emergency Services Support indicator for non-3GPP access TS 24.501CR0106
  • Storing of MPS indicator in non-volatile memory of mobile TS 24.501CR0123
  • Clarification to VoPS indicator TS 24.501CR0121
  • Encoding of Routing indicator set to default value 0 TS 24.501CR0876
Rel-16 11 changes

In Release 16, the DEI function was not a primary focus of the specified enhancements. The provided Change Requests and grounding context detail updates to other indicators and procedures, such as the re-attempt indicator, follow-on request indicator, routing indicator, and the "NSSAA to be performed" indicator, across various scenarios including initial registration, mobility updates, and operation within an SNPN. The technical refinements primarily addressed clarifications, corrections, and the extension of these specific indicator functionalities, rather than introducing new DEI-related capabilities.

  • Service gap control, follow-on request indicator at mobility update registration TS 24.501CR1387
  • Clarifications to the Routing indicator encoding TS 24.501CR1043
  • Clarification of 5GSM cause values for which network may include a back-off timer or a re-attempt indicator TS 24.501CR1053
  • Correction on follow-on request indicator TS 24.501CR1204
  • Local release when receiving REFRESH command for routing indicator in RRC inactive TS 24.501CR1342
  • Correction to re-attempt indicator IE description TS 24.501CR1570

+ 5 more changes

Rel-17 15 changes

In Release 17, the enhancements for the Drop Eligible Indicator (DEI) function are not explicitly detailed in the provided grounding context. The listed Change Requests primarily focus on other indicators and parameters, such as the Follow-on request indicator, Steering Mode Indicator, and various routing and priority indicators. Therefore, based on the given materials, no specific new feature or change for the DEI function in Release 17 can be described.

  • Condition of Inclusion of Threshold Values IE and Steering Mode Indicator IE TS 29.244CR0581
  • Definition of Routing Indicator TS 24.501CR2456
  • Set the Follow-on request indicator to "Follow-on request pending" TS 24.501CR2832
  • "ME support of SOR-CMCI" indicator TS 24.501CR3131
  • Correction on handling of the IMS VoPS over non-3GPP access indicator TS 24.501CR3480
  • The handling of paging cause support indicator in 5GS TS 24.501CR3912

+ 9 more changes

Rel-18 8 changes

In Release 18, the DEI (Drop Eligible Indicator) function itself is not explicitly mentioned in the provided materials. The new developments focus on enhancing priority service indicators, specifically extending the mechanisms for updating the MPS (Access Identity 1) and MCS (Access Identity 2) indicators. A key addition is the capability to update these indicators via the CONFIGURATION UPDATE COMMAND message over both 3GPP and non-3GPP accesses when registered to the same PLMN or SNPN.

  • Equivalent SNPNs: MPS and MCS indicators TS 24.501CR4985
  • MPS and MCS indicators for 3GPP and non-3GPP accesses TS 24.501CR4480
  • Extending Re-attempt indicator IE & 5GSM congestion re-attempt indicator IE for equivalent SNPN TS 24.501CR5113
  • Ignore 5GSM congestion re-attempt indicator IE if receiving #39 TS 24.501CR5671
  • Updating MCS indicator via configuration update command procedure TS 24.501CR5949
  • SOR-SNPN-SI and SOR-SNPN-SI-SL indicators set in UL NAS transport TS 24.501CR6153

+ 2 more changes

Rel-19 1 change

In Release 19, the DEI function was updated through corrections to the standardized mapping values for specific Ethernet frame types. The changes specifically corrected the reference values for the "extended 802.1Q C-TAG PCP/DEI type", the "802.1Q S-TAG PCP/DEI type", and the "extended 802.1Q S-TAG PCP/DEI type" within the relevant specification table.

  • In table 9.11.4.13.1 corrected values for the "extended 802.1Q C-TAG PCP/DEI type", "802.1Q S-TAG PCP/DEI type" and "extended 802.1Q S-TAG PCP/DEI type" by MCC. TS 24.501

Explore further

Broader topics and technologies where DEI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 29.244 vj40 PFCP Specification for Control/User Plane Separation Rel-19
TS 29.514 vj40 5G System; Policy Authorization Service; Stage 3 Rel-19
TS 29.890 vg00 CT3 5G System Technical Report Rel-16