Bss Network Doctor Formulas

Document number/Issue Copyright © Nokia Telecommunications Oy

NTC TAN 0936/2.3 en

1

NOKIA NMS/2000FOR MANAGING CELLULAR NETWORKS

BSS NETWORK DOCTOR FORMULAS

Reference Guide


NTC TAN 0936/2.3 en2

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 1999. All rights reserved.

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

119/JRi J Rissanen J Neva R Roppo5 March 1999 5 March 1999 5 March 1999 23 September 1998

Copyright © Nokia Telecommunications Oy 1999. All rights reserved.



TABLE OF CONTENTS

1 WHAT IS NEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 What You Need to Know First. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 Where to Find More . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.4 Terms and Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 BSS COUNTER FORMULAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1 Random Access (rach) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2 SDCCH Drop Failures (sd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.3 SDCCH Drop Ratio (sdr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.4 Setup Success Ratio (cssr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.5 TCH Drop Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.6 Drop Call Failures (dcf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.7 TCH Drop Call % (dcr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.8 Handover (ho) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.9 Handover Failure % (hfr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.10 Handover Success % (hsr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.11 Handover Failures (hof) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.12 Interference (itf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.13 Congestion (cngt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.14 Queuing (que). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603.15 Blocking (blck). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.16 Traffic (trf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.17 Traffic Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.18 Paging (pgn) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.19 Short Message Service (sms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.20 Directed Retry (dr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.21 Availability (ava) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.22 Unavailability (uav) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.23 Location Updates (lu). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.24 LU Success % (lsr). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.25 Emergency Call (ec). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.26 Emergency Call Success % (ecs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.27 Call Re-establishment (re) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.28 Call Re-establishment Success % (res) . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.29 Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.30 Downlink and Uplink Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.31 Power (pwr) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003.32 Level (lev) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003.33 Distance (dis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.34 Link Balance, Power, Level (lb) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013.35 Call Success (csf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104



3.36 Configuration (cnf). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

4 MISSING COUNTERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.1 XX1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.2 XX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.3 XX3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.4 XX4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

What is New



1 WHAT IS NEW

New formulas

In this Change Note that provides support for BSS Network Doctor version10.4.(x), the following formulas have been added, as compared to version 10.2:

• dcr_10, Drops per erlang, before re-establishment

• dcr_10a, Drops per erlang, after re-establishment

• ho_13e, HO attempts, outgoing and intra-cell

• ho_14b, TCH requests for HO

• que_2a, Queued, served TCH HO requests %

• que_8a, Non-queued, served TCH HO requests %

• blck_8c, TCH call blocking %, DR compensated, EFR excluded

• blck_9b, Blocked calls

• blck_10b, Blocked TCH HOs

• blck_11c, TCH HO blocking

• trf_13d, Handover/call %

• trf_18a, TCH requests for a new call

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

• trf_46, TCH data call seizures

• trf_48, Share of dual band traffic

• trf_49, Call retries due to A interface pool mismatch

• trf_50, HO retries due to A interface pool mismatch

• trf_51, TCH single band subscribers’ share of holding time

• trf_52, TCH dual band subscribers’ share of holding time

• moc_6, MO call bids

• mtc_6, MT call attempts

• uav_2, Total outage time

• uav_3, Number of outages

• csf_3i, TCH access probability without DR and Q

What is New



• csf_3j, TCH access probability without DR

• csf_3k, TCH access probability, real

About This Manual



2 ABOUT THIS MANUAL

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

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

Note:

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

The information contained in this document relates to BSS Network Doctorsoftware version 10.4, Nokia NMS release T10 and to release S6 of the NokiaBSC software. This document should not be used with any other versions of theNokia NMS/2000 or Nokia BSC software.

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

This chapter covers the following topics:

• What you need to know first

• Where to find more

• Typographic conventions

• Concepts and terminology

2.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 are usedfor editing certain configuration files.

2.2 Where to Find More

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

About This Manual



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 in theNMS/2000 database and the records, including counters, in each table.

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

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

2.3 Typographic Conventions

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

2.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.)

About This Manual



Table 1.Text styles in this document

2.4 Terms and Concepts

The lists below presents the terms and abbreviations used in this document.

2.4.1 Abbreviations

Bold text User interface components

Initial Upper-caseLetteringin Italics

Referenced documents

Referenced sections and chapters within a document

<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

About This Manual


NTC TAN 0936/2.3 en10

Table 2.Abbreviations.

2.4.2 Terms

The lists below presents the abbreviations and terms used in this document.

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

About This Manual


NTC TAN 0936/2.3 en11

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 period.Under one day there are hours from 00 to23.

Directed Retry A procedure used in a call set-up phase forassigning a mobile station to a trafficchannel of a cell other than the serving cellwhen 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 aspect(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

BSS Counter Formulas


NTC TAN 0936/2.3 en12

3 BSS COUNTER FORMULAS

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

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

Note:

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

3.1 Random Access (rach)

3.1.1 Average RACH slot, S1 (rach_1)

Use: Indicates the capacity of BTS for RACH bursthandling. Normally shows a constant value because itis dependent on the BTS configuration which doesnot change often.

avg(a.ave_rach_slot/a.res_acc_denom1)

Counters from table(s):p_nbsc_res_access

3.1.2 Peak RACH load, average, S1 (rach_2)

Use: Indicates the absolute peak value during ameasurement period. Correlates strongly with ULinterference.

Experiences onuse: High values may suggest that MSs have problems in

accessing the BTS.

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



NTC TAN 0936/2.3 en13

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

avg(a.peak_rach_load)


3.1.3 Peak RACH load %, S1 (rach_3)

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

max( a.peak_rach_slot )

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

max ( a.ave_rach_slot/a.res_acc_denom1)


3.1.4 Average RACH load %, S1 (rach_4)

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

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

interference is possible.

avg(a.ave_rach_busy/a.res_acc_denom3)

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

avg(a.ave_rach_slot/res_acc_denom1)


3.1.5 Average RACH busy, S1 (rach_5)

Use: This PI indicates roughly the average of the usedRACH slots. If the average approaches the “averageRACH slot” (rach_1 ) there probably are accessproblems and MS users get, more often than usual, 3beeps when trying to start calls.

avg(a.ave_rach_busy/a.res_acc_denom3)


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

sum(a.ghost_ccch_res- a.rej_seiz_att_due_dist)



NTC TAN 0936/2.3 en14


3.2 SDCCH Drop Failures (sd)

3.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. Theseshould comprise statistically 5/8 of all ghosts. Another 3/8 of ghostsare detected already before SDCCH based on some invalidestablishment cause. In GSM2 the ratio 5/8 and 3/8 is not validanymore.

• multiple seizures of SDCCH.

Known problems: This counter includes also IMSI detaches which donot 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)

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_access

3.2.2 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 timing advance

Common in connection with coverageproblems.

Triggered also if the MS user clears thecall in the SDCCH phase.

1004 SDCCH_RF_OLD_HO Transactions have ended due to an oldchannel failure in HO.

For instance, a failure in Directed Retrydrops the call and triggers this counter inthe source cell.



NTC TAN 0936/2.3 en15

1075 SDCCH_ABIS_FAIL_CALL Transactions have ended due to Abisproblems. Missing channel activationack or if no indication of callestablishment has been received.Augmented when the BSC receives anEstablish indication the contents ofwhich are corrupted, or more commonlywhen a timer (T3101, default 3 sec)expires while waiting for the Establishindication. The Establish indication isthe first message sent from the BTS tothe BSC after the MS has successfullyaccessed the SDCCH.

• Ghost seizures which accidentallyhave a valid establishment cause andare detected on SDCCH, incrementthis counter.

• Multiple SDCCH seizures may causethese failures. If the MS has to sendmultiple random accesses for a call orlocation update, it is possible thatthere will be multiple reservations ofSDCCH for one mobile – naturallythe mobile can use only one of theseand the rest will eventually time outand result insdcch_abis_fail_call . Onereason for multiple SDCCH seizurescan be DL interference.

• Too short frequency&BSIC reusedistance may cause HO burst fromone cell to be interpreted as RACHbursts in another cell causing falseSDCCH seizures. This reason may besuspected if there are short, 2 - 3second peaks with high blocking rateon SDCCH.

• A more rare yet possible reason arefailing LUs.

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

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

See #1 for all possible causes. SDCCHobservation may be used to diagnose thecause on cell level. If this occurs in theentire network or BSS areas, use ClearCode measurement for cause analysis.

ID Name Description



NTC TAN 0936/2.3 en16

Table 4.SDCCH Drop Counters

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

3.2.3 Problems with the SDCCH Drop Counters

3.2.3.1 Phantoms affect SDCCH_abis_fail_*

SDCCH drop ratio counts the ratio of all SDCCH failures to SDCCH seizures.Normally most of the seizures are caused because of phantoms which arecounted as SDCCH_abis_fail_call and SDCCH_abis_fail_old . In

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

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

1036 SDCCH_BTS_FAIL Transactions have ended due to BTSproblems. A call is lost when TRX/TSLis blocked with causebts_fail due toFU or CU or BCF fault or BTS or BCFreset.

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

1038 SDCCH_BCSU_RESET Transactions have ended due to BSCUreset (calls are lost when BSCU is reset).


1037 SDCCH_USER_ACT Transactions have ended due to useractions. Time slot or TRX is locked bythe user via the Top-level User Interfaceor BSC MML.


1039 SDCCH_NETW_ACT Transactions have ended due to a changein the radio network configuration(BCCH swap to another TRX) initiatedby the BSC. The cause for theconfiguration change fails or locallyblocked BCCH TRX.


ID Name Description



NTC TAN 0936/2.3 en17

practice, the latter case does not practically occur because SDCCH handovers areusually not used and particularly because phantoms do not perform handover.

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 network thepercentage settled down to around 18-20 per cent. In BTS B9, BTS RACHdetection was improved, and figures well under 10 per cent are now typical.

3.2.3.2 A interface blocking not shown

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

3.3 SDCCH Drop Ratio (sdr)

3.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. A

BTS decodes them from environmental orbackground noise and filters out most of them.However, all of them cannot be filtered out and theRACH request is passed on to the BSC for processingand for the allocation of a SDCCH channel.

The counterghost_ccch_res (3030) is updatedeach time a channel required is rejected because of aninvalid establishment cause. In GSM ph.1 there existaltogether eight establishment causes, three of whichare undefined as invalid, for example,resulting in thatthis counter shows only 3/8 of all the ghost accessesthe BTS has decoded. For the rest, a SDCCH isallocated and this will result insdcch_abis_fail_call failure. Because of ghostattempts the SDCCH drop ratio is high with lowtraffic. As the amount of call attempts increases, theinfluence of ghosts becomes smaller and the dropratio approaches its real value.

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

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



NTC TAN 0936/2.3 en18

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)

Counters from table(s):p_nbsc_traffic

3.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 locationupdates.


sdcch_netw_act +sdcch_bts_fail+


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


- sum(sdcch_abis_call+sdcch_fail_old)


3.3.3 Illegal establishment cause % (sdr_3a)

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

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


3.4 Setup Success Ratio (cssr)

3.4.1 SDCCH, TCH Setup Success %, S4 (cssr_2)

Use: This PI shows the setup success ratio, includingSDCCH 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 between

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 TCHat all. This causes problems in special cases when



NTC TAN 0936/2.3 en19

there are many LUs but few calls. The problems incalls are hidden by a great number of LUs whichreceive SDCCH successfully.

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

Troubleshooting: You can use SDCCH and TCH observations to seewhich one is failing. However, note that this is a time-consuming task.

sum(a.call_setup_failure)

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

sum(a.setup_succ+a.call_setup_failure)

Counters from table(s):p_nbsc_service

3.5 TCH Drop Failures

3.5.1 TCH Drop Call counters

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

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 been receivedbut Assignment Complete has not beenreceived

This counter is typical in connection withcoverage problems. This failure type isusually the dominating one.

1014 TCH_RF_OLD_HO Same as above but when trying to return tothe old channel in HO.



NTC TAN 0936/2.3 en20

1084 TCH_ABIS_FAIL_CALL • missing ack of channel activation

• missing establishment indication

• reception of error indication

• corruption of messages

• measurement results no longer receivedfrom 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 can befaulty or their TCH TRX suffers from badinterference (TCH assignment fails).

See #1 for all possible causes that triggerthis counter.

Note: If FACCH call setup is used, wemay expect that we start to see ghostseizures incrementing this counter becausethe signalling tries to use SDCCH insteadof TCH.

The portion of this failure decreased fromS4 to S5. Double counting of a coprocessfailure was causing higher values in S4.

1085 TCH_ABIS_FAIL_OLD Same as above but when trying to return tothe old channel in HO.

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

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

Note:There have been cases where the MSC ofanother vendor in inter-MSC handovershas caused high values even though thehandovers have been successful.

See #1 for all possible causes that triggerthis counter.

ID Name Description



NTC TAN 0936/2.3 en21

1088 TCH_A_IF_FAIL_OLD Same as above but when trying to return tothe 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 call attempt

This counter is updated only when BTSsends a "connection failure" with cause"remote trascoder failure" and the call isreleased due to this.

Note:If this failure is related to a transcoder, youcan see its share to be high for one BSC.Another possibility is that the problem liesin a BTS. Also interruptions of thetransmission may cause this failure (alarmsmay be filtered out in a BSC or OMC toreduce the number of alarms due todisturbance).

In analysing the problem, you may find ithelpful to check the pattern over a longerperiod 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 return tothe old channel in HO.

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, BCF reset,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.

ID Name Description



NTC TAN 0936/2.3 en22

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 triggeredby many different causes. To analyse the case in question, TCH observationsmay be used. As there are limitations on how to set the observations, the analysisis more time-consuming.

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

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

3.5.2 Drop Call Ratio

Drop call ratio is counted as the ratio of the sum of the above named counters toall TCH seizures for a new call. This ratio is used in reports for network or maintenance region level. Seedcr_3* .

3.5.3 Drop-out Ratio

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

3.5.4 Problems with the Counters

3.5.4.1 TCH Tr, Abis failures

These failures can contain also situations when timer T3109 (8 to 15 s, default 12s) expires in a BSC in the call release phase while waiting for the Releaseindication. With BTS software 6.0 these were seen as TC failures, whereas since

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/2.3 en23

BTS software 6.1 they have been Abis failures. The MS user does not see thesefailures as real drop calls.

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

3.5.4.2 TCH_A_IF_OLD high

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

3.6 Drop Call Failures (dcf)

3.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)


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

Known problems: Accuracy is not good.

sum(a.bsc_o_drop_calls)

Counters from table(s):p_nbsc_ho

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


sum(a.cell_drop_calls)


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

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

sum(bsc_i_drop_calls+bsc_o_drop_calls+cell_drop_calls)




NTC TAN 0936/2.3 en24

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


sum(a.bsc_i_drop_calls)


3.7 TCH Drop Call % (dcr)

3.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 markedly

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

Known problems: Seedcr_3g . It is assumed that call re-establishmentshappen on TCH. In fact they may happen also onSDCCH.

. 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) ;(DRcalls)

+ 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)

Counters from table(s):

a = p_nbsc_traffic

b = p_nbsc_res_access

c = p_nbsc_ho

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


Experiences onuse: In good networks where optimisation has been done

already for two to three years, values have beenaround 2 to 3 per cent (and in networks in which nooptimisation has been done yet, the values remain



NTC TAN 0936/2.3 en25

even above 10 per cent). A value of 5 per cent isachievable in many networks despite their bad initialcoverage planning.

Interference also raises the figure. Be careful whensetting the target values since the factors (whethercaused by the customer or Nokia) can be time-consuming and expensive to prove. If used on celllevel, the values can be even over 100 per cent if a celltakes HOs in but then drops them.

Known problems: Some failures in the release phase are included in thisformula (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 onTCH. It means that TCH has been successfullyseized. Some mobiles never appear to the TCHbecause:

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

• the mobile fails or

• something else goes wrong.

TCH failure counters are not triggered if the call iscleared by pre-emption (1st priority call requested tobe established, all TCH seized, lower priority callson) whereasp_nbsc-service_dropped_call istriggered.

. 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

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


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


Counters from table(s):a = p_nbsc_traffic

c = p_nbsc_ho

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

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



NTC TAN 0936/2.3 en26

Known problems: Seedcr_3g .

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_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)


c = p_nbsc_ho

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

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






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



+ 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 netto in fromother cells)


c = p_nbsc_ho

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

Use: On the area level. Tells the ratio of calls droppedwhile 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 (handovers).Accurate on the BSC and PLMN levels after a bugwas corrected.



NTC TAN 0936/2.3 en27

If call re-establishment is active and occurs, theconver_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 callstays or drops. This means that in this case seen fromcounters, the call looks like a dropped call. In fact,from the MS user’s point of view it is impossible toknow whether it was dropped or not (does callre_establishment save the call or not).

Subscriber clear during HO is counted as a droppedcall.

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

In the NMS/2000 T8 thep_nbsc_service table didhave wrong index settings (a bug in the upgradescript) and therefore the use of the table was veryslow.

External HOs (inter BSC handovers) triggerconver_started counter in target cell. Thereforeon network level the ratio does not illustrate correctlythe dropped conversation ratio from the MS’s point ofview.

sum(a.dropped_calls)

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

sum(a.conver_started)


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

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

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

Known problems: Seedcr_5 .



NTC TAN 0936/2.3 en28

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

dropped_calls is triggered once for the first re-establishment. After thatsetup_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 requestto be established, all TCHs seized, lower prioritycalls on) triggersdropped_calls . Therefore thiscounter does not indicate only technical drops.

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

sum(b.dropped_calls)

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

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

Counters from table(s):a = p_nbsc_ho

b = p_nbsc_service

3.7.7 Drops per erlang, before re-establishment, S4 (dcr_10)

Known problems: Works for 60 min period.

Use: On the area and BTS level.

Drops

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

Traffic (Erlang hours sum)





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

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

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_avail

3.7.8 Drops per erlang, after re-establishment, S4 (dcr_10a)

Known problems: Works for 60 min period.

Use: On the area and BTS level.

Drops- re-establishments

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



NTC TAN 0936/2.3 en29

Traffic (Erlang hours sum)





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

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

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


b = p_nbsc_res_avail

c = p_nbsc_res_access

3.8 Handover (ho)

3.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)

Counters from table(s):p_nbsc_underlay

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

sum(a.ho_att_from_reg_freq)


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

sum(a.ho_att_to_reg_freq)


3.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)


3.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



NTC TAN 0936/2.3 en30

+a.att_from_super_ul_if + a.att_from_super_bad_ci)


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

sum(a.att_from_super_ul_qual)

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)


3.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)


3.8.8 MSC incoming HO attempts (ho_8)

sum(msc_i_tch_tch_at+msc_i_sdcch_tch_at+msc_i_sdcch_at)


3.8.9 MSC outgoing HO attempts (ho_9)

sum(a.msc_o_tch_tch_at+a.msc_o_sdcch_tch_at+a.msc_o_sdcch_at)


3.8.10 BSC incoming HO attempts (ho_10)

sum(bsc_i_tch_tch_at+bsc_i_sdcch_tch_at+bsc_i_sdcch_at)


3.8.11 BSC outgoing HO attempts (ho_11)

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


3.8.12 HO attempts, S4 (ho_13)

sum(cause_up_qual+cause_up_level+cause_down_qual+cause_down_lev+cause_distance



NTC TAN 0936/2.3 en31

+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)


3.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)


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


+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

)


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


+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

)


