Umts Cco Feature Description - RRM Based (v100r015c00 - 01) (PDF) - en

SONMaster
V100R015C00
UMTS CCO Feature Description RRM Based

Issue
01
Date
2015-02-14
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2015-02-14)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
SONMaster
UMTS CCO Feature Description - RRM Based
About This Document
About This Document

Purpose
This document describes the UMTS Coverage and Capacity Optimization (CCO) RRM Based
feature, including implementation principles, related features, network impact, and engineering
guides.
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
SONMaster
V100R015C00
Intended Audience
This document is intended for:
l
System engineers
Network management engineers
Change History
01 (2015-02-14)
This is the first commercial release of V100R015C00.
Compared with Draft A (2015-01-15) for V100R015C00, this issue does not include any
changes.
Draft A (2015-01-15)
This is a draft for V100R015C00.
Issue 01 (2015-02-14)

ii
SONMaster
About This Document
Compared with Draft A (2014-10-15) for V100R014C01, this issue does not include any
changes.
Organization
1 Overview
2 Technical Description
3 Related Features
4 Network Impact
5 Version Mapping
6 Engineering Guidelines
7 Feature Specifications
8 References
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
avoided, may result in minor or moderate injury.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Issue 01 (2015-02-14)

iii
SONMaster
Symbol
About This Document
Description
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
Issue 01 (2015-02-14)

iv
SONMaster
About This Document
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Issue 01 (2015-02-14)
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.

SONMaster
Contents
Contents
About This Document.....................................................................................................................ii
1 Overview.........................................................................................................................................1
2 Technical Description...................................................................................................................6
2.1 Related Concepts............................................................................................................................................................7
2.2 Principles........................................................................................................................................................................7
2.3 Implementation Process..................................................................................................................................................9
2.3.1 UMTS DL Capacity Optimization RRM Based..........................................................................................................9
2.3.2 UMTS DL Coverage Optimization RRM Based.......................................................................................................16
2.4 Introduction to the Main Window................................................................................................................................20
3 Related Features...........................................................................................................................28
4 Network Impact...........................................................................................................................31
5 Version Mapping.........................................................................................................................32
6 Engineering Guidelines.............................................................................................................33
6.1 UMTS DL Capacity Optimization RRM Based...........................................................................................................34
6.1.1 Activation Advice......................................................................................................................................................34
6.1.2 Information Collection Before the Deployment........................................................................................................34
6.1.3 Feature Deployment..................................................................................................................................................37
6.1.4 Monitoring.................................................................................................................................................................59
6.1.5 Parameter Optimization.............................................................................................................................................60
6.2 UMTS DL Coverage Optimization RRM Based..........................................................................................................64
6.2.1 Activation Advice......................................................................................................................................................64
6.2.2 Information Collection Before the Deployment........................................................................................................64
6.2.3 Feature Deployment..................................................................................................................................................67
6.2.4 Monitoring.................................................................................................................................................................83
6.2.5 Parameter Optimization.............................................................................................................................................84
7 Feature Specifications.................................................................................................................87
8 References.....................................................................................................................................89
Issue 01 (2015-02-14)

vi
SONMaster
1 Overview
Overview
This section contains the following contents:

l
Feature ID and Name
Background
Definition
Data Source Analysis
Benefits
Application Scenarios
Feature ID and Name

Table 1-1 Feature ID and name
Feature ID
Feature Name
SNFD-140219
CCO - UMTS DL Capacity Optimization RRM Based
SNFD-140217
CCO - UMTS DL Coverage Optimization RRM

Based
Background
About half of the total operating expense (OPEX) of a typical network is network planning and
optimization costs in which the costs of drive tests (DTs), performance analysis, and problem
location take majority. Performance analysis and problem location involve analyzing and
handling antenna problems. DTs are mainly used to solve network coverage problems and
require high costs.
Traditional optimization depends on manual experience, and the optimization efficiency is low.
Generally, when adjusting the azimuth or downtilt angle of an antenna through traditional
optimization, engineers identify the problem by performing a DT and then provide adjustment
advice based on manual experience. After a tower operator climbs up to the antenna tower and
adjust the azimuth or downtilt angle, another DT is performed to check whether the problem
persists. The preceding operations may be performed repeatedly to solve one problem.
Issue 01 (2015-02-14)

SONMaster
1 Overview
UMTS CCO RRM Based provides two subfeatures: UMTS DL Capacity Optimization RRM
Based and UMTS DL Coverage Optimization RRM Based. With the subfeatures, a complete,
efficient, and cost-effective automatic network coverage and capacity optimization solution is
provided.
Definition
CCO: optimizes network coverage and capacity with least manual intervention, thereby reducing
network OM costs.
l
UMTS DL Capacity Optimization RRM Based: This feature helps you analyze problems
in multiple dimensions such as neighboring cell faults, incorrect configurations of
accessibility parameters, unbalanced traffic sharing, and traffic bursts. This feature also
provides multiple optimization methods, thereby avoiding site visits. The optimization
process is automated and with low risks, and implements the self closed loop SON solution.
UMTS DL Coverage Optimization RRM Based: This feature automatically detects

problematic cells, analyzes causes, and provides optimization advice. This helps solve
downlink weak coverage and downlink intra-network interference problems.
Data Source Analysis

Optimization performed by the SONMaster mainly involves the following types of data:
configuration data (CM data), performance data (PM data), measurement report data (MR data),
and call history record data (CHR data).
Figure 1-1 shows the sources of SONMaster analysis data on the network. Table 1-2 describes
the data sources.
Issue 01 (2015-02-14)

SONMaster
1 Overview
Figure 1-1 Sources of analysis data
Table 1-2 Data sources

Data Source
Description
CM
The data is obtained from the RNC. It provides configuration

information about cells and neighbor relationships for optimization
analysis.
PM
The data is obtained from the RNC. The SONMaster collects statistics
about and analyzes KPIs, checks whether the KPIs for each cell in
the optimization area meet related requirements, and then identifies
problematic cells.
MR
The data is obtained from the SAU of the RNC. It provides RSCP
and Ec/No records for handover parameter optimization and power
adjustment optimization.
CHR
The data is obtained from the SAU of the RNC. It provides

information about the transport propagation delay (TP)
corresponding to each RRC setup, whether the RRC setup fails, and
the failure causes.
NOTE
The data is used only for UMTS DL Coverage Optimization RRM Based.
Issue 01 (2015-02-14)

SONMaster
1 Overview
Data Source
Description
Engineering
parameters
Engineering parameters are manually imported or exported on the

SONMaster. They provide latitude and longitude and coverage type
(indoor, high-speed, or tunnel) information for optimization analysis
and geographic display.
Benefits
UMTS CCO RRM Based brings the following benefits:
l
Improved network coverage and capacity optimization efficiency

This feature automatically collects and processes network data and adjusts parameters. This
reduces the dependencies on manual invention, shortens the waiting time, implements
network optimization anytime and anywhere, and improves network operation and
maintenance (OM) efficiency.
Reduced network coverage and capacity optimization costs

This feature is automated. This reduces manual invention and network OM costs.
Improved network performance

UMTS DL Capacity Optimization RRM Based:
This feature detects capacity problems such as high load on the network, and solves
configuration problems and rectifies faults for high-load cells on the network. This helps
achieve load balancing among cells, improve the access success rate, and reduce the
congestion rate, thereby achieving maximum radio resource usage. This also helps
reduce network problems caused by load imbalance and improve network performance.
UMTS DL Coverage Optimization RRM Based:
This feature improves cell coverage performance from the signal level and quality
aspects, and provides benefits for KPIs. For example, reduce the call drop rate and
improve the access success rate and throughput of a cell. In addition, this feature reduces
dependency on manual experience, implements the self-closed downlink coverage
optimization solution, and avoids the high risks and costs brought by traditional RF
optimization.
Application Scenarios
Table 1-3 describes application scenarios of UMTS CCO RRM Based.
Table 1-3 Application scenarios
Issue 01 (2015-02-14)
Scenario
Description
SONMaster Function
Routine
network
adjustment
Routine coverage and load

optimization is required on the
network.
l Solves capacity problems on the

network.
The SONMaster automatically
detects high-load cell capacity
problems and optimizes network
capacity. This helps solve

SONMaster
Scenario
Description
Periodical
coverage and
capacity
optimization
on the entire
network
As network coverage and load

change due to network scale and UE
distribution changes, you need to
check and optimize coverage and
capacity on the entire network
periodically.
Coverage and
capacity
optimization
in certain
areas
In VIP areas or cell clusters with

poor KPIs, you need to optimize
coverage and capacity centrally.
This improves network quality and
user experience.
Multi-band
and multicarrier
network
evolution
Network load changes continuously

as network deployment plans for
different RATs differ.
1 Overview
SONMaster Function
capacity problems on the
network, improve network
optimization efficiency, and
reduce OM costs.
l Solves high load and traffic burst
problems.
The SONMaster solves resource
insufficiency problems caused by
overloaded cells without capacity
expansion. This helps implement
load balancing among cells and
improve resource usage.
l Solves coverage problems on the
network.
The SONMaster automatically
detects, analyzes, and takes
optimization measures for
downlink weak coverage and
interference problems. This helps
improve network optimization
efficiency and real-time
efficiency, and reduce OM costs.
NOTE
The scenario restrictions of this feature are as follows:
Issue 01 (2015-02-14)
Project scenarios: This feature is developed for solving coverage and capacity problems on existing
networks, and does not apply to new deployment, reparenting, or expansion scenarios.
Wireless scenarios: This feature does not apply to highway, tunnel, and super-distance coverage
scenarios. This feature applies to indoor, urban, and suburban coverage (30 km or less) scenarios.
Networking scenarios: In this version, this feature does not apply to inter-RAT coverage, multivendor networking, special cell, or MOCN/MORAN scenarios. This feature applies to single-carrier
coverage, multi-carrier coverage, and multi-band coverage scenarios.
Special cell scenarios: This feature does not apply to multiple RRUs in one cell and repeaters.

SONMaster
Technical Description
About This Chapter

2.1 Related Concepts
2.2 Principles
2.3 Implementation Process
2.4 Introduction to the Main Window
Issue 01 (2015-02-14)

SONMaster
2.1 Related Concepts

Table 2-1 describes related concepts of UMTS CCO RRM Based.
Table 2-1 Related concepts
Concept
Description
Stable highload problem
A high-load problem indicates that the load of a cell exceeds a specified highload threshold. If the cell frequently encounters high-load problems, a stable
high-load problem (compared to the traffic burst problem) occurs. Based on
the distribution of high-load time ranges, stable high-load problems are
classified into periodic stable high-load problems (also referred to as tidal
traffic) and non-periodic stable high-load problems.
Traffic burst
problem
(occasional)
The load of an idle cell may increase sharply to a high level because of traffic
bursts. For example, the load of the cell covering a stadium may increase
sharply during important sporting events. The traffic bursts are unpredictable.
Such high-load problems are referred to as traffic burst problems.
Downlink
weak
coverage
The downlink signal level and Ec/No may be lower than the RSCP and Ec/
No thresholds, respectively, because of weak coverage. Such problems are
referred to as downlink weak coverage problems.
Downlink
interference
The downlink signal level may be higher than the RSCP threshold and the
Ec/No may be lower than the Ec/No threshold because of interference. Such
problems are referred to as downlink weak interference problems.
Problematic
cells
Cells with load or downlink coverage problems.
Cells to be
adjusted
Some neighboring cells in the neighboring cell list of problematic cells. Such
cells are involved in adjustment to optimize problematic cells.
Cells to be
evaluated
Some neighboring cells of cells to be adjusted. Such cells are not involved in
adjustment but are affected by execution of optimization advice. Therefore,
such cells need to be evaluated to avoid that their performance deteriorate
because of execution of optimization advice.
Cells that
require
power
adjustment
association
Intra-band co-coverage but inter-frequency cells of the cells involved in

power adjustment. The power of these correlated cells must also be adjusted
together with cells to be evaluated to ensure consistent coverage and normal
blind handovers.
2.2 Principles
Figure 2-1 shows the basic principle of UMTS CCO RRM Based. Table 2-2 describes each
step in Figure 2-1.
Issue 01 (2015-02-14)

SONMaster
Figure 2-1 Basic principle
Table 2-2 Principle description

Number
Description
Set the optimization task.

Set parameters related to UMTS CCO tasks on the SONMaster.
Collect data.
Collect CM/PM/CHR/MR data.
Analyze problematic cells.

l UMTS DL Coverage Optimization RRM Based:
Optimizing weak coverage cells: The SONMaster identifies weak
coverage cells and analyzes root causes.
Optimizing cells with interference problems: The SONMaster identifies
cells with interference problems and analyzes root causes.
l UMTS DL Capacity Optimization RRM Based:
The SONMaster checks whether high-load cells are non-periodic and
periodic, monitors network load changes in real time, and identifies traffic
burst high-load cells.
Generate optimization advice.

Displays neighboring cell optimization advice on the SONMaster for users to
view.
Issue 01 (2015-02-14)

SONMaster
Number
Description
Deliver optimization advice.
Delivers optimization advice to NEs to implement the optimization advice.
2.3 Implementation Process

2.3.1 UMTS DL Capacity Optimization RRM Based
UMTS DL Capacity Optimization RRM Based: automatically detects high-load cells and
traffic burst cells and then constructs the problematic area. It also automatically provides
adjustment advice to solve load problems. UMTS DL Capacity Optimization RRM Based
involves the following types of load balancing:
l
Long-Period Load Balancing
Traffic Burst Load Balancing
Long-Period Load Balancing

Long-period load balancing: detects stable high-load problems on the network, optimizes the
load status on the network, and evaluates the optimization effect. Figure 2-2 shows the process
of long-period load balancing. For details, see Table 2-3.
Issue 01 (2015-02-14)

SONMaster
Figure 2-2 Process of long-period load balancing
Issue 01 (2015-02-14)

