BSC3153

Nokia GSM/EDGE BSS, Rel. BSS13, BSC and

TCSM, Rel. S13, Product Documentation, v.1

Traffic Reason Handover in BSC

DN9814214 # Nokia Siemens Networks 1 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Contents

Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Overview of Traffic Reason Handover in BSC 9

2 Technical description of Traffic Reason Handover 11

3 Resource indication in Traffic Reason Handover 13

4 Handover candidate enquiry in Traffic Reason Handover 19

4.1 Traffic Reason Handover candidate enquiry 20
4.2 Special cases in Traffic Reason Handover candidate enquiry 23
4.3 Counters in handover candidate enquiry 24

DN9814214 # Nokia Siemens Networks 3 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

List of tables

4 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 List of figures

List of figures

Figure 1. RF resource indication procedure 13

Figure 2. Handover candidate enquiry procedure 19

DN9814214 # Nokia Siemens Networks 5 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

6 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Summary of changes

Summary of changes

Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.

Changes made between issues 8 and 7

Information on Dual Transfer Mode (DTM) interworking has been added.

In Overview of Traffic Reason Handover, a list of related topics has been

added.

In section Counters in handover candidate enquiry, the information on the

counters has been improved.

Changes made between issues 7 and 6

Editorial changes made. No changes have been made in the document

due to changes in software.

Changes made between issues 6 and 5c

The document has been revised throughout to comply with the latest
documentation standards. No changes have been made in the document
due to new features.

DN9814214 # Nokia Siemens Networks 7 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

8 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Overview of Traffic Reason Handover in BSC

1 Overview of Traffic Reason Handover in

BSC
Traffic Reason Handover (TRHO) is based on:

. radio frequency resource indications of idle channel interferences,

which are sent from the base transceiver station (BTS) to the base
station controller (BSC)
.
resource indications, which are sent from the BSC to the mobile
services switching centre (MSC)
.
radio interface measurements, which are used in selecting a target
cell for handover.

This procedure is used by the MSC for asking the BSC to determine a
given number of mobile stations (MS) for handover from one specified cell
to other specified cells. The possible handovers are controlled by the
MSC. The reason for a handover can be, for example, an excessive load in
the cell.

Related topics in Traffic Reason Handover in BSC

. Technical description of Traffic Reason Handover

.
Resource indication in Traffic Reason Handover
. Handover candidate enquiry in Traffic Reason Handover

Other related topics in BSC/TCSM documentation

. Reference
. Counters/Performance Indicators
.
Call Control Measurements (CSW)
. 1 Traffic Measurement
.
Parameters
. BSS Radio Network Parameter Dictionary

DN9814214 # Nokia Siemens Networks 9 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

. Descriptions
. Functional Area Descriptions
. Radio Network Performance
.
Handover Signalling in BSC
. RF Power Control and Handover Algorithm
.
Feature Descriptions
. Radio Network Performance
.
Advanced Multilayer Handling

10 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Technical description of Traffic Reason Handover

2 Technical description of Traffic Reason

Handover
The Traffic Reason Handover (TRHO) procedure consists of the
subclasses described below. Operations performed in these subclasses
coincide with one another. The subclasses are:

. radio frequency (RF) resource indication

.
resource indication
. handover candidate enquiry
.
MSC-controlled handover

During RF resource indication, the BTS sends information on idle channel

interferences to the BSC according to O&M definitions. During resource
indication, the BSC sends resource information on idle channels to the
MSC using a method defined by the MSC. During handover candidate
enquiry, the MSC requests the BSC to perform a specified number of
handovers from one specified cell to other specified cells. The MSC-
controlled handover, which is external from the BSC's point of view, is
started because of handover candidate enquiry, if necessary.

Interworking

Advanced Multilayer Handling

It is not recommended to use Advanced Multilayer Handling (AMH) BSC

initiated traffic reason handover (TRHO) at the same time and in the same
cell with an MSC-controlled TRHO. For more information, see Advanced
Multilayer Handling and RF Power Control and Handover Algorithm.

Dual Transfer Mode

