Hauwei Giang Wcdma Optimization Report

8/10/2019 Hauwei Giang Wcdma Optimization Report

1/56

Drive Test Report 1

DRIVETEST ACCEPTANCE REPORT

HAU GIANG PROVINCE

VMS4 MOBIFONE

Date: Dec-25-2012

ACCEPTED BY:

On behalf of VMS Center 4 On behalf of VTC


2/56

Drive Test Report 2

Table of Contents

INTRODUCTION ..........................................................................................................................5

1. DRIVE TEST PREPARATION .............................................................................................5

1.1. TEST EQUIPMENT SETUP .............................................. .................................................5

1.2. DRIVE TEST ROUTES .............................................. ................................................ ...... 10

2. NETWORK COVERAGE PREDICTION FOR 46 3G SITES IN HAU GIANG .................. 11

2.1. RSCP PLOT PREDICTION FOR HAU GIANG ..... ...... ..... ...... ..... ..... ..... ...... ..... ...... ...... .... ..... 11

2.2. ECIO PLOT PREDICTION FOR HAU GIANG ..... ...... ..... ...... ..... ..... ..... ...... ..... ...... ...... .... ..... 12

2.3. PILOT POLUTION PREDICTION FOR HAU GIANG ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... 13

3. SITE AUDIT HARDWARE CHECK AND ALARM HANDLING ........................................ 13

3.1. SITE DATABASE AUDIT .......................................... ............................................... ....... 14

3.2. HARDWARE CHECK AND ALARM HANDLING..... ...... ...... ..... ...... .... ...... ..... ...... ...... ..... ..... 14

3.3. ANTENNA TILT/AZIMUTH RECOMMENDATION CHANGE REQUEST ...... ...... ..... ...... ..... .... 14

3.4. NEIGHBOR LIST ADD/DEL RECOMMENDATION: ..... ...... ..... ...... ..... ..... ...... ..... ...... ..... ...... 15

4. DATABASE P ARAMETERS CHECK AND OPTIMIZATION RECOMMENDED ............. 17

4.1. PARAMETER GROUPS IN RNC DATABASE:..... ...... ..... ...... ..... ..... ..... ...... ..... ...... ...... .... ..... 17

4.2. PARAMETER GROUPS IN CATEGORIZE..... ...... ..... ..... ...... ..... ...... ..... ...... ..... ..... ..... ...... .... 18

4.3. IDLE MODE PARAMETERS.......................................................................... .................. 18

4.3.1. Idle Mode WCDMA Parameters ............................................ ....................................... 18

4.3.2. Idle Mode GSM Parameters ....................................... ................................................. 21

4.4. SHO PARAMETERS ........................................ ............................................... ............... 22

4.5. INTER-SYSTEM HANDOVER PARAMETERS ..... ...... ..... ...... ..... ..... ..... ...... ..... ..... ...... ..... .... 23

4.6. INTER-FREQUENCY HANDOVER PARAMETERS ...... ...... ..... ...... ..... ..... ..... ...... ..... ...... ...... . 26

4.7. POWER CONTROL PARAMETERS ........................................... ....................................... 27

4.8. PACKAGE SCHEDULING PARAMETERS ..... ...... ..... ..... ...... ..... ...... ..... ...... ..... ..... ..... ...... .... 28

4.9. TELECOM PARAMETERS ............................................... ............................................... 30

4.10. OTHERS PARAMETERS........................................... ............................................... ....... 32

4.11. HSPDA RELATED PARAMETERS ............................................. ....................................... 33


3/56

Drive Test Report 3

4.11.1. HSPDA Power Parameters ............................................ ............................................... 33

4.11.2. HSPDA Dynamic Code Allocation ........................................ ......................................... 34

4.11.3. Other Recommended HSDPA Parameters ..... ...... ..... ...... ..... ..... ..... ...... ..... ..... ...... ..... .... 35

4.11.4. Recommended HSUPA Parameters ...... ..... ...... ..... ..... ..... ..... ...... ..... ...... ..... ..... ..... ...... ... 38

5. NETWORK DRIVE TEST RESULT BEFORE AND AFTER OPTIMIZATION .................. 39

5.1. NETWORK PERFORMANCE OVERVIEW BEFORE AND AFTER OPTIMIZATION .. 39

5.2. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SCANNER 40

5.2.1. RSCP Scan distribution result before and after optimization ...... ..... ...... ..... ..... ..... ...... .... 40

5.2.2. RSCP Scan Coverage plot result before and after optimization........ ...... ..... ..... ...... .... ..... 40

5.2.3. EcIo Scan distribution result before and after optimization ..... ...... ...... ..... ...... .... ...... ..... 41

5.2.4. EcIo Scan Coverage plot result before and after optimization ...... ..... ..... ...... ..... ..... ..... ... 42

5.2.5. Pilot Polution Scan distribution result before and after optimization ..... ...... ..... ...... ...... . 43

5.2.6. Pilot Polution Scan result before and after optimization........ ...... ..... ...... ...... ..... ..... ..... .. 43

5.3. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SHORTCALL 44

5.3.1. RSCP shortcall distribution result before and after optimization ..... ...... ..... ..... ...... ..... .... 44

5.3.2. RSCP shortcall coverage plot result before and after optimization ...... ..... ...... ...... ..... ..... 45

5.3.3. EcIo shortcall distribution result before and after optimization ..... ...... ..... ...... ...... .... ..... 46

5.3.4. EcIo shortcall coverage plot result before and after optimization ...... ..... ...... ..... ..... ..... .. 465.4. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM IDLE MODE 47

5.4.1. RSCP Idle distribution result before and after optimization ..... ...... ...... ..... ...... .... ...... ..... 47

5.4.2. RSCP Idle coverage plot result before and after optimization ...... ..... ..... ...... ..... ..... ..... ... 48

5.4.3. EcIo Idle distribution result before and after optimization....... ...... ...... ..... ...... .... ...... ..... 49

5.4.4. EcIo Idle coverage plot result before and after optimization... ...... ...... ..... ...... ..... ..... ..... . 49

5.5. NETWORK SPEECH QUALITY MOS BEFORE AND AFTER OPTIMIZATION ......... 50

5.5.1. MOS distribution result before and after optimization ..... ...... ...... ..... ...... .... ...... ..... ..... .. 50

5.5.2. MOS coverage plot result before and after optimization ...... ...... ..... ...... ..... ..... ..... ...... ... 51

5.6. DATA THROUGHPUT BEFORE AND AFTER OPTIMIZATION .................................. 52

5.6.1. HSDPA coverage plot result before and after optimization ..... ...... ..... ..... ...... ..... ...... ..... . 52

5.6.2. HSUPA coverage plot result before and after optimization ..... ...... ..... ..... ...... ..... ...... ..... . 53


4/56

Drive Test Report 4

5.6.3. PING coverage plot result before and after optimization.... ..... ...... ...... ..... ...... ..... ...... .... 54

6. CONCLUSION AND RECOMMENDATION .............................................. ........................ 55

7. APPENDIX ............................................ .................................................. ............................ 56


5/56

Drive Test Report 5

INTRODUCTION

This report is the result of the drive test optimization for 46 sites 3G in Hau Giang province to evaluate

network performance KPI.The drive test analysis provides the good information to establish keyrequirements in terms of network coverage for the nominal design.

This report will show the detailed coverage analysis, network quality and network performance for the

agreed drive test routes.The network coverage (Scan Mode & Idle Mode ), Call Setup Success Rate

(CSSR), Drop Call Rate (DCR) speech voice quality (MOS) ,data through put both uplink & downlink for

