RAS06 Pre-Optimization Guide Update 0508

UMTS Field-Optimization Guidelines

RAS06

2/56 SBU Managed ServicesNPOCapability Developement

RAS06_PreOptim Error: Reference source not found29/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 Teräväinen/Pekka Ranta

Date 22/05/2008

Approver Florian Reymond

CHANGE RECORD

VERSION DATE EDITED BY SECTION/S COMMENTS1.0 30/09/2007 Dalius Kaskelevicius ALL Version 1

0.1 -0.9 2007 Dalius Kaskelevicius, SIG, FR

ALL Working Drafts

1.0 22.05.2008 Kirsi Teräväinen,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




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

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

3 PRE OPTIMIZATION PROCEDURE.....................................................................63.1 Flowchart.............................................................................................63.2 Overview..............................................................................................6

4 CONFIGURATION AND PARAMETER CHECK..................................................84.1 Tools....................................................................................................84.1.1 Procedure.................................................................................................................. 84.2 RAS5.1 Upgrade to RAS06 – parameter recommendations................9

5 KPI HEALTH CHECK.........................................................................................125.1 Tools..................................................................................................125.2 Procedure..........................................................................................125.2.1 Alarms check...........................................................................................................125.2.2 Counters check for abnormal behaviour..................................................................145.2.3 Neighbor Definition..................................................................................................195.2.4 Cell rank/track list.....................................................................................................195.3 RAS5.1 Upgrade to RAS06 –main OSS KPIs to follow.....................20

6 DRIVE TEST TOOLS AND PROCEDURES.......................................................226.1 Introduction........................................................................................226.2 Tools..................................................................................................236.3 Procedure..........................................................................................246.3.1 Call patterns.............................................................................................................246.4 Standard Drive test Acceptance Reports and KPI’s...........................256.5 Drive Test KPIs..................................................................................266.5.1 Drive Test KPIs for CS.............................................................................................266.5.2 Drive Test KPIs for PS R99 and HSPA....................................................................276.5.3 Standardized reports examples...............................................................................28

7 INITIAL DRIVE TEST..........................................................................................317.1 Cluster and drive route definition.......................................................31

8 INVESTIGATION & PROBLEM ANALYSIS.......................................................338.1 Tools..................................................................................................338.2 Initial cluster report.............................................................................338.2.1 High level KPI Report...............................................................................................338.2.2 Measurement overview............................................................................................348.2.3 Failure categorisation...............................................................................................348.2.4 Cluster Optimisation.................................................................................................348.3 Corrective actions..............................................................................52

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

10 FINAL CLUSTER TUNING REPORT.................................................................5510.1 Executive Overview...........................................................................5510.2 Measurement Overview.....................................................................55

REFERENCES..............................................................................................................56

Annexes........................................................................................................................57




TABLE OF FIGURES

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




1 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




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




severe problems are found. After corrective actions, KPI health check has to be performed again and a second drive test should follow.

1. System engineer’s 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.




4 CONFIGURATION AND PARAMETER CHECK

4.1 Tools

Following tools are normally used in configuration and parameter check:

Plan Editor & MS Access. OmLite. Project Tools (Internal parameter audit tool). CM Analyzer (Requires access to NetAct

4.1.1 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

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 cellMax 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 valueIn 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 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.

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.

PrxTarget>=PrxMaxTargetBTS: HSUPA Best effort

Figure 3 UL interference Analysis Process for HSUPA




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]




5 KPI HEALTH CHECK

5.1 Tools

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

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

5.2 Procedure

5.2.1 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




Figure 6 – Fault Management window

Figure 7 – RNC Object Browser Window




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:




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.




Prx Total, interfered cell

-105

-104

-103

-102

-101

-100

-99

15.1

0.20

07

15:0

2:46

15.1

0.20

07

15:0

3:02

15.1

0.20

07

15:0

3:19

15.1

0.20

07

15:0

3:35

15.1

0.20

07

15:0

3:52

15.1

0.20

07

15:0

4:08

15.1

0.20

07

15:0

4:25

15.1

0.20

07

15:0

4:41

15.1

0.20

07

15:0

4:58

15.1

0.20

07

15:0

5:14

15.1

0.20

07

15:0

5:31

15.1

0.20

07

15:0

5:47

15.1

0.20

07

15:0

6:04

15.1

0.20

07

15:0

6:20

15.1

0.20

07

15:0

6:37

15.1

0.20

07

15:0

6:53

15.1

0.20

07

15:0

7:10

15.1

0.20

07

15:0

7:26

15.1

0.20

07

15:0

7:43

15.1

0.20

07

15:0

7:59

15.1

0.20

07

15:0

8:16

15.1

0.20

07

15:0

8:32

15.1

0.20

07

15:0

8:49

15.1

0.20

07

15:0

9:05

15.1

0.20

07

15:0

9:22

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

Figure 12 – Prx Noise Statistic in KPI Browser.




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




Figure 14 – NetAct Reporting Suite Window, Service Level KPIs

Figure 15 – NetAct Reporting Suite Window, Handover KPIs




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.




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).

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

5.3 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 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.

Figure 18 – Example of KPIs during the RAS upgrade

80.000

85.000

90.000

95.000

100.000

16.0

3.20

08

18.0

3.20

08

20.0

3.20

08

22.0

3.20

08

24.0

3.20

08

26.0

3.20

08

28.0

3.20

08

30.0

3.20

08

01.0

4.20

08

03.0

4.20

08

05.0

4.20

08

07.0

4.20

08

09.0

4.20

08

11.0

4.20

08

13.0

4.20

08

RNC_194a SHO Success Rate RT

RNC_191b SHO Success Rate NRT

RNC_300c ISHO Success Rate RT

RNC_301c ISHO Success Rate NRT

RNC_733a HSDPA Serving Cell ChangeSuccess Rate(%)

RAS06 upgrade

80.000

85.000

90.000

95.000

100.000

16.0

3.20

08

18.0

3.20

08

20.0

3.20

08

22.0

3.20

08

24.0

3.20

08

26.0

3.20

08

28.0

3.20

08

30.0

3.20

08

01.0

4.20

08

03.0

4.20

08

05.0

4.20

08

07.0

4.20

08

09.0

4.20

08

11.0

4.20

08

13.0

4.20

08

RNC_194a SHO Success Rate RT

RNC_191b SHO Success Rate NRT

RNC_300c ISHO Success Rate RT

RNC_301c ISHO Success Rate NRT

RNC_733a HSDPA Serving Cell ChangeSuccess Rate(%)

RAS06 upgrade




6 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 doesn’t 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.

UE Category 1 – 6 7 – 8 9 10 11 – 12

Modulation QPSK,16 - QAM

QPSK, 16 - QAM

QPSK, 16 - QAM

QPSK, 16 - QAM

QPSK

Number of HS-PDSCH codes

5 10 15 15 5

Air interface bit rate (Mbps)

4.8 9.6 14.4 14.4 2.4

Transport block size (bits)

7168 14411 20251 27952 3630

Transport channel (MAC-d flow) bit rate (Mbps)

3.584 7.2055 10.1255 13.976 1.815

RLC PDU (bits) 336 336 336 336 336

RLC blocks/TTI 21 42 60 83 10

RLC bit rate (Mbps) 3.528 7.056 10.08 13.944 1.68

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 CPICH RSCP Active/Monitored Set.o Carrier RSSI.o CPICH Ec/No Active/Monitored Set.o UL/DL Data Throughput.o Downlink BLER.o SIR target (UE dependent).o UE Tx Power.o Call Statistic: AMR, CS and PS data calls.o HSDPA: Reported CQI distributiono HSPA: Transport Block Size distribution

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

o Low coverage areas.o Antenna installation problems.o Missing neighbours.o Non optimized coverage.

6.3 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).

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 KPI’s

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 doesn’t 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.

6.5 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.

Signal above RSCP threshold

Signal below RSCP threshold

Signal above Ec/No thresho ld

Signal below Ec/No threshold - 110dBm

- -95dBm

- 80dBm

Time

RSCP

Call OK

Call OK

Call OK

Call NOK

Call NOK

- 12dB

- 5dB

- 20dB

Ec/No

Threshold

Example of Call Success Criteria

Discard sample

Call - (A)

Call - (B)

- 110dBm

-

- 80dBm

Time

RSCP

Call OK

Call OK

Call OK

Call NOK

Call NOK

-

- 5dB

- 20dB

Ec/No

Threshold


Discard sample

Call - (A)

- 110dBm

-

- 80dBm

Time

RSCP

Call OK

Call OK

Call OK

Call NOK

Call NOK

-

- 5dB

- 20dB

Ec/No

Threshold


Discard sample

- 110dBm

-

- 80dBm

Time

RSCP

Call OK

Call OK

Call OK

Call NOK

Call NOK

-

- 5dB

- 20dB

Ec/No

Threshold


Discard sample

Call - (A)

Call - (B)




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%

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.

FPI_7 Call Setup Success Rate - Voice (%)

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

FPI_8 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

FPI_9 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” )

FPI_10 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)“RRC Connection request” message to “DL direct transfer (CC: alerting)” msg.

FPI_11 Call Setup Time - Video MMC (sec)“RRC Connection request” message to “DL direct transfer (CC: alerting)” msg.

FPI_12 SHO Overhead 100*(Ave AS Size -1)%.

FPI_13 SHO Success RateSHO success is defined as the ratio of successful Active set updates and Active set update attempts

FPI_14 ISHO Success for Voice 3G-> 2G (%)From HandoverFromUTRANCommand to Handover Complete to GMS (or continue




successfully in 3G ?)

FPI_15ISHO Success for Voice 2G-> 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 timeBetween the "RRC CONNECTION REQUEST" msg. and the reception of the L3 message "ACTIVATE PDP CONTEXT ACCEPT" at a UE.

FPI_22 Activate PDP Context Success Rate (%)“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 (%)Number of successful PS setups - number of lost PS sessions/Number of established PS sessions.

FPI_28 HSDPA setup success ratio (%)“UL-DCCH -Measurement Report (e4A)” message to “Radio Bearer Reconfiguration complete” msg.

FPI_29 HSPA setup success ratio (%)“UL-DCCH - Measurement Report (e4A)” message to “Radio Bearer Reconfiguration” complete msg. (HSPA allocated)

FPI_30 HSDPA Retainability (%)(Number of Successful HSPA Setups” – “Number of lost HSPA Sessions”)/”Number of Successful HSPA Setups

FPI_31 HSPA Retainability (%)(Number of Successful HSPA Setups” – “Number of lost HSPA Sessions”)/”Number of Successful HSPA Setups

FPI_32 HSPA SCC Success (%)“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 Target Samples Result StatusCall Setup Success Rate - bad coverage excluded 95.0% 65 100.0% PASSEDDrop Call Rate - bad coverage excluded 2.0% 65 0.0% PASSEDCall Setup Success Rate 95.0% 65 100.0% Drop Call Rate 2.0% 65 0.0% Call Setup Time (sec) 6.0 65 5.7 PASSEDSoft Handover Success Rate 98.0% 486 100.0% PASSEDISHO 3G to 2G Success Rate 97.0% 13 100.0% PASSEDISHO 2G to 3G Success Rate 97.0% 0 - -

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 Target Samples Result StatusAttach Success Rate - bad coverage excluded 95.0% 54 96.3% PASSEDActivate PDP Context Success Rate - bad coverage excluded 95.0% 53 98.1% PASSEDPDP Context Drop Rate - bad coverage excluded 5.0% 52 7.7% FAILEDAttach Success Rate 95.0% 54 96.3% PASSEDActivate PDP Context Success Rate 95.0% 53 98.1% PASSEDPDP Context Drop Rate 5.0% 52 7.7% FAILEDAverage Attach Time (sec) 3.0 50 1.98 PASSEDAverage PDP Context Activation Time (sec) 2.0 52 1.62 PASSEDCell Change Order to 2G Success 96.0% 13 84.6% FAILEDCell Change Order to 3G Success 96.0% 9 77.8% FAILEDAverage Downlink Throughput 200 17 131.3 FAILEDAverage Uplink Throughput 50 13 101.3 PASSEDAverage HSDPA Throughput 1100 0 - -

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 msecHSDPA 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/sAverage HSDPA MAC Throughput 2251.31 kbit/sAverage App Throughput (HSDPA) 2079.46 kbit/sAverage HSDPA FER 10.2%




