SJ-20130524154927-017-NetNumen U31 R18 (V12.12.43) Operation Guide

NetNumen™ U31 R18
Unified Element Management System

Operation Guide for SON
Version: V12.12.43
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.5 2014-06-30 Modified "Appendix B PCI Failure Information Description".
R1.4 2014-04-15 Modified "Appendix A ANR Failure Information Description".
R1.3 2014-04-03 The following contents have been modified:

l Appendix A ANR Failure Information Description
l Appendix B PCI Failure Information Description
R1.2 2013-12-25 Modified "Appendix A ANR Failure Information Description".
R1.1 2013-10-17 The following contents have been added:
l Chapter 8 Son Log Query

l Appendix A ANR Failure Information Description
l Appendix B PCI Failure Information Description
R1.0 2013-06-30 First edition.
Serial Number: SJ-20130524154927-017
Publishing Date: 2014-06-30 (R1.5)
SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Basic Concepts .................................................................................................. 1-1
1.2 SON Configuration Window ................................................................................ 1-4
Chapter 2 ANR Policy Management.......................................................... 2-1

2.1 Setting an ANR Policy ........................................................................................ 2-1
2.2 Turning On the ANR Message Report Switch ....................................................... 2-9
2.3 Monitoring ANR Messages ............................................................................... 2-13
2.4 Viewing Neighbor Relations .............................................................................. 2-15
Chapter 3 PCI Policy Management ........................................................... 3-1

3.1 Setting a PCI Policy............................................................................................ 3-1
3.2 Turning On the PCI Message Report Switch ........................................................ 3-6
3.3 Monitoring PCI Messages ................................................................................... 3-8
3.4 Checking Cell PCI Modification ..........................................................................3-11
Chapter 4 MRO Policy Management ......................................................... 4-1

4.1 Setting an MRO Policy........................................................................................ 4-1
4.2 Turning On the MRO Message Report Switch ...................................................... 4-8
4.3 Monitoring MRO Messages................................................................................4-11
4.4 Checking MRO Parameter Modification ............................................................. 4-12
Chapter 5 X2 Policy Management ............................................................. 5-1

5.1 Setting an X2 Policy ........................................................................................... 5-1
5.2 Turning On the X2 Message Report Switch .......................................................... 5-5
5.3 Monitoring X2 Messages .................................................................................... 5-8
5.4 Checking X2 Connections................................................................................. 5-10
Chapter 6 PnP Policy Management .......................................................... 6-1

6.1 Setting a PnP Policy ........................................................................................... 6-1
6.2 Monitoring PnP Messages .................................................................................. 6-6
6.3 Checking Automatic eNodeB Commissioning....................................................... 6-9
Chapter 7 Policy Query .............................................................................. 7-1

7.1 Querying SON Polices........................................................................................ 7-1
7.2 Querying Switch Polices ..................................................................................... 7-3
Chapter 8 SON Log Query ......................................................................... 8-1

Appendix A ANR Failure Information Description ................................. A-1
Appendix B PCI Failure Information Description ................................... B-1
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII
II

About This Manual
Purpose
This manual describes how to configure Self-Organizing Network (SON) features for MO
SDR base stations (ZTE MO eNodeBs) in the NetNumenTM U31 R18 Unified Element
Management System (NetNumen U31).
Intended Audience
This manual is intended for:
l Base station commissioning engineers

l Maintenance engineers
l Network management engineers
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
1, Overview Provides an overview of SON management in the NetNumen

U31 system, including SON features, related concepts, and
the SON configuration window.
2, ANR Policy Management Describes the operations related to ANR policy management.
3, PCI Policy Management Describes the operations related to PCI policy management.
4, MRO Policy Management Describes the operations related to MRO policy management.
5, X2 Policy Management Describes the operations related to X2 policy management.
6, PnP Policy Management Describes the operations related to PnP policy management.
7, Policy Query Describes how to query the configured SON policies and switch
policies.
8, SON Log Query Describes how to query SON logs.
Appendix A, ANR Failure Describes ANR failure information.

Information Description
Appendix B, PCI Failure Information Describes PCI failure information.

Description
Conventions
This manual uses the following typographical conventions:

Typeface Meaning
Bold Menus, menu options, function names, input fields, option button
names, check boxes, drop-down lists, dialog box names, window
names, parameters, and commands.
Constant width Text that you type, program codes, filenames, directory names, and
function names.
Note: provides additional information about a certain topic.
II

Chapter 1
Overview
Self-Organizing Network (SON) management enables the system to automatically detect
and solve network problems in accordance with the configured policies. This ensures that
the network can operate in the optimal status in unattended mode.
SON provides the following features: Automatic Neighbor Relation (ANR) optimization,
Physical Cell Identity (PCI) optimization, Mobility Robustness Optimization (MRO), X2
connection setup, and Plug and Play (PnP). The actually available features depend on
the on-site situation.
The procedures for deploying Frequency Division Duplex (FDD) and Time Division Duplex
(TDD) eNodeBs are the same. This manual assumes that FDD eNodeBs are to be
deployed.
Table of Contents
Basic Concepts ..........................................................................................................1-1
SON Configuration Window........................................................................................1-4
1.1 Basic Concepts

The following explains basic concepts related to SON features:
ANR
The Automatic Neighbor Relation (ANR) policy is used to establish neighbor relations
automatically. From the measurement reports submitted by User Equipment (UEs) to the
Evolved NodeB (eNodeB), the SON discovers unknown neighbor cells. The local eNodeB
obtains the information about these unknown neighbor cells from the eNodeBs where these
neighbor cells are located, and triggers neighbor cell relation setup.
Neighbor cell relations can be established in controlled and free modes.
After the number of co-frequency neighbor cells of an eNodeB reaches the threshold,
the flow for adding neighbor cells triggers that for deleting neighbor cells. After a certain
number of neighbor cells are deleted, new neighbor cells can be added.
The ANR policy supports the following functions:
l Automatically discovers neighbor cells and maintains the integrity and validity of the
neighbor relation table, thus reducing call drop rate and improving handover success
rate.
l Reduces the operation cost by reducing the expense on network planning and
optimization personnel.
1-1

NetNumen™ U31 R18 Operation Guide for SON
MRO
The MRO feature reduces handover failures and improves resource utilization.
During an MRO process, the system detects and collects statistics of handover failures
and unnecessary handovers, determines the failure type, counts the failure occurrence in
a specified period, and then optimizes the parameters to avoid the failures.
There are four types of handover failures:
l Too-late handover: Before or during a UE handover, a radio link failure occurs in the
source cell, and the re-establishment process is initiated in the target cell.
l Too-early handover: During or after a UE handover, a radio link failure occurs in the
source or target cell, and the re-establishment process is initiated in the source cell.
l Handover to a wrong cell: During or after a UE, a radio link failure occurs in the source
or target cell, and the re-establishment process is initiated in a third cell.
l Repeated handover: A UE is frequently handed over between two cells due to similar
signal strength when the UE is located in the overlapped coverage area of these two
cells. Repeated handover costs system resources.
The MRO operation logs are saved for convenience of future query.
PCI Optimization
A Physical Cell Identity (PCI) uniquely identifies a cell.
When the PCIs of two adjacent cells conflict, a PCI message is reported. In accordance
with the PCI policy, the SON modifies the cell PCIs to eliminate the conflict or confusion.
Two types of PCI policies are available:
l Distributed: The eNodeB randomly selects a PCI from the PCI list.
l Centralized: The NetMAX network optimization system allocates PCIs to eNodeBs in
a unified manner. eNodeBs cannot select PCIs randomly.
X2 Connection Setup
X2 connection refers to the linking between eNodeBs. It is used for direct communication
between cells managed by different eNodeBs.
After an X2 policy is configured, X2 connection setup will be triggered if neighbor cell
relations are established between different eNodeBs.
In either of the following cases, X2 connection establishment is not required:
l An X2 connection already exists between the two eNodeBs involved in a neighbor cell
relation.
l The two cells involved in a neighbor cell relation are managed by the same eNodeB.
PnP
The Plug and Play (PnP) feature enables eNodeBs to be deployed automatically in
the NetNumen U31 system after being powered on. This function is applicable to all
eNodeB versions. Based on the PnP policy, the eNodeB automatically establishes a
1-2

Chapter 1 Overview
communication link with the Operation and Maintenance Center (OMC), obtains the latest
version and configuration files, and automatically activates the versions and synchronizes
data.
Before configuring a PnP policy, ensure that the following conditions are met:
l The required software version is uploaded to the OMC server.
l The required configuration data is available in the modification area and the radio
resource is configured.
The PnP policy has the following advantages:
l Reduces repeated labor
l Simplifies the process for connecting eNodeBs to the EMS
l Reduces the wireless network operation cost.
Policy Template
Policy templates are used to set the parameters required for SON service operation and to
control whether to enable the SON service. Users can configure ANR, PCI, MRO, X2, or
PnP policy templates as required, and then issue the templates to the corresponding NEs,
radio system, or cells to apply the parameters. In this way, the operation of SON services
can be controlled.
Switch Policy
The NetNumen U31 system supports creating switch policies to enable or disable different
SON features except PnP.
l A switch policy determines whether a SON policy is enabled for deploying the
corresponding feature. After an ANR, PCI, MRO, or X2 policy is deployed on an NE
or cell, the corresponding switch policy must be enabled to validate the feature.
l No switch policy is required for a PnP policy. The PnP policy is used for automatic
commissioning of eNodeBs on which no version is available to receive a switch policy.
After the eNodeBs are successfully commissioned, the corresponding PnP policy is
of no use.
Policy Configuration Granularity

SON policies can be configured at the levels of cell, radio access system, and NE.
l ANR, PCI, and MRO policies: The smallest granularity is cell level. The radio access
system level is also applicable.
l X2 and PnP policies: The smallest granularity is radio access system level. No other
levels are applicable.
All switch policies are configured at radio access system level.
1-3

Reference Point and Breakpoint

l Reference point: To make SON service operation manually controllable, the system
predefines multiple points for the SON service flow. These points are called reference
points.
l Breakpoint: When a controlled service reaches a reference point, the service is
paused and waits for users to determine whether to proceed with or stop the process.
These reference points are called breakpoints.
Controlled Mode
Controlled mode is a SON service operation mode.
If a SON service is set to the controlled mode, the breakpoint settings take effect and the
service operation is controlled manually.
Free Mode
Free mode is a SON service operation mode.
In this mode, breakpoints are invalid and the service operation cannot be controlled by
users.
1.2 SON Configuration Window

Before configuring SON features for MO SDR base stations, you must open the SON
configuration window on the NetNumen U31 client. Either of the following methods can be
used to open the SON configuration window:
l Select Configuration > MO SDR SON Configuration Application > MO SDR SON
Configuration Application from the menu bar.
l Click on the toolbar.
Figure 1-1 shows the MO SDR SON Configuration Application window.
1-4

