56402563 Nokia KPI Formulas

NTC TANDocument

NOKIA NMS/2000FOR MANAGING CELLULAR NETWORKS

BSS NETWORK DOCTOR FORMULAS

TAN 0936/3 en

Reference Guide

0936/3 en1Copyright © Nokia Telecommunications Oy number/Issue

The information in this document is subject to change without notice and describes only the product definedin the introduction of this documentation. This document is intended for the use of NokiaTelecommunications' customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without the prior writtenpermission of Nokia Telecommunications. The document has been prepared to be used by professional andproperly trained personnel, and the customer assumes full responsibility when using it. NokiaTelecommunications welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance ofthe mentioned hardware or software products cannot be considered binding but shall be defined in theagreement made between Nokia Telecommunicat ions and the customer. However, NokiaTelecommunications has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia Telecommunications will, ifnecessary, explain issues which may not be covered by the document.

Nokia Telecommunications' liability for any errors in the document is limited to the documentary correction oferrors. Nokia Telecommunications WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according to theapplicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respective companies, andthey are mentioned for identification purposes only.

Copyright © Nokia Telecommunications Oy 2000. All rights reserved.

No. of Edited by Author Approved by Previous issuepages (2.4) approved

J Rissanen J Rissanen P Alatalo144/JRi 28 Feb 2000 28 Feb 2000 28 Feb 2000 18 Aug 1999

Copyright © Nokia Telecommunications Oy 2000. All rights reserved.

NTC TAN 0936/3 en2Document number/Issue Copyright © Nokia Telecommunications Oy

TABLE OF CONTENTS

7 . . 7 . . 7 . . 8 . . . 9

2 . . 12 . 14 . 18 . . 20 . 20. 24. 25. . 35. 43 . . 63 . 66 . 69. . 71. . 71. 74. 84102

. 105 . 106107

109110

. 113

. 113

. 114 . 114. 114 . 114

115116. 117

118. 118119. 121

Summary of changes 5

1 ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.1 What you need to know first . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.2 Where to find more . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.3 Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1.4 Terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 BSS COUNTER FORMULAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Random access (rach) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2 SDCCH drop failures (sd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3 SDCCH drop ratio (sdr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.4 Setup success ratio (cssr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.5 TCH drop failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6 Drop call failures (dcf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7 TCH drop call % (dcr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8 Handover (ho) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9 Handover failure % (hfr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10 Handover success % (hsr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.11 Handover failures (hof) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.12 Interference (itf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.13 Congestion (cngt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14 Queuing (que). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15 Blocking (blck). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.16 Traffic (trf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.17 Traffic directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.18 Paging (pgn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19 Short message service (sms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.20 Directed retry (dr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.21 Availability (ava) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.22 Unavailability (uav) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.23 Location updates (lu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.24 LU success % (lsr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.25 Emergency call (ec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.26 Emergency call success % (ecs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.27 Call re-establishment (re) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.28 Call re-establishment Success % (res) . . . . . . . . . . . . . . . . . . . . . . . . . .2.29 Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.30 Downlink and uplink level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.31 Power (pwr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.32 Level (lev) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.33 Distance (dis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.34 Link balance, power, level (lb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.35 Call success (csf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NTC TAN 0936/3 en3Copyright © Nokia Telecommunications OyDocument number/Issue

135

36136136136136

137

2.36 Configuration (cnf). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 MISSING COUNTERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 XX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2 XX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3 XX3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.4 XX4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NTC TAN 0936/3 en

4Copyright © Nokia Telecommunications OyDocument number/Issue

sions

ed,

Summary of changes

In this Functionality Note

As a result of the changes made between BSS Network Doctor software ver10.5. and 11.1 the following changes have been made into this document:

New formulas

• sd_1a, Ghosts detected on SDCCH and other failures

• dcr_3i, TCH drop call %, area, real, before re-establishment, S3

• dcr_3j, TCH drop call %, area, real, after re-establishment, S7

• dcr_4e, TCH drop-out %, BTS level, before call re-establishment, S7

• dcr_4f, TCH drop-out %, BTS level, before call re-establishment, S7

• dcr_15, TCH Rf loss - ratio, IUO

• blck_8d, TCH call blocking %, DR and DAC compensated, EFR excludS5

• blck_9c, Blocked calls , S5

• trf_14b, IUO, Average TCH seizure length on super TRXs, S4

• trf_15b, IUO, Average TCH seizure length on regular TRXs, S4

• trf_25a, SDCCH true seizures S7

• trf_36a, TCH normal seizure % out of TCH call requests

• trf_39a, TCH seizures for new calls

• trf_55, TCH normal seizures

• csf_2h, SDCCH success ratio, area

• csf_2i, SDCCH success ratio, BTS

• csf_3l, TCH access probability, real

• csf_4u, TCH success ratio, area, before call re-establishment, S7

• csf_4v, TCH success ratio, area, after call re-establishment, S7

• csf_4x, TCH success ratio, BTS, after call re-establishment

• csf_4y, TCH success ratio, BTS, before call re-establishment

Removed formulas

• trf_14a and trf_15a, replaced by trf_14b and trf_15b

NTC TAN 0936/3 en


sionsnt:

Corrections in formulas:

• dcr_10b, ho_6, trf_25

In the previous Functionality Note

As a result of the changes made between BSS Network Doctor software ver10.4.(x) and 10.5, the following changes have been made into this docume

New formulas

• dcr_3h, TCH drop call %, area, real, after re-establishment

• dcr_10b, Drops per erlang, after re-establishment

• hfr_3c and hfr_3d, Intra-cell HO failure share

• hfr_4c and hfr_4d, Incoming MSC ctrl HO failure share

• hfr_5c and hfr_5d, Outgoing MSC ctrl HO failure share

• hfr_6c and hfr_6d, Incoming BSC ctrl HO failure share

• hfr_7c and hfr_7d, Outgoing BSC ctrl HO failure share

• trf_17b, Average TRX TCH seizure length, IUO

• trf_47, Share of single band traffic

• trf_53, Calls started as FACCH call setup

• trf_54, SDCCH seizures

• dr_7, DR, outgoing to another cell, failed

• dr_8, DR, intra-cell failed

• re_2, Call re-establishments

• csf_4s, TCH success ratio, area, after call re-establishment

• csf_4t, TCH success ratio, BTS, after call re-establishment

Removed formulas

The following formulas have been removed:

• blck_9a, Blocked calls

NTC TAN 0936/3 en


About this manual

nce

portspost-

s not

torokiaf the

0.

used

ed toalsnts.

1 ABOUT THIS MANUAL

This document defines the formulas used to calculating the Key PerformaIndicators based on the Nokia NMS/2000 database.

This document contains also formulas which are not used in any actual reof the NMS/2000 post-processing tools. You can see the formulas used inprocessing from the actual reports of the tools.

Note:

This document serves as a reference to the available formulas and doeinclude information on whether the formula is in use or not.

The information contained in this document relates to BSS Network Docsoftware version 11.x, Nokia NMS release T11 and to release S7 of the NBSC software. This document should not be used with any other versions oNokia NMS/2000 or Nokia BSC software.

This document is intended for the network operators of the Nokia NMS/200

This chapter covers the following topics:

• What you need to know first

• Where to find more

• Typographic conventions

• Concepts and terminology

1.1 What you need to know first

This document assumes that you are familiar with the following areas:

• The concepts of the Nokia NMS and GSM networks in general

• A text processing utility, such as vi or dtpad. These text processors arefor editing certain configuration files.

1.2 Where to find more

When you perform the user’s tasks described in this document, you may nerefer to other documentation for further information. Below is a list of manuthat you will find useful, as well as a brief description of the manual’s conte

NTC TAN 0936/3 en


About this manual

thele.

forCH

helysis

used

BSS Network Doctor documentation

• BSS Network Doctor, Feature Overview, TAN 0932, for a brief overviewon the application

• BSS Network Doctor, System Administrator’s Guide, TAN 0934, forsystem administrator’s tasks related to running Network Doctor

• BSS Network Doctor, User’s Guide, TAN 0935, for a detailed descriptionon utilising the Network Doctor reports

Other Nokia documents

• Database Description for BSC Measurements, TAN 0422, for adescription of the structure of performance management (PM) tables inNMS/2000 database and the records, including counters, in each tab

• Call Related DX Causes in BSC, Functional Description, CAN 26095,an explanation of phases and for a list of causes in TCH and SDCobservations to find details for dropping calls.#1

• DX Cause Coding Mapping, CAG 61853, for an explanation to trelationship between DX cause codes and PM counters and for the anaof TCH and SDCCH observations.#2

1.3 Typographic conventions

The following tables present the typographic conventions which have beenin this manual to describe different actions and restrictions.

1.3.1 Text styles

The following table presents the typefaces and fonts and their indications.

Style Explanation

Initial Upper-caseLettering

Application names

Italiced text Emphasis

State, status or mode

Courier File and directory names

Names of database tables

Parameters

User names

System output

User input

UPPER-CASELETTERING

Keys on the keyboard (ALT, TAB, CTRL etc.)

NTC TAN 0936/3 en


About this manual

t.

Table 1.Text styles in this document

1.4 Terms and concepts

The lists below presents the terms and abbreviations used in this documen

1.4.1 Abbreviations

Bold text User interface components

Initial Upper-caseLettering in Italics

Referenced documents

Referenced sections and chapters within adocument

<bracketed text> Variable user input

Abbreviation Explanation

AG Access Grant

BCCH Broadcast Control Channel

BCF Base Control Function

BER Bit Error Ratio

BSC Base Station Controller

BSS Base Station Subsystem

BTS Base Transceiver Station

CI Cell Identity

DL Downlink

DR Directed Retry

FCS Frame Check Sequence

HO Handover

IUO Intelligent Underlay Overlay

KPI Key Performance Indicator

MML Man-machine Language

MOC Mobile Originated Call

MR Maintenance Region

MS Mobile Station

MSC Mobile Services Switching Centre

OMC Operation and Maintenance Centre

PI Performance Indicator

Style Explanation

NTC TAN 0936/3 en


About this manual

t.

Table 2.Abbreviations.

1.4.2 Terms

The lists below presents the abbreviations and terms used in this documen

PLMN Public Land Mobile Network

PM Performance Management

RACH Random Access Control Channel

SDCCH Stand Alone Dedicated ControlChannel

SMS Short Message Service

SQL Standard Query Language

SS Supplementary Service

TCH Traffic Channel

TR Trunk Reservation

TRX Transceiver

TSL Time Slot

UL Uplink

Term Explanation

AGCH A downlink control channel that is used tocarry a response to a mobile channelallocation request. The AGCH assigns themobile to operate on a specific TDMA timeslot.

Bit Error Ratio The ratio of the number of the bit errors tothe total number of bits transmitted within agiven time period.

Broadcast Control Channel(BCCH)

A channel from a base station to a mobilestation (MS) used for transmission ofmessages to all mobile stations located inthe cell coverage area.

BTS group A predefined set of BTSs which can becreated and handled for definition byNetwork Doctor.

Cell Identity (CI) A number which identifies a cell to thenetworks within a location area (LA).

Clear Code Code that describes why the call set-up orthe call itself has been disconnected.

Abbreviation Explanation

NTC TAN 0936/3 en


About this manual

.

r

l

t

Table 3.Terms used in this document.

For any other terms, refer toGlossary, TAN 0717.

Day The counting of data per day is based on theperiod_start_time field in themeasurement tables. This field always tellsthe starting hour of the measurement periodUnder one day there are hours from 00 to23.

Directed Retry A procedure used in a call set-up phase foassigning a mobile station to a trafficchannel of a cell other than the serving celwhen the traffic is congested.

Frame Check Sequence Extra characters added to a frame for thepurposes of error control. The FCS is usedin HDCL, Frame Relay, and other data linklayer protocols.

Key Performance Indicator The performance of the network iscalculated from the NMS/2000 based on theNetwork Element counter information.Sometimes the plain counter as suchdescribes an important performance aspec(number of calls, for example) of thenetwork but sometimes a formula ofcounters is needed (e.g. drop call ratio).

Maintenance Region Each object in the NMS/2000 databasebelongs to one and only one MaintenanceRegion (MR).

Mobile Terminated Call A call in which the called subscriber used amobile telephone.

NMS/2000 A product of Nokia Telecommunicationsfor the operation and maintenance ofcellular networks.

SQL*Plus An interactive program for accessing thedatabase.

Stand-alone Dedicated ControlChannel (SDCCH)

A control channel (CCH) used for roaming,authentication, encryption activation andcall control.

Time Slot (TSL) A time slot in the time division multipleaccess (TDMA) frame in the GSM radiointerface.

Traffic Channel A logical radio channel assigned to a basestation and primarily intended forconversation.

Trunk Reservation A stochastic algorithm employed in achannel allocation from a cell.

Term Explanation

NTC TAN 0936/3 en


BSS counter formulas

sedwitho amula

ithercausefor

youTheSCnder

te ites

aL

in

reent

2 BSS COUNTER FORMULAS

This chapter lists all BSS Network Doctor formulas. The more commonly uones are described in further detail concerning their use or known problemsthem, for example. In connection with the name of a formula there is alsreference to the BSC release (S1 to S6) since when the counters of the forhave been available.

The use of formulas backwards, S4 formulas with S3 for example, gives eno results because the measurement is not available, or false results besome counters, which are new in S4, will be filled with value -1 by the OMCS3 BSCs.

Note:

When running the reports with newer counters, be careful especially whenhave two BSC software releases running in the network simultaneously.simplest way to avoid problems is to start to use new counters of a new Brelease only when the new software release is used in the entire network uthe NMS/2000.

2.1 Random access (rach)

2.1.1 Average RACH slot, S1 (rach_1)

Use: Indicates the capacity of BTS for RACH burshandling. Normally shows a constant value becausis dependent on the BTS configuration which donot change often.

avg(a.ave_rach_slot/a.res_acc_denom1)

Counters from table(s):

p_nbsc_res_access

2.1.2 Peak RACH load, average, S1 (rach_2)

Use: Indicates the absolute peak value duringmeasurement period. Correlates strongly with Uinterference.

Experiences onuse: High values may suggest that MSs have problems

accessing the BTS.

Known problems: The peak value does not tell yet how many times thehave been other peaks during the measuremperiod.

NTC TAN 0936/3 en



H

knt

n

t,

ed

sl, 3

Open questions: How serious the high values equal to average RACslot really are?

avg(a.peak_rach_load)


p_nbsc_res_access

2.1.3 Peak RACH load %, S1 (rach_3)

Use: This PI indicates how near to full capacity the peause of RACH has been during the measuremeperiod.

max( a.peak_rach_slot )

100 * ------------------------------------- %

max ( a.ave_rach_slot/a.res_acc_denom1)


p_nbsc_res_access

2.1.4 Average RACH load %, S1 (rach_4)

Use: This PI indicates how high the RACH load is oaverage.

Experiences onuse: If the value is to the order of tens of per cen

interference is possible.

avg(a.ave_rach_busy/a.res_acc_denom3)

100 * -------------------------------------- %

avg(a.ave_rach_slot/res_acc_denom1)


p_nbsc_res_access

2.1.5 Average RACH busy, S1 (rach_5)

Use: This PI indicates roughly the average of the usRACH slots. If the average approaches the″averageRACH slot″ (rach_1 ) there probably are accesproblems and MS users get, more often than usuabeeps when trying to start calls.

avg(a.ave_rach_busy/a.res_acc_denom3)


p_nbsc_res_access

NTC TAN 0936/3 en



hesestsalidany

o

disesme/8

ce

2.1.6 RACH rejected due to illegal establishment cause, S5(rach_6)

sum(a.ghost_ccch_res- a.rej_seiz_att_due_dist)


p_nbsc_res_access

2.2 SDCCH drop failures (sd)

2.2.1 Ghosts detected on SDCCH and other failures, S1(sd_1)

Use: This part of ghost RACH accesses comprises:

• ghosts which have an occasionally valid establishment cause. Tshould comprise statistically 5/8 of all ghosts. Another 3/8 of ghoare detected already before SDCCH based on some investablishment cause. In GSM2 the ratio 5/8 and 3/8 is not validmore.

• multiple seizures of SDCCH.

Known problems: This counter includes also IMSI detaches which dnot have a counter of their own.

sum(a.sdcch_assign) - sum(b.succ_seiz_term + b.succ_seiz_orig +b.sdcch_loc_upd + b.succ_emerg_call + b.sdcch_call_re_est)

a = p_nbsc_traffic

b = p_nbsc_res_access

2.2.2 Ghosts detected on SDCCH and other failures, S1(sd_1a)

Use: - Ghosts which have an occasionally valiestablishment cause. These should comprstatistically 5/8 of all ghosts. Another 3/8 of ghostare detected already before SDCCH based on soinvalid establishment cause. In GSM2 the ratio 5and 3/8 is no longer valid.

- Multiple seizures of SDCCH.

Known problems: This counter includes also supplementary servirequest which do not have a counter of their own.

sum(a.sdcch_assign) - sum(b.succ_seiz_term + b.succ_seiz_orig +b.sdcch_loc_upd + b.succ_emerg_call + b.sdcch_call_re_est +imsi_detach_sdcch)

a = p_nbsc_traffic

NTC TAN 0936/3 en




2.2.3 SDCCH drop counters

SDCCH drop calls are counted as the sum of the following counters:

ID Name Description

1003 SDCCH_RADIO_FAIL A coverage problem, for example

• MS moves out from timingadvance

Common in connection withcoverage problems.

Triggered also if the MS user clearsthe call in the SDCCH phase.

1004 SDCCH_RF_OLD_HO Transactions have ended due to anold channel failure in HO.

For instance, a failure in DirectedRetry drops the call and triggers thiscounter in the source cell.

NTC TAN 0936/3 en



.

1075 SDCCH_ABIS_FAIL_CALL Transactions have ended due to Abisproblems. Missing channelactivation ack or if no indication ofcall establishment has been receivedAugmented when the BSC receivesan Establish indication the contentsof which are corrupted, or morecommonly when a timer (T3101,default 3 sec) expires while waitingfor the Establish indication. TheEstablish indication is the firstmessage sent from the BTS to theBSC after the MS has successfullyaccessed the SDCCH.

• Ghost seizures which accidentallyhave a valid establishment causeand are detected on SDCCH,increment this counter.

• Multiple SDCCH seizures maycause these failures. If the MS hasto send multiple random accessesfor a call or location update, it ispossible that there will bemultiple reservations of SDCCHfor one mobile naturally themobile can use only one of theseand the rest will eventually timeout and result insdcch_abis_fail_call . Onereason for multiple SDCCHseizures can be DL interference.

• Too short frequency&BSIC reusedistance may cause HO burstfrom one cell to be interpreted asRACH bursts in another cellcausing false SDCCH seizures.This reason may be suspected ifthere are short, 2 - 3second peakswith high blocking rate onSDCCH.

• A more rare yet possible reasonare failing LUs.

1076 SDCCH_ABIS_FAIL_OLD Same as above but when trying toreturn back to the old channel in HO.

ID Name Description

NTC TAN 0936/3 en



r

Table 4.SDCCH Drop Counters

1078 SDCCH_A_IF_FAIL_CALL Transactions have ended due to Ainterface problems. A high value canbe related to IMSI detaches (in S3).

See #1 for all possible causes.SDCCH observation may be used todiagnose the cause on cell level. Ifthis occurs in the entire network orBSS areas, use Clear Codemeasurement for cause analysis.

1079 SDCCH_A_IF_FAIL_OLD Same as above but when trying toreturn back to the old channel in HO.

1035 SDCCH_LAPD_FAIL Transactions have ended due to Lapdproblems (a call is lost when Lapdgoes down).

1036 SDCCH_BTS_FAIL Transactions have ended due to BTSproblems. A call is lost when TRX/TSL is blocked with causebts_fail due to FU or CU or BCFfault or BTS or BCF reset.

Even if occurs, the share is normallyvery low because the situation istransient.

1038 SDCCH_BCSU_RESET Transactions have ended due toBSCU reset (calls are lost whenBSCU is reset).


1037 SDCCH_USER_ACT Transactions have ended due to useactions. Time slot or TRX is lockedby the user via the Top-level UserInterface or BSC MML.


1039 SDCCH_NETW_ACT Transactions have ended due to achange in the radio networkconfiguration (BCCH swap toanother TRX) initiated by the BSC.The cause for the configurationchange fails or locally blockedBCCH TRX.


ID Name Description

NTC TAN 0936/3 en



es.are

rs arever.

theCHl.

anSCMS

ou

. Ar.eing

f anistichatesis

To see what DX causes can trigger the counters above, see #2.

2.2.4 Problems with the SDCCH drop counters

2.2.4.1 Phantoms affect SDCCH_abis_fail_*

SDCCH drop ratio counts the ratio of all SDCCH failures to SDCCH seizurNormally most of the seizures are caused because of phantoms whichcounted as SDCCH_abis_fail_call and SDCCH_abis_fail_old . Inpractice, the latter case does not practically occur because SDCCH handoveusually not used and particularly because phantoms do not perform hando

The percentage ofSDCCH_abis_fail_call used to be very high in a lowtraffic network (even tens of per cent) whereas in a high traffic networkpercentage settled down to around 18-20 per cent. In BTS B9, BTS RAdetection was improved, and figures well under 10 per cent are now typica

2.2.4.2 A interface blocking not shown

SDCCH failures do not include A interface blocking. In A interface blocking,MSC clears the call without a request from a BSC. The failure is not in the Bwhere the principle has been that MSC failures are not counted. Yet from anuser’s point of view, A interface blocking ends up to a failed call attempt. Ycan detect A interface blocking from the NSS statistics for circuit groups.

2.3 SDCCH drop ratio (sdr)

2.3.1 SDCCH drop %, blocking excluded, S3 (sdr_1a)

Use: To follow up the performance of SDCCH.

Experiences onuse: High SDCCH drop rates result from ghost accesses

BTS decodes them from environmental obackground noise and filters out most of themHowever, all of them cannot be filtered out and thRACH request is passed on to the BSC for processand for the allocation of a SDCCH channel.

The counterghost_ccch_res (3030) is updatedeach time a channel required is rejected because oinvalid establishment cause. In GSM ph.1 there exaltogether eight establishment causes, three of whare undefined as invalid, for example,resulting in ththis counter shows only 3/8 of all the ghost accessthe BTS has decoded. For the rest, a SDCCHallocated and this will result insdcch_abis_fail_call failure. Because of ghostattempts the SDCCH drop ratio is high with low

NTC TAN 0936/3 en



heop

en

o

n

ichng

traffic. As the amount of call attempts increases, tinfluence of ghosts becomes smaller and the drratio approaches its real value.

The rate of ghosts coming to SDCCH dropped whBTS B9 was taken into use.

Known problems: In SDCCH failure counters it is not possible tseparate LU and call seizures.

sum(sdcch_radio_fail+sdcch_rf_old_ho+sdcch_user_act+sdcch_bcsu_reset+

sdcch_netw_act+sdcch_abis_fail_call+sdcch_abis_fail_old+sdcch_bts_fail+ sdcch_lapd_fail+sdcch_a_if_fail_call+sdcch_a_if_fail_old)

100 * --------------------------------------------------------------- %

sum(sdcch_assign+sdcch_ho_seiz)


p_nbsc_traffic

2.3.2 SDCCH drop %, blocking & Abis failure excluded, S3(sdr_2)

Known problems: SDCCH_ABIS_CALL does not necessarily refer toghosts but also, for example, to failing locatioupdates.


sdcch_netw_act +sdcch_bts_fail+

sdcch_lapd_fail+sdcch_a_if_fail_call+sdcch_a_if_fail_old)

100 * ----------------------------------------------------------- %


- sum(sdcch_abis_call+sdcch_fail_old)


p_nbsc_traffic

2.3.3 Illegal establishment cause % (sdr_3a)

Use: This PI gives you the number of ghost accesses whtry to seize SDCCH but are rejected before seiziSDCCH due to an illegal establishment cause.

100* (a.ghost_CCCH_res- a.rej_seiz_att_due_dist) / a.ch_req_msg_rec %


p_nbsc_res_access

NTC TAN 0936/3 en



ng

n

Heninh

ee

entH

ee-

2.4 Setup success ratio (cssr)

2.4.1 SDCCH, TCH setup success %, S4 (cssr_2)

Use: This PI shows the setup success ratio, includiSDCCH and TCH. It works also in the case of DR.

Possible fault cases:

- faulty DSP in BTS TRX

Experiences onuse: Fits for general quality monitoring. Values betwee

2.5 and 4%, for example.

Known problems: ’B no answer’ is also counted as a successful call.

Includes also SMSs and LUs which do not use TCat all. This causes problems in special cases whthere are many LUs but few calls. The problemscalls are hidden by a great number of LUs whicreceive SDCCH successfully.

There is a known case in whichcssr_1 went downby 6 per cent down due to a MSC problem whilcssr_2 did not show any change. This could be duto the location updates which increased by 10 per cin MSC restart and thus compensated the bad TCsetup.

Troubleshooting: You can use SDCCH and TCH observations to swhich one is failing. However, note that this is a timeconsuming task.

sum(a.call_setup_failure)

100* ( 1 - ----------------------------------------) %

sum(a.setup_succ+a.call_setup_failure)


p_nbsc_service

2.5 TCH drop failures

2.5.1 TCH drop call counters

TCH drop calls are counted as the sum of the following counters:

NTC TAN 0936/3 en



s

ID Name Description

1011 TCH_RADIO_FAIL • Radio link timeout

• Release indication from MS

• MS moves out from timing advance

• TCH assignment failure where anEstablish Indication has beenreceived but Assignment Completehas not been received

This counter is typical in connectionwith coverage problems. This failuretype is usually the dominating one.

1014 TCH_RF_OLD_HO Same as above but when trying to returnto the old channel in HO.

1084 TCH_ABIS_FAIL_CALL • missing ack of channel activation

• missing establishment indication

• reception of error indication

• corruption of messages

• measurement results no longerreceived from BTS

• excessive timing advance

• missing HO detection

• T3107 (assignment completelymissing) expiry

• T3109 expiry. As in this case the drophappens in the release phase, the MSuser cannot see the situation as a dropcall.

The BTS suffering from this failure canbe faulty or their TCH TRX suffers frombad interference (TCH assignmentfails).

See #1 for all possible causes that triggerthis counter.

Note:If FACCH call setup is used, we mayexpect that we start to see ghost seizureincrementing this counter because thesignalling tries to use SDCCH instead ofTCH.

The portion of this failure decreasedfrom S4 to S5. Double counting of acoprocess failure was causing highervalues in S4.

1085 TCH_ABIS_FAIL_OLD Same as above but when trying to returnto the old channel in HO.

NTC TAN 0936/3 en



1087 TCH_A_IF_FAIL_CALL • A clear command from the MSCduring the call setup phase before theassignment from MS is complete

• Abnormal clear received due to A-interface (reset circuit, SCCP clear).For example, a BSU reset in MSCmakes MSC send a "reset circuit"message.

Note:There have been cases where the MSCof another vendor in inter-MSChandovers has caused high values eventhough the handovers have beensuccessful.

See #1 for all possible causes that triggerthis counter.

1088 TCH_A_IF_FAIL_OLD Same as above but when trying to returnto the old channel in HO.

Note:Can be updated when GSM timer T8expires in the source BSC during anexternal handover.

1029 TCH_TR_FAIL • Transcoder failure during a callattempt

This counter is updated only whenBTS sends a "connection failure"with cause "remote trascoder failure"and the call is released due to this.

Note:If this failure is related to a transcoder,you can see its share to be high for oneBSC. Another possibility is that theproblem lies in a BTS. Alsointerruptions of the transmission maycause this failure (alarms may be filteredout in a BSC or OMC to reduce thenumber of alarms due to disturbance).

In analysing the problem, you may findit helpful to check the pattern over alonger period of time.

Note:In S6 the portion of this failure hasdecreased due to improvements intranscoders.

1030 TCH_TR_FAIL_OLD Same as above but when trying to returnto the old channel in HO.

ID Name Description

NTC TAN 0936/3 en



redtionsalysis

eas,

oldnt of

Table 5.TCH drop call counters

To see what DX causes can trigger the counters above, see #2.

The problem especially with failure classes Abis and Aif is that they are triggeby many different causes. To analyse the case in question, TCH observamay be used. As there are limitations on how to set the observations, the anis more time-consuming.

If the problem is not cell specific but related to the entire network or BSS aryou can also use the Clear Code measurement.

*_OLD counters are related to the handover situation when returning to thechannel fails causing a call to drop. Thus, these counters reflect the amoucall drops in handovers.

1046 TCH_LAPD_FAIL TRX is blocked due to a LAPD failure(signalling link failure or PCM failure).

Even if occurs, the share is very smallbecause only ongoing calls are droppedwhen the LAPD fails.

1047 TCH_BTS_FAIL TRX is blocked by a BTS failure.

(FU fault, CU fault, BTS reset, BCFreset, CU and FU fault, BCF fault).

Even if occurs, the share is very smallbecause only ongoing calls are droppedwhen a BTS fails.

1049 TCH_BCSU_RESET TRX is blocked by BCSU reset.

Even if occurs, the share is very smallbecause only ongoing calls are droppedwhen BCSU resets.

1048 TCH_USER_ACT Busy TSL or TRX blocked by MMLcommand (blocked by user).

Even if occurs, the share is very smallbecause only ongoing calls are droppedwhen the blocking command is given.

1050 TCH_NETW_ACT TRX is blocked by a fault leading toreconfiguration (blocked by the system).

Even if occurs, the share is very smallbecause only ongoing calls are droppedwhen reconfiguration is executed.

1081 TCH_ACT_FAIL_CALL Channel activation nack received.

ID Name Description

NTC TAN 0936/3 en



rs toor

rs tocall

faultase

sincethese

the

while

2.5.2 Drop call ratio

Drop call ratio is counted as the ratio of the sum of the above named counteall TCH seizures for a new call. This ratio is used in reports for networkmaintenance region level. Seedcr_3* .

2.5.3 Drop-out ratio

Drop-out ratio is counted as the ratio of the sum of the above named counteall TCH seizures. This ratio is used on cell level reports where the concept ofis not applicable.

2.5.4 Problems with the drop call counters

2.5.4.1 TCH Tr, Abis failures

These failures can contain also situations when timer T3109 (8 to 15 s, de12 s) expires in a BSC in the call release phase while waiting for the Releindication. With BTS software 6.0 these were seen as TC failures, whereasBTS software 6.1 they have been Abis failures. The MS user does not seefailures as real drop calls.

If you detect a high ratio of TC or Abis failures, check the BTS release andtimer.

2.5.4.2 TCH_A_IF_OLD high

There have been cases when this counter has been showing high valuesanother vendor’s MSC has cleared the call with the causeCLR_CMDin the caseof a successful inter-MSC HO.

2.6 Drop call failures (dcf)

2.6.1 TCH drop calls in HO, S2 (dcf_2)

Open questions: Claims of cases when theTCH_A_IF_OLD has notbeen a drop call have been made.

sum(tch_rf_old_ho+ tch_abis_fail_old+tch_a_if_fail_old+tch_tr_fail_old)


p_nbsc_traffic

2.6.2 TCH drop calls in BSC outgoing HO, S3 (dcf_3)

Known problems: Accuracy is not good.

sum(a.bsc_o_drop_calls)


NTC TAN 0936/3 en



ble

yoS

on

entspts,re-

p_nbsc_ho

2.6.3 TCH drop calls in intra-cell HO, S3 (dcf_4)


sum(a.cell_drop_calls)


p_nbsc_ho

2.6.4 TCH drop calls in intra-BSC HO, S3 (dcf_6)

Known problems: Use on the BTS level. On the area level causes doucounting. Accuracy is not good.

sum(bsc_i_drop_calls+bsc_o_drop_calls+cell_drop_calls)


p_nbsc_ho

2.6.5 Drop calls in BSC incoming HO, S3 (dcf_7)


sum(a.bsc_i_drop_calls)


p_nbsc_ho

2.7 TCH drop call % (dcr)

2.7.1 TCH drop call %, area, real, after re-establishment, S3(dcr_3f)

Use: On the area level.

Experiences onuse: See dcr_3g . Call re-establishments can markedl

improve the drop call ratio (for example, from 2.5 t2.0%). Since this is an improvement from the Muser’s point of view, this figure suits better tomanagement reports.

Known problems: 1) Seedcr_3g .

2) It is assumed that call re-establishments happenTCH. In fact they may happen also on SDCCH.

3) The counters used to compensate re-establishmare the ones that indicate re-establishment attemnot the successful re-establishments. In S7/T11

NTC TAN 0936/3 en



see

-s

neeno

ainisal

ener

e-ellell

his

nlly

establishments can be considered accurately (dcr_3j ).

4) On cell level it can happen that the call is reestablished in a different cell than where it wadropped, resulting in inaccuracy.

100-csf_4p =

sum(tch_radio_fail+tch_rf_old_ho+tch_abis_fail_call+tch_abis_fail_old+

tch_a_if_fail_call+tch_a_if_fail_old+tch_tr_fail+tch_tr_fail_old+

tch_lapd_fail+tch_bts_fail+tch_user_act+tch_bcsu_reset+tch_netw_act+

tch_act_fail_call

- sum(b.sdcch_call_re_est+b.tch_call_re_est) ;(call re-establishments)

100* ---------------------------------------------------------------- %

sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell_sdcch_tch) ;(DR calls)

+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup

- sum(b.sdcch_call_re_est+b.tch_call_re_est) ;(call re-establishments)


a = p_nbsc_traffic


c = p_nbsc_ho

2.7.2 TCH drop call %, area, real, before re-establishment,S3 (dcr_3g)


Experiences onuse: In good networks where optimisation has been do

already for two to three years, values have bearound 2 to 3 per cent (and in networks in which noptimisation has been done yet, the values remeven above 10 per cent). A value of 5 per centachievable in many networks despite their bad initicoverage planning.

Interference also raises the figure. Be careful whsetting the target values since the factors (whethcaused by the customer or Nokia) can be timconsuming and expensive to prove. If used on clevel, the values can be even over 100 per cent if a ctakes HOs in but then drops them.

Known problems: Some failures in the release phase are included in tformula (tch_abis_fail_call ) but are, in fact,not perceived as drop calls by the MS user.

tch_norm_seiz does not mean that the MS is oTCH. It means that TCH has been successfu

NTC TAN 0936/3 en



H

esor

stols

yoS

tsn

seized. Some mobiles never appear to the TCbecause:

• the call is cleared by the user (probability is higher if call setup taka long time, and thus DR and queuing can increase this share)

• the mobile fails or

• something else goes wrong.

TCH failure counters are not triggered if a call icleared by pre-emption (1st priority call requestedbe established, all TCH seized, lower priority calon) whereasp_nbsc-service_dropped_call istriggered.




tch_act_fail_call)

100* ---------------------------------------------------------------- %


+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell_sdcch_tch);(DR calls)

+ sum(a.tch_seiz_due_sdcch_con); calls started as FACCH call setup


a = p_nbsc_traffic

c = p_nbsc_ho

2.7.3 TCH drop call %, area, real, after re-establishment, S7(dcr_3h)


Experiences onuse: See dcr_3 . Call re-establishments can markedl

improve the drop call ratio (for example, from 2.5 t2.0%). Since this is an improvement from the Muser’s point of view, this figure suits better tomanagement reports.

Known problems: Seedcr_3g . It is assumed that call re-establishmenoccur on TCH. In fact they may occur also oSDCCH.




tch_act_fail_call

- sum(b.tch_re_est_assign) ;(call re-establishments)

100* ---------------------------------------------------------------- %


NTC TAN 0936/3 en



neeno

ainisalre.heia)

00.

his

nllyH

erd

stols





a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

2.7.4 TCH drop call %, area, real, before re-establishmentS3 (dcr_3i)

Experiences onuse: In good networks where optimisation has been do

already for two to three years, values have bearound 2 to 3 per cent (and in networks in which noptimisation has been done yet the values remeven above 10 per cent. A value of 5 per centachievable in many networks despite their bad initicoverage planning. Interference also raises the figuBe careful when setting the target values since tfactors (whether caused by the customer or Nokcan be time-consuming and expensive to prove.

If used on cell level, the values can be even over 1per cent if a cell takes HOs in but then drops them

Known problems: 1) Some failures in release phase are included in tformula (tch_abis_fail_call ) but are, in fact,not perceived as drop calls by the MS user.

2) tch_norm_seiz does not mean that the MS is oTCH. It means that TCH has been successfuseized. Some mobiles never appear to the TCbecause

2a) the call is cleared by the user (probability is highif call setup takes a long time, and thus DR anqueuing can increase this share) or

2b) the mobile fails or

2c) something else goes wrong.

3) TCH failure counters are not triggered if a call icleared by pre-emption (1st priority call requestedbe established, all TCH seized, lower priority calon), whereasp_nbsc-service.dropped_call istriggered.

100-csf_4u =

NTC TAN 0936/3 en



reuse

yoSo

on

-s




tch_act_fail_call)

100* ---------------------------------------------------------------- %



-sum(a.tch_succ_seiz_for_dir_acc) ;ref.2



a = p_nbsc_traffic

c = p_nbsc_ho

Ref.2. Compensation is needed, since in case of Direct Access to superTRX thetch_norm_seiz is triggered in parallel withcell_sdcch_tch .

2.7.5 TCH drop call %, area, real, after re-establishment, S7(dcr_3j)

Experiences onuse: See dcr_3 . Call re-establishments can markedl

improve the drop call ratio (for example, from 2.5 t2.0%). Since this is an improvement from the Muser's point of view, this figure suits better tmanagement reports.

Known problems: Seedcr_3g .

- It is assumed that call re-establishments happenTCH. In fact they may happen also on SDCCH.

- On cell level it can happen that the call is reestablished in a different cell than where it wadropped, resulting in inaccuracy.

100-csf_4v =




tch_act_fail_call


100* ---------------------------------------------------------------- %



-sum(a.succ_tch_seiz_for_dir_acc) ;ref.2




a = p_nbsc_traffic

b = p_nbsc_service

NTC TAN 0936/3 en



reuse

H).

H).eet

c = p_nbsc_ho


2.7.6 TCH drop-out %, BTS level, before call re-establishment, S3-S6 (dcr_4c)

Use: On the BTS level. To rank cells by the share of TCdrop call failures per TCH seizure (normal or HOIntra-cell HO excluded which is meaningful in thecase of IUO, for example.


sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+

a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+a.tch_tr_fail_old+

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)

100* --------------------------------------------------------------- %



+ sum(a.tch_seiz_due_sdcch_con); (FACCH call setup calls)

+ sum(c.msc_i_tch_tch+c.bsc.bsc_i_tch_tch);(TCH-TCH Ho from other cells)


a = p_nbsc_traffic

c = p_nbsc_ho

2.7.7 TCH drop-out %, BTS level, before call re-establishment, S3-S6 (dcr_4d)

Use: On the BTS level. To rank cells by the share of TCdrop call failures per TCH seizure (normal or HOIntra-cell HO is excluded, which is meaningful in thcase of IUO. Inter-cell HOs are counted only as a nvalue.






100* ---------------------------------------------------------------- %


+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell_sdcch_tch);(DR calls)+ sum(a.tch_seiz_due_sdcch_con) ; (FACCH call setup calls)

+ sum(c.msc_i_tch_tch+c.bsc.bsc_i_tch_tch)

NTC TAN 0936/3 en



H).e

reuse

H).eet

- sum(c.msc_o_tch_tch+c.bsc.bsc_o_tch_tch);(TCH-TCH Ho net in from other cells)


a = p_nbsc_traffic

c = p_nbsc_ho

2.7.8 TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4e)

Use: On the BTS level. To rank cells by the share of TCdrop call failures per TCH seizure (normal or HOIntra-cell HO is excluded, which is meaningful in thcase of IUO, for example.


100-csf_4y=





100* --------------------------------------------------------------- %



- sum(a.tch_succ_seiz_for_dir_acc) ;ref.2

+ sum(a.tch_seiz_due_sdcch_con) ; (FACCH call setup calls)

+ sum(c.msc_i_tch_tch+c.bsc.bsc_i_tch_tch);(TCH-TCH Ho from other cells)


a = p_nbsc_traffic

c = p_nbsc_ho


2.7.9 TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4f)

Use: On the BTS level. To rank cells by the share of TCdrop call failures per TCH seizure (normal or HOIntra-cell HO is excluded, which is meaningful in thcase of IUO. Inter-cell HOs are counted only as a nvalue.




NTC TAN 0936/3 en



reuse

d

).g

e

llomt,

ll

ed

ins a

de



100* ---------------------------------------------------------------- %


+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell_sdcch_tch) ;(DRcalls)

- sum(a.succ_tch_seiz_for_dir_acc) ;ref.2

+ sum(a.tch_seiz_due_sdcch_con) ; (FACCH call setup calls)

+ sum(c.msc_i_tch_tch+c.bsc.bsc_i_tch_tch)

- sum(c.msc_o_tch_tch+c.bsc.bsc_o_tch_tch);(TCH-TCH Ho net in from other cells)


a = p_nbsc_traffic

c = p_nbsc_ho


2.7.10 TCH drop call (dropped conversation) %, BSC level,S4 (dcr_5)

Use: On the area level. Tells the ratio of calls droppewhile A and B are talking, that is afterconn_ack .

Theoretically should always be less thandcr_3f ordcr_3g . Results from networks 2 to 6 %.

Known problems: Does not work on the BTS level (handoversAccurate on the BSC and PLMN levels after a buwas corrected.

If call re-establishment is active and occurs, thconver_started is triggered once anddropped_calls only once. After the first call re-establishment thedropped_calls counter is nolonger incremented in this call no matter if the castays or drops. This means that in this case seen frcounters, the call looks like a dropped call. In facfrom the MS user’s point of view it is impossible toknow whether it was dropped or not (does care_establishment save the call or not).

Subscriber clear during HO is counted as a droppcall.

Due to an error in the mapping table also blockingthe case of an external HO has been counted adropped call.

In the NMS/2000 T8 thep_nbsc_service table didhave wrong index settings (a bug in the upgra

NTC TAN 0936/3 en



ry

r

lyof

d

er

de

tlls

script) and therefore the use of the table was veslow.

External HOs (inter BSC handovers) triggeconver_started counter in target cell. Thereforeon network level the ratio does not illustrate correctthe dropped conversation ratio from the MS’s pointview.

sum(a.dropped_calls)

100* -------------------- %

sum(a.conver_started)


p_nbsc_service

2.7.11 TCH drop call (dropped conversation) %, area, S4(dcr_5a)

Use: On the area level. Tells the ratio of calls droppewhile A and B are talking, that is afterconn_ack .Inter BSC handovers are subtracted in thdenominator because they triggeconver_started . Compensation is 100% true onlyif the area has no inter-BSC handovers from outsithe area.

Theoretically should always be less thandcr_3f ordcr_3g . Results from networks 2 to 6 %.

Known problems: Seedcr_5 .

1) conver_started is not triggered for call re-establishments.

dropped_calls is triggered once for the first re-establishment. After that setup_failure istriggered if the call is a dropped call.

If the call is ’saved’ by re-establishment multipletimes, setup_failure will be triggered severaltimes accordingly.

2) Drop call by pre-emption (1st priority call requesto be established, all TCHs seized, lower priority caon) triggersdropped_calls . Therefore this counterdoes not indicate only technical drops.

Future: In S7, re-establishments can be compensated.

sum(b.dropped_calls)

NTC TAN 0936/3 en



)

)