3.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(cell_tch_tch_at + cell_sdcch_tch_at+ cell_sdcch_at)

3.8.17 TCH requests for HO (ho_14a)

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


3.8.18 TCH requests for HO, (ho_14b)

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)



NTC TAN 0936/2.3 en32


b = p_nbsc_ho

3.8.19 TCH seizures for HO (ho_15)

sum(a.tch_ho_seiz)


3.8.20 TCH-TCH HO attempts (ho_16)

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

sum( a.msc_o_tch_tch_at + a.msc_i_tch_tch_at

+ a.bsc_o_tch_tch_at + a.bsc_i_tch_tch_at

+ a.cell_tch_tch_at)


3.8.21 SDCCH-TCH HO attempts (ho_17)


sum( a.msc_o_sdcch_tch_at + a.msc_i_sdcch_tch_at

+ a.bsc_o_sdcch_tch_at + a.bsc_i_sdcch_tch_at

+ a.cell_sdcch_tch_at)


3.8.22 SDCCH-SDCCH HO attempts (ho_18)


sum( a.msc_o_sdcch_at + a.msc_i_sdcch_at

+ a.bsc_o_sdcch_at + a.bsc_i_sdcch_at

+ a.cell_sdcch_at)


3.8.23 TCH-TCH HO success (ho_19)


sum( a.msc_o_tch_tch + a.msc_i_tch_tch + a.bsc_o_tch_tch +a.bsc_i_tch_tch

+ a.cell_tch_tch)



NTC TAN 0936/2.3 en33


3.8.24 SDCCH-TCH HO success (ho_20)


sum( a.msc_o_sdcch_tch + a.msc_i_sdcch_tch + a.bsc_o_sdcch_tch +a.bsc_i_sdcch_tch

+ cell_sdcch_tch)


3.8.25 SDCCH-SDCCH HO success (ho_21)


sum( a.msc_o_sdcch + a.msc_i_sdcch + a.bsc_o_sdcch + a.bsc_i_sdcch

+ a.cell_sdcch)


3.8.26 MSC controlled HO attempts (ho_22)


sum( a.msc_o_tch_tch_at + a.msc_i_tch_tch_at

+ a.msc_o_sdcch_tch_at + a.msc_i_sdcch_tch_at

+ a.msc_o_sdcch_sdcch_at + a.msc_i_sdcch_sdcch_at)


3.8.27 BSC controlled HO attempts (ho_23)


sum( a.bsc_o_tch_tch_at + a.bsc_i_tch_tch_at

+ a.bsc_o_sdcch_tch_at + a.bsc_i_sdcch_tch_at

+ a.bsc_o_sdcch_sdcch_at + a.bsc_i_sdcch_sdcch_at)


3.8.28 Intra-cell HO attempts (ho_24)

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




NTC TAN 0936/2.3 en34

3.8.29 MSC controlled HO success (ho_25)


sum( a.msc_o_tch_tch + a.msc_i_tch_tch

+ a.msc_o_sdcch_tch + a.msc_i_sdcch_tch

+ a.msc_o_sdcch_ + a.msc_i_sdcch)


3.8.30 BSC controlled HO success (ho_26)


sum( a.bsc_o_tch_tch + a.bsc_i_tch_tch

+ a.bsc_o_sdcch_tch + a.bsc_i_sdcch_tch

+ a.bsc_o_sdcch + a.bsc_i_sdcch)


3.8.31 Intra-cell HO success (ho_27)

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


3.8.32 MSC incoming HO success (ho_28)

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


3.8.33 MSC outgoing HO success (ho_29)

sum(a.msc_o_tch_tch+a.msc_o_sdcch_tch+a.msc_o_sdcch)


3.8.34 BSC incoming HO success (ho_30)

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


3.8.35 BSC outgoing HO success (ho_31)

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




NTC TAN 0936/2.3 en35

3.8.36 Incoming HO success (ho_32)

sum(a.msc_i_succ_ho+a. bsc_i_succ_ho)


3.8.37 Outgoing HO success (ho_33)

sum(a.msc_o_succ_ho+ a.bsc_o_succ_ho)


3.8.38 Outgoing HO attempts (ho_34)

sum(a.msc_o_tch_tch_at+a.msc_o_sdcch_tch_at+a.msc_o_sdcch_at

+a.bsc_o_tch_tch_at+a.bsc_o_sdcch_tch_at+a.bsc_o_sdcch_at)


3.8.39 Incoming HO attempts (ho_35)

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

+a.bsc_i_tch_tch_at+a.bsc_i_sdcch_tch_at+a.bsc_i_sdcch_at)


3.8.40 Outgoing SDCCH-SDCCH HO attempts (ho_36)

sum(a.msc_o_sdcch_at+a.bsc_o_sdcch_at)


3.8.41 Incoming SDCCH-SDCCH HO attempts (ho_37)

sum(a.msc_i_sdcch_at+a.bsc_i_sdcch_at)


3.8.42 Outgoing SDCCH-TCH HO attempts (ho_38)

