2G Optimization

KPI case
Handover Control parameter
Power Control Parameter
Measurement processing
Radio resource Management
Idle Parameter Optimization
Radio Resource Administration
Radio Resource Administration
Basic TDMA Structure 5
4

e
3

tim
2
Physical channel 1
e.g. allocated to one 0
subscriber with FR voice 7
and no frequency hopping 6
5
4 TDMA frame
3 = 8 timeslots
2 ( 0.577ms * 8 = 4.615 ms)
1
0
7
6
5 2 2 2
4
3 TDMA frame
2
1
0
frequency
200 kHz
GSM Channel Organization

Logical Channels
for transport of specific content

mapping

MS Physical Channels
transport medium Base Station
Subsystem
Physical channel parameters
ARFCN
Time slot number
Frequency hopping algorithm
Logical Channels
FCCH Frequency Correction Channel

SCH Synchronisation Channel

DL
BCH
BCCH Broadcast Control Channel

CBCH Cell Broadcast Channel

Common
Channels
DL
PCH Paging Channel
UL
CCCH RACH Random Access Channel
DL
AGCH Access Grant Channel

SDCCH Stand alone Dedicated Control Channel

UL/DL
DCCH SACCH Slow Associated Control Channel

FACCH Fast Associated Control Channel

Dedicated
Channels
FR/HR Full rate / Halft rate TCH
UL/DL
TCH EFR Enhanced Full rate TCH

AMR FR/HR Adaptive multirate TCH (FR/HR)

Signalling Channel Mapping
(BCCH +CCCH/9)
Downlink
51 TDMA frames = 235 ms
1 51

f s f sf f s f s f s -

BCCH CCCH CCCH CCCH CCCH CCCH CCCH CCCH CCCH CCCH

Uplink
51 TDMA frames = 235 ms
1 51

r r r r r r r r r r r r rf r r r r r r r r r rf r r r r r r r r r rf r r r r r r r r r rf r r r r r r r r

f = FCCH, s = SCH, r = RACH TDMA frame

- = dummy burst
Signalling Channel Mapping
(BCCH + SDCCH/4 + SACCH/C4)
Downlink
51 TDMA frames = 235 ms
1 51

f s f sf f s f s f s -

BCCH CCCH CCCH CCCH

SDCCH 0 SDCCH 2 SACCH
SDCCH 1 SDCCH 3 0/2 SACCH
1/3
Uplink
51 TDMA frames = 235 ms
1 51

rr f r r r r r r r r rf r r r r r r r r r rf r r r r f r r

SACCH SDCCH 0 SDCCH 2

SDCCH 3 2/0 SACCH SDCCH 1
3/1
f = FCCH, s = SCH, r = RACH TDMA frame
- = dummy burst
Traffic Channel Mapping
Full Rate Traffic Channel Configuration (UL & DL)
26 TDMA frames = 120 ms

t t t t t t t t t t t t sf t t t t t t t t t tf t t i

1 26
t = full rate TCH, s = SACCH/T, i = idle TDMA frame

Half Rate Traffic Channel Configuration (UL & DL)

26 TDMA frames = 120 ms

t t t t t t s t t t t t t
f f
T T T T T T T T T T T T S
...

1 26
t = half rate TCH, s = SACCH/T (first user)
T = half rate TCH, S = SACCH/T (second user) TDMA frame
Signalling Channel Mapping
(SDCCH/8 +SACCH/C4)
Downlink
51 TDMA frames = 235 ms
1 51

f i i i

SDCCH 0 SDCCH 2 SDCCH 4 SDCCH 6 SACCH SACCH

SDCCH 1 SDCCH 3 SDCCH 5 SDCCH 7 0/4 SACCH 2/6 SACCH
1/5 3/7
Uplink
51 TDMA frames = 235 ms
1 51

f fi i i

SACCH SDCCH 0 SDCCH 2 SDCCH 4 SDCCH 6 SACCH

SACCH 6/2 SACCH SDCCH 1 SDCCH 3 SDCCH 5 SDCCH 7 4/0
5/1 7/3

i = idle TDMA frame

Signalling Channel Mapping
• New improved CCCH features in RG10
• BSS20738 CS Paging Coordination in NMO II
• BSS21538 Extended CCCH
• Extended CCCH can be allocated to timeslot 2,4,6

• BSS101411 Extended BCCH

• For example Uncombined BCCH
Channel Mapping
MO Class TR/RTSL
Parameter Setting
Parameter channelxType (CHx) where x = 0…7

Channel configuration defined by parameter channelType

TCHF (0) = full rate traffic channel

TCHH (1) = half rate traffic channel
TCHD (2) = dual rate traffic channel
SDCCH (3) = standalone (SDCCH/8)
MBCCH (4) = broadcast control channel
MBCCHC (5) = BCCH + SDCCH/4
MBCCB (7) = BCCH + SDCCH/3 with CBCH
SDCCB (8) = SDCCH/7 with CBCH
NOTUSED (9) = timeslot has no radio definition or Abis allocation
ERACH (10) = random access channel of extended area
EGTCH (14) = EGPRS packed data traffic channel for extended area
LRTCH (15) = long reach traffic channel
Note:
• Some values not allowed in certain tsl (e.g. TSL0
can’t have value 8)
• PBCCH is not supported in S13 and onwards
Paging Channel (PCH) Parameters
Mobile terminating call -> MSC performs paging

MS identifies paging message with the IMSI/TMSI

MS listens to own paging group only

SEG-BTS parameters
MO Abbreviated Range Description Default BSC - MML
Class Name And Step value Name
BTS noOfMFramesB 2...9, step Defines the number of multiframes between 4 MFR
etweenPaging 1 two transmissions of the same paging
message to the MSs of the same paging
group.

MSC parameters

Repaging Interval (INT) 0.5s…10s Time between consecutive paging

attempts
Repaging Attempts (AT) 0…5 Number of paging repetitions

Buffering

BTS stores up to 8 paging messages of the MSC in page group buffer

BTS sends paging messages to MS according noOfMultiframesBetweenPaging
RACH Parameters
Mobile sends channel requests to BTS separated by random time intervals in case of no answer!

Parameters
MO Abbreviated Range And Step Description Default BSC - MML
Class Name value Name

BTS maxNumberRetra 1,2,4,7 Maximum number of retransmissions on the RACH 4 RET

nsmission that the MS can perform.

BTS nbrOfSlotsSpread MML Range: The number of TDMA frames over which 10 SLO
Trans 3..12, 14, 16, 20, retransmission is spread on the RACH (random
25, 32, 50 access channel)

Random time interval between consecutive retransmissions

t = S + random [0,.. numberOfSlotsSpreadTrans – 1] RACH slots

S depends on numberOfSlotsSpreadTrans
signalling channel mapping
numberOfSlotsSpreadTrans = 10 (CCCH + SDCCH combined or not in one multi frame)
signalling channel mapping = not combined  S
= 58
Therefore t = 58..to..67 RACH slots
time channel requests
AGCH Parameters
Network gives the MS dedicated resources

Downlink CCCH blocks

• PCH can be used for AGCH messages

• AGCH cannot be used for PCH messages

Reservation of CCCH blocks for AGCH

noOfBlocksForAccessGrant (AG) 0..7 possible number, if CCCH and SDCCH are not combined
1..7 possible number, if CBCH is used in non combined
configuration
0..2 possible number, if CCCH and SDCCH are combined

Preference of AGCH messages on PCH

noOfBlocksForAccessGrant  0 PCH can be used only, if no paging messages have to be

send
= 0 AGCH messages have higher priority than PCH ones

Number of paging groups

N = (number of CCCH blocks – noOfBlocksForAccessGrant) * noOfMultiframesBetweenPaging

Paging Capacity
Example
• Combined CCCH / SDCCH configuration BTS 3 MS

• noOfBlocksForAccessGrant = 1  2 CCCH blocks for PCH

Paging_Request

• 3 MSs paged per paging message  3 pages per block

BTS 3 MS
• 2 blocks per multi frame  3 * 2 = 6 pages per multiframe

Paging_Request
• Number of pages per hour  3600 s / 0.235 s * 6 = 91915

• Avg of 2 pages required per MS  91915 / 2 = 45957 MSs per hour

SDCCH Signalling Capacity
Example with call Establishment & Location Update
• Cell with 325 subscribers
• 1 call per subscriber once in a hour
• 1 location update (LU) per subscriber once in 2 hours

• Duration of call assignment = 4 s  4 s / 3600 s = 1.11 mErl on SDCCH per subscriber

• 325 subscribers  325 * 1.11 mErl = 0.3607 Erl on SDCCH

• Reservation time for LU = 5s  5 s / 7200 s = 0.69 mErl on SDCCH per subscriber

• 325 subscribers  0.2242 Erl on SDCCH

• Total SDCCH traffic  0.3607 Erl + 0.2242 Erl = 0.5849 Erl

• Blocking probability = 1%  4 SDCCHs required  SDCCH combined with CCCH can be used (MBCCHC)
SDCCH Signalling Capacity
Example including SMS

• Same cell with 325 subscribers

• Additional SMS traffic of 1 mErl per subscriber

• 325 subscribers  325 * 1 mErl = 0.325 Erl on SDCCH

• Total SDCCH traffic  0.5849 + 0.325 Erl = 0.9099 Erl

• Blocking probability = 1%  5 SDCCHs required  not combined with
CCCH (MBCCH)
Base Station Identity Code

Base Station Identity Code BSIC = Network Colour Code NCC + Base Station Colour Code BCC

bsIdentityCode Setting of BSIC

NCC 0..7, distinguishes between PLMNs

BCC 0..7, distinguishes between clusters

BSIC + frequency channel  unique identity of adjacent cell

f1 bcc = 2
bcc = 1 f2
f1
f3
f1
bcc = 3
Defining Frequency carrier number

Example: GSM 900

Absolute radio frequency carrier number ARFCN

890 915 935 960

1 2 3 4 123 124 1 2 3 4 123 124

duplex distance

200 kHz

uplink direction downlink direction

Frequency Reuse

Frequency to be used by TRX (must be unique within a BTS)

initialFrequency (FREQ) 1…1023 Setting of ARFCNs

GSM 800: 128 .. 251

GSM 900: 1..124 and 975..1023, 0
GSM 1800: 512..885
GSM 1900: 512..810
f2
f2 f1 f4
f1 f4 f3
f3 f5 f7
f5 f7 f6
f6 f2
f1 f4
f3
f5 f7
f6
Principle of Frequency Hopping
Frequency hopping techniques

