You are on page 1of 86

Network Configuration

Optimization
RANOP / 2007

Company Confidential
1

2007 Nokia

13-468259 v1.0

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

Company Confidential
2

2007 Nokia

13-468259 v1.0

CM Theory
BSC Tables
Default, Specific and Sensitive Parameters

Company Confidential
3

2007 Nokia

13-468259 v1.0

BSC Tables
BSC

MA, BA

BCF

SEG

BTS

ADCE

TRX
RTSL

Company Confidential
4

2007 Nokia

13-468259 v1.0

HOC

POC

Default, Specific, and Sensitive Parameters


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

Default Parameters:
Almost all parameters are
set to default values

Sensitive Parameters:

Define Default sets


Company Confidential
5

2007 Nokia

13-468259 v1.0

Changes in some default parameters


are quite dangerous as they may
have a critical impact on the network.
Care must be taken.

Default, Specific and Sensitive Parameters


1. Default parameters

Microsoft Excel
Worksheet

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

Company Confidential
6

2007 Nokia

13-468259 v1.0

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

Company Confidential
7

2007 Nokia

13-468259 v1.0

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

Company Confidential
8

2007 Nokia

13-468259 v1.0

Design default sets


Define default parameter sets - sector template

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

Defau
l
MML t sets con
si
d
recom efault valu st of
es +
me n d
ed va
lues

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
Company Confidential
9

2007 Nokia

13-468259 v1.0

Consistency Checks
OSS
o rt
Exp

Parameter
file

Imp

Master configuration
database

Consistency
check

or t

actual specific
actual default

CMDatabase
Database
CM
Imp

or t

rt
Expo
Parameter
file

Consistency
check

default
planned
import

Consistency
check

Parameter
file

Mapinfo

export

NetAct Planner
ODBC

Company Confidential
10

2007 Nokia

13-468259 v1.0

Planning
database

CM Process
Compare network design against network configuration
Default Parameter Check
Specific Parameter Check

Company Confidential
Confidential
Company
11

2007 Nokia

13-468259
2. Network Configuration
v1.0
Optimization / 2007-05-31 / Initials

Compare network design against network


configuration

Configuration
analysis

Real system
configuration

Planned system
configuration

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

Company Confidential
12

2007 Nokia

13-468259 v1.0

Default parameter check


Databases :
Master configuration
database

Note
:V
OK b erify defa
ef
u
chec ore doing lt setting
king
s are
in ca consiste
plann
s
n
e
cy
i ng w
as do paramete
r
ne by
other
s!!!

BSC
actual specific

BSC

OSS

actual default

Consistency
check

default
planned

BSC
Responsibilities :
Operational department

Planning department
Company Confidential
13

2007 Nokia

13-468259 v1.0

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 has


been done before any optimization, as this may result in undesired and
unexpected impacts on the network.

Company Confidential
14

2007 Nokia

13-468259 v1.0

Specific parameter check


Databases :

Master configuration
database

BSC
BSC

OSS

actual specific
actual default
default

BSC

planned

Consistency
check

Planning tool
e.g. NetAct

Responsibilities :
Operational department
Company Confidential
15

2007 Nokia

13-468259 v1.0

Planning department

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 correctly


implemented before any optimization
Company Confidential
16

2007 Nokia

13-468259 v1.0

CM Process
Database check

Company Confidential
Confidential
Company
17

2007 Nokia

13-468259
2. Network Configuration
v1.0
Optimization / 2007-05-31 / Initials

Database check
BSC

BSC

ADCE

BTS
HOC
POC

BTS
HOC
POC

BTS
HOC
POC
ADCE

Company Confidential
18

2007 Nokia

ADCE

13-468259 v1.0

BSC

Consistency
check

OSS

Database check
OSS 2

OSS 1

BSC A

Company Confidential
19

2007 Nokia

13-468259 v1.0

BSC B

BSC C

Database check
Database check of Actual Parameters
fAB
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.

Company Confidential
20

2007 Nokia

13-468259 v1.0

Database check
N-BCCH in ADCE table against FREQ in TRX table
TRX
BSC id

BTS id

TRX id

FREQ
fA

N-Neighbour
ADCE
fAB

Cell A

BSC id

Cell B

BTS id

