You are on page 1of 57

UMTS Field-Optimization

Guidelines
RAS06

2/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

DOCUMENT DESCRIPTION
Title and version

UMTS Pre-Optimization Guidelines

Reference

RAS51_RAS06_PreOptim

Target Group

3G Radio

Technology and
SW release

3G/RAS51/RAS06

Service Items

Radio Network Tuning

Service Item
numbers
Author

Dalius Kaskelevicius/Kirsi Tervinen/Pekka Ranta

Date

22/05/2008

Approver

Florian Reymond

CHANGE RECORD
VERSION
1.0

DATE
30/09/2007

EDITED BY
Dalius Kaskelevicius

SECTION/S
ALL

COMMENTS
Version 1

0.1 -0.9

2007

Dalius Kaskelevicius,
SIG, FR

ALL

Working Drafts

1.0

22.05.2008

Kirsi Tervinen,Pekka
Ranta

ALL

Update for RAS06

Copyright Nokia Siemens Networks. This material, including documentation and any related
computer programs, is protected by copyright controlled by Nokia Siemens Networks. All rights
are reserved. Copying, including reproducing, storing, adapting or translating, any or all of this
material requires the prior written consent of Nokia Siemens Networks. This material also
contains confidential information which may not be disclosed to others without the prior written
consent of Nokia Siemens Networks.

TABLE OF CONTENT

3/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

INTRODUCTION AND SCOPE..............................................................................5

RAS06 FEATURE UPDATE...................................................................................5

PRE OPTIMIZATION PROCEDURE......................................................................6


3.1
Flowchart...............................................................................................6
3.2
Overview...............................................................................................6

CONFIGURATION AND PARAMETER CHECK...................................................8


4.1
Tools......................................................................................................8

4.1.1

Procedure.................................................................................................................. 8

4.2

RAS5.1 Upgrade to RAS06 parameter recommendations................9

KPI HEALTH CHECK...........................................................................................12


5.1
Tools....................................................................................................12
5.2
Procedure............................................................................................12
5.2.1
5.2.2
5.2.3
5.2.4

Alarms check........................................................................................................... 12
Counters check for abnormal behaviour..................................................................14
Neighbor Definition.................................................................................................. 19
Cell rank/track list..................................................................................................... 19

5.3

RAS5.1 Upgrade to RAS06 main OSS KPIs to follow......................20

DRIVE TEST TOOLS AND PROCEDURES........................................................22


6.1
Introduction.........................................................................................22
6.2
Tools....................................................................................................23
6.3
Procedure............................................................................................24
6.3.1

Call patterns............................................................................................................. 24

6.4
6.5

Standard Drive test Acceptance Reports and KPIs...........................25


Drive Test KPIs....................................................................................26

6.5.1
6.5.2
6.5.3

Drive Test KPIs for CS............................................................................................. 26


Drive Test KPIs for PS R99 and HSPA.....................................................................27
Standardized reports examples...............................................................................28

INITIAL DRIVE TEST...........................................................................................31


7.1
Cluster and drive route definition........................................................31

INVESTIGATION & PROBLEM ANALYSIS.........................................................33


8.1
Tools....................................................................................................33
8.2
Initial cluster report..............................................................................33
8.2.1
8.2.2
8.2.3
8.2.4

High level KPI Report............................................................................................... 33


Measurement overview............................................................................................ 34
Failure categorisation............................................................................................... 34
Cluster Optimisation................................................................................................. 34

8.3

Corrective actions...............................................................................52

SECOND DRIVE TEST........................................................................................53

10

FINAL CLUSTER TUNING REPORT..................................................................55


10.1
Executive Overview.............................................................................55
10.2
Measurement Overview......................................................................55

REFERENCES................................................................................................................56
ANNEXES.......................................................................................................................57

4/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

TABLE OF FIGURES
Figure 1 Pre Optimisation procedure flowchart (Cluster Acceptance)......................................6
Figure 2 Consistency check procedure using Plan Editor and MS Access flowchart................8
Figure 4 UL load with HSUPA...................................................................................................11
Figure 5 - Application Launcher Window...................................................................................12
Figure 6 Fault Management window......................................................................................13
Figure 7 RNC Object Browser Window..................................................................................13
Figure 8 NetAct Reporter Fault Management in Reporting Suite...........................................14
Figure 9 Effect of wrong cable loss value in the commissioning file.......................................15
Figure 10 Prx Noise Statistic in KPI Browser..........................................................................15
Figure 11 Prx Noise Rise in Interfered cell after HSUPA activation in other cell.....................16
Figure 12 Prx Noise Statistic in KPI Browser..........................................................................16
Figure 13 Prx Noise rise in Online Monitoring Tool.................................................................17
Figure 14 NetAct Reporting Suite Window, Service Level KPIs.............................................18
Figure 15 NetAct Reporting Suite Window, Handover KPIs...................................................18
Figure 16 NetAct Reporting Suite Window, Cell Resource KPIs............................................19
Figure 17 Rank/Track list example.........................................................................................20
Figure 18 Example of KPIs during the RAS upgrade.............................................................22
Figure 19 Failures related to coverage can be excluded........................................................26
Figure 20 Cluster buffer zone definition..................................................................................32
Figure 21 - RSCP plot...............................................................................................................35
Figure 22 RSCP plot per scrambling code.............................................................................36
Figure 23 Best Server plot per scrambling code....................................................................36
Figure 24 Best Server plot Swapped feeders......................................................................37
Figure 25 EcNo plot...............................................................................................................38
Figure 26 EcNo plot Comparison Tilting up helps to improve EcNo....................................38
Figure 27 Propagation delay distribution................................................................................39
Figure 28 Pilot pollution plots.................................................................................................40
Figure 29 Pilot Pollution plot with pilot polluter workbook.......................................................40
Figure 30 Call setup failure in poor coverage area.................................................................41
Figure 31 Call Setup failures caused by measurement tool...................................................42
Figure 32 Drop call in poor RSCP area. Call discarded from performance statistic................43
Figure 33 Drop caused by missing neighbor..........................................................................44
Figure 34 Overshooting site causing interference..................................................................45
Figure 35 Sudden Field drop example...................................................................................46
Figure 36 Best Server Plot.....................................................................................................47
Figure 37 Nemo Analyzer throughput breakdown..................................................................48
Figure 38 Actix Throughput breakdown..................................................................................48
Figure 39 HSDPA throughput distribution example................................................................49
Figure 40 HSDPA throughput example with 6 codes used.....................................................50
Figure 41 HSUPA throughput example as a function of Received RSCP (field test)..............50
Figure 42 HSUPA throughput example as a function of Received RSCP (lab test)...............51
Figure 43 HSUPA throughput vs. EcNo (lab test)......................................................................52
Figure 44 EcNo vs. RSCP distribution....................................................................................53
Figure 45 EcNo distribution comparison between first and second drive test.........................54