hoppingMode (HOP) BB,RF,N

BB = base band hopping (1)
RF = RF hopping (2)
N = no frequency hopping at all (0)

Frequency
Call is transmitted through several frequencies to
• average the interference (interference diversity)
• minimise the impact of fading (frequency diversity)

F1

F2

F3

Time
Base Band Hopping
TRXs do not hop
Physical channels moved from one TRX to another

Hopping sequence
hoppingSequenceNumber (HSN) 0..63
0 = cyclic hopping
1..63 = pseudorandom hopping

Baseband Hopping

0 1 2 7 Timeslot

TRX 1 BC f1 HSN1 (BB hopping group 1 and RF hopping)

CH
Timeslot 0 hops over TRXs 2-4 only
TRX 2 f2
BCCH does not hop
TRX 3 f3

TRX 4 f4 HSN2 (BB hopping group 2)

Timeslots 1-7 hop over all TRXs
RF Hopping
Standard technique
All TRXs hop except TRX1 (provides BCCH)
Up to 63 frequencies available defined by mobile allocation list -> better hopping gain

mobileAllocationList Setting of ARFCN values usedMobileAllocation (MAL)

0,1...2000 0 = BTS detached from any list
1..2000 = indicates list which shall be used

0 1 2 7 Timeslot
TRX 1 BC
CH f1 – no hopping

TRX 2

f2,f3..fn – hopping according

TRX 3 mobile allocation list
One hopping sequence
number only
TRX 4
RF Hopping
Freeform Hopping
Standard technique

9 hopping hopping frequencies MAI = 0..8

But 3 frequencies available for every TRX only

Freeform hopping

For every sector same

mobile allocation list
hopping sequence number
frame number (frame synchronization)

For every sector different

starting points for hopping sequence
possible by mobile allocation index offset

maioOffset (MO) 0..62

setting of MAIO

9 hopping hopping frequencies MAI = 0..8

9 frequencies available for every TRX
RF Hopping
Flexible MAIO Management
Freeform hopping

• Not adequate for MA list with consecutive ARFCN

values
• Avoids co-channel interference but not adjacent
channel interference

Flexible MAIO management

MAIO increases with constant step size from one TRX

to the next one

maioStep (MS)1..62

maioOffset = 0, 6, 12 for sector 1, 2, 3

maioStep = 2
18 frequencies required (2 * number of hopping TRXs)
RF Hopping (Tight Frequency Reuse)
Freeform hopping Flexible MAIO management
MAIO Offset MAIO Offset + MAIO Step

Band allocation: Band allocation:

BCCH BCCH

MA list MA list
Non-adjacent ARFCN Consecutive ARFCN

MA list and BCCH frequency planning required Only BCCH frequency planning required
Changing Frequency Plan

• Plan downloaded to BSC/BTSs via MML or GUI

• File-based plan provisioning
• Immediate Plan activation method

BSIC / TSC
Frequencies
Frequency hopping setting
Intelligent underlay overlay TRX settings
Idle Mode Operation
 Idle Mode Operation
I When?

• When the MS is switched ON

• When there is no dedicated connection MS switched ON

Why?
• To camp on the best suitable cell
Search RF channels
to find BCCH carrier
Why to camp on a specific cell?
• For MS to receive system info from the NW on DL
• For MS to be able to initiate a call whenever needed
• For the NW to be able to locate the MS when there is a Check that the PLMN
MT call/SMS & cell is allowed

Idle Mode Tasks MS camps on

the best
suitable cell
• PLMN selection
• Cell selection & re-selection
• Location updates See slide 10 for detail
ID’s and ID Codes
Parameter Value

LAI (locationAreaId)
• MCC (Mobile Country Code) 0 … 999
• MNC (Mobile Network Code) 0 … 99,
0… 999 (optional 3-digit MNC)
• LAC (Location Area Code) 1 … 65533

BSIC (bsIdentityCode)
• NCC (Network Colour Code) 0…7
• BCC (BTS Colour Code) 0…7