Average 1st ReTransmission 10.2%

Technology during data transfer Time on HSDPA 86.5%Time on R99 13.5%Time on GPRS 0.0%Time on No Channel 0.0%

HSDPA Cell Change Count Cell Change Success Rate 23 100.0%Reselection delay via DCH (msec) 22 1007Reselection delay via FACH (msec) 0 -Reselection delay via Cell Update (msec) 0 -Reselection delay via RL Recovery (msec) 0 -Reselection delay via RLC Unrecoverable (msec) 0 -Reselection delay via multiple Cell Updates (msec) 0 -Reselection delay vith RAU (msec) 0 -Non-classified cell reselection delay (msec) 1 7864Drop/Fail During Reselection 1

Table 8 – Example of HSPA report summary page

7 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.

Figure 20 – Cluster buffer zone definition




8 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).




8.2.2 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]

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.




Figure 22 – RSCP plot per scrambling code

Figure 23 – Best Server plot per scrambling code




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.




Figure 25 – EcNo plot

Figure 26 – EcNo plot Comparison – Tilting up helps to improve EcNo




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. It’s not acceptable if this is urban cell.

Cell 4377

0

100

200

300

400

500

600

SUM 0

SUM 7

03

SUM 9

37

SUM 1

171

SUM 1

639

SUM 2

107

SUM 2

575

SUM 3

043

SUM 3

745

SUM 4

447

SUM 5

149

SUM 7

021

SUM 8

893

SUM 1

0765

SUM 1

4275

SUM 1

7785

SUM 2

1295

SUM in

finity

Propagation delay, m

Nu

mb

er

of

RR

C S

etu

p R

eq

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.




Figure 28 – Pilot pollution plots

Figure 29 – Pilot Pollution plot with pilot polluter workbook




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




Figure 31 – Call Setup failures caused by measurement tool




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




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




Check for overshooting and interfering sites. See Figure 34.

Figure 34 – Overshooting site causing interference




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

Figure 35 – Sudden Field drop example




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.




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




Table 9 – Throughput report table

Figure 39 – HSDPA throughput distribution example




Figure 40 – HSDPA throughput example with 6 codes used

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




FTP throughput vs CPICH RSCP

0

1000

2000

3000

4000

5000

6000

7000

-110-105-100-95-90-85-80-75-70-65-60-55

CPICH RSCP

FT

P t

hro

ug

hp

ut

HSUPA

QPSK 5 codes

QAM 5 codes

QAM 10 codes

Shannon limit

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




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 toolo Parameter checks & modificationso Capacity issues in Node B or Iubo Core network issues

After Initial drive test exclusion (low coverage) areas must be agreed with the customer and documented.




9 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.




Figure 45 – EcNo distribution comparison between first and second drive test




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)




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


[2] Recommended Parameters.


[3] KPI Guarantees For 3G Networks.


[4] Field measurement tools.

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

[5] SIB 11 limitation


[6] Impact of MHA and Feeder loss settings in WBTS & RNC.


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

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


[9] RAS06_HSPA_Planning Guide.








https://sharenet-ims.inside.nokiasiemensnetworks.com/livelink/livelink?func=ll&objId=364619132&objAction=showdirectlinks&viewType=1&nexturl=%2Flivelink%2Flivelink%3Ffunc%3Dll%26objId%3D358221849%26objAction%3DBrowse








[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:


[12]Actix Scanner Information:


ANNEXES

Attachment 1 - Sample report





RAS06 Pre-Optimization Guide Update 0508

Documents

Transcript of RAS06 Pre-Optimization Guide Update 0508