N-LAC

N-Cell id

N-BCCH
fAB

fA

applies also to other cell parameters !!


Company Confidential
21

2007 Nokia

13-468259 v1.0

Database check
N-LAC, N-NCC, N-BCC in ADCE table against LAC, NCC,
BCC in BTS 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 network
LAC CI
FREQ PMAX NCC BCC
=== ===
=== ==== === ===
Source BSC (BTCHid)
Source BCF/BTCH
ADJ ADJ
ADJ ADJ ADJ ADJ
Target BSC (BTCHid)
Target BCF/BTCH
TGT TGT
TGT TGT TGT TGT
------------------ ---------------------------- ------ ------ ---- ---- --- --BSC1KUTOJA(6)
SUOSAA004 / SUOSAA1006 1
10010 600 30 7
2
BSC1KUTOJA(10)
LAAJAL010 /LAAJAL1010 1
10010 773 30 7
2
BSC1KUTOJA(7)
SUOSAA004 / SUOSAA1007 1
10010 600 30 7
2
BSC1KUTOJA(10)
LAAJAL010 /LAAJAL1010 1
10010 773 30 7
2
BSC1KUTOJA(9)
LAAJAL009 / LAAJAL1009 1
10010 600 30 7
2
BSC1KUTOJA(10)
LAAJAL010 /LAAJAL1010 1
10010 773 30 7
2
BSC1KUTOJA(9)
LAAJAL009 / LAAJAL1009 2
20003 594 30 7
7
BSC2UPS1(3)
3UPS001 /3UPSULTRA2003 2
20003 764 30 7
7
BSC1KUTOJA(9)
LAAJAL009 / LAAJAL1009 2
20002 600 30 7
7
BSC2UPS1(2)
3UPS001 /3UPSULTRA2002 2
20002 762 30 7
7
BSC2UPS1(1)
3UPS001 /3UPSULTRA2001 2
20001 776 30 7
7
BSC2UPS1(10)
5KOM005 / 5KOM2010
1
10009 605 30 7
2

Adjacency Discrepancies
(060) Example

Company Confidential
22

2007 Nokia

13-468259 v1.0

Database check
Adjacencies to non-existing cells
OMC 2

OMC 1

Cell C

Cell B
Cell A
BSC 2
BSC 1

Cell B is deleted but incoming adjacencies


were not removed
Cell C is not known in OMC Area 1 database
Company Confidential
23

2007 Nokia

13-468259 v1.0

Database check
Adjacencies 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 cells
Source
Source
Source ADJ.CELL ADJ.CELL
BSC (BTCH id)
BCF/BTCH
BTCH int_id
LAC
CI
-------------------------------- ---------- -------- -------BSC533(48)
BSC533
118112
22871
1022
Cid 2413
BSC552(24)
102679
22870
3291
Adjacencies to Non-existing or
BSC553(1)
97461
22870
3301
Foreign Cells (065) - Example
BSC553(2)
97769
22870
3301
BSC553(4)
98375
22870
3301
BSC553(10)
99316
22870
3142

Company Confidential
24

2007 Nokia

13-468259 v1.0

CM Process
Consistency parameter checking

Company Confidential
Confidential
Company
25

2007 Nokia

13-468259
2. Network Configuration
v1.0
Optimization / 2007-05-31 / Initials

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

Company Confidential
26

2007 Nokia

13-468259 v1.0

Cells with co-channel and adj-channel frequencies

Cell A

-6dB -9dB

Cell B
B

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.

Company Confidential
27

2007 Nokia

13-468259 v1.0

Non symmetrical adjacencies


Find all non symmetrical adjacencies :
cell B is neighbour of Cell A
cell A is not neighbour of Cell B

Cell A

Company Confidential
28

2007 Nokia

13-468259 v1.0

Cell B

Neighbours with co-channel and adj-channel


frequencies or co-BSIC, co-BCCH
Cell B
f=10

f=10, BSIC=2,2

Cell A
f=24

Cell C
f=10, BSIC=2,2

Neighbours with co-BSIC, coBCCH:


Might generate ghost-access and
HO drop calls.
High sdcch abis failure and high
handover failure could be indicators
for this case.
Company Confidential
29

2007 Nokia

13-468259 v1.0

