2G - OSS KPI v1.1

2G KPI, Performance and Alarm Monitoring
KPI Classification
Field Measurement KPI Classification
Field measurement KPI can be classified into the following category

Coverage
Accessibility
Retainability
Service Quality
Mobility
Field Measurement KPI Classification
Accessibility:
Call Setup Success Rate Usage:
SDCCH Blocking Rate Cell Availability
TCH Bocking Rate VAMOS Usage
GPRS Throughput
Retainability
Drop Call Rate Mobility
Handover Success Rate
Accessibility
Accessibility - CS
Key Performance Indicator ATP KPI Huawei Counter Counter Difination
CA303J:Call Setup Indications (Circuit Service)
CA300J:Channel Requests (Circuit Service)
((CA303J/CA300J)*(CA313/CA310)*(1- CA313:Successful Assignments
CSSR No
(CM30/K3003)))*100% CA310:Assignment Requests
CM30:Call Drops on SDCCH
K3003:Successful SDCCH Seizures
CA3030J:Call Setup Indications (SDCCH) (Circuit Service)
SDSR Yes (CA3030J-CM30)/K3000 CM30:Call Drops on SDCCH
K3000:SDCCH Seizure Requests
CA303J:Call Setup Indications (Circuit Service)
Immediate Assignment Success Rate No (CA303J/CA300J)*100%
CA300J:Channel Requests (Circuit Service)
K3001:Failed SDCCH Seizures due to Busy SDCCH
SDCCH Blocking Rate No (K3001/K3000)*100%
K3000:SDCCH Seizure Requests
K3021:Failed TCH Seizures due to Busy TCH (Signaling Channel)
TCH Blocking Rate No (k3021+K3011A)/(k3020+K3010A) K3011A: Failed TCH Seizures due to Busy TCH (Traffic Channel)
K3020: TCH Seizure Requests (Signaling Channel)
K3010A:TCH Seizure Requests (Traffic Channel)
K3021:Failed TCH Seizures due to Busy TCH (Signaling Channel)
K3011A: Failed TCH Seizures due to Busy TCH (Traffic Channel)
([K3021]+[K3011A]+[K3011B])/([K3020]+[ K3011B:Failed TCH Seizures in TCH Handovers due to Busy TCH
TCH Blocking Rate Including HandOver
K3010A]+[K3010B]) (Traffic Channel)
K3020: TCH Seizure Requests (Signaling Channel)
CA313:Successful Assignments
TCH Assignment Success Rate No (CA313/CA310)*100%
CA310:Assignment Requests
Call Flow - MTC
Call Setup
Immediate Assignment Success Rate :

(CA303J/CA300J)*100%
CA300J : Channel Requests
K3000: SDCCH Seizure Requests
SDSR :
K3020:TCH Seizure Requests (Signalling Channel)
(CA3030J-CM30)/K3000
K3003 : Successful SDCCH Seizures SDCCH Blocking Rate :

(K3001/K3000)*100%
CA303J : Call Setup Indications CSSR :

CA3030J : Call Setup Indications (SDCCH) ((CA303J/CA300J)*(CA313/CA310)*
(1-(CM30/K3003)))*100%
More than 1 counter can be triggered by same

signalling message. The different usually for
different resources, sample CA300j can be
triggered by Channel Request for SDCCH or
also FACCH.
Immediate Assignment
Basic Immediate Assignment signalling procedure:
CA300J : Channel Requests
CA303J : Call Setup Indications
Fig.1 Successful Immediate Assignment Fig.2 Failed Immediate Assignment
Immediate Assignment Success Rate : A: The BSC sends an IMM ASS REJ message due to no available channel
B: The BSC sends an IMM ASS REJ message due to channel activation failure
(CA303J/CA300J)*100% C: The BSC sends an IMM ASS REJ message due to channel activation timeout
If Immediate Assignment failures are due to no channel available (point A in Figure 2), this
means that there is SDCCH congestion.
If Immediate Assignment failures are due to channel activation failure or channel activation
timeout (points B, C in Figure 2) check hardware/software alarms.
TCH Assignment
TCH Assignment Success Rate:

(CA313/CA310)*100%
TCH Blocking Rate :

(K3021+K3011A)/(K3020+K3010A)
CA310 : Assignment Requests

CA313 : Successful
Assignments
TCH Assignment Failure
Check following counters to identify the reason for Assignment failure:
(1) Failures due to mismatch between the state machine of the BSC and the ASS REQ message or due to the abnormality of the ASS REQ
message:
(2) Failures due to abnormal radio resource allocation:
(3) Failures due to abnormal air interface access:
(4) Failures due to the abnormality of terrestrial resources or the call clearing performed by the MSC.
1. Failures due to mismatch between the state machine of the BSC and the ASS REQ message or due to the abnormality of the ASS REQ
- A3129I: CELL_ASS_FAIL_INVALID_STATE: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the
BSC receives an ASS REQ message that is not expected by the internal state machine of the BSC (for example, the state machine is in release
status).
- A3129J: CELL_ASS_FAIL_INVALID_MSG_CONTENTS: This counter provides the number of ASS FAIL messages sent by the BSC to the
MSC when the BSC receives an ASS REQ message but the ASS REQ message fails to be decoded (for example, an error occurs during the
decoding of an IE, such as CHANNEL TYPE, CIC, or Layer 3 header information).
- A3129E: CELL_ASS_FAIL_NO_CIC: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the BSC
receives an ASS REQ message that carries an unavailable A interface CIC.
- A3129F: CELL_ASS_FAIL_CIC_ALLOC: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the
BSC receives an ASS REQ message that carries an A interface CIC that is already occupied by another call.
2. Failures due to abnormal radio resource allocation:
- A312A: CELL_ASS_FAIL_Frst_ASS_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when
the cell does not have available channels and the directed retry procedure fails to be initiated or the directed retry is prohibited by the data
configuration in the first air interface assignment procedure.
- A312L: CELL_ASS_FAIL_RECONN_SUCC_ASS_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the
MSC when the cell does not have available channels and the directed retry procedure fails to be initiated or the directed retry is prohibited by
the data configuration in the air interface assignment procedure except for the first air interface assignment procedure.
- A312K: CELL_ASS_FAIL_Frst_DR_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when
the cell does not have available channels and the directed retry procedure is successfully initiated but failed due to no available channel in
the first air interface assignment procedure.
- A312M: CELL_ASS_FAIL_RECONN_SUCC_DR_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the
MSC when the BSC attempts to make a directed retry but the directed retry failed because the target cell does not have available channels
in the air interface assignment procedure except for the first air interface assignment procedure.
- A312F: CELL_ASS_FAIL_NO_IDLE_ABIS: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the
dynamic allocation of Abis resources is enabled on the BSC but the assignment fails due to no available Abis resources.
- A3129S: CELL_ASS_FAIL_NO_SPEECH_VER: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC
when the assignment fails because the intersection between the speech version set carried in the ASS REQ message from the MSC and the
speech version set supported by the current cell of the MS does not have available speech versions.
3. Failures due to abnormal air interface access:
- A3129C: CELL_ASS_FAIL_Frst_ASS_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when
the timer for the BSC to wait for an ASS CMP message expires after the BSC sends an ASS CMD message to the MS in the first air
interface assignment procedure.
- A3129P: CELL_ASS_FAIL_RECONN_SUCC_ASS_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the
MSC when the timer for the BSC to wait for an ASS CMP message expires after the BSC sends an ASS CMD message to the MS in the air
interface assignment procedure except for the first air interface assignment procedure.
- A3129O: CELL_ASS_FAIL_Frst_DR_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the
cell does not have available channels and the directed retry procedure is successfully initiated but failed due to the expiry of the timer for
waiting for an HO CMP message in the first air interface assignment procedure.
- A3129Q: CELL_ASS_FAIL_RECONN_SUCC_DR_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the
MSC when the timer for waiting for an ASS CMP message expires after the BSC sends an HO CMD message to the MS in the air interface
assignment procedure except for the first air interface assignment procedure.
- A3129D: CELL_ASS_FAIL_RECONN_SUCC_ASS_RECONN_SUCC: This counter provides the number of ASS FAIL or RR STATUS
messages reported by the MS to the BSC when the MS attempts but fails to access the new channel and then successfully reconnects to the
old channel after receiving an ASS CMD message.
- A3129R: CELL_ASS_FAIL_RECONN_SUCC_DR_RECONN_SUCC: This counter provides the number of HO FAIL or RR STATUS

messages reported by the MS to the BSC when the MS attempts but fails to access the new channel and then successfully reconnects to the
old channel after receiving an HO CMD message.
4. Failures due to the abnormality of terrestrial resources or the call clearing performed by the MSC.
- A3129B: CELL_ASS_FAIL_Frst_APPLY_TRSL_FAIL: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC
when the MS drops from the connection to the air interface, or a circuit fails to be obtained for the call, or the obtained circuit is faulty during the
circuit connection of the BSC in the first air interface assignment procedure.
- A3129N: CELL_ASS_FAIL_RECONN_SUCC_APPLY_TRSL_FAIL: This counter provides the number of ASS FAIL messages sent by the BSC
to the MSC when the MS drops from the connection to the air interface, or a circuit fails to be obtained for the call, or the obtained circuit is faulty
during the circuit connection of the BSC in the air interface assignment procedure except for the first air interface assignment procedure.
- A3129G: CELL_ASS_FAIL_A_INTERF_FAIL: This counter provides the number of times that the BSC locally releases the call when the BSC
receives an SS7 link abnormality indication in the assignment procedure.
- A3129H: CELL_ASS_FAIL_MSC_CLR_CMD: This counter provides the number of times that the BSC releases the call after receiving a
CLEAR CMD message from the MSC in the assignment procedure.
SDCCH Drop
Counter ID Counter Name Counter Description

