1.

IUO problem1
Detail description:
The setting of Assign-Optimum-Level Thrsh. takes effect when the user selects the option of
system optimization. Suppose the Assign-Optimum-Level Thrsh. is 18, will the MS prefer the
overlaid subcell when the MS receiving level is higher than -92dBm, and the underlaid subcell if
otherwise?
For any value configured for Assign-Optimum-Level Thrsh., the underlaid subcell is always
congested, why?
Reply:
If the Assign-Optimum-Level Thrsh. is set as 18, the overlaid subcell is preferred if the uplink
level in SDCCH measurement report is greater than -92dBm, and the underlaid subcell is
preferred if otherwise. If an MS keeps on selecting the underlaid subcell, the uplink signals may
be too weak. In this case, view the result of the measurement task uplink and downlink balance
performance measurementand check whether there are any hardware faults.
Inconsistency between the receiving level threshold and the assignment preferable range may
lead to frequent handovers between the overlaid subcell and the underlaid subcell, thus causing
congestion in the underlaid subcell.

2. IUO problem2
Detail description:
1. For the configuration of preferring underlaid subcell, does it mean an MS will select the
underlaid subcell first no matter how higher the receiving level is, and it selects the
overlaid subcell only when the underlaid subcell is busy?
2. For the configuration of preferring overlaid subcell, does it mean an MS will select the
overlaid subcell first no matter how higher the receiving level is, and it selects the
underlaid subcell only when the overlaid subcell is busy?
3. For the configuration of no preferment, does it mean an MS prefers the overlaid subcell
within coverage of the overlaid subcell, and selects the underlaid subcell only when the
overlaid subcell is congested?
Reply:
1. Yes. It is true.
2. Yes. It is true.
3. In this case, channels are allocated based on channel allocation algorithm.I or II.

3. IUO Problem3
Detail description:
What is the signal intensity difference between the overlaid subcell and the underlaid subcell?
What will happen if this parameter is not configured correctly?
Reply:
Since the differences in transmission power and path loss between the overlaid subcell and the

underlaid subcell may lead to differences in receiving signal intensity accordingly. The value set
for this parameter indicates a power compensation for the overlaid subcell.
The configuration of this parameter must be accurate since it is the level of the overlaid subcell
after power compensation functions in the handover decision procedure. If otherwise, such
handovers as PBGT handover and edge handover will be either delayed or advanced.

4. IUO problem 4
Detail description:
Can the Assign-Optimum-Level Thrsh. be lower than the edge handover threshold?
Reply:
The Assign-Optimum-Level Thrsh. has two options:

In the case of up-downlink unbalance, the Assign-Optimum-Level Thrsh. equals to the

sum of the receiving level threshold and the up-down link balance margin.

In the case of up-downlink balance, the Assign-Optimum-Level Thrsh. equals to the

receiving level threshold.

Therefore, Assign-Optimum-Level Thrsh. cannot be lower than the sum of the edge handover
threshold and signal intensity difference between the underlaid subcell and the overlaid subcell.

5. Please explain the T3105 and Max resent times of physical information.
Detail Description:
Please explain the T3105 and Max resent times of physical information
Reply:
During the asynchronous handover, MS constantly sends the handover access Burst to BTS.When
BTS detects the Burst, BTS send physical information to the MS on the main DCCH/FACCH,
and starts timer T3105. At the same time, it sends the MSG_ABIS_HO_DETECT message to
BSC. The physical information contains related information of different physical layers so as to
guarantee the correct access of MS. If the timer T3105 times out before receiving the SAMB
frame from MS, BTS re-sends physical information to MS. This parameter specifies the
maximum times Ny1 for re-sending physical information. If the number of resending times
exceeds Ny1 and BTS still has not received any correct SAMB frame from MS, BTS will send
BSC the connection failure message and handover failure message. After BSC receives the
messages, it will release the assigned dedicated channel and stop timer T3105. See Protocol 0858
and 0408. The value of this parameter can be increased correspondingly when the handover
becomes slow and handover success rate is low which is caused by clock or bad transmission
condition.

6. Whether it is possible to make an inter-BSC PBGT handover?

Detail Description:
Whether it is possible to make an inter-BSC PBGT handover?

Reply:
The conditions to trigger a PBGT handover include:

The receiving levels of the serving cell and the destination cell and the configuration of
associated parameters must satisfy the PBGT value configured and P/N principles.

The destination cell and the serving cell are in the same layer and the same level.

The destination cell is prior to the serving cell in the list of handover candidate cells.

Even for cells of different BSCs or MSCs, if they are the same in priority, they are also available
for PBGT handover(satisfying Huawei 16 BIT order algorithm).

7. What does the parameter UO signal intensity difference mean?

Detail Description:
According to the Guide, the signal intensity of the underlay subcell differs from that of the
overlay subcell due to the differences in transmission power and path loss. The UO signal
intensity difference means a power compensation value for the overlay subcell. Since the
handover decision procedure is based on the level after power compensation for the overlay
subcell, the configuration of this parameter must be accurate. Otherwise, the PBGT/border
handover may be delayed or advanced, thus causing handover failure. As we know, BCCH is
generally distributed in the underlay subcell, and TCH in overlay subcell. It makes no sense to
compensate power for the overlay subcell by the parameter UO signal intensity difference
because only BCCH level instead of TCH level is involved in the handover decision procedure.
Each cell has only one BCCH, which is in either the overlay subcell or the underlay subcell. If the
BCCH is distributed in the underlay subcell, the parameter does not make any sense in the
handover decision procedure.
Reply:
Indeed, BCCH is only distributed in the underlay subcell to ensure a satisfactory coverage, and
the handover decision procedure depends on only BCCH level. In a handover decision procedure
of a call undergoing in a overlay subcell, the signal intensity at the time is not the actual signal
intensity of the IUO cell. It is necessary to add RX_level of a overlay subcell and UO signal
intensity difference and then compare the sum with the BCCH level of another cell to make a
handover decision.
IUO handover (handover from the overlay subcell to the underlay subcell or contrarily) depends
on the IUO handover threshold configured, and the destination cell should be a concentric cell.

8. What are the causes for trigger handover require for the better cell?
Detail Description:
What are the causes for trigger handover require for the better cell?
Reply:

For cells of the same layer and the same level, the handover is triggered by PBGT.

For cells of different layers and different levels, the handover is triggered for layer
handover(from lower layer cell to upper layer cell).

9. How to enable a handover for a better cell?

Detail Description:
What are the terms to enable a handover for a better cell (that is, a handover from an M900 cell to
an M1800 cell)?
Reply:

The destination cell is in higher priority layer then of the serving cell layer.

The level of the destination cell > Inter-layer HO Thrsh.+ Inter-layer HO hysteresis.

The destination cell is the first (certainly ahead of the serving cell) in the candidates
queue.

10. What are the causes for incoming BSC handover failure with the reason value of
Equipment Failure?
Detail Description:
In a local network (containing both Es equipment and Huaweis), the incoming BSC handover
seldom succeeds according to the result of traffic statistics. After tracing A interface signaling, we
find the reason value of incoming BSC handover failure is Equipment Failure. What are the
causes for incoming BSC handover failure with the reason value of Equipment Failure?
Reply:
The reasons for incoming BSC handover failure with the reason value of Equipment Failure
include:

The target BSC processes the HANDOVER REQUEST message in the course of interBSC handover. It is either speech service or data service while the associated CIC
number is invalid.

The target BSC processes the Inter CCB Change Complete message in the course of
inter-BSC handover. It is an SDCCH handover and the BSC fails to search for the
buffered Inter Into BSC Handover Request message.

The target BSC processes the Inter Path Ack message in the course of inter-BSC
handover. Both decoding and searching for the buffered Inter Into BSC Handover
Request message fail.
The target BSC receives a Inter Path Rej message.

The target BSC checks the conditions of incoming-BSC handover in the course of interBSC handover and finds equipment failure.

In the course of inter-BSC handover, the target BSC fails to connect with the radio
channel over the Abis interface or fails to send a CHAN ACT message.

In the course of inter-BSC handover, the target BSC begins handover queueing procedure
due to lack of available channels. Upon receipt of an Inter Ret Res message, the target
BSC obtains idle channels, but it fails to send a CHAN ACT message, search the buffered
HANDOVER COMMAND message, and fetch the frequency of the carrier.

In the course of inter-BSC handover, the target BSC receives a CHAN ACT NACK
message.

In the course of inter-BSC handover, the target BSC receives a HANDOVER

DETECTION message and then a CONN FAIL IND message.

In the course of inter-BSC handover, the target BSC fails to receive a CHAN ACT
message before the timer expires.

11. Cell reselection is slow and handover also fails. Why?

Detail Description:

In a drive test, Cell reselection is slow and handover also fails

Reply:

According to the message received, the duration of cell reselection is so short that the MS
cannot identify the BSIC. Since the system information delivered by the BTS is correct,
the cause for the failure may be great clock deviation.

In the course of asynchronous handover, there are not any physical messages delivered.
The reasons may be:
i. When detecting a handover access at the new channel, the BTS did not deliver a
physical information. It was asynchronous handover judging by the Abis interface
message traced, but whether the corresponding channel was activated was unknown
according to the message. Since the handover command had been delivered normally
and the BTS had reset, the corresponding channel must be activated properly.
ii. The handover detection message could not be decoded due to clock fault, thus
leading to handover failure since there was no physical message to be delivered or it
was hard to decode the physical message properly.

Later it is confirmed that the clock is faulty.

12. Traffic volume of 1800M network keeps high after network upgrade.
Detail Description:
Traffic volume of 1800M network keeps high after network upgrade. The traffic volume is over
170Erl with 90 TRXs on busy hour, and it can hardly be lowered even some parameters are
modified. Which parameters should be modified to lower the undertaking traffic?
Reply:
Check whether traffic volume increases indeed (excluding equipment failure). If yes, it is
necessary to modify cell reselection and handover associated parameters.

Set a smaller value for the CRO of 1800M band.

Raise the MS minimum access level.

Decrease inter-layer handover threshold and inter-layer handover hysteresis of 1800M

band.

Modify edge handover threshold.

Modify the handover parameters of 900M band to lessen incoming 1800M handover
times.

Enable direct retry.

13. When is it the start point and stop point of the timer T3124?
Detail Description:

When is it the start point and stop point of the timer T3124?
Reply:
The mobile station starts timer T3124 at the start point of the timeslot in which the HANDOVER
ACCESS message is sent the first time on the main DCCH.
When the mobile station receives a PHYSICAL INFORMATION message, it stops timer T3124,
stops sending access bursts, activates the physical channels in sending and receiving mode and
connects the channels if need be. If the allocated channel is an SDCCH (+ SACCH), performance
of the mobile station must enable the mobile station to accept a correct PHYSICAL
INFORMATION message sent by the network in any block while T3124 is running.
Its purpose is to detect the lack of answer from the network to the special signal.
Its value is set to 675 ms if the channel type of the channel allocated in the HANDOVER
COMMAND is an SDCCH (+ SACCH); otherwise its value is set to 320 ms.

14. Handover problems of indoor micro-cell system.

Detail Description:
According to the description of Section 10.5.2.34 GSM 04.08, the parameter
early_classmark_sending specifies whether the MS can send an early Classmark Change
message to the system. If the parameter value is 0, the system cannot judge whether the MS
supports dual frequency handover.
When the early_classmark_sending is set as 0, 1 or 2, the inter-BSC handover occurring to a
dual frequency MS includes four cases:

If the handover is from a GSM900 cell to a GSM1800 cell of another BSC, the MSC can
only decode the BSIC of the GSM900 cell.

If the handover is from a GSM900 cell to a GSM1800 cell of another BSC, the MSC can
only decode the BSIC of the GSM1800 cell.

If the handover is from a GSM1800 cell to a GSM900 cell of another BSC, the MSC can
only decode the BSIC of the GSM900 cell.

If the handover is from a GSM1800 cell to a GSM1800 cell of another BSC, the MSC
can only decode the BSIC of the GSM1800 cell.

The test record is just like the Case 2. That is, when the MS handover from Huaweis GSM900
cell to Ms GSM1800 cell, the MS can only decode the BSIC of the GSM1800 neighboring cell,
but cannot switch back to Huaweis GSM900 cell even under idle state. Therefore, Huaweis
GSM900 cell cannot share the traffic load properly and call-drop events tend to occur to the
GSM1800 cell.
Since the parameter configuration of Ms BSC is correct (early_classmark_sending=3), and the
handover between Ms GSM900 and GSM1800 is normal, the parameter configuration of
Huaweis BSC must be incorrect. Check the setting of early_classmark_sending of Huaweis
BSC and the parameters relative to GSM Phase2.
Reply:
According to Section 10.5.2.34 of GSM 04.08, the value range of the parameter
early_classmark_sending is 0 and 1, indicating to the MS whether or not early sending of
CLASSMARK CHANGE is allowed. Huawei's configuration is consistent with the protocol,
while Ms configuration is not.
The reason why the MS cannot switch back to Huaweis GSM900 cell even under idle state is
irrelative to the configuration for early_classmark_sending (ECSC).
Ms parameter explain:
early_classmark_sending
For GSM system, some specifications (including service capability, frequency band, power,
encryption capability and so on) are identified with CLASSMARK. The CLASSMARK is
classified as CLASSMARK1, CLASSMARK2 and CLASSMARK3. Network can either query
various capabilities of an MS through CLASSMARK or instruct an MS to report its
CLASSMARK
immediately
after
establishment
of
a
link.
The
parameter
early_classmark_sending defines whether an MS sends its CLASSMARK to the BTS, and
whether the BTS reports the CLASSMARK to the MSC.
Value range of early_classmark_sending:
0: The MS will not send its CLASSMARK to the BTS, and neither does the BTS to the MSC.
1: The MS will not send its CLASSMARK to the BTS, but the BTS reports it to the MSC.
2: The MS sends its CLASSMARK to the BTS, but not does the BTS to the MSC.
3: The MS sends its CLASSMARK to the BTS, so does the BTS to the MSC.
Contained in the system message 3, early_classmark_sending is broadcasted periodically over
BCCH of each cell.
CLASSMARK is mainly for dual-band application. It must be set as 0 for area of single band
GSM application, and 3 for area of dual-band GSM application.

