Description
In-Device Coexistence (IDC) addresses the critical challenge of interference generated when multiple radio transceivers, such as LTE, Wi-Fi, Bluetooth, and Global Navigation Satellite System (GNSS) receivers, operate simultaneously within a single User Equipment (UE). This interference, often termed In-Device Coexistence Interference (IDCI), arises due to the physical proximity of these radios and the potential for harmonic or intermodulation products, as well as receiver desensitization (blocking). The primary interference scenario of concern is when a transmitter from one technology (e.g., LTE uplink) operates in a frequency band that is harmonically related to, or simply very close to, the receive band of another co-located technology (e.g., ISM band Wi-Fi or Bluetooth). This can severely degrade the sensitivity and performance of the victim receiver.
The 3GPP IDC framework, introduced in Release 11, defines standardized procedures to enable the UE and the network to collaboratively manage this interference. The architecture involves enhancements primarily in the UE and the E-UTRAN (eNodeB). The UE is responsible for detecting IDC problems based on its internal radio configuration and activity. It reports these issues to the eNodeB via RRC signaling, specifically using the `InDeviceCoexIndication` message. This message can convey the affected frequency bands, the direction of interference (e.g., LTE uplink interfering with Wi-Fi reception), and the UE's preferred mitigation method.
Upon receiving an IDC indication, the eNodeB can employ several mitigation strategies defined by 3GPP. The primary methods are Time-Domain Multiplexing (TDM) and Frequency-Domain Multiplexing (FDM). TDM solutions involve scheduling gaps or patterns where the interfering transmission is momentarily halted to allow the victim receiver to operate undisturbed. The eNodeB can configure `IDC-SubframePatterns` for LTE to create these quiet periods. For FDM, the network can initiate a handover or change the serving frequency of the LTE radio to a band that does not cause interference with the other in-device technology. The eNodeB makes the final decision on which mitigation technique to apply, balancing UE requests with overall network resource management and load conditions.
The IDC procedures are tightly integrated with the UE's RRC protocol stack (`36.331`) and radio resource management. The specifications also cover scenarios for autonomous denial, where the UE can, within network-authorized limits, momentarily deny LTE transmissions to protect other radios, and for UE assistance information transfer to the network. The framework ensures that the proliferation of multi-radio devices does not lead to unacceptable user experience degradation for any of the active services, be it cellular data, Wi-Fi calling, Bluetooth audio, or satellite positioning.
Purpose & Motivation
IDC was created to solve the practical and growing problem of radio frequency interference inside modern smartphones and tablets. As these devices evolved to incorporate an increasing array of wireless technologies—LTE, 3G, 2G, Wi-Fi (2.4 GHz and 5 GHz), Bluetooth, Near Field Communication (NFC), and GNSS (GPS, GLONASS)—all packed into a very small form factor, the potential for these radios to interfere with each other became significant. Prior to IDC standardization, mitigation was left to individual device manufacturers, leading to proprietary, non-interoperable solutions that were often inefficient and could negatively impact network performance without the operator's knowledge.
The key problem IDC addresses is the degradation of service quality. For example, a user making a Voice over Wi-Fi call while LTE is active on Band 7 (2500 MHz) could experience dropped calls because the LTE uplink transmissions (around 2500-2570 MHz) can generate harmonics that fall into the 2.4 GHz ISM band used by Wi-Fi, desensitizing the Wi-Fi receiver. Similarly, LTE Band 40 (2300 MHz) operations can interfere with GNSS reception. Without coordination, the device might simply experience poor performance, or resort to aggressively shutting down one radio, defeating the purpose of a multi-radio device.
3GPP standardized IDC to provide a unified, network-aware solution. This allows network operators to maintain control over radio resource usage while enabling optimal device performance. It creates a predictable environment where the network understands the device's internal constraints and can schedule resources accordingly, improving overall system efficiency, user experience, and ensuring that the introduction of new frequency bands or device form factors does not break existing functionality. It represents a shift from treating the UE as a black box to a more collaborative management model between the device and the network.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (30 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-11, normative work from Rel-15.
In Release 15, the IDC function was extended to support EN-DC (E-UTRA-NR Dual Connectivity) operation, introducing specific UE capabilities and mechanisms for this architecture. This included clarifications on reporting procedures and the handling of candidate NR frequencies for coexistence management within EN-DC. Additionally, corrections were made to address IDC reporting and hardware sharing problems.
- Introduction of increased number of E-UTRAN data bearers TS 36.331CR3446
- UE capabilty for IDC mechanism for EN-DC operation TS 36.331CR3599
- Correction of CN type indication for RRC Redirection from E-UTRA/5GC to E-UTRA/5GC or E-UTRAN TS 36.331CR3601
- Correction concerning IDC reporting TS 36.331CR3775
- NR UE capability filtering in E-UTRAN TS 36.331CR3849
- Clarification on candidate NR frequencies for IDC in EN-DC TS 36.331CR4168
+ 3 more changes
In Release 16, the key new developments for the IDC function were the introduction of an NR IDC solution and the specification of UE capability for IDC. This built upon previous releases by extending coexistence mechanisms to support New Radio operations alongside other in-device radios. A correction to the IDC indication procedure was also included to refine the signaling.
- Introduction of even further mobility enhancement in E-UTRAN TS 36.300CR1270
- Introduction of Even further Mobility enhancement in E-UTRAN TS 36.331CR4205
- UE capability for IDC TS 38.306CR0229
- Introduction of NR IDC solution TS 38.331CR1443
- Corrections to even further mobility enhancement in E-UTRAN TS 36.300CR1284
- Clarification on non-coexistence of CHO and DAPS TS 38.331CR2700
+ 2 more changes
In Release 17, the enhancements for In-Device Coexistence (IDC) introduced support for Multi-USIM devices, addressing the coordination of radio resources when a User Equipment operates with multiple active subscriptions. Furthermore, the release specified the signaling of UE Security Capabilities in E-UTRAN to ensure secure and efficient coexistence management. These updates provided a more robust framework for handling interference and resource conflicts in increasingly complex multi-radio terminals.
In Release 18, the enhancements for In-Device Coexistence (IDC) in NR introduced specific corrections and clarifications to existing procedures. These included corrections to IDC reporting and the configuration of time-division multiplexing (TDM) assistance, as detailed in the idc-TDM-AssistanceConfig. Furthermore, the release provided necessary clarifications for integrating IDC solutions with logged Minimization of Drive Tests (MDT) functionality.
- Introduction of In-Device Co-existence (IDC) Enhancements for NR TS 37.340CR0367
- Introduction of In-Device Co-existence (IDC) enhancements for NR TS 38.331CR4164
- Correction on the IDC Reporting TS 37.340CR0382
- Miscellaneous corrections for IDC TS 38.331CR4621
- Miscellaneous corrections for IDC TS 38.331CR4838
- Correction on the idc-TDM-AssistanceConfig TS 38.331CR5062
+ 1 more changes
In Release 19, the enhancements for In-Device Coexistence (IDC) specifically introduced support for NB-IoT satellite (NTN) operations within E-UTRAN. The new capabilities include the provisioning of NB-IoT NTN satellite information and the indication of a supported NB-IoT NTN band list to enable redirection from terrestrial E-UTRAN to NB-IoT non-terrestrial networks.
- Introduction of NB-IoT satellite information in E-UTRAN [EUTRAN-to-NBIoTNTN] TS 36.300CR1427
- Introduction of NB-IoT satellite information in E-UTRAN [EUTRAN-to-NBIoTNTN] TS 36.331CR5140
- Correction for the redirection from E-UTRAN TN to NB-IoT NTN [IoT_TN_NTN_redir] TS 36.331CR5173
- Indication of supported NB-IoT NTN band list in E-UTRAN [IoT_TN_NTN_redir] TS 36.331CR5183
Explore further
Broader topics and technologies where IDC plays a role.
Defining Specifications
3GPP specifications that define or reference IDC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.874 vi20 | Technical Report | Rel-18 |
| TS 32.423 vj50 | Trace Data Definition and Management | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TR 36.791 vg00 | E-UTRA 2.4 GHz TDD Band for US | Rel-16 |
| TS 36.880 vd00 | MDT Enhancements Study for E-UTRAN | Rel-13 |
| TS 37.340 vj00 | Multi-Connectivity Operation Overview | Rel-19 |
| TS 38.306 vj00 | NR UE Radio Access Capability Parameters | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |