WCDMA RAN15 Call Drop KPI and Relative Counters P-0

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-1

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-2

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters

 The scenario for “User inactivity”:

 If a user with PS service has no data transmission after a certain timer expires (this
timer is set by RNC), RNC can send signaling IU RELEASE REQUEST to CN to release
the service. This is not considered as call drop.
 The scenario for “UE generated signaling connection release”
 Some type of UE can release signaling connection automatically be sending
signaling SIGNALLING CONNECTION RELEASE INDICATION to RNC, then RNC will
send signaling IU RELEASE REQUEST to CN to release the service. This is not
considered as call drop neither.

Confidential Information of Huawei. No Spreading Without Permission

P-3
WCDMA RAN15 Call Drop KPI and Relative Counters

Confidential Information of Huawei. No Spreading Without Permission

P-4
WCDMA RAN15 Call Drop KPI and Relative Counters

Confidential Information of Huawei. No Spreading Without Permission

P-5
 WCDMA RAN15 Call Drop KPI and Relative Counters P-6

 CDR: call drop ratio

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-7

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-8

 This KPI involves CS call drops due to authentication failure during PS security mode in the
cell. You can subtract VS.RAB.AbnormRel.CS.Security from the numerator of the
formula to decrease the value of this KPI.
 VS.RAB.AbnormRel.CS.Security : Number of CS RABs Abnormally Released Due to
Security Mode Procedure Failure for Cell. It is triggered at point A as shown in the figure,
after a RAB is successfully set up, the RNC sends the CN an IU RELEASE REQUEST message
due to a Security Mode procedure failure. The CN responds with an IU RELEASE
COMMAND message. If the cause value carried in the IU RELEASE COMMAND message is
a value other than "User Inactivity", "Normal Release", "Successful Relocation", and
"Network Optimization" (for details about the cause values of the IU RELEASE COMMAND
message, see 3GPP TS 25.413), then the counter is increased by one in the best cell where
the UE camps according to different service type.

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-9

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-10

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-11

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-12

 VP: video phone

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-13

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-14

 VS.RAB.AbnormRel.PS.Security: the number of RABs abnormally released due to a

security mode procedure failure in the best cell.
 The measurement is triggered at point A as shown in the figure, after a RAB is successfully
set up, the RNC sends the CN an IU RELEASE REQUEST message due to a Security Mode
procedure failure. The CN responds with an IU RELEASE COMMAND message. If the cause
value carried in the IU RELEASE COMMAND message is a value other than "User
Inactivity", "Normal Release", "Successful Relocation", and "Network Optimization" (for
details about the cause values of the IU RELEASE COMMAND message, see 3GPP TS
25.413), then the counter is increased by one in the best cell where the UE camps
according to different service type.

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-15

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-16

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-17

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-18

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-19

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-20

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-21

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-22

 Why
VS.HSDPA.H2D.Succ+VS.HSDPA.H2F.Succ+VS.HSDPA.HHO.H2D.SuccOutIntraFreq
+VS.HSDPA.HHO.H2D.SuccOutInterFreq is added in the denominator to calculate the
HSDPA service drop ratio?
 If one user switch from HS-DSCH to other channel types due to some reason
(mobility e.g.), it should be consider as a normal HS-DSCH release (refer to second
item in Notes).

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-23

 VS.HSDPA.RAB.AbnormRel
 Number of HSDPA RABs abnormal released for cell
 VS.HSDPA.RAB.NormRel
 Number of HSDPA RABs normal released for cell
 VS.HSDPA.H2D.Succ
 Number of successful handovers from HS-DSCH to DCH for cell
 VS.HSDPA.H2F.Succ
 Number of successful handovers from HS-DSCH to CCH for cell
 VS.HSDPA.HHO.H2D.SuccOutIntraFreq
 Number of successful Intra-Frequency H2D hard handovers for cell
 VS.HSDPA.HHO.H2D.SuccOutInterFreq
 Number of successful Inter-Frequency H2D hard handovers for cell

