You are on page 1of 27

WCDMA RAN and I-HSPA, Rel.

RU30, Operating
Documentation, Issue 09

Optimizing WCDMA RAN


DN02241406
Issue 10D
Approval Date 2011-11-21

Confidential

Optimizing WCDMA RAN

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2011. All rights reserved

Important Notice on Product Safety


This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the Legal, Safety
and Environmental Information part of this document or documentation set.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit


Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.

Id:0900d805808e1ffd
Confidential

DN02241406
Issue 10D

Optimizing WCDMA RAN

Table of contents
This document has 27 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

DN02241406

Optimizing and expanding WCDMA RAN overview. . . . . . . . . . . . . . . . . 7

Principles of optimizing GSM/WCDMA interworking . . . . . . . . . . . . . . . 13

Operation and Management Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4
4.1
4.2
4.3
4.4

Optimization use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


WCDMA adjacency optimization based on measurements . . . . . . . . . .
Soft handover analysis and optimization . . . . . . . . . . . . . . . . . . . . . . . .
Interference analysis for performance and coverage optimization . . . .
WCDMA capacity optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Id:0900d805808e1ffd
Confidential

16
16
20
22
25

Optimizing WCDMA RAN

List of tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7

Network element software requirements . . . . .


Use case information . . . . . . . . . . . . . . . . . . . .
Network element software requirements . . . . .
Use case information . . . . . . . . . . . . . . . . . . . .
Network element software requirements . . . . .
Use case information . . . . . . . . . . . . . . . . . . . .
Use case information . . . . . . . . . . . . . . . . . . . .

Id:0900d805808e1ffd
Confidential

.......
.......
.......
.......
.......
.......
.......

......
......
......
......
......
......
......

. . . . . . 16
. . . . . . 17
. . . . . . 20
. . . . . . 20
. . . . . . 22
. . . . . . 23
. . . . . . 25

DN02241406

Optimizing WCDMA RAN

Summary of changes

Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Note that the issue numbering system and product naming practice are changing. For
more information, see Guide to WCDMA RAN and I-HSPA operating documentation.
Changes between issues 10C (2011-09-02, RU30) and 10D (2011-11-21, RU30)
WCDMA adjacency optimization based on measurements (4.1)

Version indices have been removed from KPI names.

Soft handover analysis and optimization (4.2)

Version indices have been removed from KPI names.

Interference analysis for performance and coverage optimization (4.3)

Version indices have been removed from KPI names.

WCDMA capacity optimization (4.4)

Step 3 Analyze the radio capacity after completing the measurements. has been
updated with KPIs.
List that contains the elements, interfaces, and the capacity information has been
modified.
Version indices have been removed from KPI names.

Changes between issues 10B (2011-02-24, RU30) and 10C (2011-09-02, RU30)
WCDMA adjacency optimization based on measurements (4.1)

The identification numbers of the following KPIs have been updated: Inter-system
Handover (ISHO) Attempts, ISHO Success Ratio, Inter-frequency Handover (IFHO)
Attempts, IFHO Success Ratio.

Soft handover analysis and optimization (4.2)

The identification number of Soft Handover Overhead [%] for One Cell or whole
RNC KPI has been updated.

WCDMA capacity optimization (4.4)

The identification numbers of the following KPIs have been updated: HSUPA
Resource Accessibility for NRT Traffic, Average NRT HS-DSCH DL Throughput
[Mbps], RAB Success Ratio, NRT Services from Network Perspective [%].

Three KPIs have been added to performance problems of Iub/Iur check in step
Analyze the radio capacity after completing the measurements.

Changes between issues 10-1 (2009-01-30, WCDMA RAN RU10) and 10B (2011-0224, WCDMA RAN RU30)

DN02241406

Id:0900d805808e41bd
Confidential

Summary of changes

Optimizing WCDMA RAN

Principles of optimizing GSM/WCDMA interworking (2)

Load-based handover has been added to WCDMA-GSM in the call active phase list.

Soft handover analysis and optimization (4.2)

The identification numbers of certain RAN counters/KPIs have been updated in the
SHO analysis and optimization list.

Interference analysis for performance and coverage optimization (4.3)

The identification number of Noise floor of the system KPI has been updated.

WCDMA capacity optimization (4.4)

The identification numbers of the following KPIs have been updated: HSDPA
Resource Accessibility for NRT Traffic, HSDPA MAC-d Average net throughput at
BTS, HSDPA MAC-d data volume at BTS [Mbit], Packet Service Setup Success
Ratio (CSSR) [%].

Two KPIs have been added to Check for performance problems of Iub/Iur in step
Analyze the radio capacity after completing the measurements.

Id:0900d805808e41bd
Confidential

DN02241406

Optimizing WCDMA RAN

Optimizing and expanding WCDMA RAN overview

1 Optimizing and expanding WCDMA RAN


