Automatic Neighbor Relation (ANR) is a SON mechanism that uses User Equipment (UE) measurement reports to automatically detect, add, and manage missing neighbor cells in the handover candidate list. Managed by the RAN Intelligent Controller (RIC) in O-RAN architectures, ANR resolves Physical Cell Identity (PCI) confusion and maintains an accurate Neighbor Relation Table (NRT) without operator intervention.
Glossary
Automatic Neighbor Relation (ANR)

What is Automatic Neighbor Relation (ANR)?
A foundational Self-Organizing Network (SON) function that automates the discovery and management of neighbor cell relationships in cellular networks, eliminating the need for manual configuration and drive testing.
The function operates by instructing UEs to decode the E-UTRAN Cell Global Identifier (ECGI) of detected cells, enabling the network to establish an X2/Xn interface with newly discovered eNBs/gNBs. This closed-loop process directly supports Mobility Robustness Optimization (MRO) by preventing radio link failures caused by missing adjacency definitions.
Frequently Asked Questions
Clear, technical answers to the most common questions about Automatic Neighbor Relation (ANR) functionality within the O-RAN Intelligent Controller architecture.
Automatic Neighbor Relation (ANR) is a foundational Self-Organizing Network (SON) function that automates the discovery and management of neighbor cell lists required for seamless handovers. It eliminates the need for manual cell planning by leveraging User Equipment (UE) measurement reports. The process begins when a serving cell instructs a connected UE to measure signal strength on a specific frequency. If the UE detects a strong Physical Cell Identity (PCI) not present in the serving cell's Neighbor Relation Table (NRT), it reports this unknown PCI back to the network. The serving cell then instructs the UE to read the E-UTRAN Cell Global Identifier (ECGI) of the target cell, which provides a globally unique identity. Upon receiving the ECGI, the network can establish an X2/Xn interface and automatically add the new cell to the NRT, defining its relationship attributes (e.g., 'No Remove', 'No HO'). This closed-loop automation is critical for dense heterogeneous network (HetNet) deployments where manual neighbor list maintenance is operationally impossible.
Key Features of ANR
ANR is a foundational Self-Organizing Network (SON) function that automates the discovery and management of neighbor cell lists, eliminating the need for manual drive testing and configuration.
UE-Assisted Discovery
ANR leverages User Equipment (UE) measurement reports to detect missing neighbor cells. When a UE reports a strong Physical Cell Identity (PCI) not in the current Neighbor Relation Table (NRT), the eNB/gNB instructs the UE to read the target cell's E-UTRAN Cell Global Identifier (ECGI) or NR Cell Global Identifier (NCGI). This automated process eliminates manual drive testing and ensures the handover candidate list remains dynamically updated as the network topology changes.
Neighbor Relation Table (NRT) Management
The Neighbor Relation Table (NRT) is the central database managed by ANR containing all established neighbor relationships. Each entry includes:
- Target Cell Identifier (TCI): The unique ECGI/NCGI of the neighbor cell
- No Remove flag: Prevents automatic deletion of critical neighbors
- No HO flag: Allows a neighbor to be listed but blocks handover attempts
- No X2/Xn flag: Prevents automatic X2/Xn interface setup The RIC can enrich these entries with AI-derived performance metrics for intelligent handover decisions.
X2/Xn Interface Auto-Setup
Upon discovering a new neighbor cell, ANR triggers the automatic establishment of the X2 interface (LTE) or Xn interface (5G NR) between base stations. The serving eNB/gNB uses the discovered target cell's global ID to resolve its IP address via the Transport Network Layer (TNL) address discovery process. This enables direct inter-cell communication for coordinated scheduling, interference management, and seamless handover execution without manual transport network configuration.
PCI Conflict Detection & Resolution
ANR continuously monitors for PCI confusion and PCI collision scenarios that cause handover failures. PCI confusion occurs when two neighbor cells share the same PCI, making it impossible to uniquely identify a handover target. PCI collision happens when two overlapping cells use the same PCI. The RIC's ANR function correlates UE measurement reports with global cell identities to detect these conflicts and trigger automated PCI reallocation, ensuring unambiguous cell identification across the network.
RIC-Enhanced ANR with AI/ML
Traditional SON-based ANR operates reactively. The RAN Intelligent Controller (RIC) enhances ANR with predictive AI/ML models that:
- Forecast mobility patterns to pre-configure neighbor relations before UEs enter overlapping coverage areas
- Optimize NRT pruning by analyzing historical handover success rates to remove stale or underperforming neighbors
- Correlate ANR events with Mobility Robustness Optimization (MRO) to jointly tune handover trigger thresholds This closed-loop mechanism transforms ANR from a reactive discovery tool into a proactive network optimization function.
Closed-Loop Automation Flow
The ANR closed-loop mechanism operates through a continuous cycle:
- Monitor: The RIC ingests UE measurement reports and handover failure statistics via the E2 interface
- Analyze: AI models detect missing neighbors, PCI conflicts, and stale NRT entries
- Decide: The xApp/rApp determines optimal neighbor additions, removals, or PCI reassignments
- Execute: Configuration changes are pushed to the RAN via the O1 or E2 interface
- Verify: Post-action KPIs confirm improved handover success rates, closing the loop without human intervention.
ANR vs. Manual Neighbor Planning
Comparison of automated neighbor cell discovery versus traditional manual configuration in cellular networks.
| Feature | Automatic Neighbor Relation (ANR) | Manual Neighbor Planning |
|---|---|---|
Discovery method | UE measurement reports trigger automated detection | Drive testing and site surveys |
Configuration speed | < 1 second per relation | Hours to days per site |
Human intervention | ||
Adaptation to RF changes | ||
PCI conflict detection | Automated via RIC analytics | Manual audit required |
Operational cost | Low (automated) | High (labor-intensive) |
Error rate | 0.3% missed neighbors | 5-15% missed neighbors |
Scalability for dense HetNets |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Automatic Neighbor Relation (ANR) is a foundational function that interacts with several other RIC and SON mechanisms to ensure seamless mobility and network stability.
Physical Cell Identity (PCI) Conflict Detection
A critical companion to ANR that resolves PCI collisions and confusion. While ANR manages the logical neighbor list, PCI detection ensures that no two neighboring cells share the same identifier, which would cause handover failures. The RIC automates this by cross-referencing UE measurement reports with the discovered topology.
Mobility Robustness Optimization (MRO)
MRO closes the loop on ANR by tuning handover parameters for discovered neighbors. Key functions include:
- Detecting too-early or too-late handovers
- Mitigating ping-pong handovers between overlapping cells
- Adjusting the Time-to-Trigger (TTT) and A3 offset thresholds MRO uses radio link failure (RLF) reports to continuously optimize the neighbor relations built by ANR.
E2 Interface & RAN Function Exposure
The E2 interface is the protocol pathway that allows the Near-RT RIC to execute ANR logic. Through RAN Function Exposure, the RIC subscribes to UE measurement reports and issues neighbor list updates directly to the O-CU/O-DU. This standardized API abstracts vendor-specific implementations, enabling a single ANR xApp to work across multi-vendor deployments.
Coverage and Capacity Optimization (CCO)
CCO leverages the topology map created by ANR to optimize the RF environment. By understanding the neighbor graph, CCO algorithms can:
- Adjust antenna tilt and beam patterns to fill coverage gaps
- Balance load between overlapping cells
- Predict the impact of a power change on the neighbor adjacency matrix ANR provides the structural map; CCO performs the spatial optimization.
Inter-Cell Interference Coordination (ICIC)
ICIC relies on ANR's neighbor topology to schedule resources intelligently. By knowing exactly which cells are adjacent, the scheduler can allocate Resource Blocks (RBs) to cell-edge users in a way that avoids collision with high-power transmissions in neighboring cells. Enhanced ICIC (eICIC) further uses Almost Blank Subframes (ABS) based on this neighbor map.
Anomaly Detection & Sleeping Cell Mitigation
ANR data feeds into anomaly detection engines monitoring for sleeping cells—cells that appear operational but fail to establish connections. If a cell stops accepting handovers, the neighbor graph built by ANR allows the RIC to quickly identify the outage and trigger compensation by expanding the coverage of surrounding cells, maintaining the integrity of the mobility domain.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us