VIETTEL TANZANIA LIMITED Code:

Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 1/21

TABLE TRACKING MODIFICATION

No. Page Amendments Effective date
1 19 Write new

Written by Examined by Approved by

Signature

1
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 2/21

I. Purpose and requirement

- The Document leads Radio engineer to trouble bad KPI in 2G and 3G system.
- Increase performance in Huawei system.
II. Scope of application
- Huawei vendor in Halotel network.
III. Reference documents
- The documents of Huawei vendor for analyze KPI.
- The Guideline Upgrade/Downgrade Radio Resources and ADD/REMOVE Co-site
2G/3G.
IV. The terminology
- SCR: SDCCH Congestion Rate.
- TCR: TCH Congestion Rate.
- SDR: SDCCH Drop Rate.
- CSSR: Call Setup Success Rate.
- CDR: Call Drop Rate.
- HOSR: Handover Outgoing Success Rate.
- PSR: Paging Success Rate.
- CS RAB CR: CS Radio Access Bearer Congestion Rate.
- PS RAB CR: PS Radio Access Bearer Congestion Rate.
- CS CSSR: CS Call Setup Success Rate.
- PS CSSR: PS Call Setup Success Rate.
- SHOSR: Soft Handover Success Rate.
- CS CDR: CS Call Drop Rate.
- PS CDR: PS Call Drop Rate.
- TU: Traffic Utilisation.
V. Content
Part 1: KPI 2G
1. SCR
a. Formula
SCR (%) = No SDCCH Congestion (D-C)/No SDCCH Attempt (D-C)*100
b. Counter on U2000
No SDCCH Congestion (D-C) define by counter K3001: Failed SDCCH
Seizures due to Busy SDCCH.
No SDCCH Attempt (D-C) define by counter K3000: SDCCH Seizure Requests.
c. Processing information on system

2
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 3/21

The cell SDCCH congestion information can get from NPMS software by path:
http://10.225.199.144:8080/PNMS/peak-Detail

The cell has congestion when you see the value on the counter SDCCH
congestion. If the Cell has SDCCH congestion 4/7 days continuous than you
must have to solution to clear this congestion.
Case 1: The TU non half rate lower than 80%
In this case, The load of cell is a little but the SD congestion exist. Using the
Command LST GTRXCHAN to check how many SDCCH channel config on
this cell and convert TCH channel to SDCCH channel to solve this problem.
Case 2: The TU non half rate greater than 80%
In this case, The load of cell is heavy. Some reason make cell heavy are more
subscriber or near border LAC. You can upgrade more TRXs and config more
SDCCHs channel or install co-site to solve this congestion.
2. TCR
a. Formula
TCR (%) = No Subscriber Perceived TCH Congestion(D-C)/No TCH Ass Att(D-
C)*100
b. Counter on U2000
K3021: Failed TCH Seizures due to Busy TCH (Signaling Channel)
K3011A: Failed TCH Seizures due to Busy TCH (Traffic Channel)
K3020: TCH Seizure Requests (Signaling Channel)
K3010A: TCH Seizure Requests (Traffic Channel)
No Subscriber Perceived TCH Congestion(D-C) = K3021+ K3011A
No TCH Ass Att(D-C) = K3020+ K3010A

3
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 4/21

c. Processing information on system

The cell TCH congestion information can get from NPMS software by path:
http://10.225.199.144:8080/PNMS/peak-Detail

The cell has congestion when you see the value on the counter TCH congestion.
If the Cell has TCH congestion 4/7 days continuous than you must have to
solution to clear this congestion.
In this case, If the TCH congestion of cell is a little, you can config HR 100%
and convert fix PDTCH channel to TCH channel. When the load of cell is heavy
(TU non half rate greater than 80%). The reason make cell heavy is more
subscriber. You can upgrade more TRXs and config or install co-site to solve this
congestion.
3. CDR
a. Formula
CDR (%) = No TCH Drop(D-C)/(No TCH Ass Succ(D-C)+No Incoming HO
Succ(D-C)-No Outgoing HO Succ(D-C))*100
b. Counter on U2000
CM33: Call Drop on Traffic Channel
K3013A: Successful TCH Seizures (Traffic Channel)
CH323: Successful Incoming Internal Inter-Cell Handovers
CH343: Successful Incoming External Inter-Cell Handovers
CH313: Successful Outgoing Internal Inter-Cell Handovers
CH333: Successful Outgoing External Inter-Cell Handovers

