Professional Documents
Culture Documents
EVOLIUM SAS
VELIZY
HANDOVER PREPARATION
Originators
SYT
RELEASE B9
System
Sub-system
Document Category
:
:
:
ALCATEL 900/BSS
SYS-TLA
PRODUCT DEFINITION
ABSTRACT
This document specifies the algorithms to be implemented in Release B9 of the Alcatel BSS for:
Handover preparation,
Directed retry preparation.
Name
App.
C.LEJEUNE
Name
App.
U. TISCH
ED
EVOLIUM
04
SYT DPM
Approvals
R.MAUGER
SYT CCM
ZHANG Y.
BSC DPM
BTS DPM
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
1/110
REVIEW
Edition 01 Proposal 02
14/04/2004
MRD/TD/SYT/rma/0188.2004
HISTORY
Version
Edition 01
Proposal 01
Date
9-03-2004
Edition 01
Proposal 02
31-03-2004
Edition 01
Released
Edition 02
Proposal 01
Edition 02
Proposal 2
Edition 02
Released
Edition 03
Proposal 01
Edition 03
Released
Edition 04
Released
14/04/2004
ED
EVOLIUM
04
15/05/2004
Changes
First working version for Release B9 based on the B8 Handover
Preparation document (3BK 11202 0353 DSZZA Edition 03). The
impacts of the following SFD have been included:
SFD: Autonomous Packet Resource Allocation
Update based on review comments, according to review report
MRD/TD/SYT/rma/0.162.2004
Takes into account B8 CR 20/138465.
Updated according to review report MRD/TD/SYT/rma/0188.2004.
29/09/2004
Updated to take into account the impacts of the SFD Enhanced EGSM band handling (Ref. 3BK 10204 0612 DTZZA).
Updated to take into account the impacts of the SFD Dual Transfer
Mode (Ref. 3BK 10204 0604 DTZZA).
Updated according to review report MRD/TD/SYT/pmo/0468.2004.
08/04/2005
15/04/2005
Editorial update
25/11/2005
30/08/2004
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
2/110
TABLE OF CONTENTS
1 SCOPE .............................................................................................................................................. 7
2 FUNCTIONAL DESCRIPTION.......................................................................................................... 7
2.1
Overview .................................................................................................................. 7
2.2
Cell configuration ................................................................................................... 7
2.2.1 Cell Environments............................................................................................................ 7
2.2.1.1
2.2.1.2
2.2.1.3
2.2.1.4
2.2.2
2.2.3
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.4.1
2.3.4.2
2.3.4.3
2.3.4.4
2.3.5
2.3.6
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
3.1.3
3.1.3.1
3.1.3.2
3.1.3.3
3.1.4
3.2
3.2.1
EVOLIUM
04
Basic principle...................................................................................................................................... 39
Required parameters and variables...................................................................................................... 40
Parameter initialisation and modification .............................................................................................. 41
3.2.1.1
ED
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
3/110
3.2.1.2
3.2.1.3
3.2.2
Handover detection........................................................................................................ 46
3.2.3
3.2.3.1
3.2.3.2
3.2.3.3
3.2.3.4
3.2.3.5
3.2.4
Ordering process.................................................................................................................................. 69
Ordering process for 2G-3G handover ................................................................................................. 73
Filtering process................................................................................................................................... 73
ORDER cell evaluation process ........................................................................................................... 73
GRADE cell evaluation process ........................................................................................................... 74
3.3
3.3.1
3.3.1.1
3.3.1.2
3.3.2
3.3.3
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
4/110
REFERENCED DOCUMENTS
Alcatel references
[ 19]
[ 20]
[ 21]
[ 22]
[ 23]
[ 24]
[ 25]
[ 26]
[ 27]
[ 28]
[ 29]
[ 30]
[ 31]
[ 32]
[ 33]
[ 34]
[ 35]
[ 36]
3GPP references
[ 37]
[ 38]
[ 39]
3GPP TS 44.018
3GPP TS 45.008
3GPP TS 48.058
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
5/110
RELATED DOCUMENTS
[ 40] CCITT Z100. Structured Definition Language.
[ 41] GEODE user manual. VERILOG.
[ 42] ART/DST/PFK/20 - ALCATEL_BSS phase 1 description of radio link control algorithms and
guidelines for setting parameters values. ART/DST/PFK/20
Note : Most of the SDL diagrams have been produced with the software tool GEODE which is a
trademark of VERILOG [ 41]. The SDL standard is defined in [ 42].
PREFACE
Not applicable
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
6/110
SCOPE
This document specifies the algorithms to be implemented in this release of the ALCATEL BSS for :
handover preparation,
directed retry preparation.
Handover preparation consists of two functions which are considered separately in this document :
detection of the need to handover a radio connection,
candidate cell list evaluation.
Directed retry preparation is specified along with handover preparation.
2
2.1
FUNCTIONAL DESCRIPTION
Overview
The main objective of the handover preparation, in connection with power control (See [ 32]), is to allow
a maximum number of MS to operate in the network while maintaining a minimum interference level.
The algorithms shall ensure that any mobile is connected with the cell in which the output powers from
the MS and the BS are as low as possible (to reduce MS power consumption and interference in the
network) while keeping a satisfactory link quality.
When on a sufficient duration the propagation conditions keep worsening, then action must be taken.
The first action is to increase the output power levels at the MS or the BS (for further details, see [ 32]).
When the maximum allowed value has been reached, a handover may become necessary.
To reflect this philosophy in macrocells (not in microcellular environment), the algorithm allows for
handover on quality and strength reasons only when the last step of power control has been reached.
Great care must be taken in choosing the relative values of the thresholds for power control and
handover as well as the averaging window sizes (smaller window size and higher threshold for power
control than for handover). It must be remembered that, although it is desired that the MS transmits
with the lowest possible power, it is more important not to lose a call. Thus early triggering for the
power control is possible, by choosing small values for the averaging window sizes and higher
comparison thresholds.
2.2
Cell configuration
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
7/110
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
8/110
omnidirectional macrocell
sectorized cell for site reduction
Figure 1: Normal cell environment with one cell layer.
Inner zone
f2
f1
f3
Outer zone
f2
f1
f3
f1
f2
outer cell
70km
35 km
inner
cell
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
9/110
outer cell
outer limit
50 km radius
inner cell
outer limit
inner limit
mini cells
0.5<R<1 km
pedestrian area
Figure 5: Cell layout with mini cells below one umbrella cell
- microcells with umbrella cells
One layout is provided for microcellular applications, that should apply to very highly dense traffic
areas or when the available spectrum is very reduced. Figure 6 presents the cell layout for
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
10/110
microcells covered by an umbrella cell to provide continuous coverage and decreased blocking
rate.
The densification strategy for microcellular enables to use the already existing macrocell layer for
the umbrella cells.
Therefore, it may be possible for the operator to use already installed single (or concentric or
multiband) cells as umbrella cells for a microcellular network.
existing cells
1<R<2 km
microcells
R < 300 m
Figure 7: Typical cellular network using three cell layers and two frequency bands.
2.2.1.3
An operator with licenses in the different frequency bands (GSM900 and DCS1800) can mix in its
network cells which use GSM frequency band with cells using DCS frequency band. This case is
referred to as multiband cell environment. In the Alcatel BSS, the following multiband cells are not
supported:
- Multiband cells using GSM850 and DCS1900 bands, and,
- Multiband cells using GSM900 and DCS1900 bands
Multiband cell environment is supposed to be made out of a main part with cells of same frequency
band. This band is the oldest one acquired by the operator and it is the most used in its network : it is
called the classical band.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
11/110
With the other new frequency band, the operator will add new cells to its network. These cells will be
deployed either to extend the coverage of the existing network or to increase the traffic capacity of the
network rather than to improve the coverage.
When the operator cell deployment strategy is to increase the capacity of its network, the biband
mobiles (mobiles with capability in both frequency bands) are preferentially directed towards the new
cells which use the frequency band different from the classical one. That is why this band is called the
preferred band.
Multiband cell environment can be applied to conventional cell environment as well as hierarchical cell
environment. In this last case, the multilayer structure will interact with the multiband concept.
2.2.2
Cell profiles
The optimisation of the use of the frequency resources is a main concern for network operators.
The Alcatel BSS provides a span of cell environments that allows to cover the whole range of traffic
density requirements : from very dense urban centres with microcells up to very low traffic areas
(desert or off shore) with extended cell sites.
These different types of cell environment must be controlled and administered in a flexible way by the
operator.
For this purpose, the Alcatel BSS provides a set of cell profiles, which enable the operator to make a
starting point configuration by just applying the default values of the profile. Each profile provides all the
configuration data associated to one given cell as default settable values. This includes handover
parameters, but also power control settings, timers.
Nine main monoband profiles are defined : single cell, micro cell, mini cell, umbrella cell, extended
inner cell, extended outer cell, concentric cell, concentric umbrella cell, and indoor micro cell. These
profiles are duplicated by the internal parameter cell_band_type which can have two different values
for each profile. In order to give the operator the possibility to have its personal usage of the ALCATEL
parameters, the profiles are user-editable. This means that all default values associated to one given
profile can be modified to reflect the standard usage of the operator.
These cell profiles correspond to one unique combination of the five parameters :
- Cell dimension type : this parameter identifies the cell size in a finite set of cell dimensions(macro or
micro).
- Cell layer type : this parameter defines the layer type of a cell in connection with other cells and with
itself. In single layer cell environment, all cells have the same layer type (single). In a hierarchical cell
environment, three cell layer types distinguish the upper layer cells, the lower layer cells, and the
indoor layer cells.
- Cell_partition type : this parameter defines the type of frequency partitioning that is used in the cell.
- Cell range : this parameter identifies the cell as a normal cell or a part of an extended cell
- Cell_band_type : this parameter defines the type of frequency band used in the cell
The first three parameters are settable on a per cell basis and changeable on-line by O&M.
The cell_range parameter is set at BTS initialisation time and only changeable off-line.
Cell_band_type is an internal parameter derived from the BCCH frequency of the serving cell
(BCCH_FREQUENCY) or from the BCCH frequency of the neighbour cells n
(BCCH_FREQUENCY(n)), reported by the mobile.
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
12/110
### Normal
### Extended inner
### Extended outer
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
13/110
Cell configuration
In the following "Cell configuration" will refer to the combination of the five parameters :
Cell dimension type,
Cell layer type,
Cell partition type,
Cell range,
Cell band type.
The frequency range supported by the cell is indicated by the parameter FREQUENCY_RANGE. The
allowed ranges are PGSM, EGSM, DCS1800, DCS1900, and GSM850 for monoband cells, and
PGSM-DCS1800 or EGSM-DCS1800 for multiband cells. The term E-GSM is used for the whole
GSM-900 frequency band, i.e. the primary band (890-915 MHz / 935-960 MHz) plus the extension
band G1 (880-890 MHz / 925-935 MHz). The term G1 is used for the extension band, whereas the
term P-GSM is used for the primary band. In the following, a cell supporting only the E-GSM band,
i.e. the P-GSM and G1 bands, is never referred to as a multiband cell.
In this release of the ALCATEL BSS, all the possible monoband cell configurations are given in Table
1. In the first column Cell Profile of Table 1, the term GSM stands for the GSM900 or GSM850 band
and the term DCS for the DCS1800 or DCS1900 band depending on the
PLMN_FREQUENCY_BANDS parameter. All the other monoband cell configurations are forbidden as
they are not relevant for operation.
The O&M functions shall ensure that the cell configurations managed by the handover preparation are
authorised. The selection of one given cell profile for applying default values will force the value of the
cell configuration.
In monoband cells, the frequency range parameter FREQUENCY_RANGE can be set to PGSM,
EGSM, DCS1800, DCS1900, or GSM850. If the parameter FREQUENCY_RANGE equals to PGSM
EGSM, or GSM850 the cell band type is GSM. If the parameter FREQUENCY_RANGE equals to
DCS1800 or DCS1900, the cell band type is DCS.
Cell Profile
Cell
layer
type
Single
Cell
partition
type
Normal
Cell range
Cell
dimension
type
Macro
Normal
Cell
band
type
GSM
Macro
Single
Normal
Normal
DCS
Micro
Lower
Normal
Normal
GSM
Micro
Lower
Normal
Normal
DCS
ED
EVOLIUM
04
RELEASED
Frequency
range
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
HANDOVER PREPARATION
0400_04.doc
28/11/2005
14/110
Macro
Lower
Normal
Normal
GSM
Macro
Lower
Normal
Normal
DCS
Macro
Upper
Normal
Normal
GSM
Macro
Upper
Normal
Normal
DCS
Macro
Single
Normal
Extended-inner
GSM
Macro
Single
Normal
Extended-inner
DCS
Macro
Single
Normal
Extended-outer
GSM
Macro
Single
Normal
Extended-outer
DCS
Macro
Single
Concentric
Normal
GSM
Macro
Single
Concentric
Normal
DCS
Macro
Upper
Concentric
Normal
GSM
Macro
Upper
Concentric
Normal
DCS
Micro
Indoor
Normal
Normal
GSM
Micro
Indoor
Normal
Normal
DCS
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
PGSM,
EGSM, or
GSM850
DCS1800 or
DCS1900
Cell
dimension
type
Cell
layer
type
Cell
partition
type
Cell
range
Cell
band
type
Frequency
range
Macro
Single
Concentric
Normal
GSM
PGSM-DCS1800 or
EGSM-DCS1800
Macro
Single
Concentric
Normal
DCS
PGSM-DCS1800 or
EGSM-DCS1800
Micro
Lower
Concentric
Normal
GSM
PGSM-DCS1800 or
EGSM-DCS1800
Micro
Lower
Concentric
Normal
DCS
PGSM-DCS1800 or
EGSM-DCS1800
Macro
Lower
Concentric
Normal
GSM
PGSM-DCS1800 or
EGSM-DCS1800
Macro
Lower
Concentric
Normal
DCS
PGSM-DCS1800 or
EGSM-DCS1800
Macro
Upper
Concentric
Normal
GSM
PGSM-DCS1800 or
EGSM-DCS1800
Macro
Upper
Concentric
Normal
DCS
PGSM-DCS1800 or
EGSM-DCS1800
Micro
Indoor
Concentric
Normal
GSM
PGSM-DCS1800 or
EGSM-DCS1800
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
15/110
Micro
Indoor
Concentric
Normal
DCS
PGSM-DCS1800 or
EGSM-DCS1800
Cell_dimension_type : macro
Cell_layer_type : single
Cell_partition_type : normal
Cell_band_type : DCS
Figure 9: Allowed outdoor monoband cell configurations for cell_range = normal and different values of
cell band type. The indoor micro cells are not represented here.
EGSM radio resource allocation strategy
The EGSM radio resource allocation strategy is defined by the O&M parameter
EGSM_RR_ALLOC_STRATEGY. Two strategies are possible :
Different behaviour for E-GSM capable MS: The BSS handles differently E-GSM capable MS
from P-GSM only capable MS in E-GSM cells. When this value is used, only E-GSM capable
MSs are allowed to use to the E-GSM TRXs. Non EGSM capable MSs are served on P-GSM
TRXs.
Same behaviour for E-GSM capable MS: The BSS handles in the same way only P-GSM
capable MS as E-GSM capable MS in E-GSM cells, i.e. the BSS assumes that all GSM900 MS
are E-GSM capable.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
16/110
2.2.3 3G cells
The 3G cells are described by means of specifics cells attributes:
-
Mobile Network Code of a neighbor 3G cell of the own PLMN or of a foreign PLMN.
2.3
Handover preparation
This function can also be named "handover algorithms" as the algorithms described in section 3 are
the "heart" of this function. In the following the word "handover preparation" will be preferred to
"handover algorithms".
The ALCATEL handover preparation is derived from the basic algorithm found in Annex A of the 3GPP
Technical Specification 05.08 [ 38]. The main differences between both algorithms are described in [
19].
2.3.1
The handover preparation is in charge of detecting a need for handover and proposing a list of target
cells. Therefore it can be divided into two processes : handover detection and handover candidate
cell evaluation.
The handover detection process analyses the radio measurements reported by the BTS and the
possible alarms sent by RAM. Then, the candidate cell evaluation process is started each time a
handover cause (emergency or better conditions type) is fulfilled.
The handover candidate cell evaluation works out a list of possible candidate cells for the handover.
This list is sorted according to the evaluation of each cell as well as the layer they belong to (in a
hierarchical network) and the frequency band they use (in a multiband network).
Once the handover preparation is completed, the handover decision and execution (handover
management entity refer to [ 28) is performed under the MSC or BSC control. The directed retry
preparation (see definition in section 2.4) is performed by the handover preparation function.
Once the directed retry preparation is completed, the directed retry is performed either under the BSC
control (internal directed retry) or under the MSC control (external directed retry). These procedures
use signalling protocols described respectively in [ 23] and [ 24].
An example of implementation of these functions except for directed retry is given in the 3GPP
Technical Specification 45.008 [ 38].
The handover preparation requires indirectly (see below) input parameters provided by the function in
charge of the radio link measurements. This function is described in [ 22].
Most of the input data required by the handover functions are provided by a function called : Active
channel pre-processing. This function is described in [ 34]. It processes raw data given by the radio
link measurements (quality, level and distance) through the A-bis interface in compression mode or
non compression mode. The compression mode uses two functions: Radio measurements data
compression in the BTS and Radio measurements data decompression in the BSC. They are
described in [ 34].
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
17/110
The functions handover detection and handover candidate cell evaluation are specified in this
document.
Figure 10 depicts in a general way :
- the interconnections between these functions,
- the implementation of these functions in the ALCATEL BSS. The functions which are specified in this
document are represented in bold type.
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
18/110
2G-3G handover: This handover is based on the radio measurements. Each time there is at least
one UTRAN neighbour cell for which the filtered (averaged) Ec/No is sufficient, a need for
handover is detected and the target cell evaluation process is triggered.
For the handovers based on the radio measurements, each time a set of preprocessed (averaged)
measurements is available, the HO detection process checks whether a handover is needed or not. If
the need for a handover is detected, the target cell evaluation process is triggered. The need for
handovers often comes to compare a predefined threshold with a radio measurement. That is why this
process is sometimes called HO threshold comparison.
In case of an intercell handover alarm, the handover detection process gives to the cell evaluation
process :
the preferred target cell layer : indoor, lower, upper or none
the raw candidate cell list, which can be either all neighbours, or the subset which verify the
handover causes (plus other specific cells in particular cases). With each cell is given one of the
handover causes which have been verified.
Depending of the context of application, the emergency and better conditions HOs can be either
intercell or intracell HO. Six HO categories are then defined as shown in Table 3.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
19/110
Context of application
Intracell HO
Intercell HO
Emergency intracell HO
Emergency intercell HO
Better conditions HO
Channel adaptation HO
Channel adaptation HO
N/A
Resource management HO
Resource management HO
N/A
Handover family
Emergency HO
2G-3G Handover
N/A
Table 3: Main categories of handover
2G-3G external HO
The detection of a need for handover is performed through handover causes which are going to be
detailed. In what follows, each cause is thus identified with a number. The following sections detail the
different categories of handover according to the context of application (intercell or intracell) and the
handover cause.
2.3.3.1 Emergency intercell handovers
These handovers are triggered when the call conditions deteriorate significantly in order to rescue the
call. The handover causes concerned are listed in Table 4.
Handover Cause
Too low quality on the uplink
Too low level on the uplink
Too low quality on the downlink
Too low level on the downlink
Too long MS-BS distance
Too short MS-BS distance
Consecutive bad SACCH frames received in a microcell
Too low level on the uplink in a microcell compared to a high threshold
Too low level on the downlink in a microcell compared to a high threshold
Table 4: Emergency intercell handover causes.
Cause Number
Cause 2
Cause 3
Cause 4
Cause 5
Cause 6
Cause 22
Cause 7
Cause 17
Cause 18
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
20/110
It may happen for example that some peculiar propagation conditions exist at one point in time that
provide exceptional quality and level although the serving BS is far and another is closer and should be
the one the mobile should be connected with if the conditions were normal.
It may then happen that these exceptional conditions suddenly drop and the link is lost which would not
have happened if the mobile had been connected to the closest cell. For these reasons also, this
cause does not wait for the power control to react.
2.3.3.1.3 Too short MS-BS distance cause (Cause 22)
The too short MS-BS distance handovers are introduced to detect when a MS that is located in an
extended outer cell reaches the inner/outer extended cell limit and requires to be handed over towards
the extended inner cell. Therefore, it is only valid when the MS is in an extended outer cell. The case
the MS is in the extended inner cell and requires to be handed over the extended outer cell can be
performed by using the handover Cause 6.
2.3.3.1.4 Handovers specific to micro cells (Causes 7, 17, and 18)
In a microcellular network, the radio propagation conditions vary so fast that the handover requires to
be triggered without waiting for the action of the power control process. An example of this phenomena
is the street corner effect.
The handovers Cause 7 come to check if the last consecutive SACCH frames have been correctly
received. The handovers Causes 17 and 18 are triggered when the level of the received signal is below
a certain threshold. These latter causes are sometimes called level dropping under high threshold.
2.3.3.2 Better conditions intercell handovers
Better conditions intercell handovers are triggered to improve the overall system traffic capacity. This
spans : interference reduction, signalling load reduction, traffic unbalance smoothing. The basic
assumption for these handovers is that they should respect the cell planning decided by the operator.
The better conditions intercell handover causes are listed in Table 5.
Handover Cause
Power budget
High level in neighbour lower or indoor cell for slow mobile
High level in neighbour cell in the preferred band
Traffic handover
General capture handover
Fast traffic handover
Table 5: Better conditions intercell handover causes.
Cause Number
Cause 12
Cause 14
Cause 21
Cause 23
Cause 24
Cause 28
The main drawback of this handover category is the risk of "ping-pong" effect, which is an oscillating
back and forth handover between two (or three) cells. As the "better conditions intercell" handover are
meant to find the "best cell", the variation of the radio conditions will trigger a big amount of better
conditions intercell handovers, if the algorithms have a too sensitive reaction. Hence, some
mechanisms are forecast, in order to prevent these oscillations from occurring repeatedly at given
places.
In order to avoid the cancellation of an on-going location service procedure, HOP inhibits the better
conditions intercell handovers for TCH to TCH or from SDCCH to SDCCH when a location procedure
is on-going (whatever the positioning method that the SMLC has selected).
2.3.3.2.1 Power budget cause (Cause 12)
In this case, there is another cell with a better power budget i.e. the link quality can be improved or
maintained with a reduced transmission power of both the MS and the BTS. The radio link is not
degraded but there is the opportunity to decrease the overall interference level by changing the serving
cell of the given MS.
In conjunction with power control it presents the advantage to keep the interference as low as possible,
since it minimises the path loss between the BTS and MS.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
21/110
This cause is especially designed to cope with the requirement that the mobile should be connected
with the cell with which the lowest possible output powers are used. To assess which of the cells is this
"best cell", the algorithm performs every measurement reporting period the comparison of the path loss
in the current and in the neighbour cell. This is a feature special to the 3GPP standard which is made
possible because the mobile measures the adjacent cell signal levels and reports the six best ones.
The power budget calculation is described in details in Section 6.1.
This power budget gives the difference in path loss between the current cell and the adjacent cells
reported by the mobile.
When PBGT(n) is greater than 0, then the path loss from cell n is less than the path loss from the
serving cell and thus the radiated power in the downlink direction, and therefore in the uplink direction
as well, will be lower in cell n than in the current cell.
However it would not be advisable to hand over the MS to another cell as soon as PBGT is greater
than 0, because the MS would probably oscillate between the two adjacent cells as the propagation
conditions vary. A hysteresis mechanism is implemented to avoid this undesirable effect.
The MS may be handed over from the serving cell indexed 0 to a neighbour cell indexed n only if the
power budget exceeds the handover Margin(0,n). The handover Margin(0,n) can be modified
according to the traffic situation in the serving cell and the neighbour cell n. In this way, power budget
handover can be delayed towards a loaded cell and traffic load handover can be triggered from a
loaded cell (see section 2.3.3.2.4.). Once the MS is handed over, the same algorithm is applied in the
new cell, and a new PBGT is computed (which will be close to the opposite value of PBGT in the old
cell) and compared to a new HOMargin. (Thus, the global hysteresis (from cell 0 to cell n and back to
cell 0) is the sum of the two HOMargins).
However, It is still possible that a ping-pong mechanism is created by different handover causes, for
instance a handover may be triggered towards a neighbour cell for bad quality, but in the neighbour
cell, a handover back may be triggered for power budget reasons. In order to avoid this, an additional
anti-ping-pong mechanism is implemented in the power budget calculation. It enables to penalise for a
certain time the cell on which the call has precedently been (See Section 6.1).
In case of handover from SDCCH to SDCCH, this cause does not take the traffic situation into
account.
In multiband cell environment, the mobile can operate in a different band than the frequency band of
the BCCHs. This can lead to circular ping-pong handovers from the inner zone if the new band is DCS
1800 or to the impossibility to trigger PBGT handovers from the inner zone if the preferred band is
GSM 900.
To avoid this problem, when the MS is in the inner zone of a multiband cell, it may be handed over
from the serving cell indexed 0 to a neighbour multiband cell indexed n only if the power budget
exceeds the handover Margin(0,n) plus the offset handover margin which allows to handicap or favour
the PBGT (In the inner zone, the cause power budget is only checked between multiband cells, in a
way to maintain the MS in the preferred band).
The offset handover margin can possibly be used in concentric cells.
In some specific network, the operator may have two different frequency band areas in its network, the
first one using the classical frequency band cell (e.g. GSM900 or GSM850), and the second one using
the new frequency band (e.g. DCS1800 or DCS1900). At the border of these two areas, handovers
based on a power budget comparison are required so as to approach the behaviour of power budget
handovers between cells having the same frequency band. These handovers are allowed by setting
the specific flag EN_MULTIBAND_PBGT_HO defined on a per cell basis at the OMC. Only biband MS
can perform these multiband power budget handovers.
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
22/110
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
23/110
This is achieved by monitoring the traffic load of the cells which use the classical band and the
preferred band. If a biband mobile is connected to a cell in the classical band where a specific
condition on the traffic load is verified, and if this mobile receives good signal level from one neighbour
cell which uses the preferred band and where the traffic load is considered as not high, the preferred
band cause will be verified for this mobile.
Then, an intercell multiband handover will be performed towards the neighbour cell. The only
requirement for this handover is that the serving cell uses the classical band and the target cell, the
preferred band.
This cause is inhibited for handover from SDCCH to SDCCH.
2.3.3.2.4 Traffic handover (Cause 23)
The principle of this handover is to reduce the size of the serving cell when it is high loaded relatively to
a low loaded cell.
When the mobile moves away from the BTS, the power budget will increase and a better cell handover
will be triggered earlier.
It is recommended to inhibit Traffic handover towards 1 TRX cells. These cells do not have enough
resources to receive incoming handovers due to congestion of neighbour cells. Moreover because of
the great variation of traffic in the 1 TRX cells, traffic load is never considered as low.
This cause is inhibited for handover from SDCCH to SDCCH.
2.3.3.2.5 General capture handover (Cause 24)
In hierarchical network where cells use different frequency bands, a general capture handover is
required to manage, on a per cell adjacency basis, the possibility for the mobiles to be captured. This is
needed in order to synchronise the capture from a macrocell to a microcell (as described in 2.3.3.2.2)
or from the same macrocell to another cell of preferred band (as described in 2.3.3.2.3).
This general capture handover takes into account the load in the serving and in the target cell.
This cause is inhibited for handover from SDCCH to SDCCH.
2.3.3.2.6 Fast traffic handover (Cause 28)
A fast traffic handover is initiated by the RAM request Fast traffic handover request when the serving
cell is congested. Like directed retry, a fast traffic handover is triggered when a call request is queued
in RAM. However, instead of pushing the queued request into a neighbour cell, the fast traffic handover
pushes an established call out in a neighbour cell in order for the queued request to be served in the
serving cell. With the fast traffic handover alarms, HOP detects the MS that could perform such an
handover.
Cause 28 only applies to handovers from TCH to TCH.
2.3.3.3
Cause Number
Cause 10
Cause 11
Cause 15
Cause 16
2.3.3.3.1 Interference or low level intracell handovers (Causes 10, 11, 15, and 16)
Emergency handovers Causes 15 and 16 are triggered for intracell application when the radio link is
deemed to suffer a high level of interference. In this case, the channel assigned to the call is changed
for another channel in the same cell, on which the measured interference level is the smallest possible.
Since AMR calls can be performed over worse carrier-to-interference ratios than non AMR calls, the
parameter setting for Causes 15 and 16 is different for non AMR and AMR calls.
In the case of concentric cell or multiband cell environment, emergency intracell handovers Causes 10
and 11 concern handovers from the inner to the outer zone of the same cell (they are called interzone
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
24/110
handovers) as well as handovers performed within one zone (they are called intrazone handovers).
The possible interzone handovers in a concentric or multiband cell are shown in Figure 12.
Cause Number
Cause 13
In order to avoid the cancellation of an on-going location service procedure, HOP inhibits the better
conditions intracell handovers (always from TCH to TCH) when a location procedure is on-going
(whatever the positioning method that the SMLC has selected).
2.3.3.5
The causes specific to the channel adaptation handovers are listed in Table 8.
Handover Cause
HR-to-FR channel adaptation due to bad radio quality
FR-to-HR channel adaptation due to good radio quality
Table 8: Channel adaptation handover causes.
Cause Number
Cause 26
Cause 27
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
25/110
triggered, a HR-to-FR channel adaptation together with an intracell handover due to bad quality is
performed. The related handover cause is called HR-to-FR channel adaptation due to bad radio
quality.
There are two ways to trigger Cause 26. The first way consists of triggering Cause 26 only if a previous
intracell handover Cause 15 or 16 have been previously detected in the serving cell for the current MS.
This way is intended to non-hopping channels for which an intracell handover Cause 15 or 16 is
sometimes not sufficient to improve the quality of the call. If the quality is not sufficient due to a too
high interference level, instead of continuing triggering intracell handover Cause 15 or 16, a HR-to-FR
channel adaptation is triggered thanks to Cause 26. The second way applies when the intracell
handover Causes 15 and 16 are both disable for AMR calls. If a too high level of interference is
detected in the serving cell for the current MS, Cause 26 is then triggered. This second way intends to
improve the quality of hopping channels which quality is generally not much improved after an intracell
handover Cause 15 or 16.
Cause Number
Cause 29
Cause 30
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
26/110
Handover Cause
Cause Number
Cause 31
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
27/110
with GRADE, :
- The candidate cell evaluation process does not interact with the handover detection.
- The candidate cell evaluation process takes into account the relative load of traffic channels in the
candidate cells.
The type of cell evaluation is chosen by the operator on a (serving) cell basis and is provided to the
BSC with the parameter CELL_EV.
Each algorithm uses the following parameters to compare candidate cells:
ORDER
GRADE
Power budget
X
X
Number of free TCH/FS
X(1)
Cell load (%)
X(1)
Handover type
X
Table 11: Comparison of candidate cell evaluation algorithms
(1) The number of free TCH in the calculation of ORDER and the cell load in the calculation of
GRADE will only be used in case of an internal candidate cell and when the flag
EN_LOAD_ORDER is set to ENABLE. Otherwise, there is no offset due to load information in
the candidate cell evaluation.
2.3.4.4 3G cell ranking
When in the serving cell, there is one UTRAN neighbour cell for which the Ec/No, averaged by the BSS
(AV_ECNO), is higher or equal to a predefined threshold (THR_ECNO), the reported UTRAN cells are
ranked according to this averaged Ec/No:
-
for each UTRAN Cell(n), meeting the criteria AV_ECNO(n) THR_ECNO, the Cell n shall be
added in the list of candidate cells, the cause 31 is added together with the 3G cell identity in the
list.
the 3G candidate cells shall be ranked according to AV_ECNO(n) in increasing order, the cell
with the highest AV_ECNO placed on the top of the list. The 3G candidate cells are on top of the list
preceding the 2G candidate cells that are also evaluated.
Note: The BSC maintains a filtered list with both 2G and 3G cells with associated handover causes,
because in the case where all the 3G cells are rejected, it shall be possible to handover to a 2G cell.
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
28/110
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
29/110
In the case of concentric or multiband cells, a handover cause due to high interference level (causes
15 or 16, see 3.2.2) triggers an intrazone or an interzone handover. Those are particular cases of
intracell handovers.
A handover cause due to too low level in the inner zone (causes 10 or 11) or the better zone cause
(cause 13) triggers an interzone handover (see section 3.2.2.1.2). An interzone handover is a particular
case of intracell handover.
The two HO causes (10, 11) cannot be enabled or disabled individually. These causes are enabled and
disabled when the parameter CELL_PARTITION_TYPE = CONCENTRIC and = NORMAL respectively
(see sections 2.2 and 3.2.2). Moreover the HO cause 13 must not be disabled in case of allocation in
the inner zone during Normal Assignment (the flag EN_BETTER_ZONE_HO should not be looked at
when deciding whether the MS should go to the inner zone or outer zone).
Therefore, HO_INTRACELL_ALLOWED flag does not control the enabling/disabling of the interzone
handover, but only of the intrazone handover (or interzone handover causes 15 or 16).
Finally , the flag EN_INTRACELL_REPEATED does not control the repetition of the interzone
handover.
T_INHIBIT_CPT
T_FILTER
T_HCP
MS & BS
parameters
cell
configuration
parameters
"Start DR algos"
Active channel
preprocessing
"Start T_INHIBIT_CPT"
"Start T_HCP"
EN_CAUSE_28
averaged measurements
for handover detection
Handover
detection
HO cause,
raw cell list,
PREF_LAYER
New codec type
HO candidate
cell evaluation
Alarm
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
30/110
Flows description
The description is done at BSC level (see Figure 13).
Input flows
- TCH usage information
* FREEfactor(n), LOADfactor(n), AV_LOAD, t(n): respectively correction factor of ORDER
depending on free level of cell n, correction factor of GRADE depending on load of cell n, averaged
traffic load and absolute number of free TCH in the cell n (refer to [ 30]). In concentric cells, if the
flag EN_LOAD_OUTER is set to enable, the load is evaluated considering the TCH resource in the
outer zone instead of in the whole cell. If E-GSM TRXs are defined in the cell, and the flag
EN_LOAD_EGSM is set to enable, and the EGSM_ALLOC_STRATEGY is set to Different
behaviour for E-GSM capable MS, the load is evaluated including the EGSM TCH resource of the
cell (See [ 30] for more details in the specific case of concentric cells). These flows are BSC
internal.
* Traffic_load(n): situation of the traffic in the cell n (refer to [ 30]).
* LOAD_SV3(n): indicates whether or not the cell n is loaded [ 30].
* EN_CAUSE_13: flag that indicates in concentric or multiband cells whether or not the inner zone
is more loaded than the outer zone.
- Averaged measurements for handover detection :
* AV_RXQUAL_UL_HO, AV_RXQUAL_DL_HO, AV_RXLEV_UL_MCHO,
* AV_RXLEV_UL_HO, AV_RXLEV_DL_HO, AV_RXLEV_DL_MCHO,
* BS_TXPWR, MS_TXPWR, AV_RANGE_HO, AV_RXLEV_PBGT_DR,
* AV_BS_TXPWR_HO, AV_BS_TXPWR_DR,
* AV_RXLEV_PBGT_HO, AV_RXLEV_NCELL(n), AV_RXLEV_NCELL_BIS(n).
* AV_RXLEV_NCELL_DR(n), n=1..BTSnum.
* BFI_SACCH
* AV_RXQUAL_DL_CA_HR_FR, AV_RXQUAL_UL_CA_HR_FR,
* AV_RXQUAL_DL_CA_FR_HR, AV_RXQUAL_UL_CA_FR_HR,
* AV_ECNO(n)
Control flows
- Cell configuration parameters : CELL_DIMENSION_TYPE, CELL_LAYER_TYPE,
CELL_PARTITION_TYPE, CELL_BAND_TYPE, ZONE_TYPE, CELL_RANGE,
FREQUENCY_RANGE.
- MS and BS parameters :
Maximum and minimum MS/BS powers allowed in the cell :
MS_TXPWR_MAX, BS_TXPWR_MAX, MS_TXPWR_MIN, BS_TXPWR_MIN,
Maximum MS power in the inner zone of a concentric or multiband cell :
MS_TXPWR_MAX_INNER,
Maximum BS power in the inner zone of a concentric or multiband cell : BS_TXPWR_MAX_INNER.
- T_FILTER : Time after which a no alarm message (an alarm message with no candidate cell, see
section 3.2.4) is sent to the handover management entity, if no new alarm has been detected whilst
running.
- T_HCP : time during which penalty PING_PONG_HCP is applied to the preceding cell (cause 12);
time during which penalty is applied to the preceding inner zone (cause 13).
- T_INHIBIT_CPT: Time during which the capture handover Causes 14, 21, and 24 are inhibited.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
31/110
- P : MS classmark (maximum MS power) for the concerned frequency band(s) (GSM900, GSM850,
DCS1800, DCS1900). In case of biband mobiles, depending on the setting of the
PLMN_FREQUENCY_BANDS parameter, the following MS classmark are considered:
- both MS classmark for GSM900 band and MS classmark for DCS1800 band, or,
- both MS classmark for GSM850 band and MS classmark for DCS1800 band, or,
- both MS classmark for GSM850 band and MS classmark for DCS1900 band, or,
- both MS classmark for GSM900 band and MS classmark for DCS1900 band.
- Candidate cell evaluation parameters :
* MS_TXPWR_MAX(n) : n=1..NBR_ADJ,
* HO_MARGIN(0,n) : n=1..NBR_ADJ,
* HO_MARGIN_LEV(0,n) : n=1..NBR_ADJ,
* HO_MARGIN_QUAL(0,n) : n=1..NBR_ADJ,
* HO_MARGIN_DIST(0,n) : n=1..NBR_ADJ,
* PRIORITY(0,n) : n=1..NBR_ADJ,
* EN_PRIORITY_ORDERING,
* OFFSET_HO_MARGIN_INNER,
* RXLEV_MIN(n) : n=1..NBR_ADJ,
* LINKFACTOR(0,n) : n=1..NBR_ADJ,
* NBR_ADJ : number of adjacent cells.
* identity (BSIC + BCCH ARFN) of the preceding cell if internal to the BSC
* EN_SPEED_DISC : flag enabling the sending of fast MS to the umbrellas
* EN_PBGT_FILTERING : flag enabling/disabling the filtering process
* L_LOAD_OBJ : maximum load on the umbrella to hand over a fast moving mobile
* PING_PONG_HCP : handicap applied to the preceding cell for power budget calculation or
handicap applied to the preceding inner zone in the cause 13.
See definition of these parameters in section 3.2.2.
* AV_ECNO(n) : n=1..NBR_ADJ_3G
"Fast traffic HO request" : Request from the RAM entity for checking if the current call can
perform a fast traffic handover.
Move from PS to CS zone HO : Request from RAM entity to make an intra-cell handover ,
to optimise packet radio resource allocation.
- MS zone Indication Request: Request from the RAM entity (refer to [ 30]) for determining the
zone location of the mobile in a concentric or multiband cell (see section 3.1.1) in case of allocation
during Normal assignment in the concentric or multiband cell.
- HO and DR enabling flags : HO_INTERCELL_ALLOWED, EN_INTRACELL_REPEATED,
EN_FORCED_DR,
EN_RXQUAL_UL, EN_RXLEV_UL,
EN_RXQUAL_DL, EN_RXLEV_DL,
EN_DIST_HO, EN_PBGT_HO, EN_MULTIBAND_PBGT_HO
EN_INTRA_UL, EN_INTRA_UL_AMR,
EN_INTRA_DL, EN_INTRA_DL_AMR,
EN_MCHO_H_UL, EN_MCHO_H_DL, EN_MCHO_RESCUE,
EN_MCHO_NCELL,
EN_PREFERRED_BAND_HO,
EN_GENERAL_CAPTURE_HO,
EN_TRAFFIC_HO(0,n),
EN_BETTER_ZONE_HO,
EN_AMR_CA.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
32/110
- EN_LOAD_ORDER : flag controlling the use of the FREEFACTOR and LOADFACTOR in the
calculation of candidate cell list (ORDER and GRADE modes).
- HO detection parameters :
* RXLEV_UL_ZONE, RXLEV_DL_ZONE, ZONE_HO_HYST_UL, ZONE_HO_HYST_DL,
* L_RXQUAL_UL_H, L_RXQUAL_UL_H_AMR, L_RXLEV_UL_H, RXLEV_UL_IH,
* L_RXQUAL_DL_H, L_RXQUAL_DL_H_AMR, L_RXLEV_DL_H, RXLEV_DL_IH,
* U_TIME_ADVANCE, L_TIME_ADVANCE,
* N_BAD_SACCH,
* L_RXLEV_CPT_HO(0,n), n=1..NBR_ADJ,
* U_RXLEV_UL_MCHO, U_RXLEV_DL_MCHO,
* L_RXLEV_NCELL_DR(n), n = 1..NBR_ADJ,
* EN_BI-BAND_MS(n),
* OUTDOOR_UMB_LEV(0,n), n ### { neighbour umbrella cells}
* PREFERRED_BAND : Frequency band type preferably used by biband mobiles.
* MULTIBAND_TRAFFIC_CONDITION : Condition on traffic load in the serving cell for a multiband
handover.
* CAPTURE_TRAFFIC_CONDITION : Condition on traffic load in the serving cell for a general
capture handover.
* NEIGHBOUR_RXLEV(0,n),
* RXLEV_LIMIT_PBGT_HO,
* DELTA_INC_HO_margin, DELTA_DEC_HO_margin,
* THR_RXQUAL_CA_HIGH, THR_RXQUAL_CA_NORMAL,
* OFFSET_CA_HIGH, OFFSET_CA_NORMAL.
* EN_LOAD_BALANCE : Flag that enables or disables the load balance between the inner and
outer zones in concentric cells,
* EN_AMR_HR, EN_AMR_FR,
* THR_ECNO
Internal flows
- Candidate cell evaluation input
* HO cause
* raw cell list of potential candidate cells with the MS zone indication in concentric cells
* PREF_LAYER : preferred target cell layer
* New codec type for Cause 29
- "Start T_HCP" : This timer is started in the target cell after an incoming internal handover. This timer
is also started after an intracell handover in a concentric cell when the preceding zone is the inner
zone.
- Start T_INHIBIT_CPT: This timer is started under the conditions specified in Section 3.2.4. While
running, it inhibits the capture handover Causes 14, 21, and 24.
- EN_CAUSE_28: This flag enables or disables the triggering of Cause 28 in HOP. The enabling of
Cause 28 is controlled via RAM messages.
Output flows
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
33/110
- Alarm: message that is sent to HOM when an alarm has been detected. This message contains
the Candidate cells list (with the MS Zone Indication for each concentric cell of the candidate cells list),
the HO cause, and the new codec type (for Cause 29).
- Fast handover alarm ACK: message that is sent to RAM when a fast traffic handover has been
detected. This message contains the reference of the queued request, and the call reference.
- MS Zone Indication ACK(ZONE): message that is sent to RAM (refer [ 30]). This message
contains the zone in the concentric or multiband cell where the mobile is situated.
2.4
2.4.1
System aspects
The directed retry consists in an SDCCH to TCH intercell handover during the call set-up process. The
directed retry is triggered when given radio conditions are met and the serving cell is congested. The
handover to TCH in another cell reduces the call set-up time (queuing phase) and allows the sharing of
resources from one cell with another, thus overcoming traffic load unbalance.
In this release of the ALCATEL BSS, the directed retry can be internal or external to the BSS (see [ 23]
and [ 24]).
The start and stop of the directed retry preparation are described in Section 3.3.1.1.
The directed retry may be performed :
- either on handover alarms : If a handover alarm is detected during queuing, and the candidate cell
evaluation process indicates at least an internal or external cell, then the BSS will perform a directed
retry .
-
or on alarm of forced directed retry : If during queuing, an internal or external neighbour cell is
reported with a sufficient level and has free TCH, then the BSS will perform a directed retry .
The expression "Forced directed retry" refers to this case, because the radio conditions in the serving
cell do not represent a need for handover. The cause which leads to forced directed retry is assimilated
to a "better conditions cause" in the handover preparation.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
34/110
2.4.5
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
35/110
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
36/110
3
3.1
DYNAMIC BEHAVIOUR
Functions linked to handover preparation
3.1.2.1
In order to assign from the start a TCH in the zone corresponding to the MS location, the information
on the measured level gathered by the handover detection function is used.
The RAM entity (refer to [ 30]) during Normal Assignment in a concentric cell or in a multiband cell will
request to the handover detection function (with the indication MS Zone Indication Request, see
section 2.3.6) the zone where the MS is deemed to be : inner or outer zone.
The HOP entity first checks whether or not the MS supports the frequency band of the inner zone:
If the MS is in a PGSM-DCS1800 or a EGSM-DCS1800 multiband cell and the MS is not biband ,
then the indication is set to OUTER.
If the MS is in a EGSM-DCS1800 multiband cell, the EGSM_ALLOC_STRATEGY is set to
Different behaviour for E-GSM capable MS, there is only EGSM TRXs in the inner zone, and the
MS is biband but does not support the E-GSM band, then the indication is set to OUTER.
To this avail, the handover detection function will check all the relations in the cause "outer zone too
high (cause 13) except the condition EN_BETTER_ZONE_HO=ENABLE in (HO-17) using
the AV_RXLEV_UL/DL_HO averages, if A_LEV_HO measurements have been received,
the average of the RXLEV_UL/DL measurements already received.
The checking of Cause 13 will indicate in which zone the MS is deemed to be on a radio criterion.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
37/110
The load balance between the inner and outer zones is managed by the RAM. The MS is allocated to
the inner zone if the MS is deemed to be in the inner zone on a radio criterion, and the inner zone is
less loaded than the outer zone.
The MS zone indication is sent to RAM in the message MS zone indication ACK (See Sections 2.4.2
and 4.2).
In (HO-17), the average of the RXLEV_NCELL(n) measurements is computed for each neighbour cell
with a same window whose size is determined by the number of MEASUREMENT RESULT messages
which have already been received since the first received MEASUREMENT RESULT message with a
Layer 3 info present.
As long as this number is lower than A_PBGT_HO, it is used as window to calculate these averages.
When this number becomes higher than A_PBGT_HO, then A_PBGT_HO is used as window to
calculate these averages.
3.1.2.2 Allocation in the inner zone in case of incoming handover
Two cases must be distinguished according that the incoming handover is based on a SDCCH channel
or on a TCH channel.
Case of an incoming handover on SDCCH
In case of an incoming intercell handover on SDCCH a channel of the outer zone of the concentric or
multiband cell is always assigned to the mobile station.
Case of an incoming handover on TCH
In case of an incoming intercell handover on TCH, the MS will be handed over in the zone
corresponding to its location if the flag EN_BETTER_ZONE_HO is set to enable (if
EN_BETTER_ZONE_HO is set to disable the MS is handed over in the OUTER ZONE).
For that the information on the downlink measured level of the target cell RXLEV_NCELL is used.
Each time, a candidate cells list is provided to the HOM entity, it must indicate for each concentric or
multiband cell, the zone where the MS is deemed to be in the target cell: inner or outer zone. If the MS
is in a PGSM-DCS1800 or a EGSM-DCS1800 multiband cell and the MS is not biband, the indication is
always OUTER zone. Furthermore, if the MS is in a EGSM-DCS1800 multiband cell, the
EGSM_ALLOC_STRATEGY is set to Different behaviour for E-GSM capable MS, there is only EGSM
TRXs in the inner zone, and the MS is biband but does not support the E-GSM band, then the
indication is always OUTER.
So each time a concentric or multiband cell is in the candidate cells list, the handover detection
function checks the equation (HO-0) in a way to determine the MS zone location in this concentric or
multiband cell.
As mentioned in Section 3.1.2.1, the load balance between the inner and outer zones is managed by
RAM.
MS zone location
If
{
(HO-0)
BS_TXPWR_MAX
BS_TXPWR_MAX_INNER,
and
EN_BETTER_ZONE_HO
}
Then
The MS is in the inner zone
Else
The MS is in the outer zone.
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
38/110
- the average of the RXLEV_NCELL(n) measurements already received from the neighbour cell target
cell n (if between two measurements, in which the neighbour cell is reported, a measurement comes
in, in which the neighbour cell is not reported, a 0 will be used to calculate the average).
RXLEV_DL_ZONE, ZONE_HO_HYST_DL, BS_TXPWR and BS_TXPWR_MAX_INNER are the
parameters of the target concentric or multiband cell. They are available only if the intercell handover is
performed in the same BSC.
3.1.2.3
For concentric cell environment, the cause "power budget" is applied in the inner zone as well as in the
outer zone.
For multiband cell environment, the cause "power budget" is applied in the inner zone as well as in the
outer zone. In the inner zone, if the flag EN_MULTIBAND_PBGT_HO is set to disable, the cause
power budget is only checked between multiband cells, in a way to maintain the MS in the preferred
band.
In order to avoid unnecessary handover alarms on SDCCH for all mobiles geographically located in the
inner zone, the handover alarms cause 13 on SDCCH (from outer zone towards inner zone) must be
filtered by the handover preparation function.
For initiation of an intercell handover between a concentric or multiband cell (inner and outer zone) and
the defined adjacent cell, the same handover criteria and handover strategies hold true as for nonconcentric cells.
The criteria for handover between the inner and outer zones is based either on the received signal
level or on the interference level (see section 3.2.2.1.2). This kind of handover is called "interzone
handover".
A handover due to interference (cause = 15 or 16) will change, when it is possible, the frequency of the
radio channel in case of non-hopping channels.
As the inner zone contains only a few frequencies, this will give the opportunity to make an interzone
handover from the inner to the outer zone in case of interference problems in the inner zone.
In case of interference problems in the outer zone, the MS will always make an intrazone handover (it
will stay connected to the outer zone).
In case of hopping channels an interzone handover may occur from the inner to outer zone but never
in the reverse direction (as with non-hopping channels).
Both intrazone and interzone handovers are intracell handovers.
3.1.3
3.1.3.1
MS speed discrimination
Basic principle
The speed discrimination procedure can only be activated in a hierarchical cell environment, i.e. when
the serving CELL_LAYER_TYPE = upper or lower or indoor . It is based on the dwell time in the lower
or indoor layer cells, either as serving or neighbour cells.
The knowledge of the speed of a MS is indicated with a flag MS_SPEED that has the values "fast",
"slow" and "indefinite". The value of this flag is kept for the whole call duration, once it has been set to
"fast". This choice relates to the assumption that a prediction is possible on the MS speed. Whenever
the MS moves into another cell and was not recognised "fast" at this occasion, or at a precedent
occasion, the MS_SPEED is reset to "indefinite".
The time experienced in a serving lower or indoor layer cell is kept in a counter C_DWELL (in SACCH
multiframes).
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
39/110
When a handover cause "power budget" is triggered, and the preceding cell was already a lower layer
cell (Respectively an indoor layer cell), this time is compared to a threshold MIN_CONNECT_TIME.
If it is found smaller than the threshold, this indicates that the MS has crossed the serving lower layer
cell (Respectively the serving indoor layer cell), in less than MIN_CONNECT_TIME seconds. In this
case , the MS is considered to be moving fast and the handover is directed towards the upper layer
preferentially.
If it is found bigger than the threshold, this indicates that the MS has not yet been recognised as fast
and the handover is directed towards the neighbour lower layer cell (Respectively the neighbour indoor
layer cell).
The handover cause power budget is used because it is assumed that in any cell environment this
cause will indicate that the MS is leaving the "better cell" zone of the serving cell, and not because of
interference, shadowing, or street corner effect.
The MS speed discrimination can only happen when the preceding cell is already a lower layer cell
(Respectively indoor layer cell) this ensures that the MS has entered the cell at its edge and not at an
arbitrary position inside the cell. This would be the case after call setup, or after a handover from an
umbrella cell.
Because the measured dwell time in the serving lower or indoor layer cell is taken between two points
located at the edge of the cell, the time interval can be related to the MS speed, assuming that the
main road on which fast moving mobiles are, is known beforehand.
The MIN_CONNECT_TIME shall be set to the value necessary for a fast moving car (mean speed v
about 40 km/h) necessary to travel along the cell on the main road.
If there is no information available about a privileged direction of fast MS, then the
Cell_ Diameter
where v represents the average
MIN_CONNECT_TIME shall be set to the value 2x
v
speed of fast moving mobiles.
The speed discrimination function can be enabled/disabled on a per cell basis, using a flag :
EN_SPEED_DISC.
If EN_SPEED_DISC is set to DISABLE, then the dwell time in a serving lower or indoor layer cell is not
used to determine if an MS is fast. Nevertheless, when the MS is on the upper layer, the dwell time in
the neighbour lower and indoor layer cells is used to decide a handover to the lower layer or to the
indoor layer cell, after a fixed period of time. The same behaviour applies if the MS is on the lower
layer: the dwell time in the serving lower layer cell is used to decide a handover to the indoor layer after
a fixed period of time. Table 12 shows which cells is used for the estimation of the MS speed as a
function of the serving cell layer.
Layer of the serving cells
Upper layer
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
40/110
= indefinite
= indefinite
By default, the flag EN_SPEED_DISC is set to disable for indoor layer cells.
### Case the serving cell is a lower layer cell (CELL_LAYER_TYPE = lower)
After call set-up or inter-cell handover
C_DWELL = 0.
After an intra-cell handover, C_DWELL is kept unchanged.
After call set-up or external handover
PREC_LAYER_TYPE
MS_SPEED
ED
EVOLIUM
04
= indefinite
= indefinite
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
41/110
= indefinite
= indefinite
Remarks :
For phase 1 MS, or when EN_SPEED_DISC = DISABLE in the umbrella cell, the initialisation of
C_DWELL(n) is done in such way that they will make a handover to the lower or indoor layer, after
L_MIN_DWELL_TIME seconds, provided they are under the coverage area of a lower or indoor layer
cell.
This will give an efficient way to reduce the load of the umbrella cell, caused by a large proportion of
Phase 1 MS, which will camp on this cell, because it has the best received level.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
42/110
For phase 2 MS and when EN_SPEED_DISC = ENABLE in the umbrella cell, the mobiles will have to
receive sufficient level from a lower or indoor layer cell during MIN_DWELL_TIME seconds before
leaving the upper layer for the lower or indoor layer. The variable MIN_DWELL_TIME is modified
according to the traffic load in the umbrella cell in order to enable the slow mobiles to leave more easily
a loaded umbrella cell (see 3.1.3.).
The "leaky bucket" mechanism on counter C_DWELL(n) allows to do with the statistical shadowing
affecting raw level measurements : if exactly 50% of the measurements are strictly above the
L_RXLEV_CPT_HO(0,n) threshold, the value of C_DWELL(n) grows, otherwise it stays at 0.
The value for the threshold L_RXLEV_CPT_HO(0,n) should be equal to the measured or planned
mean signal level at the border of the lower or indoor layer cells.
The counters C_DWELL(n) only work for neighbour cells, which belong to the lower layer or to the
indoor layer. The counter C_DWELL only work for the serving cell which belongs to the lower layer or
to the indoor layer. In other words, C_DWELL is never used for a serving cell in the upper layer.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
43/110
H_LOAD_OBJ
L_LOAD_OBJ
L_MIN_DWELL_TIME
DWELL_TIME_STEP
H_MIN_DWELL_TIME
Figure 14: Traffic regulation with MIN_DWELL_TIME modified according to the traffic load
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
44/110
3.2
Handover preparation
3.2.1
General
3.2.1.1
HO preparation configuration
At BSS initialisation, the parameters of handover preparation (see control flows of SADT diagrams in
section 2.3.6) are contained in the BSC database (for further details on BSS initialisation, see [ 26]).
Concerning the BSS reconfiguration, all the handover preparation parameters can be modified at OMC
side and then provided to the concerned BSS.
For both initialisation and reconfiguration, the algorithms are configured in the BTS by the BSC with the
message PREPROCESS CONFIGURE (see message description [ 23]). This message is sent on the
Abis radio signalling link (see [ 39]) on a TRX basis.
Note : In case of TCU restart, the message is sent to the BTS (i.e. to the TRX(s) connected to the
corresponding TCU).
3.2.1.2
Enabling
The enabling may result from :
- the establishment of a new connection,
- an intracell handover,
- an intercell handover,
- an handover request from RAM.
So, the specifications are the following ones :
- the BSC enables the algorithms upon receipt of the ESTABLISH INDICATION message from the
BTS. During an SDCCH connection, the BSC filters internally the handover alarms for a given number
of MEASUREMENT RESULT messages (defined by the parameter SDCCH_COUNTER, for further
details refer to [ 20]).
For further details on the call establishment and handover protocol refer [ 21], [ 23], and [ 24].
Disabling
- the BSC disables the algorithms whenever it initiates a channel release on the radio interface.
For further details on the call release procedure, refer to [ 10].
3.2.1.3 HO preparation function
The handover preparation function is completely handled by the BSC. The input parameters of this
function are provided by the Active channel preprocessing function every SACCH multiframe (refer to [
34]), and by the RAM entity (See [ 19]).
The following sections describe the general behaviour of the handover preparation function with its two
processes :
- HO detection : see section 3.2.2,
- HO candidate cells list evaluation : see section 3.2.3.
Handover detection
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
45/110
An emergency, better conditions, and channel adaptation handover alarm can be detected every
SACCH multiframe upon reception of the averaged measurements for handover detection. A resource
management handover is detected as soon as the message Start HO is received from RAM, and
concerns the current MS.
Handover candidate cells list evaluation
Once a handover alarm is detected, the HO detection process sends to the HO candidate cell
evaluation process the list of the MS neighbouring cells with for each of them one of the handover
causes which have been verified. It is an internal BSC action (implementation dependent).
The handover candidate cells list evaluation builds a cells list which is, according to the case and the
value of the timer T_FILTER, sent or not to HOM (see 3.2.4.). The specific management of Cause 28
is explained in Section 3.2.4.1.3. Within the list of candidate cell, the message sent to HOM also
contains the HO cause, the zone indication for concentric cells, and the new codec type for Cause 29.
In order to have an overview of the HOP entity, Figure 15 gives an SDL diagram of the HO preparation
function. However, in case of discrepancy between this diagram and the text of the document, the text
takes precedence over the diagram.
Note : the event "HO parameters change" corresponds to a on-line reconfiguration (managed by the
network operator) of the handover parameters used for HO detection and HO candidate cell
evaluation.
Document produced by GEODE <VERILOG (C)>
DESCRIPTION: PCHO
Page: 1
Partition 1/1
1.5
PROCESS PCHO/Handover_preparation/Mode_B/BSC
HO threshold
comparison
HO candidate
cell evaluation
idle channel
activate HO
preparation
init T FILTER
03-Feb-1995
active channel
HO
parameters
change
active channel
wait T FILTER
deactivate
HO
preparation
preproc meas
for HO
HO threshold
comparison
idle channel
HO
parameters
change
Wait T FILTER
T FILTER
expiry
active channel
deactivate
HO
preparation
preproc meas
for HO
HO threshold
comparison
idle channel
condition
occurs?
active channel
condition
occurs?
(Yes)
(No)
(Yes)
(No)
Wait T FILTER
HO candidate
cell
evaluation
candidate cells ,
HOcause TO
HO execution
trigger
T FILTER
HO candidate
cell
evaluation
Candidate cell
list changes?'
active channel
(No)
(Yes)
'restart
T FILTER'
candidate cells ,
HOcause TO
HO execution
restart
T FILTER
Wait T FILTER
Wait T FILTER
Wait T FILTER
Figure 15: SDL diagram - HO preparation/BSC.- partition 1/1. The specific alarm management for
Causes 28 , 29 and 30 are not described in the figure.
3.2.2
ED
EVOLIUM
Handover detection
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
46/110
When dealing with emergency, better conditions and channel adaptation handovers, the HO detection
process is also called HO threshold comparison. Threshold comparisons are performed for every new
set of average values AV_xxx_HO (i.e. every SACCH multiframe period) to detect possible need for
handover. The detection of a handover cause can be enabled/disabled by flags. For each possible
handover cause a flag is foreseen except for Causes 10 and 11 (See Section 2.3.5). These two latter
causes are automatically enabled in a concentric cell.
For resource management handover Cause 29 and 30, the HO detection process consists in checking
if a message Start HO concerning the current call is received from RAM. The flag that allows to
enable or disable Cause 29 and 30 are controlled by RAM (causes 29 and 30) and the transcoder
(cause 29 only).
Accordingly, HO alarms are sent to initiate the candidate cell evaluation function when a threshold
condition occurs or an appropriate message is received from RAM. After each intercell handover
alarm, the raw list of candidate cells and the preferred target cell layer are indicated to the handover
candidate evaluation process.
3.2.2.1 Handover causes
Twenty six different causes can lead the ALCATEL handover algorithm to detect a need for handover.
These causes are identified with a number that is used for performance measurement counters (See
Table 13).
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
47/110
Handover causes
Reference
Too low level on the uplink, inner zone (inner to outer zone handover, concentric or
multiband cell)
10
Too low level on the downlink, inner zone (inner to outer zone handover, concentric or
multiband cell)
11
Power budget
12
Too high level on the uplink and the downlink, outer zone (out. to in. zone hand.,
concentric or multiband cell)
13
14
15
16
17
18
20
21
22
Traffic HO
23
General capture HO
24
26
27
28
TFO handover
29
30
31
Table 13: Handover causes
3.2.2.1.1
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
48/110
and
(HO-18)
to
(HO-26)
are
checked
only
if
and
and
and
(HO-1)
Note : This handover cause can also be triggered in case of repetitive intracell handover, see section
3.2.2.1.1.2
Cause 3
CAUSE = 3 (too low level on the uplink)
AV_RXQUAL_UL_HO <= L_RXQUAL_UL_H + OFFSET_RXQUAL_FH
AV_RXLEV_UL_HO < L_RXLEV_UL_H
MS_TXPWR = min(P, MS_TXPWR_MAX)
EN_RXLEV_UL = ENABLE
and
and
and
(HO-2)
In (HO-1) and (HO-2), MS_TXPWR is the last MS_TXPWR_CONF value reported by the BTS in the
message MEASUREMENT RESULT or PREPROCESSED MEASUREMENT RESULT (refer to [ 34]).
Cause 4
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
49/110
and
and
and
(HO-3)
Note : This handover cause can also be triggered in case of repetitive intracell handover, see section
3.2.2.1.1.2
Cause 5
CAUSE = 5 (too low level on the downlink)
AV_RXQUAL_DL_HO <= L_RXQUAL_DL_H + OFFSET_RXQUAL_FH
(HO-4)
and
AV_RXLEV_DL_HO < L_RXLEV_DL_H
and
BS_TXPWR = BS_TXPWR_MAX
and
EN_RXLEV_DL = ENABLE
Unlike the previous causes, the five following handover causes do not take into account the increase of
the MS or the BS power to its maximum.
Cause 6
CAUSE = 6 (too long MS-BS distance)
AV_RANGE_HO > U_TIME_ADVANCE
EN_DIST_HO = ENABLE
and
(HO-5)
Cause 22
Cause 22 is only checked if the Cell range of the cell is set to extended_outer.
CAUSE = 22 (too short MS-BS distance)
AV_RANGE_HO L_TIME_ADVANCE
(HO-23)
- L_TIME_ADVANCE : Minimum distance for handover from the extended outer zone
The three following equations are only used in microcells, i.e. the corresponding flags are set to
ENABLE if the cell profile is microcell (or CELL_DIMENSION_TYPE = micro) and to DISABLE for all
other cell profiles.
Cause 7
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
50/110
and
(HO-20)
The cause 7 is managed with an internal BSC variable which counts the number of bad SACCH
frames consecutively received :
- this counter is incremented every time a MEASUREMENT RESULT or PREPROCESSED
MEASUREMENT RESULT message with BFI = 1(Bad Frame Indication) is received,
- this counter is reset every time a MEASUREMENT RESULT or PREPROCESSED MEASUREMENT
RESULT message with BFI = 0 is received.
The format of these two messages is given in [ 34].
Cause 17
CAUSE = 17 (Too low level on the uplink in a microcell compared to a high threshold)
AV_RXLEV_UL_MCHO(i) ### U_RXLEV_UL_MCHO
18)
and
and
(HO-
(HO-
3.2.2.1.1.2
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
51/110
The repetition may be inhibited by setting the O&M flag EN_INTRACELL_REPEATED to DISABLE.
Concerning the case ii, the condition no previous intracell handover for this connection failed is given
by the function handling the call in the BSC. This condition is used to avoid repetitive intracell
handovers. If an intracell handover for a given connection was not successful (handover failure, no free
timeslot, etc...) it is not repeated when the next handover alarm occurs.
If an intracell handover is still required for this connection, the handover is turned into an intercell
handover as described above. Then for the same call in the new cell, intracell handover is allowed
again.
3.2.2.1.1.3
Cause 12
Cause 12 is checked over all the neighbour cells belonging to the same layer . It means that it is
checked between cells whose CELL_LAYER_TYPE is single or upper, between cells whose
CELL_LAYER_TYPE is lower, and between cells whose CELL_LAYER_TYPE is indoor.
In addition to the condition on the cell layer type, the cell frequency band condition for checking Cause
12 in Eq. (HO-6) is as follows whether or not the MS is in the inner zone of a multiband cell:
Case the MS is not in the inner zone of a multiband cell
If the flag EN_MULTIBAND_PBGT_HO is set to disable, Cause 12 must not be checked
between cells which use different frequency band (i.e cells having different
CELL_BAND_TYPE).
If the flag EN_MULTIBAND_PBGT_HO is set to enable, Cause 12 will be checked over all
the neighbours cells without any cell frequency band restriction.
If the flag EN_MULTIBAND_PBGT_HO is set to enable, Cause 12 will be checked over all
the neighbours cells without any cell frequency band restriction.
In addition, in order not to cancel an on-going location procedure, Cause 12 for handovers from TCH to
TCH is not checked when a location procedure is on-going for the call.
Cause 12 for handover from TCH to TCH and for directed retry on handover alarms from SDCCH to
TCH is:
CAUSE = 12 (Power budget)
and
and
If EN_TRAFFIC_HO(0,n)=ENABLE
(HO-6)
then PBGT(n) > HO_MARGIN(0,n) + OFFSET_HO_MARGIN_INNER
+ max(0, DELTA_HO_MARGIN(0,n)) (n=1...BTSnum)
else PBGT(n) > HO_MARGIN(0,n) + OFFSET_HO_MARGIN_INNER
AV_RXLEV_PBGT_HO RXLEV_LIMIT_PBGT_HO
EN_PBGT_HO = ENABLE
with PBGT(n) =
AV_RXLEV_NCELL(n) - AV_RXLEV_PBGT_HO
- (BS_TXPWR_MAX - AV_BS_TXPWR_HO)
- (MS_TXPWR_MAX(n) - MS_TXPWR_MAX)
(HO-7)
- PING_PONG_MARGIN(n,call_ref)
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
52/110
Note 1: Since a monoband MS can only receive measurements from the target cells having the same
frequency band as the serving cell, the case the flag EN_MULTIBAND_PBGT_HO is set to
enable and the MS is monoband is equivalent to check Cause 12 over all the target cells
having the same frequency band as the serving cell.
Note 2: In case the flag EN_MULTIBAND_PBGT_HO is set to enable and the MS is in the inner zone
of a multiband cell, the offset OFFSET_HO_MARGIN_INNER is kept unchanged whatever the
target cell frequency band is.
Note 3: In (HO-7), OFFSET_HO_MARGIN_INNER is only used in the inner zone of a concentric or
multiband cell.
In addition to the same layer condition, the cell frequency band condition for checking Cause 12 in Eq.
(HO-6bis) is:
If the flag EN_MULTIBAND_PBGT_HO is set to disable, Cause 12 must not be checked
between cells which use different frequency band (i.e. cells having different
CELL_BAND_TYPE).
If the flag EN_MULTIBAND_PBGT_HO is set to enable, Cause 12 will be checked over all
the neighbours cells without any cell frequency band restriction.
In addition, in order not to cancel an on-going location procedure, Cause 12 for handovers from
SDCCH to SDCCH is not checked when a location procedure is on-going for the call.
Cause 12 for handover from SDCCH to SDCCH is:
CAUSE = 12 (Power budget)
and
and
(HO-6bis)
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
53/110
- DELTA_HO_MARGIN(0,n) is evaluated according to the traffic situation of the serving cell and the
neighbour cell n (Traffic_load(n), refer to [ 30]) in the following way.
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
where DELTA_DEC_HO_margin allows the cause 23 (traffic handover) detection
when the traffic in the serving cell is high and is low in the cell n.
DELTA_INC_HO_margin allows to penalise the cause 12 detection when the traffic
in the serving cell is low and is high in the cell n.
Note 1: In the case of concentric or multiband cells, if the channel is in the inner zone (ZONE_TYPE
= INNER), BS_TXPWR_MAX and MS_TXPWR_MAX in equation (HO-7) must be replaced
by BS_TXPWR_MAX_INNER and MS_TXPWR_MAX_INNER respectively.
If the channel is in the outer zone (ZONE_TYPE = OUTER), the formulation of equation (HO7) is not changed.
Note 2: The value of PBGT(n) is calculated every SACCH period for each neighbour cell n whose
measures are kept in the book-keeping list.
Note 3: If no traffic load evaluation is available in an external cell n, the Traffic_Load(n) parameter is
set to indefinite.
The four following equations are only checked for handover from TCH to TCH and for directed retry on
handover alarms from SDCCH to TCH. For handover from SDCCH to SDCCH, they are not checked.
Cause 14
Cause 14 is checked if and only if CELL_LAYER_TYPE = upper or lower (this rule is applied at the
OMC by disabling the flag EN_MCHO_NCELL when CELL_LAYER_TYPE is different from both upper
and lower).
The two following cases have to be considered depending on the cell layer of the serving cell.
Case the serving cell is in the upper layer (CELL_LAYER_TYPE(0) = upper)
If the MS is in the inner zone of a multiband cell, the cause 14 is checked over all the
neighbour cells with CELL_LAYER_TYPE(n) = lower or indoor except the ones with EN_BIBAND_MS(n)=DISABLE and CELL_BAND_TYPE(n)=CELL_BAND_TYPE(0).
If the MS is not in the inner zone of a multiband cell and the MS is in a cell with
CELL_BAND_TYPE(0)=PREFERRED_BAND, the cause 14 is checked over all the
neighbour cells with CELL_LAYER_TYPE(n) = lower or indoor except the ones with EN_BIBAND_MS(n)=DISABLE and CELL_BAND_TYPE(n)<>PREFERRED_BAND.
If the MS is not in the inner zone of a multiband cell and the MS is in a cell with
CELL_BAND_TYPE(0)<>PREFERRED_BAND, the cause 14 is checked over all the
neighbour cells with CELL_LAYER_TYPE(n) = lower or indoor.
If the MS is in the inner zone of a multiband cell, the cause 14 is checked over all the
neighbour cells with CELL_LAYER_TYPE(n) = indoor except the ones with EN_BIBAND_MS(n)=DISABLE and CELL_BAND_TYPE(n)=CELL_BAND_TYPE(0).
ED
EVOLIUM
If the MS is not in the inner zone of a multiband cell and the MS is in a cell with
CELL_BAND_TYPE(0)=PREFERRED_BAND, the cause 14 is checked over all the
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
54/110
neighbour cells with CELL_LAYER_TYPE(n) = indoor except the ones with EN_BIBAND_MS(n)=DISABLE and CELL_BAND_TYPE(n)<>PREFERRED_BAND.
If the MS is not in the inner zone of a multiband cell and the MS is in a cell with
CELL_BAND_TYPE(0)<>PREFERRED_BAND, the cause 14 is checked over all the
neighbour cells with CELL_LAYER_TYPE(n) = indoor.
In order to limit the ping-pong effect, Cause 14 is not checked while the timer T_INHIBIT_CPT is
running (See section 3.2.4). In addition, in order not to cancel an on-going location procedure, Cause
14 for handover from TCH to TCH is not checked when a location procedure is on-going for the call.
CAUSE = 14 (high level in neighbour lower or indoor layer cell for slow mobile)
(HO-21)
CELL_LAYER_TYPE(0) = upper
AV_RXLEV_NCELL(n) > L_RXLEV_CPT_HO(0,n)
MS_SPEED = slow
EN_MCHO_NCELL = ENABLE
and
and
and
n = (1...BTSnum)
Or
CELL_LAYER_TYPE(0) = lower
AV_RXLEV_NCELL(n) > L_RXLEV_CPT_HO(0,n)
MS_SPEED <> fast
EN_MCHO_NCELL = ENABLE
and
and
and
n = (1...BTSnum)
Note 1: In (HO-21), the condition on the MS_SPEED variable depends on the cell layer type. The
reason for this is that the MS_SPEED variable is by default set to indefinite. Then, the
MS_SPEED can changed from indefinite to slow only when the MS is in a upper layer cell. To
give an ease access to the MS in the indoor layer, it is therefore necessary to allow Cause 14
when MS_SPEED = indefinite in the lower layer.
Cause 21
Cause 21 is checked if and only if CELL_BAND_TYPE is different from the parameter
PREFERRED_BAND (This checking is performed at the BSC). It is checked for all neighbour cells n in
the preferred band (i.e. CELL_BAND_TYPE(n) = PREFERRED_BAND). If the parameter
PREFERRED_BAND is set to none, the equation is never checked.
In order to limit the ping-pong effect, Cause 21 is not checked while the timer T_INHIBIT_CPT is
running (See section 3.2.4). In addition, in order not to cancel an on-going location procedure, Cause
21 for handover from TCH to TCH is not checked when a location procedure is on-going for the call.
CAUSE = 21 (high level in neighbour cell in the preferred band)
and
and
and
(HO -22)
Traffic_load(0) = MULTIBAND_TRAFFIC_CONDITION
Traffic_load(n) <> high
AV_RXLEV_NCELL(n) > L_RXLEV_CPT_HO(0,n) + max(0,[MS_TXPWR_MAX(n)-P])
EN_PREFERRED_BAND_HO = ENABLE
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
55/110
NOT_LOW:
HIGH:
If the flag EN_MULTIBAND_PBGT_HO is set to enable, Cause 23 will be checked over all
the neighbour cells without any cell frequency band restriction.
If the flag EN_MULTIBAND_PBGT_HO is set to enable, Cause 23 will be checked over all
the neighbour cells without any cell frequency band restriction.
In addition, in order not to cancel an on-going location procedure, Cause 23 for handover from TCH to
TCH is not checked when a location procedure is on-going for the call.
CAUSE = 23 (Traffic HO)
(HO -24)
and
and
(n=1...BTSnum)
EN_TRAFFIC_HO(0,n) = ENABLE
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
56/110
In order to limit the ping-pong effect, Cause 24 is not checked while the timer T_INHIBIT_CPT is
running (See section 3.2.4). In addition, in order not to cancel an on-going location procedure, Cause
24 for handover from TCH to TCH is not checked when a location procedure is on-going for the call.
CAUSE = 24 (General capture HO)
(HO -25)
Traffic_load(0) = CAPTURE_TRAFFIC_CONDITION
Traffic_load(n) <> high
AV_RXLEV_NCELL(n) > L_RXLEV_CPT_HO(0,n) + max(0,[MS_TXPWR_MAX(n)-P])
EN_GENERAL_CAPTURE_HO = ENABLE
And
And
And
where
- FREElevel_DR(n) is the minimum threshold of free TCHs in the neighbour cell n for forced directed
retry and fast traffic handover.
- t(n) is the absolute number of free TCHs in the neighbour cell n.
Note 1: The threshold L_RXLEV_NCELL_DR(n) is the observed level from the neighbour cell n at the
border of the area where fast traffic handovers are enabled. This threshold fixes the size of
the overlapping area where fast traffic handovers can be performed. It should be greater than
RXLEVmin(n).
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
57/110
Note 2: For external cells, t(n) is fixed to the arbitrary value t(n) = 255. Therefore, setting
FREElevel_DR(n) to 255 for an external cell inhibits outgoing external fast traffic handover
towards this cell. Setting FREElevel_DR(n) to any other value will allow outgoing external fast
traffic handover towards this cell.
Note 3: If the BTS has dual rate capability, t(n) = absolute number of free Dual Rate TCH
Note 4: The flag EN_CAUSE_28 is not an OMC flag but an HOP flag. Its enabling and disabling is
explained in Section 3.2.4.
3.2.2.1.2 Intracell handover causes
The following general remarks need to be taken into account when reading this section.
The 3GPP coding of quality is contra-intuitive, since the value 0 codes for the best quality and 7 for the
worst. Thus, the comparison between two quality values must be understood in the opposite way in
terms of quality.
In order to take into account the frequency hopping in the RXQUAL evaluation the variable
OFFSET_RXQUAL_FH is introduced (for more information refer to [ 30]).
If on the corresponding channel,
Frequency hopping is applied
then OFFSET_RXQUAL_FH = Offset_Hopping_HO
otherwise OFFSET_RXQUAL_FH = 0
Offset_Hopping_HO is a parameter defined on a per cell basis.
The case where L_RXQUAL_XX_H_XXX + OFFSET_RXQUAL_FH > 7 corresponds in the equations
to L_RXQUAL_XX_H_XXX + OFFSET_RXQUAL_FH = 7.
3.2.2.1.2.1
Cause 15
Two set of parameters are defined to control Cause 15 whether the current call is AMR or not:
If the current call is not an AMR call,
EN_CAUSE_15 = EN_INTRA_UL,
THR_RXQUAL_CAUSE_15 = L_RXQUAL_UL_H.
If the current call is an AMR call,
EN_CAUSE_15 = EN_INTRA_UL_AMR,
THR_RXQUAL_CAUSE_15 = L_RXQUAL_UL_H_AMR.
CAUSE = 15 (too high interference level on the uplink)
AV_RXQUAL_UL_HO > THR_RXQUAL_CAUSE_15 + OFFSET_RXQUAL_FH
AV_RXLEV_UL_HO > RXLEV_UL_IH
EN_CAUSE_15 = ENABLE
( no previous intracell handover for this connection failed
or EN_INTRACELL_REPEATED = ENABLE ).
and
and
and
(HO-8)
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
58/110
EN_CAUSE_16 = EN_INTRA_UL_AMR,
THR_RXQUAL_CAUSE_16 = L_RXQUAL_DL_H_AMR.
CAUSE = 16 (too high interference level on the downlink)
AV_RXQUAL_DL_HO > THR_RXQUAL_CAUSE_16 + OFFSET_RXQUAL_FH (HO-9)
AV_RXLEV_DL_HO > RXLEV_DL_IH
EN_CAUSE_16 = ENABLE
(no previous intracell handover for this connection failed
or EN_INTRACELL_REPEATED = ENABLE )
and
and
and
A
and
(HO-15)
Cause 11
CAUSE = 11 (too low level on the downlink, inner zone)
AV_RXLEV_DL_HO < RXLEV_DL_ZONE
BS_TXPWR = BS_TXPWR_MAX_INNER
and
3.2.2.1.2.2
(HO-16)
Cause 13
Cause 13 is specific to concentric or multiband cell configurations. It is checked only if
CELL_PARTITION_TYPE = CONCENTRIC and the active channel is a TCH.
Furthermore, it is only valid for handover from the outer zone to the inner zone of the concentric or
multiband cell. Thus, the following condition is checked only if ZONE_TYPE = outer (it means that the
channel is in the outer zone partition).
If the FREQUENCY_RANGE = PGSM-DCS1800 or EGSM-DCS1800 (the MS is in a multiband cell),
the cause is checked only if the MS is biband. Furthermore, if the MS is in a EGSM-DCS1800
multiband cell, the EGSM_ALLOC_STRATEGY is set to Different behaviour for E-GSM capable MS,
there is only EGSM TRXs in the inner zone, and the MS is biband but does not support the E-GSM
band, then the cause is not checked.
The following cause must be checked for all the neighbour cells in the same layer and the same
frequency band as the serving cell.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
59/110
If the load balance between the inner and outer zones is allowed, i.e. EN_LOAD_BALANCE = enable,
Cause 13 is only checked if the flag EN_CAUSE_13 is set to enable. This later flag is sent to HOP by
RAM in the TCH usage information message. EN_CAUSE_13 is set to enable by RAM when the
inner zone is less loaded than the outer zone.
In addition, in order not to cancel an on-going location procedure, Cause 13 is not checked when a
location procedure is on-going for the call.
CAUSE = 13 (Too high level on the uplink and the downlink, outer zone)
AV_RXLEV_UL_HO > RXLEV_UL_ZONE + ZONE_HO_HYST_UL +
(MS_TXPWR - MS_TXPWR_MAX_INNER)
and
and
and
and
+ PING_PONG_MARGIN(0, call_ref)
AV_RXLEV_DL_HO > RXLEV_DL_ZONE + ZONE_HO_HYST_DL +
BS_TXPWR - BS_TXPWR_MAX_INNER
+ PING_PONG_MARGIN(0, call_ref)
AV_RXLEV_NCELL_BIS(n) NEIGHBOUR_RXLEV(0,n)
EN_CAUSE_13 = enable
EN_BETTER_ZONE_HO = ENABLE
ZONE_TYPE=
OUTER ZONE
RXLEV_DL_ZONE
RXLEV_UL_ZONE
ZONE_HO_HYST_UL
ZONE_HO_HYST_DL
MS_TXPWR_MAX_IN
NER
BS_TXPWR_MAX_IN
NER :
AV_RXLEV_DL_HO
AV_RXLEV_UL_HO
MS_TXPWR
BS_TXPWR
NEIGHBOUR_RXLEV
(0,n) :
PING_PONG_MARGI
N(0,call_ref)
ED
EVOLIUM
(HO-17)
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
60/110
the immediately precedent zone on which the call has been is the inner zone
of the serving cell, the last handover was not an external intracell handover
(case which can occur in the DCS inner zone of a multiband cell in case of
emergency handover see 3.2.2.3), less than T_HCP seconds have elapsed
since the last handover.
In this case PING_PONG_MARGIN(0,call_ref) = PING_PONG_HCP.
If the call was not precedently on the serving cells inner zone (case of
intercell or intrazone handover), or if the timer T_HCP has expired, then
PING_PONG_MARGIN(0,call_ref) = 0
Note:
1) For the computation of AV_RXLEV_NCELL_BIS(n) refer to [ 34].
2) The encoding of MS power levels depends on the frequency band. In multiband cells, the BSC shall
then compute the difference (MS_TXPWR MS_TXPWR_MAX_INNER) considering that
MS_TXPWR is encoded with the encoding scheme of the outer zone, whereas
MS_TXPWR_MAX_INNER is encoded with the encoding scheme of the inner zone.
3.2.2.1.2.3
Cause 26
The triggering of Cause 26 depends on the set of parameters and the triggering of Causes 15 and 16
for AMR calls. When the intracell HO Causes 15 or 16 are allowed for an AMR call in the serving cell,
i.e. EN_INTRA_UL_AMR = enable or EN_INTRA_DL_AMR = enable, Cause 26 shall be checked only
if a previous intracell HO Cause 15 or 16 has already been triggered for this call in the serving cell.
This condition allows to perform one intracell HO before triggering a HR-to-FR channel adaptation.
The check of Cause 26 is always allowed when the intracell HO Causes 15 and 16 are both set to
disable, i.e. EN_INTRA_UL_AMR = disable and EN_INTRA_DL_AMR = disable.
Cause 26 is only checked if the current channel is half rate, and corresponds to an AMR call.
Furthermore, the current channel has to be dual rate (DR) and changes allowed (CA) for checking
Cause 26.
According to the load of the serving cell, the variables THR_RXQUAL_CA and OFFSET_CA are set as
follows:
If LOAD_SV3(0) = false
THR_RXQUAL_CA = THR_RXQUAL_CA_NORMAL
OFFSET_CA = OFFSET_CA_NORMAL
If LOAD_SV3(0) = true
THR_RXQUAL_CA = THR_RXQUAL_CA_HIGH
OFFSET_CA = OFFSET_CA_HIGH
Cause 26 only applies to handovers from TCH to TCH.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
61/110
(HO-27)
+ OFFSET_CA +
OFFSET_RXQUAL_FH
and
AV_RXLEV_UL_HO > RXLEV_UL_IH
}
or
{
OFFSET_RXQUAL_FH
and
AV_RXLEV_DL_HO > RXLEV_DL_IH
}
}
and
and {
EN_AMR_CA = enable
(a previous intracell HO Cause 15 or 16 has been raised for this call in the serving cell)
or
(EN_INTRA_UL_AMR = disable and EN_INTRA_DL_AMR = disable)
}
Note 1: The variables THR_RXQUAL_CA and OFFSET_CA are specific to Causes 26 and 27 in
HOP. The relevant parameters that have to be set at the OMC are
THR_RXQUAL_CA_NORMAL, THR_RXQUAL_CA_HIGH, OFFSET_CA_NORMAL, and
OFFSET_CA_HIGH.
Note 2: Only the speech channels are allowed for Cause 26.
Cause 27
Cause 27 is only checked if the current channel is full rate and corresponds to an AMR call.
Furthermore, the current channel has to be dual rate (DR) and changes allowed (CA) for checking
Cause 27.
In addition, in order not to cancel an on-going location procedure, Cause 27 is not checked when a
location procedure is on-going for the call.
According to the load of the serving cell, the variable THR_RXQUAL_CA is set as follows:
If LOAD_SV3(0) = false
THR_RXQUAL_CA = THR_RXQUAL_CA_NORMAL,
If LOAD_SV3(0) = true
THR_RXQUAL_CA = THR_RXQUAL_CA_HIGH
Cause 27 only applies to handovers from TCH to TCH.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
62/110
and
and
and
and
and
(HO-28)
Note 1: The variable THR_RXQUAL_CA is specific to Causes 26 and 27 in HOP. The relevant
parameters that have to be set at the OMC are THR_RXQUAL_CA_NORMAL,
THR_RXQUAL_CA_HIGH.
Note 2: Only the speech channels are allowed for Cause 27.
The way Cause 27 interacts with Cause 26 is illustrated in Figure 16.
Figure 16: Thresholds for channel adaptation. The frequency hopping offset is not shown in the figure.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
63/110
RXQUAL
0
1
Level
intercell HO
Power Control
(HO-2,HO-4)
4
5
L_RXQUAL_XX_H
6
Intracell HO
Quality intercell HO
(HO-1,HO-3)
(HO-8,HO-9)
7
0
10
20
L_RXLEV_XX_H
30
40
50
60
RXLEV
L_RXLEV_XX_IH
Figure 17: State diagram for handover detection (signal level - signal quality)
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
64/110
Figure 18 represents the triggering areas of PBGT and traffic handovers according to the traffic load in
the serving cell and in the neighbour cell.
Figure 18: PBGT(n) according to the traffic load in the serving cell and the neighbour cell.
3.2.2.1.3
Cause 31
The cause 31 is checked when there a 3G cell whose averaged Ec/No given by the radio
measurement process is greater or equal to a predefined threshold.
CAUSE = 31 (2G-3G handover Ec/No)
AV_ECNO(n) THR_ECNO
(HO-31)
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
65/110
3.2.2.2
The handover causes are checked with the priority order defined in Table 14. The order 1 corresponds
to the highest priority whereas the order 19 to the lowest. The resource management handovers 29 ,
30 and 31 will have no priority since they are checked with a different trigger than the other handover
causes.
Order
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
HO family
HO cause
Emergency HO
Consecutive bad SACCH frames
Emergency HO
Level uplink microcell - high threshold
Emergency HO
Level downlink microcell - high threshold
Emergency HO
Too low quality Uplink
Emergency HO
Too low quality Downlink
Emergency HO
Too low level Uplink
Emergency HO
Too low level Downlink
Emergency HO
Too long MS-BS distance
Emergency HO
Too short MS-BS distance
Emergency HO
Inner zone too low level Uplink
Emergency HO
Inner zone too low level Downlink
Channel adapt. HO
HR-to-FR channel adaptation due to bad quality
Emergency HO
Too high interference intracell Uplink
Emergency HO
Too high interference intracell Downlink
Better conditions HO
High level in neighbour cell in the preferred band
Better conditions HO
High level in neighbour lower layer cell for slow MS
Better conditions HO
General capture handover
Better conditions HO
Power budget
Better conditions HO
Traffic handover
Better conditions HO
Outer zone level Uplink & Downlink
Channel adaptation
FR-to-HR channel adaptation due to good quality
Better conditions HO
Forced Directed Retry
Better conditions HO
Fast traffic handover
Table 14: Priority order of alarms for Handover.
HO cause
reference
Cause = 7
Cause = 17
Cause = 18
Cause = 2
Cause = 4
Cause = 3
Cause = 5
Cause = 6
Cause = 22
Cause = 10
Cause = 11
Cause = 26
Cause = 15
Cause = 16
Cause = 21
Cause = 14
Cause = 24
Cause = 12
Cause = 23
Cause = 13
Cause = 27
Cause = 20
Cause = 28
The better condition causes 21, 14, 24, 12 and 23 have the same priority. For each cell in the list of
possible candidate cell is associated a cause.
If a cell is in the candidate cell list because of 2 different causes, only the one with the highest priority
in the ordered list (cause 21, cause 14, cause 24, cause 12 and cause 23) in which cause 21 has the
highest priority is kept.
3.2.2.3 Indication of raw cell list and preferred layer
This section is skipped for intracell handovers.
After an inter cell handover alarm has been detected, the candidate cell evaluation receives a raw cell
list with for each cell one of the handover causes which have been verified and the indication of the
preferred layer for the target cell.
### Case the serving CELL_LAYER_TYPE is single
When the serving CELL_LAYER_TYPE is single, the following rules are applied :
The raw cell list is :
for Better conditions intercell handover (Causes 12, 14, 20, 21, 23, 24, and 28) : the neighbour
cells which verify the cause,
for Emergency handover : all neighbour cells; and if the MS is in the DCS1800 inner zone of a
multiband cell, the serving cell must be added to the raw cell list with the MS zone indication
OUTER.
However, in both cases, if the serving cell is an extended-inner cell, the extended-outer cell must be
filtered from the raw cell list except in case of handover cause 6.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
66/110
If the serving cell is an extended-outer cell, the extended-inner cell must be filtered from the raw cell
list except in case of handover cause 22.
The indication of the preferred layer is PREF_LAYER = upper+single
PREF_LAYER = upper+single
### Case the serving CELL_LAYER_TYPE is lower or indoor
When the serving CELL_LAYER_TYPE is lower or indoor, the following rules are applied :
The cell raw list is calculated as :
- for better conditions intercell handover causes (causes 12, 14, 20, 21, 23 , 24, and 28)
the subset of neighbour cells which verify the handover causes.
If there is a cell in the list because of Cause 12, and MS_SPEED = fast, the cell raw list must
also contain the whole set of internal neighbour umbrella cells with information Traffic_load(n) =
low and CELL_LAYER_TYPE(n) = upper (they do not need to verify the HO cause).
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
67/110
If there is a cell in the list because of Cause 12 and MS_SPEED = fast then PREF_LAYER =
upper, else PREF_LAYER = none.
Table 15 and Table 16 resume the indications given to the candidate cell evaluation process when the
serving CELL_LAYER_TYPE = lower or indoor.
Indication
PREF_LAYER
none
for Better cell HO
Table 15: Indications to candidate evaluation for better conditions intercell handovers when the serving
CELL_LAYER_TYPE = lower or indoor.
Indication
Raw cell list
for Emergency HO
EN_RESCUE_UM =
EN_RESCUE_UM =
EN_RESCUE_UM =
ENABLE
DISABLE
indefinite
all neighbour cells (1)
all neighbour cells (1)
all neighbour cells (1)
except the umbrella cells except the umbrella cells
except the umbrella
which do not verify
which do not verify
cells which do not
AV_RXLEV_NCELL(n)> AV_RXLEV_NCELL(n)>
verify
OUTDOOR_UMB_LEV(0 OUTDOOR_UMB_LEV(0 AV_RXLEV_NCELL(n
,n).
,n).
)>OUTDOOR_UMB_L
EV(0,n).
upper + single
lower + indoor
none
PREF_LAYER
for Emergency HO
Table 16: indications to candidate evaluation for emergency handovers when the serving
CELL_LAYER_TYPE = lower or indoor.
(1): if the MS is in the DCS inner zone of a multiband cell, the serving cell must be added to the raw
cell list with the MS zone indication OUTER.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
68/110
3.2.3
The HO candidate evaluation process is run after all intercell handover alarms as shown in Figure 19.
In case of intra-cell handover alarm (HO causes 10, 11, 13, 15, 16, 26, 27,29 and 30), the candidate
cell evaluation process is skipped since the target cell is also the serving cell. For intracell handovers in
a concentric or multiband cell, the zone which the MS is currrently allocated to (either outer or inner
zone) is forwarded to RAM via HOM together with the serving cell. In this case, the MS zone indication
is not determined by the radio criterion presented in Cause 13 and Section 3.1.2.1.
HO Detection
Handover causes
2, 3, 4, 5, 6, 7,17,
18, 22, 28
Handover cause
20
Handover causes
12,14, 21, 23, 24
Handover causes
10, 11, 13, 15, 16, 26,
27, 29, 30
Ordering process for 2G-3G
HO based on the 3G cell
ranking criteria
Handover cause
31
Input parameters
The ordering process receives (refer to input flows described in section 2.3.6) :
- measurements of up to 32 neighbour cells (TCU internal indication) handled by the BSC cell bookkeeping function.
- the raw cell list of potential candidates to be ordered with for each of them one of the handover
causes which have been verified.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
69/110
- the preferred layer for the target cell indicated by the variable PREF_LAYER
- the cell configuration parameters which contains the variable CELL_BAND_TYPE.
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
70/110
}
Candidate cells which have the next lowest PRIORITY(0,n)
{
Candidate cells whose CELL_BAND_TYPE = serving CELL_BAND_TYPE
{
cell ordering according to cell evaluation function
}
Candidate cells whose CELL_BAND_TYPE <> serving CELL_BAND_TYPE
{
cell ordering according to cell evaluation function
}
}
.
.
.
}
Serving cell (MS zone indication = OUTER)
}
Ordering process for better conditions HO alarm (except Causes 20 and 28)
In case of better condition handover alarm except causes 20 and 28, the target cell list is built from the
cell
ordering
according
to
target
layer
and
the
priority
of
each
cells
(if
EN_PRIORITY_ORDERING=ENABLE) and from the cell evaluation function indicated by the flag
CELL_EV associated to the serving cell (see Sections 3.2.3.4 and 3.2.3.5).
The priority of each cells is defined by the parameter PRIORITY(0,n). The cell priority introduced here
shall not be confused with the cause priority of Section 3.2.2.2.
The ordering of the target cell list (from the higher priority to the lower one) is performed according to
the following scheme :
Candidate cells whose CELL_LAYER_TYPE = PREF_LAYER
{
Candidate cells which have the lowest PRIORITY(0,n)
{
cell ordering according to cell evaluation function
}
Candidate cells which have the next lowest PRIORITY(0,n)
{
cell ordering according to cell evaluation function
}
.
.
.
}
Candidate cells whose CELL_LAYER_TYPE <> PREF_LAYER
{
Candidate cells which have the lowest PRIORITY(0,n)
{
cell ordering according to cell evaluation function
}
Candidate cells which have the next lowest PRIORITY(0,n)
{
cell ordering according to cell evaluation function
}
.
.
.
}
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
71/110
Note : - if PREF_LAYER = none, only the second part of the scheme (i.e. candidate cells whose
CELL_LAYER_TYPE <> PREF_LAYER) is considered.
- if PREF_LAYER = upper+single, the condition for the first part of the scheme will be :
CELL_LAYER_TYPE = upper or CELL_LAYER_TYPE = single. The condition for the second
part will be CELL_LAYER_TYPE <> upper and CELL_LAYER_TYPE <> single.
- if PREF_LAYER = lower+indoor, the condition for the first part of the scheme will be :
CELL_LAYER_TYPE = lower or CELL_LAYER_TYPE = indoor. The condition for the second
part will be CELL_LAYER_TYPE <> lower and CELL_LAYER_TYPE <> indoor.
- if EN_PRIORITY_ORDERING=DISABLE, the priority(0,n) is not taken into account.
The flag CELL_EV is managed by the network operator on a per cell basis. It has two values, which
correspond to the two cell evaluation functions ORDER and GRADE (see Sections 3.2.3.4 and 3.2.3.5)
.
A filtering process can be applied to the target list before the ORDER or GRADE evaluation process in
case of emergency handovers. The filtering process, the ORDER or GRADE evaluation process are
not applied to the serving cell when it is in the target cell list. The serving cell is always at the end of the
target cell list.
After the cell evaluation processing, the list of candidate target cells with their cause is provided to
HOM. For Cause 28, the list of candidate cells is sent to the HOM only when the message Start HO
concerning the current call and Cause 28 has been received from RAM.
Output parameters
The ordering process (after the filtering process) should provide to the handover alarm management
described in Section 3.2.4 the list of candidate cells with their cause and with the serving cell at the end
of the list in case of emergency handover from the DCS inner zone of a multiband cell.
The HO causes together with the CELL_PARTITION_TYPE parameter shall be used by HOM (for
further details, see [ 28] and [ 30]) as described in Table 17:
Concentric
HO cause
###
15, 16
26, 27
29
30
10, 11, 13
Others
ED
EVOLIUM
04
Intracell handover
Intrazone or interzone
Select a channel in the handover
same cell
Select a channel in the
same cell
Intracell handover
Intracell handover
Change the speech
Change the speech
channel rate and select a
channel rate and select a
channel in the same cell
channel in the same cell
Intracell handover
Intracell handover
Select a new codec type
Select a new codec type
Intracell handover
Intracell handover
Move TCH from PS
Move TCH from PS
preference zone to CS
preference zone to CS
preference zone.
preference zone.
Not applicable
Interzone handover
Select a channel in the
other zone
Intercell handover
Intercell handover
Channel
allocation
is Channel
allocation
is
described in [ 28] and [ 30]. described in [ 28] and [ 30].
Table 17: Channel allocation strategy
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
72/110
(HO-13)
If cause =2, 4 or 7
If cause =3, 5, 17, 18, or 28
If cause =6 or 22
If no cell fulfils the condition and the serving cell does not belong to the target cell list, the target cell list
is empty and no further action is carried out.
If the target list is not empty, it is sent to the ORDER or GRADE evaluation process according to
CELL_EV.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
73/110
For emergency handover causes (plus Cause 28), HO_MARGIN_XX(0,n) has the following values:
HO_MARGIN_XX(0,n)=HO_MARGIN_QUAL(0,n)
If cause =2, 4 or 7
HO_MARGIN_XX(0,n)=HO_MARGIN_LEV(0,n)
If cause =3, 5, 17,18, or 28
HO_MARGIN_XX(0,n)=HO_MARGIN_DIST(0,n)
If cause =6 or 22
For better cell handover causes, HO_MARGIN_XX(0,n)=HO_MARGIN(0,n)
- The flag EN_LOAD_ORDER is settable by OMC command.
- LINKfactor(0,n), HO_MARGIN_QUAL(0,n), HO_MARGIN_LEV(0,n), HO_MARGIN_DIST(0,n) and
HO_MARGIN(0,n) are parameters set by OMC command for each neighbour cell(n).
- FREEfactor(n) : weighting factor that takes into account the number of free traffic channels in a cell. It
is received in the message TCH usage information from RAM.
- For TCH, FREEfactor(n) is set to the value specified in [ 30],
- for SDCCH : FREEfactor(n) = 0.
- PBGT(n) is the power budget between the serving cell(0) and cell(n). For the formula, see Section
6.1.
All neighbour cells(n) which fulfil the following condition (HO-11) are sorted according to their
ORDER(n) :
AV_RXLEV_NCELL(n) > RXLEVmin(n) + max(0,[MS_TXPWR_MAX(n)-P])
(HO-11)
For multiband handover, P considered in (HO-11) corresponds to the classmark power in the
frequency band used by the cell n.
Equation (HO-11) ensures that the MS can communicate in the cell n.
For any handover cause, the first cell in the list is taken as target cell, i.e. the cell with the highest value
of ORDER(n). The cells do not need to fulfil any other condition.
If no cell fulfils the condition and the serving cell does not belong to the target cell list, the target cell list
is empty and no further action is carried out.
ED
EVOLIUM
04
RELEASED
(HO-12)
HANDOVER PREPARATION
0400_04.doc
28/11/2005
74/110
(HO-12bis)
For multiband handover, P considered in (HO-11) corresponds to the classmark power in the
frequency band used by the cell n.
For any handover cause the first cell in the list is taken as target cell, i.e. the cell with the highest value
of GRADE(n). If no cell fulfils the condition and the serving cell does not belong to the target cell list,
the target cell list is empty and no further action is carried out.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
75/110
3.2.4.1
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
76/110
If the timer T_FILTER expires, a handover alarm message containing no candidate cell is sent to the
handover management entity. This message means: no more alarm. The expiry of T_FILTER means
that the handover alarm initially triggered is considered as no longer valid.
Note 1: This behaviour also concerns the 3G cells.
3.2.4.1.2 Specific case of resource management handovers (Cause 29 and 30)
Each time a HO Cause 29 and cause 30 are triggered by the handover detection process, T_FILTER
is started or restarted, and an Alarm message is sent to HOM independently of the triggering of the
other causes. In this case, only the serving cell is in the list of candidate cells.
3.2.4.1.3 Specific case of fast traffic handovers (Cause 28)
The specific alarm management for Cause 28 is described in this section. Two steps are required in
HOP to deal with Cause 28. The first step consist in checking whether the current MS is capable of
performing a fast traffic handover when requested by RAM. In a second step, if RAM sends the Start
HO message and it concerns the current call and Cause 28, HOP will send the HO alarm Cause 28 to
HOM through the T_FILTER mechanism.
Upon the reception of the message Fast traffic HO request from RAM, the check of Cause 28 is
enabled by setting the HOP flag EN_CAUSE_28 to enable, and the reference and the channel rate of
the queued request is stored. When a new candidate cell list is received from the HO candidate cell
evaluation function because of Cause 28, the checking of Cause 28 is disabled by setting
EN_CAUSE_28 to disable, and the message Fast traffic HO ACK is sent to RAM. This message
contains (See also Section 4.2):
The reference of the queued request, which is given in the message Fast traffic HO request
sent by RAM,
The call reference, which is the reference of the current call.
At this step, even if Cause 28 is detected, the Alarm message is not send to HOM. This message
handling is described in Figure 21.
If two Fast traffic HO request arrive after each other, only the last one will be taken into account. This
last one concerns the top request of the queue. So only for the last received queued request reference
and channel rate, Cause 28 will be checked on reception of measurements. Every new received Fast
traffic HO request will overwrite the queued request reference and channel rate to be taken into
account when checking Cause 28.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
77/110
When an HO alarm is detected because of Cause 28bis, the handover detection function is computed
with the available radio measurements. All the relations for Cause 28 in (HO-26) are checked except
the condition EN_CAUSE_28 = enable. The handover cell evaluation function is then performed
including Cause 28 if triggered. If a candidate cell list is received from the candidate cell evaluation
function because of Cause 28, the timer T_FILTER is started or restarted, and the message Alarm is
sent to HOM containing the list of the candidate cells. The interaction of Cause 28 with the T_FILTER
mechanism is described in Figure 20.
Note 1: Since several MS can acknowledge the Fast traffic HO request, RAM needs to obtain the call
reference to distinguish the different MS acknowledgement.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
78/110
is here denoted n-1. According to the layer of the serving cell the following conditions must be checked
for starting the timer T_INHIBIT_CPT:
Case the serving cell is in the upper or single layer (CELL_LAYER_TYPE(n0) = upper or single)
Condition 1: The immediately preceding cell n-1 is in the indoor or lower layer, i.e.
CELL_LAYER_TYPE(n1) = lower or indoor, or the frequency band of the
immediately preceding cell n-1 is different from the frequency band of the
serving cell n0, i.e. CELL_BAND_TYPE(n1) <> CELL_BAND_TYPE(n0).
Condition 2: The call has previously performed i) an emergency internal handover on
quality (Cause 2, 4, and 7) towards the serving cell or ii) an external
handover with the A interface GSM cause uplink quality or downlink
quality and there is a bi-directional adjacency link between the preceding
external cell n-1and the serving cell n0.
If Conditions 1 and 2 are fulfilled the timer T_INHIBIT_CPT is started.
If these conditions are not fulfilled, the timer T_INHIBIT_CPT is not started.
The BSC detects that there is a bi-directional adjacency link between a given Cell Cext and a given Cell
Cint as follows. When the BSC receives an handover request from Cell Cext to Cell Cint, the BSC
checks whether or not there is an outgoing handover adjacency link defined from Cell Cint to Cell Cext. If
this adjacency link exists, the BSC considers that there is a bi-directional adjacency link between Cells
Cint and Cext. When performing this check, the BSC uses the Cell Global Identifier (CGI) of each cell
(i.e. the CGI where CGI = MCC + MNC + LAC + CI).
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
79/110
3.3
3.3.1
General
3.3.1.1
Enabling
The directed retry preparation is enabled upon reception of an indication from the handover
management entity (BSC internal message, see [ 28]). This indication is called "Start DR algos " in the
SADT diagram of section 2.3.6.
The directed retry is supported by the same processes as the handover preparation except for forced
directed retry (see section 2.4), consequently :
- for directed retry on handover alarms, the enabling consists in changing the behaviour of the
candidate cell evaluation process (see section 3.2.3). This process looks for target cells for TCH
channel instead of SDCCH channel.
- for forced directed retry : both the detection and candidate cell evaluation processes are enabled at
this point in time.
Note : The handover preparation function is enabled when the SDCCH connection is established
(reception of the ESTABLISH INDICATION from the corresponding BTS). Therefore the handover
preparation is always enabled before the directed retry preparation. This allows the detection process
for forced directed retry, after its enabling, to get immediately measurements from the neighbouring
cell measurements book-keeping.
When the directed retry preparation is enabled, SDCCH_COUNTER is stopped and not restarted.
Disabling
The directed retry preparation is disabled whenever the BSC initiates a channel release on the radio
interface.
3.3.1.2
The directed retry preparation function is completely handled by the BSC. The input parameters of this
function are provided by the active channel preprocessing function (refer [ 34]) which handles the
neighbour cell list book-keeping. As the handover preparation function, the directed retry preparation
function can be divided into two processes : Alarm detection and Candidate cell evaluation.
Once the directed retry preparation enabled, a directed retry on handover alarms or forced directed
retry alarm can be detected every SACCH multiframe upon reception of the averaged measurements
for directed retry detection.
Once a directed retry alarm is detected, the alarm detection process sends to the candidate cell
evaluation process the list of MS neighbouring cells with for each of them one of the handover causes
which have been verified.
The candidate cell evaluation builds a cells list which is according to the case and the value of
T_FILTER sent or not to the BSC function in charge of the handover management entity (see 3.2.4.).
3.3.2
Alarm Detection
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
80/110
The detection process is the Handover detection process described in Section 3.2.2 except that
intracell handover alarms and Cause 28 must be ignored.
Only intercell handover alarms are taken into account i.e. all handover causes except causes
mentioned above.
Forced directed retry
The following condition is checked every measurement reporting period and if at least one input
preprocessed parameter AV_RXLEV_NCELL_DR(n) is available.
CAUSE = 20 (high level in neighbour cell for forced directed retry)
AV_RXLEV_NCELL_DR(n) > L_RXLEV_NCELL_DR(n) (
(DR - 1)
and
EN_FORCED_DR = ENABLE
...
BTSnum
The threshold L_RXLEV_NCELL_DR(n) is the observed level from the neighbour cell n at the border of
the area where forced directed retry is enabled (See Section 2.4.1). This threshold fixes the size of the
overlapping area where forced directed retry can be performed. It should be greater than
RXLEVmin(n).
Alarms priority
As explained in section 2.4, the handover alarms have priority over the forced directed retry alarm (HO
cause 20). The priority order for handover alarms is indicated in Section 3.2.2.2.
3.3.3
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
81/110
with :
FREElevel_DR(n) : minimum threshold of free TCHs in the neighbour cell n for forced directed
retry.
t(n) : absolute number of free TCHs in the neighbour cell n.
For external cells, t(n) is fixed to the arbitrary value t(n)=255.
Therefore, setting FREElevel_DR(n) to 255 for an external cell inhibits outgoing external directed retry
towards this cell. Setting FREElevel_DR(n) to any other value will allow outgoing external directed retry
towards this cell.
Note : if the BTS has dual rate capability, t(n) = absolute number of free Dual Rate TCH
L_RXLEV_NCELL_DR(n) and FREElevel_DR(n) are parameters set by O&M for each neighbour cell
n.
If no cell fulfils the condition, the target cell list is empty and no further action is carried out.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
82/110
4
4.1
INTERFACES DESCRIPTION
3GPP interfaces/Physical interfaces
The messages used by the handover algorithms are carried on the Abis interface only.
Note that for handover decision and execution, all the relevant messages transmitted on the Air, Abis,
A interfaces are described in [ 23] and [ 24].
Note : In [ 34] is given the general structure of the Abis messages required by the handover algorithm.
In particular, the fields for which it is stated in the 3GPP Technical Specification 05.08 [ 38] "the coding
of this field requires further elaboration" are described. For the coding of the others information
elements, refer to [ 39].
4.2
Internal interfaces
The different BSC internal interfaces with HOP are detailed in this section (See Figure 22). The
information exchanged between handover functions is also described in Sections 2 and 4.4.
HOP : Handover preparation
This entity is responsible of triggering handover alarms. To detect handover alarm, HOP checks
continuously i) the radio environment of the mobile (radio level, radio quality, possible target cells,
traffic load, multi-layer network, etc.) and ii) the requests for handovers sent by RAM.
HOM : Handover management
This entity is responsible of managing the channel changes depending on handover alarms sent by the
HOP entity, the O&M configuration of the BSS, the events arriving from the protocol entities, etc. The
HOM behaviour is described in [ 28].
ICC : Internal channel change
This entity is responsible of running the internal channel change protocol when the HOM asks for it.
The ICC behaviour is described in [ 23].
ECC : External channel change
This entity is responsible of running the external channel change protocol, either for an outgoing
external channel change when the HOM asks for it (serving BSC) or autonomously for an incoming
channel change (target BSC). The ECC behaviour is described in [ 24].
RAM : Resource allocation and management
This entity is responsible for managing the radio resources of the BSS. RAM can also trigger handover
alarm messages that are sent to HOP. The RAM behaviour is described in [ 30].
Direction
RAM --> HOP
Message
TCH usage information
ED
EVOLIUM
04
Parameters of information
Cell reference
Total number of free TCH
LOADfactor and FREEfactor
AV_LOAD
Traffic_load
LOAD_SV3
EN_CAUSE_13
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
83/110
Move PS to CS zone
MS zone indication ACK
Channel description
Indication of the zone where the MS is located in
the serving cell: outer or inner
Call reference
Reference of the queued request
Start DR algos
Alarm
4.3
Timers list
NAME
RANGE
BIN.RANGE
BITS
T_FILTER
(0 to 31)x960 ms
0:31
0=0 ms
31=31x960ms
T_HCP
ED
EVOLIUM
(0 to 240 ) sec
04
RELEASED
0:240
HANDOVER PREPARATION
0400_04.doc
28/11/2005
84/110
0:240
1 to 30
1:30
every
TCH_INFO_PERIOD
1=1 , 30 = 30
2 to 25.5 sec
20:255
4.4
20=2 s, 255 =
25.5 s
This section provides a list of all the variables and parameters used in the algorithms and thus
encountered in the text. For each entry will be found :
its name,
its meaning,
its physical range,
its binary range,
the number of bits into which it is encoded.
The variables and parameters are ranked in the alphabetical order.
4.4.1
Handover
NAME
RANGE
BIN. RANGE
BITS
AV_BS_TXPWR_DR
0:30
0 = 0 dB
30 = -30 dB
0:30
0 = 0 dB
30 = -30 dB
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
0 to 100 %
step size 1%
0:100
0:63
0=-110
63=-47
AV_ECNO(n)
Average Ec/No of the 3G neighbour cell n
AV_LOAD(n)
Averaging load of the cell n
with a period equal to LOAD_EV_PERIOD
AV_RXLEV_DL_HO
Average Receive Downlink Level
of serving cell (used for Handover)
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
85/110
AV_RXLEV_DL_MCHO
Average Receive Downlink Level of serving
cell (used for Microcellular Handover)
AV_RXLEV_NCELL(n)
Average Receive Level
neighbour cell n at MS
AV_RXLEV_NCELL_BIS(n)
Average Receive Level
neighbour cell n at MS used for cause 13
AV_RXLEV_UL_HO
Average Receive Uplink Level
of serving cell (used for Handover)
AV_RXLEV_UL_MCHO
Average Receive Uplink Level of serving
cell (used for Microcellular Handover)
AV_RXLEV_PBGT_HO
Average Receive Downlink Level of
serving cell (PBGT calculation)
AV_RXQUAL_DL_CA_HR_FR
Average receive downlink quality of
serving cell (HR-to-FR channel adaptation)
AV_RXQUAL_UL_CA_HR_FR
Average receive uplink quality of
serving cell (HR-to-FR channel adaptation)
AV_RXQUAL_DL_CA_FR_HR
Average receive downlink quality of
serving cell (FR-to-HR channel adaptation)
AV_RXQUAL_UL_CA_FR_HR
Average receive uplink quality of
serving cell (FR-to-HR channel adaptation)
AV_RXQUAL_UL_HO
Average Receive Uplink Quality of
serving cell (used for Handover)
AV_RXQUAL_DL_HO
Average Receive Downlink Quality of
serving cell (used for Handover)
AV_RANGE_HO
0:63
0=-110
63=-47
0:63
0=-110
63=-47
0:63
0=-110
63=-47
0:63
0=-110
63=-47
0:63
0=-110
63=-47
0:63
0=-110
63=-47
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 63 x 3.69s
0:63
0 to 1023
0:1023
16
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
86/110
0 to 1023
0:1023
16
0 or 1
0:1
0 : good frame
1 : bad frame
0:15
0 = 0 dB
15 = -30 dB
0:15
0 = 0 dB
15= -30 dB
max - 30 to min 0 dB
step size 2 dB
(relative value)
0:15
0 = 0 dB
15= -30 dB
0:15
0 = 0 dB
15= -30 dB
max - 30 to min 0 dB
step size 2 dB
(relative value)
BSIC(n)
0 to 63
0:63
0 to 32
0:32
ANY_LOAD, NOT_LOW,
HIGH
0:2
BS_TXPWR_MAX
Maximum Transmit Power at BS
BS_TXPWR_MAX_INNER
Maximum BS Transmit Power permissible in the
inner zone of the concentric or multiband cell.
BS_TXPWR_MIN
0 : ANY_LOAD
1 : NOT_LOW
2 : HIGH
0 : 255
C_DWELL(n)
counter for time during which the MS has been
reporting the neighbour lower layer cell when on the
upper layer with a minimum receive level of
L_RXLEV_CPT_HO(0,n)
0 : 255
CELL_BAND_TYPE
GSM or DCS
1 : GSM
2 : DCS
Macro or Micro
0 : Macro
1 : Micro
ORDER or GRADE
0 : ORDER
1 : GRADE
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
87/110
CELL_LAYER_TYPE
Indicator of BTS layer type
0 : Single
1 :Upper
2 : Lower
3: indoor
CELL_PARTITION_TYPE
Normal or Concentric
0 : Normal
1 : Concentric
0 : Normal
1 : Extended outer
2 : Extended inner
0 to 24 dB
stepsize 1 dB
0:24
0
0
8
-DELTA_DEC_HO_margin DELTA_INC_HO_margin DELTA_DEC_HO_m
argin
DELTA_INC_HO_
margin
DELTA_INC_HO_margin
0 to 24 dB
stepsize 1 dB
0:24
0 :30 s
stepsize 1s
0:0
30 : 30
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
for
AMR
channel
EN_AMR_FR
Enable/disable AMR full rate
EN_AMR_HR
Enable/disable AMR half rate
EN_BETTER_ZONE_HO
Enable/disable flag for HO cause 13
EN_BI-BAND_MS(n)
Enables/disables the incoming handovers of bi-band
MSs from the preferred-band into a classical band
cell
EN_CAUSE_13
Enable/disable flag for HO cause 13. The flag is set
to enable when the inner zone is less loaded than the
outer zone
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
88/110
EN_CAUSE_15
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
EN_LOAD_BALANCE
Enable/disable load balance between inner and outer
zones
enable or disable
0 : disable
1 : enable
EN_LOAD_ORDER
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
89/110
1 : enable
EN_PBGT_HO
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
0 : disable
enable,
indefinite
disable
handovers
EN_RXLEV_DL
1 : enable
2 : indefinite
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
-16 to 16 dB
step size 1 dB
-16:16
0 to 255 channels
step size : 1 channel
0:255
ED
EVOLIUM
04
or
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
90/110
FREQUENCY_RANGE
Indicates in which frequency range the cell operates.
PGSM, DCS1800,
EGSM, DCS1900,
PGSM-DCS1800,
EGSM-DCS1800,
GSM850
0:6
0 : PGSM
1 : DCS18002 :
EGSM
3 : DCS1900
4 : PGSMDCS1800
5 : EGSMDCS1800
6: GSM850
GRADE(n)
-179 to 149 dB
-179:+149
16
0 to 100%
step size 10 %
0 : 10
0=0%
10 = 100%
0 to 120 s
step size 1 s
0:0s
120 : 120 s
HO Cause
Handover Cause
2, 3, 4, 5, 6, 7, 10, 11,
12, 13, 14, 15, 16, 17,
18, 20, 21, 22, 23, 24,
26, 27, 28, 29,30
0:29
0=0.. 29=29
HO_INTERCELL_ALLOWED
enable or disable
0 : disable
1 : enable
-127 to +127 dB
step size 1 dB
-127 :+127
-127 to +127 dB
step size 1 dB
-127 :+127
-127 to +127 dB
step size 1 dB
-127 :+127
-127 to +127 dB
step size 1 dB
-127 :+127
0 to 100%
step size 10 %
0 : 10
0=0%
10 = 100%
0 to 120 s
step size 1 s
0:0s
120 : 120s
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
(distance
causes)
HO_MARGIN_LEV(n1,n2)
Basic Margin for Handover (level causes) between
cell n1 and n2
HO_MARGIN_QUAL(n1,n2)
Basic Margin for Handover (quality causes) between
cell n1 and n2
L_LOAD_OBJ
Minimum desired load on umbrella cells
defined for each umbrella cell
L_MIN_DWELL_TIME
minimum value for MIN_DWELL_TIME
L_RXLEV_DL_H
Minimum Receive Level
for Downlink Level Handover
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
91/110
L_RXLEV_CPT_HO(0,n)
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
L_TIME_ADVANCE
Minimum Distance for Handover from the extended
outer zone of a cell
0 to 63 x 3.69s
0:63
LINKfactor(n1,n2)
-24 to +24 dB
step size 1 dB
-24:24
true or false
0 : false
1 : true
-16 to 0 dB
-16:0
0:100
0 to 8 cells
0:8
0=0
8=8
0:0s
120 : 120 s
0 to 120 s
step size 1 s
MIN_DWELL_TIME
0 to 120 s
0:0s
30]]
NBR_ADJ_3G
Number of 3G cell handover adjacencies
for a 2G cell.
MIN_CONNECT_TIME
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
92/110
step size 1 s
120 : 120 s
0 :2,
0 : indefinite
1 : slow
2 : fast
MS_TXPWR
Transmit Power at MS
See [ 32]
See [ 32]
MS_TXPWR_CONF
See [ 32]
See [ 32]
MS_TXPWR_MAX
Maximum Transmit Power at MS
See [ 32]
See [ 32]
MS_TXPWR_MAX(n)
Maximum Transmit Power from MS allowed by cell n
See [ 32]
See [ 32]
MS_TXPWR_MAX_INNER
Maximum MS transmit power permissible in the inner
zone of the concentric or multiband cell.
See [ 32]
See [ 32]
MS_TXPWR_MIN
Minimum Transmit Power at MS
See [ 32]
See [ 32]
MULTIBAND_TRAFFIC_CONDITION
ANY_LOAD, NOT_LOW,
HIGH
0:2
0 : ANY_LOAD
1 : NOT_LOW
2 : HIGH
1 to 128
1:128
1=1 SACCH
frames
128=128 SACCH
frames
0 to 64 cells
0:64
0=0
64=64
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
0 to 7 stepsize 0.1
0:70
0=0
70=7
0 to 7 stepsize 0.1
0:70
0=0
70=7
0 to 7 stepsize 0.1
0:70
0=0
70=7
NBR_ADJ
Number of adjacent
cells for this BTS
NEIGHBOUR_RXLEV(0,n)
Threshold of maximum downlink received level from
the neighbour cells for cause 13.
OFFSET_CA
Offset for channel adaptation hysteresis
OFFSET_CA_HIGH
Offset for channel adaptation hysteresis under high
load
OFFSET_CA_NORMAL
Offset for channel adaptation hysteresis under normal
load
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
93/110
OFFSET_RXQUAL_FH
0 to 7 stepsize 0.1
0:70
0=0
70=7
0:70
0=0
70=7
-127 to +127 dB
step size 1 dB
-127 :+127
-290 to 260 dB
-290:+290
16
0 to 63 dBm
Step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
P
Maximum Transmit Power for class of MS and for the
corresponding frequency band (GSM900, GSM850,
DCS1800, DCS1900)
See [ 32]
See [ 32]
PBGT(n)
-147 to +97 dB
-147:+97
PING_PONG_HCP
Dynamic handicap applied to the precedent cell on
which the call has been (see appx B). Defined on a
cell basis.
0 to 20 dB
stepsize 1 dB
0:20
PREC_LAYER_TYPE
indefinite,upper,
lower,single, indoor
0:4
0 : indefinite
1 : upper
2 : lower
3 : single
4 : indoor
0:3 ; 0 = none
1 = upper
2 = lower + indoor
3 = upper + single
Offset_Hopping_HO
Offset used in handover quality causes in case of
frequency hopping
OFFSET_HO_MARGIN_INNER
Offset which allows to take account of the radio
indication of
preceding cell
the
CELL_LAYER_TYPE
of
the
PREFERRED_BAND
Frequency band type where the biband
mobiles will be preferably directed
0 = none
1 = GSM
2 = DCS
PRIORITY(n1,n2)
Priority of cell n2 when serving cell=n1
0 to 5 step size 1
0:5
0: highest priority
5: lowest priority
RXLEV_DL_IH
-110 to 47 dBm
0:63
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
94/110
0=-110 dBm
63=-47 dBm
RXLEV_UL_IH
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
0=-47
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
0=-47
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
-110 to 47dBm
Step size.1dBm
63= -47
THR_RXQUAL_CA
Threshold for channel adaptation
THR_RXQUAL_CA_HIGH
Threshold for channel adaptation under high load
THR_RXQUAL_CA_NORMAL
Threshold for channel adaptation under normal load
ED
EVOLIUM
04
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
0 to 7
stepsize 0.1
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
95/110
THR_RXQUAL_CAUSE_15
0 to 7
stepsize 0.1
Traffic_load(n)
Situation of the traffic in the cell n
0:2
0 : indefinite
1 : low
2 : high
U_RXLEV_DL_MCHO
High threshold of minimum Receive Level
for Downlink (Level microcellular Handover)
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
U_RXLEV_UL_MCHO
High threshold of minimum Receive Level
for Uplink (Level microcellular Handover)
-110 to 47 dBm
step size 1 dBm
0:63
0=-110 dBm
63=-47 dBm
U_TIME_ADVANCE
Maximum Distance for Handover
0 to 63 x 3.69s
0:63
ZONE_HO_HYST_DL
Hysteresis downlink for Interzone Handover from the
outer
zone to the inner zone of a concentric cell or
multiband cell
-40 to +40 dB
step size 1 dB
0 : 80
ZONE_HO_HYST_UL
Hysteresis uplink for interzone Handover from the
outer zone to the inner zone of a concentric cell or
multiband cell
-40 to +40 dB
step size 1 dB
0 : 80
ZONE_TYPE
Indicator of cell zone
outer or inner
0 : Outer
1 : Inner
4.4.2
Directed retry
The following parameters are used by the directed retry procedure only.
NAME
RANGE
BIN. RANGE
BITS
AV_RXLEV_NCELL_DR(n)
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
0 or 1
0: Different
behaviour for E-
EGSM_RR_ALLOC_STRATEGY
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
96/110
EN_DR
1:
Same
behaviour for EGSM
capable
MS:
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
enable or disable
0 : disable
1 : enable
0:255
16
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
-110 to 47 dBm
step size 1 dBm
0:63
0=-110
63=-47
0 to 31
step size : 1 SACCH
frame
0:31
0=0
31=31
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
97/110
4.4.3
The document BSS telecom parameters[ 27] specifies also the rules to be fulfilled by the handover
parameters. The present specification is the reference document in case of discrepancy.
The default values for parameters are indicated in the document [ 27].
Each relationship is either mandatory or recommended.
The recommended relationships are not checked by an automatic procedure.
Note : - for thresholds relative to quality measurements, the 3GPP coding is assumed, as already stated,
it is contra-intuitive.
- The relationships between the parameters relative to HO preparation and the ones relative to Power
control are included. The parameters of power control are characterised by the suffix _P or _PC. For
more information about them, refer to [ 32].
Mandatory relationships
### RXLEV_UL_IH > L_RXLEV_UL_H.
### U_RXLEV_UL_P > L_RXLEV_UL_H.
### RXLEV_DL_IH > L_RXLEV_DL_H.
### U_RXLEV_DL_P > L_RXLEV_DL_H.
### Relations between LOADlevel_i :
For i=1 to 3, LOADlevel_i < LOADlevel_i+1
### Relations between LOADfactor_i :
For i=1 to 4, LOADfactor_i >= LOADfactor_i+1
### Relations between FREElevel_i :
For i=1 to 3, FREElevel_i < FREElevel_i+1
### Relations between FREEfactor_i :
For i=1 to 4, FREEfactor_i =< FREEfactor_i+1
###
Recommended relationships
### L_RXQUAL_UL_H >= L_RXQUAL_UL_P.
### L_RXQUAL_UL_H_AMR >= L_RXQUAL_UL_P.
### L_RXQUAL_DL_H >= L_RXQUAL_DL_P.
### L_RXQUAL_DL_H_AMR >= L_RXQUAL_DL_P.
### L_RXLEV_UL_H < L_RXLEV_UL_P.
### L_RXLEV_DL_H < L_RXLEV_DL_P.
### A_LEV_HO = 2 * A_LEV_PC.
### A_QUAL_HO = 2 * A_QUAL_PC.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
98/110
###
FREElevel_DR(n) > N_TCH_HO(n).
N_TCH_HO(n) is the number of TCH channel reserved in the best interference band (See [ 30] for
further details].
###
The parameters FREElevel_k shall be updated according to the cell load
evaluation. For instance, in a concentric cell, if EN_LOAD_OUTER = enable, only the TCH
resources of the outer zone of the cell shall be considered for the determination of the parameters
FREElevel_k. Regarding the EGSM TCH resources of the cell, these parameters shall also be
updated
according
to
the
value
of
the
parameters
EN_LOAD_EGSM
and
EGSM_ALLOC_STRATEGY [ 30].
###
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
99/110
When the channel adaptation handovers are enabled together with Causes 15 and 16 in the cell, it
is recommanded to use the same window size for averaging the quality measurements of Cause
15, 16 and 26: A_QUAL_CA_HR_FR = A_QUAL_HO and W_QUAL_CA = W_QUAL_HO.
###
For the definition of the different cell profiles, see section 2.4
The following relationships are mandatory, whatever CELL_BAND_TYPE.
-
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
100/110
###
then
ED
EVOLIUM
And
if
and
it is recommended:
HO_MARGIN_QUAL(n1,n2) = -127 dB
HO_MARGIN_LEV(n1,n2) = -127 dB
HO_MARGIN_DIST(n1,n2) = -127 dB
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
101/110
5
5.1
GLOSSARY
Abbreviations
3GPP
AMR
ARFCN
BA
BFI
BS
BSC
BSIC
BSS
BTS
CA
dB
DC
DR
DTX
DCS-1800
DCS-1900
E-GSM
Ec/No
FH
FR
GSM850
GSM-900
HO
HOP
HOM
HR
LCS
LOS
MSC
MS
O&M
OMC
P-GSM
PBGT
PC
RAM
SACCH
SADT
SDCCH
SDL
SMLC
TFO
TCH
TCH/FS
TCU
TOA
TRX
ED
EVOLIUM
04
rd
HANDOVER PREPARATION
0400_04.doc
28/11/2005
102/110
TS
UTRAN
Technical Specification
Universal Terrestrial Radio Access Network
Note : all the parameters and variables used in the algorithms are thoroughly described in the
dedicated sections and in section 4.
5.2
Definitions
internal HO : the handover execution is controlled by the BSC (only intracell and intercell-intraBSC HO).
external HO : the handover execution is controlled by the MSC (necessary for all intercell-interBSC HO, possible for intercell-intra-BSC HO).
intercell HO : handover between two channels of adjacent cells. The old channel belongs to the
serving cell, the new channel to the target cell.
Inter-system HO: Here covers the 2G-3G handover between a serving 2G cell and a 3G cell
external to the BSC. The handover execution is controlled by the MSC.
intra-BSC HO : the serving cell and the target cell belong to the same BSC.
Intralayer HO: An intralayer HO is an intercell HO which is performed between two cells pertaining
to the same layer.
interzone HO : intracell handover between the inner zone and the outer zone of a concentric or
multiband cell configuration.
intrazone HO : intracell handover within a zone (inner or outer) of a concentric or multiband cell
configuration.
directed retry : handover from SDCCH to TCH when the serving cell is congested at the starting
time of the assignment procedure.
In this release of the ALCATEL BSS, the directed retry is internal or external to the BSS.
- decibel unit :
The decibel is a unit currently used in radio communications. It is the logarithmic expression of the
ratio of two terms :
N dB = 10 log10(P1/P2) with P1, P2 = signal power.
M dB = 20log10(V1/V2) with V1, V2 = signal voltage.
The dB is the usual unit for the gains of power or voltage.
The dBm is a variant of the dB unit :
Power expressed in dBm = 10 log10(P) with P expressed in mW.
Ex : 1W corresponds to 30 dBm. 1pW (10-9 mW) corresponds to 90dBm.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
103/110
log normal fading : The signal attenuation during propagation is the product of small independent
attenuations. Expressed in dB, this attenuation becomes a random variable which has a normal (or
gaussian) pdf, (central limit theorem). The log normal fading is defined as a centred (mean value is
0) gaussian variable that must be added to the mean signal value resulting from propagation
attenuation in order to have the reported value of the signal level (by MS or BS).
The log normal fading standard deviation ### normally ranges about 6-7 dB in urban macrocellular
environment and about 5 dB for rural environment.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
104/110
ANNEXES
6.1
Annex A
PBGT(n)
=
AV_RXLEV_NCELL(n) AV_RXLEV_PBGT_HO
(BS_TXPWR_MAX AV_BS_TXPWR_HO)
(MS_TXPWR_MAX(n) MS_TXPWR_MAX)
- PING_PONG_MARGIN(n,call_ref)
PBGT_DR(n) =
AV_RXLEV_NCELL_DR(n) AV_RXLEV_PBGT_DR
(BS_TXPWR_MAX AV_BS_TXPWR_DR)
- (MS_TXPWR_MAX(n) MS_TXPWR_MAX)
with :
- AV_RXLEV_NCELL(n) : average of RXLEV_NCELL(n) over A_PBGT_HO or A_PBGT_DR
measurements (neighbour cell(n)).
- AV_RXLEV_NCELL_DR(n) :
average of RXLEV_NCELL(n) over A_PBGT_DR measurements
(neighbour cell(n)).
- AV_RXLEV_PBGT_HO : average of the received levels RXLEV_DL_FULL or RXLEV_DL_SUB over
A_PBGT_HO measurements (serving cell).
- AV_RXLEV_PBGT_DR : average of the received levels RXLEV_DL_FULL or RXLEV_DL_SUB over
A_PBGT_DR measurements (serving cell).
- BS_TXPWR_MAX
: max power of the BTS in the serving cell (fixed value for each BTS).
- AV_BS_TXPWR_HO : average of the BS_POWER values over A_PBGT_HO measurements.
- AV_BS_TXPWR_DR : average of the BS_POWER value over A_PBGT_DR measurements.
- MS_TXPWR_MAX(n) : max power level the MS is allowed to use in its neighbour cell(n).
- MS_TXPWR_MAX
: max. power the MS is allowed to use in the serving cell.
- PING_PONG_MARGIN(n,call_ref) is a penalty put on the cell n if :
it is the immediately precedent cell on which the call has been,
this cell belongs to the same BSC as the serving cell,
the call has not performed a forced directed retry towards the serving cell,
less than T_HCP seconds have elapsed since the last handover.
In this case PING_PONG_MARGIN(n,call_ref) = PING_PONG_HCP.,
If the call was not precedently on cell n, or if the preceding cell was external, or if
the call has just performed a forced directed retry, or if the timer T_HCP has
expired, then PING_PONG_MARGIN(n,call_ref) = 0
With abstraction of the PING_PONG_MARGIN, which is purely a handicap given to the preceding cell
for a certain time, the PBGT can be described in two steps :
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
105/110
6.2
Annex B
Recapitulation of the cell types allowed for the serving and the candidate cell for each handover cause
Handover causes
Too low quality uplink (cause 2)
All
All
All
ED
EVOLIUM
04
RELEASED
0400_04.doc
28/11/2005
106/110
All
CELL_DIMENSION_TYPE =
micro
CELL_PARTITION TYPE =
concentric
ZONE_TYPE = inner
CELL_PARTITION TYPE =
concentric
ZONE_TYPE = inner
(CELL_LAYER_TYPE = single
or
CELL_LAYER_TYPE = upper)
CELL_LAYER_TYPE = lower
CELL_LAYER_TYPE = indoor
(CELL_LAYER_TYPE = single
or
CELL_LAYER_TYPE = upper)
CELL_LAYER_TYPE = lower
CELL_LAYER_TYPE = indoor
04
CELL_PARTITION_TYPE =
concentric
ZONE_TYPE = outer
RELEASED
0400_04.doc
28/11/2005
107/110
CELL_LAYER_TYPE = upper
CELL_LAYER_TYPE = lower
CELL_LAYER_TYPE = upper
and
CELL_BAND_TYPE =
PREFERRED_BAND
CELL_LAYER_TYPE = upper
and
CELL_BAND_TYPE <>
PREFERRED_BAND
CELL_LAYER_TYPE = lower
and
CELL_BAND_TYPE =
PREFERRED_BAND
CELL_LAYER_TYPE = lower or
indoor
and
(EN_BI-BAND_MS(n)=ENABLE
or CELL_BAND_TYPE(n) <>
CELL_BAND_TYPE(0))
CELL_LAYER_TYPE = indoor
and
(EN_BI-BAND_MS(n)=ENABLE
or CELL_BAND_TYPE(n) <>
CELL_BAND_TYPE(0))
CELL_LAYER_TYPE = lower or
indoor and
(EN_BI-BAND_MS(n)=ENABLE
or CELL_BAND_TYPE(n) =
PREFERRED_BAND)
CELL_LAYER_TYPE = lower or
indoor
CELL_LAYER_TYPE = indoor
and
(EN_BI-BAND_MS(n)=ENABLE
or CELL_BAND_TYPE(n) =
PREFERRED_BAND)
CELL_LAYER_TYPE = indoor
CELL_LAYER_TYPE = lower
and
CELL_BAND_TYPE <>
PREFERRED_BAND
All
Same cell
All
Same cell
CELL_DIMENSION_TYPE =
micro
CELL_DIMENSION_TYPE =
micro
All
CELL_BAND_TYPE <>
PREFERRED_BAND
CELL_RANGE = extended
outer
Traffic handover (cause 23)
CELL_LAYER_TYPE = single
The MS is not in the inner zone of
or
a multiband cell
CELL_LAYER_TYPE = upper
CELL_LAYER_TYPE = lower
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
108/110
CELL_LAYER_TYPE = indoor
CELL_LAYER_TYPE = lower
CELL_LAYER_TYPE = indoor
All
CELL_BAND_TYPE =
PREFERRED_BAND
CELL_BAND_TYPE <>
PREFERRED_BAND
(CELL_PARTITION_TYPE =
concentric and ZONE_TYPE =
outer)
or
CELL_PARTITION_TYPE =
normal
All
All
All
CELL_LAYER_TYPE = indoor
Same CELL_BAND_TYPE (if
EN_MULTIBAND_PBGT_HO =
disable) (See note 2)
(CELL_LAYER_TYPE = single
or
CELL_LAYER_TYPE = upper)
and
FREQUENCY_RANGE =
PGSM-DCS1800 or EGSMDCS1800 (if
EN_MULTIBAND_PBGT_HO =
disable) (See note 2)
CELL_LAYER_TYPE = lower
and
FREQUENCY_RANGE =
PGSM-DCS1800 or EGSMDCS1800 (if
EN_MULTIBAND_PBGT_HO =
disable) (See note 2)
CELL_LAYER_TYPE = indoor
and
FREQUENCY_RANGE =
PGSM-DCS1800 or EGSMDCS1800 (if
EN_MULTIBAND_PBGT_HO =
disable) (See note 2)
EN_BI-BAND_MS(n)=ENABLE
or
CELL_BAND_TYPE(n) <>
CELL_BAND_TYPE(0)
EN_BI-BAND_MS(n)=ENABLE
or
CELL_BAND_TYPE(n) =
PREFERRED_BAND
All cells except serving cell
All cells except serving cell
Same cell
Same cell
3G cell
Note 1: The serving cell is a candidate cell if the MS is connected to the inner GSM 1800 zone of a
multiband cell.
Note 2: For handover causes 12 and 23, the conditions on the frequency band (Same
CELL_BAND_TYPE and FREQUENCY_RANGE = PGSM-DCS1800 or EGSM-DCS1800) are only
checked by the BSC if the EN_MULTIBAND_PBGT_HO flag is set to disable.
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
109/110
6.3
Annex C
END OF DOCUMENT
ED
EVOLIUM
04
RELEASED
HANDOVER PREPARATION
0400_04.doc
28/11/2005
110/110