parameter assessment tools

31
For internal use ©2013 Nokia Solutions and Networks. All rights reserved. Parameter assessment and tool update November 2011, Update for RU30 March 2013 RANOP2 - M2/January 2011

Upload: jardiq

Post on 10-Dec-2015

18 views

Category:

Documents


0 download

DESCRIPTION

assesment

TRANSCRIPT

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Parameter assessment and tool update

November 2011, Update for RU30 March 2013

RANOP2 - M2/January 2011

2

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Content

RANOP2 - M2/January 2011

Network parameter discrepancy checks• Discrepancy check for actual network parameters

Verification of network configuration• Introduction

• WBTS commissioning and configuration files

• Comparison of network parameters and actual configuration

3

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Parameter discrepancy check

RANOP2 - M2/January 2011

Motivation: Network configuration is under continuous change. There is a risk that some parameters are set to wrong values due to changes in planning and templates, upgrades, …

• Usually operator maintains a list of planned values. There may be several sets of planned values depending on site configuration (number of carriers, HSPA configuration, site type: microcell, macrocell, indoor, ..)

• If no planned value exists for a parameter, it can be compared to NSN default value or to the most common value in the network.

• It is not possible to have a single planned value for all parameters, such as names, IDs, neighbour parameters, …Target is to find and correct discrepancies in the parameter settings.

4

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Parameter discrepancy check

RANOP2 - M2/January 2011

• High number of parameters and objects to check

• Some of them are configuration and feature dependant

• Discrepancy check can be limited to the most important objects

5

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Parameter discrepancy check

RANOP2 - M2/January 2011

Parameter discrepancy check can be done using any tool that can access parameter data. Some options:

-Tool running directly in OSS or executing SQL queries in OSS

-Tool parsing NetAct actual configuration export files (.xml from CM Operations Manager)

-Tool using PlanEditor database (.mdb generated from the export XML)

-Manually in Excel/Access if network is small or only a few parameters are considered

-Using PlanEditor, Proton, CM Analyser, …

No widely used standardized solution for parameter discrepancy check.

6

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Parameter discrepancy check

RANOP2 - M2/January 2011

Parameter discrepancy check should be one of the first items in an optimization project. Any further optimization work can be undermined by incorrect or inconsistent parameters.

Before correcting any found discrepancies, it should be confirmed that the parameters are not set other than planned in purpose – e.g. due to parameter or feature trial, special sites, …

Together with discrepancy check it is easy to confirm that other NSN parameter recommendations such as TN159 and TN113 are followed.

7

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Parameter discrepancy check example

RANOP2 - M2/January 2011

XMLDump2Excel, reads directly the CM Operations Manager export XML file and compares them to a values defined on the main page:

https://sharenet-ims.inside.nokiasolutionsandnetworks.com/Overview/D437144080

Pros:

- Direct XML import with UI or internal values

- Discrepancy check with correction XML

- Easy and quick to use

- Easy to read output format for parameter overview

Cons:

- Only one default parameter value per parameter (no support for templates or site type dependant value settings)

- Tables and parameters hardcoded: some tables missing, RU30 tables are not yet implemented

8

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Parameter discrepancy check example

RANOP2 - M2/January 2011

123 cells set to other value than 4

18 cells have maximum bitrate lower than 384 kbps

No default value possible

9

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Enabled features in RNC

RANOP2 - M2/January 2011

Optional features enabled in RNC can be verified from OSS database / Plan Editor database using RncOptions table.

XMLDump3Excel extracts this as well.

Check that all required features are enabled in all RNCs.

Note that many of the features need to be configured and enabled with other parameters (e.g. WCEL) in addition to enabling it in RNC Fifile.

10

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Content

RANOP2 - M2/January 2011

Network parameter discrepancy checks• Discrepancy check for actual network parameters

Verification of network configuration• Introduction

• WBTS commissioning and configuration files

• Comparison of network parameters and actual configuration

11

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Network configuration verification

RANOP2 - M2/January 2011

In network configuration verification the actual network configuration is analysed against

•Mismatches between planned configuration and actual configuration

•Mismatches between enabled functionality and parameter settings

•Mismatches in the configuration parameters

