LTE PCI Self-Optimization Feature (V100R015C10_01)(PDF)-En

SONMaster V100R015C10

LTE PCI Self-Optimization Feature Description Issue

01

Date

2015-06-18

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 01 (2015-06-18)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

LTE PCI Self-Optimization Feature Description

Contents

Contents 1 About This Document .................................................................................................................. 1 1.1 Scope ............................................................................................................................................................................ 1 1.2 Intended Audience ........................................................................................................................................................ 2 1.3 Change History ............................................................................................................................................................. 2 1.4 Differences Between eNodeB Types ............................................................................................................................ 2

2 Overview......................................................................................................................................... 4 2.1 Introduction .................................................................................................................................................................. 4 2.2 Benefits ......................................................................................................................................................................... 5 2.3 Architecture .................................................................................................................................................................. 5

3 PCI Conflict Detection ................................................................................................................. 7 3.1 PCI Conflict Types........................................................................................................................................................ 7 3.1.1 PCI Collision ............................................................................................................................................................. 7 3.1.2 PCI Confusion ........................................................................................................................................................... 8 3.1.3 PCI Mod 3 Interference ............................................................................................................................................. 9 3.2 Trigger Methods.......................................................................................................................................................... 10 3.2.1 Distributed Detection ............................................................................................................................................... 10 3.2.1.1 PCI Conflict Detection Triggered by Manual Operations ..................................................................................... 11 3.2.1.2 PCI Conflict Detection Based on ANR ................................................................................................................. 12 3.2.1.3 PCI Conflict Detection Based on X2 Messages .................................................................................................... 13 3.2.2 Centralized Detection .............................................................................................................................................. 14 3.2.2.4 Collision and Confusion Detection ....................................................................................................................... 14 3.2.2.5 PCI Mod 3 Detection ............................................................................................................................................ 15

4 PCI Self-Optimization ............................................................................................................... 16 4.1 Overview .................................................................................................................................................................... 16 4.2 Related Concepts ........................................................................................................................................................ 16 4.2.1 First-Order Neighboring Cell ................................................................................................................................... 16 4.2.2 Second-Order Neighboring Cell .............................................................................................................................. 17 4.3 Prioritization of Cells with PCI Conflicts ................................................................................................................... 17 4.4 PCI Re-assignment ..................................................................................................................................................... 18

5 Related Features .......................................................................................................................... 20 6 Network Impact ........................................................................................................................... 21 Issue 01 (2015-06-18)


ii


Contents

7 Engineering Guidelines ............................................................................................................. 22 7.1 When to Use PCI Conflict Detection and Self-Optimization...................................................................................... 22 7.1.1 Distributed PCI Conflict Detection .......................................................................................................................... 22 7.1.2 Centralized PCI Conflict Detection ......................................................................................................................... 23 7.1.3 Centralized PCI Self-Optimization .......................................................................................................................... 24 7.2 Information to Be Collected ....................................................................................................................................... 24 7.3 Network Planning ....................................................................................................................................................... 24 7.3.1 RF Planning ............................................................................................................................................................. 24 7.3.2 Network Topology ................................................................................................................................................... 24 7.3.3 Hardware Planning .................................................................................................................................................. 24 7.4 Deploying PCI Conflict Detection and Self-Optimization ......................................................................................... 25 7.4.1 Deployment Requirements ...................................................................................................................................... 25 7.4.2 Data Preparation ...................................................................................................................................................... 25 7.4.2.1 Distributed PCI Conflict Detection ....................................................................................................................... 26 7.4.2.2 Centralized PCI Conflict Detection ...................................................................................................................... 28 7.4.2.3 PCI Self-Optimization .......................................................................................................................................... 31 7.4.3 Precautions............................................................................................................................................................... 34 7.4.4 Hardware Adjustment .............................................................................................................................................. 34 7.4.5 Activation................................................................................................................................................................. 34 7.4.5.1 Distributed PCI Conflict Detection ....................................................................................................................... 34 7.4.5.2 Centralized PCI Conflict Detection ...................................................................................................................... 39 7.4.5.3 PCI Self-Optimization .......................................................................................................................................... 39 7.4.6 Activation Observation ............................................................................................................................................ 41 7.4.7 Reconfiguration ....................................................................................................................................................... 42 7.4.8 Deactivation ............................................................................................................................................................. 42 7.4.8.4 Distributed PCI Conflict Detection ....................................................................................................................... 42 7.4.8.5 Centralized PCI Conflict Detection ...................................................................................................................... 44 7.4.8.6 Centralized PCI Self-Optimization ....................................................................................................................... 44 7.5 Monitoring .................................................................................................................................................................. 44 7.5.1 Optimization Advice Evaluation .............................................................................................................................. 44 7.5.2 Network KPI Monitoring ......................................................................................................................................... 45 7.6 Parameter Optimization .............................................................................................................................................. 48 7.7 Troubleshooting .......................................................................................................................................................... 50

8 Parameters .................................................................................................................................... 53 9 Counters ........................................................................................................................................ 66 10 Glossary ...................................................................................................................................... 67 11 Reference Documents............................................................................................................... 68

Issue 01 (2015-06-18)


iii


Figures

Figures Figure 2-1 Deployment architecture of PCI conflict detection and self-optimization for SingleSON 5.1 ............ 5 Figure 3-1 PCI collision ........................................................................................................................................ 8 Figure 3-2 PCI confusion – intra-frequency confusion between LTE cells ........................................................... 8 Figure 3-3 PCI confusion – inter-frequency confusion between LTE cells ........................................................... 9 Figure 3-4 PCI confusion – inter-RAT confusion created by LTE cells for a UMTS cell ..................................... 9 Figure 3-5 PCI mod 3 conflicts ........................................................................................................................... 10 Figure 3-6 Proactive PCI conflict detection based on ANR ................................................................................ 12 Figure 3-7 X2 setup signaling procedure ............................................................................................................ 14 Figure 3-8 Signaling procedure for an X2 eNodeB configuration update ........................................................... 14 Figure 7-1 MO search and configuration window ............................................................................................... 37

Issue 01 (2015-06-18)


iv


Tables

Tables Table 2-1 Functions of network components ......................................................................................................... 5 Table 7-1 PCI conflict detection license control item .......................................................................................... 25 Table 7-2 Parameter required for configuring PCI collision detection and PCI confusion detection .................. 26 Table 7-3 Parameter required for generating a PCI conflict alarm ...................................................................... 26 Table 7-4 Parameters required for configuring PCI conflict detection based on X2 messages ........................... 26 Table 7-5 Parameters required for configuring proactive PCI conflict detection based on ANR. ....................... 27 Table 7-6 Engineering parameters ....................................................................................................................... 29 Table 7-7 Reuse distances .................................................................................................................................... 30 Table 7-8 Policy parameters ................................................................................................................................ 30 Table 7-9 Parameters for determining whether a cell is a new cell...................................................................... 32 Table 7-10 Parameters related to PCI self-optimization ...................................................................................... 32 Table 7-11 eNodeB location parameters related to PCI self-optimization ........................................................... 33 Table 7-12 Antenna parameters related to PCI self-optimization ........................................................................ 33 Table 7-13 Parameters related to PCI conflict detection ...................................................................................... 35 Table 7-14 Parameter template for the available PCI range and PCI optimization priority of a cell ................... 39 Table 7-15 Engineering parameter template for PCI self-optimization ............................................................... 40 Table 7-16 Parameters related to PCI conflict detection ...................................................................................... 42 Table 7-17 assistant decision-making information .............................................................................................. 45 Table 7-18 Counters related to the service drop rate ........................................................................................... 46 Table 7-19 UMTS counters to be observed ......................................................................................................... 47 Table 7-20 Counters to be observed .................................................................................................................... 48 Table 7-21 optimization policy parameters .......................................................................................................... 49 Table 7-22 Status of a PCI self-optimization task................................................................................................ 51 Table 8-1 Parameter description .......................................................................................................................... 53

Issue 01 (2015-06-18)


v


1 About This Document

1

About This Document

About This Chapter 1.1 Scope 1.2 Intended Audience 1.3 Change History 1.4 Differences Between eNodeB Types

1.1 Scope This document describes certain features, including their technical principles, related features, network impact, and engineering guidelines. This document covers the following features: LOFD-002007 PCI Conflict Detection and Self-Optimization SNFD-151203 Centralized PCI Self-Optimization - LTE FDD SNFD-151204 Centralized PCI Self-Optimization - LTE TDD This document applies to the following types of eNodeBs. eNodeB Type

Model

Macro

3900 series eNodeB

Micro

BTS3202E

LampSite

DBS3900 LampSite

Any managed objects (MOs), parameters, alarms, or counters described herein correspond to the software release delivered with this document. Any future updates will be described in the product documentation delivered with future software releases. This document applies to LTE FDD and LTE TDD. Any "LTE" in this document refers to LTE FDD or LTE TDD, and "eNodeB" refers to LTE FDD or LTE TDD eNodeB.

Issue 01 (2015-06-18)


1



1.2 Intended Audience This document is intended for personnel who: 

Need to understand the features described herein



Work with Huawei products

1.3 Change History 01 (2015-06-18) This issue is the first commercial release of V100R015C10. Compared with Draft B (2015-05-06) for V100R015C10, this issue does not include any changes.

Draft B (2015-05-06) This is a draft for V100R015C10 Compared with Draft A (2014-12-23) V100R015C10, this issue optimized the description.

Draft A (2014-12-23) This is a draft for V100R015C10 Compared with eRAN8.1, Draft A (2014-12-23) includes the following change: The two features SNFD-151203 Centralized PCI Self-Optimization - LTE FDD and SNFD-151204 Centralized PCI Self-Optimization - LTE TDD have been added in SONMaster V100R015C10 and later

1.4 Differences Between eNodeB Types Feature Support by Macro, Micro, and LampSite eNodeBs Feature ID

Feature Name

Supported by Macro eNodeBs

Supported by Micro eNodeBs

Supported by LampSite eNodeBs

LOFD-002007

PCI Collision Detection & Self-Optimizati on

Yes

Yes

Yes

Function Implementation in Macro, Micro and LampSite eNodeBs Function

Difference

Intra-site

A micro site does not support intra-site neighboring cells. In this

Issue 01 (2015-06-18)


2



Function

Difference

neighboring cell

document, descriptions about intra-site neighboring cells apply only to macro and LampSite sites.

Issue 01 (2015-06-18)


3


2 Overview

2

Overview

About This Chapter 2.1 Introduction 2.2 Benefits 2.3 Architecture

2.1 Introduction There are 504 physical cell identifiers (PCIs) in an LTE network. They are divided into 168 groups and each group consists of three PCIs. PCIs are essential for successful signal synchronization and signal demodulation. Each E-UTRAN cell maps only one PCIWhen excessive E-UTRAN cells exist on the LTE network, multiple E-UTRAN intra-frequency cells inevitably use the same PCI. If PCIs are improperly planned or manually modified, cell frequencies are changed, or neighboring cell parameters are modified, PCIs may conflict between E-UTRAN intra-frequency cells Huawei developed the PCI conflict detection and self-optimization feature, which provides the following functions: 

PCI conflict detection PCI conflict detection is divided into the following types: 

Distributed detection Distributed detection is performed by the eNodeB. Configuration parameters on the eNodeB, such as neighboring cell information, PCIs, and frequencies, change due to manual operations, ANR, or X2 message interaction, causing the eNodeB to perform PCI conflict detection.



Centralized detection Centralized detection is performed by the SONMaster. Based on the obtained NE configuration data, engineering parameter data, and MRs and performance data to which you subscribe, the SONMaster performs PCI conflict detection manually or periodically.



Issue 01 (2015-06-18)

Distributed and centralized detection results are displayed on the SONMaster in a unified way and involved in PCI self-optimization.PCI self-optimization


4


2 Overview

Conflicting cells are re-assigned with proper PCIs based on the detected PCI conflicts combined with the network topology and neighboring cell configuration data. PCI self-optimization supports PCI mod 3, mod 6, and mod 30 optimization.

2.2 Benefits PCI conflict detection and self-optimization provided by Huawei automatically detects PCI conflicts between neighboring cells on the LTE network and assigns proper PCIs to conflicting cells using PCI self-optimization to eliminate or reduce PCI conflicts, thereby reducing service drop rates and improving handover success rates. In addition, this feature optimizes PCI mod 3 conflicts, enhancing the downlink throughput of cells and improving the SINR

2.3 Architecture Figure 2-1Figure 2-1 shows the deployment architecture of PCI conflict detection and self-optimization. Figure 2-1 Deployment architecture of PCI conflict detection and self-optimization for SingleSON 5.1

Table 2-1 lists the functions of network components. Table 2-1 Functions of network components Network Component

Issue 01 (2015-06-18)

Functions Before eRAN8.1

Functions in SingleSON 5. 1 (eRAN8.1)


5


Network Component UE

eNodeB

Functions Before eRAN8.1

The UE reports measurement reports to the eNodeB during PCI conflict detection based on ANR

UEs are not involved in PCI conflict detection triggered by eNodeB configuration changes caused by manual operations or message exchanges over the X2 interface.

UEs are not involved in PCI conflict detection triggered by eNodeB configuration changes caused by manual operations or message exchanges over the X2 interface.

The eNodeB performs distributed PCI conflict detection.

The eNodeB performs distributed PCI conflict detection.

The eNodeB reports conflict information about the detected and resolved PCI conflicts to the U2000.

The eNodeB reports conflict information about the detected and resolved PCI conflicts to the U2000.

The U2000 centrally performs PCI self-optimization. It allocates new PCIs to cells that experience PCI conflicts and sends the PCIs to eNodeBs. You can observe PCI conflict alarms in the alarm console

SONMaste

Functions in SingleSON 5. 1 (eRAN8.1)

The UE reports measurement reports to the eNodeB during PCI conflict detection based on ANR

The eNodeB reports the conflict alarm information to the alarm console.

U2000

2 Overview

None

The eNodeB reports the conflict alarm information to the alarm console.

The U2000 does not perform PCI self-optimization. It functions as a channel to report conflict information reported by the eNodeB to the SONMaster and deliver the optimization advice generated by the SONMaster to the eNodeB. You can observe PCI conflict alarms in the alarm console



The SONMaster implements the centralized PCI detection algorithm, comprehensively displays PCI conflict information reported by the eNodeB to users, and is involved in PCI self-optimization 

The U2000 implements the centralized PCI self-optimization algorithm, assigns new PCIs to cells that experience PCI conflicts, and sends the PCIs to the eNodeB through the U2000

Issue 01 (2015-06-18)


6


3 PCI Conflict Detection

3

PCI Conflict Detection

About This Chapter This chapter describes PCI conflict detection principles, including PCI conflict types and trigger methods of PCI conflict detection. For details about how to perform PCI conflict detection, see 8 Engineering Guidelines. 3.1 PCI Conflict Types 3.2 Trigger Methods

3.1 PCI Conflict Types PCI conflicts involved in this feature are classified into the PCI collision, PCI confusion, and PCI mod 3 conflict .

