You are on page 1of 85

RADIOMOBIL WORKSHOP

Handover Process
April 10 14, 2000
Prague

Overview

Handover Decision Procedure


Handover Types & Triggers
Flexible Neighbour Cell Processing
Handover Flow Charts
Handover Power Level
Intra-Cell Handovers
Handover Margin Per Cause
Specific SDCCH & TCH Placement
Separate RxQual Thresholds
Adaptive Handovers

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

Handover Process Schematic


BTS RSS (HDPC)

MR
BTS(UL)
RXLEV
RXQUAL

HREQAVE

THRESHOLDS

CRITERION 1

HREQT

N&P VOTING

CRITERION 2

NEIGH_JOURNAL

TA
INT.ON
IDLE

DISUSE_COUNT

SSM

MICRO CELL
HO CAUSES

BPM

D
E
C
I
S
I
O
N

HO
Required

MSC

(EXT.)

TARGET CANDIDATES

NCELL 1-6

C
E
L
L

BSC

HO CAUSE &

RXQUAL(S)

T
A
R
G
E
T

S
E
L
E
C
T
I
O
N

TARGET CANDIDATES

RXLEV(S)

T
R
I
G
G
E
R
I
N
G

A
V
E
R
A
G
I
N
G

HO CAUSE &

MS(DL)

HO
Performed
(INT.)

POWER CONTROL COMMANDS


April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

MS / BSS Handover & Power Control

UL & DL Measurements Taken


Averages Produced
A Number of Averages Compared Against Threshold
Threshold Exceeded

Power Output Adjusted / Handover Triggered

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

Need for Handovers

Keep MS on best server cell


Seggregate & prefer users on different layers
Prevent dropped call
Maintain quality
React to congestion situation

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

Handover Strategy Drivers

Cell density
Cell geometry and antennas
Network topology and range
Clutter
Multi-layer and multi-band system
Traffic carried
Subscriber and capacity distribution

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

Handover Procedure

Purpose is to completely modify the channel allocated to the MS and is only


used when in RR connected mode i.e. cell changed, change in channel
configCell density
The handover procedure is always initiated from the network
Suspension of normal operation except for RR management (layer 3)
Disconnection of main signalling link and other links via local end release
(layer 2) and disconnection of TCHs, if any
Disconnection and deactivation of previously assigned chans. and their
release (layer1)
Activation of new channels, and their connection
Triggering of the establishment of data link connection for SAPI=0 on the
new channels

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

Handover Command

Characteristics of new channels and exact ACCH channel to be used

Characteristics of new cell, necessary for communication i.e. arfcn, ncc, bcc

Indication of physical channel establishment procedure with channel details


e.g. type, timeslot, TSC, frequency and if hopping MAIO, HSN

Power command and handover reference (access id)

Optionally timing advance, cipher mode setting

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

Handover Cause Priority


UL RXQUAL
(UL INTERFERENCE)
DL RXQUAL
(DL INTERFERENCE)
UL RXLEV
DL RXLEV
DISTANCE
POWER BUDGET

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

Handover Decision Procedure

Activity
Quality Handover

Link
Up
Down

Enable
ul_rxqual_ho_allowed
dl_rxqual_ho_allowed

Averaging
rxqual_ul_ho
rxqual_dl_ho

Decision
decision_1_ul_rxqual_av_h
decision_1_dl_rxqual_av_h

Threshold
l_rxqual_ul_h
l_rxqual_dl_h

Voting
P6, N6
P6, N6

Level Handover

Up
Down

ul_rxlev_ho_allowed
dl_rxlev_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_h
decision_1_dl_rxlev_av_h

l_rxlev_ul_h
l_rxlev_dl_h

P5, N5
P5, N5

Interference
Handover

Up
Down

interfer_ho_allowed
interfer_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_ih
decision_1_dl_rxlev_av_ih

u_rxlev_ul_ih
u_rxlev_dl_ih

P7, N7
P7, N7

ms_distance_allowed

rel_tim_adv

decision_1_tim_adv_av_alg

ms_max_range

P8, N8

Distance Handover
Power Budget
Handover

--

Source
pwr_handover_allowed
Neighbor

Up
Power Control due
to Level
Down

Power Control due


to Quality

Up
Down

Criteria 1

--

Criteria 2

--

April 2000

rxlev_dl_ho
decision_1_pbgt_rxlev_av_h
surround_cell/p

er neighbor

handover_margin

l_rxlev_ul_p
u_rxlev_ul_p
UL RxQual
HO
l_rxlev_dl_p
bts_power_control_allowed rxlev_dl_pc
decision_1_dl_rxlev_av_p
u_rxlev_dl_p
l_rxqual_ul_p
ms_power_control_allowed rxqual_ul_pc
decision_1_ul_rxqual_av_p
u_rxqual_ul_p
l_rxqual_dl_p
bts_power_control_allowed rxqual_dl_pc
decision_1_dl_rxqual_av_p
u_rxqual_dl_p
UL Interference
HO
-surround_cell
decision_1_ncell_rxlev_av_calc
-ms_power_control_allowed rxlev_ul_pc

--

rxlev_dl_ho
surround_cell

decision_1_ul_rxlev_av_p

decision_1_pbgt_rxlev_av_h

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

--

--

P1, N1
(increase)
P2, N2
(decrease)
P3, N3
(increase)
P4, N4
(decrease)
---

Notes
Used by
interference
handover as
well
-Relevant
quality
handover must
trigger first
Uplink only
No voting as
lastest hreqt
used
--

--

---

10

Handover Decision Procedure

Activity
Quality Handover

Link
Up
Down

Enable
ul_rxqual_ho_allowed
dl_rxqual_ho_allowed

Averaging
rxqual_ul_ho
rxqual_dl_ho

Decision
decision_1_ul_rxqual_av_h
decision_1_dl_rxqual_av_h

Threshold
l_rxqual_ul_h
l_rxqual_dl_h

Voting
P6, N6
P6, N6

Level Handover

Up
Down

ul_rxlev_ho_allowed
dl_rxlev_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_h
decision_1_dl_rxlev_av_h

l_rxlev_ul_h
l_rxlev_dl_h