15. What is the function of Min DL level on candidate cell in External Cell
Description Table?
Detail Description:

What is the function of Min DL level on candidate cell in External Cell Description
Table?
Reply:
The level of a cell must be higher than the value configured for the parameter Min DL level on
candidate cell to be a handover candidate cell of the serving cell. Suppose Min DL level on
candidate cell of cell A is set as 95dBm, and that of Cell B is 100dBm. If the MS in Cell A
detects that the level of Cell B is 98dBm, then Cell B can be a handover candidate cell of Cell A.
If the MS in Cell B detects that the level of Cell A is 98dBm, then Cell A cannot be a handover
candidate cell of Cell B.
Note: The value configured for Min DL level on candidate cell must be higher than
RXLEV_ACCESS_MIN of the cell.
16. How to optimize the cells where call-drops occur frequently in the course of

handover?
Detail Description:

How to optimize the cells where call-drops occur frequently in the course of handover?
Reply:
After analyzing the Abis interface message of the associated cells, we find most of the call-drops
are due to poor cell quality, with the reason value of ERROR-INDI. Besides, the BTSs are dense
in the area and they are configured with many TRXs, so internal interference is serious in the
network.
Take the following measures to handle the case:

Register Receiving Quality Measurement and Receiving Level Measurement of the

associated cells to know uplink and downlink interferences.

After analyzing the traffic statistics and driving test, adjust the coverage for areas where
interference is serious to eliminate overlapped coverage.

Figure out the proportions of various handovers and adjust the handover threshold
according to the associated information gotten by measure 1.

Adjust the radio link failure timer and SACCH Multi-frames.

Set a bigger value for T200 of LAPDm.

Start downlink power control

Check the statistic results of call-drops and assignments of each TRX to see whether they
are within the acceptable range.

17. Why does it take long to trigger a handover?

Detail Description:
In a dual-band network, 1800M is supported by Huaweis equipment, and 900M is supported by
Ns. It is found that it takes long (about 9 seconds) to trigger a handover from a 1800M cell to a
900M cell, while very short to trigger a handover from the same 1800M cell to another 900M

cell.
Parameter configuration is give below:

900M is on the layer 3, and 1800M is on the layer 2.

Both Edge HO UL RX_LEV Thrsh and Edge HO DL RX_LEV Thrsh are set as 32.
Inter-cell HO hysteresis is set as 4dB. PBGT HO Thrsh is set as 70.

Cell description table: Inter-layer HO Thrsh is 35; Inter-layer HO hysteresis is 4dB.

External cell description table: Inter-layer HO Thrsh is 30; Inter-layer HO hysteresis

is 3dB.

Edge HO watch time is set as 4 seconds, Edge HO valid time is set as 3 seconds.

Frequency of reporting measurement result: twice per second. 10:1 configuration.

Reply:
After analyzing information obtained from driving test, we find there are six handover actions
that were triggered when the receiving level of the serving cell was lower than the border
handover threshold for 10 seconds.
1. Min interval for TCH HOs in [Handover control data table]
When a new TCH is allocated, it is necessary to start a timer to keep a handover be triggered
upon expiration of the timer. The parameter Min interval for TCH HOs is just used to specify
the waiting duration of the timer.
2. Filter length for TCH level in [Filter data table]
The parameter Filter length for TCH levelIndicates the number of MRs to be used to do TCH
signal strength averaging calculation.
Both handover and call setup are a new setup procedure. Since the measurement report in the
primary stage of a call may be untrue, it can not be taken as a reference in handover decision.
Therefore, the number of measurement reports must reach the value configured for the parameter
Filter length for TCH level (3s) before the initiation of a handover decision process. Therefore,
for traffic channels, adding the effect of Min interval for TCH HOs (6s) and PN threshold(3/4),
it is normal that it takes about 12 seconds to trigger a handover.
18. The measurement result of uplink level handovers is big. Does it mean that up-down
link unbalance occurs to the network ubiquitously?
Detail Description:

The measurement result of uplink level handovers is big. Does it mean that up-down link
unbalance occurs to the network ubiquitously?
Reply:
If both uplink and downlink satisfy the conditions to trigger an edge handover, then it will be
measured as an uplink edge handover. Therefore, a big number of the statistic result of uplink
handovers does not necessarily mean up-down link unbalance. In this case, it is necessary to
register Up-Down Link Balance Measurement, Receiving Level Measurement and Channel

Allocation Measurement to find out the reason for the abnormal.

19. In a rural network, how to estimate the levels of the neighboring cells for

various cells conveniently?

Detail Description:

In a rural network, how to estimate the levels of the neighboring cells for various cells
conveniently?
Reply:
It is infeasible to get the information about levels of various neighboring cells by driving test.
You can estimate neighboring cell levels for various cell according to the rate limit and level limit
to be input to register Defined/Undefined Neighboring Cell Measurement Function. Adding with
the data obtained from the driving test carried out at typical spots, you can get the information
about the coverage of the rural network soon.
20. Why it is hard to trigger a handover even the receiving level of the neighboring

cell is much higher than that of the serving cell?

Detail Description:
Over the carrier configured with main-BCCH, a handover occurs when the receiving level of the
neighboring cell is higher than the PBGT handover threshold. While over the carrier configured
with non-main BCCH, it is hard to trigger a handover even when the receiving level of the
serving cell is over 10dB lower than that of the neighboring cell due to power control. Why?
Reply:
The function of downlink power control is enabled for the local network, but the main BCCH
does not support power control since it provides full power transmission. Therefore, handover
over the main BCCH is just like the case when the power control is not enabled. While for
handover over non-main BCCH, the receiving level decreases due to power control after the TCH
is occupied. In this case, the BSC will compensate power for the TCH before initiating a
handover decision procedure to avoid ping-pong handover.
Cell sequencing is performed based on the real level measured for a cell. In a handover decision
procedure, the receiving level of the serving cell is the sum of the real TCH level measured and
power compensation level(for PBGT handover, IUO handover and load handover), and just the
real level measured(for other kinds of handovers).
If the CDU loss of the TCH is different from that of the main BCCH, the sum of the real TCH
level measured and power compensation level does not equal to the level of the main BCCH.
When it is the TCH that is being occupied in this case, it is necessary to compare the TCH level
after power compensation (instead of the main BCCH level of the serving cell) with the main
BCCH level of the neighboring cell to perform the handover decision.

21. When to establish A interface circuit during handover?

Detail Description:
The following is description for a handover procedure presented in a document: In a handover
procedure, the BSC starts allocating A interface circuits upon receipt of an EST IND message

from the MS, and sends a UA frame to the MS at the same time. When receiving the UA frame,
the MS sends a HANDOVER COMPLETE message to the BSC. The BSC then counts it as a
handover success when receiving the HANDOVER COMPLETE message.
Which signaling is the instruction of allocating A interface CIC delivered in?
Reply:
The description the BSC starts allocating A interface circuits upon receipt of an EST IND
message from the MS is for previous version. At present, the BSC starts net-drive upon receipt
of an EST IND message. To avoid make-and-break handover, the BSC advances the net-drive
operation to the receipt of a CHA ACT ACK message for uplink and a HO DETECT message for
downlink.
22. Handover
Detail Description:
Huawei's BSS supports external cell handover. The receiving load handover threshold of
the destination cell is one of the factors to trigger a load handover. How to trigger a load
handover?
The maximum MS transmission power is one of the factors to trigger a PBGT handover.
How to trigger a PBGT handover?
Does inter-BSC handover referred to border handover?
Reply:
1. Load handover occurs only intra-BSC.
Conditions to trigger a load handover:
Current flow level < System flux Thrsh. for load HO ,
Load of the serving cell Load HO Thrsh.
Load of the neighboring cell Load Req. on candidate cell.
Receiving level of the neighboring cell > Inter-layer HO Thrsh + Inter-layer HO
hysteresis . (depending on the adjusting bit corresponding to inter-layer handover
threshold of both the serving cell and the neighboring cell) .
When the conditions above are satisfied to trigger a load handover, the MSs within the load
handover band will switch over to the neighboring cells of light load, in sequence of their
respective levels. The load handover stops once the receiving level of the serving cell is lower
than Load HO Thrsh or that of the neighboring cell is higher than Load Req. on candidate
cell.
2. MS_TXPWR_MAX_CCH is configured in External cell description table.
MS_TXPWR_MAX_CCH Max. MS transmission power, power corresponding to the controlled
level See the GSM05.05 protocol.
Value range: 031; Default :5
Conditions to trigger a PBGT handover:
The path loss of the neighboring cell is a certain less than that of the serving cell. Besides, the
measurement results in a period must comply with the P/N rule. That is, at least P measurement
results among the total number N agree with the condition PBGT(n) > PGBT_Ho_Margin(n).
Wherein, P, N and PBGT_Ho_Margin(n) are configured on Data management system. PBGT(n)
can be figured out according to the parameter configured on the Data management system and the

measurement result reported by the BTS.

PBGT handover is only feasible between cells of the same layer and the same level and can only
be triggered over TCH channel. The destination cell must be ahead of the serving cell in the
candidate queue.
3. The MS is at the border of a cell. When the receiving power of the MS/BTS is lower than the
border handover threshold, the system initiates a handover for a better cell. This handover is
referred to as a border(EDGE) handover.
Border handover, PBGT handover and emergency handover may lead to inter-BSC handover.
23. Inter-layer handover associated parameters.
Detail Description:
Parameters involved in inter-layer handover:
Neighboring cell level Inter-layer HO Thrsh (configured for neighboring cell) + Inter-layer HO
hysteresis (configured for neighboring cell) .
Serving cell level Inter-layer HO Thrsh (configured for serving cell) Inter-layer HO hysteresis
(configured for serving cell).
So both the neighboring cell and the serving cell adopt Inter-layer HO Thrsh and Inter-layer
HO hysteresis configured for their own respectively, dont they?
Reply:
Yes, it is true.
Among the 16bits specified by the handover rule, the fourteenth is the adjusting bit of inter-layer
handover threshold.
16-bit handover rule
Serving cell: if receiving level Inter-layer HO Thrsh -Inter-layer HO hysteresis, then set
the fourteen bit as 0; If otherwise, set this bit as 1, and the bit 13, 12 and bit 10-5 as 0.

Neighboring cell: if receiving level Inter-layer HO Thrsh + Inter-layer HO hysteresis,

then set the fourteen bit as 0; If otherwise, set this bit as 1, and the bit 13, 12 and bit 10-5
as 0.
No matter whether the neighboring cell and the serving cell are on the same layer and the same
level or not, the setting for this bit of each cell must be based on the difference between Interlayer HO Thrsh and Inter-layer HO hysteresis of the cell itself.
24. Handover fails frequently
Detail Description:
The network is in normal operation previously. Recently, the handover success rate decreases
suddenly from 95%98% to 50%55%.
View the traffic statistic result, we find that almost all of the handovers from Huaweis BTS to Es
BTS fail, but both intra-BSC (Huawei) handover and the handover from Es BTS to Huaweis
BTS are normal.
The reason for this fault is that a cutover has been implemented to Es BSC and MSC without
notice to Huawei. Before the cutover, both Huaweis BSC and Es BSC are connected to the
MSC1. After the cutover, Es BSC is connected to the MSC2, and Huaweis is still to the MSC1.
Therefore, handover failure occurs frequently since that the data configuration after the cutover is
incorrect or that the data configuration is not modified after the cutover.

Reply:
1. Signaling analysis:
At A interface, Huaweis BSC sends a HANDOVER REQUIRED message to E's MSC1, and
EMSC1 responds with a HANDOVER REQUIRED REJECT message with the reason value of
Invalid cell. The reason is that the CGI of the destination cell is still configured on the MSC1
while Es BSC has been connected to MSC2 after a cutover.

2. Traffic statistic analysis:

According to the traffic statistic result, outgoing inter-BSC handover attempts all fail, and
Huaweis cells receive no incoming-BSC handover requests.

3. Possible causes:
Inter-MSC handover signaling procedure:

Possible causes:
o The CGI of the destination cell is not configured in the External cell configuration table

of Es MSC1 (some manufacturers require to configure only LAC instead of CGI in the
External cell configuration table of their MSCs, but Es MSC require to configure
CGI), so the MSC1 cannot recognize the destination cell and sends a HANDOVER
REQUIRED REJECT message with the reason value of Invalid cell. As a result, the
inter-MSC handover is refused at the A interface between Huaweis BSC and E's
MSC1, thus leading to failure of outgoing-BSC handover attempt. Likely, if Huaweis
cells have not been configured as external cells of the MSC2, the requests for interBSC handover from E BSC to Huaweis BSC will also be rejected. Therefore,
Huaweis cells do not receive any incoming-BSC handover request.
o The CGI of the destination cell has been configured in the External cell configuration
table of Es MSC1, while the CGI of Huaweis cell (source cell) has not been
configured in the External cell configuration table of the MSC2. In the course of interMSC handover, the MSC1 over the E interface sends to the MSC2 a PERFORM
HANDVOER message, which carries CGIs of both the destination cell and the source
cell. Because the CGI of Huaweis cell has not been configured in MSC2, the interMSC handover will be refused by the MSC2 at the E interface between the MSC1 and
the MSC2, thus leading to the failure of outgong-BSC handover attempt. Likely, if the
CGI of Es cell has not been configured as a external cell of the MSC1, the request of
inter-BSC handover from Es BSC to Huaweis BSC will be refused by the MSC1. As a
result, Huaweis cell does not receive any incoming-BSC handover request.
o External cells of the BSC are configured with faulty CGIs.
Trouble shooting suggestions: Since the data configuration for Es MSC1 and the MSC2 may be
incorrect, trace the E's signaling messages over the E interface to see whether there are such
messages as PERFORM HANDVOER and PERFORM HANDVOER REJECT. If yes, the data
configuration for E's MSC2 is incorrect; if otherwise, that for Es MSC1 is incorrect.
Conclusions obtained from on-site maintenance:
The trouble has been shot. The causes for this trouble are:
The CGI of Huaweis cell under the MSC1 has not been configured in the External cell
configuration table of Es MSC2. (After the corresponding data has been modified,
incoming-Huaweicell handover is normal, but outgoing-Huaweicell handover not).

