Overview of Directed Retry in BSC

Directed Retry for Nokia DX 200 Base Station Controller (BSC) is a procedure used
when there is congestion in the network in the call set-up phase and the mobile
station (MS) is assigned to a traffic channel in a cell other than the serving cell.
By using the Directed Retry procedure, it is possible to avoid the loss of a call if the
serving cell is temporarily congested. The Directed Retry is triggered by an
assignment procedure and can be used either in a mobile-originating call (MOC) or
a mobile-terminating call (MTC) attempt.
The Directed Retry function is effective in mobile stations (MS), base station controllers
(BSC), and mobile services switching centres (MSC). This is a description of the
Directed Retry procedure in the BSC.
Directed Retry is an application software.
When the Directed Retry is enabled, the BSC may perform an inter-cell handover
from an SDCCH of the serving cell to a TCH of an adjacent cell if there are no
TCHs available in the serving cell. The parameter directed retry used (DR)
indicates whether a handover caused by the directed retry is enabled. The handover
is enabled when the value is 'yes'.
The following figure shows the process leading to the handover.

Figure: Directed Retry

Directed Retry (DR) handovers are functionally divided into three types:

BSC internal, inter-cell Directed Retry handover

BSC external Directed Retry handover (source cell side)

BSC external Directed Retry handover (target cell side)

BSC internal Directed Retry handover

The normal call set-up procedures are followed until the BSC receives an
ASSIGNMENT REQUEST message from the MSC. The BSC tries to allocate a traffic
channel (TCH) of a requested type for a BTS (for more information, see Radio Channel
Allocation). When traffic channels are congested, the Directed Retry procedure is
initiated.
At this point it is also possible to put the call attempt in a queue in the BTS, provided
that the following queueing conditions are met:

MSC allows queueing for this transaction

queueing procedure is active in the BTS (defined by a BSC user parameter)

call attempt queueing is active in the BTS (defined by a BSC user parameter)

queueing is possible and the item can be placed successfully in the BTS queue

For more information on queueing, see Radio Resource Pre-emption and Queuing in
BSC.
When the call is to be put in a queue, the BSC sends the QUEUEING INDICATION message
to the MSC to inform the MSC about the delay in the allocation of radio resources. The
message will only be sent when the real queueing procedure is initiated at this phase of
the call set-up procedure.
Call attempt queueing in the initial BTS during the creation of the candidate cell list
improves the possibility of obtaining the needed TCH quickly so that the call set-up
can be continued.
After the Directed Retry procedure has started, there is a period during which the DR
handover is not allowed. This period is allowed for the mobile station (MS) to decode
the base station identity code (BSIC) of the adjacent cells before the target cell
evaluation. If the radio resource queueing and the Directed Retry procedure are active
simultaneously in the serving cell, this period also increases the possibility of allocating
a TCH from the serving cell before the execution of the DR handover. The BSC can
start the target cell evaluation for the DR handover after the time supervision has expired.
The time supervision is controlled on a cell-by-cell basis with the parameter min time
limit directed retry (MIDR).

The BSC starts processing the measurement reports it has received from a MS. The
measurement reports contain the signal strength values of the adjacent cells when
the MS is in a standalone dedicated control channel (SDCCH). The procedure
makes a real-time target cell list which is required in the Directed Retry.
The min time limit directed retry (MIDR) parameter determines the period
starting from the assignment request (this message is sent from the MSC to the BSC in
order to request the BSC to allocate a radio resource) during which the target cell
evaluation for the directed retry procedure is not allowed. The BSC starts the target cell
evaluation procedure after this time supervision has expired. The range of the MIDR
parameter is from 0 to 14 seconds. The period is allowed for the mobile station to decode
the BSIC of the adjacent cells before the HO decision. The period also increases the
possibility of allocating a TCH from the serving cell before the execution of handover to
an adjacent cell.
The BSC is able to evaluate the target cells by two alternative methods. The method
is selected with the parameter directed retry method.The alternative values are the
following:
0 The measurement results of the adjacent cell must satisfy the basic equation (1)

before the directed retry procedure is possible. For more information, see Target
cell evaluation according to radio criteria.
The measurement results of the adjacent cell must satisfy both the basic equation
1
(1) and the following equation (4) before the directed retry is possible.
EQUATION 4.
AV_RXLEV_NCELL(n) > DRThreshold(n)

The parameter Directed Retry threshold (DRT) (set for each of the 32 adjacent
cells) is the level which the signal level AV_RXLEV_NCELL(n) of the adjacent cell
(n) must exceed before the directed retry to the adjacent cell (n) is possible. The
range is from -110 dBm to -47 dBm.
The creation procedure of a handover candidate cell list is controlled with a timer. The
BSC continues the target cell evaluation for the DR handover until it finds a target cell
for the DR handover or the maximum time allowed for start of the DR handover expires.
The time supervision is controlled on a cell-by-cell basis with the parameter max time
limit directed retry (MADR).