Mismatches can be for example wrong WBTS software level, HSDPA scheduler types, errors in MHA and feeder loss settings, WCEL power settings, …

Verifying everything in the network is an enormous task. Following slides concentrate on a selected checks that are found to be useful.

12

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Content

RANOP2 - M2/January 2011

Network parameter discrepancy checks• Discrepancy check for actual network parameters

Verification of network configuration• Introduction

• WBTS commissioning and configuration files

• Comparison of network parameters and actual configuration

13

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration

RANOP2 - M2/January 2011

Several performance and capacity affecting parameters are set in WBTS commissioning phase or controlled by WBTS licenses including:

-Baseband capacity (license controlled in FlexiBTS up to HW limit)

-Number and type of HSDPA schedulers

-Number of HSUPA schedulers

-Local cell grouping and capacity allocation between local cell groups

-Cell maximum RF power

-Antenna line properties (MHA gain, feeder loss, RX diversity branch,…)

Any errors or mismatches between planned setup, configured setup, and actual hardware on site may lead to performance degradation.

14

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration

RANOP2 - M2/January 2011

WBTS configuration can be checked using WBTS site manager:

However it is very time consuming to manually log in to every WBTS and view detailed settings.

15

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration

RANOP2 - M2/January 2011

WBTS configuration files can also be collected using a tool such as FileCollectorTool:https://twiki.inside.nokiasolutionsandnetworks.com/bin/view/SEM/CommandlineTools

It collects site configuration data (including commissioning data and licenses) to xml files which can be mass post-processed.

Collecting the data takes quite long time as the tool automatically logs to every WBTS to copy the data, but it can collect all the files in background without user interaction.

16

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration

RANOP2 - M2/January 2011

WBTSFileQuery

WBTS_IP

Addre

ss

WBTS na

me

BTS Plat

form

BTS SW

Mas

ter S

M

Extens

ion S

M

WSPx c

ards

NodeB C

E capa

city

Schedu

ler ty

pe

Share

d sc

hedu

ler lic

ence

Number o

f HSDPA sc

hedule

rs

Number o

f HSUPA sc

hedule

rs

Number o

f acti

ve c

ells

Number o

f inac

tive ce

lls

Cell rang

e [m

]

RACH capa

city

Carrier

allo

catio

ns

Max

carri

er pow

er [d

Bm]

Radio u

nits

10.10.42.109Hermia 5 AudioNORA WN6.0_22.11-198 2xWSPC 128 -1 FALSE 1 1 1 0 20000(1) 2(1) 10787(1) 1xWPAI 1xWTRB10.10.42.117WBTS31 MetroNORA WN6.0_22.9-12 2xWSPC 128 Full BaseBandTRUE 1 1 1 0 20000(1) 2(1) 10787(1) 1xWTRB10.10.42.121Hermia 3B2 FlexFLEXI WN6.0_22.11-187FSMD 396 Shared HSDPA Scheduler for BB EffiecincyTRUE 1 1 3 1 20000(3) 2(3) 10662(3) 43.0(3) 2xFRGL10.10.42.129WBTS-33 Hermia 15 Rene B1FLEXI WN6.0_22.12-249FSMD 396 Shared HSDPA Scheduler for BB EffiecincyTRUE 1 1 2 0 20000(2) 2(2) 10662(1), 10637(1)43.0(2) 1xFRGC10.10.42.173Hermia 2 NORA WN6.0_22.11-198 4xWSPC 256 Full BaseBandFALSE 0 0 1 4 20000(1) 2(1) 10787(1) 5xWPAA 5xWTRA10.10.42.185Hermia 4 UPSFLEXI WN6.0_22.11-187FSMB 240 Shared HSDPA Scheduler for BB EffiecincyTRUE 1 1 3 1 20000(3) 2(3) 10564(3) 43.0(3) 2xFRGC10.10.42.61Hermia 6 IVNORA WN6.0_22.11-198 6xWSPC 384 Full BaseBandTRUE 1 1 1 2 20000(1) 2(1) 10787(1) 3xWPAA 3xWTRA

D:\userdata\pranta\My Documents\RU30\RU30

Example script for WBTS xml file mass analysis ( separate one for RU30):

Output data includes:

BTS configuration (cells, carriers, HSDPA/HSUPA schedulers, …)