overview
Purpose
The main objectives of WCDMA RAN optimization are to enable a better availability of
network services (coverage criteria) and to provide a pre-defined level of service quality
and performance (Quality of Service criteria). Since the WCDMA network is often built
on top of an existing GSM network, it is also essential to ensure seamless mobility within
and between the networks. In mature WCDMA networks, capacity optimization also
becomes very important.
Optimization based on coverage criteria:

Coverage for different data rate services and maximum loading based on traffic forecasts and margins set for load variation. The cell breathing effect allows the cell
size to vary according to the load - the smaller the load, the greater the coverage
and vice versa.
Pilot channel coverage
Soft handover areas and probabilities

The coverage criteria are met by pre-planning as well as continuous measuring, monitoring and fine-tuning of the roll-out and the running network.
Optimization based on performance and capacity criteria:

Total data throughput in a cell


End-user data throughput (application throughput)
Delays
Call setup success rates for different services
Call drop rates
Handover performance

The Quality of Service criteria are verified by checking the KPIs related to them. For
more information on KPIs, see Section Overview of WCDMA RAN key performance indicators in WCDMA RAN Key Performance Indicators.
Optimization based on mobility criteria:

Defining the neighbouring cells for seamless handovers


Handover criteria and performance
Soft handover connections and gains
Service-based and load-based handover optimization

In multi-technology and multi-service networks, mobility-based optimization is challenging. Due to the dynamic nature of the WCDMA (load coverage capacity), it is often
necessary to optimize the network that has been launched based on the actual statistics
instead of on predictions.
Optimization is necessary in several phases of the network evolution. The following different methods are used in the different phases:
1. Pre-launch optimization: the aim is to find the best settings for fulfilling the network
dimensioning and coverage criteria. This is based on predictions and simulations
that have been made before the network is rolled out.
2. Roll-out phase verification: this includes error detection and verification of the initial
performance and coverage through the use of field measurements.

DN02241406

Id:0900d805808e40df
Confidential

Optimizing and expanding WCDMA RAN overview

Optimizing WCDMA RAN

3. Operational phase optimization: this takes place when the roll-out has been completed and verified and when the network is carrying subscriber traffic. In this phase,
the best results are achieved when the optimization is done based on actual network
measurements.
The scope and pace of the pre-launch optimization is determined by the pre-defined
network quality and performance targets and the roll-out scope and schedule. The main
focus of the pre-launch optimization is on troubleshooting, that is:
1. Locating problem areas
2. Prioritizing them
3. Fixing them accordingly
The problem-solving capabilities and processes of the network operator personnel
should also be in the scope of pre-launch optimization.
The aim of the operational phase optimization is to maintain network quality and performance while the complexity of the network environment is multiplied due to additional
features and services, as well as network expansions and increased traffic.
For more information, see the following:

Monitoring use cases overview in Monitoring WCDMA RAN


Introduction in Dimensioning WCDMA RAN documents
Planning WCDMA RAN in Planning WCDMA RAN
Measuring WCDMA RAN in Measuring WCDMA RAN
Overview of WCDMA RAN key performance indicators in WCDMA RAN Key Performance Indicators

For a full list of parameters, see WCDMA Radio Network Configuration Parameters.
Before you start

Change only one parameter at a time so that the impact of the change on the network
can be seen.
Keep track of all of the changes that you make, so that you can restore the network to
the previous configuration if the changes have unwanted effects.
Networks are typically optimized in clusters. Since the frequency is the same, the optimization should be conducted simultaneously for the whole cluster. Cell-based optimization produces the best performance, but in a homogeneous environment or traffic
scenarios it is not significantly better than cluster-based optimization. Cluster-based
optimization, however, takes less effort. Clusters that are geographically isolated, for
example clusters that are separated by a hill, do not cause excessive interference
between each other. In practice, however, the roll-out plan affects the initial selection of
clusters.
In the operational phase optimization, pay particular attention to the following:
Interference and noise control (pilot
pollution)

Id:0900d805808e40df
Confidential

This exists if the received code power is


high but the Ec/Io is very low. Pilot
pollution can be optimized by, for
example, reducing the signal of the
neighbouring cells and by optimizing the
antenna tilts of the neighbouring cells.

DN02241406

Optimizing WCDMA RAN

Optimizing and expanding WCDMA RAN overview

Weak coverage

Low mobile receiver power leads to


degradation of the service quality due to
such things as fading, low Ec/Io or a poor
FER. This can be improved by adding a
site, adding a better antenna, or adjusting
the parameters.

Call functionality problems

For example, call setup fail or call drop.

System performance degradation due to


an unbalanced control channel

For example, capacity degradation.

Mobility management

Handover performance optimization in


particular.

Operational phase optimization is an area-wide tuning of parameters based on longterm statistics and trends. Network statistics are usually used to provide information
about problem spots. If the problem cannot be solved, field measurements can also be
taken into consideration. The aim of this is to identify future problems in traffic areas that
are growing quickly in order to react in time and to be prepared for network expansions.
This is done as follows:

Locate the problem spots geographically and by network elements by monitoring the
network
Prioritize the actions with the help of KPIs
Identify the reasons for the non-performance by analyzing information on the various
statistical indicators and the history of the network