10
SONMaster
Table 2-3 Description of long-period load balancing

No.
Procedure
Description
Create and
start a CCO
task.
After you start a CCO task, the SONMaster collects raw PM and
trace data of all cells involved in the task, synchronizes
configuration data, and imports engineering parameters based on the
parameter settings on the client to implement long- or short-term
load balancing.
Collect data
The SONMaster collects PM, CM, and trace data within the
monitoring period based on the monitoring granularity of longperiod load balancing.
Identify
stable highload cells
The SONMaster collects statistics about the power load and power
congestion rate of cells in all time ranges within the monitoring
period, and identifies non-periodic and periodic stable high-load
cells.
Man-machine interaction scenario 1: In manual mode, there is a
breakpoint after stable high-load cells are identified. At the
breakpoint, the SONMaster displays problematic cells, their
neighboring cells, parameters that can be adjusted by the
SONMaster for the cells such as handover parameters and pilot
power, and adjustment ranges of the parameters. The SONMaster
also allows you to set adjustable cells and parameters based on
network conditions.
Issue 01 (2015-02-14)
Check
accessibility
parameters
The SONMaster checks RAB and RRC accessibility parameters for

problematic cells in the optimization area, identifies cells with
improper configurations, and corrects the configurations.

11
SONMaster
No.
Procedure
Description
Generate
optimization
advice
UMTS CCO adopts different optimization modes based on the types

of stable high-load cells.
l Periodic stable high-load cells: The SONMaster generates and
delivers optimization advice only in periodic high-load time
ranges. When the periodic high-load time ranges end, the
parameter configuration is restored to that before the
optimization.
l Non-periodic stable high-load cells: The optimization advice
takes effect within the whole day.
The SONMaster checks neighboring cell faults and excludes pseudo
congestion caused by faulty neighboring cells. It also analyzes
traffic balancing status and uses appropriate methods to implement
load balancing among problematic cells and their neighboring cells.
Such methods include using load balancing features, capacity
improvement features, handover parameter mapping optimization,
and pilot power mapping optimization.
breakpoint after optimization advice is generated. At the breakpoint,
the SONMaster displays all optimization advice and allows you to
modify the optimization advice and select certain pieces of
optimization advice to deliver based on network conditions. The
displayed optimization advice includes that related to accessibility
parameter correction, alarms indicating neighboring cell faults,
handover parameter optimization, and pilot power optimization.
Control
delivery of
optimization
advice
The SONMaster solves the conflict between the optimization advice

provided by the long- and traffic burst load balancing modules.
Evaluate the
optimization
gains and
roll back
parameters
After delivering optimization advice, the SONMaster evaluates the

optimization gains based on KPI changes. If network capacity in the
optimization area deteriorates, the SONMaster rolls back
optimization parameters. That is, the SONMaster delivers the
parameters configured before the optimization to NEs through the
U2000. The SONMaster also generates the gain analysis report for
the problematic cells that are not involved in parameter rollback.
If the optimization advice provided by the long- and traffic burst

load balancing modules applies to the same cell, the optimization
advice provided by the traffic burst load balancing module is
delivered to the cell first. When the traffic burst load balancing
module verifies that no traffic bursts occur in the cell, the
optimization advice provided by the long-period load balancing
module is delivered to the cell if the optimization advice does not
expire.

breakpoint after rollback evaluation. At the breakpoint, the
SONMaster allows you to modify the rollback advice and select
certain pieces of rollback advice to deliver based on your experience.
Issue 01 (2015-02-14)

12
SONMaster
No.
Procedure
Description
Check
whether the
maximum
number of
optimization
iterations
(N) reaches
If the actual number of optimization iterations is smaller than the

specified maximum number of optimization iterations after a round
of long-period load balancing, the SONMaster goes to Collect
data and starts optimization of the next round.
Traffic Burst Load Balancing

Traffic burst load balancing: solves high-load problems caused by traffic bursts in special cells
within a short period of time. Figure 2-3 shows the process of traffic burst load balancing. For
details, see Table 2-4.
Issue 01 (2015-02-14)

13
SONMaster
Figure 2-3 Process of traffic burst load balancing
Issue 01 (2015-02-14)

14
SONMaster
Table 2-4 Description of traffic burst load balancing
Issue 01 (2015-02-14)
No.
Procedure
Description
Create and
start a CCO
task.
After you start a CCO task, the SONMaster collects raw PM, CM,
MR, and CHR data of all cells involved in the task, synchronizes
configuration data, and imports engineering parameters based on the
parameter settings on the client to implement long- or short-term
load balancing.
Collect data
The SONMaster supports 15-, 30-, 45-, and 60-minute traffic burst
monitoring based on network measurement periods, and collects
required PM, CM, MR, and CHR data.
Identify
traffic burst
cells
Based on PM data, the SONMaster detects traffic burst cells based

on the period of traffic burst monitoring.
Generate
optimization
advice
Based on networking of problematic cells, the SONMaster uses

appropriate methods to implement load balancing among the
problematic cells and their neighboring cells. Such methods include
using load balancing features, capacity improvement features,
handover parameter mapping optimization, and pilot power
mapping optimization.
Control
delivery of
optimization
advice
The SONMaster solves the conflict between the optimization advice

provided by the long- and traffic burst load balancing modules.
Evaluate the
optimization
gains and
roll back
parameters

optimization gains based on KPI changes. If network capacity in the
optimization area deteriorates, the SONMaster rolls back
Check
whether the
maximum
number of
optimization
iterations
(N) reaches
If the actual number of optimization iterations does not exceed the

of traffic burst load balancing, the SONMaster goes to Collect
data and starts optimization of the next round.

15
SONMaster
No.
Procedure
Description
Monitor and
handle cells
where traffic
burst
problems
persist
1. If the specified maximum number of optimization iterations of

long-period load balancing reaches, and there are problematic cells
where traffic burst problems persist, the SONMaster continues
monitoring the traffic status of those problematic cells through
traffic burst load balancing. When no traffic bursts occur in the cells,
the parameter configuration is restored to that before the
optimization and the CCO task is complete. 2. If the specified
maximum number of optimization iterations of long-period load
balancing reaches, and there are no problematic cells where traffic
burst problems persist, the CCO task is complete.
2.3.2 UMTS DL Coverage Optimization RRM Based

Downlink weak coverage problems and downlink intra-network interference problems usually
occur on wireless networks. This easily results in call drops and handover failures, thereby
affecting network performance and terminal user experience.
UMTS DL Coverage Optimization RRM Based: this feature collects statistics about and
analyzes measurement reports sent by terminals on the network, analyzes root causes of weak
coverage and interference problems from multiple dimensions, and provides parameter
optimization, feature optimization, missing neighboring cell addition, and power optimization
advice. The dimensions include parameter exceptions, handover exceptions, missing
neighboring cells, device faults, insufficient intensive coverage, coverage overlap, and pilot
pollution. This helps solve downlink weak coverage and downlink intra-network interference
problems and improve network performance and user experience.
Figure 2-4 shows the process of this feature. For details, see Table 2-5.
Issue 01 (2015-02-14)

16
SONMaster
Figure 2-4 Optimization process
Issue 01 (2015-02-14)

17
SONMaster
Table 2-5 Description

No.
Procedure
Description
Create and
start a CCO
task.
Create a UMTS CCO task, set key task parameters, and import basic
task data such as engineering parameters and antenna files for
UMTS DL Coverage Optimization RRM Based.
Collect data
for
monitoring
and gain
evaluation
Based on the monitoring period of the optimization task, the

SONMaster collects data from data sources before each round of
optimization. The data includes PM, CM, MR, and CHR data within
one week by default. The data is used to identify problematic cells,
generate optimization advice, and evaluate network performance
before optimization.
Identify
downlink
coverage
problematic
cells and
evaluate the
effect of last
round of
optimization
l Identify downlink coverage problematic cells.

The SONMaster collects statistics about the percentage of MRs
with downlink weak coverage and that of MRs with downlink
interference at busy hours within the monitoring period to
identify downlink coverage problematic cells and downlink
interference problematic cells.
l Evaluate the effect of last round of optimization.
From the second round of optimization, the SONMaster
evaluates the effect of last round of optimization. The
SONMaster evaluates the problematic cells and problematic cell
groups that have valid optimization advice in the last round of
optimization based on KPIs and coverage counters. After
evaluating the effect, the SONMaster does not automatically roll
back optimization advice. Instead, it adjusts the optimization
advice based on the evaluation results in the next round of
optimization.
breakpoint in this step. At the breakpoint, the SONMaster displays
problematic cells, their neighboring cells, parameters that can be
adjusted by the SONMaster for the cells such as handover
parameters and pilot power, and adjustment ranges of the
parameters. The SONMaster also allows you to set adjustable cells
and parameters based on network conditions.
Analyze root
causes of
coverage
problems
The SONMaster analyzes root causes for downlink coverage

problematic cells.
l For downlink weak coverage problematic cells, the SONMaster
identifies the percentages of problems such as downlink
exceptions, missing neighboring cells, isolated island areas
caused by coverage overlap, handover exceptions, intensive
weak coverage, local-end weak coverage, and remote-end weak
coverage.
l For downlink interference problematic cells, the SONMaster
identifies the percentages of problems such as missing
neighboring cells, azimuth exceptions, indoor distribution
interference, coverage overlap, and pilot pollution.
Issue 01 (2015-02-14)

18
SONMaster
No.
Procedure
Description
Generate
optimization
advice
The SONMaster generates optimization advice based on the causes

of problematic cells. The optimization advice is categorized as:
l Optimization advice that displays problem causes but cannot be
automatically executed, including optimization advice related to
device exception check, neighboring cell optimization, azimuth
optimization, indoor distribution interference optimization, and
mechanical downtilt angle optimization.
l Optimization advice that can be automatically executed,
including optimization advice related to coverage parameter
check, reselection parameter optimization, handover
optimization, feature optimization, power optimization, and
electrical downtilt angle optimization.
breakpoint after optimization advice is generated. At the breakpoint,
the SONMaster displays all optimization advice and allows you to
change values in the optimization advice based on network
conditions.
Deliver
optimization
advice
The SONMaster delivers optimization advice based on the setting

of Advice execution.
Collect data
for rollback
evaluation
Based on the parameters set for rollback evaluation monitoring, the

SONMaster collects data from data sources after each round of
optimization. The data refers to the PM data generated within at least
three busy hours after the optimization advice is delivered by
default. The data is used to quickly evaluate network performance
after optimization.
Evaluate
optimization
effect and
roll back
optimization
parameters

optimization gains based on KPI changes. If KPIs in the
optimization area deteriorate, the SONMaster rolls back
breakpoint after the evaluation. At the breakpoint, the SONMaster
allows you to change values in the rollback advice based on network
conditions.
Issue 01 (2015-02-14)
Check
whether the
maximum
number of
optimization
iterations
(N) reaches
If the onsite number of optimization iterations does not exceed the

of optimization, the SONMaster goes to Collect data for
monitoring and gain evaluation and starts optimization of the next
round.

19
SONMaster
2.4 Introduction to the Main Window

Overview of the CCO Main Window
Figure 2-5 shows the main window of CCO. For details about each step in the main window,
see Table 2-6.
Figure 2-5 Overview of the CCO main window
Table 2-6 Details about each step

Step No.
Reference
(Optional) Connecting to the OSS
Importing Engineering Parameters
(Optional) Creating a Cell Zone Template
(Optional) Adding Frozen Cells
(Optional) Importing the Antenna Data Files
N/A
Setting Parameters for UMTS CCO - RRM Based (Huawei)
Issue 01 (2015-02-14)

20
SONMaster
Step No.
Reference
l Creating and Starting a UMTS CCO Task
l Executing a UMTS CCO Task - RRM Based (Coverage)(Huawei)
l Executing a UMTS CCO Task - RRM Based (Capacity)(Huawei)
l (Optional) Checking the Information About Exceptions During UMTS CCO
Optimization
l (Optional) Evaluating the Optimaization Effect of UMTS CCO Optimization
Window for UMTS CCO Task Management

Figure 2-6 shows the window for managing UMTS CCO tasks. Table 2-7 describes the elements
in the window.
Figure 2-6 Window for UMTS CCO task management
Table 2-7 Description of the window for task management

Area
No.
Area Name
Description
Task searching
Allows you to search for a task by Service type, Cell ID, or Cell
name.
Task
management
Provides the functions of refreshing, creating, deleting,

modifying, starting, and stopping a task and checking the running
logs of the tasks.
NOTE
l You cannot delete a running task.
l Modifications to a running task take effect in the next optimization
period.
Issue 01 (2015-02-14)

21
SONMaster
Area
No.
Area Name
Description
Task attributes
Displays the status and attributes of a specific optimization task.

l An optimization task is marked with different icons according
to the task status:
: indicates that the optimization task is not started or

is complete.
: indicates that the optimization task is being executed

properly.
: indicates that the optimization task is stopping.
: indicates that the optimization task experiences

exceptions.
: indicates that the optimization task is interrupted and

you can manually adjust parameters or deliver
optimization advice for it.
l The attributes of an optimization task are as follows:

Service type: type of the involved optimization feature
Vendor: vendor of optimization objects
Start mode: method of starting the optimization task
Stop mode: method of stopping the optimization task
Advice execution: execution mode of optimization advice
Task info: execution information of the optimization task
Window for Optimization Parameters

Figure 2-7 shows the window for optimization parameters in the optimization parameter
template. Table 2-8 describes the elements in the window.
Issue 01 (2015-02-14)

22
SONMaster
Figure 2-7 Window for optimization parameters
Table 2-8 Description of the window for optimization parameters

Area
No.
Area Name
Description
Node for
setting
optimization
parameters
Provides an entry to optimization parameter settings.
List of
optimization
parameter
templates
Lists the names of all optimization parameter templates,

