SDCCH Blocking Rate (=SDCCH Congestion Rate) ------------------------------------------------SDCCH blocking rate or SDCCH congestion rate is defined as the rate

of SDCCH all ocation failure in the BSS. SDCCH blocking rate = 100 * (numSdcchAllocFailCount) / TotalSdcchAllocAttempt) where, numSdcchAllocFailCount = Number of SDCCH allocation failures at BSC. This counte r gives the count for SDCCH radio resource allocation failed. This counter is in cremented every time the SDCCH resource allocation request is rejected due to co ngestion. This counter does not get incremented incase admission control rejects the channel request (rejection could be due to insufficient BSC resources, call context, or unsupported establishment cause). TotalSdcchAllocAttempt = Total number of SDCCH allocation attempts. This counter gives the count for SDCCH Radio Resource allocation Attempts. This counter is i ncremented every time the SDCCH resource allocation request is attempted. This c ounter does not get incremented incase admission control rejects the channel req uest (rejection could be due to insufficient BSC resources, call context, or uns upported establishment cause). This KPI is defined in terms of percentage (%). Example: Assume, TotalSdcchAllocAttempt = 95000 whereas numSdcchAllocFailCount = 590 then SDCCH blocking rate = 100 * (590/95000) = 0.62 % Applicable Objects: This KPI is provided on per cell basis. The information can be used to calculate the KPI at BSS level as well. Special Considerations: All valid RACH requests (may include ghost/phantom RACH requests) gets considere d in this KPI. Request for SDCCH handovers are not considered in this KPI. All RACH (channel required messages) that are discarded due to overload situatio ns are not included in TotalSdcchAllocAttempt counter. TotalSdcchAllocAttempt implies the total SDCCH attempts that have been made. Thi s does not include the cases where admission control has failed because of any o ther system resource. Similarly, numSdcchAllocFailCount also, does not include s uch SDCCH Drop Rate/SDCCH Completion Rate --------------------------------------------SDCCH drop rate is defined as the rate of such calls where SDCCH procedures are not completed successfully. Referring to the sequence chart provided in Figure 1, this KPI maps to establish SDCCH connection and SDCCH procedures phase. Formulae: SDCCH Completion Rate SDCCH completion rate = 100 - SDCCH drop rate SDCCH Drop Rate SDCCH drop rate = 100 * [numSdcchRlto + numSdcchEstbdErrorInd + numEstbdOperator Action + numEstbdLapdLinkDown + numEstbdAifLinkDown + numEstbdUnexpectedSdcchRel Ind + + numtrxfailuresduringestablishedphase / (TotalSdcchAllocSuccessCount)] where, numSdcchRlto = Radio link time out on SDCCH. This is unlikely to happen as SDCCH is allocated for small duration. This counter is incremented when RLTO is detec ted for SDCCH radio resource. This could happen when SDCCH is in established or releasing phase. numSdcchEstbdErrorInd = ERROR_IND from BTS. Error indication received on SDCCH i n established phase. This counter in incremented when error indication is receiv

ed from TRX and SDCCH is in established phase. numEstbdOperatorAction = O and M action. This counter is incremented every time when SDCCH is released in established phase because of operation action. Followi ng actions are in SDCCH established phase: o TRX lock o Cell lock BSS lock o Abis E1 lock o A E1 lock numEstbdLapdLinkDown = LAPD link down connection in SDCCH established phase. Thi s counter in incremented when SDCCH in established phase is released because of LAPD link down is received. numEstbdAifLinkDown = AIF link down in SDCCH established phase. This counter is incremented when SDCCH in established phase is released because of AIF link down is received. numEstbdUnexpectedSdcchRelInd = Unexpected REL_IND from BTS (for example, mobile station (M)S switched-off scenario). This counter is incremented when SDCCH is in established phase and release indication is received from TRX. This causes SD CCH releasing unexpected release indication in case when BSC doesnt expect that r elease indication should come from TRX. In case of release procedure, when BSC h as send RF release in that case release indication received from TRX is consider ed as expected. TotalSdcchAllocSuccessCount = Total number of successful SDCCH allocation. This counter is incremented every time when SDCCH radio resource is successfully allo cated and entered in established phase. This KPI is defined in terms of percentage (%). The following are the possible reasons of unsuccessful completion of SDCCH call: Radio link time out ERROT_IND from BTS LAPD link down O&M action like TRX lock o Cell lock o BSS lock o Abis E1 lock o A E1 lock A-IF link down Unexpected REL_IND from BTS (for example, MS switch-off scenario) Example: Assume, TotalSdcchAllocSuccessCount = 95000 whereas <summation of all failure reasons> = 1000 then SDCCH drop rate = 100 * (1000/95000) = 1.05 % SDCCH completion rate = 100 - 1.05 = 98.95 % Applicable Objects: This KPI is provided on per cell basis. You can use this information to calculate the KPI at BSS level as well. Special Considerations: All valid RACH requests (may include ghost/phantom RACH requests) gets considere d in this KPI. Handover on SDCCH is not supported so incoming HO SDCCH call is not considered. TCH Blocking Rate (= TCH Congestion Rate) ---------------------------------------------TCH blocking rate or TCH congestion rate is defined as the rate of TCH allocatio n failure in BSS. Referring to the sequence chart provided in above figure, this KPI maps to get T CH phase. Formulae:

TCH Blocking Rate TCH blocking Rate = 100 * (numTchAllocFailCount)/ (TotalNormalCallTchAllocAttemp t) where, numTchAllocFailCount = Number of TCH allocation failures at BSC. This counter gi ves the count for TCH (HR/FR/EFR) radio resource allocation failed. This counter is incremented every time the TCH resource allocation request is rejected due t o congestion or any other reason (such as requested codec not supported). This c ounter does not get incremented in case admission control reject the assignment request (rejection could be due to insufficient BSC resources, call context, CIC is blocked etc). TotalNormalCallTchAllocAttempt = Total number of normal TCH allocation attempts. This counter gives the count for TCH (HR/FR/EFR) radio resource allocation atte mpt. This counter is incremented every time the TCH resource allocation request is attempted. This counter does not get incremented incase admission control rej ect the assignment request (rejection could be due to insufficient BSC resources , call context, or CIC is blocked etc). This KPI is defined in terms of percentage (%). Example: Assume, TotalNormalCallTchAllocAttempt = 95000 whereas numTchAllocFailCount = 490 then TCH blocking rate = 100 * (490/95000) = 0.51 % Applicable Objects: This KPI is provided on per cell basis. You can use this information to calculate the KPI at BSS level as well. Special Considerations: Handovers are not counted in this KPI. TotalNormalCallTchAllocAttempt implies the total TCH attempts that have been mad e, this does not include the cases where admission control has failed because of any other system resource. Similarly, numTchAllocFailCount also does not includ e such cases. TCH assignment failures sent because of CIC blocked/busy/unequipped/no-CIC-prese nt are not to be counted for both numTchAllocFailCount and TotalNormalCallTchAll ocAttempt counters. TCH Drop Rate/TCH Completion Rate ------------------------------------Referring to the sequence chart provided in above figure, this KPI maps after TC H connection and during call phase. Please refer OMC Performance Monitoring Guide LAC/Cell Level KPI to view the report for this KPI. Note: get TCH phase is excluded. Formulae: TCH Drop Rate TCH drop rate = 100 * [numTchRlto + numTchEstbdErrorInd + numEstbdOperatorAction + numEstbdLapdLinkDown + numEstbdAifLinkDown + numEstbdUnexpectedTchRelInd + nu mEstbdConnFailInd)/ TotalTchAssgncmplReceived + TotalTchHoCmplReceived] where, numTchRlto = Radio link time out on TCH. This counter is incremented when RLTO i s detected for TCH radio resource. This could happen when TCH is in established phase. Radio link time out occurs in MS lost condition. numTchEstbdErrorInd = ERROR_IND from BTS. Error indication received on TCH in es tablished phase. This counter is incremented when error indication is received f rom TRX and TCH is in established phase. numEstbdOperatorAction = O and M action like o TRX lock o Cell lock o BSS lock o Abis E1 lock o A E1 lock

 numEstbdLapdLinkDown = LAPD link down connection in established phase. This coun ter is incremented when TCH in established phase is released because LAPD link d own is received. numEstbdAifLinkDown = AIF link down in TCH established phase. This counter in in cremented when TCH in established phase is released because of AIF link down is received. numEstbdUnexpectedTchRelInd = Unexpected REL_IND from BTS (say MS switch-off sce nario). This counter is incremented when TCH is in established phase is received from TRX and this causes TCH releasing unexpected release indication is case wh en BSC doesnt expect that release indication should come from TRX. In case of rel ease procedure when BSC has send RF release in that case, release indication rcv d from TRX is considered as expected. numConnFailInd = Connection failure indication received from BTS after TCH estab lishment indication. This counter is incremented each time connection failure in dication is received from TRX and TCH resource releasing is started. This messag e is received only in TCH established phase. TotalTchAssgncmplReceived = TCH assign complete received from MS. This counter i s incremented every time assign complete is received from MS. TotalTchHoCmplReceived = This counter is incremented every time TCH handover com plete received from MS. TCH Completion Rate TCH completion rate = 100 - TCH Drop Rate This KPI is defined in terms of percentage (%). The following are the possible reasons of unsuccessful completion of TCH call: Radio link time out ERROR_IND from BTS CONNECTION_FAILURE_INDICATION from BTS LAPD link down O&M action like o TRX lock o Cell lock o BSS lock o Abis E1 lock o A E1 lock AIF link down Unexpected REL_IND from BTS (say MS switch-off scenario) Example: Assume, TotalTchAssgncmplReceived + TotalTchHoCmplReceived = 95000, whereas <summation o f all failure reasons> = 1000 then TCH drop rate = 100 * (1000/95000) = 1.05 % TCH Completion Rate = 100 - 1.05 = 98.95 % Applicable Objects: This KPI is provided on per cell basis. You can use this information to calculate the KPI at BSS level as well. Special Considerations: Inter-BSC as well as intra-BSC handover is considered. Call Setup Success Rate/Call Setup Failure Rate ---------------------------------------------Call setup success rate is defined as the rate of such calls where SDCCH procedu res are successfully completed and TCH is allocated as well. Please refer OMC Per formance Monitoring Guide - LAC/Cell Level KPI to view the report for this KPI. Referring to the sequence chart provided in above figure, this KPI maps to get S DCCH, establish SDCCH connection, SDCCH procedures, and get TCH phases. Note: Establish TCH connection and call phase are not considered in this KPI. Formulae: Call Setup Success Rate Call setup success rate = 100 * [SDCCH assignment success rate * SDCCH completio

n rate * TCH assignment success rate / 1000000] Call Setup Failure Rate Call setup failure rate = 100 - Call setup success rate This KPI is defined in terms of percentage (%). Example: Assume, SDCCH assignment rate = 98%, SDCCH completion rate = 99 %, and TCH assignment ra te = 97% then Call setup success rate = 100 * (98 * 99 * 97/ 1000000) = 94.1 % Applicable Objects: This KPI is provided on per cell basis. The information can be used to calculate the KPI at BSS level as well. Special Considerations: Handover calls are not considered in this definition as SDCCH channel does not g et allocated for such calls. Incoming Inter-BSC Handover Failure Rate -----------------------------------------Incoming inter-BSC Handover failure rate is defined as the rate of failed interBSC incoming handover calls. This KPI is not applicable for intra-BSC handover c alls. This KPI can be derived from existing handover performance counter tables and th us no detailed formula is provided. OMC needs to consider those handover failure counters where target cell is contr olled by VNL BSS whereas serving cell is not controlled by VNL BSS from the said t able. Formula: Incoming HO Failure Rate = 100 * TotalFailedIncInterBscHo/ TotalIncomingInterBsc HoAttempt where, TotalFailedIncInterBscHo = Total number incoming inter-BSC handover failures. Fa ilure of Inter BSC handover counter gets incremented every time incoming inter B SC handover procedure is not successful in target VNL BSS. This counter does not include the case when handover request is rejected because of admission control for example CIC is blocked in target VNL BSS. TotalIncomingInterBscHoAttempt = Total number of incoming inter-BSC handover att empts. Total Incoming inter BSC handover attempt at target VNL BSS. This counter is incremented every time an inter BSC incoming handover is attempted. This coun ter does not include the case when handover request is rejected because of admis sion control for example CIC is blocked in target VNL BSS. Example: TotalFailedIncInterBscHo = 100 TotalIncomingInterBscHoAttempt = 1000 Incoming HO Failure Rate = 100 * 100 / 1000 = 10% Applicable Objects: This KPI is provided on per cell basis. The information can be used to calculate the KPI at BSS level as well. Please refer OMC Performance Monitoring Guide Handover Distribution KPI to view th e report for this KPI. Handover Distribution --------------------------------------Successful as well as failure handover are distributed across following handover reasons: UlRxQual = Uplink Rx Quality DlRxQual = Downlink Rx Quality UlRxLevel = Uplink Rx level DlRxLevel = Downlink Rx Level PowerBudget

