2Handover

2.1General Notes on Handover

The handover algorithm is the most important algorithm in cellular mobile communications. Its main objectives are:

maintenance of connection in case of cell change (movement) channel change in case of severe disturbance (interference) design of cell borders and radio network structure.

Steps of the Handover Process The handover process can be divided into several sub-processes listed in the table below together with the network elements involved within the respective process. No. 1. Sub-process Measurements link quality serving cell received level neighbor cells 2. 3. 4. 5. 6. Measurement Preprocessing Neighbor cell book-keeping Handover Decision Target Cell Generation Target Cell Evaluation intra BSS handover inter BSS handover 7. 8. Selection of new channel Handover execution BSC MSC BSC MS, BTS, BSC, MSC MS, BTS MS BTS BTS BTS BTS Involved Network Element

Types of Handover Different types of handover can be distinguished with respect to the changed region: a cell, a BSS area or an MSC area. These are illustrated in the figure below. The different types of handover can enabled or disabled by several flags.

1. Intracell Handover 2. Intra -BSS Handover 3. Intra -MSC Handover 4. Inter -MSC Handover

BSC 1a 2

BSC 2

MSC 1

MSC 2

3 BSC 1b

Fig. 1 Types of handover

Handover Causes Two criteria groups of different handover causes are defined: Radio Criteria received quality (too low/bit error rate too high) received level (too low) MS-BS distance (too high) better cell (power budget: relative received level) Network Criteria serv. cell congestion > directed retry for call setup MS-BS distance (too high/low in extended cells) received level or MS-BS distance (too low/high in concentric cells) intracell HO The first three causes are known as mandatory or imperative causes, i.e. if one of these causes occurs, a hand-over is necessary to maintain the call. This may happen because the MS is leaving the coverage area of the serving cell (intercell handover) or because there is a strong interferer using the same channel in another cell (intracell handover). The fourth cause is an optional one, i.e. the link quality in the serving cell is sufficiently good, but there are neighbor cells with better received level. Though its not necessary for the link quality of this specific call, there is a benefit for overall network performance to handover the call to the better cell: A call in the better cell causes less interference, especially if power control is applied. Since to achieve the same received level in the better cell, a smaller transmit power can be used in this cell. In a well planned radio network better cell should be the overwhelming handover cause. Hence, the locations of a better cell handover determine the cell boundaries. The fifth cause is named forced handover because it is triggered by the BSC due to a congestion situation, and not due to radio conditions on the link. This handover (directed retry) is performed from a SDCCH in the congested cell to a TCH in a neighbor cell during call setup. The last two causes are intracell handovers in special cell configurations:

inter-/intracell HO intercell HO intercell HO intercell HO intercell HO intracell HO

in extended cells handovers are feasible from single to double timeslots and vice versa. In a concentric cell handovers are performed between the inner and complete area.

These handover causes can be enabled/disabled separately by corresponding flags.

Flags to enable/disable Handover Types and Causes due to Radio Criteria The flags to enable/disable the different handover types and causes are listed in the table below. They are administered in the object HAND. Specification Name EN_INTER_HO EN_INTRA_HO EN_BSS_INTER_HO DB Name INTERCH INTRACH LOTERCH Meaning Flag to enable/disable all handover types and causes except for intracell handover. Flag to enable/disable intracell handover. Flag to enable/disable a BSS internal intercell handover, i.e. if disabled, the handover is handled as an inter BSS handover even if the first cell in the target cell list belongs to the same BSS as the serving cell. Flag to enable/disable a BSS internal intracell handover, i.e. if disabled, the handover is handled as an inter BSS handover and the MSC is involved.

EN_BSS_INTRA_HO

LOTRACH

EN_RXQUAL_HO EN_RXLEV_HO EN_DIST_HO EN_PBGT_HO

RXQUALHO Flag to enable/disable intercell handover due to quality. RXLEVHO DISTHO PBGTHO Flag to enable/disable intercell handover due to level. Flag to enable/disable intercell handover due to distance. Flag to enable/disable better cell (power budget) handover.

Comments

Enabling BSS internal handover has the following advantages: reduction of signaling load on the A-interface reduction of processing load in the MSC faster handover execution. Consequences: BSS internal handover should be enabled, BSS regions should be adapted to traffic flows to reduce the inter-BSS handover rate.

Normally, intracell handover should be enabled to allow a handover from a channel with high interference to another one with less interference within the same cell. However, if random frequency hopping (see chapt. 6.2) is applied, it may be reasonable to disable intracell handover since interference is approximately the same on all channels and no improvement can be achieved by intracell handover. If distance handover is disabled, an MS could largely exceed the planned cell boundaries in the case of favorable radio conditions at the serving cell without causing a handover. As a consequence, neighboring cells may suffer from excessive interference produced by this MS. Furthermore, there is a risk that link quality decreases very suddenly (turn around a corner), i.e. there is the risk of a call drop. Hence, distance handover should be switched on. If power budget handover is disabled, no handovers with cause better cell are generated. Nevertheless, power budget is calculated and evaluated for the ranking of neighbor cells within the target cell list which also has to be compiled for mandatory handovers (Ch. 4.2.4).

2.2Measurement Preprocessing
Measurement Values: The following parameters are measured and calculated each SACCH multiframe (0.48 s): RXQUAL: It is defined according to GSM TS 05.08 as function of the bit error rate (BER) before channel decoding: RXQUAL = 0 RXQUAL = 1 RXQUAL = 2 RXQUAL = 3 RXQUAL = 4 RXQUAL = 5 RXQUAL = 6 RXQUAL = 7 : : : : : : : : 0.2% 0.4% 0.8% 1.6% 3.2% 6.4% 12.8% < < < < < < < BER BER BER BER BER BER BER BER < < < < < < < 0.2% 0.4% 0.8% 1.6% 3.2% 6.4% 12.8% assumed value: assumed value: assumed value: assumed value: assumed value: assumed value: assumed value: assumed value: 0.14% 0.28% 0.57% 1.13% 2.26% 4.53% 9.05% 18.01%

The RXQUAL values are measured on the dedicated channel for the uplink as well as for the downlink for each TDMA frame (100 frames) within an SACCH multiframe. The measured RXQUAL values are averaged over the respective SACCH period using the assumed values of the table above. The resulting RXQUAL value is the one used within the handover algorithm in the way described below. RXLEV: The received level is measured on the dedicated channel for the uplink as well as for the downlink for each TDMA frame (100 frames) within an SACCH multiframe. The measured level values in [dBm] are averaged over the respective SACCH period. The average value is mapped on an RXLEV value using the table below (refer to GSM TS 05.08): RXLEV = 0: RXLEV = 1: RXLEV = 2: RXLEV = 62: RXLEV = 63: - 110 dBm - 109 dBm - 49 dBm < < < RXLEV RXLEV RXLEV RXLEV RXLEV > - 110 dBm - 109 dBm - 108 dBm - 48 dBm - 48 dBm

