[RF] Call Drops on Traffic Channel Huawei

June 6, 2011 by TheBeeliever Leave a comment

Description :
 This measurement provides the number of call drops due to various reasons after the MS seizes a
traffic channel.
 The MS seizures a TCH in any of the following conditions:
 The MS sends an ASS CMP message to the BSC;
 The MS seizes a TCH and sends an HO CMP message to the BSC.
Measurement Point :
When a TCH is seized to carry traffic during a call, this counter is measured in the following
situations:
1. The BSC receives an ERROR INDICATION message from the BTS because of the abnormal
connection at the radio link layer. For details, refer to GSM Rec. 08.58.
2. The BSC receives a CONNECTION FAILURE INDICATION message from the BTS because
of the radio link fault or hardware fault. For details, refer to GSM Rec. 08.58.
3. When receiving a DISC frame on a link layer connection in multi-frame mode, the BTS sends a
REL IND message to the BSC. For details, refer to GSM Rec. 08.58.
4. The timer set to wait for an HO CMP message expires during internal intra-cell handover.
5. The timer set to wait for an HO CMP message expires during outgoing internal inter-cell
handover.
6. The timer set to wait for an HO CMP message expires during outgoing external inter-cell
handover.
7. The timer set to wait for an HO CMP message expires during incoming external inter-cell
handover.
8. The BSC does not receive any measurement report within a certain period (by default, five
minutes) and sends a CLEAR COMMAND message to the MSC to release the call.
9. The BSC detects a broken RSL and releases all the calls on the RSL.
10. A call drop occurs due to any of the following situations: TRX mutual aid; dynamic modification
of cell attributes, TRX frequencies, or TRX FH data; dynamic deletion of cells or TRXs; blocking of
cells, TRXs, or channels.
11. 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.
12. A call drop occurs due to call assignment failure during the handover.
13. The MSC cannot send a short message because the data configuration prohibits the downlink
short messages or because of flow control and the call is released.
14. A call drop occurs due to software error.
15. After seizing a channel, the MS fails to start a local switching due to terrestrial resource request
failure, failures on the BTS side, or timer expiration.
16. During the handover of the call in the local switching state, the BSC releases the call after
receiving a HANDOVER DETECT message from the BTS and then a HANDOVER FAILURE
message from the MS.
17. After a call is in the BSC or BTS local switching state, if the local switching cannot be proceeded
for handover or other reasons, the BSC restores the call to the common call state. If the restoration
fails due to terrestrial resource request failure or other reasons, the BSC releases the call.
CM33 Call Drop Cause Counter :
CM330 : Call Drops on Radio Interface in Stable State (Traffic Channel)
1. Call Drops on TCH in Stable State (Error Indication)
 Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (T200 Expired)
 Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (Unsolicited DM
Response)
 Call Drops due to ERR IND Received on TCHF (Traffic Channel) in Stable State (Sequence Error)
 Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (T200 Expired)
 Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (Unsolicited DM
Response)
 Call Drops due to ERR IND Received on TCHH (Traffic Channel) in Stable State (Sequence Error)
1. Call Drops on Traffic Channel in Stable State (Connection Failure)
 Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Radio Link
Failure)
 Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (HO Access
Failure)
 Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (OM
Intervention)
 Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Radio
Resource Unavailable)
 Call Drops due to CONN FAIL Received on TCHF (Traffic Channel) in Stable State (Other Causes)
 Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Radio Link
Failure)
 Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (HO Access
Failure)
 Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (OM
Intervention)
 Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Radio
Resource Unavailable)
 Call Drops due to CONN FAIL Received on TCHH (Traffic Channel) in Stable State (Other Causes)
1. Call Drops on Traffic Channel in Stable State (Release Indication)
 Call Drops due to REL IND Received on TCHF (Traffic Channel)
 Call Drops due to REL IND Received on TCHH (Traffic Channel)
CM331 : Call Drops on Radio Interface in Handover State (Traffic Channel)
 Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel)
 Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)
 Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel)
 Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel)
 Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHF) (Traffic Channel)
 Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHH) (Traffic Channel)
CM332 : Call Drops due to No MRs from MS for a Long Time (Traffic Channel)
 Call Drops due to No MRs from MS for a Long Time (TCHF) (TCH)
 Call Drops due to No MRs from MS for a Long Time (TCHH) (TCH)
CM333 : Call Drops due to Abis Terrestrial Link Failure (Traffic Channel)
 Call Drops due to Abis Terrestrial Link Failure (TCHF) (TCH)
 Call Drops due to Abis Terrestrial Link Failure (TCHH) (Signaling Channel)
 Call Drops due to Abis Terrestrial Link Failure (TCHH) (TCH)
CM334 : Call Drops due to Equipment Failure (Traffic Channel)
 Call Drops due to Equipment Failure (TCHF) (TCH)
 Call Drops due to Equipment Failure (TCHH) (TCH)
CM335 : Call Drops due to Forced Handover (Traffic Channel)
 Call Drops due to Forced Handover (TCHF) (TCH)
 Call Drops due to Forced Handover (TCHH) (TCH)
CM397 : Call Drops Due to Loopback Start Failure
 Call Drops due to BSC Loopback Start Failure (Terrestrial Resource Request Failure)
 Call Drops due to BSC Loopback Start Failure (Others)
 Call Drops due to BTS Loopback Start Failure (Terrestrial Resource Request Failure)
 Call Drops due to BTS Loopback Start Failure (Failures on the BTS Side)
 Call Drops due to BTS Loopback Start Failure (Others)
 Call Drops due to Loopback Start Failure (Timer Expired)
CM385 : Call Drops Due to Failures to Return to Normal Call from Loopback
 Call Drops due to Failures to Return to Normal Call from BSC Loopback (Terrestrial Resource
Request Failure)
 Call Drops due to Failures to Return to Normal Call from BTS Loopback (Terrestrial Resource
Request Failure)
 Call Drops due to Failures to Return to Normal Call from BSC Loopback (Others)
 Call Drops due to Failures to Return to Normal Call from BTS Loopback (Others)