sum(a.msc_o_sdcch_tch_at+a.bsc_o_sdcch_tch_at)


3.8.43 Incoming SDCCH-TCH HO attempts (ho_39)

sum(a.msc_i_sdcch_tch_at+a.bsc_i_sdcch_tch_at)




NTC TAN 0936/2.3 en36

3.8.44 Outgoing TCH-TCH HO attempts (ho_40)

sum(a.msc_o_tch_tch_at+a.bsc_o_tch_tch_at)


3.8.45 Incoming TCH-TCH HO attempts (ho_41)

sum(a.msc_i_tch_tch_at+a.bsc_i_tch_tch_at)


3.8.46 Outgoing SDCCH-SDCCH HO success (ho_42)

sum(a.msc_o_sdcch+a.bsc_o_sdcch)


3.8.47 Incoming SDCCH-SDCCH HO success (ho_43)

sum(a.msc_i_sdcch+a.bsc_i_sdcch)


3.8.48 Outgoing SDCCH-TCH HO success (ho_44)

sum(a.msc_o_sdcch_tch+a.bsc_o_sdcch_tch)


3.8.49 Incoming SDCCH-TCH HO success (ho_45)

sum(a.msc_i_sdcch tch+a.bsc_i_sdcch_tch)


3.8.50 Outgoing TCH-TCH HO success (ho_46)

sum(a.msc_o_tch_tch+a.bsc_o_tch_tch)


3.8.51 Incoming TCH-TCH HO success (ho_47)

sum(a.msc_i_tch_tch+a.bsc_i_tch_tch)




NTC TAN 0936/2.3 en37

3.9 Handover Failure % (hfr)

3.9.1 Total HO failure %, S1 (hfr_1)

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

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

cent, whereas in a very bad network values higherthan 15 per cent may occur. When IUO is used, thisformula shows high values due to highly failing intra-cell handovers between layers in congested cells.

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

Blocking is included. Blocking makes this indicatorshow high values especially in the case of IUO, but itdoes not necessarily mean that there are someproblems.

HO failures

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

HO attempts

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)


p_nbsc_ho

3.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 % of

hfr_1 . In a good network the value can be less than



NTC TAN 0936/2.3 en38

3 per cent, while in a very bad network values higherthan 15 per cent may occur.

If Directed Retry is enabled, the MS may, whencongestion of the source cell SDCCH occurs, bemoved from the best cell to a worse one. Then the MStries to make a handover back but fails if the first cellis still congested. This leads to incrementation of theHO failure ratio.

Known problems: Blocking is included. Blocking makes this indicatorshow high values especially in the case of IUO, but itdoes not necessarily mean that there are sometechnical problems.

Calls that are cleared by the MS user during the HOprocess increment the attempt counters but cannot becompensated in the numerator. (XX2)

HO that is interrupted due to another procedure (e.g.assignment) increments the attempt counters butcannot be compensated in the numerator.(XX3)

HO failures

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

HO attempts

HO attempts - successful HOs

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

HO attempts

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

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

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* (------------------------------------------------------------) %






NTC TAN 0936/2.3 en39


+ sum(cell_tch_tch_at + cell_sdcch_tch_at + cell_sdcch_at)


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


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* (------------------------------------------------------------) %





3.9.5 Incoming MSC ctrl HO failure %, 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)


3.9.6 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* (------------------------------------------------------------) %









NTC TAN 0936/2.3 en40

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


MSC controlled incoming HO failures

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* (------------------------------------------------------------) %





3.9.8 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* (------------------------------------------------------------) %







3.9.9 Outgoing MSC ctrl HO failure share %, S1 (hfr_5b)


MSC controlled outgoing HO failures

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)

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







NTC TAN 0936/2.3 en41

3.9.10 Incoming BSC ctrl HO failure %, 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- ---------------------------------------------------------) %

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


3.9.11 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* (------------------------------------------------------------) %







3.9.12 Incoming BSC ctrl HO failure %, S1 (hfr_6b)


BSC controlled incoming HO failures

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* (------------------------------------------------------------) %





3.9.13 Outgoing BSC ctrl HO failure %, S1 (hfr_7)

BSC controlled outgoing HO successes

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

BSC controlled outgoing HO attempts



NTC TAN 0936/2.3 en42

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)


3.9.14 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* (------------------------------------------------------------) %







3.9.15 Outgoing BSC ctrl HO failure share %, S1 (hfr_7b)


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* (-----------------------------------------------------------) %





3.9.16 Internal inter HO failure %, S4 (hfr_8)

sum(int_inter_ho_source_fail)

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

sum(int_inter_ho_source_fail+int_inter_ho_succ)


3.9.17 Internal intra HO failure %, S4 (hfr_9)

sum(int_intra_ho_source_fail)



NTC TAN 0936/2.3 en43

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

sum(int_intra_ho_source_fail+int_intra_ho_succ)


3.9.18 External source HO failure %, S4 (hfr_10)

sum(ext_ho_source_fail)

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

sum(ext_ho_source_fail+ ext_ho_source_succ)


3.9.19 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)


3.9.20 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)


p_nbsc_underlay

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

sum(ho_fail_from_reg_due_ret)

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



p_nbsc_underlay

3.9.22 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 superTRX.

sum(ho_fail_from_reg_ms_lost)

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




NTC TAN 0936/2.3 en44


p_nbsc_underlay

3.9.23 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) inHOs from regular to super TRX.

sum(ho_fail_from_reg_freq)

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



3.9.24 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 regularTRX.

sum(ho_fail_to_reg_due_ret)100* (----------------------------------------------------------------------------) %



3.9.25 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 regularTRX.

sum(ho_fail_to_reg_ms_lost)100* (----------------------------------------------------------------------------) %



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

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

‘return’ and ‘MS lost’.

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



NTC TAN 0936/2.3 en45

sum(ho_fail_to_reg_freq)

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



3.9.27 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

+ bsc_i_sdcch_at + bsc_o_sdcch_at

+ cell_sdcch_at)


3.9.28 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)


3.9.29 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)



NTC TAN 0936/2.3 en46


3.9.30 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)


3.9.31 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)


3.9.32 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)


3.9.33 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)


3.9.34 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)


3.9.35 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)


3.9.36 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)



NTC TAN 0936/2.3 en47


3.9.37 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)


3.9.38 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)


3.9.39 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)


3.9.40 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)


3.9.41 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)


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

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

100* msc_controlled_out_ho /(msc_o_sdcch_at+msc_o_sdcch_tch_at+msc_o_tch_tch_at)


3.9.43 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)


p_nbsc_ho



NTC TAN 0936/2.3 en48

3.9.44 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)


3.9.45 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)


3.9.46 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)


3.9.47 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)


3.9.48 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)


3.9.49 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)


3.9.50 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)


3.9.51 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)



NTC TAN 0936/2.3 en49


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

100* cell_fail_lack /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


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

100* cell_not_allwd /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


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

100* cell_fail_ret /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


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

100* cell_call_clr /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


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

100* cell_fail_move /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


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

100* cell_fail_bss /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


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

100* cell_drop_calls /(cell_sdcch_at+cell_sdcch_tch_at+cell_tch_tch_at)


3.9.59 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



NTC TAN 0936/2.3 en50

3.9.60 HO failure % from adjacent cell (hfr_53)

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


3.9.61 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 * ------------------------------------------------------%






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



sum(msc_o_fail_lack+bsc_o_fail_lack+cell_fail_lack)

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






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


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




NTC TAN 0936/2.3 en51

3.9.64 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)


3.9.65 HO failures to target cell, S6 (hfr_58)

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

Known problems: Not accurate because of:

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

2. HO that is interrupted due to other procedure (e.g. assignment)increments attempt counters but cannot be compensated in thenumerator.

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)


3.9.66 HO failures from target cell, S6 (hfr_59)

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

Known problems: Not accurate because of:

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

2. HO that is interrupted due to other procedure (e.g. assignment)increments attempt counters but cannot be compensated in thenumerator.

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)



NTC TAN 0936/2.3 en52


3.10 Handover Success % (hsr)

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

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


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

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


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

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


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

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


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

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


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

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




NTC TAN 0936/2.3 en53

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

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


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

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


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

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


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

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


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

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


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

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


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

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




NTC TAN 0936/2.3 en54

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

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


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

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


3.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) %


3.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) %


3.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) %


3.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) %


3.10.20 Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20)

sum(cell_sdcch)

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

sum(cell_sdcch_at)




NTC TAN 0936/2.3 en55

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

sum(cell_sdcch_tch)

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

sum(cell_sdcch_tch_at)


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

sum(cell_tch_tch)

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

sum(cell_tch_tch_at)


3.11 Handover Failures (hof)

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

sum(a.BSC_o_fail_lack+a.MSC_o_fail_lack)


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

sum(a.BSC_i_fail_lack+a.MSC_i_fail_lack)


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

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

= sum(tch_rf_new_ho + tch_abis_fail_new + tch_a_if_fail_new + tch_tr_fail_new)

- sum(tch_rf_old_ho + tch_abis_fail_old + tch_a_if_fail_old + tch_tr_fail_old)


p_nbsc_traffic

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

Handovers failed in going to new channel - Handovers failed to return to old 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



NTC TAN 0936/2.3 en56

3.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)


3.11.6 MSC outgoing HO failures (hof_6)


- msc_o_tch_tch+msc_o_sdcch_tch+msc_o_sdcch)


3.11.7 MSC outgoing HO failures (hof_6a)

sum(a.msc_o_tch_tch_at+a.msc_o_sdcch_tch_at+a.msc_o_sdcch_at

- a.msc_o_succ_ho)


3.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_tch_tch+bsc_i_sdcch_tch+bsc_i_sdcch)


3.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)


3.11.10 BSC outgoing HO failures (hof_8)

sum(bsc_o_tch_tch_at+bsc_o_sdcch_tch_at+bsc_o_sdcch_at

- bsc_o_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)


3.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_tch_tch+bsc_o_sdcch_tch+bsc_o_sdcch)




NTC TAN 0936/2.3 en57

3.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)


3.11.13 Failed outgoing HO, return to old (hof_10)

sum(msc_o_fail_ret + bsc_o_fail_ret)


3.11.14 Outgoing HO failures (hof_12)

Outgoing HO attempts - Outgoing HO suucesses

= 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)


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

sum(a.cell_fail_ret)


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

sum(a.cell_drop_calls)


3.11.17 Incoming HO failures (hof_15)

Incoming HO attempts - Incoming HO successes

= 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)


3.12 Interference (itf)

3.12.1 UL interference, BTS level, S1 (itf_1)

Use: UL interference is measured as the time-out of lowestband 1 (band 0 in BSC terminology). Band 10 is



NTC TAN 0936/2.3 en58

defined by boundaries 0 and 1 which are BTSparameters. Boundary 0 is fixed, whereas boundary 1can be set.

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

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

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

If band 1 is defined as exceptionally wide, it becomesdifficult 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)

Counters from table(s):p_nbsc_res_avail

3.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 high

values but the UL quality is still excellent. The biggerthe values are in bands towards band 5, the worse theinterference.

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)


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

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

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

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

sum(ave_full_tch_if1)

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



NTC TAN 0936/2.3 en59

sum(ave_full_tch_if1 + ave_full_tch_if2 + ave_full_tch_if3

+ ave_full_tch_if4 + ave_full_tch_if5)


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

Use: BTS reports interference of each TCH as bandnumber (0-4, where 0 is the lowest and bandboundaries are defined as cell parameters). BSC sumsup the band numbers (ave_sum_idle_ch_interf )as well as the number of TCHs reported(ave_sum_idle_tch_per_trx ), and from thesefigures an average interference band (0-4) can becalculated. Average interference is shifted by 1 (+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

3.13 Congestion (cngt)

3.13.1 TCH congestion time, S1 (cngt_1)

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

values than SDCCH congestion.

sum(a.tch_cong_time/100)

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

3.13.2 SDCCH congestion time, S1 (cngt_2)

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

smaller values than TCH congestion.

sum(a.sdcch_cong_time/100)

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



NTC TAN 0936/2.3 en60

3.14 Queuing (que)

3.14.1 Queued, served TCH call requests % (que_1)

Use: Indicates the quota of TCH call requests seizing theTCH 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 DR toanother 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) beforethe queuing timer expires.

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

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

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

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