ntspts,

100* -------------------------------------------------- %

sum(b.conver_started) - sum(a.msc_i_tch_tch)


a = p_nbsc_ho

b = p_nbsc_service

2.7.12 Drops per erlang, before re-establishment, S4 (dcr_10

Use: On the area and BTS level.

Known problems: Works for 60 min period.

Drops

-------------------------- =

Traffic (Erlang hours sum)





------------------------------------------------------------------

sum(b.ave_busy_tch/b.res_av_denom14) / (60/avg(period_duration))


a = p_nbsc_traffic

b = p_nbsc_res_avail

2.7.13 Drops per erlang, after re-establishment, S4 (dcr_10a


Known problems: Works for 60 min period.

The counters used to compensate re-establishmeare the ones that indicate re-establishment attemnot the successful re-establishments.

Drops- re-establishments

-------------------------- =



a.tch_a_if_fail_call+ a.tch_a_if_fail_old+a.tch_tr_fail+ a.tch_tr_fail_old+



- sum(c.sdcch_call_re_est+c.tch_call_re_est) ;call re-establishments

-------------------------------------------------------------------



a = p_nbsc_traffic

NTC TAN 0936/3 en



)


c = p_nbsc_res_access

2.7.14 Drops per erlang, after re-establishment, S7 (dcr_10b


Known problems: Works for the 60 min period.

Drops- re-establishments

-------------------------- =






- sum(c.tch_re_est_assign) ;call re-establishments

------------------------------------------------------------------



a = p_nbsc_traffic


c = p_nbsc_service

2.8 Handover (ho)

2.8.1 Return from super TRXs to regular TRX, S4 (ho_1)

sum(a.ho_succ_to_reg_freq)

100* ------------------------------ %

sum(a.ho_succ_from_reg_freq)


p_nbsc_underlay

2.8.2 HO attempts from regular TRXs to super, S4 (ho_2)

sum(a.ho_att_from_reg_freq)


p_nbsc_underlay

2.8.3 HO attempts from super to regular, S4 (ho_3)

sum(a.ho_att_to_reg_freq)


p_nbsc_underlay

NTC TAN 0936/3 en



2.8.4 Share of HO attempts from super to regular due to DLquality, S4 (ho_4)

sum(a.att_from_super_dl_qual)

100 * ------------------------------------------------------ %

sum(a.att_from_super_dl_qual + a.att_from_super_dl_if

+a.att_from_super_ul_if + a.att_from_super_bad_ci)


p_nbsc_underlay

2.8.5 Share of HO attempts from super to regular due to DLinterference, S4 (ho_5)

sum(a.att_from_super_dl_if)

100 * ------------------------------------------------------ %

sum(a.att_from_super_dl_qual + a.att_from_super_dl_if

+a.att_from_super_ul_if + a.att_from_super_bad_ci)


p_nbsc_underlay

2.8.6 Share of HO attempts from super to regular due to ULinterference, S4 (ho_6)

sum(a.att_from_super_ul_itf)

100 * ------------------------------------------------------ %

sum(a.att_from_super_dl_qual + a.att_from_super_dl_itf

+a.att_from_super_ul_itf + a.att_from_super_bad_ci)


p_nbsc_underlay

2.8.7 Share of HO attempts from super to regular due to badC/I, S4 (ho_7)

sum(a.att_from_super_bad_ci)

100 * ------------------------------------------------------ %

sum(a.att_from_super_dl_qual + a.att_from_super_dl_itf

+a.att_from_super_ul_itf + a.att_from_super_bad_ci)


p_nbsc_underlay

2.8.8 MSC incoming HO attempts (ho_8)

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at)


p_nbsc_ho

NTC TAN 0936/3 en



2.8.9 MSC outgoing HO attempts (ho_9)

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at)

Counters from table(s):p_nbsc_ho

2.8.10 BSC incoming HO attempts (ho_10)

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)


2.8.11 BSC outgoing HO attempts (ho_11)

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at)


2.8.12 HO attempts, S4 (ho_13)

sum(cause_up_qual+cause_up_level+cause_down_qual+cause_down_lev+cause_distance+cause_msc_invoc+cause_intfer_up+cause_intfer_dwn+cause_umbr+cause_pbdgt+cause_omc+cause_ch_adm+cause_traffic+cause_dir_retry+cause_pre_emption+cause_field_drop+cause_low_distance+cause_bad_CI+cause_good_CI)


2.8.13 HO attempts, S3 (ho_13a)

sum(msc_i_tch_tch_at + msc_i_sdcch_tch_at+ msc_i_sdcch_at)

+ sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at)

+ sum(bsc_i_tch_tch_at + bsc_i_sdcch_tch_at+ bsc_i_sdcch_at)

+ sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at)

+ sum(cell_tch_tch_at + cell_sdcch_tch_at+ cell_sdcch_at)


p_nbsc_ho

2.8.14 HO attempts, outgoing and intra-cell, S5 (ho_13c)

sum(cause_up_qual+cause_up_level+cause_down_qual+cause_down_lev+cause_distance

+cause_msc_invoc+cause_intfer_up+cause_intfer_dwn+cause_umbr+cause_pbdgt+cause_omc

+cause_dir_retry+cause_pre_emption+cause_field_drop

+cause_low_distance+cause_bad_CI+cause_good_CI

+ cause_ho_due_slow_mov_ms+ switch_crcr_pool ;S5)


p_nbsc_ho

2.8.15 HO attempts, outgoing and intra-cell, S6 (ho_13d)

sum(cause_up_qual+cause_up_level+cause_down_qual+cause_down_lev+cause_distance

NTC TAN 0936/3 en



ofen

ll

+cause_msc_invoc+cause_intfer_up+cause_intfer_dwn+cause_umbr+cause_pbdgt+cause_omc +cause_dir_retry+cause_pre_emption+cause_field_drop

+cause_low_distance+cause_bad_CI+cause_good_CI

+ cause_ho_due_slow_mov_ms+ switch_crcr_pool ;S5

+ ms_slow_speed + ms_high_speed ; S6)