f=24
f=9,10,11

Neighbours with co-channel or


adjacent channel frequencies:
Will cause interference between
neighbour cells

Check BCCH-BSIC and BCCH reuse distance


Small distances may be dangerous!
FREQ = 234
BSIC = 42

FREQ = 234

FREQ = 234
BSIC = 42

Reuse 4/12
Company Confidential
30

2007 Nokia

13-468259 v1.0

Synchronised handover
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
Non- Synchronized HO

Synchronized HO

Site A
Company Confidential
31

2007 Nokia

13-468259 v1.0

Site B

CM Process
Review Neighbour Plan

Company Confidential
Confidential
Company
32

2007 Nokia

13-468259
2. Network Configuration
v1.0
Optimization / 2007-05-31 / Initials

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.
Company Confidential
33

2007 Nokia

13-468259 v1.0

Theoretical Model
Cell
Adj Cells
Opt adj cells
Other cells

Company Confidential
34

2007 Nokia

13-468259 v1.0

Double BA List

Parameter
initialFrequency

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

bCCHAllocation-ID
bCCHAllocationList

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

Company Confidential
35

Value

2007 Nokia

13-468259 v1.0

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 BTS
Among 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 Measurement
Both 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.
Company Confidential
36

2007 Nokia

13-468259 v1.0

Undefined Adjacent Cell Measurement

Network Doctor 073

Number of samples for


calculating the average DL
signal strength
Average strength of the downlink signal
received from an undefined adjacent
cell
BCCH, NCC, BCC of adjacent cell
Company Confidential
37

2007 Nokia

13-468259 v1.0

Channel finder measurement


D

D
Serving
Cell

UD
D

D
Compare dBm values
between
serving cell and UD

D
UD

D = Defined Adjacent Cell


UD = Undefined Adjacent Cell
Company Confidential
38

2007 Nokia

13-468259 v1.0

Channel finder measurement


Decision mechanism
Meas
report
Undefined Adjacent Cell dBm - Serving Cell dBm
(update current counter)

Values after 1
hour measurement
period

Counter 1

Counter 2

Counter 3

(dBm value below 0)

( 0 < dBm value < 6)

(dBm value >6)

500

5000

Dominating

Good candidate for a defined cell

3600 sec / 0.48 sec = 7500 samplings during one hour


Company Confidential
39

2007 Nokia

13-468259 v1.0

2000

Adjacent cell measurements


Network Doctor 153

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.
Company Confidential
40

2007 Nokia

13-468259 v1.0

CM Process
Review Frequency plan

Company Confidential
Confidential
Company
41

2007 Nokia

13-468259
2. Network Configuration
v1.0
Optimization / 2007-05-31 / Initials

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

Company Confidential
42

2007 Nokia

13-468259 v1.0

Review Frequency plan


BCCH-BSIC 850
20

18

16

14

12

50
#

BCCH-BSIC

40

Optimize BCCH-BSIC reuse in


cities (no repetitions)

30

20

10

0
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 157
BCCH 850

Company Confidential
43

2007 Nokia

13-468259 v1.0

157-40

156-71

156-24

153-55

153-08

152-39

151-70

151-23

150-54

150-07

148-38

147-69

147-22

146-53

146-06

145-37

144-68

144-21

143-52

143-05

142-36

141-67

141-20

140-51

140-04

139-35

138-66

138-19

137-50

137-03

136-34

135-65

135-18

134-49

134-02

0
133-33

60

132-64

132-17

70

131-48

131-01

80

130-32

128-00

90

129-63

129-16

BCCH-850

10

128-47

Optimize BCCH reuse

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

Company Confidential
44

2007 Nokia

13-468259 v1.0

Examples of wrong parameter set with impact on


network operation/performance call setup, qual,
bands
1. 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
Company Confidential
45

2007 Nokia

13-468259 v1.0

Example 1a
No calls happening in a cell:
The cell has been barred
Handover


Call Setup
S
(C YS
ell IN
Ba FO
rrA 3
cc (B
es CC
s= H
ye )
s)

Company Confidential
46

2007 Nokia

13-468259 v1.0

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

Company Confidential
47

2007 Nokia

13-468259 v1.0

MSC does not find


(LAC, CI) in its
database