including existing ones and the current template.
Toolbar for the

optimization
parameter
template
Provides the functions of adding, deleting, refreshing, and saving

an optimization parameter template.
Editing area
for an
optimization
parameter
template
Allows you to edit an optimization parameter template.
Wizards for Optimization Tasks - RRM Based (Huawei)

The wizards for optimization tasks are divided into the following types based on the task
progress:
l
Issue 01 (2015-02-14)
Figure 2-8 shows the problematic cell identification wizard. Table 2-9 describes the
components in the wizard.
23
SONMaster
Figure 2-9 shows the optimization advice management wizard. Table 2-10 describes the
elements in the wizard.
Figure 2-10 shows the optimization effect evaluation wizard. Table 2-11 describes the
elements in the wizard.
Figure 2-8 Problematic cell identification wizard
Table 2-9 Description of the problematic cell identification wizard

Area
No.
Area Name
Description
Area for
querying task
status
Consists of the drop-down list of historical optimization periods,

the progress axis, and the navigation path to the GIS window for
an optimization task.
Provides the functions of selecting a historical optimization
period, displaying the current stage, and viewing the GIS map
for an optimization task.
Toolbar
Provides the functions of refreshing, filtering, and identifying

problematic cells, and adding and deleting data records.
Problematic
cell list
Lists all problematic cells identified within the current

optimization period.
Figure 2-9 Optimization advice management wizard
Issue 01 (2015-02-14)

24
SONMaster
Table 2-10 Description of the optimization advice management wizard

Area
No.
Area Name
Description
Toolbar for
optimization
advice
Displays the report time of the optimization advice within

historical optimization periods, and provides the functions of
refreshing, filtering, exporting, saving, executing, and rolling back
optimization advice, and starting optimization of the next round.
NOTE
Saving optimization advice: For inappropriate optimization advice, you
can double-click a parameter value, enter a new value, and then click
to save the new value.
Optimization
advice list
Indicates the reported optimization advice within a selected

Figure 2-10 Optimization effect evaluation wizard
Table 2-11 Description of the optimization effect evaluation wizard

Area
No.
Area Name
Description
Toolbar for
optimization advice

historical optimization periods, and provides the functions
of refreshing, filtering, exporting, and rolling back
optimization advice, and starting optimization of the next
round.
Optimization advice
list
Indicates the reported optimization advice within a selected

Displays the optimization advice whose effect has been
evaluated. Based on the evaluation results, Execution
Phase in Optimization Advice is displayed as Deliver or
Rollback.
Window for Traffic Burst Optimization Advice - RRM Based (Huawei)

Figure 2-11 shows the window for traffic burst optimization advice. Table 2-12 describes the
components in the window.
Issue 01 (2015-02-14)

25
SONMaster
Figure 2-11 Window for traffic burst optimization advice
Table 2-12 Description of the window for traffic burst optimization advice
Area
No.
Area Name
Description
Time axis for

optimization periods

a historical optimization period on a time axis.
Toolbar for
optimization advice

historical optimization periods, and provides the functions
of refreshing, filtering, and exporting optimization advice.
Optimization advice
list
Indicates the reported optimization advice within a

selected optimization period.
Window for Statistics About Optimization Exceptions

Figure 2-12 shows the window for statistics about optimization exceptions. Table 2-13
describes the elements in the window.
Figure 2-12 Window for statistics about optimization exceptions
Table 2-13 Description of the window for statistics about optimization exceptions
Issue 01 (2015-02-14)
Area
No.
Area Name
Description
Statistics by
exception
severity
Unconfirmed exceptions with different severities during the

current optimization period are displayed in a pie chart. The
severities include Major and Minor.

26
SONMaster
Issue 01 (2015-02-14)
Area
No.
Area Name
Description
Statistics by
exception type
You can view the statistics about unconfirmed exceptions during

the current optimization period in a bar chart based on the
exception types, including license, engineering parameter,
configuration data, network KPI, and service running exceptions.
Toolbar for
statistics about
optimization
exceptions
Provides the functions of refreshing, querying, confirming, and

exporting data about optimization exceptions.
List of
statistics about
optimization
exceptions
The exception list displays exceptions recorded during the

current and previous optimization periods. You can confirm the
unconfirmed exceptions.

27
SONMaster
3 Related Features
Related Features
UMTS DL Capacity Optimization RRM Based

l
Prerequisite Features:
For the prerequisite features of UMTS DL Capacity Optimization RRM Based, see
Table 3-1.
Table 3-1 Related features
Related Feature
Description
Some optimization advice provided by

this feature depends on the following
features:
If you have not purchased the preceding

features, UMTS DL Capacity Optimization
RRM Based still functions properly and
provides other optimization methods.
l WRFD-010683 Downlink 64
QAM
l WRFD-030010 CQI Adjustment
Based on Dynamic BLER Target
l WRFD-010610 HSDPA
Introduction Package
l WRFD-010685 Downlink
Enhanced L2
l WRFD-02040004 Traffic
Steering and Load Sharing
During RAB Setup
l WRFD-020103 Inter Frequency
Load Balance
Issue 01 (2015-02-14)

28
SONMaster
3 Related Features
Related Feature
Description
This feature can be used with the

following CCO features:
The features cannot be used simultaneously in

the same optimization area, but can be used in
sequence. The recommended sequence is as
follows:
l SNFD-140217 CCO - UMTS DL

Coverage Optimization RRM
Based
Coverage Optimization RF Based
1. Use UMTS DL Coverage Optimization

RRM Based.
RF Based.
3. Use UMTS DL Capacity Optimization
RRM Based.
It is recommended that this feature be

used with the following features:
l SNFD-140205 Automatic
Neighbor Relation - UMTS IntraFrequency
l SNFD-140222 Scrambling Code
Self-Optimization - UMTS
This feature may adjust the cell pilot power

and may lead to the change of the basic
network architecture. In automatic
optimization scenarios, you need to ensure that
other automatic parameter optimization
processes that are based on the basic network
architecture can be performed concurrently.
l SNFD-140215 Mobility
Robustness Optimization UMTS Inter-Frequency
Mutually Exclusive Features:

None
Affected Features:
None
UMTS DL Coverage Optimization RRM Based

l
Prerequisite Features:
For the prerequisite features of UMTS DL Coverage Optimization RRM Based, see
Table 3-2.
Issue 01 (2015-02-14)

29
SONMaster
3 Related Features
Table 3-2 Related features

Related Feature
Description
Some optimization advice provided by

this feature depends on the following
features:
If you have not purchased the preceding

features, UMTS DL Coverage Optimization
RRM Based still functions properly and
provides other optimization methods.
l WRFD-020400 DRD
Introduction Package
l WRFD-020401 Inter-RAT
Redirection Based on Distance
l WRFD-02040005 InterFrequency Redirection Based on
Distance
This feature can be used with the
following CCO features:
Coverage Optimization RF Based
Capacity Optimization RRM
Based
The features cannot be used simultaneously in

the same optimization area, but can be used in
sequence. The recommended sequence is as
follows:
RRM Based.
RF Based.
3. Use UMTS DL Capacity Optimization
RRM Based.
It is recommended that this feature be

used with the following features:
l SNFD-140205 Automatic
Neighbor Relation - UMTS IntraFrequency
This feature may adjust the cell coverage

range. Therefore, you are advised to use this
feature with the preceding features.
l SNFD-140222 Scrambling Code

Self-Optimization - UMTS
l SNFD-140215 Mobility
Robustness Optimization UMTS Inter-Frequency
Mutually Exclusive Features:

None
Affected Features:
None
Issue 01 (2015-02-14)

30
SONMaster
4 Network Impact
Network Impact
UMTS DL Capacity Optimization RRM Based

l
System Capacity:
Positive impact: UMTS DL Capacity Optimization RRM Based identifies high-load
cells and traffic burst cells on the network and reduces the number of high-load cells
and the load of traffic burst cells. This helps implement load balancing among cells,
achieve better radio resource usage, improve the access success rate, and reduce the
congestion rate, thereby bringing gains to system capacity.
Negative impact: none
Network Performance:
Positive impact: none
Negative impact: Network coverage does not deteriorate or deteriorates within a
tolerable range.
UMTS DL Coverage Optimization RRM Based

l
System Capacity:
Positive impact: This feature automatically identifies downlink weak coverage and
downlink interference problems on Huawei networks and executes optimization advice.
This helps improve cell coverage performance from the signal level and quality aspects
and improve the cell throughput and throughput rate.
Negative impact: none
Network Performance:
Positive impact: This feature improves cell coverage performance from the signal level
and quality aspects and provide benefits for KPIs. For example, reduce the call drop
rate and improve the access success rate and traffic volume of a cell.
Positive impact: none
Issue 01 (2015-02-14)

31
SONMaster
5 Version Mapping
Version Mapping
For details about how to activate this feature, and mapping between the SONMaster, NE
software, and other software, see iManager SONMaster V100R015***_ReleaseDoc_ENG.
You can obtain iManager SONMaster V100R015***_ReleaseDoc_ENG by performing the
following steps:
1.
Contact Huawei technical support engineers to log in to http://support.huawei.com.
2.
Obtain iManager SONMaster V100R015***_ReleaseDoc_ENG mapping the SONMaster

version in the following path: Product Support > Wireless Network > Wireless Network
Management > M2000 > M2000-GUL > iManager SONMaster.
Issue 01 (2015-02-14)

32
SONMaster
Engineering Guidelines
About This Chapter

6.1 UMTS DL Capacity Optimization RRM Based
6.2 UMTS DL Coverage Optimization RRM Based
Issue 01 (2015-02-14)

33
SONMaster
6.1 UMTS DL Capacity Optimization RRM Based

6.1.1 Activation Advice
You are advised to activate this feature in the following scenarios to decrease network congestion
problems and improve network performance:
l
Scenarios where the load on the live network is heavy and severe downlink congestion
occurs, or severe uplink and downlink CE congestion occurs.
Routine network optimization scenarios. This feature does not apply to new deployment,
reparenting, or expansion scenarios.
Networking scenarios: This feature does not apply to inter-RAT networking, multi-RRU
cell, repeater, or digital combination and division scenarios. The devices involved in one
task must be provided by the same vendor.
Network architecture scenarios: This feature does not apply to network sharing scenarios.
Radio scenarios: macro cells in densely-populated urban areas, urban areas, and suburban
areas. Currently, this feature does not apply to special coverage scenarios such as highspeed moving coverage, tunnel coverage, super-distance coverage, and indoor coverage
scenarios.
This feature applies only to macro base stations. It does not support small-cell base stations
and does not adjust or optimize such base stations.
6.1.2 Information Collection Before the Deployment

Table 6-1 describes the requirements to be met before the deployment.
Table 6-1 Requirements to be met before the deployment
Issue 01 (2015-02-14)
Feature
Check Item
Identification Criteria
Remarks
UMTS DL
Capacity
Optimizat
ion RRM
Based
1. Whether
version
mapping
requirements
are met
For version mapping

requirements of peripheral
products, see 5 Version
Mapping.

34
SONMaster
Feature
Check Item
Remarks
2. Whether
networking
scenarios
meet
requirements
Versions earlier than

R014C01SPC200 do not
apply to RAN Sharing and
MOCN scenarios. All
versions do not apply to
antenna optimization in interRAT co-antenna scenarios.
l High-speed moving
coverage scenarios, which
are indicated by
HighWay in engineering
parameters.
CCO does not support the

following scenarios:
l High-speed cell
l Tunnel cell
l Multi-RRU cell
Issue 01 (2015-02-14)

l Tunnel coverage
scenarios, which are
indicated by Tunnel
Coverage in engineering
parameters.
l Multi-RRU coverage
indicated by Contain
Redundant RRU in
engineering parameters.
35
SONMaster
Feature
Check Item
Remarks
3. Whether
data prepared
for task
creation meets
requirements
The following data must be

prepared for CCO:
The data that needs to be

prepared is as follows:
l Engineering parameters
l Engineering parameters:
You need to obtain the
accurate engineering
parameters for cells to be
optimized, such as the
mechanical downtilt
angle, azimuth, and site
height.
l Antenna files
l Antenna files: You need to

prepare the original
antenna pattern files
corresponding to the cell
antenna model. If a RET
antenna is used, the
antenna pattern files
corresponding to different
electrical downtilt angles
(for example, 0 to 10
degrees) are included.
Antenna pattern files are
used for calculating
antenna gains during
optimization advice
generation. An improper
antenna file will affect the
evaluation accuracy. If no
original antenna pattern
file corresponding to the
cell antenna model is
available, you can use
different types of antenna
files that have the same
beamwidth and antenna
gain.
Issue 01 (2015-02-14)

36
SONMaster
Feature
Check Item
Remarks
4. Whether the
switches meet
requirements
l The soft handover switch

is turned on. The intrafrequency handover
parameter adjustment is
involved in CCO.
Therefore, you need to
check the status of the soft
handover algorithm
switch.
l The soft handover switch

is turned on: Run the LST
UCORRMALGOSWIT
CH command to check
whether
HO_INTRA_FREQ_SO
FT_HO_SWITCH in the
HoSwitch parameter is set
to ON. If it is, intrafrequency soft handovers
are allowed.
l The inter-frequency hard

handover switch is turned
on. The inter-frequency
handover parameter
adjustment is involved in
CCO. Therefore, you need
to check the status of the
hard handover algorithm
switch.
5. Impact of
enabling
SONMaster
features on the
network
Impact of turning on MR/

CHR switches on the RNC
CPU load: All MR switches
are turned on and the period
is set to 12s. Compared with
the scenario where MR
switches are turned off, the
absolute value of the SPU
(BSC6900)/BSC6910 CPU
increases by 3%.
l The inter-frequency hard

handover switch is turned
on: Run the LST
UCORRMALGOSWIT
CH command to check
whether
HO_INTER_FREQ_H
ARD_HO_SWITCH in
the HoSwitch parameter
is set to ON. If it is, interfrequency hard handovers
are allowed.
-
6.1.3 Feature Deployment