HSDPA ,HSUPA and time delay (PING) are the main Key P erformance Indicators (KPIs) during the test.

VTC had been assigned 46 sites in Hau Giang province with main scope of work includes

Pre-drivetest with 05 UEs (02 UEs for Idle & dedicated ) and 03 UEs for Data card cover all

accessible route with car,bike & boat

01 Scanner to verify Coverage and Pilot Polution for main road where car can accessible only

MOS speech quality test for main road where car can access ible only

OSS/OMC Statistics collection & Analysis for worse cell KPI

Evaluation of drive test logs

Site Audit & replacement of Faulty Hardware ,VSWR

Physical antenna tilt/azimuth optimization recommendation & implementation of change request

Neighbor audit,Sc rambling Code tuning,Parameters tunning recommended Final report with comparasion pre & post drivetest performance

1. DRIVE TEST PREPARATION

1.1. TEST EQUIPMENT SETUP

The engineers will be able to monitor the performance of the network and provide solutions to

problems encountered. Therefore, main objectives of drive tests are to: check network coverage,Call

Setup Success Rate (CSSR), Drop Call Rate (DCR) speech voice quality (MOS) ,data through put


6/56

Drive Test Report 6

both downlink & uplink for HSDPA ,HSUPA and time delay (PING), monitor if blocked ,call set up

failure or drop call exists, check if actual signal strength coverage in accordance to the planned,

check orientation/tilt/height of antennas, check engineering sites audit and parameters feature

defined in the CDD, check signal quality received and data throughput.

Prior to the actual drive testing of the network, there are some initial preparation tasks that need

to be accomplished.

Create Tems Cell File

Create digital map (e.g.. MapInfo tab file)

Drive Test Route (final routes in Hau Giang)

All major and access ible roads within the intended coverage areas of the concerned site

are required to drive tested.

All major and accessible roads in the area of the site being tested including neighbour cells

as defined in nemo/TEMS cell file.

Equipments Check & Setup (per team)

o 1 Laptop

o 1 GPS (Global Positioning System)

o 1 External antenna for the GPS

o 3 Tems Mobile Phones for short +Idle Call

o 2 Nemo Mobile Phone for MOS Mobile to Mobile Call

o 1 Scanner + External antenna for the GPS

o 3 Data card for HSDPA,HSUPA and PING

o 8 Test SIM Cards

o 1 Power Inverter

Starting


7/56

Drive Test Report 7

Before opening the computer, make sure that all equipments are connected for them to be easily

detected

Engineers should ensure that the TEMS/NEMO Phone setting is always in WCDMA mode

(Except Idle mode must be set to DualMode GSM/WCDMA).

Engineers should ensure that the TEMS/NEMO phone is properly mounted in such a way that the

phone cable will not be disconnected.

Engineers should ensure that the GPS/SCANNER external antenna is properly mounted on top of

the drive test vehicle.

Engineers should ensure that the Command Sequence is ended before stopping the logfile

recording.

Engineers should ensure that during drive test, they cannot pause the recording of the logfile.

Following the command sequence settings for the TEMS mobile phones

MS1: Short call with call duration at 60s and 10s for idle duration between 2 calls.


8/56

Drive Test Report 8

MS2: Idle to measure CPICH & BCCH Coverage

Following the command sequence settings for the NEMO mobile phones

MS1: Make call with call duration at 60s and 10s for idle duration between 2 calls

MS2: Receive Call

Following the command sequence settings for the TEMS Data card

DC1: Data card Download

DC2: Data card Upload

DC3: Data card PING


9/56

Drive Test Report 9


10/56

Drive Test Report 10

1.2. DRIVE TEST ROUTES

The drive test routes for Hau Giang Province have been agreed between VMS4 and VTC. The drive test

results ONLY cover for 46 cells of VMS4 provide to VTC in this area.

Hau Giang Drive Test Routes


11/56


2. NETWORK COVERAGE PREDICTION FOR 46 3G SITES IN HAU GIANG

The following is network coverage base on prediction for 46 sites in Hau Giang in order to comapare withreal drive test result

2.1. RSCP PLOT PREDICTION FOR HAU GIANG


12/56


2.2. ECIO PLOT PREDICTION FOR HAU GIANG


13/56


2.3. PILOT POLUTION PREDICTION FOR HAU GIANG

3. SITE AUDIT HARDWARE CHECK AND ALARM HANDLING

The following information sites database was checked and action done before and duringoptimization activites carried out by VTC


14/56


Items #No Percent (%)

HW Check 21 15.22%

Antenna Tunning 25 18.12%

Cells Audit 138 100.00%

Total Cells 138

3.1. SITE DATABASE AUDIT

Data collected for sites audit includes

Sites Address ( Include details sites address,commune,district & Province) Sites GPS Coordinate longtitude/Latitude Antenna information (Antenna type/Height/Available Antenna Height,Antenna tilt&

Azimuth)

All 46 sites (138 cells) was checked & audited.Please refer to more details information in APPENDIX

3.2. HARDWARE CHECK AND ALARM HANDLING

Total 21 cells was checked for worse cell KPI & HW issues.Please refer to more details informationin APPENDIX

3.3. ANTENNA TILT/AZIMUTH RECOMMENDATION CHANGE REQUEST

Total 25/138 cells was request to change antenna tilt & azimuth to improve coverage.Please referto more details information in APPENDIX


15/56


3.4. NEIGHBOR LIST ADD/DEL RECOMMENDATION:

The following li st is recommendation for Add/Del neighbor cell s.

SourceCell_Name Source_CI Source_SC

NB

Cell_Name NB_CI N_SC RecommedationKGGQ09A 46891 289 HGVT17A 18681 215 Add NB Both 2 wayKGGQ09A 46891 289 HGVT17B 18682 213 Add NB Both 2 wayKGGQ09A 46891 289 HGVT17C 18683 214 Add NB Both 2 wayKGGQ09A 46891 289 HGVT12A 17211 336 Add NB Both 2 wayKGGQ09A 46891 289 HGVT12C 17213 338 Add NB Both 2 wayKGGQ09A 46891 289 HGVY06C 17793 275 Add NB Both 2 wayKGGQ09B 46892 297 HGVT17B 18682 213 Add NB Both 2 wayKGGQ09B 46892 297 HGVT17C 18683 214 Add NB Both 2 wayKGGQ09B 46892 297 HGVT12A 17211 336 Add NB Both 2 wayKGGQ09B 46892 297 HGVT12C 17213 338 Add NB Both 2 wayKGGQ04A 46771 96 HGVT12A 17211 336 Add NB Both 2 wayKGGQ04A 46771 96 KGGQ09B 46892 297 Add NB Both 2 wayHGVY06C 17793 275 HGVT04B 17532 377 Add NB Both 2 wayHGVT04B 17532 377 HGVT17B 18682 213 Add NB Both 2 wayHGVY07A 17711 41 HGVY21B 18452 73 Add NB Both 2 wayHGVY07A 17711 41 HGVY21C 18453 75 Add NB Both 2 wayHGVY07B 17712 42 HGVY09C 17783 10 Add NB Both 2 wayHGVT03B 17392 379 HGVY06C 17793 275 Add NB Both 2 wayHGVY03A 17771 16 HGVY15A 18551 290 Add NB Both 2 wayHGVY03A 17771 16 HGVY15C 18553 291 Add NB Both 2 wayHGVY03C 17773 18 HGVY09B 17782 9 Add NB Both 2 wayHGVY15B 18552 291 HGLM02A 17271 323 Add NB Both 2 way

