1.

Directed Retry

The feature is meant to improve the accessibility of the network and prevent blocked
calls.
1.1.1

Description

Directed retry is an optional feature which re-directs new traffic when a Cell is
congested resulting in the new call to be moved to the next most suitable Cell. It allows
for the handover of a Mobile Station (MS) from an SDCCH of one Cell directly to a
traffic channel (TCH) of another Cell.

Figure 1: Directed Retry procedure applied when original Cell congested

The Directed Retry algorithm will be activated only during call set up, when a mobile is
already on SDCCH, requires a TCH and all TCH on the cell are busy.
The mobile is then put on the TCH queue.
-If TCH is getting available on the cell by the end of the DR process, then the DR
process is aborted and is allocated the TCH available.
-Otherwise, the mobile will be move onto a TCH of a neighbour cell, for which
the 2 criteria about handover on congestion (see the next feature Directed Retry
Alternative) are valid.
1. Rxlev (neighbour X) > rxlev_min_ncell
rxlev_min_ncell is defined in the Data Base for this neighbour X.
2. PBGT (neighbour X) - congest_ho_margin > 0

If all attempts at directed retry fail or no valid neighbour are reported then the TCH
request remains queued for the remainder of the relevant queuing timer (bssmap_t11).
1.1.2

Database Configuration

1.1.2.1 dr_preference parameter

This parameter determines whether the directed retry procedures are disabled or enabled.
This action of this parameter concerns a BSS.
Valid Range: 0 (disabled), 1 (enabled)
Default Value: 0
1.1.2.2 dr_standard_congest parameter
This parameter determines if the standard directed retry congestion procedure is enabled
in the cell. The procedure initiates a handover if possible for a call needing a TCH in the
case of congestion.
Valid Range: 0 (disabled), 1 (enabled)
Default Value: 0
1.1.2.3 dr_ho_during_assign parameter
This parameter determines if a handover will be handled during an assignment procedure
(set to 1) or whether the HO will occur at the end of the assignment procedure.
This refers to the need for a HO due to Radio Frequency reasons when a call is being
queued. If the call is queued and RF conditions change such that a normal HO is required
e.g. better cell or RxQual or RxLev then a HO is carried out.
This parameter concerns the cell where DR is activated.
Valid Range: 0 (disabled), 1 (enabled)
Default Value: 0
1.1.2.4 dr_chan_mode_modify parameter
This parameter determines if the channel mode modify procedure will follow a successful
handover of a Phase 1 MS in which the channel mode changed to full rate speech.
This action of this parameter concerns a BSS.
Valid Range: 0 (disabled), 1 (enabled)
Default Value: 0
1.1.2.5 dr_allowed parameter
This parameter enables the Directed Retry option, if set to 1, otherwise set to 0.
This is a per neighbour attribute for external neighbours only.
Valid Range: 0 (disabled), 1 (enabled)
Default Value: 1
1.1.2.6 congest_ho_margin parameter
This per neighbour parameter is used in the case of a congestion handover. To make it
easier to handover to this neighbour in the case of congestion in the current cell, this
parameter value should be less that the value of the handover margin(s)

To disable congestion handovers to this neighbour, set the congestion handover margin to
the maximum value +63.
In addition as the congest_ho_margin is usually set to negative values or 0 to facilitate
DR handovers to neighbours with free resources. A positive congest_ho_margin would
mean that the chances of finding a suitable neighbour would be minimal and the
congestion situation on the serving cell couldn't be resolved effectively.
congest_ho_margin is a per neighbour parameter.
Valid Range: 63dB to 63dB Default Value: None
1.2

Congestion Relief and Congestion Relief Enhanced

They are two different types of Congestion relief. The standard one called Congestion
relief (which is called sometime Directed Retry Alternative) and the latest one available
from GSR4, the Enhanced Congestion Relief. The section will give only an overview of
these features.
1.2.1

Description

1.2.1.1 Congestion Relief

Congestion relief is an optional feature which is available as an alternative to Directed
retry for the case of a congested cell. This feature differs in that it chooses the best
candidate from all existing calls in the cell to be moved to the alternate cell thus freeing
TCHs in the congested cell. This can result in better overall system quality compared to
Directed retry because the best handover candidate is chosen instead of the candidate
requesting a TCH.

Figure 2: Alternative congestion relief procedure applied when original Cell congested

