02 Network Configuration Optimization

1 2007 Nokia 13-468259 v1.0

Company Confidential

Network Configuration Optimization RANOP / 2007

2 2007 Nokia 13-468259 v1.0Company Confidential

Summary

CM Theory BSC Tables Default, Specific and Sensitive Parameters

CM Process Design default sets Consistency Checks Review Neighbour Plan Review Frequency Plan

CM Examples Examples of wrong parameter set with impact on network

operation/performance CM Tools

Nokia NetActTM Planner, Nokia NetActTM Optimizer and RAC Tools

3 2007 Nokia 13-468259 v1.0


CM Theory

BSC TablesDefault, Specific and Sensitive Parameters


BSC Tables

ADCE POCHOCTRX

BTS

BCF

BSC

RTSL

MA, BA

SEG


Define Default sets

Default Parameters:Almost all parameters areset to default values

Specific Parameters:Are set during planning phase, e.g. frequency, BSIC etc.

Default, Specific, and Sensitive Parameters

Sensitive Parameters: Changes in some default parameters are quite dangerous as they may have a critical impact on the network. Care must be taken.


1. Default parameters BSC, BTS, HOC, POC, ADCE, TRX tables

Sensitive parameters BTS table: HOP, BAR, PLMN, ACC, RXP, TLC, PMAX, DMAX, TRP, IDLE, ACT, RDIV POC table: PMAX, UDR, UUR, LDR, LUD HOC table: EPB, HPP, LDWS, LUWS, QDWS, QUWS, QDR, QDP, QDN, QUR, QUP, QUN, LDR, LDP,

LDN, LUR, LUP, LUN, ADCE table: PMRG, LMRG, QMRG, MRGS

2. Specific parameters BTS table: BSC id, BCF id, SEG id, BTS id, BTS NAME, Cell id, MCC, MNC, LAC, RAC, NCC, BCC, MAL,

HSN1, HSN2, MO, MS, CDEF, CDED ADCE table: BSC id, BTS id, N-LAC, N-Cell id, N-BCCH, N-NCC, N-BCC, synchronised TRX table: BSC id, BTS id, TRX id, FREQ, TSC, TSL configuration

Microsoft Excel

Worksheet

Default, Specific and Sensitive Parameters

7 2007 Nokia 13-468259 v1.0


CM Process

Design default setsConsistency ChecksReview Neighbour PlanReview Frequency Plan


CM Process - Summary

Design default sets Consistency Checks

1. Compare network design against network configuration Default Parameter Check Specific Parameter Check

2. Database check Check inconsistencies between TRX, BTS table with ADCE table: Check Adjacencies to non-existing cells

3. Consistency parameter checking Neighbour cells with co-BSIC, co-BCCH ...

Review Neighbour Plan Review Frequency Plan


Design default sets Define default parameter sets - sector template

Macro 850/900 Macro 1900/1800 Micro 850/900 Micro 1900/1800 Dense-Urban Rural

Define default neighbour sets adjacency template Macro 850 Macro 850 Macro 850 Macro 1900 Macro 850 Micro 850 ...

Sector creation through dat or xml file according to: Sector template Sector specific parameters

Default sets

consist of

MML default

values +

recommended values


Consistency ChecksOSS

CM DatabaseCM Database

Export

Parameterfile

Master configurationdatabase

actual default

planned

default

actual specific

NetAct Planner

Planningdatabase

Parameterfile

export

import

Import

Consistencycheck

Parameterfile

Import Export

Mapinfo

ODBC

Consistencycheck

Consistencycheck


CM Process

Compare network design against network configurationDefault Parameter CheckSpecific Parameter Check

11 2007 Nokia 2. Network Configuration Optimization / 2007-05-31 / Initials



Compare network design against network configuration

Configurationanalysis

Real systemconfiguration

Planned systemconfiguration

"What's in the system is not always what we planned to be there"


OSS

Operational department

Planning department

Default parameter check

Databases :

Responsibilities :

BSC

BSC

BSC

actual default

planned

default

actual specific


Consistencycheck

Note: Verify

default settings

are

OK before

doing consistency

checking in

case parameter

planning was

done by

others!!!


Default parameter check