HGVY15B 18552 291 HGPH03C 17133 87 Add NB Both 2 wayHGVY15B 18552 291 HGLM05A 17231 61 Add NB Both 2 wayHGVY15C 18553 293 HGVY03C 17773 18 Add NB Both 2 wayHGVY15C 18553 293 HGVY09B 17782 9 Add NB Both 2 wayHGLM05A 17231 61 HGVY15B 18552 291 Add NB Both 2 wayHGLM05C 17233 63 HGVY09C 17783 10 Add NB Both 2 wayHGLM02A 17271 323 HGVY15B 18552 291 Add NB Both 2 wayHGCA05A 17011 176 HGPH11C 18523 188 Add NB Both 2 wayHGCA05B 17012 176 HGPH11C 18523 188 Add NB Both 2 wayHGPH08C 17623 319 CTPD15C 10973 314 Add NB Both 2 wayHGPH08C 17623 319 HGCA01C 17063 22 Add NB Both 2 wayHGPH17C 18623 415 HGCA16B 17932 328 Add NB Both 2 wayHGPH17C 18623 415 HGCA16A 17931 320 Add NB Both 2 wayHGPH15C 17343 431 HGPH17B 18622 414 Add NB Both 2 wayHGNB04B 17612 237 HGNB10A 18251 35 Add NB Both 2 wayHGNB04B 17612 237 HGNB10B 18252 36 Add NB Both 2 wayHGNB04B 17612 237 HGNB06A 17831 23 Add NB Both 2 wayHGNB04C 17613 238 HGNB10A 18251 35 Add NB Both 2 wayHGNB10A 18251 35 HGNB04B 17612 237 Add NB Both 2 wayHGNB10B 18252 36 HGNB04B 17612 237 Add NB Both 2 way


16/56


HGNB06A 17831 23 HGNB04B 17612 237 Add NB Both 2 wayHGNB10A 18251 35 HGNB04C 17613 238 Add NB Both 2 wayHGNB10A 18251 35 HGNB03B 17462 329 Add NB Both 2 wayHGNB10A 18251 35 STKS10B 60512 37 Add NB Both 2 wayHGNB10A 18251 35 STKS07C 60013 47 Add NB Both 2 wayHGNB10B 18252 36 STKS07C 60013 47 Add NB Both 2 wayHGNB03B 17462 329 HGNB10A 18251 35 Add NB Both 2 wayHGNB03B 17462 329 HGNB10B 18252 36 Add NB Both 2 wayHGNB03B 17462 329 HGNB06A 17831 23 Add NB Both 2 wayHGNB03B 17462 329 HGNB06C 17833 25 Add NB Both 2 wayHGNB03C 17463 337 HGNB08A 18231 29 Add NB Both 2 wayHGNB03C 17463 337 HGNB08C 18233 31 Add NB Both 2 wayHGNB12A 18281 322 HGNB10C 18253 37 Add NB Both 2 wayHGNB12B 18282 330 HGNB08A 18231 29 Add NB Both 2 wayHGNB06A 17831 23 HGNB04B 17612 237 Add NB Both 2 wayHGNB06A 17831 23 HGNB12A 18281 322 Add NB Both 2 wayHGNB06A 17831 23 STKS07C 60013 47 Add NB Both 2 way

HGNB06A 17831 23 STKS10B 60512 37 Add NB Both 2 wayHGNB06C 17833 25 HGPH24A 17581 224 Add NB Both 2 wayHGPH24A 17581 224 HGNB06C 17833 25 Add NB Both 2 wayHGNB08A 18231 29 HGNB12A 18281 322 Add NB Both 2 wayHGNB08A 18231 29 HGNB12B 18282 330 Add NB Both 2 wayHGNB08A 18231 29 HGNB12C 18283 338 Add NB Both 2 wayHGNB08A 18231 29 HGNB03B 17462 329 Add NB Both 2 wayHGNB08A 18231 29 HGNB03C 17463 337 Add NB Both 2 wayHGNB08A 18231 29 HGNB06C 17833 25 Add NB Both 2 wayHGNB08B 18232 30 HGPH01A 17041 500 Add NB Both 2 wayHGNB08B 18232 30 HGPH01B 17042 501 Add NB Both 2 wayHGNB08B 18232 30 HGPH01C 17043 502 Add NB Both 2 wayHGNB08B 18232 30 HGPH30A 18091 492 Add NB Both 2 wayHGNB08B 18232 30 HGPH30B 18092 493 Add NB Both 2 wayHGNB08C 18233 31 HGPH30A 18091 492 Add NB Both 2 wayHGNB08C 18233 31 HGPH30B 18092 493 Add NB Both 2 wayHGPH30A 18091 492 HGNB08B 18232 30 Add NB Both 2 wayHGPH30B 18092 493 HGNB08B 18232 30 Add NB Both 2 wayHGPH30A 18091 492 HGNB08C 18233 31 Add NB Both 2 wayHGPH30B 18092 493 HGNB08C 18233 31 Add NB Both 2 wayHGNB08C 18233 31 HGPH15B 17342 430 Add NB Both 2 wayHGNB08C 18233 31 HGNB05B 17512 287 Add NB Both 2 wayHGNB08C 18233 31 HGNB05C 17513 280 Add NB Both 2 way

HGNB08C 18233 31 HGNB03C 17463 337 Add NB Both 2 wayHGPH31B 18102 27 HGPH40B 18162 201 Add NB Both 2 wayHGPH31B 18102 27 HGPH05C 17453 390 Add NB Both 2 wayHGCT04C 17473 111 HGNB04A 17611 232 Add NB Both 2 wayHGNB04A 17611 232 HGCT04C 17473 111 Add NB Both 2 way


17/56


4. DATABASE PARAMETERS CHECK AND OPTIMIZATION RECOMMENDED

This part of the document shows the main parameters for optimization purpose. Its alsorecommended to check the lastest release of the WCDMA RAS_XX Parameter Dictionary fromsystem documentation.

Its also recommended to create a database change control procedure, including that, for anyparameter change, it has to be approved, documented and the effect verified afterwards.

Any parameters not described here should not be changed, and always follows therecommended ones.

4.1. PARAMETER GROUPS IN RNC DATABASE :

All the parameters in the database are organized in groups. There are some specific effects inchanging parameters regarding this kind of organization. The groups and the effects are describedbelow:

RNC: these parameters controls all procedures in an RNC level, which means that allcells, users, calls, NodeBs, etc. will be affected by change these kind of parameter.

COCO: these parameters refer to Connection Configuration in the RNC. WANE and WGS: these parameters are related to IMSI based HO. WLCSE and WSMLC: these parameters are related to Location Based Services. WBTS: these parameters are related to the NodeB configuration. Changing parameters

in this group will affect all WCELs related to this WBTS. WCEL: these parameters are related to the cells configuration in the NodeB. FMCSF, MCI and FMCG: these parameters are related to Frequency Measurements for

Intra-System, Inter-Frequency and Inter-RAT (GSM) Handovers respectively. Itconfigures the UE to how /when do the measurements for RNC HO decision. Theseparameters are sent to UE via BCCH SIB messages and DCH Measurement ControlMessages. FMCxs objects are created in the RNC and then associated to the WCELs,which means that changing FMCxs parameters

Will affect all WCELs associated to them. There are 8 FMCxs defaults values created in thedatabase depending on service type and NodeB output power: RT_40W, NRT_40W,HSDPA_40W, RT_HSDPA_40W, RT_20W, NRT_20W, HSDPA_20W and RT_HSDPA_20W. Itspossible to created new FMCxs, and the parameters have to be analyzed and approved by theParameter Experts.