p_nbsc_ho

2.8.16 HO attempts, outgoing and intra-cell, S3, (ho_13e)

sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at) +sum(bsc_o_tch_tch_at + bsc_o_sdcch_tch_at+ bsc_o_sdcch_at) +sum(cell_tch_tch_at + cell_sdcch_tch_at+ cell_sdcch_at)


p_nbsc_ho

2.8.17 TCH requests for HO (ho_14a)

sum(tch_req-tch_call_req-tch_fast_req)

Counters from table(s):p_nbsc_traffic

2.8.18 TCH requests for HO, (ho_14b)

Note: When you are using IUO, you can see that numbersTCH requests due to HO attempts increases (evtenfold).

sum(a.tch_req-a.tch_call_req-tch_fast_req)-sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type)


a = p_nbsc_traffic

b = p_nbsc_ho

2.8.19 TCH seizures for HO (ho_15)

sum(tch_ho_seiz)


2.8.20 TCH-TCH HO attempts (ho_16)

Use: On the BTS level. If used on the area level, it wiresult in double counting of inter-cell HOs.

sum( msc_o_tch_tch_at + msc_i_tch_tch_at + bsc_o_tch_tch_at +bsc_i_tch_tch_at + cell_tch_tch_at)


NTC TAN 0936/3 en



ll

ll

ll

ll

ll

2.8.21 SDCCH-TCH HO attempts (ho_17)


sum( msc_o_sdcch_tch_at + msc_i_sdcch_tch_at + bsc_o_sdcch_tch_at +bsc_i_sdcch_tch_at + cell_sdcch_tch_at)


2.8.22 SDCCH-SDCCH HO attempts (ho_18)


sum( msc_o_sdcch_at + msc_i_sdcch_at + bsc_o_sdcch_at + bsc_i_sdcch_at+ cell_sdcch_at)


2.8.23 TCH-TCH HO success (ho_19)


sum( msc_o_tch_tch + msc_i_tch_tch + bsc_o_tch_tch + bsc_i_tch_tch +cell_tch_tch)


2.8.24 SDCCH-TCH HO success (ho_20)


sum( msc_o_sdcch_tch + msc_i_sdcch_tch + bsc_o_sdcch_tch +bsc_i_sdcch_tch + cell_sdcch_tch)


2.8.25 SDCCH-SDCCH HO success (ho_21)


sum( msc_o_sdcch + msc_i_sdcch + bsc_o_sdcch + bsc_i_sdcch + cell_sdcch)


NTC TAN 0936/3 en



ll

ll

ll

ll

2.8.26 MSC controlled HO attempts (ho_22)


sum( msc_o_tch_tch_at + msc_i_tch_tch_at + msc_o_sdcch_tch_at +msc_i_sdcch_tch_at + msc_o_sdcch_sdcch_at + msc_i_sdcch_sdcch_at)


2.8.27 BSC controlled HO attempts (ho_23)


sum( bsc_o_tch_tch_at + bsc_i_tch_tch_at + bsc_o_sdcch_tch_at +bsc_i_sdcch_tch_at + bsc_o_sdcch_sdcch_at + bsc_i_sdcch_sdcch_at)


2.8.28 Intra-cell HO attempts (ho_24)

sum(cell_tch_tch_at+ cell_sdcch_tch_at+ cell_sdcch_at)


2.8.29 MSC controlled HO success (ho_25)


sum( msc_o_tch_tch + msc_i_tch_tch + msc_o_sdcch_tch + msc_i_sdcch_tch+ msc_o_sdcch_ + msc_i_sdcch)


2.8.30 BSC controlled HO success (ho_26)


sum( bsc_o_tch_tch + bsc_i_tch_tch + bsc_o_sdcch_tch + bsc_i_sdcch_tch+ bsc_o_sdcch + bsc_i_sdcch)


2.8.31 Intra-cell HO success (ho_27)

sum(cell_tch_tch + cell_sdcch_tch + cell_sdcch)


NTC TAN 0936/3 en



2.8.32 MSC incoming HO success (ho_28)

sum(msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)


2.8.33 MSC outgoing HO success (ho_29)

sum(msc_o_tch_tch+msc_o_sdcch_tch+msc_o_sdcch)


2.8.34 BSC incoming HO success (ho_30)

sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)


2.8.35 BSC outgoing HO success (ho_31)

sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)


2.8.36 Incoming HO success (ho_32)

sum(msc_i_succ_ho+ bsc_i_succ_ho)


2.8.37 Outgoing HO success (ho_33)

sum(msc_o_succ_ho+ bsc_o_succ_ho)


2.8.38 Outgoing HO attempts (ho_34)

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at+bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at)


2.8.39 Incoming HO attempts (ho_35)

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at+bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)


NTC TAN 0936/3 en



2.8.40 Outgoing SDCCH-SDCCH HO attempts (ho_36)

sum(msc_o_sdcch_at+bsc_o_sdcch_at)


2.8.41 Incoming SDCCH-SDCCH HO attempts (ho_37)

sum(msc_i_sdcch_at+bsc_i_sdcch_at)


2.8.42 Outgoing SDCCH-TCH HO attempts (ho_38)

sum(msc_o_sdcch_tch_at+bsc_o_sdcch_tch_at)


2.8.43 Incoming SDCCH-TCH HO attempts (ho_39)

sum(msc_i_sdcch_tch_at+bsc_i_sdcch_tch_at)


2.8.44 Outgoing TCH-TCH HO attempts (ho_40)

sum(msc_o_tch_tch_at+bsc_o_tch_tch_at)


2.8.45 Incoming TCH-TCH HO attempts (ho_41)

sum(msc_i_tch_tch_at+bsc_i_tch_tch_at)


2.8.46 Outgoing SDCCH-SDCCH HO success (ho_42)

sum(msc_o_sdcch+bsc_o_sdcch)


2.8.47 Incoming SDCCH-SDCCH HO success (ho_43)

sum(msc_i_sdcch+bsc_i_sdcch)


NTC TAN 0936/3 en



he

ereris-

rsemms

ritme

2.8.48 Outgoing SDCCH-TCH HO success (ho_44)

sum(msc_o_sdcch_tch+bsc_o_sdcch_tch)


2.8.49 Incoming SDCCH-TCH HO success (ho_45)

sum(msc_i_sdcch tch+bsc_i_sdcch_tch)


2.8.50 Outgoing TCH-TCH HO success (ho_46)

sum(msc_o_tch_tch+bsc_o_tch_tch)


2.8.51 Incoming TCH-TCH HO success (ho_47)

sum(msc_i_tch_tch+bsc_i_tch_tch)


2.9 Handover failure % (hfr)

2.9.1 Total HO failure %, S1 (hfr_1)

Use: Works best on the BTS level, but is usable on both tarea and cell level.

Experiences onuse: In a good network the value can be less than 3 p

cent, whereas in a very bad network values highthan 15 per cent may occur. When IUO is used, thformula shows high values due to highly failing intracell handovers between layers in congested cells.

Known problems: This formula emphasises the non-intra-cell handovesince they are counted twice. This causes no problon the cell level, whereas on the area level problemay occur.

Blocking is included. Blocking makes this indicatoshow high values especially in the case of IUO, butdoes not necessarily mean that there are soproblems.

HO failures100* --------------- % HO attempts

NTC TAN 0936/3 en



ofaner

nbe

Slle

ritme

Ot be

.g.but

HO attempts - successful HOs= 100 * --------------------------------- % HO attempts

successful HOs= 100 * (1- -------------- ) % HO attempts

sum(msc_i_succ_ho+msc_o_succ_ho+bsc_i_succ_ho+bsc_o_succ_ho+cell_succ_ho)= 100 * (1- --------------------------------------------------------- )% sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at+ msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at+ bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at+ bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at+ cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)


2.9.2 Total HO failure %, S1 (hfr_2)

Use: On the area or network level.

Experiences onuse: In a network gave the result of 8 % instead of 7 %

hfr_1 . In a good network the value can be less th3 per cent, while in a very bad network values highthan 15 per cent may occur.

If Directed Retry is enabled, the MS may, whecongestion of the source cell SDCCH occurs,moved from the best cell to a worse one. Then the Mtries to make a handover back but fails if the first ceis still congested. This leads to incrementation of thHO failure ratio.

Known problems: Blocking is included. Blocking makes this indicatoshow high values especially in the case of IUO, butdoes not necessarily mean that there are sotechnical problems.

Calls that are cleared by the MS user during the Hprocess increment the attempt counters but cannocompensated in the numerator. (XX2)

HO that is interrupted due to another procedure (eassignment) increments the attempt counterscannot be compensated in the numerator.(XX3)

HO failures

100* --------------- %

HO attempts

HO attempts - successful HOs

= 100 * --------------------------------- %

HO attempts

NTC TAN 0936/3 en



l to

successful HOs

= 100 * (1- -------------- ) %

HO attempts

sum(msc_o_succ_ho + bsc_o_succ_ho + cell_succ_ho) + XX2+ XX3

= 100 * (1- --------------------------------------------------------- )%

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at+

bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at+

cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)


p_nbsc_ho

2.9.3 Intra-cell HO failure share, S1 (hfr_3a)

Use: On the BTS level. The results are equal tohfr_3c .

Intra-cell HO failures

100* (--------------------------------------) %

All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch-at)

-sum(cell_succ_ho)

= 100* (--------------------------------------------------------------)%





+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


p_nbsc_ho

2.9.4 Intra-cell HO failure share, S1 (hfr_3b)

Use: On the area or network level. The results are equahfr_3d .

...... Intra-cell HO failures

100* (--------------------------------------) %

All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch-at)

-sum(cell_succ_ho)

= 100* (--------------------------------------------------------------)%

sum(msc_o_tch_tch_at + msc_o_sdcch_tch_at+ msc_o_sdcch_at)




p_nbsc_ho

NTC TAN 0936/3 en



l to

2.9.5 Intra-cell HO failure share, S1 (hfr_3c)

Use: On the BTS level. The results are equal tohfr_3a .


100* (--------------------------------------) %

All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)

- sum(cell_tch_tch+cell_sdcch_tch+cell_sdcch)

= 100* (--------------------------------------------------------------)%







p_nbsc_ho

2.9.6 Intra-cell HO failure share, S1 (hfr_3d)

Use: On the area or network level. The results are equahfr_3b .


100* (--------------------------------------) %

All HO attempts

sum(cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)

- sum(cell_tch_tch+cell_sdcch_tch+cell_sdcch)

= 100* (------------------------------------------------------------) %





p_nbsc_ho

2.9.7 Incoming MSC ctrl HO failure share, S1 (hfr_4)

MSC controlled incoming HO successes

100* (1- --------------------------------------) %

MSC controlled incoming HO attempts

sum(a.msc_i_tch_tch+a.msc_i_sdcch_tch+a.msc_i_sdcch)

= 100* (1- ---------------------------------------------------------) %

sum(a.msc_i_tch_tch_at+a.msc_i_sdcch_tch_at+a.msc_i_sdcch_at)


p_nbsc_ho

NTC TAN 0936/3 en



l to

2.9.8 Incoming MSC ctrl HO failure share, S1 (hfr_4a)

Use: On the BTS level.

MSC controlled incoming HO failures

100* (--------------------------------------) %

All HO attempts

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch-at)

-sum(msc_i_succ_ho)

= 100* (------------------------------------------------------------) %







p_nbsc_ho

2.9.9 Incoming MSC ctrl HO failure share, S1 (hfr_4b)



100* (--------------------------------------) %

All HO incoming attempts

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch-at)

-sum(msc_i_succ_ho)

= 100* (------------------------------------------------------------) %





p_nbsc_ho

2.9.10 Incoming MSC ctrl HO failure share, S1 (hfr_4c)



100* (--------------------------------------) %

All HO attempts


- sum(msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)

= 100* (--------------------------------------------------------------)%





NTC TAN 0936/3 en



l to

l to



p_nbsc_ho

2.9.11 Incoming MSC ctrl HO failure share, S1 (hfr_4d)



100* (--------------------------------------) %

All HO incoming attempts


- sum(msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)

= 100* (------------------------------------------------------------) %





p_nbsc_ho

2.9.12 Outgoing MSC ctrl HO failure share, S1 (hfr_5a)


MSC controlled outgoing HO failures

100* (--------------------------------------) %

All HO attempts

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch-at)

-sum(msc_o_succ_ho)

= 100* (------------------------------------------------------------) %







p_nbsc_ho

2.9.13 Outgoing MSC ctrl HO failure share, S1 (hfr_5b)



100* (--------------------------------------) %

All HO outgoing attempts

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch-at)

-sum(msc_o_succ_ho)

NTC TAN 0936/3 en



l to

= 100* (------------------------------------------------------------) %





p_nbsc_ho

2.9.14 Outgoing MSC ctrl HO failure share, S1 (hfr_5c)



100* (--------------------------------------) %

All HO attempts


- sum(msc_o_tch_tch+msc_o_sdcch_tch+msc_o_sdcch)

= 100* (--------------------------------------------------------------)%







p_nbsc_ho

2.9.15 Outgoing MSC ctrl HO failure share, S1 (hfr_5d)



100* (--------------------------------------) %

All HO outgoing attempts



= 100* (------------------------------------------------------------) %





p_nbsc_ho

2.9.16 Incoming BSC ctrl HO failure share, S1 (hfr_6)

BSC controlled incoming HO successes

100* (1- --------------------------------------) %

BSC controlled incoming HO attempts

sum(a.bsc_i_tch_tch+a.bsc_i_sdcch_tch+a.bsc_i_sdcch)

= 100* (1- ---------------------------------------------------------) %

NTC TAN 0936/3 en



l to

sum(a.bsc_i_tch_tch_at+a.bsc_i_sdcch_tch_at+a.bsc_i_sdcch_at)


p_nbsc_ho

2.9.17 Incoming BSC ctrl HO failure share, S1 (hfr_6a)


BSC controlled incoming HO failures

100* (--------------------------------------) %

All HO attempts

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch-at)

-sum(bsc_i_succ_ho)

= 100* (-----------------------------------------------------------) %







p_nbsc_ho

2.9.18 Incoming BSC ctrl HO failure share, S1 (hfr_6b)



100* (--------------------------------------) %

All incoming HO attempts

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch-at)

-sum(bsc_i_succ_ho)

= 100* (------------------------------------------------------------) %





p_nbsc_ho

2.9.19 Incoming BSC ctrl HO failure share, S1 (hfr_6c)



100* (--------------------------------------) %

All HO attempts


- sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)

= 100* (------------------------------------------------------------) %


NTC TAN 0936/3 en



l to






p_nbsc_ho

2.9.20 Incoming BSC ctrl HO failure share, S1 (hfr_6d)



100* (--------------------------------------) %

All incoming HO attempts


- sum(bsc_i_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)

= 100* (------------------------------------------------------------) %





p_nbsc_ho

2.9.21 Outgoing BSC ctrl HO failure share, S1 (hfr_7)

BSC controlled outgoing HO successes

100* (1- --------------------------------------) %

BSC controlled outgoing HO attempts

sum(a.bsc_o_tch_tch+a.bsc_o_sdcch_tch+a.bsc_o_sdcch)

= 100* (1- ---------------------------------------------------------) %

sum(a.bsc_o_tch_tch_at+a.bsc_o_sdcch_tch_at+a.bsc_o_sdcch_at)


p_nbsc_ho

2.9.22 Outgoing BSC ctrl HO failure share, S1 (hfr_7a)


BSC controlled outgoing HO failures

100* (--------------------------------------) %

All HO attempts

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch-at)

-sum(bsc_o_succ_ho)

= 100* (------------------------------------------------------------) %






NTC TAN 0936/3 en



l to

l to


p_nbsc_ho

2.9.23 Outgoing BSC ctrl HO failure share, S1 (hfr_7b)



100* (--------------------------------------) %

All HO attempts

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch-at)

-sum(bsc_o_succ_ho)

= 100* (-----------------------------------------------------------) %





p_nbsc_ho

2.9.24 Outgoing BSC ctrl HO failure share, S1 (hfr_7c)



100* (--------------------------------------) %

All HO attempts


- sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)

= 100* (------------------------------------------------------------) %







p_nbsc_ho

2.9.25 Outgoing BSC ctrl HO failure share, S1 (hfr_7d)



100* (--------------------------------------) %

All HO attempts


- sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)

NTC TAN 0936/3 en



= 100* (--------------------------------------------------------------)%





p_nbsc_ho

2.9.26 Internal inter HO failure %, S4 (hfr_8)

sum(int_inter_ho_source_fail)

100* (-----------------------------------------------) %

sum(int_inter_ho_source_fail+int_inter_ho_succ)


p_nbsc_service

2.9.27 Internal intra HO failure %, S4 (hfr_9)

sum(int_intra_ho_source_fail)

100* (-----------------------------------------------) %

sum(int_intra_ho_source_fail+int_intra_ho_succ)


p_nbsc_service

2.9.28 External source HO failure %, S4 (hfr_10)

sum(ext_ho_source_fail)

100* (-----------------------------------------------) %

sum(ext_ho_source_fail+ ext_ho_source_succ)


p_nbsc_service

2.9.29 HO failure % from super to regular, S4 (hfr_12)

Use: Ratio of all other failures than ’blocked’ to all HOattempts from super to regular TRX.

sum(ho_fail_to_reg_due_ret+ ho_fail_to_reg_ms_lost+ho_fail_to_reg_freq)

100* (-----------------------------------------------------------) %

sum(ho_att_to_reg_freq)


p_nbsc_underlay

2.9.30 HO failure % from regular to super, S4 (hfr_13)

sum(ho_fail_from_reg_due_ret+ ho_fail_from_reg_ms_lost+ho_fail_from_reg_freq)

100* (--------------------------------------------------------------) %

sum(ho_att_from_reg_freq)

NTC TAN 0936/3 en



er

n

ar


p_nbsc_underlay

2.9.31 Share of HO failures from regular to super due toreturn, S4 (hfr_14)

sum(ho_fail_from_reg_due_ret)

100* (-------------------------------------------------------------) %



p_nbsc_underlay

2.9.32 Share of HO failures from regular to super due to MSlost, S4 (hfr_15)

Use: Ratio of ’MS Lost’ failures to all HO attempts(blocked HOs excluded) in HOs from regular to supTRX.

sum(ho_fail_from_reg_ms_lost)

100* (-----------------------------------------------------------) %



p_nbsc_underlay

2.9.33 Share of HO failures from regular to super due toanother cause, S4 (hfr_16)

Use: Ratio of any other HO failures than ’return’ and ’MSlost’ to all HO attempts (blocked HOs excluded) iHOs from regular to super TRX.

sum(ho_fail_from_reg_freq)

100* (--------------------------------------------------------------) %



p_nbsc_underlay

2.9.34 Share of HO failures from super to regular due toreturn, S4 (hfr_17)

Use: Ratio of ’return’ HO failures to all HO attempts(blocked HOs excluded) in HOs from super to regulTRX.

sum(ho_fail_to_reg_due_ret)

100* (----------------------------------------------------------) %

NTC TAN 0936/3 en



ar

an

sar



p_nbsc_underlay

2.9.35 Share of HO failures from super to regular due to MSlost, S4 (hfr_18)

Use: Ratio of ’MS lost’ HO failures to all HO attempts(blocked HOs excluded) in HOs from super to regulTRX.

sum(ho_fail_to_reg_ms_lost)

100* (--------------------------------------------------------------) %



p_nbsc_underlay

2.9.36 Share of HO failures from super to regular due toanother cause, S4 (hfr_19)

Experiences onuse: Includes HO failures due to any other reason th

’return’ and ’MS lost’.

Use: Ratio of ’Other cause’ HO failures to all HO attempt(blocked HOs excluded) in HOs from super to regulTRX.

sum(ho_fail_to_reg_freq)

100* (--------------------------------------------------------------) %



p_nbsc_underlay

2.9.37 SDCCH-SDCCH HO failure %, S2 (hfr_20)

Experiences onuse: It is better to look at MSC and BSC controlled

handover separately.

sum(msc_i_sdcch+ msc_o_sdcch

+ bsc_i_sdcch+ bsc_o_sdcch

+ cell_sdcch)

- sum(msc_i_sdcch_at + msc_o_sdcch_at

+ bsc_i_sdcch_at + bsc_o_sdcch_at

+ cell_sdcch_at)

100* (----------------------------------------------) %

sum(msc_i_sdcch_at + msc_o_sdcch_at

NTC TAN 0936/3 en



+ bsc_i_sdcch_at + bsc_o_sdcch_at

+ cell_sdcch_at)


p_nbsc_ho

2.9.38 SDCCH-TCH HO failure %, S2 (hfr_21)

Use: These are Directed Retry.

sum(msc_i_sdcch_tch+ msc_o_sdcch_tch

+ bsc_i_sdcch_tch+ bsc_o_sdcch_tch

+ cell_sdcch_tch)

- sum(msc_i_sdcch_tch_at + msc_o_sdcch_tch_at

+ bsc_i_sdcch_tch_at + bsc_o_sdcch_tch_at

+ cell_sdcch_tch_at)

100* (-----------------------------------------------------) %

sum(msc_i_sdcch_tch_at + msc_o_sdcch_tch_at

+ bsc_i_sdcch_tch_at + bsc_o_sdcch_tch_at

+ cell_sdcch_tch_at)


p_nbsc_ho

2.9.39 TCH-TCH HO failure %, S2 (hfr_22)

sum(msc_i_tch_tch+ msc_o_tch_tch

+ bsc_i_tch_tch+ bsc_o_tch_tch

+ cell_tch_tch)

- sum(msc_i_tch_tch_at + msc_o_tch_tch_at

+ bsc_i_tch_tch_at + bsc_o_tch_tch_at

+ cell_tch_tch_at)

100* (--------------------------------------------------) %

sum(msc_i_tch_tch_at + msc_o_tch_tch_at

+ bsc_i_tch_tch_at + bsc_o_tch_tch_at

+ cell_tch_tch_at)


p_nbsc_ho

2.9.40 SDCCH-SDCCH incoming HO failure %, S2 (hfr_23)

sum(msc_i_sdcch_at+ bsc_i_sdcch_at) - sum(msc_i_sdcch + bsc_i_sdcch)

100* --------------------------------------------------------------- %

sum(msc_i_sdcch_at+ bsc_i_sdcch_at)


p_nbsc_ho

2.9.41 SDCCH-SDCCH outgoing HO failure ratio, S2(hfr_24)

sum(msc_o_sdcch_at+ bsc_o_sdcch_at) - sum(msc_o_sdcch + bsc_o_sdcch)

100* ---------------------------------------------------------------- %

sum(msc_o_sdcch_at+ bsc_o_sdcch_at)

NTC TAN 0936/3 en




p_nbsc_ho

2.9.42 SDCCH-TCH incoming HO failure %, S2 (hfr_25)

sum(msc_i_sdcch_tch_at+ bsc_i_sdcch_tch_at)- sum(msc_i_sdcch_tch+ bsc_i_sdcch_tch)

100* (--------------------------------------------------------------) %

sum(msc_i_sdcch_tch_at+ bsc_i_sdcch_tch_at)


p_nbsc_ho

2.9.43 SDCCH-TCH outgoing HO failure %, S2 (hfr_26)

sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at) - sum(msc_o_sdcch_tch+ bsc_o_sdcch_tch)

100* ---------------------------------------------------------------- %

sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at)


p_nbsc_ho

2.9.44 TCH-TCH incoming HO failure %, S2 (hfr_27)

sum(msc_i_tch_tch_at+ bsc_i_tch_tch_at) - sum(msc_i_tch_tch+ bsc_i_tch_tch)

100* -------------------------------------------------------------- %

sum(msc_i_tch_tch_at+ bsc_i_tch_tch_at)


p_nbsc_ho

2.9.45 TCH-TCH outgoing HO failure %, S2 (hfr_28)

sum(msc_o_tch_tch_at+ bsc_o_tch_tch_at) - sum(msc_o_tch_tch+ bsc_o_tch_tch)

100* --------------------------------------------------------------- %

sum(msc_o_tch_tch_at+ bsc_o_tch_tch_at)


p_nbsc_ho

2.9.46 MSC ctrl HO failure %, blocking (hfr_29)

100* msc_o_fail_lack/(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


p_nbsc_ho

2.9.47 MSC ctrl HO failure %, not allowed (hfr_30)

100* msc_o_not_allwd /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)

NTC TAN 0936/3 en



es


p_nbsc_ho

2.9.48 MSC ctrl HO failure %, return to old (hfr_31)

100* msc_o_fail_ret /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


2.9.49 MSC ctrl HO failure %, call clear (hfr_32)

100* msc_o_call_clr /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


2.9.50 MSC ctrl HO failure %, end HO (hfr_33)