MSC controlled traffic reason handover and BSC initiated traffic reason
handover are not allowed for DTM calls. For more information, see Dual
Transfer Mode.

DN9814214 # Nokia Siemens Networks 11 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

For an overview, see Overview of Traffic Reason Handover in BSC.

12 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Resource indication in Traffic Reason Handover

3 Resource indication in Traffic Reason

Handover

BTS BSC MSC

RF resource information from BTS to BSC

rf_resource_indication

rf_resource_indication

Resource indication from BSC to MSC

resource_request

resource_indication

resource_indication

Figure 1. RF resource indication procedure

The RF resource indication procedure informs the BSC of the interference

levels on idle channels of a transceiver (TRX). In the RF RESOURCE
INDICATION message, the BTS reports the interference level for every
channel that has been idle (not active) for a whole measurement period.
The RF RESOURCE INDICATION message is sent regularly with a rate
set by the O&M. The interference levels are also defined by the O&M. For
more information, see 3GPP 48.058: Base Station Controller - Base
Transceiver Station (BSC-BTS) Interface Layer 3 Specification.

The BSC receives the interference levels of the idle channels from the
BTS and stores them. The interference level information on idle channels
is used during traffic channel (TCH) allocation and resource indication in
the BSC.

DN9814214 # Nokia Siemens Networks 13 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

During resource indication, the BSC informs the MSC the number of radio
resources in a specified cell that are unused in the BSS and available for
traffic carrying purposes. The MSC determines the method by which the
BSC transfers the resource information to the MSC in the RESOURCE
REQUEST message. This message includes the following fields
according to which the cell information is transferred:

. periodicity
.
resource indication method
. cell identifier
.
extended resource indicator

The method defines the way the MSC is informed. The possible values
are:

. spontaneous indication
. one single indication
.
periodic indication according to the periodicity
. no indication expected

The resource indication procedure uses the connectionless services of the

signalling connection control part (SCCP). For more information, see
3GPP 48.008: Mobile Switching Centre - Base Station System (MSC-BSS)
Interface Layer 3 Specification.

The BSC acts as defined in the RESOURCE REQUEST message and

sends information on the free traffic channels in the RESOURCE
INDICATION message(s), if needed. The number of the free traffic
channels is indicated in two types of channels:

. full rate traffic channels

.
half rate traffic channels

As both channels are divided into five different interference bands, the
BSC sends ten items of information concerning the number of free traffic
channels of a specified cell. For example, if there is one full rate traffic
channel, which can also be used as two half rate traffic channels, the
number of free full rate traffic channels is one and the number of free half
rate traffic channels will be two. For more information, see 3GPP 48.008:
Mobile Switching Centre - Base Station System (MSC-BSS) Interface
Layer 3 Specification.

14 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Resource indication in Traffic Reason Handover

Resource indication procedure in Traffic Reason Handover

The BSC handles the Abis interface signalling, is responsible for the
interface management between the MSC and the BSC, maintains the BSS
cellular radio network configuration and parameter data in the database,
and controls the usage of radio channels and queueing.

The BSS Radio Network Configuration Database (BSDATA) contains the

configuration data and the control parameters of the radio network in the
BSS.

The BSC controls the resource indication procedure. It stores idle channel
measurements and passes the interference level information on the idle
channels to the MSC. The BSC receives RF radio resources from the BTS.

The BSC receives the RESOURCE REQUEST message from the MSC.
When the BSC receives the message, it acts according to the value of the
resource indication method element. The BSC forwards the information to
the MSC in the RESOURCE INDICATION message.

The value of the resource indication method element may be one of the
following:

1. Spontaneous indication

The BSC immediately sends one RESOURCE INDICATION

message to the MSC as an acknowledgement to the RESOURCE
REQUEST. If the cell load exceeds the limit defined for the BTS load,
the acknowledgement message includes resource information. In
other cases, the acknowledgement message does not include
resource information. After the acknowledgement, the BSC sends
the RESOURCE INDICATION message spontaneously to the MSC
every time the load conditions defined by the O&M are met in the
BSC for the considered cell.