sum(a.tch_call_req)

Counters from table(s):p_nbsc_trafficXX1 is the number of calls taken from the queue to DR.

3.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 reasonis lost (the MS user is hanging, for example) beforethe queuing 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)


3.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 reasonis lost (the MS user is hanging, for example) beforethe queuing timer expires.



NTC TAN 0936/2.3 en61

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)


b = p_nbsc_handover

3.14.4 Successful queued TCH requests (que_3)

sum(a.tch_qd_call_att-a.unsrv_qd_call_att)


3.14.5 Successful non-queued TCH requests (que_4)

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


3.14.6 Successful queued TCH HO requests (que_5)

sum(a.tch_qd_ho_att-a.unsrv_qd_ho_att)


3.14.7 Successful non-queued TCH HO requests (que_6)

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


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

Use: Indicates the quota of TCH call requests seizing theTCH successfully straight without queuing. DR isexcluded (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)


3.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* ------------------------------------------------- %





NTC TAN 0936/2.3 en62

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

Known problems: See que_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)


b = p_nbsc_ho

3.15 Blocking (blck)

3.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 intoconsideration. Rather, it shows only raw blockingincluding also HOs. Blocked HOs are normally not soserious because there are alternatives to go to.Blocked new calls can be lost calls if Directed Retryis not in use.

sum(a.tch_req_rej_lack)

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

sum(a.tch_request)


3.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)


3.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* ----------------------------------------- %



NTC TAN 0936/2.3 en63

a.SDCCH_seiz_attsum(a.SDCCH_seiz_att)


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

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

sum over super TRXs (a.tch_req_rej_lack)

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

sum over super TRXs (a.tch_request)


3.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)


3.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 res. or 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)


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

Use: On the cell level should appear in the busiest cells.The cell needs an urgent capacity extension or has lostpart of its capacity due to a fault.

It is the blocking rate that the customers will noticewhen they are driving in the mobile environmentcaused by the lack of radio resources. It is thereforeone of the most critical KPIs.



NTC TAN 0936/2.3 en64

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

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

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

Note:

2) If Trunk Reservation is used, HO and Callblocking cannot be counted precisely (there is onlyone counter for the case of Trunk ReservationInvocation Refused).

3) The ratio can show too high values in the followingcase: TCH assignment fails if the requested channeltype 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 the A-interface circuit pool. MSC can then decide if there isanother assignment request or call clear(clear_command ).

The second request may again fail or succeed. In BSCthe TCH_REJ_DUE_REQ_CH_A_IF_CRC counteris triggered every time the channel request fails due tothe above-mentioned reason.

If Nokia MSC is used, there can be only one retry.With another vendor’s MSC there can be multipleretrys.

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

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

- successful DR

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

all TCH call requests



NTC TAN 0936/2.3 en65


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

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

sum(a.tch_call_req)

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_ho

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

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

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

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

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

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

Note:

2) If Trunk Reservation is used, HO and Callblocking cannot be counted precisely (there is onlyone counter for the case of Trunk ReservationInvocation Refused).

New TCH call requests that are blocked

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

All new call requests

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

- 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/2.3 en66

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

- Aif circuit pool handover failures)


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

- 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 handover failures

+b.msc_controlled_in_ho

+b.ho_unsucc_a_int_circ_type))

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

sum(a.tch_call_req)






a = p_nbsc_traffic

b = p_nbsc_ho

3.15.9 Blocked calls, S2 (blck_9a)

Use: Shows also situations when blocking is caused by afault in the BTS - not only blocking caused purely byhigh traffic.

Known problems: TCH call seizures rejected due to A interface circuitpool mismatch get counted, too.

TCH call requests rejected due to lack of resources or routed by DRto another cell

- successful DR


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

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


b = p_nbsc_ho

3.15.10 Blocked calls, S5 (blck_9b)

Use: Shows also situations when blocking is caused by afault in the BTS - not only blocking caused purely byhigh traffic.

Known problems: TCH call seizures rejected due to A interface circuitpool mismatch get counted, too.

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

- successful DR

- Rejections due to A interface circuit mismatch


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



NTC TAN 0936/2.3 en67

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






a = p_nbsc_traffic

b = p_nbsc_ho

3.15.11 Blocked TCH HOs, S2 (blck_10a)

Use: Replacesblck_10 .

sum(tch_request-tch_call_req-tch_fast_req-tch_ho_seiz)


3.15.12 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

3.15.13 TCH HO blocking, S2 (blck_11a)

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

Note:

2) If Trunk Reservation is used, HO and Call blockingcannot be counted precisely (there is only one counterfor the case of Trunk Reservation InvocationRefused).


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

sum(tch_request-tch_call_req-a.tch_fast_req)


3.15.14 TCH HO blocking without Q, S2 (blck_11b)

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



NTC TAN 0936/2.3 en68

Known problems: Seeque_2 (factorXX1).


+ sum(a.tch_qd_ho_att-XX1-unserv_qd_ho_att)

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

sum(tch_request-tch_call_req-a.tch_fast_req)


3.15.15 TCH HO blocking, S5 (blck_11c)

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

Note:

2) If Trunk Reservation is used, HO and Call blockingcannot be counted precisely (there is only one counterfor the case of Trunk Reservation InvocationRefused).



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




a = p_nbsc_traffic

b = p_nbsc_ho

3.15.16 Blocked incoming and internal HO, S2 (blck_12)

Use: Usable with S4 and earlier.

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


3.15.17 Blocked incoming and internal HO, S2 (blck_12a)

Use: On the area level with S5 and S6.

sum(a.msc_i_fail_lack+ a.bsc_i_fail_lack + cell_fail_lack

+ bsc_i_unsucc_a_int_circ_type+msc_controlled_in_ho+ho_unsucc_a_int_circ_type)




NTC TAN 0936/2.3 en69

3.15.18 AG blocking, S1 (blck_13)

Use: A BSC sends to a BTS an immediate assignment orimmediate assignment rejected commands. If theAccess Grant (AG) buffer in the BTS is full, it willrespond with a delete indication. Thus the ratio ofdelete indications to the sum of immediateassignment and immediate assignment rejecteddescribes the AG blocking.

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


3.15.19 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 %)


3.15.20 Blocked SDCCH seizure attempts, S5 (blck_15)

All blocked - seizures to FACCH setup

sum(sdcch_busy_att - tch_seiz_due_sdcch_con)


3.15.21 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 * ------------------------------------------------





3.15.22 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 notavailable in intra-cell handover, thenho_unsucc_a_int_circ_type is triggered, butthe same channel may be seized successfully afterchanging the handover for external (A interfacecircuit changes).



NTC TAN 0936/2.3 en70


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 * ------------------------------------------------





3.15.23 Abis link blocking (blck_17)

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

3.15.24 Blocked FACCH call setup TCH requests, (blck_18)

sum(a.tch_seiz_att_due_sdcch_con - a.tch_seiz_due_sdcch_con)


3.15.25 Handover blocking to target cell, (blck_19)

100* sum(ho_fail_res_to_adj)/sum(ho_att_to_adj)


3.15.26 Handover blocking from target cell, (blck_20)

100* sum(ho_fail_res_from_adj)/sum(ho_att_from_adj)


3.16 Traffic (trf)

3.16.1 TCH traffic sum, S1 (trf_1)

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

erlangs over a longer period requires that the erlangvalues per hour are first counted and then averaged.

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

The sampling period is 20 s which means that duringthe period of one hour the number of used TCHschecked 180 times. This method is not accurate if we



NTC TAN 0936/2.3 en71

think about short seizures and low traffic, butstatistically the results have been satisfactory.

Does not show calls going to voice mail.

Note:

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

sum(a.ave_busy_tch / a.res_av_denom14)

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

3.16.2 TCH traffic sum, S1 (trf_1a)

Note: Seetrf_1 .

sum_over_area (

sum_over_BTS(a.ave_busy_tch)/ sum_over_BTS(a.res_av_denom14)

)


3.16.3 Average call length, S1 (trf_2d)

Use: On the area level gives you an idea about thebehaviour 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 BSCseizes TCH. Includes some of signalling, ringing and speech.

In the denominator there are also calls that are not answered. The numeratorcounts 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



NTC TAN 0936/2.3 en72

b = p_bsc_traffic

c = p_nbsc_ho

3.16.4 TCH usage, S1 (trf_3)

Use: On the area level gives you an idea of how well thecapacity is used. Use with S4 or earlier, or later if halfrate not yet used.

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)


3.16.5 FTCH usage, S5 (trf_3b)

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

sum(a.ave_tch_busy_full)

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

sum(a.ave_avail_full_TCH/a.res_av_denom2)


3.16.6 Average SDCCH holding time, S1 (trf_4)

Use: The holding time may change due to modification ofthe 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


3.16.7 Average FTCH holding time, S1 (trf_5)

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

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



NTC TAN 0936/2.3 en73

sum(ave_ftch_hold_tim)

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

sum(res_av_denom17)*100


3.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, notDR, not FCS).

sum(p_nbsc_traffic.tch_norm_seiz)


3.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)

Counters from table(s):a = p_nbsc_res_availb = p_nbsc_traffic

3.16.10 TCH traffic absorption on super, S4 (trf_8)


1. First, count the traffic per a TRX.

avg(a.ave_busy_tch)

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

traffic (super)

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

traffic (all)



NTC TAN 0936/2.3 en74


3.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 ---------------------------------------------------- %

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


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


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

avg(a.ave_busy_tch)

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

sum traffic of all TRXs

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

hours


3.16.13 Cell TCH traffic from IUO, S4 (trf_9a)


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




NTC TAN 0936/2.3 en75

3.16.14 Super TRX TCH traffic, S4 (trf_10)


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

avg(a.ave_busy_tch)

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

traffic (super)

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

hours


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


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

3.16.16 Average SDCCH traffic, erlang, S2 (trf_11)

Known problems: SDCCH seizures are too short to be counted by using20 s sampling time.

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

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

nbr of records count(*)


3.16.17 Average SDCCH traffic, erlang, S2 (trf_11a)

Known problems: SDCCH seizures are too short to be counted by using20 s sampling time.

Note: Gives the same results astrf_11 .

avg(a.ave_busy_sdcch / a.res_av_denom15)




NTC TAN 0936/2.3 en76

3.16.18 Average TCH traffic, erlang, S2 (trf_12)

sum of traffic sum(a.ave_busy_tch / a.res_av_denom14)

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

nbr of records count(*)


3.16.19 Average TCH traffic, erlang, S2 (trf_12a)

Note: Gives the same results astrf_12 .

avg(a.ave_busy_tch / a.res_av_denom14)


3.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(a.ave_busy_tch) / sum(a.res_av_denom14)


3.16.21 Handover/call %, (trf_13b)

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

Known problems: Includes also intra-cell handovers that are not sodirectly related to mobility. This is largely dependenton how much overlapping there is in the coverages.

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)



c = p_nbsc_ho

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

Use: Illustrates usually the impact of interference in a non-IUO network.

Known problems: Seetrf_13b .



NTC TAN 0936/2.3 en77

sum(a.tch_ho_seiz)

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






c = p_nbsc_ho

3.16.23 Handover/call %, (trf_13d)

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

Depends much on how much overlapping there is inthe coverage areas.

Usable for a non-IUO network.

Known problems: Includes also intra-cell handovers that are not sodirectly 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 * ------------------------------------------------------------------------- %






c = p_nbsc_ho

3.16.24 IUO, average TCH seizure length on super TRXs, S4(trf_14a)

call time/tch seizures = average period duratio * average traffic / tch seizures.

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

*sum of BTS (avg of super TRX(avg_trx_traf))

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

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


3.16.25 IUO, average TCH seizure length on regular TRXs, S4(trf_15a)

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



NTC TAN 0936/2.3 en78

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

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

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

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


3.16.26 Average TRX traffic, IUO, S4 (trf_16)

avg(ave_busy_tch)


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

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

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

sum(tch_succ_seiz)


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

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

sum(a.tch_call_req)


3.16.29 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

3.16.30 Peak busy TCH (trf_19)

Use: This PI is an important traffic load indicator on thecell level. By following the development of thisindicator and reacting proactively, blocking can beavoided in cells where the traffic growth is smooth.

max(a.peak_busy_tch)




NTC TAN 0936/2.3 en79