3.1.1 PCI Collision A PCI collision occurs between two intra-frequency cells that use an identical PCI but are insufficiently isolated. In this case, UEs in the overlapping area of the two cells cannot implement signal synchronization or decoding. Figure 3-1 shows a PCI collision between cell A and cell B.

Issue 01 (2015-06-18)


7



Figure 3-1 PCI collision

If a cell has the same frequency and PCI as one of its neighboring cells, there is a PCI collision between the cell and the neighboring cell. An LTE cell is not allowed to have the same frequency and PCI as its neighboring cell. However, an LTE cell can have the same frequency and PCI as its external cell or multiple local cells under an eNodeB have the same frequency and PCI. A cell has a unique center frequency but may have multiple E-UTRA Absolute Radio Frequency Channel Numbers (EARFCNs). For example, the frequency 2110 MHz corresponds to EARFCN 1950 at band4 and EARFCN 4150 at band10. Intra-frequency cells referred in this document mean the cells with the same center frequency.

3.1.2 PCI Confusion A PCI confusion occurs between a detected cell and a neighboring cell if the two cells have the same frequency and PCI and if the reference signal received power (RSRP) of the two cells reaches the handover threshold. The PCI confusion may lead to UE handover failures or service drops. The PCI confusion occurs in the following scenarios:: 1)

Intra-frequency confusion between LTE cells, as shown in Figure 3-2

Figure 3-2 PCI confusion – intra-frequency confusion between LTE cells

LTE Cell A F1,PCI=1

LTE Cell C F1,PCI=2

LTE Cell B F1,PCI=1

UE

In this scenario, cells A, B, and C are LTE cells with the same downlink frequency. Cells A and B have the same PCI. Therefore, cells A and B create confusion for cell C

According to LTE neighboring cell configuration principles, the frequency and PCI of cell C must not be the same as those of cell A or cell B. Otherwise, cell A or cell B cannot be added to the NCL of cell CLTE

Issue 01 (2015-06-18)


8


2)


Inter-frequency confusion between LTE cells, as shown in Figure 3-3

Figure 3-3 PCI confusion – inter-frequency confusion between LTE cells

LTE Cell A F1,PCI=1

LTE Cell B F1,PCI=1

LTE Cell C F2,PCI=2 UE

In this scenario, cells A, B, and C are LTE cells. Cells A and B have the same frequency and PCI and are inter-frequency neighboring cells of cell C. Therefore, cells A and B create confusion for cell C. 3) 3-4

Inter-RAT confusion created by LTE cells for a UMTS cell, as shown in Figure 3-4Figure

Figure 3-4 PCI confusion – inter-RAT confusion created by LTE cells for a UMTS cell

LTE Cell A F1,PCI=1

LTE Cell B F1,PCI=1

UE

UMTS Cell C F2,SC=2

In this scenario, two LTE cells create PCI confusion for the UMTS cell, thereby affecting the handover of the UMTS cell.

According to RNC configuration principles, two LTE cells with the same frequency and PCI must not be added to the NCL of the UMTS cell. Therefore, you can add only cell A or cell B to the NCL of cell C. 4)

Inter-RAT confusion created by LTE cells for a GSM cell

The principle diagram for LTE is the same as that for UMTS. LTE-to-GSM handovers seldom occur on the network. Therefore, LTE-to-GSM confusion is seldom created and is not considered in this version temporarily

3.1.3 PCI Mod 3 Interference On the LTE network, if PCIs of two neighboring cells are different and the mod 3 remainders are the same, this constructs the PCI mod 3 interference, as shown in Figure 3-5.

Issue 01 (2015-06-18)


9



Figure 3-5 PCI mod 3 conflicts

LTE Cell A F1,PCI=1

LTE Cell B F1,PCI=4

LTE Cell C F1,PCI=5

As shown in the preceding figure, cells A, B, and C have the same frequency but different PCIs. The PCI mod 3 remainders for cells A and B are 1, which constructs the PCI mod 3 interference. If a cell is in dual antenna mode, the carriers transmitted in the reference signal

will

generate intra-frequency interference, thereby decreasing the SINR. (Note: If cells are in single antenna mode and the PCI mod 6 remainders are the same, the carriers transmitted in the reference signal will generate intra-frequency interference, thereby decreasing the SINR.) According to the research results of PCI mod 3 conflicts on the network, the PCI mod 3 conflicts have the following impact on the user SINR and throughput:  The SINR decreases most when the cell has no load and decreases less when the network load grows. The PCI mod 3 conflicts have little impact on user throughput.  In highly-loaded scenarios, the PCI mod 3 conflicts bring insignificant impact and are not the main cause of interference problems. Therefore, the PCI mod 3 conflicts in the case of certain load need to be considered.

3.2 Trigger Methods 3.2.1 Distributed Detection PCI conflict detection is classified into PCI collision detection and PCI confusion detection that are controlled by COLLISION_DETECT_SWITCH and CONFUSION_DETECT_SWITCH of ENodeBAlgoSwitch.PciConflictDetectSwitch, respectively. 

If COLLISION_DETECT_SWITCH of ENodeBAlgoSwitch.PciConflictDetectSwitch is selected, the eNodeB detects PCI collision.



If COLLISION_DETECT_SWITCH of ENodeBAlgoSwitch.PciConflictDetectSwitch is deselected, the eNodeB does not detect PCI collision.



If CONFUSION_DETECT_SWITCH of ENodeBAlgoSwitch.PciConflictDetectSwitch is selected, the eNodeB detects PCI confusion.



If CONFUSION_DETECT_SWITCH of ENodeBAlgoSwitch.PciConflictDetectSwitch is deselected, the eNodeB does not detect PCI confusion.

Issue 01 (2015-06-18)


10



The eNodeB performs distributed PCI conflict detection if the following parameters related to PCI conflicts change: 

The PCI or frequency of an eNodeB's local cell is changed.



The PCI or frequency of an external E-UTRAN cell is changed, or an external E-UTRAN cell is added or removed.



A neighboring cell is added to or removed from the intra-frequency or inter-frequency NRT.

The preceding PCI conflict detection can be triggered using the following methods: 

Manual parameter modifications The eNodeB triggers PCI conflict detection when eNodeB parameters are manually modified.



ANR change The eNodeB triggers PCI conflict detection when a neighboring cell is automatically added to or removed from the ANR, or a neighboring cell PCI is updated.



Information in X2 messages The eNodeB triggers PCI conflict detection when it receives X2 messages and updates neighboring cell parameters based on the peer cell information in X2 messages. This type of PCI conflict detection can be triggered only if the X2 interface is configured between eNodeBs and GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is set to ON(On).

If the eNodeB detects a PCI conflict, it reports the PCI conflict information to the SONMaster and this information will be updated in the PCI Optimization Task window on the SONMaster. In addition, ENodeBAlgoSwitch.PciConflictAlmSwitch controls whether the eNodeB reports ALM-29247 Cell PCI Conflict to the U2000 and LMT if any PCI conflict is detected. For details about NCLs and NRTs, see ANR Management Feature Parameter Description of the corresponding eRAN version. If the CME is deployed and operators need to change the eNodeB parameters using the CME, set GlobalProcSwitch.X2BasedUptENodeBCfgSwitch to OFF(Off) to prevent configuration data loss. This is because when the configuration (such as the PCI or frequency) of an eNodeB is changed on the CME, the CME will update the eNodeB parameters in the NCL. This update triggers the eNodeB to detect PCI conflicts.

3.2.1.1 PCI Conflict Detection Triggered by Manual Operations The eNodeB detects PCI conflicts when its parameters are changed manually as follows: 

If the PCI or frequency of an eNodeB's local cell is changed, the eNodeB checks for PCI collisions between the local cells or between the local cell and the neighboring cell configured in the NCL.



If a cell is added to or removed from an NCL or NRT of the eNodeB, or if the PCI or frequency of a neighboring cell is changed, the eNodeB checks for PCI collisions between the local cell and the cells on the NCL or checks for PCI confusions between the neighboring cells of the local cell. The eNodeB checks only the neighboring cells contained in the NCL and NRTs, not other cells.

Issue 01 (2015-06-18)


11



3.2.1.2 PCI Conflict Detection Based on ANR ANR is a self-optimization function. It automatically ensures complete and correct neighbor relations and therefore helps reduce abnormal handovers and improve network performance. This section describes two methods for PCI conflict detection based on ANR.

PCI Conflict Detection Triggered by Intra-RAT ANR PCI conflict detection will be triggered after the eNodeB uses the intra-RAT ANR function (event-triggered ANR or fast ANR) to detect and add missing neighboring cells. The intra-RAT event-triggered ANR and intra-RAT fast ANR functions are controlled by the switches IntraRatEventAnrSwitch and IntraRatFastAnrSwitch under the ENodeBAlgoSwitch.AnrSwitch parameter, respectively. For details about the detecting and adding of missing neighboring cells by intra-RAT event-triggered ANR or intra-RAT fast ANR, see ANR Management Feature Parameter Description of the corresponding eRAN version.

Proactive PCI Conflict Detection Based on ANR Proactive PCI conflict detection is used to detect PCI confusion between configured and unconfigured neighboring cells. This function depends on the feature LOFD-002001 Automatic Neighbor Relation (ANR). Therefore, ensure that intra-RAT event-triggered ANR or intra-RAT fast ANR has been enabled before enabling proactive PCI conflict detection. For details about ANR, see ANR Management Feature Parameter Description of the corresponding eRAN version.

Proactive PCI conflict detection based on ANR is controlled by the ANR.ActivePCIConflictSwitch parameter. After this switch is turned on, the eNodeB proactively checks for PCI conflicts over the period specified by ANR.StartTime and ANR.StopTime. Figure 3-6 shows the procedure for proactive PCI conflict detection based on ANR. Figure 3-6 Proactive PCI conflict detection based on ANR

In a detection period, the procedure for proactive PCI conflict detection based on ANR is as follows:

Issue 01 (2015-06-18)


12


1.


The eNodeB chooses non-VoIP and non-CA UEs that support ANR and initially access the network. Then, the eNodeB sends measurement configurations related to events A3 and A4, requesting the UEs to measure all E-UTRAN frequencies configured on the eNodeB. 

Events A3 and A4 used in proactive PCI conflict detection are more easily triggered than those used in handovers.



When a UE sets up a bearer with the QoS class identifier (QCI) of 1 after the eNodeB triggers a proactive PCI conflict detection for the UE: If GlobalProcSwitch.VoipWithGapMode is set to ENABLE, the eNodeB does not remove the proactive PCI conflict detection result of the UE. If GlobalProcSwitch.VoipWithGapMode is set to DISABLE, the eNodeB delivers the RRC Connection Reconfiguration message to the UE and removes the proactive PCI conflict detection result of the UE.

2.

Each of the chosen UEs reports information about the neighboring cell with the highest priority to the eNodeB of the serving cell. This priority is determined by the RSRP and cell individual offset (CIO). The following steps use one UE as an example.

3.

The eNodeB sends a measurement configuration to the UE based on the received measurement report, requesting the UE to report the parameters of this best neighboring cell. These parameters include the ECGI, tracking area code (TAC), and public land mobile network (PLMN) ID list.

4.

The UE reports these parameters to the eNodeB.

5.

The eNodeB performs the following operations: −

If the ECGI of this best neighboring cell differs from the ECGI of the configured best neighboring cell of the serving cell, the eNodeB adds the neighbor relation between the serving cell and this best neighboring cell to the NRT based on the measured PCI, ECGI, and frequency. Then, the eNodeB starts PCI conflict detection.

−

If the ECGI of this best neighboring cell equals the ECGI of the configured best neighboring cell of the serving cell but the corresponding PCI is different from the configured one, the eNodeB updates the PCIs in the NCL and then starts PCI conflict detection.

If the serving cell has multiple neighboring cells with the same frequency and PCI but different ECGIs, the eNodeB can detect PCI conflicts.

3.2.1.3 PCI Conflict Detection Based on X2 Messages If an X2 interface is set up or an eNodeB parameter changes after the X2 interface is set up, the eNodeBs involved are notified through the X2 interfaces. During the setup of an X2 interface, the source eNodeB sends an X2 Setup Request message to the target eNodeB. If the request is acceptable, the target eNodeB sends an X2 Setup Response message to the source eNodeB. Figure 3-7 shows the X2 setup signaling procedure.

Issue 01 (2015-06-18)


13



Figure 3-7 X2 setup signaling procedure

After the X2 interface is set up, the source eNodeB sends an X2 eNodeB Configuration Update message to the target eNodeB if the X2-related configuration, such as serving cell PCI, TAC, and neighboring cells, of the source eNodeB changes. Figure 3-8 shows the signaling procedure for an X2 eNodeB configuration update. Figure 3-8 Signaling procedure for an X2 eNodeB configuration update

As shown in Figure 3-7 and Figure 3-8 when an eNodeB receives an X2 message (X2 Setup Request, X2 Setup Response, or X2 eNodeB Configuration Update) from the peer eNodeB, it updates corresponding parameters in the NCL for the cells under the peer eNodeB, adds cells to or removes cells from the NCL, or adds neighbor relation to or removes neighbor relation from the NRT based on the message. This will trigger PCI conflict detection For details about updating external cells or neighboring cells based on X2 messages, see ANR Management Feature Parameter Description of the corresponding eRAN version.

3.2.2 Centralized Detection Centralized PCI conflict detection is performed by creating a task on the SONMaster. The detection starts upon task start and stops upon task stop. After the centralized task starts, the SONMaster detects PCI collision, PCI confusion, and PCI mod 3 conflicts using the distance- and neighboring-cell-based methods.

3.2.2.4 Collision and Confusion Detection The SONMaster detects conflicts based on the neighbor relationships and topology distance 

Issue 01 (2015-06-18)

The SONMaster performs collision detection by detecting local cells and external cells because direct neighbor relationships do not exist, and considers the reuse distance of cells.


14





The SONMaster constructs second-order neighboring cells based on the cell to be detected and detects confusion conflicts among the second-order neighboring cells .

3.2.2.5 PCI Mod 3 Detection PCI mod 3 detection is based on the UE intra-frequency MRs. The SONMaster performs PCI mod 3 detection based on the collected intra-frequency MRs and cell load information PCI mod 3 detection determines mod 3 conflicts from the interference perspective. Only the PCI mod 3 conflicts that bring high interference between cells need to be optimized. The detection process is described as follows: 1. The SONMaster checks the interference between cells, performs PCI mod 3 detection on neighboring cells with high interference, and then evaluates the load status of the source cell, PCI mod 3 conflicts have the greatest impact on a cell when the cell load is low. 2. After calculating the average load during busy hours, the SONMaster evaluates whether PCI mod 3 conflicts between cells need to be resolved, If related requirements are met, the SONMaster outputs the conflict information. Otherwise, the SONMaster determines that the interference of the cell is not caused by PCI mod 3 conflicts and thereby PCI mod 3 problems can be left temporarily. You can perform the following operations on tasks: 

Add a task

You can create a PCI conflict detection and self-optimization task on the SONMaster. During the creation, you need to set basic task parameters and optimization parameters, and select optimization objects 