Deployment Requirements
l
NE Function Requirements
None
Software and Hardware Requirements

Server requirements: The SONMaster has been deployed.
Issue 01 (2015-02-14)

37
SONMaster
NE requirements: Hardware devices that support MR data collection, for example, SAU
boards, are available.
l
License Requirements
The following license control item is added: CCO-UMTS DL Capacity Optimization
RRM Based.
Operation Permission Requirements

You have obtained the operation rights for UMTS CCO Browser and UMTS CCO
Management under Application-Level Operation Rights > CCO. If not, apply for the
operation rights from the administrator.
Data Preparation
You must prepare the following data before deploying UMTS DL Capacity Optimization RRM
Based:
l
UMTS engineering parameters, as listed in Table 6-2.
Zone template parameters, as listed in Table 6-3.
Optimization policy parameters, as listed in Table 6-4.
Power and switch parameters, as listed in Table 6-5. Such parameters apply only to stable
high-load cells, and do not apply to traffic burst cells. In manual mode, the SONMaster
displays all problematic cells and their neighboring cells after long-period problematic cells
are identified. It also allows you to set adjustable cells and parameters one by one and adjust
the ranges, parameters, and parameter ranges for the cells to be adjusted by the SONMaster.
Global parameters for optimization tasks, as listed in Table 6-6. Such parameters apply
only to traffic burst cells and their neighboring cells.
Types of cell antennas: You need to import the antenna data file before selecting antenna
types. For detailed operations, see (Optional) Importing the Antenna Data Files in Getting
Started.
Basic parameters for optimization tasks, as listed in Table 6-7.
Table 6-2 UMTS engineering parameters

Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
RNC ID*
int
0 - 65535
Yes
CELL NAME
string
String Length: 0 - 64
The following
feature is
mandatory:
UMTS ANR
Issue 01 (2015-02-14)
CELL ID*
int
0 - 65535
Yes
MCC*
string
String Length: 3
Yes
MNC*
string
Yes
LONGITUDE*
float
-180.0 - 180.0
Yes

38
SONMaster
Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
LATITUDE*
float
-90.0 - 90.0
Yes
AZIMUTH*
float
0.0 - 360.0
Yes
BEAM WIDTH
float
0.0 - 360.0
No
ANTENNA
HEIGHT
float
0.0 - 65535.0
The following
feature is
mandatory:
UMTS CCO
LAC
int
0 - 65535
The following
feature is
mandatory:
UMTS ANR
RAC
int
0 - 65535
The following
feature is
mandatory:
UMTS ANR
SAC
int
0 - 65535
No
BAND No.
enumeration
BAND1, BAND2, BAND3,

BANDINDNOTUSED
The following
features are
mandatory:
UMTS ANR
UMTS SC SelfOptimization
UL UARFCN
int
0 - 65535
No
DL UARFCN
int
0 - 65535
The following
features are
mandatory:
UMTS ANR
UMTS CCO
SCRAMBLING
CODE
int
0 - 511
The following
features are
mandatory:
UMTS ANR
Issue 01 (2015-02-14)

39
SONMaster
Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
OUTDOOR
enumeration
Yes, No
The following
feature is
mandatory:
Default value: Yes
UMTS CCO
DIRECTIONAL
enumeration
Yes, No
No
Default value: Yes

HIGHWAY
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
TUNNEL
COVERAGE
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
SUPERDISTANCE
COVERAGE
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
CONTAIN
REDUNDANT
RRU
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
APPLICATION
SCENARIO
enumeration
DenseUrban, Urban,
SubUrban, Rural,
HighSppedRailway, Edge,
HighBaseStation, Other
Default value: Urban
The following
feature is
mandatory:
Vendor*
enumeration
Alcatel, Ericsson, Huawei,

Motorola, Nokia&Siemens,
Nortel, ZTE, NSN
Yes
REMARKS
string
No
ANTENNA
GAIN
float
0.0 - 65535.0
No
Mechanical Tilt
Angle
float
-90.0 - 90.0
The following
feature is
mandatory:
UMTS CCO
Issue 01 (2015-02-14)

40
SONMaster
Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
E-Tilt Angle
float
-90.0 - 90.0
The following
feature is
mandatory when
this parameter is
not configured in
the configuration
data: UMTS
COO.
RNC NAME
string
No
Cluster
string
No
Table 6-3 Optimization zones and optimization object parameters

Parameter Name
Parameter Description
Zone Name
This parameter specifies the optimization zone name.
Remarks
This parameter specifies the information of the optimization zone.
Vendor
This parameter specifies the vendor types of the optimization objects.

l If this parameter is set to Huawei, the optimization objects are all
the Huawei cells managed by the SONMaster.
l If this parameter is set to Ericsson, the optimization objects are
all the Ericsson cells managed by the SONMaster.
l If this parameter is set to NSN, the optimization objects are all the
NSN cells managed by the SONMaster.
RAT
This parameter specified the type of the cells to be optimized. You

are advised to set this parameter when the optimization objects are
cells.
l If this parameter is set to GSM, the cells to be optimized are GSM
cells.
l If this parameter is set to UMTS, the cells to be optimized are
UMTS cells.
l If this parameter is set to LTE, the cells to be optimized are LTE
cells.
Cell List
Issue 01 (2015-02-14)
Available Objects and Selected Objects are displayed in navigation

trees. You can select cells to be optimized by using any of the
following methods: navigation tree, template import, and GIS
window.

41
SONMaster
Table 6-4 Optimization policy parameters for UMTS DL Capacity Optimization
Name
Meaning
Value
Description
Optimization
Type
This parameter
specifies the
optimization
objective of a CCO
task.
Enumerate
d values:
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
l Longperiod
load
balanci
ng
l Traffic
burst
load
balanci
ng
Y -
Effe
ctiv
e
Mo
de
Nex
t
peri
od
Default
value:
Select All
Issue 01 (2015-02-14)

42
SONMaster
Name
Meaning
Value
Description
Optimization
Mode
This parameter
specifies the
optimization mode.
The value
Parameter check
apply only to longperiod load
balancing. The other
values apply to both
long-period load
balancing and traffic
burst load balancing.
Enumerate
d values
(You can
select
multiple
values):
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
l Power
optimiz
ation
l Fault
detectio
n
l Parame
ter
check
l Capacit
y
expansi
on
l Feature
optimiz
ation
l Handov
er
adjustm
ent
Default
value:
Select All
Issue 01 (2015-02-14)

43
SONMaster
Name
KPI monitor
time
Meaning
Value
This parameter
specifies the time
range for collecting
MR/PM data. You
are allowed to select
multiple values. If
you do not set this
parameter, the
SONMaster collects
such data within 24
hours by default.
Values: 0
to 23 The
value 0
indicates
the time
segment
from
00:00:00 to
00:59:59.
You can
infer the
other time
segments
in the same
way.
Description
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Y -
Nex
t
peri
od
Nex
t
peri
od
Default
value: 24
Unit: hour
Traffic burst
task start delay
period
Issue 01 (2015-02-14)
This parameter takes

effect when you
create both Longperiod load
balancing and
Traffic burst load
balancing tasks.
This parameter
determines the time
of starting an
emergent task.
Values:
0~14
Default
value: 7
Unit: day

44
SONMaster
Name
Meaning
This parameter
specifies the number
of KPI monitoring
days when longperiod optimization
advice is delivered. If
KPIs deteriorate
during this period,
the SONMaster rolls
back the
optimization advice.
Long-period
evaluation
period
This parameter takes

effect when you
create a Longperiod load
balancing task. The
number of data
collection days and
this parameter
determine the period
of a round of
optimization.
Traffic Burst
Monitor Period
Issue 01 (2015-02-14)
This parameter
specifies the period
for monitoring the
load of traffic burst
cells.
Value
Description
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Values:
1~7
Default
value: 3
Nex
t
peri
od
The period for

monitoring
traffic burst
problems must
be an integral
multiple of the
period for
collecting PM
data on the live
network. If not,
the SONMaster
displays an error
message.
Unit: day
Value
range: 15,
30, 45, and
60
Default
value: 15
Unit:
minute

45
SONMaster
Name
Meaning
Specified
network busy
hours
Used for selecting

neighboring cells
and performing
rollback evaluation
during load
balancing.
Value
Value
range:
00:00 to
24:00
Default
value:
08:00 to
12:00 and
18:00 to
21:00
Unit: None
Manually
Adjusting
Problematic
Cells
If this parameter is
set to Disallow, no
manual adjustment is
allowed and the next
step is automatically
performed after the
SONMaster detects
problematic cells
through KPI
monitoring.
Enumerate
d values:
Description
The start time

and end time of
the specified
network busy
hour must be
exactly divided
by the number
of hours within
this time range.
For example, the
time range can
be 08:00 to
12:00.
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
l Disallo
w
l Allow
(default
value)
If this parameter is
set to Allow, you can
perform manual
adjustment within 24
hours after the
SONMaster detects
problematic cells
through KPI
monitoring. Then,
the next step is
performed.
KPI monitoring parameters
Issue 01 (2015-02-14)

46
SONMaster
Name
Meaning
Long-period
RRC
setup
success
rate
threshold
Used for filtering

neighboring
cells
during long-period
load balancing.
Value
Value
range:
00.00 to
100.00
Default
value:
98.00
Description
For internal use

of power and
handover
algorithms.
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Unit: %
Long-period
RAB
setup
success
rate
threshold
Used for filtering

neighboring
cells
during long-period
load balancing.
Value
range:
00.00 to
100.00
Default
value:
98.00
For internal use

of power and
handover
algorithms.
Unit: %
Long-period
RAB call drop
rate threshold
Used for filtering

neighboring
cells
during long-period
load balancing.
Value
range: 0 to
100
Default
value: 0.8
For internal use

of power and
handover
algorithms.
Unit: %
High
load
threshold
on
DL total power
Issue 01 (2015-02-14)
High load threshold

on DL total power,
which is specified in
the long-period load
balancing module.
This parameter is
used
to
check
whether a cell is in
high load in a certain
time range based on
the power usage.
Value
range:
75.00 to
100.00
Default
value:
75.00
For identifying
high-load cells
during longperiod load
balancing.
Unit: %

47
SONMaster
Name
Meaning
Weak coverage
RSCP
threshold
Used for analyzing
MRs with weak
coverage.
Value
Description
Value
range:
[-110,
-105, -100,
-95, -90,
-85, -80,
-70, -60]
For internal use

of handover
algorithms.
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Default
value: -105
Unit: dBm
Value
range: -150
to 150
Interference
RSCP
threshold
A
d
v
a
n
c
e
d
Default
value: -95
For internal use

of power
algorithms.
Unit: dBm
Value
range: -10
to 60
Pilot pollution
RSCP
difference
threshold
For internal use

of
power
algorithms.
Default
value: 5
Unit: dB
Pilot pollution
overlapped
coverage cell
count threshold
Used for analyzing

MRs with pilot
pollution.
Value
range: 0 to
100
For internal use

of
power
algorithms.
Default
value: 4
Unit: None
Min.proportion
of
adjusted
pilot power to
max.Tx power
Value
range: 0 to
20
For internal use

of
power
algorithms.
Default
value: 5
Unit: %
Issue 01 (2015-02-14)

48
SONMaster
Name
Meaning
Max.proportio
n of adjusted
pilot power to
max.Tx power
Value
Description
Value
range: 0 to
20
For internal use

of
power
algorithms.
Default
value: 10
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Unit: %
Parameters for identifying problematic cells
High load
threshold on
DL non-H
power
Used for identifying

long-period highload cells.
Value
range: 0 to
100
Default
value: 60
Unit: %
High load
threshold on
DL power
congestion

Value
range: an
integer
greater
than
or
equal to 0
Default
value: 5
Unit: None
High load
threshold on
UL and DL CE
congestion

Value
range: an
integer
greater
than
or
equal to 0
Default
value: 5
Unit: None
Issue 01 (2015-02-14)

49
SONMaster
Name
Meaning
High load
threshold on
traffic burst DL
power

traffic burst cells.
Value
Value
range: 0 to
100
Default
value: 30
Description
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Unit: %
High load
threshold on
traffic burst DL
non-H power
Hourly traffic
burst DL power
congestion
threshold
The value of this

parameter must be
less than or equal to
that of High load
threshold on traffic
burst DL power.

Value
range: 0 to
100
Default
value: 30
Unit: %
Value
range: an
integer
greater
than 0
Default
value: 40
Unit:
integer
Hourly traffic
burst UL and
DL CE
congestion
threshold

Value
range: an
integer
greater
than 0
Default
value: 40
Unit:
integer
Issue 01 (2015-02-14)

50
SONMaster
Name
Meaning
Traffic
burst
RRC
setup
success
rate
threshold
Used for filtering

Value
Value
range:
00.00 to
100.00
Default
value:
90.00
Description
For internal use

of power and
handover
algorithms.
A
d
v
a
n
c
e
d
M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Y -
Nex
t
peri
od
Unit: %
Traffic
burst
RAB
setup
success
rate
threshold
Used for filtering

Value
range:
00.00 to
100.00
Default
value:
90.00
For internal use

of power and
handover
algorithms.
Unit: %
Traffic
burst
RAB call drop
rate threshold
Used for filtering

Value
range: 0 to
100
Default
value: 10
For internal use

of power and
handover
algorithms.
Unit: %
Issue 01 (2015-02-14)