Summary
The following procedure is an example of radio network optimization.
Steps
1

Agree on a master plan.


Decide on the additional services and features that are going to be introduced into the
network and the kind of capacity and service area expansions that are going to be made.
Consider both the short-term and long-term modifications. This clarifies the targets to be
set for the network and gives input for future actions in the plan, for both hardware and
software.

Set KPIs.
After deciding on the long and short-term plans, set targets for the network performance
for capacity, coverage and quality. The KPIs are network-specific and depend, for
example, on the life stage and needs of the network.

Prepare a measurement test plan and tool guidelines.


In optimization, two major measurement types can be defined:
a) Drive/field test measurements
b) Network management measurements (Nokia Siemens Networks NetAct Framework)

DN02241406

Id:0900d805808e40df
Confidential

Optimizing and expanding WCDMA RAN overview

Optimizing WCDMA RAN

Drive test measurements focus on coverage-related and call-related parameters. The


route cannot take more than 1-2 hours to drive, as otherwise the measurement data files
become too large and too complicated to be analyzed. The measurement routes should
include urban, suburban and rural roads, as well as streets and highways. Special areas
should also be included, for example shopping centers and airports. The main focus
should be on area types with the tightest requirements for network performance in terms
of quality, capacity, and coverage, typically urban regions or traffic hot spots with the
densest penetration of mobile subscribers. The measurement time period must be 3-5
working days and must cover busy hours in the network.
Network management measurements focus on quality. Activate the measurements necessary, such as traffic, resource availability, resource access, handover, power control
and quality on the RNC-level. This provides the raw counters that are needed to build
up key performance indicators on the network management and service management
level.
Define the tools that will be used for creating the measurements. Decide how the reports
will be presented, including the format and the template used.
4

Run the drive test measurements.


Drive according to the pre-defined routes and make several two-minute test calls in the
cell cluster area. Store the results in files that are named properly.

g
5

If the network configuration changes, repeat the measurements along the same routes.
It is not otherwise possible to compare the results for evaluating potential performance
improvements.

Run the measurements with NetAct.


Before you start

NetAct statistics are not reliable in the early network life stage because of the small
number of subscribers. There should be typically at least 50 calls during a busy hour per
cell.
Run the measurements on the RNC-level according to the pre-defined list of measurements. The raw counters in the NetAct database can be grouped for each network
element to build up formulae to describe the network in terms of performance indicators.
The performance indicators can be pre-defined or tailored to meet the requirements.

Analyze and process the measurements.


Use post-processing tools to analyze the network performance.

Identify the problems.


Check if the resolution database contains descriptions of any similar problems.

Find solutions.
Before you start
Take the following into account:

10

Id:0900d805808e40df
Confidential

DN02241406

Optimizing WCDMA RAN

Optimizing and expanding WCDMA RAN overview

Missing a site results in non-performance in the area and exclusion zones in acceptance.
Adding a site later affects the neighbouring sites, and a re-optimization is necessary
in the area.

Problems can be solved by either making hardware changes or optimizing parameters.


File all of the optimization actions in the resolution database for future reference.
The following are examples of different solutions:

Adding or deleting radio network objects:


This can be done using the system defaults or a reference site. An additional Base
Transceiver Station (BTS) site can be created with a number of cells or additional
cells to a given site.
When a radio network object is deleted, all objects beneath the object are deleted
as well. For example, if you delete a BTS site then all cells under it are also deleted.
Modifying: adjacencies
Modifying adjacencies is necessary when BTSs are added or deleted from the
network.
RNC split (3G rehosting):
RNC split, also known as 3G rehosting, means re-configuring and expanding the
network by rehosting a BTS site to another RNC or by adding a BTS under an RNC
using an existing site as a reference site. For further information on RNC split/3G
rehosting, see Rehosting WCDMA BTS Sites in NetAct Product Documentation.
a) Configure the BTS under the target RNC
b) Connect the cables from the RNC to the BTS
c) Unlock the additional site under the target RNC
Modifying parameters
Consider whether the modifications affect the services. If so, plan a date and time
for the task and inform the organization about the plans. If an element has to be
locked for modification, it cannot transmit traffic. Plan and prepare for service loss in
order to minimise the unavailability of the services.

Expected outcome
The network should perform within the range expected after optimization.
Verification
Verify the performance against the changes in the network.
Further information
For information on parameters and counters, see:

DN02241406

Overview of WCDMA RAN key performance indicators in WCDMA RAN Key Performance Indicators
WCDMA Radio Network Configuration Parameters
RNC Counters - RNW Part
Introduction to RNC transport and HW part counters in the RN4.0 release in RNC
Counters - Transport and HW Part
Radio network management in Administering Radio Networks
AXC counters

Id:0900d805808e40df
Confidential

11

Optimizing and expanding WCDMA RAN overview

Optimizing WCDMA RAN

More information can also be found in Implementing Parameter Plans for WCDMA,
Creating WCDMA BTS sites and Rehosting WCDMA BTS sites in NetAct Product Documentation.

12