The percentage that indicates the excess load of the cell is the same
as is used in handover algorithm. The percentage value is the BTS
object parameter BTS load threshold (BLT). This parameter is
also used in verifying spontaneous indication. The percentage
indicates the number of busy TCH channels divided by the total
number of working traffic channels in a cell.

The need to send resource indication using the spontaneous

indication method is periodically checked against periodicity. If the
cell load is greater than defined in the BTS parameters, the
RESOURCE INDICATION message is sent to the MSC. If the
periodicity is set to zero, the RESOURCE REQUEST is rejected.

DN9814214 # Nokia Siemens Networks 15 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

2. A single indication
The BSC will send a single RESOURCE INDICATION message
immediately to the MSC. If the extended resource indicator element
is not included in the RESOURCE REQUEST, the BSC stops any
resource information transfer related to a defined cell that may be in
progress.
If the extended resource indicator element is included in the
RESOURCE REQUEST, the subsequent mode is obeyed. The
subsequent mode field is decoded as follows:
.
Value 0 corresponds to the 'no indication expected' method.
After the single resource indication has been sent, the BSC
stops transferring resource information.
. Value 1 corresponds to the prior method. If the method prior to
the receipt of this indicator element was spontaneous or
periodic, the subsequent mode is spontaneous or periodic,
respectively. Otherwise the subsequent mode is 'no indication
expected'.
3. Periodic indication
The BSC immediately returns one RESOURCE INDICATION
message to the MSC and then periodically, according to the period
defined in the RESOURCE REQUEST message. If the period is set
to zero by the MSC, the BSC rejects the RESOURCE REQUEST
message.
4. No indication expected
The BSC immediately returns a single RESOURCE INDICATION
message to the MSC as an acknowledgement (the message does
not include the resource available element). The transferring of
resource information in a specified cell is disabled.

If the RESOURCE REQUEST message includes an extended resource

indicator element and in this element the total accessible resource request
has been set on, the RESOURCE INDICATION message(s) includes a
total resource accessible element. This total resource accessible element
gives the whole number of channels accessible for a given cell at the time
of the construction of the RESOURCE INDICATION message.

The BSC stays in the defined mode for a specified cell until it receives a
new RESOURCE REQUEST message for the same cell, or until the BSC
is reset. If the BSC is reset, the default is the 'no indication' mode. After the
reset, the MSC informs the BSC of a new method, if resource indication is
in use. The MSC may request simultaneously resource indications from
several cells under one BSC.

16 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Resource indication in Traffic Reason Handover

For an overview, see Overview of Traffic Reason Handover in BSC.

DN9814214 # Nokia Siemens Networks 17 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

18 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Handover candidate enquiry in Traffic Reason Handover

4 Handover candidate enquiry in Traffic

Reason Handover

BSC MSC

handover_candidate_enquiry

handover_required

...

handover_required

handover_candidate_response

Figure 2. Handover candidate enquiry procedure

The MSC uses this procedure to request handovers from the BSS to a
given number of MSs from one cell to other specified cells. The MSC
controls the possible handovers and the reason for a handover may be
excessive load in a cell.

Note

The MSC can perform only one handover candidate enquiry per one
specified cell at a time.

The procedure starts with the HANDOVER CANDIDATE ENQUIRY

message in which the MSC informs the BSC of the number of handovers
wanted. The MSC also informs the BSC of the cell from which the MSs are
to be transferred (source cell) and the cells into which the MSs are to be
handed over (target cells). The maximum number of adjacent cells in the
HANDOVER CANDIDATE ENQUIRY message in the BSC is 32.

DN9814214 # Nokia Siemens Networks 19 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

The BSC sends one HANDOVER REQUIRED message per an MS

candidate to the MSC using an appropriate signalling connection control
part (SCCP) connection. The message includes a list of candidate cells
and the reason for the handover (response to MSC invocation). The
reason for the handover makes the HANDOVER REQUIRED message
different from the normal HANDOVER REQUIRED message. The BSC
that has received the HANDOVER CANDIDATE ENQUIRY message acts
as the source BSC in the possible MSC controlled external handover(s).

When the BSC has sent all HANDOVER REQUIRED messages

