Alarm Description
The BTS checks whether there are TRX- and channel-level service faults according to the
TRX signaling messages. This alarm is reported when a service fault is detected.
This alarm has multiple tributaries, each of which has its own determining algorithm and
related parameters. For details, see the help information for the LST
GLOCELLRLALMPARA command. Descriptions for each tributary (referred to as
Specific Problem) are as follows:
This tributary indicates that the configured channel status for the BTS is inconsistent with
that for the BSC. The alarm with this specific problem is reported when the BTS responds
to the BSC with the channel activation failure message five consecutive times for the same
channel. The alarm with this specific problem is cleared when all the channel activation
failures on a TRX are rectified.
This tributary indicates normal link establishment and abnormal link releases over the Um
interface. It is used to evaluate the quality of uplink and downlink channels over the Um
interface. When the total number of times a channel is occupied reaches the base value for
abnormal channel releases(the value is 100), the proportion of the number of abnormal
channel releases to the total number of times a channel is occupied is calculated. The alarm
with this specific problem is reported when this proportion reaches the alarm generation
threshold. The abnormal channel release is rectified when this proportion is less than the
alarm clearance threshold. The alarm with this specific problem is cleared when all the
abnormal channel releases on a TRX are rectified.
Total number of times a channel is occupied = Base value for abnormal channel releases x
Number of sub-channels contained in a channel
This tributary has two parameters: Abnormal Warn Threshold, and Abnormal Release
Threshold. You can run LST GLOCELLRLALMPARA command to query the preceding
parameters.
The alarm with this specific problem is reported when the proportion of number of MRs
indicating uplink and downlink imbalance to the total number of valid MRs is greater than
or equal to the value of Up Down Balance Alarm Threshold.
This tributary has one parameter: Up Down Balance Alarm Threshold. You can run the
MML command LST GLOCELLRLALMPARA to query the preceding parameters.
This tributary indicates whether the call drop rate of the TRX is high.
When the call drop rate of a channel reaches High Call Drop Rate Fault Check Thres, the
BTS considers the call drop rate high. The alarm with this specific problem is reported
when the number of channels with a high call drop rate reaches CHA-LEV Call Drop Fault
Chan Meas Base(the value is 20) on a TRX. The alarm with this specific problem is cleared
when the high call drop rate on all the channels becomes the normal value.
This tributary has two parameters: High Call Drop Rate Fault Check Thres, and High Call
Drop Rate Fault Clear Thres. You can run the LST GLOCELLRLALMPARA command to
query the preceding parameters.
This tributary indicates whether the RX quality on the uplink channels of a TRX is bad.
The BTS considers the uplink quality of a channel bad when the following conditions are
met: The uplink quality value of the channel in a measurement report is higher than Bad
Channel Quality Threshold(the value is 5); the total number of measurement reports
received reaches Bad Chan Qua Fault Chan Measure Base(the value is 240); the ratio of the
number of measurement reports indicating bad uplink quality for a channel to the total
number of measurement reports received is higher than Bad Quality Failure Check
Threshold. The alarm with this specific problem is reported when the number of channels
with bad uplink quality reaches Number of Bad Quality Channels (the value is 2)on a TRX.
The alarm with this specific problem is cleared when all the channels with bad uplink
quality on the TRX are rectified.
This tributary has two parameters: Bad Quality Failure Check Threshold, and Bad Quality
Failure Clear Threshold. You can run the MML command LST GLOCELLRLALMPARA
to query the preceding parameters.
This tributary indicates whether the RX quality on the downlink channels of a TRX is bad.
The BTS considers the downlink quality of a channel bad when the following conditions
are met: The downlink quality value of the channel in a measurement report is higher than
Bad Channel Quality Threshold(the value is 5); the total number of measurement reports
received reaches Bad Chan Qua Fault Chan Measure Base(the value is 240); the ratio of the
number of measurement reports indicating bad downlink quality for a channel to the total
number of measurement reports received is higher than Bad Quality Failure Check
Threshold. The alarm with this specific problem is reported when the number of channels
with bad downlink quality reaches Number of Bad Quality Channels(the value is 2) on a
TRX. The alarm with this specific problem is cleared when all the channels with bad
downlink quality on the TRX are rectified.
This tributary has two parameters: Bad Quality Failure Check Threshold, and Bad Quality
Failure Clear Threshold. You can run the MML command LST GLOCELLRLALMPARA
to query the preceding parameters.
Alarm Attribute
Alarm Parameters
Impact on System
The signal levels on the uplink and downlink are imbalanced for the
TRX or its connected antenna system.
If the downlink signal level is low, the cell coverage area of the BCCH
TRX may shrink and non-BCCH TRXs may experience a low success
Alarm Severity Alarm Impact
rate of channel assignments or a high call drop rate.
If the uplink signal level is low, some MSs served by the BCCH TRX
that are on the edge of the cell may not be able to provide services even
when downlink signals are available, and non-BCCH TRXs may
experience a low success rate of channel assignments or a high call drop
rate.
The call drop rate of a channel is high. As a result, call drops frequently
occur on the TRX.
System Actions
None.
Possible Causes
Miscellaneous When the specific problems are Uplink and Downlink Imbalance,
High Call Drop Rate, Bad Uplink Quality, ad Bad Downlink
Quality, the cause is "Uplink or downlink interference."
When the specific problem is Release Abnormal, the causes are
as follows: (1) Uplink or downlink interference (2) Transmission
faults.
Prerequisites
Obtain the product documents and read the following chapters or documents:
Safety Information
Initial Configuration Guide
Preprocessing
Expand All
Configuration Handling
Remote Handling
Expand All
Onsite Preparation
Onsite Handling
Expand All
Related Information
None.