ADJS, ADJI and ADJG: these are the neighbour relations between the NodeB cells forIntra-System Handovers, Inter-Frequency Handovers and Inter-RAT Handovers (GSM)respectively.

HOPS, HOPI and HOPG: these parameters are related to Handover Paths . They areused for configuring the UE for Cell Reselection procedures and used by RNC forHandover decisions for Intra-System, Inter-Frequency and Inter-RAT (GSM) neighboursrespectively. These parameters are sent to UE via BCCH SIB messages. HOPxs objectsare created in the RNC and then associated to the ADJxs, which means that changingHOPxs parameters


18/56


will affect all ADJxs associated to them. There are 4 HOPxs defaults values created in thedatabase depending on service type: RT, NRT, HSDPA and RT_HSDPA. Its possible to creatednew HOPxs, and the parameters have to be analyzed and approved by the Parameter Experts.

Pls be noted that each modification should be evaluated on a case-by-case basis, taking intoaccount the local environnement and target network configuration

4.2. PARAMETER GROUPS IN CATEGORIZE

Idle more WCDMA/GSM parameters

Mobility

o Soft HO Parameters

o Inter-System handover parameters

o Inter-Frequency handover parameters

RRM

o Admission control parameters

o Packet Scheduling parameters

o Telecom Parameters

o Power Control parameters

HSDPA (RAS05 onwards) and HSUPA (RAS06 onwards) parameters

It is possible to view/modify all listed 3G parameters using RNC RNW Object Browser. There arealso some GSM parameters which have to be modified from BSC (MML commands).

3G network topology is varying a lot which means that the radio network optimization activitieswill be needed anyway to improve the radio network performance. Thus these parameters areonly better defaults to start the optimization

4.3. IDLE MODE PARAMETERS

4.3.1. Idle Mode WCDMA Parameters

Idle mode parameters should be optimized to improve the call setup success rate.

Parameter Object Defaultvalues

Optimizedvalues

Comments


19/56


QqualMin WCEL -18dB -18dB The minimum required quality level in the cell(Ec/No) for UE cell reselection. This parameter hasalso impact to in itial cell selection if its set with lowvalue. With high value unnecessary cell selectioncan start. This parameter is sent to UE over theBCCH SIB messages.

QrxlevMin WCEL -115dBm -115dBm The minimum required RX level in the cell (RSCP)for UE cell reselection. This parameter is also usedto create value for the parameter DeltaQrxlevmin tobe sent in SIB3/4 when the used value is < -115dBm. This parameter is sent to UE over theBCCH SIB messages.

Qhyst2 (Cellresectionhysteresis 2)

WCEL 2 dB 4 dB

2 dB

0 dB

4dB for WCDMA cells near different LA can beused to avoide ping-pong effect and also for lowmobility UEs unless compensated by AdjsQoffset2(per adj)

2 dB hysteresis between WCDMA cells can beused in Urban environment to avoid ping pong.

2dB (or less) enables faster cell reselection, whichcan contribute to improve HSDPA accessability.

0 dB hysteresis can be used in the area of highmobility.

Cell reselectiontriggering time(Treselection)

WCEL 2 s 2 s

0 s

2s reselection time helps avoid too many cellreselections between cells and hence LA/RA updateswhen crossing LA/RA border. Thus there are lesssignaling and less call failures at LA/RA border due toLA/RA update.

0s can be used in areas having high mobility like inhighways.


20/56


AdjsQoffset1 HOPS 0dB This parameter is used in the cell re-selection and

ranking between WCDMA cells. The value of this

parameter is subtracted from the measured CPICH

RSCP of the neighbour cell before the UE comparesthe quality measure with the cell re-selection/ranking

criteria.

AdjsQoffset2 HOPS 0dB This parameter is used in the cell re-selection and

ranking between WCDMA cells. The value of this

parameter is subtracted from the measured CPICH

RSCP of the neighbour cell before the UE compares

the quality measure with the cell re-selection/ranking

criteria.

AdjsQqualMin HOPS -18dB Determines the minimum required CPICH Ec/No level

which must be exceeded by the measurement result of

the neighboring cell before the cell re-selection

becomes possible.

AdjsQrxlevMin HOPS -115dBm Determines the minimum required CPICH RSCP level

which must be exceeded by the measurement result of

the neighboring cell before the cell re-selection

becomes possible


21/56


AdjgRxLevMinHO

HOPG -95dBm This parameter determines the minimum required GSM

RSSI level which the averaged RSSI value of the GSM

neighbour cell must exceed before the coverage (or

quality) reason handover to GSM is possible

AdjgQrxlevMin HOPG -101dBm Determines the minimum required RSSI level which the

measurement result of the GSM neighbour cell must

exceed before the cell re-selection becomes possible

AdjgQoffset1 HOPG 0dB This parameter is used in the cell re-selection and

ranking between WCDMA and GSM cells. The value of

this parameter is subtracted from the measured GSM

carrier RSSI of the neighboring cell before the UE

compares the quality measure with the cell re-selection/

ranking criteria

AdjSSIB

AdjGSIB

AdjISIB

ADJS

ADJG

ADJI

1

1

1

0

0

0

All the neighbour cells are included into syst em

information block (SIB11/12) by default. The

parameters are set by the system to the default value 1

(yes). The value must be set to 0 for marginally used

adjacencies if the total amout of neighbours for a given

cell exceeds the SIB11 limit (typically 47 adjacencies).

It is preferable to avoid removing intra-frequency

adjancencies

4.3.2. Idle Mode GSM Parameters


22/56


Parameter Object Default Recommendedvalue

Comments

MINIMUM FDD THRESHOLD(Fdd_Qmin)

BTS 0 (-20 dB) -6..-10 dB Should be balanced withQqualMin and SsearchRAT toreduce ping-pong. 6-8 dB