generated by the enquiry, it sends the HANDOVER CANDIDATE
RESPONSE message to the MSC as an answer to the MSC's
HANDOVER CANDIDATE ENQUIRY message. In the HANDOVER
CANDIDATE RESPONSE message the BSC informs the MSC of the
number of HANDOVER REQUIRED messages that have been sent.

The MSC can perform only one handover candidate enquiry per cell at a
time. If the BSC receives a new enquiry for the specified cell while
processing the current enquiry, it ignores the new enquiry. The handover
candidate enquiry procedure uses the connectionless services of the
SCCP.

4.1 Traffic Reason Handover candidate enquiry

The BSC handles the Abis interface signalling, the uplink and downlink
measurements, and performs the power control and handover algorithm.
The BSC is also responsible for the interface management between the
MSC and the BSC. The BSC controls the handover attempts and controls
the usage of radio channels and queueing.

The handover candidate enquiry procedure consists of the following

subprocedures:

. candidate enquiry from the MSC

. cell selection procedure
. handover required procedure and external handover controlled by
the MSC
.
candidate response procedure

20 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Handover candidate enquiry in Traffic Reason Handover

Candidate enquiry from the MSC

The HANDOVER CANDIDATE ENQUIRY message comes from the MSC.

In this message, the MSC informs the BSC of the number of handovers
wanted. The MSC also informs the BSC of the cell from which the MSs are
to be transferred (source cell) and of the cells into which the MSC wants
the MSs to be handed over (target cells). If the BSC receives a new
enquiry for the specified cell while processing the current enquiry, it
ignores the new enquiry. The BSC keeps a record of the HANDOVER
REQUIRED messages that have been sent per one cell.

Cell selection procedure

The target cell selection in traffic reason handover is based on the cells
indicated by the MSC in the HANDOVER CANDIDATE ENQUIRY
message and on the radio link measurements (for more information, see
RF Power Control and Handover Algorithm). The BSC selects the
channels which have a call in progress in the requested cell. It decides
which MSs are to be handed over. Then it generates a target cell list based
on current radio interface measurements. The BSC compares the cell
identifier list it has received from the MSC and the target cell list, which has
just been created. The cells, which can be found on both lists, will be
included in the final target cell list to be sent to the MSC. If no cells can be
found on both lists at the same time, no handover attempt will be started.

The averaged signal strength of the target cells for traffic reason handover
has to exceed an adjacent-cell-specific signal level corrected with the
difference between maximum RF power and the maximum power of the
MS as follows.

If the adjacent cell is on GSM 800 or GSM 900 band:

av_rxlev_ncell (n) > TRHO_TARGET_LEVEL (n) +

Max (0, (MsTxPwrMaxGSM (ADJ) (n) - P))

If the adjacent cell is on GSM1800 or GSM1900 band:

av_rxlev_ncell (n) > TRHO_TARGET_LEVEL (n) +

Max (0, (MsTxPwrMaxGSM1x00 (ADJ) (n) - P))

The RXLEV_MIN has to be checked always, so the comparison equation 1

is needed (for more information, see RF Power Control and Handover
Algorithm). In the case of several target cells for handover, these cells are
sorted according to the following value.

If the adjacent cell is on GSM 800 or GSM 900 band:

DN9814214 # Nokia Siemens Networks 21 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

av_rxlev_ncell (n) - (TRHO_TARGET_LEVEL (n) +

Max (0, (MsTxPwrMaxGSM (ADJ) (n) - P)))

If the adjacent cell is on GSM1800 or GSM1900 band:

av_rxlev_ncell (n) - (TRHO_TARGET_LEVEL (n) +

Max (0, (MsTxPwrMaxGSM1x00 (ADJ) (n) - P)))

where av_rxlev_ncell is the averaged adjacent cell RX level.

In addition to the traffic reason handover, there is also a penalty time for
handovers due to the umbrella and power budget handovers in the
opposite direction. If the call is handed over from cell A to cell B due to the
traffic reason handover, it can be handed over back to cell A due to the
power budget after a certain period of time. The penalty time is 20 seconds
+min int between HO req (MIH) for the cell A defined in the handover
control parameters (for more information, see RF Power Control and
Handover Algorithm).