UE
RB Reconfiguration
RB Reconfiguration Complete
Counter VS.HSDPA.H2D.Succ /
RNC
VS.HSDPA.H2F.Succ /
VS.HSDPA.HHO.H2D.SuccOutIntraFreq /
S.HSDPA.HHO.H2D.SuccOutInterFreq is added by
1 in the corresponding scenarios.

· Cpounter VS.HSDPA.H2D.Succ / VS.HSDPA.H2F.Succ is triggered in H2D / H2F channel switch.

· Counter VS.HSDPA.HHO.H2D.SuccOutIntraFreq / S.HSDPA.HHO.H2D.SuccOutInterFreq is triggered in H2D
inter-frequencty / intra-frequency hard handover.
· H2D / H2F Channel switch and H2D hard handover are both completed by RB Reconfiguration procedure.

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-24

 Why
VS.HSUPA.E2D.Succ+VS.HSUPA.E2F.Succ+VS.HSUPA.HHO.E2D.SuccOutIntraFreq+
VS.HSUPA.HHO.E2D.SuccOutInterFreq is added in the denominator to calculate the
HSUPA service drop ratio?
 If one user switch from E-DCH to other channel types due to some reason (mobility
e.g.), it should be consider as a normal E-DCH release (refer to second item in
Notes).

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-25

 VS.HSUPA.RAB.AbnormRel
 Number of HSUPA RABs abnormal released for cell
 VS.HSUPA.RAB.NormRel
 Number of HSUPA RABs normal released for cell
 VS.HSUPA.E2D.Succ
 Number of successful handovers from E-DCH to DCH for cell
 VS.HSUPA.E2F.Succ
 Number of successful handovers from E-DCH to CCH for cell
 VS.HSUPA.HHO.E2D.SuccOutIntraFreq
 Number of successful Intra-Frequency E2D hard handovers for cell
 VS.HSUPA.HHO.E2D.SuccOutInterFreq
 Number of successful Inter-Frequency E2D hard handovers for cell

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-26

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-27

 If the call drop ratio is high, we need to find the reason. Some counters can indicate the
reason of call drop.

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-28

 Normally RF (radio frequency) problem is the main reason of call drop in real network such
as bad coverage or handover failure.

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-29

 VS.RAB.AbnormRel.CS.IuAAL2
 Number of CS RABs Abnormally Released for Cell Due to Iu Interface AAL2 Link Failure
 This counter is triggered when RNC finds the AAL2 path is abnormal. Maybe it is the
problem of Iu-CS transmission.
 VS.RAB.AbnormRel.CS.RF
 Number of CS RABs Abnormally Released Due to RF for Cell
 Some RF problems will trigger this counter such as bad coverage, handover failure,
interference and etc. Normally RF problem is the main reason of call drop in real network.
 VS.RAB.AbnormRel.CS.OM
 Number of CS RAB Release Requests for Cell Due to O&M Intervention
 If RAB is release by O&M intervention (For example RAB is released by MML command),
this counter will be triggered. Normally this is not the main reason of call drop in real
network.
 VS.RAB.AbnormRel.CS.Preempt
 Number of CS RAB Release Attempts for Cell Due to RAB Preemption
 During access control procedure if system resource is limited and preemption function is
enabled, a user with higher priority can preempt a user with lower priority. Then this
counter will be triggered.
 VS.RAB.AbnormRel.CS.UTRANgen
 Number of CS RAB Abnormal Releases Triggered by RNC for Cell Due to UTRAN Cause
 If RAB is released because of UTRAN problem, this counter will be triggered. If this counter
has high value, more detailed information need to be analyzed.
 VS.RAB.AbnormRel.CS.OLC
 Number of CS Domain RABs Released Due to Congestion for Cell
 If the system load is very high and over load control function is enabled, RNC can release