100* msc_o_end_of_ho /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


2.9.51 MSC ctrl HO failure %, end HO BSS (hfr_34)

100* msc_o_end_ho_bss /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


2.9.52 MSC ctrl HO failure %, wrong A interface (hfr_35)

Use: Relates to congestion of A interface pool resourcdetected by BSC.

100* msc_controlled_out_ho /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


2.9.53 MSC ctrl HO failure %, adjacent cell error (hfr_36)

100* msc_o_adj_cell_id_err_c /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


NTC TAN 0936/3 en



es

2.9.54 BSC ctrl HO failure %, blocking (hfr_37)

100* bsc_o_fail_lack /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


2.9.55 BSC ctrl HO failure %, not allowed (hfr_38)

100* bsc_o_not_allwd /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


2.9.56 BSC ctrl HO failure %, return to old (hfr_39)

100* bsc_o_fail_ret /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


2.9.57 BSC ctrl HO failure %, call clear (hfr_40)

100* bsc_o_call_clr /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


2.9.58 BSC ctrl HO failure %, end HO (hfr_41)

100* bsc_o_end_of_ho /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


2.9.59 BSC ctrl HO failure %, end HO BSS (hfr_42)

100* bsc_o_end_ho_bss /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


2.9.60 BSC ctrl HO failure %, wrong A interface (hfr_43)


100* bsc_o_unsucc_a_int_circ_type /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


NTC TAN 0936/3 en



2.9.61 BSC ctrl HO drop call %, (hfr_44)

100* bsc_o_drop_calls /(bsc_o_sdcch_at+bsc_o_sdcch_tch_at+bsc_o_tch_tch_at)


2.9.62 Intra-cell HO failure %, cell_fail_lack (hfr_45)

100* cell_fail_lack /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


2.9.63 Intra-cell HO failure %, not allowed (hfr_46)

100* cell_not_allwd /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


2.9.64 Intra-cell HO failure %, return to old (hfr_47)

100* cell_fail_ret /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


2.9.65 Intra-cell HO failure %, call clear (hfr_48)

100* cell_call_clr /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


2.9.66 Intra-cell HO failure %, MS lost (hfr_49)

100* cell_fail_move /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


2.9.67 Intra-cell HO failure %, BSS problem (hfr_50)

100* cell_fail_bss /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


2.9.68 Intra-cell HO failure %, drop call (hfr_51)

100* cell_drop_calls /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


NTC TAN 0936/3 en



es

2.9.69 HO failure % to adjacent cell (hfr_52)

100*( sum(ho_att_to_adj - ho_succ_to_adj)/ sum(ho_att_to_adj)

Counters from table(s):p_nbsc_ho_adj

2.9.70 HO failure % from adjacent cell (hfr_53)

100*( sum(ho_att_from_adj - ho_succ_from_adj)/ sum(ho_att_from_adj)


2.9.71 HO failure %, blocking excluded (hfr_54a)


/* all HO attempts */

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at

+bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at

+cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at)

/*successful handovers */

-sum(msc_o_succ_ho +bsc_o_succ_ho+cell_succ_ho)

/* handovers failing due to blocking */

-sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)

100 * ------------------------------------------------------%






p_nbsc_ho

2.9.72 HO failure % due to radio interface blocking (hfr_55)



sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)

100 * ------------------------------------------------------%






p_nbsc_ho

2.9.73 Intra-cell HO failure %, wrong A interface (hfr_56)


NTC TAN 0936/3 en



al

Thee

ent)the

al

Thee

100* sum(ho_unsucc_a_int_circ_type)/(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


p_nbsc_ho

2.9.74 Intra-cell HO failure % (hfr_57)

Intra-cell HO successes

100* (1- -------------------------) %

Intra-cell HO attempts

sum(a.cell_tch_tch + a.cell_sdcch_tch+ a.cell_sdcch)

= 100* (1- ---------------------------------------------------------) %

sum(a.cell_tch_tch_at + a.cell_sdcch_tch_at + a.cell_sdcch_at)


p_nbsc_ho

2.9.75 HO failures to target cell, S6 (hfr_58)

Use: On the adjacency level. Gives failure % of the re(unblocked) HO attempts.

Known problems: Not accurate because of:

1. Calls that are cleared by MS user during the HO process.ho_att_to_adj counter is incremented and cannot bcompensated in the numerator.

2. HO that is interrupted due to other procedure (e.g. assignmincrements attempt counters but cannot be compensated innumerator.

sum(ho_att_to_adj-ho_succ_to_adj-ho_fail_res_to_adj)

100* -------------------------------------------------------- %

sum(ho_att_to_adj- ho_fail_res_to_adj)


p_nbsc_ho_adj

2.9.76 HO failures from target cell, S6 (hfr_59)

Use: On the adjacency level. Gives failure % of the re(unblocked) HO attempts.

Known problems: Not accurate because of:

1. Calls that are cleared by MS user during the HO process.ho_att_to_adj counter is incremented and cannot bcompensated in the numerator.

NTC TAN 0936/3 en



ent)the

2. HO that is interrupted due to other procedure (e.g. assignmincrements attempt counters but cannot be compensated innumerator.

sum(ho_att_from_adj-ho_succ_from_adj-ho_fail_res_from_adj)

100* ----------------------------------------------------------- %

sum(ho_att_from-adj- ho_fail_res_from_adj)


p_nbsc_ho_adj

2.10 Handover success % (hsr)

2.10.1 MSC controlled outgoing SDCCH-SDCCH HO success%, S1 (hsr_1)

100* sum(msc_o_sdcch) / sum(msc_o_sdcch_at) %


2.10.2 MSC controlled outgoing SDCCH-TCH HO success %,S1 (hsr_2)

100* sum(msc_o_sdcch_tch) / sum(msc_o_sdcch_tch_at) %


2.10.3 MSC controlled outgoing TCH-TCH HO success %, S1(hsr_3)

100* sum(msc_o_tch_tch) / sum(msc_o_tch_tch_at) %


2.10.4 BSC controlled outgoing SDCCH-SDCCH HO success%, S1 (hsr_4)

100* sum(bsc_o_sdcch) / sum(bsc_o_sdcch_at) %


2.10.5 BSC controlled outgoing SDCCH-TCH HO success %,S1 (hsr_5)

100* sum(bsc_o_sdcch_tch) / sum(bsc_o_sdcch_tch_at) %


NTC TAN 0936/3 en



2.10.6 BSC controlled outgoing TCH-TCH HO success %, S1(hsr_6)

100* sum(bsc_o_tch_tch) / sum(bsc_o_tch_tch_at) %


2.10.7 Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_7)

100* sum(cell_o_sdcch) / sum(cell_o_sdcch_at) %


2.10.8 Intra-cell SDCCH-TCH HO success %, S1 (hsr_8)

100* sum(cell_o_sdcch_tch) / sum(cell_o_sdcch_tch_at) %


2.10.9 Intra-cell TCH-TCH HO success %, S1 (hsr_9)

100* sum(cell_o_tch_tch) / sum(cell_o_tch_tch_at) %


2.10.10 MSC controlled incoming SDCCH-SDCCH HOsuccess %, S1 (hsr_10)

100* sum(msc_i_sdcch) / sum(msc_i_sdcch_at) %


2.10.11 MSC controlled incoming SDCCH-TCH HO success%, S1 (hsr_11)

100* sum(msc_i_sdcch_tch) / sum(msc_i_sdcch_tch_at) %


2.10.12 MSC controlled incoming TCH-TCH HO success %,S1 (hsr_12)

100* sum(msc_i_tch_tch) / sum(msc_i_tch_tch_at) %


NTC TAN 0936/3 en



2.10.13 BSC controlled incoming SDCCH-SDCCH HO success%, S1 (hsr_13)

100* sum(bsc_i_sdcch) / sum(bsc_i_sdcch_at) %


2.10.14 BSC controlled incoming SDCCH-TCH HO success %,S1 (hsr_14)

100* sum(bsc_i_sdcch_tch) / sum(bsc_i_sdcch_tch_at) %


2.10.15 BSC controlled incoming TCH-TCH HO success %, S1(hsr_15)

100* sum(bsc_i_tch_tch) / sum(bsc_i_tch_tch_at) %


2.10.16 BSC controlled incoming HO success %, S1 (hsr_16)

100* sum(bsc_i_succ_ho) /sum(bsc_i_sdcch_at + bsc_i_sdcch_tch_at + bsc_i_tch_tch_at) %


2.10.17 MSC controlled incoming HO success %, S1 (hsr_17)

100* sum(bsc_i_succ_ho) /sum(bsc_i_sdcch_at + bsc_i_sdcch_tch_at + bsc_i_tch_tch_at) %


2.10.18 Incoming HO success %, S1 (hsr_18)

100* sum(msc_i_tch_tch+bsc_i_tch_tch) /sum(msc_i_tch_tch_at +bsc_i_tch_tch_at) %


2.10.19 Outgoing HO success %, S1 (hsr_19)

100* sum(msc_o_tch_tch+bsc_o_tch_tch) /sum(msc_o_tch_tch_at +bsc_o_tch_tch_at) %


NTC TAN 0936/3 en



)

cy

2.10.20 Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20

sum(cell_sdcch)

100* ------------------ %

sum(cell_sdcch_at)


p_nbsc_ho

2.10.21 Intra-cell SDCCH-TCH HO success %, S1 (hsr_21)

sum(cell_sdcch_tch)

100* --------------------- %

sum(cell_sdcch_tch_at)


p_nbsc_ho

2.10.22 Intra-cell TCH-TCH HO success %, S1 (hsr_22)

sum(cell_tch_tch)

100* --------------------- %

sum(cell_tch_tch_at)


p_nbsc_ho

2.11 Handover failures (hof)

2.11.1 Outgoing HO failures due to lack of resources (hof_1)

sum(BSC_o_fail_lack+MSC_o_fail_lack)


2.11.2 Incoming HO failures due to lack of resources (hof_2)

sum(BSC_i_fail_lack+MSC_i_fail_lack)


2.11.3 TCH HO failures when return to old channel wassuccessful (hof_3)

Known problems: Due to the mapping of different causes the accuramay be low.

Handovers failed in going to new channel - Handovers failed to return toold channel

= sum(tch_rf_new_ho + tch_abis_fail_new + tch_a_if_fail_new +tch_tr_fail_new)

NTC TAN 0936/3 en



cy

- sum(tch_rf_old_ho + tch_abis_fail_old + tch_a_if_fail_old +tch_tr_fail_old)


p_nbsc_traffic

2.11.4 SDCCH HO failures when return to old channel wassuccessful (hof_4)

Known problems: Due to the mapping of different causes the accuramay be low.

Handovers failed in going to new channel - Handovers failed to return toold channel

= sum(sdcch_rf_new_ho + sdcch_abis_fail_new + sdccha_if_fail_new +sdcch_tr_fail_new)

- sum(sdcch_rf_old_ho + sdcch_abis_fail_old + sdccha_if_fail_old +sdcch_tr_fail_old)


p_nbsc_traffic

2.11.5 MSC incoming HO failures (hof_5)

HO attempts - successful HO

= sum(msc_i_tch_tch_at+msc_i_tch_tch_at+msc_i_sdcch_at

- msc_i_tch_tch+msc_i_sdcch_tch+msc_i_sdcch)


p_nbsc_ho

2.11.6 MSC outgoing HO failures (hof_6)




p_nbsc_ho

2.11.7 MSC outgoing HO failures (hof_6a)

sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at - msc_o_succ_ho)


2.11.8 BSC incoming HO failures (hof_7)

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at

- bsc_i_succ_ho)


p_nbsc_ho

NTC TAN 0936/3 en



2.11.9 BSC incoming HO failures (hof_7a)

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at - bsc_i_succ_ho)


2.11.10 BSC outgoing HO failures (hof_8)


sum(bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)


p_nbsc_ho

2.11.11 BSC outgoing HO failures (hof_8a)

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at

- bsc_o_succ_ho)


p_nbsc_ho

2.11.12 Intra-cell HO failures (hof_9a)

sum(cell_tch_tch_at+cell_sdcch_at+cell_sdcch_tch-cell_tch_tch-cell_sdcch-cell_sdcch_tch)


p_nbsc_ho

2.11.13 Failed outgoing HO, return to old (hof_10)

sum(msc_o_fail_ret + bsc_o_fail_ret)


2.11.14 Outgoing HO failures (hof_12)

Outgoing HO attempts - Outgoing HO successes

= sum(msc_o_tch_tch_at+msc_o_sdcch_tch_at+msc_o_sdcch_at

+ bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at)

- sum(msc_o_succ_ho+ bsc_o_succ_ho)


p_nbsc_ho

2.11.15 Intra-cell HO failure, return to old channel (hof_13)

sum(cell_fail_ret)


NTC TAN 0936/3 en



stisSy 1

ife

ecyod

es

2.11.16 Intra-cell HO failure, drop call (hof_14)

sum(cell_drop_calls)


2.11.17 Incoming HO failures (hof_15)

Incoming HO attempts - Incoming HO suucesses

= sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at

+ bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)

- sum(msc_i_succ_ho+ bsc_i_succ_ho)


p_nbsc_ho

2.12 Interference (itf)

2.12.1 UL interference, BTS level, S1 (itf_1)

Use: UL interference is measured as the time-out of loweband 1 (band 0 in BSC terminology). Band 10defined by boundaries 0 and 1 which are BTparameters. Boundary 0 is fixed, whereas boundarcan be set.

Experiences onuse: UL interference alone is not a reliable quality factor

IUO is used. In IUO cells the UL interference can bhigh but the quality is still good.

Known problems: This formula is on the BTS level, whereas thinterference problems are met on the frequen(TRX) level. This means that the accuracy is not goif there is more than one TRX in a cell.

If band 1 is defined as exceptionally wide, it becomdifficult to see the interference.

sum(ave_idle_f_TCH_1/res_av_denom4)

100x (1- ---------------------------------------------------------- ) %

sum(ave_idle_f_TCH_1/res_av_denom4+ ave_idle_f_TCH_2/res_av_denom5+ ave_idle_f_TCH_3/res_av_denom6+ ave_idle_f_TCH_4/res_av_denom7+ ave_idle_f_TCH_5/res_av_denom8)


p_nbsc_res_avail

NTC TAN 0936/3 en



hrthe

ife

ddms

be1)

2.12.2 Idle TSL percentage of time in band X, TRX level, IUO,S4 (itf_2)

Experiences onuse: In IUO cells the UL interference can show hig

values but the UL quality is still excellent. The biggethe values are in bands towards band 5, the worseinterference.

sum(ave_full_tch_ifX)

100x (------------------------------------------------------------ ) %

sum(ave_full_tch_if1 + ave_full_tch_if2 + ave_full_tch_if3

+ ave_full_tch_if4 + ave_full_tch_if5)


p_nbsc_underlay

2.12.3 UL interference from IUO, TRX level, S4 (itf_3)

Experiences onuse: UL interference alone is not a reliable quality factor

IUO is used. In IUO cells the UL interference can bhigh but the quality is still good.

Known problems: There are more than one TRX in a cell.

sum(ave_full_tch_if1)

100x (1 - ---------------------------------------------------------- ) %

sum(ave_full_tch_if1 + ave_full_tch_if2 + ave_full_tch_if3

+ ave_full_tch_if4 + ave_full_tch_if5)


p_nbsc_underlay

2.12.4 UL interference from Power Control, TRX level, S6(itf_4)

Use: BTS reports interference of each TCH as bannumber (0-4, where 0 is the lowest and banboundaries are defined as cell parameters). BSC suup the band numbers (ave_sum_idle_ch_interf ) as well as the numberof TCHs reported (ave_sum_idle_tch_per_trx ), and from thesefigures an average interference band (0-4) cancalculated. Average interference is shifted by 1 (+to comply with band numbers 1-5.

sum(ave_sum_idle_ch_interf)/sum(ave_sum_idle_tch_per_trx)+1

Counters from table(s):p_nbsc_power

NTC TAN 0936/3 en



r

e

he

to

fore

ell

heand

2.13 Congestion (cngt)

2.13.1 TCH congestion time, S1 (cngt_1)

Experiences onuse: Useful to follow on the area level. Should give highe

values than SDCCH congestion.

sum(tch_cong_time/100)

Counters from table(s):p_nbsc_res_availunit: seconds

2.13.2 SDCCH congestion time, S1 (cngt_2)

Experiences onuse: Useful to follow on the area level. Should giv

smaller values than TCH congestion.

sum(sdcch_cong_time/100)

Counters from table(s):p_nbsc_res_availunit: seconds

2.14 Queuing (que)

2.14.1 Queued, served TCH call requests % (que_1)

Use: Indicates the quota of TCH call requests seizing tTCH successfully after queuing.

Known problems: tch_qd_call_att is triggered butunsrv_qd_call_att is not if:

1. Call attempt is in the queue and while waiting is taken by DRanother cell. The formula shows as if the queuing took place.

2. If the call is lost for some other reason (e.g. MS user hangs) bethe queuing timer expires.

The impact of this depends on queuing time and cparameter Directed Retry Time Limit Min.

A call is taken from the queue to DR as soon as tDR target cell list is ready. To get an accurate ratio,additional counter XX1 would be needed (queueattempts taken to DR).

sum(a. tch_qd_call_att-XX1-a.unsrv_qd_call_att)

100* -------------------------------------------- %

sum(a.tch_call_req)

NTC TAN 0936/3 en



he

he


p_nbsc_trafficXX1 is the number of calls taken from queue to DR.

2.14.2 Queued, served TCH HO requests % (que_2)

Known problems: tch_qd_ho_att is triggered butunsrv_qd_ho_att is not if a call for some reason islost (the MS user is hanging, for example) before tqueuing timer expires.

sum(a. tch_qd_ho_att-a.unsrv_qd_ho_att)

100* ------------------------------------------------- %

sum(a.tch_request-a.tch_call_req-a.tch_fast_req)


p_nbsc_traffic

2.14.3 Queued, served TCH HO requests %, (que_2a)

Known problems: tch_qd_ho_att is triggered butunsrv_qd_ho_att is not if a call for some reason islost (the MS user is hanging, for example) before tqueuing timer expires.

sum(a. tch_qd_ho_att-a.unsrv_qd_ho_att)

100* ------------------------------------------------- %


-Sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type)


a = p_nbsc_traffic

b = p_nbsc_handover

2.14.4 Successful queued TCH requests (que_3)

sum(tch_qd_call_att-unsrv_qd_call_att)


2.14.5 Successful non-queued TCH requests (que_4)

sum(tch_norm_seiz)-sum(tch_qd_call_att-unsrv_qd_call_att)


NTC TAN 0936/3 en



hes

2.14.6 Successful queued TCH HO requests (que_5)

sum(tch_qd_ho_att-unsrv_qd_ho_att)


2.14.7 Successful non-queued TCH HO requests (que_6)

sum(tch_ho_seiz)-sum(tch_qd_ho_att-unsrv_qd_ho_att)


2.14.8 Non-queued, served TCH call requests % (que_7)

Use: Indicates the quota of TCH call requests seizing tTCH successfully straight without queuing. DR iexcluded (its impact is seen indr_3 ).

sum(a.tch_norm_seiz-(a.tch_qd_call_att-a.unsrv_qd_call_att))

100* --------------------------------------------------------- %

sum(a.tch_call_req)


p_nbsc_traffic

2.14.9 Non-queued, served TCH HO requests % (que_8)

sum(a.tch_ho_seiz-(a.tch_qd_ho_att-a.unsrv_qd_ho_att))

100* ------------------------------------------------- %



p_nbsc_traffic

2.14.10 Non-queued, served TCH HO requests %, (que_8a)

Known problems: Seeque_2 .

sum(a.tch_ho_seiz-(a.tch_qd_ho_att-a.unsrv_qd_ho_att))

100* ------------------------------------------------- %


-Sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type)


a = p_nbsc_traffic

b = p_nbsc_handover

NTC TAN 0936/3 en



ogoto.y

s

2.15 Blocking (blck)

2.15.1 TCH raw blocking, S1 (blck_1)

Experiences onuse: Was earlier (beforeblck_8a ) widely used on the cell

and the area level.

Known problems: This PI does not take Directed Retry intconsideration. Rather, it shows only raw blockinincluding also HOs. Blocked HOs are normally not sserious because there are alternatives to goBlocked new calls can be lost calls if Directed Retris not in use.

sum(a.tch_req_rej_lack)

100* --------------------- %

sum(a.tch_request)


p_nbsc_traffic

2.15.2 SDCCH blocking %, S1 (blck_5)

Known problems: sdcch_busy_att is triggered also in the case of HOattempt if there are no free SDCCHs.

sum(a.SDCCH_busy_att)

100* ---------------------- %

sum(a.SDCCH_seiz_att)


p_nbsc_traffic

2.15.3 SDCCH real blocking %, S1 (blck_5a)

Known problems: sdcch_busy_att is triggered also in the case of HOattempt if there are no free SDCCHs.

sum(a.SDCCH_busy_att-a.tch_seiz_due_sdcch_con)

100* ----------------------------------------- %

sum(a.SDCCH_seiz_att)


p_nbsc_traffic

2.15.4 TCH raw blocking % on super TRXs, S4 (blck_6)

Note: Cannot be calculated by a simple SQL*Plustatement.

sum over super TRXs (a.tch_req_rej_lack)

100* ----------------------------------------- %

NTC TAN 0936/3 en



s

ls.lost

etre

iver

as

sum over super TRXs (a.tch_request)


p_nbsc_underlay

2.15.5 TCH raw blocking % on regular TRXs, S4 (blck_7)


sum over regular TRX (a.tch_req_rej_lack)

100* ----------------------------------------- %

sum over regular TRX (a.tch_request)


p_nbsc_underlay

2.15.6 TCH call blocking, before DR, S2 (blck_8)

Experiences onuse: Shows the blocking if DR is not used.

TCH call requests rejected due to lack of resourcesor routed by DR to another cell

100* ------------------------------------------------------------- % =

all TCH call requests

sum(a.tch_call_req-a.tch_norm_seiz)

100* -------------------------------- %

sum(a.tch_call_req)


p_nbsc_traffic

2.15.7 TCH call blocking %, DR compensated, S2 (blck_8b)

Use: On the cell level should appear in the busiest celThe cell needs an urgent capacity extension or haspart of its capacity due to a fault.

It is the blocking rate that the customers will noticwhen they are driving in the mobile environmencaused by the lack of radio resources. It is therefoone of the most critical KPIs.

Experiences onuse: On the area level there is not yet a target value to g

(except that 0 % is the best). On the cell level, foexample, 2 % blocking on busy hour has been useda criterion for design.

NTC TAN 0936/3 en



ge

gtern

gnel

A-is(

SCrto

y.le

Rt -llA-

Known problems: 1) This blocking shows also situations when blockinis caused by a fault in the BTS - not only purblocking caused by high traffic.

Note:

2) If Trunk Reservation is used, HO and Call blockincannot be counted precisely (there is only one counfor the case of Trunk Reservation InvocatioRefused).

3) The ratio can show too high values in the followincase: TCH assignment fails if the requested chantype is not found in the A-interface circuit pool. Inthis case tch_norm_seiz is not triggered buttch_call_req is, i.e. this attempt in blck_8b isconsidered a blocked call.

Anyhow, BSC requests the MSC to change theinterface circuit pool. MSC can then decide if thereanother assignment request or call clearclear_command ).

The second request may again fail or succeed. In Bthe TCH_REJ_DUE_REQ_CH_A_IF_CRC counteis triggered every time the channel request fails duethe above-mentioned reason.

If Nokia MSC is used, there can be only one retrWith another vendor’s MSC there can be multipretrys.

The actual situation when this can be met is if EF(enhanced full rate) codec is the primary choice buthe selected A-interface circuit supports only FuRate- there are free circuits supporting EFR in theinterface

TCH call requests rejected due to lack of res. or saved by DR

- successful DR

100* ------------------------------------------------------------- % =

all TCH call requests


- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch)

100* ---------------------------------------------------------- %

sum(a.tch_call_req)


a = p_nbsc_traffic

NTC TAN 0936/3 en



llis

heart

to

ivelerr

eddin

ge

gtern

b = p_nbsc_handover

2.15.8 TCH call blocking %, DR compensated, EFR excluded,S5 (blck_8c)

Use: It is the failed call attempts that the MS user winotice, caused by the lack of radio resources. Itthereforeone of the most critical KPIs.

On the cell level may appear in the busiest cells. Tcell needs an urgent capacity extension or has lost pof capacity due to a fault. An MS user will usuallyhear three beep tones when the call is rejected dueblocking.


(except that the trend should be towards a smalvalue, 0 % being the best). On the cell level, foexample, 2 % blocking on Busy Hour has been usas a criterion for design. This KPI can be followestatistically, for example, as the number of cellswhich the value exceeds the given threshold.