RXLEV_NCELL(n): The mobile measures the level received on the BCCH frequency of each neighbor cell n. The mapping is as for RXLEV above. MS_BS_DIST: The distance MS_BS_DIST between the MS and BS is calculated from the timing advance (TA) value measured by the BS and is coded as follows: MS_BS_DIST = 0, 1, ... 35. Distance[Km]. Aspects of Discontinuous Transmission When Voice Activity Detection (VAD) and Discontinuous Transmission (DTX) is applied not all TDMA frames within a SACCH multiframe may be transmitted. Hence, RXQUAL and RXLEV measurement values (SUB values) for the corresponding SACCH frames are less reliable than those for that SACCH with no silence period (FULL values). Therefore SUB and FULL values have to be distinguished within measurement preprocessing (see below).

SACCH Multiframe Occupancy

D n T o X t

a le pi d p

:1 0 0

st l s o

n o t

il d e

D T X

a le pi d p

( s n pi d ie e e e l c r o

)1 : 2

st l s o

n o t

il d e

i l st d l eo

se h u t p c bs e r

S C A H C

bs ut r

S n d cp n u t ie e e r to b s l c si i r

Fig. 2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Measurement Values for Handover (Summary) Measurement RXLEV_DL_FULL RXLEV_DL_SUB RXQUAL_DL_FULL RXQUAL_DL_SUB DTX_USED RXLEV_NCELL(1..6) BCCH_FREQ_NCELL_(1... 6) BSIC_NCELL (1...6) RXLEV_UL_FULL RXLEV_UL_SUB RXQUAL_UL_FULL RXQUAL_UL_SUB MS_BS_DIST Range 0 - 63 0 - 63 0-7 0-7 0.-.1 0 - 63 0 - 31 0 - 63 0 - 63 0 - 63 0-7 0-7 0 - 35 Measurement Type Description Received signal level on TCH/SDCCH (full set of TDMA frames) downlink Received signal level on TCH (subset of TDMA frames) downlink Received signal quality on TCH/SDCCH (full set of TDMA frames downlink Received signal level on TCH (subset of TDMA frames) downlink DTX used/not used on uplink in previous frame Received signal level on BCCH of up to 6 neighbor cells (downlink) BCCH RF channel number of up to 6 neighbor cells (downlink) Base Station Identity Code of up to 6 neighbor cells (downlink) Received signal level on TCH/SDCCH (full set of TDMA frames) uplink Received signal quality on TCH (subset of TDMA frames) uplink Received signal quality on TCH/SDCCH (full set of TDMA frames) uplink Received signal quality on TCH (subset of TDMA frames) uplink Absolute MS-BS distance [km]

Illustration of Measurement Preprocessing The measured (and reported) data per SACCH multiframe are preprocessed within the BTS using a gliding average window. The size of the window can be set separately for RXQUAL, RXLEV, DIST and PBGT. The measured RXLEV_FULL/SUB or RXQUAL_FULL/SUB values are put into the gliding window with a multiplicity (weight) given by the parameter W_LEV_HO or W_QUAL_HO, respectively. This is illustrated in the figure below. DTX enabled: Averaging of RXLEV Example: average of RXLEV with a gliding window of size and a weight factor of the full values of A_LEV_HO = 4 W_LEV_HO = 2.

average value Gliding Window 32 27 27 23 29 29

= 27

21

28

31

32

27

23

29

21

Measurement Values each SACCH Multiframe (0.48 s)

RXLEV_SUB ( weight 1)

RXLEV_FULL ( weight 2)

Fig. 3 Illustration of weighting and averaging of measurement values

Parameters for Measurement Preprocessing The parameters for measurement preprocessing for handover are administered in the object HAND and are listed in the table below. Specification Name A_QUAL_HO DB Name HOAVQUAL AQUALHO HOAVQUAL WQUALHO HOAVLEV ALEVHO HOAVLEV WLEVHO HOAVDIST Range 1-31 Meaning Averaging window size for RXQUAL values, used for handover decisions due to RXQUAL Weighting factor for RXQUAL_FULL values Averaging window size for RXLEV values, used for handover decisions due to RXLEV Weighting factor for RXLEV_FULL values Averaging window size for Timing Advance values used for handover decisions due to distance. Averaging window size used for power budget calculation. Averaging is applied to: RXLEV_DL PWR_C_D RXLEV_NCELL

1-3 1-31

W_QUAL_HO A_LEV_HO

1-3 1-31

W_LEV_HO A_DIST_HO

A_PBGT_HO

HOAVPWRB 1-31

Comments: Range of W_XX: 1, 2, 3; as default value 3 is recommended.

Range of A_XX: 1...31, Step Size: 1 The adjustment of the averaging size mainly depends upon rate of change of the radio propagation conditions. Example: path loss (change of 3 dB at a distance of 2000 m) long term fading change of 6 dB short term fading MS movement of 5...100 m MS movement of 0.15 m MS movement of 400 m

Hence, at the cell border the main variation of received level is due to long and short term fading. Within one SACCH multiframes an MS moves 0.5 m 5.0 m for MS speed = 1 m/s = 3.6 km/h for MS speed = 10 m/s = 36 km/h

Using an averaging window size of 10 SACCH frames, short term fading is averaged for pedestrians (as well as for fast moving MSs). Long term fading is partly averaged for fast moving MSs (the degree of average depends on the exact speed and the correlation length of long term fading, whereas there is nearly no averaging of long term fading for pedestrians. The setting of the averaging window size has to be a compromise between a fast decision and a reliable decision. Therefore it is recommended to use a larger window size for the optional handover (better cell) to do not cause a lot of unnecessary handovers and a smaller window size for the mandatory handover causes (quality, level, distance) to be able to react quickly on a sudden decrease of link quality.

2.3Handover Criteria
Evaluation of handover criteria is based on:

Up- and downlink measurements of level and quality The absolute MS-BS distance The power budget criterion of up to 32 neighbor cells BSC-trigger to answer with a HO Condition Indication message Intercell HO requests the allocation of a dedicated channel outside the serving cell Intracell HO requests the allocation of another dedicated channel within the serving cell Power budget HO as normal criterion All other TCH-causes as alarm- or imperative criteria Forced HO triggered by the BSC (see chapter 4.2.7)

Two types of handover may occur:

GSM distinguishes three classes of handover criteria:

On TCHs it is possible that the condition for more than one handover cause is fulfilled. Therefore it is necessary to rank the evaluation of handover causes. On SDCCH where only one cause is evaluated, no ranking is necessary. Static ranking is performed according a priority list. Priority 1 2 3 4 5 6 7 Handover Cause Extended Cell Handover Concentric Cell Handover Quality Intercell Handover Level Handover Distance Handover Power Budget Handover Quality Intracell Handover Forced Handover HO type intracell intracell intercell intercell intercell intercell intracell intercell HO class imperative imperative imperative imperative imperative normal imperative forced evaluated on TCH TCH TCH TCH TCH TCH TCH SDCCH

Handover causes priorities

Handover Criteria Evaluation - Static Ranking

E v a lu a H O te c rite rio n p r io r ity 1

HO d e te c te d Y

N E v a lu a te O H c rite rio n p rio rity 2

HO d e te c te d Y

N E v a lu a te O H c rite rio n p rio rity 3

HO d e te c te d Y

N U 8 n til v a lu a tio n e o f H Oc rite rio7 n

Fig. 4

Handover Criteria Evaluation - Dynamic Ranking In some cases it is necessary to rank priorities dynamically: in case a extended cell HO (single/double timeslot) or an Concentric Cell HO (inner/complete area) was requested but could not be performed due to lack of resources, evaluation of these criteria is skipped the next time to make evaluation of other HO criteria possible (e.g. Quality, Level etc.). In case the following HO-attempt is also unsuccessful or no other HO can be detected then the skipped priority is enabled again for the next try. BTS toggles. The following flow chart shows in principle the dynamic ranking mechanism of Extended Cell HO/Concentric Cell HO:

Dynamic ranking of HO evaluation is also performed in case of Quality inter-/intracell HO (see chapter 2.3 Handover detection algorithms).

S k ip e v a lu a t io Y n o fH Oc r it e r io n (s lipf la g s e t _ ) N R e s e t _f laip sk g

HO c o n d it i o n f u lf ille d Y

S e st k ip la g _f

H Od e t e c t e d

Fig. 5

2.4Handover Detection Algorithms

The standard handover algorithm for radio criteria uses the decision criteria listed in the table below where the order of processing within the overall handover algorithm is used (see Fig. 8). These criteria will be modified for a speed sensitive handover used within hierarchical cells (refer to reg. 4.2). Handover Causes Intercell HO due to Quality Decision Criteria 9. RXQUAL_XX > L_RXQUAL_XX_H 10. RXLEV_XX < L_RXLEV_XX_IH * 11. XX_TXPWR = Min ( XX_TXPWR_MAX, P ) HO due to Level 12. RXLEV_XX < L_RXLEV_XX_H 13. XX_TXPWR = Min ( XX_TXPWR_MAX, P ) HO due to Distance HO due to Power Budget 14. MS_BS_DIST > MS_RANGE_MAX 15. RXLEV_NCELL(n) > RXLEV_MIN(n) + Max ( 0, MS_TXPWR_MAX(n) - P ) 16. PBGT(n) > HO_MARGIN(n) Intracell HO due to Quality * skip flag not set 17. RXQUAL_XX > L_RXQUAL_XX_H 18. RXLEV_XX > L_RXLEV_XX_IH

Notes:

XX: MS_TXPWR_MAX: MS_TXPWR_MAX(n): P [dBm]:

used as variable for both UL (uplink) and DL (downlink) maximum allowed transmit power of the MS in the serving cell, maximum allowed transmit power of the MS in the adjacent cell n the maximum power capability of the MS (power class)

An intercell handover due quality or level is only performed if the transmit power of the MS or BS respectively is on its maximum.

Dynamic Ranking of Quality Inter-/Intracell Handover When criteria for Quality Intercell HO are evaluated it is first checked if any Quality handover shall be performed (averaged UL/DL measurements show a high signal quality value). Then the criterion of Quality Intracell handover is evaluated. Its obvious that Quality Intercell HO is detected when the criterion of Quality Intracell HO is not given. In case a Quality Intracell HO was requested but could not be performed (HO_FAILS) than Quality Intercell HO is tried the next time (if criterion is still given). When this Intercell HO attempt also fails then BTS toggles back and tries again an Intracell HO. To initiate a Quality Intercell HO after an unsuccessful Quality Intracell HO attempt, a skip_flag is used. This skip_flag is set after an Intracell HO attempt and is processed in case of Quality Intercell detection. When the criterion of Quality HO is given and the skip_flag for Intracell HO is not set, it is possible to perform a Quality Intracell HO if the condition is fulfilled. In this case the evaluation of handover criteria is resumed with the next priority level. When the criterion of Quality HO is given and the skip_flag for Intracell HO is set, an unsuccessful Intracell HO has been performed before. The dynamic ranking mechanism forces an Intercell HO instead of the previous Intracell HO by skipping the evaluation for Quality Intracell HO condition. The skip_flag is reset again to make a future Intracell HO evaluation possible in case this Intercell HO attempt also fails. BTS toggles between intracell and intercell handover.

Limitation of Intracell HO Repetition The BTS is informed by the BSC that a number of consecutive and successful Intra Cell HO over the same connection have been performed. Any further subsequent Intracell HO has to be disabled for a defined period of time, but if criteria are given during penalization time a Intercell HO may be tried instead. The O&M flag Enable_Limitation_Intracell_HO is used to enable/disable this feature.

Parameters for Intracell handover limitation Specification Name Enable_Limitation_Intracell_H O Max_Intracell_HO Timer_No_Intracell_HO Object HAND HAND HAND DB Name ELIMITCH MAIRACHO TINOIERCH O Range TRUE/FALS E 1 .. 15 1 .. 254 Step Size 1 1

BR 4.0 Unit 1 sec

This attribute Max_Intracell_HO specifies the maximum number of consecutive successful quality intracell handovers which are permitted in the same BTS for a single connection. The next intracell HO is suspended when the threshold Max_Intracell_HO+1 is reached, until the Timer_No_Intracell_HO expires. The following flow charts (fig. 27-28) show in principle the evaluation of Quality HO criterion (incl. dynamic ranking mechanism of Quality inter-/ intracell HO and limitation of intracell HO repetition).

Dynamic Ranking of Quality Inter-/Intracell Handover

M a x .o w e r p Y

C o n d it io n f o rN Q u a liH yO t f u lf il le d Y S k ip I n t rH c e l l N aO (s k ip la g s e t _f ) Y Y r e s e t s klaipg _f Y

R XLEV < N L _ R X L E V _ IH

Q u a li t y I n t e r c e l l H Od e t e c t e d

Fig. 6

Dynamic Ranking of Quality Inter-/Intracell Handover & Limitation of Intracell HO Repetition

L im it.f o in tr a c H ll r e p eO : p e n a liz a ttim n io e a c t iv e Y s e t s k ip g _f la

S k ip I n t r a cO ll Y H e (s k ip la g s) e t _f N N I n t r a c H llO e c o n d itio n f u lf ille d Y s e t s k ip g _f la

Q u a lit y In t r a c e ll H Od e te c t e d

Fig. 7

Power Budget: PBGT(n) = RXLEV_NCELL(n) - ( RXLEV_DL + PWR_C_D ) + Min( MS_TXPWR_MAX, P ) - Min( MS_TXPWR_MAX(n), P ) > HO_MARGIN(n) RXLEV_DL: PWR_C_D: averaged value of the measured downlink level in the serving cell, BS_TXPWR_MAX [dBm] - BS_TXPWR [dBm] averaged difference between the maximum downlink RF power BS_TXPWR_MAX and the currently used downlink power BS_TXPWR (due to power control) in the serving cell. RXLEV_NCELL(n) averaged value of the measured downlink level of the adjacent : cell n HO_MARGIN(n): handover margin; if path loss with respect to the serving cell exceeds the path loss with respect to the adjacent cell n by this margin, the adjacent cell is considered as the (much) better cell.

Loss(serving) - Loss(adjacent) = = BS_TXPWR - RXLEV_DL - ( BS_TXPWR_MAX(n) - RXLEV_NCELL(n) ) = RXLEV_NCELL(n) - ( RXLEV_DL + PWR_C_D ) + BS_TXPWR_MAX - BS_TXPWR_MAX(n). Assumption: BS_TXPWR_MAX - BS_TXPWR_MAX(n) = MS_TXPWR_MAX - MS_TXPWR_MAX(n)

if the link budget of the serving cell is designed for MSs of P = MS_TXPWR_MAX and if the link budget of the adjacent cell n is designed for MSs of P = MS_TXPWR_MAX(n).

Back Handover Prevention Back-handover (due to power budget) prevention is triggered by BSC by including the old cell and the previous handover cause (GSM 08.08 Cause) in the Channel activation message. A timer is started in BTS and until the timer for the specified cell expires,

no handover condition due to Power Budget will be evaluated for this cell this cell is excluded from the target cell list in case of any other handover request due to Power Budget.

The O&M flag Enable_No_Back_HO is used to enable/disable this feature. Back handovers due to imperative criteria are not affected by this mechanism. Parameters for Back Handover Prevention Specification Name Enable_No_Back_HO Timer_Inhibit_Back_HO Object HAND ADJC DB Name NOBAKHO TINHBAKHO Range TRUE/FALS E 1 .. 254 Step Size 1 BR 4.0 Unit 1 sec

General Information Flow

BS T H O C n In od d C ll e A ( , CD B , )

BC S

C ll e

C a A tiv hn c

inB(

C ll e

AH , O

c ue as

In c s o ae f P G- O B TH : C ll A is n t in lu e e o c dd inT L C

Fig. 8

Parameters of Handover Decision Specification Name L_RXQUAL_DL_H L_RXQUAL_UL_H DB Name/ Object HOLTHQUDL HOLTHQUUL /HAND Range 0...7 Meaning Thresholds for downlink/uplink quality. If RXQUAL is above these thresholds, the received level is low and the transmit power has reached its maximum, a quality intercell handover is initiated. Thresholds for downlink/uplink level. If RXLEV is below these thresholds and the transmit power has reached its maximum a level handover is initiated. If the quality falls below a threshold, but the received level is high, higher than L_RXLEV_XX_IH, an intracell handover is initiated. If the measured timing advance value is above this threshold, a distance handover is initiated in a standard cell. Unit: 1Km

L_RXLEV_DL_H L_RXLEV_UL_H

HOLTHLVDL HOLTHLVUL /HAND

0...63

L_RXLEV_DL_IH L_RXLEV_UL_IH

HOTDLINT HOTULINT /HAND

0...63

MS_RANGE_MAX

HOTMSRM /HAND

0...35

MS_RANGE_MAX_EX T

HOTMSRME /HAND

35...100 If the measured timing advance value is above this threshold, a distance handover is initiated in an extended cell. Unit: 1Km 2...15 0...15 Maximum TXPWR an MS is allowed to used in the serving cell 2 = 39 dBm, 15 = 13 dBm (GSM) 0 = 30 dBm, 15 = 0 dBm (DCS)

MS_TXPWR_MAX

MSTXPMAX /BTSB

Specification Name MS_TXPWR_MAX (n)

DB Name/ Object MSTXPMAXCL /ADJC

Range 2...15 0...15

Meaning Maximum TXPWR an MS is allowed to use in the neighbor cell n 2 = 39 dBm, 15 = 13 dBm (GSM) 0 = 30 dBm, 15 = 0 dBm (DCS)

RXLEV_MIN(n)

RXLEVMIN /ADJC

0...63

The level received from a neighbor cell n has to exceed this threshold

to initiate a better cell handover to that neighbor cell to include this cell in the target cell list for a mandatory handover.

HO_MARGIN(n)

HOM /ADJC

0...126

The path loss difference between serving and adjacent cell has to exceed this margin for a better cell handover. 63 dB ... + 63 dB

Handover Region

RXQUAL

L_RXLEV_XX_IH

7 Intercell HO due to quality Intracell HO due to quality L_RXQUAL_XX_H

Intercell HO due to level

no handover action due to quality or level

RXLEV 0 L_RXLEV_XX_H 63

Fig. 9 Regions of handover defined by quality and level thresholds

For adjusting the handover thresholds one has to distinguish two scenarios: A) Noise Limited Scenario: Large cells (in rural area) with low traffic load: received level at the cell border not much above the receiver limit sensitivity level. B) Interference Limited Scenario: Small cells (in urban area) with high traffic load: received level at cell border significantly exceeds the receiver sensitivity level, but C/I not much above the reference interference sensitivity. In any case intercell handover due to quality should be avoided as far as possible, i.e.

set L_RXQUAL_XX_H to highest value for acceptable speech quality, set L_RXLEV_XX_IH to a appropriate value so that in case of low RXQUAL an intracell handover is initiated for the locations within the cell area defined by the other thresholds.

Scenario A: Main handover criterion is the level criterion and L_RXLEV_XX_H has to be set to a value just some dBs above the receiver limit sensitivity level. Furthermore, there should be a hysteresis between the threshold RXLEV_MIN for incoming handover and the corresponding one for outgoing handover L_RXLEV_XX_H to avoid a lot of unnecessary forward and backward handover: RXLEV_MIN - L_RXLEV_XX_H = level hysteresis > 0. The order of magnitude for the level hysteresis is given by the standard deviation of the long term fading, i.e. RXLEV_MIN > L_RXLEV_XX_H + 4 ... 10 dB. Scenario B: In this scenario the better cell criterion should be the main handover criterion, since

it is the most suitable criterion for designing well defined cell borders, it guarantees that the mobile is served by the cell with (nearly) the lowest path loss and therefore offers the greatest potential for power control to reduce interference.

To avoid a lot of unnecessary forward and backward power budget handover caused by long term fading fluctuations of the received levels from the respective BTSs, a hysteresis has to be introduced: HO_MARGIN(cell1 -> cell2) + HO_MARGIN(cell2 -> cell1) = power budget hysteresis > 0. Usually, the handover margin is chosen symmetrically; its value should be a compromise between ideal power budget handover (low value) and a low rate of forward and backward handovers (high value).

By choosing unsymmetric values for the handover margin, one can adapt the cell area to the traffic load, e.g. increasing HO_MARGIN(cell1 -> cell2) while keeping the power budget hysteresis constant (i.e. reducing HO_MARGIN(cell2 -> cell1) by the same amount), increases the effective area of cell 1 while reducing that of cell 2). RXLEV_MIN(n) should be set to a value so that RXLEV_NCELL(n) > RXLEV_MIN(n) for almost all locations where PBGT(n) > HO_MARGIN(n), i.e. a better cell handover is really initiated if the power budget condition is fulfilled. This means that there should be an overlap of the outgoing power budget area of one cell and the incoming RXLEV_MIN area of the neighbor cell n. Furthermore, as for scenario A, there should be a level hysteresis between RXLEV_MIN and L_RXLEV_XX_H. This is illustrated for an ideal situation without long term fading in the figure below:

RXLEV_MIN

L_RXLEV_XX_H

BTS1

BTS2

ideal power budget cell border

BTS3

Fig. 10 Cell borders defined by handover thresholds

BS T R L VM ( X E _ IN L_ X E _X _ ( R L V XH re ive lim se sitivity ce r it n in m g co in H ) O H ) O

o o g le utg in vel

Fig. 11 Relation between handover level thresholds

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5Target Cell List Compilation

The target cell compilation proceeds in several steps: Definition of Neighbor Cells (Maximum Number = 32) by CI_NCELL(n): CI_NCELL(n) = Location Area Code (LAC) + Cell Identifier (CI) of Neighbor Cell n. The selection of neighbor cells affects handover traffic flow. The number of target cells should be kept to a minimum:

geographical neighbor cells if there is a traffic flow from the serving cell into these cells eventually some alternative cells if there is a congestion in the preferred direct neighbor cell MS needs the BCCH frequency for each neighbor cell n: Absolute Radio Frequency Channel Number of BCCH: ARFCN_NCELL(n) MS reports to BTS level measured on a certain ARFCN(n) together with Relative BCCH frequency number BCCH_FREQ_NCELL(n) (see Fig. 16) Decoded Base Station Identity Code BSIC(n) Neighbor Cells n1 and n2 using the same BCCH frequency ARFCN(n1) = ARFCN(n2) need different Base Station Identity Codes !!! BSIC: NCC: BCC: = NCC +BCC National Color Code (3 bits) Base Station Color Code (3 bits), has to be chosen by the network operator in accordance with rule given above.

