SYV KPIs
targets and formulas
29-05-2020
1
© 2020 Nokia
Confidential
SYV KPIs: targets and formulas
Contents
Nokia committed KPI targets: 2G, 3G, 4G
Nokia proposal for 5G KPI targets
KPI formula conversions between Huawei and Nokia
2G
3G
5G KPIs
ANNEX
2
© 2020 Nokia
Confidential
4G
Target KPIs for 2G, 3G and 4G
Nokia commitment: same or better
Nokia commits to same or better KPIs. SYV has confirmed and demonstrated that the KPI levels in the network reach or
exceed these KPI levels. Thereby Nokia can commit to reaching these KPIs.
Final Acceptance (MSA target level)
Voice
2G
3G
4G
Call Setup
Success
Rate
99,80 %
99,80 %
99,80 %
Data
Minutes
Per Drop
Mobile Call
Defect Ratio
Voice Call
Drop Rate
PS Setup
Success Rate
PS Connection
Drop Rate
User Downlink
Data Rate
Availability
750
2200
2400
99,30 %
99,70 %
99,80 %
0,60 %
0,20 %
0,20 %
99,00 %
99,70 %
99,90 %
0,75 %
0,20 %
0,10 %
3840
27000
99,85 %
99,85 %
99,85 %
Conditional acceptance
Voice
2G
3G
4G
3
Call Setup
Success
Rate
99,73 %
99,73 %
99,73 %
© 2020 Nokia
Data
Minutes
Per Drop
Mobile Call
Defect Ratio
Voice Call
Drop Rate
PS Setup
Success Rate
PS Connection
Drop Rate
User Downlink
Data Rate
Availability
650
2000
2200
99,00 %
99,55 %
99,65 %
0,75 %
0,25 %
0,25 %
98,70 %
99,58 %
99,86 %
0,80 %
0,25 %
0,20 %
2900
22000
99,80 %
99,80 %
99,80 %
Confidential
Target KPIs for 5G
Nokia commitment: Gradual increase in target level with growing coverage, user penetration and device
stability
Final Acceptance end of 2022
Voice
5G FDD
5G TDD
Call
Setup
Minutes
Mobile Call
Voice Call
Success
Per Drop
Defect Ratio
Drop Rate
Rate
Voice KPIs to be agreed when available in the devices
-
Data
Accessibility
PS Connection
Drop Rate
User Downlink
Data Rate
Availability
99%
99%
0.5%
0.5%
150Mbps
150Mbps
99.5%
99.5%
Final acceptance end of 2021
Voice
5G FDD
5G TDD
Call
Setup
Minutes
Mobile Call
Voice Call
Success
Per Drop
Defect Ratio
Drop Rate
Rate
Voice KPIs to be agreed when available in the devices
-
Data
Accessibility
PS Connection
Drop Rate
User Downlink
Data Rate
Availability
98.5%
98.5%
1.0%
1.0%
125Mbps
125Mbps
99.0%
99.0%
PS Connection
Drop Rate
User Downlink
Data Rate
Availability
2.0%
2.0%
100Mbps
100Mbps
98.5%
98.5%
Conditional acceptance
Voice
Call
Setup
Minutes
Mobile Call
Voice Call
Accessibility
Success
Per Drop
Defect Ratio
Drop Rate
Rate
- Confidential 98.0%
45G FDD
© 2020 Nokia
Voice KPIs to be agreed when available in the devices
5G TDD
98.0%
Data
2G KPI Formula conversions
5
© 2020 Nokia
Confidential
2G CSSR_SYV (%) 1/6
Huawei Formula
Formula: 2G CSSR_SYV (%)={100}*([CA313:Successful Assignments]/[CA310:Assignment Requests])
Description : This KPI provides the rate of successful calls initiated by the MS from the call setup
procedure to the assignment completion procedure
CA313
6
© 2020 Nokia
Confidential
2G CSSR_SYV (%) 1/6
Nokia Formula
Formula: 2G CSSR_SYV (%)= 100*(057033:TCH_NEW_CALL_ASSIGN/057028:TCH_CALL_REQ)
Description : This KPI provides the rate of successful calls initiated by the MS from the call setup
procedure to the assignment completion procedure
TCH_NEW_CALL_ASSIGN : When an ASSIGNMENT_COMPLETE message is received on TCH from the BTS in a case
of a new call. In a case of FACCH call set-up due to SDCCH congestion, this counter is updated, when an
ESTABLISH_INDICATION message is received on the TCH from the BTS. In case of normal directed retry (inter-cell
directed retry), this counter is updated, when a HANDOVER_COMPLETE message is received on the TCH from the BTS.
This counter is also updated with S6 feature TCH Assignment to Super-reuse TRX in IUO (intra-cell/inter-cell directed
retry) and with S7 feature Direct Access to Super-reuse TRX in IUO. If external SDCCH to SDCCH handover is made after
a re-establishment, this counter is also updated.
TCH_CALL_REQ: When the TCH channel is requested from the RRM. This counter includes all TCH requests, except
TCH to TCH handovers.
This counter is not updated in re-establishment case.
7
© 2020 Nokia
Confidential
2G CS DCR_SYV (%) 2/6
Huawei formula
Formula: 2G CS DCR_SYV (%) = {100}*(CM33/CA313)
CM33:Call Drops on Traffic Channel
CA313:Successful Assignments
CM33
8
© 2020 Nokia
Confidential
2G CS DCR_SYV (%) 2/6
Nokia formula
Formula: 2G CS DCR_SYV (%) = 100*(a.tch_radio_fail - a.tch_rel_due_rad_fail_ph_2_3 + a.tch_rf_old_ho +a.tch_lapd_fail
+ a.tch_bts_fail + a.tch_bcsu_reset +a.tch_abis_fail_old + a.tch_tr_fail_old)/(a.tch_radio_fail - a.tch_rel_due_rad_fail_ph_2_3
+ a.tch_rf_old_ho +a.tch_lapd_fail + a.tch_bts_fail + a.tch_user_act + a.tch_bcsu_reset + a.tch_netw_act +
a.tch_act_fail_call + a.tch_abis_fail_old + a.tch_tr_fail_old + b.tch_norm_release)
NOTE: KPI might not 100% matched as its not clear the drops counted in H// case are those between ASSIGNMENT
COMPLETE and L3 or L2 DISCONNECT
Tch_radio_fail: When a TCH transaction ends because of a radio failure and the RRM releases the TCH. This counter is
typical in connection with coverage problems. ERROR INDICATION is sent by the BTS to the BSC in the following cases:
- Sequence error in a received message (the case where retransmission is not possible).
- Timer T200 has expired N200 +1 times (MS does not respond any more).
- Unsolicited DM response when link is established.
This counter is updated in call phases 1-8 or 15 only.
tch_rel_due_rad_fail_ph_2_3: removes Assignement failures included in
tch_radio_fail (T3107 expiry)
9
© 2020 Nokia
Confidential
2G MPD_SYV (Min) 3/6
Huawei formula
Formula: 2G MPD_SYV (Min) = 60*[K3014:Traffic Volume on TCH]/[CM33:Call Drops on Traffic Channel]
Description: Minutes per drop is the ratio between traffic on TCH to the number call drops on traffic
channel measured over 60 minutes.
10
© 2020 Nokia
Confidential
2G MPD_SYV (Min) 3/6
Nokia formula
Formula: 2G MPD_SYV (Min) =
[(resavail.ave_tch_busy_full+resavail.ave_tch_busy_half)*resavail.period_duration)]/(tch_radio_fail tch_rel_due_rad_fail_ph_2_3 + tch_rf_old_ho +tch_lapd_fail + tch_bts_fail + tch_bcsu_reset
+tch_abis_fail_old + tch_tr_fail_old)
Description: Minutes per drop is the ratio between traffic on TCH to the number call drops on traffic
channel measured over 60 minutes.
NOTE: KPI might not 100% matched as its not clear the drops counted in H// case are those between ASSIGNMENT
COMPLETE and L3 or L2 DISCONNECT
11
© 2020 Nokia
Confidential
2G MCDR_SYV (%) 4/6
Huawei formula
Formula: 2G MCDR_SYV (%) = {100}*(1-([CM330:Call Drops on Radio Interface in Stable State (Traffic
Channel)]+[CM331:Call Drops on Radio Interface in Handover State (Traffic Channel)]+[CA312:Failed
Assignments (Channel Unavailable)])/([CA313:Successful Assignments]+[CA312:Failed Assignments
(Channel Unavailable)]))
Description: This KPI is the ratio between the number of call drops by CM330+CM331+CA312 to total
number of assignments (Successful + Failed assignments)
CM330
12
© 2020 Nokia
CM331
Confidential
2G MCDR_SYV (%) 4/6
Nokia formula
Formula: 2G MCDR_SYV (%) = 100*[1-{(057028:TCH_CALL_REQ - 057030:SERVED_TCH_CALL_REQ) +
(BSC_O_HO_CMD_ASSGN + MSC_O_HO_CMD + CELL_TCH_TCH_AT - CELL_TCH_TCH - BSC_O_TCH_TCH
- MSC_O_TCH_TCH) + (tch_radio_fail - tch_rel_due_rad_fail_ph_2_3 )}/{(057028:TCH_CALL_REQ 057030:SERVED_TCH_CALL_REQ)+057033:TCH_NEW_CALL_ASSIGN}
057028:TCH_CALL_REQ - 057030:SERVED_TCH_CALL_REQ): TCH Blocking NEW CALL ONLY, this internal BSC after physical
context and before channel activation
(BSC_O_HO_CMD_ASSGN + MSC_O_HO_CMD + CELL_TCH_TCH_AT - CELL_TCH_TCH - BSC_O_TCH_TCH MSC_O_TCH_TCH): HO Failures i.e. Missing HO CPML
(tch_radio_fail - tch_rel_due_rad_fail_ph_2_3 ) : When the drop occurs between ASSIGNMENT COMPLETE and DISCONNECT
in case of the basic call
13
© 2020 Nokia
Confidential
2G MCDR_SYV (%) 4/6
Nokia formula - Comment
057028:TCH_CALL_REQ - 057030:SERVED_TCH_CALL_REQ): TCH Blocking NEW CALL ONLY, this internal BSC after physical context and
before channel activation
Comments: KPI is not 100% matched as it is not clear what is inside CM330 exactly, its not clear if CA312
includes HO or only new calls and its not clear if blocking only or assignment failure is included - it has to
be noted that also the messages where req and succ are pegged are not clear does it include phyContext
and ChanActivation, Nokia blocking counters are logical BSC counters before Channel Activation
(057030:SERVED_TCH_CALL_REQ - 057033:TCH_NEW_CALL_ASSIGN): TCH Assignment Failure NEW CALLS
ONLY
14
© 2020 Nokia
Confidential
2G PS SSR_SYV (%) 5/6
Huawei formula
Formula:2G PS SSR_SYV (%) = {100}*([A9102:Number of Successful Downlink GPRS TBF
Establishments]+[A9302:Number of Successful Downlink EGPRS TBF Establishments])/ ([A9101:Number
of Downlink GPRS TBF Establishment Attempts]+[A9301:Number of Downlink EGPRS TBF Establishment
Attempts])
Description : This KPI provides the success rate of downlink TBF establishments during downlink TBF
establishment procedure.
15
© 2020 Nokia
Confidential
2G PS SSR_SYV (%) 5/6
Nokia formula
Formula:2G PS SSR_SYV (%) = 100*(pcu.nbr_of_dl_tbf-pcu.dl_tbf_establishment_failedpcu.dl_egprs_tbf_rel_due_no_resp) / (pcu.nbr_of_dl_tbf)
Description : This KPI provides the success rate of downlink TBF establishments during downlink TBF
establishment procedure.
nbr_of_dl_tbf : The number of all downlink TBF establishments, including both acknowledged mode and
unacknowledged mode downlink TBF establishments. When a downlink TBF is established, that is, when a new downlink
TBF is created and resources have been allocated for it. The counter is triggered after IMMEDIATE_ASSIGNMENT,
PACKET_DOWNLINK_ASSIGNMENT messages.
16
© 2020 Nokia
Confidential
GSM Availability_SYV (%) 6/6
Huawei formula
Formula: GSM Availability_SYV (%) = {100}*CR373/({GP}*{60})
Description:
CR373: measures the duration of a cell in service in a GP.
GP: measurement period (Minute)
17
© 2020 Nokia
Confidential
GSM Availability_SYV (%) 6/6
Nokia formula
Formula: GSM Availability_SYV (%) = 100*(bcch_uptime) / (bcch_uptime+bcch_downtime)
Description: Cell Availability defined as the percentage of time in seconds the cell has an active BCCH
(and the alarm 7767 BCCH MISSING is NOT active).
bcch_uptime: Number of seconds the cell has an active BCCH and the alarm 7767 BCCH MISSING is not active.
UPDATED: With the number of BCCH uptime seconds at the end of BCCH uptime period. The BCCH uptime period starts
when the cell regains the working BCCH it has previously lost and the alarm 7767 BCCH MISSING is cancelled by the
system. The BCCH uptime period ends when the cell loses the working BCCH and the alarm 7767 is activated by the
system.
BCCH uptime period ends also in that case, when user locks the working BCCH TRX or its BTS/BCF to locked
administrative state.
18
© 2020 Nokia
Confidential
3G KPI Formula conversions
19
© 2020 Nokia
Confidential
3G CSSR_SYV(%) 1/8
Huawei formula
Formula: 3G CSSR_SYV (%) =
{100}*(VS.RAB.SuccEstabCS.AMR+VS.RAB.SuccEstabCS.AMRWB)/(VS.RAB.AttEstab.AMR+VS.RAB.AttEsta
bCS.AMRWB)
Description: This KPI is used to check the RAB Setup Success Ratio of the AMR Service, this formula
contains both NB-AMR and WB-AMR RAB setup procedure.
AMR RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT
REQUEST message from the CN for the CS AMR services.
The AMR RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE
message to the RNC. This procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the CN in the CS domain.
20
© 2020 Nokia
Confidential
3G CSSR_SYV(%) 1/8
Nokia formula
Formula: 3G CSSR_SYV (%) = {100}*rab_acc_comp_cs_voice / rab_stp_att_cs_voice))
Description: This KPI is used to check the RAB Setup Success Ratio of the AMR Service, this formula
contains both NB-AMR and WB-AMR RAB setup procedure.
AMR RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT
REQUEST message from the CN for the CS AMR services.
The AMR RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE
message to the RNC. This procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the CN in the CS domain.
21
© 2020 Nokia
Confidential
3G PS SSR_SYV(%) 2/8
Huawei formula
Formula: 3G PS SSR_SYV (%) = (Number of PS RAB Setup Successes/Number of PS RAB Setup
Attempts) x 100%
Associated Counters : {100}*[(VS.RAB.SuccEstabPS.Conv +VS.RAB.SuccEstabPS.Bkg +
VS.RAB.SuccEstabPS.Int + VS.RAB.SuccEstabPS.Str + VS.DCCC.P2F.Succ + VS.DCCC.URAP2F.Succ +
VS.DCCC.P2D.Succ + VS.DCCC.URAP2D.Succ)/(VS.RAB.AttEstabPS.Conv + VS.RAB.AttEstabPS.Bkg
+VS.RAB.AttEstabPS.Int + VS.RAB.AttEstabPS.Str + VS.DCCC.P2F.Att +VS.DCCC.URAP2F.Att +
VS.DCCC.P2D.Att + VS.DCCC.URAP2D.Att)]
Description: This KPI is used to check the RAB Setup Success Ratio of all PS services in an RNC or a
cluster.
The PS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT
REQUEST message from the SGSN in the PS domain, the message contains information about one of
the following service types: Conversational services, Streaming services, Interactive Services,
Background Services.
The PS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP
COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB
ASSIGNMENT RESPONSE message to the SGSN in the PS domain.
22
© 2020 Nokia
Confidential
3G PS SSR_SYV(%) 2/8
Nokia formula
Formula: 3G PS SSR_SYV (%) = (Number of PS RAB Setup Successes/Number of PS RAB Setup
Attempts) x 100%
Associated Counters : {100}*(sum(rab_acc_comp_ps_strea + rab_acc_comp_ps_inter +
rab_acc_comp_ps_backg + RAB_ACC_COMP_PS_CONV + succ_pch_dch_trans_umrlc –
cell_update_succ_cs_call + denom_st_trans_time_pch_fach)
/ (sum(rab_stp_att_ps_strea + rab_stp_att_ps_inter + rab_stp_att_ps_backg + RAB_STP_ATT_PS_CONV +
att_pch_dch_trans_umrlc - cell_update_att_cs_call + att_pch_to_fach)
Description: This KPI is used to check the RAB Setup Success Ratio of all PS services in an RNC or a
cluster.
The PS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT
REQUEST message from the SGSN in the PS domain, the message contains information about one of
the following service types: Conversational services, Streaming services, Interactive Services,
Background Services.
The PS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP
COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB
ASSIGNMENT RESPONSE message to the SGSN in the PS domain.
23
© 2020 Nokia
Confidential
3G CS DCR_SYV (%) 3/8
Huawei formula
Formula: 3G CS DCR_SYV (%) = ((VS.RAB.AbnormRel.AMR +VS.RAB.AbnormRel.AMRWB)
/(VS.RAB.AbnormRel.AMR +VS.RAB.NormRel.AMR +VS.RAB.AbnormRel.AMRWB
+VS.RAB.NormRel.AMRWB) )*100%
Description: This KPI provides the ratio of AMR RAB abnormal Releases to the total AMR RAB Releases
(Normal Release + Abnormal Release) and is used to check the retainability of AMR Service within the
UTRAN (RNC or Cluster).
This formula contains abnormal release and normal release of both NB-AMR and WB-AMR.
Description of RAB abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to
exception. If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following messages: "User Inactivity", "Normal Release", "Successful Relocation",
"Network Optimization", the RNC measures the items according to the service types in the best cell that
the UE camps on if the released RABs belong to CS domain.
24
© 2020 Nokia
Confidential
3G CS DCR_SYV (%) 3/8
Nokia formula
Formula: 3G CS DCR_SYV (%) = 100* (rab_act_rel_cs_voice_p_emp + rab_act_fail_cs_voice_iu +
rab_act_fail_cs_voice_radio + rab_act_fail_cs_voice_bts + rab_act_fail_cs_voice_iur + rab_act_fail_cs_voice_rnc +
rab_act_fail_cs_voice_ue + rab_act_fail_cs_voice_trans) /
(rab_act_comp_cs_voice + rab_act_rel_cs_voice_srnc + rab_act_rel_cs_voice_p_emp + rab_act_rel_cs_voice_hho +
rab_act_rel_cs_voice_isho + rab_act_rel_cs_voice_ganho + rab_act_fail_cs_voice_iu + rab_act_fail_cs_voice_radio +
rab_act_fail_cs_voice_bts + rab_act_fail_cs_voice_iur + rab_act_fail_cs_voice_rnc + rab_act_fail_cs_voice_ue +
rab_act_fail_cs_voice_trans)
Description: This KPI provides the ratio of AMR RAB abnormal Releases to the total AMR RAB Releases (Normal Release +
Abnormal Release) and is used to check the retainability of AMR Service within the UTRAN (RNC or Cluster).
This formula contains abnormal release and normal release of both NB-AMR and WB-AMR.
Description of RAB abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exception. If the
RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with any one of the following messages:
"User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", the RNC measures the items
according to the service types in the best cell that the UE camps on if the released RABs belong to CS domain.
25
© 2020 Nokia
Confidential
3G PS DCR_SYV (%) 4/8
Huawei formula
Formula: 3G PS DCR_SYV = (Number of PS RAB Abnormal Releases/Total Number of PS RAB Releases) x 100%
Description: This KPI provides the ratio of the PS RAB abnormal Releases to the total PSRAB Releases (Normal Release +
Abnormal Release) and is used to check the retainabililty of PS Service within the UTRAN (RNC or Cluster).
Associated Counters : [(VS.RAB.AbnormRel.PS - VS.RAB.AbnormRel.PS.PCH -VS.RAB.AbnormRel.PS.D2P VS.RAB.AbnormRel.PS.F2P ) /
(VS.RAB.AbnormRel.PS + VS.RAB.NormRel.PS -VS.RAB.AbnormRel.PS.PCH -VS.RAB.NormRel.PS.PCH +
VS.DCCC.D2P.Succ +VS.DCCC.Succ.F2P+VS.DCCC.Succ.F2U+VS.DCCC.Succ.D2U )]
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exception. If the
RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with any one of the following
information: "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if the released RABs belong to PS domain.
A RAB release caused by UE's state transition from CELL_DCH to CELL_PCH or URA_PCH without PS data transmission
should be considered as a normal RAB release because the transition has no impact on user experience. Therefore, PCHrelated abnormal RAB releases caused by state transition from CELL_DCH to CELL_PCH or URA_PCH are not taken into
account for calculating PS Call Drop Ratio.
26
© 2020 Nokia
Confidential
3G PS DCR_SYV (%) 4/8
Nokia formula
Formula: 3G PS DCR_SYV = ((rab_act_fail_ps_inter_bts + rab_act_fail_ps_inter_iu + rab_act_fail_ps_inter_iur +
rab_act_fail_ps_inter_radio + rab_act_fail_ps_inter_rnc + rab_act_fail_ps_inter_ue + rab_act_fail_ps_inter_trans +
rab_act_fail_ps_backg_bts + rab_act_fail_ps_backg_iu + rab_act_fail_ps_backg_iur + rab_act_fail_ps_backg_radio
+ rab_act_fail_ps_backg_rnc + rab_act_fail_ps_backg_ue + rab_act_fail_ps_backg_trans RAB_ACT_FAIL_PS_BACKG_PCH - RAB_ACT_FAIL_PS_INT_PCH)) / ((rab_act_comp_ps_backg +
rab_act_comp_ps_inter + rab_act_rel_ps_backg_srnc + rab_act_rel_ps_inter_srnc + rab_act_rel_ps_backg_hho +
rab_act_rel_ps_inter_hho + rab_act_rel_ps_bgr_isho + rab_act_rel_ps_inter_isho + rab_act_fail_ps_inter_iu +
rab_act_fail_ps_inter_radio + rab_act_fail_ps_inter_bts + rab_act_fail_ps_inter_iur + rab_act_fail_ps_inter_rnc +
rab_act_fail_ps_inter_ue + rab_act_fail_ps_inter_trans + rab_act_fail_ps_backg_iu + rab_act_fail_ps_backg_radio
+ rab_act_fail_ps_backg_bts + rab_act_fail_ps_backg_iur + rab_act_fail_ps_backg_rnc + rab_act_fail_ps_backg_ue
+ rab_act_fail_ps_backg_trans - RAB_ACT_FAIL_PS_BACKG_PCH - RAB_ACT_FAIL_PS_INT_PCH +
DENOM_ST_TRANS_TIME_DCH_PCH + DENOM_ST_TRANS_TIME_FACH_PCH)))
KPI NOT MATCHED
Nokia formula doesn’t include all the RAB release due PCH/DCH transitions and in general the formula might give -ve
numerator as RAB are much less than packets represented in counters below
(VS.DCCC.D2P.Succ+VS.DCCC.Succ.F2P+VS.DCCC.Succ.F2U+VS.DCCC.Succ.D2U )
Nokia is missing counters (VS.RAB.NormRel.PS.PCH/VS.RAB.AbnormRel.PS.D2P/ VS.RAB.AbnormRel.PS.F2P) which are
RAB release due to failure in the DCH/FACH to PCH/URA PCH transitions and normal RAB release while in cell PCH
27
© 2020 Nokia
Confidential
3G MPD_SYV(Min) 5/8
Huawei formula
Formula: 3G MPD_SYV (Min)
= [VS.AMR.Erlang.BestCell]*{GP}/([VS.RAB.AbnormRel.AMR]+[VS.RAB.AbnormRel.AMRWB])
Description: This KPI is used to check the Minutes per drop in the network. It is calculated by formula:
AMR traffic erlang of the best cell during the measurement period upon the number of AMR RAB
abnormal releases. This formula contains abnormal release and normal release of both NB-AMR and
WB-AMR.
GP: measurement period (Minute)
28
© 2020 Nokia
Confidential
3G MPD_SYV(Min) 5/8
Nokia formula
Formula: 3G MPD_SYV (Min) = ((avg_rab_hld_tm_cs_voice)/(100*60)) / (rab_act_rel_cs_voice_p_emp +
rab_act_fail_cs_voice_iu + rab_act_fail_cs_voice_radio + rab_act_fail_cs_voice_bts +
rab_act_fail_cs_voice_iur + rab_act_fail_cs_voice_rnc + rab_act_fail_cs_voice_ue +
rab_act_fail_cs_voice_trans))
Description: This KPI is used to check the Minutes per drop in the network. It is calculated by formula:
AMR traffic erlang of the best cell during the measurement period upon the number of AMR RAB
abnormal releases. This formula contains abnormal release and normal release of both NB-AMR and
WB-AMR.
GP: measurement period (Minute)
29
© 2020 Nokia
Confidential
3G MCDR_SYV (%) 6/8
Huawei formula
Formula: 3G MCDR_SYV(%) = 100*(1-([VS.RAB.AttEstab.AMR][VS.RAB.SuccEstabCS.AMR]+[VS.RAB.AbnormRel.AMR])/[VS.RAB.AttEstab.AMR])
Description: This KPI provides the ratio of total number of AMR success finish to total number of AMR
RAB attempted. Only contains counter related NB-AMR
30
© 2020 Nokia
Confidential
3G MCDR_SYV (%) 6/8
Nokia formula
Formula: 3G MCDR_SYV(%) = 100*(rab_stp_att_cs_voice - rab_acc_comp_cs_voice +
(rab_act_rel_cs_voice_p_emp + rab_act_fail_cs_voice_iu + rab_act_fail_cs_voice_radio +
rab_act_fail_cs_voice_bts + rab_act_fail_cs_voice_iur + rab_act_fail_cs_voice_rnc +
rab_act_fail_cs_voice_ue + rab_act_fail_cs_voice_trans))/ rab_stp_att_cs_voice
Description: This KPI provides the ratio of total number of AMR success finish to total number of AMR
RAB attempted.
31
© 2020 Nokia
Confidential
3G MCDR_SYV (%) 6/8
Nokia formula - Comment
If only NB-AMR is to be considered
Formula: 3G MCDR_SYV(%) = ((servlev.rab_stp_att_cs_voice - RAB_STP_ATT_WB_CS_VOI) (servlev.rab_acc_comp_cs_voice - RAB_ACC_COMP_WB_CS_VOI) + [(rab_act_rel_cs_voice_p_emp +
rab_act_fail_cs_voice_iu + rab_act_fail_cs_voice_radio + rab_act_fail_cs_voice_bts +
rab_act_fail_cs_voice_iur + rab_act_fail_cs_voice_rnc + rab_act_fail_cs_voice_ue +
rab_act_fail_cs_voice_trans) - (rab_act_fail_wb_cs_voi_iu + rab_act_fail_wb_cs_voi_radio +
rab_act_fail_wb_cs_voi_bts + rab_act_fail_wb_cs_voi_iur + rab_act_fail_wb_cs_voi_rnc +
rab_act_fail_wb_cs_voi_ue + rab_act_fail_wb_cs_voi_trans)])/ (servlev.rab_stp_att_cs_voice RAB_STP_ATT_WB_CS_VOI)
32
© 2020 Nokia
Confidential
3G data speed_SYV (kbps) 7/8
Huawei formula
Formula: 3G data speed_SYV (kbps) = [VS.DataOutput.Mean]/([VS.DataTtiRatio.Mean][VS.HSDPA.InactiveDataTtiRatio.Mean])
Description: Mean Throughput for One HSDPA Cell. This counter provides the MAC-hs throughput
when at least one HSDPA user is transferring data at the physical layer during the entire measurement
period.
33
© 2020 Nokia
Confidential
3G data speed_SYV (kbps) 7/8
Nokia formula
Formula: 3G data speed_SYV (kbps) = ( (received_hs_macd_bits-discarded_hs_macd_bits
+(mc_hsdpa_orig_data_pri+mc_hsdpa_orig_data_sec)*8) * 500) /
(hs_scch_pwr_dist_class_0 + hs_scch_pwr_dist_class_1 + hs_scch_pwr_dist_class_2 + hs_scch_pwr_dist_class_3 +
hs_scch_pwr_dist_class_4 + hs_scch_pwr_dist_class_5)
Description: The average active HS-DSCH MAC-d cell throughput from network perspective calculated as the HSDPA
MAC-d throughput at BTS divided by the active HS-DSCH time from the network perspective. The active time refers to
the scheduled TTIs, i.e. when sending data.
The throughput is looked at from MAC-d layer, i.e. how much MAC-d level data the HS-DSCH is able to successfully
transfer to UEs using the scheduled TTIs, so this considers also the MAC-hs efficiency.
KPI Not Fully Matched
1- H// doesn’t use the Data volume in numerator but average throughput over 5s to calculate b/s -- Nokia on the other
hand uses the Data Volume on MAC-d Level
2- denom is not very clear if it matches 100% H// uses TTI ratio when there is atleast one user with Data in buffer to
transfer - TTI ratio when there is data in buffer but no transmission happening-- Nokia uses the samples or active TTI
(when sending data) falling in different SCCH power classes
34
© 2020 Nokia
Confidential
3G Availability_SYV (%) 8/8
Huawei formula
Formula: 3G Availability_SYV (%) = (1-[VS.Cell.UnavailTime.Sys]/({GP}*{60})）*100%
Description: VS.Cell.UnavailTime.Sys : This counter provides the duration of cell unavailability. It is not
measured if a cell is blocked through the LMT or deleted by the dynamic shutdown algorithm. A cell
becomes unavailable when the cell is not set up, the common transport channel (CCH) or the
equipment is faulty after the cell is set up, or the NCP or CCP is faulty. When a cell is unavailable, all
services carried on the cell are interrupted.
Measurement point
After a cell becomes unavailable, the RNC measures the duration of cell unavailability. At the end of a
measurement period, the RNC accumulates the unavailability duration of each cell in the cell range to
obtain the value of this counter.
35
© 2020 Nokia
Confidential
3G Availability_SYV (%) 8/8
Nokia formula
Formula: 3G Availability_SYV (%) = 100*(avail_wcell_in_wo_state) / (avail_wcell_exists_in_rnw_db avail_wcell_blocked_by_user))
Description: Cell Availability, excluding blocked by user state (BLU). The KPI gives cell availability defined
as the percentage of time the cell(s) is in working state. This KPI shows specifically the availability on
times when the cell has not been BLU.
Measurement point
avail_wcell_in_wo_state :The number of samples when WCEL is in Working or power saving state.
Counter M1000C180 is always updated along with this counter. In power saving state BL(P) also
M1000C378 is updated. The counter is updated with the value 1 once in approximately 5 seconds when
the WCEL is in Working or power saving BL(P) state.
36
© 2020 Nokia
Confidential
4G KPI Formula conversions
37
© 2020 Nokia
Confidential
MCDR_VoLTE_SYV(%) 1/8
Huawei formula
Formula: [4G MCDR_VoLTE_SYV(%)] ={100}*(( [L.E-RAB.InitSuccEst.QCI.1] -[L.E-RAB.AbnormRel.QCI.1] )/ [L.ERAB.InitAttEst.QCI.1] )
Description: It’s the ration of difference between Initial establishment success of QCI1 E-RAB and QCI1 E-RAB
abnormal release to initial establishment attempt of QCI1 E-RAB.
38
© 2020 Nokia
Confidential
MCDR_VoLTE_SYV(%) 1/8
Nokia formula
Formula: [4G MCDR_VoLTE_SYV(%)] ={100}*(ERAB_INI_SETUP_SUCC_QCI1 + ERAB_ADD_SETUP_SUCC_QCI1 ERAB_REL_TEMP_QCI1 - ERAB_REL_ENB_ACT_QCI1)/(ERAB_INI_SETUP_ATT_QCI1 + ERAB_ADD_SETUP_ATT_QCI1)
Description: It’s the ratio of difference between Initial establishment success of QCI1 E-RAB and QCI1 E-RAB
abnormal release to initial establishment attempt of QCI1 E-RAB.
NOTE: if multiple ERAB setup Reques/Initial Context Setup requests for the same UE are received while the eNB is
still processing the first one they are not excluded in the proposed formula.
Also if a X2/RLF HO happens before Initial Context Setup Response/Erab Setup response is sent to the MME i.e
during ciphering / security procedure the ATT counter would be pegged on the new eNB so two attempts for the
same connection while one response is perceived –
exclusion can be done with alternative formula
39
© 2020 Nokia
Confidential
MCDR_VoLTE_SYV(%) 1/8
Nokia formula
Formula: [4G MCDR_VoLTE_SYV(%)] ={100}*(ERAB_INI_SETUP_SUCC_QCI1 + ERAB_ADD_SETUP_SUCC_QCI1 ERAB_REL_TEMP_QCI1 - ERAB_REL_ENB_ACT_QCI1)/(ERAB_INI_SETUP_ATT_QCI1 + ERAB_ADD_SETUP_ATT_QCI1)
Alternative Formula
((ERAB_INI_SETUP_SUCC_QCI1) +(ERAB_ADD_SETUP_SUCC_QCI1) -(ERAB_REL_TEMP_QCI1)ERAB_REL_ENB_ACT_QCI1)/(((ERAB_INI_SETUP_ATT_QCI1) +nvl(erab_add_setup_att_qci1_ex_rtr,0) nvl(ERAB_ADD_SETUP_ATT_QCI1_HO,0)))
ERAB_REL_TEMP_QCI1:This counter will be incremented on transmission of an S1AP: E-RAB RELEASE INDICATION
message (eNB -> MME; 3GPP TS 36.413) due to an overbooking timer expiry for a temporarily admitted QCI1
bearer.
FL19: erab_add_setup_att_qci1_ex_rtr: This counter provides the number of setup attempts from MME for
additional E-RABs of QCI1, but excludes any retries from the MME for the same UE while eNB handling for the
original MME request was still on-going.
40
© 2020 Nokia
Confidential
VoLTE Abnormal Release Rate 2/8
Huawei formula
Formula: [VOLTE Abnormal Release rate] =( [L.E-RAB.Rel.S1Reset.eNodeB.QCI.1] + [L.ERAB.AbnormRel.eNBTot.QCI.1] + [L.E-RAB.AbnormRel.HOOut.QCI.1] )/ [L.E-RAB.SuccEst.QCI.1] *{100}
Description: This KPI provides the ratio of QCI1 E-RAB Abnormal Releases to the total QCI1 E-RAB Releases.
41
© 2020 Nokia
Confidential
VoLTE Abnormal Release Rate 2/8
Nokia formula
Formula: [VOLTE Abnormal Release rate] = 100* (erab_rel_ho_part_qci1 + erab_rel_enb_qci1 erab_rel_enb_rnl_ina_qci1 - erab_rel_enb_rnl_red_qci1 - erab_rel_enb_rnl_preem_qci1 - erab_rel_temp_qci1 +
erab_rel_enb_ini_s1_g_r_qci1 + erab_rel_enb_ini_s1_p_r_qci1 + erab_rel_s1_outage_qci1) /
(erab_rel_enb_qci1 + erab_rel_ho_part_qci1 + epc_eps_bear_rel_req_n_qci1 + epc_eps_bear_rel_req_d_qci1 +
epc_eps_bear_rel_req_r_qci1 + epc_eps_bear_rel_req_o_qci1 + erab_rel_epc_path_switch_qci1 erab_rel_temp_qci1 + erab_rel_succ_ho_utran_qci1 + erab_rel_succ_ho_geran_qci1 +
erab_rel_enb_ini_s1_g_r_qci1 + erab_rel_mme_ini_s1_g_r_qci1 + erab_rel_enb_ini_s1_p_r_qci1 +
erab_rel_mme_ini_s1_p_r_qci1 + erab_rel_s1_outage_qci1)
Description: This KPI provides the ratio of QCI1 E-RAB Abnormal Releases to the total QCI1 E-RAB Releases.
NOTE:This KPI describes the ratio of abnormally released (dropped) QCI1 E-RABs from RAN point of view.
1. Each QCI1 bearer of the Bearer to be Released List IE is counted.
2. RAN point of view means that as abnormal E-RAB drops only those ones initiated by eNB are counted.
3. The KPI may provide slightly higher values compared to reality in case in the network environment there is an Ericsson
MME used when the ERAB_REL_HO_PART_QCI1 counter is erroneously pegged when E-RABs are not admitted with a
cause successful-handover, but in fact in the E-RABs to Release List IE of the S1AP:HANDOVER COMMAND message they
were accepted by the MME.  work around exist on E// MME
42
© 2020 Nokia
Confidential
VoLTE Setup Success Rate 3/8
Huawei formula
Formula: [VOLTE setup success rate] =( [L.E-RAB.SuccEst.QCI.1] + [L.E-RAB.SuccEst.QCI.5] )/( [L.E-RAB.AttEst.QCI.1]
+ [L.E-RAB.AttEst.QCI.5] )*{100}
Description: The KPI is the ratio of QCI1 and QCI5 E-RAB successfully established and QCI1 and QCI5 E-RAB
attempts.
43
© 2020 Nokia
Confidential
VoLTE Setup Success Rate 3/8
Nokia formula
Formula: [VOLTE setup success rate] =((erab_ini_setup_succ_qci5 + erab_add_setup_succ_qci5) +
(ERAB_INI_SETUP_SUCC_QCI1) +(ERAB_ADD_SETUP_SUCC_QCI1) -(ERAB_REL_TEMP_QCI1))/(
(erab_ini_setup_att_qci5 + erab_add_setup_att_qci5) + (ERAB_INI_SETUP_ATT_QCI1 +
ERAB_ADD_SETUP_ATT_QCI1))*100
Description: The KPI is the ratio of QCI1 and QCI5 E-RAB successfully established and QCI1 and QCI5 ERAB attempts.
erab_ini_setup_succ_qciX pegs at Initial Context Setup Request/ERAB Setup Request
ERAB_INI_SETUP_SUCC_QCIX pegs when eNB sends RESPONSE to MME
ERAB_REL_TEMP_QCI1 :This measurement provides the number of temporary QCI1 bearer release due
to an overbooking timer expiry. This counter will be incremented on transmission of an S1AP: E-RAB
RELEASE INDICATION message (eNB -> MME; 3GPP TS 36.413) due to an overbooking timer expiry for
a temporarily admitted QCI1 bearer.
44
© 2020 Nokia
Confidential
VoLTE MPD (min) 4/8
Huawei formula
Formula: [L.E-RAB.SessionTime.HighPrecision.PLMN.QCI1]/{600}/[L.E-RAB.AbnormRel.PLMN.QCI.1]
Description: KPI indicates the Minutes per drop for VoLTE
45
© 2020 Nokia
Confidential
VoLTE MPD (min) 4/8
Nokia formula
Formula: ((erab_in_session_time_qci1)/60 )/erab_rel_enb_act_qci1
Description: This KPI indicates the aggregated in-session activity time in minutes for all E-RABs with QCI1
characteristics divided by Active ERAB Drops
erab_rel_enb_act_qci1:released active E-RABs (that is when there was user data in the queue at the time
of release) with QCI1 characteristics. The release is initiated by the eNB due to radio connectivity
problems. The counters must be updated in case that user data are buffered (UL/DL) for an E-RAB with
QCI1 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME
46
© 2020 Nokia
Confidential
4G PS SSR_SYV(%) 5/8
Huawei formula
Formula: 4G PS SSR_SYV (%)= 100%*(L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att)*(L.E-RAB.InitSuccEst/
L.E-RAB.InitAttEst)
Description: It’s the combination of LTE RRC and ERAB setup success rate.
47
© 2020 Nokia
Confidential
4G PS SSR_SYV(%) 5/8
Nokia formula
Formula: 4G PS SSR_SYV (%)= 100%*{LUEST.sign_conn_estab_comp / (LUEST.sign_conn_estab_att_mo_s +
LUEST.sign_conn_estab_att_mt + LUEST.sign_conn_estab_att_mo_d + LUEST.sign_conn_estab_att_emg +
nvl(LUEST.sign_conn_estab_att_hiprio,0) + nvl(LUEST.sign_conn_estab_att_del_tol,0) +
nvl(LUEST.sign_conn_estab_att_mo_voice,0) + nvl(LUEST.sign_conn_estab_att_others,0))}
*{100*(ERAB_INI_SETUP_SUCC_QCI1 +
ERAB_INI_SETUP_SUCC_QCI2+ERAB_INI_SETUP_SUCC_QCI3+ERAB_INI_SETUP_SUCC_QCI4+ERAB_INI_SETUP_SUCC_QC
I5+ERAB_INI_SETUP_SUCC_QCI6+ERAB_INI_SETUP_SUCC_QCI7+ERAB_INI_SETUP_SUCC_QCI8+ERAB_INI_SETUP_SUCC_
QCI9)
/(ERAB_INI_SETUP_ATT_QCI1+ERAB_INI_SETUP_ATT_QCI2+ERAB_INI_SETUP_ATT_QCI3+ERAB_INI_SETUP_ATT_QCI4+ER
AB_INI_SETUP_ATT_QCI5+ERAB_INI_SETUP_ATT_QCI6+ERAB_INI_SETUP_ATT_QCI7+ERAB_INI_SETUP_ATT_QCI8+ERAB_I
NI_SETUP_ATT_QCI9) }
Description: It’s the combination of LTE RRC and ERAB setup success rate.
NOTE: ERAB SR for H// is initial only but for Nokia is addition + initial can be found so to match we
have to use erab_ini_setup_succ_qciX/erab_ini_setup_att_qciX but this means that all other QCI that are
established as additional after the default bearer (which is only counted in initial counters) are missed
out most. In the Later Stage the alternative KPI can be used as it reflects more the real situation
Alternative for ERAB SR:{100*sum(eps_bearer_setup_completions) /sum(eps_bearer_setup_attempts) }
48
© 2020 Nokia
Confidential
4G PS DCR_SYV (%) 6/8
Huawei formula
Formula: 4G PS DCR_SYV (%) = 100%*(L.E-RAB.AbnormRel)/(L.E-RAB.NormRel+ L.E-RAB.AbnormRel)
Description: This KPI provides the ratio of E-RAB abnormal Releases to the total E-RAB Releases
(Normal Release + Abnormal Release) and is used to check the retainability KPI
49
© 2020 Nokia
Confidential
4G PS DCR_SYV (%) 6/8
Nokia formula
Formula: 4G PS DCR_SYV (%) = 100* (erab_rel_enb_act_qci1 + erab_rel_enb_act_qci2 +
erab_rel_enb_act_qci3 + erab_rel_enb_act_qci4 + erab_rel_enb_act_non_gbr) /
(erab_rel_enb + erab_rel_ho_part + epc_eps_bearer_rel_req_norm + epc_eps_bearer_rel_req_detach +
epc_eps_bearer_rel_req_rnl + epc_eps_bearer_rel_req_oth +
erab_rel_epc_path_switch - erab_rel_temp_qci1 + erab_rel_succ_ho_utran + erab_rel_succ_ho_geran +
erab_rel_enb_ini_s1_glob_reset + erab_rel_mme_ini_s1_glob_reset +
erab_rel_enb_ini_s1_part_reset + erab_rel_mme_ini_s1_part_reset + erab_rel_s1_outage)
Description: This KPI describes the ratio of a specific E-RAB drop (abnormal release) cause related to all
E-RAB releases. Cause: E-RAB active drop ratio with data in the buffer due to RNL Radio Connection
with UE Lost cause initiated by eNB.
50
© 2020 Nokia
Confidential
4G data speed _SYV (kbps) 7/8
Huawei formula
Formula: 4G data speed_SYV (kbps)= (L.Thrp.bits.DL - L.Thrp.bits.DL.LastTTI)/
L.Thrp.Time.DL.RmvLastTTI
Description : L.Thrp.bits.DL QCI.x : Downlink traffic volume for PDCP SDUs of services with the QCI of x
in a cell. [x is the integrity from 1 to 9]
L.Thrp.Time.DL. QCI.x: Transmit duration of downlink PDCP SDUs for services with the
QCI of x in a cell [x is the integrity from 1 to 9]
L.Thrp.bits.DL.LastTTI : Downlink traffic volume sent in the last TTI for PDCP SDUs
before the buffer is empty
L.Thrp.Time.DL.RmvLastTTI : Data transmit duration except the last TTI before the
downlink buffer is empty
51
© 2020 Nokia
Confidential
4G data speed _SYV (kbps) 7/8
Nokia formula
Formula: 4G data speed_SYV (kbps)= IP_TPUT_DATA_VOL_DL_PROFILE
(M8047C0)/IP_TPUT_TIME_DL_WO_MAC_DEL_PR (M8047C23)
IP_TPUT_TIME_DL_WO_MAC_DEL_PR (M8047C23):This counter provides IP throughput time excluding the
MAC retention delay (HARQ retransmissions) per the respective PMQAP Profile in Downlink.This counter is
updated when the time to transmit a data burst excluding the last piece of data transmitted in the TTI when the
buffer is emptied and the delay introduced by any HARQ retransmissions in Downlink for the ERABs configured
in the Profile.
IP_TPUT_DATA_VOL_DL_PROFILE (M8047C0):This measurement provides IP throughput data volume per the
respective PMQAP Profile in DL as experienced by the Ue as per3GPP TS 36.314 Chapter 4.1.6.1. The volume of
a data burst excluding the data transmitted in the TTI when the buffer is emptied. A sample for ThpVolDl is the
data volume, counted on PDCP SDU level in bits, successfully transmitted (acknowledged by the UE) in DL for
the respective PMQAP Profile during a sample of ThpTimeDl. It must exclude the volume of the last piece of
data emptying the buffer.
Note: PMQAP has to be configured by all QCI 1
9
Throughput Time is up to point “A”
52
© 2020 Nokia
Confidential
4G Availability_SYV(%) 8/8
Huawei formula
Formula: 4G Availability_SYV (%) =100%*(1-L.Cell.Unavail.Dur.Sys/({GP}*{60}))
Description : L.Cell.Unavail.Dur.Sys : Duration of cell unavailability due to system faults.
Measurement Points :
The cell status is sampled per five seconds. If a cell is unavailable, the corresponding counter is
incremented by 5s at that sampling point. At the end of a measurement period, the accumulated
counter value is reported.
GP: measurement period (minute)
53
© 2020 Nokia
Confidential
4G Availability_SYV(%) 8/8
Nokia formula
Formula: 4G Availability_SYV (%) =100* (samples_cell_avail) / (denom_cell_avail samples_cell_plan_unavail))
Description : This KPI shows Cell Availability, excluding blocked by user state (BLU) that gives the
percent of available time over time that should be available.
Measurement Points :
samples_cell_avail :This counter is incremented by 1 approximately every second when the Operational
State of the cell is enabled.
samples_cell_plan_unavail :This counter is incremented by 1 approximately every second when cell state
changes to either "Administrative State is locked", "Energy State is energySaving", and "Local State is
blocked".
GP: measurement period (# of seconds)
54
© 2020 Nokia
Confidential
Nokia proposed 5G KPI formulas
55
© 2020 Nokia
Confidential
5G Availability (%)
5G KPI Proposal
NR_5150A = (100 * (samples_cell_avail) / (denom_cell_avail))
Description: This KPI shows the ratio of time in which services in a cell are available for end
users.
Recommended NOKIA Value = 99.5
Expected Value = 99.5
56
© 2020 Nokia
Confidential
5G Accessibility (%)
5G KPI Proposal
NR_5020c = (x2_sgnb_reconf_ack_received)/(x2_sgnb_add_req_ack_sent + x2_sgnb_add_req_rej_sent)
Description:This KPI shows the Non Stand Alone call accessiblity on 5G prespective. The formula
monitors the call setup procedure until the SGNB RECONFIGURATION COMPLETE is received by SgNB
fromLTE eNB (with Configuration successfully applied IE) for initial NSA call setup . The remaining steps
on NSA call setup are on LTE side an are not monitored by this formula.
OFFICIAL NOTES: The formula does not include the SgNB addition and reconfiguration procedures in
case of Inter-gNB HO.
Recommended NOKIA Value = 99
Expected Value = 98.5
57
© 2020 Nokia
Confidential
5G PS Drop Rate (%)
5G KPI Proposal
100 - NR_5030a =100 - (100*(sgnb_release_req_ue_inact)/(x2_sgnb_rel_required_sent+
x2_uerel_outgoing_reset+ x2_uerel_out_partial_reset))
Description : This KPI shows the NSA call retainability for SgNB initiated releases. The normal releases
are considered those initiated due to user inactivity, while the total number of releases are the SgNB
initiated releases and the releases caused X2 Reset. Releases initiated by the LTE MeNB are not
considered in this KPI.
sgnb_release_req_ue_inact : Number of SGNB RELEASE REQUIRED messages sent to LTE eNB with
cause equal to User inactivity
Recommended NOKIA Value = 0.5%
Expected Value = value is much higher due lack of continuous coverage and rouge UE
58
© 2020 Nokia
Confidential
5G Throughput (%)
5G KPI Proposal
NR_5100a = (8 *(pdsch_ini_vol_64tbl_mcs00 + pdsch_ini_vol_64tbl_mcs01 + .. +
pdsch_ini_vol_64tbl_mcs25 + pdsch_ini_vol_64tbl_mcs26 + pdsch_ini_vol_64tbl_mcs27 +
pdsch_ini_vol_64tbl_mcs28
+ pdsch_ini_vol_256tbl_mcs00 + pdsch_ini_vol_256tbl_mcs01 + .. + pdsch_ini_vol_256tbl_mcs25 +
pdsch_ini_vol_256tbl_mcs26 + pdsch_ini_vol_256tbl_mcs27)/1000000
/((acc_ue_dl_drb_data) * 20 * (SUM(data_slot_pdsch_time / 1000000) / SUM(data_slot_pdsch))))
Due acc_ue_dl_drb_data counter pegging characteristics (includes C-DRX sleep time) see details
under https://www.yammer.com/nokia.com/#/threads/show?threadId=970343772979200
is
Description:
This KPI shows the average MAC layer user throughput in downlink. It ,isit calculated
as Cell
advisable
to use nrcell
level throughput
throughput
divided
by number
of users.KPI (symbol time based)
Cell user throughput = Volume in Mbits / (Accumulated number of users with buffered data (sampled
every 20 slots) * 20 slots * Slot duration)
((acc_ue_dl_drb_data) * 20 * ( (data_slot_pdsch_time / 1000000) / (data_slot_pdsch))) 
( ([Accumulated number of UEs with DL DRB data buffered]) * 20 * ( ([Data slot with PDSCH - Time] / 1000000) / ([Data slot
with PDSCH]))))
Recommended NOKIA Value = TBD
Expected Value = 150Mbps
59
© 2020 Nokia
Confidential
Nokia 5G PS
5G Setup Flow Chart
60
© 2020 Nokia
Confidential
Nokia 5G VOICE KPIs
5G KPI Proposal
Voice KPIs to be agreed when available in the devices.
61
© 2020 Nokia
Confidential
Annex
62
© 2020 Nokia
Confidential
KPI Mapping worksheet
SyVKPIMapping
v1.7.xlsx
63
© 2020 Nokia
Backup
64
© 2020 Nokia
Confidential
Network Quality Service Level KPIs for Sites within Swap Cluster
65
© 2020 Nokia
Confidential
Network Quality Service Level KPIs for CCA, CFA and NW Acceptance
66
© 2020 Nokia
Confidential
Network Quality Service Level KPIs for Managed Services
67
© 2020 Nokia
Confidential
Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia. This document is
provided subject to confidentiality obligations of
the applicable agreement(s).
This document is intended for use of Nokia’s
customers and collaborators only for the purpose
for which this document is submitted by Nokia. No
part of this document may be reproduced or made
available to the public or to any third party in any
form or means without the prior written permission
of Nokia. This document is to be used by properly
trained professional personnel. Any use of the
contents in this document is limited strictly to the
use(s) specifically created in the applicable
agreement(s) under which the document is
submitted. The user of this document may
voluntarily provide suggestions, comments or other
feedback to Nokia in respect of the contents of this
document ("Feedback").
69
© 2020 Nokia
Such Feedback may be used in Nokia products and
related specifications or other documentation.
Accordingly, if the user of this document gives
Nokia Feedback on the contents of this document,
Nokia may freely use, disclose, reproduce, license,
distribute and otherwise commercialize the
feedback in any Nokia product, technology, service,
specification or other documentation.
are made in relation to the accuracy, reliability or
contents of this document. NOKIA SHALL NOT BE
RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT or for any loss of data or income or
any special, incidental, consequential, indirect or
direct damages howsoever caused, that might arise
from the use of this document or any contents of
this document.
Nokia operates a policy of ongoing development.
Nokia reserves the right to make changes and
improvements to any of the products and/or
services described in this document or withdraw
this document at any time without prior notice.
This document and the product(s) it describes
are protected by copyright according to the
applicable laws.
The contents of this document are provided "as is".
Except as required by applicable law, no warranties
of any kind, either express or implied, including, but
not limited to, the implied warranties of
merchantability and fitness for a particular purpose,
Confidential
Nokia is a registered trademark of Nokia
Corporation. Other product and company names
mentioned herein may be trademarks or trade
names of their respective owners.