Revised KPIs for Managed Services

1 2 Network Wide KPIs Radio Network Utilization (during BBH) Switch BHCA (during Switch NBH) Network Wide KPIs (during NBH) % SDCCH Blocking % TCH Assignment Success Rate % TCH Blocking (User Perceived) % SDCCH Time Congestion % TCH Time Congestion Random Access Success Rate Paging Success Rate Location Update Success Rate Successful Call Rate (during 24 hrs) Network Wide KPIs (during NBH) SDCCH Drop TCH Drop Handover Success Rate Network Wide KPIs (during NBH) Voice Quality (MOS) in all Cells during NBH Capacity Target 70% 80% Accessability Target 0.5% 97% 1% 0.3% 1.4% 98% 92% 97% 99% Retainability Target 1.2% 2% 97% Voice Quality Target 3.8 Availability Target 99% 99.97% 99.99% LCL >=50% >=75% UCL <=90% <=85% Max Penalty Limit >=100% >=90%

3 4 5 6 7 8 9 10 11

LCL <=0.4% <=96% <=0.8% <=0.25% <=1.1% <=97.5% <=90% <=96% <=98.5%

UCL >=0.6% >=98% >=1.2% >=0.35% >=1.7% >=98.5% >=94% >=98% >=99.5%

Max Penalty Limit >=1% <=95% >=2% >=0.5% >=2.8% <=95% <=88% <=92% <=95%

12 13 14

LCL <=1.1% <=1.8% <=95%

UCL >=1.3% >=2.2% >=99%

Max Penalty Limit >=2% >=3% <=90%

15

LCL <=3.7

UCL >=3.9

Max Penalty Limit <=3.2

Network Wide KPIs (during 24 hours) 16 Availability and accuracy of data for KPIs 17 Network Availability (Radio) 18 Network Availability (Switch/IN/GPRS)

LCL <=98.5% <=99.95% <=99.985%

UCL >=99.5% >=99.99% >=99.995%

Max Penalty Limit <=95% <=99.5% <=99.5%

1 2 3 4 5

GPRS/EDGE KPIs (during 24 hours) Round Trip Time Attach Success rate excluding Unregistered subs PDP context activation success rate (Only NW cause codes) Gb Utilization % blocking of data channels on air interface GPRS KPIs (during 24 hours) Average UL throughput per TBF Average DL throughput per TBF EDGE KPIs (during 24 hours) Average UL throughput per TBF Average DL throughput per TBF

Data Target 700 ms 99.00% 99.00% 70% 2% Target 20 kbps 30 kbps Target 30 kbps 45 kbps

LCL <=600 <=98.5% <=98.5% <=65% <=1% LCL <=15 <=25 LCL <=25 <=40

UCL >=800 >=99.5% >=99.5% >=75% >=3% UCL >=25 >=35 UCL >=35 >=50

Max Penalty Limit >=900 ms <=95% <=95% >=80% >=5% Max Penalty Limit <=10 kbps <=20 kbps Max Penalty Limit <=15 kbps <=30 kbps

1 2

1 2

Revised KPIs for Managed Services

Network Wide KPIs (during NBH) Cells having utilization >90% Capacity Target 10% Accessability Target Metros 95% / Circles 90% Metros 95% / Circles 90% Metros 95% / Circles 90% Metros 95% / Circles 90% Metros 95% / Circles 90% Metros 95% / Circles 90% Retainability Target Metros 95% / Circles 90% Metros 95% / Circles 90% Metros 95% / Circles 90% LCL >=9% UCL <=11% Max Penalty Limit <=15%

Cell Wise KPIs (during Cell Busy Hour) 2 3 4 5 6 7 SDCCH Blocking <=1% TCH Assignment Success Rate >=95% TCH Blocking <=3% % SDCCH Time Congestion <0.85% % TCH Time Congestion <3% Random Access Success Rate >95%