These distribution should be calculated for inter- as well as intra-BSC handover . Formula: HO distribution [UlRxQual] success rate = 100 * (TotalSuccHoUlRxQual + TotalFail HoUiRXQual) / TotalIncomingHoAttempt where, TotalSuccHoUlRxQual: Total no of successful handover trigger due to uplink Rx qu ality reason. TotalFailHoUiRXQual: Total no of failure handover trigger due to uplink Rx quali ty reason. TotalIncomingHoAttempt: Total incoming handover attempt. This counter is increme nted every time a handover is attempted in BSS including incoming Intra BSS and incoming inter BSS handover. The above formula can be followed for success/fail; any handover reason; inter-/ intra- BSC handover. Please refer OMC Performance Monitoring Guide - Handover Distribution KPI to view the report for this KPI. RxQual UL/RxQual DL ---------------------------You can define this as the percent of measurements results received by BSC with a given level of quality (q0 to q7) for a particular TRX. This means that for ea ch level of quality from q0 to q7, how many of the measurement reports received are for that particular level in the TRX. The measurements are applicable from t he period of TCH established phase only. Formula: RxQual (5) = 100* sum(freq_dl_qual0 + ... + freq_dl_qual5)/ sum(freq_dl_qual0 + ... + freq_dl_qual7) where, freq_dl_qual0 = Total number of measurement reports received for quality level 0 for a particular TRX. Applicable Objects: This KPI is applicable on per TCH basis You can use this information to calculate the KPI on TRX, cell, and BSS basis al so. Please refer OMC Performance Monitoring Guide Rxqual Calculation KPI to view t he report generated for this KPI. 3.9 Actual Erlang/Traffic Calculation --------------------------------------------Actual Erlang calculation provides the total usage of a given traffic channel. This calculation includes establish TCH connection, call phase, and call release phases. In case of handover, rather than using call release phase, successful h andover is considered. Formulae: Usage of a traffic channel (in seconds) from per call basis is calculated as per the formula given below: Actual traffic in given duration (seconds) = summation of all call durations on all TCHs of given TRX during the specified time Hourly Erlang traffic (HET) is calculated as: HET = Actual traffic in given duration (seconds)/ 3600 This formula can be extended for cell as well as for BSS. Note: Total number of TCH parameter varies as per the chosen object. Applicable Objects: This KPI is applicable on per TRX basis. You can also use this information to calculate the KPI on cell and BSS basis Example: a. TRX Erlang calculation (BCCH TRX with SDCCH/4) Total TCH = 7, Total duration = 3600 seconds. Total traffic = 25200 seconds i.e. 25200/3600 = 7E. Note: This is an ideal case calculation. b. TRX Erlang calculation (BCCH TRX with SDCCH/4).

Total TCH = 7, Total duration = 3600 seconds Total traffic = 8000 seconds i.e. 8000/3600 = 2.22E. c. Cell Erlang calculation (2-TRX cell with SDCCH/4) Total TCH = 15, Total duration = 3600 seconds Total traffic = 8000 seconds i.e. 8000/3600 = 2.22E. Note: In (b) and (c) examples, same values are used but with different configurat ion. Even though Erlang calculation has turned-out to be same, still first calcu lation is with one TRX whereas, other calculation is with 2-TRX. This signifies that cell loading is less in case of (c) when compared with (b). Special Considerations: Actual Erlang calculation is different from Erlang capacity of a given node. Thi s KPI focuses on actual Erlang calculation only. The Erlang capacity can be calc ulated from Erlang B formula. Incomplete CERs calculation has to be used only for Erlang calculation; there is no impact on any other counter. Please refer OMC Performance Monitoring Guide- Erlang Calculation KPI to view the report for this KPI.