Example Neighbor Cell 1 2 3 4 5 6 7 8 ARFCN_NCELL 4 4 11 18 25 32 39 39 BSIC 01 02 01 01 01 03 02 04 BCCH_FREQ_NCELL 0 0 1 2 3 4 5 5

BCCH_FREQ_NCELL(n) and BSIC(n) CI_NCELL(n)uniquely!

Illustration of Measurement Reporting and Neighbor Cell Book-Keeping Process

M e a s u re m e n t R e p o rt b y M S r e p o rtin g o f th e s tro n g e s t c e lls w ith k n o w n a n d a llo w e d B S IC ; m a x im u m : 6 c e lls B S IC 01 02 03 04 01 B C C H _ F R E QR X L E V _ N C E L L (n ) _ N C E LL 1 0 4 5 2 48 37 36 29 27 each S A C C H M u ltif ra m e

B o o k - K e e p in g a t B S N e ig h b o u r C e llA R F C N 1 2 3 4 5 6 7 8 4 4 11 18 25 32 39 39 B S IC 01 02 01 01 01 03 02 04

B C C H _ F R E R X L E V _ N C E L L (n ) Q_ N C E LL 0 0 1 2 3 4 5 5 0 37 48 27 0 36 0 29

F o r n o t re p o rte d n e ig h b o r c e lls R X L E V _ N C E L L is s e t to 0
Fig. 12