Id:0900d805808e40df
Confidential

DN02241406

Optimizing WCDMA RAN

Principles of optimizing GSM/WCDMA interworking

2 Principles of optimizing GSM/WCDMA interworking


The purpose of optimizing GSM/WCDMA interworking is to enhance the effective usage
of both GSM and WCDMA networks. In doing so, the largest capacity and coverage
possible can be obtained while still maintaining a good Quality of Service.
Optimizing GSM/WCDMA handover means the tuning of the parameters that trigger and
make inter-system handovers between GSM and WCDMA possible. When planning
GSM/WCDMA interworking, cell re-selection and inter-system handover parameters for
GSM and WCDMA were planned. In the optimization phase, these parameters are
tuned to meet the needs of the operator.
Handovers from WCDMA to GSM are performed mainly for coverage reasons, whereas
handovers from GSM to WCDMA are mainly carried out for load and service reasons.
In other words, WCDMA can be used to relieve the GSM overload and GSM to extend
the WCDMA coverage area. GPRS calls are switched to WCDMA whenever possible,
if so configured.
The compressed mode enables an inter-system handover in WCDMA to be performed.
When the UE uses the Uu interface in compressed mode, the contents of the Uu interface frame are compressed to open a time window through which the mobile station can
peek and decode the GSM Broadcast Control Channel (BCCH) information.
From RU10, all dual-mode users in idle mode and call setup phase are kept in the
WCDMA. In the call active phase, the following handovers and cell re-selections can be
performed:

GSM-WCDMA: load-based handover or service-based handover


GPRS-WCDMA: network-controlled cell re-selection
WCDMA-GSM: coverage-based handover or load-based handover
WCDMA-GPRS: coverage-based, network-initiated cell re-selection

For more information on handovers, see Section WCDMA RAN RRM Handover Control
in WCDMA RAN RRM Handover Control .
Coverage-based handover
The following triggers in the RNC can initiate the coverage-based handover:

Inter-system handover or cell re-selection due to Uplink Dedicated Channel (DCH)


quality
Inter-system handover or cell re-selection due to UE Radio Transmitter (UE Tx)
power
Inter-system handover or cell re-selection due to Downlink Dedicated Physical
Channel (DPCH) power
Inter-system handover or cell re-selection due to Common Pilot Channel, Received
Signal Code Power (CPICH RSCP)
Inter-system handover or cell re-selection due to CPICH Ec/No.

For information on the parameters that trigger WCDMA-GSM handovers, see WCDMA
Radio Network Configuration Parameters. For information on the counters for triggering
and the actual performing of each WCDMA-GSM handover, see Section Introduction to
RNC transport and HW part counters in RNC Counters - Transport and HW Part.

DN02241406

Id:0900d8058084c6ba
Confidential

13

Principles of optimizing GSM/WCDMA interworking

Optimizing WCDMA RAN

Load-based handover
Optimize the load-based handover to avoid unnecessary handovers. Take interference
from the surrounding cells into account. Set a certain threshold, for example 80%, for
the load of a GSM cell. In high load situations, speech calls are directed to the WCDMA
to ensure sufficient speech capacity. If the target cell load seems to be high, that is, there
are many rejected handovers, set a penalty timer to prevent inter-system handover for
a certain time.
Service-based handover
Direct data calls to the WCDMA regardless of the GSM load to ensure higher bit rates
for data users and keep speech calls in the GSM, except in high load situations. GPRS
calls are shifted to the WCDMA whenever possible.
The idle mode of GPRS mobile stations can be controlled by packet BCCH. This means
that the GPRS mobile stations can be pushed into WCDMA in idle mode.
The dedicated mode of GPRS mobile stations can be controlled by network-controlled
cell re-selections for load reasons. Inter-system cell re-selections GSM-WCDMA force
a particular mobile station into WCDMA, for example for load reasons or in the case of
an inter-system directed retry.
For more information, see Planning WCDMA RAN.

14

Id:0900d8058084c6ba
Confidential

DN02241406

Optimizing WCDMA RAN

Operation and Management Server

3 Operation and Management Server


Operation and Management Server (OMS) is a Linux OS-based management server
that is connected to the Telecommunication Management Network. OMS is used for
running measurements, storing measurement data and viewing the results.
OMS is used for making local RNC-level changes, one RNC at a time. Use the Nokia
Siemens Networks NetAct Framework for network level changes that are aimed at
several RNCs.
Main functions of OMS
OMS provides the following:

A platform for different network management applications and tools


Redundant and expandible hard disk capacity for storing measurement and configuration data as well as, for example, database backups
Scalable hardware to support additional applications
An easy to use graphical user interface
A mediation functionality between DX/IPA2800 network elements and NetAct that
can be used, for example, to filter and buffer the data collected
Common network element management tools and interfaces for 2G and 3G network
elements
For more information, see Section Administrative interfaces in WCDMA RAN Interfaces.

Performance management in OMS


