Load handover Load Accept Threshold

LoadAccThres:

Meaning: Threshold for allowing MSs to hand over from other cells to the cell through load-based
handovers. MSs are allowed to hand over from other cells to the cell through load-based handovers if
any of the following conditions is met:
1. The cell load is lower than or equal to this threshold when HOCTRLSWITCH is set to HOALGORITHM1
and LOADHOAD is set to YES in the SET GCELLHOBASIC command.
2. The cell load is lower than this threshold in other cases.
If neither of the preceding conditions is met, MSs are not allowed to hand over from other cells to the
cell through load-based handovers.
GUI Value Range: 0~100
Unit: %
Actual Value Range: 0~100
MML Default Value: 80
Recommended Value: 80
Parameter Relationship:
-Others:
1. When the cell is a 2G external cell, this parameter is valid only if [GCELLHOAD:OutBscLoadHoEn] is set
to YES(Yes).
When [GCELLHOAD:LOADHOHYSTADAPEN] is set to YES(Yes), this parameter is only used for decisions
on load-based handovers at the same layer.
2. When the cell is a 3G external cell, this parameter is valid only if either of the following conditions is
met:[GCELLHOBASIC:INTERRATOUTBSCHOEN] and [GCELLHOINTERRATLDB:OutSysLoadHoEn] are set to
YES(Yes).[GCELLHOINTERRATLDB:InterRatServiceLoadHoSwitch] is not set to OFF(Off).
3. When the cell is under the current BSC, this parameter is valid only if [GCELLHOBASIC:LoadHoEn] is
set to YES(Yes). When [GCELLHOAD:LOADHOHYSTADAPEN] is set to YES(Yes), this parameter is only used
for decisions on load-based handovers at the same layer.
4. The value of this parameter must be smaller than [GCELLHOAD:TRIGTHRES].
Service Interrupted After Modification: No (And no impact on the UE in idle mode)
Impact on Network Performance: If this parameter is set to a small value, some MSs cannot be handed
over to the corresponding target cells, worsening congestion in the surrounding cells with heavy traffic.
If this parameter is set to a large value, causing traffic overload in corresponding cells.

Handover Problems Due to Incorrect Data Configurations

This section describes how to troubleshoot handover problems due to incorrect data configurations.

Symptom

 The signal quality in the serving cell is poor. Handovers often cannot be initiated, and the call drop
rate is high.
 The signal level and quality in the neighboring cell is slightly better than the serving cell. Handovers
are performed frequently, which deteriorates voice quality and increases the number of call drops.
  If the P/N criterion is set inappropriately, PBGT handovers often fail, and the handover success rate
is less than 98%.

Background Information

 Impact of handover threshold settings

Edge handovers are performed when the receive level is continuously less than the value of
Edge HO UL RX_LEV Threshold or Edge HO DL RX_LEV Threshold during a specified
period. Generally, Edge HO UL RX_LEV Threshold is set to 10, and Edge HO DL RX_LEV
Threshold is set to 20 in handover algorithm I or 15 in handover algorithm II. If Edge HO UL
RX_LEV Threshold or Edge HO DL RX_LEV Threshold is set too low, a handover cannot be
initiated when it should be. If Edge HO UL RX_LEV Threshold or Edge HO DL RX_LEV
Threshold is set too high, handovers are performed frequently, which reduces the cell coverage
area and leads to call drops. Therefore, set Edge HO UL RX_LEV Threshold and Edge HO DL
RX_LEV Threshold to appropriate values based on the cell coverage. Changing the value of
Edge HO UL RX_LEV Threshold or Edge HO DL RX_LEV Threshold can change the
coverage area of a cell. If the serving cell coverage is weak, increase the value of Edge HO UL
RX_LEV Threshold or Edge HO DL RX_LEV Threshold by 2 dB to 5 dB to expedite
handovers to a suitable neighboring cell.
 Impact of neighboring cell configurations
If neighboring relationships are not configured or configured incorrectly even though the signal
level of a neighboring cell is high, the MS may report incorrect neighboring cell information or
may not report any neighboring cell information. As a result, the MS cannot perform a handover
or may have difficulty performing a handover.
 Incorrect setting of NCC Permitted
NCC Permitted is contained in system information 2 and 6. An MS measures only the signal
level of cells with NCC Permitted set to 1. If NCC Permitted for a serving cell is set incorrectly,
an MS cannot hand over to a neighboring cell. NCC Permitted consists of 8 bits, with bit 7 being
the most significant bit and bit 0 being the least significant bit. Each bit corresponds to an NCC
(0 to 7).
 Inappropriate data configurations for cells with repeaters or RXU co-cells
Inappropriate data configurations for cells with repeaters or RXU co-cells may lead to
asynchronous handover failures.
 Impact of hysteresis configurations