CI (cell-ID 0 … 65535

TSC (trainingSequenceCode) 0…7

CGI (Cell Global Identity) MCC + MNC + LAC + CI

States and State Transition for Cell Selection

go here when no SIM in MS SIM inserted in MS

Any cell 1
selection

no suitable no suitable
cell found
cell found cell found

Choose cell suitable cell found Camped trigger Any

on cell re-
any cell cell selection
return
to idle leave re-selected
mode idle cell found
mode on selected
Connected mode PLMN
(emergency call
only)

2
(adopted from TS 43.022 V5.1.0 chap. 6)
States and State Transition for Cell Selection
go here whenever a
new PLMN is selected

2 no BA list stored BA list stored

1 for PLMN
for PLMN

Normal no suitable cell found Stored list

cell selection cell selection

no suitable
cell found suitable cell found suitable cell found

Choose cell suitable cell found trigger

Camped Normal
normally cell re-selection
return Suitable cell
to idle re-selected
leave
mode
idle no suitable
mode cell found
• IMSI unknown
Connected • Illegal MS
mode • PLMN not allowed
no 2
suitable
cell
found
(adopted from TS 43.022 V5.1.0 chap. 6)
Normal Cell Selection
Search all the RF channels, take samples during
3-5 s and calculate averages. And put them in
ascending order with respect to signal level.
Then tune to the strongest RF channel.

Search for the frequency correction burst in that Tune to the next highest
carrier in order to verify if it is a BCCH carrier RF channel which is not
tried before

No
Is it a BCCH
carrier?

Yes

Try to synchronize to the carrier and read

the BCCH data

No
Is it a correct
PLMN ?

Yes

Yes
Is the cell barred?

No
No
Is C1>0

Yes
Camp on the cell
Pathloss Criterion C1 for Cell Selection
and Reselection
0..63 0..31
C1 = A – max(B,0)
= RLA_C – RXLEV_ACCESS_MIN – max(MS_TXPWR_MAX_CCH – P , 0)

RLA_C = avg received RxLev on BCCH

P = MS max output power

I am
outside

I am inside, but 0)
,
have not enough x(B
power ma
Cell Selection with C1
In case the neighbouring cells belong to different Location Area, a hysteresis is
applied with C1 criteria
• minimizing ping-pong cell reselections
• cellReselectHysteresis (HYS)(BTS) (0…14 dB)

Cell1 Cell2
LAC1 LAC2

C1 ( Cell1) C1 (Cell2) A= 4 dB
B= 6 dB
C= 8 dB
A B C
Pathloss Criterion C2
0 .. 126 dB 0, 10, 20, 30, 40, 20 .. 640 s
step size: 2 dB 50, 60,  dB step size: 20 s

C1 + CELL_RESELECT_OFFSET – (TEMPORARY OFFSET * H(PENALTY_TIME - T))

C2 = for PENALTY_TIME  640 s
< C1 if temporary offset big for PENALTY_TIME = 640 s

C2
no TEMPORARY OFFSET

serving cell: C1
• C2:
new candidate
CELL_RESELECT_OFFSET
List of 6 = former serving
strongest cell
T
carriers:
• C2: C2
• C2:
• C2: C1
• C2:
• C2:
• C2: CELL_RESELECT_OFFSET
new candidate
= formerly non-
serving cell TEMPORARY OFFSET
T
PENALTY_TIME
Cell Reselection Based on Pathloss
Criterion C2

C2
cell 1 cell reselection &
cell 3
location update

cell
reselection cell 2

CELL_RESELECT_
HYSTERESIS (HYS)

5 seconds 5 seconds time

LAC = A LAC = B
Cell Reselection Based on Pathloss
Criterion C2
=30 Cell "A" (Serving Cell)
=25 Cell "B"
Road
Macro 900 "C" C1 =5 Cell "C"
=50 Cell "D"

C2 = C1 + cellReselectOffset -
Micro 900 "D"
temporaryOffset*H(penaltyTime-T)
Macro 1800 "B"
=30 + 0 (H(x)=0, serving cell) Cell "A"
=25 + 20 - 30*H(20 - T) Cell "B"
C2 =5 + 0 - 0*H(20 - T) Cell "C"
=50 + 0 - 30*H(40 - T) Cell "D"

Cell "A" Cell "B" Cell "C" Cell "D"

cellReselectOffset 0 dB 20 dB 0 dB 0 dB

temporaryOffset 0 dB 30 dB 0 dB 30 dB
Macro 900 "A" Parameters
penaltyTime 20 s 20 s 20 s 40 s

Time T: (0 - 19 s) Time T: (20 - 39 s) Time T: (> 40 s)

C2 =30 Cell "A" C2 =30 Cell "A" C2 =30 Cell "A"
C2 =15 Cell "B" C2 =45 Cell "B" C2 =45 Cell "B"
C2 =5 Cell "C" C2 =5 Cell "C" C2 =5 Cell "C"
C2 =20 Cell "D" C2 =20 Cell "D" C2 =50 Cell "D"
Cell Reselection Events
Authentication Failure
Pathloss Criterion C1 notification by upper layers
C1  0 for a period of 5 s

Cell has been barred

Pathloss Criterion C2 CELL_BAR_ACCESS & CELL_BAR_QUALIFY
• neighbour‘s C2 value >
current cell‘s C2 value (same LA)
• neighbour‘s C2 value > RACH Failure
current cell‘s C2 value + HYS MAX RETRANS + 1 times
(new LA)
for a period of 5 s.
Downlink Signalling Failure
DSC  0

When shall I
select a new cell?
LocationMS Update
BSS Procedure
MSC VLR HLR

LOCATION UPDATE REQUEST

REQUEST SUBSCRIBER ID

SEND SUBSCRIBER ID

REQUEST SUBSCRIBER INFO

SEND SUBSCRIBER INFO

AUTHENTICATION

AUTHENTICATION RESPONSE

ALL OK - HLR UPDATE

Trade-off between Location Update and
Paging Traffic
signalling
traffic

function of user density,

function of cell size, call arrival rate ...
user mobility

Paging
LocUp

optimum number # of cells in Loc. area

of cells in Loc. area
Location Updates
• MS location & status flag => MSC / VLR
• Mobile Station switched ON mode
• IMSI Attach / Detach
• Same Location Area => No Location Update
• Different Location Area => Location Update
• Change of the Location Area
• Location Area under the same MSC / VLR
• Location Area under another MSC / VLR => HLR will be updated
• Service is rejected (MS unknown in VLR)
• Time-Periodic LU (MS -> MSC/VLR)
MO Abbreviated Range And Description Default BSC -
Class Name Step value MML
Name
BTS allowIMSIAtt Yes/No Defines whether IMSI attach/detach is used in the cell. Yes ATT
achDetach
BTS timerPeriodic 0...25.5 h, Defines the interval between periodic MS location 0.5 h PER
UpdateMs step 0.1 h updates.
The value 0 means that the periodic location update is
not used.
IDLE MODE OPERATION
Idle Mode Controls
Parameter Value
rxLevAccessMin -110 ... -47 (dBm)
msTxPwrMaxCCH 13 ... 43 (dBm)
notAllowedAccessClasses 0 ... 9, 11 ... 15
Access
emergencyCallRestricted Yes/No Parameters
msMaxDistanceInCallSetup 0 ... 255
radiusExtension 0 ... 67 (Km)

cellBarred Yes/No
Mobility
plmn-permitted 0 ... 7
Parameters
cellReselectHysteresis 0 ... 14 (dB)

cellReselectOffset (REO) 0 ... 126 (dB)

cell reselection parameter index (PI) (N/Y)

IDLE MODE OPERATION
Idle Mode Controls
• RxLevAccessmin :
definitions
With this parameter you define the minimum power level an MS has to receive before it is allowed to access the cell.
• MsTxPwrMaxCCH :
With this parameter you define the maximum transmission power an MS may use when accessing a CCH in the cell.
• notAllowedAccessClasses
With this parameter you define the MS access classes that are not allowed to access a cell.
• Emergency Call Restricted
With this parameter you define if an emergency call in the cell is allowed to all MSs or only to the MSs which belong to one of the
classes between 11 to 15. Value ’Y’ means the latter case.
• MsMaxDistancein CallSetup
With this parameter you define the maximum distance between the BTS and the MS in call setup. The maximum distance is
expressed as an access delay. Within the range of 0...62, one step correlates to a distance of 550 meters. If the access delay of the
channel request message exceeds the given maximum, the call attempt is rejected. When the parameter is given a value from 63 to
255, call attempts are never rejected
• radiusExtention
With this parameter you define the radius extension of an extended cell
Radio Resource management
Signalling (Mobile Originating Call)
MS Channel request (RACH) NETWORK

Immediate assignment (AGCH) Immediate assignment

Service request (SDCCH)

Service request

Authentication request (SDCCH)

Idle Authentication
Authentication response (SDCCH)
parameter
Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting

Setup (SDCCH)

Call proceeding (SDCCH) Call initiation

Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel

Alert (FACCH)

Call confirmation
Dedicated
Connect (FACCH)
parameter
Connect acknowledged (FACCH) Call accepted
Signalling (Mobile Terminating Call)
MS Page request (PCH) NETWORK

Channel request (RACH) Immediate assignment

Immediate assignment (AGCH)

Page response (SDCCH)

Service request
Idle Authentication request (SDCCH)
parameter Authentication
Authentication response (SDCCH)

Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting

Setup (SDCCH)

Call confirmation (SDCCH) Call initiation

Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel

Alert (FACCH)

Call confirmation
Dedicated
Connect (FACCH)
parameter
Connect acknowledged (FACCH) Call accepted
Signalling (Call Release)
Network initiated

MS Disconnect NETWORK

Release Call clearing

Release complete

Channel release

Release

MS initiated

MS Disconnect NETWORK

Release Call clearing

Release complete

Channel release

Release
Standard TCH Allocation (General Criteria)

MS capabilities

Channel rate : full, half, dual, multi rate

Speech codecs : normal FR, normal HR, EFR, AMR FR, AMR HR, doubleHR(OSC)

MSC demands

A interface circuit allocated for call

BTS demands

Speech codec capabilities

TCH configuration
Current resources
Homogeneous use of TRXs and radio time slots
Large free groups of radio time slots for high loaded HSCSD BTS
 TCH_HR_RADIO_CONGESTION_TIME (sec)
TCH_FR_RADIO_CONGESTION_TIME (sec)
TCH Allocation 2 TRX=16 channels

PEAK_PERMANENT_GPRS_CH
SDCCH

SDCCH_CONG_TIME(sec)
BCCH

PEAK_GPRS_CHANNELS
TCH_PEAK_BUSY_HALF
TCH_PEAK_BUSY_FULL
AVE_SDCCH (SDCCH/8)

AVE_GPRS_CHANNELS
PEAK_PERMANENT_GPRS_CH

AVE_AVAIL_FULL_TCH
AVE_TCH_BUSY_FULL
PEAK_BUSY_SDCCH
AVE_GPRS_CHANNELS

AVE_BUSY_SDCCH
AVE_TCH_BUSY_FULL

PEAK_BUSY_TCH
16.0

14.0

12.0

TIME
10.0
12:00:00 AM 32 5.0 18 6.3 4.0 9 9 0 0 8.48 0 4.7 8 2
RTSL

8.0
1:00:00 AM 32 3.1 13 6.8 3.4 9 9 0 0 1.41 0 4.2 9 2
6.0
2:00:00 AM 32 1.7 12 5.2 2.9 7 7 0 0 0 0 5.8 9 2
4.0 3:00:00 AM 32 1.5 12 6.2 1.4 7 7 0 0 0 0 4.8 9 2
4:00:00 AM 32 1.6 10 8.0 1.7 5 5 0 0 0 0 3.0 9 2
2.0
5:00:00 AM 32 8.8 32 5.7 0.8 6 6 0 559 0 0 5.3 9 2
0.0 6:00:00 AM 32 5.2 18 4.3 1.1 6 6 0 0 0 0 6.7 9 2
7:00:00 AM 32 6.5 23 8.5 2.6 8 8 0 0 0 0 2.5 6 2
12:00:00 AM

2:00:00 AM

6:00:00 AM

8:00:00 AM

10:00:00 AM

2:00:00 PM

4:00:00 PM

6:00:00 PM

8:00:00 PM

10:00:00 PM
4:00:00 AM

12:00:00 PM

8:00:00 AM 32 4.8 20 6.6 2.2 7 7 0 0 0 0 4.4 9 2

9:00:00 AM 32 4.3 20 6.8 2.4 8 8 0 0 0 0 4.3 9 2
10:00:00 AM 32 5.2 32 7.5 2.6 9 9 0 2 0.21 0 3.5 9 2
11:00:00 AM 32 5.9 18 6.3 2.9 9 9 0 0 8.98 0 4.7 9 2
12:00:00 PM 32 5.9 19 6.8 3.9 9 9 0 0 13.52 0 4.2 8 2
0 1 2 3 4 5 6 7 1:00:00 PM 32 7.3 24 6.4 3.4 9 9 0 0 8.96 0 4.6 9 2
TRX1 BCCH SDCCH SDCCH V/D V/D V/D V/D V/D 2:00:00 PM 32 6.8 30 6.2 3.9 9 9 0 0 44.05 0 4.8 8 2
TRX2 SDCCH SDCCH V/D V/D V/D V/D D D 3:00:00 PM 32 7.1 21 6.7 4.7 9 9 0 0 64.18 0 4.3 9 2
4:00:00 PM 32 7.7 23 6.6 3.9 9 9 0 0 25.61 0 4.4 8 2
5:00:00 PM 32 8.5 23 6.7 3.9 9 9 0 0 34.51 0 4.3 9 2

How can be optimized? 6:00:00 PM

7:00:00 PM
32 10.7 27 8.3 5.9
32 11.1 28 8.4 5.6
9
9
9
9
0
0
0 320.58
0 217.77
0
0
2.7
2.6
7
9
2
2
8:00:00 PM 32 10.4 30 7.8 5.5 9 9 0 0 284.15 0 3.2 8 2
9:00:00 PM 32 9.3 26 7.5 5.3 9 9 0 0 217.65 0 3.5 8 2
10:00:00 PM 32 8.3 22 7.5 5.2 9 9 0 0 185.36 0 3.5 9 2
11:00:00 PM 32 5.8 21 6.8 4.6 9 9 0 0 89.61 0 4.2 9 2
Channel allocation
Each TRX – have its own Quality both (
DL For
DL) will result bad KPI on respective TRX
each
and UL and TS)
TRX with bad quality (UL and

Placing each Time Slot (BCCH, SDCCH, TCH and PDTCH) properly will result
good KPI (SDSR, DCR, HOSR TBF Completion rate)

Shitting SDCCH, BCCH can improve SDSR and DCR

Standard TCH Allocation
(Interference Bands)
Measurement of uplink receive level on idle channels = uplink interference

Averaging over interferenceAveragingProcessAverPeriod (AP) = 1..32 SACCH

periods

Classification into interference bands based on interferenceAveragingProcess

(BO1..BO4) = -110..-47 dBm

BSC tries to allocate TCH from best interference band (can be requested by MSC)
If not available,
BSC tries to take TCH from next band

BO5 –47 (fixed)

rxLevUL = -75 dBm
BO4 -90
BO3 -95
BO2 -100
BO1 -105
BO0 –110 (fixed)
0 1 2 3 4 5 6 7
Prioritized TCH Allocation (TRP)
Whole band , 50 channels 1 ch=200kHz

Case1 BCCH, 30 channels TCH, 20 channels

Case2 All 50 channels for BCCH and TCH

Priority for TCH from BCCH TRX

BCCH transmitted permanently -> no additional interference in network

Planned to be least interfered channels

Priority for TCH from other TRX

BCCH TRX does not hop in case of RF hopping -> hopping gain only for other TRX

Parameter

trxPriorityInTCHAlloc (TRP) 0 = no priority

1 = priority for BCCH TRX
2 = priority for other TRX
3 = priority for BCCH TRX for non-AMR users,
priority for other TRX for AMR users
RX level based TCH Allocation (RXP)
Enables to differentiate Rx level requirement for:
• MS camping to the network /RxLev Access Min
• MS accessing to TCH /RX level based TCH access

RX level based TCH allocation method

• RX Level measured by the MS is used to determine whether the BTS is
acceptable for TCH allocation
• TCH allocation for emergency calls is not restricted due to low RX level

Provides better drop call meters and better performance of MSs

• MSs having too low Rx levels are not allowed to camp the network
By separating camping and TCH access thresholds the operator will be able to
provide the maximum camping footprint

Note! RG20 feature – Energy optimized TCH allocation

RX level based TCH Allocation (RXTA)
Allows to define minimum C/N ratios separately for each call type (AMR FR, AMR HR, EFR/FR, HR
and 14.4 data)
Parameter values ‘RX level based TCH access’:

0: RX level based TCH access is not used (C/N definitions not in use)
1: RX level based TCH access is used in call setup
2: RX level based TCH access is used in call setup and in handovers

Soft blocking C/N FR: 0…63dB/ def: 12dB

Soft Blocking C/N HR: 0…63dB/ def: 14dB
Soft blocking C/N AMR FR: 0…63dB/ def: 7dB
Soft blocking C/N AMR HR: 0…63dB/ def: 12dB
Soft blocking C/N 14.4 : 0…63dB/ def: 14dB
Downlink RX Level
-> TCH Access
Queuing (Parameters)
Priorities

No TCH available for call set up / handover -> request put into queue
Different kinds of requests can have different priorities

queuePriorityUsed (QPU) Y/N enables use of priorities

queueingPriorityCall (QPC) 1..14 priority for call set up request

queuePriorityNonUrgentHo (QPN) 1..14 priority for non urgent handover (power budget,
umbrella, slow moving MS, traffic reason)
request
queueingPriorityHandover (QPH) 1..14 priority for urgent handover (all other) request

Queue length and time

maxQueueLength (MQL) 0..100% percentage of number of TCHs handled by BTS

timeLimitCall (TLC) 0..15 s time a call set up request is kept in the queue
0 = queuing is disabled
timeLimitHandover (TLH) 0..10 s time a handover request is kept in the queue
0 = queuing is disabled
Queuing (Entering the Queue)
Conditions

Timers set to values > 0

User of priorities enabled
Queue not full with requests of equal or higher priority than the current one

Queuing of call set up requests

Reservation of SDCCH resources

-> SDCCH easily overbooked
-> blocking of services like SMS or location update
Queuing (Handover)
Handover request queued by target BTS

Handover timers hoPeriodPBGT and hoPeriodUmbrella stopped

Measurement processing and averaging continues as usual

Intra BSC handover Inter BSC handover

Queuing possibility checked for all Target BTS given by MSC by

possible target cells Order handover request message
according conventional ranking
Queuing (Leaving the Queue)
With TCH allocation

Release of busy TCH

 Check of queue from top to bottom for best matching request
 If TCH allocation possible, request removed from queue

Without TCH allocation

Queuing timer expires

Request of higher priority enters full queue
Queuing (Together with Directed Retry)
Directed Retry Timer maxTimeLimitDirectedRetry expires

 call cleared, even if still in queue

Queuing timer expires

 target cell evaluation continues, if directed retry timer is still running

Dropped Call Control BTS does not receive measurement report on
Radio Link Timeout SACCH for running call for the first time

Counter initialised with value of radioLinkTimeout

(4,8,..64 SACCH periods)

SACCH not received again SACCH received again

Counter decremented by 1 Counter incremented by 2

(but not beyond initial value)

Counter has value 0 Example: short tunnel

Call release due to radio link

time out
Dropped Call Control
Radio Link Timeout
• RLT is based on SACCH deletion but SACCH is though not using a dynamic
codec like voice in AMR, which means:
• Using the EFR RLT value an AMR customer can have the call dropped
because RLT = 0 when still the FER is good
• RLT is not anymore reliable with the same value in AMR than in EFR
• Due to the fact that the FER performance is different when comparing AMR
calls to EFR calls, the Radio Link Timeout need to be defined separately for
AMR
• The Radio Link Timeout parameters for AMR are ARLT and AHRLT. The
principle of these is the same than in the RLT but it is used only for the AMR
capable mobile stations. ARLT & AHRLT are not supported in Talk Family
base stations.
Dropped Call Control Radio link timeout occurs
Call Reestablishment callReestablishmentAllowed (RE) set to Y

Receive level of BCCH measured for serving and adjacent cell

Averaged over 5 s

Strongest cell considered Example: long tunnel

BCCH decoded
C1 cell selection criterion fulfilled
Cell not barred
Cell belongs to selected PLMN

Attempt to re-establish call

Successful within 20s * Not successful within 20s *

 call released
 call re-established
* MAX WAIT TIME OF RE-ESTAB REQ is a modifiable timer in MSC
NPT parameter related (Idle Parameter)
Measurement Processing
Introduction
Measurement Measurements
Report

Standard Enhanced Idle mode Dedicated mode

• Rx level Standard + following: • MS listens • MS sends DL

• Rx quality • DL frame erasure rate to BCCH measurement report on
• Level & BSIC of up • DTX bit error probability SACCH
to 6 neighbours • Real time difference serving – • BTS performs UL
• 3G cells adjacent cell measurements
• 3G cells
• Control over reporting priority
Introduction
Measurement Measurements
Report

Standard Enhanced Idle mode Dedicated mode

• Rx level Standard + following: • MS listens • MS sends DL

• Rx quality • DL frame erasure rate to BCCH measurement report on
• Level & BSIC of up • DTX bit error probability SACCH
to 6 neighbours • Real time difference serving – • BTS performs UL
• 3G cells adjacent cell measurements
• 3G cells
• Control over reporting priority
Coding of Rx Level
P (dBm) P (dBm) LEV
No offset 10 dB offset

-110 -100 0
-109 -99 1
-108 -98 2
. . .
. . .
. . .
-49 -39 61
-48 -38 62
-47 -37 63

Activation of offset to code high levels

scaleOrd (SCO)(SEG)(0,1,2)(0)

0 = no offset used
1 = offset used in general
2 = MS decides automatically about offset
Coding of Rx Quality
BER (%) BER (%) QUAL

RANGE MEAN
< 0.2 0.14 0
0.2-0.4 0.28 1
0.4-0.8 0.57 2
0.8-1.6 1.13 3
1.6-3.2 2.26 4
3.2-6.4 4.53 5
6.4-12.8 9.05 6
> 12.8 18.1 7

Average window = 4
Quality samples 0,0,7,0
WRONG!!: (0+0+7+0)/4 = 1.75 (wrong!!)
RIGHT: (0.14+0.14.+18.1+0.14)/4 = 4.63 (right!!) => corresponds to Qual5
Mapping of BEP to RX Quality
BEP BER (%) QUAL

VALUE RANGE
22..31 < 0.2 0
19..21 0.2-0.4 1
16..18 0.4-0.8 2
13..15 0.8-1.6 3
10..12 1.6-3.2 4
7..9 3.2-6.3 5
4..6 6.3-12.6 6
0..3 > 12.6 7
Mapping of FER to RX Quality

X axis: frame erasure rate (< 1%, 1-5 %, 5-10 %, 10-15 %, > 15 %)
Y axis: RX quality (0..7)
Z axis: Percentage of measurements for each FER category

Frame Erasure Rate for Handover / Power Control Decision

fepInPcHoUse (FPHO)(BSC)(Y,N)(N)
MS Measurement Execution
Idle Mode
• Decoding of BCCH
• for serving (camped) cell every 30 s
• for adjacent cells every 5 min
• Pre-synchronization and decoding of BSIC
• for adjacent cells every 30 s
• Adjacent cell list
• Updating every 60 s
• BCCH decoding of new cell in 30 s
MS Measurement Execution
Dedicated Mode I
SACCH PERIOD = 480 ms

26 FRAME MULTIFRAME = 120 ms

TDMA FRAMES
TDMA FRAMES
4.615 ms TCH SACCH IDLE

RX TX MEAS RX TX MEAS RX TX MEAS

• BSIC decoding for at least one adjacent cell
• Pre-synchronization on SCH

• Measures frequencies of adjacent cells

• Measures RX level and quality for serving cell

• Detects whether DTX is used
Power Control
Power Control Motivation

Reduced
interference on
DL/UL

• Longer service time of battery

• Realization of power class
• Supported by default on UL

Activation of DL power control

powerCtrlEnabled (PENA) Y,N

Power control independent

• for DL and UL
• for each call
Power Control Parameter
Output Power Limits Maximum MS output power

msTxPwrMaxGSM (PMAX1) 5..39 dBm GSM 900 TCH

Power msTxPwrMaxGSM1x00 0..36/32,33 dBm GSM 1800/1900 TCH
class (PMAX2)
dependent msTxPwrMaxCCH (TXP1) 5..39 dBm GSM 900 CCH
range msTxPwrMaxCCH1x00 0..30 dBm GSM 1800 CCH
Power Values (TXP2) 0..32 dBm GSM 1900 CCH

Minimum MS output power

minMSTxPower (PMIN) 5..39 dBm GSM 900

0..36 dBm GSM 1800
0..32 dBm GSM 1900

Maximum BTS output power (by minimum attenuation)

Attenuations bsTxPwrMax (PMAX1) 0..30 dB GSM 900

bsTxPwrMax1x00 (PMAX2) 0..30 dB GSM 1800/1900
30 dB
Range Minimum MS output power (by maximum attenuation)

bsTxPowerMin 0..30 dB
Power Control Parameters
Power Change Step Sizes Desired power level can be achieved in 1 or 2 commands

Yes No

Fixed step size Variable step size

Fixed increment step size

• pcIncrStepSize (INC) 2,4,6 dB

Fixed decrement step size

• pcRedStepSize (RED) 2,4,6 dB

Power Control Strategy
Measurement Averaging

POWER CONTROL
UPLINK
UL Quality <Av_RXQUAL_UL>

UL Level <Av_RXLEV_UL> THRESHOLD

COMPARISON
DL Quality <Av_RXQUAL_DL>

DL Level <Av_RXLEV_DL>
POWER CONTROL
DOWNLINK

Power control interval

powerCtrlInterval (INT) 0..31 s

Power Control Strategy
Triggering
Nx samples
Less than Px samples exceed threshold
No power change triggered
Actual average samples

threshold

Nx samples
Signal level thresholds Px samples are equal to or exceed threshold
Power change triggered
pcUpperThresholdLevelDL/UL (UDR/UUR) -110..-47 dBm
pcLowerThresholdLevelDL/UL (LDR/LUR) -110..-47 dBm
Power change step size estimation
Signal quality thresholds

pcUpperThresholdQualDL/UL (UDR/UUR) 0..7

pcLowerThresholdQualDL/UL (LDR/LUR) 0..7

Number of average samples (for each threshold)

Nx 1..32
Px 1..32
Power Control Strategy
Scenarios

Exceeded threshold Action Reason

pcUpperThresholdLevelDL BTS power decrease Signal level

pcLowerThresholdLevelDL BTS power increase Signal level
pcUpperThresholdLevelUL MS power decrease Signal level
pcLowerThresholdLevelUL MS power increase Signal level

pcUpperThresholdQualDL BTS power decrease Signal quality

pcLowerThresholdQualDL BTS power increase Signal quality
pcUpperThresholdQualUL MS power decrease Signal quality
pcLowerThresholdQualUL MS power increase Signal quality
AMR Power Control
Exceeded threshold Action Reason
AMR Power Control FR PC Lower BTS power increase Poor DL signal quality
Threshold DL Rx Qual
AMR Power Control FR PC Lower MS power increase Poor UL signal quality
Threshold UL Rx Qual
AMR FR AMR Power Control FR PC Upper BTS power decrease Good DL signal quality
Threshold DL Rx Qual
AMR Power Control FR PC Upper MS power decrease Good UL signal quality
Threshold UL Rx Qual
AMR Power Control HR PC Lower BTS power increase Poor DL signal quality
Threshold DL Rx Qual
AMR Power Control HR PC Lower MS power increase Poor UL signal quality
Threshold UL Rx Qual
AMR HR AMR Power Control HR PC Upper BTS power decrease Good DL signal quality
Threshold DL Rx Qual
AMR Power Control HR PC Upper MS power decrease Good UL signal quality
Threshold UL Rx Qual

Details in chapter on AMR

 POC
Lower Upper
-110 dB Level(-90) Level(-80)
-47 dB

Qual 0 Signal level

Ping Decrease due to good quality

pong
Upper effect
Quality(1)

Increase Decrease
No action
due to bad Due to good
Signal level Signal level
Lower
Quality(3)

Increase due to Bad quality

Qual 7
Quality
POC Lower Upper
-110 dB Level Level
-47 dB

Qual 0 Signal level

6dB Decrease due to quality

Upper
Quality

Increase No action Decrease

due to level Due to level
Lower
Quality

Increase due to quality

Qual 7
Quality
POC and HOC (UL)
UL Level HO
-110 dB Threshold
-47 dB

Qual 0 Signal level

When UL quality HO is triggered

• Should MS be sent full power?
No action
•What about UL level

UL Quality HO
Threshold

Qual 7
Quality
Power Control Summary Upper Level
-110 dBm Lower Level -47 dBm

Qual 0
Power increase Power decrease Power decrease
due to level 6 dB due to quality due to level
or quality
Upper Quality

Power increase Power decrease

No action due to level
due to level

Lower Quality
Power increase Power increase Power increase
due to level due to quality due to quality
or quality

Qual 7
Power Increase Due to Signal Level
For MS & BTS
Actual receive level RXLEV_DL/UL

pcLowerThresholdsLevelDL/UL

Power control triggered

UL: Power increase of MS
DL: Power increase of BTS

RXLEV_DL/UL > pcLowerThresholdLevelDL/UL - 2 powerIncrStepSize

Yes No

Fixed step size Variable step size

PWR_INCR_STEP = powerIncrStepSize PWR_INCR_STEP = pcLowerThresholdLevelDL/UL –

RXLEV_UL/DL
Power Decrease Due to Signal Level
For BTS
pcUpperThresholdsLevelDL

Actual received level RXLEV_DL

Power control triggered

Power decrease

RXLEV_DL < pcUpperThresholdLevelDL + 2 powerDecrStepSize OR

variableDLStepUse (VDLS) = No

Yes No

Fixed step size Variable step size

PWR_DECR_STEP = powerDecrStepSize PWR_DECR_STEP = Min (RXLEV_DL –

pcUpperThresholdLevelDL, 10)
Power Decrease Due to Signal Level
For MS
pcUpperThresholdsLevelUL

Actual received level RXLEV_UL

Power control triggered

Power decrease

RXLEV_UL < pcUpperThresholdLevelUL + 2 powerDecrStepSize

Yes No

Fixed step size Variable step size

PWR_DECR_STEP = powerDecrStepSize PWR_DECR_STEP = RXLEV_UL –

pcUpperThresholdLevelUL
Power Increase Due to Signal Quality
For MS & BTS
Actual receive quality RXQUAL_DL/UL

pcLowerThresholdsQualDL/UL

Power control triggered

UL: Power increase of MS
DL: Power increase of BTS

Variable step size based on actual quality

PWR_INCR_STEP = (1 + Max (0,QUAL)) * powerIncrStepSize

QUAL = RXQUAL_DL/UL – pcLowerThresholdQualDL/UL

Take largest step size

Step size based on actual level

Take algorithm for power increase due to signal level

Power Decrease Due to Signal Quality
For MS & BTS with No Power Optimization
pcUpperThresholdsQualDL/UL

Actual received quality RXQUAL_DL/UL

Power control triggered

Actual RXLEV_DL/UL – pcLowerThresholdLevelDL/UL < 6 dB

Yes No

No power decrease Power decrease

Avoid ping pong effect Take algorithm for power decrease due to signal level
(different for MS & BTS power decrease)
NPT parameter related (POC Parameter)

Should be greater
than HOC
Handover Control
Handover Types Germany Czech Republic

Intra PLMN
Simple Cell ID required Inter PLMN
LAC + CI Global Cell ID required
MCC + MNC + LAC + CI

Inter MSC
Intra cell
Only other carrier / timeslot

Inter cell
Intra BSC

Inter BSC
Intra MSC
Multi Layer Network Types Normal
Super reuse
frequency
frequency

Macro cells

Micro cells
Intelligent Underlay Overlay
Different frequencies for high / low power TRx

GSM 900 cell

GSM 1800 cell

Coverage Layer: Gives access to the network

Capacity Layer: Provides additional capacity and allows traffic
distribution
Handover Strategy
Triggering Nx samples
Less than Px samples >= threshold
No handover triggered
Actual average samples

threshold

Signal interference thresholds Nx samples

hoThresholdsInterferenceDL/UL (IDR/IUR) -110..-47 dBm Px samples are >= threshold
Signal quality thresholds
handover triggered
hoThresholdsQualDL/UL (QDR/QUR) 0..7

Signal level thresholds

hoThresholdLevelDL/UL (LDR/LUR) -110..-47 dBm Target cell selection
hoThresholdRapidLevelUL (RPD) -110..-47 dBm

MS speed thresholds
upper/lowerSpeedLimit (USL/LSL) 0..255 (unit = 2km/h) Trigger Point – When the set
threshold has been met or
Number of average samples
Nx 1..32 exceeded Px times of Nx times
Px 1..32
Handover Strategy
(Priorities)
More than one handover criterion fulfilled -> process of higher priority performed
Handover and power control criteria fulfilled -> handover performed

1) Interference (uplink or downlink)

