RAN KPI monitor presentation
Acceptance KPI and monitor KPI
According to consult the acceptance KPI and monitor KPI show as below
Classes
Accessibility
Retain ability
Mobility
Throughput
Classes
Traffic
User Num
Interference
resource utilization
Acceptance KPI's
KPI Value (Time)
RRC Setup Success Ratio (%)
Value
RAB Setup Success Ratio (%)
Value
CS Service Drop Ratio (%)
Value
PS Call Drop Ratio (%)
Value
Soft HO Success Ratio (%)
Value
CS W2G Inter - RAT HO out Success Ratio (%)
Value
HSDPA User Average Throughput (Kbps)
Monitor KPI's
Value
KPI Value (Time)
CS traffic
Value
PS traffic
Value
Average HSDPA Users
Value
Maximum HSDPA Users
Value
Average HSUPA Users
Value
Maximum HSUPA Users
Value
RTWP
Value
UL CE utilization
Value
TCP utilization
Value
Comments
OK. Otherwise reason for the degradation along with the
worst cells
Comments
OK. If have a large fluctuation need clarification
Page 2
RRC Connection Setup Success Ratio
Here list all RRC CSSR concert counters
Numerator
Denominator
RRC.SuccConnEstab.OrgConvCall
(RRC.AttConnEstab.OrgConvCall
RRC.SuccConnEstab.OrgStrCall
RRC.AttConnEstab.OrgStrCall
RRC.SuccConnEstab.OrgInterCall
RRC.AttConnEstab.OrgInterCall
RRC.SuccConnEstab.OrgBkgCall
RRC.AttConnEstab.OrgBkgCall
RRC.SuccConnEstab.OrgSubCall
RRC.AttConnEstab.OrgSubCall
RRC.SuccConnEstab.TmConvCall
RRC.AttConnEstab.TmConvCall
RRC.SuccConnEstab.TmStrCall
RRC.AttConnEstab.TmStrCall
RRC.SuccConnEstab.TmItrCall
RRC.AttConnEstab.TmInterCall
RRC.SuccConnEstab.TmBkgCall
RRC.AttConnEstab.TmBkgCall
RRC.SuccConnEstab.EmgCall
RRC.AttConnEstab.EmgCall
RRC.SuccConnEstab.Unkown
RRC.AttConnEstab.Unknown
RRC.SuccConnEstab.OrgHhPrSig
RRC.AttConnEstab.OrgHhPrSig
RRC.SuccConnEstab.OrgLwPrSig
RRC.AttConnEstab.OrgLwPrSig
RRC.SuccConnEstab.CallReEst
RRC.AttConnEstab.CallReEst
RRC.SuccConnEstab.TmHhPrSig
RRC.AttConnEstab.TmHhPrSig
RRC.SuccConnEstab.TmLwPrSig
RRC.AttConnEstab.TmLwPrSig
RRC.SuccConnEstab.IRATCelRes
RRC.AttConnEstab.IRATCelRes
RRC.SuccConnEstab.IRATCCO
RRC.AttConnEstab.IRATCCO
RRC.SuccConnEstab.Reg
RRC.AttConnEstab.Reg
RRC.SuccConnEstab.Detach
RRC.AttConnEstab.Detach
RRC.SuccConnEstab.MBMSRep
RRC.AttConnEstab.MBMSRep
RRC.SuccConnEstab.MBMSPtp)
RRC.AttConnEstab.MBMSPtp
Counter sampling point
Detail signaling procedure
Illustration:
1 according RRC required reasons to count RRC attempts in sampling A
2 when RNC receives RRC connection complete message, the RRC success
will be count in sampling C
3 for RRC CSSR shouldnt include RRC repeat times
Page 3
RAB Setup Success Ratio (%)
Here list all RAB SSR concert counters
Numerator
VS.RAB.SuccEstabCS.Conv
VS.RAB.SuccEstabCS.Str
VS.RAB.SuccEstabPS.Conv
VS.RAB.SuccEstabPS.Str
VS.RAB.SuccEstabPS.Int
VS.RAB.SuccEstabPS.Bkg
Denominator
VS.RAB.AttEstabCS.Conv
VS.RAB.AttEstabCS.Str
VS.RAB.AttEstabPS.Conv
VS.RAB.AttEstabPS.Str
VS.RAB.AttEstabPS.Int
VS.RAB.AttEstabPS.Bkg
Counter sampling point
According to KPI mapping with ZTE, huawei
supply counter as left table. the relative
illustrations as below
1 when RNC receive RAB ASSIGNMNT
REQUST count RAB attempts and sample at
point A
2 when RNC receive RB setup complete
message and sent RAB assignment response
will sample at Point B
3 the right chart reflect detail RAB setup
procedure.
Page 4
CS Service Drop Ratio
Here list all CS CDR concert counters
Numerator
VS.RAB.AbnormRel.CS
VS.RAB.AbnormRel.CS.Preempt
VS.RAB.AbnormRel.CS.OLC
VS.RAB.AbnormRel.CS.OM
Denominator
VS.RAB.AbnormRel.CS
VS.RAB.NormRel.CS
(VS.RAB.AbnormRel.CS -VS.RAB.AbnormRel.CS.Preempt VS.RAB.AbnormRel.CS.OLC -VS.RAB.AbnormRel.CS.OM)
/(VS.RAB.AbnormRel.CS +VS.RAB.NormRel.CS)
According to mapping ZTE formula, Huawei corresponding KPI items and
formula at right display
1 from the mapping result we can see the ZTE deduct some RAB abnormal counters in
denominator that improper logic
2 the below three chart show call drop procedure if RAB RELEASE REQUEST or IU RELEASE
REQUEST message isnt contain User InactivityNormal ReleaseSuccessful Relocation
Network Optimization or UE Generated Signaling Connection Release the call drop will
be happened
3 some comment RAB fail reason as left chart
Page 5
PS Call Drop Ratio
Here list all PS CDR concert counters
Numerator
VS.RAB.AbnormRel.PS
VS.RAB.AbnormRel.PS.PCH
VS.RAB.AbnormRel.PS.D2P
VS.RAB.AbnormRel.PS.F2P
VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.OLC
Denominator
VS.RAB.AbnormRel.PS
VS.RAB.NormRel.PS
VS.RAB.AbnormRel.PS.PCH
VS.RAB.NormRel.PS.PCH
VS.RAB.NormRel.PS.PCH
VS.DCCC.D2P.Succ
VS.DCCC.Succ.F2P
VS.DCCC.Succ.F2U
VS.DCCC.Succ.D2U
According to mapping ZTE formula, Huawei corresponding KPI
items and formula at right table
1 some comment RAB fail reason as left chart
2 since PCH in using and states retransfer enable so for the PS
call drop should use propose KPI
Page 6
HSDPA User average throughput
Huawei mapping formula: VS.HSDPA.Data.IubMacdPdu/(VS.HSDPA.All.ScheduledNum*2)
ZTE supply formula :(C310545121)/(C310546972* (2/1000));
Propose ZTE revise formula: C310545121 /(C310545123 * Gr)
C310545121: The traffic volume of UE acknowledged HSDPA user data transmitted by NodeB on MAC layer. The measurement object of this counter is CRNC-cell, the CRNC-cell is the
HSDPA serving cell.
C310546972: The number of user'TTIs that MAC-hs contains the data in the NodeB buffer. The measurement object of this counter is CRNC-cell,the CRNC-cell is the HSDPA serving cell
C310545123: The average user number for each TTI whose user data is in the NodeB's MAC-hs buffer. The average user number is for all TTIs, including these TTIs there is no user data is buffered
The measurement object of this counter is CRNC-cell, the CRNC-cell is the HSDPA serving cell.
1 the TTI schedule principle as left chart
2 according to comparison if ZTE dont revise formula, the rate reflect cell
throughput not user average throughput
user throughput=(10+10+6+6)/(3+3+2+2)=2.6
cell throughput =(10+10+6+6)/9=3.5
3 the ZTE supply formula dont consider actual schedule user for each TTI
whereas care TTI which have date transferred
Page 7
THANK YOU!