P5, N5
P5, N5

Interference
Handover

Up
Down

interfer_ho_allowed
interfer_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_ih
decision_1_dl_rxlev_av_ih

u_rxlev_ul_ih
u_rxlev_dl_ih

P7, N7
P7, N7

ms_distance_allowed

rel_tim_adv

decision_1_tim_adv_av_alg

ms_max_range

P8, N8

Distance Handover
Power Budget
Handover

--

Source
pwr_handover_allowed
Neighbor

Up
Power Control due
to Level
Down

Power Control due


to Quality

Up
Down

Criteria 1

--

Criteria 2

--

April 2000

rxlev_dl_ho
decision_1_pbgt_rxlev_av_h
surround_cell/p

er neighbor

handover_margin

l_rxlev_ul_p
u_rxlev_ul_p
DL RxQual
HO
l_rxlev_dl_p
bts_power_control_allowed rxlev_dl_pc
decision_1_dl_rxlev_av_p
u_rxlev_dl_p
l_rxqual_ul_p
ms_power_control_allowed rxqual_ul_pc
decision_1_ul_rxqual_av_p
u_rxqual_ul_p
l_rxqual_dl_p
bts_power_control_allowed rxqual_dl_pc
decision_1_dl_rxqual_av_p
u_rxqual_dl_p
DL Interference
HO
-surround_cell
decision_1_ncell_rxlev_av_calc
-ms_power_control_allowed rxlev_ul_pc

--

rxlev_dl_ho
surround_cell

decision_1_ul_rxlev_av_p

decision_1_pbgt_rxlev_av_h

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

--

--

P1, N1
(increase)
P2, N2
(decrease)
P3, N3
(increase)
P4, N4
(decrease)
---

Notes
Used by
interference
handover as
well
-Relevant
quality
handover must
trigger first
Uplink only
No voting as
lastest hreqt
used
--

--

---

11

Handover Decision Procedure

Activity
Quality Handover

Link
Up
Down

Enable
ul_rxqual_ho_allowed
dl_rxqual_ho_allowed

Averaging
rxqual_ul_ho
rxqual_dl_ho

Decision
decision_1_ul_rxqual_av_h
decision_1_dl_rxqual_av_h

Threshold
l_rxqual_ul_h
l_rxqual_dl_h

Voting
P6, N6
P6, N6

Level Handover

Up
Down

ul_rxlev_ho_allowed
dl_rxlev_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_h
decision_1_dl_rxlev_av_h

l_rxlev_ul_h
l_rxlev_dl_h

P5, N5
P5, N5

Interference
Handover

Up
Down

interfer_ho_allowed
interfer_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_ih
decision_1_dl_rxlev_av_ih

u_rxlev_ul_ih
u_rxlev_dl_ih

P7, N7
P7, N7

ms_distance_allowed

rel_tim_adv

decision_1_tim_adv_av_alg

ms_max_range

P8, N8

Distance Handover
Power Budget
Handover

--

Source
pwr_handover_allowed
Neighbor

Up
Power Control due
to Level
Down

Power Control due


to Quality

Up
Down

Criteria 1

--

Criteria 2

--

April 2000

rxlev_dl_ho
decision_1_pbgt_rxlev_av_h
surround_cell/p

er neighbor

handover_margin

l_rxlev_ul_p
u_rxlev_ul_p
UL decision_1_dl_rxlev_av_p
RxLev HO
l_rxlev_dl_p
bts_power_control_allowed rxlev_dl_pc
u_rxlev_dl_p
l_rxqual_ul_p
ms_power_control_allowed rxqual_ul_pc
decision_1_ul_rxqual_av_p
u_rxqual_ul_p
l_rxqual_dl_p
bts_power_control_allowed rxqual_dl_pc
decision_1_dl_rxqual_av_p
u_rxqual_dl_p
-surround_cell decision_1_ncell_rxlev_av_calc
-ms_power_control_allowed rxlev_ul_pc

--

rxlev_dl_ho
surround_cell

decision_1_ul_rxlev_av_p

decision_1_pbgt_rxlev_av_h

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

--

--

P1, N1
(increase)
P2, N2
(decrease)
P3, N3
(increase)
P4, N4
(decrease)
---

Notes
Used by
interference
handover as
well
-Relevant
quality
handover must
trigger first
Uplink only
No voting as
lastest hreqt
used
--

--

---

12

Handover Decision Procedure

Activity
Quality Handover

Link
Up
Down

Enable
ul_rxqual_ho_allowed
dl_rxqual_ho_allowed

Averaging
rxqual_ul_ho
rxqual_dl_ho

Decision
decision_1_ul_rxqual_av_h
decision_1_dl_rxqual_av_h

Threshold
l_rxqual_ul_h
l_rxqual_dl_h

Voting
P6, N6
P6, N6

Level Handover

Up
Down

ul_rxlev_ho_allowed
dl_rxlev_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_h
decision_1_dl_rxlev_av_h

l_rxlev_ul_h
l_rxlev_dl_h

P5, N5
P5, N5

Interference
Handover

Up
Down

interfer_ho_allowed
interfer_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_ih
decision_1_dl_rxlev_av_ih

u_rxlev_ul_ih
u_rxlev_dl_ih

P7, N7
P7, N7

ms_distance_allowed

rel_tim_adv

decision_1_tim_adv_av_alg

ms_max_range

P8, N8

Distance Handover
Power Budget
Handover

--

Source
pwr_handover_allowed
Neighbor

Up
Power Control due
to Level
Down

Power Control due


to Quality

Up
Down

Criteria 1

--

Criteria 2

--

April 2000

rxlev_dl_ho
decision_1_pbgt_rxlev_av_h
surround_cell/p

er neighbor

handover_margin

l_rxlev_ul_p
u_rxlev_ul_p
DL decision_1_dl_rxlev_av_p
RxLev HO
l_rxlev_dl_p
bts_power_control_allowed rxlev_dl_pc
u_rxlev_dl_p
l_rxqual_ul_p
ms_power_control_allowed rxqual_ul_pc
decision_1_ul_rxqual_av_p
u_rxqual_ul_p
l_rxqual_dl_p
bts_power_control_allowed rxqual_dl_pc
decision_1_dl_rxqual_av_p
u_rxqual_dl_p
-surround_cell decision_1_ncell_rxlev_av_calc
-ms_power_control_allowed rxlev_ul_pc