The BSC may monitor the signal level of the adjacent cells, and perform the
handover from a dedicated control channel until the maximum period allowed for
the directed retry procedure expires. The parameter max time limit directed
retry (MADR) determines the maximum time period starting from the assignment
request during which the target cell evaluation for the directed retry procedure is
allowed. The range of the parameter from 1 to 15 seconds. If the call cannot be
handed over from the dedicated control channel during the prescribed period, the BSC
discontinues the call setup procedure: the possibly ongoing queueing is terminated and
the call attempt is cleared. Note that once the queuing has been started, it is no longer
dependent on the value of the parameter max time limit directed retry
(MADR). The queuing continues until the time set for the parameter time limit
call (TLC) is exceeded, after which the call attempt is cleared. If queuing has not
been started, the call attempt is cleared after the MADR value is exceeded.
Note also that if queueing has been started, the timer T10 is extended by the value of
either the parameter MADR or TLC, depending on which parameter has the larger value.
That is, when queueing is ongoing, T10 equals the value of the old T10 timer plus the
value of MADR or TLC.
Note
The target cells for the directed retry procedure are ranked only according
to radio link properties. Priority levels are not used.
Note
Radio resource queueing increases the possibility of allocating a TCH from
the serving cell before the maximum period allowed for the directed retry
procedure expires (for more information, see Radio Resource Pre-emption
and Queueing). If a TCH of the serving cell can be assigned for the call, the
BSC discontinues the Directed Retry Procedure.

When the BSC has successfully identified the new target cell, the possibly ongoing
queueing is terminated in the BTS. When a traffic channel has been successfully
allocated in the new target cell, the BSC sends a HANDOVER COMMAND message to the MS
identifying both the target cell and the channel type. For more information, see Handover
Signalling in BSC.
When the BSC receives a HANDOVER COMPLETE message from the MS, it sends an
ASSIGNMENT COMPLETE message to the MSC. This message informs the MSC of a
successful Directed Retry procedure during the call set-up. It also informs the MSC of a
new cell identity.
When Directed Retry is used in a mobile-terminating call, the MS sends the message
ALERT to the BTS after the message HANDOVER COMPLETE. To be able to send the ALERT
message autonomously, the MS has to be aware that the Directed Retry procedure is
performed.
After a successful Directed Retry procedure, the SDCCH in the initial cell is released.
The main signalling during the BSC internal Directed Retry handover is presented in the
figure BSC internal Directed Retry handover (mobile-terminating call with Directed
Retry; non-synchronized).

Figure: BSC internal Directed Retry handover (mobile-terminating call with Directed
Retry; non-synchronized)

BSC external Directed Retry handover on the source cell side:

When the BSC has successfully identified a new target cell, the possibly ongoing
queueing is terminated in the initial BTS. If the chosen new target cell belongs to an
adjacent BSC, the current BSC sends a HANDOVER REQUIRED message to the MSC with
the cause 'Directed Retry'.
The main signalling in the BSC external Directed Retry handover in the source BSC is
illustrated in the figure BSC external Directed Retry handover (mobile-terminating call
on source cell side).

BSC external Directed Retry handover on the target cell side

The MSC sends a HANDOVER REQUEST message with the cause 'Directed Retry' to the
target side BSC in the external Directed Retry handover. The cause value does not change
the normal handover signalling procedures in the target BSC, rather it is used for
statistical purposes.
When the BSC receives a HANDOVER COMPLETE message from the MS, it forwards the
message to the MSC which interprets the message as ASSIGNMENT COMPLETE. This is
how the BSC informs the MSC of a successful Directed Retry during the call set-up
procedure.
In a mobile-terminating call with Directed Retry, the MS has to be aware of the started
Directed Retry after the handover in order to be able to send the message ALERT
autonomously after the message HANDOVER COMPLETE to the BTS.
Main signalling in the BSC external Directed Retry handover in the target BSC is
presented in the figure BSC external Directed Retry handover (mobile-terminating call
on target cell side).

Normal handover during assignment

A stand-alone dedicated control channel (SDCCH) handover cannot be started during the
assignment (Directed Retry) procedure. If the Directed Retry has been started, the normal
handover procedure cannot be started.
In this procedure, the criteria for selecting the possible candidate cells are not as strict as
in the normal handover algorithm analysis. The following items are taken into account
when creating the candidate list for Directed Retry handover:

The RX signal level compared to the threshold value defined by the parameter RX
lev min cell (SL)

the MS classmark

the maximum power level in the cell