No TCH Drop(D-C) define by Counter CM33

No TCH Ass Succ(D-C) define by Counter K3013A

4
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 5/21

No Incoming HO Succ(D-C) define by Counter CH323 + Counter CH343

No Outgoing HO Succ(D-C) define by Counter CH313 + Counter CH333
c. Processing information on system
The cell TCH Drop information can get from U2000 software by templet “DR
Hourly_whole day”.

Explain the reason make call drop:

- Call Drops on Radio Interface in Stable State (Traffic Channel) : Call drop
due to radio evironment. You need to check another sub counter for more
understand.
- Call Drops on Radio Interface in Handover State (Traffic Channel) : The Call
Drop when subscriber in handover state. Check relation cell to cell and
increate if mising, check the quality of cell, change new frequency when cell
has interference, optimize the corverage if the cell has overshooting.
- Call Drops due to No MRs from MS for a long time (Traffic Channel): Call
drop due to BTS don’t receive MRR message for long time. Check Quality
and TA of cell. If the quality has interfrence change a new frequency, if the
coverage is big you need check tilt, azimuth and optimize this cell.
- Call Drops due to Abis Teresstrial Link Failure (Traffic Channel): When the
transmission has problem. You can check the quality by using command Ping
from computer to BTS.
- Call Drops due to Equipment Failure (Traffic Channel) : The Call drop due to
hardware of BTS has Problem. You need replace a new and check it again.
Most of them is RRU has error.

5
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 6/21

- Call Drops due to Forced Handover (Traffic Channel): The system forces
subscriber to handover to another cell. You need check the quality of cell by
Quality map, the distance of subscriberby TA map.
- Call Drops on TCH(TA): When you see more the call Drop from this counter
it mean the position of subscriber is very far (more than 35km). So you must
optimize the corverage of the cell. You can check corverage of cell by the TA
map.
4. SDR
a. Formula
SDR (%) = No SDCCH Drop(D-C)/No SDCCH Ass Succ(D-C)*100
b. Counter on U2000
CM30: Call Drop on SDCCH
K3003: Successful SDCCH Seizures

No SDCCH Drop(D-C) define by counter CM30

No SDCCH Ass Succ(D-C) define by counter K3003
c. Processing information on system
The cell SDCCH Drop information can get from U2000 software by templet “DR
Hourly_whole day”.

Explain the reason make SDCCH drop:

- Call Drops on Radio Interface in Handover State (Signaling Channel) : The
SDCCH Drop when subscriber in handover state. Check relation cell to cell
and increate if mising, check the quality of cell, change new frequency when
cell has interference, optimize the corverage if the cell has overshooting.

6
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 7/21

- Call Drops on Radio Interface in Stable State (Signaling Channel) : SDCCH