Basic task parameters: include the task name, type, start policy, and stop policy.



Optimization parameters: indicate the parameters that are strongly related to detection and reallocation algorithms, such as the optimization period, conflict detection type, and interference and load thresholds for mod 3 detection



Optimization objects: indicate the cells involved in detection and self-optimization ,One cell can only be involved in one task for conflict detection and self-optimization.

 

Modify a task

You can reconfigure parameters, policies, and optimization objects of a configured optimization task. This enables the reconfigured optimization task to better determine and optimize PCI conflicts on the network. 

Delete a task

You can delete a stopped task. 

Stop a task

You can stop an optimization task using the following methods: 

Manual: You can manually stop an optimization task on the SONMaster.



Execution times: A periodic optimization task automatically stops after being executed for specified times.



Scheduled: An optimization task automatically stops when the preset time expires

Issue 01 (2015-06-18)


15


4 PCI Self-Optimization

4

PCI Self-Optimization

About This Chapter 4.1 Overview 4.2 Related Concepts 4.3 Prioritization of Cells with PCI Conflicts 4.4 PCI Re-assignment

4.1 Overview For distributed detection, the eNodeB reports PCI conflict information to the SONMaster after detecting PCI conflicts. After receiving distributed detection results, the SONMaster combines them with centralized detection results, performs centralized PCI self-optimization, and assigns conflicting cells with proper PCIs. PCI self-optimization results take effect only when they are delivered to the eNodeB PCI self-optimization is also supported in scenarios where some network element (NE) engineering parameters are not configured or the cells use compressed bandwidth. These parameters include longitude, latitude, azimuth, and beamwidth. Micro eNodeBs do not support the compressed bandwidth mode.

4.2 Related Concepts 4.2.1 First-Order Neighboring Cell Each eNodeB stores an NCL and NRTs. The NRTs contain information about the neighboring cells of the local cells of this eNodeB. These neighboring cells are the first-order neighboring cells. These cells may be intra-frequency, inter-frequency, or inter-RAT neighboring cells. RAT is short for radio access technology. For details about NCLs and NRTs, see ANR Management Feature Parameter Description of the corresponding eRAN version.

Issue 01 (2015-06-18)


16



4.2.2 Second-Order Neighboring Cell The first-order neighboring cells of the first-order neighboring cells of a cell are the second-order neighboring cells of this cell. Assume that cell B is a first-order neighboring cell of cell A and cell C is a first-order neighboring cell of cell B. Then, cell C is a second-order neighboring cell of cell A.

4.3 Prioritization of Cells with PCI Conflicts Prioritization Rules If multiple cells experience PCI conflicts, the SONMaster adheres to the following prioritization rules to prioritize the conflicting cells and then selects the cells for PCI optimization in descending order. 1.

Prioritizes cells with higher optimization priorities specified by users. The optimization priority of an LTE cell can be specified on the SONMaster as High priority, Low priority, or Locked. During PCI self-optimization, conflicting cells with a high priority are assigned with new PCIs in precedence. A conflicting cell whose priority is Locked will not be assigned with a new PCI.

2.

Prioritizes cells experiencing the most frequent PCI conflicts with other cells. Changing the PCI of a cell experiencing the most frequent PCI conflicts improves the PCI optimization efficiency. If multiple conflicting cells have the same optimization priority, the cell that experiences the most frequent PCI conflicts is preferentially optimized.

3.

Prioritizes cells that are newly deployed or cells whose PCIs are recently changed. This is because: −

The probability of data errors for these cells is high.

−

Changing the PCI of a cell involved in network reconfiguration has a minor impact on the live network.

If multiple conflicting cells have the same optimization priority and experience the same PCI conflict level, newly deployed cells or cells whose PCIs are recently changed are preferentially optimized. 4.

Prioritizes micro cells. A new PCI takes effect after it is delivered to the eNodeB. This PCI delivery blocks the cell under the eNodeB, thereby interrupting services. Changing the PCI of a micro cell has a minor impact on the live network because a micro cell usually covers a small area. If multiple conflicting cells have the same optimization priority, experience the same PCI conflict level, and have the same PCI modification property (cells are deployed recently or their PCIs are changed recently or neither), micro cells are preferentially optimized.

5.

Prioritizes cells that have a small number of neighboring cells. Blocking a cell with few neighboring cells has a minor impact on the live network. If multiple conflicting cells of the same type have the same optimization priority, experience the same PCI conflict level, and have the same PCI modification property, cells that have a small number of neighboring cells are preferentially optimized.

Issue 01 (2015-06-18)


17



Related Parameters The OldCellThreshold Value parameter determines whether a cell is newly deployed or its PCI is recently changed. A cell whose PCI change time is earlier than the current time by a value less than the value of the OldCellThreshold Value parameter is considered as a new cell. Otherwise, the cell is considered as an old cell, which is not prioritized by either the cell deployment time or the PCI change time. The OldCellThreshold Value parameter is set to 0 by default. That is, all cells are considered as old cells. If the interval between the PCI change time for two cells is less than the value of the SameBatchInterval Value parameter, the two cells are considered as being changed in the same batch. In this situation, the two cells have the same priority in terms of PCI change time.

4.4 PCI Re-assignment PCI re-assignment adheres to the following principles: For simplicity, the following uses "new PCI" to represent a PCI to be allocated to a conflicting cell. 

A new PCI must be different from the PCI of any first-order or second-order intra-frequency neighboring cell of the conflicting cell.



A new PCI must be different from the PCI of any intra-frequency neighboring cell in the NCL of the conflicting cell.



A new PCI must be different from the PCI of any cells under the same eNodeB as the conflicting cell.



If the blacklist is considered: −

A new PCI must be different from the PCI of any blacklisted intra-frequency E-UTRAN cell of the conflicting cell.

−

If the conflicting cell is not in the intra-frequency E-UTRAN cell blacklist of any of its first-order neighboring cells, the new PCI must not be within the range specified by IntraFreqBlkCell.PhyCellIdRange.

−

If the conflicting cell is not in the inter-frequency E-UTRAN cell blacklist of any of its first-order neighboring cells, and there is a cell with the same frequency as the conflicting cell in the inter-frequency E-UTRAN cell blacklist, the new PCI must not be within the range specified by InterFreqBlkCell.PhyCellIdRange.

The UE does not report the blacklisted cells so that the previously detected conflicting cells are still detectable after PCI self-optimization. 

New PCIs must be within the available PCI range of the cell, and this PCI range is set on the SONMaster

In addition, PCI self-optimization considers the following factors: 

Positions of physical resource blocks (PRBs) occupied by the physical HARQ indicator channel (PHICH) and physical control format indicator channel (PCFICH) If the conflicting cell uses compressed bandwidth, the SONMaster avoids allocating some restricted PCIs to the conflicting cell. This prevents the PHICH and PCFICH from being allocated nonexistent PRBs.



Issue 01 (2015-06-18)

Primary synchronization codes


18



Three cells with adjacent azimuths under an eNodeB or a virtual eNodeB have different primary synchronization codes. That is, PCI mod 3 of these cells are different. Cells with adjacent azimuths under an eNodeB or a virtual eNodeB have different primary synchronization codes. That is, PCI mod 3 of these cells are different. In remote RRU mode, cells under the same eNodeB may be far away from each other. In this situation, cells that are closely located under the same eNodeB are considered as being under a virtual eNodeB. 

Frequency-domain positions of downlink reference signals If downlink reference signals are transmitted on the same frequency-domain position in neighboring cells, the quality of these signals is poor when the network load is low. To separate these signals, the SONMaster allocates the most appropriate PCI to the conflicting cell if required engineering parameters are configured.



Uplink reference signal (UL RS) sequence group number Adjacent cells have different UL RS sequence group numbers. UL RS sequence group numbers are related to PCI mod 30. For details, see section 5.5 Reference signals in 3GPP TS 36.211 V9.1.0.



Distance between cells with the same PCI If the new PCI is the same as the PCI of another cell, the two cells must be as far apart as possible, with as many eNodeBs as possible between the two cells.

If the conflicting cell is not allocated a new PCI in a self-optimization period, this cell still uses the old PCI, and the SONMaster does not display this PCI as a suggested PCI.

Issue 01 (2015-06-18)


19


5 Related Features

5

Related Features

Prerequisite Features LOFD-002007 PCI Conflict Detection and Self-Optimization requires OSS features SNFD-151203 Centralized PCI Self-Optimization - LTE FDD and SNFD-151204 Centralized PCI Self-Optimization - LTE TDD. PCI conflict detection based on ANR on the eNodeB requires LOFD-002001 Automatic Neighbour Relation (ANR). The eNodeB updates the configuration based on X2 messages and triggers PCI conflict detection only when GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is turned on Other PCI conflict detections and PCI self-optimization do not require any features.

Mutually Exclusive Features None

Impacted Features None

Issue 01 (2015-06-18)


20


6 Network Impact

6

Network Impact

System Capacity PCI conflict detection based on ANR affects system capacity. To obtain ECGIs, a UE in connected mode needs to work in discontinuous reception (DRX) mode. A UE in DRX mode cannot perform any services. This decreases uplink and downlink throughput. PCI self-optimization has no adverse impact on system capacity. Delivering PCI optimization suggestions will deactivate and then reactivate this cell, during which time, the number of online subscribers is reduced.

Network Performance During PCI conflict detection, eNodeB operations including delivering and processing measurement information occupies CPU and memory resources, thereby consuming excessive system resources. During PCI mod 3 conflict detection, the eNodeB triggers the UE to initiate intra-frequency measurements. This increases the power consumption of the UE. In addition, the CPU and memory resource consumption of the eNodeB increases accordingly. After you deliver optimization advice on modifying cell PCIs, the function of migrating online UEs is triggered before optimization completion. The eNodeB migrates cell edge UEs to adjacent cells gradually. The process may result in call drops of UEs, thereby affecting user experience. Once PCI self-optimization is complete, the eNodeB delivers a new PCI to the conflicting cell, which deactivates and then reactivates the cell to make the new PCI take effect. This process disables the cell for a period of time. This process affects UE access, normal services, and handovers, thereby decreasing access and handover success rates. In open-loop mode, before executing advice to modify the PCI of a cell, you can block the cell to prevent UEs from reaccessing the cell. After the PCI of the cell is modified, you need to unblock the cell to ensure that UEs access the cell. PCI self-optimization can reduce or eliminate PCI conflicts between a cell and its neighboring cells and between the neighboring cells of a cell. This reduces service drop rates and increases handover success rates. After a cell PCI is changed, the cell is automatically deactivated and then reactivated.

Issue 01 (2015-06-18)


21


7

7 Engineering Guidelines

Engineering Guidelines

About This Chapter 8.1 When to Use PCI Conflict Detection and Self-Optimization 8.2 Information to Be Collected 8.3 Network Planning 8.4 Deploying PCI Conflict Detection and Self-Optimization 8.5 Monitoring 8.6 Parameter Optimization 8.7 Troubleshooting

7.1 When to Use PCI Conflict Detection and Self-Optimization 7.1.1 Distributed PCI Conflict Detection It is recommended that PCI collision detection be enabled in non-RRU scenarios. PCI confusion detection can be enabled in all scenarios. PCI conflict detections can be categorized according to trigger methods. The policies for enabling these detections are as follows: 

PCI conflict detection based on manual modifications After PCI collision detection or PCI confusion detection is enabled, the eNodeB will trigger detection if parameters are manually modified. For details, see 3.2.1 PCI Conflict Detection Triggered by Manual Operations.



PCI conflict detection based on ANR −

PCI conflict detection based on intra-RAT ANR This function requires intra-RAT ANR. The policy for enabling this detection is the same as that for enabling intra-RAT ANR. For details about the policy for enabling intra-RAT ANR, see ANR Management Feature Parameter Description of the corresponding eRAN version.

Issue 01 (2015-06-18)


22

LTE PCI Self-Optimization Feature Description −


Proactive PCI conflict detection based on ANR In multi-vendor or multi-U2000 scenarios, it is recommended that this function be enabled for cells that experience high service drop rates or low outgoing handover success rates when serving a large number of UEs. Do not enable this function in other scenarios.

Proactive PCI conflict detection based on ANR does not need to be enabled if all eNodeBs in the network are managed by the same U2000. This is because an eNodeB can add conflicting cells to its NRT using intra-RAT event-triggered ANR based on UE historical information, thereby triggering PCI conflict detection. PCI conflicts can be detected easier when a large number of UEs camp on the LTE network. This is because the number of UE at the cell edge increases in this situation. It is recommended that proactive PCI conflict detection be enabled to update network-level parameters if the configuration parameters, such as PCI, change frequently and no X2 interface is configured in the network. 

PCI conflict detection based on X2 messages Changes in neighbor relationships and PCIs of neighboring cells will trigger PCI conflict detection, and the change information is sent over the X2 interfaces only if GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is set to ON(On) or eNodeB configuration parameters are modified using the CME. If the CME is not deployed or if users do not know how to use the CME to modify the network-level parameter settings, set GlobalProcSwitch.X2BasedUptENodeBCfgSwitch to ON(On) for each cell on the network. If the CME is deployed, set GlobalProcSwitch.X2BasedUptENodeBCfgSwitch to OFF(Off) for each cell on the network before using the CME to change the network-level parameter settings.

7.1.2 Centralized PCI Conflict Detection You are advised to create the centralized PCI conflict detection and optimization task with the centralized PCI conflict detection function enabled on the SONMaster and enable the task to run periodically. The execution period is configured based on the network change frequency and customer requirements. The default value is one day. If the network change frequency is low, neighbor relationships are relatively stable, and engineering parameters are basically stable, you can set the execution period of the optimization task to a larger value, for example, one week or month. Optimization objects are configured based on site requirements and can be on the entire network or within a specified area. Detection in the following scenarios can be emphasized: 

Initial network deployment



Site deployment or capacity expansion



High service drop rate and low handover success rate



Frequent neighbor relationship changes



High interference but low load (PCI mod 3 conflicts)

You can set the execution period to one day for PCI conflict detection in the preceding scenarios

Issue 01 (2015-06-18)


23



7.1.3 Centralized PCI Self-Optimization PCI self-optimization is performed on the SONMaster. The SONMaster assigns new PCIs to conflicting cells based on the detected PCI conflict information on the network.The SONMaster starts PCI self-optimization only when a PCI self-optimization task is created on the SONMaster. PCI conflicts on the network can be reduced or eliminated only when optimized PCIs are delivered to the corresponding eNodeB, herefore, you are advised to enable PCI self-optimization. The delivery of PCI modification advice on the SONMaster automatically deactivates cells. Therefore, you are advised to set the PCI delivery duration within off-peak hours. The network parameter settings may be changed frequently during the initial phase of network deployment. Therefore, it is recommended that PCI optimization suggestions be delivered immediately after the PCI self-optimization task is complete. If the PCI optimization suggestions are delivered too late after the PCI self-optimization task is complete, these suggestions may not be suitable for the network because the network-level parameters have altered. Before manually starting a PCI self-optimization task, you can view the PCI conflict information on the SONMaster. If the information is not frequently updated, you can start the PCI self-optimization task. Note that the U2000 should not deliver PCIs during a PCI self-optimization process.