some RAB to reduce the load. Then this counter will be triggered.

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-30

 VS.RAB.AbnormRel.CS.RF.ULSync
 If NodeB loses the UL synchronization of the UE during service, the RAB will be
released and this counter will be triggered. Bad coverage or missing neighboring
cell configuration can triggered this counter.
 VS.RAB.AbnormRel.CS.RF.UuNoReply
 If UE can not respond to the signaling from RNC during service, the RAB will be
release and this counter will be triggered. Bad coverage can trigger this counter.
 VS.RAB.AbnormRel.CS.RF.SRBReset
 If RNC sends signaling to UE repeat but UE can not send a ACK response, RNC will
reset RLC layer. Then call drop will happen and this counter will be triggered. Bad
coverage or interference can trigger this counter.

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-31

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-32

 VS.RAB.AbnormRel.PS.GTPULoss
 Number of PS RABs Abnormally Released for Cell Due to GTPU Failure
 This counter is triggered when RNC finds the GTPU in Iu-PS user plane is abnormal.
Maybe it is the problem of Iu-PS transmission.
 VS.RAB.AbnormRel.PS.RF
 Number of PS RABs Abnormally Released Due to RF for Cell
 Some RF problems will trigger this counter such as bad coverage, handover failure,
interference and etc. Normally RF problem is the main reason of call drop in real
network.
 VS.RAB.AbnormRel.PS.OM
 Number of PS RAB Release Requests for Cell Due to O&M Intervention
 If RAB is release by O&M intervention (For example RAB is released by MML
command), this counter will be triggered. Normally this is not the main reason of
call drop in real network.
 VS.RAB.AbnormRel.PS.Preempt
 Number of PS RAB Release Attempts for Cell Due to RAB Preemption
 During access control procedure if system resource is limited and preemption
function is enabled, a user with higher priority can preempt a user with lower
priority. Then this counter will be triggered.
 VS.RAB.AbnormRel.PS.OLC
 Number of PS Domain RABs Released Due to Congestion for Cell
 If the system load is very high and over load control function is enabled, RNC can
release some RAB to reduce the load. Then this counter will be triggered.

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-33

 Normally RF problem is the main reason of call drop. More sub counters can be used to
analyze the detailed RF reason of call drop. To find the exact reason maybe more detailed
information such as drive test need to care.
 VS.RAB.AbnormRel.PS.RF.ULSync
 If NodeB loses the UL synchronization of the UE during service, the RAB will be
released and this counter will be triggered. Bad coverage or missing neighboring
cell configuration can triggered this counter.
 VS.RAB.AbnormRel.PS.RF.UuNoReply
 If UE can not respond to the signaling from RNC during service, the RAB will be
release and this counter will be triggered. Bad coverage can trigger this counter.
 VS.RAB.AbnormRel.PS.RF.SRBReset
 If RNC sends signaling to UE repeat but UE can not send a ACK response, RNC will
reset RLC layer. Then call drop will happen and this counter will be triggered. Bad
coverage or interference can trigger this counter.
 VS.RAB.AbnormRel.PS.RF.TRBReset
 If RNC sends PS data to UE repeat but UE can not send a ACK response, RNC will
reset RLC layer. Then call drop will happen and this counter will be triggered. Bad
coverage or interference can trigger this counter.

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-34

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-35

 The table shows the result of CS call drop of Top 10 cells in one month. It is from a real
network.
 In the example we can see that most of the CS call drops in the network are caused by RF
problems.

Confidential Information of Huawei. No Spreading Without Permission

 WCDMA RAN15 Call Drop KPI and Relative Counters P-36

 The table shows the result of PS call drop of Top 10 cells in one month. It is from a real
network.
 In the example we can see that most of the PS call drops in the network are caused by RF
problems.

Confidential Information of Huawei. No Spreading Without Permission

WCDMA RAN15 Call Drop KPI and Relative Counters P-37

Confidential Information of Huawei. No Spreading Without Permission