PCI Conflict Reporting

Feature Description

50/221 04-LZA 701 6014/1 Uen AJ16B

Copyright

© Ericsson AB 2016–2021. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

 Contents

Contents

1 Overview 1

2 Dependencies 3

3 Feature Operation 5
3.1 Process Steps 6

4 Network Impact 9

5 Parameters 10

6 Performance 12

7 Activate the Feature 13

8 Deactivate the Feature 14

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

PCI Conflict Reporting

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

1 PCI Conflict Reporting Overview

The PCI Conflict Reporting feature detects PCI conflicts and reports them to
the OSS.

Access Type: LTE

Feature Identity: FAJ 121 1898
Value Package Name: Self-Organizing Networks
Value Package Identity: FAJ 801 0435
Node Type: Baseband Radio Node
Licensing: Licensed feature. One license per
radio.

Summary
Handover statics and UE drop statics are improved, because the PCI Conflict
Reporting feature reports PCI conflicts to the OSS. This makes the fast resolving
of the PCI conflict possible.

A mobile phone cannot distinguish between two cells if the cells have the same
PCI and the same frequency. It is possible that a handover fails when the PCI
that is included in the measurement report does not uniquely identify the cell.
The PCI Conflict Reporting feature detects when PCIs do not uniquely identify
the neighbor cells. This is called PCI confusion. As a result, a faulty configuration
can be detected automatically.

PCI confusion might occur even when no configured relations exist.

PCI collision is when a UE is in one cell and can hear another cell with the same
PCI and frequency. If the UE needs to perform a handover to a cell with the same
PCI as the source cell, the UE moves towards the cell with the same PCI and
frequency. In most of these cases, the UE drops, because it does not distinguish
the target cell from the source cell. PCI collision can be detected by the PCI
Conflict Reporting feature only if relations are manually configured. However, it is
possible that a PCI collision also results in a PCI confusion for another cell. PCI
collisions are detected indirectly by this feature. This improves statistics
regarding UE drops caused by PCI collisions.

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09 1

 PCI Conflict Reporting

RBS A

RBS B
PCI=7

PCI=10

PCI=10

L0000569A

Figure 1 Both PCI Collision and Confusion

Additional Information
For information on the preferred state and parameter settings of this feature, see
RAN Parameter Recommendations Lists.

More information about this feature and related topics can be found in the
following documentation:

— 3GPP TS 36.331

— 3GPP TS 36.423

— 3GPP TS 36.330

2 50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

2 Dependencies of PCI Conflict Reporting

PCI conflicts result in failed handover.

Table 1 Feature Dependencies

Feature Relationship Description
Automated Neighbor Relations (FAJ 121 0497) Prerequisite PCI confusions can be detected by the PCI Conflict
Reporting feature if the operator is using the
Automated Neighbor Relations feature together
with one of the following:

— X2 connections with
ENodeBFunction.x2SetupTwoWayRelation
s set to true.

X2 Configuration (FAJ 121 0484)
Automatic PCI Collision Resolution (FAJ 121 2266)
Intra-LTE Handover (FAJ 121 0489)
Intra-LTE Inter-Mode Handover (FAJ 121 3042)
Coverage-Triggered Inter-Frequency handover (FAJ
121 0489)
— ENodeBFunction.zzzTemporary39 set to 1
or the default value.
Prerequisite PCI confusions can be detected by this feature if the
operator is using X2 connections with
ENodeBFunction.x2SetupTwoWayRelations set to
true together with the Automated Neighbor
Relations feature.
Related When a PCI conflict is reported by the RBS, it
results in an alarm, if the Automatic PCI Collision
Resolution feature license is active and configured
accordingly.
Conflicting PCI conflicts result in failed handover and affect the
Intra-LTE Handover feature.
Related The PCI Conflict Reporting feature identifies PCI
conflicts that result in failed handover.
Conflicting PCI conflicts result in failed handover and affect the
Coverage-Triggered Inter-Frequency Handover.

Hardware
No specific hardware requirement is expected for this feature.

Limitations
No limitations for this feature.

Network Requirements
One of the following must be fulfilled at the activation of the feature:
— ENodeBFunction.X2SetupTwoWayRelations is set to true.

— ENodeBFunction.zzzTemporary39 is set to 1 or the default value.

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09 3

 PCI Conflict Reporting