LCL 92.5%/87.5% 92.5%/87.5% 92.5%/87.5% 92.5%/87.5% 92.5%/87.5% 92.5%/87.5%

UCL 97.5%/92.5% 97.5%/92.5% 97.5%/92.5% 97.5%/92.5% 97.5%/92.5% 97.5%/92.5%

Max Penalty Limit 90%/85% 90%/85% 90%/85% 90%/85% 90%/85% 90%/85%

Cell Wise KPIs (during Cell Busy Hour) SDCCH Drop <=2.5% 8 TCH Drop <=3% 9 10 Handover Success Rate >95%

LCL 92.5%/87.5% 92.5%/87.5% 92.5%/87.5%

UCL 97.5%/92.5% 97.5%/92.5% 97.5%/92.5%

Max Penalty Limit SDCCH Drop >=5% TCH Drop >=5% HOSR <=90%

KPI Formulae with Nokia Measurement Period

KPI

Description SDCCH Congestion of Total Number Of SDCCH Seizure Attempts TCH assignment complete after EST_IND message

SDCCH Blocking %(blck_5a)

Daily during NBH*

% TCH Assignment Success Rate(csf_15)

Daily during NBH*

TCH Congestion of Total Number of TCH allocation attempts (excluding call setup after directed retry) and not including TCH HO congestion TCH Blocking User perceived (blck_8d)

Daily during NBH*

% SDCCH Time Congestion

% TCH Time Congestion

Random Access Success Rate

Paging Success Rate (pgn_4)

Location Update Success Rate(lsr_2)

Successful Call Rate (during 24 hrs)

Dropped SDCCH Connections of Total Number of SDCCH Connections SDCCH Drop Call Rate Daily during NBH*

TCH Drop Call Rate %, Area Level

Dropped TCH Connections of Total Number of Calls Terminated in the Cell or Subscriber Perceived Dropped Call on Area Level Daily during NBH*

Dropped TCH Connections of Total Number of Calls Terminated in the Cell or Subscriber Perceived Dropped Call on Cell Level

TCH Drop Call Rate, Cell Level

Daily during Cell BH*

Service of availability of the Radio Base Station Networks expressed as a percentage Network Availability** Quarterly

KPI

Description

Measurement Period

Successful Call Rate***

The ratio of any calls connect to switch and reach destinations with B-answer, B-busy, and Bno answer circumstances. Successful call indicates switching network performance and concerns in all calls connecting to MS

24 Hrs

Processor Load of each MSC, BSC and IN Nodes Processor Load 24 Hrs

Service availability of the IN system expressed as a percentage Availability of IN Nodes Quarterly

BBH will considered at cell level instead of NBH. MSC Outage will be considered as outage of all Cells served by that MSC; Similarly BSC Outage will be considered as outage of all Cells served by that BSC

**

KPI Formulae with Nokia

Formulae

Nokia Formulae

100 x (CCONGS / CCALLS); Ericsson

100 x (SDCCH_busy_att - tch_seiz_due_sdcch_con) / (SDCCH_seiz_att)

100 x sum(a.tch_new_call_assign) / b.served_dr_req + a.served_tch_call_req + a.served_facch_req)) = source , b = target