Parameters for Target Cell Generation Process The parameters for measurement reporting and target cell generation are summarized in the table below. Specification Name DB Name/ Object Range 0...999 0...999 1...65535 0...65535 0...1023 Meaning Global cell identifier of the adjacent cell consisting of mobile country code, mobile network code, location area identifier and cell identity Absolute radio frequency channel number of the BCCH frequency of the neighbor cell. Base station identity code consisting of national color code and base station color code. Neighbor cell measurement are identified using the BSIC and the relative frequency number of the BCCH. The MS includes only received level values of those cells within the measurement report which are defined as cells of a permitted PLMN. A PLMN with NCC = n - 1 is permitted if bit n of PLMNP is set to 1.

CI_NCELL CELLGLID/ MCC-MNC-LAC-CI ADJC

ARFCN_NCELL

BCCHFREQ/ ADJC BSIC/ ADJC

BSIC = NCC + BCC

0...7 0...7

PLMN_ PERMITTED

PLMNP/ BTSB

0...255

Uniqueness of Neighbor Cell Measurements: BSIC (n1) BSIC (n2) for adjacent cells n1 and n2 with ARFCN(N1) = ARFCN(n2)

Generation of the Target Cell List The target cell list is generated when a handover cause is detected. The maximum number of cells to be included in the target cell list is given by the parameter N_CELL (Parameter NCELL in object HAND, Range: 0 ... 15).

Conditions for Neighbor Cells to be included in the Target Cell List:

for Quality, Level and Distance Intercell Handover: RXLEV_NCELL(n) > RXLEV_MIN(n) + MAX(0, MS_TXPWR_MAX(n) - P) for Power Budget Handover: RXLEV_NCELL(n) > RXLEV_MIN(n) + MAX(0, MS_TXPWR_MAX(n) - P) & PBGT(n) - HO_MARGIN(n) > 0

Order Criterion for Handover Candidate Cells within the Target Cell List: PRIO_NCELL(n) = BCV(n) (Better Cell Value) BCV(n) = PBGT(n) - HO_MARGIN(n) PBGT(n): averaged value of the power budget (comp. chapt. 3.2.1, 3.2.2)

Evaluation of Target Cell List

Intracell Handover: HO Condition Indication message with cause Intracell HO without target cell list is sent from the BTS to the BSC. BSC selects new channel for the call within the same BTS.

Intercell Handover: HO Condition Indication message with cause and target cell list is sent from the BTS to the BSC. If the first cell within the target cell list is within its BSS area, the BSC selects a channel at the corresponding BTS. If no channel is available at that BTS, the next cell within the target cell is tried. If the first target cell (or the ones tried in further steps) does not belong to the own BSS area, a Handover Required message is sent to the MSC. This message contains a reduced target cell list (without the cells tried internally). This is illustrated in the following figure:

Illustration of Target Cell Evaluation

BTS

BSC

MSC

H a n d o v e ry e s D e t e c t io nH O C o n d I n d - cause - ta r g e t c e ll lis t no H andover F a ilu r e n e x t c e ll a v a ila b le yes n e x t c e ll y e s e x te rn a l H O R e q u ir e d - cause no - re d u c e d ta r g e t c e ll lis t s e le c t ch an nel

yes C hannel A c t iv a tio n