3.16.31 Average unit load (trf_20)

sum(a.load_rate)/sum(a.load_denom1)

Counters from table(s):p_nbsc_load

3.16.32 Call time difference between TRXs, S4 (trf_21)

Use: This PI shows as a percentage how much bigger thetraffic of the busiest TRX of a BTS is compared to theleast 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)

Counters from table(s):p_nbsc_rx_qual

3.16.33 Call time difference between TRXs, S4 (trf_21a)

Use: Shows how many times bigger the traffic of thebusiest TRX of a BTS is compared to the least busyTRX 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)

ul_calls=



dl_calls=

sum(freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4





NTC TAN 0936/2.3 en80

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

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

If used over a cell, it can give you an idea about howpotential 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 period= count_of_periods * period_duration/LU_period

X = nbr of MS

==>

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

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

sum(a.sdcch_loc_upd) * 0.1*b.timer_periodic_update_ms

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

count(*).a.period_duration/60

Counters from table(s):a = p_nbsc_res_accessb = c_bts

The sum of incoming handovers from other location areas has to be counted fromp_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.

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

Note: The sampling takes place every 20 seconds.ave_busy_tch counts cumulatively the number ofbusy TCHs.res_av_denom14 counts the number ofsamples taken.

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



NTC TAN 0936/2.3 en81

sum(period_duration*60*ave_busy_tch/res_av_denom14)

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

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

Note: Seetrf_24b .

sum(period_duration*ave_busy_tch/res_av_denom14/60)


unit = hour

3.16.37 SDCCH true seizures (trf_25)

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

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call +sdcch_loc_upd + <IMSI DETACH>)

3.16.38 SDCCH true seizures for call and SS (trf_26)

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

sum(succ_seiz_term+succ_seiz_orig+sdcch_call_re_est+sdcch_emerg_call

- succ_sdcch_sms_est- unsucc _sdcch_sms_est)


3.16.39 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)


3.16.40 Peak busy SDCCH seizures (trf_28)

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

max(a.peak_busy_sdcch)




NTC TAN 0936/2.3 en82

3.16.41 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)


3.16.42 SDCCH seizures (trf_30)

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

sum(a.sdcch_assign+a.sdcch_ho_seiz)


3.16.43 Call time (minutes) from p_nbsc_res_avail (trf_32)

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

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

3.16.44 Call time from p_nbsc_rx_qual (trf_32a)

Known problems: In a high load situation (OMU link) it is possible thatall call time is not measured. In other words, call timecan show a lower value than it has in reality.

Also in the beginning of the call and in handover twosamples are lost, showing a shorter time than inreality.

0.48*



/60

Counters from table(s):a = p_nbsc_rx_qualunit = minutes

3.16.45 Call time from p_nbsc_rx_statistics (trf_32b)

Known problems: In a high load situation it is possible that all call timeis not measured. In other words, call time can show alower value than it has in reality.



NTC TAN 0936/2.3 en83

0.48*



/60

Counters from table(s):a = p_nbsc_rx_statisticsunit = minutes

3.16.46 SDCCH HO seizure % out of HO seizure attempts(trf_33)

100*sum(sdcch_ho_seiz)/sum(sdcch_seiz_att)


3.16.47 SDCCH assignment % out of HO seizure attempts(trf_34)

100*sum(sdcch_assign)/sum(sdcch_seiz_att ) %


3.16.48 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) %


3.16.49 TCH norm seizure % out of TCH call request (trf_36)

sum(tch_norm_seiz)

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

sum(tch_call_req)


3.16.50 TCH FCS seizure % out of TCH FCS attempts (trf_37)

sum(tch_seiz_due_sdcch_con)

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

sum(tch_seiz_att_due_sdcch_con)


3.16.51 TCH FCS seizure % out of congested SDCCH seizureattempts (trf_38)

Use: Indicates the percentage how many SDCCH seizuresare saved by FACCH call setup.



NTC TAN 0936/2.3 en84

sum(tch_seiz_due_sdcch_con)

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

sum(sdcch_seiz_att)


3.16.52 TCH seizures for new calls (trf_39)


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

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


Counters from table(s):a = p_nbsc_trafficc = p_nbsc_ho

3.16.53 HTCH usage, S5 (trf_40)

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

sum(a.ave_tch_busy_halfl)

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

sum(a.ave_tch_avail_half)


3.16.54 MOC rate, S6 (trf_41)

Known problems: Do not include SMS, SS ==> Better accuracy forspeech calls than if 3012 and 3013 were used.

If SDCCH congested and FACCH used for SMS(SS?) then also SMS and SS get included.

tch_moc_seiz_att

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

tch_moc_seiz_att + tch_mtc_seiz_att


3.16.55 MTC rate, S6 (trf_42)

Known problems: Do not include SMS, SS ==> Better accuracy forspeech calls than if 3012 and 3013 were used.

If SDCCH congested and FACCH used for SMS(SS?) then also SMS and SS get included.

tch_moc_seiz_att

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

tch_moc_seiz_att + tch_mtc_seiz_att



NTC TAN 0936/2.3 en85


3.16.56 TCH single band subscriber holding time, S6 (trf_43)

0.48* sum(tch_single_band_hold_time)

Unit: seconds

Counters from table(s):p_nbsc_dual_band

3.16.57 TCH dual band subscriber holding time, S6 (trf_44)

0.48* sum(tch_dual_band_hold_time)

Unit: seconds

Counters from table(s):p_nbsc_dual_band

3.16.58 TCH data call seizures (trf_46)

sum(tch_norm_seiz+tch_ho_seiz+tch_seiz_due_sdcch_con) !! All TCH seizures (

- 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


p_nbsc_traffic

3.16.59 Share of dual band traffic (trf_48)

sum(tch_dual_band_hold_time)

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

sum(tch_single_band_hold_time + tch_dual_band_hold_time)


p_nbsc_dual_band

3.16.60 Call retries due to A interface pool mismatch (trf_49)

Use: Compensation of the blocking caused by the Ainterface 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

3.16.61 HO retries due to A interface pool mismatch (trf_50)

Use: Compensation of the blocking caused by the Ainterface circuit pool mismatch.



NTC TAN 0936/2.3 en86

Sum(bsc_i_unsucc_a_int_circ_type+msc_controlled_in_ho+ho_unsucc_a_int_circ_type)


p_nbsc_ho

3.16.62 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

3.16.63 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)

Unit: seconds


p_nbsc_dual_band

3.17 Traffic Directions

3.17.1 Mobile Originated Calls (moc)

3.17.1.1 SDCCH seizures for MO calls, S2 (moc_1)

Known problems: Includes supplementary services such as call divert.Includes SMS.

sum(a.succ_seiz_orig)


3.17.1.2 Successful MO speech calls, S3 (moc_2)

Note: Triggered when a call is cleared. Excludes setupfailures, TCH drops and TCH busy (congestion)cases.

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



NTC TAN 0936/2.3 en87

3.17.1.3 Successful MO data calls, S3 (moc_3)

Note: Seemoc_2.




3.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 numeratorexcludes setup failures, TCH drops and TCH busy (congestion) cases.

sum(a.nbr_of_calls) where a.counter_id = 44 /* MO call started */

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

sum(a.nbr_of_calls) where a.counter_id = 38 /* MO call completed */


3.17.1.5 MO speech call attempts, S3 (moc_5)

Note: Seemoc_2.




3.17.1.6 MO call bids, S2 (moc_6)

Known problems: Includes supplementary services such as call divert.

Includes SMS.

sum(a.succ_seiz_orig+tch_moc)




NTC TAN 0936/2.3 en88

3.17.2 Mobile Terminated Calls (mtc)

3.17.2.1 SDCCH seizures for MT calls, S2 (mtc_1)

Known problems: Includes SMS. See alsomoc_2.

sum(a.succ_seiz_term)


3.17.2.2 Successful MT speech calls (mtc_2)

Note: Seemoc_2.

Known problems: Seemoc_2.



3.17.2.3 Successful MT data calls, S3 (mtc_3)

Note: Seemoc_2.




3.17.2.4 MT call success ratio, S6 (mtc_4)

Note: MT call attempts are counted when MTCs are foundon SDCCH. The numerator excludes setup failures,TCH 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 */


3.17.2.5 MT speech call attempts (mtc_5)

Note: Seemoc_2.





NTC TAN 0936/2.3 en89


3.17.2.6 MT call attempts, S2 (mtc_6)

Use: Total number of calls bids with establishment cause‘MT’.

Known problems: Includes SMS.

sum(a.succ_seiz_term+tch_mtc)


3.18 Paging (pgn)

3.18.1 Number of paging messages sent, S2 (pgn_1)

Known problems: The number of repagings cannot be separated.

sum(a.paging_msg_sent)


3.18.2 Paging buffer size average, S1 (pgn_2)

Use: To have an idea of how close to problems the BTS hasbeen.

Known problems: It is difficult to say when the problems start. Even ifthe counter 3018 does not yet show the 0 value, theremay have been the situation in one or some of thebuffers that the capacity has run out.

avg(a.min_paging_buf)


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)



NTC TAN 0936/2.3 en90

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 astatistical unit. The minimum value of this is recorded as counter 3018. IfMinPaging Buffer (counter 3018) equals to zero, paging blocking has occurred.

3.18.3 Average paging load, S1 (pgn_3)

avg(a.ave_pch_load/a.res_acc_denom2)


3.18.4 Paging success ratio, S1 (pgn_4)

Known problems: Ghosts can increment the denominator.

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

3.19 Short Message Service (sms)

3.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)


3.19.2 SMS TCH establishment failure % (sms_2)

sum(unsucc_tch_sms_est)

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

sum(succ_tch_sms_est+unsucc_tch_sms_est)


3.19.3 SMS SDCCH establishment failure % (sms_3)

sum(unsucc_tch_sms_est)

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

sum(succ_tch_sms_est+unsucc_tch_sms_est)




NTC TAN 0936/2.3 en91

3.19.4 SMS establishment attempts (sms_4)

sum(succ_TCH_sms_est+unsucc_TCH_sms_est+succ_SDCCH_sms_est+unsucc_SDCCH_sms_est)


3.19.5 SMS SDCCH establishment attempts (sms_5)

sum(succ_sdcch_sms_est+unsucc_sdcch_sms_est)


3.19.6 SMS TCH establishment attempts (sms_6)

sum(succ_TCH_sms_est+unsucc_TCH_sms_est)


3.20 Directed Retry (dr)

3.20.1 DR, outgoing attempts, S3 (dr_1)

sum(a.msc_o_sdcch_tch_at+ a.bsc_o_sdcch_tch_at)


3.20.2 DR attempts, S3 (dr_1a)

Use: Includes all DR cases (to another cell and intra-cell).

sum(p_nbsc_ho.cause_dir_retry)


3.20.3 DR, incoming attempts, S3 (dr_2)

sum(a.msc_i_sdcch_tch_at+ a.bsc_i_sdcch_tch_at)


3.20.4 DR, outgoing success to another cell, S3 (dr_3)

sum(a.msc_o_sdcch_tch+ a.bsc_o_sdcch_tch)


3.20.5 DR, incoming success from another cell, S3 (dr_4)

sum(a.msc_i_sdcch_tch+ a.bsc_i_sdcch_tch)




NTC TAN 0936/2.3 en92

3.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(a.cell_sdcch_tch)


3.20.7 % of new calls successfully handed over to another cellby DR, S3 (dr_6)

100*sum(a.msc_o_sdcch_tch+ a.bsc_o_sdcch_tch)/sum(tch_call_req)


3.21 Availability (ava)

3.21.1 TCH availability %, S4 (ava_1a)

Known problems: If TRXs are locked and BTSs and BCFs are unlocked,the 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)


3.21.2 Average available TCH, S1 (ava_2)


sum(a.ave_avail_full_tch)/sum(a.res_av_denom2)


3.21.3 Average available SDCCH, S1 (ava_3)

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




NTC TAN 0936/2.3 en93

3.21.4 SDCCH availability %, S4 (ava_4)

Known problems: Affected by locked TRX under unlocked BCF andBTS. See TCH availability percentage.

sum(ave_sdcch_sub/res_av_denom3)

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

sum(ave_sdcch_sub/res_av_denom3)+sum(ave_non_avail_sdcch)