5/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

INTRODUCTION AND SCOPE

The scope of this document is to describe the tasks to be performed during pre-launch
optimisation of 3G radio network and provide guidance to Radio Network Planners on the way
to perform pre-launch optimization; it does not contain detailed explanation of the tools to be
used. This document covers RAS06 release.
Standardized drive test acceptance reports & KPI formulas are provided in order to allow
network benchmarking and valid comparison of performance in different netwoks.
The processes described in this document are generic and should be adapted to any project
depending on the scope and share of responsibilities between Nokia Siemens Networks (NSN)
and the operator.
2

RAS06 FEATURE UPDATE

The list of main RAS06 features can be seen in the table below. Activated feature have an
important impact on performance. More detailed information about each feature can be found in
RAS06_HSPA_Planning guide [9].

Table 1 RAS06 Feature list

6/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

HSDPA 10/15 Codes potentially have an important impact on user and cell throughput and it
should be carefully verified which features are activated and licensed in a given bts and
network. Some of these features require Ue support (see chapter 6.1).
3

PRE OPTIMIZATION PROCEDURE

3.1

Flowchart

Below is a flowchart of pre-optimization procedure.

Figure 1 Pre Optimisation procedure flowchart (Cluster Acceptance)

3.2

Overview

The main steps of pre-optimization procedure are here.

Parameter consistency check has to be performed before sites are put on air. All
inconsistencies detected have to be corrected by NSN or operator prior to optimization
activities.
Once sites are operational, network performance and system status KPIs health check
has to be performed. Any issues detected have to be investigated and corrected.
Initial drive test and drive test data analysis starts after network is cleared from
parameter inconsistencies and KPI health check is passed.
The cluster acceptance report with drive test performance KPIs is prepared. Corrective
actions are required if KPI requirements are not fulfilled.

If network performance, system status or drive test performance KPIs requirements are not
fulfilled, the reasons have to be investigated and corrected. The sites have to be switched off if

7/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

severe problems are found. After corrective actions, KPI health check has to be performed
again and a second drive test should follow.
1. System engineers investigation is required. There should be no more than 2 drive tests
performed for the cluster pre-optimization. A 3rd drive test should be performed only as
an exception.
2. Final cluster acceptance report has to be completed when drive test performance KPIs
reach the targets.
The process in greater detail will be described in the following paragraphs.

8/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

CONFIGURATION AND PARAMETER CHECK

4.1

Tools

Following tools are normally used in configuration and parameter check:

4.1.1

Plan Editor & MS Access.