Default parameter checking Export Actual Default Parameters from the OSS through a xml file, for e.g. Import xml file into a Database using for e.g. CM Plan Editor. Compare Planned Default Sets with Actual Default Parameters in the network. Mark exceptions for each default parameter Show differences Select changes to be done Create dat file or xml file for correction

It is very important to verify if any changes to Default Parameters hasbeen done before any optimization, as this may result in undesired and

unexpected impacts on the network.


OSS

Planning toole.g. NetAct

Operational department

Planning department

Specific parameter check

Databases :

Responsibilities :

BSC

BSC

BSCactual default

planned

default

actual specific

Consistencycheck



Specific parameter check

Specific sector parameter checking Export Actual Specific Parameters from the OSS through a xml file, for e.g. (this

can be done jointly with Default Parameters) Import xml file into a Database using for e.g. CM Plan Editor Import Planned Specific Parameters from NetAct Planner Use GSM Cell Id as key Compare Planned Specific parameters with Actual Specific parameters from

OSS (mainly LAC, RAC, frequencies, hopping parameters and neighbours) Mark exceptions for each default parameter Show differences Select changes to be done Create dat file or xml file for correction

It is very important to verify if Specific Parameters have been correctlyimplemented before any optimization


CM Process

Database check




Database check

OSS

BSC

BSC

BSCBTSHOCPOC

BTSHOCPOC

BTSHOCPOC

ADCEADCE

ADCE

Consistencycheck


BSC A BSC B

OSS 1

BSC C

OSS 2

Database check


Database check of Actual Parameters Export all Parameters from the OSS through a xml file, for e.g. Import xml file into a Database using for e.g. CM Plan Editor. Check inconsistencies between TRX, BTS table with ADCE table:

N-BCCH in ADCE table against FREQ in TRX table N-LAC, N-NCC, N-BCC in ADCE table against LAC, NCC, BCC in BTS table

Check Adjacencies to non-existing cells Show differences Select changes to be done Create dat file or xml file for correction

Inconsistencies in tables can generate drop calls during HOs, for e.g.

fAB

Database check


fAFREQTRX idBTS idBSC id

BTS idfABN-BCCHN-Cell idN-LACBSC id

TRX

ADCE

N-Neighbour

Cell A Cell BfAB

fA

applies also to other cell parameters !!

Database checkN-BCCH in ADCE table against FREQ in TRX table


=================================================================================

= ADJACENCY DISCREPANCIES= Network: PLMN= Area: All BTSs selected= Sorting key: source BSC name, source BTS ID=================================================================================

This report lisTCH the discrepancies of various parameters between the source cell adjacency parameters and target cell parameters.Impact of discrepancies:Any difference between two identical parameters of the target BTCH and the same parameter of adjacency usually resulTCH in handover

failures between the source and the target BTCHs.The first of each pair of lines indicates the adjacency of a source cell.The second line indicates the target cell.Parameters in the first line show the values in the adjacency (ADJ) of a source cell defined in c_adjacent_cell table.Parameters in the second line (TGT) show the values of the target cell in c_bTCH table.The checked parameters are: Location Area Code (LAC), Cell Identity (CI),Frequency (FREQ), Maximum power of MS (PMAX), Network

Colour Code (NCC) and Base Station Colour Code (BCC). These should be the same in the adjacency and in the target cell.In case there is any kind of discrepancy indicated by the report, do the following:1) Upload adjacency data from the network for the claimed BTCHs.2) Run this check again.3) If discrepancies are still found, check and correct them via MML.================================================================================

Adjacency discrepancies in PLMN networkLAC CI FREQ PMAX NCC BCC=== === === ==== === ===

Source BSC (BTCHid) Source BCF/BTCH ADJ ADJ ADJ ADJ ADJ ADJTarget BSC (BTCHid) Target BCF/BTCH TGT TGT TGT TGT TGT TGT------------------ ---------------------------- ------ ------ ---- ---- --- ---

