Physical Cell Identity (PCI) Collision Detection

A PCI collision occurs when two geographically overlapping cells use the same PCI, causing user equipment (UE) to be unable to distinguish between them during cell search and handover procedures. A related issue, PCI confusion, happens when a cell has two neighbors with the same PCI, making it impossible for the UE to report the correct target cell for handover. With only 1008 unique PCI values available in LTE and 5G NR, reuse is inevitable in dense urban deployments, making automated collision detection essential for network stability.

PCI collision detection relies on multiple data sources and algorithms to identify conflicts without manual drive testing:

• UE Measurement Reports: The network analyzes measurement reports from connected UEs, which include PCI and signal strength. If a UE reports a PCI with strong signal but the network cannot identify the corresponding cell in its Neighbor Relation Table (NRT), a potential collision is flagged.
• X2/Xn Interface Signaling: During X2 or Xn setup, neighboring eNBs/gNBs exchange their PCI and Cell Global Identity (CGI). A mismatch between the reported PCI and the expected CGI triggers a collision alarm.
• Automatic Neighbor Relation (ANR) Integration: The ANR function instructs UEs to read the CGI of unknown cells. If the CGI read-back reveals two distinct cells sharing the same PCI, a collision is confirmed.

Once a PCI collision is confirmed, the Centralized SON (C-SON) or Distributed SON (D-SON) function initiates an automated resolution workflow:

1. Conflict Classification: The system determines if the issue is a direct collision (same PCI, overlapping coverage) or confusion (one cell sees two neighbors with the same PCI).
2. Candidate Selection: An algorithm selects a new PCI from the pool of unused values, applying constraints to avoid collisions with neighbors, neighbors-of-neighbors, and to prevent PCI modulo conflicts that cause reference signal collisions.
3. Hitless Reconfiguration: The new PCI is applied during a low-traffic window or via a coordinated procedure to minimize service disruption. The updated PCI is propagated to all neighboring cells via X2/Xn interface updates.

Effective PCI collision detection algorithms must respect multiple physical layer constraints to avoid secondary interference:

• Modulo 3 Rule: PCIs are derived from Primary Synchronization Signals (PSS), which have only 3 sequences. Cells with PCIs where (PCI mod 3) are equal will have colliding PSS, degrading synchronization.
• Modulo 6 Rule: For 2-antenna port deployments, Cell-Specific Reference Signals (CRS) use a frequency shift based on (PCI mod 6). Collisions here cause persistent reference signal interference.
• Modulo 30 Rule: In 5G NR, Demodulation Reference Signal (DMRS) and Physical Uplink Control Channel (PUCCH) sequences depend on (PCI mod 30), requiring broader separation in dense deployments.
• Reuse Distance: The algorithm must ensure a minimum geographical distance between cells sharing the same PCI to prevent distant co-channel interference from being mistaken for a neighbor.

PCI collision detection can be implemented in different SON architectures, each with trade-offs:

• Centralized (C-SON): A central server aggregates measurement reports and configuration data from across the network, building a global topology graph. This provides optimal PCI assignment but introduces latency in detection and resolution.
• Distributed (D-SON): Each eNB/gNB autonomously detects collisions by analyzing incoming X2/Xn setup requests and UE reports. This enables sub-second reaction times but may lead to PCI ping-pong where two cells repeatedly change PCIs to resolve a conflict, only to create new ones.
• Hybrid (H-SON): Local nodes perform rapid detection and temporary mitigation, while a central coordinator validates the global impact of any PCI change before permanent reassignment, preventing cascading conflicts.

Unresolved PCI collisions directly degrade Key Performance Indicators (KPIs) related to mobility:

• Radio Link Failure (RLF) Rate: UEs attempting to hand over to a target cell with a colliding PCI may connect to the wrong cell, resulting in immediate RLF and call drops.
• Handover Success Rate (HOSR): Collisions cause handover preparation failures because the source eNB cannot uniquely identify the target cell in X2/Xn signaling.
• Ping-Pong Handovers: A UE at the border of two colliding cells may repeatedly hand over between them as signal strengths fluctuate, wasting signaling resources and degrading user experience.
• Access Delay: During initial cell search, a UE may attempt to camp on a cell with a colliding PCI, only to be rejected after reading the System Information Block (SIB), increasing call setup time.