Note:


New TCH call requests that are blocked

100*----------------------------------------%

All new call requests


- successful DR

- (Aif circuit pool seizure rejections (blocking or mismatch)

- Aif circuit pool handover failures)

100* ------------------------------------------------------------- % =

all TCH call requests (includes retries due to mismatch)





NTC TAN 0936/3 en



llis

heart

to

ivelerras

in

ge

gtern

- sum(a.tch_rej_due_req_ch_a_if_crc; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type; Aif circuit pool handoverfailures

+b.msc_controlled_in_ho

+b.ho_unsucc_a_int_circ_type))

100* ---------------------------------------------------------- %

sum(a.tch_call_req)


-(b.bsc_i_unsucc_a_int_circ_type; Aif circuit pool handoverfailures




a = p_nbsc_traffic

b = p_nbsc_handover

2.15.9 TCH call blocking %, DR and DAC compensated, EFRexcluded, S5 (blck_8d)

Use: It is the failed call attempts that the MS user winotice, caused by the lack of radio resources. Itthereforeone of the most critical KPIs.

On the cell level may appear in the busiest cells. Tcell needs an urgent capacity extension or has lost pof capacity due to a fault. An MS user will usuallyhear three beep tones when the call is rejected dueblocking.


(except that the trend should be towards a smalvalue, 0% being the best). On the cell level, foexample, 2% blocking on Busy Hour has been useda criterion for design. This KPI can be followedstatistically, for example, as the number of cellswhich the value exceeds the given threshold.


Note:


100-csf_3l =

NTC TAN 0936/3 en



TRX

ay

New TCH call requests that are blocked

100*----------------------------------------%

All new call requests


- successful DR



100* ------------------------------------------------------------- % =

all TCH call requests (includes retries due to mismatch)






-(b.bsc_i_unsucc_a_int_circ_type; Aif circuit pool HO failures



+sum(a.tch_succ_seiz_for_dir_acc) ;ref.2

100* ---------------------------------------------------------- %

sum(a.tch_call_req)






a = p_nbsc_traffic

b = p_nbsc_handover

Ref.2. Compensation needed since in case of Direct Access to super reusethe tch_norm_seiz is triggered in parallel withcell_sdcch_tch .

2.15.10 Blocked calls, S5 (blck_9b)

Use: Shows also situations when blocking is caused byfault in the BTS - not only blocking caused purely bhigh traffic.

TCH call requests rejected due to lack of res. or routed by DR to anothercell

- successful DR

- Rejections due to Aif circuit mismatch


- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch);inter-cell DR

- sum(b.cell_sdcch_tch); intra-cell DR in IUO

- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion




NTC TAN 0936/3 en



ay

TRX


a = p_nbsc_traffic

b = p_nbsc_handover

2.15.11 Blocked calls , S5 (blck_9c)

Use: Shows also situations when blocking is caused byfault in the BTS - not only blocking caused purely bhigh traffic.

TCH call requests rejected due to lack of res. or routed by DR to anothercell

- successful DR

- Rejections due to Aif circuit mismatch


- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch);inter-cell DR

- sum(b.cell_sdcch_tch); intra-cell DR in IUO

+ sum(a.succ_tch_seiz_for_dir_acc) ;ref.2

- sum(a.tch_rej_due_req_ch_a_if_crc ; Aif type mismatch or congestion

-(b.bsc_i_unsucc_a_int_circ_type ; Aif circuit pool HO failures




a = p_nbsc_traffic

b = p_nbsc_handover


2.15.12 Blocked TCH HOs, S2 (blck_10a)

Use: Replacesblck_10 .

sum(tch_request-tch_call_req-tch_fast_req-tch_ho_seiz)


2.15.13 Blocked TCH HOs, S5 (blck_10b)

Use: Replacesblck_10a .

sum(a.tch_request-a.tch_call_req-a.tch_fast_req-a.tch_ho_seiz)

-sum(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type)


a = p_nbsc_traffic

b = p_nbsc_ho

NTC TAN 0936/3 en



edd

gtern

.

edd

gtern

2.15.14 TCH HO blocking, S2 (blck_11a)

Known problems: 1) Shows also the situations when blocking is causby a fault in the BTS - not only blocking causepurely by high traffic.

Note:



100 * ------------------------------------------------------------- %

sum(tch_request-tch_call_req-a.tch_fast_req)


p_nbsc_traffic

2.15.15 TCH HO blocking without Q, S2 (blck_11b)

Use: Shows TCH HO blocking if queuing was not in use

Known problems: Seeque_2 (factor XX1).


+ sum(a.tch_qd_ho_att-XX1- unserv_qd_ho_att)

100 * ------------------------------------------------------------- %

sum(tch_request-tch_call_req-a.tch_fast_req)


p_nbsc_traffic

2.15.16 TCH HO blocking, S5 (blck_11c)

Known problems: 1) Shows also the situations when blocking is causby a fault in the BTS - not only blocking causepurely by high traffic.

Note:



NTC TAN 0936/3 en



orhe

ofeted


100 * ------------------------------------------------------------- %




a = p_nbsc_traffic

b = p_nbsc_ho

2.15.17 Blocked incoming and internal HO, S2 (blck_12)

Use: Usable with S4 and earlier.

sum(msc_i_fail_lack+ bsc_i_fail_lack + cell_fail_lack)


2.15.18 Blocked incoming and internal HO, S2 (blck_12a)

Use: On the area level with S5 and S6.

sum(msc_i_fail_lack+ bsc_i_fail_lack + cell_fail_lack +bsc_i_unsucc_a_int_circ_type + msc_controlled_in_ho +ho_unsucc_a_int_circ_type)


p_nbsc_ho

2.15.19 AG blocking, S1 (blck_13)

Use: A BSC sends to a BTS an immediate assignmentimmediate assignment rejected commands. If tAccess Grant (AG) buffer in the BTS is full, it willrespond with a delete indication. Thus the ratiodelete indications to the sum of immediatassignment and immediate assignment rejecdescribes the AG blocking.

100 * sum(del_ind_msg_rec)/ sum(imm_assgn_rej+imm_assgn_sent)

Counters from table(s):p_nbsc_res_access

2.15.20 FCS blocking, S5 (blck_14)

100 * sum(tch_seiz_att_due_sdcch_con-tch_seiz_due_sdcch_con)/sum(tch_seiz_att_due_sdcch_con %)


NTC TAN 0936/3 en



ot

ftere

2.15.21 Blocked SDCCH seizure attempts, S5 (blck_15)

All blocked - seizures to FACCH setup sum(sdcch_busy_att -tch_seiz_due_sdcch_con)


2.15.22 HO blocking % (blck_16a)

Use: On the area level with S4 or earlier.


-sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)

100 * ------------------------------------------------




+cell_tch_tch_at+cell_sdcch_tch_at+cell_sdcch_at


2.15.23 Handover blocking %, (blck_16b)

Use: On the area level with S5 and S6.

Known problems: If the required channel type (e.g. Full Rate) is navailable in intra-cell handover, thenho_unsucc_a_int_circ_type is triggered, butthe same channel may be seized successfully achanging the handover for external (A interfaccircuit changes).


sum(a.msc_i_fail_lack+a.bsc_i_fail_lack + cell_fail_lack+

+bsc_i_unsucc_a_int_circ_type+msc_i_unsucc_a_int_circ_type

+ho_unsucc_a_int_circ_type)

100 * ------------------------------------------------






2.15.24 Abis link blocking (blck_17)

There is no counter but an alarm: 2720 ’Telecom Link Overload’.

NTC TAN 0936/3 en



gngd.

rC.o

ngse

t

g isech.

2.15.25 Blocked FACCH call setup TCH requests, (blck_18)

sum(tch_seiz_att_due_sdcch_con - tch_seiz_due_sdcch_con)


2.15.26 Handover blocking to target cell, (blck_19)

100* sum(ho_fail_res_to_adj)/sum(ho_att_to_adj)


2.15.27 Handover blocking from target cell, (blck_20)

100* sum(ho_fail_res_from_adj)/sum(ho_att_from_adj)


2.16 Traffic (trf)

2.16.1 TCH traffic sum, S1 (trf_1)

Experiences onuse: If counted over one hour, erlang is shown. Countin

erlangs over a longer period requires that the erlavalues per hour are first counted and then average

Known problems: Shows slightly different values (around 3 % higheaccording to one study) than if counted from an MSThe reason for this is that in a BSC one call holds twTCHs for a short period in HOs.

The sampling period is 20 s which means that durithe period of one hour the number of used TCHchecked 180 times. This method is not accurate if wthink about short seizures and low traffic, bustatistically the results have been satisfactory.

Does not show calls going to voice mail.

Note:

The result represents technical traffic, not charged traffic because countinstarted when BSC seizes TCH. Includes some of signalling, ringing and spe

sum(ave_busy_tch / res_av_denom14)

Counters from table(s):p_nbsc_res_availUnit: Erlang hours if the measurement period is 1 hour.

NTC TAN 0936/3 en



he

SC

rator

ed.

2.16.2 TCH traffic sum, S1 (trf_1a)

Note: Seetrf_1 .

sum_over_area ( sum_over_BTS(ave_busy_tch)/sum_over_BTS(res_av_denom14) )

Counters from table(s):p_nbsc_res_avail

2.16.3 Average call length, S1 (trf_2d)

Use: On the area level gives you an idea about tbehaviour of the MS users.

Note:

In the numerator (a.ave_busy_tch / a.res_av_denom14 ) representstechnical traffic, not charged traffic, because counting is started when Bseizes TCH. Includes some of signalling, ringing and speech.

In the denominator there are also calls that are not answered. The numecounts both the A and B side in MS-MS calls, thus duplicating call time.

total TCH use time nbr of seconds in meas.period * average busy TCH

------------------- = -------------------------------------------------

number of calls number of calls

sum(period_duration*60* a.ave_busy_tch / a.res_av_denom14)

= ----------------------------------------------------------

sum(b.tch_norm_seiz) ;normal calls

+ sum(msc_i_sdcch_tch+ bsc_i_sdcch_tch + cell_sdcch_tch);DR calls

+ sum(a.tch_seiz_due_sdcch_con) ; FACCH call setup calls

a = p_nbsc_res_avail

b = p_bsc_traffic

c = p_nbsc_ho

2.16.4 TCH usage, S1 (trf_3)

Use: On the area level gives you an idea of how well thcapacity is used. Usable after S4 if half rate not use

used TCH

100 * ----------------------- %

available TCH

sum(a.ave_busy_tch/a.res_av_denom14)

= 100 * -------------------------------------------- %

sum(a.ave_avail_full_TCH/a.res_av_denom2)


p_nbsc_res_avail

NTC TAN 0936/3 en



e

f

fto

t

2.16.5 FTCH usage, S5 (trf_3b)

Use: On the area level gives you an idea of how well thcapacity is used. Use with S5 or later.

sum(a.ave_tch_busy_full)

= 100 * -------------------------------------------- %

sum(a.ave_avail_full_TCH/a.res_av_denom2)


p_nbsc_res_avail

2.16.6 Average SDCCH holding time, S1 (trf_4)

Use: The holding time may change due to modification othe timers or perhaps software.

Experiences onuse: The counters get 0 values if the BTS is locked.

sum(ave_sdcch_hold_tim)

------------------------ sec

sum(res_av_denom16)*100


p_nbsc_res_avail

2.16.7 Average FTCH holding time, S1 (trf_5)

Use: The holding time may change due to modification othe timers or perhaps software. You can use this PIfollow the impact of the modifications.

Experiences onuse: The counters get 0 values if the BTS is locked.

sum(ave_ftch_hold_tim)

------------------------ sec

sum(res_av_denom17)*100


p_nbsc_res_avail

2.16.8 TCH seizures for new call (call bids), S1 (trf_6)

Use: The seizures of TCH for a new call (i.e. not HO, noDR, not FCS).

sum(p_nbsc_traffic.tch_norm_seiz)


NTC TAN 0936/3 en



s

tedper

s

2.16.9 SDCCH usage %, S1 (trf_7b)

total SDCCH hold time in seconds

100 * --------------------------------------------------- %

average total nbr of SDCCH * period duration in seconds

sum(SDCCH_SEIZURES)*avg(a.ave_sdcch_hold_tim/a.res_av_denom16/100)

= 100 * ----------------------------------------------------- %

sum((a.ave_sdcch_sub/a.res_av_denom3 + a.ave_non_avail_sdcch)

* a.period duration*60)

where SDCCH_SEIZURES =(b.sdcch_assign+b.sdcch_ho_seiz+b.tch_seiz_due_sdcch_con)


a = p_nbsc_res_avail

b = p_nbsc_traffic

2.16.10 TCH traffic absorption on super, S4 (trf_8)


1. First, count the traffic per a TRX.

avg(ave_busy_tch)

2. Then, lable the TRXs to super or regular (TRX is a super if HO relacounters for this TRX show zero values). Sum up the traffic for suTRXs and for all TRXs and calculate their ratio.

traffic (super)

100 x --------------- %

traffic (all)


p_nbsc_underlay

2.16.11 TCH traffic absorption on super, S4 (trf_8a)

Use: IUO


First, count the traffic per TRX and per hour:

sum over BTS (avg per each super TRX (ave_busy_tch))

100 x ---------------------------------------------------- %

NTC TAN 0936/3 en



s

of

s

s

ber

sum over BTS (avg per each TRX (ave_busy_tch))


p_nbsc_underlay

2.16.12 Average cell TCH traffic from IUO, S4 (trf_9)


1. First, count the traffic per a TRX and per hour:

avg(ave_busy_tch)

2. Then, sum up the traffic over the period and divide it by the numberhours in the period:

sum traffic of all TRXs

100 x ------------------------ %

hours


p_nbsc_underlay

2.16.13 Cell TCH traffic from IUO, S4 (trf_9a)


sum over BTS (avg per each TRX (ave_busy_tch))

Counters from table(s):p_nbsc_underlay

2.16.14 Super TRX TCH traffic, S4 (trf_10)


1. First, count the traffic per a TRX and per hour:

avg(ave_busy_tch)

2. Then, sum it up over the period for super TRXs and divide it by the numof hours in the period:

traffic (super)

100 x --------------- 100%

NTC TAN 0936/3 en



s

ing.

ing

hours

2.16.15 Sum of super TRX TCH traffic, S4 (trf_10a)


sum over BTS (avg per each super TRX (ave_busy_tch))


p_nbsc_underlay

2.16.16 Average SDCCH traffic, erlang, S2 (trf_11)

Known problems: SDCCH seizures are too short to be counted by us20 s sampling time. if traffic is low (less than 0.5 Erl)

sum of traffic sum(a.ave_busy_sdcch / a.res_av_denom15)

--------------- = --------------------------------------

nbr of records count(*)


p_nbsc_res_avail

2.16.17 Average SDCCH traffic, erlang, S2 (trf_11a)

Known problems: SDCCH seizures are too short to be counted by us20 s sampling if traffic is low (less than 0.5 Erl).

Note: Gives the same results astrf_11 . Experimentsshowed that results match well withtrf_45 .

avg(ave_busy_sdcch / res_av_denom15)


2.16.18 Average TCH traffic, erlang, S2 (trf_12)

avg(a.ave_busy_tch / a.res_av_denom14)


p_nbsc_res_avail

2.16.19 Average TCH traffic, erlang, S2 (trf_12a)

Note: Gives the same results astrf_12 .

avg(ave_busy_tch / res_av_denom14)


NTC TAN 0936/3 en



eg

sot

s.

n-

2.16.20 Average TCH traffic, erlang, S2 (trf_12b)

Use: This formula gives the same result astrf_12a ifres_av_denom14 is the same (in practice variesslightly).

sum(ave_busy_tch) / sum(res_av_denom14)


2.16.21 Handover/call %, (trf_13b)

Use: Indicates how stationary or mobile the traffic is. Thbigger the number, the more mobile the traffic. Usinthis KPI, cells with stationary traffic can be found.

Known problems: Includes also intra-cell handovers that are notdirectly related to mobility. This is largely dependenon how much overlapping there is in the coverage

sum(a.tch_ho_seiz)

100 * -------------------------------------------------------------- %


+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch) ;(DR inter-cell calls)

+ sum(c.cell_sdcch_tch);(DR intra-cell calls in IOU,optional feature for S6)



a = p_nbsc_traffic

c = p_nbsc_ho

2.16.22 Intra-cell handover/call %, (trf_13c)

Use: Illustrates usually the impact of interference in a noIUO network.

Known problems: Seetrf_13b .

sum(c.cell_tch_tch)

100 * -------------------------------------------------------------- %






a = p_nbsc_traffic

c = p_nbsc_ho

NTC TAN 0936/3 en



eg

in

so

2.16.23 Handover/call %, (trf_13d)

Use: Indicates how stationary or mobile the traffic is: thbigger the value, the more mobile the traffic. Usinthis KPI cells with stationary traffic can be found.

Depends much on how much overlapping there isthe coverage areas.

Usable for a non-IUO network.

Known problems: Includes also intra-cell handovers that are notdirectly related to mobility.

sum(a.tch_ho_seiz)

- sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch);(DR inter-cell calls)

- sum(c.cell_sdcch_tch);(DR intra-cell calls in IOU,optional feature for S6)

100 * ------------------------------------------------------------ %






a = p_nbsc_traffic

c = p_nbsc_ho

2.16.24 IUO, average TCH seizure length on super TRXs, S4(trf_14b)

call time/tch seizures = average period duration * average traffic / tchseizures.

avg of BTS (avg of TRX (period_duration))*60! Avg.call time in seconds

*sum of BTS (sum of super TRX(ave_busy_tch))

= ------------------------------------------------------------- sec

sum of BTS( sum of super TRX(tch_succ_seiz))


p_nbsc_underlay

2.16.25 IUO, average TCH seizure length on regular TRXs, S4(trf_15b)

call time/tch seizures = average period duration * average traffic / tchseizures.

avg of BTS (avg of TRX (period_duration))*60

*sum of BTS (sum of regular TRX(avg_trx_traf))

= ------------------------------------------------------------- sec

sum of BTS( sum of regular TRX(tch_succ_seiz))

NTC TAN 0936/3 en



s

e


p_nbsc_underlay

2.16.26 Average TRX traffic, IUO, S4 (trf_16)

avg(ave_busy_tch)

Counters from table(s):p_nbsc_underlay

2.16.27 Average TRX TCH seizure length, IUO, S4 (trf_17a)

count(*) avg(ave_busy_tch)* period_duration*60

-----------------------------------------------

sum(tch_succ_seiz)


p_nbsc_underlay

2.16.28 Average TRX TCH seizure length, IUO, S4 (trf_17b)

sum(ave_busy_tch* period_duration*60)

-------------------------------------

sum(tch_succ_seiz)


p_nbsc_underlay

Unit: second

2.16.29 TCH requests for a new call, S3 (trf_18)

Known problems: A interface pool circuit type mismatch related retrieare included.

sum(tch_call_req)


2.16.30 TCH requests for a new call, S3 (trf_18a)

sum(a.tch_call_req)

- sum(a.tch_rej_due_req_ch_a_if_crc)

- (b.bsc_i_unsucc_a_int_circ_type + b.msc_controlled_in_ho +b.ho_unsucc_a_int_circ_type)


a = p_nbsc_traffic

b = p_nbsc_ho

2.16.31 Peak busy TCH (trf_19)

Use: This PI is an important traffic load indicator on thcell level. By following the development of this

NTC TAN 0936/3 en



e.

thee

esy

indicator and reacting proactively, blocking can bavoided in cells where the traffic growth is smooth

max(peak_busy_tch)


2.16.32 Average unit load (trf_20)

sum(load_rate)/sum(load_denom1)

Counters from table(s):p_nbsc_load

2.16.33 Call time difference between TRXs, S4 (trf_21)

Use: This PI shows as a percentage how much biggertraffic of the busiest TRX of a BTS is compared to thleast busy TRX of the same BTS.

100*(max_call_samples-min_call_samples)/min_call_samples

where

max_call_samples is call samples of busiest TRX of BTS:

max((ul_calls+dl_calls)/2)

and

min_call_samples is call samples of least busy TRX of BTS:

min((ul_calls+dl_calls)/2)

ul_calls=

sum(freq_ul_qual0 + freq_ul_qual1 + freq_ul_qual2 + freq_ul_qual3 +freq_ul_qual4 + freq_ul_qual5 + freq_ul_qual6 + freq_ul_qual7)

dl_calls=

sum(freq_dl_qual0 + freq_dl_qual1 + freq_dl_qual2 + freq_dl_qual3 +freq_dl_qual4 + freq_dl_qual5 + freq_dl_qual6 + freq_dl_qual7)


p_nbsc_rx_qual

2.16.34 Call time difference between TRXs, S4 (trf_21a)

Use: Shows how many times bigger the traffic of thbusiest TRX of a BTS is compared to the least buTRX of the same BTS.

max_call_samples/min_call_samples

where

max_call_samples is call samples of busiest TRX of BTS:

max((ul_calls+dl_calls)/2)

and

min_call_samples is call samples of least busy TRX of BTS:

min((ul_calls+dl_calls)/2)

NTC TAN 0936/3 en



ve.

w

=

from

ul_calls=

sum(freq_ul_qual0 + freq_ul_qual1 + freq_ul_qual2 + freq_ul_qual3 +freq_ul_qual4

+freq_ul_qual5 + freq_ul_qual6 + freq_ul_qual7)

dl_calls=

sum(freq_dl_qual0 + freq_dl_qual1 + freq_dl_qual2 + freq_dl_qual3 +freq_dl_qual4 + freq_dl_qual5 + freq_dl_qual6 + freq_dl_qual7)


p_nbsc_rx_qual

2.16.35 Number of mobiles located in a cell, BSC, (trf_23a)

Use: If counted over an area, it could be possible to deria KPI called ’Call minutes per MS’ from this formula

If used over a cell, it can give you an idea about hopotential the cell is, for example.

How many times periodic LU has been sent = PLUS

How many times one MS sends a periodic LU in a time periodcount_of_periods * period_duration/LU_period

X = nbr of MS

==>

X* count_of_periods * period_duration/LU_period = number ofperiodic updates (PLUS)

==> X = PLUS * LU_period/ (count_of_periods *period_duration)

sum(a.sdcch_loc_upd - nbr of incom.HO from other LA) *0.1*b.timer_periodic_update_ms

----------------------------------------------------------------------

count(*).a.period_duration/60


a = p_nbsc_res_access

b = c_bts

The sum of incoming handovers from other location areas has to be countedp_nbsc_ho_adj using the LA info from thec_bts table.

Note:

* b.timer_periodic_update_ms anda.period_duration should be ofthe same unit, minutes for example.

NTC TAN 0936/3 en



s.f

rertth

se

sts

ntly

2.16.36 Total TCH seizure time (call time in seconds) (trf_24b)

Note: The sampling takes place every 20 secondave_busy_tch counts cumulatively the number obusy TCHs.res_av_denom14 counts the number ofsamples taken.

This is not pure conversation time but TCH seizutime. In HO there are two TCHs seized for a shotime simultaneously and both may be counted if boseizures take place at the sampling moment.

sum(period_duration*60*ave_busy_tch/res_av_denom14)

Counters from table(s):a = p_nbsc_res_availunit = seconds

2.16.37 Total TCH seizure time (call time in hours), (trf_24c)

Note: Seetrf_24b .

sum(period_duration*ave_busy_tch/res_av_denom14/60)

Counters from table(s):p_nbsc_res_avail |unit = hours

2.16.38 SDCCH true seizures (trf_25)

Known problems: There is no counter for IMSI detaches until in releaS7.

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call +sdcch_loc_upd)


p_nbsc_res_access

2.16.39 SDCCH true seizures, S7 (trf_25a)

Known problems: There is no counter for supplemetary service requeuntil in release S9.

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call +sdcch_loc_upd + imsi_detach_sdcch)


p_nbsc_res_access

2.16.40 SDCCH true seizures for call and SS (trf_26)

Known problems: Supplementary services cannot be separated curreon the cell level.

NTC TAN 0936/3 en



or

e

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call

- succ_sdcch_sms_est- unsucc _sdcch_sms_est)


p_nbsc_res_access

2.16.41 SDCCH true seizures for call, SMS, SS (trf_27)

Known problems: Supplementary services cannot be separated.

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call)


2.16.42 Peak busy SDCCH seizures (trf_28)

Use: The peak value of SDCCH usage is needed fpreventive capacity monitoring on the cell level.

max(peak_busy_sdcch)


2.16.43 IUO layer usage % (trf_29)

Use: Counted for overlay TRXs or underlay TRXs.

sum(ave_busy_tch)

100 * ----------------------------------------------------------- %

sum(ave_full_tch_if1+ ave_full_tch_if2+ ave_full_tch_if3+

ave_full_tch_if4+ ave_full_tch_if5)

