Professional Documents
Culture Documents
Objectives
l
Page1
Contents
1. Definition Of a Call Drop
2. RNC Call Drop Counter system and KPI
3. Cell Call Drop Counter system and KPI
Page2
l
l
Page3
All Service
CDR
0.48%
0.92%
0.34%
HSDPA
CDR
0.27%
HSUPA
CDR
0.29%
Page4
Contents
1. Definition Of a Call Drop
2. RNC Call Drop Counter system and KPI
3. Cell Call Drop Counter system and KPI
Page5
Based on reasons
n
RF reasons
Non-RF reasons
Based on services:
n
AMR
CS64K
l
l
Page6
VS.RAB.Loss.CS.RF.RNC
VS.RAB.Loss.CS.Abnorm.RNC
VS.RAB.Loss.CS.Norm.RNC
Page7
If the RNC has sent an IU RELEASE REQUEST message or a RAB RELEASE REQUEST
message with the release cause of "Radio Connection With UE Lost" or "Failure in the
Radio Interface Procedure", RNC measures these by RF reason counters.
After the RABs have been successfully set up, the RNC releases the related RABs if an
exception occurs .These abnormal released RABs include all released RABs except the
following causes: Normal Release, RF Failures . For example, the AAL2 link on the Iu
interface becomes abnormal, RNC measures these by abnormal reason counters.
After call drop , according to different services, RNC measures the counters for AMR
services and video call services also.
The counters for normal RAB release are used to calculate call drop rate.
VS.RAB.Loss.CS.RF.RNC + VS.RAB.Loss.CS.Abnorm.RNC
VS.RAB.Loss.CS.RF.RNC + VS.RAB.Loss.CS.Abnorm.RNC + VS.RAB.Loss.CS.Norm
l
l
Page8
Similar counters are defined for PS services based on release reason and Max bit rate.
Because of some specific UE, UE signaling trigged releases are not taken as call drop. That
means VS.RAB.Loss.PS.Abnorm.RNC exclude UE signaling trigged releases .
VS.RAB.Loss.CS.AMR.RNC
VS.RAB.Loss.CS.Conv64K.RNC
Page9
After call drop , according to different services, RNC measures the counters for AMR
services and video call services.
Here , the RNC level service normal releases is the sum of the cell level counters.
Questions
l
How to calculate RNC level AMR and VP services call drop Rate ?
Page10
VS.RAB.Loss.CS.AMR.RNC
VS.RAB.Loss.CS.AMR.R NC + VS.RAB.Loss.CS.Norm.AMR
VS.RAB.Loss.CS.Conv64K.RNC
VS.RAB.Loss.CS.Conv64K.RNC + VS.Norm.Rel.CS.Conv.RB.64
Based on reasons
n
RF reasons
Non-RF reasons
l
l
Page11
For PS domain, there are call drop counters for services with different typical rates.
For analyze, same as the CS counters ,there are call drop counters based on reasons,
include RF reasons and Non-RF reasons.
VS.RAB.Loss.PS.RF.RNC
VS.RAB.Loss.PS.Abnorm.RNC
VS.RAB.Loss.PS.Norm
Page12
VS.RAB.Loss.PS.RF.RNC + VS.RAB.Loss.PS.Abnorm.RNC
VS.RAB.Loss.PS.RF.RNC + VS.RAB.Loss.PS.Abnorm.RNC + VS.RAB.Loss.PS.Norm
l
l
Page13
Similar counters are defined for PS services based on release reason and Max bit rate.
Because of some specific UE, UE signaling trigged releases are not taken as call drop. That
means VS.RAB.Loss.PS.Abnorm.RNC exclude UE signaling trigged releases .
Contents
1. Definition Of a Call Drop
2. RNC Call Drop Counter system and KPI
3. Cell Call Drop Counter system and KPI
Page14
Contents
3. Cell Call Drop Counter system and KPI
3.1 R99 Service Call Drop Counter System and KPI
3.2 HSPA Service Call Drop Counter System and KPI
Page15
VS.RAB.Loss.CS.RF
VS.RAB.Loss.CS.Abnorm
VS.RAB.Loss.CS.Norm
Page16
After a call drop, according to the call drop reason, RNC measure these counters in the
best cell.
The call drop reasons include RF reasons , abnormal reasons.
VS.RAB.Loss.CS.RF + VS.RAB.Loss.CS.Abnorm
VS.RAB.Loss.CS.RF + VS.RAB.Loss.CS.Abnorm + VS.RAB.Loss.CS.Norm
Page17
Number of CS domain RAB releases triggered by the RNC due to RLC reset
n
VS.RAB.Loss.CS.RF.RLCRst
VS.RAB.Loss.CS.RF.ULSync
VS.RAB.Loss.CS.RF.UuNoReply
Page18
VS.RAB.RelReqCS.RABPreempt
VS.RAB.RelReqCS.OM
VS.RAB.Loss.CS.Congstion.CELL
VS.RAB.Loss.CS.Aal2Loss
l
l
l
Page19
Cause of "O&M Intervention: by LMT, any user or service can be released manually.
Cause of "RAB pre-empted and CELL Congestion are related to load control algorithm.
Cause of Iu Interface AAL2 Link Failure is related to the Iu transmission.
VS.RAB.Loss.PS.RF
VS.RAB.Loss.PS.Abnorm
VS.RAB.Loss.PS.Norm
Page20
After a call drop, according to the call drop reason, RNC measure these counters in the
best cell.
The call drop reasons include RF reasons , abnormal reasons.
Page21
Number of PS domain RAB releases triggered by the RNC due to RLC reset
n
VS.RAB.Loss.PS.RF.RLCRst
VS.RAB.Loss.PS.RF.ULSync
VS.RAB.Loss.PS.RF.UuNoReply
l
l
Page22
VS.RAB.RelReqPS.RABPreempt
VS.RAB.RelReqPS.OM
VS.RAB.Loss.PS.Congstion.CELL
VS.RAB.Loss.PS.GTPULoss
Page23
The counters for abnormal failures are similar with the CS counters.
Questions
l
How to calculate Cell level AMR and VP services call drop Rate ?
Can you tell the procedure of the call drop caused by missing
neighbors?
Page24
Contents
3. Cell Call Drop Counter system and KPI
3.1 R99 Service Call Drop Counter System and KPI
3.2 HSPA Service Call Drop Counter System and KPI
Page25
VS.HSDPA.RAB.Loss.RF
VS.HSDPA.RAB.Loss.Abnorm.NonRF
VS.HSDPA.RAB.Loss.Norm
l
l
Page26
If the RAB is set up for the HSDPA service, the RNC measures the items in the HSDPA cell
that the UE camps on after HSDPA call drop.
The call drop reasons could be RF or abnormal (Non-RF) reasons.
Because of some specific UE, UE signaling trigged releases are not taken as call drops,
these releases are included in VS.HSDPA.RAB.Loss.Norm
VS.HSUPA.RAB.Loss.Abnorm
VS.HSUPA.RAB.Loss.Norm
Page27
Page28
Thank you
www.huawei.com