hysteresis recommended (ifQqualmin+ SsearchRAT=-16,Fdd_Qmin= -8 dB,

Note: actual value based onUE interpretation.

Non GPRS Multi RAT MS Qual(QsearchI) (GSM), QSRI

GPRS Multi RAT MS Qual

(QsearchP) (GSM), QSRP

BTS 15 (no meas) 7 (=always) UE will measure always 3Gcells if they are definedneighbours. On the other hand

this will have effect to the UEbattery life time.

Multi RAT MS Qual(QsearchC), QSRC

HOC 15 (no meas) 7 (=always) If set to 15 MeasurementInformation (MI) is sendanyway (even though UEshould not measure 3Gneighbours with that value 15),if ISHO_SUPPORT_IN_BSCor EMR_SUPPORT_IN_BSCfeatures are used.

Note: In case ISHO_SUPPORT_IN_BSC or EMR_SUPPORT_IN_BSC features are used the parametervalues set with QSRI, QSRP or QSRC do not affect to the Measurement Info message and MI is alwayssend by Mobile. This is valid in S10.5, S10.5 ED and S11. Only if both features are not used, MI info isnot send.

4.4. SHO PARAMETERS

Note: From RAS05 onwards, the default system value for FMCS parameters is equivalent to the optimalrecommendation. However in there are some modifications needed.


23/56


Several customers use 4 FMCS sets: for RT, NRT traffic, HSPA and AMR+ HSPA.

RT traffic uses default set of values of (4,6,2) dB for (Addition, Drop and Replacement Window) values,respectively

NRT traffic uses default set of values of (2.5,4,2) dB for (Addition, Drop and Replacement Window) values,respectively

Parameter Object Defaultvalues

Recommendedvalues

Comments

DropreportingInterval FMCS 0.5s 1s This is to related to first observations aboutSRB blocking -> decrease signaling with thischange

ReplacementReportingInterval

FMCS 0.5s 1s This is to related to first observations aboutSRB blocking -> decrease signaling with thischange

ReplacementWindow FMCS 2 dB 4-6 dB priorizes branch additions over branchdeletions to enable fast addition of new celland decrease call drop rate, Current defaulttrigger setting of SHO event 1C causesplenty of events to be reported -> SRBblocking

ReplacementTime FMCS 100ms 640ms SRB Blocking, see above.

4.5. INTER-SYSTEM HANDOVER PARAMETERS

Parameter Object Default values Recommendedvalues

Comments

GSM HO caused by CPICHEc/No

FMCG Disabled Enabled

GSM HO caused by CPICHRSCP


GSM HO caused by UE TxPower



24/56


UE TX Power Filter Coefficient FMCG 10 ms 60 ms In case GSM HO caused byUE Tx Power is enabled.

10 ms, too short delay totrigger ISHO.

Consider using longer period,at least 60 ms.

GSM HO caused by DL DPCHTX Power

FMCG Disabled Enabled Some Ues are performingISHO under good RFconditions due to peaks of highBLER, so DL power should beenabled to avoid dropped call.

Maximum Measurement

Period

FMCG 6 measurement

reports

12

measurementreports to 20measurementreports

ISHO delays of 5 s has been

measured, also the delaydepends on the length ofneighbour list.

Decreases the probability forno cell found in ISHO.

6 is often too low inenvironment where 2G BCCH

reuse is high.

It is recommended to use atleast 12.

Handover of NRT PS Serviceto GSM

RNC/HC&PC

No Yes In case PS ISHO is activated

FMCG needs to be added incell parameter window.


25/56


Maximum Allowed UL UserBitrate in HHO

WCEL 32 kbits/s 384 kbits/s Used only with high UE TXpower level (RT&NRT) or baduplink DCH quality triggers.

In case of bad uplink DCHquality, the bitrate thresholdconcerns only RT data (CS orPS) connections.

This parameter value shouldbe aligned withMaxBitRateULPSNRT, whichis by default 384 kbits/s inRAN04 / RAS05.

The RNC is not aware of whichTF the UE is using.

CPICH Ec/No HHO Threshold,CPICH Ec/No HHO Cancel,CPICH RSCP HHO Threshold,CPICH RSCP HHO Cancel forNRT Services

FMCS

NRT,

FMCSHSDPA

-12dB,

-9dB,

-105dBm,

-102dBm

-16..-18 dB,

-12..-14 dB,

-115dBm,

-110dBm

Lower values for for NRTservices to increase thecoverage area, valid forHSDPA also.

Due the signalling delays atinter-system change causedby LU and RAU, and due tothe low bit rate available inGPRS network without EDGE,it is beneficial to leave UMTSas late as possible

CPICH Ec/No HHO Threshold,CPICH Ec/No HHO Cancel,CPICH RSCP HHO Threshold,CPICH RSCP HHO Cancel forNRT Services

FMCSRT

-12dB,

-9dB,

-105dBm,

-102dBm

-14..-16 dB

-10..-12 dB

-108..-110 dBm

-105..-18 dBm

Lower values for RT to havemore coverage.

Absolute Isho number (and

ISHO) drops will bedecreased.


26/56


DedicatedMeasReportPeriod WBTS 2.5 s 0.5 s This parameter determines thereporting interval that Node Bshould use (by default, wheninitialized) for sendingdedicated measurementreports to the RNC related thepower on DCH channel.

When ISHO Downlink LinkPower trigger is in use,reducing this parameter to 0.5seconds allows faster ISHOand can help reduce drop rate.

Requires cell locking prior tochange.

4.6. INTER-FREQUENCY HANDOVER PARAMETERS

Parameter Object Default values Recommendedvalues

Comments

IFHO caused by CPICH Ec/No FMCI Disabled Enabled

IFHO caused by CPICH RSCP FMCI Disabled Enabled

IFHO caused by UE TxPower FMCI Disabled Enabled

UE TX Power Filter Coefficient FMCI 10 ms 60 ms In case IFHO caused by UE TxPower is enabled (see above).

10 ms, too short delay totrigger IFHO.

Consider using longer period,at least 60 ms.

Maximum MeasurementPeriod

FMCI 20 meas report 12 meas report This should be in line withISHO delay.


27/56


4.7. POWER CONTROL PARAMETERS


Comments

PtxPrimaryCPICH WCEL 33dB 20W

36dB - 40W

This is the transmission powerof the primary common pilotchannel and its defined as10% of the total NodeB TxPower. . For 20W NodeB isconfigured as 33dBm, and for40W NodeB is configured as36dBm. The P-CPICH physicalchannel carries the commonpilots of the cell, which isdefined in the cell setup. Thetransmission power of the

CPICH physical channeldefines the actual cell size, sofor optimization purpose likesolving Pilot Pollutionproblems and CPICHImbalance problems thisparameter could be changed0-3dB maximum range. Thisparameter is used, forexample, for neighbourmeasurements, critical for thenetwork performance. All othercontrol and signaling channelstransmission powerparameters are related toPtxPrimaryCPICH.

CPICHtoRefRABoffset (Offsetof the P-CPICH and referenceservice powers)

WCEL 2 dB 0 dB

-1 -2 dB (withhigh HSDPAtraffic)

This change means that themaximum link power for aconnection is increased by 2dB to improve the DLcoverage. This change meansalso that the minimum power isincreased as well (as theminimum power is Max power

DL PC Range) which mightlead to the situation where toohigh powers are allocatedeven in the good coverageconditions as a result power iswasted.


28/56


With high HSDPA traffic theincreased interference willdecrease the EcNo level,which could mean increasedpeak power for AMR, thus maxradio link power for AMRshould be increased also.

PcrangeDL (Radio linkdownlink power control range)

RNC 15 dB 20 dB This change is needed tocompesate the increase ofCPICHtoRefRABoffsetmentioned above.

21-22 dB can be used withnegativeCPICHtoRefRABOffset

Required received C/I onPRACH at WCDMA BTS

WCEL -25 dB -20..-18 dB With increased traffic and thefluctuation of noise levels thedefault value -25 just leads tounnecessary unansweredRRC connections or pages i.e.no response from BTS to RRCConnection Request (i.e. no

AICH). This can be avoided byadjusting the parameter to -20dB. This has not anynegative impact such asincreased noise level or

spikes.

4.8. PACKAGE SCHEDULING PARAMETERS


Comments

MSActivitySupervision (MSactivity supervision timer)

(Time supervision of userinactivity (for NRT RBs))

RNC 29 min 15 min MSActivitySupervision timer isused in Cell_PCH state forsupervising the inactivity of

NRT RAB(s). If the parametervalue is set to zero: statetransition to Cell_PCH is notallowed when inactivity isdetected in Cell_FACH stateand the MS will be switched tothe Idle Mode.


29/56


PtxDLabsMax (Plannedmaximum downlinktransmission power of a radiolink)

WCEL 37 dBm 35-37 dBm This parameter is related to theDynamic Link Optimizationfeature. It will limit the plannedmaximum limit for the radiolink.

Bitrate downgrade due to DyLohappens if the current linkpower is 2 dB (fixed value) lessthan maximum link power.However with this parameter itis possible to optimize the NRTusage in different bitrates. Theoptimised value foPtxDLAbsMax is between 35-37dBm based on the variousmeasurements.

Offset for activation time

StandAloneDCCHBitRate

RNC

RNC

300ms 500..700 ms

13.6kbps

The RB setup success is betterwith longer time in badcoverage areas. As SignallingDelay Improvement isimplemented in RAS5, shorter

Activation Time Offset canpotentially be used.

Configuring to 300ms woulddecrease the setup time by400ms for each leg, butdeclines the Call SetupSuccess Rate of 0.2-0.4%. Soin case this parameter ischanged the effects to callsetup time and call setupsuccess rate has to beobserved from counters .

For full improvement in callsetup time the SRB size shouldbe set to 13.6 kbps. SRB 13.6gives approximately 1-2 secfaster call setup time and gives30% faster GPRS attach timeand PDP activation time thanSRB 3.4, but also requiresmore capacity on Iub during


30/56


500 ms

the call setup phase

500 ms has been tested withsuccess in some cases. Needs

to be evaluated case-by-casebased on Ue mix in network.

Can impact Packet RAB droprate and AMR/Video RABsetup success rate.

MinAllowedBitRateDL/UL

(Initial and minimum allowedbit rate in DL/UL)

WCEL Uplink 8 kbit/s

Downlink 8kbit/s

UL/DL 8..32kbit/s

Optionally consider usingrecommended values: UL/DL =32/32 kbits/s. This is due to lowthroughput on FTP type ofservices by using TCP. If there

are some TCP re-transmissions, these can causelarge queue of TCP framesbuffered in RLC and thenpushed to higher layer. Sincedownlink TCP frames arereceived faster than feedbackchannel is able to transmitsTCP acks, throughput willsuffer.

Initial bit rate in downlink/uplink WCEL 64 kbits/s 8 or 16 kbits/s In loaded networks it may be

useful to use lower initialbitrates

4.9. TELECOM PARAMETERS


Comments

Cell range WCEL Default value isnot possible

10 km or 20 km The maximum cell range canbe 20 km when using twoantennas and AICHTransmission Timing has value1. If AICH TransmissionTiming has value 0 or fourantennas are used themaximum value can be 10 km


31/56


PRACH Preamble RetransMax

WCEL 8 7 These parameters makesRACH procedure slightlylonger, giving the BTS moretime to catch the RACH, at thesame time decreasing themaximum power used inPRACH power ramping.

If this change is not made,there may be a risk forexcessive peaks in the uplinkcell load when operating at ahigh load (>40 AMR calls)

RACH maximum number ofpreamble cycles

WCEL 8 16

Wait Time RRC registration RNC 1s 5s The time indicates the howlong UE shall wait beforesending the same RRCconnection request messageto the same cell.This changemeans to decrease thenumber of RRC pollution,useful with high load cells also.

Wait Time RRCinteractive/background

RNC 5s 8s This is similar to aboveindicating the RRC wait timedue to NRT blocking. When

AC has rejected call, PS is thelowest priority with the mostconsuming resource. Minimise

the chance for NRT call toattempt is recommended.

T3212 RNC 0 decihours 6h The value depens how it is setin VLR/CN. It is recommendedto be half of the value ofVLR/CN. Default value in VLRis 12 h.

T313 WCEL 3s 6-8s In some case, can reduce NRTcall drop rate (in OSS KPI) by

allowing more time before Uesends Radio Link Failureindication. Note that end userexperience is likely notimproved.


32/56


N313 WCEL 20 50 In some case, can reduce NRTcall drop rate (in OSS KPI) byallowing more time before Uesends Radio Link Failureindication. Note that end userexperience is likely notimproved.

T315 WCEL 4 (180 s) 1 (10 s) It has been observed that afew terminals were in somecase unable to perform a 2Greselection before the expiry oftimer T315. Reducing timer to10s minimizes the impact whilemaintaining PS dropperformance.

4.10. OTHERS PARAMETERS


Comments

StandAloneDCCHBitRate(Signallingradio bearerbit rate at RRCconnectionestablishment)

RNC 34 (3.4 kbps), 136 (13.6 kbps) The parameter UsedSRBALCSet (Used SRB ALC set) allows to useStandAloneDCCHBitRate=13.6 kbit/s toreduce call setup delays without impact onIub AAL capacity by defining an activityfactor. Default value for UsedSRBALCSet is3, which corresponds to an activity factor of7.5% for a StandAloneDCCHBitRate of 13.6kbps.

Parameter Object Default Recommended

Value

Comments

DRRCprxMargin WCEL -0.5 dB 0 dB Directed RRC connection Setup parameter ;based on field measurements, target celldoes not need to be at lower load in UL

DRRCptxMargin WCEL - 2 dB -0.5 dB Directed RRC connection Setup parameter ;based on field measurements, easier accessto another frequency especially in the casefor 384 kbits/s service


33/56


NbrofSCCPCHs WCEL 1 3 3 is the value if Service Area Broadcast(SAB) is used

NforCTCH WCEL 2 4 This value should be used here ifNbrofSCCPCHs is 3.

ConfAreaLevel WSMLC 0100% 67 % This is related to LCS (=location basedservices. There is no default value mentionedfor this, but 67 % is given value from productline.

Note: All other LCS parameters should becarefully set, for example all those Antennarelated parameters, to have accurate LCSresults.

4.11. HSPDA RELATED PARAMETERS

4.11.1. HSPDA Power Parameters

The most important BTS power related parameters are summarized in the table below for 8, 20 and 40WPA per cell configuration. Target values are given with and without optional feature HSDPA DynamicResource Allocation.

DefaultPtxCellMax 43 43 46 39 43 46 39 dBm

20.0 20.0 39.8 7.9 20.0 39.8 7.9 W

PtxCPICH, dBm 33 33 36 29 33 36 29 dBmPtxTarget 40 42 45 38 42 45 38 dBm

PtxTarget (in Watts) 10.0 15.8 31.6 6.3 15.8 31.6 6.3 W

PtxOffset 1.0 0.8 0.8 0.8 0.8 0.8 0.8 dBmPtxTarget+PtxOffset (in Watts) 12.6 19.1 38.0 7.6 19.1 38.0 7.6 W

Dynamic resource a l loca t ion (RAS06) PtxTargetPSMin 36 36 39 32 36 39 32 dBm

PtxTargetPSMin (in Watts) 4.0 4.0 7.9 1.6 4.0 7.9 1.6 W

PtxTargetPSMax 40 42 45 38 40 43 36 dBmPtxTargetPSMax (in Watts) 10.0 15.8 31.6 6.3 10.0 20.0 4.0 WMin. power available for HSDPA 10.0 4.1 8.2 1.6 10.0 19.9 4.0 W

PtxHighHSDPAPwr 42 42.5 45.5 38.5 42 45 38 dBmPtxHighHSDPAPwr (in Watts) 15.8 17.8 35.5 7.1 15.8 31.6 6.3 W

Dynamic Power al locat io n (RAS5.1-RAS06) PtxMaxHSDPA 38.5 42.0 45.0 38.0 42.0 45.0 38.0 dBm

PtxMaxHSDPA (in Watts) 7.1 15.8 31.6 6.3 15.8 31.6 6.3 WPtxTargetHSDPA 37.8 40 43 37 40 43 37 dBm

PtxTargetHSDPA (in Watts) 6.0 10.0 20.0 5.0 10.0 20.0 5.0 W

PtxOffsetHSDPA 0.8 0.8 2 0.8 0.8 2 0.8 dBmPtxTargetHSDPA+PtxOffsetHSDPA (in Watts) 7.2 12.0 31.6 6.0 12.0 31.6 6.0 WMin. power available for HSDPA 7.1 7.9 8.2 1.9 7.9 8.2 1.9 W

Shared HSDPA carrier Dedicated HSDPA carrier

Figure 1: Recommended HSDPA powe r setting for different PA powers.


34/56


Note 1. The full BTS Power Amplifier power can be allocated in downlink without margin, for optimalcapacity performance. However, some operators privilege more conservative allocation. ParameterWCEL:PtxCellMax has a default value of 43 dBm, and it MUST be adapted to the BTS PAs. In case ofMetrosite BTS, the value MUST be set to 39dBm (or less), as it will not be set automatically by thesystem. The same rule applies to Ultrasite and Flexi BTS with 40W PAs: the PtxCellMax value must beset to 46dBm to benefit from the full PA power range. In RU10 BTS link adaptation reduces HS-PDSCHpower for low data rate users and users who are in good radio conditions.

Note2. PtxMaxHSDPA parameter in RAS06 does have an impact on Dynamic Resource allocation also,so it should be set higher value or even equal to PtxCellMax, to allow all left over power for HSDPA withDRA.

If Dynamic Resouce Allocation feature is activated, default values for parameter PSPtxTargetPSMin andPSPtxTargetPSMax is 40dB and must be lowered in case of Metrosite BTS or Flexi 8W license to respect

the maximal value for these configurations (39dBm).

In case of Dedicated carrier configuration, RRC layering must be activated.

4.11.2. HSPDA Dynamic Code Allocation

Parameter Object Default RecommendedValue

Comments

HSPDSCHMarginSF128 WCEL 8 0-4 This parameter will be used onlywith HSDPA 10 or 15 codefeature. The parameter defines

the required number of freeSF128 channelisation codes leftfor DPCHs. The number of freeDPCH codes after the HS-PDSCH code upgrade has to beequal or higher than theparameter value, otherwise theHS-PDSCH code upgrade is notallowed. Also, if the number offree DPCH codes is lower thanthe value of the parameter,periodical HS-PDSCH codedowngrade can be initiated.

Minimum margin of 5 SF128codes allows the allocation of upto 14 HS-PDSCH codes.


35/56


HSUPA + 15 codes is possiblewith value 0 and with 2 HS-SCCH. If HSPA with highthroughput is favoured insteadof PS NRT value 0 can be used.

DPCHOverHSP DSCHThreshold WCEL 0 1-4 NRT DCH connections can pre-empt codes allocated to HSDPAbut in this case, the pre-emptioncan happen in case there isroom in codes: # HS-PDSCHcodes > Maximum code set-DPCHOverHSPDSCHThreshold

parameter. This parameter isapplied if there are activeHSDPA connections in the cell.

If this is set to zero thre will bemore RRC setups with RT overNRT pre-emption which causesthen BTS to be frozen andduring the pre-emption all newrequests to be queued which inturn can cause some delays toRRC setups and queue overflow

and therefore rejections.

HSPDSCHAdjustPeriod RNC 10s 5s Faster adjustement periodallows faster code allocation toHSDPA users.

4.11.3. Other Recommended HSDPA Parameters

Parameter Object Default RecommendedValue Comments

HSDPARRCdiversity

(SHO of HSDPA capableUE)

RNC Allowed Not allowed Only if HSDPA Serving Cell Change isdisabled.

When Not Allowed, parametersReleaseMarginAverageEcNo andReleaseMarginPeakEcNo are used to


36/56


define threshold for neighbouring cell tobe added in to active set while havingonly SRB

AdditionTime FMCS(HSDPA

Id)

6 (100ms) 13 (1280ms) Only if HSDPA Serving Cell Change isdisabled.

AdditionWindow FMCS(HSDPAId)

2.5 dB 0 dB If HSDPA Serving Cell Change isenabled, it is beneficial to delay themeasurement report in order to maintainHSDPA service longer. Also due tocapacity reasons it is recommended toset window as 0 dB to to save BTSWSPC capacity in the target cell. Thisdoes not have impact to the HSDPAthroughput degradation during SCC.

EnableRRCRelease HOPS(HSDPAId)

0 (No) 1 (Yes) With this parameter (with HSDPA onalso) it is possible to see PS droppedcalls due to BTS: lack of WSPC CE.

ReleaseMarginAverageEcNo

HOPS(HSDPAId)

2.5dB 2dB This set will allow shorter time beforeRRC release: WSPC CE savings.

DynUsageHSDPAReturnChannel

RNC 0(Disabled)

1 (Enabled) In case of high UL Channel Elementusage, it is recommended to allow theuse of ThroughputBasedOptimization forthe HSDPA UL return channel. Note thatboth Throughput Based Optimization andFlexible Uprade features need to beenabled.

HSDPA16KBPSReturnChannel

RNC 0 (disabled) 1 (Enabled) This parameter change will improveHSPDA accessibility and maintain theRAB with lower throughput (RBdowngrade) without releasing it in case ofcapacity problems.

Initial bitrate for HSDPAassociated UL DCH

RNC 64 kbits/s 16 kbits/s In loaded networks it is recommended touse lower Initial bitrate in order to savecapacity.

HSDPAminAllowedBitrateU

RNC 64 kbits/s 16 kbits/s In loaded networks it is recommended touse lower Initial bitrate in order to savecapacity.

MaxBitRateNRTMACDFlow

RNC 3456 kbps 3456kbps For basic HSDPA 5 Codes(QPSK/16QAM),


37/56


6784kbps

9600 kbps

MaxBitRateNRTMACDFlow=3456kbps

For basic HSDPA 10/15 Codes,MaxBitRateNRTMACDFlow=6784kbps

For HSDPA 10Mbps per User,

MaxBitRateNRTMACDFlow=9600 kbps.

Code Tree Usage WCEL 40 % 60 % This is the default without HSDPAfeature. With HSDPA enabled in the cellthe code tree usage is already about 38%. The recommendation is to use 60 %.

AM RLC maxRSTtransmissions for PS NRTwith HS-DSCH (theamount of RESET PDUs)

RNC 12 24 This parameter defines the value of theRLC protocol parameter MaxRST for the

AM RLC entity of the PS interactive andbackground radio bearers when data istransferred over HS-DSCH. It has been

hidden parameter before RAS06.

The change will have less RL failures andimproved HSDPA retainability .

RLC unrecoverable error with newsettings = 15*300ms+24*300ms = 11.7s

RLC unrecoverable error with old settings= 15*200ms+12*200ms = 5.4s

The reason for increasing the timervalues for PS NRT is to reduce thepropability that the RLC does theunrecoverable error due to theretransmissions by reducing the RLCpolling frequency.

AM RLC status periodmax for PS NRT with HS-DSCH (periodic pollingand reset polling repeatinterval from 200 to300ms)

RNC 133 % 300 % This parameter defines the maximumstatus reporting period of the AM RLC inrelation to the RLC round trip time for thePS interactive and background radiobearers when the data is transferred overHS-DSCH. It has been hidden parameterbefore RAS06.


38/56


The change will have less RL failures andimproved HSDPA retainability.

AM RLC status periodmax for PS NRT withDCH (periodic polling and

reset polling repeatinterval from 200->300/400/500 msdepending on TTI length,300ms in HSDPA returnchannel case)

RNC 140 % 300 % This parameter defines the maximum AMRLC status reporting period of the AMRLC in relation to the RLC round trip time

for the PS interactive and backgroundradio bearers when data is transferredwith DCH. Hidden parameter beforeRAS06.

AM RLC MaxRSTtransmissions for PS NRTwith DCH (the amount ofRESET PDUs)

RNC 12 24 This parameter defines the value of theRLC protocol parameter MaxRST for the

AM RLC entity of the PS interactive andbackground radio bearers when data istransferred with DCH. Hidden parameterbefore RAS06.

AM RLC maxRSTtransmissions for PS NRTwith E-DCH

RNC 12 24 RLC parameter for HSUPA

AM RLC status periodmax for PS NRT with E-DCH

RNC 133 % 300 % RLC parameter for HSUPA

4.11.4. Recommended HSUPA Parameters

Parameter Object Default RecommendedValue

Comments

MaxTotalUplinkSymbolRate

WCEL 1920 kbps 3840 kbps In case HSUPA2.0 is used

FactorEDCHMaxBitRate RNC 1.5 5 In case HSUPA2.0 is used, to avoidhaving HLR as limiting factor in HSUPAthroughput

NumberEDCHReservedSHOBranchAdditions

WCEL 2 0-1 With default of 2 used with 3 HSUPAlicense only it is not possible to havemore than one HSUPA connection in thecell in case of HSUPA SHO.


39/56


Delay ThresholdMax RNC 8 ms 100 ms HSUPA cong. Control.

Delay ThresholdMid RNC 4 ms 70 ms HSUPA cong. Control.

Delay ThresholdMin RNC 1 ms 50 ms HSUPA cong. Control.

ProbabilityFactorMax RNC 0.8 0.1 HSUPA cong. Control.

5. NETWORK DRIVE TEST RESULT BEFORE AND AFTER OPTIMIZATION

5.1. NETWORK PERFORMANCE OVERVIEW BEFORE AND AFTER OPTIMIZATION

Table below summarizes main drive test KPIs for Hau Giang province before and after optimizationactivities

ITEMS BEFORE AFTER

STATISTICS DATA

#Call Attempts 2224 1467

#Call Setup Successes 2203 1463

#Dropped Calls 17 1

KPI BEFORE AFTER

CSSR(%) 99.06% 99.73%

DCR(%) 0.77% 0.07%

MOS 3.16 3.52

PILOT POLLUTION (COUNT >=4) 5.59% 5.52%RSCP Scan (dBm) -85.69 -73.88

RSCP Shortcall (dBm) -86.16 -84.00EcIo Scan (dBm) -7.11 -6.93EcIo Shortcall (dBm) -5.63 -5.77HSDPA (Kbit/s) 3010 3002HSUPA (Kbit/s) 619 916PING (ms) 200 197


40/56


5.2. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SCANNER

5.2.1. RSCP Scan distribution result before and after optimization

Scan RSCP Before After

Average Coverage (dBm) -85.69 -72.65

5.2.2. RSCP Scan Coverage plot result before and after optimization

RSCP Scan before


41/56


RSCP Scan After

5.2.3. EcIo Scan distribution result before and after optimization

Scan EcIo Before AfterAverage Coverage (dBm) -7.11 -6.9


42/56


5.2.4. EcIo Scan Coverage plot result before and after optimization

EcIo Scan before

EcIo Scan After


43/56


5.2.5. Pilot Polution Scan distribution result before and after optimization

Pilot Pollution Before AfterPilot Pollution count >=4 5.59% 5.52%

5.2.6. Pilot Polution Scan result before and after optimization


44/56


Pilot Polution before

Pilot Polution After

5.3. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SHORT CALL

5.3.1. RSCP shortcall distribution result before and after optimization

ShortCall RSCP Before AfterAverage Coverage (dBm) -86.16 -84


45/56


5.3.2. RSCP shortcall coverage plot result before and after optimization

RSCP Shortcall before

RSCP Shortcall After


46/56


5.3.3. EcIo shortcall distribution result before and after optimization

ShortCall EcIo Before AfterAverage Coverage (dBm) -5.63 -5.77

5.3.4. EcIo shortcall coverage plot result before and after optimization

EcIo Shortcall before


47/56


EcIo Shortcall After

5.4. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM IDLE MODE

5.4.1. RSCP Idle distribution result before and after optimization

Idle RSCP Before AfterAverage Coverage (dBm) -86.21 -81.82


48/56


5.4.2. RSCP Idle coverage plot result before and after optimization

RSCP Idle Before

RSCP Idle After


49/56


5.4.3. EcIo Idle distribution result before and after optimization

Idle EcIo Before AfterAverage Coverage (dBm) -5.67 5.7

5.4.4. EcIo Idle coverage plot result before and after optimization

EcIo Idle Before


50/56


EcIo Idle After

5.5. NETWORK SPEECH QUALITY MOS BEFORE AND AFTER OPTIMIZATION

5.5.1. MOS distribution result before and after optimization

MOS Before AfterSpeech Quality 3.16 3.52


51/56


5.5.2. MOS coverage plot result before and after optimization

Speech Quality MOS before

Speech Quality MOS After


52/56


5.6. DATA THROUGHPUT BEFORE AND AFTER OPTIMIZATION

5.6.1. HSDPA coverage plot result before and after optimization

HSDPA Throughput Before

HSDPA Throughput After


53/56


5.6.2. HSUPA coverage plot result before and after optimization

HSUPA Throughput Before

HSUPA Throughput After


54/56


5.6.3. PING coverage plot result before and after optimization

PING Time delay Before

PING Time delay After


55/56


6. CONCLUSION AND RECOMMENDATION

The result has indicated that network KPIs are improved significantly,however there are some areas needto add more 3G sites to improve network coverage,capacity and data throughput.The detail sites nameand location is summarized in figure below.These areas had already 2G sites installed.

STT TN TRM ID TNH QUN/HUYN X/PHNG/TH TRN LONG LAT

11 11 11 11 11 11 11 11

1 HG Ci Tc 3 HGCA03 Hu Giang Chu ThnhA Ci Tc 105.72584 9.924

2 HG Chu Thnh A HGCA04 Hu Giang Chu ThnhA Mt ngn 105.63409 9.921

3 Hu Giang 87 HGCA15 Hu Giang Chu ThnhATn PhThnh 105.73108 9.946

4 Hu Giang 95HGCA16

Hu Giang Chu ThnhA

Tn PhcThnh

105.72021 9.923

5 HG Long Bnh HGLM05 Hu Giang Long M Long Bnh 105.57704 9.7386 HG Ng By 1 HGNB01 Hu Giang Ng By Li Hiu 105.81017 9.8057 Hu Giang 157 HGNB14 Hu Giang Ng By Hip Li 105.78732 9.8488 HG Tn Long 2 HGPH12 Hu Giang Phng Hip Tn Long 105.76601 9.88309 HG V Thanh 8 HGVT08 Hu Giang TP.V Thanh Phng 3 105.46001 9.775

10 HG Hu Giang 97 HGCA17 Hu Giang Chu ThnhA

Tn Thun 105.60487 9.902

11HG Hu Giang 151 NGNB09 Hu Giang TX Ng By

Phng NgBy 105.82861 9.808


56/56

7. APPENDIX

SITES DATA BASE CHECKED AND AUDITED

VTC_Ket qua audit46 tram TWH tai_HU

VTC HW Checked ForWorse Cells KPI.xls

VTC AntennaChange Request 191

Date post:	02-Jun-2018
Category:	Documents
Upload:	rahim-khan
View:	222 times
Download:	0 times

Hauwei Giang Wcdma Optimization Report

Documents