3.21.5 Average available FTCH in area, S1 (ava_5)

sum_over_area (

sum_over_BTS(a.ave_avail_full_TCH)/sum_over_BTS(a.res_av_denom2)

)


3.21.6 DMR availability %, S6 (ava_6)

sum(avail_time)

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

sum(total_time)

Counters from table(s):p_nbsc_dmr

3.21.7 DN2 availability %, S6 (ava_7)

sum(avail_time)

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

sum(total_time)

All counters from table(s):p_nbsc_dn2

3.21.8 TRU availability %, S6 (ava_8)

sum(avail_time)

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

sum(total_time)

Counters from table(s):p_nbsc_tru_bie

3.22 Unavailability (uav)

3.22.1 Average unavailable TSL per BTS, S1 (uav_1)




NTC TAN 0936/2.3 en94

sum(a.ave_non_avail_tsl)/sum(a.res_av_denom1)


3.22.2 Average unavailable TSL per BTS, S1 (uav_1a)


avg(ave_non_avail_tsl/res_av_denom1)


3.22.3 Average unavailable TSL per BTS, S1 (uav_1b)


sum(ave_non_avail_tsl/res_av_denom1)

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

count(*)


3.22.4 Total outage time, (uav_2)

Known problems: It should be made possible to differentiate the reasonsfor 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 */

unit = minutes

Counters from table(s):fx_alarm

3.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



NTC TAN 0936/2.3 en95

3.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 BTSlevel cannot be seen.

sum(ave_non_avail_user)

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

sum(ave_non_avail_user + ave_non_avail_int + ave_non_avail_ext)

Counters from table(s):p_nbsc_trx_avail

3.22.7 Share of unavailability due to internal reasons (uav_5)

Known problems: The measurement is made on the BSC level. The BTSlevel cannot be seen. This includes, for example, alsoan electricity break which, in fact, is not a BTS fault.

sum(ave_non_avail_int)

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



3.22.8 Share of unavailability due to external reasons (uav_6)

Known problems: The measurement is made on the BSC level. The BTSlevel cannot be seen.

sum(ave_non_avail_ext)

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



3.22.9 TRX unavailability time due to user (uav_7)

Experiences onuse: Locked TRXs can make this PI show high values.

sum(a.period_duration * a.ave_non_avail_user)


3.22.10 TRX unavailability time due to internal reasons(uav_8)

Known problems: This includes, for example, also an electricity breakwhich, in fact, is not a BTS fault.



NTC TAN 0936/2.3 en96

sum(a.period_duration * a.ave_non_avail_int)


3.22.11 TRX unavailability time due to external reasons(uav_9)

sum(a.period_duration * a.ave_non_avail_ext)


3.23 Location Updates (lu)

3.23.1 Number of LU attempts, S1 (lu_1)

sum(a.sdcch_loc_upd)


3.23.2 Average of LU attempts per hour, S1 (lu_2)

sum(sdcch_loc_upd)

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

avg(period_duration)*count(*)/60


3.23.3 Number of LU attempts, S1 (lu_3)

sum(a.nbr_of_calls) where a.counter_id = 25 /* LU started */


3.24 LU Success % (lsr)

3.24.1 LU success %, S6 (lsr_2)

Use: Probable causes to make this KPI show bad values:interference, coverage, possibly MSC side problems.

Known problems: The measurement is made on the BSC level.

The LU started (51025) is triggered from establishindication. Any problems prior to that cannot be seen.For example, interference prevents a mobile stationfrom making a location update.

Values: Good: >99% .

sum(a.nbr_of_calls) where a.counter_id = 26 /* LU completed */



NTC TAN 0936/2.3 en97

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

sum(a.nbr_of_calls) where a.counter_id = 25 /* LU started */


3.25 Emergency Call (ec)

3.25.1 Emergency calls, S6 (ec_1)

sum(a.nbr_of_calls) where a.counter_id = 35 /* Em.call started */


3.26 Emergency Call Success % (ecs)

3.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 */


3.27 Call Re-establishment (re)

3.27.1 Call re-establishment attempts, S6 (re_1)

sum(a.nbr_of_calls) where a.counter_id = 36 /* Call reest. started */


3.28 Call Re-establishment Success % (res)

3.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 */


3.29 Quality

3.29.1 Downlink quality (dlq)

3.29.1.1 DL BER, S1 (dlq_1)

Known problems: BER % is not a very easy entity for network planners.



NTC TAN 0936/2.3 en98

sum(a.freq_dl_qual0 + ... + a.freq_dl_qualX)

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

sum(a. freq_dl_qual0 + ... + a.freq_dl_qual7)

Unit = BER %Counters from table(s):p_nbsc_rx_qual

3.29.1.2 DL cumulative quality % in class X, S1 (dlq_2)

Use: This PI gives a cumulative percentage of call samplesin classes 1 to X. X=5 is normally used as qualityindicator. If X=5 and this figure is 100 %, then the MSusers obviously have not perceived any qualityproblems.


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



3.29.1.3 DL cumulative quality % in class X, S1 (dlq_2a)



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


Counters from table(s):p_nbsc_rx_statistics

3.29.2 Uplink quality (ulq)

3.29.2.1 UL BER, S1 (ulq_1)

Known problems: BER % is not a very easy entity for network planners.

sum(a.ave_ul_sig_qual)

------------------------ %

sum(a.power_denom6)*100


3.29.2.2 UL cumulative quality % in class X, S1 (ulq_2)

Use: This PI gives a cumulative percentage of call samplesin classes 1 to X. X=5 is normally used as quality



NTC TAN 0936/2.3 en99

indicator. If X=5 and this figure is 100 %, then the MSusers obviously have not perceived any qualityproblems.

Known problems: Investigations in late 1997 showed that UL DTXmakes UL quality seem worse than it actually is. Theimpact was about one 1% unit (1% of samples morein classes 6 and 7). When investigated with field tests,no 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)


3.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)


3.30 Downlink and Uplink Level

3.30.1 Downlink level (dll)

3.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


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

sum over all ranges

(freq_dl_qual0+freq_dl_qual1+freq_dl_qual2+freq_dl_qual3+freq_dl_qual4





NTC TAN 0936/2.3 en100

3.30.2 Uplink level (ull)

3.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


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

sum over all ranges

(freq_ul_qual0+freq_ul_qual1+freq_ul_qual2+freq_ul_qual3+freq_ul_qual4



3.31 Power (pwr)

3.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)


3.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(a.ave_ms_power)/sum(a.power_denom1)


3.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

3.32 Level (lev)

3.32.1 Average DL signal strength, S2 (lev_1)

-110+sum(ave_dl_sig_str)/sum(power_denom3)




NTC TAN 0936/2.3 en101

3.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))

)


3.32.3 Average UL signal strength, S2 (lev_2)

-110+sum(ave_ul_sig_str)/sum(power_denom4)


3.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))

)


3.33 Distance (dis)

3.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 do nothave traffic and for that reason show 0:

peak_ms_bs_dist+ave_dl_sig_str/power_denom3+ave_ul_sig_str/power_denom4 > 0

3.34 Link Balance, Power, Level (lb)

3.34.1 Link balance, S1 (lb_1)

Known problems: Inaccurate.

avg(ave_dl_sig_str/power_denom3) - avg(ave_ul_sig_str/power_denom4)



NTC TAN 0936/2.3 en102


3.34.2 Share in acceptance range, S4 (lb_2)

Known problems: The usefulness of link balance measurement isquestionable.

sum(normal+ms_limited+bs_limited+max_power)

{where class_sig_level <= upper threshold

and class_sig_level >= lower threshold }

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


Counters from table(s):p_nbsc_link_balance

3.34.3 Share in normal, S4 (lb_3)


sum(normal)

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



3.34.4 Share in MS limited, S4 (lb_4)


sum(ms_limited)

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



3.34.5 Share in BS limited, S4 (lb_5)


sum(bs_limited)

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





NTC TAN 0936/2.3 en103

3.34.6 Share in maximum power, S4 (lb_6)


sum(max_power)

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



3.34.7 Average MS power attenuation, S2 (lb_7)

2*sum(ave_MS_power)/sum(power_denom1)

Unit = dBCounters from table(s):p_nbsc_power

3.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 = dBmCounters from table(s):p_nbsc_power

3.34.9 Average UL signal strength, S2 (lb_9)

Use: Values as defined by GSM 5.08 (0..63: 0 = less than-110 dBm, 1 = -110 to -109 dBm, 3 = -109 to -108dBm ... 62 = -49 to -48, 63 =greater than -48)

sum(ave_ul_sig_str)/sum(power_denom4)


3.34.10 Average DL signal strength, S2 (lb_10)

Use: Values as defined by GSM 5.08 (0..63: 0 = less than-110 dBm, 1 = -110 to -109 dBm, 3 = -109 to -108dBm ... 62 = -49 to -48, 63 =greater than -48)

sum(ave_dl_sig_str)/sum(power_denom3)


3.34.11 Average MS power attenuation, S2 (lb_11)

2*sum(ave_MS_power)/sum(power_denom1)

All counters from table(s):p_nbsc_powerUnit = dB



NTC TAN 0936/2.3 en104

3.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

3.35 Call Success (csf)

3.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 phenomenon ismet 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


3.35.2 SDCCH access probability (csf_1a)

Known problems: 1) The momentary SDCCH blocking phenomenon ismet 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


3.35.3 SDCCH success ratio (csf_2a)

Experiences onuse: The best values seen are around 98 %.

Known problems: The formula does not separate the SDCCH callseizures from other seizures (such as LU). The failurerate in the case of a call or LU can greatly differ fromone another, wherefore you cannot use this formulafor SDCCH call success ratio calculation.



NTC TAN 0936/2.3 en105

It is not exactly known how large a share ofsum(sdcch_abis_fail_call +sdcch_abis_fail_old) really are setup failures.

100 - non abis SDCCH drop ratio =


sdcch_netw_act +sdcch_bts_fail+


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


- sum(sdcch_abis_fail_call+sdcch_abis_fail_old)


3.35.4 SDCCH success ratio, area (csf_2f)


Experiences onuse: The best values seen are around 95 %. Includes A

interface blocking!

Known problems: As consistency is a critical property in measurements,the combining of three tables can lead into problems.Unknown factors in the dividor make the values seempessimistic.

1. The calls are cleared before TCH can vary between networksdepending on the call setup time which, again, may depend on theuse of DR or queuing features. Other reasons can be authenticationfails, identity check fails and MOC calls having wrong dialling, forexample.

2. The number of supplementary service requests such as callforwarding is not available as a BTS level counter.

3. This formula does not count correctly the situation when the first callor call re-establishment fails on SDCCH (MS never comes to TCH).

4. For the BTS area there is no way knowing how much SDCCH-SDCCH handovers take place across the area border. The netincoming amount of SDCCH handovers ends up in a successful caseto TCH seizures but they are not seen in the nominator.

5. For the BTS area there is no way knowing how much SDCCH-TCH(DR) handovers take place across the area border. The net incomingamount of SDCCH-TCH (DR) handovers ends up in a successfulcase to TCH seizures but they are not seen in the nominator.

(succ tch seiz) - (call re-establ.)

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

(sdcch seizures for new calls) - (blocked calls)



NTC TAN 0936/2.3 en106

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_trafficb = p_nbsc_res_accessc = p_nbsc_ho

Note:

This formula includes also A interface blocking. It works for call re-establishment if the drop occurs on TCH. If the drop occurs on SDCCH and thecall is re-established, there is double count in the dividor.

3.35.5 SDCCH success ratio, BTS (csf_2g)

Use: BTS level.

Experiences onuse: Includes A interface blocking!

Known problems: As consistency is a critical property in measurements,the combining of three tables can lead into problems.See problems 1-3 fromcsf_2d . Unknown factors inthe denominator make the values seem pessimistic(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)

- supplem.serv. requests ;(unknown factor)

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_res_accessc = p_nbsc_ho



NTC TAN 0936/2.3 en107

Note:

Includes also A interface blocking. If call re-establishment occurs already onSDCCH, the formula is not correct, but if it occurs on TCH, it is correct.

3.35.6 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 theDR has caused.

100-blck_8 =

sum(a.tch_call_req - a.tch_norm_seiz)

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

sum(a.tch_call_req)


3.35.7 TCH access probability without DR and Q (csf_3b)