Chapter 1 Overview
Figure 1-1 MO SDR SON Configuration Application Window
The MO SDR SON Configuration Application window has two panes:

l The left SON Management Tree pane displays all available SON functions.
l The right function display pane displays the corresponding function details after a node
in the SON Management Tree pane is double-clicked.
For example, after the SON Monitor Management > Real-Time Monitoring >
Optimization Monitoring in the left SON Management Tree pane is double-clicked, the
Optimization Monitoring tab is displayed in the right pane, see Figure 1-2.
1-5

Figure 1-2 Optimization Monitoring Tab
1-6

Chapter 2
ANR Policy Management
Table of Contents
Setting an ANR Policy ................................................................................................2-1
Turning On the ANR Message Report Switch .............................................................2-9
Monitoring ANR Messages .......................................................................................2-13
Viewing Neighbor Relations......................................................................................2-15
2.1 Setting an ANR Policy

This procedure describes how to set an Automatic Neighbor Relation (ANR) policy and
apply the policy to specific cells (for example, eNodeBs 147 and 161).
Steps
1. On the NetNumen U31 client, select Configuration > MO SDR SON Configuration
Application > MO SDR SON Configuration Application from the menu bar. The
MO SDR SON Configuration Application window is displayed.
2. In the left SON Management Tree, double-click SON Policy Management > SON
Policy Template, and then double-click Managed Element > LTE FDD > E-UTRAN
FDD Cell > FDD ANR Policy under the Policy Tree tab. The FDD ANR Policy tab is
displayed in the right pane, see Figure 2-1.
2-1

Figure 2-1 FDD ANR Policy Tab
3. Click on the toolbar. The FDD ANR Policy dialog box is displayed, see Figure 2-2.
Figure 2-2 FDD ANR Policy Dialog Box
2-2

Chapter 2 ANR Policy Management
For a description of the parameters in the FDD ANR Policy dialog box, refer to Table
2-1.
Table 2-1 Parameters for Setting an FDD ANR Policy
Parameter Description
Template ID Uniquely identifies a policy template.
Template Name Specifies the ANR policy template name. The recommended
name format is “radio system_ANR_operation mode”, for example,
FDD_ANR_Con.
Service Type Fixed to ANR.
Run Mode Specifies the processing mode of the ANR policy when an ANR
message is received.
l Free mode: The system directly implements the ANR policy
upon receiving the ANR message.
l Controlled mode: After the system receives the ANR message,
how to implement the ANR policy is manually controlled.
ANR Refer Point Policy Sets the reference points, which are used to determine whether
each step in the ANR policy is a breakpoint for user’s confirmation
when the ANR policy is in controlled mode.
Click . In the displayed SON Refer Point Attribute Table
dialog box, set the required breakpoints, see Figure 2-3.
The rows with a green background can be modified.
ANR Enable Enables or disables the ANR function. When Enable is selected
from the drop-down list, the ANR policy is validated and the ANR
reports messages.
ANR Min DRX Cycle Specifies the minimum Discontinuous Reception (DRX) length. It
is an eNodeB algorithm parameter used for filtering the UEs for
ANR optimization measurement.
Value range: 0–65535.
Default: 150.
The default value is recommended and no modification is required.
ANR Measure Object Specifies the maximum number of UE selection attempts.

Choice Counter Value range: 1–65535.
Default: 9.
2-3

Neighbor Report Threshold Threshold of the number of times that a neighbor cell is reported.
It is used with the parameter Handover Success Threshold in
eNodeB algorithm. When the number of times that an unknown
neighbor cell is reported exceeds both Neighbor Report
Threshold and Handover Success Threshold, this neighbor cell
is added to the temporary neighbor cell list.
Default: 30.
Handover Success Threshold of handover successes. It is used with the parameter

Threshold Neighbor Report Threshold in eNodeB algorithm. When the
number of successful handovers to the neighbor cell exceeds both
Handover Success Threshold and Neighbor Report Threshold,
this neighbor cell changes from a temporary neighbor cell to a
formal one.
Default: 6.
Intra-LTE ANR Self-Delete Switch for automatically deleting neighbor cells in the LTE system.
Switch After this parameter is set to Open, if the number of LTE neighbor
cells of an LTE FDD cell reaches the threshold (The Number of
Neighbor Cell to Trigger ANR Self-Delete Function), the system
automatically deletes the unqualified neighbor cells according to
the KPI. This also applies to LET TDD cells.
The default setting is Close.
Intra-system GSM ANR Switch for enabling the ANR auto-optimization function for GSM
Switch neighbor cells of an LTE NE. When the switch is turned on,
automatic optimization of neighbor cells will be triggered when
Neighbor Report Threshold and Handover Success Threshold
are reached.
Inter-system GSM ANR Switch for automatically deleting GSM neighbor cells of an LTE NE.
Self-Delete Switch When the switch is turned on, automatic deletion of neighbor cells
will be triggered when the specified threshold (The Number of
Neighbor Cell to Trigger ANR Self-Delete Function) is reached.
2-4