1278072520 CELL.SD.CALL.DROPS CM30:Call Drops on SDCCH
This measurement provides the number of call releases by the BSC on the SDCCH
due to various reasons.
Measurement
Description
points
A1 The BSC receives an ERROR INDICATION message from the BTS because of the abnormal
connection on the radio link layer.
A2 The BSC receives a CONNECTION FAILURE INDICATION message from the BTS because of
link fault or hardware fault on the radio link layer
A3 Call Drops Due to REL IND Received in Stable State.
A4 Call Drops Due to No MR from MS for a Long Time,
Call Drops due to Abis Terrestrial Link Failure,
Call Drops Due to Equipment Failure,
Call Drops due to Resource Check,
A5 Clear Requests Sent on the A Interface
A6 Call Drops Due to Forced Handover
A10 Successful SDCCH Seizures (Call Type)
Call Drops on SDCCH = [Call Drops on Radio Interface (SDCCH)] (CM30A)
+ [Call Drops Due to No MR from MS for a Long Time (SDCCH)] (M302)
+ [Call Drops due to Abis Terrestrial Link Failure (SDCCH)] (M303)
+ [Call Drops Due to Equipment Failure (SDCCH)] (M304)
+ [Call Drops due to Forced Handover (SDCCH)] (M305)
SDCCH Failure Radio Causes
Call Drops on Radio Interface (SDCCH) =
[Call Drops due to ERR IND Received on SDCCH in Stable State (T200 Expired)] +
[Call Drops due to ERR IND Received on SDCCH in Stable State (Unsolicited DM Response)] + Error Indication
[Call Drops due to ERR IND Received on SDCCH in Stable State (Sequence Error)] +
[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Radio Link Failure)] +
[Call Drops due to CONN FAIL Received on SDCCH in Stable State (HO Access Failure)] +
Connection Failure
[Call Drops due to CONN FAIL Received on SDCCH in Stable State (OM Intervention)] +
Indication
[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Radio Resource Unavailable)] +
[Call Drops due to CONN FAIL Received on SDCCH in Stable State (Other Causes)] +
[Call Drops due to REL IND Received on SDCCH] +
[Failed Internal Intra-Cell Handovers (Timer Expired) (SDCCH)] +
[Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (Timer Expired) (SDCCH) (Excluding Directed Retry)] +
[Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (Timer Expired) (Directed Retry)] +
[Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (SDCCH) (Excluding Directed Retry)] +
[Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (Directed Retry)] +
[Failed Incoming External Inter-Cell Handovers (Timer Expired) (SDCCH)]
SDCCH Block

1278087420 CELL.KPI.SD.CONGEST K3001:Failed SDCCH Seizures due to Busy SDCCH
In the immediate assignment procedure, the BSC measures the counter in

the local cell when an SDCCH request fails because of no available SDCCH, as
shown by point C in Figure
For SDCCH Blocking analysis, check usage of SDCCH for each causes :
- Call Setup : CELL.ESTB.IND.MOC.NONSMS.SD (A3030A)
CELL.ESTB.IND.MTC.SD (A3030C)
- SMS : CELL.ESTB.IND.MOC.SMS.SD (A3030B)
- Location update : CELL.ESTB.IND.LOC.UPDATE.SD (A3030F)
- Emergency : CELL.ESTB.IND.ECALL.SD (A3030D)
- Reestablishment: CELL.ESTB.IND.CALL.REESTB.SD (A3030E)
TCH Block (1) Traffic Channel

1278087431 CELL.KPI.TCH.ASS.CONG.TRAF K3011A:Failed TCH Seizures due to Busy TCH (Traffic Channel)
This counter measures the number of failed TCH (traffic channel) seizures due to
no TCH available.
The BSC will assign a channel after receiving the ASSIGNMENT REQUEST message. If there is no channel available and the
BSC does not support queuing or directed retry, the BSC measures the counter.
After the BSC receives the ASSIGNMENT REQUEST message, if there is no channel available and the BSC supports
queuing, a timer is set to wait for an idle channel. If an idle channel becomes available before the timer expires, the BSC
successfully assigns the channel. If no idle channels exist when the timer expires and directed retry is not supported, the
BSC measures the counter.
Directed retry when the MRs reported by the MS have no target cell available.
Directed retry to another cell in the BSC. The originating cell receives the Intercell Handover Reject message from the
target cell. The measurement object is the originating cell.
Directed retry to another cell in the BSC. The handover fails and the MS reconnects to the original signaling channel. The
measurement object is the originating cell.
Directed retry to another cell in the BSC. The target cell response is not received within scheduled time. The
Directed retry to another cell in the BSC. The originating cell receives the Inter Clear Request message from the target
cell. This clear message is used to inform the originating cell of the directed retry failure and to request the originating
cell to clear the connection. The measurement object is the originating cell.
Directed retry to another cell in the BSC. The originating cell sends the MS a HANDOVER COMMAND message, requesting
the MS to access a new channel. If the originating cell does not receive the Inter Clear Request from the target cell within
scheduled time, the BSC measures the counter.
Directed retry to another BSC. The originating cell receives the Handover Reject message from the target BSC. The
TCH Block (1) Signaling Channel (FACCH)
1278087426 CELL.KPI.TCH.CONG.SIG K3021:Failed TCH Seizures due to Busy TCH (Signaling Channel)
This counter provides the number of times that the BSC has no TCH available in
the very early assignment of the TCH.
In the immediate assignment procedure, the BSC measures the counter when it
fails to allocate a TCH after receiving the CHAN RQD message from the BTS, as
shown by point A in Figure 1. The counter is measured in the cell where the TCH
fails to be allocated.
Accessibility - PS
Accessibility (E)GPRS
A9003:Number of Failed Uplink GPRS TBF Establishments due to No Channel
A9001:Number of Uplink GPRS TBF Establishment Attempts

( 1- (A9003+A9203) /
Uplink TBF establisth Success rate Yes
(A9001+A9201) ) *100%
A9203:Number of Failed Uplink EGPRS TBF Establishments due to No Channel
A9201: Number of Uplink EGPRS TBF Establishment Attempts
A9103:Number of Failed downlink GPRS TBF Establishments due to No Channel
A9101:Number of downlink GPRS TBF Establishment Attempts

( 1- (A9103+A9303) /
Downlink TBF establisth Success rate Yes
(A9101+A9301) ) *100% A9303:Number of Failed downlink EGPRS TBF Establishments due to No
Channel
A9301: Number of downlink EGPRS TBF Establishment Attempts
UL TBF Establishment
Successful TBF Establishment
Uplink TBF Establishment Success Rate

A9001:Number of Uplink GPRS TBF Establishment Attempts ( 1- (A9003+A9203) / (A9001+A9201) ) *100%
A9201:Number of Successful Uplink EGPRS TBF Establishments
A9002:Number of Successful Uplink GPRS TBF Establishments

A9202:Number of Successful Uplink EGPRS TBF Establishments
A9001:Number of Uplink GPRS TBF Establishment Attempts

In case no Radio Resource A9201:Number of Successful Uplink EGPRS TBF Establishments
A9003:Number of Failed Uplink GPRS TBF Establishments due to No Channel

A9201:Number of Uplink EGPRS TBF Abnormal Releases due to No Channel
UL GPRS TBF Establishment Failure - All
1.Identify the possible cause of the TBF establishment failures by checking the following counters:
A. UL GPRS TBF establishment failures:

- A9003:UP_GPRS_TBF_ESTB_FAIL_NO_CHAN_RES: number of failed uplink GPRS TBF establishments due to no channel available.
Indicates congestion on the TCH;
- A9004:UP_GPRS_TBF_ESTB_FAIL_MS_NO_RESP: number of failed uplink GPRS TBF establishments due to no response from MS.
Indicates bad RF conditions in the cell. Check cell coverage and interference.
- A9037:UP_GPRS_TBF_ESTB_FAIL_SEND_ASSMSG_FAIL: In dedicated mode, the BSS sends the resource assignment command to
the MS over the DCCH if both the network and the MS support DTM (Dual Transfer Mode simultaneous support of CS+PS service). If
the resource assignment command is not sent successfully and the establishment of the uplink GPRS TBF thus fails, this counter is
incremented by one.
- A9038:UP_GPRS_TBF_ESTB_FAIL_MS_RESP_ASS_FAILURE: In dedicated mode, the BSS sends the resource assignment command
to the MS over the DCCH if both the network and the MS support DTM (Dual Transfer Mode simultaneous support of CS+PS service). If
the MS responds with the resource assignment failure message and the establishment of the uplink GPRS TBF thus fails, this counter is
incremented by one.
- A9016:UP_GPRS_TBF_ESTB_FAIL_OTHER_CAUSE: This measurement provides the number of failed uplink GPRS TBF
establishments due to other causes in a granularity period. This may happen because an exception or failure occurs in the resource
assignment or the overload protection (flow control) is triggered. Check BSS alarms in order to locate possible faults in the equipment
(h/w or s/w).
UL EGPRS TBF Establishment Failure - All
B. UL EGPRS TBF establishment failures:

- A9203:UP_EGPRS_TBF_ESTB_FAIL_NO_CHAN_RES: number of failed uplink EGPRS TBF establishments due to no channel available.
- A9204:UP_EGPRS_TBF_ESTB_FAIL_MS_NO_RESP: number of failed uplink EGPRS TBF establishments due to no response from MS.
- A9235:UP_EGPRS_TBF_ESTB_FAIL_SEND_ASSMSG_FAIL: In dedicated mode, the BSS sends the resource assignment command to the
MS over the DCCH if both the network and the MS support DTM. If the resource assignment command is not sent successfully and the
establishment of the uplink EGPRS TBF thus fails, this counter is incremented by one.
- A9236:UP_EGPRS_TBF_ESTB_FAIL_MS_RESP_ASS_FAILURE: In dedicated mode, the BSS sends the resource assignment command to
the MS over the DCCH if both the network and the MS support DTM. If the MS responds with the resource assignment failure message and
the establishment of the uplink EGPRS TBF thus fails, this counter is incremented by one.
- A9216:UP_EGPRS_TBF_ESTB_FAIL_OTHER_CAUSE: This measurement provides the number of failed uplink EGPRS TBF establishments
due to other causes in a granularity period. This may happen because an exception or failure occurs in the resource assignment or the
overload protection (flow control) is triggered. Check BSS alarms in order to locate possible faults in the equipment (h/w or s/w).
DL TBF Establishment
Successful TBF Establishment
In case no Radio Resource
A9101:DL GPRS TBF Establishment Attempts

A9101:DL GPRS TBF Establishment Attempts
A9301:DL EGPRS TBF Establishments Attempt
A9301:DL EGPRS TBF Establishments Attempt
A9103: GPSR TBF Est. Fail due to No Channel
A9102: Successful DL GPRS TBF Establishments A9303: GPSR TBF Est. Fail due to No Channel
A9302: Successful DL EGPRS TBF Establishments
Downlink TBF Establishment Success Rate