RELATED INFORMATION

3.1.2 Report PCI Conflict Detected Based on X2 Functionality on page 7

3.1.3 Report PCI Conflict Detected Based on S1 Incoming Handover on page

8

4 50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

3 Feature Operation of PCI Conflict Reporting

The PCI Conflict Reporting feature detects when PCIs do not uniquely
identify the neighbor cells.

PCI confusion occurs because a mobile phone cannot distinguish between two
cells if they have the same PCI and the same frequency.

Operational Process
The prerequisites for PCI Conflict Reporting are the following:

1. PCI=1 cells are on the same frequency.

2. Neighbor cell relations from the PCI=10 cell to the PCI=1 cell of RBS C exist.

OSS

4
3
Relation
Relation Re
lati
PCI=1 1 PCI=10 on

2
PCI=1

RBS A RBS B RBS C

L0000570C

Figure 2 Operational Sequence Diagram of PCI Conflict Reporting

1. A first neighbor cell relation from the PCI=1 cell of RBS A to the PCI=10 cell
of RBS B is created in RBS A by ANR or manually.

2. One of the following occurs:

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09 5

 PCI Conflict Reporting

a. RBS B receives X2 setup request, X2 setup response, or eNodeB

configuration update from RBS A with information about the new
neighbor cell relation.
b. S1 incoming handover is attempted from RBS A to RBS B with
information about the new neighbor cell relation.

3. The external cell list in RBS B contains two PCI=1 cells. Depending on acting
functionality, the following cases are possible:

a. If ENodeBFunction.x2SetupTwoWayRelations is true, RBS B creates

mutual relation from the PCI=10 cell to the PCI=1 cell of RBS A.
b. If ENodeBFunction.zzzTemporary39 is set to 1 or the default value, a
relation from the PCI=10 cell of RBS B to the PCI=1 cell of RBS A is
created.

4. When the relation is created, PCI confusion (PCI=1) is detected in the cell in
RBS B and reported to OSS.

Note: A PCI conflict can exist even if configured relations do not exist. For
example, the PCI=10 cell can have a configured relation to the PCI=1
cell of RBS C, but not a configured relation to the PCI=1 cell of RBS A.

A UE connected to the PCI=10 cell can report the PCI=1 cell in order to
perform handover to the cell of RBS A, but RBS B prepares the handover
to RBS C. This results in a failed handover. Because of this, PCI conflicts
must be detected even if relations are not configured.

3.1 Process Steps

PCI confusion and conflict detection is based on one of the following:
— Configured relation

— X2 Functionality

— S1 incoming handover

3.1.1 PCI Conflict Detected Based on Configured Relation

PCI confusion and collision are detected based on configured relation.

PCI confusion is reported to the OSS if the following is true:

— An E-UTRAN cell has neighbor cell relationship for mobility to two E-UTRAN
cells where both cells have the same PCI and frequency.

PCI collision is reported to the OSS if the following is true:

6 50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

 — An E-UTRAN cell has neighbor cell relationship to an E-UTRAN cell with the
same PCI and frequency.

Note: This can only occur when a neighbor cell relation is created
manually.

The following triggers the execution of PCI conflict check:

— One new relation is added.

— ExternalENodeBFunction.ExternalEUtranCellFDD or
ExternalENodeBFunction.ExternalEUtranCellTDD gets a new PCI.

— The ENodeBFunction.EUtranCellFDD or the

ENodeBFunction.EUtranCellTDD internal cell gets a new PCI.

If a PCI conflict is detected, the pciConflict attribute is set to YES. This results
in the PCI CONFLICT DETECTED CM event.

3.1.2 Report PCI Conflict Detected Based on X2 Functionality

PCI confusion detection is based on sending neighbor information in X2

setup request, X2 setup response, and eNodeB configuration update.

Neighbor information is information about configured relations for each served

cell. When the relation is added or deleted, the neighbor information is sent to the
neighbor RBSs over X2.

Neighbor information for an E-UTRAN cell relation contains the following

information:

— E-UTRAN Cell Global Identifier of the neighbor cell

— PCI of the neighbor cell

— DL EARFCN for FDD and EARFCN for TDD

Neighbor information is used to create two-way relations, that is, the RBS creates
a two-way relation for each entry in the received neighbor information that
contains a relation to a source cell.