Example 1c
No calls happening in a cell:
MsMaxDistanceInCallSetup (DMAX) = 0
Despite the coverage
of the cell, no calls will
be established!

DMAX = 0

Company Confidential
48

2007 Nokia

13-468259 v1.0

Call Setup

RxLevel =
-70 dBm

Example 2a
Very few calls happening in a cell:
RxLevAccesMin
Mapping

OSS database BSS MML

Lowest range

-110 dBm

-109 dBm

...

...

62

-48 dBm

63

-47 dBm

Highest range

Cell coverage

RxLevAccessMin = -47 dBm

Company Confidential
49

2007 Nokia

13-468259 v1.0

Be careful when setting


parameter through xml or dat
file! 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 correct
value)

Company Confidential
50

2007 Nokia

13-468259 v1.0

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

lta
e
D

Parameter
value
bsTxPwrMax
bsTxPwrMin
minMsTxPower
msTxPwrMax

Value_______Default
0 30 dB
0 30 dB
0 36 dBm
0 36 dBm

0 dB
30 dB
0 dB

Attenuation Values (dB)


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

lu
o
s
Ab

te

Power Values (dBm)


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

Company Confidential
51

2007 Nokia

13-468259 v1.0

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

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

RDIV = Y

Uplink Diversity
improves quality of
signal received.

Company Confidential
52

2007 Nokia

13-468259 v1.0

Example 5

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


Idle Mode: C2 parameters not set properly (temporaryOffset, penaltyTime)

BCCH
BCCH

slow moving mobile


1800: micro-Layer

Company Confidential
53

2007 Nokia

13-468259 v1.0

fast moving mobile


900: macro-layer

Examples of wrong parameter set with impact on


network operation/performance upgrade
1.

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

Company Confidential
54

2007 Nokia

13-468259 v1.0

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

Company Confidential
55

2007 Nokia

13-468259 v1.0

Example 1b

High drop call rate after upgrading a cell from 4 to 6 TRXs:


TRXs with different power without ICE activated
Coverage
BCCH - TRX

Capacity
Traffic - TRX

MS in a region covered only by Coverage-TRX, ICE not activated.


Result: BTS may allocate a TSL in Capacity TRX. Call will drop.
Company Confidential
56

2007 Nokia

13-468259 v1.0

Example 1b
TRXs with different power
TRX RF Units

TX
RX

main
div

+3dB

LNA

LNA

TX
RX

main
div

TX
RX

main
div

TX
RX

main
div

2007 Nokia

LNA

WBC
LNA

Company Confidential
57

WBC

13-468259 v1.0

Duplexer

main
div

Duplexer

TX
RX

Duplexer

main
div

X
X
X

Dual Duplex Unit


Duplexer

TX
RX

Receive Multicouplers
& Wideband Combiners

Antennas

TX/RX ant

X
X
X
TX/RX-div
ant

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 from


different BSCs

ADCE table has not been updated for other BSC

Company Confidential
58

2007 Nokia

13-468259 v1.0

Example 1
Drop call rate increase after new frequency plan implementation:
In the meantime, measurementBcchAllocation has been changed to idle and MA list
defined with old BCCH frequency band
OLD MA List
BCCH

TCH

BCCH

TCH

TCH

OLD FREQUENCY PLAN

NEW FREQUENCY PLAN

These BCCH frequencies will not be measured by old MA List


These TCH frequencies will be wrongly measured

Company Confidential
59

2007 Nokia

13-468259 v1.0

Example 2

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


After frequency hopping retune, some BCCH frequency equal to TRX frequency
of non-BCCH TRXs
After changing TRX frequency, verify BSIC and TSC (Training Sequence Code)
is changed accordingly.

Company Confidential
60

2007 Nokia

13-468259 v1.0

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

SEG
EGENA = Y
(E)GPRS territory

GTRX = Y
GTRX = Y

Company Confidential
61

2007 Nokia

13-468259 v1.0

SEG
BTS
EDGE TRX(s)
NON-EDGE
TRX(s)

EGENA = Y

BTS

(E)GPRS territory
EDGE TRX(s)
GTRX = Y
GTRX = N

NON-EDGE
TRX(s)

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
SEG
EGENA = Y
1

BTS