51
SONMaster
Table 6-5 Power and switch parameters
Name
Meaning
Allow
Adjusting Pilot
Power
This parameter
specifies whether
pilot power
adjustment is
allowed.
Min_Pilot_Proportion
This
parameter
specifies
the
minimum percentage
of the pilot power of
the problematic cells
or the cells to be
adjusted
in
the
maximum
TX
power.
Max_Pilot_Pro
portion
Allow
Adjusting
Handover
Parameter
Issue 01 (2015-02-14)
This
parameter
specifies
the
maximum
percentage of the
pilot power of the
problematic cells or
the cells to be
adjusted
in
the
maximum
TX
power.
This
parameter
specifies whether the
cells to be adjusted
support problematic
cell load sharing
through
handover
parameter
optimization.
Value
Description
Value
range: 0 to
20
Default
value: 5
Unit: %
Value
range: 0 to
20
Default
value: 10
Unit: %
A
d
v
a
n
c
e
d
These
parameters
apply only to
cells involved in
long-period load
balancing
(including nonperiodic and
periodic load
balancing).
They do not
apply to cells
involved in
occasional load
balancing.
Enumerate
d values:
l Yes
l No

M
a
n
d
a
t
o
r
y
R
i
s
k
y
Effe
ctiv
e
Mo
de
Curr
ent
peri
od
Curr
ent
peri
od
Curr
ent
peri
od
Curr
ent
peri
od
52
SONMaster
Table 6-6 Global parameters for optimization tasks

Type
Name
CGI
Value
-
Meaning
UMTS CGI
format: MccMncRNCIdCellId
Data Source
Network plan
(negotiation not
required)
This
parameter is
used to
maintain the
list of all
cells on the
network of
customers.
-
Is Active
Enumerated
values:
l Yes
(default
value)
l No
Is Lock
Enumerated
values:
l Yes
l No
(default
value)
Pilot Power
Proportion_Min
Parameters for
adjusting the
pilot power
Default pilot
power
adjustment
range: 0 to
20
Default
value of
Pilot Power
Proportion
_Min: 5
You can
adjust
parameters
only for
active cells.
All
parameters
for inactive
cells cannot
be adjusted.
User-defined
This
parameter
specifies
whether cell
pilot power
adjustment is
allowed.
User-defined
This
parameter
specifies the
minimum
percentage of
the pilot
power in the
maximum
power.
Default
value of
Pilot Power
Proportion
_Max: 10
Issue 01 (2015-02-14)

53
SONMaster
Type
Name
Value
Pilot Power
Propotion_Max
Unit: %
Is Lock
Adjustable
handover
parameter of
cells
Enumerated
values:
l Yes
l No
(default
value)
Meaning
Data Source
This
parameter
specifies the
maximum
percentage of
the pilot
power in the
maximum
power.
This
parameter
specifies
whether cell
handover
parameter
adjustment is
allowed.
User-defined
Table 6-7 Basic Parameters for Optimization Tasks

Name
Meaning
Value
Description
Service
name
This parameter uniquely

identifies a task.
The value is a
character
string.
You need to set this

parameter when creating
an optimization task. The
value cannot be changed
in subsequent operations.
Service
type
This parameter identifies the

type of an SON feature.
Huawei:

l UMTS
CCO-RRM
Based
l UMTS
CCO-RF
Based
You can select only one

option.
Ericsson:
l DL
Capacity
l DL
Coverage
l UMTS
CCO-RRM
Based
(Capacity)
Issue 01 (2015-02-14)

54
SONMaster
Name
Meaning
Value
Description
Start mode
This parameter specifies the

method of starting an
optimization task.
Enumerated
values:
l Manual
(default
value)
l Automatic
l Schedule
Start time
This parameter specifies the time

when an optimization task will
start after Start Mode is set to
Schedule.
Stop mode

method of stopping an
optimization task.
Enumerated
values:
l Manual
(default
value)
l Schedule
l Repeat
interval
Stop time

stop after Stop Mode is set to
Schedule.
Repeat
interval

number of execution periods
after which an optimization task
will automatically stop when
Stop Mode is set to Repeat
interval. The value of Repeat
interval determines the number
of execution periods within
which the optimization task is
running.
Value range:
1~1000

method of executing
optimization advice, which
supports open-loop and closedloop.
Enumerated
values:
Advice
execution
Default value:
1
l Manual
(default
value)
l Automatic
l Schedule
Issue 01 (2015-02-14)

55
SONMaster
Name
Meaning
Value
Description
Execution
time
This parameter specifies a time

point within 24 hours. The
SONMaster executes
optimization advice at the time
point every day.
This parameter specifies

a time point at which the
SONMaster
automatically executes
optimization advice
every day when Advice
Execution is set to
Schedule.

mode for rolling back
optimization advice. The
parameter setting takes effect on
both quick evaluation and
coverage and capacity
evaluation.
Enumerated
values:
This parameter is
dedicated to CCO tasks
and is involved in both
coverage optimization
and load balancing
scenarios.
Advice
rollback
l Manual
(default
value)
l Automatic
l Schedule
Rollback
time

when optimization advice is
rolled back when Advice
Rollback is set to Schedule.
Format:
HH:MM:SS
This parameter is
dedicated to CCO tasks.
Default value:
03:00:00
Process
Figure 6-1 shows the process of UMTS CCO. Table 6-8 describes the process.
Issue 01 (2015-02-14)

56
SONMaster
Figure 6-1 Process of UMTS CCO
Table 6-8 Process description
Issue 01 (2015-02-14)
Procedure
Description
Log in to the
SONMaster
For detailed operations, see Logging In to the SONMaster in

Getting Started.
(Optional) Connect to
the OSS
For detailed operations, see (Optional) Connecting to the OSS in

Getting Started.
Prepare basic data.
For detailed operations, see Preparing Basic Data in Getting

Started.

57
SONMaster
Procedure
Description
(Optional) Set
parameters for UMTS
CCO
For detailed operations, see (Optional) Setting Parameters for

UMTS CCO under the UMTS CCO node in CCO Management
User Guide.
Create and start a UMTS

CCO task
For detailed operations, see Creating and Starting a UMTS CCO

Task under the UMTS CCO node in CCO Management User
Guide.
Executing a UMTS
CCO Task
For detailed operations, see Executing a UMTS CCO Task under

the UMTS CCO node in CCO Management User Guide.
(Optional) Check the

information about
exceptions during
UMTS CCO
optimization
For detailed operations, see (Optional) Checking the Information

About Exceptions During UMTS CCO Optimization under the
UMTS CCO node in CCO Management User Guide.
(Optional) Evaluate the

optimaization effect of
UMTS CCO
optimization
For detailed operations, see (Optional) Evaluating the

Optimaization Effect of UMTS CCO Optimization under the
Activation Observation
After you activate the feature, you can perform activation observation using the methods in
Table 6-9:
Table 6-9 Observation methods
Issue 01 (2015-02-14)
Method
Description
Reference
Method 1
Check the task running status on the

task management GUI of the
SONMaster.
See Window for CCO Task

Management in 2.4
Introduction to the Main
Window.
Method 2
Check the generated logs after the

feature is activated.
See the following section in

SONMaster System Management
User Guide : Log Management >
Querying SON Logs.
Method 3
Check the identified problematic cells

on the problematic area construction
GUI.
See Wizards for Optimization

Tasks in 2.4 Introduction to the
Main Window.

58
SONMaster
Method
Description
Reference
Method 4
Check the CCO optimization advice on

the optimization advice management
GUI. You are advised to do so after a
feature running period.
See the following section in CCO

Management User Guide: UMTS
CCO > Executing a UMTS CCO
Task - RRM Based (Capacity)
(Huawei).
Feature Deactivation
To deactivate a feature, you can stop the running optimization task of this feature:
1.
Select the running optimization task.
2.
Click
to stop the task.
6.1.4 Monitoring
When load imbalance problems exist on the network and network conditions do not change,
activating UMTS DL Capacity Optimization RRM Based will solve high-load problems and
traffic burst problems, reduce the number of overloaded cells, the load of traffic burst cells, and
the power congestion occurrence times, and improve the access success rate nad network
throughput. This also ensures that network coverage does not deteriorate or the coverage
deterioration is acceptable. You can evaluate the feature performance by monitoring the
following counters:
l
Load counters:
Total HSDPA throughput before and after optimization
Number of overloaded cells before and after optimization
Traffic KPIs:
RRC setup failure rate
RAB setup failure rate
Call drop rate
Handover success rate
If KPIs deteriorate after the optimization advice is delivered and executed, check whether KPI
deterioration is caused by the optimization. If so, use the optimization advice rollback function
to restore the previous network parameters. You can use the rollback function to restore the
network parameters to the last optimization period.
You can check the optimization effect using one of the following methods:
l
Perform optimization effect evaluation using the KPI evaluation function.

For detailed operations, see (Optional) Evaluating the Optimization Effect of UMTS CCO
Optimization under the UMTS CCO node in CCO Management User Guide.
Check the values of performance KPIs before and after the optimization. The performance
KPIs are as follows:
RRC setup success rate;
Issue 01 (2015-02-14)

59
SONMaster
RAB setup success rate;

RAB call drop rate;
Soft HO success rate;
Inter-cell hard HO success rate;
DL power congestion rate
DL power congestion count
UL and DL CE congestion rate
UL and DL CE congestion count
NOTE
You are advised to pay attention to KPI changes before the optimization. The optimization should
not be performed before, after, or during holidays or major events because they will cause KPI
fluctuation.
6.1.5 Parameter Optimization

This section describes the optimization parameters. After UMTS DL Capacity Optimization
RRM Based is activated, you can properly adjust the parameters, such as those listed in Table
6-10, to achieve better optimization effect.
Table 6-10 Optimization Parameters
Parameter Name
Repeat interval
High load threshold on

DL total power
Setting Notes
This parameter indicates the operation times of long-period load
balancing. A larger value of this parameter indicates more rounds
of long-period load balancing will be performed. By default, a
period is set to 10 days. You can reconfigure the period duration on
the server.
This parameter specifies the power usage threshold for identifying
long-period high-load cells. If the power usage of a cell is larger
than the value of this parameter, the SONMaster may identify this
cell as a long-period high-load cell.
A larger value of this parameter indicates that less high-load cells
will be identified but the load will be more severe.
A smaller value of this parameter indicates that more high-load cells
will be identified.

DL non-H power
This parameter specifies the non-H power usage threshold for

identifying long-period high-load cells. If the non-H power usage
of a cell is larger than the value of this parameter, the SONMaster
may identify this cell as a long-period high-load cell.
will be identified.
Issue 01 (2015-02-14)

60
SONMaster
Parameter Name
Setting Notes
This parameter specifies the DL power congestion count threshold
for identifying long-period high-load cells. If the DL power
congestion count of a cell is larger than the value of this parameter,
the SONMaster may identify this cell as a long-period high-load
cell.

DL power congestion

will be identified but the congestion of high-load cells will be more
severe.
will be identified but the congestion of high-load cells will be less
severe.

UL and DL CE
congestion
This parameter specifies the UL and DL CE congestion count

threshold for identifying long-period high-load cells. If the UL and
DL CE congestion count of a cell is larger than the value of this
parameter, the SONMaster may identify this cell as a long-period
high-load cell.
severe.
severe.
RRC setup success rate

threshold
This parameter specifies the threshold for the RRC setup success
rate. If the RRC setup success rate for a cell is larger than the value
of this parameter, the SONMaster may identify this cell as a
candidate target cell.
A larger value of this parameter indicates that less candidate target
cells may be identified based on the RRC setup success rate.
A smaller value of this parameter indicates that more candidate
target cells may be identified based on the RRC setup success rate.
RAB setup success rate

threshold
This parameter specifies the threshold for the RAB setup success
rate. If the RAB setup success rate for a cell is larger than the value
of this parameter, the SONMaster may identify this cell as a
candidate target cell.
A larger value of this parameter indicates that less candidate target
cells may be identified based on the RAB setup success rate.
A smaller value of this parameter indicates that more candidate
target cells may be identified based on the RAB setup success rate.
Issue 01 (2015-02-14)

61
SONMaster
Parameter Name
RAB call drop rate

threshold
Setting Notes
This parameter specifies the threshold for the RAB call drop rate.
If the RAB call drop rate for a cell is smaller than the value of this
parameter, the SONMaster may identify this cell as a candidate
target cell.
A larger value of this parameter indicates that more candidate target
cells may be identified based on the RAB call drop rate.
A smaller value of this parameter indicates that less candidate target
cells may be identified based on the RAB call drop rate.
Specified network
busy hours
This parameter is used for evaluating the performance of candidate

target cells.
Weak coverage RSCP

threshold
This parameter specifies the weak coverage RSRP threshold and is

used to identify weak coverage problems.
A larger value of this parameter indicates that more weak coverage
problems may be identified based on the RSRP.
A smaller value of this parameter indicates that less weak coverage
Interference RSCP
threshold
This parameter specifies the interference and pilot pollution RSCP

threshold and is used to identify interference and pilot pollution
problems.
A larger value of this parameter indicates that less interference and
pilot pollution problems may be identified based on the RSCP.
A smaller value of this parameter indicates that more interference
and pilot pollution problems may be identified based on the RSCP.
Pilot pollution RSCP

difference threshold
This parameter specifies the pilot pollution RSCP difference

threshold and is used to identify pilot pollution problems.
A larger value of this parameter indicates that more pilot pollution
problems may be identified based on the RSCP difference.
A smaller value of this parameter indicates that less pilot pollution
problems may be identified based on the RSCP difference.
Pilot pollution
overlapped coverage
cell count threshold
This parameter specifies the threshold for the number of cells with
pilot pollution problems and is used to identify pilot pollution
problems.
A larger value of this parameter indicates that less pilot pollution
A smaller value of this parameter indicates that more pilot pollution
Issue 01 (2015-02-14)

62
SONMaster
Parameter Name
Setting Notes
This parameter is used to set the minimum pilot power. You are
advised to retain the default value.
Min.proportion of
adjusted pilot power to
max.transmit power
A larger value of this parameter indicates higher pilot power and