The difference between the signal level of a candidate cell and that of the serving cell must be
greater than the handover hysteresis. Therefore, a large handover hysteresis may lead to
handover failures. If the serving cell coverage is weak, decrease the handover hysteresis by 1 to
2 dB to expedite handovers to a suitable neighboring cell. If coverage overlap exists, increase
the handover hysteresis by 1 to 2 dB.
 Inappropriate configuration of optimal cell measurement time
During common handovers, an MS selects the target cell according to the N/P criteria. That is,
the MS selects the optimal cell for P seconds in N seconds as the target cell. If two cells are the
optimal cell alternatively, a handover may fail because the handover algorithm cannot determine
the target cell. In this case, reduce the optimal cell measurement time by adjusting the values of
N and P and ensure that the handover decision is more sensitive to level changes. Handover
failures may also occur when the receive level of a moving MS fluctuates significantly in a
serving cell with complex topography, which makes it difficult for the target cell to meet the N/P
criteria. The following are some N/P parameters:
  Handover algorithm II Edge HO Watch Time
 Handover algorithm II Edge HO Valid Time
 Handover algorithm I Edge HO Watch Time
 Handover algorithm I Edge HO Valid Time
 Intracell F-H HO Stat Time
 Intracell F-H HO Last Time

Location Procedure

Figure 1 shows the procedure for locating handover problems due to incorrect data configurations.
Figure 1 Procedure for locating handover problems due to incorrect data configurations

Troubleshooting Procedure

1. Run the MML command LST GCELLHO2GBA2 to check whether neighboring cells are
configured correctly, especially whether any neighboring cells are missing based on
measurement reports, onsite network planning data, and engineering parameter settings.
Then, run the MML command LST GCELLIDLEBASIC to check whether NCC permitted for
the serving cell is set correctly.
 If yes (see Background Information), go to Step 2.
  If no, adjust neighboring cell configurations, or run the MML command SET
GCELLIDLEBASIC to set NCC permitted to its correct value by referring to Background
Information. Then, check whether the handover problem is resolved.
 If yes, no further action is required.
 If no, go to Step 2.
2. Check whether the problem cell is configured with a repeater or an RXU co-cell based on the
network plan, data configurations, and engineering parameter settings.
 If no, go to Step 3.
 If yes, run the MML command LST GCELLSOFT and check whether Directly Magnifier
BTS Flag or Co-Cell Switch is set to Yes.
 If yes, go to 3.
 If no, run the MML command SET GCELLSOFT to set Directly Magnifier BTS
Flag or Co-Cell Switch to Yes. Then, check whether the handover problem is
resolved.
 If yes, no further action is required.
 If no, go to Step 3.
3. Run the MML command LST GCELLHOBASIC to check whether Edge HO UL RX_LEV
Threshold and Edge HO DL RX_LEV Threshold are set correctly by referring to Background
Information.
 If yes, go to Step 4.
 If no, run the MML command SET GCELLHOBASIC to change the value. Then, check
whether the handover problem is resolved.
 If yes, no further action is required.
 If no, go to Step 4.
4. Run the MML command LST GCELLHOBASIC to check whether Inter-layer HO Hysteresis
is set correctly by referring to Background Information.
 If yes, go to Step 5.
 If no, run the MML command SET GCELLHOBASIC to change the value. Then, check
whether the handover problem is resolved.
 If yes, no further action is required.
 If no, go to Step 5.
5. Run the MML command LST GCELLHOBASIC to check whether parameters relevant to
optimal cell measurement time such as Handover algorithm II Edge HO Watch Time and
Handover algorithm II Edge HO Valid Time are set correctly by referring to Background
Information.
 If yes, go to Step 6.
 If no, run the MML command SET GCELLHOBASIC to change the value. Then, check
whether the handover problem is resolved.
 If yes, no further action is required.
 If no, go to Step 6.
 6. Go to Procedure for Locating Handover Problems.
Typical Case

Symptom
The handover success rates for some cells are low. The outgoing handovers in these cells are normal,
but the number of incoming cell handovers is 0.
Cause Analysis
Possible causes for this problem are: incorrect data configurations, interference.
Troubleshooting Procedure
1. Check whether the neighboring cells of the problem cell work on the same frequency and have
the same BSIC.
No such neighboring cells exist.
2. Check whether the BCCH frequency used by the problem cell has been changed.
The BCCH frequency has not been changed.
3. Check whether there is strong interference for the problem cell.
The traffic statistics show that the interference bands are normal and that there are a small
number of call drops and handovers due to poor voice quality in the problem cell. Even if there
is strong interference for the problem cell, at least one handover can be performed
successfully. Therefore, the handover problem is not caused by interference.
4. Check whether the TRXs are operating properly.
The TRXs are operating properly.
5. Check the data configurations for the problem cell.
The BSIC of the problem cell has been changed, but the corresponding data of the neighboring
cells has not been changed. As a result, the BSC cannot locate the target cell after initiating a
handover request.
6. Change the corresponding data of all neighboring cells. The handover problem is resolved.
Parent topic: Handover Problems