+ sum(ave_busy_tch)


p_nbsc_underlay

2.16.44 SDCCH seizures (trf_30)

Use: This figure tells the number of all events that havseized SDCCH.



2.16.45 Call time (minutes) from p_nbsc_res_avail (trf_32)

sum(period_duration * ave_busy_tch/res_av_denom14)

Counters from table(s):p_nbsc_res_availunit = minutes

NTC TAN 0936/3 en



te

oin

ea

2.16.46 Call time from p_nbsc_rx_qual (trf_32a)

Known problems: In a high load situation (OMU link) it is possible thaall call time is not measured. In other words, call timcan show a lower value than it has in reality.

Also in the beginning of the call and in handover twsamples are lost, showing a shorter time thanreality.

0.48*

sum(freq_ul_qual0 + freq_ul_qual1 + freq_ul_qual2 +f req_ul_qual3 +freq_ul_qual4 + freq_ul_qual5 + freq_ul_qual6 + freq_ul_qual7)

/60


p_nbsc_rx_qual

unit = minutes

2.16.47 Call time from p_nbsc_rx_statistics (trf_32b)

Known problems: In a high load situation it is possible that all call timis not measured. In other words, call time can showlower value than it has in reality.

0.48*

sum(freq_ul_qual0 + freq_ul_qual1 + freq_ul_qual2 + freq_ul_qual3 +freq_ul_qual4 + freq_ul_qual5 + freq_ul_qual6 + freq_ul_qual7)

/60


p_nbsc_rx_statistics

unit = minutes

2.16.48 SDCCH HO seizure % out of HO seizure attempts(trf_33)

100*sum(sdcch_ho_seiz)/sum(sdcch_seiz_att)


2.16.49 SDCCH assignment % out of HO seizure attempts(trf_34)

100*sum(sdcch_assign)/sum(sdcch_seiz_att ) %


NTC TAN 0936/3 en



res

2.16.50 TCH HO seizure % out of TCH HO seizure request(trf_35)

100*sum(tch_ho_seiz)/sum(tch_request-tch_call_req-tch_fast_req) %


2.16.51 TCH norm seizure % out of TCH call request (trf_36)

sum(tch_norm_seiz)

100 * --------------------------- %

sum(tch_call_req)


p_nbsc_traffic

2.16.52 TCH normal seizure % out of TCH call requests,(trf_36a)

sum(tch_norm_seiz)

-sum(tch_succ_seiz_for_dir_acc) ; ref.1

100 * -------------------------------- %

sum(tch_call_req)


p_nbsc_traffic

Ref.1tch_norm_seiz is triggered also in case of DAC.

2.16.53 TCH FCS seizure % out of TCH FCS attempts (trf_37)

sum(tch_seiz_due_sdcch_con)

100 * ----------------------------------- %

sum(tch_seiz_att_due_sdcch_con)


p_nbsc_traffic

2.16.54 TCH FCS seizure % out of congested SDCCH seizureattempts (trf_38)

Use: Indicates the percentage how many SDCCH seizuare saved by FACCH call setup.

sum(tch_seiz_due_sdcch_con)

100 * ----------------------------------- %

sum(sdcch_seiz_att)


p_nbsc_traffic

NTC TAN 0936/3 en



TRX

e

r

S

2.16.55 TCH seizures for new calls (trf_39)






a = p_nbsc_traffic

c = p_nbsc_ho

2.16.56 TCH seizures for new calls (trf_39a)




+ sum(c.cell_sdcch_tch) ;(DR intra-cell calls in IOU)



a = p_nbsc_traffic

c = p_nbsc_ho


2.16.57 HTCH usage, S5 (trf_40)

Use: On the area level gives you an idea of how well thcapacity is used. Use with S5 or later.

sum(a.ave_tch_busy_halfl)

= 100 * -------------------------------------------- %

sum(a.ave_tch_avail_half)


p_nbsc_res_avail

2.16.58 MOC rate, S6 (trf_41)

Known problems: Do not include SMS, SS ==> Better accuracy fospeech calls than if 3012 and 3013 were used.

If SDCCH congested and FACCH used for SM(SS?) then also SMS and SS get included.

tch_moc_seiz_att

100 * ------------------------------------ %

tch_moc_seiz_att + tch_mtc_seiz_att


p_nbsc_traffic

NTC TAN 0936/3 en



r

S

2.16.59 MTC rate, S6 (trf_42)

Known problems: Do not include SMS, SS ==> Better accuracy fospeech calls than if 3012 and 3013 were used.

If SDCCH congested and FACCH used for SM(SS?) then also SMS and SS get included.

tch_moc_seiz_att

100 * ------------------------------------ %

tch_moc_seiz_att + tch_mtc_seiz_att


p_nbsc_traffic

2.16.60 TCH single band subscriber holding time, S6 (trf_43)

0.48* sum(tch_single_band_hold_time)


p_nbsc_dual_band

Unit: seconds

2.16.61 TCH dual band subscriber holding time, S6 (trf_44)

0.48* sum(tch_dual_band_hold_time)


p_nbsc_dual_band

Unit: seconds

2.16.62 TCH data call seizures (trf_46)

sum(tch_norm_seiz+tch_ho_seiz + tch_seiz_due_sdcch_con)!! All TCHseizures (- sum(tch_full_seiz_speech_ver1 + tch_full_seiz_speech_ver2 +tch_full_seiz_speech_ver3+ tch_half_seiz_speech_ver1 + tch_ half _seiz_speech_ver2 + tch_ half_seiz_speech_ver3)

!! Speech seizures


2.16.63 Share of single band traffic (trf_47)

sum(tch_single_band_hold_time)

100* -------------------------------------------------------- %

sum(tch_single_band_hold_time + tch_dual_band_hold_time)


p_nbsc_dual_band

2.16.64 Share of dual band traffic (trf_48)

sum(tch_dual_band_hold_time)

NTC TAN 0936/3 en



A

A

100* -------------------------------------------------------- %

sum(tch_single_band_hold_time + tch_dual_band_hold_time)


p_nbsc_dual_band

2.16.65 Call retries due to A interface pool mismatch (trf_49)

Use: Compensation of the blocking caused by theinterface circuit pool mismatch.

Aif type mismatch or congestion - Aif circuit pool handover failure

= a.tch_rej_due_req_ch_a_if_crc

-(b.bsc_i_unsucc_a_int_circ_type+b.msc_controlled_in_ho+b.ho_unsucc_a_int_circ_type)


a = p_nbsc_traffic

b = p_nbsc_ho

2.16.66 HO retries due to A interface pool mismatch (trf_50)

Use: Compensation of the blocking caused by theinterface circuit pool mismatch.

Sum(bsc_i_unsucc_a_int_circ_type+msc_controlled_in_ho+ho_unsucc_a_int_circ_type)


2.16.67 TCH single band subscribers’ share of holding time, S6(trf_51)

sum(tch_single_band_hold_time)

100 * ------------------------------------------------------ %

sum(tch_single_band_hold_time+tch_dual_band_hold_time)


p_nbsc_dual_band

2.16.68 TCH dual band subscribers’ share of holding time, S6(trf_52)

sum(tch_dual_band_hold_time)

100 * ------------------------------------------------------ %

sum(tch_single_band_hold_time+tch_dual_band_hold_time)


p_nbsc_dual_band

Unit: seconds

NTC TAN 0936/3 en



rt.

up)

2.16.69 Calls started as FACCH call setup (trf_53)

sum(tch_seiz_att_due_sdcch_con)

Counters from table(s):p_nbsc_trafficUnit: seconds

2.16.70 SDCCH seizures (trf_54)



2.16.71 TCH normal seizures, (trf_55)

sum(tch_norm_seiz)

-sum(tch_succ_seiz_for_dir_acc) ; ref.1


p_nbsc_traffic

Ref.1tch_norm_seiz is triggered also in case of DAC.

2.17 Traffic directions

2.17.1 Mobile originated calls (moc)

2.17.1.1 SDCCH seizures for MO calls, S2 (moc_1)

Known problems: Includes supplementary services such as call diveIncludes SMS.

sum(succ_seiz_orig)


2.17.1.2 Successful MO speech calls, S3 (moc_2)

Note: Triggered when a call is cleared. Excludes setfailures, TCH drops and TCH busy (congestioncases.

Known problems: The measurement is on the BSC level.

sum(a.nbr_of_calls) where a.counter_id = 44

Counters from table(s):p_nbsc_cc_pm

2.17.1.3 Successful MO data calls, S3 (moc_3)

Note: Seemoc_2.

NTC TAN 0936/3 en



rator

rt.




2.17.1.4 MO call success ratio, S6 (moc_4)

Note: Seemoc_2.


Note:

MO call attempts are counted when MOCs are found on SDCCH. The numeexcludes setup failures, TCH drops and TCH busy (congestion) cases.

sum(a.nbr_of_calls) where a.counter_id = 44 /* MO call completed */

100 * -----------------------------------------------------------------

sum(a.nbr_of_calls) where a.counter_id = 38 /* MO call attempt */


p_nbsc_cc_pm

2.17.1.5 MO speech call attempts, S3 (moc_5)

Note: Seemoc_2.




2.17.1.6 MO call bids, S2 (moc_6)

Known problems: Includes supplementary services such as call dive

Includes SMS.

sum(succ_seiz_orig+tch_moc)


2.17.2 Mobile terminated calls (mtc)

2.17.2.1 SDCCH seizures for MT calls, S2 (mtc_1)

Known problems: Includes SMS. See alsomoc_2.

NTC TAN 0936/3 en



ds,

sum(succ_seiz_term)


2.17.2.2 Successful MT speech calls (mtc_2)

Note: Seemoc_2.

Known problems: Seemoc_2.



2.17.2.3 Successful MT data calls, S3 (mtc_3)

Note: Seemoc_2.




2.17.2.4 MT call success ratio, S6 (mtc_4)

Note: MT call attempts are counted when MTCs are founon SDCCH. The numerator excludes setup failureTCH drops and TCH busy (congestion) cases.


sum(a.nbr_of_calls) where a.counter_id = 43 /* MT call completed */

100 * -----------------------------------------------------------------

sum(a.nbr_of_calls) where a.counter_id = 37 /* MT call attempt */


p_nbsc_cc_pm

2.17.2.5 MT speech call attempts (mtc_5)

Note: Seemoc_2.




NTC TAN 0936/3 en



se

as

iferehe

2.17.2.6 MT call attempts, S2 (mtc_6)

Use: Total number of calls bids with establishment cau’MT’.

Known problems: Includes SMS.

sum(succ_seiz_term+tch_mtc)


2.18 Paging (pgn)

2.18.1 Number of paging messages sent, S2 (pgn_1)

Known problems: The number of repagings cannot be separated.

sum(paging_msg_sent)


2.18.2 Paging buffer size average, S1 (pgn_2)

Use: To have an idea of how close to problems the BTS hbeen.

Known problems: It is difficult to say when the problems start. Eventhe counter 3018 does not yet show the 0 value, thmay have been the situation in one or some of tbuffers that the capacity has run out.

avg(a.min_paging_buf)


p_nbsc_res_access

Parameters related:

Number of Blocks for AGCH (AG): e.g. = 2

Number of MultiFrames (MFR): e.g. = 6

Formulas related:

Nbr of paging groups = (3-AG)*MFR ;if combined control channel

Nbr of paging groups = (9-AG)*MFR ;if non-combined control channel

Paging_Buffer_Size = free buffers (max 8) * Nbr of paging groups

Min Paging Buffer (counter 3018) = min(Paging_Buffer_Space)

. = min(Paging_Buffer_Size/2)

Paging Buffer Space is sent by BTS in theCCH_Load_Ind message to a BSCevery 30 s. A BSC sends current paging load asPaging_Buffer_Size to a

NTC TAN 0936/3 en



ed.

heis

the

is

statistical unit. The minimum value of this is recorded as counter 3018. IfMinPaging Buffer (counter 3018) equals to zero, paging blocking has occurr

2.18.3 Average paging buffer space, S1 (pgn_3)

Use: Average remaining space for paging commands.

avg(ave_pch_load/res_acc_denom2)


2.18.4 Paging success ratio, S1 (pgn_4)

Known problems: Ghosts can increment the denominator. Due to tvery dynamic behaviour it seems that this formulanot useful.

sum over all BTS in LA (a.succ_seiz_term + a.tch_mtc)

100* ---------------------------------------------------- %

sum over LA(a.paging_msg_sent) / sum over LA (count of BTS)


p_nbsc_res_access

2.19 Short message service (sms)

2.19.1 SMS establishment failure % (sms_1)

100* unsuccessful SMS establishments / all SMS establishments =

sum(unsucc_TCH_sms_est+unsucc_SDCCH_sms_est)

100* ---------------------------------------------------------------- %

sum(succ_TCH_sms_est + unsucc_TCH_sms_est + succ_SDCCH_sms_est+ unsucc_SDCCH_sms_est)


p_nbsc_res_access

2.19.2 SMS TCH establishment failure % (sms_2)

sum(unsucc_TCH_sms_est)

100 * ------------------------------------------- %

sum(succ_TCH_sms_est+unsucc_TCH_sms_est)


p_nbsc_res_access

2.19.3 SMS SDCCH establishment failure % (sms_3)

Use: MOC: Instead of the sending SETUP message,MS starts SMS by sending SABM with SAPI 3 toBTS, and a new establishment indicationgenerated.

NTC TAN 0936/3 en



hegeTan

ern,s

ll).

MTC : Instead of the sending SETUP message, tMSC starts SMS by sending the CP DATA messato BSC and BSC sends an ESTABLISH REQUESto BTS, then MS answers by UA message, andESTABLISH CONFIRM message is generated.

SMS fails if the message data is corrupted, timexpires in waiting for an establishment confirmatioor if an error indication or release indication ireceived.

sum(unsucc_sdcch_sms_est)

100 * -------------------------------------------- %

sum(succ_sdcch_sms_est+unsucc_sdcch_sms_est)


p_nbsc_res_access

2.19.4 SMS establishment attempts (sms_4)

sum(succ_TCH_sms_est+unsucc_TCH_sms_est+succ_SDCCH_sms_est+unsucc_SDCCH_sms_est)


2.19.5 SMS SDCCH establishment attempts (sms_5)

sum(succ_sdcch_sms_est+unsucc_sdcch_sms_est)


2.19.6 SMS TCH establishment attempts (sms_6)

sum(succ_TCH_sms_est+unsucc_TCH_sms_est)


2.20 Directed retry (dr)

2.20.1 DR, outgoing attempts, S3 (dr_1)

sum(msc_o_sdcch_tch_at+ bsc_o_sdcch_tch_at)


2.20.2 DR attempts, S3 (dr_1a)

Use: Includes all DR cases (to another cell and intra-ce

NTC TAN 0936/3 en



l

sum(p_nbsc_ho.cause_dir_retry)


2.20.3 DR, incoming attempts, S3 (dr_2)

sum(msc_i_sdcch_tch_at+ bsc_i_sdcch_tch_at)


2.20.4 DR, outgoing success to another cell, S3 (dr_3)

sum(msc_o_sdcch_tch+ bsc_o_sdcch_tch)


2.20.5 DR, incoming success from another cell, S3 (dr_4)

sum(msc_i_sdcch_tch+ bsc_i_sdcch_tch)


2.20.6 DR, intra-cell success, S3 (dr_5)

Use: Triggered by

• S6 feature ’TCH assignment to super-reuse in IUO’

• S7 feature ’Direct access to super-reuse TRX’

sum(cell_sdcch_tch)


2.20.7 % of new calls successfully handed over to another celby DR, S3 (dr_6)

100*sum(msc_o_sdcch_tch+ bsc_o_sdcch_tch)/sum(tch_call_req)


2.20.8 DR, outgoing to another cell, failed, S3 (dr_7)

sum(msc_o_sdcch_tch_at + bsc_o_sdcch_tch_at - msc_o_sdcch_tch +bsc_o_sdcch_tch)


2.20.9 DR, intra-cell failed, S3 (dr_8)

Use: Triggered by

NTC TAN 0936/3 en



d,

d,

d

• S6 feature ’TCH assignment to super-reuse in IUO’

• S7 feature ’Direct access to super-reuse TRX’

sum(cell_sdcch_tch_at - cell_sdcch_tch)


2.21 Availability (ava)

2.21.1 TCH availability %, S4 (ava_1a)

Known problems: If TRXs are locked and BTSs and BCFs are unlockethe TCHs appear as unavailable.

This PI does not take HTCH into consideration.

available TCH

100 * ------------------ %

all TCH

sum(ave_avail_full_TCH/res_av_denom2)

=100 * -------------------------------------------------------------- %

sum(ave_avail_full_TCH/res_av_denom2)+sum(ave_non_avail_TCH)


p_nbsc_res_avail

2.21.2 Average available TCH, S1 (ava_2)


sum(ave_avail_full_tch)/sum(res_av_denom2)


2.21.3 Average available SDCCH, S1 (ava_3)

sum(ave_sdcch_sub)/sum(res_av_denom3)


2.21.4 SDCCH availability %, S4 (ava_4)

Known problems: Affected by locked TRX under unlocked BCF anBTS. See TCH availability percentage.

sum(ave_sdcch_sub/res_av_denom3)

100 * --------------------------------------------------------- %

sum(ave_sdcch_sub/res_av_denom3)+sum(ave_non_avail_sdcch)


p_nbsc_res_avail

NTC TAN 0936/3 en



d,

d,

2.21.5 Average available FTCH in area, S1 (ava_5)

sum_over_area ( sum_over_BTS(ave_avail_full_TCH)/sum_over_BTS(res_av_denom2) )


2.21.6 DMR availability %, S6 (ava_6)

sum(avail_time)

100 * ---------------- %

sum(total_time)


p_nbsc_dmr

2.21.7 DN2 availability %, S6 (ava_7)

sum(avail_time)

100 * --------------- %

sum(total_time)


p_nbsc_dn2

2.21.8 TRU availability %, S6 (ava_8)

sum(avail_time)

100 * --------------- %

sum(total_time)


p_nbsc_tru_bie

2.22 Unavailability (uav)

2.22.1 Average unavailable TSL per BTS, S1 (uav_1)


sum(ave_non_avail_tsl)/sum(res_av_denom1)


2.22.2 Average unavailable TSL per BTS, S1 (uav_1a)


avg(ave_non_avail_tsl/res_av_denom1)


NTC TAN 0936/3 en



d,

ns

TS

2.22.3 Average unavailable TSL per BTS, S1 (uav_1b)


sum(ave_non_avail_tsl/res_av_denom1)

------------------------------------

count(*)


p_nbsc_res_avail

2.22.4 Total outage time, (uav_2)

Known problems: It should be made possible to differentiate the reasofor outage.

Note: Alarm number changed in S7.

sum of BCCH missing alarm durations =

sum(a.cancel_time-a.alarm_time)*24*60

where a.probable_cause = 2567 /* BCCH missing alarm */

Counters from table(s):fx_alarmUnit = minutes

2.22.5 Number of outages, (uav_3)

Note: Alarm number changed in S7.

number of BCCH missing alarm starts =

count(alarm_start_time)

where a.probable_cause = 2567 /* BCCH missing alarm */

Counters from table(s):fx_alarm

2.22.6 Share of unavailability due to user (uav_4)

Experiences onuse: Locked TRXs can make this PI show high values.

Known problems: The measurement is made on the BSC level. The Blevel cannot be seen.

sum(ave_non_avail_user)

100 * -------------------------------------------------------------- %

sum(ave_non_avail_user + ave_non_avail_int + ave_non_avail_ext)


NTC TAN 0936/3 en



TSlsolt.

TS

k

p_nbsc_trx_avail

2.22.7 Share of unavailability due to internal reasons (uav_5)

Known problems: The measurement is made on the BSC level. The Blevel cannot be seen. This includes, for example, aan electricity break which, in fact, is not a BTS fau

sum(ave_non_avail_int)

100 * -------------------------------------------------------------- %



p_nbsc_trx_avail

2.22.8 Share of unavailability due to external reasons (uav_6)

Known problems: The measurement is made on the BSC level. The Blevel cannot be seen.

sum(ave_non_avail_ext)

100 * -------------------------------------------------------------- %



p_nbsc_trx_avail

2.22.9 TRX unavailability time due to user (uav_7)

Experiences onuse: Locked TRXs can make this PI show high values.

sum(period_duration * ave_non_avail_user)

Counters from table(s):p_nbsc_trx_avail

2.22.10 TRX unavailability time due to internal reasons(uav_8)

Known problems: This includes, for example, also an electricity breawhich, in fact, is not a BTS fault.

sum(period_duration * ave_non_avail_int)


2.22.11 TRX unavailability time due to external reasons(uav_9)

sum(period_duration * ave_non_avail_ext)


NTC TAN 0936/3 en



es:s.

hn.on

2.23 Location updates (lu)

2.23.1 Number of LU attempts, S1 (lu_1)

sum(sdcch_loc_upd)


2.23.2 Average of LU attempts per hour, S1 (lu_2)

sum(sdcch_loc_upd)

--------------------------------

avg(period_duration)*count(*)/60


p_nbsc_res_access

2.23.3 Number of LU attempts, S1 (lu_3)

sum(a.nbr_of_calls) where a.counter_id = 25 /* LU started */


2.24 LU success % (lsr)

2.24.1 LU success %, S6 (lsr_2)

Use: Probable causes to make this KPI show bad valuinterference, coverage, possibly MSC side problem

Known problems: The measurement is made on the BSC level.

The LU started (51025) is triggered from establisindication. Any problems prior to that cannot be seeFor example, interference prevents a mobile statifrom making a location update.

Values: Good: >99% .

sum(a.nbr_of_calls) where a.counter_id = 26 /* LU completed */

100 * ----------------------------------------------------------- %

sum(a.nbr_of_calls) where a.counter_id = 25 /* LU started */


p_nbsc_cc_pm

NTC TAN 0936/3 en



2.25 Emergency call (ec)

2.25.1 Emergency calls, S6 (ec_1)

sum(a.nbr_of_calls) where a.counter_id = 35 /* Em.call started */


2.26 Emergency call success % (ecs)

2.26.1 Emergency call success %, S6 (ecs_1)

sum(a.nbr_of_calls) where a.counter_id = 41 /* Em.call completed */

100 * ---------------------------------------------------------------

sum(a.nbr_of_calls) where a.counter_id = 35 /* Em.call started */


p_nbsc_cc_pm

2.27 Call re-establishment (re)

2.27.1 Call re-establishment attempts, S6 (re_1)

sum(a.nbr_of_calls) where a.counter_id = 36 /* Call reest. started */


2.27.2 Call re-establishments, S6 (re_2)

sum(sdcch_call_re_est+tch_call_re_est)


2.28 Call re-establishment Success % (res)

2.28.1 Call re-establishment success %, S6 (res_1)

sum(a.nbr_of_calls) where a.counter_id = 42 /* Call reest. completed */

100 * ----------------------------------------------------------------

sum(a.nbr_of_calls) where a.counter_id = 36 /* Call reest. started */


p_nbsc_cc_pm

NTC TAN 0936/3 en



s.

lesty

ty

lesty

ty

s.

2.29 Quality

2.29.1 Downlink quality (dlq)

2.29.1.1 DL BER, S1 (dlq_1)

Known problems: BER % is not a very easy entity for network planner

sum(a.ave_dl_sig_qual)

------------------------ %

sum(a.power_denom5)*100


p_nbsc_power

Unit = BER %

2.29.1.2 DL cumulative quality % in class X, S1 (dlq_2)

Use: This PI gives a cumulative percentage of call sampin classes 0 to X. X=5 is normally used as qualiindicator. If X=5 and this figure is 100 %, then the MSusers obviously have not perceived any qualiproblems.

sum(a.freq_dl_qual0 + ... + a.freq_dl_qualX)

100 * --------------------------------------------- %

sum(a. freq_dl_qual0 + ... + a.freq_dl_qual7)


p_nbsc_rx_qual

2.29.1.3 DL cumulative quality % in class X, S1 (dlq_2a)


sum(a.freq_dl_qual0 + ... + a.freq_dl_qualX)

100 * --------------------------------------------- %

sum(a. freq_dl_qual0 + ... + a.freq_dl_qual7)



2.29.2 Uplink quality (ulq)

2.29.2.1 UL BER, S1 (ulq_1)

Known problems: BER % is not a very easy entity for network planner

NTC TAN 0936/3 en



lesty

ty

erets,

lesty

ty

sum(a.ave_ul_sig_qual)

------------------------ %

sum(a.power_denom6)*100


p_nbsc_power

2.29.2.2 UL cumulative quality % in class X, S1 (ulq_2)


Known problems: Investigations in late 1997 showed that UL DTXmakes UL quality seem worse than it actually is. Thimpact was about one 1% unit (1% of samples moin classes 6 and 7). When investigated with field tesno real degradation of quality could be found.

sum(a.freq_ul_qual0 + ... + a.freq_ul_qualX)

100 * --------------------------------------------- %

sum(a. freq_ul_qual0 + ... + a.freq_ul_qual7)


p_nbsc_rx_qual

2.29.2.3 UL cumulative quality % in class X, S1 (ulq_2a)


sum(a.freq_ul_qual0 + ... + a.freq_ul_qualX)

100 * --------------------------------------------- %

sum(a. freq_ul_qual0 + ... + a.freq_ul_qual7)



2.30 Downlink and uplink level

2.30.1 Downlink level (dll)

2.30.1.1 Share % per range, S4 (dll_1)

sum over a range (a.class_upper_range)

(freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4

+freq_dl_qual5+freq_dl_qual6+freq_dl_qual7)

NTC TAN 0936/3 en



100 * ----------------------------------------------------------- %

sum over all ranges

(freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4

+freq_dl_qual5+freq_dl_qual6+freq_dl_qual7)



2.30.2 Uplink level (ull)

2.30.2.1 Share % per range, S4 (ull_1)

sum over a range (a.class_upper_range)

(freq_ul_qual0+freq_ul_qual1+freq_ul_qual2+freq_ul_qual3+freq_ul_qual4

+freq_ul_qual5+freq_ul_qual6+freq_ul_qual7)

100 * ----------------------------------------------------------- %

sum over all ranges

(freq_ul_qual0+freq_ul_qual1+freq_ul_qual2+freq_ul_qual3+freq_ul_qual4

+freq_ul_qual5+freq_ul_qual6+freq_ul_qual7)



2.31 Power (pwr)

2.31.1 Average MS power, S2 (pwr_1)

max_power-2*sum(ave_ms_power)/sum(power_denom1)

max_power = 43 (GSM900) or max_power = 30 (GSM1800, GSM1900)


p_nbsc_power

2.31.2 Average MS power, S2 (pwr_1b)

Note: max_power = 43 (GSM900) or 30 (GSM1800,GSM1900)

decode(objects.frequency_band_in_use,0,43,30)-2*sum(ave_ms_power)/sum(power_denom1)


2.31.3 Average BS power, S2 (pwr_2)

max_power - 2*sum(ave_BS_power)/sum(power_denom2)

max_power depends on the TRX used.Counters from table(s):p_nbsc_power

NTC TAN 0936/3 en



not

2.32 Level (lev)

2.32.1 Average DL signal strength, S2 (lev_1)

-110+sum(ave_dl_sig_str)/sum(power_denom3)


p_nbsc_power

2.32.2 Average DL signal strength, S2 (lev_1a)

decode(

ave_dl_sig_str/power_denom3,

0,'< -110',

63,'> -48',

(-110+(round(ave_dl_sig_str/power_denom3)-1))||'..'||(-110+round(ave_dl_sig_str/power_denom3))

)


p_nbsc_power

2.32.3 Average UL signal strength, S2 (lev_2)

-110+sum(ave_ul_sig_str)/sum(power_denom4)


2.32.4 Average UL signal strength, S2 (lev_2a)

decode(

ave_ul_sig_str/power_denom4,

0,'< -110',

63,'> -48',

(-110+(round(ave_ul_sig_str/power_denom4)-1))||'..'||(-110+round(ave_ul_sig_str/power_denom4))

)


p_nbsc_power

2.33 Distance (dis)

2.33.1 Average MS-BS distance (dis_1)

avg(ave_ms_bs_dist)*550 meter


The condition below should be applied in order to filter out the hours that dohave traffic and for that reason show 0:

peak_ms_bs_dist+ave_dl_sig_str/power_denom3+ave_ul_sig_str/power_denom4 > 0

NTC TAN 0936/3 en



is

is

is

is

2.34 Link balance, power, level (lb)

2.34.1 Link balance, S1 (lb_1)

Known problems: Inaccurate.

avg(ave_dl_sig_str/power_denom3) - avg(ave_ul_sig_str/power_denom4)


2.34.2 Share in acceptance range, S4 (lb_2)

Known problems: The usefulness of link balance measurementquestionable.

sum(normal+ms_limited+bs_limited+max_power)

{where class_sig_level <= upper threshold

and class_sig_level >= lower threshold }

100 * ------------------------------------------------- %



p_nbsc_link_balance

2.34.3 Share in normal, S4 (lb_3)


sum(normal)

100 * ------------------------------------------------- %



p_nbsc_link_balance

2.34.4 Share in MS limited, S4 (lb_4)


sum(ms_limited)

100 * ------------------------------------------------- %



p_nbsc_link_balance

2.34.5 Share in BS limited, S4 (lb_5)


NTC TAN 0936/3 en



is

n -8

n -8

sum(bs_limited)

100 * ------------------------------------------------- %



p_nbsc_link_balance

2.34.6 Share in maximum power, S4 (lb_6)


sum(max_power)

100 * ------------------------------------------------- %



p_nbsc_link_balance

2.34.7 Average MS power attenuation, S2 (lb_7)

2*sum(ave_MS_power)/sum(power_denom1) Unit = dB


2.34.8 Average MS power, S2 (lb_7b)

avg(decode(o_bts.freq_band_in_use,0,43,1,30)-2*ave_MS_power/power_denom1 Unit = dBm


2.34.9 Average UL signal strength, S2 (lb_9)

Use: Values as defined by GSM 5.08 (0..63: 0 = less tha110 dBm, 1 = -110 to -109 dBm, 3 = -109 to -10dBm ... 62 = -49 to -48, 63 =greater than -48)

sum(ave_ul_sig_str)/sum(power_denom4)


2.34.10 Average DL signal strength, S2 (lb_10)

Use: Values as defined by GSM 5.08 (0..63: 0 = less tha110 dBm, 1 = -110 to -109 dBm, 3 = -109 to -10dBm ... 62 = -49 to -48, 63 =greater than -48)

sum(ave_dl_sig_str)/sum(power_denom3)


NTC TAN 0936/3 en



is

is

2.34.11 Average MS power attenuation, S2 (lb_11)

2*sum(ave_MS_power)/sum(power_denom1)

Counters from table(s):p_nbsc_powerUnit = dB

2.34.12 Average BS power attenuation, S2 (lb_12)

2*sum(ave_BS_power)/sum(power_denom2)

Counters from table(s): p_nbsc_powerUnit = dB

2.35 Call success (csf)

2.35.1 SDCCH access probability, before FCS (csf_1)

Known problems: 1) sdcch_busy_att triggers if there is FACCH callsetup.

2) The momentary SDCCH blocking phenomenonmet in some networks.