channel a v a ila b le no t ry n e x t c e ll

Fig. 13

2.6Handover Signaling and Timer

MS BTS s e r v in g M e a s u re m e n ts M e a s u re m e n ts H O C o n d In d H O R e q u ire d T_H AN D _R E Q T7 H OC o m m a n d H OR e q u e s t BSC s e rv in g M SC BSS ta rg e t

H OR e q u e s t A c k

H OC o m m a n d

H OC o m m a n d T8 H O C o n d In d

H O A ccess H O A ccess

H O R e q u ir e d

T 3124

H O D e te c t P h y s ic a l fo In

NY1

H O C o m p le te

T3105 P h y s ic a l fo In

H O F a ilu re C le a r C o m m a n d C h a n n e l e le a s e R C h a n n e l e le a s e R H O C o m p le te

m e s s a g e s fo r s u c c e s s fu l h a n d.o v e r , e .g m e s s a g e s a t tim e r , eex.g iry p.

H O R e q u ire d H O F a ilu re

Fig. 14 Non synchronized handover

Parameter and Timer for Handover Signaling T_HAND_REQ Object HAND Purpose: Start: Stop: Package DB Name THORQST Range 0...31 Step Size 1 Unit 2 * SACCH multiframe

minimum time for HANDOVER CONDITION INDICATION messages for the same connection sending of HANDOVER CONDITION INDICATION by BTS

HANDOVER COMMAND received reason for handover has disappeared communication with MS is lost transaction has ended, call cleared

Action expiry: Default: T7 Object BSC

repetition of HANDOVER CONDITION INDICATION 4

Package DB Name BSCT BSCT7

Range unit * (0...255)

Step Size 1

Unit MS100 = 100 msec HLFSEC = 0.5 sec SEC5 = 5 sec

Purpose: Start: Stop:

minimum time for HANDOVER REQUIRED messages for the same connection sending of HANDOVER REQUIRED by BSC

HANDOVER COMMAND received reason for handover has disappeared communication with MS is lost transaction has ended, call cleared

Action expiry: Default:

repetition of HANDOVER REQUIRED HLFSEC-4

T8 Object BSC Package BSCT DB Name BSCT8 Range unit * (0...255) Step Size 1 Unit MS100 = 100 msec HLFSEC = 0.5 sec SEC5 = 5 sec

Purpose: Start: Stop: Action expiry: Default:

keep the old channel sufficient long to be able to return to it, and to release the channels if the MS is lost reception of HANDOVER COMMAND at BSC reception of CLEAR COMMAND from MSC or HANDOVER FAILURE from MS at BTS release of old channels HLFSEC-20

T3124 - MS Timer, not adjustable by parameter, Purpose: Start: Stop: Action expiry: Default: detect the lack of answer from the network at handover access. sending of first HANDOVER ACCESS by MS reception of PHYSICAL INFORMATION by MS deactivation of new channel, reactivation of old channel, send HANDOVER FAILURE 675 msec for SDCCH - 320 msec else

T3105 Object BTS Purpose: Start: Stop: Action expiry: Package BTST DB Name T3105 Range unit * (0...255) Step Size 1 Unit MS10 = 10 msec

period for repetition of PHYSICAL INFORMATION sending of PHYSICAL INFORMATION by BTS reception of correctly decoded signaling or TCH frame on new channel from MS at BTS repetition of PHYSICAL INFORMATION; if the maximum number of repetitions has been reached: release of new channel MS10-10

Default: NY1 Object BTS

Package BTSC

DB Name NY1

Range 0...254

Step Size 1

Unit -

NY1 is the maximum number of repetitions of the physical information by the BTS. Default: 20

HOSYNC Object BSC Package BSCB DB Name HOSYNC Range NONSYNC/SYNC Step Size -

BR 4.5 Unit

Purpose: finely synchronized Handover (GSM 04.08) The finely synchronized handover is restricted to internal BTSE handover. In this case the MS only sends four HANDOVER ACCESS bursts (continuously in case of non-synchronized handover). Furthermore no PHYSICAL INFORMATIO is sent. The synchronized handover improves the speech quality during handover by a shorter handover procedure at the air interface.

Prevention of Handover Failure Repetition To prevent handover repetition after consecutive HO failures to the same cell a Handover Failure Indication message is received from the BSC. A timer is started and until expiry of the timer the defined cell is excluded from the target cell list for any kind of handover. The penalization time is defined by the O&M parameter Timer_Inhibit_Failure_HO, the number of permitted HO failures is defined by the O&M parameter Max_Failure_HO. The O&M flag Enable_No_Failure_Rep_HO is used to enable/disable this feature. Parameters for Handover Failure Repetition Specification Name Enable_No_Failure_Rep_H O Max_Failure_HO Timer_Inhibit_Failure_HO Object HAND HAND ADJC DB Name Range Step Size 1 1 BR 4.0 Unit 1 sec

NOFREPHO TRUE/FALSE MAXFAILHO TINHFAIHO 1 .. 15 1 .. 254

General Information Flow

BS T

BC S

Cll e

H O Cn I d odn H O Cn I d odn H O F ilueI d a r n

( , CD B , ) H O ( , CD B , ) ( ) B F ilue a r (c ll e ( c ll e B ) B )

H O F ilue a r

C ll e B is n t o in lu e c dd inT L C f r a df e o ein d pr d eio t e im

H O Cn I d odn

( ,D C )

ae ft r MX A H A F IL O c neu e o s c tiv H O f ilue o th a rs n e s m a ja e t c lls a e d cn e

Fig. 15

2.7Extended Cell Handover

Maximum propagation delay within one timeslot allows a maximum BS-MS distance of 35 km. In extended cells the operator can configure TCHs optionally as double timeslot channels where two subsequent timeslots are used for transmission to provide a coverage farther than 35km. Extended Cell Handover is the intracell handover between a single timeslot channel and a double timeslot channel and vice versa. Handover detection is based on comparison of actual BS-MS distance with a threshold (O&M parameter). Extended Cell handover can be enabled/disabled via O&M flag ENABLE_EXTENDED_CELL_HO only if there are double and single timeslots configured in the cell. Parameters for Extended Cell Handover Specification Name ENABLE_EXTENDED_CELL_H O HO_MS_TA_MAX HO_MARGIN_TA Object HAND HAND HAND DB Name EXTCHO HOMSTAM HOMRGTA Range TRUE/FALS E 0 .. 34 0 .. 35 Step Size 1 1 BR 4.0 Unit km km

A single-to-double handover is detected when the actual BS-MS distance exceeds the threshold HO_MS_TA_MAX (handover alarm distance_near_far); a double-tosingle handover is detected when the actual BS-MS distance falls below the threshold minus a hysteresis factor HO_MARGIN_TA (handover alarm distance_far_near). Following conditions must be fulfilled for a extended cell handover:

Enable_Extended_Cell_HO skip_flag

= TRUE = not set (see dynamic ranking).

