TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS

ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 10204 0326 DTZZA 1/1
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
Site
VELIZY MOBILE COMMUNICATION DIVISION
Originator(s)
PJ. PIETRI
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
Domain : ALCATEL 900/BSS
Division : PRODUCT DEFINITION
Rubric : SYS-TLA
Type : TECHNICAL FEATURE DESCRIPTION
Distribution Codes Internal : External :
PREDISTRIBUTION:
MCD - Velizy MCD - Colombes MCD - Berlin
L. CRUCHANT O. BESSET L. CARRE
P. DUPUY C. COLIN
J-P BARDEL
E. DESORBAY D. BERTHOUMIEUX MCD - Kontich SSD - Velizy
JY. AMAUDRUT J.F. MAILLARD M. BOLSENS (fpo)
O. BORDERIE B. VIREZ (fpo) G. VAN DIJCK
JJ. ROY B. LANDAIS
M. ROBERTS L. DARTOIS (fpo)
S. SAADA R. BIALOBRODA
S. BAUDET M. DELPRAT
P. FOUILLAND O. ROLLINGER
J. ACHARD M. DOBROSIELSKI
M. WU P. PELOUAS
PREDISTRIBUTION: DOC. CENTRES
MCD VELIZY MCD ANTWERP MCD STUTTGART
B. Marliac L. Van Eyck I. Lentzsch
ABSTRACT
This TFD describes the "Traffic management in handover algorithms" feature.
Approvals
Name
App.
D. BERTHOUMIEUX
AM
O. KERMIN
PM
M. FERRANDEZ
DPM
Name
App.
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 10204 0326 DTZZA 2/1
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
REVIEW
Not applicable
HISTORY
Version Date Author Details
Ed 01 16/10/95 C. Cherpantier First draft
Ed 02 27/10/95 C. Cherpantier after TLA review R5#6
Ed 03 20/11/95 C.Cherpantier editorial modifications
Ed 04
IN PREPARATION
29/01/97 F.Colin Rewriting of the TFD
Ed 04
PROPOSAL 01
03/03/97 F. Colin New version after TLAr6#2, according to
the minutes in ref. TD/SAS/EDE/272.97
Ed 04
PROPOSAL 02
03/04/97 F. Colin New version after TLAr6#5, according to
the minutes in ref. TD/SAS/EDE/489.97
Ed 04
RELEASED
18/04/97 F. Colin New version after TLAr6#9, according to
the minutes in ref. TD/SAS/LCR/569.97
Ed 05
RELEASED
23/03/98 PJ PIETRI Document updated. Reviewed by
moderator E. DESORBAY.
INTERNAL REFERENCED DOCUMENTS
Not applicable
FOR INTERNAL USE ONLY
Not applicable
END OF DOCUMENT
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 10204 0326 DTZZA 1/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
TECHNICAL FEATURE DESCRIPTION
TABLE OF CONTENTS
0. HISTORY....................................................................................................................................... 2
1. TYPE ............................................................................................................................................. 2
2. REFERENCES............................................................................................................................... 2
2.1. DOCUMENTATION REFERENCES:................................................................................... 2
2.2. DEFINITIONS ..................................................................................................................... 2
3. TECHNICAL DESCRIPTION ......................................................................................................... 3
3.1. INTRODUCTION................................................................................................................. 3
3.2. GENERAL REQUIREMENTS AND REMARKS................................................................... 3
3.2.1. Compliance to the Marketing Feature Description..................................................... 3
3.2.2. Requirements: .......................................................................................................... 3
3.2.3. Remarks: .................................................................................................................. 3
3.3. PRESENTATION OF THE TECHNICAL FEATURE............................................................ 3
3.3.1. Presentation of the decision process........................................................................ 5
3.3.2. Evaluation of the decision process........................................................................... 6
3.3.3. Restrictions of the traffic management in case of 1 TRX cells. ................................. 7
3.3.4. Introduction of the traffic management in handover algorithms ................................ 7
3.3.5. Handover behaviour depending on traffic load.......................................................... 9
4. OPEN POINTS: ........................................................................................................................... 11
5. HW/FW/SW IMPACTS:................................................................................................................ 11
5.1. OMC IMPACTS................................................................................................................. 11
5.2. BSC IMPACTS.................................................................................................................. 11
5.3. BTS IMPACTS.................................................................................................................. 11
5.4. TOOLS IMPACTS............................................................................................................. 12
6. SPECIFICATION IMPACTS......................................................................................................... 12
7. GLOSSARY:................................................................................................................................ 12
05 23/03/98 MCD/TD MCD/TD/SAS
04 07/04/97 MCD/TD MCD/TD/SAS
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 10204 0326 DTZZA 2/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
0. HISTORY
Version Date Author Details
Ed 01 16/10/95 C. Cherpantier First draft
Ed 02 27/10/95 C. Cherpantier after TLA review R5#6
Ed 03 20/11/95 C.Cherpantier editorial modifications
Ed 04 07/04/97 F.Colin Rewriting of the TFD
Ed 05 23/03/98 PJ PIETRI Document updated
1. TYPE
Linked to a Marketing Feature Description
Technical improvement without Marketing
impact
2. REFERENCES
2.1. DOCUMENTATION REFERENCES:
[1] TD/SAS/fc/1053.96/Ed. 1 Traffic load measurements and their application
[2] TD/SAS/fc/1681.96/Ed. 1 Traffic management
[3] 3BK 10204 0420 DRZZA Ed. 1 Improvements in radio resource management
[4] 3BK 10204 0327 DRZZA Ed. 1 General handover algorithms improvements
2.2. DEFINITIONS
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 10204 0326 DTZZA 3/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
3. TECHNICAL DESCRIPTION
3.1. INTRODUCTION
As the cellular networks grow in terms of subscribers, the issue of traffic management
becomes more and more serious. Indeed, due to the random generation of traffic in cells, it is usual
that a congestion is focused on a cell or two while the neighbour ones have free resources.
Now, thanks to an increase of the overlapping areas between cells, it is possible to modify the way
mobiles (and thus calls) are distributed among cells, according to the traffic situation of each cell. In
the same way, the arrival of new channel types (such as half rate channels) allows different allocation
strategies, depending on the congestion of cells.
However, such traffic management in a cellular network requires a continuous estimation of the
traffic situation in each cell. This estimation shall be reliable and fast enough to allow a better
distribution of the traffic load among cells and a gain in the overall network capacity.
This TFD proposes new algorithms in order to get an efficient and homogeneous traffic
management in handover algorithms.
3.2. GENERAL REQUIREMENTS AND REMARKS
3.2.1. Compliance to the Marketing Feature Description
There is currently no MFD dealing with traffic management in handover algorithms.
3.2.2. Requirements:
The traffic management defined in this TFD should give better performances than what is
currently implemented in the handover algorithms.
The new algorithms needed for traffic management should lead to an simple, coherent and
homogeneous mechanism. The same mechanism should be found wherever traffic load
estimation is needed. In this way, it should allow the discarding of all the different parameters
defined for that purpose.
3.2.3. Remarks:
3.3. PRESENTATION OF THE TECHNICAL FEATURE
The proposed improvements about traffic management are justified and detailed in [1] and [2].
These improvements are based on a decision process which gives an information about the
situation of traffic in one cell. This information is called Traffic_load and it can have three values :
high, low or indefinite.
The table below lists the different algorithms implied in the traffic management. For each
algorithm, it indicates the context of the application of the information Traffic_load as well as the
conditions and the requirements for such an application. The gain brought by this improvement is
explained for each algorithm involved in it. For the other algorithms, specific improvements will be
proposed.
From this table, one can see that the improvements are really valuable : they will improve the
way traffic can be distributed between cells through the various algorithms (traffic regulation of
umbrella cells, preferred band handover and traffic handover).
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 4/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
Description of the algorithm Application of
Traffic_load
Conditions Requirements Gain
Load factors used in GRADE
evaluation function No
Forced directed retry Non applicable
Half rate channels allocation in
case of cell congestion
(Unloading algorithm) *
No
Traffic regulations in the
umbrella cells No
Filtering of candidate umbrella
cells in case of transfer of fast
mobiles to the upper layer
Yes None Modification of the selection of
the cells for the cell raw list.
Compliance of the filtering with the
traffic regulation of umbrella cells.
Preferred band handover Yes None Modification of the cause 21
(Preferred band handover)
Better detection and application of
preferred band handover.
Discarding of 1 parameter :
MULTIBAND_LOAD_LEVEL
Traffic handover
Yes None Modification of the cause 23
(Traffic handover)
More reliable working of traffic
handover. Improvement of the traffic
distribution between cells.
* The improvements pertaining to this algorithm are described in ref. [3]
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 5/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
3.3.1. Presentation of the decision process
Before applying the information Traffic_load to algorithms, the decision process which gives this
information according to the situation of traffic in one cell must be defined.
As introduced in [1], the decision process shall give long term decisions : It means that the
decisions will be taken from a specific averaging, giving reliable decisions but requiring long
evaluation period.
Starting from these decisions, the algorithms are expected to be triggered (or to have their
behaviour changed) for a continuous and noticeable period, until a new decision is taken.
The decision process proposed to perform such a task is described in the following diagram.
Load
Averaging according
to A_TRAFFIC_LOAD
AV_TRAFFIC
LOAD
Threshold comparison with
N_TRAFFIC_LOAD averages
Traffic_load
Thresholds
Samples
This decision process is divided into two steps : the first one corresponds to what is currently
implemented : load samples (corresponding to the number of busy traffic channels divided by the
total number of traffic channels) are received regularly (with a periodicity going from 5 seconds
to 10 seconds). The load samples are averaged with a non-sliding window whose size is equal
to a parameter called A_TRAFFIC_LOAD. This parameter is changeable on a per cell basis. The
obtained average is recorded in the variable AV_TRAFFIC_LOAD.
The second step is new and it allows the definition of Traffic_load. Its principle is to consider
several consecutive averages AV_TRAFFIC_LOAD and to compare each of them to the
thresholds. The number of considered averages is given by the parameter N_TRAFFIC_LOAD,
which is changeable on a per cell basis.
The information Traffic_load will be set to its possible value (high, low and indefinite) according to
this threshold comparison. However, the number of averages considered, as well as the thresholds
used, will be different, depending on the current value of Traffic_load.
3 thresholds shall be defined :
- One called HIGH_TRAFFIC_LOAD, which corresponds to the decision Traffic_load = high
- Another called LOW_TRAFFIC_LOAD, which corresponds to the decision Traffic_load = low
- A last one, called IND_TRAFFIC_LOAD, which corresponds to the decision Traffic_load =
indefinite. IND_TRAFFIC_LOAD is between HIGH_TRAFFIC_LOAD and
LOW_TRAFFIC_LOAD. It can be disabled by tuning it to 0%.
The decision process will apply the following algorithm when a new AV_TRAFFIC_LOAD becomes
available :
If ( Traffic_load = indefinite ) and :
- The last N_TRAFFIC_LOAD averages AV_TRAFFIC_LOAD (including the new one) verifies
:
AV_TRAFFIC_LOAD > HIGH_TRAFFIC_LOAD
Then Traffic_load = high
INCORPORER
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 6/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
- The last N_TRAFFIC_LOAD averages AV_TRAFFIC_LOAD (including the new one) verifies
:
AV_TRAFFIC_LOAD < LOW_TRAFFIC_LOAD
Then Traffic_load = low
If (Traffic_load = low ) and the new AV_TRAFFIC_LOAD verifies :
( IND_TRAFFIC_LOAD <> 0 and AV_TRAFFIC_LOAD > IND_TRAFFIC_LOAD)
or AV_TRAFFIC_LOAD > HIGH_TRAFFIC_LOAD
Then Traffic_load = indefinite
If (Traffic_load = high ) and the new AV_TRAFFIC_LOAD verifies :
( IND_TRAFFIC_LOAD <> 0 and AV_TRAFFIC_LOAD < IND_TRAFFIC_LOAD)
or AV_TRAFFIC_LOAD < LOW_TRAFFIC_LOAD
Then Traffic_load = indefinite
As it can be seen, the algorithm makes easier the transfer of Traffic_load to indefinite than to
values low and high. This can be explained by the fact that these last values must be used with a
maximum of confidence : this means an ensured decision for choosing it and a quick return to the
indefinite value as soon as the confidence can no more be assumed.
Figures 1 gives an example of the application of the decision process with the combination of the
3 thresholds.
Traffic_load
high
HIGH_TRAFFIC_LOAD
LOW_TRAFFIC_LOAD
Indefinite
Variation of
averaged load
measurements
low
IND_TRAFFIC_LOAD
Figure 1 : Example of decision process with A_TRAFFIC_LOAD = 3 and 3 thresholds
3.3.2. Evaluation of the decision process
The decision process has been evaluated through software simulations. The main conclusions
coming from this evaluation are the following ones :
1. The decision process performs better than what is currently implemented in terms of
detection rate and reactivity of the decision.
INCORPORER
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 7/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
2. The decision process generates false alarms but these false alarms are not useless as they can
allow the application of the traffic management as a preventive solution towards blocked
calls.
3. The tuning of the decision process for high traffic load decisions must be based on the
averaging process i.e. the parameters A_TRAFFIC_LOAD and N_TRAFFIC_LOAD. The
required amount of load samples to evaluate a cell as loaded (which corresponds to
N_TRAFFIC_LOAD x A_TRAFFIC_LOAD) is about 24, whatever cell configuration.
4. The tuning of the decision process for low traffic load decisions is perfomed by means of the
thresholds i.e. the parameter LOW_TRAFFIC_LOAD.
5. The application of 3 thresholds gives flexibility and stability to the decision process. It
can be used in any case to reduce the periods of low or high traffic load, especially the ones
corresponding to false alarms.
6. For the specific case of 1-TRX, no decision on low traffic load is possible.
7. Again for 1-TRX, the decisions on high traffic load are uncertain and they can ensure a level of
performances (detection rate, decision delay) only for really high traffic load (in simulations, it
corresponded to a blocking rate of 5%).
3.3.3. Restrictions of the traffic management in case of 1 TRX cells.
The evaluation of the decision process presented previously shows that although good
performances in the general case, the traffic management shall be restricted in case of 1-TRX
cell.
In practice, this means that the 1-TRX cells (which are mainly microcells) could not receive
incoming handovers due to congestion of neighbour cells.
This restriction is not a problem as we can consider that such a cell has not enough resources to
accept supplementary handovers. The LOW_TRAFFIC_LOAD parameter could be used to inhibit
totally the decision on low traffic load. Moreover, the traffic management is already taken into account
in the speed discrimination process, as a way of unloading the umbrella cells towards microcells.
Moreover, the traffic management in case of 1 TRX congestion will be reactive only to strong
traffic load. Once again, if we consider that 1-TRX cells are mainly microcells, this is not really a
restriction as forced directed retry can be applied to avoid blocked calls in the microcells and
distribute the traffic with the umbrella cells. Other means of unloading (such that half rate channel
allocation) will be triggered to face up with critical period of congestion.
3.3.4. Introduction of the traffic management in handover algorithms
3.3.4.1 Preferred band handover
A condition on traffic_load should replace the comparison with Multiband_load_level in the
handover cause. In this way, the parameter Multiband_load_level could be discarded and the
condition on traffic load situation would become reliable.
The preferred band handover cause will be changed to :
CAUSE = 21 (high level in neighbour cell in the preferred band) (HO-22)
Traffic_load(0) = MULTIBAND_TRAFFIC_CONDITION
and Traffic_load(n) <> HIGH
and AV_RXLEV_NCELL(n) > L_RXLEV_CPT_HO(n) + max(0,[MS_TXPWR_MAX(n)-P])
and EN_MULTIBAND_HO = ENABLE
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 8/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
MULTIBAND_TRAFFIC_CONDITION is a parameter changeable on a per cell basis. It can have
three different values :
ANY_LOAD : the condition on traffic load is always fulfilled
NOT_LOW : the condition on traffic load is fulfiled only if traffic_load <> low
HIGH : the condition on traffic load is fulfiled only if traffic_load = high
3.3.4.2 Traffic load handover
The same mechanism could be kept but all the threshold comparison would be replaced by
conditions on the information of traffic load in the serving cell (traffic_load(0)) and in the
neighbour cell n (traffic_load(n)). This would enable to apply a long term decision process.
The specification of traffic load handover will be performed through three aspects :
- Modification of the cause Power Budget only for handovers from TCH to TCH and directed
retry from SDCCH to TCH (the cause 12 is unchanged for handover from SDCCH to SDCCH)
CAUSE = 12 (Power budget evaluation)
IF EN_TRAFFIC_HO(n,0) = ENABLE
PBGT(n) > HO_MARGIN(0,n) +max(0, DELTA_HO_MARGIN(0,n))
(n=1...BTSnum) (HO-6)
ELSE PBGT(n) > HO_MARGIN(0,n)
and EN_PBGT_HO = ENABLE
with PBGT(n) = AV_RXLEV_NCELL(n) - AV_RXLEV_PBGT_HO (HO-7)
- (BS_TXPWR_MAX - BS_TXPWR)
- (MS_TXPWR_MAX(n) - MS_TXPWR_MAX)
- PING_PONG_MARGIN(n,call_ref)
- Creation of the cause Traffic handover
CAUSE 23 : Traffic HO
DELTA_HO_MARGIN(0,n) < 0 dB
& PBGT(n) > HO_MARGIN(0,n) + DELTA_HO_MARGIN(0,n) (n=1...BTSnum)
and EN_TRAFFIC_HO(0,n) = ENABLE
- Definition of the value of DELTA_HO_MARGIN(0,n) according to the traffic situation of the
serving cell and the neighbour cell n.
If traffic_load(0) = high and traffic_load(n) = low,
DELTA_HO_MARGIN(0,n) = - DELTA_DEC_HO_margin
If traffic_load(0) = low and traffic_load(n) = high,
DELTA_HO_MARGIN(0,n) = DELTA_INC_HO_margin
else DELTA_HO_MARGIN(0,n) = 0.
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 9/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
3.3.4.4 Load factors used in the GRADE evaluation function
The LOADfactors should be kept as currently specified since they provide a great flexibility for the
operators and can be used in many different ways.
In the GRADE evaluation, the FREEfactors should be discarded because they create a redundancy
with the LOADfactors. Thus, the GRADE formula will be :
GRADE(n) = PBGT(n) + LINKfactor(0,n) + LOADfactor(n) - LOADfactor(0)
Finally, considering the improvements on the candidate cell evaluation (ref. to [4]), the filtering on
GRADE could disappear and, in this case, the GRADE formula could be simplified to :
GRADE(n) = PBGT(n) + LINKfactor(0,n) + LOADfactor(n)
3.3.4.5. Filtering of candidate umbrella cells in case of transfer of fast mobiles to the upper
layer
The information traffic_load should be used in order to really consider the traffic situation of the
umbrella cells. It is the only way to regulate efficiently the traffic load in these cells.
The filtering should therefore be changed to :
If the serving CELL_LAYER_TYPE = lower, the handover cause = 12 and MS_SPEED = fast, the cell
raw list must also contain the whole set of internal neighbour umbrella cells which information
traffic_load(n) = low (they do not need to verify the HO cause).
3.3.5. Handover behaviour depending on traffic load
Figure 2 represents the different handover behaviours which allow the unloading of a cell under
congestion . It should be stressed that it is the set of all these behaviours which can have a real
impact on the cell load and not just one of them.
It must be noticed that external cell, whose load is unknown, will correspond to Traffic_load =
indefinite.
When traffic_load = high, the traffic in the serving cell is considered as high, thus :
The dual band mobiles are transferred to their preferred band (the band which is the newest in
the network, so the one which must be less used).
Traffic load handovers are triggered towards cells in low traffic situation, in order to distribute
the traffic.
Theses different actions have a limited influence on the unloading of the loaded cell. However, the
combination at the same moment of these different mechanisms increases the capacity of handover
algorithms to unload a cell under congestion.
When traffic_load = indefinite, the traffic in the serving cell is not identifiable, thus the handover
algorithm do not take specific actions in order to load or unload the cells.
When traffic_load = low, the traffic in the serving cell is considered as low, thus :
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 10/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
The cell will be able to accept incoming traffic load handovers for a more distributed traffic.
The umbrella cells will accept fast moving mobiles from microcells.
These mechanisms are not meant to load the unloaded cell but to allow a better distributed traffic
and a diminution of blocked calls in the neighbour loaded cells.
Traffic_load = indefinite
Macro DCS
Macro GSM
Micro GSM
Fast mobile transfered
only to cell with
Traffic_load = low
Traffic load
Handovers
Traffic_load = low
Traffic_load = high
Handover
Multiband
Path of a mobile, the length of the arrow is proportionnal to its speed.
Handover related to traffic management
Figure 2 : Representation of the different way of unloading a cell by means of handover.
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 11/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
4. OPEN POINTS:
5. HW/FW/SW IMPACTS:
OMC BSC BTS TSC TRANS equipments TOOLS
OMU others Alcatel NCS Alcatel NCS
SW SW
5.1. OMC IMPACTS
Creation of parameters :
5 parameters for Traffic management :
A_TRAFFIC_LOAD_SAMPLEper cell basis, */C
N_TRAFFIC_LOADper cell basis, */C
HIGH_TRAFFIC_LOAD per cell basis, */C
LOW_TRAFFIC_LOAD per cell basis, */C
IND_TRAFFIC_LOAD per cell basis, */C
3 parameters for Traffic load handover :
EN_TRAFFIC_HO(0,n) per adjacent cell relationship, */C
DELTA_INC_HO_margin per cell basis, */C
DELTA_DEC_HO_margin per cell basis, */C
1 parameter for multiband handover :
MULTIBAND_TRAFFIC_CONDITION per cell basis, */C
Removal of 1 parameter :
MULTIBAND_LOAD_LEVEL
Modification of the status of 1 parameters :
LOAD_EV_PERIOD changed from per BSS basis to per cell basis and from CDE/B to */C
5.2. BSC IMPACTS
New algorithms to be implemented in the context of handover detection and candidate cell
evaluation.
5.3. BTS IMPACTS
TRAFFIC MANAGEMENT IN HANDOVER ALGORITHMS
ED 05 RELEASED
MCD
0326_05.DOC
10/07/98
3BK 11204 0326 DTZZA 12/12
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s


d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s


n
o
t
p
e
r
m
i
t
t
e
d
w
i
t
h
o
u
t
w
r
i
t
t
e
n
a
u
t
h
o
r
i
z
a
t
i
o
n
f
r
o
m
A
l
c
a
t
e
l
5.4. TOOLS IMPACTS
6. SPECIFICATION IMPACTS
Handover preparation.
Dedicated Radio Resource Control
BSS Telecom parameters.
7. GLOSSARY:
BSC Base Station Controller
BSS Base Station System
BTS Base Transceiver Station
MFD Marketing Feature Description
MS Mobile Station
OMC Operation and Maintenance Center
PC Power Control
TFD Technical Feature Description
END OF DOCUMENT