You can define the adjacent-cell-specific traffic reason handover target cell
level by using the Adjacent Cell Handling MML (EA MML command group)
adjacent-cell-specific parameter. The traffic reason target cell level TRHO
target level (TRHO) parameter is included in the adjacent cell
parameters in the BSC. The range of the parameter is from -109 to -47
dBm. The traffic reason handover cannot be applied to an adjacent cell
with the parameter value 'not used' (=0). The value of rxlev should be
bigger than TRHO target level.

Handover required procedure and external handover controlled by

the MSC

The handover attempt is similar to a regular external handover attempt,

except for the cause of the handover, which in this case is a response to
the MSC invocation. For each selected MS candidate, the BSC sends a
single HANDOVER REQUIRED message to the MSC using the
appropriate SCCP connections. For more information, see Handover
Signalling in BSC.

If the GSM timer T7 expires, the handover attempt is stopped and no new
attempt is started because of the handover candidate enquiry (HOCEQ) in
the selected call. After the BSC has sent the HANDOVER REQUIRED
message to the MSC, it increases the number of the HANDOVER
REQUIRED messages that have been sent. During a handover attempt
with the cause of handover candidate enquiry (response to the MSC
invocation), another handover attempt start based on the radio link
measurements of this connection is forbidden.

22 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en
 Handover candidate enquiry in Traffic Reason Handover

Candidate response procedure

When the BSC has sent all HANDOVER REQUIRED messages that have
been generated during the enquiry, it sends the HANDOVER CANDIDATE
RESPONSE message to the MSC. The BSC makes the decision on
ending the transaction. When the number of calls that have been handed
over is the same as in the request from the MSC (the number of the
HANDOVER REQUIRED messages is the same as the value of the
element 'Number of MSs'), the procedure ends. The handover candidate
enquiry procedure ends also, if a handover has been attempted to all calls
in the specified cell. The BSC sends the HANDOVER CANDIDATE
RESPONSE message to the MSC. This message contains the number of
the HANDOVER REQUIRED messages. The HANDOVER CANDIDATE
RESPONSE message is the answer of the BSC to the HANDOVER
CANDIDATE ENQUIRY message sent by the MSC.

4.2 Special cases in Traffic Reason Handover

candidate enquiry
Negative acknowledgement to new handover attempt

The BSC always knows if a handover is in progress for a specified call.

When the BSC receives a request for a handover attempt with the cause
'HOCEQ', it rejects the request. The BSC tries to select another call to
which a handover has not yet been attempted.

Cell emptying procedure

Cell emptying is an O&M defined procedure, in which all calls from a

specified cell are handed over to another cell or other cells. The BSC
always knows if the cell emptying is in progress, and it immediately sends
a response to the HOCEQ, where the value of the element 'Number of
MSs' is zero. This response is passed to the MSC via the BSC.

Minimum handover interval

If the minimum interval between two handover attempts or successful

handovers has not passed, the BSC tries to select another call to which a
handover has not yet been attempted.

DN9814214 # Nokia Siemens Networks 23 (24)

Issue 8-0 en
 Traffic Reason Handover in BSC

Not enough MSs to be handed over

If the BSC has selected all calls in progress in a specified cell for which the
handover has been attempted, and if the number of the HANDOVER
REQUIRED messages that have been sent is smaller than the number of
MSs to be handed over, the handover candidate enquiry procedure ends.
The BSC sends the HANDOVER CANDIDATE RESPONSE message to
the MSC.

For an overview, see Overview of Traffic Reason Handover in BSC

4.3 Counters in handover candidate enquiry

There are two statistical counters that are used during the handover
candidate enquiry:

.
001052 TRHO REQ

Updates the number of TRHOs requested by the MSC

.
001053 TRHO ENQUIRIES
Updates the number of BSC-initiated TRHOs

For more information, see 1 Traffic Measurement.

For an overview, see Overview of Traffic Reason Handover.

24 (24) # Nokia Siemens Networks DN9814214

Issue 8-0 en