BSC1KUTOJA(6) SUOSAA004 / SUOSAA10061 10010 600 30 7 2BSC1KUTOJA(10) LAAJAL010 /LAAJAL1010 1 10010 773 30 7 2BSC1KUTOJA(7) SUOSAA004 / SUOSAA10071 10010 600 30 7 2BSC1KUTOJA(10) LAAJAL010 /LAAJAL1010 1 10010 773 30 7 2BSC1KUTOJA(9) LAAJAL009 / LAAJAL10091 10010 600 30 7 2BSC1KUTOJA(10) LAAJAL010 /LAAJAL1010 1 10010 773 30 7 2BSC1KUTOJA(9) LAAJAL009 / LAAJAL10092 20003 594 30 7 7BSC2UPS1(3) 3UPS001 /3UPSULTRA20032 20003 764 30 7 7BSC1KUTOJA(9) LAAJAL009 / LAAJAL10092 20002 600 30 7 7BSC2UPS1(2) 3UPS001 /3UPSULTRA20022 20002 762 30 7 7BSC2UPS1(1) 3UPS001 /3UPSULTRA20012 20001 776 30 7 7BSC2UPS1(10) 5KOM005 / 5KOM2010 1 10009 605 30 7 2

Database checkN-LAC, N-NCC, N-BCC in ADCE table against LAC, NCC, BCC in BTS table

Adjacency Discrepancies (060) Example


Cell ACell C

OMC 1 OMC 2

Cell B

Cell B is deleted but incoming adjacencieswere not removed

Cell C is not known in OMC Area 1 database

BSC 2BSC 1

Database checkAdjacencies to non-existing cells


==============================================================================

= ADJACENCIES TO NON-EXISTING OR FOREIGN CELLS= Network: PLMN= Area: All BTCHs selected= Sorting key: source BSC name, source BTCH ID===============================================================================

Normally every adjacency should be towards an existing cell.In this report all adjacencies are checked so that the adjacent cell(c_bTCH:ci, lac) really is found in the Nokia NetAct database in the c_bTCH table.Discrepancies are reported.

Instructions:Remove the incorrect adjacencies by the Top-level User Interface after comparing the report to the plan.Note that if the adjacent cell exisTCH in another Nokia NetAct, no correction is needed.Note: Running this report takes a few minutes. Patience please.===============================================================================

Adjacencies to non-existing cellsSource Source Source ADJ.CELL ADJ.CELLBSC (BTCH id) BCF/BTCH BTCH int_id LAC CI--------------- ------------------ ---------- -------- --------

BSC533(48) BSC533 118112 22871 1022Cid 2413

BSC552(24) 102679 22870 3291BSC553(1) 97461 22870 3301BSC553(2) 97769 22870 3301BSC553(4) 98375 22870 3301BSC553(10) 99316 22870 3142

Adjacencies to Non-existing or Foreign Cells (065) - Example

Database checkAdjacencies to non-existing cells


CM Process

Consistency parameter checking




Check cells in MSC vs cells in BSC Check external adjacencies in MSC Cells with co-channel frequencies Cells with adj-channel frequencies Non symmetrical adjacencies Neighbours with co-channel frequencies Neighbours with adj-channel frequencies Neighbours of a same cell with co-BSIC, co-BCCH Check BCCH-BSIC reuse distance Check BCCH reuse distance Check site with same MA List in different sectors and different HSN Check site with same MA List in different sectors and MAIO collision Synchronized HO

Consistency parameter checking


Cell A Cell B

Cells with co-channel and adj-channel frequencies

FREQ=10 FREQ=9,10,11

Co-channel frequencies: HO is not possible in case of co-BCCH Adj-channel frequencies: Ho is possible but might fail due to interference.

A

B

-6dB -9dB


Cell A Cell B

Non symmetrical adjacencies Find all non symmetrical adjacencies :

cell B is neighbour of Cell A cell A is not neighbour of Cell B


Neighbours with co-channel and adj-channel frequencies or co-BSIC, co-BCCH

Cell Af=24

Cell Bf=10, BSIC=2,2

f=24f=9,10,11

f=10

Neighbours with co-BSIC, co-BCCH:Might generate ghost-access and HO drop calls. High sdcch abis failure and high handover failure could be indicators for this case.

Neighbours with co-channel or adjacent channel frequencies:Will cause interference between neighbour cells

Cell Cf=10, BSIC=2,2


Check BCCH-BSIC and BCCH reuse distance

Small distances may be dangerous!

Reuse 4/12

FREQ = 234BSIC = 42

FREQ = 234BSIC = 42

FREQ = 234


Synchronised handover

Site BSite A