Note: Two-way relations are created only if the

ENodeBFunction.x2SetupTwoWayRelations parameter is set to true.

The sending of neighbor information over X2 and the setup of two-way relations
result in configured relations. This makes the detection of PCI confusions
possible.

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09 7

 PCI Conflict Reporting

RELATED INFORMATION

3.1.1 PCI Conflict Detected Based on Configured Relation on page 6

3.1.3 Report PCI Conflict Detected Based on S1 Incoming Handover

PCI conflict detection is based on neighbor cell CGI, PCI, and EARFCN
received along with S1 Incoming Handover attempt.

When PCI conflict is identified, a new relation is created, and the RBS can report
this to the operator.

Note: Relation is created only if the parameter

ENodeBFunction.zzzTemporary39 is set to 1 or -2000000000.

3.1.4 Report PCI Conflict Resolved to the OSS

The RBS checks if a PCI conflict is resolved if one of the following is true:

— One relation is deleted.

— ExternalENodeBFunction.ExternalEUtranCellFDD or
ExternalENodeBFunction.ExternalEUtranCellTDD gets a new PCI.

— ENodeBFunction.EUtranCellFdd (internal cell) gets a new PCI.

If a PCI conflict is resolved, the pciConflict attribute is set to NO. This results in
the PCI CONFLICT RESOLVED CM event.

8 50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

4 Network Impact of PCI Conflict Reporting

The PCI Conflict Reporting feature makes the fast resolving of faulty
configurations possible.

Capacity and Performance

PCI conflicts can result in failed handover. The PCI Conflict Reporting feature can
detect PCI conflicts automatically. This way, a faulty configuration can be
detected and it is possible to resolve the PCI conflict fast.

Interfaces
No impact.

Other Network Elements

No impact.

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09 9

 PCI Conflict Reporting
5 Parameters of PCI Conflict Reporting
The feature can be parameterized by setting temporary, X2-related, and
PCI conflict-related attributes.
Table 2 Parameters
Parameter
ENodeBFunction.x2SetupTwoWayRelation
s
ENodeBFunction.zzzTemporary39
EUtranCellFDD.pciConflict
EUtranCellTDD.pciConflict
ExternalEUtranCellFDD.pciConflict
ExternalEUtranCellTDD.pciConflict
EUtranCellFDD.pciConflictCell
EUtranCellTDD.pciConflictCell
ExternalEUtranCellFDD.pciConflictCel
l ExternalEUtranCellFDD.pciDetectingCe
10
Type Description
Introduced See MOM description.
Introduced Indicates if a relation is created during S1
incoming handover when PCI conflict is
identified.
A relation is created when the attribute is
set to 1 or the default value.
No relation is created when the attribute is
set to 0.
Affected
Affected
If a PCI conflict is detected, the attribute is
Affected set to YES.
Affected
Affected The first cell in the
EUtranCellFDD.pciDetectingCell list
corresponds to the first cell in the
EUtranCellFDD.pciConflictCell list and
to the first value of
EUtranCellFDD.pciConflict. The second
cell in the
EUtranCellFDD.pciDetectingCell list
corresponds to the second cell in the
EUtranCellFDD.pciConflictCell list and
to the first value of
EUtranCellFDD.pciConflict.
Affected The first cell in the
EUtranCellTDD.pciDetectingCell list
corresponds to the first cell in the
EUtranCellTDD.pciConflictCell list and
to the first value of
EUtranCellTDD.pciConflict. The second
cell in the
EUtranCellTDD.pciDetectingCell list
corresponds to the second cell in the
EUtranCellTDD.pciConflictCell list and
to the first value of
EUtranCellTDD.pciConflict.
Affected The first cell in the
ll list corresponds to the first cell in the
ExternalEUtranCellFDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellFDD.pciConflict.
The second cell in the
ExternalEUtranCellFDD.pciDetectingCe
ll list corresponds to the second cell in the
ExternalEUtranCellFDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellFDD.pciConflict.
50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09
 Parameter