If the Directed Retry threshold method is in use, the minimum threshold value of the RX
signal level is also taken into account when creating the candidate cell list. The minimum
threshold value of the RX signal level is defined with the Directed Retry threshold
(DRT) parameter. If the value of the Directed Retry threshold parameter has been set
below the adjacent cell parameter RX lev min cell (SL), the measured signal strength
is compared with the RX lev min cell instead.
If there are no neighbouring cells with satisfactory radio quality, the creation of a
candidate list is not possible and therefore it is not possible to continue the started
Directed Retry.
Unsuccessful creation of a target cell list during DR
A time limit is given for the BSC handover algorithm that processes the measurement
reports to make a real-time target cell list for Directed Retry. The user can change the
time value parameter max time limit directed retry (MADR) with MML
commands. The parameter is controlled by the BSC.
If no suitable candidate can be located within the time limit, the possibly ongoing
queueing is continued until timer T10 expires.
Note
The value of the timer max time limit directed retry (MADR) should
be smaller than the value of the timer T10. If the MADR value is more than
the T10 value, the call is released after the T10 timer has stopped and the
MADR is still ticking
Successful queueing during Directed Retry
If queueing is in progress while the BSC is processing measurement reports to make a
real-time target cell list for Directed Retry, a suitable busy traffic channel may be released
in the BTS. In this case, during the Directed Retry procedure, the creation of the
candidate cell list is terminated and the call attempt is successfully handled in the initial
BTS.
Queueing time-out during DR procedure
If queueing is in progress while the BSC is processing measurement reports to make a
real-time target cell list for Directed Retry, a queueing time-out may occur. In this case,
during the Directed Retry procedure, the BSC does not start clearing call attempts
immediately, but only after the time allowed for creating a candidate cell list has passed.

Special cases in BSC internal Directed Retry handover

Radio resource allocation in Directed Retry handover
As in the normal BSC internal handover, it is possible to send a maximum of 16 chosen
BTSs as target BTSs to be used in the channel allocation algorithm also in a Directed
Retry. These BTSs are sent in a single allocation request message to the BSC. This
increases the possibility of finding a new cell with available radio resources. For more
information, see Radio Channel Allocation.
Queueing possibility of Directed Retry handover in the new cell
No queueing is allowed in the new target BTS after the Directed Retry procedure has
been started. The BSC starts a clearing procedure if no TCH can be allocated in the target
cell during the BSC internal Directed Retry handover.
Unsuccessful entering of an MS to a new traffic channel
An MS may fail to enter the new traffic channel in the new target cell when the BSC
internal Directed Retry procedure is in progress. In this case the MS returns to the old
radio resource, that is, to the SDCCH in the initial BTS, and the BSC starts to clear the
Directed Retry attempt.
If the timer T8 expires, the Directed Retry attempt is cleared. This takes place if
HANDOVER COMPLETED message has not been received from the MS after the HANDOVER
COMMAND message during supervision.

Special cases of BSC external Directed Retry handover

Handover type reselection due to Directed Retry
If all the BSSs in the network do not support Directed Retry, the parameter disable
external DR (DEXDR) must be set in the BSC.
If the parameter disable external DR is set in the serving BSC and the first candidate
cell belongs to another BSC, the BSC searches through the candidate cell list for cells
belonging to the serving BSC. This search creates a new candidate cell list, which is then
used for attempting a BSC-internal Directed Retry.
Unsuccessful entering of an MS to a new TCH
It is possible that an MS fails to enter the new TCH in a new target cell while the BSC
external Directed Retry procedure is in progress. In this case the MS returns to the old
radio resource, that is, to the SDCCH in the initial BTS. In this situation the MSC starts
to clear the Directed Retry attempt.

ther instances of unsuccessful Directed Retry

An MS can clear a call during a BSC external Directed Retry handover attempt. In this
case, all allocated resources are released and the attempt is cleared.
The timer T7 supervises the responses to the HANDOVER REQUIRED message from the
MSC. If this timer expires, the message is not repeated during the Directed Retry
procedure. The BSC starts a clearing procedure.
If the message CONNECTION FAILURE INDICATION arrives from the old channel before
the message HANDOVER COMMAND, or if it arrives from the new BTS, the BSC starts to
clear the Directed Retry attempt.
If the timer T8 expires, the Directed Retry attempt is cleared. This takes place if the
message HANDOVER COMMAND has been sent, but neither HANDOVER FAILURE message
from the MS nor CLEAR COMMAND message from the MSC is received during supervision.

Before testing, make sure that the internal handover is not disabled:
The value of the parameter disable internal HO should be NO. Output the value with
the EEO MML command.
The value of the parameter can be changed with the EEQ MML command.
ZEEO:MIS;
ZEEQ:DINHO=N;

If SDCCH handover is supported, make sure that it is disabled:

ZEHG:BTS=1:ESD=N;