E has refreshed the CGI of those cells under its MSC2, but not informed us about it.
(After the associated data of the MSC1 has been modified, the outgoing-Huawei's cell
handover becomes normal).

25. Call-drop in the course of handover

Detail Description:
Does the call-drop in the course of handover refer to a call-drop really?
Is the number of call-drops in the course of handover displayed in the traffic statistic result?
Reply:
The figure below shows the procedure of an intra-BSC handover.

Call-drop during handover:

Call-drop during handover means that the handover fails in the handover procedure (from the
delivery of the handover command to the completion of the handover), and the system measure it
as a handover failure when the system receives a channel establish failure message. Generally, the
call really drops in this case. Sometimes, however, unreasonable parameter setting may also lead
to faulty statistics for handover failures.
For example, in the incoming BSC handover procedure, if the value set for the T3103 timer is too
small, the timer may expires before the MS sends to the BSC a CLEAR COMMAND message
when the MS reverses to the original channel after a handover failure.
Call-drops can be classified into four categories according to the reason values:
TCH lost radio connections (connection failure).
TCH lost radio connections (error indication).
TCH seizure failures due to terrestrial link failures.
4.Call-drops caused by other reasons (mainly caused by handover and preemption). (The
call-drops of this category are not measured separately in Huawei's traffic statistic )
Refer to the measurement item Unsuccessful internal inter cell handovers with unsuccessful
reversions for the number of call-drops in the course of intra-BSC handover.
26. How to lessen handover failures for the BTSs in the suburb?
Detail Description:

Will the handover success rate of the BTSs in the suburb rise after the increase of
handover threshold, Min DL level on candidate cell and Ny1 T3105?

Reply:
Handover thresholds can be classified into multiple categories: uplink and downlink border
handover threshold, inter-layer handover threshold and PBGT handover threshold. The higher is
the border handover threshold or inter-layer handover threshold, the easier the handover will be
triggered. The rise of PBGT handover threshold may make a handover more difficult to trigger.
Since border handover occurs frequently in the suburb, the rise of border handover threshold will
easy the border handover, avoiding handover failures due to fast level decrease. The rise of PBGT
handover threshold, however, prevents handover from occurring frequently, thus decrease the
handover success rate.
The handover success rate of the BTSs in the suburb can also be raised by increasing Min DL
level on candidate cell and Ny1 T3105. While the increase of Min DL level on candidate cell
may lead to more call-drops, and the increase of Ny1 T3105 may have impact upon call
quality.
Therefore, it is important to raise the border handover success rate to raise the handover success
rate in the suburb.
Therefore, measures can be taken in the following ways:
Study the local coverage state, land form;
Analyze cell neighboring relationship, relationship between handover number and handover
success rate.
Adjust uplink and downlink border handover threshold, P/N decision rule according to up-down
link balance.
Ensure that signals of both cells involved in the handover are not deteriorating.
Adjust parameter configuration for the BTSs where handover frequently occurs.
27. Handover associated traffic statistics
Detail Description:
Do the following inter-cell handover performance measurement items correspond to various
handovers configured?
Attempted handover for uplink quality
Emergency handover
Attempted handover for down link quality
Emergency handover
Attempted handover for uplink strength
Border handover
Attempted handover for down link strength
Border handover
Attempted handover for timing advance
Emergency handover
Attempted handover for better cell
PBGT inter-layer handover
Attempted handover for traffic load
Load handover
Attempted handover for rapid level drop
Emergency handover
Attempted handover for directed retry
Attempted handover for other causes
Is the correspondence listed above correct? What does the handover for better cells include?
Reply:
The correspondence listed above is correct.
Attempted handover for better cell: It includes both intra-BSC inter-cell handover and outgoing
BSC handover and is often triggered for better cells (neighboring cells of low pass loss, high
priority or high level).

Attempted handover for directed retry: It includes both intra-BSC inter-cell handover and
outgoing BSC handover and is often triggered upon receipt of a DIRECTED RETRY message
(the current cell is in congestion in the assignment procedure).
Attempted handover for other causes: It includes intra-BSC intra-cell handover, intra-BSC intercell handover and outgoing BSC handover. It is often triggered for such reasons as fast moving,
abnormal handover reason and so on.
Refer to Traffic Statistic Manual for details.
28. Candidates for handover
Detail Description:
What is the function of Min DL level on candidate cell in the cell description table? Suppose
cell A and cell B are neighboring cells of each other, Min DL level on candidate cell of cell A is
set as -95dBm, and that of cell B is -100dBm. If an MS undergoing a call in cell A finds that the
receiving level of cell B is -98dBm, then can cell B act as a candidate cell of cell A if Min access
level offset is not taken into consideration? Does only one of the two parameters (Min DL level
on candidate cell and Min access level offset) take effect? Which one takes effect?
Reply:
No matter for External cell description table or Cell description data table, Min DL level on
candidate cell takes effect only when the local cell will act as a candidate cell of another instead
of itself.
That is, if cell B will act as a candidate cell of Cell B, it is necessary to compare the receiving
level of cell B with Min DL level on candidate cell configured for cell B instead of cell A.
With Min access level offset taken into consideration, it is necessary to compare the receiving
level of cell B with the sum of Min DL level on candidate cell and Min access level offset
configured for cell B.
For the case presented above, the cell B can be a candidate cell of cell A.
Note: The value configuration for this parameter must be bigger than the MS minimum access
level of the cell.
29. In a abnormal handover procedure, how does the MS decides a handover failure

and then initiates a procedure to back over to the previous channel?

Detail Description:

In a abnormal handover procedure, how does the MS decides a handover failure and then
initiates a procedure to back over to the previous channel?
Reply:
The MS starts the T3124 timer when sending a handover access message, attempting to perform
handover access over a new channel. Upon receipt of the handover access message, the BTS
sends a phys info to the MS. The MS then stops the T3124 timer upon receipt of the phys info
message. If the MS does not receive the phys info message before the T3124 timer expires, the
MS then initiates a procedure to back over to the previous channel. The T3124 timer is set as
675ms for SDCCH and 320ms for others.
At the MS side, if the T3124 timer expires (for asynchronous handover), and the bottom layer of
the new channel fails prior to the delivery of a handover complete message, the MS deactivates

the new channel and then activates the previous one to re-connect TCH and establish a main
signaling link. After the main signaling link is established, the MS sends a HANDVOER
FAILURE message over the link and resumes the state before the handover access attempt.
As shown in the figure below:

When the T3124 timer expires, the MS initiates a procedure to back over to the previous
channel. When the MS receives a phys info message correctly, it starts sending SABM
frame. In this case, the MS occupies the radio link successfully and keeps detecting the
link. When detecting a bottom layer link failure before the delivery a HANDOVER
COMPLETE message, the MS deactivates the new channel and initiates a procedure to
back over to the previous channel.
30. Data configuration and function of negative PBGT handover?
Detail Description:

How to configure the associated parameters for negative PBGT handover? What is the
function of negative PBGT handover?
Reply:

1. Data configuration:
The configuration of cell neighboring relationship for negative PBGT handover is different from
that for common PBGT handover. The PBGT threshold must be set lower than 64 (that is, the
receiving level of the destination cell can be lower than that of the serving cell). Besides, the
inter-cell handover hysteresis is set as 0, indicating this parameter will not affect cell sequencing.
PBGT handover can be classified into two categories:
1. PBGT handover when PBGT threshold is higher than 64. Conditions to trigger such a
handover are:
The receiving level and all associated parameters of both the serving cell and the
target cell satisfy the triggering conditions for a PBGT handover (PBGT threshold
and P/N criteria).

Both the target cell and the serving cell are on the same layer and the same level.

The target cell is ahead of the serving cell in the list of candidate cells. When Intercell HO hysteresis is greater than PBGT HO Thrsh. 64, Inter-cell HO
hysteresis functions instead of PBGT HO Thrsh.. When Inter-cell HO
hysteresis is smaller than PBGT HO Thrsh.-64, PBGT HO Thrsh. functions.

2. PBGT handover when PBGT threshold is lower than 64. Conditions to trigger such a
handover are:
The receiving level and all associated parameters of both the serving cell and the
target cell satisfy the triggering conditions for a PBGT handover (PBGT threshold
and P/N criteria).

Both the target cell and the serving cell are on the same layer and the same level.

When Inter-cell HO hysteresis is 0, PBGT HO Thrsh. functions.

When Inter-cell HO hysteresis is greater than 0, PBGT HO Thrsh. does not function, and
Inter-cell HO hysteresis functions instead.
Examples:
Set the PBGT threshold of handover from cell B to cell A as 58 and inter-cell handover hysteresis
0. When cell B is the serving cell, and the receiving level of cell A is 6dB (=58-64) greater than
that of the cell B, the negative PBGT handover will occur from cell B to cell A. In this case, the
PBGT handover threshold from cell B to cell A takes effect.
Set the PBGT threshold of handover from cell B to cell A as 58 and inter-cell handover hysteresis
1. When cell B is the serving cell, and the receiving level of cell A is 1dB higher than that of the
cell B, the PBGT handover will occur from cell B to cell A. In this case, the Inter-cell HO
hysteresis instead of PBGT handover threshold takes effect.
2. Function
Negative PBGT handover makes it possible to hand over from high-level cell to low-level cell for
traffic balance purpose. It also helps to control cell coverage by adjusting handover occurrence
position. To avoid frequent ping-pong handover, it is necessary to set a relative higher positive
PBGT handover threshold for the reverse neighboring cell. In the case of tight frequency
multiplexing, be cautious to adopt negative PBGT handover to control interference since the
receiving level of the serving cell is not the highest.
31. All the incoming BSC handovers fail

Detail Description:
Huawei BSC(V01.06.1120) and the BSC of M manufacturer are adopted in X office but the MSC
belongs to A manufacturer. All the incoming handovers from the cell of M manufacturer to
Huawei cell fail.
The on-site signaling tracing shows that after the peer office sends the HO REQ to the Huawei
BSC, Huawei BSC returns the HO REQ ACK but MSC delivers the clear command within the
less than 1 second to result in the handover failure.
A-interface Phase flag of Huawei BSC is Phase 2+, MSCs is Phase 2+ and the BSC of M
manufacturer is Phase 2.
Reply:
1. Trace the signaling of A interface at both sides and compare the HO REQ ACK sent by
Huawei BSC with the HO REQ ACK sent by the BSC of M manufacturer and find that there is
difference about the descriptions of L3 message in the message domain for Huawei and M
manufacturer. The HO REQ ACK returned by Huawei BSC carries such four IEs as Speech
Version, Chosen Channel, Chosen Encryption Algorithm and Circuit Pool. But the above four IEs
are not included in the HO REQ ACK returned by M manufacturer. Therefore, MSC cannot
identify any one of the above four IEs, resulting in the handover failure.
2. Check the 08.08 protocol (PHASE 2+), BSC determines whether the HO REQ ACK carries
such four optional IEs as Speech Version, Chosen Channel, Chosen Encryption Algorithm and
Circuit Pool and the MSC should be compatible with it. The descriptions about the Circuit pool
show that BSC determines whether to carry circuit pool when BSC configures multiple circuit
pools.
3. Contact the manufacturer of the MSC for the technical support and the MSC cannot identify
Speech Version and Circuit Pool. Wherein, the MSC of A manufacturer enables the EFR
function to identify the Speech Version and the BSC shields the Circuit Pool.
4. The incoming BSC handover success rate is up to 94% after the MSC enables the EFR function
and Huawei BSC shields the Circuit Pool of the HO REQ ACK.
As previously mentioned, if the BSC is subject to the BSC V01.06.1120A and BSC configures
only one circuit pool, Huawei BSC sets a parameter to shield such IE as the Circuit Pool when
cooperating with the MSC of A manufacturer. At the same time, MSC solves the problem of
Huawei BSC incoming handover after enabling the EFR function. (The other three IEs under the
BSC 01.06.1120A cannot be shielded by a parameter)
The following table shows the analysis related to the BSC version (for the Phase 2 and Phase 2+
if no special notes)
IE(HO REQ ACK) G3 BSC32.10101.04.1120A G3 BSC32.10101.06.1120A
Circuit pool The HO REQ ACK does not carry this IE when it is shielded by a parameter or the
circuit pool is set to 255. The HO REQ ACK does not carry this IE when it is shielded by the
parameter.
Chosen channel If the HO REQ carries full rate or half rate TCH, the HO REQ ACK does not
carry the IE. Otherwise, the HO REQ ACK carries the IE. The HO REQ ACK must carry this IE
in case of Phase 2 and Phase 2+
Chosen Encryption Algorithm MSC is not encrypted by selection or the encryption algorithm
selected by the BSC is inconsistent with that required by the MSC, the HO REQ ACK carries this
IE. MSC is not encrypted by selection or the encryption algorithm selected by the BSC is

inconsistent with that required by the MSC, the HO REQ ACK carries this IE.
Speech Version The HO REQ ACK must carry this IE in case of Phase2+ instead of Phase 2 The
HO REQ ACK must carry this IE in case of Phase2+ instead of Phase 2
The above shows following information:
(1) For the BSC V10101.06.1120A (Phase 2), the HO REQ ACK must carry the Circuit Pool
whatever the number of circuit pools configured by the BSC unless it is shielded by a parameter.
Consequently, the MSC of A manufacturer cannot identify the circuit pool, resulting in the
incoming BSC handover failure.
(2) Whether Huawei BSC HO REQ ACK message carries the Speech Version is irrelevant
with the version of BSC. The message does not carry the Speech Version under the Phase 2 but
does under the Phase 2+.
In the subsequent BSC V02.06.1120A, you can set a parameter to control whether the HO REQ
ACK message carries other optional IEs to control the four optional IEs flexibly. Therefore,
after the BSC is upgraded to 01.06.1120A version and the MSC belongs to A manufacturer, it is
recommended to record corresponding traffic measurement when the incoming BSC handover
success rate is low and to trace A interface or NO.7 signaling.
Contact the 800 hot line for technical support when one case is the same as the above.
32. Preprocessing of measurement report
Detail Description:
Data configuration adopts preprocessing of BTS measurement report, and how does the BTS
handle measurement report?
Whether to average this measurement report with about twice/second?
Reply:
Preprocessing of measurement report with twice/second is to equalize and filter instead of
average this measurement report.
Under the condition of radio transmission, measurement report from MS may be lost.
Preprocessing of measurement report is to handle the measurement report and equalize this
definite lost measurement report through an algorithm. Additionally, preprocessing of
measurement report completes the filtering. Finally, preprocessing of measurement report exports
the measurement report after equalization and filtering.
Preprocessing of measurement report is performed by the BTS or BSC, but the BTS is preferred.
Data configuration adopts preprocessing of BTS measurement report and the BTS performs the
preprocessing and sends the preprocessed measurement report to the BSC.
33. The causes for outgoing BTS handover failure in the BSCV06.1120A
Detail Description:
Whether inter-BSC outgoing cell handover failures (Cause reported by MS: Abnormal release, no
activity on the radio path) are caused by target cell congestion? What are the inter-BSC outgoing
cell handover failures (Cause reported by MS: Protocol error unspecified) caused? Whether the
interference is caused?
Reply:
In the traffic measurement of BSCV04.1120A and later, two traffic measurement items on

outgoing BSC handover failure are shown below:

(1) Unsuccessful outgoing BSC handovers with successful reversion;
(2) Unsuccessful outgoing BSC handovers with unsuccessful reversion.
You cannot locate the specific cause.
Starting from BSC V06.1120A, the causes for Huawei outgoing BSC handover failure includes:
1. Local BSC (source BSC) is abnormal. (5 kinds of causes).
2. Receive HANDOVER REQUIRED REJECT from the MSC (14 kinds of causes).
3. Receive CLEAR COMMAND from the MSC (8 kinds of causes)
4. Handover fails and returns to source channel, HANDOVER FAILURE reported by MS
contain the cause (17 kinds of causes).
The first type is caused by local BSC but the second, third and fourth is caused by target BSC,
MS or Um interface.
When MS fails to access target cell and returns to source channel, the fourth type is sent to the
BSC and then BSC sends it to the MSC (the cause is radio interface failure - reversion to old
channel"). This message contains the following RR cause values:
1. Inter-BSC outgoing cell handover failures (Cause reported by MS: Abnormal release,
unspecified)
2. Inter-BSC outgoing cell handover failures (Cause reported by MS :Abnormal release,
channel unacceptable)
3. Inter-BSC outgoing cell handover failures (Cause reported by MS: Abnormal release,
timer expired)
4. Inter-BSC outgoing cell handover failures (Cause reported by MS: Abnormal release, no
activity on the radio path)
5. Inter-BSC outgoing cell handover failures (Cause reported by MS: Preemptive release)
6. Inter-BSC outgoing cell handover failures (Cause reported by MS: Handover impossible,
timing advance out of range)
7. Inter-BSC outgoing cell handover failures (Cause reported by MS: Channel mode
unavailable)
8. Inter-BSC outgoing cell handover failures (Cause reported by MS: Frequency not
implemented)
9. Inter-BSC outgoing cell handover failures (Cause reported by MS: Call already cleared)
10. Inter-BSC outgoing cell handover failures (Cause reported by MS: Semantically incorrect
message)
11. Inter-BSC outgoing cell handover failures (Cause reported by MS: Invalid mandatory
information)
12. Inter-BSC outgoing cell handover failures (Cause reported by MS: Message type nonexistent or not implemented)
13. Inter-BSC outgoing cell handover failures (Cause reported by MS: Message type not
compatible with protocol state)
14. Inter-BSC outgoing cell handover failures (Cause reported by MS: Conditional IE error)
15. Inter-BSC outgoing cell handover failures (Cause reported by MS: No cell allocation
available)
16. Inter-BSC outgoing cell handover failures (Cause reported by MS: Protocol error
unspecified)
17. Inter-BSC outgoing cell handover failures (Cause reported by MS: Other)
Details are the cause value (4) and (16) carried in the handover failure. Wherein, cause value
(4) "Abnormal release, no activity on the radio path" does not measure target cell congestion. If
target cell has no available channel to result in inter-BSC handover failure, source BSC receives

Handover REQUIRED REJECT (cause value: No radio resource available) sent by the MSC
and source BSC measures once inter-BSC outgoing cell handover failure.
Wherein, cause value (16) is "Protocol error unspecified". In this case, received decode is not
defined in the protocol because of interference.
34. Huawei PBGT handover algorithm formula
Detail Description:

What is Huawei PBGT handover algorithm formula?

Reply:
The formula is as follows:
PBGT(n) = ( Min ( MS_TXPWR_MAX,P ) - RXLEV_DL - PWR_C_D )
- ( Min ( MS_TXPWR_MAX (n),P ) - RXLEV_NCELL(n) )
The meanings of each parameter are shown below:
MS_TXPWR_MAX: The maximum transmit power of MS allowed by the serving cell
MS_TXPWR_MAX (n): The maximum transmit power of MS allowed by neighbor cell n
RXLEV_DL :
The receiving power of MS to the serving cell
RXLEV_NCELL(n): The receiving power of MS to neighbor cell n
PWR_C_D:
The difference between the maximum downlink transmit power of
serving cell caused by power control and actual downlink transmit power
of serving cell
P:
The maximum transmit power capability of MS
35. Whether to trigger the inter-layer handover only from the cell with low priority

to that with high priority?

Detail Description:

Huawei 1800M network cooperates with 900M network of other manufacturers. Huawei
BSC defines higher priority (level 2) for 1800M cell and lower priority (level 3) for
900M cell. Whether 1800M cell cannot perform inter-layer handover to 900M cell?
Reply:
Inter-layer handover is only triggered from the cell with lower priority to that with high priority.
If priority of 1800M cell is higher than that of 900M cell, the inter-layer handover and PBGT
handover from 900M cell to 1800M cell cannot be triggered.
If conditions permit, emergency handover, load handover and edge handover can be triggered
from 1800M cell to 900M cell. (the BSC handover algorithm of 900M manufacturer determines
whether to trigger inter-layer handover and PBGT handover from 900M cell to 1800M cell)
Target cell required by inter-layer handover must satisfy the following three conditions:
1) Level of target cell is higher than that of serving cell.
2) Receiving level of target cell is more than inter-layer handover threshold+ inter-layer
handover hysteresis.
3) 16bit of target cell is located before that of servicing cell.
The above case shows that 1800M cell is of level 2 and 900M cell is of level 3 and priority of
1800M cell is higher than that of 900M cell. Consequently, inter-layer handover from 900M cell