drop due to radio evironment. You need to check another sub counter for
more understand.
- Call Drops due to Abis Teresstrial Link Failure (Signaling Channel) : When
the transmission has problem. You can check the quality by using command
Ping from computer to BTS.
- Call Drops due to No MRs from MS for a long time (Signaling Channel) :
SDCCH drop due to BTS don’t receive MRR message for long time. Check
Quality anh TA of cell. If the quality has interfrence change a new frequency,
if the coverage is big you need check tilt, azimuth and optimize this cell.
- Call Drops due to Equipment Failure (Signaling Channel) : The SDCCH drop
due to hardware of BTS has Problem. You need repalace a new and check it
agian. Most of them is RRU has error.
- Call Drops due to Forced Handover (Signaling Channel) : The system forces
subscriber to handover to another cell. You need check the quality of cell by
Quality map, the distance of subscriberby TA map.
- Call Drops on SDCCH(TA) : When you see more the SDCCH drop from this
counter it mean the position of subscriber is very far (more than 35km). So
you must optimize the corverage of the cell. You can check corverage of cell
by the TA map.
- Call drop on SDCCH(Received Level) : This counter will sum all SDCCH
drop due to Received Level. You need check receive level and TA on the map
and then have solution to increate signal of MS.
- Call drop on SDCCH(Quality) : This counter will sum all SDCCH drop due
to quality. You need check quality on the map and change frequency when
the cell has interference.
- Call drop on SDCCH(Other) : The SDCCH drop without define on sub
counter. In this case, Huawei define reason is Other.
5. CSSR
a. Formula
CSSR (%) = (1 – (No SDCCH Drop (Call type)/No SDCCH Succ (Call
type))*(No TCH Ass Succ/No TCH Ass Att)*100
b. Counter on U2000
CM30C: Call Drops on SDCCH (Call Type)
K3003A: Successful SDCCH Seizures (Call Type)
K3023: Successful TCH Seizures (Signaling Channel)

7
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 8/21

K3013A: Successful TCH Seizures (Traffic Channel)

K3020: TCH Seizures Requests (Signaling Channel)
K3010A: TCH Seizures Requests (Traffic Channel)

No SDCCH Drop (Call type) define by counter CM30C

No SDCCH Succ (Call type) define by counter K3003A
No TCH Ass Succ define by counter K3023 + Counter K3013A
No TCH Ass Att define by counter K3020 + K3010A
c. Processing information on system
The CSSR information can get from U2000 software by templet “DR
Hourly_whole day”.

- Due to CSSR relative with SDR and TCH Assigment Success so we need to
define bad KPI CSSR from SDR or TCH Assigment Success. For
troubleshooting SDR KPI you can refer to last explain. We have some
reasons make TCH Assigment Success, TCH congestion is one of the reason,
for troubleshooting TCR KPI refer to last explain. TCH Assigment Success
reduce due to radio environment, You need to check interference, TA, rxlev
for cell to solve this problem.

8
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 9/21

6. HOSR
a. Formula
HOSR (%) = No Outgoing HO Succ(D-C)/No Outgoing HO Att(D-C)*100
b. Counter on U2000
CH313: Successful Outgoing Internal Inter-Cell Handover
CH333: Successful Outgoing External Inter-Cell Handover
CH311: Outgoing Internal Inter-Cell Handover Commands
CH331: Outgoing External Inter-Cell Handover Commands

No Outgoing HO Succ(D-C) define by counter CH313 + counter CH333

No Outgoing HO Att(D-C) define by counter CH311 + counter CH331
c. Recommand solution
We have some reasons make bad HOSR as below:
- Missing Neighbour : Use Planchecker to check relation.
- Due to interference with other cells : Use MCOM software to check
frequency.
- The Neighbour cell has hardware problem : In this case you need to check
alarm on system and clear this alarm.
- The Neighbour cell has congestion : Upgarade resoure for cell congestion.
7. PSR
a. Formula
PSR (%) = No paging Responses/First Pagings to A Interface*100
b. Counter on MSC
No Paging Succ define by Paging Responses from A Interface + Repeated
Paging Responses from A Interface
First Pagings to A Interface is total paging message send from MSC to BSC
c. Recommand solution
We have some reasons make bad PSR as below:
- The big corverage of cell : Use TA record to check service distance, optimize
the corverage.
- Due to interference with other cells : Use MCOM software to check
frequency.
- The SDCCH congestion : Follow the recommand solution SCR KPI.

9
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 10/21

Part 2: KPI 3G
1. CS RAB CR
a. Formula
CS RAB CR (%) = No CS RAB Congestion/No CS RAB Attempt*100
b. Processing information on system
The CS congestion information can get from U2000 software by templet
“Congestion”

Explain counter:
- VS.RAB.FailEstCS.Code.Cong: The congestion due to code congestion,
when the Cell supplies service for many subscribers so the code tree not
enough resource to assign for subscriber. You can change the corverage of
cell congestion or neighbor cell to share together. If the cell congestion has
only F1, you can upgrade new F2 for this cell to solve the congestion.
- VS.RAB.FailEstCS.DL.Power.Cong: The congestion due to downlink power,
the solution in this case is same solution for code congestion.
- VS.RAB.FailEstCS.UL.Power.Cong: Congestion due to uplink power, the
solution in this case is same solution for code congestion.

10
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 11/21

- VS.RAB.FailEstCS.DLCE.Cong: Congestion due to DL CE (Channel

Element) not enough resource. The CE has supplied by WBBP, when you see
this congestion, you must insert more WBBPs.
- VS.RAB.FailEstCS.ULCE.Cong: Congestion due to UL CE (Channel
Element) not enough resource. The CE has supplied by WBBP, when you see
this congestion, you must insert more WBBPs.
- VS.RAB.FailEstab.CS.DLIUBBand.Cong: Congestion due to bandwidth of
transmisstion is limited. In this case, You must expand the transmisstion
capacity.
- VS.RAB.FailEstab.CS.ULIUBBand.Cong: Congestion due to bandwidth of
transmisstion is limited. In this case, You must expand the transmisstion
capacity.
2. CS RAB CR
a. Formula
PS RAB CR (%) = No PS RAB Congestion/No PS RAB Attempt*100
b. Processing information on system
The PS congestion information can get from U2000 software by templet
“Congestion”

Explain counter:
- VS.RAB.FailEstPS.Code.Cong: The congestion due to code congestion,
when the Cell supplies service for many subscribers so the code tree not
enough resource to assign for subscriber. You can change the corverage of

11
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 12/21

cell congestion or neighbor cell to share together. If the cell congestion has
only F1, you can upgrade new F2 for this cell to solve the congestion.
- VS.RAB.FailEstPS.DL.Power.Cong: The congestion due to downlink power,
the solution in this case is same solution for code congestion.
- VS.RAB.FailEstPS.UL.Power.Cong: Congestion due to uplink power, the
solution in this case is same solution for code congestion.
- VS.RAB.FailEstPS.DLCE.Cong: Congestion due to DL CE (Channel
Element) not enough resource. The CE has supplied by WBBP, when you see
this congestion, you must insert more WBBPs.
- VS.RAB.FailEstPS.ULCE.Cong: Congestion due to UL CE (Channel
Element) not enough resource. The CE has supplied by WBBP, when you see
this congestion, you must insert more WBBPs.
- VS.RAB.FailEstab.PS.DLIUBBand.Cong: Congestion due to bandwidth of
transmisstion is limited. In this case, You must expand the transmisstion
capacity.
- VS.RAB.FailEstab.PS.ULIUBBand.Cong: Congestion due to bandwidth of
transmisstion is limited. In this case, You must expand the transmisstion
capacity.
- VS.RAB.FailEstab.PS.HSDPAUser.Cong: The congestion due to the
subscriber request HSDPA service more than the subscriber config on system.
You can check how many subscriber config on system by LST UCELLCAC.
In this case, you must expand the value config on system to solve this
problem.
- VS.RAB.FailEstab.PS.HSUPAUser.Cong: The congestion due to the
subscriber request HSDPA service more than the subscriber config on system.
You can check how many subscriber config on system by LST UCELLCAC.
In this case, you must expand the value config on system to solve this
problem.
3. CS CSSR
a. Formula
CS CSSR (%) = (CS RRC SR*CS RAB SR)/100
With:
CS RRC SR (%) = CS RRC Succ/CS RRC Att*100
CS RAB SR (%) = CS RAB Succ/CS RAB Att*100
b. Processing information on system

12
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 13/21

You can get RRC Failed and CS RAB Failed information from U2000 as
below:
RRC is failed: You can get information from “RRC analyse” on U2000

Explain counter:
- VS.RRC.Rej.Sum: This counter calculate all RRC failed of cells.
- VS.RRC.Rej.RL.Fail: This counter calculate all RRC failed of cells due to
Radio link. When you see this counter, you have to check quality radio
environment.
- VS.RRC.Rej.TNL.Fail: This counter calculate all RRC failed of cells due to
quality of the transmission.
- VS.RRC.FailConnEstab.Cong: This counter calculate all RRC failed of cells
due to congestion. Depend on type of congestion you will have situation
solution.
- VS.RRC.Rej.Code.Cong: The RRC is rejected due to code resource. You can
change the corverage of cell congestion or neighbor cell to share together. If
the cell congestion has only F1, you can upgrade new F2 for this cell to solve
the congestion.
- VS.RRC.Rej.ULIUBBand.Cong: The RRC is rejected due to Iub congestion.
You must expand the transmisstion capacity.
- VS.RRC.Rej.DLIUBBand.Cong: The RRC is rejected due to Iub congestion.
You must expand the transmisstion capacity.

13
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 14/21

- VS.RRC.Rej.ULCE.Cong: The RRC is rejected due to CE congestion. The

CE has supplied by WBBP, when you see this congestion, you must insert
more WBBPs.
- VS.RRC.Rej.DLCE.Cong: The RRC is rejected due to CE congestion. The
CE has supplied by WBBP, when you see this congestion, you must insert
more WBBPs.
- VS.RRC.Rej.ULPower.Cong: The congestion due to uplink power, the
solution in this case is same solution for code congestion.
- VS.RRC.Rej.DLPower.Cong: The congestion due to downlink power, the
solution in this case is same solution for code congestion.
- VS.RRC.FailConnEstab.NoReply: The RRC is failed due to UE not reply to
Node B. When you see this counter, you have to check quality radio
environment.

CS RAB Failed: You can get information from “CS RAB analyse” on U2000

Explain counter:
- VS.RAB.FailEstabCS.UuFail: The CS RAB is failed due to Uu interface
(Radio link). you have to check quality radio environment.
- VS.RAB.FailEstabCS.SRBReset: The CS RAB is failed due to SRB
(Signalling Radio Bearer) reset. When the radio environment has problem, the
SRB will reset to reconnect signalling.
- VS.RAB.FailEstabCS.Cong: This counter calculate all RAB failed of cells
due to congestion. Depend on type of congestion you will have situation
solution.

14
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 15/21

- VS.RAB.FailEstabCS.Code.Cong: The CS RAB is failed due to code

resource. You can change the corverage of cell congestion or neighbor cell to
share together. If the cell congestion has only F1, you can upgrade new F2 for
this cell to solve the congestion.
- VS.RAB.FailEstabCS.DLCE.Cong: The CS RAB is failed due to CE
congestion. The CE has supplied by WBBP, when you see this congestion,
you must insert more WBBPs.
- VS.RAB.FailEstabCS.ULCE.Cong: The CS RAB is failed due to CE
congestion. The CE has supplied by WBBP, when you see this congestion,
you must insert more WBBPs.
- VS.RAB.FailEstabCS.DLIUBBand.Cong: The CS RAB is failed due to Iub
congestion. You must expand the transmisstion capacity.
- VS.RAB.FailEstabCS.ULIUBBand.Cong: The CS RAB is failed due to Iub
congestion. You must expand the transmisstion capacity.
- VS.RAB.FailEstabCS.DLPower.Cong: The congestion due to downlink
power, the solution in this case is same solution for code congestion.
- VS.RAB.FailEstabCS.ULPower.Cong: The congestion due to uplink power,
the solution in this case is same solution for code congestion.
- VS.RAB.FailEstabCS.RNL: This counter calculate all CS RAB failed of cells
due to Radio link. When you see this counter, you have to check quality radio
environment.
- VS.RAB.FailEstabCS.TNL: The CS RAB is failed due to Iub error or
attenuation. In this case, you can ping from RNC to NodeB checking delay
time.
- VS.RAB.FailEstabCS.Unsp: This counter calculate all CS RAB failed but not
supported by system.
4. PS CSSR
a. Formula
PS CSSR (%) = (PS RRC SR*PS RAB SR)/100
With:
PS RRC SR (%) = PS RRC Succ/PS RRC Att*100
PS RAB SR (%) = PS RAB Succ/PS RAB Att*100
b. Processing information on system
With RRC is failed, you can analyse same way CS CSSR KPI.
PS RAB is failed: You can get information from “PS RAB analyse” on U2000

15
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 16/21

Explain counter:
- VS.RAB.FailEstabPS.UuFail: The PS RAB is failed due to Uu interface
(Radio link). you have to check quality radio environment.
- VS.RAB.FailEstabPS.SRBReset: The PS RAB is failed due to SRB
(Signalling Radio Bearer) reset. When the radio environment has problem, the
SRB will reset to reconnect signalling.
- VS.RAB.FailEstabPS.CellUpd: This counter calculate all PS RAB failed but
not supported by system.
- VS.RAB.FailEstabPS.Cong: This counter calculate all RAB failed of cells
due to congestion. Depend on type of congestion you will have situation
solution.
- VS.RAB.FailEstabPS.Code.Cong: The PS RAB is failed due to code
resource. You can change the corverage of cell congestion or neighbor cell to
share together. If the cell congestion has only F1, you can upgrade new F2 for
this cell to solve the congestion.
- VS.RAB.FailEstabPS.DLCE.Cong: The PS RAB is failed due to CE
congestion. The CE has supplied by WBBP, when you see this congestion,
you must insert more WBBPs.
- VS.RAB.FailEstabPS.ULCE.Cong: The PS RAB is failed due to CE
congestion. The CE has supplied by WBBP, when you see this congestion,
you must insert more WBBPs.

16
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 17/21

- VS.RAB.FailEstabPS.DLIUBBand.Cong: The PS RAB is failed due to Iub

congestion. You must expand the transmisstion capacity.
- VS.RAB.FailEstabPS.ULIUBBand.Cong: The PS RAB is failed due to Iub
congestion. You must expand the transmisstion capacity.
- VS.RAB.FailEstabPS.DLPower.Cong: The congestion due to downlink
power, the solution in this case is same solution for code congestion.
- VS.RAB.FailEstabPS.ULPower.Cong: The congestion due to uplink power,
the solution in this case is same solution for code congestion.
- VS.RAB.FailEstabPS.RNL: This counter calculate all PS RAB failed of cells
due to Radio link. When you see this counter, you have to check quality radio
environment.
- VS.RAB.FailEstabPS.TNL: The PS RAB is failed due to Iub error or
attenuation. In this case, you can ping from RNC to NodeB checking delay
time.
- VS.RAB.FailEstabPS.HSUPAUser.Cong: The congestion due to the
subscriber request HSUPA service more than the subscriber config on system.
You can check how many subscriber config on system by LST UCELLCAC.
In this case, you must expand the value config on system to solve this
problem.
- VS.RAB.FailEstabPS.HSDPAUser.Cong: The congestion due to the
subscriber request HSDPA service more than the subscriber config on system.
You can check how many subscriber config on system by LST UCELLCAC.
In this case, you must expand the value config on system to solve this
problem.
5. SHOSR
a. Formula
SHOSR (%) = No SHO Success/No SHO Attempt*100
No SHO Attempt = VS.SHO.AttRLAdd + VS.SHO.AttRLDel
No SHO Success = VS.SHO.SuccRLA + VS.SHO.SuccRLDel
b. Processing information on system
You can get information from “SHO analyse” on U2000

17
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 18/21

Explain counter:
- VS.SHO.AttRLAdd: This counter count how many times UE add new radio
link for soft handover.
- VS.SHO.AttRLDel: This counter count how many times UE delete radio link
for soft handover.
- No SHO Attempt: This counter is sum of VS.SHO.AttRLAdd and
VS.SHO.AttRLDel.
- VS.SHO.SuccRLA: This counter count how many times UE add success new
radio link for soft handover.
- VS.SHO.SuccRLDel: This counter count how many times UE delete success
radio link for soft handover.
- No SHO Success: This counter is sum of VS.SHO.SuccRLA and
VS.SHO.SuccRLDel
When the cell has bad SHOSR KPI, You need to check relation cell to cell and
add more if missing neighbor.
6. CS CDR
a. Formula

18
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 19/21

CS CDR (%) = No CS Call Drop/No CS Call Attempt*100

b. Processing information on system
You can get information from “CS CDR analyse” on U2000

Explain counter:
- VS.RAB.AbnormRel.CS: This counter calculate all CS RAB abnormal
release of cells.
- VS.RAB.AbnormRel.CS.RF: Number of CS RABs abnormally released due
to RF for cell(The RF failure includes radio connection with UE lost and
failure in the radio interface procedure). You must check the quality of cell,
relation cell to cell, corverage of cell, RTWP.
- VS.RAB.AbnormRel.CS.RF.SRBReset: Number of CS RABs abnormally
released due to signaling RLC reset(Fault over Iu:Radio connection with UE
lost). You have to check radio environment to solve this problem.
- VS.RAB.AbnormRel.CS.RF.UuNoReply: Number of CS RABs abnormally
released due to UU interface Fail(Failure in the Radio Interface Procedure).
You must check the quality of cell, relation cell to cell, corverage of cell,
RTWP.
- VS.RAB.AbnormRel.CS.RF.ULSync: Number of CS RABs abnormally
released due to Uplink Synchronization Fail(radio connection with UE lost).
In this case, You must check the quality of cell, relation cell to cell, corverage
of cell, RTWP.
- VS.RAB.AbnormRel.CS.OM: Number of CS RAB abnormal released due to
OM Intervention for Cell.

19
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 20/21

- VS.RAB.AbnormRel.CS.OLC: Number of CS RAB release attempts due to

congestion for cell. Depend on type of congestion, you have situation solution
to solve this problem.
7. PS CDR
a. Formula
PS CDR (%) = No PS Call Drop/No PS Call Attempt*100
b. Processing information on system
You can get information from “PS CDR analyse” on U2000

Explain counter:
- VS.RAB.AbnormRel.PS: This counter calculate all PS RAB abnormal release
of cells.
- VS.RAB.AbnormRel.PS.RF: Number of PS RABs abnormally released due
to RF for cell(The RF failure includes radio connection with UE lost and
failure in the radio interface procedure). You must check the quality of cell,
relation cell to cell, corverage of cell, RTWP. Some time PS RAB abnormal
release due to UE error.
- VS.RAB.AbnormRel.PS.RF.SRBReset: Number of PS RABs abnormally
released due to signaling RLC reset(Fault over Iu:Radio connection with UE
lost). You have to check radio environment to solve this problem.

20
 VIETTEL TANZANIA LIMITED Code:
Effective date:
GUIDELINE Issued: 01
TROUBLESHOOTING HUAWEI
Expiry date:
KPI 2G/3G
Page: 21/21

- VS.RAB.AbnormRel.PS.RF.TRBReset: Number of PS RABs abnormally

released due to traffic RLC reset(Fault over Iu:Radio Connection With UE
Lost). You must check the quality of cell, relation cell to cell, corverage of
cell, RTWP.
- VS.RAB.AbnormRel.PS.RF.UuNoReply: Number of PS RABs abnormally
released due to UU interface Fail(Failure in the Radio Interface Procedure).
You must check the quality of cell, relation cell to cell, corverage of cell,
RTWP.
- VS.RAB.AbnormRel.PS.RF.ULSync: Number of CS RABs abnormally
released due to Uplink Synchronization Fail(radio connection with UE lost).
In this case, You must check the quality of cell, relation cell to cell, corverage
of cell, RTWP.
- VS.RAB.AbnormRel.PS.OM: Number of PS RAB abnormal released due to
OM Intervention for Cell.
- VS.RAB.AbnormRel.PS.OLC: Number of PS RAB release attempts due to
congestion for cell. Depend on type of congestion, you have situation solution
to solve this problem.
8. PSR
a. Formula
PSR (%) = No paging Responses/First Pagings to Iu Interface*100
No Paging Succ define by Paging Responses from Iu Interface + Repeated
Paging Responses from Iu Interface
First Pagings to Iu Interface is total paging message send from MSC to RNC
b. Recommand solution
We have some reasons make bad PSR as below:
- The big corverage of cell : Use EcNo follow distance to check service
distance, optimize the corverage.
- Due to interference : Check RTWP of cell to confirm the up link quality.

21