--

rxlev_dl_ho
surround_cell

decision_1_ul_rxlev_av_p

decision_1_pbgt_rxlev_av_h

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

--

--

P1, N1
(increase)
P2, N2
(decrease)
P3, N3
(increase)
P4, N4
(decrease)
---

Notes
Used by
interference
handover as
well
-Relevant
quality
handover must
trigger first
Uplink only
No voting as
lastest hreqt
used
--

--

---

13

Handover Decision Procedure

Activity
Quality Handover

Link
Up
Down

Enable
ul_rxqual_ho_allowed
dl_rxqual_ho_allowed

Averaging
rxqual_ul_ho
rxqual_dl_ho

Decision
decision_1_ul_rxqual_av_h
decision_1_dl_rxqual_av_h

Threshold
l_rxqual_ul_h
l_rxqual_dl_h

Voting
P6, N6
P6, N6

Level Handover

Up
Down

ul_rxlev_ho_allowed
dl_rxlev_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_h
decision_1_dl_rxlev_av_h

l_rxlev_ul_h
l_rxlev_dl_h

P5, N5
P5, N5

Interference
Handover

Up
Down

interfer_ho_allowed
interfer_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_ih
decision_1_dl_rxlev_av_ih

u_rxlev_ul_ih
u_rxlev_dl_ih

P7, N7
P7, N7

ms_distance_allowed

rel_tim_adv

decision_1_tim_adv_av_alg

ms_max_range

P8, N8

Distance Handover
Power Budget
Handover

--

Source
pwr_handover_allowed
Neighbor

Up
Power Control due
to Level
Down

Power Control due


to Quality

Up
Down

Criteria 1

--

Criteria 2

--

April 2000

rxlev_dl_ho
decision_1_pbgt_rxlev_av_h
surround_cell/p

er neighbor

handover_margin

l_rxlev_ul_p
u_rxlev_ul_p
l_rxlev_dl_p
bts_power_control_allowed rxlev_dl_pc
decision_1_dl_rxlev_av_p
u_rxlev_dl_p
l_rxqual_ul_p
ms_power_control_allowed rxqual_ul_pc
decision_1_ul_rxqual_av_p
u_rxqual_ul_p
Distance HO
l_rxqual_dl_p
bts_power_control_allowed rxqual_dl_pc
decision_1_dl_rxqual_av_p
u_rxqual_dl_p
-surround_cell decision_1_ncell_rxlev_av_calc
-ms_power_control_allowed rxlev_ul_pc

--

rxlev_dl_ho
surround_cell

decision_1_ul_rxlev_av_p

decision_1_pbgt_rxlev_av_h

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

--

--

P1, N1
(increase)
P2, N2
(decrease)
P3, N3
(increase)
P4, N4
(decrease)
---

Notes
Used by
interference
handover as
well
-Relevant
quality
handover must
trigger first
Uplink only
No voting as
lastest hreqt
used
--

--

---

14

Handover Decision Procedure

Activity
Quality Handover

Link
Up
Down

Enable
ul_rxqual_ho_allowed
dl_rxqual_ho_allowed

Averaging
rxqual_ul_ho
rxqual_dl_ho

Decision
decision_1_ul_rxqual_av_h
decision_1_dl_rxqual_av_h

Threshold
l_rxqual_ul_h
l_rxqual_dl_h

Voting
P6, N6
P6, N6

Level Handover

Up
Down

ul_rxlev_ho_allowed
dl_rxlev_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_h
decision_1_dl_rxlev_av_h

l_rxlev_ul_h
l_rxlev_dl_h

P5, N5
P5, N5

Interference
Handover

Up
Down

interfer_ho_allowed
interfer_ho_allowed

rxlev_ul_ho
rxlev_dl_ho

decision_1_ul_rxlev_av_ih
decision_1_dl_rxlev_av_ih

u_rxlev_ul_ih
u_rxlev_dl_ih

P7, N7
P7, N7

ms_distance_allowed

rel_tim_adv

decision_1_tim_adv_av_alg

ms_max_range

P8, N8

Distance Handover
Power Budget
Handover

--

Source
pwr_handover_allowed
Neighbor

Up
Power Control due
to Level
Down

Power Control due


to Quality

Up
Down

Criteria 1

--

Criteria 2

--

April 2000

rxlev_dl_ho
decision_1_pbgt_rxlev_av_h
surround_cell/p

er neighbor

handover_margin

l_rxlev_ul_p
u_rxlev_ul_p
l_rxlev_dl_p
bts_power_control_allowed rxlev_dl_pc
decision_1_dl_rxlev_av_p
u_rxlev_dl_p
l_rxqual_ul_p
ms_power_control_allowed rxqual_ul_pc
decision_1_ul_rxqual_av_p
u_rxqual_ul_p
PBGT HO
l_rxqual_dl_p
bts_power_control_allowed rxqual_dl_pc
decision_1_dl_rxqual_av_p
u_rxqual_dl_p
-surround_cell decision_1_ncell_rxlev_av_calc
-ms_power_control_allowed rxlev_ul_pc

--

rxlev_dl_ho
surround_cell

decision_1_ul_rxlev_av_p

decision_1_pbgt_rxlev_av_h

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

--

--

P1, N1
(increase)
P2, N2
(decrease)
P3, N3
(increase)
P4, N4
(decrease)
---

Notes
Used by
interference
handover as
well
-Relevant
quality
handover must
trigger first
Uplink only
No voting as
lastest hreqt
used
--

--

---

15

Handover Decision Procedure

HO

RXLEV_NCELL(n) > RXLEV_MIN(n) + Max(0,Pa)


Evaluate criterion 1
for all neighbours
num_ho_cand = number
of neighbours passing

Evaluate criterion 2
for all neighbours
passing criteria 1

where : Pa = ms_txpwr_max(n) - P
P = max power of mobile

PBGT(n) Ho_margin

Execute the
appropriate
Motorola handover
procedure

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

16