( 1- (A9103+A9303) / (A9101+A9301) ) *100%
DL GPRS TBF Establishment Failure - All
C. DL GPRS TBF establishment failures:
- A9103:DOWN_GPRS_TBF_ESTB_FAIL_NO_CHAN_RES: number of failed downlink GPRS TBF establishments due to no channel available.
- A9104:DOWN_GPRS_TBF_ESTB_FAIL_MS_NO_RESP: number of failed downlink GPRS TBF establishments due to no response from MS.
- A9135:DOWN_GPRS_TBF_ESTB_FAIL_SEND_ASSMSG_FAIL: In dedicated mode, the BSS sends the resource assignment command to
the MS over the DCCH if both the network and the MS support DTM. If the resource assignment command is not sent successfully and the
establishment of the downlink GPRS TBF thus fails, this counter is incremented by one.
- A9136:DOWN_GPRS_TBF_ESTB_FAIL_MS_RESP_ASS_FAILURE: In dedicated mode, the BSS sends the resource assignment command
to the MS over the DCCH if both the network and the MS support DTM. If the MS responds with the resource assignment failure message and
the establishment of the downlink GPRS TBF thus fails, this counter is incremented by one.
- A9115:DOWN_GPRS_TBF_ESTB_FAIL_OTHER_CAUSE: This measurement provides the number of failed downlink GPRS TBF
establishments due to other causes in a granularity period. This may happen because an exception or failure occurs in the resource
assignment or the overload protection (flow control) is triggered. Check BSS alarms in order to locate possible faults in the equipment (h/w or
s/w).
DL EGPRS TBF Establishment Failure - All
D. DL EGPRS TBF establishment failures:
- A9303:DOWN_EGPRS_TBF_ESTB_FAIL_NO_CHAN_RES: number of failed downlink EGPRS TBF establishments due to no

channel available. Indicates congestion on the TCH;
- A9304:DOWN_EGPRS_TBF_ESTB_FAIL_MS_NO_RESP: number of failed downlink EGPRS TBF establishments due to no

response from MS. Indicates bad RF conditions in the cell. Check cell coverage and interference.
- A9333:DOWN_EGPRS_TBF_ESTB_FAIL_SEND_ASSMSG_FAIL: In dedicated mode, the BSS sends the resource assignment

command to the MS over the DCCH if both the network and the MS support DTM. If the resource assignment command is not sent
successfully and the establishment of the downlink EGPRS TBF thus fails, this counter is incremented by one.
- A9334:DOWN_EGPRS_TBF_ESTB_FAIL_MS_RESP_ASS_FAILURE: In dedicated mode, the BSS sends the resource assignment

command to the MS over the DCCH if both the network and the MS support DTM. If the MS responds with the resource assignment
failure message and the establishment of the downlink EGPRS TBF thus fails, this counter is incremented by one.
- A9315:DOWN_EGPRS_TBF_ESTB_FAIL_OTHER_CAUSE: This measurement provides the number of failed downlink EGPRS

TBF establishments due to other causes in a granularity period. This may happen because an exception or failure occurs in the
resource assignment or the overload protection (flow control) is triggered. Check BSS alarms in order to locate possible faults in the
equipment (h/w or s/w).
TBF Establishment Failure Corrective Actions
1. If TBF establishment failure is due to congestion in TCH,

- Check availability of current and neighbouring sites in order to make sure that TCH congestion is not due to
unavailability issues.
Check FR/HR parameterization (including AMR if enabled in the network). Check usage of HR resources.
Check Load balancing configuration between cells.
Add TRX.
2. If TBF establishment failure is due to poor RF quality, then:

Check cell coverage and interference.
Check signal strength and quality in Huawei 2G system.
Adjust antenna parameters (tilt, azimuth) to improve coverage and/or suppress interference in the problematic areas.
Check antenna line (feeders, jumpers) to identify faulty connections.
Check BTS hardware (relative alarms) to identify faulty TRXs.
3. If TBF establishment failure is due to equipment fault, check relative BSS alarms (hardware and software alarms) in order to
identify the faulty part. Repair or replace the faulty equipment once found.
Retainability
Retainability

CM33:Call Drops on TCH
TCH Drop Rate Yes CM33/K3013A
K3013A:Successful TCH Seizures (Traffic Channel)
K3014: Traffic Volume on TCH
EMD (Erlang Minutes Drop) No 60*K3014/CM33
CM33:Call Drops on TCH
TCH Drop Rate
TCH Drop Rate

CM33/K3013A * 100%

1278087432 CELL.KPI.TCH.ASS.SUCC.TRAF K3013A:Successful TCH Seizures (Traffic Channel)
K3013A :
If the assignment procedure is successful, the BSC sends the ASSIGNMENT
COMPLETE message to the MSC and measures the counter. See measurement point
B
K3013A : Successful TCH Seizures
(Traffic Channel)
CM33 : Call Drop on TCH
1278072498 CELL.TRAF.CH.CALL.DROPS CM33:Call Drops on Traffic Channel
CM33 :
This counter provides the number of call drops due to various reasons after the MS seizes a
traffic channel and before the BSC receives the CLEAR CMD message from the MSC.
Call Drops on Traffic Channel (CM33)=

[Call Drops on Radio Interface in Stable State (Traffic Channel)]
+ [Call Drops on Radio Interface in Handover State (Traffic Channel)]
+ [Call Drops Due to No MR from MS for a Long Time (Traffic Channel)]
+ [Call Drops due to Abis Terrestrial Link Failure (Traffic Channel)]
+ [Call Drops due to Equipment Failure (Traffic Channel)]
+ [Call Drops due to Forced Handover (Traffic Channel)]
+ [Call Drops due to local switching Start Failure]
+ [Call Drops due to Failures to Return to Normal Call from local switching]
Assignment and intra-cell Handover
Measurement Description
points
A1 Call Drops Due to ERR IND Received in Stable State
A2 Call Drops Due to the CONN FAIL IND Received in Stable State
A3 Call Drops Due to REL IND Received in Stable State
Call Drops due to Abis Terrestrial Link Failure,
Call Drops Due to Abis Link Failures in Stable Local Switch State,
Call Drops Due to Resource Check,
Call Drops Due to Other Causes in Stable State,
Call Drops Due to Handover Failure During the Local Switch
A5 Clear Requests Sent on the A Interface, Call Drops after Answer
A6 Call Drops Due to Forced Handover,
Failed Internal Intra-Cell Handovers (Timer Expired)
A7 Call Drops Due to Equipment Failure, Call Drops Due to Local Switch
Start Failure
A8 Successful TCH Seizures,
Call Drops Due to Failures to Return to Normal Call from Local Switch
A9 Successful Connections
Intra BSC Handover Procedure
Measurement Description
points
A1 Call Drops Due to ERR IND Received in Stable State
A2 Call Drops Due to the CONN FAIL IND Received in Stable State
A3 Call Drops Due to REL IND Received in Stable State
Call Drops Due to Abis Terrestrial Link,
Call Drops Due to Abis Link Failures in Stable Local Switch State,
Call Drops due to Resource Check,
Call Drops due to Other Causes Received in Stable State
A5 Clear Requests Sent on the A Interface,
Call Drops after Answer
A6 Call Drops Due to Forced Handover,
Failed Internal Intra-Cell Handovers (Timer Expired),
Failed Outgoing Internal Inter-Cell Handovers (Timer Expired),
Call Drops Due to Handover Failure During the Local Switch
A8 Successful TCH Seizures
A9 Successful Connections
A10 Successful SDCCH Seizures (Call Type)
TCH Drop Causes
Call Drop on Radio Interface

1278072502 CELL.TRAF.CH.CALL.DROPS.IN.STABLE.STATE CM330:Call Drops on Radio Interface in Stable State (Traffic Channel)
CM330 Description :
This measurement provides the number of calls released because of the ERR IND, CONN FAIL
IND, and REL IND messages received by the BSC after the MS seizes a traffic channel.
Call Drops on Radio Interface in Stable State (Traffic Channel): indicates RF issue.
Check coverage at drop points; check interference in the cell; check for missing
neighbours.
TCH Drop Causes
Call Drop on Radio Interface in Handover State

1278072503 CELL.TRAF.CH.CALL.DROPS.HO.FAIL CM331:Call Drops on Radio Interface in Handover State (Traffic Channel)
CM331 Description :
During the handover process, this measurement provides the number of times that the timer for the target cell waiting for the handover
completion expires if the MS fails to access the new channel at the radio interface, or the number of times when the timer for the
originating cell waiting for the handover completion expires if the MS fails to return to the original channel.
This counter is calculated at A6, as shown previous figure
Call Drops on Radio Interface in Handover State (Traffic Channel): drops during handover procedure; check the handover failure counters to get
more details for the handover failure cause
TCH Drop Causes
Call Drop Due to No MR from MS for a Long Time

1278072516 CELL.TRAF.CH.CALL.DROPS.NO.MR CM332:Call Drops Due to No MR from MS for a Long Time (Traffic Channel)
CM332 Description :
After seizing a TCH, the MS sends a measurement report to the BSC every 480 ms. If the BSC does not receive any measurement
report within a certain period (five minutes, by default), it deems that a call drop occurs on the Um interface.
This measurement provides the number of call releases by the BSC because the BSC does not receive any measurement report on the
traffic channel within a certain period.
Call Drops due to No MRs from MS for a Long Time (Traffic Channel):
Check UL coverage/UL interference at drop points. Check for possible MS problem.
TCH Drop Causes
Call Drop due to Abis Terrestrial Link Failure

1278072517 CELL.TRAF.CH.CALL.DROPS.ABIS.LNK.FAIL CM333:Call Drops due to Abis Terrestrial Link Failure (Traffic Channel)
CM333 Description :
If the terrestrial link on the Abis interface seized by the call fails (BSC detects a broken RSL ) after the MS seizes a channel, the BSC
releases the call.
This measurement provides the number of call releases by the BSC due to the terrestrial link failure over the Abis interface on the traffic
channel.
Call Drops due to Abis Terrestrial Link Failure (Traffic Channel): indicates Abis transmission problem. Check relative alarms.
TCH Drop Causes
Call Drop due to Equipment Failure

1278072518 CELL.TRAF.CH.CALL.DROPS.EQUIP.FAIL CM334:Call Drops due to Equipment Failure (Traffic Channel)
CM334 Description :
After the MS seizes a channel, if the status of the BSC internal resources is abnormal, the BSC releases the call that seizes the
abnormal resources.
This measurement provides the number of call releases by the BSC on the traffic channel due to an abnormal internal resource status.
This counter is measured in the following situations:

A call drop occurs because of any of the following: TRX mutual aid; dynamic modification of cell attributes, TRX frequencies, or
TRX FH data; dynamic deletion of TRXs; TRX deactivation.
The timer set to wait for the outgoing BSC handover command expires, or the clear request message is received from the MSC
before the timer expires, and the handover cause is other causes than OM intervention, MSC triggering, or preemption.
A call drop occurs because of call assignment failure during the handover.
The MSC cannot send a short message because of the restriction on sending downlink short messages in data configuration or
because of flow control, and then the call is released.
A call drop occurs because of software error.

Call Drops due to Equipment Failure (Traffic Channel): indicates BSS hardware or software problem. Check relative alarms.
TCH Drop Causes
Call Drop due Forced Handover

1278072519 CELL.TRAF.CH.CALL.DROPS.FORCE.HO CM335:Call Drops due to Forced Handover (Traffic Channel)
CM335 Description :
After the MS seizes a traffic channel, the BSC initiates forced handover in the case of channel preemption, channel failure, or channel
blocking. If the handover of the MS fails, the BSC releases the call.
This measurement provides the number of call releases by the BSC on the traffic channel due to forced handover failure.

Retainability - PS
Retainability - PS

A9006:Number of Uplink GPRS TBF Abnormal Releases due to N3101 Overflow
(MS No Response)
1(A9006+A9206+A9118+A9318)/
TBF completion Success rate Yes (A9501+A9507)*100% A9206:Number of Uplink EGPRS TBF Abnormal Releases due to N3101
Overflow (MS No Response)
A9501:Number of Uplink Assignments
A9507:Number of Downlink Assignments
TBF Drop
- KPI formula:
Uplink GPRS TBF Drop Rate = (([Number of Uplink GPRS TBF Abnormal Releases due to N3101 Overflow (MS No Response)]+[Number of Uplink
GPRS TBF Abnormal Releases due to N3103 Overflow (MS No Response)])
/[Number of Successful Uplink GPRS TBF stablishments])*{100}
Uplink EGPRS TBF Drop Rate = (([Number of Uplink EGPRS TBF Abnormal Releases due to N3101 Overflow (MS No Response)]+[Number of Uplink
EGPRS TBF Abnormal Releases due to N3103 Overflow (MS No Response)])
/[Number of Successful Uplink EGPRS TBF Establishment])*{100}
Downlink GPRS TBF Drop Rate = ([Number of Downlink GPRS intermit transfers]/[Number of Successful Downlink GPRS TBF Establishments])*{100}
Downlink EGPRS TBF Drop Rate = ([Number of Downlink EGPRS intermit transfers]
/[Number of Successful Downlink EGPRS TBF Establishments])*{100}
Analysis process:
1.Identify the possible cause of the TBF drops by checking the following counters:
A. UL GPRS TBF Drops:

- A9006:UP_GPRS_TBF_ABNORM_REL_N3101_OVERFLOW: Number of Uplink GPRS TBF Abnormal Releases due to N3101 Overflow (MS No
Response). Indicates poor radio conditions in the cell. Check signal level, signal quality and interference in the cell.
- A9007:UP_GPRS_TBF_ABNORM_REL_N3103_OVERFLOW: Number of Uplink GPRS TBF Abnormal Releases due to N3103 Overflow (MS No
Response). Indicates poor radio conditions in the cell. Check signal level, signal quality and interference in the cell.
TBF Drop UL GPRS
Additional UL GPRS TBF abnormal releases:
- A9008:UP_GPRS_TBF_ABNORM_REL_SUSPEND: number of uplink GPRS TBF abnormal releases due to cell suspension. This may
happen because the MS often initiates CS services during the process of PS services. Another possible cause is that the cell is on the edge of
the network location area and therefore the location update of the MS is frequent.
- A9009:UP_GPRS_TBF_ABNORM_REL_FLUSH: number of uplink GPRS TBF abnormal releases due to cell flush. This may happen
because the cell reselection procedure is frequently initiated by the MS.
- A9010:UP_GPRS_TBF_ABNORM_REL_NO_CHAN_RES: number of uplink GPRS TBF abnormal releases due to no channel. Indicates that
the channel malfunction is frequent or the channel is blocked manually. Also indicates congestion on the traffic channel. To guarantee stable
PS service in a cell with heavy CS traffic, add fixed packet channels.
- A9017:UP_GPRS_TBF_ABNORM_REL_CHAN_PREEMPT: number of uplink GPRS TBF abnormal releases due to channel preemption.
Preemption may happen because congestion occurs on the Abis interface or the dynamic PDCHs in use are occupied by the CS services.
Check relative alarms to locate the cause.
- A9018:UP_GPRS_TBF_ABNORM_REL_OTHER_CAUSE: number of uplink GPRS TBF abnormal releases due to other causes. This may
happen because of incorrect parameters or the number of uplink GPRS TBFs on the PDCH reaches the limit or the cell is manually blocked.
Check relative alarms to locate the cause.
- A9034: UP_GPRS_TBF_ABNORM_REL_EGPRS_TBF_CONNECT: number of abnormal uplink GPRS TBF releases due to the access of the
EGPRS service.
- A9039:UP_GPRS_TBF_ABNORM_REL_CS_HO: number of uplink GPRS TBF abnormal releases due to CS handover.

TBF Drop UL EGPRS
B. UL EGPRS TBF Drops:
- A9206:UP_EGPRS_TBF_ABNORM_REL_N3101_OVERFLOW: Number of Uplink EGPRS TBF Abnormal Releases due to N3101
Overflow (MS No Response). Indicates poor radio conditions in the cell. Check signal level, signal quality and interference in the cell.
- A9207: UP_EGPRS_TBF_ABNORM_REL_N3103_OVERFLOW: Number of Uplink EGPRS TBF Abnormal Releases due to N3103
Overflow (MS No Response). Indicates poor radio conditions in the cell. Check signal level, signal quality and interference in the cell.
Additional UL EGPRS TBF abnormal releases:

- A9208:UP_EGPRS_TBF_ABNORM_REL_SUSPEND: number of uplink EGPRS TBF abnormal releases due to cell suspension. This may
happen because the MS often initiates CS services during the process of PS services. Another possible cause is that the cell is on the edge
of the network location area and therefore the location update of the MS is frequent.
- A9209:UP_EGPRS_TBF_ABNORM_REL_FLUSH: number of uplink EGPRS TBF abnormal releases due to cell flush. This may happen
because the cell reselection procedure is frequently initiated by the MS. Check and tune if necessary cell reselection parameters in the
area.
- A9210:UP_EGPRS_TBF_ABNORM_REL_NO_CHAN_RES: number of uplink EGPRS TBF abnormal releases due to no channel. Indicates
that the channel malfunction is frequent or the channel is blocked manually. Also indicates congestion on the traffic channel. To guarantee
table PS service in a cell with heavy CS traffic, add fixed packet channels.
- A9217:UP_EGPRS_TBF_ABNORM_REL_CHAN_PREEMPT: number of uplink EGPRS TBF abnormal releases due to channel
preemption. Preemption may happen because congestion occurs on the Abis interface or the dynamic PDCHs in use are occupied by the
CS services. Check relative alarms to locate the cause.
- A9218:UP_EGPRS_TBF_ABNORM_REL_OTHER_CAUSE: number of uplink EGPRS TBF abnormal releases due to other causes. This
may happen because of incorrect parameters or flow control or the cell is manually blocked. Check relative alarms to locate the cause.
- A9237:UP_EGPRS_TBF_ABNORM_REL_CS_HO: number of uplink EGPRS TBF abnormal releases due to CS handover.

TBF Drop DL GPRS
C. DL GPRS TBF Drops:
- A9118:DOWN_GPRS_TRANS_INTERRUPT_TIMES: number of intermitted downlink GPRS TBF transfers in a granularity period. The
counter is incremented because the downlink PDU buffer is emptied upon abnormal downlink GPRS TBF releases due to SUSPEND,
FLUSH, or failed downlink re-establishments due to other causes.
- A9106:DOWN_GPRS_TBF_ABNORM_REL_N3105_OVERFLOW: number of downlink GPRS TBF abnormal releases due to N3105

overflow. Indicates bad radio conditions in the cell. Check coverage and interference in the cell.
- A9107:DOWN_GPRS_TBF_ABNORM_REL_SUSPEND: number of downlink GPRS TBF abnormal releases due to cell suspension. This
may happen because the MS often initiates CS services during the process of PS services. Another possible cause is that the cell is on the
edge of the network location area and therefore the location update of the MS is frequent.
- A9108:DOWN_GPRS_TBF_ABNORM_REL_FLUSH: number of downlink GPRS TBF abnormal releases due to cell flush. This may
happen because the cell reselection procedure is frequently initiated by the MS. Check and tune if necessary cell reselection parameters in
the area.
- A9109:DOWN_GPRS_TBF_ABNORM_REL_NO_CHAN_RES: number of downlink GPRS TBF abnormal releases due to no channel.
Indicates that the channel malfunction is frequent or the channel is blocked manually. Also indicates congestion on the traffic channel. To
guarantee stable PS service in a cell with heavy CS traffic, add fixed packet channels.
- A9116:DOWN_GPRS_TBF_ABNORM_REL_CHAN_PREEMPT: number of downlink GPRS TBF abnormal releases due to channel
- A9117:DOWN_GPRS_TBF_ABNORM_REL_OTHER_CAUSE: number of downlink GPRS TBF abnormal releases due to other causes.
This may happen because of incorrect parameters or the number of uplink GPRS TBFs on the PDCH reaches the limit or the cell is
manually blocked. Check relative alarms to locate the cause.
- A9132:DOWN_GPRS_TBF_ABNORM_REL_EGPRS_TBF_CONNECT: number of abnormal downlink GPRS TBF releases due to the
access of the EGPRS service.
- A9137:DOWN_GPRS_TBF_ABNORM_REL_CS_HO: number of downlink GPRS TBF abnormal releases due to CS handover.
TBF Drop DL EGPRS
D. DL EGPRS TBF Drops:
- A9318:DOWN_EGPRS_TRANS_INTERRUPT_TIMES: number of intermitted downlink EGPRS TBF transfers in a granularity period. The
counter is incremented because the downlink PDU buffer is emptied upon abnormal downlink GPRS TBF releases due to SUSPEND,
FLUSH, or failed downlink re-establishments due to other causes.
- A9306:DOWN_EGPRS_TBF_ABNORM_REL_N3105_OVERFLOW: number of downlink EGPRS TBF abnormal releases due to N3105

