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

Glossary term · Radio Access Network

Overshoot coverage

Overshoot Coverage

Radio Access Network →

Overshoot coverage is the phenomenon where a cell's signal extends far beyond its planned boundaries, creating isolated coverage islands that cause interference and call drops in other cells.

Introduced
Rel-10
Where
Management
Specifications
2 specs
Overshoot coverage Description Purpose What changed Specifications

Description

Overshoot coverage refers to a condition in cellular networks where the radio coverage of a cell extends significantly beyond its intended or planned geographical boundary. This can result in an isolated "island" of coverage from one cell appearing deep inside the coverage area of another cell, even if the two cells are not direct neighbors. Overshoot is typically caused by anomalous radio propagation conditions such as reflections off buildings, ducting over water bodies (lakes, seas), or unusual terrain features that guide signals over long distances. It is a key concern in radio network planning and optimization because it can lead to severe interference and degraded service quality.

The impact of overshoot coverage is multifaceted. User equipment (UE) located in the overshoot area may experience call drops, poor voice quality, or low data throughput due to high interference from the overshooting cell. The overshooting cell's signal may be strong enough to attract UEs that should be served by the local cell, but the timing advance and power control may be suboptimal, leading to link failures. Additionally, the overshooting cell may cause co-channel or adjacent-channel interference to the local cell, reducing its capacity and coverage. In extreme cases, overshoot can create pilot pollution in CDMA systems or PCI confusion in LTE/5G, where UEs cannot reliably identify the best serving cell.

From a standards perspective, overshoot coverage is addressed in 3GPP specifications such as TS 28.628 (Self-Organizing Networks (SON) for 5G) and TS 32.522 (SON for LTE). These documents define mechanisms for detecting and mitigating overshoot, often as part of Mobility Robustness Optimization (MRO) and Coverage and Capacity Optimization (CCO) use cases. Detection typically involves analyzing measurement reports from UEs, such as Reference Signal Received Power (RSRP) or Received Signal Strength Indicator (RSSI), to identify cells appearing as neighbors that are not in the planned neighbor list. Once detected, mitigation may involve adjusting antenna tilt, azimuth, or transmit power, or blacklisting the overshooting cell for certain UEs.

In Self-Organizing Networks (SON), overshoot detection and correction are automated to reduce manual drive tests and optimization effort. The network can collect performance measurements (e.g., handover failure rates, call drop rates) and correlate them with cell topology to pinpoint overshoot. Machine learning techniques are increasingly used to predict and prevent overshoot by analyzing historical data and propagation models. The goal is to maintain planned coverage boundaries while adapting to changing radio conditions.

Overshoot coverage has been a recognized issue since the early days of cellular networks, but its formal treatment in 3GPP specifications began with Release 10 as part of SON enhancements. Since then, the concept and its management have been carried forward through subsequent releases, with ongoing refinements in detection algorithms and mitigation strategies. It remains a critical consideration for operators deploying dense heterogeneous networks, where interference management is paramount.

Purpose & Motivation

Overshoot coverage exists as a concept to describe and manage a common radio propagation anomaly that can severely degrade cellular network performance. Prior to its formal definition in 3GPP, network operators dealt with overshoot on an ad-hoc basis, often through manual drive tests and trial-and-error antenna adjustments. This reactive approach was costly, time-consuming, and not scalable as networks grew denser and more complex. The introduction of SON (Self-Organizing Networks) in Release 10 provided a framework to automate the detection and mitigation of overshoot, making it a first-class citizen in network management.

The primary problem overshoot solves is the need to maintain planned coverage and interference boundaries in the presence of unpredictable radio propagation. In an ideal world, cells would radiate exactly as planned, with sharp boundaries. In reality, reflections and atmospheric ducting can cause signals to travel far beyond intended limits, creating interference and service degradation. By defining overshoot coverage and specifying SON use cases for its detection and correction, 3GPP enables networks to automatically adapt to these anomalies, ensuring that UEs are served by the intended cells and that interference is kept within acceptable limits.

Historically, the limitations of previous approaches were manual optimization and lack of standardized metrics. Before Release 10, there was no standardized way to detect overshoot from network measurements, and mitigation relied on expert judgment. The SON framework introduced standardized measurements and algorithms that could be implemented by vendors, allowing multi-vendor interoperability and reducing operational costs. Today, overshoot coverage management is an integral part of network planning and optimization tools, leveraging data analytics and automation to maintain optimal performance in increasingly complex networks.

What changed in its specifications

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

TS 28.628Rel-14 → Rel-15

Added SON for AAS management clauses, new attributes for AAS switches/load rates, and performance measurement support.

Full comparison in TS 28.628 →
TS 32.522Rel-10 → Rel-11

SON coordination, energy saving management, and inter-RAT energy saving policies were added to 3GPP TS 32.522 in Rel-11.

Full comparison in TS 32.522 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-10 Initial

Initial definition of overshoot coverage as part of SON enhancements. Introduces the concept and the need for automated detection and mitigation to improve network performance.

Definition carried over unchanged. No modifications to the overshoot coverage concept.

Definition carried over unchanged. The description and management principles remained the same.

Definition carried over unchanged. No technical changes were made.

Definition carried over unchanged. Overshoot coverage continued to be addressed by existing SON mechanisms.

Definition carried over unchanged. No updates to the definition or associated procedures.

Definition carried over unchanged. The concept remained stable.

Definition carried over unchanged. Wording is identical, indicating no change.

Definition carried over unchanged. No modifications were introduced.

Definition carried over unchanged. Overshoot coverage remains as originally defined.

Defining Specifications

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

SpecificationTitleRelease
TS 28.628 vj00 SON Policy NRM IRP Information Service Rel-19 read
TS 32.522 vb70 SON Policy NRM IRP Information Service Rel-11 read