(sum( a

100 x ((CNRELCONG + TFNRELCONG) / TASSALL); Ericsson

sum(tch_call_req-tch_norm_seiz) - sum(msc_o_sdcch_tch+ bsc_o_sdcch_tch +cell_sdcch_tch) + sum(tch_succ_seiz_for_dir_acc) - sum(tch_rej_due_req_ch_a_if_crc -(bsc_i_unsucc_a_int_circ_type + msc_controlled_in_ho + ho_unsucc_a_int_circ_type)) 100 * ----------------------------------------------------------- % sum(tch_call_req) - sum(tch_rej_due_req_ch_a_if_crc -(bsc_i_unsucc_a_int_circ_type + msc_controlled_in_ho + ho_unsucc_a_int_circ_type))

Formula available only for SDCCH congestion time

100 x sum(tch_fr_radio_congestion_time / (sum(period_duration*ave_tch_busy_full/60)

RACH rejection ratio or RACH load

100 x sum over all BTS in LA (succ_tch_seiz + tch_mtc)/ sum over LA (paging_msg_sent)/ sum over LA(count of BTS)

100 x sum(nbr_of_calls) where counter_id = 26 /* LU completed */ sum(nbr_of_calls) where counter_id = 25 /* LU started */

100 x (CNDROP / CMESTAB) ; Ericsson

100 x sum (sdcch_radio_fail + sdcch_rf_old_ho ) / (sum (sdcch_assign + sdcch_ho_seiz) sum(sdcch_abis_fail_call + sdcch_abis_fail_old+ sdcch_user_act + sdcch_bcsu_reset + sdcch_netw_act + sdcch_bts_fail + sdcch_lapd_fail + sdcch_a_if_fail_call + sdcch_a_if_fail_old) )

100 x (TFNDROP / TFCASSALL);Ericsson

100 x (TFNDROP / TFCASSALL);Ericsson

p_nbsc_service, a = source, b = target Bharti suggestion ok, with the following comments: 100 * (Total days * 24 * 60 * Total Excludes force majeur No of Cells - Summation Excludes planned maintenance of Downtime of Cells) / (Total days Excludes non-Nokia faults (power, transmission etc) * 24 * 60 * Total No of Cells) Excludes major events (public holidays etc) where: Total days = Total no of If a BSC is unavailable, all sites under that BSC are days in the quarter, 1 day = 24 considered unavailable hours, 1 hour = 60 mins; Downtime If a MSC is unavailable, all sites under that MSC are = Total Cell outage in mins considered unavailable Formulae Formulae

Siemens Switch : {SPEECH_CALLS_WITH_ANSW ER(PLMN+notPLMN+Term) + CALLS_WITH_ANSWER + CALL_REL_A_ALERT(PLMN+Not PLMN) + CALL_REL_ALERT(Term+Trans) + CALL_TIOUT_ALERT(PLMN+Not PLMN) + = 1- ((INTERNAL_FAILURES)/TOTAL CALLS) UNS_MS_DETACH(Term) + UNS_MS_BLOCKED(Term) + UNS_MS_BUSY(PLMN+NotPLMN +Term) } / {CALL_ATTEMPTS (PLMN+NotPLMN+Term+Trans)} Ericsson Switch : (NBANS+NABEFA1+NABEFA2+N CAWNOA+ NTOBEFA+NBOUT+NBBUSY) / NCALLS

Peak Value during 24 hrs period

As the Nokia processor load is distributed, this could be an average over all processors. In case peak load in 24 hour period is needed, the exact meaning in a distributed processing system requires further clarification, that can be done in the nearest future.

100 * (Total days * No of IN Nodes * 24 * 60 Summation of IN Nodes Downtime) / (No of IN Nodes * Total Days * 24 * 60) where : Total days = Total no of days in the month;1 day = 24 hours, 1 hour = 60 mins; Downtime = Total outage in mins

Bharti suggestion is ok with the following comments: Excludes force majeur Excludes planned maintenance Excludes non-Nokia faults (power, transmission etc) Excludes major events (public holidays etc)

Comments

Counter drop after TCH assign in the numerator encapsulates drops due to various reasons such RF, Abiset Counter TCH new call assign in the denominator prevents the same call being counted twice because of incoming handovers on an area level

Use: On the BTS level. To rank cells by the share of TCH drop call failures per TCH seizure (normal or HO). Intra-cell HO is excluded, which is meaningful in the case of IUO. Inter-cell HOs are counted only as a net value.

Comments

-INTERNAL_FAILURES : Call is failed in MSC due to (MSC's) Internal problems, Clear Codes (400...7FF) (like problem with charging or SW failure). Clear Codes 400...7FF description attached for reference in ClearCodes sheet