to 1800M cell cannot be triggered.

Note: The inter-layer handover from layer 3 (900M cell) to layer2 (1800M cell) cannot be
triggered, but inter-layer handover threshold and inter-layer handover hysteresis take
effect on the sequence of 16Bit. Similarly, load handover is not triggered but Load HO
Thrsh. and Load Req. on candidate cell take effect on the sequence of 16bit.
36. The difference between enhanced and common concentric circles.
Detail Description:
BSCV02.06.1120A adds enhanced concentric circle function. What is the difference between
enhanced concentric circle handover and common concentric circle handover?
Reply:
1. Two parameters control inner cycle/excircle of concentric circle handover: Direction for IUO
HO UL to OL HO Allowed and Direction for IUO HO OL to UL HO Allowed. The two
parameters are defaulted to Yes, that is, the handover between the inner circle and excircle
grant.
2. Three conditions for common concentric circle handover: Criterion for IUO HO Rx_Lev for
UO HO Allowed, Criterion for IUO HO Rx_Qual for UO HO Allowed and Criterion for IUO
HO TA UO HO Allowed. The three parameters are defaulted to Yes, that is, the handover
between inner circle and excircle of common concentric circle should consider level, quality and
TA. The parameters RX-LEV Thrsh. and RX-LEV Hysteresis control the level handover, the
parameter Receiving Quality Thrsh. controls the quality handover and the parameters TA
threshold and TA hysteresis control the TA handover.
When the switches of common concentric circle handover are enabled,
If the handover from excircle to inner circle of common concentric circle occurs, the
following conditions must be satisfied: Receiving level>= receiving level threshold
+ receiving level hysteresis, and TA<TA threshold - TA hysteresis and receiving
quality<receiving quality threshold.
If the handover from inner circle to excircle of common concentric circle occurs, the
following conditions must be satisfied: Receiving level< receiving level threshold
receiving level hysteresis, or TA >=TA threshold + TA hysteresis or receiving
quality >=receiving quality threshold.
The middle blank place is the hysteresis band to control the ping-pong handover of inner circle
and excircle of common concentric circle, that is, the following conditions must be satisfied:
Receiving level threshold receiving level hysteresis <= receiving level <receiving level
threshold + receiving level hysteresis and TA threshold- TA hysteresis <= TA < TA thrershold +
TA hysteresis.
If any one of the level, quality and TA handover switches is disabled, this condition should not be
considered during the handover.
3. Four conditions for enhanced concentric circle handover: Criterion for IUO HO Rx_Lev for
UO HO Allowedreceiving level condition of concentric circle handover grant, Criterion for IUO
HO Rx_Qual for UO HO Allowedreceiving quality condition of concentric circle handover
grant , Criterion for IUO HO TA UO HO Allowed and U to O Traffic HO Allowed. The four
parameters are defaulted to Yes, that is, the handover between inner circle and excircle of
concentric circle should consider level, quality, TA and excircle traffic.
Compared with the common concentric circle handover, the differences lie in that the parameters
O to U HO received level Thrsh. and U to O HO received level Thrsh. replace the parameters

receiving level threshold and receiving level hysteresis to control the level handover.
When the switches of enhanced concentric circle handover are enabled,
If the handover from excircle to inner circle of enhanced concentric circle occurs, the
following conditions must be satisfied: Receiving level>= U to O HO received level
Thrsh., and TA< (TA threshold - TA hysteresis), receiving quality<receiving
quality threshold and excircle traffic>= Traffic Thrsh. of underlay.
If the handover from inner circle to excircle of enhanced concentric circle occurs, the
following conditions must be satisfied: Receiving level< O to U HO received level
Thrsh., or TA >= (TA threshold + TA hysteresis) or receiving quality>=receiving
quality threshold.
The middle blank place is the hysteresis band to control the ping-pong handover of inner circle
and excircle of enhanced concentric circle, that is, the following conditions must be satisfied: O
to U HO received level Thrsh. <= receiving level < U to O HO received level Thrsh. and (TA
threshold - TA hysteresis) <= TA < (TA threshold + TA hysteresis).
The enhanced concentric circle adds the conditions of excircle traffic handover selection. When
the U to O Traffic HO Allowed is enabled, the parameters Traffic Thrsh. of underlay,
Underlay HO Step period, Underlay HO Step level control the excircle traffic handover.
To trigger the excircle traffic handover, not only the conditions of excircle traffic handover but
also that of level, quality and TA of the handover from excircle to inner circle must be satisfied.
The advantages of enhanced concentric circle function are as follows:
1Optimize the excircle during the assignment to enable the calls occupy the excircle channel in
case of low traffic, decreasing the assignment failure caused by immediate assignment inner
circle.
2Switch the call with the higher level in the excircle into the inner circle during the appropriate
traffic, occupying the inner circle and excircle rationally.
The common concentric circle predicts the level at another layer through the signal difference
between inner circle and excircle. When the signal difference between inner circle and excircle is
non-linear or fluctuates dramatically, it is difficult to ensure the accuracy of prediction.
The enhanced concentric circle function modifies the handover mechanism to avoid the above
problems.
37. Why does the handover not occur even when the level of adjacent cell is higher

than that of serving cell for a long time during the drive test?
Detail Description:

Why does the handover not occur even when the level of adjacent cell is higher than that
of serving cell for a long time during the drive test?
Reply:
The trigger conditions of handover are not satisfied, so the handover is not performed. The trigger
conditions of handover are not the completely same. If the neighbor cell level is very high during
drive test but trigger conditions still cannot be satisfied, the causes are as follows:
It is a handover between BSC/MSC but Co-BSC/MSC Adjustment is set to YES to
affect sequence of candidate cells.
Inappropriate setting of load handover threshold affects sequence of candidate cells.
Incomplete data configuration of neighbor cell relation.
Handover algorithm. There is a problem about data configuration of handover trigger

condition.
Target cell is busy.

38. Whether the MS knows that intra-BSC inter-cell handover fails because of TCH

congestion?
Detail Description:

When intra-BSC inter-cell handover fails because of TCH congestion, whether it is