The following additional condition must be fulfilled for a single to double timeslot handover:

actual BS-MS distance

> HO_MS_TA_MAX

or the following additional condition must be fulfilled for a double to single timeslot handover:

actual BS-MS distance

< HOMSTAM - HOMRGTA

(no double to single HO will be performed in case of HOMSTAM - HOMRGTA < 0 ).

2.8Preemption, Directed Retry, Queuing

This feature allows the assignment of a TCH when, due to the unavailability of resources, no unused channel can be found within the serving cell. Three main procedures are possible: Preemption, which is a means of providing TCH resources for high priority TCH requests; Directed Retry, which causes the handover from a SDCCH in one cell to a TCH in another cell; Queuing, which allows the queuing of TCH requests on a per cell and priority basis.

In case of unavailability of resources, two cases can be foreseen: Assignment Request and Handover Request. In case of Assignment Request, Preemption is tried first: BSC looks for a call in the cell with a priority lower than the new TCH request and, then moves the lower priority call to another cell performing a Forced Handover (or a Forced Release if HO fails) in order to free the TCH. The freed TCH is then assigned to the new request. If no call with a lower priority is using a TCH or a call with the same priority or higher is already waiting (queued) Directed Retry is performed. If still no free TCH is available, the queuing procedure is carried out, storing the TCH request in the cell queue based on their priority. In case of Handover Request, Preemption is tried first. If Preemption is not successful, the Directed Retry procedure will be skipped and Queuing is carried out. Preemption feature gives to the operator the possibility to differentiate subscriptions per user class (e.g. different contracts for high priority class such us police and other emergency body, business people and children) Queuing and Direct Retry features improve the network access and, in general, network QoS Parameter and Timer for Preemption and Queuing EN_PREEMPTION Object BTS Package BTSO DB Name EPRE Range ENABLED DISABLED Step Size Unit

Enable Preemption is used to enable/disable the preemption feature.

EN_QUEUEING Object BTS Package BTSO DB Name EQ Range ENABLED DISABLED Step Size Unit

Enable Queuing is used to enable/disable the queuing feature. QUEUEING_LENGTH Object BTS Package BTSO DB Name QL Range 1...100 Step Size 1 Unit

Queuing Length defines the maximum number of TCH requests hat can be queued in the cell. T11 Object BSC Package BSCT DB Name BSCT11 Range unit * (0...255) Step Size 1 Unit MS100 = 100 msec HLFSEC = 0.5 sec SEC5 = 5 sec

Purpose: Start: Stop: Action expiry: Default: Tqho Object BSC

maximum queuing time for ASS_REQ ASS_REQ is queued, BSC sends QUEUE_IND to MSC TCH becomes free for assignment or the request is replaced by an other request with higher priority. remove ASS_REQ from queue, send CLEAR_REQ to MSC HLFSEC-16

Package BSCT

DB Name

Range

Step Size 1

Unit MS100 = 100 msec HLFSEC = 0.5 sec SEC5 = 5 sec

BSCTQHO unit * (0...255)

Purpose: Start: Stop: Action expiry: Default:

maximum queuing time for HO_REQ HO_REQ is queued, BSC sends QUEUE_IND to MSC TCH becomes free for assignment or the request is replaced by an other request with higher priority. remove HO_REQ from queue, send HO_FAIL to MSC HLFSEC-20

New Information element in messages from MSC:

Assignment Request

Handover Request

Priority Information Element

Bit 8 spar e

Bit 7 PCI

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2 QA

Bit 1 PVI

PRIORITY LEVEL

PCI (preemption capability indicator) - it indicates if the preemption shall be applied or not. PRIORITY LEVEL - it contains the priority of the call; GSM supports the prioritization of calls using 14 priority levels (1 is the highest and 14 is lowest priority) QA (queuing allowed indicator) - it is used to perform the queuing procedure. PVI (preemption vulnerability indicator) - it indicates if this connection might be preempted by another allocation request. In GSM different priorities and access types are supported via the Priority Information Element being (optionally) conveyed in the ASS REQ or HO REQ message. The priority information element contains the following entries: The Preemptive Capability Indicator (PCI) applies to the allocation of resources for an event (e.g. ASS REQ, HO REQ) and indicates whether the event is able to trigger the preemption of radio resources. The Preemptive Vulnerability Indicator (PVI) applies for the entire duration of a connection and indicates whether the connection may become a target of preemption. The Queuing Allowed Indicator (QA) is used to decide on a per call basis if queuing shall be applied or not. The Priority Level (PL) is subdivided in 14 different levels, Priority Level 1 being the highest value. The entire procedure is shown in the Figures 19 and 20. These flowcharts basically indicate which algorithms and which checks are necessary in which network entity (BTS, BSC or MSC) and the message flow that has to be conveyed between the networks entities. It can be seen immediately that, in the best case, an assignment of a TCH in a neighbor cell takes place.

Flowchart of Preemption

A S S _ R E Q / H O _ R E Q (n v a T C b le a o ila H )

D o e s th e m e s s aN e g c o n ta in th e p rio rity I.E .? Y D ir e c te d R e try P ro c e d u re (s e e F.ig2 0 ) N PCI = 1 ? Y

S e t P C I= 0 , P V I= 0 , Q A =1, P L=14

Y O th e r q u e u e d c a lls w ith P C I= 1 a n d h e r o r h ig e q u a l p rio rity ? N N O th e r a c tiv e c a ll w ith P V I= 1 a n dw e P L lo r Y S e n d o rc e d H a n d o v e r F fo r th e lo wPeLrc a ll N

S u c c e s s? l fu Y

F o r c e R e le a s e th fe d o lo w e P Lc a ll r

B S Ca s s ig n s th e T C e fre H

Fig. 16

Flowchart of Directed Retry

D ir e c te d R e tr y P ro c e d u r e

Is th e in c o m in g N m e s s a gaen A s s ig n m _ R tE Q ? en Y B S Cs e n d to B T S s F o rc e_dH O R e q u e s t _ B T Ss e n d to B S C s In te rc _ H OC o n _In d e ll _ d w ith ta r g e t c e ll lis t S u ite b le c eN ll in lis t ? Y B S Ca s s ig nTsC H in te rn a lly a n d s e n d s Y A s s ig n m e n d m p le te _C o to M S C C e ll w ith in B S Ca re a? N S ta rt Q u e u e in g P ro c e d u r e

E N _ IN T E R _ S D C C HN H O _ s e tto e n a b le ? Y A s s ig T C H n rd Y D ire c te d R e try to w aN s M S Cs u c c e s s ? l fu

Fig. 17