7.2 Information to Be Collected N/A

7.3 Network Planning 7.3.1 RF Planning N/A

7.3.2 Network Topology N/A

7.3.3 Hardware Planning N/A

Issue 01 (2015-06-18)


24



7.4 Deploying PCI Conflict Detection and Self-Optimization 7.4.1 Deployment Requirements PCI Conflict Detection 

Operators must purchase and activate the license listed in Table 7-1.

Table 7-1 PCI conflict detection license control item Feature ID

Feature Name

License Control Item

NE

Sales Unit

LOFD-002007

PCI Collision Detection & Self-Optimizatio n (FDD)

PCI Collision Detection & Self-Optimiza tion (FDD)

eNodeB

per cell

SNFD-151203

Centralized PCI Self-Optimizatio n - LTE FDD

Centralized PCI Self-Optimiza tion - LTE FDD

SONM aster

Per cell

Centralized PCI Self-Optimizatio n - LTE TDD

Centralized PCI Self-Optimiza tion - LTE TDD

SONM aster

SNFD-151204

Per cell



If the license of LOFD-002007 is not activated, the eNodeB does not perform PCI conflict detection and deliver PCI conflict information to the SONMaster



If the license of SNFD-151203 or SNFD-151204 is not activated, you cannot create PCI conflict detection and self-optimization tasks, manage distributed and centralized PCI detection, and trigger PCI self-optimization on the SONMaster.

Active PCI conflict detection based on ANR on the eNodeB requires that UEs support intraand inter-frequency ANR-related measurements and also support DRX.Either intra-RAT event-triggered ANR or intra-RAT fast ANR is activated on the eNodeB

PCI Self-Optimization SONMaster V100R015C10 or later is used.

7.4.2 Data Preparation This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario. There are three types of data sources:

Issue 01 (2015-06-18)


25





Network plan (negotiation required): parameter values planned by the operator and negotiated with the EPC or peer transmission equipment



Network plan (negotiation not required): parameter values planned and set by the operator



User-defined: parameter values set by users

7.4.2.1 Distributed PCI Conflict Detection 

Table 7-2 lists the parameter required for configuring PCI collision detection and PCI confusion detection.

Table 7-2 Parameter required for configuring PCI collision detection and PCI confusion detection Parameter Name

Parameter ID

Data Source

Setting Notes

PCI Conflict Detect Switch

ENodeBAlgoSwit ch.PciConflictDete ctSwitch

User-define d



In non-RRU scenarios, select COLLISION_DETECT_SWI TCH and CONFUSION_DETECT_SW ITCH.



In RRU scenarios, select only CONFUSION_DETECT_SW ITCH.



(Optional) Table 7-3 lists the parameter for generating a PCI conflict alarm. If PCI conflict detection and self-optimization is deployed, you can view PCI conflict information on the PCI conflict self-optimization page on the SONMaster. You are advised to set the PciConflictAlmSwitch parameter to OFF(Off) If PCI conflict detection and self-optimization is not deployed, you are advised to set the PciConflictAlmSwitch parameter to ON(On) to view PCI conflict information in the alarm console.

Table 7-3 Parameter required for generating a PCI conflict alarm Parameter Name

Parameter ID

Data Source

Setting Notes

PCI conflict alarm switch

ENodeBAlgoSwitc h.PciConflictAlmSw itch

User-defined

If this parameter is set to ON(On), the eNodeB reports a PCI conflict alarm to the U2000 alarm console when a PCI conflict is detected.



PCI conflict detection triggered by eNodeB parameter adjustment N/A



Table 7-4 lists the parameters required for configuring PCI conflict detection based on X2 messages.

Table 7-4 Parameters required for configuring PCI conflict detection based on X2 messages Parameter Name

Issue 01 (2015-06-18)

Parameter ID

Data Source

Setting Notes


26



Parameter Name

Parameter ID

Data Source

Setting Notes

Update eNB Configuration Via X2 Switch

GlobalProcSwitch .X2BasedUptENod eBCfgSwitch

User-def ined



If the CME is not deployed or if users do not know how to use the CME to modify the network-level parameter settings, set GlobalProcSwitch.X2BasedUptE NodeBCfgSwitch to ON(On) for each cell on the network.



If the CME is deployed, set GlobalProcSwitch.X2BasedUptE NodeBCfgSwitch to OFF(Off)for each cell on the network before using the CME to change the network-level parameter settings.



Table 7-5 lists the parameters required for configuring proactive PCI conflict detection based on ANR.

Table 7-5 Parameters required for configuring proactive PCI conflict detection based on ANR. Parameter Name

Parameter ID

Data Source

Setting Notes

ANR Active PCI Conflict Detection Switch

ANR.ActivePCICon flictSwitch

User-defined

If this parameter is set to ON(On) in the period when proactive PCI conflict detection based on ANR is enabled, proactive PCI conflict detection based on ANR is enabled. If this parameter is set to OFF(Off), proactive PCI conflict detection based on ANR is disabled or stopped. It is recommended that this parameter be set to ON(On) for cells that experience high service drop rates or low outgoing handover success rates.

Start time

Issue 01 (2015-06-18)

ANR.StartTime

User-defined


This parameter specifies the start time of proactive PCI conflict detection based on 27


Parameter Name

Parameter ID


Data Source

Setting Notes ANR. If ANR.ActivePCICon flictSwitch is set to ON(On), proactive PCI conflict detection based on ANR is started at the time specified by this parameter. It is recommended that this parameter be set to the time when many UEs camp on the network. This is because PCI conflict is easier to detect at that time.

Stop time

ANR.StopTime

User-defined

This parameter specifies the stop time of proactive PCI conflict detection based on ANR. If ANR.ActivePCICon flictSwitch is set to ON(On), proactive PCI conflict detection based on ANR is stopped at the time specified by this parameter. This parameter is used with StartTime. It is recommended that proactive PCI conflict detection based on ANR be enabled when many UEs camp on the network.

7.4.2.2 Centralized PCI Conflict Detection You need to prepare the following data for centralized PCI conflict detection 1) Engineering parameters Engineering parameters, such as the cell longitude and latitude information, must be configured for cells involved in PCI detection and self-optimization. Table 7-6 describes the engineering parameters for LTE cells

Issue 01 (2015-06-18)


28



Table 7-6 Engineering parameters Parameter

Description

Value

Mcc

Mobile country code

An integer ranging from 0 to 999

Mnc

Mobile network code


eNodeBId

BS ID


CellId

Cell ID


Longitude

Cell longitude

A double-precision floating number ranging from -180.0 to 180.0

point

Latitude

Cell latitude

A double-precision floating number ranging from -90.0 to 90.0

point

BEAMWID

Beamwidth

A double-precision floating number ranging from 0.0 to 360.0

point

SCENARIO

Cell application scenario

TH

Densely populated urbanarea, urban area (default), suburban area, rural area, high-speed railway, cell edge, high site, and others

The preceding fields are contained in the engineering parameter template for the SONMaster. You can export the template through the engineering parameter management module on the SONMaster and configure them based on network requirements After configuring the engineering parameter template, you need to import engineering parameter data through the engineering parameter management module on the SONMaster

The SCENARIO parameter is used to calculate the reuse distance of cells. If the SCENARIO parameter is not configured in the engineering parameter template, the urban area is used by default 2) Intra-frequency neighbor relationships To support intra-frequency confusion detection, the SONMaster needs to obtain LTE intra-frequency neighbor relationships within the detection scope 3) Inter-frequency neighbor relationships To support inter-frequency confusion detection, the SONMaster needs to obtain LTE inter-frequency neighbor relationships within the detection scope 4) Inter-RAT neighbor relationships To support inter-RAT confusion detection between UMTS and LTE, the SONMaster needs to obtain LTE-to-UMTS and UMTS-to-LTE neighbor relationships within the detection scope 5) Cell reuse distance, as described in Table 7-7

Issue 01 (2015-06-18)


29



Table 7-7 Reuse distances Application Scenario

Value Range (km)

Default Value (km)

Densely populated urban area Urban area Suburban area Rural area High-speed railway Cell edge High site Others

0~100 0~100 0~100 0~100 0~100 0~100 0~100 0~100

1 4 12 12 12 12 12 12

Remarks

Default

6) Policy parameters, as described in Table 7-8 Table 7-8 Policy parameters Parameter Name Detection method

Detection period

Value Range Distributed detection Centralized detection

Enumerated values, including 1 day, 2 days, 3 days, 7 days, 14 days, and 30 days.

Default Remarks Value All

You can select one or more

1day

Centralized detection type

Enumerated values,including collision, confusion, and mod 3.

All

You can select one or more This parameter is valid only for the centralized detection

Distribute detection type

Enumerated values,including collision, confusion

All

You can select one or more This parameter is valid only for the distributed detection.

Migrate users before PCI modification

Value: Yes or No

Yes

This parameter applies only to NEs in verisions later than eRAN7.0.

PCI conflict interface threshold PCI conflict load threshold

Value range: [-10,10]

6

Mod 3 detection

Value range: 0-100 Unit: %

50

Mod 3 detection

Good RSRP threshold [-120, -70] dBm (DLRSRP.Good_THD

Issue 01 (2015-06-18)

-105d Mod 3 detection: MR data records where the RSRP Bm


30


)

Poor RSRQ threshold [-24, -6] dB (RSRQ.Bad_THD)


of the primary serving cell is less than the value of threshold are regarded to be weak coverage and poor quality MR data records. -14dB Mod 3 detection: MR data records where the RSRP of the primary serving cell is greater than or equal to the value of DLRSRP.Good_THD and the RSRQ is less than the value of RSRQ.Bad_THD are regarded to be interference MR data records.

Interference MR Value range: 0% to 100% 10% proportion threshold

This parameter identifies problematic cells of the downlink poor quality category. This parameter is valid only for mod 3 detection in the centralized detection.

DL PRB threshold

This parameter identifies the heavy load duration of a cell. This parameter is valid only for mod 3 detection in the centralized detection.

high-load Value range: 0% to 100% 80%

Online user quantity Value range: 0-10000 threshold

50

Busy hour proportion Value range: 0% to 100% 50% threshold



7.4.2.3 PCI Self-Optimization Table 7-9 lists parameters for determining whether a cell is a new cell and the parameter values can be set on the SONMaste. PCI self-optimization preferentially re-assigns PCIs to cells that are newly deployed or cells whose PCIs are recently changed.

Issue 01 (2015-06-18)


31



Table 7-9 Parameters for determining whether a cell is a new cell Parame ter Name

Paramet er ID

Data Source

Setting Notes

OldCell Threshol d Value

-

User-defin ed

The default value of this parameter is 0. You are advised to set this parameter to 30 (unit: day) if you need to prioritize the conflicting cells based on the cell deployment time or PCI change time. In this case, a cell that was deployed more than 30 days ago or a cell whose PCI was changed more than 30 days ago is considered as an old cell. OldCellThreshold Value must be greater than SameBatchInterval Value.

SameBat chInterv al Value

User-defin ed

-

The default value of this parameter is 0. You are advised to set this parameter to 7 (unit: day) if you need to prioritize the conflicting cells based on the cell deployment time or PCI change time. In this situation, two cells with a PCI change time interval of less than 7 days are considered as being changed in the same batch. SameBatchInterval Value must be smaller than OldCellThreshold Value.

Table 7-10 lists parameters related to PCI self-optimization. Only PCIs within the specified range can be used by LTE cells. The PCI re-assignment priority can be set for each LTE cell. For example, if a cell covers the VIP area, you can set the Optimization Priority parameter for this cell to Locked so that the PCI of this cell cannot be changed. Parameters in Table 7-10 can be set one by one on the SONMaster, or be set by importing a file. To set these parameters by importing a file, you must prepare the file based on the template. Table 7-10 Parameters related to PCI self-optimization Parameter Name

Parameter ID

Data Source

Setting Notes

Available PCI Range

-

Network plan (negotiation required)

This parameter specifies the range of PCIs available to a cell. The range can be consecutive or discrete, for example, "[0-100], 220". The default PCI range is 0-503. The PCI range of a cell in the boundary coverage area must be negotiated with the peer end.

Optimization Priority

Issue 01 (2015-06-18)

-

Network plan (negotiation


This parameter specifies the PCI re-assignment priority of a cell, which can be High

32


Parameter Name


Parameter ID

Data Source

Setting Notes

required)

priority, Low priority, or Locked. The default value is Low priority.

The PCI self-optimization result is related to cell location parameters listed in Table 7-11 and antenna parameters listed in Table 7-12. These parameters will be considered for PCI reuse and PCI mod 3/PCI mod 30 staggering. These parameters can be configured on the eNodeB by running MML commands, or be filled in to the engineering parameter files and imported to the SONMaster. To set these parameters by importing a file, you must prepare the file based on the template. If some parameters in Table 7-11 or Table 7-12 are not collected or have incorrect values, the new PCI assigned by PCI self-optimization to a conflicting cell can solve the PCI conflict but may not be the optimal one. If a cell is not installed with an RET antenna, the antenna parameters cannot be configured by running MML commands.

Table 7-11 eNodeB location parameters related to PCI self-optimization Parameter Name

Parameter ID

Data Source

Setting Notes

Longitude With Degree Format

Location.L ONGITUD EDEGFO RMAT

Network plan (negotiation not required)

In PCI self-optimization scenarios, the longitude and latitude must be set based on actual conditions.

Location.L ONGITUD ESECFOR MAT


Latitude With Degree Format

Location.L ATITUDE DEGFOR MAT


Latitude With Second Format

Location.L ATITUDE SECFOR MAT


Longitude With Second Format

Use either the longitude with degree format or the longitude with second format. Use either the latitude with degree format or the latitude with second format.

Table 7-12 Antenna parameters related to PCI self-optimization Parameter Name

Parameter ID

Data Source

Setting Notes

Antenna Bearing

RetDeviceData. BEARING


If an RET antenna is used, set this parameter using MML commands based on actual conditions.

Issue 01 (2015-06-18)


33


Parameter Name

Parameter ID


Data Source

Setting Notes If a non-RET antenna is used, import the engineering parameter template that includes this parameter through the U2000. If an omnidirectional antenna is used, set this parameter to 0 in the engineering parameter template.

Beamwidth1Beamwidth4

RetDeviceData. BEAMWIDTH1 ~4


If an RET antenna is used, set this parameter using MML commands based on actual conditions. If a non-RET antenna is used, import the engineering parameter template that includes this parameter through the U2000. If an omnidirectional antenna is used, set this parameter to 359 in the engineering parameter template.

7.4.3 Precautions Both this feature and the LTE PCI Conflict Optimization feature on the U2000 can provide distributed detection results of eNodeBs and reallocate PCIs. Inconsistencies of management scopes and available PCI ranges between the U2000 and SONMaster may result in PCI reallocation consistencies. Once this feature is activated on the SONMaster, you need to mask the PCI self-optimization feature on the U2000, ensuring optimization consistency and management capability coordination. The distributed detection function on eNodeBs remains enabled.