obtained through handover failure of the handover analysis in the drive test tools?
How does the MS know the handover failure?
Reply:
In the intra-BSC inter-cell handover, BSC sends Channel Activation to the BTS of target cell
before delivering Handover CMD to the MS. When the target cell allocates new channel,
exceptions occur. For example, there are no available channels, queuing, inner error or the cell ID
is out of the range. The measurement value shows that handover failure because of channel
congestion and target cell sends Intercell Handover Reject message to source cell. When the
handover flow stops, the BSC does not deliver Handover CMD to MS.
The drive test equipment collects data through MS. Intra-BSC inter-cell handover fails because of
TCH congestion and the signaling flow involved is irrelevant with the MS. Therefore, obtaining
related information through drive test is impossible. But nothing happens to the MS, because MS
does not know the handover failure because of TCH congestion.
39. Why is handover not launched?
Detail Description:
The client reflects that the base station A and B in the urban area have something wrong in
handover. The level and quality of the MS within the cell is bad, and the level of the cell B is
satisfied. However, the MS does not launch any handover request. The other base stations also
have the same problem. The traffic statistics denotes that the success rate of outgoing cell
handover and incoming cell handover of some cells is 0 or the success rate is very low.
Reply:
If the MS does not hand over to the neighbor cell in case of bad level and conversation quality,
the causes are generally as follows:
(1) There is interference in the downlink, which disables the MS to receive or decode the message
Handover Command sent from the network side. And the message Handover Command is
also invisible in the review of the drive test, which causes that the MS is locked in the current cell
all along.
(2) The parameter definition is not reasonable, for instance, the margin handover level and
emergency handover threshold of the cell are defined too low, which cannot reach the trigger
condition of handover. Therefore, the handover is not launched.
(3) The asynchronous clock makes the inter-cell reselection and handover become abnormal (the
MS cannot decode the BSIC and system information).
Through analyzing the traffic statistics and DBF data, we find that there are mainly the following
problems existing in this place at present:
1(1) The traffic load of the urban area is very heavy, and part of cells need expanding the capacity

urgently to reduce the handover failure caused by insufficient available channels. For those cells
whose capacity cannot be expanded, suggest splitting them to share the traffic load. If the
measure cannot be executed at present, execute it in the next construction stage.
(2) The TCH in the urban area adopts the 13 frequency hopping, however, the HSN
configurations of the three cells of one base station are different, which easily brings commonfrequency and neighboring-frequency interference to the three cells of the co-site base station and
causes the handover failure or call-drop. Suggest configuring the same HSN to the three cells that
perform the frequency hopping at the same base station, and configure different MAIOs to the
three cells. Suggest configuring the HSNs and MAIOs as follows in the case of that the hopping
frequencies of the TCH are grouped continuously:
HSN
MAIO
Cell1

1~63

0, 2

Cell2

1~63

1, 3

Cell3

1~63

0, 2

The above assignment can avoid the neighboring-frequency collision within one base station and
reduce the uplink and downlink interference.
1(3) The HSN of part of hopping cells is configured as 0, that is, cyclic frequency hopping.
Suggest taking proper HSNs within 1~63 to reduce the probability of the common-frequency and
neighboring-frequency collision and reduce the call-drop.
(4) There are cross coverage and common BCCH frequencies and common BSIC of the neighbor
and this makes the MS to hand over to the wrong cell. Therefore, the handover certainly fails.
Suggest checking and adjusting the urban BCCH frequency planning.
2(5) Seen from the traffic statistics, transmission interruption occurs in a certain number of base
stations in the urban area. The trouble of interface A causes the call-drop. Suggest strengthening
the hardware checking to timely clear the trouble. Check part of the base stations at the near end,
and mainly check the diversity reception connecting line and connector of the CDU. Meanwhile,
register the channel assignment performance of the said cells, and observe the condition of
interference at the TRX level and occupation failure of these cells. Replace the frequencies for the
TRX with unsatisfied indexes and check the hardware to replace the unsatisfied hardware.
3(6) The setting of some parameters is unreasonable. Suggest modifying the inter-layer handover
threshold in the Cell Description Table from 37 to 25; and, respectively modifying the PBGT
watch time and PBGT valid time in the Normal Handover Data Table as 4 seconds and 3 seconds.
4(7) Use the test MS on the spot to perform the forced handover and see whether the handover
succeeds.
5(8) If it is difficult to adjust the BCCH, properly adjust the BSIC of the base station and observe
how the handover traffic statistics changes.
(9) If necessary, suggest optimizing the network comprehensively.
40. Can the measurement result be obtained in preprocessing the measurement report?
Detail Description:
How does the BTS send the measurement report to the BSC and can the BSC obtain the
measurement result of the BTS/MS in preprocessing the measurement report? Why there is null
result of the downlink measurement report?
Reply:

The preprocessing of the measurement report mainly includes the two functions:
1) Measurement report interpolation (MR Interpolation)
Generally, the MS periodically reports the measurement report of the downlink and the
neighboring cell, and the BTS combines the corresponding measurement values of the uplink into
the Measurement Result and reports it to the BSC. If the received Measurement Result is
discontinuous somehow or other, the missing Measurement Result must be made up within a
certain missing limit and this process is called MR interpolation calculation.
The continuousness of the Measurement Result is judged by the measurement result number. The
MR interpolation calculation for the missing measurement report uses the simplified first order
interpolation. The missing values are worked out according to the measurement values on both
sides of the missing values in the missing Measurement Result.
2) MR Time Evaluation
The series of various measurement values corresponding with a radio link will not form a smooth
curve. To eliminate the contingency of the handover judgment, the various measurement results
must undergo the treatment of smoothness, and this process can be considered as MR Time
Evaluation. There are multiple methods for the average processing of the MR. At present we
adopt the simple method of averaging forward to obtain the current judging value. The number of
the forward averaged values is called the filter length. The filter length varies with different
measurement values.
The preprocessing of the measurement report can be carried out at both the BSC and the BTS.
When the OMC data is set as the MR preprocessing and instructs the preprocessing of MR to be
performed at the BTS. Therefore, the measurement report sent from the Abis interface has
undergone the said preprocessing. The BSC can get the measurement results that undergo the
preprocessing, and carry out the handover judgment according to the measurement result. After
the preprocessing of measurement report is enabled, the BTS judges the power control.
The BTS measures the uplink received signal strength and creates the uplink measurement report,
and generates the Measurement Result and reports it to the BSC in accordance with the downlink
measurement report reported by the MS. If there is uplink interference and therefore the base
station cannot decode the downlink measurement report reported by the MS, it will be processed
in accordance with the interpolation algorithm. If the measurement report of the MS cannot be
decoded in a long time, the downlink measurement report will be null in the measurement result,
and at this point, the uplink measurement result also may be unsatisfied.
41. Understanding of the handover timer
Detail Description:
In the case of non synchronous handover, the MS continuously sends the handover access Burst
to the network (generally the counter T3124 lasts for 320ms). When the BTS detects the handover
access Burst sent by the MS, the BTS sends on the main DCCH (FACCH) the message Physical
information back to the MS and starts the timer T3105 and meanwhile sends the message
MSG_ABIS_HO_DETECT to the BSC. The message Physical information contains the
related information of different physical layers in order to ensure correct transmission of the MS.
If the timer timeout before the SABM frame from the MS is received, the BTS resends the
message Physical information to the MS. This parameter specifies the maximum number (Ny1)
of sending the physical information. If the BTS does not receive any correct SABM frame from
the MS when the resending number is over Ny1, the BTS sends the message of connection failure
(including the information of handover failure) to the BSC. After receiving the message of
connection failure, the BSC releases newly assigned dedicated channels and stops the timer

T3105.
The problem lies in the following: For the data configuration of the existing network, the
maximum resend times of the physical information is 30, and T3105 is 7 (equivalent to 70ms). It
means that, if the MS still does not access correctly within 2100ms (=3070) after receiving the
handover detection, the handover fails. However, for the tracked signaling from handover
detection to deactivate SACCH, the time is 1510ms (less than 2100ms). How to explain this case?
The related signalings are as follows:

Reply:
In the field tracked signaling from handover detection to deactivate SACCH, the time is about
1510ms. At this point, the MS cannot access the target channel and returns the message of
handover failure on the original channel (the target channel does not reach the maximum resend
times of physical information). The original cell informs the target cell of releasing the newly
assigned dedicated channels. This is the signaling of the target cell of handover, and the
signalings of the original cell of handover tracked from the field are as follows:
The MS receives the handover command on the original channel but cannot access the target
channel and returns the message of handover failure. At this point, the original channel informs
the target cell of releasing the resource of the target channel. This is the signaling of the original
cell of handover. From sending the handover command to returning the message of handover
failure, it takes about 1.6 seconds.
The condition of the signaling through the filed tracking is as follows: The MS cannot access the
target channel, and returns the message of handover failure on the original channel. The cell of
the original channel informs the target cell of releasing the newly assigned dedicated channels. It
has no direct relation to the maximum resend times of physical information.
42. How to accelerate the cross-MSC handover?
Detail Description:
How to accelerate the cross-MSC handover?
Reply:
To guarantee the speed of the cross-MSC handover, at the network side the signaling and speech
link between the MSCs must use direct route; the data configuration between the MSCs must be
up to standard and accurate and reasonable, without redundancy; and, the signaling link and
speech link must have no congestion.
For the radio side, besides that the handover data configuration must be up to standard and
accurate and reasonable, without redundancy (for instance, reduce the judgment time of P/N
handover, lower the handover triggering judgment threshold, and set the co-MSC/BSC
adjusting as No, and set cells the same layer), the coverage of the cross-MSC handover area
must be good, with a high carrier-to-interference ratio; and, the cell access performance must be
good.

43. About PBGT handover and neighbor cell assignment?

Detail Description:
1. In terms of the PBGT handover, the GSM data describes that only the cells at the same layers
and priority levels are supported. I always think that different BSC equipment does not support
the PBGT handover. For example, supposing there is one BSC of Huawei and one BSC of L
manufacturer, can the PBGT handover arise between the two networks?
2. How many neighbor cells are supported at most in the data configuration of Huawei?
Reply:
1. The PBGT handover arises only between the cells at the same layers and priority levels. First
of all, in the [External cell descriptive data table], set the cell layers and priority levels of other
manufacturers as the same with that in the [Cell Descriptive data table].
The triggering criterions of the PBGT handover are as follows:
The path loss of the target cell is less than a certain threshold of the path loss of
the service cell, and satisfies the P/N criterion.
According to the 16bit ordering criterion, the target cell is before the service cell.
If Co-BSC/MSC adjustment is set as No, the judging adjusting conditions of the PBGT
handover are the same with the judging conditions of the PBGT handover conditions between the
cells within the same BSC, and trigger the PBGT handover in accordance with the normal PBGT
handover conditions.
If Co-BSC/MSC adjustment is set as Yes:
a) When the service cell level >=inter-layer handover thresholdinter-layer handover
hysteresis, set the 14th bit to 0; When the neighbor cell level >= inter-layer handover
threshold + inter-layer handover hysteresis, also set the 14th bit to 0. For the neighbor
cells of the same BSC/MSC, the 12th and 13rd bits are set as 00, and this cell may have
the opportunity to be queued before the service cell. If it is higher than the PBGT
handover threshold of the service cell (higher than the handover hysteresis at the same
time), the PBGT handover is performed. For the neighbor cells of different BSC/MSCs,
the 12th and 13rd bits are set as 11, the target cell is queued after the service cell and no
handover is performed.
b) When the service cell level >=inter-layer handover thresholdinter-layer handover
hysteresis, set the 14th bit to 0; when the neighbor cell level < inter-layer handover
threshold + inter-layer handover hysteresis, set the 14th bit to 1, and the target cell is
queued after the service cell and no handover is performed.
c) When the service cell level<inter-layer handover thresholdinter-layer handover
hysteresis, set the 14th bit to 1; when the neighbor cell level >= inter-layer handover
threshold + inter-layer handover hysteresis, set the 14th bit to 0, and the target cell is
queued before the service cell and the handover is performed according to the normal
conditions of PBGT handover. If it is higher than the PBGT handover threshold of the
service cell (higher than the handover hysteresis at the same time), the cell level is
queued to the first and the PBGT handover is performed.
d) When the service cell level<inter-layer handover thresholdinter-layer handover
hysteresis, and the neighbor cell level < inter-layer handover threshold + inter-layer
handover hysteresis, set the 14th bits of both the service cell and neighbor cell to 1 and
mask the 5th~13rd bits. At this point, the PBGT handover is triggered according to the
normal judging conditions of PBGT handover.

2. Table BA1 and BA2 of Huawei support at most 32 BCCH frequencies of the neighbor cells,
and meanwhile, from BSC01.04.1120 on, the BCCH frequencies of the same BCCHs and
different BSIC neighbor cells occur in Table BA1 and BA2 repeatedly, that is, there are at most
32 neighbor cells actually.
44. Inlfuence of handover juding bits in Huawei handover algorithm?
Detail Description:
In Huawei handover algorithem, when BIT14 (inter-layer handover hysteresis digit) of the 16BITS in
the cell is set as 1, BIT13, 12 and 5~10 are masked and all set as 0. Please confirm whether BIT11
(load adjustment digit) is also masked in BSC06.1120A.
Reply:
From BSC00.06.1120A on, if BIT14 is set as 1, BIT5-13 are all set as 0. However, the value
of BIT11 is the same with that of the earlier version and not controlled by the start switch of load
handover. The value of this digit is always related to the comparison between the current load of
the cell and the start and receipt threshold in the load handover data table.
For detailed meanings of various BITS, see the Guide to Specifications for Data Configuration.
45. MS classmark report problem during dual band handovers
Detail Description:
At one place, the problem occurs during the inter-BSC of the same MSC handover between BTS
GSM900 and BTS DCS1800. More specifically, the MSs handover from GSM900 to DCS1800
normally; the problem occurs when the MSs handover back from DCS1800 to GSM900.
The MSC is the product of S manufacturer, the BSC of DCS1800 is the product of M
manufacturer, and GSM900 is the Huawei product.
Reply:
After drive tests, we found that when the MS hands over successfully from GSM900 to DCS1800
(The original cell and the target cell are at different BSCs.), there is no "system information 5ter"
in the messages that the network delivers to the MS over SACCH. Thus, the MS cannot get the
neighbor cell information of GSM900. However, GSM900 cell of the neighbor cell actually
exists. When the MS in this DCS1800 cell initiates another call, there is "system information
5ter" in the message that the network delivers to the MS over SACCH.
There is no "system information 5ter" in the message that the network delivers to the MS because
the network recognizes the MS as a single-band mobile. Namely, the BSC does not have the
specific information on which bands that the MS supports.
There is capacity information of every MS, such as the power level, the supported ciphering
algorithm, whether to support SMS, multi-band ability and so on, which is reported by the
CLASSMARK.
The SABM frame during the call proceeding generally reports "Classmark information 1" or
"Classmark information 2" to the network. The BSC sends the information to the MSC with the
EST IND message. In "Classmark information 1" or "Classmark information 2", it is not stated
whether the MS has the dual band ability, which is reported in "Classmark information 3".
Additionally, MS will not report "Classmark information 3" initiatively.
The contents of "Classmark information 2" that the same MS reports to the network differ when
the MS is in different bands. The network does not care over which band the dual band MS
accesses to it. When the MS reports "Classmark information 2" in message EST IND, the network