BTS HW (system modules, radio modules, WSPx/WPAx/WTRx cards)

BTS licenses

Local cell group configuration

MHA and antennaline data

17

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, general data

RANOP2 - M2/January 2011

WBTS software level

Baseband capacity

Number of cells

18

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, HSUPA and local cell groups

RANOP2 - M2/January 2011

Check allocation of local cell groups:

• number of cells per LCG

• baseband allocation per LCG

• Is HSUPA enabled in the LCG

Non-optimal LCG allocation can cause unnecessary blocking due to lack of baseband capacity in LCG or reduced HSUPA performance if unused baseband capacity is allocated to other LCG.

19

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, HSDPA scheduler type

RANOP2 - M2/January 2011

Check HSDPA scheduler type and number:

•HSDPA scheduler type is defined in WBTS commissioning phase or by HSDPA shared scheduler license (note that dedicated HSDPA scheduler overrides shared scheduler license)

•If shared scheduler is used, the number of schedulers depend on Tcell parameter settings on the site.

Wrong scheduler type may cause HSDPA setup problems due to too many users, or waste baseband capacity if schedulers are underutilized.

20

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

BTS PlatformBTS SW NodeB CE capacityScheduler type Shared scheduler licenceFLEXI WN6.0_22.12-1451224 Shared HSDPA Scheduler for BB Effiecincy TRUEFLEXI WN6.0_22.12-1451224 Shared HSDPA Scheduler for BB Effiecincy TRUEFLEXI WN6.0_22.12-1451224 Shared HSDPA Scheduler for BB Effiecincy TRUEFLEXI WN6.0_22.12-1451224 Shared HSDPA Scheduler for BB Effiecincy TRUEFLEXI WN6.0_22.11-187_B1224 Shared HSDPA Scheduler for BB Effiecincy TRUEFLEXI WN6.0_22.11-187_B1224 Shared HSDPA Scheduler for BB Effiecincy TRUEFLEXI WN6.0_22.11-187_B1224 HSDPA 16 Users per Cell FALSEFLEXI WN6.0_22.11-187_B1224 Shared HSDPA Scheduler for BB Effiecincy TRUEFLEXI WN6.0_22.11-187_B1224 Full BaseBand FALSEFLEXI WN6.0_22.11-187_B612 Full BaseBand FALSE

WBTS configuration, HSDPA scheduler type

RANOP2 - M2/January 2011

High HS-DSCH setup failures due to max users during busy hours. Max HSDPA users stay at 17 most of the day.

Either full baseband or shared HSDPA scheduler was planned to all sites, but due to a missing licence 16 Users per cell HSDPA scheduler is used.

21

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, cell carrier power

RANOP2 - M2/January 2011

BTS Platform BTS SW NodeB CE capacityMax carrier power [dBm] Radio units 435: Flexi WCDMA BTS 40W Power Licence 1125: Flexi WCDMA BTS 60W PowerFLEXI WN6.0_22.11-187_B1224 46.0(1) 1xFRGP 1/ 3FLEXI WN6.0_22.11-187_B1224 43.0(3), 46.0(3) 2xFRGP 3/ 6FLEXI WN6.0_22.11-187_B1224 46.0(3) 2xFRGP 3/ 6FLEXI WN6.0_22.11-187_B1224 44.8(8), 43.0(1) 2xFRGP 6/ 6 3/ 6FLEXI WN6.0_22.11-187_B1224 46.0(6) 2xFRGP 6/ 6FLEXI WN6.0_22.11-187_B1224 44.8(9) 2xFRGP 6/ 6 3/ 6

3 cells commissioned to 46 dBm and 3 cells to 43 dBm. Only 3 out of 6 installed 40W power licenses are used.

8 cells commissioned to 44.8 dBm and 1 cell to 43 dBm. Site also has excess licenses (6x 40W and 6x 60W, some of them not used)

Check that cell carrier power is commissioned to same as cell physical maximum power or maximum licensed power:

• It is possible to commission lower maximum power to cell than it supports

• Also check that cell power related parameters in WCEL are in-line with commissioned maximum power.

22

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, antenna line properties

RANOP2 - M2/January 2011