7.4.4 Hardware Adjustment N/A

7.4.5 Activation The feature activation is divided into the following two parts: 

Distributed PCI conflict detection on the eNodeB



PCI conflict detection and self-optimization task created on the SONMaster. PCI conflict detection triggered by eNodeB parameter adjustment does not require activation.

7.4.5.1 Distributed PCI Conflict Detection Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs Enter the values of the parameters listed in Table 7-13 in a summary data file, which also contains other data for the new eNodeBs to be deployed.

Issue 01 (2015-06-18)


34



Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB product documentation. The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions: 

The managed objects (MOs) in Table 7-13 are contained in a scenario-specific summary data file. In this situation, set the parameters in the MOs, and then verify and save the file.



Some MOs in Table 7-13 are not contained in a scenario-specific summary data file. In this situation, customize a summary data file to include the MOs before you can set the parameters.

Table 7-13 Parameters related to PCI conflict detection MO

Sheet in the Summary Data File

Parameter Group

Remarks

GLOBA LPROC SWITC H

User-defined sheet (GLOBALPROC SWITCH is recommended.)

Update eNB Configuratio n Via X2 Switch

This parameter must be customized on a list-type sheet of the template. Add the GLOBALPROCSWITCH sheet (Global Radio Parameter > Global Algorithm Information > GlobalProcSwitch) to the template. On the CME, add the GLOBALPROCSWITCH sheet to the Basic Scenario: using for the Scenario of VLAN and without Security,etc template.

ANR

ENodeB AlgoSwi tch

User-defined sheet (ANR is recommended.)

User-defined sheet (ENodeBAlgoSwi tch is recommended.)

ANR Active PCI Conflict Detection Switch/Start time/Stop time

This parameter must be customized on a list-type sheet of the template.

PCI Conflict Detect Switch/PCI conflict alarm switch

This parameter must be customized on a list-type sheet of the template.

Add the ANR sheet (Global Radio Parameter > Global Algorithm Information > ANR) to the template. On the CME, add the ANR sheet to the Basic Scenario: using for the Scenario of VLAN and without Security,etc template.

Add the ENodeBAlgoSwitch sheet (Global Radio Parameter > Global Algorithm Information > ENodeBAlgoSwitch) to the template. On the CME, add the ENodeBAlgoSwitch sheet to the Basic Scenario: using for the Scenario of VLAN and without Security,etc template.

Issue 01 (2015-06-18)


35



Using the CME to Perform Batch Configuration for Existing eNodeBs Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relations, for multiple eNodeBs in a single procedure. The procedure is as follows: Step 1 Customize a summary data file with the MOs and parameters listed in section "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For online help, press F1 when a CME window is active, and select Managing the CME > CME Guidelines > LTE Application Management > eNodeB Related Operations > Customizing a Summary Data File for Batch eNodeB Configuration. Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into the customized summary data file. Step 3 In the summary data file, set the parameters in the MOs according to the setting notes provided in section "Data Preparation" and close the file. Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station Bulk Configuration Data (CME client mode), to import the summary data file into the CME, and then start the data verification. Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. For detailed operations, see Managing the CME > CME Guidelines > Script File Management > Exporting Incremental Scripts from a Planned Data Area in the CME online help. ----End

Using the CME to Perform Single Configuration On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows: Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window. Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.

Issue 01 (2015-06-18)


36



Figure 7-1 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL. Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are displayed in area 4. Step 5 Set the parameters in area 4 or 5. Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts. ----End

Using MML Commands 

PCI collision detection Run the MOD ENODEBALGOSWITCH command with COLLISION_DETECT_SWITCH of PCI Conflict Detect Switch set to 1.



PCI confusion detection Run the MOD ENODEBALGOSWITCH command with CONFUSION_DETECT_SWITCH of PCI Conflict Detect Switch set to 1.



PCI conflict detection based on X2 messages Run the MOD GLOBALPROCSWITCH with Update eNB Configuration Via X2 Switch set to ON(On).



PCI conflict detection based on ANR Run the MOD ANR command with ANR Active PCI Conflict Detection Switch set to ON(On) and Start Time and Stop Time set to appropriate values.



(Optional) PCI conflict alarm reporting After PCI conflict alarm reporting is enabled, the eNodeB reports an alarm to the U2000 alarm console when it detects a PCI conflict. Run the MOD ENODEBALGOSWITCH command with PCI conflict alarm switch set to ON(On).

Issue 01 (2015-06-18)


37



MML Command Examples 

PCI collision detection

MOD ENODEBALGOSWITCH: PciConflictDetectSwitch=COLLISION_DETECT_SWITCH-1; 

PCI confusion detection

MOD ENODEBALGOSWITCH: PciConflictDetectSwitch=CONFUSION_DETECT_SWITCH-1; 

PCI conflict detection based on X2 messages

MOD GLOBALPROCSWITCH: X2BasedUptENodeBCfgSwitch=ON; 

PCI conflict detection based on ANR

MOD ANR: ActivePciConflictSwitch=ON, StartTime=11&50&12, StopTime=11&50&15; 

(Optional) PCI conflict alarm reporting

MOD ENODEBALGOSWITCH: PciConflictAlmSwitch=ON;

Using an Optimization Task on the SONMaster to Activate Distributed PCI Conflict Detection You can create an optimization task on the SONMaster and start the task to activate the distributed PCI conflict detection; 

Add a task

You can create a PCI conflict detection and self-optimization task on the SONMaster. During the creation, you need to set basic task parameters and optimization parameters, and select optimization objects 

Basic task parameters: include the task name, type, start policy, and stop policy.



Optimization parameters: indicate the parameters that are strongly related to detection and reallocation algorithms, such as the optimization period, conflict detection type, and interference and load thresholds for mod 3 detection.

To enable distributed PCI conflict detection, you must set the detection method in optimization parameter policies to distributed detection 

Optimization objects: indicate the cells involved in detection and self-optimization. One cell can only be involved in one task for conflict detection and self-optimization.



Start a task

You can start an optimization task using the following methods: 

Manual: When the task start policy is set to Manual, you need to manually start the task on the SONMaster



Immediate: After you create a task, the SONMaster automatically starts the task



Scheduled: After creating a task, you can set the start time. The SONMaster automatically starts the task upon the preset start time

When the detection method for a task contains distributed detection, the distributed detection function on the eNodeB is activated in the optimization task

Issue 01 (2015-06-18)


38



In distributed PCI conflict detection configured by using MML commands or the CME, conflict information cannot be reported to the SONMaster and assigned on the SONMaster. However, the conflict information can be viewed in the U2000 alarm console Conflict information can be reported to the SONMaster and assigned only when the distributed detection is activated by following the instructions provided in section

7.4.5.2 Centralized PCI Conflict Detection Centralized PCI conflict detection can be activated only by creating an optimization task and starting the task on the SONMaster. 1.

On the SONMaster, create a PCI conflict detection and self-optimization task and set Detection method in policy parameter settings to include centralized detection Then, set other parameter based on site requirements.

2.

Start the task: 

If the task start method in Step 1 is set to Manual, you need to manually start the

task so as to activate centralized PCI conflict detection 

If the task start method in Step 1 is set to Immediate, the SONMaster automatically starts the task after the task is created and activates centralized PCI conflict detection



If the task start method in Step 1 is set to Scheduled and specified time is set, the SONMaster automatically starts the task upon the preset time and activates centralized PCI conflict detection.

Before starting an optimization task for detection activation, you need to provide the data prepared in section 7.4.2 on the SONMaster. Otherwise, the task will fail.

7.4.5.3 PCI Self-Optimization Prerequisites The available PCI range and PCI optimization priority of cells can be configured on the SONMaster. Table 7-14 lists the parameter template for the available PCI range and PCI optimization priority. Table 7-14 Parameter template for the available PCI range and PCI optimization priority of a cell Mcc

Mnc

eNodeBId

CellId

Range

PCI Optimization Priority

MCC of the

MNC of the cell

eNodeB ID of the cell

Cell ID

Available PCI range for the

PCI optimization priority of the

Issue 01 (2015-06-18)


39


Mcc

Mnc


eNodeBId

CellId

cell 

Range

PCI Optimization Priority

cell

cell

Viewing or setting the available PCI range and PCI optimization priority for LTE cells by exporting or importing a file When the available PCI range and PCI optimization priority for LTE cells are configured by importing a file, a maximum of 100,000 records can be imported. You can choose to import all parameter values or only increment parameter values. A consecutive PCI range is set in format of [StartPCI, EndPCI]. A discrete PCI can be added by using a comma (,), and then the whole PCI range should be enclosed in double quotation marks (""), for example: "[0-100],[500]." Available PCI ranges and PCI optimization priorities for all cells under the eNodeB can be viewed by exporting the file.



Viewing or setting the available PCI range and PCI optimization priority for LTE cells on the SONMaster GU To view or set the available PCI range for LTE cells on the SONMaster GUI, select LTE cells on the SONMaster GUI first.

Engineering parameters for cell PCI self-optimization can be configured by importing the engineering parameter template into the SONMaster. If engineering parameters of a sector are configured both on the eNodeB and in the engineering parameter template, Longitude, Latitude, and Azimuth in the engineering parameter template take effect while Beamwidth configured on the eNodeB takes effect. Table 7-15 lists the engineering parameter template for PCI self-optimization. The parameters listed in the template are configured for the cell where PCI self-optimization needs to be performed. Table 7-15 Engineering parameter template for PCI self-optimization MC C

MNC

eNod eBId

CellI D

Actu al ID

De vic eN O

Su bU nit NO

Long itude

Latit ude

Azim uth

Beam widt h

MC C of the cell

MNC of the cell

eNod eB ID of the cell

Cell ID

Actua l ID

Ant enn a devi ce num ber

Ant enn a sub unit num ber

Set the longit ude with degre e forma t based on the netwo rk plan.

Set the latitud e with degre e forma t based on the netwo rk plan.

Set the azimu th based on the netwo rk plan.

Set the beam width based on the netwo rk plan.

The preceding two templates are both in .csv format.

Issue 01 (2015-06-18)


40



If the eNodeB is configured with the RET antenna and the corresponding antenna parameters are configured in the engineering parameter template, DeviceNO and SubunitNO in the engineering parameter template must be set to the same values as RET.DeviceNO and RETSUBUNIT.SUBUNITNO configured in the eNodeB, respectively. In other scenarios, ensure that the values of DeviceNO and SubunitNO are unique for each sector in the engineering parameter template.

Activation Procedure Centralized PCI self-optimization and centralized PCI conflict detection are activated in one optimization task. Therefore, the activation procedure for centralized PCI self-optimization is the same as that of centralized PCI conflict detection in section 7.4.5.2

7.4.6 Activation Observation PCI Conflict Detection If no PCI conflict exists in the network, simulate a PCI conflict scenario before performing activation observation. To verify the activation of PCI conflict detection, use one of the following methods: 

Querying the PCI conflict alarm: If the ENodeBAlgoSwitch.PciConflictAlmSwitch parameter is set to ON(On), you can check whether ALM-29247 Cell PCI Conflict exists in the alarm console on the U2000. If the alarm exists, distributed PCI conflict detection has been activated.



Querying PCI conflict information: On the SONMaster, open the PCI conflict detection and self-optimization page. If you can find PCI conflict information in the PCI Conflict Information area on the PCI Conflict tab page, PCI conflict detection has been activated





If the detection method is OSS, centralized PCI conflict detection has been activated and the conflict information has been detected



If the detection method is eNodeB, distributed PCI conflict detection on the eNodeB has been activated and the conflict information has been detected.



If the detection method is OSS&eNodeB, centralized and distributed PCI conflict detection has been activated and the conflict information has been detected.

Querying SON logs: On the SONMaster, choose System > Log Management. In the left pane, select SON Logs. On the displayed SON Logs Management page, click the Query tab. On the Query tab page, set Log Category to LTE PCI Conflict detection and Optimization Log. If logs related to PCI conflicts can be queried, the PCI conflict detection and self-optimization function has been activated

PCI Self-Optimization To verify the activation of PCI self-optimization, use either of the following methods: 

Querying optimization suggestions on the SONMaster TheSONMaster generates optimization suggestions after the PCI self-optimization process is complete. If these optimization suggestions can be queried, the PCI conflict detection function is successfully activated. The optimization suggestions are described as follows:

Issue 01 (2015-06-18)


41





−

If the SONMaster delivers a new PCI for the cell that experiences PCI conflicts, the cell that needs to be allocated a new PCI, the current PCI, and the recommended PCI are displayed under Optimization Advice.

−

If PCI self-optimization cannot allocate new PCIs for certain conflicting cells, the cells and causes are recorded on the Exception tab page.

Querying SON logs On the SONMaster, choose System > Log Management. In the left pane, select SON Logs. On the displayed SON Logs Management page, click the Query tab. On the Query tab page, set Log Category to LTE PCI Conflict detection and Optimization Log. If logs related to PCI conflict optimization advice can be queried, the PCI conflict detection and self-optimization function has been activated.

7.4.7 Reconfiguration N/A

7.4.8 Deactivation PCI collision detection, PCI confusion detection, and PCI conflict detection based on ANR can be deactivated. PCI conflict detection triggered by eNodeB parameter adjustment, PCI conflict detection based on X2 messages, and PCI self-optimization do not require deactivation. This section describes how to deactivate PCI collision detection, PCI confusion detection, and PCI conflict detection based on ANR.

7.4.8.4 Distributed PCI Conflict Detection Using the CME to Perform Batch Configuration Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relations, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 7-16. Table 7-16 Parameters related to PCI conflict detection MO


Parameter Group

Setting Notes

ANR

User-defined sheet (ANR is recommended.)

ANR Active PCI Conflict Detection Switch

Set ANR Active PCI Conflict Detection Switch to OFF(Off).

ENodeBAlgo Switch

User-defined sheet (ENodeBAlgoSwitc h is recommended.)

PCI conflict alarm switch

Set PCI conflict alarm switch to OFF(Off).

ENodeBAlgo Switch