OMS performs the post-processing of the statistics data required for performance management in the RNC. The radio network measurement timing and handling in the RNC
is located in OMS, which provides measurement timing, starting and stopping, as well
as data handling, storing, and forwarding. For the RNC platform, measurement (ATM
and NE performance) handling is located in the network element and OMS performs
post-processing for the ATM module data.
The prerequisite for OMS performance management is that the RNC implements a performance management function. OMS has the following Graphical User Interfaces
(GUIs):

RNW Measurement Management for managing radio network measurements


RNW Measurement Presentation for creating graphical and textual presentations of
radio network measurement data
NE Measurement Explorer for viewing transmission and NE performance measurement data
NE Threshold Management GUI for managing KPIs and threshold monitoring
parameters in the RNC

More information can be found in the OMS documents in this library. See section How
to find Operation and Management Server (OMS) documentation in Guide to WCDMA
RAN Documentation.

DN02241406

Id:0900d80580640448
Confidential

15

Optimization use cases

Optimizing WCDMA RAN

4 Optimization use cases


4.1

WCDMA adjacency optimization based on measurements

Note that version indices have been removed from KPI names. For proper KPI version
please refer to WCDMA RAN Key Performance Indicators document and view the latest
KPI definition corresponding to appropriate RU release.
Purpose
These instructions are used to perform the use case for WCDMA adjacency optimization
based on measurements. This can be done by using the NetAct tools, for example, Optimizer. For more information, see NetAct Product Documentation.
Perform this use case in the following situations:

When changes have been made in the network and this causes a need for the
neighbour cell list to be optimized.
When the validity of the adjacency optimization plan needs to be checked.

Before you start


Check the network element software requirements for this use case using the table
below.
Network element

Release

RNC

RN4.0

mcRNC

mcRNC1.0

BTS

N/A

AXC

N/A

NetAct

OSS5.0 CD set 1

SGSN

N/A

MSC

N/A

MGW

N/A

UE

N/A

Table 1

Network element software requirements

Summary
Candidates for the neighbor cell list are measured and selected on the basis of set performance criteria. Measurements are carried out by rotating cells that have adjacency
candidates.
There are different types of adjacencies, depending on the type of cells for which the
relationship is defined:

16

Inter-System Adjacency (ADJG): an adjacency from a WCDMA Cell (WCEL) to a


Master BTS
Intra-frequency Adjacency (ADJS): an adjacency between WCELs on the same frequency

Id:0900d805808e41a1
Confidential

DN02241406

Optimizing WCDMA RAN

Optimization use cases

Inter-frequency Adjacency (ADJI): an adjacency between WCELs on different frequencies

The following table gives the basic information on the WCDMA adjacency optimization
based on measurements use case.
ID

RAN_USE_CASE_OPT_001

Use case name

WCDMA adjacency optimization based on


measurements

RAN releases

All RAN releases

Actors

Network planner, operation engineer

Summary

An optimized neighbour cell list is produced based on


measurements from the network.

Reasons for performing the


use case

Changes have been made in the network resulting in


a need to optimize the neighbour cell list
The validity of the adjacency optimization plan needs
to be checked.

Triggers for
service/resource
information used

KPIs based on measurement reports 1A and 1C

Limitations and restrictions

None

Preconditions

The adjacency list to be used has been decided.

Postconditions

A new neighbour cell list has been defined based on the


measurements.

Table 2

Use case information

The KPIs measured for ADJS are:

Soft Handover (SHO) Attempts (M1013C0)


SHO Success Ratio (M1013C1/ M1013C0)
SHO Average Ec/No Difference (M1013C2/ M1013C3)
SHO Average Ec/No (M1013C4/M1013C5)
SHO Average RSCP (M1013C6/M1013C7)

The KPIs measured for ADJG are:

Inter-system Handover (ISHO) Attempts (RNC_298 for RT and RNC_299 for NRT)
ISHO Success Ratio (RNC_300 for RT and RNC_301 for NRT)
Received Signal Strength Indicator (RSSI) (M1015C2/M1015C3)
Base Station Identity Code (BSIC) Verification Time (M1015C4/M1015C5)

The KPIs measured for ADJI are:

Inter-frequency Handover (IFHO) Attempts (RNC_743)


IFHO Success Ratio (RNC_168)
IFHO Average Ec/No (M1014C2/M1014C3)
IFHO Average RSCP (M1014C4/M1014C5)

The KPIs measured for detected set cells are:

DN02241406

Detected set Average Ec/No (M1028C0/M1028C1)


Detected set Average RSCP (M1028C2/M1028C3)

Id:0900d805808e41a1
Confidential

17

Optimization use cases

Optimizing WCDMA RAN

Based on these KPIs, Optimizer calculates a share of handover attempts per adjacency
(SHO Share for ADJS, ISHO Share for ADJG, and IFHO Share for ADJI) and fitness
value to help you to verify the performance of the adjacency.
For information on using Optimizer, see Section Introduction to Optimizer in Optimizer
Principles and Section Overview of the procedure in Optimizing a Network Using Optimizer in NetAct Product Documentation.
Steps
1

Select the scope of the adjacency creation.