Flexible Neighbour Cell Processing

Prior to GSR4, the ncell_proc flag simultaneously


enabled/disabled 4 separate functionalities

Management of unreported neighbours and missing MR


Qualify neighbours with lower levels than the serving cell
Level and Quality handovers at maximum power
Permits no warm up period for neighbours

Separate flags introduced to control each function


individually

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

17

Sporadic Neighbour Cell Reporting

A neighbour reported sporadically (some times does not fall


into the top 6) may be considered as qualified for criteria 1 and
2 processing
disuse_cnt_hreqave: Number of consecutive MR not reported
by a mobile and relating to a previously reported neighbour
0: The maximum disuse count is set to 8
1: The maximum disuse count is defined by the surrounding
cell hreqave
If the neighbour is reported before the maximum disuse count
is reached, it is reset to 0
If the disuse count reaches the maximum, the previous reports
for the neighbour are deleted and the averaging mechanism
reset neighbour no longer considered to be a valid handover
candidate

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

18

Sporadic Neighbour Cell Reporting

Each time a neighbour is not reported a disuse counter is


increased
neighbour_journal: Way of managing unreported neighbours
0: Only neighbours with disuse counter equal to 0 are
qualified

1: Qualified neighbours are those having a disuse counter


less than the value disuse_cnt_hreqave

April 2000

A neighbour will only be qualified if reported in the last MR


The value used to average and compute HREQT for that missing
report is repeated from the last reported value

The value used to average and compute hreqt for that missing report
is set to -110 dBm
No warm up period for neighbours (padded with -110 dBm for
averaging)
CUSTOMER SUPPORT SERVICES DIVISION
Network Operations Engineering

19

Neighbour Journal
WARM UP PERIOD

Neighbour_journal = 0
R
Disuse
0
Count
Q

NR

NR

0
Q

2
NQ

1
NQ

0
Q

0
Q

0
Q

0
Q

0
Q

0
Q

RXLEV -80

-82

-81

-81

-81

-79

-82

-83

-81

-79

First MREP

hreqave = 4

LEGEND:
NR - Not Reported
R - Reported

Q - Qualified
NQ - Not Qualified

HO cannot be performed
hreqt=1

Neighbour_journal = 1

First MREP NO WARM UP

NR

NR

NR

NR

NR

Disuse
0
Count
Q

0
Q

2
Q

1
Q

0
Q

0
Q

0
Q

0
Q

0
Q

0
Q

3
NQ

2
NQ

1
NQ

RXLEV -80

-82

-110

-110

-81

-79

-82

-83

-81

-79

-110

-110

-110

hreqave = 4

LEGEND:
NR - Not Reported
R - Reported

April 2000

Q - Qualified
NQ - Not Qualified

HO can be performed
hreqt=1

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

20

MR Processing Example
If neighbour_journal flag
is set to 0, the last
recieved RxLev for the
unreported neighbour is
used and a negative HO
may be triggered

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

21

Neighbour Journal Results

Improved Outgoing Inter-Cell HO Success Rate

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

22

Handover to Worse Neighbours

It is possible to qualify neighbours with RxLev lower


than the serving cell as candidates for RxLev
Handovers
worse_neighbor_ho

0: Disable handovers to a neighbour with lower RxLev than


the serving cell
1: Enable handovers to a neighbour with lower RxLev than
the serving cell

This parameter is not used in the Uplink Level


handover procedure. The RSS does not remove weaker
candidates from the handover recognised message

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

23

Handover at Maximum Power

It is possible to configure that RxQual and RxLev handovers


are only performed when MS / BTS are at full power
ho_only_max_pwr
0: Disable handovers at full power
1: Enable handovers at full power
All candidates for interference handovers are removed until MS
/ BTS is at full power
It is required that decision_alg_num = 1 with this functionality
to allow the MS / BTS to reach full power for quality cases
(PC)
If ho_only_max_pwr enabled, qual_margin will be bypassed
and HO to weaker cells may occur!

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

24

Neighbour Cell Processing


ncell_proc setting =0
For dl_rxlev handovers, neighbor must
be >server
For imperative handovers, bts power
status ignored
Neighbors require hreqave period for
candidature

Previously reported but now missing


neighbor ceases to be valid after 8sacch

April 2000

Equivalent GSR4 parameter


Worse_ngbr_ho = 0
Disable handover to neighbor to cell with
rxlev less than server
Ho_only_max_pwr = 0
i.e bts power status ignored
Neighbor_journal = 0
Neighbors require hreqave period for
candidature
Only neighbors reported in last sacch are
qualified
i.e. disuse_count = 0
disuse_count incremented every time
neighbor not reported
For averaging, use last reported value of
neighbor for missing report
If disuse_count reaches value defined by
disuse_cnt_hreqave then delete previous
neighbor measurement reports and reset
averaging mechanism
disuse_count_hreqave = 0
i.e neighbor ceases to be valid after
disuse_count reaches value = 8

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

25

Neighbour Cell Processing


ncell_proc setting = 1
For dl_rxlev handovers, neighbor may be
<server
For imperative handovers, bts power
must be at maximum for handover to be
allowed

Equivalent GSR4 parameter


W orse_ngbr_ho = 1
Enable handover to neighbor to cell with
rxlev less than server
H o_only_max_pwr = 1
i.e. bts power must be at maximum for
handover to be allowed

Neighbor averaging is im mediate,


missing neighbor average = -110dBm

Neighbor_journal = 1
Neighbor averaging is im mediate, initially
all neighbor information is padded with
value
-110dBm.

Previously reported but now


missing neighbor = -110dBm

Neighbor_journal = 1
For averaging, use -110dB m as value of
neighbor, for missing neighbor report
If disuse_count reaches value defined by
disuse_cnt_hreqave then delete previous
neighbor measurement reports and reset
averaging mechanism
disuse_count_hreqave = 1
i.e neighbor ceases to be valid after
disuse_count reches value defined in
surround_cell hreqave

Previously reported but now missing


neighbor ceases to be valid after
surroud_cell hreqave

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

26

UL/DL RxQual HO Process


Uplink/Downlink
ho_process

num_ho_ cand = 0