User-defined sheet ((ENodeBAlgoSwit ch is

PCI Conflict Detect Switch

Set COLLISION_DETECT_SWI TCH and

Issue 01 (2015-06-18)


42



MO


Parameter Group

recommended.)

Setting Notes

CONFUSION_DETECT_SW ITCH of PCI Conflict Detect Switch to 0.

Using the CME to Perform Single Configuration On the CME, set parameters according to Table 7-16. For detailed instructions, see "Using the CME to Perform Single Configuration" for feature activation.

Using MML Commands 

PCI collision detection Run the MOD ENODEBALGOSWITCH command with COLLISION_DETECT_SWITCH of PCI Conflict Detect Switch set to 0.



PCI confusion detection Run the MOD ENODEBALGOSWITCH command with CONFUSION_DETECT_SWITCH of PCI Conflict Detect Switch set to 0.



PCI conflict detection based on X2 messages Run the MOD GLOBALPROCSWITCH command with Update eNB Configuration Via X2 Switch set to OFF(Off).



Proactive PCI conflict detection based on ANR Run the MOD ANR command with ANR Active PCI Conflict Detection Switch set to OFF(Off).



(Optional) PCI conflict alarm reporting Run the MOD ENODEBALGOSWITCH command with PCI conflict alarm switch set to OFF(Off).

MML Command Examples 

PCI collision detection

MOD ENODEBALGOSWITCH: PciConflictDetectSwitch=COLLISION_DETECT_SWITCH-0; 

PCI confusion detection

MOD ENODEBALGOSWITCH: PciConflictDetectSwitch=CONFUSION_DETECT_SWITCH-0; 

PCI conflict detection based on X2 messages

MOD GLOBALPROCSWITCH: X2BasedUptENodeBCfgSwitch=OFF; 

Proactive PCI conflict detection based on ANR

MOD ANR: ActivePciConflictSwitch=OFF; 

(Optional) PCI conflict alarm reporting

MOD ENODEBALGOSWITCH: PciConflictAlmSwitch=OFF;

Issue 01 (2015-06-18)


43



Using an Optimization Task on the SONMaster to Deactivate Distributed PCI Conflict Detection This method is used to stop distributed detection managed by an optimization task on the SONMaster. For a running optimization task where the detection method is distributed detection, you can deactivate distributed detection using the following methods: 

Manual: You can manually stop the optimization task, thereby deactivating distributed detection.



End time: You have set end time in the task stop policy. The SONMaster automatically stops the optimization task upon the preset end time, thereby deactivating distributed detection.



Execution times: You have set the number of execution times in the task stop policy. The SONMaster automatically stops the optimization task upon the preset number of execution times, thereby deactivating distributed detection.

7.4.8.5 Centralized PCI Conflict Detection You can deactivate centralized detection using the method similar to that in section "Using an Optimization Task on the SONMaster to Deactivate Distributed PCI Conflict Detection." For an optimization task where the task status is running and detection method is centralized detection, you can deactivate centralized detection using the following three methods: Manual, End time, and Execution times

7.4.8.6 Centralized PCI Self-Optimization You can deactivate centralized PCI self-optimization using the method similar to that in section "Using an Optimization Task on the SONMaster to Deactivate Distributed PCI Conflict Detection."

7.5 Monitoring 7.5.1 Optimization Advice Evaluation The optimization advice evaluation is divided into the following types: 

After the SONMaster generates PCI conflict information, you can evaluate the quality of the PCI conflict detection based on assistant decision-making information in the PCI conflict list.



After the SONMaster generates PCI reallocation optimization advice, you can evaluate the quality of the optimization advice based on assistant decision-making information in the optimization advice list.

Table 7-17 the following table describes the assistant decision-making information about PCI conflict detection and PCI reallocation.

Issue 01 (2015-06-18)


44



Table 7-17 assistant decision-making information Type

Assistant Decision-Making Information

Description

PCI conflict detection

Distance between cells (km)

In normal cases, a smaller value of Distance between cells (km) indicates more serious conflict and a more urgent demand to resolve the conflict.

Number of MRs

During PCI mod 3 conflict detection, more MRs indicate more serious conflict.

Detection times (accumulated)

More detection times indicate longer existence of the conflicting pair, more detection repetitions, and a more urgent demand to resolve the conflict.

Detected cell PCI

Used to check whether PCI conflict exists between two cells.

Conflicting cell PCI

PCI reallocation

Online UE count

In PCI collision and confusion scenarios, PCIs of the detected cell and conflicting cell are the same. In the PCI mod 3 scenario, their PCIs are different, but the remainder of dividing the PCI by 3 is the same for them. In manual mode, you can determine whether to change cell PCIs based on the number of online UEs. Changing PCIs results in cell restart.

7.5.2 Network KPI Monitoring You can monitor the performance of the PCI conflict detection and self-optimization feature by checking the service drop rates and outgoing handover success rates. This feature has been delivering good performance if call drop rates decrease after the feature is enabled. Call drop rates are as follows: 

Call Drop Rate(all) Call Drop Rate(all) = L.E-RAB.AbnormRel/(L.E-RAB.AbnormRel + L.E-RAB.NormRel)



Call Drop Rate(VoIP) Call Drop Rate(VoIP) = L.E-RAB.AbnormRel.QCI.1/(L.E-RAB.AbnormRel.QCI.1 + L.E-RAB.NormRel.QCI.1)

This feature has been delivering good performance if outgoing handover success rates decrease after the feature (especially the proactive PCI conflict detection) is enabled. Call drop rates are as follows: 

Intra-Frequency Handover Out Success Rate Intra-Frequency Handover Out Success Rate = (L.HHO.IntraeNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.IntraFreq.ExecSuccOut)/(L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.IntraFreq.ExecAttOut)



Issue 01 (2015-06-18)

Inter-Frequency Handover Out Success Rate Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

45



Inter-Frequency Handover Out Success Rate = (L.HHO.IntraeNB.InterFreq.ExecSuccOut + L.HHO.IntereNB.InterFreq.ExecSuccOut)/(L.HHO.IntraeNB.InterFreq.ExecAttOut + L.HHO.IntereNB.InterFreq.ExecAttOut) Table 7-18 describes counters related to the service drop rate. Table 7-18 Counters related to the service drop rate Counter ID

Counter Name

Description

1526726686

L.E-RAB.AbnormRel.QCI.1

Number of abnormal E-RAB releases for services with the QCI of 1 in a cell

1526726687

L.E-RAB.NormRel.QCI.1

Number of normal E-RAB releases for services with the QCI of 1 in a cell

1526727546

L.E-RAB.AbnormRel

Total number of abnormal E-RAB releases by the eNodeB

1526727547

L.E-RAB.NormRel

Total number of normal E-RAB releases by the eNodeB

1526726996

L.HHO.IntraeNB.IntraFreq. ExecAttOut

Number of intra-eNodeB intra-frequency outgoing handovers executions in a cell

1526726997

L.HHO.IntraeNB.IntraFreq. ExecSuccOut

Number of successful intra-eNodeB intra-frequency outgoing handovers in a cell

1526726999

L.HHO.IntraeNB.InterFreq. ExecAttOut

Number of intra-eNodeB inter-frequency outgoing handovers executions in a cell

1526727000

L.HHO.IntraeNB.InterFreq. ExecSuccOut

Number of successful intra-eNodeB inter-frequency outgoing handovers in a cell

1526727002

L.HHO.IntereNB.IntraFreq. ExecAttOut

Number of inter-eNodeB intra-frequency outgoing handovers executions in a cell

1526727003

L.HHO.IntereNB.IntraFreq. ExecSuccOut

Number of successful inter-eNodeB intra-frequency outgoing handovers in a cell

1526727005

L.HHO.IntereNB.InterFreq.

Number of inter-eNodeB

Issue 01 (2015-06-18)


46


Counter ID

1526727006


Counter Name

Description

ExecAttOut

inter-frequency outgoing handovers executions in a cell

L.HHO.IntereNB.InterFreq. ExecSuccOut

Number of successful inter-eNodeB inter-frequency outgoing handovers in a cell

Table 7-19 describes the improved performance counters of UMTS cells after PCI self-optimization is performed for UMTS-to-LTE PCI confusion conflicts. Table 7-19 UMTS counters to be observed Counter to Be Observed

Calculation Method

Raw Counter

PS RAB service drop rate for UMTS cells (%)

PS Service Drop Ratio (Cell) =

67179781

[VS.RAB.AbnormRel.PS (67179781)/(VS.RAB.AbnormRel.PS (67179781)+VS.RAB.NormRel.PS (67179782))]*100%

67179782

PS RAB service drops for UMTS cells

PS call drops: VS.RAB.AbnormRel.PS (67179781)

67179781

Service-triggered UMTS-to-LTE PS handover success rate for UMTS cells (%)

Service-based UMTS-to-LTE PS Handover Success Rate (Cell) = VS.U2LTEHO.SuccOutPS.Service (73423387)/VS.U2LTEHO.AttOutPS.Service (73423386).

73423386

Service-based UMTS-to-LTE PS handover success times for UMTS cells

Service-based UMTS-to-LTE PS Handover Success Times: VS.U2LTEHO.SuccOutPS.Service (73423387)

73423387

PS RAB service drop rate for RNCs (%)

PS Call Drop Ratio (RNC) = [VS.RAB.AbnormRel.PS.RNC (67174964)/(VS.RAB.AbnormRel.PS.RNC (67174964)+VS.RAB.NormRel.PS.RNC (67174966))]*100%

67174964

PS RAB service drops for RNCs

PS call drops: VS.RAB.AbnormRel.PS.RNC (67174964)

67174964

73423387

67174966

In addition to the call drop rate and handover success rate, you can observe the following counters for PCI mod 3 conflicts: 

Downlink PRB usage (including the PRB): indicates the downlink load of a cell. The PCI mod 3 interference is greatest when the cell has no load or is lightly loaded.

 Downlink throughput: The downlink cell throughput decreases when PCI mod 3 conflicts deteriorate.

Issue 01 (2015-06-18)


47



 RSRP difference between the source cell and conflicting cell: A larger difference indicates higher interference. Table 7-20 describes the counters to be observed. Table 7-20 Counters to be observed Counter to Be Observed

Calculation Method

Raw Counter

Downlink PRB usage of a cell

L.ChMeas.PRB.DL.Used.Avg/L.ChMeas.PRB.D L.Avail *100%

1526726740

Average number of downlink PRBs used by CEUs

L.ChMeas.PRB.DL.CEU.Used.Avg

1526728480

Total downlink traffic volume for PDCP SDUs in a cell (bit)

L.Thrp.bits.DL

1526728261

Total downlink CEU traffic volume for PDCP SDUs in a cell (bit)

L.Thrp.bits.DL.CEU

1526728477

1526728433

7.6 Parameter Optimization 

PCI conflict detection triggered by eNodeB parameter adjustment or based on X2 messages N/A



Proactive PCI conflict detection based on ANR The ANR.StartTime and ANR.StopTime parameters need to be optimized. For recommended settings of these parameters, see 7.4.2 Data Preparation.

Centralized PCI conflict detection and optimization allows you to optimize the following parameters: 

Cell application scenario Add cells to corresponding scenarios by modifying the engineering parameter table so that you can allocate PCIs to cells properly.



Reuse distance Each application scenario has a default reuse distance. You can adjust the reuse distance based on site requirements, ensuring the proper and accurate detection and reallocation.



Issue 01 (2015-06-18)

Table 7-21 Optimization policy parameters


48



Table 7-21 optimization policy parameters Name

Reconfiguration Description

Centralized detection period

You can reconfigure the period to meet the period requirements of network optimization frequencies.

PCI conflict interference threshold

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates less identified PCI mod 3 conflict. A smaller value indicates more identified PCI mod 3 conflict.

PCI conflict threshold

load

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates less identified PCI mod 3 conflict. A smaller value indicates more identified PCI mod 3 conflict.

Good RSRP threshold

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates fewer identified conflict MRs and less identified PCI mod 3 conflict. A smaller value indicates more identified conflict MRs and more PCI mod 3 conflict.

Poor RSRQ threshold

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates more identified conflict MRs and more PCI mod 3 conflict. A smaller value indicates fewer identified conflict MRs and less identified PCI mod 3 conflict.

Interference MR proportion threshold

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates more MR requirements for identifying PCI mod 3 conflict and more difficulties in identifying PCI mod 3 conflict. A smaller value indicates fewer MR requirements for identifying PCI mod 3 conflict and fewer difficulties in identifying PCI mod 3 conflict.

DL PRB high load threshold

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates fewer identified cell busy hours and more identified PCI mod 3 conflict. A smaller value indicates more identified cell busy hours and less identified PCI mod 3 conflict.

Issue 01 (2015-06-18)


49


Name Online UE threshold


Reconfiguration Description count

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates fewer identified cell busy hours and more identified PCI mod 3 conflict. A smaller value indicates more identified cell busy hours and less identified PCI mod 3 conflict.

Busy hour proportion threshold

This parameter is used for PCI mod 3 detection. You can reconfigure the parameter based on site requirements. A larger value indicates more identified PCI mod 3 conflict. A smaller value indicates less identified PCI mod 3 conflict.

7.7 Troubleshooting Fault Description A PCI conflict is manually detected between neighboring cells or between a neighboring cell and a source cell, but the PCI conflict detection and self-optimization feature cannot solve this problem.

Fault Handling To clear the fault, perform the following steps: Step 1 On the SONMaster client, check whether the PCI conflict information is displayed. 

If the PCI conflict information is not displayed, go to Step 2.



If the PCI conflict information is displayed, go to Step 3.

Step 2 Check the NCL of the eNodeB of the source cell and the NRT of the source cell. Determine whether the neighboring cell parameters are updated or PCI conflict detection at the eNodeB is ineffective. If the following conditions are met: 

There is a PCI conflict between neighboring cells of the source cell, and at least one conflicting cell is the external cell of the source cell.



There is a PCI conflict between the source cell and its neighboring cell, and the neighboring cell is the external cell of the source cell.

Then check whether the PCI of the conflicting cell in the NCL is consistent with the configured neighboring cell parameter and is identical to the conflicted PCI. If the PCI of the conflicting cell in the NCL is inconsistent with the configured neighboring cell parameter, update the PCI in the NCL. Otherwise, contact Huawei technical support.

Issue 01 (2015-06-18)


50





Run the MML command LST CELL to query the configured parameters of the cell.



Run the MML command LST EUTRANEXTERNALCELL to query the NCL.



Run the MML command LST EUTRANINTRAFREQNCELL to query the intra-frequency neighboring cell relation.



Run the MML command LST EUTRANINTERFREQNCELL to query the inter-frequency neighboring cell relation.

Step 3 Table 7-22Check whether a PCI self-optimization task is proper based on the status of the task Table 7-22 Status of a PCI self-optimization task If...

Then...

A PCI self-optimization task is not created

Create a PCI self-optimization task. For details, see 7.4.5.3 PCI Self-Optimization.

A PCI self-optimization task has been created and is running properly, and the optimization suggestion is generated

Go to Step 5.

A PCI self-optimization task has been created and its Start Optimization Task is set to Periodic, but the task failed to start as scheduled

Contact Huawei technical support.

A PCI self-optimization task has been created and its Start Optimization Task is set to Now, but the task failed to start immediately


The PCI self-optimization task is started, but the PCI conflict persists

The SONMaster fails to find a proper PCI. Go to Step 5.

Other faults occur


Step 4 Check whether the PCI optimization suggestions are displayed. 

If the PCI optimization suggestions are displayed but PCI conflicts persist on the network, new PCI conflicts may occur during the optimization or the U2000 may fail to deliver an appropriate PCI for the conflicting cells in the last optimization. To solve this problem, you can remove some neighboring cells that are not used as handover cells or add some available PCIs for a new PCI self-optimization task.



If the PCI optimization suggestions are not displayed, contact Huawei technical support. You can view the PCI delivery status on the SONMaster.

Step 5 Check whether PCIs are properly set. 

Check whether any improper neighbor relation exists. When allocating a new PCI to a conflicting cell, PCI self-optimization will not choose the PCIs of the first-order and second-order intra-frequency neighboring cells of the conflicting cell. Also, PCIs of the intra-frequency external cells will also not be chosen. If the conflicting cell is configured with redundant neighbor relations or external cells, the conflicting cell may not be allocated a new PCI even if the available PCI range is set to [0, 503]. Therefore, improper neighbor relation and external cells should be removed.

Issue 01 (2015-06-18)


51



Two functions in intra-RAT event-triggered ANR can be used to remove redundant neighbor relations and external cells:



−

Automatic removal of improper neighbor relations and external cells. With this function, improper neighbor relations and external cells can be removed automatically.

−

Automatic detection of abnormal neighboring cell coverage. With this function, neighboring cells with overshoot coverage can be detected, and you can remove these cells manually.

Check whether the conflicting cell and its first-order neighboring cells have too many blacklisted cells. Blacklisted cells of the local cell and its first-order neighboring cells affect the available PCI range. Therefore, delete improper neighbor relations from the blacklist of the local cell and its first-order neighboring cells if PCIs are insufficient.

----End

Issue 01 (2015-06-18)


52


8 Parameters

8

Parameters

Table 8-1 Parameter description MO

eNBCell QciRsvd Para

Parame ter ID

RsvdSw Para2

MML Comma nd

Feature ID

Feature Name

Description

MOD ENBRS VDPAR A

None

None

Meaning: Indicates reserved 32-bit switch parameter 2 that is reserved for future requirements. Note on parameter replacement: Reserved parameters are temporarily used in patch versions and will be replaced with new parameters. For example, the ID of a new parameter can signify the parameter function. Therefore, avoid using this parameter.

LST ENBRS VDPAR A

GUI value range: RsvdSwPara2_bit1(ReservedSwitchParameter2_bit1), RsvdSwPara2_bit2(ReservedSwitchParameter2_bit2), RsvdSwPara2_bit3(ReservedSwitchParameter2_bit3), RsvdSwPara2_bit4(ReservedSwitchParameter2_bit4), RsvdSwPara2_bit5(ReservedSwitchParameter2_bit5), RsvdSwPara2_bit6(ReservedSwitchParameter2_bit6), RsvdSwPara2_bit7(ReservedSwitchParameter2_bit7), RsvdSwPara2_bit8(ReservedSwitchParameter2_bit8), RsvdSwPara2_bit9(ReservedSwitchParameter2_bit9), RsvdSwPara2_bit10(ReservedSwitchParameter2_bit1 0), RsvdSwPara2_bit11(ReservedSwitchParameter2_bit1 1), RsvdSwPara2_bit12(ReservedSwitchParameter2_bit1 2), RsvdSwPara2_bit13(ReservedSwitchParameter2_bit1 3), RsvdSwPara2_bit14(ReservedSwitchParameter2_bit1 4), RsvdSwPara2_bit15(ReservedSwitchParameter2_bit1 5), RsvdSwPara2_bit16(ReservedSwitchParameter2_bit1 6), RsvdSwPara2_bit17(ReservedSwitchParameter2_bit1 7),

Issue 01 (2015-06-18)


53


MO

Parame ter ID

MML Comma nd

Feature ID

8 Parameters

Feature Name

Description

RsvdSwPara2_bit18(ReservedSwitchParameter2_bit1 8), RsvdSwPara2_bit19(ReservedSwitchParameter2_bit1 9), RsvdSwPara2_bit20(ReservedSwitchParameter2_bit2 0), RsvdSwPara2_bit21(ReservedSwitchParameter2_bit2 1), RsvdSwPara2_bit22(ReservedSwitchParameter2_bit2 2), RsvdSwPara2_bit23(ReservedSwitchParameter2_bit2 3), RsvdSwPara2_bit24(ReservedSwitchParameter2_bit2 4), RsvdSwPara2_bit25(ReservedSwitchParameter2_bit2 5), RsvdSwPara2_bit26(ReservedSwitchParameter2_bit2 6), RsvdSwPara2_bit27(ReservedSwitchParameter2_bit2 7), RsvdSwPara2_bit28(ReservedSwitchParameter2_bit2 8), RsvdSwPara2_bit29(ReservedSwitchParameter2_bit2 9), RsvdSwPara2_bit30(ReservedSwitchParameter2_bit3 0), RsvdSwPara2_bit31(ReservedSwitchParameter2_bit3 1), RsvdSwPara2_bit32(ReservedSwitchParameter2_bit3 2 Unit: None Actual value range: RsvdSwPara2_bit1, RsvdSwPara2_bit2, RsvdSwPara2_bit3, RsvdSwPara2_bit4, RsvdSwPara2_bit5, RsvdSwPara2_bit6, RsvdSwPara2_bit7, RsvdSwPara2_bit8, RsvdSwPara2_bit9, RsvdSwPara2_bit10, RsvdSwPara2_bit11, RsvdSwPara2_bit12, RsvdSwPara2_bit13, RsvdSwPara2_bit14, RsvdSwPara2_bit15, RsvdSwPara2_bit16, RsvdSwPara2_bit17, RsvdSwPara2_bit18, RsvdSwPara2_bit19, RsvdSwPara2_bit20, RsvdSwPara2_bit21, RsvdSwPara2_bit22, RsvdSwPara2_bit23, RsvdSwPara2_bit24, RsvdSwPara2_bit25, RsvdSwPara2_bit26, RsvdSwPara2_bit27, RsvdSwPara2_bit28, RsvdSwPara2_bit29, RsvdSwPara2_bit30, RsvdSwPara2_bit31, RsvdSwPara2_bit32 Default value:

Issue 01 (2015-06-18)


54


MO

Parame ter ID

MML Comma nd

Feature ID

8 Parameters

Feature Name

Description

RsvdSwPara2_bit1:On, RsvdSwPara2_bit2:On, RsvdSwPara2_bit3:On, RsvdSwPara2_bit4:On, RsvdSwPara2_bit5:On, RsvdSwPara2_bit6:On, RsvdSwPara2_bit7:On, RsvdSwPara2_bit8:On, RsvdSwPara2_bit9:On, RsvdSwPara2_bit10:On, RsvdSwPara2_bit11:On, RsvdSwPara2_bit12:On, RsvdSwPara2_bit13:On, RsvdSwPara2_bit14:On, RsvdSwPara2_bit15:On, RsvdSwPara2_bit16:On, RsvdSwPara2_bit17:On, RsvdSwPara2_bit18:On, RsvdSwPara2_bit19:On, RsvdSwPara2_bit20:On, RsvdSwPara2_bit21:On, RsvdSwPara2_bit22:On, RsvdSwPara2_bit23:On, RsvdSwPara2_bit24:On, RsvdSwPara2_bit25:On, RsvdSwPara2_bit26:On, RsvdSwPara2_bit27:On, RsvdSwPara2_bit28:On, RsvdSwPara2_bit29:On, RsvdSwPara2_bit30:On, RsvdSwPara2_bit31:On, RsvdSwPara2_bit32:On GlobalP rocSwitc h

VoipWit hGapMo de

MOD GLOBA LPROC SWITC H

LOFD-0 02001 / TDLOF D-00200 1

LST GLOBA LPROC SWITC H

LOFD-0 02002 / TDLOF D-00200 2 LOFD-0 02007 / TDLOF D-00200 7 MRFD231808

Automat ic Neighbo ur Relation (ANR) Inter-R AT ANR PCI Collisio n Detectio n& Self-Opt imizatio n GSM and LTE Buffer Zone Optimiz ation(LT E)

Meaning: Indicates whether VoIP UEs are allowed to enter the periodical measurement gap and whether they can exit the gap if VoIP services are initiated during the gap. A VoIP UE can enter the periodical measurement gap during GSM and LTE buffer zone optimization or periodic inter-frequency/RAT measurements in cell tracing. If a UE enters the measurement gap and then VoIP services are initiated for this UE, fast ANR, active PCI conflict detection, GSM and LTE buffer zone optimization, or periodic inter-frequency/RAT measurements in cell tracing can trigger the UE's exiting from the gap. If this parameter is set to ENBALE, VoIP UEs are allowed to enter the periodic measurement gap during GSM and LTE buffer zone optimization and periodic inter-frequency/RAT measurement in cell tracing. The parameter setting does not affect the entering of the gap during fast ANR and active PCI conflict detection for VoIP UEs. If this parameter is set to DISABLE, VoIP UEs are prohibited to enter the periodic measurement gap and the UEs entering the gap and initiating VoIP services cannot exit the gap. GUI value range: DISABLE(disable), ENABLE(enable) Unit: None Actual value range: DISABLE, ENABLE Default value: ENABLE(enable)

GlobalP rocSwitc h

X2Base dUptEN odeBCf

Issue 01 (2015-06-18)

MOD GLOBA LPROC SWITC

LOFD-0 02001 / TDLOF D-00200

Automat ic Neighbo ur

Meaning: Indicates whether the eNodeB automatically updates the configuration of neighboring cells based on the messages received over the X2 interface. The messages include X2 SETUP REQUEST, X2 SETUP


55


MO

8 Parameters

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

gSwitch

H

1

Relation (ANR)

RESPONSE, and ENB CONFIGURATION UPDATE.

LST GLOBA LPROC SWITC H

Turn off the switch if the eNodeB configuration data on a network is to be modified by using the interlocking modification function on the CME and modifications to the parameters of a neighboring eNodeB will be updated on the local eNodeB through messages over the X2 interface. These parameters include eNodeBId, CellId, LocalCellId, CnOperator, CnOperatorTa, CellOp, PhyCellId, and DlEarfcn. This prevents the configuration data from being lost or abnormal during the automatic update. This switch must be turned on if the interlocking modification function on the CME is not used and the eNodeB configuration data on a network is to be modified by using the automatic eNodeB configuration update over the X2 interface GUI value range: OFF(Off), ON(On) Unit: None Actual value range: OFF, ON Default value: OFF(Off)

ENodeB AlgoSwi tch

PciConfl ictAlmS witch

MOD ENODE BALGO SWITC H

LOFD-0 02007 / TDLOF D-00200 7

LST ENODE BALGO SWITC H

PCI Collisio n Detectio n& Self-Opt imizatio n

Meaning: Indicates whether to display PCI conflict alarms in the alarm console. If the PciConflictAlmSwitch parameter is set to ON(On) and PCI collision or confusion occurs, PCI conflict alarms are displayed in the alarm console. Otherwise, PCI conflict alarms are not displayed in the alarm console GUI value range: OFF(Off), ON(On) Unit: None Actual value range: OFF, ON Default value: OFF(Off)

ENodeB AlgoSwi tch

AnrSwit ch

MOD ENODE BALGO SWITC H

LOFD-0 02001 / TDLOF D-00200 1

LST ENODE BALGO SWITC H

LOFD-0 02002 / TDLOF D-00200 2

Automat ic Neighbo ur Relation (ANR) Inter-R AT ANR

Meaning: Indicates whether to enable automatic neighbor relati1 (ANR). This parameter includes the following switches: IntraRatEventAnrSwitch: If this switch is on, intra-RAT event-triggered ANR is enabled to construct and optimize intra-RAT neighbor relationships by triggering intra-RAT coverage-based handover events IntraRatFastAnrSwitch: If this switch is on, intra-RAT fast ANR is enabled to construct and optimize intra-RAT neighbor relationships based on periodic intra-RAT measurements IntraRatAnrAutoDelSwitch: If this switch is on,

Issue 01 (2015-06-18)


56


MO

Parame ter ID

MML Comma nd

Feature ID

8 Parameters

Feature Name

Description

IntraRatEventAnrSwitch is on, and NoRmvFlag of an intra-RAT neighboring cell is set to PERMIT_RMV_ENUM, automatic removal of the intra-RAT neighbor relationship is allowed. If IntraRatAnrAutoDelSwitch is off, automatic removal of the intra-RAT neighbor relationship is not allowed. UtranEventAnrSwitch: If this switch is on, event-triggered ANR with UTRAN is enabled to construct and optimize inter-RAT neighbor relationships with UTRAN cells by triggering events for inter-RAT coverage-based handovers to UTRAN GeranEventAnrSwitch: If this switch is on, event-triggered ANR with GERAN is enabled to construct and optimize inter-RAT neighbor relationships with GERAN cells by triggering events for inter-RAT coverage-based handovers to GERAN UtranFastAnrSwitch: If this switch is on, fast ANR with UTRAN is enabled to construct and optimize inter-RAT neighbor relationships with UTRAN cells based on periodic UE measurements on UTRAN. The eNodeB does not deliver information about external UTRAN cells in the measurement configuration to UEs and the UEs measure only neighboring cells contained in the measurement configuration. Therefore, if you want external UTRAN cells added by fast ANR with UTRAN to be measured in handovers, you are advised to turn on UtranEventAnrSwitch as well GeranFastAnrSwitch: If this switch is on, fast ANR with GERAN is enabled to construct and optimize inter-RAT neighbor relationships with GERAN cells based on periodic inter-RAT measurements on GERAN. CdmaFastAnrSwitch: If this switch is on, fast ANR with CDMA2000 is enabled to construct and optimize inter-RAT neighbor relationships with CDMA2000 cells based on periodic inter-RAT measurements on CDMA2000 networks. UtranAut1rtDeleteSwitch: If this switch is on, UtranEventAnrSwitch is on, and NoRmvFlag of a neighboring UTRAN cell is set to PERMIT_RMV_ENUM, automatic removal of the inter-RAT neighbor relationship with UTRAN cells is allowed. If UtranAut1rtDeleteSwitch is off, automatic removal of the inter-RAT neighbor relationship with UTRAN cells is not allowed GeranAut1rtDeleteSwitch: If this switch is on, GeranEventAnrSwitch is on, and NoRmvFlag of a neighboring GERAN cell is set to

Issue 01 (2015-06-18)


57


MO

Parame ter ID

MML Comma nd

Feature ID

8 Parameters

Feature Name

Description

PERMIT_RMV_ENUM, automatic removal of the inter-RAT neighbor relationship with GERAN cells is allowed. If GeranAut1rtDeleteSwitch is off, automatic removal of the inter-RAT neighbor relationship with GERAN cells is not allowed. CdmaAut1rtDeleteSwitch: If this switch is on, CdmaEventAnrSwitch is on, and NoRmvFlag of a neighboring CDMA2000 cell is set to PERMIT_RMV_ENUM, automatic removal of the inter-RAT neighbor relationship with CDMA2000 cells is allowed. If CdmaAut1rtDeleteSwitch is off, automatic removal of the inter-RAT neighbor relationship with CDMA2000 cells is not allowed ExtendIntraRatAnrSwitch: Indicates whether cells with unknown physical cell identifiers (PCIs) can be c1figured as external cells of the eNodeB by using the eCoordinator. If this switch is on, cells with unknown PCIs can be c1figured as external cells of the eNodeB by using the eCoordinator in any of the following scenarios: (1) When unknown PCIs are detected by triggering handover events, IntraRatEventAnrSwitch is off or the UE is incapable of reporting cell global identificati1s (CGIs). (2) When unknown PCIs are detected by performing periodic intra-RAT measurements based on fast ANR, the UE is incapable of reporting CGIs. If this switch is off, cells with unknown PCIs cannot be c1figured as external cells of the eNodeB by using the eCoordinator CdmaEventAnrSwitch: If this switch is on, event-triggered ANR with CDMA2000 is enabled to construct and optimize inter-RAT neighbor relationships with CDMA2000 cells by triggering events for inter-RAT handovers to CDMA2000 MlbBasedEventAnrSwitch: Indicates whether to enable the MLB-based event-triggered ANR. When this switch is on and IntraRatEventAnrSwitch is on, inter-frequency MLB can be triggered to construct and optimize inter-frequency neighbor relationships with intra-RAT cells. When this switch is on and UtranEventAnrSwitch is on, MLB to UTRAN can be triggered to construct and optimize inter-RAT neighbor relationships with UTRAN cells. When this switch is on and GeranEventAnrSwitch is on, MLB to GERAN can be triggered to construct and optimize inter-RAT neighbor relationships with GERAN cells. When this switch is off, the neighbor relationship construction and optimization based on MLB is

Issue 01 (2015-06-18)


58


MO

Parame ter ID

MML Comma nd

Feature ID

8 Parameters

Feature Name

Description

disabled. IntraRatNoHoSetAnrSwitch: Indicates whether to automatically set the NoHoFlag parameter of an intra-RAT neighboring cell to FORBID_HO_ENUM. If IntraRatEventAnrSwitch and IntraRatNoHoSetAnrSwitch are both on, the NoHoFlag parameter of a neighboring cell can be automatically set. If IntraRatNoHoSetAnrSwitch is off, the NoHoFlag parameter of a neighboring cell cannot be automatically set. To maintain service quality, it is recommended that the neighboring cell whose NoHoFlag is set to FORBID_HO_ENUM be monitored when IntraRatNoHoSetAnrSwitch is on. This switch takes effect only when the OptMode parameter is set to FREE IntraRatDoubleThdAnrSwitch: If this switch is on and IntraRatEventAnrSwitch is on, intra-RAT neighbor relationships can be c1structed and optimized based on intra-RAT ANR measurement events. The probability to trigger intra-RAT ANR measurement can be c1figured to be higher than or equal to that of the measurement for intra-RAT coverage-based handovers. If IntraRatDoubleThdAnrSwitch is off, intra-RAT neighbor relationships cannot be c1structed or optimized based on intra-RAT ANR measurement events. In the current versi1, this switch applies only to LTE TDD cells. ServiceBasedEventAnrSwitch: If this switch is on and IntraRatEventAnrSwitch is on, service-based inter-frequency handovers can trigger ANR to add and optimize neighbor relationships with inter-frequency neighboring cells. If this switch is on and UtranEventAnrSwitch is on, service-based handovers can trigger ANR to add and optimize neighbor relationships with neighboring UTRAN cells ServiceReqEventAnrSwitch: If this switch is on and IntraRatEventAnrSwitch is on, service-based inter-frequency handovers can trigger ANR to add and optimize neighbor relationships with inter-frequency neighboring cells GUI value range: IntraRatEventAnrSwitch(IntraRatEventAnrSwitch), IntraRatFastAnrSwitch(IntraRatFastAnrSwitch), IntraRatAnrAutoDelSwitch(IntraRatAnrAutoDelSwit ch), UtranEventAnrSwitch(UtranEventAnrSwitch), GeranEventAnrSwitch(GeranEventAnrSwitch), UtranFastAnrSwitch(UtranFastAnrSwitch),

Issue 01 (2015-06-18)


59


MO

Parame ter ID

MML Comma nd

Feature ID

8 Parameters

Feature Name

Description

GeranFastAnrSwitch(GeranFastAnrSwitch), CdmaFastAnrSwitch(CdmaFastAnrSwitch), UtranAutoNrtDeleteSwitch(UtranAutoNrtDeleteSwitc h), GeranAutoNrtDeleteSwitch(GeranAutoNrtDeleteSwit ch), CdmaAutoNrtDeleteSwitch(CdmaAutoNrtDeleteSwit ch), ExtendIntraRatAnrSwitch(ExtendIntraRatAnrSwitch), CdmaEventAnrSwitch(CdmaEventAnrSwitch), MlbBasedEventAnrSwitch(MlbBasedEventAnrSwitch ), IntraRatNoHoSetAnrSwitch(IntraRatNoHoSetAnrSwi tch), IntraRatDoubleThdAnrSwitch(IntraRatDoubleThdAnr Switch), ServiceBasedEventAnrSwitch(ServiceBasedEventAnr Switch), ServiceReqEventAnrSwitch(ServiceReqEventAnrSwi tch) Unit: None Actual value range:: IntraRatEventAnrSwitch, IntraRatFastAnrSwitch, IntraRatAnrAutoDelSwitch, UtranEventAnrSwitch, GeranEventAnrSwitch, UtranFastAnrSwitch, GeranFastAnrSwitch, CdmaFastAnrSwitch, UtranAutoNrtDeleteSwitch, GeranAutoNrtDeleteSwitch, CdmaAutoNrtDeleteSwitch, ExtendIntraRatAnrSwitch, CdmaEventAnrSwitch, MlbBasedEventAnrSwitch, IntraRatNoHoSetAnrSwitch, IntraRatDoubleThdAnrSwitch, ServiceBasedEventAnrSwitch, ServiceReqEventAnrSwitch Default value: IntraRatEventAnrSwitch:Off, IntraRatFastAnrSwitch:Off, IntraRatAnrAutoDelSwitch:On, UtranEventAnrSwitch:Off, GeranEventAnrSwitch:Off, UtranFastAnrSwitch:Off, GeranFastAnrSwitch:Off, CdmaFastAnrSwitch:Off, UtranAutoNrtDeleteSwitch:On, GeranAutoNrtDeleteSwitch:On, CdmaAutoNrtDeleteSwitch:On, ExtendIntraRatAnrSwitch:Off, CdmaEventAnrSwitch:Off, MlbBasedEventAnrSwitch:Off, IntraRatNoHoSetAnrSwitch:Off,

Issue 01 (2015-06-18)


60


MO

Parame ter ID

MML Comma nd

Feature ID

8 Parameters

Feature Name

Description

IntraRatDoubleThdAnrSwitch:Off, ServiceBasedEventAnrSwitch:Off, ServiceReqEventAnrSwitch:Off ANR

ActiveP ciConfli ctSwitch

MOD ANR LST ANR

LOFD-0 02007 / TDLOF D-00200 7


Meaning: Indicates the switch used to enable or disable proactive PCI conflict detection. Within a specified duration after this switch is turned on, the eNodeB delivers measurement configurations for proactive PCI conflict detection to UEs that meet specific requirements. Then, the eNodeB starts the detection based on the measurement reports from the Ues GUI value range: OFF(Off), ON(On) Unit: None Actual value range: OFF, ON Default value: OFF(Off)

ANR

StartTim e

MOD ANR LST ANR

LOFD-0 02007 / TDLOF D-00200 7


Meaning: Indicates the start time of the active PCI conflict detection. If the stop time is earlier than or the same as the start time, the stop time is assumed to be the time of the next day GUI value range: 00:00:00~23:59:59 Unit: None Actual value range: 00:00:00~23:59:59 Default value: 14:00:00

ANR

StopTim e

MOD ANR LST ANR

LOFD-0 02007 / TDLOF D-00200 7


Meaning: Indicates the stop time of the active PCI conflict detection. If the stop time is earlier than or the same as the start time, the stop time is assumed to be the time of the next day GUI value range: 00:00:00~23:59:59 Unit: None Actual value range: 00:00:00~23:59:59 Default value: 15:00:00

IntraFre qBlkCel l

PhyCellI d

ADD INTRA FREQB LKCEL L

LBFD-0 02009 / TDLBF D-00200 9

Broadca st of system informat ion

LST INTRA FREQB LKCEL L

LBFD-0 0201801 / TDLBF D-00201 801

Coverag e Based Intra-fre quency Handov er

MOD INTRA FREQB Issue 01 (2015-06-18)

Meaning: Indicates the starting physical cell ID of the intra-frequency blacklisted cell. For details, see 3GPP TS 36.331 GUI value range: 0~503 Unit: None Actual value range: 0~503 Default value: None


61


MO

Parame ter ID

MML Comma nd

8 Parameters

Feature ID

Feature Name

Description

ADD INTRA FREQB LKCEL L

LBFD-0 02009 / TDLBF D-00200 9

Broadca st of system informat ion

Meaning: Indicates the physical cell ID range of the intra-frequency blacklisted cell. For details, see 3GPP TS 36.331

MOD INTRA FREQB LKCEL L

LBFD-0 0201801 / TDLBF D-00201 801

Coverag e Based Intra-fre quency Handov er

LKCEL L RMV INTRA FREQB LKCEL L IntraFre qBlkCel l

PhyCellI dRange

LST INTRA FREQB LKCEL L InterFre qBlkCel l

PhyCellI d

ADD INTERF REQBL KCELL

Default value: n1(n1)

Meaning: Indicates the starting physical cell ID of the inter-frequency blacklisted cell. For details, see 3GPP TS 36.331

LBFD-0 0201804 / TDLBF D-00201 804

Distance Based Inter-fre quency Handov er

Actual value range: 0~503

RMV INTERF REQBL KCELL

LBFD-0 0201805 / TDLBF D-00201 805

Service Based Inter-fre quency Handov er

ADD INTERF REQBL KCELL

LBFD-0 0201802 / TDLBF D-00201 802

Coverag e Based Inter-fre quency Handov er

LBFD-0

Distance

MOD INTERF REQBL

Issue 01 (2015-06-18)

Actual value range: n1, n4, n8, n12, n16, n24, n32, n48, n64, n84, n96, n128, n168, n252, n504

Coverag e Based Inter-fre quency Handov er

MOD INTERF REQBL KCELL

PhyCellI dRange

Unit: None

LBFD-0 0201802 / TDLBF D-00201 802

LST INTERF REQBL KCELL

InterFre qBlkCel l

GUI value range: n1(n1), n4(n4), n8(n8), n12(n12), n16(n16), n24(n24), n32(n32), n48(n48), n64(n64), n84(n84), n96(n96), n128(n128), n168(n168), n252(n252), n504(n504)

GUI value range: 0~503 Unit: None Default value: None

Meaning: Indicates the physical cell ID range of the inter-frequency blacklisted cell. For details, see 3GPP TS 36.331 GUI value range: n1(n1), n4(n4), n8(n8), n12(n12), n16(n16), n24(n24), n32(n32), n48(n48), n64(n64), n84(n84), n96(n96), n128(n128), n168(n168), n252(n252), n504(n504)


62


MO

Parame ter ID

MML Comma nd

Feature ID

Feature Name

Description

KCELL

0201804 / TDLBF D-00201 804

Based Inter-fre quency Handov er

Unit: None

LBFD-0 0201805 / TDLBF D-00201 805

Service Based Inter-fre quency Handov er

None

None

LST INTERF REQBL KCELL

LOCAT ION

LONGI TUDED EGFOR MAT

8 Parameters

ADD LOCAT ION MOD LOCAT ION

LOCAT ION

LONGI TUDES ECFOR MAT

LATIT UDEDE GFORM AT

ADD LOCAT ION

LATIT UDESE CFORM AT

Issue 01 (2015-06-18)

Meaning: Indicates the longitude of the base station. A negative value indicates the west and a positive value indicates the east Unit: 1e-6 degree Actual value range: -180~180 Default value: 0

None

None

Meaning: Indicates the longitude of the base station in the WGS-84 coordinate system GUI value range: 0~64 characters

MOD LOCAT ION

Unit: s

LST LOCAT ION

Default value: 00:00:00.0000

ADD LOCAT ION

Actual value range: 0~64 characters

None

None

MOD LOCAT ION

ADD LOCAT ION

Meaning: Indicates the latitude of the base station. A negative value indicates the south and a positive value indicates the north. GUI value range: -90000000~90000000 Unit: 1e-6 degree Actual value range: -90~90

LST LOCAT ION LOCAT ION

Default value: n1(n1)

GUI value range: -180000000~180000000

LST LOCAT ION LOCAT ION

Actual value range: n1, n4, n8, n12, n16, n24, n32, n48, n64, n84, n96, n128, n168, n252, n504

Default value: 0

None

None

Meaning: Indicates the latitude of the base station in the WGS-84 coordinate system GUI value range: 0~64 characters

MOD LOCAT ION

Unit: s

LST

Default value: 00:00:00.0000

Actual value range: 0~64 characters


63


MO

Parame ter ID

MML Comma nd

8 Parameters

Feature ID

Feature Name

Description

MOD RETDE VICED ATA

MRFD210601

Meaning: Indicates the antenna azimuth

DSP RETDE VICED ATA

WRFD060003

Connect ion with TMA (Tower Mounte d Amplifi er) Remote Electrica l Tilt

LOCAT ION RETDE VICED ATA

BEARI NG

MRFD210602

LST RETDE VICED ATA

RETDE VICED ATA

BEAM WIDTH 1

GUI value range: 0~359 Unit: degree Actual value range: 0~359 Default value: 0

Same Band Antenna Sharing Unit (900Mh z)

MOD RETDE VICED ATA

MRFD210601

LST RETDE VICED ATA

WRFD060003

MRFD210602

Connect ion with TMA (Tower Mounte d Amplifi er) Remote Electrica l Tilt

Meaning: Indicates the beamwidth of band 1. Beamwidth is used to describe the capability of the antenna to transmit RF signals. It is also used to measure the antenna pattern. GUI value range: 0~359 Unit: degree Actual value range: 0~359 Default value: 0

Same Band Antenna Sharing Unit (900Mh z) RET

DEVIC ENO

ADD RET

MRFD210601

DLD ALDSW

WRFD060003

DSP ALDVE R DSP RET

Issue 01 (2015-06-18)

Connect ion with TMA (Tower Mounte d Amplifi er) Same Band

Meaning: Indicates the device number of the ALD. The device number of the ALD must be unique GUI value range: 0~125 Unit: None Actual value range: 0~125 Default value: None


64


MO

Parame ter ID

MML Comma nd

Feature ID

LST RET

8 Parameters

Feature Name

Description

Antenna Sharing Unit (900Mh z)

MOD RET RMV RET RST ALD RETSU BUNIT

SUBUN ITNO

CLB RET DLD RETCF GDATA DSP RETSU BUNIT

LOFD-0 01024 / TDLOF D-00102 4

Remote Electrica l Tilt Control

Meaning: Indicates the number of the RET subunit, which starts from 1 GUI value range: 1~8 Unit: None Actual value range: 1~8 Default value: None

LST RETSU BUNIT MOD RETSU BUNIT

Issue 01 (2015-06-18)


65


9 Counters

9

Counters

There are no specific counters associated with this feature.

Issue 01 (2015-06-18)


66


10 Glossary

10

Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 01 (2015-06-18)


67


11

11 Reference Documents

Reference Documents

1.

ANR Management Feature Parameter Description of the corresponding eRAN version.

Issue 01 (2015-06-18)


68

LTE PCI Self-Optimization Feature (V100R015C10_01)(PDF)-En

Recommend Documents