Select the adjacency types.


ADJS, ADJG, and ADJI add a reference to the parameter descriptions to be optimized.
It is recommended that you optimize the ADJSs first.

Define the input parameters for the algorithm.


Define the criteria on the basis of which adjacencies are created and/or deleted.

Check BSIC/BCCH or scrambling code/frequency collisions.

Correct any possible collisions.

Define whether to have a fixed number or variable number of candidates for each
cell.

Generate the candidate pool.

Verify the pool generated and decide whether to continue to the rotation.

Start the cell rotation.


Start by defining the time to provision the candidate adjacencies from the pool. Then
define the time to get the performance needed to evaluate the adjacency candidates.

18

10

Check if performance measurements have been retrieved.

11

Repeat steps 9 and 10 until all iterations have been performed.

12

Study the candidate list and modify it if needed.

13

Save the results in a plan.

Id:0900d805808e41a1
Confidential

DN02241406

Optimizing WCDMA RAN

14

Optimization use cases

Verify the results in a table format or on a map.


This can be done, for example, by displaying the relevant KPIs on the top of the cell
dominance area.

DN02241406

Id:0900d805808e41a1
Confidential

19

Optimizing WCDMA RAN

4.2

Soft handover analysis and optimization

Note that version indices have been removed from KPI names. For proper KPI version
please refer to WCDMA RAN Key Performance Indicators document and view the latest
KPI definition corresponding to appropriate RU release.
Purpose
Follow these instructions to perform the use case for Soft handover analysis and optimization. This use case may need to be performed if problematic areas have been found
based on cell-level SHO KPIs. Based on cell-to-cell level KPIs, SHO problems can be
identified, profiled and corrected manually.
Perform this use case using the NetAct tools. For more information, see NetAct Product
Documentation.
Before you start
Check the network element software requirements for this use case using the table
below.
Network element

Release

RNC

All RN releases

mcRNC

mcRNC1.0

BTS

N/A

AXC

N/A

NetAct

All OSS releases

SGSN

N/A

MSC

N/A

MGW

N/A

UE

N/A

Table 3

Network element software requirements

Summary
The following table contains the basic information needed to perform this use case.
ID

RAN_USE_CASE_OPT_002

Use case name

Soft handover analysis and optimization

RAN releases

All RAN releases

Actors

Network planner, operation engineer

Summary

Based on cell-to-cell level KPIs, you can identify,


profile and manually correct SHO problems

Triggers for service/resource


information used

KPIs based on mobile reports

Limitations and restrictions

Measurements are not available

Table 4

20

Use case information

Id:0900d805808e4151
Confidential

DN02241406

Optimizing WCDMA RAN

Reasons for performing the use


case

Problematic areas were found based on cell-level


SHO KPIs.

Preconditions

Reliable traffic data is available.

Postconditions

Initial adjacencies have been created and their


performance can be measured.

Table 4

Use case information (Cont.)

SHO analysis and optimization is based on the following counters/KPIs:

Number of SHO attempts from cell A to cell B, leading to a dropped call (M1013C0
M1013C1)
Total SHO attempts from cell pair (M1013C0)
Average Ec/No difference between cell pair (M1013C2/M1013C3)
Average SHO duration
((M1007C6+M1007C8+M1007C25+M1007C26)/(M1007C15+M1007C32))
Period of time where cell A and cell B are in the active set simultaneously (M1007C1
+ M1007C20)
Average number of SHO attempts from cell pair per call (M1030C0/M802C19)
Total number of radio link failure messages during an SHO attempt
(M1005C180+M1005C181+M1005C182+M1005C183)
Total time in SHO
(SHO duration timers - M1007C8+M1007C26+M1007C6+M1007C25
for HSUPA - M1007C66
for HSDPA - M1007C52+M1007C51 (when, after the SHO, the UE receives the HSDSCH))
Total time a cell is in Active Set Size = 1 (M1007C0+M1007C19 (differentiation for
RT and NRT bearers))
Soft Handover Overhead [%] for One Cell or whole RNC (RNC_192)

Steps

DN02241406

Select the threshold for the cell level cost function for cells that are performing
well and those that are performing badly.

Visualize the cell-level SHO KPIs and identify problematic areas.

Visualize the cell-to-cell KPIs further for adjacencies to the problematic cells.

Modify the CM data necessary to improve the SHO conditions.

Verify and save the changes.

Provision the changes to the network.

Id:0900d805808e4151
Confidential

21

Optimizing WCDMA RAN

4.3

Interference analysis for performance and coverage optimization