Use: This PI indicates what would be the TCH blocking ifDR and queuing were not used. When compared tocsf_3a , you can see, assuming that DR is in use, theimprovement that the DR has caused.

Known problems: See XX1.


+ sum(a.tch_qd_call_att-XX1-a.unsrv_qd_call_att) ;calls thatsucceeded via queuing

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

sum(a.tch_call_req)

Counters from table(s):p_nbsc_trafficXX1 = attempts taken from queue to DR (unknown)

3.35.8 TCH access probability without Q (csf_3c)

Use: This PI indicates what would be the blocking ifqueuing 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



NTC TAN 0936/2.3 en108

3.35.9 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)

Counters from table(s):a = p_nbsc_trafficb = p_nbsc_ho

3.35.10 TCH access probability without DR and Q, (csf_3i)

Use: This PI indicates what would be the TCH blocking ifDR and queuing were not used. When compared tocsf_3a , you can see, assuming that DR is in use, theimprovement that the DR has caused. Does notcontain the congestion of the A interface circuit pool.

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

XX1 = attempts taken from queue to DR (unknown)

3.35.11 TCH access probability without DR, (csf_3j)

Use: This PI indicates what would be the TCH blocking ifDR was not used. When compared tocsf_3a , youcan see, assuming that DR is in use, the improvementthat the DR has caused. Does not contain thecongestion of the A interface circuit pool.

100-blck_8c =






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

sum(a.tch_call_req)







NTC TAN 0936/2.3 en109


a = p_nbsc_traffic

b = p_nbsc_ho

3.35.12 TCH access probability, real, (csf_3k)

Use: This KPI is affected by the blocking 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)






a = p_nbsc_traffic

b = p_nbsc_ho

3.35.13 TCH success ratio, area, before call re-establisment(csf_4o)

Use: On the area level. The impact of call re-establishmentis not yet taken into account.






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





c = p_nbsc_ho

3.35.14 TCH success ratio, area, after call re-establishment(csf_4p)







NTC TAN 0936/2.3 en110



- 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





c = p_nbsc_ho

3.35.15 TCH success ratio, BTS, before call re-establisment(csf_4q)


Known problems: Seedcr_4c .

100-dcr_3g =





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




+ sum(c.msc_i_tch_tch+c.bsc_i_tch_tch) ;(TCH-TCH HO in)


c = p_nbsc_ho

3.35.16 TCH success ratio, BTS, after call re-establishment(csf_4r)








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


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


+ sum(c.msc_i_tch_tch+c.bsc_i_tch_tch) ;(TCH-TCH HO in)




c = p_nbsc_ho



NTC TAN 0936/2.3 en111

3.36 Configuration (cnf)

3.36.1 Reuse pattern (cnf_1)

Experiences onuse: For example, 30/3 = 10 means that the frequency can

be repeated with 10 cells!

The smaller the figure, the better the planning.

Known problems: This indicator can be counted from the NMS/2000only 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 BCF) areunlocked.

Missing Counters


NTC TAN 0936/2.3 en112

4 MISSING COUNTERS

This chapter handles counters that are found to be needed in the formulas but aremissing or scheduled for later BSC software releases.

4.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 soonas the DR target list is ready. In this case countersshow as if the queuing took place:tch_qd_call_att is triggered butunsrv_qd_call_att is not.

Planned schedule: S8 (BSC name: REM_FROM_QUEUE_DUE_DR,counter id 1173)

4.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.

4.3 XX3

Meaning: Clear by another procedure during the HO procedure,for example assignment.

Related problem: Affects the counting of HO failure ratios. The ratiocannot be counted accurately (seehfr_2 ).

Planned schedule: Open.

4.4 XX4

Meaning: The number of available time slots for TCH (half orfull rate).

Related problem: Without this counter it is not possible to count theTCH availability in case HTCH is used.

Planned schedule: S9.


NTC TAN 0936/2.3 en113

INDEX

A

A interface blocking 17, 105, 106, 107abbreviations 9

B

BSS formulasava_1a, TCH availability % 92ava_2, average available TCH 92ava_3, average available SDCCH 92ava_4, SDCCH availability % 93ava_5, average available FTCH in area 93ava_6, DMR availability % 93ava_7, DN2 availability % 93ava_8, TRU availability % 93blck_1, TCH raw blocking 62blck_10a, blocked TCH HOs 67blck_10b, blocked TCH HOs 67blck_11a, TCH HO blocking 67blck_11b, TCH HO blocking without Q 67blck_11c, TCH HO blocking 68blck_12, blocked incoming and internal

HO 68blck_12a, blocked incoming and internal

HO 68blck_13, AG blocking 69blck_14, FCS blocking 69blck_15, blocked SDCCH seizure

attempts 69blck_16a, HO blocking % 69blck_16b, handover blocking % 69blck_17, Abis link blocking 70blck_18, blocked FACCH call setup TCH

requests 70blck_19, handover blocking to target cell

70blck_20, handover blocking from target

cell 70blck_5, SDCCH blocking % 62blck_5a, SDCCH real blocking % 62blck_6, TCH raw blocking % on super

TRXs 63blck_7, TCH raw blocking % on regular

TRXs 63blck_8, TCH call blocking, before DR 63blck_8b, TCH call blocking %, DR

compensated 63blck_8c, TCH call blocking %, DR

compensated, EFR excluded 65blck_9a, blocked calls 66blck_9b, blocked calls 66cnf_1, reuse pattern 111cngt_1, TCH congestion time 59cngt_2, SDCCH congestion time 59csf_1, SDCCH access probability 104csf_1a, SDCCH access probability 104csf_2a, SDCCH success ratio 104csf_2f, SDCCH success ratio, area 105csf_2g, SDCCH success ratio, BTS 106csf_3a, TCH access probability without

DR 107csf_3b, TCH access probability without

DR and Q 107csf_3c, TCH access probability without Q

107csf_3d, TCH access probability, real 108csf_3i, TCH access probability without

DR and Q 108csf_3j, TCH access probability without

DR 108csf_3k, TCH access probability, real 109csf_4o, TCH success ratio, area, before

call re-establisment 109csf_4p, TCH success ratio, area, after call

re-establishment 109csf_4q, TCH success ratio, BTS, before

call re-establisment 110csf_4r, TCH success ratio, BTS, after call

re-establishment 110cssr_2, SDCCH, TCH Setup Success % 18dcf_2, TCH drop calls in HO 23dcf_3, TCH drop calls in BSC outgoing

HO 23dcf_4, TCH drop calls in intra-cell HO 23dcf_6, TCH drop calls in intra-BSC HO 23dcf_7, drop calls in BSC incoming HO 24dcr_10, drops per erlang, before re-

establishment 28dcr_10a, drops per erlang, after re-

establishment 28dcr_3f, TCH drop call %, area, real, after

re-establishment 24dcr_3g, TCH drop call %, area, real,

before re-establishment 24


NTC TAN 0936/2.3 en114

dcr_4c, TCH drop-out %, BTS level,before call re-establishment 25

dcr_4d, TCH drop-out %, BTS level,before call re-establishment 26

dcr_5, TCH drop call (droppedconversation) %, BSC level 26

dcr_5a, TCH drop call (droppedconversation) %, area 27

dis_1, average MS-BS distance 101dll_1, share % per range 99dlq_1, DL BER 97dlq_2, DL cumulative quality % in class X

98dlq_2a, DL cumulative quality % in class

X 98dr_1, DR, outgoing attempts 91dr_1a, DR attempts 91dr_2, DR, incoming attempts 91dr_3, DR, outgoing success to another cell

91dr_4, DR, incoming success from another

cell 91dr_5, DR, intra-cell success 92dr_6, % of new calls successfully handed

over to another cell by DR 92ec_1, emergency calls 97ecs_1, emergency call success % 97hfr_1, total HO failure % 37hfr_10, external source HO failure % 43hfr_12, HO failure % from super to regular

43hfr_13, HO failure % from regular to super

43hfr_14, share of HO failures from regular

to super due to return 43hfr_15, share of HO failures from regular

to super due to MS lost 43hfr_16, share of HO failures from regular

to super due to another cause 44hfr_17, share of HO failures from super to

regular due to return 44hfr_18, share of HO failures from super to

regular due to MS lost 44hfr_19, share of HO failures from super to

regular due to another cause 44hfr_2, total HO failure % 37hfr_20, SDCCH-SDCCH HO failure % 45hfr_21, SDCCH-TCH HO failure % 45hfr_22, TCH-TCH HO failure % 45hfr_23, SDCCH-SDCCH incoming HO

failure % 46hfr_24, SDCCH-SDCCH outgoing HO

failure ratio 46hfr_25, SDCCH-TCH incoming HO

failure % 46hfr_26, SDCCH-TCH outgoing HO

failure % 46hfr_27,TCH-TCH incoming HO failure %

46hfr_28, TCH-TCH outgoing HO failure %

46hfr_29, MSC ctrl HO failure %, blocking

46hfr_30, MSC ctrl HO failure %, not

allowed 47hfr_31, MSC ctrl HO failure %, return to

old 47hfr_32, MSC ctrl HO failure %, call clear

47hfr_33, MSC ctrl HO failure %, end HO

47hfr_34, MSC ctrl HO failure %, end HO

BSS 47hfr_35, MSC ctrl HO failure %, wrong A

interface 47hfr_36, MSC ctrl HO failure %, adjacent

cell error 47hfr_37, BSC ctrl HO failure %, blocking

48hfr_38, BSC ctrl HO failure %, not

allowed 48hfr_39, BSC ctrl HO failure %, return to

old 48hfr_3a, intra-cell HO failure share 38hfr_3b, intra-cell HO failure share 39hfr_4, incoming MSC ctrl HO failure % 39hfr_40, BSC ctrl HO failure %, call clear

48hfr_41, BSC ctrl HO failure %, end HO 48hfr_42, BSC ctrl HO failure %, end HO

BSS 48hfr_43, BSC ctrl HO failure %, wrong A

interface 48hfr_44, BSC ctrl HO drop call % 48hfr_45, intra-cell HO failure %,

cell_fail_lack 49hfr_46, intra-cell HO failure %, not

allowed 49hfr_47, intra-cell HO failure %, return to

old 49hfr_48, intra-cell HO failure %, call clear

49hfr_49, intra-cell HO failure %, MS lost 49hfr_4a, incoming MSC ctrl HO failure


NTC TAN 0936/2.3 en115

share 39hfr_4b, incoming MSC ctrl HO failure

share 40hfr_50, intra-cell HO failure %, BSS

problem 49hfr_51, intra-cell HO failure %, drop call

49hfr_52, HO failure % to adjacent cell 49hfr_53, HO failure % from adjacent cell 50hfr_54a, HO failure %, blocking excluded

50hfr_55, HO failure % due to radio

interface blocking 50hfr_56, intra-cell HO failure %, wrong A

interface 50hfr_57, intra-cell HO failure % 51hfr_58, HO failures to target cell 51hfr_59, HO failures from target cell 51hfr_5a, outgoing MSC ctrl HO failure

share % 40hfr_5b, outgoing MSC ctrl HO failure

share % 40hfr_6, incoming BSC ctrl HO failure % 41hfr_6a, incoming BSC ctrl HO failure

share % 41hfr_6b, incoming BSC ctrl HO failure %

41hfr_7, outgoing BSC ctrl HO failure % 41hfr_7a, outgoing BSC ctrl HO failure

share % 42hfr_7b, outgoing BSC ctrl HO failure

share % 42hfr_8, internal inter HO failure % 42hfr_9, internal intra HO failure % 42ho_ 13c, HO attempts, outgoing and intra-

cell, S5 31ho_1, return from super TRXs to regular

TRX 29ho_10, BSC incoming HO attempts 30ho_11, BSC outgoing HO attempts 30ho_13, HO attempts, S4 30ho_13a, HO attempts, S3 31ho_13d, HO attempts, outgoing and intra-

cell, S6 31ho_13e, HO attempts, outgoing and intra-

cell 31ho_14a, TCH requests for HO 31ho_14b, TCH requests for HO 31ho_15, TCH seizures for HO 32ho_16, TCH-TCH HO attempts 32ho_17, SDCCH-TCH HO attempts

(ho_17) 32