Non-synchronised Handover MS sends access bursts (HO_ACCESS) (with varying TA) until it receives

PHYSICAL_INFO Synchronised Handover

MS sends a few access bursts (HO_ACCESS) and then starts transmission with previous TA

Non-synchronised handover leads to a longer communication interruption than synchronised handover (200ms vs. 100ms)

Synchronized HO should be activated between sectors of the same site. If activated on inter-site adjacencies the handover can fail

Synchronized HONon- Synchronized HO


CM Process

Review Neighbour Plan




Review Neighbour plan Neighbour planning

According to best server areas Neighbour optimisation adding

Activate double BA List feature in cells to be integrated/optimised Analyse Undefined Adjacent Cell Measurements Activate channel finder measurements Add neighbour cells appearing with high RxLev and many occurences

Neighbour optimisation deleting Activate handover adjacent cell measurements Find pair of cells with low number of attempts incoming and outgoing Delete corresponding adjacencies

Remark: number of adjacencies should be optimised (minimised) in order to facilitate the measurement tasks performed by the handsets

Note: Even when Optimizer is used for automatic Neighbour Optimization, Double BA List and Channel Finder features need to be activated in order to collect measurements from the Network.


Theoretical Model

Cell

Adj Cells

Opt adj cells

Other cells


Double BA List

Parameter Value

bCCHAllocation-ID 1 ... 255bCCHAllocationList 1 ... 124 in GSM (max. 32 freq. for all bands)

idleStateBCCHAllocation 0 (BCCH list is taken from the adjacent cell)1 ... 255 (number of the BCCH list used)

measurementBCCHAllocation ADJ (BCCH frequency list taken from adj. cell)IDLE (active MS uses same list as MS in IDLE mode)

initialFrequency 1..124 & 975..1023, 0; 512..885 GSM900;1800 (FREQ TRX)


Undefined Adjacent Cell Measurement Registers statistics on cells, which have not been defined as adjacent cells but

which are among those six neighbouring cells, that the MS receives best

Source BTS

Defined Adjacencies in source BTSAmong the best measured Adjacencies by the Mobile but not defined as adjacencies in the Source BTS. These Adjacencies to be reported in the Undefined Adjacent Cell MeasurementBoth defined as Adjacencies in the source BTSand among the 6 best measured Adjacencies in the Mobile. These are the only one to make the handover to if necessary.


Undefined Adjacent Cell Measurement

Average strength of the downlink signal received from an undefined adjacent cell

Number of samples for calculating the average DL signal strength

BCCH, NCC, BCC of adjacent cell

Network Doctor 073


Serving CellUD

UD

D

D

D D

D

D

D = Defined Adjacent CellUD = Undefined Adjacent Cell

Compare dBm values betweenserving cell and UD

Channel finder measurement


Measreport

Undefined Adjacent Cell dBm - Serving Cell dBm(update current counter)

Counter 1(dBm value below 0)

Counter 2( 0 < dBm value < 6)

Counter 3(dBm value >6)

500 5000 2000Values after 1 hour measurement period

Dominating Good candidate for a defined cell

3600 sec / 0.48 sec = 7500 samplings during one hour

Channel finder measurementDecision mechanism


Adjacent cell measurements

Nbr of HO Attempts outgoing and incoming

In case Number of HO Attempts is very low to a certain cell, consider removing this cell from Adjacency list.

Network Doctor 153


CM Process

Review Frequency plan




Review Frequency plan

Optimise BCCH-BSIC reuse in cities ( no repetitions) Optimise BCCH reuse Implement new frequency plan with Optimizer using existing band splitting

strategy Implement new frequency plan with Optimizer using existing band strategy Simulate new band strategies in simulation tool (1/1, 1/3, 3/3, heuristic RF

hopping with different number of frequencies) Implement the strategy that gives the best simulation result


BCCH-850

0

10

20

30

40

50

60

70

80

90

128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 150 151 152 153 156 157BCCH 850

#

Review Frequency planBCCH-BSIC 850

0

2

4

6

8

10

12

14

16

18

20

1

2

8

-

0

0

1

2

8

-

4

7

1

2

9

-

1

6

1

2

9

-

6

3

1

3

0

-

3

2

1

3

1

-

0

1

1

3

1

-

4

8

1

3