2) Intra-segment inter-band because of downlink level (from higher to lower frequency band)
3) Uplink quality
4) Downlink quality
5) AMR unpacking (uplink level and also uplink unpacking quality triggers)
6) Uplink level
7) AMR unpacking (downlink level and also downlink unpacking quality triggers)
8) Downlink level
9) Coverage based inter-system handover to WCDMA RAN
10) IMSI-based inter-system handover to WCDMA RAN
11) IMSI-based handover
12) DTM-based handover to WCDMA RAN
13) Inter-system handover to WCDMA RAN Exercise:
14) MS-BS distance (maximum or minimum)
15) Turn-around-corner MS Whu UL has many times
16) Rapid field drop
17) Slow/fast-moving MS higher priority than DL?
18) Umbrella
19) Power budget
20) DTM-based handover to a GSM DTM cell
21) BSC-initiated TRHO
22) IUO
23) Intra-segment HO based on load
24) AMR packing because of good uplink and downlink quality
25) AMR unpacking because of bad uplink or downlink quality
26) PC because of lower quality thresholds (uplink and downlink)
27) PC because of lower level thresholds (uplink and downlink)
28) PC because of upper quality thresholds (uplink and downlink)
29) PC because of upper level thresholds (uplink and downlink)
HO due to UL/DL Quality
IF
AV_RXQUAL_DL_HO >=
HoThresholdsQualDL
IF
AV_RXQUAL_UL_HO >=
HoThresholdsQualUL
THEN THEN
Handover cause Downlink quality Handover cause Uplink quality