overflow. Indicates bad radio conditions in the cell. Check coverage and interference in the cell.
- A9307:DOWN_EGPRS_TBF_ABNORM_REL_SUSPEND: number of downlink EGPRS TBF abnormal releases due to cell suspension.
This may happen because the MS often initiates CS services during the process of PS services. Another possible cause is that the cell is on
the edge of the network location area and therefore the location update of the MS is frequent.
- A9308:DOWN_EGPRS_TBF_ABNORM_REL_FLUSH: number of downlink EGPRS TBF abnormal releases due to cell flush. This may
happen because the cell reselection procedure is frequently initiated by the MS. Check and tune if necessary cell reselection parameters in
the area.
- A9309:DOWN_EGPRS_TBF_ABNORM_REL_NO_CHAN_RES: number of downlink EGPRS TBF abnormal releases due to no channel.
Indicates that the channel malfunction is frequent or the channel is blocked manually. Also indicates congestion on the traffic channel. To
guarantee stable PS service in a cell with heavy CS traffic, add fixed packet channels.
- A9316:DOWN_EGPRS_TBF_ABNORM_REL_CHAN_PREEMPT: number of downlink EGPRS TBF abnormal releases due to channel
- A9317:DOWN_EGPRS_TBF_ABNORM_REL_OTHER_CAUSE: number of downlink EGPRS TBF abnormal releases due to other causes.
This may happen because of incorrect parameters or overload protection (flow control) or the cell is manually blocked. Check relative
alarms to locate the cause.
- A9335:DOWN_EGPRS_TBF_ABNORM_REL_CS_HO: number of downlink EGPRS TBF abnormal releases due to CS handover.

Mobility
Mobility
CH313:Successful Outgoing Internal Inter-Cell Handovers
CH333:Successful Outgoing External Inter-Cell Handovers

HOSR Yes ([CH313]+[CH333])/([CH311]+[CH331])*100)
CH311:Outgoing Internal Inter-Cell Handover Commands per Cell
CH331:Outgoing External Inter-Cell Handover Commands

Inter Cell Handover
Handover Success Rate :

(CH313+CH333)/(CH311+CH331)*100)
CH311 : Number of Outgoing Internal Inter-

Cell Handover Commands
CH313 : Number of Successful Outgoing

Internal Inter-Cell Handovers
Inter Cell Handover Failure
Number of Unsuccessful Outgoing Internal Inter-Cell Handovers =

[Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (900/850/810-900/850/810)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (1800/1900-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (900/850/810-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (1800/1900-900/850/810)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (900/850/810-900/850/810)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (1800/1900-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (900/850/810-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (1800/1900-900/850/810)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (900/850/810-900/850/810)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (1800/1900-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (900/850/810-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (1800/1900-900/850/810)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (Directed Retry) (900/850/810-900/850/810)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (Directed Retry) (1800/1900-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (Directed Retry) (900/850/810-1800/1900)]
+ [Number of Unsuccessful Outgoing Internal Inter-Cell Handovers (Directed Retry) (1800/1900-900/850/810)]
Internal Handover (Intra-BSC)
Basic intra-BSC inter-cell handover signalling procedure:
The main causes for a failed outgoing internal inter-cell handover include:
1) Causes related to resource allocation:

- No traffic channel is available.
- No speech version is available.
- No Abis resource is available.
- The BSC fails to obtain the terrestrial resources.
2) Causes related to access on the Um interface

- The MS fails to access the new channel and then reconnects to the
old channel.
- The timer for the BSC to wait for an HO CMP message expires.
3) Abnormal causes
- The BSC fails to activate the allocated channel.
- A fault occurs on the A interface.
Internal Handover Failure - Resource
(1) The following counters are measured when the outgoing internal inter-cell handover fails because of failed allocation of relevant
resources.
- H312A:CELL_INTRABSC_OUTCELL_HO_FAIL_CONG: no channel is available in the target cell (congestion)

- H312L: CELL_INTRABSC_OUTCELL_HO_FAIL_NO_IDLE_ABIS: no circuit resource is available on the Abis interface in the target cell
when the Abis dynamic allocation is enabled (congestion on Abis)
- H312H:CELL_INTRABSC_OUTCELL_HO_FAIL_NO_SPEECH_VER: no proper speech version is available in the target cell; check
speech version configuration
- H312B:CELL_INTRABSC_OUTCELL_HO_FAIL_APPLY_TRSL_FAIL: BSC fails to obtain circuit resource when establishing the
terrestrial connection; check A interface circuit status; check A interface alarms
Internal Handover Failure Reconnect to old Channel
(2) The following counters provide the numbers of failed internal intra-cell handovers when the MS fails to access the new channel on the Um interface.
In the outgoing internal inter-cell handover procedure, the BSC sends an HO CMD message to the MS through the originating cell and initiates a timer
(T3103) to wait for a HO CMP message. If the MS reconnects to the old channel and sends a HO FAIL message on the old channel before the
timer expires, the following counters are measured in the originating cell based on the failure cause value:
- H312Da:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_UNS: Abnormal Release, Unspecified

- H312Db:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_CHN: Abnormal Release, Channel Unacceptable
- H312Dc:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_EXP: Abnormal Release, Timer Expired
- H312Dd:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_NO_ACT: Abnormal Release, No Activity on the
Radio Path
- H312De:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_PREEMPT: Preemptive Release
- H312Df:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_HO_TA: Timing Advance out of Range
- H312Dg:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_CH_MODE: Channel Mode Unavailable
- H312Dh:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_FREQ: Frequency Unavailable
- H312Di:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_C_CLR: Call Already Cleared
- H312Dj:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_SEMANT: Semantically Incorrect Message
- H312Dk:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_INV_MAN: Invalid Mandatory Information
- H312Dl:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_M_T_NE: Message Type Non-existent or Not Implemented
- H312Dm:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_M_T_NC: Message Type Not Compatible with Protocol State
- H312Dn:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_CONDIT: Conditional IE Error
- H312Do:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_NO_CA: No Cell Allocation Available
- H312Dp:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_PROTOCL: Protocol Error Unspecified
- H312Dq:CELL_INTRABSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_OTHER: Other Causes
Internal Handover Failure T3103 Expired
During the handover procedure excluding directed retry, after the BSC successfully allocates and activates the channel in the target cell,
it sends an HO CMD message to the MS and starts the timer T3103 to wait for the HO CMP message. If no HO CMP is received by
the BSC before T3103 expires, the BSC releases the call. Then, the specific one of the following counters is measured in the target
cell based on the type of the target channel, that is, signalling channel (SDCCH/TCHF/TCCH) or traffic channel (TCHF/TCHH):
- H3120C:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP_SD_NOT_INCLUDE_DR
- H3127Cb:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP_TCHF_SIG_NOT_INCLUDE_DR
- H3128Cb:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP_TCHH_SIG_NOT_INCLUDE_DR
- H3127Ca:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP_TCHF_TRAF_NOT_INCLUDE_DR
- H3128Ca:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP_TCHH_TRAF_NOT_INCLUDE_DR
In directed retry procedure, the BSC sends an HO CMD message to the MS through the originating cell and starts timer T3103 to wait for
an HO CMP message. If no HO CMP is received by the BSC before T8 expires, the following counter is measured:
- H3121C:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP_DR
Note: The counter CH312C:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP is the sum of all the above counters, i.e. the six counters
above are sub-items of this counter.
Internal Handover Failure Abnormal Causes
(3) The following counters are measured when the outgoing internal inter-cell handover fails because of equipment faults.
After the BSC successfully performs channel allocation and speech version confirmation in the target cell, it sends a CH ACT message to
the BTS for activating the channel, and starts the corresponding timer to wait for the response. If the BSC receives a CH ACT NACK
or no response from the BTS before the timer expires, the following counter is measured:
- H312I:CELL_INTRABSC_OUTCELL_HO_FAIL_CHACT_FAIL
If an outgoing internal intra-cell handover fails because the BSC locally releases the call after receiving an SS7 link abnormality
indication, the following counter is measured:
- H312G:CELL_INTRABSC_OUTCELL_HO_FAIL_A_INTERF_FAIL
External Handover (Inter-BSC)
Basic inter-BSC inter-cell handover signalling procedure:
The main causes for a failed outgoing

external inter-cell handover include:
1. The timer T7 for the BSC to wait for a HO CMD message, after having
sent a HO RQD message, expires.
2. The BSC receives a HO RQD REJ message from the MSC.
3. The MS fails to access the new channel and then reconnects to the
old channel, sending a HO FAIL message.
4. The timer T8 for the BSC to wait for a CLEAR CMD message , after
having sent a HO CMD message, expires.
5. The BSC receives a CLEAR CMD message from the MSC which
contains a failure handover cause.
6. An SS7 link failure occurs on the A interface

External Handover Failure T7 Expired
(1) During the outgoing external inter-cell handover procedure, timer T7 is started after the BSC sends the HO RQD to the MSC and waits for the
HO CMD command from the MSC. If no HO CMD is received by the BSC before T7 expires, the BSC re-sends the HO RQD message. The
specific counter provides the number of failed outgoing external inter-cell handovers when the number of resending times has exceeded the
maximum configuration.
In the outgoing external inter-cell handover (excluding directed retry) procedure, the following counters are
measured when T7 expires based on the channel type:
- H3320L:CELL_INTERBSC_OUTCELL_HO_FAIL_T7_EXP_SD_NOT_INCLUDE_DR
- H3327Lb:CELL_INTERBSC_OUTCELL_HO_FAIL_T7_EXP_TCHF_SIG
- H3328Lb:CELL_INTERBSC_OUTCELL_HO_FAIL_T7_EXP_TCHH_SIG
- H3327La:CELL_INTERBSC_OUTCELL_HO_FAIL_T7_EXP_TCHF_TRAF_CH
- H3328La:CELL_INTERBSC_OUTCELL_HO_FAIL_T7_EXP_TCHH_TRAF_CH
In the outgoing external inter-cell handover (directed retry) procedure, the following counter is measured:
- H3321L:CELL_INTERBSC_OUTCELL_HO_FAIL_T7_EXP_DR
External Handover Failure HO RQD REJ
(2) The following counters provide the number of times that the BSC terminates the outgoing external inter-cell handover because it receives
an HO RQD REJ message from the MSC after sending the HO RQD message to the MSC.
- H332Ka:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_OM_INTERVENTION: OM Intervention
- H332Kb:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_EQUIP_FAIL: Equipment Failure
- H332Kc:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_NO_RADIO_RES: No Radio Resource Available
- H332Kd:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_REQ_NO_TER_RES: Requested Terrestrial Resource Unavailable
- H332Ke:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_BSS_NOT_EQUIP: BSS not Equipped
- H332Kf:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_INVALID_CELL: Invalid Cell
- H332Kg:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_REQ_TRANS_NO_ADAPT: Requested Transcoding/Rate Adaption Unavailable
- H332Kh:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_CIRCUIT_POOL_MISMATCH: Circuit Pool Mismatch
- H332Ki:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_REQ_NO_SV: Requested Speech Version Unavailable
- H332Kj:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_CIPH_ALG_NOT_SUPPORT: Ciphering Algorithm not Supported
- H332Kk:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_TER_CIR_ALLOC: Terrestrial Circuit Already Allocated
- H332Kl:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_INVALID_MSG: Invalid Message
- H332Km:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_PROTOCOL_ERR: Protocol Error between BSS and MSC
- H332Kn:CELL_INTERBSC_OUTCELL_HO_REQ_REJ_OTHER: Other Causes
External Handover Failure Reconnect to Old Channel
(3) In the outgoing external inter-cell handover procedure, the BSC sends a HO CMD message to the MS through the originating cell and initiates
timer T8 to wait for a CLEAR CMD message from the MSC which will indicate Successful Handover. If the MS reconnects to the old channel
and sends an HO FAIL message on the old channel before T8 expires, the specific one of the following counters is measured in the target cell
based on the cause value in the HO FAIL message.
- H332Da:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_UNS: Abnormal Release, Unspecified

- H332Db:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_CHN: Abnormal Release, Channel
Unacceptable
- H332Dc:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_EXP: Abnormal Release, Timer Expired
- H332Dd:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_ABNORM_REL_NO_ACT: No Activity on the Radio Path
- H332De:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_PREEMPT: Preemptive Release
- H332Df:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_HO_TA: Timing Advance out of Range
- H332Dg:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_CH_MODE: Channel Mode Unavailable
- H332Dh:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_FREQ: Frequency Unavailable
- H332Di:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_CALL_CLR: Call Already Cleared
- H332Dj:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_SEMANT: Semantically Incorrect Message
- H332Dk:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_INVALID_MAN: Invalid Mandatory Information
- H332Dl:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_MSG_TYPE_NEXISTENT: Message Type Non-existent or Not
Implemented
- H332Dm:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_MSG_TYPE_NOT_COMPATIBLE: Message Type Not
Compatible with Protocol State
- H332Dn:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_CONDIT: Conditional IE Error
- H332Do:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_NO_CA: No Cell Allocation Available
- H332Dp:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_PROTOCL: Protocol Error Unspecified
- H332Dq:CELL_INTERBSC_OUTCELL_HO_FAIL_RECONN_SUCC_MS_RPT_OTHER: Other Causes
External Handover Failure T8 Expired
(4) In the outgoing external inter-cell handover procedure, after sending the HO CMD message to the MS, the BSC starts the timer T8 to
wait for the CLEAR CMD message from the MSC. The specific counter provides the number of times that the BSC terminates the
handover due to the expiration of T8.
In the outgoing external inter-cell handover (excluding directed retry) procedure, the following counters are measured when T8 expires
based on the channel type:
- H3320C:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP_SD_NOT_INCLUDE_DR
- H3327Cb:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP_TCHF_SIG
- H3328Cb:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP_TCHH_SIG
- H3327Ca:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP_TCHF_TRAF_CH
- H3328Ca:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP_TCHH_TRAF_CH
In the outgoing external inter-cell handover (directed retry) procedure, the following counter is measured:
- H3321C:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP_DR
Note: The counter CH332C:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP is the sum of all the above

counters, i.e. the six counters above are sub-items of this counter.
External Handover Failure CLEAR CMD from MSC
(5) The following counters provides the number of times that the BSC terminates the outgoing external inter-cell handover because the
BSC receives a CLEAR CMD message from the MSC and the cause value carried in the message is not Handover successful.
- H332Ha:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_RADIO_INTF_MSG_FAIL: Radio Interface Message Failure

- H332Hb:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_RADIO_INTF_FAIL: Radio Interface Failure
- H332Hc:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_OM_INTERVENTION: OM Intervention
- H332Hd:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_EQUIP_FAIL: Equipment Failure
- H332He:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_PREEMPTION: Preemption
- H332Hf:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_INVALID_MSG: Invalid Message
- H332Hg:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_PROTOCOL_ERR: Protocol Error between BSS and MSC
- H332Hh:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_OTHER: Other Causes
External Handover Failure A interface Failure
(6) The following counter provides the number of failed outgoing external inter-cell handovers when the BSC detects an SS7 link failure
on the A interface and releases the call:
- H332G:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_A_INTF_FAIL
Handover Failure Analysis
1. Check interference in source and target cells. High interference can cause handover failure.
2. Check whether ping-pong handover occurs due to no dominant server in the area. Ping-pong may lead to HO failures.
3. Parameters that affect HO Success Rate:
- T3103A: Timer started after the BSC delivers a HANDOVER COMMAND in an intra-BSC inter-cell handover. If the BSC receives a
HANDOVER COMPLETE message before this timer expires, the timer stops. If this timer expires, the BSC considers the handover
as failed. Recommended value: 10000 ms
- T7: Timer is started after the BSC sends the HO RQD to the MSC and waits for the HO CMD command from the MSC in an inter-BSC
inter-cell handover procedure. Recommended value: 10000 ms
- T8: After sending the HO CMD message to the MS, the BSC starts this timer to wait for the CLEAR CMD message from the MSC in an
inter-BSC inter-cell handover procedure. Recommended value: 10000 ms
Traffic, Payload & Throughput
Traffic
Hall Rate Traffic No K3034 K3034:TCHH Traffic Volume
k3014:TCH Traffic Volume
Full Rate Traffic No K3014-K3034
K3034:TCHH Traffic Volume
TCH Traffic No K3014 k3014:TCH Traffic Volume
SDCCH Traffic No K3004 K3004:Traffic Volume on SDCCH
K3040:Successful TCH Seizures
TCH Mean Holding time No (3600*(K3014/K3040))*100%
K3014: Traffic Volume on TCH
K3003:Successful SDCCH Seizures
SDCCH Mean Holding time No (3600*(K3004/K3003))*100%
K3004:Traffic Volume on SDCCH
Payload
L9202: Total Number of Uplink EGPRS MCS1 RLC Data Blocks
(L9202*22+L9203*28+L9204*37+L9205*44+L L9209: Total Number of Uplink EGPRS MCS8 RLC Data Blocks
9206*56+L9207*74+L9208*56+L9209*68+L92
Payload (Mbit) --EDGE No 10*74+L9302*22+L9303*28+L9304*37+L9305
L9302: Total Number of Downlink EGPRS MCS1 RLC Data Blocks
*44+L9306*56+L9307*74+L9308*56+L9309*6
8+L9310*74)*8/(1024*1024) L9303: Total Number of Downlink EGPRS MCS2 RLC Data Blocks
L9002:Total Number of Uplink RLC Data Blocks Using CS1
L9003:Total Number of Uplink RLC Data Blocks Using CS2
L9004Total Number of Uplink RLC Data Blocks Using CS3
L9002*23+L9003*34+L9004*40+L9005*54+L910 L9005:Total Number of Uplink RLC Data Blocks Using CS4
Payload (Mbit) --GPRS No
2*23+L9103*34+L9104*40+L9105*54)*8/(1024 L9102:Total Number of Downlink RLC Data Blocks Using CS1
*1024) L9103:Total Number of Downlink RLC Data Blocks Using CS2
L9104:Total Number of Downlink RLC Data Blocks Using CS3
Throughput
((L9102*23+L9103*34+L9104*40+L9105*54)*8*50 L9103:Total Number of Downlink RLC Data Blocks Using CS2

GPRS DL Throughput No /1024/(L9102+L9103+L9104+L9105))*AR9303 L9104:Total Number of Downlink RLC Data Blocks Using CS3
AR9303:Average Number of Available PDCHs
((L9302*22+L9303*28+L9304*37+L9305*44+ L9305: Total Number of Downlink EGPRS MCS4 RLC Data Blocks
L9306*56+L9307*74+L9308*56+L9309*68+L9310*74
)*8*50/1024/ L9306: Total Number of Downlink EGPRS MCS5 RLC Data Blocks
EDGE DL Throughput No
(L9302+L9303+L9304+L9305+L9306+L9307+(L9308
+L9309+L9310)/2))*AR9303
AR9303:Average Number of Available PDCHs
Throughput
B. Average throughput per TBF:
Average Throughput of Uplink GPRS TBF (kbit/s) =

[Average Payload of Single Uplink GPRS TBF (KB)]*{1024}*{8}/[Average Duration of Uplink GPRS TBF (s)]
Average Throughput of Uplink EGPRS TBF (kbit/s) =

[Average Payload of Single Uplink EGPRS TBF (KB)]*{1024}*{8}/[Average Duration of Uplink EGPRS TBF (s)]
Average Throughput of Downlink GPRS TBF (kbit/s) =

[Average Payload of Single Downlink GPRS TBF (KB)]*{1024}*{8}/[Average Duration of Downlink GPRS TBF (s)]
Average Throughput of Downlink EGPRS TBF (kbit/s) =

[Average Payload of Single Downlink EGPRS TBF (KB)]*{1024}*{8}/[Average Duration of Downlink EGPRS TBF (s)]
Low Throughput - Analysis
Analysis process:
1.Low throughput may be due to problems across the packet service transmission path. Thorough checks should be done in Gb, Abis, Um interfaces.
Also in SGSN, PCU, BSC systems.
2.Gb interface:
- Check usage of Gb links. Expand Gb capacity if congestion appears.
Gb usage can be checked through Real Time Monitoring function of BSC LMT: On the Trace & Monitor tab page, choose Monitor > Monitor GPRS
Flux.
Also Gb utilization can be checked through following counters:
- RL9608:BC_TRAN_UP_UTILIZATION_RATE: Uplink Utilization Rate on BC (%)
- RL9610:BC_TRAN_DOWN_UTILIZATION_RATE: Downlink Utilization Rate on BC (%)
Both counters above provide the ratio of actually used bandwidth over configured bandwidth on a BC of Gb.
- Check alarms on GDPUP board (BSC6000) or DPUd board (BSC6900) which are the boards that provide
PCU functionality in BSC (internal PCU).
Analysis process:
3.Abis interface:
- Check for congestion on Abis interface. Congestion will lower the throughput.
- Higher CS and MCS coding schemes will occupy higher number of Abis timeslots. Check relative parameters for CS transition:
- UPTHDCSUPGRADE1: Uplink TBF Threshold from CS1 to CS2
- UPTHDCSDEGRADE1: Uplink TBF Threshold from CS2 to CS1
- DNTHDCSUPGRADE1: Downlink TBF Threshold from CS1 to CS2

- DNTHDCSDEGRADE1: Downlink TBF Threshold from CS2 to CS1
Analysis process:
4.Um interface:
- Check if TCH congestion exists on air interface. High CS usage will leave less dynamic PDCHs free for PS service. Refer to Case 4 of present
document for handling suggestions on TCH blocking.
- Check Radio quality in the cell. Bad quality will negatively affect throughput. Refer to Case 7 of present document for more details on RxQual
measurements.
- Check UL interference in the cell. High interference will negatively affect UL throughput. Refer to Case 8 of present document for more details on UL
interference measurements.
Availability
(([AR3027A]+[AR3027B]+[AR3028A]+[AR3028B])/
TCH Availability No
([AR3017A]+[AR3017B]+[AR3018A]+[AR3018B]))*100
SDCCH Availability No (([AR3020A]+[AR3020B])/([AR3010A]+[AR3010B]))*100

Available TCHs No K3015 K3015:Available TCHs
Available SDCCHs No K3005 K3005:Available SDCCHs
Coverage
Timing Advance
The following counters provide TA distribution per TRX in the cell. The measurements can be checked
versus cell radius to identify possible coverage problems.
- S4400A:TRX_MR_NUM_BY_TA_0 - S4420A:TRX_MR_NUM_BY_TA_20
- S4410A:TRX_MR_NUM_BY_TA_10 - S4430A:TRX_MR_NUM_BY_TA_30_TO_31
- S4419A:TRX_MR_NUM_BY_TA_19 - S4463A:TRX_MR_NUM_BY_TA_GT_63
Rxlevel & Rxquality measurements
BSC receives reports that contain the uplink and downlink receive level rank and the uplink and downlink receive quality rank.
- The receive level ranges from rank 0 to rank 7. Each rank corresponds to a receive level range.
- The receive quality ranges from rank 0 to rank 7. Each rank corresponds to a bit error rate range.
Receive Level Rank Receive Level (dBm) Receive Quality Rank Bit Error Rate
0 -100 0 < 0.2%
1 (-100,-95] 1 0.2%-0.4%
2 (-95,-90] 2 0.4 %-0.8%
3 (-90,-85] 3 0.8%-1.6%
4 (-85,-80] 4 1.6%-3.2%
5 (-80,-75] 5 3.2%-6.4%
6 (-75,-70] 6 6.4%-12.8%
7 > -70 7 > 12.8%
Receive Level Measurement, together with Receive Quality Measurement per TRX, reflects the radio signal coverage and interference of a cell.
For example,
a high ratio of high level and low quality suggests possible interference;
a high ratio of low level and low quality suggests poor coverage.
Rxlevel & Rxquality measurements
TCHF Receive Level Measurement per TRX provides the number of measurement reports from the TCHF that contain receive level rank
and receive quality rank. TCHF receive level and quality measurements for UL and DL are given by following counters:
- S4100A:TRX_FR_UP_LEV_0_RX_QLTY_0 - S4100B:TRX_FR_DOWN_LEV_0_RX_QLTY_0
... ..
Saaaaa:TRX_FR_UP_LEV_x_RX_QLTY_y Saaaaa:TRX_FR_UP_LEV_x_RX_QLTY_y
where: aaaaa=counter ID, x=receive level rank (0~7), y=receive quality rank (0~7)
TCHH Receive Level Measurement per TRX refers to the measurement of the sampled receive level ranks and receive quality ranks in the
MRs on the TCHH. TCHH receive level and quality measurements for UL and DL are given by following counters:
- S4100C:TRX_HR_UP_LEV_0_RX_QLTY_0 - S4100D:TRX_HR_DOWN_LEV_0_RX_QLTY_0

Saaaaa:TRX_HR_UP_LEV_x_RX_QLTY_y Saaaaa:TRX_FR_UP_LEV_x_RX_QLTY_y
where: aaaaa=counter ID, x=receive level rank (0~7), y=receive quality rank (0~7)
Interference Band
Idle UL Interference
The interference band is the uplink interference level of a channel reported by the BTS to the BSC in the RF RESOURCE INDICATION
message when the channel is idle. There are five levels of interference bands. The threshold of each interference band can be configured:
Parameter ID Interference Band Recommended Value (dBm)

INTERFTHRES1 1 -105
INTERFTHRES2 2 -98
INTERFTHRES3 3 -92
INTERFTHRES4 4 -87
INTERFTHRES5 5 -85
Higher rank suggests higher interference level.

Interference Band
The following counters provide the average number of idle channels (TCHF, TCHH, or SDCCH) whose interference level are in each
interference band (1-5) per granularity period.
- AS4200A:TRX_CH_IN_INTFR1_AVR_NUM_SD
- AS4200B:TRX_CH_IN_INTFR2_AVR_NUM_SD
- AS4200C:TRX_CH_IN_INTFR3_AVR_NUM_SD
- AS4200D:TRX_CH_IN_INTFR4_AVR_NUM_SD
- AS4200E:TRX_CH_IN_INTFR5_AVR_NUM_SD
- AS4207A:TRX_CH_IN_INTFR1_AVR_NUM_FR
- AS4207B:TRX_CH_IN_INTFR2_AVR_NUM_FR
- AS4207C:TRX_CH_IN_INTFR3_AVR_NUM_FR
- AS4207D:TRX_CH_IN_INTFR4_AVR_NUM_FR
- AS4207E:TRX_CH_IN_INTFR5_AVR_NUM_FR
- AS4208A:TRX_CH_IN_INTFR1_AVR_NUM_HR
- AS4208B:TRX_CH_IN_INTFR2_AVR_NUM_HR
- AS4208C:TRX_CH_IN_INTFR3_AVR_NUM_HR
- AS4208D:TRX_CH_IN_INTFR4_AVR_NUM_HR
- AS4208E:TRX_CH_IN_INTFR5_AVR_NUM_HR
Rxlevel & Quality distributions can be used to identify interference in a cell.

TA measurements can be used to identify interference in a cell.
Alarm Monitoring
Alarm
No Alarm Name Description Impact to System
The voltage of surge protector 1 or 2 and the alarm voltage are consistent for
1 Arrester Fail sensor, voltage, board, cable damage/incorect
20 seconds
The maintenance link between the main control board and the other boards The board may not work normally. The ongoing services carried on the board are
2 BBU Board Maintenance Link Failure
in the subrack malfunctions disrupted.
In chain topology, the CPRI link of lower-level RF units is disconnected. The
This alarm is reported when the data transmission on the CPRI link (at the services carried on lower-level RF units are disrupted. In ring topology, the
3 BBU CPRI Interface Error
link layer) malfunctions between the BBU and the lower-level RF units reliability of the CPRI link decreases. In this case, the active CPRI link of lower-
level RF units is switched over to the standby CPRI link. In the case of a hot
This alarm is reported when a person enters the equipment room or the door
4 Burglar Alarm The equipment may be damaged or stolen.
of the cabinet is open
Heat dissipation of the BTS does not work properly. In a severe case, the
5 Fan Stalled This alarm is reported when a fan is faulty.
hardware of the BTS may be damaged.
The functions such as printing, interface tracing, call tracing, RRM performance
monitoring, or resource auditing may be temporarily stopped due to the high
6 Flow Control Flow control on system
system load. The paging message or the access message may be discarded in
serious overload situation.
The BSC periodically checks the BCCH TRX and the RSL of the BCCH TRX.
7 GSM Cell out of Service This alarm is generated when the RSL of the BCCH TRX is faulty or the All the speech services and data services are disrupted in the cell
BCCH TRX is unavailable for use.
In multi-mode configuration, this alarm is reported when the main control
The consistency check cannot be performed for inter-system configuration. The
8 Inter-System Communication Failure board in the current mode cannot communicate with the main control board
common alarms shared by different systems are reported repeatedly.
in the other mode.
In multi-mode configuration, this alarm is reported when the parameter The parameter settings of a monitoring device in a mode are incorrect. In this
Inter-System Monitoring Device
9 settings of a monitoring device in a mode are inconsistent with those of the case, the related data configuration may not take effect in this mode, and alarms
Parameter Settings Conflict
same monitoring device in the other mode. may be mistakenly reported.
AC Failure, AC Phase Loss, AC Overvoltage, AC Undervoltage --> Output power
10 Mains Input Out of Range This alarm is reported when the mains input is out of range. decreases and some boards are powered off, the durability of power system is
shortened
Alarm
This event is generated when the size of the log exceeds 80% of the
If the log is not backed up and the size of the log exceeds the maximum size, the
12 Oversized Log maximum size. The maximum size of the text log is 500 MB, and it is saved
earlier information of the log is removed.
in "OMU installation directory/mbsc/bam/common/fam/famlog".
13 Phase Failure
The TRX automatically shuts down the power amplifier (PA), and the ongoing
This alarm is reported when the radio signaling link (RSL) between the BSC
14 Radio Signaling Link Disconnected services carried on the TRX are disrupted. If the TRX is the BCCH TRX, the
and the TRX fails.
ongoing services of the cell holding the TRX are disrupted.
This alarm is reported when the average RX level difference between the The UL receive sensitivity drops, and the coverage area is reduced. If the faulty
15 RF Unit RX Channel Fault main and diversity RX channels of the RF unit exceeds the statistical RX TRX is a BCCH TRX, the coverage area of the cell is reduced, which may lead to
level difference in each measurement period (32 dB). the drop of the handover success rate.
16 RF Unit Startup This event is reported when the RF unit is powered on or reset. The RF unit starts. The services of the RF unit are set up again.
The return loss at the antenna port is excessive. In this case, the RF unit
This alarm is reported when the VSWR at the antenna port of the TX channel
17 RF Unit VSWR Threshold Crossed automatically switches off the TX channel, and the ongoing services carried on
of an RF unit is higher than the preset threshold.
the TX channel are disrupted.
This event is generated when the switchback after BCCH mutual aid occurs
under the following conditions: The BSC detects that the original BCCH TRX
Switchback After BCCH Mutual Aid in The cell is re-initialized, and the BCCH is switched back to the original BCCH
18 resumes normal operation, the BCCH is in the unblocked administrative
a GSM Cell TRX. Thus, the services are temporarily disrupted (for no more than 10 seconds).
state, and the switchback is allowed in the cell. This event alarm will also be
generated when a forced switchback occurs due to data configuration.
19 Sensor Failure This alarm is reported when an analog sensor fails to work properly. The BTS cannot work properly, and heat dissipation of the system is affected.
If the maintenance link of the RET antenna is broken, the antenna tilt cannot be
regulated. In this case, the state of the RET antenna cannot be monitored. If the
This alarm is reported when the maintenance link between the RF unit and
20 RF Unit Maintenance Link Failure maintenance link of the TMA is broken, the TMA gain cannot be configured. In
the ALD (RET antenna, TMA, or SASU) malfunctions.
this case, the state of the TMA cannot be monitored.
This event alarm is generated when a cell that supports the PS service
When the cause of this event is "Delay in a normal cell longer than 240 ms", the
detects that the transmission delay between the BTS and the BSC does not
GSM Cell Transmission Delay channels are allocated normally for EGPRS services but the service performance
21 meet the specified requirements. According to the requirements, delay in a
Abnormal is degraded; for GPRS services, up to one uplink channel and three downlink
normal cell must be shorter than or equal to 240 ms, delay in a satellite cell
channels can be assigned, and the service performance is affected.
must be shorter than or equal to 800 ms.
Cabinet Air Outlet Temperature This alarm is reported when the temperature at the air outlet of the cabinet is The device may be damaged because of a high temperature. In this case, the
22
Unacceptable too high or too low. ongoing services are disrupted.
Alarm
This alarm is generated when the bandwidth available for an IP
logical port (forward bandwidth or backward bandwidth) is equal
to or lower than the congestion left bandwidth threshold (forward
bandwidth or backward bandwidth) of the IP logical port due to
23 IP Logical Port Congestion The subsequent connection requests may be rejected.
the access of new services, the change of the bandwidth (forward
bandwidth or backward bandwidth) available for the IP logical
port, or the modification of the congestion threshold (forward
bandwidth or backward bandwidth) of the IP logical port.
Some functions of the RF unit may fail, such as channel gain
This alarm is reported when the CPU usage of the RF unit is correction. In this case, the quality of services carried on the RF unit
24 RF Unit Overload
beyond the operating threshold. decreases. Long-term CPU overload may result in delayed response
or timeout of maintenance tasks of the RF unit.
The base station fails to synchronize to the clock reference. The
This alarm is reported in the case of clock reference loss,
system clock may be unusable if the base station does not obtain the
External Clock Reference excessive frequency deviation between the clock reference and
25 clock reference for a long time. As a result, the quality of services of
Problem the local oscillator, unstable clock reference frequency, or
the base station decreases, resulting in handover failure and call
excessive jitter.
drop. In certain cases, the base station cannot provide services.
The data link layer protocol between the BSC and the BTS is the
LAPD protocol. To enable the communication between the data
link layers of the BSC and the BTS through the LAPD protocol,
the LAPD link should be established. The link carries operation All the BTS services are disrupted when the LAPD_OML is
26 OML Fault
and maintenance information is called OML or LAPD_OML. This disconnected.
alarm is generated when the BSC detects the LAPD_OML
disconnection between the BSC and the BTS or the BSC detects
that the handshake with the BTS times out.
This alarm is generated when the extended signaling link (ESL)
27 ESL Link Fault The speech services are all disrupted in the related BTS.
between the BSC and the BTS is disconnected.
Alarm
This event is reported when a board is restarted because of user command or

29 Board Startup The ongoing services carried on the board are disrupted.
exception.
This alarm is generated when the Ethernet port of the
30 Ethernet Link Fault FG2a/GOUa/FG2c/GOUc is configured with an IP address or added to a The services carried on the Ethernet link are disrupted.
trunk group but the Ethernet port cannot transmit or receive packets.
31 Board Not In Position
RF Unit Optical Module or Electrical
32
Port Not Ready
In ring topology, the CPRI uplink and downlink of the RF unit cooperate in
In the case of a hot ring, the ongoing services are not affected. In the case of a
33 RF Unit CPRI Interface Switchover active/standby mode. If the CPRI uplink is faulty, the RF unit automatically
cold ring, the ongoing services are disrupted temporarily.
switches to the CPRI downlink. This event is reported in this case.
34 Local User Login Failed This event is generated when the local user fails to log in to the system. The administrator is notified that the local user fails to log in to the system.
When this alarm is generated, the surge protection module in the surge protection
35 AC Surge Protector Fault This alarm is reported when the AC surge protector is faulty. device is damaged. This lowers the surge protection capability of the BTS. The
BTS, if struck by lightening again, may be damaged.
This alarm is reported when the BTS detects that the radio link is faulty. A
faulty radio link may be caused by abnormal channel release, zero traffic on
36 Radio Link Failure the TCH, SDCCH, and PDCH for a long time period, imbalance between The network KPIs deteriorate. The service quality decreases.
uplink and downlink, or abnormal channel activation in a preset alarm
detection period.
This event is generated when the BCCH TRX is faulty and a normal TRX in The cell is re-initialized, and the services are temporarily disrupted (for no more
37 BCCH Mutual Aid in a GSM Cell
the cell is selected as the new BCCH TRX. than 10 seconds).
The DC output overvoltage may cause damage to the boards of the base station.
In this case, the ongoing services carried on the boards are disrupted. The DC
output undervoltage may lead to board power-off at the base station. In this case,
Power Supply DC Output Out of This alarm is reported when the DC output of the power system is out of
38 the ongoing services carried on the boards are disrupted.
Range range.
This alarm is reported when the batteries are exhausted, the battery When the batteries are disconnected due to low voltage, the base station stops
39 Battery Power Unavailable temperature is extremely high, or when the batteries are powered off working and all related services are disrupted. The services are resumed only
manually or remotely. after the AC power supply is available.
THANK YOU

2G - OSS KPI v1.1

Uploaded by

Copyright:

Available Formats

You might also like

2G - OSS KPI v1.1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2G - OSS KPI v1.1

Uploaded by

Copyright:

Available Formats

2G KPI, Performance and Alarm Monitoring

Field measurement KPI can be classified into the following category

Immediate Assignment Success Rate :

K3003 : Successful SDCCH Seizures SDCCH Blocking Rate :

CA303J : Call Setup Indications CSSR :

More than 1 counter can be triggered by same

Basic Immediate Assignment signalling procedure:

CA300J : Channel Requests

CA303J : Call Setup Indications

Fig.1 Successful Immediate Assignment Fig.2 Failed Immediate Assignment

TCH Assignment Success Rate:

TCH Blocking Rate :

CA310 : Assignment Requests

Check following counters to identify the reason for Assignment failure:

2. Failures due to abnormal radio resource allocation:

3. Failures due to abnormal air interface access:

- A3129R: CELL_ASS_FAIL_RECONN_SUCC_DR_RECONN_SUCC: This counter provides the number of HO FAIL or RR STATUS

Counter ID Counter Name Counter Description

Counter ID Counter Name Counter Description

In the immediate assignment procedure, the BSC measures the counter in

Counter ID Counter Name Counter Description

Key Performance Indicator ATP KPI Huawei Counter Counter Difination

A9003:Number of Failed Uplink GPRS TBF Establishments due to No Channel

A9001:Number of Uplink GPRS TBF Establishment Attempts

A9201: Number of Uplink EGPRS TBF Establishment Attempts

A9103:Number of Failed downlink GPRS TBF Establishments due to No Channel

A9101:Number of downlink GPRS TBF Establishment Attempts

Uplink TBF Establishment Success Rate

A9002:Number of Successful Uplink GPRS TBF Establishments

A9001:Number of Uplink GPRS TBF Establishment Attempts

A9003:Number of Failed Uplink GPRS TBF Establishments due to No Channel

A. UL GPRS TBF establishment failures:

B. UL EGPRS TBF establishment failures:

A9101:DL GPRS TBF Establishment Attempts

Downlink TBF Establishment Success Rate

- A9303:DOWN_EGPRS_TBF_ESTB_FAIL_NO_CHAN_RES: number of failed downlink EGPRS TBF establishments due to no

- A9304:DOWN_EGPRS_TBF_ESTB_FAIL_MS_NO_RESP: number of failed downlink EGPRS TBF establishments due to no

- A9333:DOWN_EGPRS_TBF_ESTB_FAIL_SEND_ASSMSG_FAIL: In dedicated mode, the BSS sends the resource assignment

- A9334:DOWN_EGPRS_TBF_ESTB_FAIL_MS_RESP_ASS_FAILURE: In dedicated mode, the BSS sends the resource assignment

- A9315:DOWN_EGPRS_TBF_ESTB_FAIL_OTHER_CAUSE: This measurement provides the number of failed downlink EGPRS

1. If TBF establishment failure is due to congestion in TCH,

2. If TBF establishment failure is due to poor RF quality, then:

Key Performance Indicator ATP KPI Huawei Counter Counter Difination

TCH Drop Rate

Counter ID Counter Name Counter Description

Call Drops on Traffic Channel (CM33)=

Counter ID Counter Name Counter Description

Counter ID Counter Name Counter Description

This counter is calculated at A6, as shown previous figure

Counter ID Counter Name Counter Description

This counter is calculated at A4, as shown previous figure

Counter ID Counter Name Counter Description

This counter is calculated at A4, as shown previous figure

Counter ID Counter Name Counter Description

This counter is measured in the following situations:

This counter is calculated at A4, as shown previous figure

Counter ID Counter Name Counter Description

((L910223+L910334+L910440+L910554)850 L9103:Total Number of Downlink RLC Data Blocks Using CS2