The SDCCH handovers can only be disabled because of the testing environment. If the
SDCCH handover criteria are fulfilled before the Directed Retry handover criteria, the
SDCCH handover takes place and if the Directed Retry handover criteria are fulfilled
before the SDCCH handover criteria, Directed Retry handover takes place. In a live
environment, the SDCCH handover and Directed Retry can be used simultaneously.

directed retry used (DR)

Parameter name

Directed Retry Used

Abbreviated name

drInUse

Managed object

BTS

Parameter group

Multiplicity

Description

With this parameter you define if the directed retry feature is

in use in the cell.

Range and step

directed retry is not in use (N) (0), directed retry is in use (Y)
(1)
gui ==> internal

Formula for getting

internal value

directed retry is not in use (N) ==> 0

directed retry is in use (Y) ==> 1

Default value

directed retry is not in use (N) (0)

Default value notes

Required on Creation

optional

Related functions

Modification

Online

Related parameters

Parameter relationships

Related options
Related features

Directed Retry (1) (optional)

RACApp <-> RAC

Planner <-> RAC

Interfaces

References

RAC <-> Optimizer

RAC <-> BSC

GSM reference: ETS 300 590 (GSM 08.08)

MML Commands

EQF, EQO

MML Abbreviated Name

DR

MML Full Name

directed retry used

Segment Level Parameter

true

DB Name

base_station.dr_in_use

File based provisioning

supported

true

disable external DR (DEXDR)

Parameter name

Disable External DR

Abbreviated name

disableExtDr

Managed object

BSC

Parameter group

Multiplicity

Description

With this parameter you disable or enable the external directed

retry handovers.

Range and step

0 (enable external directed retry handovers (N)), 1 (disable

external directed retry handovers (Y))
gui ==> internal

Formula for getting

internal value

enable external directed retry handovers (N) ==> 0

disable external directed retry handovers (Y) ==> 1

Default value

enable external directed retry handovers (N) (0)

Default value notes

Required on Creation

mandatory

Related functions

Modification

Online

Related parameters

Parameter relationships Related options

Related features

Interfaces

References

MML Commands

EEQ, EEO

MML Abbreviated Name DEXDR

MML Full Name

disable external DR

DB Name

bsc.disable_ext_dr

File based provisioning true

supported

Functionality of Intelligent Directed Retry

Cells in MCN/GSM network
There are two types of cells in the MCN/GSM network:
1. GSM type
o serves subscribers who have GSM classmarks when service separation is
based on classmarks (typically classmarks 1-4)
o

serves subscribers who have a GSM subscriber priority when separation is

based on priority.

2. MCN type
o

serves subscribers of all classes when classmark based service separation

is used (typically classmarks 1-5)

serves both subscribers with a GSM priority and subscribers with an MCN
priority when separation is based on priority.

In this context, the term "serves" means that an MS is allowed to camp on the cell and
that the TCH required to support a call is provided by this cell or an adjacent/overlaid
cell.
The operation during call set-up ensures that an MS is only camped on a cell which is
able to serve. The selection of the most suitable cell is based on measurement reports
from the MS and from the BTS (for more information, see RF Power Control and
Handover Algorithm). Both intra-BSC IDR and inter-BSC IDR are supported.

IDR decision algorithm

Intelligent directed retry (IDR) divides cells into GSM cells and MCN cells. Mobiles are
divided into GSM mobiles and MCN mobiles. If IDR is not in use in the BSC, all cells
are handled as GSM cells and all mobiles as GSM mobiles.
The principle is that IDR is applied only to MCN mobiles and DR only to GSM mobiles.
Most commonly both IDR and DR are activated. However, they can be turned on and off
separately. If, for instance, IDR is in use in the BSC, DR should also be activated,
because otherwise GSM subscribers remain without DR.
An attempt is first made to allocate the TCH from an accessed cell. If the allocation does
not succeed, allocation is attempted from specified adjacent cells. If the TCH allocation
from adjacent cell fails, the call is rejected. MCN cells can be target cells in the IDR only,
whereas in the DR both MCN cells and GSM cells can be target cells.

The decision is made as follows (in this example both IDR and DR are in use in the
BSC):
Ch Req from MS
IMM ASS to DCCH of accessed cell
MS sends RXLEV measurements of adjacent cells
? Is TCH available on accessed cell
Yes -> Allocate TCH on accessed cell
No -> ? Classmark check or Priority check
MCN -> ? Is IDR in use in this BTS
Yes -> IDR start, create new cell list of MCN cells
No -> reject call
GSM -> ? Is DR in use in this BTS
Yes -> DR start, create new cell list of all adjacent
cells
No -> reject call

An IDR & DR target cell list for handover consists of a maximum of 16 cells. The
selection of adjacent cells is based on radio interface measurements, MS classmark or
priority level, and BTS and adjacent cell parameters, including cell type. The selected
adjacent cells are sorted according to imperative handover criteria.