Description
The Energy Detection Threshold (EDT) is a configurable power level, measured in dBm, that serves as the decision point for a wireless device's clear channel assessment (CCA) procedure. When a device needs to transmit, it first listens to the intended channel for a specified duration. During this listening period, it measures the total received power in the channel. The core operation is a simple comparison: if the measured energy is above the EDT, the device declares the channel 'busy' and defers its transmission. If the energy is below the EDT, the channel is declared 'idle,' and the device may proceed to transmit, subject to other rules.
Architecturally, EDT functionality is implemented in the physical layer (Layer 1) of the device's radio modem. Key components include the radio frequency (RF) front-end, which receives the signal, and baseband processing circuitry that performs the energy measurement and comparison against the stored threshold value. The specific EDT value can be fixed by regulation (e.g., by the FCC or ETSI for unlicensed bands), dynamically adjusted by the network, or set by the device's implementation based on sensed conditions. In 3GPP technologies like License Assisted Access (LAA) and NR-U, the gNB (base station) or UE may signal or configure EDT parameters as part of the radio resource control.
How EDT works in practice involves trade-offs. A low EDT makes a device very sensitive, causing it to defer transmission even in the presence of weak interference, which promotes coexistence but may lead to overly conservative underutilization of the spectrum. A high EDT makes the device less sensitive, allowing it to transmit more aggressively, which can increase its own throughput but may cause harmful interference to other nearby networks. Therefore, setting the EDT is a critical aspect of Radio Resource Management (RRM) for unlicensed operations. Its role is to be the foundational gatekeeper for channel access, enabling multiple systems to share the same medium with a degree of fairness and minimizing collisions, which is essential for predictable performance in shared spectrum.
Purpose & Motivation
EDT exists to enable orderly and fair shared access to unlicensed or lightly licensed radio spectrum. Without such a threshold, devices would transmit blindly, leading to constant collisions, degraded performance for all users, and an unusable shared medium—a scenario known as the 'tragedy of the commons.' The problem it solves is fundamental to any distributed wireless system: how to determine, in a decentralized way, when it is acceptable to transmit.
The historical context for its prominence in 3GPP stems from the introduction of LTE in unlicensed spectrum (LAA) in Release 13 and NR-U in Release 16. Prior to this, Wi-Fi was the dominant technology in bands like 5 GHz and used CSMA/CA with its own EDT definitions. 3GPP's foray into unlicensed spectrum necessitated a robust Listen-Before-Talk (LBT) mechanism to meet regulatory requirements (e.g., ETSI EN 301 893) and ensure peaceful coexistence with incumbent systems like Wi-Fi. EDT is the central parameter of this LBT mechanism.
The creation and standardization of EDT parameters within 3GPP were motivated by the need for cellular technologies to operate as good citizens in shared bands. It addresses the limitations of previous cellular systems, which were designed for exclusive, licensed spectrum and did not require such sensing capabilities. By defining EDT, 3GPP allows network-controlled optimization of coexistence behavior, balancing the aggressive efficiency of cellular scheduling with the polite contention-based access needed in shared environments.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (42 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the EDT (Energy Detection Threshold) function was newly introduced for both eMTC and NB-IoT enhancements, as detailed in specifications TS 36.300, TS 36.321, and TS 36.331. This introduction included updates to the LTE suspend/resume procedures to support EDT-capable UEs and defined specific procedures such as EDT-CP where CPSR is provided during RRC connection establishment. The release also encompassed corrections and clarifications for EDT operations, including aspects like the ShortResumeMAC-I calculation and user plane integrity protection.
- LTE - updating suspend/resume procedures to include EDT TS 33.401CR0664
- Introduction of further NB-IoT enhancements other than EDT in TS 36.300 TS 36.300CR1127
- Introduction of EDT for eMTC and NB-IoT enhancements in TS 36.300 TS 36.300CR1128
- Introduction of enhancements for eMTC excluding EDT TS 36.300CR1134
- Introduction of EDT for eMTC and NB-IoT in Rel-15 TS 36.321 TS 36.321CR1249
- Running Rel-15 36.321 CR for eMTC (excluding EDT) TS 36.321CR1273
+ 29 more changes
In Release 16, the EDT function was enhanced with the addition of Mobile-Terminated EDT (MT-EDT) support indication, allowing the network to signal its capability for this feature. Furthermore, the specification provided clarification on the completion procedure for User Plane EDT (UP-EDT) specifically when utilizing RLC Acknowledged Mode (RLC AM). These updates introduced new procedural details and capability signaling to the existing EDT framework.
In Release 17, the EDT function was updated to specifically address reporting for Location Services (LCS) events. The change involved replacing the reporting entity from "NR-RAN" to "ng-eNB" in these specific EDT reports. This modification clarifies the responsible node within the NG-RAN architecture for handling EDT-related LCS event reporting.
- Replacing NR-RAN with ng-eNB in case of EDT reporting of LCS event TS 23.273CR0213
In Release 18, the changes for EDT focused on providing clarification for data transmission procedures. This work aimed to resolve ambiguities in the existing specifications to ensure more reliable operation. The update specifically addressed the implementation details within the EDT function set.
- Clarification on data transmission for EDT TS 36.300CR1422
In Release 19, the corrections for the CB-MSG3 EDT function were a focus, including specific updates for IoT NTN TDD operation. The changes addressed the EDT procedure in conjunction with DRX for these scenarios. The enhancements aimed to improve the reliability and performance of the EDT function within the specified CB-MSG3 framework.
Explore further
Broader topics and technologies where EDT plays a role.
Defining Specifications
3GPP specifications that define or reference EDT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.226 vj00 | Global Text Telephony (GTT) Stage 1 | Rel-19 |
| TS 23.273 vj50 | 5G Location Services Stage 2 Architecture | Rel-19 |
| TS 23.725 vg20 | Study on URLLC Architecture Enhancements | Rel-16 |
| TS 23.731 vg00 | 5G LCS Architecture Enhancement Study | Rel-16 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 33.401 vj10 | EPS Security Architecture | Rel-19 |
| TS 33.501 vk00 | 5G Security Architecture and Procedures | Rel-20 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.321 vj00 | E-UTRA MAC Protocol Specification | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TR 38.808 vh00 | Study on NR above 52.6 GHz to 71 GHz | Rel-17 |
| TR 38.889 vg00 | NR-based access to unlicensed spectrum study | Rel-16 |