Platform LcrId ANTLid Feeder loss [dB]FLEXI 1 1 -10FLEXI 1 2 -3

3 dB feeder loss in one RX branch, 10 dB in other?

Check MHA use. If MHA is configured to the cell then,

• MHA voltage should be set correctly

• MHA should be configured to both RX feeds

• Feeder losses should be defined for both RX feeds

• Feeder loss of the RX feeds should be the same (or very similar)

• Feeder loss should be set to as correct value as possible

Incorrect feeder loss setting in WBTS commissioning affects AC and UL capacity due to wrongly calculated RX noise floor and to the cell pilot power reported to UE in SIB7 message.

Check also that MHA and cableloss parameters in WCEL matches to what is commissioned to the cell.

23

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, antenna line properties

RANOP2 - M2/January 2011

PrxNoise

102.0

104.0

106.0

108.0

110.0

112.0

114.0

0 5000 10000 15000 20000 25000 30000 35000

Wcell hours

-Prx

No

ise

Faulty MHA or incorrect commissioning of feeder losses may also be visible in WCEL PrxNoise counters:

Noisefloor of the system RNC_177c = avg(AVE_PRX_NOISE) / -100

Low PrxNoise indicates possibly missing bias power or faulty MHA.

High Prxnoise indicates possibly too high feeder loss setting.

Configuration check on those cells is recommended.

24

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, installed licenses

RANOP2 - M2/January 2011

Audit installed licenses in the WBTS for missing or excess licenses:

• Baseband capacity license

• Shared HSDPA scheduler license

• 16QAM HSDPA license

• Proportionally fair HSDPA scheduler license

• Branch activation license

• 40W or 60W power license

• MHA license

25

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

WBTS configuration, installed licenses

RANOP2 - M2/January 2011

WBTS_IPAddress BTS PlatformNodeB CE capacityScheduler type Shared scheduler licence Number of HSDPA schedulers10.29.12.138 FLEXI 1224 Shared HSDPA Scheduler for BB Effiecincy TRUE 310.29.12.153 FLEXI 1224 Shared HSDPA Scheduler for BB Effiecincy TRUE 310.29.12.161 FLEXI 1224 HSDPA 16 Users per Cell FALSE 210.29.12.169 FLEXI 1224 Shared HSDPA Scheduler for BB Effiecincy TRUE 310.29.13.65 FLEXI 1224 Full BaseBand FALSE 310.29.13.73 FLEXI 1224 Full BaseBand TRUE 610.29.13.81 FLEXI 1224 Shared HSDPA Scheduler for BB Effiecincy TRUE 2

WBTS_IP

Addre

ss

BTS Plat

form

306:

HSDPA 16

QAM S

uppo

rt

309:

Anten

na Li

ne Sup

ervis

ion

435:

Flexi W

CDMA B

TS 40W

Pow

er L

icenc

e

616:

IMA (F

TM)

767:

UBR+ for I

ub U

ser P

lane

649:

HSDPA Sha

red

Sched

uler f

or B

TS

1216

: Rx S

igna

l Lev

el M

onito

ring

307:

HSDPA PFRP S

ched

uler

598:

Additio

nal 2

E1, T

1, JT

1 int

erface

(FTM

)

308:

Licen

ce B

ased

BTS c

hann

el ca

pacit

y

1052

: Flex

i WCDM

A BTS B

ranc

h Acti

vatio

n Lice

nc

554:

Flexi W

CDMA B

TS AIS

G MHA S

uppo

rt

434:

Flexi W

CDMA B

TS Mult

i Car

rier L

icence

1125

: Flex

i WCDM

A BTS 6

0W P

ower