Note: decision_ alg_num=1 must be used


with ho_only_max_ pwr and qual _pwr_flag
YES
Abort handover
NO

NO
ho_only_max_
pwr =1

MS/ bts
ul/dl
Full Power

YES

NO
qual_pwr _flag
set?

YES

YES

NO
qual_margin_flag
set?

YES

YES

MS/ bts
ul/dl
Full Power
For each candidate:
pwr_bgt + adj_qual_margin < 0
if yes remove neighbour from
cand list and decrement num_ho_ cand

NO
send ho_ rec message with
num_ho_ cand cells ordered
best to worse by criterion 2 result
(only if num_ho_ cand >0

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

27

UL/DL Interference HO Process

Abort handover

Uplink/Downlink
ho_process

NO
ho_only_max_
pwr=1

NO

NO
qual_pwr_flag
set?

YES

YES

YES

MS/bts
ul/dl
Full Power
YES

NO
qual_margin_flag
set?

MS/bts
ul/dl
Full Power

YES

For each candidate:


pwr_bgt + adj_qual_margin < 0
if yes remove neighbour from
cand list and decrement num_ho_cand

NO
send ho_rec message with
num_ho_cand cells ordered
best to worse by criterion 2 result

April 2000

Note: decision_alg_num=1 must be used


with ho_only_max_pwr and qual_pwr_flag

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

28

DL Level HO Process
Downlink level
ho_process

worse_neighbor_ho
=1

NO

Remove candidates with


lower RXLEV than the server
from candidate list decrement
num_ho_cand

YES

Abort

YES

NO

BTS on full power

YES

num_ho_cand = 0
NO

YES

ho_only_max_pwr
=1
NO

SEND ho_recognised message


with num_ho_card cells ordered
best to worst by criterion 2 result
(only if num_ho_cand > 0)

April 2000

Note: decision_alg _num= 1, must be used


if ho_only max_pwr is to be enabled.

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

29

UL Level HO Process
Uplink level
ho_process

num_ho_cand = 0

YES

NO

ho_only_max_pwr =1

YES

NO
MS on full power
YES

NO
Abort ho
Send ho_rec message with
num_ho_cand cells ordered
best to worse by Criteria 2 result
Note: decision_alg_num=1 must be used if ho_only_max_pwr is to be enabled

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

30

Distance HO Process
Distance
ho_process

YES
num_ho_cand = 0

Abort ho

NO

Send ho_rec message with


num_ho_cand cells ordered
best to worse by Criteria 2 result

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

31

PBGT HO Process
Power Budget
ho_process

YES
num_ho_cand = 0

Abort ho

NO

Any cells satisfy


Criterion 2

NO

YES
Num_ho_cand= number
Of cells with positive
Criterion 2 result
Send ho_ rec message with
num_ho_cand cells ordered
best to worse by Criteria 2 result

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

32

Handover Parameter Look-up

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

33

Handover Power Level Calculation


Feature Overview

Command the Mobile Station on inter-cell intra-BSS handovers


with an optimal handover power level

Handover power level is derived from path loss calculation with


respect to the target cell

The calculation aims at instructing the MS to access the target


cell at the middle of the database defined power box
(u_rxlev_ul_p + l_rxlev_ul_p) / 2

Benefits:

April 2000

Promotes battery conservation


Reduces interference
Eliminates unnecessary MS power control after a handover
CUSTOMER SUPPORT SERVICES DIVISION
Network Operations Engineering

34

Handover Power Level Calculation

Before GSR3

Database defined parameter handover_power_level was


used to instruct the MS on inter-cell handovers

From GSR3

The handover power level is derived as follows:

Handover Power Level = MIN(C + ((A - B), D, P)


where:
A
max_tx_bts of the target cell
B
rxlev reported by the MS for the target cell
C
middle of the target cell power box:
(u_rxlev_ul_p + l_rxlev_ul_p)/2
D
max_tx_ms of the target cell
P
maximum power capability of the MS
April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

35

Handover Power Level Calculation


Example:
An inter-cell handover orders the MS to access the
target cell with power level 7.
target cell:
rxlev_dl
max_tx_bts
max_tx_ms
handover_power_level
l_rxlev_ul_p
u_rxlev_ul_p
Power Class 2 MS

= 37
= 2 (39 dBm)
= 5 (33 dBm)
= 5 (33 dBm)
= 30
= 40
= 39 dBm

derived handover power level:


= MIN((40 + 30)/2 + ((31 - 37), 33, 33)
= MIN(29, 39, 39)
= 29 dBm (power level 7)

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

36

Feature Limitations

To enable/disable the MS handover power level based on path


loss calculation:

use_derived_ho_power

0: feature disabled (default)


1: feature enabled

Provided only for inter-cell intra-BSS handovers due to the


target cell needing the power level information on initial
downlink SACCH. The information is included in the
Handover Command
Currently, GSM TS 08.08 does not provide a means to convey
power information to the target cell for an external handover
For incoming external handovers, the BSS instructs the MS to
use the database defined handover_power_level

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

37

Different Power Levels in GSM900 &


GSM1800

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

38

Inter/Intra-Cell Handovers

intra_cell_handover_allowed

0: Not performed by BSS (controlled by the MSC). Handover required


message may contain server as potential candidate along with other
targets

1: Performed by BSS if applicable. Intra-cell HO may be attempted


only if ho_recognised message specifies cause value quality or
interference

April 2000

Cause quality intra-cell attempt only if other targets are exhausted


Cause interference intra-cell first, if fails try other targets

2: Not permitted

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

39

Inter/Intra-Cell Handovers

inter_cell_handover_allowed

0: Not performed by BSS (controlled by the MSC). Handover required


message will be sent to MSC for both internal & external HO.

1: Performed by BSS if applicable. Internal inter-cell HO controlled by


BSC

2: Internal disabled & external enabled. Internal HO will not be


executed by MSC either.

3: Internal & external disabled. HO will not be executed by MSC


either.

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

40

Prefer Different Carrier for Intra-cell


Handover

A carrier change within a cell is in the best interest of a


mobile experiencing interference
This functionality will select the best channel on a
different carrier if possible for uplink or downlink
interference handovers
Interference bands used to classify channels within the
cell
Different carriers have priority as targets:

BCCH Carrier (non-hopping)


Non-BCCH Carrier (hopping)

Functionality always enabled

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

41

Prefer Different Carrier for Intra-cell


Handover

Compile a list A with channels in the best interference band

From list A, select any channels on a carrier other than the


current carrier and in a different hopping system if
applicable and make list B. If none, select best from list A

If non-hopping cell: From list B, select the best channel of


the BCCH carrier. If none, select best from list B

If hopping cell: From list B, select best channel on nonBCCH carrier. If none, select best from list B

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

42

Prefer Different Carrier for Intra-cell


Handover

NON HOPPING CELL

BCCH
April 2000

TCH1

TCH2

HOPPING CELL

BCCH

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

TCH1

TCH2
43

Prefer Different Carrier for Intra-cell


Handover

List A

List B

TCH Carrier 0

TCH Carrier 0

TCH Carrier 1

TCH Carrier 2

TCH Carrier 2
TCH Carrier 1

TCH Carrier 0

List C
TCH Carrier 0

TCH Carrier 0
PRIORITY

PRIORITY

PRIORITY

1. 3 carrier non-hopping cell. Carrier 0 is BCCH


2. Current call on Carrier 1 and interference handover is detected
3. TCH from Carrier 0 (BCCH) will be chosen
April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

44

Interference Averaging

INTAVE

One rolling average produced every 480 ms i.e. HREQT =


1 by default

Each idle timeslot sampled by HDPC for noise interference


and categorised into one of the interferer bands

One such category for each idle slot is passed to CRM in


RF resource indication message sent every
rf_res_ind_period (1-127 SACCH MF)

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

45

Time Limitation for Excessive Intra-cell


Handovers

If a cell has bad interference for all timeslots,


intra-cell handovers can be continuously done

This functionality will limit the number of


intra-cell handovers due to interference which
can occur in a specified amount of time by
escalating the handover to an RXQUAL
handover

This type of RXQUAL handover can be


subjected to the re-ordering described for
Micro-Micro and Timed Offset

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

46

Time Limitation for Excessive Intra-cell


Handovers

A per cell parameter hop_count, determines


the number of intra-cell hops one mobile will
do before doing the inter-cell handover

When the first intra-cell handover occurs, start


a timer for hop_count_timer SACCH periods

If the number of intra-cell hops exceeds


hop_count before hop_count_timer expires, a
RXQUAL handover will be done to another
cell

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

47

Time Limitation for Excessive Intracell Handovers

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

48

Time Limitation for Excessive Intra-cell


Handovers

Element Name

Min Max Default Type

hop_count
0
hop_count_timer 0
hop_count
hop_count

255 255
255 0

per cell
per cell

0
1-255

: Results in disabling intracell handovers


: Number of interference handovers allowed
within hop_count_timer
hop_count_timer 0
: Disables Functionality
hop_count_timer 1-255: Number of SACCH periods before
hop_count value is reset
Both elements are not prompted for in the add_cell command, but are modifiable via the
chg_cell_element or chg_element
commands
CUSTOMER
SUPPORT SERVICES DIVISION

April 2000

Network Operations Engineering

49

Handover Margin per Cause

More parameters needed to optimize or fine-tune


handovers in a network

Two new handover margins per neighbor specific to


the cause of the handover being detected

Uplink/Downlink RXQUAL - ho_margin_rxqual[n]

Uplink/Downlink RXLEV - ho_margin_rxlev[n]

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

50

Handover Margin per Cause


Handover

margins always
used for the candidate
exclusion procedure

Handover Detected

Per cell flag

Exclusion Procedure

ho_margin_usage_flag will use


the per cause handover margins
for the candidate sorting
procedure, otherwise ho_margin
is used

Sorting Procedure

Handover Generated

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

51

Handover Margin per Cause

Exclusion Procedure - Remove neighbor from


candidate list if:

Better Cell HO: PBGT-ho_margin[n]<0

UL/DL RXQUAL HO: PBGT-ho_margin_rxqual[n]<0

UL/DL RXLEV HO: PBGT-ho_margin_rxlev[n]<0

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

52

Handover Margin per Cause

Sorting Procedure

If ho_margin_usage_flag = 0

All Handover Causes: PBGT - ho_margin[n]

If ho_margin_usage_flag = 1

UL/DL RXQUAL HO: PBGT-ho_margin_rxqual[n]

UL/DL RXLEV HO: PBGT - ho_margin_rxlev[n]

All other Handover causes: PBGT - ho_margin[n]

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

53

Handover Margin per Cause

Element
Min
ho_margin_usage_flag 0

Max
1

Default
0

Type
per cell

ho_margin_rxqual[n]

-63

63

-63

per
neighbor

ho_margin_rxlev[n]

-63

63

-63

per
neighbor

Notes: ho_margin_usage element is not prompted for in the add_cell command, but
is modifiable via the chg_cell_element and chg_element commands
Per cause handover
margins are not prompted for in the add_neighbor
CUSTOMER SUPPORT SERVICES DIVISION
April 2000 but are modifiable via the modify_neighbor command
54
command,
Network Operations Engineering

Handover Margin per Cause


Candidate list

ho_margin_rxqual(n)

ho_margin_rxlev(n) Excluded?

Serving cell Rxlev: 15, Rxlev_min(n): 10


N 1: 44 rxlev
8
N 2: 42 rxlev
8
N 3: 24 rxlev
10
N 4: 14 rxlev
8
N 5: 8 rxlev
8

12
6
8
8
8

No/No
No/No
Yes/No
Yes/Yes
Yes/Yes

PBGT(n)

21 / 17
19 / 21
-1 / 1
-9 / -9
-15 / -15

RXQUAL Handover:
If ho_margin_usage=0, candidate list is : N1, N2
If ho_margin_usage=1, candidate list is: N1, N2
RXLEV Handover:
If ho_margin_usage=0, candidate list is: N1, N2, N3
If ho_margin_usage=1, candidate list is: N2, N1, N3
April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

55

Handover Reporting
HDPC

SSM

Handover_recognised message
contains:

Cause value
Qualified neighbours

When timer
(handover_recognised_period) is
running further handover decision
process is inhibited

Another message for the same


connection can not be generated

April 2000

handover_recognised

handover_recognised

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

56

Handover Evaluating
handover_recognised

MSC

SSM determines if internal or


external HO is needed

SSM

Cause value
Qualified neighbours

handover_required

When timer (GSM timer T7) is


running no more
handover_required message is
sent
handover_recognised

Another message for the same


connection can only be generated
after expiry of timer if another
handover_recognised message
was recieved

April 2000

handover_recognised

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

57

Handover Rejection

Handover_required_reject_switch

1: BSS expects to receive a "handover required reject"


message from the MSC. Any internal cells that are
candidates for the handover will not be included in the
"Handover Required" message. On receipt of the
"Handover Required Reject" message the BSS will perform
an internal handover if there are valid candidates.

0: BSS will not expect to receive a "Handover Required


Reject" message from the switch and will include internal
candidates in the "HO Required" message.

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

58

Preferred Target Cells

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

59

Improved SDCCH and TCH Control

Explicit SDCCH Assignment


Flexibility to designate the carrier on which the
SDCCH/8 channels will be configured
Maximum 2 Timeslots (16 SDCCHs) per carrier
Two parameters per RTF (Carrier)

April 2000

sd_load: Maximum number of SDCCH/8 timeslots


configurable per carrier (0, 1 or 2). Not prompted for inner
zone carriers
sd_priority: Priority of the carrier to configure SDCCHs (0 highest, 1, 2, , 250). Only prompted if sd_load is higher
than 0
CUSTOMER SUPPORT SERVICES DIVISION
Network Operations Engineering

60

SDCCH Placement Results

DEFAULT
Distributed over all the carriers on TS 0. The feature was disabled.
SDCCH on BCCH
All the SDCCHs allocated on the BCCH carrier
SDCCH on TCH1
All the SDCCHs allocated on the same TCH carrier (TCH1 has been
selected)
SETUP & CALL SUCCESS
89,46%
90,00%
89,00%

87,97%
87,14%

88,00%

85,83%

87,00%

86,37%
85,11%

86,00%
CALL_SETUP_SUC

85,00%

CALL_SUCCESS
84,00%
83,00%
82,00%
81,00%
80,00%
SDCCHBCCH

April 2000

SDCCHTCH1

DEFAULT

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

61

Improved SDCCH and TCH Control


Carrier Priority
Implements a radio channel (SDCCH/TCH) allocation
algorithm based on priorities
Priorities assigned per carrier
Interference On Idle is the first criterion
Consider carrier priority for intra-cell handovers
1 parameter per RTF (Carrier)

April 2000

Chan_alloc_priority: Priority of the carrier when using the


radio channel allocation algorithm (0 - highest, 1, 2, , 250)

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

62

Separate Rxqual Thresholds

Optimize quality handovers and power control for


both situations simultaneously on the same cell
Yes

RxQual
Thresholds
for Hopping

Hopping
Call ?
No

April 2000

RxQual
Thresholds
for NonHopping
CUSTOMER SUPPORT SERVICES DIVISION
Network Operations Engineering

HANDOVER &
POWER
CONTROL
PROCESSES

63

Quality HO/PC Thresholds for Hopping


hop_qual_enabled: Enable/Disable alternative thresholds
Prompts for the following parameters:

l_rxqual_dl_h_hopping
l_rxqual_ul_h_hopping
l_rxqual_dl_p_hopping
l_rxqual_ul_p_hopping

Quality thresholds can be set in:

BER: 0 - 1810 (1 step = 0.01% BER)


RxQual: 0 7
Depending on the value of alt_qual_proc (0 / 1)

Similar parameters are available for data: data_qual_enabled, ...

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

64

Adaptive Handovers

Normal

handovers operate based on either


absolute average or a voting mechanism

Adaptive

handovers operate by maintaining a


cumulative total:

Cumulative

value is maintained and updated


every measurement report

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

65

Adaptive Handovers

Handover speed adapts to the scenario:

Conditions deteriorate rapidly Fast handover


Conditions marginally poor Slow handover

A cumulative value is maintained and updated at each


measurement with the difference between the value
reported and a certain handover threshold

Adaptive handover algorithm for:

April 2000

Power Budget
Uplink and Downlink Quality
Uplink and Downlink Level
CUSTOMER SUPPORT SERVICES DIVISION
Network Operations Engineering

66

Adaptive Handovers

Selective activation per cell

adapt_ho_pbgt: Enable/Disable adaptive power budget handovers


adapt_ho_rxlev: Enable/Disable adaptive level handovers (UL and DL)
adapt_ho_rxqual: Enable/Disable adaptive quality handovers (UL and
DL)

Select BER or RxQual

Trigger adaptive quality handovers based on either BER or RxQual


values. Dependant on the value of alt_qual_proc as for standard quality
handovers

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

67

Adaptive Handovers

Trigger value per cell

adapt_trigger_pbgt: Adaptive power budget handovers trigger


adapt_trigger_rxlev_ul: Adaptive Uplink receive level handovers trigger
adapt_trigger_rxlev_dl: Adaptive Downlink receive level handovers trigger
adapt_trigger_ rxqual _ul: Adaptive Uplink receive quality handovers trigger
adapt_trigger_ rxqual _dl: Adaptive Downlink receive quality handovers
trigger

Separate quality threshold for hopping

adapt_ho_alt_trigger_rxqual: Enable/Disable the use of alternative quality


thresholds for hopping calls to trigger adaptive quality handovers
adapt_trigger_ hop_rxqual _ul: Adaptive UL receive quality handovers trigger
adapt_trigger_ hop_rxqual _dl: Adaptive DL receive quality handovers trigger

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

68

Adaptive handovers

Adaptive power budget handover


If
then

PBGT(n) >HO_margin
PBGT_cumulative value=
PBGT_cumulative value + (PBGT(n) - HO_margin)

If
then

PBGT_cumulative value > PBGT_trigger


generate handover

If
then

PBGT(n) < HO_margin


PBGT_cumulative value= 0 (i.e reset)

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

69

Adaptive handovers
Adaptive Handover With Ho_Margin = 0
RxLev

Server
Cumulative
Area

Neighbour
HO Point

Time

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

70

Adaptive handovers

Adaptive Handover With HO_Margin > 0


RxLev

Cumulative
Area

Server

Neighbour

HO. Point
HO. Margin

Time

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

71

Adaptive handovers

Adaptive level handover


If
then

rxlev_xx < l_rxlev_xx_ho, where xx=UL/DL


rxlev_cumulative value= rxlev_cumulative value +
(l_rxlev_xx_ho - rxlev_xx)

If
then

rxlev_cumlative value> rxlev_trigger


generate handover

If
then

rxlev_xx > l_rxlev_xx_h


rxlev_cumulative value= 0

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

72

Adaptive handovers
IMPERATIVE HANDOVER
BY RXLEV
RxLev
60
40

Level
Threshold

20

Time

4
8

Cumulative
Trigger

12

HO Point
Cumulative
Area
April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

73

Adaptive Handovers

Adaptive Quality Handover


If
then

rxqual_xx > l_rxqual_xx_h, where xx= UL/DL


rxqual_cumulative value= rxqual_cumulative value +
(rxqual_xx - l_rxqual_xx_h)

If
and
then

adap_ho_alt_trigger_rxqual is disabled
rxqual_cumulative value> adap_trigger_rxqual_xx
generate handover

or if

hopping is enabled and adap_ho_alt_trigger_rxqual is


enabled
rxqual_cumulative value > adap_trigger_hop_rxqual_xx
generate handover

and
then

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

74

Adaptive Handovers
CURRENT IMPERATIVE HO
RxQual
6

Dropped
Call
Quality
Threshold

4
2

Time

Cumulated
Area
12

Cumulative
Trigger

8
4

Time
April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

75

Adaptive Handovers
ADAPTIVE IMPERATIVE HO
RxQual
6

HO Point
Quality
Threshold

4
2

Time

Cumulated
Area
12

Cumulative
Trigger

8
4

Time

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

76

Adaptive Handovers Trial

One BSC under test

Adaptive Handovers in Macro cells with


SFH 1x1 (6 sites, 15 cells)

April 2000

Adaptive Handovers in Micro cells (5 sites)

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

77

Adaptive Handovers Trial

Macro cell parameters

RxQual Adaptive Handovers

RxLev Adaptive Handovers

l_rxlevl_xx_h=15
Cumulative_area=20
hreqave=1 for UL and DL

Power Budget

April 2000

l_rxqual_xx_h=3
Cumulative_area=12 for non hopping
Cumulative_area=15 for hopping
hreqave=1 for UL and DL

Cumulative_area=36
hreqave=1 for all the neighbours
ho_margin=0 for all macro neighbours
ho_margin=-24 for all micro neighbours
CUSTOMER SUPPORT SERVICES DIVISION
Network Operations Engineering

78

Adaptive Handovers Trial

11,5% Reduction in RF Losses


16% Reduction in drop call rate

DROPPED CALLS

DROPPED CALLS PER ERLANG


1,66%

1,80%

0,17%

1,39%

0,18%

1,60%

0,15%

0,17%

1,40%

0,16%

1,20%
1,00%
0,54%

0,61%

0,80%

TCH_RF_LOSS_RATE (%)

0,15%

DROP_CALL_RATE

0,14%

0,60%

0,13%

0,40%

0,12%

0,20%

0,11%
0,10%

0,00%
HOADAPT2

April 2000

DEFAULT

HOADAPT2

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

DEFAULT

79

Adaptive Handovers Trial

20% Reduction in Handover fails


More PBGT Handovers

HANDOVER CAUSE DISTRIBUTION

HANDOVER FAILURE RATE


1,77%
1,90%
1,41%

1,70%

100%
90%

1,50%

UPLINK_QUALITY

80%

UPLINK_LEVEL

70%

1,30%

POWER_BUDGET

60%

1,10%

DOWNLINK_QUALITY

50%

DOWNLINK_LEVEL

40%

0,90%

30%
20%

0,70%

10%

0,50%

0%

HOADAPT2

April 2000

DEFAULT

HOADAPT2

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

DEFAULT

80

Adaptive Handovers Trial

CALL SUCCESS
86,47%
87,00%

85,11%

86,00%
85,00%
84,00%
83,00%
82,00%
81,00%
80,00%
HOADAPT2

April 2000

DEFAULT

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

81

Adaptive Handovers Trial

Micro cell parameters

RxQual Adaptive Handovers

RxLev Adaptive Handovers

l_rxlevl_dl_h=15
Cumulative_area= 25
hreqave=1

Power Budget

April 2000

l_rxqual_dl_h=3
Cumulative_area= 10 for micros without fast mobiles
Cumulative_area= 8 for micros with fast mobiles
hreqave=1

Cumulative_area=30
hreqave=1 for all the neighbours
ho_margin=0 for all neighbours

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

82

Adaptive Handovers Trial

10% Reduction in RF Losses


12% Reduction in drop call rate
DROP_CALL & TCH_LOSSES

DROP_CALL PER ERLANG

0,8148
0,9
0,8
0,7
0,6
0,5
0,4
0,3
0,2
0,1
0

0,4016

0,7155

0,5
0,4589

0,4132

0,3260

0,4
Drop-Call

0,3

TCH-loss

0,2
0,1
0

HO - Adap

April 2000

DEFAULT

HO - Adap

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

DEFAULT

83

Adaptive Handovers Trial

4% Reduction in Handover Fails


8% Increase in traffic

HO_FAILURE_MICROS

TRAFFIC IN MICROS
2,1947

1,2448

1,3

2,2

1,1907

2,0286

2,1
1,2

1,1

1,9
HO - Adap

April 2000

DEFAULT

HO - Adap

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

DEFAULT

84

CONCLUSIONS

Adaptive Handovers:

Decrease TCH RF Loss, HO_Failure & Dropped calls

Increase traffic carried in micros

Good behaviour with hopping

Easy to configure (less parameters and unique values)

April 2000

CUSTOMER SUPPORT SERVICES DIVISION


Network Operations Engineering

85

You might also like