2

-

1

7

1

3

2

-

6

4

1

3

3

-

3

3

1

3

4

-

0

2

1

3

4

-

4

9

1

3

5

-

1

8

1

3

5

-

6

5

1

3

6

-

3

4

1

3

7

-

0

3

1

3

7

-

5

0

1

3

8

-

1

9

1

3

8

-

6

6

1

3

9

-

3

5

1

4

0

-

0

4

1

4

0

-

5

1

1

4

1

-

2

0

1

4

1

-

6

7

1

4

2

-

3

6

1

4

3

-

0

5

1

4

3

-

5

2

1

4

4

-

2

1

1

4

4

-

6

8

1

4

5

-

3

7

1

4

6

-

0

6

1

4

6

-

5

3

1

4

7

-

2

2

1

4

7

-

6

9

1

4

8

-

3

8

1

5

0

-

0

7

1

5

0

-

5

4

1

5

1

-

2

3

1

5

1

-

7

0

1

5

2

-

3

9

1

5

3

-

0

8

1

5

3

-

5

5

1

5

6

-

2

4

1

5

6

-

7

1

1

5

7

-

4

0

BCCH-BSIC

#

Optimize BCCH-BSIC reuse in cities (no repetitions)

Optimize BCCH reuse

44 2007 Nokia 13-468259 v1.0


CM Examples

Examples of wrong parameter set with impact on network operation/performance


Examples of wrong parameter set with impact on network operation/performance call setup, qual, bands1. No calls happening in a cell

Cell Barred Non existent (LAC, Cell ID) in MSC DMAX = 0

2. Very few calls happening in a cell RxLevAccesMin Wrong MNC, MCC, LAC declaration

3. Very low traffic in a cell msTxPwrMax = 0, bsTxPwrMax = 30

4. Bad quality in UL after rehoming

5. Few traffic in 1800 layer of a dual band 900/1800 network


Example 1a

Handover

Call Setup

SYS INFO

3 (BCCH)

(CellBarrAccess= yes)

No calls happening in a cell: The cell has been barred


Example 1b

MSC does not find(LAC, CI) in itsdatabase

No calls happening in a cell: CI different between MSC and BSC or non existent (LAC, Cell ID) in MSC


Example 1c

No calls happening in a cell:MsMaxDistanceInCallSetup (DMAX) = 0

DMAX = 0

RxLevel = -70 dBm

Call Setup

Despite the coverageof the cell, no calls willbe established!


Example 2a Very few calls happening in a cell:

RxLevAccesMin

Cell coverage

RxLevAccessMin = -47 dBm

......

-109 dBm1

-47 dBm63Highest range

-48 dBm62

-110 dBm0Lowest rangeBSS MMLOSS databaseMapping Be careful when setting

parameter through xml or datfile! OSS database unit should be used to specify parameter value!


Example 2b

Very few calls happening in a cell: Wrong MNC, MCC, LAC declaration in network - MNC: 01 1 !!! (In OSS correctvalue)


Example 3

bsTxPwrMax 0 30 dB 0 dBbsTxPwrMin 0 30 dB 30 dBminMsTxPower 0 36 dBm 0 dBmsTxPwrMax 0 36 dBm

Parameter Value_______Defaultvalue

BTS Max Power = BTS Power (bsTxPwrMax = 0 dB)BTS Min Power = BTS Power (bsTxPwrMin = 30 dB)

Attenuation Values (dB)

Power Values (dBm)MS Max Power = (msTxPwrMax = 33 dB)MS Min Power = (minMsTxPower = 13 dB)

Absolut

e

Delt

a

Very low traffic in a cell: msTxPwrMax = 0, bsTxPwrMax = 30


Example 4

Bad quality in UL after rehoming: DiversityUsed parameter not set to yes anymore

RDIV = Y

Uplink Diversityimproves quality of signal received.

After rehomingRDIV parameter was set to default value (No) and UL quality was affected.


Example 5

Few traffic in 1800 layer of a dual band 900/1800 network:Idle Mode: C2 parameters not set properly (temporaryOffset, penaltyTime)

BCCHBCCH

fast moving mobileslow moving mobile

1800: micro-Layer 900: macro-layer


Examples of wrong parameter set with impact on network operation/performance upgrade1. High drop call rate after upgrading a cell from 4 to 6 TRXs