3) sdcch_busy_att triggers also in the case of HOattempt if there are no free SDCCH.

sdcch_busy_att

100*(1- --------------) %

sdcch_seiz_att


p_nbsc_traffic

2.35.2 SDCCH access probability (csf_1a)

Known problems: 1) The momentary SDCCH blocking phenomenonmet in some networks.

2) sdcch_busy_att triggers also in the case of HOattempt if there are no free SDCCH.

sdcch_busy_att- tch_seiz_due_sdcch_con

100-(100* ----------------------------------------) %

sdcch_seiz_att


p_nbsc_traffic

2.35.3 SDCCH success ratio (csf_2a)

Experiences onuse: The best values seen are around 98 %.

NTC TAN 0936/3 en



allre

la

f

A

ts,s.m

rksthe

ationr

call

allH).

H-netase

Known problems: The formula does not separate the SDCCH cseizures from other seizures (such as LU). The failurate in the case of a call or LU can greatly differ fromone another, wherefore you cannot use this formufor SDCCH call success ratio calculation.

It is not exactly known how large a share osum(sdcch_abis_fail_call +sdcch_abis_fail_old) really are setup failures.

100 - non abis SDCCH drop ratio =


sdcch_netw_act +sdcch_bts_fail+

sdcch_lapd_fail+sdcch_a_if_fail_call+sdcch_a_if_fail_old)

100- 100*------------------------------------------------------------ %


- sum(sdcch_abis_fail_call+sdcch_abis_fail_old)


p_nbsc_traffic

2.35.4 SDCCH success ratio, area (csf_2f)


Experiences onuse: The best values seen are around 95 %. Includes

interface blocking!

Known problems: As consistency is a critical property in measurementhe combining of three tables can lead into problemUnknown factors in the dividor make the values seepessimistic.

• The calls are cleared before TCH can vary between netwodepending on the call setup time which, again, may depend onuse of DR or queuing features. Other reasons can be authenticfails, identity check fails and MOC calls having wrong dialling, foexample.

• The number of supplementary service requests such asforwarding is not available as a BTS level counter.

• This formula does not count correctly the situation when the first cor call re-establishment fails on SDCCH (MS never comes to TC

• For the BTS area there is no way knowing how much SDCCSDCCH handovers take place across the area border. Theincoming amount of SDCCH handovers ends up in a successful cto TCH seizures but they are not seen in the nominator.

NTC TAN 0936/3 en



Hmingsful

ers

s

M

-the

ts,s.

• For the BTS area there is no way knowing how much SDCCH-TC(DR) handovers take place across the area border. The net incoamount of SDCCH-TCH (DR) handovers ends up in a succescase with TCH seizures but they are not seen in the nominator.

• The ratio shows values of over 100% when the SMS count(succ_sdcch_sms_est and unsucc_sdcch_sms_est ) aretriggered without triggering of SDCCH counter(succ_seiz_term and succ_seiz_orig ) if interference in theair interface causes repetition of the first message for SMS (SABfor SAPI3).

(succ tch seiz) - (call re-establ.)

100 * ------------------------------------------------------- %

(sdcch seizures for new calls) - (blocked calls)

sum(a.tch_norm_seiz);(all TCH seiz.for new call)

-call re-establ. (unknown factor)

=100* ------------------------------------------------------------ %

sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_emerg_call

+b.sdcch_call_re_est);(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est+ b.unsucc_sdcch_sms_est)

;(sms attempts)

- sum(a.tch_call_req-a.tch_norm_seiz-bsc_o_sdcch_tch- msc_o_sdcch_tch)

;(blocked calls & Aif pool circuit type mismatch)

- supplem.serv.requests (unknown factor )

- call clears before TCH (unknown factor)

+ net impact of SDCCH-SDCCH ho on area(unknown factor)

+ net incoming DR to area (unknown factor)

Counters from table(s):a = p_nbsc_traffic


c = p_nbsc_ho

Note:

This formula includes also A interface blocking. It works for call reestablishment if the drop occurs on TCH. If the drop occurs on SDCCH andcall is re-established, there is double count in the dividor.

2.35.5 SDCCH success ratio, BTS, S6 (csf_2g)

Use: BTS level.

Experiences onuse: Includes A interface blocking!

Known problems: As consistency is a critical property in measurementhe combining of three tables can lead into problemSee problems 1-3 fromcsf_2d . Unknown factors in

NTC TAN 0936/3 en



stic

on

A

ts,s.m

rksthe

ationr

call

allH).

the denominator make the values seem pessimi(See problems 1-3 fromcsf_2d .).

sum(a.tch_norm_seiz);(all TCH seiz.for new call)

=100* ------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig

+b.sdcch_call_re_est+b.sdcch_emerg_call);(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est

+ b.unsucc_sdcch_sms_est) ;(sms attempts)

+ sum(c.msc_i_sdcch + c.bsc_i_sdcch ;(net SDCCH HO in)

-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls

- sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking)

- supplem.serv. requests ;(unknown factor)

- call clears before TCH ;(unknown factor)



a = p_nbsc_traffic


c = p_nbsc_ho

Note:

Includes also A interface blocking. If call re-establishment occurs alreadySDCCH, the formula is not correct, but if it occurs on TCH, it is correct.

2.35.6 SDCCH success ratio, area, (csf_2h)


Experiences onuse: The best values seen are around 95 %. Includes

interface blocking!

Known problems: As consistency is a critical property in measurementhe combining of three tables can lead into problemUnknown factors in the dividor make the values seepessimistic.

• The calls are cleared before TCH can vary between netwodepending on the call setup time which, again, may depend onuse of DR or queuing features. Other reasons can be authenticfails, identity check fails and MOC calls having wrong dialling, foexample.

• The number of supplementary service requests such asforwarding is not available as a BTS level counter.

• This formula does not count correctly the situation when the first cor call re-establishment fails on SDCCH (MS never comes to TC

NTC TAN 0936/3 en



H-netase

Hmingsful

ers

s

M

-the

• For the BTS area there is no way knowing how much SDCCSDCCH handovers take place across the area border. Theincoming amount of SDCCH handovers ends up in a successful cto TCH seizures but they are not seen in the nominator.

• For the BTS area there is no way knowing how much SDCCH-TC(DR) handovers take place across the area border. The net incoamount of SDCCH-TCH (DR) handovers ends up in a succescase with TCH seizures but they are not seen in the nominator.

• The ratio shows values of over 100% when the SMS count(succ_sdcch_sms_est and unsucc_sdcch_sms_est ) aretriggered without triggering of SDCCH counter(succ_seiz_term and succ_seiz_orig ) if interference in theair interface causes repetition of the first message for SMS (SABfor SAPI3).

(succ tch seiz) - (call re-establ.)

100 * ------------------------------------------------------- %

(sdcch seizures for new calls) - (blocked calls)

sum(a.tch_norm_seiz) ;(all TCH seiz.for new call)

-call re-establ. (unknown factor)

=100* -------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig+b.sdcch_emerg_call

+b.sdcch_call_re_est) ;(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est+ b.unsucc_sdcch_sms_est)

;(sms attempts)

- b.bsc_o_sdcch_tch - b.msc_o_sdcch_tch - b.cell_sdcch_tch

+ a.succ_tch_seiz_for_dir_acc)

- supplem.serv.requests (unknown factor )

- call clears before TCH (unknown factor)

+ netto impact of SDCCH-SDCCH ho on area(unknown factor)

+ netto incoming DR to area (unknown factor)



c = p_nbsc_ho

Note:

This formula includes also A interface blocking. It works for call reestablishment if the drop occurs on TCH. If the drop occurs on SDCCH andcall is re-established, there is double count in the dividor.

2.35.7 SDCCH success ratio, BTS, (csf_2i)

Use: BTS level.

Experiences onuse: Includes A interface blocking!

NTC TAN 0936/3 en



ts,s.

stic

on

he

ifto

Known problems: As consistency is a critical property in measurementhe combining of three tables can lead into problemSee problems 1-3 fromcsf_2d . Unknown factors inthe denominator make the values seem pessimi(See problems 1-3 fromcsf_2d .).

sum(a.tch_norm_seiz) ;(all TCH seiz.for new call)

=100* ------------------------------------------------------------- %

sum(b.succ_seiz_term+b.succ_seiz_orig

+b.sdcch_call_re_est+b.sdcch_emerg_call);(calls,sms, ss reqs)

- sum(b.succ_sdcch_sms_est

+ b.unsucc_sdcch_sms_est) ;(sms attempts)

+ sum(c.msc_i_sdcch + c.bsc_i_sdcch ;(netto SDCCH HO in)

-c.msc_o_sdcch - c.bsc_o_sdcch) ;(unknown how big part calls

- sum(c.cell_sdcch_tch)

+ sum(a.tch_succ_seiz_for_dir_acc);direct access related correction

- sum(a.tch_call_req-a.tch_norm_seiz) ;(DR and air itf blocking)


- call clears before TCH ;(unknown factor)



a = p_nbsc_traffic


c = p_nbsc_ho

Note:

Includes also A interface blocking. If call re-establishment occurs alreadySDCCH, the formula is not correct, but if it occurs on TCH, it is correct.

2.35.8 TCH access probability without DR (csf_3a)

Use: This PI indicates what would be the blocking if DRwas not used. When compared tocsf_3 , you can see,assuming that DR is in use, the improvement that tDR has caused.

100-blck_8 =

sum(a.tch_call_req - a.tch_norm_seiz)

100-100* ------------------------------------- %

sum(a.tch_call_req)


p_nbsc_traffic

2.35.9 TCH access probability without DR and Q (csf_3b)

Use: This PI indicates what would be the TCH blockingDR and queuing were not used. When compared

NTC TAN 0936/3 en



he

f

ifto

heotl.

csf_3a , you can see, assuming that DR is in use, timprovement that the DR has caused.

Known problems: See XX1.


+ sum(a.tch_qd_call_att-XX1-a.unsrv_qd_call_att) ;calls that succeeded via queuing

100-100*------------------------------------------- %

sum(a.tch_call_req)


p_nbsc_traffic table.

XX1 = attempts taken from queue to DR (unknown)

2.35.10 TCH access probability without Q (csf_3c)

Use: This PI indicates what would be the blocking iqueuing was not used (but DR is used).

sum(a.tch_call_req - a.tch_norm_seiz - b.msc_o_sdcch_tch -b.bsc_o_sdcch_tch)

+ sum(a.tch_qd_call_att-a.unsrv_qd_call_att) ;calls that succeeded via queuing

100-100* ------------------------------------------------------------ %

sum(a.tch_call_req)


a = p_nbsc_traffic

b = p_nbsc_ho

2.35.11 TCH access probability, real (csf_3d)

Use: This KPI is affected by the congestion on TCH.

100-blck_8b =


- sum(b.msc_o_sdcch_tch+ b.bsc_o_sdcch_tch+b.cell_sdcch_tch);DR calls

100-100* ----------------------------------------------------------- %

sum(a.tch_call_req)


b = p_nbsc_handover

2.35.12 TCH access probability without DR and Q, (csf_3i)

Use: This PI indicates what would be the TCH blockingDR and queuing were not used. When comparedcsf_3a , you can see, assuming that DR is in use, timprovement that the DR has caused. Does ncontain the congestion of the A interface circuit poo

NTC TAN 0936/3 en



if

enthe

Known problems: See XX1.


+ sum(a.tch_qd_call_att-XX1-a.unsrv_qd_call_att);succ. calls via queuing

- sum(a.tch_rej_due_req_ch_a_if_crc); Aif pool rejections

100-100*-------------------------------------------------------- %

sum(a.tch_call_req)

- sum(a.tch_rej_due_req_ch_a_if_crc); Aif pool rejections


p_nbsc_traffic table.

XX1 = attempts taken from queue to DR (unknown)

2.35.13 TCH access probability without DR, (csf_3j)

Use: This PI indicates what would be the TCH blockingDR was not used. When compared tocsf_3a , youcan see, assuming that DR is in use, the improvemthat the DR has caused. Does not contain tcongestion of the A interface circuit pool.

100-blck_8c =






100-100* ------------------------------------- %

sum(a.tch_call_req)






a = p_nbsc_traffic

b = p_nbsc_handover

2.35.14 TCH access probability, real, (csf_3k)

Use: This KPI is affected by the blocking on TCH.

100-blck_8c =



- sum(a.tch_rej_due_req_ch_a_if_crc;Aif type mismatch or congestion




100-100* ----------------------------------------------------------- %

sum(a.tch_call_req)

NTC TAN 0936/3 en



er

TRX

nt






b = p_nbsc_handover

2.35.15 TCH access probability, real, (csf_3l)

Use: This KPI is affected by the blocking on TCH.

Known problems: On cell level the formula is inaccurate in case of intcell direct access (BSS7057).

100-blck_8d =



+ sum(a.tch_succ_seiz_for_dir_acc);ref.2





100-100* ----------------------------------------------------------- %

sum(a.tch_call_req)






b = p_nbsc_handover

Ref.2. Compensation needed since in case of Direct Access to super reusethe tch_norm_seiz is triggered in parallel with thecell_sdcch_tch .

2.35.16 TCH success ratio, area, before call re-establisment(csf_4o)

Use: On the area level. The impact of call re-establishmeis not yet taken into account.


sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call +a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old +a.tch_tr_fail + a.tch_tr_fail_old + 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)

100 -100* ----------------------------------------------------------- %

NTC TAN 0936/3 en



on

entspts,re-see

-s





a = p_nbsc_traffic

c = p_nbsc_ho

2.35.17 TCH success ratio, area, after call re-establishment, S6(csf_4p)


Known problems: 1) Seedcr_3g .

2) It is assumed that call re-establishments happenTCH. In fact they may happen also on SDCCH.

3) The counters used to compensate re-establishmare the ones that indicate re-establishment attemnot the succesful re-establishments. In S7/T11establishments can be considered accurately (csf_4v ).

4) On cell level it can happen that the call is reestablished in a different cell than where it wadropped, which results in inaccuracy.

100-dcr_3f =

sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call +a.tch_abis_fail_old + a.tch_a_if_fail_call + a.tch_a_if_fail_old +a.tch_tr_fail + a.tch_tr_fail_old + 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) - sum(b.sdcch_call_re_est + b.tch_call_re_est);

call re-establishments

100 -100* ----------------------------------------------------------- %

sum(a.tch_norm_seiz);calls started directly in the cell

+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell_sdcch_tch); DR calls


- sum(b.sdcch_call_re_est+b.tch_call_re_est) ;call re-establishments


a = p_nbsc_traffic


c = p_nbsc_ho

2.35.18 TCH success ratio, BTS, before call re-establisment(csf_4q)


Known problems: Seedcr_4c .

NTC TAN 0936/3 en



100-dcr_4b =

sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+a.tch_tr_fail+ a.tch_tr_fail_old+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)

100 -100* ----------------------------------------------------------- %

sum(a.tch_norm_seiz);(normal calls)


+ sum(a.tch_seiz_due_sdcch_con); FACCH call setup calls

+ sum(c.msc_i_tch_tch+c.bsc_i_tch_tch);(TCH-TCH Ho in)


a = p_nbsc_traffic

c = p_nbsc_ho

2.35.19 TCH success ratio, BTS, after call re-establishment(csf_4r)



sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+a.tch_tr_fail+ a.tch_tr_fail_old+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)-

sum(b.sdcch_call_re_est+b.tch_call_re_est);call re-establishments

100 -100* ---------------------------------------------------------- %


+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell sdcch_tch);(DR calls)



- sum(b.sdcch_call_re_est+b.tch_call_re_est);call re-establishments


a = p_nbsc_traffic


c = p_nbsc_ho

2.35.20 TCH success ratio, area, after call re-establishment, S6(csf_4s)



sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+a.tch_tr_fail+ a.tch_tr_fail_old+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)

- sum(b.tch_re_est_assign);call re-establishments

100 -100* ---------------------------------------------------------- %

NTC TAN 0936/3 en



s

sum(a.tch_norm_seiz); calls started directly in the cell





a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

2.35.21 TCH success ratio, BTS, after call re-establishment,(csf_4t)


Known problems: Seedcr_3d .

sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+a.tch_tr_fail+ a.tch_tr_fail_old+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)

-sum(b.tch_re_est_assign);call re-establishments

100 -100* -------------------------------------------------------- %







a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho

2.35.22 TCH success ratio, area, before call re-establishment,S7(csf_4u)


Known problems: Seedcr_3g . The impact of call re-establishment inot yet taken into account.

100-dcr_dcr_3i =

sum(a.tch_radio_fail + a.tch_rf_old_ho + a.tch_abis_fail_call +a.tch_abis_fail_old +

a.tch_a_if_fail_call + a.tch_a_if_fail_old + a.tch_tr_fail +a.tch_tr_fail_old +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)

100 -100* --------------------------------------------------------- %



- sum(a.succ_tch_seiz_for_dir_acc);ref.2

NTC TAN 0936/3 en



TRX

on

-nd

TRX



a = p_nbsc_traffic

c = p_nbsc_ho


2.35.23 TCH success ratio, area, after call re-establishment, S7(csf_4v)


Known problems: 1) It is assumed that call re-establishments happenTCH. In fact they may happen also on SDCCH.

2) On cell level it can happen that the call is reestablished in a different cell than it was dropped athis causes inaccuracy.

100-dcr_3j=

sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+a.tch_tr_fail_old+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)

- sum(b.tch_re_est_assign) ;call re-establishments

100 -100* ----------------------------------------------------------- %

sum(a.tch_norm_seiz) ;calls started directly in the cell


- sum(a.tch_succ_seiz_for_dir_acc) ;ref.2




a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho


2.35.24 TCH success ratio, BTS, after call re-establishment,(csf_4x)



NTC TAN 0936/3 en



TRX

TRX

sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+a.tch_tr_fail_old+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

-sum(b.tch_re_est_assign) ;call re-establishments

100 -100* ----------------------------------------------------------- %





+ sum(c.msc_i_tch_tch+c.bsc_i_tch_tch) ;(TCH-TCH Ho in)



a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_ho


2.35.25 TCH success ratio, BTS, before call re-establishment,(csf_4y)



100-dcr_4e=

