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

Glossary term · Radio Access Network

IDC

In-Device Coexistence

Radio Access Network →

IDC is a set of mechanisms to manage radio interference between different technologies operating concurrently within a single device.

Introduced
Rel-11
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
9 specs
IDC Description Purpose What changed Neighbours Detected Changes Specifications

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.

What changed in its specifications

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

TS 32.423Rel-18 → Rel-19

Rel-19 adds a GPB annex of Streaming Trace message examples to TS 32.423. It also adds new Immediate MDT measurement fields, extended Trace Record Header fields, and new GPB field definitions for subscriber and equipment trace and QoE collection management.

Full comparison in TS 32.423 →
TS 36.300Rel-18 → Rel-19

Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.

Full comparison in TS 36.300 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 5 changes
  • UE capabilty for IDC mechanism for EN-DC operation TS 36.331CR3599
  • Correction concerning IDC reporting TS 36.331CR3775
  • Clarification on candidate NR frequencies for IDC in EN-DC TS 36.331CR4168
  • Introduction of IDC mechanism for EN-DC operation TS 37.340CR0098
  • Correction for IDC hardware sharing problems TS 36.331CR3357
Rel-16 3 changes
Rel-18 7 changes
  • 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

Defining Specifications

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

SpecificationTitleRelease
TR 22.874 vi20 Technical Report Rel-18 read
TS 32.423 vk10 Trace Data Definition and Management Rel-20 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TR 36.791 vg00 E-UTRA 2.4 GHz TDD Band for US Rel-16 read
TS 36.880 vd00 MDT Enhancements Study for E-UTRAN Rel-13 read
TS 37.340 vj30 Overview of Multi-Connectivity Operation using E-UTRA and NR Rel-19 read
TS 38.306 vj40 NR UE Radio Access Capability Parameters Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read