Note that version indices have been removed from KPI names. For proper KPI version
please refer to WCDMA RAN Key Performance Indicators document and view the latest
KPI definition corresponding to appropriate RU release.
Purpose
Follow these instructions to perform the use case for Interference analysis for performance and coverage optimization. This use case may need to be performed to find out
about interference-related problems in the NW in both DL and UL direction.
Perform the use case by using the NetAct tools, for example, Optimizer. For more information, see NetAct Product Documentation.
This use case allows you to, for example, show and analyze the average noise level on
the top of the dominance area and the average uplink load on the cell icon. Depending
on whether the cells with high noise are clustered or singular, different conclusions can
be drawn and respective measures can be taken.
To analyze load against throughput (efficiency), show a KPI indicating downlink/uplink
total traffic or throughput on a dominance area and show Average downlink/uplink load
on the cell icon. If a cell has a high load and low traffic, there is a problem with the downlink/uplink.
For interference levels experienced in the cell from the bordering cells that have not
been defined as adjacent cells in the adjacent cell list, analyze the cell level Soft
Handover (SHO) overhead. Show the KPI on a map, and check the adjacent cell list
length. Check the other KPIs for the problem cells.
To check the differences in Cell Common Pilot Channel (CPICH), visualize the CPICH
on the dominance area and the Tx power or SHO Overhead in the cell icon.
Before you start
Check the requirements for network element software for this use case by using the
table below.
Network element

Release

RNC

All RN releases

mcRNC

mcRNC1.0

BTS

N/A

AXC

N/A

NetAct

OSS5.0 CD set 1 / OSS5.0 CD set 2


NOTE: Optimizer WCDMA cell pairlevel interference analysis is available in
OSS5.0 CD set 2.

SGSN

N/A

MSC

N/A

MGW

N/A

Table 5

22

Network element software requirements

Id:0900d805808e4153
Confidential

DN02241406

Optimizing WCDMA RAN

Network element

Release

UE

N/A

Table 5

Network element software requirements (Cont.)

Summary
The following table gives the basic information on the Interference Analysis use case.
ID

RAN_USE_CASE_OPT_003

Use case name

Interference Analysis

RAN releases

All RAN releases

Actors

Network planner, performance engineer

Summary

Cells receiving high interference are identified.

Reasons for performing the use


case

Low performance
Alarms
As a regular check

Triggers for service/resource


information used

Common measurement report


Mobile reports

Limitations and restrictions

None

Preconditions

There are measurements available.

Postconditions

High interfering cells have been identified and


subsequent actions should be taken to reduce
the interference.

Table 6

Use case information

Interference analysis and optimization is based on the following counters/KPIs:

Noise floor of the system [dBm] (RNC_177)


Average Uplink R99 Load [dBm] (RNC_101)
Average R99 Downlink Load [dBm] (RNC_102)
Average HSUPA Uplink Load [dBm] (RNC_1180)
Average HSPA Downlink Load [dBm] (RNC_1181)
Average CPICH Ec/No (WCEL pair) (M1013C4/M1013C5)
CPICH RSCP (WCEL pair) (M1013C6/M1013C7)
Detected set Average Ec/No (M1028C0/M1028C1)
Detected set Average RSCP (M1028C2/M1028C3)
Propagation delay (Timing advance during call setup, propagation delay = time difference between mobile and base station) (M1006C128.. M1006C148)

For information on using Optimizer, see Section Introduction to Optimizer in Optimizer


Principles and Section Overview of the procedure in Optimizing a Network Using Optimizer in NetAct Product Documentation.

DN02241406

Id:0900d805808e4153
Confidential

23

Optimizing WCDMA RAN

Steps
1

Display and analyze the interference-related KPIs on a cell level.


a) Analyze the cell KPIs and the parameters.
Average uplink load against average noise level
If a cell has a low load and high noise, this means that there is a problem with
the uplink conditions.
Downlink total traffic (or throughput) against average downlink load
If a cell has a high load and low traffic, this means that there is a problem with
the downlink conditions.
CPICH Power against Total DL Tx Power (and/or SHOO)
If there are big differences between bordering cells in CPICH Tx Power, find a
way to change the CPICH Tx Power.
b) Select the problematic cells/RNCs.
c) Check the Scrambling Code re-use for any collisions and make corrections if
needed (Optimizer can be used for this).
d) Create a correction plan and provision to the network.

Proceed to the cell pair level analysis using Optimizer.


a) Fetch IM raw data to Optimizer (downlink measurements).
Fetch the Timing Advance KPI also.
b) Create the Interference Matrix.
c) Visualize the interference on a map.
d) Perform the interference root cause analysis.

Identify and remove the man-made interference and/or improve the site installation.
To improve the interference situation, check swapped cables, bad connections, shadowers nearby and so on.

24

Change downtilts for the cells that are interfering a lot.


Change parameters (for example, CPICH Tx Power, Targets for the Max Tx Powers
and offsets).
Create new adjacencies.

Verify and save the changes.

Provision the changes to the network.

Verify the changes after provisioning.

Id:0900d805808e4153
Confidential

DN02241406

Optimizing WCDMA RAN

4.4

WCDMA capacity optimization

Note that version indices have been removed from KPI names. For proper KPI version
please refer to WCDMA RAN Key Performance Indicators document and view the latest
KPI definition corresponding to appropriate RU release.
Purpose
Follow these instructions to perform the use case WCDMA capacity visualization and
analysis. This use case can be performed as part of a regular check or because capacity
problems have been identified.
Perform this use case by using the NetAct tools. For more information, see NetAct
Product Documentation.
Before you start
Check the following:

All of the configuration information needed and the most critical KPIs have been
loaded
KPIs can be retrieved from NetAct (the retrieval is a minimum of 5 days). Configuration Management (CM) parameters have been retrieved from NetAct Configurator.

Summary
The following table provides the basic information needed for this use case.
ID

RAN_USE_CASE_OPT_004

Use case name

WCDMA capacity visualisation and analysis

RAN releases

All RAN releases

Actors

Network planner, operations engineer

Summary

Some elements/interfaces are selected a NetAct


capacity analysis tool is started for the elements/
interfaces with all elements as the scope. A
WCDMA capacity analysis tool view is opened
and the information needed on elements/
interfaces and their performance/capacity is
shown.

Reasons for performing the use


case

Capacity problems have been identified


As a regular check

Triggers for used service/resource


information

Common measurement report


Mobile reports

Limitations and restrictions

None

Preconditions

All of the configuration information needed and


the most critical KPIs are loaded.
KPIs can be retrieved from NetAct (retrieval is a
minimum of 5 days). Configuration Management
(CM) parameters have been retrieved from
NetAct Configurator.

Table 7

DN02241406

Use case information

Id:0900d805808e419f
Confidential

25

Optimizing WCDMA RAN

Postconditions

Table 7

3G network elements/interfaces and their


performance can be seen in the 3G capacity
analysis tool visualisation view.

Use case information (Cont.)

The following list contains the elements and interfaces and the capacity information with
which you can investigate them:

Radio interface: packet data performance and congestion


WCDMA Base Station (WBTS): Base band decoding capacity
Iub: Asynchronous Transfer Mode, Virtual Channel Connection (ATM VCC) and/or
IP based - capacity, performance, and congestions for packet data transmission
RNC: performance for HSDPA and DCH data capacity
Iur: ATM VCC or IP capacity, performance, and congestion
IuPS: ATM VCC or IP capacity, performance, and congestion
3G SGSN performance

Steps
1

Select the scope of the optimization.

Start the measurements for a minimum of five days.


Define the KPI groups needed.

Analyze the radio capacity after completing the measurements.

26

Check the configuration mis-matches of Power Optimization for HSPA:


PtxMaxHSDPA [W], PtxTargetHSDPA [W], PtxOffsetHSDPA [W]
HSDPA Priority [enum]
PrxMaxTargetBTS [dBm], PrxNoise [dBm], TargetNSEDCHToTotalEDCHPR
[dBm]
Check for performance problems of WCDMA Base Station (WBTS) (Wideband Signalling Processor cards for HSDPA).
Active HS-DSCH cell throughput [Mbps] (RNC_722)
Average HSUPA UL Load [dBm] (RNC_1180)
Active HSUPA cell throughput [Mbps] (RNC_1883)
Check for performance problems of WCEL/Uu (High-speed Downlink Packet
Access (HSDPA), DCH data).
Percentage of RTWP in marginal area [%] (RNC_5203)
Marginal Transmitted Carrier Power Time Share DL [%] (RNC_5201)
HSDPA Access Failure Rate due to UL DCH [%] (RNC_661)
Check for performance problems of the RNC, for example, performance for HSDPA,
HSUPA, and DCH data capacity.
HSDPA Resource Accessibility for RT Traffic (RNC_5000)
HSDPA Resource Retainability for RT Traffic (RNC_5010)
HSDPA Resource Accessibility for NRT Traffic (RNC_605)
HSDPA Resource Retainability for NRT Traffic (RNC_609)

Id:0900d805808e419f
Confidential

DN02241406

Optimizing WCDMA RAN

DN02241406

HSUPA Resource Accessibility for NRT Traffic (RNC_913)


Average NRT DCH DL Throughput [Mbps] (RNC_611)
Average NRT HS-DSCH DL Throughput [Mbps] (RNC_5033)
Average Allocated Downlink Dedicated Channel Capacity for Data Calls in Controlling RNC [Mbps] (RNC_165)
Average Allocated Uplink Dedicated Channel Capacity for Data Calls in Controlling RNC [Mbps] (RNC_164)
RAB Success Ratio, NRT Services from Network Perspective [%] (RNC_615)
Packet Service Setup Success Ratio (CSSR) [%] (RNC_576)
Check for performance problems of Iub/Iur, for example, transmission capability.
Iub throughput capacity for PS traffic
Available Iub transport capacity per HSDPA connection
AAl2 connectivity capacity
AAL2 connection reservation success rate [%] (RNC_602)
AAL2 path average reserved bandwidth [%] (RNC_601)
IU-PS data volume per drop (RNC_5051)
IP ROUTE Accessibility for outgoing traffic (RNC_5005)
IP ROUTE Accessibility for incoming IUB traffic (RNC_5031)
reserved IP bandwidth (RNC_1909)

Solve the problem(s).

Save the changes.

Visualize the changes.

Provision the plan.

Verify the changes.

Id:0900d805808e419f
Confidential

27