ho_18, SDCCH-SDCCH HO attempts 32ho_19, TCH-TCH HO success 32ho_2, HO attempts from regular TRXs to

super 29ho_20, SDCCH-TCH HO success 33ho_21, SDCCH-SDCCH HO success 33ho_22, MSC controlled HO attempts 33ho_23, BSC controlled HO attempts 33ho_24, intra-cell HO attempts 33ho_25, MSC controlled HO success 34ho_26, BSC controlled HO success 34ho_27, intra-cell HO success 34ho_28, MSC incoming HO success 34ho_29, MSC outgoing HO success 34ho_3, HO attempts from super to regular

29ho_31, BSC outgoing HO success 34ho_32, incoming HO success 35ho_33, outgoing HO success 35ho_34, outgoing HO attempts 35ho_35, incoming HO attempts 35ho_36, outgoing SDCCH-SDCCH HO

attempts 35ho_37, incoming SDCCH-SDCCH HO

attempts 35ho_38, outgoing SDCCH-TCH HO

attempts 35ho_39, incoming SDCCH-TCH HO

attempts 35ho_4, share of HO attempts from super to

regular due to DL quality 29ho_40, outgoing TCH-TCH HO attempts

36ho_41, incoming TCH-TCH HO attempts

36ho_42, outgoing SDCCH-SDCCH HO

success 36ho_43, incoming SDCCH-SDCCH HO

success 36ho_44, outgoing SDCCH-TCH HO

success 36ho_45, incoming SDCCH-TCH HO

success 36ho_46, outgoing TCH-TCH HO success

36ho_47, incoming TCH-TCH HO success

36ho_5, share of HO attempts from super to

regular due to DL interference 29ho_6, share of HO attempts from super to

regular due to UL interference 30ho_7, share of HO attempts from super to


NTC TAN 0936/2.3 en116

regular due to bad C/I 30ho_8, MSC incoming HO attempts 30ho_9, MSC outgoing HO attempts 30ho-30, BSC incoming HO success 34hof_1, outgoing HO failures due to lack of

resources 55hof_10, failed outgoing HO, return to old

57hof_12, outgoing HO failures 57hof_13, intra-cell HO failure, return to old

channel 57hof_14, intra-cell HO failure, drop call 57hof_15, incoming HO failures 57hof_2, incoming HO failures due to lack of

resources 55hof_3, TCH HO failures when return to

old channel was successful 55hof_4, SDCCH HO failures when return to

old channel was successful 55hof_5, MSC incoming HO failures 56hof_6, MSC outgoing HO failures 56hof_6a, MSC outgoing HO failures 56hof_7, BSC incoming HO failures 56hof_7a, BSC incoming HO failures 56hof_8, BSC outgoing HO failures 56hof_8a, BSC outgoing HO failures 56hof_9a, intra-cell HO failures 57hsr_1, MSC controlled outgoing SDCCH-

SDCCH HO success % 52hsr_10, MSC controlled incoming

SDCCH-SDCCH HO success %53

hsr_11, MSC controlled incomingSDCCH-TCH HO success % 53

hsr_12, MSC controlled incoming TCH-TCH HO success % 53

hsr_13, BSC controlled incomingSDCCH-SDCCH HO success %53

hsr_14, BSC controlled incomingSDCCH-TCH HO success % 54

hsr_15, BSC controlled incoming TCH-TCH HO success % 54

hsr_16, BSC controlled incoming HOsuccess % 54

hsr_17, MSC controlled incoming HOsuccess % 54

hsr_18, incoming HO success % 54hsr_19, outgoing HO success % 54hsr_2, MSC controlled outgoing SDCCH-

TCH HO success % 52hsr_20, intra-cell SDCCH-SDCCH HO

success % 54hsr_21, intra-cell SDCCH-TCH HO

success % 55hsr_22, intra-cell TCH-TCH HO success

% 55hsr_3, MSC controlled outgoing TCH-

TCH HO success % 52hsr_4, BSC controlled outgoing SDCCH-

SDCCH HO success % 52hsr_5, BSC controlled outgoing SDCCH-

TCH HO success % 52hsr_6, BSC controlled outgoing TCH-

TCH HO success % 52hsr_7, intra-cell SDCCH-SDCCH HO

success % 53hsr_8, intra-cell SDCCH-TCH HO

success % 53hsr_9, intra-cell TCH-TCH HO success %

53itf_1, UL interference, BTS level 57itf_2, idle TSL percentage of time in band

X, TRX level, IUO 58itf_3, UL interference from IUO, TRX

level 58itf_4, UL interference from Power

Control, TRX level 59lb_1, link balance 101lb_10, average DL signal strength 103lb_11, average MS power attenuation 103lb_12, average BS power attenuation 104lb_2, share in acceptance range 102lb_3, share in normal 102lb_4, share in MS limited 102lb_5, share in BS limited 102lb_6, share in maximum power 103lb_7, average MS power attenuation 103lb_7b, average MS power 103lb_9, average UL signal strength 103lev_1, average DL signal strength 100lev_1a, average DL signal strength 101lev_2, average UL signal strength 101lev_2a, average UL signal strength 101lsr_2, LU success % 96lu_1, number of LU attempts 96lu_2, average of LU attempts per hour 96lu_3, number of LU attempts 96moc_1, SDCCH seizures for MO calls 86moc_2, successful MO speech calls 86moc_3, successful MO data calls 87moc_4, MO call success ratio 87moc_5, MO speech call attempts 87moc_6, MO call bids 5, 87


NTC TAN 0936/2.3 en117

mtc_1, SDCCH seizures for MT calls 88mtc_2, successful MT speech calls 88mtc_3, successful MT data calls 88mtc_4, MT call success ratio 88mtc_5, MT speech call attempts 88mtc_6, MT call attempts 89pgn_1, number of paging messages sent

89pgn_2, paging buffer size average 89pgn_3, average paging load 90pgn_4, paging success ratio 90pwr_1, average MS power 100pwr_1b, average MS power 100pwr_2, average BS power 100que_1, queued, served TCH call requests

% 60que_2, queued, served TCH HO requests

% 60que_2a, queued, served TCH HO requests

% 60que_3, successful queued TCH requests

61que_4, successful non-queued TCH

requests 61que_5, successful queued TCH HO

requests 61que_6, successful non-queued TCH HO

requests 61que_7, non-queued, served TCH call

requests % 61que_8, non-queued, served TCH HO

requests % 61que_8a, non-queued, served TCH HO

requests % 62rach_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 13re_1, call re-establishment attempts 97res_1, call re-establishment success % 97sd_1, ghosts detected on SDCCH and

other failures 14sdr_1a, SDCCH Drop %, blocking

excluded 17sdr_2, SDCCH drop %, blocking & Abis

failure excluded 18sdr_3a, illegal establishment cause % 18sms_1, SMS establishment failure % 90sms_2, SMS TCH establishment failure %

90sms_3, SMS SDCCH establishment

failure % 90sms_4, SMS establishment attempts 91sms_5, SMS SDCCH establishment

attempts 91sms_6, SMS TCH establishment attempts

91trf_1, TCH traffic sum 70trf_10, super TRX TCH traffic 75trf_10a, sum of super TRX TCH traffic 75trf_11, average SDCCH traffic, erlang 75trf_11a, average SDCCH traffic, erlang 75trf_12, average TCH traffic, erlang 76trf_12a, average TCH traffic, erlang 76trf_12b, average TCH traffic, erlang 76trf_13b, handover / call % 76trf_13c, intra-cell handover / call % 76trf_13d, handover/call % 77trf_14a, IUO, average TCH seizure length

on super TRXs 77trf_15a, IUO, average TCH seizure length

on regular TRXs 77trf_16, average TRX traffic, IUO 78trf_17a, average TRX TCH seizure length

78trf_18, TCH requests for new call 78trf_18a, TCH requests for a new call 78trf_19, peak busy TCH 78trf_1a, TCH traffic sum 71trf_20, average unit load 79trf_21, call time difference between TRXs

79trf_21a, call time difference between

TRXs 79trf_23a, number of mobiles located in a

cell, BSC 80trf_24b, total TCH seizure time (call time)

80trf_24c, total TCH seizure time (call time

in hours) 81trf_25, SDCCH true seizures 81trf_26, SDCCH true seizures for call and

SS 81trf_27, SDCCH true seizures for call,

SMS, SS 81trf_28, peak busy SDCCH seizures 81trf_29, IUO layer usage % 82trf_2d, average call length 71trf_3, TCH usage 72trf_30, SDCCH seizures 82trf_32, call time (minutes) from


NTC TAN 0936/2.3 en118

p_nbsc_res_avail 82trf_32a, call time from p_nbsc_rx_qual 82trf_32b, call time from

p_nbsc_rx_statistics 82trf_33, SDCCH HO seizure % out of HO

seizure attempts 83trf_34, SDCCH assignment % out of HO

seizure attempts 83trf_35, TCH HO seizure % out of TCH HO

seizure request 83trf_36, TCH norm seizure % out of TCH

call request 83trf_37, TCH FCS seizure % out of TCH

FCS attempts 83trf_38, TCH FCS seizure % out of

congested SDCCH seizureattempts 83

trf_39, TCH seizures for new calls 84trf_3b, FTCH usage 72trf_4, average SDCCH holding time 72trf_40, HTCH usage 84trf_41, MOC rate 84trf_42, MTC rate 84trf_43, TCH single band subscriber

holding time 85trf_44, TCH dual band subscriber holding

time 85trf_46, TCH data call seizures 85trf_48, share of dual band traffic 85trf_49, call retries due to A interface pool

mismatch 85trf_5, average FTCH holding time 72trf_50, HO retries due to A interface pool

mismatch 85trf_51, TCH single band subscribers’

share of holding time 86trf_52, TCH dual band subscribers’ share

of holding time 86trf_6, TCH seizures for new call (call bids)

73trf_7b, SDCCH usage % 73trf_8, TCH traffic absorption on super 73trf_8a, TCH traffic absorption on super 74trf_9, average cell TCH traffic from IUO

74trf_9a, cell TCH traffic from IUO 74uav_1, average unavailable TCH per BTS

93uav_1a, average unavailable TCH per

BTS 94uav_1b, average unavailable TCH per

BTS 94

uav_2, total outage time 94uav_3, number of outages 94uav_4, share of unavailability due to user

95uav_5, share of unavailability due to

internal reasons 95uav_6, share of unavailability due to

external reasons 95uav_7, TRX unavailability time due to

user 95uav_8, TRX unavailability time due to

internal reasons 95uav_9, TRX unavailability time due to

external reasons 96ull_1, share % per range 100ulq_1, UL BER 98ulq_2, UL cumulative quality % in class X

98ulq_2a, UL cumulative quality % in class

X 99BSS Network Doctor 8BTS group 10

C

countersmissing 112SDCCH drop 14TCH drop call 19

D

documentationBSS Network Doctor 8other Nokia documents 8

dtpad 7

F

formula typesavailability (ava) 92blocking (blck) 62call re-establishment (re) 97call re-establishment success % (res) 97call success (csf) 104configuration (cnf) 111congestion (cngt) 59directed retry (dr) 91distance (dis) 101downlink level (dll) 99downlink quality (dlq) 97drop call failures (dcf) 23


NTC TAN 0936/2.3 en119

emergency call (ec) 97emergency call success % (ecs) 97handover (ho) 29handover failure % (hfr) 37handover failures (hof) 55handover success % (hsr) 52interference (itf) 57level (lev) 100link balance, power, level (lb) 101location updates (lu) 96LU success % (lsr) 96mobile originated calls (moc) 86mobile terminated calls (mtc) 88paging (pgn) 89power (pwr) 100queuing (que) 60random access (rach) 12SDCCH drop failures (sd) 14SDCCH drop ratio (sdr) 17setup success ratio (cssr) 18short message service (sms) 90TCH drop call % (dcr) 24traffic (trf) 70unavailability (uav) 93uplink level (ull) 100uplink quality (ulq) 98

further information 7

G

ghost accesses 17, 18

K

Key Performance Indicator (KPI) 11

M

missing counters 112

P

prerequisitesfor user knowledge 7

T

terms 10typographic conventions

text styles 8

V

vi 7

W

where to find more 7

Date post:	26-Dec-2015
Category:	Documents
Upload:	adeel-muhammad
View:	18 times
Download:	0 times