10.29.12.177 FLEXI ON ON 3/ 6 ON ON ON ON 5/ 16 1224/ 1224 6/ 610.29.12.17 FLEXI ON ON 6/ 6 ON ON ON ON 5/ 16 612/ 612 6/ 6 ON10.29.12.185 FLEXI ON ON 6/ 6 ON ON ON ON ON 14/ 16 1224/ 1224 6/ 6 ON 3/ 18 3/ 610.29.12.193 FLEXI ON ON 6/ 6 ON ON ON ON ON 12/ 16 1224/ 1224 6/ 6 ON10.29.12.1 FLEXI ON ON 3/ 9 ON ON ON ON 4/ 16 1224/ 1224 3/ 910.29.12.201 FLEXI ON ON 6/ 6 ON ON ON ON ON 15/ 16 1224/ 1224 6/ 6 ON10.29.12.209 FLEXI ON ON 3/ 6 ON ON ON ON ON 4/ 16 1224/ 1224 6/ 6 ON10.29.12.217 FLEXI ON ON 6/ 6 ON ON ON ON ON 3/ 16 1224/ 122410.29.12.225 FLEXI ON ON 3/ 6 ON ON ON ON 4/ 16 1224/ 1224 6/ 6 ON10.29.12.233 FLEXI ON ON 1/ 3 ON ON ON ON 4/ 16 1224/ 1224 1/ 310.29.12.241 FLEXI ON ON 3/ 6 ON ON ON ON ON 15/ 16 1224/ 1224 6/ 610.29.12.249 FLEXI ON ON 3/ 6 ON ON ON ON 8/ 16 1224/ 1224 6/ 6 ON Should be correlated with antenna

line data to check if site has MHA or not.

?

Excess licenses, branch activation and power licenses:

Missing/excess licenses, HSDPA schedulers:

26

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Content

RANOP2 - M2/January 2011

Network parameter discrepancy checks• Discrepancy check for actual network parameters

Verification of network configuration• Introduction

• WBTS commissioning and configuration files

• Comparison of network parameters and actual configuration

27

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

OSS parameters vs actual configuration

RANOP2 - M2/January 2011

Some OSS parameters can be set freely regardless of what actually is installed on the site or configured elsewhere in the database.

To find such mismatches following can be done:

• Comparing WBTS commissioning data to OSS parameters

• Comparing relations of OSS parameters

-Sanity checks in parameter values

-WCEL MaxDLPowerCapability

-CM Analyser checks

• Comparing WBTS commissioning and OSS parameters to external data

-Input data from operator or other data source

28

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

Commissioned max cell power and WCEL power parameters

RANOP2 - M2/January 2011

Actual power settings depend on operator, but usually they should be set relative to PtxCellMax.

PtxCellMax should not be set higher than MaxDLPowerCapability.

CId

PtxPrim

aryCPICH

MaxDLPo

werCapability

PtxM

axHS

DPA

PtxO

ffsetHSD

PA

PtxPSstreamAb

sMax

PtxTargetHSD

PA

PtxCellM

ax

53129 270 390 460 8 370 410 46054534 270 390 460 8 370 410 46054533 270 390 460 8 370 410 46064220 300 390 460 8 370 410 46064530 280 390 460 8 370 410 460

Microcells with 8W carrier power.

CPICH is lowered, but other WCEL power settings are left as in 40W macrocells.

Check that WCEL power settings are in-line with commissioned maximum power capability of the cell:

WCEL parameter MaxDLPowerCapability is a non-modifiable parameter which shows the cell commissioned power capability.

29

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

RNC data WBTS dataCId CellRangeRACHCapacityCableLossMHA WBTS_MHA WBTS_feederLoss

64124 10000 2 0 1 MHA used -3064126 10000 2 0 1 MHA used -3062047 10000 2 0 1 MHA used -3462049 10000 2 0 1 MHA used -3448897 10000 2 0 1 NO MHA -2548898 10000 2 0 1 NO MHA -25

MHA and feederloss (cableloss) parameters in commissioning and RNC data base

RANOP2 - M2/January 2011

MHA commissioned to the cell with cable/feederloss, but it is not set correctly in WCEL

No MHA commissioned, but MHA parameter in WCEL is set to ’MHA used (1)’

Note: cableLoss in WCEL is a positive value for loss, but feederLoss commissioned to WBTS is negative value for loss!

Feeder/cable loss for each cell and whether MHA is used or not should be set similarly in WBTS commissioning and WCEL parameters.

30

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

CM Analyser checks

RANOP2 - M2/January 2011

Number of configuration checks based solely on RNC database are defined in CM Analyser:

-Neighbour parameters (intra- and inter-system)

-Neighbour bi-directionality

-Some cell parameter checks

For internal use

©2013 Nokia Solutions and Networks. All rights reserved.

RANOP2 - M2/January 2011