Update MAL, no update of MAIO offset TRXs with different power without ICE activated


Example 1a

High drop call rate after upgrading a cell from 4 to 6 TRXs:Update of the MAL with no update of the MAIO offset


Example 1b

High drop call rate after upgrading a cell from 4 to 6 TRXs:TRXs with different power without ICE activated

CoverageBCCH - TRX

Capacity

MS in a region covered only by Coverage-TRX, ICE not activated. Result: BTS may allocate a TSL in Capacity TRX. Call will drop.

Traffic - TRX


Example 1b TRXs with different power

Dual Duplex Unit

Antennas

TRX RF Units

TXRX maindiv

WBC

Receive Multicouplers& Wideband Combiners

TX/RX ant TX/RX-divant

XXX

XXX

TXRX maindivTXRX maindiv

TXRX maindiv

TXRX maindiv

TXRX maindiv

WBC

Duple

xer

LNA

Duple

xer

LNA

Duple

xer

LNA

Duple

xer

LNA

+3dB


Examples of wrong parameter set with impact on network operation/performance frequencies

1. Drop call rate increase after new frequency plan implementation Double BA List activated

2. Impossibility to unlock some BTS after a RF-frequency hopping implementation

3. Impossibility to unlock some BTS after a frequency retune NON-EDGE TRX, with GTRX = Y TRX, with GTRX = Y, not attached to any EDAP pool

4. No handover happening after frequency retune between 2 cells fromdifferent BSCs ADCE table has not been updated for other BSC


Example 1

Drop call rate increase after new frequency plan implementation:In the meantime, measurementBcchAllocation has been changed to idle and MA listdefined with old BCCH frequency band

BCCH TCH OLD FREQUENCY PLAN

BCCH TCH NEW FREQUENCY PLANTCH

OLD MA List

These BCCH frequencies will not be measured by old MA List

These TCH frequencies will be wrongly measured


Example 2

Impossibility to unlock some BTS after a RF-frequency hopping implementation: After frequency hopping retune, some BCCH frequency equal to TRX frequencyof non-BCCH TRXs

After changing TRX frequency, verify BSIC and TSC (Training Sequence Code) is changed accordingly.


Example 3a

Impossibility to unlock some BTS after a frequency retune:NON-EDGE TRX, with GTRX = Y, in a cell with EGENA set to yes

BBTS

NON-EDGE TRX(s)

(E)GPRS territoryEGENA = Y

SEG

GTRX = Y

EDGE TRX(s)BTS

NON-EDGE TRX(s)

EGENA = YSEG

GTRX = N

EDGE TRX(s)B(E)GPRS territory

GTRX = Y GTRX = Y


Example 3b

Impossibility to unlock some BTS after a frequency retune:TRX, with GTRX = Y, not attached to any EDAP pool in a cell with EGENA set to yes

BTS

NON-EDGE TRX(s)

EGENA = YSEG

GTRX = N

EDGE TRX(s)B(E)GPRS territory

GTRX = Y

EDAP pool

1

2

Add TRX-1 to EDAP pool


Example 4

No handover happening after frequency retune between 2 cells from differentBSCs:Frequency retune has been done with MML command. ADCE table has not beenupdated for incoming adjacencies belonging to other BSCs

fAFREQTRX idBTS idBSC id

BTS idfABN-BCCHN-Cell idN-LACBSC id

TRX

ADCE

N-Neighbour

Cell A Cell BfAB

fA


Examples of wrong parameter set with impact on network operation/performance Handover

1. No handover from a cell towards all its neighbours PLMN permitted = No

2. High Handover failures after implementation of new adjacency plan SYNC = YES

3. No handover happening from an interfered cell hoMarginQual set to 0

4. 100% of handover failures in an adjacency relation Co-BSIC co-BCCH declaration

5. High number of handovers hoThresholdsLevUL = hoThresholdsLevDL

6. Handover not happening when DL signal level of neighbour much greater thanserving cell POC DL activated


Example 1

No handover from a cell towards all its neighbours:PLMN permitted not set properly. MML Default value is the NCC of the BTS. So HOs will not happen towards neighbours with different NCC.

Cell ANCC 3

Cell BNCC 4

Plmn permitted 0 = No.