OmLite.
Project Tools (Internal parameter audit tool).
CM Analyzer (Requires access to NetAct
Procedure

Even though main target of pre launch optimisation is coverage and dominance areas, it is
important that parameter consistency check is performed before starting drive tests. The
following has to be checked using either Plan Editor and Project Tools, or CM Analyzer:

Cell has no neighbours defined.


Intra site neighbours missing.
One-way adjacencies.
ADJG data.
Feeder and MHA data in BTS commissioning file matches RNC site data (Requires
OmLite to fetch BTS commissioning data).
Iub and transmission are correctly set up.

Check whether parameters are set to recommended/default values already in initial data build.
Latest recommended parameter list can be found in [2]. The parameter audit procedure can be
found in [1].
The consistency check procedure using Plan Editor and MS Access, Project Tools is showed
below.

Figure 2 Consistency check procedure using Plan Editor and MS Access flowchart

9/57

SBU Managed Services


NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

lAlternatively, when it is accessible, CM Analyzer can be used by simply choosing the audit
rules from the GUI menu.
4.2

RAS5.1 Upgrade to RAS06 parameter recommendations

During RNC SW upgrade it is recommended to change some parameters compared to RAS5.1.


With RAS06 Dynamic resource allocation (DRA) HSDPA power is limited by the PtxMaxHSDPA
parameter. Normally this parameter is used without DRA.
In RAS06 the new parameter PtxCellMax limits the maximum cell total power (non HSDPA +
HSDPA power). Its default value is 43 dBm. The maximum cell power allowed by the RNC will
be min(PtxCellMax, max DL power capability) where "max DL power capability" is the capability
of the WPA This parameter should be set according to the WPA Power in the cell.

PtxCellMax = 39 dBm for 8W metrosites


PtxCellMax = 43 dBm for 20W ultrasites
PtxCellMax = 46 dBm for 40W ultrasites

Also this parameter should be set in line with maximum HSDPA power allowed in the cell
Max DL Power Capability of BTS >= PtxMaxHSDPA
Recommendation: set PtxMaxHSDPA equal to PtxCellMax
With this setting, HSDPA power is free to use the full WPA power
PtxCellMax should be also set to a value higher than PtxTargetHSDPA + PtxMaxHSDPA if static
resource allocation is used otherwise RNC downgrades HSDPA power.
Possible upgrade from RAS5.1:

PtxTargetPSMax = PtxTargetPSMin = old value of PtxTargetHSDPA

There are also parameters used for Dynamic NRT DCH scheduling NRT DCH scheduling
between R99 and HSDPA power. It is possible to switch off the feature;
PrxTargetPSMax = PrxTargetPSMin = PrxTarget, 4 dB default value
In case the feature is switched on:

PrxTargetPSMin <= PrxTargetPSMax <= PrxTarget in order to avoid inconsistency


PtxTargetPSMin <= PtxTargetPSMax <= PtxTarget in order to avoid inconsistency

The introduction of HSUPA requires consideration of the target maximum uplink load and the
corresponding maximum uplink interference power. Also in RAS06 throughput based algorithm
is used with low load (better throughput compared to power based algorithm with high UL
interference)
In general, the target should reflect the interference margin assumed within the link budgets
generated during radio network planning. If the target value is allowed to become significantly

10/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

greater than the planned value then UE are more likely to experience a lack of uplink coverage,
i.e. they will not have sufficient transmit power to be received by the Node B.
The introduction of HSUPA will increase the uplink interference power and so can increase the
probability of a UE experiencing a lack of uplink coverage. This increases the importance of
monitoring KPI associated with uplink coverage both before and after HSUPA has been
introduced.
Below is described a possible process for determining UL interference prior to HSUPA
activation.

Figure 3 UL interference Analysis Process for HSUPA

The maximum planned uplink load is defined by the parameter PrxMaxTargetBTS (WCEL
parameter).
The Node B uplink interference margin corresponds to the value allocated to the RNC databuild
parameter, PrxMaxTargetBTS. The RNC uplink interference margin corresponds to the value
allocated to the RNC databuild parameter, PrxTarget.

Node B scheduler shares resources between UE with HSUPA connections


RNC scheduler continues to manage R99 DCH connections

PrxTarget<PrxMaxTargetBTS: HSUPA Capacity issue


The interference margin allocated to the RNC is relatively small. This approach ensures that the
Node B always has a relatively large share of the total interference margin to allocate to HSUPA
connections.

11/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

PrxTarget>=PrxMaxTargetBTS: HSUPA Best effort


The Node B is allocated the same interference margin as the RNC
(Prxtarget=PrxMaxTargetBTS) which means that the Node B packet scheduler will be limited to
operating on a best effort basis after the RNC has scheduled its DCH connections, i.e. the DCH
connections will have priority to the interference margin resource.

Figure 4 UL load with HSUPA

The Default value of planned Maximum UL Load is of 75%, defined by the parameter
PrxMaxTargetBTS=6db.
To enable HSUPA, there are more parameters which should be checked. For example it is
required to specify a dedicated HSPA FMCS measurement id. The content of HSPA FMCS
identifier could potentially be the same as used for HSDPA, but if somebody wants different
values for HSPA then a new FMCS identifier should be generated.
HSUPA activation requires the HSDPA Dynamic Resource Allocation (RAN312) feature to be
enabled. It also requires the HSDPA Serving Cell Change (RAN828) and HSDPA Soft Handover
for Associated DPCH (RAN829) features to be enabled.
HSUPA must be enabled for all cells at a Node B which are configured with the same RF
carrier. Enabling HSUPA requires the relevant cells to be locked and cannot be done online.
See other parameter recommendations in [2]

12/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

KPI HEALTH CHECK

5.1

Tools

NetAct tool family can be used for basic KPI check. They are listed below.

5.2
5.2.1

Net Act Reporting Suite (optional module).


Net Act Reporter (Report Builder, Report Explorer and KPI Browser).
RNW Online Monitoring Tool.
RNC Object Browser.
Optimizer 2.0
Procedure
Alarms check

Node B and transmission problems should be solved using counters, alarms:


Alarms associated with WBTSs and transmission should be checked before and during
drive test.
Alarm checking can be done with standard NetAct tools such as RNC RNW Object Browser
Figure 7 and Fault Management GUI via a direct connection to NEMU
Figure 6, or in the
Fault Management Reporting Suite Figure 8.

Figure 5 - Application Launcher Window

13/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Figure 6 Fault Management window

Figure 7 RNC Object Browser Window

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

14/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 8 NetAct Reporter Fault Management in Reporting Suite

5.2.2

Counters check for abnormal behaviour

The following counters will provide quick check whether cell is available and for abnormal
behaviour:
Ave Prx Noise (M1000C10). PrxNoise measurements allow identifying of the cells that
are experiencing uplink interference or are having hardware, commissioning issues.
Normal value of -104-108 dBm should be expected as seen in Figure 10. This
measurement can be found in the table 3G RAN Reports/Cell Resources/RSRAN001
(Uplink load in cells) of Net Act Reporting Suite Services. A rough filter as PrxNoise <110 dBm and >-98 dBm can be applied to get the list of the cells with too high or low
PrxNoise.
Causes of abnormal PrxNoise values:
MHA, feeder problems, WBTS commissioning problems, hardware problems, see
Figure 9 and Figure 13. More on this can be found in [6]

MHA malfunction can lead to artificially low PrxNoise value. There are often cases when
MHA is installed but power is not on.

UL Load, in case of HSUPA the UL interference may be higher than normally, see

External interference source - . If it is suspected that high PrxNoise is due to external UL


interference, the area should be drive tested to check for any external interferer

Interference can be checked with:

15/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Nokia WCEL counters (and KPIs).

Cell Load Monitoring Tool for on-line/real-time results, see Figure 13

Figure 9 Effect of wrong cable loss value in the commissioning file

Figure 10 Prx Noise Statistic in KPI Browser.

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

-100

-101

Figure 12 Prx Noise Statistic in KPI Browser.

RAS06_PreOptim
Error: Reference source not found
29/02/2008

15.10.2007 15:09:22

15.10.2007 15:09:05

15.10.2007 15:08:49

15.10.2007 15:08:32

15.10.2007 15:08:16

15.10.2007 15:07:59

15.10.2007 15:07:43

15.10.2007 15:07:26

15.10.2007 15:07:10

15.10.2007 15:06:53

15.10.2007 15:06:37

15.10.2007 15:06:20

NPO
Capability Developement

15.10.2007 15:06:04

15.10.2007 15:05:47

15.10.2007 15:05:31

15.10.2007 15:05:14

15.10.2007 15:04:58

15.10.2007 15:04:41

15.10.2007 15:04:25

15.10.2007 15:04:08

15.10.2007 15:03:52

15.10.2007 15:03:35

15.10.2007 15:03:19

15.10.2007 15:03:02

15.10.2007 15:02:46

16/57 SBU Managed Services


Copyright 2007 Nokia Siemens Networks.
All rights reserved.

Prx Total, interfered cell

-99

-102

-103

-104

-105

Figure 11 Prx Noise Rise in Interfered cell after HSUPA activation in other cell

17/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 13 Prx Noise rise in Online Monitoring Tool

Cell Availability, It is important to make sure that cells within the cluster are in normal
working order. Missing cells may have negative impact to cluster performance, analysis
and optimisation decisions. Cell Availability is measured as the ratio of the time when
cell has been available for service (cell state = WO) and the time when cell has existed
in RNC database. This measurement can be found in the table 3G RAN
Reports/Services/RSRAN003 (Summary) of Net Act Reporting Suite. The expected
value should typically be above 99%.

Load power identifies if all of the transmission power samples are in the class 0, which
means that there is nothing sent to terminals. This measurement can be found in the
table 3G RAN Reports/Cell Resources /RSRAN002 (Downlink load in cells) of Net Act
Reporting Suite. Expected value depends on CCH power settings, and can be in
between 35 and 36.5 dBm (20W / carrier) depending on FACH load.

RRC Setup Attempt identifies if there are any call attempts The value 0 means either
that the cell is unable to communicate with terminal and start call set up procedure, or
that no registrations or call setups have been made in that cell which can be unlikely
in many scenarios. This measurement can be found in the table 3G RAN
Reports/Services/RSRAN004 (RRC Connection Setup) of Net Act Reporting Suite.

RRC Setup Success identifies that call attempts continues to real calls from the network
point of view. Value 0 means no calls were established in the cell. This measurement
can be found in the table 3G RAN Reports/Services/RSRAN004 (RRC Connection
Setup) of Net Act Reporting Suite.

Active Set Time = 0 identifies that there has not been any terminal connected in any
way to the cell. Can be found in the table 3G RAN Reports/Handover/RSRAN016 and
RSRAN017 (Active set size for real time traffic/Active set size for non-real time traffic) of
Net Act Reporting Suite.

The Counter/KPIs can be checked using NetAct Reporter Services, Handover, and Cell
Resources KPIs as showed in Figure 14, Figure 15 and Figure 16

18/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Figure 14 NetAct Reporting Suite Window, Service Level KPIs

Figure 15 NetAct Reporting Suite Window, Handover KPIs

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

19/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 16 NetAct Reporting Suite Window, Cell Resource KPIs

5.2.3

Neighbor Definition

In case traffic exists in the network Autodef HO statistics and E-NAPS tool can be used to
define/delete neighbors in the network prior to drive test. For more refer to [7].
Additionally NetAct Optimizer 2.0 can detect and correct missing neighbors, see more in
RAS06 delta optimization training [10]
5.2.4

Cell rank/track list

During the pre-optimization cells rank/track list can be maintained to provide daily cell level
performance statistics. This helps quickly to find out cells having major impact to the
performance and RRC pollution See Figure 17.

20/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 17 Rank/Track list example

The following KPIs are most useful and can be included to the Rank/Track list. The new RAS06
packet call measurements could be used also to see accessibility for DCH users (user plane
capacity allocation).

5.3

RRC_CONN_STP_FAIL_AC.
RRC_CONN_STP_FAIL_TRANS.
RRC_CONN_STP_IUB_AAL2
RRC_CONN_STP_FAIL_BTS.
RRC_CONN_ACC_FAIL_RADIO
RRC_CONN_ACT_FAIL_RADIO
RAB_ACT_FAIL_<traffic class>_RADIO
SETUP_FAIL_IUB_HS_TOTAL_BGR/INT.
SETUP_FAIL_BTS_HS_DSCH_BGR/INT
SETUP_FAIL_HS_DSCH_AMR_BGR/INT
RAS5.1 Upgrade to RAS06 main OSS KPIs to follow

The following KPIs will inform the performance change (if any) during the upgrade. These are
mainly from RAS06 System Program report.
Setup phase:
RRC setup and access complete ratio, RNC_94e
RAB setup complete success ratio for CS voice calls, RNC_23a

21/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

RAB setup success ratio for PS NRT,RNC_576d


CSSR CS Voice, RNC_565f
Packet Session Setup Success Ratio, RNC_916a
HSDPA Setup Success Ratio from user perspective, RNC_914a

Mobility phase:
SHO Success Rate RT, RNC_194a
SHO Success Rate NRT, RNC_191b
ISHO Success Rate RT, RNC_300c
ISHO Success Rate NRT, RNC_301a
IFHO Success Rate, RNC_168a
HSDPA Serving Cell Change Success Rate, RNC_733a
Release phase:

RRC Connection Succ Ratio, RNC_217d


RAB Success ratio CS Voice, RNC_231c
CS Voice minutes, RNC_745a
PS NRT RAB success ratio, RNC_615b
Packet Session Success Ratio, RNC_922a
HSDPA Success Ratio from user perspective, RNC_920a

Other:

HSDPA data volume (MAC-d) at Iub, RNC_608b


Active HS-DSCH MAC-d throughput network perspective, RNC_722b
HSDPA MAC-hs efficiency (%), RNC_607c

Below is one example of mobility KPIs during the upgrade. SCC success rate were improved
due to amount of AC failures decreased after RAS06 upgrade.
100.000

95.000
RNC_194a SHO Success Rate RT
RNC_191b SHO Success Rate NRT
RNC_300c ISHO Success Rate RT

90.000

RNC_301c ISHO Success Rate NRT


RNC_733a HSDPA Serving Cell Change
Success Rate(%)
85.000

80.000

RAS06
upgrade

22/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 18 Example of KPIs during the RAS upgrade

DRIVE TEST TOOLS AND PROCEDURES

6.1

Introduction

The main purpose of the drive test is to collect network performance data from the user
perspective and use it to find installation errors and adjust antennas directions and down tilts.
The main KPIs used to pre-optimize the radio network are related to coverage and call
performance.
Coverage KPIs:

RSCP, dBm. Try to avoid any commitments to any level of RSCP since NSN
usually doesnt have influence to the site selection and coverage holes can not be
avoided.

EcNo, dB. Try to avoid any commitments to any level of EcNo since traffic growth
will increase interference, measured with no HSDPA active users in the cell.

If HSPA is activated in the cell, the reported CQI distribution can be used as well.

Performance KPIs:

Throughput UL & DL, kbps. Commitment to reasonably low values is possible since
there is no control of the traffic in the network.

CDR (Call Drop Rate).

CSSR (Call Setup Success Rate)

RTT (Round Trip Time between client (PC) and FTP server)

SHO success rate (R99)

SCC success rate (HSPA)

Note that HSDPA and HSUPA maximal throughput depend on the UE category.

23/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Table 2 HSDPA bit rates for different UE categories

Table 3 Different UE categories

UE category 6 is not supported in RAS06.

6.2

Tools

Any drive test tool can be used, however recommended tools is Anite Nemo Outdoor. See more
information about the tool from [4]
NEMO test kit with UE primarily measures SC signals from the cells that the system has the UE
through the BCH (neighbour list) or via the measurement control message to identify:
o
o
o
o
o
o
o

CPICH RSCP Active/Monitored Set.


Carrier RSSI.
CPICH Ec/No Active/Monitored Set.
UL/DL Data Throughput.
Downlink BLER.
SIR target (UE dependent).
UE Tx Power.

24/57 SBU Managed Services

NPO
Capability Developement

o
o
o

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Call Statistic: AMR, CS and PS data calls.


HSDPA: Reported CQI distribution
HSPA: Transport Block Size distribution

Scanner for scanning CPICH RSCP (dBm) and EcNo (dB) values of all DL scrambling
codes in operators frequency range to identify:
o
o
o
o

6.3

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Low coverage areas.


Antenna installation problems.
Missing neighbours.
Non optimized coverage.

Procedure

Enough call samples have to be made to make the measurement statistically valid:

In a 50 call sample one dropped call will cause a change in performance of -2%.

In a 500 call sample one dropped call will cause a change in performance of -0.2%.

Call length should be defined at the beginning. It can be set different call testing
patterns for different optimisation techniques as Short calls (for Call setup performance
and delay) and Long calls (for Drop call performance and SHO performance), but to
save post processing time and resources it is recommended to use only one call type as
suggested further.

6.3.1

Call patterns

It is recommended to perform measurement with the following test patterns:


Voice and Video Mobile Originated (MOC) and Mobile Terminated (MTC) calls:

5 seconds idle.

60 seconds call time

When testing ISHO, UE should be in Dual mode (2G/3G) to see possible handover
areas.

PS Call:
GPRS Attach.
PDP Context Activation.
FTP Download (example 4MB file)/FTP Upload (example 2 MB file).
PDP Context Deactivation.
GPRS Detach.
5 sec idle time.
UE should be in Dual mode (2G/3G) to see possible handover areas.
HSDPA call:
FTP continuous download (example 100 MB file download).

25/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Ideally simultaneous Voice +Video+ PS + HSDPA+ Scanner test should be performed, but
possibility of running four simultaneous tests in the single computer is not verified. To run
additionally HSDPA test in the same time, extra computer and NEMO license will be needed.
HSUPA Call
FTP continues upload (~100 MB file Upload)
6.4

Standard Drive test Acceptance Reports and KPIs

Standardized Actix and Nemo Analyzer reports should be used to analyze Field measurement
results and KPIs. Using Standard drive test reports:

No need to create own reports for each projects

Results are comparable between the projects

Currently there are reports supporting Nemo Outdoor data, but versions for other drive test
tools can be made once requested/needed (and sample files provided). Following reports are
currently (05/2008) available for Actix.
-

NSN Nemo CS Acceptance Report is for CS domain and includes RF information part
typically used in Actix default cluster acceptance reports

NSN Nemo PS Acceptance Report is for PS domain and includes RF information part
typically used in Actix default cluster acceptance reports

NSN Nemo HSPA Acceptance Report is for PS domain

Due to too heavy report structure, PS R99 and HSPA reports are separated
NSN Standard acceptance reports for Actix can be found from [11].
These reports should be more accurate than any default reports in Actix Analyzer/Spotlight. For
e.g. RACH & RRC connection problems are detected for PS setups and failures should be
aligned with 3GPP specs (considering repetitions of GMM and SM messages). Also reports
work for dual mode measurements although at the moment RF failures are given only for
UMTS side (application/signalling level failures should be ok for 2G too).
This package could be extended to include other reports or these reports can be expanded to
show more details. Also there might be some special cases (tool problems etc.) that are not
properly handled as development has been based on a limited set of test files.
About Actix - Current Actix version (GA11) has limited HSUPA support, so it is recommended
to use Nemo Analyze instead for basic optimization work. Also using Actix Analyzer requires
ALWAYS dedicated/modified workbooks. The default analysis in Actix doesnt provide reliable
results.
About Nemo Analyzer - NSN specific customized analysis for Nemo Analyze are to be
provided during 2H/2008. Already today it is possible to customize KPIs in Nemo Analyze, but
in larger scale (NSN standard reports) it should be possible with the release of version 5.11.

26/57 SBU Managed Services

RAS06_PreOptim
Error: Reference source not found
29/02/2008

NPO
Capability Developement

6.5

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Drive Test KPIs

Drive test KPIs typically contains set of KPIs for Coverage and for Service Level. In General,
service level KPI targets are valid in regions with sufficient coverage and good radio conditions.
Using NSN standard Acceptance report it is possible to exclude failures related to bad
coverage if wanted.

Example of Call Success Criteria

RSCP
Signal
above
RSCP
threshold

-80dBm

Call
OK

Call
OK
Call
NOK

Call- (B)

Ec/No

-5dB

Signal above
Ec/No
threshold

- 12dB

- -95dBm
Signal
below
RSCP
threshold

-110dBm

Call
OK

Threshold

Call-(A)

Call
NOK

- 20dB

Signal
below
Ec/No
threshold

Discard sample

Time

Figure 19 Failures related to coverage can be excluded

Service level KPIs are divided for CS and PS part.


6.5.1

Drive Test KPIs for CS

Following table present drive test KPIs for CS domain. Measurement triggering methods
presented here equals to those used in NSN Nemo CS Acceptance Reports. KPIs in table
below are divided for General CS KPIs, which should be always measured and for Optional CS
KPIS. FPI (Field Performance Indicator) Identifier is provided for all Drive test KPIs.
PI #

FPI Name

Triggering

KPIs for CS
FPI_6a

Call Setup Time - Voice MOC @ 95%

FPI_7

Call Setup Success Rate - Voice (%)

MOC setup time is the interval between the


submission of the "RRC CONNECTION
REQUEST" message and the reception of the L3
msg "CC ALERTING" at a UE.
Ratio between successfully established CS voice
calls compared to the overall number of voice call
establishment attempts - DL direct transfer (CC:
alerting) message is received by UE

27/57 SBU Managed Services

NPO
Capability Developement

FPI_8

FPI_9

FPI_10

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Call Setup Success Rate - Video (%)

Ratio between successfully established CS voice


calls compared to the overall number of voice call
establishment attempts - DL direct transfer (CC:
alerting) message is received by UE

Drop Call Rate - Voice (%)

Ratio between abnormally released voice calls


and the overall number of established voice calls
(e.g. RRC Connection Release message is
received before UL/DL CC: disconnect )

Drop Call Rate - Video (%)

Ratio between abnormally released video calls


and the overall number of established video calls
(e.g. RRC Connection Release message is
received before UL/DL CC: disconnect )

KPIs for CS Optional


FPI_6b

Call Setup Time - Voice MMC (sec)

FPI_11

Call Setup Time - Video MMC (sec)

FPI_12

SHO Overhead

FPI_13

SHO Success Rate

FPI_14

ISHO Success for Voice 3G-> 2G (%)

FPI_15
ISHO Success for Voice 2G-> 3G (%)

RRC Connection request message to DL direct


transfer (CC: alerting) msg.
RRC Connection request message to DL direct
transfer (CC: alerting) msg.
100*(Ave AS Size -1)%.
SHO success is defined as the ratio of successful
Active set updates and Active set update
attempts
From HandoverFromUTRANCommand to
Handover Complete to GMS (or continue
successfully in 3G ?)
From RR Inter System From UTRAN Handover
Command to HandoverToUTRANComplete
message.

Table 4 - Drive test KPIs for CS domain

6.5.2

Drive Test KPIs for PS R99 and HSPA

Following table present drive test KPIs for PS domain. Measurement triggering methods
presented here equals to those used in NSN Nemo PS and HSPA Acceptance Reports. KPIs
in table below are divided for General PS KPIs, which should be always measured and for
Optional PS KPIS. FPI (Field Performance Indicator) Identifier is provided for all Drive test
KPIs.

PI #

FPI Name

Triggering

KPIs for PS
FPI_20

Average Attach Time (sec)

RRC Connection request message to Attach


Accept message

FPI_21a

Average PDP Context Activation time

Between the "RRC CONNECTION REQUEST"


msg. and the reception of the L3 message
"ACTIVATE PDP CONTEXT ACCEPT" at a UE.

28/57 SBU Managed Services

NPO
Capability Developement

FPI_22

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Activate PDP Context Success Rate (%)

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

RRC Connection request message to


Activate PDP context Accept message

FPI_23
Average DL throughput (DCH) @ 95%
FPI_24
Average UL throughput (DCH) @ 95 %
FPI_25
Average HSPA DL throughput @ 95%
FPI_26
Average HSPA UL throughput @ 95 %
KPIs for PS - Optional
FPI_27

PS Session Retainability ratio (%)

FPI_28

HSDPA setup success ratio (%)

FPI_29

HSPA setup success ratio (%)

FPI_30

HSDPA Retainability (%)

FPI_31

HSPA Retainability (%)

FPI_32

HSPA SCC Success (%)

Number of successful PS setups - number of


lost PS sessions/Number of established PS
sessions.
UL-DCCH -Measurement Report (e4A)
message to Radio Bearer Reconfiguration
complete msg.
UL-DCCH - Measurement Report (e4A)
message to Radio Bearer Reconfiguration
complete msg. (HSPA allocated)
(Number of Successful HSPA Setups
Number of lost HSPA Sessions)/Number of
Successful HSPA Setups
(Number of Successful HSPA Setups
Number of lost HSPA Sessions)/Number of
Successful HSPA Setups
Radio Bearer Reconfiguration message to
Radio Bearer Reconfiguration complete msg.

Table 5 Drive Test KPIs for PS

6.5.3

Standardized reports examples

NSN Nemo CS Acceptance Report Contains CS domain service level KPIs and includes RF
information part. Results in RF info part are based on UE measurement, and provide useful
information about field conditions but cannot be used for official acceptance. Coverage KPIs
(CPICH EcNo and CPICH RSCP) should always measured by the scanner.
The following Service level KPIs can be measured with CS Acceptance Reports:

CS Call setup times


CS Call Setup Success (with or without bad coverage failures excluded)
CS Call drop ratio (with or without bad coverage failures excluded)
SHO success ratio
ISHO (3G <->2G ) success Rate

Example below presents CS acceptance report summary page. Target values can be modified
with Actix.
Service level KPIs
Call Setup Success Rate - bad coverage excluded
Drop Call Rate - bad coverage excluded
Call Setup Success Rate
Drop Call Rate

Target
95.0%
2.0%
95.0%
2.0%

Samples
65
65
65
65

Result
100.0%
0.0%
100.0%
0.0%

Status
PASSED
PASSED

29/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Call Setup Time (sec)


Soft Handover Success Rate
ISHO 3G to 2G Success Rate
ISHO 2G to 3G Success Rate

6.0
98.0%
97.0%
97.0%

65
486
13
0

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

5.7
100.0%
100.0%
-

PASSED
PASSED
PASSED
-

Table 6 Example of CS domain acceptance report summary page


Due to the heavy report structure, there are currently two distinct reports for DCH PS R99 and
HSPA bearers. NSN Nemo PS acceptance reports contains PS domain service level KPIs and
includes RF information part based on UE measurements. NSN Nemo HSPA reports contains
HSPA service level KPIs.
Following Service level KPIs can be measured with PS Acceptance report:

Average Attach Time

Average PDP context Activation time

Attach Success Rate

PDP context Success rate (with or without bad coverage failures excluded)

PDP context drop rate (with or without bad coverage failures excluded)

PS ISHO success (3G <-> 2G)

Average DL throughput

Average UL throughput

Average HSDPA throughput

Following Service Level KPIs can be measured with HSPA acceptance report

HSPA setup success rate

HSPA Retainability

HSPA SCC success

HSDPA throughput

HSUPA throughput

Additionally to KPIs listed here, these reports provide lots of other useful information.
Example below presents PS report summary page. Target values can be modified with Actix.
Service level KPIs
Attach Success Rate - bad coverage excluded
Activate PDP Context Success Rate - bad coverage
excluded
PDP Context Drop Rate - bad coverage excluded
Attach Success Rate
Activate PDP Context Success Rate

Target
95.0%

Samples
54

Result
96.3%

Status
PASSED

95.0%
5.0%
95.0%
95.0%

53
52
54
53

98.1%
7.7%
96.3%
98.1%

PASSED
FAILED
PASSED
PASSED

30/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

PDP Context Drop Rate


Average Attach Time (sec)
Average PDP Context Activation Time (sec)
Cell Change Order to 2G Success
Cell Change Order to 3G Success
Average Downlink Throughput
Average Uplink Throughput
Average HSDPA Throughput

5.0%
3.0
2.0
96.0%
96.0%
200
50
1100

52
50
52
13
9
17
13
0

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

7.7%
1.98
1.62
84.6%
77.8%
131.3
101.3
-

FAILED
PASSED
PASSED
FAILED
FAILED
FAILED
PASSED
-

Table 7 - Example of PS domain acceptance report summary page

Example below presents HSPA report summary page. Top of the KPIs, it provides lots of other
useful information like used modulation and technology during data transfer
KPI
HSDPA Availability (cell level)
94.4%
HSDPA Availability (transfer level)
97.1%
HSDPA Retainability (transfer level)
98.5%
HSDPA Setup Success Rate
98.6%
HSDPA Setup Time @ 95%
1503
msec
HSDPA Connection Drop Rate
0.0%
Average HSDPA QPSK Use
39.3%
Average HSDPA 16QAM Use
60.7%
Average CQI
18.88
Average HSDPA L1 Throughput
2616.61 kbit/s
Average HSDPA MAC Throughput
2251.31 kbit/s
Average App Throughput (HSDPA)
2079.46 kbit/s
Average HSDPA FER
10.2%
Average 1st ReTransmission
10.2%
Technology during data transfer
Time on HSDPA
Time on R99
Time on GPRS
Time on No Channel
HSDPA Cell Change
Cell Change Success Rate
Reselection delay via DCH (msec)
Reselection delay via FACH (msec)
Reselection delay via Cell Update (msec)
Reselection delay via RL Recovery (msec)
Reselection delay via RLC Unrecoverable (msec)
Reselection delay via multiple Cell Updates
(msec)
Reselection delay vith RAU (msec)

86.5%
13.5%
0.0%
0.0%
Count
23
22
0
0
0
0

100.0%
1007
-

0
0

31/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Non-classified cell reselection delay (msec)


Drop/Fail During Reselection

1
1

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

7864

Table 8 Example of HSPA report summary page

INITIAL DRIVE TEST

The following is required for the drive test:

Planned drive test routes. Exclusion areas defined if data is available from operator.

Support is available from RNC team. If a severe network problem is encountered then
the drive test will be temporarily suspended and problem rectified before proceeding.

7.1

Cluster and drive route definition

The clusters shall be defined by NSN and agreed with customer and documented. Following
criteria shall be used in defining the cluster:

Each cluster shall comprise a network area of approximately 10 to 20 geographically


adjacent sites.

The drive route in the cluster shall be planned in such a way that it covers different
clutter categories e.g. highway, main roads and major streets, however, the total
measurement time for a cluster shall not exceed 5 hours.

Clusters are influenced by a number of factors including geography (water, mountains,


etc.), clutter type and RNC or LAC boundaries.

All sites in the cluster must be integrated and in working state during the measurements.

Small markets may have only one or two clusters.

As UMTS cells interfere with each other, it is not possible to reliably optimise the
coverage of a site unless its adjacent sites also exist. The Buffer Zone can be created
consisting of cells belonging to adjacent clusters that contribute interference to the
cluster being optimised. Typically, this corresponds to 2 or more tiers of sites from all
adjacent clusters as shown in Figure 20. All cells on-air in the Buffer Zone shall be
optimised at the same time as cluster 2, but with minimal changes made to cells
pointing towards cluster 1.

32/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Buffer zone also considered when cluster


2 is optimised.

Cluster 1

Cluster 2

Figure 20 Cluster buffer zone definition

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

33/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

INVESTIGATION & PROBLEM ANALYSIS

8.1

Tools

Any post processing tool can be used, however recommended tools are:

Actix/Actix Spotlight.

NEMO Analyze 5.

8.2

Initial cluster report

8.2.1

High level KPI Report

Key indicators:

CPICH RSCP (best server), mean and cumulative values.

CPICH Ec/No (best server), mean and cumulative values.

Detected SCs (within window), mean and cumulative values.

Call Setup Success Rate (CSSR). Successful call setup means that DL/UL Direct
Transfer (CC: Alerting) message is received by UE.

Call Drop Rate (CDR). The call is dropped when RRC connection release (not normal
release) message has been send from RNC to UE, but there will be cases when no
messages are sent.

Session Setup Success Rate. This is related to PDP context activation. Successfully
activated PDP context means that activate PDP context accept message has been sent
from RNC to UE (RRC: downlink direct transfer (activate PDP context Accept)).

Session Drop Rate. Session drop rate can be defined as the number of successful PDP
deactivations against number of successful PDP activations.

Active Set (AS) distribution.

DL BLER.

HSUPA HARQ retransmission rate

DL/UL Throughput (cell efficiency)

HSDPA Throughput with UL DCH

HSDPA Throughput with E-DCH

HSUPA Throughput

Cluster status (site condition, cluster completion).

34/57 SBU Managed Services

NPO
Capability Developement

8.2.2

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Measurement overview

Measurement Overview has to contain:


Drive route summary.
Drive Test Route with Best Server RSCP.
Drive Test Route with Best Server Ec/No.
Drive Test Route with DL BLER.
Drive Test Route with DL Throughput.
Drive Test Route with UL Throughput.
Drive Test Route with HSDPA Throughput.
Drive Test Route with HSUPA Throughput
Drive Test Route with Best Server scrambling codes (equiv. to Best Server Plot).
Detected scrambling codes (within window).
Map of drop and block locations.
Site database.
RF condition (tilt, azimuth).
Problems (cross feeders, etc.).
8.2.3

Failure categorisation

It is beneficial to categorise call failures during the analysis and reporting.


Non-genuine failures:
Measurement system fault (Collection or Analysis Tools).
Genuine failures:
RF issues (Coverage/ Interference/ Poor dominance).
Capacity Issue (WBTS, TRS)
Missing neighbour.
System issue WBTS.
System issue RNC.
Core network issue.
Unknown.
An example of a Cluster Report can be found in Attachment 1 - Sample report.
The KPI measurement conditions should be set to define exclusion areas during drive test for
acceptance of a cluster. All failures happening in those areas should be discarded.

8.2.4

Cluster Optimisation

KPI targets have to be agreed during contract negotiations phase. As mentioned before any
commitments to the RSCP and EcNo levels should be avoided. Regarding KPI values refer to
[3]

35/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

CPICH RSCP:
Must maintain typically good value of -98 dBm or better. Attenuators of typically 10-20dB
can be used to simulate indoor coverage during drive test if so requested by customer.
Without attenuators, dependent upon environment and site density, the targets will vary
per cluster taking into account indoor penetration loss of typically 10-20dB, i.e. -88-78
dBm. See Figure 21.

Optimization by changing antenna tilting and azimuth.

Figure 21 - RSCP plot

Plotting RSCP and best server areas of each SC highlights any hardware or data build
issues where the coverage area of the cell is different from the planned coverage. This
will include swapped feeders, incorrect azimuths/tilts or incorrect scrambling codes
assigned to the cell. See Figure 22, Figure 23, Figure 24.

Alternatively swapped feeders can be detected using Autodef counters, see more from
[7]. Also it is possible to detect swapped feeders with Actix scanner statistics, see more
from

It can also be used Tx Power or BLER plots for RSCP< -95dBm to help identify call
sustainability on the edge of the coverage.

36/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Figure 22 RSCP plot per scrambling code

Figure 23 Best Server plot per scrambling code

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

37/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 24 Best Server plot Swapped feeders

CPICH Ec/No:

Identifies areas of poor quality. See Figure 25.

Low EcNo usually occurs in poor dominance, i.e. pilot pollution areas. Best Server plot
will help to identify such areas, see Figure 36

Load generation can help generate more realistic Ec/No distribution. Simultaneous R99
and HSDPA test and HSDPA users in the network will automatically generate load.

Higher the better, the target is to improve without reduction of coverage, i.e. RSCP.
Typically EcNo of -12 dB is considered to be a good value.

38/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Figure 25 EcNo plot

Figure 26 EcNo plot Comparison Tilting up helps to improve EcNo

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

39/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

RNC ICSU logs can be post-processed by Logos tool or NetACT Optimizer to get
propagation delay per cell. This information can be used to find overshooting cells. As
seen in the cell 4377 has majority of RRC Setup Request samples coming from 14 km
distance. Its not acceptable if this is urban cell.

Figure 27 Propagation delay distribution

Plotting in Actix areas with EcNo<-12dB and RSCP>-92 dBm will help to identify
excessive polluters (overshooting cells), see Figure 28. Actix pilot polluter workbook will
help identify scrambling codes with highest number of samples, see Figure 29.

40/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Figure 28 Pilot pollution plots

Figure 29 Pilot Pollution plot with pilot polluter workbook

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

41/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Call Setup Success Rate (CSSR):


o Determine causes of all set-up failures and present solution. Since hardware
problems should be solved before the drive test, high call number of call setup
failure will happen in poor RSCP, dominance, i.e. low EcNo areas. Very often
these samples can be excluded from the drive test performance statistics. See
Figure 30.
o

Often call setup failures can be caused by measurement tool. It can be


recognized by consecutive failures as showed in the Figure 31.

Figure 30 Call setup failure in poor coverage area

42/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Figure 31 Call Setup failures caused by measurement tool

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

43/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Drop Call Rate (DCR):


o Target is to minimize dropped connections. Usually it will happen in poor RSCP,
dominance, i.e. low EcNo areas. See Figure 32.

Figure 32 Drop call in poor RSCP area. Call discarded from performance statistic

44/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Optimize neighbours. Keep in mind limitation of maximum allowed number. Max


number of neighbouring cells currently is 47 due to SIB 11/12 capacity limitation.
Planning rule of thumb is ADJS=15, ADJG=15, ADJI=15. More on this can be found
in [5]

Actix Analyzer contains functionality to suggest missing neighbours based on


scanner measurements. There are also cases when drops occur due to missing
neighbours, they can be found just by checking serving cell EcNo and RSCP levels
in location of the drop. See Figure 33

Figure 33 Drop caused by missing neighbor

45/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Check for overshooting and interfering sites. See Figure 34.

Figure 34 Overshooting site causing interference

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

46/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Often sudden field drop is reason of the drop. See Figure 35

Figure 35 Sudden Field drop example

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

47/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

SHO:
o Determine cases of excessive AS changes which are usually related to poor
dominance areas.

Figure 36 Best Server Plot

Throughput UL/DL:
Usually low throughput is related to poor dominance, low coverage areas.
Average throughput during the drive will vary due to different radio conditions,
number of HSDPA users, R99 radio bearers assigned and Dynamic Link
Optimization (Dylo) feature (in case it is enabled). For instance, some networks
have target average throughput of 200 kbps.
Low Iub capacity can have impact to the throughput. AAL2 reservations can be
checked in ATM counters (optional).
Alternatively throughput samples can be sorted out per bit rate using Actix or NEMO
Analyzer as presented in Figure 37, Figure 38. Actix scripts to perform this are
available in [4].
R99 and HSDPA throughput can be reported as presented in Table 9 and Figure 39.

48/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

It is recommended to have test server in the local network not the internet to be able
to control its status and connection.
HSUPA throughput can be limited to UE power, number of E1 links,
RSCP/interference situation, application itself or server problem, Figure 41 , Figure
42 and Figure 42

Figure 37 Nemo Analyzer throughput breakdown

Figure 38 Actix Throughput breakdown

49/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Table 9 Throughput report table

Figure 39 HSDPA throughput distribution example

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

50/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 40 HSDPA throughput example with 6 codes used

Figure 41 HSUPA throughput example as a function of Received RSCP (field test)

51/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 42 HSUPA throughput example as a function of Received RSCP (lab test)

52/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 43 HSUPA throughput vs. EcNo (lab test)

8.3

Corrective actions

Actions that are taken during the pre- optimisation are:


o Antenna Tilt.
o Antenna Azimuth.
o Neighbour List adjustment with Optimizer or E-NAPS tool
o Parameter checks & modifications
o Capacity issues in Node B or Iub
o Core network issues
After Initial drive test exclusion (low coverage) areas must be agreed with the customer and
documented.

53/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

SECOND DRIVE TEST

Second drive test is done for benchmarking purposes.

After corrections are implemented the second drive test is required.


Site status has to be checked to ensure all sites are performing properly.
The same route as the initial drive test will be followed.
For all drive routes make the same tests Voice Call +PS call+ HSDPA +Scanner.
Target to improve network performance, minimum to ensure corrective action do not
degrade performance. The plot in Figure 44 is very useful to compare whether network
improvement has been achieved in second drive test. Target is to have as many
samples as possible in the left corner in the figure. Separate reports available based on
Ue measurements and scanner measurements.

Figure 44 EcNo vs. RSCP distribution

Please note there might be the cases in operational network that EcNo is lower during the
second drive due to higher load, see Figure 45.

54/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

Figure 45 EcNo distribution comparison between first and second drive test

55/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

10 FINAL CLUSTER TUNING REPORT


After second drive test the final report has to be completed. It has to summarize improvements
achieved during series of the drive tests. The sample report can be found in Attachment 1 Sample report.
10.1 Executive Overview

Key indicators.

Cluster status.

10.2 Measurement Overview


Drive tests:
Drive route summary.

Results, Plots and Graphs.

Analysis

Problem areas summary

Solved (what has been done)

Unsolved

Unsolvable (as identified under exclusions)

Future Solutions (Sometimes you have to build a site)

Corrective Actions:

That have been proposed and implemented

Hardware/implementation issues

Azimuth, tilt adjustment

Parameter Tuning or Change Proposal

Site Database

Confirmed site database

Anomalies

Hardware problems during test

Performance degradation for reason outside of RF (uncontrollable)

56/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

REFERENCES

[1] UTRAN Audit Procedure (Currently, September 2007 is being updated).


Neighbour Assessment
https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/380115223
Parameter Assessment
https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/380101296
Configuration Assessment
https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/380108534
[2] Recommended Parameters.
https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/364619132
[3] KPI Guarantees For 3G Networks.
https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/364616733
[4] Field measurement tools.
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/364029436

[5] SIB 11 limitation


https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/364118774

[6] Impact of MHA and Feeder loss settings in WBTS & RNC.
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/364126227

[7] E - NAPS tool. Contact Simon Brown for more information.

[8] WCDMA Radio Network Optimization Guidelines for NetAct OPTIMIZER.


https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/364621128

[9] RAS06_HSPA_Planning Guide.

Copyright 2007 Nokia Siemens Networks.


All rights reserved.

57/57 SBU Managed Services

NPO
Capability Developement

RAS06_PreOptim
Error: Reference source not found
29/02/2008

https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/363690818
[10]

RAS06 Delta Optimization training.

https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?
func=ll&objId=387456853&objAction=Browse&viewType=1

[11]Standard Drive test Acceptance Reports:


https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/362255054

[12]

Actix Scanner Information:

https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/369367886

ANNEXES

Attachment 1 - Sample report

PRE-OPTMISATION_
PRIENAI_2007.08.24.zip

Copyright 2007 Nokia Siemens Networks.


All rights reserved.