ExternalEUtranCellTDD.pciConflictCel
l ExternalEUtranCellTDD.pciDetectingCe
EUtranCellFDD.pciDetectingCell
EUtranCellTDD.pciDetectingCell
ExternalEUtranCellFDD.pciDetectingCe
ll
ExternalEUtranCellTDD.pciDetectingCe
ll
50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09
Type Description
Affected The first cell in the
ll list corresponds to the first cell in the
ExternalEUtranCellTDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellTDD.pciConflict.
The second cell in the
ExternalEUtranCellTDD.pciDetectingCe
ll list corresponds to the second cell in the
ExternalEUtranCellTDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellTDD.pciConflict.
Affected The first cell in the
EUtranCellFDD.pciDetectingCell list
corresponds to the first cell in the
EUtranCellFDD.pciConflictCell list and
to the first value of
EUtranCellFDD.pciConflict. The second
cell in the
EUtranCellFDD.pciDetectingCell list
corresponds to the second cell in the
EUtranCellFDD.pciConflictCell list and
to the first value of
EUtranCellFDD.pciConflict.
Affected The first cell in the
EUtranCellTDD.pciDetectingCell list
corresponds to the first cell in the
EUtranCellTDD.pciConflictCell list and
to the first value of
EUtranCellTDD.pciConflict. The second
cell in the
EUtranCellTDD.pciDetectingCell list
corresponds to the second cell in the
EUtranCellTDD.pciConflictCell list and
to the first value of
EUtranCellTDD.pciConflict.
Affected The first cell in the
ExternalEUtranCellFDD.pciDetectingCe
ll list corresponds to the first cell in the
ExternalEUtranCellFDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellFDD.pciConflict.
The second cell in the
ExternalEUtranCellFDD.pciDetectingCe
ll list corresponds to the second cell in the
ExternalEUtranCellFDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellFDD.pciConflict.
Affected The first cell in the
ExternalEUtranCellTDD.pciDetectingCe
ll list corresponds to the first cell in the
ExternalEUtranCellTDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellTDD.pciConflict.
The second cell in the
ExternalEUtranCellTDD.pciDetectingCe
ll list corresponds to the second cell in the
ExternalEUtranCellTDD.pciConflictCel
l list and to the first value of
ExternalEUtranCellTDD.pciConflict.
11
 PCI Conflict Reporting

6 Performance of PCI Conflict Reporting

The Mobility Success Rate Key Performance Indicator (KPI) is associated

with the PCI Conflict Reporting feature. PCI conflict detection and
resolution related events are also associated with the feature.

KPIs
For the main KPIs associated with the Mobility Success Rate of the feature, see
Key Performance Indicators.

Counters
This feature has no directly associated counters.

Events

Table 3 Events
Event Event Parameter Description
INTERNAL_EVENT_PCI_CONFLICT_D EVENT_PARAM_NEIGHBOR_PCI PCI conflict is detected.
ETECTED EVENT_PARAM_NEIGHBOR_CGI
EVENT_PARAM_NEIGHBOR_CGI2
INTERNAL_EVENT_PCI_CONFLICT_R EVENT_PARAM_NEIGHBOR_PCI PCI conflict is resolved.
ESOLVED EVENT_PARAM_NEIGHBOR_CGI
EVENT_PARAM_NEIGHBOR_CGI2

12 50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09

7 Activate PCI Conflict Reporting

To use the feature, it must be activated following the usual feature

activation procedure.

Prerequisites

— The license key is installed in the node.

— Continuous Cell Trace Recording (CCTR) is activated since at least one week.
This ensures there is troubleshooting data available if something goes
wrong.

Steps

1. Set the FeatureState.featureState attribute to ACTIVATED in the

FeatureState=CXC4011183 MO instance.

After This Task

Let the CCTR be active for one week, for continued collection of troubleshooting
data.

50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09 13

 PCI Conflict Reporting

8 Deactivate PCI Conflict Reporting

If the feature is no longer needed, it can be deactivated following the usual

feature deactivation procedure. It must also be deactivated before the
activation of any conflicting feature.

Prerequisites
Continuous Cell Trace Recording (CCTR) is activated since at least one week. This
ensures there is troubleshooting data available if something goes wrong.

Steps

1. Set the FeatureState.featureState attribute to DEACTIVATED in the

FeatureState=CXC4011183 MO instance.

After This Task

Let the CCTR be active for one week, for continued collection of troubleshooting
data.

14 50/221 04-LZA 701 6014/1 Uen AJ16B | 2021-07-09