(E)GPRS territory
EDGE TRX(s)
GTRX = Y
GTRX = N

NON-EDGE
TRX(s)

Add TRX-1 to EDAP pool

Company Confidential
62

2007 Nokia

13-468259 v1.0

EDAP pool

Example 4
No handover happening after frequency retune between 2 cells from different
BSCs:
Frequency retune has been done with MML command. ADCE table has not been
updated for incoming adjacencies belonging to other BSCs
TRX
BSC id

BTS id

TRX id

FREQ
fA

N-Neighbour
fAB

Cell A
fA

Company Confidential
63

2007 Nokia

13-468259 v1.0

ADCE

Cell B

BSC id

BTS id

N-LAC

N-Cell id

N-BCCH
fAB

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 than
serving cell

POC DL activated

Company Confidential
64

2007 Nokia

13-468259 v1.0

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.
No Measurement reports of Cell
B are sent to BSC. So no HOs
occur from Cell A to Cell B

Plmn permitted 0 = No
.
Plmn permitted 3 = Yes
Plmn permitted 4 = No

Cell A
NCC 3

Cell B
NCC 4

Set Plmn permitted 4 = Yes

Plmn permitted 7 = No

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).
Company Confidential
65

2007 Nokia

13-468259 v1.0

Example 2
High Handover failures after implementation of new adjacency plan
All adjacencies have been implemented with synchronised parameter set
to yes. HOs between cells of different sites will probably fail.
Synchronized Handover
MS

NETWORK
ACTIVE CALL
HANDO CMD

Old Channel, Old Cell

Set SYNC = YES


only between
sectors of the
same site.
SYNC = NO

HANDO ACC

New Channel, New Cell

SYNC = YES

PHYS INFO
HANDO COM
ACTIVE CALL

Company Confidential
66

2007 Nokia

Recommendation is to have Sync HO within BTSs in the


same BCF and Non Sync HO between BTSs in different
BCFs.

13-468259 v1.0

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

Ho Margin Qual = -4

PBGT margin = 6dB

B
Ho Margin Qual = 0
(MML Default)
In an interfered cell, despite high signal strength, quality is not good. So HO Margin Qual
should permit HO to a cell that despite its lower signal strength, may have a better quality.

Company Confidential
67

2007 Nokia

13-468259 v1.0

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

Cell A

Company Confidential
68

2007 Nokia

13-468259 v1.0

Cell B

FREQ=10

FREQ=10

BSIC = 33

BSIC = 33

Example 5
High number of handovers. hoThresholdsLevUL = hoThresholdsLevDL
Quality

hoThresholdsLevUL,
high thresholds will
anticipate HOs:

-95 -> -100

Level Ho

No Action Needed

Quality Ho

hoThresholdsLevDL:
-95 -> -90

Interference Ho

HoThresholdInterferenceUL/DL
HoThresholdLevUL

Company Confidential
69

2007 Nokia

13-468259 v1.0

HoThresholdLevDL

HoThresholdLevUL/D
L

-50

-52

-54

-56

-58

-60

-62

-64

-66

-68

-70

-72

-74

-76

-78

-80

-82

-84

-86

-88

-90

-92

-94

-96

-98

-100

-102

-104

-106

-108

-110

dBm

Example 6
Handover not happening when DL signal level of neighbour much greater than
serving cell
Power control DL activated

A
Power Control
-6dB
B
-3dB

Company Confidential
70

2007 Nokia

13-468259 v1.0

-9dB

Examples of wrong parameter set with impact on


network operation/performance Background Plan
Background Loading of
Radio Network Plan

BSC

Plan

OSS

BSC

BSC

Company Confidential
71

2007 Nokia

13-468259 v1.0

Examples of wrong parameter set with impact on


network operation/performance Background Plan
1. 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!

Company Confidential
72

2007 Nokia

13-468259 v1.0

Examples of wrong parameter set with impact on


network operation/performance PRFILE, MSC,
SGSN
PARAMETERS

MSC

BTS

BSC

PSTN

GPRS Core

SGSN

GPRS
Backbone
IP Network

PRFILE
+
PARAMETERS
PARAMETERS

Company Confidential
73

2007 Nokia

13-468259 v1.0

GGSN

Internet