starts to treat the MS as a single band mobile. It will not treat the MS as a dual band mobile until
it receives "Classmark information 3" from it. Therefore, in the dual band network or hybrid
network, the network needs to query the CLASSMARK of the MS every time the MS accesses to
it. (At the query, the MS reports its CLASSMARK through message CLASSMARK CHANGE.)
In GSM Specifications Phase2+, a newly added option "ECSC" (Early Classmark Sending
Control) can make the network know about the capacity supported by the MS as early as possible.
When the network adopts the option, the MSs that support the option will send message
CLASSMARK CHANGE as early as possible at their access. Thus, the network does not need to
query.
If the network does not have the ECSC function, it can deliver CLASSMARK ENQUIRY to ask
the MS to report "Classmark information 3" when it receives message EST IND by the setting at
the MSC if the MSC supports dual band function.
If the network has started the ECSC function, the MS can get the indication of it from System
information 3. When the call is proceeding, the MS reports "Classmark information 3" to the
network through message CLASSMARK CHANGE, and the BSC will report this message to the
MSC. (M Manufacturer provides the switch control the report of this to the MSC.)
During the call, if there is inter-BSC handover, the MSC sends "Classmark information 3" to the
target BSC in HANDOVER REQUEST message.
From GSM08.08 Protocol, there is no "Classmark information 3" in message HANDOVER
REQUIRED that the original BSC sends to the MSC during inter-BSC handovers. The table
below lists the content of message HANDOVER REQUIRED:
INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN
Message Type 3.2.2.1 BSS-MSC M 1
Cause 3.2.2.5 BSS-MSC M 3-4
Response Request 3.2.2.28 BSS-MSC O 1
Cell Identifier List (Preferred) 3.2.2.27 BSS-MSC M 2n+3 to 7n+3
Circuit Pool List 3.2.2.46 BSS-MSC O V
Current Channel Type 1 3.2.2.49 BSS-MSC O 2
Speech Version (Used) 3.2.2.51 BSS-MSC O 2
Queueing Indicator 3.2.2.50 BSS-MSC O 2
Old BSS to New BSS Information 3.2.2.59 BSS-MSC O 2-n
That is why the MSC does not send "Classmark information 3" to the target BSC during the interBSC handovers, which has nothing to do with the original BSC.
The figure below is the collected signal flow at A interface of the target BSC:

For the content of message Handover Request, see the figure below:

From the figure above, we can see that there is no "Classmark information 3", which contains the
information of the MS multiple-band capacity, namely which bands the MS supports. The main
content of the message is as follows:
Multiband Supported (3 bit field)
Band 1 supported (third bit of the field)
0 P-GSM not supported
1 P-GSM supported
Band 2 supported (second bit of the field)
0 E-GSM or R-GSM not supported

1 E-GSM or R-GSM supported

Band 3 supported (first bit of the field)
0 DCS 1800 not supported
1 DCS 1800 supported
The indication of support of P-GSM band or E-GSM or R-GSM band is mutually exclusive.
When the 'Band 2 supported' bit indicates support of E-GSM or R-GSM, the presence of the <R
Support> field, see below, indicates if the E-GSM or R-GSM band is supported.
In this version of the protocol, the sender indicates in this field either none or two of these 3
bands supported. However, if only one band is indicated, the receiver shall ignore the Associated
Radio Capability 2.
For single band mobile station all bits are set to 0.
A5/4
0 encryption algorithm A5/4 not available
1 encryption algorithm A5/4 available
A5/5
0 encryption algorithm A5/5 not available
1 encryption algorithm A5/5 available
A5/6
0 encryption algorithm A5/6 not available
1 encryption algorithm A5/6 available
A5/7
0 encryption algorithm A5/7 not available
1 encryption algorithm A5/7 available
From the GSM Protocol 08.08, we can view Handover Request message, in which "Classmark
information 3" is optional. Whether the message contains it depends on whether the MSC has
received "Classmark information 3" from the MS before. The content of message Handover
Request is as below:
INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN
Message Type 3.2.2.1 MSC-BSS M 1
Channel Type 3.2.2.11 MSC-BSS M 5-10
Encryption Information 3.2.2.10 MSC-BSS M 3-n
Classmark Information 1 Or 3.2.2.30 MSC-BSS M 2
Classmark Information 2 3.2.2.19 MSC-BSS M 4-5
Cell Identifier (Serving) 3.2.2.17 MSC-BSS M 5-10
Priority 3.2.2.18 MSC-BSS O 3
Circuit Identity Code 3.2.2.2 MSC-BSS O 3
Downlink DTX Flag 3.2.2.26 MSC-BSS O 2
Cell Identifier (Target) 3.2.2.17 MSC-BSS M 3-10
Interference Band To Be Used 3.2.2.21 MSC-BSS O 2
Cause 3.2.2.5 MSC-BSS O 3-4

Classmark Information 3 3.2.2.20 MSC-BSS O 3-14

Current Channel type 1 3.2.2.49 MSC-BSS O 2
Speech Version (Used) 3.2.2.51 MSC-BSS O 2
Group Call Reference 3.2.2.55 MSC-BSS O 3-8
Talker Flag 3.2.2.54 MSC-BSS O 1
Configuration Evolution Indication 3.2.2.57 MSC-BSS O 2
Chosen Encryption Algorithm (Serving) 3.2.2.44 MSC-BSS O 2
Old BSS to New BSS Information 3.2.2.59 MSC-BSS O 2-n
LSA Information 3.2.2.23 MSC-BSS O 3+4n
LSA Access Control Suppression 3.2.2.61 MSC-BSS O 2
As the "Classmark information 3" is optional, the handover will not fail for lack of it.
To summarize, when the MS hands over successfully from GSM900 cell to GSM1800 cell (the
original cell and the target cell are at different BSCs.), the message Handover Request that the
MSC produced by manufacturer S delivers to the target BSC does not contain "Classmark
information 3" because the MSC does not support the dual band function. Then, there is no
"system information 5ter" in the system information that the network delivers to the MS over
SACCH because the BSC produced by M manufacturer does not receive "Classmark information
3". (The BSC produced by M manufacturer sends "system information 5ter" only when it receives
"Classmark information 3". Consequently, the MS at the GSM1800 cell cannot receive the
information of the hetero-band neighbor cell (GSM900 neighbor cell), which cause the failure in
the MS handing over back from GSM1800 to GSM900.
The BSC produced by Huawei decides whether to send "system information 5ter" according to
the frequency configuration in BA2 Table of the data configuration. Whether the MSC sends
"Classmark information 3" does not affect this procedure. If there is the frequency configuration
of the hetero-band, the Huawei BSC will deliver "system information 5ter". Such a problem will
not occur in the handover from GSM900 cell to GSM1800 cell.
46. Questions about the Inter-layer Handover Threshold and Inter-layer Handover
Hysteresis
Detail Description:
Do the inter-layer handover threshold and hysteresis adopted in 16 Bit sorting belong to serving cell or
the neighboring cell? Is it possible that the change of the inter-layer handover threshold and hysteresis
of 1800M cell in dualband networking can enable 1800M cell to load traffic?
Reply:
1. The inter-layer handover threshold and hysteresis adopted in 16bit sequence for the serving
cell and the neighboring cells are those defined respectively in BSC data configuration for both
cells. The two parameters are described in the internal cell data table for BSC internal cells and
in the external cell data table for external cells.
2. In dualband networking, it is possible to adjust the CRO cell parameters and give priority for
the higher layer in 1800M cells. And it is also possible to lower the inter-layer HO threshold
and hysteresis of the 1800M cell or to increase the inter-layer HO threshold and hysteresis of
the 900M cell. This is because the adjustment of inter-layer HO threshold and hysteresis might
have great influence on 16 bit sorting (Bit 14). After the setup above, the receiving level of
1800M cell complies with the demand of inter-layer HO threshold and hysteresis and is sorted
in priority. The inter-layer HO threshold must not be below the Edge HO threshold. Otherwise,
Ping-Pong handover might occur. In theory, the 16 Bit sorting of 900M cells can be lowered by
setting its HO threshold. and hysteresis higher and the edge HO to 900M cell is therefore

unlikely to occur on the mobile. MS can be kept in 1800M cell. However, the MS might be
hindered from handover to the neighboring cell of 900M cell through edge HO and the session
might be of poor quality or even drop if the inter-layer threshold and hysteresis of the 900M
cell is increased too much.
Suppose the inter-layer HO threshold and hysteresis of the 900M cell is 25/3 and the layer is 3,
the inter-layer HO threshold of the 1800M cell is 20/3 with the layer 2, the sorting of the
neighboring cells is as follows:
No.
S
N
Rxlev(s)
Rxlev(n)
S(bit14) N(bit14)
HOs triggered
1
900
1800 >-88
>-87
0
0
Inter-layer HO
2
900
1800 >-88
<-87
0
1
None
3
900
1800 <-88
>-87
1
0
Inter-layer HO
4
900
1800 <-88
<-87
1
1
Edge HO (rare)
5
1800 900
>-93
>-82
0
0
None
6
1800 900
>-93
<-82
0
1
None
7
1800 900
<-93
>-82
1
0
EdgeHO (pssiblty)
8
1800 900
<-93
<-82
1
1
Edge HO(rare)
Note:
1(1) The HOs in the table above include edge HO or inter-layer HO, exclude the emergency HOs
which might occur. The sorting for emergency HOs is done according to the receiving level of the
neighboring cells.
2(2) PBGT handover does not occur because 1800 cells and 900 cells have the different layer, but
emergency HOs, edge HOs and load HOs might occur between 1800M cell and 900M cell.
(3) Edge HOs are prior to inter-layer HOs. The prerequisite for inter-layer handover is that the
serving cell does not reach the edge handover threshold.
47. Questions about the interval of HOs in dualband network
Detail Description:
Q 1: How long is the interval for the initial handover under the following situation? How to
calculate it? What is the function of the parameters such as Min interval for TCH HOs, Filter
length for TCH level, and Edge HO watch time?
11. The parameter Min interval for TCH HOs in the [Handover control data table]: 6 seconds.
A timer must be started when a new TCH channel is assigned. Handover is possible only when
the timer is expired and the parameter Min interval for TCH HOs is the time limit of the timer.
12. In the [Filter Data Table], the parameter Filter length for TCH level is 6. This parameter
indicates the number of MRs to be used to do TCH signal strength averaging calculation.
23. Edge HO watch time is 4/3 second.
34. Sent Frequency of preprocessed MR: 1 time per second, 15:1 configuration.
Q 2:
How to shorten the time of the initial handover?
Q 3:
When the Sent Frequency of preprocessed MR is one time per second and configured as 15:1,
is it possible to change the parameter Filter length for TCH level to 3 which means 3 MRs are
to be sent within 3 seconds?
Reply:
Answer to Q1:

The time limit is the minimum interval of the initial TCH handover. That is, handover is not to
occur even when the PN criterion is satisfied. When the session goes beyond the limit, the time
limit is invalid. Filter length for TCH level functions during the average of the MR. If the
parameter is 6, make average of the MRs from NO.1 to No.6 to get a filter measurement report.
Edge HO watch time is 4/3 indicates that three of four MRs within four seconds must satisfy
the handover demand if one survey report comes at a second in a succession of filter MRs. The
first initial handover can be triggered only when the three terms above are satisfied. The last two
terms must be satisfied for sessions that last long. This is the PN criterion.
Answer to Q2:
Min interval for TCH HOs can be shortened to 2 or 4 second, or the PN can be set as 2/3, or the
filter length is set as 4.
Answer to Q3:
Yes. The value of parameters are defined in Network Planning Data
Configuration Criteria.
Besides, when the Sent Frequency of preprocessed MR is one time per second and configured
as 15:1, increase handover speed by following the answers to Q2 and shorten the filter length for
TCH level because one MR is reported by BTS every time.
48. Problems triggered by load handover?
Detail Description:
11. How does the system measure TCH occupation ratio in load handover algorithm?
2. Once the load handover is triggered in the system, under what circumstance will it stop? Does
the load handover stop only when it is completed?
Reply:
1. Every five seconds the system measures the TCH occupation ratio of the current serving cell
(the number of occupied TCHs / total of channels in the cell) and compare the result with the
parameter ClsLevel/ClsAcc. Load Handover occurs in the following cases:
1 The system flow is lower than a certain level threshold
The system flow of the serving cell is higher than Load HO Starting Thrsh
1 The target cell flow is lower than Load HO Receiving Thrsh
2 The RX level of the target cell is higher than Intercell HO Thrsh+Hysteresis
3 The RX level of the serving cell level is in the load HO band.
4 The cells are in the same BSC
Once the Load HO is triggered and each MR is reported every 0.5 second within the Load HO
step period, the system will judge that the level of the subscriber is within Load HO step level
and measure the load of its serving cell and target cell (reported once every 0.5 second). If the
load is qualified for HO, the subscriber will handover to the target cell, otherwise, the subscriber
will be given up. The system will wait for the next MR and perform handover for two subscribers
which are qualified within two Load HO step level. The handover will end when the load of the
serving cell is lower than the threshold or the load of the target cell is higher than the threshold.
2. Once the serving cell load is lower than Load HO Thrsh, or the load of the neighboring cell
is higher than Load HO Receiving Thrsh, the handover ends immediately.
49. Must the target cell switch on the Load HO control during the load handover?