sum(a.tch_radio_fail+a.tch_rf_old_ho+a.tch_abis_fail_call+a.tch_abis_fail_old+a.tch_a_if_fail_call+ a.tch_a_if_fail_old+ a.tch_tr_fail+a.tch_tr_fail_old+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)

100 -100* ----------------------------------------------------------- %





+ sum(c.msc_i_tch_tch+c.bsc_i_tch_tch) ;(TCH-TCH Ho in)


a = p_nbsc_traffic

c = p_nbsc_ho


NTC TAN 0936/3 en



an

0

) are

2.36 Configuration (cnf)

2.36.1 Reuse pattern (cnf_1)

Experiences onuse: For example, 30/3 = 10 means that the frequency c

be repeated with 10 cells!

The smaller the figure, the better the planning.

Known problems: This indicator can be counted from the NMS/200only for the latest moment (no history).

<nbr of used frequencies > / <average TRXs per cell>

The used frequency means that the TRX and its parents (BTS and BCFunlocked.

NTC TAN 0936/3 en


Missing Counters

ut are

nrs:

R

re,

r

e

3 MISSING COUNTERS

This chapter handles counters that are found to be needed in the formulas bmissing or scheduled for later BSC software releases.

3.1 XX1

Meaning: How many calls were taken from the queue to DR.

Related problem: If a call attempt is in queue, it is taken to DR as sooas the DR target list is ready. In this case counteshow as if the queuing took placetch_qd_call_att is triggered butunsrv_qd_call_att is not.

Planned schedule: S8 (BSC name: REM_FROM_QUEUE_DUE_D,counter ID 1173)

3.2 XX2

Meaning: Clear by MS user during HO procedure.

Related problem: Affects the counting of HO failure ratios. The ratiocannot be counted accurately (seehfr_2 ).

Planned schedule: Open.

3.3 XX3

Meaning: Clear by another procedure during the HO procedufor example assignment.

Related problem: Affects the counting of HO failure ratios. The ratiocannot be counted accurately (seehfr_2 ).

Planned schedule: Open.

3.4 XX4

Meaning: The number of available time slots for TCH (half ofull rate).

Related problem: Without this counter it is not possible to count thTCH availability in case HTCH is used.

Planned schedule: S9.

NTC TAN 0936/3 en


INDEX

ll

l

ll

l

ll

A

A interface blocking 18, 122, 123abbreviations 9

B

BSS formulasava_1a, TCH availability % 109ava_2, average available TCH 109ava_3, average available SDCCH 109ava_4, SDCCH availability % 109ava_5, average available FTCH in area

110ava_6, DMR availability % 110ava_7, DN2 availability % 110ava_8, TRU availability % 110blck_1, TCH raw blocking 74blck_10a, blocked TCH HOs 80blck_10b, blocked TCH HOs 80blck_11a, TCH HO blocking 81blck_11b, TCH HO blocking without Q 81blck_11c, TCH HO blocking 81blck_12, blocked incoming and internal

HO 82blck_12a, blocked incoming and internal

HO 82blck_13, AG blocking 82blck_14, FCS blocking 82blck_15, blocked SDCCH seizure

attempts 83blck_16a, HO blocking % 83blck_16b, handover blocking % 83blck_17, Abis link blocking 83blck_18, blocked FACCH call setup TCH

requests 84blck_19, handover blocking to target cell

84blck_20, handover blocking from target

cell 84blck_5, SDCCH blocking % 74blck_5a, SDCCH real blocking % 74blck_6, TCH raw blocking % on super

TRXs 74blck_7, TCH raw blocking % on regular

TRXs 75blck_8, TCH call blocking, before DR 75

blck_8b, TCH call blocking %, DRcompensated 75

blck_8c, TCH call blocking %, DRcompensated, EFR excluded 77

blck_8d, TCH call blocking %, DR andDAC compensated, EFR excluded78

blck_9b, blocked calls 79blck_9c, blocked calls 80cnf_1, reuse pattern 135cngt_1, TCH congestion time 71cngt_2, SDCCH congestion time 71csf_1, SDCCH access probability, before

FCS 121csf_1a, SDCCH access probability 121csf_2a, SDCCH success ratio 121csf_2f, SDCCH success ratio, area 122csf_2g, SDCCH success ratio, BTS 123csf_2h, SDCCH success ratio, area 124csf_2i, SDCCH success ratio, BTS 125csf_3a, TCH access probability without

DR 126csf_3b, TCH access probability without

DR and Q 126csf_3c, TCH access probability without Q

127csf_3d, TCH access probability, real 127csf_3i, TCH access probability without

DR and Q 127csf_3j, TCH access probability without

DR 128csf_3k, TCH access probability, real 128csf_3l, TCH access probability, real 129csf_4o, TCH success ratio, area, before

call re-establisment 129csf_4p, TCH success ratio, area, after ca

re-establishment 130csf_4q, TCH success ratio, BTS, before

call re-establisment 130csf_4r, TCH success ratio, BTS, after cal

re-establishment 131csf_4s, TCH success ratio, area, after ca

re-establishment 131csf_4t, TCH success ratio, BTS, after cal

re-establishment 132csf_4u, TCH success ratio, area, before

call re-establishment 132csf_4v, TCH success ratio, area, after ca


r
re-establishment 133csf_4x, TCH success ratio, BTS, after call
re-establishment 133csf_4y, TCH success ratio, BTS, before

call re-establishment 134cssr_2, SDCCH, TCH setup success % 20dcf_2, TCH drop calls in HO 24dcf_3, TCH drop calls in BSC outgoing

HO 24dcf_4, TCH drop calls in intra-cell HO 25dcf_6, TCH drop calls in intra-BSC HO 25dcf_7, drop calls in BSC incoming HO 25dcr_10, drops per erlang, before re-

establishment 34dcr_10a, drops per erlang, after re-

establishment 34dcr_10b, drops per erlang, after re-

establishment 35dcr_3f, TCH drop call %, area, real, after

re-establishment 25dcr_3g, TCH drop call %, area, real,

before re-establishment 26dcr_3h, TCH drop call %, area, real, after

re-establishment 27dcr_3i, TCH drop call %, area, real, before

re-establishment 28dcr_3j, TCH drop call %, area, real, after

re-establishment 29dcr_4c, TCH drop-out %, BTS level,

before call re-establishment 30dcr_4d, TCH drop-out %, BTS level,

before call re-establishment 30dcr_4e, TCH drop-out %, BTS level,

before call re-establishment 31dcr_4f, TCH drop-out %, BTS level,

before call re-establishment 31dcr_5, TCH drop call (dropped

conversation) %, BSC level 32dcr_5a, TCH drop call (dropped

conversation) %, area 33dis_1, average MS-BS distance 118dll_1, share % per range 116dlq_1, DL BER 115dlq_2, DL cumulative quality % in class X

115dlq_2a, DL cumulative quality % in class

X 115dr_1, DR, outgoing attempts 107dr_1a, DR attempts 107dr_2, DR, incoming attempts 108dr_3, DR, outgoing success to another cell

108

dr_4, DR, incoming success from anothecell 108

dr_5, DR, intra-cell success 108dr_6, % of new calls successfully handed

over to another cell by DR 108dr_7, DR, outgoing to another cell, failed

108dr_8, DR, intra-cell failed 108ec_1, emergency calls 114ecs_1, emergency call success % 114hfr_1, total HO failure % 43hfr_10, external source HO failure % 53hfr_12, HO failure % from super to regular

53hfr_13, HO failure % from regular to super

53hfr_14, share of HO failures from regular

to super due to return 54hfr_15, share of HO failures from regular

to super due to MS lost 54hfr_16, share of HO failures from regular

to super due to another cause 54hfr_17, share of HO failures from super to

regular due to return 54hfr_18, share of HO failures from super to

regular due to MS lost 55hfr_19, share of HO failures from super to

regular due to another cause 55hfr_2, total HO failure % 44hfr_20, SDCCH-SDCCH HO failure % 55hfr_21, SDCCH-TCH HO failure % 56hfr_22, TCH-TCH HO failure % 56hfr_23, SDCCH-SDCCH incoming HO

failure % 56hfr_24, SDCCH-SDCCH outgoing HO

failure ratio 56hfr_25, SDCCH-TCH incoming HO

failure % 57hfr_26, SDCCH-TCH outgoing HO

failure % 57hfr_27, TCH-TCH incoming HO failure %

57hfr_28, TCH-TCH outgoing HO failure %

57hfr_29, MSC ctrl HO failure % 57hfr_30, MSC ctrl HO failure %, not

allowed 57hfr_31, MSC ctrl HO failure %, return to

old 58hfr_32, MSC ctrl HO failure %, call clear

58hfr_33, MSC ctrl HO failure %, end HO


-

-

-

58hfr_34, MSC ctrl HO failure %, end HO

BSS 58hfr_35, MSC ctrl HO failure %, wrong A

interface 58hfr_36, MSC ctrl HO failure %, adjacent

cell error 58hfr_37, BSC ctrl HO failure %, blocking

59hfr_38, BSC ctrl HO failure %, not

allowed 59hfr_39, BSC ctrl HO failure %, return to

old 59hfr_3a, intra-cell HO failure share 45hfr_3b, intra-cell HO failure share 45hfr_3c, intra-cell HO failure share 46hfr_3d, intra-cell HO failure share 46hfr_4, incoming MSC ctrl HO failure

share 46hfr_40, BSC ctrl HO failure %, call clear

59hfr_41, BSC ctrl HO failure %, end HO 59hfr_42, BSC ctrl HO failure %, end HO

BSS 59hfr_43, BSC ctrl HO failure %, wrong A

interface 59hfr_44, BSC ctrl HO drop call % 60hfr_45, intra-cell HO failure %,

cell_fail_lack 60hfr_46, intra-cell HO failure %, not

allowed 60hfr_47, intra-cell HO failure %, return to

old 60hfr_48, intra-cell HO failure %, call clear

60hfr_49, intra-cell HO failure %, MS lost 60hfr_4a, incoming MSC ctrl HO failure

share 47hfr_4b, incoming MSC ctrl HO failure

share 47hfr_4c, incoming MSC ctrl HO failure

share 47hfr_4d, incoming MSC ctrl HO failure

share 48hfr_50, intra-cell HO failure %, BSS

problem 60hfr_51, intra-cell HO failure %, drop call

60hfr_52, HO failure % to adjacent cell 61hfr_53, HO failure % from adjacent cell 61hfr_54a, HO failure %, blocking excluded

61

hfr_55, HO failure % due to radiointerface blocking 61

hfr_56, intra-cell HO failure %, wrong Ainterface 61

hfr_57, intra-cell HO failure % 62hfr_58, HO failures to target cell 62hfr_59, HO failures from target cell 62hfr_5a, outgoing MSC ctrl HO failure

share 48hfr_5b, outgoing MSC ctrl HO failure

share 48hfr_5c, outgoing MSC ctrl HO failure

share 49hfr_5d, outgoing MSC ctrl HO failure

share 49hfr_6, incoming BSC ctrl HO failure share

49hfr_6a, incoming BSC ctrl HO failure

share 50hfr_6b, incoming BSC ctrl HO failure

share 50hfr_6c, incoming BSC ctrl HO failure

share 50hfr_6d, incoming BSC ctrl HO failure

share 51hfr_7, outgoing BSC ctrl HO failure share

51hfr_7a, outgoing BSC ctrl HO failure

share 51hfr_7b, outgoing BSC ctrl HO failure

share 52hfr_7c, outgoing BSC ctrl HO failure

share 52hfr_7d, outgoing BSC ctrl HO failure

share 52hfr_8, internal inter HO failure % 53hfr_9, internal intra HO failure % 53ho_1, return from super TRXs to regular

TRX 35ho_10, BSC incoming HO attempts 37ho_11, BSC outgoing HO attempts 37ho_13, HO attempts 37ho_13a, HO attempts 37ho_13c, HO attempts, outgoing and intra

cell 37ho_13d, HO attempts, outgoing and intra

cell 37ho_13e, HO attempts, outgoing and intra

cell 38ho_14a, TCH requests for HO 38ho_14b, TCH requests for HO 38ho_15, TCH seizures for HO 38


-

-

ho_16, TCH-TCH HO attempts 38ho_17, SDCCH-TCH HO attempts 39ho_18, SDCCH-SDCCH HO attempts 39ho_19, TCH-TCH HO success 39ho_2, HO attempts from regular TRXs to

super 35ho_20, SDCCH-TCH HO success 39ho_21, SDCCH-SDCCH HO success 39ho_22, MSC controlled HO attempts 40ho_23, BSC controlled HO attempts 40ho_24, intra-cell HO attempts 40ho_25, MSC controlled HO success 40ho_26, BSC controlled HO success 40ho_27, intra-cell HO success 40ho_28, MSC incoming HO success 41ho_29, MSC outgoing HO success 41ho_3, HO attempts from super to regular

35ho_30, BSC incoming HO success 41ho_31, BSC outgoing HO success 41ho_32, incoming HO success 41ho_33, outgoing HO success 41ho_34, outgoing HO attempts 41ho_35, incoming HO attempts 41ho_36, outgoing SDCCH-SDCCH HO

attempts 42ho_37, incoming SDCCH-SDCCH HO

attempts 42ho_38, outgoing SDCCH-TCH HO

attempts 42ho_39, incoming SDCCH-TCH HO

attempts 42ho_4, share of HO attempts from super to

regular due to DL quality 36ho_40, outgoing TCH-TCH HO attempts

42ho_41, incoming TCH-TCH HO attempts

42ho_42, outgoing SDCCH-SDCCH HO

success 42ho_43, incoming SDCCH-SDCCH HO

success 42ho_44, outgoing SDCCH-TCH HO

success 43ho_45, incoming SDCCH-TCH HO

success 43ho_46, outgoing TCH-TCH HO success

43ho_47, incoming TCH-TCH HO success

43ho_5, share of HO attempts from super to

regular due to DL interference 36

ho_6, share of HO attempts from super toregular due to UL interference 36

ho_7, share of HO attempts from super toregular due to bad C/I 36

ho_8, MSC incoming HO attempts 36ho_9, MSC outgoing HO attempts 37hof_1, outgoing HO failures due to lack of

resources 66hof_10, Failed outgoing HO, return to old

68hof_12, outgoing HO failures 68hof_13, intra-cell HO failure, return to old

channel 68hof_14, intra-cell HO failure, drop call 69hof_15, incoming HO failures 69hof_2, incoming HO failures due to lack of

resources 66hof_3, TCH HO failures when return to

old channel was successful 66hof_4, SDCCH HO failures when return to

old channel was successful 67hof_5, MSC incoming HO failures 67hof_6, MSC outgoing HO failures 67hof_6a, MSC outgoing HO failures 67hof_7, BSC incoming HO failures 67hof_7a, BSC incoming HO failures 68hof_8, BSC outgoing HO failures 68hof_8a, BSC outgoing HO failures 68hof_9a, intra-cell HO failures 68hsr_1, MSC controlled outgoing SDCCH

SDCCH HO success % 63hsr_10, MSC controlled incoming

SDCCH-SDCCH HO success %64

hsr_11, MSC controlled incomingSDCCH-TCH HO success % 64

hsr_12, MSC controlled incoming TCH-TCH HO success % 64

hsr_13, BSC controlled incomingSDCCH-SDCCH HO success %65

hsr_14, BSC controlled incomingSDCCH-TCH HO success % 65

hsr_15, BSC controlled incoming TCH-TCH HO success % 65

hsr_16, BSC controlled incoming HOsuccess % 65

hsr_17, MSC controlled incoming HOsuccess % 65

hsr_18, incoming HO success % 65hsr_19, outgoing HO success % 65hsr_2, MSC controlled outgoing SDCCH


t

s

s

ts

14

TCH HO success % 63hsr_20, intra-cell SDCCH-SDCCH HO

success % 66hsr_21, intra-cell SDCCH-TCH HO

success % 66hsr_22, intra-cell TCH-TCH HO success

% 66hsr_3, MSC controlled outgoing TCH-

TCH HO success % 63hsr_4, BSC controlled outgoing SDCCH-

SDCCH HO success % 63hsr_5, BSC controlled outgoing SDCCH-

TCH HO success % 63hsr_6, BSC controlled outgoing TCH-

TCH HO success % 64hsr_7, intra-cell SDCCH-SDCCH HO

success % 64hsr_8, intra-cell SDCCH-TCH HO

success % 64hsr_9, intra-cell TCH-TCH HO success %

64itf_1, UL interference, BTS level 69itf_2, idle TSL percentage of time in band

X, TRX level, IUO 70itf_3, UL interference from IUO, TRX

level 70itf_4, UL interference from Power

Control, TRX level 70lb_1, link balance 119lb_10, average DL signal strength 120lb_11, average MS power attenuation 121lb_12, average BS power attenuation 121lb_2, share in acceptance range 119lb_3, share in normal 119lb_4, share in MS limited 119lb_5, share in BS limited 119lb_6, share in maximum power 120lb_7, average MS power attenuation 120lb_7b, average MS power 120lb_9, average UL signal strength 120lev_1, average DL signal strength 118lev_1a, average DL signal strength 118lev_2, average UL signal strength 118lev_2a, average UL signal strength 118lsr_2, LU success % 113lu_1, number of LU attempts 113lu_2, average of LU attempts per hour 113lu_3, number of LU attempts 113moc_1, SDCCH seizures for MO calls 102moc_2, successful MO speech calls 102moc_3, successful MO data calls 102moc_4, MO call success ratio 103

moc_5, MO speech call attempts 103moc_6, MO call bids 103mtc_1, SDCCH seizures for MT calls 103mtc_2, successful MT speech calls 104mtc_3, successful MT data calls 104mtc_4, MT call success ratio 104mtc_5, MT speech call attempts 104mtc_6, MT call attempts 105pgn_1, number of paging messages sen

105pgn_2, paging buffer size average 105pgn_3, average paging buffer space 106pgn_4, paging success ratio 106pwr_1, average MS power 117pwr_1b, average MS power 117pwr_2, average BS power 117que_1, queued, served TCH call request

% 71que_2, queued, served TCH HO request

% 72que_2a, queued, served TCH HO reques

% 72que_3, successful queued TCH requests

72que_4, successful non-queued TCH

requests 72que_5, successful queued TCH HO

requests 73que_6, successful non-queued TCH HO

requests 73que_7, non-queued, served TCH call

requests % 73que_8, non-queued, served TCH HO

requests % 73que_8a, non-queued, served TCH HO

requests % 73rach_1, average RACH slot 12rach_2, peak RACH load, average 12rach_3, peak RACH load % 13rach_4, average RACH load % 13rach_5, average RACH busy 13rach_6, RACH rejected due to illegal

establishment cause, 14re_1, call re-establishment attempts 114re_2, call re-establishments 114res_1, call re-establishment success % 1sd_1, ghosts detected on SDCCH and

other failures 14sd_1a, ghosts detected on SDCCH and

other failures 14sdr_1a, SDCCH drop %, blocking

excluded 18


l

l

sdr_2, SDCCH drop %, blocking & Abisfailure excluded 19

sdr_3a, illegal establishment cause % 19sms_1, SMS establishment failure % 106sms_2, SMS TCH establishment failure %

106sms_3, SMS SDCCH establishment

failure % 106sms_4, SMS establishment attempts 107sms_5, SMS SDCCH establishment

attempts 107sms_6, SMS TCH establishment attempts

107trf_1, TCH traffic sum 84trf_10, super TRX TCH traffic 88trf_10a, sum of super TRX TCH traffic 89trf_11, average SDCCH traffic, erlang 89trf_11a, average SDCCH traffic, erlang 89trf_12, average TCH traffic, erlang 89trf_12a, average TCH traffic, erlang 89trf_12b, average TCH traffic, erlang 90trf_13b, handover/call % 90trf_13c, intra-cell handover/call % 90trf_13d, handover/call % 91trf_14b, IUO, average TCH seizure length

on super TRXs 91trf_15b, IUO, average TCH seizure length

on regular TRXs 91trf_16, average TRX traffic, IUO 92trf_17a, average TRX TCH seizure length,

IUO 92trf_17b, average TRX TCH seizure length,

IUO 92trf_18, TCH requests for a new call 92trf_18a, TCH requests for a new call 92trf_19, peak busy TCH 92trf_1a, TCH traffic sum 85trf_20, average unit load 93trf_21, call time difference between TRXs

93trf_21a, call time difference between

TRXs 93trf_23a, number of mobiles located in a

cell, BSC 94trf_24b, total TCH seizure time (call time

in seconds) 95trf_24c, total TCH seizure time (call time

in hours) 95trf_25, SDCCH true seizures 95trf_25a, SDCCH true seizures 95trf_26, SDCCH true seizures for call and

SS 95

trf_27, SDCCH true seizures for call 96trf_28, peak busy SDCCH seizures 96trf_29, IUO layer usage % 96trf_2d, average call length 85trf_3, TCH usage 85trf_30, SDCCH seizures 96trf_32, call time (minutes) from

p_nbsc_res_avail 96trf_32a, call time from p_nbsc_rx_qual 97trf_32b, call time from

p_nbsc_rx_statistics 97trf_33, SDCCH HO seizure % out of HO

seizure attempts 97trf_34, SDCCH assignment % out of HO

seizure attempts 97trf_35, TCH HO seizure % out of TCH HO

seizure request 98trf_36, TCH norm seizure % out of TCH

call request 98trf_36a, TCH normal seizure % out of

TCH call requests 98trf_37, TCH FCS seizure % out of TCH

FCS attempts 98trf_38, TCH FCS seizure % out of

congested SDCCH seizureattempts 98

trf_39, TCH seizures for new calls 99trf_39a, TCH seizures for new calls 99trf_3b, FTCH usage 86trf_4, average SDCCH holding time 86trf_40, HTCH usage 99trf_41, MOC rate 99trf_42, MTC rate 100trf_43, TCH single band subscriber

holding time 100trf_44, TCH dual band subscriber holding

time 100trf_46, TCH data call seizures 100trf_47, share of single band traffic 100trf_48, share of dual band traffic 100trf_49, call retries due to A interface poo

mismatch 101trf_5, average FTCH holding time 86trf_50, HO retries due to A interface poo

mismatch 101trf_51, TCH single band subscribers’

share of holding time 101trf_52, TCH dual band subscribers’ share

of holding time 101trf_53, calls started as FACCH call setup

102trf_54, SDCCH seizures 102


4

trf_55, TCH normal seizures 102trf_6, TCH seizures for new call (call bids)

86trf_7b, SDCCH usage % 87trf_8, TCH traffic absorption on super 87trf_8a, TCH traffic absorption on super 87trf_9, average cell TCH traffic from IUO

88trf_9a, cell TCH traffic from IUO 88uav_1, average unavailable TSL per BTS

110uav_1a, average unavailable TSL per BTS

110uav_1b, average unavailable TSL per BTS

111uav_2, total outage time 111uav_3, number of outages 111uav_4, share of unavailability due to user

111uav_5, share of unavailability due to

internal reasons 112uav_6, share of unavailability due to

external reasons 112uav_7, TRX unavailability time due to

user 112uav_8, TRX unavailability time due to

internal reasons 112uav_9, TRX unavailability time due to

external reasons 112ull_1, share % per range 117ulq_1, UL BER 115ulq_2, UL cumulative quality % in class X

116ulq_2a, UL cumulative quality % in class

X 116BSS Network Doctor 7BTS group 10

C

countersmissing 136SDCCH drop 15TCH drop call 20

D

documentationBSS Network Doctor 8other Nokia documents 8

dtpad 7

F

formula typesavailability (ava) 109blocking (blck) 74call re-establishment (re) 114call re-establishment success % (res) 11call success (csf) 121configuration (cnf) 135congestion (cngt) 71directed retry (dr) 107distance (dis) 118downlink level (dll) 116downlink quality (dlq) 115drop call failures (dcf) 24emergency call (ec) 114emergency call success % (ecs) 114handover (ho) 35handover failure % (hfr) 43handover failures (hof) 66handover success % (hsr) 63interference (itf) 69level (lev) 118link balance, power, level (lb) 119location updates (lu) 113LU success % (lsr) 113mobile originated calls (moc) 102mobile terminated calls (mtc) 103paging (pgn) 105power (pwr) 117queuing (que) 71random access (rach) 12SDCCH drop failures (sd) 14SDCCH drop ratio (sdr) 18setup success ratio (cssr) 20short message service (sms) 106TCH drop call % (dcr) 25traffic (trf) 84unavailability (uav) 110uplink level (ull) 117uplink quality (ulq) 115

further information 7

G

ghost accesses 18, 19

K

Key Performance Indicator (KPI) 7


M

missing counters 136

P

prerequisitesfor user knowledge 7

T

terms 10typographic conventions

text styles 8

V

vi 7

W

what you need to know first 7where to find more 7


56402563 Nokia KPI Formulas

Documents

Transcript of 56402563 Nokia KPI Formulas