If a call (MSa on the figure) needing a TCH has not had the chance to report a neighbour
that is a good handover candidate, it may be better to handover an established call (MSb
on the figure). This frees up TCHs in the congested cell (cell 1 on the figure). The
maximum number of calls handed over can be either of the following:

The number of queued requests in the congested cell.

The number of calls meeting the congestion handover criteria in the congested
cell. This has the potential to relieve congestion on a bigger scale than the
previous option.
The hand over criteria are as for Directed Retry feature:
1. Rxlev (neighbour X) > rxlev_min_ncell
rxlev_min_ncell is defined in the Data Base for this neighbour X.
2. PBGT (neighbour X) - cr_ho_margin > 0

1.2.1.2 Enhanced Congestion Relief

Once a cell reaches its operator-defined congestion threshold, existing traffic is optimally
handed over to non-congested cells, thereby relieving the condition and clearing capacity
for new calls or originations. By way of comparison, Directed Retry forces originations
in congested cells to be `directed' immediately to other cells which, on many occasions,
can result in poor cell assignments and poor call quality (see chapter 3.3).
Advanced Congestion Relief defines new handover procedures to select active calls to be
handed over to relieve congestion in the cell.
These new procedures take the form of expanding the decision process for handover to
include the state of congestion at the target cell and incorporate the added dimension of
time over which the decision is to be implemented. For example, target cells will not
accept a congestion relief handover that puts itself into a congested state, resulting in
further congestion procedures being invoked. Excessive handovers are therefore
eliminated.
A source cell will not attempt a congestion relief handover, for a period of time, to a
target cell that had rejected a previous handover attempt. The time period may be
specified by the operator or as a default, may be set to the time between the onset and
completion of a congestion relief procedure. This protects the system from experiencing
excessive handover attempts, as well as resulting in a reduction in signalling.
1.2.2

Database Configuration

The main O&M impacts of this feature are to the BSS database with several BSS, Cell
and Neighbour parameters, some of which are shared with the Directed Retry feature.

1.2.2.1 HO_exist_congest parameter

This parameter determines if attempts to handover existing calls on a TCH will be
initiated in the case of an MS needing a TCH when there are none available in that cell.
This parameter indicates either to attempt to handover as many calls as the number of
queued assignment requests (if set to 1) or attempt to handover as many calls as meet the
congestion handover criteria (if set to 2). It concerns a cell.
Valid Range: 0,1 or 2
Default Value: 0
If set to 0, the functionality is disabled.
1.2.2.2 Congest_HO_Margin parameter
This parameter is used in the case of a congestion handover. To make it easier to
handover to this neighbour in the case of congestion in the current cell, this parameter
value should be less that the value of the handover margin(s).
To disable congestion handovers to this neighbour, set the congestion handover margin to
the maximum value.
Valid Range: 63dB to 63dB
Default Value: None
1.2.2.3 tch_congest_prevent_thres parameter
This per cell parameter specifies the level of overall TCH utilisation by any MS in a
given Cell, at which the Congestion Relief procedure is initiated. The parameter is
expressed as a percentage.
Valid Range: 0 to 101
Default Value: 100
If set to 0, the congestion relief is disabled. If set to 101, the congestion relief process
starts when all available TCHs are in use, and at least one more TCH is requested.
[mb_tch_congest_thres must be less than or equal to tch_congest_prevent_thres.]

The last 3 parameters concern the Enhanced Congestion Relief :

1.2.2.4 congest_at_source parameter
Used to control how a given cell behaves should it be unable to force a given imperative
handover
Valid Range: 0,1
Default Value: 1
If set to 0: The system takes no actions if a given candidate rejects a handover.
If set to 1: if an imperative handover is needed, the source Cell retries candidates which
were previously unable to serve the handover request.
1.2.2.5 congest_at_target parameter
Used to control how a given cell behaves should it reject a handover request (either an
imperative or congestion relief attempt).
Valid Range: 0,1
Default Value: 1
If set to 0: The system will take no action if the Cell reject a handover request.

If set to 1: The system will invoke Congestion Relief procedures if this cell rejects a
handover request.

A parameter about redirecting extra load traffic onto the multiband :

1.2.2.6 mb_tch_congest_thres parameter
Used to control the percentage point at which Multiband Mobile Stations will start to be
redirected to the preferred band.
Valid Range: 1 to 101
Default Value: 100
If set to 101, there are no resources left to allocate.