Plmn permitted 3 = YesPlmn permitted 4 = No

Plmn permitted 7 = No

Set Plmn permitted 4 = Yes

PLMN permitted parameter consists actually of 8 parameters (0 7) related to the NCC part of the BSICs of neighbour cells. MS only reports measurements of cells with NCC permitted (plmn permitted = YES).

No Measurement reports of Cell B are sent to BSC. So no HOsoccur from Cell A to Cell B


Example 2

High Handover failures after implementation of new adjacency planAll adjacencies have been implemented with synchronised parameter set to yes. HOs between cells of different sites will probably fail.

SYNC = YES

SYNC = NONew Channel, New Cell

ACTIVE CALLHANDO CMD

HANDO ACC

HANDO COMACTIVE CALL

MS NETWORK

Old Channel, Old Cell

PHYS INFOx

Synchronized Handover Set SYNC = YES only between sectors of the same site.

Recommendation is to have Sync HO within BTSs in the same BCF and Non Sync HO between BTSs in different BCFs.


Example 3

No handover happening from an interfered cellhoMarginQual set to 0

In an interfered cell, despite high signal strength, quality is not good. So HO Margin Qualshould permit HO to a cell that despite its lower signal strength, may have a better quality.

A

B

PBGT margin = 6dBHo Margin Qual = -4

Ho Margin Qual = 0(MML Default)


Example 4

100% of handover failures in an adjacency relationCo-BSIC co-BCCH declaration

Cell A Cell B

FREQ=10BSIC = 33

FREQ=10BSIC = 33


Example 5

0

1

2

3

4

5

6

7

-

1

1

0

-

1

0

8

-

1

0

6

-

1

0

4

-

1

0

2

-

1

0

0

-

9

8

-

9

6

-

9

4

-

9

2

-

9

0

-

8

8

-

8

6

-

8

4

-

8

2

-

8

0

-

7

8

-

7

6

-

7

4

-

7

2

-

7

0

-

6

8

-

6

6

-

6

4

-

6

2

-

6

0

-

5

8

-

5

6

-

5

4

-

5

2

-

5

0

dBmdBm

QualityQuality

HoThresholdLevUL/DL

HoThresholdInterferenceUL/DL

Interference HoInterference Ho

No Action NeededNo Action Needed

Quality HoQuality Ho

Level HoLevel Ho

HoThresholdLevDLHoThresholdLevUL

High number of handovers. hoThresholdsLevUL = hoThresholdsLevDL

hoThresholdsLevUL, high thresholds willanticipate HOs:-95 -> -100

hoThresholdsLevDL:-95 -> -90


Example 6

Handover not happening when DL signal level of neighbour much greater thanserving cellPower control DL activated

A

B

-6dB

-3dB

Power Control

-9dB


OSS

BSC

BSC

BSC

Plan

Background Loading of Radio Network Plan

Examples of wrong parameter set with impact on network operation/performance Background Plan


Examples of wrong parameter set with impact on network operation/performance Background Plan1. Few handovers after implementation of new adjacency plan

Only half of the plan has been downloaded. Half of the adjacencies missing.

2. High drop call rate in some sites after frequency hopping activation Some sites did not hop as some frequencies were not correctly set!

Important to verify network parameters through MML command!

In case not all parameters were changed correctly, use MML to implement the changes!


BTS BSC

MSC

SGSN GGSN Internet

PSTN

GPRS Backbone IP Network

GPRS Core

PRFILE+

PARAMETERS

PARAMETERS

PARAMETERS

Examples of wrong parameter set with impact on network operation/performance PRFILE, MSC, SGSN


Examples of wrong parameter set with impact on network operation/performance PRFILE, MSC, SGSN1. No queuing happening after activating it with BTS parameters.

Queuing should be activated also in BSC PRFILE (PREEMPT_USAGE parameter set to FF) and in MSC!

2. No rejection due to distance when activating the parametermsMaxDistanceInCallSetup.

The parameter DISTANCE_VERIFYING should be set to FF in BSC PRFILE

3. Tremendous amount of GPRS attaches. The detach timer set to 01h00 in the SGSN! Verify parameters in SGSN related to

implicit detach.

4. Mal functioning MS and Bad RxQual DL. DL DTX is activated in BSC level and by MSC parameters in cell level. It is not