Target cells is listed based on below criteria

1. AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0,Pa)
2. AND IF
EnableHoMarginLevQual(n)= Yes
Listing set of
THEN target cell
AV_RXLEV_NCELL(n) > AV_RXLEV_DL_HO + (BsTxPwrMax - BS_TXPWR) +
HoMarginQual(n)
3. ELSE
PBGT(n) > HoMarginPBGT(n) (2)

Order of preference of target cells

PRIORITY(n) = HoPriorityLevel(n) - HoLoadFactor(n) Priority of
HoLoadFactor value is taken into account when BTSLoadThreshold is target cell
exceeded.

Interval between handovers and handover attempts Timer of

source cell
HO due to UL/DL LEVEL
IF
AV_RXLEV_DL_HO<=
HoThresholdsLevDL
IF
AV_RXLEV_UL_HO<=
HoThresholdsLevUL
THEN THEN
Handover cause Downlink level Handover cause Uplink level

Target cells is listed based on below criteria

1. AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0,Pa)
2. AND IF
EnableHoMarginLevQual(n)= Yes
Listing set of
THEN target cell
AV_RXLEV_NCELL(n) > AV_RXLEV_DL_HO + (BsTxPwrMax - BS_TXPWR) +
HoMarginLev(n)
3. ELSE
PBGT(n) > HoMarginPBGT(n) (2)

Order of preference of target cells

PRIORITY(n) = HoPriorityLevel(n) - HoLoadFactor(n) Priority of
HoLoadFactor value is taken into account when BTSLoadThreshold is target cell
exceeded.

GUARD_TIME = 2 * HoPeriodPBGT (Ho Due PBGT) Timer of

GUARD_TIME = 2 * HoPeriodUmbrella (HO Due to Umbrella)
source cell
HO due to Fast/Slow moving MS
MS speed in relation to cell size:
IF
MsSpeedDetectionState= 0
Measured MS speed:
IF
AV_MS_SPEED <= LowerSpeedLimit
AdjCellLayer(n) = Lower
THEN
FastMovingThreshold(n)> 0
MS is slow-moving
IF
AV_MS_SPEED >= UpperSpeedLimit
THEN
AV_RXLEV_NCELL(n) >
MS is fast-moving
RxLevMinCell(n) + MAX (0, Pa)
THEN
RXLEV_CNT(n) = RXLEV_CNT(n) + 2
ELSE
RXLEV_CNT(n) = RXLEV_CNT(n) - 1 IF
MsSpeedDetectionState= 0
THEN
Handover Cause Fast/Slow-moving MS
IF
ELSE
RXLEV_CNT(n) >=
Scale averaging parameters
FastMovingThreshold(n)
THEN
Handover cause Slow-moving MS

Target cell evaluation:

AdjCellLayer(n) = Lower/Upper
AND
AV_RXLEV_NCELL(n) > HoLevelUmbrella(n) (1')
Handover to low layer cell is not possible if maximum power capability of MS exceeds
gsm/dcsMicrocellThreshold
HO due to Fast/Slow moving MS (Count) Target cell evaluation:
AdjCellLayer(n) = Lower/Upper
AND
AV_RXLEV_NCELL(n) > HoLevelUmbrella(n) (1')
Handover to low layer cell is not possible if maximum power capability of MS exceeds
gsm/dcsMicrocellThreshold

Order of preference of target cells

PRIORITY(n) = HoPriorityLevel(n) - HoLoadFactor(n)
HoLoadFactor value is taken into account when
BTSLoadThreshold is exceeded

Interval between handovers and handover attempts

HO due to Umbrella IF
EnableUmbrellaHO= Yes
HoPeriodUmbrella - interval between the umbrella
handover threshold comparisons

Umbrella handover and target cell evaluation:

AV_RXLEV_NCELL(n) > HoLevelUmbrella(n) (1')
AND
( [(P >= macro_thr) AND (pwr(n) >= macro_thr)]
OR
[(P <= micro_thr) AND (pwr(n) <= micro_thr)]
OR
[(P < macro_thr) AND (pwr(n) < macro_thr) AND
(P > micro_thr) AND (pwr(n) > micro_thr)] )

Order of preference of target cells

PRIORITY (n) = HoPriorityLevel(n) - HoLoadFactor(n)
HoLoadFactor value is taken into account when
BTSLoadThreshold is exceeded.

Interval between handovers and handover attempts

Umbrella +FMT Handover
Example
hoLevelUmbrella = -85 dBm PTCH (msTxPwrMax(n)) = 30 dBm -> micro cell
gsmMacrocellThreshold = 33 dBm
PMAX = 30 dBm -> handover to micro cell only
dcsMacrocellThreshold = 33 dBm
hoThresholdLevelDL = -95 dBm

900 ‘Macro’

After FMT>1 (example)

A
1800 ‘Micro’
Threshold umbrella
handover –85 dBm

Threshold RX level
handover –95 dBm

B Umbrella handover to RX level handover

1800 cell back to 900 cell
HO due to PBGT IF
EnablePowerBudgetHO= Yes
HoPeriodPBGT - interval between the power budget
threshold comparisons

Power budget and target cell evaluation:

AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0, Pa) (1)
AND
PBGT(n) > HoMarginPBGT(n) (2)
PBGT(n) = (B - AV_RXLEV_DL_HO -
(BsTxPwrMax - BS_TXPWR)) - (A - AV_RXLEV_NCELL(n))

Order of preference of target cells

PRIORITY (n) = HoPriorityLevel(n) - HoLoadFactor(n)
HoLoadFactor value is taken into account when
BTSLoadThreshold is exceeded.

Interval between handovers and handover attempts

Power Budget Handover BTS A
Exercise BTS B
Serving cell: A
HO candidate target cells: B, C, D
Serving cell A:
AV_RXLEV_DL_HO= -92 dBm
All cells have the following parameter set:
BTS_TX_PWR= 42 dBm
rxLevMinCell= -99 dBm
msTxPwrMax= 33 dBm
BTS C
btsTxPwrMax= 42 dBm
hoMarginPBGT= 6 dB
BSC
BTS D

Target cell ‘hoPriorityLevel’: AV_RXLEV_NCELL (B)= -80 dBm

B priority: 4
AV_RXLEV_NCELL (C)= -83 dBm
C priority: 3
D priority: 3 AV_RXLEV_NCELL (D)= -85 dBm
Target cell ‘HOLoadFactor’:
B load factor: 2
C load factor: 1
Which cell (B/C/D) will be chosen as target for
D load factor: 1
the Power Budget HO?
Target cell B is considered overloaded

Exercise Solution
Combined Umbrella & Power Budget HO
Overview

• enablePowerBudgetHo = Yes & enableUmbrellaHo = Yes

• Power budget handover to cells of the same layer
• Umbrella and FMT handover to cells of different layer

UMBR umbrella HO
RR radio reason HO
PBGT power budget HO
macrocells

PBGT,RR
UMBR+FMT RR

PBGT,RR
microcells
Combined Umbrella & Power Budget HO
Adjacent Cell Classification
• Predefinition of layer possible by adjCellLayer (ACL)
• Three layers visible relative to serving cell
• Used for target cell evaluation
• Combined umbrella and power budget
• Handover based on MS speed
• Fast moving MS handling in macro cell

UPPER layer (macro)

SAME layer (serving layer)

LOWER layer (micro)

N (no predefinition)
HO due to Directed Retry IF
DirectedRetryUsed = Yes
Handover from SDCCH of serving cell to TCH of adjacent cell due to congestion
minTimeLimitDR – Target cell evaluation started
MaxTimeLimitDR - Target cell evaluation stopped

Target Cell evaluation

IF
DirectedRetryMethod = 1
THEN
AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0, Pa) (1)
AND
AV_RXLEV_NCELL(n) > DRThreshold
ELSE
AV_RXLEV_NCELL(n) >RxLevMinCell(n) + MAX (0,Pa)

Interval between handovers and handover attempts

Directed Retry
Parameters
No TCH available during call set up in serving cell -> handover to TCH of other cell

Must be enabled with

drInUse (DR) Y/N

Thresholds to be exceeded by target cell according condition (1a)

drMethod (DRM) 0/1 Defined type of threshold
rxLevMinCell -110..-47 dBm Used if drMethod = 0
drThreshold (DRT) -110..-47 dBm Used if drMethod = 1 and
drThreshold > rxLevMin Cell
Timers (to be counted from TCH assignment)
minTimeLimitDirectedRetry (MIDR) 0..14 s No target cell evaluation
allowed
maxTimeLimitDirectedRetry (MADR) 1..15 s Target cell evaluation allowed

TCH
SDCCH minTimeLimitDR

Assignment
congested Request Time
maxTimeLimitDR

DR not allowed
DR allowed
HO due to Rapid Field Drop
IF
HoThresholdsRapidLevUL/Px > 0

IF
Px number of RXLEV_UL measurement < HoThresholdsRapidLevUL
THEN
Handover cause Rapid field drop

Target cell evaluation

IF
ChainedAdjacentCell(n) = Yes
AND
AV_RXLEV_NCELL(n) > RxLevMinCell(n) + MAX(0, Pa) (1)

Order of preference of target cells:

The target cells are ranked according to radio link properties
(equation 1).
Rapid Field Drop Handover
Example

hoThresholdRapidLevUL = -93 dBm Chained

hoThresholdRapidLevUlN =2 Cell
chainedAdjacentCell =Y
Serving Cell

Serving cell

Threshold rapid field drop

handover –93 dBm
1st

2nd
Handover
triggered
NPT parameter related (HOC Parameter)

Should be lower
than POC
NPT parameter related (ADCE Parameter)
NPT parameter related (ADCE Parameter)
KPI case
 Site with FRL/FRU = 100% will
have max capacity but have
lower Quality
Site with height >40m with
total tilt =2 will have wide
cell capacity cell coverage
coverage but KPI will bad
Excessive value RxLevAmi will
improve KPI but coverage and and Tailoring
quality will reduce Optimization
quality
service
Optimization process is a way to do changes in
a network so that those network have maximum
on Capacity, Coverage and Quality
Optimization Principle
KPI- Rules, SDCCH Blocking
SDCCH
Blocking ND_211 No Case closed No
>X% ND_130
Cngt_2
Blck_5
Blck_5b ND_211

Check sdcch blocking. Can

SDCCH sdcch Blocking
sdcch capacity be added no
blocking is high is still high
without tch blocking
ND_139,ND_131
ND_130, uav_22 yes
csf_1a,csf_11
Ava_45a Yes
Check unavailability
Yes, make in the cells,
corrections averarage available
sdcch
Yes, add sdcch Add TRX and add
capacity Sdcch capacity
Availability OK

No, activate Is dynamic sddch

Dynamic sdcch active

ND_211
c1154 yes If SDCCH block high please check:
1. TCH/SDCCH availability
No, check parameter
Values and make
Is dynamic sdcch
reaching max values
No
2. LOC design (SDCCH traffic profile)
corrections in some moment
3. Parameter (CRO, CRH, RxLevAmi)
ND_211
c2032 yes

Yes, remove
combined sdcch Is combined sdcch
used

Yes, Optimize LU
area border NetAct Planner no
P_nbcs_cc_pm

Is high sdcch traffic due to

Location updates. If yes, can LU
area be optimized? Check also
PRAU parameter, can the value
be increased?
KPI- Rules, SDCCH DropND_166

Drops due to
SD DCR > 2% and Drops due to Drops due to Drops due to
Yes No No A-interface No
SD DCRnum > 10 RF Reasons Abis Reasons other Reasons
Reasons

Yes Yes Yes Yes

RF Abis A Other

No
No Case Closed

If SDCCH drop high please check:

1. DL/UL Quality
2. CRO/CRH, TRP setting
3. TA profile – overshooting possibility
4. SDCCH TS location
KPI- Rules, SDCCH Drop due to RF/Abis
Hardware and Physical
•Hardware problem (alarm 7745, 7743, TRX faulty/degraded) – reset as first action/switch TS
•Check overshooting based on ND232 (down tilt if overshooting)

TS check
•Check TRX Quality (UL and DL)based on ND196. Do retune if interference detected (also check bad quality happened on BCCH TRX or non BCCH TRX
•Check signal strength and path loss based on ND 208

Parameter optimization
•CRO/CRH parameter changes
•TRP parameter implementation
KPI- Rules, SDCCH Drop due to Aif
•Usually happened not only on 1 cells instead this cause happened on 1

Hardware BSC
•Happened on link from BSC towards MGW/MSC

Non Hardware •Check Based on DX cause for detail problem

KPI- Rules, SDCCH Drop (A)
alarms

A interface Check ET lines in

problems. Alarms the BSC and Still A drops or
A
>X%
are checked and A Yes transcoders /TCSM. No problems No
Any problems
interface trace is
done

No
Repair ET
lines Yes
No
Investigate
Alarms alarms.If problems
Are are not solved, Case Closed
Solved activate A trace

Any
No
improvements
Activate
Trace was
Long enough. Not
An problem
was found

Investigate log
Trace files. Check DX
was causes, see
not document Call
long related DX causes
enough in BSC

Any problems
found. Trace
was long
enough

Make corrections
Yes

Yes
KPI- Rules, SDCCH Drop (other)
Other Case Closed No

Check all the Netw Act User Act, bcsu, Still lots of
Lapd fails No BTS fails No No No
alarms Fails resets other drops

Yes Yes Yes Yes

signalling fails TRX or BTS
Configuration
or PCM fails. fails. Check Resets or act
problems,
Check that BTS/ TRX fail channel
check
transmissio / are working failures
configurations
parameters properly

Yes
KPI- Rules, TCH Block
Hardware and Physical
•Check TCH availability of cells. (alarm 7745, 7743, TRX faulty/degraded) – reset as first action/switch TS
•Check overshooting based on ND232 (down tilt if overshooting)

•Check FRL/FRU setting

BTS parameter •Check CDED/CDEF and GTRX – reduce if possible

•Reduce SDCCH if possible

•Check ADCE relation

Parameter optimization •Sharing traffic (not only for idle parameter BTS but also ADCE and HOC parameter)
•BTS – ADCE and HOC parameter must be check to avoid ping pong HO
 Dcr_3j

KPI- Rules, TCH Drop Call Ratios

TCH DROPS AFTER SEIZURE
TCH_RADIO_FAIL
+TCH_RF_OLD_HO
/c1013
/c1014
+TCH_ABIS_FAIL_CALL /c1084 Dcr_8h
+TCH_ABIS_FAIL_OLD /c1085
+TCH_A_IF_FAIL_CALL /c1087 Dcr_5a
+TCH_A_IF_FAIL_OLD /c1088
+TCH_TR_FAIL /c1029
+TCH_TR_FAIL_OLD /c1030 TCH DROPS AFTER ASSIGNMENT
+TCH_LAPD_FAIL /c1046 tch_new_call_assign /c57033 CONVERSATION DROPS
+TCH_BTS_FAIL /c1047 +tch_ho_assign /c57034 dropped_calls /c57007
+TCH_USER_ACT /c1048
+TCH_BCSU_RESET /c1049 -tch_norm_release /c57035
+TCH_NETW_ACT /c1050 -tch_ho_release /c57036
+TCH_ACT_FAIL_CALL /c1081
-tch_re_est_assign /c57032
-tch_re_est_assign /c57032 (S7)
DROPS
100 * %
CALLS
TCH SEIZURES FOR NEW CALL TCH ASSIGNMENTS FOR NEW CALL
tch_norm_seiz /c1009 tch_new_call_assign /c57033
+tch_seiz_due_sdcch_con /c1099 (S5)
+msc_i_sdcch_tch /c4044 STARTED CONVERSATIONS
-tch_re_est_assign /c57032 conver_started /c57015
+bsc_i_sdcch_tch /c4057 - msc_i_tch_tch /c4043
+cell_sdcch_tch /c4074
-tch_succ_seiz_for_dir_acc /c1165 (S7) TCH RELEASE
-tch_re_est_assign /c57032 (S7)
CONVERSATION STARTED Disconnect from MS
conn_ack to BTS
TCH SEIZED
BSC allocates a TCH as a response to TCH ASSIGNED
TCH request (Channel Activation) Assignment_complete from BTS

RF CHN RELEASE
Rf_channel_release_ack
from BTS
KPI- Rules, TCH Drop due to RF/Abis
Hardware and Physical •Hardware problem (alarm 7745, 7743, TRX faulty/degraded) – reset as first action/switch TS
•Check overshooting based on ND232 (down tilt if overshooting)

TS check
•Check TRX Quality (UL and DL)based on ND196. Do retune if interference detected (also check bad quality happened on BCCH TRX or non BCCH TRX
•Check signal strength and path loss based on ND 208 – for hardware problem possibility

Parameter optimization
•CRO/CRH parameter changes
•TRP parameter implementation
KPI- Rules, TCH Drop due to RF Old
General problem •Same reason for Drop due to RF/Abis. All reason mention below can also generate TCH drop due to RF Old

Specific problem
•TCH drop due to RF old happened due to failure during HO.
•Reducing HO or fix parameter between HOC/POC and ADCE can fix this problem

Parameter optimization •Check inconsistency parameter between HOC, ADCE and BTS to avoid unnecessary HO
How unnecessary HO happened?? RxLev = -80dBm
CRO=0

GSM

DCS

RxLev = -95dBm
CRO=23
HO threshold = 20

On idle mode received level for GSM is

-80 dBm while DCS can be (-95 dBm +
(2 x 23) -49dBm
On dedicated mode user will move Unecessary HO can lead to DCR due
from DCS to GSM due to DCS level to RF Old and HO fail (ex. Due to GSM
already too low blocking)
How unnecessary HO happened?? RxLev = -95dBm
HO threshold = 20
RxLev = -92dBm
HO threshold = 20
RxLevmin from A to B = 12 RxLevmin from A to B = 12

GSM/DCS A GSM/DCS B

Call establish on cell A, then received After user serve by cell B, cell B will
level drop below HO threshold. User ask user to do handover as received
will move from cell A to cell B level on cell B already below HO
threshold.
KPI- Rules, TCH Drop due to Aif
•Usually happened not only on 1 cells instead this cause happened on 1

Hardware BSC
•Happened on link from BSC towards MGW/MSC

Non Hardware •Check Based on DX cause for detail problem

KPI- Rules, TCH Drop due to Transcoder
•Usually happened not only on 1 cells instead this cause happened on 1 BSC

Problem cause •Happened on link from BSC towards MGW/MSC

•Alarm TCSM usually exist

Solution •Reset TCSM as first action

•Replace TCSM card
KPI- Rules, TCH Drop
ND_163

Drops due to Drops due to

DCR > X% and Drops due to Drops due to Drops due to
Yes No No A-interface No Transcoder No
DCRnum > XX RF Reasons Abis Reasons other Reasons
Reasons Reasons

Yes Yes Yes Yes Yes

RF Abis A TR Other

No Case Closed No
KPI- Rules, TCH Drop (Other)
Other Case Closed No

Check all the Netw Act User Act, bcsu, Still lots of
Lapd fails No BTS fails No No No
alarms Fails act fails other drops

Yes Yes Yes Yes

signalling fails TRX or BTS
Configuration
or PCM fails. fails. Check Resets or act
problems,
Check that BTS/ TRX fail channel
check
transmissio / are working failures
configurations
parameters properly

Yes
KPI-
Here Rules,
Q0
coverage
are some examples how differentproblems
Q1 Q2
kind of HW problems
Like Normal distribution
Q3 Q4
can beand
(dlq_2a
Q5
found
ulq_2a)
Here are some examples how different kind of problems can be found

Q6 Q7 Q0
HW Problem, TRX/combiner etc is broken
Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 10645 8516 6813 5450 4360 3488 2791 2232 CL10 5323 4258 3406 2725 2180 1744 4563 9765
CL15 47043 37634 30108 24086 9865 7543 5643 2345 CL15 11761 9409 7527 6022 9383 1886 65432 7675
CL20
CL30
CL40
CL63
56204
200863
12785
4583
44963
160690
10228
1123
35971
128552
8182
583
28776
102842
6546
452
6574
17654
456
261
10324
9876
112
76
345
145
24
26
65
28
23
2
3
CL20
CL30
CL40
CL63
14051
33772
3196
1146
11241
27017
2557
281
8993
21614
2046
146
7194
17291
1636
113
18271
75037
4938
3378
2581
2469
28
19
65438
18765
3659
100
63562
14523
2648
174

HW problem, Q4 amount of samples is strange Interference problem

Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7 Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 5323 4258 3406 2725 2180 1744 1395 1116 CL10 5323 4258 3406 2725 2180 1744 1395 1116
CL15 23522 18817 15054 12043 18765 3772 2822 1173 CL15 23522 13234 10588 8470 13234 10588 8470 6776

1 4
CL20 28102 22482 17985 14388 36542 5162 173 33 CL20 28102 2123 1699 1359 2123 1699 1359 1087
CL30 67544 54035 43228 34582 150073 4938 73 14 CL30 67544 3634 2908 2326 3634 2908 2326 1861
CL40 6393 5114 4091 3273 9876 56 12 12 CL40 6393 4091 3273 2618 4091 3273 2618 4532
CL63 2292 562 292 226 6756 38 13 1 CL63 9987 7543 4323 3454 2275 1187 876 654

HW Problem, TRX/combiner etc is broken

Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
CL10 200863 160690 128552 102842 17654 9876 7865 6543
CL15 16543 13234 10588 8470 6776 2822 1173 234

2
CL20 2654 2123 1699 1359 1087 173 33 65
CL30 4543 3634 2908 2326 1861 73 14 28
CL40 5114 4091 3273 2618 2095 12 12 23
CL63 24 54 8 87 7 0 0 0

1. Lots of Q4 samples. Distribution is not OK  HW problem. Site reset will help

2. Lots of bad signal level samples. TRX/Combiner is broken. If no HW problem 
Site is totally in wrong place, site is like transferring traffic to another cell ( cause
level HO). Typically a HW problem
3. Lots of Q6 and Q7 samples. Distribution is not OK, no Q5 samples  HW
problems. Site reset or broken TRX
4. Typical normal interference problem.
KPI- Rules, InterferenceSame
analysis DL /UL
level – quality distribution
for both UL and DL
Rx Quality x Rx Level
HW Proble m :
Ba d Qua lity
Go od Qua lity fo r a ll Rx Le vels

Coverage Prob lem :

Ba d qua lity a nd
Low Rx Le vel
HW Problem
All samples below -
100dBm
CL10  <-100dBm

Hig h Rv Leve l
Interfe re nce Proble m :
Bad qua lity a nd
Hig h Rx Le ve l
NWD re po rt 2 0 4 m o de l
KPI- Rules, Interference, UL
-100dBm
q0
10645
q1
8516
q2
6813
q3
5450
q4
4360
q5
3488
q6
2791
q7
2232 MS power control can be seen here.
-95dBm 47043 37634 30108 24086 9865 7543 5643 2345 If Power is reduced → no bad UL
-90dBm 56204 44963 35971 28776 16574 5676 845 65
-80dBm 200863 160690 128552 102842 17654 3653 145 28
problems. BSC border is increasing
-70dBm 1234 987 790 632 505 404 323 259 good level samples
-47dBm 24 19 15 12 10 8 6 5

q0 q1 q2 q3 q4 q5 q6 q7
-100dBm 10645 8516 6813 5450 4360 3488 2791 2232 Bad interference problems. By POC
-95dBm 47043 37634 30108 24086 9865 7543 5643 2345 parameter interference can be
-90dBm 56204 44963 35971 28776 16574 5676 845 65 decreased, how power is adjusted
-80dBm 200863 160690 128552 102842 17654 3653 145 28 etc. Also optimum MS power feature
-70dBm 1234 987 790 632 505 404 323 259 improves UL interference, no full
-47dBm 24 19 15 12 10 8 6 5
power is sent after HO.

q0 q1 q2 q3 q4 q5 q6 q7 Bad quality sample due to signal

-100dBm 10645 8516 6813 5450 4360 3488 2791 2232 level problems. Diversity should be
-95dBm 47043 37634 30108 24086 9865 7543 5643 2345 checked, also possibilities to use
-90dBm 56204 44963 35971 28776 16574 5676 845 65
LNA to improve UL signal level.
-80dBm 200863 160690 128552 102842 17654 3653 145 28
-70dBm 1234 987 790 632 505 404 323 259
Antenna place should be also
-47dBm 24 19 15 12 10 8 6 5 checked if there are some obstacles
near the antenna.
KPI- Rules, Interference, UL, examples
-100dBm
-95dBm
-90dBm
UL_q0
490
8410
38512
UL_q1
137
3768
5249
UL_q2
368
3225
3066
UL_q3
605
3023
2323
UL_q4
1014
2767
1692
UL_q5
1378
2304
1570
UL_q6
1830
1561
1191
UL_q7
2586
1859
1268
Some UL interference in good signal
level. UL power control is not
-80dBm 219137 4600 2453 2311 1470 1724 1864 1221
working properly. Ul power control is
-70dBm 509591 2504 1812 3050 1271 1465 1649 337 good indicator, if power is adjusted,
-47dBm 244302 582 711 1363 1713 873 671 87 there are no big problems in UL
direction

UL_q0 UL_q1 UL_q2 UL_q3 UL_q4 UL_q5 UL_q6 UL_q7 There is no UL interference, or just a
-100dBm 70004 5020 3500 2564 2232 1946 2190 2579
-95dBm 80339 392 286 461 328 250 275 92
little. MS is adjusting power properly,
-90dBm 106883 233 318 602 199 146 234 64 there are only little samples in good
-80dBm 246892 227 314 860 298 338 395 60 UL signal level.
-70dBm 254875 155 298 935 203 135 166 15
-47dBm 23288 21 27 103 109 11 41 0

UL_q0 UL_q1 UL_q2 UL_q3 UL_q4 UL_q5 UL_q6 UL_q7 DL_q0 DL_q1 DL_q2 DL_q3 DL_q4 DL_q5 DL_q6 DL_q7
-100dBm 251992 30668 20552 18417 18156 18286 16983 12478 27862 5537 5529 6069 6109 6107 5389 4119
-95dBm 123653 1151 403 692 519 351 221 72 89094 4236 3853 3576 2893 2264 1372 584
-90dBm 62938 247 144 288 353 129 62 29 142228 2732 2550 2356 1510 1114 774 404
-80dBm 27005 51 65 149 177 82 40 16 222462 1523 1355 1552 716 812 1081 343
-70dBm 2831 3 9 28 87 10 6 0 44504 91 123 151 81 101 191 88
-47dBm 751 0 4 10 25 1 0 0 5994 49 17 17 12 29 65 10

Huge amount of UL bad samples. Cells is not working properly, it is like transferring traffic, UL quality/ UL level HO’s are triggering
immediately. These kind of cells must be investigated.
KPI- Rules, Interference, DL
-100dBm
-95dBm
-90dBm
q0
10645
47043
56204
q1
8516
37634
44963
q2
6813
30108
35971
q3
5450
24086
28776
q4
4360
9865
16574
q5
3488
7543
5676
q6
2791
5643
845
q7
2232
2345
65
Really bad interference problem → signal level is really
good (<-70dBm) and usually no better cell available → no
HO → samples can be seen in the table. Interference is
-80dBm 200863 160690 128552 102842 17654 3653 145 28
causing drops.
-70dBm 12785 10228 8182 6546 456 112 24 23
-47dBm 4583 1123 583 452 261 76 26 2

q0 q1 q2 q3 q4 q5 q6 q7 Bad interference problem → signal level good (<-80dBm)

-100dBm 10645 8516 6813 5450 4360 3488 2791 2232 and sometimes no better cell available. If better cell
-95dBm 47043 37634 30108 24086 9865 7543 5643 2345 available and quality samples are 4 or worse → HO (reason
-90dBm 56204 44963 35971 28776 16574 5676 845 65
quality or interference, depends on the parameter)
-80dBm 200863 160690 128552 102842 17654 3653 145 28
Interference is causing drops.
-70dBm 12785 10228 8182 6546 456 112 24 23
-47dBm 4583 1123 583 452 261 76 26 2

q0 q1 q2 q3 q4 q5 q6 q7 Situation is “network is working properly” If there are quality

-100dBm 10645 8516 6813 5450 4360 3488 2791 2232 4 or worse samples → quality HO. Most of the samples are
-95dBm 47043 37634 30108 24086 9865 7543 5643 2345 q4 samples. If lots of q5..q7 samples → interference
-90dBm 56204 44963 35971 28776 16574 5676 845 65 problem and interference must be analyzed / removed. If
-80dBm 200863 160690 128552 102842 17654 3653 145 28 quality HOs but no q5..q7 samples → better cell is available
-70dBm 12785 10228 8182 6546 456 112 24 23 → no interference problems. In these signal levels
-47dBm 4583 1123 583 452 261 76 26 2 overlapping exists and if handover reason is no PBGT, it will
be quality HO. By parameter amount of quality HOs can be
adjusted

q0 q1 q2 q3 q4 q5 q6 q7 Bad quality samples due to signal level problems. If PBGT

-100dBm 10645 8516 6813 5450 4360 3488 2791 2232 overlapping is not existing → lots of quality HOs + level HOs
-95dBm 47043 37634 30108 24086 9865 7543 5643 2345 (margin are lower than in PBGT).
-90dBm 56204 44963 35971 28776 16574 5676 845 65 Not interference problem, more signal level problem.
-80dBm 200863 160690 128552 102842 17654 3653 145 28
-70dBm 12785 10228 8182 6546 456 112 24 23
-47dBm 4583 1123 583 452 261 76 26 2

Check how much samples vs. HOs → are

better cells available or not.
KPI- Rules, Interference, DL, examples
DL_q0 DL_q1 DL_q2 DL_q3 DL_q4 DL_q5 DL_q6 DL_q7
-100dBm 12057 2827 3108 3952 4783 6200 7013 8156 There are almost as much samples Q5 and Q7 samples as
-95dBm 44818 4811 5041 5866 6587 7223 7259 6781 Q 4 samples → even interference is really bad or there is
-90dBm 98587 7107 7400 8334 8470 8781 7825 6162
no better cell available ( no ho’s after bad quality samples).
-80dBm 225919 7450 7731 8445 7726 7441 5695 3369
-70dBm 88708 1014 971 998 751 688 689 367
These kind of interference cells should be optimized,
-47dBm 15881 84 109 122 104 167 199 184 otherwise there are lots of drops etc

DL_q0 DL_q1 DL_q2 DL_q3 DL_q4 DL_q5 DL_q6 DL_q7

-100dBm 8006 1636 1681 2197 2379 2510 2025 1290
There are no as much Q5…Q7 samples as Q4 samples →
-95dBm 24951 1636 1627 1767 1037 431 175 53
-90dBm 57559 2171 1884 1651 781 330 161 47 after interference samples Quality HO is done or the
-80dBm 200602 5771 4686 4130 1736 566 254 97 interference situation is not so bad, for example sampling is
-70dBm 304206 5464 4310 3796 1315 350 153 105 Q0,Q2,Q4,Q2,Q5,Q0,Q2,Q3,Q4,Q2 → quality HO is not
-47dBm 108047 2134 1908 1623 689 230 129 64 triggering

DL_q0 DL_q1 DL_q2 DL_q3 DL_q4 DL_q5 DL_q6 DL_q7

-100dBm 7055 1398 1374 1906 2163 2003 1468 832 There are bad quality samples only due to signal level
-95dBm 20109 1307 1274 1161 694 332 211 84 problems.
-90dBm 34531 1053 745 587 273 131 94 41
-80dBm 107539 875 518 630 161 98 113 47
-70dBm 177614 283 316 663 61 32 29 9
-47dBm 58718 78 91 198 54 40 54 32
KPI- Rules, Interference (internal / external)
• Internal Interference
• Interference can be seen from stats or can be measured by scanner.
• Neighbor cells (DL) or mobiles (UL) are causing interference.
• By frequency / network planning interference can be decreased.
• External Interference
• Interference can be seen from stats or can be measured by scanner.
• External radio frequencies are causing interference
• Military use
• In the border area, interference is coming from other country.
• Some external wireless system (for example some wireless industry system) is causing
interference
• Increased I level can be also due to external interference
KPI- Rules, HOSR
General problem •Check TCH availability of cells. (alarm 7745, 7743, TRX faulty/degraded) – reset as first action/switch TS
•Check overshooting based on ND232 (down tilt if overshooting)

•Check all ADCE of problem cells – any possibility of missing ADCE and check freq, BSIC of all target cell

Specific problem •Check with ADCE have problem (example towards cell A) and check cause for HO
•Check ADCE type of contributor (intra BSC, inter Cell or inter BSC)
•Check all incoming ADCE of cell A

optimization •Modify ADCE parameter

•Fix target cell (if hardware problem founded)
KPI- Rules, HO fail
• sum(msc_o_succ_ho + bsc_o_succ_ho + cell_succ_ho)
• Total HO success ratio = 100 * (-------------------------------------------------------------------------------- ) (ho_65)
•
sum(msc_o_ho_cmd + bsc_o_ho_cmd_assgn + bts_ho_assgn)

•
• sum(a.msc_o_succ_ho + a.bsc_o_succ_ho + a.cell_succ_ho + a.msc_to_wcdma_ran_succ_tch_ho)
• Total HO failure ratio = 100 * (1- -------------------------------------------------------------------------------------) (hfr_2b)
• sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn + b.bts_ho_assgn+a.msc_gen_sys_wcdma_ran_ho_com)

• /* handovers failing due to blocking */

• sum(a.msc_o_fail_lack + a.bsc_o_fail_lack + a.cell_fail_lack
• + a.msc_to_wcdma_ran_fail_lack)
• HO failure ratio due to RF blocking = 100 * ---------------------------------------------------------------------------------------
• /* all HO attempts */
• sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn + b.bts_ho_assgn + a.msc_gen_sys_wcdma_ran_ho_com)
•
• (hfr_55a)