Inter-system UTRAN ANR Switch for enabling the ANR auto-optimization function for UTRAN
are reached.
Inter-system UTRAN ANR Switch for automatically deleting UTRAN neighbor cells of an LTE
Self-Delete Switch NE. When the switch is turned on, automatic deletion of neighbor
cells will be triggered when the specified threshold (The Number of
Intra-LTE Neighbor Cell Controls whether two cells are configured as mutual neighbor
Relation Bidirectional cells. The default is Close.
Configuration Switch For example, the policy is set for cell B and this parameter is set
to Open. When cell A receives an ANR message and adds cell
B to its neighbor cell list, cell B adds cell A as its neighbor cell
at the same time.
Timer Length for ANR Specifies the time in hour for collecting statistics on an ANR
Temporary Neighbor Cell temporary neighbor cell.
Statistic (Hour) If an unknown neighbor cell is found at the NE side, the system first
adds the cell to the temporary neighbor cell list, and then collects
statistics on the KPIs of the cell based on the parameter value. If
the KPIs meet the requirement, the cell is reported to the NMS and
validated as a formal neighbor cell.
Default: 24.
HO Times Threshold to Specifies the threshold number of handover times, which must
Modify NoHo Attribute be reached so that the NoHo attributes of a neighbor cell can be
modified.
The NE summarizes the number of handovers and handover failure
ratios of a formal neighbor cell in a period. If the two thresholds
are exceeded, the NE sends a request indicating that the neighbor
NoHo attribute needs modification.
Default: 50.
2-5

HO Failure Ratio Threshold Specifies the threshold of handover failure ratio, which must be
to Modify NoHo Attribute reached so that the NoHo attributes of a neighbor cell can be
(%) modified.
The NE summarizes the number of handovers and handover failure
ratios of a formal neighbor cell in a period. If the two thresholds
are exceeded, the NE sends a request indicating that the neighbor
NoHo attribute needs modification.
Default: 80.
Inter-System CDMA ANR Switch for enabling the ANR auto-optimization function for CDMA
are reached.
Inter-System CDMA ANR Switch for automatically deleting CDMA neighbor cells of an LTE
Self-Delete Switch NE. When the switch is turned on, automatic deletion of neighbor
cells will be triggered when the specified threshold (The Number of
The Number of Neighbor Specifies the number of neighbor cells that can trigger ANR
Cell to Trigger ANR self-deletion function.
Self-Delete Function The value range is 1–32. Use the default 30 generally.
Default: 30.
Timer Length for ANR After a temporal ANR neighbor cell is added, the eNodeB starts
Self Delete Neighbor Cell the statistic timer to count its measurement reports and handover
Statistic successes. After the timer expires, only the temporal neighbor
cells whose numbers of measurement reports and handover
successes both meet the specified thresholds can be added as
formal neighbor cells.
Unit: hour
The Grade of ANR Statistic Sets the time granularity of ANR statistics.
Timer Length
The Total HO Counter Sets the threshold of handover count for deleting a neighbor cell.
Threshold for Neighbour When the ANR self-deletion statistics end, if the total number of
Cell Delete handovers from the serving cell to a neighbor cell is smaller than
this threshold, the neighbor cell can be deleted.
2-6

The Maximum Number Sets the maximum number of neighbor cells that can be deleted
of Neighbour Cell Delete each time.
Once If the number of neighbor cells meeting the deletion conditions
exceeds the threshold, the neighbor cell with the smallest number
of MR reports is deleted first.
NoHo Attribute Modify Controls whether to enable the NoHO attribute modification
Switch function.
Timer Length for NoHo Sets the time length of the neighbor NoHO attribute modification
Attribute Modify Statistic statistic timer.
After NoHo Attribute Modify Switch is set to Open, the static
timer starts. When handover occurs during the statistical period,
the system counts the total number of handovers and calculates
the handover failure rate. If both the total number of handovers
and failure rate reach the thresholds, the system modifies the
NoHO attribute.
Control ANR Switch by Controls whether to modify the cell’s ANR switch during self-healing
Self-healing compensation.
Figure 2-3 SON Refer Point Attribute Table Dialog Box
4. Click OK. The new ANR policy is displayed on the FDD ANR Policy tab, see Figure
2-4.
2-7

Figure 2-4 FDD ANR Policy Tab (with the New ANR Policy)
5. Click the added ANR policy, and then click on the toolbar. The Set dialog box is
displayed, see Figure 2-5.
Figure 2-5 Set Dialog Box
6. Select the cells or NEs on which the ANR policy is to take effect, and then click OK.
After the ANR policy takes effect on the target cells, Succeed is displayed in the Result
column in the lower part of FDD ANR Policy tab, see Figure 2-6.
2-8

Figure 2-6 ANR Policy Configuration Success
– End of Steps –
2.2 Turning On the ANR Message Report Switch

This procedure describes how to turn on the ANR message report switch and send the
switch configuration to specific eNodeBs.
Steps
1. In the MO SDR SON Configuration Application window, double-click SON Policy
Template in the left SON Management Tree pane. The SON Policy Template tab is
displayed in the right pane.
2. On the SON Policy Template tab, double-click Managed Element > LTE FDD > FDD
SON Control in the Policy Tree pane. The FDD SON Control tab is displayed, see
Figure 2-7.
2-9

Figure 2-7 FDD SON Control Tab
3. Click on the toolbar. The FDD SON Control dialog box is displayed, see Figure 2-8.
Figure 2-8 FDD SON Control Dialog Box
For a description of the parameters in the FDD SON Control dialog box, refer to Table
2-2.
Table 2-2 Parameters for Configuring FDD Switch
2-10

Template Name Specifies the switch template name. The recommended

name format is “FDD_function_switch mode”, for example,
FDD_ANR_Open.
Service Type Provides the available switch policy types.

Select ANR from the drop-down list.
Service Switch Turns on or off the switch.

Select Open from the drop-down list.
4. Set the required parameters, and then click OK. The added ANR message report
switch is displayed on the FDD SON Control tab, see Figure 2-9.
Figure 2-9 Added ANR Message Report Switches
5. Click the newly added switch, and then click on the toolbar. The Set Policy dialog
box is displayed, see Figure 2-10.
2-11

Figure 2-10 Set Policy Dialog Box
6. Select the eNodeBs that the ANR switch configuration will be sent to, and then click
OK. After the ANR switch configuration is successfully sent to the eNodeBs, Succeed
is displayed in the Result column, see Figure 2-11.
Figure 2-11 Successfully Sending the ANR Switch Configuration
2-12

After the ANR policy and message report switch are distributed successfully, if
an eNodeB reports an ANR message requesting for adding a neighbor cell, the
corresponding neighbor cell relation is established.
2.3 Monitoring ANR Messages

This procedure describes how to monitor the received ANR messages, and process them
based on the mode selected in the ANR policy.
l If the ANR policy is set to free mode, the system automatically processes the reported
message and adds the neighbor relation.
l If the ANR policy is set to controlled mode, the ANR message is processed in steps
confirmed by users.
Steps
1. In the MO SDR SON Configuration Application window, right-click SON Monitor
Management > Real-Time Monitoring > Optimization Monitoring in the left SON
Management Tree. The Optimization Monitoring tab is displayed, containing the
traced messages, see Figure 2-12.
2-13

Note:
You can click an ANR message to view related information in the lower part. The
Monitor Step Information sub-tab shows the processing steps, and the Monitor
Detail Information sub-tab shows the message details.
2. Double-click an ANR message, the Show Details dialog box is displayed. The dialog
box gives the details, for example, indicating that neighbor cells need to be added to
eNodeB 147, see Figure 2-13.
Figure 2-13 Show Details Dialog Box
For more information, please refer to Appendix A ANR Failure Information Description.
3. Right-click the ANR message, and perform the required operations.
The shortcut menu items vary depending on the policy operation mode.
l If the ANR policy of the eNodeB involved in the ANR message is set to free mode,
View and Batch Export items are available.
l If the ANR policy of the eNodeB involved in the ANR message is set to controlled
mode, all items are available.
For a detailed description of the menu items, refer to Table 2-3.
2-14

Table 2-3 Shortcut Menu Items of an ANR Message
Shortcut Menu Item Description
View Checks the monitoring message details.
Acknowledged-Continue Acknowledges the operation of proceeding the steps.
Acknowledged-Cancel Acknowledges the cancellation of performing the steps and closes

the message.
Redo Performs the steps again.
Alter Params Modifies the parameters.

Click a controlled ANR message whose parameters are being
distributed, and then click Alter Params. In the displayed dialog
box, modify the parameters to be distributed.
Batch Export Displayed when users right-click in the traced message area. It is
used to export all controlled messages in batches to a specified
Excel file in the local computer.
Batch Import Displayed if users right-click in the traced message area after the
parameters in the bulk exported Excel file are modified. This menu
item is used to import all controlled messages into the NetNumen
U31 to validate the parameters.
After the ANR message is completely processed, 100% is displayed in the Progress
column.
2.4 Viewing Neighbor Relations

This procedure describes how to verify that an ANR policy is correctly configured by
checking the corresponding neighbor relation.
Prerequisite
The Configuration Management window is open.
Steps
1. In the NE tree, click Modify Area$0 under the eNodeB 147 node. Then, in the
Managed Element tree, double-click Radio Parameter > LTE FDD > Neighbor Cell
Configuration > E-UTRAN FDD Neighbor Cell. The E-UTRAN FDD Neighbor
Cell-List tab is displayed, showing all neighbor cells of eNodeB 147, see Figure 2-14.
2-15

Figure 2-14 E-UTRAN FDD Neighbor Cell-List Tab
2. Double-click a record. The E-UTRAN FDD Neighbor Cell tab is displayed, showing
the details of the neighbor cell, see Figure 2-15.
Figure 2-15 E-UTRAN FDD Neighbor Cell Tab
If cells under eNodeB 161 are configured as the neighbor cells of eNodeB 147, infer
that the neighbor cell relation is correct.
2-16

Chapter 3
PCI Policy Management
Table of Contents
Setting a PCI Policy....................................................................................................3-1
Turning On the PCI Message Report Switch...............................................................3-6
Monitoring PCI Messages ..........................................................................................3-8
Checking Cell PCI Modification ................................................................................3-11
3.1 Setting a PCI Policy

This procedure describes how to set a Physical Cell Identity (PCI) policy and apply the
policy to specific cells (for example, eNodeBs 147 and 161).
Steps
Policy Template.
3. In the expanded Policy Tree, double-click Managed Element > LTE FDD > E-UTRAN
FDD Cell > FDD PCI Policy. The FDD PCI Policy tab is displayed in the right pane,
see Figure 3-1.
3-1

Figure 3-1 FDD PCI Policy Tab
4. Click on the toolbar. The FDD PCI Policy dialog box is displayed, see Figure 3-2.
Figure 3-2 FDD PCI Policy Dialog Box
3-2

Chapter 3 PCI Policy Management
For a description of the parameters in the FDD PCI Policy dialog box, refer to Table
3-1.
Table 3-1 Parameters for Setting a FDD PCI Policy
Template Name Specifies the PCI policy template name. The recommended name format
is “radio system_PCI_operation mode”, for example, FDD_PCI_Con.
Service Type Fixed to PCI.
Run Mode Specifies the processing mode of the PCI policy when the EMS receives
an ANR message.
l Free mode: The system directly implements the PCI policy upon
receiving the PCI message.
l Controlled mode: After the system receives the PCI message, how
to implement the ANR policy is manually controlled.
PCI Refer Point Sets the reference points, which are used to determine whether each
Policy step in the PCI policy is a breakpoint for user’s confirmation when the
policy is in controlled mode.
Click . In the displayed SON Refer Point Attribute Table dialog
box, set the required breakpoints, see Figure 3-3.
PCI Enable Disables or disabled the PCI policy.

l After this parameter is set to Enable, the PCI policy is validated.
l After this parameter is set to Enable and the PCI message report
switch is enabled, PCI messages can be reported.
Resolve Manner Indicates the solution to PCI conflict or confusion. The options are:
when PCI is Conflict l Resolved by centralization: The NetNumen U31 system uniformly
or Confusion allocates PCIs in accordance with the algorithm.
l Resolved by distributed: The eNodeBs respectively select available
PCIs from the PCI list.
Enable to Detect Enables or disables PCI detection. When this parameter is set to Open,
Neighbor Cell By UE UEs are used to detect whether conflicts exist between a cell using the
PCI policy and its corresponding neighbor cells.
Periodic Number of Specifies the times for detecting PCI conflicts through UEs after an
Detect Neighbor Cell eNodeB is started. It is an eNodeB algorithm parameter.
By UE The value range is 0–255, with 5 as the default.
Resolving PCI The switch for resolving PCI conflicts at the scheduled time .
Conflict or Confusion If this parameter is set to Open, in free mode, the system resolves PCI
at The Appointed conflicts at the time point defined by the The Appointed Time Used to
Time Switch Resolving PCI Conflict or Confusion parameter. This is not applicable
to controlled mode.
3-3

The Appointed Time Specifies the time when the system starts to resolve PCI conflicts. It
Used to Resolving is applicable when the Resolving PCI Conflict or Confusion at The
PCI Conflict or Appointed Time Switch is set to Open. The default is 2, indicating
Confusion 02:00.
The Appointed Time Specifies the time when the UE starts to detect whether a neighbor has
Used to Detecting been configured with a time point for resolving PCI conflicts and whether
Neighbour Cell by PCI conflicts exist when the pre-defined time arrives. The default is 10,
UE indicating 10:00.
5. Set the required parameters, and click OK. The new PCI policy is displayed on the
FDD PCI Policy tab, see Figure 3-4.
Figure 3-4 FDD PCI Policy Tab (with the New PCI Policy)
6. Click the new PCI policy, and then click on the toolbar. The Set dialog box is
3-4

7. Set the cell on which the PCI policy is to take effect, and then click OK. After The
PCI policy is successfully configured, Succeed is displayed in the Result column, see
Figure 3-6.
Figure 3-6 PCI Policy Configuration Success
3-5

3.2 Turning On the PCI Message Report Switch

This procedure describes how to turn on the PCI message report switch, and distribute the
configuration data to the specified eNodeB.
Steps
Template in the left SON Management Tree.
2. In the Policy Tree, double-click Managed Element > LTE FDD > FDD SON Control.
The FDD SON Control tab is displayed in the right pane, see Figure 3-7.
3. Click on the toolbar. The FDD SON Control dialog box is displayed, see Figure
3-8.
3-6

3-2.
Table 3-2 Parameters for Setting a PCI Message Report Switch
Template Name Specifies the switch template name, which is recommended to use the
format “FDD_function_switch mode”, for example, FDD_PCI_Open.
Service Type Specifies the switch policy type. Set it to PCI.
Service Switch Opens or closes the switch. Set it to Open.
4. Set the PCI parameters, and click OK. The new PCI message report switch is
displayed on the FDD SON Control tab, see Figure 3-9.
Figure 3-9 FDD SON Control Tab (with New PCI Message Report Switch)
5. Click the new switch, and then click on the toolbar. The Set dialog box is displayed.
6. Set the eNodeB to which the PCI switch is to be distributed, and then click OK. After
the PCI switch is successfully distributed to the eNodeBs, Succeed is displayed in the
Result column, see Figure 3-10.
3-7

Figure 3-10 Successfully Distributed PCI Switch
After the PCI policy and message report switch are distributed successfully, if PCIs
conflict, the eNodeB reports a PCI message, triggers resolution mechanism, and
re-allocates PCIs.
3.3 Monitoring PCI Messages

This procedure describes how to monitor a PCI message and process it based on the
mode selected in the PCI policy.
l If the PCI policy is set to free mode, the system automatically processes the reported
message as the policy specifies.
l If the PCI policy is set to controlled mode, the PCI message is processed in steps
confirmed by users.
Steps
1. In the MO SDR SON Configuration Application window, double-click SON Monitor
Management Tree. The Optimization Monitoring tab is displayed in the right pane,
showing all the traced messages, see Figure 3-11.
3-8

Note:
You can click a PCI message and view the details in the lower part. The Monitor Step
Information sub-tab shows the processing steps, and the Monitor Detail Information
sub-tab shows the message details.
2. Double-click a PCI. The Show Details dialog box is displayed, see Figure 3-12.
3-9

The PCI message in Figure 3-12 indicates that a cell of eNodeB 161 has PCI conflicts
with other cells. According to the distributed PCI policy, the eNodeB allocates 0 as the
new PCI.
For more information, please refer to Appendix B PCI Failure Information Description.
3. Right-click the PCI message, and perform the required operations.
The shortcut menu items vary depending on the policy operation mode, refer to Table
3-3.
Table 3-3 Shortcut Menu Items of a PCI Message
Acknowledged-Cancel Acknowledges the cancellation of performing the steps and

closes the message.
3-10


Click a controlled PCI message whose parameters are
being issued, and then click Alter Params. In the displayed
dialog box, modify the parameters to be issued.
Batch Export Displayed when users right-click in the traced message

area. It is used to export all controlled messages in batches
to a specified Excel file in the local computer.
Batch Import Displayed if users right-click in the traced message

area after the parameters in the bulk exported Excel
file are modified. This menu item is used to import all
controlled messages into the NetNumen U31 to validate
the parameters.
l If the PCI policy mode of the eNodeBs involved in the PCI message is set to
controlled mode, right-click the PCI message and then click a menu item to
perform the corresponding operation.
l If the PCI policy mode of the eNodeBs involved in the PCI message is set to free
mode. the system directly implements the policy.
After the message is completely processed, 100% is displayed in the Progress
column.
3.4 Checking Cell PCI Modification

This procedure describes how to verify that a PCI policy is correct by checking the PCI
modification.
Prerequisite
Steps
1. In the NE tree, click Modify Area$0 under the eNodeB 161 node.
2. In the Managed Element tree, double-click Radio Parameter > LTE FDD > E-UTRAN
FDD Cell. The E-UTRAN FDD Cell-List tab is displayed in the right pane, listing all
cells under eNodeB 161, see Figure 3-13.
3-11

Figure 3-13 E-UTRAN FDD Cell-List Tab
3. Double-click a record. The E-UTRAN FDD Cell tab is displayed, showing the details
of the selected cell, see Figure 3-14.
3-12

Figure 3-14 E-UTRAN FDD Cell Tab
The PCI of the conflicted cell is changed to 0, indicating that the PCI policy is correctly
configured.
3-13

This page intentionally left blank.
3-14

Chapter 4
MRO Policy Management
Table of Contents
Setting an MRO Policy ...............................................................................................4-1
Turning On the MRO Message Report Switch ............................................................4-8
Monitoring MRO Messages ......................................................................................4-11
Checking MRO Parameter Modification....................................................................4-12
4.1 Setting an MRO Policy

This procedure describes how to set an MRO policy and apply the policy to specific cells.
Steps
Policy Template.
3. In the expanded Policy Tree, double-click Managed Element > LTE FDD > FDD MRO
Policy. The FDD MRO Policy tab is displayed, see Figure 4-1.
4-1

Figure 4-1 FDD MRO Policy Tab
4. Click on the toolbar. The FDD MRO Policy dialog box is displayed, see Figure 4-2.
4-2

Chapter 4 MRO Policy Management
Figure 4-2 FDD MRO Policy Dialog Box
For a description of the parameters in the FDD MRO Policy dialog box, refer to Table
4-1.
Table 4-1 Parameters for Setting an FDD MRO Policy
Template Name Specifies the MRO policy template name, which is recommended
to use the format “radio system_MRT_operation mode”, for
example, FDD_MRO_Con.
Service Type Fixed to MRO.
Run Mode Specifies the processing mode of the MRO policy when the EMS
receives an MRO message.
l Free mode: The system directly implements the MRO policy
upon receiving the MRO message.
l Controlled mode: After the system receives the MRO
message, how to implement the MRO policy is manually
controlled.
4-3

MRO Refer Point Policy Sets the reference points, which are used to determine whether
each step in the MRO policy is a breakpoint for user’s confirmation
when the policy is in controlled mode.
MRO Enable Disables or disabled the MRO policy.

l After this parameter is set to Enable, the MRO policy is
validated.
l After this parameter is set to Enable and the MRO message
report switch is enabled, MRO messages can be reported.
Timer of eNodeB Statistics Sets the period of cell handover fault statistics.
MRO Error Information The eNodeB counts the same cell handover fault that occurs
(Hour) in the specified cell in the period. If the number reaches the
threshold, the MRO function is automatically triggered.
Range: 1–255.
Default: 24.
The Minimum Time Interval Sets the minimum interval between two MRO parameter
Between MRO Parameter optimizations.
Optimization (Hour) Range: 1–255.
Default: 48.
The Maximum Value Sets the maximum value that can MRO parameter optimization
Adjusted By MRO be adjusted after MRO parameter is triggered only when all the
Parameter Optimization optimization is triggered. three conditions are met.
(dB) Range: 1–10.
Default: 6.
The Distinguish Threshold Sets the threshold for determining

of Parameter Optimization parameter optimization type.
Type In the statistical period, the NE
calculates the ratio of all types
of handover faults (too-early
handover/too-late handover) in all
handover faults. If the ratio of a
handover fault type exceeds the
threshold, the MRO function is
triggered for the type.
Range: 50–100.
Default: 50.
The Threshold of Start MRO Sets the minimum occurrence

Parameter Optimization threshold of a handover fault
(too-early handover/too-late
4-4

handover) for starting MRO

parameter optimization.
Range: 1–255.
Default: 2.
If the Timer of eNodeB Statistics
MRO Error Information
parameter is set to 24, the
recommended setting of this
parameter is 48, meaning
optimization is started if 48
handover faults occur within 24
hours.
Enable MRO According to Determines whether to monitor the KPI of the base station cell
KPI and enable the MRO detection switch according to the threshold
setting.
By default, this parameter is set to Enable.
Call Dropping Rate Sets the call drop rate threshold for triggering MRO.
Threshold to Trigger MRO When the call drop rate of a cell is higher than this threshold, the
MRO function is triggered and the related handover parameters
are modified automatically.
Range: 0–100.
Default: 2.
RRC Re-Establishment Sets the threshold number of cell re-establishment times for
Threshold to Trigger MRO triggering MRO.
If the number of cell re-establishment times is higher than this
threshold, the MRO function is triggered and the related handover
parameters are automatically modified.
Range: 0–1024.
Default: 10.
Period of OAM Statistics Sets the period for monitoring cell KPI statistics.
KPI This parameter is valid to all cells managed by the OAM.
Range: 1–24.
Default: 1.
Threshold of Inter-Rat Sets the threshold for triggering parameter optimization for
Handover Parameter handovers with a different radio system.
Optimization (%) If the failure rate of a handover to a different radio system exceeds
this threshold, the MRO function is triggered and the related
handover parameters are optimized.
Range: 20–100.
Default: 20.
4-5

Threshold of ping-pang Sets the threshold percentage of ping-pang handovers in all

Handover Parameter handovers.
Optimization (%) Ping-pang handover optimization is triggered when the following
conditions are met:
l The percentage of ping-pang handovers in the total
handovers reaches the threshold.
l The number of ping-pang handover times reaches the
configured The Threshold of Start MRO Parameter
Optimization.
l No too-early-handover optimization or too-late- handover
optimization has been implemented.
Range: 10–100.
Default: 10.
Threshold of Last Serving Sets the threshold of latest signal When the UE’s reference
Cell Rsrp for SON CCO reference strength of the serving signal strengths in both the
(dBm) cell serving cell and neighbor
cell exceed their respective
Threshold of Neighbour Cell Sets the threshold of reference
thresholds, the fault is
Rsrp for SON CCO (dBm) signal strength of the neighbor
regarded as an MRO fault
cells
and the MRO function is
implemented. Otherwise,
the fault is a Coverage and
Capacity Optimization fault.
5. Set the required parameters, and click OK. The new MRO policy is displayed on the
FDD MRO Polciy tab, see Figure 4-4.
Figure 4-4 FDD MRO Policy Tab (with the New MRO Policy)
4-6

6. Click the new MRO policy, and then click on the toolbar. The Set dialog box is
7. Set the cell on which the MRO policy is to take effect, and then click OK. After the
MRO policy is successfully configured, Succeed is displayed in the Result column,
see Figure 4-6.
4-7

Figure 4-6 MRO Policy Configuration Success
4.2 Turning On the MRO Message Report Switch

This procedure describes how to turn on the MRO message report switch, and distribute
the configuration data to the specified eNodeB.
Steps
The FDD SON Control tab is displayed, see Figure 4-7.
4-8

4-8.
4-2.
Table 4-2 Description of Parameters in the FDD Switch Dialog Box
Template Name Specifies the switch template name, which is recommended

to use the format “FDD_function_switch mode”, for example,
FDD_MRO_Open.
4-9

Service Type Specifies the switch policy type. Set it to MRO.
4. Set the required parameters, and then click OK. The new MRO message report switch
is displayed on the FDD SON Control tab, see Figure 4-9.
Figure 4-9 FDD SON Control Tab (with the New MRO Message Report Switch)
6. Set the eNodeB to which the MRO message report switch is to be distributed, and
then click OK. After the MRO message report switch is successfully distributed to the
eNodeBs, Succeed is displayed in the Result column, see Figure 4-10.
Figure 4-10 Successfully Distributed MRO Switch
4-10

After the MRO policy and message report switch are distributed successfully, if an
eNodeB reports an MRO message, the MRO function is triggered.
4.3 Monitoring MRO Messages

This procedure describes how to monitor an MRO message and process it based on the
mode selected in the MRO policy.
l If the MRO policy is set to free mode, the system automatically processes the reported
l If the MRO policy is set to controlled mode, the MRO message is processed in steps
confirmed by users.
Steps
Mangement > Real-Time Monitoring > Optimization Monitoring in the left SON
showing all the traced messages, see Figure 4-11.
2. Click an MRO message. The Monitor Step Information sub-tab shows the
processing steps, and the Monitor Detail Information sub-tab shows the message
details.
3. (Optional) Right-click the MRO message, and perform the required operations.
4-3.
4-11

Table 4-3 Shortcut Menu Items of an MRO Message
Acknowledged-Cancel Acknowledges the cancellation of performing the steps and

closes the message.

Click a controlled MRO message whose parameters are being
distributed, and then click Alter Params. In the displayed dialog
box, modify the parameters to be distributed.
Batch Export Displayed when users right-click in the traced message area.
It is used to export all controlled messages in batches to a
specified Excel file in the local computer.
Batch Import Displayed if users right-click in the traced message area after
the parameters in the bulk exported Excel file are modified. This
menu item is used to import all controlled messages into the
NetNumen U31 to validate the parameters.
l If the MRO policy mode of the eNodeBs involved in the MRO message is set
to controlled mode, right-click the MRO message and then click a menu item to
l If the MRO policy mode of the eNodeBs involved in the MRO message is set to
free mode. the system directly implements the policy.
After the message is completely processed, 100% is displayed in the Progress
column.
4.4 Checking MRO Parameter Modification

This procedure describes how to verify that an MRO policy is correct by checking whether
the optimized parameters are correct.
Context
The MRO process starts from the minimum granularity, which is increased to a larger
granularity if the optimization is invalid. After optimization, the parameter values are
modified. The optimization granularities are as follows:
l The Offset Frequency field in the measurement optimization parameter

Inter-Frequency Measurement Configuration.
l The cell optimization parameter Offset of the Serving Cell.
4-12

l The neighbor relation optimization parameter Cell Individual Offset.
Prerequisite
Steps
1. Check the optimization of the Offset Frequency field in the measurement parameter
Inter-Frequency Measurement Configuration.
a. In the NE tree, click Modify Area$0 under the eNodeB 1169 node.
b. In the Managed Element tree, double-click Radio Parameter > LTE FDD >
E-UTRAN FDD Cell > Measurement Parameter. The Measurement Parameter
- List tab is displayed in the right pane, listing all cells under eNodeB 1169, see
Figure 4-12.
Figure 4-12 Measurement Parameter - List Tab
c. Double-click the record. The Measurement Parameter tab is displayed, showing

the details of the selected cell, see Figure 4-13.
4-13

Figure 4-13 Measurement Parameter Tab
d. Click the input box of the Inter-Frequency Measurement Configuration

parameter. The Inter-Frequency Measurement Configuration dialog box is
Figure 4-14 Inter-Frequency Measurement Configuration Dialog Box
e. Check whether the Offset Frequency column is modified.

2. Check the optimization of the cell parameter Offset of the Serving Cell.
4-14

b. In the Managed Element tree, double-click Radio Parameter > LTE FDD >
E-UTRAN FDD Cell. The E-UTRAN FDD Cell - List tab is displayed in the right
pane, listing all cells under eNodeB 1169, see Figure 4-15.
Figure 4-15 E-UTRAN FDD Cell - List Tab
c. Double-click the record. The E-UTRAN FDD Cell tab is displayed, showing the
details of the selected cell, see Figure 4-16.
4-15

Figure 4-16 E-UTRAN FDD Cell Tab
3. Check the optimization of the neighbor relation parameter Cell Individual Offset.
b. In the Managed Element tree, double-click Radio Parameter > LTE FDD
> Neighbor Relation Configuration > E-UTRAN Neighbor Relation. The
E-UTRAN Neighbor Relation - List tab is displayed in the right pane, listing all
cells under eNodeB 1169, see Figure 4-17.
4-16

Figure 4-17 E-UTRAN Neighbor Relation - List Tab
c. Double-click the record. The E-UTRAN Neighbor Relation tab is displayed,

showing the details of the selected cell, see Figure 4-18.
4-17

Figure 4-18 E-UTRAN Neighbor Relation Tab
4-18

Chapter 5
X2 Policy Management
Table of Contents
Setting an X2 Policy ...................................................................................................5-1
Turning On the X2 Message Report Switch ................................................................5-5
Monitoring X2 Messages ............................................................................................5-8
Checking X2 Connections ........................................................................................5-10
5.1 Setting an X2 Policy

This procedure describes how to set an X2 policy and apply the policy to specific cells (for
example, eNodeBs 147 and 161).
Steps
Policy Template.
3. In the expanded Policy Tree, double-click Managed Element > LTE FDD > FDD X2
Policy. The FDD X2 Policy tab is displayed in the right pane, see Figure 5-1.
5-1

Figure 5-1 FDD X2 Policy Tab
4. Click on the toolbar. The FDD X2 Policy dialog box is displayed, see Figure 5-2.
Figure 5-2 FDD X2 Policy Dialog Box
5-2

Chapter 5 X2 Policy Management
For a description of the parameters in the FDD X2 Policy dialog box, refer to Table
5-1.
Table 5-1 Parameters for Configuring a FDD X2 Policy
Template Name Specifies the X2 policy template name, which is recommended to

use the format “radio system_X2_operation mode”, for example,
FDD_X2_Free.
Service Type Fixed to X2.
Run Mode Specifies the processing mode of the X2 policy when the EMS
receives an X2 message.
l Free mode: The system directly implements the X2 policy upon
receiving the X2 message.
l Controlled mode: After the system receives the X2 message,
how to implement the X2 policy is manually controlled.
X2 Refer Point Policy Sets the reference points, which are used to determine whether each
step in the X2 policy is a breakpoint for user’s confirmation when the
X2 policy is in controlled mode.
X2 Self Setup Enable Enables or disables automatic X2 connection setup upon receiving
an X2 message.
X2 Self Delete Enable Enables or disables automatic X2 connection deletion when

corresponding neighbor cells are deleted.
X2 Self Delete Specifies the threshold for deleting automatic X2 connections.

Threshold When the number of X2 connections is smaller than the threshold,
automatic X2 connection deletion will never be triggered. Even if a
neighbor cell is deleted, the related X2 connections are not deleted.
Range: 1–32.
Default: 20.
S1 HO Success Specifies the threshold of S1 handover success times.

Threshold This parameter is used for triggering X2 self-setup. After the statistical
period expires, if the number of successful S1 handovers between
two eNodeBs is greater than the threshold, the system starts an X2
connection self-setup process.
Range: 0–65535.
Default: 48.
5-3

X2 HO Success Specifies the threshold of X2 handover success times.

Threshold This parameter is used for triggering X2 self-deletion. After the
statistical period expires, if the number of successful X2 handovers
between two eNodeBs is smaller than the threshold, the system starts
an X2 connection self-deletion process.
Range: 0–65535.
Default: 48.
X2 Self-Setup/Self- Specifies the timer length of X2 self-setup/deletion.

Delete Statistic Timer This parameter is used for X2 self-setup/deletion. The system counts
Length (Hour) the number of successful S1/X2 handovers in the specified period,
which serves as a condition for determining X2 self-setup/deletion.
Range: 1–255.
Default: 24.
5. Set the required parameters, and click OK. The new X2 policy is displayed on the FDD
X2 Policy tab, see Figure 5-4.
Figure 5-4 FDD X2 Policy Tab (with the New X2 Policy)
6. Click the new X2 policy, and click on the toolbar. The Set dialog box is displayed.
7. Set the radio system of the eNodeB on which the X2 policy is to take effect, and click
OK. After the X2 policy is successfully configured, Succeed is displayed in the Result
column, see Figure 5-5.
5-4

Figure 5-5 X2 Policy Configuration Success
5.2 Turning On the X2 Message Report Switch

This procedure describes how to turn on the X2 message report switch, and distribute the
configuration data to the specified eNodeB.
Steps
The FDD SON Control tab is displayed, see Figure 5-6.
5-5

5-7.
5-2.
Table 5-2 Parameters for Setting X2 Message Report Switch
5-6

Template Name Specifies the switch template name, which is recommended

to use the format “FDD_function_switch mode”, for example,
FDD_X2_Open.
Service Type Specifies the switch policy type. Set it to X2.
4. Set the required parameters, and then click OK. The new X2 message report switch
is displayed on the FDD SON Control tab, see Figure 5-8.
Figure 5-8 FDD SON Control Tab (with the New X2 Message Report Switch)
6. Set the eNodeB to which the X2 switch is to be distributed, and then click OK. After
the X2 switch is successfully distributed to the eNodeBs, Succeed is displayed in the
Result column, see Figure 5-9.
Figure 5-9 Successfully Distributed X2 Switch
After the X2 policy and message report switch are distributed successfully, if an
eNodeB reports an X2 message, the corresponding X2 connection is established.
5-7

5.3 Monitoring X2 Messages

This procedure describes how to monitor an X2 message and process it based on the
mode selected in the X2 policy.
l If the X2 policy is set to free mode, the system automatically processes the reported
l If the X2 policy is set to controlled mode, the X2 message is processed in steps con-
firmed by users.
Steps
showing the traced messages, see Figure 5-10.
Note:
You can click an X2 message and view the details in the lower part. The Monitor Step
2. Double-click an X2 message. The Show Details dialog box is displayed, see Figure
5-11.
5-8

The X2 message in Figure 5-11 indicates that an X2 connection to eNodeB 161 needs
to be added to eNodeB 147.
Use the same method to check whether an X2 connection to eNodeB 147 needs to
be added to eNodeB 161.
3. Right-click the ANR message, and perform the required operations.
5-3.
Table 5-3 Shortcut Menu Items of an X2 Message
Trigger Timing Checks the time for triggering X2 connection.
Acknowledged-Cancel Acknowledges the cancellation of performing the steps

and closes the message.
5-9


Click a controlled X2 message whose parameters are
being distributed, and then click Alter Params. In the
displayed dialog box, modify the parameters to be
distributed.
Batch Export Displayed when users right-click in the traced message

area. It is used to export all controlled messages in
batches to a specified Excel file in the local computer.
Batch Import Displayed if users right-click in the traced message

area after the parameters in the bulk exported Excel
file are modified. This menu item is used to import all
controlled messages into the NetNumen U31 to validate
the parameters.
l If the X2 policy mode of the eNodeBs involved in the X2 message is set to

controlled mode, right-click the PCI message and then click a menu item to
l If the X2 policy mode of the eNodeBs involved in the X2 message is set to free
mode, the system directly implements the policy.
After the X2 message is completely processed, 100% is displayed in the Progress
column.
5.4 Checking X2 Connections

This procedure describes how to verify that an X2 policy is correctly configured by checking
the X2 connections.
Prerequisite
Steps
1. Click Modify Area$0 under the eNodeB 147 node. Then, in the Managed Element,
double-click Transmission Network > Signaling and Business > SCTP. The
SCTP-List tab is displayed in the right pane, showing all Stream Control Transmission
Protocol (SCTP) messages of eNodeB 147, see Figure 5-12.
5-10

Figure 5-12 SCTP-List Tab (eNodeB 147)
In Figure 5-12, the remote address of eNodeB 147 is that of eNodeB 161, indicating
that eNodeB is configured with an X2 connection to eNodeB 161.
2. Use the same method to check whether eNodeB 161 is configured with an X2
connection to eNodeB 147, see Figure 5-13.
5-11

Figure 5-13 SCTP-List List Tab (eNodeB 161)
In Figure 5-13, the remote address of eNodeB 161 is that of eNodeB 147, indicating
that eNodeB 161 is configured with an X2 connection to eNodeB 147.
5-12

Chapter 6
PnP Policy Management
Table of Contents
Setting a PnP Policy...................................................................................................6-1
Monitoring PnP Messages..........................................................................................6-6
Checking Automatic eNodeB Commissioning .............................................................6-9
6.1 Setting a PnP Policy

This procedure describes how to set a PnP policy and apply the policy to a specific cell
(for example, eNodeB 147)..
Context
The PnP-based commissioning refers to an automatic version downloading and activation
process.
1. The system downloads the specified version to an NE in accordance with the schedule
in the PnP policy.
2. After the version downloading is completed, the system automatically activates the
version and synchronizes the prepared configuration data.
3. After successful activation, the system restarts the NE and automatically establishes
a link to the NE.
Prerequisite
The required software version must exist on the corresponding OMM server and the
configuration data must be available before automatic version downloading.
Steps
1. In the NE tree, check the eNodeB 147 status, see Figure 6-1.
Figure 6-1 eNodeB 147 Status
6-1

If a icon is displayed before eNodeB 147, infer that the base station is not
commissioned and the connection to the NetNumen U31 is improper.
2. Select Configuration > MO SDR SON Configuration Application > MO SDR SON
Configuration Application from the menu bar. The MO SDR SON Configuration
Application window is displayed.
Management > SON Policy Template in the SON Management Tree. Then, under
the Policy Tree tab, double-click Managed Element > PNP Policy. The PNP Policy
tab is displayed in the right pane, see Figure 6-2.
Figure 6-2 PNP Policy Tab
4. Click on the toolbar. The PnP Policy dialog box is displayed, see Figure 6-3.
6-2

Chapter 6 PnP Policy Management
Figure 6-3 PnP Policy Dialog Box
5. Set the required parameters.

For a description of the parameters in the PNP Policy dialog box, refer to Table 6-1.
Table 6-1 Parameters for Setting a PNP Policy
Template Name Specifies the PnP policy template name, which is recommended
to use the format “radio system_PnP_operation mode”, for
example, FDD_PNP_Free.
Service Type Fixed to PnP.
SON Run Mode Specifies the processing mode of the PnP policy when the EMS
receives a PnP message.
l Free Mode: The system directly implements the PnP policy
upon receiving the PnP message.
l Controlled Mode: After the system receives the PnP
message, how to implement the PnP policy is manually
controlled.
6-3

Refer Point Policy Sets the reference points, which are used to determine
whether each step in the PnP policy is a breakpoint for user’s
confirmation when the PnP is in controlled mode.
Version Package Type Fixed to package.
Plat Version List Specifies the platform version packages.

Click the input box. In the displayed Select Version dialog box,
select the platform version packages that need to be obtained
automatically, see Figure 6-5.
Product Version List Specifies the product version packages.

Click the input box. In the displayed Select Version dialog box,
select the product version packages that need to be obtained
automatically, see Figure 6-6.
6-4

Figure 6-5 Select Version Dialog Box (for Platform Version)
Figure 6-6 Select Version Dialog Box (for Product Version)
6. Click OK. The new PnP policy is displayed on the PNP Policy tab, see Figure 6-7.
6-5

Figure 6-7 New PnP Policy
7. Click the new PnP policy and then click . The Set dialog box is displayed.
8. Set the eNodeB on which the PnP policy is to take effect, and then click OK.
After the PnP policy is successfully configured, Succeed is displayed in the Result
column, see Figure 6-8.
Figure 6-8 PnP Policy Configuration Success
6.2 Monitoring PnP Messages

This procedure describes how to monitor PnP messages. Additional operations are
required if the controlled mode is specified in the PnP policy.
l If the free mode is specified in the PnP policy, the NetNumen U31 system will
automatically process the received PnP messages and establish a communication
link with the corresponding OMM. In this mode, the system obtains the latest version
and configuration file, activates the version, and synchronizes configuration data to
complete the automatic commissioning.
l If the controlled mode is specified in the PnP policy, manual intervention is required
to complete the steps required by the PnP messages.
Steps
1. In the SON Management Tree, double-click SON Monitor Management > Real-Time
Monitoring > Deploy Monitoring. The Deploy Monitoring tab is displayed in the
right pane, showing all the traced messages, see Figure 6-9.
6-6

Figure 6-9 Deploy Monitoring Tab
Note:
You can click a PnP message and view the details in the lower part. The Monitor Step
2. Double-click a PnP message. The Show Details dialog box is displayed, showing the
message details, see Figure 6-10.
6-7

The PnP message in Figure 6-10 shows the detailed process of downloading and
activating versions.
3. Based on the PnP policy mode configured for the eNodeBs involved in the PnP
message, take appropriate actions:
PnP Policy Mode Action
Controlled mode Right-click the PnP message and then click a menu item to
Free mode The system directly implements the policy.
After the PnP message is completely processed, 100% is displayed in the Progress
column.
6-8

6.3 Checking Automatic eNodeB Commissioning

This procedure describes how to verify that the PnP policy is correctly configured by
checking the eNodeB 147 commissioning.
Steps
1. In the NE tree of the Configuration Management window, check the eNodeB 147
status, see Figure 6-11.
Figure 6-11 eNodeB 147 Status
If is displayed before eNodeB 147, infer that the eNodeB is successfully

commissioned.
2. In the SON Management Tree of the MO SDR SON Configuration Application
window, double-click SON eNodeB Commission Report Management > SON
eNodeB Commission Report Query. The SON eNodeB Commission Report
Query tab is displayed in the right pane, see Figure 6-12.
Figure 6-12 SON eNodeB Commission Report Query Tab
3. (Optional) On the SON eNodeB Commission Report Query tab, right-click the record
to be checked, and select View. The View dialog box is displayed, where you can
check the eNodeB commissioning report, see Figure 6-13.
6-9

Figure 6-13 View Dialog Box
4. On SON eNodeB Commission Report Query tab, right-click the commissioning

report to be exported, and select Download Report. The Export dialog box is
displayed, where you can set a path to export the report to the local computer.
The exported file is saved in a compressed package.
6-10

Chapter 7
Policy Query
The NetNumen U31 system supports query of all configured policies, including SON
policies and switch policies.
Table of Contents
Querying SON Polices ...............................................................................................7-1
Querying Switch Polices.............................................................................................7-3
7.1 Querying SON Polices

This procedure describes how to set conditions for querying SON policies, view the
details, and check whether the policies are successfully distributed to and validated on
the eNodeBs.
Steps
Management > SON Function Policy Query in the left SON Management Tree. The
SON Function Policy Query tab is displayed in the right pane, see Figure 7-1.
Figure 7-1 SON Function Policy Query Tab
7-1

2. Click on the toolbar. The Query Function Policy dialog box is displayed, see
Figure 7-2.
Figure 7-2 Query Function Policy Dialog Box
For a description of the parameters in the Query Switch Policy dialog box, refer to
Table 7-1.
Table 7-1 Parameters for Querying SON Policies
Policy Grade Specifies the grade of the SON policy, which can be:
l Managed Element Grade
l Radio Grade
l Cell Grade
The nodes in the Selected policy area vary depending on the
selected Policy Grade.
Radio Type Specifies the radio type. The NEs in the Selected location
area vary depending on the selected eNodeB type.
Selected location Lists the objects to be queried, which can be NEs or cells.
Selected policy Lists the function policies.
7-2

Chapter 7 Policy Query
3. Set the query conditions, and then click OK. The query result is displayed, see Figure
7-3.
Figure 7-3 Results of SON Policy Query
4. (Optional) Perform any of the following operations:

l Double-click a function policy.
l Right-click a function policy, and click View.
l Select a function policy, and click on the toolbar.
The View dialog box is displayed, in which the policy details are displayed on the
Operation Detail tab, see Figure 7-4.
Figure 7-4 View Dialog Box – Operation Detail Tab
7.2 Querying Switch Polices

This procedure describes how to set conditions to query switch policies, view the details,
and check whether the policies are successfully distributed to and validated on the
eNodeBs.
7-3

Steps
Management > SON Switch Policy Query in the left SON Management Tree. The
SON Switch Policy Query tab is displayed in the right pane, see Figure 7-5.
Figure 7-5 SON Switch Policy Query Tab
2. Click on the toolbar. The Query Switch Policy dialog box is displayed, see Figure
7-6.
7-4

Chapter 7 Policy Query
Figure 7-6 Query Switch Policy Dialog Box
3. Set the query conditions.
For a description of the parameters in the Query Switch Policy dialog box, refer to
Table 7-2.
Table 7-2 Parameters for Querying Switch Policies
Switch Type Supports FDD SON Control and TDD SON Control.
Selected SON Function Lists the SON functions, of which the switch policies can be
queried.
Selected location Lists the objects to be queried, which can be NEs or cells.
4. Click OK. The query result is displayed, see Figure 7-7.
7-5

Figure 7-7 Results of Switch Policy Query
5. (Optional) Perform any of the following operations:

l Double-click a switch policy.
l Right-click a switch policy, and click View.
l Select a switch policy, and click on the toolbar.
The View dialog box is displayed, in which the policy details are displayed on the
Operation Detail tab, see Figure 7-8
Figure 7-8 View Dialog Box – Operation Detail Tab
7-6

Chapter 8
SON Log Query
SON Logs can record events that impact functions and key parameters. Logs may be
displayed as prompt information or error messages based on their levels.
Because the monitoring message quantity of some functions is limited, not all parameter
modifications are reported, but these events are recorded as SON logs. For example, after
the ANR automatically optimizes a parameter based on statistics data, if no monitoring
report, the parameter modification is recorded as a SON log.
SON logs report the following functions: ANR, X2, and PCI.
Steps
1. In the MO SDR SON Configuration Application window, double-click SON
Monitor Management > SON Log Management > SON Log Query in the left SON
Management Tree. The SON Log Query tab is displayed in the right pane to show
SON logs, see Figure 8-1.
Figure 8-1 SON Log Query Tab
2. Double-click a SON Log. The View dialog box is displayed, see Figure 8-2.
8-1

Figure 8-2 View Dialog Box
3. On the SON Log Query tab, find the storage address of log files in the Detail column.
You can get log files in the EMS based on the address.
Log files are stored in a compressed format, for example,

SON-6205-1-1-1-1-20131010212853.csv.gz is the name of a compressed file, where
“6205” is the NE ID. Figure 8-3 shows log contents.
Figure 8-3 SON Log Files
The header meanings are described as follows:

l Rack-Shelf-Slot-CpuId: rack number, shelf number, slot number, and CPU ID.
l ProductID: Radio Access Technology (RAT). The RATs and the corresponding
numbers are describes as follows:
à PLAT: 1
à UMTS: 2
à GSM: 3
à TD: 4
à CDMA: 5
8-2

Chapter 8 SON Log Query
à LTE FDD: 6
à LTE TDD: 7
l LogClass: log class.
The value of SON logs is 2, but a log with LogClass = 2 may be not a SON log in
actual environments.
l AppLevel: log level. The meanings and the corresponding numbers are described
as follows:
à Information: 1
à Note: 2
à Warning: 3
à Minor: 4
à Major: 5
à Critical: 6
l AppInfo: transaction ID.
l dwEventNo: event number.
l LogData: log data. SrvType indicates the corresponding SON function type of the
reported log. The functions and the numbers are described as follows:
à ANR: 46
à PCI: 47
à X2: 48
à MRO: 49
l Year-Mon-Dat: year, month, and day.
l ucPad: reserved.
8-3

8-4

Appendix A
ANR Failure Information
Description
Not all the failure codes are described in this appendix. If you find new ones, contact the
equipment vendor.
Table A-1 ANR Failure Information
Error Type Key Words
1. ANR statistics result didn't l ANR Fail in Statistic state

meet the threshold l ANR Fail in Delay state
2. Processing Timed Out l Receiving the command response times out

l Thread timeout
3. Processing Error Send mml error
4. Object Has Existed l XXX already exists. Check whether XXX is unique
l XXX can’t be duplicated
5. Fail to apply mutex right l A special operation is being executed. Wait for several
minutes and try again
l XXX does not have mutex right. Mutex right is being used
by another client
6. Fails to Synchronize Data to Data baseline is inconsistent with NE

NEs
7. SON Data Is Abnormal Generate ANR data failed
8. Added neighbor cells fails due l there are at most XXX records
to meet the system limitation l ANR Fail in WaitNbrDel state
9. Policy setting fails l ID does not exist

l ‘Service Type’can’t be the same with ‘SON Switch’
l MOC is not exist
1. ANR statistics result didn't meet the threshold

l Description
à The ANR statistics threshold (Handover Success Threshold & Neighbor Cell
Report Threshold) is not reached when the timer (based on UE measurement)
expires, see Figure A-1.
A-1

Figure A-1 ANR Fail in Statistic state
à The ANR statistics threshold (Handover Success Threshold & Neighbor Cell
Report Threshold) is not reached when the timer (based on X2 interface) expires,
see Figure A-2.
Figure A-2 ANR Fail in Delay state
l Causes
A-2

Appendix A ANR Failure Information Description
The found neighbor cells do not meet the requirements (Handover Success Threshold
& Neighbor Cell Report Threshold).
l Handling Suggestion
These cases are normal. These cases occur if the threshold is not reached. Check
whether the threshold is properly configured. If yes, no need to handle. If not, optimize
the threshold.
2. Processing Timed Out

l Description
à Timed out while receiving an ICM response, see Figure A-3.
Figure A-3 Receiving the command response times out
à ICM processing timed out, see Figure A-4
A-3

Figure A-4 Thread timeout
l Causes
In general, if there are a large number of SON messages or other client is processing
ICM data, the SON requests sent to the ICM are put in a queue. When the request
stays in the queue for a long time, ICM processing timeout occurs.
No need to handle, because the NE would send an ANR request again.
3. Processing Error
l Description
ICM fails to send mml commands to OMMB, see Figure A-5.
A-4

Figure A-5 Send mml error
l Causes
The corresponding process starting of ICM server is not completed.
Functions of the ICM are as follows:
à Provides the latest configuration data to the SON.
à Provides the SON incremental synchronization data to the channel of an NE.

Verify ICM server was launched normally ， if no ， please contact the system
administrator.
4. Object Has Existed

l Description
à The neighbor cell has existed, see Figure A-6.
A-5

Figure A-6 XXX already exists. Check whether XXX is unique
à The neighbor cell has existed due to MCC, MNC, eNodeBID, and CellID collision,
see Figure A-7.
Figure A-7 XXX can’t be duplicated
l Causes
à External cell already existed.
à The same IDs (E-UTRAN Neighbor Relation ID) are selected due to inconsistent
ICM data and OMMB data.
Wait for one day and check whether the same ANR request from the NE is reported.
A-6

à If the fault persists after multiple ANR requests are sent, the same ID may be
selected because the ICM data is inconsistent with the OMMB data. Try to upload
the NE data to the EMS.
à If the same ANR request is not reported from the NE, no need to handle.
5. Fail to apply mutex right

l Description
à The SON cannot apply for the mutually exclusive access, see Figure A-8.
Figure A-8 A special operation is being executed. Wait for several minutes
and try again
à Other client is modifying data through the EMS, and the mutually exclusive access
is occupied, see Figure A-9.
A-7

Figure A-9 XXX does not have mutex right, Mutex right is being used by
another client
l Causes
Other client apply the mutex right. Because an NE can be operated by one client at
the same time, the SON fails to operate the NE.
à If other client apply the mutex right, no need to handle, and the NE sends an ANR
request again.
à If the BS permission fails to be released after a long period of time, contact the
system administrator.
6. Fails to Synchronize Data to NEs

l Description
Data synchronization fails due to inconsistent NE data and OMMB data, see Figure
A-10.
A-8

Figure A-10 Data baseline is inconsistent with NE
l Causes
The NE data and OMMB data are inconsistent, so data modified by the SON fails to
be synchronized to NEs.
Perform global synchronization or upload NE data to the EMS (caution: global

synchronization may cause the eNodeB to restart).
7. SON Data Is Abnormal

l Description
The SON fails to generate data, see Figure A-11.
A-9

Figure A-11 Generate ANR data failed
l Causes
Data processing is abnormal, information (PCIs and frequencies) reported by the NE
is not correct, or there have duplicated eNodeBs stored in the EMS.
Check failure codes after the SON is triggered again. If this fault persists, handle it as
follows:
1. Check whether there are two NEs with the same eNodeB ID on the EMS. If yes,
go to step 2. If no, go to step 3.
2. Delete either of the two NEs with the same eNodeB ID or modify either of
their eNodeB IDs, perform incremental synchronization to the NE (caution: this
operation causes the cell out of service), and wait the next SON procedure.
3. Check whether the reported PCI and frequency of the remote-end NE are
consistent with the configuration data on the EMS. If yes, go to step 4. If no,
check the NE and configuration data on the EMS. If the information reported by
the NE is not correct, restart the corresponding eNodeB. If the configuration data
on the EMS is not correct, modify it and perform incremental synchronization to
the NE.
4. Send the logs to the system administrator for further analysis.
8. Added neighbor cells fails due to meet the system limitation

l Description
The number of neighbor cells exceeds the limit, see Figure A-12.
A-10

Figure A-12 The number of neighbor cells exceeds the limit
l Causes
EMS message processing is delayed.
A-11

1. Check whether the ANR self-delete function is enabled. If the function is disabled,
enable it. If the function is enabled, go to step 2.
2. Check whether the number of configured neighbor cells reaches the maximum
value. If it does not, go to step 3. If it does, check all neighbor cell relations
to see whether the minimum number of handovers is lower than the threshold
for deletion. If all the number of handovers are higher than the threshold for
deletion, check the configured parameters of “The Total HO Counter Threshold
for Neighbour Cell Deleted”, and increase the threshold properly. Otherwise, go
to step 3.
3. Report the problem to the equipment vendor for further handling.
9. Policy setting fails

l Description
Policy setting fails and the system cannot find the MOC(Managed Object Class), see
Figure A-13.
Figure A-13 MOC is not exist
l Causes
à The ICM model is not uploaded or fails to be uploaded.
à The ICM data and OMMB data are inconsistent.
à If the ICM has not uploaded the model yet, upload the model corresponding to
the OMMB where the NE is located.
à If the ICM already uploads the model, delete the model corresponding to the
OMMB where the NE is located, and then re-upload the model.
A-12

Appendix B
PCI Failure Information
Description
Not all the failure codes are described in this appendix. If you find new ones, contact the
equipment vendor.
Table B-1 PCI Failure Information
Error Type Key Words
1. Sync Request Time Out Sync Request Time Out
2. PCI is null null
3. PCI List Is null PCIList= return PCI list is null
4. Needn't modify PCI value Needn't modify PCI value
5. Other PCI transaction has processed, Other PCI transaction has processed, this transaction
this transaction need not process need not process
1. Sync Request Time Out

l Description
The SON Server does not return the results in the specified time, see Figure B-1.
B-1

Figure B-1 Sync Request Time Out
l Causes
The SON Server is too busy to process new PCI requests because the requests occur
frequently.
Wait for one day. When the NE triggers a PCI optimization request again, check
whether the processing still expires. If the fault persists, contact the equipment
manufacturer.
2. PCI is null
l Description
The PCI optimization result returned by the distributed/centralized SON Server is null,
see Figure B-2 and Figure B-3.
Figure B-2 Repeated PCI Allocation in Distributed Mode
B-2

Appendix B PCI Failure Information Description
Figure B-3 Repeated PCI Allocation in Centralized Mode
l Causes
The PCIs on the SON server are not sufficient.
AddavailablePCIsinthecellPCIlistandwaitthenextPCI confusion/collision message
reported from the NE, or manually enter PCIs in control mode.
3. PCI List Is null

l Description
The PCI List planning result returned by the SON Server is null, see Figure B-4.
Figure B-4 PCI List Is Null
l Causes
à The engineering parameters on the SON server are not configured correctly.
à The configuration data of the SON Server is inconsistent with that of the OMMB.
1. Check the SON server engineering parameters and determine whether the
records corresponding to the cell exist. If no, configure the engineering
parameters of the cell and then import them to the SON server. If yes, go to Step
2.
2. Export the engineering parameters and the configuration parameters
corresponding to this NE from the SON server, and then contact the equipment
manufacturer.
B-3

4. Needn't modify PCI value

l Description
Needn't modify PCI value, see Figure B-5.
Figure B-5 Needn't modify PCI value
l Causes
à This NE’s request has been processed before and no more processing is
required.
à The user modified a collision and the SON detected that no more modification is
required.
No need to handle.
5. Other PCI transaction has processed, this transaction need not process
l Description
Other PCI transaction has processed, this transaction need not process, see Figure
B-6.
B-4

Appendix B PCI Failure Information Description
Figure B-6 Other PCI transaction has processed, this transaction need not process
l Causes
The PCI transaction sent by this NE is included into the transactions sent by other
cells, so the NMS indicates that no more processing is required.
No need to handle.
B-5

B-6

Figures
Figure 1-1 MO SDR SON Configuration Application Window .................................... 1-5
Figure 1-2 Optimization Monitoring Tab..................................................................... 1-6
Figure 2-1 FDD ANR Policy Tab................................................................................ 2-2
Figure 2-2 FDD ANR Policy Dialog Box .................................................................... 2-2
Figure 2-3 SON Refer Point Attribute Table Dialog Box............................................. 2-7
Figure 2-4 FDD ANR Policy Tab (with the New ANR Policy)...................................... 2-8
Figure 2-5 Set Dialog Box ......................................................................................... 2-8
Figure 2-6 ANR Policy Configuration Success .......................................................... 2-9
Figure 2-7 FDD SON Control Tab ........................................................................... 2-10
Figure 2-8 FDD SON Control Dialog Box ................................................................ 2-10
Figure 2-9 Added ANR Message Report Switches .................................................. 2-11
Figure 2-10 Set Policy Dialog Box........................................................................... 2-12
Figure 2-11 Successfully Sending the ANR Switch Configuration............................ 2-12
Figure 2-12 Optimization Monitoring Tab................................................................. 2-13
Figure 2-13 Show Details Dialog Box...................................................................... 2-14
Figure 2-14 E-UTRAN FDD Neighbor Cell-List Tab ................................................. 2-16
Figure 2-15 E-UTRAN FDD Neighbor Cell Tab........................................................ 2-16
Figure 3-1 FDD PCI Policy Tab ................................................................................. 3-2
Figure 3-2 FDD PCI Policy Dialog Box...................................................................... 3-2
Figure 3-4 FDD PCI Policy Tab (with the New PCI Policy)......................................... 3-4
Figure 3-6 PCI Policy Configuration Success ............................................................ 3-5
Figure 3-7 FDD SON Control Tab ............................................................................. 3-6
Figure 3-8 FDD SON Control Dialog Box .................................................................. 3-7
Figure 3-9 FDD SON Control Tab (with New PCI Message Report Switch) ............... 3-7
Figure 3-10 Successfully Distributed PCI Switch ....................................................... 3-8
Figure 3-11 Optimization Monitoring Tab ................................................................... 3-9
Figure 3-12 Show Details Dialog Box...................................................................... 3-10
Figure 3-13 E-UTRAN FDD Cell-List Tab ................................................................ 3-12
Figure 3-14 E-UTRAN FDD Cell Tab....................................................................... 3-13
Figure 4-1 FDD MRO Policy Tab............................................................................... 4-2

Figure 4-2 FDD MRO Policy Dialog Box.................................................................... 4-3

Figure 4-4 FDD MRO Policy Tab (with the New MRO Policy) .................................... 4-6
Figure 4-6 MRO Policy Configuration Success.......................................................... 4-8
Figure 4-9 FDD SON Control Tab (with the New MRO Message Report
Switch).................................................................................................. 4-10
Figure 4-10 Successfully Distributed MRO Switch................................................... 4-10
Figure 4-11 Optimization Monitoring Tab ................................................................. 4-11
Figure 4-12 Measurement Parameter - List Tab ...................................................... 4-13
Figure 4-13 Measurement Parameter Tab............................................................... 4-14
Figure 4-14 Inter-Frequency Measurement Configuration Dialog Box ..................... 4-14
Figure 4-15 E-UTRAN FDD Cell - List Tab .............................................................. 4-15
Figure 4-16 E-UTRAN FDD Cell Tab....................................................................... 4-16
Figure 4-17 E-UTRAN Neighbor Relation - List Tab ................................................ 4-17
Figure 4-18 E-UTRAN Neighbor Relation Tab ......................................................... 4-18
Figure 5-1 FDD X2 Policy Tab................................................................................... 5-2
Figure 5-2 FDD X2 Policy Dialog Box ....................................................................... 5-2
Figure 5-4 FDD X2 Policy Tab (with the New X2 Policy)............................................ 5-4
Figure 5-5 X2 Policy Configuration Success ............................................................. 5-5
Figure 5-8 FDD SON Control Tab (with the New X2 Message Report Switch) ........... 5-7
Figure 5-9 Successfully Distributed X2 Switch .......................................................... 5-7
Figure 5-10 Optimization Monitoring Tab................................................................... 5-8
Figure 5-11 Show Details Dialog Box ........................................................................ 5-9
Figure 5-12 SCTP-List Tab (eNodeB 147)............................................................... 5-11
Figure 5-13 SCTP-List List Tab (eNodeB 161) ........................................................ 5-12
Figure 6-1 eNodeB 147 Status.................................................................................. 6-1
Figure 6-2 PNP Policy Tab ........................................................................................ 6-2
Figure 6-3 PnP Policy Dialog Box ............................................................................. 6-3
Figure 6-5 Select Version Dialog Box (for Platform Version)...................................... 6-5
II

Figures
Figure 6-6 Select Version Dialog Box (for Product Version)....................................... 6-5
Figure 6-7 New PnP Policy ....................................................................................... 6-6
Figure 6-8 PnP Policy Configuration Success ........................................................... 6-6
Figure 6-9 Deploy Monitoring Tab ............................................................................. 6-7
Figure 6-10 Show Details Dialog Box........................................................................ 6-8
Figure 6-11 eNodeB 147 Status ................................................................................ 6-9
Figure 6-12 SON eNodeB Commission Report Query Tab ........................................ 6-9
Figure 6-13 View Dialog Box................................................................................... 6-10
Figure 7-1 SON Function Policy Query Tab............................................................... 7-1
Figure 7-2 Query Function Policy Dialog Box ............................................................ 7-2
Figure 7-3 Results of SON Policy Query ................................................................... 7-3
Figure 7-4 View Dialog Box – Operation Detail Tab................................................... 7-3
Figure 7-5 SON Switch Policy Query Tab.................................................................. 7-4
Figure 7-6 Query Switch Policy Dialog Box ............................................................... 7-5
Figure 7-7 Results of Switch Policy Query ............................................................... 7-6
Figure 7-8 View Dialog Box – Operation Detail Tab................................................... 7-6
Figure 8-1 SON Log Query Tab................................................................................. 8-1
Figure 8-2 View Dialog Box....................................................................................... 8-2
Figure 8-3 SON Log Files ......................................................................................... 8-2
Figure A-1 ANR Fail in Statistic state ........................................................................A-2
Figure A-2 ANR Fail in Delay state ...........................................................................A-2
Figure A-3 Receiving the command response times out............................................A-3
Figure A-4 Thread timeout ........................................................................................A-4
Figure A-5 Send mml error........................................................................................A-5
Figure A-6 XXX already exists. Check whether XXX is unique..................................A-6
Figure A-7 XXX can’t be duplicated...........................................................................A-6
Figure A-8 A special operation is being executed. Wait for several minutes and try
again ......................................................................................................A-7
Figure A-9 XXX does not have mutex right, Mutex right is being used by another
client .......................................................................................................A-8
Figure A-10 Data baseline is inconsistent with NE ....................................................A-9
Figure A-11 Generate ANR data failed ....................................................................A-10
Figure A-12 The number of neighbor cells exceeds the limit ................................... A-11
Figure A-13 MOC is not exist ..................................................................................A-12
Figure B-1 Sync Request Time Out...........................................................................B-2
Figure B-2 Repeated PCI Allocation in Distributed Mode ..........................................B-2
III

Figure B-3 Repeated PCI Allocation in Centralized Mode .........................................B-3

Figure B-4 PCI List Is Null.........................................................................................B-3
Figure B-5 Needn't modify PCI value ........................................................................B-4
Figure B-6 Other PCI transaction has processed, this transaction need not
process...................................................................................................B-5
IV

Tables
Table 2-1 Parameters for Setting an FDD ANR Policy ............................................... 2-3
Table 2-2 Parameters for Configuring FDD Switch .................................................. 2-10
Table 2-3 Shortcut Menu Items of an ANR Message ............................................... 2-15
Table 3-1 Parameters for Setting a FDD PCI Policy .................................................. 3-3
Table 3-2 Parameters for Setting a PCI Message Report Switch ............................... 3-7
Table 3-3 Shortcut Menu Items of a PCI Message................................................... 3-10
Table 4-1 Parameters for Setting an FDD MRO Policy .............................................. 4-3
Table 4-2 Description of Parameters in the FDD Switch Dialog Box .......................... 4-9
Table 4-3 Shortcut Menu Items of an MRO Message .............................................. 4-12
Table 5-1 Parameters for Configuring a FDD X2 Policy ............................................. 5-3
Table 5-2 Parameters for Setting X2 Message Report Switch ................................... 5-6
Table 5-3 Shortcut Menu Items of an X2 Message .................................................... 5-9
Table 6-1 Parameters for Setting a PNP Policy ......................................................... 6-3
Table 7-1 Parameters for Querying SON Policies...................................................... 7-2
Table 7-2 Parameters for Querying Switch Policies ................................................... 7-5
Table A-1 ANR Failure Information............................................................................A-1
Table B-1 PCI Failure Information .............................................................................B-1

Tables
VI

Glossary
ANR
- Automatic Neighbor Relation
BS
- Base Station
DRX
- Discontinuous Reception
FDD
- Frequency Division Duplex
KPI
- Key Performance Index
LTE
- Long Term Evolution
MO
- Measured Object
MRO
- Mobility Robustness Optimization
OAM
- Operating and Maintenance
OMC
- Operation & Maintenance Center
OMM
- Operation and Maintenance Management
PCI
- Physical Cell Identity
PnP
- Plug and Play
SCTP
- Stream Control Transmission Protocol
SDR
- Software Defined Radio
SON
- Self-Organizing Network
TDD
- Time Division Duplex
VII

UE
- User Equipment
UTRAN
- UMTS Terrestrial Radio Access Network
eNodeB
- Evolved NodeB
VIII

SJ-20130524154927-017-NetNumen U31 R18 (V12.12.43) Operation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20130524154927-017-NetNumen U31 R18 (V12.12.43) Operation Guide

Uploaded by

Copyright:

Available Formats

NetNumen™ U31 R18

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.5 2014-06-30 Modified "Appendix B PCI Failure Information Description".

R1.4 2014-04-15 Modified "Appendix A ANR Failure Information Description".

R1.3 2014-04-03 The following contents have been modified:

R1.2 2013-12-25 Modified "Appendix A ANR Failure Information Description".

R1.1 2013-10-17 The following contents have been added:

l Chapter 8 Son Log Query

R1.0 2013-06-30 First edition.

Serial Number: SJ-20130524154927-017

Publishing Date: 2014-06-30 (R1.5)

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Chapter 2 ANR Policy Management.......................................................... 2-1

Chapter 3 PCI Policy Management ........................................................... 3-1

Chapter 4 MRO Policy Management ......................................................... 4-1

Chapter 5 X2 Policy Management ............................................................. 5-1

Chapter 6 PnP Policy Management .......................................................... 6-1

Chapter 7 Policy Query .............................................................................. 7-1

Chapter 8 SON Log Query ......................................................................... 8-1

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

l Base station commissioning engineers

What Is in This Manual

1, Overview Provides an overview of SON management in the NetNumen

5, X2 Policy Management Describes the operations related to X2 policy management.

8, SON Log Query Describes how to query SON logs.

Appendix A, ANR Failure Describes ANR failure information.

Appendix B, PCI Failure Information Describes PCI failure information.

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Note: provides additional information about a certain topic.

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

1.1 Basic Concepts

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Policy Configuration Granularity

All switch policies are configured at radio access system level.

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Reference Point and Breakpoint

1.2 SON Configuration Window

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Figure 1-1 MO SDR SON Configuration Application Window

The MO SDR SON Configuration Application window has two panes:

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Figure 1-2 Optimization Monitoring Tab

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

2.1 Setting an ANR Policy

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Figure 2-1 FDD ANR Policy Tab

Figure 2-2 FDD ANR Policy Dialog Box

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Table 2-1 Parameters for Setting an FDD ANR Policy

Template ID Uniquely identifies a policy template.

Service Type Fixed to ANR.

ANR Measure Object Specifies the maximum number of UE selection attempts.

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Handover Success Threshold of handover successes. It is used with the parameter

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Figure 2-3 SON Refer Point Attribute Table Dialog Box

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential

Figure 2-5 Set Dialog Box

SJ-20130524154927-017|2014-06-30 (R1.5) ZTE Proprietary and Confidential