larger cell coverage. This results in interference and affects network
capacity.
A smaller value of this parameter indicates lower pilot power and
smaller cell coverage. This affects handover and network capacity.
This parameter is used to set the minimum pilot power. You are
advised to retain the default value.
Max.proportion of
adjusted pilot power to
max.transmit power
A larger value of this parameter indicates higher pilot power and

larger cell coverage. This results in interference and affects network
capacity.
A smaller value of this parameter indicates lower pilot power and
smaller cell coverage. This affects handover and network capacity.
Traffic Burst Monitor

Period

traffic burst DL power
You are advised to set this parameter based on the onsite traffic
statistics reporting period.
This parameter specifies the power usage threshold for identifying
traffic burst high-load cells. If the power usage of a cell is larger
than the value of this parameter, the SONMaster may identify this
cell as a traffic burst high-load cell.
will be identified.

traffic burst DL non-H
power
This parameter specifies the non-H power usage threshold for

identifying traffic burst high-load cells. If the non-H power usage
of a cell is larger than the value of this parameter, the SONMaster
may identify this cell as a traffic burst high-load cell.
will be identified.
Hourly traffic burst DL

power congestion
threshold
Issue 01 (2015-02-14)
This parameter specifies the DL power congestion count threshold

for identifying traffic burst high-load cells. If the DL power
congestion count of a cell is larger than the value of this parameter,
the SONMaster may identify this cell as a traffic burst high-load
cell.

63
SONMaster
Parameter Name
Setting Notes
severe.
severe.
Hourly traffic burst UL

and DL CE congestion
threshold
This parameter specifies the UL and DL CE congestion count

threshold for identifying traffic burst high-load cells. If the UL and
DL CE congestion count of a cell is larger than the value of this
parameter, the SONMaster may identify this cell as a traffic burst
high-load cell.
severe.
severe.
6.2 UMTS DL Coverage Optimization RRM Based

6.2.1 Activation Advice
You are advised to activate this feature when the following scenarios are met to relieve KPI
deterioration caused by weak coverage, pilot pollution, and coverage overlapping and improve
network performance:
l
Project scenarios: This feature is developed for solving coverage and capacity problems on
existing networks, and does not apply to new deployment, reparenting, or expansion
scenarios.
Wireless scenarios: This feature does not apply to highway, tunnel, and super-distance
coverage scenarios. This feature applies to indoor, urban, and suburban coverage (30 km
or less) scenarios.
Networking scenarios: In this version, this feature does not apply to inter-RAT coverage,
multi-vendor networking, special cell, or MOCN/MORAN scenarios. This feature applies
to single-carrier coverage, multi-carrier coverage, and multi-band coverage scenarios.
Special cell scenarios: This feature does not apply to multiple RRUs in one cell and
repeaters.
6.2.2 Information Collection Before the Deployment

Table 6-11 describes the requirements to be met before the deployment.
Issue 01 (2015-02-14)

64
SONMaster
Table 6-11 Requirements to be met before the deployment

Feature
Name
Check Item
Remarks
UMTS DL
Coverage
Optimization
RRM Based
1. Whether
version
mapping
requirements
are met
For details about the version

mapping between
peripheral products, see 5
Version Mapping.
2. Whether
networking
scenarios
meet
requirements
CCO supports only routine

network OM scenarios and
does not apply to site
deployment scenarios.
l High-speed moving
coverage scenarios,
which are indicated by
HighWay in
CCO does not support RAN

Sharing and MOCN
scenarios and does not
apply to antenna
optimization in inter-RAT
co-antenna scenarios.
CCO does not support the
following scenarios:
l High-speed cell
l Tunnel cell
l Tunnel coverage
indicated by Tunnel
Coverage in
l Multi-RRU coverage
indicated by Contain
Redundant RRU in
l Multi-RRU cell
Issue 01 (2015-02-14)

65
SONMaster
Feature
Name
Check Item
Remarks
3. Whether
the switches
meet
requirements
l The soft handover

switch is turned on. The
intra-frequency
handover parameter
adjustment is involved.
Therefore, you need to
check the status of the
soft handover algorithm
switch.
Run the LST

UCORRMALGOSWITC
H command to check
whether
HO_INTRA_FREQ_SOF
T_HO_SWITCH in the
HoSwitch parameter is set
to ON. If it is set to ON,
intra-frequency soft
handovers are enabled.
l For the license related to

the feature InterFrequency Redirection
Based on Distance,
check whether the
license control item
LQW1HDR03 is
enabled.
the feature Inter-RAT
Redirection Based on
Distance:
Check whether the
LQW1HDR03 is
enabled.
Check whether the
LQW1IRRBD01 is
enabled.
l The soft handover

switch is turned on: Run
the LST
UCORRMALGOSWI
TCH command to check
whether
HO_INTRA_FREQ_S
OFT_HO_SWITCH in
the HoSwitch parameter
is set to ON. If it is, intrafrequency soft
handovers are allowed.
the feature InterFrequency Redirection
Based on Distance,
check whether the
LQW1HDR03 is
enabled. You can run the
DSP LICUSAGE
command to check
whether LQW1HDR03
exists in the query result.
the feature Inter-RAT
Redirection Based on
Distance: You can run
the DSP LICUSAGE
command to check
whether LQW1HDR03
and LQW1IRRBD01
exist in the query result.
Issue 01 (2015-02-14)

66
SONMaster
Feature
Name
Check Item
Remarks
4. Impact of
activating
SONMaster
features on
the network
Impact of turning on MR/

CHR switches on the RNC
CPU load:
l All MR switches are

turned on and the period
is set to 12s. Compared
with the scenario where
MR switches are turned
off, the absolute value of
the SPU (BSC6900)/
BSC6910 CPU
increases by 3%.
l After all CHR switches
are turned on, the
absolute value of the
SPU (BSC6900)/
BSC6910 CPU
increases by 3%.
l After all MR and CHR
switches are turned on,
the absolute value of the
SPU (BSC6900)/
BSC6910 CPU
increases by 5%.
This algorithm subscribes to
MRs (for example, periodic
intra-frequency MRs,
periodic inter-frequency
MRs, periodic inter-RAT
MRs, BLER, UE TX
POWER, and LCS_RTT)
and CHR events (RRC
access block). Before
activating this feature, you
need to evaluate whether the
current CPU load exceeds
the value of Flow Control
Threshold set on the RNC.
6.2.3 Feature Deployment
Issue 01 (2015-02-14)

67
SONMaster
Deployment Requirements
l
NE Function Requirements
None
Software and Hardware Requirements

Server requirements: The SONMaster has been deployed.
NE requirements: Hardware devices that support MR data collection, for example, SAU
boards, are available.
License Requirements
The following license control item is added: CCO-UMTS DL Coverage Optimization
RRM Based.
Operation Permission Requirements

You have obtained the operation rights for UMTS CCO Browser and UMTS CCO
Management under Application-Level Operation Rights > CCO. If not, apply for the
operation rights from the administrator.
Data Preparation
You must prepare the following data before deploying UMTS DL Coverage Optimization
RRM Based:
l
UMTS engineering parameters, as listed in Table 6-12.
Zone template parameters, as listed in Table 6-13.
List of global parameters for optimization tasks.

Types of cell antennas: You need to import the antenna data file before selecting antenna
types. For detailed operations, see (Optional) Importing the Antenna Data Files in
Getting Started.
Adjustment ranges for RF parameters, as listed in Table 6-14.
To ensure normal operation of the feature, you need to set the cell-level common
parameters before starting the task.
Optimization policy parameters, as listed in Table 6-15. The parameters include control
parameters for optimization tasks, parameters for identifying problematic cells, parameters
for generating optimization advice, and parameters for rollback evaluation.
Basic parameters for optimization tasks, as listed in Table 6-16.
Table 6-12 UMTS engineering parameters

Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
RNC ID*
int
0 - 65535
Yes
CELL NAME
string
The following
feature is
mandatory:
UMTS ANR
CELL ID*
Issue 01 (2015-02-14)
int
0 - 65535

Yes
68
SONMaster
Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
MCC*
string
String Length: 3
Yes
MNC*
string
Yes
LONGITUDE*
float
-180.0 - 180.0
Yes
LATITUDE*
float
-90.0 - 90.0
Yes
AZIMUTH*
float
0.0 - 360.0
Yes
BEAM WIDTH
float
0.0 - 360.0
No
ANTENNA
HEIGHT
float
0.0 - 65535.0
The following
feature is
mandatory:
UMTS CCO
LAC
int
0 - 65535
The following
feature is
mandatory:
UMTS ANR
RAC
int
0 - 65535
The following
feature is
mandatory:
UMTS ANR
SAC
int
0 - 65535
No
BAND No.
enumeration

BANDINDNOTUSED
The following
features are
mandatory:
UMTS ANR
UL UARFCN
int
0 - 65535
No
DL UARFCN
int
0 - 65535
The following
features are
mandatory:
UMTS ANR
UMTS CCO
Issue 01 (2015-02-14)

69
SONMaster
Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
SCRAMBLING
CODE
int
0 - 511
The following
features are
mandatory:
UMTS ANR
OUTDOOR
enumeration
Yes, No
Default value: Yes
The following
feature is
mandatory:
UMTS CCO
DIRECTIONAL
enumeration
Yes, No
No
Default value: Yes

HIGHWAY
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
TUNNEL
COVERAGE
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
SUPERDISTANCE
COVERAGE
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
CONTAIN
REDUNDANT
RRU
enumeration
Yes, No
Default value: No
The following
feature is
mandatory:
UMTS CCO
APPLICATION
SCENARIO
enumeration
DenseUrban, Urban,
SubUrban, Rural,
HighSppedRailway, Edge,
HighBaseStation, Other
Default value: Urban
Issue 01 (2015-02-14)
The following
feature is
mandatory:
Vendor*
enumeration
Alcatel, Ericsson, Huawei,

Motorola, Nokia&Siemens,
Nortel, ZTE, NSN
Yes
REMARKS
string
No

70
SONMaster
Parameter
Name
Parameter Type
Value Range
Mandatory or
Not
ANTENNA
GAIN
float
0.0 - 65535.0
No
Mechanical Tilt
Angle
float
-90.0 - 90.0
The following
feature is
mandatory:
UMTS CCO
E-Tilt Angle
float
-90.0 - 90.0
The following
feature is
mandatory when
this parameter is
not configured in
the configuration
data: UMTS
COO.
RNC NAME
string
No
Cluster
string
No
Table 6-13 Optimization zones and optimization object parameters

Parameter Name
Zone Name
This parameter specifies the optimization zone name.
Remarks
This parameter specifies the information of the optimization zone.
Vendor
This parameter specifies the vendor types of the optimization objects.

l If this parameter is set to Huawei, the optimization objects are all
the Huawei cells managed by the SONMaster.
l If this parameter is set to Ericsson, the optimization objects are
all the Ericsson cells managed by the SONMaster.
l If this parameter is set to NSN, the optimization objects are all the
NSN cells managed by the SONMaster.
RAT
This parameter specified the type of the cells to be optimized. You

are advised to set this parameter when the optimization objects are
cells.
l If this parameter is set to GSM, the cells to be optimized are GSM
cells.
l If this parameter is set to UMTS, the cells to be optimized are
UMTS cells.
l If this parameter is set to LTE, the cells to be optimized are LTE
cells.
Issue 01 (2015-02-14)

71
SONMaster
Parameter Name
Cell List
Available Objects and Selected Objects are displayed in navigation

trees. You can select cells to be optimized by using any of the
following methods: navigation tree, template import, and GIS
window.
Table 6-14 Adjustable RF parameters for problematic areas

Parameter
Name
Value Range
Description
CGI
UMTS CGI format: Mcc-MncRNCId-CellId

This parameter maintains the list of
all cells on the network of
customers.
Is Active
Enumerated values:
l Yes (default value)
l no
You can adjust parameters only for

active cells. None of the parameters
for inactive cells can be adjusted.
Parameters for adjusting the pilot power

Is Lock
Enumerated values:
l yes
l no (default value)
Pilot Power
Proportion_Min
Pilot Power
Proportion_Ma
x
Default pilot power adjustment

range: 0 to 20
Default value of Pilot Power
Proportion_Min: 5
Default value of Pilot Power
Proportion_Max: 10
This parameter specifies whether

cell pilot power adjustment is
allowed.
minimum proportion of the pilot
power in the maximum power.
maximum proportion of the pilot
power in the maximum power.
Unit: %
Parameters for adjusting the electrical downtilt angle
Is Lock
Enumerated values:
l yes
E-Tilt_Max
E-Tilt_Min
Adjustment of the electrical

downtilt angle.
l Default maximum value: 8
l Default minimum value: 0
l Unit: 0.1 Degree
Issue 01 (2015-02-14)
This parameter determines whether

to adjust the electrical downtilt
angle. This parameter is set to yes if
the network does not support
adjustment of the electrical downtilt
angle or users do not want to.
If the adjustment is supported, the
maximum and minimum absolute
values that can be adjusted for the
electrical downtilt angle.

72
SONMaster
Parameter
Name
Value Range
Description
Parameters for adjusting the mechanical downtilt angle

Is Lock
Enumerated values:
l yes
M-Tilt_Max
M-Tilt_Min
Adjustment of the mechanical

downtilt angle
l Default maximum value: 8
l Default minimum value: 0

to adjust the mechanical downtilt
angle of a cell. If users do not want
to, this parameter is set to yes.
If the adjustment is supported, the
maximum and minimum absolute
values that can be adjusted for the
mechanical downtilt angle.
l Unit: Degree
Adjustable handover parameter of cells
Is Lock
Enumerated values:
l yes
This parameter specifies whether

cell handover parameter adjustment
is allowed.
Table 6-15 Optimization policy parameters for UMTS DL Coverage Optimization

Parameter
Name
Value Range
Description
Optimization
target
Value range (single choice):

optimization target of a CCO task.
You can select DL Coverage
Optimization or DL Capacity
Optimization. Select DL Coverage
Optimization for this task.
l Coverage
l Load balancing
Default value: Coverage
Frequency list
Value range: 0 to 16383