Detail Description:

If one of the two neighboring cells switches on Load HO control and the other not, will a
handover occur between them? Will the successful handover rate be affected?
Reply:
The cell that switches on Load HO control and is qualified for load HO will handover to the other
one (which is qualified as a HO target cell).
Load HO is meant to reduce traffic in case of high load. Switch on only the Load HO control of
some cells with heavy load. It is a traffic bypass method in special cases (such as meeting, party,
and big events). If the cell is loaded with heavy traffic for long, expansion is the critical solution.
The setting of the parameter related to Load HO will influence the sorting of the candidate cells.
Improper setting may affect the HO success rate of the whole network. For details, refer to
PBGT HO Failure due to Load HO Thrsh in A Collection of GSM Network Planning and
Optimization Cases No. 1-20020605-A-1.0.
50. Emergency handover
Detail Description:

Is it necessary to judge whether the target cell reaches level threshold of the candidate
cell during emergency handover?
Reply:
Yes, it is. The reason is that cells lower than Handover Candidate Cell Minimum Downlink
Power threshold cannot enter candidate cell queue, thereby causing no handover.
In addition, Minimum Access Level Offset should be also considered. This offset is based on
Handover Candidate Cell Minimum Downlink Power. Different offsets can be defined for
different neighbor cells. To enter the candidate queue, corresponding neighbor cells must be
greater than the sum of Handover Candidate Cell Minimum Downlink Power plus this offset.
Value range: 0~63
Unit: level class value
Recommended value: 0
Level of effect on equipment: level 0; level of effect on network service: level 0
51. Circinal coverage within concentric cells and bad conversation quality
Detail Description:

In a GSM network, concentric cells are configured with 6 TRXs. Among them, those with
5 and 13 as the carrier number are set to outer circle and configured with PBU and those
with 0, 1,2 and 3 as the carrier number are set to inner circle and configured with
SCU+CDU. Two kilometers away from the BTS, the downlink received level of outer
circles is about -80dBm and that of inner circles has decreased to -90~-100dBm.
However, this positon features even landform and from which the BTS can be seen
because there is no high buildings though there are thin woods. The BTS tower is 60m
high; the antenna features high gain of 18dBi; there is a tower mounted amplifier; the
antenna azimuth just directs at bad coverage areas and the mechanical downtilt is 5. By

checking, the hardware is normal. But great downlink loss still occurs to inner circles
after replacing CDU and SCU and switching over the antenna feeder.
Reply:
Based on uplink/downlink balance traffic measurement analysis,the carrier measurement reports
on concentric circles with 0, 1, 2 and 3 as the carrier number are partial to level 1, 2, 3 and 4. This
indicates downlink loss is really great and on-site phenomena accord with traffic measurement
data. Inner circles must have greater loss than outer circles because SCU+CDU configuration is
adopted. Since SCU and CDU are replaced and the antenna feeder is exchanged, hardware faults
can be excluded. This cell antenna, 60m high, just directs at covered objects and its downtilt is 5.
Based on estimation, it is not in zero point areas. Based on the current ordinary concentric circle
handover alogrithm, outer and inner circle areas are jointly determined by received level
threshold, received level hysteresis, received quality threshold, TA threshold and TA hysteresis.
The field test shows that the outer and inner border of this cell is away 1.5~2 kilometers and
current parameter settings are unreasonable. Therefore, the following modifications are
recommended:
Received level threshold: 26 -> 35
Received level hysteresis:8 -> 5
Assigned preferred level threshold: 26 -> 35
At present, the on-site BSC version is 01.06.1120. After the current BSC version is upgraded to
02.06.1120 version, it is recommended to enable enhanced concentric circle alogrithm to make
MS subscribers gradually hand over to inner circle cells from outer circle cells when outer cells
are congested.
After modifying above parameters, observe TCH congestion and perform field tests.
52. Maximum times of sending
synchronous/asynchronous Handover

HANDOVER

ACCESS

message

during

the

Detail Description:

How many HANDOVER ACCESS message should be sent during MS handover?

Reply:
During the synchronous handover, the MS sends four HANDOVER ACCESS messages
continuously. And the HANDOVER FAILURE
message will be returned to the original channel.
The asynchronous handover is stated in 0408 protocol:
After having switched to the assigned channels, the mobile station starts repeating the
HANDOVER ACCESS message in successive layer 1 frames on the main DCCH and optionally
on the SACCH. This message is sent in an access burst. Its content is reduced to the handover
reference information element. The mobile station starts timer T3124 at the start point of the
timeslot in which the HANDOVER ACCESS message is sent the first time on the main DCCH.
On the mobile station side, if timer T3124 times out (only in the non- synchronized case) or if a
lower layer failure happens on the new channel before the HANDOVER COMPLETE message
has been sent, the mobile station deactivates the new channels, reactivates the old channels,
reconnects the TCHs if any and triggers the establishment of the main signaling link. It then sends
a HANDOVER FAILURE message on the main signaling link and resumes normal operation as
if no handover attempt had occurred. The operational parameters (e.g. ciphering mode) when
returning on the old channel are those applied before the HANDOVER COMMAND message
was received.

The above descriptions show that the MS continuously sends HANDOVER ACCESS message
until physical messages are received or timer T3124 times out during the asynchronous handover.
For handovers on the TCHs, T3124 equals 320ms and 320/4.615=69 is obtained. That is to say,
the MS at most sends 69 HANDOVER ACCESS messages in successive frames. For SD
handovers, T3124 equals 675ms and 675/4.615=146 is obtained. That is to say, the MS at most
sends 146 HANDOVER ACCESS messages in successive frames.
53. Trigger conditions of Huawei intra-cell handoff and effect on the network
Detail Description:
During the implementation of a project, customers require using intra-cell handoff function just
like Motorola, which is not recommended in the guide. Can you provide specific intra-cell
handoff principles, trigger conditions, handoff threshold, handoff control, signaling flow, and
possible effect of enabling intra-cell handoff system on network index.
Reply:
1. When triggering a handoff with bad quality, select the outgoing cell handoff first and then
trigger intra-cell handoff if there is no other candidate cell and intra-cell handoff is enabled.
2. When triggering an interference handoff, select a candidate cell based on the normal order.
Select this cell if it is in the first place and the intra-cell handoff function is enabled.
Otherwise, select the second candidate cell.
3. Beginning with G3BSC32.10102.06.1120A version, channels on carriers different from those
occupied by the call before the handoff are preferred to guarantee QoS during originating an
intra-cell handoff.
4. Determine whether to allow intra-cell handoff. Intra-cell handoff is to change the timeslot and
hand off to another carrier. It can improve bad propagation caused by intra-frequency
interference but cannot differentiate temporary interference from time dispersion. Intra-cell
handoff does not work well for time dispersion. In addition, this parameter does not affect
intelligent underlay-overlay (IUO) handoff.
For networks with frequency hopping enabled, enabling intra-cell handoff function may result in
more handoff failures, thereby affecting handoff success ratio.
54. Must the inter-layer handoff target cell be in the first position?
Detail Description:

Must the inter-layer handoff target cell be in the first position? As described in Huaweis
Handoff Problems Analysis, the target cell only should be before the serving cell. But
there is another description that the target cell must be in the first position in some
examinations or answers. Which one is correct?
Reply:
Requirements for inter-layer handoff are as follows:
Serving cell: Null
Target cell: Meet the following conditions at the same time:
1.The target cell has higher layer priority than the serving cel.
2.The target cell level is greater than target cell inter-layer handoff threshold + target cell interlayer handoff hysterersis.
3. The target cell is before the serving cell.

If an inter-layer handoff is triggered, the target cell triggered by the system must be a neighbor
cell satisfying inter-layer handoff trigger conditions and being in the first position in the
integrated sequencing. Note that the system continuously sequences at most 6 neighbor cells
based on sequencing requirements for different handoff algorithms. If an inter-layer handoff is
triggered, it indicates that the serving cell or neighbor cell fails to satisfy trigger requirements for
emergency handoff, load handoff and edge handoff with higher priority.
55. Preferred voice version switchover and interface phase flag
Detail Description:
In an office, Huawei BSC is mounted under the Huawei MSC and Motorola BSC is under the
Alcatel MSC. The ratio of handoff into Huawei BSC (MSC) is very low, about 50~60%. Tests
show that all subsequent handovers controlled by Huawei switch fail. By analyzing, it is
discovered that Motorola BSC and Alcatel MSC adopt phase 2 but Huaweis adopts phase 2+.
Although both enable EFR function, Alcatel switch (handover) prefers FR. A further test shows
that the handset adopts EFR at the Motorola BTS in the case of Alcatel switch-controlled
handover. After being handed over to Huawei MSC, Alcatel MSC prefers FR and Huawei
successfully designates EFR in the case of handover to Motorola MSC again. While the handset
adopts EFR at Huawei BTS in the case of Huawei switch-controlled handover and after being
handed over to Motorola MSC. However, handover from Motorola MSC to Huawe MSC fails,
representing that Alcatel MSC sends ABORT after Huawei MSC returns HANDOVER REQ
ACK.
However, it is impossible to modify Motorola BSC and Alcatel MSC into PHASE 2+. Therefore,
Huawei MSC does not support handoff preferred version.
Please provide answers to the following two questions:
11. Can the BSC prefer handoff voice version?

2. Does Huawei BSC (MSC) support EFR after they are switched back to phase 2.
Reply:
1. The BSC obtains the voice version actually used based on the voice version required by the
MSC and the one supported by itself. Therefore, on-site engineers can modify the voice version
supported by Huawei by modifying Huawei circuit pool configuration.
2. The current version of Huawei BSC supports adopting EFR under phase 2. However, EFR
function should be enabled under phase 2+ based on the protocol. If the interconnected MSC
adopts EFR under phase 2, Huawei BSC supports corresponding flows.

56. Difference of BSC level and cell level handovers in traffic measurement
Detail Description:
The traffic measurement shows that Attempted intercell handovers on BSC level are 1/2 of
Successful intercell handovers on the cell level.
Attempted intercell handovers (BSC level)
Successful intercell handovers
(BSC level)
Attempted intercell handovers
(cell level)
Successful
intercell handovers
(cell level)
678 651 1361 1307
192 178 379 349

Reply:
11. Intra-BSC attempted intercell handovers (BSC level traffic measurement: Start the
measurement after the handover algorithm decision, the source cell sends an Intercell Handover
Request message to target cell, and source cell is different from the target cell)
2. Intra-BSC successful intercell handovers (BSC level traffic measurement: Start the measurement
after the MS accesses successfully target cell, BSC sends a HANDOVER PERFORMED message
to MSC)
13. Intercell handover requests (cell level traffic measurement: Attempted intra-BSC incoming cell
handovers + inter-BSC incoming cell handover requests + attempted intra-BSC outgoing cell
handovers + attempted inter- BSC outgoing cell handovers)
24. Successful intercell handovers (cell level traffic measurement: Successful intra-BSC incoming
cell handovers + successful inter-BSC incoming cell handovers + successful intra- BSC outgoing cell
handovers + successful inter- BSC outgoing cell handovers)
From the above descriptions, Item 3 and 4 intercell handovers are sum of intra-BSC (incoming cell +
outgoing cell) handovers + inter-BSC (incoming cell + outgoing cell) handovers. Because the existing
network has no inter-BSC handovers, inter-BSC handovers are 0, and the values of item 3 and 4 are
twice of item 1 and 2 respectively.

57. 2G/3G reselection and handover

Detail Description:
11. When the UE transits from a GSM network to a WCDMA network, in the sentence In case of a
cell reselection occurring within the previous 15 seconds, XXX_Qoffset is increased by 5 dB
described in the 3GPP 0508-8m0.doc, a cell reselection means 2G3G reselection or 3G2G
reselection, or no difference.
22. In the case of 2G3G reselection, UE raises the minimum requirement of quality (RSCP&ECNO)
for 3G target cell. Whether the requirement discriminates CS or PS? How to discriminate them about
the parameters?
3. UE realizes the PS handover from GSM to WCDMA through the cell reselection. Whether to
configure minimum requirement of quality for RSCP&ECNO of WCDMA cell in a GSM network?
What are the configured parameters? How about the recommended value?
14. If CS handover from GSM to WCDMA is realized, whether there is the minimum requirement of
quality for WCDMA target cell? What are the configured parameters? How about the recommended
value for RSCP and ECNO respectively?
5. How to prohibit CS handover from GSM to WCDMA but support PS handover from GSM to
WCDMA?

Reply:
11. XXX_Qoffset is a 2G3G reselection parameter, but this parameter is not used in the case of 3G
2G reselection. Therefore, a cell reselection means 2G cell2G cell or 3G cell2G cell. The serving
cell of 2G delivers XXX_Qoffset to MS through SI.
12. In the case of 2G3G reselection, UE has the minimum requirement of quality (RSCP&ECNO)
for 3G target cell. This requirement does not discriminate CS and PS. The requirement for target cell
is as follows:
1) The MS reselects a suitable UTRAN cell if its measured RSCP value exceeds the
value of RLA_C for the serving cell and all of the suitable non-serving GSM cells by