recommended to activate DL DTX, specially when BB Hopping is being used.


Examples of wrong parameter set with impact on network operation/performance PRFILE, MSC, SGSN5. Paging request decrease after msPeriodicLocationUpdate setting

DEREGISTRATION TIMER < msPeriodicLocationUpdate!

Verify the parameters in BSC and MSC are correctly set.

E.g. of valuesBSC: msPeriodicLocationUpdate (BTS) 4-6hrsMSC: Implicit IMSI Detach Time Limit (VLR) 12 hrs

Loitering time (VLR) 24hrs


6. Tremendous amount of Location updatemsPeriodicLocationUpdate = 30 minutes

Examples of wrong parameter set with impact on network operation/performance BSC

Too manyLocation Updates

will cause SDCCH

congestion!


Conclusion

Do consistency checks: verify network parameters are as planned. Check configuration! Verify differences between OSS template and BSC default parameters! In some cases recommended values should be used instead of default values (e.g.

msPeriodicLocationUpdate: 0.5 -> 6) Verify value of sensitive parameters (e.g. DMAX, RxLevAccessMin) Adjust parameters to balance traffic (e.g. C2 in idle mode) Inter-related parameters (e.g. New Frequency Plan + BA List) Activate parameters in PRFILE, MSC and SGSN (e.g. queuing) When downloading background database, verify parameters through MML command

(e.g. new frequency plan)

Before suspecting anything, check the parameters active in the network!!!

78 2007 Nokia 13-468259 v1.0


CM Tools (Optional)Nokia NetActTM PlannerNokia NetActTM OptimizerRAC Tools


PLANNING & ROLLOUT

NetAct MultiRadio

Planner

NetAct Optimal Planner

NetAct Transmission

Planner

OPTIMIZATION

NetAct Optimal Planner

NetAct Optimizer

NetAct Service Optimizer

NetAct RAC

Field Measurements CM

DB

OPERATIONS NetAct SQM

NetAct Monitor (FM)

NetAct Inspector

NetAct Reporter

NetAct Traffica

F

M

C

D

R

P

a

s

s

i

v

e

P

M

A

c

t

i

v

e

P

M

PM DB

Nokia NetAct


MultiRadio Planner

Support GSM, GPRS, WCDMA Technology 2G-2.5G Radio network planning

General Planning Support : coverage, capacity and frequency planning Microcellular network planning Dual-band planning Frequency Hopping planning Data service planning AMR and HR support

3G Radio network planning Monte Carlo simulations

Nokia NetActTM Planner


Nokia NetActTM Optimizer

Perform Frequency allocation BCCH and TCH allocation RF Hopping allocation: MA-lists MAIO

parameters, HSN Other necessary parameters: TSC,

BSIC, all IDs

Perform adjacency optimisation Automated adjacency creation based on measurements Automated adjacency deletion based on KPIs


CMAnalyser

Radio Access Configurator Application Layer

CM Provisioner

CMEditor

CM PlanManager

Provided functionality: Plan import / export (XML file format) Actual network data export Plan identification and browsing User-defined plan status visualization and control Plan deletion

RAC Tools - CM Plan Manager


CMAnalyser


CM Provisioner

CMEditor

CM PlanManager

Provided functionality: Plan creation Plan content browsing Actual data visualization User configurable parameter views Parameter mass modification Template management Integrated GSM and 3G object/parameter editing

RAC Tools - CM Editor


CMAnalyser


CM Provisioner

CMEditor

CM PlanManager

Provided functionality: Predefined rules for consistency checks Rule result status information Defined action property in rules - automated correction, automated inconsistency reporting Integration with other Radio Access Configurator functionality Support of simultaneous consistency check operations

RAC Tools - CM Analyser


CMAnalyser


CM Provisioner

CMEditor

CM PlanManager

Provided functionality:User Requested / Scheduled Plan download to networkMaintaining the timestamp and originator of the last downloadDownload progress tracking and status feedbackSupport of simultaneous download operationsAccess control and authorization

RAC Tools - CM Provisioner

86 2007 Nokia 13-468259 v1.0


Thank you! RANOP / 2007

02 Network Configuration Optimization

Documents

Transcript of 02 Network Configuration Optimization