Default value: none
After you select an optimization

area, the SONMaster lists all
ARFCNs involved in the
optimization area. You must select
at least one ARFCN. All ARFCNs
are selected by default.
Cells whose ARFCNs are not
selected will not be involved in the
CCO task.
Issue 01 (2015-02-14)

73
SONMaster
Parameter
Name
Value Range
Description
Optimization
mode
Enumerated values (You can select

multiple values):

optimization mode.
l Parameter check
l Handover adjustment
l Feature optimization
l Power optimization
l Antenna optimization
Manually
adjusting
problematic
cells
Value range:
l Disallow
l Allow
Default value: Allow
Evaluation
monitor period
Default value: 3
Unit: day
Issue 01 (2015-02-14)
If this parameter is set to Disallow,

no manual adjustment is allowed
and the next step is automatically
performed when the SONMaster
detects problematic cells through
KPI monitoring. If this parameter is
set to Allow, you can perform
manual adjustment within 24 hours
after the SONMaster detects
problem cells through KPI
monitoring. Then, the next step is
performed.
Within the evaluation monitoring
period, the SONMaster collects
performance and MR data. When
the monitoring is complete, the
SONMaster calculates MR
counters and KPIs, identifies
problematic cells of the coverage
category within the period, and
evaluates the optimization gains in
the previous period.

74
SONMaster
Parameter
Name
Value Range
Description
Evaluation
monitor start
mode
Value range:
Startup mode of the evaluation

monitoring period
l INSTANT
l SCHEDULE
Default value: INSTANT
l If the parameter is set to

SCHEDULE, the start time of
each optimization period is the
same. For example, if the start
time is set to 08:00, after the
rollback of the previous
optimization period is
evaluated, the SONMaster
needs to wait until the next 08:00
to start another optimization.
l If the parameter is set to
INSTANT, the next
optimization period is started
immediately after the rollback
of the previous period is
complete. In this case, the start
time of each optimization period
is different.
Evaluation
monitor
schedule time
Value format: HH:MM:SS
Rollback
monitor busyhour period
Value range: 1 to 8
Default value: 08:00:00
Default value: 3
Unit: hour
If Evaluation Monitoring Start

Mode is set to SCHEDULE, you
can set the start time for the
scheduled evaluation monitoring.
Ensure the number of busy hour
segments during the rollback
monitoring period. The busy hour is
determined by Specified network
busy hours. The SONMaster
continuously collects and monitors
performance data from the time
when the optimization advice is
delivered to the end of the first N
busy hours. If the rollback
conditions are met, the SONMaster
performs the rollback. The counters
for rollback evaluation must be the
same as those at the time segment of
the previous day.
The value of Rollback judgment
period count must not be greater
than that of Rollback monitor
busy-hour period.
Issue 01 (2015-02-14)

75
SONMaster
Parameter
Name
Value Range
Description
Rollback
judgment period
count
Value range: 1 to 8
During the rollback monitoring

period, if KPIs meet rollback
conditions within the continuous
Rollback judgment period count,
the SONMaster perform the
rollback for the cell group.
Default value: 2
Unit: integer
The value of Rollback judgment

period count must not be greater
than that of Rollback monitor
busy-hour period.
Specified
network busy
hours
Value range: 00:00 to 24:00

Default value: 08:00 to 12:00 and
18:00 to 21:00
This parameter specifies the busy

hours for rollback monitoring and
for load-related KPIs.
The start time and end time of the
specified network busy hour must
be exactly divided by the number of
hours within this time range.
Good RSCP
threshold
Value range: -110, -105, -100, -95,

-90, -85, -80, -70, -60. Unit: dBm
Default value: -95
Poor Ec/No
threshold
Value range: -23, -18, -16, -14, -12,

-10, -8, -6. Unit: dB
Default value: -14
An MR data record with weak

coverage refers to an MR data
record in which the RSCP of the
primary serving cell is less than the
value of Good RSCP threshold.
An MR data record with
interference refers to an MR data
record that meets the following
requirements:
l The RSCP of the primary
serving cell is greater than or
equal to the value of Good
RSCP threshold.
l The Ec/No of the primary
serving cell is less than the value
of Poor Ec/No threshold.
The value of Poor Ec/No
threshold must not be greater than
that of Good Ec/No threshold.
Pilot pollution
RSCP
difference
threshold
Issue 01 (2015-02-14)
Value range: -10 to 60. Unit: dB

Default value: 5
Threshold for determining MRs of

the pilot pollution category.

76
SONMaster
Parameter
Name
Value Range
Description
Good Ec/No
threshold
Value range: -24 to 60. Unit: dB

Default value: -12
The value of Poor Ec/No

threshold must not be greater than
that of Good Ec/No threshold.
Issue 01 (2015-02-14)
Pilot pollution
overlapped
coverage cell
count threshold
DL weak
coverage MR
proportion
threshold
Value range: 0% to 100%
DL interference
MR proportion
threshold
DL poor MR
proportion
threshold
Power
congestion rate
threshold
Min.proportion
of adjusted pilot
power to
max.Tx power
Max.proportion
of adjusted pilot
power to
max.Tx power
RRC setup
success rate
threshold
Default value: 4
Default value: 10%
Default value: 10%
Default value: 10%
Default value: 1
Unit: %
Default value: 5%
Default value: 10%
Default value: 99%

Floating number

This parameter identifies

problematic cells of the weak
downlink coverage category.
problematic cells of the downlink
interference category.
problematic cells of the downlink
poor quality category.
the power congestion rate of a target
cell is over large. If the RRC power
congestion rate or RAB power
congestion rate of a cell is greater
than this threshold, the cell will not
be used as the target cell for
handover parameter optimization or
the performance may deteriorate
after handover parameter
optimization.
This parameter controls the range
for adjusting the pilot power.
This parameter controls the range

for adjusting the pilot power.
This parameter is used for KPI

monitoring to identify cells with
abnormal KPIs.

77
SONMaster
Parameter
Name
Value Range
Description
RAB setup
success rate
threshold

abnormal KPIs.
RAB PS service
drop rate
threshold
RAB CS service
drop rate
threshold
Default value: 99%

Floating number

abnormal KPIs.
Default value: 0.8%

Floating number

abnormal KPIs.
Default value: 3%
Floating number
Table 6-16 Basic Parameters for Optimization Tasks

Name
Meaning
Value
Description
Service
name
This parameter uniquely

identifies a task.
The value is a
character
string.

Service
type

type of an SON feature.
Huawei:

l UMTS
CCO-RRM
Based
l UMTS
CCO-RF
Based
You can select only one

option.
Ericsson:
l DL
Capacity
l DL
Coverage
l UMTS
CCO-RRM
Based
(Capacity)
Issue 01 (2015-02-14)

78
SONMaster
Name
Meaning
Value
Description
Start mode

method of starting an
optimization task.
Enumerated
values:
l Manual
(default
value)
l Automatic
l Schedule
Start time

start after Start Mode is set to
Schedule.
Stop mode

method of stopping an
optimization task.
Enumerated
values:
l Manual
(default
value)
l Schedule
l Repeat
interval
Stop time

stop after Stop Mode is set to
Schedule.
Repeat
interval

number of execution periods
after which an optimization task
will automatically stop when
Stop Mode is set to Repeat
interval. The value of Repeat
interval determines the number
of execution periods within
which the optimization task is
running.
Value range:
1~1000

method of executing
optimization advice, which
supports open-loop and closedloop.
Enumerated
values:
Advice
execution
Default value:
1
l Manual
(default
value)
l Automatic
l Schedule
Issue 01 (2015-02-14)

79
SONMaster
Name
Meaning
Value
Description
Execution
time
This parameter specifies a time

point within 24 hours. The
SONMaster executes
optimization advice at the time
point every day.
This parameter specifies

a time point at which the
SONMaster
automatically executes
optimization advice
every day when Advice
Execution is set to
Schedule.

mode for rolling back
optimization advice. The
parameter setting takes effect on
both quick evaluation and
coverage and capacity
evaluation.
Enumerated
values:
This parameter is
dedicated to CCO tasks
and is involved in both
coverage optimization
and load balancing
scenarios.
Advice
rollback
l Manual
(default
value)
l Automatic
l Schedule
Rollback
time

when optimization advice is
rolled back when Advice
Rollback is set to Schedule.
Format:
HH:MM:SS
This parameter is
dedicated to CCO tasks.
Default value:
03:00:00
Process
Figure 6-2 shows the process of UMTS CCO. Table 6-17 describes the process.
Issue 01 (2015-02-14)

80
SONMaster
Figure 6-2 Process of UMTS CCO
Table 6-17 Process description
Issue 01 (2015-02-14)
Procedure
Description
Log in to the
SONMaster
For detailed operations, see Logging In to the SONMaster in

Getting Started.
(Optional) Connect to
the OSS
For detailed operations, see (Optional) Connecting to the OSS in

Getting Started.
Prepare basic data.
For detailed operations, see Preparing Basic Data in Getting

Started.

81
SONMaster
Procedure
Description
(Optional) Set
parameters for UMTS
CCO
For detailed operations, see (Optional) Setting Parameters for

UMTS CCO under the UMTS CCO node in CCO Management
User Guide.
Create and start a UMTS

CCO task
For detailed operations, see Creating and Starting a UMTS CCO

Task under the UMTS CCO node in CCO Management User
Guide.
Executing a UMTS
CCO Task
For detailed operations, see Executing a UMTS CCO Task under

the UMTS CCO node in CCO Management User Guide.
(Optional) Check the

information about
exceptions during
UMTS CCO
optimization
For detailed operations, see (Optional) Checking the Information

About Exceptions During UMTS CCO Optimization under the
(Optional) Evaluate the

optimaization effect of
UMTS CCO
optimization
For detailed operations, see (Optional) Evaluating the

Optimaization Effect of UMTS CCO Optimization under the
Activation Observation
After you activate the feature, you can perform activation observation using the methods in
Table 6-18:
Table 6-18 Observation methods
Issue 01 (2015-02-14)
Method
Description
Reference
Method 1
Check the task running status on the

task management GUI of the
SONMaster.
See Window for CCO Task

Management in 2.4
Introduction to the Main
Window.
Method 2
Check the generated logs after the

feature is activated.
See the following section in

SONMaster System Management
User Guide : Log Management >
Querying SON Logs.
Method 3
Check the identified problematic cells

on the problematic area construction
GUI.
See Wizards for Optimization

Tasks in 2.4 Introduction to the
Main Window.

82
SONMaster
Method
Description
Reference
Method 4
Check the CCO optimization advice on

the optimization advice management
GUI. You are advised to do so after a
feature running period.
See the following section in CCO

Management User Guide: UMTS
CCO > Executing a UMTS CCO
Task - RRM Based (Coverage)
(Huawei).
Feature Deactivation
To deactivate a feature, you can stop the running optimization task of this feature:
1.
Select the running optimization task.
2.
Click
to stop the task.
6.2.4 Monitoring
When downlink coverage problems exist on the network, activating UMTS DL Coverage
Optimization RRM Based will reduce the percentages of MRs with downlink weak coverage
and MRs with downlink interference, and improve accessibility and retainability KPIs on the
network if network conditions do not change. If KPIs deteriorate after the optimization advice
is delivered and executed, check whether KPI deterioration is caused by the optimization. If so,
use the optimization advice rollback function to restore the previous network parameters. You
can use the rollback function to restore the network parameters to any optimization period.
You can check the optimization effect using one of the following methods:
l
Perform optimization effect evaluation using the KPI evaluation function.

For detailed operations, see (Optional) Evaluating the Optimization Effect of UMTS CCO
Optimization under the UMTS CCO node in CCO Management User Guide.
Evaluate optimization effect based on rollback and gain evaluation KPIs.

KPIs for the problematic cells and problematic cell groups that have valid optimization
advice before and after optimization. For definitions of the KPIs, see Table 8-1.
Accessibility KPIs: RRC Setup Success Rate and RAB Setup Success Rate
Retainability KPIs: CS RAB Call Drop Rate and PS RAB Call Drop Rate
Traffic KPIs: CS Traffic, HSDPA Throughput, and HSDPA Traffic
Evaluate optimization effect based on gain evaluation KPIs.

Signal level and quality CDF curves before and after optimization: each of which refers to
an MR percentage CDF curve. Figure 6-3 shows an example.
Issue 01 (2015-02-14)

83
SONMaster
Figure 6-3 CDF curve of RSCP
NOTE
You are advised to pay attention to KPI changes before the optimization. The optimization should not be
performed before, after, or during holidays or major events because they will cause KPI fluctuation.
6.2.5 Parameter Optimization

This section describes the optimization parameters. After UMTS DL Coverage Optimization
RRM Based is activated, you can properly adjust these parameters in Table 6-19 to achieve
better optimization results.
Table 6-19 Parameter optimization
Parameter Name
Setting Notes
Good RSCP threshold
This parameter specifies the weak coverage RSCP threshold and

is used to identify weak coverage problems.
l A larger value of this parameter indicates that more weak
coverage problems may be identified based on the RSCP.
l A smaller value of this parameter indicates that less weak
coverage problems may be identified based on the RSCP.
Issue 01 (2015-02-14)

84
SONMaster
Parameter Name
Setting Notes
Poor Ec/No threshold
This parameter specifies the poor EC/NO threshold and is used to

identify MRs with poor quality.
l A larger value of this parameter indicates that more poor quality
problems may be identified based on the EC/NO.
l A smaller value of this parameter indicates that less poor
quality problems may be identified based on the EC/NO.
DL poor MR proportion
threshold
This parameter specifies the threshold for the percentage of MRs

with poor quality and is used to identify poor quality problems.
l A larger value of this parameter indicates a lower probability
that poor quality problems are identified and a higher
probability that the optimization advice is effective.
l A smaller value of this parameter indicates a higher probability
that poor quality problems are identified and a lower
DL weak coverage MR
proportion threshold