the value XXX_Qoffset for a period of 5 seconds and, for FDD, the UTRAN cells
measured Ec/No value is equal or greater than the value FDD_Qmin. In case of a cell
reselection occurring within the previous 15 seconds, XXX_Qoffset is increased by 5
dB
2) If the cell reselection is performed within previous 15 seconds, XXX_Qoffset
increases by 5 dB.
3) MS cannot return to UTRAN within the previous 5 seconds from UTRAN cell to
GSM cell.
4) 3G target cell is a proper cell (greater than the minimum quality and level). This
item is optional. The protocol describes that the parameters required to determine if
the UTRAN cell is suitable are broadcast on BCCH of the UTRAN cell. An MS may
start reselection towards the UTRAN cell before decoding the BCCH of the UTRAN
cell, leading to a short interruption of service if the UTRAN cell is not suitable.

The target cell requires the same CS and PS, but they are controlled by different parameters. In a 2G
system, two parameters Qsearch_I and Qsearch_P control whether to start the reselection
towards 3G cell in idle mode or packet mode respectively.
Description of parameter Qsearch_I (3G cell search threshold in idle mode) is as follows:
1 Vale: 015
2 Unit: class
3 Default value:15
In the idle mode, the MSs search for cells when cell reselection level is less than (07) but greater than
(8-15). 0 = - 98 dBm, 1 = - 94 dBm, , 6 = - 74 dBm, 7 = (always) 8 = - 78 dBm, 9 = - 74 dBm,
, 14 = - 54 dBm, 15 = (never).
Default value = (never).
Description of parameter Qsearch_P (3G cell search threshold in packet mode) is as follows:
1 Value: 015
2 Unit: class
3 Default value: 15
In the packet idle mode, the MSs search for cells when cell reselection level is less than the threshold
(0-7): - 98, - 94, , - 74 dBm, (always) or higher than the threshold (8-15): - 78, - 74, , - 54
dBm, (never). Default value = (never).
13. The UE realizes PS services handover towards WCDMA from GSM. At that time, for minimum
quality requirements for RSCP and Ec/No of target WCDMA cell configured in GSM, see the
parameter setting in 2. XXX_Qoffset (FDD_Qoffset) is defaulted to 0dB, and Ec/No(FDD_Qmin) is
defaulted to 10, indicating -19.5dB (the value ranges from 0 to 49, indicating from -24 0dB, increased
by 0.5dB).
The recommended values are set based on scenarios and application requirements, for example,
1 Started from the protocols in September 2003, FDD_Qmin is set to the following value range
through the CR GP-032221:
Para. Explain value default
FDD_Qmin A minimum threshold for Ec/No for UTRAN FDD cell re-selection,
0= -20dB, 1= -6dB, 2= -18dB, 3= -8dB, 4= -16dB, 5= -10dB, 6= -14dB, 7= -12dB.
Default value= -12dB 0-7 3 BCCH D/L
1 If the MS updates the location based on GP-032221, set FDD_Qmin to -8dB. Compared with the
starting measurement threshold of cell reselection towards to 3G from 2G (-14dB), the difference is
6dB, so the ping-pong reselection towards 3G from 2G decreases because of signal fluctuation.

14. When CS services handover towards to a WCDMA network from a GSM network is performed,
the minimum quality requirements for WCDMA target cell are raised. Min. RSCP Thrsh and Min.
Ec/No Thrsh of 3G cell are set in 2G BSC. The two parameters are different from the settings in cell
reselection. In the case of reselection towards 3G cell from 2G cell, the two parameters configured in
2G serving cell take effect. In the case of handover towards 3G cell from 2G cell, the 3G cell
attributes set in the Cell External Attributes list take effect. The two parameters are defaulted to 10.
The RSCP must be greater than -100dBm, and Ec/No greater than -19.5dB (Ec/No corresponds to
-14dB, that is, 20.)
In the SI of 2G serving cells, according to the parameter FDD_REP_QUANT, the measurement report
decides to use RSCP or Ec/No. 2G BSC decides the type of measurement report based on the
parameter and judges whether 3G cell meets the requirements for handover and reselection. If the type
of measurement report is determined, the algorithm parameters (including best cell threshold and cell
handover offset) use the threshold corresponding to the type of measurement report. If RSCP is used,
the Ec/No parameter cannot be reference and reverse.
2G handover type is controlled by the BSC.
1 Whether CS services handover towards 2G cells (serving cell) from 2G cell is controlled by the
following parameters:
(1) Description of QSearch_C (SI parameter) is as follows:
1 Value:015
2 Unit: class
3 Default value: 15
In the connect mode, the MS searches the 3G cells when the cell reselection level is less than the
threshold (0-7) or higher than the threshod (8-15), 0 = - 98 dBm, 1 = - 94 dBm, , 6 = - 74 dBm, 7
= (always) 8 = - 78 dBm, 9 = - 74 dBm, , 14 = - 54 dBm, 15 = (never).
Default value = (never).
(2) Outgoing system handover granted (cell handover parameter)
1 Different preference strategies for handover to target cell are controlled by the following two
parameters:
(1) 2G/3G cell handover preference -- 0 indicates 2G cell handover preference, 1 indicates 3G
cell handover preference, and 2 indicates 2G cell preference based on the priority.
(2) 2G cell preference threshold when 2G/3G cell handover preference is set to 2: if the receiving
level of the first candidate neighbor cell in a 2G network is less than or equals to 2G cell
preference threshold, hand off to 3G cell first. Otherwise, hand off to 2G cells.
1 Huawei 2G BSC supports handover to better cells in a 3G network.
5. If Qsearch_C (3G cell search threshold in connect mode) is defaulted to Never according to
descriptions of answer 4, CS handover from 2G to 3G is prohibited. If Qsearch_P (3G cell search
threshold in packet mode) is set to Never, the UE does not perform PS reselection towards 3G cells. If
this value is not set to Never, select a proper value, that is, enable the PS reselection towards to 3G
cells.

58. Partial MSs fail to start reselection towards 3G cell from 2G cell
Detail Description:
1. Huawei BSC and RNC are mounted in Huawei MSC, and 2G BSC version is

GBSC32.10101.07.1120A..
The network collaboration strategy is to allow 2G3G cell reselection but forbid 2G 3G cell
handover. 3G neighbor cells of GSM related cell are added to BSC. The test shows that Sony Ericsson
Z1010 MSs have 2G3G reselection for five times, but Huawei U626 MSs and Moto A385 NSs
cannot start reselection towards 3G network in the same place. 2G 3G handover related parameters
are configured based on Huawei guides and suggestions of technical support experts. The settings of
related parameters are as follows:
1 Qsearch_I=7
FDD_Qoffset=0
Qsearch_C=7
Outgoing-RAT HO Allowed=1
MIN RSCP Thrsh=10

Reply:
The parameters are configured correctly. To realize 2G cell3G cell reselection, configure the
following parameters:
1Qsearch_I (3G cell search threshold in idle mode)
2FDD_Qoffset(FDD cell reselection level offset)
3FDD_Qmin(minimum requirement for Ec/No of 3G cell)
4 Qsearch_I=7 (always search for cell)
5 FDD_Qoffset=0 (always select a cell if acceptable)
6 FDD_Qmin is defaulted to 10, namely, -19.5dB (recommended as 20, that is, -14dB).
The above parameters decide that dual-mode MS can start reselection towards 3G cell if 3G cell meets
the requirement of Ec/No.
Qualcomm terminals fail to start reselection towards 3G network from 2G network. You can read the
GSM system information (SI) from the Probe records. The SI2quater includes reselection threshold
only, without the information of 3G neighbor cells. MS starts the reselection towards the cell through
the inter-system reselection threshold and information of neighbor cells in the SI2quater, so MS
cannot reselect the cell without the information of neighbor cells.

Figure 1 SI2quater when MS fails to transit from 2G to 3G

The analysis is as follows:
The G3BSC32.10100.07.1120A starts to support 2G3G reselection and handover. According to 3GPP
protocol, BSC adds three bytes to the last of CLASSMARK ENQUIRY message from MSC. A
problem is present when Samsung MSs process the CLASSMARK ENQUIRY message, and the
call cannot be connected. The patch SP01 helps solve the problem.
1Reserve the parameter to control whether the solution takes effect. For details, reserve one digit of
the parameter FDD_Qoffset, that is, the eighth digit (counting from o from low to top). If this digit is
1, it is normal and the modification using the patch does not take effect. If this digit is 0, MSC version
in SI3 is Release '98 or older. Otherwise, fill in the version based on the data configuration, and
delete the optional bit SI2quater Indicator struct (as shown in Figure 1) from SI3. This bit ID is sent
to SI2 quarter on BCCH or extended BCCH.
The description of SI2quater Indicator struct in the protocol is as follows:
SI2quater Indicator struct
The presence of this field indicates that the SI2quater message is broadcast.
0 SI2quater_POSITION (1 bit field)
1 This field indicates where the SYSTEM INFORMATION TYPE 2 quater message is
sent:
2 0--- SYSTEM INFORMATION TYPE 2 quater message is sent on BCCH Norm
3 1--- SYSTEM INFORMATION TYPE 2 quater message is sent on BCCH Ext.
2SI2quater is received when MS works in idle mode and indicates the SI related to neighbor cells of
inter-system reselection. For example, 900 MHz serving cell is 900 MHz cell, and the frequency of
900 MHz neighbor cell is in the SI2 and 2bis. The frequency of 1800 MHz cell is in SI2ter, and the
frequency of 3G neighbor cell and related reselection information is in SI2quater.

When the parameter FDD_QoffsetBSC is set to FEFF, SI2quater is not indicated in SI3. In fact, the
system broadcasts SI2quater, but most MSs do not read the entire SI2quater and fails to obtain the
information of 3G neighbor cells, so the cell reselection is not present. Sony Ericsson MSs read all the
information of SI2quater without considering the indication in SI3, so the reselection is successful.

Figure 2 SI3 content before and after modification of reserved parameters

After the path function is disabled on site, SI2quater_POSITION (as shown in figure 2) in SI3 is
sent, and the SI2quater received by MS includes the information of 3G neighbor cell (as shown in
Figure 3), MS can start the reselection towards 3G network. Disable the CLASSMARK
ENQUIRY to mitigate the call failure by Samsung MSs.
SI2quater is present

Figure 3 SI2quater received by MS after parameter modification

59. An MS handing over from a 900MHz cell to an 1800MHz cell with weak signals.
Detail Description:
The equipments area are all Huawei equipments. The level for the 900MHz cell is -58 dBm, and
the level for the 1800MHz cell is -80 dBm. MS started conversation in 900MHz cell first, but it
still handed over to an 1800MHz cell. Is this handover normal?
Reply:
It is normal. In this case, the MS triggers the inter-layer hierarchical handover from a 900MHz
cell to a 1800MHz cell.
The on-site parameters are configured as follows:

The 1800MHz cells are in layer 2.

The 900MHz cells are in layer 3.

The inter-layer handover threshold is 25.

The inter-layer handover hysteresis is 3.

When the MS keeps conversation in a 900MHz cell, the conditions triggerred the MS to hand
over to a 1800MHz cell according to inter-layer hierarchical handover as follows:

The priority class of the layer and level of the target 1800MHz cell is higher than that of the
900MHz service cell.

The level of the target 1800MHz cell is greater than the sum of the inter-layer handover
threshold and inter-layer handover hysteresis.

According to 16bit queuning rules, the target 1800MHz cell queues ahead of the 900MHz
service cell.
If the previous conditions are met, the MS will hand over from a 900MHz cell to a 1800MHz cell
even if the level of the 900MHz cell is 22 dB greater than that of the 1800MHz cell.
In fact, this is determined by the handover strategies of the dual-band network. The purpose is to
make the 1800MHz cells absorb more traffic to ease the traffic load of the 900MHz cells. When
the priority class of a 1800MHz cell is higher than that of a 900MHz cell, if the level of the
1800MHz cell is greater than the sum of the inter-layer hanover threshold and the inter-layer
handover hysteresis and the traffic load of the 1800MHz cell is lower than the load handover
receiving threshold, the MS will hand over to the 1800MHz cell regardless of the level of the
900MHz cell.

60. Priority to enable load handover and half rate function.

Detail Description:
If both the load handover threshold and the half rate adjust threshold are 80% according to BSC
data configuration, which one is enabled first when the load reaches 80%?
Reply:
The half rate adjustment will be triggered first. The load handover threshold means that the load
handover is started when the load in the corresponding cell exceeds this threshold. That is, the
load handover is started when the seized TCHs reach the corresponding percentage in a cell.
TCH rate adjust traffic threshold (%) is one of the factors enabling a full rate TCH to be
converted into a half rate TCH. Only when the traffic volume (seized channels in the cell /total
available channels in the cell) is greater than this threshold and the TCH rate adjust allowed is
positively set, then will a full rate TCH can be converted into a half rate TCH so as to expand
system capacity.
For the BSCs of C12 earlier, after the host converts a full rate TCH into a half rate TCH during
channel allocation, only the next call can seize the half rate TCH, and the current call can only
seize the full rate TCH.
For the BSCs of C12 later, if the host performs half rate allocation according to the channel
allocation algorithm, and if no half rate is available in a cell, the host will convert a full rate TCH
into a half rate TCH and allocate it to the current call.
The following introduces the priority to enable load handover and half rate function.
According to call flow, TCH rate adjust is triggered during TCH assignment. For load
handover, however, it is triggered by the BSC according to handover decision flow. That is, after
TCH assignment and call setup, the BSC triggers the load handover upon receiving the valid
measurement report submitted by BTS. Therefore, the TCH rate adjustment is triggered first.