Examples of wrong parameter set with impact on


network operation/performance PRFILE, MSC,
SGSN
1.

No queuing happening after activating it with BTS parameters.

2.

No rejection due to distance when activating the parameter


msMaxDistanceInCallSetup.

3.

The parameter DISTANCE_VERIFYING should be set to FF in BSC PRFILE

Tremendous amount of GPRS attaches.

4.

Queuing should be activated also in BSC PRFILE (PREEMPT_USAGE parameter set


to FF) and in MSC!

The detach timer set to 01h00 in the SGSN! Verify parameters in SGSN related to
implicit detach.

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.

Company Confidential
74

2007 Nokia

13-468259 v1.0

Examples of wrong parameter set with impact on


network operation/performance PRFILE, MSC, SGSN
5. Paging request decrease after msPeriodicLocationUpdate setting
DEREGISTRATION TIMER < msPeriodicLocationUpdate!
Verify the parameters in BSC and MSC are correctly set.
E.g. of values
BSC:

msPeriodicLocationUpdate (BTS)

MSC: Implicit IMSI Detach Time Limit (VLR)


Loitering time (VLR)

Company Confidential
75

2007 Nokia

13-468259 v1.0

4-6hrs
12 hrs
24hrs

Examples of wrong parameter set with impact on


network operation/performance BSC
6. Tremendous amount of Location update
msPeriodicLocationUpdate = 30 minutes

Too many
Location Updates
will cause
SDCCH
congestion!

Company Confidential
76

2007 Nokia

13-468259 v1.0

Conclusion
Before suspecting anything, check the parameters active in the network!!!
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)

Company Confidential
77

2007 Nokia

13-468259 v1.0

CM Tools (Optional)
Nokia NetActTM Planner
Nokia NetActTM Optimizer
RAC Tools

Company Confidential
78

2007 Nokia

13-468259 v1.0

Nokia NetAct
PLANNING & ROLLOUT

OPERATIONS

OPTIMIZATION

NetAct
SQM

NetAct
Transmission
Planner

NetAct
Service Optimizer

NetAct
Optimal Planner

NetAct
Optimizer

NetAct
MultiRadio
Planner

NetAct
Monitor (FM)

NetAct
Reporter

Active PM

Passive PM

CDR

NetAct
Optimal Planner

NetAct
Inspector

NetAct
Traffica

FM

P
M
D
B

NetAct
RAC

Field
Measurements

Company Confidential
79

2007 Nokia

13-468259 v1.0

C
M
D
B

Nokia NetActTM Planner


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

Company Confidential
80

2007 Nokia

13-468259 v1.0

Nokia NetActTM Optimizer


Perform adjacency optimisation
Automated adjacency creation based on measurements
Automated adjacency deletion based on KPIs
Perform Frequency allocation
BCCH and TCH allocation
RF Hopping allocation: MA-lists MAIO
parameters, HSN
Other necessary parameters: TSC,
BSIC, all IDs

Company Confidential
81

2007 Nokia

13-468259 v1.0

RAC Tools - CM Plan Manager


Radio Access Configurator Application Layer
CM Plan

CM

CM

CM

Manager

Editor

Analyser

Provisioner

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

Company Confidential
82

2007 Nokia

13-468259 v1.0

RAC Tools - CM Editor


Radio Access Configurator Application Layer
CM Plan

CM

CM

CM

Manager

Editor

Analyser

Provisioner

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

Company Confidential
83

2007 Nokia

13-468259 v1.0

RAC Tools - CM Analyser


Radio Access Configurator Application Layer
CM Plan

CM

CM

CM

Manager

Editor

Analyser

Provisioner

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

Company Confidential
84

2007 Nokia

13-468259 v1.0

RAC Tools - CM Provisioner


Radio Access Configurator Application Layer
CM Plan

CM

CM

CM

Manager

Editor

Analyser

Provisioner

Provided functionality:
User

Requested / Scheduled Plan download to network

Maintaining
Download
Support
Access

Company Confidential
85

2007 Nokia

13-468259 v1.0

the timestamp and originator of the last download

progress tracking and status feedback

of simultaneous download operations

control and authorization

Thank you!
RANOP / 2007

Company Confidential
86

2007 Nokia

13-468259 v1.0