Directed retry is the transition (handover) from a SDCCH in one cell to a TCH in another cell during call setup because of unavailability of an empty TCH within the first cell. Directed retry is a means to control the traffic distribution between cells and to avoid a call rejection because of congestion in one cell. If Queuing of ASS REQs is not supported within a BSC Directed retry is merely triggered by the BSC by sending a Forced HO Request message to the BTS which has to respond with a "initiated" Intercell HO Cond. Indic. message. It can happen that the Intercell HO Cond. Indic. message does contain only an empty target cell list (If triggered by a Forced HO Request message the BTS has to send a Intercell HO Cond. Indic. message even if no suitable neighbor cell exists - in this case the target cell list is empty!). In this case a TCH can not be assigned and the BSC shall not send a HO RQD message to the MSC of course but shall send an ASS FAILURE (cause "no radio resource available"). If the target cell list contains cells from inside and outside the BSC area and if e.g. the first and second cell is inside, the third outside and the fourth inside the BSC area than the Directed retry attempts shall be carried out as BSC controlled Directed retries to the first and second one. If these Directed retries are not possible for any reason (e.g. no empty TCH) than the third attempt and all following attempts (independently whether the fourth and the following cells lie in- or outside the BSC area) shall be executed as MSC controlled Directed retry. If in case of a MSC controlled handover the MS cannot access the new cell and the MSC receives a HO FAILURE (cause "radio interface failure, reversion to old channel") from the old BSS, it can happen that the MSC generally releases this SDCCH connection by sending a CLEAR CMD message (cause "radio interface failure, reversion to old channel") to the BSC independently. If the MSC does not support Directed retry HOs the BSC may perform BSC controlled Directed retries (approximately 75% of all Directed retries) only. In this case the EN_INTER_SDCCH_HO flag in the BSC shall be set to "disabled" and the BSC has to check the target cell list of Intercell HO_Cond_Ind messages belonging to a SDCCH connection. All cell identifiers not belonging to the BSC area shall be skipped and if there remain cell identifiers belonging to the BSC area the corresponding HO shall be performed to strongest (if impossible to the second strongest, third strongest etc.) remaining cell. If the target cell list does not contain a remaining or any cell identifier of the same BSC area, this Intercell HO Cond. Indic. message shall be discarded and the BSC shall release this SDCCH connection (Sending of an ASS FAILURE with cause "no radio resource available").

HO Algorithm/Generation of the Target Cell List The BTS has to send the Intercell HO Cond. Indic. messages toward the BSC. Please note that for Directed retry the sending of an Intercell HO Cond. Indic. message for a SDCCH may only be triggered by a BTS external event: The BSC sends a Forced HO Request because of "no TCH available". If an Intercell HO Cond. Indic. message is to be sent, the target cell list shall contain all neighbor cells with: RXLEV > RXLEV_MIN + Max(0, MS_TXPWR_MAX-P) + FHO_RXLEV_MIN_OFFSET in the order of decreasing values of (PBGT - HO_MARGIN <=> 0). Additional parameters specific to speed sensitive HO shall be taken into account for the ranking of the target cells. Even if no suitable neighbor cell exist, the BTS shall send an Intercell HO Cond. Indic. message. In this case the target cell list ("Cell Identif. List Pref. IE") shall be empty! The cause of the Intercell HO Cond. Indic. message shall be FORCED. FHO_RXLEV_MIN_OFFSET is a cell specific O&M-parameter to select only target cells for forced HO which the MS can access without any problems. It is a result of radio planning for each individual cell. It allows to influence the amount of Forced HOs failed because of empty target cell list, the amount of HO attempts back to the "old" cell and the success rate of HO ACCESSes to the target cell. Prevention of "Back-HOs" A major general problem of forced HO (Directed retry is one sort of forced HO!) is the probability of HO due to PBGT back to the "old" (congested) cell. Its drawbacks are: 19. increased load at the Abis-interface because of periodic sending of Intercell HO_Cond_Ind messages in intervals of T7 20. increased load at the A-interface in case of inter-BSC-HO because of the same reason 21. additional processor capacity in BSC (and MSC) is required for HO trials for which it is known in advance that they are useless 22. the load in the congested cell will not be reduced for a certain time, but it will be kept at a permanent high level. For the Channel Activation message a new optional information element "Cell Identifier List (no target)" is defined. This information element contains the cell identifier (CI) of a cell from which a handover request (intra- or inter-BSC) because of forced HO was received. If this information element exists in the Channel Activation message, the BTS

shall not trigger a (TCH-)HO due to PBGT for the time Tbho if the PBGT condition is fulfilled for the indicated cell only and shall not include the indicated CIs in the target cell list in this case for the time Tbho (i.e. for the condition HO due QUAL/LEV/DIST the indicated cell identifier may be part of the target cell list).

Tbho is a timer that limits the mentioned prohibitions. It has to be set by O&M command. If a HO is necessary the target BSC has to generate the Channel Activation message. The target BSC shall insert the Cell Identifier List (no target) IE into this message. The BSC shall derive the CI for the Cell Identifier List (no target) IE from the stored context in case of intra BSC HO or from the mandatory Cell Identifier (serving) IE of the HO REQ message in case of inter BSC HO with cause "Directed retry".

EN_FORCED_HO Object BSC Package BSCB DB Name ENFORCHO Range ENABLE DISABLE Step Size Unit -

This BSC specific O&M flag allows to enable/disable the sending of Forced HO Request messages for running SDCCH connections (e.g. queued or not queued ASS REQs which do not find an empty TCH). It is used to enable/disable Directed retry.

EN_INTER_SDCCH_HO Object BSC Package BSCB DB Name EISDCCHHO Range ENABLE DISABLE Step Size Unit -

This BSC specific O&M flag allows to enable/disable inter BSC SDCCH-HOs (i.e. SDCCH-SDCCH-HO and Directed retry). It simply prevents the sending of HO RQD messages for SDCCH connections to the MSC. This flag should be set to "disable" by an operator if in a network the MSC which the BSS is connected to or other adjacent BSSs do not support the prevention of "back-HO". If it is set to "disable" the BSC shall skip all cell identifiers of the target cell list of the Intercell HO Cond. Ind. message which belong to another BSC area.

FHO_RXLEV_MIN_OFFSET Object ADJC Package DB Name FHORLMO Range 0...24 Step Size 1 Unit 1 dB

FHO_RXLEV_MIN_OFFSET ("RXLEV_MIN offset for forced-handover") is a cell specific O&M-parameter used within the BTS to select only target cells for forced HO which the MS can access without any problems. It is a result of radio planning for each individual cell. It allows to influence the amount of Forced HOs failed because of empty target cell list, the amount of HO attempts back to the "old" cell and the success rate of HO ACCESSes to the target cell. Default: 6.

Tbho Object ADJC Package DB Name TIMERFHO Range 1...320 Step Size 1 Unit 10 sec

Tbho (bho=back handover) is a neighbor cell specific O&M parameter. It is the value of a timer running in the BTS that controls the duration how long a former serving cell from which forced HO was performed to the new serving cell may not be considered in the PBGT HO decision algorithm of the new serving cell and may not be contained in the target cell list. It is started at the reception of a Channel Activation message containing a Cell Identifier (no target) IE. Default: 12.