with weak coverage and is used to identify weak coverage
problems and check whether the optimization advice is effective.
that weak coverage problems are identified and a higher
that weak coverage problems are identified and a lower
DL interference MR
proportion threshold

with interference and is used to identify interference problems and
check whether the optimization advice is effective.
that weak coverage problems are identified and a higher
that weak coverage problems are identified and a lower
Pilot pollution RSCP

difference threshold
This parameter specifies the pilot pollution RSCP difference

threshold and is used to identify pilot pollution problems.
l A larger value of this parameter indicates that more pilot
pollution problems may be identified based on the RSCP
difference.
l A smaller value of this parameter indicates that less pilot
pollution problems may be identified based on the RSCP
difference.
Issue 01 (2015-02-14)

85
SONMaster
Parameter Name
Setting Notes
Pilot pollution
overlapped coverage
cell count threshold
This parameter specifies the threshold for the number of cells with
pilot pollution problems and is used to identify pilot pollution
problems.
l A larger value of this parameter indicates that less pilot
pollution problems may be identified based on the RSCP.
l A smaller value of this parameter indicates that more pilot
pollution problems may be identified based on the RSCP.
Issue 01 (2015-02-14)

86
SONMaster
Feature Specifications
Table 7-1 describes feature specifications.

Table 7-1 Feature specifications
Issue 01 (2015-02-14)
Task
Type
Task
Specifica
tion Maximu
m
Number
of Tasks
Task
Specifica
tion Number
of
Optimiza
tion
Objects
Availabl
e for a
Single
Task
Historica
l
Optimiza
tion
View
Specifica
tion Historica
l
Optimiza
tion
Storage
Period
Historica
l
Optimiza
tion
View
Specifica
tion Historica
l
Optimiza
tion
Storage
Duration
(Day)
Historica
l KPI
View
Specifica
tion Historica
l KPI
Storage
Duration
(Day)
Optimiza
tion
Rollback
Specifica
tion Allowabl
e Time to
Be Rolled
Back to
UMTS
DL
Capacity
Optimizat
ion RRM
Based
10
20000
l LongPeriod
Load
Balanc
ing: 30
90
Last
optimized
l Traffic
Burst
Load
Balanc
ing: 3

87
SONMaster
Task
Type
Task
Specifica
tion Maximu
m
Number
of Tasks
Task
Specifica
tion Number
of
Optimiza
tion
Objects
Availabl
e for a
Single
Task
Historica
l
Optimiza
tion
View
Specifica
tion Historica
l
Optimiza
tion
Storage
Period
Historica
l
Optimiza
tion
View
Specifica
tion Historica
l
Optimiza
tion
Storage
Duration
(Day)
Historica
l KPI
View
Specifica
tion Historica
l KPI
Storage
Duration
(Day)
Optimiza
tion
Rollback
Specifica
tion Allowabl
e Time to
Be Rolled
Back to
UMTS
DL
Coverage
Optimizat
ion RRM
Based
10
20000
30
90
Last
optimized
NOTE
For historical optimization view specifications, both the settings in Historical Optimization View
Specification - Historical Optimization Storage Period and Historical Optimization View
Specification - Historical Optimization Storage Duration (Day) must be met.
Issue 01 (2015-02-14)

88
SONMaster
8 References
References
Table 8-1 describes evaluation granularities, evaluation KPIs, and KPI generation rules related
to optimization effect evaluation of UMTS CCO RRM Based.
Table 8-1 Optimization effect evaluation counters
Task Type
Evaluation
Granularit
y
Evaluation Counter
Counter Generation Rule
UMTS DL
Capacity
Optimizatio
n RRM
Based
Neighboring
cell
Soft HO Success Rate

Between Neighboring Cells
(%)
(VS.SHO.SuccASU.NCell) /
(VS.SHO.AttASU.NCell)
Hard HO Success Rate

(%)
(VS.HHO.SuccOut.NCell) /
(VS.HHO.AttOut.NCell)
Cell DL Power Load

Proportion(%)
(10^( VS.MeanTCP
(67199618) /10) / (10^
(MaxTxPower/10))
Cell RRC Setup Success Rate

(%)
RRC.SuccConnEstab.sum/
VS.RRC.AttConnEstab.Sum
Cell
Issue 01 (2015-02-14)

89
SONMaster
Task Type
Evaluation
Granularit
y
8 References
Evaluation Counter
Cell RAB Setup Success

Rate(%)
(VS.RAB.SuccEstabCS.Str
+VS.RAB.SuccEstabCS.Co
nv
+VS.RAB.SuccEstabPS.Str
+VS.RAB.SuccEstabPS.Int
+VS.RAB.SuccEstabPS.Co
nv
+VS.RAB.SuccEstabPS.Bk
g)
/(VS.RAB.AttEstabCS.Str
+VS.RAB.AttEstabCS.Conv
+VS.RAB.AttEstabPS.Str
+VS.RAB.AttEstabPS.Int
+VS.RAB.AttEstabPS.Conv
+VS.RAB.AttEstabPS.Bkg)
Cell CS RAB Service Drop

Rate(%)
(VS.RAB.AbnormRel.CS)/
(VS.RAB.AbnormRel.CS
+VS.RAB.NormRel.CS)
Cell PS RAB Service Drop

Rate(%)
(VS.RAB.AbnormRel.PSVS.RAB.AbnormRel.PS.PC
H
VS.RAB.AbnormRel.PS.D2
PVS.RAB.AbnormRel.PS.F2
P)
/( VS.RAB.AbnormRel.PS
+VS.RAB.NormRel.PS
VS.RAB.AbnormRel.PS.PC
HVS.RAB.NormRel.PS.PCH
+VS.DCCC.D2P.Succ
+VS.DCCC.Succ.F2P)
Issue 01 (2015-02-14)
RRC Setup Failure Count

due to Cell DL Power
Resource Congestion
VS.RRC.Rej.DLPower.Con
g
RRC Setup Failure

Proportion due to Cell DL
Power Resource Congestion
(%)
VS.RRC.Rej.DLPower.Con
g/

90
SONMaster
Task Type
Evaluation
Granularit
y
8 References
Evaluation Counter
RAB Setup Failure Count

due to Cell DL Power
Resource Congestion
VS.RAB.FailEstabCS.DLPo
wer.Cong+
VS.RAB.FailEstabPS.DLPo
wer.Cong
RAB Setup Failure

Proportion due to Cell DL
Power Resource Congestion
(%)
(VS.RAB.FailEstabCS.DLP
ower.Cong
+VS.RAB.FailEstabPS.DLP
ower.Cong)
/
(VS.RAB.AttEstabCS.Conv
+VS.RAB.AttEstabCS.Str
+
VS.RAB.AttEstabPS.Conv
+ VS.RAB.AttEstabPS.Str
+ VS.RAB.AttEstabPS.Int +
VS.RAB.AttEstabPS.Bkg)

due to Cell UL CE
Congestion
VS.RRC.Rej.ULCE.Cong
RRC Setup Failure

Proportion due to Cell UL CE
Congestion(%)
VS.RRC.Rej.ULCE.Cong/

due to Cell UL CE
Congestion
VS.RAB.FailEstabCS.ULC
E.Cong
+VS.RAB.FailEstabPs.ULC
E.Cong
RAB Setup Failure

Proportion due to Cell UL CE
Congestion(%)
(VS.RAB.FailEstabPS.ULC
E.Cong
+VS.RAB.FailEstabCS.UL
CE.Cong)
/(VS.RAB.AttEstabPS.Conv
+VS.RAB.AttEstabPS.Bkg
+VS.RAB.AttEstabCS.Str)

due to Cell DL CE
Congestion
Issue 01 (2015-02-14)

VS.RRC.Rej.DLCE.Cong
91
SONMaster
Task Type
Evaluation
Granularit
y
8 References
Evaluation Counter
RRC Setup Failure

Proportion due to Cell DL CE
Congestion(%)
VS.RRC.Rej.DLCE.Cong/

due to Cell DL CE
Congestion
VS.RAB.FailEstabCS.DLC
E.Cong
+VS.RAB.FailEstabPs.DLC
E.Cong
RAB Setup Failure

Proportion due to Cell DL CE
Congestion(%)
(VS.RAB.FailEstabPS.DLC
E.Cong
+VS.RAB.FailEstabCS.DL
CE.Cong)
/(VS.RAB.AttEstabPS.Conv
+VS.RAB.AttEstabPS.Bkg
+VS.RAB.AttEstabCS.Str)
Voice Traffic(Erl)
VS.AMR.Erlang.BestCell
+VS.VP.Erlang.BestCel
HSDPA DL Traffic Volume

(Bytes)
VS.HSDPA.MeanChThroug
hput.TotalBytes
Cell Soft HO Success Rate

(%)
(VS.SHO.SuccRLAdd+
VS.SHO.SuccRLDel)
/ (VS.SHO.AttRLAdd
+VS.SHO.AttRLDel)
UMTS DL
Coverage
Optimizatio
n RRM
Based
Issue 01 (2015-02-14)
Cell Inter-Frequency Hard

HO Success Rate(%)
(VS.HHO.SuccInterFreqOut/VS.HHO.AttInterFreqOut)
Neighboring
cell
Soft HO Success Rate

(%)
(VS.SHO.SuccASU.NCell) /
(VS.SHO.AttASU.NCell)
Cell
Cell DL Power Load

Proportion(%)
(10^( VS.MeanTCP
(67199618) /10) / (10^
(MaxTxPower/10))
Cell RRC Setup Success Rate

(%)
RRC.SuccConnEstab.sum/

92
SONMaster
Task Type
Evaluation
Granularit
y
8 References
Evaluation Counter
Cell RAB Setup Success

Rate(%)
(VS.RAB.SuccEstabCS.Str
+VS.RAB.SuccEstabCS.Co
nv
+VS.RAB.SuccEstabPS.Str
+VS.RAB.SuccEstabPS.Int
+VS.RAB.SuccEstabPS.Co
nv
+VS.RAB.SuccEstabPS.Bk
g)
/(VS.RAB.AttEstabCS.Str
+VS.RAB.AttEstabPS.Conv
+VS.RAB.AttEstabPS.Bkg)
Cell CS RAB Service Drop

Rate(%)
(VS.RAB.AbnormRel.CS)/
(VS.RAB.AbnormRel.CS
+VS.RAB.NormRel.CS)
Cell PS RAB Service Drop

Rate(%)
(VS.RAB.AbnormRel.PSVS.RAB.AbnormRel.PS.PC
H
VS.RAB.AbnormRel.PS.D2
PVS.RAB.AbnormRel.PS.F2
P)
/( VS.RAB.AbnormRel.PS
+VS.RAB.NormRel.PS
VS.RAB.AbnormRel.PS.PC
HVS.RAB.NormRel.PS.PCH
+VS.DCCC.D2P.Succ
+VS.DCCC.Succ.F2P)
Issue 01 (2015-02-14)
Voice Traffic(Erl)
VS.AMR.Erlang.BestCell
+VS.VP.Erlang.BestCel
HSDPA Traffic(bytes)
VS.HSDPA.MeanChThroug
hput.TotalBytes
HSDPA Throughput(kbps)
VS.HSDPA.MeanChThroughput

93
SONMaster
Task Type
Evaluation
Granularit
y
8 References
Evaluation Counter
RRC Rej Power Cong Rate
(VS.RRC.Rej.DLPower.Con
g
+VS.RRC.Rej.ULPower.Co
ng) /
RAB FailEstCs Power Cong

Rate
(VS.RAB.FailEstabCS.DLP
ower.Cong
+VS.RAB.FailEstabCS.ULP
ower.Cong +
VS.RAB.FailEstabPS.DLPo
wer.Cong
+VS.RAB.FailEstabPS.ULP
ower.Cong) /
(VS.RAB.AttEstabCS.Conv
+VS.RAB.AttEstabCS.Str+
VS.RAB.AttEstabPS.Conv
+ VS.RAB.AttEstabPS.Str +
VS.RAB.AttEstabPS.Int +
VS.RAB.AttEstabPS.Bkg)
NOTE
For details about raw counters and counter IDs related to counter generation rules, see BSC6900 UMTS
Performance Counter Reference and BSC6910 UMTS Performance Counter Reference.
Issue 01 (2015-02-14)

94

Umts Cco Feature Description - RRM Based (v100r015c00 - 01) (PDF) - en

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Umts Cco Feature Description - RRM Based (v100r015c00 - 01) (PDF) - en

Caricato da

Copyright:

Formati disponibili

SONMaster

UMTS CCO Feature Description RRM Based

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

Network management engineers

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

Items (keywords or arguments) in brackets [ ] are optional.

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Huawei Proprietary and Confidential

About This Document

Buttons, menus, parameters, tabs, window, and dialog titles

Multi-level menus are in boldface and separated by the ">"

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

This section contains the following contents:

Feature ID and Name

Data Source Analysis

Feature ID and Name

CCO - UMTS DL Capacity Optimization RRM Based

CCO - UMTS DL Coverage Optimization RRM

Huawei Proprietary and Confidential

UMTS DL Coverage Optimization RRM Based: This feature automatically detects

Data Source Analysis

Huawei Proprietary and Confidential

Figure 1-1 Sources of analysis data

Table 1-2 Data sources

The data is obtained from the RNC. It provides configuration

The data is obtained from the SAU of the RNC. It provides

Huawei Proprietary and Confidential

Engineering parameters are manually imported or exported on the

Improved network coverage and capacity optimization efficiency

Reduced network coverage and capacity optimization costs

Improved network performance

Routine coverage and load

l Solves capacity problems on the

Huawei Proprietary and Confidential

As network coverage and load

In VIP areas or cell clusters with

Network load changes continuously

The scenario restrictions of this feature are as follows: